Cross-domain entity relationship model for managing data related to communications products

• US 20040260705A1
• Filed: 06/23/2003
• Published: 12/23/2004
• Est. Priority Date: 06/23/2003
• Status: Abandoned Application

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Inventors: Roman, Pamela Dooley
• Application Number:
  US10/602,250
• Publication Number:
  US 20040260705A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

An embodiment of the invention is a method of managing data related to communications products. The method includes defining a contract domain including a contract entity having attributes of an agreement between a customer and a provider of a communications product. A product domain is defined including a product entity having attributes, of the communications product. A location domain is defined including a location entity having attributes of a geographic location. An account receivables domain is defined including an account entity having attributes of a customer account. A customer domain is defined including a party entity having attributes of a party. Within the customer domain, a contract instance of the contract entity, a product instance of the product entity, a location instance of the location entity and an account instance of the account entity are defined.

Claims

1. A method of establishing data domains and cross-domain relationships for managing data related to communications products, the method comprising:

defining a contract domain including a contract entity having attributes of an agreement between a customer and a provider of a communications product;

defining a product domain including a product entity having attributes of the communications product;

defining a location domain including a location entity having attributes of a geographic location;

defining an account receivables domain including an account entity having attributes of a customer account;

defining a customer domain including a party entity having attributes of a party;

defining within said customer domain a contract instance of said contract entity, a product instance of said product entity, a location instance of said location entity and an account instance of said account entity;

wherein an entity in one of said contract domain, product domain, location domain, account receivables domain and customer domain is directly related to another entity in another one of said contract domain, product domain, location domain, account receivables domain and customer domain.

2. The method of claim 1 wherein:

said contract entity is directly related to said product entity.

3. The method of claim 1 wherein:

said contract domain includes a terms and conditions entity having attributes of the terms and conditions of a contract;

said terms and conditions entity is directly related to said product entity.

4. The method of claim 3 further comprising:

defining within said customer domain a terms and conditions instance of said terms and conditions entity.

5. The method of claim 1 wherein:

said contract domain includes an outcome entity having attributes of the outcome of a contract;

said outcome entity is directly related to said product entity.

6. The method of claim 5 further comprising:

defining within said customer domain an outcome instance of said outcome entity.

7. A cross-domain data model for managing data related to communications products, the cross-domain data model comprising:

a contract domain including a contract entity having attributes of an agreement between a customer and a provider of a communications product;

a product domain including a product entity having attributes of the communications product;

a location domain including a location entity having attributes of a geographic location;

an account receivables domain including an account entity having attributes of a customer account;

a customer domain including a party entity having attributes of a party, within said customer domain a contract instance of said contract entity, a product instance of said product entity, a location instance of said location entity and an account instance of said account entity;

wherein an entity in one of said contract domain, product domain, location domain, account receivables domain and customer domain is directly related to another entity in another one of said contract domain, product domain, location domain, account receivables domain and customer domain.

8. The cross-domain data model of claim 7 wherein:

said contract entity is directly related to said product entity.

9. The cross-domain data model of claim 7 wherein:

said contract domain includes a terms and conditions entity having attributes of the terms and conditions of a contract;

said terms and conditions entity is directly related to said product entity.

10. The cross-domain data model of claim 9 further comprising:

within said customer domain a terms and conditions instance of said terms and conditions entity.

11. The cross-domain data model of claim 7 wherein:

said contract domain includes an outcome entity having attributes of the outcome of a contract;

said outcome entity is directly related to said product entity.

12. The cross-domain data model of claim 11 further comprising:

within said customer domain an outcome instance of said outcome entity.