WO2003015940A1 - Verfahren zum automatischen erzeugen von aktuellen verteilreihenfolgedaten - Google Patents
Verfahren zum automatischen erzeugen von aktuellen verteilreihenfolgedaten Download PDFInfo
- Publication number
- WO2003015940A1 WO2003015940A1 PCT/DE2002/002852 DE0202852W WO03015940A1 WO 2003015940 A1 WO2003015940 A1 WO 2003015940A1 DE 0202852 W DE0202852 W DE 0202852W WO 03015940 A1 WO03015940 A1 WO 03015940A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- address directory
- data
- distribution order
- distribution
- copied
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000012550 audit Methods 0.000 claims abstract description 44
- 230000008859 change Effects 0.000 claims abstract description 25
- 238000012546 transfer Methods 0.000 claims abstract description 5
- 238000012384 transportation and delivery Methods 0.000 claims description 64
- 230000005540 biological transmission Effects 0.000 claims description 7
- 238000012986 modification Methods 0.000 abstract 4
- 230000004048 modification Effects 0.000 abstract 4
- 230000010076 replication Effects 0.000 description 8
- 230000008676 import Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000012937 correction Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 229940124447 delivery agent Drugs 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000001502 supplementing effect Effects 0.000 description 1
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B07—SEPARATING SOLIDS FROM SOLIDS; SORTING
- B07C—POSTAL SORTING; SORTING INDIVIDUAL ARTICLES, OR BULK MATERIAL FIT TO BE SORTED PIECE-MEAL, e.g. BY PICKING
- B07C3/00—Sorting according to destination
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B07—SEPARATING SOLIDS FROM SOLIDS; SORTING
- B07C—POSTAL SORTING; SORTING INDIVIDUAL ARTICLES, OR BULK MATERIAL FIT TO BE SORTED PIECE-MEAL, e.g. BY PICKING
- B07C1/00—Measures preceding sorting according to destination
Definitions
- the invention relates to a method for the automatic generation of current distribution order data, including central address directories stored in databases and transmitted by data transmission as distribution order data.
- Modern postal organizations have a central electronic address directory (ZAV) in which all addresses to be delivered (delivery points) are recorded.
- the address directory (ZAV) is the information basis for several postal applications and is updated regularly, e.g. per month. Changes are typically made based on requests from users of the ZAV-dependent postal applications, e.g. Post deliverer, carried out.
- the ZAV data are often structured hierarchically: delivery districts, delivery sections (groups of delivery points) and delivery points.
- sorting plans are prepared in which the order of the mail items is specified and which are loaded by the distribution order sorting systems.
- the VFM must also store quality of service (QoS) features such as, for example, "only carry out on Tuesdays" with the address data. These QoS features are evaluated by the VFM in order to keep the sorting plans up to date on a daily basis.
- QoS quality of service
- the ZAV either contains no or only imprecise sequence information in order to specify the distribution order.
- the delivery order required by the delivery agents can also change for other reasons, e.g. Representation of illness, change daily. These changes must be immediately feasible in order not to impair the efficiency of the distribution order sorting. For this reason and to make the QoS information maintainable on site, the VFM systems are preferably installed on separate computers on site at the sorting systems.
- Each VFM is therefore usually responsible for a separate postal area and its database does not have to be compared with that of the other VFMs. According to this architecture, however, new versions of the ZAV must be replicated to several VFMs and integrated there with local changes in the previous version. This replication would be easy to implement if the ZAV system made a log file of the changes available (as usual for merge replication between database systems (Microsoft SQL Server 2000 Reference Library (ISBN 0-7356-1280-3) )) or if the VFM system would not allow changes to the data (read- only snapshots (Buretta, Marie “Data Replication: Tools and Techniques for Managing Distributed Information", (ISBN 0- 471-15754-6))). If the VFM had been implemented with an industry standard DBMS (Database Management System) and replication service, the missing change history could be
- Compensate (log file).
- the VFM should be operable from several end devices, which together with the number of distributed VFM computers can mean considerable license costs for a DBMS.
- the ZAV data should also serve as a master version, the distribution order data as a replica
- the invention has for its object to provide a simple method for the automatic generation of current distribution order data with the replication of ZAV databases and with local changes without a database management system.
- the invention is also intended to integrate centrally maintained quality of service features, e.g. Forwarding requests, the simple integration of changes made in parallel as well as the addition and correction of an existing address directory by incremental changes.
- the new database is simply imported by the VFM as a new version of the distribution order data.
- the change commands saved in the audit file of the previous version can then be automatically applied to the new version by an editor program.
- the changes are also written to the initially empty audit file of the new version and thus passed on from version to version.
- context information from the identification data is provided in the audit file in order to enable a semantic check of the validity of the audit file entries during their use. This means that only the changes that are still valid are transferred from one version to the next. It is also an important basis of this procedure that the audit entries are designed in such a way that they not only enable the data changes to be transferred easily, but also allow the change instructions to be checked at the same time.
- Every time a new version of the ZAV data is replicated, a new version of the distribution order data is created on each VFM. Each VFM only processes the ZAV data for its area of responsibility, which means a distribution and parallelization of the work. Complicated merging of the ZAV and distribution order databases is not necessary with this master / slave procedure. By creating a new version of the distribution order data, the old data stock will automatically still be available for backup.
- the sorting plans for the sorting systems only one, the current, version of the distribution order data is used.
- multiple operators can make changes to the same version of the distribution order data at the same time.
- the content of his audit file is automatically applied to the current database as described above. As a result, his changes are only valid. If there are changes that cannot be made due to changes made by another operator, the operator can be informed and then edit the changed distribution order data again.
- the structure of the audit file allows an audit file to be created based on changes to a version of the distribution order data, and then applied to a version of the distribution order data that has since been changed.
- the identification data also contain house number extensions.
- identification data also contain characteristic comments, for example “none Delivery on Tuesday “or” Delivery from a certain date to a new address ".
- the new forwarding and / or distribution information is inserted into the copied address directory, new information replaces the old information of the same type, and the complete change data for the forwarding and / or distribution information is transferred to the audit file.
- only incremental changes are transmitted via data transmission in order to update the central address directory or parts of the central address directory.
- These incremental changes are merged with the copied, up-to-date address directory or part of the address directory, by using the identification data at each delivery time in the previously current address directory or part of the address directory to check whether the respective delivery point of the incremental change already exists. If this is not the case, it is included in the copied address directory or part of the address directory in the position of the distribution order that was transmitted. If the delivery point already exists in the incremental change in the address directory or part of the address directory, it will be moved to the changed position in the address directory.
- the moving process is advantageously carried out by deleting the delivery point at the previous position in the address directory and re-entering it at the changed position.
- Sorting systems 2 shows a flowchart for correcting / supplementing the
- Feature file shows a flowchart of the import of an audit file.
- a distribution order manager is supplied with at least the central address directory (ZAV) data relevant to its postal area in files by data transmission.
- ZAV central address directory
- 1 shows the systems required for processing the address data and for the distribution order sorting by a postal organization.
- the VFM 100 receives the ZAV data from the system 101, on which the ZAV data are maintained, and uses them to prepare the sorting plans for the distribution order sorting systems 104 by means of a generator program 106. If necessary, there is a second application system 102, which also accesses the ZAV data, on which forwarding requests are managed. Other application systems that manage further information useful for the distribution order sorting are also possible.
- the forwarding data is also transmitted to the VFM via data transmission, e.g. ftp, delivered.
- the complete ZAV data are completely adopted by the VFM and stored locally as distribution order data on a hard disk 103. Every time there is a new version of the ZAV data, a new version of the copied local distribution order data is created. In this way, the ZAV data is replicated in master / slave mode.
- QoS Quality of service
- the operator can also correct or supplement the distribution order data with an editor program 105 in order to take account of changes in the street scene, for example new houses that are not yet known in the ZAV system, in the distribution order sorting.
- 2 shows as a flowchart the maintenance of the distribution order data by an operator with an editor 105.
- the version of the distribution order data to be processed is read 201 from the hard disk.
- the editor then reacts to user inputs which make changes to the data 202.
- Changes to the address data can be carried out at different levels of the hierarchy in order to move 203, delete 204 or add 205 one or more delivery districts, one or more delivery sections or single / several delivery points. These operations change the data and are simultaneously used as audit entries of the types MOVE 207, DELETE 208 and ADD 209 logged. Should the operator add, delete or move QoS features for a delivery point / section / district 206, all changes are logged 210 in the audit file with a SET features entry. If the operator wants to save the changed data after editing 211, the distribution order data will be saved and the new audit entries added at the end of the audit file 212.
- the affected delivery point, section or district is specified as a parameter in the entry.
- District ID Section ID, Section Name
- for delivery areas District ID, district name.
- the position in the distribution order at which the delivery point / section / district is to be inserted is also identified. Instead of a position number, the corresponding position is noted based on the before / after delivery points / sections / districts.
- a MOVE entry also receives before / after delivery points / sections / districts as parameters. Because a MOVE entry can move more than one delivery point / section / district at the same time as a contiguous area, the area with the first and last delivery point / section / district is specified.
- QoS features are entered with the editor and saved as SET audit entries.
- An essential part of an audit file consists of SET characteristics instructions. Because each delivery point / section / district generally only has a few QoS features, the evaluation of the audit file is kept simple by always specifying all the features available for a delivery point / section / district in each SET entry. This means that only the last SET entry for each delivery point / section / district needs to be evaluated.
- superfluous SET entries can simply be ignored, which compresses the audit file after being saved again. Reading in a new complete version of the ZAV data and creating a new version of the distribution order data begins, as shown in FIG. 3, with the transmission of the new ZAV data to 400.
- a syntactical check of the ZAV data for correctness and completeness backing up the records is first done 401. To transfer local changes that have been made to the new version of the data, it is necessary that the records can be identified from one version to the next. Districts and sections are defined in the ZAV data only as a set of delivery point records, and are generated in the distribution order data as required. In order to identify delivery point data records, identification data are formed from the sort code + house number extension + remark of a delivery point.
- the sort code represents the goal of the sorting and is often printed as a barcode on mail items in automated letter distribution. The sort code does not have to consist of the postcode, street name and house number. However, the method becomes more effective if clear abstract sort codes are used.
- the entries of an existing audit file for example from the previously current version of the data, can be applied 403 to the new data in order to transfer all local changes.
- Each entry must first be checked for validity 404. The entry is no longer valid, for example if the delivery point to be moved already is in the right place. All valid entries are applied 405 by the editor program.
- audit entries are created for the new version of the distribution order data. These audit entries of the new version are saved 406. All audit entries that are no longer valid are saved 407 in a log file and can be viewed by the operator as required. After all audit entries have been processed 408, the new version of the distribution order data can be saved 409 with a generally smaller audit file.
- each database is combined with the current version of the distribution order data to form a new full version of the distribution order data.
- the current version of the distribution order data is first read 500 from the hard disk.
- a hash table is typically built 501 in the memory according to the usual programming technique in order to enable the delivery points to be found quickly afterwards.
- the identification data already mentioned which is formed from the sort code + house number extension + remark of a delivery point, serves as the key in the hash table.
- some ZAV databases do not have any sort codes, in this case the correct sort code is generated during the import.
- All new delivery points are processed 502 one after the other.
- the first step is to check whether the delivery point already exists 503. If the new delivery point already exists, its relative position is compared 504 with the previous relative position. If the positions are the same, no further action is necessary. If the positions are different, the delivery point is entered 505 in a list of delivery points that are to be deleted. These delivery points to be moved are also entered 506 like new delivery points in a list of the new delivery points. position points were edited 507, all delivery points to be deleted are removed 508. All new or moved delivery points are then added 509. Finally, the new version of the distribution order data can be saved 510. Empty sections and empty districts are omitted.
- the QoS features from another central application system are provided as a file.
- a characteristics file can be combined with the current version of the distribution order data to form a new version.
- the current version of the distribution order data is first read 600 from the hard disk.
- a hash table is built up 601 in memory according to the usual programming technique as already described above. All features in the file are processed 602 one after the other, whereby first it is checked whether the delivery point concerned exists at all 603. If the delivery point exists, the previous characteristics are combined with the new characteristics, the new characteristics having priority 605.
- the supplemented data record is stored in the distribution order data and as a complete SET entry in the audit file is saved 606. If the delivery point concerned is not available, an entry is logged in an error file 604. After all delivery points have been processed 607, the new version of the distribution order data is saved.
- the current version of the distribution order data is first read 700 from the hard disk.
- a hash table is constructed 701 in the memory according to the usual programming technique as described above. All audit entries from the audit file are processed 702, and first it is checked whether each entry is still 703 is valid. If an entry cannot be applied, for example because the delivery point is missing, the entry is saved 706 in the audit log file. If the entry can nevertheless be used, the change is made 704 and a new entry is made in the new audit file is saved 705. After all audit entries have been processed, the new version of the distribution order data is saved 708.
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Circuits Of Receivers In General (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2002320933A AU2002320933B2 (en) | 2001-08-09 | 2002-08-02 | Method for automatically producing actual distributed data sequences |
DE50204696T DE50204696D1 (de) | 2001-08-09 | 2002-08-02 | Verfahren zum automatischen erzeugen von aktuellen verteilreihenfolgedaten |
EP02754489A EP1414591B1 (de) | 2001-08-09 | 2002-08-02 | Verfahren zum automatischen erzeugen von aktuellen verteilreihenfolgedaten |
NO20031596A NO325251B1 (no) | 2001-08-09 | 2003-04-08 | Fremgangsmate for automatisk tilvirkning av aktuelle fordelingsrekkefolgedata |
US10/763,216 US20040153470A1 (en) | 2001-08-09 | 2004-01-26 | Method for automatically generating current distribution order data |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10139249.4 | 2001-08-09 | ||
DE10139249A DE10139249A1 (de) | 2001-08-09 | 2001-08-09 | Verfahren zum automatischen Erzeugen von aktuellen Verteilreihenfolgedaten |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/763,216 Continuation US20040153470A1 (en) | 2001-08-09 | 2004-01-26 | Method for automatically generating current distribution order data |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003015940A1 true WO2003015940A1 (de) | 2003-02-27 |
Family
ID=7694979
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/DE2002/002852 WO2003015940A1 (de) | 2001-08-09 | 2002-08-02 | Verfahren zum automatischen erzeugen von aktuellen verteilreihenfolgedaten |
Country Status (6)
Country | Link |
---|---|
US (1) | US20040153470A1 (de) |
EP (1) | EP1414591B1 (de) |
AU (1) | AU2002320933B2 (de) |
DE (2) | DE10139249A1 (de) |
NO (1) | NO325251B1 (de) |
WO (1) | WO2003015940A1 (de) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007022880A1 (de) * | 2005-08-26 | 2007-03-01 | Siemens Aktiengesellschaft | Verfahren zur identifizierung von zu sortierenden sendungen |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1804217B1 (de) * | 2005-12-05 | 2015-04-29 | Deutsche Post AG | Verfahren und Vorrichtung zum Verarbeiten von für die Sortierung von Postsendungen relevanten Daten |
US20160373405A1 (en) * | 2015-06-16 | 2016-12-22 | Amazon Technologies, Inc. | Managing dynamic ip address assignments |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999006914A2 (en) * | 1997-07-29 | 1999-02-11 | Acxiom Corporation | Method and system for the update of remote data using persistent keys |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5422821B1 (en) * | 1992-04-06 | 1998-07-21 | Electrocom Automation Lp | Apparatus for intercepting and forwarding incorrectly addressed postal mail |
US5454038A (en) * | 1993-12-06 | 1995-09-26 | Pitney Bowes Inc. | Electronic data interchange postage evidencing system |
JP3441249B2 (ja) * | 1995-07-24 | 2003-08-25 | 株式会社東芝 | コーディングシステム及び郵便物処理システム |
US6067525A (en) * | 1995-10-30 | 2000-05-23 | Clear With Computers | Integrated computerized sales force automation system |
US7236970B1 (en) * | 1999-10-19 | 2007-06-26 | Stamps.Com | Address matching system and method |
US6557000B1 (en) * | 1999-11-30 | 2003-04-29 | Pitney Bowes Inc. | Method of updating an addressee database in a mail sorting apparatus |
US6954729B2 (en) * | 2000-01-27 | 2005-10-11 | Bowe Bell & Howell Postal Systems Company | Address learning system and method for using same |
JP2001256386A (ja) * | 2000-03-08 | 2001-09-21 | Sony Corp | 流通管理装置、流通管理方法、プログラム格納媒体及び流通管理システム |
US6762384B1 (en) * | 2000-09-25 | 2004-07-13 | Siemens Aktiengesellschaft | Method of presorting mail for minimized effort to sequence mail for delivery |
US20030046103A1 (en) * | 2001-05-16 | 2003-03-06 | Michael Amato | Dynamic change of address notification |
-
2001
- 2001-08-09 DE DE10139249A patent/DE10139249A1/de not_active Ceased
-
2002
- 2002-08-02 EP EP02754489A patent/EP1414591B1/de not_active Expired - Fee Related
- 2002-08-02 WO PCT/DE2002/002852 patent/WO2003015940A1/de active IP Right Grant
- 2002-08-02 DE DE50204696T patent/DE50204696D1/de not_active Expired - Lifetime
- 2002-08-02 AU AU2002320933A patent/AU2002320933B2/en not_active Ceased
-
2003
- 2003-04-08 NO NO20031596A patent/NO325251B1/no not_active IP Right Cessation
-
2004
- 2004-01-26 US US10/763,216 patent/US20040153470A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999006914A2 (en) * | 1997-07-29 | 1999-02-11 | Acxiom Corporation | Method and system for the update of remote data using persistent keys |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007022880A1 (de) * | 2005-08-26 | 2007-03-01 | Siemens Aktiengesellschaft | Verfahren zur identifizierung von zu sortierenden sendungen |
Also Published As
Publication number | Publication date |
---|---|
DE50204696D1 (de) | 2005-12-01 |
EP1414591A1 (de) | 2004-05-06 |
NO20031596L (no) | 2003-04-08 |
NO325251B1 (no) | 2008-03-10 |
US20040153470A1 (en) | 2004-08-05 |
NO20031596D0 (no) | 2003-04-08 |
EP1414591B1 (de) | 2005-10-26 |
DE10139249A1 (de) | 2003-03-06 |
AU2002320933B2 (en) | 2006-12-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1151399B1 (de) | Integration heterogener Datenbank-Systeme | |
EP1258812B1 (de) | Virtuelle Datenbank heterogener Datenstrukturen | |
DE10311082B4 (de) | Elektronikdokumentmanagementverfahren | |
DE60224030T2 (de) | Verwaltungs- und synchronisierungsapplikation für netzwerkdateisystem | |
DE60306674T2 (de) | Verfahren und systeme zur regelung des zugriffs auf ein datenobjekt mittels sperren | |
DE19844013A1 (de) | Strukturierter Arbeitsordner | |
DE19607149A1 (de) | Verfahren zum rechnergestützten Abgleich mehrerer, in mindestens einem Rechner gespeicherten Dateikopien einer gespeicherten Datei | |
DE19844071A1 (de) | Verfahren zum Lösen von Datenkonflikten in einem gemeinsamen Datenumfeld | |
DE60004211T2 (de) | Entfernung von duplizierten objekten aus einem objektspeicher | |
WO2008025719A1 (de) | Verfahren zur erzeugung eines grössenoptimierten delta-files | |
EP1414591B1 (de) | Verfahren zum automatischen erzeugen von aktuellen verteilreihenfolgedaten | |
DE102016005519B4 (de) | Verfahren zur Erstellung eines Metadaten-Datenmodells für eine BI-Infrastruktur | |
EP1605368B1 (de) | Erstellen elektronisch verarbeitbarer Unterschriftendateien | |
DE10346802B4 (de) | Verfahren zur Bearbeitung von CDR-Informationen | |
DE19607132B4 (de) | Verfahren zum rechnergestützten Abgleich mehrerer, in mindestens einem Rechner gespeicherten Dateikopien einer gespeicherten Datei | |
DE60315030T2 (de) | Vermeiden von datenverlusten beim aktualisieren eines data warehouse | |
DE19851727B4 (de) | Verfahren und Vorrichtung zum automatischen Integrieren von externen Archivsystemen auf einem Zentralarchivsystem | |
WO2000007116A1 (de) | Verfahren, anordnung und satz mehrerer anordnungen zur behebung mindestens einer inkonsistenz in einer datenbankmenge, die eine datenbank sowie mindestens eine kopiedatenbank der datenbank aufweist | |
DE19911373A1 (de) | Einrichtung und Verfahren zum Betrieb von Geschäftsprozessen in einem verteilten Informationsnetz | |
EP0791889A2 (de) | Verfahren zum rechnergestützten Abgleich mehrerer, in mindestens einem Rechner gespeicherten Dateikopien einer gespeicherten Datei | |
EP1593036A2 (de) | Verfahren und vorrichtung zum modifizieren von modular aufgebauten nachrichten | |
DE19607134A1 (de) | Verfahren zur rechnergestützten Verwaltung mehrerer, in mindestens einem Rechner gespeicherten Dateikopien einer gespeicherten Datei | |
WO2005088497A2 (de) | Datenverarbeitungseinrichtung, datenstruktur und verfahren für die auslieferung von finanzinformationen für eine finanzinformationsdatenbank | |
EP3324321A1 (de) | Verfahren zum ermitteln einer bei einem rechteverwerter anzugebenden dateneinheit bezüglich eines musikstücks, computerprogrammprodukt, rechnereinrichtung und netzwerk | |
DE10203775A1 (de) | Verfahren und Systemkonfiguration zum Verarbeiten von Daten eines Online-Systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AU NO US Kind code of ref document: A1 Designated state(s): AU NO |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FR GB GR IE IT LU MC NL PT SE SK TR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2002754489 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002320933 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10763216 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2002754489 Country of ref document: EP |
|
WWG | Wipo information: grant in national office |
Ref document number: 2002754489 Country of ref document: EP |