Patent Grant
9451010
The present disclosure is directed, in general, to containerized software, and more specifically, to systems and methods for distributing containerized software.
Online shopping has increased in recent years. Consumers use technology to simplify the shopping experience to shop from home without needing to travel to the store. Merchants have become increasingly competitive to market their products and services to consumers over the Internet. Traditionally, when a consumer sees an advertisement for a product or desires to purchase something online, the consumer needs to visit the website for the merchant in order to complete the transaction. This may be undesirable in certain situations. For example, consumers may not wish to be distracted by advertisements or may not wish to leave the website that they are viewing in order to purchase something. As a result, online sales potential is diminished due to lack of convenience from the consumer perspective. Additionally, hosts of the website the consumer is viewing may not want consumers to leave their website to go transact business elsewhere.
Videos and other types of media are often popular among viewers. Websites, such as YouTube, allow users to post videos for others to view. Some videos gain popularity that can be tracked through number of views or “hits.”
Monetization of media content can present challenges even despite the popularity of the video. For example, some websites provide advertising that is displayed prior to the video or elsewhere on the webpage. Such advertisements may interfere with the video content and may annoy viewers. While website advertisement may generate some revenue, that revenue is often primarily retained by the website hosting the video content. This results in a dynamic where the website doing the hosting profits financially while the creators of the video content, although gaining notoriety, often struggle to see a return on investment.
Accordingly, there is a need for methods, systems, devices and computer readable media that take into account one or more of these issues and possibly other issues as well. For example, there is a need to bring the store to the consumer.
According to various embodiments of the present disclosure, methods, systems devices and computer readable media are disclosed for enabling containerized software.
In one embodiment, a method is provided for including objects with media content. The method includes receiving, at one or more servers, a request for the media content to be displayed at an endpoint. The method includes identifying information about an environment associated with the endpoint. The method includes identifying a set of objects to include in a container for the media content based on the information identified about the environment. At least one of the objects includes program code for completing an electronic commerce transaction during display of the media content. Additionally, the method includes sending, by one or more servers, the set of objects to the endpoint.
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; and the term “controller” means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
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:
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, net books, tablet computers (e.g., IPAD)), a switch, mobile phones (e.g., including IPHONE and Android-based phones), 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 130. In various embodiments, the endpoint(s) 110 and 120 may be a website or email message. 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 801.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.
The communication network 130 and links 105, 115 and 125 to the communication network 130 may include, but is 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 (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 or communication network 130 may be on the Internet.
Although an 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.
When the endpoints(s) 110 and 120 communicate with one another, any of a variety of security schemes may be utilized. As an example, in particular embodiments, endpoint(s) 110 may represent a client and endpoint(s) 120 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 into 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.
Embodiments of the present disclosure provide innovative new methods 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 online purchases. 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, they are much less likely to leave their current activity to visit some external Internet destination.
Various embodiments of the present disclosure bring the product information or store to the consumer. Various embodiments of the present disclosure utilize an innovative new Smart Container™ code/technology that virally syndicates across the web, for example, using components described with reference to
Shopping and marketing experiences can be enhanced when interactive media is used. The container 205 serves up interactive media to users. For example, one of the objects 210 in the container 205 is a media player 215. The media player 215 includes instructions and parameters for rendering or otherwise displaying media content in a display unit 220 located at the endpoint 225. The media player 215 displays or streams media content from media server(s) 230 in the display unit 220 at the endpoint 225. For example, the media player 215 may reference a URL or other location to stream media content from the media server(s) 230. In some examples, the media player 215 may stream content from websites, such as YouTube™. Examples of media content that may be displayed include video data (such as video clips and animation), image data (e.g., still images from the video data, advertisements, pictures of goods or services, etc.) and audio data (e.g., narration or marketing content associated with the video data or the image data, music or songs). Various embodiments recognize that one of the most appealing forms of media for sales and shopping is video. Video allows a much more lifelike representation than text or static pictures. Video also creates a rich product browsing or shopping experience.
In various embodiments of the present disclosure, the container 205 supports many different types of transactions. For example, the container 205 can be configured in a variety of ways to address an entire value chain of online marketing and shopping. The value chain of online marketing and shopping includes impressions, clicks (e.g., enticing a viewer to click on an object and be directed to a different website or to different content within the container 205), lead generation (e.g., submitting personal information with a request for offers of products or service), and performing electronic commerce transactions. Electronic commerce is the buying and selling of products or services over computer networks, such as the Internet. Electronic commerce transactions are transactions associated with electronic commerce. In non-limiting examples, electronic commerce transactions include the purchase or sale of goods and services and donation of items of value (e.g., money, goods or services) to an organization (e.g., a charity, campaign, cause, etc.). In other non-limiting examples, electronic commerce transactions may encompass activities (such as impressions, clicks or lead generation) that lead up to other electronic commerce transactions (such as the purchase or sale of goods and services).
The container 205 includes transaction objects 235 to support the different types of transactions. The transaction objects 235 include code for marketing and completing transactions within the container 205. For example, the transaction objects 235 may include images and information about a selection of products or services being offered, data for competing payment transactions, an electronic shopping cart and/or other data for completion of electronic commerce transactions. The media content, such as video clips, may be displayed by the media player 215 at one of the endpoints to allow a consumer to learn more about the products, services or transactions supported by the container 205. The consumer can select any of these offered items to get more details (e.g., using the transaction objects 235), all enclosed within the container 205.
The syndication objects 240 include code for allowing a user to share, embed or otherwise send a container to another endpoint. For example, the syndication objects 240 include code for allowing a user to share the media content (and consequently the objects accompanying the media content in the container 205) on a social website, embed within a webpage or send the container 205 (or at least a link (e.g., uniform resource locator (URL)) for the container) via an electronic message (e.g., email, text message, instant message).
The authentication objects 245 include program code for allowing a user of the endpoint 225 to authenticate or login to an account associated with the container 205. The authentication objects 245 may provide a user interface for a user to login or may automatically log a user in based on a combination of one or more of user settings, device recognition, and/or data stored in a cookie. The account may be a user account for the provider of the container or the merchant associated with the container. For example, the account may be used for easy payment processing of transactions or a distributed shopping cart, as will be described in greater detail below. If the user selects to share the container 205, the authentication objects 245 may include information about the user sharing the container 205 for data tracking analytics and/or identifying information about which objects to include in the syndicated container.
The tethering objects 250 include program code for tethering the container 205 with another container at another endpoint. The tethering objects 250 enhance the shopping experience for different users. The tethering objects 250 enable a shared container experience between two or more different users. For example, the tethering objects 250 may synchronize the display of the media content, allow users to share purchases or a shopping cart, provide an interface for text, voice and/or video chat between the users.
The reporting objects 255 include program code for keeping track of information about the container 205. For example, the reporting objects 255 may report information on clicks, impressions, lead generation, product sales, donations, users, syndication paths, syndication locations, and/or any other reportable metrics for merchants and/or container providers to track and improve container performance. The description of the objects 210 included in the container 205 is not intended to be exhaustive or limiting. Any other suitable types of objects may be included in the container 205.
Because the code for the container 205 handles all the complexity, in some embodiments, the container 205 can turn a simple web site into an instant e-commerce store. The container 205 enables users to transact online without having to deal with the complexity of setting up an e-commerce site. For merchants with an e-commerce site, the container 205 readily enables a rich shopping experience with the interaction between the media content and transaction objects 235. In non-limiting examples of a creative hobbyist or local band, the container 205 allows the user to readily sell directly to interested consumers. In some embodiments, the transaction objects 235 may include offers in the container 205 for custom merchandise. For example, merchants can custom design a selection of apparel with their art and graphics to be sold along with their own creations. Some embodiments may dynamically produce and ship the custom apparel for the merchant, eliminating the need to manage inventory, and providing online customers with a richer line of products. Because the e-commerce store uses the container 205, the e-commerce store can also propagate out onto all forms of viral syndication methods as well.
These offered items (products or services) may be items being advertised or sold. Depending on the type, the container 205 may allow the consumer to request to be contacted, or even purchase the object, within the container 205. The consumer need not leave their current activity or web page. The offered items could also include getting discounts or coupons. The offered items may even be an opportunity to donate to a charity or political campaign. In certain instances, it does make sense to visit another Internet designation, and if appropriate, the consumer can be linked there as well.
The objects 210 in the container 205 are supported by backend event server(s) 260. The objects 210 are individual applications (e.g., mini apps or applets) that provide the functionality for implementing the container 205. The objects 210 are intelligent and lightweight, which improves the transferability of the container 205 while allowing the container 205 to implement tasks in a dynamic and effective manner. The objects 210 may not include everything necessary for handling all the tasks required. The objects 210 may communicate with one or more servers in backend event server(s) 260 to complete tasks in the container 205.
For example, to process a transaction, the transaction objects 235 may securely send payment information to payment server(s) 265. In other examples, the transaction objects 235 or authentication objects 245 may send information about impressions, clicks, shares, and/or user login information to admin server(s) 270 for reporting and analytics. In other examples, all the objects needed for the container 205 may not be initially provisioned. For example, to keep the container initially lightweight, identifiers or locations for objects may be included in the container 205 initially with the objects later provisioned by the objects server(s) 275. In another example, certain objects may be provided in the container 205 based on initial information about the endpoint 225 (e.g., object selection based on assumed device type, website location, or programming language). Upon recognition that additional or different objects should be included in the container 205, the objects server(s) 275 may provision the additional or different objects for improved container experience at the endpoint 225. Peer event server(s) 280 may send and receive information from objects to handle information related to sharing and purchases. For example, the peer event server(s) 280 support tethering events, such as notification of video clip views, purchases, and/or user messaging.
The container 205 can virally syndicate across the Internet following the more popular network paths. The container 205 can be hosted on traditional web pages, blogs, contained in emails, operate on mobile devices, or propagate social networks. Because the container 205 code is flexible, the container 205 can also be set up in the form factor of a display ad unit and distributed via ad servers on display advertising networks. When the code for the container 205 exists on social networks like Facebook™, the container 205 can ride the wave of user “likes”. For example, if a woman shopper likes some great shoes shown in a video in the container 205, the container 205 code can propagate directly to their “wall.” Now all her friends see the video and products in the container, and can view or transact right there on their own wall. Of course, if any of their friends also “like” it, the container 205 code propagates and rides the wave further out into that branch of the social network yielding a potential exponential growth factor. In other examples, the container 205 objects may support 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 may donate to the cause within the container 205. In another example, such as sports, 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™, and a container 205 code could exist on such an IP TV box as well, enabling the sharing of a container 205 in a variety of Internet connected devices.
Another form of tracking relates to how the container 205 is propagated. A merchant may wish to use affiliates to help syndicate the container 205 and pay a percentage based on the transactions resulting from their work. The container 205 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.
The container 205 is a smart container in that the container 205 is capable of customizing automatically based on the environment to which the container 205 is propagated. For example, the objects 210 included in the container 205 may be configured or selected in real-time based on different criteria. The container 205 is generated by the configurator 285 when the configurator 285 receives a request for the container 205, such as an embed code 290. The configurator 285 is a backend service or application that runs on a server (e.g., one or more of the server(s) 102 in
The environment associated with the endpoint 225 where the container is being propagated to is one example of criteria that may be used to select or otherwise configure the objects 210 included in the container 205. For example, the configurator 285 may identify this environment information from the embed code 290. The embed code 290 is a request for the container 205 that includes information, such as, for example, without limitation, an identifier of the container 205 being propagated, an originating Internet Protocol (IP) address, a time the request was sent and/or received, reference codes, such as a requester identifier, merchant identifier, website (e.g., URL) where the embed code 290 was sent from and/or is requesting the container 205 be rendered at, and/or other information that may be identified about the environment where container 205 renders. From the IP address and/or the website information, the configurator 285 may identify a location of the endpoint 225, a type of device (e.g., mobile device, computer, etc.) of the endpoint, the website (e.g., stand alone web page, embedded within a webpage, displayed on a social website) for the endpoint and/or other information about the environment.
In some examples, if the device is a traditional PC or laptop, the configurator 285 will include objects for the container 205 to render using the optimal technology or rendering parameters, which, for this purpose, may be flash video. On mobile devices, such as IPhones, IPads, or Android phones, the rendering parameters may be selected as HTML5 or a native interactive app. Based on the information about how the content should be rendered, configurator 285 includes the appropriate objects for the media player 215 to render properly for the environment. Beyond device type, there are other dimensions of customization. Smaller devices and some environments, such as a social site, restrict window sizes, so the media player 215 in the container 205 adapts to properly render the media content.
In other examples, the configurator 285 may identify which products to advertise or ways to customize the media content based on the location of the endpoint 225, which can be identified from the IP address. For example, the container 205 can provide different content customized based on geo-location. In one example, if the location of the endpoint is in a cold climate, objects in the transaction objects 235 may be selected to offer appropriate seasonal products with the media content. In other examples, the media content may be customized based on the location. For example, text associated with the media content and the transaction objects 235 may be selected based on a language commonly spoken at the location. In other examples, the media content may be selected to appeal to location preferred sports teams, activities, etc.
As other examples of criteria that may be used to select or otherwise configure the objects 210 included in the container 205, the configurator 285 may communicate with backend event server(s) 260 to identify the objects to identify objects to include in the container 205. For example, the configurator 285 may identify products to market or video clips to send based on merchant information accessible via the admin server(s) 270. For example, the status of a marketing campaign may be used to select or otherwise configure the objects 210 and media content included in the container 205. The objects in the container 205 may be updated and/or selected based on real-time information about successes and failures based on information about the marketing campaign. For example, embodiments of the present disclosure track sales data and video propagation data, such as what video clips are popular, and/or a demographic of the viewers syndicating or viewing the media content. The server(s) 102 in
The admin server(s) 270 can track data on how a merchant campaign is performing and when merchants launch and syndicate their container 205 code onto the Internet. For example, the reporting objects can report back the status on events and transactions of interest, (e.g., how many impressions, video views, clicks, leads, sales have occurred). All such statuses can be sent back as events occur, providing details on how they are doing. Because the containers 205 are smart, the server(s) can instruct the container 205 to change behavior, offer different clips, update products, or to stop the marketing or sales campaign.
The objects in the container 205 code know about each other in certain embodiments. When a video is playing, the container 205 can update the product and service objects being shown that correspond with the particular sequence in a video segment. The container 205 allows a shopping channel to be created and syndicated across the Internet.
The code for the container 205 is designed to be highly scalable in particular embodiments. Rather than burden a single website with massive traffic which would result from a traditional model of bringing all consumers to the store, the code for the container 205 operates in a distributed manner. In particular embodiments, the code for the container 205 executes at the endpoint 225, (e.g., on a blog, social network or mobile device). The container 205 can fetch the instructions when stated, and then gather product items and video streams from a worldwide distributed content delivery network (e.g., the network 130). This results in highly scalable architecture allowing millions of concurrent consumers.
Although the container 205 has been described with media content and objects 210, such media content and objects 210 may not all be sent to an endpoint at the same time or as a bundle. Rather, in particular embodiments, information concerning the container may initially be stored on, for example, a server accessed by the endpoint. Then, when the endpoint requests the information for the container, additional information can be dynamically pushed to the endpoint or pulled from the endpoint (e.g., by the server sending a pointer to the endpoint).
By utilizing such a dynamic push/pull scenario, a single container 205 can be modified over time. As a simple example, a price may be associated with an item for sale at a point in time; however, when that point in time changes, the price for that item may change. Although the price changes, the initial information for requesting the container 205 does not change. Further examples of dynamic content will be described below.
The container 205 can be implemented in a variety of different environments.
By bringing the store to the customer, the container 205 enables many new ways for merchants to connect with their consumers without disrupting the consumers' web activities. The end result is to connect the consumer directly with the merchant eliminating the intermediary and promoting a much more natural shopping experience.
According to an embodiment of the disclosure, an innovative new method for merchants to administer their virtual stores online is provided. To manage features with the container 205, an administrative feature may be provided via the admin server(s) 270 in what is referred to as an administration application. In an online administration model, merchants are typically required to have a fully featured computing device with persistent access to the World Wide Web. As an alternative to such a scenario and to enable on-the-go management, an embodiment of the disclosure provides merchants with a fully featured administration application—executable on mobile, handheld and smart devices—that is capable of creating and administering an entire virtual online store. In such embodiments, camera and video features may be utilized to capture digital assets for the container 205, whereas the mobile device's communication capabilities may be utilized to not only upload the digital assets, but also to issue commands and/or retrieve information for the management of an account that is used to create objects for the container 205.
The administration application for the mobile device is capable of running in both connected and disconnected modes. In a connected mode, the mobile administration application sends commands to the remote server instructing it to perform various actions related to store administration. Alternatively, in a disconnected mode, the mobile administration application performs all of the commands locally, on the installed device, with periodic synchronization to the remote server.
Below are non-limiting features of administration applications for the mobile device:
Given the above, in particular embodiments, a user may create objects for virally spreadable container(s) 205 directly from a mobile device. As a non-limiting example, a user may shoot a video from the mobile device, upload the video asset from the mobile device (e.g., using the wireless network described in
In particular embodiments, a traditional web interface for the administration application may largely be replicated to allow a mobile user the convenience of modifying and/or creating information for one's account on the go.
In various embodiments, the container 205 technology allows users to select products and services in context of their video or animation viewing experience in the confines of the display unit for the container 205. Upon product or service selection, a user is presented with details of the selected product or service without leaving the confines of the display unit or interrupting the animation or video viewing experience, as illustrated for example in
It is important to note that the container 205 retains all of the purchasing and advertising capabilities—substantially conducted in the same manner—when shared on social distribution channels, such as social networks or blogs. In particular configurations, the container 205 is fully capable to be distributed or virally syndicated upon any media that supports Adobe Flash™ and HTML5 technologies.
In addition to physical goods and services, the container 205 technology supports sale and redemption of digital goods, such as coupons and gift certificates. Digital products presented in the container 205 display units are available for purchase or as a reward for completing an action a merchant deems worthy of product redemption. Such actions may include purchase, submission of requested information, advertisement or video viewing or acknowledgement. Upon the sale of a digital product or as a result of the action deemed to be satisfactory to qualify a user for a digital product award, the digital product is available for redemption. A digital product can be redeemed using a variety of mechanisms, including, but not limited to: a) thanks for the purchase email; b) thanks for the purchase screen; c) end of play of a screen; or d) third party redemption web page.
In particular configurations, a “thanks for the purchase” email may constitute a digital mail delivered to the user upon performing a downloadable product redemption qualifying action. Digital mail provides instructions on how a downloadable product shall be redeemed. In other configurations, a “thanks for the purchase” screen is presented to the user upon performing a downloadable product redemption qualifying action. In such configurations, the aforementioned screen may optionally contain instruction on how to redeem downloadable product or how to download the product itself.
In other configurations, an “end of play screen” may be presented to the user upon completing an animation or video viewing experience until the end. In such configurations, the aforementioned screen may optionally contain instructions on how to redeem the downloadable product or how to download the product itself. In other configurations, a third party redemption webpage served by a third party provider to the user may be provided upon performing a downloadable product redemption qualifying action. The presented webpage may optionally contain instructions of how to redeem a downloadable product or how to download the product itself.
Various embodiments of the present disclosure also provide companion products and up sell products with intelligent Internet objects. The container 205 technology supports companion products and services as well as up sell products and services. Companion products and services are presented to the user at the time of the product selection or post product sale. Upon product or service selection, a user may be presented with details of the selected product or service, in addition to a matching mechanism. The matching mechanism either may be predefined or dynamically selected additional products or services that complement an original selection. The user is given a choice to perform an action using original product or service selection or proceed with a suggested product or service bundle. In the context of the container 205, an action is defined as a purchase, a charitable contribution, a submission of requested information, advertisement or video viewing or acknowledgement. An identical mechanism may be utilized during the post purchase process where, upon completion of the purchase, a user is presented with up sell products or services suggesting additional actions.
Any suitable algorithm may be utilized with either mechanisms based, for example, on common linkage between products and services. Alternatively, the algorithm may be based, for example, on a statistical analysis that looks at users and linked products to yield what linked products or services are most often purchased with a particular product or service or grouping of products or services. Yet other techniques will become apparent to one of ordinary skill in the art.
Various embodiments of the present disclosure provide a distributed shopping cart with intelligent Internet objects. The container 205 technology supports a distributed shopping cart (e.g., accessible via “add to cart” button 505 as illustrated in
As a brief recapitulation of the above and as an example, a user may be visiting a friend's Facebook™ wall and see a display of a container with something of interest. The particular container display may become associated with the user upon the user's interaction with the container using any suitable tracking mechanism. As a simple example, a user may log into a particular account directly within the display to associate the container and any items placed within a shopping cart with the user. The user may then visit another site or simply access a container display via an email. Upon the display being associated with the same user, the user may access the items previously placed within the cart and continue shopping, placing additional items within the cart. The above is a non-limiting example and is not intended to preclude other manners of accessing the distributed shopping cart.
Various embodiments of the present disclosure provide distributed retargeting of products with intelligent Internet objects. The container 205 supports distributed retargeting of products and services. Distributed retargeting of products and services allows merchants to display products or services that were viewed or similar to the products or services that were viewed by users that belong to a merchant or a group of merchants combined into the merchant network. Upon recognition of a user that has viewed one or several products or services in the container 205 or a merchant website belonging to the same merchant network, the user may be presented with the products or services that were viewed or similar to the products and services that were viewed during previous visits. Any suitable algorithm may be used for the presentment of distributed retargeting, including collaborative filtering and others. Such algorithms may avail from data from a group of merchants. Additionally, in the distributed retargeting, additional types of media may be shown with such media associated with the other products or services.
Various embodiments of the present disclosure provide dynamic configuration of intelligent internet objects. The container 205 technology supports dynamic configuration. The dynamic configuration allows the container 205 to determine the number of screens, screen fields, field validation, business rules and user specific characteristics based on the configuration file that is passed to the container 205 technology during the runtime or assembly time. The configuration file contains configuration metadata. Upon receipt of the configuration file, the container 205 determines what screens, containing what fields, requiring what validation should be presented to the user. Based on the user input, the container 205 interprets business rules passed to it using the configuration file, the logic and the flow of the screen execution. In addition to accepting metadata centric configuration files, the container 205 allows inclusion of third party dynamic flows. Such flows can be passed to the container 205 in the form of executable files during container 205 configuration or during runtime. Just like dynamic configuration files, third party dynamic flows contain screens, screen fields, field validation, business rules and user-specific characteristics. Unlike dynamic configuration files, third party dynamic flows may not require separate interpretation steps and can be executed natively inside of the web browser.
The process begins by the system receiving a request for the media content to be displayed at an endpoint at block 1505. For example, in block 1505, the system may receive the request as a click to play a video or may receive the request from a second endpoint where the media content has been viewed and shared to the first endpoint.
Thereafter, the system identifies information about an environment associated with the endpoint at block 1510. For example, in block 1510, the system may identify a type of a device associated with the endpoint, a website where the media content is to be displayed, and a network speed between the endpoint and the system. In other examples, the system may identify information about a location of a device associated with the endpoint.
The system then identifies a set of objects to send with the requested media content based on the information identified about the environment at block 1515. For example, in block 1515, the system may include objects and the media content in a container (e.g., the container 205 in
In some examples, the system may identify information about a user associated with the second endpoint and identify objects to send with the requested media content based on the information about the user. For example, higher quality media content may be sent where the network bandwidth between an endpoint and the system is high. In other examples, the system may identify rendering parameters associated with the type of the device or the website and include objects designed to generate the display of the media content in the set of objects to send based on the rendering parameters. In other examples, the system may identify a product to advertise with the media content, a language for text associated with the media content and/or a type of video to send as the media content for display based on information about the location of the device and include appropriate objects in the container. In yet other examples, the system may identify information about a status of the marketing campaign associated with the media content and objects based on the information about the status of the marketing campaign.
In a variety of configurations, analytics may be utilized to determine what to send to a user based on their environment and/or profile information about the user. For example, based on a geographic location or determined profile, a shirt advertisement may be sent as opposed to a hat advertisement (which may also be shown in the video) because the analytics are showing the shirt to be more likely to sell than the hat.
Thereafter, the system sends the set of objects including the media content for display at the endpoint in block 1520. For example, in block 1520, the system sends the container to the endpoint for the media content to be displayed and the electronic transaction opportunities to occur. As referenced above, the objects and media may be sent separately or together.
The process begins by receiving a request to render a container at an endpoint at block 1605. For example, in block 1605, the process may receive the request from a user requesting to view a video clip associated with the container. The process may also receive the request from a user sharing the container. The process then identifies a server supporting the container at block 1610. For example, in block 1610, the process may identify the server from the container. The server may be one or more of the server(s) 102 in
Thereafter, the process provides information about the environment at the endpoint at block 1615. For example, in block 1615, the process may provide the identifier of the container information about the endpoint (e.g., website, device type, IP address), information about the user sharing or requesting to view the video, cookies, shopping cart information, container tethering information and/or any other type of information that may be useful in selecting objects to include in the container.
The process then receives container objects and location of media content at block 1620. For example, in block 1620, the process receives the container objects from the configurator 285 having configured or otherwise selected the objects to include in the container. The location of the media content may be a server that the media player in the container is to stream or otherwise receive the media content. Thereafter, the process receives and displays media content from the location at block 1625. For example, in block 1625, the process may stream the media content inside a display unit for the container from a media server specified in the container.
The processor 1704 processes instructions for software that may be loaded into the memory 1706. The processor 1704 may be a number of processors, a multi-processor core or some other type of processor, depending on the particular implementation. Further, the processor 1704 may be implemented using a number of heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, the processor 1704 may be a symmetric multi-processor system containing multiple processors of the same type.
The memory 1706 and the persistent storage 1708 are examples of storage devices 1717. A storage device is any piece of hardware that is capable of storing information, such as, for example, without limitation; data, program code in functional form and/or other suitable information either on a temporary basis and/or a permanent basis. The memory 1706, in these examples, may be, for example, a random access memory or any other suitable volatile or non-volatile storage device. For example, the persistent storage 1708 may contain one or more components or devices. For example, the persistent storage 1708 may be a hard drive, a flash memory, an optical disk, a rewritable magnetic tape or some combination of the above. The media used by the persistent storage 1708 also may be removable. For example, a removable hard drive may be used for the persistent storage 1708.
The communications unit 1710 provides for communications with other data processing systems or devices. For example, the communications unit 1710 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. For example, the communications unit 1710 may include a network interface card. The communications unit 1710 may provide communications through the use of either or both physical and wireless communications links. The communications unit 1710 may also include a radio frequency (RF) transceiver enabling wireless network communication (e.g., WiFi, cellular data connection, etc.). The communications unit 1710 may also include a GPS transceiver enabling positional location information.
The input/output unit 1712 allows for input and output of data with other devices that may be connected to the data processing system 1700. For example, the input/output unit 1712 may provide a connection for user input through a keyboard, a mouse, a touch screen and/or some other suitable input device. Further, the input/output unit 1712 may send output to a printer. The input/output unit 1712 may also include or be connected to a camera, microphone, speaker, accelerometer and/or proximity sensor. The data processing system 1700 may utilize inputs and outputs from a camera, microphone, speaker, accelerometer and/or proximity sensors in accordance with various communication and data transfer principles of the present disclosure. The display 1714 provides a mechanism to display information to a user. For example, the display 1714 may be a touch screen.
Program code for an operating system, applications or other programs may be located in the storage devices 1717, which are in communication with the processor 1704 through the bus system 1702. In some embodiments, the program code is in a functional form on the persistent storage 1708. These instructions may be loaded into the memory 1706 for processing by the processor 1704. The processes of the different embodiments may be performed by the processor 1704 using computer implemented instructions, which may be located in the memory 1706. For example, the processor 1704 may perform processes for one or more of the modules and/or devices described above.
In some embodiments, various functions described above are implemented or supported by a computer program product that is formed from computer-readable program code and that is embodied in a computer-readable medium. Program code for the computer program product may be located in a functional form on a computer-readable storage device that is selectively removable and may be loaded onto or transferred to the data processing system 1700 for processing by the processor 1704. In some illustrative embodiments, the program code may be downloaded over a network to the persistent storage 1708 from another device or data processing system for use within the data processing system 1700. For instance, program code stored in a computer-readable storage medium in a server data processing system may be downloaded over a network from the server to the data processing system 1700. The data processing system providing program code may be a server computer, a client computer, or some other device capable of storing and transmitting program code.
As will be appreciated by one skilled in the art, aspects of the present disclosure may take the form of a computer program embodied in one or more computer-readable storage medium(s) having program code embodied thereon. A computer-readable storage medium may be, for example, without limitation, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), flash memory, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device or any suitable combination of the foregoing. The program code may also be loaded for execution by a processor to provide processes for implementing the functions or operations described in the present disclosure.
Although
Several embodiments of the disclosure may include logic contained within a medium. In the embodiment of
The functionality of the above description, once again may avail from any of the components described in
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.
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.
The present application is a continuation of U.S. patent application Ser. No. 13/598,443 filed Aug. 29, 2012 which is related to: U.S. Provisional Patent Application No. 61/528,635, filed Aug. 29, 2011; U.S. Provisional Patent Application No. 61/650,917, filed May 23, 2012; U.S. Provisional Patent Application No. 61/650,873, filed May 23, 2012; U.S. Provisional Patent Application No. 61/650,888, filed May 23, 2012; U.S. Provisional Patent Application No. 61/650,897, filed May 23, 2012; U.S. Provisional Patent Application No. 61/650,900, filed May 23, 2012; U.S. Provisional Patent Application No. 61/650,881, filed May 23, 2012 and U.S. Provisional Patent Application No. 61/662,765, filed Jun. 21, 2012. U.S. patent application Ser. No. 13/598,443 and Provisional Patent Application Nos. 61/528,635; 61/650,917; 61/650,873; 61/650,888; 61/650,897; 61/650,900; 61/650,881 and 61/662,765 are owned by the assignee of the present application and are hereby incorporated by reference into the present application as if fully set forth herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5715400 | Reimer et al. | Feb 1998 | A |
| 5774664 | Hidary et al. | Jun 1998 | A |
| 5778181 | Hidary et al. | Jul 1998 | A |
| 5903816 | Broadwin et al. | May 1999 | A |
| 5929849 | Kikinis | Jul 1999 | A |
| 6006257 | Slezak | Dec 1999 | A |
| 6009410 | LeMole et al. | Dec 1999 | A |
| 6014638 | Burge et al. | Jan 2000 | A |
| 6018768 | Ullman et al. | Jan 2000 | A |
| 6154771 | Rangan et al. | Nov 2000 | A |
| 6169573 | Sampath-Kumar et al. | Jan 2001 | B1 |
| 6188398 | Collins-Rector et al. | Feb 2001 | B1 |
| 6233682 | Fritsch | May 2001 | B1 |
| 6240555 | Shoff et al. | May 2001 | B1 |
| 6263505 | Walker et al. | Jul 2001 | B1 |
| 6275989 | Broadwin et al. | Aug 2001 | B1 |
| 6282713 | Kitsukawa et al. | Aug 2001 | B1 |
| 6321209 | Pasquali | Nov 2001 | B1 |
| 6330595 | Ullman et al. | Dec 2001 | B1 |
| 6357042 | Srinivasan et al. | Mar 2002 | B2 |
| 6536041 | Knudson et al. | Mar 2003 | B1 |
| 6553566 | Grant et al. | Apr 2003 | B1 |
| 6564380 | Murphy | May 2003 | B1 |
| 6573907 | Madrane | Jun 2003 | B1 |
| 6628307 | Fair | Sep 2003 | B1 |
| 6766528 | Kim et al. | Jul 2004 | B1 |
| 6857010 | Cuijpers et al. | Feb 2005 | B1 |
| 6910049 | Fenton et al. | Jun 2005 | B2 |
| 6912726 | Chen et al. | Jun 2005 | B1 |
| 6941575 | Allen | Sep 2005 | B2 |
| 6976028 | Fenton et al. | Dec 2005 | B2 |
| 6990498 | Fenton et al. | Jan 2006 | B2 |
| 7000242 | Haber | Feb 2006 | B1 |
| 7017173 | Armstrong et al. | Mar 2006 | B1 |
| 7072683 | King et al. | Jul 2006 | B2 |
| 7136853 | Kohda et al. | Nov 2006 | B1 |
| 7158676 | Rainsford | Jan 2007 | B1 |
| 7162263 | King et al. | Jan 2007 | B2 |
| 7168051 | Robinson et al. | Jan 2007 | B2 |
| 7188186 | Meyer et al. | Mar 2007 | B1 |
| 7207057 | Rowe | Apr 2007 | B1 |
| 7222163 | Girouard et al. | May 2007 | B1 |
| 7231651 | Pong | Jun 2007 | B2 |
| 7243139 | Ullman et al. | Jul 2007 | B2 |
| 7254622 | Nomura et al. | Aug 2007 | B2 |
| 7269837 | Redling et al. | Sep 2007 | B1 |
| 7331057 | Eldering et al. | Feb 2008 | B2 |
| 7353186 | Kobayashi | Apr 2008 | B2 |
| 7409437 | Ullman et al. | Aug 2008 | B2 |
| 7412406 | Rosenberg | Aug 2008 | B2 |
| 7432768 | Han et al. | Oct 2008 | B2 |
| 7444659 | Lemmons | Oct 2008 | B2 |
| 7464344 | Carmichael et al. | Dec 2008 | B1 |
| 7485397 | Eck et al. | Feb 2009 | B2 |
| 7487112 | Barnes, Jr. | Feb 2009 | B2 |
| 7509340 | Fenton et al. | Mar 2009 | B2 |
| 7539738 | Stuckman et al. | May 2009 | B2 |
| 7574381 | Lin-Hendel | Aug 2009 | B1 |
| 7593965 | Gabriel | Sep 2009 | B2 |
| 7613691 | Finch | Nov 2009 | B2 |
| 7614013 | Dollar et al. | Nov 2009 | B2 |
| 7624416 | Vandermolen et al. | Nov 2009 | B1 |
| 7631327 | Dempski et al. | Dec 2009 | B2 |
| 7661121 | Smith et al. | Feb 2010 | B2 |
| 7664678 | Haber | Feb 2010 | B1 |
| 7673017 | Kim et al. | Mar 2010 | B2 |
| 7691666 | Levy et al. | Apr 2010 | B2 |
| 7721307 | Hendricks et al. | May 2010 | B2 |
| 7725362 | Weathers, Jr. | May 2010 | B2 |
| 7739596 | Clarke-Martin et al. | Jun 2010 | B2 |
| 7747037 | Hein, III | Jun 2010 | B2 |
| 7750343 | Choi et al. | Jul 2010 | B2 |
| 7756758 | Johnson et al. | Jul 2010 | B2 |
| 7769827 | Girouard et al. | Aug 2010 | B2 |
| 7769830 | Stuckman et al. | Aug 2010 | B2 |
| 7773093 | Bates et al. | Aug 2010 | B2 |
| 7774161 | Tischer | Aug 2010 | B2 |
| 7774815 | Allen | Aug 2010 | B1 |
| 7796941 | Poltorak | Sep 2010 | B2 |
| 7800102 | Park et al. | Sep 2010 | B2 |
| 7804506 | Bates et al. | Sep 2010 | B2 |
| 7818763 | Sie et al. | Oct 2010 | B2 |
| 7870592 | Hudson et al. | Jan 2011 | B2 |
| 7885951 | Rothschild | Feb 2011 | B1 |
| 7899719 | Lin-Hendel | Mar 2011 | B2 |
| 7912753 | Struble | Mar 2011 | B2 |
| 7923722 | Ryu et al. | Apr 2011 | B2 |
| 7923772 | Mauder et al. | Apr 2011 | B2 |
| 7925973 | Allaire et al. | Apr 2011 | B2 |
| 7946492 | Rohs | May 2011 | B2 |
| 7975020 | Green et al. | Jul 2011 | B1 |
| 7975062 | Krikorian et al. | Jul 2011 | B2 |
| 7979877 | Huber et al. | Jul 2011 | B2 |
| 7982216 | Imai | Jul 2011 | B2 |
| 7987098 | Schifone | Jul 2011 | B2 |
| 7987483 | Des Jardins | Jul 2011 | B1 |
| 8001116 | Cope | Aug 2011 | B2 |
| 8001577 | Fries | Aug 2011 | B2 |
| 8006265 | Redling et al. | Aug 2011 | B2 |
| 8010408 | Rubinstein et al. | Aug 2011 | B2 |
| 8032421 | Ho et al. | Oct 2011 | B1 |
| 8055688 | Giblin | Nov 2011 | B2 |
| 8091103 | Cope | Jan 2012 | B2 |
| 8108257 | Sengamedu | Jan 2012 | B2 |
| 8117281 | Robinson et al. | Feb 2012 | B2 |
| 8122480 | Sholtis | Feb 2012 | B2 |
| 8132486 | Calvert | Mar 2012 | B1 |
| 8141112 | Cope et al. | Mar 2012 | B2 |
| 8181212 | Sigal | May 2012 | B2 |
| 8196162 | van de Klashorst | Jun 2012 | B2 |
| 8234218 | Robinson et al. | Jul 2012 | B2 |
| 8244830 | Robinson et al. | Aug 2012 | B2 |
| 8312486 | Briggs et al. | Nov 2012 | B1 |
| 8316450 | Robinson et al. | Nov 2012 | B2 |
| 8341152 | Bates | Dec 2012 | B1 |
| 8356077 | Robinson et al. | Jan 2013 | B2 |
| 8423467 | Johansson et al. | Apr 2013 | B1 |
| 8433611 | Lax et al. | Apr 2013 | B2 |
| 8438646 | Sidi | May 2013 | B2 |
| 8458053 | Buron et al. | Jun 2013 | B1 |
| 8468562 | Miller et al. | Jun 2013 | B2 |
| 8549555 | Briggs et al. | Oct 2013 | B2 |
| 8615474 | Avedissian et al. | Dec 2013 | B2 |
| 8635169 | Avedissian et al. | Jan 2014 | B2 |
| 8639621 | Ellis et al. | Jan 2014 | B1 |
| 8645214 | Hipolito et al. | Feb 2014 | B2 |
| 8645217 | Siegel et al. | Feb 2014 | B2 |
| 8645991 | McIntire et al. | Feb 2014 | B2 |
| 8655146 | Bennett et al. | Feb 2014 | B2 |
| 8682809 | Avedissian et al. | Mar 2014 | B2 |
| 8707185 | Robinson et al. | Apr 2014 | B2 |
| 8708223 | Gates et al. | Apr 2014 | B2 |
| 8725826 | Robinson et al. | May 2014 | B2 |
| 8752083 | Geer, III et al. | Jun 2014 | B2 |
| 8769016 | Jakobson | Jul 2014 | B2 |
| 8769053 | Spitz | Jul 2014 | B2 |
| 8769584 | Neumeier et al. | Jul 2014 | B2 |
| 8782690 | Briggs et al. | Jul 2014 | B2 |
| 8813132 | Andrews, II et al. | Aug 2014 | B2 |
| 8818941 | Kiilerich | Aug 2014 | B2 |
| 8893173 | Briggs et al. | Nov 2014 | B2 |
| 20020059196 | I'Anson et al. | May 2002 | A1 |
| 20020062481 | Slaney et al. | May 2002 | A1 |
| 20020075332 | Geilfuss, Jr. et al. | Jun 2002 | A1 |
| 20020083447 | Heron et al. | Jun 2002 | A1 |
| 20020083469 | Jeannin et al. | Jun 2002 | A1 |
| 20020126990 | Rasmussen et al. | Sep 2002 | A1 |
| 20020199181 | Allen | Dec 2002 | A1 |
| 20030023490 | Lenyon et al. | Jan 2003 | A1 |
| 20030028873 | Lemmons | Feb 2003 | A1 |
| 20030055723 | English | Mar 2003 | A1 |
| 20030135563 | Bodin et al. | Jul 2003 | A1 |
| 20030149983 | Markel | Aug 2003 | A1 |
| 20030163832 | Tsuria et al. | Aug 2003 | A1 |
| 20030228615 | Rossi et al. | Dec 2003 | A1 |
| 20030231851 | Rantala et al. | Dec 2003 | A1 |
| 20040021684 | Millner | Feb 2004 | A1 |
| 20050022226 | Ackley et al. | Jan 2005 | A1 |
| 20050033656 | Wang et al. | Feb 2005 | A1 |
| 20050076372 | Moore et al. | Apr 2005 | A1 |
| 20050091107 | Blum | Apr 2005 | A1 |
| 20060009243 | Dahan et al. | Jan 2006 | A1 |
| 20060089843 | Flather | Apr 2006 | A1 |
| 20060122895 | Abraham et al. | Jun 2006 | A1 |
| 20060136305 | Fitzsimmons et al. | Jun 2006 | A1 |
| 20060202191 | Gerlach et al. | Sep 2006 | A1 |
| 20060242016 | Chenard | Oct 2006 | A1 |
| 20060256133 | Rosenberg | Nov 2006 | A1 |
| 20060265657 | Gilley | Nov 2006 | A1 |
| 20060276266 | Sullivan | Dec 2006 | A1 |
| 20070030080 | Han et al. | Feb 2007 | A1 |
| 20070087489 | Park et al. | Apr 2007 | A1 |
| 20070106646 | Stern et al. | May 2007 | A1 |
| 20070150360 | Getz | Jun 2007 | A1 |
| 20070157228 | Bayer et al. | Jul 2007 | A1 |
| 20070180461 | Hilton | Aug 2007 | A1 |
| 20070204308 | Nicholas et al. | Aug 2007 | A1 |
| 20070239546 | Blum et al. | Oct 2007 | A1 |
| 20070241327 | Kim et al. | Oct 2007 | A1 |
| 20070250901 | McIntire et al. | Oct 2007 | A1 |
| 20070266399 | Sidi | Nov 2007 | A1 |
| 20070271149 | Siegel et al. | Nov 2007 | A1 |
| 20070276721 | Jackson | Nov 2007 | A1 |
| 20070288518 | Crigler et al. | Dec 2007 | A1 |
| 20070300263 | Barton et al. | Dec 2007 | A1 |
| 20070300280 | Turner et al. | Dec 2007 | A1 |
| 20080005999 | Pervan | Jan 2008 | A1 |
| 20080012010 | Myung-Seok et al. | Jan 2008 | A1 |
| 20080066099 | Brodersen et al. | Mar 2008 | A1 |
| 20080066107 | Moonka et al. | Mar 2008 | A1 |
| 20080097843 | Menon et al. | Apr 2008 | A1 |
| 20080098425 | Welch | Apr 2008 | A1 |
| 20080109306 | Maigret et al. | May 2008 | A1 |
| 20080109844 | Baldeschwieler et al. | May 2008 | A1 |
| 20080126191 | Schiavi | May 2008 | A1 |
| 20080126226 | Popkiewicz et al. | May 2008 | A1 |
| 20080126949 | Sharma | May 2008 | A1 |
| 20080148283 | Allen et al. | Jun 2008 | A1 |
| 20080149921 | Choi et al. | Jun 2008 | A1 |
| 20080162343 | Bedier | Jul 2008 | A1 |
| 20080177627 | Cefail | Jul 2008 | A1 |
| 20080177630 | Maghfourian et al. | Jul 2008 | A1 |
| 20080235085 | Kovinsky et al. | Sep 2008 | A1 |
| 20080250445 | Zigmond et al. | Oct 2008 | A1 |
| 20080255934 | Leventhal et al. | Oct 2008 | A1 |
| 20080276266 | Huchital et al. | Nov 2008 | A1 |
| 20080281685 | Jaffe et al. | Nov 2008 | A1 |
| 20080294694 | Maghfourian et al. | Nov 2008 | A1 |
| 20080296568 | Ryu et al. | Dec 2008 | A1 |
| 20080306999 | Finger et al. | Dec 2008 | A1 |
| 20080307310 | Segal et al. | Dec 2008 | A1 |
| 20080319852 | Gardner et al. | Dec 2008 | A1 |
| 20080319856 | Zito et al. | Dec 2008 | A1 |
| 20090013347 | Ahanger et al. | Jan 2009 | A1 |
| 20090018904 | Shipman et al. | Jan 2009 | A1 |
| 20090031382 | Cope | Jan 2009 | A1 |
| 20090032809 | Kim et al. | Feb 2009 | A1 |
| 20090043674 | Minsky et al. | Feb 2009 | A1 |
| 20090077598 | Watson et al. | Mar 2009 | A1 |
| 20090083815 | McMaster et al. | Mar 2009 | A1 |
| 20090094339 | Allen et al. | Apr 2009 | A1 |
| 20090119169 | Chandratillake et al. | May 2009 | A1 |
| 20090132349 | Berkley et al. | May 2009 | A1 |
| 20090157500 | Ames et al. | Jun 2009 | A1 |
| 20090158322 | Cope et al. | Jun 2009 | A1 |
| 20090199230 | Kumar et al. | Aug 2009 | A1 |
| 20090210790 | Thomas | Aug 2009 | A1 |
| 20090248546 | Norris et al. | Oct 2009 | A1 |
| 20090259563 | Ruhnke et al. | Oct 2009 | A1 |
| 20090265255 | Jackson et al. | Oct 2009 | A1 |
| 20090276805 | Andrews, II et al. | Nov 2009 | A1 |
| 20090320073 | Reisman | Dec 2009 | A1 |
| 20100030578 | Siddique et al. | Feb 2010 | A1 |
| 20100114983 | Robert et al. | May 2010 | A1 |
| 20100131385 | Harrang et al. | May 2010 | A1 |
| 20100145795 | Haber et al. | Jun 2010 | A1 |
| 20100153831 | Beaton | Jun 2010 | A1 |
| 20100223107 | Kim et al. | Sep 2010 | A1 |
| 20100247061 | Bennett et al. | Sep 2010 | A1 |
| 20100279766 | Pliska et al. | Nov 2010 | A1 |
| 20100283827 | Bustamente | Nov 2010 | A1 |
| 20100287580 | Harding et al. | Nov 2010 | A1 |
| 20100299616 | Chen et al. | Nov 2010 | A1 |
| 20100306402 | Russell et al. | Dec 2010 | A1 |
| 20100306805 | Neumeier et al. | Dec 2010 | A1 |
| 20100332329 | Roberts et al. | Dec 2010 | A1 |
| 20110004517 | Soto et al. | Jan 2011 | A1 |
| 20110052144 | Abbas et al. | Mar 2011 | A1 |
| 20110071865 | Leeds et al. | Mar 2011 | A1 |
| 20110133176 | Lee et al. | Jun 2011 | A1 |
| 20110173300 | Levy et al. | Jul 2011 | A1 |
| 20110191809 | Briggs et al. | Aug 2011 | A1 |
| 20110231260 | Price | Sep 2011 | A1 |
| 20110238755 | Khan et al. | Sep 2011 | A1 |
| 20110251897 | Litvack et al. | Oct 2011 | A1 |
| 20110307397 | Benmbarek | Dec 2011 | A1 |
| 20110321096 | Landow | Dec 2011 | A1 |
| 20120030704 | Schiller et al. | Feb 2012 | A1 |
| 20120036048 | Robb et al. | Feb 2012 | A1 |
| 20120079021 | Roman et al. | Mar 2012 | A1 |
| 20120158511 | Lucero et al. | Jun 2012 | A1 |
| 20120185355 | Kilroy | Jul 2012 | A1 |
| 20120201521 | Frojdh et al. | Aug 2012 | A1 |
| 20120222064 | Geer, III et al. | Aug 2012 | A1 |
| 20120227060 | Allen et al. | Sep 2012 | A1 |
| 20120227074 | Hill et al. | Sep 2012 | A1 |
| 20120284607 | Jones | Nov 2012 | A1 |
| 20120296738 | Leeder | Nov 2012 | A1 |
| 20120296739 | Cassidy et al. | Nov 2012 | A1 |
| 20120296782 | Tsai et al. | Nov 2012 | A1 |
| 20120304065 | Cai | Nov 2012 | A1 |
| 20130014137 | Bhatia et al. | Jan 2013 | A1 |
| 20130014155 | Clarke et al. | Jan 2013 | A1 |
| 20130054757 | Spitz | Feb 2013 | A1 |
| 20130110608 | Cassidy et al. | May 2013 | A1 |
| 20130117131 | Robinson et al. | May 2013 | A1 |
| 20130117409 | Yang | May 2013 | A1 |
| 20130144903 | Andrews, II et al. | Jun 2013 | A1 |
| 20130151352 | Tsai et al. | Jun 2013 | A1 |
| 20130152123 | Briggs et al. | Jun 2013 | A1 |
| 20130162655 | Mueller | Jun 2013 | A1 |
| 20130166382 | Cassidy et al. | Jun 2013 | A1 |
| 20130183021 | Osman | Jul 2013 | A1 |
| 20130211891 | Daniel et al. | Aug 2013 | A1 |
| 20130212611 | Van Aacken et al. | Aug 2013 | A1 |
| 20130215116 | Siddique et al. | Aug 2013 | A1 |
| 20130218964 | Jakobson | Aug 2013 | A1 |
| 20130228615 | Gates et al. | Sep 2013 | A1 |
| 20130254018 | Rao | Sep 2013 | A1 |
| 20130290550 | Bangalore et al. | Oct 2013 | A1 |
| 20140019860 | Sathish et al. | Jan 2014 | A1 |
| 20140032366 | Spitz et al. | Jan 2014 | A1 |
| 20140052576 | Zelenka et al. | Feb 2014 | A1 |
| 20140095330 | Briggs et al. | Apr 2014 | A1 |
| 20140181208 | Robinson et al. | Jun 2014 | A1 |
| 20140208235 | Robinson et al. | Jul 2014 | A1 |
| 20140250211 | Spitz et al. | Sep 2014 | A1 |
| 20140254942 | Liu et al. | Sep 2014 | A1 |
| 20140282700 | Briggs et al. | Sep 2014 | A1 |
| 20140359671 | Andrews, II et al. | Dec 2014 | A1 |
| 20150039468 | Spitz et al. | Feb 2015 | A1 |
| 20150073919 | Spitz et al. | Mar 2015 | A1 |
| 20150074710 | Spitz et al. | Mar 2015 | A1 |
| 20150074711 | Spitz et al. | Mar 2015 | A1 |
| 20150092111 | Spitz et al. | Apr 2015 | A1 |
| 20150095455 | Spitz et al. | Apr 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 102782608 | Nov 2012 | CN |
| 100824197 | Apr 2008 | KR |
| WO 0169364 | Sep 2001 | WO |
| WO 0191869 | Dec 2001 | WO |
| WO 2005036875 | Apr 2005 | WO |
| WO 2005039131 | Apr 2005 | WO |
| WO 2008016634 | Feb 2008 | WO |
| WO 2009012580 | Jan 2009 | WO |
| WO 2011149491 | Dec 2011 | WO |
| WO 2013033239 | Mar 2013 | WO |
| WO 2013192557 | Dec 2013 | WO |
| WO 2015013117 | Jan 2015 | WO |
| WO 2015038795 | Mar 2015 | WO |
| WO 2015038798 | Mar 2015 | WO |
| WO 2015038802 | Mar 2015 | WO |
| WO 2015048375 | Apr 2015 | WO |
| WO 2015048377 | Apr 2015 | WO |
| WO 2015054644 | Apr 2015 | WO |
| WO 2015054644 | Apr 2015 | WO |
| Entry |
|---|
| Office Action dated Aug. 27, 2014 in connection with U.S. Appl. No. 14/079,385. |
| Office Action dated Aug. 27, 2014 in connection with U.S. Appl. No. 12/787,505. |
| Office Action dated Aug. 20, 2014 in connection with U.S. Appl. No. 13/923,089. |
| Office Action dated Jul. 9, 2014 in connection with U.S. Appl. No. 13/753,384. |
| International Search Report dated Nov. 24, 2014 in connection with International Application No. PCT/US14/55233; 2 pages. |
| Written Opinion of International Searching Authority dated Nov. 24, 2014 in connection with International Application No. PCT/US14/55233; 3 pages. |
| International Search Report dated Dec. 15, 2014 in connection with International Application No. PCT/US14/57595; 2 pages. |
| Written Opinion of International Searching Authority dated Dec. 15, 2014 in connection with International Application No. PCT/US14/57595; 3 pages. |
| International Search Report dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55226; 2 pages. |
| Written Opinion of International Searching Authority dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55226; 4 pages. |
| International Search Report dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55229; 2 pages. |
| Written Opinion of International Searching Authority dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55229; 4 pages. |
| Non-Final Office Action dated Oct. 2, 2014 in connection with U.S. Appl. No. 12/434,569; 18 pages. |
| Non-Final Office Action dated Dec. 18, 2014 in connection with U.S. Appl. No. 12/484,047; 8 pages. |
| Non-Final Office Action dated Dec. 19, 2014 in connection with U.S. Appl. No. 14/484,065; 8 pages. |
| Non-Final Office Action dated Dec. 26, 2015 in connection with U.S. Appl. No. 14/484,225; 8 pages. |
| Non-Final Office Action dated Jan. 6, 2015 in connection with U.S. Appl. No. 14/512,204; 18 pages. |
| International Search Report dated Jan. 9, 2015 in connection with International Application No. PCT/US14/57597; 2 pages. |
| Written Opinion of International Searching Authority dated Jan. 9, 2015 in connection with International Application No. PCT/US14/57597; 4 pages. |
| International Search Report dated Jan. 26, 2015 in connection with International Application No. PCT/US2014/060150; 2 pages. |
| Written Opinion of International Searching Authority dated Jan. 26, 2015 in connection with International Application No. PCT/US2014/060150; 4 pages. |
| Non-Final Office Action dated Jan. 9, 2015 in connection with U.S. Appl. No. 14/292,423; 14 pages. |
| Kongwah Wan, et al., “Advertising Insertion in Sports Webcasts”, 2007 IEEE, p. 78-82. |
| Miguel Helft, “Google Aims to Make YouTube Profitable With Ads”, The New York Times, Aug. 22, 2007, 3 pages. |
| Chris Tomlinson, “Google tries to relive past glories by making YouTube pay for itself”, Birmingham Post, Sep. 4, 2007, 3 pages. |
| John Skidgel, “Producing Flash CS3 Video, Techniques for Video Pros and Web Designers”, 2007, 9 pages. |
| Jan Krikke, “Streaming Video Transforms the Media Industry”, IEEE, Jul./Aug. 2004, p. 6-12. |
| Tao Mei, et al., “VideoSense—Towards Effective Online Video Advertising”, Sep. 23-28, 2007, p. 1075-1084. |
| Dr. Harry van Vliet, “Where Television and Internet meet . . . New experiences for rich media”, Jan. 2002, 35 pages. |
| “IAB Announces Advertising Creative Guidelines for Online Broadband Video Commercials”, Nov. 29, 2005, 4 pages. |
| “Digital Video In-Stream Ad Format Guidelines and Best Practices”, Interactive Advertising Bureau, May 2008, 17 pages. |
| “Broadband Ad Creative Guidelines”, Dec. 31, 2006, 3 pages. |
| Rich Media Guidelines: Fall 2004, Dec. 31, 2006, 3 pages. |
| “About Rich Media Guidelines Compliance: In-Page Units”, Jan. 7, 2007, 2 pages. |
| “About Rich Media Guidelines Compliance: Over-the-Page Units”, Jan. 7, 2007, 2 pages. |
| “Digital Video Ad Serving Template (VAST), Version 2.0”, iab., Nov. 2009, 18 pages. (Redlined). |
| “Digital Video Ad Serving Template (VAST), Version 2.0”, iab., Nov. 2009, 16 pages. |
| “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. |
| “DoubleClick Debuts Video Ad-Serving Solution”, Nov. 6, 2006, 2 pages. |
| Liz Gannes, “YouTube's New Inline Ads: Screenshots”, May 11, 2007, 7 pages. |
| “Final Broadband Ad Creative Guidelines”, Interactive Advertising Bureau, Standards & Guidelines, 4 pages. |
| 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. |
| “Content distributors can shopping-enable video content”, www.web.archive.org, Apr. 27, 2007, 1 page. |
| Dan Kaplan, “Delivery Agent lets you buy products in your favorite TV shows”, www.web.archive.org, May 4, 2007, 4 pages. |
| “Shopisodes Enable You to Dress Like Your Favorite TV Character”, www.web.archive.org, Oct. 26, 2007, 1 page. |
| Jesse Liebman, “Reality TV That's Social, Bravo!”, www.web.archive.org, Dec. 22, 2008, 6 pages. |
| 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. |
| “Akamai for Media & Entertainment”, Akamai Technologies, Inc., 2007, 38 pages. |
| “ebd Web Video Player, Increase Online Video Ad Monetization”, www.ebdsoft.tv, 2010, 2 pages. |
| Written Opinion of International Searching Authority dated Nov. 14, 2012 in connection with International Patent Application No. PCT/US2012/52897, 4 pages. |
| International Search Report dated Nov. 14, 2012 in connection with International Patent Application No. PCT/US2012/52897, 3 pages. |
| Office Action dated Apr. 10, 2014 in connection with U.S. Appl. No. 14/042,477. |
| Office Action dated Apr. 11, 2014 in connection with U.S. Appl. No. 14/091,219. |
| Non-Final Office Action dated Oct. 3, 2011 in connection with U.S. Appl. No. 12/363,713; 9 pages. |
| Non-Final Office Action dated May 4, 2012 in connection with U.S. Appl. No. 12/434,596; 7 pages. |
| Final Office Action dated Jun. 13, 2012 in connection with U.S. Appl. No. 12/363,713; 13 pages. |
| Non-Final Office Action dated Mar. 15, 2013 in connection with U.S. Appl. No. 12/434,569; 9 pages. |
| Non-Final Office Action dated May 17, 2013 in connection with U.S. Appl. No. 13/753,384; 10 pages. |
| Final Office Action dated Jul. 18, 2013 in connection with U.S. Appl. No. 12/434,569; 9 pages. |
| Final Office Action dated Oct. 25, 2013 in connection with U.S. Appl. No. 13/753,384; 15 pages. |
| Non-Final Office Action dated Nov. 19, 2013 in connection with U.S. Appl. No. 12/434,569; 12 pages. |
| Non-Final Office Action dated Dec. 20, 2013 in connection with U.S. Appl. No. 13/753,384; 11 pages. |
| Final Office Action dated Mar. 20, 2014 in connection with U.S. Appl. No. 12/434,569; 11 pages. |
| Final Office Action dated Jul. 9, 2014 in connection with U.S. Appl. No. 13/753,384; 10 pages. |
| Final Office Action dated Jul. 21, 2014 in connection with U.S. Appl. No. 14/091,219; 12 pages. |
| Non-Final Office Action dated Feb. 24, 2015 in connection with U.S. Appl. No. 14/497,686; 13 pages. |
| Non-Final Office Action dated Mar. 3, 2015 in connection with U.S. Appl. No. 14/079,385; 13 pages. |
| Non-Final Office Action dated Mar. 27, 2015 in connection with U.S. Appl. No. 14/498,800; 19 pages. |
| Final Office Action dated May 18, 2015 in connection with U.S. Appl. No. 14/484,047; 10 pages. |
| Final Office Action dated May 21, 2015 in connection with U.S. Appl. No. 14/484,225; 13 pages. |
| Final Office Action dated Jul. 1, 2015 in connection with U.S. Appl. No. 14/079,385; 13 pages. |
| Non-Final Office Action dated Jul. 16, 2015 in connection with U.S. Appl. No. 12/787,505; 15 pages. |
| Final Office Action dated Jul. 17, 2015 in connection with U.S. Appl. No. 14/484,065; 13 pages. |
| “Digital Video In-Stream Ad Format Guidelines and Best Practices”; Interactive Advertising Bureau; May 2008; 17 pages. |
| Reid, et al,: “An Analysis of Anonymity in the Bitcoin System”; http://arxiv.org/pdf/1107.4524.pdf; May 7, 2012; 29 pages. |
| Notification dated Feb. 16, 2015 in connection with Russian Application No. 2012105917/08 (009063); 7 pages. |
| Office Action for U.S. Appl. No. 12/787,505, mailed Mar. 1, 2013, 10 pages. |
| Office Action for U.S. Appl. No. 12/434,569, mailed Oct. 25, 2012, 9 pages. |
| Office Action for Australian Application No. 2012302021, dated Oct. 22, 2015, 3 pages. |
| Notice of Acceptance for Australian Application No. 2012302021, dated May 4, 2016, 2 pages. |
| First Office Action for Chinese Application No. 201280053145.7, mailed Mar. 1, 2016, 3 pages. |
| Supplementary European Search Report for European Application No. 12828677.0, mailed Sep. 28, 2015, 7 pages. |
| Office Action for Russian Application No. 2014112353, mailed Feb. 18, 2016, 2 pages. |
| Office Action for Canadian Application No. 2,877,567, dated Feb. 29, 2016, 5 pages. |
| Supplementary European Search Report for European Application No. 13806161.9, mailed Jan. 28, 2016, 5 pages. |
| Office Action for U.S. Appl. No. 13/923,089, mailed Mar. 22, 2016, 11 pages. |
| Office Action for U.S. Appl. No. 13/923,089, mailed Dec. 2, 2014, 5 pages. |
| Office Action for U.S. Appl. No. 14/512,204, mailed Dec. 4, 2015, 20 pages. |
| Office Action for U.S. Appl. No. 14/512,204, mailed Jul. 30, 2015, 21 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2014/057597, mailed Jan. 9, 2015, 6 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2015/018140, mailed Jun. 3, 2015, 9 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2015/019979, mailed Jul. 30, 2015, 10 pages. |
| 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. |
| MediaTomb, MediaTomb Scripting [online], Retrieved on Oct. 11, 2015, URL: http://mediatomb.cc/pages/scripting, 24 pages. |
| Morin, J-H et al., “HyperNews: a commercial electronic newspaper,” pp. 147-163 (Nov. 8, 2004). |
| Office Action for Mexican Patent Application No. MX/a/2014/002490 mailed Jun. 10, 2016 (machine translation). |
| Office Action for Japanese Patent Application No. 2014-528557 mailed Jul. 26, 2016. |
| Number | Date | Country | |
|---|---|---|---|
| 20140250211 A1 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61528635 | Aug 2011 | US | |
| 61650917 | May 2012 | US | |
| 61650873 | May 2012 | US | |
| 61650888 | May 2012 | US | |
| 61650897 | May 2012 | US | |
| 61650900 | May 2012 | US | |
| 61650881 | May 2012 | US | |
| 61662765 | Jun 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13598443 | Aug 2012 | US |
| Child | 14280235 | US |
