SYSTEM FOR MAINTAINING TYPE AND/OR STATUS INFORMATION FOR A PARTY - COMMUNICATION POINT RELATIONSHIP

• US 20070237315A1
• Filed: 06/06/2007
• Published: 10/11/2007
• Est. Priority Date: 02/24/2004
• Status: Abandoned Application

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Grear, Michael, Donlin, Gretchen, Melanson, Patricia, Henry-Saal, Margaret
• Application Number:
  US11/759,191
• Publication Number:
  US 20070237315A1
• Time in Patent Office: Days
• US Class Current: 379/100.150
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1457 using an account
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 67/306 User profiles

Abstract

According to one embodiment of the invention, a system is provided that comprises a communication point database configured to provide a communication point data set; a party database configured to provide a party data set; wherein the communication point database and the party database are communicatively coupled with one another so as to associate the communication point data set with the party data set; a relationship type code database communicatively coupled with the communication point data set and the party data set.

Claims

1. A method of managing communication point data, said method comprising:

providing a communication point data set;

providing a party data set;

associating said communication point data set with said party data set;

associating a relationship type code with said communication point data set and said party data set.

2. The method as claimed in claim 1 and further comprising:

providing a communication point data set identifier;

providing a party data set identifier; and

wherein said associating said communication point data set with said party data set comprises;

associating said communication point data set identifier with said party data set identifier.

3. The method as claimed in claim 1 and further comprising:

providing a communication point data set identifier;

providing a party data set identifier; and

wherein said associating said communication point data set with said party data set comprises;

associating said communication point data set identifier with said party data set identifier;

said method further comprising;

providing a relationship type code identifier; and

wherein said associating said relationship type code with said communication point data set and said party data set comprises;

associating said relationship type code identifier with said communication point data set identifier and said party data set identifier.

4. The method as claimed in claim 1 and further comprising:

providing a relationship type code database.

5. The method as claimed in claim 1 and further comprising:

providing a relationship status code.

6. The method as claimed in claim 1 and further comprising:

providing a relationship status code database; and

storing a relationship status code in said relationship status code database.

7. The method as claimed in claim 6 and further comprising:

providing a relationship status code identifier;

associating said relationship status code identifier with said relationship status code.

8. The method as claimed in claim 3 and further comprising:

providing a relationship status code identifier; and

associating said relationship status code identifier with said relationship type code identifier and said communication point data set identifier and said party data set identifier.

9. The method as claimed in claim 4 wherein said providing said relationship type code database comprises:

providing a static list of different relationship type codes in said database.

10. The method as claimed in claim 9 wherein said list is established by a data processor entity.

11. The method as claimed in claim 9 wherein said list is established by a service provider.

12. The method as claimed in claim 9 wherein said relationship type code is provided by a customer so as to depict the relationship between the customer and the communication point.

13. The method as claimed in claim 12 wherein said relationship type code indicates that said communication point data set represents the home of said party identified by said party data set.

14. The method as claimed in claim 12 wherein said relationship type code indicates that said communication point data set represents the employment address for said party identified by said party data set.

15. A system for managing communication point data, said system comprising:

a communication point database configured to provide a communication point data set;

a party database configured to provide a party data set;

wherein said communication point database and said party database are communicatively coupled with one another so as to associate said communication point data set with said party data set;

a relationship type code database communicatively coupled with said communication point data set and said party data set.

16. The apparatus as claimed in claim 15

wherein said communication point database is configured to provide a communication point data set identifier;

and

wherein said party database is configured to provide a party data set identifier; and

wherein said association between said communication point data set and said party data set comprises an association between said communication point data set identifier and said party data set identifier.

17. The apparatus as claimed in claim 15

wherein said communication point database is configured to provide a communication point data set identifier;

and

wherein said party database is configured to provide a party data set identifier; and

wherein said association between said communication point data set and said party data set comprises an association between said communication point data set identifier and said party data set identifier; and

wherein said relationship type code database is configured to provide a relationship type code identifier.

18. The apparatus as claimed in claim 17 and wherein said communicative coupling of said relationship type code database with said communication point data set and said party data set comprises associating said relationship type code identifier with said communication point data set identifier and said party data set identifier.

19. The apparatus as claimed in claim 15 and further comprising:

a relationship status code.

20. The apparatus as claimed in claim 15 and further comprising:

a relationship status code database configured to store a relationship status code.

21. The apparatus as claimed in claim 20 wherein said relationship status code database is configured to store a relationship status code identifier associated with said relationship status code.

22. The apparatus as claimed in claim 17 and further comprising:

a relationship status code database configured to store a relationship status code identifier for association with said relationship type code identifier.

23. The apparatus as claimed in claim 18 said relationship type code database is configured to provide a static list of different relationship type codes.

24. The apparatus as claimed in claim 23 wherein said static list is established by a data processor entity.

25. The apparatus as claimed in claim 23 wherein said static list is established by a service provider.

26. The apparatus as claimed in claim 23 wherein said relationship type code is provided by a customer so as to depict the relationship between the customer and the communication point.

27. The apparatus as claimed in claim 26 wherein said relationship type code indicates that said communication point data set represents the home of said party identified by said party data set.

28. The apparatus as claimed in claim 26 wherein said relationship type code indicates that said communication point data set represents the employment address for said party identified by said party data set.