Abstract: A method for error management is provided. The method comprises receiving a message call request regarding an error event generated by a software application. The message call request comprises a message ID associated with an error type. In response to the call request a message cache is searched for the message ID. If the ID is in the cache, an error message associated with the ID is returned. The error message provides a description of the error and suggested remedial action. If the message ID is not in the cache, the error message is fetched from a message repository that contains error messages corresponding to respective message IDs. The fetched error message is loaded into the cache and returned. Message call request data is stored in a metrics repository. The message call request data comprises frequency metrics that describe how often the message ID is received.

Abstract: A method for error management is provided. The method comprises receiving a message call request regarding an error event generated by a software application. The message call request comprises a message ID associated with an error type. In response to the call request a message cache is searched for the message ID. If the ID is in the cache, an error message associated with the ID is returned. The error message provides a description of the error and suggested remedial action. If the message ID is not in the cache, the error message is fetched from a message repository that contains error messages corresponding to respective message IDs. The fetched error message is loaded into the cache and returned. Message call request data is stored in a metrics repository. The message call request data comprises frequency metrics that describe how often the message ID is received.

Abstract: A method for error management is provided. The method comprises receiving a message call request regarding an error event generated by a software application. The message call request comprises a message ID associated with an error type. In response to the call request a message cache is searched for the message ID. If the ID is in the cache, an error message associated with the ID is returned. The error message provides a description of the error and suggested remedial action. If the message ID is not in the cache, the error message is fetched from a message repository that contains error messages corresponding to respective message IDs. The fetched error message is loaded into the cache and returned. Message call request data is stored in a metrics repository. The message call request data comprises frequency metrics that describe how often the message ID is received.

Abstract: Some demonstrative embodiments include devices, systems and methods of Wireless Local Area Network (WLAN) setting of a User Equipment (UE). For example, a UE may include a Wireless Local Area Network (WLAN) transceiver to communicate with a WLAN; a cellular transceiver to communicate with a cellular network; a user interface to provide a user with a plurality of WLAN setting options and to receive an indication of a selected WLAN setting from the plurality of WLAN setting options; and a connection manager to cause the WLAN transceiver to operate according to the selected WLAN setting.

Abstract: Some demonstrative embodiments include devices, systems and methods of Wireless Local Area Network (WLAN) setting of a User Equipment (UE). For example, a UE may include a Wireless Local Area Network (WLAN) transceiver to communicate with a WLAN; a cellular transceiver to communicate with a cellular network; a user interface to provide a user with a plurality of WLAN setting options and to receive an indication of a selected WLAN setting from the plurality of WLAN setting options; and a connection manager to cause the WLAN transceiver to operate according to the selected WLAN setting.

Abstract: Example methods, apparatus and articles of manufacture (e.g., physical storage media) to perform real-time cost management for utilities are disclosed. Disclosed example methods for real-time utility cost management include displaying, on a display associated with an appliance, utility pricing data received via a network. Such disclosed example methods also include, after displaying the utility pricing data, determining, based on a first input received via a user interface associated with the appliance, whether remote control of the appliance is permitted. Such disclosed example methods further include, in response to determining that remote control of the appliance is permitted, delaying activation of an operation of the appliance until receipt of a first command via the network.