Abstract: A method of establishing a first network connection of a wired network with a customer premise equipment (CPE) installed at a customer premise (CP). The method monitors the first network connection and detects an outage of the first network connection. The method provides an option of using a second network connection of a wireless network, for delivery of services during the first outage of the first network connection. The method receives a response, and switches the delivery of services, via a machine to machine (M2M) interface in the CPE, to the second network connection.

Abstract: An approach is provided for determining that a device has been placed on a hold status during a communication session, wherein hold media is presented to the device during the hold status. The approach involves determining that the device and/or the communication session is registered for a hold music service that provides media from a content provider. The approach also involves requesting personalized media from the content provider. The approach further involves presenting the personalized media to the device as the hold media during the hold status.

Abstract: A method of establishing a first network connection of a wired network with a customer premise equipment (CPE) installed at a customer premise (CP). The method monitors the first network connection and detects an outage of the first network connection. The method provides an option of using a second network connection of a wireless network, for delivery of services during the first outage of the first network connection. The method receives a response, and switches the delivery of services, via a machine to machine (M2M) interface in the CPE, to the second network connection.

Abstract: An approach is provided for determining that a device has been placed on a hold status during a communication session, wherein hold media is presented to the device during the hold status. The approach involves determining that the device and/or the communication session is registered for a hold music service that provides media from a content provider. The approach also involves requesting personalized media from the content provider. The approach further involves presenting the personalized media to the device as the hold media during the hold status.

Abstract: A system comprising at least one controller including a controller processor with a memory configured to execute self-healing rules. The self-healing rules may include at least one corrective measure and at least one failure symptom. The system may include an automated incident management device including a central processor with a memory to receive service management information from the at least one controller, correlate at least one corrective measure with at least one failure symptom, adjust the self-healing rules based on the correlation, and propagate the adjusted self-healing rules to the at least one controller.

Abstract: An automated incident management device may receive a message from a customer site, the message indicative of a customer issue with a managed service provided to the customer site by way of a primary network connection. The device may connect to an item of customer equipment by way of a secondary network connection to the customer site; retrieve information from the customer equipment by way of the secondary network connection; attempt a corrective measure with the managed service based on the retrieved information, the corrective measure being determined according to rules that specify corrective measures likely to resolve the trouble ticket; and update a trouble ticket associated with the customer site responsive to the attempted corrective measure. In some examples, the automated incident management device may determine that the customer issue is responsibly of the customer to address.

Abstract: An interface engine provides animated views in a user interface. The interface engine directs the operation of a rendering environment to create an interface in a rendering area. The interface engine includes views, layouts, animators, and constraints. Views identify child views and resources for display in the rendering area. In response to events, such as user inputs, a view modifies itself by calling layouts, animators, and constraints. A layout manages the attributes of a view's child views, including child view position and size. An animator modifies the view's appearance over a specified period of time. A constraint imposes limits on view properties. In one implementation, an Internet site delivers an interface engine to a browser to supply content and a user interface. A presentation server compiles an interface engine description and specified resources into an interface engine.

Abstract: A server is disclosed that presents content to a client. The server receives a request for particular content. In response to the request, the server accesses data and/or code that describes the particular content. The server compiles that code and/or data to create executable code, and transmits the executable code to the client for execution on the client. In one embodiment, the code describing the particular content is a mark-up language description. In various implementations, the executable code includes a user interface that provides access to the requested content.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: An interface engine provides animated views in a user interface. The interface engine directs the operation of a rendering environment to create an interface in a rendering area. The interface engine includes views, layouts, animators, and constraints. Views identify child views and resources for display in the rendering area. In response to events, such as user inputs, a view modifies itself by calling layouts, animators, and constraints. A layout manages the attributes of a view's child views, including child view position and size. An animator modifies the view's appearance over a specified period of time. A constraint imposes limits on view properties. In one implementation, an Internet site delivers an interface engine to a browser to supply content and a user interface. A presentation server compiles an interface engine description and specified resources into an interface engine.

Abstract: An interface engine provides animated views in a user interface. The interface engine directs the operation of a rendering environment to create an interface in a rendering area. The interface engine includes views, layouts, animators, and constraints. Views identify child views and resources for display in the rendering area. In response to events, such as user inputs, a view modifies itself by calling layouts, animators, and constraints. A layout manages the attributes of a view's child views, including child view position and size. An animator modifies the view's appearance over a specified period of time. A constraint imposes limits on view properties. In one implementation, an Internet site delivers an interface engine to a browser to supply content and a user interface. A presentation server compiles an interface engine description and specified resources into an interface engine.

Abstract: A server is disclosed that presents content to a client. The server receives a request for particular content. In response to the request, the server accesses data and/or code that describes the particular content. The server compiles that code and/or data to create executable code, and transmits the executable code to the client for execution on the client. In one embodiment, the code describing the particular content is a mark-up language description. In various implementations, the executable code includes a user interface that provides access to the requested content.

Abstract: The present invention provides software developers with the capability to create applications that can access information online and offline without having to program such capabilities into their applications. An application can gather information from various remote data sources via a network or other communication means, and still have access to all or a portion of that information when the computing device running the application is no longer connected to the network. In one embodiment, a client manages information access, caching and synchronization for the application. When connected, information accessed is stored in a local data store on (or near) the computing device. When disconnected, requests are run against the local data store instead of the remote data source. When reconnected, information is synchronized between the local data store and the remote data source.

Abstract: An interface engine provides animated views in a user interface. The interface engine directs the operation of a rendering environment to create an interface in a rendering area. The interface engine includes views, layouts, animators, and constraints. Views identify child views and resources for display in the rendering area. In response to events, such as user inputs, a view modifies itself by calling layouts, animators, and constraints. A layout manages the attributes of a view's child views, including child view position and size. An animator modifies the view's appearance over a specified period of time. A constraint imposes limits on view properties. In one implementation, an Internet site delivers an interface engine to a browser to supply content and a user interface. A presentation server compiles an interface engine description and specified resources into an interface engine.

Abstract: An interface engine provides animated views in a user interface. The interface engine directs the operation of a rendering environment to create an interface in a rendering area. The interface engine includes views, layouts, animators, and constraints. Views identify child views and resources for display in the rendering area. In response to events, such as user inputs, a view modifies itself by calling layouts, animators, and constraints. A layout manages the attributes of a view's child views, including child view position and size. An animator modifies the view's appearance over a specified period of time. A constraint imposes limits on view properties. In one implementation, an Internet site delivers an interface engine to a browser to supply content and a user interface. A presentation server compiles an interface engine description and specified resources into an interface engine.