Source: http://www.google.com/patents/US20050210113?dq=552685
Timestamp: 2014-03-14 23:22:34
Document Index: 561353680

Matched Legal Cases: ['art 401', 'art 402', 'art 403', 'art 401', 'art 402', 'art 402', 'art 403', 'art 403', 'art 401', 'art 402', 'art 402', 'art 403', 'art 403', 'art 403', 'art 403', 'art 402', 'art 403', 'art 402', 'art 403', 'art 402', 'art 401', 'art 403', 'art 403', 'art 403', 'art 710', 'art 720', 'art 710', 'art 720', 'art 403', 'art 403', 'art 403', 'art 403', 'art 403', 'art 403', 'art 403', 'art 403']

Patent US20050210113 - Presence information sharing method and system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsPresence information is shared between a plurality of applications, to grasp a change of presence information of a different kind of application. An IM(X) server 3 receives a notification of a change of presence information from a client A1 (S902), and sends a change notification message for notifying...http://www.google.com/patents/US20050210113?utm_source=gb-gplus-sharePatent US20050210113 - Presence information sharing method and systemAdvanced Patent SearchPublication numberUS20050210113 A1Publication typeApplicationApplication numberUS 11/079,274Publication dateSep 22, 2005Filing dateMar 15, 2005Priority dateMar 16, 2004Also published asCN1671105A, CN100344102C, US7716293Publication number079274, 11079274, US 2005/0210113 A1, US 2005/210113 A1, US 20050210113 A1, US 20050210113A1, US 2005210113 A1, US 2005210113A1, US-A1-20050210113, US-A1-2005210113, US2005/0210113A1, US2005/210113A1, US20050210113 A1, US20050210113A1, US2005210113 A1, US2005210113A1InventorsKenji Kasuga, Tatsuhiko Miyata, Mitsuru Ikezawa, Kazuyoshi HoshinoOriginal AssigneeKenji Kasuga, Tatsuhiko Miyata, Mitsuru Ikezawa, Kazuyoshi HoshinoExport CitationBiBTeX, EndNote, RefManReferenced by (12), Classifications (15), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetPresence information sharing method and systemUS 20050210113 A1Abstract Presence information is shared between a plurality of applications, to grasp a change of presence information of a different kind of application. An IM(X) server 3 receives a notification of a change of presence information from a client A1 (S902), and sends a change notification message for notifying the change of the presence information to a presence server 5 (S906). Then, the presence server 5 sends the change notification message received from the IM(X) server 3 to the IM(Y) server 4 (S908). The IM(Y) server 4 sends the change notification message received from the presence server 5 to a client B2 (S910). Images(10) Claims(8)
DETAILED DESCRIPTION Now, embodiments of the present invention will be described. FIG. 1 is a block diagram showing a presence information sharing system to which one embodiment of the present invention is applied. As shown in the figure, the presence information sharing system of the present embodiment comprises a client A1, a client B2, an instant message X server 3 (hereinafter, referred to as the IM(X) server 3), an instant message Y server 4 (hereinafter, referred to as the IM(Y) server 4), and a presence server 5. These apparatuses are connected through a network 9 such as Internet, an intranet, or the like. The client A1 is an information processing apparatus used by a user A, and can use kinds of instant messaging services (so-called text chat). An instant messaging service is a service that displays an inputted text in real time on an output unit of a client as a communication partner and has a function of knowing a status of a terminal of a communication partner. The instant messaging service can cooperate with another application such as an online game, Internet telephony, video conference, and the like. In the present embodiment, it is assumed that the client A1 has two kinds of application software (instant messengers), IM(X) 11 and IM(Y) 12. Further, it is assumed that text chat, video chat, an online game or the like is performed between instant messengers of the same kind The client B2 is au information processing apparatus used by a user B, and has the same configuration as the client A1. Namely, the client B has two kinds of application software, IM(X) 21 and IM(Y) 22. The IM(X) server 3 is an information processing apparatus that provides a certain instant messaging service to the client A1 and the client B2 connected to the IM(X) server 3 itself. The IM(X) server 3 comprises: a service processing unit 31 that provides a certain service such as text chat, video chat, an online game, or the like to each client 1 or 2; a presence management unit 32 that manages a status of a user; a service information storage unit 33 for storing data required for the service processing unit to provide its service; a presence information storage unit 34 for storing presence information described below referring to FIG. 3; and a communication processing unit 35 that sends and receives data to and from another apparatus through the network 9. The IM(Y) server 4 is an information processing apparatus that provides a different instant messaging service from the service of the IM(X) server 3, and the configuration of the IM(Y) 4 is similar to the one of the IM(X) server 3. The presence server 5 is an information processing apparatus that collects presence information (described below) from the IM(X) server 3 and the IM(Y) server 4 for the purpose of sharing the presence information between the servers 3 and 4 The presence server 5 comprises: a presence management unit 51 that collects presence information from the IM(X) server 3 and the IM(Y) server 4; a presence information storage unit 52 for storing presence information (described below referring to FIG. 3); and a communication processing unit 53 that sends and receives data to and from another apparatus through the network 9. The present embodiment has two clients 1 and 2 and two IM servers 3 and 4. However, there may exist three or more clients or IM servers. In addition, a plurality of presence servers 5 may exist. As each of the above-described clients 1 and 2, IM servers 3 and 4 and presence server 5, may be used a general purpose computer system as shown in FIG. 2, comprising a CPU 901, a memory 902 such as a RAM, an external storage unit 903 such as an HDD, an input unit 904 such as a keyboard or a mouse, an output unit 905 such as a display or a printer, a communication controller unit 906 for connecting with a network, and a bus 907 for connecting these devices, for example. Functions of the above-mentioned apparatuses are each realized on such a computer system when the CPU 901 executes a certain program loaded on the memory 902. For example, each function of the clients 1 and 2, IM servers 3 and 4 and the presence server 5 is realized when the CPU 901 of the client 1 or 2 executes a program for the client 1 or 2, or when the CPU 901 of the IM server 3 or 4 executes a program for the IM server 3 or 4, or when the CPU 901 of the presence server 5 executes a program for the presence server 5. In this case, the memory 902 or the external storage unit 903 of the IM server 8 or 4 is used as the service information storage unit 33 or 43 and the presence information storage unit 34 or 44 of the IM server 3 or 4. Further, the memory 902 or the external storage unit 903 of the presence server 5 is used as the presence information storage unit 52 of the presence server 5. Next, will be described the presence information. The presence information indicates a status of a user (or the client 1 or 2 used by a user). FIG. 3 shows an example of a presence information table 300 that uses the table structure to indicate presence information for each kind of instant messaging service used by each user. As shown in the figure, the presence information table 300 has user information 301 as information for identifying a user, and a status 302 of IM(X) and a status 303 of IM(Y) of each user. With respect to the user A, the example of FIG. 3 shows that the status of IM(X) 11 is �chatting� and the status of IM(Y) 12 is �standby�. Further, with respect to the user B, the example shows that the status of IM(X) 21 is �standby� and the status of XM(Y) is �chatting�. As categories of status, the present embodiment uses two categories, i.e. �standby� and �chatting�. However, it is possible to use other categories such as �playing a game�, �video chatting�, �being out�, �staying at desk�, and the like, according to a service provided by the instant messaging. Further, the present embodiment describes the case of two users, the user A using the client A and the user B using the client B. However, in the case where another user uses this presence information sharing system, the presence information of that user is generated also. Further, the presence information table 300 is stored in the respective presence information storage units 34, 44 and 52 of the IM(X) server 3, the IM(Y) server 4 and the presence server 5. Next, will be described a SIP message. In the present embodiment, SIMPLE (SIP for instant Messaging and Presence Leveraging Extension), which is an extension of SIP, is used for sending and receiving presence information. SIP (Session Initiation Protocol) is a protocol used for call control of establishing/changing/ending a multimedia communication (session) including voice, video and text through an IP network. SIMPLE is extended from SIMP to send and receive presence information and instant message information. FIG. 4 shows a configuration of an ordinary SIP message. As shown in the figure, a SIP message has a request line part 401, a header part 402 and a body part 403. The request line part 401 describes such information as a �method� indicating a purpose (a type) of a request, �Request URI� indicating a destination as a communication partner, and the like. In the example shown, its method is �SUBSCRIBE�. The header part 402 describes information on a client that has issued the message and information used for the SIP protocol. For example, as shown in the figure, the header part 402 describes �Via� indicating a response path, �From� indicating a sender, �To� indicating a destination address, �Call-ID� indicating a session identifier, �CSeq� indicating a command sequence, �Contact� indicating an address for a session partner to access the message sender himself, �Content-Length� indicating the number of octets of the body part 403, and the like. The body part 403 describes a medium that can be used, parameters, and the like, if necessary. For sending and receiving presence information, is used a message whose request part 401 describes the �SUBSCRIBE� method or the �NOTIFY� method prescribed in SIMPLE The method �SUBSCRIBE� is a change notification request method, which is used for requesting a communication partner in advance to notify a change of the presence information (status) of the communication partner each time. The method �NOTIFY� is a method used for notifying a change of presence information (status) to a communication partner who has sent a change notification request using �SUBSCRIBE�. Thus, to acquire presence information of a communication partner, a client 1 or 2 previously sends a SUBSCRIBE message whose �Request URI� designates the URI of the communication partner to an IM servers 3 or 4 (Or, the URI of the communication partner may be designated in �To� of the header part 402) Thereafter, each time the status of the communication partner changes, for example, owing to log-in of the client as the communication partner, the client 1 or 2 as the communication partner notifies the presence information (status) to the IM servers 3 or 4. Then, the IM servers 3 or 4 sends a NOTIFY message to notify the status change of the communication partner to the client 1 or 2 that has sent the SUBSCRIBE message. In the case of a conventional SUBSCRIBE message, its request line part describes �Request URI� indicating a destination of a user as a communication partner, as shown in FIG. 4 (Or, the destination may be described in �To� of the header part 402). As a result, a change notification request is designated for one user. In other words, even in the case where a user as a communication partner uses a plurality of instant messaging services and presence information (status) changes with respect to only one of the instant messaging services, all pieces of presence information (all the statuses) of the instant messaging services that the user uses are notified using a NOTIFY message. In the case of the example shown, �user B� is the object of the change notification request. Further, a conventional SUBSCRIBE message does not use the body part 403. Accordingly, �Content-Length� of the header part is always set with �0�. The present invention extends SUBSCRIBE prescribed by SIMPLE, and uses the body part 403 to designate details of the object of the change notification request. Namely, a user as the object of the change notification request and an instant messaging service are set in the body part 403. Accordingly, when the presence information of the instant messaging service designated in the body part 403 changes among various pieces of presence information of the user as the object of the change notification request, then only the changed presence information of the instant messaging service is notified using a NOTIFY message. FIGS. 5A and 5B show a conventional SUBSCRIBE message and a SUBSCRIBED message extended by the present invention. FIG. 5A shows au example of a conventional SUBSCRIBE message. As shown in the figure, �Content-Length� of the header part 402 of the message shown in FIG. 5A is set with �0�, and the message part 403 does not exit. On the other hand, FIG. 5B shows an example of an extended SUBSCRIBE message. In the header part 402 of the message shown in FIG. 5B, �Content-Length� is set with a value other than �0�, and the message part 403 describes a user as the object of the change notification request and the instant messaging service as the object of the change notification request. The shown example requests a notification of a change of only the presence information of IM(X) of �user B�. Next, will be described processing performed in each of the IM(X) server 3, the IM(Y) server 4 and the presence server 5 when a SUBSCRIBE message is received. FIG. 6 is a flowchart showing processing in each server 3, 4 or 5. In the following, the IM(X) server 3 is taken as an example. The similar processing is performed also in the IM(Y) server 4 and the presence server 5. First, the presence management unit 32 receives a SUBSCRIBE message through the communication processing unit 34 (S601). Then, the presence management unit 32 refers to �Content-Length� of the header part 402 of the received message, to judge whether �0� is set to �Content-Length� (S602). In the case where �Content-Length� is set with �0� (S602: YES), the presence management unit 32 notifies a change of presence information with respect to one user designated in �Request URI� in the request line part 401 to the communication partner who has sent the SUBSCRIBE message (S603). Namely, this is processing of a conventional SUBSCRIBE message. And when any piece of presence information of the object user is changed, all pieces of presence information of that user are sent using a NOTIFY message. On the other hand, in the case where �Content-Length� is set with a value other than �0� (S602: NO), then the presence management unit 32 refers to the body part 403. Only when the presence information of the instant messaging service designated in the body part 403 is changed, the change of the presence information in question is notified to the communication partner who has sent the SUBSCRIBE message (S604). Namely, this is processing of an extended SUBSCRIBE message. And, among the presence information of the object user, only the presence information of the instant messaging service designated in the body part 403 is sent using a NOTIFY message when that presence information is changed. Thus, each server 3, 4 ox 5 can judge whether the conventional SUBSCRIBE processing should be performed or the extended SUBSCRIBE processing should be performed, depending on whether �Content-Length� of a SUBSCRIBE message is set with �0� or not. As a result, in the presence information sharing system of the present embodiment, a conventional SUBSCRIBE message and an extended SUBSCRIBE message can coexist. Further, using an extended SUBSCRIBE message, it is possible to designate details of objects of a presence information change notification requests and not to notify an unnecessary change of presence information. Next, will be described a display screen (GUI: Graphical User Interface) of an instant messaging service of IM(X) or IM(Y), which is displayed on the output unit of the client A1 or the client B2. FIG. 7 shows an example of a display screen of a text chat instant messaging service. The display screen shown in the figure has a presence information registration part 710, a chat part 720 for text chat, and a member list 730 for displaying presence information of users using the text chat in question. The presence information registration part 710 receives registration of presence information (such as standby, chatting, or the like, for example), which is set in advance in a pall-down menu 711 or the like, from the input unit 904 of the client A1 or the client B2. When a depression of a registration button 712 is received, the registered presence information is sent to the IM server 3 or 4 that provides the instant messaging service in question. The chat part 720 has a display area 721 for displaying a text sent by each user using the text chat, an input area 722 for displaying a text inputted by a user using the client in question through the input unit 904, and a send button 723 for sending a text displayed in the input area 722. This text inputted in the input area 722 is sent using a SIP message whose method is �MESSAGE� prescribed in SIMPLE. The member list 730 displays similar information to information of the presence information table 300 described referring to FIG. 3. Namely, the member list 730 has user information (i.e. information identifying a user) and statuses of IM(X) and IM(Y) of that user. The example of member list 730 shown in FIG. 7 displays presence information of the other users than the user of the client itself. However, it is possible that the member list 730 displays the presence information of the user (the user B, in this case) of the client itself. Next, will be described processing of a presence information-change notification request using a SUBSCRIBE message. FIG. 8 shows a flow of SUBSCRIBE messages that are sent in advance in order that a change in XM(X) 11 of the user A can be confirmed through each display screen (See FIG. 7) of IM(X) 2 ox IM(Y) in the client A1 of the user A. First, the following processing is performed so that IM(X) 21 of the client B2 of the user B acquires the presence information of IM(X) 11 of the client A1 of the user A. Namely, IM(X) 21 of the client B2 sends a SUBSCRIBE message (the message 801) that requests a notification of a change of the presence information of IM(X) 11 of the user A, to the presence management unit 32 of the IM(X) server 3 that provides the instant messaging service of IM(X) 21. In detail, when the power of the client B2 is turned on, or the instant messaging service of IM(X) 21 is activated, a presence management unit (not shown) of IM(X) 21 of the client 332 sends the following message to the IM(X) server 3. This SUBSCRIBE message is an extended SUBSCRIBE message with its �Content-Length� being set with a value other than �0� For the sake of convenience of description, URI (Uniform Resource Identifier) is not used for describing destinations and addresses in �Request URI� of the request line part and �From� and �To� of the header part. Also, for the sake of convenience of description, �Via�, �Call-ID� and the like to be described in the header part are omitted. [Request line part] SUBSCRIBE URI of the user A [Header part] From: URI of the user B To: URI of the user A Content-Length: nnn [Body part] target = the user A::IM(X) On the other hand, in order that IM(Y) 22 of the client B2 of the user B acquires the presence information of IM(X) 11 of the client A1 of the user A, it is necessary to send three messages, the message 802, the message 803 and the message 804 shown in the figure. First, the message 802 is a SUBSCRIBE message that IM(Y) 22 of the client B2 sends to the IM(Y) server 4. In detail, when the client B2 is turned on or the instant messaging service of IM(Y) 22 is activated, a presence management unit (not shown) of IM(Y) 22 sends a SUBSCRIBE message similar to the above-mentioned message 801, for requesting a notification of a change of the presence information of IM(X) 11 of the user A, to the presence management unit 42 of the IM(Y) server 4. Further, the message 803 is a SUBSCRIBE message that the presence management unit 42 of the IM(Y) server 4 sends to the presence server 5. In detail, when the IM(X) server 4 is activated by turning on the power for example, then the presence 10 management unit 42 of the IM(X) server 4 sends the following message to the presence management unit 51 of the presence server 5 for requesting a notification of a change of the presence information of IM(X) 11 of the user A. [Request line part] SUBSCRIBE URI of the user A [Header part] From: URI of the IM(Y) server To: URI of the user A Content-Length: nnn [Body part] target = the user A::IM(X) Further, the message 804 is a SUBSCRIBE message send by the presence management unit 51 of the presence server 5 to the IM(X) server 3. In detail, when the presence server 5 is activated by turning on the power for example, then the presence management unit 51 of the presence server 5 sends the following message to the presence management unit 32 of the IM(X) server 3 for requesting a notification of a change of the presence information of IM(X) 11 of the user A. [Request line part] SUBSCRIBE URI of the user A [Header part] From: URI of the presence server To: URI of the user A Content-Length: nnn [Body part] target = the user A::IM(X) Thus, when IM(X) 21 of the client B2 sends the message 801 in advance, the user B can know a change of the presence information of IM(X) 11 of the user A through the display screen (See FIG. 7) of IM(X) 21. Further, when the IM(Y) 22 of the client B2 sends the message 802 in advance, the IM(Y) server 4 sends the message 803 in advance and the presence server 4 sends the message 804 in advance, the user B can also know a change of the presence information of IM(X) 11 of the user A through the display screen (See FIG. 7) of IM(X) 22. In other words, it is possible to k)now presence information of a different kind of instant messaging service. Next, will be described processing of a presence information change notification using a NOTIFY message. FIG. 9 shows a flow of change notification messages in the case where the user A changes the presence information of IM(X) 11 after the SUBSCRIBE messages (messages 801-804) shown in FIG. 8 are sent in advance. As shown in FIG. 10, it is assumed that all the presence information statuses are �standby� in the presence information tables 300 of the IM(X) server 3, the IM(Y) server 4 and the presence server 5 before the user A changes the presence information of IM(X) 11. First, the client A1 receives an instruction to change the presence information of IM(X) 11 from the user A (S901). Namely, using the input unit 904 of the client A1, the user A changes his presence information of IM(X) 11 through the display screen (See FIG. 7) of the instant messaging service of IM(X) 11 In this case, the user A registers a change of the presence information of IM(X) from �standby� to �chatting�. Next, a presence management unit (not shown) of the client A1 sends the received presence information to the IM(X) server 3 (S902). Namely, the presence management unit of the client A1 sends a message for registering the changed presence information, to the IM(X) server 3 Here, a message for registering changed presence information is not prescribed in SIP and SIMPLE. Accordingly, the presence information registration message is sent using a SIP message of the request type �PUBLISH� or using another protocol than SIP. Next, the presence management unit 32 of the IM(X) server 3 updates the presence information table 300 stored in the presence information storage unit 34 (S903). Namely, the presence management unit 32 receives the presence information registration message from IM(X) 11 of the client A1 through the communication processing unit 35. Then, based on the received message, the presence management unit 32 updates the presence information table 300. In this case, the presence management unit 32 changes the status of IM(X) 11 of the user A in the presence information table 300 from �standby� to �chatting�. FIGS. 11A to 11C show the respective presence information tables 300 of the IM(X) server 3, the IM(Y) server 4 and the presence server 5 after the processing of S903. As shown in the figure, only the status of the user A's IM(X) in the IM(X) server 3 has been updated to �chatting� 11 a. Next, the presence management unit 32 of the IM(X) server 3 sends a NOTIFY message for notifying the user A's presence information of IM(X) 11 in the presence information table 300 (S904 and S906). Namely, the presence management unit 32 of the IM(X) server 3 has previously received the SUBSCRIBE messages (the messages 801 and 804) shown in FIG. 8 from the IM(X) 21 of the client B2 and from the presence server 5. Accordingly, since the user A's presence information of IM(X) 11 has been changed, the presence management unit 32 sends a NOTIFY message (S904) to the client B2 and a NOTIFY message (S906) to the presence server 5. Here, the message that the presence management unit 32 of the IM(X) server 3 has received from IM(X) 21 of the client B2 is an extended SUBSCRIBE message having the body part 403 in which �target� is described. Accordingly, as for the NOTIFY message (S904) to the client B2, the presence management unit 32 notifies only the presence information of IM(X) described in the �target� of the body part 403 among the user A's presence information stored in the presence information table 300. The presence management unit 32 of the IM(X) server 3 sends the following NOTIFY message to IM(X) 21 of the client B2. Here, the user A's presence information of IM(X) is described in the XML format in the body part of the message. [Request line part] NOTIFY the contact address of the user B [Header part] From: URI of the user A To: URI of the user B Content-Length: nnn [Body part] (description of the status (�chatting�) of user A's IM(X)) Then, IM(X) 21 of the client )32 receives the NOTIFY message from the IM(X) server 3, and changes the member list 730 in the display screen (See FIG. 7) (which is outputted to the output unit 905) of the instant messaging service of IM(X) 21 (S905). In detail, the status of user A's IM(X) in the member list 730 is changed to �chatting� Through this display screen, the user B can know a change of the status of the user A each time. Further, the presence management unit 32 of the IM(X) server 3 sends the NOTIFY message to the presence server 5 (S906) Here, the message that the presence management unit 32 of the IM(X) server 3 has received from the presence management unit 51 of the presence server 5 is an extended SUBSCRIBE message having the body part 403 in which �target� is described. Accordingly, as for the NOTIFY message (S906) to the presence server 5, the presence management unit 32 of the IM(X) server 3 notifies only the presence information of IM(X) described in the �target� of the body part 403 among the user A's presence information stored in the presence information table 300. Namely, the presence management unit 32 of the IM(X) server 3 sends the following NOTIFY message to the presence server 5. Here, the user A's presence information of IM(X) 11 is described in the XML format in the body part of the message. [Request line part] NOTIFY the contact address of the presence server [Header part] From: URI of the user A To: URI of the presence server Content-Length: nnn [Body part] (description of the status (�chatting�) of user A's IM(X)) Next, the presence management unit 51 of the presence server 5 updates the presence information table stored in the presence information storage unit 52 (S907). Namely, the presence management unit 51 receives the NOTIFY message from the, IM(X) server 3 through the communication processing unit 53. Then, based on the received NOTIFY message, the presence management unit 51 updates the presence information table 300. In this case, the presence management unit 51 changes the status of user A's IM(X) 11 in the presence information table 300 from �standby� to �chatting�. FIGS. 12A to 12C show the respective presence information tables 300 of the IM(X) server 3, the IM(Y) server 4 and the presence server 5 after the processing of S907. As shown in the figure, the status of user A's IM(X) 11 has been updated to �chatting� 12 c in the presence server 5. Then, the presence management unit 51 of the presence server 5 sends a NOTIFY message to the IM(Y) server 4 (S908). Namely, the presence management unit 51 of the presence server 5 has previously received the SUBSCRIBE message (FIG. 8: the message 803) from the IM(Y) server 4. Accordingly, since the user A's presence information of IM(X) 11 has been changed, the presence management unit 51 sends a NOTIFY message to the IM(Y) server 4 (S908). Here, the message that the presence management unit 51 of the presence server 5 has received from the XM(Y) server 4 is an extended SUBSCRIBE message having the body part 403 in which �target� is described. Accordingly, the presence management unit 51 notifies only the user A's presence information of IM(X) 11 described in the �target� of the body part 403 among the user A's presence information stored in the presence information table 300, to the IM(Y) server 4. The presence management unit 51 of the presence server 5 sends the following NOTIFY message to the IM(Y) server 4. Here, the user A's presence information of IM(X) 11 is described in the XML format in the body part of the message [Request line part] NOTIFY the contact address of the user A [Header part] From: URI of the user A To: URI of the IM(Y) server Content-Length: nnn [Body part] (description of the status (�chatting�) of user A's IM(X)) Next, the presence management unit 42 of the IM(Y) server 4 updates the presence information table 300 stored in the presence information storage unit 44 (S909). Namely, the presence management unit 42 receives the NOTIFY message from the presence server 5 through the communication processing unit 45. Then, based on the received NOTIFY message, the presence management unit 42 updates the presence information table 300. In this case, the presence management unit 42 changes the status of user A's IM(X) 11 in the presence information table 300 from �standby� to �chatting�. FIGS. 13A to 13C show the respective presence information tables 300 of the IM(X) server 3, the IM(Y) server 4 and the presence server 5 after the processing of S909. As shown in the figure, the status of user A's IM(X) has been updated to �chatting� 13 b. Next, the presence management unit 42 of the IM(Y) server 4 sends a NOTIFY message to IM(Y) 22 of the client B2 (S910). Namely, the presence management unit 42 of the IM(Y) server 4 has previously received the SUBSCRIBE message (FIG. 8, the message 802) from IM(Y) 22 of the client B2. Accordingly, since the user A's presence information of IM(X) 11 has been changed, the presence management unit 42 sends a NOTIFY message to the client B2. Here, the message that the presence management unit 42 of the IM(Y) server 4 has received from IM(Y) 22 of the client B2 is an extended SU)3SCRIBE message having the body part 403 in which �target� is described. Accordingly, the presence management unit 32 notifies only the user A's presence information of IM(X) 11 described in the �target� of the body part 403 among the user A's presence information stored in the presence information table 300, to the client B2. The presence management unit 42 of the IM(Y) server 4 sends the following NOTIFY message to IM(Y) 22 of the client B2. Here, the user A's presence information of IM(X) 11 is described in the XML format in the body part of the message. [Request line part] NOTIFY the contact address of the user A [Header part] From: URI of the user A To: URI of the user B Content-Length: nnn [Body part] (description of the status (�chatting�) of user A's IM(X)) Then, IM(Y) 22 of the client B2 receives the NOTIFY message from the IM(Y) server 4 and changes the member list 730 in the display screen (See FIG. 7) of the instant messaging service IM(Y) 22, which is displayed on the output unit 905 (S911). In detail, the user A's status of IM(X) in the member list 730 is changed to �chatting�. Thus, on the display screen of IM(Y) 22, the user B can each time know a change of the presence information (status) of the user A using IM(X) 21 that is a different kind of instant messaging service from IM(Y) 22. Hereinabove, one embodiment of the present invention has been described. In this embodiment, provision of the presence server 5 makes it possible to share presence information of a plurality of instant messaging services. As a result, when a communication partner registers a change of his presence information in any instant messaging service, the change of the presence information is notified to all the instant messaging services. Accordingly, a user using any instant messaging service can know a change of presence information of a communication partner promptly without fail. Further, the above-described embodiment uses an extended SUBSCRIBE message shown in FIG. 5B. As a result, it is possible to designate details of the object of a change notification request. Namely, only when presence information of an instant messaging service designated in the body part of a message is changed, the presence information in question only is notified using a NOTIFY message. As a result, it is possible to suppress sending and receiving of unnecessary messages. The present invention is not limited to the above-described embodiment, and can be variously varied within the scope of the invention. For example, in the above embodiment, the user A uses the client A1, and the client A1 has two instant messaging services, IM(X) 11 and IM(Y) 12. However, IM(X) 11 and IM(Y) 12 may be used in different information apparatuses, respectively. For example, it is possible that the user A uses a personal computer for IM(X) 11 and a mobile phone for IM(Y) 12. Further, in the above embodiment, the IM(X) server 3, the IM(Y) server 4 and the presence server 5 each have its own presence information table 300 in its presence information storage unit. However, it is possible that only the presence server 5 has the presence information table 300. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7685608Dec 22, 2006Mar 23, 2010Palm, Inc.Data processing apparatus and a method of operating data processing apparatus for generating representations of availability status for application programsUS7694313 *Dec 22, 2006Apr 6, 2010Palm, Inc.Terminating device and a method of operating a terminating device configured to communicate availability status directly between terminating devicesUS7715859 *Dec 22, 2006May 11, 2010Palm, Inc.Presence engine and a method of operating a presence engine for encoding or decoding availability status into a signal representative of an audio signalUS7831673 *Oct 31, 2007Nov 9, 2010Google Inc.Methods and systems for processing offline chat messagesUS7970391 *Mar 25, 2010Jun 28, 2011Hewlett-Packard Development Company, L. P.Managing availability status in a communications networkUS8266226Jun 26, 2009Sep 11, 2012International Business Machines CorporationSystem and method to enhance user presence management to enable the federation of rich media sessionsUS8291067 *Jun 29, 2007Oct 16, 2012Microsoft CorporationProviding access to presence information using multiple presence objectsUS8396922Nov 20, 2006Mar 12, 2013Aol Inc.Promoting interoperability of presence-based systems through the use of ubiquitous online identitiesUS8396965Apr 25, 2012Mar 12, 2013International Business Machines CorporationSystem and method to enhance user presence management to enable the federation of rich media sessionsUS20070162555 *Nov 20, 2006Jul 12, 2007Aol LlcPromoting interoperability of presence-based systems through the use of ubiquitous online identitiesEP2190154A1Oct 15, 2009May 26, 2010Samsung Electronics Co., Ltd.Method of updating user presence information in mobile instant messaging and mobile terminal using the sameWO2008079823A2 *Dec 18, 2007Jul 3, 2008Palm IncData processing apparatus and a method of operating data processing apparatus for generating representations of availability status for application programs* Cited by examinerClassifications U.S. Classification709/206, 709/224International ClassificationH04L29/08, H04L12/18, G06F15/16, G06F15/173, G06F13/00, H04L12/58, G06F15/00Cooperative ClassificationH04L67/24, H04L12/581, H04L51/04European ClassificationH04L51/04, H04L29/08N23, H04L12/58BLegal EventsDateCodeEventDescriptionOct 16, 2013FPAYFee paymentYear of fee payment: 4Jun 7, 2005ASAssignmentOwner name: HITACHI, LTD., JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KASUGA, KENJI;MIYATA, TATSUHIKO;IKEZAWA, MITSURU;AND OTHERS;REEL/FRAME:016669/0929;SIGNING DATES FROM 20050420 TO 20050421Owner name: HITACHI, LTD.,JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KASUGA, KENJI;MIYATA, TATSUHIKO;IKEZAWA, MITSURU AND OTHERS;SIGNED BETWEEN 20050420 AND 20050421;US-ASSIGNMENT DATABASE UPDATED:20100511;REEL/FRAME:16669/929Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KASUGA, KENJI;MIYATA, TATSUHIKO;IKEZAWA, MITSURU;AND OTHERS;SIGNING DATES FROM 20050420 TO 20050421;REEL/FRAME:016669/0929RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google