JP2009080552A - Presence information collection and distribution system, network system, and presence information collection and distribution program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a presence information collection and distribution system for informing a watcher (presence information collecting side) of presence information according to a state of the watcher in real time, from a presentity (presence information providing side). <P>SOLUTION: The presence information collection and distribution system has a means for receiving presence information from a presence information providing terminal, a means for receiving information on a state of a presence information collecting terminal, a means for processing the received presence information according to the state of the presence information collecting terminal, and a means for transmitting the processed presence information to the presence information collecting terminal. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a presence information collection / distribution system, a network system, and a presence information collection / distribution program, and can be applied to, for example, a presence information collection / distribution system using SIP (Session Initiation Protocol).

  There is a service called “presence service” as a communication service that informs the other party in real time of the user's state (on the phone, away from the seat, etc.). The recent presence service can notify various statuses as well as the conventional online / offline status. Along with this, there is a demand to implement optimal information notification according to the user's condition, such as limiting information that the user wants to receive depending on the location status (user's whereabouts), the type of terminal used by the user, and the like.

  There is a system using SIP (Session Initiation Protocol) as a method of limiting information notified from a presentity side terminal that provides presence information to a watcher side terminal that subscribes (collects) presence information. For example, it is conceivable to limit information to be transmitted to the watcher by managing and controlling a disclosure policy for the watcher of presence information based on the Presence Authorization rule (see Non-Patent Document 4). In addition, unnecessary presence information update notification is made based on the contents of the event notification filter (Event Notification filtering, see Non-Patent Document 3) set at the time of SUBSCRIBE (at the time of information notification reservation) from the watcher side to the presentity side. It is also possible to filter and notify only necessary information on the watcher side.

  However, in the above-mentioned method, the information that is uniquely transmitted is determined by the event notification filter set at the time of SUBSCRIBE (at the time of reservation of information notification) from the watcher and the disclosure policy for the watcher of the presence information, and it corresponds to the situation of the watcher Cannot send. If the watcher's status changes, it may be possible to send a SUBSCRIBE with the event notification filter set again from the watcher. However, if the watcher subscribes to presence information for multiple presentities, the network There is a problem that a lot of traffic is generated on the top. There is also a problem that the load on the presence server and the client terminal increases. Furthermore, it is assumed that the watcher side has an event notification filter function.

As systems for controlling the contents of presence information transmitted on the presentity side based on information from the watcher side, those shown in Patent Literature 1 and Patent Literature 2 have been proposed. The system described in Patent Document 2 notifies the state on the watcher side based on the condition (policy) on the presentity side, and the presentity side restricts the information to be notified depending on the state on the watcher side. . The system described in Japanese Patent Laid-Open No. 2004-228561 limits information notified from the presentity side to the watcher side according to pre-registered conditions (policy).
Japanese Patent Laying-Open No. 2005-044134 JP 2006-277243 A IETF RFC3265 IETF RFC3261 IETF RFC4660 IETF, “Presence Authorization Rules”, [Online], INTERNET, [searched September 11, 2007], <URL: http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-rules -10.txt> IETF RFC3856 IETF RFC3857 IETF RFC3903

  However, the means described in Patent Document 2 is a method for notifying the watcher's state based on the condition (policy) on the presentity side, and does not consider the application of the watcher side policy. Further, the system of Patent Document 2 is described based on realization on a terminal (client terminal), and in what framework (configuration) is specifically used on a server (presence server using SIP). It is not clear whether the information of the watcher is notified to the presentity, and in particular, it is not considered to be realized by the configuration of a plurality of presence servers.

  Patent Document 1 has also been proposed as an optimal notification method means. However, since it is assumed to be implemented according to a policy (condition) registered in advance, the real-time watcher state is changed to the presentity side. Notification is not considered.

  Therefore, a presence information collection / distribution system, a network system, and a presence information collection / distribution program capable of notifying a watcher of presence information corresponding to a real-time watcher state is desired.

  The presence information collection / delivery system of the first aspect of the present invention comprises: (1) a providing presence information receiving means for receiving presence information related to the presence information providing terminal from a presence information providing terminal providing presence information; A collecting-side status information receiving means for receiving information on the status of the presence information collecting terminal from a presence information collecting terminal that collects presence information; and (3) the providing-side presence information according to the status of the presence information collecting terminal. Presence information processing means for processing the presence information received by the receiving means; and (4) providing presence information transmitting means for transmitting the presence information processed by the presence information processing means to the presence information collecting terminal. It is characterized by.

  The network system of the second aspect of the present invention includes (1) a presence information providing terminal that provides presence information, a presence information collecting terminal that collects presence information, and presence information received from the presence information providing terminal. In a network system having a presence information collection and distribution system for transmitting information to the presence information collection terminal, (1) the presence information collection and distribution system of the first aspect of the present invention is applied as the presence information collection and distribution system A network system characterized by

  According to a third aspect of the present invention, there is provided a presence information collection and distribution program comprising: (1) providing presence information receiving means for receiving presence information related to the presence information providing terminal from a presence information providing terminal providing presence information; (2) a collecting-side status information receiving means for receiving information on the status of the presence information collecting terminal from a presence information collecting terminal that collects presence information; and (3) the provision according to the status of the presence information collecting terminal. Presence information processing means for processing the presence information received by the side presence information receiving means; and (4) providing presence information transmission means for transmitting the presence information processed by the presence information processing means to the presence information collecting terminal. It is made to function.

  Provided is a presence information collection / distribution system capable of notifying a watcher of presence information corresponding to the state of a real-time watcher (presence information collecting side) from a presentity (presence information providing side).

(A) Main embodiment
Hereinafter, embodiments of a presence information collection and distribution system, a network system, and a presence information collection and distribution program according to the present invention will be described in detail with reference to the drawings.

(A-1) Configuration of Embodiment FIG. 2 is a block diagram showing the overall configuration of the network system 1.

  The network system 1 includes a presence server 10, a terminal 20, and an IP network 30. In the network system 1, it is assumed that the presence server 10 and the terminal 20 are connected to and communicate with the IP network 30. Here, the network system 1 includes three presence servers 10 (10-1, 10-2, 10-3) and three terminals 20 (20-1, 20-2, 20-3). However, the number of presence servers 10 and terminals 20 is not limited. The terminal 20-1 is a terminal used by a presentity (presence information provider), and the terminals 20-2 and 20-3 are terminals used by a watcher (presence information collecting (subscriber)). And

  The presence servers 10-1 to 10-3 collect presence information having information such as the state of the presentity from the terminals 20 used by the presentity, and send the presence information to the terminals 20 used by a predetermined watcher. It is a notification in real time. Here, the presence server 10-1 collects presence information from the terminal 20-1 (presentity terminal) and uses the presence information collected by the terminal 20-2 (watcher terminal) via the presence server 10-2. Shall be notified.

  Further, the presence server 10 may be connected to the terminal 20 by SIP or XCAP (see XML Configuration Access Protocol, IETF RFC4825), and may be connected to other presence servers 10 by SIP.

  FIG. 1 is a block diagram showing the internal configuration of the presence servers 10-1 to 10-3. FIG. 1 shows the internal configuration of the presence server 10-1 as an example, but the other presence servers 10 have the same configuration.

  Each presence server 10-1 to 10-3 includes a presence information processing unit 11, a SIP signal processing unit 12, a virtual watcher processing unit 13, a policy control unit 14, an XCAP / HTTP processing unit 15, a presence information management unit 16, and user information. A management unit 17 and a policy information management unit 18 are provided.

  It is assumed that the presence information collection / distribution system of this embodiment has at least presence servers 10-1 and 10-2 as subsystems. In FIG. 1 and FIG. 2, the presence server 10-1 and the presence server 10-2 are described as separate devices, but they may be constructed as one device or distributedly processed by three or more devices. The distributed processing method is not limited. Further, the presence information collection / distribution system of this embodiment is not limited to the information processing apparatus such as a personal computer (not limited to one, but may be a system in which a plurality of devices can be distributedly processed). 1 is installed by installing a presence information collection / distribution program (including fixed data), but can be functionally expressed as shown in FIGS.

  In addition, the information collection and distribution system and the network system 1 according to this embodiment may be constructed using, for example, a SIP / SIMPLE (SIP for Instant Messaging and Presentation Leveraging Extensions) framework that is being studied by the IETF. good. As a framework related to presence services in IETF SIP / SIMPLE, for example, as shown in IETF RFC3265 (see Non-Patent Document 1), registration of presence information and notification of presence information are realized using SUBSCRIBE / NOTIFY methods. Things. For example, the SUBSCRIBE / NOTIFY method may be used for registration of presence information and notification of presence information between the presence servers 10 and between the presence server 10 and the terminal 20.

  The presence information processing unit 11 controls presence related information. The SIP signal processing unit 12 performs data transmission / reception control with other presence servers 10 and terminals 20 based on SIP signals.

  The policy control unit 14 performs policy control for presence notification based on the policy information stored in the policy information management unit 18. The policy information management unit 18 manages policy information applied in the policy control unit 14. The policy information stored in the policy information management unit 18 may be set for each presentity or watcher (terminal 20) based on information received from the presentity or watcher (terminal 20). The policy information stored in the policy information management unit 18 may be pre-registered. Specific functions of the policy control unit 14 and details of information stored in the policy information management unit 18 will be described later.

  The virtual watcher processing unit 13 realizes appropriate presence information notification to the watcher (terminal 20-2) by handling the presence server in cooperation with the policy control unit 14, and includes a watcher information storage unit 13a. The virtual watcher processing unit 13 stores information related to the watcher in the watcher information storage unit 13a, and collects and notifies presence information based on the stored information. Specific functions of the virtual watcher processing unit 13 and information stored in the watcher information storage unit 13a will be described later.

  The user information management unit 17 manages subscriber information, location information, and the like. The presence information management unit 16 manages presence information of each user. The XCAP / HTTP processing unit 15 performs reception of presence policy information from the terminal 20 using XCAP or HTTP.

  Next, specific processing in the virtual watcher processing unit 13 and policy control unit 14 in the presence server 10-1 on the presentity side, and details of information managed in the watcher information storage unit 13a and policy information management unit 18 Will be described.

  FIG. 3 is an explanatory diagram illustrating an example of a watcher list 300 that is generated in the virtual watcher processing unit 13 and stored in the watcher information storage unit 13a when the presence server 10 operates as a presence server of a presentity. .

  The watcher list 300 shows the information of the watcher currently subscribed to the presentity (terminal 20-1), and is generated when a subscription request is received from the presence server 10-2 on the watcher side. is there. For example, in the presence server 10-1, when there is a subscription request for the presentity (terminal 20-1) from the presence server 10-2 on the watcher side, the virtual watcher processing unit 13 in the presence server 10-1 Generated for each presentity. Further, the virtual watcher processing unit 13 generates (activates) a virtual watcher for each presentity. The virtual watcher manages the contents of the watcher list 300 of the corresponding presentity, and also has functions such as generating presence information according to the watcher state and notifying the presence server 10-2 on the watcher side. .

The watcher list 300 includes information of an information distribution destination user ID 301, a transmission address 302, and a watcher state 303.

  The information distribution destination user ID 301 (virtual watcher ID) indicates information for identifying the virtual watcher subscribed to the presence information of the presentity in the presence server 10-2 on the watcher side. Details of the virtual watcher in the presence server 10-2 on the watcher side will be described later.

The transmission address 302 is information for identifying the terminal 20 of the watcher. For example, an IP address and a domain name are input here.

  The watcher state 303 indicates the state of the watcher, and here, for example, it is assumed to be indicated by three statuses of state 1, state 2, and state 3. The state 1 indicates whether the watcher is logged in online or logged off. State 2 indicates whether the watcher is currently working or in a private state rather than working. State 3 shows the current location (location) of the watcher. The location display may be a location name (for example, “蕨”, “home”, etc.) or may be indicated by coordinate information (for example, latitude and longitude information). The format is not limited.

  FIG. 5 is an explanatory diagram showing an example of a notification policy table 500 applied in the policy control unit 14 when the presence server 10 operates as a presence server of a presentity.

  The notification policy table 500 is a table that defines the presentity presence information policy to be notified to the watcher, and is set in the policy information management unit 18 when a policy is registered from the presentity (terminal 20-1). . The notification policy table 500 includes policy ID 501 and notification policy 502 information. The policy ID 501 is an ID for identifying a policy.

  A notification policy 502 indicates presentity information to be notified to the watcher. Here, the presence information notified to the watcher includes items of state 1 (online / offline), state 2 (work / private), and state 3 (location information), and any combination of information in the notification policy 502 It is defined whether to send For example, since the policy ID 501 is “2” and “notification policy 502 is state 1 (online / offline) and state 2 (work / private)”, watchers to which this policy is applied include: Information on the state 1 and the state 2 is notified, but the state 3 (location information) is not notified.

  FIG. 4 is an explanatory diagram showing an example of the notification condition table 400 applied in the policy control unit 14 when the presence server 10 operates as a presence server on the presentity side.

  The notification condition table 400 is a table that defines which policy of the notification policy table 500 (see FIG. 5) is to be applied under what conditions (states) the watcher is, and presentity (terminal 20-1). Is set in the policy information management unit 18 at the time of policy registration. The notification condition table 400 includes information on condition NO 401, condition 402, and application policy 403.

  Condition NO 401 indicates information for identifying the condition.

  The condition 402 indicates the state of the watcher, and corresponds to the watcher state 303 (see FIG. 3) in the watcher list 300. The application policy 403 indicates the policy ID 501 (see FIG. 5) of the notification policy table 500 applied when the watcher is in a state that matches the condition 402. For example, in the condition 402 where the condition NO 401 is “2”, the condition 402 is “watcher state 2 = private”, and the applied policy 403 is “2”, so that the state 2 of the watcher state 303 in the watcher list 300 is “2”. For a watcher that is “private”, a notification policy 502 with a policy ID 501 of “2” in the notification policy table 500 is applied, and only state 1 (online / offline) and state 2 (work / private) are notified. It will be.

  In the presentity-side presence server 10-1, the virtual watcher processing unit 13 (virtual watcher) notifies the policy control unit 14 of the information of the watcher list 300 (see FIG. 3), and the policy control unit 14 The notification conditions are determined by the notification condition table 400 (see FIG. 4) and the notification policy table 500 (see FIG. 5), and respond to the virtual watcher processing unit 13 (virtual watcher). The virtual watcher processing unit 13 (virtual watcher) that has received the response generates presence information according to the notification policy notified from the policy control unit 14 and transmits the presence information to the transmission destination (presence server 10-2 on the watcher side). .

  Next, details of the virtual watcher processing unit 13 and the policy control unit 14 in the presence server 10-2 on the watcher side will be described.

  FIG. 6 is an explanatory diagram showing an example of a watcher information management table 600 that is generated by the virtual watcher processing unit 13 and stored in the watcher information storage unit 13a when the presence server 10 operates as a presence server of a watcher. is there.

  The watcher information management table 600 manages the status of each watcher accommodated in the presence server 10 and information on presentities that are currently subscribed to presence information. Information of the watcher information management table 600 is generated in the virtual watcher processing unit 13 when a subscription request is received from the watcher (terminal 20-2). For example, when the presence server 10-2 receives a subscription request for a presentity (terminal 20-1) from a watcher (terminal 20-2), the virtual watcher processing unit 13 in the presence server 10-2 provides a presentation. Generated for each Titi. The virtual watcher processing unit 13 generates (activates) a virtual watcher for each watcher. The virtual watcher manages the contents of the watcher information management table 600 of the corresponding watcher, generates presence information corresponding to the state of the watcher, and notifies the watcher (terminal 20-2). .

  The watcher information management table 600 has information of an information distribution destination user ID 601, a virtual watcher ID 602, a watcher state 603, and a presentity ID 604. The information distribution destination user ID 601 indicates the user ID of the watcher. The virtual watcher ID 602 is information for identifying a virtual watcher corresponding to the watcher.

  The watcher state 603 indicates the state of the watcher, and here, for example, it is assumed to be indicated by four statuses of state 1, state 2, state 3, and state 4. Since the state 1, the state 2, and the state 3 are the same as those of the watcher list 300 described above, description thereof is omitted. State 4 is a terminal condition indicating information on a terminal currently used by the watcher. For example, the watcher state 603 whose information distribution destination user ID 601 is “aaa” indicates that the watcher is logged in using a mobile phone because the state 4 is “mobile”.

  A presentity ID 604 indicates a list of presentities to which the watcher currently subscribes for presence information.

  FIG. 8 is an explanatory diagram showing an example of a notification policy table 800 applied in the policy control unit 14 when the presence server 10 operates as a watcher-side presence server.

  The notification policy table 800 is a table that defines a policy of presentity information to be transmitted to the watcher, and is set in the policy information management unit 18 when the watcher (terminal 20-2) registers the policy. The notification policy table 800 includes policy ID 801 and notification policy 802 information. Since the policy ID 801 and the notification policy 802 have the same contents as the policy ID 501 and the notification policy 502 in the notification policy table 500 described above, detailed description thereof is omitted.

  FIG. 7 is an explanatory diagram showing an example of a notification condition table 700 applied in the policy control unit 14 when the presence server 10 operates as a watcher-side presence server.

  The notification condition table 700 is a table that defines which policy of the notification policy table 800 (see FIG. 8) is to be applied under what condition (state) of the watcher. This is set in the policy information management unit 18 at the time of policy registration. The notification condition table 700 has information of condition NO 701, condition 702, and application policy 703.

  Condition NO701 indicates information for identifying the condition. The condition 702 indicates the state of the watcher, and corresponds to the watcher state 603 (see FIG. 6) of the watcher information management table 600. The application policy 703 indicates the policy ID 801 (see FIG. 8) of the notification policy table 800 applied when the watcher is in a state that matches the condition 702. Since the policy application method is the same as the notification condition table 400 and the notification policy table 500 described above, a detailed description thereof will be omitted.

  In the watcher-side presence server 10-2, the virtual watcher processing unit 13 (virtual watcher) notifies the policy control unit 14 of the above-described watcher information management table 600 (see FIG. 6), and the policy control unit 14 The notification condition is determined by the notification condition table 700 (see FIG. 7) and the notification policy table 800 (see FIG. 8), and responds to the virtual watcher processing unit 13 (virtual watcher). Upon receiving the response, the virtual watcher processing unit 13 (virtual watcher) generates information according to the notification policy notified from the policy control unit 14, and transmits the information to the transmission destination (watcher (terminal 20-2)).

(A-2) Operation of Embodiment Next, the operation of presence information collection / delivery in the network system 1 of this embodiment having the above-described configuration will be described.

  FIG. 9 is an explanatory diagram showing operations related to presence information collection / distribution in the network system 1.

  Here, it is assumed that the presentity user is using the terminal 20-1 and the watcher user is logging in using the terminal 20-2.

  First, the status notification of the presentity (terminal 20-1) is sent to the presence server 10-1 (S101), and the status notification of the watcher (terminal 20-2) is sent to the presence server 10-2 (S102). ).

  Then, it is assumed that a subscription request for the presentity (terminal 20-1) is transmitted from the watcher (terminal 20-2) to the presence server 10-2 (S103).

  When the subscription request for the presentity (terminal 20-1) is received, the virtual watcher processing unit 13 of the presence server 10-2 generates a virtual watcher corresponding to the watcher (terminal 20-2). Information is generated (S104).

  Then, the virtual watcher processing unit 13 in the presence server 10-2 transmits a subscription request to the presence server 10-1 that houses the presentity (terminal 20-1) requested by the watcher (terminal 20-2). (S105).

  When the subscription request is received from the presence server 10-2, the virtual watcher processing unit 13 of the presence server 10-1 generates a virtual watcher corresponding to the presentity (terminal 20-1), and generates a watcher list 300 ( S106).

  Then, the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-1 sends the watcher (terminal 20-) to the presence server 10-2 in order to sequentially manage the state of the watcher (terminal 20-2) that requested the subscription. A subscription request is made for the state 2 (presence information). Then, the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-2 collects the status (presence information) of the watcher (terminal 20-2), and the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-1. ). When the status (presence information) of the watcher (terminal 20-2) is notified, the notified status (presence information) is reflected in the watcher list 300 in the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-1. (S107).

  When the status (presence information) of the watcher (terminal 20-2) is received, the virtual watcher processing unit 13 (virtual watcher) and policy control unit 14 of the presence server 10-1 receive the contents of the watcher list 300 and the notification condition table 400. And the content of the notification policy table 500, notification content is determined, and presence information to be notified to the watcher (terminal 20-2) is generated (S108).

  Next, the presence information generated in step S108 described above is notified to the presence server 10-2 by the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-1 (S109).

  When the presence information of the presentity (terminal 20-1) is received, the virtual watcher processing unit 13 (virtual watcher) and policy control unit 14 of the presence server 10-2 receive the contents of the watcher information management table 600 and the notification condition table 700. And the contents of the notification policy table 800 are determined, and presence information to be transmitted to the watcher (terminal 20-2) is generated (S110).

  Next, the presence information generated in step S110 described above is notified to the presence server 10-2 by the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-2 (S111).

  When the status of the watcher (terminal 20-2) is changed, a status notification similar to that in step S102 described above is transmitted from the watcher (terminal 20-2) to the presence server 10-2, and the content is the presence server 10-2. Are reflected in the watcher information management table 600 by the virtual watcher processing unit 13 (virtual watcher). Thereafter, the status (presence information) of the watcher (terminal 20-2) is notified to the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-1, and the virtual watcher processing unit 13 (virtual watcher) of the presence server 10-1 As a result, the information in the watcher list 300 is updated.

  When the state of the presentity (terminal 20-1) is changed, a state notification similar to that in step S101 described above is transmitted, and thereafter, the same operation as in steps S108 to S111 described above is performed.

  10 and 11 are sequence diagrams representing the operation shown in FIG. 9 described above on a SIP / SIMPLE basis (using the SCRIBE / NOTIFY method).

  First, as advance preparation, the presentity (terminal 20-1) notifies the presence server 10-1 of terminal registration (REGISTER), status notification (PUBLISH), and policy information (XCAP PUT). Then, the policy information management unit 18 of the presence server 10-1 sets the notified policy information in the notification condition table 400 and the notification policy table 500 (S201). Step S201 is an operation corresponding to step S101 described above.

  Similarly, terminal registration (REGISTER), status notification (PUBLISH), and policy information are set (XCAP PUT) from the watcher (terminal 20-2) to the presence server 10-2. The notified policy information is set in the notification condition table 700 and the notification policy table 800 in the policy information management unit 18 of the presence server 10-2 (S202). Step S202 is an operation corresponding to step S102 described above.

  Next, when a subscription request (SUBSCRIBE) is notified of presence information of the presentity (terminal 20-1) from the watcher (terminal 20-2) to the presence server 10-2, virtual watcher processing of the presence server 10-2 In the unit 13, a watcher information management table 600 is generated, and a virtual watcher corresponding to the watcher (terminal 20-2) is generated. Then, the presence server 10-2 notifies the presence server 10-1 of a subscription request (SUBSCRIBE) for the presence information of the presentity (terminal 20-1) (S203). Step S203 is an operation corresponding to steps S103 to S105 described above.

  When a subscription request (SUBSCRIBE) is notified from the presence server 10-2 to the presence server 10-1, the virtual watcher processing unit 13 of the presence server 10-1 generates a watcher list 300 and presents the terminal 20 A virtual watcher corresponding to -1) is generated. The presence server 10-1 then notifies the presence server 10-2 of a subscription request (SUBSCRIBE) for the presence information of the watcher (terminal 20-2) (S204).

  When a subscription request (SUBSCRIBE) is notified from the presence server 10-1, the presence server 10-2 refers to information on the status of the watcher (terminal 20-2) in the watcher information management table 600, and the presence server 10-1 Status notification (NOTIFY). Then, the virtual watcher processing unit 13 of the presence server 10-1 updates the contents of the watcher list 300 based on the notified information (S205). Steps S204 and S205 are operations corresponding to the above-described steps S106 and S107.

  Next, in the presence server 10-1, the virtual watcher processing unit 13 and the policy control unit 14 determine one of the policies in the notification policy table 500 based on the information in the watcher list 300 and the notification condition table 400. Presence information based on the set policy is generated. That is, presence information of the presentity (terminal 20-1) notified to the presence server 10-2 is generated based on the policy determined according to the state of the watcher (terminal 20-2). The generated presence information is notified from the presence server 10-1 to the presence server 10-2 (NOTIFY). When presence information of the presentity (terminal 20-1) is notified from the presence server 10-1, in the presence server 10-2, the virtual watcher processing unit 13 and the policy control unit 14 perform a watcher information management table 600, notification conditions. Based on the information in the table 700, one of the policies in the notification policy table 800 is determined, and presence information based on the determined policy is generated. The generated presence information is notified (NOTIFY) from the presence server 10-2 to the watcher (terminal 20-2) (S206). Step S206 is an operation corresponding to S108 to S111 described above.

  Next, the operation when the state of the watcher (terminal 20-2) changes will be described. When the status of the watcher (terminal 20-2) changes, status notification (PUBLISH) is sent to the presence server 10-2. When the status notification (PUBLISH) is made, the presence server 10-2 updates the information in the watcher information management table 600 based on the notified information. Then, status notification (NOTIFY) regarding the watcher (terminal 20-2) is sent from the presence server 10-2 to the presence server 10-1. When status notification (NOTIFY) related to the watcher (terminal 20-2) is made, the presence server 10-1 updates the contents of the watcher list 300 based on the notified information (S207).

  Next, the operation when the state of the presentity (terminal 20-1) changes will be described. When the state of the presentity (terminal 20-1) changes, a state notification (PUBLISH) is sent to the presence server 10-1. When the status notification (PUBLISH) is made, the presence server 10-1 generates again the presence information for notifying the watcher (terminal 20-2) by the same operation as the above-described step S206, and the presence server 10- Two-state notification (NOTIFY) is made. Similarly, presence information for notifying the watcher (terminal 20-2) is again generated in the presence server 10-2, and status notification (NOTIFY) is sent to the watcher (terminal 20-2). However, in the presence server 10-2, when the applied policy in the notification policy table 800 is “not notify”, the presence information is sent from the presence server 10-2 to the watcher (terminal 20-2). There are cases where notification (NOTIFY) is not made.

(A-3) Effects of Embodiment According to this embodiment, the following effects can be achieved.

  In this embodiment, both the presentity-side presence server 10-1 and the watcher-side presence server 10-2 manage the virtual watcher process and the respective notification policy information, so that the state of the watcher is received from the presentity side. It is possible to realize information notification according to the situation. In addition, the watcher can receive the presentity information in consideration of the reception policy on the watcher side.

  Also, as shown in FIGS. 10 and 11 described above, the network system (presence information collection / distribution system) of this embodiment can be constructed without departing from the IETF SIPMPLE-based framework. Thus, a network system (presence information collection / distribution system) can be realized by using a SIP / SIMPLE-based framework.

  In this embodiment, since the event notification filter technology (IETF RFC4660, see Non-Patent Document 3) is not used, the traffic flowing through the network can be reduced, and the processing load on the terminal 20-1 on the presentity side can also be reduced. be able to.

(B) Other Embodiments The present invention is not limited to the above-described embodiments, and may include modified embodiments as exemplified below.

(B-1) Communication between presence servers defined in the above embodiment is not limited to SIP. For example, data files having presence information and various commands (subscription requests etc.) information may be exchanged by HTTP or the like.

(B-2) In the above embodiment, both the presentity-side presence server 10-1 and the watcher-side presence server 10-2 include the virtual watcher processing unit 13, the policy control unit 14, and the like. The presence information related to the presentity (terminal 20-1) is processed according to the state of the watcher (terminal 20-2), but the presence information is processed only by the presence server 10-1 on the presentity side. Anyway. Further, the presence information may be processed only by the presence server 10-2 on the watcher side.

(B-3) In the above embodiment, the presence server 10 may have only a configuration necessary as a watcher-side presence server. For example, the presence server 10 may accommodate only the presentity terminal and may not perform the processes related to the watcher information management table 600, the notification condition table 700, and the notification policy table 800.

  The presence server 10 may have only a configuration necessary as a watcher-side presence server. For example, the presence server 10 may accommodate only the watcher's terminal and may not perform the processing related to the watcher list 300, the notification condition table 400, and the notification policy table 500.

(B-4) In the above embodiment, a configuration may be adopted in which a call control server is separately arranged in the network system 1 and connected to the IP network, and call control is performed for communication between each device (system).

(B-5) In the above embodiment, the watcher list 300, the notification condition table 400, the notification policy table 500, the watcher information management table 600, the notification condition table 700, and the notification policy table 800 store information of each item. For example, the table structure is not limited to those shown in FIGS.

It is a block diagram explaining the internal structure of the presence server which concerns on embodiment. It is a block diagram explaining the whole network system composition concerning an embodiment. It is explanatory drawing shown about the example of the watcher list produced | generated in a presence server based on Embodiment. It is explanatory drawing explaining the example of the notification condition table applied when the presence server which concerns on embodiment operates as a presentity side presence server. It is explanatory drawing explaining the example of the notification policy table applied when the presence server which concerns on embodiment operate | moves as a presentity side presence server. It is explanatory drawing shown about the example of the watcher information management table produced | generated in a presence server based on Embodiment. It is explanatory drawing explaining the example of the notification condition table applied when the presence server which concerns on embodiment operates as a presence server by the side of a watcher. It is explanatory drawing explaining the example of the notification policy table applied when the presence server which concerns on embodiment operates as a watcher side presence server. It is explanatory drawing shown about operation | movement of the network system (presence information collection delivery system) which concerns on embodiment. It is the first half part of the sequence diagram which showed operation | movement of the network system (presence information collection delivery system) based on embodiment on the basis of SIP / SIMPLE. It is the latter half part of the sequence diagram which showed operation | movement of the network system (presence information collection delivery system) based on embodiment on the basis of SIP / SIMPLE.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Network system 10, 10-1-10-3 ... Presence server 20, 20, 20-1-20-3 ... Terminal, 30 ... IP network, 11 ... Presence information processing part, 12 ... SIP signal processing part, 13 DESCRIPTION OF SYMBOLS ... Virtual watcher processing part, 13a ... Watcher information storage part, 14 ... Policy control part, 15 ... XCAP / HTTP processing part, 16 ... Presence information management part, 17 ... User information management part, 18 ... Policy information management part.

Claims (6)

Providing presence information receiving means for receiving presence information related to the presence information providing terminal from a presence information providing terminal for providing presence information;
A collecting-side status information receiving means for receiving information on the status of the presence information collecting terminal from a presence information collecting terminal that collects presence information;
Presence information processing means for processing the presence information received by the providing-side presence information receiving means according to the state of the presence information collecting terminal;
A presence information collection / distribution system comprising: presence information transmitting means for transmitting presence information processed by the presence information processing means to the presence information collection terminal. A first subsystem for accommodating the presence information providing terminal; and a second subsystem for accommodating the presence information collecting terminal;
The first subsystem includes the providing side presence information receiving unit and the presence information processing unit,
The presence information collection and distribution system according to claim 1, wherein the second subsystem includes the collection-side state information receiving unit and the providing-side presence information transmission unit. The second subsystem is
Further comprising presence information reprocessing means for further processing the presence information processed by the presence information processing means,
The presence information collection / delivery system according to claim 2, wherein the providing side presence information transmission means transmits the presence information processed by the presence information reprocessing means to the presence information collection terminal.   4. The presence information collection / delivery system according to claim 1, wherein the presence information collection / delivery system is constructed using an IETF SIP / SIMPLE framework. Presence information providing terminal for providing presence information; presence information collecting terminal for collecting presence information; presence information collecting for receiving presence information from the presence information providing terminal and transmitting the received presence information to the presence information collecting terminal In a network system having a distribution system,
5. A network system, wherein the presence information collection and distribution system according to claim 1 is applied as the presence information collection and distribution system. Computer
Providing presence information receiving means for receiving presence information related to the presence information providing terminal from a presence information providing terminal for providing presence information;
A collecting-side status information receiving means for receiving information on the status of the presence information collecting terminal from a presence information collecting terminal that collects presence information;
Presence information processing means for processing the presence information received by the providing-side presence information receiving means according to the state of the presence information collecting terminal;
A presence information collection and distribution program for causing presence information processed by the presence information processing means to function as providing presence information transmission means for transmitting to the presence information collection terminal.

Images