Methods and apparatus for providing and uploading content to personalized network storage

Description

BACKGROUND
1. Technological Field

The present disclosure relates generally to the field of providing content over a network and other distribution channels, and specifically in one aspect to the configuration, delivery, upload, and storage of such content over a managed network such as e.g., cable television network.

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. The advent of PVR technology has greatly increased the ability of a subscriber to utilize certain content delivered over their cable system on their schedule. Some PVR devices can be used to transmit the stored content over a network interface to another device (which may or may not be remote from the PVR) where the same or another user can access the content. As a result, PVRs allow users a great degree of control over the playback and viewing of their selected content.

Additionally, network-based content recording and storage allow users of a network to obtain what would otherwise be “live” content (e.g., linear television broadcasts or the like) at a time convenient to the user. These systems typically receive instructions from the user as to which programming they want to view, and the network “cloud” streams the requested content to that user. Variants of these types of systems either receive prior instructions from a user before the broadcast of the live event, or alternatively store various content based on some other criteria (e.g., popularity), and then allow the user a period of time to watch it.

However, content source or copyright owner must have assurances that the network operator (e.g., multiple systems operator or 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. Content owners may 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, such as in the case of networked PVRs (NPVRs).

Network operators that provide users with personalized PVR functionality and storage in the network can simplify the distribution and upgrade process of their services, and offer potentially unlimited storage capacity, without sacrificing ease of use or convenience at the user end. However, current PVR and NPVR implementations avoid uploading content to network storage when the content has already been received at a PVR or NPVR, due in part to restrictions associated with upload bandwidth, thereby potentially leaving some copyright concerns unaddressed.

Accordingly, there is a need for improved methods and apparatus which effectively balances the preservation of copyright interests with the convenience and flexibility of PVR and NPVR functionality.

These methods and apparatus would also, in one embodiment, 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.

SUMMARY

The foregoing needs are satisfied by providing improved apparatus and methods for content management and device configuration for uploading and storing content over a content network.

In a first aspect, a method of content management is disclosed. In one embodiment, the method is utilized within a content delivery network having a plurality of users, and the method includes receiving content at a client device, the client device associated with at least one of the plurality of users of the network; and in response to the act of receiving, causing at least a portion of the content to be uploaded to a storage entity of the network. In one variant, the storage entity is configured to store the content at a storage location specifically associated with at least the at least one user.

In another aspect, a network apparatus configured to obtain and store content from one or more client devices is disclosed. In one embodiment, the apparatus includes: a storage apparatus; and a digital processor configured to run at least one computer program thereon, the computer program comprising a plurality of instructions. In one variant, the instructions are configured to, when executed, cause the network apparatus to: configure at least one of the one or more client devices for upload; receive a request from at least one of the one or more client devices for the content; determine whether the requested content has previously been uploaded to a storage location specifically associated with the one or more client devices; and based at least in part on the determination, provide the requested content to the at least one of the one or more client devices.

In another aspect, a method of managing content via a content delivery network, so as to ensure copyright preservation is disclosed. In one embodiment, the method includes: recording a first content element on a recording device at a first location, the recording device being associated with a first user; automatically uploading the first content element to a second device at a second location, the second location being in communication with the first location via the content delivery network, the first content element being made accessible only to the first user so as to protect a copyright associated with the first content element.

In a further aspect, a consumer premises device is disclosed. In one embodiment, the device includes computerized logic configured to cause download of content from a network entity to the device (or a proxy thereof), and also upload of the content back to the same or different network entity, the receiving network entity having one or more access restrictions associated therewith.

In yet another aspect, a computer readable apparatus is disclosed. In one embodiment, the apparatus includes a storage medium and at least one computer program disposed thereon, the at least one program configured to, when executed, implement content copyright protection upload functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating an exemplary hybrid fiber coax (HFC) cable network configuration useful with various aspects of the present disclosure.

FIG. 1a is a functional block diagram illustrating one exemplary HFC cable network head-end configuration useful with various aspects of the present disclosure.

FIG. 1b is a functional block diagram illustrating one exemplary local service node configuration useful with various aspects of the present disclosure.

FIG. 1c is a functional block diagram illustrating one exemplary broadcast switched architecture (BSA) useful with various aspects of the present disclosure.

FIG. 1d is a functional block diagram illustrating one exemplary packetized content delivery network architecture useful with the present disclosure.

FIG. 2 is a functional block diagram of one exemplary embodiment of the system architecture according to the disclosure.

FIG. 3 is a functional block diagram of one exemplary embodiment of a network server apparatus adapted for use with the system architecture of FIG. 2.

FIG. 4 is a functional block diagram of one exemplary embodiment of consumer premises equipment (CPE) adapted for use with the system architecture.

FIG. 5 is a logical flowchart illustrating one embodiment of the generalized content delivery, upload and storage methodology of the disclosure.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer to like parts throughout.

As used herein, the term “application” refers generally and without limitation 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., DSTEts), 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-I (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 without limitation 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 glia, 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, RDRAM, 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 00B, 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/v.

As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth, 3G, LTE/LTE-A, HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, narrowbancl/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, improved apparatus and methods are provided to, inter alia, enable upload and storage of content over a network. In one embodiment, content stored on a CPE is uploaded to server at the head-end, as opposed to traditional network DVR functionality which records content for subscribers at the head-end before it is received by the CPE. The improved apparatus and methods disclosed herein may be useful, for example, as one potential model for preserving the digital rights of content owners.

In an exemplary embodiment, a CPE and/or server at the network head-end is configured with logic to manage content delivery, upload and storage. A user receives content from a content source (which may be the network, or yet another source), and automatically uploads the content to a network storage device, where a complete copy of the content is made available for subsequent strearning/download to the user (or user devices that are allowed access to the network storage device).

In addition, the system determines which content items have already been uploaded/stored to the head-end so that an optimal number of copies are stored at the head-end and/or client device. Further, uploads may be prioritized in accordance with the copyright of individual content items.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods 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 e.g., a “secondary” communication channel or network, the general principles and advantages of the system may be extended to other types of networks and architectures where 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 system 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 are described primarily in the context of 6 MHz RF channels within the HFC network, any frequency/bandwidth, such as for example 8 MHz channels may be applicable.

Furthermore, as referenced above, the system is in no way limited to traditional cable system frequencies (i.e., below 1 GHz), and in fact may be used with systems that operate above 1 GHz band in center frequency or bandwidth, to include without limitation so-called ultra-wideband (UWB) systems. For example, in one variant, high-bandwidth UWB signals imposed atop the traditional QAMs of the cable network are used to provide a high-speed data download capability for the content to be utilized at the subscriber's premises (e.g., applications or archived data).

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 other types of protocols (and in fact bearer networks to include other internets and intranets) may be used to implement the described functionality.

FIG. 1 illustrates a typical generalized content delivery network configuration with which the personal media delivery apparatus and methods may be used. The various components of the network 100 include (i) one or more data and application origination points 102; (ii) one or more content sources 103, (iii) one or more application distribution servers 104; (iv) one or more VOD servers 105, and (v) consumer premises equipment (CPE) 106. The distribution server(s) 104, VOD servers 105 and CPE(s) 106 are connected via a bearer (e.g., HFC) network 101. A simple architecture comprising one of each of the aforementioned components 102, 104, 105, 106 is shown in FIG. 1 for simplicity, although it will be recognized that comparable architectures with multiple origination points, distribution servers, VOD servers, and/or CPE devices (as well as different network topologies) may be utilized. For example, the head-end architecture of FIG. 1a (described in greater detail below) may be used.

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.

Referring now to FIG. 1a, one exemplary embodiment of a head-end architecture is described. As shown in FIG. 1a, the head-end architecture 150 comprises typical head-end components and services including billing module 152, subscriber management system (SMS) and CPE configuration management module 154, cable-modem termination system (CMTS) and OOB system 156, as well as LAN(s) 158, 160 placing the various components in data communication with one another. It will be appreciated that while a bar or bus LAN topology is illustrated, any number of other arrangements as previously referenced (e.g., ring, star, etc.) may be used. It will also be appreciated that the head-end configuration depicted in FIG. 1a is high-level, conceptual architecture and that each MSO may have multiple head-ends deployed using custom architectures.

The architecture 150 of FIG. 1a further includes a multiplexer/encrypter/modulator (MEM) 162 coupled to the HFC network 101 adapted to “condition” content for transmission over the network. The distribution servers 104 are coupled to the LAN 160, which provides access to the MEM 162 and network 101 via one or more file servers 170. The VOD servers 105 are coupled to the LAN 160 as well, although other architectures may be employed (such as for example where the VOD servers are associated with a core switching device such as an 802.3z Gigabit Ethernet device). As previously described, information is carried across multiple channels. Thus, the head-end must be adapted to acquire the information for the carried channels from various sources. Typically, the channels being delivered from the head-end 150 to the CPE 106 (“downstream”) are multiplexed together in the head-end and sent to neighborhood hubs (FIG. 1b) via a variety of interposed network components.

Content (e.g., audio, video, 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 system 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 FIG. 1b, the network 101 of FIGS. 1 and 1a comprises a fiber/coax arrangement wherein the output of the MEM 162 of FIG. 1a is transferred to the optical domain (such as via an optical transceiver 177 at the head-end or further downstream). The optical domain signals are then distributed to a fiber node 178, which further distributes the signals over a distribution network 180 to a plurality of local servicing nodes 182. This provides an effective 1:N expansion of the network at the local service end.

“Switched” Networks—

FIG. 1c illustrates an exemplary “switched” network architecture. While a so-called “broadcast switched architecture” or BSA network is illustrated in this exemplary embodiment, it will be recognized that the system is in no way limited to such architectures.

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.

FIG. 1c shows the implementation details of one exemplary embodiment of this broadcast switched network architecture. Specifically, the head-end 150 contains switched broadcast control and media path functions 190, 192; these element cooperating to control and feed, respectively, downstream or edge switching devices 194 at the hub site which are used to selectively switch broadcast streams to various service groups. A BSA server 196 is also disposed at the hub site, and implements functions related to switching and bandwidth conservation (in conjunction with a management entity 198 disposed at the head-end). An optical transport ring 197 is utilized to distribute the dense wave-division multiplexed (D WDM) optical signals to each hub in an efficient fashion.

Co-owned and co-pending U.S. patent application Ser. No. 09/956,688 filed Sep. 20, 2001 and entitled “TECHNIQUE FOR EFFECTIVELY PROVIDING PROGRAM MATERIAL IN A CABLE TELEVISION SYSTEM”, incorporated herein by reference in its entirety, describes one exemplary broadcast switched digital architecture, 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 FIGS. 1a-1c (and FIG. 1d discussed below) can also deliver Internet data services using the Internet protocol (IP), although other protocols and transport mechanisms of the type well known in the digital communication art may be substituted. One exemplary delivery paradigm comprises delivering MPEG-based video content (e.g., “IPTV” or the like), with the video transported to user PCs (or IP-based STBs) over the aforementioned DOCSIS channels comprising MPEG (or other video codec such as H.264 or AVC) over IP over MPEG. That is, the higher layer MPEG—or other encoded content is encapsulated using an IP protocol, which then utilizes an MPEG packetization of the type well known in the art for delivery over the RF channels. In this fashion, a parallel delivery mode to the normal broadcast delivery exists; i.e., delivery of video content both over traditional downstream QAMs to the tuner of the user's STB or other receiver device for viewing on the television, and also as packetized IP data over the DOCSIS QAMs to the user's PC or other IP-enabled device via the user's cable modem.

Referring again to FIG. 1c, the IP packets associated with Internet services are received by edge switch 194, and forwarded to the cable modem termination system (CMTS) 199. The CMTS examines the packets, and forwards packets intended for the local network to the edge switch 194. Other packets are discarded or routed to another component.

The edge switch 194 forwards the packets receive from the CMTS 199 to the QAM modulator, which transmits the packets on one or more physical (QAM-modulated RF) channels to the CPEs. 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.

It will be appreciated that while the exemplary embodiments presented herein are described in the context of Internet services that include multicast and unicast data (e.g., using an Internet Protocol (IP) networking protocol over one or more transports), other types of services that include multicast transmission of data delivered over a network having multiple physical channels or even virtual or logical channels may be used. For example, switching between various physical channels that comprise a virtual channel, can itself be conducted according to the “switched” approach. As a simple illustration, if a first virtual channel is comprised of physical channels (e.g., QAMs) A, B and D, and a second virtual channel is comprised of QAMs C, E and F, a CM or other CPE can be configured to switch between the A/B/D and C/E/F virtual channels as if they were a single QAM.

“Packetized” Networks—

While the foregoing network architectures described herein can (and in fact do) carry packetized content (e.g., IP over MPEG for high-speed data or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), they are often not optimized for such delivery. Hence, in accordance with another embodiment, a “packet optimized” delivery network is used for carriage of the packet content (e.g., IPTV content). FIG. 1d illustrates one exemplary implementation of such a network, in the context of a 3GPP IMS (IP Multimedia Subsystem) network with common control plane and service delivery platform (SDP), as described in U.S. Provisional Patent Application Ser. No. 61/256,903 filed Oct. 30, 2009 and entitled “METHODS AND APPARATUS FOR PACKETIZED CONTENT DELIVERY OVER A CONTENT DELIVERY NETWORK”, which is now published as U.S. Patent Application Publication No. 2011/0103374 of the same title filed on Apr. 21, 2010, each of which is incorporated herein by reference in its entirety. Such a network provides, inter alia, significant enhancements in terms of common control of different services, implementation and management of content delivery sessions according to unicast or multicast models, etc.; however, it is appreciated that the various features of the present disclosure are in no way limited to this or any of the other foregoing architectures.

System Architecture—

FIG. 2 is a functional block diagram showing an exemplary embodiment of the content distribution system architecture 200 according to the disclosure. It will be appreciated that this generalized architecture may be readily integrated into the existing architecture of a cable television network (such as those shown in FIGS. 1-1d), or alternatively used in conjunction with other types of networks (e.g., satellite networks, DSL networks, optical fiber networks, terrestrial wireless networks, hybrid fiber copper (HFCu) networks, etc.).

As shown in FIG. 2, the exemplary embodiment of the system architecture 200 generally comprises one or more servers 208 (e.g., VOD or broadcast servers) associated with one or more local storage devices 212, one or more network storage devices 214, one or more content sources 216, and one or more CPEs 202 and/or client devices 206.

As shown in FIG. 2, the head-end receives content from a source (such as a web server, studio, etc.) and processes the content into a format compatible with the MSO network. For example, processing may comprise (without limitation): (i) decryption; (ii) authentication of the content source (to prevent, e.g., “spoof” attacks or providing false or surreptitious content); (iii) virus or other mal-ware screening; (iv) encoding, decoding, or transcoding; (v) protocol translation or encapsulation; (vi) “upconversion” or “downconversion” of resolution, and/or (vii) filtration, error correction, or other conditioning of the content. Metadata or other such ancillary data may also be appended to or associated with the ingested content, as described in greater detail subsequently herein.

A client-server software architecture is employed in the exemplary embodiment to provide content management. The software may be employed either wholly or partially on the server-side, such as via a server content management process 210 (SCM). Additionally, the software may be employed either wholly or partially on the client side (e.g., as a client content management process 204 (CCM)). Each of the SCM 210 or CCM 204 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.

In one embodiment, an object-oriented distributed application (DA) of the type well known in the art resides on the server portion of the DA, which in the illustrated embodiment can also function as the server content manager (SCM) 210, and is disposed at the head-end 150 of the network (such as on a VOD server or BSA manager 198). The client portion(s) 204 of the DA are disposed at a client device 202 or remote client device 206.

The content source 216 is also in communication with the server content management process 210, so that inter alia the content source can coordinate transfer of purchased or otherwise obtained content (or content prior to purchase) to the MSO network (e.g., local storage 212 and/or virtual storage 214), for supply to the CPE 202. The CPE 202 of the exemplary embodiment can communicate with the server 208 via any number of different channels including, e.g., an OOB upstream channel; in-band upstream channel allocated for this purpose, or a TCP/IP DOCSIS channel.

In one embodiment, the SCM 210 acts as the overall logical control or supervisory process for delivering content to subscribers. In this regard, the SCM 210 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, multicast/unicast IP generation and delivery, etc.

In another embodiment, the CPE 202 communicates with the MSO network via a DOCSIS modem or other such interface, which then relays the communication to an external network (e.g., Internet), which in turn passes the communication to the content source server 218. For example, the user's PC or Wi-Fi connected laptop or tablet at their premises can access the content source website using e.g., the device's browser and TCP/IP protocols, via the indigenous DOCSIS modem, or yet another upstream channel (such as a WiMAX reverse channel, or LTE cellular data interface). In the illustrated example, the CPE 202 and the content source 218 act substantially as peers, and the interposed networks providing physical media and routing functions, although it will be appreciated that other approaches may be used (e.g., such as where processing, reformatting or encapsulation, security wrappers, etc. are applied to the packets issued by the client device by the intermediate networks, routers, and gateways).

After the content source 218 receives the communications (either directly or indirectly) from the CPE 202, it then communicates with the MSO server 208 as previously described. The CPE 202 then subsequently communicates with the server 208, requesting e.g., delivery such as streaming or broadcast of the purchased content. The MSO server portion (or its proxy) then streams or broadcasts the content to the requesting device, or a designated target client device (e.g., one associated with a network or client device on or off the premises, such as a Wi-Fi enabled mobile device).

Content is transmitted to the requesting purchaser's CPE 202 or client device 206, such as via a session between the content server and the CPE 202 (e.g. VOD) that transmits the content over one or more in-band downstream QAMs. Alternatively, delivery may occur via a broadcast (e.g., BSA) mode, an IPTV (e.g., MPEG over IP) mode, unicast/multicast, via satellite link, or any other mode having suitable bandwidth and quality of service (QoS).

In one embodiment, the disclosed system 200 also advantageously provides for upload (such as a substantially automatic upload) of content to a server, storage device, or other network entity from a CPE 202 or other client device 206. This upload functionality of the system may serve as one potential model for preserving copyrights associated with delivered content. Specifically, by downloading the content to a particular user's (or group of user's) CPE, and then uploading the downloaded content in at least a substantially similar fowl, the receiving user or users has/have become the “owner” of the physical rendering of the content (contrast: copyright in the content) and any rights associated with that rendering (such as rights to perform, reproduce a copy for archival purposes, etc.), and hence what is uploaded back to the network can in fact be considered an “archival” or space-shifted copy of the content they already own. Note that in one implementation of the system 200 of FIG. 2, the content that is received by the CPE or other client 206 is stored on the receiving device in a substantially permanent form (as contrasted with purely ephemeral or transient storage), and then also transmitted upstream to e.g., the network server or storage device for storage thereon, in effect creating two separate versions of the content originally delivered to the CPE. Alternatively, the content received at the CPE/client 206 may simply be ephemerally stored or buffered (e.g., temporarily, while it is processed for upload), and then maintained only at the receiving network-side device, the ephemeral version being deleted. Under the first model, the user can advantageously access the local (CPE) version under most all circumstances, such as when no network connection is active. Likewise, the CPE 202 can act as a local content “server” of sorts for other clients or mobile devices in data communication with the receiving/storing CPE 202. However, the local content consumes significant storage space, and must then be managed with respect to reproduction, distribution, etc. Under the second “cloud based” model, user storage is obviated in favor of e.g., a streaming delivery, but this is obviously subject to network delivery/capabilities, and consumes downstream bandwidth within the network. Combinations or permutations of the foregoing are also envisaged, such as where a “local” copy is only accessible when the network or cloud copy is inaccessible, the network is experiencing downstream bandwidth constraints, a connected client at the CPE premises is requesting the content (and has no direct network access), etc.

In various implementations, the CPE 202 may be configured to automatically upload received content to a designated network storage device. Alternatively, SCM 210 on the server 208 may be configured to automatically initiate a content upload process (e.g., a content “pull”) for content that has been delivered to a CPE 202 or client device 206.

The uploaded content can be subsequently downloaded such as via VOD, unicast/multicast to eligible subscribers, as a binary image or file, or other mechanism. For example, a user can upload content to a 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 CPE or other desired platform, while preserving the digital rights associated with such content.

Network Upload and Storage—

In one embodiment, virtual storage devices 214 are maintained for subscribers of the aforementioned networks (or other designated users), thereby giving client devices storage space that they could not otherwise have using their existing equipment. This can be used for any number of different reasons, such as: (i) to archive or back-up data, (ii) to permit access to a data volume by multiple MSO subscribers, (iii) to maintain the security of the data (i.e., when no local copy is present at the subscriber's premises, theft of their computer from the premises is much less troubling), or (iv) to provide the subscriber with storage volume that they could otherwise not obtain. It is also envisioned that the network storage devices 214 within the system can be used as one potential model for preserving the copyright interests of content owners.

The server 208 of FIG. 2 may further comprise or be associated with a storage entity which acts as a network digital video recorder (nDVR) for the CPE 202. In one embodiment, the network DVR may be of the type discussed in co-owned, co-pending U.S. patent application Ser. No. 11/440,490 entitled “PERSONAL CONTENT SERVER APPARATUS AND METHODS” and filed on May 24, 2006, previously incorporated herein by reference in its entirety.

While illustrated generally as a plurality of substantially local components, the architecture of FIG. 2 can have one or more components (such as e.g., storage devices 212 or 214) disposed at a remote location. In one variant, either local storage device 212 or network storage device 214 may be co-located and co-managed by a content source (e.g., studio) or third party. In one variant, requests to access content are processed by the MSO but serviced by content from one or more third party databases (e.g., the databases of studios or other content source can collectively act as the MSO's “virtual library”). Such servicing of content requests can be effectively real-time, with any encoding, annotation, inclusion of metadata, etc. performed essentially on-the-fly (“just in time” processing) if desired.

It may be desirable under certain circumstances (e.g., for certain business models, in order to address security or legal/copyright issues, etc.) to provide the user with some degree of “ownership” or control of the MSO network facilities, whether on a short-term or long-term basis. As such, the user or subscriber may: (i) lease or even own equipment within the network operator's infrastructure or facilities; and/or (ii) extend a virtual control boundary around one or more components or portions of the network operator's equipment or infrastructure.

In one variant, the user or subscriber leases or purchases storage space and/or playback functionality from the MSO. Such lease or purchase may be for a period of time (or number of uses, etc.), or even permanent if desired. To this end, the MSO or other network operator may utilize a highly modular architecture, such that the operations of the leased space/equipment for respective subscribers are largely or completely separated from one another. The MSO maintains the leased/owned equipment (including physical security thereof), and operates the equipment at the behest of the owner. For example, the MSO would determine the configuration of the device, perform software upgrades, periodic maintenance, control encryption/decryption of the stored content, regulate access thereto, etc.

In another variant, a virtual control boundary is further constructed around the subscriber's leased or purchased equipment, thereby allowing them to be in direct control of all aspects of the operation and access of their equipment. For example, one embodiment employs a software application disposed at the client premises (e.g., on their CPE 202) which communicates with a corresponding application or portion at the MSO node (e.g., head-end 150) that controls the operation of the leased/purchased equipment. In this sense, the MSO's equipment is in a very real sense in the possession and under the control of the subscriber, albeit being physically located at a place remote from the subscriber's premises (e.g., the head-end of the cable network). In another variant, these storage and recording/playback apparatus are disposed at a local hub site or other node even more physically proximate to the user's premises.

In another embodiment, the virtual control boundary may be constructed around a group of subscribers or be determined pursuant to determinations made by the server content management process 210. While network storage space is allocated to individual subscribers, other subscribers or the network operator may be able to access, retrieve and/or upload content pursuant to various business models. For example, in response to a request for a content item from a first subscriber, the MSO may access/retrieve that content item stored on the network storage of the second subscriber. This may prove useful in situations where a local copy of the content item is not easily available to the headend or for the purposes of saving storage space when the same or similar content item (i.e., same title, same personalizations, same encoding etc.) exists on the network storage. Alternatively, the MSO may grant access to the first subscriber to access or download content stored on the second subscriber's network storage space. Granted access may be limited to specific content (i.e., the content item that was requested) or limited in duration.

In one variant, subscribers may be grouped according to common characteristics and allowed varying levels of access to other subscribers' network storage space within the same group. For example, subscribers could be grouped according to subscription type, geographic location, node location, or similarities in requested content. Subscribers belonging to the group may access/retrieve content that is stored on the network storage space of other group member's network storage space or network storage space that is specifically allocated for the group.

It will be appreciated that various business models may also be constructed around such “virtual possession” schemes, including for example where the user or subscriber can themselves specify or configure the equipment that they lease or own, much like one currently configures a PC or laptop from a manufacturer at time of purchase. A user can also be provided with the capability of changing or upgrading their equipment, such as for more storage space, different codecs, network interfaces, conditional access, encryption/authentication schemes, indigenous processing or signal conditioning capability, etc.

The network storage device 214 may store content and/or the operating system of the subscriber's CPE 202. In one variant, the CPE 202 operating system may reside entirely off-device, including at the MSO head-end or other such location if desired. Moreover, the data volumes for each subscriber may be encrypted, authenticated, and made physically secure, thereby providing a level of protection that exceeds that of the normal home PC, PMD, or the like.

The virtual storage device 214 can also be made part of a business paradigm; e.g., wherein the user pays a fee (such as on a per-Tb used) or subscribes for X terabytes of storage space for a given period of time.

In one embodiment, the virtual storage device 214 provides storage space for MSO subscribers to upload content to the server 208 or other network entity. The uploaded content can then be accessed, downloaded and/or streamed by a linked subscriber.

In one embodiment, the uploaded content comprises user-generated content. For example, using a cellular phone or tablet 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 client device or other desired platform (e.g., PC).

It will also be appreciated that uploaded (e.g., copyright-protected) content may be shared across multiple unrelated “eligible” users of the network. For example, suppose CPEs A, B, and C (each associated with different subscribers at different premises) all download content from the network, such as via respective VOD purchases. Under one implementation, the downloaded content is uploaded by each of the users (e.g., automatically, as described elsewhere herein) to a network storage location. The storage “location” may comprise a common storage area or server (e.g., all three users utilize the same storage), or three (separate) storage areas for each of the users. Hence, any number of logical and/or physical storage partitioning schemes may be utilized consistent with the present disclosure. In one paradigm, all three users in this example maintain separate, independent storage and access thereto. Alternatively, the users may employ a common storage/access approach, such as where each of the users can access a common copy of the content (assuming it is identical). This latter approach economizes on storage requirements in the cloud, since only one copy need be maintained (versus three) in this example. Moreover, upstream bandwidth requirements/latency can in some cases be reduced, since all three copies in the foregoing example need not be uploaded (assuming identical content), but rather only one. Hence, in one variant, the architecture 200 of FIG. 2 is configured such that it includes logic which identifies such commonalities (especially those occurring within a prescribed temporal window), and leverages them to obviate consumption of upstream bandwidth or undue latency for the users. For instance, where the CPE A, B and C of the prior example all request download of content element X within a few minutes of each other, the first downloading device (say, CPE B) initiates its upload first, and the remaining CPE A and C are in effect “waived off” by the network content management process 210 (or other entity) from having to upload their delivered content as well, such as via downstream in-band or OOB message or other signaling.

Likewise, a single cloud-based copy of the content can be logically “interlocked” between two or more users (such as by logic within the management process 210) such that if the content is being accessed by one eligible user, it cannot be accessed by another until the first has completed.

Moreover, where the demand for the content from the network-side storage element will not be immediate, upstream assets can further be optimized through “opportunistic” use of these assets; e.g., a “trickle” and/or “bursty” delivery upstream as time/resources permit. It is also envisaged that different portions of the content may be uploaded from different CPE, so as to in effect cobble together one complete version or copy from multiple sources.

Network Server and Content Management—

Referring now to FIG. 3, one embodiment of the improved network content server 208 adapted for content delivery and upload according to the disclosure is described. As shown in FIG. 3, the server 208 generally comprises a network server module adapted for interface with the networks of FIG. 2, digital processor(s) 304, RAM 306, a mass storage device 308, and a plurality of interfaces 307 for use with other network apparatus such as LANs, routers, and other packet network devices, network management and provisioning systems, local PCs, etc. Other components which may be utilized within the server include amplifiers, board level electronic components, as well as media processors and other specialized SoC or ASIC devices. Support for various processing layers and protocols (e.g., TCP/IP, 802.3, DHCP, SNMP, H.323/RTP/RTCP, VoIP, SIP, LSCP, etc.) may also be provided as required. Where the content server is also acting in a local network capacity (e.g., as a VOD or application server), an appropriate application is also disposed to run on the server to provide a functional interface for e.g., VOD session requests received from the client device or other interposed entities. These additional components and functionalities are well known to those of ordinary skill in the cable and embedded system fields, and accordingly not described further herein.

As previously discussed, the server 208 also may run the server content management process 210 (SCM). The SCM 210 may be integrated into the server portion of a distributed application process, or alternatively comprise a discrete or stand-alone module having inter-process communication with the server portions (or portions where multiple content servers and server portions are used in conjunction with the SCM 210).

In one variant, the SCM 210 may determine whether the content was previously requested and/or stored on the subscriber's CPE 202 attached to the local (cable) network. This information is gathered by either querying the CPE 202, or by querying a process at the head-end for the program titles stored by or on the CPE 202. In one embodiment, in response to a determination that content has been stored or partially stored on a CPE 202, the SCM 210 may initiate an upload process.

The SCM 210 may also be configured to facilitate reception of uploaded content to the server 208 or other designated host/storage entity. In one variant, uploaded content is received at the network storage device 214 previously described herein. Uploaded content may be stored and organized for example according to metadata associated with the content, or other approach. Metadata information may for instance include description of the content (e.g., title, genre, subject, file type) or details about the data (e.g., size, last updated, source).

In other variants, uploaded content is stored and organized according to predefined rules set by content owners, network operators, users, or a combination thereof. For example, it may be useful for the MSO to index the stored content according to one scheme or rule set (e.g., that minimizes access time, required storage volume, or addresses other parameters), while the user may obtain the best user experience or ease of use through a different organizational scheme. Additionally, content may be stored and organized according to a CPE identifier and/or user identifier that the SCM 210 can cross-reference and use to direct the storage of data. The SCM process 210 may also include options for the configuration of the display and storage of the uploaded content.

The server device 208 of FIG. 4 may take any number of physical forms, comprising for example one of a plurality of discrete modules or cards within a larger network head-end or edge device of the type well known in the art. The server may also comprise firmware, either alone or in combination with other hardware/software components such as those previously described (e.g., disposed in the aforementioned edge device). Alternatively, the server module 208 may be a stand-alone device disposed at the head end or other location (such as a VOD server 105 or application server 104), and may even include its own RF front end (e.g., modulators, encryptors, etc.) or optical interface so as to interface directly with various portions of the HFC network 101 if desired. Numerous other configurations may be used with any configuration or combination of hardware, firmware, or software, and may be disposed within one or any number of different physical or logical entities.

CPE Architecture and Operation—

FIG. 4 illustrates a first exemplary embodiment of the improved CPE 202 with content selection, download, and upload capability.

In the case of HFC or satellite networks, the CPE 202 in one embodiment comprises a client device 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 CPE 202 may or may not include DVR/PVR functionality. Also, the CPE 202 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. It will be recognized by those of ordinary skill that myriad different device and software architectures may be used consistent with the content selection, download, and upload functionality, the device of FIG. 4 being merely exemplary.

As shown in FIG. 4, the CPE 202 generally comprises an OpenCable-compliant embedded system (e.g., DSTB) having an RF front end 402 (including tuner and demodulator/decryptors) for interface with the HFC network, digital processor(s) 404, mass storage device 406, and a plurality of interfaces 408 (e.g., video/audio interfaces, IEEE-1394 “FireWire”, USB, serial/parallel ports, ThunderBolt, Ethernet, MoCA, etc.) for interface with other end-user apparatus such as televisions, personal electronics, computers, Wi-Fi or other network hubs/routers, etc. Although various protocol are illustrated in FIG. 4, it is appreciated that the CPE 202 of the present disclosure may be configured to communicate over any current and future wireline protocols. Other components which may be utilized within the device (deleted from FIG. 4 for simplicity) various processing layers (e.g., DOCSIS MAC or DAVIC OOB channel, MPEG, etc.) as well as media processors and other specialized SoC or ASIC devices. The CPE 202 may also comprise an integrated HD decoder, thereby relieving any connected monitors or other devices from the requirement of having such a decoder. These additional components and functionality are well known to those of ordinary skill in the cable and embedded system fields, and accordingly not described further herein.

The CPE 202 of FIG. 4 is also provided with an OCAP-compliant application and Java-based middleware which, inter glia, manages the operation of the device and applications running thereon. Different device and software architectures may be used consistent with the tuning and channel request functions, for example, different middlewares (e.g., MHP, ARIB, or ACAP) may be used in place of the OCAP middleware of the illustrated embodiment.

As part of the application layer of the CPE 202 protocol stack (not shown), various different types of client applications may be operational. In one embodiment, a separate (dedicated) client application adapted for content selection, browsing, download, and upload may be used to interface with the lower layers of the stack. This may include, e.g., a separate GUI or other type of UI, and may operate substantially independent of other applications on the CPE 106. Alternatively, the selection, download, and upload functionality described herein may be integrated into one or more existing or downloadable applications (such as a VOD application, “Watch TV” application, navigator, TV-commerce application, or even EPG). The application (and even session) layer protocols necessary to control the content selection, download, and upload functionality may even be disposed on another device (e.g., PDA or cellular smartphone) as previously described in order to instigate the browsing, selection, purchase, download/streaming, and upload of content.

In another embodiment, the client application can function in response to signals or communications provided by a device in communication with the CPE 202. For example, the CPE 202 may comprise a wireless interface (e.g., 802.11 a/b/g/n, Bluetooth, 802.15 PAN, 802.16 WiMAX, 802.20, etc.) such that it can service content selection, payment, download/streaming, and upload requests from client devices of the CPE 202 itself. In one such variant, the client device comprises a tablet, smartphone, PDA, gaming console, or similar handheld device that has a distributed portion of the client application running thereon. This application may be stand-alone or integrated with another application. Hence, users operating the distributed client application on the tablet/smartphone/PDA will utilize their wireless interface to the CPE 202 in order to remotely instigate a content download or upload from the network via the CPE, the latter in effect acting as a gateway to the content distribution network. The wireless forward channel(s) of the interface (e.g., CPE to PDA) can be used to transmit the content after processing (e.g., decoding) by the CPE, or even stream the “raw” unprocessed content (or even the received and demultiplexed MPEG encoded packets) to other client devices and/or network storage.

The exemplary client device 202 further comprises a personal content or media application, which allows a user to manage his/her 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 upload of content. 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 client device 202 to check on the content titles stored on the client device 202 (when a local storage model is used), and upload data related thereto.

In one implementation, the client program resident on the CPE 202 tracks and reports user activity related to personal content viewing to the relevant server(s) for each client device. This activity tracking is useful from a number of perspectives, including: (i) determining when content is stored or uploaded to a network storage device; (ii) determining when programs are added or deleted from the local storage (e.g., subscriber's DVR); and (iii) for billing purposes. 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 co-owned, co-pending U.S. patent application Ser. No. 11/186,452 filed on Jul. 20, 2005 and entitled “METHOD AND APPARATUS FOR BOUNDARY-BASED NETWORK OPERATION”, which is incorporated herein by reference in its entirety. Such mechanisms allow for specific identification of the CPE 202 which has recorded or accessed content, without necessarily having to know the subscriber's identity.

Furthermore, an application on the CPE 202 can be made to be responsive to the user's commands to control the DVR from the remote or visited network. 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 CPE 202 and the remote client device 206 (e.g., via Internet), relayed communications that pass through the MSO (local) infrastructure and so forth. Allowing the subscriber to set up such a connection provides a remote management interface to managing the CPE 202 to perform personal media related functions, among others, thereby adding significant flexibility to the operation and utilization of the remote content access functionality.

As previously discussed, content can be uploaded to the MSO or third party network storage device, and subsequently downloaded/streamed and viewed 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 remote client device 206. Content may be uploaded on an upstream channel of the cable network, or through another network such as through a cell network (e.g., LTE/LTE-A) or 802.16 wireless, or via a broadband Internet connection (such as e.g., optical fiber, wireless, or other mechanism.

In one embodiment, the upload functionality may be automatic or otherwise completely transparent to the end user, such as where an application running on the CPE 202 (or an associated device) (i) initiates a session if not already established, (ii) uploads the data, including any necessary error correction and/or retransmission, and (iii) manages termination of the session. The upload may comprise any form of transmission, such as binary image, streamed, one or more files, etc.

Individualized Content Channel Variants

In one aspect, the foregoing techniques of local receipt (and optional storage) and upload back to the network or other entity may be combined with personalized virtual or other content channel approaches to, inter alia, leverage data relating to user behavior on a per-user basis. See for example co-owned and co-pending U.S. patent application Ser. No. 12/414,554 filed Mar. 30, 2009 entitled “PERSONAL MEDIA CHANNEL APPARATUS AND METHODS” which is incorporated herein by reference in its entirety, which discloses among other things, methods and apparatus for “fused” targeted content delivery in a content-based network. Specifically, a substantially user-friendly mechanism for viewing content compiled from various sources is provided, including, inter alia, DVR, broadcast, VOD, Start Over, etc. Content selected to align with a user's preferences is displayed as a substantially continuous stream as part of a “virtual” user-based channel. In one embodiment, a user profile is constructed and targeted content gathered without requiring any user intervention whatsoever; e.g., based on a user's past or contemporaneous interactions with respect to particular types of content. This information can be generated by, for example, a recommendation “engine” such as that described in co-owned and co-pending U.S. patent application Ser. No. 12/414,576 filed Mar. 30, 2009 entitled “RECOMMENDATION ENGINE APPARATUS AND METHODS” which is also incorporated herein by reference in its entirety. The “virtual channel” acts as a centralized interface for the user and their content selections and preferences, as if the content relevant to a given user were in fact streamed over one program channel. The compiled content may also presented to the user in the form of a “playlist” from which a user may select desired content for viewing and/or recording. The user is able to navigate between on-demand content, the virtual channel, an EPG, a search tool, and a DVR navigation tool from a single user interface (e.g., on-screen display).

In another aspect, client applications (e.g., those disposed on a subscriber's CPE and/or network servers) are utilized to compile the playlist based on user-imputed as well as pre-programmed user profiles. Various feedback mechanisms may also be utilized to enable the client application to “learn” from the user's activities in order to update the user profile and generate more finely-tuned and cogent recommendations. Client applications may also be utilized to manage the seamless presentation of content on the virtual channel, and locate/flag various scenes inside selected content for user viewing or editing.

Hence, in one variant, logic is included within the CPE and/or network content management entity (e.g., SCM 210) such that the items which are selected to populate the user's virtual channel are selectively downloaded (and then uploaded back to the network for storage), so as to populate the storage entity of the network associated with that user with content that has been particularly selected for that user/premises. When a user selects something outside of the recommended content, the logic is configured in one embodiment to cause download and upload of that content onto the storage entity, so as to update the storage on a rolling basis.

Method of Uploading—

FIG. 5 shows one exemplary embodiment of the generalized method of delivering, uploading, and storing content over a network as described. It will be appreciated that while the following embodiment is described primarily in terms of an on-demand (OD) “session” based model delivering content over an in-band channel, the system is equally adapted to non-OD models such as broadcast/multicast (described in detail subsequently herein), data/content download via a cable modem (e.g., IP transport modality), out-of-band (OOB) communications channel, etc., the VOD exemplar being merely illustrative of the broader principles of the disclosure.

In a first step 502 of the method 500, a CPE 202 is configured. In one embodiment, the server content management process 210 configures the CPE 202 to operate in a determined fashion. Alternatively, the client content management process 204 configures the CPE 202 to operate in a determined fashion. In one variant, the CPE 202 is configured to designate a server 208 and/or network storage device 214 for the reception of uploaded content. The CPE may also merely upload the content “blindly” to a designated network address (e.g., cache or buffer), which is then processed by a head-end or other entity in order to properly record the content in a fashion accessible by the user.

In another variant, the CPE 202 may be configured to automatically upload content at a predetermined time. In yet another variant, the CPE 202 may be configured to automatically upload content upon the occurrence of an event (e.g., expiration of a timer, receipt of a message from the network, sufficient bandwidth availability, etc.). In still yet another variant, the CPE 202 may be configured to automatically upload in response to a user upload command. Various techniques for the configuration of the CPE 202 will be discussed further herein.

In step 504 of the method 500, the desired content is made available, and purchased or requested by a user (e.g., MSO subscriber). The request for the content may be instigated from the CPE 202 or a client device 206, or may be as a result of interaction with a third party (e.g., content source) web server, operator or other such network agent.

In one embodiment, a user is provided with a listing of available content, comprising e.g., one or more entries corresponding to different content titles, encoding formats, features, purchase options, and so forth, via a user interface. For example, one variant utilizes an on-screen display or GUI, generally similar to the well-known electronic programming guide (EPG), that lists the various choices available for purchase. These might be indexed by category (e.g., feature length movie, gaming application, video “shorts”, music, etc.), and sub-indexed by genre (e.g., comedy, drama, etc.), alphabetically by title or primary actors, etc. Alternatively, a user might simply be presented with a short GUI menu or pop-up display mechanism (e.g., window) listing new releases for that week or month. The user interface can be invoked in response to a user request, such as for example by selecting a button on the user's remote that interacts with their CPE 202, at a pre-designated periodicity (e.g., once per week), upon the occurrence of a particular event (e.g., new release), or at the instigation of the MSO, although myriad other approaches will be recognized by those of ordinary skill.

It will be appreciated that such user interface is not limited to the MSO network domain either. For example, as described in greater detail subsequently herein, the user interface may comprise part of a PMD or mobile device (e.g., PDA or smartphone), which can access the MSO virtual database manager from a remote location or network.

Once the user makes their selection(s), this information is transferred to the server content management process 210 via an upstream communication channel, DOCSIS modem, ISP connection, or other modality appropriate to the user's situation. The user's selection (e.g., availability) and payment information are then validated, such as by accessing a subscriber database associated with that user (as determined by, e.g., TUNER ID, MAC, or other information uniquely identifying the requesting CPE/subscriber.

Menus or other user interfaces may also be generated for receiving user preferences (e.g., format, particular versions of the same content, codec selection, upload configuration etc.). This information can be transmitted to the head-end at time of selection, or alternatively pre-stored in a configuration file disposed in the head-end or other location directly accessible to SCM 210).

Next, per step 506, the purchased/requested content is delivered to a storage facility at the headend 150 (if not already there), such as a local storage device 212 shown in FIG. 2. In one embodiment, the user's content selections and preferences, which may be received either at time of purchase or pre-stored, are received by the SCM 210.

Selected content is optionally encoded or recoded as required (e.g., such as where the content requires encoding into the format requested by the user). The content can alternatively be coded “on the fly”, such as immediately preceding streaming over a VOD session.

Note that storage need not necessarily occur at this stage of the method 500 (or at all); rather, in another variant the SCM 210 merely identifies and validates the subscriber and permits access to content that has already been stored or that is available for streaming.

In one embodiment, the system provides a storage optimization algorithm rendered as a computer program running within the architecture (i.e., either at the head-end, the client device, or as a distributed application as described elsewhere). The optimization algorithm may be structured to store content in a more space-efficient and operationally efficient mariner. In one variant, the storage optimization determines whether a content item has already been uploaded/stored to the head-end. If the content item has already been uploaded once, the content optimization algorithm may prevent or delete duplicate copies from being stored or uploaded at the head-end. The algorithm may operate with respect to the network storage space associated with an individual user, or alternatively to the network storage space of multiple users or even the local storage of the head-end or network storage as a whole. To that end, the MSO head-end saves space by building a database or library of content that has been uploaded in network storage space by subscribers and using that database as a source for future requests of content. If there is a request for a content item that has been already uploaded but requires different personalizations or encodings, the SCM 210 may access the content item stored in the network storage device 214 and apply the differences before delivering the content item to the requesting device. The requesting device may or may not be required to be grouped or linked with the subscriber account associated with the uploaded content.

In step 508, the content is delivered to the target device (e.g., customer CPE 202 or client device 206) via a communication channel. The content is transmitted to the requesting CPE or client device, such as via a session between the content server and the CPE (e.g. VOD) that transmits the content over one or more in-band downstream QAMs. Alternatively, delivery may occur via a broadcast (e.g., BSA) mode, an IPTV (e.g., MPEG over IP) mode, via satellite link, or any other mode having suitable bandwidth and quality of service (QoS).

Delivery may also occur to remote or visited networks; e.g., to client devices that are outside the MSO or “local” delivery network. Co-owned and co-pending U.S. patent application Ser. No. 11/440,490 filed May 24, 2006 entitled “PERSONAL CONTENT SERVER APPARATUS AND METHODS”, previously incorporated herein by reference in its entirety, discloses exemplary apparatus and methods for delivery of content to remote client devices and networks, although it will be recognized that other apparatus and techniques may be used for this purpose. Accordingly, it will be appreciated that the methodology of FIG. 5 advantageously is substantially agnostic to the bearer medium, and amenable to redirection (i.e., requesting, customizing, receiving, and uploading the content can all be conducted at different locations or using different platforms).

In other variants, a user session based on the Session Initiation Protocol (SIP) is used for delivery, whether with the same or another bearer medium such as a non-VOD approach, or a WAP Wireless Session Protocol (WSP) session disposed on a handheld device, and so forth. It is noted that in such SIP or WAP variants, the initiating device need not necessarily be the target device (e.g., DSTB) to which the content is streamed. Rather, the SIP or WAP-enabled device can act as a session proxy for the DSTB or other target CPE, such as where the user utilizes their SIP-enabled PDA to communicate with a head-end or other content-providing network entity to establish the download session.

The aforementioned VOD or other session (or user-specific broadcast in the BSA variant) may be initiated promptly, e.g., automatically upon authorization of the transaction, or alternatively at another time selected by either the MSO or the user (such as, e.g., at a pre-determined day or date when the content is to be released). Similarly, if the target CPE (e.g., DSTB) has multiple RF tuners and one is available, data/content streaming or download can be initiated immediately, or as soon as a tuner becomes available when all are initially in use. Likewise, if the CPE has a single tuner, the data/content streaming or download is initiated when that single tuner is free.

The foregoing transmission or delivery logic can also be masked with other requirements if desired, such as where both a free tuner and the permitted viewing start time falling within a prescribed temporal window are required (i.e., viewing or access is valid only for a certain “aging” period), or where the user acknowledges a splash screen or comparable mechanism acknowledging the copyright of the content to be viewed (akin to a physical DVD, where the user's DVD player controls are ineffective during the copyright notice portions), and the restrictions on its use. Masking may also be based on network status or bandwidth availability, such as where the session will not be instantiated until sufficient bandwidth is available to provide a sufficiently high assurance of completing the streaming or download (and/or upload).

Upon receipt, the target device either conducts playback of the content, such as the playing of an MPEG-2 stream, or alternatively the playback of a compressed video file downloaded at high speed, or even the installation and execution of an application. In response to the receipt of content, a notification may be sent upstream that includes recording information about the content item.

It will be appreciated that the delivery of the content may occur immediately, e.g., immediately after or even contemporaneous with storage (if used) or buffering, and/or may occur at a subsequent time or date, depending on the purchaser's preferences.

In step 510, the CPE 202 or client device 206 uploads the received content to a designated network host. The designated network host may be a server 208 in the headend 150, or network storage space not located and/or directly associated with the MSO server. In one variant, the server 208 receives the uploaded content and redirects the content to its associated network storage space 214. Content may be uploaded on an upstream channel of the cable network or through a remote network as previously described. In one variant, content may be uploaded by transferring the content to a connected user device and using the connected user device to upload the content. For example, a CPE 202 may, in response to a user request, transfer content (e.g., via a premises network connection, USB connection, etc.) to a client device which is configured to upload the content contemporaneously with or as an alternative to the upload function of the CPE 202. The request may come from a user of the CPE 202 or a remote client device. In one variant, only a portion of the whole program content is transferred to the connected user device.

In one variant, the content is transferred to a second premises device and uploaded to the network storage from there, in response to a determination that insufficient upload bandwidth or tuner availability at a first premises device will frustrate upload of content to the head-end. For instance, the received content may be transferred via wired or wireless interface to the upload session will not be instantiated until sufficient bandwidth is available to provide a sufficiently high assurance of completing the upload. Alternatively, content is transferred upon determination that another premises device will upload data more efficiently.

In one embodiment, the system provides an upload prioritization algorithm rendered as a computer program running within the architecture (i.e., either at the head-end, the client device, or as a distributed application as described elsewhere). The upload prioritization algorithm contains an upload queue and may schedule and/or rank multiple upload events. In one variant, content items may be cross referenced with a database stored within the system 200 or contain metadata that indicates the importance that a particular item is uploaded. The upload prioritization algorithm interprets the upload priority information and schedules upload events accordingly. For example, Content Item A has an upload priority of 10, Content Item B has an upload priority of 5, and Content Item C has an upload priority of 1. Upon receiving and interpreting this data, the upload prioritization algorithm schedules Content Item A for immediate upload, Content Item B for upload next week, and Content Item C for upload not necessary or only upon user request. As such, the system is able to adapt to varying requirements for digital rights as set by content owners or the MSO while preserving upload bandwidth for items where upload may not be necessary.

In another embodiment, the CPE 202 is configured to upload content periodically. After a predetermined period of time, the CPE 202 determines if any new or updated content has been stored and uploads the new or updated content. Content may be considered new or updated if all or a portion of the files associated with the stored content have changed since the last upload occurred. The CPE 202 may maintain a list or database of content items that have been stored or are scheduled to be stored. In one variant, the database includes information about the stop and start times of download, upload and record events. Alternatively, the CPE 202 may indicate changes to content and the start and stop times of download, upload, and record events in the metadata associated with the content. As an illustrated example, a CPE 202 may be configured to upload content every Monday at 12:00 PM. The CPE 202 scans its records for new content on Monday at 12:00 PM, finds content item A was stored the previous Saturday, adds item A to an automatic upload queue and indicates the appropriate changes in a database and/or metadata.

In one embodiment, the CPE 202 is configured to automatically upload content upon reception of the content. In one variant, the CPE 202 is configured to automatically upload content once it has been received and/or after a predetermined time occurs/lapses after reception. Content may be considered received when reception of the content begins, when storage of the content has been completed, or at a time in between those two stages (i.e., a predetermined percentage of content has been downloaded and stored). In one variant, the CPE 202 parses the content in a memory buffer so that portions of the content may be uploaded to the network before the entirety of the content item has been received at the CPE 202.

In one embodiment, a flag or marker may be stored and/or transmitted by the client content management process 204 on the CPE 202 to indicate reception of content. The flag may identify a content item to an internal or external process as new content that has been received. Alternatively, the flag may indicate that a search or query should be performed by an internal or external process to identify new content on the CPE 202. The head-end or CPE may initiate an upload in response to receiving the flag.

In one embodiment, the CPE 202 is configured to automatically upload content in response to an event. In one instance, content upload is performed after a predetermined number of content items have been received at the CPE 202. Alternatively, content upload is performed when the server 208 has delivered a predetermined number of content items. In another variant, content upload my performed when storage space on the CPE 202 hard drive has exceeded a predetermined capacity.

In one embodiment, the determination of new content is performed by the server content management process 210 at the headend. When content is delivered to the subscriber, the SCM 210 updates a database that tracks the reception of content by the CPE 202. The database may be stored at the CPE 202, the headend 150, or network storage devices located offsite. In response to a lapsed period of time, event, or request, the SCM 210 accesses the database to determine if the CPE 202 has received content that has not yet been uploaded and if so, sends a command to the CPE 202 to initiate an upload of the new content. Alternatively, the server content management process 210 may query files stored on the CPE 202 to determine if new content exists.

In one embodiment, individual storage space is allocated for each CPE 202. The allocated storage space may be expanded or reduced based on various business considerations and/or the subscription agreement between the operator and user. Content that is uploaded is stored at the head-end or network storage device 214 and then made available for subsequent access. Additionally, the content may be encrypted before being uploaded to the head-end.

In one embodiment, when a plurality of users have requested, downloaded or uploaded the same content item(s), the storage optimization algorithm discussed above may store fewer or a single instance of the content item at the network storage device to prevent or reduce multiple copies of the same content item. The storage optimization algorithm may dynamically adjust the number of content item(s) stored in the network according to the popularity of the item or according to a time that has been determined to be a time of high demand for at item or similar content items.

In another embodiment, the storage optimization algorithm determines whether a content item has already been uploaded by that user. If not, an upload is scheduled for content that has not yet been uploaded. If the content has already been uploaded, the storage optimization algorithm may remove the content from the local storage of the CPE 202 since the subscriber will be able to access and receive the content at a subsequent time from the network storage. In one variant, the SCM 210 or CCM 204 prompts the user with options for deleting local content that has already been uploaded. In another variant, a pre-stored configuration file stored on the CPE 220 or at the head-end is used to determine rules for removing duplicate copies of content. For example, the CPE 202 may be configured to prompt the user for duplicate removal only when the capacity of the CPE 202 hard disk space has exceeded a predetermined threshold. In yet another variant, removal or prompting for removal only occurs after a determination that both the content has already been uploaded and the content has been viewed at least once by the user.

An upload may be cancelled if the recording or storage of the content at the CPE 202 is interrupted or fails to complete. In one variant, the CPE 202 may automatically send a notification upstream to the head-end if the content item is not completely received. Alternatively, the head-end may determine that a recording is incomplete when it compares metadata (e.g., start/stop times of the recording, size, etc.) with data values known to be consistent with a complete recording of that particular content item.

It will be recognized that while certain aspects herein are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of a broader method 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 system disclosed and claimed herein.

While the above detailed description has shown, described, and pointed out novel features 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. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles. The scope should be determined with reference to the claims.

Claims

1. Computer readable apparatus comprising a non-transitory storage medium, the non-transitory storage medium comprising at least one computer program having a plurality of instructions, the plurality of instructions configured to, when executed on a digital processing apparatus: enable at least a first computerized client device and a second computerized client device to upload one or more digital content elements to a computerized storage apparatus;receive first data representative of a first request for upload of a first digital content element from the first computerized client device;based at least on the received first data, cause the upload of the first digital content element from the first computerized client device;receive second data representative of a second request for upload of a second digital content element from the second computerized client device;utilize the second digital content element to identify at least a portion thereof that is a duplicate of at least a portion of the first digital content element, the identification comprising: access of data stored at a computerized network entity, the stored data related to prior activity associated with at least one of the first digital content element or the second digital content element; anddetermination, based at least on the accessed data, that the prior activity has occurred within a prescribed period of time prior to the determination;based at least on the identification, assign a priority level for the upload of the second digital content element from the second computerized client device, the priority level being lower than a priority level for the upload of the first digital content element; andbased at least on (i) the identification, and (ii) the assigned priority level of the upload of the second digital content element, prevent upload of the at least portion of the second digital content element that is duplicative of the at least portion of the first digital content element from the second computerized client device.
2. The computer readable apparatus of claim 1, wherein the plurality of instructions are further configured to, when executed on the digital processing apparatus: based at least on the receipt of the second data representative of the second request, cause a second upload of a portion of the second digital content element from the second computerized client device, the portion of the second digital content element of the second upload being different than any portion of the first digital content element.
3. The computer readable apparatus of claim 1, wherein: the computerized storage apparatus comprises a network-based mass storage apparatus used to store data accessible to a plurality of different subscribers of a managed content delivery network utilizing the mass storage apparatus; andthe first computerized client device and the second computerized client device are each allocated a respective user-specific or device-specific storage location within the mass storage apparatus so as to maintain at least one of security or copyright protection over digital content stored in the respective user-specific or device-specific storage locations.
4. The computer readable apparatus of claim 1, wherein the first computerized client device and the second computerized client device each are configured to assert a respective virtual control boundary over at least respective user-specific or device-specific storage locations of the computerized storage apparatus, the respective virtual control boundaries each enforced via one or more software applications configured to be run from at least one of: (i) the respective first or second computerized client device, or (ii) the computerized storage apparatus.
5. The computer readable apparatus of claim 1, wherein: the computerized storage apparatus comprises a network-based mass storage apparatus used to store data accessible to a plurality of different subscribers of a managed content delivery network utilizing the mass storage apparatus;the first computerized client device and the second computerized client device are each allocated a respective user-specific or device-specific storage location within the network-based mass storage apparatus; andat least one of the first computerized client device or the second computerized client device is configured to assert a virtual control boundary over at least (i) a respective user-specific or device-specific storage location of the computerized storage apparatus of the at least one computerized client device, and (ii) a respective user-specific or device-specific storage location of the computerized storage apparatus of another of the first or the second computerized client device.
6. The computer readable apparatus of claim 5, wherein an ability of the at least one of the first computerized client device or the second computerized client device to assert the virtual control boundary over at least (i) the respective user-specific or device-specific storage location of the computerized storage apparatus of the at least one computerized client device, and (ii) the respective user-specific or device-specific storage location of the computerized storage apparatus of the another of the first or the second computerized client device, enables the computerized storage apparatus to conserve storage space as compared to operation thereof without the virtual control boundary; wherein the conservation of the storage space is based at least in part on an ability of the computerized storage apparatus to store at least portions of the first or the second digital content element which are accessible to both the first and the second computerized client devices, thereby obviating duplication of storage of the at least portions, based at least on the asserted virtual control boundary.
7. The computer readable apparatus of claim 1, wherein the data stored at the computerized network entity comprises data representative of prior viewing activity at the first computerized client device or the second computerized client device, the prior viewing activity associated with the at least one of the first digital content element or the second digital content element.
8. The computer readable apparatus of claim 7, wherein the data representative of the prior viewing activity is (i) tracked via instances of a client application program configured to run on respective ones of the first and the second computerized client devices, and (ii) uploaded to the computerized network entity.
9. A computerized method of content management within a content delivery network in data communication with a plurality of computerized client devices, a first of the computerized client devices and a second of the computerized client devices being enabled for upload of a plurality of digital content elements to a computerized network storage apparatus, the computerized network storage apparatus in data communication with the first computerized client device and the second computerized client device via the content delivery network, the computerized method comprising: receiving first data indicative of a first request for upload of a first digital content element to the computerized network storage apparatus from the first computerized client device;receiving second data indicative of a second request for upload of a second digital content element to the computerized network storage apparatus from the second computerized client device, the second digital content element comprising at least a portion that is duplicative of a corresponding portion of the first digital content element;evaluating at least portions of the first digital content element and the second digital content element with respect to one or more criteria, the evaluating comprising: accessing a database disposed at a computerized entity within the content delivery network, the database configured to maintain data related to stop and start times of at least one instance, prior to the accessing, of: (i) downloading, (ii) recording, or (iii) uploading, of at least one of (a) the corresponding portion of the first digital content element, or (b) the at least portion of the second digital content element; andutilizing the data related to the stop and the start times to determine whether the at least one instance of the downloading, the recording, or the uploading has been performed within a prescribed temporal limit;determining an upload classification of each of the first digital content element and the second digital content element based at least on the evaluating; andcausing an upload of at least one portion of at least one of the first digital content element or the second digital content element based at least on the determining, and not the at least portion of the second digital content element that is duplicative of the corresponding portion of the first digital content element.
10. The computerized method of claim 9, wherein the determining of the upload classification comprises utilizing at least the determination of the performance within the prescribed temporal limit to classify each of the first digital content element and the second digital content element as either requiring upload or not.
11. The computerized method of claim 9, wherein the accessing of the database comprises accessing the data related to the stop and the start times, the data related to the stop and the start times tracked via client application computer programs each configured to run on respective ones of the plurality of computerized client devices.
12. The computerized method of claim 9, wherein the determining of the upload classification comprises: identifying metadata stored in association with each of the first digital content element and the second digital content element, the metadata comprising data related to the stop and the start times; andassigning a metric relating to a relative priority classification based at least on the identified metadata.
13. The computerized method of claim 9, wherein the evaluating comprises: (i) determining a bandwidth requirement for upload of the at least portions of the first digital content element and the second digital content element; and(ii) comparing the determined bandwidth requirement with a criterion relating to available upstream bandwidth within the content delivery network; andwherein the determining of the upload classification comprises using results of the comparing to determine said upload classification.
14. The computerized method of claim 9, wherein the causing of the upload of the at least one portion of the at least one of the first digital content element or the second digital content element comprises at least one of: (i) preventing upload of another portion of the at least one of the first digital content element or the second digital content element until a sufficient level of bandwidth availability is detected; or(ii) preventing the upload of the another portion of the at least one of the first digital content element or the second digital content element until receiving data representative of a subsequent request for the upload of the another portion of the at least one of the first digital content element or the second digital content element.
15. Computer readable apparatus comprising a non-transitory storage medium, the non-transitory storage medium comprising at least one computer program having a plurality of instructions, the plurality of instructions configured to, when executed on a processing apparatus of a computerized network entity, cause said computerized network entity to: receive first data relating to a first request for upload of a first digital content element from a first computerized client device of a plurality of computerized client devices;receive second data relating to a second request for upload of a second digital content element from a second computerized client device of said plurality of computerized client devices, said second digital content element comprising digital content which is duplicative of digital content of said first digital content element;based at least on said first request and said second request, determine an upload priority for said first digital content element, the determination of the upload priority comprising: identification of metadata stored in association with each of the first digital content element and the second digital content element, the metadata comprising data related to stop and start times of at least one instance of downloading or uploading, of at least one of (a) digital content of the first digital content element, or (b) digital content of the second digital content element; andassignment of a metric relating to a relative priority classification based at least on the identified metadata;based at least on said upload priority, cause a first upload of at least a portion of said first digital content element to at least one computerized network storage entity from said first computerized client device; andprevent upload of said digital content of said second digital content element which is duplicative of said digital content of said first digital content element from said second computerized client device.
16. The computer readable apparatus of claim 15, wherein said plurality of computerized client devices each are configured to assert a virtual control boundary around at least a portion of a storage location of said at least one computerized network storage entity.
17. The computer readable apparatus of claim 15, wherein said plurality of instructions are further configured to, when executed, cause said computerized network entity to: receive data relating to at least one subsequent request for said first digital content element from a third computerized client device;determine whether at least one of: (i) a different personalization, or (ii) a different encoding, is required for said third computerized client device; andbased at least on said determination, cause a provision of at least one of differently personalized variant or differently encoded variant of said first digital content element to said third computerized client device.
18. The computer readable apparatus of claim 15, wherein said plurality of instructions are further configured to, when executed, cause said computerized network entity to: provide said second computerized client device with data relating to a plurality of options for removal of said duplicative digital content of said second digital content element from a local storage device of or in data communication with said second computerized client device.
19. The computer readable apparatus of claim 15, wherein said at least one computerized network storage entity comprises one or more device-specific or user-specific storage locations allocated to each of said first computerized client device and said second computerized client device, said first upload comprising an upload to at least one of the one or more device-specific or user-specific storage locations allocated to said first computerized client device.
20. The computer readable apparatus of claim 15, wherein said plurality of instructions are further configured to, when executed, cause said computerized network entity to: communicate with a database where the metadata is stored; andutilize the metadata to determine whether the at least one instance of the downloading or the uploading, of the at least one of (a) the digital content of the first digital content element, or (b) the digital content of the second digital content element, has been performed within a prescribed temporal limit;wherein the assignment of the metric relating to the relative priority classification based at least on the identified metadata comprises utilization of at least the determination of the performance within the prescribed time limit to classify each of the first digital content element and the second digital content element as requiring upload or not.

PRIORITY AND RELATED APPLICATIONS

This application is a divisional of, and claims priority to, co-owned and co-pending U.S. patent application Ser. No. 13/797,577 of the same title and filed on Mar. 12, 2013, which is incorporated herein by reference in its entirety. This application is related to commonly owned U.S. patent application Ser. No. 11/440,490 filed May 24, 2006 and entitled “PERSONAL CONTENT SERVER APPARATUS AND METHODS”, and U.S. patent application Ser. No. 11/811,953 filed Jun. 11, 2007 entitled “METHODS AND APPARATUS FOR PROVIDING VIRTUAL CONTENT OVER A NETWORK”, each of the foregoing incorporated herein by reference in its entirety.

US Referenced Citations (1228)

Number	Name	Date	Kind
3388376	Magee	Jun 1968	A
4355415	George et al.	Oct 1982	A
4384610	Cook et al.	May 1983	A
4534056	Feilchenfeld et al.	Aug 1985	A
4546382	McKenna et al.	Oct 1985	A
4577177	Marubashi	Mar 1986	A
4602279	Freeman	Jul 1986	A
4694490	Harvey et al.	Sep 1987	A
4696578	Mansuria et al.	Sep 1987	A
4708224	Schrooder	Nov 1987	A
4749062	Tsuji et al.	Jun 1988	A
4902732	Itoh et al.	Feb 1990	A
4905080	Watanabe et al.	Feb 1990	A
4908707	Kinghorn	Mar 1990	A
4930120	Baxter et al.	May 1990	A
4930158	Vogel	May 1990	A
4959720	Duffield et al.	Sep 1990	A
4975909	Masson et al.	Dec 1990	A
4977455	Young	Dec 1990	A
4979593	Watanabe et al.	Dec 1990	A
4995479	Fujiwara et al.	Feb 1991	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
5369707	Follendore, III	Nov 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
5577209	Boyle et al.	Nov 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
5715403	Stefik	Feb 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 et al.	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
5828832	Holden 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
5870474	Wasilewski et al.	Feb 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
5982412	Nulty	Nov 1999	A
5984051	Morgan et al.	Nov 1999	A
5987506	Carter et al.	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 et al.	Dec 1999	A
6009098	Asamizuya	Dec 1999	A
6009103	Woundy	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
6134532	Lazarus et al.	Oct 2000	A
6137793	Gorman et al.	Oct 2000	A
6144401	Casement et al.	Nov 2000	A
6148400	Arnold	Nov 2000	A
6154844	Touboul et al.	Nov 2000	A
6157719	Wasilewski et al.	Dec 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
6167521	Smith et al.	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
6212636	Boyle et al.	Apr 2001	B1
6216129	Eldering	Apr 2001	B1
6219710	Gray et al.	Apr 2001	B1
6223160	Kostka et al.	Apr 2001	B1
6233341	Riggins	May 2001	B1
6233389	Barton et al.	May 2001	B1
6233687	White	May 2001	B1
6236968	Kanevsky et al.	May 2001	B1
6240401	Oren et al.	May 2001	B1
6256393	Safadi et al.	Jul 2001	B1
6259701	Shur et al.	Jul 2001	B1
6266421	Domyo et al.	Jul 2001	B1
6286041	Collins, III et al.	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
6456716	Arnold	Sep 2002	B1
RE37881	Haines	Oct 2002	E
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
6601171	Carter et al.	Jul 2003	B1
6604138	Virine et al.	Aug 2003	B1
6611654	Shteyn	Aug 2003	B1
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
6657991	Akgun et al.	Dec 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
6742116	Matsui et al.	May 2004	B1
6757796	Hofmann	Jun 2004	B1
6760768	Holden et al.	Jul 2004	B2
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
6782475	Sumner	Aug 2004	B1
6782550	Cao	Aug 2004	B1
6785810	Lirov et al.	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
6807573	Saito et al.	Oct 2004	B2
6810528	Chatani	Oct 2004	B1
6813505	Walley et al.	Nov 2004	B2
6813776	Chernock et al.	Nov 2004	B2
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
6859535	Tatebayashi et al.	Feb 2005	B1
6859845	Mate	Feb 2005	B2
6898708	Hori et al.	May 2005	B2
6898762	Ellis et al.	May 2005	B2
6909726	Sheeran	Jun 2005	B1
6909837	Unger	Jun 2005	B1
6910064	Astarabadi et al.	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
6948183	Peterka	Sep 2005	B1
6954632	Kobayashi	Oct 2005	B2
6957261	Lortz	Oct 2005	B2
6957328	Goodman et al.	Oct 2005	B2
6959288	Medina et al.	Oct 2005	B1
6973576	Giobbi	Dec 2005	B2
6975730	Kuroiwa et al.	Dec 2005	B1
6975850	Hurtta et al.	Dec 2005	B1
6978370	Kocher	Dec 2005	B1
6985355	Allirot	Jan 2006	B2
6990312	Gioscia et al.	Jan 2006	B1
6990680	Wugofski	Jan 2006	B1
6996544	Sellars et al.	Feb 2006	B2
7004243	Babcock et al.	Feb 2006	B1
7006881	Hoffberg et al.	Feb 2006	B1
7007170	Morten	Feb 2006	B2
7009972	Maher et al.	Mar 2006	B2
7016376	Goldenberg et al.	Mar 2006	B1
7016963	Judd et al.	Mar 2006	B1
7017179	Asamoto et al.	Mar 2006	B1
7017189	DeMello et al.	Mar 2006	B1
7020892	Levesque et al.	Mar 2006	B2
7024466	Russell et al.	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
7028329	Mizutani	Apr 2006	B1
7039048	Monta et al.	May 2006	B1
7039928	Kamada et al.	May 2006	B2
7054443	Jakubowski et al.	May 2006	B1
7054843	Charas	May 2006	B2
7054902	Toporek et al.	May 2006	B2
7055040	Klemba et al.	May 2006	B2
7058685	Van et al.	Jun 2006	B1
7058810	Kumazawa et al.	Jun 2006	B2
7065216	Benaloh et al.	Jun 2006	B1
7068639	Varma et al.	Jun 2006	B1
7069449	Weaver et al.	Jun 2006	B2
7069577	Geile et al.	Jun 2006	B2
7069578	Prus et al.	Jun 2006	B1
7072950	Toft	Jul 2006	B2
7073189	McElhatten et al.	Jul 2006	B2
7073193	Marsh	Jul 2006	B2
7073199	Raley	Jul 2006	B1
7075945	Arsenault et al.	Jul 2006	B2
7080397	Cochran et al.	Jul 2006	B2
7080400	Navar	Jul 2006	B1
7092397	Chandran et al.	Aug 2006	B1
7099308	Merrill et al.	Aug 2006	B2
7100183	Kunkel et al.	Aug 2006	B2
7103181	Ananth	Sep 2006	B2
7103906	Katz et al.	Sep 2006	B1
7106382	Shiotsu	Sep 2006	B2
7107326	Fijolek et al.	Sep 2006	B1
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
7154912	Chong et al.	Dec 2006	B2
7155226	Oh et al.	Dec 2006	B1
7155508	Sankuratripati et al.	Dec 2006	B2
7159235	Son et al.	Jan 2007	B2
7165268	Moore et al.	Jan 2007	B1
7171485	Roach et al.	Jan 2007	B2
7174126	McElhatten et al.	Feb 2007	B2
7174127	Otten et al.	Feb 2007	B2
7174371	Elo 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
7194756	Addington et al.	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
7225333	Peinado et al.	May 2007	B2
7228427	Fransdonk	Jun 2007	B2
7228555	Schlack	Jun 2007	B2
7231669	Leung et al.	Jun 2007	B2
7233948	Shamoon et al.	Jun 2007	B1
7237112	Ishiguro et al.	Jun 2007	B1
7237250	Kanojia et al.	Jun 2007	B2
7240196	Cooper et al.	Jul 2007	B2
7242960	Van et al.	Jul 2007	B2
7246150	Donoho et al.	Jul 2007	B1
7246172	Yoshiba et al.	Jul 2007	B2
7248694	Husemann et al.	Jul 2007	B2
7254608	Yeager et al.	Aug 2007	B2
7257227	Chen et al.	Aug 2007	B2
7257308	Plourde et al.	Aug 2007	B2
7263187	Pedlow et al.	Aug 2007	B2
7263188	Kohno	Aug 2007	B2
7266198	Medvinsky	Sep 2007	B2
7266726	Ladd et al.	Sep 2007	B1
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
7289534	Bailey et al.	Oct 2007	B1
7299502	Bailey et al.	Nov 2007	B2
7301944	Redmond	Nov 2007	B1
7305357	Hamilton	Dec 2007	B2
7305460	Park	Dec 2007	B2
7305691	Cristofalo	Dec 2007	B2
7313611	Jacobs et al.	Dec 2007	B1
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
7324531	Cho	Jan 2008	B2
7325073	Shao et al.	Jan 2008	B2
7327692	Ain et al.	Feb 2008	B2
7330483	Peters, Jr. et al.	Feb 2008	B1
7330875	Parasnis et al.	Feb 2008	B1
7330967	Pujare et al.	Feb 2008	B1
7337147	Chen et al.	Feb 2008	B2
7337459	Tsutsui et al.	Feb 2008	B1
7340510	Liskov et al.	Mar 2008	B1
7340760	Wachtfogel et al.	Mar 2008	B2
7346558	Rosenberg	Mar 2008	B2
7346630	Eichstaedt et al.	Mar 2008	B2
7352775	Powell	Apr 2008	B2
7353543	Ohmori et al.	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
7373506	Sano et al.	May 2008	B2
7373594	Lopez et al.	May 2008	B1
7376386	Phillips et al.	May 2008	B2
7376976	Fierstein et al.	May 2008	B2
7383228	Lisanke et al.	Jun 2008	B2
7386621	Hlasny	Jun 2008	B1
7397825	Woodward, Jr. et al.	Jul 2008	B2
7406099	Schlagintweit	Jul 2008	B2
7409546	Platt	Aug 2008	B2
7438233	Leiper	Oct 2008	B2
7441037	Saxena	Oct 2008	B2
7457520	Rossetti et al.	Nov 2008	B2
7472280	Giobbi	Dec 2008	B2
7486869	Alexander et al.	Feb 2009	B2
7487363	Alve et al.	Feb 2009	B2
7496647	Karaoguz et al.	Feb 2009	B2
7506367	Ishibashi	Mar 2009	B1
7533376	Anwar et al.	May 2009	B2
7567262	Clemens et al.	Jul 2009	B1
7567988	Wolf et al.	Jul 2009	B2
7577118	Haumonte et al.	Aug 2009	B2
7587172	Kim et al.	Sep 2009	B2
7592912	Hasek et al.	Sep 2009	B2
7602820	Helms et al.	Oct 2009	B2
7603529	MacHardy et al.	Oct 2009	B1
7627492	Nishizawa et al.	Dec 2009	B2
7634546	Strickholm et al.	Dec 2009	B1
7636792	Ho	Dec 2009	B1
7640581	Brenton et al.	Dec 2009	B1
7647618	Hunter et al.	Jan 2010	B1
7673004	Sherstinsky et al.	Mar 2010	B1
7690020	Lebar	Mar 2010	B2
7693171	Gould	Apr 2010	B2
7707644	Choi et al.	Apr 2010	B2
7712125	Herigstad et al.	May 2010	B2
7720432	Colby et al.	May 2010	B1
7721314	Sincaglia et al.	May 2010	B2
7730321	Gasparini et al.	Jun 2010	B2
7730509	Boulet et al.	Jun 2010	B2
7742074	Minatogawa	Jun 2010	B2
7752617	Blinick et al.	Jul 2010	B2
7757101	Nonaka et al.	Jul 2010	B2
7769629	Kriza et al.	Aug 2010	B1
7783891	Perlin et al.	Aug 2010	B2
7787416	Gidwani	Aug 2010	B2
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
7865440	Jaquette	Jan 2011	B2
7870599	Pemmaraju	Jan 2011	B2
7878908	Sloate et al.	Feb 2011	B2
7900229	Dureau	Mar 2011	B2
7908626	Williamson et al.	Mar 2011	B2
7925592	Issa et al.	Apr 2011	B1
7930558	Hori	Apr 2011	B2
7954131	Cholas et al.	May 2011	B2
7983418	Oyama et al.	Jul 2011	B2
7984473	Casile et al.	Jul 2011	B1
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
8150757	Sieffert et al.	Apr 2012	B1
8166508	Mitsuji et al.	Apr 2012	B2
8181206	Hasek	May 2012	B2
8181262	Cooper et al.	May 2012	B2
8205226	Ko et al.	Jun 2012	B2
8214256	Riedl et al.	Jul 2012	B2
8234387	Bradley et al.	Jul 2012	B2
8280982	La Joie et al.	Oct 2012	B2
8332370	Gattegno et al.	Dec 2012	B2
8332657	Eskicioglu et al.	Dec 2012	B1
8341242	Dillon et al.	Dec 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
8472627	Denning et al.	Jun 2013	B2
8520850	Helms et al.	Aug 2013	B2
8527602	Rasmussen	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
8761402	McAvoy et al.	Jun 2014	B2
9215423	Kimble et al.	Dec 2015	B2
9300919	Cholas et al.	Mar 2016	B2
9317241	Tranchina	Apr 2016	B2
9325710	Lajoie et al.	Apr 2016	B2
9578288	Chen	Feb 2017	B2
9706160	Marsh et al.	Jul 2017	B2
9832246	Lajoie et al.	Nov 2017	B2
9906838	Cronk et al.	Feb 2018	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
20010014946	Ichinoi et al.	Aug 2001	A1
20010019614	Madoukh et al.	Sep 2001	A1
20010029581	Knauft	Oct 2001	A1
20010030975	Limb et al.	Oct 2001	A1
20010037223	Beery et al.	Nov 2001	A1
20010049705	Murase et al.	Dec 2001	A1
20010053223	Ishibashi et al.	Dec 2001	A1
20010053226	Akins et al.	Dec 2001	A1
20010054181	Corvin	Dec 2001	A1
20010056541	Matsuzaki et al.	Dec 2001	A1
20020003789	Kim et al.	Jan 2002	A1
20020004870	Kobayashi	Jan 2002	A1
20020013772	Peinado	Jan 2002	A1
20020013940	Tsukamoto et al.	Jan 2002	A1
20020019984	Rakib	Feb 2002	A1
20020026496	Boyer et al.	Feb 2002	A1
20020026575	Wheeler et al.	Feb 2002	A1
20020027883	Belaiche	Mar 2002	A1
20020032754	Logston et al.	Mar 2002	A1
20020038296	Margolus et al.	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
20020048367	Maillard	Apr 2002	A1
20020049800	Kobayashi et al.	Apr 2002	A1
20020049902	Rhodes	Apr 2002	A1
20020054754	Kikuchi et al.	May 2002	A1
20020056118	Hunter et al.	May 2002	A1
20020056125	Hodge et al.	May 2002	A1
20020056175	Magarino et al.	May 2002	A1
20020059619	Lebar	May 2002	A1
20020059621	Thomas et al.	May 2002	A1
20020059635	Hoang	May 2002	A1
20020062440	Akama	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
20020077984	Ireton	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 et al.	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
20020126654	Preston et al.	Sep 2002	A1
20020129358	Buehl et al.	Sep 2002	A1
20020138854	Desai et al.	Sep 2002	A1
20020143565	Headings et al.	Oct 2002	A1
20020144067	Jeong	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
20020152393	Thoma et al.	Oct 2002	A1
20020152458	Eyer et al.	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
20020183985	Hori et al.	Dec 2002	A1
20020184154	Hori et al.	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
20020199105	Ishiguro 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
20030009681	Harada et al.	Jan 2003	A1
20030018977	McKenna	Jan 2003	A1
20030020744	Ellis et al.	Jan 2003	A1
20030021421	Yokota 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
20030041336	Del et al.	Feb 2003	A1
20030046560	Inomata et al.	Mar 2003	A1
20030048380	Tamura	Mar 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
20030069965	Ma et al.	Apr 2003	A1
20030070052	Lai	Apr 2003	A1
20030074571	Fujiwara et al.	Apr 2003	A1
20030074661	Krapf et al.	Apr 2003	A1
20030084003	Pinkas et al.	May 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
20030097340	Okamoto 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	Iver 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
20030140227	Asano et al.	Jul 2003	A1
20030143984	Umeda	Jul 2003	A1
20030145323	Hendricks et al.	Jul 2003	A1
20030149884	Hernandez et al.	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
20030151621	McEvilly et al.	Aug 2003	A1
20030163697	Pabla et al.	Aug 2003	A1
20030163739	Armington et al.	Aug 2003	A1
20030163832	Tsuria et al.	Aug 2003	A1
20030165241	Fransdonk	Sep 2003	A1
20030166401	Combes et al.	Sep 2003	A1
20030174838	Bremer	Sep 2003	A1
20030177490	Hoshino et al.	Sep 2003	A1
20030182551	Frantz et al.	Sep 2003	A1
20030187799	Sellars et al.	Oct 2003	A1
20030188023	Grecco et al.	Oct 2003	A1
20030205763	Park et al.	Nov 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
20040006694	Heelan et al.	Jan 2004	A1
20040015608	Ellis et al.	Jan 2004	A1
20040015989	Kaizu et al.	Jan 2004	A1
20040024688	Bi et al.	Feb 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
20040039911	Oka et al.	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
20040052377	Mattox et al.	Mar 2004	A1
20040060076	Song	Mar 2004	A1
20040073915	Dureau	Apr 2004	A1
20040078371	Worrall et al.	Apr 2004	A1
20040078602	Rothbarth et al.	Apr 2004	A1
20040078809	Drazin	Apr 2004	A1
20040088558	Candelore	May 2004	A1
20040093394	Weber et al.	May 2004	A1
20040103120	Fickle et al.	May 2004	A1
20040103429	Carlucci et al.	May 2004	A1
20040019569	Ellison et al.	Jun 2004	A1
20040103479	Mossbeck et al.	Jun 2004	A1
20040104842	Drury et al.	Jun 2004	A1
20040114539	Beshai et al.	Jun 2004	A1
20040117817	Kwon et al.	Jun 2004	A1
20040117836	Karaoguz et al.	Jun 2004	A1
20040117846	Karaoguz et al.	Jun 2004	A1
20040123125	Zuili	Jun 2004	A1
20040123129	Ginter et al.	Jun 2004	A1
20040128499	Peterka et al.	Jul 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
20040163111	Palazzo et al.	Aug 2004	A1
20040163129	Chapman et al.	Aug 2004	A1
20040172531	Little et al.	Sep 2004	A1
20040177369	Akins	Sep 2004	A1
20040177383	Martinolich et al.	Sep 2004	A1
20040181800	Rakib et al.	Sep 2004	A1
20040181811	Rakib	Sep 2004	A1
20040184616	Morten	Sep 2004	A1
20040185856	McKenna et al.	Sep 2004	A1
20040190714	Masui et al.	Sep 2004	A1
20040190721	Barrett et al.	Sep 2004	A1
20040193609	Phan et al.	Sep 2004	A1
20040193680	Gibbs et al.	Sep 2004	A1
20040193712	Benenati et al.	Sep 2004	A1
20040198386	Dupray	Oct 2004	A1
20040221305	Broussard et al.	Nov 2004	A1
20040224425	Gjerde et al.	Nov 2004	A1
20040237100	Pinder et al.	Nov 2004	A1
20040246933	Valko et al.	Dec 2004	A1
20040250273	Swix et al.	Dec 2004	A1
20040255139	Giobbi	Dec 2004	A1
20040255335	Fickle et al.	Dec 2004	A1
20040260798	Addington et al.	Dec 2004	A1
20040261096	Rebaud 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
20050005287	Claussen	Jan 2005	A1
20050015810	Gould et al.	Jan 2005	A1
20050021940	Ma	Jan 2005	A1
20050021985	Ono et al.	Jan 2005	A1
20050022227	Shen et al.	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
20050039212	Baran et al.	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
20050065888	Benaloh	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
20050091173	Alve	Apr 2005	A1
20050091539	Wang et al.	Apr 2005	A1
20050091681	Borden et al.	Apr 2005	A1
20050097006	Nyako	May 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
20050114686	Ball et al.	May 2005	A1
20050114900	Ladd et al.	May 2005	A1
20050138357	Swenson et al.	Jun 2005	A1
20050144333	Kotzin	Jun 2005	A1
20050144635	Boortz et al.	Jun 2005	A1
20050153778	Nelson et al.	Jul 2005	A1
20050166224	Ficco	Jul 2005	A1
20050169468	Fahrny et al.	Aug 2005	A1
20050172127	Hartung et al.	Aug 2005	A1
20050177740	Athaide et al.	Aug 2005	A1
20050177741	Chen et al.	Aug 2005	A1
20050177855	Maynard et al.	Aug 2005	A1
20050179938	Kayashima et al.	Aug 2005	A1
20050182931	Robert et al.	Aug 2005	A1
20050183120	Jain et al.	Aug 2005	A1
20050188210	Perlin et al.	Aug 2005	A1
20050190912	Hopkins et al.	Sep 2005	A1
20050195975	Kawakita	Sep 2005	A1
20050198693	Choi et al.	Sep 2005	A1
20050204019	Flynn et al.	Sep 2005	A1
20050210500	Stone	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
20050235318	Grauch et al.	Oct 2005	A1
20050239402	Gioscia et al.	Oct 2005	A1
20050251454	Wood	Nov 2005	A1
20050261970	Vucina et al.	Nov 2005	A1
20050262418	Gehrmann	Nov 2005	A1
20050262542	DeWeese et al.	Nov 2005	A1
20050267787	Rose et al.	Dec 2005	A1
20050268107	Harris et al.	Dec 2005	A1
20050273629	Abrams et al.	Dec 2005	A1
20050273819	Knudson et al.	Dec 2005	A1
20050273828	Barton	Dec 2005	A1
20050278259	Gunaseelan et al.	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
20060002551	Brown et al.	Jan 2006	A1
20060004662	Nadalin et al.	Jan 2006	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060010226	Hurtta et al.	Jan 2006	A1
20060013557	Poslinski	Jan 2006	A1
20060015352	Wynn et al.	Jan 2006	A1
20060015580	Gabriel et al.	Jan 2006	A1
20060015925	Logan	Jan 2006	A1
20060019702	Anttila et al.	Jan 2006	A1
20060020786	Helms et al.	Jan 2006	A1
20060020950	Ladd et al.	Jan 2006	A1
20060021004	Moran et al.	Jan 2006	A1
20060021019	Hinton et al.	Jan 2006	A1
20060031558	Ortega et al.	Feb 2006	A1
20060031883	Ellis et al.	Feb 2006	A1
20060031892	Cohen	Feb 2006	A1
20060036750	Ladd et al.	Feb 2006	A1
20060041903	Kahn et al.	Feb 2006	A1
20060041905	Wasilewski	Feb 2006	A1
20060041910	Hatanaka et al.	Feb 2006	A1
20060047603	Fontijn	Mar 2006	A1
20060047745	Knowles et al.	Mar 2006	A1
20060047801	Haag et al.	Mar 2006	A1
20060047957	Helms et al.	Mar 2006	A1
20060053473	Vau et al.	Mar 2006	A1
20060064583	Birnbaum 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
20060137005	Park	Jun 2006	A1
20060137015	Fahrny et al.	Jun 2006	A1
20060148362	Bridges	Jul 2006	A1
20060149850	Bowman	Jul 2006	A1
20060153017	Kim	Jul 2006	A1
20060159048	Han et al.	Jul 2006	A1
20060161635	Lamkin et al.	Jul 2006	A1
20060163340	Leiper	Jul 2006	A1
20060167808	Greene et al.	Jul 2006	A1
20060168219	Ahluwalia et al.	Jul 2006	A1
20060168616	Candelore	Jul 2006	A1
20060171390	La	Aug 2006	A1
20060171423	Helms et al.	Aug 2006	A1
20060173787	Weber et al.	Aug 2006	A1
20060176884	Fair et al.	Aug 2006	A1
20060179138	Van Gassel et al.	Aug 2006	A1
20060184972	Rafey 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
20060200856	Salowey et al.	Sep 2006	A1
20060200865	Leake 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
20060212400	Kamperman et al.	Sep 2006	A1
20060212435	Williams et al.	Sep 2006	A1
20060218604	Riedl et al.	Sep 2006	A1
20060218647	Hars et al.	Sep 2006	A1
20060222321	Russ	Oct 2006	A1
20060236131	Vauclair	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
20070011335	Burns et al.	Jan 2007	A1
20070019645	Menon	Jan 2007	A1
20070022032	Anderson et al.	Jan 2007	A1
20070022459	Gaebel et al.	Jan 2007	A1
20070022469	Cooper et al.	Jan 2007	A1
20070033531	Marsh	Feb 2007	A1
20070038931	Allaire et al.	Feb 2007	A1
20070046791	Wang et al.	Mar 2007	A1
20070049245	Lipman	Mar 2007	A1
20070061331	Ramer et al.	Mar 2007	A1
20070061336	Ramer 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 et al.	Apr 2007	A1
20070079381	Hartung et al.	Apr 2007	A1
20070083899	Compton et al.	Apr 2007	A1
20070086372	Lee et al.	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
20070098178	Raikar	May 2007	A1
20070101359	Schiller et al.	May 2007	A1
20070104456	Craner	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
20070118857	Chen et al.	May 2007	A1
20070121612	Nadeau et al.	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
20070124602	Wald et al.	May 2007	A1
20070124781	Casey et al.	May 2007	A1
20070129987	Hauser et al.	Jun 2007	A1
20070136743	Hasek et al.	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
20070157295	Mangalore et al.	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
20070174888	Rubinstein	Jul 2007	A1
20070186103	Randle et al.	Aug 2007	A1
20070192615	Varghese 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
20070206799	Wingert et al.	Sep 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
20070220024	Putterman et al.	Sep 2007	A1
20070220158	Tolgu et al.	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
20070250872	Dua	Oct 2007	A1
20070250880	Hainline	Oct 2007	A1
20070261116	Prafullchandra et al.	Nov 2007	A1
20070265978	Kahn et al.	Nov 2007	A1
20070271388	Bowra et al.	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
20080008321	Gagnon et al.	Jan 2008	A1
20080008371	Woods et al.	Jan 2008	A1
20080009268	Ramer et al.	Jan 2008	A1
20080021836	Lao	Jan 2008	A1
20080022012	Wang	Jan 2008	A1
20080040758	Beetcher et al.	Feb 2008	A1
20080052157	Kadambi et al.	Feb 2008	A1
20080059409	Montpetit	Mar 2008	A1
20080059804	Shah et al.	Mar 2008	A1
20080066112	Bailey et al.	Mar 2008	A1
20080072249	Hovnanian et al.	Mar 2008	A1
20080090513	Collins et al.	Apr 2008	A1
20080091805	Malaby et al.	Apr 2008	A1
20080091807	Strub et al.	Apr 2008	A1
20080092181	Britt	Apr 2008	A1
20080098212	Helms et al.	Apr 2008	A1
20080098422	Rodriguez et al.	Apr 2008	A1
20080103976	Read et al.	May 2008	A1
20080103977	Khosravy et al.	May 2008	A1
20080112405	Cholas et al.	May 2008	A1
20080115161	Kurzion	May 2008	A1
20080115169	Ellis et al.	May 2008	A1
20080117920	Tucker	May 2008	A1
20080123862	Rowley	May 2008	A1
20080133551	Wensley et al.	Jun 2008	A1
20080139193	Hao et al.	Jun 2008	A1
20080141353	Brown	Jun 2008	A1
20080147497	Tischer	Jun 2008	A1
20080148362	Gilder et al.	Jun 2008	A1
20080154626	Gounares et al.	Jun 2008	A1
20080155059	Hardin et al.	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
20080162353	Tom et al.	Jul 2008	A1
20080163305	Johnson et al.	Jul 2008	A1
20080165460	Whitby-Strevens	Jul 2008	A1
20080171423	Ieong et al.	Jul 2008	A1
20080177998	Apsangi et al.	Jul 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
20080212945	Khedouri et al.	Sep 2008	A1
20080216106	Maxwell	Sep 2008	A1
20080221986	Soicher et al.	Sep 2008	A1
20080222684	Mukraj et al.	Sep 2008	A1
20080229354	Morris et al.	Sep 2008	A1
20080235746	Peters et al.	Sep 2008	A1
20080256510	Auerbach	Oct 2008	A1
20080263578	Bayer et al.	Oct 2008	A1
20080270307	Olson 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
20080288618	Vardi 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
20090007234	Birger et al.	Jan 2009	A1
20090019134	Bellifemine et al.	Jan 2009	A1
20090019492	Grasset	Jan 2009	A1
20090025075	Chow et al.	Jan 2009	A1
20090031371	Munsell et al.	Jan 2009	A1
20090034521	Kato	Feb 2009	A1
20090083813	Dolce et al.	Mar 2009	A1
20090094652	Al et al.	Apr 2009	A1
20090098861	Kalliola et al.	Apr 2009	A1
20090100147	Igarashi	Apr 2009	A1
20090100459	Riedl et al.	Apr 2009	A1
20090102983	Malone et al.	Apr 2009	A1
20090132346	Duggal et al.	May 2009	A1
20090138922	Thomas et al.	May 2009	A1
20090151006	Saeki et al.	Jun 2009	A1
20090182815	Czechowski, III et al.	Jul 2009	A1
20090185576	Kisel et al.	Jul 2009	A1
20090187939	Lajoie	Jul 2009	A1
20090198794	Beals	Aug 2009	A1
20090201917	Maes et al.	Aug 2009	A1
20090210899	Lawrence-Apfelbaum et al.	Aug 2009	A1
20090210912	Cholas et al.	Aug 2009	A1
20090220216	Marsh et al.	Sep 2009	A1
20090225760	Foti	Sep 2009	A1
20090235319	Mao et al.	Sep 2009	A1
20090248794	Helms et al.	Oct 2009	A1
20090249473	Cohn	Oct 2009	A1
20090265750	Jones et al.	Oct 2009	A1
20090282241	Prafullchandra et al.	Nov 2009	A1
20090282449	Lee	Nov 2009	A1
20090290711	Bloom et al.	Nov 2009	A1
20090292922	Park	Nov 2009	A1
20090293101	Carter et al.	Nov 2009	A1
20090317065	Fyock et al.	Dec 2009	A1
20090319379	Joao	Dec 2009	A1
20090320059	Bolyukh	Dec 2009	A1
20100017627	Princen et al.	Jan 2010	A1
20100030578	Siddique et al.	Feb 2010	A1
20100031299	Harrang et al.	Feb 2010	A1
20100042478	Reisman	Feb 2010	A1
20100082983	Shah et al.	Apr 2010	A1
20100083329	Joyce et al.	Apr 2010	A1
20100083362	Francisco et al.	Apr 2010	A1
20100088236	Karabulut et al.	Apr 2010	A1
20100088292	Tirpak et al.	Apr 2010	A1
20100106846	Noldus et al.	Apr 2010	A1
20100107194	McKissick et al.	Apr 2010	A1
20100131973	Dillon et al.	May 2010	A1
20100138900	Peterka et al.	Jun 2010	A1
20100146539	Hicks, III et al.	Jun 2010	A1
20100169977	Dasher et al.	Jul 2010	A1
20100175584	Kusaka et al.	Jul 2010	A1
20100185855	Margolus et al.	Jul 2010	A1
20100198888	Blomstedt et al.	Aug 2010	A1
20100217837	Ansari et al.	Aug 2010	A1
20100251304	Donoghue et al.	Sep 2010	A1
20100251305	Kimble et al.	Sep 2010	A1
20100251312	Albano et al.	Sep 2010	A1
20100287584	Starikov et al.	Nov 2010	A1
20100287609	Gonzalez et al.	Nov 2010	A1
20100306369	Riley	Dec 2010	A1
20100310076	Barzilai et al.	Dec 2010	A1
20100313225	Cholas et al.	Dec 2010	A1
20100313226	Cholas et al.	Dec 2010	A1
20110015989	Tidwell et al.	Jan 2011	A1
20110016479	Tidwell et al.	Jan 2011	A1
20110016482	Tidwell et al.	Jan 2011	A1
20110040755	Hindle et al.	Feb 2011	A1
20110041146	Lewis	Feb 2011	A1
20110055347	Hu et al.	Mar 2011	A1
20110071841	Fomenko et al.	Mar 2011	A1
20110078721	Wang et al.	Mar 2011	A1
20110093900	Patel et al.	Apr 2011	A1
20110099593	Kim et al.	Apr 2011	A1
20110103374	Lajoie et al.	May 2011	A1
20110107379	Lajoie et al.	May 2011	A1
20110164753	Dubhashi et al.	Jul 2011	A1
20110169977	Masuda	Jul 2011	A1
20110179096	Friedman	Jul 2011	A1
20110197070	Mizrah	Aug 2011	A1
20110206200	Sovio et al.	Aug 2011	A1
20110213688	Santos et al.	Sep 2011	A1
20110219229	Cholas et al.	Sep 2011	A1
20110252236	De et al.	Oct 2011	A1
20110252243	Brouwer et al.	Oct 2011	A1
20120005756	Hoefelmeyer et al.	Jan 2012	A1
20120008786	Cronk et al.	Jan 2012	A1
20120011567	Cronk et al.	Jan 2012	A1
20120030714	Sweatt, III et al.	Feb 2012	A1
20120089699	Cholas	Apr 2012	A1
20120131629	Shrum, Jr. et al.	May 2012	A1
20120158547	Wood et al.	Jun 2012	A1
20120159603	Queck	Jun 2012	A1
20120167173	Nadalin et al.	Jun 2012	A1
20120260346	Carey et al.	Oct 2012	A1
20120284765	Killick	Nov 2012	A1
20120291062	Pearson et al.	Nov 2012	A1
20120291140	Robert	Nov 2012	A1
20130036011	Roberts et al.	Feb 2013	A1
20130120570	Stanley	May 2013	A1
20130191443	Gan et al.	Jul 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
20130309971	Kiukkonen et al.	Nov 2013	A1
20130318629	Lajoie et al.	Nov 2013	A1
20130347089	Bailey et al.	Dec 2013	A1
20140233923	Bradley et al.	Aug 2014	A1
20140281489	Peterka et al.	Sep 2014	A1
20140282750	Civiletto	Sep 2014	A1
20140283137	Rebaud et al.	Sep 2014	A1
20150348129	Inoue et al.	Dec 2015	A1
20160050190	Mooij et al.	Feb 2016	A1
20160165650	Kim et al.	Jun 2016	A1
20160165651	Pathuri et al.	Jun 2016	A1
20160301525	Canard et al.	Oct 2016	A1

Foreign Referenced Citations (89)

Number	Date	Country
2376550	Dec 2000	CA
2376550	Aug 2008	CA
2438497	Nov 2013	CA
1134951	Sep 2001	EP
1139198	Oct 2001	EP
1691523	Aug 2006	EP
2113860	Nov 2009	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	Aug 1993	JP
H-0263440	Oct 1996	JP
2000156676	Jun 2000	JP
2000332746	Nov 2000	JP
2001243707	Sep 2001	JP
2001274786	Oct 2001	JP
2001274788	Oct 2001	JP
2001285821	Oct 2001	JP
2002163396	Jun 2002	JP
2002335507	Nov 2002	JP
2002352094	Dec 2002	JP
2003058657	Feb 2003	JP
2003162600	Jun 2003	JP
2003233690	Aug 2003	JP
2003248508	Sep 2003	JP
2003296484	Oct 2003	JP
2003348508	Dec 2003	JP
2004030111	Jan 2004	JP
2004072721	Mar 2004	JP
2004120736	Apr 2004	JP
2004120738	Apr 2004	JP
2004303111	Oct 2004	JP
2005506627	Mar 2005	JP
2005519365	Jun 2005	JP
2005519501	Jun 2005	JP
2005339093	Dec 2005	JP
2006185473	Jul 2006	JP
2006311267	Nov 2006	JP
2007020144	Jan 2007	JP
2008186272	Aug 2007	JP
2007534030	Nov 2007	JP
2007336553	Dec 2007	JP
2008005047	Jan 2008	JP
2008015936	Jan 2008	JP
2008021293	Jan 2008	JP
2008507905	Mar 2008	JP
2008167018	Jul 2008	JP
2008206039	Sep 2008	JP
2008539631	Nov 2008	JP
2009071786	Apr 2009	JP
2009515238	Apr 2009	JP
2009176060	Aug 2009	JP
2009211632	Sep 2009	JP
2010502109	Jan 2010	JP
2010079902	Apr 2010	JP
2012505436	Mar 2012	JP
2012523614	Oct 2012	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-0103410	Jan 2001	WO
WO-0110125	Feb 2001	WO
WO-0137479	May 2001	WO
WO-0156285	Aug 2001	WO
WO-0160771	Aug 2001	WO
WO-0169842	Sep 2001	WO
WO-0177778	Oct 2001	WO
WO-0191474	Nov 2001	WO
WO-0213032	Feb 2002	WO
WO-0221841	Mar 2002	WO
WO-0242966	May 2002	WO
WO-02080556	Oct 2002	WO
WO-03038704	May 2003	WO
WO-03087799	Oct 2003	WO
WO-03093944	Nov 2003	WO
WO-2004027622	Apr 2004	WO
WO-2005015422	Feb 2005	WO
WO-2006020141	Feb 2006	WO
WO-2008070062	Jun 2008	WO
WO-2008080556	Jul 2008	WO
WO-2009020476	Feb 2009	WO
WO-2012021245	Feb 2012	WO

Non-Patent Literature Citations (65)

Entry
5C Digital Transmission Content Protection White Paper, Hitachi, Ltd., et al. dated Jul. 14, 1998, 15 pages.
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/security/saml/v2.0/saml-core-2.0-os.pdf).
David P.A., “The Beginnings and Prospective Ending of ‘End-to-End’: An Evolutionary Perspective on the Internet's Architecture,” Stanford Institute for Economic Policy Research, Aug. 2001, 34 pages.
DCAS Authorized Service Domain, Version 1.2, dated Nov. 4, 2008, 58 pages.
DCAS Authorized Service Domain, Version 1.2, Nov. 30, 2005, 56 pages.
DCAS Licensed Specification Abstracts, CableLabs Confidential Information, Jan. 12, 2006, 4 pages.
Digital Video Broadcasting (DVB); DVB SimulCrypt; Part 1: “Head-end architecture and synchronization” Technical Specification—ETSI TS 101 197 V1.2.1 (Feb. 2002), 40 pages.
DVB (Digital Video Broadcasting), DVB Document A045 Rev. 3, Jul. 2004, “Head-end Implementation of SimulCrypt,” 289 pages.
Extended European Search Report for Application No. EP05848363, dated Aug. 26, 2009, 9 pages.
Extended European Search Report for Application No. EP12151109, dated May 23, 2014, 9 pages.
Federal Information Processing Standards Publication, US FIPS PUB 197, Nov. 26, 2001, “Advanced Encryption Standards (AES),” 47 pages.
Ford B., “Unmanaged Internet Protocol: Scalable Application-Friendly Internet Routing,” Jul. 24, 2003, 6 pages.
Ford B., “Unmanaged Internet Protocol: Taming the Edge Network Management Crisis,” ACM SIGCOMM Computer Communications Review, vol. 34 (1), Jan. 2004, pp. 93-98.
High-bandwidth Digital Content Protection System, Revision 1.091, dated Apr. 22, 2003, Digital Content Protection LLC Draft, 78 pages.
International Search Report for Application No. PCT/US05/44537, dated Aug. 8, 2008, 1 pages.
Media Server; 1 Device Template Version 1.01 Jun. 25, 2002.
Open Cable Specification entitled “Enhanced TV Binary Interchange Format 1 0” 0C-SP-ETV-131F1.0-106-110128 dated Jan. 28, 2011, 408 pages.
OpenCable Application Platform Specification, OCAP 2.0 Profile, OC-SP-OCAP2.0-I01-020419, Apr. 19, 2002.
OpenCable Application Platform Specifications, OCAP Extensions, OC-SP-OCAP--HNEXT-I03-080418, 2005-2008.
OpenCable Host Device, Core Functional Requirements, OC-SP-HOST-CFR-I13-030707, Jul. 7, 2003.
OpenCable, HOST-POD Interface Specification, OC-SP-HOSTPOD-IF-113-030707, Jul. 7, 2003.
OpenCable Specification, Home Networking Protocol 2.0, OC-SP-HNP2.0-I01-08418, 2007.
OpenCable Specifications, Home Networking Security Specification, OC-SP-HN-SEC-DO1-081027, draft (Oct. 27, 2008).
Primergy BX300 Switch Blade user's manual, Fujitsu Corp., Sep. 30, 2002, first edition, pp. 1 to 20.
Zhang, et al., “A Flexible Content Protection System for Media-On-Demand” Multimedia Software Engineering, 2002 Proceedings. Fourth International Symposium on Dec. 11-13, 2002, Piscataway, NJ, USAA, IEEE, Dec. 11, 2002, pp. 272-277, XP010632760ISBN: 978-0-7695-1857-2.
Real System Media Commerce Suite (Technical White Paper), at http://docs.real.com/docs/drm/DRM.sub-WP1.pdf, 12 pages, Nov. 2001.
Real System Media Commerce Suite Technical White Paper, Copyright 2011, Real Networks, Inc., 16 pages, (http://www.realnetworkis).
RealSystem Media Commerce Suite Technical White Paper, Copyrgt, 2001 RealNetworks, Inc., http://www.realnetworks.com, 16 pages.
Sadok D.H., et al., “Trends in Network and Device Composition,” Topics in Internet Technology, IEEE Communications Magazine, Oct. 2006, pp. 112-118.
Tandberg Television specification entitled “AdPoint.RTM. Advanced Advertising Platform” dated Mar. 2008, 2 pages.
Van Moffaert, K., et al. (“Digital Rights Management: DRM is a key enabler for the future growth of the broadband access market and the telecom/networking market in general”, Alcatel Telecommunications Review, Alcatel, Paris Cedex FR, Apr. 1, 2003, XP007005930ISSN; 8 pages.
Written Opinion for Application No. PCT/US05/44537, dated Aug. 8, 2008, 3 pages.
Zhang, et al., A Flexible Content Protection System for Media-on-Demand, ISM China Research Lab, Proceedings of the IEEE Fourth International Symposium on Multimedia Software Engineering (MSE'02), 6 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, Document ID saml-bindings-2.0-os , (http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf).
Congdon et al., “IEEE 802.1 X Remote Authentication Dial in User Service (RADIUDS) Usage Guidelines”, RFC 3580, 2003.
Carnoy, David, “Anthony Wood and Mike Ramsey at War,” Success, Mar. 1999, pp. 52-57.
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.
Lipschitz Sugarman, Margo “A Picture of the Future” pp. 1-2, http://vvww.vsoft.com/prints/picture.sub.-- of.sub.--the.sub.--future.htm, Dec. 20, 1999.
Marusic, et al., “Share it!—Content Transfer in Home-to-Home Networks.” IEEE MELECON 2004, May 12-15, 2004, Dubrovnik, Croatia.
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.
“Powerkey” family (Powerkey Book 2, Powerkey Book 3, etc.) NDS (including VideoGuard, mVideoGuard, etc.). ANSI/SCTE Standard 52 2003 (DVS-042).
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/press2000o.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.

Related Publications (1)

	Number	Date	Country
	20180324494 A1	Nov 2018	US

Divisions (1)

	Number	Date	Country
Parent	13797577	Mar 2013	US
Child	15969597		US

Methods and apparatus for providing and uploading content to personalized network storage

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Term Extension

Abstract