Patent Grant
11455376
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The invention relates generally to the field of data and content distribution and delivery. In one exemplary aspect, the invention relates to the delivery of content to an IP-enabled device via a content distribution network.
Content distribution networks (such as e.g., Cable Television (CATV), satellite, or hybrid fiber/copper (HFCu) systems) provide content from various content sources at a network headend to a plurality of subscriber devices. In a typical “managed” network, a network operator (e.g., multiple systems operator or MSO) provides access to content via the network. Generally, the MSO provides audio/video content to subscribers via the network headend.
Recent advances in digital information processing and technology have made a whole range of services and functions available for delivery to consumers at various types of devices for very reasonable prices or subscription fees. These services and functions include delivery of digital content or programming (movies, etc.), digital video-on-demand (VOD) services, personal video recorder (PVR) and networked PVR (nPVR) services, Internet Protocol television (IPTV), digital media playback and recording, as well high speed Internet access (including so-called “Internet TV”, where television programming is delivered over the Internet) and IP-based telephony (e.g., VoIP). Other services available to network users include without limitation access to, and recording of, digital music (e.g., MP3 files), and submission of “organic” media (e.g., home-grown Youtube™ videos, etc.).
Currently, many of these services are provided to users via a wide variety of different equipment environments and delivery paradigms including, inter alia, cable or satellite modems or QAMs, HFCu (i.e., Hybrid Fiber-copper distribution via indigenous POST/PSTN and/or coaxial wiring in a premises), optical fiber such as FTTC, FTTH, etc., Wi-Fi™ hubs, Ethernet hubs, gateways, switches, and routers, and to a plurality of user equipment types (e.g., set-top boxes, personal (desktop) computers, laptop computers, other mini-computers such as so-called “netbooks” and mini-notebook computers, and/or other devices). Recent advances in consumer electronics have also led to the widespread introduction of a variety of portable media devices (PMDs) such as, inter alia, portable digital music devices such as the well known Apple iPod™ and other so-called “MP3 players”, cellular telephones/smartphones, handheld computers, tablets such as the Kindle™ and Nook™ and iPad™, and personal digital assistants (PDA), which allow users to store and playback audio and video files.
Although a myriad of services, equipment, data formats and providers are available, current systems offer no suitable mechanism for efficiently providing content to IP-enabled devices via a managed network without utilizing a traditional IP content delivery system (i.e., a high speed data connection, such as a cable modem termination system or CMTS). As noted previously, network operators may be capable of providing audio/video data over their own managed IP content delivery networks; however, such mechanisms are only accessible to subscribers of the network via a high-speed data connection. For example, “basic cable” CATV subscribers (which often form the backbone of revenue streams for a managed network operator), do not under existing technology have access to MSO-provided content via an IP-enabled device such as a PC, smartphone, or tablet computer.
Hence, methods and apparatus are needed which enable flexible delivery of content to IP-enabled devices without the use of a high-speed data connection; i.e., via another distribution platform (such as for example a traditional CATV or other distribution network). Ideally, the methods and apparatus would be able to allow the network operator to provide audio/video content services to an IP-enabled device associated with a non-data subscriber of the operator's network though the use of a cable modem or other network bridge. For example, an MSO would be able to make content delivery services available to a subscriber's tablet computer (e.g., iPad) when the owner thereof does not subscribe to the MSO's high-speed data network or services, and instead only subscribes to the MSO's video services via a network bridge. Such methods and apparatus would advantageously enable a user to receive content on IP-enabled devices, which are generally more mobile than non-IP devices, thereby enhancing the user experience by no longer anchoring the user to a fixed location.
The foregoing delivery of content may ideally utilize a modem to provide the content to the user devices which is limited to only retrieving content for delivery to the IP-enabled devices, and cannot access high-speed data services or other prohibited functions/services. In addition, the modem may be configured to filter or block traffic to or from an unauthorized entity. Ideal solutions may further enable the MSO network user/subscriber to no longer be limited to utilizing access points which are serviced by an MSO managed network and may include a premises modem which is able to register as a client of a third-party provided access point; however, is able to receive requested content from the distribution network for delivery to the client devices.
Furthermore, the ideal solution would take advantage of extant network structure and function to the maximum extent practicable in order to minimize MSO investment/latency in providing such services.
The present invention provides, inter alia, apparatus and methods for packet (e.g., IP) content distribution to packet-enabled devices.
In a first aspect of the invention, an apparatus for receiving content from a managed network, and providing the content to at least one client device is disclosed. In one embodiment, the client device is an Internet protocol (IP)-enabled client device, and the apparatus includes a network interface, a client interface, a storage device having at least one computer program stored thereon, and a processor in communication with the network and client interfaces and the storage device.
In one variant, the processor is configured to run the at least one computer program thereon, the at least one computer program configured to, when executed: receive a request for content via the client interface, provide at least one address within the managed network for the request, and transmit the request to the at least one address via the network interface and a high-speed data channel of the managed network.
In another variant, the provision of the at least one address is performed so that only the content can be retrieved via the high-speed data channel, and no high-speed data services can be provided via the high-speed data channel.
In a second aspect of the invention, a method for providing content to an Internet protocol (IP)-enabled consumer device is disclosed. In one embodiment, the method includes receiving at a first apparatus a request to access content from the IP-enabled consumer device, providing the request and a plurality of information necessary to verify permission of the consumer device to access the content to at least one network entity, the at least one entity verifying the permission of the consumer device, and upon verification of the permission of the consumer device, receiving data relating to the content, the data enabling the consumer device to obtain at least portions of the content for delivery. In one variant, the delivery includes providing the content to the consumer device via the first apparatus over a repurposed high-speed data channel.
In a third aspect of the invention, an apparatus for providing packetized content provided from a content distribution network to at least one Internet protocol (IP)-enabled client device is disclosed. In one embodiment, the apparatus includes a first interface for communication with the content distribution network, a second interface for communication with a third party access point, the access point configured to provide data from a third party network at least to the IP-enabled client device, and a processor in communication with the first and second interfaces and configured to run at least one computer program thereon.
In one variant, the at least one computer program comprises a plurality of commands which, when executed on the processor, cause the apparatus to: receive via the second interface a request issued from the client device for delivery of packetized content from the content distribution network, cause routing of the request via the first interface to an entity of the content distribution network for servicing the request, receive the requested content from the content distribution network, and cause forwarding the received content to the IP-enabled client device for rendering.
In a fourth aspect of the invention, a client apparatus for receiving content from a managed network is disclosed. In one embodiment, the client apparatus includes a communications interface, a display device, and a processor in communication with the display device and the communications interface. In one variant, the processor is configured to run at least one computer application thereon, the at least one computer application configured to, when executed display a listing of a plurality of content elements available for download from the network on the display device, receive a selection of at least one of the content elements from a user, issue a request to an entity for the at least one selected content element via the communications interface, receive a plurality of segments from the entity via the interface, receive a playlist from the entity via the interface, and use the playlist to utilize the segments to render the at least one content element on the display device.
In a fifth aspect of the invention, method of providing packetized media over a managed network is disclosed. In one embodiment. The network has at least a first channel configured for delivery of media content, and a second channel configured for delivery of high-speed data service, and the method includes enabling a user to receive only the media content otherwise available on the first channel as packetized media via the second channel.
In a sixth aspect of the invention, a method of providing packetized media over a managed network having a first channel configured for delivery of media content, and a second channel configured for delivery of high-speed data service is disclosed. In one embodiment, the method includes enabling a user to receive the media content via the first channel, or as packetized content via the second channel, and restricting a user from receiving any of the high speed data service via the second channel.
In a seventh aspect of the invention, a method of providing Internet Protocol (IP) content delivery services to mobile device users via a managed content distribution network having both a first media delivery channel and a second high speed data channel is disclosed. In one embodiment, the method includes associating a mobile device with an apparatus capable of accessing the second channel, issuing a request to receive IP content from the mobile device to the network via the apparatus, receiving the requested content at the mobile device from the network via the apparatus and the second channel, and rendering the content on the mobile device.
In one variant, the apparatus restricts the mobile device from otherwise receiving any high speed data services via the apparatus and the second channel.
In an eighth aspect of the invention, a managed network architecture is disclosed. In one embodiment, the managed network architecture enables delivery of packetized (e.g., IP) content to user devices without use of high-speed data service infrastructure.
In a ninth aspect of the invention, a method of doing business is disclosed. In one embodiment, the method includes providing a separate service class (e.g., mobile IP data) for network users/subscribers that is decoupled from high-speed data service provided by the same network; i.e., IP delivery without the need for high-speed data service.
In a tenth aspect of the invention, a computer readable medium is disclosed. In one embodiment, the computer readable medium comprises a plurality of instructions which are configured to, when executed enable delivery of Internet Protocol (IP) content delivery services to mobile device users via a managed content distribution network having both a first media delivery channel and a second high speed data channel.
These and other aspects of the invention shall become apparent when considered in light of the disclosure provided herein.
All Figures © Copyright 2011 Time Warner Cable, Inc. All rights reserved.
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 terms “client device” and “end user device” include, but are not limited to, set-top boxes (e.g., DSTBs), gateways, modems, personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), tablets, and smartphones.
As used herein, the term “codec” refers to a video, audio, or other data coding and/or decoding algorithm, process or apparatus including, without limitation, those of the MPEG (e.g., MPEG-1, MPEG-2, MPEG-4/H.264, etc.), Real (RealVideo, etc.), AC-3 (audio), DiVX, XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, 9, 10, or 11), ATI Video codec, or VC-1 (SMPTE standard 421M) families.
As used herein, the term “computer program” or “software” is meant to include any sequence or human or machine cognizable steps which perform a function. Such program may be rendered in virtually any programming language or environment including, for example, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML, VoXML), and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA), Java™ (including J2ME, Java Beans, etc.), Binary Runtime Environment (e.g., BREW), and the like.
The terms “consumer premises equipment (CPE)” and “host device” refer without limitation to any type of electronic equipment located within a consumer's or user's premises and connected to a network. The term “host device” includes terminal devices that have 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 “consumer premises equipment” (CPE) includes such electronic equipment such as set-top boxes, televisions, Digital Video Recorders (DVR), gateway storage devices (Furnace), and ITV Personal Computers.
As used herein, the term “DOCSIS” refers to any of the existing or planned variants of the Data Over Cable Services Interface Specification, including for example DOCSIS versions 1.0, 1.1, 2.0 and 3.0.
As used herein, the term “gateway” includes, without limitation, devices configured to interface with a network, and pass signals to or exchange signals with, another device in communication therewith. Various exemplary gateways are described in, inter alia, co-owned U.S. patent application Ser. No. 11/818,236 filed on Jun. 13, 2007 entitled “PREMISES GATEWAY APPARATUS AND METHODS FOR USE IN A CONTENT-BASED NETWORK”, which issued as U.S. Pat. No. 7,954,131 on May 31, 2011, U.S. patent application Ser. No. 12/582,619 filed on Oct. 20, 2009 and entitled “GATEWAY APPARATUS AND METHODS FOR DIGITAL CONTENT DELIVERY IN A NETWORK”, which issued as U.S. Pat. No. 9,027,062 on May 5, 2015, and co-pending U.S. patent application Ser. No. 12/480,597 filed on Jun. 8, 2009 and entitled “MEDIA BRIDGE APPARATUS AND METHODS”, each of the foregoing being incorporated herein by reference in its entirety.
As used herein, the term “headend” refers generally to a networked system controlled by an operator (e.g., an MSO or multiple systems operator) that distributes programming to MSO clientele using client devices. Such programming may include literally any information source/receiver including, inter alia, free-to-air TV channels, pay TV channels, interactive TV, and the Internet.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet.
As used herein, the 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 computer fabrics (RCFs), array processors, secure microprocessors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single unitary IC die, or distributed across multiple components.
As used herein, the terms “MSO” or “multiple systems operator” refer without limitation to a cable, fiber to the home (FTTH), fiber to the curb (FTTC), satellite, Hybrid Fiber Copper (HFCu), 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, HFCu networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications or networking protocols.
As used herein, the term “network interface” refers to any signal, data, or software interface with a component, network or process including, without limitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g., USB2), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radio frequency tuner (e.g., in-band or OOB, cable modem, etc.), Wi-Fi (802.11), WiMAX (802.16), PAN (e.g., 802.15), cellular (e.g., 3G; LTE/LTE-A/TD-LTE, GSM, etc.) or IrDA families.
As used herein, the term “node” refers to any functional entity associated with a network, such as for example an OLT or ONU, whether physically discrete or distributed across multiple locations.
As used herein, the term “QAM” refers to modulation schemes used for sending signals over cable networks. Such modulation scheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM, 256-QAM, etc.) depending on details of a cable network. A QAM may also refer to a physical channel modulated according to the schemes.
As used herein, the term “server” refers to any computerized component, system or entity regardless of form which is adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer system or network.
As used herein, the term “service”, “content”, “program” and “stream” are sometimes used synonymously to refer to a sequence of packetized data that is provided in what a subscriber may perceive as a service. A “service” (or “content”, or “stream”) in the former, specialized sense may correspond to different types of services in the latter, non-technical sense. For example, a “service” in the specialized sense may correspond to, among others, video broadcast, audio-only broadcast, pay-per-view, or video-on-demand. The perceivable content provided on such a “service” may be live, pre-recorded, delimited in time, undelimited in time, or of other descriptions. In some cases, a “service” in the specialized sense may correspond to what a subscriber would perceive as a “channel” in traditional broadcast television.
As used herein, the term “service group” refers without limitation to either a group of service users (e.g. subscribers), or the resources shared by them in the form of for example entire cable RF signal, only the RF channels used to receive the service or otherwise treated as a single logical unit by the network for resource assignment.
As used herein, the term “Wi-Fi” refers to, without limitation, any of the variants of IEEE-Std. 802.11 or related standards including 802.11 a/b/g/n/s/v.
As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, narrowband/FDMA, OFDM, PCS/DCS, LTE/LTE-A/TD-LTE, analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
Overview
In one salient aspect, the present invention discloses methods and apparatus for providing content to a plurality of IP-enabled devices serviced by a content distribution network. In one exemplary embodiment, a network architecture is disclosed which enables delivery of content to such IP-enabled devices without the use of a high-speed data service; i.e., via another distribution platform (such as for example a traditional CATV or other managed distribution network in-band QAMs). This capability allows the managed network operator to provide audio/video content services to an IP-enabled device (e.g., mobile wireless content rendering device such as a smartphone or tablet computer) associated with a non-data subscriber of the operator's network. For example, an MSO is, utilizing the exemplary apparatus and methods described herein, able to make content delivery services available to a subscriber's tablet computer (e.g., iPad) when the owner thereof does not subscribe to the MSO's high-speed data network or services, and instead only subscribes to the MSO's video services. This approach advantageously enables a user to receive content on IP-enabled devices, which are generally more mobile than non-IP devices, thereby enhancing the user experience by allowing the user to received the content at various locations (as well as that specified in the subscription agreement; e.g., at the subscriber's premises). It also provides the basis for alternate business models for the network operator; i.e., since provision of IP-based content is no longer tied to high-speed data services, a larger customer base can be reached, and with greater flexibility and available options/combinations and locations.
In the exemplary implementation, extant network structure and function (e.g., DOCSIS or in-band QAMs of an HFC network) are utilized to the maximum extent in order to minimize MSO investment in providing such services, thereby also enhancing rapid incorporation of the technology and provision of services to the users/subscribers.
In one embodiment, a modem (e.g., DOCSIS-enabled cable modem) is utilized to provide content to the IP-enabled client or user devices associated with a content distribution network. The modem is configured so as to only point to a root server (or other designated servers) in the content distribution network. The modem is therefore limited to only retrieving content for delivery to the IP-enabled devices, and cannot access high-speed data services or other prohibited functions/services. In addition, the modem may be configured to filter or block traffic to or from an unauthorized entity, so as to further tailor the functionality of the modem to a desired service or set of services. Such tailoring may be useful for, inter alia, ensuring that copyright restrictions or royalty arrangements are not subrogated through delivery of the same content over multiple modalities.
In another embodiment, the client device receives Internet data from a non-managed or third-party network via a third-party provided access point. In order to receive content from the managed network (MSO network), a premises modem that acts effectively as a media server is provided. The premises modem is associated with and communicates with the MSO network. The premises modem (media server) registers as a client of the third-party provided access point; however, is identified by the content distribution (MSO) network and therefore able to receive requested content from the distribution network for delivery to the client devices. This approach advantageously offers a user of the client device a more seamless user experience when utilizing both the third-party network and the MSO network for services.
In yet another embodiment, the MSO network user/subscriber is not limited to utilizing access points which are serviced by an MSO managed network. Rather, the transcoded/transrated and segmented content and playlist are delivered to the IP-enabled device over a non-managed network or third party network such as the Internet. A network gateway is utilized to interface the non-managed network to the managed network (e.g., CATV network). Various mechanisms for ensuring the security of content transmitted utilizing the methods and apparatus of the present invention are also disclosed. Such mechanisms include, e.g., authenticating the user as a subscriber to the MSO (such as by login/password combinations), determining whether the subscriber's service/subscription level permits viewing of the requested content (and optionally one or more use restrictions), and/or determining whether the requesting device is within a home network or other premises serviced by the MSO (such as by verifying the IP or MAC address of the entity used to access the MSO network).
Detailed Description of Exemplary Embodiments
Exemplary embodiments of the apparatus and methods of the present invention are now described in detail. While these exemplary embodiments are described in the context of the aforementioned hybrid fiber/coax (HFC) cable system architecture having an multiple systems operator (MSO), digital networking capability, IP delivery capability, and plurality of client devices/CPE, the general principles and advantages of the invention may be extended to other types of networks and architectures, whether broadband, narrowband, wired or wireless, or otherwise, the following therefore being merely exemplary in nature. For example, the invention may be practiced over a fiber-to-the-home (FTTH) or fiber-to-the-curb (FTTC) system, HFCu networks, or over satellite or millimeter wave-based networks.
It will also be appreciated that while described generally in the context of a consumer (i.e., residential) end user domain, the present invention may be readily adapted to other types of environments (e.g., commercial/enterprise, government/military, etc.) as well. Myriad other applications are possible.
It is further noted that while exemplary embodiments are described primarily in the context of a hybrid fiber/conductor (e.g., cable) system with legacy 6 MHz RF channels, the present invention is applicable to literally any network topology or paradigm, and any frequency/bandwidth. Furthermore, as referenced above, the invention is in no way limited to traditional cable system frequencies (i.e., below 1 GHz), and in fact may be used with systems that operate above 1 GHz band in center frequency or bandwidth, to include without limitation so-called ultra-wideband systems.
Other features and advantages of the present invention will immediately be recognized by persons of ordinary skill in the art with reference to the attached drawings and detailed description of exemplary embodiments as given below.
Network—
The data/application origination point 102 comprises any medium that allows data and/or applications (such as a VOD-based or “Watch TV” application) to be transferred to a distribution server 104. This can include for example a third party data source, application vendor website, CD-ROM, external network interface, mass storage device (e.g., RAID system), etc. Such transference may be automatic, initiated upon the occurrence of one or more specified events (such as the receipt of a request packet or ACK), performed manually, or accomplished in any number of other modes readily recognized by those of ordinary skill.
The application distribution server 104 comprises a computer system where such applications can enter the network system. Distribution servers are well known in the networking arts, and accordingly not described further herein.
The VOD server 105 comprises a computer system where on-demand content can be received from one or more of the aforementioned data sources 102 and enter the network system. These servers may generate the content locally, or alternatively act as a gateway or intermediary from a distant source.
The CPE 106 includes any equipment in the “customers' premises” (or other locations, whether local or remote to the distribution server 104) that can be accessed by a distribution server 104 or other network component.
Referring now to
The exemplary architecture 150 of
It will also be recognized, however, that the multiplexing operation(s) need not necessarily occur at the headend 150 (e.g., in the aforementioned MEM 162). For example, in one variant, at least a portion of the multiplexing is conducted at a BSA switching node or hub (see discussion of
Content (e.g., audio, video, data, files, software images, etc.) is provided in each downstream (in-band) channel associated with the relevant service group. To communicate with the headend or intermediary node (e.g., hub server), the CPE 106 may use the out-of-band (00B) or DOCSIS channels and associated protocols. The OCAP 1.0, 2.0, 3.0 (and subsequent) specification provides for exemplary networking protocols both downstream and upstream, although the invention is in no way limited to these approaches.
It will also be recognized that the multiple servers (broadcast, VOD, or otherwise) can be used, and disposed at two or more different locations if desired, such as being part of different server “farms”. These multiple servers can be used to feed one service group, or alternatively different service groups. In a simple architecture, a single server is used to feed one or more service groups. In another variant, multiple servers located at the same location are used to feed one or more service groups. In yet another variant, multiple servers disposed at different location are used to feed one or more service groups.
“Packetized” Networks—
While the foregoing network architectures described herein can (and in fact do) carry packetized content (e.g., IP over MPEG for high-speed data or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), they are often not optimized for such delivery. Hence, in accordance with another embodiment of the present invention, a “packet optimized” distribution network is used for carriage of the packet content (e.g., IPTV content).
Exemplary Network Architecture Using a Cable Modem—
Referring now to
Additionally, the architectures and systems discussed in previously referenced co-owned U.S. patent application Ser. No. 13/403,802 filed on Feb. 23, 2012 and entitled “APPARATUS AND METHODS FOR PROVIDING CONTENT TO AN IP-ENABLED DEVICE IN A CONTENT DISTRIBUTION NETWORK”, which is incorporated herein by reference in its entirety, may be utilized in conjunction with the present invention as well.
As illustrated in
The network switch 205 provides the received and decoded content to a plurality of linear transcoders 210 via e.g., a Gigabit Ethernet (GBE) or 10 Gigabit (10G) connection. The network switch 205 provides data to a source monitoring entity 204, which monitors the capacity of the switch.
The linear transcoders 210 receive the content from the network switch 205, and perform the necessary adaptive and/or non-adaptive rate steps to transcode and/or transrate content to any number of different desired formats such as e.g., Microsoft® Smooth Stream™ (MP4), Apple® Live Streaming™ (MP4), and Adobe Streaming®, for distribution of this content as a linear broadcast (multicast). As is well known, the exemplary MP4 format is a container format which allows, inter alia, combination of different multimedia streams (e.g., audio and video) into a single file. MP4 is a file extension for the container format defined in the Systems Part of the MPEG-4 standard (ISO 14496-1), incorporated herein by reference in its entirety. MP4 supports different kinds of multimedia content (multiple audio streams, video streams, subtitle streams, pictures, etc.) and advanced content (also referred to as “Rich Media” or “BIFS”) such as 2D and 3D graphics, user interactivity, and DVD-like menus. MP4 is a (linear) streamable format.
Although not illustrated, the linear transcoders 210 may perform the necessary rate steps to transcode/transrate the received content into any number of transport streams or streaming protocol, the foregoing being merely illustrative of the general concepts and of the common protocol used by typical IP-enabled client devices 207.
The transcoded and/or transrated content is provided to a content distribution network (CDN) origin server 202 using e.g., Hypertext Transport Protocol (HTTP) POST request methods, Real-Time Messaging Protocol (RTMP), or any other appropriate protocol. As will be discussed in greater detail below, the CDN origin server 202 stores the content to service requests from the IP-enabled devices 207.
One or more transcoders 210 may also be used to transcode the content to MP4 in MPEG-2 transport stream (TS) format in a non-rate adaptive manner. The non-rate adaptive format may be used in this case because the stream has a constant bit rate (CBR) at this stage. Utilization of the MPEG-2 TS container enables the MP4 content to be multicast to a plurality of devices on the network. Additionally, the MPEG-2 TS content may be delivered with advertisement or other “secondary” content inserted therein via one or more intermediary advertisement insertion mechanisms (not shown). Exemplary apparatus and methods for selection of secondary content to be inserted (e.g., via a “targeted” approach) are described in co-owned and 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”, U.S. patent application Ser. No. 12/284,757 filed on Sep. 24, 2008 and entitled “METHODS AND APPARATUS FOR USER-BASED TARGETED CONTENT DELIVERY”, which issued as U.S. Pat. No. 9,071,859 on Jun. 30, 2015, and U.S. patent application Ser. No. 12/766,433 filed on Apr. 23, 2010 and entitled “APPARATUS AND METHODS FOR DYNAMIC SECONDARY CONTENT AND DATA INSERTION AND DELIVERY”, each of which is incorporated herein by reference in its entirety, although other approaches may be used with equal success.
As shown in
Content and data are additionally provided from the MPEG-2 TS linear transcoders 210 to an acquisition server (A-server) 206. Then, via the A-server 206, the content is multicast to a plurality of other devices including those having IPTV server platform with digital rights management (e.g., the Microsoft MediaRoom® platform or MR DRM) options available. The content is provided from the A-server 206 to the switch for eventual delivery to consumers.
Another monitoring entity 208 is also provided as part of the exemplary architecture 200. In one embodiment, this entity 208 comprises a Cheetah Technologies® Stream Probe™ monitoring entity, although it will be recognized that other solutions or technologies may be employed with equal success. The monitoring entity in the exemplary embodiment provides analysis of IP and MPEG video coding layer attributes, in order to ensure network transmission trends and events are reported. In this manner, the network 200 can detect impairments and degradations in real-time. Generally, the monitoring entity 208 uses information fed back from the switch(es) 219. The monitoring entity 208 uses this information to monitor transcoded MPEG-4 content after it has been transcoded or down-sampled.
The illustrated network architecture 200 of
The cable modem 224 in turn requests the content (using an HTTP GET command) from a CDN edge cache 220 which is disposed at or near the edge of the network. In one variant, the modem 224 is placed at the switch 219, or elsewhere in the network based on operational considerations.
The edge cache 220 rests at the edge of the network, and is accessible via a bearer network (e.g., HFC network) access network interface 222. The HFC access network interface 222 in one exemplary embodiment comprises a web services interface managed by the content distribution network 200. The edge cache 220 requests content (using e.g., an HTTP GET command) from the origin server 202 further upstream in the network.
Alternatively or in addition, the edge cache 220 may store popular content for provision to the cable modem 224 and requesting device 207 more efficiently. In one variant, the methods and apparatus discussed in co-owned U.S. patent application Ser. No. 11/726,095 filed on Mar. 20, 2007 and entitled “METHOD AND APPARATUS FOR CONTENT DELIVERY AND REPLACEMENT IN A NETWORK”, which is incorporated herein by reference in its entirety, may be utilized for identifying and storing content at the network edge (such as at the edge cache 220). As discussed therein, a peer-to-peer architecture is utilized to provide acquisition, delivery, and reconstitution of content present within the network. The approach described therein has many potential benefits including, for example, the ability to push at least some network bandwidth consumption out to the edge of the network (e.g., hubs or other distribution nodes), thereby conserving bandwidth at the core of the network, the latter which can often be the most critical or bandwidth constrained portion of the system. Moreover, requests outside the MSO network are in some cases obviated, thereby conserving resources in this regard. Latency can also be reduced in some cases (e.g., where the network is over-subscribed), since the requested content is acquired and distributed locally versus having to come from the core (or a third-party content source routed through the core or other network infrastructure).
In another variant, the apparatus and methods of co-owned U.S. patent application Ser. No. 11/904,375 filed on Sep. 26, 2007 and entitled “METHODS AND APPARATUS FOR CONTENT CACHING IN A VIDEO NETWORK”, which issued as U.S. Pat. No. 8,561,116 on Oct. 15, 2103 and is incorporated herein in its entirety, may be utilized consistent with the present invention to provide “intelligent” caching and de-caching of content within the network using on-demand or other user-specified delivery mode. As discussed therein, the “intelligent” caching addresses issues relating to the trade-off between content storage space and transcoding/transrating/transcripting efficiencies within the system that occur as a result of trying to support a broad range of end-user device profiles and capabilities. By evaluating the demand for certain content elements and/or encoding formats and rates within the network, and identifying “duplications” of requests (or alternatively, the “proximity” of one request to another in content/encoding/bitrate/encryption space), a caching controller is able to dynamically balance caching of multiple versions of a content element (e.g., movie) and the need for “on the fly” transcoding/transrating/transcription and associated assets. In this fashion, greater efficiencies and economies of scale in operating the network can be realized while simultaneously supporting a wide range of devices. Thus, content which is requested more often can be “intelligently” stored at a content cache at the network edge, such as e.g., the edge cache 220 of
Referring back again to the cable modem 224 utilized herein the embodiment of
As shown in
The cable modem 224 further comprises a plurality of back end interfaces 260 for communication with one or more client devices 207 and CPE. Exemplary backend interfaces may include e.g., Wi-Fi, Bluetooth, Ethernet, IEEE 1394, Thunderbolt™, etc. In the exemplary implementation, a Wi-Fi (e.g., 802.11g) interface is used to communicate with an indigenous Wi-Fi interface in the client device, thereby affording the user significant mobility within/near the premises. The Wi-Fi interface also affords sufficient bandwidth so that the client device (e.g., tablet computer or other video rendering device) can render the streamed media linearly and without any artifact (e.g., pauses for buffering, jerkiness, etc.).
The cable modem 224 further includes a processor 256 and associated memory (e.g., RAM) 258. The processor 256 of the cable modem 224 is configured to run various applications, including for ensuring the security of the content transmitted via the cable modem 224. In one embodiment, the cable modem 224 runs also includes software to monitor outbound communications (the so-called origin or root server “pointer” software 254), and software to filter or block requests from the client devices 207, or conversely to block delivery of data or content from impermissible IP addresses (the so-called “filter” software 252). It will be appreciated by those of ordinary skill that while the foregoing pointer and filter software is shown and described as two separate software programs (e.g., middleware, or applications), the functionality of both can be combined into a single program if desired.
Moreover, the filter and pointer functions can be linked or dependent, such as where the filtering algorithm is only applied if the pointer application has not been invoked by the user/user device 207. For example, if a user is attempting to access content from the MSO origin server via an MSO-supplied application on the client device 207, selection of a content element via say a menu of the MSO application would invoke the pointer routine of the modem 224 to generate an appropriate pointer (e.g., IP address) within the permissible address range/space. The “pedigree” of this address is in one variant presumed, and hence filtration would not be required. However, contrast the foregoing with the case where the user utilizes an indigenous or non-MSO application (e.g., a third-party browser) on the client 207 to select a URL or IP address; this was not generated by the MSO application and does not invoke the pointer routine, and hence it's pedigree is unknown. Under such cases, the filtering routine would automatically be invoked (and would block any attempted accesses outside the permissible address range/space). Identification of MSO-versus non-MSO application/pointer origination can readily be accomplished, such as for example via embedding data within the request that uniquely identifies the MSO-application as “authentic”, and/or logic which alerts the filter routine that the pointer was not used in formulating the communication.
Alternatively, the filter routine can simply be configured to filter every request as to its address range/space, irrespective of origin of the request and/or use of the pointer.
The root server pointer program 254 provides the modem with appropriate information to ensure that communication from the cable modem 224 is only performed with acceptable entities within the MSO network (e.g., the appropriate origin (root) or distribution server(s)). In one exemplary embodiment, the cable modem 224 only points at the root server or a CDN origin server 202, and the necessary infrastructure and entities for providing content to IP-enabled client devices 207 in communication therewith (which includes the origin server 202, edge cache 220, DNS server, etc.). This is accomplished in one embodiment by defining a range of contiguous IP address space (which may also be distributed across multiple data centers) with which the modem 224 must communicate. In this manner, when a communication is to be sent, the root server pointer 254 provides the destination address within the known (permissible) address space for effecting the desired action (e.g., obtaining a program guide or content). Therefore, the cable modem 224 will only enable communication with devices having an IP address in the defined space. For example, the CDN root server 202, the edge cache 220, application servers, etc. which may be needed for delivery of content to the IP-enabled client devices 207 are each given an IP address within the defined address space. Additionally, other entities required for cable modem 224 functioning may be given IP addresses within the defined space (i.e., management entities). In one variant, the permissible address range is static, and hence communications needed to update the range are largely if not totally obviated, and the modem 224 can be pre-programmed for these addresses if desired.
In another embodiment, the root server pointer application 254 is given a list of appropriate IP addresses corresponding to those entities with which communication is permitted, which is non-contiguous. According to this embodiment, the network 200 does not need to create a contiguous IP address space; updated IP addresses as new entities are added, replaced, etc. are provided to the cable modem 224 periodically or as needed.
The filter program 252 comprises a set of instructions which, when run on the cable modem 224, block communication from a client device 207 to entities other than the designated server entities of the network 200. The filter 252 may also be configured to block “inbound” communications (i.e., from the network inbound to the premises) that originate from non-approved IP addresses. In one embodiment, the filter 252 is configured to block traffic originated by the client device to address spaces other than those permissible within the delivery network (i.e., the origin server 202, edge cache 220, etc.). This may be accomplished using the previously discussed contiguous IP address spaces, or the list of known addresses.
Therefore, when the client device 207 connects to modem 224, it is permitted to access all the services on the network necessary to obtain an IP address for itself (if required), access the domain name system (DNS) server (which is within the predetermined specific IP address space), etc. In addition, the cable modem 224 can resolve the host name, URL, CDN, etc. and can access content by logging onto the application server, obtaining the UI (e.g., navigator or EPG if not already present on the client device), and accessing the root server to populate the EPG and allow the user to select content.
However, if the client device 207 attempts an “out of range” communication (e.g., the user starts up a browser application and tries to access a URL that corresponds to an IP address other than within the predefined IP address space), the communication will fail. That is, traffic/packets sent to addresses other than those approved addresses are blocked at the cable modem 224 via the filter 252. The filter 252 also optionally acts as both an inbound filter, hence communications received from non-permissible IP addresses will not be passed to the client device 207.
In addition, the filter 252 may serve as a DNS block. Accordingly, the filter 252 in such cases denies access to all domains or URLs (e.g., www.xyz.net) other than those specified by the network. The DNS block may be used in conjunction with or in place of the IP address block discussed above.
As an alternate or additional protection mechanism, the DNS server to which communication is permitted (e.g., is within the permissible range of addresses) may be set up to only resolve IP addresses to services needed to deliver the content to the IP-enabled devices 207. Hence, even if an impermissible request escapes the filter 252, the server will not resolve the address.
In certain use cases (such as e.g., where a MSO network user or subscriber is using the client device 207 to also access broadband data services via a third-party carrier or service provider) the foregoing mechanisms for ensuring protection of communications between the network 200 and client devices 207 may require that a client device 207 requesting access to content disconnect from a first wireless service set identifier (SSID) associated with the third-party carrier, and switch to that of the cable modem 224 (and hence the MSO network). When the client device 207 switches to the SSID of the cable modem 224, the only functions which may be performed on that device 207 are those of obtaining content as discussed above.
For instance, if a user seeks access to the herein-described MSO-based content delivery services via Wi-Fi on an iPad where the device is currently associated to a non-MSO Wi-Fi access point SSID, the client must access the cable modem SSID (such as by starting a content request application associated with the MSO which uses the cable modem SSID, and accessing the MSO network via the cable modem's 224 SSID port, or alternatively reconfiguring an already running application to access the cable modem SSID, such as by manually entering or selecting that SSID in a drop down menu).
Exemplary Network Architecture Using a Media Server—
Referring now to
Although not shown, the MSO network portion of the exemplary network 300 contains apparatus similar to those discussed above with respect to the network 200 of
Although not illustrated, an edge cache may be positioned at the edge of the MSO network. The edge cache may be utilized to request content (using e.g., an HTTP GET command) from the origin server 202 further upstream in the network. This allows content to be pushed to the edge of the network (i.e., to the cache) for faster and more efficient delivery therefrom.
The origin (root) server 202 and/or edge cache are accessible via a bearer network (e.g., HFC network) access network interface. The HFC access network interface in one exemplary embodiment comprises a web services interface managed by an MSO.
In the network 300 architecture of
The media server 306 may further comprise one or more interfaces 324 for communicating to client devices 207 (not shown), for example to enable operation such as that described previously with respect to
Additionally, the media server modem 306 comprises a processor 326 and associated memory such as RAM 328. The processor is configured to run a root server pointer application 330, which is adapted to enable the media server modem 306 to only communicate with particular entities of the managed network (including e.g., the origin/root server 202).
As discussed above with respect to
The processor 326 is further configured to run a filtering program 332, which filters communications received thereat from either the client device 207 (outbound) or entities of the managed network (inbound). The filter application 332 blocks communication from a client device 207 to entities other than the designated server entities of the network using the previously referenced contiguous address spaces or the list of approved IP addresses; i.e., the filter 332 blocks traffic to address spaces other than those known to the system as identified as being permissible within the delivery network (i.e., the origin server 202, edge cache 220, etc.). Similar to the filter application of the cable modem 224 of
Notwithstanding, the client device 207 of the embodiment of
The processor 326 is in the illustrated embodiment configured to run a publication/discovery program 334, which enables the client device to discover the modem 306 (which is acting as a client of the access point 304), and/or otherwise facilitates communication therewith. A myriad of approaches for providing a predetermined mechanism for the client device (or client application) to discover the gateway, and use it for external communication, may be utilized. In one embodiment, a standards-based solution such as universal plug and play (UPnP), Zeroconf, etc. may be used. Alternatively, a broadcast or multicast within the home may be utilized to discover the gateway. Each of the foregoing solutions may be implemented without requiring the incumbent AP to natively support the discovery technology. Rather, the AP merely passes the traffic necessary for the above-disclosed protocols to function (which in the case of the standards-based protocols, the AP would indigenously be configured to perform).
Accordingly, in one example, a fiber optic drop (e.g., FTTH, or FIOS) is run into a customer's home to provide high speed data service therein. The media server modem 306 registers as a client of the access point associated with the optical drop; the modem 306 therefore receives an IP address from the access point 304. When the client device 207 runs an application to access the modem (and content at the managed network), the client device 207 discovers (or is discovered by) the media server modem 306. The client device 207 knows the IP address or port of the modem 306, and communicates its requests (e.g., for program guide, content, etc.) to the modem 306 via the AP 304. The media server modem 306 can then facilitate serving these requests via its connection to the MSO network (such as via a DOCSIS or WiMAX connection thereto).
In another embodiment, the “content only” services provided by the MSO described above (i.e., no high speed data) are provided via a wireless broadband or WAN interface, such as a WiMAX (e.g., 802.16e or m) compliant interface. In this fashion, new subscribers to the MSO network need not have any extant or installed cable or fiber “drop” into their premises; the MSO merely provides the new subscriber with a WAN transceiver (base station), which can include a WLAN or similar interface as well to facilitate quick establishment of a completely wireless content delivery system within the subscriber's premises. The installed WAN modem is configured to allow access to only the designated IP address space or list (as previously described). Either the architecture of
Exemplary Network Architecture Using a Network Gateway—
In yet another embodiment, an architecture 400 of
Although not illustrated, an edge cache may be positioned at the edge of the MSO network. The edge cache may be utilized to request content (using e.g., an HTTP GET command) from the origin server 202 further upstream in the network. This allows content to be pushed to the edge of the network (i.e., to the cache) for faster and more efficient delivery therefrom.
The root server 202 and/or edge cache are accessible via a bearer network (e.g., HFC network) access network interface. The HFC access network interface in one exemplary embodiment comprises a web services interface managed by an MSO.
In the embodiment of
In one such variant, a cellular service provider (CSP) with an LTE (Long Term Evolution) or LTE-A infrastructure for providing high speed mobile data service to its subscribers is the third-party network 404; subscribers of this network 404 use their smartphones or LTE-enabled tablets as video rendering devices for the MSO-originated content. In one implementation, the methods and apparatus of co-owned U.S. patent application Ser. No. 11/258,229 filed Oct. 24, 2005 entitled “METHOD AND APPARATUS FOR ON-DEMAND CONTENT TRANSMISSION AND CONTROL OVER NETWORKS”, incorporated herein by reference in its entirety, are used to provide the cross-network functionality, although other approaches may be used with equal success. The MSO origin or root server 202 exists within the permissible IP address space (or list) as previously described. In one implementation, the user device (e.g., smartphone or tablet) includes an MSO application which is configured to, when run on the user device, perform the pointing and filtering functions described supra, such that the user device can only access the requested MSO streamed (e.g., MP4) content after proper login and authentication, and not other services.
In another implementation, the inter-network gateway 402 (described in greater detail below) is equipped to perform these pointing and filtering functions.
The content/playlist in the embodiment of
The embodiment of
In one exemplary configuration, the gateway apparatus 402 of
In yet another embodiment, the apparatus and methods of co-owned, co-pending U.S. patent application Ser. No. 12/480,597 filed on Jun. 8, 2009 and entitled “MEDIA BRIDGE APPARATUS AND METHODS”, which is incorporated herein by reference in its entirety, may be utilized. As discussed therein, an apparatus (such as the gateway 402, cable modem 224, and/or media server modem 306) may, in addition to providing content to a plurality of devices (including IP-enabled devices 207) in communication therewith, act as a connection between a portable media device (PMD) such as an MP3 player and a user's home network. This bridging apparatus may be used, for example, to convert content stored on the PMD to a format capable of being presented on a user's set-top box or other client device. Control of the presentation is also provided by the bridging apparatus.
Secure Content Delivery—
Various mechanisms for ensuring the security of content transmitted utilizing the methods and apparatus of the present invention are disclosed in previously referenced U.S. patent application Ser. No. 13/403,802 entitled “APPARATUS AND METHODS FOR PROVIDING CONTENT TO AN IP-ENABLED DEVICE IN A CONTENT DISTRIBUTION NETWORK” filed concurrently herewith.
As discussed with respect to one embodiment therein, an entity associated with the MSO determines whether the requesting user is permitted to access the content. The process by which it is determined whether a user may access content includes: (i) authenticating the user as a subscriber to the MSO, and (ii) determining whether the subscriber's service/subscription level permits viewing of the requested content (and optionally one or more use restrictions).
In one variant, the user is authenticated by requiring him/her to establish a login identity and password, and/or assigning the user a globally unique identifier (GUID). For example, the user's MAC address or IP address may be stored at an MSO entity, and when the user requests content, the user must log into the MSO; the relevant information is retrieved and compared to information that the user has provided in their login. If valid login information is entered (i.e., the information provided matches the stored information for that user GUID), then a session is created between the MSO and user permitting the transmission of content there between.
In another variant, the third party (unmanaged network) service provider and MSO accounts for a particular user may be linked or federated such that a trust relationship is established between them and utilized to verify subscriber information. One exemplary implementation of this arrangement is additionally discussed in co-owned and co-pending U.S. patent application Ser. No. 12/834,801 entitled “APPARATUS AND METHODS FOR CONTENT DELIVERY AND MESSAGE EXCHANGE ACROSS MULTIPLE CONTENT DELIVERY NETWORKS” and filed on Jul. 12, 2010, which is incorporated herein by reference in its entirety.
The determination of whether the subscriber's service/subscription level permits viewing of the requested content may include determining a subscription level of the user (or whether a user has provided consideration to the MSO for gaining access to the content, such as on a pay-per basis), and applying an appropriate filter to the content which can be requested thereby.
In addition, it may also be determined whether the requesting device is within a home network or other premises serviced by the MSO. This may be verified based on the IP or MAC address of the entity used to access the MSO network (such as e.g., the cable modem 224, media server modem 306, and/or gateway 402). Each of the herein-referenced authentication/entitlements checks are discussed in greater detail in the previously referenced U.S. patent application Ser. No. 13/403,802 entitled “APPARATUS AND METHODS FOR PROVIDING CONTENT TO AN IP-ENABLED DEVICE IN A CONTENT DISTRIBUTION NETWORK”.
In another embodiment, the aforementioned entitlements check to ensure that the requesting device is behind a recognized cable modem or Wi-Fi hotspot is performed according to the methods and apparatus discussed in co-owned U.S. patent application Ser. No. 12/536,724 filed on Aug. 6, 2009 and entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER A NETWORK”, which issued as U.S. Pat. No. 8,341,242 on Dec. 15, 2012 and is incorporated herein by reference in its entirety. As discussed therein, entitlement to content residing on a server is determined by e.g., the computing device operated by a subscriber generating a request for access to a requested content residing on a content access provider server. The subscriber has an account with a multi-channel video program distributor (MVPD) and the account comprises subscription information indicative of the services provided by the MVPD to the subscriber. The content request is received by the content access provider and forwarded to an entitlements server. The entitlements server determines whether the subscriber is entitled to receive the requested content based on the subscription information and sends an access granted message to the content access provider server when the subscriber is entitled to receive the requested content.
In another embodiment, entitlements are determined via a geographic location of an MSO-managed access point (e.g., public Wi-Fi or WiMAX hotspot).
With respect to the transmitted content itself, symmetric or asymmetric encryption techniques, such as e.g., Advanced Encryption Standard (AES) encryption, may be utilized to protect the content. In one embodiment, a single key is used for both encryption and decryption (symmetric-key encryption), although it will be appreciated that non-symmetric or asymmetric encryption techniques may be used as well. According to this embodiment, the content encryption/decryption key is generated and provided to the origin server as discussed in the previously referenced U.S. patent application Ser. No. 13/403,802 entitled “APPARATUS AND METHODS FOR PROVIDING CONTENT TO AN IP-ENABLED DEVICE IN A CONTENT DISTRIBUTION NETWORK”. A URL to the content encryption/decryption key is provided to client device 207 upon request and authentication/authorization thereof.
In order to obtain the encryption/decryption key, in one embodiment, when the client device 207 logs in and is authenticated (see login as discussed above) to the access network, it receives program guide data and an encrypted cookie. In order to request the key, the device 207 presents the server entity (to which the content request is transmitted) with the previously received cookie (after it is decrypted). The key server can then determine whether the cookie presented is appropriate for the requesting device, such as by cross-checking the cookie-device pair against stored information and once authorized, provide the key thereto. Once the AES key is obtained in the clear, the client device 207 may then use the key to decrypt and play the content fragments which correspond to those listed in the playlist of the requested content.
In yet another embodiment, content may be secured using the methods and apparatus of co-owned, co-pending U.S. patent application Ser. No. 12/901,417 filed on Oct. 8, 2010 and entitled “APPARATUS AND METHODS FOR ENFORCING CONTENT PROTECTION RULES DURING DATA TRANSFER BETWEEN DEVICES”. As discussed therein, a content server (such as e.g., the origin server, edge cache, or other entity of the herein described network architectures) is utilized to determine not only copy protection rights (such as those utilized by the well known Digital Transmission Content Protection-Internet Protocol (DTCP-IP)), but also the rights of specific requesting subscribers to access, use, copy, and/or distribute content. These rules are provided to, and implemented by, a subscriber device requesting specific content (such as e.g. an IP-enabled client device 207, cable modem 224, media server 306, and/or gateway 402). The subscriber device implements the protection rules when determining how the content may be used, and whether the content may be provided to subsequent devices.
In one further embodiment, the subscriber device is configured to enable content to be provided to second devices (such as other devices within the home network, including e.g., IP-enabled client devices 207) consistent with the protection rules by generating a mobile or transferrable version of content, and providing this version to the requesting device. To avoid having multiple available versions of the same content existing at both the (source) subscriber device and the target device to which the subscriber transferred the content, the subscriber device employs in one variant a mechanism for marking the original content stored thereon so that it is unavailable for use or further transfer while the mobile version exists at the target device (i.e., so-called “check out”). In this manner, there is at any one time only one available or useable version of the content for the given subscriber. The subscriber may reinstate the original version of the content at the subscriber device (i.e., so-called “check in”) in order for it to be used thereon, or to be transferred to yet another device. Reinstatement is accomplished in one implementation by deleting the version existing at the first target device, and transmitting a signal or message back to the subscriber device indicating that the copy has been deleted. This transmission then causes the subscriber device to “unblock” the original version of the content as stored thereon.
The client device responsible for implementing and/or enforcing the protection rules (e.g., the cable modem 224, media server modem 306, and/or gateway 402) may also work within a premises network or trusted domain for media content, thereby allowing a subscriber total mobility in the premises network. For example, media content from the client device may be accessed via extant networks (e.g., MoCA, Ethernet, Wi-Fi, or PAN) for distribution to any STB, PC, mobile device, or other PMD in the network. The client device may also utilize the existing premises network to allow other devices to share media content with it.
Methodology—
Referring now to
Once the login is complete and the user's identity verified (such as by login ID, password, etc.), a request to access a content list or guide data may be manually or automatically sent from the device 207 to the cable modem 224 per step 504.
At step 506, the cable modem 224 provides the destination address(es) of the communication to provide proper routing and to ensure that it is within a set of known IP addresses and/or within a pre-defined contiguous IP address space. In the present example, the provided address would correlate to a guide data server (which may be the origin server, or another server within the network) that is within the permissible address range/space.
At step 508, filtration is optionally applied based on, e.g., whether the request is generated by the MSO application (and the pointer routine is invoked to provide the address). See discussion of various embodiments of filtering logic provided supra.
Assuming that the communication is not filtered, it is sent to the prescribed address to obtain the guide data per step 510. Upon receipt of the request, a check is performed (step 512) to ensure that the requesting device is authorized or entitled to receive content. In one embodiment, one or more of the aforementioned authorization or entitlement checks may be utilized. For example, it may be determined that the client device 207 is registered to a user of the system, that the device 207 is behind an MSO-managed cable modem 224, and/or that the user associated to the device 207 is a subscriber to the appropriate services of the MSO. This is accomplished using various combinations of IP address (i.e., of the cable modem 224), the MAC of the cable modem and/or client device 207, and the user login data (e.g., login ID and password). An “entitlements” database may also be accessed based on the foregoing information to determine if the user is entitled to receive the requested content/services (here, only guide data). A further processing step may also be applied at this level to filter the MSO-managed content, so as to identify only that content to which the subscriber is authorized to have access. If the user/device is not authenticated/authorized/entitled to access the guide data (and subsequently content), an error message will be presented to the user/device.
Assuming proper authentication, per step 512, an electronic program guide (EPG) or other data reflecting available content is provided to the requesting device 207 via the cable modem 224 (step 514). As noted above, the guide data may be filtered to take into account the specific authorization/entitlements of the requesting client device 207 or user.
Per step 516, a user selects one or more content elements from the provided guide or index, thereby causing a request for that particular one or more content elements to be transmitted to the cable modem 224 (for eventual communication to the origin server or edge cache) per step 518. The cable modem assigns a permissible address to the request (step 520), and filters the communication if required (step 522).
At step 524, it is determined whether the requesting device 207 or user is authorized to receive the requested content. However, it is appreciated that the present step may be obviated in favor of providing the filtered guide data discussed above (or otherwise verifying the user's entitlement to access the requested content as part of an earlier step). If the device or user is not authorized, an error message is provided thereto (step 526).
An authorized client device 207 will receive the playlist of URL addresses for the content segments associated with the requested content at step 528. It is noted that at this step the device may further receive a URL to the content decryption key (as discussed elsewhere herein). In response to receiving the playlist, the device 207 uses the playlist URLs to request the various content segments needed to render the desired content (step 530). The URL requests are received and optionally filtered by the cable modem 224. If the requests are addressed to unknown/unauthorized recipients, they are blocked.
Appropriately addressed URL requests are transmitted to the edge cache or origin server and the requested content provided to the device per step 532. Per step 534, each of the URLs in the content playlist are requested and provided. Although illustrated as having an optional filtering step at each URL request, it is appreciated that the system may implement a single filtering step at the first URL request and forego subsequent filtering.
Per step 536, the decryption key is obtained from its designated URL, and the key used to decrypt the received (encrypted) segments (step 538). The content is then rendered on the client device using the decrypted segments and playlist data (step 540).
It will be appreciated that the foregoing methodology may be adapted for use with different configurations, such as where the client device 207 includes provision for assigning permissible addresses to the requests it issues. For example, in one variant, the client device includes an MSO application which is configured to obtain or generate a permissible IP address, and associate this with its content request forwarded to the modem 224. The list or range of permissible addresses obtained by the MSO application may be coded into the application, and/or obtained at startup by the application accessing a dedicated network entity tasked with providing the application a current list/range of addresses (e.g., after user device authentication and user login). The received request may also be optionally filtered at the modem 224 (i.e., to ensure that the address is permissible based on the modem's available information), or alternatively the filtering may be obviated by the cable modem determining that the request was originated (and hence the address assigned) by the “authorized” MSO application (such as via the request carrying the aforementioned MSO application identifying information), and hence its pedigree is assumed known.
It will further be appreciated that the login and guide/content access process described above may be accomplished in any number of different ways. For instance, in one variant, the MSO-provided application on the client 207 is started by the user, and the application immediately requests login information (e.g., user ID, password) before any further actions can be taken with respect to the application. If the login information is successfully entered, the user is given access to the GUI/menu structure of the application, whereby the user can perform various actions such as selecting delivery of a new or updated program guide, select content elements for delivery, etc. At this stage, however, the user has not been authenticated (i.e., by user ID/password, IP address, MAC, etc.) to the MSO network, but rather only to the MSO application resident on the client 207. Once the user selects an action (e.g., deliver Movie X) via the GUI, the proper request is formulated by the application layer, including accessing or using the pointer routine of the modem 224 to provide a permissible IP address at which to obtain the content. However, before content can be delivered, this request must first be authenticated within the MSO network, such as by sending the request (including the user login data) to the appropriate network entity, which may be the origin/CDN server itself, or an MSO security server. In one variant, since the MSO-provided application originated the request, and the MSO-provided modem 224 (pointer routine) provided the IP address(es) for the request, the request is presumed authentic, and no filtering is invoked. The request is then sent from the modem 224 to the target address provided by the pointer, and the request authenticated (i.e., by user login, IP, MAC, subscriber privilege/entitlement, etc.), and upon successful authentication, the content is prepared for delivery as previously discussed herein (i.e., segmented, encrypted, and a playlist prepared).
In another variant, the user initiates the MSO-provided application on the client 207, and is again presented with a login screen. However, at this stage, the login information is transmitted to a designated login server or other entity within the MSO network via the modem 224, the address thereof provided by the pointer routine on the modem 224. The client device application knows the address/port of the modem 224, and forwards the user login data on to the modem 224 for direction to the address selected by the pointer routine. Further interaction with the MSO application on the client is at this point frustrated until the modem 224 receives authorization from the network as to the user's ability to access the MSO network functionality (i.e., based on a verification of the login data, IP address or MAC, entitlements, etc.). Hence, in contrast to the foregoing variant, the present variant is “network centric” for all authentication functionality.
Alternatively, the login to the network (i.e., IP or MAC address authentication, etc.) may be performed upon starting the MSO application; this may be seamless to the user, such as where the MSO application is configured to send its appropriate verification data (IP address, MAC, etc.) to the modem 306, which sends this data according to the appropriate protocol to an address (or multiple addresses) specified by the modem's pointer routine. Once the modem/client has been verified by the network, it is directed to obtain updated guide data from the network. The guide data is forwarded to the client, and populates the menus of the MSO application. The user then can view the guide data, and if interested, select content for delivery. Once the content is selected, the user is then required to login using e.g., user ID and password. This login information is forwarded to a server within the prescribed address space of the MSO network, which verifies the login. At that point, the user request is then forwarded to the appropriate origin or CDN server for delivery of the content.
In yet another variant, the login is accomplished by the user via a non-MSO application (e.g., web browser). The user enters a known URL (e.g., www.twc.com/smart-tv or the like) into their browser, and that request is forwarded to the modem 224 which then applies the filter routine to determine if the request is valid (the client/request may also be given access to other permissible entities as required to resolve the address, such as DNS). The filter may be invoked for instance for every request, or by the absence of the aforementioned MSO-specific application ID data present in the request. The relevant MSO network web server at the address then serves the modem 224 the login web page for the service, and the foregoing protocols regarding login and authentication are then implemented to authenticate the user (login ID/password), their entitlements, and the device (e.g., IP address, MAC, etc.) as desired. This approach has the advantage of obviating an MSO-specific application being loaded onto the client, yet still limits the user's web browsing activities (via the MSO modem 224) to those necessary to invoke streaming services as described herein, and no others (since non-permissible addresses/URLs will not be passed upstream or resolved).
Per step 602 of the method 600, the media server (such as media server modem 306 of
Next, per step 604, the media server modem 306 is “discovered” in the premises network by the client 207. In one embodiment, this may be accomplished when the user logs into the software application associated with the MSO services (i.e., MSO “app”) running on the client device 207. That is, the software application may cause a service or discovery request to be sent to the IP address of the media server modem 306 via the third-party access point 304. It is noted that in this respect, unlike the methodology of
Once the media server modem 306 has been discovered as an accessible resource of the access point (premises network), the user logs in. As noted above, depending on configuration, the user may log into the MSO application resident on the client 207 alone, or also to the MSO network entity managing logins (the latter in one variant obviating further subsequent login activity). As yet another alternative, the user may simply start the MSO application, and access the menu structures, and be required to log in only when content is selected.
Under any of the foregoing scenarios, the user is given access to the relevant functionality of the MSO application, and the user (via the client device 207) requests access to content and/or a program guide, such as via a menu or icon selection in the MSO-provided application, per step 606. This may include for example an automatic request for a guide update, so that the user has the most current available program listing without further action. If not already performed, login and authentication to the MSO network (versus merely the client device application) may occur at this stage; i.e., as part of the request. In one scenario, the content/guide request from the client 207 is received at the media server modem 306, where the pointer routine adds the necessary addressing information to enable the request to be routed appropriately within the permissible address range/space. The request is then transmitted to the edge cache or origin server within the MSO infrastructure, along with any required network login/authentication entity. Filtering may also optionally be applied as discussed previously herein.
After appropriate authentication/authorization, the requested content or guide data is provided to the device 207 at step 608 per the previously described mechanisms (e.g., requesting and retrieving the relevant playlist (steps 610 and 612), encrypted content segments (step 616), and decryption key in the case of content, or merely obtaining the guide data “in the clear”). This process is repeated for additional content requests (step 618).
It is noted that the methods for providing content to an IP-enabled device 207 in the architecture of
Although discussed herein in an exemplary implementation as a cable modem having an embedded gateway, it is recognized that the concepts discussed herein are equally applicable in the instance the premises device (e.g., cable modem) simply comprises an Ethernet or other network bridge (which does not contain any intelligence or application level functionality). In this instance, the gateway functionality described herein is applicable to the application level intelligence performed by a logically (and/or physically) separate gateway entity or other process. Such separation advantageously enables the gateway to be used for different WAN access technologies (fiber, DSL, etc.), yet may also necessitate additional cost, space and power requirements, service calls, etc.
It will be recognized that while certain aspects of the invention are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the invention, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the invention disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the invention as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the invention. The foregoing description is of the best mode presently contemplated of carrying out the invention. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the invention. The scope of the invention should be determined with reference to the claims.
This application is a divisional of and claims priority to co-owned U.S. patent application Ser. No. 15/243,353 of the same title filed Aug. 22, 2016, now issued as U.S. Pat. No. 10,389,853 on Aug. 20, 2019, which is a divisional of and claims priority to co-owned U.S. patent application Ser. No. 13/403,814 of the same title filed Feb. 23, 2012, issued as U.S. Pat. No. 9,426,123 on Aug. 23, 2016, each of the foregoing incorporated herein by reference in its entirety. In addition, this application is related to co-owned U.S. patent application Ser. No. 13/403,802 filed on Feb. 23, 2012 and entitled “APPARATUS AND METHODS FOR PROVIDING CONTENT TO AN IP-ENABLED DEVICE IN A CONTENT DISTRIBUTION NETWORK”, which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4677501 | Saltzman et al. | Jun 1987 | A |
| 5410344 | Graves et al. | Apr 1995 | A |
| 5606726 | Yoshinobu | Feb 1997 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5790935 | Payton | Aug 1998 | A |
| 5828420 | Marshall et al. | Oct 1998 | A |
| 5999525 | Krishnaswamy et al. | Dec 1999 | A |
| 6016316 | Moura et al. | Jan 2000 | A |
| 6026211 | Nakamura et al. | Feb 2000 | A |
| 6212562 | Huang | Apr 2001 | B1 |
| 6233389 | Barton et al. | May 2001 | B1 |
| 6442332 | Knudson et al. | Aug 2002 | B1 |
| 6581207 | Sumita et al. | Jun 2003 | B1 |
| 6609253 | Swix et al. | Aug 2003 | B1 |
| 6642938 | Gilboy | Nov 2003 | B1 |
| 6642939 | Vallone et al. | Nov 2003 | B1 |
| 6754904 | Cooper et al. | Jun 2004 | B1 |
| 6769127 | Bonomi et al. | Jul 2004 | B1 |
| 6774926 | Ellis et al. | Aug 2004 | B1 |
| 6917614 | Laubach et al. | Jul 2005 | B1 |
| 6917641 | Kotzin et al. | Jul 2005 | B2 |
| 6931657 | Marsh | Aug 2005 | B1 |
| 7073189 | McElhatten et al. | Jul 2006 | B2 |
| 7167895 | Connelly | Jan 2007 | B1 |
| 7174126 | McElhatten et al. | Feb 2007 | B2 |
| 7185355 | Ellis et al. | Feb 2007 | B1 |
| 7197708 | Frendo et al. | Mar 2007 | B1 |
| 7240359 | Sie et al. | Jul 2007 | B1 |
| 7325043 | Rosenberg et al. | Jan 2008 | B1 |
| 7421725 | Hane et al. | Sep 2008 | B2 |
| 7457520 | Rosetti et al. | Nov 2008 | B2 |
| 7571452 | Gutta | Aug 2009 | B2 |
| 7592912 | Hasek et al. | Sep 2009 | B2 |
| 7602820 | Helms et al. | Oct 2009 | B2 |
| 7657907 | Fennan et al. | Feb 2010 | B2 |
| 7763360 | Paul et al. | Jul 2010 | B2 |
| 7937725 | Schaffer et al. | May 2011 | B1 |
| 7954131 | Cholas et al. | May 2011 | B2 |
| 8024762 | Britt | Sep 2011 | B2 |
| 8073460 | Scofield et al. | Dec 2011 | B1 |
| 8078696 | Lajoie et al. | Dec 2011 | B2 |
| 8087050 | Ellis et al. | Dec 2011 | B2 |
| 8090014 | Cheung et al. | Jan 2012 | B2 |
| 8090104 | Wajs et al. | Jan 2012 | B2 |
| 8095610 | Gould et al. | Jan 2012 | B2 |
| 8099757 | Riedl et al. | Jan 2012 | B2 |
| 8151294 | Carlucci et al. | Apr 2012 | B2 |
| 8181209 | Hasek et al. | May 2012 | B2 |
| 8196201 | Repasi et al. | Jun 2012 | B2 |
| 8214256 | Riedl et al. | Jul 2012 | B2 |
| 8280833 | Miltonberger et al. | Oct 2012 | B2 |
| 8280982 | La et al. | Oct 2012 | B2 |
| 8341242 | Dillon et al. | Dec 2012 | B2 |
| 8396055 | Patel et al. | Mar 2013 | B2 |
| 8472371 | Bari et al. | Jun 2013 | B1 |
| 8516529 | Lajoie et al. | Aug 2013 | B2 |
| 8561103 | Begeja et al. | Oct 2013 | B2 |
| 8561116 | Hasek | Oct 2013 | B2 |
| 8615573 | Walsh et al. | Dec 2013 | B1 |
| 8776101 | Donoghue et al. | Jul 2014 | B2 |
| 8782194 | Eyal et al. | Jul 2014 | B2 |
| 8813122 | Montie et al. | Aug 2014 | B1 |
| 8838149 | Hasek | Sep 2014 | B2 |
| 9015736 | Cordray et al. | Apr 2015 | B2 |
| 9021566 | Panayotopoulos et al. | Apr 2015 | B1 |
| 9043431 | Chappell et al. | May 2015 | B2 |
| 9049344 | Savoor et al. | Jun 2015 | B2 |
| 9215423 | Kimble et al. | Dec 2015 | B2 |
| 9264743 | Diep | Feb 2016 | B1 |
| 9357247 | Cronk et al. | May 2016 | B2 |
| 9380329 | Donoghue et al. | Jun 2016 | B2 |
| 9426123 | Pfeffer et al. | Aug 2016 | B2 |
| 9473730 | Roy et al. | Oct 2016 | B1 |
| 9832425 | Barnes et al. | Nov 2017 | B2 |
| 9858396 | Nair | Jan 2018 | B2 |
| 9906838 | Cronk et al. | Feb 2018 | B2 |
| 9992520 | Williamson et al. | Jun 2018 | B2 |
| 10116676 | Roosenraad et al. | Oct 2018 | B2 |
| 10313755 | Kimble et al. | Jun 2019 | B2 |
| 10389853 | Pfeffer et al. | Aug 2019 | B2 |
| 20010047516 | Swain et al. | Nov 2001 | A1 |
| 20020042914 | Walker et al. | Apr 2002 | A1 |
| 20020053076 | Landesmann | May 2002 | A1 |
| 20020056087 | Berezowski et al. | May 2002 | A1 |
| 20020075805 | Gupta | Jun 2002 | A1 |
| 20020083451 | Gill et al. | Jun 2002 | A1 |
| 20020104087 | Schaffer et al. | Aug 2002 | A1 |
| 20020129368 | Schlack et al. | Sep 2002 | A1 |
| 20020133815 | Mizutome et al. | Sep 2002 | A1 |
| 20020152474 | Dudkiewicz | Oct 2002 | A1 |
| 20020174430 | Ellis et al. | Nov 2002 | A1 |
| 20020174433 | Baumgartner et al. | Nov 2002 | A1 |
| 20020188744 | Mani | Dec 2002 | A1 |
| 20020188947 | Wang et al. | Dec 2002 | A1 |
| 20020188949 | Wang et al. | Dec 2002 | A1 |
| 20020191950 | Wang | Dec 2002 | A1 |
| 20020199194 | Ali | Dec 2002 | A1 |
| 20030005457 | Faibish et al. | Jan 2003 | A1 |
| 20030028451 | Ananian | Feb 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030061618 | Horiuchi et al. | Mar 2003 | A1 |
| 20030066068 | Gutta et al. | Apr 2003 | A1 |
| 20030086422 | Klinker et al. | May 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030093794 | Thomas et al. | May 2003 | A1 |
| 20030120817 | Ott et al. | Jun 2003 | A1 |
| 20030121041 | Mineyama | Jun 2003 | A1 |
| 20030123465 | Donahue | Jul 2003 | A1 |
| 20040003402 | McKenna, Jr. | Jan 2004 | A1 |
| 20040015986 | Carver et al. | Jan 2004 | A1 |
| 20040038689 | Holur | Feb 2004 | A1 |
| 20040073915 | Dureau | Apr 2004 | A1 |
| 20040073924 | Pendakur | Apr 2004 | A1 |
| 20040083177 | Chen et al. | Apr 2004 | A1 |
| 20040117838 | Karaoguz et al. | Jun 2004 | A1 |
| 20040117855 | Nakamura | Jun 2004 | A1 |
| 20040216158 | Blas | Oct 2004 | A1 |
| 20040268403 | Krieger et al. | Dec 2004 | A1 |
| 20050002638 | Putterman et al. | Jan 2005 | A1 |
| 20050028208 | Ellis et al. | Feb 2005 | A1 |
| 20050034171 | Benya | Feb 2005 | A1 |
| 20050050579 | Dietz et al. | Mar 2005 | A1 |
| 20050076365 | Popov et al. | Apr 2005 | A1 |
| 20050097599 | Plotnick et al. | May 2005 | A1 |
| 20050235307 | Relan et al. | Oct 2005 | A1 |
| 20060059342 | Medvinsky et al. | Mar 2006 | A1 |
| 20060059532 | Dugan et al. | Mar 2006 | A1 |
| 20060061682 | Bradley et al. | Mar 2006 | A1 |
| 20060085416 | Naoi et al. | Apr 2006 | A1 |
| 20060128397 | Choti et al. | Jun 2006 | A1 |
| 20060139379 | Toma et al. | Jun 2006 | A1 |
| 20060165082 | Pfeffer et al. | Jul 2006 | A1 |
| 20060288366 | Boylan et al. | Dec 2006 | A1 |
| 20070014293 | Filsfils et al. | Jan 2007 | A1 |
| 20070022459 | Gaebel et al. | Jan 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070038671 | Holm et al. | Feb 2007 | A1 |
| 20070053513 | Hoffberg | Mar 2007 | A1 |
| 20070073704 | Bowden et al. | Mar 2007 | A1 |
| 20070079333 | Murakami et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070118848 | Schwesinger et al. | May 2007 | A1 |
| 20070136777 | Hasek et al. | Jun 2007 | A1 |
| 20070157228 | Bayer et al. | Jul 2007 | A1 |
| 20070199019 | Angiolillo et al. | Aug 2007 | A1 |
| 20070204308 | Nicholas et al. | Aug 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070261089 | Aaby et al. | Nov 2007 | A1 |
| 20070276925 | La et al. | Nov 2007 | A1 |
| 20080022309 | Begeja et al. | Jan 2008 | A1 |
| 20080027801 | Walter et al. | Jan 2008 | A1 |
| 20080059646 | Ludvig | Mar 2008 | A1 |
| 20080066095 | Reinoso | Mar 2008 | A1 |
| 20080086750 | Yasrebi et al. | Apr 2008 | A1 |
| 20080092058 | Afergan et al. | Apr 2008 | A1 |
| 20080098212 | Helms | Apr 2008 | A1 |
| 20080101763 | Bhogal et al. | May 2008 | A1 |
| 20080109853 | Einarsson et al. | May 2008 | A1 |
| 20080155614 | Cooper et al. | Jun 2008 | A1 |
| 20080168487 | Chow et al. | Jul 2008 | A1 |
| 20080172696 | Furusawa et al. | Jul 2008 | A1 |
| 20080178225 | Jost | Jul 2008 | A1 |
| 20080184344 | Hernacki et al. | Jul 2008 | A1 |
| 20080189617 | Covell et al. | Aug 2008 | A1 |
| 20080200154 | Maharajh et al. | Aug 2008 | A1 |
| 20080201736 | Gordon et al. | Aug 2008 | A1 |
| 20080215755 | Farber et al. | Sep 2008 | A1 |
| 20080216119 | Pfeffer | Sep 2008 | A1 |
| 20080216135 | Pfeffer | Sep 2008 | A1 |
| 20080216136 | Pfeffer | Sep 2008 | A1 |
| 20080235746 | Peters et al. | Sep 2008 | A1 |
| 20080256615 | Schlacht et al. | Oct 2008 | A1 |
| 20080294713 | Saylor et al. | Nov 2008 | A1 |
| 20080313690 | Tsang | Dec 2008 | A1 |
| 20080320523 | Morris et al. | Dec 2008 | A1 |
| 20090006211 | Perry et al. | Jan 2009 | A1 |
| 20090019488 | Ruiz-Velasco et al. | Jan 2009 | A1 |
| 20090030802 | Plotnick et al. | Jan 2009 | A1 |
| 20090031335 | Hendricks et al. | Jan 2009 | A1 |
| 20090049468 | Shkedi | Feb 2009 | A1 |
| 20090064218 | Yamagishi | Mar 2009 | A1 |
| 20090076898 | Wang et al. | Mar 2009 | A1 |
| 20090077583 | Sugiyama et al. | Mar 2009 | A1 |
| 20090083279 | Hasek | Mar 2009 | A1 |
| 20090094347 | Ting et al. | Apr 2009 | A1 |
| 20090119703 | Piepenbrink et al. | May 2009 | A1 |
| 20090125934 | Jones et al. | May 2009 | A1 |
| 20090132347 | Anderson et al. | May 2009 | A1 |
| 20090133090 | Busse | May 2009 | A1 |
| 20090158311 | Hon et al. | Jun 2009 | A1 |
| 20090172757 | Aldrey et al. | Jul 2009 | A1 |
| 20090172762 | Assouline | Jul 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090187944 | White et al. | Jul 2009 | A1 |
| 20090210899 | Lawrence-Apfelbaum et al. | Aug 2009 | A1 |
| 20090228941 | Russell et al. | Sep 2009 | A1 |
| 20090248794 | Helms et al. | Oct 2009 | A1 |
| 20090271826 | Lee et al. | Oct 2009 | A1 |
| 20090327057 | Redlich | Dec 2009 | A1 |
| 20090328105 | Craner et al. | Dec 2009 | A1 |
| 20090328109 | Pavlovskaia et al. | Dec 2009 | A1 |
| 20100005499 | Covey | Jan 2010 | A1 |
| 20100011388 | Bull et al. | Jan 2010 | A1 |
| 20100027787 | Benkert et al. | Feb 2010 | A1 |
| 20100036720 | Jain et al. | Feb 2010 | A1 |
| 20100043030 | White | Feb 2010 | A1 |
| 20100046927 | Manthoulis | Feb 2010 | A1 |
| 20100082635 | Elsner et al. | Apr 2010 | A1 |
| 20100115540 | Fan et al. | May 2010 | A1 |
| 20100121936 | Liu et al. | May 2010 | A1 |
| 20100131973 | Dillon et al. | May 2010 | A1 |
| 20100131983 | Shannon et al. | May 2010 | A1 |
| 20100132003 | Bennett et al. | May 2010 | A1 |
| 20100146541 | Velazquez | Jun 2010 | A1 |
| 20100162294 | Yin et al. | Jun 2010 | A1 |
| 20100162367 | Lajoie et al. | Jun 2010 | A1 |
| 20100169503 | Kollmansberger et al. | Jul 2010 | A1 |
| 20100186029 | Kim et al. | Jul 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100262461 | Bohannon | Oct 2010 | A1 |
| 20100262999 | Curran | Oct 2010 | A1 |
| 20100287588 | Cox et al. | Nov 2010 | A1 |
| 20100313225 | Cholas et al. | Dec 2010 | A1 |
| 20100333137 | Hamano et al. | Dec 2010 | A1 |
| 20110015989 | Tidwell et al. | Jan 2011 | A1 |
| 20110016479 | Tidwell et al. | Jan 2011 | A1 |
| 20110055866 | Piepenbrink et al. | Mar 2011 | A1 |
| 20110058675 | Brueck et al. | Mar 2011 | A1 |
| 20110083069 | Paul et al. | Apr 2011 | A1 |
| 20110083144 | Bocharov et al. | Apr 2011 | A1 |
| 20110093900 | Patel et al. | Apr 2011 | A1 |
| 20110103374 | Lajoie et al. | May 2011 | A1 |
| 20110107364 | Lajoie et al. | May 2011 | A1 |
| 20110107379 | Lajoie et al. | May 2011 | A1 |
| 20110126246 | Thomas et al. | May 2011 | A1 |
| 20110138064 | Rieger et al. | Jun 2011 | A1 |
| 20110154383 | Hao et al. | Jun 2011 | A1 |
| 20110154409 | Rhee et al. | Jun 2011 | A1 |
| 20110223944 | Gosselin | Sep 2011 | A1 |
| 20110231660 | Kanungo | Sep 2011 | A1 |
| 20110246616 | Ronca et al. | Oct 2011 | A1 |
| 20110258049 | Ramer et al. | Oct 2011 | A1 |
| 20110264530 | Santangelo et al. | Oct 2011 | A1 |
| 20110265116 | Stern et al. | Oct 2011 | A1 |
| 20110302624 | Chen et al. | Dec 2011 | A1 |
| 20120008786 | Cronk et al. | Jan 2012 | A1 |
| 20120011567 | Cronk et al. | Jan 2012 | A1 |
| 20120042337 | De Bonet et al. | Feb 2012 | A1 |
| 20120072526 | Kling et al. | Mar 2012 | A1 |
| 20120076015 | Pfeffer | Mar 2012 | A1 |
| 20120079523 | Trimper et al. | Mar 2012 | A1 |
| 20120084828 | Rowe et al. | Apr 2012 | A1 |
| 20120089699 | Cholas | Apr 2012 | A1 |
| 20120096106 | Blumofe et al. | Apr 2012 | A1 |
| 20120096499 | Dasher | Apr 2012 | A1 |
| 20120124612 | Adimatyam et al. | May 2012 | A1 |
| 20120131139 | Siripurapu et al. | May 2012 | A1 |
| 20120137332 | Kumar | May 2012 | A1 |
| 20120144195 | Nair et al. | Jun 2012 | A1 |
| 20120151077 | Finster | Jun 2012 | A1 |
| 20120167132 | Mathews et al. | Jun 2012 | A1 |
| 20120170544 | Cheng et al. | Jul 2012 | A1 |
| 20120170741 | Chen et al. | Jul 2012 | A1 |
| 20120173746 | Salinger et al. | Jul 2012 | A1 |
| 20120185693 | Chen et al. | Jul 2012 | A1 |
| 20120197980 | Terleski et al. | Aug 2012 | A1 |
| 20120240176 | Ma | Sep 2012 | A1 |
| 20120246462 | Moroney et al. | Sep 2012 | A1 |
| 20120278833 | Tam et al. | Nov 2012 | A1 |
| 20120284804 | Lindquist et al. | Nov 2012 | A1 |
| 20120308071 | Ramsdell et al. | Dec 2012 | A1 |
| 20120324552 | Padala et al. | Dec 2012 | A1 |
| 20130024901 | Sharif-Ahmadi et al. | Jan 2013 | A1 |
| 20130031578 | Zhu et al. | Jan 2013 | A1 |
| 20130046849 | Wolf et al. | Feb 2013 | A1 |
| 20130132986 | Mack et al. | May 2013 | A1 |
| 20130133010 | Chen | May 2013 | A1 |
| 20130166906 | Swaminathan et al. | Jun 2013 | A1 |
| 20130167168 | Ellis et al. | Jun 2013 | A1 |
| 20130174271 | Handal et al. | Jul 2013 | A1 |
| 20130179588 | McCarthy et al. | Jul 2013 | A1 |
| 20130198770 | Xiong et al. | Aug 2013 | A1 |
| 20130219178 | Xiques et al. | Aug 2013 | A1 |
| 20130227283 | Williamson | Aug 2013 | A1 |
| 20130227284 | Pfeffer et al. | Aug 2013 | A1 |
| 20130254815 | Pfeffer | Sep 2013 | A1 |
| 20140012843 | Soon-Shiong | Jan 2014 | A1 |
| 20140059055 | Nag et al. | Feb 2014 | A1 |
| 20140230003 | Ma et al. | Aug 2014 | A1 |
| 20140245341 | Mack et al. | Aug 2014 | A1 |
| 20140259182 | Mershon | Sep 2014 | A1 |
| 20140282777 | Gonder | Sep 2014 | A1 |
| 20140282784 | Pfeffer | Sep 2014 | A1 |
| 20140344857 | Kanojia et al. | Nov 2014 | A1 |
| 20150020126 | Kegel et al. | Jan 2015 | A1 |
| 20150109122 | Stern et al. | Apr 2015 | A1 |
| 20150161386 | Gupta et al. | Jun 2015 | A1 |
| 20150163540 | Masterson | Jun 2015 | A1 |
| 20150215424 | Chun et al. | Jul 2015 | A1 |
| 20160241617 | Jelley et al. | Aug 2016 | A1 |
| 20170048357 | Pfeffer et al. | Feb 2017 | A1 |
| 20170070773 | Phillips | Mar 2017 | A1 |
| 20190014368 | Donoghue et al. | Jan 2019 | A1 |
| 20190075128 | Roosenraad et al. | Mar 2019 | A1 |
| 20190098505 | Mars | Mar 2019 | A1 |
| 20190171341 | Eubanks | Jun 2019 | A1 |
| 20190394530 | Kimble et al. | Dec 2019 | A1 |
| 20210377290 | Roosenraad et al. | Dec 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 3041380 | Oct 2010 | CA |
| 2806713 | Aug 2013 | CA |
| 2769893 | May 2019 | CA |
| 2762974 | Jun 2019 | CA |
| 1087619 | Mar 2001 | EP |
| 2632107 | Aug 2013 | EP |
| WO-9935846 | Jul 1999 | WO |
| WO-0156285 | Aug 2001 | WO |
| WO-2010008487 | Jan 2010 | WO |
| WO-2010114857 | Oct 2010 | WO |
| WO-2011035443 | Mar 2011 | WO |
| WO-2011053858 | May 2011 | WO |
| WO-2021084326 | May 2021 | WO |
| Entry |
|---|
| US 6,940,674 B2, 09/2005, Sugiyama (withdrawn) |
| Apple Inc., HTTP Live Streaming Overview, Apr. 1, 2011. |
| OpenCable Specifications, Alternate Content, Real-Time Event Signaling and Management API, OC-SP-ESAM-API-I01-120910 (2012). |
| SCTE American National Standard ANSI/SCTE 118-2 2007. |
| SCTE American National Standard ANSI/SCTE 130-1 2008. |
| SCTE, American National Standard, ANSI/SCTE 35 2012. |
| Zarnbelli, The Apparatus and Methods of HS Smooth Streaming Technical Overview, Mar. 2009. |
| Number | Date | Country | |
|---|---|---|---|
| 20200045141 A1 | Feb 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15243353 | Aug 2016 | US |
| Child | 16544558 | US | |
| Parent | 13403814 | Feb 2012 | US |
| Child | 15243353 | US |
