WO2000026807A2 - Gestion active de serveurs - Google Patents

Gestion active de serveurs Download PDF

Info

Publication number
WO2000026807A2
WO2000026807A2 PCT/IB1999/001878 IB9901878W WO0026807A2 WO 2000026807 A2 WO2000026807 A2 WO 2000026807A2 IB 9901878 W IB9901878 W IB 9901878W WO 0026807 A2 WO0026807 A2 WO 0026807A2
Authority
WO
WIPO (PCT)
Prior art keywords
server
servers
server manager
network
dhcp
Prior art date
Application number
PCT/IB1999/001878
Other languages
English (en)
Other versions
WO2000026807A3 (fr
Inventor
Tony Farrow
Ian Hamilton
Glenn Waters
Original Assignee
Nortel Networks Corporation
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 Nortel Networks Corporation filed Critical Nortel Networks Corporation
Priority to AU64848/99A priority Critical patent/AU6484899A/en
Publication of WO2000026807A2 publication Critical patent/WO2000026807A2/fr
Publication of WO2000026807A3 publication Critical patent/WO2000026807A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • 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/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • 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/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • 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/50—Address allocation
    • H04L61/5076—Update or notification mechanisms, e.g. DynDNS
    • 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

Definitions

  • the present invention relates to the field information networking and more specifically to transmitting configuration information between a central database and one or more servers in a network.
  • FIG. 1 illustrates an overall diagram of a conventional Transmission Control Protocol (TCP)/Internet Protocol (IP) network 101 including one or more Domain Name Service (DNS) servers 102 A - N, one or more Dynamic Host Configuration Protocol (DHCP) servers 103 A - N and a central database 104.
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • DNS Domain Name Service
  • DHCP Dynamic Host Configuration Protocol
  • the one or more DNS servers 102 A - N and DHCP servers 103 A - N on the network transmit requests for configuration information and send configuration updates to the central database 104.
  • the central database 104 either transmits the requested configuration information back to each server or it stores the configuration updates received from each server.
  • DHCP simplified the management and assignment of IP addresses to clients by eliminating the need for the network administrator to manually configure the network.
  • DCHP when a client requests an IP address in order to communicate over the network, a DHCP server answers the request by providing network configuration information that was obtained from a database and dynamically assigning an IP address to the client.
  • Each DHCP server manages a range of client addresses and can pick any address from that range as long as it is not being used by a another client managed by that DHCP server. Since the address is dynamically assigned, the client can have a different IP address each time it logs on to the network.
  • a DHCP server also supports static IP address that have been assigned to one particular client on the network. Based on the configuration information received from the database, the DHCP server can automatically assign a specific IP address to a specific client.
  • DNS also simplified the management of networks by translating domain names into IP addresses. Since the DNS server contains a list of domain names and their associated IP addresses, a host or client can be located through by its domain name rather than its IP address. Any given domain name could be associated with more than one IP address and any IP address could be associated with more than one domain name.
  • a DNS server updates the domain name and IP address associations by periodically polling a central database containing configuration information for the network. When a new client is assigned an IP address by a DHCP server, the new configuration information is stored in the central database. Each DNS servers on the network poll the central database for configuration changes. If a new IP address was assigned to a client managed by a DNS server, the DNS server updates the domain name with the new IP address or updates the IP address with the new domain name. 2
  • a server manager acts as an interface between the one or more servers and the central database.
  • the server manager also synchronizes requests for configuration information and configuration updates from the one or more servers and transmits the requests and updates to the central database through a single communication channel.
  • the server manager receives the configuration information from the central database and sends the information to the servers that issued the requests.
  • the server manager also transmits the configuration updates from the one or more servers to the central database.
  • the server manager polls the central database for any changes in configuration made to the network. If the server manager finds any changes stored in the central database, it transmits the changes to the appropriate servers.
  • the server manager also processes multiple requests at one time and queues up any further requests based on the priority of the work requested or the order in which they were received.
  • Figure 1 is an overall diagram of a conventional TCP/IP network.
  • FIG. 2 is an overall diagram of a TCP/IP network as may implement the present invention.
  • Figure 3 is a flow diagram illustrating the steps for a server to server manager login process as may be utilized by an embodiment of the present invention.
  • Figure 4 is a flow diagram illustrating a method for communicating configuration information from the central database to a DHCP server through the server manager as may be utilized by an embodiment of the present invention.
  • Figure 5 is a flow diagram illustrating a method for communicating configuration updates from the central database to a DNS server as may be utilized by an embodiment of the present invention.
  • Figure 6 is a flow diagram illustrating a method for retrieving any configuration changes in the network from the delta-logging facility in the central database and transmitting them to the servers on the network as may be utilized by an embodiment of the present invention.
  • Figure 7 is a flow diagram illustrating a method for determining the operational status of the DNS and DHCP servers on the network and transmitting the status information to the NMS as may be utilized by an embodiment of the present invention.
  • Figure 8 is a flow diagram illustrating a method for authenticating a user and binding the user to the IP address dynamically assigned to it by a DHCP server as may be utilized by an embodiment of the present invention.
  • reference numerals in all of the accompanying drawings typically are in the form "drawing number" followed by two digits, xx; for example, reference numerals on Figure 1 may be numbered lxx; on Figure 3, reference numerals may be numbered 3xx.
  • FIG. 2 illustrates a TCP/IP network configured in accordance with the methods and apparatus discussed herein.
  • the network can contain a plurality of servers that must access the central database in order to obtain configuration information.
  • a server manager can be introduced. The server manager would communicate directly with the plurality of servers and the central database and transmit any requests from the servers to the central database. Therefore, the central database only would need to communicate with the server manager. As will be discussed, this reduces the number of requests which must be managed by the central database.
  • IP addressing is integrated with DNS and DHCP management. All configuration changes, whether made statically, dynamically or at remote locations, are registered in the central database and automatically distributed to the appropriate servers. Also, DHCP redundancy guarantees that a DHCP server is always serving a given range of client addresses. Primary and backup DHCP servers serve the same address range which ensures that DHCP clients in the range can always acquire an IP address. Internet Service Providers (ISP) can benefit from the present invention because management of IP address space is simplified.
  • ISP Internet Service Providers
  • DHCP servers can act as both DHCP and Bootstrap Protocol (BootP) servers which enables ISPs to integrate the static allocation of IP addresses to cable modems through BootP with the dynamic allocation of IP addresses to end users through DHCP.
  • the present invention also will be of great importance in such applications as Voice/Fax Over IP and Policy-Enabled Networking where a user needs an authenticated address to access network services.
  • the network includes a server manager 201, one or more DNS servers 202A - N, one or more DHCP servers 203A - N, a central database 204, a NMS 205, one or more clients 208, a Lightweight Directory Access Protocol (LDAP) server 209 and a LDAP database 210.
  • the one or more DNS servers 202A - N and DHCP servers 203 A - N are coupled in communication with the server manager 201 through individual communication channels.
  • the server manager 201 is coupled in communication with the central database 204 over a single communication channel 206 and the NMS 205 over a single communication channel 207.
  • the LDAP server 209 is coupled in communication with the server manager 201 over a single communication channel 211.
  • the LDAP server 209 can communicate directly with the central database 204.
  • the central database 204 may be any number of conventional databases. In the described embodiment, either a Sybase 7.3 or 8.0, available from Sybase, Inc. of Emeryville, CA or Oracle 11.x database, available from Oracle Corporation of Redwood Shores, CA, is utilized to store network configuration information.
  • the configuration information may include DNS and DHCP parameters, other server parameters, IP addresses, domain names, the operational status of servers that have successfully logged in to the network and the like.
  • the central database 204 is relational and stores changes in configuration made to the network. Because the central database 204 is relational, it can log any configuration changes in a separate area. For purposes of this disclosure, the section of the central database 204 that contains the log of changes in configuration will be referred to as the delta-logging facility.
  • the server manager 201 can restore the central database 204 to a previously known state. For example, if the central database becomes corrupted, the server manager can search the delta logging facility for the configuration information of a previously known uncorrupted state.
  • the one or more DNS servers 202A - N are Berkeley Internet Name Domain (BIND) 4.9.5 DNS servers, BIND 8. 1.1 DNS servers or the like. These servers 202A - N communicate with the central database 204 through the server manager 201. Each DNS server is coupled to the server manager 201 through a TCP link. The TCP links from the servers 202 A - N to the server manager 201 enable dynamic DNS updates and dynamic DNS reconfiguration.
  • the one or more DHCP servers 203A - N are based on the BootP. These servers 203A - N also communicate with the server manager 201 through a TCP link and update the central database 204 with changes in DHCP configuration.
  • the ability of the DHCP servers to update the central database with configuration changes enables incremental synchronization of DNS and DHCP services.
  • the servers that can be linked to the server manager are not limited to DNS and DHCP servers.
  • a similar configuration could be used to support Remote Access Dial In User Services (RADIUS), Policy and future servers through the use of protocol server plug-in technology.
  • RADIUS Remote Access Dial In User Services
  • the server manager 201, DNS 202 A - N and DHCP 203 A - N servers described in the embodiment may, for example, run on the operating systems and hardware platforms given in Table 1.
  • the DNS servers 202A - N and DHCP servers 203 A - N must first login with the server manager 201. If the login process is successful, the servers 202A - N, 203 A - N must set their server id in able to issue command and requests to the server manager 201 for processing.
  • the following sections describe how the servers 202A - N, 203A - N complete the login process and how they communicate with the server manager 201. It should be appreciated that the methods described can be performed in other ways without departure from the scope of the present invention.
  • FIG. 3 provides a flow diagram illustrating steps utilized in the described embodiment for a server to server manager login process.
  • the login process is not unique to one type of server and can be used by any server attempting to establish a communication channel with the server manger 201.
  • the one or more DNS servers 202A - N and DHCP servers 203A - N establish a TCP link to the server manager 201, step 301.
  • each server 202A - N, 203A - N issues a login request by providing a userid and a password to the server manager 201, step 302.
  • the password for each server 202A - N, 203A - N is only known by each individual server and the server manager 201.
  • the server manager 201 validates the userid and password by using MD5, which is described in detail in Rivest, R., "The MD5 Message-Digest Algorithm,” Networking Group Request For Comments (RFC) 1331, April 1992, to compute a digest value, step 303. If the password is correct, the server, for example a DNS server 202 A, is logged in to the server manager 201, step 305. If the password is incorrect, the login fails and the server manager 201 drops the TCP link, step 304. In order to retry the login sequence, the server 202 A must reinitiate a TCP link to the server manager 201 and start the login process from the beginning, step 301.
  • each DNS server 202 A - N and DHCP server 203A - N After logging in with the server manager 201 , each DNS server 202 A - N and DHCP server 203A - N must set their server-id, step 306. Each server-id is checked against all of the DNS and DHCP servers already coupled in communication with the server manager 201, step 307. If the server-id is the same as a server-id for a server already on the network, the TCP link for the requesting server will be dropped, step 308. If the server-id is unique to that server, the login process is complete, step 309.
  • the servers can issue requests for configuration information from the central database 204 or send updated configuration information to the central database 204.
  • the server manager 201 synchronizes all of the requests and updates from the servers and transmits them to the central database 204.
  • the server manager 201 monitors all the DNS servers 202A - N and DHCP servers 203A - N on the network from a single point and acts as a single pipeline to the central database 204. For example, when a new client 208 sends a request for an IP address to a DHCP server 203A, the DHCP server 203 A determines if it can send configuration information to the requesting client 208.
  • the DHCP server 203A can give an IP address and configuration information to the client 208, it sends host configuration information and an IP address to the client 208.
  • the DHCP server 203A automatically registers the new domain name, the IP address and the host configuration information with the central database 204 through the server manager 201.
  • the DNS server 202 A detects the new IP address through the server manager and updates its DNS information.
  • the DHCP server 203A notifies the central database 204 of the change through the server manager 201.
  • the IP address is available for reassignment by the DHCP server 203A to a new client. Therefore, the server manager 201 eliminates the need for the individual DNS servers 202 A - N and DHCP servers 203A - N to establish direct communication channels with the central database by providing access to the central database 204 through one communication channel 206. (more????)
  • the described embodiment utilizes plug-in technology in order to allow support for current as well as future generation servers.
  • the DHCP server plug-in has three functions: (1) Provides configuration information to the DHCP servers linked to the network; (2) Informs the DHCP servers of any relevant changes in the central database; and (3) Transacts the DHCP hosts into the central database.
  • FIG 4 provides a flow diagram which is useful for describing a method of the described embodiment for transmitting configuration information from the central database 204 to a DHCP server 203 A.
  • the server manager 201 receives a request for configuration information from a DHCP server 203 A, step 401, it checks to see if the server-id is zero, step 402. If the server-id is zero, the message is ignored, step 403. 6 Otherwise, the server manager 201 initiates a process to retrieve configuration information from the central database 204.
  • the server manager 201 first receives information, such as range and host lists, from the DHCP server 203 A, step 404. It then builds a subnet list associated with the DHCP server 203 A based on the range and host lists, step 405.
  • the server manager 201 then requests the configuration information from the central database 204 based on the lists provided by the DHCP server 203A and the lists it created, step 407.
  • the central database 204 transmits configuration information requested by the server manager 201, step 408, and this information is sent to the DHCP server 203 A requesting the configuration information, step 409.
  • the configuration information can consist of (1) the global options for the network, which is sent to the requesting server and the backup server serving the same address ranges, if DHCP redundancy is supported, (2) the network options for each network contained in the network list that was created by the server manager, (3) the subnet options for each subnet contained in the subnet list, (4) the range options for each range contained in the range list and (5) the host options for each host contained in the host list. 7
  • a benefit of processing all requests for configuration information from the central database 204 by the DHCP servers 203A - N in the server manager 201 is that the load on the central database 204 is reduced.
  • the server manager 204 eliminates the active link between every DHCP server 203A - N that needs configuration information from the central database 204.
  • the server manager 201 also notifies each DHCP server 203 A - N of any changes to the central database 201.
  • the server manager 201 polls the delta-logging facility in the central database 204 for configuration changes made to the network that would effect the DHCP servers 203A - N coupled in communication with the server manager 201.
  • the interval in between polling can be either a default value or a value set by a user such as the network administrator. In the described embodiment, the interval between each time the server manager 201 polls the central database 204 for configuration changes is 60 seconds.
  • Figure 5 provides a flow diagram which illustrates a method of the described embodiment for retrieving, any changes in configuration made to the network from the delta-logging facility in the central database 204 and transmitting them to the DHCP 203A - N servers coupled in communication with the server manager 201.
  • the server manager 201 queries the delta-logging facility in the central database 204, step 501, to determine if there were any configuration changes, step 502. If there were changes in configuration, the server manager 201 issues a request to the central database 204 for the global range information, the network information, the global client pool and each client pool and client pool entry managed by the DHCP servers 203A - N, step 503.
  • the server manager 201 retrieves the appropriate information, step 504 and distributes it to the appropriate DHCP 203 A - N servers. 9 If the server manager 201 finds no changes or has completed distributing the changes to the DHCP server 203A - N, it waits the set interval of time and polls the delta-logging facility again for changes, step 501.
  • a benefit of only allowing the server manger 201 to pool the delta-logging facility for changes in configuration is that the load on the network is reduced. The reduced load and reduced amount of traffic to the database increases the overall performance of the network because the server manager 201 automatically determines which DHCP servers 203 A - N are effected by the changes. This eliminates update requests from DHCP servers that are not affected by the configuration changes made to the network.
  • the server manager 201 also processes host commit requests from DHCP servers 203A - N. 10
  • the server manager 201 In order to add host information to the central database 204, the server manager 201 must determine if the domain name is available, unavailable, moving from another host or being updated.
  • the server manager 201 Upon receiving a request from a DHCP server 203A to add a host, the server manager 201 first checks if the domain is a Canonical Name (CNAME) or primary name. If the domain is a CNAME, it fails validation and the server manager 201 notifies the DHCP server 203 A that the domain is unavailable." If the domain does not exist in the central database 204, the label 12 may be assigned to the host and the server manager 201 notifies the DHCP server 203 A that the domain is available.
  • CNAME Canonical Name
  • the label may be assigned to the requesting host and the server manager notifies the DHCP server 203A that the domain is available. If the host in the central database 204 is static, the label can't be used and the server manager 201 notifies the DHCP server 203 A that the domain is unavailable. If the IP addresses match, the label is updated and the server manager 201 notifies the DHCP server 203 A that the domain has been updated. If the IP addresses do not match, the label is moved to the requesting host and the server manager 201 notifies the DHCP server 203 A that the domain has been moved.
  • the server manager 201 notifies the DHCP server 203 A that the domain is unavailable. If the server manager 201 determines that the domain name is available, the server manager adds the new host to the network by (1) setting the host IP address; (2) assigning a client-id to the host; (3) setting the hardware address; (4) setting the DHCP server-id; (5) assigning a lease expire time; and (7) determining a domain name. 13 The server manager 201 will then validate all of the above information. If the validation fails, the server manager 201 notifies the DHCP server 203 A that the host commit failed, otherwise the server manager 201 notifies the DHCP server 203 A that the host has been committed and transmits the host information to the central database 204.
  • the DNS server's plug-in has two functions: (1) Provides format configuration information to the both the BIND 4.9.5 DNS servers and the BIND 8.1.1 DNS servers; and (2) Informs them of the relevant changes in the central database.
  • Figure 6 provides a flow diagram which is useful for describing a method of the described embodiment for communicating configuration updates from the central database 201 to a DNS server 202 A. 14
  • the server manager 201 receives a configuration update message from a DNS server 202A, step 601
  • the server manager 201 receives the primary and secondary zones managed by the DNS server 202 A, step 604.
  • the server manager 201 then issues a configuration update request for each zone managed by the DNS server 202 A to the central database 204, step 605.
  • the central database 204 transmits the configuration information for each zone to the sever manager 201, step 606.
  • the server manager 201 then transmits the updated configuration information to the DNS server, step 607.
  • the server manger 201 sends the Start of Authority (SOA) record, name servers of the zone, the A record, 15 RR record, option record, CNAME record and the glue record with the subzones to the DNS server 202A.
  • SOA Start of Authority
  • the server manager 201 For each primary reverse zone, the server manager 201 sends the SOA record, name servers of the zone, the PTR record for each subdomain of the zone and the glue record with the subzones to the DNS server 202A. For each secondary zone, the server manager 201 sends that zone transfer list to the DNS server 202 A. Finally, the server manager 201 sends information about the root server on the network to the DNS server 202A. 17
  • the server manager 201 also polls the delta-logging facility in the central database 204 periodically to determine if there were any changes in configuration made to the network that would effect the DNS servers 202 A - N.
  • the process of polling the delta-logging facility in the central database 204 for the DNS servers 202A - N is similar to the process previously described in Figure 5 for the DHCP servers 203A - N.
  • the server manager 201 requests the primary and secondary zone information, the primary forward and reverse zone information, the subzone information for each subzone not managed by a DNS server and the subdomain of one of the primary zones managed by the DNS server. Once the server manager 201 retrieves this information, it transmits the relevant information to the appropriate DNS servers 203A - N. 18
  • This method has a similar benefit, as described above in the DHCP section, in that DNS servers that are not effected by the configuration changes will not be polling the central database 204 for changes since the only server manager 201 is coupled in communication with the central database 204.
  • the server manager 201 can process multiple requests or commands at the same time. However, the number of requests or updates that the server manager 201 can process at the same time is determined by the machine that it is running on. Therefore, the server manager 201, as used by the described embodiment, prioritizes what it processes based on the type of work requested.
  • the server manager 201 services the requests and updates in the following order: (1) get configuration requests from the DCHP servers; (2) polling the central database for any configuration changes in the network; (3) configuration update requests from the DNS servers; and (4) removing leases for IP addresses when they expire. 19 Prioritizing based on the type of work requested is not the only method available for the server manager 201 to process information. It could also process the information based on a first-in first-out method. For example, the first request or packet of information received by the server manager 201 would be processed first and the last request or packet of information received by the server would be processed last.
  • the server manager 201 also has the ability to actively manage the DNS 202A to 202N and DHCP 203 A - N servers and report their operational status to the NMS 205.
  • the NMS 205 communicates with an agent, the server manager 201, to keep track of the network statistics and resources. Network administrators can use the NMS 205 to view the real-time operating status of the DNS 202 A - N and DHCP 203 A - N servers that are linked with the server manager 201.
  • the NMS 205 could be a graphical user interface (GUI) running on a powerful computer such as a workstation.
  • GUI graphical user interface
  • Figure 7 provides a flow diagram which illustrates a method of the described embodiment for determining the operational status of the DNS 202 A - N and DHCP 203 A - N servers on the network and transmitting the status information to the NMS 205.
  • the server manager 201 polls the servers every 40 seconds to determine if the server is still running or if it has stopped, step 701. 20
  • the server generates an alarm or warning to indicate its operating status and communicates the message to the server manager 201, step 702.
  • the message could contain information such as a key word to trigger the correct plug-in, the severity of the alarm, the specific server-id, and an alarm code to indicate the problem.
  • the server manager 201 queues up the reports from the servers along with any other requests that it receives and attaches a database time stamp to each one.
  • the server manager 201 then communicates the alarms to the central database 204 and to the NMS 205, step 703. 21
  • the alarms are sent to the NMS 205 through a Simple Network Management Protocol (SNMP) trap.
  • the traps could contain information such as setting the server status to up when the server successfully establishes a TCP link with the server manager 201, setting the server status to down when the TCP link between the server and the server manager is dropped and setting the server status to failed login when the server successfully establishes a TCP link with the server manager 201 but tried an invalid login. These traps can then be viewed from the GUI by the network administrator.
  • the advantage to using the server manager 201 for active server management is that the server manager 201 can detect when a server has crashed. In some embodiments, multiple servers are running on the same hardware. If the hardware is still running but one of the servers has crashed, the server manager 201 can detect the change through the TCP link which will be dropped if the server crashes. When the TCP link is started or dropped, the server manager 201 generates an exception, such as the described SNMP traps, to the NMS 205. Therefore, the network administrator is able to determine if a server has gone down if the hardware is still operational.
  • the present invention also allows a user to be authenticated and binds the user to the IP address that was given to it by the DHCP server on the network.
  • Figure 8 provides a flow diagram which illustrates a method of the described embodiment for authenticating a user and binding the user to their current address.
  • a client 208 requests an IP address from the DHCP server 203N on the network, step 801.
  • the DHCP server 203N dynamically assigns the client 208 an IP address before it has been authenticated, step 802.
  • the client 208 then issues a registration request with the binding server 209 and communicates its userid, password and the IP address it just obtained from the DHCP server 203N to the binding server 209, step 803.
  • the method of communication used by the client in the described embodiment is the Hyper Text Transfer Protocol (HTTP) but alternative methods can be used.
  • HTTP Hyper Text Transfer Protocol
  • the client does not provide itself with a userid or password.
  • two examples of methods for the client to obtain its userid and password are to have the user go to a World Wide Web (WWW) page or download a Java applet to obtain information from a PC or workstation which could modify the operating system to automatically provide it.
  • WWW World Wide Web
  • the binding server 209 then authenticates the userid, password and IP address through an LDAP request to the LDAP database 210, step 804.
  • the LDAP request searches the LDAP database 210 for the userid, password and the possible IP addresses that the DHCP server 203N could assign, step 805.
  • the LDAP database 210 is organized in a tree hierarchy. For example, the root of an Internet address is at the top and the common name associated with the user is at the bottom.
  • the LDAP database 210 is accessible through an open, standards based protocol such as TCP. If the information is found in the LDAP database 210, it notifies the binding server 209 that the user credentials were verified by returning the authenticated credentials, step 807. 22
  • the binding server 209 then sends the authenticated credentials to be stored in the central database 204, step 808.
  • the binding server 209 communicates with the server manager 201 over a single channel 211 to store the credentials in the central database 204. However, the binding server 209 could also communicate directly or through some other device with the central database 204 in order to store the authenticated credentials.
  • the present invention as utilized in the described embodiment authenticates the actual userid password and address combination.
  • Applications such as Voice/Fax over IP and Video Conferencing can benefit from the present invention because routing and bandwidth considerations are based on source and destination addresses. Therefore, deciding which users can access the network services requires authenticated addresses.

Abstract

Procédé et dispositif permettant de gérer l'adressage IP dans un réseau et de synchroniser efficacement la communication entre une base de données centrale et un ou plusieurs serveurs (tels que DNS et DHCP).
PCT/IB1999/001878 1998-10-29 1999-10-29 Gestion active de serveurs WO2000026807A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU64848/99A AU6484899A (en) 1998-10-29 1999-10-29 Active server management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/183,537 1998-10-29
US09/183,537 US6374295B2 (en) 1998-10-29 1998-10-29 Active server management

Publications (2)

Publication Number Publication Date
WO2000026807A2 true WO2000026807A2 (fr) 2000-05-11
WO2000026807A3 WO2000026807A3 (fr) 2000-08-31

Family

ID=22673228

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB1999/001878 WO2000026807A2 (fr) 1998-10-29 1999-10-29 Gestion active de serveurs

Country Status (3)

Country Link
US (1) US6374295B2 (fr)
AU (1) AU6484899A (fr)
WO (1) WO2000026807A2 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002005510A1 (fr) * 2000-07-11 2002-01-17 Nokia Corporation Procede permettant de fournir une liste d'adresses de serveurs dns d'un serveur a un client
US6920506B2 (en) 2001-06-28 2005-07-19 Canon Information Systems, Inc. Discovery and management of network printers
JP2005521635A (ja) * 2001-10-10 2005-07-21 ネオス・テクノロジーズ・インコーポレーテツド ペプチドの改造および複合糖質化
WO2005106701A2 (fr) 2004-04-16 2005-11-10 Infoblox, Inc. Maintien de l'integrite des donnees dans un environnement reparti
US7454482B2 (en) 2001-06-28 2008-11-18 Canon Information Systems, Inc. Print queue manager
US8498971B2 (en) 2004-04-16 2013-07-30 Infoblox Inc. Maintaining consistency in a database
EP3107248A4 (fr) * 2014-02-12 2017-10-18 Nec Corporation Dispositif de traitement d'informations, procédé de communication, dispositif et procédé de commande de réseau, système de communication et programme

Families Citing this family (91)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6564216B2 (en) * 1998-10-29 2003-05-13 Nortel Networks Limited Server manager
US7167904B1 (en) * 1999-03-19 2007-01-23 Network Solutions, Llc Unified web-based interface-to multiple registrar systems
IL146091A0 (en) * 1999-04-22 2002-07-25 Network Solutions Inc A shared registrations system for registering domain names
US6587455B1 (en) * 1999-05-27 2003-07-01 Telefonaktiebolaget Lm Ericsson (Publ) Automatic discovery of nodes associated with a virtual subnet
US7251826B1 (en) 1999-06-07 2007-07-31 Register.Com, Inc. Domain manager for plural domains and method of use
US7032022B1 (en) 1999-06-10 2006-04-18 Alcatel Statistics aggregation for policy-based network
ATE301895T1 (de) 1999-06-10 2005-08-15 Alcatel Internetworking Inc System und verfahren zur automatischen erreichbarkeitsaktualisierung in virtuellen privaten netzen
US6708187B1 (en) * 1999-06-10 2004-03-16 Alcatel Method for selective LDAP database synchronization
DE69935138T2 (de) * 1999-08-20 2007-11-22 International Business Machines Corp. System und Verfahren zur Optimierung der Leistung und der Verfügbarkeit eines DHCP Dienstes
US6687746B1 (en) * 1999-08-30 2004-02-03 Ideaflood, Inc. System apparatus and method for hosting and assigning domain names on a wide area network
CA2281367C (fr) * 1999-09-01 2002-12-17 Ibm Canada Limited-Ibm Canada Limitee Methode et appareil d'administration simplifiee d'un grand nombre de serveurs semblables de traitement d'information
US6760324B1 (en) * 1999-09-10 2004-07-06 Array Telecom Corporation Method, system, and computer program product for providing voice over the internet communication
US6823454B1 (en) * 1999-11-08 2004-11-23 International Business Machines Corporation Using device certificates to authenticate servers before automatic address assignment
US6826690B1 (en) * 1999-11-08 2004-11-30 International Business Machines Corporation Using device certificates for automated authentication of communicating devices
US6487594B1 (en) * 1999-11-30 2002-11-26 Mediaone Group, Inc. Policy management method and system for internet service providers
EP1104965B1 (fr) * 1999-12-02 2007-02-28 Sony Deutschland GmbH Protocole de messagerie instantanée
JP2001195333A (ja) * 2000-01-06 2001-07-19 Sony Corp 情報通信装置の設定方法
US6842769B1 (en) * 2000-05-05 2005-01-11 Interland, Inc. Automatically configured network server
US6868444B1 (en) * 2000-05-05 2005-03-15 Interland, Inc. Server configuration management and tracking
US7962603B1 (en) 2000-06-06 2011-06-14 Nobuyoshi Morimoto System and method for identifying individual users accessing a web site
US6895431B1 (en) * 2000-09-29 2005-05-17 Interland, Inc. Providing user access to dynamic updating of remote configuration information
DE10049610A1 (de) * 2000-10-05 2002-04-18 Alcatel Sa Netzwerkmanagement-Client
US7039697B2 (en) * 2000-11-01 2006-05-02 Snapnames.Com Inc. Registry-integrated internet domain name acquisition system
US6976063B1 (en) * 2000-11-02 2005-12-13 Microsoft Corporation Method and system for dynamically configuring a server computer
JP2003052660A (ja) * 2001-07-25 2003-02-25 Ge Medical Systems Global Technology Co Llc プロトコル・医用画像登録方法、医用画像提供方法、プロトコル利用方法、プロトコル・医用画像登録システム、医用画像提供システム、プロトコル利用システム、ベンダー端末、利用者端末、およびプロトコル管理サーバ装置
JP2003099341A (ja) * 2001-09-20 2003-04-04 Canon Inc ネットワークデバイス管理装置、管理システム及び管理方法、並びにネットワークデバイス
US6823362B2 (en) * 2001-10-16 2004-11-23 Hewlett-Packard Development Company, L.P. Effectively and efficiently updating content files among duplicate content servers
WO2003050648A2 (fr) * 2001-11-12 2003-06-19 Worldcom, Inc. Systeme et procede pour la mise en oeuvre fluide de micro-paiements relatifs a des services consommables
US7519729B2 (en) * 2002-02-27 2009-04-14 Ricoh Co. Ltd. Method and apparatus for monitoring remote devices through a local monitoring station and communicating with a central station supporting multiple manufacturers
PL372459A1 (en) * 2002-03-27 2005-07-25 Siemens Aktiengesellschaft Aaa server system for efficient access control and address assignment
AU2003216667A1 (en) * 2002-04-19 2003-11-03 Nagravision Sa Method for the transmission of management messages in an ip network broadcasting system
US7600003B1 (en) * 2002-04-22 2009-10-06 Cisco Technology, Inc. Method and apparatus for dynamically configuring customer premises network equipment
KR100505221B1 (ko) * 2002-07-03 2005-08-03 엘지전자 주식회사 조속한 아이피주소 업데이트가 가능한 가전기기 네트워크망의 원격제어시스템 및 그 아이피주소 업데이트방법
US7143435B1 (en) * 2002-07-31 2006-11-28 Cisco Technology, Inc. Method and apparatus for registering auto-configured network addresses based on connection authentication
US20040034705A1 (en) * 2002-08-13 2004-02-19 Mihai Focsaneanu Connecting devices in a data network
US7734745B2 (en) * 2002-10-24 2010-06-08 International Business Machines Corporation Method and apparatus for maintaining internet domain name data
WO2004042999A1 (fr) * 2002-11-06 2004-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Procede et agencement empechant une utilisation illegitime d'adresses ip
US6836798B1 (en) * 2002-12-31 2004-12-28 Sprint Communications Company, L.P. Network model reconciliation using state analysis
US7389345B1 (en) 2003-03-26 2008-06-17 Sprint Communications Company L.P. Filtering approach for network system alarms
US7421493B1 (en) 2003-04-28 2008-09-02 Sprint Communications Company L.P. Orphaned network resource recovery through targeted audit and reconciliation
DE10329858A1 (de) * 2003-07-02 2005-01-27 Siemens Ag Verfahren zur Konfiguration einer Einrichtung in einem Datennetz
TWI237792B (en) * 2003-07-11 2005-08-11 Via Tech Inc Method and apparatus for updating simultaneously distributed webpage data of various languages, and storage medium therefor
US7519988B2 (en) * 2003-07-31 2009-04-14 International Business Machines Corporation Method and apparatus for authenticated network address allocation
DE10338113B4 (de) * 2003-08-15 2006-10-12 Hewlett-Packard Development Co., L.P., Houston Netzwerkserver und Verfahren zur Auffindung von Netzwerkknoten
US8254896B2 (en) * 2003-08-25 2012-08-28 Research In Motion Limited Implementing a web server on a mobile station
JP3886484B2 (ja) * 2003-10-27 2007-02-28 Ｎｅｃビューテクノロジー株式会社 端末装置、ネットワーク設定方法、ネットワークシステム及びプログラム
US20050125559A1 (en) * 2003-12-02 2005-06-09 Mutha Kailash K. Employment of one or more identifiers of one or more communication devices to determine one or more internet protocol addresses
US20050144287A1 (en) * 2003-12-11 2005-06-30 International Business Machines Corporation Computer product and system for establishing network connections
US20050128952A1 (en) * 2003-12-11 2005-06-16 International Business Machines Corporation Executing and implementing a service for establishing network connections
US7181653B2 (en) * 2003-12-11 2007-02-20 Lenovo Singapore Pte, Ltd Method for establishing network connections
US8156081B2 (en) * 2004-06-25 2012-04-10 Apple Inc. Method and apparatus for updating resource records in a name-server database
US7940730B1 (en) 2004-11-04 2011-05-10 At&T Mobility Ii Llc Network-initiated method and system for establishing data communication using IP with a wireless terminal
EP1662752A1 (fr) * 2004-11-26 2006-05-31 Siemens Schweiz AG Procédé pour configurer un dispositif via PPPoE utilisant DHCP
US20080275992A1 (en) * 2005-02-09 2008-11-06 Access Systems Americas, Inc. System and method of managing connections between a computing system and an available network using a connection manager
US20060250982A1 (en) * 2005-05-05 2006-11-09 Harrow Products Llc Methods and systems for discovering and configuring network devices
GB2430279A (en) * 2005-05-11 2007-03-21 Royce Technology Ltd Metasearch tool for recruitment purposes
US7506067B2 (en) * 2005-07-28 2009-03-17 International Business Machines Corporation Method and apparatus for implementing service requests from a common database in a multiple DHCP server environment
US20070033272A1 (en) * 2005-08-04 2007-02-08 Vasu Vallabhaneni Dynamic subnet updates
US20070061355A1 (en) * 2005-09-13 2007-03-15 International Business Machines Corporation Computer- implemented method, system, and program product for managing data for an information technology (IT) migration
US20070198993A1 (en) * 2006-02-06 2007-08-23 Zhongyao Zhang Communication system event handling systems and techniques
US7596615B2 (en) * 2006-02-22 2009-09-29 Microsoft Corporation Multi-server automated redundant service configuration
US20070282782A1 (en) * 2006-05-31 2007-12-06 Carey Julie M Method, system, and program product for managing information for a network topology change
TWI323992B (en) * 2006-09-08 2010-04-21 Quanta Comp Inc Method for detecting status of host and/or i/o peripherals in certralized computer system
US8862735B1 (en) 2006-12-05 2014-10-14 Aol Inc. IP address management of multiple DHCP and DNS servers
US7694016B2 (en) * 2007-02-07 2010-04-06 Nominum, Inc. Composite DNS zones
US7689671B2 (en) * 2007-03-09 2010-03-30 International Business Machines Corporation System and method for multiple IP addresses during domain name resolution
US7694019B2 (en) * 2007-03-09 2010-04-06 International Business Machines Corporation System and method for accessing multiple addresses per domain name using networked repository
JP4858271B2 (ja) * 2007-03-30 2012-01-18 ブラザー工業株式会社 ネットワークシステムとネットワークデバイス
US8898277B2 (en) * 2007-06-08 2014-11-25 Oracle International Corporation Performance monitoring infrastructure for distributed transaction service
US9137093B1 (en) * 2007-07-02 2015-09-15 Comscore, Inc. Analyzing requests for data made by users that subscribe to a provider of network connectivity
DE602007010841D1 (de) * 2007-07-23 2011-01-05 Ericsson Telefon Ab L M Verfahren und vorrichtung zur verwendung in einem kommunikationsnetz
DE602007010990D1 (de) * 2007-07-23 2011-01-13 Ericsson Telefon Ab L M Verfahren und vorrichtung zur verwendung in einem kommunikationsnetz
US7962649B2 (en) * 2007-10-05 2011-06-14 Cisco Technology, Inc. Modem prioritization and registration
US8239422B2 (en) 2007-10-18 2012-08-07 At&T Intellectual Property I, Lp Methods and apparatus to provision network resource records
US20090248841A1 (en) * 2008-03-28 2009-10-01 Motorola, Inc. Unique prefix assignment with automatic address configuration
TW201039593A (en) * 2009-04-30 2010-11-01 Vivotek Inc DDNS system and auto-registering method
FR2949634B1 (fr) * 2009-09-02 2012-12-28 Alcatel Lucent Procede de notification dans un reseau de communication sans fil
US7965630B1 (en) 2009-09-08 2011-06-21 Southern Company Services, Inc. Load balancing port proxy for dynamically controlling routing of query requests
US8683567B2 (en) 2011-03-31 2014-03-25 Belkin International, Inc. Method of distributing information regarding one or more electrical devices and system for the same
EP2728809B1 (fr) * 2011-06-30 2017-04-26 Mitsubishi Electric Corporation Système de distribution d'adresse ip
US8510807B1 (en) 2011-08-16 2013-08-13 Edgecast Networks, Inc. Real-time granular statistical reporting for distributed platforms
US8972542B2 (en) * 2011-12-22 2015-03-03 International Business Machines Corporation Extending a DHCP relay to backup a DHCP server
US9736005B2 (en) 2011-12-22 2017-08-15 International Business Machines Corporation Duplicate IP address detection by a DHCP relay agent
US9444779B2 (en) 2012-06-04 2016-09-13 Microsoft Technology Lincensing, LLC Dynamic and intelligent DNS routing with subzones
US9680790B2 (en) 2013-08-29 2017-06-13 Mastercard International Incorporated Systems and methods for resolving data inconsistencies between domain name systems
US10908937B2 (en) * 2013-11-11 2021-02-02 Amazon Technologies, Inc. Automatic directory join for virtual machine instances
US9430267B2 (en) * 2014-09-30 2016-08-30 International Business Machines Corporation Multi-site disaster recovery consistency group for heterogeneous systems
US9703646B2 (en) * 2015-07-20 2017-07-11 Bank Of America Corporation Centralized database system
CN106612196B (zh) 2015-10-23 2019-02-01 华为技术有限公司 获取资源的方法及装置
US10129395B1 (en) 2017-10-26 2018-11-13 Sorenson Ip Holdings Llc Systems and related methods for visual indication of callee ID information for an incoming communication request in a hearing-impaired environment
US11240027B2 (en) * 2019-02-04 2022-02-01 Hewlett Packard Enterprise Development Lp Synchronizing radius server databases using distributed ledger network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5581552A (en) * 1995-05-23 1996-12-03 At&T Multimedia server
US5651006A (en) * 1994-06-14 1997-07-22 Hitachi, Ltd. Hierarchical network management system
US5652908A (en) * 1991-10-02 1997-07-29 International Business Machines Corporation Method and apparatus for establishing communications sessions in a remote resource control environment

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4949248A (en) * 1988-07-15 1990-08-14 Caro Marshall A System for shared remote access of multiple application programs executing in one or more computers
US5287343A (en) * 1991-02-25 1994-02-15 Matsushita Electric Works, Ltd. Network administration system
US5287461A (en) * 1991-10-31 1994-02-15 Sun Microsystems, Inc. Method and apparatus for remotely accessing a plurality of server consoles
US5600797A (en) * 1993-11-24 1997-02-04 Intel Corporation System for identifying new client and allocating bandwidth thereto by monitoring transmission of message received periodically from client computers informing of their current status
US5586304A (en) * 1994-09-08 1996-12-17 Compaq Computer Corporation Automatic computer upgrading
US6076107A (en) * 1995-05-09 2000-06-13 International Business Machines Corporation Method for reducing SNMP instrumentation message flows
US5748896A (en) * 1995-12-27 1998-05-05 Apple Computer, Inc. Remote network administration methods and apparatus
US5774660A (en) * 1996-08-05 1998-06-30 Resonate, Inc. World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network
US5996010A (en) * 1996-08-29 1999-11-30 Nortel Networks Corporation Method of performing a network management transaction using a web-capable agent
US5909549A (en) * 1996-11-12 1999-06-01 International Business Machines Corporation Network management system wherein the managed device reestablishes a connection to a management station after detecting a broken connection
US6006264A (en) * 1997-08-01 1999-12-21 Arrowpoint Communications, Inc. Method and system for directing a flow between a client and a server

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5652908A (en) * 1991-10-02 1997-07-29 International Business Machines Corporation Method and apparatus for establishing communications sessions in a remote resource control environment
US5651006A (en) * 1994-06-14 1997-07-22 Hitachi, Ltd. Hierarchical network management system
US5581552A (en) * 1995-05-23 1996-12-03 At&T Multimedia server

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
A.S. TANENBAUM: "Computer Networks" 1996 , PRENTICE-HALL, INC. , NEW JERSEY, US XP002138500 394248 page 630, line 15 -page 633, line 4 *
CHUL-JIN PARK ET AL: "The improvement for integrity between DHCP and DNS" PROCEEDINGS. HIGH PERFORMANCE COMPUTING ON THE INFORMATION SUPERHIGHWAY,XX,XX, 28 April 1997 (1997-04-28), pages 511-516-516, XP002110636 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002005510A1 (fr) * 2000-07-11 2002-01-17 Nokia Corporation Procede permettant de fournir une liste d'adresses de serveurs dns d'un serveur a un client
US7734683B1 (en) 2000-07-11 2010-06-08 Nokia Corporation Method for providing a DNS server address list from a server to a client
US6920506B2 (en) 2001-06-28 2005-07-19 Canon Information Systems, Inc. Discovery and management of network printers
US7454482B2 (en) 2001-06-28 2008-11-18 Canon Information Systems, Inc. Print queue manager
JP2005521635A (ja) * 2001-10-10 2005-07-21 ネオス・テクノロジーズ・インコーポレーテツド ペプチドの改造および複合糖質化
JP2009108087A (ja) * 2001-10-10 2009-05-21 Neose Technologies Inc ペプチドの改造および複合糖質化
WO2005106701A2 (fr) 2004-04-16 2005-11-10 Infoblox, Inc. Maintien de l'integrite des donnees dans un environnement reparti
EP1738282A2 (fr) * 2004-04-16 2007-01-03 Infoblox Inc. Maintien de l'integrite des donnees dans un environnement reparti
EP1738282A4 (fr) * 2004-04-16 2007-07-04 Infoblox Inc Maintien de l'integrite des donnees dans un environnement reparti
US8498971B2 (en) 2004-04-16 2013-07-30 Infoblox Inc. Maintaining consistency in a database
EP3107248A4 (fr) * 2014-02-12 2017-10-18 Nec Corporation Dispositif de traitement d'informations, procédé de communication, dispositif et procédé de commande de réseau, système de communication et programme

Also Published As

Publication number Publication date
US6374295B2 (en) 2002-04-16
AU6484899A (en) 2000-05-22
WO2000026807A3 (fr) 2000-08-31
US20020010767A1 (en) 2002-01-24

Similar Documents

Publication Publication Date Title
US6374295B2 (en) Active server management
US6564216B2 (en) Server manager
US6654891B1 (en) Trusted network binding using LDAP (lightweight directory access protocol)
US9154557B2 (en) Automatic proxy registration and discovery in a multi-proxy communication system
US6427170B1 (en) Integrated IP address management
EP1079583B1 (fr) Procédé et système pour optimiser le rendement et la disponibilité d'un service DHCP
US6292838B1 (en) Technique for automatic remote media access control (MAC) layer address resolution
US7185079B1 (en) Automated management of network addresses in a broadband managed access environment
EP1125421B1 (fr) Module de relais dns dans un modem de reseau numerique
US20050108432A1 (en) Automatic address management method
US6470389B1 (en) Hosting a network service on a cluster of servers using a single-address image
EP0998099B1 (fr) Gestion d'adresse réseau
US7991856B2 (en) Network system
JP2000209231A (ja) デバイス初期化方法，ネットワ―ク情報の自動割り当て方法，ネットワ―ク自動初期化方法，サ―ビス自動発見方法およびネットワ―ク
JP2004266305A (ja) 動的ｉｐアドレス割当てを受けた機器を管理する方法およびシステム
JPH11341053A (ja) サ―ビス品質割当の方法および機構
US7848258B2 (en) Dynamically transitioning static network addresses
EP0918412A2 (fr) Découverte automatique des dispositifs liés à un réseau
CN100461693C (zh) 网络系统
Cisco Glossary
Cisco Chapter 2: Cisco ACNS Software Commands
Cisco Routing AppleTalk
Cisco Using the nrcmd Commands
Cisco Routing AppleTalk
Lee et al. Scaling the number of DNS root servers with Internet

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 1999 64848

Country of ref document: AU

Kind code of ref document: A

AK Designated states

Kind code of ref document: A2

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM 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 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 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)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM 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 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: A3

Designated state(s): GH GM KE LS MW 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

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
WWE Wipo information: entry into national phase

Ref document number: 2005019

Country of ref document: LT