WO2001029710A2 - Noms de domaines derives - Google Patents

Noms de domaines derives Download PDF

Info

Publication number
WO2001029710A2
WO2001029710A2 PCT/US2000/041168 US0041168W WO0129710A2 WO 2001029710 A2 WO2001029710 A2 WO 2001029710A2 US 0041168 W US0041168 W US 0041168W WO 0129710 A2 WO0129710 A2 WO 0129710A2
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
name
derivative
domain
server
Prior art date
Application number
PCT/US2000/041168
Other languages
English (en)
Other versions
WO2001029710A3 (fr
Inventor
Kenneth F. Leonard
Original Assignee
Nametree, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nametree, Inc. filed Critical Nametree, Inc.
Priority to AU19648/01A priority Critical patent/AU1964801A/en
Publication of WO2001029710A2 publication Critical patent/WO2001029710A2/fr
Publication of WO2001029710A3 publication Critical patent/WO2001029710A3/fr

Links

Classifications

    • C—CHEMISTRY; METALLURGY
    • C07—ORGANIC CHEMISTRY
    • C07D—HETEROCYCLIC COMPOUNDS
    • C07D209/00—Heterocyclic compounds containing five-membered rings, condensed with other rings, with one nitrogen atom as the only ring hetero atom
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/345—Types of network names containing wildcard characters

Definitions

  • a domain name is an identifier that identifies a computer, or group of computers, on the Internet.
  • users try to select a domain name that is easily remembered and somewhat representative of the services provided by the computers associated with the domain name.
  • the Boston Globe has registered the domain name "Boston.com" for a set of computers that offer a website having information about current events in the Boston area.
  • the invention features a method for allowing a domain name holder to create a sub- space of derivative domain names.
  • the method includes allowing the registered holder of a domain name to designate a selected authoritative server for that domain name, allowing a third party to request an operator of the designated authoritative server to register a derivative domain name that is to be associated with a network device or service chosen by the third party, and creating for the selected authoritative server a table of derivative domain names.
  • Each derivative domain name including a primary domain name and being associated with a pointer to the network device or service chosen by the third party.
  • Embodiments may include one or more of the following.
  • Designating an authoritative name server may include transferring rights in the name to a trusted third party.
  • the derivative domain names may include domain names expressed in natural language or using characters from different character sets such as Unicode.
  • the method may include use of a hierarchical security system.
  • the invention features a computer-implemented method of processing a domain name query.
  • the method includes storing Internet Protocol addresses corresponding to respective derivative domain names, receiving a domain name query for a derivative domain name, and retrieving an Internet Protocol address corresponding to the received domain name query.
  • Embodiments may include one or more of the following.
  • the derivative domain names may include at least one spaces between non-space characters.
  • the derivative domain names may be encoded using at least two different character sets.
  • the domain names may be stored in a table .
  • the method may also include receiving a derivative domain name and a corresponding Internet Protocol address for storage in the table. Such a method may include determining whether an entity submitting the derivative domain name and corresponding Internet Protocol address is authorized to store the derivative domain name in the table.
  • the method may also include determining whether an entity attempting to access the table has authorization.
  • the method may include storing Internet Protocol addresses corresponding to non- derivative domain names.
  • the method may also include transmitting the retrieved Internet Protocol address over a network to an entity requesting processing of the domain name query.
  • the invention features a computer program product, disposed on a computer readable medium, for causing a processor to store Internet Protocol addresses corresponding to respective derivative domain names, receive a domain name query for a derivative domain name, and retrieve an Internet Protocol address corresponding to the received domain name query.
  • the invention features a method of doing business that includes registering a domain name and licensing one or more derivative domain names including the registering domain name without licensing the registered domain name.
  • Fig. 1 is a diagram of the hierarchical structure of the Domain Name Space
  • Fig. 2 is a block diagram of a system for allowing a domain name holder to create a sub-space of domain names
  • Fig. 3 is a flow chart of a process for allowing a registered domain name holder to provide a domain sub-space to a third party user.
  • the disclosure describes a name server that is capable of creating a sub- space of domain names for a registered domain space.
  • the sub-space may include domain names in a wide variety of languages, character sets, and forms.
  • search systems including search systems that may process a requested domain name to provide a list of sub-domains associated with that domain name, or for any other suitable application.
  • Other additions and modifications can be made to the invention without departing from the scope hereof .
  • domain name holders can leverage the present architecture of the Internet, or a similar computer network, to allow a holder of a registered domain name to create a sub-space of derivative domain names and license, sell, share, or assign the sub-space, or portions of the sub-space, to third parties
  • identity of a computer on the Internet is given by a binary address .
  • a common notation for representing the binary address depicts the address as a series of numbers such as 198.203.55.175.
  • the Internet provides a system, the domain name system (DNS) , that allows a user to employ a domain name, such as "nametree.com,” to refer to a host computer.
  • DNS domain name system
  • the DNS acts as a distributed database that can resolve a domain name, like nametree.com, into an associated Internet address, such as 198.203.55.175.
  • the DNS system employs a hierarchical structure to support the translation service.
  • the DNS hierarchical structure has an unnamed root directory ("root") with a well-known address.
  • the level immediately below the root of the Internet DNS includes a number of top level domains ("tld-s") including the ARPA domain; generic or organizational domains, such as com, edu, and gov; and a country or geographical group of domains that includes a set of two character country codes .
  • the Internet DNS distributes responsibility for maintaining the DNS database across different servers. These different servers have responsibility for resolving different types of domain names. For example, the root directory may pass a domain name query for a ".com" domain name to the server responsible for translating ".com" domain names. Similarly, these second level servers may identify the appropriate name server for a particular domain being sought. To this end, a name server can examine an incoming name query to determine whether that server has authority, or is the authoritative server, for the specified domain. To accomplish this, the name server can parse the domain name, for example, to identify the label that occurs to the left of the tld.
  • the name server may parse the domain name "nametree.com” to identify the tld ".com” and the preceding label "nametree.” If the preceding label indicates a domain over which that server has authority, the server translates the name into an IP address, using the local name server database, and sends the answer to the client.
  • the server's response depends on the type of query sent by the resolver.
  • Resolvers typically request a domain name translation in one of two ways.
  • the resolver may ask the server to perform the complete translation. This is deemed a recursive resolution. If the client requests recursive resolution and the server cannot resolve the name, the server will contact a domain name server that may resolve the domain name and return the answer to the client.
  • resolvers may also request an iterative resolution of a domain name. A request for an iteratative resolution tells the server to either resolve the name or tell the client which server to contact next. In this case, the contacted server does not handle the complete resolution for the client.
  • FIG. 2 shows a functional block diagram of a domain name server system 10 that forms a distributed database with an authoritative name server 18 capable of parsing a name query for a derivative domain name to identify a host address associated with that derivative domain name. More specifically, Fig. 2 depicts a system 10 that includes a browser machine 12, a root name server 14, an authoritative server 18, having a primary and a secondary name server, servers 20 and 22 respectively, and a target machine 24.
  • the browser machine 12 may comprise conventional data processing platforms, such as IBM PC-compatible computers running the Windows operating systems, or a SUN workstation running a version of the Unix operating system.
  • the browser machine 12 maybe running an Internet browser program, such as the Netscape Navigator browser program, the Microsoft Internet Explorer program, the Lynx browser program or any other suitable browser program.
  • an Internet browser program such as the Netscape Navigator browser program, the Microsoft Internet Explorer program, the Lynx browser program or any other suitable browser program.
  • the depicted system 10 is described with reference to a browser operating with an Internet DNS system, it will be understood by those of ordinary skill in the art that the systems and methods described herein can also work with other types of client applications that request a name server to resolve the IP address for a domain name, as well as with other types of networks including intranets, extranets, and any other suitable network.
  • Fig. 2 further depicts that the system 10 includes a root level name server 14 that can be, for example the root level Internic name server which is capable of receiving from the browser machine 12 a name query representative of a request to resolve a domain name into an Internet address .
  • the root name server 14 resolves a name query to identify a second tier name server, such as the depicted authoritative name server 18, that has responsibility for resolving the domain name carried within the name query.
  • the structure of the authoritative name server 18 can vary from the server 18 shown.
  • the authoritative name server 18 may be authoritative for sub-domains, but not necessarily for the domain name. Other architectures and designs can be employed without departing from the scope of the invention.
  • the root level name server 14 may respond to a name query from the browser machine 12 by transmitting a response that indicates where the authoritative server 18 for the domain name is located.
  • the browser machine 12 may then employ this information to request the authoritative server 18 to resolve the domain name into an Internet address.
  • the authoritative server 18 may resolve all name queries that end in the registered domain name, "nametree.com.”
  • any name query that includes the domain name "nametree.com” such as for example "People at nametree.com”, or "Products from nametree.com” will be forwarded to the authoritative server 18 to be resolved thereby.
  • the depicted authoritative server 18 is capable of parsing a domain name to identify an extension to the domain name that precedes the domain name within the name query.
  • the authoritative server 18 may parse a complex domain name such as "people at nametree.com” to identify the terms and white space that may occur within any phrase that immediately preceded the domain name, "nametree.com.”
  • the authoritative name server 18 of the invention allows the resolution of complex, or derivative, domain names wherein the domain name requested by the client machine 12 may include a primary domain name such as "nametree.com” or "boston.com” as well as further labels that precede the primary domain name .
  • the authoritative server 18 may include a primary name server 20 and a secondary name server 22 that may act as conventional name servers capable of resolving domain names for the zone of responsibility for that authoritative server 18. Additionally, however, the authoritative server 18 is also capable of accessing a database 28 that can store information about derivative domain names as well as the IP addresses to which these domain names can map. For example, the database 28 may store derivative domain names and associated IP addresses such as those depicted in Table I .
  • a derivative domain name may include one ore more spaces in between non-space characters. Since such domain names do not follow the traditional syntax of DNS domain names, traditional name servers may handle receipt of such domain names unpredictably.
  • the database 28 may couple to the authoritative name server 18 to act as a supplemental database. Additionally, the database 28 may couple to a work station 26 wherein an operator can supplement, modify, or otherwise work with the contents of the database 28.
  • the database 28 may provide or distribute to other servers portions of the data. These portion can correspond to sub- domains or other logical structures. Additionally, entities, such as individuals and companies, can register sub-domains. The design of such a system follows from principles known in the art, and various embodiments, including appropriate additional features can be added to the system without departing from the scope of the invention.
  • the authoritative server 18 maybe capable of parsing different types of derivative domain names including derivative domain names that include Unicode characters, kanj i characters, Cyrillic characters, or any other type of characters. Additionally, the authoritative server 18 maybe capable of parsing derivative domain names that are formed as natural language statements, such as, for example, derivative domain names that employ white spaces or multiple white spaces for separating the labels within the derivative domain name. Other types of derivative domain names may also be parsed by the systems described herein without departing from the scope of the invention. As further shown by TABLE I, each of the derivative names within the database 28 maybe associated with an IP address.
  • the IP addresses can reference one or more host computers that are owned or operated by third parties that have licensed or otherwise received the right to use the primary domain name as part of their derivative domain name. Alternatively, the IP addresses may point to host computers or other resources .
  • the database 28 may store entries, such as the entry "Directory of Boston.com", that links to a service or other resource that provides information about all, or portions, of the other derivative domains associated with the primary domain.
  • entries such as the entry "Directory of Boston.com”
  • a query for "Directory of Boston.com” can retrieve a link to a web server that provides a web page that describes or identifies the derivative domains under the primary domain Boston.com.
  • the systems described herein may include search engine systems that allow users to search through the data of the central registry, or portions of the central registry, to allow a user to identify domains or sub domains that are include a keyword or phrase, or that relate to a certain IP address.
  • Such a search engine may allow for a user to employ Boolean logic operators to form complex user queries for retrieving domain names or sub-domain names that include certain patterns of text, numbers, kanji, Unicode, or other atomic unit of an extant domain or sub-domain name.
  • the systems described herein can include a security or control system that provides a hierarchical structure of authority to the domain space, or portions of the domain space.
  • the system may include a hierarchical control structure that requires a user to enter a password before the structure of a sub-domain can be altered.
  • the user can be provided a login page that allows the user to enter a username and password.
  • the security system can determine an authority level for that user given that password, and provide for that user a predetermined level of authority that allows the user to change portions of the structure of the defined domain space or to view or alter certain sub-domains within the defined domain space.
  • the system will employ a username and password to identify a portion of the defined domain space that can be altered or viewed or otherwise accessed by the user.
  • the system may operate similar to a Unix file system, that may mount, in response to the username and password entered by the user, a portion of a directory structure into an existing file system, which can be generally available to all users.
  • the mounted portion maybe viewed and accessed by the user, or perhaps just viewed, depending on the level of authority granted to the user.
  • the name server may also interpret aspects of the derivative domain names as instructions for the domain name server.
  • Fig. 3 depicts one process for allowing a person to register a domain name and then allow the registered domain name to be employed by third parties that wish to create derivative domain names that maybe resolved by an authoritative server such as the authoritative server 18 described above.
  • the process 30 depicted in Fig. 3 begins when a user registers 32 a domain name.
  • the processes for registering a domain name are well known in the art and any suitable process maybe practiced with the present invention without departing from the scope hereof.
  • the nameholder designates 34 an authoritative server.
  • the designated authoritative server is the server that is understood by the Internet DNS system, or any other system that is being employed for resolving a name to a computer address, as the server that is responsible for being able to resolve the domain name into a suitable computer address.
  • the process may allow the registered name holder to transfer ownership for the domain name to a trusted party, or to an escrow agent, that will be charged with maintaining the server 18 as the recorded authoritative server for the registered domain name.
  • the domain name registered may be published 38 for third parties to view and consider using as a primary domain name for a derivative domain name of interest to the third party.
  • the third party can then register 40 a derivative domain name based on one of the published available domain names.
  • the registration process employed in 40 maybe similar to the process employed in 32, however it will be understood that the registered derivative domain name may employ characters and a format that the Internet DNS system may be incapable of resolving but that the authoritative server 18 would be capable of resolving.
  • an entry representative 42 of the derivative name and an associated IP address is entered into a table that maybe stored within a database such as the database 28 depicted in Fig. 2.
  • the process 30 may proceed to 44 wherein conventional Internet domain names are resolved by the primary and secondary servers 20 and 22 respectively of the authoritative server 18.
  • Derivative domain names may also be resolved by the authoritative server 18 through access to the database 28 depicted in Fig. 2.
  • the authoritative server 18 may function both as a conventional authoritative server 18 suitable for use with a typical domain name system as well as an authoritative server that is capable of resolving derivative domain names such as those described above and other similar types of derivative domain names .
  • the systems and processes described herein are merely examples of the types of systems and processes that can implemented according to the invention. These systems can be implemented as C language computer programs, or as computer programs written in any high level language including C++, Fortran, Java or basic. The development of such systems arises from principles well known in the art including those set forth in, for example, Stephen G. Kochan, Programming in C, Hayden Publishing (1983) . Those skilled in the art will know or be able to ascertain using no more than routine experimentation, many equivalents to the embodiments and practices described herein.
  • the systems of the invention can be provided as development systems for allowing users to develop their own systems for distributing rights in a domain name.
  • the business practices described herein can include practice for establishing domain name franchises. Accordingly, it will be understood that the invention is not to be limited to the embodiments disclosed herein, but is to be understood from the following claims, which are to be interpreted as broadly as allowed under the law.

Landscapes

  • Engineering & Computer Science (AREA)
  • Organic Chemistry (AREA)
  • Chemical & Material Sciences (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)
  • Stored Programmes (AREA)
  • Devices For Executing Special Programs (AREA)

Abstract

L'invention concerne des procédés, des programmes informatiques et des systèmes destinés à prendre en charge les interrogations relatives aux noms de domaines. Les interrogations relatives aux noms de domaines peuvent inclure des noms de domaine dérivés tels que les noms de domaines comprenant des espaces.
PCT/US2000/041168 1999-10-15 2000-10-13 Noms de domaines derives WO2001029710A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU19648/01A AU1964801A (en) 1999-10-15 2000-10-13 Derivative domain names

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US15977799P 1999-10-15 1999-10-15
US60/159,777 1999-10-15

Publications (2)

Publication Number Publication Date
WO2001029710A2 true WO2001029710A2 (fr) 2001-04-26
WO2001029710A3 WO2001029710A3 (fr) 2004-05-06

Family

ID=22573979

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2000/028382 WO2001029001A2 (fr) 1999-10-15 2000-10-13 Recherche du nom de domaine
PCT/US2000/041168 WO2001029710A2 (fr) 1999-10-15 2000-10-13 Noms de domaines derives

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2000/028382 WO2001029001A2 (fr) 1999-10-15 2000-10-13 Recherche du nom de domaine

Country Status (2)

Country Link
AU (2) AU1964801A (fr)
WO (2) WO2001029001A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7099956B2 (en) * 2000-01-31 2006-08-29 Ideaflood, Inc. Method and apparatus for conducting domain name service

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9311399B2 (en) 1999-09-07 2016-04-12 C. Douglass Thomas System and method for providing an updating on-line forms and registrations
US7747592B2 (en) 1999-09-07 2010-06-29 Thomas C Douglass Method and system for monitoring domain name registrations
DE102005029661B3 (de) * 2005-06-21 2006-11-30 Siemens Ag Verfahren zur Namensauflösung und Namensauflösungs-Server

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997031490A2 (fr) * 1996-02-20 1997-08-28 Hewlett-Packard Company Procede d'acces a une entite cible sur un reseau de telecommunications

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997031490A2 (fr) * 1996-02-20 1997-08-28 Hewlett-Packard Company Procede d'acces a une entite cible sur un reseau de telecommunications

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
DUERST M: ", INTERNATIONALIZATION OF DOMAIN NAMES" INTERNET DRAFT, XX, XX, July 1998 (1998-07), pages 1-14, XP002167569 *
FOO S ET AL: "APPROACHES FOR RESOLVING DYNAMIC IP ADDRESSING" INTERNET RESEARCH: ELECTRONIC NETWORKING APPLICATIONS AND POLICY, XX, XX, vol. 7, no. 3, 1997, pages 208-216, XP000199862 ISSN: 1066-2243 *
NETWORK SOLUTIONS: "DOMAIN NAMES CALIFORNIA TORTILLA" NETWORK SOLUTIONS, January 1998 (1998-01), pages 1-1, XP002936812 Retrieved from the Internet: URL:HTTP://REGISTER.WORLDNIC.COM/SERVLET/N SI.REGPLUS.MAIN.UPDATEDOMAINLIST> [retrieved on 2002-12-13] *
P. MOCKAPETRIS: "rfc1034 - Domain Names: Concepts and facilities" REQUEST FOR COMMENT, November 1987 (1987-11), pages 1-55, XP002108902 *
ROBERT J. DUWORS: "RE: What is the Private Sector?" GTLD-MOU GENERAL DISCUSSION LIST, 24 November 1996 (1996-11-24), pages 1-1, XP002269899 ISSN: 7 Retrieved from the Internet: URL:http://www.gtld-mou.org/gtld-discuss/m ail-archive/05486.html> [retrieved on 2004-02-11] *
RON FITZHERBERT: "Re: don heath's comments" GTLD-MOU GENERAL DISCUSSION LIST, 24 November 1996 (1996-11-24), pages 1-1, XP002269898 Retrieved from the Internet: URL:http://www.gtld-mou.org/gtld-discuss/m ail-archive/00615.html> [retrieved on 2004-02-11] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7099956B2 (en) * 2000-01-31 2006-08-29 Ideaflood, Inc. Method and apparatus for conducting domain name service
US8015317B2 (en) 2000-01-31 2011-09-06 Hoshiko Llc Method, system and computer-readable medium for conducting domain name service

Also Published As

Publication number Publication date
WO2001029710A3 (fr) 2004-05-06
WO2001029001A3 (fr) 2003-12-24
WO2001029001A2 (fr) 2001-04-26
AU1202701A (en) 2001-04-30
AU1964801A (en) 2001-04-30

Similar Documents

Publication Publication Date Title
US7280999B2 (en) Network address server
US6745248B1 (en) Method and apparatus for analyzing domain name registrations
US7603474B2 (en) Efficient endpoint matching using a header-to-bit conversion table
KR100444757B1 (ko) 다언어 도메인 네임 서비스
EP1159820B1 (fr) Procede et systeme d'internationalisation de noms de domaines
US8543732B2 (en) Method and apparatus for multiplexing internet domain names
US20070208877A1 (en) Method and Apparatus for Providing Name Services
EP1234434B1 (fr) Serveur d'adresses reseau
US20060218289A1 (en) Systems and methods of registering and utilizing domain names
US20040162916A1 (en) Multiple use of identical names to identify different IP numerical addresses
US20040019697A1 (en) Method and system for correcting the spelling of incorrectly spelled uniform resource locators using closest alphabetical match technique
JP2002082856A (ja) ネットワーク上の情報へのアクセス方法及びシステム
US20080294796A1 (en) Native Language Internet Address System
KR100706702B1 (ko) 도메인네임서버를 이용한 한글 인터넷컨텐츠주소 서비스 방법 및 시스템
US8341252B2 (en) Internet domain name super variants
WO2001029710A2 (fr) Noms de domaines derives
CN114978740B (zh) 基于区块链的标识关联和验证的解析方法
US20020133591A1 (en) Method and apparatus for mapping of attributes to networked resources
US20020073209A1 (en) Method for redirecting a network communication
CA2392619C (fr) Serveur d'adresses reseau
KR20010081927A (ko) 단일 아이디를 이용한 다중 서비스 액서스 방법 및 시스템
WO2001069456A1 (fr) Procede et dispositif pour mapper des attributs a rattacher aux ressources d'un reseau
Popp et al. Common name resolution protocol (CNRP)
Popp et al. RFC3367: Common Name Resolution Protocol (CNRP)
WO2017191495A1 (fr) Nouveau système de nom de domaine et son utilisation

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN 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 PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

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

Ref country code: JP