US20160316247A1 - Program and device class entitlements in a media platform - Google Patents

Program and device class entitlements in a media platform Download PDF

Info

Publication number
US20160316247A1
US20160316247A1 US14/829,142 US201514829142A US2016316247A1 US 20160316247 A1 US20160316247 A1 US 20160316247A1 US 201514829142 A US201514829142 A US 201514829142A US 2016316247 A1 US2016316247 A1 US 2016316247A1
Authority
US
United States
Prior art keywords
program
entitlements
entitlement
media
channel
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.)
Abandoned
Application number
US14/829,142
Other languages
English (en)
Inventor
Daniel Biagini
Mikhail Mikhailov
Kevin Ma
Prabhudev Navali
Robert Arritt
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ericsson AB
Original Assignee
Ericsson AB
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ericsson AB filed Critical Ericsson AB
Priority to US14/829,142 priority Critical patent/US20160316247A1/en
Priority to TW105112984A priority patent/TWI633781B/zh
Publication of US20160316247A1 publication Critical patent/US20160316247A1/en
Assigned to ERICSSON AB reassignment ERICSSON AB ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ARRITT, Robert, BIAGINI, DANIEL, MA, KEVIN, MIKHAILOV, MIKHAIL, NAVALI, PRABHUDEV
Abandoned legal-status Critical Current

Links

Images

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/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
    • H04N21/2662—Controlling the complexity of the video stream, e.g. by scaling the resolution or bitrate of the video stream based on the client capabilities
    • 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/09—Arrangements for device control with a direct linkage to broadcast information or to broadcast space-time; Arrangements for control of broadcast-related services
    • H04H60/14—Arrangements for conditional access to broadcast information or to broadcast-related services
    • 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/09—Arrangements for device control with a direct linkage to broadcast information or to broadcast space-time; Arrangements for control of broadcast-related services
    • H04H60/14—Arrangements for conditional access to broadcast information or to broadcast-related services
    • H04H60/23—Arrangements for conditional access to broadcast information or to broadcast-related services using cryptography, e.g. encryption, authentication, key distribution
    • 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
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • 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
    • H04N21/218—Source of audio or video content, e.g. local disk arrays
    • H04N21/2187—Live feed
    • 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 or manipulating encoded video stream scene graphs
    • H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • H04N21/23439—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements for generating different versions
    • 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 or manipulating encoded video stream scene graphs
    • H04N21/2347—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving video stream encryption
    • 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/254—Management at additional data server, e.g. shopping server, rights management server
    • H04N21/2541—Rights Management
    • 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/25816—Management of client data involving client authentication
    • 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/25866—Management of end-user data
    • H04N21/25875—Management of end-user data involving end-user authentication
    • 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/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H04N21/26258—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list
    • 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
    • H04N21/26606—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 for generating or managing entitlement messages, e.g. Entitlement Control Message [ECM] or Entitlement Management Message [EMM]
    • 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/4518—Management of client data or end-user data involving characteristics of one or more peripherals, e.g. peripheral type, software version, amount of memory available or display capabilities
    • 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/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
    • H04N21/4627—Rights management associated to the 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/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/64746—Control signals issued by the network directed to the server or the client
    • H04N21/64753—Control signals issued by the network directed to the server or the client directed to 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/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/65—Transmission of management data between client and server
    • H04N21/654—Transmission by server directed to the client
    • H04N21/6543—Transmission by server directed to the client for forcing some client operations, e.g. recording
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/835—Generation of protective data, e.g. certificates
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/835—Generation of protective data, e.g. certificates
    • H04N21/8352—Generation of protective data, e.g. certificates involving content or source identification data, e.g. Unique Material Identifier [UMID]
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/835—Generation of protective data, e.g. certificates
    • H04N21/8355—Generation of protective data, e.g. certificates involving usage data, e.g. number of copies or viewings allowed
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/845—Structuring of content, e.g. decomposing content into time segments
    • H04N21/8456—Structuring of content, e.g. decomposing content into time segments by decomposing the content in the time domain, e.g. in time segments

Definitions

  • the present disclosure generally relates to communication networks. More particularly, and not by way of any limitation, the present disclosure is directed to a system and method for providing program and device class entitlements in a media platform configured for adaptive bitrate (ABR) media distribution and delivery in a network environment.
  • ABR adaptive bitrate
  • a Content Delivery Network can be a large distributed system of servers deployed in multiple data centers connected to the Internet or other public/private communication network.
  • the goal of a CDN is to serve media content (e.g., video/audio/etc.) to User Equipment nodes (UEs) with high availability and high performance.
  • Media content e.g., video/audio/etc.
  • UEs User Equipment nodes
  • Example UEs that can receive media content are set-top-boxes, television, multimedia computers, and wireless terminals (e.g., smart phones and tablet computers).
  • Adaptive streaming technology is being implemented to handle increasing consumer demands for streaming content from Over The Top (OTT) applications on OTT content servers (e.g., broadcast and on demand movies/TV etc.) across one or more CDNs to UEs having widely differing performance and protocols.
  • Example adaptive streaming technology that continues to be developed includes Apple initiated HTTP Live Streaming (HLS) protocol, Microsoft initiated Smooth Streaming (SS) over HTTP protocol, Adobe initiated Dynamic Streaming protocol, and MPEG Dynamic Adaptive Streaming over HTTP (MPEG DASH) protocol, etc.
  • Adaptive streaming technology converts a source media content stream into a plurality of content streams having different coding bit rates.
  • a group of multiple bit rate content streams may be transcoded to provide a plurality of groups of multiple bit rate content streams having different distribution container formats that can be required by different streaming protocols used by UEs (e.g., HLS protocol, Smooth Streaming protocol, Dynamic Streaming protocol, MPEG DASH protocol, etc.).
  • UEs e.g., HLS protocol, Smooth Streaming protocol, Dynamic Streaming protocol, MPEG DASH protocol, etc.
  • a single group of multiple bitrate content streams can result in numerous groups of differently formatted multiple bit rate content streams that need to be distributed and stored at a central CDN server and/or distributed to Edge replication servers to enable high availability and high performance delivery to many different types of UEs.
  • An example adaptive streaming server system may be configured to accept media content from live sources and/or static file sources, e.g., online content providers such as Hulu®, Netflix®, YouTube®, or Amazon® Prime, etc.
  • Media content from live sources may comprise live programming captured relative to any type of event, e.g., sporting/entertainment/gaming events, concerts, live TV shows, live news broadcasting, etc.
  • the present patent disclosure is broadly directed to systems, methods, apparatuses, devices, and associated non-transitory computer-readable media for providing and effectuating program and device class entitlements in a media environment configured for, by way of illustration, ABR media distribution and/or delivery in a network environment as set forth in this and accompanying materials.
  • Embodiments set forth herein identify individual programs within a live channel and can apply a wide range of entitlements not only to the parent channel but also to each individual program within that channel.
  • the rules for an individual program if specified, take precedence over channel rules.
  • some entitlements depend on the particular user/subscriber, there are also content-specific entitlements that apply to content in general and do not depend on the user.
  • the content-specific entitlements for a program can be delivered in the generic manifest available on the CDN, rather than fetched by the client as part of the license, as in traditional DRM systems.
  • the manifest may contain a number of encrypted sets of entitlements, each targeted to a specific class of client devices. Each client selects the set of entitlements that matches the device on which the client is running.
  • a signal can be sent to the client when the client needs to take user/subscriber information into account when evaluating entitlements.
  • the client can proactively fetch entitlements from the DRM server by issuing an explicit request.
  • Entitlements delivered directly from the DRM server can either be combined with the entitlements delivered via the manifest or can provide stand-alone entitlements that override all other provided entitlements. All entitlements are delivered and used in a secure manner and cannot be tampered with by an attacker, either while in transit or while on the user device.
  • the list of entitlements supported in this manner is incomparably larger than those supported by traditional DRM systems and can include play count, activation time, expiration time, device type (phone/tablet/browser/STB), playback enabled/disabled on jailbroken devices, network connection type (3g/4g/wifi), hdmi/airplay enabled/disabled, in/out home, in/out country, stream count limits, minimum bitrate, maximum bitrate, fast-forward enabled/disabled, rewind enabled/disabled, maximum bitrate on a jailbroken device, minimum/maximum play position, maximum number of ads to play, session shift enabled/disabled, etc. New entitlements can be added as necessary or desired.
  • an embodiment of a method operable on a media platform for providing program entitlements in a broadcast stream comprises, inter alia, identifying a program within a received media stream for a channel; receiving entitlements associated with the program; and writing an entitlement block containing the entitlements into a manifest file for delivery to a media client in the broadcast stream.
  • an embodiment of a method operable on a media platform for providing program entitlements in a broadcast stream involves, inter alia, receiving channel entitlements for a channel in the broadcast stream; receiving program entitlements for a program provided on the channel; providing the channel entitlements to a media client responsive to a request for the channel; and providing the program entitlements to the media client prior to showing the program on the channel.
  • an embodiment of an apparatus for providing program entitlements in a broadcast stream comprises, inter alia, one or more processors operably coupled to a memory having a sequence of program instructions which, when executed by the one or more processors, perform the following: identifying a program within a received media stream for a channel; receiving entitlements associated with the program; and writing an entitlement block containing the entitlements into a manifest file for delivery to a media client in the broadcast stream of the channel.
  • FIG. 1 depicts an embodiment of a media environment wherein an embodiment of the present invention may be practiced
  • FIG. 2 depicts a block diagram of a client device wherein an embodiment of the present invention may be practiced
  • FIG. 3 depicts the data flow between components of the media environment according to an embodiment of the present patent application
  • FIG. 4 depicts communications between various components of the media environment according to an embodiment of the present patent application
  • FIGS. 5A-5C depict an illustrative method for providing program and device class entitlements to a media client according to an embodiment of the present patent application
  • FIGS. 6A-6B depict an illustrative method for providing program and device class entitlements to a media client according to an embodiment of the present patent application
  • FIG. 7A depicts an illustrative method for enforcing entitlements at a media client according to an embodiment of the present patent application
  • FIGS. 7B-7E depict additional aspects that can be practiced in combination with the method of FIG. 7A according to an embodiment of the present patent application;
  • FIG. 8A depicts an illustrative method for enforcing entitlements at a media client according to an embodiment of the present patent application
  • FIGS. 8B-8D depict additional aspects that can be practiced in combination with the method of FIG. 8A according to an embodiment of the present patent application;
  • FIG. 9 depicts a block diagram of an example network node in the implementation of FIG. 1 according to an embodiment of the present patent application.
  • FIG. 10 depicts a block diagram of an example set top box according to an embodiment of the present patent application.
  • FIG. 11 depicts a block diagram of an example mobile device or wireless UE device according to an embodiment of the present patent application.
  • Coupled may be used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, co-operate or interact with each other.
  • Connected may be used to indicate the establishment of communication, i.e., a communicative relationship, between two or more elements that are coupled with each other.
  • an element, component or module may be configured to perform a function if the element is capable of performing or otherwise structurally arranged to perform that function.
  • a network element or node may be comprised of one or more pieces of service network equipment, including hardware and software that communicatively interconnects other equipment on a network (e.g., other network elements, end stations, etc.), and is adapted to host one or more applications or services with respect to one or more subscribers.
  • some network elements may be disposed in a wireless/wireline telecommunications network or a cable provider network whereas other network elements may be disposed in a public packet-switched network infrastructure (e.g., the Internet or worldwide web, also sometimes referred to as the Cloud), private packet-switched network infrastructures such as Intranets and enterprise networks, as well as service provider network infrastructures, any of which may span or involve a variety of access networks and core networks in a hierarchical arrangement.
  • network elements hosting such digital content or assets may be disposed in suitable CDN infrastructures.
  • some network elements may comprise “multiple services network elements” that provide support for multiple network-based functions.
  • the terms “content” or “content file” as used in reference to at least some embodiments of the present patent disclosure may include digital assets and program assets such as any type of audio/video (NV) content or program segment, live streaming or static (e.g., recorded over-the-air free network TV shows or programs, pay TV broadcast programs via cable networks or satellite networks, free-to-air satellite TV shows, IPTV programs, etc.), OTT and VOD or Movie-on-Demand (MOD) shows or programs, time-shifted TV (TSTV) content, locally stored content or network-stored content, as well as other content assets provided by content publishers, owners or providers, including but not limited to software files, executable computer code or programs, online electronic games, Internet radio shows/programs, entertainment programs, educational programs, movies, music video programs, and the like.
  • NV audio/video
  • static e.g., recorded over-the-air free network TV shows or programs, pay TV broadcast programs via cable networks or satellite networks, free-to-air satellite TV shows, IPTV programs, etc.
  • the content may be delivered, received or provided to the UE devices using broadcast cable TV, local TV, switched digital video (SDV) TV, satellite TV, broadband Internet, via one or more ABR streaming technologies.
  • Example subscriber end stations or client devices may comprise any device configured to execute, inter alia, a streaming client application (e.g., an ABR streaming client application) for receiving content from one or more content providers, e.g., via a broadband access network.
  • a streaming client application e.g., an ABR streaming client application
  • Such client devices may therefore include set-top boxes (STBs) with or without integrated cable cards, TVs, personal/digital video recorders (PVR/DVRs), networked media projectors, portable laptops, netbooks, palm tops, tablets, smartphones, video phones, mobile/wireless user equipment, portable media players, portable gaming systems or consoles (such as the Wii®, Play Station 3®, etc.) and the like that may access or consume content/services provided via a suitable dynamic packager network architecture for purposes of one or more embodiments set forth herein.
  • STBs set-top boxes
  • PVR/DVRs personal/digital video recorders
  • networked media projectors portable laptops, netbooks, palm tops, tablets, smartphones, video phones, mobile/wireless user equipment, portable media players, portable gaming systems or consoles (such as the Wii®, Play Station 3®, etc.) and the like that may access or consume content/services provided via a suitable dynamic packager network architecture for purposes of one or more embodiments set forth herein.
  • One or more embodiments of the present patent disclosure may be implemented using different combinations of software, firmware, and/or hardware.
  • one or more of the techniques shown in the Figures may be implemented using code and data stored and executed on one or more electronic devices or nodes (e.g., a subscriber client device or end station, a network element, etc.).
  • Such electronic devices may store and communicate (internally and/or with other electronic devices over a network) code and data using computer-readable media, such as non-transitory computer-readable storage media (e.g., magnetic disks, optical disks, random access memory, read-only memory, flash memory devices, phase-change memory, etc.), transitory computer-readable transmission media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals), etc.
  • non-transitory computer-readable storage media e.g., magnetic disks, optical disks, random access memory, read-only memory, flash memory devices, phase-change memory, etc.
  • transitory computer-readable transmission media e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals
  • network elements may typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (e.g., non-transitory machine-readable storage media) as well as storage database(s), user input/output devices (e.g., a keyboard, a touch screen, a pointing device, and/or a display), and network connections for effectuating signaling and/or bearer media transmission.
  • the coupling of the set of processors and other components may be typically through one or more buses and bridges (also termed as bus controllers), arranged in any known (e.g., symmetric/shared multiprocessing) or heretofore unknown architectures.
  • the storage device or component of a given electronic device or network element may be configured to store code and/or data for execution on one or more processors of that element, node or electronic device for purposes of implementing one or more techniques of the present disclosure.
  • FIG. 1 depicts an embodiment of a media environment 100 wherein the present invention may be practiced.
  • Media platform 101 sits logically between a service provider's back office and client devices 103 , and provides live streaming media to client device 103 through CDNs such as CDN 106 .
  • the service provider's back office includes Content Management System (CMS) 108 , Subscriber Management Systems (SMS) 114 and Customer Care system 118 .
  • CMS 108 manages the acquisition of content and provides bookkeeping of digital assets and associated business rules and service profiles.
  • SMS 114 receives and stores all subscriber-related information and, in conjunction with a billing system, is the arbiter of which subscribers have access to specific elements of content.
  • CMS Content Management System
  • SMS Subscriber Management Systems
  • Customer Care system 118 provides billing and revenue management.
  • Each of these back office servers provides information that is critical to the real-time provisioning of streaming media to customers, but none have a presence in the video session setup path. Therefore, these servers are not aware of device authentication and runtime analytics, such as usage and actual device profile for client device 103 , to effectively enforce entitlements.
  • Media platform 101 provides integration of CMS, SMS and Customer Care functions into the authentication pathway for client devices and the delivery of live streaming media to those clients through Content Server (CS) 110 , Entitlement Director (ED) 116 , and Analytics Report Generator (ARG) respectively.
  • CS 110 , ED 116 and ARG 120 communicates with its respective back office functionality and also communicates with either Media Manager (MM) 112 A or Content Controller (CC) 122 .
  • MM Media Manager
  • CC Content Controller
  • Media Manager 112 A and its backup, MM 112 B act as an administrator to receive electronic programming data and subscriber information and authenticates user access based on correlating device, user and content rights.
  • Content Controller 122 is a DRM license server that interacts with client devices to support content delivery based on client requests and service mediation.
  • an external rights server can push rights information to MM 112 .
  • CC 122 can perform call outs to an external rights server in order to provide entitlements in response to client requests.
  • Media platform 101 also receives incoming media 130 for each provided channel from a content provider 102 , which may provide both stored VOD and live media.
  • one or more preparation processors (PP) 104 act on the incoming media 130 .
  • PP 104 can transcode ( 132 ) the media into multiple bitrates to support ABR delivery where necessary, segment ( 134 ) the media for transport, and encrypt ( 136 ) and upload ( 138 ) the segmented media for delivery to CDN 106 as processed media 140 that is ready for distribution on one or more channels of live streaming media.
  • CDN 106 streams the processed media to requesting client device 103 .
  • the final piece of media environment 100 is client device(s) 103 .
  • CC 122 interacts with numerous client devices.
  • the traditional client device for streaming media has been the STB for in-home television viewing.
  • client device 103 now includes unmanaged devices such as laptops, smartphones, tablets, smart TVs, game consoles and DVD players. Since these devices are not preregistered or preconfigured to receive subscribed services, service delivery to client device 103 must be dynamically detected, authenticated and controlled on demand based on their entitlement.
  • Client device 103 typically contains a media client 124 , which interacts with CC 122 , as well as media player 126 , which may be provided as part of the operating system of the client device.
  • media platform 101 is configured to support program entitlements for use during certain VOD playback modes (e.g., catch-up & network PVR (nPVR)) only.
  • media platform 101 is configured to provide support for media program based entitlements applied during live, e.g., linear, playback mode. Live program entitlements may be used to enforce playback business rules, which are required for compliance of content rights agreements.
  • program entitlements can be signaled to MC 124 for each program occurrence on the linear stream.
  • MC 124 is configured to dynamically update the current entitlement rule-set upon the start of the corresponding program and to trigger enforcement using the updated rules.
  • restrictions such as out-of-home playback are supported on a per program basis.
  • FIG. 2 provides a simplified block diagram of a client device 200 , such as client device 103 , showing the components involved in receipt and playback of streaming media, specifically Service Provider Application 202 , Media Client (MC) 220 and Media Player 242 .
  • SP Application 202 provides communication with a user through User Interface 204 , which supports login of the user and provides programming information to the user. In at least one embodiment SP Application 202 pairs itself with an STB; SP Application 202 can then determine whether client device 200 is in-home or -out-of-home and provide that information to MC 220 .
  • the Service Provider Application 202 also contains PVR Controls 206 , EPG Discovery 208 , Ad Delivery 210 and Portal Interface 212 .
  • Media client 220 which is one embodiment of media client 124 , manages authentication of client device 200 with media platform 101 , retrieves content, plays the content on media player 242 , and provides local enforcement of DRM through its connection to media player 242 , which is part of the operating system (OS) 240 of the client device 200 .
  • Media client 220 also contains modules to perform Device Management 222 , Entitlement Enforcement 224 , Analytics 226 , Ad Insertion 228 , CDN Selection 230 and Bandwidth Management 232 .
  • ABR Manifest File Control 234 receives the manifest file that is provided for a requested channel and is able to coordinate changes in the requested bitrate for streaming.
  • Transparent Data Proxy 236 provides connection between MC 220 and the Internet and ABR/DRM 238 communicates with CC 122 for authentication, exchanges channel information (including entitlements associated with the channel) and subscriber information with CC 122 , and when a subscriber override is in effect, requests entitlements for each program from CC 122 .
  • MC 220 can apply at least the following example program entitlements dynamically at program boundaries; in at least one embodiment, these entitlements can be based on device classification:
  • MC 220 is configured for this purposes to utilize a beaconing mechanism, i.e., keep-alive messaging that regularly exchanges information with CC 122 regarding, e.g., content consumption, user overrides, etc.
  • these entitlements can include at least:
  • a set of entitlements uses a 5-tuple that includes primary (a.k.a. account), user_token, device_id, media Unique Identification Number (UID) and media group to determine which entitlement properties or rights are applied to a given playback request.
  • primary a.k.a. account
  • user_token a.k.a. token
  • device_id a.k.a. token
  • media Unique Identification Number a.k.a. account
  • an additional entitlement targeting mechanism is provided to allow more granular application of program entitlements on specific types of devices, as well as the potential to apply other types of entitlements. This mechanism is similar to an MP Device Class object, which allows classification based on at least the following device attributes:
  • a mechanism is provided to force MC 124 to query CC 122 for entitlement updates on a per program basis.
  • MC 124 does not wait until the moment right before or after a program change occurs to callout to CC 122 for an entitlements update.
  • content owners can restrict certain content from being played from outside the home.
  • In-home-only playback can be controlled by at least the following two mechanisms:
  • Scalability of signaling for content program entitlements can be accomplished by limiting the amount of communication between MC 124 and CC 122 required for entitlements messaging. Embedding the entitlements, as well as any associated device classifiers, within the video stream, e.g., inline, in-band, or in-stream signaling, may advantageously provide the signaling of content entitlements without any additional MC-CC interactions.
  • Preparation processor video processing outputs a manifest file which contains stream metadata.
  • the manifest file is configured to deliver content entitlement and device classifying data to clients with minimal overhead on CC 122 .
  • the manifest file is also utilized to signal many value-added features, e.g. ad-insertion, parental controls, timeshifting features, etc.
  • manifests are provided in HLS m3u8 format; in at least one embodiment the manifest entitlement signaling approach is provided in MPEG DASH mpd files or extended to other manifest types.
  • FIG. 3 depicts an embodiment of the data flow between components of the media environment for program entitlement delivery.
  • Media Manager 112 , Content Controller 122 and Preparation Processor 104 are each part of media platform 101 , which is connected to both CDN 106 and Media Client 124 .
  • An external EPG data source 302 pushes program data and entitlement information into Media Manager 112 via a media/program Application Programming Interface (API) 310 .
  • a program scheduler (not specifically shown), which may be operating at or otherwise associated with MM 112 , is responsible for provisioning the next program at PP 104 .
  • a network node/functionality may be configured as a recorder, transcoder and uploader (RTU) (not specifically shown) associated with PP node 104 that is operative to fetch original content file from a remote system, transcode it into various bitrates appropriate for the target client platforms, and then upload transcoded and segmented files to a Content Distribution Network 304 or Origin Server.
  • the program scheduler can retrieve the corresponding entitlements, based on program media UID & program's media groups, and pass an entitlements “block” to the RTU via a ProgramInfo message over communication link 312 . This may occur for both Timeshift enabled channels (“out-of-band” segmentation) and legacy live streams.
  • the RTU functionality passes the ProgramInfo message to a segmenter process (not specifically shown), which may be operating at or otherwise associated with PP 104 .
  • the segmenter may be configured to write the entitlements into the manifest file. If the channel is running in program segmentation mode then the entitlements block may be placed at the top of the manifest file. If the channel is in sliding window mode the entitlements may be placed at the top of the file and after any program boundary indicators, including the program media UID, start/end times, and any program parental control rating that was passed.
  • the manifest file and video content is then sent to CDN 106 over communication link 314 .
  • MC 124 performs a playback request using a suitable “client/roll” API, shown as communication link 320 .
  • the DRM object that is returned from CC 122 contains the entitlements for the parent channel.
  • the object may also contain an additional override flag to support subscriber_check, a subscriber override option.
  • MC 124 is configured to retrieve entitlements for the next program via a DRM token retrieval API or a beacon API.
  • various MCs are configured to spread the next program entitlement lookup over different beacons to help spread the load out over the full program duration.
  • MC 124 parses ProgramInfo comments from the manifest file, and iterates through the entitlement objects, choosing the first object whose Device Class matches the local platform attributes. If subscriber_check is true, MC 220 calls client/token retrieval to retrieve the entitlements for the next program, preferably before the end_time of the current program. End_time and next program UID can both be found in the PROGRAM-INFO tag of the bitrate manifest files.
  • the DRM token retrieval API call shown as communication link 322 , may contain the media UID of the next program in order to retrieve the full set of entitlements for that next program.
  • the token retrieval API is configured to perform a subscriber/content entitlement merge for that program and return a single DRM Object with the corresponding rights and the first encryption key for the program. If key rotation is disabled, the key may be the same.
  • the RTU and segmenter adds the necessary Program-Info tag, including entitlements, to the manifest files when the Preparation Processor node 104 is operating in either packager or transcoder mode. Similar manifest entitlement support can also be added to a Just-In-Time Packager (JITP) manifest processing to allow for integrated Playback Business Rules (PBR) with suitable PP or packaging implementations.
  • JITP Just-In-Time Packager
  • PBR Playback Business Rules
  • the top of the manifest contains PROGRAM-INFO tags for 3 programs: previous, current and next.
  • Each PROGRAM-INFO can include at least the following information:
  • the manifest file is protected by manifest cryptographic signing and verification workflow.
  • MC 124 parses through the objects for the next program and select the first object which matches the local device characteristics.
  • the entitlements block includes multiple entitlement objects, each with an optional Device Class (DC) Target.
  • Each entitlement with an association to the program, either directly or via media group, can be merged using an exemplary entitlement rules precedence engine, e.g., wherein a lower priority numerical value indicates a higher rule precedence.
  • different DC targets do not merge into a single entitlement; instead each distinct DC target carries a merged entitlement set for the target.
  • multiple sets of merged entitlements for different DC targets are combined to form the entitlements block. Maintaining an existing DRM token object format can allow MC 124 to reuse existing parsing and handling code.
  • the combined Device Class and Entitlement object string has the following form:
  • the corresponding entitlement block for Prog1 may contain the following two Entitlement Objects, the first for DC1 and the second having a NULL DC (wildcard, applies to all):
  • MC 124 is responsible for parsing the encoded Device Class definitions of each Entitlement Object within the Entitlement Block until a match is found.
  • the first matching object in the block is chosen to provide the new set of entitlements to apply starting at the specified start time in the Program Info of the manifest file. If a signature hash is utilized, MC 124 is operable to determine whether the hash value for the next program is the same as the hash value for the current program. If the two values are equal, there is no change between the two sets of entitlements. In this embodiment, MC 124 is operable to skip parsing of the Entitlement Block and to apply the entitlements for the current program to the next program. In at least one embodiment, specific browsers and/or operating systems may be targeted using different targeting mechanisms.
  • Device Class encoding is in the form:
  • a subscriber override of content entitlements can be signaled by a property or parameter called, e.g., subscriber_check in a DRM Rights Object that is returned from the response to the client/roll API mentioned previously.
  • MC 124 can ignore the program entitlements contained within the manifest Entitlement Blocks.
  • MC 124 periodically utilizes an API to CC 122 to retrieve the computed entitlements for each program. The CC API call can be done at a random time before the start of the next program in order to amortize the load on CC 122 over the full time span of the current program.
  • DRM Agent 238 can use the entitlements for the channel as a fallback object if there is an error in the program entitlement from the manifest.
  • MC 124 refreshes rights via a token retrieval API call before each program boundary. This call may use a program_media_uid query string parameter to specify the program's media_uid.
  • media platform 101 and media client 124 are configured to support an application such as in/out home detection in order to enforce in-home-only playback restrictions.
  • FIG. 4 depicts an example architecture for facilitating in-home-only playback restrictions, wherein appropriate steps/blocks/acts may take place to effectuate the applicable restrictions.
  • an entitlement parameter or variable out_of home_blocked is used to transmit this feature.
  • the out_of home_blocked entitlement can be applied to targets similar to or compatible with an existing suite of entitlement properties. Operators can use the media/rights API to set this entitlement or use rights callout to return the property.
  • MC 124 handles out_of home_blocked property changes on a per program basis, signaled either through the manifest, via communication link 416 , or via the subscriber override mechanism, signaled via communication link 410 .
  • MC 124 can signal SP Application 202 when out_of home_blocked is true to enable SP Application 202 to provide in/out home detection. This signal is shown in the figure as communication link 412 .
  • SP Application 202 use an API called setHomeStatus( ) shown as communication 414 , to signal whether the client is in or out of home, allowing MC 124 and DRM Agent 238 to restrict or allow playback as appropriate.
  • MC 124 is configured to treat SP Application 202 as in-home, i.e., fail open, in the default state.
  • a media/rights API is configured to support device class targeting features set forth herein, as well as supporting desired additional entitlements.
  • the media/rights API is provided with the following signature, including one or more new parameters:
  • the following payload XML fields are configured to support new entitlements:
  • CC Rights callout payload response parsing can be configured to handle the inclusion of the additional rights properties such as, e.g., out_of_home_blocked and subscriber_check, as set forth hereinabove.
  • a CC DRM token retrieval API is used by MC 124 to retrieve media DRM tokens.
  • a request from MC 124 to CC 122 can be generated to retrieve media meta information along with entitlements and content decryption key, which can be referred to as a roll request.
  • the response from CC 122 is in XML, containing various pieces of information describing for MC 124 where to find media segments, what bitrates are available, etc.
  • entitlements and/or a content decryption key are contained in the encrypted DRM token returned in one of the XML tags.
  • FIGS. 5A-5C depict a series of flowcharts of an illustrative method at a network node for providing program and device class entitlements to a media client according to an embodiment of the present patent application.
  • Flowchart 500 A begins with a network node identifying ( 502 ) a program within a received media stream for a channel.
  • the node also receives ( 504 ) the entitlements associated with the program.
  • the entitlements can be received from a media source, e.g., at the time the media is received.
  • the node writes ( 506 ) an entitlement block containing the entitlements into a manifest file for delivery to a media client in the live broadcast stream.
  • entitlements associated with the channel are provided as shown in flowchart 500 B.
  • This aspect of the method includes receiving ( 512 ) entitlements associated with the channel and providing ( 514 ) the channel entitlements to a media client in response to receiving a playback request for the channel from the media client. In this manner, when a program's entitlements are missing or otherwise not available, the client is able to utilize the channel entitlements to enforce entitlements for the program.
  • the network node provides ( 522 ) a subscriber override indicator to a media client, e.g., the subscriber_check indicator provided with the channel manifest during communications between MC 124 and CC 122 .
  • the network node determines ( 524 ) whether an override entitlement request for a next program has been received from MC 220 . If not, the node continues to wait on a request. If a subscriber override request has been received, the network node then provides ( 526 ) the media client with override entitlements that are specific to the program and the media client.
  • FIGS. 6A-6B depict another series of flowcharts of an illustrative method at a network node for providing program entitlements to a media client according to an embodiment of the present patent application.
  • a network node receives ( 602 ) channel entitlements for a channel in the broadcast stream. These channel entitlements provide entitlements that apply to all programs on the channel.
  • the network node also receives ( 604 ) program entitlements for a program provided on the channel, e.g., by writing one or more entitlements into a manifest file.
  • the network node can receive these program entitlements for as many or as few programs as desired. Program entitlements, if provided, will override the channel entitlements.
  • the network node then ensures that the channel entitlements are provided ( 606 ) to a media client responsive to a request for the channel.
  • the channel entitlements are sent to CC 122 , which can provide the channel entitlements to MC 124 when a request to join a channel is received.
  • the node also ensures that program entitlements are provided ( 608 ) to the media client prior to showing the program on the channel.
  • the entitlement block is included in a manifest that is sent to CDN 106 . CDN 106 then provides the manifest and media to media client 124 at an appropriate time.
  • the ability to override the program manifest can be provided as shown in flowchart 600 B.
  • the network node such as CC 122 , provides ( 612 ) a subscriber override indicator to the media client, such as media client 124 .
  • the subscriber override indicator is provided to the media client when a new session begins, e.g., at the time a channel is requested.
  • the subscriber override indicator is provided in a beaconing message between, e.g., CC 122 and MC 124 .
  • the network node then waits to determine ( 614 ) whether an override entitlement request for a next program has been received from a media client. If not, the network node continues to wait, but if an override entitlement request has been received, the network node provides ( 616 ) the media client with override entitlements that are specific to the subscriber and the program.
  • FIG. 7A depicts flowchart 700 A, which is directed to a method operating on a user device for enforcing program entitlements in a broadcast stream.
  • a media client such as media client 124 , receives ( 702 ) a manifest for a program in the live broadcast stream; the manifest providing a program entitlement block. The media client then uses ( 706 ) the entitlements specified in the program entitlement block to enforce entitlements for the program.
  • FIGS. 7B-7E depict flowcharts 700 B- 700 E of additional aspects of the method that may be practiced in combination with the method of FIG. 7A .
  • the media platform can also provide channel entitlements that provide default entitlement values and override entitlements that can supersede the program entitlements, as well as using device class entitlements to provide multiple entitlement objects in the manifest. While it can be beneficial to practice all of these elements in a single embodiment, it is not necessary to do so. Accordingly, the process in the media client may proceed along several paths in dependence on which elements are included in any embodiment.
  • Flowchart 700 B deals with the use of a subscriber override.
  • media client 124 will receive ( 710 ) the indicator in a message from CC 122 , e.g., when a channel is requested.
  • the media client will determine ( 712 ) whether the subscriber override is in effect, e.g., whether the value of the indicator is “True”. If the subscriber override is not in effect, the method can move to either block 706 or block 722 , depending on the options used. If the subscriber override is in effect, the media client sends ( 714 ) an override entitlement request to a content controller node or other network node performing this function.
  • the media client will receive ( 716 ) override entitlements and will use ( 718 ) the override entitlements to enforce entitlements for the program.
  • Flowchart 700 C provides for the use of channel entitlements, such that not every program manifest needs to contain a program entitlement block. As will be understood, portions of flowchart 700 C logically precedes flowchart 700 A.
  • Media client receives ( 720 ) channel entitlements for the channel in which the program is broadcast. The channel entitlements can be received, e.g., during communications with CC 122 when the channel is requested.
  • the media client then receives ( 722 ) a manifest containing new program information.
  • the media client determines ( 724 ) whether the manifest file contains a program entitlement block. If the manifest file does contain a program entitlement block, the flow moves to either block 702 or block 732 , depending on options. If the manifest file does not contain a program entitlement block, the media client uses ( 726 ) the entitlements specified in the channel entitlement block to enforce digital rights for the program.
  • Flowchart 700 D provides for the use of device class entitlements, where multiple entitlement objects are provided in the program entitlement block, and can be entered from either block 702 or block 724 .
  • the media client determines whether the program entitlement block contains ( 732 ) multiple entitlement objects. If multiple entitlement objects are not present, the method moves to block 706 . If multiple entitlement objects are present, the media client selects ( 734 ) a first entitlement object that has a device class that matches the user device. The media client then uses ( 736 ) entitlements that are specified in the selected entitlement object to enforce entitlements for the program.
  • Flowchart 700 E is directed to the use of a hash code with the program entitlement block, which provides a method to streamline the process of implementing entitlements, by determining whether the program entitlement block has changed from the previous program.
  • a hash code is implemented, the content of each program entitlement block is used to create a respective hash code, which is transmitted with the program entitlement block.
  • all entitlements are encrypted when they are received by the media client to prevent user abuse of digital rights, so if it is determined that two hash codes are identical, there is no need to decrypt the entitlement block or to search for a matching device class.
  • This flow chart is entered after block 724 after an entitlement block for a second program has been received.
  • the media client determines ( 742 ) whether the hash code of the new program, which will be the next program to play, matches the hash code of the current program. If the hash codes do not match, the media client will move to one of blocks 706 or 732 . If the hash codes do match, the media client uses ( 746 ) the entitlements specified in the current entitlement block to enforce entitlements for the new program.
  • FIG. 8A depicts flowchart 800 A, which is directed to a method operating on a user device for enforcing program entitlement in a broadcast stream.
  • the media client receives ( 802 ) channel entitlements for a requested channel in the broadcast stream.
  • the channel entitlements can be received, e.g., at the time the channel is requested from the content controller node.
  • the media client also receives ( 812 ) program information for a program on the channel, e.g., in the manifest.
  • the media client determines ( 804 ) whether a program entitlement block is provided for the new program.
  • the media client uses ( 806 ) the entitlements specified in the program entitlement block to enforce entitlements for the program. If a program entitlement block is not provided, the media client uses ( 808 ) the channel entitlements to enforce entitlements for the program.
  • FIGS. 8B-8D depict flowcharts of additional aspects of the method that may be practiced in combination with the method of FIG. 8A .
  • Flowchart 800 B is directed to the use of a hash code with the program entitlement block. The flowchart can be entered when the answer to block 804 is “yes”.
  • the media client receives ( 810 ) a program entitlement block for a new program.
  • the media client determines ( 812 ) whether the new hash code matches the current hash code. If the hash codes do not match, the media client can proceed to either block 806 or block 820 , depending on the options used. If the hash codes match, so will the contents of the entitlement blocks. Therefore, the media client can use ( 814 ) the entitlements specified for the current program to enforce entitlements for the new program.
  • Flowchart 800 C is directed to the use of device class entitlements such that multiple entitlement objects can be received in the entitlement block and is entered from a “yes” on blocks 804 or block 812 or from a “no” on block 832 .
  • the media client determines ( 820 ) whether the program entitlement block comprises a plurality of entitlement objects. If multiple entitlement objects are not present, the method proceeds to block 806 . If multiple entitlement objects are present, the media client selects ( 822 ) a first entitlement object that has a device class that matches the user device and uses ( 824 ) the entitlements in the selected entitlement object to enforce entitlements for the program.
  • Flowchart 800 D is directed to the use of a subscriber override indicator.
  • the media client will receive ( 830 ) a subscriber override indicator from the network node, such as CC 122 .
  • the subscriber override indicator is provided at the time the user requests a channel.
  • the subscriber override indicator can be provided in a beaconing mechanism. Remaining blocks of this flowchart are entered from block 802 .
  • the media client determines ( 832 ) whether the user override is active, e.g., whether the value of the indicator is “True”. If the user override is not active, the method can proceed to any of block 804 , block 810 or block 820 , depending on the embodiment.
  • the media client sends ( 834 ) an override entitlement request to a content controller node and receives ( 836 ) override entitlements.
  • the media client uses ( 838 ) the override entitlements to enforce entitlements for the program.
  • FIG. 9 depicts a block diagram of an example network node 900 , e.g., CC 122 , according to an embodiment of the present patent application.
  • One or more processors 902 may be operatively coupled to various modules that may be implemented in persistent memory 904 for executing suitable program instructions 908 or code portions with respect to one or more processes set forth hereinabove for providing program and device class entitlements to client devices. Although only a single set of program instructions are shown, it will be understood that any number of processes can be instantiated in node 900 .
  • Appropriate interfaces (I/F) 920 - 1 to 920 -M are operative to effectuate request/response messages to and from client devices, which can include managed devices, such as STBs, as well as unmanaged devices, such as mobile phones, tablets and laptops.
  • client devices can include managed devices, such as STBs, as well as unmanaged devices, such as mobile phones, tablets and laptops.
  • client devices can include managed devices, such as STBs, as well as unmanaged devices, such as mobile phones, tablets and laptops.
  • appropriate interfaces 1418 - 1 to 1418 -K to various network elements and/or nodes may be provided in an example network node implementation.
  • FIG. 10 depicts an overview of an STB 1000 , which is an example of a managed client device.
  • STB 1000 can include appropriate hardware/software components and subsystems configured for performing any of the device-side processes (either individually or in any combination thereof) with respect to receiving and enforcing program entitlements and device class entitlements as described herein.
  • One or more microcontrollers/processors 1002 are provided for the overall control of the STB 1000 and for the execution of various stored program instructions embodied in a media client 1013 that may be part of a memory subsystem 1011 .
  • a media client may be provided as a plug-in or an application within a browser, e.g., an HTML5 application executed within a browser.
  • Controller/processor complex referred to by reference numeral 1002 may also be representative of other specialty processing modules such as graphic processors, video processors, digital signal processors (DSPs), and the like, operating in association with suitable video and audio interfaces (not specifically shown).
  • appropriate interfaces such as cable TV I/F modules 1004 and/or satellite TV I/F modules 1006 involving tuners, demodulators, descramblers, MPEG/H.264/H.265 decoders/demuxes may be included for processing and interfacing with TV and other content signals received via an HFC cable network 1098 or a satellite network 1096 .
  • example demodulators may include QAM demodulator 1014 and NTSC/ATSC demodulator 1017 .
  • I/O or interfaces such as a display interface 1015 , Electronic Program Guide (EPG) 1016 , user interface 1020 , USB/HDMI ports 1018 , Ethernet I/F 1008 , and short-range and wide area wireless connectivity interfaces 1012 are also provided.
  • a hard disk drive (HDD) or DVR system 1010 is provided for mass storage of all sorts of program assets such as NV media, TV shows, movie titles, multimedia games, etc.
  • a suitable power supply block 1022 which may include AC/DC power conversion to provide power for the device 1000 .
  • the actual power architecture for the subscriber device 1000 may vary by the hardware platform used, e.g., depending upon the core SoC (System on Chip), memory, analog front-end, analog signal chain components and interfaces used in the specific platform, and the like.
  • SoC System on Chip
  • STB Logic 624 may also be provided that allows for receipt and processing of these specific entitlements.
  • FIG. 11 depicts a block diagram of an example mobile device or wireless UE device 1100 including a media client 1113 configured to execute certain aspects under control of processor(s) 1102 according to one or more embodiments of the present patent application.
  • Appropriate transceiver (Tx/Rx) circuitry 1104 coupled to one or more antenna units 1114 is operative to effectuate radio communications for purposes of the present disclosure including, e.g., streaming of media and manifests and communication with a network node for channel and override entitlements, etc. in addition to other standard cellular telephony/data communications.
  • the ABR client/player 1106 is operative to play out segments stored in an ABR buffer 1112 and a local cache 1110 is operative to store content.
  • the ABR client/player 1106 is provided with a plurality of ABR client controls 1116 that may be selectively operated by users for controlling user experience.
  • ABR client controls may comprise audio controls as well as video controls available with respect to a streaming session and may include Play 1116 -A, Skip 1116 -B, Fast Forward 1116 -C, Trick Mode or Trick Play 1116 -D, Rewind 1116 -E, and Next Channel or Channel Change 1116 -E.
  • a persistent memory module 1118 may be provided for storing appropriate program code or software instructions that may be executed by processors 1102 for effectuating outage message processing, display of notifications, ABR client control modulation, etc. in conjunction with other modules of the mobile device 1100 .
  • Such computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, so that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).
  • the computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks.
  • tangible, non-transitory computer-readable medium may include an electronic, magnetic, optical, electromagnetic, or semiconductor data storage system, apparatus, or device. More specific examples of the computer-readable medium would include the following: a portable computer diskette, a random access memory (RAM) circuit, a read-only memory (ROM) circuit, an erasable programmable read-only memory (EPROM or Flash memory) circuit, a portable compact disc read-only memory (CD-ROM), and a portable digital video disc read-only memory (DVD/Blu-ray).
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • DVD/Blu-ray portable digital video disc read-only memory
  • the computer program instructions may also be loaded onto or otherwise downloaded to a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus to produce a computer-implemented process.
  • embodiments of the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor or controller, which may collectively be referred to as “circuitry,” “a module” or variants thereof.
  • an example processing unit may include, by way of illustration, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • an example processor unit may employ distributed processing in certain embodiments.
  • the functions/acts described in the blocks may occur out of the order shown in the flowcharts.
  • two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
  • the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated.
  • some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction relative to the depicted arrows.
  • other blocks may be added or inserted between the blocks that are illustrated.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Graphics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
US14/829,142 2015-04-27 2015-08-18 Program and device class entitlements in a media platform Abandoned US20160316247A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/829,142 US20160316247A1 (en) 2015-04-27 2015-08-18 Program and device class entitlements in a media platform
TW105112984A TWI633781B (zh) 2015-04-27 2016-04-26 媒體平台中之節目及器件類別授權

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562153036P 2015-04-27 2015-04-27
US14/829,142 US20160316247A1 (en) 2015-04-27 2015-08-18 Program and device class entitlements in a media platform

Publications (1)

Publication Number Publication Date
US20160316247A1 true US20160316247A1 (en) 2016-10-27

Family

ID=55953327

Family Applications (2)

Application Number Title Priority Date Filing Date
US14/829,142 Abandoned US20160316247A1 (en) 2015-04-27 2015-08-18 Program and device class entitlements in a media platform
US14/829,196 Active US10455265B2 (en) 2015-04-27 2015-08-18 Program and device class entitlements in a media platform

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/829,196 Active US10455265B2 (en) 2015-04-27 2015-08-18 Program and device class entitlements in a media platform

Country Status (6)

Country Link
US (2) US20160316247A1 (de)
EP (2) EP3289768B1 (de)
CN (1) CN107810613B (de)
AR (1) AR104397A1 (de)
TW (1) TWI633781B (de)
WO (2) WO2016174560A1 (de)

Cited By (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109348269A (zh) * 2018-12-02 2019-02-15 甘肃万维信息技术有限责任公司 一种跨网投屏系统及其使用方法
US20190132627A1 (en) * 2016-12-31 2019-05-02 Turner Broadcasting Systems, Inc. Publishing disparate live media output streams in mixed mode
CN110213669A (zh) * 2019-05-18 2019-09-06 杭州当虹科技股份有限公司 一种基于ts切片的视频内容防盗系统和方法
US20200204834A1 (en) 2018-12-22 2020-06-25 Turner Broadcasting Systems, Inc. Publishing a Disparate Live Media Output Stream Manifest That Includes One or More Media Segments Corresponding to Key Events
US10750224B2 (en) 2016-12-31 2020-08-18 Turner Broadcasting System, Inc. Dynamic scheduling and channel creation based on user selection
US10827220B2 (en) 2017-05-25 2020-11-03 Turner Broadcasting System, Inc. Client-side playback of personalized media content generated dynamically for event opportunities in programming media content
US10856016B2 (en) 2016-12-31 2020-12-01 Turner Broadcasting System, Inc. Publishing disparate live media output streams in mixed mode based on user selection
US10880606B2 (en) 2018-12-21 2020-12-29 Turner Broadcasting System, Inc. Disparate live media output stream playout and broadcast distribution
US20210035143A1 (en) * 2019-07-30 2021-02-04 Fanuc Corporation Application sales management server system, application sales management system, management controller, and distribution controller
US10965967B2 (en) 2016-12-31 2021-03-30 Turner Broadcasting System, Inc. Publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content
US10992973B2 (en) * 2016-12-31 2021-04-27 Turner Broadcasting System, Inc. Publishing a plurality of disparate live media output stream manifests using live input streams and pre-encoded media assets
US11005823B2 (en) * 2016-01-08 2021-05-11 Capital One Services, Llc Field level security system for securing sensitive data
US11038932B2 (en) 2016-12-31 2021-06-15 Turner Broadcasting System, Inc. System for establishing a shared media session for one or more client devices
US11051061B2 (en) 2016-12-31 2021-06-29 Turner Broadcasting System, Inc. Publishing a disparate live media output stream using pre-encoded media assets
US11051074B2 (en) 2016-12-31 2021-06-29 Turner Broadcasting System, Inc. Publishing disparate live media output streams using live input streams
US11082734B2 (en) 2018-12-21 2021-08-03 Turner Broadcasting System, Inc. Publishing a disparate live media output stream that complies with distribution format regulations
US11134309B2 (en) 2016-12-31 2021-09-28 Turner Broadcasting System, Inc. Creation of channels using pre-encoded media assets
US20220038755A1 (en) * 2020-07-31 2022-02-03 Charter Communications Operating, Llc Video client management of video service feature flags
US20220150241A1 (en) * 2020-11-11 2022-05-12 Hewlett Packard Enterprise Development Lp Permissions for backup-related operations
US11438658B2 (en) 2016-12-31 2022-09-06 Turner Broadcasting System, Inc. Client-side dynamic presentation of programming content in an indexed disparate live media output stream
US11451846B2 (en) * 2017-05-05 2022-09-20 Nagravision S.A. Pre-entitlement enforcement
US11463780B1 (en) * 2016-12-02 2022-10-04 Didja, Inc. Locally relayed broadcast and community service television
US11470373B2 (en) 2016-12-31 2022-10-11 Turner Broadcasting System, Inc. Server-side dynamic insertion of programming content in an indexed disparate live media output stream
US11477254B2 (en) 2016-12-31 2022-10-18 Turner Broadcasting System, Inc. Dynamic playout buffer for disparate live media output stream
US11503352B2 (en) 2016-12-31 2022-11-15 Turner Broadcasting System, Inc. Dynamic scheduling and channel creation based on external data
US11546400B2 (en) 2016-12-31 2023-01-03 Turner Broadcasting System, Inc. Generating a live media segment asset
US20230015697A1 (en) * 2021-07-13 2023-01-19 Citrix Systems, Inc. Application programming interface (api) authorization
WO2023205620A1 (en) * 2022-04-19 2023-10-26 Tencent America LLC Methods, devices, and computer readable medium for processing alternative media presentation description
US11962821B2 (en) 2016-12-31 2024-04-16 Turner Broadcasting System, Inc. Publishing a disparate live media output stream using pre-encoded media assets
US11968291B2 (en) * 2018-09-11 2024-04-23 International Business Machines Corporation Access to data broadcast in encrypted form based on blockchain
US12022142B2 (en) 2016-12-31 2024-06-25 Turner Broadcasting System, Inc. Publishing a plurality of disparate live media output stream manifests using live input streams and pre-encoded media assets
US12028575B2 (en) 2021-07-02 2024-07-02 Turner Broadcasting System, Inc. Rules-based delivery and presentation of non-programming media items at client device

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9917690B2 (en) * 2015-10-01 2018-03-13 Time Warner Cable Enterprises Llc Encryption management, content recording management, and playback management in a network environment
US10432993B2 (en) * 2016-12-20 2019-10-01 Arris Enterprises Llc Output and playback control delivery for adaptive bitrate streaming
AU2020100285B4 (en) * 2019-03-18 2020-09-10 Apple Inc. User interfaces for subscription applications
US10904375B2 (en) 2019-03-18 2021-01-26 Apple Inc. User interfaces for subscription applications
CN112135165B (zh) * 2020-08-06 2022-07-12 河北广电无线传媒有限公司 一种iptv模板文件防篡改方法及系统
WO2022031395A1 (en) * 2020-08-07 2022-02-10 Arris Enterprises Llc System and method for the common control of heterogeneous media service restrictions
US11425460B1 (en) 2021-01-29 2022-08-23 Rovi Guides, Inc. Selective streaming based on dynamic parental rating of content
EP4344206A1 (de) * 2022-09-22 2024-03-27 MK Systems USA Inc. Systeme und verfahren für streaming mit reduzierter latenz

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020018684A1 (en) * 2000-06-05 2002-02-14 Chisei Hosaka Method and recording apparatus for detecting rear edge of a recording medium
US7233948B1 (en) * 1998-03-16 2007-06-19 Intertrust Technologies Corp. Methods and apparatus for persistent control and protection of content
US20130015954A1 (en) * 2011-07-12 2013-01-17 Sony Corporation Electronic book reader
US20130021265A1 (en) * 2011-07-21 2013-01-24 Imerj LLC Second view
US20130031204A1 (en) * 2011-07-28 2013-01-31 Graham Christoph J Systems and methods of accelerating delivery of remote content
US20140019607A1 (en) * 2011-03-28 2014-01-16 Fredrick Beste Method, Apparatus and Computer Program Product For Updating Load Balancer Configuration Data

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1062812B1 (de) * 1998-03-16 2005-05-25 Intertrust Technologies Corp. Streaming-media-abspielgerät mit fortdauernde kontrolle und schutz von medieninhalt
US6735313B1 (en) * 1999-05-07 2004-05-11 Lucent Technologies Inc. Cryptographic method and apparatus for restricting access to transmitted programming content using hash functions and program identifiers
US7266704B2 (en) * 2000-12-18 2007-09-04 Digimarc Corporation User-friendly rights management systems and methods
US8930561B2 (en) 2003-09-15 2015-01-06 Sony Computer Entertainment America Llc Addition of supplemental multimedia content and interactive capability at the client
EP1564994A1 (de) * 2004-02-13 2005-08-17 Nagravision S.A. Verfahren zum Verwalten der Rechte eines Teilnehmers eines bezahlten Fernsehsystems mit mehreren Betreibern
CN100364332C (zh) * 2004-09-01 2008-01-23 华为技术有限公司 一种保护宽带视音频广播内容的方法
US8291504B2 (en) * 2008-12-31 2012-10-16 Akamai Technologies, Inc. Enforcing single stream per sign-on from a content delivery network (CDN) media server
CN101998164B (zh) * 2009-08-17 2013-08-07 北京视博数字电视科技有限公司 节目信息生成方法及其终端设备
US20110258656A1 (en) 2010-04-19 2011-10-20 Disney Enterprises, Inc. System and method for television application channel sync (TACS)
US8789196B2 (en) 2010-05-28 2014-07-22 Adobe Systems Incorporated System and method for providing content protection of linearly consumed content with a bidirectional protocol for license acquisition
US8782268B2 (en) 2010-07-20 2014-07-15 Microsoft Corporation Dynamic composition of media
US9794312B2 (en) 2010-09-01 2017-10-17 Electronics And Telecommunications Research Institute Method and device for providing streaming content
US8898303B2 (en) 2010-09-09 2014-11-25 Albert J. McGowan Enterprise grade rights management
EP2626808B1 (de) 2010-10-07 2018-09-05 Samsung Electronics Co., Ltd Drm-dienstbereitstellungsverfahren und -vorrichtung
SI2640842T1 (sl) * 2010-11-17 2018-09-28 Aduro Biotech, Inc. Postopki in sestavki za induciranje imunskega odziva na EGFRvIII
ES2755780T3 (es) 2011-09-16 2020-04-23 Veracode Inc Análisis estático y de comportamiento automatizado mediante la utilización de un espacio aislado instrumentado y clasificación de aprendizaje automático para seguridad móvil
US10257194B2 (en) 2012-02-14 2019-04-09 Airwatch Llc Distribution of variably secure resources in a networked environment
US20130312046A1 (en) 2012-05-15 2013-11-21 Mark Robertson Smart stream delivery server, system and methods for assembling a mix of services to be delivered to a subscriber's premises
WO2014059047A2 (en) 2012-10-10 2014-04-17 Red.Com, Inc. Video distribution and playback
EP2929695A1 (de) 2012-12-10 2015-10-14 Koninklijke KPN N.V. Digitale rechteverwaltung für segmentierten inhalt
US9179159B2 (en) * 2013-06-20 2015-11-03 Wowza Media Systems, LLC Distributed encoding of a video stream
MX354712B (es) * 2013-07-23 2018-03-16 Ericsson Ab Sistema de distribucion de medios con ejecucion de autorizacion con base en una declaracion.
US9160540B2 (en) 2013-07-25 2015-10-13 Adobe Systems Incorporated Preventing playback of streaming video if ads are removed
US20150271541A1 (en) * 2014-03-19 2015-09-24 Time Warner Cable Enterprises Llc Apparatus and methods for recording a media stream
US9613190B2 (en) * 2014-04-23 2017-04-04 Intralinks, Inc. Systems and methods of secure data exchange
US10162944B2 (en) 2015-03-30 2018-12-25 Arris Enterprises Llc Library style media DRM APIs in a hosted architecture

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7233948B1 (en) * 1998-03-16 2007-06-19 Intertrust Technologies Corp. Methods and apparatus for persistent control and protection of content
US20020018684A1 (en) * 2000-06-05 2002-02-14 Chisei Hosaka Method and recording apparatus for detecting rear edge of a recording medium
US20140019607A1 (en) * 2011-03-28 2014-01-16 Fredrick Beste Method, Apparatus and Computer Program Product For Updating Load Balancer Configuration Data
US20130015954A1 (en) * 2011-07-12 2013-01-17 Sony Corporation Electronic book reader
US20130021265A1 (en) * 2011-07-21 2013-01-24 Imerj LLC Second view
US20130031204A1 (en) * 2011-07-28 2013-01-31 Graham Christoph J Systems and methods of accelerating delivery of remote content

Cited By (66)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11005823B2 (en) * 2016-01-08 2021-05-11 Capital One Services, Llc Field level security system for securing sensitive data
US12015830B1 (en) * 2016-12-02 2024-06-18 Didja, Inc. Locally relayed broadcast and community service television
US11463780B1 (en) * 2016-12-02 2022-10-04 Didja, Inc. Locally relayed broadcast and community service television
US11622143B2 (en) * 2016-12-31 2023-04-04 Turner Broadcasting System, Inc. Publishing disparate live media output streams in mixed mode
US11611804B2 (en) 2016-12-31 2023-03-21 Turner Broadcasting System, Inc. Publishing disparate live media output streams using live input streams
US12022142B2 (en) 2016-12-31 2024-06-25 Turner Broadcasting System, Inc. Publishing a plurality of disparate live media output stream manifests using live input streams and pre-encoded media assets
US10856016B2 (en) 2016-12-31 2020-12-01 Turner Broadcasting System, Inc. Publishing disparate live media output streams in mixed mode based on user selection
US11438658B2 (en) 2016-12-31 2022-09-06 Turner Broadcasting System, Inc. Client-side dynamic presentation of programming content in an indexed disparate live media output stream
US11974017B2 (en) 2016-12-31 2024-04-30 Turner Broadcasting System, Inc. Publishing disparate live media output streams using live input streams
US11962821B2 (en) 2016-12-31 2024-04-16 Turner Broadcasting System, Inc. Publishing a disparate live media output stream using pre-encoded media assets
US11917217B2 (en) 2016-12-31 2024-02-27 Turner Broadcasting System, Inc. Publishing disparate live media output streams in mixed mode based on user selection publishing disparate live media output streams in mixed mode based on user selection
US11671641B2 (en) 2016-12-31 2023-06-06 Turner Broadcasting System, Inc. Publishing disparate live media output streams in mixed mode
US10965967B2 (en) 2016-12-31 2021-03-30 Turner Broadcasting System, Inc. Publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content
US10992973B2 (en) * 2016-12-31 2021-04-27 Turner Broadcasting System, Inc. Publishing a plurality of disparate live media output stream manifests using live input streams and pre-encoded media assets
US11665398B2 (en) 2016-12-31 2023-05-30 Turner Broadcasting System, Inc. Creation of channels using pre-encoded media assets
US11038932B2 (en) 2016-12-31 2021-06-15 Turner Broadcasting System, Inc. System for establishing a shared media session for one or more client devices
US11375248B2 (en) 2016-12-31 2022-06-28 Turner Broadcasting System, Inc. Publishing disparate live media output streams in mixed mode based on user selection
US11051074B2 (en) 2016-12-31 2021-06-29 Turner Broadcasting System, Inc. Publishing disparate live media output streams using live input streams
US11546400B2 (en) 2016-12-31 2023-01-03 Turner Broadcasting System, Inc. Generating a live media segment asset
US11503352B2 (en) 2016-12-31 2022-11-15 Turner Broadcasting System, Inc. Dynamic scheduling and channel creation based on external data
US10750224B2 (en) 2016-12-31 2020-08-18 Turner Broadcasting System, Inc. Dynamic scheduling and channel creation based on user selection
US11109086B2 (en) * 2016-12-31 2021-08-31 Turner Broadcasting System, Inc. Publishing disparate live media output streams in mixed mode
US11134309B2 (en) 2016-12-31 2021-09-28 Turner Broadcasting System, Inc. Creation of channels using pre-encoded media assets
US11503349B2 (en) 2016-12-31 2022-11-15 Turner Broadcasting System, Inc. Publishing a plurality of disparate live media output stream manifests using live input streams and pre-encoded media assets
US11483596B2 (en) 2016-12-31 2022-10-25 Turner Broadcasting System, Inc. Publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content
US11477254B2 (en) 2016-12-31 2022-10-18 Turner Broadcasting System, Inc. Dynamic playout buffer for disparate live media output stream
US11470373B2 (en) 2016-12-31 2022-10-11 Turner Broadcasting System, Inc. Server-side dynamic insertion of programming content in an indexed disparate live media output stream
US11051061B2 (en) 2016-12-31 2021-06-29 Turner Broadcasting System, Inc. Publishing a disparate live media output stream using pre-encoded media assets
US20190132627A1 (en) * 2016-12-31 2019-05-02 Turner Broadcasting Systems, Inc. Publishing disparate live media output streams in mixed mode
US11451846B2 (en) * 2017-05-05 2022-09-20 Nagravision S.A. Pre-entitlement enforcement
US11095942B2 (en) 2017-05-25 2021-08-17 Turner Broadcasting System, Inc. Rules-based delivery and presentation of non-programming media items at client device
US11432044B2 (en) 2017-05-25 2022-08-30 Turner Broadcasting System, Inc. Client-side overlay of graphic items on media content
US11375278B2 (en) 2017-05-25 2022-06-28 Turner Broadcasting System, Inc. Concurrent presentation of non-programming media assets with programming media content at client device
US11617011B2 (en) 2017-05-25 2023-03-28 Turner Broadcasting System, Inc. Delivery of different services through different client devices
US10827220B2 (en) 2017-05-25 2020-11-03 Turner Broadcasting System, Inc. Client-side playback of personalized media content generated dynamically for event opportunities in programming media content
US11297386B2 (en) 2017-05-25 2022-04-05 Turner Broadcasting System, Inc. Delivery of different services through different client devices
US20220060787A1 (en) 2017-05-25 2022-02-24 Turner Broadcasting System, Inc. Delivery of different services through different client devices
US11245964B2 (en) 2017-05-25 2022-02-08 Turner Broadcasting System, Inc. Management and delivery of over-the-top services over different content-streaming systems
US10939169B2 (en) 2017-05-25 2021-03-02 Turner Broadcasting System, Inc. Concurrent presentation of non-programming media assets with programming media content at client device
US11778272B2 (en) 2017-05-25 2023-10-03 Turner Broadcasting System, Inc. Delivery of different services through different client devices
US11825162B2 (en) 2017-05-25 2023-11-21 Turner Broadcasting System, Inc. Management and delivery of over-the-top services over different content-streaming systems
US11825161B2 (en) 2017-05-25 2023-11-21 Turner Broadcasting System, Inc. Management and delivery of over-the-top services over different content-streaming systems
US11228809B2 (en) 2017-05-25 2022-01-18 Turner Broadcasting System, Inc. Delivery of different services through different client devices
US11659246B2 (en) 2017-05-25 2023-05-23 Turner Broadcasting System, Inc. Client-side playback of personalized media content generated dynamically for event opportunities in programming media content
US11051073B2 (en) 2017-05-25 2021-06-29 Turner Broadcasting System, Inc. Client-side overlay of graphic items on media content
US11638064B2 (en) 2017-05-25 2023-04-25 Turner Broadcasting System, Inc. Dynamic verification of playback of media assets at client device
US10924804B2 (en) 2017-05-25 2021-02-16 Turner Broadcasting System, Inc. Dynamic verification of playback of media assets at client device
US11736534B2 (en) 2018-07-17 2023-08-22 Turner Broadcasting System, Inc. System for establishing a shared media session for one or more client devices
US11968291B2 (en) * 2018-09-11 2024-04-23 International Business Machines Corporation Access to data broadcast in encrypted form based on blockchain
CN109348269A (zh) * 2018-12-02 2019-02-15 甘肃万维信息技术有限责任公司 一种跨网投屏系统及其使用方法
US11553227B2 (en) 2018-12-21 2023-01-10 Turner Broadcasting System, Inc. Publishing a disparate live media output stream that complies with distribution format regulations
US11082734B2 (en) 2018-12-21 2021-08-03 Turner Broadcasting System, Inc. Publishing a disparate live media output stream that complies with distribution format regulations
US11483607B2 (en) 2018-12-21 2022-10-25 Turner Broadcasting System, Inc. Publishing a disparate live media output stream that complies with distribution format regulations
US10880606B2 (en) 2018-12-21 2020-12-29 Turner Broadcasting System, Inc. Disparate live media output stream playout and broadcast distribution
US11438659B2 (en) 2018-12-21 2022-09-06 Turner Broadcasting System, Inc. Disparate live media output stream playout and broadcast distribution
US11477499B2 (en) 2018-12-22 2022-10-18 Turner Broadcasting System, Inc. Publishing a disparate live media output stream manifest that includes one or more media segments corresponding to key events
US20200204834A1 (en) 2018-12-22 2020-06-25 Turner Broadcasting Systems, Inc. Publishing a Disparate Live Media Output Stream Manifest That Includes One or More Media Segments Corresponding to Key Events
US11477500B2 (en) 2018-12-22 2022-10-18 Turner Broadcasting System, Inc. Publishing a disparate live media output stream manifest that includes one or more media segments corresponding to key events
US10873774B2 (en) 2018-12-22 2020-12-22 Turner Broadcasting System, Inc. Publishing a disparate live media output stream manifest that includes one or more media segments corresponding to key events
CN110213669A (zh) * 2019-05-18 2019-09-06 杭州当虹科技股份有限公司 一种基于ts切片的视频内容防盗系统和方法
US20210035143A1 (en) * 2019-07-30 2021-02-04 Fanuc Corporation Application sales management server system, application sales management system, management controller, and distribution controller
US20220038755A1 (en) * 2020-07-31 2022-02-03 Charter Communications Operating, Llc Video client management of video service feature flags
US20220150241A1 (en) * 2020-11-11 2022-05-12 Hewlett Packard Enterprise Development Lp Permissions for backup-related operations
US12028575B2 (en) 2021-07-02 2024-07-02 Turner Broadcasting System, Inc. Rules-based delivery and presentation of non-programming media items at client device
US20230015697A1 (en) * 2021-07-13 2023-01-19 Citrix Systems, Inc. Application programming interface (api) authorization
WO2023205620A1 (en) * 2022-04-19 2023-10-26 Tencent America LLC Methods, devices, and computer readable medium for processing alternative media presentation description

Also Published As

Publication number Publication date
TWI633781B (zh) 2018-08-21
CN107810613A (zh) 2018-03-16
CN107810613B (zh) 2020-06-02
EP3289767A1 (de) 2018-03-07
US20160316244A1 (en) 2016-10-27
TW201707459A (zh) 2017-02-16
EP3289768B1 (de) 2019-02-27
EP3289767B1 (de) 2019-06-12
US10455265B2 (en) 2019-10-22
AR104397A1 (es) 2017-07-19
EP3289768A1 (de) 2018-03-07
WO2016174560A1 (en) 2016-11-03
WO2016174559A1 (en) 2016-11-03

Similar Documents

Publication Publication Date Title
US10455265B2 (en) Program and device class entitlements in a media platform
US11973992B2 (en) Apparatus and methods for selective secondary content insertion in a digital network
US10148992B2 (en) Apparatus and methods for recording, accessing, and delivering packetized content
US11659257B2 (en) System and method for watermarking of media segments using sample variants for normalized encryption (SVNE)
KR101685515B1 (ko) 다운로딩 및 스트리밍을 위한 저장 및 전송 콘텐츠
US9167287B2 (en) Controlling a viewing session for a video program
US8719921B2 (en) User and device authentication for media services
US9288278B2 (en) Providing user content with streamed media chunks
US20110197237A1 (en) Controlled Delivery of Content Data Streams to Remote Users
US11997365B2 (en) System and method of content streaming and downloading
US9118943B2 (en) Video on demand processing
US9223944B2 (en) Media rights management on multiple devices
WO2013081944A1 (en) Methods and apparatuses for domain management
US8970668B2 (en) High bandwidth streaming to media player
US8468558B2 (en) Method and apparatus for bandwidth consumption usage reporting of non-managed sources
US10334314B1 (en) Preload-supported concurrent video stream limiting
US8930446B2 (en) Altering transcoding priority
US10440097B1 (en) Profile based streaming

Legal Events

Date Code Title Description
AS Assignment

Owner name: ERICSSON AB, SWEDEN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ARRITT, ROBERT;BIAGINI, DANIEL;MA, KEVIN;AND OTHERS;SIGNING DATES FROM 20150814 TO 20150817;REEL/FRAME:043804/0250

STPP Information on status: patent application and granting procedure in general

Free format text: ADVISORY ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION