PRESENCE SYSTEM AND INFORMATION PROCESSING EQUIPMENT, DYNAMIC BUDDY LIST GENERATION METHOD IN PRESENCE SYSTEM, AND PRESENCE NOTIFICATION DESTINATION CONTROLLING METHOD AND ITS PROGRAM FOR USE WITH PRESENCE SYSTEM

• US 20090138566A1
• Filed: 01/29/2009
• Published: 05/28/2009
• Est. Priority Date: 01/22/2003
• Status: Active Grant

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: ITO, Naoko, Watanabe, Masafumi
• Granted Patent: US 7,953,811 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Abstract

A presentity service client has a presentity that issues presence information to a presence service and a watcher which observes presence information for other presentities; a presence change rule holding part holds a presence change rule; and a presence calculating part changes the presence information for the presentity, using as a trigger a change in presence information of other presentities, based on the presence information of other presentity acquired by the watcher and in accordance with the presence change rule held by a presence change rules holding part.

Claims

1. A dynamic buddy list generation method for automatically generating a buddy list for use by each client on a network to manage state information for own client or other clients, wherein:

each client has a state managing part which stores state information A for own client;

a state monitoring part which stores state information B for other clients and holds a buddy list (population list) that manages said state information B;

a buddy list generating part which generates a buddy list (selection list) based on a given generation rule; and

a buddy list managing part which holds said selection list,

and comprising;

when a change occurs in the state of own client or any other client,

first step wherein said state managing part updates and transmits said state information A to said buddy list generating part,

second step wherein said state monitoring part transmits state notification request information which acquires the state after change to other clients included in said population list, and receives from other clients state change notification information in response to said state notification request information and said state information B,

third step wherein said state monitoring part updates state information B being managed by said population list, based on said state change notification information, and transmits said population list to said buddy list generating part,

fourth step wherein said buddy list generating part generates said selection list, based on said state information A received from said state managing part in said first step, said state information B being managed by said population list received from said state monitoring part in said third step, and said generation rule, and transmits said selection list to said buddy list managing part, and

fifth step wherein said buddy list managing part holds said selection list received from said buddy list generating part in said fourth step.

2. The dynamic buddy list generation method as set forth in claim 1, wherein:

said buddy list generating part includes a generation rule managing part which changes said generation rule, and said generation rule managing part has the first changing step of changing said generation rule by reflecting said state information A or B received in said fourth step.

3. The dynamic buddy list generation method as set forth in claim 2, wherein:

said generation rule managing part has the second changing step of causing a generation rule to be changed in response to the action taken from own client to change said generation rule.

4. A dynamic buddy list generation method for automatically generating a buddy list for a server on a network to manage state information for each client, wherein:

each client includes a state managing part which stores state information C for own client and buddy list managing part which holds a buddy list (selection list) generated and transmitted by a server, wherein

the server includes a state monitoring part which stores said state information C and holds a buddy list (population list) which manages said state information C, and a buddy list generating part which generates said selection list for each client based on the pre-set rule,

and comprising;

when a change occurs in a state of any of the clients,

sixth step wherein said state managing part updates said state information C,

seventh step wherein said state monitoring part transmits state notification request information which acquires the state after change to other clients included in said population list, and receives from other clients state change notification information in response to said state notification request information and said state information C,

eighth step wherein said state monitoring part updates state information C being managed by said population list, based on said state change notification information, and transmits said population list to said buddy list generating part,

ninth step wherein said buddy list generating part generates said selection list for each client, based on said state information C being managed by said population list received from said state monitoring part in said eighth step and said generation rule, and transmits said selection list to said buddy list managing part of each client, and

tenth step wherein said buddy list managing part holds said selection list received from said buddy list generating part in said ninth step.

5. The dynamic buddy list generation method as set forth in claim 4, wherein:

said buddy list generating part includes a generation rule managing part which changes said generation rule, wherein said generation rule managing part has the third changing step of changing said generation rule by reflecting said state information C received in said ninth step.

6. The dynamic buddy list generation method as set forth in claim 5, wherein:

said generation rule managing part has the fourth changing step of causing a generation rule to be changed in response to the action taken from each client to change said generation rule.

7. A presence system, comprising:

presentities that provide presence information indicating at least the state of own entity;

subscribers that observe said presence information; and

a presence service that delivers said presence information received from said presentities to said subscribers;

wherein said presentities are provided with a notification part which notifies said presence information to specific subscribers only.

8. The presence system as set forth in claim 7, wherein

said presentities include an element which derives said specific subscribers in accordance with a notification destination determination rule held by said presentities,

wherein said notification part notifies said presence information to said specific subscribers thus derived only.

9. The presence system as set forth in claim 7, wherein

said presentities include an element which derives said specific subscribers in accordance with a notification destination determination rule that includes a notification condition designated by said subscribers,

wherein said notification part notifies said presence information to said specific subscribers thus derived only.

10. The presence system as set forth in claim 7, wherein

said subscribers determine subscribers to which said presence information is to be notified in accordance with the order in which said subscribers have performed subscription.

11. The presence system as set forth in claim 7, wherein

subscribers to which said presence information is to be notified are determined according to the attributes of said subscribers.

12. The presence system as set forth in claim 7, wherein

subscribers to which said presence information is to be notified are determined according to the presences for said presentities.

13. The presence system as set forth in claim 7, wherein

when notifying said presence information, information for authenticating that the destination subscribers are said specific subscribers is added.

14. The presence system as set forth in claim 13, wherein

said information for authenticating is information with a pre-set time limit.

15. The presence system as set forth in claim 7, wherein

at least any of instant messaging, e-mail, or telephone notification is included as a means of notifying said presence information.

16. A presence notification destination controlling method, wherein

said method is a presence notification destination controlling method for a presence system comprising presentities that provides presence information indicating at least the state of own entity;

subscribers that observe said presence information; and

a presence service that delivers said presence information received from said presentities to said subscribers;

and comprising on the side of said presentities the step of notifying said presence information to specific subscribers only.

17. The presence notification destination controlling method as set forth in claim 16, wherein

the step of deriving said specific subscribers in accordance with a notification destination determination rule held by said presentities is included on the side of said presentities,

wherein the step of notifying said presence information notifies said presence information to said specific subscribers thus derived only.

18. The presence notification destination controlling method as set forth in claim 16, wherein

the step of deriving said specific subscribers in accordance with a notification destination determination rule that includes a notification condition designated by said subscribers is included on the side of said presentities,

wherein the step of notifying said presence information notifies said presence information to said specific subscribers thus derived only.

19. The presence notification destination controlling method as set forth in claim 16, wherein

said subscribers determine subscribers to which said presence information is to be notified in accordance with the order in which said subscribers have performed subscription.

20. The presence notification destination controlling method as set forth in claim 16, wherein

subscribers to which said presence information is to be notified are determined according to the attributes of said subscribers.

21. The presence notification destination controlling method as set forth in claim 16, wherein

subscribers to which said presence information is to be notified are determined according to the presences for said presentities.

22. The presence notification destination controlling method as set forth in claim 16, wherein

when notifying said presence information, information for authenticating that the destination subscribers are said specific subscribers is added.

23. The presence notification destination control method as set forth in claim 22, wherein

said information for authenticating is information with a pre-set time limit.

24. The presence notification destination controlling method as set forth in claim 16, wherein

the step of notifying said presence information notifies said presence information using a means including any of instant messaging, e-mail, or telephone notification.

25. A presence notification destination controlling program, wherein

said program is a presence notification destination controlling program for a presence system comprising presentities that provides presence information indicating at least the state of own entity;

subscribers that observe said presence information; and

a presence service that delivers said presence information received from said presentities to said subscribers;

and comprising capabilities of having a computer execute a function of notifying said presence information to specific subscribers only.