CA2774363A1 - Dynamic content packaging - Google Patents
Dynamic content packaging Download PDFInfo
- Publication number
- CA2774363A1 CA2774363A1 CA2774363A CA2774363A CA2774363A1 CA 2774363 A1 CA2774363 A1 CA 2774363A1 CA 2774363 A CA2774363 A CA 2774363A CA 2774363 A CA2774363 A CA 2774363A CA 2774363 A1 CA2774363 A1 CA 2774363A1
- Authority
- CA
- Canada
- Prior art keywords
- content
- determining
- delivery route
- packager
- requested
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
- H04L47/2433—Allocation of priorities to traffic types
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1014—Server selection for load balancing based on the content of a request
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1021—Server selection for load balancing based on client or server locations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
- H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
- H04N21/2365—Multiplexing of several video streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
- H04N21/2368—Multiplexing of audio and video streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2389—Multiplex stream processing, e.g. multiplex stream encrypting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25808—Management of client data
- H04N21/25841—Management of client data involving the geographical location of the client
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
- H04N21/4353—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream involving decryption of additional data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
- H04N21/4508—Management of client data or end-user data
- H04N21/4524—Management of client data or end-user data involving the geographical location of the client
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/64—Addressing
- H04N21/6405—Multicasting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/64—Addressing
- H04N21/6408—Unicasting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/16—Analogue secrecy systems; Analogue subscription systems
- H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
- H04N7/17309—Transmission or handling of upstream communications
- H04N7/17318—Direct or substantially direct transmission and handling of requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04H—BROADCAST COMMUNICATION
- H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
- H04H60/35—Arrangements for identifying or recognising characteristics with a direct linkage to broadcast information or to broadcast space-time, e.g. for identifying broadcast stations or for identifying users
- H04H60/38—Arrangements for identifying or recognising characteristics with a direct linkage to broadcast information or to broadcast space-time, e.g. for identifying broadcast stations or for identifying users for identifying broadcast time or space
- H04H60/41—Arrangements for identifying or recognising characteristics with a direct linkage to broadcast information or to broadcast space-time, e.g. for identifying broadcast stations or for identifying users for identifying broadcast time or space for identifying broadcast space, i.e. broadcast channels, broadcast stations or broadcast areas
- H04H60/44—Arrangements for identifying or recognising characteristics with a direct linkage to broadcast information or to broadcast space-time, e.g. for identifying broadcast stations or for identifying users for identifying broadcast time or space for identifying broadcast space, i.e. broadcast channels, broadcast stations or broadcast areas for identifying broadcast stations
Abstract
To be accessed on different media players, requested content must be delivered in a format that is supported by the requesting device. A dynamic content packager for encrypting and packaging requested content for different requesting devices at the time of consumption is disclosed.
Description
DYNAMIC CONTENT PACKAGING
CROSS-REFERENCE TO RELATED APPLICATIONS
[01] The present application claims priority to U.S. Provisional Application Number 61/242,444, entitled "IP Video Service Delivery Reference Architecture," filed September 15, 2009, and to U.S. Provisional Application Number 61/242,456, entitled "TV
Anywhere Architecture," filed September 15, 2009, the contents of which are hereby incorporated by reference as non-limiting example embodiments.
BACKGROUND
CROSS-REFERENCE TO RELATED APPLICATIONS
[01] The present application claims priority to U.S. Provisional Application Number 61/242,444, entitled "IP Video Service Delivery Reference Architecture," filed September 15, 2009, and to U.S. Provisional Application Number 61/242,456, entitled "TV
Anywhere Architecture," filed September 15, 2009, the contents of which are hereby incorporated by reference as non-limiting example embodiments.
BACKGROUND
[02] Content providers distribute content, services, and other information to a user's premises via an information distribution network using various protocols. Users at the premises are increasingly demanding a greater variety of content, services, and other information at a faster response time. This has led to a growing collection of management schemes and protocols used throughout a distribution network. The content to be delivered may be encrypted depending upon the content and/or service. In addition, users may want to receive content in different formats depending on the device being used for accessing received content. Users may also want to access the same content at different times on different devices. For example, users may access content for use on a portable device during a particular time period and access the same content via a second device such as a stationary device during a second time period. This may occur, for example, when a user starts to watch a video on a mobile device and returns home to finish watching the remaining video content on a home television.
[03] Thus, to support different devices, content may be converted into different formats so that users may access and utilize the content on different media devices. Storing multiple formats of the same content for delivery to users utilizing different devices requires large amounts of storage, provides increased operational cost for preprocessing of the content into different formats, and may not provide content for new device formats which may be introduced into the market. Thus, there is an ever present need for efficient solutions for -I-providing content to numerous different devices without storing the same content in numerous different formats.
SUMMARY
SUMMARY
[04] The features described herein generally relate to a dynamic content packager for encrypting and packaging requested content for different requesting devices at the time of consumption. A content packager which may reside at the ingress or egress of a content delivery network provides the requested content along a determined content delivery route.
[05] In an exemplary embodiment, a device location and profile of a requesting device may be determined. Based on the requesting device location and profile, at least one content packager may be determined. A content path may be determined along which the at least one content packager resides. Encryption keys and packaging metadata may be retrieved to encrypt, transcode, and segment the requested content for the requesting device. The requested content may be delivered to the requesting device along the determined content delivery route.
[06] Additional aspects of the disclosure relate to determining that the requested content already resides in resident cache located along the determined content delivery route.
The content packager may cache the first requested content for each different requesting device format for future delivery to subsequent requesting devices.
The content packager may cache the first requested content for each different requesting device format for future delivery to subsequent requesting devices.
[07] The preceding presents a simplified summary in order to provide a basic understanding of some aspects of the disclosure. The summary is not an extensive overview of the disclosure. It is neither intended to identify key or critical elements of the disclosure nor to delineate the scope of the disclosure. The summary merely presents some concepts of the disclosure in a simplified form as a prelude to the description below.
BRIEF DESCRIPTION OF THE DRAWINGS
BRIEF DESCRIPTION OF THE DRAWINGS
[08] The present disclosure is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:
[09] Figure 1 illustrates an example information distribution network on which features of the disclosure may be implemented.
[10] Figure 2 illustrates an example hardware platform on which the various features of the disclosure may be implemented.
[11] Figure 3 illustrates an example system diagram on which features of the disclosure may be implemented.
[12] Figure 4 illustrates a detailed portion of the system diagram of Figure 3 in which features of the disclosure may be implemented.
[13] Figure 5 represents another exemplary system diagram on which features of the disclosure may be implemented.
[14] Figure 6 illustrates an exemplary flow diagram in which content may be received in accordance with an aspect of the disclosure.
[15] Figure 7 illustrates another exemplary flow diagram in which a content delivery route may be delivered to in accordance with an aspect of the disclosure.
DETAILED DESCRIPTION
DETAILED DESCRIPTION
[16] In the following description of various illustrative embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown, by way of illustration, various embodiments in which aspects of the disclosure may be practiced. It is to be understood that other embodiments may be utilized, and structural and functional modifications may be made, without departing from the scope of the present disclosure.
[17] FIG. 1 illustrates an example content (e.g., data, media, information, services, etc.), distribution network 100 on which many of the various features described herein may be implemented. Network 100 may be any type of information distribution network, such as satellite, telephone, cellular, wired or wireless, etc. One example may be an optical fiber network, a coaxial cable network or a hybrid fiber/coax (HFC) distribution network.
Such networks 100 use a series of interconnected communication lines 101 (e.g., coaxial cables, optical fibers, wireless, etc.) to connect multiple premises 102 (e.g., businesses, homes, consumer dwellings, etc.) to a central office or headend 103 (e.g., a headend, a processing facility, etc.). The central office 103 may transmit downstream information signals onto the lines 101, and each premises 102 may have a receiver used to receive and process those signals.
Such networks 100 use a series of interconnected communication lines 101 (e.g., coaxial cables, optical fibers, wireless, etc.) to connect multiple premises 102 (e.g., businesses, homes, consumer dwellings, etc.) to a central office or headend 103 (e.g., a headend, a processing facility, etc.). The central office 103 may transmit downstream information signals onto the lines 101, and each premises 102 may have a receiver used to receive and process those signals.
[18] There may be one line 101 originating from the central office 103, and it may be split a number of times to distribute the signal to various premises 102 in the vicinity (which may be many miles) of the central office 103. The lines 101 may include components not illustrated, such as splitters, filters, amplifiers, etc. to help convey the signal clearly, but in general each split introduces a bit of signal degradation. Portions of the lines 101 may also be implemented with fiber-optic cable, while other portions may be implemented with coaxial cable, other lines, or wireless communication paths. By running fiber optic cable along some portions, for example, signal degradation in those portions may be significantly minimized, allowing a single central office 103 to reach even farther with its network of lines 101 than before.
[19] The various premises 102 may be connected (through wiring and/or wireless connections) to one another, forming a local premises access network operationally distinct from another local access network. The connected homes forming a local premises access network may be located near one another, such as neighboring townhomes, individual apartments in a downtown highrise, or the like. For example, a local premises access network may include the various premises 102. Another group of homes (now shown) may form a separate local premises access network. The local premises access network of the various premises 102 may be identifiable from the separate local premises access network. A local premises access network may also be associated with a particular geographic region (e.g., city, county, geographic area, etc.).
In some embodiments, homes connected to a termination system (TS), such as a modem termination system (MTS), may form a local premises access network.
In some embodiments, homes connected to a termination system (TS), such as a modem termination system (MTS), may form a local premises access network.
[20] The central office 103 may include a termination system (TS) 104, such as a cable modem termination system (CMTS) in an example of a HFC-type network, which may be a computing device configured to manage communications between devices on the network of lines 101 and backend devices such as servers 105-107 (to be discussed further below). In the example of an HFC-type network, the MTS may be as specified in a standard, such as the Data Over Cable Service Interface Specification (DOCSIS) standard, published by Cable Television Laboratories, Inc. (a.k.a. CableLabs), or it may be a similar or modified device instead. The MTS may be configured to place data on one or more downstream frequencies to be received by modems at the various premises 102, and to receive upstream communications from those modems on one or more upstream frequencies. The central office 103 may also include one or more network interfaces 108, which can permit the central office 103 to communicate with various other external networks 109. These networks 109 may include, for example, Internet Protocol (IP) networks having Internet devices, telephone networks, cellular telephone networks, fiber optic networks, local wireless networks (e.g., WiMAX), satellite networks, and any other desired network, and the interface 108 may include the corresponding circuitry needed to communicate on the network 109, and to other devices on the network such as a cellular telephone network and its corresponding cell phones 117.
[211 As noted above, the central office 103 may include a variety of servers 105-107 that may be configured to perform various functions. For example, the central office 103 may include a push notification server 105. The push notification server 105 may generate push notifications to deliver data and/or commands to the various premises 102 in the network (or more specifically, to the devices in the premises 102 that are configured to detect such notifications). The central office 103 may also include a content server 106.
The content server 106 may be one or more computing devices that are configured to provide content to users in the homes. This content may be, for example, video on demand movies, television programs, songs, services, information, text listings, etc. In some embodiments, the content server 106 may include software to validate (or initiate the validation of) user identities and entitlements, locate and retrieve (or initiate the locating and retrieval of) requested content, encrypt the content, and initiate delivery (e.g., streaming, transmitting via a series of content fragments) of the content to the requesting user and/or device.
[221 The central office 103 may also include one or more application servers 107. An application server 107 may be a computing device configured to offer any desired service, and may run various languages and operating systems (e.g., servlets and JSP
pages running on Tomcat/MySQL, OSX, BSD, Ubuntu, Redhat, HTML5, JavaScript, AJAX and COMET). For example, an application server may be responsible for collecting television program listings information and generating a data download for electronic program guide listings. Another application server may be responsible for monitoring user viewing habits and collecting that information for use in selecting advertisements. Another application server may be responsible for formatting and inserting advertisements in a video stream and/or content item being transmitted to the premises 102.
[231 An example premises 102a may include a modem 110 (or another receiver and/or transmitter device suitable for a particular network), which may include transmitters and receivers used to communicate on the lines 101 and with the central office 103. The modem 110 may be, for example, a coaxial cable modem (for coaxial cable lines 101), a fiber interface node (for fiber optic lines 101), or any other desired modem device. The modem 110 may be connected to, or be a part of, a gateway interface device 111. The gateway interface device 111 may be a computing device that communicates with the modem 110 to allow one or more other devices in the home to communicate with the central office 103 and other devices beyond the central office. The gateway 111 may be a set-top box (STB), digital video recorder (DVR), computer server, or any other desired computing device. The gateway 111 may also include (not shown) local network interfaces to provide communication signals to other devices in the home (e.g., user devices), such as televisions 112, additional STBs 113, personal computers 114, laptop computers 115, wireless devices 116 (wireless laptops and netbooks, mobile phones, mobile televisions, personal digital assistants (PDA), etc.), and any other desired devices.
Examples of the local network interfaces may include Multimedia Over Coax Alliance (MoCA) interfaces, Ethernet interfaces, universal serial bus (USB) interfaces, wireless interfaces (e.g., IEEE 802.11), Bluetooth interfaces, and others.
[24] FIG. 2 illustrates general hardware elements that can be used to implement any of the various computing devices discussed herein. The computing device 200 may include one or more processors 201, which may execute instructions of a computer program to perform any of the features described herein. The instructions may be stored in any type of computer-readable medium or memory, to configure the operation of the processor 201. For example, instructions may be stored in a read-only memory (ROM) 202, random access memory (RAM) 203, removable media 204, such as a Universal Serial Bus (USB) drive, compact disk (CD) or digital versatile disk (DVD), floppy disk drive, or any other desired electronic storage medium. Instructions may also be stored in an attached (or internal) hard drive 205. The computing device 200 may include one or more output devices, such as a display 206 (or an external television), and may include one or more output device controllers 207, such as a video processor. There may also be one or more user input devices 208, such as a remote control, keyboard, mouse, touch screen, microphone, etc. The computing device 200 may also include one or more network interfaces, such as input/output circuits 209 (such as a network card) to communicate with an external network 210. The network interface may be a wired interface, wireless interface, or a combination of the two. In some embodiments, the interface 209 may include a modem (e.g., a cable modem), and network 210 may include the communication lines 101 discussed above, the external network 109, an in-home network, a provider's wireless, coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., a DOCSIS network), or any other desired network.
[25] The FIG. 2 example is an example hardware configuration. Modifications may be made to add, remove, combine, divide, etc. components as desired. Additionally, the components illustrated may be implemented using basic computing devices and components, and the same components (e.g., processor 201, storage 202, user interface 205, etc.) may be used to implement any of the other computing devices and components described herein. For example, the various components herein may be implemented using computing devices having components such as a processor executing computer-executable instructions stored on a computer-readable medium, as illustrated in FIG. 2.
[26] One or more aspects of the disclosure may be embodied in a computer-usable data and/or computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other data processing device. The computer executable instructions may be stored on one or more computer readable media such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc. As will be appreciated by one of skill in the art, the functionality of the program modules may be combined or distributed as desired in various embodiments. In addition, the functionality may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA), and the like. Particular data structures may be used to more effectively implement one or more aspects of the invention, and such data structures are contemplated within the scope of computer executable instructions and computer-usable data described herein.
[27] As discussed above, the central office of an information distribution network may transmit information downstream to various user devices. The transmitted information may include content for consumption (e.g., playback, viewing, listening, display, storage, etc.) by a user via user equipment, such as a gateway interface device (e.g., gateway interface device 111 of FIG. 1) and/or other computing device (e.g., televisions 112, additional STBs 113, personal computers 114, laptop computers 115, wireless devices 116 of FIG. 1). To assist in providing the content to a user, a content provider may implement in their distribution network an information distribution management system that includes one or more information distribution management devices (e.g., one or more servers and/or other devices) configured to perform various processes related to managing the providing of content to the user equipment (e.g., user device).
[28] For example, such managing may include requesting, creating and handling various sessions (e.g., user sessions, multicast group sessions, cache fill sessions, quality of service sessions); managing transmission of the content (e.g., managing the establishing of transmissions providing unicast content, such as on demand, and linear content, such as multicast content); monitoring usage data of the distribution network, and/or handling requests and notifications from user equipment. As another example, managing may include managing the content discovery, content locating and content delivery processes of the distribution network. In some embodiments, the managing may be implemented using IP (Internet Protocol) and/or HTTP (Hypertext Transfer Protocol) based processes.
For example, communication between various devices may be performed using HTTP
and/or IP packets. In one example, a session manager server may locate a streaming server and/or a multicast address for a particular content item, and may notify user equipment of the streaming server and/or multicast address for the particular content item using HTTP packets. The user equipment may receive the particular content item (via a unicast signal and/or a multicast signal) by receiving HTTP packets that include fragments of the content item and metadata identifying the streaming server and/or multicast address. In some embodiments, communication between devices may use only a single protocol (e.g., only HTTP packets or IP packets). Content items may also be transmitted using the single protocol (e.g., HTTP or IP packets including fragments of content items). Details of these processes, and others, will be discussed in further detail below.
[291 Content discovery processes may include supporting the discovery of content for various content items being provided by a distribution network. For example, content discovery processes may support the discovery of content items for multicast and/or linear transmission. In some embodiments, content discovery and the various related processes may use an HTTP-based approach (e.g., communication is via HTTP and/or IP
packets) that includes communication between user equipment, application servers, and other various servers of the central office.
[301 Content locating processes may include supporting the setup of various sessions and managing the resources of the information distribution network. In some embodiments, content locating processes may enforce entitlement procedures and digital rights management (DRM) licenses. Additionally, in some embodiments, content locating and the various related processes may use an HTTP based approach that includes communication between user equipment, session manager servers, and other servers of the central office.
[31] Content delivery processes may include supporting the streaming of the content items from various servers, such as a streaming server of the central office. In some embodiments, content delivery processes may enable user equipment to receive multicast signals (e.g., signals directed at a plurality and/or group of user equipment) and/or receive unicast signals (e.g., signals directed at a specific user device).
Additionally, in some embodiments, content streaming and the various related processes may use an HTTP
based approach that includes communication between user equipment, content servers, and other servers of the central office.
[32] Figure 3 illustrates an example system of components that may be implemented on the network 100, and which may be used to implement various features described herein to supply various content to users. The system may include one or more sources of the content. For example, in the case of video content (e.g., audiovideo content), there may be one or more video on demand (VOD) content encoders 301, each of which may include an application server (such as application server 107) configured to store video content such as movies, television shows, video clips, musical videos, etc.
The encoders 301 may include encoding hardware and/or software to provide content in a desired format, such as MPEG.
[331 The system may also include one or more linear content encoders 302.
Linear content encoders 302 may be similar to VOD content encoders 301, but may further be configured to supply content according to a predetermined schedule, as opposed to on demand. For example, the NBC content service may have one or more linear encoders 302 configured to supply a video stream of NBC scheduled video programming (e.g., the nightly news) at the appropriate time.
[34] The system may include one or more content packagers 303. In an embodiment, packager 303 may be included in premises gateway 311. The content packager 303 may be another application server, but configured to receive content and package it for delivery to users. This packaging may include, for example, reformatting the content (e.g., video resolution conversion, coder/decoder conversion, audio conversion, compression altering, synchronization, etc.), and segmenting the content (e.g., a two-hour movie may be divided into a plurality of discrete time segments for delivery).
In addition, packaging may include encrypting the content.
[35] The system may include a license server/key manager 304, which may be a server configured to manage content entitlement. For example, the manager 304 may contain encryption and/or decryption keys, and can supply those keys to content packager 303 for use in encrypting content for delivery. The manager 304 may also store information identifying users, and the level(s) of service to which the users are entitled, and may make determinations as to whether a particular user is actually entitled to receive a piece of requested content.
[36] Content delivery network 305 may be any desired type of communication network, such as network 109. The network 305 may span a large geographic area, and may be used to disseminate content or make content accessible. For example, some content may be supplied to. a streaming server 306. The streaming server 306 may be a server configured to receive packaged content, and generate a unicast stream of that content for delivery to a user.
[37] Another example may be a multicast server 307. Like the streaming server, multicast server 307 may also be configured to generate a stream of packaged content.
However, the multicast server's stream may be a multicast stream, configured to be received by a plurality of recipient users.
[38] The multicast server 307 may operate at the direction of a multicast controller 308, which may in turn communicate with a session manager 309 to establish multicast sessions for the delivery of various pieces of content. Session Manager 309 may be configured to manage one or more sessions of the distribution network by interfacing with various devices in the distribution network and communicating session information with the various devices. In some embodiments, the sessions that are managed by session manager 309 may include a user session, a multicast group session, a cache fill session, and/or a QoS flow session. For example, a user session may be created upon a user device requesting content, and may include information related to the requested content and the entitlements of the user device. A multicast group session may be created upon a user device joining a multicast group of a particular group of user equipment, and may include information related to the multicast group. A cache fill session may be created upon a user device requesting a cache fill of a particular content item being transmitted (e.g., multicast or unicast), and may include information related to the user device and the particular content item. A QoS flow session may be created based on the initiation of a transmission to a user device, and may include information related to the QoS
profile being enforced and the user device. Details of these sessions will be discussed in further detail below.
[39] The servers 306/307 may communicate with a termination system 310 (e.g., termination system 104) to ultimately deliver the content to a user's premises, or to a premises gateway 311 that can, in turn, supply content to various pieces of user equipment, such as a set-top box 312a, computer 312b, or any other desired display device or piece of user equipment.
[40] Other servers may be used as part of this delivery as well. For example, a quality of service (QoS) configuration manager 313 may be used to determine quality of service parameters for a given stream. As another example, a location resolution server 314 may contain geographic identification information for the various servers 306/307, termination servers 310, packagers 303, and other components in the system, and may be configured to determine which device(s) are closest geographically to a requesting user device.
Location resolution server 314 may be configured to determine location information for a particular user device. For example, in some embodiments, location resolution server 314 may receive a location request identifying a particular user device, determine geographic information (e.g., latitude and longitude) for the user device, determine whether the user device is on-network or off-network and transmit the information to the session manager 309. A user device being on-net may include user devices connected via termination systems (e.g., termination system 310) of the content provider. A
user device being off-net may include user devices (e.g., user equipment) connected via third party distribution networks that are not under the management or control of the session manager 309 and multicast controller 308.
[41] An entitlement resolution server 315 may be configured to validate a user device's entitlement to a particular content item. For example, in some embodiments, entitlement resolution server 315 may receive a validate entitlement request identifying a content item; determine whether a user device has a valid entitlement to the content item, based on user session information, content item information, and location information of the user device; and transmit the information indicating the result of the determination to the session manager 309. Entitlement resolution server 315 may also be configured to validate a user device's license to a particular content item. For example, in some arrangements, entitlement resolution server 315 may receive a validate license request identifying a content item, determine whether a user device has a valid license to the content item, based on user session information and content item information, and transmit information indicating the result of the determination to a license resolution server 316.
[42] License resolution server 316 may be configured to distribute licenses and/or distribute decryption and encryption keys. For example, in some embodiments, license resolution device 316 may distribute encryption keys to content packager 303 (or to license server/key manager 304). The license resolution server may also receive a license request from a user device; transmit a request to the entitlement resolution device to validate the license; and upon receiving an indication that the user device has a valid license, and transmit the license and one or more decryption keys to the user device.
[43] In an aspect of the disclosure, content packager 303 may receive content in a mezzanine or universal file format to be reformatted, encoded, and segmented based on a users request for content. The mezzanine or universal file format may comprise, for example, a MPEG-2 single program transport stream or a similar transport stream as described in ISO 13818-1. For instance, in an embodiment of the disclosure content packager may be functionally positioned at the ingress of content delivery network 305.
Positioning content packager 303 at the ingress of content delivery network 305 may allow for caching of the output stream of content packager 303 for fulfilling other user requests for the same content accessed by similar device types. Caching the output of content packager 303 upstream of content delivery network 305 may reduce overall load on content packager 303. In addition, caching the output upstream of content delivery network 305 may enable the cached content to be available to a larger pool of users that may be geographically distant. For instance, numerous users utilizing a particular smart phone may request a recent episode of a television series for viewing. These users may be geographically widespread as some may be located in Chicago, Illinois while others may be located in Tampa, Florida. The output requested from the first requesting user may be cached so that the next similar device type request from a user may be delivered from cache reducing overall load on content packager 303.
[44] Figure 4 illustrates content cache 402 which may be used to store output of content packager 303. Those skilled in the art will realize that content cache 402 may also be supplemented or physically placed within content delivery network 305. In addition, content cache 402 trough 409 may be part of a multi-tier caching structure. In an embodiment, each content cache 409-411 may be utilized for different geographical regions.
[45] In Figure 4, distribution system 400 may include one or more content packagers 303, 404, and 406. Each content packager 303, 404, and 406 may also be associated with different content caches 402, 405, and 407. In addition, content caches may be located across content delivery network 305 such as content caches 409 and 411. Based on a received device type, packaging of the requested content may be routed to the appropriate content packager 303, 404, and 406. Those skilled in the art will realize that additional content packagers 303 may be utilized to support different requesting device types. Each content packager 303 based on received or determined requesting device type may reformat the content, encrypt the content, and segment the content.
[46] In another aspect of the disclosure, content packager 303 may be functionally positioned at the egress of content delivery network 305 as shown in Figure 5.
Positioning content packager 303 at the egress of content delivery network 305 may allow all content delivered through the content delivery network 305 to be in a mezzanine or universal file format. In addition, a content packager 303 positioned at the egress of the content delivery network 305 may be very close to termination system 310 and premises gateway 311 which may support session based encryption for increased content security.
[47] Location resolution server 314 may be configured to determine location information for a particular user device. For example, location resolution server 314 may determine a requesting location for a user device requesting content delivery. The determined location of the requesting device may be used to determine an optimal content packager 303 and streaming server 306 to complete content delivery. In addition, alternative content packagers 303 and streaming servers 306 may be identified and/or utilized based on availability and utilization of all content packagers 303 and streaming servers 306. In an embodiment, an IP address or GPS data for a requesting device may be used to determine device location. For instance, some pieces of user equipment (312a and 312b) may contain GPS units. These devices may upon setup specify their coordinates such as longitude and latitude to allow the system to know the exact location of the user device.
[48] Content Router 317 may be configured to determine an optimal content delivery path for delivery of requested content. In an embodiment, session manager 309 along with content router 317 may consider specifications and utilization of content packagers 303 and content streamers 306 to determine an optional content delivery path. In another embodiment, based on the determined device types both ingress 303 and egress content packagers 303 may be utilized to provide optimal content delivery.
[49] Session manager 309 may also in some aspects of the disclosure communicate with premises gateway 311 in order to determine the devices types for various user equipment, e.g., CPE devices, such as 312a and 312b so that the optimal content packager 303 and content streamer 306 may be determined. For instance, premises gateway 311 may forward a setup session request from a CPE device to session manger 309. The setup session request may be used to validate a content purchase and return resource information to the CPE so that CPE can 1) obtain a list of content to access from a selected streaming server; 2) obtain a content manifest file; and 3) receive a DRM license and decryption key.
[50] Upon receiving a request for content, session manager 309 may retrieve requested content based on content packager 303 and content streamer 306 capabilities and configurations. Content packager 303 and content streamer 306 may be preselected at session startup for a particular CPE device. The session manger 309 and the content router 317 may provision target content format to either an ingress or egress content packager 303. Upon session startup for content consumption, a requesting user device may pull the content file and/or fragment from the content origin via content packager 303. The content packager 303 may retrieve the appropriate packaging metadata and encryption keys and begin the just-in-time packaging process.
[51] Table 1 illustrates an example of different media players that may be used on different devices along with their associated codecs and other properties which may be considered by content packager 303. Table 1 is merely illustrative and not meant to be an exhaustive list of devices and their associated properties.
Table 1 Player Codec Container Transport Stream Control Rate Adaptation QuickTime MPEG-4 AVC/AAC MP4 RTP over UDP/TCP RTSP No Streaming: RTMP Streaming: Yes Flash MPEG-4 AVC/AAC MP4 Progressive: HTTP N/A Progressive: No MS Window Media VC-1 ASF RTP over UDP/TCP RTSP No MS Silverlight MPEG-4 AVC/AAC MP4 (fragmented) HTTP HTTP (extension) Yes MS Mediaroom MPEG-4 AVC/AAC MPEG-2 Transport RTP/UDP (Linear) HTTP Yes RTP/HTTP (VOID) Move On2 VP7 N/A HTTP HTTP Yes Table 1 Player Codec Container Transport Stream Control Rate Adaptation RealVideo & RealVideo &
Real RDT (Proprietary) RTSP No RealAudio RealAudio Video: MPEG-2, HTTP
MPEG-2 Transport HTTP (extension) -DLNA MPEG-4 AVC RTP over UDP No Audio PCM, AC-3 MP4 (optional) proposed DVB MPEG-2 / AC-3 MPEG-2 Transport MPEG-2 transport N/A No MPEG-4 AVC / AC-3 MP4 Container (embedded) Apple HTTP Live MPEG-4 AVC/AAC MPEG-2 Transport HTTP HTTP Yes [52] The content packager 303 may reformat, encode, and segment the requested content for delivery to the requesting user device. The post packaged output content file and/or fragment may be cached at content delivery network 305.
[53] Figure 6 illustrates an exemplary flow diagram in which dynamic content, which may be referred to as just-in-time content, may be received by a requesting device in accordance with an aspect of the disclosure. In Figure 6, at step 601 a content request may be received from a requesting device. Next, in step 603 a device geographical location and device profile may be determined for the requesting device. In an embodiment, the device profile may be determined from received device type information from the request or requesting device.
[54] At least one content packager 303 may be determined in step 604 for providing content to the requesting device. In an embodiment, the determined at least one content packager 303 may support a media player included in the requesting device as indicated in a device profile, or may support format of the content needed by the requesting device.
[55] In step 605, a content delivery route may be determined. The content delivery route may be determined from various different content routing routines. In an alternative embodiment, the content delivery route may be determined before a content packager is determined.
[56] In an embodiment, a content delivery route may be determined in accordance with the exemplary flow diagram shown in Figure 7. In Figure 7, at step 703 a determination may be made as to whether the requesting device is on/off the content provider's network.
Next, in step 705 resource availability for each determined at least one content packager may be determined.
[57] In step 707, availability of the requested content may be determined.
Next, in step 709 geographical proximity of a requesting device to a determined content packager may be determined to use as a factor in selecting a content delivery route.
[58] Referring again to Figure 6, in step 607, a discovery process may be executed to determine if the requested content resides in cache located on a determined content delivery route. If the requested content is stored in cache along a determined content delivery route, then the discovered requested content may be delivered to the requesting device from cache.
However, if the requested content is not stored along the content delivery route, then the process may continue to retrieve and package requested content.
[59] In an alternative embodiment, the discovery process may include other cache not located on the content delivery path. In an embodiment, a discovery process may include generating a list of content packagers throughout a network system that includes the requested content in cache. In an embodiment, the list may be ranked and evaluated for fulfilling different client content requests.
[60] In step 609, packaging metadata and encryption keys may be retrieved for use in fulfilling the content request. Next, in step 611 the requested content may be packaged and encrypted. The content may delivered to the requesting device along the determined content delivery route in step 613.
[61] Aspects of the disclosure have been described in terms of illustrative embodiments thereof.
While illustrative systems and methods as described herein embodying various aspects of the present disclosure are shown, it will be understood by those skilled in the art, that the disclosure is not limited to these embodiments. Modifications may be made by those skilled in the art, particularly in light of the foregoing teachings. For example, each of the features of the aforementioned illustrative examples may be utilized alone or in combination or subcombination with elements of the other examples. For example, any of the above described systems and methods or parts thereof may be combined with the other methods and systems or parts thereof described above. For example, one of ordinary skill in the art will appreciate that the steps illustrated in the illustrative figures may be performed in other than the recited order, and that one or more steps illustrated may be optional in accordance with aspects of the disclosure. It will also be appreciated and understood that modifications may be made without departing from the true spirit and scope of the present disclosure. The description is thus to be regarded as illustrative instead of restrictive on the present disclosure.
[211 As noted above, the central office 103 may include a variety of servers 105-107 that may be configured to perform various functions. For example, the central office 103 may include a push notification server 105. The push notification server 105 may generate push notifications to deliver data and/or commands to the various premises 102 in the network (or more specifically, to the devices in the premises 102 that are configured to detect such notifications). The central office 103 may also include a content server 106.
The content server 106 may be one or more computing devices that are configured to provide content to users in the homes. This content may be, for example, video on demand movies, television programs, songs, services, information, text listings, etc. In some embodiments, the content server 106 may include software to validate (or initiate the validation of) user identities and entitlements, locate and retrieve (or initiate the locating and retrieval of) requested content, encrypt the content, and initiate delivery (e.g., streaming, transmitting via a series of content fragments) of the content to the requesting user and/or device.
[221 The central office 103 may also include one or more application servers 107. An application server 107 may be a computing device configured to offer any desired service, and may run various languages and operating systems (e.g., servlets and JSP
pages running on Tomcat/MySQL, OSX, BSD, Ubuntu, Redhat, HTML5, JavaScript, AJAX and COMET). For example, an application server may be responsible for collecting television program listings information and generating a data download for electronic program guide listings. Another application server may be responsible for monitoring user viewing habits and collecting that information for use in selecting advertisements. Another application server may be responsible for formatting and inserting advertisements in a video stream and/or content item being transmitted to the premises 102.
[231 An example premises 102a may include a modem 110 (or another receiver and/or transmitter device suitable for a particular network), which may include transmitters and receivers used to communicate on the lines 101 and with the central office 103. The modem 110 may be, for example, a coaxial cable modem (for coaxial cable lines 101), a fiber interface node (for fiber optic lines 101), or any other desired modem device. The modem 110 may be connected to, or be a part of, a gateway interface device 111. The gateway interface device 111 may be a computing device that communicates with the modem 110 to allow one or more other devices in the home to communicate with the central office 103 and other devices beyond the central office. The gateway 111 may be a set-top box (STB), digital video recorder (DVR), computer server, or any other desired computing device. The gateway 111 may also include (not shown) local network interfaces to provide communication signals to other devices in the home (e.g., user devices), such as televisions 112, additional STBs 113, personal computers 114, laptop computers 115, wireless devices 116 (wireless laptops and netbooks, mobile phones, mobile televisions, personal digital assistants (PDA), etc.), and any other desired devices.
Examples of the local network interfaces may include Multimedia Over Coax Alliance (MoCA) interfaces, Ethernet interfaces, universal serial bus (USB) interfaces, wireless interfaces (e.g., IEEE 802.11), Bluetooth interfaces, and others.
[24] FIG. 2 illustrates general hardware elements that can be used to implement any of the various computing devices discussed herein. The computing device 200 may include one or more processors 201, which may execute instructions of a computer program to perform any of the features described herein. The instructions may be stored in any type of computer-readable medium or memory, to configure the operation of the processor 201. For example, instructions may be stored in a read-only memory (ROM) 202, random access memory (RAM) 203, removable media 204, such as a Universal Serial Bus (USB) drive, compact disk (CD) or digital versatile disk (DVD), floppy disk drive, or any other desired electronic storage medium. Instructions may also be stored in an attached (or internal) hard drive 205. The computing device 200 may include one or more output devices, such as a display 206 (or an external television), and may include one or more output device controllers 207, such as a video processor. There may also be one or more user input devices 208, such as a remote control, keyboard, mouse, touch screen, microphone, etc. The computing device 200 may also include one or more network interfaces, such as input/output circuits 209 (such as a network card) to communicate with an external network 210. The network interface may be a wired interface, wireless interface, or a combination of the two. In some embodiments, the interface 209 may include a modem (e.g., a cable modem), and network 210 may include the communication lines 101 discussed above, the external network 109, an in-home network, a provider's wireless, coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., a DOCSIS network), or any other desired network.
[25] The FIG. 2 example is an example hardware configuration. Modifications may be made to add, remove, combine, divide, etc. components as desired. Additionally, the components illustrated may be implemented using basic computing devices and components, and the same components (e.g., processor 201, storage 202, user interface 205, etc.) may be used to implement any of the other computing devices and components described herein. For example, the various components herein may be implemented using computing devices having components such as a processor executing computer-executable instructions stored on a computer-readable medium, as illustrated in FIG. 2.
[26] One or more aspects of the disclosure may be embodied in a computer-usable data and/or computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other data processing device. The computer executable instructions may be stored on one or more computer readable media such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc. As will be appreciated by one of skill in the art, the functionality of the program modules may be combined or distributed as desired in various embodiments. In addition, the functionality may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA), and the like. Particular data structures may be used to more effectively implement one or more aspects of the invention, and such data structures are contemplated within the scope of computer executable instructions and computer-usable data described herein.
[27] As discussed above, the central office of an information distribution network may transmit information downstream to various user devices. The transmitted information may include content for consumption (e.g., playback, viewing, listening, display, storage, etc.) by a user via user equipment, such as a gateway interface device (e.g., gateway interface device 111 of FIG. 1) and/or other computing device (e.g., televisions 112, additional STBs 113, personal computers 114, laptop computers 115, wireless devices 116 of FIG. 1). To assist in providing the content to a user, a content provider may implement in their distribution network an information distribution management system that includes one or more information distribution management devices (e.g., one or more servers and/or other devices) configured to perform various processes related to managing the providing of content to the user equipment (e.g., user device).
[28] For example, such managing may include requesting, creating and handling various sessions (e.g., user sessions, multicast group sessions, cache fill sessions, quality of service sessions); managing transmission of the content (e.g., managing the establishing of transmissions providing unicast content, such as on demand, and linear content, such as multicast content); monitoring usage data of the distribution network, and/or handling requests and notifications from user equipment. As another example, managing may include managing the content discovery, content locating and content delivery processes of the distribution network. In some embodiments, the managing may be implemented using IP (Internet Protocol) and/or HTTP (Hypertext Transfer Protocol) based processes.
For example, communication between various devices may be performed using HTTP
and/or IP packets. In one example, a session manager server may locate a streaming server and/or a multicast address for a particular content item, and may notify user equipment of the streaming server and/or multicast address for the particular content item using HTTP packets. The user equipment may receive the particular content item (via a unicast signal and/or a multicast signal) by receiving HTTP packets that include fragments of the content item and metadata identifying the streaming server and/or multicast address. In some embodiments, communication between devices may use only a single protocol (e.g., only HTTP packets or IP packets). Content items may also be transmitted using the single protocol (e.g., HTTP or IP packets including fragments of content items). Details of these processes, and others, will be discussed in further detail below.
[291 Content discovery processes may include supporting the discovery of content for various content items being provided by a distribution network. For example, content discovery processes may support the discovery of content items for multicast and/or linear transmission. In some embodiments, content discovery and the various related processes may use an HTTP-based approach (e.g., communication is via HTTP and/or IP
packets) that includes communication between user equipment, application servers, and other various servers of the central office.
[301 Content locating processes may include supporting the setup of various sessions and managing the resources of the information distribution network. In some embodiments, content locating processes may enforce entitlement procedures and digital rights management (DRM) licenses. Additionally, in some embodiments, content locating and the various related processes may use an HTTP based approach that includes communication between user equipment, session manager servers, and other servers of the central office.
[31] Content delivery processes may include supporting the streaming of the content items from various servers, such as a streaming server of the central office. In some embodiments, content delivery processes may enable user equipment to receive multicast signals (e.g., signals directed at a plurality and/or group of user equipment) and/or receive unicast signals (e.g., signals directed at a specific user device).
Additionally, in some embodiments, content streaming and the various related processes may use an HTTP
based approach that includes communication between user equipment, content servers, and other servers of the central office.
[32] Figure 3 illustrates an example system of components that may be implemented on the network 100, and which may be used to implement various features described herein to supply various content to users. The system may include one or more sources of the content. For example, in the case of video content (e.g., audiovideo content), there may be one or more video on demand (VOD) content encoders 301, each of which may include an application server (such as application server 107) configured to store video content such as movies, television shows, video clips, musical videos, etc.
The encoders 301 may include encoding hardware and/or software to provide content in a desired format, such as MPEG.
[331 The system may also include one or more linear content encoders 302.
Linear content encoders 302 may be similar to VOD content encoders 301, but may further be configured to supply content according to a predetermined schedule, as opposed to on demand. For example, the NBC content service may have one or more linear encoders 302 configured to supply a video stream of NBC scheduled video programming (e.g., the nightly news) at the appropriate time.
[34] The system may include one or more content packagers 303. In an embodiment, packager 303 may be included in premises gateway 311. The content packager 303 may be another application server, but configured to receive content and package it for delivery to users. This packaging may include, for example, reformatting the content (e.g., video resolution conversion, coder/decoder conversion, audio conversion, compression altering, synchronization, etc.), and segmenting the content (e.g., a two-hour movie may be divided into a plurality of discrete time segments for delivery).
In addition, packaging may include encrypting the content.
[35] The system may include a license server/key manager 304, which may be a server configured to manage content entitlement. For example, the manager 304 may contain encryption and/or decryption keys, and can supply those keys to content packager 303 for use in encrypting content for delivery. The manager 304 may also store information identifying users, and the level(s) of service to which the users are entitled, and may make determinations as to whether a particular user is actually entitled to receive a piece of requested content.
[36] Content delivery network 305 may be any desired type of communication network, such as network 109. The network 305 may span a large geographic area, and may be used to disseminate content or make content accessible. For example, some content may be supplied to. a streaming server 306. The streaming server 306 may be a server configured to receive packaged content, and generate a unicast stream of that content for delivery to a user.
[37] Another example may be a multicast server 307. Like the streaming server, multicast server 307 may also be configured to generate a stream of packaged content.
However, the multicast server's stream may be a multicast stream, configured to be received by a plurality of recipient users.
[38] The multicast server 307 may operate at the direction of a multicast controller 308, which may in turn communicate with a session manager 309 to establish multicast sessions for the delivery of various pieces of content. Session Manager 309 may be configured to manage one or more sessions of the distribution network by interfacing with various devices in the distribution network and communicating session information with the various devices. In some embodiments, the sessions that are managed by session manager 309 may include a user session, a multicast group session, a cache fill session, and/or a QoS flow session. For example, a user session may be created upon a user device requesting content, and may include information related to the requested content and the entitlements of the user device. A multicast group session may be created upon a user device joining a multicast group of a particular group of user equipment, and may include information related to the multicast group. A cache fill session may be created upon a user device requesting a cache fill of a particular content item being transmitted (e.g., multicast or unicast), and may include information related to the user device and the particular content item. A QoS flow session may be created based on the initiation of a transmission to a user device, and may include information related to the QoS
profile being enforced and the user device. Details of these sessions will be discussed in further detail below.
[39] The servers 306/307 may communicate with a termination system 310 (e.g., termination system 104) to ultimately deliver the content to a user's premises, or to a premises gateway 311 that can, in turn, supply content to various pieces of user equipment, such as a set-top box 312a, computer 312b, or any other desired display device or piece of user equipment.
[40] Other servers may be used as part of this delivery as well. For example, a quality of service (QoS) configuration manager 313 may be used to determine quality of service parameters for a given stream. As another example, a location resolution server 314 may contain geographic identification information for the various servers 306/307, termination servers 310, packagers 303, and other components in the system, and may be configured to determine which device(s) are closest geographically to a requesting user device.
Location resolution server 314 may be configured to determine location information for a particular user device. For example, in some embodiments, location resolution server 314 may receive a location request identifying a particular user device, determine geographic information (e.g., latitude and longitude) for the user device, determine whether the user device is on-network or off-network and transmit the information to the session manager 309. A user device being on-net may include user devices connected via termination systems (e.g., termination system 310) of the content provider. A
user device being off-net may include user devices (e.g., user equipment) connected via third party distribution networks that are not under the management or control of the session manager 309 and multicast controller 308.
[41] An entitlement resolution server 315 may be configured to validate a user device's entitlement to a particular content item. For example, in some embodiments, entitlement resolution server 315 may receive a validate entitlement request identifying a content item; determine whether a user device has a valid entitlement to the content item, based on user session information, content item information, and location information of the user device; and transmit the information indicating the result of the determination to the session manager 309. Entitlement resolution server 315 may also be configured to validate a user device's license to a particular content item. For example, in some arrangements, entitlement resolution server 315 may receive a validate license request identifying a content item, determine whether a user device has a valid license to the content item, based on user session information and content item information, and transmit information indicating the result of the determination to a license resolution server 316.
[42] License resolution server 316 may be configured to distribute licenses and/or distribute decryption and encryption keys. For example, in some embodiments, license resolution device 316 may distribute encryption keys to content packager 303 (or to license server/key manager 304). The license resolution server may also receive a license request from a user device; transmit a request to the entitlement resolution device to validate the license; and upon receiving an indication that the user device has a valid license, and transmit the license and one or more decryption keys to the user device.
[43] In an aspect of the disclosure, content packager 303 may receive content in a mezzanine or universal file format to be reformatted, encoded, and segmented based on a users request for content. The mezzanine or universal file format may comprise, for example, a MPEG-2 single program transport stream or a similar transport stream as described in ISO 13818-1. For instance, in an embodiment of the disclosure content packager may be functionally positioned at the ingress of content delivery network 305.
Positioning content packager 303 at the ingress of content delivery network 305 may allow for caching of the output stream of content packager 303 for fulfilling other user requests for the same content accessed by similar device types. Caching the output of content packager 303 upstream of content delivery network 305 may reduce overall load on content packager 303. In addition, caching the output upstream of content delivery network 305 may enable the cached content to be available to a larger pool of users that may be geographically distant. For instance, numerous users utilizing a particular smart phone may request a recent episode of a television series for viewing. These users may be geographically widespread as some may be located in Chicago, Illinois while others may be located in Tampa, Florida. The output requested from the first requesting user may be cached so that the next similar device type request from a user may be delivered from cache reducing overall load on content packager 303.
[44] Figure 4 illustrates content cache 402 which may be used to store output of content packager 303. Those skilled in the art will realize that content cache 402 may also be supplemented or physically placed within content delivery network 305. In addition, content cache 402 trough 409 may be part of a multi-tier caching structure. In an embodiment, each content cache 409-411 may be utilized for different geographical regions.
[45] In Figure 4, distribution system 400 may include one or more content packagers 303, 404, and 406. Each content packager 303, 404, and 406 may also be associated with different content caches 402, 405, and 407. In addition, content caches may be located across content delivery network 305 such as content caches 409 and 411. Based on a received device type, packaging of the requested content may be routed to the appropriate content packager 303, 404, and 406. Those skilled in the art will realize that additional content packagers 303 may be utilized to support different requesting device types. Each content packager 303 based on received or determined requesting device type may reformat the content, encrypt the content, and segment the content.
[46] In another aspect of the disclosure, content packager 303 may be functionally positioned at the egress of content delivery network 305 as shown in Figure 5.
Positioning content packager 303 at the egress of content delivery network 305 may allow all content delivered through the content delivery network 305 to be in a mezzanine or universal file format. In addition, a content packager 303 positioned at the egress of the content delivery network 305 may be very close to termination system 310 and premises gateway 311 which may support session based encryption for increased content security.
[47] Location resolution server 314 may be configured to determine location information for a particular user device. For example, location resolution server 314 may determine a requesting location for a user device requesting content delivery. The determined location of the requesting device may be used to determine an optimal content packager 303 and streaming server 306 to complete content delivery. In addition, alternative content packagers 303 and streaming servers 306 may be identified and/or utilized based on availability and utilization of all content packagers 303 and streaming servers 306. In an embodiment, an IP address or GPS data for a requesting device may be used to determine device location. For instance, some pieces of user equipment (312a and 312b) may contain GPS units. These devices may upon setup specify their coordinates such as longitude and latitude to allow the system to know the exact location of the user device.
[48] Content Router 317 may be configured to determine an optimal content delivery path for delivery of requested content. In an embodiment, session manager 309 along with content router 317 may consider specifications and utilization of content packagers 303 and content streamers 306 to determine an optional content delivery path. In another embodiment, based on the determined device types both ingress 303 and egress content packagers 303 may be utilized to provide optimal content delivery.
[49] Session manager 309 may also in some aspects of the disclosure communicate with premises gateway 311 in order to determine the devices types for various user equipment, e.g., CPE devices, such as 312a and 312b so that the optimal content packager 303 and content streamer 306 may be determined. For instance, premises gateway 311 may forward a setup session request from a CPE device to session manger 309. The setup session request may be used to validate a content purchase and return resource information to the CPE so that CPE can 1) obtain a list of content to access from a selected streaming server; 2) obtain a content manifest file; and 3) receive a DRM license and decryption key.
[50] Upon receiving a request for content, session manager 309 may retrieve requested content based on content packager 303 and content streamer 306 capabilities and configurations. Content packager 303 and content streamer 306 may be preselected at session startup for a particular CPE device. The session manger 309 and the content router 317 may provision target content format to either an ingress or egress content packager 303. Upon session startup for content consumption, a requesting user device may pull the content file and/or fragment from the content origin via content packager 303. The content packager 303 may retrieve the appropriate packaging metadata and encryption keys and begin the just-in-time packaging process.
[51] Table 1 illustrates an example of different media players that may be used on different devices along with their associated codecs and other properties which may be considered by content packager 303. Table 1 is merely illustrative and not meant to be an exhaustive list of devices and their associated properties.
Table 1 Player Codec Container Transport Stream Control Rate Adaptation QuickTime MPEG-4 AVC/AAC MP4 RTP over UDP/TCP RTSP No Streaming: RTMP Streaming: Yes Flash MPEG-4 AVC/AAC MP4 Progressive: HTTP N/A Progressive: No MS Window Media VC-1 ASF RTP over UDP/TCP RTSP No MS Silverlight MPEG-4 AVC/AAC MP4 (fragmented) HTTP HTTP (extension) Yes MS Mediaroom MPEG-4 AVC/AAC MPEG-2 Transport RTP/UDP (Linear) HTTP Yes RTP/HTTP (VOID) Move On2 VP7 N/A HTTP HTTP Yes Table 1 Player Codec Container Transport Stream Control Rate Adaptation RealVideo & RealVideo &
Real RDT (Proprietary) RTSP No RealAudio RealAudio Video: MPEG-2, HTTP
MPEG-2 Transport HTTP (extension) -DLNA MPEG-4 AVC RTP over UDP No Audio PCM, AC-3 MP4 (optional) proposed DVB MPEG-2 / AC-3 MPEG-2 Transport MPEG-2 transport N/A No MPEG-4 AVC / AC-3 MP4 Container (embedded) Apple HTTP Live MPEG-4 AVC/AAC MPEG-2 Transport HTTP HTTP Yes [52] The content packager 303 may reformat, encode, and segment the requested content for delivery to the requesting user device. The post packaged output content file and/or fragment may be cached at content delivery network 305.
[53] Figure 6 illustrates an exemplary flow diagram in which dynamic content, which may be referred to as just-in-time content, may be received by a requesting device in accordance with an aspect of the disclosure. In Figure 6, at step 601 a content request may be received from a requesting device. Next, in step 603 a device geographical location and device profile may be determined for the requesting device. In an embodiment, the device profile may be determined from received device type information from the request or requesting device.
[54] At least one content packager 303 may be determined in step 604 for providing content to the requesting device. In an embodiment, the determined at least one content packager 303 may support a media player included in the requesting device as indicated in a device profile, or may support format of the content needed by the requesting device.
[55] In step 605, a content delivery route may be determined. The content delivery route may be determined from various different content routing routines. In an alternative embodiment, the content delivery route may be determined before a content packager is determined.
[56] In an embodiment, a content delivery route may be determined in accordance with the exemplary flow diagram shown in Figure 7. In Figure 7, at step 703 a determination may be made as to whether the requesting device is on/off the content provider's network.
Next, in step 705 resource availability for each determined at least one content packager may be determined.
[57] In step 707, availability of the requested content may be determined.
Next, in step 709 geographical proximity of a requesting device to a determined content packager may be determined to use as a factor in selecting a content delivery route.
[58] Referring again to Figure 6, in step 607, a discovery process may be executed to determine if the requested content resides in cache located on a determined content delivery route. If the requested content is stored in cache along a determined content delivery route, then the discovered requested content may be delivered to the requesting device from cache.
However, if the requested content is not stored along the content delivery route, then the process may continue to retrieve and package requested content.
[59] In an alternative embodiment, the discovery process may include other cache not located on the content delivery path. In an embodiment, a discovery process may include generating a list of content packagers throughout a network system that includes the requested content in cache. In an embodiment, the list may be ranked and evaluated for fulfilling different client content requests.
[60] In step 609, packaging metadata and encryption keys may be retrieved for use in fulfilling the content request. Next, in step 611 the requested content may be packaged and encrypted. The content may delivered to the requesting device along the determined content delivery route in step 613.
[61] Aspects of the disclosure have been described in terms of illustrative embodiments thereof.
While illustrative systems and methods as described herein embodying various aspects of the present disclosure are shown, it will be understood by those skilled in the art, that the disclosure is not limited to these embodiments. Modifications may be made by those skilled in the art, particularly in light of the foregoing teachings. For example, each of the features of the aforementioned illustrative examples may be utilized alone or in combination or subcombination with elements of the other examples. For example, any of the above described systems and methods or parts thereof may be combined with the other methods and systems or parts thereof described above. For example, one of ordinary skill in the art will appreciate that the steps illustrated in the illustrative figures may be performed in other than the recited order, and that one or more steps illustrated may be optional in accordance with aspects of the disclosure. It will also be appreciated and understood that modifications may be made without departing from the true spirit and scope of the present disclosure. The description is thus to be regarded as illustrative instead of restrictive on the present disclosure.
Claims (6)
1. A method, comprising:
receiving, by a processor, a content request from a device;
determining, by the processor, a device profile for the device, the device profile indicating device capabilities for the device;
based on the received content request and determined device profile, determining, by the processor, at least one content packager for packaging the requested content;
determining, by the processor, a content delivery route;
retrieving packaging metadata and encryption keys for the requested content;
packaging the requested content; and delivering the requested content along the determined content delivery route to the device.
receiving, by a processor, a content request from a device;
determining, by the processor, a device profile for the device, the device profile indicating device capabilities for the device;
based on the received content request and determined device profile, determining, by the processor, at least one content packager for packaging the requested content;
determining, by the processor, a content delivery route;
retrieving packaging metadata and encryption keys for the requested content;
packaging the requested content; and delivering the requested content along the determined content delivery route to the device.
2. The method of claim 1, further comprising encrypting the requested content.
3. The method of claim 1, wherein determining the content delivery route further comprises determining resource availability of the content packager.
4. The method of claim 1, wherein determining the content delivery route further comprises determining content availability.
5. The method of claim 1, wherein determining the content packager further comprises:
determining based on the received content request and determined device profile, content packager capabilities for packaging the requested content.
determining based on the received content request and determined device profile, content packager capabilities for packaging the requested content.
6. The method of claim 1, further comprising determining a geographical location for the device.
8. A method, comprising:
receiving, by a processor, a content request from a device;
determining, by the processor, a device profile for the device, the device profile indicating device capabilities for the device;
based on the received content request and determined device profile, determining, by the processor, at least one content packager for packaging the requested content;
determining, by the processor, a content delivery route;
if the requested content is stored in cache along the determined content delivery route, delivering the requested content from the cache to the device; and if the requested content is not stored along the content delivery route, retrieving packaging metadata and encryption keys for the requested content;
packaging the requested content; and delivering the,requested content along the determined content delivery route to the device.
9. The method of claim 8, further comprising encrypting the requested content for delivery to the device.
10. The method of claim 8, wherein determining the content delivery route further comprises determining resource availability of the content packager.
11. The method of claim 8, wherein determining the content delivery route further comprises determining content availability 12. The method of claim 8, wherein determining the content packager further comprises:
determining based on the received content request and determined device profile, content packager capabilities for packaging the requested content.
13. The method of claim 8, further comprising determining a geographical location for the device.
14. The method of claim 8, wherein determining the content delivery route further comprises determining availability of content streamers along the content delivery route.
15. The method of claim 14, further comprising selecting a content streamer from the determined available content streamers for delivery of the requested content.
16. The method of claim 8, wherein determining the content delivery route further comprises determining on/off network status.
17. The method of claim 8, wherein determining the content delivery route further comprises determining proximity of content streamer to device.
18. An apparatus comprising:
at least one processor; and at least one memory having stored therein machine executable instructions, the at least one memory and stored instructions configured to, with the at least one processor, cause the apparatus to:
receive a content request from a device;
determine a device profile for the device, the device profile indicating device capabilities for the device;
based on the received content request and determined device profile, determine at least one content packager for packaging the requested content;
determine a content delivery route;
retrieve packaging metadata and encryption keys for the requested content;
package the requested content; and deliver the requested content along the determined content delivery route to the device.
19. The apparatus of claim 18, wherein the content packager comprises an ingress content packager.
20. The apparatus of claim 18, wherein the apparatus comprises a gateway device.
8. A method, comprising:
receiving, by a processor, a content request from a device;
determining, by the processor, a device profile for the device, the device profile indicating device capabilities for the device;
based on the received content request and determined device profile, determining, by the processor, at least one content packager for packaging the requested content;
determining, by the processor, a content delivery route;
if the requested content is stored in cache along the determined content delivery route, delivering the requested content from the cache to the device; and if the requested content is not stored along the content delivery route, retrieving packaging metadata and encryption keys for the requested content;
packaging the requested content; and delivering the,requested content along the determined content delivery route to the device.
9. The method of claim 8, further comprising encrypting the requested content for delivery to the device.
10. The method of claim 8, wherein determining the content delivery route further comprises determining resource availability of the content packager.
11. The method of claim 8, wherein determining the content delivery route further comprises determining content availability 12. The method of claim 8, wherein determining the content packager further comprises:
determining based on the received content request and determined device profile, content packager capabilities for packaging the requested content.
13. The method of claim 8, further comprising determining a geographical location for the device.
14. The method of claim 8, wherein determining the content delivery route further comprises determining availability of content streamers along the content delivery route.
15. The method of claim 14, further comprising selecting a content streamer from the determined available content streamers for delivery of the requested content.
16. The method of claim 8, wherein determining the content delivery route further comprises determining on/off network status.
17. The method of claim 8, wherein determining the content delivery route further comprises determining proximity of content streamer to device.
18. An apparatus comprising:
at least one processor; and at least one memory having stored therein machine executable instructions, the at least one memory and stored instructions configured to, with the at least one processor, cause the apparatus to:
receive a content request from a device;
determine a device profile for the device, the device profile indicating device capabilities for the device;
based on the received content request and determined device profile, determine at least one content packager for packaging the requested content;
determine a content delivery route;
retrieve packaging metadata and encryption keys for the requested content;
package the requested content; and deliver the requested content along the determined content delivery route to the device.
19. The apparatus of claim 18, wherein the content packager comprises an ingress content packager.
20. The apparatus of claim 18, wherein the apparatus comprises a gateway device.
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US24244409P | 2009-09-15 | 2009-09-15 | |
US24245609P | 2009-09-15 | 2009-09-15 | |
US61/242,456 | 2009-09-15 | ||
US61/242,444 | 2009-09-15 | ||
PCT/US2010/048975 WO2011034956A2 (en) | 2009-09-15 | 2010-09-15 | Dynamic content packaging |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2774363A1 true CA2774363A1 (en) | 2011-03-24 |
CA2774363C CA2774363C (en) | 2020-06-23 |
Family
ID=43759260
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2774480A Active CA2774480C (en) | 2009-09-15 | 2010-09-15 | Control plane architecture for multicast cache-fill |
CA2774363A Active CA2774363C (en) | 2009-09-15 | 2010-09-15 | Dynamic content packaging |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2774480A Active CA2774480C (en) | 2009-09-15 | 2010-09-15 | Control plane architecture for multicast cache-fill |
Country Status (4)
Country | Link |
---|---|
US (8) | US9456226B2 (en) |
EP (2) | EP2478454A4 (en) |
CA (2) | CA2774480C (en) |
WO (2) | WO2011034955A2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106534895A (en) * | 2016-11-01 | 2017-03-22 | 青岛海信电器股份有限公司 | Method for playing encrypted multimedia file and terminal |
US9609364B2 (en) | 2009-09-15 | 2017-03-28 | Comcast Cable Communications, Llc | Proximity dependent content delivery |
US11553018B2 (en) | 2014-04-08 | 2023-01-10 | Comcast Cable Communications, Llc | Dynamically switched multicast delivery |
Families Citing this family (110)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9432433B2 (en) | 2006-06-09 | 2016-08-30 | Qualcomm Incorporated | Enhanced block-request streaming system using signaling or block creation |
US10410222B2 (en) | 2009-07-23 | 2019-09-10 | DISH Technologies L.L.C. | Messaging service for providing updates for multimedia content of a live event delivered over the internet |
US9917874B2 (en) | 2009-09-22 | 2018-03-13 | Qualcomm Incorporated | Enhanced block-request streaming using block partitioning or request controls for improved client-side handling |
JP2011087033A (en) * | 2009-10-14 | 2011-04-28 | Sanyo Electric Co Ltd | Content reproduction device |
GB201105502D0 (en) | 2010-04-01 | 2011-05-18 | Apple Inc | Real time or near real time streaming |
TWI451279B (en) * | 2010-04-07 | 2014-09-01 | Apple Inc | Content access control for real-time or near real-time streaming |
US8910295B2 (en) * | 2010-11-30 | 2014-12-09 | Comcast Cable Communications, Llc | Secure content access authorization |
TWI434189B (en) * | 2010-12-10 | 2014-04-11 | Miiicasa Holding Cayman Inc | File access and sharing system and its method |
US9118432B2 (en) * | 2011-03-31 | 2015-08-25 | CSC Holdings, LLC | Systems and methods for real time media consumption feedback |
US8869217B2 (en) * | 2011-05-12 | 2014-10-21 | Cable Television Laboratories, Inc. | Media files delivery system and method |
US9264508B2 (en) * | 2011-08-19 | 2016-02-16 | Time Warner Cable Enterprises Llc | Apparatus and methods for reduced switching delays in a content distribution network |
WO2013085920A2 (en) | 2011-12-06 | 2013-06-13 | DISH Digital L.L.C. | Remote storage digital video recorder and related operating methods |
US9049484B2 (en) | 2011-12-06 | 2015-06-02 | Echostar Technologies L.L.C. | Efficient assignment of program copies in a network digital video recorder |
EP2605469A1 (en) * | 2011-12-13 | 2013-06-19 | Thomson Licensing | Method and apparatus to control a multipath adaptive streaming session |
WO2013127459A1 (en) * | 2012-03-01 | 2013-09-06 | Telefonaktiebolaget L M Ericsson (Publ) | Mixer for providing media streams towards a plurality of endpoints whereby the media streams originating from one or more media source and method therefore |
US8996519B2 (en) * | 2012-03-12 | 2015-03-31 | Oracle International Corporation | Automatic adaptive content delivery |
US8811258B2 (en) * | 2012-04-13 | 2014-08-19 | Intel Corporation | Enhanced local communications in mobile broadband networks |
US9538183B2 (en) | 2012-05-18 | 2017-01-03 | Home Box Office, Inc. | Audio-visual content delivery with partial encoding of content chunks |
US9071453B2 (en) | 2012-06-11 | 2015-06-30 | Apple Inc. | Location-based device automation |
US9516477B2 (en) | 2012-07-23 | 2016-12-06 | Samsung Electronics Co., Ltd | Method and system for delivering multimedia content cached in wireless cellular network nodes using multimedia broadcast multicast services (MBMS) |
US9584573B2 (en) * | 2012-08-29 | 2017-02-28 | Ericsson Ab | Streaming policy management system and method |
US9167042B1 (en) * | 2012-09-10 | 2015-10-20 | Amazon Technologies, Inc. | Maintaining communication channel for device notifications |
JP6079121B2 (en) * | 2012-10-11 | 2017-02-15 | 富士通株式会社 | COMMUNICATION SYSTEM, MANAGEMENT DEVICE, BASE STATION, COMMUNICATION DEVICE, AND COMMUNICATION PATH CONTROL METHOD |
US9727321B2 (en) | 2012-10-11 | 2017-08-08 | Netflix, Inc. | System and method for managing playback of streaming digital content |
US9565475B2 (en) | 2012-10-11 | 2017-02-07 | Netflix, Inc. | System and method for managing playback of streaming digital content |
US9716916B2 (en) | 2012-12-28 | 2017-07-25 | Echostar Technologies L.L.C. | Adaptive multicast delivery of media streams |
US10051025B2 (en) | 2012-12-31 | 2018-08-14 | DISH Technologies L.L.C. | Method and apparatus for estimating packet loss |
US10708319B2 (en) | 2012-12-31 | 2020-07-07 | Dish Technologies Llc | Methods and apparatus for providing social viewing of media content |
US10104141B2 (en) | 2012-12-31 | 2018-10-16 | DISH Technologies L.L.C. | Methods and apparatus for proactive multi-path routing |
US9317188B2 (en) * | 2013-03-15 | 2016-04-19 | Arris Enterprises, Inc. | Devices and methods for providing navigation images associated with adaptive bit rate video content |
US9066153B2 (en) * | 2013-03-15 | 2015-06-23 | Time Warner Cable Enterprises Llc | Apparatus and methods for multicast delivery of content in a content delivery network |
US20140279047A1 (en) * | 2013-03-15 | 2014-09-18 | General Instrument Corporation | Enhancing targeted advertising in a home network gateway device |
US9402107B2 (en) | 2013-03-15 | 2016-07-26 | Time Warner Cable Enterprises Llc | Apparatus and methods for delivery of multicast and unicast content in a content delivery network |
EP2793475A1 (en) * | 2013-03-15 | 2014-10-22 | Ricoh Company, Ltd. | Distribution control system, distribution control method, and computer-readable storage medium |
EP2785006A1 (en) * | 2013-03-28 | 2014-10-01 | British Telecommunications public limited company | Content delivery system and method |
US9813741B2 (en) * | 2013-04-05 | 2017-11-07 | Sony Corporation | Controller, control method, computer program, and video transmission system |
US9973559B2 (en) * | 2013-05-29 | 2018-05-15 | Avago Technologies General Ip (Singapore) Pte. Ltd. | Systems and methods for presenting content streams to a client device |
EP2819420A1 (en) * | 2013-06-25 | 2014-12-31 | British Telecommunications public limited company | Content distribution system and method |
EP2819419A1 (en) | 2013-06-25 | 2014-12-31 | British Telecommunications public limited company | Content distribution system and method |
EP2819364A1 (en) | 2013-06-25 | 2014-12-31 | British Telecommunications public limited company | Content distribution system and method |
ITMI20131710A1 (en) * | 2013-10-15 | 2015-04-16 | Sky Italia S R L | "ENCODING CLOUD SYSTEM" |
US10108692B1 (en) * | 2013-10-15 | 2018-10-23 | Amazon Technologies, Inc. | Data set distribution |
US10148448B2 (en) * | 2013-11-22 | 2018-12-04 | Arris Enterprises Llc | Control messaging in a cable network |
US11477538B2 (en) * | 2013-12-05 | 2022-10-18 | Time Warner Cable Enterprises Llc | Methods and apparatus that support delivery of targeted advertising content via a secondary channel |
US10154110B2 (en) * | 2014-04-22 | 2018-12-11 | Qwilt, Inc. | System and methods thereof for delivery of popular content using a multimedia broadcast multicast service |
US10423982B2 (en) | 2014-05-19 | 2019-09-24 | Allstate Insurance Company | Content output systems using vehicle-based data |
US10133530B2 (en) | 2014-05-19 | 2018-11-20 | Allstate Insurance Company | Electronic display systems connected to vehicles and vehicle-based systems |
US9293042B1 (en) | 2014-05-19 | 2016-03-22 | Allstate Insurance Company | Electronic display systems connected to vehicles and vehicle-based systems |
US11127042B2 (en) | 2014-05-19 | 2021-09-21 | Allstate Insurance Company | Content output systems using vehicle-based data |
US10708651B2 (en) * | 2014-06-04 | 2020-07-07 | Comcast Cable Communications, Llc | Dynamic content ratings |
US10057618B2 (en) | 2014-06-06 | 2018-08-21 | Microsoft Technology Licensing, Llc | System for filtering media manifests using manifest attributes |
US9924239B2 (en) * | 2014-06-10 | 2018-03-20 | Gilat Satellite Networks Ltd. | Video on demand over satellite |
KR101650756B1 (en) * | 2014-08-05 | 2016-08-24 | 삼성에스디에스 주식회사 | QoS-Guaranteed Video Stream Method and System, Transmitting Server |
US9584836B2 (en) * | 2014-09-03 | 2017-02-28 | International Business Machines Corporation | Mobility enhanced advertising on internet protocol television |
US11917002B2 (en) * | 2014-10-14 | 2024-02-27 | Comcast Cable Communications, Llc | Manipulation and recording of content transmissions |
US11943289B2 (en) | 2014-10-14 | 2024-03-26 | Comcast Cable Communications, Llc | Manipulation of content transmissions |
US9858195B2 (en) | 2014-12-10 | 2018-01-02 | International Business Machines Corporation | Near-cache distribution of manifest among peer applications in in-memory data grid (IMDG) non structured query language (NO-SQL) environments |
US9407968B2 (en) * | 2014-12-22 | 2016-08-02 | Verizon Patent And Licensing Inc. | Multicast and unicast adaptive bitrate services |
US9961004B2 (en) * | 2015-02-18 | 2018-05-01 | Viasat, Inc. | Popularity-aware bitrate adaptation of linear programming for mobile communications |
US10432688B2 (en) | 2015-03-13 | 2019-10-01 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for optimized delivery of live ABR media |
US10735823B2 (en) * | 2015-03-13 | 2020-08-04 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for optimized delivery of live ABR media |
US9621933B2 (en) * | 2015-03-27 | 2017-04-11 | Ericsson Ab | System and method for providing VOD content in a switched digital video network using unicast ABR streaming |
US9843828B2 (en) | 2015-03-27 | 2017-12-12 | Ericsson Ab | System and method for providing non-guaranteed channel content in a switched digital video network using multicast ABR streaming |
US9788028B2 (en) * | 2015-03-27 | 2017-10-10 | Ericsson Ab | System and method for providing guaranteed channel content in a switched digital video network using multicast ABR streaming |
US10069738B2 (en) * | 2015-04-01 | 2018-09-04 | At&T Intellectual Property I, L.P. | One cellular radio to support multiple phone lines and data at a location |
US9414095B1 (en) | 2015-04-10 | 2016-08-09 | Ses S.A. | Linear video distribution methods, systems, and devices |
US10191949B2 (en) | 2015-06-18 | 2019-01-29 | Nbcuniversal Media, Llc | Recommendation system using a transformed similarity matrix |
US9788053B2 (en) * | 2015-09-09 | 2017-10-10 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (MABR) streaming network using HTTP download segment recovery in a dedicated bandwidth pipe |
US9942290B2 (en) | 2015-09-09 | 2018-04-10 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (MABR) streaming network using HTTP download segment recovery in a shared progressive ABR download pipe |
US9774889B2 (en) * | 2015-09-10 | 2017-09-26 | Verizon Patent And Licensing Inc. | Content delivery network integration for home media client content |
US10397631B2 (en) * | 2015-10-23 | 2019-08-27 | At&T Intellectual Property I, L.P. | Method and apparatus for flexible consumption of media content |
US10313391B1 (en) * | 2015-10-30 | 2019-06-04 | Cyberinc Corporation | Digital distillation |
US10320809B1 (en) * | 2015-10-30 | 2019-06-11 | Cyberinc Corporation | Decoupling rendering engine from web browser for security |
CA3010038C (en) | 2015-12-29 | 2020-09-22 | DISH Technologies L.L.C. | Methods and systems for adaptive content delivery |
EP3373577B1 (en) * | 2015-12-30 | 2023-08-30 | Huawei Technologies Co., Ltd. | Multicast profile switching method, device and system |
US11146865B2 (en) | 2016-03-03 | 2021-10-12 | Comcast Cable Communications, Llc | Determining points of interest in a content item |
US10614088B2 (en) * | 2016-04-11 | 2020-04-07 | International Business Machines Corporation | Assessing value of one or more data sets in the context of a set of applications |
US10404541B2 (en) | 2016-07-07 | 2019-09-03 | Ericsson Ab | Smart data cap avoidance with personalized predictions based on linear regression or historical usage alpha-generation patterns |
US10104413B2 (en) * | 2016-07-07 | 2018-10-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Bandwidth and ABR video QoE management based on OTT video providers and devices |
US10523451B2 (en) | 2016-07-07 | 2019-12-31 | Telefonaktiebolaget Lm Ericsson (Publ) | System, apparatus, and method providing data cap avoidance |
US9888278B2 (en) * | 2016-07-07 | 2018-02-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Bandwidth and ABR video QoE management based on OTT video providers and devices |
US10911804B2 (en) * | 2016-08-17 | 2021-02-02 | Nec Corporation | Bitrate instruction device, bitrate instruction method, and non-transitory recording medium |
CA3037294C (en) * | 2016-09-16 | 2022-08-16 | Allstate Insurance Company | Electronic display systems connected to vehicles and vehicle-based systems |
US11317171B2 (en) | 2016-09-30 | 2022-04-26 | British Telecommunications Public Limited Company | Viewer importance adaptive bit rate delivery |
EP3520421B1 (en) | 2016-09-30 | 2023-03-22 | British Telecommunications public limited company | Viewer importance adaptive bit rate delivery |
US10191990B2 (en) | 2016-11-21 | 2019-01-29 | Comcast Cable Communications, Llc | Content recommendation system with weighted metadata annotations |
US10063902B2 (en) * | 2016-12-22 | 2018-08-28 | Cisco Technology, Inc. | ABR network profile selection engine |
EP3588847A4 (en) * | 2017-02-22 | 2020-12-23 | LG Electronics Inc. -1- | Multicast signal transmitting and receiving method and device |
US10958951B2 (en) * | 2017-03-10 | 2021-03-23 | Sling Media Pvt. Ltd. | Media session management |
US10958948B2 (en) | 2017-08-29 | 2021-03-23 | Charter Communications Operating, Llc | Apparatus and methods for latency reduction in digital content switching operations |
US10461884B2 (en) | 2017-10-05 | 2019-10-29 | Comcast Cable Communications, Llc | Server selected variable bitrate streaming |
US10382822B2 (en) * | 2017-12-28 | 2019-08-13 | Dish Network L.L.C. | Device resource management during video streaming and playback |
US10571991B2 (en) | 2018-04-30 | 2020-02-25 | Centurylink Intellectual Property Llc | Method and system for implementing auto-switching or auto-playing video content |
US20190335228A1 (en) * | 2018-04-30 | 2019-10-31 | Centurylink Intellectual Property Llc | Method and System for Implementing Auto-Switching or Auto-Playing Video Content |
US10631061B2 (en) | 2018-04-30 | 2020-04-21 | Centurylink Intellectual Property Llc | System and method for displaying and interacting with notifications |
US10924775B2 (en) * | 2018-06-26 | 2021-02-16 | Qualcomm Incorporated | Uplink and downlink methods for efficient operation of live uplink streaming services |
US10979248B1 (en) * | 2018-12-26 | 2021-04-13 | Open Invention Network Llc | Onboarding a VNF which includes a VNFC composed of manageable software elements |
US11102319B2 (en) * | 2019-01-29 | 2021-08-24 | Wangsu Science and Technology Co., Ltd. | Method, system and server for stream-pushing |
CN113132765A (en) * | 2020-01-16 | 2021-07-16 | 北京达佳互联信息技术有限公司 | Code rate decision model training method and device, electronic equipment and storage medium |
US11310568B2 (en) * | 2020-05-05 | 2022-04-19 | Panasonic Avionics Corporation | Systems and methods for securely providing preview samples of media content distributed to in-flight entertainment systems |
US11947637B2 (en) | 2020-05-28 | 2024-04-02 | Comcast Cable Communications, Llc | Authorization of access rights licenses |
US20230275949A1 (en) * | 2020-06-30 | 2023-08-31 | Lg Electronics Inc. | Method and apparatus for processing multicast signal |
WO2022037798A1 (en) * | 2020-08-18 | 2022-02-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Estimating video resolution delivered by an encrypted video stream |
WO2022087946A1 (en) * | 2020-10-29 | 2022-05-05 | Comcast Cable Communications, Llc | Generating unique identifiers |
EP4243429A1 (en) * | 2020-11-03 | 2023-09-13 | LG Electronics Inc. | Method and apparatus for processing multicast signal |
US11664923B2 (en) * | 2021-05-12 | 2023-05-30 | T-Mobile Usa, Inc. | Optimizing use of existing telecommunication infrastructure for wireless connectivity |
US20230199015A1 (en) * | 2021-12-20 | 2023-06-22 | Noname Gate Ltd | System and method for contextual misconfiguration detection |
JP7123517B1 (en) * | 2021-12-20 | 2022-08-23 | 一般社団法人日本ケーブルラボ | Core system device, terminal, system, program and method for delivering content by broadcast and unicast |
WO2024056452A1 (en) * | 2022-09-12 | 2024-03-21 | British Telecommunications Public Limited Company | Multicast join policy |
WO2024056455A1 (en) * | 2022-09-12 | 2024-03-21 | British Telecommunications Public Limited Company | Multicast leave policy |
Family Cites Families (75)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5694546A (en) * | 1994-05-31 | 1997-12-02 | Reisman; Richard R. | System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list |
US7529856B2 (en) * | 1997-03-05 | 2009-05-05 | At Home Corporation | Delivering multimedia services |
US6112239A (en) * | 1997-06-18 | 2000-08-29 | Intervu, Inc | System and method for server-side optimization of data delivery on a distributed computer network |
EP1022875B1 (en) * | 1999-01-25 | 2005-06-01 | Nippon Telegraph and Telephone Corporation | Push network |
US9538386B2 (en) | 1999-11-24 | 2017-01-03 | Robert C. Yen | Wireless internet access with enhanced bandwidth capabilities |
US20060259926A1 (en) * | 2000-07-20 | 2006-11-16 | Digital Deck, Inc. | Adaptable programming guide for networked devices |
WO2002017213A2 (en) * | 2000-08-18 | 2002-02-28 | International Business Machines Corporation | Server-side optimization of content delivery to clients by selective in-advance delivery |
US8527639B1 (en) | 2000-08-18 | 2013-09-03 | Cisco Technology, Inc. | Content server selection for accessing content in a content distribution network |
JP2002189801A (en) * | 2000-12-21 | 2002-07-05 | Sony Corp | Service providing system, management server, service provider, terminal device, storage medium issuing device, service providing method, and storage medium |
US7587500B2 (en) | 2001-01-10 | 2009-09-08 | Xcelera | Distributed selection of a content server |
US7421411B2 (en) | 2001-07-06 | 2008-09-02 | Nokia Corporation | Digital rights management in a mobile communications environment |
US20030028890A1 (en) | 2001-08-03 | 2003-02-06 | Swart William D. | Video and digital multimedia acquisition and delivery system and method |
US7428725B2 (en) * | 2001-11-20 | 2008-09-23 | Microsoft Corporation | Inserting devices specific content |
JP2004013283A (en) * | 2002-06-04 | 2004-01-15 | Hitachi Ltd | Method and apparatus for distributing content |
US7233790B2 (en) | 2002-06-28 | 2007-06-19 | Openwave Systems, Inc. | Device capability based discovery, packaging and provisioning of content for wireless mobile devices |
US7734684B2 (en) * | 2002-09-26 | 2010-06-08 | Haivision Network Video Inc. | Digital content delivery and viewing system and method |
US9108107B2 (en) * | 2002-12-10 | 2015-08-18 | Sony Computer Entertainment America Llc | Hosting and broadcasting virtual events using streaming interactive video |
US7590704B2 (en) | 2004-01-20 | 2009-09-15 | Microsoft Corporation | Systems and methods for processing dynamic content |
US7362776B2 (en) | 2004-11-01 | 2008-04-22 | Cisco Technology, Inc. | Method for multicast load balancing in wireless LANs |
US20060117020A1 (en) | 2004-12-01 | 2006-06-01 | John Toebes | Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device |
US8352627B1 (en) * | 2005-03-23 | 2013-01-08 | Apple Inc. | Approach for downloading data over networks using automatic bandwidth detection |
US20070168523A1 (en) | 2005-04-11 | 2007-07-19 | Roundbox, Inc. | Multicast-unicast adapter |
AU2010201379B2 (en) * | 2010-04-07 | 2012-02-23 | Limelight Networks, Inc. | System and method for delivery of content objects |
US7567671B2 (en) * | 2005-06-10 | 2009-07-28 | Aniruddha Gupte | Encryption method and apparatus for use in digital distribution system |
US20070124201A1 (en) * | 2005-11-30 | 2007-05-31 | Hu Hubert C | Digital content access system and methods |
US8018964B2 (en) | 2005-12-16 | 2011-09-13 | Cisco Technology, Inc. | Multicast operations using prioritized state information |
US8146157B2 (en) * | 2005-12-19 | 2012-03-27 | Rockstar Bidco, LP | Method and apparatus for secure transport and storage of surveillance video |
CN1997014A (en) | 2006-01-05 | 2007-07-11 | 三星电子株式会社 | Streaming service providing method adaptive to dynamic network changes |
US8627390B2 (en) | 2006-02-01 | 2014-01-07 | Arris Solutions, Inc. | Method and device for providing programs to multiple end user devices |
CN101438256B (en) * | 2006-03-07 | 2011-12-21 | 索尼株式会社 | Information processing device, information communication system, information processing method |
US11477617B2 (en) * | 2006-03-20 | 2022-10-18 | Ericsson Evdo Inc. | Unicasting and multicasting multimedia services |
JP4624294B2 (en) * | 2006-03-31 | 2011-02-02 | Necカシオモバイルコミュニケーションズ株式会社 | Mobile communication terminal, content information server, and content list providing method |
US20070282959A1 (en) * | 2006-06-02 | 2007-12-06 | Stern Donald S | Message push with pull of information to a communications computing device |
US8185435B2 (en) | 2006-06-16 | 2012-05-22 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for facilitating content-based selection of long-tail business models and billing |
US20080141317A1 (en) | 2006-12-06 | 2008-06-12 | Guideworks, Llc | Systems and methods for media source selection and toggling |
US8713192B2 (en) | 2006-12-08 | 2014-04-29 | Yahoo! Inc. | System and method for routing streaming data requests |
US8995815B2 (en) | 2006-12-13 | 2015-03-31 | Quickplay Media Inc. | Mobile media pause and resume |
US20080160956A1 (en) * | 2006-12-22 | 2008-07-03 | Jackson Jonathan B | Method and system for delivering and/or displaying targeted content to a mobile handheld device |
US8479241B2 (en) | 2007-05-10 | 2013-07-02 | At&T Intellectual Property I, Lp | System and method to control communication of data |
US20120233644A1 (en) | 2007-06-05 | 2012-09-13 | Bindu Rama Rao | Mobile device capable of substantially synchronized sharing of streaming media with other devices |
US20090077254A1 (en) | 2007-09-13 | 2009-03-19 | Thomas Darcie | System and method for streamed-media distribution using a multicast, peer-to- peer network |
US20090106792A1 (en) * | 2007-10-22 | 2009-04-23 | Alcatel Lucent | Method and apparatus for advertisement and content distribution with customized commercial insertion during channel change |
EP2232365A4 (en) * | 2007-12-10 | 2013-07-31 | Deluxe Digital Studios Inc | Method and system for use in coordinating multimedia devices |
US8386629B2 (en) * | 2007-12-27 | 2013-02-26 | At&T Intellectual Property I, L.P. | Network optimized content delivery for high demand non-live contents |
US8427943B2 (en) | 2008-01-28 | 2013-04-23 | Cisco Technology, Inc. | Bandwidth-aware multicast load balancing on a multi-interface host |
EP2294733B1 (en) | 2008-06-05 | 2019-12-18 | Telefonaktiebolaget LM Ericsson (publ) | A method and equipment for providing unicast preparation for iptv |
US20090307758A1 (en) | 2008-06-05 | 2009-12-10 | Motorola, Inc. | Method and apparatus to facilitate using a multicast stream to provide on-demand streaming content |
KR101113061B1 (en) * | 2008-06-25 | 2012-04-12 | 엔조스탄카토 | Multifunction Apparatus for Telecommunications |
US9338407B2 (en) | 2008-07-17 | 2016-05-10 | At&T Intellectual Property I, Lp | Apparatus and method for presenting an electronic programming guide |
US8713627B2 (en) | 2008-08-14 | 2014-04-29 | Juniper Networks, Inc. | Scalable security services for multicast in a router having integrated zone-based firewall |
US8042143B2 (en) * | 2008-09-19 | 2011-10-18 | At&T Intellectual Property I, L.P. | Apparatus and method for distributing media content |
AU2010202034B1 (en) * | 2010-04-07 | 2010-12-23 | Limelight Networks, Inc. | Partial object distribution in content delivery network |
EP2173078A1 (en) * | 2008-10-01 | 2010-04-07 | Thomson Licensing | Network device and method for setting up an IPTV session |
US8548946B2 (en) * | 2008-10-14 | 2013-10-01 | Microsoft Corporation | Content package for electronic distribution |
US20100094962A1 (en) * | 2008-10-15 | 2010-04-15 | Patentvc Ltd. | Internet backbone servers with edge compensation |
US8385245B2 (en) | 2008-11-13 | 2013-02-26 | Cisco Technology, Inc. | System and method for multicasting in a network environment |
US20100153573A1 (en) * | 2008-12-12 | 2010-06-17 | At&T Intellectual Property I, L.P. | Methods and Apparatus to Provide Content |
EP2359573B1 (en) | 2008-12-18 | 2015-02-18 | Telefonaktiebolaget L M Ericsson (publ) | Method for content delivery involving a policy database |
US8027961B2 (en) * | 2009-02-27 | 2011-09-27 | Yahoo! Inc. | System and method for composite record keys ordered in a flat key space for a distributed database |
US8484458B2 (en) * | 2009-03-17 | 2013-07-09 | At&T Mobility Ii, Llc | System and method for secure transmission of media content |
US20100312857A1 (en) | 2009-06-05 | 2010-12-09 | Macrovision Solutions Corporation | System and method for enabling content aggregation by user proximity |
JP5340062B2 (en) | 2009-07-14 | 2013-11-13 | アラクサラネットワークス株式会社 | Network relay device and network system |
US20110051646A1 (en) | 2009-08-26 | 2011-03-03 | Rice Christopher T | Dynamic multicasting |
US9203816B2 (en) * | 2009-09-04 | 2015-12-01 | Echostar Technologies L.L.C. | Controlling access to copies of media content by a client device |
WO2011034955A2 (en) | 2009-09-15 | 2011-03-24 | Comcast Cable Communications, Llc | Control plane architecture for multicast cache-fill |
US20110119703A1 (en) | 2009-11-17 | 2011-05-19 | General Instrument Corporation | Method and apparatus for delivering sdv unicast programming with targeted advertising on a bandwidth-available basis |
US8306049B2 (en) * | 2010-02-22 | 2012-11-06 | Microsoft Corporation | Multicast subscription based on forward error correction |
US8819264B2 (en) | 2011-07-18 | 2014-08-26 | Verizon Patent And Licensing Inc. | Systems and methods for dynamically switching between unicast and multicast delivery of media content in a wireless network |
US8804721B2 (en) | 2011-08-31 | 2014-08-12 | International Business Machines Corporation | Multi-stream communication |
US9438883B2 (en) | 2012-04-09 | 2016-09-06 | Intel Corporation | Quality of experience reporting for combined unicast-multicast/broadcast streaming of media content |
US9113311B2 (en) * | 2012-05-09 | 2015-08-18 | Verizon Patent And Licensing Inc. | Multicast/broadcast content delivery based on feedback from a user device |
US9030988B2 (en) | 2012-06-29 | 2015-05-12 | Alcatel Lucent | Method and apparatus for switching between multicast/broadcast and unicast service |
US9402107B2 (en) | 2013-03-15 | 2016-07-26 | Time Warner Cable Enterprises Llc | Apparatus and methods for delivery of multicast and unicast content in a content delivery network |
US9215569B2 (en) | 2013-03-15 | 2015-12-15 | Cellco Partnership | Broadcast media content to subscriber group |
US9819953B2 (en) | 2013-12-31 | 2017-11-14 | International Business Machines Corporation | Decoding media streams within thresholds |
-
2010
- 2010-09-15 WO PCT/US2010/048974 patent/WO2011034955A2/en active Application Filing
- 2010-09-15 US US13/496,338 patent/US9456226B2/en active Active
- 2010-09-15 EP EP10817785.8A patent/EP2478454A4/en not_active Ceased
- 2010-09-15 EP EP10817786.6A patent/EP2478461A4/en not_active Ceased
- 2010-09-15 US US13/000,909 patent/US8681680B2/en active Active
- 2010-09-15 CA CA2774480A patent/CA2774480C/en active Active
- 2010-09-15 WO PCT/US2010/048975 patent/WO2011034956A2/en active Application Filing
- 2010-09-15 CA CA2774363A patent/CA2774363C/en active Active
-
2014
- 2014-02-12 US US14/179,171 patent/US9693079B2/en active Active
-
2015
- 2015-01-07 US US14/591,674 patent/US9609364B2/en active Active
-
2017
- 2017-02-10 US US15/429,248 patent/US10582226B2/en active Active
- 2017-05-24 US US15/604,110 patent/US10327012B2/en active Active
-
2019
- 2019-04-29 US US16/396,960 patent/US10856014B2/en active Active
-
2020
- 2020-10-15 US US17/071,146 patent/US20210105509A1/en active Pending
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9609364B2 (en) | 2009-09-15 | 2017-03-28 | Comcast Cable Communications, Llc | Proximity dependent content delivery |
US11553018B2 (en) | 2014-04-08 | 2023-01-10 | Comcast Cable Communications, Llc | Dynamically switched multicast delivery |
CN106534895A (en) * | 2016-11-01 | 2017-03-22 | 青岛海信电器股份有限公司 | Method for playing encrypted multimedia file and terminal |
Also Published As
Publication number | Publication date |
---|---|
US20170302732A1 (en) | 2017-10-19 |
WO2011034955A2 (en) | 2011-03-24 |
WO2011034956A2 (en) | 2011-03-24 |
US20150120961A1 (en) | 2015-04-30 |
US10856014B2 (en) | 2020-12-01 |
CA2774480C (en) | 2023-02-28 |
US9456226B2 (en) | 2016-09-27 |
US9693079B2 (en) | 2017-06-27 |
US10582226B2 (en) | 2020-03-03 |
EP2478454A4 (en) | 2015-07-29 |
US20110188439A1 (en) | 2011-08-04 |
US20210105509A1 (en) | 2021-04-08 |
CA2774480A1 (en) | 2011-03-24 |
EP2478454A2 (en) | 2012-07-25 |
EP2478461A2 (en) | 2012-07-25 |
EP2478461A4 (en) | 2015-03-04 |
CA2774363C (en) | 2020-06-23 |
US20200029101A1 (en) | 2020-01-23 |
US20140237534A1 (en) | 2014-08-21 |
US20120222063A1 (en) | 2012-08-30 |
US9609364B2 (en) | 2017-03-28 |
WO2011034955A3 (en) | 2014-03-20 |
US10327012B2 (en) | 2019-06-18 |
WO2011034956A3 (en) | 2014-03-20 |
US8681680B2 (en) | 2014-03-25 |
US20180048918A1 (en) | 2018-02-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10582226B2 (en) | Geography-based dynamic content packaging and delivery | |
US11418823B2 (en) | Delivering content | |
US20230216906A1 (en) | Dynamically Switched Multicast Delivery | |
US10764623B2 (en) | Method and system for media adaption | |
US8887214B1 (en) | System and method for unified metadata brokering and policy-based content resolution in a video architecture | |
US9749136B2 (en) | Method for watermarking content | |
US7945924B2 (en) | Detecting distribution of multimedia content | |
US10218756B2 (en) | Streamlined delivery of video content | |
EP3217670B1 (en) | Policy based transcoding | |
US20090144790A1 (en) | Broadcast receiver and method for receiving adaptive broadcast signal | |
US20200099729A1 (en) | Aligning content packager instances | |
US8468558B2 (en) | Method and apparatus for bandwidth consumption usage reporting of non-managed sources | |
US11671636B2 (en) | Per-segment parameters for content | |
US20220038789A1 (en) | Video content processing systems and methods | |
US10440097B1 (en) | Profile based streaming | |
US9531778B2 (en) | Message rate mixing for bandwidth management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request |
Effective date: 20150914 |