# Patent

## Title
Presence-based event driven architecture

## Abstract

Embodiments of the invention provide systems and methods for using a presence-based network to monitor systems, devices, or agents. According to one embodiment, monitoring a system can comprise receiving a publication of one or more presence attributes from a presence network agent. The presence attributes can comprise at least one attribute indicating information other than presence information. A presence profile associated with the presence network agent can be updated based on the received presence attributes. One or more of the presence attributes of the presence profile associated with the presence network agent can be provided to a listener. For example, providing presence attributes to the listener can comprise providing a notification of a change in the at least one presence attribute. Additionally or alternatively, a request can be received from the listener for one or more presence attributes and the presence attribute can be provided in response to the request.

## Background
CROSS-REFERENCES TO RELATED APPLICATIONS
Background of the Invention
Embodiments of the present invention relate generally to methods and systems for monitoring of systems, devices, or agents and more particularly to using a presence-based network for monitoring of systems, devices, or agents.
As the pace of business increases, companies are being forced to more quickly sense and respond to changes, threats and opportunities in the markets they serve, their supply chain and their internal operations. Each of these changes, threats and opportunities manifests itself as an event, i.e., a record of something that has happened. An Event-Driven Architecture (EDA) is an architectural paradigm based on using events as triggers that initiate the delivery of a message that informs numerous recipients about the event so they can take appropriate action. When used with event management, the collection of events can be analyzed and correlated to identify relevant patterns or non-patterns, and then aggregated to build up information that is needed to proactively prevent future problems. An EDA can be implemented on or using an Enterprise Service Bus (ESB). Generally speaking, an ESB is a framework built upon any of a variety of different standard or propriety protocols for interconnecting and providing communications between elements (i.e., applications, devices, systems, etc.) of an architecture such as an EDA.
However, such systems present problems in their implementation. For example, it is complicated to develop an EDA and integrate it with applications and/or middleware. Additionally, it is complicated to manage appropriate real-time performances of the EDA and minimize delay in handling events and responses. Furthermore, scalability/extensibility of an EDA can be limited or at least very difficult. Also, EDA systems are stateless. That is, they treat each transaction as independent and do not persist the transaction beyond its initial handling. Hence, there is a need for improved methods and systems for monitoring of systems, devices, or agents in a real-time or other system.
BRIEF SUMMARY OF THE INVENTION
Embodiments of the invention provide systems and methods for using a presence-based network to monitor systems, devices, or agents. For example, embodiments of the present invention provide for use of a presence network to implement systems such as an event driven architecture. Since presence data models as used with eXtensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol (SIP), SIP Instant Messaging and Presence Leveraging Extensions (SIP/SIMPLE), Open Mobile Alliance (OMA) SIP/SIMPLE presence eXtensible Markup Language (XML) Document Management (XDM) enablers etc. are extensible (i.e. new attributes can be defined), a presence attribute can be defined for any type of information of a system to be monitored that can then be used, i.e., published/subscribed, as with other presence attributes. However, it should be noted that embodiments of the present invention are not limited to use with SIP/SIMPLE, XMPP, or any other specific protocol. Rather, embodiments of the present invention can be implemented using any other presence solution including, for example, Instant Messaging and Presence Service (IMPS)/Wireless village, Parlay/Network presence, and presence associated with Multimedia IM messages like Skype, Google Talk, MSN messenger, Y!, AIM etc.
Regardless of the exact protocols and/or presence solution used, when the information of the monitored system changes or another event occurs, the presence attributes in the presence profile of that system can be updated and the update can be published to authorized subscribers, for example via a presence server. It should be understood that the attributes can be generalized in many different ways and need not be limited to a state or status of a monitored device or process. Rather, the attributes can be any multimedia document (e.g. XML or “XMLized” binary documents) or a URI to one or more documents or streams.
According to one embodiment, a system can comprise a presence network agent. The presence network agent can be adapted to publish one or more presence attributes which can comprise at least one attribute indicating information other than presence information. Presence information is that information indicating a transient state of an entity that can be used by others to determine how to best contact that entity. A presence server can be communicatively coupled with the presence network agent. The presence server can be adapted to receive the published presence attributes and update a presence profile associated with the presence network agent based on the received presence attributes. The presence server can also be adapted to apply one or more policies. In such cases, updating the presence profile associated with the presence network agent based on the received presence attributes can be further based on the one or more policies. According to one embodiment, when implemented with OMA SIP/SIMPLE these functions can be split between XDM enablers and presence enablers.
The system can further comprise a listener communicatively coupled with the presence server and adapted to receive presence attributes from the presence server. The presence server can be adapted to provide at least one of the one or more presence attributes of the presence profile associated with the presence network agent to the listener. Providing at least one of the one or more presence attributes to the listener can be based on the presence server applying one or more policies. For example, the listener can be adapted to subscribe to one or more presence attributes of the presence profile associated with the presence network agent. In such a case, the presence server can provide the subscribed presence attributes to the listener by providing a notification of a change in the at least one presence attribute. In another example, the listener can be adapted to request the presence attributes from the presence server. In such a case, the presence server can provide the presence attribute to the listener in response to the request. In either case, the listener can comprise a handler adapted to process the presence attributes received from the presence server.
The information other than presence information can comprise, for example, event information from or a status of the monitored system or process. Additionally or alternatively, the information other than presence information can comprise, for example, a multimedia document, a URI to a document or stream, etc. In the case of event information, the presence server can be further adapted to provide or implement an Event Driven Architecture (EDA) based on the event information. The EDA can be adapted to provide real-time monitoring of a device associated with the presence network agent. In some cases, the presence attributes can further comprise at least one attribute indicating presence information. So, for example, the EDA can provide tracking of the device, e.g., a Radio Frequency IDentification (RFID) tag, associated with the presence network agent based on the at least one attribute indicating presence information (e.g., a sensor on a device/user to provide presence information when the user is “manning” the device). In another example, the device associated with the presence network agent can comprise a sensor and the EDA can be adapted to perform process monitoring based on at least one of the presence attributes. In still another example, the EDA can be adapted to provide real-time monitoring of a process associated with the presence network agent and provide a notification of a change in status of the process based on one or more of the presence attributes.
According to another embodiment, a method of monitoring a system can comprise receiving a publication of one or more presence attributes from a presence network agent. The presence attributes can comprise at least one attribute indicating information other than presence information. A presence profile associated with the presence network agent can be updated based on the received presence attributes. One or more policies can be applied to the presence attributes. Updating the presence profile associated with the presence network agent can be based on applying the one or more policies. At least one of the one or more presence attributes of the presence profile associated with the presence network agent can be provided to a listener. Providing the presence attributes to the listener can also be based at least in part on applying the one or more policies. For example, providing at least one of the one or more presence attributes of the presence profile associated with the presence network agent to the listener can comprise providing a notification of a change in the at least one presence attribute. Additionally or alternatively, a request can be received from the listener for at least one of the one or more presence attributes of the presence profile associated with the presence network agent and the at least one presence attribute to the listener can be provided in response to the request.
In some cases, the information other than presence information can comprise event information. In such cases, an Event Driven Architecture (EDA) can be provided or implemented based on the event information. For example, providing the EDA can comprise providing real-time monitoring of a device, system, or application associated with the presence network agent. In some cases, the presence attributes can further comprise at least one attribute indicating presence information. Generally, such an EDA can, via Short Message Peer-to-Peer (SMPP) protocol, Java Management Extensions (JMX), or other monitoring protocol, provide an event or indication of an event to the presence network agent which in turn provides the event of indication of the event to the presence server to be published as a presence attribute to one or more subscribers and/or otherwise provided to one or more authorized users/monitors. So, for example, providing the EDA can comprise providing tracking of the device associated with the presence network agent based on the at least one attribute indicating presence information. In another example, the device associated with the presence network agent can comprise a sensor. In such cases, providing the EDA can comprise performing process monitoring based on at least one of the presence attributes. In yet another example, providing the EDA can comprise providing real-time monitoring of a process associated with the presence network agent and providing a notification of a change in status of the process based on one or more of the presence attributes.
In yet another embodiment, a machine-readable medium can have stored thereon a series of instructions which, when executed by a processor, cause the processor to monitor a system by receiving a publication of one or more presence attributes from a presence network agent. The presence attributes can comprise at least one attribute indicating information other than presence information. A presence profile associated with the presence network agent can be updated based on the received presence attributes. At least one of the one or more presence attributes of the presence profile associated with the presence network agent can be provided to a listener. A presence profile associated with the presence network agent can be updated based on the received presence attributes. One or more policies can be applied to the presence attributes. Updating the presence profile associated with the presence network agent can be based on applying the one or more policies. At least one of the one or more presence attributes of the presence profile associated with the presence network agent can be provided to a listener. Providing the presence attributes to the listener can also be based at least in part on applying the one or more policies.
For example, providing at least one of the one or more presence attributes of the presence profile associated with the presence network agent to the listener can comprise providing a notification of a change in the at least one presence attribute. Additionally or alternatively, a request can be received from the listener for at least one of the one or more presence attributes of the presence profile associated with the presence network agent and the at least one presence attribute to the listener can be provided in response to the request. In one implementation, the information other than presence information can comprise event information. In such a case, an Event Driven Architecture (EDA) can be implemented based on the event information. In such an EDA or in other embodiments of the present invention, the listener or other element monitoring the system or element(s) of the system can therefore comprise simple client devices such as cell phones, pagers, etc that are commonly adapted to use presence information. That is any client device able to receive a notification of a change in the presence attributes or query to obtain the presence attributes can be used in the EDA or other embodiments of the present invention to monitor various devices, systems, applications, etc.
According to still another embodiment, a stateful Event Driven Architecture (EDA) can comprise a network, a monitored device, a profile associated with the monitored device, the profile comprising one or more attributes associated with monitored information, and a policy enforcement module adapted to persist one or more of the attributes based on one or more policies. The policy enforcement module can be further adapted to expire one or more of the attributes based on the one or more policies. The profile can comprise a presence profile and the attributes can comprise presence attributes. In some cases, the EDA can further comprise a stateful Enterprise Service Bus (ESB).
For example, the EDA can comprise a presence server communicatively coupled with the network and can be adapted to receive the one or more presence attributes via the network and update the presence profile based on the received presence attributes. The monitored device can comprise a presence network agent adapted to publish the one or more presence attributes to the presence server. The presence network agent can be adapted to receive monitored information from the network and publish the one or more presence attributes in response to receiving the monitored information. Additionally or alternatively, the presence network agent can be adapted to request monitored information from the network, receive the monitored information in response to the request, and publish the one or more presence attributes in response to receiving the monitored information.
The EDA can further comprise a listener communicatively coupled with the presence server and adapted to receive presence attributes from the presence server. The listener can be adapted to subscribe to the at least one of the one or more presence attributes of the presence profile. The presence server can provide the at least one presence attribute to the listener by providing a notification of a change in the at least one presence attribute. Additionally or alternatively, the listener can be adapted to request the presence attributes from the presence server and he presence server can provide the at least one presence attribute to the listener in response to the request. The listener can comprise a handler adapted to process the presence attributes received from the presence server.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram illustrating components of an exemplary operating environment in which various embodiments of the present invention may be implemented.
FIG. 2 is a block diagram illustrating an exemplary computer system in which embodiments of the present invention may be implemented.
FIG. 3 is a block diagram illustrating, at a high-level, functional components of a system for monitoring a system according to one embodiment of the present invention.
FIG. 4 is a flowchart illustrating a process for monitoring a system according to one embodiment of the present invention.
FIG. 5 is a flowchart illustrating a process for monitoring a system according to an alternative embodiment of the present invention.
FIG. 6 is a flowchart illustrating a process for monitoring a system according to on embodiment of the present invention.
FIG. 7 is a flowchart illustrating a process for monitoring a system according to an alternative embodiment of the present invention.
FIG. 8 is a flowchart illustrating additional details of a process for monitoring a system according to an alternative embodiment of the present invention.
FIG. 9 is a block diagram illustrating additional details of an exemplary implementation of a system according to one embodiment of the present invention.
FIG. 10 is a block diagram illustrating, at a high-level, functional components of a system for monitoring a system according to an alternative embodiment of the present invention.



DETAILED DESCRIPTION OF THE INVENTION
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of various embodiments of the present invention. It will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.
The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth in the appended claims.
Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
The term “machine-readable medium” includes, but is not limited to portable or fixed storage devices, optical storage devices, wireless channels and various other mediums capable of storing, containing or carrying instruction(s) and/or data. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine readable medium. A processor(s) may perform the necessary tasks.
Embodiments of the invention provide systems and methods for using a presence-based network for monitoring of systems, devices, or agents. More specifically, embodiments of the present invention provide for use of a presence network to implement systems such as an Event Driven Architecture (EDA) by extending a presence profile to include attributes indicating information other than or in addition to presence information. Presence information as conventionally defined is a transient state of a principal that can be used by other entities to make a decision about how to best communicate with the principal. A principal can be defined as an entity that has an identity, that is capable of providing consent and other data, and to which authenticated actions are done on its behalf. Thus, as will be described in detail below, a principal, referred to herein as a monitored system or device, can be any device, system, agent, application, individual, etc. Furthermore, the presence attributes described herein are not limited to identifying or indicating presence information. Rather, embodiments of the present invention provide for using presence attributes to identify or indicate any type of information related to the principal. For example, such information can include but is not limited to a state or status of a device or process, a reading or measurement from a device such as a sensor, information collected or generated by an application or process, etc, as well as presence information. Additionally or alternatively, information indicated by the presence attributes can include other types of information. For example, information indicated by one or more presence attributes can include but is not limited to a multimedia document, a Uniform Resource Identifier (URI) to a document of stream, etc.
Since presence data models as used with Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol (SIP), SIP Instant Messaging and Presence Leveraging Extensions (SIMPLE), OMA SIP/SIMPLE presence XML Document Management (XDM) enablers etc. are extensible (i.e. new attributes can be defined), a presence attribute can be defined for any type of information of a device, system, agent, or other entity to be monitored that can then be used, i.e., published/subscribed. However, as noted above, embodiments of the present invention are not limited to use with SIP/SIMPLE, XMPP, or any other specific protocol. Rather, embodiments of the present invention can be implemented using any other presence solution including, for example, Instant Messaging and Presence Service (IMPS)/Wireless village, Parlay/Network presence, and presence associated with Multimedia IM messages like Skype, Google Talk, MSN messenger, Y!, AIM etc. Regardless of the exact protocol and/or presence solution used, presence information can be obtained using a subscribe/publish model wherein a principal publishes presence attributes to a presence server which in turn notifies authorized subscribers, referred to herein as listeners, of the information or change of information. Thus, when the information of the monitored system changes or another event occurs, the presence attributes in the presence profile of that system can be updated and the update can be published to authorized listeners via a presence server. Additionally or alternatively, presence information can be obtained from the presence server by the listener interrogating or querying the server which in turn responds to the query. According to one embodiment, presence information can additionally or alternatively be published by a presence network agent. Such a presence network agent can additionally or alternatively be adapted to monitor the system or elements of the system by receiving notifications or querying the system for presence attributes.
As will be described below, updating the presence profile, notifying subscribers/listeners, and/or responding to queries, etc. can be subject to the application of one or more policies by the presence server. As used herein the term policy refers to a combination of one or more conditions and a set of one or more associated actions to be performed upon the condition(s) being satisfied. That is, the policies can define conditions to be met and corresponding actions to be taken when receiving a publication of a presence attribute, notifying subscribers/listeners, responding to queries, etc. For example, the policies can define which subscribers or listeners are authorized to receive a notification or access a presence profile or attribute. Additionally or alternatively, the policies can define conditions and actions for use by the presence service to determine what information is shown to who, how is it transformed, under what conditions etc. Other possible policies, i.e., any combination of any condition and any action, are contemplated and considered to be within the scope of the present invention. According to one embodiment, application of policies, handling of events, and implementation of the attributes can be performed as described in U.S. patent application Ser. No. 11/424,451 filed Jun. 15, 2006 by Maes and entitled “Past Presence Hints” the entire disclosure of which is incorporated herein by reference for all purposes. That is, presence attributes as described herein can represent past presence hints or information as described in the referenced application and can be treated according to the embodiments described therein including but not limited to possible expiration of attributes etc.
As noted above and as will be described in detail below, systems built or implemented using embodiments of the present invention can include but are not limited to an EDA. Generally speaking an EDA implemented on a presence network according to embodiments of the present invention can provide for handling an event published as a presence attribute by a principal. So for example, a presence agent or other event source can publish a presence attribute indicating an event and/or other information to a presence server. The presence server, based on the application of policies, can handle the event by notifying one or more listeners/subscribers. That is, the presence server can apply one or more policies to determine which listeners/subscribers to inform or notify, whether and/or how to transform the event, etc. The presence server can then provide the presence attributes to the listener/subscribers based on the applied policies. Each or some of the listeners can include a handler for further processing or handling of the event notification. Systems implemented in this way can include, by way of example and not limitation, systems for monitoring and/or controlling a system, process, application, etc., systems for handling or controlling communications, etc.
As will be described, embodiments of the present invention can implement an Enterprise Service Bus (ESB). According to one embodiment, when implementing an ESB on a presence based EDA, listeners on the bus can subscribe to sources/attributes. The presence server can transform incoming events based on policies or may give raw outputs. In such cases, handlers can perform any dedicated transformation as appropriate. According to one embodiment, application of policies by the presence server can be performed in accordance with embodiments described in the application entitled Past Presence Hints referenced above to provide or control expiration of presence attributes. Accordingly, expiration of state information or other presence attributes can occur instantly or after some amount of time. That is, a “stateful” EDA can be implemented in which state and/or attribute persistence can be managed or expired to provide no persistence or some persistence based on the policies defined. Therefore, a notion of an EDA including persistence and/or a persistent ESB and the possibilities provided thereby are described. Additional details of various embodiments of the present invention will be described below with reference to the figures.
FIG. 1 is a block diagram illustrating components of an exemplary operating environment in which various embodiments of the present invention may be implemented. The system 100 can include one or more user computers 105, 110, which may be used to operate a client, whether a dedicate application, web browser, etc. The user computers 105, 110 can be general purpose personal computers (including, merely by way of example, personal computers and/or laptop computers running various versions of Microsoft Corp.'s Windows and/or Apple Corp.'s Macintosh operating systems) and/or workstation computers running any of a variety of commercially-available UNIX or UNIX-like operating systems (including without limitation, the variety of GNU/Linux operating systems). These user computers 105, 110 may also have any of a variety of applications, including one or more development systems, database client and/or server applications, and web browser applications. Alternatively, the user computers 105, 110 may be any other electronic device, such as a thin-client computer, Internet-enabled mobile telephone, and/or personal digital assistant, capable of communicating via a network (e.g. the network 115 described below) and/or displaying and navigating web pages or other types of electronic documents. Although the exemplary system 100 is shown with two user computers, any number of user computers may be supported.
In some embodiments, the system 100 may also include a network 115. The network may can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, the network 115 maybe a local area network (“LAN”), such as an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network (e.g., a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth protocol known in the art, and/or any other wireless protocol); and/or any combination of these and/or other networks such as GSM, GPRS, EDGE, UMTS, 3G, 2.5 G, CDMA, CDMA2000, WCDMA, EVDO etc.
The system may also include one or more server computers 120, 125, 130 which can be general purpose computers and/or specialized server computers (including, merely by way of example, PC servers, UNIX servers, mid-range servers, mainframe computers rack-mounted servers, etc.). One or more of the servers (e.g., 130) may be dedicated to running applications, such as a business application, a web server, application server, etc. Such servers may be used to process requests from user computers 105, 110. The applications can also include any number of applications for controlling access to resources of the servers 120, 125, 130.
The web server can be running an operating system including any of those discussed above, as well as any commercially-available server operating systems. The web server can also run any of a variety of server applications and/or mid-tier applications, including HTTP servers, FTP servers, CGI servers, database servers, Java servers, business applications, and the like. The server(s) also may be one or more computers which can be capable of executing programs or scripts in response to the user computers 105, 110. As one example, a server may execute one or more web applications. The web application may be implemented as one or more scripts or programs written in any programming language, such as JavaTM, C, C# or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages. The server(s) may also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, IBM® and the like, which can process requests from database clients running on a user computer 105, 110.
In some embodiments, an application server may create web pages dynamically for displaying on an end-user (client) system. The web pages created by the web application server may be forwarded to a user computer 105 via a web server. Similarly, the web server can receive web page requests and/or input data from a user computer and can forward the web page requests and/or input data to an application and/or a database server. Those skilled in the art will recognize that the functions described with respect to various types of servers may be performed by a single server and/or a plurality of specialized servers, depending on implementation-specific needs and parameters.
The system 100 may also include one or more databases 135. The database(s) 135 may reside in a variety of locations. By way of example, a database 135 may reside on a storage medium local to (and/or resident in) one or more of the computers 105, 110, 115, 125, 130. Alternatively, it may be remote from any or all of the computers 105, 110, 115, 125, 130, and/or in communication (e.g., via the network 120) with one or more of these. In a particular set of embodiments, the database 135 may reside in a storage-area network (“SAN”) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers 105, 110, 115, 125, 130 may be stored locally on the respective computer and/or remotely, as appropriate. In one set of embodiments, the database 135 may be a relational database, such as Oracle 10g, that is adapted to store, update, and retrieve data in response to SQL-formatted commands.
FIG. 2 illustrates an exemplary computer system 200, in which various embodiments of the present invention may be implemented. The system 200 may be used to implement any of the computer systems described above. The computer system 200 is shown comprising hardware elements that may be electrically coupled via a bus 255. The hardware elements may include one or more central processing units (CPUs) 205, one or more input devices 210 (e.g., a mouse, a keyboard, etc.), and one or more output devices 215 (e.g., a display device, a printer, etc.). The computer system 200 may also include one or more storage device 220. By way of example, storage device(s) 220 may be disk drives, optical storage devices, solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like.
The computer system 200 may additionally include a computer-readable storage media reader 225a, a communications system 230 (e.g., a modem, a network card (wireless or wired), an infra-red communication device, etc.), and working memory 240, which may include RAM and ROM devices as described above. In some embodiments, the computer system 200 may also include a processing acceleration unit 235, which can include a DSP, a special-purpose processor and/or the like.
The computer-readable storage media reader 225a can further be connected to a computer-readable storage medium 225b, together (and, optionally, in combination with storage device(s) 220) comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing computer-readable information. The communications system 230 may permit data to be exchanged with the network 220 and/or any other computer described above with respect to the system 200.
The computer system 200 may also comprise software elements, shown as being currently located within a working memory 240, including an operating system 245 and/or other code 250, such as an application program (which may be a client application, web browser, mid-tier application, RDBMS, etc.). It should be appreciated that alternate embodiments of a computer system 200 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed. Software of computer system 200 may include code 250 for implementing embodiments of the present invention as described herein.
FIG. 3 is a block diagram illustrating, at a high-level, functional components of a system for monitoring a system according to one embodiment of the present invention. Generally speaking, the system 300 of this example illustrates a presence network that can be adapted to provide for monitoring of systems, devices, or agents. More specifically, the system 300 includes a communications network 335. The communications network 335 can comprise any type of network such as described above. A number of devices 345 and 350 can be communicatively coupled with the communications network 335. The devices 345 and 350 can include a monitored device 345 and a listener 350. Additionally or alternatively, the system 300 can include an application 360 and/or another subscriber 355 device or system 355 communicatively coupled with the communications network 335.
Generally speaking, the monitored device 345 can comprise any device, system, application, etc. that is to be monitored and the listener 350 can be any device, system, application etc that can receive and/or react to information provided by or relating to the monitored device 345. It should be noted that the names monitored device and listener are used only to illustrate a particular device's function at a given time and are not meant to imply any limitations on the functions that can be performed by a given device. That is, any given device, system, or application can alternately or concurrently act as a monitored device 345 or listener 350.
The system can also include a presence server 305 communicatively coupled with the communications network 335. The presence server 305 can include a presence enabler 310. It should be noted that the presence enabler 310 can comprise any one or more of a number of different enablers. For example, the presence enabler 310 can comprise an XDM enabler, a Resource List Server (RLS) enabler, or other presence enabler. Furthermore, multiple enablers may be utilized and provide internal decomposition of functions between the different enablers. Any or all such enablers are considered to be represented by presence enabler 310 and are considered to be within the scope of the present invention. It should be noted and understood that, while described herein with reference to OMA SIP/SIMPLE presence and XDM enablers, other presence server approaches can be used depending upon the exact implementation and are considered to be within the scope or the present invention. Furthermore, embodiments of the present invention do not depend upon any particular technology for implementing the presence enabler, presence server, or the presence network and the exact technology used can vary depending upon the implementation without departing from the scope of the present invention.
As noted above, the presence service provided via the presence enabler 310 of the presence server 305 can maintain a set of presence profiles 325 for any number of principals participating in the service. For example, a presence profile 325 can be maintained for or related to the monitored device 345. The presence profile 325 can include a set of one or more presence attribute 326. The presence attributes 326 can include attributes identifying or related to presence information as noted above. However, the presence attributes 326 described herein are not limited to identifying or indicating presence information. Rather, embodiments of the present invention provide for using presence attributes 326 to identify or indicate any type of information related to the principal such as the monitored device 345. For example, such information can include but is not limited to a state or status, information collected or generated by an application or process, etc, as well as presence information. Additionally or alternatively, information indicated by the presence attributes can include other types of information. For example, information indicated by one or more presence attributes can include but is not limited to a multimedia document, a Uniform Resource Identifier (URI) to a document of stream, etc.
The monitored device 345 can be adapted to maintain or execute a presence agent 346. The presence agent 346 can be adapted to publish one or more presence attributes 326 to the presence profile 325 maintained by the presence server 305 and associated with the monitored device and/or presence agent 346. As noted above, the presence attribute(s) 326 published to the presence server 305 by the presence network agent 346 can comprise at least one attribute indicating information other than presence information. For example, such information can comprise state or status information of the monitored device 345 or process thereof, a reading or measurement from the monitored device 345 such as a sensor reading or measurement, information collected or generated by an application or process of the monitored device 345, etc.
The presence attributes 326 can be published to the presence server 305 by the presence agent 345 via any appropriate method, message, or signal of the underlying protocol of the communications network 335. For example, embodiments of the present invention, while not so limited, may be implemented on Session Initiation Protocol (SIP)/SIP Instant Messaging and Presence Leveraging Extensions (SIMPLE). In such cases, the presence network agent 346 can publish the presence attributes using the known SIP/SIMPLE “PUBLISH” method. However, it should be understood that use of this protocol and method is offered by way of example only and not limitation. In other implementations, various other protocols and methods may be used.
The presence server 305 can be adapted to receive the published presence attribute(s) 326 and update the presence profile 325 associated with the presence network agent 346 based on the received presence attribute(s) 326. The presence server 305, for example via policy enforcement module 315 of the presence enabler 3160, can also be adapted to apply one or more policies 320. In such cases, updating the presence profile 325 associated with the presence network agent 346 based on the received presence attribute(s) 326 can be further based on the one or more policies 320. For example, such policies can define when, how, under what conditions, etc., the presence attributes 326 can be updated.
As noted, the system 300 can also comprise a listener 350 communicatively coupled with the presence server 305 via the communications network 335. The listener can comprise any type of system, device, application, etc. and can be adapted to receive presence attributes 326 from the presence server 305. The presence server 305 can be adapted to provide at least one of the one or more presence attributes 326 of the presence profile 325 associated with the presence network agent 346 to the listener 350. For example, providing presence attributes 326 to the listener 350 can be based on a subscribe/notify model. That is, the listener 350 can be adapted to subscribe to one or more presence attributes 326 of the presence profile 325 associated with the presence network agent 346. In such a case, the presence server 305 can provide the subscribed presence attributes 326 to the listener 350 by providing a notification of a change in the presence attribute. Additionally or alternatively, the notification can be provided to application 360 and/or another subscriber 355. For example, the application 360 and/or other subscriber 355, via a user agent 356, can subscribe to the one or more presence attributes 326 of the presence profile 325 associated with the presence network agent 346 and in turn receive notification of changes in the presence attribute.
In another example, the listener 350 and/or application 360 can be adapted to request the presence attributes 326 from the presence server 305, for example via a northbound interface of the presence enabler such as an interface including but not limited to a Parlay X presence interface. The presence server 305 can provide the presence attribute 326 to the listener 350 in response to the request. The listener can include a handler 351 or other application or process for further handling of the presence attribute(s) provided by the presence server 305. That is, the handler 351 of the listener 350 may perform further processing to, for example, inform a user of the listener 350 of the attribute(s), initiate a communication, perform actions to control a process based on the attribute(s), etc.
The presence attributes 326 can be published or provided by the presence server 305 to the listener 350 via any appropriate method, message, or signal of the underlying protocol of the communications network 335. For example, embodiments of the present invention, while not so limited, may be implemented on Session Initiation Protocol (SIP). In such cases, the presence server 305 can provide the notification to the listener using the known SIP “NOTIFY” message. In another example, a request and response between the listener and presence server can be implemented using the known Hyper Text Transfer Protocol (HTTP) “GET” and “PUT” methods.
Regardless of the exact implementation, providing presence attributes to the listener 350, application 360, and/or other subscriber 355, either as a notification or in response to a request, can be based on the presence server 305 applying one or more policies 320, for example via policy enforcement module 315 of the presence enabler 310. The policies 320 can define, for example, which subscribers or listeners 350 are authorized to receive a notification or access a presence profile 325 or attribute. Additionally or alternatively, the policies 320 can define conditions and actions for use by the presence server 305 to determine what information is shown to who, how is it transformed, under what conditions etc. Other possible policies 320, i.e., any combination of any condition and any action, are contemplated and considered to be within the scope of the present invention. As noted, application of policies and handling of events can be performed as described in the application entitled “Past Presence Hints” referenced above to provide, for example, expiration of attributes etc.
Generally speaking an Event Driven Architecture (EDA) implemented on a presence network according to embodiments of the present invention can provide for handling an event published as a presence attribute 326 by a principal, i.e., by a presence network agent 346. Generally, such an EDA can provide the features and functions of a typical EDA and can include, based on the application of policies by the presence server, persistence and state management for the event. Therefore, a richer, stateful EDA and/or ESB can be implemented. So for example, a presence network agent 346 can publish a presence attribute 326 indicating an event and/or other information to a presence server 305. The presence server 305, based on the application of policies 320, can handle the event by notifying one or more listeners 350 or subscribers. Furthermore, the event can be persisted, or not, based on the application of the policies. Expiration of the events or attributes can also be managed based on policies that expire, filter, change the attributes. Each or some of the listeners 350 can include a handler 350 for further processing or handling of the event notification. Systems implemented in this way can include, by way of example and not limitation, systems for monitoring and/or controlling a system, process, application, etc., systems for handling or controlling communications, etc.
In another example, a user agent 356 operating on a subscriber device 355 can be adapted to subscribe to and receive notifications of changes to presence attributes 326 published by a principal. Thus, the user agent 356 can be adapted to monitor one or more presence attributes for administration and/or management purposes. For example, the user agent 356 can be a “watcher” that can be present on any device or application. Therefore, a status or update for a monitored system can be provided to any device that has a user agent 356 or “watcher.”
In yet another example, an application 360 can be adapted to query the presence server 305 to obtain one or more presence attributes 326 of a principal. In such a case, the presence server 305 can receive the query or request from the application 360 and respond with the requested attributes. The application 360 can then use the returned attributes, for example, to test whether/when to update/report a status of the monitored system, application, device, etc. As noted, the response by the presence server 305 may be based on application on one or more policies 320. That is, the policies 320 can define whether the requester is authorized to access the presence profile 325 and/or requested attribute. Additionally or alternatively, the policies 320 can define conditions and actions for use by the presence server 305 to determine what information is shown, how is it transformed, under what conditions etc. Other possible policies, i.e., any combination of any condition and any action, are contemplated and considered to be within the scope of the present invention.
Furthermore, as noted above, the presence attributes 326 maintained by the presence server 305 can comprise other types of content, i.e., other than a state or status of a monitored system, application, device, etc. For example, the presence attributes can comprise information indicating or including a multimedia document (e.g. XML or “XMLized” binary documents). Additionally or alternatively, the presence attributes can comprise a URI to one or more documents or streams, for example, provided by or through a media server (not shown here) or other system.
As noted above, the presence server 305, based on application of the policies 320, can provide persistence and state management for the events. So for example, a presence network agent 346 can publish a presence attribute 326 indicating an event and/or other information to a presence server 305. The presence server 305, based on the application of policies 320, can handle the event by notifying one or more listeners 350 or subscribers. Furthermore, the event can be persisted, or not, based on the application of the policies 320. Therefore, when a listener 350 or subscriber 355 connects with the network 335, it can be provided with past, persisted events, if any. Such events can be persisted for a time defined by the policies after which the events are expired as described in the application entitled Past Presence hints referenced above.
FIG. 4 is a flowchart illustrating a process for monitoring a system according to one embodiment of the present invention. In this example, the process begins with a listener subscribing 405 and 410 to one or more presence attribute of a presence profile maintained by the presence server. The subscription 405 and 410 can be performed via any appropriate message of the underlying protocol of the presence network as described herein and in a manner consistent with the implementation of the presence server. At some point thereafter, the presence network agent can publish 415 an update of one or more presence attributes indicating information relating the monitored device, system, application, etc. Again, the publication 415 can be performed via any appropriate message of the underlying protocol of the presence network as described herein.
The presence service can receive 420 the publication of one or more presence attributes from the presence network agent. A presence profile associated with the presence network agent can be updated 425 based on the received presence attributes. As noted above one or more policies can be applied to the presence attributes by the presence service. Therefore, updating 425 the presence profile associated with the presence network agent can be based on applying the one or more policies. At least one of the one or more presence attributes of the presence profile associated with the presence network agent can be provided 430 to a listener, i.e., a notification can be sent to the listener. Providing 430 the presence attributes to the listener can also be based at least in part on applying the one or more policies. That is, one or more policies can be applied to determine, for example, which listeners are to be notified, how they are to be notified, over what channels, how the attribute is to be provided, transformed, etc. The notification can be provided 430 to the listener via any appropriate message of the underlying protocol of the presence network as described herein.
The listener can receive 435 the notification from the presence server. As noted above, the listener can include a handler or other application or process for further handling 440 of the notification. That is, the listener may perform further processing 440 to, for example, inform a user of the listener of the notification, initiate a communication, perform actions to control a process based on the notification, etc.
It should be understood that the process illustrated by FIG. 4 can vary according to the implementation and is offered by way of example only. In another implementation, for example, rather than the listener subscribing 405 to and receiving 435 notification of changes to an attribute, a user agent or “watcher” as described above may be adapted to subscribe 405 to and receive 435 notification of changes to an attribute. In such a case, processing 440 the notification can comprise displaying or otherwise presenting an indication of the notification, for example, via a user interface of the “watcher” device or application.
FIG. 5 is a flowchart illustrating a process for monitoring a system according to an alternative embodiment of the present invention. In this example, the process begins with the presence network agent publishing 505 an update of one or more presence attributes indicating information relating the monitored device, system, application, etc. The publication 505 can be performed via any appropriate message of the underlying protocol of the presence network as described herein.
The presence service can receive 510 the publication of one or more presence attributes from the presence network agent. A presence profile associated with the presence network agent can be updated 515 based on the received presence attributes. As noted above, one or more policies can be applied to the presence attributes by the presence service. Therefore, updating 515 the presence profile associated with the presence network agent can be based on applying the one or more policies.
As some point thereafter, a listener may request 520 or query the presence service for one or more of the presence attributes. The request 520 can be made via any appropriate message of the underlying protocol of the presence network as described herein. The presence server can receive 525 the request and can, in response, return 530 one or more presence attributes of the presence profile associated with the presence network agent. As noted above one or more policies can be applied to the presence attributes by the presence service. Therefore, returning 530 one or more presence attributes of the presence profile associated with the presence network agent can be based on applying the one or more policies. That is, one or more policies can be applied to determine, for example, whether the requesting listener is authorized to receive the requested attributes, how they are to be returned, over what channels, how the attribute is to be transformed, if at all, etc.
The listener can receive 535 the attribute(s) from the presence server. As noted above, the listener can include a handler or other application or process for further handling 540 of the attribute(s). That is, the listener may perform further processing 540 to, for example, inform a user of the listener of the attribute(s), initiate a communication, perform actions to control a process based on the attribute(s), etc.
It should be understood that the process illustrated by FIG. 5 can vary according to the implementation and is offered by way of example only. In another implementation, for example, rather than the listener requesting 520 and receiving 535 an attribute, an application as described above may be adapted to requesting 520 and receiving 535 an attribute. In such a case, processing 540 the received attribute(s) can comprise, for example, determining whether to update/report a status of the monitored system, application, device, etc.
FIG. 6 is a flowchart illustrating a process for monitoring a system according to on embodiment of the present invention. As noted above, the presence network agent can also receive notification of an event from another element of the system. Thus, in this example, processing begins with the presence network agent receiving 605 a notification of an event or other information from another element of the system. The presence network agent can then determine 610 whether to publish the event or information to the presence server. This determination 610 can be based on, for example, whether the corresponding attribute has changed, a set of policies applied by the presence network agent, etc. In response to determining 610 to publish the event or information, the presence network agent can publish 615 an update of one or more presence attributes indicating information relating the monitored device, system, application, etc. Again, the publication 615 can be performed via any appropriate message of the underlying protocol of the presence network as described herein.
The presence service can receive 620 the publication of one or more presence attributes from the presence network agent. A presence profile associated with the presence network agent can be updated 625 based on the received presence attributes. As noted above one or more policies can be applied to the presence attributes by the presence service. Therefore, updating 625 the presence profile associated with the presence network agent can be based on applying the one or more policies. At least one of the one or more presence attributes of the presence profile associated with the presence network agent can be provided 630 to a listener, i.e., a notification can be sent to the listener. Providing 630 the presence attributes to the listener can also be based at least in part on applying the one or more policies. That is, one or more policies can be applied to determine, for example, which listeners are to be notified, how they are to be notified, over what channels, how the attribute is to be provided, transformed, etc. The notification can be provided 730 to the listener via any appropriate message of the underlying protocol of the presence network as described herein.
FIG. 7 is a flowchart illustrating a process for monitoring a system according to an alternative embodiment of the present invention. As noted above, the presence network agent may additionally or alternatively query another element of the system to receive an event or information. Thus, in this example, processing begins with the presence network agent querying another element of the system for status or other information. The presence network agent can the receive 710 information from the other element of the system in response to the query. The presence network agent can then determine 715 whether to publish the event or information to the presence server. This determination 715 can be based on, for example, whether the corresponding attribute has changed, a set of policies applied by the presence network agent, etc. In response to determining 715 to publish the event or information, the presence network agent can publish 720 an update of one or more presence attributes indicating information relating the monitored device, system, application, etc. Again, the publication 720 can be performed via any appropriate message of the underlying protocol of the presence network as described herein.
The presence service can receive 725 the publication of one or more presence attributes from the presence network agent. A presence profile associated with the presence network agent can be updated 730 based on the received presence attributes. As noted above one or more policies can be applied to the presence attributes by the presence service. Therefore, updating 730 the presence profile associated with the presence network agent can be based on applying the one or more policies. At least one of the one or more presence attributes of the presence profile associated with the presence network agent can be provided 735 to a listener, i.e., a notification can be sent to the listener. Providing 735 the presence attributes to the listener can also be based at least in part on applying the one or more policies. That is, one or more policies can be applied to determine, for example, which listeners are to be notified, how they are to be notified, over what channels, how the attribute is to be provided, transformed, etc. The notification can be provided 735 to the listener via any appropriate message of the underlying protocol of the presence network as described herein.
FIG. 8 is a flowchart illustrating additional details of a process for monitoring a system according to an alternative embodiment of the present invention. In this example, the process begins with the presence network agent publishing 805 an update of one or more presence attributes indicating information relating the monitored device, system, application, etc. Again, the publication 805 can be performed via any appropriate message of the underlying protocol of the presence network as described herein.
The presence service can receive 810 the publication of one or more presence attributes from the presence network agent. A presence profile associated with the presence network agent can be updated 815 based on the received presence attributes. As noted above one or more policies can be applied to the presence attributes by the presence service. Therefore, updating 815 the presence profile associated with the presence network agent can be based on applying the one or more policies. At least one of the one or more presence attributes of the presence profile associated with the presence network agent can be provided 820 to subscribers, i.e., a notification can be sent to the subscribers. Providing 820 the presence attributes to the listener can also be based at least in part on applying the one or more policies. That is, one or more policies can be applied to determine, for example, which subscribers are to be notified, how they are to be notified, over what channels, how the attribute is to be provided, transformed, etc. The notification can be provided 820 to the listener via any appropriate message of the underlying protocol of the presence network as described herein.
Additionally, a determination 825 can be made as to whether to persist the presence attributes. This determination 825 can be based on application of the policies. That is, the policies can define what attributes should or should not be persisted, if any, how long to persist the attributes, etc. Based on application of the policies and in response to determining 825 to persist the attributes, the attributes can be persisted 830, i.e., can be saved, marked for persistence, etc.
At some point thereafter, the listener can subscribe to 835 and 840 to one or more presence attribute of a presence profile maintained by the presence server. The subscription 835 and 840 can be performed via any appropriate message of the underlying protocol of the presence network as described herein and in a manner consistent with the implementation of the presence server. A determination 845 can be made as to whether the subscribed attributes are currently persisted. This determination 845 can be made, for example, by applying policies to any saved attributes to determine whether the attributes are valid/relevant or have expired such as described, for example, in the application entitled Past Presence Hints referenced above. In response to determining 845 the attributes subscribed to by the listener are persisted, i.e., still relevant or not expired, a notification of the persisted attributed can be sent 850 to the listener.
The listener can receive 855 the notification from the presence server. As noted above, the listener can include a handler or other application or process for further handling 860 of the notification. That is, the listener may perform further processing 860 to, for example, inform a user of the listener of the notification, initiate a communication, perform actions to control a process based on the notification, etc.
FIG. 9 is a block diagram illustrating additional details of an exemplary implementation of a system according to one embodiment of the present invention. More specifically, this example illustrates a system such as described above with reference to FIG. 3 but implemented on SIP using Java Management Extensions (JMX) MBean Events. In this case, the system 900 includes a presence server 305 as described above but implemented on a SIP servlet 925 with a presence enabler 310 as known in the art. The listener 350, including handler 351 as described above, can be coupled with the presence server 305 via a communications network (not shown here) implementing SIP.
According to one embodiment, a JMX MBean Monitor 920 can be used, for example, for monitoring one or more conditions, events, readings, results, etc. of the monitored device 346 described above. The JMX MBean Monitor 920 can provide the collected event or other information to a JMX Event to Presence Information Data Format (PIDF) Transformer 915 to convert the event or other information to PIDF. The JMX Event to PIDF Transformer 915 can in turn pass the converted information to the presence network agent 346 to be published as presence attributes to the presence server 305. As noted above, the presence network agent 346 can publish the presence attributes using the known SIP “PUBLISH” method.
Additionally or alternatively, the system 900 can include an application server 905 on which a JMX MBean server 910 is implemented. That is, in addition to or instead of being implemented to monitor a device, the JMX MBean Monitor 920 can be implemented to monitor a process or processes of the application server 905. In such a case, the JMX MBean Monitor 920 can be adapted to monitor the processes, information, events, etc. of the application server 905 via the JMX MBean server 910. Again, the JMX MBean Monitor 920 can provide the collected event or other information to a JMX Event to PIDF Transformer 915 to convert the event or other information to PIDF. The JMX Event to PIDF Transformer 915 can in turn pass the converted information to the presence network agent 346 to be published as presence attributes to the presence server 305, for example, using the known SIP “PUBLISH” method.
Regardless of whether the presence attributes published by the presence network agent 346 relate to information or events from a monitored device or process(es) of the application server 905, the presence module 310 of the presence server can be adapted to provide the presence attributes to the listener 350. As noted above, the presence server 305 can implement a publish/subscribe model. In such a case, the listener 350 after subscribing to the presence attributes, can receive notification provided by the presence server 305 upon a change of the presence attribute(s) subscribed to. The notifications can comprise, for example, a SIP “NOTIFY” message.
As noted above, the system 900 can additionally or alternatively include another subscriber device 355. A user agent 356 operating on the subscriber device 355 can be adapted to subscribe to and receive notifications of changes to presence attributes 326 published by a principal. Thus, the user agent 356 can be adapted to monitor one or more presence attributes for administration and/or management purposes. For example, the user agent 356 can be a “watcher” that can be present on any device or application. Therefore, a status or update for a monitored system can be provided to any device that has a user agent 356 or “watcher.”
In use, embodiments of the present invention can provide a variety of functions including but not limited to enabling chat, voice, web conf interaction from a desktop application, enabling cross device interactions, enable workflow applications efficiency, expose presence state of applications for efficient end-user interaction, performing intelligent call routing in VoIP, providing a multi-channel follow-me service, creating efficient notification systems, improving application interaction with end-users, etc. As noted, the information monitored by such a system 900 can comprise event information and can be used by the system 900 to implement an Event Driven Architecture (EDA). For example, applications subscribing to presence of other principals in such an EDA can perform CRM/call center applications that direct IM or SIP interactions, EM monitoring of a process, push email/notification to client, etc. Additionally or alternatively, an application in an EDA can provide notice of its presence information to a process publishing presence information available for EM monitoring or to an administrator who can monitor processes that he is in charge of through it's presence agent and be notified when status changes occur. In yet another example, an application in an EDA can query presence information maintained by an intelligent messaging/notification server to decide where to send a message/notification or present a corporate directory web page based on such a query.
FIG. 10 is a block diagram illustrating, at a high-level, functional components of a system for monitoring a system according to an alternative embodiment of the present invention. As noted above, embodiments of the present invention, such as illustrated here, can be implemented on an Enterprise Service Bus (ESB) 1005. In such an implementation, the source or publisher of an event can be the ESB 1005 or can publish the event via the ESB 1005. Additionally or alternatively, the subscriber or recipient of the event can be the ESB 1005 or can receive the event via the ESB 1005.
More specifically, the system 1000 of this example includes a number of devices 345 and 350 communicatively coupled with the ESB 1005. The devices 345 and 350 can include a monitored device 345 and a listener 350 as described above. Additionally or alternatively, the system 1000 can include an application 360 and/or another subscriber 355 device or system 355 as described above and also communicatively coupled with the ESB 1005.
The system 1000 can also include a presence server 305 as described above and communicatively coupled with the ESB 1005. As noted, the presence service provided via the presence enabler 310 of the presence server 305 can maintain a set of presence profiles 325 for any number of principals participating in the service. For example, a presence profile 325 can be maintained for or related to the monitored device 345. The presence profile 325 can include a set of one or more presence attribute 326. The presence attributes 326 can include attributes identifying or related to presence information as noted above. However, the presence attributes 326 described herein are not limited to identifying or indicating presence information. Rather, embodiments of the present invention provide for using presence attributes 326 to identify or indicate any type of information related to the principal such as the monitored device 345. For example, such information can include but is not limited to a state or status, information collected or generated by an application or process, etc, as well as presence information. Additionally or alternatively, information indicated by the presence attributes can include other types of information. For example, information indicated by one or more presence attributes can include but is not limited to a multimedia document, a Uniform Resource Identifier (URI) to a document of stream, etc maintained by or provided via a media server 1010 communicatively coupled with the ESB 1005.
Generally speaking, the system 1000 can provide for handling an event published as a presence attribute 326 by a principal. According to one embodiment, the source or publisher of an event can be the ESB 1005. For example, the ESB can be implemented on SIP and events can be published via JMX MBean Events as described above. Additionally or alternatively, the source or publisher of the event can be the presence network agent 346 of the monitored device 345 as described above that passes the event to the presence server 305 via the ESB 1005. As described, the presence server 305, based on the application of policies 320, can handle the event by notifying one or more listeners 350 or subscribers. According to one embodiment of the present invention, the subscriber can be the ESB 1005 which receives the notification and in turn passes the notification and/or attributes to or otherwise informs another element of the system 1000 such as the listener 350 or other subscriber 355 which in turn processes the attributes as described above.
In the foregoing description, for the purposes of illustration, methods were described in a particular order. It should be appreciated that in alternate embodiments, the methods may be performed in a different order than that described. It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine, such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software.
While illustrative and presently preferred embodiments of the invention have been described in detail herein, it is to be understood that the inventive concepts may be otherwise variously embodied and employed, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art.

## Claims

1. A monitoring system comprising:
an Enterprise Service Bus (ESB);
a monitored device associated with a presence network agent, the present network agent receiving monitored information from the monitored device and publishing one or more presence attributes via the ESB in response to receiving the monitored information;
a presence server communicatively coupled with the ESB, the presence server receiving the one or more published presence attributes from the presence agent of the monitored device via the ESB and updating a presence profile associated with the monitored device based on the received presence attributes, wherein the received presence attributes comprise at least one attribute indicating presence or location information and a plurality of attributes indicating information other than presence information, wherein the information other than presence information includes at least each of information indicating a non-presence status of a monitored device, a measurement from a monitored sensor other than a presence or location measurement, and a multimedia document, wherein the non-presence status indicates a status of the monitored device other than presence or location, and wherein updating the presence profile associated with the monitored device comprises storing the received at least one presence attribute indicating presence or location information and the plurality of presence attributes indicating information other than presence information all as attributes of the presence profile associated with the monitored device.

2. The system of claim 1, wherein the presence network agent comprises a Java Management Extension (JMX) MBean Monitor and wherein publishing one or more presence attributes comprises publishing Presence Information Data Format (PIDF) information.

3. The system of claim 2, wherein the presence network agent is adapted to request monitored information, receive the monitored information in response to the request, and publish the one or more presence attributes in response to receiving the monitored information.

4. The system of claim 1, further comprising a listener communicatively coupled with the presence server and adapted to receive presence attributes from the presence server.

5. The system of claim 4, wherein the listener is adapted to subscribe to the at least one of the one or more presence attributes of the presence profile and wherein the presence server provides the at least one presence attribute to the listener by providing a notification of a change in the at least one presence attribute.

6. The system of claim 4, wherein the listener is adapted to request the presence attributes from the presence server and wherein the presence server provides the at least one presence attribute to the listener in response to the request.

7. The system of claim 4, wherein the listener comprises a handler adapted to process the presence attributes received from the presence server.

8. The system of claim 4, wherein the information other than presence information comprises event information.

9. The system of claim 8, wherein the presence server is further adapted to provide an Event Driven Architecture (EDA) based on the event information.

10. The system of claim 9, wherein the EDA is adapted to persist the one or more presence attributes based on one or more policies.

11. The system of claim 10, wherein the EDA is adapted to expire the one or more presence attributes based on one or more policies.

12. The system of claim 10, wherein the EDA is adapted to provide notification of past events to the listener based on one or more policies.

13. The system of claim 9, wherein the EDA is implemented on the ESB.

14. The system of claim 9, wherein the ESB is implemented on the EDA.

15. The system of claim 9, wherein the ESB is adapted to subscribed to at least one of the one or more presence attributes of the presence profile associated with the presence network agent and receive a notification of a change in the at least one presence attribute from the presence server.

16. The system of claim 15, wherein the ESB is adapted to publish one or more presence attributes to the presence server.

17. The system of claim 16, wherein the ESB is adapted to publish the one or more presence attributes using Java Management Extensions (JMX) MBean Events.

18. The system of claim 9, wherein the EDA is adapted to provide real-time monitoring of a device associated with the presence network agent.

19. The system of claim 18, wherein the presence attributes further comprise at least one attribute indicating presence information and one or more attributes indicating each of a non-presence status of a monitored device or process wherein the non-presence status indicates a status of the monitored device other than presence or location, a measurement from a monitored device other than a presence or location measurement, non-presence information collected or generated by a monitored application or process, and a multimedia document.

20. The system of claim 19, wherein the EDA provides tracking of the device associated with the presence network agent based on the at least one attribute indicating presence information.

21. The system of claim 20, wherein the device associated with the presence network agent comprises a Radio Frequency IDentification (RFID) tag.

22. The system of claim 18, wherein the device associated with the presence network agent comprises a sensor and the EDA is adapted to perform process monitoring based on at least one of the presence attributes.

23. The method of claim 1, wherein the information other than presence information further comprises non-presence information collected or generated by a monitored application or process.

24. The method of claim 23, wherein the information other than presence information further comprises a Uniform Resource Identifier (URI) to a document.

25. The method of claim 24, wherein the information other than presence information further comprises a URI to a multimedia stream.

26. A method of monitoring a system, the method comprising:
receiving at a presence network agent information from a monitored device associated with the presence network agent;
publishing by the presence network agent a plurality of presence attributes via an Enterprise Service Bus (ESB) in response to receiving the information from the monitored device;
receiving at a presence server through the ESB the publication of the plurality of presence attributes from the presence network agent, the received presence attributes comprising at least one attribute indicating presence or location information and a plurality of attributes indicating information other than presence information, wherein the information other than presence information includes at least each of information indicating a non-presence status of a monitored device, a measurement from a monitored sensor other than a presence or location measurement, and a multimedia document, and wherein the non-presence status indicates a status of the monitored device other than presence or location;
updating a presence profile associated with the presence network agent with the presence server based on the received presence attributes, wherein updating the at least one presence profile comprises storing the received at least one presence attribute indicating presence or location information and the plurality of presence attributes indicating information other than presence information all as attributes of the presence profile associated with the monitored device; and
providing at least one of the one or more presence attributes of the presence profile associated with the presence network agent from the presence server to a listener.

27. The method of claim 26, wherein providing at least one of the one or more presence attributes of the presence profile associated with the presence network agent to the listener comprises providing a notification of a change in the at least one presence attribute.

28. The method of claim 26, further comprising receiving at the presence server a request from the listener for at least one of the one or more presence attributes of the presence profile associated with the presence network agent and wherein providing the at least one presence attribute to the listener is performed in response to the request.

29. The method of claim 26, wherein the information other than presence information comprises event information.

30. The method of claim 29, further comprising providing with the presence server an Event Driven Architecture (EDA) based on the event information.

31. The method of claim 30, wherein providing the EDA comprises providing real-time monitoring of a device associated with the presence network agent.

32. The method of claim 30, wherein providing the EDA comprises persisting one or more of the presence attributes based on one or more policies.

33. The method of claim 32, wherein providing the EDA comprises expiring one or more of the presence attributes based on one or more policies.

34. The method of claim 32, wherein providing the EDA comprises providing notification of past events to the listener based on one or more policies.

35. The method of claim 30, wherein providing the EDA comprises providing tracking of the device associated with the presence network agent based on the at least one attribute indicating presence information.

36. The method of claim 30, wherein the device associated with the presence network agent comprises a sensor and wherein providing the EDA comprises performing process monitoring based on at least one of the presence attributes.

37. The method of claim 36, wherein providing the EDA comprises providing real-time monitoring of a process associated with the presence network agent.

38. The method of claim 37, wherein providing real-time monitoring of the process associated with the presence network agent comprises providing a notification of a change in status of the process based on one or more of the presence attributes.