IP Library Granted Patent US 7,451,071
Granted Patent B2
US 7,451,071 · App. 09/766,615 · Granted Nov 11, 2008

Data model for automated server configuration

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,451,071
App. No.
09/766,615
Granted
Nov 11, 2008
Kind
B2
Abstract

The present invention is directed to a data model. The data model allows for modeling of all information relating to a computer network to be conveniently stored in a database in a manner which minimizes the effort associated with the addition of new devices to the network and maximizes software code reuse. The information relating to the network that may be modeled in the data model of the present invention include: software information, configuration information, monitoring information, hardware information, domain name server (DNS) information, network information, and information regarding queues that may be used by business logic, or intelligent agents in accessing and maintaining various portions of the network.

Claims (47)

1. A provisioning method employing a DNS data model for relating DNS objects of a computer network to other DNS objects, and for expressing the software objects of a computer network in a form accessible by other network components, the method comprising:

configuring a central database to be able to implement the DNS data model, the DNS data model including:

DNS domains entities that represent DNS domains of devices connected to a computer network and are related to various entities representing DNS permissions and types selected from the group consisting of DNS ACLs entities, DNS ACL entries entities, DNS allow transfers entities, DNS allow queries entities, DNS domain types entities, DNS domain masters entities, and DNS master IPs entities; and

DNS hosts entities that represent various DNS hosts connected to the computer network; and

automatically provisioning the computer network according to the DNS data model.

2. The method of claim 1 , wherein said DNS domains entities represent the DNS domains of one or more DNS hosts represented by said DNS hosts entities.

3. A provisioning method employing a DNS data model for relating DNS entities of a computer network to other DNS entities of the computer network, and for expressing the DNS entities in a form accessible by other network components, the method comprising:

configuring a central database to be able to implement the DNS data model, the DNS data model including:

a plurality of devices entities;

a plurality of DNS hosts entities;

a plurality of DNS host types entities;

a plurality of DNS ACLs entities;

a plurality of DNS ACL entries entities;

a plurality of DNS allow transfers entities;

a plurality of DNS domain types entities;

a plurality of DNS domains entities;

a plurality of DNS allow queries;

a plurality of DNS domain masters entities; and

a plurality of DNS master IPs; and

automatically provisioning the computer network according to the DNS data model.

4. The method of claim 3 , further comprising a plurality of DNS configuration entities.

5. The method of claim 3 , wherein said DNS hosts entities represent DNS host devices, and wherein said DNS hosts entities relate to:

said DNS host types entities by a many-to-one relationship;

said DNS domains entities by a many-to-one relationship; and

a plurality of configuration entities by an optional one-to-many relationship.

6. The method of claim 3 , wherein said DNS host types entities represent allowed DNS host types, and wherein said DNS host types entities relate to said DNS hosts entities in a one-to-many relationship.

7. The method of claim 3 , wherein said DNS ACLs entities represent ACLs associated with specific DNS names, and wherein said DNS ACLs entities relate to:

said DNS ACL entries entities by a one-to-many relationship;

said DNS allow transfers entities by a one-to-many relationship; and

said DNS allow queries entities by a one-to-many relationship.

8. The method of claim 3 , wherein said DNS ACL entries entities relate to said DNS ACLs entities by a many-to-one relationship.

9. The method of claim 3 , wherein said DNS allow transfers entities relate to:

said DNS ACLs entities by a many-to-one relationship; and

said DNS domains entities by a many-to-one relationship.

10. The method of claim 3 , wherein said DNS domain types entities represent the allowed types of DNS names for the network, and wherein said DNS domain types entities relate to said DNS domains entities by a one-to-many relationship.

11. The method of claim 3 , wherein said DNS domains entities represent the various DNS domains of the network, and wherein said DNS domains entities relate to:

said DNS hosts entities by a one-to-many relationship;

said DNS allow transfers entities by a one-to-many relationship;

said DNS allow queries entities by a one-to-many relationship;

said DNS domain types entities by a many-to-one relationship;

said DNS domain masters entities by a many-to-one relationship; and

a plurality of network entities by an optional many-to-one relationship.

12. The method of claim 3 , wherein said DNS allow queries entities represent specific DNS queries allowed on the network, and wherein said DNS allow queries entities relate to:

said DNS domains entities by a many-to-one relationship; and

said DNS ACLs entities by a many-to-one relationship.

13. The method of claim 3 , wherein said DNS domain masters entities relate DNS domains represented by said DNS domains entities and DNS master IPs represented by DNS master IPs entities by way of a one-to-many relationship with said DNS domains entities and a many-to-one relationship with said DNS master IPs entities.

14. The method of claim 3 , wherein said DNS master IPs entities relate to DNS master IP addresses of the network, and relate to said DNS domain masters entities by a one-to-many relationship.

Assignments (7)
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC)
Reel/Frame 063560/0001 →
CHANGE OF NAME Recorded Aug 8, 2019
From: ENTIT SOFTWARE LLC
To: MICRO FOCUS LLC
Reel/Frame 050004/0001 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ENTIT SOFTWARE LLC; ARCSIGHT, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0577 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2017
From: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
To: ENTIT SOFTWARE LLC
Reel/Frame 042746/0130 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2015
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 037079/0001 →