WO2000078006A2 - Procede de communication par internet - Google Patents

Procede de communication par internet Download PDF

Info

Publication number
WO2000078006A2
WO2000078006A2 PCT/US2000/016371 US0016371W WO0078006A2 WO 2000078006 A2 WO2000078006 A2 WO 2000078006A2 US 0016371 W US0016371 W US 0016371W WO 0078006 A2 WO0078006 A2 WO 0078006A2
Authority
WO
WIPO (PCT)
Prior art keywords
condition
event
container
exchange
action
Prior art date
Application number
PCT/US2000/016371
Other languages
English (en)
Other versions
WO2000078006A3 (fr
Inventor
Israel Hilerio
Vijayasarathy S. Chakravarthy
Ajit Sagar
Original Assignee
I2 Technologies, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US09/592,775 external-priority patent/US7277863B1/en
Application filed by I2 Technologies, Inc. filed Critical I2 Technologies, Inc.
Priority to AU57377/00A priority Critical patent/AU5737700A/en
Publication of WO2000078006A2 publication Critical patent/WO2000078006A2/fr
Publication of WO2000078006A3 publication Critical patent/WO2000078006A3/fr

Links

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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates generally to communications systems and control for computer networks, and more specifically to an intelligent control system for use with a message exchange network.
  • High-level communications interconnectivity between companies allows them to establish relationships not hereto possible. Separate companies are beginning to establish communication links which allow them to cooperate much more closely with suppliers and customers. For example, systems currently coming into use are allowing companies to take an order for a customer, confirm availability of products from suppliers, and confirm to the customer a shipping date for the order. As a network available to everyone, the internet is the generally accepted vehicle for implementing these systems.
  • a communication system provides an exchange service between multiple companies. Messages between companies are routed through the exchange. These messages may represent any data or functionality desired by the companies. These messages may be requests, quotes, replies, and similar messages. Certain types of messages are designated as events to the exchange system. A portion of the exchange handles these events with rules, producing actions and additional events in response to occurrences consistent with the rules.
  • Figure 1 is a high level diagram showing an exchange communication system for transacting business between numerous companies
  • Figure 2 is a dataflow diagram illustrating an exchange of messages between companies
  • Figure 3 is a block diagram showing the structure of a preferred event-condition- action control system
  • Figures 4 and 5 are block diagrams illustrating examples of how the preferred embodiment functions
  • Figures 6, 7, and 8 are petri-net examples illustrating operation of control logic of the preferred embodiment.
  • Figure 9 is a petri-net illustrating control flow in a transaction example.
  • a centralized communications service hereinafter referred to as an exchange 10
  • an exchange 10 is provided in communication with numerous corporate computer systems.
  • users of the exchange are grouped into suppliers 12, manufacturers 14, resellers 16, customers 18, and logistics 20.
  • suppliers 12, manufacturers 14, resellers 16, customers 18, and logistics 20 are represented by numerous companies.
  • any one company may fall under different categories at different times.
  • a manufacturer may have numerous suppliers, each of which considers that manufacturer to be a customer.
  • Each of the suppliers may in turn have suppliers of their own.
  • Companies designated as resellers may be considered as suppliers to one manufacturer or customer, and customers to another. It will be understood that the functional groupings shown in Figure 1 are for convenience only, and many relationships are not easily formed into a simplistic definition.
  • the exchange service provides a mechanism for routing messages between companies. These messages can be formatted in numerous ways so that companies having disparate computer systems can communicate effectively.
  • the messaging system is independent of the system designs used by various companies, but the particular messaging system utilized does not itself form a part of the present invention.
  • those companies designated as logistics are generally shippers of physical items. Including shipment details in a communications network so that they can be accessed improves efficiency of the overall system.
  • FIG. 2 an example is shown of a particular simple transaction to illustrate how the exchange works.
  • four separate companies are designated as customer 22, reseller 24, manufacturer 26, and logistics 28, or transportation.
  • customer 22, reseller 24, manufacturer 26, and logistics 28, or transportation are designated as customer 22, reseller 24, manufacturer 26, and logistics 28, or transportation.
  • the relationships between these companies can change in the context of a different transaction.
  • the customer 22 sends an order message A through the exchange 10 to reseller 24.
  • This order can be a firm order, a request for a quotation, or similar request.
  • reseller 24 sends messages B and C to manufacturer
  • Messages B and C pass through the exchange 10 to these companies.
  • the manufacturer 26 determines the terms upon which it can supply the order, and returns message D through the exchange 10 to reseller 24.
  • the logistics company 28 determines availability of shipping, and returns message E with this information to reseller 24.
  • shipping information may pass between manufacturer 26 and logistics company 28, with shipping being a part of message D returned from manufacturer 26 to reseller 24.
  • reseller 24 determines availability in terms of the order based upon a promise from the manufacturer 26. In addition, shipping date and terms are determined. This information is placed into message F, which is returned through the exchange 10 to customer 22. In this example, placing an order and the relationships between various companies are straightforward. However, use of the exchange 10 becomes more valuable if it can contain intelligence of its own, and perform more complex tasks.
  • customers will often want to request quotes from several suppliers, or possibly even select one or more suppliers through an auction or similar process.
  • This can involve the customer placing an order to a shared location in a manner that is available to all interested suppliers. Any supplier who wishes to bid on the order can do so, and the exchange can handle collecting quotes and making it available to the customer as is described below.
  • suppliers can automate, or partially automate, the interface between themselves and their potential customers.
  • simple orders can be responded to automatically. For example, in the same communications sequence given above in Figure 2, messages B and C generated by reseller need not be generated as the result of human interaction.
  • this order is one of a standard type which fits certain parameters, as selected by reseller 24, messages B and C can be generated automatically upon receipt of a qualifying order.
  • This type of automated message handling can, of course, be provided independently by the reseller, but in the preferred embodiment of the present invention certain functions are available within the exchange itself. This provides enhanced flexibility and service to companies using the exchange, with minimum software generation requirements for these companies.
  • the exchange itself is depicted in the drawings as a single, central object. However, in reality it will be a multi-part, highly distributed service. Insofar as the various users are concerned, the exchange will look like a single object in the same manner that most users view the Internet today. However, the various pieces of the exchange will be located on a large number of systems, providing capacity, flexibility, and system robustness. Preferably, backup devices and fault tolerant systems are provided using techniques known in the art.
  • An event container 30 accepts incoming events (messages) 32, and stores date and time information about them. As described below, the event container preferably contains a timer 34, enabling time sensitive events to be handled.
  • a condition container 36 contains instances of conditions 38, which are generally supplied by users of the system.
  • An action container 40 contains instances of actions 42, which are also generally supplied by users.
  • a message is sent. For example, if a customer wishes to obtain goods to supply an order, a request for quotes message can be sent to the appropriate companies, or posted to a central location made available in the exchange. Replies to the message, which will consist of quotations by various suppliers, will be accepted as events by the exchange and handled in a manner designated by the center of the original message. All messages 32 come into the event container 30, and are stored there for further processing.
  • the timer 34 is used to generate events related to the clock or the calendar. If, for example, the customer wants to consider only bids which are submitted within a particular time window, responsive messages are time stamped and compared with timing events generated by the timer 34.
  • condition container 36 Within the condition container 36 are numerous instances of conditions 38 which have been defined by users of the exchange. In the example of a customer putting an order out for bids, conditions regarding receipt of those bids, for example, can be defined as condition instances. Any type of condition desired by the customer can be implemented in the conditions instances. These are implemented as logical relationships between characteristics of the events, such as time, number, and value of various parameters. For example, the customer could want to consider only the first three responsive events, or only responses returned before close of business on the same day as the request, and so forth.
  • the action container 40 contains instances of actions 42 which are to occur in response to conditions being met. Typically, the actions will be to generate additional events. In such case, actions which occur are also returned as events to the event container 30.
  • Breaking the function of the exchange into these three conceptual blocks allows many changes to be made dynamically. For example, changes can be made to conditions without affecting events which have already occurred. Because events are stored in the event container, conditions can be modified as desired by the user without impacting the event container. As is described further below, once a condition, whether original or modified, has been met, the events fulfilling that condition are removed from the event container 30. In a similar manner, actions can be changed independently of events or conditions. When a condition instance is changed, it will be common to change the corresponding action instance. However, these two sets of instances are not tightly tied together, and may be modified independently. Each container utilizes a listener to watch for incoming events.
  • condition container This will typically be interrupt driven, so that something will be done within the container when the listener detects that an event has arrived.
  • the events are stored and catalogued. Additionally, conditional determinations may be made as described below.
  • the condition framework when an event arrives from the event container, the condition framework, or engine, determines which conditions may be affected by the event. There may be more than one such condition. The framework then determines whether any of the potentially affected conditions are satisfied, and if so an event is sent to the action container.
  • receipt of an event by the listener causes the appropriate action or actions to be performed. As described above, some of these actions will be the generation of an event which is returned to the event container, where they are detected by the event listener.
  • FIG 4 is an example illustrating how the exchange functions in a simple instance.
  • a business can automatically accept simple orders within certain parameters, and send a return message to the customer promising fulfillment of the order.
  • orders are to be processed only between 8:00 a.m. and 6:00 p.m.
  • This rule referred to as an Event-Condition-Action (ECA) rule, is set up to deal with a certain specific case.
  • ECA rules would be setup for other ordering conditions.
  • an event framework so is an operational portion of the event container. It contains a listener, which constantly scans for events.
  • the timer 34 generates timing events, 52, 54 which are recognized by the event framework 50.
  • the event framework is aware of the current time. In the present case, incoming events are only to be processed between the hours of 8:00 a.m. and 6:00 p.m.
  • the event framework contains conditions in addition to those contained in the condition container.
  • Conditions in the event container are preferably a small subset of possible conditions, directed to timing and counting of events.
  • a rule within the event framework can provide that a message is sent to the condition container only if an order is received between the timed events of 8:00 a.m. and 6:00 p.m.
  • Another type of condition preferably implemented in the event framework is an event counting condition, such as 'lake an action once three proposals have been received.” Such counting of events is preferably a task performed within the event container. If desired, all of these timing and counting conditions could be implemented in the condition container, but in a large system, the condition container will generally contain many complex conditions set up by system users. Low level decisions, such as time related or count related decisions, can easily be implemented within the event container without adding to the complexity already inherent in the large number of conditions in the condition container.
  • Event2 56 is an order by a customer which has a quantity of 400, and a price of $4,500.
  • the listener of the event framework 50 recognizes the occurrence of Event2, and determines that it occurs between Eventl (8:00 a.m.) and Event3 (6:00 p.m.). It therefore generates an Event2', containing the terms of the order, and sent to the condition container. If, as described above, the time related conditions are instead implemented in the condition container, the just described condition would be processed there.
  • the condition instance 58 in the condition container specifies that this condition is triggered if an order comes in having a quantity less than 500, and a price less than $5000.
  • Event2 is generated.
  • Event2" is an order having the previously noted quantity and price.
  • Event2" is sent to the action instance 60, which defines the actions to be taken when such an order is received.
  • Event4 62 is generated, which is a return promise back to the customer. The customer will presumably provide its own conditions for handling a promise such as Event4, but the message may simply be forwarded by the system to be handled by a person in the usual way.
  • an event when an event occurs that event is remembered within the system until it is used and explicitly removed. In other words, the event persists within the system, and is not lost due to changes and conditions or actions. For example, if a customer wishes to accept ten bids on an order before making a decision, an ECA rule can be set up which reports the bids only after ten are received. If the customer changes his mind at some point, that rule can be modified to generate an action when, for example, only five bids are received. Each incoming message is an event, and changing the condition does not lose any bids already in the system. In other words, each event is held within the event container until the condition container indicates that each of the corresponding events has been used to fulfill a condition and generate an action.
  • Events are preferably defined to expire within some selected time period, such as a few days, so the event container does not become clogged with unused events. Expiration is a time-related condition which operates in the normal manner, to delete messages which have a date stamp older than a desired value.
  • Persistence allows many changes to be made to the system dynamically, without interrupting running of the system. For example, if the customer decides that, in addition to the regular notification, a certain manager is to be notified via pager that the requisite number of bids have been received, an action can simply be added corresponding to the condition instance to send a message to a designated pager. Even if this type of capability is not present on the system initially, once the capability is added action instances may be modified to take advantage of it. This allows the system to grow dynamically in response to user demands and the availability of new technology.
  • petri-nets the internal logic within the condition container and the event container utilizes the concept of "petri-nets". As is known in the art, this is a conceptual framework which allows for generation of actions in response to asynchronous events, and persistence in the manner described above. Simple examples of petri-nets are shown in Figures 6-8, and will be recognized by those familiar with this technology.
  • FIG. 6 a simple petri-net which corresponds to the conjunction of two events generating an action is shown.
  • the first and second event represented by circles70 and 72, correspond to "places" in petri-net terminology.
  • Action event 74 also corresponds to a place.
  • the condition instance 76 corresponds to a transition. In Figure 6, the transition occurs if both the first and second events have occurred, causing the resulting action 74 to be generated.
  • the first two places correspond to events received by the event container, and the resulting place corresponds to an event generated by an action instance.
  • Figure 7 shows a similar petri-net diagram, with the first and second events 78, 80 being combined in a logical or operation. If either event occurs, the resulting action event 82 is generated.
  • Figure 8 shows an event that is a composite of composite events.
  • nets-nets can be logically combined to any level of complexity to define the desired condition.
  • Figure 8 shows a petri-net for (E1 or (E2 and E3)).
  • E4 corresponding to an event generated by an action instance, is generated when either E1 or both of E2 and E3 occur.
  • Manipulation of petri-nets calls for tokens to be placed in various places. When all of the places which provide an input to a transition are filled, these tokens are all removed and tokens are placed in all output places. This corresponds conceptually to the generation of persistent events in the event container, followed by removal of these events and generation of action events as described above.
  • a transition corresponds to a condition instance, and output places correspond to actions.
  • a petri-net separates inputs from outputs, in a manner similar to separation of ECA events into the three separate event, condition and action containers.
  • Figure 9 is a more complex petri-net representing a condition similar to the request for three quotes described above.
  • the customer desires to make a selection only when three separate quotes have been submitted in response to a request.
  • a transition occurs which generates two outputs 82, 84.
  • the first output action 82 is an acknowledgement to all who have submitted quotes that the quotes have been received, and the second output action 84 is submission of the quotes to a selection process. This may be automated, or may be reported to a person to make decision as to which quote is to be accepted. If selection is automated, the selection may be as complex as necessary.
  • the selector action 84 represents activity which may take place out of the exchange, by sending appropriate messages to the company which will be returned when a decision has been made. Once a decision has been made and returned to the exchange, the selector place 84 will be filled by a token, which will initiate the second transition. Outputs from the second transition are, in this example, to enter an order with the company providing the winning quote 86, and to send a notice of non-acceptance to the others 88.
  • this petri-net corresponds to the logic of the exchange controller.
  • Quotes Q1 , Q2, and Q3 correspond to messages sent to the exchange in response to a bid.
  • the condition defined by the customer requires three quotes to be submitted before a decision is made, so that acknowledgement of the submissions and initiation of the selection process, are made only after three quotes are received.
  • counting three quotes is prefably done in the event container, but could be implemented in the condition container if desired.
  • the selection process can be a simple or as complex as desired by the customer, and can be entirely automated or entirely manual.
  • Event-Condition-Action logical control for the exchange can be used to perform quite complex behavior.
  • the system itself is very simple, it simply responds to events which occur. If no events occur, the exchange logic control does nothing. As events occur, however, any number of resulting events may be directly or indirectly generated and fed back through additional condition instances. With minimal effort, the user can describe desired actions to be taken by the exchange, and it will handle many routine tasks associated with message passing through the exchange.
  • the system described above provides an intelligent, dynamically modifiable control system for dealing with messages in a common exchange.
  • Users may define conditions at any time, and receipt of messages (events) triggers actions when various conditions are met.
  • events By separating receipt of messages, conditions, and actions into three separate containers, system flexibility is greatly enhanced. Modifications to conditions, actions, or both may be made any time.
  • the conditions may be expressed as simple text statements, and interpreted at execution time by the condition framework. In this manner, event handling, conditions, and actions are not compiled in as part of the system, but are rather data which are used by the system to perform actions as messages are received. It will be appreciated by those skilled in the art that the described system can grow into a network having great complexity and flexibility.
  • Each message will have an address showing where it is supposed to go, and will be directed to the appropriate system, and therefore the appropriate event container, by this address. This is similar to the manner in which message are currently communicated over the internet based upon addressing information contained in a header of the message.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un système de communication comprenant un système d'échange entre diverses entreprises. Les messages des entreprises sont acheminés par le système d'échange. Ces messages peuvent représenter toutes les données ou fonctionnalités désirées par les entreprises. Ces messages peuvent être des demandes, des quotes, des réponses, ou d'autres messages similaires. Certains types de messages sont désignés comme des évènements pour le système d'échange. Une partie du système d'échange manipule ces évènements selon des règles, générant des actions et des évènements supplémentaires en réponse aux occurrences conformes aux règles.
PCT/US2000/016371 1999-06-14 2000-06-14 Procede de communication par internet WO2000078006A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU57377/00A AU5737700A (en) 1999-06-14 2000-06-14 Internet communications method

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US13902399P 1999-06-14 1999-06-14
US60/139,023 1999-06-14
US09/592,775 US7277863B1 (en) 2000-06-13 2000-06-13 Electronic marketplace communication system
US09/592,775 2000-06-13

Publications (2)

Publication Number Publication Date
WO2000078006A2 true WO2000078006A2 (fr) 2000-12-21
WO2000078006A3 WO2000078006A3 (fr) 2002-05-10

Family

ID=26836796

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/016371 WO2000078006A2 (fr) 1999-06-14 2000-06-14 Procede de communication par internet

Country Status (2)

Country Link
AU (1) AU5737700A (fr)
WO (1) WO2000078006A2 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998029822A1 (fr) * 1996-12-31 1998-07-09 Buildnet, Inc. Systemes et procedes facilitant l'echange d'informations entre des entreprises separees
WO1999007118A1 (fr) * 1997-07-30 1999-02-11 British Telecommunications Public Limited Company Dispositif de communication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998029822A1 (fr) * 1996-12-31 1998-07-09 Buildnet, Inc. Systemes et procedes facilitant l'echange d'informations entre des entreprises separees
WO1999007118A1 (fr) * 1997-07-30 1999-02-11 British Telecommunications Public Limited Company Dispositif de communication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Automatic Processing of Meeting Notices." IBM TECHNICAL DISCLOSURE BULLETIN, vol. 34, no. 9, 1 February 1992 (1992-02-01), pages 48-49, XP002183866 New York, US *
ANONYMOUS: "Technique for Electronic Data Interchange Supplier Simulation" IBM TECHNICAL DISCLOSURE BULLETIN, vol. 40, no. 3, 1 March 1997 (1997-03-01), pages 219-221, XP002183867 New York, US *

Also Published As

Publication number Publication date
WO2000078006A3 (fr) 2002-05-10
AU5737700A (en) 2001-01-02

Similar Documents

Publication Publication Date Title
US8195518B2 (en) Collaborative commerce hub
US5991743A (en) System and method for proactively monitoring risk exposure
US6256667B1 (en) Intelligent messaging
JP3892987B2 (ja) メッセージ・ブローカ・データ処理装置、方法、及び記録媒体
Peng et al. A multi-agent system for enterprise integration
US6230201B1 (en) Configurable transaction routing system and method
US20080162164A1 (en) Method and system for centralized management of sources of supply
AU2002354789B2 (en) Business process policy object
US20030084053A1 (en) System and method for analyzing and utilizing data, by executing complex analytical models in real time
JP2001134677A (ja) 注文処理方法と注文履行処理システム
JP2002099792A (ja) 分散型オンデマンドサービスの提供におけるサービスプロバイダのオンライン選択
WO2007035452A1 (fr) Procede et systeme permettant de construire, traiter et mettre a jour des scenarios dans des systemes d'informations diriges par des evenements
AU2002354789A1 (en) Business process policy object
WO2000072210A9 (fr) Systeme de gestion de pistes de clients eventuels
US7277863B1 (en) Electronic marketplace communication system
US7133913B2 (en) Information routing
US20020116354A1 (en) Method and system for transforming session data
WO2001084349A2 (fr) Negociation multimode dans un environnement réseau
WO2001065382A1 (fr) Procede et systeme de traitement de demandes au moyen de regles dynamiquement chargeables determinees par la classe et le contexte
WO2000078006A2 (fr) Procede de communication par internet
CN116862365A (zh) 出库控制方法、装置与电子设备
US20050114164A1 (en) Method of and system for coordinating events between applications of a customer relationship management system
US8392522B2 (en) Business inquiries and operations using messaging service
EP0992143B1 (fr) Messagerie intelligente
GB2363216A (en) Publish/subscribe data processing with subscriptions based on changing business concepts

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 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 MZ 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)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

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

Ref country code: JP