Patent Grant
10911794
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The present disclosure relates generally to the field of content data delivery over a network. More particularly, the present disclosure is related in one exemplary aspect to apparatus and methods for secondary content (e.g., advertising, promotions, etc.) management and provision within a managed content distribution network such as a cable, satellite, or hybrid fiber/copper (HFCu) distribution network.
In the context of network services, it is often highly desirable to provide users or subscribers of the network with ready and instant access to a variety of different types of content (e.g., linear or broadcast content, video-on-demand (VOD), “start-over”, streaming media, etc.), accessible at different locations, and on different platforms (e.g., via set-top box, smart-TV, tablet or smartphone, etc.). In many cases, it is also desirable to provide the same users with “secondary” content (such as e.g., advertisements, promotions or “info-mercials”, related shorts, telescoping information/advertisements, hyperlinks, etc.). The secondary content may be directly or indirectly related to the “primary” content which the user selected in the first place (such as via a common theme or context, common persons of interest, common demographic factors, etc.), or can be totally unrelated.
Delivery of secondary content may comprise a major source of revenue for commercial television or movie distributors, and for the network operator. For example, where the secondary content comprises advertisements, it may be a main source of income for national television broadcasters and their local over-the-air affiliates. Cable, satellite, HFCu, and other content distribution networks, as well as Internet content providers, also derive income from the sale of advertising time and insertion opportunities (and “impressions” associated therewith).
Moreover, an advertiser may seek to maximize the return on their advertising investment by targeting specific users or groups of users that are likely to be most receptive to the commercial message embodied in the advertisements. The aforementioned selective “targeting” and delivery of content to e.g., subscribers in a cable or other MSO-based network is generally well known in the prior art. For example, it may be desirable to include certain types of advertising at specific demographic or geographic segments of an MSO's subscriber base. One way of targeting viewers involves selecting advertisements based on a geographical region in which the advertisement is to be delivered; i.e., a so-called “advertisement zone”. In other words, it is advantageous to provide certain advertising content to viewers in one local or regional area which is different than that provided to the viewers in a different local or regional area.
For example, the advertisements may be limited by the geographic area in which a business operates. Hence, it typically only makes financial sense for an advertisement for that business to be provided in geographical areas where the business is operated or provides services. Similar logic applies to the demographic, psychographic, and other planes; e.g., an advertisement for a super-high end sports car would likely be wasted when delivered to lower- or middle-class households or subscribers (which may or may not be correlated to geography), as would an advertisement for a feminine product delivered to a predominantly male audience. Additionally, the context of the primary content may not be compatible with particular types/themes of secondary content (e.g., a VOD movie having a non-violent theme might not mesh optimally with advertisements for UFC sporting or boxing events, regardless of demographics or geography).
One technique for advertising comprises use of so-called “audience bundles”. Typically, such audience bundles are built to reach a certain demographic group. Audience bundles are useful when a client (e.g., advertiser) has a defined demographic or other target, and wants assurance that their audience is being reached with a certain level of frequency.
One problem commonly encountered in the foregoing scenarios relates to delivery of particularly relevant content to particular users, and at particular times or relative chronological reference points. Typical prior art linear advertising delivery approaches (including the aforementioned “bundles”) typically have a very low degree of granularity in terms of the target audience; i.e., they may have some degree of applicability to some of the people watching the advertisement, but more often than not have little or no applicability to a majority of users watching the advertisement, and hence in effect are largely wasted on such viewers. Such low “applicability density” has obvious drawbacks, including lack of efficacy at reaching desired subsets of subscribers, unnecessary network resource consumption, and user frustration (at having to be exposed to advertisements in which they have no interest).
One salient reason for the foregoing lack of applicability of advertising is the inability to particularly target it to one individual (or a constrained subset of individuals). Given so many geographically and demographically diverse subscribers within a typical MSO's subscriber pool, even broadly watched advertisements (e.g., during a contentious Presidential debate or the NFL's Super Bowl) may really have applicability to only a relatively small number of subscribers, despite being seen by tens of millions of people. Like snowflakes, every subscriber/household is ostensibly different in some way, and hence in theory the optimal degree of penetration for advertising is via advertisements which are uniquely targeted (or at least their applicability confirmed) for each user.
Yet determining not only (i) unique attributes or prospective interests of a given user, and (ii) insertion opportunities when in fact that user is watching and is engaged (i.e., ostensibly paying attention) is extremely challenging at very least. One could conceivably flood delivery channels (e.g., in-band QAMs) with a plethora of advertising applicable to any number of different demographics/psychographics, such that something at least partly relevant to most users was always present, but such approach is both horribly inefficient from a bandwidth/network resource conservation perspective, and still suffers from the disability of how one would identify and steer a given user to something at least generally relevant to them which was then being delivered over the network.
Moreover, sometimes the best efficacy of an advertisement is when it is also contextually relevant; e.g., relates to subject matter the particular subscriber is watching when the advertisement is presented, and/or relates to a present geographic, psychographic, or other context then-relevant to the subscriber (e.g., when the subscriber is in Paris on vacation, or has recently returned therefrom, advertisements in some way contextually related to France or French culture may be particularly interesting to that subscriber).
Prior art Internet “banner” ads are one technique for attempting to divine a user's interest or context; i.e., by evaluating historical visits or clicks of the user on certain topical advertisements or websites. However, such approaches are fraught with potential issues, and largely inapplicable to the aforementioned MSO subscriber or other on-demand user context for a variety of reasons, including for instance: (i) the user may not interact with any links or websites from which useful information can be gleaned (e.g., they may simply tune to a given MSO channel without other interaction); (ii) the user may have merely inadvertently selected a given link or site, such as by a small finger placement error on their tablet or smartphone capacitive touchscreen; and (iii) the user may merely be expressing “morbid curiosity” as it were for something they find offensive or actually dislike. Hence, such approaches have little if any power in making objective assessment of a subscriber's demographic or psychographic profile. Rather, fact-based data relating to, inter alia, longer term decisions or activities of the user such as buying or refinancing a house, buying or leasing a car, traveling to certain locations, purchasing certain items, dining out at certain restaurants, investing in certain investment vehicles, subscribing to certain services or packages (including those of the MSO), etc. are often far more telling and accurate depictions of a given subscriber (and/or household) than that obtained from any anecdotal “click-based” sources.
Yet further, the broad variety of different delivery paradigms and target platforms further complicates targeting of secondary content. As indicated above, the typical MSO network includes both linear (e.g., broadcast, and non-repeatable) content, as well as non-linear content such as streaming IP-based content, VoD, cDVR, start-over, and the like, each of which raise their own particular insertion opportunity and delivery issues. For example, a linear broadcast schedule may be known well in advance of actual broadcast, whereas a stream-based on-demand delivery modality (e.g., VoD, or web streaming to a user portable device over the MSO's web portal or the like) may be completely spurious, and may stop and start again unpredictably, such as when the user is interrupted or wants to watch the remainder of a program at a later time.
Similarly, the subscriber's context using one type of delivery mode versus another may vary; e.g., in the foregoing Paris example, the user may only have online streaming available to them via an Internet connection when in Paris, whereas both online streaming and other modalities (e.g., in-band broadcast delivery via QAM to their digital set top box (DSTB), as well as VoD, start-over, etc.) may be available when they are home.
Based on the foregoing, there is a salient need for improved methods and apparatus for delivering targeted secondary content within a content distribution network. Such improved apparatus and methods would ideally, in exemplary implementations, enable delivery of geographically, demographically, and/or psychographically relevant secondary content to particular users or subsets of users, and would be based at least partly on some verifiable data or profile of the user(s), and would also be implemented without consuming disproportionate amounts of network resources. Such improved method and apparatus would also ideally be adaptable or able to delivery over different content distribution paradigms, including both linear and non-linear modalities.
The present disclosure addresses the foregoing needs by disclosing, inter alia, apparatus and methods for secondary content selection and insertion within a content distribution network infrastructure.
In one aspect of the disclosure, a computerized method of delivering secondary content in a content distribution network is disclosed. In one embodiment, the method includes: identifying one or more secondary content elements applicable to a target population of users of the content distribution network; identifying one or more insertion opportunities within programming consumed by the target population; causing delivery of the one or more secondary content elements at one or more of the identified insertion opportunities via selective switching; and causing one or more receiving devices of the target population to access the selectively switched one or more secondary content elements for at least a period of time.
In one variant, the selective switching comprises switching the one or more secondary content elements into delivery via a switching apparatus disposed at a non-central distribution node of the network, the switching into delivery occurring substantially contemporaneous with a start of the identified one or more insertion opportunities. The switching apparatus disposed at a non-central distribution node of the network comprises for example an edge switch of a switched digital video (SDV) delivery architecture.
In another variant, the target population comprises an individual subscriber or household of the network, and the identifying one or more secondary content elements applicable to the target population includes: accessing at least a network-side repository of data for data relating to attributes of the individual or subscriber; and utilizing at least the accessed data relating to attributes to correlate the attributes to corresponding aspects of the one or more secondary content elements.
In a further variant, the target population comprises an individual subscriber or household of the network, and the identifying one or more insertion opportunities within programming consumed by the target population comprises receiving from an application computer program or middleware component operative to run on a receiving device of the individual subscriber or household a communication indicating the one or more insertion opportunities within the consumed programming.
In one implementation, the causing one or more receiving devices of the target population to access the selectively switched one or more secondary content elements for at least a period of time comprises transmitting a communication to respective software processes operative on the one or more receiving devices, the transmitted communication causing the respective software processes to instigate a tune, at a prescribed time, from a current QAM channel to another QAM channel, the another QAM channel carrying the one or more secondary content elements.
In a second aspect of the disclosure, a computerized method of operating a content distribution network is disclosed. In one embodiment, the method includes: identifying one or more secondary content elements applicable to a target population of users of the content distribution network; identifying one or more insertion opportunities within programming consumed by the target population, the programming delivered over a first modulated radio frequency (RF) channel; causing delivery of the one or more secondary content elements at one or more of the identified insertion opportunities via selective switching of the one or more secondary content elements onto a second modulated RF channel; causing one or more receiving devices of the target population to access the selectively switched one or more secondary content elements via the second RF channel; and subsequently causing the one or more receiving devices accessing the selectively switched one or more secondary content elements to cease accessing the one or more secondary content elements and return to accessing the programming via the first RF channel. In one variant, upon a completion of the one or more secondary content elements, removal of delivery of the one or more content elements via the second modulated RF channel is performed.
In another variant, at least the (i) causing delivery via selective switching, and (ii) causing removal, cooperate to minimize use of the bandwidth.
In a further variant, the method further comprising causing, during at least a portion of delivery of the one or more secondary content elements, removal of at least part of the programming from the first modulated RF channel. For example, in one implementation, during at least a portion of the removal of at least part of the programming from the first modulated RF channel, delivery of alternate programming via the first modulated RF channel is provided.
In another aspect of the disclosure, computer readable apparatus is disclosed. In one embodiment, the apparatus includes a non-transitory storage medium, the non-transitory medium comprising at least one computer program having a plurality of instructions, the instructions configured to, when executed on a processing apparatus: obtain first data relating to one or more present or future available advertising insertion opportunities within a programming content stream being delivered over a content distribution network; receive a communication from a network side process, the communication comprising data indicating a channel to which to tune for delivery of advertising appropriate for the one or more opportunities; and cause tuning of a receiver apparatus to the channel at a prescribed time associated with the one or more insertion opportunities to access the appropriate advertising.
In one variant, the plurality of instructions are further configured to obtain second data identifying at least a receiver device of a user of the content distribution network, and transmit at least a portion of the second data to a second network-side process. The second network-side process is configured, for example, to utilize the second data to access a network account database, the database comprising a plurality of data relating to demographic factors associated with an account with which the receiver device is associated.
In another variant, the at least one computer program further comprises a computer program configured to: generate impression data relating to a receiver device on which the at least one computer program is operative to run, the impression data based at least on functional activity within the receiver device during use; and cause transmission of the impression data to a network-side process via a communication channel. For example, in one implementation, the causation of tuning of a receiver apparatus to the channel to receive the appropriate advertising comprises accessing an application programming interface (API) associated with middleware of the receiver device, the API configured to cause the receiving apparatus to tune to a particular radio frequency (RF) channel at the prescribed time.
In one particular configuration, the receipt of the communication from a network side process is performed using an in-band RF channel of the network, and the transmission of the impression data is performed using an out-of-band (OOB) communication channel of the network, e.g., one that utilizes a connection-less communication protocol.
In another variant, the at least one computer program further comprises logic configured to: detect that, after the tuning to the channel, the appropriate advertising is not present or available on the channel; and obtain an alternate channel to which to tune the receiver apparatus so as to access second appropriate advertising, and take corrective action based thereon; e.g., select second appropriate advertising so as to fit within the remaining time period.
In a further aspect of the disclosure, computerized network apparatus is disclosed. In one embodiment, the apparatus is configured for substantially automated insertion of secondary content for use by one or more users of a managed content distribution network, and includes server apparatus comprising: processor apparatus; first network interface apparatus in data communication with the processor apparatus configured to communicate with a secondary content processing entity of the managed content distribution network; second network interface apparatus in data communication with the processor apparatus and configured to communicate with one or more network entities configured to select appropriate secondary content for respective ones of the plurality of user receiver devices; third network interface apparatus in data communication with the processor apparatus configured to communicate with a plurality of user receiver devices via at least one or more communication channels of the managed content distribution network; and storage apparatus in data communication with the processor apparatus, the storage apparatus comprising at least one computer program.
In one variant, the at least one computer program is configure to, when executed on the processor apparatus: receive, via the first network interface apparatus, indication of an impending insertion opportunity within a program stream being accessed by a particular one of the plurality of receiver devices; receive, via the second network interface apparatus, data indicative of a communication channel over which the particular one receiver device can access secondary content, the secondary content having been determined to be applicable to that particular one receiver device; and transmit, via the third interface, at least a portion of the data indicative of the communication channel to an insertion process of the network, for insertion thereof by the insertion process within the program stream.
In one implementation, the indication of an impending insertion opportunity within a program stream being accessed by a particular one of the plurality of receiver devices comprises an SCTE-35 compliant cue issued by a program network entity that is the source of the program stream, and the communication channel comprises a radio frequency (RF) QAM channel accessible to the particular one of the receiver devices via a switched digital video (SDV) switching device of the content distribution network. Insertion of the at least portion of the data by the insertion process within the program stream comprises insertion into a program mapping table (PMT) via a splicing process of the content distribution network.
In another embodiment, the computerized network apparatus is configured for substantially automated selection and insertion of secondary content, and includes: first server apparatus comprising: processor apparatus; first network interface apparatus in data communication with the processor apparatus and configured to communicate with a receiver evaluation entity; second network interface apparatus in data communication with the processor apparatus and configured to communicate with a second server apparatus configured to select appropriate secondary content for respective ones of the plurality of user receiver devices; and storage apparatus in data communication with the processor apparatus, the storage apparatus comprising at least one computer program. In one implementation, the computer program is configured to, when executed: receive from the receiver evaluation entity via the first network interface apparatus, data relating to one or more of the plurality of receiver devices; and transmit, via the second interface, at least a portion of the data relating to the one or more receiver devices for use by the second server apparatus to select appropriate secondary content.
In another embodiment, the network apparatus further includes a second server apparatus comprising: processor apparatus; first network interface apparatus in data communication with the processor apparatus of the second server apparatus and configured to communicate with the first server apparatus; second network interface apparatus in data communication with the processor apparatus of the second server apparatus and configured to communicate with a third server apparatus; and storage apparatus in data communication with the processor apparatus of the second server apparatus, the storage apparatus comprising at least one computer program. In one variant, the at least one computer program is configured to, when executed: receive from the first server apparatus the at least portion of the data relating to one or more of the plurality of receiver devices; utilize the received at least portion of the data to generate one or more secondary content selections appropriate to the one or more receiver devices; obtain the one or more selected secondary content; and transmit, via the second interface, at least a portion of the selected and obtained secondary content, to the third server apparatus.
In another embodiment, the network apparatus includes a third server apparatus having: processor apparatus; first network interface apparatus in data communication with the processor apparatus of the third server apparatus and configured to communicate with a secondary content processing entity of the managed content distribution network; second network interface apparatus in data communication with the processor apparatus of the third server apparatus and configured to communicate with the second server apparatus to receive the at least portion of the selected secondary content appropriate to the one or more receiver devices; third network interface apparatus in data communication with the processor apparatus configured to communicate with a plurality of user receiver devices via at least one or more communication channels of the managed content distribution network; and storage apparatus in data communication with the processor apparatus of the third server apparatus, the storage apparatus comprising at least one computer program. In one implementation, the at least one computer program is configured to, when executed: receive, via the first network interface apparatus, indication of an impending insertion opportunity within a program stream being accessed by a particular one of the plurality of receiver devices; receive, via the second network interface apparatus, data indicative of a communication channel over which the particular one receiver device can access secondary content, the secondary content having been determined to be applicable to that particular one receiver device; transmit, via the third interface, at least a portion of the data indicative of the communication channel to an insertion process of the network, for insertion thereof by the insertion process within the program stream; and subsequently transmit, via the third interface, at least a portion of the received secondary content for insertion thereof by the insertion process within the program stream.
In another aspect of the disclosure, a computerized method of delivering secondary content in a content distribution network is described. In one embodiment, the method includes: receiving a message indicate of an impending event within a program stream; based at least on the received first message, generating a second message and transmitting the second message to a network secondary content management process to alert the secondary content management process of the impending event; based at least on the second message, generating via the secondary content management process a third message relating at least to one or more source channels over which secondary content is to be delivered, and transmitting the third message to an insertion process; inserting, via the insertion process and based at least on the third message, data relating to the one or more source channels into one or more primary content streams; based on a start of the impending event, generating a fourth message and transmitting the fourth message to the secondary content management process; based at least on the fourth message, generating via the secondary content management process a fifth message relating at least to the start of the event, and transmitting the fifth message to an insertion process; inserting, via the insertion process and based at least on the fifth message, data indicative of the start of the event into the one or more primary content streams; and causing transmission of the secondary content via the one or more source channels.
In one variant, the method further includes: generating via the secondary content management process a sixth message relating at least to an end of the event, and transmitting the sixth message to an insertion process; inserting, via the insertion process and based at least on the sixth message, data indicative of the end of the event into the one or more primary content streams; and causing cessation of transmission of the secondary content via the one or more source channels. In one implementation, the method yet further includes receiving via an out-of-band (OOB) channel of the network, data indicative of a receiver device having tuned to the one or more source channels to receive the secondary content.
In another variant, the first message comprises an SCTE-35-compliant message; the second message comprises a simple network message protocol (SNMP) trap message; the third message comprises a client break message; the fourth message comprises a second SNMP trap message; and the fifth and sixth messages each comprise a client trigger message.
In another aspect of the disclosure, a computerized method of accessing secondary content via a client device of a content distribution network is described. In one embodiment, the method includes: receiving a program stream via at least a first radio frequency (RF) channel of the network; extracting data from the program stream relating at least to one or more source RF channels over which secondary content is to be delivered; storing the extracted data in a data structure; receiving a trigger event via the program stream; based at least on the received trigger event, causing access of the data structure to obtain at least a portion of the extracted data; utilizing the obtained extracted data to identify a second radio frequency channel to which to tune a receiver apparatus of the client device; and causing tuning of the receiver apparatus to the second RF channel to access a program stream carrying the secondary content.
In another aspect of the disclosure, a computerized decision “engine” is disclosed. In one embodiment, the engine comprises a plurality of computer algorithms operative to run on a computerized platform (e.g., client device such as set-top box or portable tablet computer or smartphone) and configured to extract data from in-band program streams received by the device over a network, store the extracted data, and utilize the stored data to access targeted secondary content via a switched digital video delivery model.
In a further aspect, a data architecture is disclosed.
In a further aspect, a network architecture for use within a managed content distribution network is disclosed.
These and other aspects of the disclosure shall become apparent when considered in light of the detailed description provided herein.
All figures © Copyright 2016 Charter Communications, Inc. All rights reserved.
Reference is now made to the drawings wherein like numerals refer to like parts throughout.
As used herein, the term “advertising zone” may include the delivery of advertisements, promotions, or other secondary content with an actual geographic zone, a demographic “zone” or logical space, a psychographic zone or logical space, a user-based preference space, a primary/secondary content context space, and so forth.
As used herein, the term “application” refers generally to a unit of executable software that implements a certain functionality or theme. The themes of applications vary broadly across any number of disciplines and functions (such as on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculator etc.), and one application may have more than one theme. The unit of executable software generally runs in a predetermined environment; for example, the unit could comprise a downloadable Java Xlet™ that runs within the JavaTV™ environment.
As used herein, the term “client device” includes, but is not limited to, digital set-top boxes (e.g., DSTBs), personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, tablets, phablets, personal digital assistants (PDAs), personal media devices (PMDs), and smartphones.
As used herein, the term “computer program” or “software” is meant to include any sequence or human or machine cognizable steps which perform a function. Such program may be rendered in virtually any programming language or environment including, for example, Python, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML, VoXML), and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA), Java™ (including J2ME, Java Beans, etc.), Binary Runtime Environment (e.g., BREW), C#, and the like.
The terms “consumer premises equipment” (CPE) and “consumer device” refer without limitation to any type of electronic equipment for use within a consumer's or user's premises and connected to a content distribution network. The term “consumer device” includes terminal devices that have access to digital television content via a satellite, cable, or terrestrial network. The term “consumer premises equipment” (CPE) includes such electronic equipment such as set-top boxes (e.g., DSTBs or IPTV devices), televisions, cable modems (CMs), embedded multimedia terminal adapters (eMTAs), whether stand-alone or integrated with other devices, digital video recorders (DVR), gateway storage devices, and ITV personal computers.
As used herein, the term “database” refers generally to one or more tangible or virtual data storage locations, which may or may not be physically co-located with each other or other system components.
As used herein, the term “DOCSIS” refers to any of the existing or planned variants of the Data Over Cable Services Interface Specification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0 and 3.1. DOCSIS (version 1.0) is a standard and protocol for internet access using a “digital” cable network.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet.
As used herein, the terms “microprocessor” and “digital processor” are meant generally to include all types of digital processing devices including, without limitation, digital signal processors (DSPs), reduced instruction set computers (RISC), general-purpose complex instruction set computing (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable compute fabrics (RCFs), array processors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single unitary IC die, or distributed across multiple components.
As used herein, the terms “MSO” or “multiple systems operator” refer to a cable, satellite, or terrestrial network provider having infrastructure required to deliver services including programming and data over those mediums.
As used herein, the term “network content provider” refers generally and without limitation to any content service provider or content-providing logical “network” such as e.g., ABC, NBC, CBS, etc., regardless of delivery platform or underlying content distribution network infrastructure (see below).
As used herein, the terms “network” and “bearer network” (distinguished from “network content provider” supra) refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications or networking protocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP, 3GPP2, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).
As used herein, the term “network interface” refers to any signal, data, or software interface with a component, network or process including, without limitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g., USB2, USB 3.0), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radio frequency tuner (e.g., in-band or OOB, cable modem, etc.), Wi-Fi (802.11), WiMAX (802.16), PAN (e.g., 802.15), cellular (e.g., LTE/LTE-A, 3GPP, 3GPP2, UMTS), or IrDA families.
As used herein, the terms “personal media device” and “PMD” refer to, without limitation, any device, whether portable or otherwise, capable of storing and/or rendering media.
As used herein, the term “secondary content” refers without limitation to content other than primary programming content, such as e.g., advertisements, promotions, “telescoping” content, info-mercials, trailers, icons or animated overlays, etc. which may be presented either alone or in conjunction with the primary (or yet other) content.
As used herein, the term “server” refers to, without limitation, any computerized component, system or entity regardless of form which is adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer network.
As used herein, the term “user interface” refers to, without limitation, any visual, graphical, tactile, audible, sensory, or other means of providing information to and/or receiving information from a user or other entity.
As used herein, the term “Wi-Fi” refers to, without limitation, any of the variants of IEEE-Std. 802.11 or related standards including 802.11 a/b/g/n/s/v/ac or 802.11-2012, as well as so-called “Wi-Fi Direct”, each of the foregoing incorporated herein by reference in its entirety.
As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, Zigbee, RFID/NFC, narrowband/FDMA, OFDM, PCS/DCS, LTE/LTE-A, analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
Overview
In one salient aspect, the present disclosure provides apparatus and methods for substantially automatically selecting and inserting secondary content (e.g., advertising) which is particularly targeted to one or more users of a managed content distribution network such as a cable, satellite, of HFCu network.
In one exemplary embodiment, the methods an apparatus disclosed herein leverage extant network infrastructure, including so-called “switched digital video” or SDV capability, to efficiently identify insertion opportunities within programming or other content being delivered to the targeted user(s), select appropriate advertising content, and cause placement of the advertising content onto an SDV channel accessible by the targeted user(s). In one implementation, a software component (decision engine) resident on each user's set-top box or other media receiver communicates with network-side entities to identify the placement opportunities, and receive device-specific “targeting” instructions (e.g., particular SDV RF channels and related data) for use in conjunction with the identified opportunities. Upon reaching the targeted insertion opportunity, the software utilizes extant interfaces (e.g., middleware on the set-top box) to cause tuning of the device to the appropriate SDV channel at the appropriate time, and subsequent tuning back to the (primary) content program stream upon completion of the advertisement.
In another implementation, the client-side decision engine is configured with additional intelligence, such that it can use audience segmentation profiles or other data to indigenously correlate certain available secondary content with a particular receiver device or household, in effect making the targeting decision locally.
Notably, in the exemplary embodiment, the targeted advertisements are only placed onto the relevant SDV channel when they are needed (e.g., there is an opportunity and an advertisement relevant to the particular targeted receiver device and which fits within the allotted time), and in a “just-in-time” fashion, so that bandwidth consumption within the network is minimized. Economies of scale may also be created where multiple different users are viewing the same primary program stream, and have similar demographic and/or psychographic profiles wherein a common advertisement can be used for each; in such cases, multiple users can be tuned (by their respective software components) to a common SDV channel to simultaneous receive the targeted advertisement(s).
In alternate embodiments, targeted advertising is delivered via IP-based streaming to a user's IP-enabled mobile device or Smart TV via the MSO's data services. In one such implementation, the user's IP-enabled device is equipped with a an application program (decision engine comparable to that described above) receives notification via the IP streaming media of insertion opportunities; the decision engine then instructs the IP-enabled device to access a URL of a secondary content source (e.g., third party web server) where appropriate secondary content for the IP-enabled device (and/or associated subscriber or household) is available. Upon completion, the media stream is switched back to the primary content URL.
Advantageously, some exemplary embodiments of the present disclosure also maximally leverage extant network advertising and other infrastructure, thereby making upgrade or addition of the various described functionalities substantially “drop in”, and obviating significant component retrofits or replacement (i.e., much is accomplished via software/firmware updates or downloads).
Exemplary embodiments of the apparatus and methods of the present disclosure are now described in detail. While these exemplary embodiments are described in the context of a managed content distribution network (e.g., hybrid fiber coax (HFC) cable) architecture having a multiple systems operator, digital networking capability, and plurality of client devices/CPE, and
Internet delivery via e.g., RF QAM and DOCSIS cable modem, the general principles and advantages of the disclosure may be extended to other types of networks, architectures and applications, whether broadband, narrowband, wired or wireless, terrestrial or satellite, managed or unmanaged (or combinations thereof), or otherwise, the following therefore being merely exemplary in nature.
It will also be appreciated that while described generally in the context of a network providing service to a customer or consumer or end user (i.e., residential), the present disclosure may be readily adapted to other types of environments including, e.g., commercial/retail, or enterprise domain (e.g., businesses), and government/military applications. Myriad other applications are possible.
Also, while certain aspects are described primarily in the context of the well-known Internet Protocol (described in, inter alia, Internet Protocol DARPA Internet Program Protocol Specification, IETF RCF 791 (September 1981) and Deering et al., Internet Protocol, Version 6 (Ipv6) Specification, IETF RFC 2460 (December 1998), each of which is incorporated herein by reference in its entirety), it will be appreciated that the present disclosure may utilize other types of protocols (and in fact bearer networks to include other internets and intranets) to implement the described functionality.
Other features and advantages of the present disclosure, including improvements to computerized technology, will immediately be recognized by persons of ordinary skill in the art with reference to the attached drawings and detailed description of exemplary embodiments as given below.
Managed Service Provider Network—
Moreover, the functions described below with respect to
The exemplary architecture 150 of
Content (e.g., audio, video, data, files, etc.) is provided in each downstream (in-band) channel associated with the relevant service group. To communicate with the headend or intermediary node (e.g., hub server), the client devices/CPE 106 may use the out-of-band (OOB) or DOCSIS channels and associated protocols, although the present disclosure is in no way limited to these approaches.
In addition to “broadcast” content (e.g., video programming), the systems of
Referring again to
The edge switch 194 forwards the packets received from the CMTS 199 to the QAM modulator, which transmits the packets on one or more physical (QAM-modulated RF) channels to the CPE/client devices. The IP packets are typically transmitted on RF channels (e.g., DOCSIS QAMs) that are different that the RF channels used for the broadcast video and audio programming, although this is not a requirement. The client devices/CPE 106 are each configured to monitor the particular assigned RF channel (such as via a port or socket ID/address, or other such mechanism) for IP packets intended for the subscriber premises/address that they serve. For example, in one embodiment, a business customer premises obtains its Internet access (such as for a connected Wi-Fi AP) via a DOCSIS cable modem or other device capable of utilizing the cable “drop” to the premises (e.g., a premises gateway, etc.); see the discussion of
While the foregoing network architectures described herein can (and in fact do) carry packetized content (e.g., IP over MPEG for high-speed data or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), they are often not optimized for such delivery. Hence, in accordance with another embodiment of the disclosure, a “packet optimized” delivery network is used for carriage of the packet content (e.g., Internet data, IPTV content, etc.).
Secondary Content Selection and Insertion Architecture—
Referring now to
Also shown in
In one implementation, one or more “advertising feeder programs” are designated within the SDV system. In one embodiment, these feeder programs are configured as Source ID's, which are recognized by the switched digital (SDV) delivery system as a source video feed where the secondary content (e.g., advertisements) will be placed when required, based on the triggering mechanism(s) described elsewhere herein. In one implementation, the “targeted” secondary content is placed in the “open” switched digital bandwidth pool, and do not “hard allocate” particular RF frequencies to the secondary content. This approach is used, inter alia, so as to utilize or share the physical (QAM) resources with the switched digital system, such sharing which promotes more efficient utilization of resources as a whole within the network. Notwithstanding, it is appreciated that such hard-allocation (e.g., of one or more particular frequencies or QAMs), such as to only carry secondary content, may be utilized consistent with the present disclosure if desired, whether alone or in conjunction with the “open pool” approach previously described, such as where a limited number of the available QAMs are hard-allocated, while the great preponderance are left “open.”
The relevant DE 222 of the DSTB 220 is configured to request a specific advertising feeder program every time it wants to switch to an addressable advertisement, thereby acting as a priori “designated point of entry” for each individual DSTB or customer account (or other unique identifier, including particular individuals associated with a particular account when their identity as being a viewer can be ascertained). Logic within the SDV system conducts necessary mapping to a given service group (SG), edge QAM frequency, etc. to effect delivery of the designated secondary content to that particular DSTB 220. Advantageously, the foregoing approach both (i) requires (smaller) modifications to the CASU 204, DE 222, and SDV client API 224, and (ii) reduces the total required bandwidth (even with an assumed 2% collision rate), depending on service group sizes. Specifically, the foregoing approach bypasses the need to continuously reserve bandwidth resources for secondary content when such resources can be used elsewhere for primary video delivery; rather, they can merely be switched-in or switched-out dynamically without such reservation process and its associated complexity.
It is also recognized that SDV advertisements within a service group (SG) of the network are not continuous. By adding linear advertisements, which only play a comparatively short time (e.g., on the order of seconds or a minute), QAM resources within the service group can be more efficiently utilized.
In the exemplary embodiment, the amount of bandwidth needed for secondary content delivery depends on the combination of: (i) the total addressable linear channels; (ii) the amount of overlap in the existing secondary content schedules between content networks (aka “collision rate”); and (iii) the percentage of the secondary content schedule that will be made addressable (for example, a higher percentage of the schedule made addressable requires more bandwidth than having a lower percentage of the schedule be addressable). In one implementation, this relationship can generally be represented by Eqn: (1):
BWr=(BWbi×nabi×nazi×navi)+(BWbj×nabj×nazj×navj) Eqn. (1)
wherein:
So, as an illustration of the foregoing, two (2) advertisements run in a given break with three (3) variants each and supporting HD & SD placements in 6 advertising zones would require 2×3×6=36×baseline (SD) advertising bandwidth+36×HD advertising bandwidth, or 36+(4×36)=180×SD bandwidth (assuming HD=4×SD BW). Hence, under a reservation-based scheme, appreciable amounts of bandwidth would need to be reserved to accommodate the foregoing schedule, whereas in the SDV implementation, such bandwidth is only accessed/consumed when needed. In the exemplary specific implementation of the architecture 200 of
A third-party campaign management server 218 is also shown, communicating with the SDS 216 in the exemplary embodiment via a VPN (virtual private network) “tunnel” so as to protect the transmitted (sensitive) data flowing between the MSO and the third-party advertising campaign management service. Hence, in the illustrated embodiment, many of the higher-level or strategic campaign management functions are allocated to a non-MSO entity, while the “tactical” insertion of particular secondary content within program streams delivered to particular receiver devices/households is handled by the MSO infrastructure. So, for example, and advertiser (e.g., car maker) who wants to maximize their penetration into the subset of MSO subscribers who might have interest in their cars could simply communicate such desire to the third-party campaign manager, who then structures a campaign for delivery to “targeted” MSO subscribers (e.g., those who have previously purchased or leased a car from the car maker, have expressed interest in their cars, etc.) as determined by the receiver/household profile (described in greater detail below).
As shown, the architecture 200 of
Additionally, on the client device side, the DSTB 220 further includes a switch engine or API (application programming interface) 224 with which the DE conducts inter-process communication so as to effect content delivery “switches” (i.e., per the SDV infrastructure of the MSO network, as shown in
The foregoing components are in one embodiment each in data communication with one another via a LAN/WAN/MAN 160 (see
Alternatively, in a localized (decentralized) approach, all the CASU servers 204 for the MSO are located in the respective (local) headend. Each CASU server 204 is accordingly configured for one advertising zone. In addition, the SDS 216, hub 202, and CPSU 206 are also located within the same (respective) headend. Various permutations of the foregoing are also envisaged by the present disclosure.
Moreover, while the architecture 200 of
Referring now to
As shown, the various entities of the architecture 200 transfer various types of data structures (e.g., .ser and .ver files, encoded video advertising content, and other data files) between themselves to effect the functions of (i) secondary content selection, and (ii) secondary content insertion within extant program streams delivered to particular receiver devices 220.
The architecture of
In one exemplary scenario, the extant content channels (and the SCTE 35 or other cues present therein) are replaced by a customized linear addressable cue (described in greater detail below); however, instead of having the advertisements be present on the local video library 244, a third-party advertisement agency or content provider is used to dynamically supply advertising content via the CDN 254 for placement into the linear feed, such dynamic supply being based on e.g., various predetermined business rules.
In one implementation, the incoming programming content (e.g., from a content network or source) includes inserted SCTE-35 cues; these cues are removed and replaced with a customized linear addressable counterpart cue structured specifically to useable by the client application on linear-addressable enabled devices (e.g., DSTBs) of network subscribers, such as the client 220 of
In the exemplary implementation, the DPI (digital program insertion) packet identifier or PID is sourced from the CASU 204 (
The “linear addressable” encoded SCTE-35 cue is then mixed into the transport stream (TS) stream via the splicer 210 (with a different PID; e.g., hexadecimal 0x86), so that the client application/decision engine 222 on the relevant client devices can access the stream designated by that PID (i.e., the targeted advertisement) in advance of the beginning of the advertising spot, so as to render a substantially seamless transition for the client device user.
Non-Linear Variants—
It will also be appreciated that the methods and apparatus described herein can be readily adapted for use with non-linear delivery paradigms such as e.g., VOD (video on demand). In one such variant, non-linear content-related delivery includes inserted breaks or cues similar to the linear content. Although primarily envisaged as “commercial free”, such non-linear content can be encoded with breaks for advertisements or other secondary content either by the content source or the MSO, such as for example for use with non-premium or free content streaming by the MSO. For instance, the MSO might upcharge for “commercial free” VoD or Start Over functionality, whereas that with the commercial breaks might be offered at a reduced monthly or one-time rate, or even free or as consideration for some other service provided by the subscriber (e.g., participating in a survey).
In one implementation, the non-linear content (e.g., VOD movie or TV episode) is characterized, whether by the MSO or an upstream content source or processing entity, as to one or more insertion opportunities therein (e.g., is parsed into segments divided by one or more insertion opportunities). In one methodology, one or more of the insertion opportunities associated with the non-linear content (e.g., at onset, such as when VOD session is queueing up the requested content for delivery, at a pre-planned intermediate break within the movie, at the end of the movie, or as part of a telescoping function associated with the movie) are identified, whether before delivery or “on the fly” during delivery, and one or more secondary content elements selected for “insertion” into the non-linear opportunities based on e.g., fitting within a prescribed temporal window, suitability for audience (e.g., no “adult” themes for a prospectively juvenile audience), as well as the CPSU-provided profile data resident on the CPE and used by the DE 222. In the present context, the insertion of the secondary content may use the aforementioned extant SDV infrastructure of the MSO network 101, such the DSTB 220 is accessing one in-band QAM (e.g., a designated VoD QAM) for the delivery of the primary (VoD) content, including trick mode functionality via LSCP, whereas the targeted secondary content is provided via a selected SDV channel which is also accessible to the client device 220. In one such variant, the trick-mode functionality is disabled or suspended during the play of the secondary content, such that the user must effectively sit through the targeted spot to “come out the other side” within the VoD primary content. Moreover, if a user trick-modes across the break boundary (thereby triggering the SCTE-35 message to the advertising server 208 and subsequent operations; see
IP-Based Variants—
The requesting client device 286 may include home gateway devices and/or media client devices. In one embodiment a media client device is a portable device. Common examples of portable devices include, without limitation, tablets, phablets, smart phones, smart televisions (TVs), desktop and laptop personal computers (PC), and portable media players. In another embodiment, the media client device may comprise a file server; file servers are common in both commercial and residential use. For example, a subscriber may have a PC which can play media files, but which also serves his/her other consumer electronics (e.g., smart phone and tablet).
In one embodiment, an encoder 264 encodes a source file 262 from a content source 261 into at least one encoding format (e.g., transcodes a source file from one format to at least one other format). In another variant, the source file 262 is encoded into a plurality of encodings that correspond to a respective plurality of one or more device types, codecs, resolutions, file formats, audio encodings, bit rates, etc. The variety of encodings may be utilized by the CDN 278 (and the packager 270) via adaptive bitrate (ABR) streaming.
“Adaptive bitrate (ABR) streaming” refers to streaming multimedia over computer networks such that a source file thereof is encoded into multiple bitrates. Encoded content segments of varying bit rates are sent to a client device. Non-limiting examples of ABR streaming include, without limitation, MPEG-Dynamic Adaptive Streaming over HTTP (DASH), Adobe® Dynamic Streaming for flash, Apple® HTTP Adaptive Streaming, Microsoft® Smooth Streaming, QuavStreams® Adaptive Streaming over HTTP, and upLynk®.
As shown in
An output stream 266 comprises key frames (e.g., I-frames) at a certain temporal distance (e.g., 2 seconds or 10 seconds) apart. A key frame is a fully specified picture like a conventional static image file. Key frames may be placed in any number of temporal distances, from 0 (i.e., every frame is a key frame) to a single key frame followed by all delta frames, per stream.
Parameters used by the encoder 264 to encode the source file 262 include: (i) whether the output streams should be encoded into separate video and audio only tracks, or video tracks with audio included, (ii) an appropriate key frame period, (iii) a frame rate, (iv) segmentation duration, (v) video resolutions, (vi) video bitrate, (vii) audio bit rate (where necessary), (viii) audio sample rate, (ix) a number of audio channels, (x) aspect ratio, (xi) video codec, (xii) specific device profiles, (xiii) audio volume, (xiv) file type and extension, and (xv) standard specific encoding profiles. Standard specific encoding profiles include e.g., H.264, which includes different standard encoding profiles for baseline, main, and high encoding. Additionally, the encoder 264 may utilize information used for cutting out other resolutions/aspect ratios from a higher resolution/different aspect ratio file. For example, the encoder 264 may center-punch a standard definition (SD) image or video from a high definition (HD) source. Similarly, an HD image or video may be center punched from a 4K, 8K, 16K source.
While output streams 266 are shown as separate files (for example MPEG 4 transport stream (.ts) files), in a further embodiment of the present disclosure, all of the streams (i.e., streams 266) are presented in a single “super” file. Having a single comprehensive file comprising multiple streams will lower the number of files the CDN 278 must manage.
The encoder 264 may encode output streams 266 with audio tracks (e.g., AC3 audio). Different encoding formats and bit rates may be selected based on the requirements of the stream, end user equipment, and the protocols and formats used by the CDN 278.
The encoded output streams 266 may be encrypted by an encryptor 268 via an encryption algorithm (e.g., AES, DES, public key encryption, etc.). The encoded and encrypted output streams are stored in a storage device 263. In one embodiment, the functionality of both the encoder 264 and the encryptor 268 may be integrated into a single apparatus
The stored output streams are utilized by a packager 270 to provide a manifest (or index/playlist) file 276 and video segments 272 to a requesting client device 282. Specifically, the manifest file 276 is a data structure comprising a listing of addresses for each of the video segments 272 of a stream of data, and includes information about the video segments 272 such as bitrates, closed captioning, audio, etc. Different ABR models may use different manifest files 276.
In one implementation, the list of media segment entries in the manifest file 276 comprises a list of network addresses (which may be remote or local) where the corresponding segments 272 of media content, including the targeted secondary content and key frames 274, may be accessed and/or downloaded. For instance, each of the media segment entries may be listed by a Uniform Resource Locator (URL). In some embodiments, the entries may be in computing resource “path” format. Computing paths may be either absolute (i.e., the path provides the fully elaborated and unique location of the segment 272 in a file structure 276) or relative (i.e., the path provides a relative location of the segment 272 in a file structure 276).
The service provider may be a conglomeration of multiple logical entities. Multiple logical entities may be useful to further distribute services over various network resources or enable additional features provided by partnered corporations or providers. Multiple logical entities, for example, may provide local content for a particular service group or geographic area. Furthermore, having content providing entities closer to end users may offer lower latency and may add network redundancy. Common examples of network resources include e.g., broadcast, multicast, video-on-demand, advertisement services, local services, etc. In one specific example, the media segment listing may include a listing of URL links which is further punctuated with HTML tags or Javascript, which is configured to enable targeted advertisement insertion. For instance, the video client of the client device 282 (e.g., DE “app”; not shown) may insert tailored locally or remotely stored advertisement for commercial breaks, such as under the direction of the CPSU 206 of
In the exemplary embodiment, each media segment 272 is an encoded and encrypted subsection or segment of media content. The media segments 272, when decrypted, decoded, and played in the appropriate order, render the original media content. In one implementation, each media segment 272 represents a portion of video associated with a specific resolution, codec, and time stamp. The media segments are assembled according to a time stamp sequence.
Access control such as Digital Rights Management (DRM), conditional access (CA), trusted domain (TD), etc. may be implemented by the packager 204 (or alternatively the CDN 206). One example of utilization of the foregoing technologies is described within co-owned U.S. patent application Ser. No. 13/710,308 filed on Dec. 10, 2012 entitled “APPARATUS AND METHODS FOR CONTENT TRANSFER PROTECTION”, and issued as U.S. Pat. No. 9,565,472 on Feb. 7, 2017, which is incorporated herein by reference in its entirety. As discussed therein content is delivered via a managed content distribution network (such as a cable or satellite or HFCu network having an MSO), and the MSO manages the rights and restrictions of the content outside of a premises, and in a data center or headend, by providing requested content to a gateway device within the premises of a user.
In another embodiment, the methods and apparatus disclosed in U.S. Pat. No. 8,701,138 issued Apr. 15, 2014 and entitled “ZONE CONTROL METHODS AND APPARATUS”, which is incorporated herein by reference in its entirety, may be used consistent with the present disclosure. Specifically, the aforementioned patent discloses, inter alia, methods and apparatus for selectively providing targeted secondary content to a user based at least in part on a logical, geographic, or other “zone” or space associated with the user. In one embodiment, when the user requests primary content at a non-legacy device (e.g., an IP-capable device such as an IP-enabled DSTB, portable computer, or 4G smartphone), the secondary content that is provided therewith is the same secondary content which would have been provided to the user had the request been generated at a legacy device; i.e., the “zone” (whether geographic, demographic, psychographic, or otherwise) is preserved. In one implementation, a non-legacy device is associated with a user's zone by introducing a link between a server providing content to the device (e.g., a web server) and a server which has the ability to determine an appropriate zone for the user. This is accomplished for example by associating each user with an advertisement zone identifier. Alternatively, the foregoing may be accomplished by associating each user with a device that is associated with a physical hub or node identifier, which, in turn, is associated with an advertisement zone identifier. In yet another variant, a service group identifier (rather than advertisement zone identifier) may be used.
Hence, using such methods and apparatus, the “reach” of a given advertising schedule (and its associated particular spots) generated using the methodology herein that is based on data derived from legacy CPE can be preserved for non-legacy, mobile devices.
Server Apparatus—
The server apparatus of
In the illustrated embodiment, the CASU/CPSU/SDS/GS logical processes 371 described above with respect to
In the illustrated implementation, the CASU/CPSU/SDS/GS server functionality is based on an a “distributed’ architecture wherein each component implements its own persistence database, in lieu of a centralized data store, although it will be appreciated that other configurations may be used consistent with the present disclosure. This decentralized approach advantageously provided enhanced/simpler failover and redundancy features, and also may reduce access latency when compared with a more centralized approach. In one particular implementation, the component storage is placed within a virtual SAN (storage area network) to “future-simplify” failover and redundancy. If any one of these components becomes unavailable, a replacement server can easily be brought online to replace it, thereby mitigating the effects of such failure.
Client Device—
The client device 220 of
In the illustrated embodiment, the DE logical process 222 and the SDV “switch engine” (with API) 224 described above with respect to
Also resident on the client device 220 is middleware configured to execute one or more privileged applications (which may also be remotely controllable by the MSO or its proxy), including the SDV “switch engine” function 224. In the exemplary implementation, the middleware contains the SDV switch API 224, and the DE 222 is coded to access the API in order to effect selective tuning of one or more tuners in the front end 460 of the DSTB to designated QAMs or other channels upon which the targeted secondary content is carried, and subsequent tuning back to the original (primary) program stream PID, as described in greater detail below with respect to
Referring now to
As shown, the head end of the HFC network 101 (per the infrastructure 200 of
So-called “command and control” of the DE 222 occurs in this embodiment via the OOB HFC channels (i.e., low bandwidth “side channels” used for ancillary communication and the like), so as to provide profile and segmentation data to the DE 222 from the CPSU 206, receive impression data reporting, cause updates of or configuration changes to the DE 222, or otherwise control its operation remotely (including from third party campaign management entities which may be outside the MSO network, e.g., via the hub and SDS of the MSO network as shown in
Referring now to
The CM 502 of
In the illustrated embodiment, the client 282 (e.g., a wireless-enabled tablet, smartphone, Smart TV, etc.) includes the DE logical process 222 implemented as computerized logic rendered as code and operative to run on the respective client 282. In one embodiment, the DE client 222 comprises a software application (“app”) that is downloaded onto the client device 282 either at time of install or subsequently thereafter, such as via an “app store” or similar functionality, or by insertion of media such as CD-ROM or USB flash drive. The MSO or a proxy thereof may also provide the DE app 222 to the user for install on the client 282 such as via download of an executable, and subsequent remote execution thereof via the processor apparatus of the client 282.
The exemplary client device 282 shown in
Also resident on the client device 282 is other application software 523 configured to (i) enable user browsing of the necessary content source or portal (e.g., MSO URL) to select primary content, (ii) decode and render the selected and downloaded primary content (e.g., an AVC or H.264 codec or media player) as well as any “inserted” secondary content, (iii) implement any DRM or similar content protection policies (if any).
Methodology—
As shown, the general method 600 includes first identifying one or more insertion or placement opportunities within primary content (step 602). As described in greater detail below with respect to
Next, per step 604, a user and/or receiver profile is obtained. For example, in one embodiment, the user's receiver device (e.g., DSTB 220 or portable IP-enabled device 228) has unique identifying information such as a MAC address or IP address associated therewith, and this information is correlated to a user (subscriber) account within the MSO subscriber database which also contains demographic, geographic, psychographic, and other information of possible use (e.g., subscription level, recently selected OD content, etc.) for which the subscriber (and any associated household members) can be “profiled” in terms possible correlation to secondary content. As described previously herein, this analytical capability in one implementation resides within one or more cloud-based entities (either MSO- or third-party operated algorithms), or to varying degrees within the DE 222 of the client device.
Per step 606, the appropriate secondary content is selected based on the aforementioned profiling. Such selections may be made “on the fly” (e.g., at time of signaling of the impending insertion opportunity), or in advance (e.g., based on characterization of the individual secondary content by the provider or source as being applicable to certain profiles, demographics, geographics, psychographics, etc.).
The selection may also take into account attributes of the primary content within which the secondary content will be inserted. For example, if the primary content comprises a children's show or movie, it may be fairly safe to assume that the primary viewer in the household consuming the content is not an adult, and hence more adult-oriented secondary content may not be appropriate (or even if an adult is co-consuming, such adult-oriented content is not appropriate for the child). Such information regarding the primary content can be gleaned for example from the descriptive metadata associated with the primary content (e.g., rating, origin, content descriptors or codes, etc.).
Per step 608, the selected secondary content is placed onto one or more delivery channels (e.g., the SDV “feeder” previously referenced) which are accessible to the user receiver device. As described elsewhere herein, such placement (and subsequent removal) may also be in a “just in time” fashion, such as where the secondary content is delivered to the edge device or switch within the network (see
In yet another alternative, one or more time-shifted copies of the same targeted advertisement may be placed on different delivery channels accessible by the SDV logic, such that in the event of a subsequent time-shifted user (e.g., another DSTB watching another primary content stream yet having an insertion opportunity calling for the same advertisement), the time-shifted copy can be accessed by the user so long as insertion criteria such as remaining time period, etc. are met.
It is also appreciated that the insertion logic of the system 200 may further be configured to, based at least on detection that the appropriate targeted advertising is not present or available on the alternate or feeder SDV channel, identify a remaining time period associated with the one or more insertion opportunities, and select second appropriate advertising so as to fit within said remaining time period. For example, a 30-second spot may not be available at time t=0 (start of the break) based on e.g., absence of marker messages as described below with respect to
Lastly, per step 610 of the method, 600, the receiver device (e.g., DSTB) is tuned from the primary content channel to an alternate channel (e.g., via the SDV logic of the network and switch engine 224 under control of the DE 222, or to a new URL for streaming media.
Per step 624, the server 208 generates an SNMP (simple network management protocol) “trap” message to alert the CASU server 204 of the impending insertion opportunity for the PID.
Per step 626, the CASU 204 generates a client break such as via a “DPI” (SCTE 35) trigger for transmission to the splicer 210 to insert in the primary program stream, and ultimate delivery to the CPE. In the exemplary embodiment, the message is generic (i.e., addressed as a “multicast” and thereby extractable by all CPE or clients receiving the program stream), although it will be appreciated that specific addressing may be used as desired. The message also includes the appropriate PID and other necessary information (e.g., QAM frequency) to ensure insertion of the message into the appropriate primary content stream only.
Per step 628, the splicer 210 inserts the message into the primary program stream (i.e., the appropriate PID of the PMT), and the QAMs deliver the program, stream via the HFC distribution network to the clients 220.
It will also be appreciated that the exemplary implementations described herein may further include insertion of one or more “heartbeat” messages within the secondary content stream, such as via the splicer 210. These heartbeat message may be used for, inter alia, detection by a receiving client 220 (and its application 222) of an erroneous tune or switch event, network or equipment failure, or other anomalous condition which prevents the secondary content stream from being delivered to the client. Specifically, in one variant, the splicer inserts SCTE-35 messages into the secondary content stream every N seconds, and the client application 222 is configured to, during any tune-away from the primary content stream, look for such heartbeat messages within the received secondary content stream. If such messages are not detected according to a prescribed logic (e.g., every message must be received, every message must be received and it must be received within a prescribed time window or periodicity, at least every other message must be received, etc.), then the client application 222 will cause the switch API/application 224 to invoke a tune back to the primary content, so as to avoid the user seeing “dead air” for the duration of the advertising break.
The foregoing heartbeat messages can also be used for other purposes, such as e.g., to passively cue the client application 222 to take other actions such as rendering of some locally stored content or display element on the screen concurrent with the then-showing advertisement, sampling or logging of the state of one or more parameters associated with the client device, or yet other actions. For instance, one variant of the client application 222 may be configured to count the heartbeats received, and based on knowledge of the total duration of the advertisement, identify a prescribed place within the advertising stream at which to invoke such actions. For example, a 30-second advertisement may include one heartbeat message every 2 seconds (e.g., 14 total), and by counting that 7 of the 14 heartbeats have been received know that it is approximately at the middle of the run duration of the advertisement.
Per step 630, each client receives the client break message, and the DE 222 extracts and parses it for further processing and storage.
Per step 632, the DE 222 accesses and evaluates the (previously) obtained and stored profile data sent from the CPSU 206 for selection of an appropriate SDV channel/source ID over which the secondary content will be delivered.
In one exemplary implementation, the “targeting” information derived based on the evaluation of step 632 is transmitted in one or more profiles to each affected client (e.g., DSTB). This transmitted profile includes, inter alia, information for each DSTB as to which source to select (including the correct source or program ID), and is tagged with an advertisement identifier for reference. The previously discussed digital program insertion (DPI) trigger (received seconds before the actual delivery of the advertisement) identifies the impending advertisement break, including the appropriate advertisement identifier. Based on this identifier, the DSTB then knows (based on the previously sent profile) which source or program ID to which to tune for the appropriate advertising content to be rendered on the DSTB.
Per step 634, the primary content insertion break starts (based on the existing SCTE 35 trigger in the primary content video stream), the client process operating on the relevant DSTB perform a virtual channel switch when it identifies the triggering PID value sent from the CASU, and the advertising server 208 generates a second SNMP trap message to the CASU to alert the CASU 204 of the break (step 636).
Per step 638, the CASU generates a client trigger message and sends it to the splicer 210. Per step 640, the splicer inserts the message into the program stream identified by the PID for delivery to the client(s) 220.
Per step 642, the CASU 204 conditions and begins streaming the selected secondary content onto the appropriate SDV channel identified by the SDV ID of step 632. As previously noted, the “selected” secondary content may comprise content which was previously selected (such as by a third party campaign manager) for correlation with a particular subscriber profile or subset of profiles (or “template”), or alternatively may be selected on-the-fly based on, e.g., primary content context or subject matter, prevailing events (e.g., breaking news), advertiser updates (e.g., car maker introducing brand new model), or yet other considerations.
Per step 644, the client 220 receives the client trigger message, and extracts and parses it for processing.
Per step 646, the DE 222, upon processing the message of step 644, accesses the previously stored SDV ID and generates an inter-process communication (i.e., API “call” to the switch engine API of the middleware 224) per step 648 to cause the middleware to invoke a tune event of the relevant RF tuner(s) to the appropriate frequency associated with the SDV ID. In one such sequence, the DE provides the SDV ID to the switch engine API 224, which then creates and transmits a message with the correlated SDV ID to a network-side SDV server 196 or switch 194 (see
During delivery of the secondary content via the designated SDV channel, the CASU 204 generates a series of client marker messages (in one embodiment, SCTE-35 DPI triggers) per step 650, which basically function as keep-alive messages for the SDV tune-away from the primary content. For instance in one variant, the messages are inserted via the splicer 210 every prescribed interval (e.g., 0.1 seconds) per step 652; the DE receives and parses the messages (step 654) so as to maintain the SDV ID tune-away event per step 656. If the markers are not present, the DE causes tuning back to the primary content PID per step 655, and play of the primary content at the client device 220 continues (largely unnoticed by the viewer due to the short interval).
Per step 658, when the end of the break is detected (such as via one or more additional DPI triggers specifically indicative of the end of the break), the CASU 204 generates another client trigger message and causes insertion by the splicer 210 (per step 660) into the secondary content stream so as to affirmatively and cleanly transition from the advertising content to the primary content per step 662. It will also be appreciated that multiple advertisements may be sequenced within the available break (e.g., four 30-second spots in a two-minute break). In one such implementation, each PID associated with its respective advertisement stream has a trigger or termination message inserted at or near its end to indicate to the client application 222 to queue the next sequential PID in its profile (i.e., by invoking a switch via the SDV system as previously described.
In another implementation, the client application 222 includes code which extracts an advertisement duration value for each advertisement, and hence in effect knows when to make the switch to the next advertisement (or back to the primary stream) even without a trigger message. In such case, a trigger message indicating the end of the sequence of advertisements (i.e., the end of the break) may be used to effect a smooth transition back to the primary stream if desired.
It will also be appreciated that the aforementioned heartbeat messages may, where used, act as “end of content” markers as well. For example, where a heartbeat message is purposely inserted to “coincide” with the insertion point where an “end of advertisement” message would nominally be inserted, the latter may be obviated in favor of the former. Here, the term “coincide” refers to the fact that the insertion of the heartbeat should account for any processing delays by the client in the heartbeat logic (e.g., if the latency of the client causing the tune back to the primary stream, or the next advertisement in the sequence if any is a known amount, the last heartbeat for that PID should be inserted temporally ahead of the desired transition point by that known latency value).
In a less complex paradigm, the heartbeat can merely be used as a “hard tune” event if the latency of the logic is short enough; i.e., if the time between failure to detect a requisite heartbeat and the retune back to the primary PID is short enough, so as to not cause a significant discontinuity or transition for the viewer.
At step 664, the DE accesses the stored primary content PID/SDV ID, and per step 666 makes a call to the switch engine API 224 to instigate a re-tune back to the primary content.
Per step 668, an “impression” is stored by the DE in the client 220 (e.g., in memory), and per step 670, the impression is transmitted to the CPSU 206 for further processing. In one implementation, multiple impressions are aggregated by the client/DE 222 over time, and then transmitted en masse to the CPSU 206 at a randomized time (or alternatively based on available transmission medium access, such as via a CSMA/CD or other scheme). Once the impressions have been received by the CPSU (or a proxy thereof), an ACK is sent confirming the same, and the DE 222 processes the ACK to enable logic to delete or enable overwrite of the stored impressions, so as to inter alia, make additional storage space within the client device memory.
As shown, the method 680 of
At step 684, the MSO or third party server processes the requested media stream (which may be obtained locally, or from a content library or other source as described above) to insert one or more cues or timing references within the stream. For instance, in one embodiment, the stream includes data indicative of both the start point and end point of the planned “break” within the packet stream of the processed content. These temporal references (or yet other types of data) may also be included as separate “files” as part of the manifest file generated per step 686, or as metadata.
At step 686, the packager 270 (or other entity within the network) generates the manifest file and transmits it via e.g., DOCSIS modem or other transport to the requesting client device 282.
The CASU 204, CPSU 206 (
To that end, the CPSU 206 also sends the client 282 with DE app a profile (similar to those described supra) to specify URLs for various demographics, psychographics, etc. (not shown).
Per step 690, the receiving client device's DE app unpacks the manifest file and extracts the cue (timing information), and if needed, calculates the available break time.
At step 692, the first URL in the manifest is then played by the client device's media player, and thereon in succession until the advertising break (timing cue) is reached.
At that point (or shortly before), per step 694, the DE app accesses the stored profile and selects secondary content for insertion (i.e., play by the media player app). The selected URL(s) for the secondary content are inserted into the manifest at the cue per step 696.
The media player then executes the first secondary content URL in the manifest (i.e., next on the play list), and begins playing the secondary content streamed from the web server serving that URL, per step 698.
Finally, at step 699, the media play executes the final URL in the secondary content, and reverts to the next primary content (requested stream) URL in the playlist, which in effect picks up where the user left off at the cue or break.
It is appreciated that while the foregoing methodology 680 describes a scenario where the network-side entity or entities insert cues or timing references into the streamed primary content, the present disclosure envisages other permutations, including for instance: (i) the network side entity or entities inserting the actual URL(s) for the secondary content into the primary stream; (ii) the DE or other process on the client device 282 selecting the insertion points for the secondary content; and (iii) a third party campaign manager and/or server inserting the cues/timing information, and/or the secondary content URLs, into the stream.
It will be recognized that while certain aspects of the disclosure are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the disclosure, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the disclosure disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the disclosure as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the disclosure. The foregoing description is of the best mode presently contemplated of carrying out the disclosure. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the disclosure. The scope of the disclosure should be determined with reference to the claims.
It will be appreciated that while certain steps and aspects of the various methods and apparatus described herein may be performed by a human being, the disclosed computer technology improvements are computer-implemented, and computerized apparatus and methods are necessary to fully implement these aspects for any number of reasons including, without limitation, commercial viability, practicality, and even feasibility (i.e., certain steps/processes simply cannot be performed by a human being in any viable fashion).
| Number | Name | Date | Kind |
|---|---|---|---|
| 4521881 | Stapleford et al. | Jun 1985 | A |
| 4546382 | McKenna et al. | Oct 1985 | A |
| 4602279 | Freeman | Jul 1986 | A |
| 4905080 | Watanabe et al. | Feb 1990 | A |
| 4930120 | Baxter et al. | May 1990 | A |
| 5155591 | Wachob | Oct 1992 | A |
| 5313454 | Bustini et al. | May 1994 | A |
| 5373315 | Dufresne et al. | Dec 1994 | A |
| 5481294 | Thomas et al. | Jan 1996 | A |
| 5497185 | Dufresne et al. | Mar 1996 | A |
| 5600364 | Hendricks et al. | Feb 1997 | A |
| 5673253 | Shaffer | Sep 1997 | A |
| RE35651 | Bradley et al. | Nov 1997 | E |
| 5734380 | Adams et al. | Mar 1998 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5774170 | Hite et al. | Jun 1998 | A |
| 5793409 | Tetsumura | Aug 1998 | A |
| 5793410 | Rao | Aug 1998 | A |
| 5812642 | Leroy | Sep 1998 | A |
| 5815662 | Ong | Sep 1998 | A |
| 5862312 | Mann et al. | Jan 1999 | A |
| 5878324 | Borth et al. | Mar 1999 | A |
| 5884037 | Aras et al. | Mar 1999 | A |
| 5914945 | Abu-Amara et al. | Jun 1999 | A |
| 5926205 | Krause et al. | Jul 1999 | A |
| 5929849 | Kikinis | Jul 1999 | A |
| 5935206 | Dixon et al. | Aug 1999 | A |
| 5956037 | Osawa et al. | Sep 1999 | A |
| 5963844 | Dail | Oct 1999 | A |
| 5974299 | Massetti | Oct 1999 | A |
| 6002393 | Hite et al. | Dec 1999 | A |
| 6029045 | Picco et al. | Feb 2000 | A |
| 6047327 | Tso et al. | Apr 2000 | A |
| 6081830 | Schindler | Jun 2000 | A |
| 6088722 | Herz et al. | Jul 2000 | A |
| 6092178 | Jindal et al. | Jul 2000 | A |
| 6105134 | Pinder et al. | Aug 2000 | A |
| 6124878 | Adams et al. | Sep 2000 | A |
| 6128316 | Takeda et al. | Oct 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6157377 | Shah-Nazaroff et al. | Dec 2000 | A |
| 6161142 | Wolfe et al. | Dec 2000 | A |
| 6167432 | Jiang | Dec 2000 | A |
| 6169728 | Perreault et al. | Jan 2001 | B1 |
| 6175856 | Riddle | Jan 2001 | B1 |
| 6182050 | Ballard | Jan 2001 | B1 |
| 6202210 | Ludtke | Mar 2001 | B1 |
| 6211869 | Loveman et al. | Apr 2001 | B1 |
| 6211901 | Imajima et al. | Apr 2001 | B1 |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6216152 | Wong et al. | Apr 2001 | B1 |
| 6219710 | Gray et al. | Apr 2001 | B1 |
| 6219840 | Corrigan et al. | Apr 2001 | B1 |
| 6240243 | Chen et al. | May 2001 | B1 |
| 6240553 | Son et al. | May 2001 | B1 |
| 6252964 | Wasilewski et al. | Jun 2001 | B1 |
| 6256393 | Safadi et al. | Jul 2001 | B1 |
| 6272176 | Srinivasan | Aug 2001 | B1 |
| 6282713 | Kitsukawa et al. | Aug 2001 | B1 |
| 6330609 | Garofalakis et al. | Dec 2001 | B1 |
| 6337715 | Inagaki et al. | Jan 2002 | B1 |
| 6353626 | Sunay et al. | Mar 2002 | B1 |
| 6378130 | Adams | Apr 2002 | B1 |
| 6434141 | Oz et al. | Aug 2002 | B1 |
| 6446261 | Rosser | Sep 2002 | B1 |
| 6463508 | Wolf et al. | Oct 2002 | B1 |
| 6463585 | Hendricks et al. | Oct 2002 | B1 |
| 6467089 | Aust et al. | Oct 2002 | B1 |
| 6498783 | Lin | Dec 2002 | B1 |
| 6502076 | Smith | Dec 2002 | B1 |
| 6502139 | Birk et al. | Dec 2002 | B1 |
| 6516412 | Wasilewski et al. | Feb 2003 | B2 |
| 6560578 | Eldering | May 2003 | B2 |
| 6571102 | Hogberg et al. | May 2003 | B1 |
| 6590865 | Ibaraki et al. | Jul 2003 | B1 |
| 6594699 | Sahai et al. | Jul 2003 | B1 |
| 6601237 | Ten Kate et al. | Jul 2003 | B1 |
| 6604138 | Virine et al. | Aug 2003 | B1 |
| 6615039 | Eldering | Sep 2003 | B1 |
| 6615251 | Klug et al. | Sep 2003 | B1 |
| 6647548 | Lu et al. | Nov 2003 | B1 |
| 6651103 | Markowitz et al. | Nov 2003 | B1 |
| 6671736 | Virine et al. | Dec 2003 | B2 |
| 6681393 | Bauminger et al. | Jan 2004 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6700624 | Yun | Mar 2004 | B2 |
| 6704930 | Eldering et al. | Mar 2004 | B1 |
| 6718551 | Swix et al. | Apr 2004 | B1 |
| 6725459 | Bacon | Apr 2004 | B2 |
| 6728269 | Godwin et al. | Apr 2004 | B1 |
| 6728840 | Shatil et al. | Apr 2004 | B1 |
| 6738978 | Hendricks et al. | May 2004 | B1 |
| 6742187 | Vogel | May 2004 | B1 |
| 6745245 | Carpenter | Jun 2004 | B1 |
| 6763391 | Ludtke | Jul 2004 | B1 |
| 6771290 | Hoyle | Aug 2004 | B1 |
| 6772435 | Thexton et al. | Aug 2004 | B1 |
| 6775843 | McDermott | Aug 2004 | B1 |
| 6799196 | Smith | Sep 2004 | B1 |
| 6842783 | Boivie et al. | Jan 2005 | B1 |
| 6868439 | Basu et al. | Mar 2005 | B2 |
| 6891841 | Leatherbury et al. | May 2005 | B2 |
| 6901606 | Wright et al. | May 2005 | B2 |
| 6909837 | Unger | Jun 2005 | B1 |
| 6917628 | McKinnin et al. | Jul 2005 | B2 |
| 6944166 | Perinpanathan et al. | Sep 2005 | B1 |
| 6948183 | Peterka | Sep 2005 | B1 |
| 6961430 | Gaske et al. | Nov 2005 | B1 |
| 6981045 | Brooks | Dec 2005 | B1 |
| 6985934 | Armstrong et al. | Jan 2006 | B1 |
| 6986156 | Rodriguez et al. | Jan 2006 | B1 |
| 7010801 | Jerding et al. | Mar 2006 | B1 |
| 7012891 | Chandran et al. | Mar 2006 | B1 |
| 7024461 | Janning et al. | Apr 2006 | B1 |
| 7024676 | Klopfenstein | Apr 2006 | B1 |
| 7027460 | Iyer et al. | Apr 2006 | B2 |
| 7039116 | Zhang et al. | May 2006 | B1 |
| 7039169 | Jones | May 2006 | B2 |
| 7039614 | Candelore | May 2006 | B1 |
| 7039928 | Kamada et al. | May 2006 | B2 |
| 7039938 | Candelore | May 2006 | B2 |
| 7047309 | Baumann et al. | May 2006 | B2 |
| 7058387 | Kumar et al. | Jun 2006 | B2 |
| 7069573 | Brooks et al. | Jun 2006 | B1 |
| 7075945 | Arsenault et al. | Jul 2006 | B2 |
| 7086077 | Giammaressi | Aug 2006 | B2 |
| 7089577 | Rakib et al. | Aug 2006 | B1 |
| 7093272 | Shah-Nazaroff et al. | Aug 2006 | B1 |
| 7100183 | Kunkel et al. | Aug 2006 | B2 |
| 7103906 | Katz et al. | Sep 2006 | B1 |
| 7107462 | Fransdonk | Sep 2006 | B2 |
| 7127619 | Unger et al. | Oct 2006 | B2 |
| 7133837 | Barnes, Jr. | Nov 2006 | B1 |
| 7143431 | Eager et al. | Nov 2006 | B1 |
| 7146627 | Ismail et al. | Dec 2006 | B1 |
| 7150017 | Vogl et al. | Dec 2006 | B1 |
| 7152237 | Flickinger et al. | Dec 2006 | B2 |
| 7155508 | Sankuratripati et al. | Dec 2006 | B2 |
| 7174126 | McElhatten et al. | Feb 2007 | B2 |
| 7174385 | Li | Feb 2007 | B2 |
| 7178161 | Fristoe et al. | Feb 2007 | B1 |
| 7181010 | Russ et al. | Feb 2007 | B2 |
| 7191461 | Arsenault et al. | Mar 2007 | B1 |
| 7194756 | Addington et al. | Mar 2007 | B2 |
| 7197472 | Conkwright et al. | Mar 2007 | B2 |
| 7200788 | Hiraki et al. | Apr 2007 | B2 |
| 7203940 | Barmettler et al. | Apr 2007 | B2 |
| 7207055 | Hendricks et al. | Apr 2007 | B1 |
| 7216265 | Hughes et al. | May 2007 | B2 |
| 7222078 | Abelow | May 2007 | B2 |
| 7225164 | Candelore et al. | May 2007 | B1 |
| 7225458 | Klauss et al. | May 2007 | B2 |
| 7228555 | Schlack | Jun 2007 | B2 |
| 7237250 | Kanojia et al. | Jun 2007 | B2 |
| 7246150 | Donoho et al. | Jul 2007 | B1 |
| 7246172 | Yoshiba et al. | Jul 2007 | B2 |
| 7246366 | Addington et al. | Jul 2007 | B1 |
| 7254608 | Yeager et al. | Aug 2007 | B2 |
| 7257650 | MacIesowicz | Aug 2007 | B2 |
| 7263065 | Cahn | Aug 2007 | B1 |
| 7266198 | Medvinsky | Sep 2007 | B2 |
| 7266611 | Jabri et al. | Sep 2007 | B2 |
| 7266726 | Ladd et al. | Sep 2007 | B1 |
| 7274661 | Harrell et al. | Sep 2007 | B2 |
| 7280737 | Smith | Oct 2007 | B2 |
| 7283803 | Karaoguz et al. | Oct 2007 | B2 |
| 7305691 | Cristofalo | Dec 2007 | B2 |
| 7308415 | Kimbrel et al. | Dec 2007 | B2 |
| 7317728 | Acharya et al. | Jan 2008 | B2 |
| 7324523 | Dacosta | Jan 2008 | B2 |
| 7325073 | Shao et al. | Jan 2008 | B2 |
| 7327692 | Ain et al. | Feb 2008 | B2 |
| 7334044 | Allen | Feb 2008 | B1 |
| 7340759 | Rodriguez | Mar 2008 | B1 |
| 7346688 | Allen et al. | Mar 2008 | B2 |
| 7352775 | Powell | Apr 2008 | B2 |
| 7355980 | Bauer et al. | Apr 2008 | B2 |
| 7356751 | Levitan | Apr 2008 | B1 |
| 7363371 | Kirkby et al. | Apr 2008 | B2 |
| 7363643 | Drake et al. | Apr 2008 | B2 |
| 7370120 | Kirsch et al. | May 2008 | B2 |
| 7376386 | Phillips et al. | May 2008 | B2 |
| 7379494 | Raleigh et al. | May 2008 | B2 |
| 7403618 | Van Rijnsoever et al. | Jul 2008 | B2 |
| 7434245 | Shiga et al. | Oct 2008 | B1 |
| 7457520 | Rossetti et al. | Nov 2008 | B2 |
| 7464179 | Hodges et al. | Dec 2008 | B2 |
| 7567565 | La Joie | Jul 2009 | B2 |
| 7574726 | Zhang et al. | Aug 2009 | B2 |
| 7577118 | Haumonte et al. | Aug 2009 | B2 |
| 7602820 | Helms et al. | Oct 2009 | B2 |
| 7603529 | MacHardy et al. | Oct 2009 | B1 |
| 7617516 | Huslak et al. | Nov 2009 | B2 |
| 7690020 | Lebar | Mar 2010 | B2 |
| 7720432 | Colby et al. | May 2010 | B1 |
| 7729940 | Harvey et al. | Jun 2010 | B2 |
| 7730509 | Boulet et al. | Jun 2010 | B2 |
| 7757251 | Gonder et al. | Jul 2010 | B2 |
| 7783316 | Mitchell | Aug 2010 | B1 |
| 7801803 | Forlai | Sep 2010 | B2 |
| 7836178 | Bedell et al. | Nov 2010 | B1 |
| 7930715 | Hendricks et al. | Apr 2011 | B2 |
| 7954131 | Cholas et al. | May 2011 | B2 |
| 8028322 | Riedl et al. | Sep 2011 | B2 |
| 8042131 | Flickinger | Oct 2011 | B2 |
| 8065703 | Wilson et al. | Nov 2011 | B2 |
| 8099757 | Riedl et al. | Jan 2012 | B2 |
| 8156520 | Casagrande et al. | Apr 2012 | B2 |
| 8170065 | Hasek et al. | May 2012 | B2 |
| 8205226 | Ko et al. | Jun 2012 | B2 |
| 8214256 | Riedl et al. | Jul 2012 | B2 |
| 8296185 | Isaac | Oct 2012 | B2 |
| 8347341 | Markley et al. | Jan 2013 | B2 |
| 8365212 | Orlowski | Jan 2013 | B1 |
| 8365213 | Orlowski | Jan 2013 | B1 |
| 8458125 | Chong, Jr. et al. | Jun 2013 | B1 |
| 8468099 | Headings et al. | Jun 2013 | B2 |
| 8516529 | Lajoie et al. | Aug 2013 | B2 |
| 8571931 | Riedl et al. | Oct 2013 | B2 |
| 8621501 | Matheny et al. | Dec 2013 | B2 |
| 8701138 | Stern et al. | Apr 2014 | B2 |
| 8713623 | Brooks | Apr 2014 | B2 |
| 8726303 | Ellis, III | May 2014 | B2 |
| 8769559 | Moon et al. | Jul 2014 | B2 |
| 8997136 | Brooks et al. | Mar 2015 | B2 |
| 9027062 | Patel et al. | May 2015 | B2 |
| 9215423 | Kimble et al. | Dec 2015 | B2 |
| 20010013123 | Freeman et al. | Aug 2001 | A1 |
| 20010030785 | Pangrac et al. | Oct 2001 | A1 |
| 20010050901 | Love et al. | Dec 2001 | A1 |
| 20020004912 | Fung | Jan 2002 | A1 |
| 20020019984 | Rakib | Feb 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020046404 | Mizutani | Apr 2002 | A1 |
| 20020049902 | Rhodes | Apr 2002 | A1 |
| 20020049980 | Hoang | Apr 2002 | A1 |
| 20020053082 | Weaver et al. | May 2002 | A1 |
| 20020054589 | Ethridge et al. | May 2002 | A1 |
| 20020059577 | Lu et al. | May 2002 | A1 |
| 20020059619 | Lebar | May 2002 | A1 |
| 20020063621 | Tseng et al. | May 2002 | A1 |
| 20020078441 | Drake et al. | Jun 2002 | A1 |
| 20020078444 | Krewin et al. | Jun 2002 | A1 |
| 20020087975 | Schlack | Jul 2002 | A1 |
| 20020087976 | Kaplan et al. | Jul 2002 | A1 |
| 20020095684 | St. John et al. | Jul 2002 | A1 |
| 20020100059 | Buehl et al. | Jul 2002 | A1 |
| 20020104083 | Hendricks et al. | Aug 2002 | A1 |
| 20020112240 | Bacso et al. | Aug 2002 | A1 |
| 20020120498 | Gordon et al. | Aug 2002 | A1 |
| 20020123928 | Eldering et al. | Sep 2002 | A1 |
| 20020124182 | Bacso et al. | Sep 2002 | A1 |
| 20020129378 | Cloonan et al. | Sep 2002 | A1 |
| 20020144262 | Plotnick et al. | Oct 2002 | A1 |
| 20020144263 | Eldering et al. | Oct 2002 | A1 |
| 20020147771 | Traversat et al. | Oct 2002 | A1 |
| 20020152299 | Traversat et al. | Oct 2002 | A1 |
| 20020154655 | Gummalla et al. | Oct 2002 | A1 |
| 20020162109 | Shteyn | Oct 2002 | A1 |
| 20020162115 | Bruckner et al. | Oct 2002 | A1 |
| 20020163928 | Rudnick et al. | Nov 2002 | A1 |
| 20020166119 | Cristofalo | Nov 2002 | A1 |
| 20020170057 | Barrett et al. | Nov 2002 | A1 |
| 20020178445 | Eldering et al. | Nov 2002 | A1 |
| 20020178447 | Plotnick et al. | Nov 2002 | A1 |
| 20020194595 | Miller et al. | Dec 2002 | A1 |
| 20020194607 | Connelly | Dec 2002 | A1 |
| 20020196939 | Unger et al. | Dec 2002 | A1 |
| 20030002862 | Rodriguez et al. | Jan 2003 | A1 |
| 20030004810 | Eldering | Jan 2003 | A1 |
| 20030005056 | Yamamoto et al. | Jan 2003 | A1 |
| 20030005453 | Rodriguez et al. | Jan 2003 | A1 |
| 20030005454 | Rodriguez et al. | Jan 2003 | A1 |
| 20030007516 | Abramov et al. | Jan 2003 | A1 |
| 20030021412 | Candelore et al. | Jan 2003 | A1 |
| 20030025832 | Swart et al. | Feb 2003 | A1 |
| 20030028884 | Swart et al. | Feb 2003 | A1 |
| 20030033199 | Coleman | Feb 2003 | A1 |
| 20030037068 | Thomas et al. | Feb 2003 | A1 |
| 20030046704 | Laksono et al. | Mar 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030061619 | Giammaressi | Mar 2003 | A1 |
| 20030074565 | Wasilewski et al. | Apr 2003 | A1 |
| 20030077067 | Wu et al. | Apr 2003 | A1 |
| 20030088876 | Mao et al. | May 2003 | A1 |
| 20030093311 | Knowlson | May 2003 | A1 |
| 20030093784 | Dimitrova et al. | May 2003 | A1 |
| 20030093792 | Labeeb et al. | May 2003 | A1 |
| 20030095791 | Barton et al. | May 2003 | A1 |
| 20030101449 | Bentolila et al. | May 2003 | A1 |
| 20030101451 | Bentolila et al. | May 2003 | A1 |
| 20030101454 | Ozer et al. | May 2003 | A1 |
| 20030110499 | Knudson et al. | Jun 2003 | A1 |
| 20030115612 | Mao et al. | Jun 2003 | A1 |
| 20030118014 | Iyer et al. | Jun 2003 | A1 |
| 20030135860 | Dureau | Jul 2003 | A1 |
| 20030139980 | Hamilton | Jul 2003 | A1 |
| 20030140351 | Hoarty et al. | Jul 2003 | A1 |
| 20030145323 | Hendricks et al. | Jul 2003 | A1 |
| 20030149975 | Eldering et al. | Aug 2003 | A1 |
| 20030161473 | Fransdonk | Aug 2003 | A1 |
| 20030172376 | Coffin | Sep 2003 | A1 |
| 20030179773 | Mocek et al. | Sep 2003 | A1 |
| 20030182261 | Patterson | Sep 2003 | A1 |
| 20030191826 | Bellinger et al. | Oct 2003 | A1 |
| 20030195927 | Virine et al. | Oct 2003 | A1 |
| 20030214962 | Allaye-Chan et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030229681 | Levitan | Dec 2003 | A1 |
| 20040006625 | Saha et al. | Jan 2004 | A1 |
| 20040013136 | Mailhot et al. | Jan 2004 | A1 |
| 20040031053 | Lim et al. | Feb 2004 | A1 |
| 20040045030 | Reynolds et al. | Mar 2004 | A1 |
| 20040078809 | Drazin | Apr 2004 | A1 |
| 20040103437 | Allegrezza et al. | May 2004 | A1 |
| 20040109672 | Kim et al. | Jun 2004 | A1 |
| 20040123313 | Koo et al. | Jun 2004 | A1 |
| 20040133467 | Siler | Jul 2004 | A1 |
| 20040133907 | Rodriguez et al. | Jul 2004 | A1 |
| 20040133917 | Schilling | Jul 2004 | A1 |
| 20040138909 | Mayer | Jul 2004 | A1 |
| 20040146006 | Jackson | Jul 2004 | A1 |
| 20040148625 | Eldering et al. | Jul 2004 | A1 |
| 20040163109 | Kang et al. | Aug 2004 | A1 |
| 20040179605 | Lane | Sep 2004 | A1 |
| 20040181800 | Rakib et al. | Sep 2004 | A1 |
| 20040181811 | Rakib | Sep 2004 | A1 |
| 20040186774 | Lee | Sep 2004 | A1 |
| 20040187150 | Gonder et al. | Sep 2004 | A1 |
| 20040187159 | Gaydos et al. | Sep 2004 | A1 |
| 20040193648 | Lai et al. | Sep 2004 | A1 |
| 20040193704 | Smith | Sep 2004 | A1 |
| 20040194134 | Gunatilake et al. | Sep 2004 | A1 |
| 20040199789 | Shaw et al. | Oct 2004 | A1 |
| 20040210936 | Rao et al. | Oct 2004 | A1 |
| 20040261114 | Addington et al. | Dec 2004 | A1 |
| 20040261116 | McKeown et al. | Dec 2004 | A1 |
| 20040267965 | Vasudevan et al. | Dec 2004 | A1 |
| 20050034171 | Benya | Feb 2005 | A1 |
| 20050034173 | Hatanaka | Feb 2005 | A1 |
| 20050039205 | Riedl | Feb 2005 | A1 |
| 20050039206 | Opdycke | Feb 2005 | A1 |
| 20050041679 | Weinstein et al. | Feb 2005 | A1 |
| 20050047596 | Suzuki | Mar 2005 | A1 |
| 20050050070 | Sheldon | Mar 2005 | A1 |
| 20050050160 | Upendran et al. | Mar 2005 | A1 |
| 20050055685 | Maynard et al. | Mar 2005 | A1 |
| 20050058115 | Levin et al. | Mar 2005 | A1 |
| 20050060742 | Riedl et al. | Mar 2005 | A1 |
| 20050060745 | Riedl et al. | Mar 2005 | A1 |
| 20050060758 | Park | Mar 2005 | A1 |
| 20050071669 | Medvinsky | Mar 2005 | A1 |
| 20050071882 | Rodriguez et al. | Mar 2005 | A1 |
| 20050086691 | Dudkiewicz et al. | Apr 2005 | A1 |
| 20050097598 | Pedlow et al. | May 2005 | A1 |
| 20050108529 | Juneau | May 2005 | A1 |
| 20050111844 | Compton et al. | May 2005 | A1 |
| 20050114141 | Grody | May 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050123001 | Craven et al. | Jun 2005 | A1 |
| 20050125528 | Burke et al. | Jun 2005 | A1 |
| 20050125832 | Jost et al. | Jun 2005 | A1 |
| 20050135476 | Gentric et al. | Jun 2005 | A1 |
| 20050160470 | Strauss | Jul 2005 | A1 |
| 20050168323 | Lenoir et al. | Aug 2005 | A1 |
| 20050198686 | Krause et al. | Sep 2005 | A1 |
| 20050210502 | Flickinger et al. | Sep 2005 | A1 |
| 20050223409 | Rautila et al. | Oct 2005 | A1 |
| 20050229209 | Hildebolt et al. | Oct 2005 | A1 |
| 20050234998 | Lesandrini et al. | Oct 2005 | A1 |
| 20050276284 | Krause et al. | Dec 2005 | A1 |
| 20050289588 | Kinnear | Dec 2005 | A1 |
| 20050289618 | Hardin | Dec 2005 | A1 |
| 20050289619 | Melby | Dec 2005 | A1 |
| 20060010075 | Wolf | Jan 2006 | A1 |
| 20060020984 | Ban et al. | Jan 2006 | A1 |
| 20060025148 | Karaoguz et al. | Feb 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060037060 | Simms et al. | Feb 2006 | A1 |
| 20060047957 | Helms et al. | Mar 2006 | A1 |
| 20060050784 | Lappalainen et al. | Mar 2006 | A1 |
| 20060059098 | Major et al. | Mar 2006 | A1 |
| 20060059342 | Medvinsky et al. | Mar 2006 | A1 |
| 20060062059 | Smith et al. | Mar 2006 | A1 |
| 20060064728 | Son et al. | Mar 2006 | A1 |
| 20060073843 | Aerrabotu et al. | Apr 2006 | A1 |
| 20060084417 | Melpignano et al. | Apr 2006 | A1 |
| 20060085824 | Bruck et al. | Apr 2006 | A1 |
| 20060088063 | Hartung et al. | Apr 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060133398 | Choi et al. | Jun 2006 | A1 |
| 20060133644 | Wells et al. | Jun 2006 | A1 |
| 20060171390 | La Joie | Aug 2006 | A1 |
| 20060171423 | Helms et al. | Aug 2006 | A1 |
| 20060190336 | Pisaris-Henderson et al. | Aug 2006 | A1 |
| 20060197828 | Zeng et al. | Sep 2006 | A1 |
| 20060218601 | Michel | Sep 2006 | A1 |
| 20060218604 | Riedl et al. | Sep 2006 | A1 |
| 20060236353 | Cheng et al. | Oct 2006 | A1 |
| 20060248553 | Mikkelson et al. | Nov 2006 | A1 |
| 20060248555 | Eldering | Nov 2006 | A1 |
| 20060253328 | Kohli et al. | Nov 2006 | A1 |
| 20060253584 | Dixon et al. | Nov 2006 | A1 |
| 20060253864 | Easty | Nov 2006 | A1 |
| 20060256376 | Hirooka | Nov 2006 | A1 |
| 20060271946 | Woundy et al. | Nov 2006 | A1 |
| 20060277569 | Smith | Dec 2006 | A1 |
| 20060288374 | Ferris et al. | Dec 2006 | A1 |
| 20060291506 | Cain | Dec 2006 | A1 |
| 20060294259 | Matefi et al. | Dec 2006 | A1 |
| 20070022459 | Gaebel, Jr. | Jan 2007 | A1 |
| 20070028260 | Williams et al. | Feb 2007 | A1 |
| 20070029379 | Peyer | Feb 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070047449 | Berger et al. | Mar 2007 | A1 |
| 20070053293 | McDonald et al. | Mar 2007 | A1 |
| 20070055985 | Schiller et al. | Mar 2007 | A1 |
| 20070061818 | Williams et al. | Mar 2007 | A1 |
| 20070074258 | Wood et al. | Mar 2007 | A1 |
| 20070076728 | Rieger et al. | Apr 2007 | A1 |
| 20070089127 | Flickinger et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070094692 | De Heer | Apr 2007 | A1 |
| 20070101157 | Faria | May 2007 | A1 |
| 20070101370 | Calderwood | May 2007 | A1 |
| 20070113243 | Brey | May 2007 | A1 |
| 20070118852 | Calderwood | May 2007 | A1 |
| 20070121569 | Fukui et al. | May 2007 | A1 |
| 20070121678 | Brooks et al. | May 2007 | A1 |
| 20070124781 | Casey et al. | May 2007 | A1 |
| 20070130581 | Del Sesto et al. | Jun 2007 | A1 |
| 20070150919 | Morishita | Jun 2007 | A1 |
| 20070153820 | Gould | Jul 2007 | A1 |
| 20070156539 | Yates | Jul 2007 | A1 |
| 20070157234 | Walker | Jul 2007 | A1 |
| 20070157242 | Cordray et al. | Jul 2007 | A1 |
| 20070162927 | Ramaswamy et al. | Jul 2007 | A1 |
| 20070192794 | Curtis et al. | Aug 2007 | A1 |
| 20070204300 | Markley et al. | Aug 2007 | A1 |
| 20070204310 | Hua et al. | Aug 2007 | A1 |
| 20070204311 | Hasek et al. | Aug 2007 | A1 |
| 20070204314 | Hasek et al. | Aug 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070233857 | Cheng et al. | Oct 2007 | A1 |
| 20070241176 | Epstein et al. | Oct 2007 | A1 |
| 20070244760 | Bodnar et al. | Oct 2007 | A1 |
| 20070250872 | Dua | Oct 2007 | A1 |
| 20070250880 | Hainline | Oct 2007 | A1 |
| 20070263653 | Hassan et al. | Nov 2007 | A1 |
| 20070271386 | Kurihara et al. | Nov 2007 | A1 |
| 20070274400 | Murai et al. | Nov 2007 | A1 |
| 20070276925 | La Joie et al. | Nov 2007 | A1 |
| 20070276926 | LaJoie et al. | Nov 2007 | A1 |
| 20080016526 | Asmussen | Jan 2008 | A1 |
| 20080022012 | Wang | Jan 2008 | A1 |
| 20080040768 | Robotham | Feb 2008 | A1 |
| 20080052157 | Kadambi et al. | Feb 2008 | A1 |
| 20080066112 | Bailey et al. | Mar 2008 | A1 |
| 20080092181 | Britt | Apr 2008 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080098446 | Seckin et al. | Apr 2008 | A1 |
| 20080101460 | Rodriguez | May 2008 | A1 |
| 20080103903 | Flake et al. | May 2008 | A1 |
| 20080109823 | Whitfield et al. | May 2008 | A1 |
| 20080109857 | Goodwill et al. | May 2008 | A1 |
| 20080115166 | Bhogal et al. | May 2008 | A1 |
| 20080134156 | Osminer et al. | Jun 2008 | A1 |
| 20080134165 | Anderson et al. | Jun 2008 | A1 |
| 20080141317 | Radloff et al. | Jun 2008 | A1 |
| 20080147497 | Tischer | Jun 2008 | A1 |
| 20080152116 | Sylvain | Jun 2008 | A1 |
| 20080152316 | Sylvain | Jun 2008 | A1 |
| 20080155059 | Hardin et al. | Jun 2008 | A1 |
| 20080177998 | Apsangi et al. | Jul 2008 | A1 |
| 20080192820 | Brooks et al. | Aug 2008 | A1 |
| 20080201748 | Hasek et al. | Aug 2008 | A1 |
| 20080229354 | Morris et al. | Sep 2008 | A1 |
| 20080235746 | Peters et al. | Sep 2008 | A1 |
| 20080244667 | Osborne | Oct 2008 | A1 |
| 20080263578 | Bayer et al. | Oct 2008 | A1 |
| 20080271068 | Ou et al. | Oct 2008 | A1 |
| 20080273591 | Brooks et al. | Nov 2008 | A1 |
| 20080313691 | Cholas et al. | Dec 2008 | A1 |
| 20090025027 | Craner | Jan 2009 | A1 |
| 20090028182 | Brooks et al. | Jan 2009 | A1 |
| 20090030802 | Plotnick et al. | Jan 2009 | A1 |
| 20090132346 | Duggal et al. | May 2009 | A1 |
| 20090162033 | Del Sordo | Jun 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090210899 | Lawrence-Apfelbaum et al. | Aug 2009 | A1 |
| 20090210912 | Cholas et al. | Aug 2009 | A1 |
| 20090254971 | Herz et al. | Oct 2009 | A1 |
| 20090320059 | Bolyukh | Dec 2009 | A1 |
| 20100057560 | Skudlark et al. | Mar 2010 | A1 |
| 20100058406 | Xu et al. | Mar 2010 | A1 |
| 20100115060 | Julia | May 2010 | A1 |
| 20100157928 | Spinar et al. | Jun 2010 | A1 |
| 20100161492 | Harvey et al. | Jun 2010 | A1 |
| 20100223491 | Ladd et al. | Sep 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100251305 | Kimble et al. | Sep 2010 | A1 |
| 20100262488 | Harrison et al. | Oct 2010 | A1 |
| 20100269131 | Newberry et al. | Oct 2010 | A1 |
| 20100313225 | Cholas et al. | Dec 2010 | A1 |
| 20110015989 | Tidwell et al. | Jan 2011 | A1 |
| 20110016479 | Tidwell et al. | Jan 2011 | A1 |
| 20110016482 | Tidwell et al. | Jan 2011 | A1 |
| 20110093900 | Patel et al. | Apr 2011 | A1 |
| 20110103374 | Lajoie et al. | May 2011 | A1 |
| 20110107364 | Lajoie et al. | May 2011 | A1 |
| 20110107379 | Lajoie et al. | May 2011 | A1 |
| 20110119703 | Schlack | May 2011 | A1 |
| 20110178880 | Karaoguz et al. | Jul 2011 | A1 |
| 20110231265 | Brown et al. | Sep 2011 | A1 |
| 20110307339 | Russell et al. | Dec 2011 | A1 |
| 20110317977 | Harris | Dec 2011 | A1 |
| 20120011269 | Krikorian et al. | Jan 2012 | A1 |
| 20120023522 | Anderson et al. | Jan 2012 | A1 |
| 20120042331 | Wolf, Sr. | Feb 2012 | A1 |
| 20120084813 | Dmitriev et al. | Apr 2012 | A1 |
| 20120110620 | Kilar et al. | May 2012 | A1 |
| 20120159539 | Berberet et al. | Jun 2012 | A1 |
| 20120224834 | Chen et al. | Sep 2012 | A1 |
| 20120278841 | Hasek et al. | Nov 2012 | A1 |
| 20130133009 | Bhogal et al. | May 2013 | A1 |
| 20130227608 | Evans et al. | Aug 2013 | A1 |
| 20130290556 | Giladi | Oct 2013 | A1 |
| 20130325870 | Rouse et al. | Dec 2013 | A1 |
| 20130330063 | Bonovich et al. | Dec 2013 | A1 |
| 20140020017 | Stern et al. | Jan 2014 | A1 |
| 20140157313 | Shartzer et al. | Jun 2014 | A1 |
| 20140164760 | Hybertson | Jun 2014 | A1 |
| 20140208349 | Nair | Jul 2014 | A1 |
| 20140282777 | Gonder et al. | Sep 2014 | A1 |
| 20170164378 | Gunasekara | Jun 2017 | A1 |
| 20170164416 | Yeddala et al. | Jun 2017 | A1 |
| 20180014041 | Chen et al. | Jan 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2643806 | Jun 2013 | CA |
| WO-0110125 | Feb 2001 | WO |
| WO-0191474 | Nov 2001 | WO |
| WO-2004008693 | Jan 2004 | WO |
| WO-2007136399 | Nov 2007 | WO |
| WO-2008016786 | Feb 2008 | WO |
| Entry |
|---|
| Cisco Intelligent Network Architecture for Digital Video--SCTE Cable-Tec Expo 2004 information page, Orange County Convention Center, Jun. 2004, 24 pages. |
| Deering et al., Internet Protocol, Version 6 (lpv6) Specification, IETF RFC 2460 (Dec. 1998). |
| “DOCSIS 3.0 Management Features Differences Technical Report” CM-TR-MGMT V3.0-DEGG-V01-071228. |
| “DOCSIS 3.0 OSSI Configuration Management Technical Report” CM-TR-OSSIv3.0-CM-VO1-080926. |
| Griffith, et al.,Resource Planning and Bandwidth Allocation in Hybrid Fiber-Coax Residential Networks, National Institute of Standards and Technology (NIST), 10 pages, no date. |
| Inter alia, Section 6.5 of SCTE Standard SCTE 35 2016. |
| Internet Protocol DARPA Internet Program Protocol Specification, IETF RFC 791 (Sep. 1981). |
| Kanouff, Communications Technology: Next-Generation Bandwidth Management—The Evolution of the Anything-to-Anywhere Network, 8 pages, Apr. 1, 2004. |
| Motorola DOCSIS Cable Module DCM 2000 specifications, 4 pages, no date. |
| OpenVision Session Resource Manager—Open Standards-Based Solution Optimizes Network Resources by Dynamically Assigning Bandwidth in the Delivery of Digital Services article, 2 pages, (copyright 2006), (http://www.imake.com/hopenvision). |
| OpenVision Session Resource Manager features and information, 2 pages, no date, (http://www.imake.com/hopenvision). |
| Number | Date | Country | |
|---|---|---|---|
| 20180131975 A1 | May 2018 | US |
