List management server for managing updating of list by third-party terminal, list management system, list managing method, and program

• US 7,814,120 B2
• Filed: 01/04/2006
• Issued: 10/12/2010
• Est. Priority Date: 01/06/2005
• Status: Expired due to Fees

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Ito, Naoko, Watanabe, Masafumi, Tsutazawa, Natsuko
• Primary Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US11/324,343
• Publication Number:
  US 20060149740A1
• Time in Patent Office: 1,742 Days
• Field of Search: 707 1- 2, 707/9, 707/10, 707/100, 707102-103 R, 707/200, 707/203, 707204-205, 707/609, 707705-709, 707/732, 707781-789, 707826-827, 709218-225, 713/153, 705/1, 705/26, 715743-747
• US Class Current: 707/783
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]

Abstract

A buddy list manager stores a buddy list sent from a receiver terminal and manages the buddy list. A controller accepts an updating request and identifying information of a third party terminal from the third party terminal. When the controller accepts the updating request and the identifying information from the third party terminal, the controller determines whether the third party has an updating authority for updating the buddy list or not, using the identifying information. If the controller judges that the third party has an updating authority for updating the buddy list, then the controller permits the third party terminal to update the buddy list.

Claims

1. A list management server for adding or deleting an information provider terminal, which is monitored by a receiver terminal, in a buddy list that is used to distribute information from said information provider terminal to said receiver terminal, based on an updating request sent through a communication link from a third party terminal which is different from both said receiver terminal and an administrator terminal of an administrator of said buddy list, said server comprising:

a list storage unit for storing said buddy list; and

a controller for accepting said updating request from said third party terminal and identifying information for identifying a user of said third party terminal, determining whether said user has an updating authority to update said buddy list or not, using said identifying information, and, if said controller judges that said user has an updating authority to update said buddy list, permitting said third party terminal to add or delete said information provider terminal in or from said buddy list, said controller comprising;

an authority storage unit for storing specifying information for specifying an authority holder that has an updating authority for updating the buddy list stored in said list storage unit, wherein said authority storage unit stores first specifying information indicating whether each user that is capable of using said list management server has the updating authority for updating said buddy list, second specifying information for specifying an authority holder having an updating authority for updating each of buddy lists, and third specifying information for specifying an authority holder having an updating authority for updating each of information provider terminals indicated by said buddy list; and

an updating permission unit for accepting said updating request and said identifying information from said third party terminal, determining whether said user has said updating authority or not based on said identifying information and the specifying information stored in said authority storage unit, and permitting said third party terminal to add or delete said information provider terminal in or from said buddy list if said updating permission unit judges that said user has said updating authority, wherein said updating permission unit selects either one of said first specifying information, said second specifying information, and said third specifying information depending on said updating request from said third party terminal.

2. The list management server according to claim 1, wherein said specifying information comprises a condition for specifying said authority holder.

3. The list management server according to claim 1, wherein said specifying information comprises a list for specifying said authority holder.

4. The list management server according to claim 1, wherein said specifying information represents said authority holder.

5. The list management server according to claim 1, wherein said specifying information represents an updating rejected person who is denied adding or deleting said information provider terminal in or from said buddy list.

6. The list management server according to claim 1, wherein said specifying information represents said authority holder and an updating rejected person who is denied adding or deleting said information provider terminal in or from-said buddy list.

7. The list management server according to claim 1, wherein said updating permission unit determines whether said user has the updating authority for updating said buddy list based on the identifying information of the user and the specifying information stored in said authority storage unit, and, if said updating permission unit is unable to determine whether said user has the updating authority for updating said buddy list, said updating permission unit asks an authorized person terminal used by an authorized person having an updating authority for updating said buddy list to inquire if said user is permitted to update said buddy list, accepts an answer to the inquiry, and determines whether said user has the updating authority for updating said buddy list based on said answer.

8. A list managing method to be carried out by a list management server for adding or deleting an information provider terminal, which is monitored by a receiver terminal, to or from a buddy list that is used to distribute information from said information provider terminal to said receiver terminal, based on an updating request sent through a communication link from a third party terminal which is different from both said receiver terminal and an administrator terminal of an administrator of said buddy list, said list management server including a list storage unit for storing said buddy list, and an authority storage unit for storing first specifying information indicating whether each user capable of using said list management server has the updating authority for updating said buddy list, second specifying information for specifying an authority holder having an updating authority for updating each of buddy lists, and third specifying information for specifying an authority holder having an updating authority for updating each of information provider terminals indicated by said buddy list stored in said list storage unit, said list managing method comprising the steps of:

(a) accepting said updating request and identifying information for identifying a user of said third party terminal from said third party terminal, and determining whether said user has an updating authority based on said identifying information and the specifying information stored in said authority storage unit to update said buddy list;

(b) selecting either one of said first specifying information, said second specifying information, and said third specifying information depending on said updating request from said third party terminal; and

(c) if it is judged that said user has an updating authority to add or delete said information provider terminal in or from said buddy list, permitting said third party terminal to update said buddy list.

9. The list managing method according to claim 8, wherein said specifying information comprises a condition for specifying said authority holder.

10. The list managing method according to claim 8, wherein said specifying information comprises a buddy list for specifying said authority holder.

11. The list managing method according to claim 8, wherein said specifying information represents said authority holder.

12. The list managing method according to claim 8, wherein said specifying information represents an updating rejected person who is denied adding or deleting said information provider terminal in or from said buddy list.

13. The list managing method according to claim 8, wherein said specifying information represents said authority holder and an updating rejected person who is denied adding or deleting said information provider terminal to or from said buddy list.

14. The list managing method according to claim 8, further comprising the steps of:

(d) determining whether said user has the updating authority for updating said buddy list based on the identifying information of the user and the specifying information stored in said authority storage unit

(e) if it is impossible to determine whether said user has the updating authority for updating said buddy list, asking an authorized person terminal used by an authorized person having an updating authority for updating said buddy list to inquire if said user is permitted to update said buddy list; and

(f) accepting an answer to the inquiry;

wherein said step (a) further comprises the step of determining whether said user has the updating authority for updating said buddy list based on said answer.

15. A computer readable recording medium in which a program is recorded, said program controlling a computer for adding or deleting an information provider terminal, which is monitored by a receiver terminal, to or from a buddy list that is used to distribute information from said information provider terminal to said receiver terminal, based on an updating request sent through a communication link from a third party terminal which is different from both said receiver terminal and an administrator terminal of an administrator of said buddy list, said computer being connected to a list storage unit for storing said buddy list, and an authority storage unit for storing first specifying information indicating whether each user capable of using said list management server has the updating authority for updating said buddy list, second specifying information for specifying an authority holder having an updating authority for updating each of buddy lists, and third specifying information for specifying an authority holder having an updating authority for updating each of information provider terminals indicated by said buddy list stored in said list storage unit, said program enabling said computer to perform a list management process comprising the steps of:

(a) accepting said updating request and identifying information for identifying a user of said third party terminal from said third party terminal, and determining whether said third party terminal has an updating authority based on said identifying information and the specifying information stored in said authority storage unit to update said buddy list;

(b) selecting either one of said first specifying information, said second specifying information, and said third specifying information depending on said updating request from said third party terminal; and

(c) if it is judged that said user has an updating authority to update said buddy list, permitting said third party terminal to add or delete said information provider terminal in or from said buddy list.

16. The computer readable recording medium of claim 15, wherein the list management process further comprises the steps of:

(d) determining whether said user has the updating authority for updating said buddy list based on the identifying information of the user and the specifying information stored in said authority storage unit;

(e) if it is impossible to determine whether said user has the updating authority for updating said buddy list, asking an authorized person terminal used by an authorized person having an updating authority for updating said buddy list to inquire if said user is permitted to update said buddy list;

(f) accepting an answer to the inquiry; and

wherein said step (a) comprising the step of determining whether said user has the updating authority for updating said buddy list based on said answer.