Abstract: Customer premise network configuration to enable a new service within the network is provided by a network configuration manager. The network configuration manager is either manually or automatically invoked upon a new service being used in the network. The configuration manager obtains a service template for the service, which template provides generic end-to-end requirements for enabling the service. A configuration generator generates vendor-neutral device-configuration settings from the service template. A service configuration validator module then validates the service. Finally, an adaptor module translates the vendor-neutral device-configuration settings to vendor specific configuration settings corresponding to the devices in the network and configures the devices.

Abstract: Errant conditions, including configuration issues, device/application failures, and performance problems, affecting a home network are detected by considering end-to-end information flows within the home network and between the home network and an external network. Specifically, errant conditions are detected by analyzing monitored network information flows, by analyzing responses resulting from the active stimuli of hardware/software components within the home and external network, and by considering in this analysis configuration information obtained from network devices. Gathered information and detected errant conditions are reported to an administrative management system for further analysis and for use by a help-desk administrator or home user in resolving the reported conditions.

Abstract: Customer premise network configuration to enable a new service within the network is provided by a network configuration manager. The network configuration manager is either manually or automatically invoked upon a new service being used in the network. The configuration manager obtains a service template for the service, which template provides generic end-to-end requirements for enabling the service. A configuration generator generates vendor-neutral device-configuration settings from the service template. A service configuration validator module then validates the service. Finally, an adaptor module translates the vendor-neutral device-configuration settings to vendor specific configuration settings corresponding to the devices in the network and configures the devices.

Abstract: Session Initiation Protocol (SIP) is used to communicate with Network-capable appliances. In a system employing SIP, a remote user agent client (UAC) sends a message over the Internet via a Proxy server to a user agent server at the location of the appliances, e.g., the client's home. This communications channel allows the client to control the appliances and to determine their status. The Proxy server between the UAC and a plurality of UAS processors has the address mapping, authentication, authorization and/or translation functions out-sourced from the UAS processors to the Proxy server connected to them.

Abstract: Session Initiated Protocol (SIP) is used to communicate with Network-capable appliances by leveraging SIP capabilities to directly communicate with appliances, even when they are behind firewalls, Network Address Translators or other entities that prevent direct end-to-end communication. A remote user agent client (UAC) sends a message over the Internet via proxy servers to a user agent server at the location of the appliances, e.g., the client's home. This communications channel allows the client to control the appliances and to determine their status. In order to enable this operation, conventional SIP messages are extended to a DO message that includes a universal resource locator (URL) without location information otherwise specified in the SIP message and a generalized payload body with control and/or query instructions specific to networked appliances. When the command message is a SIP INVITE type, it includes a description of the appliance.