Multi-services gateway device at user premises

Description

TECHNICAL FIELD

The present subject matter relates to gateway devices and/or programming for such devices that provide application services for a user premises and for associated endpoint devices, wherein to facilitate management of the application services, wherein service access if provided to a user via voice commands.

BACKGROUND

The digital home is now becoming more complex with the myriad of new and emerging digital devices intended to address many user and consumer needs such as communication, entertainment, privacy and security, etc. However, given the complexity of the emerging digital home and digital environments generally, users who are technologically challenged may find it a daunting and intimidating task to manage their home networks and interconnected digital devices. Moreover, new paradigms are emerging oriented to delivering media content to and the consuming of media content at the home. Many of these paradigms rely on communication of application specific data to and/or from the Internet, as opposed to conventional telephone or broadcast video type applications. The protection of received Internet-sourced media content in addition to user-generated media content is additionally an important aspect that may be inadequately addressed by the technologically challenged user. Furthermore, with respect to Internet based data, most of the content delivery solutions are provided to the digital home networks through availability of the “two-foot” interface (i.e. the PC). It is relatively cumbersome to bring this content to the “ten-foot” interface (e.g. the television).

Thus, a need exists for a technique or devices to simplify the overall management of services and applications available to the digital home or even the small enterprise. Such a technique or devices would reduce the complexity of the maintenance, upgrading, and operation of even the more basic needs addressed by emerging digital endpoint devices and networks. Approaches that suggest greater functionality in home-based appliances fail to reduce or address the complexity of managing and provisioning those appliances. For example, while the home gateway server appliance described in U.S. Pat. No. 6,930,598 enables networked electronic devices to communicate with each other without the direct interaction with external networks, and provides a mechanism whereby a member of the household may be informed of certain network related events without having to use their home computer or other client devices, it does not provide a convenient or simplified way of managing the services and applications executed by, or associated with, that device. Thus, an unmet need exists for a device associated with a user premises that has robust functionality but does not require sophisticated or inordinate attention from the user to manage, provision, and utilize them.

In practice, a customer typically subscribes to basic transport services from a network “Service Provider” (e.g. ISP-Internet Service Provider, cable provider, fixed wireless providers, ILEC—Incumbent Local Exchange Carrier, or CLEC—Competitive Local Exchange Carrier). For example, a customer may have broadband Internet access, via cable modem, digital subscriber line service or the like. Digital video service may be provided separately. The network service provider manages these basic services, at the logical network layer, typically at layers 1, 2 or 3 of the OSI model. While network services and associated devices may operate minimally at those levels, they operate at those levels only to support operations at OSI layers 1, 2 or 3. Many applications, however, involve higher level service logic for applications that view the network transport as a transparent pipe. The current internet applications delivery and management architecture, and many devices or management systems based on it, require a server with robust processing and storage capability to be located at the network operations center, not in the home. For voice over internet protocol (VoIP) type telephone service, for example, the VoIP service provider operates a session initiation protocol (SIP) server or the like, and each user has only client functionality. The network transport layers are transparent to the IP packets containing the voice and related signaling. The SIP server, however, controls the call set-up, tear-down, billing and the like for the voice call services. With such an architecture, the major capabilities and functionalities connected with providing application services from the server throughout the network reside on the server and supporting elements, all of which are located in the network operations center.

It might be helpful to walk through examples of the configuration for application services delivery to a client of an application within a user premises under the typical, current network configuration. FIG. 10 depicts one possible configuration for a client application to access a particular service that is being hosted or served outside of the user premises based on the typical, and currently employed, network application service configuration. We identify two regimes in the overall architecture, the Service Provider Network regime (WAN side), and the User Premises Network regime (LAN side). The association between the Service Provider Network and the User Premises Network is broken down into three layers; Network Interconnect Layer (NI), Network Function Layer (NF), and the Application Services Layer (AS). These layers do not represent physical communication pathways, but are a logical representation of pathways and elements employed in a network-based communication.

The separation between the managed Service Provider Network (WAN side) and the User Premises Network (LAN side) is depicted as the Network Service Provider Demarcation. The Network Service Provider Demarcation at the Network Interconnect Layer represents the logical and physical separation between the user premises and the broad-band network. In the present representation of the three functional layers, the Network Service Provider Demarcation is extended into the Services and Application Layer to emphasize the functional barrier at that layer between the Service Provider Network and the User Premises Network, in currently configured networks.

The NI Layer depicts how the connectivity between a User Premises Network and the Public/Service Provider Network is established. On the Service Provider Network side, the Wide Area Network services are terminated onto a WAN termination device with the appropriate interface (e.g. a Broadband internet service such as ADSL would terminate on to a managed ADSL Terminal Adapter). The WAN termination layer adapts the WAN interface into a compatible LAN interface (e.g. Ethernet or WiFi). On the User Premises Network side the LAN Termination interfaces are used to connect to the Local Area Network via a variety of interfaces, such as Ethernet, WiFi, MOCA, etc.

The LAN Termination interfaces and the WAN Termination interface could reside on two separate physical devices or they could reside on one physical device. In either case, on the User Premises Network side, packets or data must flow through the NF Layer between the WAN Termination Interface and the LAN Termination Interface. One or both of these interfaces may reside on a “gateway” device. Gateway and like router devices are currently available for various premises that allow several computers to communicate with one another and to share a broadband Internet connection. These devices function as routers by matching local network addresses and the hostnames of the local computers with the actual networking hardware detected. As gateways, these devices translate local network addresses to those used by the Internet for outgoing communications, and do the opposite translation for incoming packets.

The User Premises NF Layer allows for switching of packets between LAN devices and routing or bridging of packets between the LAN and WAN interfaces. It could physically reside on the same device(s) with the LAN Termination or it could exist at an independent device that could interconnect to the LAN Termination interface via a variety of physical interfaces (e.g. Ethernet, MOCA, etc.). The Service Provider NF Layer provides the Wide Area Network access between the WAN Termination device and the AS Layer where all the applications servers are being hosted. The Internet could be used for this connectivity as could a private packet/cell network (e.g. Cellular packet network, or a private ATM or packet backbone).

The AS Layer represents the functional layer that provides access to applications services by application clients. On the User Premises side, the AS Layer provides a Firewall to protect the application client from application level attacks from the open Internet. On the Service Provider side, the AS Layer encompasses application services such as Parental Control, Backup, and Call Processing. These application services exist on a managed Application Service Delivery Platform (ASD) on a secure network server that can be hosted at a facility that has private and or public data connection paths. The ASD may include three functional modules, namely the Application Service Enforcement (ASE) module, the Application Service Logic (ASL) module, and the Application Service Management (ASM) module.

The ASE module is responsible for enforcing the relevant Application Client privileges to the application services. It gets the policies and permissions of each application client from the ASM module (such as provisioning data and subscription data) and enforces those policies against the requested actions by the client application.

The ASL module executes the application services that the Application Clients request. Such services could be Call Processing, Parental Control, Peered Networking, Backup, etc. The ASL module must interact with the ASM module for monitoring purposes and status information such as Call Data Recording and Billing. It must also interact with the ASE module to provide access to the client applications that have passed the policy enforcement procedures.

The ASM module, as described above, provides the necessary data to the ASE and ASL modules for them to carry out their respective functions. It also oversees the overall integration and communication among all the modules and the services that are managed by the ASM. The ASM also manages the overall security and integrity of the ASD.

All ASD modules are in constant communication with each other, preferably through secure connections. The inter-module communication may be managed by the ASM, or may be independent of a central management function. Note that the ASE, ASL and ASM modules are only examples of functions that may be logically bundled; other bundles, and other means of bundling these functions, are possible.

FIG. 11 depicts a logical flow of how a specific Application Client residing at a user premises could interact with an Application Service that is being managed in the typical network configuration. Traditionally, as depicted in this example, an Application Client (e.g. Telephony) that needs to connect to an Application Service (e.g. call processing) must first connect to the Local Area Network termination interface (1). Depending on the specific deployment, a switching function, routing function or bridging function is used to establish the connection path between the application client (2) and the Firewall service (3). The Firewall Service works in conjunction with the router function (4) to permit access to the Wide Area Network interface (5) and maintain a level of security to the Application Client. The firewall service in this example is not aware of either the type of application client or the specific application service that is being targeted. There is no feedback mechanism between the Application Service Delivery Platform and the Firewall function. Once connectivity to the WAN termination interface is established, routing mechanisms are used to establish a connection through the Service Provider Network Function Layer (6) to the Application Service Layer (7). At the Application Service Layer, the client application goes through application validation procedures and privilege and permission checks by the ASE prior to allowing the application client to connect to the desired application service.

In the logical hierarchy, such as shown in FIGS. 10 and 11, a home gateway device may implement the NI layer functions and the user premises side NF layer functions. The firewall functionality may reside in the gateway or in one or more other elements on the premises network. For example, many PCs internally implement firewalls, e.g. in close association with the client programming of the endpoint device. As can be seen by the illustrations in FIG. 11, however, even with a home gateway deployment for a premises network, the application services functionality still requires the support and service logic to reside on a server in the network. That is, for service provisioning, service management and upgrades, remote diagnostics, for a digital endpoint device such as a PC or SIP phone, the home premises still must rely on the application service logic executed by the service providers in their server networks, typically according to proprietary platforms. Moreover, many other core services, e.g., file storage, media content access and delivery, are offloaded to other 3rd-party service providers that provide service logic and support applications at their network server devices.

With the paradigm discussed above relative to FIGS. 10 and 11, it is currently the case that many of the application service providers also find it difficult to provide and support new emerging technologies at the home. That is, service providers are challenged to select a platform that can evolve with their applications. With existing service architectures, the launch of new services compounds complexity to the core network, adding to both capital and operating expenditures.

Thus, as new services come to the fold, often with the requirement of new equipment, e.g. integrated access devices (IADs) for VoIP and set-top boxes for streaming video, the management of the customer premises equipment (both hardware and software) complicates customer support requirements. Managing the home network environment can be an inhibitor to the adoption of new services, both from the user perspective and from the perspective of management by the service providers.

A need exists for a new paradigm, with improved convenience for the user and easier management for the application service provider. In that regard, it would be desirable to provide a multi-services application gateway device that provides not only a variety of IP-based communication services, but also offers a centralized management capability for application services.

SUMMARY

The technology discussed herein may be embodied in gateway devices, typically for deployment at user premises, and/or to programming for devices that may function as such gateways. Such a gateway device includes a first interface for enabling bi-directional communications within the premises; a second interface for enabling bidirectional communications external to the premises via a wide area network; a voice-based user interface enabling management and control of application services executed by the gateway and at least one of the associated endpoint device via voice commands from a user, and a processor coupled to the interfaces for execution of the programming to provide a managed service for one or more endpoint devices associated with the gateway device. The gateway devices are implemented in such a manner as to offer users of endpoint devices one or more application services and to implement logical demarcations.

An application gateway can include application service programming logically positioned on a user premises side of a logical network demarcation forming an edge of the wide area network at a user premises provides managed services to at least one of a user and one or more endpoint devices associated with the application gateway. The application gateway can be controlled remotely by the application service provider through a service management center and configured to execute an application service provided from the application service provider. The application gateway executes the application service at the user premises independent of application services executing on the application service provider's network. An application service logic manager can communicate with an application service enforcement manager to verify that the request conforms with the policy and usage rules associated with the application service in order to authorize execution of the application service on the application gateway, either directly or through endpoint devices. A graphical user interface rendered on a display associated with at least one of the gateway and an endpoint device for enabling management and control of application services executed by the application gateway.

An application gateway can enable multiple services including: home automation of connected devices within the user premises; home security of the user premises via connected devices within the user premises; management of video cameras and associated video data captured within the user premises; management of sensors located at or within the user premises; management of monitors at or within the user premises; home automation of connected devices within the user premises; management, including monitoring, of medical devices within the user premises; management of wired and wireless connections to endpoint devices at or within the user premises; management of digital rights utilized by endpoint devices at or within the user premises; management of context sensitive advertising that is available for rendering on endpoint devices at or within the user premises.

In a disclosed example, the demarcation in accessibility to hardware resources of the gateway device, provided by the logical service provider-user demarcation, delineates a portion of the storage accessible by a user via an endpoint device from an application service provider portion of the storage, which contains the application service programming and/or data of the application service provider. For example, the user of an associated endpoint device may be able to store and retrieve data files in the user accessible portion of the storage of the gateway device. The application service provider, in turn, can control storage and retrieval of data files in the application service provider space portion via the wide area network. However, the user of the associated endpoint device is prevented from accessing one or more of the data files in the application service provider portion. In one service application, the application service provider can allow storage and retrieval of data files in the application service provider portion via the wide area network, for other gateway devices. In a specific example, the logical location of the demarcation line separating the portions of the storage is controllable by the application service provider, from the service management center, via the wide area network and the second interface.

The programming for example may implement a number of application services. For each application service, execution of the programming causes the gateway device to provide functions in relation to a respective service for one or more of the associated endpoint devices. The functions of such an application service include application server communication with a client functionality of one or more endpoint devices, for the respective service, communicated on top of network layer communications through one or both of the interfaces. The application service logic on the user premises side may also enforce authorization, authentication, configuration, or use of the respective service via an endpoint device. However, management of the application service is based upon the communications with the service management center, via the wide area network, through the second interface.

Although based on a Client-Server architecture, the exemplary gateway devices and service management center move substantial functions performed by the typical network server into the user premises by incorporating those functions into the gateway device, but in a way that allows for the server functionality to be externally managed by the service management center, which may be operated by a third-party service provider. Moreover, the server functionality residing in the gateway device is not only located in the premises but it now resides on the premises side of the Network Service Provider Demarcation. This approach in the examples does not just move server functionality from the servers in the network operations center, where they were previously located, to the home; but it also moves the logical position of the execution of application services logic of the server to the user premises side of the Network Service Provider Demarcation and provides logical hooks to enable the external service manager to perform its function(s) on that side of the demarcation. For example, application services related to the use of one or more endpoint devices can now be provisioned, serviced, and managed on the user premises side of the Network Service Provider Demarcation, albeit by an external service management center operated by a third-party service provider. The application software architecture, coupled with the specific managed hardware implementation at the user premises, enables a single service provider to provide the network services, whereas one or more application services providers (possibly including the network service provider) can provide the applications services to the customer independently of providing the network service.

The illustrated architecture also manages the utilization of network and transport resources in the use and execution of application services in the premises. Because appreciable functionality now resides in the gateway device, and many application services may now be located and executed at or through it, with a concomitant demand on premises resources, the utilization of resources in the application or execution of application services may need to be coordinated. For example, if one or more application services are invoked at the user premises and these application services utilize resources (e.g. CPU, WAN bandwidth, LAN bandwidth, memory), an application service may compete for resources with either basic network service usage activities (downloading files from the internet, etc.) or other application services. The architecture provides for “managed application services” functions at the gateway device that monitor resource demand and usage, according to policies and priorities for management set by the service management center, allocating resources to application services based upon application service characteristics and priorities. This helps ensure a consistent, reliable user experience, even when there are multiple application services and other activities consuming resources in the home. The service management center is not involved in these functions on a real-time basis; it does, however, establish (and update) the policies and priorities that are configured and implemented in the gateway device.

By distributing the application services to the edge of the novel architecture of this network, but retaining a central management feature, the disclosed architecture addresses network computing and traffic capacity and latency challenges of providing application services at the network level. The exemplary architecture thus results in significantly reduced latency and improved reliability.

Another aspect of the architecture is that it enables the managed service provider to control hardware elements (endpoint devices) of various types located on the other side of the Network Service Provider Demarcation through the gateway, and to manage application services directed to particular endpoint devices. The robustness of the gateway device, coupled with the central management capabilities of the service management center, allow the system to register, configure, provision, and enable inter-communication among, a wide variety of endpoint devices, such as TV, cell phone, radios, PC, and digital picture frames. Such a centralized management greatly reduces the burden on end users in managing their equipment or network. However, with this approach, it is relatively simple for a service provider to adapt service to a new user-premises technology.

Additional advantages and novel features will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following and the accompanying drawings or may be learned by production or operation of the examples. The advantages of the present teachings may be realized and attained by practice or use of various aspects of the methodologies, instrumentalities and combinations set forth in the detailed examples discussed below.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord with the present teachings, by way of example only, not by way of limitation. In the figures, like reference numerals refer to the same or similar elements.

FIG. 1 is a layered logical block diagram with arrows representing steps of a sample logical flow, for an application client to access a specific managed application service, in a gateway device-service management center type network configuration, and shows a first or Network Service Provider Demarcation at the network edge;

FIG. 2 is a high-level depiction of the logical architecture of the software and hardware of a multi-services applications gateway device, together with a network service provider termination apparatus for broadband connection to a wide area network, and shows the first demarcation as well as a second demarcation between the Application Service Provider and the User;

FIGS. 3A to 3C depict the software and hardware architectures of the multi-services applications gateway device;

FIG. 4 is a network diagram, depicting a gateway device, endpoint devices at the user premises, one or more wide area networks and a service management center;

FIGS. 5A and 5B conceptually depict the demarcation in a storage media that provides isolation of downloaded service logic and associated data for implementing services from service provider and/or downloaded content, from a user generated content;

FIG. 6 conceptually depicts a virtual hosting (space-sharing) service provided by the gateway device;

FIG. 7 is a signal flow diagram;

FIGS. 8 and 9 are process flow diagrams, which illustrate operations for providing backup services for files to a third party storage provider and peer gateway appliances;

FIG. 10 is a layered logical block diagram of one possible configuration for service delivery to a client of an application within a user premises based on a typical current network architecture; and

FIG. 11 is similar to FIG. 10, but overlaid with arrows to show a sample flow of logical steps taken by an Application Client to access a specific managed Application Services in the typical current network configuration.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are set forth by way of examples in order to provide a thorough understanding of the relevant teachings. However, it should be apparent to those skilled in the art that the present teachings may be practiced without such details. In other instances, well known methods, procedures, components, and circuitry have been described at a relatively high-level, without detail, in order to avoid unnecessarily obscuring aspects of the present teachings.

The various technologies disclosed herein move application service logic, formerly resident in a network node, into a gateway device in the customer premises. The gateway device is implemented in such a manner as to offer its user many of the applications services, such as were previously offered from network-side servers, from the user premises. A logical Network Service Provider Demarcation is formed at the edge of the wide area network at the user premises, that is to say between the wide area network and the equipment in the user premises. The application service logic resides on the user premises side of this first demarcation. The gateway device programming also defines a logical service provider-user demarcation between the user premises and the application service provider, referred to in later examples as the Applications Service Provider Demarcation. The application service programming resides on the service provider side of this second demarcation and can be controlled or managed by the application service provider, typically by communications through the wide area network. The user's access to the programming and resources between the two demarcations is limited. The application service programming only provides a logical application service interface across the Applications Service Provider Demarcation, for delivery of one or more application services to an endpoint device. The Applications Service Provider Demarcation also provides a demarcation in accessibility to hardware resources of the gateway device, whereby some hardware resources of the gateway device are on the service provider side of the logical service provider-user demarcation and are inaccessible to an endpoint device from the user side of that demarcation.

In a typical scenario, a network service provider takes responsibility for managing resources on the network side of the Network Service Provider Demarcation, leaving the user to manage everything on the premises side of that first demarcation. However, in the gateway devices discussed below, an application service provider takes responsibility and controls/manages the software and hardware resources between the two demarcations. This approach provides the application service provider with management control over resources in the premises that deliver that providers' higher layer services, and the application service provider can relieve the end user of many of the burdens of managing customer premises resources.

Examples of application services include one or more of: media delivery, content management, access control and use tracking, file sharing, and protection and back-up services of both Internet/Web-generated digital media content and user generated digital media content. The disclosed gateway device thus is configured and programmed to simplify various aspects of managing the emerging home/business digital networks including the myriad of interconnected digital endpoint devices associated with the gateway device. The endpoint devices need not reside within, or be located at, the premises to maintain their association with the gateway device. For many of the exemplary application services, the application service programming between the demarcations in the gateway device implement server functionality for interactive communication with client functionality of the endpoint devices. Application service functionality of the gateway device, as provided by this client-server interaction, is enabled/disabled and configured by the application service provider, via communications between the gateway device and a service management center via the wide area network.

In this way, the gateway device and service management center move substantial functions performed by the typical network server into the user premises by incorporating those functions between the two demarcations at the gateway device, but in a way that allows for the server functionality to be externally managed by the service management center from the network side, which may be operated by a third-party service provider. In this exemplary architecture, both the server functionality and the application services offered via the gateway device may be managed by the service management center. Moreover, the server function residing in the gateway device is not only located in the premises but it now resides logically on the premises side of the Network Service Provider Demarcation and on the service provider side of the Applications Service Provider Demarcation. In the detailed examples, the gateway device and system architecture place a set of application services on a tightly coupled (e.g. always-on or always-available basis), secure hardware platform that is externally managed.

Reference now is made in detail to the examples illustrated in the accompanying drawings and discussed below. FIG. 1 is a high-level diagram of the architecture of a gateway-service management center network, as well as the logical flow of how a specific Application Client residing at a User Premises could interact with an Application Service in a gateway device that is being managed in the gateway-service management center network configuration. Heretofore, as described above, many application services that form part of the Application Service Delivery Platform were logically positioned at the AS Layer but on the network side of the Network Service Provider Demarcation (see FIGS. 10 and 11). FIG. 1 shows that, in the exemplary architecture, many of these application service functionalities that were previously offered from network-side servers have now been moved across the Network Service Provider Demarcation and now logically reside at the AS Layer in the User Premises Network, i.e., on the hardware components located, in the user premises, such as, by example, a gateway device. In particular, the programming that implements application services is logically positioned on the user premises side of the Network Service Provider Demarcation. The application service on the user premises side that enforces authorization, authentication, configuration, or use of the respective service via an endpoint device is logically depicted in FIG. 1 as the ASE module in the AS Layer of the User Premises Network. The ASE module may also communicate via the wide area network with the ASM logic residing in the service management center.

FIG. 1 thus depicts an approach in which the ASL and the ASE functions have moved to the User Premises side. In the example of FIG. 1, the application client would be implemented on an endpoint device, whereas other elements/functions to the right of the Network Service Provider Demarcation are implemented in a gateway device. As discussed more below, the ASL and the ASE functions are implemented as high-level server type logic within the gateway device at a user premises. Hence, elements shown in FIG. 1 that may reside in the user premises gateway device include the user premises-side network function or NF (switch, router or bridge) and the LAN termination for communication with the endpoint devices implementing the application client functions. Thus, with reference to FIG. 1, the first interface, as described above, for enabling bi-directional network layer communications on the user's side of the premises with one or more of the associated endpoint devices resides at the NI Layer and provides the LAN Termination referenced therein. FIG. 1 also depicts the WAN termination providing connectivity to the wide area network (network-side NF—Internet or private wide area data network). The gateway device's second interface, as described above, for enabling bi-directional network layer communications for the associated endpoint devices via a wide area network resides at the NI Layer and provides the WAN Termination referenced therein. The gateway device's second interface also enables bi-directional communications between it and the service management center via the WAN.

With reference to FIG. 1, the core of the logical capacities of the service management center resides on the Service Provider Network, and is depicted as the Application Service Management (ASM) portion of the Application Service Delivery Platform in the AS Layer. The ASM function is implemented in the service management center, which is external to the user premises, and, perforce, on the network side of the Network Service Provider Demarcation. The ASL and ASE functions maintain logical connectivity or interaction with the Application Service Management (ASM) function in the service management center, typically via communication through a wide area network. This logical connectivity is established through an always-on (or on an as needed, periodic basis), secure communication channel between the User Premises AS Layer (ASL and ASE) and the Service Provider AS Layer (ASM) at the service management center. The service management center and the communications of the center with one or more of the gateway devices provides an infrastructure support and/or management of the application services offered to endpoint devices and their users by the logic implemented in the gateway device(s). Effectively, the ASD, considered in its entirety, extends all the way to the User Premises and traverses the Network and Network Service Provider Demarcation. The secure communications channel is established through the NF Layer and the NI layer.

The examples discussed herein also introduce a logical platform management layer to the user premises-side, which allows for inter-layer allocation of local resources. This function guarantees access between the Application Service Logic function on the user premises network and the applications service management function in the service management center by assuring that the local user premises hardware and software modules are functioning at a required state (CPU and memory usage, bandwidth usage, QoS settings, etc.) in order for the ASL to have the necessary resources to establish its required communications path to the ASM.

The platform management layer is also responsible for implementing that part of the managed application services to be performed by the gateway device. In that regard, the platform manager secures and manages the overall hardware platform, given that in this scenario, the NF layer and the AS layer reside on one hardware platform. This secure hardware platform provides a robust and secure operating environment for the AS Layer. So, to establish a secure and robust hardware operating environment, the platform manager must interface with all the layers above it and allow for bi-directional management information flow among all of the functions. For example, if the Application Client is a telephony application and the desired application is call processing, the application must first connect to the LAN termination interface (1). Then a connection must be established to the AS Layer through the NF layer (2). At this point the platform manager determines if there are sufficient resources available for this to take place on the routing and switching modules and if there is not sufficient resources on either the LAN Termination interface or the NF layer functions, it would take the necessary corrective measure to free up the required resources so that the application can execute properly (e.g. prioritize packets, throttle bandwidth, attempt to reduce noise on an RF interface, or free up time slices on a TDMA interface such as MoCA). Once that is done, the connection is established to the AS Layer (3), where the ASE and ASL, having been updated by the ASM in the network, respond instantaneously to the Application Client, completing the service request.

Application services represent functionalities, implemented in the higher layer(s) of the protocol or logical stack above the network layer(s) that may extend up to the top application layer (layer 7 of the OSI model). An application service, for example, provides application server communication with a client functionality of one or more endpoint devices, for the respective service, communicated on top of network layer communications through the interfaces. In the examples, the services are provided on a subscription service basis to users at the premises. Hence, the application service logic provides enforcement regarding authorization, authentication, configuration, and/or use of the respective service via the endpoint devices. The application service includes service and feature functions, implemented and controlled by the application service logic. Management of the application service is based on communications with the service management center via the wide area network.

The illustrated architecture of the gateway device-service management center network enables other features and capabilities that have not previously been available to the user. For instance, peer-to-peer application communication between or among gateways is possible without the need to go through, or utilize resources at, an external service management center. Communications through the service management center are also possible. In addition, given the considerable functionality present in the gateway device, and its ability to manage the various endpoint devices associated with it (as explained below), the user interface with the gateway can be presented and utilized on the home TV. Additionally, information from other endpoint devices, such as the PC, network sources (such as an RSS (Really Simple Syndication) service), may now be overlaid on the TV screen so that, for example, PC messages, or weather information, can be viewed on the TV screen, and the functionality of the PC (or other home-networked endpoint devices) can be accessed from the TV screen.

As shown by the discussion of FIG. 1, application service programming is logically positioned on a user premises side of a logical network demarcation forming an edge of the wide area network at the user premises, that is to say on the user premises side of the Network Service Provider Demarcation. The gateway device programming however, also defines a logical service provider-user demarcation between the user premises and the application service provider, as will be described in more detail with regard to FIG. 2.

FIG. 2 depicts logical and physical elements as may be deployed at a user premises. At the Physical/Network layer shown therein, the drawing shows an example of user premises hardware components required for delivering data services (i.e. Internet connectivity) along with a separate, non-integrated managed hardware used in delivering a set of managed application services (e.g. IM, VOD, IP telephony). The Network Service Provider Wide Area Network Termination Apparatus (NSP-TA) allows for a typical termination of a Wide Area Network Services connection, such as DSL, Cable, Fiber, etc., by a network services provider. The NSP-TA provides the WAN Termination in the NI Layer (FIG. 1). The NSP-TA may be an existing user-premises device, provided by the carrier supplying network services to the premises. FIG. 2 also depicts the Network Service Provider Demarcation at the hardware level.

If configured as a standalone device, the NSP-TA device is required to have its own CPU, Memory, physical interfaces and logic control. In order for Network Service Providers to deliver managed services, they typically require a management element controlled by the CPU on the NSP-TA. To depict these logical elements residing on the hardware components, FIG. 2 includes a representation of the user premises Application Services Layer above the hardware layer. This layer corresponds to the AS Layer of FIG. 1, but without reference to any logical elements residing at the network services provider. The management element, represented by the Network Service Provider Managed Application, allows the network service provider to determine the status of the network hardware device and interfaces as well as maintain a certain degree of security enforcement at the customer premises.

As noted, the network service functionality is at the NI and NF Layers and generally does not extend to the AS Layer(s) beyond basic authentication, authorization and state management. As with the hardware components, the logical elements also have a Network Service Provider Demarcation as shown in FIG. 2. On the WAN side, depicted as the Network Service Provider Managed Applications side, of the Network Service Provider Demarcation, resides the applications that are managed, and under the exclusive control, of the network service provider (the Network Service Provider Logic). The User Interface to Managed Applications is present on the LAN side of the Network Service Provider Demarcation within the Application Services Layer. Within this interface resides programming and logic available to users other than the network service provider referred to as the Network User Controlled Logic. The Network User Controlled Logic, which is depicted at the Application Services Layer in FIG. 2, provides a user interface to the Network Service Provider Logic and, to the extent permitted by the Network Service Provider Logic, interaction with or communication between the user and network service provider through the Network User Controlled Logic and the Network Service Provider Logic, and to the NSP-TA hardware components. The Network User Controlled Logic allows for the User of the hardware to make certain, minimal programming changes relevant to their preferences (e.g., user name and password changes, local IP addresses changes, local interface selection). All user devices typically can only communicate with the NSP-TA through one or more of the User Premises Network Interfaces. The user can modify the Network User Controlled Logic through the User Premises Network Interface. The Network Service Provider Demarcation is typically within the NSP-TA, logically dividing the Network Service Provider Interface and the User Premises Network Interface modules. The network service provider does not have any in-depth visibility or significant responsibility beyond the Network Service Provider Demarcation.

In the example, the User Network and Application Delivery Apparatus (UNA-DA), shown on the right hand side of FIG. 2, is a separate managed gateway device 10 that a managed-service provider (which may be different than the network service provider) would control in delivering a set of application services to the user premises. This device is required to have its own dedicated CPU, memory, logic control, as well as its own dedicated set of interfaces. The UNA-DA includes one or more Network Interfaces providing connectivity to the NSP-TA as well as to user premises endpoint devices. The interfaces provide the LAN Termination functionality at the NI Layer (FIG. 1). One skilled in the art will readily recognize, however, that the physical connection that connects the UNA-DA to the NSP-TA also provides connectivity for the UNA-DA to the public (WAN side) network, and is the means by which the UNA-DA accesses the public network. The end point devices connected to the LAN Interface are on the private (LAN) side of that interface. The UNA-DA also includes a switch, router or bridge for the NF Layer.

Programming elements of the UNA-DA in the gateway device 10 are depicted at the Application Services Layer of the UNA-DA. Certain logical elements, depicted as the Application Service Provider Managed Applications and Platform in FIG. 2, on which resides, inter alia, the programming corresponding to the ASL and ASE of FIG. 1, are managed by the managed application service provider's network control center, e.g. by the ASM through a wide area network (WAN) by means of a control channel to the Application Service Provider Managed Applications and Platform. The Application Service Provider Managed Applications and Platform includes a platform management logic module that, with other programming in the Platform and the ASM, allows the managed application service provider to control the hardware elements of the UNA-DA in addition to any other relevant application services logic or hardware that may reside on the user premises. For example, this programming enables a managed application service provider to control and manage the hardware elements on the UNA-DA to ensure proper use and allocation of the UNA-DA's processing, memory, storage, and bandwidth, to monitor local hardware security and generate needed alarms or protection sequences, and to prioritize applications based on a set of established policies. The user would have control over specific parameters of application services obtained through the UNA-DA, through the User Interface and Platform to Managed Applications (User Controlled Logic) shown in FIG. 2. These parameters allow the user to control the local behavior of the interfaces and to configure the specific applications to accommodate the user network as configured by the user and to implement the user preferences for those applications.

Hence, FIG. 2 illustrates the logical architecture of the software and hardware of the UNA-DA in the form of a multi-services applications gateway device 10, together with a network service provider termination apparatus for broadband connection to a wide area network in this case implemented by the NSP-TA. The gateway device 10 is an application delivery apparatus, for delivering application services to endpoint devices using network layer communications through the network termination apparatus and the wide area network. The drawing also illustrates relevant demarcations between functionalities of the gateway device and termination, which delineate control/management access. The arrangement of the ASL and ASE logic between the two demarcations and the attendant logical demarcations in management access to the hardware resources at the premises result in significant management control by the application service provider and relieve the user of significant burdens in arranging and configuring the systems/services at the premises. Hence, we will consider the demarcations and the resulting relationships to the provider and the user at the various layers, in more detail.

As outlined above, the logical Network Service Provider Demarcation is formed at the edge of the wide area network (WAN) at the user premises, that is to say between the WAN and the equipment in the user premises. The arrows at the bottom of FIG. 2 show that the area covered to the LEFT of the Network Service Provider Demarcation (as depicted by the lower arrow on the left of vertical plane) is the Network Service Providers responsibility. From the perspective of a network service provider, anything to the RIGHT of that first demarcation (as depicted by the lower arrow on the right of the vertical plane) normally would be the customer's responsibility. As shown, this separation at the first demarcation includes delineation among the hardware elements for the NSP-TA.

As shown in FIG. 2, the application services layer also defines an Application Service Provider Demarcation, which extends through the hardware modules on the “Hardware Components” plane as well as the programming in the logical application services plane. In this way, the drawing depicts those modules that are under the responsibility of Application Service Provider (as depicted by the top middle bi-directional arrow). On the logic plane, the user can interact with the managed services through the Application Services Interface function 140, and the Application Service Provider can interact with the Network Service Providers managed Applications through the Network Service Provider Managed Application function. This is an optional function but it helps show how the UNA-DA can interface with Network devices from a network services provider, and provide a unified application interface to both hardware elements (NSA-TA, UNA-DA). This management relationship is represented by a dotted line on the logic layer between the Platform Management Logic module 110 and the network service provider management application in the NSP-TA. In effect, the application service provider can “manage” the NSP-TA for the user, even though it is not the application service provider's hardware. In the case where the application service provider is a network service provider as well (the NSP-TA is the application service providers own hardware), then it would work in practically the same way.

FIG. 2 also shows how the programming effectively partitions the hardware at the Application Service Provider Demarcation, which gives the application service provider the ability to provide a managed Peer-2-Peer private service that will enable that provider to use the UNA-DA for performing distributed computing, search, indexing, file backup, sharing, etc., all managed and controlled by the providers service management center.

The arrows at the top of FIG. 2 thus show the delineations in management responsibility created by the two logical demarcations. As at the bottom, the area covered to the LEFT of the Network Service Provider Demarcation (as depicted by the upper arrow on the left of first vertical plane) is the Network Service Provider's responsibility. Anything to the RIGHT of that second demarcation plane (as depicted by the upper arrow on the right of the second vertical plane) would be the customer's responsibility. However, the logic and hardware in the NSP-TA between the two vertical planes (as depicted by the upper arrow on the left of second vertical plane) is the Application Service Provider's responsibility. As noted above, a logical interface may be provided to the NSP-TA may enable the Application Service Providers to assume the user's responsibility in managing the premises side of the NSP-TA as depicted by the upper arrow on the right of the first vertical plane.

To identify the separation of, and distinguish between, the programming and hardware components subject to control by the application service provider and those subject to control by the user premises, FIG. 2 identifies a dividing line across the logical elements of the UNA-DA, and a corresponding dividing line across hardware components, referred to as the Applications Service Provider Demarcation. The Applications Service Provider Demarcation is flexible in that it may extend logically through the Application Services Interface (and, in a hardware context, through the Network Interface) to other devices that are under the logical control of the Application Services Provider Managed Applications and Platform, given that “services” are not restricted to a specific hardware boundary.

There is no hard requirement for cross management between the UNDA-DA and the NSP-TA. Under this first scenario the user is responsible for making the configuration changes in the specific user controlled logic modules in order to get the two devices to communicate with each other. Optionally the two sub-systems can be combined together, either physically in one hardware device, or logically as two separate hardware devices, but having one managed interface.

As noted, the two hardware regimes described above (NSP-TA and the UNA-DA) may be combined into one managed hardware platform and, thereby, replace the need for the user to have access to the User Premises Network Interface with the logic residing in the Platform Management logic module of the Application Service Provider Managed Applications and Platform (compare to above-discussed FIG. 10). This would in effect replace the “user” access with a managed “machine” access, for aspects of the NSP-TA, as well as aspects of the application services offered through the UNA-DA. Thus, the combination creates an integral gateway device providing both network service and application services, under centralized management. Although integrated, network interconnect functions of the NSP-TA may still be managed by the network service provider, as in the example of FIG. 2. Those skilled in the art will readily see additional combinations and configurations for the hardware comprising the NSP-TA and the UNA-DA. For example, in a further embodiment, all the hardware dedicated to the Network Service Provider Interface may reside and be integral with the hardware comprising the UNA-DA. Thus, the hardware for the WAN interface may reside on the UNA-DA.

The composition of the premises gateway device 10, earlier described with reference to FIG. 2, is now described in greater detail with reference to that drawing together with FIGS. 3A-3C. FIG. 2 illustrates the relationship of the demarcations to hardware and software of the gateway device 10 and an associated NSP-TA device providing the wide area network termination at the user premises. As shown in FIGS. 3A and 3B, the gateway device 10 utilizes a layered architecture, which enables the encapsulation of similar functionality and the minimization of dependencies between functions in different layers. FIG. 3A shows the lower portion of the layered architecture, and FIG. 3B shows the upper portion of the layered architecture. The completed set of layers can be conceptualized as if FIG. 3B was combined with FIG. 3A, with the layers of FIG. 3B above those of FIG. 3A. FIGS. 2, 3A and 3B also depict exemplary functionality (hardware and logical) resident in each of the layers.

The layers include a hardware layer 102, and device driver software 104 for allowing the processor to operate other hardware elements of the gateway device 10. FIG. 3C is a functional block diagram illustrating interconnection of exemplary elements of the hardware layer 102.

The logical elements of the NI Layer residing on the gateway device 10 are found in the Hardware Drivers 104, which govern the operation of the Hardware Components 102. The processor runs an operating system shown at layer 106, which plays a role in each of the NI, NF, AS and Platform Management Layers (FIG. 1). The layered architecture 100 also includes software for systems services 108 and for the platform management layer shown at 110 in this drawing. Logical elements represented by the NF Layer depicted in FIG. 1 are comprised of elements from the system services 108. In a similar fashion, the Platform Management Layer depicted in FIG. 1 is implemented in the exemplary architecture of FIGS. 2, 3A and 3B by the platform modules 109 and the platform management layer 110.

Particular logical elements comprising the ASL and ASE functionalities of the AS Layer represented in FIG. 1, and that reside on the gateway device 10 (predominately in the Application Service Provider Managed Applications and Platform of the UNA-DA shown in FIG. 2) are depicted in FIG. 3B, and comprise logical elements from each of services framework 120 and application services 130. The layered architecture facilitates reuse or sharing of logic across the layers to provide a managed service framework 120. The service management functionality provided by the framework 120 enables deployment of new services as pluggable modules comprising computer readable instructions, data structures, program modules, objects, and other configuration data, in a plug and play fashion. The layered service architecture additionally provides the gateway device 10 with intra-process communication and inter-process communication amongst the many services and modules in the service framework layer 120 that enables the provisioning, management and execution of many applications and services 130, depicted e.g. services A, B . . . N at the gateway device 10. Additionally provided are the application service interfaces 140 that enable communications from user endpoint devices with service environments. In that regard, the interfaces 140 enable the application service logic 130 to act as an appropriate server with respect to client device application or service functionality of the endpoint devices. The application service interfaces 140 also enable corresponding interfaces for the application services with aspects of service environments implemented outside the user premises. In that regard, the interfaces 140 enable the application service logic 130 to act as an appropriate client, for extending the application or service related communications to a server accessed via the wide area network 99, such as a server of the service management center 50. For example, the gateway device may appear as a SIP server to a SIP client in an end point device, e.g. for a VoIP telephone service; but the gateway device will appear as a SIP client with respect to some related functions provided by a server (such as a SIP directory server) provided by the service management center 50.

FIG. 2 thus depicts a high level service framework upon which are built services, e.g. downloaded via the service management center network 50 and a wide area network as packages that are developed and offered by a service entity for customers. These services may be offered as a part of a default service package provisioned and configured at the gateway device 10, or provisioned and configured subject to user subscription and may be added at any time as plug-in service modules in cooperation with the service management center, as discussed later. It is understood however, that while the gateway device 10 includes much of the intelligence or service logic for providing various services, it is also possible that for some services, some or all of service logic may reside in the service management center network and/or with a third party provider.

As shown, the base support layer 102 comprises hardware components including a processor device 152, e.g. a system on chip central processing unit (“CPU”) that includes processing elements, digital signal processor resources and memory. The CPU 152 is also coupled to a random access memory or “RAM” (see FIG. 3C) and additionally, non-volatile hard drive/disk magnetic and/or optical disk memory storage 154. Generally, the above-identified computer readable media provide non-volatile storage of computer readable instructions, data structures, program modules, objects, service configuration data and other data for use by the gateway device. The non-volatile hard drive/disk magnetic and/or optical disk memory storage 154 may be partitioned into a network side which is the repository for storing all of the service logic and data associated with executing services subscribed to by the user, and, is invisible to the user, and, a user side for storing user generated content and applications in which the user has visibility. Although not shown, the CPU 152 may be coupled to a microcontroller for controlling a display device.

Additional hardware components include one or more Ethernet LAN and WAN interface cards 155, 156 (e.g. 802.11, T1, T3, 56 kb, X.25, DSL or xDSL) which may include broadband connections (e.g. ISDN, Frame Relay, ATM, Gigabit Ethernet, Ethernet over SONET, etc.), wireless connections, or some combination of any or all of the above. The card 155 referred to as the LAN interface card provides data communication connectivity within the user premises, essentially, for communication via a user premises network 60 with any endpoint devices operating within the premises. The card 156 referred to as the WAN interface card provides data communication connectivity for the gateway device 10 and endpoint devices communicating through the device 10, with the wide area IP network 99. For additional or alternative customer premises communications, the hardware components 102 may also include one or more USB interfaces 158; and for additional or alternative communications with the wide area network, the hardware components may also include the PCMCIA EvDO interface card 160.

A data encryption/decryption unit 162 is additionally provided as part of the architecture for providing data security features. A watchdog timer element or like timer reset element 164 is provided as is one or more LED devices 166 for indicating status and other usable information to users of the gateway device 10.

The gateway device provides an in-premises footprint enabling the service connectivity and local management to client(s). The implementation of functions and the related control such as a router (with quality of service (QoS)), firewall, VoIP gateway, voice services and voice mail may be embodied and performed within the CPU 152.

The discussion of the gateway hardware layer above and the illustration thereof in the drawings provides a high-level functional disclosure of an example of the hardware that may be used in the gateway device. Those skilled in the art will recognize that the gateway device may utilize other hardware platforms or configurations.

Continuing, as shown in FIG. 3A, the device driver layer 104 comprises a multitude of driver interfaces including but not limited to: a PCMCIA driver 104a, for enabling low level communication between the gateway CPU 152 and the PCMCIA network interface card wireless interface, an IDE driver 104b for enabling low level communication between the gateway CPU 152 and the local mass memory storage element, and LAN/WAN drivers 104c for enabling low level communication between the gateway CPU 152 and the respective network interface cards 155 and 156. The exemplary driver layer also includes an LED driver/controller 104d for driving LED(s) 166, a USB driver 104e allowing CPU 152 to communicate via USB interface 158, and an 802.11b/g (or n) wireless network driver 104f for allowing the CPU 152 to communicate via the access point 62. The drivers provide the logical connectivity between the low level hardware devices 102 and the operating system 106 which controls the execution of computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services for the gateway device. With respect to the operating system 106, the gateway computing may support any embedded operating system, any real-time operating system, any open source operating system, any proprietary operating system, or even any operating systems for mobile computing devices as long as the operational needs of the client discussed herein below can be met. Exemplary operating systems that may be employed include Windows®, Macintosh®, Linux or UNIX or even an embedded Linux operating system. For instance, the gateway device 10 may be advantageously provided with an embedded operating system 106 that provides operating system functions such as multiple threads, first-in first-out or round robin scheduling, semaphores, mutexes, condition variables, message queues, etc.

Built upon the system operating system 106 is a system services support layer 108 providing both client-like and server-like functions that enable a wide range of functionality for the types of services capable of being managed by the gateway device 10. For instance, there is provided a Dynamic Host Configuration Protocol (DHCP) client and server software modules. The DHCP client particularly requests via a UDP/IP (User Datagram Protocol/Internet Protocol (e.g. Ipv4, Ipv6, etc.) configured connection information such as the IP address that the gateway device 10 has been dynamically assigned by a DHCP service (not shown), and/or any the subnet mask information, the gateway device should be using. The DHCP server dynamically assigns or allocates network IP addresses to subordinate client endpoints on a leased, e.g. timed basis. A Virtual Private Network (VPN) client may communicate via a proxy server in the service control network 50, according to a VPN protocol or some other tunneling or encapsulation protocol. An SMPT client handles incoming/outgoing email over TCP, in accordance with the Simple Mail Transfer protocol. A Network Time Protocol (NTP) (RFC 1305) generates and correlates timestamps for network events and generally provides time synchronization and distribution for the Internet. A Domain Name Server (DNS) client and server combination are used by the IP stack to resolve fully-qualified host or symbolic names, i.e. mapping host names to IP addresses.

An HTTP(S) server handles secure Hypertext Transfer Protocol (HTTP) (Secure Sockets Layer) communications and provides a set of rules for exchanges between a browser client and a server over TCP. It provides for the transfer of information such as hypertext and hypermedia, and for the recognition of file types. HTTP provides stateless transactions between the client and server.

A Secure File Transfer Protocol (SFTP) client and server combination govern the ability for file transfer over TCP. A SAMBA server is an open source program providing Common Internet Files Services (CIFS) including, but not limited to file and print services, authentication and authorization, name resolution, and service announcement (browsing). An EvDO/PPP driver includes a Point-to-Point Protocol (PPP) daemon configuration for wireless broadband services. A PPPoE (Point-to-Point Protocol over Ethernet) client combines the Point-to-Point Protocol (PPP), commonly used in dialup connections, with the Ethernet protocol; and it supports and provides authentication and management of multiple broadband subscribers in a local area network without any special support required from either the telephone company or an Internet service provider (ISP). The gateway device 10 is thus adapted for connecting multiple computer users on an Ethernet local area network to a remote site through the gateway and can be used to enable all users of an office or home to share a common Digital Subscriber Line (DSL), cable modem, or wireless connection to the Internet. A Secure Shell or SSH server implemented with HTTP protocol provides network protocol functionality adapted for establishing a secure channel between a local and a remote computer and encrypts traffic between secure devices by using public-key cryptography to authenticate the remote computer and (optionally) to allow the remote computer to authenticate the user.

Additionally provided as part of the system services layer 108 is intelligent routing capability provided by an intelligent router device 185 that provides Quality of Service (QoS, guaranteed bandwidth) intelligent routing services, for example, by enforcing routing protocol rules and supporting unlimited multiple input sources and unlimited multiple destinations and, particularly, for routing communications to networked digital endpoint devices subordinate to the gateway. A central database server 183 handles all of the database aspects of the system. For example, the database server 183 maintains and updates registries and status of connected digital endpoint devices, maintains and updates service configuration data, services specific data (e.g. indexes of backed-up files, other service specific indexes, metadata related to media services, etc.) and firmware configurations for the devices. The database server 183 may also store billing and transaction detail records and performance diagnostics. The database server logic 183 also satisfies all other database storage needs as will be described in greater detail herein.

Referring back to FIGS. 2 and 3A, built on top of the system services layer 108 is the platform module layer 109. The platform module layer 109 provides a software framework for operating system and communications level platform functionality such as CPU management; Timer management; memory management functions; a firewall; a web wall for providing seamless WWW access over visual displays via access technologies enumerated herein, e.g. HTTP, SMS (Short Messaging Service) and WAP (Wireless Access Protocol); QoS management features, bandwidth management features, and, hard disk drive management features. The layered architecture further provides a platform management layer 110 as shown in FIG. 3B, which together with the platform modules 109 implement the platform management layer/logic discussed earlier (with regard to FIG. 1). In the layered architecture, the platform management layer 110 (and elements shown above it in FIG. 3B) is built upon the platform modules 109.

The features/functions in the layer 110 include a platform manager module which will implement unique rules based notification services. On operational failure, for example, when one of the components or services fails, the platform manager would detect this failure and take appropriate action such as implement a sequence of rules to provide notification to a user. A scheduler module manages scheduled device maintenance, managing scheduled services, e.g. back-up services, etc. The layer 110 also includes a diagnostics module and a firmware upgrades management module for managing firmware upgrades. A resource management module manages system resources and digital contention amongst the various resources, e.g. CPU/Bandwidth utilization, etc. A display management module and a logger management module store and track gateway log-in activity of users and applications, e.g. voice call logs, at the user premises. The platform management layer 110 in concert with resource and service management components enforces the separation of network side managed service control and user side delegations depending upon service subscriptions and configurations. For example, the platform and resource management encompass rules and guidelines provided according to subscribed services that act to enforce, manage and control input/output operations, and use of hard drives space etc. A demarcation point, logically depicted as the Application Service Provider Demarcation in FIG. 2, is thus defined that provides a hard line between what is “owned by” the customer and what is “owned by” the application service provider.

The logical platform management layer 110 allows for inter-layer allocation of local resources. This function guarantees access between the application service/management logic implemented at the higher layers in the gateway device 10 and the applications service management function in the service management center 50, by assuring that the local user premises hardware and software modules are functioning at a required state (CPU and memory usage, bandwidth usage, QoS settings, etc.). The platform manager is also responsible for implementing that part of the managed application services to be performed by the gateway device. In that regard, the platform manager secures and manages the overall hardware platform, given that in this scenario, the network function layer and the application service layer reside on one hardware platform. This secure hardware platform provides a robust and secure operating environment for the application services layer. So, to establish a secure and robust hardware operating environment, the platform management layer must interface with all the layers above it and allow for bi-directional management information flow among all of the functions.

Referring back to FIGS. 2 and 3B, built on top of the platform management layer 110 is the Services Framework 120, which provides a library of application support service processes that facilitate data collection and data distribution to and from the multimedia endpoint devices. The application support service processes include, but are not limited to: an authentication manager for use in authenticating devices connected to the gateway device; a billing manager for collecting and formatting service records and service usage by endpoint devices, e.g. calls, back-up services etc.; a fault manager for detecting and managing determined system and/or service faults that are monitored and used for performance monitoring and diagnostics; a database manager; a control channel interface via which the gateway initiates secure communications with the operations support infrastructure; a configuration manager for tracking and maintaining device configuration; a user manager; a service manager for managing service configuration and firmware versions for subscribed services provided at the gateway device; and a statistics manager for collecting and formatting features associated with the gateway device. Statistics may relate to use of one or more services and associated time-stamped events that are tracked.

Built on top of the Services Framework layer 120 is the Application Services layer 130 providing library of user application services and application support threads including, but not limited to: file sharing functionality; backup services functionality; home storage functionality; network device management functionality; photo editing functionality; home automation functionality; media services functionality; call processing functionality; voice mail and interactive voice response functionality; presence and networking functionality; parental control functionality; and intelligent ads management functionality. The multi-services applications gateway 10 further provides application service interfaces 140 that are used to enable a variety of user applications and communications modalities.

For instance, the SIP Interface 141 is an interface to the generic transactional model defined by the Session Initiation Protocol (SIP) that provides a standard for initiating, modifying or terminating interactive user sessions that involve one or more multimedia elements that can include voice, video, instant messaging, online games, etc., by providing access to dialog functionality from the transaction interface. For instance a SIP signaling interface enables connection to a SIP network that is served by a SIP directory server via a Session Border Controller element in the service management center.

The Web Interface 142 enables HTTP interactions (requests and responses) between two applications. The Web services interface 149 provides the access interface and manages authentication as multi-services gateway devices access the service management center via web services. The IM Interface 144 is a client that enables the multi-services gateway device 10 to connect to one or more specific IM network(s). As further shown in FIG. 3B, the UpNp (Universal Plug and Play) interface enables connectivity to other stand-alone devices and PCs from many different vendors.

The XMPP interface 145 is provided to implement the protocol for streaming (XML) elements via the gateway device 10, in order to exchange messages and presence information in close to real time, e.g. between two gateway devices. The core features of XMPP provide the building blocks for many types of near-real-time applications, which may be layered as application services on top of the base TCP/IP transport protocol layers by sending application-specific data qualified by particular XML namespaces. In the example, the XMPP interface 145 provides the basic functionality expected of an instant messaging (IM) and presence application that enable users to perform the following functions including, but not limited to: 1) Exchange messages with other users; 2) Exchange presence information with other devices; 3) Manage subscriptions to and from other users; 4) Manage items in a contact list (in XMPP this is called a “roster”); and 5) Block communications to or from specific other users by assigning and enforcing privileges to communicate and send or share content amongst users (buddies) and other devices.

As noted, FIG. 3C provides a functional block diagram of exemplary elements of the hardware layer 102. For example, a system on a chip provides the CPU 152 and associated system components. The CPU 152 is also coupled to a random access memory (“RAM”) and flash memory. The system on a chip also includes a hard drive controller for controlling a hard disk drive, and together the controller and drive form the hard disk example of the storage 154. An Ethernet switch and associated LAN port(s) provide the Ethernet LAN interface 155; and the Ethernet switch and associated WAN port provide a landline implementation of the WAN interface 156L, for connection to a broadband modem or the like implementing the NSP-TA. The WAN interface may also be wireless, as implemented at 156w for example by a wireless WAN module and associated antenna. An example of such an interface would be the EvDO interface discussed earlier. If the gateway device uses the wireless WAN interface 156w, there would be no separate NSP-TA.

In the example of FIG. 3C, a USB controller in the system on a chip and one or more associated USB ports provide the USB interface 158. The USB interface 158 may provide an alternate in-premises data communication link instead of or in addition to the wired or wireless Ethernet LAN communications. The system on a chip includes a security engine, which performs the functions of the data encryption/decryption unit 162.

The hardware layer 102 may also include an option module. The UNA-DA hardware components at layer 102 have multiple interfaces for connection to such an option module. These interfaces, by way of example, could be a data bus (e.g. PCI, etc.), network interface (e.g. Ethernet (RJ45), MoCA/HPNA (Coax)) and Power feeds. The option module allows additional functionality to be added to the base UNA-DA functionality of the gateway device. For example, this additional functionality could be everything from support for a variety of extra Wide Area Network Interfaces (e.g. xDSL, DOCSIS, Fiber (PON), Cellular Packet, WIMAX, etc.), Media Processing (e.g. Cable TV termination, Digital Video Recording, Satellite TV Termination, etc.), to Voice Processing (FXS, FXO, Speech Detection, Voice to Text, etc.). The option module may have its own standalone CPU, Memory, I/O, Storage, or provide additional functionality by its use of the CPU, Memory, I/O, and storage facilities off of the main hardware board. The option module may or may not be managed directly by the Platform Management of the UNA-DA.

Those skilled in the art will recognize that functions of the service management center, which reside in the Application Service Management node on the Service Provider Network, as depicted in FIG. 1, may be implemented in a variety of different ways, on one or more computer hardware platforms connected to 10 gateway devices via a wide area network. FIG. 4 depicts an example wherein the implementation is on Internet or other wide area IP network 99. The example uses a distributed processing approach, in which the elements/platforms implementing the service management center are interconnected for communication and for wide area communication, and in this way, those elements form a network 50 for implementing the service management center.

As shown in FIG. 4, the service management center network, through the logical capabilities earlier depicted in FIG. 4 as the ASM module of the ASD Platform at the AS Layer, manages application services for a number of gateway devices 10, 10.sub.1 . . . 10.sub.n located at various users' premises. These application services, shown as ASL and ASE in FIG. 1, implement their functionality within the Application Services Layer (FIG. 1), through programming that resides, at least in part, within the Application Service Provider Managed Applications and Platform of the UNA-DA (FIG. 2). As shown in FIG. 4, secure connectivity to the service management center network 50 is provided, in one embodiment, via a WAN Termination interface, such as Ethernet WAN 53 over a broadband connection via the public Internet 99, or, for example, via a wireless EvDO (Evolution Data Optimized) Internet data interface embodied as a PCMCIA (personal computer memory) wireless card 56. When the WAN Termination interface 53 is used, for example, it may provide connectivity to a broadband modem serving as the NSP-TA of FIG. 2, either as a separate unit or on a board included within the gateway device 10. If the wireless WAN interface is used, there may be no physical NSP-TA device, and the logic of the gateway device would implement functions of the NSP-TA as well.

As will be described in greater detail herein below, the service management center 50 generally provides a communications and processing infrastructure for supporting the variety of application services and related communications residing at the gateway devices 10, 10.sub.1 . . . 10.sub.n. In an exemplary embodiment, this infrastructure may be configured to provide a secure environment and may be IP-based. Preferably, this support architecture is designed for high availability, redundancy, and cost-effective scaling.

The secure platform for building and providing multiple application services for digital endpoints associated with a gateway device requires connectivity between the gateway device 10 and each of a user's devices (referred interchangeably herein as “endpoint devices” or “digital endpoint devices”). This connectivity may be provided by implementation of one or more USB ports (interfaces) 13, a wired Local Area Network connection such as provided by an Ethernet local area network (LAN) interface 16, or, a wireless network interface via a WiFi LAN access point 62 provided, for example, in accordance with the I.E.E.E. 802.11b/g/n wireless or wireless network communications standard. These physical interfaces provide the required network interconnectivity for the endpoint devices to connect to the multiple application services. Although not shown in FIG. 4, this connectivity between digital endpoint devices and the gateway device may be accomplished by other means, including, by way of example, through of a virtual private area network connection accessed through a WAN interface.

That is, the gateway device 10 interfaces with digital endpoint devices including, but not limited to: a home automation networking device 20 (e.g. X10, Z-Wave or ZigBee) for wired or wireless home network automation and control of networked home devices such as a switch controller 22, sensor devices 23, automatically controlled window blinds 24, a controlled lighting or lamp unit 25 etc., individual or wired or wireless network of personal computing (PC) and laptop/mobile devices 30a, . . . , 30c that serve as file sources, control points and hosts for various other client endpoints, one or more television display devices 32 including associated set top boxes (STB) 35a or digital media adapters (DMA) 35b, one or more VoIP phone devices (e.g. SIP phones) 40, or other devices (not shown) that convert IP interfaces to PSTN FXO and FXS interfaces.

As noted earlier, the gateway device 10 may provide an interface 35b to the Digital Media Adapter (DMA) for television (TV) 32, which enables bidirectional wireline or wireless communication. This interface supports several functions for multiple services including, but not limited to: media (e.g., video and music) by enabling the transfer of media (e.g., video and music) to the TV; voice services, by providing for Called Line ID and for voice mail control; and provide Home Automation Services including status and control of networked home automation devices. The DMA element 35b converts audio and video (optionally) to a format suitable for a TV. In addition, the Digital Media Adapter 35b may be capable of receiving context-sensitive commands from a remote control device (not shown) and forwarding those commands to the gateway device 10. This enables the use of menus on the TV 32 for controlling application services and various features functions thereof, as offered by the gateway device 10. For example, the Media Adapter/TV combination is able to provide the following features including, but not limited to: display of media; media control functions, when enabled (FF, REW, STOP, PAUSE, etc.); display of Calling Line Identification (CLID); control of voicemail; picture viewing; control of home automation; and user functions for the gateway device 10.

A Set Top Box 35a as shown in FIG. 4 also may handle media format conversion (for example NTSC to ATSC television RF signals), digital decryption and other DRM (digital rights management) functions, and Video On Demand Purchases, etc. The Set Top Box/TV combination may thus enable, by way of example: Media format conversion (for example NTSC to ATSC); decryption; other DRM functions (such as expiry of leases), prohibition of copying to digital outputs, function restriction, etc.; Video On Demand Purchases; and media control functions (e.g., FF, REW, STOP, PAUSE, etc.).

Whether provided by the DMA interface 35b and the TV 32 or by the set-top-box 35a and the TV 32, the communications to and from the TV provide a user interface for interaction with the gateway device 10. The programming of the gateway device supports, among other things, a graphical user interface (GUI) via the TV, sometimes referred to as the “ten-foot” interface.

With respect to PCs interfacing with the gateway device 10, PCs may serve as, among other things, file sources, control points and hosts for various software clients. Thus, the PC programming may work in conjunction with the ASL and ASE programming of the gateway device. Together, the PC programming and the ASL and ASE programming provide a more comprehensive and robust user experience. The gateway device 10 may further provide a bidirectional wireline or wireless interface 35c to a PC device 30b for supporting the transfer of media (e.g., video and music) to the computer for storage and viewing; for supporting voice services, e.g., by providing for calls from SIP soft clients; for file sharing, file back-up and home storage and home automation control functions. The access point 62 offers wireless data communications with a PC 30c. The gateway device interface through any PC may provide for the bidirectional moving of files, and status and control for the endpoint devices, including for example, status and control of networked home automation devices. In addition, using the PC interface, users may, for example, share files on the gateway devices, back-up or transfer files to the gateway devices or other storage; access personal page for notifications, RSS, shared photos, voicemail, etc. In addition to the IM and SIP capabilities of the gateway device, as described more below, PCs may also serve as a host for IM and SIP soft phone clients and other client devices. The client-server interaction of the PC with the application service logic of the gateway device 10 offers an alternative GUI for at least some of the services. The PC based GUI is sometimes referred to as the “two-foot” interface.

Although not shown in FIG. 4, other digital endpoint devices for which connectivity may be established with the gateway device 10 include, but are not limited to: personal music or media players, hi-fi audio equipment with media streaming capability, game stations, Internet radio devices, WiFi phones, WiFi or other wirelessly enabled digital cameras, facsimile machines, electronic picture frames, health monitors (sensor and monitoring devices), etc.

As described in greater detail herein, the gateway device 10 includes both a hardware and software infrastructure that enables a bridging of the WAN and LAN networks, e.g. a proxy function, such that control of any digital endpoint device at the premises from the same or remote location is possible via the gateway device 10 using, optionally, a secure peer and presence type messaging infrastructure or other communications protocols, e.g. HTTPS. For example, via any IM—capable device or client 80a, 80b respectively connected with an Instant Messaging (IM) or XMPP (Extensible Messaging and Presence Protocol) network messaging infrastructure, e.g. IM networks 99a, 99b such as provided by Yahoo, Microsoft (MSN), Skype, America Online, ICQ, and the like, shown for purposes of illustration in FIG. 4, a user may access any type of functionality at a subordinate digital endpoint device at the premises via the gateway device 10 and service management center 50 by simple use of peer and presence messaging protocols. In one exemplary embodiment, a peer and presence communications protocol may be used such as Jabber and/or XMPP. Particularly, Jabber is a set of streaming XML protocols and technologies that enable any two entities on the Internet to exchange messages, presence, and other structured information in close to real time. The Internet Engineering Task Force (IETF) has formalized the core XML streaming protocols as an approved instant messaging and presence technology under the name of XMPP (Extensible Messaging and Presence Protocol), the XMPP specifications of which are incorporated by reference herein as IETF RFC 3920 and RFC 3921. Thus, the gateway device is provided with functionality for enabling a user to remotely tap into and initiate functionality of a digital endpoint device or application at the premises via the IM-based messaging framework. In addition, the gateway device 10 and network connectivity to the novel service management center 50, provides, in a preferred embodiment, a secure peer and presence messaging framework, enabling real-time communications among peers via other gateway devices 10.sub.1 . . . 10.sub.n. For instance, the device 10 provides the ability to construct communication paths between peers with formal communications exchanges available between, for example, one gateway device 10.sub.1 at a first premises and a second gateway device 10.sub.n located at the remote premises. Thus, such an infrastructure provides for content addressing, enabling peers through remote gateway devices 10.sub.1 . . . 10.sub.n. to supply and request content such as files, media content or other resources of interest to a community of interest.

As noted above, the novel system architecture allocates the logical functionality of the ASD Platform (FIG. 1) between the gateway device 10 and the service management center 50 within an environment that enables communication and feedback at the AS Layer (FIG. 1) between the gateway device 10 and service management center 50. Thus, the gateway device 10, when operable with the service management center 50, makes possible the management of services for the digital home and facilitates the easy addition of new services or modification of existing services. Such services may include, for example, facility management (home automation), media content downloading and Digital Rights Management (DRM), device updates, data backups, file sharing, media downloading and transmission, etc., without the intermediary of a plurality of external service providers who may typically provide these individual services for every digital endpoint device in the home or premises. The programming for these services resides in the Application Service Provider Managed Applications and Platform of the UNA-DA (FIG. 2). That is, as earlier shown, the gateway device 10 is integrated with hardware and software modules and respective interfaces that handle all aspects of home automation and digital endpoint service and management for the home in a manner without having to rely on external service providers and, in a manner that is essentially seamless to the user. This, advantageously is provided by the service management center 50 which is able to access regions of the gateway device 10 that are not accessible to the user, e.g. for controlling the transport and storing of digital content and downloading and enabling service applications and upgrades and providing largely invisible support for many tasks performed by users.

For example, with the robust capabilities of the Application Service Provider Managed Applications and Platform (FIG. 2), the gateway device 10 is capable of handling all aspects of the digital home communications, e.g. IP, voice, VoIP, phone connectivity. In this example, the service logic located and stored at the gateway device 10 may provide soft-switch functionality for implementing call-processing features at the premises (rather than the network) for voice communications, and enabling management of other service features to be described. With the provision of central office type call services and other service features provided at the gateway devices 10.sub.1 . . . 10.sub.n, a distributed soft-switch architecture is built. The ASM logical functionality of the service management center 50, in cooperation with the ASE logical functionality of the gateway device, may, among other things, provide, manage and regulate, for example, service subscription/registration, authentication/verification, key management, and billing aspects of service provision, etc. With all of the service logic and intelligence residing at the gateway device, a service provider can offer customers a broad spectrum of services including, but not limited to: media services, voice services, e.g. VoIP, automated file backup services, file sharing, digital photo management and sharing, gaming, parental controls, home networking, and other features and functions within the home or premises (e.g. home monitoring and control). Users can access their content and many of the solution's features remotely. Moreover, software updates for the in-home devices that require updating are handled in an automated fashion by the system infrastructure. The service management center infrastructure additionally provides a web interface for third-party service providers to round out the service solutions provided at the gateway device for the premises. For example, a third-party service provider other than the managed service provider associated with the service management center may be allowed access through the infrastructure to particular endpoint devices to provide additional services such trouble shooting, repair and update services.

For the in-home services, the multi-services gateway device 10 connects the various service delivery elements together for enabling the user to experience a connected digital home, where information from one source (for example, voicemail) can be viewed and acted on at another endpoint (for example, the TV 32). The multi-services gateway device 10 thus hosts the various in-home device interfaces, and facilitates the moving of information from one point to another. Some of the in-home endpoint device processing duties performed by the gateway device 10 include, but are not limited to: 1) detecting new devices and provide IP addresses dynamically or statically; 2) functioning as a (Network Address Translator) NAT, Router and Firewall; 3) providing a centralized disk storage in the home; 4) obtaining configuration files from the service management center and configuring all in-home devices; 5) acting as a Registrar for SIP-based devices; 6) receiving calls from and delivering calls to voice devices; providing voicemail services; 7) decrypting and securely streaming media having digital rights management (DRM) encoding; 8) distributing media to an appropriate in-home device; 9) compressing and encrypting files for network back-up; 10) backing-up files to the network directly from gateway device; 11) handling home automation schedules and changes in status; 12) providing in-home personal web-based portals for each user; 13) providing Parental Control Services (e.g. URL filtering, etc.); 14) creating and transmitting billing records of in-home devices including, recording and uploading multi-service billing event records; 15) distributing a PC client to PCs in the home, used in support of the various services such as monitoring events or diagnostic agents; 16) storing and presenting games that users and buddies can play; 17) delivering context-sensitive advertising to the endpoint device; and, 18) delivering notifications to the endpoint device; and, 19) enabling remote access through the web, IM client, etc. Other duties the gateway device 10 may perform include: service maintenance features such as setting and reporting of alarms and statistics for aggregation; perform accessibility testing; notify a registration server (and Location server) of the ports it is “listening” on; utilize IM or like peer and presence communications protocol information for call processing and file sharing services; receive provisioning information via the registration server; utilize a SIP directory server to make/receive calls via the SBC network element to/from the PSTN and other gateway device devices; and download DRM and non-DRM based content and facilitating the DRM key exchanges with media endpoints.

While the gateway devices 10 as described above are each equipped with various logic and intelligence for service features that enable the gateway devices to provide various integrated digital services to the premises, as described herein with respect to FIG. 3, the network-based elements of the service management center 50 supports and manages multi-services gateway devices, for instance, so as to control the accessibility to functionalities and service features provisioned in the gateway devices and the ability to communicate with other gateway devices and various digital endpoint devices connected thereto. These elements that support and manage the gateway devices 10 comprise the ASM module described above with reference to FIG. 1. These ASM elements may, for example, provide the necessary data to the ASE and ASL modules so that they may carry out their respective functions, oversee the overall integration and communication among all the modules and the services that are managed by the ASM, manages the overall security and integrity of the ASD, and maintains alarm, statistical, subscription and provisioning data, and data necessary for the integration of services from third-party service providers, e.g., media content aggregators.

Examples of various ASM functionalities performed at the service management center 50, from the Service Provider Network regime, include but are not limited to: service initialization of the gateway devices, providing security for the gateway devices and the network support infrastructure, enabling real time secure access and control to and from the gateway devices, distributing updates and new service options to the gateway devices, providing service access to and from the gateway devices and remote access to the gateway devices, but not limited to such. In support of these services, the service management center 50 provides the following additional services and features: authentication; multi-service registration; subscription control; service authorization; alarm management; remote diagnostic support; billing collection and management; web services access; remote access to gateway devices (e.g. via SIP or Internet/web based communications); reachability to access challenged gateway devices; software updates; service data distribution; location service for all services; SIP VoIP service; media services; backup services; sharing services; provisioning; gateway interfaces to other service providers (Northbound and peering); load balancing; privacy; security; and network protection.

The logical network architecture for the service management center network 50 delivering these capabilities is illustrated and described in greater detail in U.S. Provisional Application No. 60/882,865 Filed Dec. 29, 2006 entitled “A MULTI-SERVICES APPLICATION GATEWAY AND SYSTEM EMPLOYING THE SAME,” and of U.S. Provisional Application No. 60/882,862 Filed Dec. 29, 2006 entitled “SYSTEM AND METHOD FOR PROVIDING NETWORK SUPPORT SERVICES AND PREMISE GATEWAY SUPPORT INFRASTRUCTURE,” and the disclosures of the service management center network and its operations from those applications are entirely incorporated herein by reference.

With the gateway architecture implementing the Application Service Provider Demarcation (e.g. FIG. 2 and FIGS. 3A-3C), the demarcation in accessibility to hardware resources of the gateway device 10 delineates a portion of the storage accessible by a user via an endpoint device from an application service provider portion of the storage containing the application service programming and/or data of the application service provider. For example, the user of an associated endpoint device may be able to store and retrieve data files in the user accessible portion of the storage of the gateway device 10. The application service provider, in turn, can control storage and retrieval of data files in the application service provider portion via the of the wide area network as well as installation and configuration of various software/firmware logic modules. However, as outlined above, the user access to the logic and resources between the two demarcations is limited. The application service programming only provides a logical application service interface across the Applications Service Provider Demarcation, for delivery of one or more application services to an endpoint device. The user can obtain and use the application service and its features but cannot access the underlying application service logic or its configuration data. For example, the user of the associated endpoint device is prevented from accessing one or more of the data files in the application service provider portion of the storage media. For some service applications, the application service provider can allow storage and retrieval of data files in the application service provider portion via the wide area network, for other gateway devices. Also, the logical location of the demarcation line separating the portions of the storage is controllable by the application service provider, from the service management center 50, via the wide area network 99 and the second interface. To illustrate these points, it may be helpful to consider some examples.

FIG. 5A conceptually depicts the logical demarcation in a storage media, between a portion thereof accessible by the user and a portion thereof that is accessible and controlled by the application service provider. In the example, the delineation provides isolation of downloaded service logic and associated data for implementing services from service provider and/or downloaded content from a user generated content.

As shown in FIG. 5A, the gateway device 10 includes functionality for logically combining the storage available from its own internal and attached hard drive(s) 154, with any Network Attached Storage (NAS) device 158 available via the local area network (and/or possibly via the wide area network) to create a single virtual file system that consumers can use like a single drive. The gateway device 10 will automatically detect, mount and manage the connections to the NAS devices and add them to its own file system. Users of the gateway device 10 are thus presented with a single consolidated storage device that they can access just like another drive on their PC. Users will not be exposed to the underlying protocols and management features required to provide such a feature. Users no longer have to use each of the storage devices separately.

However, as further shown in FIG. 5A, a virtual demarcation 155 is enforced at the centralized disc storage device 154 of the gateway device 10, e.g., which may comprise one or more physical hard drives. The demarcation 155 is essentially the extension of the Application Service Provider Demarcation (FIG. 2) that extends through the gateway storage 154. With respect to the storage 154, the virtual demarcation 155 physically and logically isolates the storage partition or portion 156 where service logic and associated data for implementing services from the application service provider and/or downloaded media content controlled by that service provider are stored, from another partition or portion 157 where user generated data, e.g., user files, is stored. Thus, the portion 156 of storage 154 belongs to the application service provider and is accessible by the service management center 50. The application service provider can use the portion 156 for receiving logic and intelligence for the device 10, and backed-up user files, all of which is managed by the service control center 50 and enforced locally at the ASE logic in the gateway device 10. However, the other portion 157 of storage 154 is storage that is user accessible and includes a user accessible graphic user interface (GUI) which may be accessed by a digital endpoint device, e.g., a PC, programmed to enable visibility if granted to the user. Thus, the user is enabled to skew the demarcation point depending upon the amount of control granted or authorized to the user according to subscribed features and service configurations. However, the demarcation location is controlled by the application service provider. This separation within the gateway device 10 is an enabler for delivery of the service logic that resides on the device on the network side of the virtual demarcation. That is, the service provider offers all of its services upstream of this demarcation point; and the customer can choose which service is selected that is within the control of the service provider's network. Hence, the physical size of each partition is dynamic. It becomes possible to determine partition sizes on the hard disk at a low level, or to determine which file goes in which “virtual” partition, based on the type of file or a tag on the file.

While the service center 50 is responsible for placement of service modules and data beyond the demarcation 155, the gateway device 10 is equipped with certain functional elements such as encryption techniques, local directory obfuscation techniques and local enforcement to prevent user visibility beyond the demarcation 155 that belongs to the service provider unless the user is enabled with such visibility. The intelligence and service logic that is on the gateway device 10 is managed by the service center 50 and provides the logic to limit user access.

FIG. 5B illustrates the virtual demarcation 155 within storage 154 of the gateway device 10 located on the customer premises, and this drawings provides examples of how the location of the demarcation 155 is moveable. The logic allows the customer to skew the location of the demarcation, albeit, within limits enforced by the logic managed by the application service provider. The provider also can adjust the location of the demarcation within the storage 154 on gateway device 10. The demarcation within this device can occur on a physical storage medium, e.g., a hard disk drive 154 that has been sectored for different users, or in a virtual memory location, e.g. locations 155a, 155b or 155c, based on the service levels being offered, e.g. service A, service B or service C, respectively. This approach allows the customer more flexibility in manipulating the service rendered and services offered by the provider. By allowing the demarcation closer to the customer this allows more control of features from the customer and allows the service provider closer control of the customer infrastructure without owning it all. Thus, with this device in place, the new demarcation moves based on the service.

For an example of demarcation control, if some data is required to be stored, e.g., a downloaded movie, the customer can store it locally, securely locally, or securely remotely. While it is the customer's responsibility to do storage locally and securely locally, with the virtual demarcation, the service of providing locally secure data is now part of an offering of the service provider. While the data is still on site, the data is under control of the service provider and follows service agreements for that storage of data.

As another example of demarcation control, movies may be downloaded and stored at the service provider's side beyond the demarcation 155, as requested by a user via a user interface through an endpoint device communicating with the gateway device. This user interface, enabled via the user side of the Application Service Provider Demarcation of the gateway device 10, is accessed through a PC, a TV, and cell phone. After authentication, the user could select and prioritize movies to purchase for example, in compliance with the media content service provider. The choice of interfaces and amount of visibility by endpoint devices accessing this user interface may be optimally designed from a contention standpoint from the perspective of controls, security, network service control manageability, and cost. A selected movie is downloaded to the service center's portion 156 of the storage 154 as shown in FIG. 5A. Unless and until the user has purchased the movie for playback via an authentication process, that user will be prevented from accessing the content. Otherwise, the user may initiate streaming of the content directly to a digital endpoint device, e.g., a television, or will be granted permissions to download and play the movie according to the subscription with the media content provider as managed by the gateway device. If the user has purchased the movie, the movie may be transferred physically to the user storage portion 157 of the storage 154. Otherwise, the content may be temporarily tagged or copied, for local storage by the user at the user accessible portion of the demarcation point for playback at the user endpoint device.

Another example of demarcation control is the manipulation of features for a given service. Currently a subscription order is processed, and these features are manipulated within the service provider's network and sent down to the customer for provisional changes to equipment at the service center's side of the demarcation point. The location of the demarcation can be adjusted to meet storage space needs on either or both sides, as needed for various services offered to this user or even services provided to other users. Via a GUI established for the endpoint device when connected with the gateway device 10, when authenticated, files may be unlocked so the customer may locally manipulate services before and after the Application Service Provider Demarcation, thereby virtually shifting the point or location of the demarcation. Thus, a virtual demarcation allows the application service provider flexibility in offering different services and features. Examples of relevant services include, but are not limited to services such as: parental control, advertisement monitoring and replacement, home user habit monitoring, home channel monitoring, and back-up services.

In one service example, the gateway device 10 and service management center 50 provide a file management feature generally including functionality that enables a user to back-up files or content to a virtual memory storage area provided in the gateway device 10, and then subsequently forward the backed-up files to an external wholesale service provider providing the backup service. Thus, gateway storage device 10 provides the protected storage for user files and user content at its side of the demarcation point in a two-stage storage process: 1) storing the content across the virtual demarcation point (partition); and then, encrypting the content; and, 2) dispersing the stored content to other gateway devices, or at another storage location provided by the service center or by a partnered third party back-up storage service provider. This could be performed automatically, or on a scheduled basis. In such an example, after the file is encrypted (and encrypt is an option, not a requirement), the file may be moved to the Service Provider side of the Demarcation or it may stay on the user side of the Demarcation. The precise position is an implementation detail given by way of example. Also, if moved, the file could be taken out of the one partition (erased from the first partition), or it may merely “tagged” so that it has been “virtually” moved. These also are given by way of example, and those skilled in the art will recognize that other procedures may be used. The gateway device 10 knows where the pieces will be stored, based on the service configuration and subscription. Backup may be on a central host operated by the application service provider; or in an implementation discussed more below, the backup files and/or portions thereof may actually reside in the service provider's portion of storage in other gateway devices. The locations of devices that may back up content pieces are known at the network level, e.g., hardware IDs of each of the other gateway devices are known based on the unique identity of the device, and the mappings of the IP addresses of the devices that change dynamically are known at location servers provided by the service management center 50, so the location of backed-up content for a user is always known.

In a further aspect of the file-sharing service, the gateway device 10 and service management center 50 may provide a hosted service-virtual space on the centralized disk storage at the gateway device for users. Dedicated areas of user storage may be designated as sharable—including application level sharing for any application that has data. As shown in FIG. 6, this virtual storage area 159 may be combined from its internal hard disc storage with any network attached storage device located at the network to create a single virtual file system that consumers can use like a single drive.

FIG. 7 depicts a process 800 for back-up file services using a third party storage provider according to one aspect of the invention. As shown, in a first step 801, the device has been programmed to initiate an automatic back-up process at the PC endpoint. Then, at step 803, the files to be stored from a user device, e.g., a PC, are first compressed, encrypted and transferred to the gateway device 10. Referring back to FIG. 5A, this service may be configured to automatically implement a transfer 158 of user data or files from an attached user controlled portion 157 of storage 154 to be backed-up. Optionally, the gateway device 10 may compress and encrypt the data. After any such processing, the transferred data or files are stored at the application service provider side 156 of the virtual demarcation 155 (the encrypted partition) where the service management center 50 has visibility. Again, this could be a physical partition or a “virtual partition” defined by file information or some other method. Then, the device File Manager module of the gateway device 10 starts the Backup Manager module, which performs the File Backup to the a Data Center which may be implemented as part of the service management center 50. A Backup Manager functionality in the service management center 50 checks to see if the user is subscribed, and if so, proceeds to create an index of backup data and obtain an access key from the service management center 50, as indicated at step 806. Once authorized, the back-up service key is provided to the user's gateway device 10 at step 807. Then, in stage 2 of the back-up process, as indicated at step 810, the backed-up files are transferred with the service key to the third party storage provider 96 via the wide area network. Then, once successfully stored at the third party back-up storage service provider 96, a positive acknowledgement is communicated from the service provider to the gateway device 10 as indicated at step 812.

As controlled by the management service center 50, in an alternate embodiment, the encrypted content to be stored is transmitted to at least one other gateway device 10, for storage at a location 156 beyond the respective demarcation 155 for service provider storage in the storage 154 of the other gateway device(s). If multiple other gateway devices 10 are used for this service, the user's data or files can be back-up in a distributed, safe and redundant manner on the provider's storage portion 156 of the other devices 10. That is, each file may be partitioned into a plurality of pieces for further transfer or storage in a redundant and secure manner, e.g., and transferred to the service provider portions 156 behind the virtual demarcations 155. These pieces may then be encrypted and sent out externally for further storage, automatically, e.g., at time of log-in, on a scheduled basis, or, upon user initiation.

The gateway device 10 and its interactions with various endpoint devices and with the service management center 50 have been described with reference to diagrams of methods, apparatus (systems) and computer program products. It will be understood that elements and functions illustrated in the diagrams, can be implemented by computer program instructions running on one or more appropriately configured hardware platforms, e.g. to operate as a gateway device 10 or as one or more systems implementing functions of the service management center 50. Hence, operations described above may be carried out by execution of software, firmware, or microcode operating on a computer other programmable device of any type. Additionally, code for implementing such operations may comprise computer instruction in any form (e.g. source code, object code, interpreted code, etc.) stored in or carried by any computer or machine readable medium.

Program aspects of the technology may be thought of a “products,” typically in the form of executable code and/or associated data for implementing desired functionality, which is carried on or embodied in a type of machine readable medium. In this way, computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, so as to implement functions described above.

Terms regarding computer or machine “readable medium” (or media) as used herein therefore relate to any storage medium and any physical or carrier wave transmission medium, which participates in providing instructions or code or data to a processor for execution or processing. Storage media include any or all of the memory of the gateway device or associated modules thereof or any of the hardware platforms as may be used in the service management center, such as various semiconductor memories, tape drives, disk drives and the like, which may provide storage at any time for the software programming. All or portions of the software may at times be communicated through the Internet or various other telecommunication networks. Such communications, for example, may enable loading of the software from one computer into another computer, for example, from the updater 51 a hardware platform for a gateway device 10 or from another source into an element of the service management center 50. Thus, another type of media that may bear the software elements includes optical, electrical and electromagnetic waves, such as used across physical interfaces between local devices, through wired and optical landline networks and over various air-links. The physical elements that carry such waves, such as wired or wireless links, optical links or the like, also may be considered as media bearing the software. Hence, the broad class of media that may bear the instructions or data encompass many forms, including but not limited to, non-volatile storage media, volatile storage media as well as carrier wave and physical forms of transmission media.

Those skilled in the art will recognize that the teachings of this disclosure may be modified, extended and/or applied in a variety of ways. An extension of the system architecture, for example, provides the ability of various and disparate third-party application service providers to provide multiple application services independently. Application services are managed by the “managed” service provider through the service management center 50, meaning, generally, authorizing, provisioning, and monitoring the usage of a particular application service. This can be accomplished in a variety of ways with varying degrees of involvement of, or coordination with, the service management center. The service management center 50 could manage these items “soup-to-nuts” or have minimal involvement. For example, the service management center 50 could deal directly with the third-party service provider to acquire application services at the request of a user and manage the delivery, authorization, usage-monitoring and upgrading of the application service. At the other end of the spectrum, the managed service provider may have arrangements with the third-party application service provider by which orders or requests from the users may come directly to the third-party application service provider, and services are delivered to the user by the third-party service provider who in turn coordinates with the managed service provider to register and monitor the particular application service placed in the gateway device 10. It should be noted that this ability to manage application services extends through the gateway device into the endpoint devices registered or associated with the gateway or network.

While the foregoing has described what are considered to be the best mode and/or other examples, it is understood that various modifications may be made therein and that the subject matter disclosed herein may be implemented in various forms and examples, and that the teachings may be applied in numerous applications, only some of which have been described herein. It is intended by the following claims to claim any and all applications, modifications and variations that fall within the true scope of the present teachings.

Claims

1. A communication device for operation at a user premises, the communication device comprising: a first interface configured for wireless communication between endpoint devices associated with the user premises;a second interface configured for bi-directional communications, via a wide area network, with at least one of a service management center or an application service provider located externally to the user premises, wherein an application service enforcement manager is controlled by the application service provider through the service management center and configured to provide at least one policy rule or usage rule associated with an application service provided by the application service provider, and wherein the application service provider through the service management center provides the at least one policy rule or usage rule associated with the application service to the communication device;a voice-based user interface enabling management and control of application services, executed by the communication device, via one or more voice commands from a user present at the user premises;a graphical user interface rendered on a display associated with at least one of the communication device for enabling management and/or control of the application services executed by the communication device;one or more processors coupled to the first and second interfaces;storage coupled to the one or more processors, andprogramming in the storage for execution, wherein the programming, when executed by the one or more processors, causes the communication device to process at least one voice command from the user to: cause authentication and/or authorization to be performed by the application service provider and, upon successful authentication and/or authorization, to stream audible media from a server associated with the application service provider to at least one of the endpoint devices,wherein, in response to the processed at least one voice command, cause authentication and/or authorization to be performed by another application service provider from which the communication device is programmed to stream media upon successful authentication and/or authorization,wherein the programming includes—(a) the application service received from the application service provider; and(b) a communication device program, managed by the application service provider and configured to execute the application service provided from the application service provider, wherein the communication device executes the application service at the user premises independent of any application service that is executing on a networm of the application service provider, wherein, upon receiving a voice command request from the user to execute the application service at the communication device, an application service logic manager communicates with the application service enforcement manager to verify that the request conforms with the at least one policy rule and/or usage rule associated with the application service in order to authorize execution of the application service by the communication device.
2. The communication device of claim 1, wherein the application service executed at the communication device enables management of at least one of: digital rights of media utilized by at least one of the endpoint devices at or within the user premises or context sensitive advertising that is available for rendering on the at least one endpoint device at or within the user premises.
3. The communication device of claim 1, wherein the application service executed at the communication device enables automation of associated endpoint devices within the user premises including management of digital rights utilized by endpoint devices at or within the user premises.
4. The communication device of claim 1, wherein the application service executed at the communication device enables home automation and/or control of at least one of: the associated endpoint devices located within the user premises or endpoint devices located remote from the user premises.
5. The communication device of claim 1, wherein the application service executed at the communication device enables at least one of: home automation of connected devices within the user premises;home security of the user premises via connected devices within the user premises;management of video cameras and associated video data captured within the user premises;management of sensors located at or within the user premises;management of monitors at or within the user premises;management, including monitoring, of medical devices within the user premises;management of wired and wireless connections to endpoint devices at or within the user premises;management of digital rights utilized by endpoint devices at or within the user premises; ormanagement of context sensitive advertising that is available for rendering on endpoint devices at or within the user premises.
6. The communication device of claim 1, wherein the service application executed at the communication device enables management including monitoring of medical devices within the user premises.
7. A method performed at user premises by a communication device, the method comprising: providing, via a first interface, wireless communication between endpoint devices associated with the user premises;providing, via a second interface, bi-directional communications via a wide area network with at least one of a service management center or an application service provider located externally to the user premises, wherein an application service enforcement manager is controlled by the application service provider through the service management center and configured to provide at least one policy rule or usage rule associated with an application service provided by the application service provider, andwherein the application service provider, through the service management center, provides, to the communication device, the at least one policy rule or usage rule associated with the application service;enabling management and control of application services, executed by the communication device, via one or more voice commands from a user present at the user premises and via a graphical user interface rendered on a display associated with the communication device;in response to processing at least one voice command from the user causing authentication and/or authorization to be performed by the application service provider and, upon successful authentication and/or authorization, streaming audible media from a server associated with the application service provider to at least one endpoint device; andcausing authentication and/or authorization to be performed by another application service provider from which the communication device is programmed to stream media upon successful authentication and/or authorization,wherein:(a) the application service was received from the application service provider; and(b) a communication device program is managed by the application service provider and is configured to execute the application service provided from the application service provider, wherein the communication device executes the application service at the user premises independent of an application service that is executing on a network of the application service provider, wherein, upon receiving a voice command request from the user to execute the application service at the communication device, an application service logic manager communicates with the application service enforcement manager to verify that the request conforms with the at least one policy rule and/or usage rule associated with the application service in order to authorize execution of the application service by the communication device.
8. The method of claim 7, wherein the application service executed at the communication device enables management of at least one of: digital rights of media utilized by at least one of the endpoint devices at or within the user premises or context sensitive advertising that is available for rendering on the at least one endpoint device at or within the user premises.
9. The method of claim 7, wherein the application service executed at the communication device enables automation of associated endpoint devices within the user premises including management of digital rights utilized by endpoint devices at or within the user premises.
10. The method of claim 7, wherein the application service executed at the communication device enables home automation and/or control of at least one of: the associated endpoint devices located within the user premises or endpoint devices located remote from the user premises.
11. The method of claim 7, wherein the application service executed at the communication device enables at least one of: home automation of connected devices within the user premises;home security of the user premises via connected devices within the user premises;management of video cameras and associated video data captured within the user premises;management of sensors located at or within the user premises;management of monitors at or within the user premises;management, including monitoring, of medical devices within the user premises;management of wired and wireless connections to endpoint devices at or within the user premises;management of digital rights utilized by endpoint devices at or within the user premises; ormanagement of context sensitive advertising that is available for rendering on endpoint devices at or within the user premises.
12. The method of claim 7, wherein the application service executed at the communication device enables management including monitoring of medical devices within the user premises.
13. A non-transitory computer-readable storage medium storing instructions that, when executed by a communication device at a user premises, cause the communication device to perform operations comprising: providing, via a first interface, wireless communication between endpoint devices associated with the user premises;providing, via a second interface, bi-directional communications via a wide area network with at least one of a service management center or an application service provider located externally to the user premises, wherein an application service enforcement manager is controlled by the application service provider through the service management center and configured to provide at least one policy rule or usage rule associated with an application service provided by the application service provider, andwherein the application service provider, through the service management center, provides, to the communication device, the at least one policy rule or usage rule associated with the application service;enabling management and control of application services, executed by the communication device, via one or more voice commands from a user present at the user premises and via a graphical user interface rendered on a display associated with the communication device;in response to processing at least one voice command from the user: causing authentication and/or authorization to be performed by the application service provider and, upon successful authentication and/or authorization, streaming audible media from a server associated with the application service provider to at least one endpoint device; andcausing authentication and/or authorization to be performed by another application service provider from which the communication device is programmed to stream media upon successful authentication and/or authorization,wherein:(a) the application service was received from the application service provider; and(b) a communication device program is managed by the application service provider and is configured to execute the application service provided from the application service provider, wherein the communication device executes the application service at the user premises independent of an application service that is executing on a network of the application service provider, wherein, upon receiving a voice command request from the user to execute the application service at the communication device, an application service logic manager communicates with the application service enforcement manager to verify that the request conforms with the at least one policy rule and/or usage rule associated with the application service in order to authorize execution of the application service by the communication device.
14. The non-transitory computer-readable storage medium of claim 13, wherein the application service executed at the communication device enables management of at least one of: digital rights of media utilized by at least one of the endpoint devices at or within the user premises or context sensitive advertising that is available for rendering on the at least one endpoint device at or within the user premises.
15. The non-transitory computer-readable storage medium of claim 13, wherein the application service executed at the communication device enables automation of associated endpoint devices within the user premises including management of digital rights utilized by endpoint devices at or within the user premises.
16. The non-transitory computer-readable storage medium of claim 13, wherein the application service executed at the communication device enables home automation and/or control of at least one of: the associated endpoint devices located within the user premises or endpoint devices located remote from the user premises.
17. The non-transitory computer-readable storage medium of claim 13, wherein the application service executed at the communication device enables at least one of: home automation of connected devices within the user premises;home security of the user premises via connected devices within the user premises;management of video cameras and associated video data captured within the user premises;management of sensors located at or within the user premises;management of monitors at or within the user premises;management, including monitoring, of medical devices within the user premises;management of wired and wireless connections to endpoint devices at or within the user premises;management of digital rights utilized by endpoint devices at or within the user premises; ormanagement of context sensitive advertising that is available for rendering on endpoint devices at or within the user premises.
18. The non-transitory computer-readable storage medium of claim 13, wherein the application service executed at the communication device enables management including monitoring of medical devices within the user premises.

RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No. 14/633,449, filed Feb. 27, 2015, entitled “MULTI-SERVICES GATEWAY DEVICE AT USER PREMISES,” which is a continuation of U.S. application Ser. No. 13/618,238, filed Sep. 14, 2012, entitled “DEMARCATION BETWEEN SERVICE PROVIDER AND USER IN MULTI-SERVICES GATEWAY DEVICE AT USER PREMISES,” which is a continuation of U.S. application Ser. No. 12/521,763, filed Apr. 23, 2010, entitled “DEMARCATION BETWEEN SERVICE PROVIDER AND USER IN MULTI-SERVICES GATEWAY DEVICE AT USER PREMISES,” which is a United States national phase application of international application Number PCT/US2007/019543 filed Sep. 7, 2007, which claims the benefit of U.S. Provisional Application No. 60/882,865, filed Dec. 29, 2006 and of U.S. Provisional Application No. 60/882,862, filed Dec. 29, 2006, the disclosures of which are incorporated herein by reference.

US Referenced Citations (459)

Number	Name	Date	Kind
2273733	Paddock	Feb 1942	A
2316993	Sherwood	Apr 1943	A
4297607	Lynnworth et al.	Oct 1981	A
4467586	Long et al.	Aug 1984	A
4814552	Stefik et al.	Mar 1989	A
4835130	Box	May 1989	A
4991148	Gilchrist	Feb 1991	A
5339259	Puma et al.	Aug 1994	A
5372138	Crowley et al.	Dec 1994	A
5421338	Crowley et al.	Jun 1995	A
5515853	Smith et al.	May 1996	A
5517579	Baron et al.	May 1996	A
5524630	Crowley	Jun 1996	A
5588432	Crowley	Dec 1996	A
5673252	Johnson et al.	Sep 1997	A
5715825	Crowley	Feb 1998	A
5750941	Ishikawa et al.	May 1998	A
5840031	Crowley	Nov 1998	A
5867146	Kim et al.	Feb 1999	A
5867666	Harvey	Feb 1999	A
5878223	Becker et al.	Mar 1999	A
5943478	Aggarwal et al.	Aug 1999	A
5977958	Baron et al.	Nov 1999	A
5991739	Cupps et al.	Nov 1999	A
5995272	Patz	Nov 1999	A
6004269	Crowley et al.	Dec 1999	A
6016520	Facq et al.	Jan 2000	A
6029045	Picco et al.	Feb 2000	A
6033150	Culen	Mar 2000	A
6039251	Holowko	Mar 2000	A
6055569	O'Brien et al.	Apr 2000	A
6092114	Shaffer et al.	Jul 2000	A
6118205	Wood et al.	Sep 2000	A
6158483	Trpkovski	Dec 2000	A
6228290	Reames et al.	May 2001	B1
6301609	Aravamudan et al.	Oct 2001	B1
6330599	Harvey	Dec 2001	B1
6377571	Tai	Apr 2002	B1
6426955	Gossett Dalton, Jr. et al.	Jul 2002	B1
6434158	Harris et al.	Aug 2002	B1
6434618	Cohen	Aug 2002	B1
6449344	Goldfinger et al.	Sep 2002	B1
6456597	Bare	Sep 2002	B1
6457294	Virnelson et al.	Oct 2002	B1
6487646	Adams et al.	Nov 2002	B1
6493128	Agrawal et al.	Dec 2002	B1
6496575	Vasell	Dec 2002	B1
6526581	Edson	Feb 2003	B1
6542506	Lee	Apr 2003	B1
6549937	Auerbach et al.	Apr 2003	B1
6553345	Kuhn	Apr 2003	B1
6622168	Datta	Sep 2003	B1
6631412	Glasser et al.	Oct 2003	B1
6658091	Naidoo	Dec 2003	B1
6671730	Akatsu	Dec 2003	B1
6677976	Parker et al.	Jan 2004	B2
6681232	Sistanizadeh et al.	Jan 2004	B1
6694007	Lang et al.	Feb 2004	B2
6697474	Hanson et al.	Feb 2004	B1
6731992	Ziegler	May 2004	B1
6735619	Sawada	May 2004	B1
6745632	Dryer et al.	Jun 2004	B1
6771006	Zioter et al.	Aug 2004	B2
6798403	Kitada et al.	Sep 2004	B2
6850252	Hoffberg	Feb 2005	B1
6850901	Hunter et al.	Feb 2005	B1
6850979	Saulpaugh et al.	Feb 2005	B1
6851054	Wheeler et al.	Feb 2005	B2
6865150	Perkins	Mar 2005	B1
6871193	Campbell et al.	Mar 2005	B1
6889321	Kung et al.	May 2005	B1
6891838	Petite et al.	May 2005	B1
6898276	Millet et al.	May 2005	B1
6910074	Amin	Jun 2005	B1
6928576	Sekiguchi	Aug 2005	B2
6930598	Weiss	Aug 2005	B2
6931445	Davis	Aug 2005	B2
6957275	Sekiguchi	Oct 2005	B1
6961335	Millet et al.	Nov 2005	B1
6961857	Floryanzia	Nov 2005	B1
6965614	Osterhout et al.	Nov 2005	B1
6981025	Frazier	Dec 2005	B1
6988070	Kawasaki	Jan 2006	B2
7007070	Hickman	Feb 2006	B1
7035270	Moore, Jr. et al.	Apr 2006	B2
7054376	Rubinstain et al.	May 2006	B1
7058036	Yu et al.	Jun 2006	B1
7075919	Wendt et al.	Jul 2006	B1
7107217	Watanabe	Sep 2006	B2
7123700	Weaver, III et al.	Oct 2006	B1
7130719	Ehlers et al.	Oct 2006	B2
7139811	Lev Ran	Nov 2006	B2
7167920	Traversat et al.	Jan 2007	B2
7203477	Coppinger et al.	Apr 2007	B2
7207048	McQuillan et al.	Apr 2007	B2
7222087	Bezos et al.	May 2007	B1
7235710	Hatzfeld et al.	Jun 2007	B2
7266589	Brownhill	Sep 2007	B2
7269162	Turner	Sep 2007	B1
7277384	Chan	Oct 2007	B1
7305550	Oliver	Dec 2007	B2
7313120	Ekberg et al.	Dec 2007	B2
7336262	Tsuji	Feb 2008	B2
7349993	Kawamoto et al.	Mar 2008	B2
7397807	Chen et al.	Jul 2008	B2
7403838	Deen et al.	Jul 2008	B2
7421483	Kalra	Sep 2008	B1
7433836	August	Oct 2008	B1
7444401	Keyghobad	Oct 2008	B1
7461122	Kawana	Dec 2008	B2
7480724	Zimler et al.	Jan 2009	B2
7526539	Hsu	Apr 2009	B1
7551071	Bennett, III et al.	Jun 2009	B2
7574660	Campbell et al.	Aug 2009	B2
7584263	Hicks, III	Sep 2009	B1
7596692	Fox et al.	Sep 2009	B2
7627679	Bowen et al.	Dec 2009	B1
7650361	Wong et al.	Jan 2010	B1
7673001	Battle et al.	Mar 2010	B1
7685629	White et al.	Mar 2010	B1
7706928	Howell	Apr 2010	B1
7707606	Hofrichter et al.	Apr 2010	B2
7761527	Ferreira et al.	Jul 2010	B2
7765294	Edwards et al.	Jul 2010	B2
7809605	Tonse et al.	Oct 2010	B2
7818444	Brueck	Oct 2010	B2
7831748	Dernis et al.	Nov 2010	B2
7836044	Kamvar et al.	Nov 2010	B2
7865735	Yiachos	Jan 2011	B2
7895633	Van Hoff et al.	Feb 2011	B2
7913278	Ellis et al.	Mar 2011	B2
7933970	Zimler et al.	Apr 2011	B2
7948992	Holmgren et al.	May 2011	B1
7961712	Rabenko et al.	Jun 2011	B2
7970863	Fontaine	Jun 2011	B1
7970914	Bowen et al.	Jun 2011	B2
7987490	Ansari et al.	Jul 2011	B2
8020174	Sedogbo et al.	Sep 2011	B2
8031726	Ansari et al.	Oct 2011	B2
8060589	Kao	Nov 2011	B1
8090856	Bonefas	Jan 2012	B1
8189608	Duo et al.	May 2012	B2
8280978	Ansari et al.	Oct 2012	B2
8315266	Lam et al.	Nov 2012	B1
8374586	Bentkovski	Feb 2013	B2
8375657	Buchwald et al.	Feb 2013	B2
8391299	Schliserman	Mar 2013	B2
8459119	Miyamoto	Jun 2013	B2
8461413	Frankard	Jun 2013	B2
8577739	Ansari et al.	Nov 2013	B2
8583055	Park	Nov 2013	B2
8621588	Yoshida	Dec 2013	B2
8654936	Eslambolchi et al.	Feb 2014	B1
8665885	Pastorino et al.	Mar 2014	B2
8694523	Lim	Apr 2014	B2
8701166	Courtney et al.	Apr 2014	B2
8738921	Gephart	May 2014	B2
8893293	Schmoyer	Nov 2014	B1
8971341	Ansari et al.	Mar 2015	B2
8973056	Ellis et al.	Mar 2015	B2
9071606	Braun et al.	Jun 2015	B2
9167176	Winter	Oct 2015	B2
9203912	Krishnaswamy et al.	Dec 2015	B2
9253150	Ansari et al.	Feb 2016	B2
9270492	Ansari et al.	Feb 2016	B2
9325540	Zhang	Apr 2016	B2
9426151	Richards et al.	Aug 2016	B2
10263803	Ansari et al.	Apr 2019	B2
20010011284	Humpleman	Aug 2001	A1
20010025349	Sharood	Sep 2001	A1
20010041982	Kawasaki	Nov 2001	A1
20010048030	Sharood	Dec 2001	A1
20010049786	Harrison et al.	Dec 2001	A1
20010051996	Cooper et al.	Dec 2001	A1
20020021465	Moore	Feb 2002	A1
20020023131	Wu et al.	Feb 2002	A1
20020027504	David	Mar 2002	A1
20020033416	Gerszberg	Mar 2002	A1
20020035404	Ficco	Mar 2002	A1
20020046279	Chung	Apr 2002	A1
20020052915	Amin-Salehi	May 2002	A1
20020059425	Belfiore et al.	May 2002	A1
20020059586	Carney et al.	May 2002	A1
20020060994	Kovacs et al.	May 2002	A1
20020065894	Dalal et al.	May 2002	A1
20020067376	Martin	Jun 2002	A1
20020069243	Raverdy et al.	Jun 2002	A1
20020071440	Cerami et al.	Jun 2002	A1
20020078150	Thompson et al.	Jun 2002	A1
20020103877	Gagnon	Aug 2002	A1
20020112047	Kushwaha et al.	Aug 2002	A1
20020120686	Schell, III	Aug 2002	A1
20020122410	Kulikov et al.	Sep 2002	A1
20020124257	Ismagilov	Sep 2002	A1
20020128930	Nakamoto et al.	Sep 2002	A1
20020133613	Teng	Sep 2002	A1
20020136226	Christoffel et al.	Sep 2002	A1
20020156688	Horn	Oct 2002	A1
20020169858	Bellinger	Nov 2002	A1
20020176404	Girard	Nov 2002	A1
20020184358	Traversal et al.	Dec 2002	A1
20020184620	Davies et al.	Dec 2002	A1
20030005112	Krautkremer	Jan 2003	A1
20030012155	Sayeedi	Jan 2003	A1
20030023131	Antaki	Jan 2003	A1
20030023730	Wengrovitz et al.	Jan 2003	A1
20030083961	Bezos et al.	May 2003	A1
20030095569	Wengrovitz et al.	May 2003	A1
20030104010	Raa et al.	Jun 2003	A1
20030112755	McDysan	Jun 2003	A1
20030118726	Nakayama et al.	Jun 2003	A1
20030126207	Creamer et al.	Jul 2003	A1
20030135823	Marejka	Jul 2003	A1
20030140103	Szeto et al.	Jul 2003	A1
20030151621	McEvilly	Aug 2003	A1
20030169752	Chen et al.	Sep 2003	A1
20030171996	Chen et al.	Sep 2003	A1
20030185360	Moore et al.	Oct 2003	A1
20030210770	Krejcarek	Nov 2003	A1
20030217110	Weiss	Nov 2003	A1
20030229900	Reisman	Dec 2003	A1
20030231641	Ryoo	Dec 2003	A1
20030237004	Okamura	Dec 2003	A1
20040001480	Tanigawa et al.	Jan 2004	A1
20040003070	Fernald et al.	Jan 2004	A1
20040005859	Ghercioiu et al.	Jan 2004	A1
20040006477	Craner	Jan 2004	A1
20040006769	Ansari et al.	Jan 2004	A1
20040010327	Terashima	Jan 2004	A1
20040030750	Moore et al.	Feb 2004	A1
20040032399	Sekiguchi et al.	Feb 2004	A1
20040047310	Chen et al.	Mar 2004	A1
20040047358	Chen et al.	Mar 2004	A1
20040060079	Tanaka et al.	Mar 2004	A1
20040062230	Taylor et al.	Apr 2004	A1
20040073867	Kausik et al.	Apr 2004	A1
20040078573	Matsuyama	Apr 2004	A1
20040114608	Rao et al.	Jun 2004	A1
20040114610	Featherson	Jun 2004	A1
20040128310	Zmudzinski et al.	Jul 2004	A1
20040133657	Smith et al.	Jul 2004	A1
20040136373	Bareis	Jul 2004	A1
20040140989	Papageorge	Jul 2004	A1
20040148655	Choe et al.	Jul 2004	A1
20040160969	Moon et al.	Aug 2004	A1
20040174858	Caspi et al.	Sep 2004	A1
20040174863	Caspi	Sep 2004	A1
20040177376	Caspi et al.	Sep 2004	A1
20040203942	Dehlin	Oct 2004	A1
20040213273	Ma	Oct 2004	A1
20040215750	Stilp	Oct 2004	A1
20040218609	Foster et al.	Nov 2004	A1
20040228324	Alexiou et al.	Nov 2004	A1
20040230695	Anschutz et al.	Nov 2004	A1
20040240389	Bessis	Dec 2004	A1
20040255048	Lev et al.	Dec 2004	A1
20040255326	Hicks, III et al.	Dec 2004	A1
20050018612	Fitzgerald	Jan 2005	A1
20050025887	Xin et al.	Feb 2005	A1
20050027887	Zimler	Feb 2005	A1
20050038526	Choi	Feb 2005	A1
20050038875	Park	Feb 2005	A1
20050065855	Geller	Mar 2005	A1
20050068938	Wang	Mar 2005	A1
20050071663	Medvinsky	Mar 2005	A1
20050076198	Skomra et al.	Apr 2005	A1
20050089052	Chen et al.	Apr 2005	A1
20050094621	Acharya et al.	May 2005	A1
20050107086	Tell	May 2005	A1
20050108091	Sotak et al.	May 2005	A1
20050141492	Chan et al.	Jun 2005	A1
20050144616	Hammond	Jun 2005	A1
20050149922	Vincent	Jul 2005	A1
20050150697	Altman et al.	Jul 2005	A1
20050174950	Ayyagari	Aug 2005	A1
20050180396	Lim	Aug 2005	A1
20050190744	Sun et al.	Sep 2005	A1
20050190898	Priest et al.	Sep 2005	A1
20050195752	Amin-Salehi	Sep 2005	A1
20050195802	Klein et al.	Sep 2005	A1
20050198040	Cohen	Sep 2005	A1
20050208948	Hori	Sep 2005	A1
20050210064	Caldini	Sep 2005	A1
20050216302	Raji	Sep 2005	A1
20050216580	Raji	Sep 2005	A1
20050216949	Candelora et al.	Sep 2005	A1
20050220081	Urquizo	Oct 2005	A1
20050222933	Wesby	Oct 2005	A1
20050226158	Takahashi	Oct 2005	A1
20050232284	Karaoguz et al.	Oct 2005	A1
20050240680	Costa-Requena et al.	Oct 2005	A1
20050240943	Smith et al.	Oct 2005	A1
20050249196	Ansari et al.	Nov 2005	A1
20050257039	Marshall	Nov 2005	A1
20050260996	Groenendaal	Nov 2005	A1
20050262257	Major	Nov 2005	A1
20050286466	Tagg et al.	Dec 2005	A1
20060020589	Wu et al.	Jan 2006	A1
20060025132	Karaoguz et al.	Feb 2006	A1
20060029007	Ayyagari	Feb 2006	A1
20060029064	Rao et al.	Feb 2006	A1
20060031406	Watson et al.	Feb 2006	A1
20060031476	Mathes et al.	Feb 2006	A1
20060040667	Coppinger et al.	Feb 2006	A9
20060041926	Istvan	Feb 2006	A1
20060041936	Anderson	Feb 2006	A1
20060067344	Sakurai	Mar 2006	A1
20060075108	Sylvain	Apr 2006	A1
20060075276	Kataria	Apr 2006	A1
20060075429	Istvan	Apr 2006	A1
20060080352	Boubez et al.	Apr 2006	A1
20060104432	Evslin	May 2006	A1
20060122976	Baluja et al.	Jun 2006	A1
20060136246	Tu	Jun 2006	A1
20060146784	Karpov et al.	Jul 2006	A1
20060153214	Moore et al.	Jul 2006	A1
20060159116	Gerszberg	Jul 2006	A1
20060164205	Buckingham	Jul 2006	A1
20060167985	Albanese	Jul 2006	A1
20060174289	Theberge	Aug 2006	A1
20060178943	Rollinson et al.	Aug 2006	A1
20060209857	Hicks, III	Sep 2006	A1
20060220830	Bennett, III	Oct 2006	A1
20060227724	Thubert et al.	Oct 2006	A1
20060236419	La Rosa et al.	Oct 2006	A1
20060239425	Hurst et al.	Oct 2006	A1
20060253894	Bookman	Nov 2006	A1
20060256759	Sayeedi	Nov 2006	A1
20060258396	Matsuoka	Nov 2006	A1
20060259584	Watson et al.	Nov 2006	A1
20060271695	Lavian	Nov 2006	A1
20060291506	Cain	Dec 2006	A1
20060293965	Burton	Dec 2006	A1
20070005766	Singhal et al.	Jan 2007	A1
20070021867	Woo	Jan 2007	A1
20070038637	Taneja	Feb 2007	A1
20070043476	Richards et al.	Feb 2007	A1
20070043478	Ehlers et al.	Feb 2007	A1
20070049342	Mayer et al.	Mar 2007	A1
20070050351	Kasperski et al.	Mar 2007	A1
20070055759	McCoy	Mar 2007	A1
20070058608	Lin	Mar 2007	A1
20070058644	Brahmbhatt et al.	Mar 2007	A1
20070061149	Chang	Mar 2007	A1
20070089183	Poovaiah et al.	Apr 2007	A1
20070100981	Adamczyk et al.	May 2007	A1
20070106570	Hartman et al.	May 2007	A1
20070109976	Samanta et al.	May 2007	A1
20070115922	Schneider et al.	May 2007	A1
20070143262	Kasperski	Jun 2007	A1
20070143831	Pearson	Jun 2007	A1
20070147420	Dean, Jr.	Jun 2007	A1
20070150286	Miller	Jun 2007	A1
20070150345	Tonse et al.	Jun 2007	A1
20070156265	McCoy	Jul 2007	A1
20070165629	Chaturvedi et al.	Jul 2007	A1
20070169144	Chen	Jul 2007	A1
20070171895	Oberle et al.	Jul 2007	A1
20070192477	Hicks et al.	Aug 2007	A1
20070192486	Wilson	Aug 2007	A1
20070192735	Lehto et al.	Aug 2007	A1
20070198437	Eisner et al.	Aug 2007	A1
20070199022	Moshiri	Aug 2007	A1
20070220165	Moorer	Sep 2007	A1
20070253443	Dean, Jr. et al.	Nov 2007	A1
20070286159	Preiss et al.	Dec 2007	A1
20070291650	Ormazabal	Dec 2007	A1
20070294721	Haeuser	Dec 2007	A1
20070297454	Brothers	Dec 2007	A1
20080005306	Kushalnagar	Jan 2008	A1
20080005565	Shiga	Jan 2008	A1
20080022391	Sax	Jan 2008	A1
20080043719	Pok et al.	Feb 2008	A1
20080052393	McNaughton et al.	Feb 2008	A1
20080066126	Walter	Mar 2008	A1
20080069121	Adamson et al.	Mar 2008	A1
20080084888	Yadav et al.	Apr 2008	A1
20080098212	Helms	Apr 2008	A1
20080101320	Krahn et al.	May 2008	A1
20080123683	Cheng et al.	May 2008	A1
20080127880	Dhellemmes et al.	Jun 2008	A1
20080130666	Kawamoto et al.	Jun 2008	A1
20080134258	Goose	Jun 2008	A1
20080141315	Ogilvie	Jun 2008	A1
20080144642	Song	Jun 2008	A1
20080151778	Venkitaraman et al.	Jun 2008	A1
20080155613	Benya	Jun 2008	A1
20080163059	Craner	Jul 2008	A1
20080165789	Ansari et al.	Jul 2008	A1
20080166048	Raif et al.	Jul 2008	A1
20080177856	Howard	Jul 2008	A1
20080189774	Ansari et al.	Aug 2008	A1
20080221715	Krzyzanowski	Sep 2008	A1
20080239957	Tokura	Oct 2008	A1
20080240125	Purvis et al.	Oct 2008	A1
20080304500	Schliserman et al.	Dec 2008	A1
20090034419	Flammer, III et al.	Feb 2009	A1
20090037382	Ansari et al.	Feb 2009	A1
20090067441	Ansari et al.	Mar 2009	A1
20090070229	Ansari et al.	Mar 2009	A1
20090077207	Karaoguz et al.	Mar 2009	A1
20090100460	Hicks, III	Apr 2009	A1
20090168787	Ansari et al.	Jul 2009	A1
20090178079	Derrenberger et al.	Jul 2009	A1
20090180422	Bohacek et al.	Jul 2009	A1
20090189774	Brundridge et al.	Jul 2009	A1
20090216847	Krishnaswamy et al.	Aug 2009	A1
20100014444	Ghanadan et al.	Jan 2010	A1
20100030734	Chunilal	Feb 2010	A1
20100061309	Buddhikot et al.	Mar 2010	A1
20100071053	Ansari et al.	Mar 2010	A1
20100202450	Ansari et al.	Aug 2010	A1
20100205152	Ansari et al.	Aug 2010	A1
20100205301	Ansari et al.	Aug 2010	A1
20100211636	Starkenburg	Aug 2010	A1
20100217837	Ansari et al.	Aug 2010	A1
20100231790	Ansari et al.	Sep 2010	A1
20100235433	Ansari et al.	Sep 2010	A1
20100238810	Ormazabal	Sep 2010	A1
20100241711	Ansari et al.	Sep 2010	A1
20100241748	Ansari et al.	Sep 2010	A1
20100291940	Koo	Nov 2010	A1
20110019135	Koganezawa	Jan 2011	A1
20110092232	Lee	Apr 2011	A1
20110182205	Gerdes et al.	Jul 2011	A1
20110261654	Miyamoto et al.	Oct 2011	A1
20120060181	Craner	Mar 2012	A1
20120101881	Taylor et al.	Apr 2012	A1
20120110490	Keller	May 2012	A1
20120157043	LaJoie	Jun 2012	A1
20120311665	Lim	Dec 2012	A1
20130191871	Gilboy	Jul 2013	A1
20130329745	Phillips et al.	Dec 2013	A1
20140259074	Ansari et al.	Sep 2014	A1
20140362253	Kim	Dec 2014	A1
20150074259	Ansari et al.	Mar 2015	A1
20150208363	Fu	Jul 2015	A1
20150347683	Ansari et al.	Dec 2015	A1
20160226823	Ansari et al.	Aug 2016	A1
20160254962	Ansari et al.	Sep 2016	A1
20160330200	Ansari et al.	Nov 2016	A1
20160344745	Johnson	Nov 2016	A1
20170070395	Ansari et al.	Mar 2017	A1
20170078154	Ansari et al.	Mar 2017	A1
20170344703	Ansari et al.	Nov 2017	A1
20180123819	Ansari et al.	May 2018	A1
20180123905	Ansari et al.	May 2018	A1
20180124115	Ansari et al.	May 2018	A1
20180126414	Ansari et al.	May 2018	A1
20180131571	Ansari et al.	May 2018	A1
20180131572	Ansari et al.	May 2018	A1
20180152310	Ansari et al.	May 2018	A1
20180152311	Ansari et al.	May 2018	A1
20180198692	Ansari et al.	Jul 2018	A1
20180333746	Ansari et al.	Nov 2018	A1
20180361426	Ansari et al.	Dec 2018	A1
20190245714	Ansari et al.	Aug 2019	A1
20190312745	Ansari et al.	Oct 2019	A1
20200076638	Ansari et al.	Mar 2020	A1

Foreign Referenced Citations (43)

Number	Date	Country
102500747	Jun 2012	CN
3002904	Aug 1980	DE
3818631	Dec 1989	DE
9116206	Apr 1992	DE
19723596	Oct 1998	DE
10024525	Nov 2001	DE
20304806	Jul 2003	DE
0805254	Nov 1997	EP
0921260	Jun 1999	EP
1 113 659	Jul 2001	EP
1195497	Apr 2002	EP
1377005	Jan 2004	EP
1394986	Mar 2004	EP
1657396	May 2006	EP
03269387	Nov 1991	JP
07104063	Apr 1995	JP
11290082	Oct 1999	JP
2002139565	May 2002	JP
WO-0193533	Dec 2001	WO
WO-2005111653	Nov 2005	WO
WO-2007004921	Jan 2007	WO
WO-2008021665	Feb 2008	WO
2008082441	Jul 2008	WO
2008083384	Jul 2008	WO
2008083385	Jul 2008	WO
2008083387	Jul 2008	WO
2008083391	Jul 2008	WO
2008085201	Jul 2008	WO
2008085202	Jul 2008	WO
2008085203	Jul 2008	WO
2008085204	Jul 2008	WO
2008085205	Jul 2008	WO
2008085206	Jul 2008	WO
2008085207	Jul 2008	WO
WO-2008082346	Jul 2008	WO
WO-2008085205	Sep 2008	WO
WO-2008085204	Oct 2008	WO
WO-2008085207	Oct 2008	WO
WO-2008085203	Nov 2008	WO
WO-2008085206	Nov 2008	WO
2009036088	Mar 2009	WO
2009036185	Mar 2009	WO
2009086134	Jul 2009	WO

Non-Patent Literature Citations (62)

Entry
“FAD-binding, type 2,” SuperFamily Accession SSF56176, InterPro Accession IPR016166, downloaded May 24, 2012.
“FAD-linked oxidase, N-terminal,” InterPro Accession IPR006094, downloaded May 24, 2012.
Choe, S., et al., “Overexpression of DWARF4 in the Brassinosteroid Biosynthetic Pathway Results in Increased Vegetative Growth and Seed Yield in Arabidopsis,” The Plant Journal, vol. 26, No. 6, 2001, pp. 573-582.
DLNA enables streaming of premium video in connected homes across Europe. (New Products) IPTV Newsletter, v 5, n 10, p. 4 Oct. 2011.
Fraaije, M.W., et al., “A Novel Oxidoreductase Family Sharing a Conserved FAD-Binding Domain,” TIBS, vol. 23, 1998, pp. 206-207.
H. Kashiwagi, “M-sequence and its application,” Shokodo, Mar. 25, 1996, pp. 1-5, 16-32.
Haerick W et al., “Success in Home Service Deployment: Zero-Touch or Chaos?”, British Telecommunications, Jul. 1, 2007, pp. 36-43, vol. 5, No. 3, London, GB.
Hong et al, “The Rice brassinosteroid-deficient dwarf2 Mutant, Defective in the Rice Homolog of Arabidopsis DIMINUTO/DWARD1, is Rescued by the Endogenously Accumulated Alternative Bioactive Brassinosteroid, Dolichosterone,” The Plant Cell, 2006, col. 17, pp. 2243-2254.
Il-Woo Lee, et al., A Proposed Platform & Performance Estimation of Digital-Home Service Delivery/Management Systems, Apr. 10, 2006, pp. 713-719, Information Technology: New Generations, 2006.
International Application No. PCT/US2008/087724, filed Dec. 19, 2008, 7 Pages, 1211 Geneva 20, Switzerland.
International Search Report and the Written Opinion of the International Searching Authority issued in International Application No. PCT/US2008/087724 dated Feb. 17, 2009.
International Search Report and the Written Opinion of the International Searching Authority issued in International Patent Application No. PCT/US08/75889 dated Nov. 24, 2008.
International Search Report and Written Opinion in International Application No. PCT/US05/15860, dated Jul. 17, 2006, 8 pages.
International Search Report and Written Opinion in International Application No. PCT/US08/76036, dated Nov. 14, 2008.
International Search Report in International Application No. PCT/JP2008/051225, dated Feb. 29, 2008.
Klahre, U., et al., “The Arabidopsis DIMINUTO/DWARD1 Gene Encodes a Protein Involved in Steroid Synthesis,” The Plant Cell, vol. 10, 1998, pp. 1677-1690.
Machine Translation of JP11290082-A, Oct. 1999.
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Aug. 27, 2008, 24 pages, Application No. PCT/US2007/089232.
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Aug. 8, 2008, 22 pages, Application No. PCT/US2007/089227.
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Oct. 22, 2008, 12 pages, Application No. PCT/US2007/089232.
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, dated Feb. 26, 2008, 11 pages, Application No. PCT/US07/19483.
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, dated Mar. 14, 2008, 12 pages, Application No. PCT/US07/19533.
PCT Invitation to Pay Additional Fees and, where Applicable, Protest Fee (PCT/ISA/206) and Communication Relating to the Results of the Partial International Search (Annex to PCT/ISA/206) dated May 19, 2008 for PCT Application No. PCT/US2007/089237, 7 pages.
PCT Invitation to Pay Additional Fees and, where Applicable, Protest Fee (PCT/ISA/206) and Communication Relating to the Results of the Partial International Search (Annex to PCT/ISA/206) dated May 21, 2008 for PCT Application No. PCT/US2007/089227, 7 pages.
Sakamoto, T., “Phytohormones and Rice Crop Yield: Strategies and Opportunities for Genetic Improvement,” Transgenic Research, vol. 15, 2006, pp. 399-404.
Takahashi, T., et al., “The DIMINUTO Gene of Arabidopsis is Involved in Regulating Cell Elongation,” Genes and Development, vol. 9, 1995, pp. 97-107.
Technology and challenges of virtual communities. International Journal of Business Research , v 7 , n 4, p. 69 Jul. 2007.
Yokota, T., “The Structure, Biosynthesis and Function of Brassinosteroids,” Trends in Plan Science, vol. 2, No. 4, 1997, pp. 137-143.
Young-Gab Kim et al., A Service Bundle Authentication Mechanism in the OSGI Service Platform, Advanced Information Networking and Applications, 2004, AINA 2004. 18th International Conference on Fukuoka, Japan, Mar. 29-31, 2004, Piscataway, NJ, USA, IEEE, vol. 1, Mar. 29, 2004, pp. 420-425.
Wen-Shyang Hwang et al., “A QoS-aware Residential Gateway with Bandwidth Management,” Aug. 2005.
U.S. Appl. No. 15/944,620 for Ansari et al., filed Apr. 3, 2018.
U.S. Appl. No. 16/002,945 for Ansari et al., filed Jun. 7, 2018.
U.S. Appl. No. 16/124,500 for Ansari et al., filed Sep. 7, 2018.
Duenas Juan C. An End-to-End Service Provisioning scenario for the Residential Environment, IEEE Communications Magazine, Sep. 2005, pp. 94-100.
Intel, “Delivering on the Promise of Triple Play Digital Media,” Technology Backgrounder, Consumer Electronics, 2004, pp. 1-4.
Yeon-Joo, Oh, et al., “Design of a SIP-based Real-time Visitor Conversation and Door Control Architecture using a Home Gateway.” Consumer Electronics, 2006. ICCE '06. 2006 Digest of Technical Papers, International Conference. Las Vegas, NV, USA, IEEE, Jan. 7, 2006, pp. 187-188.
Ganguly, Arjit, et al., “IP over P2P: enabling self-configuring virtual IP networks for grid computing.” In Parallel and Distributed Processing Symposium, 2006, IPDPS 2006, Apr. 25-29, retrieved on Jan. 20, 2010. Retrieved from the Internet: <URL:http://aarxiv.org/PS_cache/cs/pdf/0603/060387v1.pdf.>.
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Oct. 30, 2008, International Application No. PCT/US2007/089237, filed Dec. 31, 2007, 15 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Aug. 27, 2008, International Application No. PCT/US2007/089237, filed Dec. 31, 2007, 6 pages.
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Jul. 17, 2008, International Application No. PCT/US2007/019543, filed Sep. 7, 2007, 5 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Jul. 17, 2008, International Application No. PCT/US2007/019543, filed Sep. 7, 2007, 1 page.
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Jul. 14, 2008, International Application No. PCT/US2007/019546, filed Sep. 7, 2007, 5 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Jul. 14, 2008, International Application No. PCT/US2007/019546, filed Sep. 7, 2007, 1 page.
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Apr. 25, 2008, International Application No. PCT/US2007/019531, filed Sep. 7, 2007, 7 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Apr. 25, 2008, International Application No. PCT/US2007/019531, filed Sep. 7, 2007, 1 page.
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Aug. 21, 2008, International Application No. PCT/US2007/019534, filed Sep. 7, 2007, 5 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Aug. 21, 2008, International Application No. PCT/US2007/019534, filed Sep. 7, 2007, 1 page.
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Aug. 25, 2008, International Application No. PCT/US2007/0195345, filed Sep. 7, 2007, 5 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Aug. 25, 2008, International Application No. PCT/US2007/019545, filed Sep. 7, 2007, 1 page.
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Jul. 2, 2008, International Application No. PCT/US2007/019544, filed Sep. 7, 2007, 5 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Jul. 2, 2008, International Application No. PCT/US2007/019544, filed Sep. 7, 2007, 1 page. PCT International Searching Authority—European Patent Office, PCT Written Opinion of the
PCT International Searching Authority—European Patent Office, PCT Written Opinion of the International Searching Authority dated Mar. 14, 2008, International Application No. PCT/US2007/019533, filed Sep. 7, 2007, 7 pages.
PCT International Searching Authority—European Patent Office, PCT International Search Report dated Mar. 14, 2008, International Application No. PCT/US2007/019533, filed Sep. 7, 2007, 1 page.
U.S. Appl. No. 16/817,905 for Ansari et al., filed Mar. 13, 2020.
U.S. Appl. No. 16/291,856 for Ansari et al., filed Mar. 4, 2019.
U.S. Appl. No. 16/439,501 for Ansari et al., filed Jun. 12, 2019.
U.S. Appl. No. 16/460,148 for Ansari et al., filed Jul. 2, 2019.
U.S. Appl. No. 16/512,876 for Ansari et al., filed Jul. 16, 2019.
U.S. Appl. No. 16/514,803 for Ansari et al., filed Jul. 17, 2019.
U.S. Appl. No. 16/531,914 for Ansari et al., filed Aug. 5, 2019.
U.S. Appl. No. 16/684,915 for Ansari et al., filed Nov. 15, 2019.
U.S. Appl. No. 16/778,304 for Ansari et al., filed Jan. 31, 2020.

Related Publications (1)

	Number	Date	Country
	20160226920 A1	Aug 2016	US

Provisional Applications (2)

	Number	Date	Country
	60882865	Dec 2006	US
	60882862	Dec 2006	US

Continuations (3)

	Number	Date	Country
Parent	14633449	Feb 2015	US
Child	15011843		US
Parent	13618238	Sep 2012	US
Child	14633449		US
Parent	12521763		US
Child	13618238		US

Multi-services gateway device at user premises

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract