Abstract: A system for managing a plurality of assets and a plurality of parties related to those assets includes a plurality of data sources with information related to the parties and the service of the assets and a first service management server. The service management server may be configured as first and second servers with different functionalities. The service management server, or the first and second service management servers, is configured to collect the data from the plurality of data sources related to the parties and the service of the assets; and is configured to determine maintenance or service requirements for the assets, collect and distribute asset specific data for managing the service requirements of the assets, facilitate communication between parties to a service event, and maintain current and historical data about the service event.

Abstract: A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture enables use of multiple instances of a notification process, each configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. Each notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. Each notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference.

Abstract: An application server is configured for initiating a messaging session for an incoming call by accessing a subscriber profile information from a directory server and a subscriber announcement from a messaging server. The application server includes a fault tolerant routine for initiating a messaging session, enabling playing of the subscriber's spoken name during the messaging session based on a determined unavailability of the messaging server. The subscriber announcement and the subscriber's spoken name (or another audible subscriber identifier) are stored in the messaging server as first and second data files having first and second sizes, respectively, where the second size is substantially smaller than the first size. The second data file also is stored in the directory server with the subscriber profile information.

Abstract: A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference.

Abstract: A method is provided in an application server configured for responding to hypertext transport protocol (HTTP) requests. The method includes storing, in response to a first HTTP request, an XML document that specifies for a user, a call number of a second party. The stored XML document is retrieved based on a second HTTP request by the user. A first HTML document is generated based on the retrieved XML document. The first HTML document has instructions including the call number for accessing the second party. A second HTML document is generated based on a prescribed input received from the second party. The second HTML document has instructions for connecting the second party with the user. Hence, a user may speak with a called party without ever having to remain on hold.

Abstract: A method is provided in an application server configured for responding to hypertext transport protocol (HTTP) requests. The method includes storing, in response to a first HTTP request, an XML document that specifies for a user, a call number of a second party. The stored XML document is retrieved based on a second HTTP request by the user. A first HTML document is generated based on the retrieved XML document. The first HTML document has instructions including the call number for accessing the second party. A second HTML document is generated based on a prescribed input received from the second party. The second HTML document has instructions for connecting the second party with the user. Hence, a user may speak with a called party without ever having to remain on hold.

Abstract: A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture enables use of multiple instances of a notification process, each configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. Each notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. Each notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference.

Abstract: A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture enables use of multiple instances of a notification process, each configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. Each notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. Each notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference.

Abstract: A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference.

Abstract: A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The notification process determines, for each received notification message, the subscriber's notification preference based on the accessed profile information, and selectively outputs a notification delivery message according to a prescribed open protocol to at least one notification delivery process within the notification architecture based on the subscriber's notification preference.

Abstract: A notification architecture utilizes multiple processes configured for managing notification operations based on reception of SMTP-based messages within IMAP based message stores. The notification architecture includes a notification process, configured for receiving notification messages for respective subscribers from messaging sources according to a prescribed open protocol such as Internet Protocol. The notification process accesses subscriber profile information from an open protocol-based subscriber directory based on the received notification messages. The subscriber directory is controlled by a directory management process, configured for storing subscriber notification preference information in an open protocol-based subscriber directory (such as LDAP). The directory management process stores, as a first object class, notification attributes for respective notification types, each notification attribute specifying for the corresponding notification type a corresponding notification device tag.