WO2002071281A1 - Data exchange between insurer and repairer - Google Patents
Data exchange between insurer and repairer Download PDFInfo
- Publication number
- WO2002071281A1 WO2002071281A1 PCT/AU2002/000176 AU0200176W WO02071281A1 WO 2002071281 A1 WO2002071281 A1 WO 2002071281A1 AU 0200176 W AU0200176 W AU 0200176W WO 02071281 A1 WO02071281 A1 WO 02071281A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- varchar2
- cde
- null
- quotesummary
- data
- Prior art date
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Definitions
- This invention concerns a data exchange, and in particular a computer system for exchanging data between an insurer and a repairer, for instance between software applications of a vehicle insurer and a crash repairer.
- the invention also concerns the structure of a database in which the messages are stored. In a further aspect it concerns a method of exchanging the data.
- the invention is a computer system for exchanging data between a software application of an insurer and a repairer, comprising
- a message transceiving station to send messages to and receive messages from the repairer.
- the messages being one of a closed set in the form of data wrapped in syntax to allow them to be mapped into a complex database structure which obeys relationship constraints and has referential integrity.
- the incoming messages are usually zipped.
- a message receiver to unpack received messages to retrieve their data content.
- a message data content parser to parse the data content and write it to tables organised in a predetermined schema in a first database that does not have the relationship constraints and referential integrity.
- a data collector to extract the data from the first database, validate it and store it in tables organised in the predetermined schema in a second database that does have the relationship constraints and referential integrity.
- An applications server may subsequently transfer data between the second database and applications software for processing.
- the data collector may operate to retrieve data from the database at set time intervals, such as once a minute.
- an outgoing message is usually produced, marked up in XML format and written to the repairer's mailbox so that the repairer can receive it.
- the outgoing messages are generally not zipped.
- Monitoring software may run continuously to check for errors in the validation done by the data collector.
- the monitoring software may display any error and probable resolution. It has a connected knowledge base that is dynamic and allowed to grow and record resolutions to new errors as they are detected for the first time.
- the monitoring software may also raise an alarm when a record has not been collected within a specified time, for example ten minutes, so that support staff may intervene.
- the monitor software program is scalable to include the use of technologies such as paging, short message service (SMS), wireless application protocol (WAP) or auto e-mail.
- the system can effectively and efficiently communicate quote information because it takes advantage of an efficiently built database structure, intelligent message transportation and a high level of quality control of the data through error checking and correction procedures.
- the implementation of a data exchange between repairers and assessors via the Internet allows for quicker response times, and allows for a paperless process for detailed quote information transmission.
- the reduction in intermediary staff between repairers and assessors also reduces the risk of human error when using this data exchange mechanism.
- This mechanism as envisaged would direct and manage the communication process to the most appropriate assessor, thus allowing the most optimum method in handling particular claims. From the repairer and customer's perspective the repair process would be transparent, and the complex processes of validation, approval and other associated checking and data extraction of the repairing process would be done typically on the transmission of the first message by the repairer to the assessor.
- the invention also concerns the database which has been constructed to accept all relevant information concerning the insurance claims process between repairers and assessors, and keeps the relevant information stored in tables, where a list of tables is given below:
- the User Defined tables contain information belonging to the sender that is guaranteed to be returned unchanged. This enables the sender to funnel multiple categories of information into a single category for the recipients benefit but allows the dissemination of this information back into the senders categories on return.
- the key relationships between the core set of tables for the passing of information are:
- the primary key of a RequestForQuote is a foreign key of the QuoteSummary table.
- the QuoteSummary table has a primary key of the Repairer Id, the Quote Number generated by the Repairers Quotation Software package plus a blind key to allow multiple occurrences of QuoteSummary records and the keeping of quotation history.
- the QuoteNote table has a blind primary key but contains the foreign keys of the RequestForQuote and QuoteSummary that it pertains to.
- the Claim Vehicle table primary key is comprised of the Claim Number and Vehicle Registration Number which form part of the primary key of the Request for Quote.
- the invention is a method for exchanging data between an insurer application software and a repairer, comprising the steps of:
- Unpacking the received message to retrieve its data content Parsing the data content and writing it to tables organised in a predetermined schema in a first database that does not have the relationship constraints and referential integrity.
- Fig. 1 is a block diagram of the network topology and hardware.
- Fig. 2 is a message flow diagram of the message transportation.
- the diagram can be divided into three distinct groups.
- the first group is the repairers 10, the second is the Internet 11 and the third is the assessor's system ("the system") 12.
- the system 12 is protected by a firewall 20 and comprises of three servers.
- the Websuite server 21 is connected to the Gentran server 22 that in turn is connected to the Forte App server 23.
- the system 12 uses two Oracle databases, the Gentran database 24 that is connected to the Gentran server 22 and the ORM/Forte database 25 that is connected to the Forte applications server 23.
- the Assessing Centre 26 connects to the Forte App server 23 to serve data out to individual assessors 27.
- Messages 28 are transmitted between the repairers 10 and the system 12 via the Internet 11 in the form of data wrapped in XML syntax and zipped using a known protocol such as HTTP or FTP. These messages pass through the firewall 20 to and from the websuite server 21.
- the XML once it has been unpacked is passed 14 to the Gentran server 22.
- the XML is parsed and sent 15 through ODBC to the Gentran oracle database 24.
- the Forte applications server 23 runs a program called Forte Collector to transfer data 16 between the Gentran database 24 and the ORM/Forte database 25.
- the system 12 belongs to an insurer and communicates over the Internet 11 with repairers 10.
- the repairer 10 prepares a message 13 and transmits it to a mailbox 30 on the websuite server 21.
- the message 13 comprises Data fields wrapped into an XML syntax which allows the specification of data type, length, valid values, grouping, nesting of elements of data and the assignment of mandatory/optional attributes. Because the reference data sets may be different at the repairer and insurers computer systems, the data is denormalised into specific tags or a series of valid values are specified for a given element. As a result the apparently flat messages include intelligence to allow them to be mapped into a complex database structure which obeys relationship constraints and referential integrity.
- the Gentran server 22 duplicates the message and sends the duplicate to an application inbox where it is enacted upon by a delivery rule.
- the delivery rule assumes that the message is a zip file and initiates an Unzipper software 31 program to load, passing the name of the zip file as a parameter.
- the unzipper software program ensures validity of the zip file, and that the XML file extracted from the zip file is valid and parses correctly.
- the unzipper is not responsible for validation of the data types or lengths of fields. However, the unzipper extracts any images 33 that may be in the zip file.
- the XML file unzips correctly it is checked, by checking a message log 35, to verify that it is not a duplicate of an earlier message. Provided it is not a duplicate, a message is written to the message log 35 detailing that the message has been received. The XML file is then taken 14 by the Gentran server and parsed 32.
- the zip file contains any images 33, they are written to a single directory on the local DASD 36.
- the images are subsequently moved 37 from the NT DASD to a tower Unix server 38 where they are stored with index files.
- the unzipper will write a message 39 to an error table 40.
- An entry in the error table 40 causes an outbound XML error message to be prepared and placed in the outbound mailbox of the relevant repairer for transmission 41 back to the repairer. It is the repairer's responsibility to rectify any error.
- Gentran system If there is a validation problem during parsing the Gentran system writes an error message to one of its internal tables. The problem is then either actioned automatically or user intervention is sought.
- the Gentran system After parsing is complete the Gentran system attempts to write the data into a set of tables 34 that are organised in a predetermined schema. These are tables in a Gentran Oracle database which has no relationship constraints or referential integrity. As a result all messages that will parse are stored.
- the assessing centre 26 retrieves data from the Gentran system using collector software 43.
- the collector 43 extracts the data from each of the incoming message tables, validates it and creates new records 44 within the ORME/Forte database 25. This database includes relationship constraints and referential integrity so the validation includes examination for error conditions including referential integrity.
- the collector software 43 runs at a set time interval, currently once a minute.
- the ORM Forte server 23 uses applications software 45 to action the incoming messages, either automatically or using the assessing centre 26. As a result of actioning incoming messages an outgoing message 46 is usually produced, marked up in XML format and written to the repairer's mailbox 30 so that the repairer can receive it 47. These outgoing messages are not zipped.
- a monitor software program 42 (which could be located on either a client machine or server depending on the support structure of the business group, supporting this system) is run continuously to check the errors arising in the validation being performed by the collector software 43.
- the program 42 also displays any system error and probable resolution. It has a connected knowledge base that is dynamic and allowed to grow and records/catalogues methods of resolutions to new errors detected.
- monitor software program 42 Another function of the monitor software program 42 is to verify that the collector 43 is running at all times.
- the monitoring software 42 will raise an alarm when a record has not been collected within a specified time, for example ten minutes, so that support staff may intervene.
- the method by which the monitor software program's alarm is raised is through the comparison of the time stamp in the message log 35 to the time stamp in the Gentran tables 34 held by the Gentran database 24. If the difference between the two times is greater than a specified period, say 10 minutes, the alarm is raised.
- the monitor software program 42 is scalable to include the use of technologies such as paging, short message service (SMS), wireless application protocol (WAP) or auto e-email.
- SMS short message service
- WAP wireless application protocol
- auto e-email auto e-email
- the insurer transmits a "Request for Quote” message to the repairer 10 with insurance information on the property, the property details for example, make, model, engine number, and the customer's contact details.
- the repairers 10 After receipt of a "Request for Quote” message, the repairers 10 in response, transmit their "Quotation” message containing an extensible mark-up language (XML) file and images, zipped into a single file via the Internet 11 to reach the system 12.
- XML extensible mark-up language
- an incoming message from a repairer could be one of the following:
- AMTJREMOVEREPLACE NUMBER (10,2) NOT NULL AMT_REPAIR NUMBER (10,2) NOT NULL
- AM ⁇ _PA ⁇ NT NUMBER (10,2) NOT NULL
- NAM_CUSTOMERNAME VARCHAR2 (200), TXT_CUSTOMERHOMEPHONE VARCHAR2 (20), TXT_CUST0MERBUS1NESSPH0NE VARCHAR2 (20), FLG_AUTHORISEDINDICATOR CHAR (1), CDEJOBCATEGORY VARCHAR2 (20), FLG_HIRECAR ⁇ NDICATOR CHAR (1), PPJMARY KEY ( NUM_CCISAUD ⁇ D )
- TXT_EQUTPMENTLEVEL VARCHAR2 (10), CDE_TRANSMISSIONTYPE VARCHAR2 (20) NOT NULL, CDE_TRANSMISSIONCODE VARCHAR2 (20) NOT NULL, CDE_MODEL VARCHAR2 (20),
- TXT_DESCRTPTION VARCHAR2 (30) NOT NULL
- TXT_SHORTDESCRIPTION VARCHAR2 (15) NOT NULL
- TXT_APPLICATIONID VARCHAR2 (lOO) NOT NULL
- TXTJPKTIME VARCHAR2 (21) NOT NULL
- TXT_DATATYPEDESCRIPTION VARCHAR2 (4000), TXT_DATATYPEELEMENTNAME VARCHAR2 (4000), TXT_DATATYPEVALUE VARCHAR2 (4000),
- TXT_DATACONTENTDESCRIPTION VARCHAR2 (4000), TXT_DATACONTENTELEMENTNAME VARCHAR2 (4000), TXT_DATACONTENTVALUE VARCHAR2 (4000), TXT_MESSAGEORDERDESCRIPTION VARCHAR2 (4000), NUM_MESSAGEORDEREXPECTEDNO NUMBER (3), NUM_MESSAGEORDERRECEIVEDNO NUMBER (3), TXT_MESSAGETYPEDESCRIPTION VARCHAR2 (4000), TXT_DTDVERSIONDESCRIPTION VARCHAR2 (4000), TXT_DTDVERSI0NRECEIVEDVER VARCHAR2 (4000), TXT_MISCELLANEOUSDESCR]PTION VARCHAR2 (4000), TXT_DTDVERSION VARCHAR2 (4000),
- TXT_TIMESTAMP_N_INBOUND VARCHAR2 (4000)
- TXT_TIMESTAMP_Y_INBOUND VARCHAR2 (4000)
- TXT_DESCRIPTION VARCHAR2 (100) NOT NULL, AMT_GSTRATE NUMBER (10,2) NOT NULL, AMTJNVOICE NUMBER (10,2) NOT NULL, CDE_LNVOICESTATUSTYPE VARCHAR2 (20), CDEJNVOICESTATUSCODE VARCHAR2 (20), DTE_TRANSACTIONDATE DATE, TXT_TAXL ⁇ ERAL VARCHAR2 (30), NUM_TOTALEXCLUDINGGST NUMBER (10,2),
- TXT DESCRLPTION VARCHAR2 (30) NOT NULL, NUM_DAYS NUMBER (38), AMT_HOURS NUMBER (10,2), PRIMARY KEY ( CDE_PERIOD )
- TXT PASSWORD VARCHAR2 (30) NOT NULL, NAM_BONUSID VARCHAR2 (30), TXT_BONUSPASSWORD VARCHAR2 (30), NAM_TOWERTD VARCHAR2 (30), TXT TOWERPASSWORD VARCHAR2 (30),
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- General Engineering & Computer Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2002231471A AU2002231471B2 (en) | 2001-03-01 | 2002-02-20 | Data exchange between insurer and repairer |
NZ527509A NZ527509A (en) | 2001-03-01 | 2002-02-20 | Data exchange between insurer and repairer |
AU2007200869A AU2007200869A1 (en) | 2001-03-01 | 2007-02-28 | Data Exchange Between Insurer and Repairer |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AUPR3462 | 2001-03-01 | ||
AUPR3462A AUPR346201A0 (en) | 2001-03-01 | 2001-03-01 | Data exchange |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2002071281A1 true WO2002071281A1 (en) | 2002-09-12 |
Family
ID=3827477
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/AU2002/000176 WO2002071281A1 (en) | 2001-03-01 | 2002-02-20 | Data exchange between insurer and repairer |
Country Status (3)
Country | Link |
---|---|
AU (2) | AUPR346201A0 (en) |
NZ (1) | NZ527509A (en) |
WO (1) | WO2002071281A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1917613A1 (en) * | 2006-08-17 | 2008-05-07 | Scene Genesis, Inc. | Direct repair program management systems and methods thereof |
CN110516128A (en) * | 2019-08-15 | 2019-11-29 | 中国平安财产保险股份有限公司 | Information configuring methods, equipment, storage medium and device |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10963966B1 (en) | 2013-09-27 | 2021-03-30 | Allstate Insurance Company | Electronic exchange of insurance information |
US8799034B1 (en) | 2013-03-08 | 2014-08-05 | Allstate University Company | Automated accident detection, fault attribution, and claims processing |
US10032226B1 (en) | 2013-03-08 | 2018-07-24 | Allstate Insurance Company | Automatic exchange of information in response to a collision event |
US9019092B1 (en) | 2013-03-08 | 2015-04-28 | Allstate Insurance Company | Determining whether a vehicle is parked for automated accident detection, fault attribution, and claims processing |
US10572943B1 (en) | 2013-09-10 | 2020-02-25 | Allstate Insurance Company | Maintaining current insurance information at a mobile device |
US9443270B1 (en) | 2013-09-17 | 2016-09-13 | Allstate Insurance Company | Obtaining insurance information in response to optical input |
US10713717B1 (en) | 2015-01-22 | 2020-07-14 | Allstate Insurance Company | Total loss evaluation and handling system and method |
US9767625B1 (en) | 2015-04-13 | 2017-09-19 | Allstate Insurance Company | Automatic crash detection |
US10083551B1 (en) | 2015-04-13 | 2018-09-25 | Allstate Insurance Company | Automatic crash detection |
US11361380B2 (en) | 2016-09-21 | 2022-06-14 | Allstate Insurance Company | Enhanced image capture and analysis of damaged tangible objects |
US10902525B2 (en) | 2016-09-21 | 2021-01-26 | Allstate Insurance Company | Enhanced image capture and analysis of damaged tangible objects |
US10937103B1 (en) | 2017-04-21 | 2021-03-02 | Allstate Insurance Company | Machine learning based accident assessment |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5218539A (en) * | 1986-12-01 | 1993-06-08 | International Business Machines Corporation | Forms processor with controlled remote revision |
US5950169A (en) * | 1993-05-19 | 1999-09-07 | Ccc Information Services, Inc. | System and method for managing insurance claim processing |
US20020007289A1 (en) * | 2000-07-11 | 2002-01-17 | Malin Mark Elliott | Method and apparatus for processing automobile repair data and statistics |
WO2002015079A1 (en) * | 2000-08-17 | 2002-02-21 | Farmers Insurance Exchange | Automated claims filing and tracking |
-
2001
- 2001-03-01 AU AUPR3462A patent/AUPR346201A0/en not_active Abandoned
-
2002
- 2002-02-20 NZ NZ527509A patent/NZ527509A/en not_active IP Right Cessation
- 2002-02-20 WO PCT/AU2002/000176 patent/WO2002071281A1/en not_active Application Discontinuation
-
2007
- 2007-02-28 AU AU2007200869A patent/AU2007200869A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5218539A (en) * | 1986-12-01 | 1993-06-08 | International Business Machines Corporation | Forms processor with controlled remote revision |
US5950169A (en) * | 1993-05-19 | 1999-09-07 | Ccc Information Services, Inc. | System and method for managing insurance claim processing |
US20020007289A1 (en) * | 2000-07-11 | 2002-01-17 | Malin Mark Elliott | Method and apparatus for processing automobile repair data and statistics |
WO2002015079A1 (en) * | 2000-08-17 | 2002-02-21 | Farmers Insurance Exchange | Automated claims filing and tracking |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1917613A1 (en) * | 2006-08-17 | 2008-05-07 | Scene Genesis, Inc. | Direct repair program management systems and methods thereof |
EP1917613A4 (en) * | 2006-08-17 | 2010-12-22 | Scene Genesis Inc | Direct repair program management systems and methods thereof |
CN110516128A (en) * | 2019-08-15 | 2019-11-29 | 中国平安财产保险股份有限公司 | Information configuring methods, equipment, storage medium and device |
CN110516128B (en) * | 2019-08-15 | 2024-04-02 | 中国平安财产保险股份有限公司 | Information configuration method, device, storage medium and apparatus |
Also Published As
Publication number | Publication date |
---|---|
AU2007200869A1 (en) | 2007-03-22 |
AUPR346201A0 (en) | 2001-03-29 |
NZ527509A (en) | 2004-04-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU2007200869A1 (en) | Data Exchange Between Insurer and Repairer | |
US7742958B1 (en) | System and method for preparing a tax return using electronically distributed tax return data | |
US6574630B1 (en) | Investor relations event notification system and method | |
US6915234B2 (en) | Monitoring submission of performance data describing a relationship between a provider and a client | |
US8380797B2 (en) | Business data exchange layer | |
US20040083119A1 (en) | System and method for implementing a vendor contract management system | |
US20020157017A1 (en) | Event monitoring, detection and notification system having security functions | |
EP1577819A1 (en) | Advertising management system and method of operation | |
WO2003027865A1 (en) | Monitoring submission of performance data describing a relationship between a provider and a client | |
AU2002323103B2 (en) | Informational object authoring and distribution system | |
CA2667206A1 (en) | Method and apparatus for sending notification to subscribers of requested events | |
US20020156601A1 (en) | Event monitoring and detection system | |
US20030078756A1 (en) | Managing performance metrics describing a relationship between a provider and a client | |
AU2002323103A1 (en) | Informational object authoring and distribution system | |
CA2471022A1 (en) | Business transaction management | |
US20070198631A1 (en) | Method and system for data exchange between servers and mobile devices | |
CN111768013B (en) | Commercial bank public account comprehensive management system and method | |
CN101964710A (en) | Digital signature and signature authenticating method | |
CN112819437A (en) | Cloud management system for potential safety hazards in production | |
CN117217699A (en) | Contract approval management system and method | |
CN112131131A (en) | Automatic interface testing framework system for pre-constructed domain name and request body | |
AU2002231471B2 (en) | Data exchange between insurer and repairer | |
CN110009078A (en) | Station informatization management method and system based on two dimensional code | |
AU2002231471A1 (en) | Data exchange between insurer and repairer | |
US20030216984A1 (en) | System and method for querying accounts receivable and supporting decision-making |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ 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 MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM 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 GQ 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) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2002231471 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 527509 Country of ref document: NZ |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 527509 Country of ref document: NZ |
|
122 | Ep: pct application non-entry in european phase | ||
WWG | Wipo information: grant in national office |
Ref document number: 527509 Country of ref document: NZ |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |