Patent Grant
11082723
1. Field of the Invention
The invention relates to the fields of content storage and delivery over one or more networks such as for example cable television networks and other networks (e.g., the Internet).
2. Description of Related Technology
Recent advances in video capture and data storage technologies have led to the proliferation of consumer electronics devices that allow a user to record video programming or other content received from a bearer network (such as a cable television or satellite network) on a digital video recorder (DVR) or personal video recorder (PVR), and contemporaneously or subsequently access the content. Additionally, such DVR/PVR devices can also be used to transmit the stored content over a network interface to another device (which may or may not be remote from the DVR/PVR) where the same or another user can access the content.
However, such distribution of the content to a second device or location generally makes inefficient use of the available network bandwidth. For example, when the bearer network is cable television network, and the network interface comprises an internetworking (e.g., Internet) connection realized via a cable or other type of modem, the delivery of the content requires effectively twice the bandwidth it would otherwise require; i.e., first in the downstream direction to receive the content, and second in the upstream direction to transmit the program to the desired destination via the upstream channels (e.g., QAMs) associated with the DOCSIS or other modem architecture in use.
Exemplary prior art in this area includes the “Slingbox™” device manufactured by Sling Media of San Mateo, Calif. This device is capable of enabling a user to, inter alia, watch TV programming from various locations via an Internet-connected PC or similar device. The device utilizes an analog television (RF) tuner; when the user tunes to a given channel, the Slingbox encodes the video input received via the downstream delivery channels (e.g., QAMs or otherwise) in Windows Media or similar format. The encoded content is then streamed to a client application disposed on a Windows XP-based or similar PC via an IP network such as the Internet. 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 Slingbox approach (and those similar thereto) suffers from several disadvantages. Specifically, in the case where the programming delivered to the premises is in digital format, the conversion of this digital program to analog format, and back again to digital, results in some degradation in media quality. Also, metadata such as closed captioning, teletext, etc. associated with a digital program is generally lost when converted to and back from the analog format.
Additionally, since the upstream bandwidth from a premises at which the Slingbox or similar device is installed is typically shared by multiple devices, other applications desiring to transmit data upstream may have to compete with the upstream transmission for the remote viewing session, thereby potentially leading to contention and reduced data rates for each user (especially if the Slingbox transmission enforces a minimum required upstream bandwidth for QoS or other considerations).
Similarly, because such use of remote viewing is constrained by the upstream bandwidth of a user's premises to the Internet, viewing high-quality, high-resolution programming such as high definition (HD) programming may be limited or even not available.
Furthermore, once a user makes the investment in a storage and streaming device such as the Slingbox, he/she is largely “locked into” the technology, and accordingly may have difficulty retrofitting the device with enhancements such as new developments in encoding technologies (e.g., new compression formats, new pre-processing techniques, etc.) for generating video for transmission to the remote location.
Aside from the upstream bandwidth requirements, retransmission of content actually present on a premises recording device has several additional disabilities, including the need to maintain the recording or storage device powered up at all times when an upstream transmission may be required, as well as the finite storage volume limitations of the device which can effectively limit the user's selection for content.
Moreover, the viewer must incur added expenses to establish a connection between his television network and the IP network (e.g., must obtain a cable modem and Internet service in addition to the MSO content delivery service). This connection must also have sufficient bandwidth to accommodate “slinging” of the desired content.
Using the aforementioned prior art approaches, content owners also generally cannot protect their copyright and distribution rights, since the Slingbox or comparable device is generally agnostic to the content it is “slinging”, as well as the location or address to which the content is being delivered. Hence, copyrighted content can be intentionally or unintentionally directed to remote domains or environments which may or may not have copyright protection or digital rights management (DRM) capability. In a particularly troublesome case, the remote device to which the content is transmitted may comprise a peer in a peer-to-peer (P2P) file-sharing network environment (such as Kazaa, Morpheus, etc.), thereby facilitating broad distribution of the copyrighted content over the P2P network, e.g., the Internet.
Content owners may further be concerned with the reproduction of copies of their content within the network for distribution purposes. For example, a network operator may have restrictions on replicating and/or distributing content received from the content source. Certain activities are generally recognized as not being in violation of a content owner's copyright. For example, so called “time shifting” (i.e., recording or storing the content for later viewing), and “space shifting” (i.e., moving content from one device or medium to another) of content owned by a purchaser in certain circumstances are recognized by U.S. courts as not violating copyrights. However, the application of such rules is typically quite fact-specific, and hence each situation must be individually analyzed. In short, the content source or copyright owner must have assurances that the network operator (e.g., MSO) which is entrusted with their valuable content will process and distribute this content within the limitations of the law, and not expose the content to undue risk of unauthorized reproduction or distribution.
Based on the foregoing, there is a need for improved apparatus and methods for enabling secondary (e.g., remote) access of content such as television programs without repetitious or inefficient use of network bandwidth. Such apparatus and methods would, in addition to efficiently and flexibly delivering content to one or more remote locations, also ideally protect the content by enforcing authentication and/or rights protection rules.
Additionally, when the network delivers programs in digital format, such apparatus and methods would preferably be able to preserve the high visual quality.
These features would also be provided using substantially extant network infrastructure and components, and would be compatible with a number of different client device and delivery systems including both wired and wireless technologies.
The present invention satisfies the foregoing needs by providing improved apparatus and methods for the delivery of content over a network to one or more remote nodes.
In a first aspect of the invention, a personal content distribution system is disclosed. In one embodiment, the system comprises: a first network adapted for distribution of content to a first device at a first location; a personal content server operatively communicating with the first network; and a second network in data communication with the content server and adapted to receive a request to access first content from a second device at a second location remote from the first location. The distribution system is operative to selectively insert second content with the first content for delivery to the second device.
In one variant, the selective insertion of the second content is based at least in part on the second location. The content that is specifically adapted to one or more attributes of the second location, the one or more attributes being selected from the group consisting of: (i) local weather, (ii) local sports teams, and (iii) local television programming.
In another variant, the second content is selected for the selective insertion based at least in part on the date and/or time of day.
In yet another variant, the second content is topically related at least a portion of the first content.
The second content may also stored in a variety of different formats, each of the formats adapted for a given software environment within the second device.
In still another variant, the access comprises delivery of the content to the second device, and the personal content server is operative to dynamically select at least one of the following for delivery of the content to the second device: (i) encoding/decoding format; (ii) conditional access format; and (iii) the network interface over which the content is delivered to the second device.
In another embodiment, the system further comprises a third network in communication with the first network; wherein the second device is capable of moving between the second and third networks, and the personal content server is adapted to authenticate the second device at each of the second and third networks.
In a second aspect of the invention, a client device architecture adapted for delivery of content over a network is disclosed. In one embodiment, the architecture comprises: a server disposed substantially within a content-based network and adapted to serve content requests from client devices; a content source in data communication with the server for providing first content thereto; and a management process in operative communication with the server, the management process being adapted to evaluate requests from one or more client devices associated with a remote network in data communication with the content-based network for access to the first content, and to select and provide second content substantially with the primary content in response to the request.
In one variant, the evaluation of the requests comprises analyzing the location of a client device issuing one of the requests, and the selection comprises selecting second content appropriate to that location.
In another variant, the evaluation of the requests comprises analyzing the configuration of a client device issuing one of the requests, and the selection comprises selecting second content appropriate to that configuration of client device.
In still another variant, the evaluation of the requests comprises analyzing metadata associated with the first content requested to identify a context, and the selection comprises selecting second content related to the context.
In a third aspect of the invention, a method of delivering content over a network is disclosed. In one embodiment, the method comprises: receiving a request for access to first content via a first network from a first device; selecting second content for inclusion with the first content based at least in part on the context of the first device; and causing delivery of the first and second content to the first device.
In one variant, the network comprises a cable television network, and the delivery of content is conducted according to a substantially “point-to-point” session based protocol. In another variant, the network has a broadcast switched architecture (BSA) and a plurality of hub sites, and at least the act of selecting is performed by a software process running on a server disposed at one of the hub sites. Apparatus at the hub site may be used to insert the second content into the first content if desired.
In a fourth aspect of the invention, a method optimizing bandwidth usage within a cable television network is disclosed. In one embodiment, the method comprises: providing first and second content at a first node of the network; distributing the first and second content from the first node to a second node in response to a request for delivery originated from the second node; receiving a request for delivery for the first content from a third node, the third node not being part of the cable television network; selecting third content based at least in part on the request; and causing delivery of the first content and the third content to the third node.
In one variant, the delivery of at least the first content occurs from the first node, and without having to transmit the first content from the second node to the third node.
In another variant, the second content comprises advertising or promotional content applicable to the second node, and the third content comprises advertising or promotional content applicable to the third node, the second content being substantially non-applicable to the third node.
In a fifth aspect of the invention, server apparatus adapted for use in a content-based network is disclosed. In one embodiment, the server apparatus comprises: a storage device; a processor in data communication with the storage device and adapted to run at least one computer program thereon, at least a portion of the at least one program being stored in the storage device; a first network interface in data communication with the content-based network; a second network interface in data communication with a remote network; and a data interface in data communication with a content source. The at least one computer program is adapted to: receive a request for access to first content from a remote client device in data communication with the remote network via the second network interface; evaluate the request to determine whether second content associated with the first content for delivery via the content-based network is appropriate for delivery to the remote network; and based at least in part on the evaluation, selectively replace at least portions of the second content with the third content before delivery of the first content to the remote network.
In one variant, the content-based network comprises a cable television network, and the at least one computer program is further adapted to cause a session to be created between the apparatus and the remote client device substantially over the second network, the session delivering the requested first content.
In another variant, the at least one computer program is further adapted to cause a session to be created between a proxy of the apparatus and the remote client device substantially over the second network, the session delivering the second or third content as applicable.
In a sixth aspect of the invention, a method of doing business over a network is disclosed. In one embodiment, the method comprises: receiving a request for first content from a user in communication with the network; and selecting second content for inclusion with the first content based on at least one of (i) the identity of the user; and (ii) the location of the user.
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 term “browser” refers to any computer program, application or module which provides network access capability including, without limitation, Internet browsers adapted for accessing one or more websites or URLs over the Internet, as well as any “user agent” including those adapted for visual, aural, or tactile communications.
As used herein, the terms “client device” and “end user device” include, but are not limited to, set-top boxes (e.g., DSTBs), digital television sets, personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), such as for example an iPod™ or Motorola ROKR, 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, etc.), Real (RealVideo, etc.), AVC/H.264, AC-3 (audio), DiVX, XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, or 9), 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.) and the like.
As used herein, the term “conditional access” refers to any access control scheme, whether implemented in hardware, software, or firmware (or combinations thereof), including without limitation members of the “Powerkey” family (Powerkey Book 2, Powerkey Book 3, etc.), NDS (including VideoGuard, mVideoGuard, etc.), ANSI/SCTE Standard 52 2003 (DVS-042), incorporated herein by reference in its entirety, and Motorola/General Instrument DigiCipher® family (DigiCipher II, etc.). These can be implemented using, for example, the so-called “CableCard” plug-in security module access technology, a downloadable CA system (DCAS), or otherwise.
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 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. The term “customer premises equipment” (CPE) includes such electronic equipment such as set-top boxes (e.g., DSTBs), televisions, cable modems (CMs), embedded multimedia terminal adapters (eMTAs), whether stand-alone or integrated with other devices, Digital Video Recorders (DVR), gateway storage devices (Furnace), and ITV Personal Computers.
As used herein, the term “database” refers generally to one or more tangible or virtual data storage locations, which may or may not be physically co-located with each other or other system components.
As used herein, the term “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 or function whereby content sent over a network can be recorded and selectively recalled, including without limitation so-called “personal video recording” (PVR) functions or devices. Such DVR may be dedicated in nature, or part of a non-dedicated or multi-function system.
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. DOCSIS (version 1.0) is a standard and protocol for internet access using a “digital” cable network. DOCSIS 1.1 is interoperable with DOCSIS 1.0, and has data rate and latency guarantees (VoIP), as well as improved security compared to DOCSIS 1.0. DOCSIS 2.0 is interoperable with 1.0 and 1.1, yet provides a wider upstream band (6.4 MHz), as well as new modulation formats including TDMA and CDMA. It also provides symmetric services (30 Mbps upstream).
As used herein, the term “head-end” 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 any information source/receiver including, inter alia, free-to-air TV channels, pay TV channels, interactive TV, and the Internet. DSTBs may take on any configuration, and can be retail devices meaning that consumers may or may not obtain their DSTBs from the MSO exclusively. Accordingly, it is anticipated that MSO networks may have client devices from multiple vendors, and these client devices will have widely varying hardware capabilities. Multiple regional head-ends may be in the same or different cities.
As used herein, the term “integrated circuit (IC)” refers to any type of device having any level of integration (including without limitation ULSI, VLSI, and LSI) and irrespective of process or base materials (including, without limitation Si, SiGe, CMOS and GaAs). ICs may include, for example, memory devices (e.g., DRAM, SRAM, DDRAM, EEPROM/Flash, ROM), digital processors, SoC devices, FPGAs, ASICs, ADCs, DACs, transceivers, memory controllers, and other devices, as well as any combinations thereof.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet.
As used herein, the terms “local” and “remote” refer generally to devices, entities, or users that are serviced by substantially different communications channels. These terms are intended to be relative, and bear no physical or absolute reference or connotation as to the placement of the communication channels or the served device, entities or users. For example, a “local” network may comprise the MSO cable or satellite network, whereas a “remote” network may comprise the Internet or a LAN/WAN/MAN, the latter which may serve the very same premises.
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, 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 term “modem” refers to any kind of modulation or demodulation process or apparatus including without limitation cable (e.g., DOCSIS compliant) modems, DSL modems, analog modems, and so forth.
As used herein, the terms “MSO” or “multiple system operator” refer to a cable, satellite, or terrestrial network provider having infrastructure required to deliver services including programming and data over those mediums.
As used herein, the terms “network” and “bearer network” refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications or networking protocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP, 3GPP2, WAP, SIP, UDP, FTP, RTP/RTCP, TCP/IP, H.323, etc.)
As used herein, the term “network agent” refers to any network entity (whether software, firmware, and/or hardware based) adapted to perform one or more specific purposes. For example, a network agent may comprise a computer program running in server belonging to a network operator, which is in communication with one or more processes on a CPE or other device.
As used herein, the term “network interface” refers to any signal or data interface with a component or network including, without limitation, those of the Firewire (e.g., FW400, FW800, etc.), USB (e.g., USB2), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E, etc.), MoCA, Serial ATA (e.g., SATA, e-SATA, SATAII), Ultra-ATA/DMA, Coaxsys (e.g., TVnet™), radio frequency tuner (e.g., in-band or OOB, cable modem, etc.), modem, WiFi (802.11a,b,g,n), WiMAX (802.16), PAN (802.15), or IrDA families.
As used herein, the term “purchase” shall mean without limitation any sale, agreement for sale, transfer of funds, promise to transfer funds, barter arrangement, promotional or incentive agreement or arrangement, virtual ownership, subscription, or other relationship wherein consideration of any kind is exchanged between two or more parties (or their proxies).
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, QAM-16, QAM-64, QAM-256 etc.) depending on details of a cable network. A QAM may also refer to a physical channel modulated according to said schemes.
As used herein, the term “recording medium” refers to any material, component, collection of components or device adapted to store information in a substantially permanent or semi-permanent state. Exemplars of recording media include, without limitation, magnetic media, integrated circuits (e.g., RAM or ROM), optical media, chemical media, and atomic- and subatomic-level storage structures (e.g., crystalline structures, quantum or spin states, etc.).
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 “user interface” refers to, without limitation, any visual, graphical, tactile, audible, sensory, or other means of providing information to and/or receiving information from a user or other entity. A user interface may comprise, for example, a computer screen display, touch screen, speech recognition engine, text-to-speech (TTS) algorithm, and so forth.
As used herein, the term “Wi-Fi” refers to, without limitation, any of the variants of IEEE-Std. 802.11 or related standards including 802.11 a/b/g/n.
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, analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
Overview
In one salient aspect, the present invention provides, inter alia, improved apparatus and methods for allowing access to primary content (e.g., program viewing) and secondary content (e.g., promotions, advertising, etc.) delivered over a content-based network via other networks or communication channels outside of the content-based network. For example, in the context of a cable television network, programming or other content delivered to a subscriber over the cable network can be accessed via other networks such as the Internet, LANs/WANs/MANs, a wireless service provider (WSP) network, cellular service provider (CSP) network, or even a satellite network. Methods and apparatus for dynamic secondary content insertion (e.g., replacement of dated or geographically inappropriate advertisements or promotions) are disclosed, thereby allowing the MSO or other network operator to adjust the secondary content to make it more applicable to the remote user's context (e.g., location, hardware/software environment, date/time, etc.).
In one embodiment, the invention comprises a personal content server located, e.g., at the head-end of the bearer (cable) network; this server distributes content to the remote requesting location(s), thereby eliminating repetitious traffic to and from subscriber's premises to fulfill the requests for remote content delivery. Relevant secondary content is also identified and selectively inserted for delivery to the requesting user.
In one variant, information relating to the requesting subscriber's prior activity for the requested content is used as a basis for authorizing delivery of the remote content. For example, the remote content manager may determine whether the requested program was previously stored on the subscriber's DVR attached to the local (cable) network. This information is gathered by either querying the DVR or by querying a process at the head-end for the program titles stored on the DVR.
In another variant of the invention, when the subscriber wishing to access content (e.g., watch a program) from a location outside the bearer network does not have a DVR on his premises, the personal media management server communicates with either a “network DVR” or a “virtual DVR” maintained for the subscriber at the head-end or other location outside of the subscriber premises in order to determine remote access privileges.
In yet another variant, activity or status of the tuner(s) within the local premises device is used as the basis for controlling or determining delivery of the requested content to the remote location; e.g., the remote user can watch that channel to which the premises tuner is currently tuned.
The requested primary content (as well as the secondary or inserted content) advantageously may comprise video, audio, gaming content, software applications, stored data, or any other form of data which can be delivered over a network. On-demand content delivery (including trick mode and similar functions) is also optionally supported through the establishment of a session between the remote client device and a VOD server within the cable head-end and control using extant session and stream control protocols (e.g., LSCP).
Broadcast or “live” content can also be accessed via the secondary network approach of the present invention. For example, one variant allows the broadcast streams to be switched via the head-end to the remote node via the secondary network (e.g., Internet, WAN, CSP network, etc.). Another variant of the invention places the content server function at a hub site of a broadcast switched architecture (BSA), thereby allowing for a close coupling between the hub switch state and the remote delivery for individual subscribers.
The improved methods and apparatus of the invention are readily implemented using substantially existing infrastructure, thereby obviating significant modifications or expense in implementing such capability.
An operational and business rules “engine” useful in implementing various operational or business goals is also disclosed.
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 architecture used in conjunction with a “secondary” communication channel or network, the general principles and advantages of the invention may be extended to other types of networks and architectures where secondary delivery of content is required or desirable, whether broadband, narrowband, wired or wireless, content or data, or otherwise, and irrespective of topology. Hence, the following description is merely exemplary in nature.
It will also be appreciated that while described generally in the context of a network providing service to a consumer (i.e., home) end user domain, the present invention may be readily adapted to other types of environments including, e.g., commercial/enterprise, and government/military applications. Myriad other applications are possible.
It is further noted that while aspects of the invention are described primarily in the context of 6 MHz RF channels within the HFC network, the present invention is applicable to any frequency/bandwidth, such as for example 8 MHz channels.
Moreover, while generally described in terms of content delivery over discrete QAMs or channels, relevant portions of the invention can be used in conjunction with multiplexing algorithm and wideband tuner apparatus such as that described in co-owned and co-pending U.S. patent application Ser. No. 11/013,671 filed Dec. 15, 2004 and entitled “Method And Apparatus For Wideband Distribution Of Content”, incorporated herein by reference in its entirety.
Also, while certain aspects are described primarily in the context of the well-known Internet Protocol (described in, inter alia, RFC 791 and 2460), it will be appreciated that the present invention may utilize other types of protocols (and in fact bearer networks to include other internets and intranets) to implement the described functionality.
Furthermore, as discussed in greater detail subsequently herein, the generalized network of
The data/application origination point 102 comprises any medium that allows data and/or applications (such as a VOD-based application, gaming application, 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 servers 104, 105) that can be accessed by a distribution server 104 or VOD server 105. Exemplary embodiments of a “converged” CPE (i.e., CD) of the invention are also described subsequently herein.
Referring now to
The architecture 150 of
Content (e.g., audio, video, data, applications, etc.) is provided in each downstream (in-band) channel associated with the relevant service group. To communicate with the head-end 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.
It will also be recognized that the multiple servers (broadcast, VOD, or otherwise) can be used, and disposed at two or more different locations if desired, such as being part of different server “farms”. These multiple servers can be used to feed one service group, or alternatively different service groups. In a simple architecture, a single server is used to feed one or more service groups. In another variant, multiple servers located at the same location are used to feed one or more service groups. In yet another variant, multiple servers disposed at different location are used to feed one or more service groups.
As shown in
“Switched” Networks
Switching architectures allow improved efficiency of bandwidth use for ordinary digital broadcast programs. Ideally, the subscriber will be unaware of any difference between programs delivered using a switched network and ordinary streaming broadcast delivery.
Co-owned 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”, which issued as U.S. Pat. No. 8,713,623 on Apr. 29, 2014 and is 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 CPEs (or CD). 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.
Personal Content Delivery Architecture
As shown in
The remote network 204 interfaces with the server entity 210, the latter receiving requests from a remote client device 214 (e.g., a PMD, remote PC, laptop, etc.). As discussed in greater detail subsequently herein, these remotely-issued requests are serviced by the server entity 210 based on one or more criteria.
It will be recognized that while the terms “remote” and “local” are used, these terms carry no specific connotation relating to distance or location, but rather are merely meant to differentiate between the various domains of the system 200. For example, the “remote” network 204 may actually be physically proximate or within a subscriber's premises along with the local network 202. Similarly, extensions of the local network 202, such as at the subscriber's premises via a LAN/WAN, or WiFi interface, may place the local client device 208 or LCD (e.g., a PMD, laptop, or other mobile device) more distant from the server entity 210 than the remote device.
Furthermore, while one of each the local and remote networks are shown in
The content manager 238, media processor 240, and content server 242 may be physically and/or logically integrated into one device or process, or maintained as separate devices/processes even located at disparate locations, as described further below. Alternatively, the function may be implemented in a distributed manner where one or more functional aspects are implemented on multiple platforms.
The content manager acts as the overall logical control or supervisory process for the remote content delivery functionality described herein. In this regard, the CM 238 acts as somewhat of an overlay onto existing logical and physical processes occurring within the network including, e.g., authentication of subscribers, instantiation of VOD sessions, switching of BSA hubs to deliver content to various subscribers, etc.
The media processor 240 acts to process media ingested by the head-end 150 (or stored therein, etc.) before delivery to the requesting remote client device (RCD). For example, the RCD might require the media to be encoded in Real or AVC format versus MPEG-2, may require compression, etc. Alternatively, the bitrate of the local network program may be different than the bandwidth available to the RCD via the remote network. In such a case, the media processor 240 may perform the function of rate shaping the content using any number of different implementations recognized by those of ordinary skill. One such exemplary implementation performs rate shaping by setting a target rate where the input bitstream is converted to a constant bitrate stream. In another implementation, the rate shaping is performed based on feedback from the network connection between the streaming content source and the RCD. In yet another implementation, the rate shaping is performed in multiple stages, depending on hops in the network and their availability of downstream bandwidth.
In certain implementations, the media processor may also add or convert portions of the content before transmission. For example, the media processor may include a watermark or other steganographic or DRM data on outgoing video, or encrypt it (e.g., according to an AES or DES encryption algorithm).
The media processor function may also be implemented by storing multiple copies of the content suitable for a variety of network conditions, and picking the appropriate copy as needed. This method becomes especially useful when the remote or visited network is a network that supports a well known parameter set or requirement; e.g., a prescribed data transfer speed (such as e.g., 56 Kbps or 384 Kbps), QoS, etc.
The content server 242 may comprise any server capable of serving the content to the requesting RCD, including for example existing broadcast, application or VOD servers (
On the remote network side 204, a remote client device (RCD) 214 is in communication with the remote network 244 which in turn is coupled to the head-end 150 via a remote network gateway (RNG) 246. The RNG can take any one of several forms, depending on the nature of remote or visited network. The exemplary RNG of
The RNG may also be equipped with 802.1x/RADIUS authentication capability, in event barring communications issued by the RCD from passing without proper authentication by the RADIUS server. This approach helps limit “spoofing” of the head-end processes (including the content manager) by surreptitious entities seeking to gain unauthorized access to the content distributed by the MSO. This can also be used as part of a multi-layer system; such as where the aforementioned 802.1x/RADIUS function or similar is layered with an independent authentication performed by the TA or a designated proxy (e.g., trusted authentication authority).
The exemplary architecture of
Another example of a remote network according to the invention is a wide area wireless network such as cellular telephony network. In such a case, the remote network must be capable of following user commands from his/her mobile phone to reach the head-end servers, and also be able to forward personal media streamed by the content server 242 to the RCD. Exemplary methods and apparatus for implementing such connectivity and interoperability between an MSO network and a cellular or other such mobile device network are described in co-owned U.S. patent application Ser. No. 11/258,229 filed Oct. 24, 2005 and entitled “Method and Apparatus For On-Demand Content Transmission and Control Over Networks”, incorporated herein by reference in its entirety. This disclosure provides exemplary apparatus and methods for accessing data (such as video, audio or data files) over a network according to download or “on demand” paradigms. In one embodiment, the network comprises a cable television network connected with a CSP (cellular service provider) or wireless service provider (WSP), and on-demand content delivery is accomplished via a “point-to-point” approach wherein a session is established between a content receiving entity (such as a cellular telephone) and a distributing entity (e.g., a VOD server). Session establishment and data flow control are advantageously implemented using protocols and bandwidth that are typically used for (i) providing on-demand services to subscribers within the cable network, and (ii) delivery and control of streaming multimedia to client mobile devices.
In one embodiment, session establishment and data flow control are advantageously implemented using protocols and bandwidth that are typically used for delivery and control of streaming multimedia to a subscriber's LCD 208, such as a cable network's VOD infrastructure. The content delivered may be an MPEG transport stream, for example, in either standard definition (SD) at 3.75 Mbps, or high definition (HD) at 15 Mbps (or any increments or multiples thereof).
The receiving client device, via a fixed-or soft-function key or other such user interface, can also invoke FF, REW or other “trick mode” functionality with respect to the video streamed over the wireless network (and any intermediate fiber/wired links within the IP network). This feature can also be used as a complement to other existing modalities, such as “real time” streaming or simply transferring the complete video/audio data file(s) to the requesting client for storage (and provision of “trick mode” functions) thereon.
The on-demand content provided to a subscriber's mobile device can be billed to the same MSO account held by the subscriber for the cable network services provided to the subscriber's premises. This allows for a convenient “bundling” of services, obviating a need to pay for access to this additional on-demand content on a separate bill or billing account.
The on-demand access of content according to the invention is also advantageously agnostic to the type of session establishing protocol or data transfer protocol used, thereby allowing the transfer of content to a client mobile device over virtually any type of multimedia-capable cellular or wireless bearer network (including e.g., 3G, CDMA, TDMA, 802.11, etc.).
The present invention can make use of packet-over-circuit technologies to extend its reach; e.g., use of UMTS CDMA air interface, RAN, etc. Almost all current cellular phones have WAP or similar Internet access technology (which accesses distant WAP server site via a gateway or similar infrastructure), but these are generally not equipped to handle any significant download sizes due to very limited bandwidth. The exemplary use 3G IMS increases bandwidth significantly, and hence is a natural choice to carry video content (even streamed).
The disclosed apparatus and methods also advantageously provide for upload of content to a server or other network entity, and the uploaded content can then be downloaded and “VOD'd” by a linked subscriber. For example, using a cellular phone camera, microphone, etc., user can stream video up to the VOD server for download/VOD access by others who have authorized access to the content-based network (perhaps other family members or friends), so these other persons can watch the uploaded content on their LCD 208 or other desired platform (e.g., PC).
Another example of remote network comprises a user connection to the Internet over a wireless network or interface. One such wireless network might comprise an 802.11 a/b/g/n network, PAN, or 802.16 WiMAX interface.
Yet another example of a remote network comprises an Internet Service Provider's (ISP) network when the user accesses the Internet through his ISP connection and then makes a request over the Internet to view personal media form the MSO (local) network.
Alternatively, the RCD may comprise a WAP-enabled client (e.g., PDA or other PMD) that interfaces with a WAP gateway, the latter which may comprise or be integrated with the remote network gateway (RNG) previously described.
It will be appreciated that the present invention also contemplates situations when the subscriber/RCD is not static in the remote network 204, but is mobile within that network, and may also transition from one remote network to another. Because the personal content delivery of the present invention can be implemented by delivery technologies that typically are enabled for such mobility, IP or comparable mobility solutions can be used consistent with the invention in order to ensure that a subscriber is able to receive their content when making a transition from one network to another. In one embodiment, the exemplary content manager 238 or MP 240 may contain a functional process (e.g., algorithm) that monitors for such transitions, including changes in bandwidth available for media streaming. For example, when a subscriber makes transition from a wide area network such as 3G network to a more localized 802.11 Wi-Fi network, the bandwidth available for streaming may increase substantially. The MP 240 then will be appropriately instructed by the algorithm, such as via inter-process messaging or communication between the CM 238 and the MP 240, to increase the bandwidth of outbound personal content streaming session.
The present invention can be used with any device capable of communication over the network and capable of receiving and utilizing the distributed content (e.g., displaying video streams). The RCD may comprise a wired device, such as a laptop or desktop personal computer or wireless receiver. The RCD may implement receive, decode and display capabilities for content on a single platform (e.g., a mobile phone), or on more than one platforms (e.g., a cable or other modem, and a PC connected to the modem and capable of decoding and displaying media).
The RCD may also have the ability to provide enough credentials on behalf of the user/subscriber, so that the content manager 238 is able to ascertain that the content access request is from a subscriber of the local network service (e.g., MSO). This capability may be implemented within the RCD via, e.g., a user interface for the subscriber to be able to provide username/password, or alternatively in the form of a digital authentication technology such as a SIM card for mobile phones.
The content source 206 shown in
Furthermore, it will be recognized that virtual content recording services and apparatus may be used consistent with the present invention in order to provide, inter alia, extended storage capabilities and access to the remote (or local) subscriber(s). See, e.g., the methods and apparatus disclosed in co-owned U.S. patent application Ser. No. 10/626,051 filed Jul. 24, 2003 and entitled “Technique for Providing a Virtual Digital Video Recorder Service Through a Communications Network”, which issued as U.S. Pat. No. 7,457,520 on Nov. 25, 2008 and is incorporated herein by reference in its entirety. In this manner, the size of the accessible “library” of stored content available to a subscriber is not limited to that of physical devices on their premises. For example, were the system of
The architecture of
One advantage provided by the present invention is the ability for the head-end 150, BSA hub site, or other such network node to transmit or relay content in a packetized digital format to the network address of the RCD, thereby avoiding the potentially signal-degrading analog-to-digital conversion previously described under prior art approaches.
Another advantage of such a system is the use of the same strong encryption used to deliver the high-value content over the local network when sending the content stream to the subscriber's remote or visited network.
Furthermore, another advantage provided by the architecture used in the exemplary embodiments of the invention relates to the fact that upstream bandwidth limitations that would be imposed upon prior art solutions such as the Slingbox are not present in this architecture. For example, it is possible that between the content server and the remote client device 214 located in the visited network, comparatively high (e.g., multi-megabit) bandwidth is available for streaming content. Accordingly, the quality of programming that can be streamed using this high-bandwidth connection or network is higher, since the architecture is not constrained by the typical upstream bandwidth rates (e.g., 384 Kilobits per second in a typical cable system) that support only a minimal quality video. Hence, by removing the “choke point” of the upstream channels from the premises to a distribution node, delivery of the content from the head-end or other upstream node in the network to the client in the remote network can occur at potentially greater bandwidths. This can be analogized to removing a flow restriction in a pipe capable of carrying much higher flow rates than those which the restriction can accommodate.
Moreover, the limited upstream bitrates associated with the prior art techniques make it effectively impossible to stream high definition (HD) programming. In contrast, according to one embodiment of the present invention, high definition (HD) programs can be streamed to the visited network client device since the upstream “bottleneck” of the downstream or edge portions of the MSO distribution network is removed.
Remote RCD Configuration
In another embodiment of the invention, the RCD can be dynamically configured by content manager 238 (or content server 242) in order to enable certain types of functionality. This dynamic configuration approach can be extended to, e.g., the codec configuration (e.g., MPEG-4, AVC, Real, etc.), the conditional access (CA) technologies, and network interfaces associated with delivery of the content, such as via the exemplary methods and apparatus of co-owned U.S. patent application Ser. No. 11/363,577 filed Feb. 27, 2006 entitled “Methods and Apparatus for Selecting Digital Coding/Decoding Technology for Programming and Data Delivery” and issued as U.S. Pat. No. 7,916,755 on Mar. 29, 2011, U.S. patent application Ser. No. 11/363,578 filed Feb. 27, 2006 entitled “Methods and Apparatus for Selecting Digital Access Technology for Programming and Data Delivery” and issued as U.S. Pat. No. 8,170,065 on May 1, 2012, and U.S. patent application Ser. No. 11/364,147 filed Feb. 27, 2006 entitled “Methods and Apparatus for Selecting Digital Interface Technology for Programming and Data Delivery” and issued as U.S. Pat. No. 8,718,100 on May 6, 2014, respectively, each of the foregoing being incorporated herein by reference in its entirety. For example, one RCD 214 may have a Powerkey or similar CA capability, while another is enabled for downloadable conditional access (DCAS) within its trusted domain. Accordingly, the head-end server process can configure the CA aspects of the content as appropriate for the relevant CA context, and also trigger other processes (such as DCAS download, key negotiation, etc.) necessary to facilitate the playback of the requested content. In this regard, the server process 242 can be made “self healing”; i.e., where the requesting RCD is not properly configured to play back the content, the necessary configuration changes can be instituted automatically to provide a seamless appearance to the remote user.
The CM/content server can also instantiate a trusted domain within the RCD if one does not already exist. For example, using a downloadable CA (DCAS) approach, the necessary software and firmware if any can be downloaded to the RCD, thereby enabling designation of the RCD as a trusted domain for handling content. Exemplary trusted domain apparatus and methods are described in co-owned U.S. patent application Ser. No. 11/006,404 filed Dec. 7, 2004 and entitled “Technique For Securely Communicating Programming Content”, which issued as U.S. Pat. No. 8,312,267 on Nov. 13, 2012 and is incorporated herein by reference in its entirety, although it will be recognized that other approaches may be used.
In one embodiment, an authorized service domain (ASD) approach is utilized for protecting content delivered to the RCD 214. The exemplary configuration of the ASD comprises a UPnP digital rights management technology that is used by the network operator to protect content using security credentials of a multi-stream cable card or secure microprocessor disposed on the RCD 214. An exemplary ASD service (ASDService) defines a service that runs on the content server 242 and is invoked by the RCD (or the CM 238). The ASDService process in defined for exchanging and authenticating security credentials to the RCD (and any connected devices within the RCD domain).
The exemplary ASDService described herein abides by the UPnP AV Architecture for browsing content, setting up connections, transporting content and finally controlling the flow of the content between devices, although this is by no means a requirement for practicing the invention. The ASDService is a precursor to the UPnP general playback process, and is executed before the remote device can browse as ASD content directory (e.g., maintained by the content server 242 or CM 238) or allow playback.
The exemplary ASD Service also allows an ASD capable rendering device (e.g., RCD) to scan the remote or local domain networks for ASD capable “servers”. Once identified, the RCD can request authentication from the ASD capable servers to view the ASD content directory. The RCD 214 or its proxy selects content from the directory and submits its ASD credentials along with the content ID or other data identifying the content of interest in order to gain access from the server. The submission of the security package is required each time a RCD accesses content in order for the server to maintain counters to comply with “copy once” and “copy never” classified content.
Secondary Content Insertion
In another aspect, the present invention utilizes a dynamic secondary content (e.g., advertisement) insertion process that gives the network operator the opportunity to provide secondary content such as advertisements or promotions that are more tailored or better suited for the primary content (e.g., programming) than that associated with the primary content when it is transmitted to and stored on the subscriber's local or premises equipment (e.g., DVR). Because a program in the exemplary embodiment is streamed from the head-end server (e.g., the content server 242) or another network node upstream of the LCD 208, a decision is made at the time of streaming or delivery of the primary content whether to insert relevant advertisements or other secondary content that is more logically proximate to the primary content or other network context than that associated with the original delivery of the content that is being used as the reference for establishing the current requester's access.
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.
The term “network context” refers to secondary content which bears some logical or deterministic relationship to one or more network operational, business, or other parameters. For example, logically proximate secondary content based on network context may be that which is properly encoded to be delivered over the relevant distribution path, which fits the allotted time, which maximizes bandwidth or profits, etc.
Hence, while the original delivery of the target primary content might have advertising that is effectively randomized in terms of logical proximity or network context, the network operator can, using the apparatus and methods of the present invention, dynamically adjust the secondary content based as desired before it is delivered to the remote user/RCD.
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. For example, a promotion such as “Tonight on NBC” becomes less relevant when the primary content is watched by the subscriber three days later than the original airing of the promotion. However, using the method of the present invention, the promotion could in fact relate to a program that is scheduled to be broadcast on the day that the subscriber watches the promotion. This can be readily determined by any number of means, such as e.g., using the date/time reference associated with the network (e.g., SI reference) as compared to metadata relating to date/time associated with the content. 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 exemplary advertising or secondary content insertion algorithm (not shown) included within the CM 238, or running on the content server 242. The insertion algorithm of the exemplary embodiment can, for example, select secondary content which is contextually, temporally and/or logically related to one or more elements of primary content, the network context, and so forth. The algorithm may comprise, for example, a Boolean, natural language, or other search engine adapted to locate relevant second content based on one or more search criteria. These criteria may be inserted by an MSO operator, or automatically, such as where metadata or other search terms associated with the primary content are extracted and used as the basis of the search. For example, for the foregoing movie “Pirates of the Caribbean”, metadata associated with this movie might comprise the word “Pirate”, which could then be used in the search engine to locate exact (Boolean) or logical (natural language) matches within a database of secondary content, such as the aforementioned advertisement for Disneyland.
Alternatively, a third party “ad server” or other database or source can be used to provide the secondary content for insertion. See, e.g., co-owned and co-pending U.S. patent application Ser. No. 11/198,620 filed Aug. 4, 2005 entitled “Method and Apparatus For Context-Specific Content Delivery” and issued as U.S. Pat. No. 9,286,388 on Mar. 15, 2016, incorporated herein by reference in its entirety, which describes inter alia exemplary context-specific content insertion methods and apparatus, including the exemplary Google “AdSense” suite of services. This suite can be utilized as the basis of the secondary content source in the present invention. The Google “AdSense for Content” provides contextually targeted advertisements to users. Access is provided to a large number of advertisers, and advertisements from these advertisers are served on designated content pages. User sites are compensated for traffic (e.g., “click throughs”) on displayed advertisements, thereby generating revenue for the site operator.
Accordingly, the PCS 242 or other MSO entity in the exemplary embodiment can receive the “targeted” advertising content from Google AdSense or a comparable server, and then insert this content into the primary content (e.g., requested television program or movie) at appropriate locations, such as at the segmentation breakpoints. In one variant, this secondary content can comprise a screen display with links to web pages or the like, that can be actuated using input devices on the user's RCD 214. Alternatively, the MSO can prepare “passive” video related to the returned links. So, in the exemplary context of “Pirates of the Caribbean”, the Google AdSense server might return a link to the Disneyland web page or URL. The MSO (or even the third party server operator, such as Google), may also generate a video corollary to the web page, such as an advertisement for Disneyland rendered in an MPEG-2 or similar format. Note that the advertisement or video can also be web-enabled if desired, such as where the user may not only view the video content (e.g., MPEG stream), but may also actuate an associated link such as via an on-screen display or browser to link them directly to the web page for more information.
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-owned U.S. patent application Ser. No. 11/298,247 entitled “Caption Data Delivery Apparatus and Methods” filed Dec. 9, 2005, issued as U.S. Pat. No. 8,566,887 on Oct. 22, 2013, 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-owned U.S. patent application Ser. No. 11/299,169 entitled “Emergency Alert Data Delivery Apparatus and Methods” also filed Dec. 9, 2005, which issued as U.S. Pat. No. 7,592,912 on Sep. 22, 2009, and is incorporated herein by reference in its entirety.
In one embodiment, the (primary) content stored or routed from the head-end, hub site, or other node is segmented according to a segmentation algorithm of the type well known in the art. For example, an otherwise continuous piece or content can be divided into two or more segments of varying length (or uniform length if desired), thereby allowing for the insertion of secondary content into the “gaps” formed between the segments. The total run-time (e.g., end-to-end) for the primary content and second content can also be controlled by any number of mechanisms including for example: (i) editing or deleting portions of the content contiguous with the segment gaps; (ii) adding “filler” content or small periods of dead air to fill any remaining gaps; and/or (iii) adjusting the coding or delivery rate upwards or downwards slightly in order to make the content run imperceptibly faster or slower, respectively. Alternatively, the added or subtracted run-time added by the secondary content inserted can simply be propagated into adjacent or non-adjacent time slots, and there beyond, so that the whole of the added/subtracted runtime is spread across several program time slots. Similarly, where the start and stop times of programming are not fixed, these can merely be adjusted to provide a seamless flow from primary to secondary content and vice-versa.
The secondary content may also be stored on a content server (e.g., a separate advertising server, the PCS 242 of
The primary and secondary content can also be manipulated 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-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” and issued as U.S. Pat. No. 8,214,256 on Jul. 3, 2012, 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.
In another variant, the LCD 208 and/or RCD 214 can be configured with an OCAP or eBIF enhanced TV application client running thereon which enables the user of that device to respond to network polls, advertising RFIs, or other types of interactive content and interactive advertising. These applications may also be configured to send the user to the appropriate Internet or “walled garden” web site (i.e., one with pre-vetted content or restricted access), for fulfillment of information requests, user submissions, and so forth.
The secondary content insertion or modification processes of the invention can also be “targeted” at, inter alia, particular individuals, demographics, equipment configurations, contexts or location, and so forth. For example, in one variant of the invention, secondary content selected for delivery to the requesting RCD 214 is chosen based on the type of platform or RCD making the request (e.g., secondary content optimized for comparatively lower bitrate, larger text (font) and reduced graphics for mobile phones, etc.).
In another variant, the content or theme of the secondary content itself (as well as optionally its physical parameters) can be used as a basis for selection/insertion. For example, the fact that a user is issuing the request from, or targeting delivery to, a given platform (e.g., a cell phone or a computer) is used to select appropriate secondary content. In this case, cell phones or computers are frequently upgraded or changed out, and hence such users may be more receptive to this type of advertising or promotions than others.
Alternatively, the “location” of the requesting or target platform (RCD) can be used as a basis for selection. As used in the present context, the term “location” can mean either virtual location (e.g., a network address, TUNER ID, MAC, membership in a population or group, number of intermediary router or switch “hops” from the content source, part of a given service group or node, and so forth), or a geographic or physical location (zip code, GPS coordinates, area code, etc.) of the remote device 214. For example, selective replacement of secondary content might be based on such geography or location; e.g., a promotion for a sports event for a local team, or local news, etc. might have limited applicability to a subscriber who is located out of the geographic area. Accordingly, one embodiment of the invention uses secondary content that contains geographic metadata when stored, the metadata being used as the basis for insertion based on a particular geographic location.
The foregoing techniques can also be applied to target secondary content delivery to particular individuals, family members, enterprise employees, etc. For example, mobile phones tend to have one owner/user, so data maintained by the MSO (or obtained from a participating CSP or WSP) to correlate the RCD 214 with a particular owner or individual. This correlation can be used as the basis for targeted content delivery, such as where a vendor or other source identifies that individual as having a particular attribute. For example, the MSO or other network operator might have access to information showing that the owner requesting delivery to their RCD is a Jaguar owner, and that the lease on their vehicle is expiring. Hence, the MSO (either manually or via computer algorithms adapted to analyze such information and select appropriate secondary content for insertion, such as via metadata associated with the secondary content) might select advertising or promotional information relating to a new Jaguar XK-R, thereby hoping to entice the particular user into a new lease or purchase of goods or services for which they have a positive response history. This approach also advantageously can avoid targeting individuals for whom such content is inappropriate; e.g., the family's adolescent daughter, who would clearly not be buying or leasing a new Jaguar.
It will be appreciated that one or more other parameters or metrics can be used to control (at least in part) the selection and/or insertion or provision of secondary content. For example, secondary content selection may also be made a function of date or time of day (e.g., evening program oriented advertisements in afternoon time slots), available network bandwidth, user demographics as a class, the position in which such secondary content is to be inserted relative to the primary content (e.g., previews along the lines of “Next week on 24 . . . ” would likely be more appropriate at the end of an episode of “24” versus at the beginning), as a function of the primary content (i.e., an advertisement for an action movie may be best received when inserted into another action movie), and so forth.
In another embodiment, two or more parameters are used to determine secondary content insertion choices or priority. For example, if the user requesting “Pirates of the Caribbean” also happens to be requesting this content from a location in Southern California, the aforementioned search or management algorithm might use this information to identify and prioritize secondary content that bears more than one dimension or degree of relationship (e.g., an advertisement for the “Pirates of the Caribbean” ride at Disneyland, which also happens to be in Southern California and hence geographically proximate to the requesting user.
Moreover, if the user is specifically identified in the database as having a particular affinity for fine dining, an advertisement for Disneyland's “Club 33” restaurant might also be inserted, thereby providing a multi-dimensional logical (and geographic) proximity.
In this capacity, the secondary content selection and insertion algorithms of the invention are highly adaptive, in that they can dynamically tailor the secondary content perceived by the requesting user much more effectively than based merely on one parameter or criterion.
It will be appreciated that the secondary content insertion apparatus and methods described herein are in no way limited to advertising and/or promotional content. For example, secondary content may comprise a software application for download, data, or other such forms that are selected by the foregoing algorithms as being logically or contextually applicable to the requesting user, device or requested (primary) content.
Third Party Content Authority (CA)
In another aspect of the invention, a third party content source database or other such data repository is used to determine whether a given subscriber or entity (which may be anonymous by virtue, e.g., identification or association of the subscriber's CPE/CD/PMD with the purchased content instead of their actual physical identity) has purchased particular content. For example, in one variant, the user registers with the content source such as during an on-line Internet purchase via the content source website. This information is maintained by the content source and, through agreement or cooperation between the MSO and the content source, provided to the MSO when the latter receives a “remote” request for content from one of its subscribers. Hence, the content server 242 at the head-end or BSA hub can authenticate the user, and also access the content source database to determine if the content has been previously purchased by that user. A correlation table or similar data structure can be maintained by the content source, MSO, or combination thereof, which correlates the various devices under a subscriber's MSO account or otherwise associated with the subscriber. For example, in one variant, the content source maintains a correlation table containing the user's name (or alternatively identification information such as TUNER ID or MAC; see, e.g., co-owned and co-pending U.S. patent application Ser. No. 11/186,452 entitled “Method and Apparatus for Boundary-Based Network Operation” filed Jul. 20, 2005 and incorporated herein by reference in its entirety), as well as network or other addresses (e.g., 32-bit IP address) for other devices associated with the subscriber's MSO account. In this fashion, a remote request being issued from a subscriber's PC, PMD or other such device that is not their CPE/CD at their premises can be immediately recognized and granted access to content that was purchased and downloaded to, e.g., the subscriber's CPE/CD, or was purchased on-line via a web account.
In another variant, two or more content sources (e.g., copyright holders) may create an accessible database (“Content Authority” or CA) for content purchases, somewhat akin to the centralized trusted authority (TA) architecture used for authentication and security purchases. The CA can then act as a local- or even national-level clearinghouse for remote content requests from MSO subscribers. This approach provides a substantially centralized point (or points) of access for network operators of varying types and configurations, so that they may process requests for content from “remote” locations or entities in a timely fashion, thereby also potentially relieving the MSO of having to store data and information relating to content purchases or downloads.
However, it will be appreciated that each MSO may desire to maintain such information for, e.g., backup, quicker service for in-network requests, and so forth. Accordingly, in another variant, the CA described above is used only in the case where the remote content request originates outside of a network or device reflected within the MSO database. For instance, one exemplary algorithm according to the invention accesses the MSO internal or local database (e.g., maintained at the head-end 150) first to determine if a requesting device is reflected in that database. If the requesting device (as identified by, e.g., its MAC address, device ID, TUNER ID, etc.) is not present, then the algorithm calls out to the CA to see if the requesting device is present in the CA database. Conversely, the situation may occur where the requesting device is present in the MSO local database, yet the requested content is not reflected therein. Hence, since the subscriber may have purchased the content via a non-MSO linked source (e.g., an independent third party content source, such as via an Internet website), the algorithm may check the CA database (which would be updated with the third-party purchase of the content) to see if that content has been associated with that device (or subscriber).
The MSO database may also contain a correlation table or other such mechanism for correlating a specific subscriber's identity (e.g., name, SSN, address, etc. and their CPE/CD/PMD identifying data (e.g., TUNER ID, MAC, etc.), so as to permit cross-referencing within the third-party (e.g., non-MSO) databases. For example, such third-party databases may merely have the subscriber's name/address or other such information associated with a purchase of content. However, in order to associate a request from a CPE/CD/PMD that is rendered only in the device's identifying data, the MSO subscriber database must correlate the received device identifying data with a name, so that the third-party database can be cross-referenced.
It will be appreciated that the foregoing cross-referencing function can also be accomplished using an anonymous approach. For example, one exemplary embodiment of the invention comprises use of an “opaque” variable that is generated based on the user's device data via a cryptographic hash; see, e.g., the exemplary approach of U.S. patent application Ser. No. 11/186,452 previously referenced and incorporated herein. The hash and opaque variable frustrate de-encryption or reverse-engineering of the individual subscriber's identity or specific location. Accordingly, the association between the subscriber's actual identity and the content they have purchased can be maintained anonymous, thereby advantageously affording the subscriber total privacy as to their content purchases, yet still affording the ability to perform remote location access.
Similarly, a “two-way” hashing or anonymous association approach can be used, so that anonymity can be maintained within the CA or other third party database as well. This helps alleviate privacy concerns arising from the CA or third-party database. Specifically, in on embodiment, the user's content purchase information can be maintained using a similar yet independent opaque variable or other such mechanism generated by the CA/third-party source. For example, the user's IP address and a device ID (or other information uniquely identifying the user's platform or the user themselves, such as SSN, credit card number, etc.) can be used to generate a cryptographic hash and resulting opaque variable that is correlated to the purchased content. Hence, when an MSO subscriber purchases content via whatever channel outside the MSO network, a unique opaque variable is established and correlated to the content purchased. This second opaque variable can then be forwarded to the MSO, who can add this to a correlation table or other data structure, such as the table in which the MSO's (local) opaque variable is stored. Hence, a correlation between the first (local) and second (third party) opaque variables is established, thereby allowing for end-to-end anonymity for the subscriber/purchaser. The correlation between the two opaque variables can be established by, e.g., a physically and virtually secure database that is discrete from those previously described and which is populated through use of information that definitively correlates the two opaque variables in at least one aspect (e.g., name and SSN/CCN). Hence, surreptitious theft or “hacking” into this secure database by itself would not allow correlation between an individual and their content choices, since it only contains a data structure relating one or more MSO opaque variables to one or more third-party or CA opaque variables. Hence, three different databases are use in the exemplary architecture (and required to correlate an individual to particular content purchases): (i) an MSO local database that correlates the subscriber's unique MSO local opaque variable(s) to that subscriber; (ii) a third-party or CA database that correlates a content purchase to a second opaque variable (e.g., hash generated by way of the user's personal information, etc.); and (iii) a third database that correlates the first and second opaque variables (or sets thereof).
So, as an example of the foregoing, subscriber A (John Smith) first purchases “Pirates of the Caribbean” via third-party website B, which takes the subscriber's CCN or SSN and produces an opaque variable V based on a hash, the variable which is then stored as an entry associated with “Pirates of the Caribbean”. Hence, anyone gaining surreptitious access to this database would merely have a group of opaque variables correlated with various specific content.
Stored at the MSO head-end, or other designated location is a second database which correlates the subscriber's devices with their identity; e.g., John Smith located at 742 Evergreen Terrace has devices P, Q, and R associated with his subscriber account (the devices being identified by opaque variables S, T, and U respectively unique to that subscriber and to each device).
Next, John Smith travels to Paris on vacation, and wishes to access the movie he purchased via the Internet website B previously discussed. Hence, he issues a request using his laptop, which is sent to the cable network head-end via an Internet connection. The opaque variable T is generated for John's laptop, which is associated with John's account as previously noted. However, the laptop opaque variable is merely used to enter the third database; i.e., the opaque variable correlation table, to correlate variable T (laptop) to variable V (purchase of ““Pirates of the Caribbean”” via internet website B). The access to the third database can be conducted on a per-variable basis; i.e., simply search for variable T and return all corresponding “content” variables (e.g., V), and match the returned variable(s) against the current content request. Hence, an “end-to-end opaque” transaction is supported, and anyone gaining access to only one (or even two) of the three aforementioned databases could not affirmatively correlate an individual's identity to particular content purchases, since the opaque variable in the third-party or CA database is not the same as that in the MSO database. This “distributed” approach of dividing the information necessary to correlate purchases to individuals provides enhanced security, since different security measures are employed at the CA/third party as compared to those at the MSO, and hence multiple systems must be “hacked” or breached.
It will be appreciated that in the context of the invention, the term “subscriber” or “user” can refer to more than one entity, such as for example a group of related family members, co-workers at an enterprise, etc. In one variant, a “virtual site license” approach is used, wherein the members of a logically related group (e.g., family members) are given copyright license to purchased content for unlimited personal use, such as for an additional fee. Hence, a set of device ID's (e.g., MAC, TUNER ID, IP address, etc.) for all of the devices in a family can be maintained in the aforementioned database(s), and each member given unlimited remote or local network access. The term “virtual” refers to the fact that the devices of the various members may be mobile, and hence the license is associated with a device rather than a fixed location or premises (although it clearly can be used at a fixed location or premises as well).
Method of Establishing Remote Access
In one embodiment, the client application allows the subscriber to browse (via, e.g., a user interface such as a browser) and select content for delivery from a listing of available titles, with availability of the titles for delivery to the remote device being determined according to one or more criteria described subsequently herein.
In another exemplary implementation, the subscriber may navigate to a universal resource locator (URL) for access to the server hosting the server side component of the personal content distribution DA.
When the viewing request is received at the server entity 210 (e.g., cable network head-end server), an authentication of the request and its origin is performed (step 304) to ensure that the request has come from a user using an RCD 214 that can be served. Such authentication may rely on a variety of methods, including, but not limited to, user identification by password and User ID, known device address, use of digital certificates, public/private keying and other well known cryptographic techniques.
If the server entity 210 determines that the request is not authentic per step 304, an authentication error message is sent to the requesting application (step 306) and the session is terminated (step 312). Such an error message could provide the user explanatory information as to why their request was not successful, an opportunity to re-send the request, and/or contain promotional messages such as a subscription or purchase web page URL. If the user request is authenticated, an interactive session is established (308) in which, among other things, the user is provided with a menu of tasks he can perform and content genre/titles available to him.
When the user makes a selection to access a particular content element (e.g., movie or TV program), an inquiry is made per step 314 to determine if the user's subscription or other access privileges allows him to watch the desired program. If the user is not entitled to watch the program, an appropriate error message is sent (step 310) and the interactive session continues where viewer is given choice to select something different per step 332. Alternatively, the user can merely be presented with a pre-screened listing of available content, such as where only those titles which the user has previously purchased or downloaded to their DVR are presented for selection. Myriad other schemes for presenting the remote user with choices for selection will be recognized by those of ordinary skill when provided the present disclosure, and accordingly are not described further herein.
When the viewer is found to be entitled to access the particular title, a determination is made about the type of title desired (step 316). In the exemplary embodiment relating to media (e.g., video services), three types of titles are generally made available to a user: (i) live or broadcast television, (ii) VOD material available in the local network; and (iii) user programs, either existing on the subscriber's DVR (or networked or virtual DVR, or some such arrangement). It will be appreciated, however, that the invention is in no way limited to media or video-related content, and remote access accordingly can be extended to a number of other different forms of content including without limitation audio content (e.g., music CD's, individual MP3 or comparable files, etc.), gaming or simulation content, software applications, and even stored data (e.g., archived data stored at the head-end or another designated storage location, such as part of a “virtual RAID” service for the subscriber).
If the content desired by the user is a live or broadcast program (or other substantially real-time content delivery modality), the personal content server 242 may check for additional constraints (step 320) that might limit the delivery. These checks may include, e.g., determining the geographic location of the user, and whether the selected content can be delivered to that location at that specific time, such as due to blackouts or other such restrictions. For example, professional sports organizations routinely use blackouts. Such a blackout can be enforced by obtaining information about the subscriber's location from the remote network.
Once the server has ensured that the program viewing request can be fulfilled, further steps to set up the content delivery session are undertaken (step 324). These steps are generally consistent with conventional content delivery techniques, and accordingly not described further herein. The content manager 238 may also select an appropriate origination point from within the local network (or a proxy) for delivering the content to the subscriber. The choice may depend on several factors, including for example location of any remote network gateways or nodes with respect to available content servers 242 in the network.
If the content desired by the user is a title available on the VOD servers of the delivery network, the CM 238 will hand off the streaming session to an appropriate VOD server (step 318). As a result, a VOD delivery session will be instantiated, and the content delivered via the session to the requesting RCD.
If the content desired by the user is a title present on his DVR (step 326), multiple scenarios are possible, including: (i) the DVR is present in the subscriber's premises, or (ii) the DVR is on the network side in the form of a virtual DVR (VDVR) or a network DVR (NDVR). So as to avoid use of upstream bandwidth, if the selected title is present on the premises DVR, a third party content source is accessed to locate and provide the requested content, as opposed to retrieving the content from the premises DVR. Alternatively, if the requested content is already present on the network in the form of a NDVR/VDVR copy, then a call is made to the relevant storage function to obtain the requested content.
When the local network contains a DVR or similar recording device, additional signal exchanges may take place between the content manager 238, and the local/remote devices in order to authenticate, validate, and/or synchronize remote viewing. For example, content providers are concerned about copyright issues associated with recording and storing high value content in unprotected physical devices and formats. Such concerns may be addressed by the present invention by synchronizing or correlating the content stored by the subscriber on the home DVR or other such device; if the content desired to be accessed from the visited or remote location is present on the home DVR, then the remote user will be allowed access. If no correlation exists, then remote access is denied. This approach carries advantages relating to copyright protection and management as well; in simple terms, since the subscriber already has a copy on their DVR, allowing that same subscriber to view the same content except in a remote location is no different than if that subscriber had merely brought their DVR with them to the remote location.
In another embodiment of the invention, the remote content delivery functionality previously described is predicated upon what the subscriber's premises device (e.g., CPE 106 or CD) is presently tuned to, or will be tuned to (such as via an advance reservation or channel tuning selection on an EPG or the like). This information can readily be obtained from the head-end 150 or BSA hub infrastructure, and passed to the content server 242 tasked with serving the remote content request from the RCD. In this fashion, the subscriber makes an affirmative selection of the content that they wish to have delivered to them, and the remote content delivery mechanisms of the invention act as a “repeater” only; i.e., they are coupled to the subscriber's premises tuning activities. Stated differently, the subscriber can be selectively blocked from remotely accessing content that is not presently selected for viewing or recording by a premises device. This approach has advantages from, inter alia, a copyright standpoint, since there is direct coupling between what the subscriber is tuned to at their premises and what they are receiving remotely. Hence, the “time shifting” and “space shifting” paradigms are preserved; the subscriber is merely displacing their viewing location for the content, as if they merely had a very long “wire” from their premises to the remote location.
The foregoing approach also enables a “watch-along” function; i.e., by allowing remote delivery of content that is also contemporaneously being delivered over a channel to which subscriber's LCD 208 is tuned, family or other logically related groups can be serviced in effectively identical fashion. Hence, a parent away on a business trip can be apprised of what his/her children are watching at home with the aforementioned watch-along or repeater function. VoIP or similar audio/video communications (e.g., webcam) between the RCD and LCD domains may also be provided, such as to provide conversational capability between the parent and the family members while all are watching the content, so that all participants feel proximate to one another.
Similarly, the RCD can be configured to communicate with the CM 238 (or even the LCD 208 directly) to enable/disable certain functions or tuning capabilities. For example, the RCD can instruct the CM 238 to disable serving VOD or broadcast content associated with more adult or mature channels to the LCD during certain time periods.
In another embodiment of the invention, the recording of content at the head-end 150, BSA hub site or other MSO node is controlled based on subscriber selections. For example, in one variant, the subscriber must affirmatively select content for recording via their DVR/NDVR/VDVR before it can delivered to the RCD. In this manner, the user has affirmatively selected content for recording, and hence the MSO or other entity tasked with recording the content (if necessary) for delivery to the RCD is in effect simply acting as a remote recorder for the subscriber. In the case where the user has recorded content within an NDVR or VDVR environment, that same copy or recorded content can be used as the basis or source of the content used to service the remote delivery request if desired, thereby causing the MSO or other content recording entity to make only a single copy of the content.
It will be appreciated that the subscriber tuning and the recording actions described above can be invoked remotely if desired as well as locally. Hence, a given subscriber might remotely transmit a “tune” command from their RCD or another device (e.g., via a packetized communication delivered over an in-band-channel, OOB, DOCSIS channel, telephony or other link) to tune their LCD to a given program channel, or invoke a DVR record function, thereby enabling the aforementioned delivery of the same content to the remote location.
Network Server
Referring now to
As previously discussed, the server device 401 also may run the server portion 252 of the content management DA.
The server device 242 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, any required conditioning of the content before delivery (such as the inclusion of watermarking or other data, encryption, generation of encryption key pairs and/or challenges, and so forth) may take the form of one or more computer programs running on a single device disposed within the network (e.g., the content server 242 of
As yet another example, portions of the content distribution functionality may be rendered as a dedicated or application specific IC (ASIC) or DSP having code running thereon. For example, a security processor of the type well known in the art can be used to implement encryption algorithms on the delivered content, and/or to perform key pair generation and the like. Myriad different configurations for practicing the invention will be recognized by those of ordinary skill in the network arts provided the present disclosure.
The server operation can also be masked or controlled by a “business rules” engine” or other logical wrapper or layer as described subsequently herein.
Local Client Device
Referring now to
In the case of HFC or satellite networks, the LCD 208 in one embodiment comprises a CPE in the form of a set-top box with a tuner stage or front end adapted for interface with the relevant physical medium (e.g., connected to the coaxial cable, or a satellite antenna). The LCD 208 may or may not include DVR/PVR functionality. Also, the LCD may not be a physically separate or stand-alone piece of equipment but be integrated into another device, such as in the case of a cable-ready television set.
The LCD 208 of
The exemplary LCD 208 further comprises a personal content or media application, which allows a user to manage his personal content. Such management includes, but is not limited to, the ability to browse through content stored to see which are available for viewing, select content for local viewing, and configure various parameters associated with the remote access (e.g., user logon names, passwords, etc.). As previously described, the content available for viewing may be stored locally, or alternatively may be stored remotely, such as at the head-end, BSA hub, or even a third party content source.
The personal content application is also responsive to a network-side application (e.g., server portion of a DA) that queries the LCD to check on the content titles stored on the LCD, and other data related thereto.
In one implementation, the client program resident on the LCD 208 tracks and reports user activity related to personal content viewing to the relevant server(s) for each LCD. This activity tracking is useful from a number of perspectives, including: (i) determining remote access to content that has been stored or viewed locally; (ii) in billing; and (iii) in determining when programs are added or deleted from the local storage (e.g., subscriber's DVR). This tracking can also be performed in a substantially anonymous fashion, such as through use of cryptographic hashes of TUNER ID, MAC, and similar variables as described in detail elsewhere herein. Such mechanisms allow for specific identification of the LCD 208 which has recorded or accessed content, without necessarily having to know the subscriber's identity.
Furthermore, an application on the LCD 208 can be made to be responsive to the user's commands to control the DVR from the remote or visited network 204. Such a logical connection from the remote network to the LCD can be implemented using any number of different approaches, including direct communications between the LCD 208 and the RCD 214 (e.g., via Internet), relayed communications that pass through the MSO (local) infrastructure (e.g., RCD 214 to CM 238 to LCD 208), and so forth. Allowing the subscriber to set up such a connection provides a remote management interface to managing the LCD to perform personal media related functions, among others, thereby adding significant flexibility to the operation and utilization of the remote content access functionality.
The converged premises device can also provide a trusted domain for content or data, as well as allowing a subscriber total mobility in the home by not limiting content or data to any one viewing/access location. For example, content or data may be accessed on any monitor in the premises, as well as on a PC or personal media device (PMD).
A wired home network utilizing existing coaxial cable in the premises is also created, using e.g., an Ethernet-to-coaxial bridge technology based on the MoCA specification. This allows existing devices and DVRs to connect and share content with the CD, and also allows the network operator (e.g., MSO) to control and manage the premises coaxial network.
The CD is also advantageously accessible via any remote device with internetworking (e.g., Internet) capability, thereby allowing personal content to be accessed by the user (or other entities such as the content manager 238) from outside the premises.
Business Methods and Considerations
Various exemplary business-related aspects of the remote content delivery technology previously discussed herein are described in detail.
In one embodiment, remote access capability is provided as an incentive or feature as part of the subscriber's subscription plan. Hence, this approach treats the remote location as merely an extension of the subscriber's premises, thereby requiring no differentiation between the remote and local domains.
In a second embodiment, streamed content or data sent to a RCD (e.g., cellular telephone, PDA, laptop, etc.) is differentiated (from a billing perspective) from that delivered to the subscriber's premises, and billed directly to the subscriber's MSO account, such as via their monthly cable TV bill. The billing module 152 or other comparable process software at the MSO head-end is configured to obtain the relevant data regarding the subscriber's remote device usage, which is then integrated with that subscriber's other activity to generate a monthly statement. Such data may comprise, for example, the number of movies or other content the subscriber has downloaded during the past billing cycle. As an alternative to the foregoing “per-use” model, the subscriber may be offered a plan wherein they can obtain an unlimited (or finite) number of remote downloads or access per billing cycle, such as for a flat fee. As yet another alternative, the selected/downloaded content or data can be billed on a “pay as you go” basis, such as via debit card, electronic payment service (e.g., “Paypal™”) or the like, with successful negotiation of the payment contract being a condition precedent to delivery of the content/data.
Content as discussed previously also need not be full length features (e.g., movies); rather, music videos, promotional materials, tutorials, trailers, and other desirable content can be provided in a broadcast or session fashion without the extra effort associated with entering into a contract with a separate service provider. Similarly, it is anticipated that content developers (such as the MSO themselves, or a third-party entity such as a studio or channel) will develop content specifically adapted to the remote delivery paradigm set forth herein; e.g., suitable to perhaps more limited bandwidth availability of the remote network 204. In this fashion, the MSO or other content source may also maintain two or more versions of the content recorded or purchased by the subscriber; e.g., a “local” or home copy, and a “remote” or lower bandwidth or differently encoded/compressed copy, with the applicable version being delivered to the user depending on their location. The local copy might also comprise HD, while the remote copy comprises an SD rendition of the same content.
This process can also work in reverse; i.e., to provide content or data from the subscriber upstream. As previously discussed, the captured video can be uploaded to the MSO or third party server, for later download and viewing at the subscriber's premises (or those of other subscribers authorized to view the content). Such download may also be to a second appropriately equipped RCD 214.
Referring now to
In step 702, an MSO subscriber wishing to access content initiates a session directly or indirectly with the network entity providing the content (e.g., content server 242).
Per step 704, the subscriber is authenticated for purposes of verifying that the subscriber attempting to access content through an MSO account is indeed the person named in the MSO account. This can be accomplished through a variety of means including via security architecture at the cable (MSO) side of the system architecture, and/or authentication via the CSP/WSP, or any other portion on the IP network side of the system.
Per step 706, the content server 242 can access the billing module 152 or other billing entity within the network, whether directly or indirectly, and write a record or data into the appropriate database so that the subscriber can be charged for the content on his/her home cable bill. Other relevant information such as date/time, content requested, CSP/WSP network identification, and so forth may be included in the billing information if desired in order to be included on the subscriber invoice.
Lastly, the billing module 152 or other entity responsible for generating billing data assembles the invoice or statement for the subscriber using the cable system component (e.g., monthly service/use charges) as well as those associated with content access and download via the CSP/WSP if any. These latter charges can be set off in a separate section of the statement if desired, or merely integrated into existing categories of services or charges.
Furthermore, where a business relationship exists between the CSP/WSP and the MSO, the subscribers wireless or mobile access charges during the billing period (whether related to content access or not) may also be incorporated into the subscriber's MSO-generated bill. In this fashion, the subscriber can be provided only one “umbrella” invoice covering both their cable/satellite and wireless charges. Various of the foregoing data may also be optionally bundled with VoIP or similar access charges, such as for example where the MSO offers VoIP telephony service to their subscribers via their indigenous cable/satellite and IP infrastructure. This allows for an even higher level of service integration, with the subscriber receiving only one bill for their “home” (e.g., VoIP-based) and wireless telephony, as well as their cable or satellite and Internet access. In one exemplary configuration, the MSO can offer 1) cable access (including premium services such as DVR/PVR and on-demand), 2) high speed Internet access (such as the “Roadrunner®” offered by the Assignee hereof), 3) VoIP-based telephone service, and 4) remote content delivery service.
It will also be appreciated that there are significant economies of scale to this approach for the service provider(s), such as by obviating the need for the printing and mailing or electronic processing of multiple separate monthly invoices, and reduced customer service overhead. Such integrated service packages also offer increased opportunities for promotions, incentives, and “cross-over” sales of products and services, thereby increasing the profitability of this paradigm.
Delivery of the content to remote client or mobile devices (or the user's PC or laptop) can also be effected according to the methods and apparatus described in co-owned U.S. patent application Ser. No. 11/198,620 entitled “Method And Apparatus For Context-Specific Content Delivery” filed Aug. 4, 2005 and issued as U.S. Pat. No. 9,286,388 on Mar. 15, 2016, incorporated herein by reference in its entirety, which describes, inter alia, the display and seamless transition of primary and secondary content within, e.g., a unified display mechanism (window). This integration allows for yet additional business or economic opportunities, since the content downloaded by the user can be coupled (seamlessly) to an advertising server or the like, the latter presenting the user with context-specific links or other information (secondary content) relating to the primary content (e.g., video) downloaded. The user then merely selects one or more of these links, and is provided additional information relating to the topic of interest (either the primary content or the links which individually may or may not be commercial in nature). These links can be accessed, e.g., a traditional IP or similar mechanism of the type previously described herein, such as the well known WAP protocol and browser.
In addition to the foregoing, the “watch-along” function can also be marketed as an incentive or additional premium feature. Specifically, parents or others may desire to have the capability to both monitor what their children are watching while they are away, as well as affirmatively control access to certain channels or content from a remote location. This paradigm can also be readily extended into the enterprise or business arenas, such as to monitor/control employee channel usage.
Operations/Business Rules Engine
In another aspect of the invention, the aforementioned content manager 238 (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 content server device 242 or other associated hardware/firmware environment adapted to control the operation of the content management algorithms previously described. These rules may also be fully integrated within the content manager 238 itself, and controlled via e.g., a GUI on a PC connected to the server 242. In effect, the rules engine comprises a supervisory entity which monitors and selectively controls, via the content manager 238, the remote content delivery 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 remote content management and delivery algorithms. For example, the content manager 238 may invoke certain operational protocols or decision processes based on requests received from the RCD, subscriber 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 manually) control the operation of the CM 238. The rules may be, e.g., operational or business-oriented in nature, or related to preservation of security, and may also be applied selectively in terms of time of day, duration, specific local areas, or even at the individual user level.
For example, one rule implemented by the rules engine may comprise only providing targeted secondary content insertion (e.g., advertising) to certain classes of subscribers (e.g., those at a premium level of service, or subscribers who have “opted-in” to receiving targeted advertising, 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 delivering certain content (even if already viewed or recorded by the subscriber at the LCD 208) over the remote network to the RCD due to an actual or perceived threat of theft or unauthorized copying. For example, the MSO may only allow remote delivery of certain classes of content that are not considered “high value”, or are sufficiently dated since their release over the local network.
It will also be appreciated that certain subscribers may be given preference for remote delivery of content over others, such as in cases where the remote network bandwidth is limited.
It will be appreciated that less “binary” approaches than that described above can be utilized consistent with the invention, whether in the context of secondary content insertion, servicing remote delivery requests, or otherwise. Specifically, the foregoing approaches to remote delivery of content based on prior recording or tuner state has effectively two states; i.e., delivered or not delivered. This model has the advantage of simplicity, in that little real intelligence is required for implementation. For example, a supervisory process (e.g., algorithm) may comprise a fuzzy logic, Bayesian, or similar approach to classify individual RCDs into one of two categories in terms of a particular context (e.g., “high-value” or “low-value”, “local” or “distant”, “low bandwidth” or “high bandwidth”, etc.), which can then be used as the sole (or at least partial) basis for delivering content for the designated RCD.
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. 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. 11/441,476 filed on May 24, 2006, issuing as U.S. Pat. No. 9,386,327 on Jul. 5, 2016, and entitled “SECONDARY CONTENT INSERTION APPARATUS AND METHODS”, which is incorporated herein by reference in its entirety. This application is also related to commonly owned U.S. patent application Ser. No. 11/440,490 filed contemporaneously herewith entitled “Personal Content Server Apparatus And Methods” and issued as U.S. Pat. No. 8,280,982 on Oct. 2, 2012, U.S. patent application Ser. No. 11/080,693 filed Mar. 14, 2005 entitled “Method And Apparatus For Network Content Download and Recording” and issued as U.S. Pat. No. 8,028,322 on Sep. 27, 2011, U.S. patent application Ser. No. 10/182,307 filed Jul. 26, 2002 entitled “System And Method For Providing Broadcast Programming, A Virtual VCR, And A Video Scrapbook To Programming Subscribers” and issued as U.S. Pat. No. 8,584,182 on Nov. 12, 2013, and U.S. patent application Ser. No. 10/626,051 filed Jul. 24, 2003 entitled “Technique for Providing a Virtual Digital Video Recorder Service Through a Communications Network” and issued as U.S. Pat. No. 7,457,520 on Nov. 25, 2008, each of the foregoing incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 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 |
| 5042620 | Yoneda et al. | Aug 1991 | A |
| 5047867 | Strubbe et al. | Sep 1991 | A |
| 5056629 | Tsuji et al. | Oct 1991 | A |
| 5086450 | Kitagawa et al. | Feb 1992 | A |
| 5155591 | Wachob | Oct 1992 | A |
| 5159163 | Bahjat et al. | Oct 1992 | A |
| 5172413 | Bradley et al. | Dec 1992 | A |
| 5200583 | Kupersmith et al. | Apr 1993 | A |
| 5200822 | Bronfin et al. | Apr 1993 | A |
| 5253066 | Vogel et al. | Oct 1993 | A |
| 5255341 | Nakajima | Oct 1993 | A |
| 5285272 | Bradley et al. | Feb 1994 | A |
| 5287266 | Malec et al. | Feb 1994 | A |
| 5290710 | Haj-Ali-Ahmadi et al. | Mar 1994 | A |
| 5295064 | Malec et al. | Mar 1994 | A |
| 5335277 | Harvey et al. | Aug 1994 | A |
| 5357276 | Banker et al. | Oct 1994 | A |
| 5371532 | Gelman et al. | Dec 1994 | A |
| 5371551 | Logan et al. | Dec 1994 | A |
| 5373315 | Dufresne et al. | Dec 1994 | A |
| 5394182 | Klappert et al. | Feb 1995 | A |
| 5412720 | Hoarty | May 1995 | A |
| 5414455 | Hooper et al. | May 1995 | A |
| 5442389 | Blahut et al. | Aug 1995 | A |
| 5461415 | Wolf et al. | Oct 1995 | A |
| 5463209 | Figh et al. | Oct 1995 | A |
| 5479266 | Young et al. | Dec 1995 | A |
| 5479268 | Young et al. | Dec 1995 | A |
| 5481294 | Thomas et al. | Jan 1996 | A |
| 5485897 | Matsumoto et al. | Jan 1996 | A |
| 5497185 | Dufresne et al. | Mar 1996 | A |
| 5512934 | Kochanski | Apr 1996 | A |
| 5515510 | Kikinis | May 1996 | A |
| 5517257 | Dunn et al. | May 1996 | A |
| 5524195 | Clanton, III et al. | Jun 1996 | A |
| 5528282 | Voeten et al. | Jun 1996 | A |
| 5528284 | Iwami et al. | Jun 1996 | A |
| 5534911 | Levitan | Jul 1996 | A |
| 5535206 | Bestler et al. | Jul 1996 | A |
| 5541738 | Mankovitz | Jul 1996 | A |
| 5551532 | Kupersmith | Sep 1996 | A |
| 5583561 | Baker et al. | Dec 1996 | A |
| 5583563 | Wanderscheid et al. | Dec 1996 | A |
| 5585838 | Lawler et al. | Dec 1996 | A |
| 5589892 | Knee et al. | Dec 1996 | A |
| 5592551 | Lett et al. | Jan 1997 | A |
| 5600364 | Hendricks et al. | Feb 1997 | A |
| 5606154 | Doigan et al. | Feb 1997 | A |
| 5619247 | Russo | Apr 1997 | A |
| 5619249 | Billock et al. | Apr 1997 | A |
| 5625405 | Dulac et al. | Apr 1997 | A |
| 5652615 | Bryant et al. | Jul 1997 | A |
| 5657072 | Aristides et al. | Aug 1997 | A |
| 5659350 | Hendricks et al. | Aug 1997 | A |
| 5671225 | Hooper et al. | Sep 1997 | A |
| 5675647 | Garneau et al. | Oct 1997 | A |
| 5682597 | Ganek et al. | Oct 1997 | A |
| 5684714 | Yogeshwar et al. | Nov 1997 | A |
| 5684963 | Clement | Nov 1997 | A |
| 5689094 | Friedli et al. | Nov 1997 | A |
| 5701383 | Russo et al. | Dec 1997 | A |
| 5708961 | Hylton et al. | Jan 1998 | A |
| 5710970 | Walters et al. | Jan 1998 | A |
| 5721878 | Ottesen et al. | Feb 1998 | A |
| 5724646 | Ganek et al. | Mar 1998 | A |
| 5729280 | Inoue et al. | Mar 1998 | A |
| 5729648 | Boyce et al. | Mar 1998 | A |
| 5748254 | Harrison et al. | May 1998 | A |
| 5749443 | Romao | May 1998 | A |
| 5751282 | Girard et al. | May 1998 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5761607 | Gudesen | Jun 1998 | A |
| 5771354 | Crawford | Jun 1998 | A |
| 5771435 | Brown | Jun 1998 | A |
| 5774170 | Hite et al. | Jun 1998 | A |
| 5778181 | Hidary et al. | Jul 1998 | A |
| 5778187 | Monteiro et al. | Jul 1998 | A |
| 5781228 | Sposato | Jul 1998 | A |
| 5793409 | Tetsumura | Aug 1998 | A |
| 5793971 | Fujita et al. | Aug 1998 | A |
| 5794217 | Allen | Aug 1998 | A |
| 5805154 | Brown | Sep 1998 | A |
| 5805155 | Allibhoy et al. | Sep 1998 | A |
| 5805763 | Lawler et al. | Sep 1998 | A |
| 5805804 | Laursen et al. | Sep 1998 | A |
| 5808608 | Young et al. | Sep 1998 | A |
| 5809204 | Young et al. | Sep 1998 | A |
| 5812642 | Leroy | Sep 1998 | A |
| 5815146 | Youden | Sep 1998 | A |
| 5815148 | Tanaka | Sep 1998 | A |
| 5818438 | Howe et al. | Oct 1998 | A |
| 5818440 | Allibhoy et al. | Oct 1998 | A |
| 5818510 | Cobbley et al. | Oct 1998 | A |
| 5819034 | Joseph et al. | Oct 1998 | A |
| 5822530 | Brown | Oct 1998 | A |
| 5826168 | Inoue et al. | Oct 1998 | A |
| 5832231 | Raman et al. | Nov 1998 | A |
| 5835125 | Bhagavath | Nov 1998 | A |
| 5841468 | Wright | Nov 1998 | A |
| 5844181 | Amo et al. | Dec 1998 | A |
| 5844897 | Asamizuya | Dec 1998 | A |
| 5847703 | Teicher et al. | Dec 1998 | A |
| 5850218 | Lajoie et al. | Dec 1998 | A |
| 5861881 | Freeman et al. | Jan 1999 | A |
| 5864176 | Babock et al. | Jan 1999 | A |
| 5887139 | Madison, Jr. et al. | Mar 1999 | A |
| 5887243 | Harvey et al. | Mar 1999 | A |
| 5892535 | Allen et al. | Apr 1999 | A |
| 5892915 | Duso et al. | Apr 1999 | A |
| 5896454 | Cookson et al. | Apr 1999 | A |
| 5897635 | Torres et al. | Apr 1999 | A |
| 5909638 | Allen | Jun 1999 | A |
| 5914945 | Abu-Amara et al. | Jun 1999 | A |
| 5917538 | Asamizuya | Jun 1999 | A |
| 5918222 | Fukui et al. | Jun 1999 | A |
| 5918665 | Babcock et al. | Jul 1999 | A |
| 5930473 | Teng et al. | Jul 1999 | A |
| 5930893 | Eaton | Aug 1999 | A |
| 5932853 | Friedli et al. | Aug 1999 | A |
| 5940370 | Curtis et al. | Aug 1999 | A |
| 5955710 | DiFranza | Sep 1999 | A |
| 5956716 | Kenner et al. | Sep 1999 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 5970206 | Yuen et al. | Oct 1999 | A |
| 5974299 | Massetti | Oct 1999 | A |
| 5979757 | Tracy et al. | Nov 1999 | A |
| 5984051 | Morgan et al. | Nov 1999 | A |
| 5987506 | Carter | Nov 1999 | A |
| 5991308 | Fuhrmann et al. | Nov 1999 | A |
| 5995708 | Corey | Nov 1999 | A |
| 6002393 | Hite et al. | Dec 1999 | A |
| 6005603 | Flavin | Dec 1999 | A |
| 6005643 | Morimoto et al. | Dec 1999 | A |
| 6006265 | Rangan | Dec 1999 | A |
| 6009098 | Asamizuya | Dec 1999 | A |
| 6011839 | Friedli et al. | Jan 2000 | A |
| 6016509 | Dedrick | Jan 2000 | A |
| 6018509 | Itoh et al. | Jan 2000 | A |
| 6029045 | Picco et al. | Feb 2000 | A |
| 6047327 | Tso et al. | Apr 2000 | A |
| 6052145 | Macrae et al. | Apr 2000 | A |
| 6057832 | Lev et al. | May 2000 | A |
| 6058380 | Anderson et al. | May 2000 | A |
| 6069023 | Bernier et al. | May 2000 | A |
| 6073160 | Grantham et al. | Jun 2000 | A |
| 6073727 | DiFranza et al. | Jun 2000 | A |
| 6078928 | Schnase et al. | Jun 2000 | A |
| 6081830 | Schindler | Jun 2000 | A |
| 6082500 | Amo et al. | Jul 2000 | A |
| 6088722 | Herz et al. | Jul 2000 | A |
| 6091883 | Artigalas et al. | Jul 2000 | A |
| 6092197 | Coueignoux | Jul 2000 | A |
| 6097431 | Anderson et al. | Aug 2000 | A |
| 6112192 | Capek | Aug 2000 | A |
| 6122647 | Horowitz | Sep 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6137793 | Gorman et al. | Oct 2000 | A |
| 6144401 | Casement et al. | Nov 2000 | A |
| 6160989 | Hendricks et al. | Dec 2000 | A |
| 6161142 | Wolfe et al. | Dec 2000 | A |
| 6167188 | Young et al. | Dec 2000 | A |
| 6167432 | Jiang | Dec 2000 | A |
| 6169570 | Suzuki | Jan 2001 | B1 |
| 6177931 | Alexander et al. | Jan 2001 | B1 |
| 6181697 | Nurenberg et al. | Jan 2001 | B1 |
| 6182050 | Ballard | Jan 2001 | B1 |
| 6202008 | Beckert et al. | Mar 2001 | B1 |
| 6202210 | Ludtke | Mar 2001 | B1 |
| 6202799 | Drop | Mar 2001 | B1 |
| 6206142 | Meacham | Mar 2001 | B1 |
| 6208335 | Gordon et al. | Mar 2001 | B1 |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6219710 | Gray et al. | Apr 2001 | B1 |
| 6223160 | Kostka et al. | Apr 2001 | B1 |
| 6233389 | Barton et al. | May 2001 | B1 |
| 6236968 | Kanevsky et al. | May 2001 | B1 |
| 6240401 | Oren et al. | May 2001 | B1 |
| 6259701 | Shur et al. | Jul 2001 | B1 |
| 6286041 | Collins, III | Sep 2001 | B1 |
| 6292624 | Saib et al. | Sep 2001 | B1 |
| 6321257 | Kotola et al. | Nov 2001 | B1 |
| 6324338 | Wood et al. | Nov 2001 | B1 |
| 6327418 | Barton | Dec 2001 | B1 |
| 6341668 | Fayette et al. | Jan 2002 | B1 |
| 6343313 | Salesky et al. | Jan 2002 | B1 |
| 6343647 | Kim et al. | Feb 2002 | B2 |
| 6349797 | Newville et al. | Feb 2002 | B1 |
| 6369840 | Barnett et al. | Apr 2002 | B1 |
| 6378035 | Parry et al. | Apr 2002 | B1 |
| 6378129 | Zetts | Apr 2002 | B1 |
| 6397976 | Hale et al. | Jun 2002 | B1 |
| 6421305 | Gioscia et al. | Jul 2002 | B1 |
| 6434562 | Pennywitt et al. | Aug 2002 | B1 |
| 6446261 | Rosser | Sep 2002 | B1 |
| 6460036 | Herz | Oct 2002 | B1 |
| 6463585 | Hendricks et al. | Oct 2002 | B1 |
| 6466232 | Newell et al. | Oct 2002 | B1 |
| 6467089 | Aust et al. | Oct 2002 | B1 |
| 6470378 | Tracton et al. | Oct 2002 | B1 |
| 6504571 | Narayanaswami et al. | Jan 2003 | B1 |
| 6519062 | Yoo | Feb 2003 | B1 |
| 6523696 | Saito et al. | Feb 2003 | B1 |
| 6549718 | Grooters et al. | Apr 2003 | B1 |
| 6553178 | Abecassis | Apr 2003 | B2 |
| 6560203 | Beser et al. | May 2003 | B1 |
| 6560578 | Eldering | May 2003 | B2 |
| 6571279 | Herz et al. | May 2003 | B1 |
| 6574617 | Immerman et al. | Jun 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6588015 | Eyer et al. | Jul 2003 | B1 |
| 6591420 | McPherson et al. | Jul 2003 | B1 |
| 6598228 | Hejna et al. | Jul 2003 | B2 |
| 6604138 | Virine et al. | Aug 2003 | B1 |
| 6611654 | Shteyn | Aug 2003 | B1 |
| 6613776 | Knegtel et al. | Sep 2003 | B2 |
| 6615039 | Eldering | Sep 2003 | B1 |
| 6615175 | Gazdzinski | Sep 2003 | B1 |
| 6615251 | Klug et al. | Sep 2003 | B1 |
| 6622305 | Willard | Sep 2003 | B1 |
| 6640145 | Hoffberg et al. | Oct 2003 | B2 |
| 6647548 | Lu et al. | Nov 2003 | B1 |
| 6651045 | Macaulay | Nov 2003 | B1 |
| 6671736 | Virine et al. | Dec 2003 | B2 |
| 6671879 | Schlarb et al. | Dec 2003 | B1 |
| 6681393 | Bauminger et al. | Jan 2004 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6694145 | Riikonen et al. | Feb 2004 | B2 |
| 6704930 | Eldering et al. | Mar 2004 | B1 |
| 6718551 | Swix et al. | Apr 2004 | B1 |
| 6738978 | Hendricks et al. | May 2004 | B1 |
| 6741980 | Langseth et al. | May 2004 | B1 |
| 6757796 | Hofmann | Jun 2004 | B1 |
| 6760918 | Rodriguez et al. | Jul 2004 | B2 |
| 6769127 | Bonomi et al. | Jul 2004 | B1 |
| 6771290 | Hoyle | Aug 2004 | B1 |
| 6772434 | Godwin | Aug 2004 | B1 |
| 6775778 | Laczko, Sr. et al. | Aug 2004 | B1 |
| 6782550 | Cao | Aug 2004 | B1 |
| 6785704 | McCanne | Aug 2004 | B1 |
| 6788676 | Partanen et al. | Sep 2004 | B2 |
| 6792577 | Kimoto | Sep 2004 | B1 |
| 6801792 | Schuster et al. | Oct 2004 | B1 |
| 6802077 | Schlarb | Oct 2004 | B1 |
| 6810528 | Chatani | Oct 2004 | B1 |
| 6817028 | Jerding et al. | Nov 2004 | B1 |
| 6826267 | Daum et al. | Nov 2004 | B2 |
| 6832259 | Hymel et al. | Dec 2004 | B2 |
| 6851063 | Boyle et al. | Feb 2005 | B1 |
| 6853731 | Boyle et al. | Feb 2005 | B1 |
| 6857132 | Rakib et al. | Feb 2005 | B1 |
| 6859845 | Mate | Feb 2005 | B2 |
| 6898762 | Ellis et al. | May 2005 | B2 |
| 6909726 | Sheeran | Jun 2005 | B1 |
| 6909837 | Unger | Jun 2005 | B1 |
| 6914446 | Tustaniwskyj et al. | Jul 2005 | B1 |
| 6915528 | McKenna, Jr. | Jul 2005 | B1 |
| 6920565 | Isaacson et al. | Jul 2005 | B2 |
| 6925257 | Yoo | Aug 2005 | B2 |
| 6934880 | Hofner | Aug 2005 | B2 |
| 6944150 | McConnell et al. | Sep 2005 | B1 |
| 6959288 | Medina et al. | Oct 2005 | B1 |
| 6975850 | Hurtta | Dec 2005 | B1 |
| 6978370 | Kocher | Dec 2005 | B1 |
| 6990312 | Gioscia et al. | Jan 2006 | B1 |
| 6990680 | Wugofski | Jan 2006 | B1 |
| 7004243 | Babcock et al. | Feb 2006 | B1 |
| 7006881 | Hoffberg et al. | Feb 2006 | B1 |
| 7009972 | Maher et al. | Mar 2006 | B2 |
| 7016376 | Goldenberg et al. | Mar 2006 | B1 |
| 7017179 | Asamoto et al. | Mar 2006 | B1 |
| 7020892 | Levesque et al. | Mar 2006 | B2 |
| 7024466 | Outten | Apr 2006 | B2 |
| 7024678 | Gordon et al. | Apr 2006 | B2 |
| 7025209 | Hawkins | Apr 2006 | B2 |
| 7027460 | Iyer et al. | Apr 2006 | B2 |
| 7028009 | Wang et al. | Apr 2006 | B2 |
| 7028071 | Slik | Apr 2006 | B1 |
| 7028329 | Mizutani | Apr 2006 | B1 |
| 7039048 | Monta et al. | May 2006 | B1 |
| 7039928 | Kamada et al. | May 2006 | B2 |
| 7054843 | Charas | May 2006 | B2 |
| 7054902 | Toporek et al. | May 2006 | B2 |
| 7058685 | Van Zee et al. | Jun 2006 | B1 |
| 7058810 | Kumazawa et al. | Jun 2006 | B2 |
| 7068639 | Varma et al. | Jun 2006 | B1 |
| 7069577 | Geile et al. | Jun 2006 | B2 |
| 7073189 | McElhatten et al. | Jul 2006 | B2 |
| 7073193 | Marsh | Jul 2006 | B2 |
| 7075945 | Arsenault et al. | Jul 2006 | B2 |
| 7080397 | Cochran et al. | Jul 2006 | B2 |
| 7080400 | Navar | Jul 2006 | B1 |
| 7099308 | Merrill et al. | Aug 2006 | B2 |
| 7100183 | Kunkel et al. | Aug 2006 | B2 |
| 7103906 | Katz et al. | Sep 2006 | B1 |
| 7106382 | Shiotsu | Sep 2006 | B2 |
| 7109848 | Schybergson | Sep 2006 | B2 |
| 7124195 | Roach et al. | Oct 2006 | B2 |
| 7136573 | Kikuchi et al. | Nov 2006 | B2 |
| 7136853 | Kohda et al. | Nov 2006 | B1 |
| 7137728 | Witham et al. | Nov 2006 | B2 |
| 7143431 | Eager et al. | Nov 2006 | B1 |
| 7146627 | Ismail et al. | Dec 2006 | B1 |
| 7146630 | Dravida et al. | Dec 2006 | B2 |
| 7149772 | Kalavade | Dec 2006 | B1 |
| 7152237 | Flickinger et al. | Dec 2006 | B2 |
| 7155226 | Oh et al. | Dec 2006 | B1 |
| 7155508 | Sankuratripati et al. | Dec 2006 | B2 |
| 7159235 | Son | Jan 2007 | B2 |
| 7171485 | Roach et al. | Jan 2007 | B2 |
| 7174126 | McElhatten et al. | Feb 2007 | B2 |
| 7174127 | Otten et al. | Feb 2007 | B2 |
| 7174385 | Li | Feb 2007 | B2 |
| 7184526 | Cook | Feb 2007 | B1 |
| 7191244 | Jennings et al. | Mar 2007 | B2 |
| 7194001 | Leatherbury et al. | Mar 2007 | B2 |
| 7194009 | Eng | Mar 2007 | B2 |
| 7197472 | Conkwright et al. | Mar 2007 | B2 |
| 7203185 | Dhara et al. | Apr 2007 | B1 |
| 7203311 | Kahn et al. | Apr 2007 | B1 |
| 7209458 | Ahvonen et al. | Apr 2007 | B2 |
| 7209892 | Galuten et al. | Apr 2007 | B1 |
| 7212543 | Arwald et al. | May 2007 | B1 |
| 7213742 | Birch et al. | May 2007 | B1 |
| 7216170 | Ludvig et al. | May 2007 | B2 |
| 7222078 | Abelow | May 2007 | B2 |
| 7222163 | Girouard | May 2007 | B1 |
| 7228359 | Monteiro | Jun 2007 | B1 |
| 7228555 | Schlack | Jun 2007 | B2 |
| 7231669 | Leung et al. | Jun 2007 | B2 |
| 7233948 | Shamoon et al. | Jun 2007 | B1 |
| 7237017 | Pecus | Jun 2007 | B1 |
| 7237250 | Kanojia et al. | Jun 2007 | B2 |
| 7240196 | Cooper et al. | Jul 2007 | B2 |
| 7242960 | Van Rooyen | Jul 2007 | B2 |
| 7246150 | Donoho et al. | Jul 2007 | B1 |
| 7246172 | Yoshiba et al. | Jul 2007 | B2 |
| 7254608 | Yeager et al. | Aug 2007 | B2 |
| 7257308 | Plourde et al. | Aug 2007 | B2 |
| 7260564 | Lynn | Aug 2007 | B1 |
| 7263187 | Pedlow, Jr. et al. | Aug 2007 | B2 |
| 7263188 | Kohno | Aug 2007 | B2 |
| 7266198 | Medvinsky | Sep 2007 | B2 |
| 7266832 | Miller | Sep 2007 | B2 |
| 7266836 | Anttila et al. | Sep 2007 | B2 |
| 7269854 | Simmons et al. | Sep 2007 | B2 |
| 7280737 | Smith | Oct 2007 | B2 |
| 7281261 | Jaff et al. | Oct 2007 | B2 |
| 7301944 | Redmond | Nov 2007 | B1 |
| 7305357 | Hamilton | Dec 2007 | B2 |
| 7305691 | Cristofalo | Dec 2007 | B2 |
| 7315886 | Meenan et al. | Jan 2008 | B1 |
| 7317728 | Acharya et al. | Jan 2008 | B2 |
| 7320134 | Tomsen et al. | Jan 2008 | B1 |
| 7321923 | Rosenberg et al. | Jan 2008 | B1 |
| 7325073 | Shao et al. | Jan 2008 | B2 |
| 7327692 | Ain et al. | Feb 2008 | B2 |
| 7330483 | Peters, Jr. et al. | Feb 2008 | B1 |
| 7330875 | Parasnis | Feb 2008 | B1 |
| 7337147 | Chen et al. | Feb 2008 | B2 |
| 7337459 | Tsutsui et al. | Feb 2008 | B1 |
| 7340510 | Liskov | Mar 2008 | B1 |
| 7340760 | Wachtfogel et al. | Mar 2008 | B2 |
| 7346558 | Rosenberg | Mar 2008 | B2 |
| 7346630 | Eichstaedt | Mar 2008 | B2 |
| 7352775 | Powell | Apr 2008 | B2 |
| 7355980 | Bauer et al. | Apr 2008 | B2 |
| 7356751 | Levitan | Apr 2008 | B1 |
| 7360233 | Russ et al. | Apr 2008 | B2 |
| 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 |
| 7376386 | Phillips et al. | May 2008 | B2 |
| 7383228 | Lisanke et al. | Jun 2008 | B2 |
| 7386621 | Hlasny | Jun 2008 | B1 |
| 7406099 | Schlagintweit | Jul 2008 | B2 |
| 7438233 | Leiper | Oct 2008 | B2 |
| 7441037 | Saxena | Oct 2008 | B2 |
| 7457520 | Rosetti et al. | Nov 2008 | B2 |
| 7486869 | Alexander et al. | Feb 2009 | B2 |
| 7496647 | Karaoguz et al. | Feb 2009 | B2 |
| 7533376 | Anwar et al. | May 2009 | B2 |
| 7558837 | Denny | Jul 2009 | B1 |
| 7567262 | Clemens et al. | Jul 2009 | B1 |
| 7567988 | Wolf et al. | Jul 2009 | B2 |
| 7577118 | Haumonte et al. | Aug 2009 | B2 |
| 7592912 | Hasek et al. | Sep 2009 | B2 |
| 7602820 | Helms et al. | Oct 2009 | B2 |
| 7603321 | Gurvey | Oct 2009 | B2 |
| 7603529 | MacHardy et al. | Oct 2009 | B1 |
| 7627492 | Nishizawa et al. | Dec 2009 | B2 |
| 7636792 | Ho | Dec 2009 | B1 |
| 7640581 | Brenton et al. | Dec 2009 | B1 |
| 7647618 | Hunter et al. | Jan 2010 | B1 |
| 7653689 | Champagne | Jan 2010 | B1 |
| 7690020 | Lebar | Mar 2010 | B2 |
| 7693171 | Gould | Apr 2010 | B2 |
| 7711605 | Santeufemia | May 2010 | B1 |
| 7712125 | Herigstad et al. | May 2010 | B2 |
| 7720432 | Colby et al. | May 2010 | B1 |
| 7721314 | Sincaglia et al. | May 2010 | B2 |
| 7730509 | Boulet et al. | Jun 2010 | B2 |
| 7742074 | Minatogawa | Jun 2010 | B2 |
| 7769629 | Kriza et al. | Aug 2010 | B1 |
| 7787416 | Gidwani | Aug 2010 | B2 |
| 7788687 | Conrad et al. | Aug 2010 | B1 |
| 7793334 | Lewis | Sep 2010 | B2 |
| 7805515 | Riley | Sep 2010 | B2 |
| 7809942 | Baran et al. | Oct 2010 | B2 |
| 7843876 | Holt et al. | Nov 2010 | B2 |
| 7849491 | Perlman | Dec 2010 | B2 |
| 7878908 | Sloate et al. | Feb 2011 | B2 |
| 7900229 | Dureau | Mar 2011 | B2 |
| 7908626 | Williamson et al. | Mar 2011 | B2 |
| 7984473 | Casile et al. | Jul 2011 | B1 |
| 7986686 | Nadeau | Jul 2011 | B2 |
| 8006262 | Rodriguez et al. | Aug 2011 | B2 |
| 8006273 | Rodriguez | Aug 2011 | B2 |
| 8015583 | Bates et al. | Sep 2011 | B2 |
| 8024762 | Britt | Sep 2011 | B2 |
| 8028322 | Riedl et al. | Sep 2011 | B2 |
| 8042131 | Flickinger | Oct 2011 | B2 |
| 8055585 | Wu | Nov 2011 | B2 |
| 8065703 | Wilson et al. | Nov 2011 | B2 |
| 8127331 | Heilbron et al. | Feb 2012 | B2 |
| 8151295 | Eldering et al. | Apr 2012 | B1 |
| 8181206 | Hasek | May 2012 | B2 |
| 8205226 | Ko et al. | Jun 2012 | B2 |
| 8214256 | Riedl et al. | Jul 2012 | B2 |
| 8249918 | Biere et al. | Aug 2012 | B1 |
| 8272020 | Watson | Sep 2012 | B2 |
| 8280982 | La Joie et al. | Oct 2012 | B2 |
| 8347341 | Markley et al. | Jan 2013 | B2 |
| 8396055 | Patel et al. | Mar 2013 | B2 |
| 8424048 | Lyren et al. | Apr 2013 | B1 |
| 8438243 | Lajoie et al. | May 2013 | B2 |
| 8527602 | Rasmussen et al. | Sep 2013 | B1 |
| 8561113 | Cansler et al. | Oct 2013 | B2 |
| 8583758 | Casey et al. | Nov 2013 | B2 |
| 8584182 | Berberet et al. | Nov 2013 | B2 |
| 8713623 | Brooks | Apr 2014 | B2 |
| 8848969 | Ramsdell | Sep 2014 | B2 |
| 9215423 | Kimble et al. | Dec 2015 | B2 |
| 9317241 | Tranchina | Apr 2016 | B2 |
| 9325710 | Lajoie et al. | Apr 2016 | B2 |
| 9832246 | Lajoie et al. | Nov 2017 | B2 |
| 10506296 | Bonvolanta et al. | Dec 2019 | B2 |
| 20010001160 | Shoff et al. | May 2001 | A1 |
| 20010003194 | Shimura et al. | Jun 2001 | A1 |
| 20010004768 | Hodge et al. | Jun 2001 | A1 |
| 20010013123 | Freeman et al. | Aug 2001 | A1 |
| 20010013173 | Mertens et al. | Aug 2001 | A1 |
| 20010030975 | Limb et al. | Oct 2001 | A1 |
| 20010037223 | Beery et al. | Nov 2001 | A1 |
| 20010054181 | Corvin | Dec 2001 | A1 |
| 20010056573 | Kovac et al. | Dec 2001 | A1 |
| 20020003789 | Kim et al. | Jan 2002 | A1 |
| 20020004870 | Kobayashi | Jan 2002 | A1 |
| 20020013940 | Tsukamoto et al. | Jan 2002 | A1 |
| 20020019984 | Rakib | Feb 2002 | A1 |
| 20020026496 | Boyer et al. | Feb 2002 | A1 |
| 20020027883 | Belaiche | Mar 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020038296 | Margolus | Mar 2002 | A1 |
| 20020042921 | Ellis | Apr 2002 | A1 |
| 20020046286 | Caldwell et al. | Apr 2002 | A1 |
| 20020046406 | Chelehmal et al. | Apr 2002 | A1 |
| 20020046407 | Franco | Apr 2002 | A1 |
| 20020049800 | Kobayashi et al. | Apr 2002 | A1 |
| 20020049902 | Rhodes | Apr 2002 | A1 |
| 20020054754 | Kikuchi et al. | May 2002 | A1 |
| 20020056107 | Schlack | May 2002 | A1 |
| 20020056118 | Hunter et al. | May 2002 | A1 |
| 20020056125 | Hodge et al. | May 2002 | A1 |
| 20020056175 | Magarino | May 2002 | A1 |
| 20020059619 | Lebar | May 2002 | A1 |
| 20020059621 | Thomas et al. | May 2002 | A1 |
| 20020059635 | Hoang | May 2002 | A1 |
| 20020066033 | Dobbins et al. | May 2002 | A1 |
| 20020069404 | Copeman et al. | Jun 2002 | A1 |
| 20020073327 | Vellandi | Jun 2002 | A1 |
| 20020073419 | Yen et al. | Jun 2002 | A1 |
| 20020073421 | Levitan et al. | Jun 2002 | A1 |
| 20020078176 | Nomura et al. | Jun 2002 | A1 |
| 20020078441 | Drake et al. | Jun 2002 | A1 |
| 20020078444 | Krewin et al. | Jun 2002 | A1 |
| 20020082858 | Heddaya | Jun 2002 | A1 |
| 20020083456 | Bates et al. | Jun 2002 | A1 |
| 20020085516 | Bridgelall | Jul 2002 | A1 |
| 20020087661 | Matichuk et al. | Jul 2002 | A1 |
| 20020087975 | Schlack | Jul 2002 | A1 |
| 20020087976 | Kaplan et al. | Jul 2002 | A1 |
| 20020099642 | Schwankl et al. | Jul 2002 | A1 |
| 20020100055 | Zeidman | Jul 2002 | A1 |
| 20020100063 | Herigstad et al. | Jul 2002 | A1 |
| 20020104019 | Chatani et al. | Aug 2002 | A1 |
| 20020104083 | Hendricks et al. | Aug 2002 | A1 |
| 20020112186 | Ford 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 |
| 20020138854 | Desai et al. | Sep 2002 | A1 |
| 20020143565 | Headings et al. | Oct 2002 | A1 |
| 20020144262 | Plotnick et al. | Oct 2002 | A1 |
| 20020144263 | Eldering et al. | Oct 2002 | A1 |
| 20020147771 | Traversat et al. | Oct 2002 | A1 |
| 20020147984 | Tomsen et al. | Oct 2002 | A1 |
| 20020151271 | Tatsuji et al. | Oct 2002 | A1 |
| 20020152299 | Traversat et al. | Oct 2002 | A1 |
| 20020152318 | Menon et al. | Oct 2002 | A1 |
| 20020152458 | Eyer et al. | Oct 2002 | A1 |
| 20020161835 | Ball | Oct 2002 | A1 |
| 20020166119 | Cristofalo | Nov 2002 | A1 |
| 20020166121 | Rovira | Nov 2002 | A1 |
| 20020169961 | Giles et al. | Nov 2002 | A1 |
| 20020174430 | Ellis et al. | Nov 2002 | A1 |
| 20020178445 | Eldering et al. | Nov 2002 | A1 |
| 20020178447 | Plotnick et al. | Nov 2002 | A1 |
| 20020184091 | Pudar | Dec 2002 | A1 |
| 20020184629 | Sie et al. | Dec 2002 | A1 |
| 20020184634 | Cooper | Dec 2002 | A1 |
| 20020184635 | Istvan | Dec 2002 | A1 |
| 20020188689 | Michael | Dec 2002 | A1 |
| 20020188744 | Mani | Dec 2002 | A1 |
| 20020188869 | Patrick | Dec 2002 | A1 |
| 20020191950 | Wang | Dec 2002 | A1 |
| 20020194498 | Blight et al. | Dec 2002 | A1 |
| 20020196940 | Isaacson et al. | Dec 2002 | A1 |
| 20030004810 | Eldering | Jan 2003 | A1 |
| 20030005446 | Jaff et al. | Jan 2003 | A1 |
| 20030005447 | Rodriguez | Jan 2003 | A1 |
| 20030005453 | Rodriguez et al. | Jan 2003 | A1 |
| 20030018977 | McKenna | Jan 2003 | A1 |
| 20030020744 | Ellis et al. | Jan 2003 | A1 |
| 20030022990 | Hirota et al. | Jan 2003 | A1 |
| 20030023690 | Lohtia | Jan 2003 | A1 |
| 20030028893 | Addington et al. | Feb 2003 | A1 |
| 20030030751 | Lupulescu et al. | Feb 2003 | A1 |
| 20030033199 | Coleman | Feb 2003 | A1 |
| 20030037330 | Makofka | Feb 2003 | A1 |
| 20030037335 | Gatto et al. | Feb 2003 | A1 |
| 20030037338 | Suzuki | Feb 2003 | A1 |
| 20030049021 | Kamieniecki | Mar 2003 | A1 |
| 20030053476 | Sorenson et al. | Mar 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030058887 | Dworkin et al. | Mar 2003 | A1 |
| 20030070052 | Lai | Apr 2003 | A1 |
| 20030074661 | Krapf et al. | Apr 2003 | A1 |
| 20030093311 | Knowlson | May 2003 | A1 |
| 20030093515 | Kauffman | May 2003 | A1 |
| 20030093784 | Dimitrova et al. | May 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030093792 | Labeeb et al. | May 2003 | A1 |
| 20030093806 | Dureau et al. | May 2003 | A1 |
| 20030097574 | Upton | 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 |
| 20030115267 | Hinton et al. | Jun 2003 | A1 |
| 20030115601 | Palazzo et al. | Jun 2003 | A1 |
| 20030118014 | Iyer et al. | Jun 2003 | A1 |
| 20030130008 | Rajaniemi et al. | Jul 2003 | A1 |
| 20030135513 | Quinn et al. | Jul 2003 | A1 |
| 20030135628 | Fletcher et al. | Jul 2003 | A1 |
| 20030143984 | Umeda | Jul 2003 | A1 |
| 20030145323 | Hendricks et al. | Jul 2003 | A1 |
| 20030149581 | Chaudhri | Aug 2003 | A1 |
| 20030149884 | Hernandez | Aug 2003 | A1 |
| 20030149975 | Eldering et al. | Aug 2003 | A1 |
| 20030149988 | Ellis et al. | Aug 2003 | A1 |
| 20030149990 | Anttila et al. | Aug 2003 | A1 |
| 20030149993 | Son et al. | Aug 2003 | A1 |
| 20030163832 | Tsuria et al. | Aug 2003 | A1 |
| 20030165241 | Fransdonk | Sep 2003 | A1 |
| 20030166401 | Combes et al. | Sep 2003 | A1 |
| 20030177490 | Hoshino et al. | Sep 2003 | A1 |
| 20030182551 | Frantz et al. | Sep 2003 | A1 |
| 20030188023 | Grecco | Oct 2003 | A1 |
| 20030208763 | McElhatten et al. | Nov 2003 | A1 |
| 20030208767 | Williamson et al. | Nov 2003 | A1 |
| 20030208768 | Urdang et al. | Nov 2003 | A1 |
| 20030217137 | Roese et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030223450 | Bender et al. | Dec 2003 | A1 |
| 20030225777 | Marsh | Dec 2003 | A1 |
| 20030226150 | Berberet et al. | Dec 2003 | A1 |
| 20030229898 | Babu et al. | Dec 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20030231661 | Depietro et al. | Dec 2003 | A1 |
| 20030236839 | Demsky et al. | Dec 2003 | A1 |
| 20030237090 | Boston et al. | Dec 2003 | A1 |
| 20040001087 | Warmus et al. | Jan 2004 | A1 |
| 20040006694 | Heelan | Jan 2004 | A1 |
| 20040015608 | Ellis et al. | Jan 2004 | A1 |
| 20040015989 | Kaizu et al. | Jan 2004 | A1 |
| 20040025181 | Addington et al. | Feb 2004 | A1 |
| 20040025190 | McCalla et al. | Feb 2004 | A1 |
| 20040034873 | Zenoni | Feb 2004 | A1 |
| 20040034877 | Nogues | Feb 2004 | A1 |
| 20040045032 | Cummings et al. | Mar 2004 | A1 |
| 20040045035 | Cummings et al. | Mar 2004 | A1 |
| 20040045037 | Cummings et al. | Mar 2004 | A1 |
| 20040047599 | Grzeczkowski | Mar 2004 | A1 |
| 20040049694 | Candelore | Mar 2004 | A1 |
| 20040060076 | Song | Mar 2004 | A1 |
| 20040073915 | Dureau | Apr 2004 | A1 |
| 20040078809 | Drazin | Apr 2004 | A1 |
| 20040093394 | Weber et al. | May 2004 | A1 |
| 20040103120 | Fickle | May 2004 | A1 |
| 20040103429 | Carlucci et al. | May 2004 | A1 |
| 20040103479 | Mossbeck et al. | Jun 2004 | A1 |
| 20040104842 | Drury et al. | Jun 2004 | A1 |
| 20040113936 | Dempski | Jun 2004 | A1 |
| 20040114539 | Beshai | Jun 2004 | A1 |
| 20040117817 | Kwon et al. | Jun 2004 | A1 |
| 20040117846 | Karaoguz et al. | Jun 2004 | A1 |
| 20040123125 | Zuili | Jun 2004 | A1 |
| 20040133467 | Siler | Jul 2004 | A1 |
| 20040133923 | Watson et al. | Jul 2004 | A1 |
| 20040137918 | Varonen et al. | Jul 2004 | A1 |
| 20040148625 | Eldering et al. | Jul 2004 | A1 |
| 20040153525 | Borella | Aug 2004 | A1 |
| 20040162900 | Bucher | Aug 2004 | A1 |
| 20040163111 | Palazzo et al. | Aug 2004 | A1 |
| 20040163129 | Chapman et al. | Aug 2004 | A1 |
| 20040172531 | Little et al. | Sep 2004 | A1 |
| 20040177383 | Martinolich et al. | Sep 2004 | A1 |
| 20040181811 | Rakib | Sep 2004 | A1 |
| 20040185856 | McKenna et al. | Sep 2004 | A1 |
| 20040189873 | Konig et al. | Sep 2004 | A1 |
| 20040193712 | Benenati et al. | Sep 2004 | A1 |
| 20040199789 | Shaw et al. | Oct 2004 | A1 |
| 20040221305 | Broussard et al. | Nov 2004 | A1 |
| 20040246933 | Valko | Dec 2004 | A1 |
| 20040250273 | Swix et al. | Dec 2004 | A1 |
| 20040255139 | Giobbi | Dec 2004 | A1 |
| 20040255335 | Fickle et al. | Dec 2004 | A1 |
| 20040261099 | Durden et al. | Dec 2004 | A1 |
| 20040264511 | Futch et al. | Dec 2004 | A1 |
| 20040264551 | Eidson | Dec 2004 | A1 |
| 20040266336 | Patsiokas et al. | Dec 2004 | A1 |
| 20040268386 | Logan et al. | Dec 2004 | A1 |
| 20050021940 | Ma | Jan 2005 | A1 |
| 20050022237 | Nomura | Jan 2005 | A1 |
| 20050022242 | Rosetti et al. | Jan 2005 | A1 |
| 20050022247 | Bitran et al. | 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 |
| 20050038904 | Dougall | Feb 2005 | A1 |
| 20050039205 | Riedl | Feb 2005 | A1 |
| 20050049886 | Grannan et al. | Mar 2005 | A1 |
| 20050055220 | Lee et al. | Mar 2005 | A1 |
| 20050060742 | Riedl et al. | Mar 2005 | A1 |
| 20050060745 | Riedl et al. | Mar 2005 | A1 |
| 20050071882 | Rodriguez et al. | Mar 2005 | A1 |
| 20050080330 | Masuzawa et al. | Apr 2005 | A1 |
| 20050086683 | Meyerson | Apr 2005 | A1 |
| 20050086691 | Dudkiewicz et al. | Apr 2005 | A1 |
| 20050091539 | Wang et al. | Apr 2005 | A1 |
| 20050091681 | Borden et al. | Apr 2005 | A1 |
| 20050102529 | Buddhikot et al. | May 2005 | A1 |
| 20050105396 | Schybergson | May 2005 | A1 |
| 20050108529 | Juneau | May 2005 | A1 |
| 20050108763 | Baran et al. | May 2005 | A1 |
| 20050111467 | Ng et al. | May 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050132191 | Joshi | Jun 2005 | A1 |
| 20050144333 | Kotzin | Jun 2005 | A1 |
| 20050144635 | Boortz | Jun 2005 | A1 |
| 20050153778 | Nelson et al. | Jul 2005 | A1 |
| 20050166224 | Ficco | Jul 2005 | A1 |
| 20050172312 | Lienhart et al. | Aug 2005 | A1 |
| 20050177855 | Maynard et al. | Aug 2005 | A1 |
| 20050179938 | Kayashima et al. | Aug 2005 | A1 |
| 20050183120 | Jain | Aug 2005 | A1 |
| 20050204019 | Flynn et al. | Sep 2005 | A1 |
| 20050210502 | Flickinger et al. | Sep 2005 | A1 |
| 20050216942 | Barton | Sep 2005 | A1 |
| 20050223032 | Shan et al. | Oct 2005 | A1 |
| 20050223409 | Rautila et al. | Oct 2005 | A1 |
| 20050229209 | Hildebolt et al. | Oct 2005 | A1 |
| 20050229213 | Ellis et al. | Oct 2005 | A1 |
| 20050233776 | Allen et al. | Oct 2005 | A1 |
| 20050235318 | Grauch et al. | Oct 2005 | A1 |
| 20050238238 | Xu et al. | Oct 2005 | A1 |
| 20050239402 | Gioscia et al. | Oct 2005 | A1 |
| 20050251454 | Wood | Nov 2005 | A1 |
| 20050261970 | Vucina | Nov 2005 | A1 |
| 20050262418 | Gehrmann | Nov 2005 | A1 |
| 20050262542 | Deweese et al. | Nov 2005 | A1 |
| 20050273819 | Knudson et al. | Dec 2005 | A1 |
| 20050273828 | Barton | Dec 2005 | A1 |
| 20050278741 | Robarts et al. | Dec 2005 | A1 |
| 20050278760 | Dewar et al. | Dec 2005 | A1 |
| 20050289588 | Kinnear | Dec 2005 | A1 |
| 20050289618 | Hardin | Dec 2005 | A1 |
| 20060010226 | Hurtta et al. | Jan 2006 | A1 |
| 20060013557 | Poslinski | Jan 2006 | A1 |
| 20060015502 | Szucs | Jan 2006 | A1 |
| 20060015580 | Gabriel et al. | Jan 2006 | A1 |
| 20060015637 | Chung | Jan 2006 | A1 |
| 20060015925 | Logan | Jan 2006 | A1 |
| 20060019702 | Anttila et al. | Jan 2006 | A1 |
| 20060020786 | Helms et al. | Jan 2006 | A1 |
| 20060021004 | Moran et al. | Jan 2006 | A1 |
| 20060021019 | Hinton et al. | Jan 2006 | A1 |
| 20060031558 | Ortega | Feb 2006 | A1 |
| 20060031883 | Ellis et al. | Feb 2006 | A1 |
| 20060031892 | Cohen | Feb 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060041910 | Hatanaka et al. | Feb 2006 | A1 |
| 20060047603 | Fontijn | Mar 2006 | A1 |
| 20060047745 | Knowles et al. | Mar 2006 | A1 |
| 20060047957 | Helms et al. | Mar 2006 | A1 |
| 20060075230 | Baird, III | Apr 2006 | A1 |
| 20060080408 | Istvan et al. | Apr 2006 | A1 |
| 20060088063 | Hartung et al. | Apr 2006 | A1 |
| 20060089911 | Dandekar et al. | Apr 2006 | A1 |
| 20060095940 | Yearwood | May 2006 | A1 |
| 20060107302 | Zdepski | May 2006 | A1 |
| 20060116966 | Pedersen et al. | Jun 2006 | A1 |
| 20060117341 | Park | Jun 2006 | A1 |
| 20060117365 | Ueda et al. | Jun 2006 | A1 |
| 20060117366 | Fries | Jun 2006 | A1 |
| 20060123147 | Yasuhara | Jun 2006 | A1 |
| 20060130099 | Rooyen | Jun 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060130120 | Brandyberry et al. | Jun 2006 | A1 |
| 20060136964 | Diez et al. | Jun 2006 | A1 |
| 20060149850 | Bowman | Jul 2006 | A1 |
| 20060159048 | Han | Jul 2006 | A1 |
| 20060161635 | Lamkin et al. | Jul 2006 | A1 |
| 20060163340 | Leiper | Jul 2006 | A1 |
| 20060167808 | Greene et al. | Jul 2006 | A1 |
| 20060168119 | Inoue | Jul 2006 | A1 |
| 20060168616 | Candelore | Jul 2006 | A1 |
| 20060171390 | La Joie | Aug 2006 | A1 |
| 20060171423 | Helms et al. | Aug 2006 | A1 |
| 20060173787 | Weber et al. | Aug 2006 | A1 |
| 20060173974 | Tang | Aug 2006 | A1 |
| 20060176884 | Fair et al. | Aug 2006 | A1 |
| 20060185004 | Song et al. | Aug 2006 | A1 |
| 20060187900 | Akbar | Aug 2006 | A1 |
| 20060190336 | Pisaris-Henderson et al. | Aug 2006 | A1 |
| 20060195553 | Nakamura | Aug 2006 | A1 |
| 20060200559 | Ling et al. | Sep 2006 | A1 |
| 20060200761 | Judd et al. | Sep 2006 | A1 |
| 20060200865 | Leake, Jr. et al. | Sep 2006 | A1 |
| 20060206565 | Ganesan et al. | Sep 2006 | A1 |
| 20060206712 | Dillaway et al. | Sep 2006 | A1 |
| 20060209799 | Gallagher et al. | Sep 2006 | A1 |
| 20060218604 | Riedl et al. | Sep 2006 | A1 |
| 20060222321 | Russ | Oct 2006 | A1 |
| 20060242267 | Grossman | Oct 2006 | A1 |
| 20060248209 | Chiu et al. | Nov 2006 | A1 |
| 20060248355 | Thayer | Nov 2006 | A1 |
| 20060248553 | Mikkelson et al. | Nov 2006 | A1 |
| 20060248555 | Eldering | Nov 2006 | A1 |
| 20060253328 | Kohli et al. | Nov 2006 | A1 |
| 20060253545 | Lakamp | Nov 2006 | A1 |
| 20060253584 | Dixon et al. | Nov 2006 | A1 |
| 20060253864 | Easty | Nov 2006 | A1 |
| 20060253894 | Bookman et al. | Nov 2006 | A1 |
| 20060256814 | Caci | Nov 2006 | A1 |
| 20060259924 | Boortz et al. | Nov 2006 | A1 |
| 20060259927 | Acharya et al. | Nov 2006 | A1 |
| 20060272032 | Jogand-Coulomb et al. | Nov 2006 | A1 |
| 20060277569 | Smith | Dec 2006 | A1 |
| 20060277576 | Acharya et al. | Dec 2006 | A1 |
| 20060282319 | Maggio | Dec 2006 | A1 |
| 20060291506 | Cain | Dec 2006 | A1 |
| 20060291507 | Sarosi et al. | Dec 2006 | A1 |
| 20060293954 | Anderson et al. | Dec 2006 | A1 |
| 20060294259 | Matefi et al. | Dec 2006 | A1 |
| 20060294371 | Fanning | Dec 2006 | A1 |
| 20070019645 | Menon | Jan 2007 | A1 |
| 20070022032 | Anderson et al. | Jan 2007 | A1 |
| 20070022459 | Gaebel, Jr. et al. | Jan 2007 | A1 |
| 20070022469 | Cooper et al. | Jan 2007 | A1 |
| 20070027809 | Alve | Feb 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070038931 | Allaire | Feb 2007 | A1 |
| 20070049245 | Lipman | Mar 2007 | A1 |
| 20070061331 | Ramer et al. | Mar 2007 | A1 |
| 20070061336 | Ramer | Mar 2007 | A1 |
| 20070067297 | Kublickis et al. | Mar 2007 | A1 |
| 20070067851 | Fernando et al. | Mar 2007 | A1 |
| 20070076728 | Rieger et al. | Apr 2007 | A1 |
| 20070077921 | Hayashi et al. | Apr 2007 | A1 |
| 20070078714 | Ott, IV et al. | Apr 2007 | A1 |
| 20070083899 | Compton et al. | Apr 2007 | A1 |
| 20070086372 | Lee | Apr 2007 | A1 |
| 20070088801 | Levkovitz et al. | Apr 2007 | A1 |
| 20070088832 | Tsang et al. | Apr 2007 | A1 |
| 20070089127 | Flickinger et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070101359 | Schiller et al. | May 2007 | A1 |
| 20070106814 | Son et al. | May 2007 | A1 |
| 20070107035 | Howe et al. | May 2007 | A1 |
| 20070112685 | Yamamichi | May 2007 | A1 |
| 20070113243 | Brey | May 2007 | A1 |
| 20070115389 | McCarthy et al. | May 2007 | A1 |
| 20070115922 | Schneider | May 2007 | A1 |
| 20070118857 | Chen et al. | May 2007 | A1 |
| 20070121612 | Nadeau | May 2007 | A1 |
| 20070121678 | Brooks et al. | May 2007 | A1 |
| 20070123253 | Simongini et al. | May 2007 | A1 |
| 20070124416 | Casey et al. | May 2007 | A1 |
| 20070124488 | Baum et al. | May 2007 | A1 |
| 20070124781 | Casey et al. | May 2007 | A1 |
| 20070129987 | Hauser et al. | Jun 2007 | A1 |
| 20070136743 | Hasek | Jun 2007 | A1 |
| 20070136777 | Hasek et al. | Jun 2007 | A1 |
| 20070150919 | Morishita | Jun 2007 | A1 |
| 20070157249 | Cordray et al. | Jul 2007 | A1 |
| 20070157260 | Walker | Jul 2007 | A1 |
| 20070162958 | Kao et al. | Jul 2007 | A1 |
| 20070166687 | Bell et al. | Jul 2007 | A1 |
| 20070168429 | Apfel et al. | Jul 2007 | A1 |
| 20070171274 | Yim | Jul 2007 | A1 |
| 20070186103 | Randle et al. | Aug 2007 | A1 |
| 20070204300 | Markley et al. | Aug 2007 | A1 |
| 20070204310 | Hua et al. | Aug 2007 | A1 |
| 20070204311 | Hasek et al. | Aug 2007 | A1 |
| 20070204314 | Hasek et al. | Aug 2007 | A1 |
| 20070209054 | Cassanova | Sep 2007 | A1 |
| 20070209059 | Moore et al. | Sep 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070219910 | Martinez | Sep 2007 | A1 |
| 20070220158 | Tolgu | Sep 2007 | A1 |
| 20070220573 | Chiussi et al. | Sep 2007 | A1 |
| 20070220605 | Chien | Sep 2007 | A1 |
| 20070233857 | Cheng et al. | Oct 2007 | A1 |
| 20070237330 | Srivastava | Oct 2007 | A1 |
| 20070244760 | Bodnar et al. | Oct 2007 | A1 |
| 20070247395 | Barraclough et al. | Oct 2007 | A1 |
| 20070250880 | Hainline | Oct 2007 | A1 |
| 20070260604 | Haeuser | Nov 2007 | A1 |
| 20070261116 | Prafullchandra et al. | Nov 2007 | A1 |
| 20070265978 | Kahn et al. | Nov 2007 | A1 |
| 20070271388 | Bowra | Nov 2007 | A1 |
| 20070276864 | Espelien | Nov 2007 | A1 |
| 20070276925 | La Joie et al. | Nov 2007 | A1 |
| 20070276926 | Lajoie et al. | Nov 2007 | A1 |
| 20070279625 | Rzasa et al. | Dec 2007 | A1 |
| 20070280110 | Murphy et al. | Dec 2007 | A1 |
| 20070294178 | Pinder et al. | Dec 2007 | A1 |
| 20070294720 | Cohen et al. | Dec 2007 | A1 |
| 20080009268 | Ramer et al. | Jan 2008 | A1 |
| 20080040758 | Beetcher et al. | Feb 2008 | A1 |
| 20080052157 | Kadambi et al. | Feb 2008 | A1 |
| 20080059409 | Montpetit | Mar 2008 | A1 |
| 20080072249 | Hovnanian et al. | Mar 2008 | A1 |
| 20080090513 | Collins et al. | Apr 2008 | A1 |
| 20080092181 | Britt | Apr 2008 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080098422 | Rodriguez et al. | Apr 2008 | A1 |
| 20080115161 | Kurzion | May 2008 | A1 |
| 20080115169 | Ellis et al. | May 2008 | A1 |
| 20080139193 | Hao et al. | Jun 2008 | A1 |
| 20080147497 | Tischer | Jun 2008 | A1 |
| 20080155589 | McKinnon et al. | Jun 2008 | A1 |
| 20080155600 | Klappert et al. | Jun 2008 | A1 |
| 20080155607 | Klappert | Jun 2008 | A1 |
| 20080155616 | Logan et al. | Jun 2008 | A1 |
| 20080162623 | Flynn | Jul 2008 | A1 |
| 20080163305 | Johnson et al. | Jul 2008 | A1 |
| 20080171423 | Ieong et al. | Jul 2008 | A1 |
| 20080188964 | Bech et al. | Aug 2008 | A1 |
| 20080192820 | Brooks et al. | Aug 2008 | A1 |
| 20080195871 | Peinado et al. | Aug 2008 | A1 |
| 20080196056 | Bassett et al. | Aug 2008 | A1 |
| 20080209464 | Wright-Riley | Aug 2008 | A1 |
| 20080216106 | Maxwell et al. | Sep 2008 | A1 |
| 20080221986 | Soicher et al. | Sep 2008 | A1 |
| 20080229354 | Morris et al. | Sep 2008 | A1 |
| 20080235722 | Baugher et al. | Sep 2008 | A1 |
| 20080263578 | Bayer et al. | Oct 2008 | A1 |
| 20080271068 | Ou et al. | Oct 2008 | A1 |
| 20080273591 | Brooks et al. | Nov 2008 | A1 |
| 20080282299 | Koat et al. | Nov 2008 | A1 |
| 20080289009 | Lee et al. | Nov 2008 | A1 |
| 20080313671 | Batrouny et al. | Dec 2008 | A1 |
| 20080313691 | Cholas et al. | Dec 2008 | A1 |
| 20090019134 | Bellifemine et al. | Jan 2009 | A1 |
| 20090019492 | Grasset | Jan 2009 | A1 |
| 20090030802 | Plotnick et al. | Jan 2009 | A1 |
| 20090034521 | Kato | Feb 2009 | A1 |
| 20090064219 | Minor | Mar 2009 | A1 |
| 20090094652 | Al Adham et al. | Apr 2009 | A1 |
| 20090098861 | Kalliola et al. | Apr 2009 | A1 |
| 20090100459 | Riedl et al. | Apr 2009 | A1 |
| 20090132346 | Duggal et al. | May 2009 | A1 |
| 20090138922 | Thomas et al. | May 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090198794 | Beals | Aug 2009 | A1 |
| 20090210899 | Lawrence-Apfelbaum et al. | Aug 2009 | A1 |
| 20090222853 | White et al. | Sep 2009 | A1 |
| 20090235319 | Mao et al. | Sep 2009 | A1 |
| 20090248794 | Helms et al. | Oct 2009 | A1 |
| 20090249473 | Cohn | Oct 2009 | A1 |
| 20090282241 | Prafullchandra et al. | Nov 2009 | A1 |
| 20090313654 | Paila et al. | Dec 2009 | A1 |
| 20090317065 | Fyock et al. | Dec 2009 | A1 |
| 20090319379 | Joao | Dec 2009 | A1 |
| 20090320059 | Bolyukh | Dec 2009 | A1 |
| 20090327346 | Teinila et al. | Dec 2009 | A1 |
| 20090328113 | Van De Klashorst | Dec 2009 | A1 |
| 20100042478 | Reisman | Feb 2010 | A1 |
| 20100082440 | Vaidyanathan et al. | Apr 2010 | A1 |
| 20100083362 | Francisco et al. | Apr 2010 | A1 |
| 20100107194 | McKissick et al. | Apr 2010 | A1 |
| 20100122285 | Begeja et al. | May 2010 | A1 |
| 20100146539 | Hicks, III et al. | Jun 2010 | A1 |
| 20100175584 | Kusaka et al. | Jul 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100251305 | Kimble et al. | Sep 2010 | A1 |
| 20100251312 | Albano et al. | Sep 2010 | A1 |
| 20100269128 | Gordon | Oct 2010 | A1 |
| 20100293221 | Sidman et al. | Nov 2010 | A1 |
| 20110015989 | Tidwell et al. | Jan 2011 | A1 |
| 20110016479 | Tidwell et al. | Jan 2011 | A1 |
| 20110016482 | Tidwell et al. | Jan 2011 | A1 |
| 20110040755 | Hindle et al. | Feb 2011 | A1 |
| 20110041146 | Lewis | Feb 2011 | A1 |
| 20110055347 | Hu et al. | Mar 2011 | A1 |
| 20110099593 | Kim et al. | Apr 2011 | A1 |
| 20110103374 | Lajoie et al. | May 2011 | A1 |
| 20110106784 | Terheggen et al. | May 2011 | A1 |
| 20110202270 | Sharma, Sr. et al. | Aug 2011 | A1 |
| 20120005756 | Hoefelmeyer et al. | Jan 2012 | A1 |
| 20120011567 | Cronk | Jan 2012 | A1 |
| 20120117584 | Gordon | May 2012 | A1 |
| 20120158547 | Wood et al. | Jun 2012 | A1 |
| 20120284765 | Killick et al. | Nov 2012 | A1 |
| 20120291140 | Robert | Nov 2012 | A1 |
| 20130007799 | Sandoval | Jan 2013 | A1 |
| 20130036011 | Roberts et al. | Feb 2013 | A1 |
| 20130219458 | Ramanathan | Aug 2013 | A1 |
| 20130227608 | Evans et al. | Aug 2013 | A1 |
| 20130239134 | Britt et al. | Sep 2013 | A1 |
| 20130239135 | Parker et al. | Sep 2013 | A1 |
| 20140052696 | Soroushian | Feb 2014 | A1 |
| 20140075466 | Zhao | Mar 2014 | A1 |
| 20140282695 | Bakar et al. | Sep 2014 | A1 |
| 20150304698 | Redol | Oct 2015 | A1 |
| 20150348129 | Inoue et al. | Dec 2015 | A1 |
| 20150382034 | Thangaraj et al. | Dec 2015 | A1 |
| 20160055606 | Petrovic et al. | Feb 2016 | A1 |
| 20160094893 | Tse | Mar 2016 | A1 |
| 20160182973 | Winograd et al. | Jun 2016 | A1 |
| 20170070789 | Liassides et al. | Mar 2017 | A1 |
| 20180035174 | Littlejohn | Feb 2018 | A1 |
| 20190251602 | Cormie | Aug 2019 | A1 |
| 20200059693 | Neumeier et al. | Feb 2020 | A1 |
| 20200329260 | Mathur | Oct 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2376550 | Dec 2000 | CA |
| 2376550 | Aug 2008 | CA |
| 2438497 | Nov 2013 | CA |
| 1134951 | Sep 2001 | EP |
| 1691523 | Aug 2006 | EP |
| S5218653 | Feb 1977 | JP |
| S5218653 | Feb 1977 | JP |
| S5239237 | Mar 1977 | JP |
| H01226681 | Sep 1989 | JP |
| H03272977 | Dec 1991 | JP |
| H0517083 | Jan 1993 | JP |
| H0558564 | Mar 1993 | JP |
| H05201624 | Jun 1993 | JP |
| 2002335507 | Nov 2002 | JP |
| 2005519365 | Jun 2005 | JP |
| 2005519501 | Jun 2005 | JP |
| 2005339093 | Dec 2005 | JP |
| 20060009376 | Jan 2006 | KR |
| WO-9617306 | Jun 1996 | WO |
| WO-9929107 | Jun 1999 | WO |
| WO-9963759 | Dec 1999 | WO |
| WO-0018120 | Mar 2000 | WO |
| WO-0072592 | Nov 2000 | WO |
| WO-0110125 | Feb 2001 | WO |
| WO-0156285 | Aug 2001 | WO |
| WO-0160071 | Aug 2001 | WO |
| WO-0191474 | Nov 2001 | WO |
| WO-2005015422 | Feb 2005 | WO |
| Entry |
|---|
| David, “The Beginnings and Prospective Ending of ‘End-to-End’: An Evolutionary Perspective On the Internet's Architecture”, 2001. |
| Ford, “Unmanaged Internet Protocol Scalable Application-Friendly Internet Routing”, 2003. |
| Ford, “Unmanaged Internet Protocol Taming the Edge Network Management Crisis”, 2004. |
| Sadok et al., “Trends in Network and Device Composition”, 2006. |
| Merriam-Webster, “apparatus”, 2019 (Year: 2019). |
| Microsoft Computer Dictionary, “device”, 5th edition, 2002 (Year: 2002). |
| Wikipedia, “Client (computing)”, 2020 (Year: 2020). |
| Merriam-Webster, “mapping”, 2020 (Year: 2020). |
| Dictionary, “recorded”, 2021 (Year: 2021). |
| Dictionary, “recording”, 2021 (Year: 2021). |
| Cantor, et al., Assertions and Protocols for the OASIS Security Assertion Markup Language (SAML) V2.0, OASIS Standard, Mar. 15, 2005. Document ID: saml-core-2.0-os (http://docs.oasis-open.org/securit/saml/v2.0/saml-core-2.0-os.pdf). |
| Open Cable Specification entitled “Enhanced TV Binary Interchange Format 1 0” OC-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. |
| 3 Point Digital to Showcase Revolutionary Video-On-Demand at Streaming Media West '99, http://www.vsoftcom/press 1999nhtm, Dec. 3, 1999. |
| Almeroth, IEEE Journal on Selected Areas in Communications, The Use of Multicast Delivery to Provide a Scalable and Interactive Video-On-Demand Service, pp. 1110-1122, vol. 14: No. 6, 1996. |
| Bodzinga et al., “Enhancing the IPTV Service Architecture to Enable Service Innovation”, International Engineering Consortium, May 1, 2006. |
| Butts, Tom, “Israeli Defense Technology Fuel's Vsoft's Software”, pp. 1-2, http://www.vsoft.com/prints/israeli.sub.--defence.htm, Feb. 1, 1999. |
| Cantor, et al., Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0, OASIS Standard, Mar. 2005 (http://docs.oasis-open.org/security/saml/v2.0/). |
| Carnoy, David, “Anthony Wood and Mike Ramsey at War,” Success, Mar. 1999, pp. 52-57. |
| Congdon et al., “IEEE 802.1 X Remote Authentication Dial in User Service (RADIUS) Usage Guidelines”, RFC 3580, 2003. |
| Furchgott, Roy, “Don't People Want to Control Their TV's?” The New York Times, Aug. 24, 2000, p. GI. |
| Hamilton, David P., “Driving Force”, The Wall Street Journal, Jun. 26, 2000, p. R12. |
| Jacobs, Karen (Dec. 7, 1999) “Elevator Maker to Add Commercial Touch,” The Wall Street Journal, pp. 1-2. |
| Kahaner, (Mar. 16, 1991) “Hitachi 1991 Technology Exhibition, Tokyo,” Asian Technology Information Program, pp. 1-14. |
| Lewis M,, “Boom Box”, The New York Times Magazine, Aug. 13, 2000, p. 36. |
| Margo Lipschitz Sugarman, “A Picture of the Future” pp. 1-2, http://vvww.vsoft.com/prints/picture.sub.-- of.sub.--the.sub.--future.htm, Dec. 20, 1999. |
| Maxwell, Kim, Residential Broadband: An Insider's Guide to the Battle for the Last Mile, 1999, pp. 43-46, 308-312, John Wiley & Sons, Inc., New York. |
| McDevitt et al., “Switched vs Broadcast Video for Fiber-To-The Home Systems”, 1990. |
| Merriam Webster, “subscribe”, 2015. |
| Metadata Specifications, CableLabs Asset Distribution Interface Specification, Version 1.1 MD-SP-ADI 1-104-060505, May 5, 2006. |
| Motorola Next-Generation CMTS Architecture Protecting Network Investments While Migrating to Next-Generation CMTS Platforms, 2004 Motorola, Inc. |
| Parsons, Patrick R., et al., The Cable and Satellite Televison Industries, 1998, pp. 162-163, 170-172, Allyn and Bacon, Boston. |
| Perdue, Lewis (Jul. 20, 1999) “Forget Elevator Music Here Comes Elevator Internet,” Internet VC Watch, pp. 1-2. |
| Stevens Institute of Technology, Spring 1999 Final Report, pp. 1-12. |
| Videodick 2.0 is Now Available on Sun Servers, p. 1, http://www.vsoft.com/press1999d.htm, Apr. 19, 1999. |
| Vsoft Launches Videoclick .COPYRGT. Home at IBC 2000, pp. 1-2, http:/www.vsoft.com/pres2000o.htm, Sep. 8, 2000. |
| Vsoft to Implement Its Advanced Videoclick Interactive TV Software on Power TV Based Digital Cable Set-Top Boxes, pp. 1-2, http://www.vsoft.com/press1999m.htm, Dec. 13, 1999. |
| Vsoft to Present First Set-Top Box Implementation of Its Digital Video Software Platform, Targeted to Service Providers of Digital Video Services for Home Video, p. 1, http://www.vsoft.com/press1999j.htm, Sep. 8, 1999. |
| Wikipedia, “Content delivery network”, 2015. |
| Wikipedia, “Hybrid fibre-coaxial”, 2015. |
| Wikipedia, “Packet switching”, 2015. |
| Wikipedia, “switched”, 2015. |
| Yoneda, et al. (Dec. 1997) “Multi-Objective Elevator Supervisory-Control System with Individual Floor-Situation Control,” Hitachi Review, p. 1, month & year only. |
| Number | Date | Country | |
|---|---|---|---|
| 20170006317 A1 | Jan 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11441476 | May 2006 | US |
| Child | 15201181 | US |
