Patent Grant
10587906
The present invention relates generally to the field of content and/or data delivery over one or more networks. More particularly, the present invention is related in one exemplary aspect to apparatus and methods for content delivery and message exchange across these networks.
Recent advances in digital information processing and technology have made a whole range of services and functions available for delivery to consumers at various types devices for very reasonable prices or subscription fees. These services and functions include digital content or programming (movies, etc.), digital video-on-demand (VOD), personal video recorder (PVR) and networked PVR (nPVR), Internet Protocol television (IPTV), digital media playback and recording, as well high speed Internet access (including so-called “Internet TV”, where television programming is delivered over the Internet without QoS) and IP-based telephony (e.g., VoIP). Other services available to network users include access to, and recording of, digital music (e.g., MP3 files).
Currently, many of these services are provided to the user via a wide variety of different equipment environments and delivery paradigms including, inter alia, cable or satellite modems or QAMs, HFCu (i.e., Hybrid Fiber-copper distribution via indigenous POST/PSTN and/or coaxial wiring in a premises), optical fiber such as FTTC, FTTH, etc., Wi-Fi™ hubs, Ethernet hubs, gateways, switches, and routers, to a plurality of user equipment types. For example, content may be delivered to users at set-top boxes, personal (desktop) computers, laptop computers, other mini-computers (such as so-called “netbooks”, mini-notebook computers), and/or other devices. Recent advances in consumer electronics have also led to the widespread introduction of a variety of portable media devices (PMDs) such as, inter alia, portable digital music devices such as the well known Apple iPod™ and other so-called “MP3 players”, cellular telephones/smartphones, handheld computers, and personal digital assistants (PDA), which allow users to store and playback audio and video files. Furthermore, many users today wish to view at least some content via the Internet.
Although a myriad of services, equipment, data formats and providers are available, current systems offer no mechanism for a managed network operator (e.g., MSO) to partner with programmers (content producers) in order to allow users who are verified as subscribers of the MSO network to utilize and purchase content from the network (such as via a subscription, pay-per-view, etc.), and to be able to view this content via the Internet or another such external or internetwork via partnered programmer websites.
Hence, methods and apparatus are needed which enable a partnered programmer to, either on its own or through communication with the network operator, determine if an identified potential viewer of Internet content already subscribes to this content through the MSO, and if so provide the content (e.g., according to one or more delivery models associated with the user's subscription). Such methods and apparatus would advantageously enable a user to receive content on any device and via any delivery paradigm, thereby enhancing the user experience by no longer anchoring the user to a fixed location. Ideally, the aforementioned methods and apparatus might also allow users to access real-time and scheduled content from multiple viewing mediums without being restricted to fixed schedules, and further enable users to achieve geographical independence via use of mobile technology which provides enhanced flexibility over traditional means of video distribution. Furthermore, the ideal solution would include enhanced access to premium-based content which not available to non-subscribers, or which cannot be delivered across traditional transport (i.e., behind the scenes outtakes, alternate endings, actor interviews, etc.).
The present invention addresses the foregoing needs by disclosing, inter alia, apparatus and methods for content management and message exchange between entities of two networks.
In a first aspect of the invention, a method for determining content permission(s) is disclosed. In one embodiment, the determination is made at a content distribution network entity, and the permission relates to access of protected content from a remote source via an internetwork (e.g., the Internet). In one variant, the method comprises: receiving at the network entity a communication relating to a request for the protected content from a user device, the communication being sent to the content distribution network entity from an entity associated with the remote source; determining whether the user device is associated to the subscriber of the content distribution network; if the user device is associated to the subscriber, determining whether the protected content is within an approved level of service of the subscriber; and if the protected content is within the approved level of service of the subscriber, transmitting a message to the entity associated with the remote source, the message causing the remote source to deliver the protected content to the user device.
In a second aspect of the invention, an apparatus for managing delivery of a plurality of protected content from a remote device is disclosed. In one embodiment, the remote device comprises a content server, and the apparatus comprises: at least one first interface for receiving a plurality of information from a user device, the information comprising: information identifying a user of the user device; and information identifying a particular one of the plurality of protected content requested by the user, a first computer program configured to utilize the information identifying the user to determine whether the user is among the plurality of entitled users; a second computer program configured to utilize the information identifying the user and the information identifying the particular one of the plurality of protected content to determine whether the particular one of the plurality of protected content is within an authorized service class for the user; and at least one second interface for transmitting at least one message to a remote content server. The at least one message causes the remote content sever to: (i) provide the protected content to the user device, or (ii) to deny the user device the protected content. The message may be based at least in part on the determination of whether the user is among the plurality of entitled users, and/or on the determination of whether the particular one of the plurality of protected content is within the authorized service class for the user.
In a third aspect of the invention, a method for determining whether a user is permitted in a first network to access protected content associated with a second network is disclosed. In one embodiment, the method comprises: receiving a request for the protected content from the user in the first network; determining the second network to which the user is associated; sending a message to the second network, the message comprising: login and password information entered by the user; and the request for the protected content; and receiving, in response to the message, a message indicating whether the user is permitted in the first network to access the protected content associated with the second network.
In a fourth aspect of the invention, a method of determining whether a particular one of a plurality of protected content may be provided to a user via a first network based at least in part on service details of the user in a second network is disclosed. In one embodiment, the method comprises: receiving a request for authorization of the user's access to the particular one of the plurality of protected content from an entity of the first network, the request for authorization comprising at least a globally unique identifier (GUID) associated with the user and information identifying the particular one of the plurality of protected content; determining in response to the request, whether a session has been established by the user and the second network; determining a subscriber identity within the second network based at least in part on the GUID; retrieving the service details associated with the user; comparing the service details to the information identifying the particular one of the plurality of protected content; and if the service details match the information identifying the particular one of the plurality of protected content, providing a message enabling the particular one of the plurality of protected content to be delivered to the user via the first network.
In a fifth aspect of the invention, a method for enabling the distribution of protected content associated with a managed content distribution network to subscribers of the network is disclosed. In one embodiment, the method comprises receiving a communication relating to a request for the protected content from a subscriber, the communication being sent from an entity associated with a third party content source that has access to the protected content; determining whether the protected content is authorized for delivery to the subscriber; and if the protected content is authorized, causing the third party content source to deliver the protected content to the subscriber (e.g., via the Internet).
In a sixth aspect of the invention, a computer readable apparatus is disclosed. In one embodiment, the apparatus comprises a storage medium, the medium comprising at least one computer program adapted for use in managing remote requests for protected content of a managed content distribution network. The program comprises first logic configured to process a received content request from a third party entity, the request being generated at least in part using network subscriber login information; second logic configured to utilize at least portions of the login information to access a subscriber database maintained by the network; third logic configured to determine, based on the access and the at least portions of the login information, whether the subscriber is entitled to access the protected content; and fourth logic configured to cause issuance of a message to the third party entity authorizing or denying provision of the requested content to the subscriber by the third party entity.
In a seventh aspect of the invention, a client device having a processor configured to run at least one client application thereon is disclosed. In one embodiment, the client application follows appropriate protocol for sending requests for content and receiving requested content as well as for providing additional information to the network to facilitate authentication and authorization. In another embodiment, the client application is configured to collect information regarding the user's actions with respect to content, and pass this information upstream. In one variant this information is used to make business decisions including e.g., secondary content insertion decisions.
In an eighth aspect of the invention, a business and operation “rules” engine is disclosed. In one embodiment, the engine comprises one or more computer programs adapted to control various aspects of content and message exchange between two entities so as to achieve desired business or operation goals (or obey certain rules).
In a ninth aspect of the invention, methods of doing business relating to content provision and permissions are disclosed.
These and other aspects of the invention shall become apparent when considered in light of the disclosure provided herein.
All Figures and Appendices Copyright 2010 Time Warner Cable, Inc. All rights reserved.
Reference is now made to the drawings wherein like numerals refer to like parts throughout.
As used herein, the term “application” refers generally to a unit of executable software that implements a certain functionality or theme. The themes of applications vary broadly across any number of disciplines and functions (such as on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculator etc.), and one application may have more than one theme. The unit of executable software generally runs in a predetermined environment; for example, the unit could comprise a downloadable Java Xlet™ that runs within the JavaTV™ environment.
As used herein, the terms “client device” and “end user device” include, but are not limited to, set-top boxes (e.g., DSTBs), personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), and smartphones.
As used herein, the term “codec” refers to a video, audio, or other data coding and/or decoding algorithm, process or apparatus including, without limitation, those of the MPEG (e.g., MPEG-1, MPEG-2, MPEG-4/H.264, etc.), Real (RealVideo, etc.), AC-3 (audio), DiVX, XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, 9, 10, or 11), ATI Video codec, or VC-1 (SMPTE standard 421M) families.
As used herein, the term “computer program” or “software” is meant to include any sequence or human or machine cognizable steps which perform a function. Such program may be rendered in virtually any programming language or environment including, for example, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML, VoXML), and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA), Java™ (including J2ME, Java Beans, etc.) and the like.
The terms “Customer Premises Equipment (CPE)” and “host device” refer to any type of electronic equipment located within a customer's or user's premises and connected to a network. The term “host device” refers generally to a terminal device that has access to digital television content via a satellite, cable, or terrestrial network.
As used herein, the term “display” means any type of device adapted to display information, including without limitation CRTs, LCDs, TFTs, plasma displays, LEDs, incandescent and fluorescent devices, or combinations/integrations thereof. Display devices may also include less dynamic devices such as, for example, printers, e-ink devices, and the like.
As used herein, the term “DOCSIS” refers to any of the existing or planned variants of the Data Over Cable Services Interface Specification, including for example DOCSIS versions 1.0, 1.1, 2.0 and 3.0. DOCSIS (version 1.0) is a standard and protocol for internet access using a “digital” cable network.
As used herein, the term “headend” refers generally to a networked system controlled by an operator (e.g., an MSO) that distributes programming to MSO clientele using client devices. Such programming may include literally any information source/receiver including, inter alia, free-to-air TV channels, pay TV channels, interactive TV, and the Internet.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet.
As used herein, the terms “microprocessor” and “digital processor” are meant generally to include all types of digital processing devices including, without limitation, digital signal processors (DSPs), reduced instruction set computers (RISC), general-purpose (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable compute fabrics (RCFs), array processors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single unitary IC die, or distributed across multiple components. As used herein, the terms “MSO” or “multiple systems operator” refer to a cable, satellite, or terrestrial network provider having infrastructure required to deliver services including programming and data over those mediums.
As used herein, the terms “network” and “bearer network” refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications or networking protocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP, 3GPP2, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).
As used herein, the term “network interface” refers to any signal or data interface with a component or network including, without limitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g., USB2), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radio frequency tuner (e.g., in-band or OOB, cable modem, etc.), Wi-Fi (802.11a,b,g,n), WIMAX (802.16), PAN (e.g., 802.15), or IrDA families.
As used herein, the term “QAM” refers to modulation schemes used for sending signals over cable networks. Such modulation scheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM, 256-QAM, etc.) depending on details of a cable network. A QAM may also refer to a physical channel modulated according to the schemes.
As used herein, the term “server” refers to any computerized component, system or entity regardless of form which is adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer network.
As used herein, the term “storage device” refers to without limitation computer hard drives, DVR device, memory, RAID devices or arrays, optical media (e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices or media capable of storing content or other information.
As used herein, the term “Wi-Fi” refers to, without limitation, any of the variants of IEEE-Std. 802.11 or related standards including 802.11 a/b/g/n/v.
As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth, 3G, HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, narrowband/FDMA, OFDM, PCS/DCS, analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
Overview
The present invention discloses, inter ala, methods and apparatus for providing protected oontent to subscribers of a managed network (e.g., MSO network such as cable, satellite, or HFCu) via a content source accessible to the subscriber via an internetwork (e.g., the Internet). In one embodiment, a user accesses a programmer (content source) website, or an MSO website, and requests content. If the particular content requested is protected content, or content which is only accessible to certain types of subscribers, the programmer and/or MSO determines whether the requesting user is permitted to access the content and if so, what use restrictions if any apply. The process by which it is determined whether a user may access content includes: (i) authenticating the user as a subscriber to the MSO, and then (ii) determining whether the subscriber's service level (subscription level) permits or entitles viewing of the requested content.
In one embodiment, the user is authenticated by requiring him/her to establish a login identity and password, and/or assigning the user a globally unique identifier (GUID). This unique information is stored at an MSO entity such as an entitlements or authentication server, and when the user logs into a website (such as a common login application (CLA) maintained by the MSO), the information is accessed and compared to information the user provides to login. If valid login information is entered (i.e., the information provided matches the stored information for that user GUID), then a session is created between the MSO and user.
The aforementioned authentication at the MSO may be facilitated by various entities associated with the programmer. For instance, the user may first log in to a third party (e.g., programmer's) website, such as by establishing a login identity and password which are stored at the programmer's site. Once logged in, the programmer may forward requests to view content to an appropriate MSO, and provide a platform for the user to log in to the MSO site (e.g., a virtual MSO interface).
In one embodiment, the programmer and MSO accounts for a particular user may be linked or “federated”. According to this embodiment, a given user will have MSO-specific information regarding its identity (such as login information for the MSO, GUID, etc.) and/or information regarding its subscription level and other service details stored at the programmer site, or other entity accessible to the programmer without requiring consultation with the MSO. Messages received from the MSO representing permission for the user to access content may also be stored at the programmer site. The programmer may later reference this information when subsequent requests for content are made by the user, and thereby provide faster and more efficient service. Methods for unlinking or de-federating a user's account in the programmer and MSO sites are also given.
Determination of whether the subscriber's service level (e.g., subscription level) permits viewing of the requested content is, in one embodiment, performed at the MSO in response to receiving a request for content. In one embodiment, one or more MSO entities utilize the user login information to determine the identity of the user as a subscriber, and then determines the details of the service to which the subscriber has subscribed. The identity of the user may also be determined at least in part via a device ID associated with the request (e.g., MAC, IP address, etc.), which can be correlated to one or more subscriber accounts by the MSO.
The MSO generates and transmits messages to the third party programmer (content source) indicating whether or not the user should be permitted access to the content. (and optionally what restrictions if any apply) based on the authentication and authorization determinations. In one variant, the programmer may store a so-called “entitlement cookie” which may be referred to at future instances wherein the subscriber requests content. The entitlement cookie may comprise a stored MSO message indicating the subscriber is entitled to access the content, which may be relied upon for, e.g., a certain period of time or number of transactions.
Delivery of the requested content may occur via a number of different models, including for example (i) delivery back over the MSO's infrastructure, and (ii) delivery over non-MSO operated infrastructure, such as the Internet, wireless link, etc.
Business rules for the implementation of the aforementioned authentication and authorization and for the delivery of content are also described.
A uniform description language (e.g., “entitlements description language” or EDL that allows for management of protected content across heterogeneous network environments (including those outside of the MSO's direct control) is also described.
Detailed Description of Exemplary Embodiments
Exemplary embodiments of the apparatus and methods of the present invention are now described in detail. While these exemplary embodiments are described in the context of the aforementioned hybrid fiber coax (HFC) cable system or satellite network architecture having an multiple systems operator (MSO), digital networking capability, IP delivery capability, and plurality of client devices/CPE, the general principles and advantages of the invention may be extended to other types of networks and architectures, whether broadband, narrowband, wired or wireless, or otherwise, the following therefore being merely exemplary in nature. For instance, the invention may be adapted for use on so-called hybrid fiber copper (HFCu) networks, or WiMAX (IEEE Std. 802.16) wireless networks.
It will also be appreciated that while described generally in the context of a consumer (i.e., home) end user domain, the present invention may be readily adapted to other types of environments (e.g., commercial/enterprise, government/military, etc.) as well. Myriad other applications are possible.
Also, while certain aspects are described primarily in the context of the well-known Internet Protocol (described in, inter alia, RFC 791 and 2460) and Session Initiation Protocol (SIP), it will be appreciated that the present invention may utilize other types of protocols (and in fact bearer networks to include other internets and intranets) to implement the described functionality.
Moreover, while, many aspects of the invention are described within the context of traditional “on demand” services traditionally provided over e.g., a cable, satellite, or HFCu network (e.g., FVOD, SVOD, MOD, etc.), it will be appreciated that the concepts and apparatus described herein are readily extensible to other content delivery paradigms including without limitation broadcast (linear) and “start over”.
Other features and advantages of the present invention will immediately be recognized by persons of ordinary skill in the art with reference to the attached drawings and detailed description of exemplary embodiments as given below.
Exemplary Content Distribution Network—
The data/application origination point 102 comprises any medium that allows data and/or applications (such as a VOD-based or “Watch TV” application) to be transferred to a distribution server 104. This can include for example a third party data source, application vendor website, CD-ROM, external network interface, mass storage device (e.g., RAID system), etc. Such transference may be automatic, initiated upon the occurrence of one or more specified events (such as the receipt of a request packet or ACK), performed manually, or accomplished in any number of other modes readily recognized by those of ordinary skill.
The application distribution server 104 comprises a computer system where such applications can enter the network system. Distribution servers are well known in the networking arts, and accordingly not described further herein.
The VOD server 105 comprises a computer system where on-demand content can be received from one or more of the aforementioned data sources 102 and enter the network system. These servers may generate the content locally, or alternatively act as a gateway or intermediary from a distant source.
The CPE 106 includes any equipment in the “customers' premises” (or other locations, whether local or remote to the distribution server 104) that can be accessed by a distribution server 104.
Referring now to
The exemplary architecture 150 of
It will also be recognized, however, that the multiplexing operation(s) need not necessarily occur at the headend 150 (e.g., in the aforementioned MEM 162). As yet another alternative, a multi-location or multi-stage approach can be used, such as that described in U.S. Pat. No. 7,602,820, entitled “APPARATUS AND METHODS FOR MULTI-STAGE MULTIPLEXING IN A NETWORK” incorporated herein by reference in its entirety, which discloses inter alia improved multiplexing apparatus and methods that allow such systems to dynamically compensate for content (e.g., advertisements, promotions, or other programs) that is inserted at a downstream network node such as a local hub, as well as “feed-back” and “feed forward” mechanisms for transferring information between multiplexing stages.
Content (e.g., audio, video, data, files, etc.) is provided in each downstream (in-band) channel associated with the relevant service group. To communicate with the headend or intermediary node (e.g., hub server), the CPE 106 may use the out-of-band (OOB) or DOCSIS channels and associated protocols. The OCAP 1.0 (and subsequent) specification provides for exemplary networking protocols both downstream and upstream, although the invention is in no way limited to these approaches.
It will also be recognized that the multiple servers (broadcast, VOD, or otherwise) can be used, and disposed at two or more different locations if desired, such as being part of different server “farms”. These multiple servers can be used to feed one service group, or alternatively different service groups. In a simple architecture, a single server is used to feed one or more service groups. In another variant, multiple servers located at the same location are used to feed one or more service groups. In yet another variant, multiple servers disposed at different location are used to feed one or more service groups.
An optical transport ring (not shown) is also commonly utilized to distribute the dense wave-division multiplexed (DWDM) optical signals to each hub within the network in an efficient fashion.
In addition to on-demand and broadcast content (e.g., video programming), the system of
The CPE 106 are each configured to monitor the particular assigned RF channel (such as via a port or socket ID/address, or other such mechanism) for IP packets intended for the subscriber premises/address that they serve.
While the foregoing network architectures described herein can (and in fact do) carry packetized content (e.g., IP over MPEG for high-speed data or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), they are often not optimized for such delivery. Hence, in accordance with another embodiment of the present invention, a “packet optimized” delivery network is used for carriage of the packet content (e.g., IPTV content) when the request issues from an MSO network (see discussion of
Content Delivery Authorization and Message Exchange Architecture—
The approach to providing access to protected content outside of an MSO network described in the present disclosure are based in the exemplary embodiment on a pro-defined set of transactions or assertions which are passed between the content provider (e.g., programmer or other third-party entity) and the managed network operator (e.g., MSO). The assertions, categorized by authentication and authorization (each of which will be discussed in greater detail subsequently herein), are conducted between applications proprietary to both of the aforementioned organizations, yet externalized through a set of standards-based protocols. In one implementation of the invention, the protocols utilized include those defined by the Liberty Alliance Project, and/or by the Organization for the Advancement of Structured Information Standards (OASIS), although it will be recognized that other protocols may be used with equal success.
The Liberty Alliance, formed in 2001, created a set of open standards and guidelines for identity management with the fundamental concept of “identity federation” (or the linking of accounts within or across disparate organizations). The guidelines produced from the project, known as Liberty Alliance Identity Federation Framework (ID-FF) V1.2 specification, which is incorporated herein by reference in its entirety, define the process by which identities from trusted sources can be linked in order to reduce ongoing multiple logins, thus increasing identity assurance while reducing identity fraud. In 2003, the Liberty Alliance contributed their body of work to OASIS that was founded in 1993 under the name SGML Open. SGML Open's original charter was the creation of guidelines for interopeability among products supporting the Standard Generalized Markup Language (SGML), but in 1998 SGML Open changed its name and shifted its focus from SGML to Extensible Markup Language (XML), as it became widely adopted by the technology industry.
To date, specifications from OASIS have become the de facto standard for security and identification management between consenting business partners, which is represented through the Security Assertion Markup language (SAML) Specification (Version 2.0 released in 2005), as SAML Core: S. Cantor et al. Assertions and Protocols for the OASIS Security Assertion Markup Language (SAML) V2.0. OASIS Standard, March 2005. Document ID saml-core-2.0-os (http://docs.oasis-open.org/security/saml/v2.0/sa-core-2.0-os.pdf) and SAML Binding: S. Cantor et al. Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0. OASIS Standard, March 2005. Document ID saml-bindings-2.0-os (http://docs.oasisopen.org/security/saml/v2.0/saml-bindings-2.0-os.pdf), each of which is incorporated herein by reference in its entirety. Early versions of SAML and the ID-FF were compatible; however, the two standards became incompatible based on component changes within SAML for greater consistency and component symmetry. Other key differences addressed in SAML v2.0 were encryption metadata and multi-endpoint support for a single protocol. Also, SAML v2.0 generalized the Liberty functionality to account for more options or use cases for expanded definition. However, it will be appreciated that the present invention is not limited to any particular standards or languages, the foregoing SAML and ID-FF being merely exemplary of the broader principles of the invention.
Referring now to
As shown in
The programmers/sources 204 may for example include any broadcast provider (such as e.g., NBC, Turner Broadcasting, Viacom, etc.) which distributes content across one or more mediums, or through distribution agreements with the MSO. Subscribers include the individual consumers or users of video/audio/data services.
Subscribers request access to content via user devices such as e.g., consumer premises equipment (CPE) 106, personal media devices (PMD) 107, personal computers (PC), laptop computers, mobile devices, etc. The user devices may include any apparatus capable receiving audio/video/data services from the MSO 221 or programmer 204 via the Internet. Hence, two primary request/delivery models are envisaged (although others may be used as well, or combinations or variants of the foregoing): (i) request from an MSO-network device (e.g., CPE 106 such as an IP-enabled DSTB or premises gateway 113) to an Internet site, for content to be returned back to the requesting MSO-network device (see
An example of the former case (i) might be an IP-enabled DSTB or PC/DOCSIS cable modem registered with the MSO that utilizes MSO infrastructure to access the Internet (and the third party programmer/source site), with content being streamed back to the requesting device over a comparable pathway. Here, the MSO network acts both as a “bearer” and “authorizer” network.
An example of the latter case (ii) might be an IP-enabled mobile device (e.g., smartphone or laptop computer) which may or may not be registered with the MSO, and is being operated by an authorized MSO subscriber. The device may obtain access to the Internet via e.g., a service provider WLAN, cellular 3G/4G (e.g., LTE-A), WiMAX, or other such interface 250, whereby it may connect to the third party website and request content, the latter streamed to the device over a comparable return path when delivery is authorized. In this fashion, the MSO network is not a bearer, but rather merely an authorizer.
The flow of various communications (and the protected content) under the foregoing exemplary scenarios are also illustrated in
Once the subscriber (and/or device) is authenticated and authorized, the content may be provided from the programmer content server 203 to the requesting device (e.g., CPE 106, PMD 107, etc.).
As noted above, the requested/provided content may comprise broadcast content as well as on-demand content. Other types of content may also be provided. For example, so called “quick clips” content (described in co-owned U.S. Pat. No. 7,174,126 issued Feb. 6, 2007 and entitled “TECHNIQUE FOR EFFECTIVELY ACCESSING PROGRAMMING LISTING INFORMATION IN AN ENTERTAINMENT DELIVERY SYSTEM” incorporated herein by reference in its entirety), so-called “start-over” content (described in co-owned, co-pending U.S. Patent Publication No. 2005/0034171 entitled “TECHNIQUE FOR DELIVERING PROGRAMMING CONTENT BASED ON A MODIFIED NETWORK PERSONAL VIDEO RECORDER SERVICE” incorporated herein by reference in its entirety), so-called “lookback” content (as described in co-owned, co-pending U.S. patent application Ser. No. 10/913,064 filed Aug. 6, 2004 and entitled “TECHNIQUE FOR DELIVERING PROGRAMMING CONTENT BASED ON A MODIFIED NETWORK PERSONAL VIDEO RECORDER SERVICE” incorporated herein by reference in its entirety), and/or so-called “remote DVR” content (as discussed in co-owned U.S. Pat. No. 7,457,520 issued Nov. 25, 2008 and entitled “TECHNIQUE FOR PROVIDING A VIRTUAL DIGITAL VIDEO RECORDER SERVICE THROUGH A COMMUNICATIONS NETWORK” incorporated herein by reference in its entirety) may be ingested at the third party content source. Still further, enhanced access to premium based content which is not available to non-subscribers, or which cannot be delivered across traditional transport may also be provided, such as e.g., behind the scenes outtakes, alternate endings, actor interviews, etc.
The CLA 207 is used as an entry point into the MSO network's 221 web portals by both residential and commercial users. In one embodiment, the CLA 207 communicates with the EIS 214 to store user-specific information, including a digital identity. Hence, an MSO subscriber may establish a digital identity at the CLA 207 which is stored thereon, and which may be shared with the EIS 214 and storage entities communicating with each. The creation of an MSO-specific digital identity for each subscriber will be discussed in greater detail below.
It is via the CLA 207 that a subscriber in the illustrated embodiment may access subscriber-controlled services such as Digital Video Recorders (DVRs), personal video recorders (PVR), network-based DVR and/or PVR, and self-controlled phone services (such as, e.g., call forwarding, call waiting, etc.). A subscriber may also obtain information pertaining to call records and billing information by accessing the web portals via the CLA 207.
Delivery of content to the CPE 106 and/or PMD 107 occurs within the MSO network (i.e., under the paradigm of
Moreover, the foregoing apparatus and methods provide for enhanced content access, reproduction, and distribution control (via e.g., a DRM-based approach and other security and content control measures), as well as quality-of-service (QoS) guarantees which maintain high media quality and user experience, especially when compared to prior art “Internet TV” paradigms. In one exemplary implementation, the network may be based on an IMS (IP Multimedia System, such as e.g., that defined in relevant 3GPP standards) which includes SIP session protocols, as well as a Service Delivery Platform (SDP).
In another implementation (
In one variant of this approach, network services are sent “over the top” of other provider's infrastructure 250, thereby making the service provider network substantially transparent (i.e., the protected content requests and other communications are passed over the service provider network and the Internet as if they are any other traffic). In another variant, a cooperative approach between providers is utilized, so that features or capabilities present in one service provider's network (e.g., authentication of mobile devices to an AP or RAN) can be leveraged by another provider operating in cooperation therewith. In another embodiment, requested content may be authorized via the content and data distribution architecture 200, and provided to the CPE 106 and/or PMD 107 as described in co-owned, co-pending U.S. patent application Ser. No. 11/258,229 filed on Oct. 24, 2005 and entitled “METHOD AND APPARATUS FOR ON-DEMAND CONTENT TRANSMISSION AND CONTROL OVER NETWORKS”, which is incorporated herein by reference in its entirety. As discussed therein, data may be provided according to download or “on demand” paradigms. In one embodiment, the network comprises a cable television network connected with a CSP (cellular service provider) or wireless service provider (WSP), and on-demand content delivery is accomplished via a “point-to-point” approach wherein a session is established between a content receiving entity (such as a cellular telephone) and a distributing entity (e.g., a VOD server). Session establishment and data flow control are advantageously implemented using protocols and bandwidth that are typically used for (i) providing on-demand services to subscribers within the cable network, and (ii) delivery and control of streaming multimedia to client mobile devices.
Yet other mechanisms and architectures for providing content to PMDs 107 and/or CPE 106 located in or out of a managed network may be used consistent with the invention as well, the foregoing being merely exemplary of the broader principles.
As will be discussed in greater detail below, the architecture 200 utilizes information obtained from or stored at an MSO-maintained authorization server (not shown) to determine whether a requesting user device is authorized to receive the content. In one embodiment, the provision of content and use thereof are effectively controlled by the supplying web or programmer content server 203 (or any intermediary MSO-operated infrastructure). For example, once a user is authorized to receive content, the server 203 serves the content to the user device over the prescribed delivery path/model.
In another embodiment, various restrictions to the provision of content to a user at a display or rendering device associated with the user device are determined by the device (e.g., CPE 106, PMD 107, etc.) itself, as discussed in co-owned U.S. patent application Ser. No. 12/716,131 filed on Mar. 2, 2010, entitled “APPARATUS AND METHODS FOR RIGHTS-MANAGED CONTENT AND DATA DELIVERY”, and issued as U.S. Pat. No. 9,342,661 on May 17, 2016, which is incorporated herein by reference in its entirety. As discussed therein, a downloadable or transferable rights profile coupled with a “smart” media player application are given. The rights profile contains information regarding the specific rights of a device and/or a subscriber to access content. It is via the rights profile that the device (via the media player and its associated rights management application) determines whether to provide content to a subscriber.
In one implementation of the architecture of
In another exemplary embodiment, the receiving device may comprise a converged premises device (CPD) and/or a media bridge. The CPD may for example be of the type described in co-owned U.S. patent application Ser. No. 11/378,129 filed Mar. 16, 2006, entitled “METHODS AND APPARATUS FOR CENTRALIZED CONTENT AND DATA DELIVERY” and issued as U.S. Pat. No. 8,347,341 on Jan. 1, 2013, incorporated herein by reference in its entirety. As discussed therein, the CPD comprises a WLAN (e.g., Wi-Fi) and/or PAN (e.g., Bluetooth or 802.15) wireless interface. Packetized (e.g., IP) traffic may be exchanged between the CPD and a PMD 107 via, e.g. the WLAN/PAN interface. Hence, in one embodiment, the PMD 107 may request content from the CPD.
In another embodiment, the user device may comprise a media bridge, which may, for example, be of the type disclosed in co-owned U.S. patent application Ser. No. 12/480,597 filed Jun. 8, 2009, entitled “MEDIA BRIDGE APPARATUS AND METHODS”, and issued as U.S. Pat. No. 9,602,864 on Mar. 21, 2017, incorporated herein by reference in its entirety. As discussed therein, the media bridging apparatus acts as a connection between a PMD 107 (which may include e.g., an iPod™, handheld computer, smartphone, PDA, etc.) and a user's home network. This bridging apparatus may be used, for example, to convert content stored on the PMD 107 to a format capable of being presented on a user's set-top box or other client device. The bridging apparatus may also be utilized for transmitting content to the PMD 107 (such as by converting the content to a format capable of being stored/presented on the PMD 107) provided the user of the PMD 107 is authorized to receive the content.
Referring now to
As noted above in
As shown in
In one embodiment (illustrated at
The identity providers 218 are useful in accessing and evaluating subscriber information to determine if a requesting subscriber is a subscriber of the MSO 221, and/or the level of service or other service details of the subscriber's subscription. As discussed in greater detail elsewhere herein, a two-step process is used in one embodiment to authenticate the user, and then authorize what content they are entitled to access; failure can occur at either step. First, the authentication infrastructure 206 validates (i.e., authenticates) that the subscriber has an active account based on e.g., user entry of a correct username/password combination, regardless of service (e.g., video, high speed data, phone). Next, the authorization infrastructure 202 validates (i.e., authorizes) that the subscriber is entitled to access requested content based on subscription-based services (such as e.g., video).
The EIS 214 is used to store a subscriber's digital identity. A digital identity is in the present embodiment a subscriber-specific identifier which is used to uniquely (and optionally anonymously) identify the subscriber. A digital identity may further be linked to a particular MSO 221, a geographic region, demographic, subscriber type, etc. In one embodiment, the digital identity comprises a plurality of records identifiable by the subscriber's entry of a login and a password value at the CLA 207. In one such implementation, the EIS 214 and identity provider 218 in conjunction are responsible for authenticating a subscriber's identity for account linking or content delivery. For example, the EIS 214 may authenticate a subscriber if the programmer 204 has no system for validating a subscriber's identity, such as if the programmer 204 does not support its own identity management system (IDMS).
Referring again to
The SOA adapters 208 are used to revalidate a subscriber's identity, and obtain information from multiple disparate systems having subscriber information on purchased services (i.e., monthly and on-demand) stored thereon. The obtained information is used by the SOA adapters 208 to confirm or deny entitlement of the subscriber to requested content. The SOA 208 performs an authorization of subscriber-based requests for access to protected content. In one embodiment, “protected content” comprises that content which is protected by being placed behind a firewall or other similar security barrier/mechanism. Content may be protected based on one or both of the MSO 221 or/and programmer 204 identifying the programming as such, and may further be limited to certain ones of the MSO 221 (and/or other MSO's) subscribers. For example, certain content may only be made available to a particular tier of subscriber (e.g., premium subscriber, etc.) across one or multiple different MSOs.
Various reasons may exist for protecting the content, including for example: (i) it is “first run” or recent content that is surreptitiously obtained and distributed, would usurp significant revenue and advertising opportunities from the MSO and/or source; (ii) it is content that is not suitable for all classes of viewers (e.g., adult content); (iii) it is copyright or otherwise legally protected; (iv) it must be pre-processed before delivery in order to ensure one or more attributes such as proper advertisement insertion, encoding format/QoS, etc.
Additionally, content may be placed in a protected class according to e.g., franchising agreements which do not allow certain pieces of content to be distributed outside a set geographical area(s). Local sports, educational and government programming that cannot be or has not paid for the right to distribute across specified physical boundaries based on local franchising rights (or those of third-parties that distribute such content on behalf of the MSO), would be examples of such protected content.
Environment Setup—
Referring now to
As shown, per step 302, both the MSO 221 and the programmer 204 independently configure their networks to support connectivity between servers of each network. In one embodiment, this may include e.g., creating firewall policies, and/or translating the external Internet Protocol (IP) address to an internal address (as required). The well known network address translation (NAT) approach may be utilized for translating the external IP address to an internal address. Alternatively other mechanisms may be utilized, including those configured to masquerade and/or hide a network address, or change/rotate it as a function of time or accesses (e.g., for security reasons).
Next, at step 304, at least one of the MSO 221 and the programmer 204 set up a firewall. The policies set forth during the configuration step (step 302) may be implemented to establish the firewall as discussed above. In general terms, a formal firewall request is submitted to the MSO TSG 202 operators to process and add the programmer's IP address, addresses or address ranges to internal firewall policies. The TSG 202 operators add a policy to the firewall that allows two-way traffic between the programmer and the MSO (i.e., “white-lists” the programmer by IP address, etc.). White-listing of the type discussed herein is required because the MSO in many instances maps a specific port on the authorization server and does not allow the port to be open to the public. In another embodiment, no firewall setup is needed for the authentication servers 206. Rather, all traffic comes across port 443, which is already secure (i.e., HTTPS with encrypted transactions).
Then, per step 306, the connectivity between the MSO 221 and programmer 204 is validated. In one embodiment, the validation may include exchanging of port designations and IP addresses (as discussed above). Alternatively, the MSO may schedule a formal connectivity test that includes a “ping” and telnet set of tests between the programmer's servers and the MSO authentication and authorizations servers. During this connectivity test, the MSO and the programmer confirm access to one another's servers. If access cannot be confirmed, then corresponding operators for each the programmer and the MSO are contacted to aid in troubleshooting issues.
Next, executions of sample authentication and authorization transactions are performed. To accomplish this, the MSO provides the programmer a set of sample authentication and authorization transactions (i.e., formatted XMLs), which the programmer uses to “push” to the associated servers in its certification environment. The MSO and the programmer then confirm that the transactions are processed appropriately. If not, various troubleshooting techniques are used to determine why the transactions are failing, including e.g., looking through log files for corresponding request/response transactions.
Per step 308, digitally signed certificates used within the Secure Sockets Layer (SSL) 2-way interfaces are exchanged between the MSO 221 and programmer 204. In one embodiment, different servers may be used for the aforementioned authentication and authorization. Hence, separate Uniform Resource Locators (URLs) may be required for each server by the programmer 204.
For example, the authentication process may make use of Security Assertion Markup Language (SAML) for exchanging authentication and authorization data between security domains. As noted previously, SAML is a product of the OASIS® Security Services Technical Committee. The authentication process may follow the specification for Single Sign-On (SSO) between a service provider and the identity provider (e.g., the programmer 204 and MSO 221 respectively). Within the SAML domain, digital certificates are contained within a set of metadata that also includes other specific interface control values such as Time-To-Live (TTL) along with an applicable KeyDescriptor (i.e., public key portion of public/private encryption key pair). In the exemplary embodiment, both the MSO 221 and the programmer 204 generate specific metadata that is exchanged and loaded on one another's web servers. It is noted that the exchange of metadata may need to be accomplished using secure data exchange techniques (e.g., encryption, integrity protection such as cryptographic residues, etc.) as, in many instances, the metadata exchanged between the MSO 221 and programmer 204 is humanly readable. Once the metadata is loaded, then the trust relationship is formed, and assertions between parties can begin.
With respect to authorization, however, a more traditional Extensible Markup Language (XML) interface may be used. This may include, for example, passing data in a set of element structures that closely follows the concepts of eXtensible Access Control Markup Language (XACML). Within this framework, digitally signed certificates are exchanged and loaded to the MSO 221 and the programmer's 204 web servers, similar to the metadata. To complete the setup, a Common Secure Interoperability (CSI) session is conducted between the MSO 221 and the programmer 204, wherein the public key information is exchanged and both parties verify certificate signature, validity times, and revocation status.
Additional configurations by the MSO 221 and the programmer 204 may also be required outside the connectivity setup and certificate exchange. SAML general services are configured on associated web servers which further define attribute details used for processing of authentication assertions. The precise configuration of the SAML general services is performed within the framework of the application server being used and may vary based on product (e.g., Weblogic®, WebSphere®, Apache®, etc.).
Per step 310, the programmer 204 is then provided with a globally unique identifier (GUID) from the MSO 221; the programmer GUID is used during all authorization requests. Each time an authorization request is made from the programmer to the MSO 221, the programmer 204 provides its assigned programmer GUID. The programmer GUID is verified prior to any further processing by the MSO 221. The programmer GUID may, in one embodiment, comprise a 36 alpha/numeric-character string uniquely identifying the programmer in an obfuscated (non-readable) manner.
Appendices A-D hereto detail the functional requirements to which the provision of service according to one embodiment of the present invention must adhere. Appendix A hereto contains information on the formatting of the exemplary request (and response) according to one embodiment of the invention.
Appendix B illustrates exemplary requirements of the service request. The table of Appendix B includes both: (i) the XML element definitions, and (ii) any validation and behavioral rules to be applied by the request. The table describes the service specific XML elements in the body of the service's request (note that other elements common to all services may also be required). The element list includes basic XML element descriptions. The request header is assumed to be the standard header used unless otherwise indicated. Each service must use a standard header when sending responses or receiving requests from SOA.
Each element listed in the table is unique for this service, and is validated by a series of standard validation requirements. See Appendix C for the list of validation requirements that are common to all SOA services for the elements listed. Any additional unique validation requirements that should be implemented for this service are fully described as an exception requirement (as described elsewhere herein).
The table of Appendix D illustrates additional exemplary request requirements according to an exemplary embodiment of the invention.
A specific set of values defining the resources (e.g., channels) supported by a programmer 204 are also negotiated as part of the setup process of the method of
The table(s) of Appendices E, et seq. provides the detailed requirements for the service request definition, including the XML element definitions, as well as any validation and behavioral rules to be applied by the response.
Appendix E illustrates exemplary service-specific XML elements in the body of the service's response. The hierarchy of the requests is: subject (SubscriberID), resource (ResourceID), action (ActionID), environment (EnvironmentID and SubscriberIP). The table of Appendix F illustrates exemplary response requirements.
Next, per step 314, after the MSO 221 and programmer 204 have begun communication, certain types of information, such as e.g., “co-branded” information, may be configured and displayed to the subscriber during the login process. In one embodiment, the co-branded information may comprise information such as banners, advertisements, etc., which have been pre-defined and approved by both the MSO 221 and the programmer 204. The co-branded text and images from the MSO 221 and/or the programmer 204 (i.e., co-branded information) are loaded to each party's web servers. The co-branded information is mapped to the content display pages on the programmer's 204 site, and login pages on MSO's site, which is mapped to the appropriate HTML forms/fields. Co-branded text and images are set up by the MSO 221 for each of the programmers 204 and each content or virtual channel. When a subscriber logs in via either the programmer 204 or the MSO 221 site, the co-branding information is displayed in the pre-approved manner as mutually defined and agreed upon between the MSO 221 and the programmer 204.
Lastly, per step 316, the subscriber is able to request content, and have the requested content delivered thereto using authentication and authorization processes discussed in greater detail below.
The table of Appendix G illustrates exemplary exception requirements according to one embodiment of the present invention. The table contains exemplary requirements related to business exceptions that pertain specifically to this service. In addition, this service includes any common SOA framework exceptions outlined in the SOA error guidelines of Appendix H.
Account Creation—
Methods for authentication and authorization (discussed in detail below) of a subscriber requesting access to content according to the present invention rely on the requesting subscriber having set up a digital identity.
In this implementation, the subscriber is responsible for establishing his/her digital identity through the CLA 207, maintained in one embodiment by the MSO 221. As shown, per step 402, the subscriber is prompted to enter, and enters, information at the CLA 207. The subscriber enters information which is used to validate the subscriber's identity. Additional information may be entered, and/or the above-provided information may further be used to associate the subscriber to an MSO 221 business market (such as a demographic, service level type, etc.) or division (e.g., a geographic region, advertisement zone, etc.). Correlation of the subscriber to a division may be useful for example in enabling account records to be correlated to the subscriber, and/or for performing searches for service details during the authorization process (discussed below).
The subscriber may also be prompted for login and password values as part of the digital identity creation process of step 402. The login and password values are defined by the subscriber within for example, a given MSO 221 policy. The login and password values, once established and stored (at the MSO 221 or programmer 204) may then be used for future login attempts to the MSO site and/or to the programmer site in order to access services supported thereby.
It will be appreciated that while a login and password combination are described above, other implementations of the invention may utilize other security mechanisms or approaches. For example, in one variant, the login and password are also coupled with a challenge question (for which the user has previously provided an answer). In another variant, a user-specific or pseudo-unique icon is used, such that the user must enter (i) the login identity; (ii) the password, and (iii) a selection of “their” icon from among many possible icons. In yet another variant, the IP address and/or MAC address from which the user request is issued id evaluated in conjunction with the user-supplied login information to further validate that the request is coming from a registered address or device, respectively.
Per step 404, the CLA 207 communicates with the EIS 214. These entities communicate to set various attributes surrounding the subscriber's profile and per step 406, the EIS 214 assigns to the subscriber a subscriber identifier (e.g., GUID). In one embodiment, similar to the aforementioned programmer GUID, the subscriber GUID may comprise a 36 alpha/numeric character value, or may take other forms. The subscriber GUID uniquely identifies the subscriber in an obfuscated manner (i.e., not exposing any private information to internal or external parties). As will be discussed in greater detail below, the subscriber GUID is utilized to provide authentication and authorization of the subscriber when the subscriber requests content at the MSO and/or programmer site.
It is appreciated that various mechanisms for providing assistance in the event the subscriber is unable to create their digital identity may be employed. For example, by entering the subscriber's zip code or region (e.g., state, city), the subscriber may be directed to division-specific contact details, along with online information aiding the user with usage on various service offerings. Frequently asked questions (FAQs) and access to an online help via an “ask” or “help” feature may also be provided. Access to online assistance may also be provided during the authentication process, if required.
As noted above, the subscriber may, in one embodiment, be required to also create a login and password (or enter other verification information) at the programmer's website. According to this embodiment, the programmer 204 implements its own IDMS-based solution which may or may not link accounts stored therein to those of the MSO 221. The aforementioned linking being used to reduce the need for ongoing authentications (discussed herein below).
In order to provide content to a requesting subscriber, the subscriber must be authenticated and authorized to view the requested content.
Authentication with Linked Accounts—
In one embodiment of the invention, a single subscriber is authenticated only once, the process creating a link between the MSO 221 information for the subscriber and the programmer information for the same subscriber (i.e., federating the accounts). According to this embodiment, the subscriber will not have to be authenticated each time they attempt to view content, but rather are authenticated only once. In one variant, the methods and apparatus of co-owned, co-pending U.S. patent application Ser. No. 12/834,801 filed concurrently herewith and entitled “APPARATUS AND METHODS FOR CONTENT MANAGEMENT AND ACCOUNT LINKING ACROSS MULTIPLE CONTENT DELIVERY NETWORKS” and issued as U.S. Pat. No. 9,906,838 on Feb. 27, 2018, which has been previously incorporated by reference in its entirety, may be utilized for providing identity federation.
To accomplish the aforementioned account federation, the programmer 204 must employ at least a basic mechanism for identity management (such as e.g., an IDMS). An exemplary method of federated authentication is illustrated in
As shown, per step 502, the subscriber logs into a programmer website in order to request access to protected content (step 504). As noted above, the content may be protected by being placed behind a firewall, however other methods of content protection may alternatively or additionally be employed (such as e.g., encryption, hashing or cryptographic residue for integrity protection, etc.). The type of login (e.g., password and user ID combination), information required at login and creation of a login identity are each controlled by the programmer 204 itself. For example, the programmer 204 determines whether the subscriber may identify him/herself within the programmer website by e.g., providing an email address and password combination, or any of the other mechanisms previously described with respect to
At step 506, upon subscriber login, the programmer 204 uses the IP address of the requesting subscriber device to perform a reverse lookup of the MSO 221 associated to that device (i.e., IP address aaa.bbb.ccc.ddd is associated with MSO XYZ). It is determined at step 508 whether the MSO 221 (XYZ) associated to the subscriber device address is a “known” MSO 221; i.e., is at that point known to the programmer 204. It will be appreciated, however, that alternative methods for determining the MSO 221 associated to the subscriber and/or to the subscriber device may be utilized, the reverse lookup method being merely exemplary. For instance, the programmer 204 may obtain a MAC address for the device issuing the request, and use that MAC address to perform the reverse lookup. As yet another alternative, a programmer or third party database of user/MSO associations (such as by user name, email address, etc.) may be accessed. Myriad other approaches may be used as well to make this determination.
If the MSO 221 of the requesting device is unknown or cannot be determined, then the subscriber is provided with a list of MSO's from which the subscriber may select the appropriate provider (step 510). In one embodiment, the list may be provided as a pop up window, or alternatively the subscriber may be redirected to an alternate web page for selecting the appropriate MSO 221. Alternatively, the user may be prompted to simply enter the name or identifier of their MSO (e.g., TWC). A “word wheel” type function of the type known in the user interface arts may optionally be used; i.e., as the user enters the letter “T”, the available choices of MSOs are narrowed to only those beginning with the letter “T”, and so forth.
Once the appropriate MSO 221 is selected (step 510), or if the MSO 221 of the requesting device is known to the programmer 204, the programmer 204 sends an assertion to the identity provider 218 of the appropriate MSO 221 (step 512). In one embodiment, the assertion comprises an SAML Extensible Hypertext Markup Language (XHTML) form; e.g., a Hypertext Transfer Protocol (HTTP) POST message. The exemplary POST message is transmitted to the identity provider server 218, and includes the following information fields or elements:
At step 514, the subscriber is redirected to a login page for the MSO 221. At the MSO 221 login page, the subscriber is prompted to provide login information (e.g., MSO-specific login information). The subscriber must log into the MSO 221 web page via the identity provider server 218, since no session has been started. That is to say, a session is started each time the subscriber logs into the identify provider. The session remains active for a predefined period (e.g., 15 minutes), and terminates automatically after this time period expires for security purposes, regardless of whether the user is still on the programmer's web site. Having the session active allows the subscriber to move from one programmer to another without re-authenticating or across video assets if asset based authorizations are invoked. However, authorizations are still required regardless of the presence of an active session when changing programmer sites and/or video assets.
In one embodiment, the login requires the subscriber to enter the login and password values which were established during creation of that subscriber's digital identity (see
The MSO identity provider 218 examines the provided login information to determine whether it is valid at step 516. If the login information is not valid, an error message is transmitted to the subscriber (step 518).
If the subscriber's login to the MSO 221 fails at step 516, the subscriber may be provided an opportunity to be redirected to the CLA 207 in order to resolve the issue. For example, the subscriber may resolve the issue by directly logging into the MSO website. A successful login at the MSO website causes the subscriber to be redirected back the programmer site, and the method repeats at step 512. If the subscriber is unsuccessful at logging into the MSO website directly, the subscriber may be directed to a support page, phone number, email address, or live chat. In another example, if the subscriber has not yet created a digital identity, the subscriber may do so at the MSO website (see
If the subscriber's login to the MSO 221 is successful (at step 516), the MSO identity provider server 218 processes the assertion (sent at step 512), and provides a response at step 520. In one embodiment, the response to the SAML assertion is an XHTML form which is sent to the browser containing the following elements:
The “RelayState” identifies the destination that the user (e.g., MSO subscriber) is attempting to access (i.e., programmer URL or guarded deep link). This value is passed by the programmer with the SAML request to the MSO's identity provider. Upon successful user login, the SAML response is passed back to the user's browser, which includes the RelayState that routes the user to the associated URL containing guarded content.
The browser then sends the information (e.g., SAML assertion) back the programmer 204. Per step 522, the programmer 204 may link its stored subscriber login information to that of the MSO 221 by storing the subscriber's GUID within the programmer's protected data store(s) of their IDMS framework, so that future linking or authentication assertions are advantageously not required.
Lastly per step 524, the process continues to authorization of the subscriber to view the requested content. The process of authorization will be discussed in greater detail below.
Authentication without Linked Accounts—
Referring now to
As noted above, SAML supports both federated (linked accounts) and non-federated authentication models, each having their own relative strengths and weaknesses. For example, in the federated model, the user only needs to access the MSO login page once to authenticate; thereafter, the user simply uses the programmer's login capabilities. This eliminates the need to access the MSO login page if the programmer's site is the primary origin for content viewing. However, in the federated model, the MSO has no control over session management, and is reliant on the authorization service 202 to validate whether the user is still an active subscriber. Furthermore, in certain implementations, the federation model requires that the user remember two sets of usernames/passwords.
Alternatively, in the non-federated model, the programmer does not have to support IDMS functionality, and may be totally reliant on the MSO to manage username/password functions and associated identities (i.e., sub-accounts). Furthermore, the MSO is able to recognize during the authorization request that a subscriber is no longer active, and may eliminate the need for a programmer to execute an authorization request for that subscriber. However, under the non-federated model, the user is required to access the MSO's login page for each browser session, and again after a predetermined period from the start of a session, which is based on the expiry value contained in the authorization response (e.g., 24 hours). Still further, the MSO may be required to support complex login pages managed through iframes and pop-ups to mask redirection from the programmer's site to an MSO hosted login page
Per step 602 of the method, a request for access to protected content is received from the subscriber at the programmer website. According to this method, the subscriber need not login to the programmer's site, because the programmer 204 does not support an IDMS or other system for maintaining subscriber information. For instance, in one case, the subscriber directly or indirectly enters the programmer's website URL into their Internet browser (e.g., clicks on a hyperlink or the like), and when at the site, selects content for download, thereby causing a request to be sent to the programmer's content server.
When the request is received, an MSO 221 associated with the subscriber and/or the device is determined at step 604. This can be accomplished for example using the methods previously described herein, or other approaches. For example, the subscriber may be redirected to a page on the programmers' site where the user can select from a dropdown list or menu structure or other mechanism, their associated MSO. Thereafter, the corresponding login page will be displayed to complete the authentication process based on the implemented approach (i.e., redirect, popup or iframe). Note that the programmer may provide MSO selection capabilities on a main page, foregoing the need to redirect to a sub-page.
In another embodiment, the programmer only supports guarded content for the MSO, and when the user selects something requiring login, the subscriber is presented a login page based on the implemented approach (i.e., redirect, popup or iframe).
In yet another embodiment, the programmer can derive the subscriber's MSO based on the IP address from which they originated. Then, the programmer can elect to initiate the MSO login process based on the implemented approach (i.e., redirect, popup or iframe) and/or confirm with the subscriber their MSO to ensure the correct login page is presented.
Next, per step 606, the programmer 204 sends the request to the identity provider 218 of the associated MSO identified in step 604. In one embodiment, the programmer 204 sends an XHTML form that POSTs to the identity provider server 218, the POST containing the following elements:
The identity provider 218 determines that no login session has been created or is active, and redirects the subscriber to the MSO login page, where the subscriber must login to validate credentials (step 608). According to this method 600, the subscriber has only one set of login credentials (i.e., those necessary to log into the MSO site). Since the programmer 204 in the embodiment of
Per step 610, the login credentials are validated. If the entered credentials are not valid (do not match stored information for the subscriber, and/or no stored information for the subscriber can be found), an error message is presented to the subscriber (612). Failure during the login process may cause the subscriber to be redirected to CLA 207 to resolve the conflict by re-trying the login process, creating a digital identity (if one has not yet been created), seeking help from online resources, or directly contacting the MSO 221.
If the credentials are valid, the identity provider 218 returns a response to the request at step 614. In one embodiment, an XHTML form is returned to the browser which returns the following elements to the programmer 204:
Lastly, once the subscriber is authenticated, the method proceeds to subscriber authorization (step 616), where it is determined whether the subscriber is authorized to view the requested content. The process of authorization will be discussed in greater detail below.
Account Decoupling (De-Federation)—
As noted above, in certain embodiments, the programmer 204 may utilize a separate IDMS, and may link a subscriber account contained therein to an MSO 221 subscriber account for the same subscriber. Later, it may be necessary to decouple or unlink the subscriber's account, such as if the subscriber is no longer a customer of a first MSO, and instead now is a customer of a second MSO. This may be executed through a backoffice “call” or communication from the programmer 204 to the MSO 221.
To accomplish the do-federation process, the programmer 204 in one embodiment must create a set of web pages which allow the subscriber to conduct the unlinking process, including verifying the subscriber wants to remove the link of their account with the programmer 204 to the MSO 221.
As shown, per step 702 a request to de-federate the account is received from the subscriber at the programmer 204. In response to receiving the subscriber request, the programmer 204 develops a request to be sent to the MSO 221 (step 704). The programmer 204 may utilize the Name Identifier Management Protocol or other such mechanism to generate and send the request to the identity provider 218, for example, an <ManageIDNameRequest> containing the subscriber's pseudonym may be sent.
The Name Identifier Management Protocol provides mechanisms to change the value or format of the name of a principal (subscriber). The issuer of the request can be either the service provider (programmer) or the identity provider (MSO). The protocol also provides a mechanism to terminate an association of a name between an identity provider and service provider.
The ManageNameID within the Name Identifier Management Protocol provides a way to initiate name identifier changes or terminations. For example, after establishing a name identifier for use when referring to a principal, the identity provider may want to change its value and/or format. Additionally, an identity provider might want to indicate that a name identifier will no longer be used to refer to the principal. The identity provider will notify service providers of the change by sending them a ManageNameIDRequest. A service provider also uses this message type to register or change the SPProvidedID value (included when the underlying name identifier is used to communicate with it), or to terminate the use of a name identifier between itself and the identity provider.
The identity provider 218 (and/or other MSO 221 entities) processes the request at step 706. If the request is processed successfully (step 708), then per step 712, a verification code is returned to the programmer 204. In one embodiment, the verification code may comprise a <ManageIDNameResponse> with a code verifying the success of the unlinking. If the de-federation is successful, any future attempts by the subscriber to view protected content will be denied. The subscriber must re-establish its identity via the authentication process (
If the request is not processed successfully (step 708), then, per step 710, a failure message is returned to the programmer 204. In one embodiment, the failure message may comprise a <ManageIDNameResponse> with a code indicating the failure of the unlinking. The programmer 204 can initiate another request if the response provided by the MSO 221 indicates failure to unlink the accounts.
In another embodiment, the methods and apparatus of co-owned, co-pending U.S. patent application Ser. No. 12/834,801 entitled “APPARATUS AND METHODS FOR CONTENT MANAGEMENT AND ACCOUNT LINKING ACROSS MULTIPLE CONTENT DELIVERY NETWORKS” and issued as U.S. Pat. No. 9,906,838 on Feb. 27, 2018, which has been previously incorporated by reference in its entirety may be utilized for de-federating accounts.
Authorization—
As discussed above, once a subscriber is authenticated, it must be determined whether the subscriber is authorized to view the particular content requested, and optionally if any use (or even distribution) restrictions apply. An exemplary authorization process is illustrated in
In one embodiment, authorization is conducted real-time against various backend information management systems within the MSO 221. In one example, the authorization process (e.g.,
As illustrated, per step 802, before an authorization can take place, it is determined whether the subscriber is logged into the MSO site. The subscriber must have started a session through either the programmer's IDMS application (if account linking is supported by the programmer 204), or by logging into the identity provider server 218 (if account linking is not being supported by the programmer 204). If it is determined that the subscriber has not yet logged in, per step 804, the subscriber is redirected to either the programmer's or MSO's co-branded login pages, where a session may be setup.
Next, per step 806, an authorization request is sent from the programmer 204 to the SOA 208 (at the MSO 221). In one embodiment, the request may include the subscriber GUID acquired during the authentication process, along with other information including one or more of the following elements:
Note that in one embodiment, the ResourceID element contains identifiers for multiple resources supported by a programmer 204 (i.e., 1 thru X channels, or a request for ALL), thus reducing the number of individual authorizations per subscriber. As will be discussed below, the MSO 221 may then return a single response which provides individual decisions for each resource.
At step 808, when an authorization request is received, the SOA 208 immediately interrogates the EIS 214 to validate that the subscriber GUID is active. If the subscriber GUID is not active, a message is returned to the programmer 204 indicating that the programmer may retry (step 810) sending the authorization request.
If the subscriber GUID is active, the SOA 208 continues to process the request for information. Per step 812, the SOA 208 determines the subscriber identity. Acquisition of subscriber identity may include determining an associated division ID, billing system ID, etc.
At step 814, the SOA 208 begins collection of service details associated to the subscriber including e.g., service level. The SOA 208 initiates a series of requests to backend information management systems, or to local data caches within the MSO 221, for retrieval of service details after the identity of the subscriber's account has been obtained from the EIS 214. The information collected is then compared to the request to determine authorization at step 816.
If the service details match the requirements for the requested content, a “Permit” message is transmitted to the programmer 204 (step 818). For example, if the service details indicate that the subscriber is currently purchasing a premium level of service, and the requested content is within the premium package, the subscriber will be permitted access to the content. The Permit message indicates that the subscriber was found to have rights to the resource (i.e., active account and active service). Accordingly, the content may be provided to the subscriber (step 820).
At step 822, the programmer 204 may elect to set an entitlement cookie on the subscriber's browser after receiving a Permit decision from the MSO 221 (step 818). The entitlement cookie allows the subscriber to view content from the programmer's site without requiring an additional authorization request to be issued, unless the cookie is cleared or the subscriber uses a different device. While the user experience is heightened by establishing a cookie and eliminating delays in content viewing when another authorization request is conducted, security concerns may be raised. For example, a risk of fraud through reuse of the cookie across a wider user community that is not subscribing to paid services of the MSO 221 and/or the programmer 204 is increased.
However, it is noted that each authorization request has an expiry value in the exemplary embodiment, and the programmer must adhere to the same value in the cookie, which is tested during certification. The default is 24-hours, but the value is configurable by the MSO based on ResourceID. Reducing the expiry value can help reduce fraud possibilities by requiring more frequent authorizations. In addition, the cookie is meant to be specific to a programmer and associated resource (i.e., channel or brand), and not ubiquitous across programmers or other resources, thus, requiring the subscriber to login each time if outside the 15-minute authentication session and execution of another authorization, regardless of within the 15-minute session, or if accounts are federated.
It is appreciated that, if a cookie is used, the cookie does not contain the subscriber GUID in order to protect the privacy of the subscriber. In other words, the GUID should not be persisted in the cookie. While an obfuscated value, the GUID is still permanently linked to the subscriber's account under one embodiment of the authentication service.
In lieu of the cookie, the programmer 204 may elect instead to persist the value of the last good authorization request for each subscriber within the programmer's 204 backoffice application(s). The stored authorization request may be used for future subscriber requests within for example, a 24-hour period for the same content. Using this embodiment, additional authorization requests for the same subscriber (and for the same content) are reduced. The programmer 204 may resort to the stored authorization request as well as in the event of a failed authorization from the MSO 221 indicating an “Indeterminate” response. As discussed elsewhere herein, an Indeterminate response indicates that the lookup to MSO 221 backend information systems failed to return expected results or timed out during the request.
The programmer 204 can reference the last successful authorization (as discussed above) when the subscriber terminates and reestablishes their web session. For example, if the content requested and associated length of time is within e.g., a 24-hour expiration window, then no further authorizations are required. However, if the authorization is no longer within the 24-hour (or other predetermined length of time) expiration window for the requested content, then the programmer 204 is required to execute another authorization, such as according to the method of
As noted previously, the aforementioned process can be used by the programmer 204 for authorizations that failed to produce any response from the MSO 221, or for those which receive an Indeterminate response. In these situations, the programmer 204 may elect to default to the last positive authorization, and provide content to the Subscriber according to one or more policies for doing so, which are predetermined and agreed upon by the MSO 221 and programmer 204. For instance, the content may be provided with copyright/DRM or other types of protection in order to limit its distribution/copying. Or, the content may only be provided with certain “trick mode” or Start-over type features (or lack thereof).
Referring again to
In some instances the MSO 221 may not be able to determine whether the request for content and subscriber service details match. Accordingly, the MSO 221 may transmit a “Not Applicable” or an Indeterminate message. The Not Applicable message indicates that the SystemID, ResourceID, and/or SubscriberID are not configured, associated and/or recognized. As discussed elsewhere herein, an Indeterminate response indicates that the lookup to MSO 221 backend information systems failed to return expected results or timed out during the request.
The decision table of Appendix I illustrates an exemplary mechanism for how the service renders a decision, what should be logged to the SOA logging system, and what reason should be returned to the programmer with the rendered decision. Note that the numeric value in the “Reason” column of Appendix I may be returned in the reason field of the response as discussed elsewhere herein. In one embodiment, the text in the “Reason Description” column is not returned as part of the service response.
In response to receiving the Not Applicable or an Indeterminate message, the programmer 204 may elect to automatically issue another authorization request to the MSO 221 (i.e., retry) in an attempt to obtain a less ambiguous response (step 826). As noted above, in response to an Indeterminate message, other methods for authorizing the subscriber may be used, such as reverting to a previously authorized request.
In many instances, a decision value of Indeterminate may be used to indicate that one or more pieces of information passed on the request were not recognized/provided, and are likely outdated and require updating, by either the programmer 204 or the MSO 221, if a different response is to be expected.
The decision to use an automated retry process (step 826) is an implementation detail which is determined by both the MSO 221 and the programmer 204, including the amount of retries (i.e., number and frequency) permissible. Generally, the method of
It is also noted that while authorization under the method of
In one exemplary embodiment, the transmitted Permit, Deny, Not Applicable and Indeterminate messages received from the SOA 208 will each contain the following information:
Exemplary business rules which may be utilized to make decisions on whether to send any of the aforementioned messages are illustrated in the table of Appendix J.
It is also noted that rules or functional restrictions can be relayed from the MSO to the programmer 204 via messaging conducted pursuant to a particular subscriber request, or alternatively can be pre-positioned within the programmer site as a rule set (i.e., every Gold subscriber request has Rule Set 1 applied, every Silver subscriber has Rule Set 2 applied, and so forth). The former approach has the advantage of being able to particularly tailor the rule(s) sent to the programmer 204 to the individual subscriber (e.g., via the subscriber GUID, MAC address, or other unique information), yet necessitates extra messaging traffic and latency.
Additionally, the MSO 221 and/or programmer 204 may, throughout the authorization process (
Potential delays in the authorization process may be addressed by causing the programmer to return the subscriber to the RelayState URL and start playing advertisements within their player while the authorization completes. In many instances, advertisements are shown prior to displaying a requested video; therefore, pre-running the advertisement would be consistent in the current user experience while the authorization is executed.
In the event a DENY response is returned, then the programmer can use the opportunity to suggest an “up-sell” of MSO services and/or supply a message to contact the MSO for additional information on how to access online content including telephone numbers and web site URLs.
Appendix K illustrates exemplary reason codes per MSO organizational unit (e.g., per division): Each cell in the table represents the subscriber message content to be returned for that reason for that division(s). Although only the Greensboro (GSO) divisions are illustrated in the given table, it is appreciated that other divisions may use similar messages and/or reason codes (such as e.g., New York City (NYC), Rochester (ROC), Syracuse (SYR), Charlotte (CLT), etc.). The table contains the values to be configured for development (DEV) and quality assurance (QA) environments. The development environment is used for the development of the authentication and authorizations services. The quality assurance environment is used for testing of the authentication and authorizations services. For the authorization service, there are multiple QA environments used for functional, performance and regression testing as well as one used for external testing with programmers during the formal certification process (discussed above).
Various MSO 221 entities are responsible for working with the business owners (or programmers) to determine values to be used in production. However, in the absence of explicit business input on production values, all divisions are configured to use the “Other” value listed in the table.
Session Control—
Control of a subscriber's web session may be directed by the programmer 204 in one embodiment (such as via the account linking or federation discussed above). Alternatively, the MSO 221 may control the web session by e.g., hosting all or part of content streamed by programmers 204, and/or both the MSO 221 and programmer 204 may provide control mechanisms thereby allowing one or dual paths for subscriber access.
According to the linked or federated embodiment, the MSO 221 will only have session awareness during the initial authentication process for account linking (see
Alternatively, if the programmer 204 relies on the MSO 221 to manage the login process (e.g., the non-federated approach of
For either of the above described embodiments (linked and non-linked accounts), the programmer 204 is provided a pseudonym and GUID upon successful login (i.e., at authentication). The GUID may then be used for authorization requests throughout the established session.
In one embodiment, the pseudonym is transient and only valid during the session. It is the responsibility of the programmer 204 to destroy the invalid pseudonym and information relating thereto, once the session expiry time (or other condition, such as number of accesses) has elapsed, or when the programmer 204 detects that the subscriber has exited the programmer's site or a restricted set of web pages. In addition, the programmer 204 may send an XHTML form that will POST to the identity provider server 218 containing the following information:
It is appreciated that various metrics on the “user experience” may be collected and shared by both the MSO 221 and the programmer 204 throughout each user session. The scope of the information gathered and related web analytics applied is defined by both the MSO 221 and programmer 204. For example, such metrics may include the time an established session lasts, the ratio of successful login attempts to total login attempts, etc. Examples of authorization based metrics are listed in the tables of
Performance, Operational, and Security Requirements, Errors and Logging—
The performance requirements utilized with the exemplary embodiments of the invention address expected service response times and required task-level accuracy. Exemplary performance requirements are illustrated in Appendices L-S. As defined therein, the requirements are only measurable within the internal service boundaries.
Appendix L illustrates exemplary volume and speed requirements.
Appendix M illustrates exemplary reliability and availability requirements.
Appendices N-O illustrate exemplary operational requirements; the operational requirements describe the environment in which the service will exist. This table contains requirements on the physical environment, hardware, software, communication interfaces and data formats.
The table of Appendix P illustrates exemplary requirements related to the security of the service. More specifically, this table provides details related to service access and the sensitivity of data processed by the service.
Exemplary requirements for logging, monitoring and alarming are illustrated in Appendix Q.
Sample SOA service summary logging reports are illustrated in Appendix R.
Appendix S illustrates exemplary disaster recovery requirements.
User Device—
Generally, the exemplary user devices useful with the present invention will include e.g., a network interface (including an interface for accessing the Internet), a processor and associated storage, and optionally a plurality of back end interfaces for communication with other devices. The user device can assume literally any discrete form factor, including those adapted for settop/desktop, hand-held, or wall-mounted use, or alternatively may be integrated in whole or part (e.g., on a common functional basis) with other devices if desired. Additionally, the user device may include other elements and interfaces such as for example an interface for the HomePlug A/V standard which transmits digital data over power lines, a PAN (e.g., 802.15), Bluetooth, or other short-range wireless interface for localized data communication, etc.
In one embodiment, the network interface receives content and/or data via one or more RF tuners configured to receive content from an HFC network 101. The RF tuner(s) may comprise traditional video RF tuner(s) adapted to receive video signals over, e.g., a QAM. For example, the RF tuner(s) may comprise one or more tuners, a demodulator, decryption module, and demultiplexer of the type well known in the art, although other configurations may be used. A wideband tuner arrangement such as that described in co-owned U.S. patent application Ser. No. 11/013,671 entitled “Method and Apparatus for Wideband Distribution of Content” filed Dec. 15, 2004, issued as U.S. Pat. No. 9,723,267 on Aug. 1, 2017, and incorporated herein by reference in its entirety, may also be utilized, such as where the content associated with one or more program streams is distributed across two or more QAMs. Additionally, the RF tuner(s) may incorporate functionality to modulate, encrypt/multiplex as required, and transmit digital information for receipt by upstream entities such as the CMTS.
Alternatively, the network interface may comprise any other means for receiving content from a network. Digital data received via the network interface may include for example MPEG-2 encoded programming data that is forwarded to a television monitor via a video interface. Programming data may also be stored on the storage unit for later distribution by way of the video interface, or using a Wi-Fi interface, Ethernet interface, FireWire (IEEE Std 1394), USB/USB2, or any number of other such options.
Programming and other types of data including pictures, video, music or MP3 files, software applications, metadata files, etc. may also be received by way of the various digital interfaces in the user device. These data may be stored locally (e.g., in the storage unit) or even on a device or network agent in communication with the user device, for later use by a user as is discussed in co-owned U.S. patent application Ser. No. 11/378,129 entitled “METHODS AND APPARATUS FOR CENTRALIZED CONTENT AND DATA DELIVERY”, and issued as U.S. Pat. No. 8,347,341 on Jan. 1, 2013, previously incorporated herein.
During operation of the user device, a client application (located in the storage unit) is run on the microprocessor. The client application follows appropriate protocol for sending requests for content and receiving requested content as well as for providing additional information to the network to facilitate authentication and authorization (discussed above) by providing information regarding the subscriber/user and/or device to the network entities discussed above. For example, the client application may provide subscriber account information upstream in order for the EIS 217, SOA 208, and other entities to identify the subscriber and provide content based on what is known (at the MSO 221) about the subscriber.
While the foregoing embodiments of the invention have been described primarily with respect to the network-side elements (i.e., programmer site 204, MSO, etc.), it will be appreciated that other implementations of the invention may utilize a specially adapted CPE or client device (e.g., PMD) used by the subscriber in generating the request for protected content. For example, the CPE or client software application or stack component may obtain and format request messages or other messages (e.g., logins) for certain programmer sites according to a prescribed configuration. In one such implementation, a subscriber accesses a designated programmer website, wherein the website passes the subscriber its programmer GUID or other identifying information. The client application then uses this information to recognize the site as “MSO affiliated”, and thereby necessarily being compliant with the aforementioned protocols and EDL. The client application then formats and requests for protected content or other messages between the subscriber device and that website according to the EDL, such as by including MAC address, subscriber GUID, etc. In this fashion, the website is relieved of some of the burden of such formatting, and one or more subsequent messages between the two entities may be obviated (i.e., the website does not have to go back and ask the client device for each requisite piece of information it requires to process the subscriber's request). In order to address privacy and security concerns with this model, it is appreciated that in one embodiment, authentication and authorization interfaces may be created with additional content management systems (CMS) entities including utilization of this model where data is stored more securely at a server.
In another embodiment, the various restrictions (if any) to the provision of content to a user at a display or rendering device associated with the user device are determined by the device (e.g., CPE 106, PMD 107, etc.) itself, as discussed in co-owned, co-pending U.S. patent application Ser. No. 12/716,131 filed on Mar. 2, 2010, entitled “APPARATUS AND METHODS FOR RIGHTS-MANAGED CONTENT AND DATA DELIVERY”, and issued as U.S. Pat. No. 9,342,661 on May 17, 2016, which is incorporated herein by reference in its entirety. As discussed therein, a downloadable or transferable rights profile coupled with a “smart” media player application are given. The rights profile contains information regarding the specific rights of a device and/or a subscriber to access content. It is via the rights profile that the device (via the media player and its associated rights management application) determines whether to provide content to a subscriber, and/or what restrictions or privileges to apply. Hence, in the present context, the MSO (e.g., CLA 207) might generate a rights profile and pass this profile (or information indicating which of a plurality of pre-positioned profiles to apply) to the programmer 204 for transmission to the smart media player on the client device.
In addition, the client application may be configured to collect information regarding the user's actions with respect to content, and pass this upstream (whether to the programmer or the MSO). For example, the client application may record button presses, playback events, trick mode events, etc. and pass this information to MSO 221 entities which may use the information to make various business decisions including e.g., secondary content insertion decisions.
Methods and apparatus for providing such secondary content insertion may be of the type discussed in co-owned U.S. patent application Ser. No. 11/441,476 filed on May 24, 2006 entitled “SECONDARY CONTENT INSERTION APPARATUS AND METHODS”, and issued as U.S. Pat. No. 9,386,327 on Jul. 5, 2016, which is incorporated herein by reference in its entirety, and may be utilized to provide dynamic secondary content insertion (e.g., replacement of dated or geographically inappropriate advertisements or promotions), and thereby allow the MSO or other network operator to adjust the secondary content to make it more applicable to the remote user's context (e.g., location, hardware/software environment, date/time, etc.). Additionally, the apparatus and methods discussed in co-owned U.S. patent application Ser. No. 11/198,620 filed on Aug. 4, 2005 and entitled “METHOD AND APPARATUS FOR CONTEXT-SPECIFIC CONTENT DELIVERY”, and issued as U.S. Pat. No. 9,286,388 on Mar. 15, 2016, which is incorporated herein by reference in its entirety, may be utilized consistent with the present invention. As discussed therein, contextually-related “secondary” content (e.g., advertising messages, useful informational links, etc.) may be provided in association with other primary content selected by the user.
While there are no limitations on the user devices in reference to the authentication and authorization services discussed herein, in one embodiment, the devices may include an operating system (e.g., Windows 2000, Windows XP, Windows Vista, Windows 7, Mac OS X 10.2 “Jaguar”, 10.3 “Leopard”, 10.4 “Tiger”), RAM (e.g., 128 MB or 512 MB), video card (e.g., 32 MB or 128 MB), Internet browser (e.g., Internet Explorer 5.5 (or higher), or Firefox/Mozilla 1.5 (or higher)), Internet broadband Connection, and media player application (e.g., Adobe Flash or similar).
It is further noted that power line-based Internet adapters and other wireless technology such as Wi-Fi, Bluetooth and wireless data cards may be used consistent with the exemplary embodiment as long as they can support the proper download speeds necessary to render video play at an acceptable user level (i.e., not causing jerkiness, freezing dropout, pixilation, etc.).
Anonymity—
As noted above, certain data (including collected data, etc.) may be particular to or identified with a particular subscriber, user, or user device. Accordingly, such data may, in addition to being obfuscated as described above, also be anonymized by inter alia, the use of a cryptographic hash to protect the privacy of the identified subscriber, user, and/or device. In one embodiment, the techniques for providing anonymity utilizing a cryptographic hash described in U.S. patent application Ser. No. 11/186,452 filed Jul. 20, 2005 and entitled “METHOD AND APPARATUS FOR BOUNDARY-BASED NETWORK OPERATION”, which is incorporated herein by reference in its entirety, may be utilized in conjunction with the present invention. As disclosed therein, the identity of a subscriber device or subscriber is anonymized by using a cryptographic hash coupled with an optional “opaque” variable which carries information relating to the subscriber device of the hash with which it is associated. The hash and opaque variable-frustrate de-encryption or reverse-engineering of the individual subscriber's identity or specific location. Alternative methods of providing anonymization may also be utilized consistent with the present invention.
While complete anonymization (i.e., there is no way of tracing or identifying the source) is generally not applicable to information which must be used to uniquely identify an individual and/or device, partial anonymization such as that described above is readily used with the present invention. For example, it may be desirable to perform a one-way hash of a user's IP address or MAC address so that someone surreptitiously obtaining the information cannot determine the source data (actual address), but the hash algorithm produces a known deterministic result with the same “seed”, and hence the hash output can be used to uniquely identify a given user/device, such as by matching that hashed output with known outputs from the same algorithm corresponding to existing subscribers/devices. This hashing is to be distinguished from encryption, wherein the original source data (address) can in fact be recovered and read when the encrypted data is decrypted (such as via a public/private encryption key pair).
Business/Operational Decision Engine—
In another aspect of the invention, a so-called “decision” engine may be disposed at e.g., the SOA 208, EIS 217, CIA 207, identity provider 218, content server 203, CPE 106, or other location (e.g., rendered as one or more computer programs disposed thereon). This engine comprises, in an exemplary embodiment, one or more software routines adapted to control the authentication/authorization and content delivery processes in order to achieve one or more goals relating to operations or business (e.g., profit or revenue or subscriber retention). Included within these areas are network optimization and reliability goals, increased maintenance intervals, increased subscriber or user satisfaction/longevity, increased subscription base, higher profit (e.g., from increased advertising revenues, more subscriber “views” of given content, greater flexibility in the types and locations of platforms from which the subscriber may access content, and so forth).
These decision rules may comprise a separate entity or process, and may also be fully integrated within other processing entities (such as the applications running on the aforementioned entities and/or the client application), and controlled via e.g., a GUI displayed on a device connected to the relevant server, network entity, or even CPE. In effect, the rules engine comprises a supervisory entity which monitors and selectively controls content access and delivery operation at a higher level, so as to implement desired operational or business rules. The decision engine can be considered an overlay of sorts to the more fundamental algorithms used to accomplish required network operation, such as IP address assignment, secondary content selection and insertion, statistical multiplexing, BSA switching, and so forth.
For example, the SOA 208, EIS 217, CLA 207, identity provider 218, content server 203, CPE 106 may invoke certain operational protocols or decision processes based on information or requests received from the CPE 106 or PMD 107, conditions existing within the network, demographic data, geographic data, etc. However, these processes may not always be compatible with higher-level business or operational goals, such as maximizing profit or system reliability. Hence, when imposed, the business/operational rules can be used to dynamically (or manually) control access to and delivery of content. The decision rules may be, e.g., operational or business-oriented in nature, and may also be applied selectively in terms of time of day, duration, specific local areas, or even at the individual user level (e.g., via specific identification of the CPE or client device via TUNER ID, IP address, MAC address, or the like, or via a user-based login or “entitlements” profile of the type previously described herein).
For example, one decision rule implemented by the decision engine may comprise providing protected content from the third party (e.g., programmer 204) according to a tiered system. Content under such an approach might be selected in part on the revenue such delivery will bring to the MSO based on the content source.
In another variant, the use rights or features provided with the requested (protected) content may be varied as a function of e.g., subscriber subscription level, time of day, requesting device capability, etc. For instance, a request received from a premium level of “Gold” subscriber might be serviced with a content stream that includes complete “trick mode” functionality (i.e., FF, REW, Pause, etc.), or for broadcasts a “start over” functionality, whereas a lower tier subscriber's request might not include one or any of these capabilities. The number of plays can be limited as well; e.g., Gold subscribers receive unlimited plays, while lower tiers receive only one or a finite number of plays of the content. As noted above, these rules or functional restrictions can be relayed from the MSO to the programmer 204 via messaging conducted pursuant to a particular subscriber request, or alternatively can be pro-positioned within the programmer site as a decision rule set.
Moreover, the quality of content provided can be varied as needed or desired. For instance, use of different encodings or bitrates (e.g., HD versus SD), QoS parameters, latency, etc. can be employed depending on the subscriber (individually), the general classification of the subscriber (e.g., Gold), time of day, available resources, revenue/profit implications of each option, etc.
Secondary content (e.g., advertisements, promotions, featured links, etc.) insertion decisions may also be governed by these business/operational rules, as previously noted.
It will also be recognized that both the MSO and the third party (e.g., programmer) may employ different business or operation decision rules to one another. For example, the MSO might establish preferential rules or classes for the various programmers, such that service provided to these different programmers is differentiated in some fashion. In one such case, those programmers paying the MSO a fee, or with which the MSO has a pre-existing business relationship, may be given preferential service and capabilities.
The MSO and/or programmer may also structure a business relationship whereby one “pays” the other via some sort of consideration for servicing of requests. For example, an MSO might pay a given programmer $X for each valid MSO subscriber request serviced by the programmer, since the MSO is in effect leveraging the programmer's infrastructure to extend the reach of its capabilities for the MSO customers (i.e., extension of the “four any's” model described in co-owned U.S. Provisional Application Ser. No. 61/256,903 entitled “METHODS AND APPARATUS FOR PACKETIZED CONTENT DELIVERY OVER A CONTENT DELIVERY NETWORK” previously incorporated herein. Conversely, the programmer might pay the MSO consideration for each MSO subscriber request serviced, or an advertisement click-through basis, etc. in that if the MSO instructs its subscribers to use the programmer's site preferentially over others, this may generate additional revenue (such as via the aforementioned click-throughs) for the programmer or its advertisers.
In one embodiment, the so called “Roadrunner Video Channel” or “Symphoni™ Online” products of Assignee hereof may use the authentication/authorization applications. Under this model the MSO can conduct its own regional or localized advertising as part of programmer ingested content or outside, including eventually targeted personalization of advertisements based on user demographics and viewing heuristics. This includes e.g., click-through to advertiser's web sites that can be monitored via web analytics for monetary remittance or collection.
Many other approaches and combinations of various operational and business paradigms are envisaged consistent with the invention, as will be recognized by those of ordinary skill when provided this disclosure.
It will be recognized that while certain aspects of the invention are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the invention, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the invention disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the invention as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the invention. The foregoing description is of the best mode presently contemplated of carrying out the invention. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the invention. The scope of the invention should be determined with reference to the claims.
This application is a divisional of and claims priority to U.S. patent application Ser. No. 14/861,628 filed on Sep. 22, 2015 of the same title, and issuing as U.S. Pat. No. 10,136,172 on Nov. 20, 2018, which is a divisional of and claims priority to U.S. patent application Ser. No. 12/834,796 filed on Jul. 12, 2010 of the same title, and issuing as U.S. Pat. No. 9,357,247 on May 31, 2016, and which is a continuation-in-part of U.S. patent application Ser. No. 12/536,724 filed on Aug. 6, 2009, entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER A NETWORK”, and issued as U.S. Pat. No. 8,341,242 on Dec. 25, 2012, which claims priority to (i) U.S. Provisional Application Ser. No. 61/117,265 filed on Nov. 24, 2008 and entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER A NETWORK” and (ii) U.S. Provisional Application Ser. No. 61/117,248 filed on Nov. 24, 2008 and entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO STORED DATA OVER A NETWORK,” each of which are incorporated herein by reference in its entirety. Additionally, this application is related to U.S. Provisional Application Ser. No. 61/256,903 filed on Oct. 30, 2009 and entitled “METHODS AND APPARATUS FOR PACKETIZED CONTENT DELIVERY OVER A CONTENT DELIVERY NETWORK”, and to co-owned, co-pending U.S. patent application Ser. No. 12/834,801 entitled “APPARATUS AND METHODS FOR CONTENT MANAGEMENT AND ACCOUNT LINKING ACROSS MULTIPLE CONTENT DELIVERY NETWORKS”, each of which are incorporated herein by reference in its entirety. The present application is further related to co-owned and co-pending U.S. patent application Ser. No. 13/721,154 filed on Dec. 20, 2012 and entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER A NETWORK”, which is also incorporated herein by reference in its entirety. A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5410344 | Graves et al. | Apr 1995 | A |
| 5528284 | Iwami et al. | Jun 1996 | A |
| 5534911 | Levitan | Jul 1996 | A |
| 5557319 | Gurusami et al. | Sep 1996 | A |
| 5628284 | Sheen et al. | May 1997 | A |
| 5708961 | Hylton et al. | Jan 1998 | A |
| 5745837 | Fuhrmann | Apr 1998 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5818438 | Howe et al. | Oct 1998 | A |
| 5822530 | Brown | Oct 1998 | A |
| 5838921 | Speeter | Nov 1998 | A |
| 5897635 | Torres et al. | Apr 1999 | A |
| 5940738 | Rao | Aug 1999 | A |
| 5999535 | Wang et al. | Dec 1999 | A |
| 6125397 | Yoshimura et al. | Sep 2000 | A |
| 6167432 | Jiang | Dec 2000 | A |
| 6181697 | Nurenberg et al. | Jan 2001 | B1 |
| 6219710 | Gray et al. | Apr 2001 | B1 |
| 6233389 | Barton et al. | May 2001 | B1 |
| 6259701 | Shur et al. | Jul 2001 | B1 |
| 6286049 | Rajakarunanayake et al. | Sep 2001 | B1 |
| 6317884 | Eames et al. | Nov 2001 | B1 |
| 6345038 | Selinger | Feb 2002 | B1 |
| 6389538 | Gruse et al. | May 2002 | B1 |
| 6396531 | Gerszberg et al. | May 2002 | B1 |
| 6473793 | Dillon et al. | Oct 2002 | B1 |
| 6519062 | Yoo | Feb 2003 | B1 |
| 6523696 | Saito et al. | Feb 2003 | B1 |
| 6546016 | Gerszberg et al. | Apr 2003 | B1 |
| 6564381 | Hodge et al. | May 2003 | B1 |
| 6640145 | Hoffberg et al. | Oct 2003 | B2 |
| 6642938 | Gilboy | Nov 2003 | B1 |
| 6642939 | Vallone et al. | Nov 2003 | B1 |
| 6643262 | Larsson et al. | Nov 2003 | B1 |
| 6672961 | Uzun | Jan 2004 | B1 |
| 6694145 | Riikonen et al. | Feb 2004 | B2 |
| 6711742 | Kishi et al. | Mar 2004 | B1 |
| 6718552 | Goode | Apr 2004 | B1 |
| 6748395 | Picker et al. | Jun 2004 | B1 |
| 6754904 | Cooper et al. | Jun 2004 | B1 |
| 6757906 | Look et al. | Jun 2004 | B1 |
| 6758746 | Hunter et al. | Jul 2004 | B1 |
| 6774926 | Ellis et al. | Aug 2004 | B1 |
| 6788676 | Partanen et al. | Sep 2004 | B2 |
| 6847778 | Vallone et al. | Jan 2005 | B1 |
| 6865746 | Herrington et al. | Mar 2005 | B1 |
| 6909726 | Sheeran | Jun 2005 | B1 |
| 6918131 | Rautila et al. | Jul 2005 | B1 |
| 6925257 | Yoo | Aug 2005 | B2 |
| 6931018 | Fisher | Aug 2005 | B1 |
| 6934964 | Schaffer et al. | Aug 2005 | B1 |
| 6944150 | McConnell et al. | Sep 2005 | B1 |
| 6978474 | Sheppard et al. | Dec 2005 | B1 |
| 7003670 | Heaven et al. | Feb 2006 | B2 |
| 7006881 | Hoffberg et al. | Feb 2006 | B1 |
| 7009972 | Maher et al. | Mar 2006 | B2 |
| 7013290 | Ananian | Mar 2006 | B2 |
| 7020652 | Matz et al. | Mar 2006 | B2 |
| 7027460 | Iyer et al. | Apr 2006 | B2 |
| 7039048 | Monta et al. | May 2006 | B1 |
| 7051352 | Schaffer | May 2006 | B1 |
| 7054902 | Toporek et al. | May 2006 | B2 |
| 7055031 | Platt | May 2006 | B2 |
| 7055165 | Connelly | May 2006 | B2 |
| 7068639 | Varma et al. | Jun 2006 | B1 |
| 7096483 | Johnson | Aug 2006 | B2 |
| 7099308 | Merrill et al. | Aug 2006 | B2 |
| 7100183 | Kunkel et al. | Aug 2006 | B2 |
| 7103905 | Novak | Sep 2006 | B2 |
| 7106382 | Shiotsu | Sep 2006 | B2 |
| 7136866 | Springer et al. | Nov 2006 | B2 |
| 7146627 | Ismail et al. | Dec 2006 | B1 |
| 7149772 | Kalavade | Dec 2006 | B1 |
| 7154901 | Chava et al. | Dec 2006 | B2 |
| 7167895 | Connelly | Jan 2007 | B1 |
| 7174126 | McElhatten et al. | Feb 2007 | B2 |
| 7174127 | Otten et al. | Feb 2007 | B2 |
| 7174385 | Li | Feb 2007 | B2 |
| 7185355 | Ellis et al. | Feb 2007 | B1 |
| 7206775 | Kaiser et al. | Apr 2007 | B2 |
| 7207055 | Hendricks et al. | Apr 2007 | B1 |
| 7209458 | Ahvonen et al. | Apr 2007 | B2 |
| 7213036 | Apparao et al. | May 2007 | B2 |
| 7228556 | Beach et al. | Jun 2007 | B2 |
| 7242960 | Van et al. | Jul 2007 | B2 |
| 7242988 | Hoffberg et al. | Jul 2007 | B1 |
| 7254608 | Yeager et al. | Aug 2007 | B2 |
| 7257106 | Chen et al. | Aug 2007 | B2 |
| 7260823 | Schlack et al. | Aug 2007 | B2 |
| 7266726 | Ladd et al. | Sep 2007 | B1 |
| 7293276 | Phillips et al. | Nov 2007 | B2 |
| 7312391 | Kaiser et al. | Dec 2007 | B2 |
| 7325043 | Rosenberg et al. | Jan 2008 | B1 |
| 7325073 | Shao et al. | Jan 2008 | B2 |
| 7330483 | Peters, Jr. et al. | Feb 2008 | B1 |
| 7330510 | Castillo et al. | Feb 2008 | B2 |
| 7333483 | Zhao et al. | Feb 2008 | B2 |
| 7336787 | Unger et al. | Feb 2008 | B2 |
| 7337458 | Michelitsch et al. | Feb 2008 | B2 |
| 7340762 | Kim | Mar 2008 | B2 |
| 7343398 | Lownsbrough | Mar 2008 | B1 |
| 7359375 | Lipsanen et al. | Apr 2008 | B2 |
| 7363643 | Drake et al. | Apr 2008 | B2 |
| 7376386 | Phillips et al. | May 2008 | B2 |
| 7382786 | Chen et al. | Jun 2008 | B2 |
| 7404082 | Medvinsky et al. | Jul 2008 | B2 |
| 7406515 | Joyce et al. | Jul 2008 | B1 |
| 7444655 | Sardera | Oct 2008 | B2 |
| 7457520 | Rosetti et al. | Nov 2008 | B2 |
| 7486869 | Alexander et al. | Feb 2009 | B2 |
| 7487523 | Hendricks | Feb 2009 | B1 |
| 7532712 | Gonder et al. | May 2009 | B2 |
| 7548562 | Ward et al. | Jun 2009 | B2 |
| 7567983 | Pickelsimer et al. | Jul 2009 | B2 |
| 7571452 | Gutta | Aug 2009 | B2 |
| 7592912 | Hasek et al. | Sep 2009 | B2 |
| 7602820 | Helms et al. | Oct 2009 | B2 |
| 7603469 | Fletcher | Oct 2009 | B2 |
| 7609637 | Doshi et al. | Oct 2009 | B2 |
| 7624337 | Sull et al. | Nov 2009 | B2 |
| 7650319 | Hoffberg et al. | Jan 2010 | B2 |
| 7690020 | Lebar | Mar 2010 | B2 |
| 7693171 | Gould | Apr 2010 | B2 |
| 7721314 | Sincaglia et al. | May 2010 | B2 |
| 7725553 | Rang et al. | May 2010 | B2 |
| 7742074 | Minatogawa | Jun 2010 | B2 |
| 7770200 | Brooks et al. | Aug 2010 | B2 |
| 7809942 | Baran et al. | Oct 2010 | B2 |
| 7870245 | Butler | Jan 2011 | B2 |
| 7893171 | Le et al. | Feb 2011 | B2 |
| 7900052 | Jonas et al. | Mar 2011 | B2 |
| 7908626 | Williamson et al. | Mar 2011 | B2 |
| 7916755 | Hasek et al. | Mar 2011 | B2 |
| 7936775 | Iwamura | May 2011 | B2 |
| 7954131 | Cholas et al. | May 2011 | B2 |
| 8024762 | Britt | Sep 2011 | B2 |
| 8042054 | White et al. | Oct 2011 | B2 |
| 8095610 | Gould et al. | Jan 2012 | B2 |
| 8166126 | Bristow et al. | Apr 2012 | B2 |
| 8170065 | Hasek et al. | May 2012 | B2 |
| 8219134 | Maharajh et al. | Jul 2012 | B2 |
| 8249497 | Ingrassia et al. | Aug 2012 | B2 |
| 8281352 | Brooks et al. | Oct 2012 | B2 |
| 8302111 | Ladd et al. | Oct 2012 | B2 |
| 8341242 | Dillon et al. | Dec 2012 | B2 |
| 8347341 | Markley et al. | Jan 2013 | B2 |
| 8429702 | Yasrebi et al. | Apr 2013 | B2 |
| 8484511 | Engel et al. | Jul 2013 | B2 |
| 8516529 | Lajoie et al. | Aug 2013 | B2 |
| 8520850 | Helms et al. | Aug 2013 | B2 |
| 8583758 | Casey et al. | Nov 2013 | B2 |
| 8732854 | Cholas | May 2014 | B2 |
| 8738607 | Dettinger et al. | May 2014 | B2 |
| 8750490 | Murtagh et al. | Jun 2014 | B2 |
| 8750909 | Fan et al. | Jun 2014 | B2 |
| 8805270 | Maharajh et al. | Aug 2014 | B2 |
| 8843622 | Graham et al. | Sep 2014 | B1 |
| 8949919 | Cholas et al. | Feb 2015 | B2 |
| 8995815 | Maharajh et al. | Mar 2015 | B2 |
| 9083513 | Helms et al. | Jul 2015 | B2 |
| 9124608 | Jin et al. | Sep 2015 | B2 |
| 9124650 | Maharajh et al. | Sep 2015 | B2 |
| 9215423 | Kimble et al. | Dec 2015 | B2 |
| 9258608 | Dillon et al. | Feb 2016 | B2 |
| 9906838 | Cronk et al. | Feb 2018 | B2 |
| 20010004768 | Hodge et al. | Jun 2001 | A1 |
| 20010043613 | Wibowo et al. | Nov 2001 | A1 |
| 20010050945 | Lindsey | Dec 2001 | A1 |
| 20020002688 | Gregg et al. | Jan 2002 | A1 |
| 20020024943 | Karaul et al. | Feb 2002 | A1 |
| 20020027883 | Belaiche | Mar 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020042921 | Ellis | Apr 2002 | A1 |
| 20020053076 | Landesmann | May 2002 | A1 |
| 20020056125 | Hodge et al. | May 2002 | A1 |
| 20020059218 | August et al. | May 2002 | A1 |
| 20020059619 | Lebar | May 2002 | A1 |
| 20020066033 | Dobbins | May 2002 | A1 |
| 20020083451 | Gill et al. | Jun 2002 | A1 |
| 20020087995 | Pedlow et al. | Jul 2002 | A1 |
| 20020095689 | Novak | Jul 2002 | A1 |
| 20020123931 | Splaver et al. | Sep 2002 | A1 |
| 20020131511 | Zenoni | Sep 2002 | A1 |
| 20020144267 | Gutta et al. | Oct 2002 | A1 |
| 20020147771 | Traversat et al. | Oct 2002 | A1 |
| 20020152091 | Nagaoka et al. | Oct 2002 | A1 |
| 20020152299 | Traversat et al. | Oct 2002 | A1 |
| 20020178444 | Trajkovic et al. | Nov 2002 | A1 |
| 20020188744 | Mani | Dec 2002 | A1 |
| 20020188869 | Patrick | Dec 2002 | A1 |
| 20020194595 | Miller et al. | Dec 2002 | A1 |
| 20030005453 | Rodriguez et al. | Jan 2003 | A1 |
| 20030012190 | Kaku et al. | Jan 2003 | A1 |
| 20030028451 | Ananian | Feb 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030065623 | Corneil | Apr 2003 | A1 |
| 20030093794 | Thomas et al. | May 2003 | A1 |
| 20030097574 | Upton | May 2003 | A1 |
| 20030115267 | Hinton et al. | Jun 2003 | A1 |
| 20030135628 | Fletcher et al. | Jul 2003 | A1 |
| 20030163443 | Wang | Aug 2003 | A1 |
| 20030165241 | Fransdonk | Sep 2003 | A1 |
| 20030166401 | Combes et al. | Sep 2003 | A1 |
| 20030200548 | Baran et al. | Oct 2003 | A1 |
| 20030208767 | Williamson et al. | Nov 2003 | A1 |
| 20030217137 | Roese et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030220100 | McElhatten et al. | Nov 2003 | A1 |
| 20040034677 | Davey et al. | Feb 2004 | A1 |
| 20040034877 | Nogues | Feb 2004 | A1 |
| 20040045032 | Cummings et al. | Mar 2004 | A1 |
| 20040045035 | Cummings et al. | Mar 2004 | A1 |
| 20040045037 | Cummings et al. | Mar 2004 | A1 |
| 20040117254 | Nemirofsky et al. | Jun 2004 | A1 |
| 20040133923 | Watson et al. | Jul 2004 | A1 |
| 20040137918 | Varonen et al. | Jul 2004 | A1 |
| 20040166832 | Portman et al. | Aug 2004 | A1 |
| 20040230994 | Urdang et al. | Nov 2004 | A1 |
| 20040250273 | Swix et al. | Dec 2004 | A1 |
| 20050034171 | Benya | Feb 2005 | A1 |
| 20050044223 | Meyerson | Feb 2005 | A1 |
| 20050049886 | Grannan et al. | Mar 2005 | A1 |
| 20050055220 | Lee et al. | Mar 2005 | A1 |
| 20050055729 | Atad et al. | Mar 2005 | A1 |
| 20050066353 | Fransdonk | Mar 2005 | A1 |
| 20050083921 | McDermott, III et al. | Apr 2005 | A1 |
| 20050086334 | Aaltonen et al. | Apr 2005 | A1 |
| 20050086683 | Meyerson | Apr 2005 | A1 |
| 20050108763 | Baran et al. | May 2005 | A1 |
| 20050114701 | Atkins et al. | May 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050130585 | Gnuschke et al. | Jun 2005 | A1 |
| 20050138193 | Encarnacion et al. | Jun 2005 | A1 |
| 20050157731 | Peters | Jul 2005 | A1 |
| 20050165899 | Mazzola | Jul 2005 | A1 |
| 20050177855 | Maynard et al. | Aug 2005 | A1 |
| 20050188415 | Riley | Aug 2005 | A1 |
| 20050223097 | Ramsayer et al. | Oct 2005 | A1 |
| 20050228725 | Rao et al. | Oct 2005 | A1 |
| 20050289616 | Horiuchi et al. | Dec 2005 | A1 |
| 20050289618 | Hardin | Dec 2005 | A1 |
| 20060020786 | Helms et al. | Jan 2006 | A1 |
| 20060021004 | Moran et al. | Jan 2006 | A1 |
| 20060021019 | Hinton et al. | Jan 2006 | A1 |
| 20060041905 | Wasilewski | Feb 2006 | A1 |
| 20060041915 | Dimitrova et al. | Feb 2006 | A1 |
| 20060047957 | Helms et al. | Mar 2006 | A1 |
| 20060053463 | Choi | Mar 2006 | A1 |
| 20060088030 | Beeson et al. | Apr 2006 | A1 |
| 20060095940 | Yearwood | May 2006 | A1 |
| 20060117379 | Bennett et al. | Jun 2006 | A1 |
| 20060130099 | Rooyen | Jun 2006 | A1 |
| 20060130101 | Wessel | Jun 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060136964 | Diez et al. | Jun 2006 | A1 |
| 20060136968 | Han et al. | Jun 2006 | A1 |
| 20060149850 | Bowman | Jul 2006 | A1 |
| 20060156392 | Baugher et al. | Jul 2006 | A1 |
| 20060161635 | Lamkin et al. | Jul 2006 | A1 |
| 20060171423 | Helms et al. | Aug 2006 | A1 |
| 20060187900 | Akbar | Aug 2006 | A1 |
| 20060190990 | Gruper et al. | Aug 2006 | A1 |
| 20060206712 | Dillaway et al. | Sep 2006 | A1 |
| 20060209799 | Gallagher et al. | Sep 2006 | A1 |
| 20060218604 | Riedl et al. | Sep 2006 | A1 |
| 20060221246 | Yoo | Oct 2006 | A1 |
| 20060238656 | Chen et al. | Oct 2006 | A1 |
| 20060248553 | Mikkelson et al. | Nov 2006 | A1 |
| 20060259927 | Acharya et al. | Nov 2006 | A1 |
| 20060291506 | Cain | Dec 2006 | A1 |
| 20070019645 | Menon | Jan 2007 | A1 |
| 20070022459 | Gaebel, Jr. et al. | Jan 2007 | A1 |
| 20070022469 | Cooper et al. | Jan 2007 | A1 |
| 20070025372 | Brenes et al. | Feb 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070049245 | Lipman | Mar 2007 | A1 |
| 20070053513 | Hoffberg et al. | Mar 2007 | A1 |
| 20070061023 | Hoffberg et al. | Mar 2007 | A1 |
| 20070067851 | Fernando et al. | Mar 2007 | A1 |
| 20070073704 | Bowden et al. | Mar 2007 | A1 |
| 20070076728 | Rieger et al. | Apr 2007 | A1 |
| 20070081537 | Wheelock | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070118848 | Schwesinger et al. | May 2007 | A1 |
| 20070121578 | Annadata et al. | May 2007 | A1 |
| 20070121678 | Brooks et al. | May 2007 | A1 |
| 20070124488 | Baum et al. | May 2007 | A1 |
| 20070124769 | Casey et al. | May 2007 | A1 |
| 20070124781 | Casey et al. | May 2007 | A1 |
| 20070150920 | Lee et al. | Jun 2007 | A1 |
| 20070153820 | Gould | Jul 2007 | A1 |
| 20070154041 | Beauchamp | Jul 2007 | A1 |
| 20070157234 | Walker | Jul 2007 | A1 |
| 20070157262 | Ramaswamy et al. | Jul 2007 | A1 |
| 20070169144 | Chen et al. | Jul 2007 | A1 |
| 20070180230 | Cortez | Aug 2007 | A1 |
| 20070204300 | Markley et al. | Aug 2007 | A1 |
| 20070204314 | Hasek et al. | Aug 2007 | A1 |
| 20070209054 | Cassanova | Sep 2007 | A1 |
| 20070209059 | Moore et al. | Sep 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070219910 | Martinez | Sep 2007 | A1 |
| 20070220553 | Branam et al. | Sep 2007 | A1 |
| 20070226365 | Hildreth et al. | Sep 2007 | A1 |
| 20070245376 | Svendsen | Oct 2007 | A1 |
| 20070250880 | Hainline | Oct 2007 | A1 |
| 20070250912 | Rassool et al. | Oct 2007 | A1 |
| 20070261116 | Prafullchandra et al. | Nov 2007 | A1 |
| 20070276925 | La Joie | Nov 2007 | A1 |
| 20070276926 | Lajoie et al. | Nov 2007 | A1 |
| 20070280298 | Hearn et al. | Dec 2007 | A1 |
| 20070288637 | Layton et al. | Dec 2007 | A1 |
| 20070288715 | Boswell et al. | Dec 2007 | A1 |
| 20070294717 | Hill et al. | Dec 2007 | A1 |
| 20070294738 | Kuo et al. | Dec 2007 | A1 |
| 20070299728 | Nemirofsky et al. | Dec 2007 | A1 |
| 20080009345 | Bailey et al. | Jan 2008 | A1 |
| 20080021836 | Lao | Jan 2008 | A1 |
| 20080022012 | Wang | Jan 2008 | A1 |
| 20080059804 | Shah et al. | Mar 2008 | A1 |
| 20080066112 | Bailey et al. | Mar 2008 | A1 |
| 20080086750 | Yasrebi et al. | Apr 2008 | A1 |
| 20080091805 | Malaby et al. | Apr 2008 | A1 |
| 20080091807 | Strub et al. | Apr 2008 | A1 |
| 20080092163 | Song et al. | Apr 2008 | A1 |
| 20080092181 | Britt | Apr 2008 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080098450 | Wu et al. | Apr 2008 | A1 |
| 20080112405 | Cholas | May 2008 | A1 |
| 20080133551 | Wensley et al. | Jun 2008 | A1 |
| 20080137541 | Agarwal et al. | Jun 2008 | A1 |
| 20080155059 | Hardin et al. | Jun 2008 | A1 |
| 20080162353 | Tom et al. | Jul 2008 | A1 |
| 20080170530 | Connors et al. | Jul 2008 | A1 |
| 20080170551 | Zaks | Jul 2008 | A1 |
| 20080177998 | Apsangi et al. | Jul 2008 | A1 |
| 20080192820 | Brooks et al. | Aug 2008 | A1 |
| 20080201386 | Maharajh et al. | Aug 2008 | A1 |
| 20080201748 | Hasek | Aug 2008 | A1 |
| 20080222684 | Mukraj et al. | Sep 2008 | A1 |
| 20080235746 | Peters et al. | Sep 2008 | A1 |
| 20080273591 | Brooks et al. | Nov 2008 | A1 |
| 20080279534 | Buttars | Nov 2008 | A1 |
| 20080281971 | Leppanen et al. | Nov 2008 | A1 |
| 20080282299 | Koat et al. | Nov 2008 | A1 |
| 20080297669 | Zalewski et al. | Dec 2008 | A1 |
| 20080306903 | Larson et al. | Dec 2008 | A1 |
| 20080320523 | Morris et al. | Dec 2008 | A1 |
| 20090013356 | Doerr et al. | Jan 2009 | A1 |
| 20090030802 | Plotnick et al. | Jan 2009 | A1 |
| 20090031335 | Hendricks et al. | Jan 2009 | A1 |
| 20090031384 | Brooks et al. | Jan 2009 | A1 |
| 20090064221 | Stevens | Mar 2009 | A1 |
| 20090083279 | Hasek | Mar 2009 | A1 |
| 20090083811 | Dolce et al. | Mar 2009 | A1 |
| 20090083813 | Dolce et al. | Mar 2009 | A1 |
| 20090086643 | Kotrla et al. | Apr 2009 | A1 |
| 20090086722 | Kaji | Apr 2009 | A1 |
| 20090089438 | Agarwal et al. | Apr 2009 | A1 |
| 20090098861 | Kalliola et al. | Apr 2009 | A1 |
| 20090100459 | Riedl et al. | Apr 2009 | A1 |
| 20090100493 | Jones et al. | Apr 2009 | A1 |
| 20090113472 | Sheth et al. | Apr 2009 | A1 |
| 20090133048 | Gibbs et al. | May 2009 | A1 |
| 20090133090 | Busse | May 2009 | A1 |
| 20090141696 | Chou et al. | Jun 2009 | A1 |
| 20090150400 | Abu-Hakima et al. | Jun 2009 | A1 |
| 20090150917 | Huffman et al. | Jun 2009 | A1 |
| 20090151006 | Saeki et al. | Jun 2009 | A1 |
| 20090158311 | Hon et al. | Jun 2009 | A1 |
| 20090172776 | Makagon et al. | Jul 2009 | A1 |
| 20090175218 | Song et al. | Jul 2009 | A1 |
| 20090177794 | Alexander et al. | Jul 2009 | A1 |
| 20090185576 | Kisel et al. | Jul 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090193486 | Patel et al. | Jul 2009 | A1 |
| 20090201917 | Maes et al. | Aug 2009 | A1 |
| 20090210899 | Lawrence-Apfelbaum et al. | Aug 2009 | A1 |
| 20090210912 | Cholas et al. | Aug 2009 | A1 |
| 20090225760 | Foti | Sep 2009 | A1 |
| 20090235308 | Ehlers et al. | Sep 2009 | A1 |
| 20090282241 | Prafullchandra et al. | Nov 2009 | A1 |
| 20090282449 | Lee | Nov 2009 | A1 |
| 20090293101 | Carter et al. | Nov 2009 | A1 |
| 20090296621 | Park et al. | Dec 2009 | A1 |
| 20090313116 | Ashbaugh | Dec 2009 | A1 |
| 20100012568 | Fujisawa et al. | Jan 2010 | A1 |
| 20100027560 | Yang et al. | Feb 2010 | A1 |
| 20100030578 | Siddique et al. | Feb 2010 | A1 |
| 20100031299 | Harrang et al. | Feb 2010 | A1 |
| 20100042478 | Reisman | Feb 2010 | A1 |
| 20100043030 | White | Feb 2010 | A1 |
| 20100083329 | Joyce et al. | Apr 2010 | A1 |
| 20100083362 | Francisco et al. | Apr 2010 | A1 |
| 20100106846 | Noldus et al. | Apr 2010 | A1 |
| 20100115091 | Park et al. | May 2010 | A1 |
| 20100115113 | Short et al. | May 2010 | A1 |
| 20100122274 | Gillies et al. | May 2010 | A1 |
| 20100122276 | Chen | May 2010 | A1 |
| 20100125658 | Strasters | May 2010 | A1 |
| 20100131973 | Dillon et al. | May 2010 | A1 |
| 20100138900 | Peterka et al. | Jun 2010 | A1 |
| 20100169977 | Dasher et al. | Jul 2010 | A1 |
| 20100199299 | Chang et al. | Aug 2010 | A1 |
| 20100199312 | Chang et al. | Aug 2010 | A1 |
| 20100217613 | Kelly | Aug 2010 | A1 |
| 20100218231 | Frink et al. | Aug 2010 | A1 |
| 20100219613 | Zaloom et al. | Sep 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100251305 | Kimble et al. | Sep 2010 | A1 |
| 20100269144 | Forsman et al. | Oct 2010 | A1 |
| 20100280641 | Harkness et al. | Nov 2010 | A1 |
| 20100287609 | Gonzalez et al. | Nov 2010 | A1 |
| 20100313225 | Cholas et al. | Dec 2010 | A1 |
| 20100325547 | Keng et al. | Dec 2010 | A1 |
| 20110015989 | Tidwell et al. | Jan 2011 | A1 |
| 20110016479 | Tidwell et al. | Jan 2011 | A1 |
| 20110016482 | Tidwell et al. | Jan 2011 | A1 |
| 20110071841 | Fomenko et al. | Mar 2011 | A1 |
| 20110090898 | Patel et al. | Apr 2011 | A1 |
| 20110093900 | Patel et al. | Apr 2011 | A1 |
| 20110099017 | Ure | Apr 2011 | A1 |
| 20110102600 | Todd | May 2011 | A1 |
| 20110103374 | Lajoie et al. | May 2011 | A1 |
| 20110107379 | Lajoie et al. | May 2011 | A1 |
| 20110110515 | Tidwell et al. | May 2011 | A1 |
| 20110119637 | Tuli et al. | May 2011 | A1 |
| 20110126018 | Narsinh et al. | May 2011 | A1 |
| 20110138064 | Rieger et al. | Jun 2011 | A1 |
| 20110145049 | Hertel et al. | Jun 2011 | A1 |
| 20110166932 | Smith et al. | Jul 2011 | A1 |
| 20110173053 | Aaltonen et al. | Jul 2011 | A1 |
| 20110173095 | Kassaei et al. | Jul 2011 | A1 |
| 20110178943 | Motahari et al. | Jul 2011 | A1 |
| 20110191801 | Vytheeswaran | Aug 2011 | A1 |
| 20110213688 | Santos et al. | Sep 2011 | A1 |
| 20110219229 | Cholas et al. | Sep 2011 | A1 |
| 20110265116 | Stern et al. | Oct 2011 | A1 |
| 20110276881 | Keng et al. | Nov 2011 | A1 |
| 20120005527 | Engel et al. | Jan 2012 | A1 |
| 20120011567 | Cronk et al. | Jan 2012 | A1 |
| 20120023535 | Brooks et al. | Jan 2012 | A1 |
| 20120030363 | Conrad | Feb 2012 | A1 |
| 20120124606 | Tidwell et al. | May 2012 | A1 |
| 20120144416 | Wetzer et al. | Jun 2012 | A1 |
| 20120185899 | Riedl et al. | Jul 2012 | A1 |
| 20130014140 | Ye et al. | Jan 2013 | A1 |
| 20130014171 | Sansom et al. | Jan 2013 | A1 |
| 20130024888 | Sivertsen | Jan 2013 | A1 |
| 20130046849 | Wolf et al. | Feb 2013 | A1 |
| 20130097647 | Brooks et al. | Apr 2013 | A1 |
| 20130117692 | Padmanabhan et al. | May 2013 | A1 |
| 20140051485 | Wang et al. | Feb 2014 | A1 |
| 20140074855 | Zhao et al. | Mar 2014 | A1 |
| 20140281904 | Burckart et al. | Sep 2014 | A1 |
| 20150006744 | Chatterjee et al. | Jan 2015 | A1 |
| 20150040176 | Hybertson et al. | Feb 2015 | A1 |
| 20150095932 | Ren | Apr 2015 | A1 |
| 20160134912 | Dillon et al. | May 2016 | A1 |
| 20160337464 | Eriksson et al. | Nov 2016 | A1 |
| 20170048336 | Novo et al. | Feb 2017 | A1 |
| 20180054774 | Cohn et al. | Feb 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 1821459 | Aug 2007 | EP |
| 2081361 | Jul 2009 | EP |
| 2001275090 | Oct 2001 | JP |
| 2005519365 | Jun 2005 | JP |
| 2005519501 | Jun 2005 | JP |
| 2005339093 | Dec 2005 | JP |
| 2008015936 | Jan 2008 | JP |
| 2009211632 | Sep 2009 | JP |
| 2010502109 | Jan 2010 | JP |
| 2010079902 | Apr 2010 | JP |
| 2012505436 | Mar 2012 | JP |
| 2012523614 | Oct 2012 | JP |
| WO-0110125 | Feb 2001 | WO |
| WO-2005015422 | Feb 2005 | WO |
| WO-2005031524 | Apr 2005 | WO |
| WO-2007060451 | May 2007 | WO |
| WO-2012021245 | Feb 2012 | WO |
| WO-2012114140 | Aug 2012 | WO |
| Entry |
|---|
| Alcatel: “Delivering True Triple Play-Common Capabilities for the Delivery of Composite Services”, Internet Citation, Jun. 2006 (Jun. 2006), XP002418653, Retrieved from the Internet: URL:http://www.alcatel-lucent.com/tripleplay [retrieved on Feb. 6, 2007] . |
| Florin L., et al., “Content Delivery and Management in Networked MPEG-4 System,” 2000 10th European Signal Processing Conference, IEEE, Sep. 4, 2000 (Sep. 4, 2000), pp. 1-4, XP032755920, ISBN: 978-952-15-0443-3 [retrieved on Mar. 31, 2015]. |
| Pantjiaros C.A. P., et al., “Broadband Service Delivery: CY.T.A. ADSL Field Trial Experience”, Electrotechnical Conference, 2000 MELECON, 2000 10th Mediterranean, May 29-31, 2000, Piscataway, NJ, USA,IEEE, vol. 1, May 29, 2000 (May 29, 2000), pp. 221-224, XP010518859, ISBN: 978-0-7803-6290-1. |
| Cantor, et al., Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0, OASIS Standard, Mar. 2005, Document ID saml-bindings-2.0-os ,(http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf). |
| DLNA (Digital Living Network Alliance) protocols described in DLNA Networked Device Interoperability Guidelines Expanded, Mar. 2006 and subsequent expanded version dated Oct. 2006. |
| OpenCable, Enhanced TV Binary Interchange, Format 1.0 OC-SP-ETV-BIF1.0-104-070921 Date: Sep. 21, 2007, 420 pages. |
| Redux screenshot from http://www.redux.com, “Select a channel to start watching” © 2014 Redux, Inc.014 Redux, Inc. All rights reserved; http://www.redux.com/; 2 pages. |
| Siebenlist F., et al., “Global Grid Forum Specification Roadmap towards a Secure OGSA,” Jul. 2002, pp. 1-22. |
| UTF-32, IBM, retrieved from http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2FnIs%2Frbagsutf32.htm on Aug. 28, 2013. |
| Number | Date | Country | |
|---|---|---|---|
| 20190200062 A1 | Jun 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61117265 | Nov 2008 | US | |
| 61117248 | Nov 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14861628 | Sep 2015 | US |
| Child | 16195408 | US | |
| Parent | 12834796 | Jul 2010 | US |
| Child | 14861628 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12536724 | Aug 2009 | US |
| Child | 12834796 | US |
