Abstract: Various embodiments pertain to managing electronic devices using an electronic device as a root of trust. According to one embodiment, registration information for an electronic device 150 is received 220. The registration information identifies the electronic device 150 and an environment 130 that the electronic device 150 is trusted in. The electronic device150 is specified 230 as a root of trust device 150 for the trusted environment 130 based on the registration information. The root of trust device 150 is specified 240 as the root of trust for a new electronic device 170 based on new information that identifies the root of trust device 150 and identifies the new electronic device 170. The new electronic device 170 is managed 250 using the root of trust device 150 without requiring the user of the root of trust device 150 and the new electronic device 170 to configure any electronic devices.

Abstract: A mobile device apparatus uses an HyperText Transfer protocol (HTTP) push operation to simulate server-initiated sessions. The illustrative mobile device apparatus comprises a push server logic operable in a push server that sends a message to a mobile device over a network. The push server logic is configured to receive a GET command from a mobile device. The GET command includes a mobile device identifier parameter and a timeout parameter designating a maximum time interval for the push server to reply with a message. The push server logic holds a GET command session until expiration of a timeout designated by the timeout parameter in a condition that no message is targeted to the mobile device. The push server logic terminates the GET command session by sending a message immediately in a condition that the message is targeted to the mobile device.

Abstract: Various embodiments pertain to managing a converged electronic device 110 that is capable of communicating with a plurality of connections 132, 134. According to one embodiment, a first configuration associated with the converged electronic device 110 is used 220 while the converged electronic device 110 communicates using a first connection 132. An event that relates to the converged electronic device 110 is detected 230 that indicates a second connection 134 could provide a higher level of service for the converged electronic device 110. A second configuration that would be used for the converged electronic device 110 is determined 240 while the converged electronic device 110 communicates using the second connection 134. The second configuration is used 250 while the converged electronic device 110 communicates using the second connection 134.

Abstract: A mobile device apparatus uses an HyperText Transfer protocol (HTTP) push operation to simulate server-initiated sessions. The illustrative mobile device apparatus comprises a push server logic operable in a push server that sends a message to a mobile device over a network. The push server logic is configured to receive a GET command from a mobile device. The GET command includes a mobile device identifier parameter and a timeout parameter designating a maximum time interval for the push server to reply with a message. The push server logic holds a GET command session until expiration of a timeout designated by the timeout parameter in a condition that no message is targeted to the mobile device. The push server logic terminates the GET command session by sending a message immediately in a condition that the message is targeted to the mobile device.

Abstract: A mobile device apparatus uses an HyperText Transfer protocol (HTTP) push operation to simulate server-initiated sessions. The illustrative mobile device apparatus comprises a push server logic operable in a push server that sends a message to a mobile device over a network. The push server logic is configured to receive a GET command from a mobile device. The GET command includes a mobile device identifier parameter and a timeout parameter designating a maximum time interval for the push server to reply with a message. The push server logic holds a GET command session until expiration of a timeout designated by the timeout parameter in a condition that no message is targeted to the mobile device. The push server logic terminates the GET command session by sending a message immediately in a condition that the message is targeted to the mobile device.

Abstract: A request for a first function is detected 420. The first function is associated with a first device management protocol. A mapping 140 between a device location agnostic device management entity 110's functions and a device location limited device management entity 130's functions is accessed 430. The mapping 140 is used to translate 440 from the first function to a second function. The second function is associated with a device management protocol that is different from the first electronic device management protocol. The second function is used to provide 450 manageability to the electronic device 200B.

Abstract: Various embodiments pertain to managing electronic devices using an electronic device as a root of trust. According to one embodiment, registration information for an electronic device 150 is received 220. The registration information identifies the electronic device 150 and an environment 130 that the electronic device 150 is trusted in. The electronic device150 is specified 230 as a root of trust device 150 for the trusted environment 130 based on the registration information. The root of trust device 150 is specified 240 as the root of trust for a new electronic device 170 based on new information that identifies the root of trust device 150 and identifies the new electronic device 170. The new electronic device 170 is managed 250 using the root of trust device 150 without requiring the user of the root of trust device 150 and the new electronic device 170 to configure any electronic devices.

Abstract: Various embodiments pertain to managing electronic devices with different types of device location limited device management clients. According to one embodiment, first information describing first device capabilities 122 for a first type of device location limited device management client 126 associated with a first electronic device 120 is received. Second information describing second device capabilities 132 for a second type of device location limited device management client 136 associated with a second electronic device 130 is received. A device location agnostic device management client 124 is installed on the first electronic device 120 while communicating with the first electronic device 120 based on the first device capabilities 122. The device location agnostic device management client 134 is installed on the second electronic device 130 while communicating with the second electronic device 130 based on the second device capabilities 132.

Abstract: A mobile device apparatus uses an HyperText Transfer protocol (HTTP) push operation to simulate server-initiated sessions. The illustrative mobile device apparatus comprises a push server logic operable in a push server that sends a message to a mobile device over a network. The push server logic is configured to receive a GET command from a mobile device. The GET command includes a mobile device identifier parameter and a timeout parameter designating a maximum time interval for the push server to reply with a message. The push server logic holds a GET command session until expiration of a timeout designated by the timeout parameter in a condition that no message is targeted to the mobile device. The push server logic terminates the GET command session by sending a message immediately in a condition that the message is targeted to the mobile device.

Abstract: A user detects a computer failure. The user communicates the fact of the fault to a support server. The support server requests a central management server to access diagnostic data on the computer. The central management server accesses the diagnostic data via a lights-out module of the computer and forwards the diagnostic data to the support server.

Abstract: In one aspect, a system for providing remote electronic services to a device includes an access module and a voice interface module. The access module is configured to expose messaging/collaboration data stored on a messaging/collaboration server. The voice interface module is configured to translate messaging/collaboration service requests from a voice device for presentation to the access module and to translate a requested messaging/collaboration service deliverable from the access module for presentation to the voice device. In another aspect, a wireless interface module is configured to translate messaging/collaboration service requests from a wireless device for presentation to the access module and to translate a requested messaging/collaboration service deliverable from the access module for presentation to the wireless device. The access module also integrates fax functionality with the messaging/collaboration services provided by the messaging/collaboration server.

Abstract: A system for providing remote electronic services includes an agent, a communication module, and an access file. The agent receives request for-service-calls in any format selected from a voice format, an internet format, an e-mail format, and a wireless format, and transmits a request-for-service call to the access file in accordance with a hypertext transfer protocol for each of the received request-for-service calls. The access file invokes at least one service module in response to a given request-for-service call received from the agent. The at least one service module performs a prescribed function to produce a service deliverable requested in the given request-for-service call, accesses an instance of the communication module, and passes the one or more control parameters and the service deliverable to the communication module.