Method for implementing a server-based, common communication identifier for multiple communication applications

• US 20030070093A1
• Filed: 10/10/2001
• Published: 04/10/2003
• Est. Priority Date: 10/10/2001
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hayes, Bernard J.
• Application Number:
  US09/974,429
• Publication Number:
  US 20030070093A1
• Time in Patent Office: Days
• US Class Current: 713/201
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof

Abstract

A method for implementing a server-based, common communication identifier for use with multiple communication applications is disclosed. In an exemplary embodiment of the invention, the method includes configuring a server-based repository for storing individual communication location records therein, with each of the individual communication location records corresponding to individual owners thereof. The individual communication location records containing one or more communication location record (CLR) fields therein, with each of the CLR fields corresponding to a specific communication medium by which a particular owner may be contacted. A CLR identifier is assigned for each owner having an individual communication location record stored in said repository. Thereby, a selected CLR field for a given owner is individually accessed by presenting the CLR identifier corresponding to the given owner, along with a CLR field identifier corresponding to the selected CLR field, to the server-based repository.

Claims

1. A method for implementing a server-based, common communication identifier for use with multiple communication applications, the method comprising:

configuring a server-based repository for storing individual communication location records therein, each of said individual communication location records corresponding to individual owners thereof;

said individual communication location records further containing one or more communication location record (CLR) fields therein, each of said CLR fields corresponding to a specific communication medium by which a particular one of said individual owners may be contacted; and

assigning a CLR identifier for each owner having an individual communication location record stored in said repository;

wherein a selected CLR field for a given owner is individually accessed by presenting the CLR identifier corresponding to said given owner, along with a CLR field identifier corresponding to said selected CLR field, to said server-based repository.

2. The method of claim 1, further comprising:

designating a public/private status for each of said CLR fields, said public/private status for a given CLR field being determined by the individual owner of said communication location record containing said given CLR field;

wherein, if said public/private status for said given CLR field is public, then access to said given CLR field is not restricted; and

if said public/private status for said given CLR field is private, then access to said given CLR field is restricted to individuals authorized by said individual owner.

3. The method of claim 2, further comprising:

configuring an access list for each CLR field designated as private, said access list including the individuals authorized to access the corresponding CLR field.

4. The method of claim 3, wherein:

a request from a user for access to a selected CLR field for a selected owner is processed by a server that controls said server-based repository; and

said server further receiving, as part of said request for access;

the CLR identifier corresponding to said selected owner;

the CLR field identifier corresponding to said selected CLR field; and

a CLR identifier corresponding to said user.

5. The method of claim 4, wherein:

said server examines the public/private status of said selected CLR field, and

if said public/private status for said selected CLR field is public, then said server allows said user to access information contained in said selected CLR field, regardless of the identity of the CLR identifier corresponding to said user;

if said public/private status for said selected CLR field is private, then said server compares the CLR identifier of said user to said access list for said selected CLR field;

then

if said access list includes the CLR identifier of said user, then said server allows said user to access information contained in said selected CLR field; and

if said access list does not include the CLR identifier of said user, then said server does not allow said user to access information contained in said selected CLR field.

6. The method of claim 5, wherein said CLR identifier contains a server address therein, said server address corresponding to a location in said server-based repository where the communication location record identified by said CLR identifier is stored.

7. A common communication identifier system for use with multiple communication applications, the system comprising:

a server-based repository for storing individual communication location records therein, each of said individual communication location records corresponding to individual owners thereof;

said individual communication location records further containing one or more communication location record (CLR) fields therein, each of said CLR fields corresponding to a specific communication medium by which a particular one of said individual owners may be contacted; and

a CLR identifier assigned for each owner having an individual communication location record stored in said repository;

wherein a selected CLR field for a given owner is individually accessed by presenting the CLR identifier corresponding to said given owner, along with a CLR field identifier corresponding to said selected CLR field, to said server-based repository.

8. The system of claim 7, further comprising:

a public/private status designated for each of said CLR fields, said public/private status for a given CLR field being determined by the individual owner of said communication location record containing said given CLR field;

wherein, if said public/private status for said given CLR field is public, then access to said given CLR field is not restricted; and

if said public/private status for said given CLR field is private, then access to said given CLR field is restricted to individuals authorized by said individual owner.

9. The system of claim 8, further comprising:

an access list configured for each CLR field designated as private, said access list including the individuals authorized to access the corresponding CLR field.

10. The system of claim 9, wherein:

a request from a user for access to a selected CLR field for a selected owner is processed by a server that controls said server-based repository; and

said server further receiving, as part of said request for access;

the CLR identifier corresponding to said selected owner;

the CLR field identifier corresponding to said selected CLR field; and

a CLR identifier corresponding to said user.

11. The system of claim 10, wherein:

said server examines the public/private status of said selected CLR field, and

if said public/private status for said selected CLR field is public, then said server allows said user to access information contained in said selected CLR field, regardless of the identity of the CLR identifier corresponding to said user;

if said public/private status for said selected CLR field is private, then said server compares the CLR identifier of said user to said access list for said selected CLR field;

then

if said access list includes the CLR identifier of said user, then said server allows said user to access information contained in said selected CLR field; and

if said access list does not include the CLR identifier of said user, then said server does not allow said user to access information contained in said selected CLR field.

12. The system of claim 11, wherein said CLR identifier contains a server address therein, said server address corresponding to a location in said server-based repository where the communication location record identified by said CLR identifier is stored.

13. A storage medium encoded with a machine readable computer program code for implementing a server-based, common communication identifier for use with multiple communication applications, the storage medium including instructions for causing a computer to implement a method, the method comprising:

configuring a server-based repository for storing individual communication location records therein, each of said individual communication location records corresponding to individual owners thereof;

said individual communication location records further containing one or more communication location record (CLR) fields therein, each of said CLR fields corresponding to a specific communication medium by which a particular one of said individual owners may be contacted; and

assigning a CLR identifier for each owner having an individual communication location record stored in said repository;

wherein a selected CLR field for a given owner is individually accessed by presenting the CLR identifier corresponding to said given owner, along with a CLR field identifier corresponding to said selected CLR field, to said server-based repository.

14. The storage medium of claim 13, further comprising:

designating a public/private status for each of said CLR fields, said public/private status for a given CLR field being determined by the individual owner of said communication location record containing said given CLR field;

wherein, if said public/private status for said given CLR field is public, then access to said given CLR field is not restricted; and

if said public/private status for said given CLR field is private, then access to said given CLR field is restricted to individuals authorized by said individual owner.

15. The storage medium of claim 14, further comprising:

configuring an access list for each CLR field designated as private, said access list including the individuals authorized to access the corresponding CLR field.

16. The storage medium of claim 15, wherein:

a request from a user for access to a selected CLR field for a selected owner is processed by a server that controls said server-based repository; and

said server further receiving, as part of said request for access;

the CLR identifier corresponding to said selected owner;

the CLR field identifier corresponding to said selected CLR field; and

a CLR identifier corresponding to said user.

17. The storage medium of claim 16, wherein:

said server examines the public/private status of said selected CLR field, and

if said public/private status for said selected CLR field is public, then said server allows said user to access information contained in said selected CLR field, regardless of the identity of the CLR identifier corresponding to said user;

if said public/private status for said selected CLR field is private, then said server compares the CLR identifier of said user to said access list for said selected CLR field;

then

if said access list includes the CLR identifier of said user, then said server allows said user to access information contained in said selected CLR field; and

if said access list does not include the CLR identifier of said user, then said server does not allow said user to access information contained in said selected CLR field.

18. The storage medium of claim 17, wherein said CLR identifier contains a server address therein, said server address corresponding to a location in said server-based repository where the communication location record identified by said CLR identifier is stored.

19. A computer data signal for implementing a server-based, common communication identifier for use with multiple communication applications, the computer data signal comprising code configured to cause a processor to implement a method, the method comprising:

configuring a server-based repository for storing individual communication location records therein, each of said individual communication location records corresponding to individual owners thereof;

said individual communication location records further containing one or more communication location record (CLR) fields therein, each of said CLR fields corresponding to a specific communication medium by which a particular one of said individual owners may be contacted; and

assigning a CLR identifier for each owner having an individual communication location record stored in said repository;

wherein a selected CLR field for a given owner is individually accessed by presenting the CLR identifier corresponding to said given owner, along with a CLR field identifier corresponding to said selected CLR field, to said server-based repository.

20. The computer data signal of claim 19, further comprising:

designating a public/private status for each of said CLR fields, said public/private status for a given CLR field being determined by the individual owner of said communication location record containing said given CLR field;

wherein, if said public/private status for said given CLR field is public, then access to said given CLR field is not restricted; and

if said public/private status for said given CLR field is private, then access to said given CLR field is restricted to individuals authorized by said individual owner.

21. The computer data signal of claim 20, further comprising:

configuring an access list for each CLR field designated as private, said access list including the individuals authorized to access the corresponding CLR field.

22. The computer data signal of claim 21, wherein:

a request from a user for access to a selected CLR field for a selected owner is processed by a server that controls said server-based repository; and

said server further receiving, as part of said request for access;

the CLR identifier corresponding to said selected owner;

the CLR field identifier corresponding to said selected CLR field; and

a CLR identifier corresponding to said user.

23. The computer data signal of claim 22, wherein:

said server examines the public/private status of said selected CLR field, and

if said public/private status for said selected CLR field is public, then said server allows said user to access information contained in said selected CLR field, regardless of the identity of the CLR identifier corresponding to said user;

if said public/private status for said selected CLR field is private, then said server compares the CLR identifier of said user to said access list for said selected CLR field;

then

if said access list includes the CLR identifier of said user, then said server allows said user to access information contained in said selected CLR field; and

if said access list does not include the CLR identifier of said user, then said server does not allow said user to access information contained in said selected CLR field.

24. The computer data signal of claim 23, wherein said CLR identifier contains a server address therein, said server address corresponding to a location in said server-based repository where the communication location record identified by said CLR identifier is stored.