WO2001050376A2 - Suivi en ligne d'informations d'etat de livraison dans un reseau informatique - Google Patents

Suivi en ligne d'informations d'etat de livraison dans un reseau informatique Download PDF

Info

Publication number
WO2001050376A2
WO2001050376A2 PCT/US2000/033839 US0033839W WO0150376A2 WO 2001050376 A2 WO2001050376 A2 WO 2001050376A2 US 0033839 W US0033839 W US 0033839W WO 0150376 A2 WO0150376 A2 WO 0150376A2
Authority
WO
WIPO (PCT)
Prior art keywords
status information
delivery status
order
carrier
server
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/033839
Other languages
English (en)
Other versions
WO2001050376A3 (fr
Inventor
Rebecca Rhea Guidice
Bruce John Mcdonald
Scott M. Dix
John Andrew Moore
Timothy Lamonte Atwell
Aaron M. Linz
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.)
General Electric Co
Original Assignee
General Electric Co
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/498,464 external-priority patent/US6463420B1/en
Application filed by General Electric Co filed Critical General Electric Co
Priority to AU30743/01A priority Critical patent/AU3074301A/en
Publication of WO2001050376A2 publication Critical patent/WO2001050376A2/fr
Anticipated expiration legal-status Critical
Publication of WO2001050376A3 publication Critical patent/WO2001050376A3/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders

Definitions

  • the present invention relates generally to conducting electronic commercial transactions over a computer network. More particularly, the present invention relates to comprehensive online tracking of shipment information over a computer network.
  • U.S. Patent 5,319,542 to King et al. discloses a system for ordering items from a supplier.
  • the system includes an electronic catalogue and an electronic requisition facility.
  • the catalogue includes a public-access portion, stored on a publicly-accessible database for access by customers, and a private portion, stored on a customer's computer system.
  • the private portion contains unique pricing data based on pricing agreements.
  • Customers use the electronic requisition facility to create purchase requisitions based on the information in the electronic catalogue. The requisitions are routed through an appropriate approval process, processed through the customer's procurement system, and transmitted to the supplier.
  • the present invention overcomes the problems noted above, and provides additional advantages, by providing for a method and system for the online tracking of orders placed with a supplier and shipped by any of a variety of different carriers, entirely within the confines of the supplier's web site.
  • a method in accordance with an exemplary embodiment of the invention is performed by providing for electronic communication of delivery status information between a variety of different carriers and the supplier's server.
  • the method further provides, through a supplier's web site on the World Wide Web, an interface allowing a user to track the delivery status of any submitted order, regardless of the individual carrier shipping the order.
  • Methods, systems and programs in accordance with the present invention greatly increase the efficiency and convenience of tracking the delivery status of orders placed over a computer network.
  • FIG. 1 is a block diagram of a computer network suitable for implementing a method according to the present invention
  • FIG. 2 is a flow chart describing a process for conducting a commercial transaction involving the purchase of an item over the network of FIG. 1;
  • FIG. 3 is a flow chart describing a process for enabling suppliers to track the delivery status of orders placed in the commercial transaction of FIG. 2;
  • FIG. 4 is a flow chart describing a second process for enabling suppliers to track the delivery status of orders placed in the commercial transaction of FIG. 2; and
  • FIG. 5 is a flow chart describing a process for enabling customers to track the delivery status of orders placed in the commercial transaction.
  • FIG. 6 is a flow chart describing a process for enabling authorized carriers to submit delivery status information over the network for subsequent display to cus- tomers.
  • An Internet computer system 10 is generally illustrated in FIG. 1.
  • a conventional client computer system 12, executing a client browser application that supports the HTTP protocol, is connected typically through an Internet Service Provider (ISP) to the Internet 14.
  • ISP Internet Service Provider
  • a server computer system 16 is also coupled typically through an Internet Service Provider to the Internet 14.
  • the server computer system 16 preferably provides local storage for at least one, though typically many Web pages.
  • the client computer system requests a Web page by issuing a URL request through the Internet 14 to the server system 16.
  • a URL consistent with the present invention may be a simple URL of the form:
  • a " protocol_identif ⁇ er" of "http” specifies the conventional hyper-text transfer protocol.
  • a URL request for a secure Internet transaction typically utilizes the secure protocol identifier "https,” assuming that the client browser and Web server are presumed to support and implement the secure sockets layer (SSL).
  • the "server_path” is typically of the form “prefix.domain,” where the prefix is typically “www” to designate a Web server and the "domain” is the standard Internet sub- domain.top-level-domain of the server system 16.
  • the optional "web_page_path” is provided to specifically identify a particular hyper-text page maintained by the Web server.
  • the server system 16 returns the Web page, subject to the HTTP protocol, to the client computer system 12.
  • This Web page typically incorporates both textural and graphical information including embedded hyper-text links that permit the client user to readily select a next URL for issuance to the Internet 14.
  • the URL issued from the client system 12 may also be of a complex form that identifies a common gateway interface (CGI) program on a server system 16.
  • CGI common gateway interface
  • Such a HTML hyperlink reference is typically of the form:
  • a hyper-text link of this form directs the execution of the logon.cgi program on an
  • a logon form supported by a logon CGI program is typically used to obtain a client user login name and password to initiate an authenticated session between the client browser and Web server for purposes of supporting, for example, a secure purchase transaction.
  • FIG. 2 there is illustrated a flow chart describing a method for processing an order for an item over a network (e.g., as shown and described above).
  • This method can be implemented by a software program resident in one or more servers associated with the supplier.
  • This method assumes the use of a so-called “shopping cart” purchase model, in which a user can select any number of desired items, which are then separately stored as a list (or "cart") of desired items; when the user is ready to complete the transaction, the list is recalled and the user can then proceed to purchase the items. It will of course be appreciated that other purchasing models may be used.
  • the customer accesses an order entry web page via the network.
  • step 202 it is determined whether the customer has any orders currently awaiting processing (e.g., in a "shopping cart" or list of desired items which the user has not yet purchased). If it is determined that the user does have orders awaiting processing, the process proceeds in a manner to be described below. If it is determined in step 202 that the user does not have any orders awaiting processing, the process continues in step 204, where the server causes an order entry page to be displayed to the user on the user's computer. In this embodiment, the entry order page presents the user with an option of using a previously entered order template.
  • Such an order template would preferably include information material to the purchase of particular product (e.g., part number, product identification number, product description, quantity, and shipping address) and would increase the speed and simplicity in the event a re-order is required, by eliminating the need for the customer to re-enter this information.
  • information material to the purchase of particular product (e.g., part number, product identification number, product description, quantity, and shipping address) and would increase the speed and simplicity in the event a re-order is required, by eliminating the need for the customer to re-enter this information.
  • step 206 if the user selects an order template, the process proceeds in a manner to be described below. If, on the other hand, the user does not select an order template, the process proceeds to step 208, where the customer enters order information through the interface, and the supplier's server receives this order information. In step 210, the user indicates to the supplier server, via the interface and the network, that the user has finished entering the order information. If the user had selected the use of an order template in step 206, then in step 207 the server causes order informa- tion to be populated from the template, and in step 209, the customer is allowed to modify the order information provided from the template and to enter additional information not provided in the template such as a requested delivery date.
  • step 212 the server determines if all required fields (that is, all information required to process the order) have been entered. If required information is missing, the customer is so informed (e.g., by flagging the fields that require information) in step 215, and the process returns to step 210. If there is no required information missing, the process continues to step 214, where the server examines an inventory database to determine whether the ordered item(s) are presently in inventory, and determines an estimated delivery date for the ordered item(s). In step 216, a list of potential delivery dates or times is determined for the ordered item(s).
  • step 218 the server determines whether an off list price (OLP), or discounted price, is available for the ordered item(s). If such an alternative price exists, the process continues to step 219, where the customer or user is requested to identify the end user of the product on whose behalf the user is purchasing the product. In step 221, whether or not the customer or user can identify an end user for which the product or item is intended determines whether the OLP, or some other price, will be applied. If a specific end user is identified, the process continues to determine a price and/or price bracket as will be described in more detail below. If the purchaser is not ordering the item(s) on behalf of some other end user, the process continues to step 220, where it is determined whether a customer price list (CPL) exists for the ordered item(s). If such a CPL exists, the process jumps to step 228, where a unit price and price breakdown are determined in a manner to be described below.
  • OLP off list price
  • step 220 If such a CPL is determined not to exist in step 220, then the process continues to step 222, where it is determined whether a list price exists. If a list price exists, it is determined whether that list price is equal to a predetermined default value representing an insufficient order quantity (in this example, S99.99) in step 224. If a list price is found not to exist in step 222, or if the list price is found to be a default value, step 226 will cause the customer to be informed that there is no price found for the product, and the process will end. If a list price is found to exist, and the list price is not a default value, or if the customer is purchasing a product on behalf of another user, the process continues to step 228, where a unit price and price bracket are determined.
  • a predetermined default value representing an insufficient order quantity (in this example, S99.99)
  • step 230 the customer is presented with an "shopping cart" page which displays all the information entered (or populated by a template) during the ordering process for each non-submitted order.
  • step 232 the customer submits the shopping cart to the supplier.
  • step 234 the pricing, inventory availability, and delivery date are be calculated, and in step 236, the customer is presented with an order summary.
  • step 2308 it is determined whether an order confirmation number is avail- able for the customer's order. If such a number is available, it is provided to the customer in step 240 (e.g., by automatically causing an electronic mail message to be sent), and if such a number is not available, the order exceptions are resolved in step 240 (e.g., by automatically causing an electronic mail message to be sent), and if such a number is not available, the order exceptions are resolved in step
  • FIG. 1 the network of FIG. 1 and the electronic commerce method of FIG. 2 are merely exemplary models used to illustrate the environment in which the present invention may be used.
  • the present invention may be used with any suitable network or electronic commerce method and should not be limited to those described above.
  • step 300 the supplier establishes communication with all of the carriers authorized to deliver orders.
  • carriers refers to any entity which delivers a product to a customer and may include commercial delivery services, in-house warehouses, and third party vendors.
  • Communication with the carriers may take any suitable form that permits the exchange of tracking information between the carrier and the supplier.
  • EDI electronic data interchange
  • VAN Value Added Network
  • EDI is often referred to as the electronic exchange of information between two business concerns in a specific pre-determined format.
  • the benefits of EDI include the ability to transfer large quantities of information in a short amount of time, without requiring the need for personal contact, physical handling of papers, or re-entry of data.
  • all parties concerned must be capable of sending and receiving information in a standard format regardless of the particular system being used by each party.
  • a second form of communication suitable for use with the present invention is personal contact between the carriers and the supplier. This form of communication facilitates manual entry of information by customer service personnel in circumstances where electronic information cannot be obtained.
  • the supplier's customer service personnel periodically contact the carriers through conventional means (e.g., electronic mail, telephone, etc.) and hand key the information obtained into the system.
  • the carrier may themselves manually enter the information into the supplier's system through a suitable interface described in detail below.
  • step 310 the supplier sources the order from appropriate warehouse(s), out- side vendor(s), or manufacturing facilities for delivery to the customer.
  • the warehouse, vendor, or manufacturer ships the order using any of a variety of authorized carrier services, including their own in house carriers.
  • step 314 the warehouse, vendor, or manufacturer returns a description of all pertinent shipping information (e.g., carrier used, tracking numbers, etc.) associated with a particular order.
  • the supplier in step 316, then periodically
  • the carrier (and automatically) communicates with the appropriate carrier(s) and tracks the delivery status of the relevant order.
  • this communication may take any suitable form including, but not limited to, EDI, seamless web site integration, and personal contact.
  • the carriers return the relevant information to the supplier, which is then stored in a database for future access by the system in step 318.
  • the supplier maintains a complete database of delivery information for all orders placed within a predetermined period of time (e.g., the last 30 days) from all authorized carriers. This information is maintained completely separate from the carrier's own online tracking information and is therefore not subject to disruptions in the carrier's service.
  • step 400 the supplier sources an order from an appropriate ware- house(s), outside vendor(s), or manufacturing facilities for delivery to the customer.
  • the warehouse, vendor, or manufacturer ships the order using any of a variety of authorized carrier services, including their own in house carriers.
  • the warehouse, vendor, or manufacturer returns a description of all pertinent shipping information (e.g., carrier used tracking numbers, etc.) associated with a particular order.
  • the supplier receives a request from an authorized customer to track the delivery status of the order.
  • the supplier in step 416, in response to the request, formulates and transmits an internal request for tracking information from the carrier's web site.
  • the carrier's web site returns the relevant information to the supplier in step 418, which is then displayed to a customer in step 420.
  • the customer By integrating carrier tracking information into the supplier's web site, the customer is not forced to navigate away from the supplier's site and navigate back to continue business with the supplier. In this manner, the supplier provides the most recent delivery status information to customers for all orders placed within a predetermined period of time (e.g., the last 30 days) from all authorized carriers having web tracking capabilities.
  • a predetermined period of time e.g., the last 30 days
  • step 500 the customer accesses a shipment tracking web page via the network.
  • the server determines, in step 510, whether the customer has submitted any orders within a predetermined period of time (e.g., the last 30 days). If not, the server displays a message at step 512 indicating that no recent orders have been submitted. If at least one recent order has been submitted, the server displays a listing of all such orders in step 514. In step 516, the customer is asked to select an order to track.
  • a predetermined period of time e.g., the last 30 days.
  • the server determines whether the carrier has web tracking capabilities on its web site. If the carrier does not have web tracking capabilities, the server, in step 520, references the tracking information database discussed above in FIG. 3 and displays, in step 522, the retrieved delivery status information to the customer. If the carrier does have web tracking capabilities, the server, in step 524, formulates and transmits an internal request for tracking informa- tion from the carrier's web site. In step 526, the server receives tracking information from the carrier's web site and displays, in step 528, the information to the customer. In this manner, the customer is able to track the progress of recent orders regardless of the carrier by which they are being shipped and without the need to navigate off of the supplier's web site.
  • FIG. 6 there is illustrated a flow chart describing a method for enabling authorized carriers to submit delivery status information over a network for subsequent display to customers, in accordance with the present invention.
  • This method may be implemented by a software program resident in one or more servers associated with the supplier.
  • step 600 the server receives a request by the client machine of a carrier representative to access a update shipment status web page.
  • the process continues to step 602 in which the server 14 interacts with the carrier representative client, in a conventional manner, to determine the identity of the particular customer operating the client.
  • One conventional method of determining identity is the logon form briefly described above, although any suitable method for identifying a particular customer user may be utilized (e.g., cookies, etc.).
  • a message is generated in step 604 indicating that the representative must log in to proceed.
  • the server determines in step 606, whether the identified representative is authorized to access shipment tracking information.
  • the server denies access and displays a corresponding message in step 608. If the representative is authorized to view and modify shipment tracking information, the server displays, in step 610, a listing of all undelivered shipments for the individual carrier. Of course, it must be anticipated that carriers may have a large number of such undelivered orders. Therefore, in step 612, the server displays a search request form enabling the carrier representative to search through the list of undelivered orders for a particular order. Although not limited to the following criteria, orders should be searchable through a variety of attributes, such as PRO number, Bill of Lading number, shipment date. In step 614, the server receives a search request for a particular undelivered order.
  • step 616 the server determines whether any results match the requested search. If not, an appropriate message is displayed to the carrier representative, in step 618, and the representative is permitted to re-enter a search request. If results do match the search request, the server, in step 620, displays the resulting orders in sortable fashion, enabling the carrier representative to sort the search results by any searchable attribute.
  • the server receives, in step 622, a request to modify the shipment status for the order. This is typically accomplished via a hyperlink associated with the particular order, but any suitable means may be used.
  • the server displays a form for the entry of shipment tracking information.
  • the form includes at least the following entries: status code (selected from a drop down menu), the date and time of the status information.
  • the form may include provisions for enabling the entry of location information and carrier comments.
  • the server receives a submitted form from the carrier representative and, in step 628, the carrier ascertains whether all of the required information has been submitted.
  • step 630 If the form is deficient in any manner, an error message is displayed in step 630 and the form is re-displayed to the carrier representative for correction. If the form is complete, the server displays, in step 632, an appropriate "modification successful" message and further re-displays the listing of undelivered orders, so that the carrier representative may modify the status of another order.

Landscapes

  • Business, Economics & Management (AREA)
  • Economics (AREA)
  • Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Quality & Reliability (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé et un système de suivi, dans un réseau informatique, d'ordres placés chez un fournisseur et expédiés par un transporteur parmi divers autres transporteurs, le suivi s'effectuant entièrement dans les limites du site Web du fournisseur. En assurant des communications électroniques sous forme d'informations d'état de livraison entre divers transporteurs et le serveur du fournisseur, le fournisseur sera en mesure de fournir des informations de suivi en ligne à un client quelle que soit la manière particulière de livraison.
PCT/US2000/033839 1999-12-30 2000-12-14 Suivi en ligne d'informations d'etat de livraison dans un reseau informatique Ceased WO2001050376A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU30743/01A AU3074301A (en) 1999-12-30 2000-12-14 Online tracking of delivery status information over a computer network

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US17379999P 1999-12-30 1999-12-30
US60/173,799 1999-12-30
US09/498,464 2000-02-04
US09/498,464 US6463420B1 (en) 1999-12-30 2000-02-04 Online tracking of delivery status information over a computer network
US56840200A 2000-05-10 2000-05-10
US09/568,402 2000-05-10

Publications (2)

Publication Number Publication Date
WO2001050376A2 true WO2001050376A2 (fr) 2001-07-12
WO2001050376A3 WO2001050376A3 (fr) 2002-08-01

Family

ID=27390334

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/033839 Ceased WO2001050376A2 (fr) 1999-12-30 2000-12-14 Suivi en ligne d'informations d'etat de livraison dans un reseau informatique

Country Status (2)

Country Link
AU (1) AU3074301A (fr)
WO (1) WO2001050376A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1336928A1 (fr) * 2001-12-31 2003-08-20 Neopost Industrie B.V. Méthode et logiciel pour surveiller le transport des objets dans un système réparti
SG116497A1 (en) * 2002-07-23 2005-11-28 Dell Products Lp Manufacturing optimization and synchronization process.

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4799156A (en) * 1986-10-01 1989-01-17 Strategic Processing Corporation Interactive market management system
US5758327A (en) * 1995-11-01 1998-05-26 Ben D. Gardner Electronic requisition and authorization process
US5971587A (en) * 1997-08-01 1999-10-26 Kato; Kiroku Package and mail delivery system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1336928A1 (fr) * 2001-12-31 2003-08-20 Neopost Industrie B.V. Méthode et logiciel pour surveiller le transport des objets dans un système réparti
SG116497A1 (en) * 2002-07-23 2005-11-28 Dell Products Lp Manufacturing optimization and synchronization process.

Also Published As

Publication number Publication date
AU3074301A (en) 2001-07-16
WO2001050376A3 (fr) 2002-08-01

Similar Documents

Publication Publication Date Title
US6463420B1 (en) Online tracking of delivery status information over a computer network
US7222087B1 (en) Method and system for placing a purchase order via a communications network
US6430540B1 (en) Method and system for monitoring and modifying a consumption forecast over a computer network
EP0927945B1 (fr) Méthode et système pour effectuer une commande par un réseau de communication
US8332282B2 (en) On-line merchandise return labels
US8341036B2 (en) Combining disparate purchases into a single purchase order for billing and shipment
US7475024B1 (en) System and method for distributing in real-time, inventory data acquired from in-store point of sale terminals
US20070118434A1 (en) System and method for transaction automation
US20030004816A1 (en) User-specific method of selling products, computer program product, and system for performing the same
US7366689B2 (en) Method of notifying information about commodity
US20040117263A1 (en) Method, server system and computer program product for user registration and electronic commerce system
US20030212570A1 (en) System and method for inquiring remaining quantity of orders
WO2001050376A2 (fr) Suivi en ligne d'informations d'etat de livraison dans un reseau informatique
US7707094B1 (en) System and method for electronically sourcing products
WO2000072213A1 (fr) Systemes et procedes de commerce electronique
JP2005115451A (ja) ポータルサイトシステム、受注・発注システム及び方法
WO2001057766A2 (fr) Procede d'affichage automatique d'historique des commandes anterieures via un reseau informatique
JP2003263596A (ja) 電子商取引における注文システムおよび注文方法、並びに注文プログラム
JP2003196504A (ja) 小売業向け物流仲介システム
WO2001050374A1 (fr) Procede et systeme de livraison de marchandises a partir d'une commande complexe, sur reseau informatique
JP2005078562A (ja) 注文受付装置、商品引渡装置、注文受付商品引渡システム、それらの方法及びプログラム
JP2002049794A (ja) 商品受発注システム及び商品受発注方法
JP2002288551A (ja) 商品流通管理システム
WO2001050303A2 (fr) Production automatique de requêtes de certificats
WO2001050375A1 (fr) Procede et appareil de suivi en ligne de questions litigieuses pour systeme d'achat

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): 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 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 TR 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): 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 ZW

AL Designated countries for regional patents

Kind code of ref document: A3

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 TR 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

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

Ref country code: JP