Electrical computers and digital processing systems: support – Multiple computer communication using cryptography – Protection at a particular protocol layer
Reexamination Certificate
1998-10-29
2003-11-25
Hua, Ly V. (Department: 2131)
Electrical computers and digital processing systems: support
Multiple computer communication using cryptography
Protection at a particular protocol layer
C713S152000, C370S352000, C370S242000
Reexamination Certificate
active
06654891
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates in general to information networking and more particulary to transmitting configuration information between a central database and one or more servers in a network.
2. Description of the Related Art
In a typical network, a server directly communicates with the central database in order to obtain configuration information.
FIG. 1
illustrates an overall diagram of a conventional Transmission Control Protocol (TCP)/Intemet 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
. Typically, 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.
In the past, organizations relied on paper based methods of managing IP addresses in a network. DHCP simplified the management and assignment of IP addresses to clients by eliminating the need for the network administrator to manually configure the network. With 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. Along with the ability to dynamically assign IP addresses, 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.
In mid-to large-scale networks, a significant number of transmissions between the central database
104
and the DNS servers
102
A-N and DHCP servers
103
A-N occur. Each DNS server
102
A-N and DHCP server
103
A-N must individually contact the central database
104
to obtain any configuration changes made to the network that were stored in the central database
104
. If there are a large number of DNS servers
102
A-N and DHCP servers
103
A-N, for example
100
, on the network, a bandwidth issue is created at the central database
104
.
Therefore, it would be useful to provide an improved means of communicating between a database and one or more servers.
SUMMARY OF THE INVENTION
A method and apparatus for providing information between a central database and at least one server. A server manager is coupled between the central database and the at least one server. The server manager communicates configuration information between the central database and the at least one server in a single communication channel.
REFERENCES:
patent: 5553234 (1996-09-01), Cotner et al.
patent: 5689633 (1997-11-01), Cotner et al.
patent: 5768519 (1998-06-01), Swift et al.
patent: 5790677 (1998-08-01), Fox et al.
patent: 5812819 (1998-09-01), Rodwin et al.
patent: 5850442 (1998-12-01), Muftic
patent: 5884024 (1999-03-01), Lim et al.
patent: 5923756 (1999-07-01), Shambroom
patent: 6006018 (1999-12-01), Burnett et al.
patent: 6009103 (1999-12-01), Woundy
patent: 6023464 (2000-02-01), Woundy
patent: 6026445 (2000-02-01), Kephart et al.
patent: 6070242 (2000-05-01), Wong et al.
patent: 6131164 (2000-10-01), Parker
patent: 6351536 (2002-02-01), Sasaki
patent: 6460141 (2002-10-01), Olden
M. Wahl, “A Summary of the X.500(96) User Schema for use with LDAPv3”, Dec. 1, 1997. pp. 1-38.
M. Wahl, et al., “Lightweight Directory Access Protocol (v3)”, Dec. 1997, 59 pages.
R. Droms, “Authentication for DHCP Messages”, Nov. 1996, 10 pages.
P. Vixie, et al. Dynamic Updates in the Domain Name System (DNS Update), Apr. 1997.
Anderson Rod
Borsato Larry W.
Gaudet Mark
Hamilton Ian
Waters Glenn
LandOfFree
Trusted network binding using LDAP (lightweight directory... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Trusted network binding using LDAP (lightweight directory..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Trusted network binding using LDAP (lightweight directory... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3173558