Presence system and method for presence management

• US 7,677,436 B2
• Filed: 03/03/2005
• Issued: 03/16/2010
• Est. Priority Date: 03/30/2004
• Status: Active Grant

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Ohno, Takashi, Kakuta, Jun
• Primary Examiner(s): Lee; Seung H
• Application Number:
  US11/070,295
• Publication Number:
  US 20050218206A1
• Time in Patent Office: 1,839 Days
• Field of Search: 235/375, 235/376, 709/204, 709/227, 455/456.6
• US Class Current: 235/375
• CPC Class Codes: G07C 11/00 Arrangements, systems or apparatus for checking, e.g. the occurrence of a condition, not provided for elsewhere
• CPC Class Codes: G07C 9/27 with central registration
• CPC Class Codes: G07C 9/28 the pass enabling tracking or indicating presence
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• 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

Abstract

A presence server stores a presence that is identified by presence IDs “a1” and “a2”, as the presence of a user “A”. User “A” can pass a card that they hold through a card reader at a timing of their choosing. The card reader reads in data from the card and transmits a renewal request to the presence server. The renewal request includes a renewer ID, an object ID, category information and the presence. When the presence server receives the renewal request, it specifies the presence ID “a1” of user “A” to be the presence that is to be renewed, based on the category information, and moreover, rewrites the presence of the presence ID “a1” to a presence “meeting room A” that is included in the renewal request. Thus, the card reader can renew the presence designated by the “category information”. As for the presence that is renewed, it is notified to a watcher of the presence “a1” from the presence server.

Claims

1. A presence system that manages presences of a user identified by a user identifier that specifies the user, the presence system comprising:

a reception unit for receiving a renewal request that includes;

a user identifier of a renewer, who is a user other than the owner of the presences;

a user identifier of an object to be renewed, the object possessing a presence that the renewer attempts to set, and

a presence that the renewer attempts to set;

a category acquisition unit for acquiring category information associated with the renewer, wherein the category information represents the category of the content of the presence;

an association table that stores an association of the identifiers of the presences of the object to be renewed, and the category information;

a presence specification unit for referring to the association table, and for specifying the presence identifier associated with the category information corresponding to the renewer, and

a presence setting unit for setting the presence included in the renewal request, with respect to the specified presence identifier.

2. The presence system according to claim 1, wherein the renewal request further includes the category information, and wherein the category acquisition unit acquires the category information from the reception unit.

3. The presence system according to claim 1, further comprising:

a category information management unit for storing a category information management table that stores the category information in association with the user identifier of the renewer;

wherein the category acquisition unit acquires category information corresponding to the renewer from the category information management unit.

4. The presence system according to claim 1, further comprising:

a conversion rule table that stores conversion rules for converting the presence included in the renewal request into another presence, and

a conversion unit for converting the presence included in the renewal request in accordance with the conversion rules.

5. The presence system according to claim 1, further comprising:

a requester memory unit for storing the user identifier of the renewer and the category information associated with the renewer;

a category information notification unit for notifying the category information associated with the renewer, to the object to be renewed before the reception unit receives the transfer request, and

an association reception unit for receiving an association of the identifier of each presence of the object that is to be renewed with the category information associated with the renewer, and storing it in the association table.

6. A presence management method performed by a computer for managing presences of a user identified by a user identifier that specifies the user, the presence management method comprising:

a reception step for receiving, by the computer, a renewal request that includes;

a user identifier of a renewer, who is a user other than the owner of the presences;

a user identifier of an object to be renewed, the object possessing a presence that the renewer attempts to set, and

a presence that the renewer attempts to set;

a category acquisition step for acquiring, by the computer, category information associated with the renewer, wherein the category information represents the category of the content of the presence;

an association memory step for storing, in a storage medium, an association table that stores an association of the identifiers of the presences of the object to be renewed, and the category information;

a presence specification step for referring to the association table stored in the storage medium, and for specifying the presence identifier associated with the category information corresponding to the renewer, and

a presence setting step for setting, by the computer, the presence included in the renewal request, associated with the specified presence identifier.

7. A computer readable recording medium on which a presence management program is recorded in order to execute the management of presences of a user identified by a user identifier that specifies the user, the presence management program comprising:

a reception step for receiving a renewal request that includes;

a user identifier of a renewer, who is a user other than the owner of the presences;

a user identifier of an object to be renewed, the object possessing a presence that the renewer attempts to set, and

a presence that the renewer attempts to set;

a category acquisition step for acquiring category information associated with the renewer, wherein the category information represents the category of the content of the presence;

an association memory step for storing an association table that stores an association of the identifiers of the presences of the object to be renewed, and the category information;

a presence specification step for referring to the association table, and for specifying the presence identifier associated with the category information corresponding to the renewer, and

a presence setting step for setting the presence included in the renewal request, associated with the specified presence identifier.

8. A presence management program for managing presences of a user identified by a user identifier that specifies the user, the presence program causing a computer to function as:

a reception unit for receiving a renewal request that includes;

a user identifier of a renewer, who is a user other than the owner of the presences;

a user identifier of an object to be renewed, the object possessing a presence that the renewer attempts to set, and

a presence that the renewer attempts to set;

a category acquisition unit for acquiring category information associated with the renewer, wherein the category information represents the category of the content of the presence;

an association table that stores an association of the identifiers of the presences of the object to be renewed, and the category information;

a presence specification unit for referring to the association table, and for specifying the presence identifier associated with the category information corresponding to the renewer, and

a presence setting unit for setting the presence included in the renewal request, associated with the specified presence identifier.

9. A presence system that manages presences of a user identified by a user identifier, the presence system comprising:

an acquisition unit for acquiring a user identifier of a requester, who is a user other than the owner of a given presence, a user identifier of an object that possesses a presence and category information that expresses the category of any presence, and that is associated with the renewer or the object;

a deciding unit for determining the type of command to process the presence of the object;

a command creation unit for creating commands that include the type of the command that the deciding unit determines, category information that the acquiring unit acquires, and the user identifier of the object; and

a command execution unit for receiving commands created by the command creation unit, for performing renewal of the presence of the object, subscription/subscription cancellation, or transfer/transfer cancellation in accordance with the commands thereof.

10. The presence system according to claim 9, wherein the acquisition unit further acquires an acquisition time of the user identifier of the requester, the presence system further comprising:

a history memory unit for storing acquired history including the user identifier of the object and the acquisition time,

wherein when a user identifier of a new requester is acquired, the judgment unit judges whether or not the user identifier of the object was acquired within a past predetermined time interval Δ

T, based on the acquisition history, and determines the type of the command based on the decision.

11. The presence system according to claim 10, wherein if the type of the command that was decided is transfer, then the judgment unit sets any one of the user identifiers of the objects acquired within the past predetermined time interval Δ

T to be the user identifier of the transfer origin user.

12. The presence system according to claim 9, further comprising:

a corresponding memory unit for storing the association of the user identifier of the object and the type of the command;

wherein the judgment unit determines the command type corresponding to the user identifier of the object based on the association stored in the corresponding memory unit.

13. The presence system according to claim 12, wherein the acquisition unit further acquires an acquisition time of the user identifier of the requester, the presence system further comprising:

a history memory unit for storing an acquisition history including the user identifier of the object and the acquisition timing thereof;

wherein the judgment unit groups the user identifier of the object based on the acquisition history, and if the command type is transfer or subscription, then the judgment unit specifies the user identifier that will be the transfer origin and the subscribee, within the single group.

14. The presence system according to claim 9, further comprising:

a presence content acquisition unit for acquiring the content of a presence based on the user identifier of the object and the category information corresponding to the requester or the object;

wherein the judgment unit judges whether or not the transfer origin is set in the acquired presence content, and designates the command type as either transfer or transfer cancellation, based on the judgment result.