Patent Grant
10863238
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.
1. Field of Invention
The present invention relates generally to the field of network service and content delivery and utilization, and specifically in one aspect to delivering such services and content to particular subsets or groupings within the user base of a content distribution network.
2. Description of Related Technology
In the context of network services, it is often highly desirable to provide users of the network with ready and instant access to a variety of different types of content, accessible at different locations, and on different platforms. In many cases, it is also desirable to provide the same user 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, hybrid fiber-copper (HFCu), and other content distribution networks, as well as Internet content providers, also derive income from the sale of advertising time and insertion opportunities (or “impressions”).
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 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 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).
Hence, 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.
In a typical U.S. cable or terrestrial content distribution system, downstream RF channels used for transmission each occupy a 6 MHz spectral slot in the available bandwidth (between approximately 54 MHz and 870 MHz). Established analog and digital cable television services including standard definition (SD) broadcasts utilize this spectrum. The spectrum is also shared with the deployment of next-generation services such as video on-demand (VOD), high definition (HD) broadcast/simulcast services, personal video recorder (PVR), and digital video recorder (DVR) services, as well as high-speed data (HSD). For this reason, the exact RF (physical) channel used for a given service may differ from plant to plant. However, within a given cable plant, all homes that are electrically connected to the same cable feed running through a neighborhood will receive the same downstream signal. For the purpose of managing services, these homes are grouped into logical aggregations or clusters typically called “service groups”. Homes belonging to the same service group generally receive their services (e.g., broadcast or VOD service) on the same set of RF channels.
In current cable systems, a correct advertising zone may be determined for a legacy STB through use of a Service Group ID (Service_Group_id). Specifically, when the STB boots up, it learns its Service_Group_id from the edge QAM (eQAM) from which it receives video (each such eQAM is manually configured to be associated with a Service_Group_id). When the VOD client on the STB requests a primary content element (e.g. video), the Service_Group_id is contained in the requesting message. The application server receives the message, extracts the Service_Group_id, performs a lookup to determine which advertising zone is associated with that Service_Group_id, and then instructs the VOD server to serve the appropriate version of the requested video which contains the secondary content associated with the STB's advertising zone.
This architecture, however, is generally not optimal for the delivery of targeted content based on e.g., geographic or logical boundaries, since inter alia the level of targeting granularity that can be achieved is very low (i.e., there is a lack of precision in determining who receives what). Geographic boundaries (or zones) are not precise, and often do not overlap well with the network distribution configuration—a service group may in fact straddle two or more geographic regions of interest (e.g., zip codes, metropolitan markets, etc). Accordingly, it is often impossible for network operator to draw precise lines of demarcation between different subsets or groups of its viewers. As a simple case, consider where an operator wishes to deliver particular content to all of the residents of Town X. Depending on where Town X is situated in proximity to its neighbors, its residents may be served by multiple different distribution nodes or hubs of a cable system. Or, certain portions of the Town may be serviced by one system operator and other portions by another. This can lead to very crude and imprecise delivery of content, with a potentially significant rate of error (error here being defined as instances where content should have been delivered to a particular premises but wasn't, or alternatively should not have been delivered but was).
Further, this architecture (as well as other prior art architectures enabling distribution of content to devices outside the traditional home network) is not optimal for the delivery of targeted content to devices capable of utilizing the now-ubiquitous Internet Protocol (so called “IP devices”). Under the prior art, video destined for an IP device would be served to that device by a web or Internet video streamer such as Real Network's Helix™ Server, Microsoft® SilverLight™, or Adobe® video server. These servers comprise separate entities from the VOD servers that are used to serve on-demand content to non-IP devices, referred to herein as “legacy devices” (e.g., set-top boxes). Thus, according to the prior art, in order to serve content having the same inserted advertisements to both IP and legacy devices, various operationally “painful” (aka complex) mechanisms are required for maintaining two advertisement insertion systems, two video server systems, and in some cases two advertisement campaign managers, each of the foregoing serving either the legacy devices or the non-legacy (e.g., IP) devices, yet being synchronized to ensure that the same advertisements are inserted for viewing on the separate platforms. As one may imagine, this approach is costly, time consuming, and prone to error.
Moreover, the MSO, content source (e.g., studio), and/or advertiser may wish to apply other rules to secondary content selection and insertion (i.e., in addition to or in place of the aforementioned zone preservation). For instance, an MSO might want to give its subscriber the ability to tailor the secondary content it receives based on e.g., the subscriber's preferences, the subscriber's location, etc. Current secondary content selection and insertion paradigms are substantially limited in this regard, being based on Service_Group_id or the like as previously described.
Hence, apparatus and methods for providing primary content having secondary content inserted therein which is targeted to individual ones of a plurality of users such as based on geographic or other logical boundaries (or alternatively the context or other attributes of the primary content) are desired. Ideally, these apparatus and methods would provide linear and non-linear content to non-legacy video-consuming devices (including personal computers (PCs), digital set-top boxes (DSTBs), portable media devices (PMDs), etc.) with the advertisements appropriate to the consumer's advertisement zone embedded therein. The apparatus and methods would thereby enable the user of the devices to see the same advertisement that he/she would see if that user had requested to view the same programming on his/her legacy device, or alternatively see other secondary content according to a prescribed rule set or preference selected by the subscriber, MSO, content source, or even the advertiser. Secondary content insertion methods and apparatus which targets the user, the device, and/or is related to the context of the primary content, would also ideally be provided such that it could be meshed with preservation of the desired advertising “zone” (or imposition of the alternative rule set or preferences) in a cohesive fashion.
The present invention satisfies the foregoing needs by providing improved apparatus and methods for zone-preserved secondary content delivery such as may be used in a content distribution (e.g., cable, HFCu or satellite) network.
In a first aspect of the invention, a method of ensuring delivery of program content and advertising content is disclosed. In one embodiment, the program content is delivered “on-demand” from a content delivery network to an Internet Protocol (IP)-capable user device, the advertising being selected based at least in part on an advertisement zone of a user of the IP-capable user device, and the method comprises: receiving a request for the program content from the IP capable user device, the request comprising at least a user identifier (UID); forwarding the UID to an entity of the network, the entity determining at least a Media Access Control (MAC) address of the IP capable user device from the UID; receiving from the entity the MAC address; forwarding the MAC address to a network controller of the network, the network controller determining at least a quadrature amplitude modulation (QAM) identifier using the MAC address; receiving from the network controller the QAM identifier; associating the QAM identifier to the advertisement zone; and providing information regarding the advertisement zone to a content server of the network, the content server providing the program and the advertising content to the IP capable user device.
In one variant, the user of the IP-capable user device is able to receive the same advertising content that the user would receive if the request had originated from a non-IP device associated to the user.
In a second aspect of the invention, a method for use in a content delivery network is disclosed. In one embodiment, the content delivery network is capable of providing program and advertising content to a plurality of legacy and non-legacy devices, and the method ensures delivery of zone-preserved advertising content. The method of this embodiment comprises: receiving a request for program content from a non-legacy device, the device being associated with a user, the request comprising at least information identifying the user; forwarding the information identifying the user to at least one entity of the network, the entity being configured to associate the information to an address of the user; receiving an indicator of the address from the at least one entity; associating the indicator to at least one advertising zone; and providing information regarding the at least one advertising zone to a content server of the network, the content server being configured to provide the program and the advertising content to the legacy and non-legacy devices. The advertising content received at the non-legacy device comprises the same content which would have been received by the user at a legacy device.
In a third aspect of the invention, a server apparatus is disclosed. In one embodiment, the apparatus is for use in a content distribution network comprising at least a content server and a plurality of user devices capable of receiving primary and secondary content therefrom, and comprises a secondary content zone preservation server apparatus. In one variant, the apparatus comprises a first interface configured to receive a request from at least one of the plurality of user devices, the request comprising at least user identification information; a storage entity configured to store a plurality of records thereon, the records indicating at least one secondary content zone applicable to individual ones of a plurality of device indicators; a digital processor, the processor configured to run at least one computer program thereon, the computer program comprising a plurality of instructions which are configured to determine at least one secondary content zone by: forwarding the user identification information to a network entity capable of providing a device indicator; receiving the device indicator; and comparing the device indicator to the plurality of records to identify at least one secondary content zone associated therewith; and a second interface configured to provide data related to the at least one secondary content zone to the content server.
In a fourth aspect of the invention, a method of delivering primary and secondary content over a network is disclosed. In one embodiment, the method comprises: receiving a request for the primary content from a packet-enabled user device; receiving entitlement information relating to a subscriber making the request; using the entitlement information to associate the subscriber to a subscriber account, the account indicating the subscriber is authorized to receive the requested primary content; and delivering the primary content to the subscriber in a packetized format via the packet-enabled device, the primary content having secondary content contained therein which is zone-controlled with respect to delivery of the primary content via another non-packet enabled device of the subscriber.
In a fifth aspect of the invention, a method of operating a network is disclosed. In one embodiment, the method comprises: receiving a user preference regarding advertising; creating a rule based on the preference; and implementing the rule with respect to requests for primary content that are received via one or more IP-enabled devices of the user that are located at a location different than the user's premises.
In a sixth aspect of the invention, a method of operating a network is disclosed. In one embodiment, the method comprises: receiving a request for primary content from an IP-enabled device of a user of the network; determining a first location of the device; and selecting and inserting secondary content that have one or more common attributes to secondary content that would be selected and inserted if the request were received from a non-IP enabled device of the user at a location different from the first location.
In a seventh aspect of the invention, network apparatus is disclosed. In one embodiment, the apparatus comprises: a processor; a storage device in data communication with the processor; and at least one computer program capable of being run on the processor and being stored in the storage device. The at least one program is capable of, when executed: receiving a request for primary content originated from a user; and if the request originated from a legacy device of the user, determining an advertising zone associated with that legacy device; or if the request originated from an IP-enabled non-legacy device of the user, applying the same rules for advertising selection or insertion that are applied for the advertising zone associated with the legacy device.
In an eighth aspect of the invention, a system is disclosed. In one embodiment, the system comprises a zone control and preservation server, a VOD server, and an entitlements server.
In a ninth aspect of the invention, a computer-readable apparatus is disclosed. In one embodiment, the apparatus comprises a medium having one or more computer programs stored thereon, the one or more programs being configured to implement advertising zone control and/or preservation within a content delivery network.
In a tenth aspect, a method of operating a network is disclosed. In one embodiment, the method comprises: receiving a preference regarding advertising; creating a rule based on the preference; and causing the rule to be implemented with respect to requests for primary content that are received via one or more IP-enabled devices associated to a user that are located at a location different than a location of a premises of the user.
In an eleventh aspect, an apparatus configured to operate in a network is disclosed. In one embodiment, the apparatus comprises: an interface in communication with a mobile user device; a storage apparatus; and a processor configured to execute at least one computer program thereon, the computer program comprising a plurality of instructions configured to, when executed: (i) receive a request for primary content from a mobile user device; (ii) identify a user associated to the mobile user device; (iii) identify a zone associated to the user; (iv) cause one or more of a plurality of secondary content elements to be inserted into the requested primary content for delivery to the mobile user device based at least in part on a rule for the insertion thereof. The rule comprises selection of the one or more secondary content elements selected from among the plurality based at least in part on: a correspondence of the one or more secondary content elements to the identified zone associated to the user; and a time-based qualification associated to the one or more secondary content elements.
In a twelfth aspect, a network apparatus is disclosed. In one embodiment, the network apparatus comprises: a processor; a storage device in data communication with the processor: and at least one computer program configured to run on the processor and stored in the storage device, the at least one program comprising a plurality of instructions configured to, when executed: (i) receive a request for primary content originated from a user, the request comprising at least an address, and the primary content comprising a plurality of content segments; (ii) identify individual ones of a plurality of secondary content based on a secondary content zone of the user; and (iii) cause individual ones of the plurality of content segments of the primary content to have the individual ones of the plurality of secondary content inserted therebetween. The plurality of instructions are further configured to: when the request originated from a legacy device of the user, base said secondary content zone on the address associated with the legacy device; and when the request originated from an IP-enabled non-legacy device of the user, utilize a secondary content zone associated with the legacy device.
In a thirteenth aspect, a network server apparatus is disclosed. In one embodiment, the zone preservation server apparatus comprises: a first interface configured to receive a request from at least one of the plurality of user devices associated with the network, the request comprising at least user identification information; a storage entity configured to store a plurality of records thereon, the plurality of records configured to indicate at least one secondary content zone applicable to individual ones of a plurality of device indicators; a digital processor, the processor configured to run at least one computer program thereon, the computer program comprising a plurality of instructions configured to, when executed: (i) forward the user identification information to a network entity configured to provide a device indicator; (ii) receive the device indicator; and (iii) compare the device indicator to the plurality of records to identify at least one secondary content zone associated therewith; and a second interface configured to pass data related to the at least one secondary content zone to a content server, the content server configured to provide content to at least the at least one user device.
Other features and advantages of the present invention 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.
Reference is now made to the drawings wherein like numerals refer to like parts throughout.
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 terms “client device” and “user device” include, but are not limited to, personal computers (PCs) and minicomputers, whether desktop, laptop, or otherwise, set-top boxes (e.g., DSTBs), mobile devices such as personal digital assistants (PDAs), handheld computers, personal communicators, cellular telephones, wireless nodes (e.g., WiFi APs or STAs), or literally any other device capable of interchanging data with a network, as well as personal media devices (PMDs), and smartphones.
As used herein, the term “codec” refers to an video, audio, or other data coding and/or decoding algorithm, process or apparatus including, without limitation, those of the MPEG (e.g., MPEG-1, MPEG-2, MPEG-4/H.264, etc.), Real (RealVideo, etc.), AC-3 (audio), DiVX, XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, 9, 10, 11), ATI Video codec, or VC-1 (SMPTE standard 421M) families.
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, 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), and the like.
The terms “Customer Premises Equipment (CPE)” and “host device” refer to any type of electronic equipment located within a customer's or user's premises and connected to a network. The term “host device” refers generally and without limitation to a terminal device that has access to digital television content via a satellite, cable, or terrestrial network. The host device functionality may be integrated into a digital television (DTV) set or other type of consumer electronic device (e.g., BluRay player). The term “customer premises equipment” (CPE) includes electronic equipment such as for example set-top boxes (e.g., DSTBs), televisions, cable or other modems, HFCu receivers, embedded multimedia terminal adapters (eMTAs), whether stand-alone or integrated with other devices, Digital Video Recorders (DVR), gateways/storage devices (Furnace), and ITV Personal Computers.
As used herein, the term “display” means any type of device adapted to display information, including without limitation CRTs, LCDs, TFTs, plasma displays, LEDs, incandescent and fluorescent devices. Display devices may also include less dynamic devices such as, for example, printers, e-ink devices, and the like.
As used herein, the term “DVR” (digital video recorder) refers generally to any type or recording mechanism and/or software environment whereby content sent over a network can be recorded and selectively recalled. Such DVR may be dedicated in nature, or part of a non-dedicated or multi-function system and/or may be “virtual” or network-based rather than located at any customer premises.
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 and 3.0.
As used herein, the term “headend” refers generally to a networked system controlled by an operator (e.g., an MSO) that distributes programming to MSO clientele using client devices. Such programming may include literally any information source/receiver including, inter alia, free-to-air TV channels, pay TV channels, on-demand/PPV, interactive TV, and the Internet.
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 term “memory” includes any type of integrated circuit or other storage device adapted for storing digital data including, without limitation, ROM. PROM, EEPROM, DRAM, SDRAM, DDR/2 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), and PSRAM.
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 (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable compute fabrics (RCFs), array processors, secure microprocessors, 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 without limitation 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 teens “network” and “bearer network” refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) or hybrid fiber copper (HFCu) 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, PHY, 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., USB 2.0, 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.11a, b, g, n), WiMAX (802.16), PAN (802.15), or IrDA families.
As used herein, the term “QAM” refers to modulation schemes used for sending signals over cable networks. Such modulation scheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM, 256-QAM, etc.) depending on details of a cable network. A QAM may also refer to a physical channel modulated according to one or more of the schemes.
As used herein, the term “server” refers to 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 “service group” refers to either a group of service users (e.g. subscribers) or the resources shared by them in the form of entire cable RF signals, only the RF channels used to receive the service or otherwise treated as a single logical unit by the network for resource assignment.
As used herein, the term “storage device” refers to without limitation computer hard drives, DVR device, memory, RAID devices or arrays, optical media (e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), flash drives or cards (e.g., USB or Compact Flash), or any other devices or media capable of storing content or other information.
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.11a/b/g/n/v.
As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth, 3G, HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, narrowband/FDMA, OFDM, PCS/DCS, FLO (i.e., forward-link only systems such as Qualcomm MediaFLO), analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
As used herein, the term “zone” refers to, without limitation, any actual, geographic, logical, or virtual zone or implementation rule as specified by one or more criteria. For example, a geographic zone may be specified by one or more postal zip codes, telephone area codes/exchanges, or the like. Alternatively, a logical zone or rule may be specified by membership in an organization, subscription to a particular service, or the like.
Overview
The present invention discloses, inter alia, methods and apparatus for selectively providing targeted 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 3G/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 of the invention, 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 VOD server or 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.
The exemplary apparatus for making the aforementioned association may utilize the advertisement zone identifier (or service group identifier) to direct the delivery of primary and secondary content. For example, if on-demand content is requested by an IP-enabled client device, signals are sent to the VOD server (or web server) which indicate which secondary content (e.g., advertisements) should be placed in the primary content prior to delivery to the user, based on a determination of the zone associated with the user of the device.
Alternatively, in another embodiment of the invention, the zone may purposely be not preserved, but rather implemented according to one or more prescribed or dynamically determined rules which determine appropriate alternate secondary content based on e.g., a user, device, and/or primary content context. These rules may be determined by, inter alia, (i) the advertiser or a designated campaign manager or entity; (ii) the primary content source; (iii) the MSO or other network operator; and/or (iv) the receiving subscriber themselves. Relationships between the zones or contexts may also be applied, such as where advertising for use with content requested by an IP-enabled device “off network” maintains a common theme or attribute with that delivered with the same content “on-net”, yet is not identical.
The present invention advantageously overcomes several disabilities of the prior art including the requirement for intricate, separate, and yet coordinated systems for providing targeted secondary content delivery to subscribers across the same or multiple different networks and types of devices (e.g., legacy and non-legacy devices), as well as the ability to selectively apply customized secondary content rule sets based on the context of a user, their device, and/or the primary content with which the secondary content is associated.
Additional secondary content targeting and insertion methods are also described, wherein the relationship between two ostensibly requesting devices (e.g., legacy DSTB and IP-enabled device) is leveraged for selection of secondary content as part of an advertising campaign management strategy.
An improved network server and CPE capable of implementing the aforementioned zone enforcement and targeting methodologies is also described, as well as mechanisms to implement operational and/or business rules during system operation.
Exemplary embodiments of the apparatus and methods of the present invention are now described in detail. While these exemplary embodiments are described in the context of the aforementioned hybrid fiber coax (HFC) cable system or satellite network architecture having multiple systems operator (MSO), digital networking capability, IP delivery capability, and plurality of client devices/CPE, the general principles and advantages of the invention may be extended to other types of networks and architectures, whether broadband, narrowband, wired or wireless, or otherwise, the following therefore being merely exemplary in nature. For instance, the invention may be adapted for use on so-called hybrid fiber copper (HFCu) networks, or WiMAX (IEEE Std. 802.16) wireless networks.
It will also be appreciated that while aspects of the invention are described generally in the context of a consumer (i.e., home) end user domain or premises, the invention may be readily adapted to other types of environments (e.g., commercial/enterprise, government/military, university/educational, healthcare facility, etc.) as well. Myriad other applications are possible.
It is further noted that while described primarily in the context of a cable system with 6 MHz QAM-modulated RF channels, the present invention is applicable to literally any network topology or paradigm, and any frequency/bandwidth or modulation type, such as for example 8 MHz channels. Furthermore, as referenced above, the invention is in no way limited to traditional cable system frequencies (i.e., below 1 GHz), and in fact may be used with systems that operate above 1 GHz band in center frequency or bandwidth, to include without limitation so-called ultra-wideband systems.
Also, while certain aspects are described primarily in the context of the well-known IP or Internet Protocol (described in, inter alia, RFC 791 and 2460), it will be appreciated that the present invention may utilize other types of network and other protocols (and in fact bearer networks to include other internets and intranets) to implement the described functionality.
Moreover, while many aspects of the invention are described within the context of traditional linear broadcast or “on demand” services provided over e.g., a cable, satellite, of HFCu network, it will be appreciated that the concepts and apparatus described herein are readily extensible to other content delivery paradigms which provide content, including without limitation: (i) “pay per view”; and (ii) selection of a video for play via the Internet, such as via the “YouTube®” or other similar website.
Other features and advantages of the present invention 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.
Network—
The data/application origination point 102 comprises any medium that allows data and/or applications (such as a VOD-based or “Watch TV” application) to be transferred to a distribution server 104. This can include for example a third party data source, application vendor website, CD-ROM, external network interface, mass storage device (e.g., RAID system), etc. Such transference may be automatic, initiated upon the occurrence of one or more specified events (such as the receipt of a request packet or ACK), performed manually, or accomplished in any number of other modes readily recognized by those of ordinary skill.
The application distribution server 104 comprises a computer system where such applications can enter the network system. Distribution servers are well known in the networking arts, and accordingly not described further herein.
The VOD server 105 comprises a computer system where on-demand content can be received from one or more of the aforementioned data sources 102 and enter the network system. These servers may generate the content locally, or alternatively act as a gateway or intermediary from a distant source.
The CPE 106 includes any equipment in the “customers' premises” (or other locations, whether local or remote to the distribution server 104) that can be accessed by a distribution server 104.
Referring now to
The network headend 150 of the architecture of
As shown in
It will also be recognized, however, that the multiplexing operation(s) need not necessarily occur at the headend 150 (e.g., in the aforementioned MEM 162). For example, in one variant, at least a portion of the multiplexing is conducted at a BSA switching node or hub (see discussion 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 CPE 106 may use the out-of-band (OOB) or DOCSIS channels and associated protocols. The OCAP 1.0, 2.0, 3.0 (and subsequent) specification provides for exemplary networking protocols both downstream and upstream, although the invention is in no way limited to these approaches.
The network headend 150 may further comprise a plurality of additional components and services omitted from
“Switched” Networks—
Switching architectures allow improved efficiency of bandwidth use for ordinary digital broadcast programs. Ideally, the subscriber is unaware of any difference between programs delivered using a switched network and ordinary streaming broadcast delivery.
In the present context, a switched network architecture can be used to deliver linear (e.g., broadcast) content, which may also have its advertising or other “zones” preserved (or subject to a prescribed rules set) as previously discussed.
Co-owned and co-pending U.S. patent application Ser. No. 09/956,688 filed Sep. 20, 2001 and entitled “TECHNIQUE FOR EFFECTIVELY PROVIDING PROGRAM MATERIAL IN A CABLE TELEVISION SYSTEM”, incorporated herein by reference in its entirety, describes one exemplary broadcast switched digital architecture useful with the present invention, although it will be recognized by those of ordinary skill that other approaches and architectures may be substituted.
In addition to “broadcast” content (e.g., video programming), the systems of
Referring again to
The edge switch 194 forwards the packets receive from the CMTS 199 to the QAM modulator 189, which transmits the packets on one or more physical (QAM-modulated RF) channels to the CPE. The IP packets are typically transmitted on RF channels that are different that the RF channels used for the broadcast video and audio programming, although this is not a requirement. The 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.
“Packetized” Networks—
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 present invention, a “packet optimized” delivery network is used for carriage of the packet content (e.g., IPTV content).
Zone-Controlled Secondary Content Delivery Architecture—
As will be discussed in greater detail below, various user devices may be configured to receive the primary and secondary content according to the present invention. These devices include e.g., consumer premises equipment (CPE) 106 such as DSTBs, personal computers (PC) 212, converged premises devices (CPD) 210 discussed below, portable media devices (PMD) 208 such as personal MP3 players, 3G/4G smartphones, etc. It is noted that while particular embodiments using individual ones of these devices may require different components, delivery methods, etc., the present invention is intended to include delivery to each of these types of device; hence, the aforementioned devices (as well as other devices capable of receiving content from the aforementioned networks) will herein collectively be referred to as “user device(s)”. An exemplary user device is discussed below with respect to
Although illustrated as providing primary content from an on-demand server 105, it is appreciated that the apparatus and methods of the invention may be further utilized to provide other types or forms of primary content. For example, so called “quick clips” content (described in co-owned U.S. Pat. No. 7,174,126 issued Feb. 6, 2007 and entitled “TECHNIQUE FOR EFFECTIVELY ACCESSING PROGRAMMING LISTING INFORMATION IN AN ENTERTAINMENT DELIVERY SYSTEM” incorporated herein by reference in its entirety), so-called “start-over” content (described in co-owned, co-pending U.S. Patent Publication No. 2005/0034171 entitled “TECHNIQUE FOR DELIVERING PROGRAMMING CONTENT BASED ON A MODIFIED NETWORK PERSONAL VIDEO RECORDER SERVICE” incorporated herein by reference in its entirety), so-called “lookback” content (as described in co-owned, co-pending U.S. patent application Ser. No. 10/913,064 filed Aug. 6, 2004 and entitled “TECHNIQUE FOR DELIVERING PROGRAMMING CONTENT BASED ON A MODIFIED NETWORK PERSONAL VIDEO RECORDER SERVICE” incorporated herein by reference in its entirety), and/or so-called “remote DVR” content (as discussed in co-owned U.S. Pat. No. 7,457,520 issued Nov. 25, 2008 and entitled “TECHNIQUE FOR PROVIDING A VIRTUAL DIGITAL VIDEO RECORDER SERVICE THROUGH A COMMUNICATIONS NETWORK” incorporated herein by reference in its entirety) may be provided. Other types of content may also be utilized consistent with the invention as well, including traditional linear broadcast content.
As illustrated in
In one embodiment, the AS 104 comprises an application server of the type discussed in co-owned, co-pending U.S. patent application Ser. No. 11/263,015 filed Oct. 2, 2002 and entitled “NETWORK BASED DIGITAL INFORMATION AND ENTERTAINMENT STORAGE AND DELIVERY SYSTEM”, incorporated herein by reference in its entirety. In one variant, the AS 104 is a Mystro™ server device of the type utilized by the Assignee hereof, although it will be appreciated that other configurations may be utilized with equal success. The Mystro Application server is configured to receive a request for content from the user device and extract therefrom the service group identifier (Service_Group_id). The Mystro server may then look up the zone associated with the service group identifier as discussed herein.
The AS 104 monitors and records the content reserved and viewed by a user, and thus can be used to vary secondary content inserted therein prior to distributing a program to the user devices, e.g., CPE 106, PMD 208, PC 212, etc. Hence, the AS 104 may assist in providing zone-preserved secondary content, and may further be useful in additional targeting of secondary content (as will be discussed below).
Various methods are known in the art for providing secondary content insertion. For example, in one variant, the methods and apparatus discussed in co-owned, co-pending U.S. patent application Ser. No. 12/766,433 filed on Apr. 23, 2010 and entitled “APPARATUS AND METHODS FOR DYNAMIC SECONDARY CONTENT AND DATA INSERTION AND DELIVERY”, which is incorporated herein by reference in its entirety, may be utilized in conjunction with the present invention. As discussed therein, a network operator's on-demand product portfolio (e.g., single selection/purchase VOD, SVOD, FVOD, etc.) is leveraged as a platform for the insertion of multiple different types of targeted secondary content (including for example zone-preserved secondary content), offered as placement opportunities to prospective or existing advertisers. In one variant, a replacement model is given whereby one or more segments of secondary content are used to replace one or more segments of secondary content currently resident within a primary content element. For example, the segments may be replaced “one-for-one”, “one-for-N”, or “N-for-one”. In another variant, a fill model may be used to insert secondary content into primary content which does not otherwise have secondary content inserted therein, and/or may be used to increase the frequency of inserted secondary content therein. Lastly, an additive model may be used to insert secondary content in a non-disruptive fashion into primary content which does not otherwise have secondary content inserted therein, and/or non-disruptively increase the frequency of inserted secondary content. In one example, the fill model may insert secondary content according to user-initiated interruptions, thereby appearing non-disruptive to the viewer.
In another embodiment, secondary (e.g., advertising) content may be inserted using the methods and apparatus discussed in co-owned, co-pending U.S. patent application Ser. No. 11/974,700 filed on Oct. 15, 2009 and entitled “METHODS AND APPARATUS FOR REVENUE-OPTIMIZED DELIVERY OF CONTENT IN A NETWORK”, which is incorporated herein by reference in its entirety. As discussed therein, when a user device tunes to a specific program, it may have one or more specific revenue implications to the network operator. In one example, the device may be associated with a subscriber that the operator has identified as a target customer for personal advertisement. The network operator can maximize or optimize revenue by e.g., using an advertising “splicer” in conjunction with a network device such as a server (e.g., a VoD server). In one exemplary embodiment, the splicer entity is located at the VOD or other content server, thereby requiring the acquisition of only one stream. The splicer splices targeted advertising content into a stream delivered to that user; this “micro-zoned” output may be constructed at time of program stream configuration. Hence using the VOD server as a splicer/stream generator for multicast feeds may assist in providing a highly economical hardware model for the implementation of BSA microcasting. However, a “dedicated” splicer approach may also be used for the repurposing VOD assets to provide a less complex and more elegant solution which reduces real-time acquisition (RTA) costs significantly.
The splicer in the above embodiment may be of the type discussed in co-pending and co-owned U.S. patent application Ser. No. 10/662,776 filed Sep. 15, 2003 entitled “SYSTEM AND METHOD FOR ADVERTISEMENT DELIVERY WITHIN A VIDEO TIME SHIFTING ARCHITECTURE” (published as patent publication No. 20050060745 on Mar. 17, 2005), which is incorporated by reference herein in its entirety. Exemplary advertising insertion and splicer apparatus and methods are discussed therein in the context of, e.g., networked digital video recorder (NDVR) or VoD delivery paradigms.
The ZCPS 200 of
The VOD server 105 may further receive instruction regarding secondary content insertion from e.g., a campaign manager (not shown) such as that discussed in co-owned, U.S. patent application Ser. No. 12/503,772 filed on Jul. 15, 2009, issued as U.S. Pat. No. 8,935,721 on Jan. 13, 2015, and entitled “Methods and Apparatus for Classifying an Audience in a Content Distribution Network”, which is incorporated herein by reference in its entirety. As discussed therein, data relating to audience or viewer qualities is identified, created and distributed to an advertisement management system and an advertisement decision maker. An advertising “inventory” is created and related to audiences by combining the audience data with advertisement placement opportunities. The advertising inventory is managed via e.g., a network-based management system including a campaign manager. The apparatus and methods discussed are further adapted to manage advertising campaigns for one or more advertisement/promotional providers in order to, for example, increase advertising or associated sales revenue for an MSO, as well as to increase the likelihood a particular advertiser will reach its targeted audience as precisely as possible (and within any limitations of an advertiser-MSO defined relationship).
Also illustrated in
The CPD 210 of
Also illustrated at
In yet another embodiment (not shown), the CPE 106 may comprise a personal video encoder (PVE) or comparable device. For example, the “Slingbox” device manufactured by Sling Media of San Mateo, Calif. is one such exemplary device which is capable of enabling a user to watch TV programming from various locations via an Internet-connected PC or similar device. The device is generally connected between the subscriber's cable/satellite video drop and DSTB, and has a TV tuner inside. The user tunes to a given channel, and the device encodes the video streamed over the cable/satellite in Windows Media or similar format. The encoded content is streamed to a client application on a Windows XP-based or similar PC via an IP network such as the Internet, and hence the user can view the data locally (i.e., at the same premises) or remotely so long as they have access to the IP distribution network. The delivered content may comprise both the requested content as well as zone-preserved secondary content as discussed herein.
Referring now to
Since the content is leaving the MSO network, an entitlements server 214 is utilized to ensure that the content is being delivered only to authorized users. However it is appreciated that the entitlements server 214 functions may be utilized in the embodiments discussed above where the content does not leave the MSO network (e.g.,
In one embodiment, the entitlements of the user to receive requested content are determined utilizing the systems and methods discussed in co-owned, co-pending U.S. patent application Ser. No. 12/536,724 filed on Aug. 6, 2009 and entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER A NETWORK”, incorporated herein by reference in its entirety. As discussed therein, in one embodiment, a request for content is received from the user device at the network 101. The request is forwarded to a network entity which obtains information identifying the user account (such as subscriber identification number, account number, etc.) and uses this information to request entitlements from an entitlements server 214 (also located at the headend in one embodiment). The entitlements server 214 accesses subscription information in a subscriber database to obtain sufficient information to determine the entitlements of the subscriber; and based on the results returned from the entitlements server 214, the network entity either grants or denies the request.
The client application 222 may request and receive application catalogs (having information regarding available content) from the application server 104. The client application 222 may be utilized to enable a user to sort through a plurality of available content and select one or more content items for display, recording, etc.
As noted above, the SRM 220 is in communication with the BMS 218 via SSP and in communication with the Billing System 152 via a Billing Operations Support Systems (BOSS) interface. The BMS 218 and Billing System 152 communicate with one another via a Customer Billing Interface (CBI).
As previously discussed, a correct advertising zone may be determined for a legacy STB and its client application 222 through use of a Service Group ID (Service_Group_id). Specifically, when the VOD client on the STB requests a primary content element (e.g. video), the Service_Group_id is contained in the requesting message. The application server 104 receives the message, extracts the Service_Group_id, performs a lookup to determine which advertising zone is associated with that Service_Group_id, and then instructs the VOD server 105 to serve the appropriate version of the requested video which contains the secondary content associated with the STB's advertising zone. Content may then be provided from the VOD server 105 to the client using lightweight stream control protocol (LSCP).
As illustrated in
Referring now to
As shown in
In operation, the aforementioned components operate in a generally comparable fashion to their counterpart legacy portion of the architecture, except for IP-encapsulated content. The IP client 223 sends a request to the IP SRM, the latter which establishes a session with the IP client 223. The IP stream server is used to receive content streams from the VOD server, and deliver the IP-encapsulated content stream(s) via the session (subject to authorization by the IP BMS), and zone control/preservation is maintained via information exchanged between the legacy VOD server and the stream server via the IVP 213.
Using any of the architectures discussed in
As discussed above, the present invention advantageously allows e.g., non-legacy devices (such as e.g., an IP device) to receive video content with the appropriate embedded advertisements from the legacy VOD storage solutions (i.e., the VOD server 105 and/or web server 203). The non-legacy devices may also access video from the VOD server 105 rather than from an IP-specific video server as is needed in the prior art.
In one embodiment, the architectures discussed above (
The actual video files on the VOD server 105 go through a transport layer adaptation process that converts the aforementioned MPEG2-TS into the appropriate protocols for delivery to a non-legacy device (for example converting to Real Time Messaging Protocol (RTMP), RTMPT, RTMPTS, RTMFP, RTP/RTCP, etc.). The IVP process 213 can also translate ISA messages destined to and from the SRM 220 into another format; e.g., packet cable multimedia (PCMM)-based COPS messages to allocate QoS resources on e.g., a DOCSIS network. The IVP can also be used to “pretend” to deliver messages to/from the SRM 220 when the video traffic is destined for a device that is served by an unmanaged (e.g., non-MSO) network such as the Internet, upon which no QoS reservations are made in order to enable the SRM 220 to track the resources of the VOD server 105.
In the exemplary embodiment, the proxy functionality of the IVP process 213 is of the type discussed in co-owned, co-pending U.S. patent application Ser. No. 11/284,427 entitled “METHODS AND APPARATUS FOR PROVIDING VIDEO ON DEMAND AND NETWORK PVR FUNCTIONS USING IP STREAMING”, previously incorporated herein (e.g., an RTSP-ISA Proxy Module), although other approaches and configurations may be used with equal success.
Zone-Controlled Secondary Content Delivery Methods—
Under the prior art approaches discussed above, correct advertisement zones are determined for legacy user devices by learning the Service Group ID (Service_Group_id) of the device from the edge quadrature amplitude modulator (eQAM) to which it receives video when the device boots up. Each eQAM is manually configured to be associated with a Service_Group_id. When the VOD client on the user device requests a video, the Service_Group_id is contained in the requesting message. The application server 104 receives the message, extracts the Service_Group_id, performs a lookup to determine which advertisement zone is associated with that Service_Group_id, and then instructs the VOD server 105 to serve the appropriate version of the requested video which contains the advertisements associated with the requesting device's advertisement zone.
However, as noted, the prior art does not provide mechanisms for ensuring that the correct advertisements are sent to the correct non-legacy devices from a “legacy” VOD server 105. The present invention provides methods for performing this and other functions (i.e., zone-controlled secondary content delivery).
Referring now to
Next, per step 308, the ZCPS 200 uses the eQAM_id to determine the user's associated Service_Group_id and/or advertisement zone_id.
Lastly, at step 310, the ZCPS 200 uses the Service_Group_id and/or advertisement zone_id to direct content delivery. For example, the on-demand video server 105 is instructed by the ZCPS 200 (via the aforementioned Service_Group_id and/or advertisement zone_id) to provide the appropriate video stream to the PC or IP device that is associated with the service group identity and/or advertisement zone identity. It is noted that the video storefront (e.g., as controlled by the application server 104) may be configured to request a video based upon either the service group identity and/or advertisement zone identity. It is further noted that multiple service groups can be associated with a single advertisement zone.
Referring now to
Per step 402 of the method, a user request is received from a client device for access to content. As above, the request includes the UID.
Next, per step 404, the ZCPS 200 forwards the UID to billing system 152.
At step 406, the billing system 152 returns a subscriber billing address information associated with the UID.
Then, per step 408, the ZCPS 200 uses the subscriber billing address information (or a portion thereof such as zip code, area code, etc.) to map to a service group and/or advertisement zone associated with the geographic area of the service address. The service_group_id and/or advertisement zone_id is then utilized to direct content delivery at the VOD server 105 (step 410).
Delivery to a Remote Network—
In another embodiment of the invention, the determination of an advertisement zone may be utilized in conjunction with the insertion of advertisements according to a user's actual location (versus e.g., their address of record as in
In one variant, the methods and apparatus discussed in co-owned, co-pending U.S. patent application Ser. No. 11/440,490 entitled “PERSONAL CONTENT SERVER APPARATUS AND METHODS” and filed May 24, 2006 may be utilized to provide the aforementioned secondary content insertion functions based on the location of the user.
The secondary content inserted for delivery to devices outside the MSO network may further be implemented or restricted according to a rules set. For example, a user may specify that, when content is requested from a “remote” network or location, advertisements specific to the user's location should be provided. Alternatively, the user may specify that he/she would like to continue receiving advertisements specific to his/her “home” location, even though the request is received from outside that geographic area. The MSO may also specify rules for the delivery of secondary (e.g., advertising) content, for example, the MSO may dictate whether the advertisements should match the geographic area of delivery (e.g., the remote location) or should match the geographic area generally associated with the user (e.g., the user's “home”).
Additionally, rule sets may provide time-based qualifications for the delivery of secondary content. For example, the rule sets (whether selected by the user or the MSO, or some combination thereof) may indicate that secondary content which has a particular time/date association may only be provided if the delivery time/date matches, or is prior to the relevant period. In one example, it may be determined that a user should receive an advertisement for “American Idol”; the advertisement has “date relevance” data which indicates that the advertised event (the particular broadcast of “American Idol” with which the advertisement is contextually associated) will occur at 9:00 P.M. in the Pacific Time Zone (which corresponds to 6:00 P.M Eastern). Suppose also that the user travels to New York (Eastern Time Zone) and the time of the delivery of the advertisement is 7:00 P.M. Eastern. Since the broadcast time for the advertised event has passed before the user is to receive the advertisement, this advertisement will not be presented to the user. Hence, the rules set may prohibit delivery of “old” advertisements (e.g., advertisements which have date/time expirations).
Referring now to
If the request originated from the user premises, per step 504 the method of either
Per step 506, the advertisements appropriate to the advertisement zone are then inserted into the requested content and the method continues.
If, at step 502, it is determined that the user is not making the request from his/her premises (i.e., the user is at a remote location), then per step 510 the user is located if not already done (using the aforementioned methods), and at step 520 the user is validated. Steps 510 and 520 may be performed simultaneously, or serially. Alternatively, only one of the steps may be performed, and the other comprising an optional step.
The user is located (step 510) by e.g., reviewing the IP address associated to the received request and determining at step 512 whether the MAC address of the requesting device matches a plurality of MAC address associated to a subscriber (such as is contained in a subscriber or account profile maintained by the MSO in the billing system or entitlements server 214 of
At step 516, the rules set is applied. The rules set, as noted above, comprises one or more MSO- or user-specified rules which dictate the parameters of delivery of secondary content (e.g., advertisements). The rules set may be based on date/time expirations of certain content, thus disabling the delivery of expired content. In addition (or as an alternative), the rules set may specify whether the received advertisements should be related to the context of the primary content, related to the context of the network, related to the remote geographic location which the user is currently located, or related to a user context (e.g., at home, at work, visiting a client on the road, etc.).
At step 518, according to the advertisement zone and rules set, the appropriate advertisements are inserted into the requested content and the method continues.
The user is validated (step 520) by prompting the user to enter login or other validating information (such as a user identification and password). In one embodiment, the user login validation may utilize the methods and apparatus discussed in co-owned, co-pending U.S. patent application Ser. No. 12/536,724 filed on Aug. 6, 2009 and entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER A NETWORK”, which is incorporated herein by reference in its entirety. As discussed therein, in one embodiment, a request for content is received from user device (e.g., PC 212, PMD 208, etc.) at an entity of the content distribution network. The network entity obtains information identifying the user account (such as subscriber identification number, account number, etc.) and uses this information to request entitlements from an entitlements server (located at the network headend 150 in one embodiment). Based on the results returned from the entitlements server, the network entity determines whether the login information is valid (step 522) and either grants or denies the request. The entitlements server accesses subscription information in a subscriber database to obtain sufficient information to determine the entitlements of the subscriber.
Note that the use of a user-specific login also advantageously enables user-specific targeted advertising (as may the MAC address of the device), if the MSO maintains data to that level of granularity. For instance, multiple different IP devices registered under a given subscriber account may correspond to individual family members, each having different preferences, demographics, psychographics, etc. If the MSO makes this association with data received, it can more finely target advertising to the requesting individual. This is particularly useful since account-based demographics, etc. may not be representative of all members of the population in that account. For example, a household associated with a subscription may have a gross or family income above $300K per year, yet the actual requester (e.g., child) may have no disposable income whatsoever, and hence an advertisement for a high end sports car or the like would be pointless and a waste of resources and impressions.
If the request is denied (the login information is not valid), then an error message will be displayed to the user at step 524. If the request is granted (the login information is valid), the method will proceed to step 514, where the advertisement zone is determined, the rules set is applied (step 516) and the appropriate advertisements are inserted (step 518).
The primary and secondary content may also be manipulated as part of the foregoing methods to perform all relevant advertising formats and schemes (e.g., bookends, replacement, pause, telescoping, etc.) on the content transferred by the network or from other content source. See, e.g., co-pending and co-owned U.S. patent application Ser. No. 10/662,776 filed Sep. 15, 2003 and entitled “SYSTEM AND METHOD FOR ADVERTISEMENT DELIVERY WITHIN A VIDEO TIME SHIFTING ARCHITECTURE”, incorporated herein by reference in its entirety, which describes exemplary methods and apparatus for implementing the foregoing (and other) schemes and formats within the context of a content-based network.
Additional Targeting Mechanisms—
In another aspect of the invention, the secondary content may be further targeted based on one or more user- or content-specific characteristics e.g., may be targeted to the user, their use context, and/or device from which a request is received, as well as to the primary content requested. This capability is leveraged by the functionality provided by the present invention, including inter alia the ability of a user to issue a request from an on-net or off-net IP-based device, and have that device and/or user validated and associated with an advertising or other zone. For example, once the pool of available advertising or other secondary content is narrowed by the relevant “zone” (as discussed above), the pool may be further narrowed based on e.g., demographics, psychographics, etc. by using a dynamic secondary content (e.g., advertisement) insertion process which gives the network operator the opportunity to provide the secondary content tailored to or which is logically proximate to the context of the primary content (e.g., programming).
As used herein, the term “logically proximate” refers to secondary content which bears some direct or indirect logical relationship to the primary content. For example, a logically proximate advertisement for the movie “Pirates of the Caribbean” might be one for Disneyland, which includes a “Pirates of the Caribbean” theme ride.
Such functionality also allows for the substitution or replacement of secondary content which is less suited to the present context or environment, or which is dated (see discussion above regarding time-sensitive content), even though it may by synchronized or “preserved” with respect to what the subscriber might receive over their legacy STB. In the context of the foregoing exemplary promotion, the promotion might carry “date relevance” data or the like in the form of metadata, which can be read and evaluated by the ZCPS 200 or other entity.
Hence, information may be obtained, for example, relating to the demographics, or psychographics of the subscriber, capabilities of the requesting device, etc. in order to target the secondary content to be logically related to the context of the primary content, whether in conjunction with a defined “zone” (e.g., geographic zone), or independently.
The user context may also be exploited; e.g., knowing based on time of day which members of a household is most likely to be viewing the programming, etc., or making use of a user-supplied classification or context (e.g., at work, traveling, etc.). In another variant, the network context may also be exploited; i.e., delivery of secondary content which is properly encoded to be delivered over the relevant distribution path, which fits the allotted time, which maximizes bandwidth or profits, is compatible with the user's requesting device (e.g., 3G smartphone, which may only have certain codecs, etc.), and so forth.
For instance, the present invention contemplates zone “pairs” or “tuples” which slice the targeting in two or more dimensions. In one such implementation, a zone pair might comprise the cross-section or subset of users which: (i) are associated with a given geographic region, and (ii) are associated with a given demographic. As another example, the pair might comprise (i) a given demographic, and (ii) a given psychographic. As yet another example, a tuple might comprise {a, b, c}, where:
a=a geographic zone;
b=a demographic factor; and
c=a primary content or user “use” context.
Myriad other permutations and combinations will be recognized by those of ordinary skill given the present disclosure.
For example, the apparatus and methods discussed in co-owned, co-pending U.S. patent application Ser. No. 11/198,620 filed on Aug. 4, 2005 and entitled 7“METHOD AND APPARATUS FOR CONTEXT-SPECIFIC CONTENT DELIVERY”, which is incorporated herein by reference in its entirety, may be utilized consistent with the present invention. As discussed therein, contextually-related “secondary” content (e.g., advertising messages, useful informational links, etc.) may be provided in association with other primary content selected by the user. In one exemplary embodiment, the secondary content is selected at least in part based on metadata associated with the primary content. The metadata may be provided by, e.g., the content originator or the network operator, and is sent to a network entity (e.g., advertising server) which returns contextually specific advertising matching the search terms. In one variant, the search term is simply one or more keywords drawn from the metadata and used as an input to a search engine. In another variant, more sophisticated analysis of the metadata is performed so as to ostensibly reduce the number of irrelevant or marginally relevant “hits” returned by the search engine/advertising server. Hence the pool of available secondary content may be narrowed not only by advertisement zone, but also by the context of the primary content.
Still further, the methods and apparatus discussed in co-owned, co-pending U.S. patent application Ser. No. 12/503,710 filed Jul. 15, 2009 and entitled “METHODS AND APPARATUS FOR TARGETED SECONDARY CONTENT INSERTION”, which is incorporated herein by reference in its entirety, may be utilized as well. This embodiment is particularly useful in targeting content to a set of subscribers, such as those serviced by a local service node. As discussed therein, content targeted to a particular audience within a content-based network may be identified and inserted. For instance, the content is identified by analyzing audience or viewer qualities (i.e., psychographic, geographic, or demographic, characteristic or classifications) at a particular insertion opportunity using an advertisement management system (and associated advertisement decision maker process). The audience information can in one embodiment be gathered in real-time directly from users' CPE (i.e., set top boxes, cable modems, PC, etc.), thereby allowing information to be gathered which is specific to actual content viewers. Historical or other information relating to particular subscribers (or subscribers in general, or even the broader general population) may also be utilized in characterizing an audience. The advertisement management system then uses the gathered audience information to correlate particular advertisements or other content thereto. In one variant, an algorithm is used to analyze audience qualifiers (i.e., attributes of an audience or its behavior), and determine the “proximity” of a given audience (e.g., that currently viewing a program where an impending placement opportunity will occur) to a set of audience qualifiers of a target audience of an advertisement. The placement opportunity can then be optimized for one or more variables (e.g., proximity, revenue, impressions, etc.) by selecting the best fitting advertisement for that opportunity within the advertisement zone of the requesting device.
The aforementioned methods and apparatus can advantageously provide content across multiple delivery platforms utilizing substantially extant network infrastructure and components compatible with a number of different client device and delivery systems including both wired and wireless technologies.
It will also be recognized that other types of information may also be included with the primary content that is delivered to the requester in the remote or visited network. For example, one variant of the invention comprises the inclusion of closed caption (cc) data, such as for example through use of the methods and apparatus described in co-pending and co-owned U.S. patent application Ser. No. 11/298,247 entitled “Caption Data Delivery Apparatus and Methods” filed Dec. 9, 2005 and incorporated herein by reference in its entirety. Similarly, emergency alert (e.g., EAS) data can be included for example using the methods and apparatus of co-pending and co-owned U.S. patent application Ser. No. 11/299,169 entitled “Emergency Alert Data Delivery Apparatus and Methods” also filed Dec. 9, 2005 and incorporated herein by reference in its entirety. This data may be geographically or contextually selected; e.g., EAS messages for the actual location of the requesting device, as described in the foregoing disclosure.
Zone Matching—
In yet another embodiment of the present invention, the “zones” discussed herein (such as e.g., advertisement zones) may be matched up to respective switched digital service group “zones”. For example, one or more of the herein-discussed zones may be correlated to or restricted by what previously comprised a single service group (or alternatively two or more service groups that comprise a subset of the zone), thereby generally decreasing the size of each zone (measured by number of customers in each) from what it would be without such correlation or restriction.
Bandwidth constraints are reduced as a result of the zone matching discussed above. More specifically, the needs of the constituents of the smaller groups are often more similar to one another in terms of: (i) requested primary content; (ii) targeted secondary content, or both. Hence, similar primary and/or secondary content may be distributed to the zone across fewer channels, requiring less bandwidth.
It is further appreciated that the zoning approaches discussed herein, such as those based on service group correlation/restriction described above, may be re-aggregated and/or re-distributed to create different units than those associated with the current zone(s). For instance, if one or more patterns of viewership become apparent, this may be used as the basis for re-organizing one or more zones, such as based on geography.
Start-Over and Lookback Variants—
As noted above, the primary content may also be used in conjunction with so-called “start-over” content (as described in previously incorporated co-owned, co-pending U.S. Patent Publication No. 2005/0034171 entitled “TECHNIQUE FOR DELIVERING PROGRAMMING CONTENT BASED ON A MODIFIED NETWORK PERSONAL VIDEO RECORDER SERVICE”) and/or “lookback” content (as described in previously incorporated co-owned, co-pending U.S. patent application Ser. No. 10/913,064 filed Aug. 6, 2004 and entitled “TECHNIQUE FOR DELIVERING PROGRAMMING CONTENT BASED ON A MODIFIED NETWORK PERSONAL VIDEO RECORDER SERVICE”).
The aforementioned services “harvest” linear broadcast content for storage on the VOD platforms (e.g., VOD server 105). The harvested start-over and/or lookback content is then made available to subscriber devices during a window of time after the original airing time. For start-over content, the window may be much smaller and may be more strictly tied to the broadcast time. For example, if the program Lost (episode #100) is broadcast from 8 PM to 9 PM on some Tuesday night, a file is captured that contains that episode of Lost, placed on the MSO VOD server, and made available for some period of time (for example, 3 days after the original airing time as “lookback” content). After the time period expires, the content is no longer available.
In one embodiment, secondary content which was originally included in the broadcast remains embedded in the video file that is stored on the VOD server 105. Further, some of the content may be “ad-insertable”, meaning that the MSO has the rights and ability to insert advertisements (or other secondary content) into the programming at pre-determined intervals.
According to the present invention, the aforementioned stored primary content may be provided to devices in different advertisement zones. Hence, for each advertisement insertion opportunity, a different advertisement may be inserted depending on the different geographic region of the requesting devices.
For example, suppose a single MSO division is divided into 20 zones; the episode of “Lost” may be stored 20 different times, with each stored instance containing the advertisements appropriate for each of the 20 zones. Alternatively, the program may be stored only one time on the VOD servers 105 in a series of components or segments which begin and end at advertisement insertion breaks. According to this embodiment, a playlist may then be created which “stitches” the pieces of the primary content and the different advertisements (different based on zone) together to provide the program with the correct embedded advertisements appropriate for the subscriber's advertisement zone.
Server Device—
Referring now to
As shown in
The digital processor 604 comprises at least one zone control/preservation application 610. The preservation application 610 comprises a series of executable code which runs on the processor 604 and when executed provide for the zone control and preservation functionality discussed above. For example, in one embodiment (see e.g.,
In another embodiment (see e.g.,
The mapping tables 612 may include e.g., a first set of tables mapping one or more eQAM_ids to a Service_Group_id and a second set of tables mapping each Service_Group_id to an advertisement zone_id.
The zone control/preservation application 610 may be configured to perform the user location and user validation functionalities discussed above with respect to
In another embodiment, the ZCPS 200 may further comprise a rule set implementation application (not shown). This application enables the ZCPS 200 to utilize both MSO- and user-specified rules of the type previously described herein in the selection of advertisements for delivery to a user. Storage of the rules sets may be at the ZCPS 200, or alternatively, at another entity in communication therewith. It is further appreciated that access to the stored rules may be granted to certain MSO entities and/or the user upon proper validation/verification.
The ZCPS 200 of
It can also be appreciated that the methods of the present invention may be practiced using any configuration or combination of hardware, firmware, or software, and may be disposed within one or any number of different physical or logical entities. For example, the zone control preservation functionality described above may take the form of one or more computer programs running on a single device disposed within the network (such as the ZCPS 200). As yet another example, portions of the functionality may be rendered as a dedicated or application specific IC (ASIC) having code running thereon, or a distributed application across multiple entities (e.g., ZCPS, VOD server, billing system, entitlements server, etc.). Myriad different configurations for practicing the server device of the invention will be recognized by those of ordinary skill in the network arts provided the present disclosure.
Exemplary CPE—
As shown in the simplified diagram of
The user device 700 further includes one or more digital processor(s) 704, storage device 706, and a plurality of optional interfaces 708 (e.g., video/audio interfaces, IEEE-1394 “FireWire”, USB, HDMI, serial/parallel ports, etc.) for interface with other end-user apparatus such as televisions, personal electronics, computers, WiFi or other network hubs/routers, etc. Various other components may also optionally be utilized within the device 700 include various processing layers (e.g., DOCSIS MAC or DAVIC OOB channel, MPEG, etc.) as well as media processors and other specialized SoC or ASIC devices. In certain embodiments, the device 700 may also comprise an integrated HD decoder, thereby relieving any connected monitors or other devices from the requirement of having such a decoder. These additional components and functionality are well known to those of ordinary skill in the cable and embedded system fields, and accordingly not described further herein.
The processor 704 of the exemplary user device 700 comprises at least one client application 223. The client application 223 comprises a series of executable code which run on the processor 704 and when executed facilitate the zone preservation functionality discussed above. For example, the client application 223 may be configured to: (i) communicate with the SRM 220, (ii) request and receive the application catalogs, (iii) provide a UID to the network 101 (and ultimately the ZCPS 200), and (iv) receive content from the network 101.
The device 700 of
The exemplary device 700 may further comprise a conventional “Watch TV” application or the like, which services those program or user channels available over the network. The Watch TV application, residing in memory, provides such functions as channel navigation control, channel selection in response to a channel change event, etc.
In another embodiment, the Watch TV application further comprises all necessary functionality need to support both the channel request features previously described herein (i.e., comprises the client application 223 previously described).
The device 700 also includes a TCP/IP (Transport Control Protocol/Internet Protocol) transport layer/network layer stack which enables IP decapsulation of received content (and optionally encapsulation of content received from e.g., a connected media capture device).
It will be recognized that while an IP enabled device for use “on net” (i.e., IP DSTB) having an RF stage and tuner is described herein, other types of IP enabled devices may be configured for “off net” communication as previously described, such as via another PHY such as WiFi, WiMAX, Ethernet LAN, cellular (e.g., UMTS, LTE/LTE-A, GSM), DSL, HFCu, satellite, and so forth.
It will also be recognized that while the foregoing methodology and apparatus is described in the context of a server-centric targeting paradigm (i.e., where the zone preservation server 200 or other network server performs the zone preservation functions), a more CPE-centric approach can be utilized, such as where the CPE generates or otherwise is assigned an identifier indicating an advertisement zone. The CPE may then provide the identifier to the ZCPS 200 which uses this information to direct the VOD or other content server's secondary content insertion decisions. For instance, the CPE might have protocol support for messaging between itself and another network entity to obtain the requisite identifier, or alternatively may be able of generating the identifier itself, such as based on a priori knowledge of its placement within the network, knowing its geographic location independently (such as association with a wireless node, or via AGPS), or yet other approaches.
Operations/Business Rules Engine—
In another aspect of the invention, the aforementioned zone control/preservation server 200 (e.g., rendered as one or more computer programs) includes a so-called “rules” engine. This engine comprises, in an exemplary embodiment, a series of software routines running on the ZCPS 200 or other associated hardware/firmware environment adapted to control the operation of the algorithms previously described. These rules may also be fully integrated within the ZCPS 200 itself, and controlled via e.g., a GUI on a PC connected thereto. In effect, the rules engine comprises a supervisory entity which monitors and selectively controls, via the ZCPS 200, the control/preservation and secondary content targeting functions at a higher level, so as to implement desired operational or business rules.
The rules engine can be considered an overlay of sorts to the ZCPS 200 algorithms. For example, the ZCPS 200 may invoke certain operational protocols or decision processes based on requests received from the user devices, demographic data, geographic data, etc. However, these processes may not always be compatible with higher level business or operational goals, such as maximizing profit or system reliability. Hence, when imposed, the business/operational rules can be used to dynamically (or even manually) control the operation of the ZCPS 200 and the messages which are relayed therefrom to the content servers (e.g., VOD server 105). The rules may be, e.g., operational or business-oriented in nature, and may also be applied selectively in terms of time of day, duration, specific local areas, or even at the individual user level. They may also implement the aforementioned user- or MSO-specified rule sets.
For example, one rule implemented by the rules engine may comprise only providing zone preservation or targeted advertising to certain classes of subscribers (e.g., those at a premium level of service, since these subscribers may be considered to have the highest revenue potential or likelihood of responding to the targeted advertisement).
Another rule might impose a moratorium on establishing or generating new versions of available content (directed towards different zones) until a certain minimum threshold of requests have been received.
Yet another rule might comprise enforcement of the aforementioned time-based restrictions; e.g., prohibit delivery of advertisements which have date/time expirations.
It will also be appreciated that advertisers may be tiered with only certain tier advertisements being delivered to devices in certain zones. For example, it may be known through historical usage or purchase data that certain zip codes or geographic zones will tend to respond better to increased targeted advertising than other zip codes (say, due to the increased disposable income of residents in that zip code). Hence, an advertiser's budget is most effectively used when their advertisements are included in streams which are requested by devices in such zip codes. An MSO might also be able to charge a premium rate for advertising within such channels, since the advertiser's expected yield is typically higher in these rather than other zip codes. Accordingly, the MSO might invoke a business rule (such as via the business engine of the ZCPS 200) which selectively provides only “premium” advertisements to the best zones (such as by zip code, etc.), while providing second-tier advertisements into other zones.
It will be appreciated that less “binary” approaches than those described above may be utilized consistent with the invention, whether in the context of providing zone-based targeting, other targeted advertising, etc. Specifically, the foregoing approach to zone-based targeted advertising effectively provides one of two states for the stream containing the targeted advertisement; i.e., delivered or not delivered. This approach has the advantage of simplicity, in that little real intelligence is required for implementation. In one embodiment, however, a supervisory process (e.g., algorithm) may comprise a fuzzy logic, Bayesian, or similar approach to classify individual requesting device into one of two categories in terms of a particular advertisement context (e.g., “enthusiast” or “non-enthusiast”), which can then be used as the sole (or at least partial) basis for delivering or not delivering a particular advertisement to the designated device. This logic may be used on top of or in conjunction with zone-based logic to further target advertisements within a zone (e.g., by demographics, psychographies, etc.). The categorization may be based, for example, on aggregated historic (anecdotal) data for that subscriber which is pooled irrespective of other considerations (such as, e.g., the day of the week, the particular family member viewing, and/or the time of day).
Additional business rules useful with the invention may include the utilization of individual or device-specific controls. Suppose for example that certain content is inappropriate for certain viewers (e.g., adult programming which is inappropriate for children). Accordingly, when it is determined that the receiving device is owned by or currently being used by a person who is among those people for whom the content is inappropriate, such content will not be delivered thereto. In the context of the aforementioned advertisement insertion, if the person receiving content is determined to be a child (such as by determining the device is owned or operated by a child), inappropriate advertisements, or interactive TV advertisements, are not provided to that child/device and/or to that zone. The determination of who is receiving the content may be made in a variety of ways, such as e.g.: (i) via a user-specific login or profile; (ii) via the request being associated with a member of a subscriber account (e.g., a mobile device known to be owned and operated by a member of a family), and/or (iii) via association with a user-specific environment (see, e.g., co-owned and co-pending U.S. patent application Ser. No. 12/414,554 file Mar. 30, 2009 entitled “Personal Media Channel Apparatus and Methods”, incorporated herein by reference in its entirety, which describes a user- or group-specific profile environment and supporting virtual channel approach).
In another exemplary embodiment, advertisements may be selected for insertion based on whether that advertisement was viewed by the customer, zone, and/or device previously. In other words, if a zone has previously received a first advertisement (or alternatively, received and has had one or more confirmed viewings of the received advertisement), the advertisement insertion processes (discussed above) may select a second advertisement rather than providing the first advertisement again.
Many other approaches and combinations are envisaged consistent with the invention, as will be recognized by those of ordinary skill when provided this disclosure.
It will be recognized that while certain aspects of the invention are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the invention, 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 invention disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the invention 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 invention. The foregoing description is of the best mode presently contemplated of carrying out the invention. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the invention. The scope of the invention should be determined with reference to the claims.
This application is a continuation of and claims priority to co-owned U.S. patent application Ser. No. 12/766,753 of the same title filed Apr. 23, 2010, issuing as U.S. Pat. No. 8,701,138 on Apr. 15, 2014, which is incorporated herein by reference in its entirety.
| 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 |
| 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 |
| 5675647 | Garneau et al. | Oct 1997 | A |
| 5724525 | Beyers, II | Mar 1998 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5774170 | Hite et al. | Jun 1998 | A |
| 5793409 | Tetsumura | Aug 1998 | A |
| 5812642 | Leroy | Sep 1998 | A |
| 5862312 | Mann et al. | Jan 1999 | A |
| 5914945 | Abu-Amara et al. | Jun 1999 | A |
| 5929849 | Kikinis | Jul 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 |
| 6016316 | Moura et al. | Jan 2000 | 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 |
| 6124878 | Adams et al. | Sep 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6161142 | Wolfe et al. | Dec 2000 | A |
| 6169728 | Perreault et al. | Jan 2001 | B1 |
| 6177931 | Alexander et al. | Jan 2001 | B1 |
| 6182050 | Ballard | Jan 2001 | B1 |
| 6202210 | Ludtke | Mar 2001 | B1 |
| 6211901 | Imajima et al. | Apr 2001 | B1 |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6272176 | Srinivasan | Aug 2001 | B1 |
| 6282713 | Kitsukawa et al. | Aug 2001 | B1 |
| 6292624 | Saib et al. | Sep 2001 | B1 |
| 6330609 | Garofalakis et al. | Dec 2001 | B1 |
| 6389538 | Gruse et al. | May 2002 | B1 |
| 6396055 | Biedendorf | May 2002 | B1 |
| 6446261 | Rosser | Sep 2002 | B1 |
| 6463585 | Hendricks et al. | Oct 2002 | B1 |
| 6467089 | Aust et al. | Oct 2002 | B1 |
| 6502076 | Smith | Dec 2002 | B1 |
| 6549718 | Grooters et al. | Apr 2003 | B1 |
| 6560578 | Eldering | May 2003 | B2 |
| 6601237 | Ten 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 |
| 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 |
| 6725461 | Dougherty et al. | Apr 2004 | B1 |
| 6738978 | Hendricks et al. | May 2004 | B1 |
| 6742187 | Vogel | May 2004 | B1 |
| 6769127 | Bonomi et al. | Jul 2004 | B1 |
| 6771290 | Hoyle | Aug 2004 | B1 |
| 6775843 | McDermott | Aug 2004 | B1 |
| 6785901 | Horiwitz et al. | Aug 2004 | B1 |
| 6813776 | Chernock et al. | Nov 2004 | B2 |
| 6859845 | Mate | Feb 2005 | B2 |
| 6898762 | Ellis et al. | May 2005 | B2 |
| 6901606 | Wright et al. | May 2005 | B2 |
| 6909837 | Unger | Jun 2005 | B1 |
| 6915528 | McKenna, Jr. | Jul 2005 | B1 |
| 6917614 | Laubach et al. | Jul 2005 | B1 |
| 6917641 | Kotzin et al. | Jul 2005 | B2 |
| 6990680 | Wugofski | Jan 2006 | B1 |
| 7017179 | Asamoto et al. | Mar 2006 | B1 |
| 7024676 | Klopfenstein | Apr 2006 | B1 |
| 7039928 | Kamada et al. | May 2006 | B2 |
| 7075945 | Arsenault et al. | Jul 2006 | B2 |
| 7100183 | Kunkel et al. | Aug 2006 | B2 |
| 7109848 | Schybergson | Sep 2006 | B2 |
| 7143431 | Eager et al. | Nov 2006 | B1 |
| 7146627 | Ismail et al. | Dec 2006 | B1 |
| 7152237 | Flickinger et al. | Dec 2006 | B2 |
| 7155508 | Sankuratripati et al. | Dec 2006 | B2 |
| 7174126 | McElhatten | Feb 2007 | B2 |
| 7191461 | Arsenault et al. | Mar 2007 | B1 |
| 7197472 | Conkwright et al. | Mar 2007 | B2 |
| 7213036 | Apparao et al. | May 2007 | B2 |
| 7222078 | Abelow | May 2007 | B2 |
| 7228555 | Schlack | Jun 2007 | B2 |
| 7237250 | Kanojia et al. | Jun 2007 | B2 |
| 7242988 | Hoffberg et al. | Jul 2007 | B1 |
| 7246150 | Donoho et al. | Jul 2007 | B1 |
| 7246172 | Yoshiba et al. | Jul 2007 | B2 |
| 7266836 | Anttila et al. | Sep 2007 | B2 |
| 7280737 | Smith | Oct 2007 | B2 |
| 7281261 | Jaff et al. | Oct 2007 | B2 |
| 7317728 | Acharya et al. | Jan 2008 | B2 |
| 7327692 | Ain et al. | Feb 2008 | B2 |
| 7352775 | Powell | Apr 2008 | B2 |
| 7355980 | Bauer et al. | Apr 2008 | B2 |
| 7356751 | Levitan | Apr 2008 | B1 |
| 7357775 | Koh | Apr 2008 | B1 |
| 7363371 | Kirby et al. | Apr 2008 | B2 |
| 7363643 | Drake et al. | Apr 2008 | B2 |
| 7367043 | Dudkiewicz et al. | Apr 2008 | B2 |
| 7369750 | Cheng et al. | May 2008 | B2 |
| 7444655 | Sardera | Oct 2008 | B2 |
| 7457520 | Rossetti | Nov 2008 | B2 |
| 7567983 | Pickelsimer et al. | Jul 2009 | B2 |
| 7577118 | Haumonte et al. | Aug 2009 | B2 |
| 7592912 | Hasek et al. | Sep 2009 | B2 |
| 7602820 | Helms | Oct 2009 | B2 |
| 7603529 | MacHardy et al. | Oct 2009 | B1 |
| 7650319 | Hoffberg et al. | Jan 2010 | B2 |
| 7712125 | Herigstad et al. | May 2010 | B2 |
| 7720432 | Colby et al. | May 2010 | B1 |
| 7729940 | Harvey et al. | Jun 2010 | B2 |
| 7730509 | Boulet et al. | Jun 2010 | B2 |
| 7763360 | Paul | Jul 2010 | B2 |
| 7783316 | Mitchell | Aug 2010 | B1 |
| 7801803 | Forlai | Sep 2010 | B2 |
| 7900052 | Jonas et al. | Mar 2011 | B2 |
| 7900229 | Dureau | Mar 2011 | B2 |
| 7954131 | Cholas et al. | May 2011 | B2 |
| 8024762 | Britt | Sep 2011 | B2 |
| 8028322 | Riedl et al. | Sep 2011 | B2 |
| 8042131 | Flickinger | Oct 2011 | B2 |
| 8065703 | Wilson et al. | Nov 2011 | B2 |
| 8073460 | Scofield | Dec 2011 | B1 |
| 8078696 | Lajoie et al. | Dec 2011 | B2 |
| 8090014 | Cheung et al. | Jan 2012 | B2 |
| 8090104 | Wajs et al. | Jan 2012 | B2 |
| 8095610 | Gould et al. | Jan 2012 | B2 |
| 8099757 | Riedl | Jan 2012 | B2 |
| 8151294 | Carlucci et al. | Apr 2012 | B2 |
| 8156520 | Casagrande et al. | Apr 2012 | B2 |
| 8181209 | Hasek | May 2012 | B2 |
| 8205226 | Ko et al. | Jun 2012 | B2 |
| 8214256 | Riedl | Jul 2012 | B2 |
| 8280982 | La et al. | Oct 2012 | B2 |
| 8296185 | Isaac | Oct 2012 | B2 |
| 8341242 | Dillon et al. | Dec 2012 | B2 |
| 8347341 | Markley et al. | Jan 2013 | B2 |
| 8365213 | Orlowski | Jan 2013 | B1 |
| 8396055 | Patel et al. | Mar 2013 | B2 |
| 8396056 | Dalton, Jr. et al. | Mar 2013 | B2 |
| 8472371 | Bari | Jun 2013 | B1 |
| 8484511 | Engel et al. | Jul 2013 | B2 |
| 8516529 | Lajoie et al. | Aug 2013 | B2 |
| 8561113 | Cansler et al. | Oct 2013 | B2 |
| 8561116 | Hasek | Oct 2013 | B2 |
| 8571931 | Riedl et al. | Oct 2013 | B2 |
| 8621501 | Matheny et al. | Dec 2013 | B2 |
| 8769559 | Moon et al. | Jul 2014 | B2 |
| 8838149 | Hasek | Sep 2014 | B2 |
| 9021566 | Panayotopoulos et al. | Apr 2015 | B1 |
| 9215423 | Kimble et al. | Dec 2015 | B2 |
| 9400875 | Barraclough et al. | Jul 2016 | B1 |
| 20010001160 | Shoff et al. | May 2001 | A1 |
| 20010013123 | Freeman et al. | Aug 2001 | A1 |
| 20020026496 | Boyer et al. | Feb 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020049902 | Rhodes | Apr 2002 | A1 |
| 20020059577 | Lu et al. | May 2002 | A1 |
| 20020059602 | MacRae et al. | May 2002 | A1 |
| 20020059619 | Lebar | May 2002 | A1 |
| 20020069404 | Copeman et al. | Jun 2002 | A1 |
| 20020073419 | Yen et al. | Jun 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. et al. | Jul 2002 | A1 |
| 20020100063 | Herigstad et al. | Jul 2002 | A1 |
| 20020104083 | Hendricks et al. | Aug 2002 | A1 |
| 20020104096 | Cramer 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 |
| 20020129368 | Schlack et al. | Sep 2002 | A1 |
| 20020144263 | Eldering et al. | Oct 2002 | A1 |
| 20020147984 | Tomsen et al. | Oct 2002 | A1 |
| 20020154655 | Gummalla et al. | Oct 2002 | A1 |
| 20020163928 | Rudnick et al. | Nov 2002 | A1 |
| 20020166119 | Cristofalo | Nov 2002 | A1 |
| 20020174430 | Ellis et al. | Nov 2002 | A1 |
| 20020178445 | Eldering et al. | Nov 2002 | A1 |
| 20020178447 | Plotnick et al. | Nov 2002 | A1 |
| 20020184629 | Sie et al. | Dec 2002 | A1 |
| 20020184634 | Cooper | Dec 2002 | A1 |
| 20020184635 | Istvan | Dec 2002 | A1 |
| 20030004810 | Eldering | Jan 2003 | A1 |
| 20030005446 | Jaff et al. | Jan 2003 | A1 |
| 20030018977 | McKenna | Jan 2003 | A1 |
| 20030020744 | Ellis et al. | Jan 2003 | A1 |
| 20030023489 | McGuire | Jan 2003 | A1 |
| 20030030751 | Lupulescu et al. | Feb 2003 | A1 |
| 20030033199 | Coleman | Feb 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030077067 | Wu et al. | Apr 2003 | A1 |
| 20030086422 | Klinker et al. | May 2003 | A1 |
| 20030093311 | Knowlson | May 2003 | A1 |
| 20030093784 | Dimitrova et al. | May 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030093792 | Labeeb 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 |
| 20030110503 | Perkes | Jun 2003 | A1 |
| 20030115601 | Palazzo et al. | Jun 2003 | A1 |
| 20030115612 | Mao et al. | Jun 2003 | A1 |
| 20030123465 | Donahue | Jul 2003 | A1 |
| 20030135513 | Quinn et al. | Jul 2003 | A1 |
| 20030140351 | Hoarty et al. | Jul 2003 | A1 |
| 20030145323 | Hendricks et al. | Jul 2003 | A1 |
| 20030145329 | Candelore | Jul 2003 | A1 |
| 20030149975 | Eldering et al. | Aug 2003 | A1 |
| 20030149990 | Anttila et al. | Aug 2003 | A1 |
| 20030149993 | Son et al. | Aug 2003 | A1 |
| 20030172374 | Vinson et al. | Sep 2003 | A1 |
| 20030172376 | Coffin | Sep 2003 | A1 |
| 20030177495 | Needham et al. | Sep 2003 | A1 |
| 20030198461 | Taylor et al. | Oct 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030220100 | McElhatten et al. | Nov 2003 | A1 |
| 20030229681 | Levitan | Dec 2003 | A1 |
| 20030237090 | Boston et al. | Dec 2003 | A1 |
| 20040003400 | Carney | Jan 2004 | A1 |
| 20040034873 | Zenoni | Feb 2004 | A1 |
| 20040047599 | Grzeczkowski | Mar 2004 | A1 |
| 20040060076 | Song | Mar 2004 | A1 |
| 20040070678 | Toyama et al. | Apr 2004 | A1 |
| 20040073915 | Dureau | Apr 2004 | A1 |
| 20040078809 | Drazin | Apr 2004 | A1 |
| 20040083177 | Chen et al. | Apr 2004 | A1 |
| 20040103429 | Carlucci et al. | May 2004 | A1 |
| 20040109672 | Kim et al. | Jun 2004 | A1 |
| 20040117817 | Kwon et al. | Jun 2004 | A1 |
| 20040133467 | Siler | Jul 2004 | A1 |
| 20040138909 | Mayer | Jul 2004 | A1 |
| 20040148625 | Eldering et al. | Jul 2004 | A1 |
| 20040163109 | Kang et al. | Aug 2004 | A1 |
| 20040163111 | Palazzo et al. | Aug 2004 | A1 |
| 20040177383 | Martinolich et al. | Sep 2004 | A1 |
| 20040181811 | Rakib | Sep 2004 | A1 |
| 20040186774 | Lee | Sep 2004 | A1 |
| 20040194134 | Gunatilake et al. | Sep 2004 | A1 |
| 20040199789 | Shaw et al. | Oct 2004 | A1 |
| 20040230994 | Urdang et al. | Nov 2004 | A1 |
| 20050002638 | Putterman et al. | Jan 2005 | A1 |
| 20050022237 | Nomura | Jan 2005 | A1 |
| 20050027696 | Swaminathan et al. | Feb 2005 | A1 |
| 20050028208 | Ellis et al. | Feb 2005 | A1 |
| 20050034171 | Benya | Feb 2005 | A1 |
| 20050034173 | Hatanaka | Feb 2005 | A1 |
| 20050039205 | Riedl | Feb 2005 | A1 |
| 20050047596 | Suzuki | Mar 2005 | A1 |
| 20050055685 | Maynard et al. | Mar 2005 | A1 |
| 20050060742 | Riedl et al. | Mar 2005 | A1 |
| 20050060745 | Riedl et al. | Mar 2005 | A1 |
| 20050086334 | Aaltonen et al. | Apr 2005 | A1 |
| 20050086691 | Dudkiewicz et al. | Apr 2005 | A1 |
| 20050105396 | Schybergson | May 2005 | A1 |
| 20050114141 | Grody | May 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050123001 | Craven et al. | Jun 2005 | A1 |
| 20050138656 | Moore et al. | Jun 2005 | A1 |
| 20050144635 | Boortz et al. | Jun 2005 | A1 |
| 20050160308 | Elcock et al. | Jul 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 |
| 20050235318 | Grauch et al. | Oct 2005 | A1 |
| 20050251827 | Ellis et al. | Nov 2005 | A1 |
| 20050262542 | Deweese et al. | Nov 2005 | A1 |
| 20050273819 | Knudson et al. | Dec 2005 | A1 |
| 20050276284 | Krause et al. | Dec 2005 | A1 |
| 20050289588 | Kinnear | Dec 2005 | A1 |
| 20050289618 | Hardin | Dec 2005 | A1 |
| 20060019702 | Anttila et al. | Jan 2006 | A1 |
| 20060031883 | Ellis et al. | Feb 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060037060 | Simms et al. | Feb 2006 | A1 |
| 20060059532 | Dugan et al. | Mar 2006 | A1 |
| 20060080408 | Istvan et al. | Apr 2006 | A1 |
| 20060117341 | Park | Jun 2006 | A1 |
| 20060128397 | Choti et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060139379 | Toma et al. | Jun 2006 | A1 |
| 20060165082 | Pfeffer et al. | Jul 2006 | A1 |
| 20060171390 | La | 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 |
| 20060218604 | Riedl et al. | Sep 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 |
| 20060259924 | Boortz et al. | Nov 2006 | A1 |
| 20060277569 | Smith | Dec 2006 | A1 |
| 20060287915 | Boulet | Dec 2006 | A1 |
| 20060288374 | Ferris et al. | Dec 2006 | A1 |
| 20060294259 | Matefi et al. | Dec 2006 | A1 |
| 20070014293 | Filsfils et al. | Jan 2007 | A1 |
| 20070022459 | Gaebel, Jr. | Jan 2007 | A1 |
| 20070029379 | Peyer | Feb 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070061023 | Hoffberg et al. | Mar 2007 | A1 |
| 20070074258 | Wood et al. | Mar 2007 | A1 |
| 20070076728 | Rieger et al. | Apr 2007 | A1 |
| 20070088852 | Levkovitz | Apr 2007 | A1 |
| 20070089127 | Flickinger et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070094692 | De | Apr 2007 | A1 |
| 20070101370 | Calderwood | May 2007 | A1 |
| 20070113243 | Brey | May 2007 | A1 |
| 20070115389 | McCarthy et al. | May 2007 | A1 |
| 20070118852 | Calderwood | May 2007 | A1 |
| 20070136777 | Hasek | Jun 2007 | A1 |
| 20070150919 | Morishita | Jun 2007 | A1 |
| 20070157228 | Bayer | Jul 2007 | A1 |
| 20070157242 | Cordray et al. | Jul 2007 | A1 |
| 20070157262 | Ramaswamy et al. | Jul 2007 | A1 |
| 20070180230 | Cortez | Aug 2007 | A1 |
| 20070204308 | Nicholas | Aug 2007 | A1 |
| 20070204310 | Hua et al. | Aug 2007 | A1 |
| 20070217436 | Markley | Sep 2007 | A1 |
| 20070233857 | Cheng et al. | Oct 2007 | A1 |
| 20070239536 | Bollapragada | Oct 2007 | A1 |
| 20070244760 | Bodnar et al. | Oct 2007 | A1 |
| 20070276925 | La Joie | Nov 2007 | A1 |
| 20070276926 | Lajoie et al. | Nov 2007 | A1 |
| 20070280298 | Hearn et al. | Dec 2007 | A1 |
| 20080016526 | Asmussen | Jan 2008 | A1 |
| 20080022309 | Begeja et al. | Jan 2008 | A1 |
| 20080027801 | Walter | Jan 2008 | A1 |
| 20080052157 | Kadambi et al. | Feb 2008 | A1 |
| 20080066095 | Reinoso | Mar 2008 | A1 |
| 20080092058 | Afergan | Apr 2008 | A1 |
| 20080092181 | Britt | Apr 2008 | A1 |
| 20080109853 | Einarsson et al. | May 2008 | A1 |
| 20080115169 | Ellis et al. | May 2008 | A1 |
| 20080124056 | Concotelli | May 2008 | A1 |
| 20080147497 | Tischer | Jun 2008 | A1 |
| 20080155588 | Roberts et al. | Jun 2008 | A1 |
| 20080163305 | Johnson et al. | Jul 2008 | A1 |
| 20080168487 | Chow et al. | Jul 2008 | A1 |
| 20080170551 | Zaks | Jul 2008 | A1 |
| 20080184344 | Hernacki et al. | Jul 2008 | A1 |
| 20080189617 | Covell et al. | Aug 2008 | A1 |
| 20080192820 | Brooks et al. | Aug 2008 | A1 |
| 20080200154 | Maharajh et al. | Aug 2008 | A1 |
| 20080201736 | Gordon et al. | Aug 2008 | A1 |
| 20080215755 | Farber et al. | Sep 2008 | A1 |
| 20080229354 | Morris et al. | Sep 2008 | A1 |
| 20080235746 | Peters et al. | Sep 2008 | A1 |
| 20080256615 | Schlacht et al. | Oct 2008 | A1 |
| 20080263578 | Bayer et al. | Oct 2008 | A1 |
| 20080271068 | Ou et al. | Oct 2008 | A1 |
| 20080271070 | Kanojia et al. | Oct 2008 | A1 |
| 20080273591 | Brooks et al. | Nov 2008 | A1 |
| 20080301727 | Cristofalo | Dec 2008 | A1 |
| 20080306903 | Larson et al. | Dec 2008 | A1 |
| 20080307454 | Ahanger et al. | Dec 2008 | A1 |
| 20080313671 | Batrouny et al. | Dec 2008 | A1 |
| 20080313691 | Cholas et al. | Dec 2008 | A1 |
| 20090006211 | Perry et al. | Jan 2009 | A1 |
| 20090030802 | Plotnick et al. | Jan 2009 | A1 |
| 20090076898 | Wang | Mar 2009 | A1 |
| 20090077583 | Sugiyama et al. | Mar 2009 | A1 |
| 20090083279 | Hasek | Mar 2009 | A1 |
| 20090086643 | Kotrla et al. | Apr 2009 | A1 |
| 20090094347 | Ting et al. | Apr 2009 | A1 |
| 20090119703 | Piepenbrink et al. | May 2009 | A1 |
| 20090132346 | Duggal et al. | May 2009 | A1 |
| 20090132347 | Anderson | May 2009 | A1 |
| 20090133048 | Gibbs et al. | May 2009 | A1 |
| 20090150917 | Huffman et al. | Jun 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090187941 | Smith | Jul 2009 | A1 |
| 20090210899 | Lawrence-Apfelbaum et al. | Aug 2009 | A1 |
| 20090228941 | Russell et al. | Sep 2009 | A1 |
| 20090248794 | Helms et al. | Oct 2009 | A1 |
| 20090319379 | Joao | Dec 2009 | A1 |
| 20090320059 | Bolyukh | Dec 2009 | A1 |
| 20090327057 | Redlich | Dec 2009 | A1 |
| 20100005527 | Jeon | Jan 2010 | A1 |
| 20100027560 | Yang et al. | Feb 2010 | A1 |
| 20100027787 | Benkert et al. | Feb 2010 | A1 |
| 20100036720 | Jain | Feb 2010 | A1 |
| 20100057560 | Skudlark et al. | Mar 2010 | A1 |
| 20100107194 | McKissick et al. | Apr 2010 | A1 |
| 20100114696 | Yang | May 2010 | A1 |
| 20100115091 | Park et al. | May 2010 | A1 |
| 20100115540 | Fan et al. | May 2010 | A1 |
| 20100121936 | Liu et al. | May 2010 | A1 |
| 20100122276 | Chen | May 2010 | A1 |
| 20100125658 | Strasters | May 2010 | A1 |
| 20100131973 | Dillon | May 2010 | A1 |
| 20100132003 | Bennett et al. | May 2010 | A1 |
| 20100146541 | Velazquez | Jun 2010 | A1 |
| 20100151882 | Gillies et al. | Jun 2010 | A1 |
| 20100161492 | Harvey et al. | Jun 2010 | A1 |
| 20100162367 | Lajoie et al. | Jun 2010 | A1 |
| 20100169503 | Kollmansberger | Jul 2010 | A1 |
| 20100175084 | Ellis et al. | Jul 2010 | A1 |
| 20100175584 | Kusaka et al. | Jul 2010 | A1 |
| 20100186029 | Kim et al. | Jul 2010 | A1 |
| 20100218231 | Frink et al. | Aug 2010 | A1 |
| 20100251304 | Donoghue | Sep 2010 | A1 |
| 20100251305 | Kimble et al. | Sep 2010 | A1 |
| 20100262461 | Bohannon | Oct 2010 | A1 |
| 20100262488 | Harrison et al. | Oct 2010 | A1 |
| 20100262999 | Curran | Oct 2010 | A1 |
| 20100269131 | Newberry et al. | Oct 2010 | A1 |
| 20100275226 | Kitazato | Oct 2010 | A1 |
| 20100280641 | Harkness et al. | Nov 2010 | A1 |
| 20100293047 | Schwarz et al. | Nov 2010 | A1 |
| 20100313225 | Cholas | Dec 2010 | A1 |
| 20100333137 | Hamano | Dec 2010 | A1 |
| 20110015989 | Tidwell et al. | Jan 2011 | A1 |
| 20110016479 | Tidwell | Jan 2011 | A1 |
| 20110016482 | Tidwell et al. | Jan 2011 | A1 |
| 20110055866 | Piepenbrink et al. | Mar 2011 | A1 |
| 20110058675 | Brueck et al. | Mar 2011 | A1 |
| 20110083069 | Paul et al. | Apr 2011 | A1 |
| 20110083144 | Bocharov et al. | Apr 2011 | A1 |
| 20110090898 | Patel et al. | Apr 2011 | A1 |
| 20110093900 | Patel et al. | Apr 2011 | A1 |
| 20110099017 | Ure | Apr 2011 | A1 |
| 20110103374 | Lajoie | May 2011 | A1 |
| 20110107364 | Lajoie et al. | May 2011 | A1 |
| 20110107379 | Lajoie et al. | May 2011 | A1 |
| 20110110515 | Tidwell et al. | May 2011 | A1 |
| 20110138064 | Rieger et al. | Jun 2011 | A1 |
| 20110154383 | Hao et al. | Jun 2011 | A1 |
| 20110178880 | Karaoguz et al. | Jul 2011 | A1 |
| 20110178943 | Motahari et al. | Jul 2011 | A1 |
| 20110223944 | Gosselin | Sep 2011 | A1 |
| 20110231265 | Brown et al. | Sep 2011 | A1 |
| 20110231660 | Kanungo | Sep 2011 | A1 |
| 20110246616 | Ronca et al. | Oct 2011 | A1 |
| 20110258049 | Ramer et al. | Oct 2011 | A1 |
| 20110264530 | Santangelo | Oct 2011 | A1 |
| 20110265116 | Stern et al. | Oct 2011 | A1 |
| 20110302624 | Chen et al. | Dec 2011 | A1 |
| 20110307339 | Russell et al. | Dec 2011 | A1 |
| 20110307920 | Blanchard et al. | Dec 2011 | A1 |
| 20110317977 | Harris | Dec 2011 | A1 |
| 20120008786 | Cronk et al. | Jan 2012 | A1 |
| 20120011269 | Krikorian et al. | Jan 2012 | A1 |
| 20120030363 | Conrad | Feb 2012 | A1 |
| 20120072526 | Kling et al. | Mar 2012 | A1 |
| 20120076015 | Pfeffer | Mar 2012 | A1 |
| 20120079523 | Trimper et al. | Mar 2012 | A1 |
| 20120084813 | Dmitriev et al. | Apr 2012 | A1 |
| 20120089699 | Cholas | Apr 2012 | A1 |
| 20120096106 | Blumofe et al. | Apr 2012 | A1 |
| 20120110620 | Kilar et al. | May 2012 | A1 |
| 20120124161 | Tidwell et al. | May 2012 | A1 |
| 20120124606 | Tidwell et al. | May 2012 | A1 |
| 20120124612 | Adimatyam et al. | May 2012 | A1 |
| 20120137332 | Kumar | May 2012 | A1 |
| 20120144195 | Nair et al. | Jun 2012 | A1 |
| 20120151077 | Finster | Jun 2012 | A1 |
| 20120159539 | Berberet et al. | Jun 2012 | A1 |
| 20120167132 | Mathews et al. | Jun 2012 | A1 |
| 20120170544 | Cheng et al. | Jul 2012 | A1 |
| 20120170741 | Chen et al. | Jul 2012 | A1 |
| 20120173746 | Salinger et al. | Jul 2012 | A1 |
| 20120174150 | Reddy et al. | Jul 2012 | A1 |
| 20120185693 | Chen et al. | Jul 2012 | A1 |
| 20120246462 | Moroney et al. | Sep 2012 | A1 |
| 20120278833 | Tam et al. | Nov 2012 | A1 |
| 20120284804 | Lindquist et al. | Nov 2012 | A1 |
| 20120308071 | Ramsdell et al. | Dec 2012 | A1 |
| 20120324552 | Padala et al. | Dec 2012 | A1 |
| 20130029716 | Lee | Jan 2013 | A1 |
| 20130031578 | Zhu et al. | Jan 2013 | A1 |
| 20130041747 | Anderson et al. | Feb 2013 | A1 |
| 20130046849 | Wolf et al. | Feb 2013 | A1 |
| 20130114940 | Merzon et al. | May 2013 | A1 |
| 20130132986 | Mack et al. | May 2013 | A1 |
| 20130133010 | Chen | May 2013 | A1 |
| 20130166906 | Swaminathan et al. | Jun 2013 | A1 |
| 20130174271 | Handal et al. | Jul 2013 | A1 |
| 20130179588 | McCarthy et al. | Jul 2013 | A1 |
| 20130219178 | Xiques et al. | Aug 2013 | A1 |
| 20130227283 | Williamson et al. | Aug 2013 | A1 |
| 20130227284 | Pfeffer et al. | Aug 2013 | A1 |
| 20130227608 | Evans et al. | Aug 2013 | A1 |
| 20140012843 | Soon-Shiong | Jan 2014 | A1 |
| 20140020017 | Stern et al. | Jan 2014 | A1 |
| 20140033252 | Radloff et al. | Jan 2014 | A1 |
| 20140230003 | Ma et al. | Aug 2014 | A1 |
| 20140245341 | Mack et al. | Aug 2014 | A1 |
| 20140259182 | Mershon | Sep 2014 | A1 |
| 20150109122 | Stern et al. | Apr 2015 | A1 |
| 20150163540 | Masterson | Jun 2015 | A1 |
| 20160241617 | Jelley et al. | Aug 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-0191474 | Nov 2001 | WO |
| WO-2010008487 | Jan 2010 | WO |
| WO-2011035443 | Mar 2011 | WO |
| WO-2011053858 | May 2011 | WO |
| Entry |
|---|
| American national Standard. ANSI/SCTE 35 2012. Digital Program Insertion Cueing Message for Cable, by Society of Cable Telecommunication Engineers. 2012. |
| Apple Inc, The apparatus and methods of H1TP Live Streaming Overview, Apr. 1, 2011. |
| Open Cable Specifications Alternate Content Real-Time Event Signaling and Management API by Cable Television Laboratories. Inc. 2012. |
| SCTE Standards Document ANSUSCTE 118-2 2007 entitled Program-Specific Ad Insertion—Content Provider to Traffic Communication Applications Data Model. |
| SCTE Standards Document ANSUSCTE 130-1 2008 entitled Digital Progra section Advertising Systems Interfaces. |
| Zarnbell °T he Apparatus and Methods of HS Smooth Streaming Technical Overview, Mar. 2009. |
| Open Cable Specification entitled “Enhanced TV Binary Interchange Format 1 0” 0C-SP-ETV-131F1.0-106-110128 dated Jan. 28, 2011, 408 pages. |
| Tandberg Television specification entitled “AdPoint.RTM. Advanced Advertising Platform” dated Mar. 2008, 2 pages. |
| UTF-32, IBM, retrieved from http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2FnIs%2Frbagsutf32.htm on Aug. 28, 2013. |
| Number | Date | Country | |
|---|---|---|---|
| 20140317657 A1 | Oct 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12766753 | Apr 2010 | US |
| Child | 14252686 | US |
