Patent Grant
11843641
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The disclosure relates generally to the field of networking and content delivery. In one exemplary aspect, the disclosure relates to the use of a network architecture for centralized message exchange via apparatus disposed on a user premises (e.g., residence, enterprise, etc.).
The provision of content to a plurality of subscribers in a network is well known. In a typical configuration, the content is distributed to the subscribers' devices over any number of different topologies including for example: (i) Hybrid Fiber Coaxial (HFC) network, which may include e.g., dense wave division multiplexed (DWDM) optical portions, coaxial cable portions, and other types of bearer media; (ii) satellite network (e.g., from an orbital entity to a user's STB via a satellite dish); (iii) optical fiber distribution networks such as e.g., “Fiber to the X” or FTTx (which may include for example FTTH, FTTC, FTTN, and FTTB variants thereof); (iv) Hybrid Fiber/copper or “HFCu” networks (e.g., a fiber-optic distribution network, with node or last-mile delivery being over installed POTS/PSTN phone wiring or CAT-5 cabling); (v) microwave/millimeter wave systems; etc.
Various types of content delivery mechanisms are utilized in providing content to subscribers. For example, certain content may be provided in accordance with “push” technology where a content server “pushes” unsolicited or asynchronous information out to specific client devices. Push services may be based on information preferences expressed in advance. In a publish-subscribe model, a client device “subscribes” to various information “channels” provided by the content server; whenever new content is available on one of those channels, the server pushes the information out to the client device. Examples of content delivery services that use push technology include instant messaging applications, video streaming services, Emergency Alert System (EAS), market data distribution services (e.g., stock tickers), sports results distribution services, home monitoring applications, and home device control applications.
A content server can push data to a client device over a full-duplex connection. For example, a web server can push information to a web server via a Transmission Control Protocol (TCP) connection. In U.S. cable systems, for instance, out-of-band (OOB) channels (and associated protocols) may be used to deliver asynchronous messages (e.g., global software updates, EAS notification, service entitlement distribution) to a subscriber device, as well as to provide communication between the headend of the content-distribution network and the subscriber device.
The content server communicates with each client device over a dedicated connection. In some cases (e.g., instant messaging sessions, video streaming sessions), the content server does not terminate the connection after the data has been transmitted to the client device. The content server leaves the connection open so that if an event occurs for reporting data to the client device, the content server can send the data to the client device immediately. In other cases, the connection is kept open through a series of periodic messages, termed “keep-alive” (KA) or “heartbeat” messages, that are sent from the client device to the content server to indicate that the client device is ready to receive data, and that the connection should be preserved. Because many centralized server systems are distributed computing structures fronted by e.g., a Global Server Load Balancer (GSLB) and a security firewall, a high cost is associated with maintaining hundreds of thousands or even millions of connections.
In scenarios where a one-time message is broadcast to multiple clients (e.g., in the aforementioned publish-subscribe model), a content server must send a message to each client device registered to receive the message from the content server. One example of a broadcast message is an EAS message. An EAS message may be targeted at a small geographic area (e.g., in the case of a storm), or to a large geographic area (e.g., in the case of a nuclear attack). The EAS server may provide the EAS notification to client devices via unicast mechanisms (i.e., each client device receives an individual copy of the message). As such, delivery of EAS messages to millions or hundreds of millions of client devices would be greatly bandwidth-inefficient and take considerable amounts of processing power. Further, typical content delivery networks may not have sufficient bandwidth capacity to support unicast delivery of EAS messages to a large number of client devices, whether due to “core” infrastructure, “edge” infrastructure, third-party infrastructure, or combinations of the foregoing. Although, some network topologies and architectures have a more efficient “multicast” capability which more effectively uses available bandwidth, most Internet Protocol (IP)-enabled client devices (and even some network infrastructure) do not support such multicast, and hence networks are relegated to use of the less efficient unicast or similar mechanism for delivery of broadcast messages.
The foregoing inefficiencies can be even more pronounced when multiple clients are each trying to communicate with entities or processes within the core portion of a network; e.g., the headend, or via “backbone” or other common core infrastructure.
In some home monitoring and home device control applications, each premises device is in communication with a centralized server—which is remote to the home. When a first premises device needs to be informed of a change of state of a second premises device, the second premises device communicates the state change to the centralized server, and the centralized server pushes a message to the first premises device notifying it of the state change of the second premises device. For example, when a remote control application with a graphic display needs to be informed of a change of state within a display device, the display device (or process relating thereto) would typically cause communication of the instruction to a remote central messaging server, which would then send a message using push technology to the remote control. As the messaging server may be thousands of miles from the home and encumbered by multiple network and switching delays, the delay between the changing of the display device and the notification on the remote control may cause the user to perform multiple button presses, and accordingly be annoyed by the lack of responsiveness of the system.
Hence, it would be desirable to provide mechanisms for exchanging messages between a content provider and a user premises device that more effectively uses communications bandwidth and processing power. It would also be desirable to provide mechanisms for exchanging messages within a user premises that provides less latency and more responsiveness than mechanisms that require repetitive transmissions to/from a central server.
The present disclosure addresses the foregoing needs by disclosing, inter alia, apparatus and methods for centralized message exchange via apparatus disposed on or “near” a user premises (e.g., residence, enterprise, etc.).
In a first aspect of the disclosure, a method of minimizing a number of network connections maintained by a premises gateway device is described. In one embodiment, the gateway device comprises a local message server process, and the method includes utilizing the message server to aggregate messages originated from higher layer processes within respective client devices served by the premises gateway into a single network or transport layer message for transmission to a remote network entity requiring that a network or transport layer connection be maintained.
In a second aspect of the disclosure, a premises gateway device for managing upstream communications between client devices of a premises network and a service provider is disclosed. In one embodiment, the premises gateway device includes: a first apparatus configured to receive first data from a first client device of the premises network; a second apparatus configured to receive second data from a second client device of the premises network; a third apparatus configured to communicate third data to a device of the service provider; and a processor apparatus in data communication with the first, second and third apparatus and configured to execute at least one computer program.
In one variant, the at least one program is configured to, when executed by the processor apparatus, cause the premises gateway device to: receive the first data from the first client device via the first apparatus; receive the second data from the second client device via the second apparatus; generate a single message based at least in part on the first data and the second data; and communicate the single message to the device of the service provider via the third apparatus.
In one implementation, each of the first data and the second data comprises an application layer keep-alive message for maintaining a respective streaming connection, and the single message comprises a transport or network layer keepalive message, and the generated single message further comprises information identifying the streaming connections associated with the first client device and the second client device.
In another implementation, each of the first data and the second data comprises a request to subscribe to publish-subscribe content provided by the service provider.
In another aspect of the disclosure, a premises gateway device for managing communications between a service provider and client devices of a premises network is described. In one embodiment, the premises gateway device includes: local area network interface apparatus configured to communicate data to at least a first client device and a second client device of the premises network; a network interface apparatus configured to receive data generated by a device of the service provider; a processor apparatus in data communication with the first, second and third apparatus; and a server process operative to execute on the processor apparatus.
In one variant, the server process is configured to, when executed by the processor apparatus, causes the premises gateway to: receive the data generated by the device of the service provider via the network interface apparatus; evaluate the received data; based at least in part on the evaluation, determine that the at least a portion of the received data is to be communicated to both the first client device and the second client device; generate a first message based at least in part on the at least portion of the received data; communicate the first message to the first client device via the first apparatus; generate a second message based at least in part on the at least portion of the received data; and communicate the second message to the second client device via the second apparatus.
In one implementation, the server process comprises a process utilizing at least and Extensible Messaging and Presence Protocol (XMPP) ad a Secure Websockets (WSS) protocol, and the received data comprises information identifying the first client device and the second client device.
In another implementation, the received data comprises an Emergency Alert Services (EAS) notification.
In a further implementation, the server process further comprises computerized logic configured to determine first and second acceptable formats associated with the first and second client devices, respectively, and the generation of the first and second messages comprises generation of the first message in the first format, and the second message in the second format.
In another aspect of the disclosure, apparatus for handling asynchronous messaging between devices connected with a content distribution network is disclosed. In one embodiment, the apparatus includes: a first interface for communication with at least one network device associated with the content distribution network; a second interface for communication with a first client device; a third interface for communication with a second client device; and a processor apparatus in data communication with each of the first, second and third interfaces and configured to execute at least one computer program.
In one variant, the at least one computer program is configured to, when executed by the processor apparatus, cause the apparatus to: manage, via the first interface, a first connection for communicating asynchronous messages associated with the first client device, the second client device, and both the first client device and the second client device to and from the at least one network device; manage, via the second interface, a second connection for communicating asynchronous messages to and from the first client device; manage, via the third interface, a third connection for communicating asynchronous messages to and from the second client device; communicate asynchronous messages associated with the first client device, the second client device, and both the first the first and second client devices to and from the at least one network device over the first connection; and communicate asynchronous messages exchanged between the first and second client devices over only the second connection and the third connection.
In one implementation, the first connection comprises a transmission control protocol (TCP) connection.
In yet a further aspect of the disclosure, anon-transitory computer readable apparatus is disclosed. In one embodiment, the apparatus includes a storage medium including at least one computer program implementing computerized logic, the computerized logic comprising a message server process configured to, when executed on a host platform within a premises network: aggregate two or more messages received by the host platform from different client devices within the premises network into a single consolidated message before transmission of the single consolidated message to a remote network server, the two or more messages associated with respective application layer processes of the different client devices, and the single consolidated message comprising a transport layer message configured to maintain an open socket or connection; dis-aggregate single messages received by the host platform and originated from the remote network server for distribution to at least the different client devices; and route messages originated from one of different client devices and addressed to another of the different client devices only locally so as to obviate sending the routed messages to the remote network server.
In still another aspect, a method of operating a premises network having a plurality of client devices associated therewith so as to reduce at least one of (i) network bandwidth consumption, and/or (ii) communications latency, is disclosed. In one embodiment, the method includes: receiving at least first and second messages from respective ones of first and second client devices, the first and second messages intended for a remote network server; aggregating the at least first and second message into a common message; transmitting the common message to the remote network server; receiving from the remote server a response to the common message; dis-aggregating the received response; and delivering at least portions of the received response to each of the first and second client devices.
In a further aspect of the disclosure, a premises gateway device architecture is disclosed. In one embodiment, the architecture comprises a local message server operable to interface with multiple heterogeneous client device environments or services via a Secure WebSockets process, using both publish-subscribe and RESTful communications interfaces.
These and other aspects shall become apparent when considered in light of the disclosure provided herein.
All Figures © Copyright 2016 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), gateways, modems, personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), tablets, “phablets”, 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 term “Customer Premises Equipment (CPE)” refers without limitation to any type of electronic equipment located within a customer's or user's premises and connected to or in communication with a network. The term “customer premises equipment” (CPE) includes such electronic equipment such as set-top boxes (e.g., DSTBs), televisions, cable modems (CMs), embedded multimedia terminal adapters (eMTAs), whether stand-alone or integrated with other devices, Digital Video Recorders (DVR), gateway storage devices (Furnace), and ITV Personal Computers.
As used herein, the term “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. DOCSIS 1.1 is interoperable with DOCSIS 1.0, and has data rate and latency guarantees (VoIP), as well as improved security compared to DOCSIS 1.0. DOCSIS 2.0 is interoperable with 1.0 and 1.1, yet provides a wider upstream band (6.4 MHz), as well as new modulation formats including TDMA and CDMA. It also provides symmetric services (30 Mbps upstream).
As used herein, the terms “keepalive”, “keep-alive” and similar may refer, without limitation, to communications (e.g., messages or signals), functions, or other approaches for indicating a status of one or more entities or processes, and may include for example TCP (OSI layer 4/5) keepalive messages, higher layer (e.g., OSI layer 7 or “application layer”) keep-alive functions, etc. as applicable to the prevailing context.
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 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 “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.11), 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/s/v/ac or 802.11-2012, as well as so-called “Wi-Fi Direct”, each of the foregoing incorporated herein by reference in its entirety.
As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth®, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, Zigbee®, RFID/NFC, narrowband/FDMA, OFDM, PCS/DCS, LTE/LTE-A, analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
Overview
The present disclosure provides, inter alia, methods and apparatus for providing a messaging server within a CPE; e.g., a home or residential gateway device, or at another network “edge” location in physical/logical proximity to the CPE. In one aspect, a system is described that includes a premises device that, inter alia, acts as a unified proxy or centralized client messaging platform providing messaging services between a content provider and client devices, and between client devices within a premises network. This premises device may be used, for example, in a home or residential environment, enterprise or corporate environment, military or government environment, or combinations of the foregoing. The premises device acts as a central messaging server for some or all devices in the premises via a cable or satellite modem or other such network interface, communicating and exchanging messages with and between devices throughout the premises, and providing a wired and wireless network in the home.
In one embodiment, the client devices associated with the premises (which may or may not be physically located at the premises at any given time) register with the premises device using their private network addresses e.g., RFC-1918 IPv4 or link-local IPv6 addresses. These private network addresses are commonly used for devices within home, office, and enterprise local area networks (LANs). When a client device needs to send a message to another client device within the premises network (again, which may or may not be physically located therein), the premises device will enable the message to bypass the long trip and propagation delay over the Internet or other interconnection medium (aka a long “hairpin”), and “connect” the message directly to the other client device across the premises network; e.g., within the home or building or other physically/logically proximate location within the premises network.
In one variant, the premises device is an Extensible Messaging and Presence Protocol (XMPP) and Secure Websockets (WSS) protocol-enabled gateway that is allocated a publicly routable IP address, and includes a network address translator (NAT) function to provide Internet connectivity to the client devices. The messaging server within the premises device enables messages to be communicated between a content provider outside the premises network and the client devices via a single connection e.g., a single Internet connection. At the request of client devices, the premises device registers with content providers for specific publish-subscribe broadcast messages, and performs the distribution of the messages to the client devices. For any Internet connections that need to be preserved for receiving content (e.g., TCP/IP socket or similar), the premises device sends a single keepalive message to a content provider, and handles the keep-alive messaging from the local devices (e.g., at the application layer) within the premises network.
Advantageously, the foregoing use of the messaging server within the premises device minimizes the number of Internet connections that need to be opened and the number of messages communicated with servers outside of the premises network which, inter alia, saves network bandwidth and computation time.
In another variant, aggregation of communications is used with respect to multiple client devices within the premises network utilizing a common Internet or other connection, such that if any of the clients are utilizing the connection, the connection is kept alive via a single “coincidence” message versus individual messages for each of the clients.
In yet a further variant, aggregation of communications is accomplished at one or more network “edge” nodes with respect to multiple premises networks. Hence, the edge node virtualizes or aggregates the various premises (which each in turn may aggregate their respective associated client devices, or alternatively operate without such aggregation).
The various aspects of the present disclosure may have utility in any number of different applications, including (without limitation), within home or premises gateways, set-top boxes, smart TVs, remote controls, and/or mobile device applications running via a network connection within the home that contains software products such as e.g., video applications, home monitoring applications, and home device control (e.g., “Internet of Things” or IOT).
Exemplary embodiments of the apparatus and methods are now described in detail. While these exemplary embodiments are described in the context of the aforementioned hybrid fiber coax (HFC) cable system architecture having an multiple systems operator (MSO), digital networking capability, IP delivery capability, and plurality of client devices/CPE, the general principles and advantages of the present disclosure may be extended to other types of networks and architectures, whether broadband, narrowband, wired or wireless, managed or unmanaged, or otherwise, the following therefore being merely exemplary in nature.
It will also be appreciated that while described generally in the context of a consumer (e.g., home) end user domain, the present disclosure 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, it will be appreciated that the present disclosure may utilize other types of protocols (and in fact bearer networks to include other internets and intranets) to implement the described functionality.
Other features and advantages of the present disclosure 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.
Content Distribution Network—
The exemplary architecture 150 of
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, 2.0, 3.0 (and subsequent) specification provides for exemplary networking protocols both downstream and upstream, although the present disclosure is in no way limited to these approaches.
In addition to “broadcast” content (e.g., video programming), the systems of
Referring again to
The edge switch 194 forwards the packets receive from the CMTS 199 to the QAM modulator 189, which transmits the packets on one or more physical (QAM-modulated RF) channels to the CPE. The IP packets are typically transmitted on RF channels (e.g., DOCSIS QAMs) that are different that the RF channels used for the broadcast video and audio programming, although this is not a requirement. The CPE 106 are each configured to monitor the particular assigned RF channel (such as via a port or socket ID/address, or other such mechanism) for IP packets intended for the subscriber premises/address that they serve.
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 disclosure, a “packet optimized” delivery network is used for carriage of the packet content (e.g., IPTV content).
Referring now to
The network 1000 generally comprises a local headend 1001 in communication with at least one hub 1003 via an optical ring 1007. The distribution hub 1003 is able to provide content to one or more premises networks 1009 each having e.g., various user devices, CPE 1022, and gateway devices 1020, via a network 1005.
Various content sources 1002 are used to provide content to a content server 1004. For example, content may be received from a local, regional, or network content library. Alternatively, content may be received from linear analog or digital feeds, as well as third party content sources. Internet content sources 1010 (such as e.g., a web server) provide internet content to a packetized content server 1006. Other IP content may also be received at the packetized content server 1006, such as voice over IP (VoIP) and/or IPTV content. Content may also be received from subscriber and non-subscriber devices (e.g., a PC or smartphone-originated user made video). In one embodiment, the functionality of both the content server 1004 and packetized content server 1006 may be integrated into a single server entity.
A central media server located in the headend 1001 may be used as an installed backup to the hub media servers as (i) the primary source for lower demand services, and (ii) as the source of the real time, centrally encoded programs with PVR (personal video recorder) capabilities. By distributing the servers to the hub stations 1003 as shown in
Individual CPEs 1022 of the implementation of
In the switched digital variant, the IP packets associated with Internet services are received by edge switch, and forwarded to the cable modem termination system (CMTS) 1016. The CMTS examines the packets, and forwards packets intended for the local network to the edge switch. Other packets are in one variant discarded or routed to another component.
The edge switch forwards the packets receive from the CMTS to the QAM modulator, which transmits the packets on one or more physical (QAM-modulated RF) channels to the CPE. The IP packets are typically transmitted on RF channels that are different than the RF channels used for the broadcast video and audio programming, although this is not a requirement. As noted above, the CPE 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.
In one embodiment, both IP data content and IP-packetized audio/video content is delivered to a user via one or more universal edge QAM devices 1018. According to this embodiment, all of the content is delivered on DOCSIS channels, which are received by a premises gateway 1020 (described subsequently herein) and distributed to one or more CPE 1022 in communication therewith. Alternatively, the CPE 1022 may be configured to receive IP content directly without need of the gateway or other intermediary. As a complementary or back-up mechanism, audio/video content may also be provided in downstream (in-band) channels as discussed above; i.e., via traditional “video” in-band QAMs. In this fashion, a co-enabled digital set top box (DSTB) or other CPE could readily tune to the new (in-band) RF video QAM in the event that their IP session over the DOCSIS QAM is for some reason interrupted. This may even be accomplished via appropriate logic within the CPE (e.g., autonomously, or based on signaling received from the headend or other upstream entity, or even at direction of a user in the premises; e.g., by selecting an appropriate DSTB or other CPE function).
In the embodiment illustrated in
In another variant, IP simulcast content and existing on-demand, voice, and broadcast content are all provided to the headend switch device 1008 of
The IP-packet content is transmitted to subscriber devices via the universal edge QAM 1018 and the edge network 1005. The IP video (“simulcast”) content is presented to client devices capable of receiving content over the DOCSIS QAMs. For example, the aforementioned gateway device 1020 (as well as an advanced CPE 1022 such as an IP-enabled DSTB may receive the IP simulcast. Legacy CPE may receive content via the gateway device 1020, or via an audio/video “back-up” MPEG transport stream as previously described.
In the illustrated embodiment, the gateway device 1020 serves as a gateway to the IP content for other client devices (such as other CPE 1022 and PMD). The gateway device 1020 may communicate with one or more connected CPE 1022, as well as utilize Wi-Fi capabilities (where so equipped) to communicate wirelessly to other devices. It will also be recognized that the present disclosure may be configured with one or more short-range wireless links such as Bluetooth for lower bandwidth applications (or UWB/PAN for greater bandwidth applications).
Premises Network—
The CMTS 199 is in the illustrated embodiment coupled to multiple households or other premises, including the exemplary illustrated household 140. In particular, the CMTS 199 is coupled via the aforementioned HFC network and local coaxial cable or fiber drop to the premises 140, including the consumer premises equipment (CPE) 106 which may be e.g., a premises gateway. The exemplary CPE 106 is in signal communication with any number of different devices including, e.g., a wired telephony unit 222, a Wi-Fi or other wireless-enabled phone 224, a Wi-Fi or other wireless-enabled laptop 226, a SIP phone, an H.323 terminal or gateway, etc. Additionally, the CPE 106 is also coupled to a digital video recorder (DVR) 228 and diplexer 230 via a coax cable. A network-to-coax bridge 231 places the coax environment in communication with a network (here, an Ethernet network complaint with IEEE Std. 802.3, although any number of other network protocols and topologies could be used) and a personal computer (PC) 232. The DVR 228 is also connected to a television or other monitor 234, which may be in communication via a wired or wireless interface (e.g., cabling, PAN or 802.15 UWB micro-net, etc.).
A premises LAN (PLAN) is created in the exemplary embodiment, which may include for example the network formed over the installed coaxial cabling in the premises (e.g., Ethernet with CAT-5/6 cabling or MoCA-based system), the Wi-Fi (WLAN) network, and so forth.
As a brief aside, current “gateway” devices used in content distribution networks such as cable television networks often consist of a network interface; e.g., cable modem, Small Form-factor Pluggable (SFP) or other transceiver, disposed within an host such as an IP network switch, or a combination of the interface, an internal network router (a.k.a. “gateway”), a Dynamic Host Configuration Protocol (DHCP) server, and a Wi-Fi or similar LAN interface. In the exemplary context of cable television networks, a narrow bandwidth broadcast signal has historically been used to send asynchronous messages to television set-top boxes (STBs) in order to perform such exercises as Emergency Alert System (EAS) notification, global software update, or service entitlement distribution. Such functions generally cannot be performed on the public (unmanaged) Internet, as the broadcast mechanism defined for IP utilizes User Datagram Protocol (UDP) messages on specific IP addresses that would tend to flood the bearer network. Additionally, networks within the subscriber's premises (and behind a premises router) will utilize a predetermined IP address range (e.g., one set forth in Internet Engineering Task Force (IETF) Request For Comments (RFC) 1918); such IP addresses are deemed non-routable on the public IP network, in that the network beyond the IP router does not permit the use of such RFC-1918 or IPV6 equivalent (link-local) non-routable addresses.
In contrast, the exemplary CPE 106 of the present disclosure (e.g., premises gateway) advantageously contains one or more messaging server processes therein; when the messaging server is contained within the premises network, the in-premises devices will register with that server (e.g., using their RFC-1918 IPV4 or link-local IPV6 address), and the premises server will then bypass the long trip over the Internet or other network infrastructure, and connect the messages across the premises “intranet” instead. This obviates potentially numerous “outbound” and “inbound” messages to/from distant servers (e.g., at the network core or elsewhere), and further greatly reduces latency, thereby improving responsiveness of various processes and functions, and increasing user/subscriber satisfaction.
Returning again to the exemplary CPE of
Any number of different data flows may occur within the premises network. For example, the CPE 106 may exchange digital telephone signals from the CMTS 199 which are further exchanged with the telephone unit 222 or the Wi-Fi phone 224. The digital telephone signals may be IP-based such as Voice-over-IP (VoIP), or may utilize another protocol or transport mechanism. The well-known session initiation protocol (SIP) may be used, for example, in the context of a “SIP phone” for making multi-media calls. The premises network may also interface with a cellular or other wireless system, such as for example a 3G/4G IMS (IP multimedia subsystem) system, in order to provide multimedia calls between a user or consumer in the household domain 140 (e.g., using a SIP phone or H.323 terminal) and a mobile 3G/4G telephone or personal media device (PMD) user via that user's radio access network (RAN). See, e.g., co-owned and co-pending U.S. patent application Ser. No. 11/258,229 entitled “Method And Apparatus For On-Demand Content Transmission And Control Over Networks” filed Oct. 24, 2005, incorporated herein by reference in its entirety, wherein media can be streamed between a mobile unit and the CPE 106, including optionally in an on-demand or session-based fashion.
The CPE 106 may also exchange Internet traffic (e.g., TCP/IP and other packets) with the CMTS 199 which is further exchanged with the Wi-Fi-enabled laptop 226, the PC 232, or other device by way of a diplexer 230 and the exemplary coax bridge 231. CPE 106 may also receive digital programming that is forwarded to the DVR 228 or to the television 234. Programming requests and other control information may be received by the CPE 106 and forwarded to the CMTS 199 as well. The CMTS 199 routes the information to the corresponding subsystem within the headend 150 or to other systems located upstream from the CPE 106.
In the exemplary embodiment, a message server or comparable device is used as part of or is in communication with the CPE 106 (or an associated client device coupled thereto). In one embodiment, the message server comprises a software process running on the host CPE hardware environment, although it will be appreciated that other implementations (including discrete server hardware/software environments such as server blades or cards) may be used consistent with the present disclosure.
The exemplary CPE message server is capable communicating asynchronous messages with the CMTS 199 and the client devices of the premises network in a bandwidth-efficient manner without unnecessary delay. In one implementation, the client devices register with the message server using their private network addresses e.g., RFC-1918 IPv4 or link-local IPv6 addresses. When a client device e.g., Wi-Fi-enabled laptop 226, needs to send a message to another client device e.g., DVR 228, within the premises, the message server recognizes that the message is addressed to the DVR 228 and connects the message directly to the DVR 228 via the home network 104 without utilizing the CMTS 199 and associated headend network 150.
Additionally, the CPE 106 of the exemplary embodiment is allocated a publicly routable IP address, and includes a network address translator (NAT) process to provide Internet connectivity to the client devices via the CPE 106. The CPE's embedded or associated message server enables messages to be communicated between a content or service provider and the client devices via a single connection e.g., a single Internet connection, between the CPE 106 and the CMTS 199. The messages may include programming requests, control information, instant messages, “pub/sub” (publish/subscribe) content, EAS notifications, keepalive signals, etc. For example, at the request of client devices, the message server registers with content providers for specific broadcast messages (e.g., publish-subscribe broadcast messages) using the publicly routable IP address of the CPE 106 and performs the distribution of the messages to the client devices using their private network addresses.
For any Internet connections that need to be preserved for e.g., receiving content, the message server in one embodiment is configured to send a single keepalive or heartbeat message to a content provider via the CMTS 199, and also handles the keep-alive messaging from the local devices within the premises network (e.g., those issued by application layer processes). Such handling of the indigenous keep-alive messaging includes in one exemplary implementation a “coincidence” type logic for each individual network content provider or target. Specifically, the message server process of the CPE is configured to receive any such keep-alive messages from any client device (or associated process running thereon, such as a messaging stream as part of an application program running on the client), and to the degree that a given network target or connection is required by any of the communicating clients/client processes, a single network or transport-layer keepalive message is generated by the CPE message server and transmitted upstream to e.g., a corresponding application server.
As previously referenced, the message server functionality can be a software process operative to run on the host CPE environment, made part of a separate physical (yet integrated component such as a sever card or blade), or alternatively have some or all of its functionality disposed within other devices in data communication with the CPE (e.g., another computerized device on the premises LAN). It may also be integrated with other devices (such as connected client devices or PMDs) as previously noted.
To enable this functionality, the message server may include or have access to a client device registry or other type of registry; see e.g., co-owned U.S. Pat. No. 8,302,111 entitled “METHODS AND APPARATUS FOR HARDWARE REGISTRATION IN A NETWORK DEVICE”, and U.S. Pat. No. 9,083,513 entitled “TECHNIQUE FOR SECURELY COMMUNICATING AND STORING PROGRAMMING MATERIAL IN A TRUSTED DOMAIN”, each incorporated herein by reference in their entirety, for exemplary types of registry configurations that may be used consistent with the present disclosure. The client device registry in the exemplary embodiment contains records that correspond to the client devices within the premises network. Each record (or set of records) may contain fields that: (i) identify the client device (e.g., the private network address of the device), (ii) identify content or service providers with which the client device is registered to receive messages, (iii) identify content or service providers with which the client device needs to preserve an open connection, and/or (iv) identify information channels that the client devices are subscribed to receive information.
The CPE's indigenous message server uses the information in the registry to route messages received from outside and within the premises network. For example, when a message, content, or information arrives at the message server from outside the premises network, the message server accesses the registry to identify the client device(s) to which the message, content, or information should be forwarded. In cases where the message is destined for the message server (as opposed to a particular client device, such as where the server issued a keepalive message on behalf of several clients within the premises network), various approaches may be implemented, including e.g., maintaining an association table (AT) or other data structure within the CPE message server that associates connections/processes with one or more client devices, such that when a connection-related message is received and is addressed merely to the CPE message server, the AT can be consulted to forward the received message (if necessary) to the appropriate client devices/processes associated with the connection.
When the message server receives a keep-alive message from a client device, the message server uses the registry to determine which content or service provider should be notified at the predetermined interval (or occurrence of other triggering event, such as a change in status in the CPE 106 local hardware registry indicating e.g., inactivity) to preserve or terminate the connection between the content or service provider and the CPE 106, for the client device to receive (or discontinue receiving) data.
In another embodiment, an entity or process of the headend network 150 (e.g., a remote messaging server), the CPE 106, and the client devices may be configured to communicate messages using a predefined message format which includes “routing” information. The message format may contain, inter alia, information that identifies: (i) one or more source entities of the message and/or (ii) one or more destination entities of the message. The CPE message server and the headend network entity uses the information contained in the message to route the messages to the appropriate destination entities, and to send response messages to the appropriate source entities. For example, when a message arrives at the message server from outside the premises network (e.g., via the aforementioned DOCSIS modem connection to the CMTS), the CPE message server reads the information in the message identifying the destination entities, and forwards the message to the specified client devices.
As another example, when the message server receives a keep-alive message from a client device within the premises network, the CPE message server reads the information in the message identifying the destination entity and notifies the specified content/service provider at the predetermined interval to preserve a connection (which may be a connection separate from the keepalive message e.g., a unicast video stream) between the content/service provider and the CPE 106 for the client device to receive data. The content/service provider may read the information in the message identifying the source entity to determine which connection needs to be preserved.
As yet another example, when the message server receives a message from one client device with the destination entity field identifying another client device, the message server forwards the message directly to the other client device via the premises network.
It will also be recognized that aspects of the present disclosure may be used in conjunction with a number of different capabilities and features useful with traditional (prior art) CPE. For example, the error logging and reporting methods and apparatus described in co-owned and co-owned U.S. patent application Ser. No. 10/722,206 entitled “METHODS AND APPARATUS FOR EVENT LOGGING IN AN INFORMATION NETWORK” FILED Nov. 24, 2003, and issued as U.S. Pat. No. 7,266,726 on Sep. 4, 2007, which is incorporated herein by reference in its entirety. For example, the aforementioned disclosure describes methods and apparatus (including APIs) for logging errors that occur on client devices or CPE 106. In the present context, these errors can then be transmitted upstream to a responsible entity (e.g., management node, conditional access server, etc.) for further analysis or correction in accordance with the techniques described herein. Such logging events may also be aggregated by the CPE message server as appropriate; e.g., collected over a prescribed period of time for one or more client devices within the premises network and sent via a single communication to one or more responsible network or other entities.
In another aspect, the CPE 106 of the present disclosure may also be made compatible with the methods and apparatus disclosed in co-owned U.S. patent application Ser. No. 11/363,578 filed Feb. 27, 2006 entitled “METHODS AND APPARATUS FOR SELECTING DIGITAL ACCESS TECHNOLOGY FOR PROGRAMMING AND DATA DELIVERY” and issued as U.S. Pat. No. 8,170,065 on May 1, 2012, which is incorporated herein by reference in its entirety. Specifically, electronic devices such as set-top boxes, PMDs, or other types of equipment containing one or more hardware and software functions or modules are in data communication with the CPE message server; the hardware and software functions/modules of the different devices on the network contain various capabilities and options, including conditional access capabilities, video coding or compression capabilities, encryption schema, and network interfaces. These capabilities are utilized as a basis for determining which conditional access, coding, encryption, and/or network interfaces to utilize for delivery of content to each particular client device, such capabilities being maintained in a CPE client device “capabilities” registry or other data structure. The CPE message server or other component of the CPE can accordingly be equipped with such capability if desired in order to, inter alia, profile the CPE clients for tailoring content or other functions to that specific end-user environment. For example, if a connected client devices of the CPE (e.g., legacy DSTB, PC or the like) has only an MPEG-2 decoder, only MPEG-2 encoded content would be sent to that client device based on the registry maintained by the CPE, or alternatively the CPE or client devices would obtain the necessary codec (e.g., MPEG-4 or Real) from another source, such as an MSO or third party website. Hence, the CPE master device capabilities registry can be used for communicating messages to relevant network entities as a proxy for the affected client(s).
Exemplary CPE—
In one embodiment, the message server 303 provides an OSI layer 7 (application layer) message protocol for communications between clients connected via an OSI layer 2 or 3 switch 305 and external application servers (e.g., e.g., server 104 of
The message server 303 of the exemplary embodiment also provides a mechanism for clients to register for specific types of messages. This “publication-subscription pattern” allows, inter alia, clients to subscribe to messages relevant to them; e.g., a display client registering for video program time updates, such as when sports broadcasts run into overtime and multi-zone building temperature controls registering for temperature control messages via the Internet. Similarly, in another example, a set-top box, smart TV or other device may register for remote-control messages (e.g., a remote used in conjunction with the set-top or a rendering device such as the smart TV). A remote-control could then send a message (“publish”) to the Message Server 303, and it would then forward the message to the registered set-top boxes. As another example, a building with intelligent multi-zone temperature control valves could have the control valves register to receive messages from a central thermostat control that would send messages (such as for example, that it is presently a given time of day such as morning or evening, and the valves should adjust the temperature in all areas in preparation for people entering or departing the building). Numerous other applications will be recognized by those of ordinary skill given the present disclosure.
A network router 313 is also included within the exemplary CPE 106 and in communication with the bus 312 and the network interface (e.g., DOCSIS modem) 320 so as to enable, inter alia, local routing of OSI layer 3 traffic within the premises LAN to the external WAN as a network gateway as well as providing Network Address Translation (NAT) to incoming/outgoing traffic OSI layer 3 traffic. Hence, in the exemplary embodiment, the router still behaves as a destination for IP addresses not found within the network. In one variant, the Ethernet interface 324 comprises an Ethernet switch with multiple clients attached, including the Wi-Fi AP/interface 322. The exemplary switch allows OSI layer 3 (MAC address) routing between devices connected to the switch via e.g., the Ethernet interface 324 and the Wi-Fi interface 322. The CPE 106 also optionally may include a network processing unit (e.g., network processor, not shown) to process the premises or home network (e.g., PLAN) services. The network processor also provides in one embodiment the ability to download firmware updates via TFTP or another selected protocol as desired.
The illustrated CPE 106 can assume literally any discrete form factor, including those adapted for desktop, floor-standing, 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.
It will be recognized that while a linear or centralized bus architecture is shown as the basis of the exemplary embodiment of
Furthermore, many if not all of the foregoing functions may be integrated into one or more integrated circuit (IC) devices in the form of an ASIC or “system-on-a-chip” (SoC). Myriad other architectures well known to those in the data processing and computer arts may accordingly be employed.
It will also be recognized that the CPE configuration shown is essentially for illustrative purposes, and various other configurations of the CPE 106 are consistent with other embodiments of the invention. For example, the CPE 106 in
Standard 10/100/1000 Base T Ethernet ports for the purpose of a Home LAN connection are provided; however, it will be recognized that other rates (e.g., 10-Gig-E) and local networking protocols (e.g., X.25, etc.) may be used. These interfaces may be serviced via a WLAN interface, wired RJ-45 ports, or otherwise. The CPE 106 also includes a plurality of RJ-11 ports for telephony interface, as well as a plurality of USB (e.g., USB 2.0/3.0) ports, and IEEE-1394 ports. S-video and other signal interfaces may also be provided if desired.
The CPE 106 mass storage device 328 of the illustrated embodiment comprises a Serial-ATA (SATA) or other hard disk drive solid state storage device (SSD) for the operating system and content storage, although other configurations RAID arrays may be used for this purpose. The CPE 106 hard disk is preferably removable without the need for tools, and the CPE 106 is also configured to allow for an external USB (e.g., USB 2.0/3.0) drive to be attached and automatically added to the existing storage. It will also be appreciated that USB keys of the type well known in the art can be used consistent with the USB port(s) of the CPE 106, so as to make the data storage device highly mobile and of very small size.
The RF front end 301 of the exemplary embodiment comprises a cable modem (CM) of the type known in the art. In this fashion, content or data normally streamed over the CM can be received and distributed by the CPE 106, such as for example packetized video (e.g., IPTV). The digital data exchanged using RF front end 301 includes IP or other packetized protocol traffic that provides access to interne service. As is well known in cable modem technology, such data may be streamed over one or more dedicated QAMs resident on the HFC bearer medium, or even multiplexed or otherwise combined with QAMs allocated for content delivery, etc. The packetized (e.g., IP) traffic received by the CPE 106 may then be exchanged with other digital systems in the local environment (or outside this environment by way of a gateway or portal) via, e.g. the Wi-Fi interface 322, Ethernet interface 324 or PnP interface 318.
It will be appreciated, however, that the RF front end 301 of the CPE 106 may comprise (either in addition to or in place of the CM) a traditional video RF front end 320 (e.g., tuner) adapted to receive video signals over, e.g., a QAM. For example, one exemplary embodiment of the RF front end 320 comprises one or more tuners, a demodulator, decryption module, and demultiplexer of the type well known in the art, although other configurations may be used. Additionally, the RF front end 320 modulates, encrypts/multiplexes as required, and transmits digital information for receipt by upstream entities such as the CMTS or a network server. Digital data transmitted via the RF front end 320 may include for example MPEG-2 encoded programming data that is forwarded to a television monitor via the video interface 316. Programming data may also be stored on the CPE storage unit 328 for later distribution or output by way of the video interface 316, or using the Wi-Fi interface 322, HDMI, DVI-D, Ethernet interface 324, IEEE Std. 1394, USB/USB2/USB3.0, or any number of other such options.
Programming and other types of data including messages, pictures, video, music or MP3 files, software applications, metadata files, etc. may also be received by way of the various digital interfaces in the CPE 106. These data may be stored locally (e.g., in the CPE storage unit 308) and/or forwarded to a client device or network agent in communication with the CPE 106.
In accordance with the exemplary embodiment of the invention, the CPE 106 includes a DOCSIS cable modem for delivery of traditional broadband Internet services. This connection is preferably shared by all Internet devices in the premises; e.g. IPTV devices, PCs, laptops, tablets, smartphones, etc. In addition, the CPE 106 can be remotely managed (such as from the head end 150, or another remote network agent) to support IP services such as DHCP, DNS, NAT and firewall capabilities as well as anti-virus, pop-up blocking, and spyware protection.
The CPE 106 may also create a home Local Area Network (LAN) utilizing the existing coaxial cable in the home. For example, an Ethernet-over-coax based technology allows services to be delivered to other devices in the home utilizing a frequency outside (e.g., above) the traditional cable service delivery frequencies. For example, one embodiment uses frequencies on the order of 1150 MHz to deliver data and applications to other devices in the home such as PCs, PMDs, media extenders and set-top boxes. The coaxial network is merely the bearer; devices on the network utilize Ethernet or other comparable networking protocols over this bearer.
The exemplary CPE 106 shown in
An optional DHCP server running on the CPE 106 manages IP address generation and dissemination on the coax, Wi-Fi, and other local networks in communication with the CPE 106. The cable modem (e.g., DOCSIS) interface of the exemplary embodiment is set to DHCP, and obtains an IP address from the CMTS DHCP server on the appropriate DOCSIS channel.
Internet and Wi-Fi phone traffic is preferably routed from both the coax and Wi-Fi interfaces to the cable modem interface. The CPE 106 also includes the means (e.g., a software module) for doing network address translation (NAT) of the Wi-Fi and coax interfaces, although it will be appreciated that other approaches to address management may be used as well.
During operation of the CPE 106, software located in the storage unit 328 is run on the microprocessor 336 using the memory unit 330 (e.g., a program memory within or external to the microprocessor). The software controls the operation of the other components of the system, and provides various other functions within the CPE. Other system software/firmware may also be externally reprogrammed, such as using a download and reprogramming of the contents of the memory, replacement of files on the storage device or within other non-volatile storage, etc. This allows for remote reprogramming or reconfiguration of the CPE 106 by the MSO or other network agent.
In one embodiment, the microprocessor 326 executes a messaging application or software suite to configure the CPE 106 to act as a message server for the premises network. As previously discussed, the message server allows, inter alia, for a content/service provider to communicate with client devices via the CPE 106 using a single connection. The message server maintains a single connection to the content/service provider for communications between the content/service provider and all client devices in the premises network. The foregoing approach is particularly useful in the content of IP or similar “multicast” or broadcast messages (e.g., pub/sub content or EAS notification) that are targeted for multiple client devices. Under the prior art, multicasting or broadcasting of such messages would consume significant amounts of bandwidth on the downstream channels, since the message was essentially replicated for each different client device and sent unicast from the content/service provider to each different client device. In contrast, the improvements provided by the present invention allows a content/service provider to deliver messages to multiple client devices connected to the CPE 106 by sending a single message to the CPE 106 which then replicates and multicasts or broadcasts the message to the client devices, thereby allowing for a 1:N communication of the message with minimal if any replication at the headend.
Similar, the CPE 106 allows for N:1 communication of messages between client devices and a content/service provider. For example, the message server can combine messages (e.g., keep-alive messages and subscription messages) received from client devices targeted for a content/service provider into a single message communicated to the content/service provider. Under the prior art, each different client device would send its own message to the content/service provider, resulting in unnecessary consumption of bandwidth on upstream channels.
It will also be appreciated that the inventive message server of the CPE can be configured for N:N communication if desired. For instance, consider the case where a plurality of client devices within a given premises network are connected to a corresponding number of different content sources/processes through the CPE 106. Keep-alive messages may be required for each of these different services. Rather than send individual messages originated from each client to each of the respective processes, the CPE message server may be configured to aggregate the keep-alive messages issued by each individual client process, and send a single multicast message to each of the target content sources or processes, which in certain case may have economies of scale over sending a plurality of unicast messages individually, as in the prior art. For instance, the message server may schedule the common multicast at a time when upstream network bandwidth is not (or is less) constrained. In another approach, the message server may be configured to send a single message to a node further upstream within the network (e.g., closer to the core), such node from which a subsequent multicast to each of the content sources is generated. The message may include as part of its payload or other structure information on each of the destinations. In this fashion, the individual messages of the multicast are carried for a shorter “distance” within the network topology, thereby ostensibly reducing network congestion. By analogy, a car carrier which travels to a given city and then unloads each of its cars for delivery in that city may have economies as compared to having individuals drive each car from an origin to the city separately. This approach is useful where a common message type/content is used for each of the constituent clients (e.g., where all are attempting to transmit the same “keepalive” message upstream, such as to keep a connection open). In one variant, the methods and apparatus described in U.S. Pat. No. 8,681,645 entitled “System and method for coordinated discovery of the status of network routes by hosts in a network” issued Mar. 25, 2014 and incorporated herein by reference in its entirety, may be used consistent with the present disclosure to provide the aforementioned functionality (e.g., so-called “cluster groups” with one or more master nodes can be utilized for, inter alia, aggregation or inter-device messaging and status).
The message server also allows for bidirectional device to device communication within the premises network. When a client device requests to communicate with another premises device via the premises network, the message server may present to a user of the client device a list of currently registered premises devices with which the client device can communicate. The user of the client device may select the device from the list, and the message server directly communicates messages from the client device to the selected device. In some embodiments, the client device and selected device may be paired (e.g., in the case of a client running a remote control application communicating with a DVR) for ongoing bidirectional communication. By including the message server in the CPE 106, the transport distance for messages, particularly IP messages, between the client devices is minimized and thus the propagation delay is minimized.
The message server may use an appropriate protocol for communicating messages. For example, in one exemplary embodiment, the message server uses the Extensible Messaging and Presence Protocol (XMPP) on top of the Secure Websockets (WSS) protocol. Each client device may be initialized and authenticated for messaging using a token issued by the message server or headend network and other credentials (e.g., device identifier). Each client device is assigned a private network address as an addressable end point in the premises network.
The message server may store a client device registry in the storage 308, as previously discussed. The client device registry contains records that correspond to the client devices within the premises network as described above. In some embodiments, when the message server receives a message, the message server accesses the storage 308 to retrieve the client device registry and uses the information in the registry to route the message.
Exemplary Methodology—
Referring now to
At step 402, the CPE receives a message from a client device. The message may contain e.g., a programming request, control information, a subscription request, and/or a keep-alive notification. The message may contain an identifier of the content/service provider to which the message is targeted (e.g., a URL or other network address).
Based on the information contained in the message, the CPE may update record(s) in the client device registry (step 404). For example, if the message contains a subscription request, the CPE updates a record associated with the client device to indicate that the client device has subscribed to content from the content provider. The record can be updated with subscription information identifying the content provider, specific channels of content, and/or the attributes/category of the content. When the CPE receives a message from the content provider that satisfies the subscription information in the record, the CPE forwards the message to the client device. The CPE thus in one aspect acts as a message filter for publish-subscribe messages directed to the client devices.
At step 406, the message server process of the CPE generates the message to be sent to a network entity (e.g., to the headend network of the content distribution network previously described with respect to
At step 408, the CPE sends the generated message to the recipient; e.g., via the headend of the network. The CPE may send the message over an in-band or OOB channel, such as via a TCP (transport control protocol) connection depending on the interfaces and protocols of the destination device.
In some implementations, the CPE may combine information from messages received from multiple client devices as previously discussed. For example, the CPE may receive keep-alive messages from multiple client devices before the predetermined time period for sending a keep-alive message to the content/service provider has expired (e.g., before expiration of the earliest or most stringent time period has expired). For instance, a first message may have an expiration in t=30 sec. from receipt, in which case the CPE message server logic may hold off generation and transmission of its message until the 30 sec. limit is approached, so as to aggregate other messages which may be received within that window from other client devices (and which will not expire during that window), so as to enable transmission of a common keep-alive message.
The CPE may also combine the information extracted from the keep-alive messages received from the client devices to generate a single keep-alive message to be sent to the content/service provider. The generated keep-alive message contains information associated with each client device e.g., a client device identifier and/or a connection identifier. The content/service provider extracts this information from the message to manage the connections for the multiple client devices.
In some implementations, the CPE may forego sending a message to the headend network. For example, the CPE may receive a subscription message from a first client device, e.g., a laptop computer, specifying a content provider and a category of content. The CPE updates the client device registry information to reflect the subscription. The CPE generates and sends a message to the content provider indicating that the CPE has subscribed to the content indicated in the message. Subsequently, the CPE receives a subscription message from a second client device, e.g., a handheld mobile device, subscribing to the same content as the first client device. The CPE updates the registry information to reflect that the second client device has also subscribed to the content. Because the CPE has previously subscribed to the content, the CPE foregoes sending a message to the content provider relating to the second device, since the “subscription” has already been established for an entity within that premises network. When the CPE receives published messages from the content provider, the CPE forwards the messages to both the first client device and the second client device in accordance with the information in the client device registry.
Referring now to
At step 502, the CPE receives a message from the headend network. The message may contain e.g., publish-subscribe content, an EAS notification, or control information.
At step 504, the CPE determines which client device(s) are to receive the message. In some embodiments, the message contains identifiers of specific client devices to which the message is targeted. For example, a message with control information may contain information identifying a specific device to which the control information applies (such as via unique MAC address or other identifier). In another embodiment, the CPE may consult the client device registry to determine distribution of the message, such as based on message type (e.g., only Clients A, C, and E are capable of or support that type of message protocol), and hence client-specific information in the message is obviated. In yet other embodiments, the CPE may determine that the message is to be broadcast to all client devices. For example, the CPE may determine that an EAS notification is to be broadcast to all client devices connected to the CPE (e.g., via a designation in the registry that all clients are to receive EAS messages regardless). In yet other embodiments, the CPE accesses the client device registry to determine where to send the message based on e.g., prior subscription. For example, when the CPE receives a publish-subscribe message addressed to only the CPE, the CPE searches the client device registry for records indicating which client devices subscribed to the message.
At step 506, the CPE generates the message(s) to be sent to the client device(s). The message may be generated using a format or protocol that can be interpreted by the client device (or where a given format or protocol is not common across all clients, via two or more formats or protocols). If the CPE determines that the message is to be sent to multiple client devices, the CPE replicates relevant portions of the message and inserts the relevant portions into the generated messages. For example, the message received from the headend network by the CPE message server process may include different control information for multiple client devices. The CPE may extract the information that is directed to a first device and include that information in the message generated for the first device, and extract the information directed to a second device and include that information in the message generated for the second device.
At step 508, the CPE sends the generated messages to the client devices. The CPE sends the generated messages by pushing the messages to the client devices via respective interfaces to the client devices.
Referring to
At step 602, the CPE receives a message from a premises device e.g., a remote control application running on a mobile device. The message may contain information for controlling another premises device e.g., a DVR, a STB, a home security camera, or a smart TV.
At step 604, the CPE determines that the message is directed to another premises device. In some embodiments, the CPE may determine this by extracting information from the message that identifies a destination device. The CPE may recognize that the information specifies a destination device that is within the premises network, such as by consulting a registry within the CPE listing all premises devices, or alternatively via an address falling within a specified address range or complying with a prescribed format. In other embodiments, the premises device sending the message may be paired with another premises device for ongoing communication (such as e.g., an open SIP or other session between processes running on the two devices). This pairing information may be stored in records of the client device registry associated with the paired devices. When the message indicates that it is a message directed to a paired device, the CPE may look up the pairing information for the message sender to determine which device is paired with the sender device.
At step 606, the CPE generates the message to be sent to the other premises device. The message may be generated using a format or protocol that can be interpreted by the other premises device. In some embodiments, a premises device may send one message that is to be forwarded to multiple premises devices. If the CPE determines that the message is to be sent to multiple premises devices, the CPE replicates relevant portions of the message and inserts the relevant portions into the generated messages. For example, the message received from the message sending device may include different control information for multiple other premises devices. The CPE may extract the information that is directed to a first premises device and include that information in the message generated for the first premises device, and extract the information directed to a second premises device and include that information in the message generated for the second premises device.
At step 608, the CPE sends the generated messages to the premises devices. The CPE sends the generated messages by pushing the messages to the premises devices via respective interfaces to the premises devices.
As one example of the foregoing, consider premises (e.g., home) automation functionality, such as for environmental control. In one such scenario, a user adjusts the central thermostat control of the premises (Client 2 in this example) to increase the overall temperature by 1 degree C. The central thermostat control sends a message to the CPE router 302, which sends it on to the CPE message server 303. The CPE message server recognizes the e.g., Layer 7 address to a publish/subscribe queue, and sends the message to such queue. Subsequently, all registered temperature control valves for the premises receive the message, as they were previously subscribed to that “topic”/queue.
As one specific example of the foregoing, the client devices (Client 1 and Client 2 may be set-top boxes attached to displays that are each showing a grid of times and channels in which programs will be shown). Corresponding users are associated with each display in this example. Client 2 includes a remote control, and the application server is a cloud Digital Video Recorder (cDVR). When the user with the remote of Client 2 presses “record” (such as when their display is showing a highlight of a particular program on a particular channel), a message is generated and sent to the router 302 of the CPE 106 via e.g., the CPE switch, since the network address of the (remote) application server is not in the address table of the router (so no ARP response is given), and the client then sends it to the router network address. The router then forwards the message from the remote onto the next-hop router on the network (e.g., Internet) for delivery to the application server. The application server sets up the schedule to perform the recording, and then sends a message to the central messaging server (e.g., a “push notification” server), which may or may not be within the same MSO or other network), which sends the message back to the CPE router 302, which then sends it to the message server 303 in the CPE 106. Thereafter, the message is sent onward (e.g., using the “pub/sub” approach) to both Client 1 and Client 2. Both of those devices now generate visual indicia on the displays indicating that the desired program is scheduled to be recorded. Thus, both displays provide accurate information with a single message coming back from the remote network entities. Without the message server 303 in the CPE 106, two messages would be required to provide this same functionality.
In one exemplary implementation (
In another implementation (
It will also be recognized that while many of the foregoing embodiments are described in terms of “generation” of messages, the present disclosure contemplates that messages, when appropriately formatted, may simply be forwarded, or modified (contrast generation of a new message). For instance, a given message generated by a client device in the context of the method of
Many other approaches and combinations of various operational and business paradigms are envisaged consistent with the present disclosure, as will be recognized by those of ordinary skill when provided this disclosure.
It will be recognized that while certain aspects of the present disclosure are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods, 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 present disclosure and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the disclosure 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 ideas set forth herein. The foregoing description is of the best mode presently contemplated of carrying out the disclosure. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of. The scope of the disclosure should be determined with reference to the claims.
This application is a divisional of and claims priority to U.S. patent application Ser. No. 16/557,619 of the same title filed on Aug. 30, 2019, and issuing as U.S. Pat. No. 11,258,832 on Feb. 22, 2022, which is a divisional of and claims priority to co-owned U.S. patent application Ser. No. 15/055,205 of the same title filed on Feb. 26, 2016, and issued as U.S. Pat. No. 10,404,758 on Sep. 3, 2019, each of which are incorporated herein by reference in its entirety.
| 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 |
| 6678004 | Schultheiss | 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 et al. | Oct 2009 | B2 |
| 7609637 | Doshi et al. | Oct 2009 | B2 |
| 7624337 | Sull et al. | Nov 2009 | B2 |
| 7624415 | Zhang | Nov 2009 | B1 |
| 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 et al. | 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 | Sep 2014 | B1 |
| 8910218 | Tirasirikul | Dec 2014 | B2 |
| 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 |
| 9357247 | Cronk et al. | May 2016 | B2 |
| 9906838 | Cronk et al. | Feb 2018 | B2 |
| 10136172 | Cronk et al. | Nov 2018 | B2 |
| 10404758 | Straub | Sep 2019 | B2 |
| 11258832 | Straub et al. | Feb 2022 | B2 |
| 11343554 | Cronk et al. | May 2022 | 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 et al. | 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 et al. | 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 |
| 20050259645 | Chen | Nov 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 | 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 et al. | 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 |
| 20080098089 | Luciani | Apr 2008 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080098450 | Wu et al. | Apr 2008 | A1 |
| 20080112405 | Cholas et al. | May 2008 | A1 |
| 20080133551 | Wensley et al. | Jun 2008 | A1 |
| 20080134165 | Anderson | 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 et al. | 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 |
| 20090240829 | Hildebrand | 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 |
| 20100138858 | Velazquez | Jun 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 |
| 20100287585 | Frondal 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 |
| 20110107436 | Cholas 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 |
| 20110252146 | Santamaria | Oct 2011 | A1 |
| 20110265116 | Stern et al. | Oct 2011 | A1 |
| 20110276881 | Keng et al. | Nov 2011 | A1 |
| 20120005527 | Engel et al. | Jan 2012 | A1 |
| 20120008786 | Cronk et al. | Jan 2012 | A1 |
| 20120011567 | Cronk et al. | Jan 2012 | A1 |
| 20120023535 | Brooks | 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 |
| 20130227284 | Pfeffer et al. | Aug 2013 | A1 |
| 20140051485 | Wang | Feb 2014 | A1 |
| 20140074855 | Zhao et al. | Mar 2014 | A1 |
| 20140223505 | Lazaridis | Aug 2014 | A1 |
| 20140281707 | Su | Sep 2014 | A1 |
| 20140281904 | Burckart | Sep 2014 | A1 |
| 20140359153 | Heng | Dec 2014 | A1 |
| 20150006744 | Chatterjee | Jan 2015 | A1 |
| 20150040176 | Hybertson et al. | Feb 2015 | A1 |
| 20150095932 | Ren | Apr 2015 | A1 |
| 20150271865 | Carson | Sep 2015 | A1 |
| 20150350714 | Normile | Dec 2015 | A1 |
| 20150381680 | Thornburgh | Dec 2015 | A1 |
| 20160134912 | Dillon et al. | May 2016 | A1 |
| 20160337464 | Eriksson | Nov 2016 | A1 |
| 20170048336 | Novo Diaz | Feb 2017 | A1 |
| 20170177321 | Seastrom | Jun 2017 | A1 |
| 20170230702 | Sarosi et al. | Aug 2017 | A1 |
| 20170251026 | Straub | Aug 2017 | A1 |
| 20170339200 | Roy | Nov 2017 | A1 |
| 20180054774 | Cohn | Feb 2018 | A1 |
| 20180359621 | Singhal | Dec 2018 | A1 |
| 20190200062 | Cronk et al. | Jun 2019 | A1 |
| 20200059497 | Straub | Feb 2020 | A1 |
| 20220182421 | Straub | Jun 2022 | 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]. |
| Cantor., et al., “Bindings for the Oasis Security Assertion Markup Language (SAML) V2.0,” Oasis Standard, Mar. 2005, DocumentID saml-bindings-2.0-os, (http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf), 46 pages. |
| DLNA (Digital Living Network Alliance) protocols described in DLNA Networked Device Interoperability Guidelines Expanded, Mar. 2006 and subsequent expanded version dated Oct. 2006, 23 pages. |
| 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]. |
| OpenCable, Enhanced TV Binary Interchange, Format 1.0 OC-SP-ETV-BIF1.0-104-070921 Date: Sep. 21, 2007, 420 pages. |
| 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. |
| 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. |
| Savolainen T., et al., “IPv6 Addressing Strategies for IoT,” IEEE Sensors Journal, 2013, vol. 13 (10), pp. 3511-3519. |
| Siebenlist F., et al., “Global Grid Forum Specification Roadmap towards a Secure OGSA,” Jul. 2002, pp. 1-22. |
| Spagna S., et al., “Design Principles of an Operator-owned Highly Distributed Content Delivery Network,” IEEE Communications Magazine, 2013, vol. 51 (4), pp. 132-140. |
| UTF-32, IBM, retrieved from http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Fnls%2Frbagsutf32.htm on Aug. 28, 2013, 1 page. |
| Number | Date | Country | |
|---|---|---|---|
| 20220182421 A1 | Jun 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16557619 | Aug 2019 | US |
| Child | 17675408 | US | |
| Parent | 15055205 | Feb 2016 | US |
| Child | 16557619 | US |
