WO2002027540A1 - Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator - Google Patents
Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator Download PDFInfo
- Publication number
- WO2002027540A1 WO2002027540A1 PCT/AU2001/001173 AU0101173W WO0227540A1 WO 2002027540 A1 WO2002027540 A1 WO 2002027540A1 AU 0101173 W AU0101173 W AU 0101173W WO 0227540 A1 WO0227540 A1 WO 0227540A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- contact information
- entity
- server system
- address book
- electronic address
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
Definitions
- the present invention relates to a computer method and system for the rapid addition of an entity's contact information to an offline electronic address book through the use of a Uniform Resource Locator (URL).
- URL Uniform Resource Locator
- a person or organization typically has a large amount of contact information associated with it. For instance, a person may have several phone numbers (e.g., telephone, facsimile, cell phone and pager) and addresses (e.g., mail, email and street).
- phone numbers e.g., telephone, facsimile, cell phone and pager
- addresses e.g., mail, email and street.
- contact details are represented in a non-electronic format, such as a business card, only a limited amount of information may be shown. In many instances it may not be possible to depict all of an entity's contact details. Even where there is space available to allow representation of all an entity's contact details, in many cases a recipient of that information is unlikely to enter all of these details into their electronic address book, since this may require considerable time to be expended to input infrequently used though potentially useful details.
- Business card scanners such as those manufactured by Corex Technologies Corporation of Cambridge, Massachusetts have been developed to accelerate the process of entering business card details into electronic address books. Such devices will scan a business card and convert it to a digital representation. Optical character recognition techniques can then be applied to the digital representation allowing details depicted on the card to be converted into text and placed in an electronic address book. The accuracy of details captured from a business card using a scanning device will depend upon whether those details are depicted on the card in way suitable for optical character recognition. Only details present on the business card may be entered into an electronic address book using a business card scanner.
- a person may register a network name (e.g., JohnKevinSmith.com) and map the network name to a numeric network address from which a network server can deliver information about the person (e.g., a web server delivering HyperText Markup Language pages).
- a network name e.g., JohnKevinSmith.com
- a network server e.g., a web server delivering HyperText Markup Language pages.
- personalized URLs It is also common for personalized URLs to be generated from existing network names by specifying an identifier in the network path portion of the URL.
- Apache a widely used HyperText Transfer Protocol (HTTP) server distributed by the Apache Software Foundation of Forest Hill, Maryland allows a person's personal home page to be retrieved by appending an identifier to domain name.
- HTTP HyperText Transfer Protocol
- an Apache server which listens on the network address associated with the domain name "xyzname.com” will, in response to a request for the URL "http://xyzname.com/ ⁇ jks" deliver the personal web page of the person with the identifier "jks”.
- Various Internet domains have been established which allow a user identifier to be prepended to an existing domain name thereby creating a personalized URL.
- the assigned names authority administrator of the ".au” domain established the "id.au” domain in 1995 for this purpose (http://www.id.au).
- the id.au domain has been subsequently subdelegated into a number of subdomains (e.g. "wattle.id.au” and “dropbear.id.au”) in which persons can apply for further subdomains based on the prepending of a personal identifier (e.g. "smith.wattle.id.au”).
- Such personalised domain names then allow persons allocated those domains to maintain resources of a personal nature which can be located using the personalised domain name.
- U.S. Pat. No. 6,085,242 describes a method of managing a repository of user information by providing a network user with a personalized URL consisting of an identifier prepended to a domain name. While reference is made to personal information, such as contact details, being part of the repository managed using the method, U.S. Pat. No. 6,085,242 does not teach a method of enabling contact information to be rapidly entered into an electronic address book.
- the present invention provides a method and system for enabling the recipient of a business card to rapidly enter information associated with the entity represented by the business card in an offline electronic address book.
- a Uniform Resource Locator ("URL") consisting of a domain name mapping to a server system and a unique identifier is placed on the business card.
- a recipient of the business card can use a browser to send a request to retrieve the network resource associated with the URL.
- the server system receives the request it isolates the identifier from the URL.
- the identifier is then used by the server system to retrieve contact details for the entity from a database.
- the server system then sends the browser a Web page containing hyperlinks which allow automated entry of those details in an offline electronic address book in response to a single action by the recipient.
- the browser is immediately sent the entity's contact details encoded in a form enabling automated entry of those details in an electronic address book.
- FIG. 1 is a block diagram illustrating an embodiment of the present invention.
- FIG. 2 is an illustration of a business card containing a URL which permits rapid entry of contact information.
- FIG. 3 illustrates two methods of encoding an identifier into a URL.
- FIG. 4 is a flow diagram illustrating the steps taken by the server system once a URL is entered in a browser by a card recipient.
- FIG. 5 is a flow diagram of a routine for determining whether a request received by the server system is for contact information.
- FIG. 6 provides examples of requests received by the server system as a consequence of a card recipient entering each different type of URL in a browser.
- FIG. 7 is an example of a HTML page generated by the server system in response to a request for contact information.
- FIG. 8 is a flow diagram of a routine for sending a card recipient an entity's contact information in a particular file format in response to a selection made by the recipient.
- FIG. 9 provides examples of contact information generated by the server system in output formats suitable for rapid entry into electronic address book applications.
- the present invention provides a method and system which enables the recipient of a business card to rapidly enter information associated with the entity represented by the business card in an electronic address book using a server system.
- FIG. 1 is a block diagram illustrating an embodiment of the present invention which allows rapid entry of contact information in an electronic address book using the Internet and HyperText Transport Protocol (World Wide Web) as a communications method.
- the server system includes a server engine 101 , a contact information database 102 and an identifier/contact information table 103.
- the server engine In response to network requests 109 from a browser 107 the server engine generates HyperText Markup Language ("HTML") pages 104 and files 105 containing contact information.
- HTML HyperText Markup Language
- the files containing contact information are suitable for direct import by electronic address book applications 108.
- an entity with a business card enters information associated with itself into a contact information database which can be accessed by the server engine.
- the information entered may include typical contact details such as the entity's name, job title, organisation, phone numbers or addresses (e.g., street, postal, website and email).
- the entity may also include other details which could be useful to communicate to business or personal contacts, such as a photo, geographic position coordinates, timezone information, birthdate, public key or digital recording of the correct pronunciation of the entity's name.
- This information may be either manually entered by or on behalf of the entity, or it could all or in part be taken from an existing database of information (e.g., a corporate or white pages directory).
- contact information may be stored in a database 106 which while not part of the server system can be queried by the server engine.
- the entity is assigned an identifier.
- the identifier may be allocated by the server system, chosen by the entity or allocated by the operator of the server system.
- the identifier could also one of the entity's contact details (e.g., a telephone number).
- the identifier consists of one or more characters or symbols drawn from a character set (e.g., ASCII) which can be entered using a keyboard.
- the server system maps the identifier to the contact information accessible by the server system which the entity wishes to make available to recipients of the entity's business card. This mapping is stored in an identifier / contact information table. A person skilled in the art would be aware that this table could be integrated into the contact information database.
- the entity places the identifier on the entity's business card in combination with instructions to retrieve a network resource which enables capture of the entity's contact details.
- the instructions may take the form of a Uniform Resource Locator ("URL") or Internet address in combination with words stating that the entity's contact details can be retrieved from this location, as illustrated in FIG. 2.
- the URL consists of an Internet domain name in conjunction with the identifier.
- the Internet domain name maps to the network address of the server system such that requests for resources located at the domain name are received by the server system.
- FIG. 3 illustrates two possible ways in which the identifier may be incorporated into the URL. In 301 the identifier is placed after the domain name and separated from it using the character "/".
- the identifier is again placed after the domain name, but it is separated from it using the character "/" followed by an additional delimiter consisting of one or more characters.
- This scheme allows the use of a domain name which is also used to deliver other network resources.
- the delimiter should be chosen so as to not conflict with the names of any network resources also to be made available at the network location represented by the domain name. For instance, if the network protocol associated with the URL is the HyperText Transport Protocol ("HTTP”) a delimiter consisting of the character "+" could be used because resources associated with HTTP servers rarely begin with the character "+".
- HTTP HyperText Transport Protocol
- This form of URL would enable a domain name which is already associated with a HTTP server to be used because the presence of a "+" at the beginning of the resource name could be used to differentiate URLs associated with contact information from URLs associated other with network resources.
- a person skilled in the art would recognise that there are other ways of encoding the identifier in a URL in combination with a domain name which maps to the server system. Where the scheme associated with the URL is HTTP, the prefix "http://" may be omitted since the HTTP protocol is normally inferred in the case of URLs which are not prefaced by a scheme.
- the identifier associated with the card entity is encoded, together with a domain name which maps to the server system, into a single URL. This enables a card recipient to send a request for contact details associated with the card entity to the server system by entering the URL in a browser.
- Each encoding scheme results in a URL consisting only of a domain name, identifier and delimiter characters. This permits entry of such URLs with as few keystrokes as possible.
- FIG. 4 illustrates in overview the steps taken by the server system when the recipient of a business card enters the URL in a browser. Each of these steps is described below.
- FIG. 5 is a flow diagram of a routine for determining whether a request is for contact information or another resource.
- the browser When a card recipient types the URL depicted in the card in a browser, the browser will send a request for the URL to the server system.
- the server system receives this request.
- the server system checks if the request contains the delimiter character (e.g., a "+") in the appropriate position (e.g., after the "/"). If the delimiter is present the server system knows the request is for contact information. If the delimiter is not present the server system can conclude that this is a request for a network resource other than contact information and either deliver that network resource to the requesting browser or redirect the browser to another URL where the network resource can be found (step 503).
- the delimiter character e.g., a "+”
- the server system can conclude immediately that the request is for contact information on the basis that no other resources share these domain names. All requests for resources to network addresses mapped to these domain names must be requests for contact information since these domain names are only used to construct URLs which refer to contact information.
- the server system determines that the request is for contact information the server system then, in step 403, determines the identifier sent by the browser as part of the request.
- FIG. 6 illustrates the HTTP version 1.1 requests the server system can expect to receive if an example URL of type 301 (601) or 302 (602) is entered in a HTTP version 1.1 compliant browser.
- the browser transmits the identifier to the server system as shown in underline, and the server engine isolates the identifier from the request.
- step 404 the server engine queries the identifier/contact information table to determine which items of contact information the entity associated with the identifier wishes to make available to card recipients.
- the contact information is then retrieved from the contact information database and utilised by the server engine in step 405 to generate a HTML page.
- FIG. 7 is an example of such a HTML page.
- Section 701 contains all or part of the entity's contact information.
- Section 702 contains a number of hyperlinks to URLs which allow direct download of the entity's contact information in different file formats.
- the URL associated with each hyperlink consists of a domain name which maps to the server system, the identifier, and an indication of the file format to be downloaded.
- Each hyperlink is represented on the page by text which describes the file format of contact information which will be sent if a link is clicked on and/or the application software or device which can utilise contact information in that particular file format.
- FIG. 8 shows the steps which occur if a card recipient clicks on one of the hyperlinks enabling download of the entity's contact information in a particular file format.
- the card recipient's browser will send a request which will be received by the server system in step 801.
- the server engine first determines the identifier from the request and then queries the identifier / contact information table to determine which items of contact information the entity associated with the identifier wishes to make available to card recipients.
- the contact information is then retrieved from the contact information database.
- step 803 the server engine reformats the contact information into the particular file format (e.g., vCard) the card recipient has requested.
- step 804 the server system sends this file to the card recipient's browser.
- the browser Once the browser has completed download of the file (step 805) the browser will typically launch application software associated with the file type (e.g., in the case of a card recipient who chooses to download the entities details in vCard format, an address book application which supports vCard format files will be launched) (step 806).
- address book application software which supports the file format downloaded as a method of importing contact information is available (e.g., Microsoft Outlook when the file type is a vCard) the entity's contact information will be automatically profiled into a new entry in the card recipient's electronic address book.
- the entity's contact information may also be stored in scripting language commands (e.g., Javascript) embedded in a hyperlink in the HTML page generated in step 405 and delivered to the card recipient.
- scripting language commands e.g., Javascript
- address book application software which supports entry of address book details via scripting language commands (e.g., Netscape Communicator)
- activating such a hyperlink will cause the execution of the scripting commands resulting in the entity's contact information being entered in the electronic address book associated with the card recipient's software which supports the scripting commands used.
- FIG. 9 illustrates step 803 in detail and shows three possible output formats for contact information.
- the server engine 902 retrieves the contact information from the contact information database 901. This information is then dynamically reformatted by the server engine into a format which can imported into an electronic address book. Which particular format the information is delivered in is determined by the hyperlink clicked on by the card recipient.
- Format 903 is an example of contact information formatted into a vCard file which can then be directly imported into an electronic address book which supports vCard.
- the HTTP "Content-type" header is set to "application/vcard” so the browser is aware the file being sent is a vCard and can launch any address book application available which is associated with this file type (e.g., Microsoft Outlook).
- the same contact information is URL encoded in a HTML hyperlink containing Javascript commands which when clicked on will cause the contact information to be profiled into a new entry in the address book of a compatible application (e.g., Netscape Communicator).
- the contact information is formatted as a comma separated values (CSV) file suitable for electronic address books which support the import of generically formatted information (e.g. Psion Series 3a handheld computers).
- CSV comma separated values
- a card recipient can have an entity's contact information automatically entered into an electronic address book simply by typing a single URL into a browser and selecting the type of electronic address book to populate from a list shown on the resulting HTML page.
- the system entirely avoids manual entry of the entity's contact information and the potential for errors to be made during this process. Since the contact information used to populate the electronic address book is not drawn from the card itself but a contact information database, up to date contact information can be retrieved using a card which may contain out of date details, provided information in the contact information database is kept current.
- the system also allows more contact information than is present on a card to be entered into an electronic address book.
- the server system does not generate a HTML page in response to a request for a URL which relates to contact information but instead sends the recipient's browser a file containing the entity's contact information (e.g., a vCard file) without the intermediate step of generating a HTML page offering a selection of file formats.
- a file containing the entity's contact information e.g., a vCard file
- This method would be appropriate where a particular file format for storing contact details predominates and it is not necessary to provide the card recipient with a choice of format to download.
- the present invention is not intended to be limited to the particular preferred embodiments which have been described above. Modifications which fall within the spirit and scope of the invention will be apparent to those skilled in the art.
- the server system may respond to requests from any type of browser (e.g., a Wireless Application Protocol microbrowser).
- contact information may be encoded in file formats (e.g. SyncML) which can be imported into electronic address books residing on devices other than personal computers, such as mobile phones, personal organizers, handheld computers and personal digital assistants.
- the URL used to request card information may also be placed on items other than business cards where it is desirable to allow recipients of the item to rapidly add contact information to their address book (e.g., letterheads and advertisements).
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB0307346A GB2385444B (en) | 2000-09-26 | 2001-09-19 | Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator |
AU9148101A AU9148101A (en) | 2000-09-26 | 2001-09-19 | Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator |
AU2001291481A AU2001291481B2 (en) | 2000-09-26 | 2001-09-19 | Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US66958800A | 2000-09-26 | 2000-09-26 | |
US09/669,588 | 2000-09-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2002027540A1 true WO2002027540A1 (en) | 2002-04-04 |
Family
ID=24686909
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/AU2001/001173 WO2002027540A1 (en) | 2000-09-26 | 2001-09-19 | Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator |
Country Status (3)
Country | Link |
---|---|
AU (2) | AU9148101A (en) |
GB (1) | GB2385444B (en) |
WO (1) | WO2002027540A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003088613A1 (en) * | 2002-04-15 | 2003-10-23 | Nokia Corporation | Method and device for handling synchronization related information |
EP1494148A1 (en) * | 2003-07-01 | 2005-01-05 | Alexandre Rambaud | System and Method for storing data in an electronic diary via internet |
US7194484B2 (en) | 2003-11-17 | 2007-03-20 | America Online, Inc. | Correction of address information |
WO2007139824A2 (en) | 2006-05-22 | 2007-12-06 | Microsoft Corporation | Synchronizing structured web site contents |
US8798584B1 (en) | 2002-11-07 | 2014-08-05 | Joseph G. Swan | Apparatuses for requesting, retrieving and storing contact records |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2328304A (en) * | 1997-08-15 | 1999-02-17 | Ken Scott Associates | Portable device for storing and displaying personal information |
WO1999033293A1 (en) * | 1997-12-23 | 1999-07-01 | Global Mobility Systems, Inc. | System and method for controlling personal information and information delivery to and from a telecommunications device |
WO2000014640A1 (en) * | 1998-09-03 | 2000-03-16 | Sony Electronics, Inc. | Apparatus and method for retrieving information over a computer network utilizing a hand-held portable device |
US6085242A (en) * | 1999-01-05 | 2000-07-04 | Chandra; Rohit | Method for managing a repository of user information using a personalized uniform locator |
-
2001
- 2001-09-19 GB GB0307346A patent/GB2385444B/en not_active Expired - Fee Related
- 2001-09-19 AU AU9148101A patent/AU9148101A/en active Pending
- 2001-09-19 AU AU2001291481A patent/AU2001291481B2/en not_active Ceased
- 2001-09-19 WO PCT/AU2001/001173 patent/WO2002027540A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2328304A (en) * | 1997-08-15 | 1999-02-17 | Ken Scott Associates | Portable device for storing and displaying personal information |
WO1999033293A1 (en) * | 1997-12-23 | 1999-07-01 | Global Mobility Systems, Inc. | System and method for controlling personal information and information delivery to and from a telecommunications device |
WO2000014640A1 (en) * | 1998-09-03 | 2000-03-16 | Sony Electronics, Inc. | Apparatus and method for retrieving information over a computer network utilizing a hand-held portable device |
US6085242A (en) * | 1999-01-05 | 2000-07-04 | Chandra; Rohit | Method for managing a repository of user information using a personalized uniform locator |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003088613A1 (en) * | 2002-04-15 | 2003-10-23 | Nokia Corporation | Method and device for handling synchronization related information |
US7308642B2 (en) | 2002-04-15 | 2007-12-11 | Nokia Mobile Phones, Ltd. | Method and device for handling synchronization related information |
KR100873711B1 (en) | 2002-04-15 | 2008-12-12 | 노키아 코포레이션 | Method and device for handling synchronization related information |
US8798584B1 (en) | 2002-11-07 | 2014-08-05 | Joseph G. Swan | Apparatuses for requesting, retrieving and storing contact records |
EP1494148A1 (en) * | 2003-07-01 | 2005-01-05 | Alexandre Rambaud | System and Method for storing data in an electronic diary via internet |
FR2857118A1 (en) * | 2003-07-01 | 2005-01-07 | Alexandre Rambaud | SYSTEM AND METHOD FOR SAVING DATA IN AN INTERNET ELECTRONIC AGENDA |
US7194484B2 (en) | 2003-11-17 | 2007-03-20 | America Online, Inc. | Correction of address information |
WO2007139824A2 (en) | 2006-05-22 | 2007-12-06 | Microsoft Corporation | Synchronizing structured web site contents |
EP2024866A2 (en) * | 2006-05-22 | 2009-02-18 | Microsoft Corporation | Synchronizing structured web site contents |
EP2024866A4 (en) * | 2006-05-22 | 2012-05-09 | Microsoft Corp | Synchronizing structured web site contents |
US8572028B2 (en) | 2006-05-22 | 2013-10-29 | Microsoft Corporation | Synchronizing structured web site contents |
Also Published As
Publication number | Publication date |
---|---|
AU9148101A (en) | 2002-04-08 |
GB2385444B (en) | 2004-07-07 |
GB2385444A (en) | 2003-08-20 |
GB0307346D0 (en) | 2003-05-07 |
AU2001291481B2 (en) | 2006-06-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6018761A (en) | System for adding to electronic mail messages information obtained from sources external to the electronic mail transport process | |
US7437383B2 (en) | System and method for searching heterogeneous electronic directories | |
CN1640109B (en) | Method of mapping names or identifiers to telecommunications network resource locations | |
US6674453B1 (en) | Service portal for links separated from Web content | |
RU2245577C2 (en) | Electronic message board and mail server | |
US6728346B2 (en) | User recognition support for multifunction office device | |
US20020069223A1 (en) | Methods and systems to link data | |
US20080243793A1 (en) | Contact Information Capture and Link Redirection | |
US20020078180A1 (en) | Information collection server, information collection method, and recording medium | |
US20020184319A1 (en) | Systems and methods for facilitating access to an information address | |
KR20010031603A (en) | Method and system for accessing information on a network | |
US20030177274A1 (en) | Virtual subdomain address file suffix | |
US7080079B2 (en) | Method of using the internet to retrieve and handle articles in electronic form from printed publication which have been printed in paper form for circulation by the publisher | |
WO2013056340A1 (en) | Method for automatically tagging documents with matrix barcodes and providing access to a plurality of said document versions | |
US20030050920A1 (en) | Contacts management using virtual subdomains | |
US6977740B1 (en) | Method and system for centralized information storage retrieval and searching | |
US20020087529A1 (en) | System and method for a digital business card | |
AU2001291481B2 (en) | Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator | |
AU2001291481A1 (en) | Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator | |
AU733242B3 (en) | Method and system for the rapid addition of contact information to an electronic address book using a uniform resource locator | |
JP3361509B2 (en) | Server, information provision support method, program | |
KR20010016370A (en) | Electronic business card service system and method for performing the same | |
US11188706B2 (en) | System and method for regionalized resolution of a network path | |
KR20030004653A (en) | Information support system and the method using real-time web search | |
WO2001035237A1 (en) | A system for webpage connection of using electronic mail address and a method of the same |
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 EC 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 PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA 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 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 |
|
ENP | Entry into the national phase |
Ref document number: 0307346 Country of ref document: GB Kind code of ref document: A Free format text: PCT FILING DATE = 20010919 Format of ref document f/p: F |
|
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: 2001291481 Country of ref document: AU |
|
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 |