+

EP1239385B1 - Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte et exécution conditionelle - Google Patents

Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte et exécution conditionelle Download PDF

Info

Publication number
EP1239385B1
EP1239385B1 EP01104875A EP01104875A EP1239385B1 EP 1239385 B1 EP1239385 B1 EP 1239385B1 EP 01104875 A EP01104875 A EP 01104875A EP 01104875 A EP01104875 A EP 01104875A EP 1239385 B1 EP1239385 B1 EP 1239385B1
Authority
EP
European Patent Office
Prior art keywords
computer
message
group
user
users
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Lifetime
Application number
EP01104875A
Other languages
German (de)
English (en)
Other versions
EP1239385A1 (fr
Inventor
Andreas Leukert-Knapp
Joachim Becker
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SAP SE
Original Assignee
SAP SE
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=8176626&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP1239385(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by SAP SE filed Critical SAP SE
Priority to EP03007940A priority Critical patent/EP1339002A1/fr
Priority to ES01104875T priority patent/ES2202233T3/es
Priority to PT01104875T priority patent/PT1239385E/pt
Priority to EP01104875A priority patent/EP1239385B1/fr
Priority to AT01104875T priority patent/ATE244423T1/de
Priority to DK01104875T priority patent/DK1239385T3/da
Priority to DE60100430T priority patent/DE60100430T2/de
Priority to PCT/EP2002/002113 priority patent/WO2002073478A1/fr
Priority to CA002439588A priority patent/CA2439588A1/fr
Priority to IL15595702A priority patent/IL155957A0/xx
Priority to AU2002242711A priority patent/AU2002242711B2/en
Priority to US10/469,336 priority patent/US7409430B2/en
Priority to JP2002572064A priority patent/JP3930432B2/ja
Publication of EP1239385A1 publication Critical patent/EP1239385A1/fr
Publication of EP1239385B1 publication Critical patent/EP1239385B1/fr
Application granted granted Critical
Priority to US10/706,878 priority patent/US7373388B2/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q99/00—Subject matter not provided for in other groups of this subclass
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324—Display of status information
    • G06F11/327—Alarm or error message display
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention generally relates to data processing and, more particularly, relates to business application computer systems, programs, and methods that use alert messages.
  • a customer relation management (CRM) application reports that a key customer terminates a contract.
  • a production planning application reports delivery problems for an important order.
  • a business analysis application detects a decline in revenue.
  • a computer system monitor points out insufficiency of resources and informs about an expected memory overflow.
  • Geissbühler et al. discusses a publish-subscribe paradigm as a mechanism providing a framework for the exchange of data between independent applications in an event-driven manner.
  • the paradigm is used in the context of a clinical notification system. Escalation is incorporated.
  • Landry as well as Breed et al. discuss event-based notification systems arranged to support escalation procedures.
  • Business applications can be configured to provide electronic notifications to a single recipient or to a group of recipients (cf. Linstead et al.). There is a technical problem relating to the configuration of the business application notification system to select a specific target group that receives alert notifications from a particular business application.
  • peripheral computers (901/902) with business applications (201/202) send alert messages (211/212) to a central computer (900), for example, when a current variable exceeds a reference value.
  • the central computer implements an alert server to notify (301) a target group of users (1, 2, 3) via communication devices (903, 904, 905).
  • the central computer escalates further notifications (321) to a supervisor user (4) in the event that during a predetermined time period no user of the group has confirmed reception.
  • the notifications (301, 321) have predefined fixed and variable text portions that relate to the alert type.
  • the group of users to be notified is determined by subscription and a role-to-application assignment.
  • Computers 900-902 are coupled via inter-computer network 990.
  • Computer 900 comprises processor 910, memory 920, bus 930, and, optionally, input device 940 and output device 950 (I/O devices, user interface 960).
  • the invention is present by computer program product 100 (CPP), program carrier 970 and program signal 980, collectively "program”.
  • computer 901/902 is sometimes referred to as "remote computer", computer 901/902 is, for example, a server, a router, a peer device or other common network node, and typically comprises many or all of the elements described relative to computer 900.
  • Computer 900 is, for example, a conventional personal computer (PC), a desktop and hand-held device, a multiprocessor computer, a pen computer, a microprocessor-based or programmable consumer electronics, a minicomputer, a mainframe computer, a personal mobile computing device, a mobile phone, a portable or stationary personal computer, a palmtop computer or the like.
  • PC personal computer
  • desktop and hand-held device a multiprocessor computer
  • pen computer a microprocessor-based or programmable consumer electronics
  • minicomputer a mainframe computer
  • a personal mobile computing device a mobile phone
  • portable or stationary personal computer a palmtop computer or the like.
  • Processor 910 is, for example, a central processing unit (CPU), a micro-controller unit (MCU), digital signal processor (DSP), or the like.
  • CPU central processing unit
  • MCU micro-controller unit
  • DSP digital signal processor
  • Memory 920 symbolizes elements that temporarily or permanently store data and instructions. Although memory 920 is conveniently illustrated as part of computer 900, memory function can also be implemented in network 990, in computers 901/902 and in processor 910 itself (e.g., cache, register), or elsewhere. Memory 920 can be a read only memory (ROM), a random access memory (RAM), or a memory with other access options.
  • ROM read only memory
  • RAM random access memory
  • Memory 920 is physically implemented by computer-readable media, such as, for example: (a) magnetic media, like a hard disk, a floppy disk, or other magnetic disk, a tape, a cassette tape; (b) optical media, like optical disk (CD-ROM, digital versatile disk - DVD); (c) semiconductor media, like DRAM, SRAM, EPROM, EEPROM, memory stick, or by any other media, like paper.
  • computer-readable media such as, for example: (a) magnetic media, like a hard disk, a floppy disk, or other magnetic disk, a tape, a cassette tape; (b) optical media, like optical disk (CD-ROM, digital versatile disk - DVD); (c) semiconductor media, like DRAM, SRAM, EPROM, EEPROM, memory stick, or by any other media, like paper.
  • memory 920 is distributed across different media. Portions of memory 920 can be removable or non-removable.
  • computer 900 uses devices well known in the art such as, for example, disk drives, tape drives.
  • Memory 920 stores support modules such as, for example, a basic input output system (BIOS), an operating system (OS), a program library, a compiler, an interpreter, and a text-processing tool.
  • support modules are commercially available and can be installed on computer 900 by those of skill in the art. For simplicity, these modules are not illustrated.
  • CPP 100 comprises program instructions and - optionally - data that cause processor 910 to execute method steps of the present invention. Method steps are explained with more detail below.
  • CPP 100 defines the operation of computer 900 and its interaction in system network system 999.
  • CPP 100 can be available as source code in any programming language, and as object code ("binary code") in a compiled form.
  • Persons of skill in the art can use CPP 100 in connection with any of the above support modules (e.g., compiler, interpreter, operating system).
  • CPP 100 is illustrated as being stored in memory 920, CPP 100 can be located elsewhere. CPP 100 can also be embodied in carrier 970.
  • Carrier 970 is illustrated outside computer 900. For communicating CPP 100 to computer 900, carrier 970 is conveniently inserted into input device 940. Carrier 970 is implemented as any computer readable medium, such as a medium largely explained above (cf. memory 920). Generally, carrier 970 is an article of manufacture comprising a computer readable medium having computer readable program code means embodied therein for executing the method of the present invention. Further, program signal 980 can also embody computer program 100. Signal 980 travels on network 990 to computer 900.
  • program carrier 970 Having described CPP 100, program carrier 970, and program signal 980 in connection with computer 900 is convenient.
  • program carrier 971/972 (not shown) and program signal 981/982 embody computer program product (CPP) 101/102 to be executed by processor 911/912 (not shown) in computers 901/902, respectively.
  • processor 911/912 (not shown) in computers 901/902, respectively.
  • Input device 940 symbolizes a device that provides data and instructions for processing by computer 900.
  • device 940 is a keyboard, a pointing device (e.g., mouse, trackball, cursor direction keys), microphone, joystick, game pad, scanner.
  • a wireless receiver e.g., with satellite dish or terrestrial antenna
  • a sensor e.g., a thermometer
  • a counter e.g., goods counter in a factory.
  • Input device 940 can serve to read carrier 970.
  • Output device 950 symbolizes a device that presents instructions and data that have been processed.
  • a monitor or other type of display (cathode ray tube (CRT), flat panel display, liquid crystal display (LCD), a speaker, a printer, a plotter, a vibration alert device.
  • output device 950 communicates with the user, but it can also communicate with further computers.
  • Input device 940 and output device 950 can be combined to a single device; any device 940 and 950 can be provided optional.
  • Bus 930 and network 990 provide logical and physical connections by conveying instruction and data signals. While connections inside computer 900 are conveniently referred to as “bus 930", connections between computers 900-902 are referred to as “network 990". Devices 940 and 950 are coupled to computer 900 by bus 930 (as illustrated) or by network 990 (optional). While the signals inside computer 900 are mostly electrical signals, the signals in network are electrical, magnetic, optical or wireless (radio) signals.
  • Networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the internet (i.e. world wide web). The physical distance between a remote computer and computer 900 is not important.
  • Network 990 can be a wired or a wireless network.
  • network 990 is, for example, a local area network (LAN), a wide area network (WAN), a public switched telephone network (PSTN); a Integrated Services Digital Network (ISDN), an infra-red (IR) link, a radio link, like Universal Mobile Telecommunications System (UMTS), Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), or satellite link.
  • LAN local area network
  • WAN wide area network
  • PSTN public switched telephone network
  • ISDN Integrated Services Digital Network
  • IR infra-red
  • radio link like Universal Mobile Telecommunications System (UMTS), Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), or satellite link.
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System for
  • Transmission protocols and data formats are know, for example, as transmission control protocol/internet protocol (TCP/IP), hyper text transfer protocol (HTTP), secure HTTP, wireless application protocol, unique resource locator (URL), a unique resource identifier (URI), hyper text markup language HTML, extensible markup language (XML), extensible hyper text markup language (XHTML), wireless application markup language (WML), etc.
  • TCP/IP transmission control protocol/internet protocol
  • HTTP hyper text transfer protocol
  • HTTP secure HTTP
  • wireless application protocol unique resource locator
  • URL unique resource locator
  • URI unique resource identifier
  • HTML hyper text markup language
  • XML extensible markup language
  • XHTML extensible hyper text markup language
  • WML wireless application markup language
  • An interface can be, for example, a serial port interface, a parallel port interface, a game port, a universal serial bus (USB) interface, an internal or external modem, a video adapter, or a sound card.
  • USB universal serial bus
  • FIG. 2 illustrates a simplified block diagram of the computer network system of FIG. 1 with details of the central computer, the peripheral computers, and the communication devices.
  • Computer system 999 of the present invention has central computer 900 and at least one peripheral computer 901/902. Communication devices 903-906 are also computers. As explained in FIG. 1, computers 90n are coupled via network 990. In FIG 2, messages and their preferred way in network 990 are illustrates by boxes and arrows. The use of singular language and of the forward slash "/" to describe elements like “computer” stands for “at least one” but indicates that in a preferred embodiment multiple elements are used.
  • Peripheral computer 901/902 executes at least one business application (BA) 201/202.
  • application stands for an application computer program.
  • Peripheral computer 901/902 further issues alert message 211/212 ("ALERT") when a current value of a predetermined variable in business application 201/202 is in a predetermined relation to a reference value.
  • Central computer 900 receives alert message 211/212 and, according to a predefined type of alert message 211/212 (e.g., business type), forwards notification message 301 to communication devices 903, 904 and 905 that present a representation (cf. FIG. 4, 301-1) of notification message 301 to a predefined group of multiple original users (e.g., users 1, 2, 3, "GROUP").
  • a predefined type of alert message 211/212 e.g., business type
  • Computer system 999 with central computer 900 after having forwarded notification message 301, issues further notification message 321 (cf. FIG. 5) to a further user (e.g., user 4) outside the group in the event that during a predetermined time period (cf. FIG. 3, T) no user of the group has confirmed reception of notification message 301 (case (2)).
  • a further user e.g., user 4
  • T a predetermined time period
  • message distribution list 140 (illustrated in computer 900).
  • the inclusion of users to list 140 (or exclusion) according to the present invention is discussed below in connection with tables 110, 120, and 130 and FIG. 6.
  • Central computer 900 is conveniently implemented as workplace application server 900' by that the users of the group interact with applications 201/202 (running on peripheral computer 901/902). I/O devices of computers 901 and 902 are shown in FIG. 1 but are omitted in FIG. 2 for simplicity.
  • the predefined relation between current and reference values is detected, preferably, by comparing absolute values, so that the relation is a "larger than” or “smaller than” relation. It is also possible to monitor the current values over a time period to detect either an increase or a decrease that is larger (or smaller) than a reference increase or a reference decrease, respectively.
  • computer 901/902 monitors the "revenue” as the predetermined variable in business application 201/202.
  • Computer 901/902 issues alert message 211/212 when the "actual revenue” (i.e., current value) is smaller than or equal to critical revenue (i.e., reference value).
  • the notification message has "low revenue” or similar content, (cf. FIG. 4, 301-1).
  • Issuing further notification message 321 to a further user is, preferably, provided by forwarding further notification message 321 to further communication device 906.
  • Device 906 presents a further representation (cf. FIG. 5) of notification message 321 to the further user.
  • the present invention is conveniently explained with dedicated communication devices for each user, the present invention can also be implemented with a single communication device, such as a large signboard visible for all users.
  • any communication device When instructed by the user, any communication device returns a receipt message to central computer 900 (case (1)). As illustrated in FIG. 2, device 905 is the confirming device that returns receipt message 315, devices 903 and 904 are non-confirming devices.
  • Communication device 903-906 is, for example, a fax machine ("facsimile”), a voice mail system, a selective call receiver (“pager”), a mobile phone with short message service (SMS) receiver, an audio device (e.g., a text-to-voice converter with speaker) or any other technical apparatus, such as a conventional personal computer (PC, e.g., with electronic mail, or pop-up function, or unified message function), that communicates to a user.
  • PC personal computer
  • communication device 903-906 presents the representations of notification 301/321 visually, for example, by displays 953, 954, 955, 956.
  • devices 903-906 are conveniently implemented to run browser programs, such as HTML-browser in a PC or WAP-browser on a mobile phone.
  • browser programs such as HTML-browser in a PC or WAP-browser on a mobile phone.
  • device 903-906 can present also audible.
  • central computer 900 assigns a unique message identification (MID) number to notification message 301, and confirming communication device 905 returns this identification number as part of receipt message 315.
  • MID unique message identification
  • the MID number is "241220011616" and is derived from data and time of alert (e.g., 24 December 2001, 16.16 hours).
  • confirming communication device 315 also returns user identification (e.g., the name of user 3: "K !).
  • central computer 900 optionally stores the user identification.
  • FIG. 3 illustrates the operation of system 999 of the present invention as method 400 in a simplified time and flow-chart diagram. Method steps 410-460 are explained in boxes. Dashed lines to the time axis indicate a preferred sequence of events; plain arrows indicate a preferred method flow. At the top of the figure, box 499 indicates that computer 901/902 optionally execute application 201/202 continuously. It is an advantage that feeding back alert information to peripheral computer 901/902 is not required.
  • XML extensible markup language
  • Method 400 comprises issuing alert message 410, receiving alert message 420, forwarding notification message 430, presenting 440, as well as either returning receipt 450 in case (1) or issuing further notification message 460.
  • peripheral computer 901/902 issues alert message 211/212 going to central computer 900.
  • central computer 900 receives alert message 211/212.
  • central computer 430 forwards notification message 301 to communication devices 903-905 (e.g., at 16.16 hours).
  • communication device 903-905 presents the representation of message 301 to the users 1, 2, 3 (details in FIG. 4).
  • communication device 905 returns receipt 450 (case (1)).
  • central computer 900 issues further notification message 321, this time to user 4 (details in FIG. 5).
  • alert notification method 400 comprising that central computer 900 performs the following steps:
  • steps 401, 402 and 403 allow the management of the message distribution list (cf. 140 in FIG. 7) by computer 900.
  • steps 401, 402 and 403 are executed prior to steps 410-460.
  • This is convenient, but not essential, updating the list is possible.
  • deriving user group step 401 the group of users is derived from a role-to-user assignment and from an application-to-role assignment (details in FIG. 6), wherein the assignments define the business application that each user is allowed to access.
  • representations of the group of users are stored in the message distribution list (cf. 140 in FIG. 7).
  • receive subscription requests step 403 the list is modified.
  • FIG. 4 illustrates display 953/954/955 of communication device 903/904/905 with notification message 301 issued by central computer 900.
  • the representation of message 301 is conveniently hyperlink 301-1 (e.g., "LOW REVENUE") to a full version of notification message 301.
  • the text of hyperlink 301-1 can be composed by text portions (details below). Not illustrated in the figures, because hyper-linking is well known in the art, the full text is stored, for example, in memory 920 of computer 900 (cf. FIGS. 1-2) and could read, for example, as:
  • notification message 301 comprises predefined text portions 301-3 and 301-4.
  • 301-4 "REVENUE” is fixed and points to the type of application 201/202 where the alert originates (e.g., application that evaluates revenue); and 301-3 "LOW” is alert specific and could also be "HIGH”.
  • the predefined message texts are assigned to the particular business application; in other words, for each type of business application, particular text portions are defined.
  • the message text (short of full versions) has placeholder for business variables that are updated when computer 900 generates message 301.
  • the message text has placeholder for business variables that are updated when computer 900 generates message 301.
  • the natural language of the predefined message can automatically be selected according to user attributes, stored in computer 900 or communication devices 903-905.
  • the text could read as "NIEDRIGES EINKOMMEN - MEETING ORGANISIEREN".
  • hyperlinks is convenient, for example, to shield unauthorized persons from the full information about the alert.
  • computer 900 forwards the full version of message to device 905 only after having confirmed the identity of user 3 as being authorized. Displaying the full version on the same device as the short version (the hyperlink) is convenient, but not necessary. The user reacting on the hyperlink can cause computer 900 to re-direct the full version to a different communication device.
  • computer 900 forwards notification messages with short text and with full text to different communication devices.
  • computer 900 forwards short texts as SMS to a mobile phone and - simultaneously or on request by the user - computer 900 forwards full texts as electronic mail.
  • FIG. 5 illustrates display 956 of communication device 906 with further notification message 321 issued by central computer 900.
  • message 321 cites message 301 (with link 301-1 and suggestion 301-2 in FIG. 4).
  • Message 321 has descriptive portion 321-1 to indicate that message 321 is a further notification.
  • portion 321-1 could read as: "Original recipients did not confirm”.
  • the above explanation assumed that the group of users to be notified (e.g., original users 1, 2, 3, further user 4) is predetermined. It is possible that all users of system 999 (computers 901, 902, 903) are notified. But it is desired to keep the overall number of users in the message distribution list small. In other words, the list should comprise only these users for that alert information is relevant.
  • the distribution list can optionally distinguish between original and further users; but for convenience, the following explanation does not distinguish original and further users.
  • Computer 900 creates the distribution list after receiving alert message 211/212 (dynamic creation in real-time), or before (static creation). Details are explained in connection with FIG. 3, steps 401-403, and FIGS. 6-7.
  • the present invention thereby takes advantage of existing user-to-role and role-to-application assignments.
  • Computer 900 combines the existing assignments with the alert scheme described above.
  • the distribution list is provided according to one or more of the following approaches:
  • Workplace 900' stores assignment tables, preferably, in memory 920.
  • the tables are illustrated here as matrices, wherein a matrix element with a plus symbol stands for an existing assignment.
  • First assignment table 110 provides a role-to-user assignment.
  • USER 1 belongs to ROLES 1, 2, 3 and R; USER 2 belongs to ROLE 1, 2 and R, and so on.
  • Second assignment table 120 provides a business-application-to-role assignment.
  • ROLE 1 belongs to application 201 and 202, 203 and 20P;
  • ROLE 2 belongs to application 201, 203 and 20P, etc.
  • Roles are, for example, Chief Financial Officer, Employee, Sales Representative, and Accountant.
  • Distribution list 140 (cf. steps 401 and 402 in FIG. 3).
  • distribution list 140 for application 201 is obtained as comprising users in roles 1, 2 and R (table 120), these users are USER 1, 2, 3 and U.
  • distribution list 140 for application 202 is obtained as comprising users in roles 1, 3 and R (table 120); these users are USER 1 and USER 3.
  • Third assignment table 130 provides alert-type-to-role assignment.
  • application 201 might create an alert of technical nature, such as an expected memory overflow, that alert is notified to technicians; application 201 might also create an alert of a business nature, such as the revenue alert (cf. FIGS. 2, 4-5), that alert is notified to business persons.
  • Alert types are sometimes referred to as "alert categories”.
  • the predefined group of users is determined in distribution list 140 that is derived from a role-to-user assignment and from an application-to-role assignment, wherein the assignments (110, 120, 130) define the business application that each user is allowed to access.
  • FIG. 7 further illustrates modified distribution list 140', in the example, user 3 has un-subscribed from being notified about alerts in application 201, und user 1 has un-subscribed from being notified about alerts in application 202.
  • Lists 140 and 140' store representations of the group of users and receive (step 403) subscription requests to alert notification messages from the users of the group.
  • Subscription requests can be a request to cancel an existing notification (as illustrated) or, can be a request to establish a new notification.
  • subscription requests selectively add and remove representations of users from distribution list 140.
  • Persons of skill in the art are able to use assignment tables 110 and 120 to let computer 900 selectively allow or reject such requests. In other words, the possibility of a user to request is related to the role.
  • central computer 900 relates to computer program product 100 with program instructions for processor 910 in central computer 900 (central computer 900 coupled to computer 901/902 that executes business application 201/202, peripheral computer 901/902 issuing alert message 211/212 when a current value of a predetermined variable in the business application is in a predetermined relation to a reference value), central computer 900 receiving alert message 201/202, CPP 100 is characterized in that the program instructions cause processor 910 of computer 900 to execute the following: upon receiving 420 alert message 211/212, forwarding 430 notification message 301 to communication devices 903, 904, 905 that present 440 a representation of notification 301 to a group of users 1, 2, 3; and issuing 460 further notification message 321 to a further user 4 outside the group in the event that during predetermined time period T no user of the group has confirmed reception of notification 301 by a receipt message 315.
  • CPP 100 causes processor 910 to derive 401 the group of users from a role-to-user assignment and from an application-to-role assignment.
  • CPP 100 causes processor 910 to store 402 representations of the group of users in message distribution list 140 and to receive 403 subscription requests to alert notification messages from the users of the group.
  • CPP 100 can be embodied in signal 980 and on carrier 970.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • General Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Tourism & Hospitality (AREA)
  • Information Transfer Between Computers (AREA)
  • Debugging And Monitoring (AREA)
  • Alarm Systems (AREA)
  • Telephonic Communication Services (AREA)

Claims (17)

  1. Système d'ordinateurs (999) comprenant un ordinateur central (900) et au moins un ordinateur périphérique (901/902) pour exécuter au moins une application d'affaires (201/202), l'ordinateur périphérique délivrant en outre un message d'alerte (211/212) lorsqu'une valeur en cours d'une variable prédéterminée dans l'application d'affaires présente une relation prédéterminée avec une valeur de référence, l'ordinateur central servant à recevoir le message d'alerte et, suivant un type prédéfini du message d'alerte, à transmettre un message de notification (301) à des dispositifs de communication (903, 904, 905) qui présentent une représentation du message de notification à un groupe prédéfini d'utilisateurs (1, 2, 3) ;
    dans le système d'ordinateurs, l'ordinateur central délivrant un autre message de notification (321) à un autre utilisateur (4) en dehors du groupe si, durant une période de temps prédéterminée, aucun utilisateur du groupe prédéfini n'a accusé réception de la notification, le système d'ordinateurs étant caractérisé en ce que
    le groupe prédéfini d'utilisateurs est déterminé à partir d'une liste de distribution de messages (140) établie à partir d'une affectation de rôles à des utilisateurs et d'une affectation d'applications à des rôles, les affectations définissant l'application d'affaires à laquelle chaque utilisateur a le droit d'accéder.
  2. Système selon la revendication 1, dans lequel le dispositif de communication (par ex. le dispositif 905) renvoie, sous l'instruction de l'utilisateur, un message de réception (315) à l'ordinateur central (900).
  3. Système selon la revendication 2, dans lequel le dispositif de communication (903-904) est un dispositif choisi dans un groupe comprenant : un télécopieur, un système de messagerie vocale, un récepteur d'appels sélectif, un téléphone portable doté d'un récepteur SMS, un dispositif audio, un convertisseur texte-parole doté d'un haut-parleur, un ordinateur personnel avec courrier électronique.
  4. Système selon la revendication 2, dans lequel le dispositif de communication présente la représentation de façon visuelle (953, 954, 955) ou sonore.
  5. Système selon la revendication 4, dans lequel le dispositif de communication exécute un programme de navigation.
  6. Système selon la revendication 5, dans lequel le dispositif de communication présente la représentation sous la forme d'un hyperlien (301-1) avec une version intégrale du message de notification.
  7. Système selon la revendication 1, dans lequel l'ordinateur central est mis en oeuvre sous la forme d'un serveur d'applications (900') sur le lieu de travail, grâce auquel les utilisateurs du groupe entrent en interaction avec des applications exécutées sur l'au moins un ordinateur périphérique (901/902).
  8. Système selon la revendication 7, dans lequel le serveur d'applications (900') sur le lieu de travail ajoute une suggestion de suivi (301-2) au message de notification, dont la description est choisie dans une table à consulter.
  9. Système selon la revendication 2, dans lequel l'ordinateur central (900) affecte un numéro d'identification unique au message de notification, et dans lequel le dispositif de communication renvoie le numéro d'identification dans le message de réception.
  10. Système selon la revendication 9, dans lequel le dispositif de communication (903-905) renvoie également une identification d'utilisateur à l'ordinateur central (900).
  11. Système selon la revendication 10, dans lequel l'ordinateur central (900) mémorise l'identification d'utilisateur.
  12. Système selon la revendication 1, dans lequel l'autre message de notification comprend une partie descriptive (321-1) pour indiquer qu'il s'agit d'une autre notification.
  13. Système selon la revendication 1, dans lequel le message de notification comprend des parties de texte prédéfinies (301-3, 301-4).
  14. Système selon la revendication 1, dans lequel le message de notification comprend des parties de texte adaptées de façon dynamique (301-3, 301-4) ayant trait à l'application d'affaires (201) dans lesquelles la valeur en cours de la variable prédéterminée présente une relation prédéterminée avec la valeur de référence.
  15. Procédé de notification d'alerte (400) pour un ordinateur central (900), le procédé comprenant les étapes suivantes :
    établissement (401) d'un groupe d'utilisateurs (1, 2, 3) à partir d'une affectation de rôles à des utilisateurs et d'une affectation d'applications à des rôles, l'affectation définissant au moins une application d'affaires à laquelle chaque utilisateur a le droit d'accéder ;
    mémorisation (402) de représentations du groupe d'utilisateurs (1, 2, 3) dans une liste de distribution de messages (140) et réception (403) de demandes d'abonnement à des messages de notification d'alerte en provenance des utilisateurs du groupe ;
    réception (420) d'un message d'alerte (211/212) par l'ordinateur central (900), le message d'alerte étant délivré (410) par au moins un ordinateur périphérique (901/902) qui exécute l'application d'affaires et qui détecte qu'une valeur en cours d'une variable prédéterminée dans l'application d'affaires présente une relation prédéterminée avec une valeur de référence ;
    transmission (430) d'un message de notification (301) à une pluralité de dispositifs de communication (903, 904, 905) présentant (440) une représentation de la notification au groupe d'utilisateurs (1, 2, 3) ; et
    délivrance (460) d'un autre message de notification à un autre utilisateur (4) en dehors du groupe si, durant une période de temps prédéterminée (T), aucun utilisateur du groupe n'a accusé réception de la notification (301) à l'aide d'un message de réception (315).
  16. Procédé selon la revendication 15, dans lequel les demandes d'abonnement ajoutent ou retirent de façon sélective des représentations d'utilisateurs à ou de la liste de distribution.
  17. Logiciel d'ordinateur (100) comprenant des instructions de programme pour un processeur (910) dans un ordinateur central (900), l'ordinateur central étant relié à au moins un ordinateur périphérique (901/902) qui exécute au moins une application d'affaires (201/202), l'ordinateur périphérique délivrant un message d'alerte (211/212) lorsqu'une valeur en cours d'une variable prédéterminée dans l'application d'affaires présente une relation prédéterminée avec une valeur de référence, l'ordinateur central (900) servant à recevoir un message d'alerte, le logiciel d'ordinateur comprenant des instructions de programme amenant le processeur de l'ordinateur central à exécuter les opérations suivantes :
    mémorisation (402) de représentations d'un groupe d'utilisateurs dans une liste de distribution de messages (140) et réception (403) de demandes d'abonnement à des messages de notification d'alerte en provenance des utilisateurs du groupe ;
    lors de la réception (420) du message d'alerte (211/212), transmission (430) d'un message de notification (301) à une pluralité de dispositifs de communication (903, 904, 905) présentant (440) une représentation de la notification au groupe d'utilisateurs (1, 2, 3) ;
    délivrance (460) d'un autre message de notification à un autre utilisateur (4) en dehors du groupe si, durant une période de temps prédéterminée (T), aucun utilisateur du groupe n'a accusé réception de la notification (301) à l'aide d'un message de réception (315),
    le logiciel d'ordinateur étant caractérisé en ce que les instructions de programme amènent le processeur à établir (401) le groupe d'utilisateurs à partir d'une affectation de rôles à des utilisateurs et d'une affectation d'applications à des rôles, l'affectation définissant l'application d'affaires à laquelle chaque utilisateur a le droit d'accéder.
EP01104875A 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte et exécution conditionelle Expired - Lifetime EP1239385B1 (fr)

Priority Applications (14)

Application Number Priority Date Filing Date Title
EP03007940A EP1339002A1 (fr) 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte
ES01104875T ES2202233T3 (es) 2001-02-28 2001-02-28 Sistema de ordenadores para aplicaciones de negocios con notificacion de avisos y cumplimiento condiconal.
PT01104875T PT1239385E (pt) 2001-02-28 2001-02-28 Sistema de computador para aplicacoes comerciais com notificacoes de alerta e execucao condicional
EP01104875A EP1239385B1 (fr) 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte et exécution conditionelle
AT01104875T ATE244423T1 (de) 2001-02-28 2001-02-28 Computersystem für geschäftsanwendungen mit alarmmeldung und bedingter inkraftsetzung
DK01104875T DK1239385T3 (da) 2001-02-28 2001-02-28 Computersystem for forretningsapplikationer med varsko-notifikation og betinget eksekvering
DE60100430T DE60100430T2 (de) 2001-02-28 2001-02-28 Computersystem für Geschäftsanwendungen mit Alarmmeldung und bedingter Inkraftsetzung
CA002439588A CA2439588A1 (fr) 2001-02-28 2002-02-27 Systeme informatique pour applications de gestion avec notification d'alerte et mise en oeuvre conditionnelle
PCT/EP2002/002113 WO2002073478A1 (fr) 2001-02-28 2002-02-27 Systeme informatique pour applications de gestion avec notification d'alerte et mise en oeuvre conditionnelle
IL15595702A IL155957A0 (en) 2001-02-28 2002-02-27 Computer system for business applications with alert notification and conditional enforcing
AU2002242711A AU2002242711B2 (en) 2001-02-28 2002-02-27 Computer system for business applications with alert notification and conditional enforcing
US10/469,336 US7409430B2 (en) 2001-02-28 2002-02-27 Notification message distribution
JP2002572064A JP3930432B2 (ja) 2001-02-28 2002-02-27 警報報知と条件付き実行を備えたビジネスアプリケーションのためのコンピュータシステム
US10/706,878 US7373388B2 (en) 2001-02-28 2003-11-12 Notification message distribution

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP01104875A EP1239385B1 (fr) 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte et exécution conditionelle

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP03007940A Division EP1339002A1 (fr) 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte

Publications (2)

Publication Number Publication Date
EP1239385A1 EP1239385A1 (fr) 2002-09-11
EP1239385B1 true EP1239385B1 (fr) 2003-07-02

Family

ID=8176626

Family Applications (2)

Application Number Title Priority Date Filing Date
EP01104875A Expired - Lifetime EP1239385B1 (fr) 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte et exécution conditionelle
EP03007940A Withdrawn EP1339002A1 (fr) 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP03007940A Withdrawn EP1339002A1 (fr) 2001-02-28 2001-02-28 Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte

Country Status (12)

Country Link
US (2) US7409430B2 (fr)
EP (2) EP1239385B1 (fr)
JP (1) JP3930432B2 (fr)
AT (1) ATE244423T1 (fr)
AU (1) AU2002242711B2 (fr)
CA (1) CA2439588A1 (fr)
DE (1) DE60100430T2 (fr)
DK (1) DK1239385T3 (fr)
ES (1) ES2202233T3 (fr)
IL (1) IL155957A0 (fr)
PT (1) PT1239385E (fr)
WO (1) WO2002073478A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7224957B2 (en) 2003-03-17 2007-05-29 Spector Shelley J Apparatus and method for broadcasting messages to selected group(s) of users
DE102006032355A1 (de) * 2006-07-13 2008-01-17 Matthias Wanner Computersystem mit einem Zentralcomputer und mindestens zwei Peripheriecomputern

Families Citing this family (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8868659B2 (en) 2001-05-15 2014-10-21 Avaya Inc. Method and apparatus for automatic notification and response
EP1298515A3 (fr) * 2001-09-26 2004-02-04 Siemens Aktiengesellschaft Procédé de contrôle d'accès à des ressources d'un système de traitement de données
US7219112B2 (en) * 2001-11-20 2007-05-15 Ip-First, Llc Microprocessor with instruction translator for translating an instruction for storing random data bytes
US7146320B2 (en) * 2002-05-29 2006-12-05 Microsoft Corporation Electronic mail replies with speech recognition
US7467183B2 (en) * 2003-02-14 2008-12-16 Microsoft Corporation Method, apparatus, and user interface for managing electronic mail and alert messages
US9448860B2 (en) * 2003-03-21 2016-09-20 Oracle America, Inc. Method and architecture for providing data-change alerts to external applications via a push service
WO2004092901A2 (fr) * 2003-04-11 2004-10-28 Richard Postrel Procede et systeme de synchronisation de commande
EP1486896A2 (fr) * 2003-06-13 2004-12-15 Sap Ag Système d'ordinateur et procédé implémenté par ordinateur pour la gestion des voyages
US8370436B2 (en) * 2003-10-23 2013-02-05 Microsoft Corporation System and method for extending a message schema to represent fax messages
US8150923B2 (en) * 2003-10-23 2012-04-03 Microsoft Corporation Schema hierarchy for electronic messages
US7424513B2 (en) * 2003-10-23 2008-09-09 Microsoft Corporation Decoupling an attachment from an electronic message that included the attachment
US7546640B2 (en) * 2003-12-10 2009-06-09 International Business Machines Corporation Fine-grained authorization by authorization table associated with a resource
US20050177630A1 (en) * 2003-12-19 2005-08-11 Jolfaei Masoud A. Service analysis
US7734731B2 (en) 2004-03-18 2010-06-08 Avaya Inc. Method and apparatus for a publish-subscribe system with third party subscription delivery
US7533149B2 (en) * 2004-04-30 2009-05-12 Microsoft Corporation Maintaining multiple versions of message bodies in a common database
US20060117336A1 (en) * 2004-10-20 2006-06-01 Dolgin Jess Z System and method for instantaneously deploying packetized alert data
US7747733B2 (en) 2004-10-25 2010-06-29 Electro Industries/Gauge Tech Power meter having multiple ethernet ports
US7277988B2 (en) 2004-10-29 2007-10-02 International Business Machines Corporation System, method and storage medium for providing data caching and data compression in a memory subsystem
US8756225B1 (en) * 2005-05-31 2014-06-17 Saba Software, Inc. Method and system for interfacing with a back end server application through a messaging environment
US20070073816A1 (en) * 2005-09-28 2007-03-29 Shruti Kumar Method and system for providing increased information and improved user controls for electronic mail return receipts
US20070094266A1 (en) * 2005-10-17 2007-04-26 Microsoft Corporation Collecting information on component implementation and use
JP5205695B2 (ja) * 2006-02-15 2013-06-05 富士通株式会社 表示制御プログラム、表示制御方法、クライアント装置及びシステム
US7486196B1 (en) * 2008-04-14 2009-02-03 International Business Machines Corporation Using audio to detect changes to the performance of an application
CN101668031B (zh) * 2008-09-02 2013-10-16 阿里巴巴集团控股有限公司 一种消息处理方法及系统
US8244669B2 (en) * 2008-12-30 2012-08-14 Blackboard Connect Inc. Dynamic formation of groups in a notification system
US20100199310A1 (en) * 2009-01-30 2010-08-05 Echostar Technologies L.L.C. Methods and devices for recommending media content
US8588733B2 (en) 2009-11-11 2013-11-19 Lifestream Corporation Wireless device emergency services connection and panic button, with crime and safety information system
US8954514B2 (en) * 2009-12-22 2015-02-10 Sprint Communications Company L.P. System and method for displaying time-sensitive alerts in a mobile device
JP5708168B2 (ja) * 2010-06-16 2015-04-30 株式会社リコー 伝送端末、伝送システム、伝送方法、及び伝送端末用プログラム
US8924489B2 (en) * 2011-01-05 2014-12-30 Apple Inc. Message push notification client improvements for multi-user devices
US9946988B2 (en) * 2011-09-28 2018-04-17 International Business Machines Corporation Management and notification of object model changes
US20170063566A1 (en) * 2011-10-04 2017-03-02 Electro Industries/Gauge Tech Internet of things (iot) intelligent electronic devices, systems and methods
US10771532B2 (en) 2011-10-04 2020-09-08 Electro Industries/Gauge Tech Intelligent electronic devices, systems and methods for communicating messages over a network
US20150356104A9 (en) 2011-10-04 2015-12-10 Electro Industries/Gauge Tech Systems and methods for collecting, analyzing, billing, and reporting data from intelligent electronic devices
US10862784B2 (en) 2011-10-04 2020-12-08 Electro Industries/Gauge Tech Systems and methods for processing meter information in a network of intelligent electronic devices
US10275840B2 (en) 2011-10-04 2019-04-30 Electro Industries/Gauge Tech Systems and methods for collecting, analyzing, billing, and reporting data from intelligent electronic devices
US12260078B2 (en) 2011-10-04 2025-03-25 Ei Electronics Llc Dynamic webpage interface for an intelligent electronic device
US9767668B2 (en) * 2013-03-14 2017-09-19 International Business Machines Corporation Automatic adjustment of metric alert trigger thresholds
US11816465B2 (en) 2013-03-15 2023-11-14 Ei Electronics Llc Devices, systems and methods for tracking and upgrading firmware in intelligent electronic devices
JP6200784B2 (ja) * 2013-11-13 2017-09-20 株式会社日立製作所 障害記録管理装置
US11734396B2 (en) 2014-06-17 2023-08-22 El Electronics Llc Security through layers in an intelligent electronic device
US10063507B2 (en) * 2014-09-08 2018-08-28 Accenture Global Services Limited Digital collaboration process enablement tool
US10958435B2 (en) 2015-12-21 2021-03-23 Electro Industries/ Gauge Tech Providing security in an intelligent electronic device
US10311696B2 (en) * 2017-04-26 2019-06-04 General Electric Company Patient monitoring method and system providing incident grouping of alarm events
US10637946B2 (en) 2017-08-15 2020-04-28 Microsoft Technology Licensing, Llc Subscription based event notifications
US11734704B2 (en) 2018-02-17 2023-08-22 Ei Electronics Llc Devices, systems and methods for the collection of meter data in a common, globally accessible, group of servers, to provide simpler configuration, collection, viewing, and analysis of the meter data
US11686594B2 (en) 2018-02-17 2023-06-27 Ei Electronics Llc Devices, systems and methods for a cloud-based meter management system
US11754997B2 (en) 2018-02-17 2023-09-12 Ei Electronics Llc Devices, systems and methods for predicting future consumption values of load(s) in power distribution systems
US12288058B2 (en) 2018-09-20 2025-04-29 Ei Electronics Llc Devices, systems and methods for tracking and upgrading firmware in intelligent electronic devices
CN111245875B (zh) * 2018-11-28 2022-03-04 京东方科技集团股份有限公司 事件通知方法、设备、装置和计算机存储介质
US12028430B2 (en) * 2018-11-28 2024-07-02 Beijing Boe Technology Development Co., Ltd. Event notification method, server device, apparatus and computer storage medium
US11863589B2 (en) 2019-06-07 2024-01-02 Ei Electronics Llc Enterprise security in meters
US11882003B2 (en) 2020-08-20 2024-01-23 Simetric, Inc. Device management systems and methods
CN112650655A (zh) * 2020-12-30 2021-04-13 深圳市世强元件网络有限公司 一种业务系统自动告警装置、方法及计算机设备

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5548753A (en) * 1994-09-14 1996-08-20 Johnson Service Company Automatic electronic mail notification of database events
US5754111A (en) * 1995-09-20 1998-05-19 Garcia; Alfredo Medical alerting system
US5748884A (en) * 1996-06-13 1998-05-05 Mci Corporation Autonotification system for notifying recipients of detected events in a network environment
US5786755A (en) 1997-02-12 1998-07-28 At&T Corp Alarm escalation method
US6185603B1 (en) 1997-03-13 2001-02-06 At&T Corp. Method and system for delivery of e-mail and alerting messages
US6092102A (en) * 1997-10-24 2000-07-18 University Of Pittsburgh Of The Commonwealth System Of Higher Education System and method for notifying users about information or events of an enterprise
US6202066B1 (en) * 1997-11-19 2001-03-13 The United States Of America As Represented By The Secretary Of Commerce Implementation of role/group permission association using object access type
US6157941A (en) 1998-03-18 2000-12-05 Oracle Corporation Architecture for client-server communication over a communication link
US6182142B1 (en) * 1998-07-10 2001-01-30 Encommerce, Inc. Distributed access management of information resources
US6067548A (en) * 1998-07-16 2000-05-23 E Guanxi, Inc. Dynamic organization model and management computing system and method therefor
US6347330B1 (en) 1998-09-04 2002-02-12 International Business Machines Corporation Dynamic selective distribution of events to server receivers
US6725445B1 (en) * 1999-07-08 2004-04-20 International Business Machines Corporation System for minimizing notifications in workflow management system
US6857017B1 (en) * 1999-10-11 2005-02-15 I2 Technologies Us, Inc. Customizable notification user window
US6751657B1 (en) * 1999-12-21 2004-06-15 Worldcom, Inc. System and method for notification subscription filtering based on user role
US6775658B1 (en) * 1999-12-21 2004-08-10 Mci, Inc. Notification by business rule trigger control
AU2001234587A1 (en) * 2000-01-26 2001-08-07 Yefim Zhuk Distributed active knowledge and process base
US6757357B1 (en) * 2000-02-29 2004-06-29 Bellsouth Intellectual Property Corporation Failure response procedure and system
US6766368B1 (en) * 2000-05-23 2004-07-20 Verizon Laboratories Inc. System and method for providing an internet-based correlation service
US7185192B1 (en) * 2000-07-07 2007-02-27 Emc Corporation Methods and apparatus for controlling access to a resource
US6772167B1 (en) * 2000-09-07 2004-08-03 International Business Machines Corporation System and method for providing a role table GUI via company group
US6985955B2 (en) * 2001-01-29 2006-01-10 International Business Machines Corporation System and method for provisioning resources to users based on roles, organizational information, attributes and third-party information or authorizations
CN1662901A (zh) * 2002-06-25 2005-08-31 国际商业机器公司 用于在分布式环境中监视应用性能的方法和系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7224957B2 (en) 2003-03-17 2007-05-29 Spector Shelley J Apparatus and method for broadcasting messages to selected group(s) of users
US7965995B2 (en) 2003-03-17 2011-06-21 Spector Shelley J Apparatus and method for broadcasting messages to selected group(s) of users
US8532609B2 (en) 2003-03-17 2013-09-10 One-12 Group L.L.C. Apparatus and method for broadcasting messages to selected group(s) of users
DE102006032355A1 (de) * 2006-07-13 2008-01-17 Matthias Wanner Computersystem mit einem Zentralcomputer und mindestens zwei Peripheriecomputern

Also Published As

Publication number Publication date
ATE244423T1 (de) 2003-07-15
CA2439588A1 (fr) 2002-09-19
PT1239385E (pt) 2003-11-28
EP1339002A1 (fr) 2003-08-27
EP1239385A1 (fr) 2002-09-11
US20040133646A1 (en) 2004-07-08
DE60100430T2 (de) 2004-04-15
JP2004530198A (ja) 2004-09-30
AU2002242711B2 (en) 2005-04-21
US7409430B2 (en) 2008-08-05
IL155957A0 (en) 2003-12-23
JP3930432B2 (ja) 2007-06-13
DK1239385T3 (da) 2003-10-20
ES2202233T3 (es) 2004-04-01
DE60100430D1 (de) 2003-08-07
US20040098459A1 (en) 2004-05-20
US7373388B2 (en) 2008-05-13
WO2002073478A1 (fr) 2002-09-19

Similar Documents

Publication Publication Date Title
EP1239385B1 (fr) Système d'ordinateur pour des logiciels d'affaires avec notification d'alerte et exécution conditionelle
AU2002242711A1 (en) Computer system for business applications with alert notification and conditional enforcing
US7337210B2 (en) Method and apparatus for determining availability of a user of an instant messaging application
US5960406A (en) Scheduling system for use between users on the web
US20110314481A1 (en) Dynamically generating and delivering information in response to the occurrence of an event
US8302012B2 (en) Providing status of portal content
US9986015B2 (en) Desktop assistant for multiple information types
US20040104931A1 (en) Portal-based desktop
CA2456126C (fr) Procede et systeme informatique destine a identifier des objets a archiver
JP2004530198A5 (fr)
AU2002355456A1 (en) Method and computer system for identifying objects for archiving
US20060059033A1 (en) Interaction object
US7606162B2 (en) Tracking of process-related communication
JP2004246901A (ja) ドキュメントコンテンツおよび配信設定を駆動するためのデータマッピングの使用
WO2002075528A1 (fr) Procede, programme informatique et ordinateur permettant de selectionner automatiquement des services logiciels pour transmettre des donnees depuis un serveur vers un client en fonction du type de dispositif client
US20080148158A1 (en) Method, system, and program product for differentially displaying an instant messaging (im) availability
US7475355B2 (en) Integrated e-mail system
JP2024172364A (ja) 業務管理システム
EP1677479B1 (fr) Surveillance de communication liée à un processus
Salami et al. Towards a context-aware multi-channel messaging model for African banks: preliminary investigations
CN118193592A (zh) 基于流式处理的数据处理方法、装置、设备及介质
Kantor Push technologies for enhancing awareness and coordination
EP1580944A1 (fr) Acheminement de messages d'un demandeur à un fournisseur basé sur l'histoire des activités
KR20030093871A (ko) 협업 메일 시스템
HK1134351B (en) Email forms engine for portable devices

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20010323

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17Q First examination report despatched

Effective date: 20021115

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AKX Designation fees paid

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AK Designated contracting states

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60100430

Country of ref document: DE

Date of ref document: 20030807

Kind code of ref document: P

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: GR

Ref legal event code: EP

Ref document number: 20030404027

Country of ref document: GR

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20040228

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20040228

PLBQ Unpublished change to opponent data

Free format text: ORIGINAL CODE: EPIDOS OPPO

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2202233

Country of ref document: ES

Kind code of ref document: T3

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

PLAX Notice of opposition and request to file observation + time limit sent

Free format text: ORIGINAL CODE: EPIDOSNOBS2

ET Fr: translation filed
26 Opposition filed

Opponent name: MATTHIAS WANNER, GESCHAEFTSFUEHRER DES IBW, INGENI

Effective date: 20040324

NLR1 Nl: opposition has been filed with the epo

Opponent name: MATTHIAS WANNER, GESCHAEFTSFUEHRER DES IBW, INGENI

PLBB Reply of patent proprietor to notice(s) of opposition received

Free format text: ORIGINAL CODE: EPIDOSNOBS3

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: SAP AG

NLT2 Nl: modifications (of names), taken from the european patent patent bulletin

Owner name: SAP AG

Effective date: 20051012

PLAY Examination report in opposition despatched + time limit

Free format text: ORIGINAL CODE: EPIDOSNORE2

PLAH Information related to despatch of examination report in opposition + time limit modified

Free format text: ORIGINAL CODE: EPIDOSCORE2

PLBC Reply to examination report in opposition received

Free format text: ORIGINAL CODE: EPIDOSNORE3

PLCK Communication despatched that opposition was rejected

Free format text: ORIGINAL CODE: EPIDOSNREJ1

PLBN Opposition rejected

Free format text: ORIGINAL CODE: 0009273

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: OPPOSITION REJECTED

27O Opposition rejected

Effective date: 20070115

NLR2 Nl: decision of opposition

Effective date: 20070115

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DK

Payment date: 20110210

Year of fee payment: 11

Ref country code: IE

Payment date: 20110218

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20110216

Year of fee payment: 11

Ref country code: IT

Payment date: 20110221

Year of fee payment: 11

Ref country code: SE

Payment date: 20110214

Year of fee payment: 11

Ref country code: PT

Payment date: 20110217

Year of fee payment: 11

Ref country code: AT

Payment date: 20110214

Year of fee payment: 11

Ref country code: TR

Payment date: 20110221

Year of fee payment: 11

Ref country code: FI

Payment date: 20110214

Year of fee payment: 11

Ref country code: CH

Payment date: 20110222

Year of fee payment: 11

REG Reference to a national code

Ref country code: DK

Ref legal event code: EAP

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20110222

Year of fee payment: 11

Ref country code: BE

Payment date: 20110211

Year of fee payment: 11

BERE Be: lapsed

Owner name: *SAP A.G.

Effective date: 20120228

REG Reference to a national code

Ref country code: PT

Ref legal event code: MM4A

Free format text: LAPSE DUE TO NON-PAYMENT OF FEES

Effective date: 20120831

REG Reference to a national code

Ref country code: NL

Ref legal event code: V1

Effective date: 20120901

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120229

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120229

Ref country code: FI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120228

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120301

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120831

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120228

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 244423

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120228

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120228

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120901

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20130823

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120301

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120228

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 60100430

Country of ref document: DE

Representative=s name: MUELLER-BORE & PARTNER PATENTANWAELTE PARTG MB, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 60100430

Country of ref document: DE

Owner name: SAP SE, DE

Free format text: FORMER OWNER: SAP AG, 69190 WALLDORF, DE

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GR

Payment date: 20150123

Year of fee payment: 15

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 60100430

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0017600000

Ipc: G06Q0010000000

Ref country code: DE

Ref legal event code: R079

Ref document number: 60100430

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06Q0010060000

Ipc: G06Q0010000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: CY

Payment date: 20150122

Year of fee payment: 15

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160228

Ref country code: GR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160905

REG Reference to a national code

Ref country code: GR

Ref legal event code: ML

Ref document number: 20030404027

Country of ref document: GR

Effective date: 20160905

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20200219

Year of fee payment: 20

Ref country code: DE

Payment date: 20200219

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20200219

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 60100430

Country of ref document: DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20210227

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20210227

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载