[go: up one dir, main page]

WO2000060433A9 - Techniques d'echange d'informations sur des evenements entre plusieurs utilisateurs et applications - Google Patents

Techniques d'echange d'informations sur des evenements entre plusieurs utilisateurs et applications

Info

Publication number
WO2000060433A9
WO2000060433A9 PCT/US2000/009457 US0009457W WO0060433A9 WO 2000060433 A9 WO2000060433 A9 WO 2000060433A9 US 0009457 W US0009457 W US 0009457W WO 0060433 A9 WO0060433 A9 WO 0060433A9
Authority
WO
WIPO (PCT)
Prior art keywords
application
event
users
action
user
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.)
Ceased
Application number
PCT/US2000/009457
Other languages
English (en)
Other versions
WO2000060433A3 (fr
WO2000060433A2 (fr
Inventor
Taha Khedro
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.)
ATTIVO SOFTWARE Inc
Original Assignee
ATTIVO SOFTWARE 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
Application filed by ATTIVO SOFTWARE Inc filed Critical ATTIVO SOFTWARE Inc
Priority to AU44531/00A priority Critical patent/AU4453100A/en
Publication of WO2000060433A2 publication Critical patent/WO2000060433A2/fr
Publication of WO2000060433A3 publication Critical patent/WO2000060433A3/fr
Anticipated expiration legal-status Critical
Publication of WO2000060433A9 publication Critical patent/WO2000060433A9/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/451—Execution arrangements for user interfaces

Definitions

  • the present invention relates to communicating (or sharing) information in multiple user environments. More specifically, the invention relates to capturing application events and propagating the application events to interested users so that the users can coordinate working together.
  • Computers are amazing tools that allow us to perform many tasks efficiently in both the work place and the home. Perhaps the most common application that is run on computers is the word processing program that allows users to produce documents including letters, reports, articles, books, and the like. Computer applications can also be used to produce spreadsheets, slide presentations, databases, drawings, and many more.
  • Database applications provide a good example of allowing users to work on projects in parallel. Many database applications allow multiple users to access the database simultaneously. When a user is accessing a record of the database, that record is typically locked so that the integrity of the information stored in the database is maintained.
  • a database application By locking a record, a database application allows multiple users to access and enter data in the database simultaneously.
  • the present invention provides techniques for communicating application events among multiple users. More specifically, application events are detected and propagated to other interested users (via applications) encapsulated in action messages.
  • the interested users whose privileges allow them to receive the application events can decide on a case by case basis whether to accept the application event. In addition, the interested users can decide to accept or reject all the application events that are received.
  • the invention allows multiple users to work together more efficiently and with more knowledge than is provided prior art techniques. Several embodiments of the invention are described below.
  • the invention provides a method of distributing an application event.
  • An event from a user to an application is captured. Once captured, information about the event is obtained and a message that includes the event and the information about the event is created. The message that is created is then sent to interested users.
  • the invention provides a method of propagating an action message.
  • An action message including a header and a self contained object is received.
  • Information from the header and the self contained object is extracted from the action message.
  • the appropriate call to apply data of the self contained object to an application is determined and the call is made to realize the action message in the application.
  • the call is an application programming interface (API) call.
  • API application programming interface
  • the invention provides a method of processing transactions.
  • a transaction for an application including at least one action message is received.
  • An action message in the transaction is selected and it is determined if the action message includes new content. If the action message includes new content, the new content is added to a content list. Users that are interested in the action message are identified and the access privileges of those users that interested are checked. The action message is put in a local queue for the application for the users that are interested and have appropriate access privileges.
  • the invention provides a method of sending action messages. A check is made to determine if an application having action messages in a local queue is online on the same activity. If the application is online, a transaction that includes the action messages is sent to a remote agent. Otherwise, if the application is not online, the action messages are saved until the application is online.
  • the invention provides a system for communicating action messages among users.
  • the system includes an application that executes on computer systems for multiple users.
  • An agent executes on each computer system that detects application events and sends the application events to a coordinator. The coordinator determines the users that are interested in each application event and sends the application events to the agents on the computer systems of interested users.
  • FIG. 1 illustrates an example of a computer system that can be utilized to execute the software of an embodiment of the invention.
  • FIG. 2 illustrates a system block diagram of the computer system of FIG. 1.
  • FIG. 3 shows a network of multiple computer systems.
  • FIG. 4 shows the interaction of a typical user with an application, such as a word processor or database management system.
  • FIG. 5 shows a system of one embodiment of the invention that allows users to receive application events generated by other users.
  • FIG. 6 illustrates queues that may be maintained for each application by an agent of the invention.
  • FIG. 7 shows queues that may be maintained for each activity of an application by a coordinator of the invention.
  • FIG. 8 shows a flow chart of a process of distributing an application event to interested users.
  • FIGS. 9A and 9B show a flow chart of another process of distributing an application event to interested users.
  • FIG. 10 shows a flow chart of a process of propagating the action message so that the action message can be utilized in the application.
  • FIGS. 11A-11C show a flow chart of a process of processing transactions so that action messages in the transactions can be sent to interested users that have the appropriate access privileges.
  • FIG. 12 shows a flow chart of a process of sending action messages when the user is online with the same activity.
  • FIG. 1 illustrates an example of a computer system that can be used to execute the software of an embodiment of the invention.
  • FIG. 1 shows a computer system 1 that includes a display 3, screen 5, cabinet 7, keyboard 9, and mouse 11. Mouse 11 can have one or more buttons for interacting with a graphical user interface.
  • Cabinet 7 houses a CD-ROM drive 13, system memory and a hard drive (see FIG. 2) which can be utilized to store and retrieve software programs incorporating computer code that implements the invention, data for use with the invention, and the like.
  • CD-ROM 15 is shown as an exemplary computer readable storage medium, other computer readable storage media including floppy disk, tape, flash memory, system memory, and hard drive can be utilized.
  • a data signal embodied in a carrier wave e.g., in a network including the Internet
  • a carrier wave e.g., in a network including the Internet
  • FIG. 2 shows a system block diagram of computer system 1 used to execute the software of an embodiment of the invention.
  • computer system 1 includes monitor 3 and keyboard 9, and mouse 11.
  • Computer system 1 further includes subsystems such as a central processor 51, system memory 53, fixed storage 55 (e.g., hard drive), removable storage 57 (e.g., CD-ROM drive), display adapter 59, sound card 61, speakers 63, and network interface 65.
  • Other computer systems suitable for use with the invention can include additional or fewer subsystems.
  • another computer system could include more than one processor 51 (i.e., a multi-processor system) or a cache memory.
  • the system bus architecture of computer system 1 is represented by arrows 67.
  • FIG. 2 is but an example of a computer system suitable for use with the invention.
  • Other computer architectures having different configurations of subsystems can also be utilized.
  • FIG. 3 shows a network that connects multiple computer systems, such as the ones shown in FIGS. 1 and 2. As shown, multiple computer systems 1 are interconnected through a network 101. Network 101 allows the computer systems to share data and resources. Typically, the computer system that controls access to data or a resource is called the server because it provides access to client computer systems.
  • the network can be any kind of network including a local area network (LAN) and wide area network (WAN), such as the Internet.
  • LAN local area network
  • WAN wide area network
  • FIG. 4 illustrates a user interacting with a typical application, which in this case is a word processor or database application.
  • a user 201 interacts with a graphical user interface (GUI) 203.
  • GUI 203 allows the user to enter and receive data through an interface that is easy for the user to utilize.
  • GUI events are sent to application logic 205.
  • Application logic 205 receives GUI events and processes them to perform the actions requested by the user.
  • the actions can include any number of forms including storing data in a database 207, files 209, retrieving stored data, making calculations on data, and displaying information through GUI 203, just to name a few.
  • API 211 allows for programmatic data entry/access 213.
  • API 211 provides calls that direct the application to perform specific actions.
  • the API calls can be thought of as a back door through which to direct the application.
  • APIs can provide access to application events generated by applications as a result of user interaction.
  • FIG. 5 shows a system that allows application events to be detected and propagated to other users according to the invention.
  • a user 301 can interact with applications 303 and 305. The interaction with the applications can be as described in reference to FIG. 4. Accordingly, user 301 may interact with applications 303 and 305 utilizing a graphical user interface for the applications (not shown).
  • a GUI 307 allows user 301 to, among other things, view application events that have been sent to the user, as well as generated by local applications, and specify what should be done with application events and configure the users preferences.
  • An agent 309 monitors application events including GUI events so that they can be propagated or sent to interested users. Agent 309 can store the application events that are to be sent to the interested users.
  • agent 309 has captured an event that may be of interest to other users.
  • agent 309 Once agent 309 captures an application event, the agent sends the application event to a coordinator 311.
  • action message When used herein, the term "action message" will be used to denote a message that includes an application event and additional information regarding the application event.
  • multiple application events can be sent together as a transaction in order to make the system more efficient.
  • Coordinator 311 receives the application event and determines if there are users interested in receiving the event. For example, coordinator 311 can maintain a list of application events in which users are interested. Coordinator 311 determines if there are any users that are interested in the received application event and then determines if the users have the appropriate access privileges to receive the event. For example, the action message can include the access privileges that specify the users that are allowed to receive the application event.
  • coordinator 311 determines if the interested user is online on the same activity of the application in which the application event was generated. If so, coordinator 311 sends an action message, preferably bundled in a transaction, to an agent 313.
  • Agent 313 monitors applications 315 and 317 for application events. Additionally, agent 313 receives application events from coordinator 311 and can propagate the application events to integrated applications 315 and/or 317.
  • a GUI 319 allows a user 321 to view application events that have been specified should only be committed to applications upon user confirmation. In order to finish this example, GUI 319 could display an application event that was generated by user 301. User 321 could then specify through GUI 319 that the application event should be accepted and agent 313 would make the appropriate calls to commit the application event to the appropriate application, which could be application 315 as an example.
  • coordinator 311 has described coordinator 311 as receiving application events and determining users that may be interested in the application events. These functions can also be performed by an agent. Additionally, a GUI can be used to communicate directly with coordinator 311, such as in an embodiment where a web based GUI communicates with the coordinator.
  • FIG. 5 has been described in a high level to introduce several aspects of the invention. For simplicity, only two users and two applications were shown. However, a system can include many more users and many more applications. Also, there can be multiple coordinators (see dashed lines in FIG. 5) and the agents and coordinators can be on the same or different computer systems. Furthermore, the system was described as propagating an application event from user 301 to user 321, but this process can be bidirectional and the application events can be propagated to multiple interested users.
  • the network configuration of the system shown in FIG. 5 can be varied, a typical configuration is that a client computer system 323 interacts with user 301 and a client computer system 325 interacts with user 321.
  • a server computer system 327 includes coordinator 311 and therefore coordinates communication among multiple users. Other network configurations can also be utilized in different environments.
  • FIG. 6 shows queues that may be utilized to store action messages for each application.
  • An application 401 is monitored by an agent.
  • the agent maintains an in queue 403 that stores action messages that are to be sent to application 401.
  • an out queue 405 stores action messages that have been sent form application 401.
  • the queues are utilized to more efficiently organize the action messages that are being routed through the agent.
  • Action messages are also routed through the coordinator so it is also beneficial to maintain queues for the coordinator.
  • FIG. 7 shows queues that can be utilized to store action messages for the coordinator.
  • the coordinator can organize the action messages in terms of activity (or session), application, and then whether the action messages are being sent to or from the application of interest.
  • Application 501 has had two (or more) activities 503 and 505 online. For each activity, the coordinator maintains in queues 507 and out queues 509. In queues 507 store action messages that have been received from the agents and out queues 509 store action messages that are to be sent to the agents.
  • FIG. 8 shows a flow chart of a process of distributing an application event.
  • an event from the user to an application is captured.
  • the event is typically an application event and can include GUI, application logic, and database events.
  • the event is typically captured by an agent that monitors events generated by an application as a result of user interaction.
  • Information about the event is obtained at a step 603.
  • the information can include the identity of the user who is generating the event, the date and time of the event, the object or component on which the event is performed, creator/user, the owner of the object or component, the last updated time, the application in which the event was generated, and access privileges of who can receive the action message including this event.
  • FIG. 8 shows a high level process of distributing an application event and FIGS. 9A and 9B show more details in another embodiment.
  • FIGS. 9A and 9B show a flow chart of a process of distributing an application event.
  • a user interacts with an application.
  • the user may be entering data, accessing data or performing any other functions within the application.
  • the system generates an application event at a step 653.
  • the application event is detected and the event type of the application event is determined.
  • the application event is detected and initially processed by an agent running on the system in which the application event was generated.
  • the event type can be that data was added, deleted, modified, and the like.
  • the object that is associated with the event is found at step 657. Once the object has been identified, information about the object including the schema of the object is extracted at a step 659.
  • information for a header of the action message is determined.
  • the information may include the user who caused the application event to be generated, the date of the application event, the owner of the object that is acted on by the application event, the last update date and time of the object, and any other information that may be desired.
  • a self contained object and schema is created at a step 663.
  • the self contained object and schema (also called an "action object") can include the event type (such as added, deleted, modified, etc.), context of the event, status, and access privileges.
  • the access privileges can be whether the action message, and underlying application event, is private, can be distributed to the public at large, or can only be distributed to certain users.
  • the schema is the structure of the object and can include the super class, class, and list of properties, where each property includes a name, value, type, and unit.
  • the super class of an object could be "entity” and the class could be "circle.”
  • the list of properties could include definitions for the radius, center, color and the like of the circle.
  • the name of the property could be radius, the value could be "r,” the type could be "float,” and the unit "inches.”
  • the action message is created and includes the self contained object and the header. Accordingly, the action message is an encapsulation of the application event and includes other information that may be beneficial in replicating the application event in another user's activity of the application.
  • the action message is sent to interested users at 667. In a preferred embodiment, the action message is sent by an agent to a coordinator.
  • FIG. 10 shows a flow chart of a process of propagating the action message in a activity of an application of another user.
  • the action message is received.
  • the action message is received by an agent that is monitoring the application events of another user.
  • the information from the message header is extracted.
  • the self contained object is extracted from the action message at a step 705.
  • the self contained object is examined to determine the appropriate call to apply the self contained object data to the application at a step 708.
  • the call e.g., API call
  • the call is made to realize the action message, and underlying application event, in the application at a step 709.
  • the flow described in FIG. 10 is performed by an agent. Therefore, FIGS. 9A-9B and 10 have described processes that may be performed by the agents.
  • FIGS. 11 A-l 1C show a process of processing transactions that will include a process that a coordinator may perform to coordinate between the agents at either end of the action message.
  • a user gets online with an application on a computer system.
  • the user is online with the activity of the application.
  • the user performs an operation that generates an application event.
  • the application event is detected by the agent, which precedes to generate an action message as described in FIGS. 9 A and 9B.
  • the agent will send the transaction to the coordinator. This is denoted by the user committing a transaction at a step 805.
  • the coordinator receives the transaction and acknowledges receipt back to the agent.
  • the coordinator starts processing the transaction at a step 809.
  • the coordinator checks if the transaction has more action message to process at a step 811. If it is determined that there are more action messages to process at a step 813, the coordinator gets the next action message to process at a step 815.
  • the coordinator examines the content of the action message to determine if the action message includes new content.
  • the content can be utilized by users to specify application events in which they are interested. If it is determined that the action message includes new content at a step 819, the coordinator adds the new content to a content list at a step 821.
  • the coordinator identifies users that are interested in the action message and underlying application event. Once the coordinator has identified interested users, the coordinator checks the access privileges of those interested at a step 825 to determine if they can receive the action message.
  • the access privileges of the action event can be specified in a self contained object in the action message as described previously.
  • the coordinator puts the appropriate messages in each application's out queue at a step 827. Referring back to FIG. 7, the coordinator may place the action messages in out queues 509 of the activity of the application.
  • FIG. 12 shows a flow chart of a process of sending action messages to interested users.
  • the coordinator checks if the application is online on the same activity. If it is determined that the application is online on the same activity at a step 903, the coordinator sends a transaction including the action messages to the agent representing that application at a step 905. Once the agent receives the transaction, the agent will respond with an acknowledgement that is received by the coordinator at a step 907.
  • the coordinator saves the action messages in the out queue until the user is online with the activity at a step 909.
  • the agent can propagate the action messages as described in FIG. 10.
  • a user can specify whether action messages will be automatically accepted and committed to an application or whether the user would like to manually review the action messages and accept only those action messages that they are interested. For example, if a user specifies that all action messages should be automatically accepted, the agent will automatically extract the underlying application events and commit them to the appropriate application. However, if the user specifies that the action messages should be manually accepted, the agent will display the underlying application events to the user so that the user can select those that should be accepted and committed.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne des techniques d'échange d'informations sur des événements entre plusieurs utilisateurs et applications. On contrôle et on détecte des événements se produisant dans une application de manière à pouvoir créer des messages d'action concernant l'événement d'application et d'autres informations sur l'événement. Les messages d'action sont envoyés aux utilisateurs intéressés de sorte que l'événement se produisant dans l'application sous-jacent puisse être dupliqué dans une application intéressant l'utilisateur. Ainsi, on peut coordonner des événements d'application simultanément entre plusieurs utilisateurs.
PCT/US2000/009457 1999-04-07 2000-04-06 Techniques d'echange d'informations sur des evenements entre plusieurs utilisateurs et applications Ceased WO2000060433A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU44531/00A AU4453100A (en) 1999-04-07 2000-04-06 Techniques for communicating events among users and applications

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US28786699A 1999-04-07 1999-04-07
US09/287,866 1999-04-07

Publications (3)

Publication Number Publication Date
WO2000060433A2 WO2000060433A2 (fr) 2000-10-12
WO2000060433A3 WO2000060433A3 (fr) 2001-04-19
WO2000060433A9 true WO2000060433A9 (fr) 2002-04-04

Family

ID=23104705

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/009457 Ceased WO2000060433A2 (fr) 1999-04-07 2000-04-06 Techniques d'echange d'informations sur des evenements entre plusieurs utilisateurs et applications

Country Status (2)

Country Link
AU (1) AU4453100A (fr)
WO (1) WO2000060433A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8984386B2 (en) 2000-11-29 2015-03-17 Dov Koren Providing alerts in an information-sharing computer-based service

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6608945B2 (en) 2001-05-17 2003-08-19 Optronx, Inc. Self-aligning modulator method and associated apparatus

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5008853A (en) * 1987-12-02 1991-04-16 Xerox Corporation Representation of collaborative multi-user activities relative to shared structured data objects in a networked workstation environment
JP3064469B2 (ja) * 1991-04-19 2000-07-12 株式会社日立製作所 Ｃａｄ部品管理システム
US5634016A (en) * 1993-01-21 1997-05-27 Blade Software, Inc. Event management system
US5819243A (en) * 1996-11-05 1998-10-06 Mitsubishi Electric Information Technology Center America, Inc. System with collaborative interface agent

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8984386B2 (en) 2000-11-29 2015-03-17 Dov Koren Providing alerts in an information-sharing computer-based service
US8984387B2 (en) 2000-11-29 2015-03-17 Dov Koren Real time sharing of user updates
US9098829B2 (en) 2000-11-29 2015-08-04 Dov Koren Sharing of information associated with events
US9098828B2 (en) 2000-11-29 2015-08-04 Dov Koren Sharing of information associated with events
US9105010B2 (en) 2000-11-29 2015-08-11 Dov Koren Effective sharing of content with a group of users
US9208469B2 (en) 2000-11-29 2015-12-08 Dov Koren Sharing of information associated with events
US9535582B2 (en) 2000-11-29 2017-01-03 Dov Koren Sharing of information associated with user application events

Also Published As

Publication number Publication date
AU4453100A (en) 2000-10-23
WO2000060433A3 (fr) 2001-04-19
WO2000060433A2 (fr) 2000-10-12

Similar Documents

Publication Publication Date Title
US7454516B1 (en) Scalable virtual partitioning of resources
US6901405B1 (en) Method for persisting a schedule and database schema
JP4594306B2 (ja) 自己記述型ビジネスオブジェクト
US6266716B1 (en) Method and system for controlling data acquisition over an information bus
US6704804B1 (en) Method and system for communicating information among interactive applications
US8146054B2 (en) Hybrid data object model
US7577731B2 (en) System and method for monitoring program code
US8447745B2 (en) Synchronizing field values in an on-demand database prior to committing a change
JP4571636B2 (ja) サービス指向ビジネスフレームワークのサービス管理
KR101219856B1 (ko) 데이터 프로세싱을 자동화하기 위한 방법 및 시스템
US20050154711A1 (en) System and method for context sensitive searching
US7082457B1 (en) System and method for delegation in a project management context
JP2000029814A (ja) サ―バ・パフォ―マンスを改良するためのシステムおよび方法
JPH11327919A (ja) オブジェクト指向割込みシステム用の方法およびデバイス
TW201901491A (zh) 一種關聯信息查詢方法、終端及設備
CN112181704A (zh) 一种大数据任务处理方法、装置、电子设备及存储介质
US7188111B2 (en) System and method for connectivity to structured query language database
CN113626869A (zh) 数据处理方法、系统、电子设备以及存储介质
US7890535B2 (en) Management of processes based on reference information
US20070033640A1 (en) Generic context service in a distributed object environment
WO2001033362A1 (fr) Action de communication et de synchronisation pour documents consultes par plusieurs utilisateurs
US7805422B2 (en) Change notification query multiplexing
WO2000060433A9 (fr) Techniques d'echange d'informations sur des evenements entre plusieurs utilisateurs et applications
US20070192405A1 (en) Assured validation for facade method invocations
US20050097555A1 (en) Method, system and program product for processing a transaction

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK 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 MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK 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 MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

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

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

AK Designated states

Kind code of ref document: C2

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK 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 MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C2

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

COP Corrected version of pamphlet

Free format text: PAGES 1/14-14/14, DRAWINGS, REPLACED BY NEW PAGES 1/14-14/14; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: COMMUNICATION PURSUANT TO RULE 85A(1) EPC - NON-PAYMENT OF THE NATIONAL BASIC FEE AND THE SEARCH FEE COMMUNICATION PURSUANT TO RULES 85A AND 8

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS (R. 69(1)EPC) EPO FORM 2524 SENT ON 18.02.03

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP