WO2003060711A2 - Systeme et procede permettant de determiner le comportement de notification d'un systeme - Google Patents

Systeme et procede permettant de determiner le comportement de notification d'un systeme Download PDF

Info

Publication number
WO2003060711A2
WO2003060711A2 PCT/US2003/001144 US0301144W WO03060711A2 WO 2003060711 A2 WO2003060711 A2 WO 2003060711A2 US 0301144 W US0301144 W US 0301144W WO 03060711 A2 WO03060711 A2 WO 03060711A2
Authority
WO
WIPO (PCT)
Prior art keywords
notification
notification mode
sent out
new
mode
Prior art date
Application number
PCT/US2003/001144
Other languages
English (en)
Other versions
WO2003060711A3 (fr
Inventor
Jeremy S. De Bonet
Todd A. Stiers
Jeffrey R. Annison
Original Assignee
Idetic, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/342,113 external-priority patent/US7073178B2/en
Application filed by Idetic, Inc. filed Critical Idetic, Inc.
Priority to AU2003214841A priority Critical patent/AU2003214841A1/en
Publication of WO2003060711A2 publication Critical patent/WO2003060711A2/fr
Publication of WO2003060711A3 publication Critical patent/WO2003060711A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/226—Delivery according to priorities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor

Definitions

  • Embodiments of the invention relate generally to notification systems. More particularly, embodiments of the present invention relate to systems and methods for determining the notification behavior of a system.
  • a centralized management server receives notifications regarding the status of various monitored components from software agents installed on those components.
  • the software agents will send out status notifications at the same frequency and in the same manner regardless of the state of the monitored component.
  • the software agent associated with that component will send out notifications at the same frequency. In a large system, this can lead to an overabundance of notifications.
  • NMS network management station
  • the operator can configure the NMS to display only a subset of the notifications received so that the operator does not have to view every notification received by the centralized management server.
  • SNMP simple network management protocol
  • levels include a level in which all alarm messages, but no other notifications, are sent by the software agents, a level in which all SNMP traps are sent by the software agents, or a midlevel in which both SNMP traps indicating normal operation and alarm conditions are sent by the software agent according to some predefined rule.
  • these systems only provide a course control that is typically applied to all the software agents (or SNMP traps of those agents). They do not allow fine control for tuning a particular SNMP trap to send out notifications at, for example, different frequencies or for adjusting the behavior of the particular SNMP trap depending on the status of the component being monitored by the SNMP trap.
  • Embodiments of the present invention provide a system and method for determining notification behavior of a system that substantially reduces or eliminates the disadvantages associated with previously-developed notification systems and methods. More particularly, embodiments of the present invention provide a system and method for dynamically controlling the notification behavior of a system.
  • One embodiment of the present invention can include a system for controlling notification behavior of a system comprising a notification program stored on a computer-readable memory. The notification program can be executable by a computer processor to determine a first notification mode based on a set of configuration parameters and a first system state.
  • Embodiments of the present invention provide advantages over prior art notification systems by allowing the notification characteristics of multiple notification modes to be defined. This allows an operator to tune the notification characteristics of embodiments of the present invention to prevent information overload while ensuring that sufficient alarm notifications are received. Embodiments of the present invention provide another advantage over prior art systems and methods of determining notification behavior by allowing configuration parameters associated with various notification modes to be dynamically changed during execution of the remote agent thereby allowing the notification behavior of the system to be dynamically turned.
  • FIGURE 3 illustrates a flow chart for a method of controlling notification behavior according to one embodiment of the present invention.
  • Embodiments of the present invention provide a system and method to manage the notification behavior of a system.
  • One embodiment of the present invention can define multiple notification modes, each exhibiting different notification behavior, based on the state of a component being monitored.
  • embodiments of the present invention can define notification modes such that notifications that indicate a problem state in a monitored component can be sent out more frequently than notifications that indicate that the monitored component is functioning properly.
  • a number of notification modes can be defined to provide various gradations of notification behavior depending on the state of the monitored component.
  • the manner in which a particular notification is sent out can also be controlled. Thus, for example, important notifications can be sent to an operator's pager whereas less important notifications can be sent in some other manner (e.g. email).
  • FIGURE 1 is a diagrammatical representation of a system 100 in which one embodiment of the present invention can be implemented.
  • System 100 can comprise a management system 110 that can include a management computer processor 112, a management computer readable memory 114 (e.g. RAM, ROM, magnetic storage device, optical storage device, and/or any other computer readable memory known in the art) and a management system network adaptor 116 (e.g. modem, Ethernet card or any other network communication device known in the art).
  • Management System 110 can further include a management program 115 stored on computer-readable memory 114 that is executable by management processor 112.
  • Management program 115 can Teceive and process multiple notifications from various software agents over network 120.
  • management program 115 can include an NMS to allow an operator to limit the number of notifications he or she views. Although shown as a single physical unit in FIGURE 1, it should be noted that the functionality of management System 110 can be distributed. In addition to management system 110, system 100 can include multiple monitoring systems
  • notification program 140 can be separate from the program that determines the system state or can be implemented in any other suitable manner as would be understood by one of ordinary skill in the art (e.g. as a software component of larger software package, a function larger software package, a separate program, a portion of another program).
  • the monitored components can include components of the monitoring system, such as hardware or software components, or may include external components.
  • notification program 140 of monitoring system 130 can determine the system state of one or components of monitoring system 130.
  • notification program 140 can be implemented, in one embodiment of the present invention, as firmware on the monitored component (e.g. firmware on a hard drive).
  • notification program 140 of monitoring system 170 can receive data from pressure gauge 175 to determine the system state of a pressure chamber.
  • monitored components can include hardware components, such as hard drives, memory, network adapters or any other hardware, software or mechanical system capable of being automatically monitored by a program.
  • notification program 140 can determine the system state for a component being monitored. For example, notification program 140 of monitoring system 170 can, through monitoring portion 145, can determine the pressure of a chamber through pressure gauge 175. Similarly, monitoring portion 145 in monitoring system 130 can determine, for example, the saturation of RAM in monitoring system 130 (i.e. can determine the amount of memory being used). Based on this state information, notification program 140 can determine a notification mode that corresponds to the system state. Each notification mode can define the notification behavior for a particular system state. For example, monitoring system 170 can define a first notification mode for a pressure between zero and 1,000 psi (e.g. a low-pressure mode), a second notification mode for a pressure from 1,000 psi to 9,000 psi (e.g.
  • Each notification mode can define how frequently and how many times a notification for a particular system state is sent out.
  • the first notification mode (the low-pressure notification mode), corresponding to a pressure of less than 1,000 psi, can be configured to send out notifications every five minutes for a maximum of six consecutive notifications.
  • the second notification mode (the normal-pressure notification mode), corresponding to a pressure of 1,000 to 9,000 psi, can be configured to send out notifications every two minutes for a maximum of 8 consecutive notifications, and the third notification mode (the high-pressure notification mode), corresponding to a pressure of greater than 9,000 psi, can be configured to send out notifications every 10 seconds without limit.
  • a new notification can be sent out based on the new notification mode.
  • the notification program 140 can send out anew notification in accordance with the second notification mode.
  • notification program 140 can send out a new notification in accordance with the first notification mode.
  • system 170 may delay sending out the new notification until the five minutes pass.
  • Notification program 140 can send out notifications in a variety of manners including email, pager, fax or SNMP trap and embodiments of notification program 140 can send notifications associated with different notification modes in different formats. For example, notifications program 140 could send high-priority notifications to an operator's pager, but send lower priority notifications to the operator's email address.
  • management program 115 can send updated configuration parameters to the monitoring systems thereby dynamically altering the notification behavior of a monitored system. For example, rather than having a frequency of every five minutes for the first notification mode of monitoring system 170, management program 115 can change the frequency parameter for the first notification mode to 3 minutes. This can be done while notification program 140 is running, resulting in a dynamic update to the notification behavior of monitoring system 170.
  • FIGURE 2A is a diagrammatic representation of a notification type 198 with configuration parameters that can be used by notification program 140 to determine if a notification should be sent according to the state of a monitored component.
  • Each notification program 140 can utilize several notification types, with notification modes defined for each notification type.
  • the notification type can represent the function for sending out a notification for a particular type of system state.
  • monitoring system 170 could have two notification types, one for notifications regarding pressure and one for notifications regarding temperature, with each notification type having several notification modes.
  • each notification type can represent different types of SNMP traps implemented at the same monitored components).
  • the configuration parameters for each notification type can include a status parameter 200 and a count parameter 205.
  • the status parameter indicates the notification mode (e.g.
  • notification mode 210-1 notification mode 210-1 or notification mode 210-3) that is associated with the current state of the component being monitored for notification type 198.
  • the appropriate notification mode for a system state can be determined from one or more threshold parameters.
  • each notification mode is associated with a "min" parameter 215 and a "max" parameter 220.
  • Other threshold parameters can be used and m some cases the notification modes may only be associated with a single threshold parameter, rather than multiple threshold parameters as shown in FIGURE 2A.
  • Each notification mode can further be associated with a frequency parameter 230, a repeats parameter 235 and a last-sent parameter 240.
  • the frequency parameter can determine how much time must lapse between notifications sent for a particular mode.
  • frequency parameter 230-1 will indicate the frequency at which notifications according to notification mode 210-1 can be sent.
  • the last sent parameter 240 can indicate the time that a notification was last sent for the respective notification mode and the repeats parameter 235 can indicate the number of consecutive times that a notification according to the associated notification mode can be sent.
  • a count parameter 205 can keep track of how many consecutive. times a notification according to the current notification mode (indicated by status parameter 200) has been sent.
  • notification program 140 can define a notification type associated with monitoring RAM saturation and further defining multiple notification modes, including a light-usage mode 210-1, a medium-usage mode 210-2, and a heavy- usage mode 210-3.
  • the names of the modes can be stored in the respective mode parameter 250.
  • light-usage mode can have a min parameter equal or greater than to 0% and a max parameter equal to or less than 20%
  • medium-usage mode 210-2 can have a min parameter 215-2 greater than 20% and a max parameter 220-2 equal to or less than 70% and the heavy usage mode
  • notification program 140 can determine the status of the component being monitored by comparing the performance data of the monitored component to the threshold parameter or parameters for the notification modes. For example, if the performance measurements indicate that 15% of the RAM of the monitored component is being used, this is within the threshold parameters 215-1 and 220-1 of light-usage mode 210-1. Therefore, notification program 140 can determine that the system state corresponds to light-usage mode 210-1 and set the status parameter 200 equal to the mode parameter 250-1. Additionally, if the status has changed since the last measurement was taken, notification program 140 can reset count parameter 205 to zero.
  • the notification program 140 determined that the notification mode did not change. If however, notification program 140 determines that the notification mode changes since the last system measurement (e.g. goes from light-usage mode 210-1 to medium-usage mode 210-2), notification program 140 can reset count parameter 205 to zero. In one embodiment notification program 140 can then send out a notification under medium-usage mode 210-2. Alternatively, notification program 140 can determine if enough time has passed since the last notification has been sent out under medium-usage mode 210-2 to send out a new notification under medium-usage mode 210-2 by, for example, comparing the difference between the current time and the value of last sent parameter 240-2 to frequency parameter 230-2.
  • each notification program 140 may define several notification types. For example, if notification program 140 monitors both CPU usage and memory usage, the notification program may define a RAM usage notification function and a CPU usage notification function, each defining their own notification modes. Based on the system state of the monitored competent, notification program 140 can call the various notification types to send notifications regarding the RAM usage and the CPU usage. This allows notifications regarding different aspects of the same or different monitored component to be sent separately. Moreover, in the embodiments of FIGURE 2A and FIGURE 2B, multiple notification modes are defined for notification type 198.
  • the system state may indicate that 15% of the RAM is being used, indicating a light-usage mode for the notification type corresponding to RAM monitoring.
  • Notification program 140 at step 315, can then determine if the notification mode is the same as the previous notification mode or if a new notification mode has been entered. Notification program 140 can also check to ensure that a notification for the notification mode has not been sent too many times (step 325). In one embodiment of the present invention, this can be done by comparing count parameter 205 for the notification type to the repeats parameter for a particular notification mode. If, for example, the notification mode is the light-usage mode, repeats parameter 235-1 can be compared to count parameter 205.
  • step 330 can occur even if a new notification mode was entered as determined at step 315. Therefore, notification program 140, in one embodiment of the present invention, may not immediately send out a notification even if notification program 140 determines that the system state corresponds to a new notification mode.
  • notification program 140 can increment the count parameter 205 for the notification type and update the last-sent parameter for the notification mode if a notification is sent out.
  • Notification program 140 can optionally repeat the process of FIGURE 3 (step 345).
  • Table 1 includes an example of pseudo-code for implementing one embodiment of the process of FIGURE 3.
  • the code of table 1 is provided by way of example only and is not limiting of the present invention.
  • Notification program 140 can be implemented using any suitable programming language and structure, as would be understood by those of ordinary skill in the art.
  • Examples of the shared resources may include a content cache, a parameter cache, a connection pool, a domain name server cache, a clock, a counter, a database/a global variables space (e.g., a logging database), or the like.
  • a list of potential shared resources is nearly limitless. Note that not all shared resources may be connected to all modules along a row. For example, modules 3202 and 3204 may not need access to the content cache because they may not receive or process content returned for a request.
  • Each connection from a client may be handled independently on its own thread. However in other embodiments, fewer threads or a single thread can be used to operate all connections to a specific row that supports a particular application or protocol. Unless stated to the contrary, the method below is described from the perspective of proxy computer 140.
  • the method can further comprise routing the incoming communication to a first software plug-in module for the specific application (block 604).
  • Proxy computer 140 can route the request to request reception software plug-in module 3202 because the incoming request uses the application corresponding to row 3200.
  • the method can comprise parsing the incoming communication into a header portion and a content portion (block 622). The parsing can be performed by module 3202 to obtain information from the request.
  • the method can also comprise generating a function call to at least one of the shared resources using data within the associative array (block 702 in FIG. 7).
  • proxy computer 140 can make a function call to a shared resource, more specifically to a clock (shared resource) and a logging system (another shared resource) to get the time and log the beginning of the transaction.
  • the logging information may include the time and a transaction identifier. Note that some of the information within the associative array could be sent with the function call to the shared resource.
  • the method can further comprise receiving data from the function call (block 704).
  • the transaction identifier may be passed back to module 3202.
  • the method can still further comprise processing data from the function call with other code within the first software module (block 706).
  • the next software plug-in module is authorization module 3204.
  • Authorization module 3204 may use some of the information that was collected or generated by module 3202. Passing the information reduces the load on hardware by not sending a communication from proxy computer 140 to another computer (e.g., client computer 120) or making the same or similar function call to a shared resource for the same information.
  • the method can also comprise receiving data from the function call (block 824).
  • the data may include information regarding whether user at client computer 120 has proper security clearance, whether the connection could be made, priority of the connection, and the like.
  • the method can further comprise processing data from the function call with other code within the current software plug-in module (block 826).
  • An example may include sending a communication from proxy computer 140 to client computer 120 informing the user whether the connection was made. Alternatively, no further processing may occur with module 3204.
  • Content manipulation module 3210 may delete, add, or replace some or all of the content within the proper network page returned. For example, when the proper Google network page is received or accessed, module 3210 may add advertisement(s) around the border(s) of the page. A function call can be made to a shared resource to determine which advertisement(s) should be added. The logging system may keep track of which advertisement is being added, whose advertisement it is, and how many times the advertisement has been added during the current billing cycle. The logging system, which is a shared resource, may access the counter (another shared resource) by itself. In other works, some or all of the shared resources may interact with each other without requiring an application-specific software plug-in module to intervene. The manipulated content and other information may be passed to module 3212.
  • the billing information may be within a shared resource managed by an accounting department.
  • Billing information for the user at client computer 120 may be passed from one of the shared resources to module 3214, which may return some of the information for the user at client computer 120.
  • Proxy computer 140 may send a message to client computer 120 similar to "You were connected for 2.1 minutes and were charged $1.27. Thank you for using our service.” Alternatively, no message may be sent and the method may end.
  • the power of creating new applications for the same, protocol may be better understood with the flow diagram in FIG. 9 and an example.
  • different applications may be generated for different priorities of users for a network site.
  • the communication protocol may use HTTP.
  • the method can comprise developing a first set of plug-in modules for a first application (block 902). The set may correspond to row 3200 and be directed to premium users of a network site. A new application may need to be developed for regular users of the network site.
  • the communication protocol may also use HTTP.
  • the method can comprise copying the first set of plug- in modules to form a second set of plug-in modules (block 922).
  • the request manipulation plug-in module For the new application, only the request manipulation plug-in module, the content manipulation plug-in module, or both may be replaced.
  • the remainder of the plug-in modules may be unchanged and be substantially the same as the remainder of the plug-in modules for the first application.
  • the method may comprise replacing a first request manipulation plug-in module with a second request manipulation plug-in module for a second application (block 924).
  • the premium user may have access to some network pages that the regular user may not. If the regular user requests a premium page, the second request manipulation module may direct the regular user to another network page for which the regular user has proper access.
  • the method may also comprise replacing a first content manipulation plug-in module with a second content manipulation plug-in module for the second application (block 926).
  • the premium user may have only 10 percent of his or her window occupied by advertisements, whereas the regular user may have 50 percent of his or her window occupied by advertisements.
  • the second content manipulation module may reformat the retrieved content to allow for more advertising space.
  • the second content manipulation module may also access the shared resources to obtain the advertisements and keep track of which advertisements were used.
  • Device dependent optimization of network pages can be achieved by plugging in a module which transcodes content using settings developed for the particular device that made the initial request.
  • the method can still further comprise executing the second application using the second set of plug-in modules (block 942).
  • those modules may be generated by editing code within the corresponding modules within the first set for the first application.
  • the multiple-protocol software architecture and plug-in modules may be installed in client computer 120 or server computer 160. Not all modules in proxy computer 140 may be needed by client computer 120 or server computer 160.
  • Authorization modules 3204, 3404, and 3604 may not be used or can be coded to allow authorization (always authorized) at client computer 120.
  • the content manipulation modules 3210, 3410, and 3610 may not be used by the server computer 160.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Environmental & Geological Engineering (AREA)
  • Stored Programmes (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne des modes de réalisation d'un système et d'un procédé, qui permettent de contrôler, de façon dynamique, le comportement de notification d'un système. Un mode de réalisation de l'invention peut comprendre un système destiné à contrôler le comportement de notification d'un système présentant un programme de notification stocké dans une mémoire lisible par ordinateur. Le programme de notification peut être exécuté par un processeur pour déterminer un premier mode de notification basé sur un ensemble de paramètres de configuration et un premier état du système. Le programme de notification peut en outre être exécuté pour déterminer si une notification doit être envoyée sur la base d'un ensemble de paramètres de configuration associé à un premier mode de notification. Si une notification doit être envoyée, le programme de notification communique la notification par le biais d'un réseau. Le programme de notification peut aussi recevoir un paramètre de configuration mis à jour associé au premier mode de notification et envoyer une nouvelle notification basée sur le paramètre de configuration mis à jour.
PCT/US2003/001144 2002-01-15 2003-01-15 Systeme et procede permettant de determiner le comportement de notification d'un systeme WO2003060711A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003214841A AU2003214841A1 (en) 2002-01-15 2003-01-15 System and method for determining notification behavior of a system

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US34869202P 2002-01-15 2002-01-15
US60/348,692 2002-01-15
US34942402P 2002-01-18 2002-01-18
US34934402P 2002-01-18 2002-01-18
US60/349,424 2002-01-18
US60/349,344 2002-01-18
US10/342,113 US7073178B2 (en) 2002-01-18 2003-01-14 Method and system of performing transactions using shared resources and different applications
US10/342,113 2003-01-14

Publications (2)

Publication Number Publication Date
WO2003060711A2 true WO2003060711A2 (fr) 2003-07-24
WO2003060711A3 WO2003060711A3 (fr) 2003-11-13

Family

ID=27502654

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/001144 WO2003060711A2 (fr) 2002-01-15 2003-01-15 Systeme et procede permettant de determiner le comportement de notification d'un systeme

Country Status (2)

Country Link
AU (1) AU2003214841A1 (fr)
WO (1) WO2003060711A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8620295B2 (en) 2009-03-05 2013-12-31 Blackberry Limited Method and apparatus for modifying notification settings on a mobile electronic device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5388189A (en) * 1989-12-06 1995-02-07 Racal-Datacom, Inc. Alarm filter in an expert system for communications network
WO1996035994A1 (fr) * 1995-05-08 1996-11-14 Compuserve Incorporated Systeme de gestion de messages electroniques a base de regles
US5655081A (en) * 1995-03-08 1997-08-05 Bmc Software, Inc. System for monitoring and managing computer resources and applications across a distributed computing environment using an intelligent autonomous agent architecture
US5987514A (en) * 1996-10-30 1999-11-16 Sun Microsystems, Inc. System and method for advanced event request management for networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5388189A (en) * 1989-12-06 1995-02-07 Racal-Datacom, Inc. Alarm filter in an expert system for communications network
US5655081A (en) * 1995-03-08 1997-08-05 Bmc Software, Inc. System for monitoring and managing computer resources and applications across a distributed computing environment using an intelligent autonomous agent architecture
WO1996035994A1 (fr) * 1995-05-08 1996-11-14 Compuserve Incorporated Systeme de gestion de messages electroniques a base de regles
US5987514A (en) * 1996-10-30 1999-11-16 Sun Microsystems, Inc. System and method for advanced event request management for networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PENG WU ET AL: "Alarm correlation engine (ACE)" NETWORK OPERATIONS AND MANAGEMENT SYMPOSIUM, 1998. NOMS 98., IEEE NEW ORLEANS, LA, USA 15-20 FEB. 1998, NEW YORK, NY, USA,IEEE, US, 15 February 1998 (1998-02-15), pages 733-742, XP010267438 ISBN: 0-7803-4351-4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8620295B2 (en) 2009-03-05 2013-12-31 Blackberry Limited Method and apparatus for modifying notification settings on a mobile electronic device

Also Published As

Publication number Publication date
AU2003214841A1 (en) 2003-07-30
AU2003214841A8 (en) 2003-07-30
WO2003060711A3 (fr) 2003-11-13

Similar Documents

Publication Publication Date Title
US7650403B2 (en) System and method for client side monitoring of client server communications
US6654804B1 (en) Method and apparatus for automatic dial-up dial-down web hosting
US20050060372A1 (en) Techniques for filtering data from a data stream of a web services application
US8898277B2 (en) Performance monitoring infrastructure for distributed transaction service
US7073178B2 (en) Method and system of performing transactions using shared resources and different applications
US7353269B2 (en) Network monitoring system
JP4593812B2 (ja) データ交換システム及び方法
US7617190B2 (en) Data feeds for management systems
US7243136B2 (en) Approach for managing and providing content to users
EP2409246B1 (fr) Journalisation souple, par exemple pour un serveur web
US9390118B2 (en) Computer implemented method for transforming an event notification within a database notification infrastructure
US7610377B2 (en) Overload management in an application-based server
US9172765B2 (en) Polling-based secure network message notification system and method with performance enhancing features
US20020188568A1 (en) Systems and methods of containing and accessing generic policy
US7299472B2 (en) System and method for dynamically determining notification behavior of a monitoring system in a network environment
US20070240169A1 (en) Computer implemented method for removing an event registration within an event notification infrastructure
WO2003060711A2 (fr) Systeme et procede permettant de determiner le comportement de notification d'un systeme
CN114615073A (zh) 访问流量控制方法及其装置、设备、介质
EP1474762A2 (fr) Sous-systeme de collecte et de generation d'enregistrement/facturation a plate-forme hautement redondante, a fiabilite elevee et a haut rendement
US20080172490A1 (en) Data scanning system and method thereof
US7773527B2 (en) Method and system for dynamically changing quality of service for message communication
JP2005063240A (ja) 階層型データベース検索システム、方法、および該システムのプログラム
CN117061636A (zh) 消息交换方法和装置
WO2003069475A2 (fr) Programme complementaire api pour traitement de transaction dans un reseau modulaire
Cheng et al. Exploiting Architectural Style for Self-repairing Systems

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP