JP4549687B2 - Cooperation system and cooperation method - Google Patents

Description

The present invention relates to instant messaging (hereinafter referred to as IM system). In the IM system, presence information representing the state of each user application device is shared between applications.
In the present invention, the IM system includes an IM server and an IM client. The IM client operates on a user agent that is a computer terminal, generates and updates presence information, and notifies the IM server. The IM server stores presence information generated and updated by the IM client, and when the presence information is updated, notifies the user agent of the watcher of the presence information of the update. Here, the user agent of the watcher is a user agent that requests the IM server to notify the presence information (hereinafter referred to as “subscribe”). A user agent that provides status information to the IM server is called a presentity. The presence information is data including a wide range of text data including a text message, image data such as an icon, voice data including a voice message, and the like.

  For example, AOL Messenger, Yahoo Messenger, and Microsoft Messenger are provided as IM systems. In the IM system, for example, a one-to-one real-time dialogue by instant messaging can be performed. In addition, the IM system manages user status such as “online”, “offline”, and “busy now” as presence information, and a user who requests subscription (hereinafter referred to as “subscribe”) to the presence information and its computer terminal (Hereinafter, both are referred to as watchers) is notified of a change in presence information. The user who generates the presence information and the computer terminal are called presentity.

  In order for the watcher to acquire presence information in the IM system, it is necessary to send a subscribe request from the watcher to the IM system and establish a subscribe state for the presence information. The subscribe request includes an identifier or address designation of presence information that the watcher is interested in. For a watcher who has subscribed to some presence information, the IM system notifies the change when the presence information is changed by the presentity. This communication model is generally called subscribe notify. This subscribe-notify is a simple communication model, and provides an efficient information exchange mechanism by distributing presence information only to the parties who need it in real time.

By the way, a business process management (hereinafter referred to as BPM) system has a function of improving business efficiency of a company by, for example, preventing human work mistakes and monitoring the progress of a business flow. Such BPM system is being introduced in the enterprise.
JP 2003-186775 A

Presence information handled by a conventional IM system is data relating to the state of the user or user terminal. However, in the future, it is expected that the number of objects handled as presence information will increase, such as automobiles, information appliances, and products and packages with RFID (Radio Frequency ID) tags. If so, it can be expected that the number of applications on the watcher side will increase, and it will be necessary to process presence changes in relation to different types of presence information.
The business flow handled by the BPM system can be regarded as a kind of presence information. Then, how far the business flow has been executed can be defined as presence information, and the progress of the business flow can be monitored by the IM system. In this case, by using a presence management protocol (for example, SIMPLE: SIP for Instant Messaging and Presence Leveraging Extensions) used by the IM system, it is possible to grasp and manage the progress of the business flow in real time.

For example, when there is a different type of business flow and one of the business flows is in a specific state, the presence information may be notified or the notification content may be changed according to the state of the other business flow. Conceivable. In addition, for example, it can be assumed that the network application controls the information home appliance connected to the home network based on the presence change of the information home appliance and the user presence change, and finally provides the service to the user.
Conventionally, the application on the watcher side has dealt with the increase in the number of presences and the complexity of the subscribing relationship. Therefore, when trying to develop a complicated application using presence management by the IM system, the processing of the application on the watcher side becomes complicated. Also, if the watcher-side application has a logic that manages a complicated subscribing relationship and changes processing according to the relationship, the result is a rigid application that is vulnerable to specification changes.

  For example, it is assumed that a service in which systems having different operation policies are linked in a company is realized. For example, it is a case where a sales management system, an inventory management system, a delivery management system, and the like are linked to perform a product sales business. In that case, presence information (events, alerts, etc.) exchanged between systems is important for inter-system linkage control. However, once a linkage rule is set, it has a great influence on other systems when an attempt is made to change or add it later, making it difficult to change the presence information notification logic on a case-by-case basis.

In the present invention, presence information can be passed between different systems based on the need to apply the IM system to various fields and the weaknesses of the conventional methods corresponding thereto, and without significant changes to the system. It is an object of the present invention to provide a technology capable of flexibly changing and adding presence information notification logic.
Another object of the present invention is to provide a technique that can handle a wide variety of information using a subscribe-notify IM system.

In order to solve the above-described problem, the first aspect of the present invention relates to a first management method in which one or more provider is connected and one or more status information generated by each provider is associated with a status identifier for identifying each status information. Provided is a linkage system connected to a first status information management device and the second status information management device . This system includes the following means.
State information receiving means for receiving notification of state information (hereinafter referred to as one or more state information) corresponding to one or more state identifiers from the first state information management device;
Generating means for generating first meta-state information different from each received state information based on the one or more received state information;
A status information notification means for notifying the second status information management device of a first meta status identifier for identifying the first meta status information and the first meta status information; and a reference request for the first meta status information. In response to the received inquiry from the second status information management device , request means for transmitting a reference request for the one or more status information, which is a source of the first meta status information , to the first status information management device;
- according to the response from the first state information managing device to the reference request of the one or more state information, whether it is possible to see the first meta state information, the first meta through the second state information managing device Notification means for transmitting to the requester of the state information reference request.

  For example, it is assumed that the IM server SA (corresponding to the first state information management apparatus) manages presence information PDA1, PDA2 (hereinafter simply referred to as presence information UA1, UA2) of the user agents UA1, UA2 in association with each other. User agent identifiers (hereinafter referred to as user IDs) UA1, UA2,... Are also identifiers of presence information (hereinafter referred to as presence IDs). For example, the cooperation system receives a plurality of presence information UA1 and UA2 from the IM server SA, and generates first metapresence information MPD1 (hereinafter referred to as first metapresence information CA1) based on the first metapresence ID “CA1”. . For example, the first meta presence information CA1 can be generated according to the following formula (1) or the following formula (2).

(First meta presence information CA1) = (presence information UA1) + (presence information UA2) (1)
(First meta presence information CA1) = (presence information UA1) × (presence information UA2) (2)
As will be described later, meta presence information can be generated based on presence information managed by different IM servers SA and SB, respectively.
For example, the cooperation system may generate the first meta presence information CA1 based on one presence information UA1. For example, when the value PDA1 of the presence information CA1 is within a predetermined range, the first meta presence information CA1 can be generated according to the following equation (3).

(First meta presence information CA1) = predetermined value X (3)
The first meta presence information and the presence ID “CA1” generated as described above are notified from the cooperation system to the IM server. This notification can be performed using a command for notifying presence information from the presentity to the IM server in the IM system. That is, the cooperation system functions as a presentity for generating the first meta-presence information CA1 when viewed from the IM server. Accordingly, the watcher of the first meta presence information CA1 receives the notification from the IM server every time the first meta presence information CA1 is updated.

As described above, the cooperation system connects to one or more IM servers as a user agent. The cooperation system subscribes to presence information managed by the IM server, and generates and updates new presence information by independently processing the presence information. Furthermore, the generated new presence information is notified to the IM server. Therefore, the user agent of the IM server that manages meta-presence information can be a meta-presence information watcher.
A second aspect of the present invention provides the cooperation system according to the first aspect, further comprising rule storage means for storing a first rule for generating the first meta state information from the received one or more pieces of state information. In this system, the generation unit generates the first meta state information according to the first rule stored in the rule storage unit.

In the above example, the rule is expressed by Expression (1), Expression (2), or Expression (3). The meta-presence information to be notified can be flexibly changed by simply changing the rules without changing the design of the IM server to which the cooperation system is connected or the BPM system in which the IM server is incorporated.
The invention 3 is the invention 2, wherein the generation means receives a second rule for generating the second meta-state information from the second state information management device, writes it in the rule storage means, and based on the second rule The second meta state information is generated, and the state information notifying means sends a second meta state identifier for identifying the second meta state information and the second meta state information to the second state information management device. Notice.
A fourth aspect of the invention relates to a first state information management device and a second state information management device that associate and manage one or more state information generated by each provider connected to one or more providers and a state identifier that identifies each state information. Provided is a linkage method executed by a linkage system connected to a state information management device. The method includes the following steps.
A state information receiving step of receiving notification of state information (hereinafter referred to as one or more state information) corresponding to one or more state identifiers from the first state information management device;
A generating step of generating first meta-state information different from each received state information based on the one or more received state information;
A state information notification step of notifying the second state information management device of a first meta state identifier for identifying the first meta state information and the first meta state information;
In response to an inquiry from the second state information management apparatus that has received the reference request for the first meta state information, the reference request for the one or more state information, which is a source of the first meta state information, 1 requesting step to send to the status information management device;
Whether or not the first meta status information can be referred to in response to a response from the first status information management device to the one or more status information reference requests is determined through the second status information management device. A notification step to be transmitted to the requester of the state information reference request.

This method has the same effects as the first aspect.
A fifth aspect of the present invention relates to a first state information management apparatus and a second state information management apparatus that associate and manage one or more state information generated by each of the providers connected to one or more providers and a state identifier that identifies each state information . Provided is a linkage program executed by a computer connected to the state information management apparatus . This program causes the computer to function as the cooperation system of the first aspect. This program has the same effects as the first aspect.
A sixth aspect of the invention provides a computer-readable recording medium on which the cooperation program according to the fifth aspect of the invention is recorded. This recording medium has the same effects as the first aspect.

  By using the present invention, a variety of information can be distributed using the presence information distribution mechanism by the IM system. Various information can be generated by processing and converting the presence information. Moreover, what information is generated can be flexibly changed according to needs.

<Summary of invention>
The cooperation system of the present invention generates new presence information based on presence information (corresponding to state information) managed by one or more IM servers. This new presence information is called meta-presence information (corresponding to meta-state information). For example, if a linkage system is connected to an IM server that manages business status information generated by a BPM system that performs business processing of a company, new meta-presence information can be generated based on the business status information. The generated meta-presence information is managed as presence information of the IM server and subscribed to the user agent of the IM system. By setting the generation method of the meta state information according to the needs independently of the BPM system, various meta state information can be generated according to various needs in the business society. Moreover, when changing the method of generating meta-state information, it is not necessary to make significant changes to the BPM system itself, so the entire system consisting of the BPM system, IM system, and linkage system has a wide range of flexibility and expandability. Can be made.

<First embodiment>
[overall structure]
FIG. 1 is a functional configuration diagram of a cooperative IM system including a cooperative system and an IM system according to the first embodiment of the present invention. The linked IM system shown in FIG. 1 connects to an IM system including an IM server SA and its user agents UA1 and UA2, an IM system including an IM server SB and its user agents UB1 and UB2, and an IM server SA and SB. Includes linkage system CA. In this example, the cooperation system CA is realized on one computer terminal. The IM server and its user agent, and the IM server and the connecting device CA are connected via a network such as the Internet.

  The IM server SA associates and manages presence information PDA1 and PDA2 of the user agents UA1 and UA2. The IM server SB associates and manages the presence information values PDB1 and PDB2 of the user agents UB1 and UB2. UA1 and UA2 are user agent IDs for identifying user agents, and presence IDs for identifying the respective presence information PDA1 and PDA2. Similarly, UB1 and UB2 are user agent IDs and presence IDs. The presence ID includes the network address of the IM server that manages the presence ID. Hereinafter, the presence information value PDA1 specified by the presence ID “UA1” may be simply referred to as presence information UA1.

[Function configuration]
Next, functions of the cooperation system CA and the IM servers SA and SB will be sequentially described with reference to the drawings.
(1) Cooperation System The cooperation system CA has a meta-presence agent 10 and preferably further has a rule table 20. In this example, the cooperation system CA generates meta presence information based on the rules stored in the rule table 20. The metapresence agent 10 includes an agent unit 11 and a generation unit 12. Further, the meta-presence agent 10 preferably has a rule adding unit 13 and a subscribe permission unit 14. When the cooperation system CA handles a plurality of meta-presence information, each meta-presence information is identified by a meta-presence ID, and a plurality of meta-presence agents 10 can be generated so as to correspond one-to-one with the meta-presence ID. In other words, the status information of each metapresence agent 10 is identified by the metapresence ID. Of course, a single metapresence agent 10 can manage a plurality of metapresence IDs and metapresence information. The function of each part of the meta-presence agent 10 and the details of the rule table 20 are as follows.

(A) Agent Part The agent part 11 is roughly divided into a presence information reception function and a meta-presence information notification function.
The agent unit 11 receives notification of presence information from either or both of the IM servers SA and SB. Which IM server receives the notification of presence information depends on a rule for generating meta-presence information. For example, when meta-presence information is generated based on presence information UA1, notification of presence information UA1 is received from IM server SA. Further, for example, when meta-presence information is generated based on presence information UA1 and presence information UB1, notification of presence information UA1 is received from IM server SA, and notification of presence information UB1 is received from IM server SB. That is, when viewed from the IM servers SA and SB, the cooperation system CA functions as a watcher for presence information. The agent unit 11 has a presence buffer 11a for temporarily storing presence information received from the IM servers SA and SB, and the value of the corresponding presence information in the presence buffer 11a is obtained by the presence information update notification. Update.

  The agent unit 11 notifies the meta-presence information generated by the generation unit 12 and the meta-presence ID for identifying the meta-presence information to either or both of the IM servers SA and SB. The meta presence ID includes the network address of the IM server that manages the corresponding meta presence information. The IM server that manages the meta-presence information may be determined in advance when setting the cooperation system CA, or may be determined when a rule for generating the meta-presence information is added, as will be described later. For example, when the user agent UA of the IM server SA adds a rule, meta presence information may be notified to the IM server SA. Similarly, when the user agent UB of the IM server SB adds a rule, the meta-presence information may be notified to the IM server SB (see the rule addition process described later).

  Notification of meta-presence information to the IM servers SA and SB can be performed using a command for notifying presence information from the presentity to the IM server in the IM system. For example, if the metapresence ID is “CA1” and the metapresence information value is “MPD1”, the command “Set CA1, MPD1” is transmitted from the agent unit 11 to the IM server SA and / or IM server SB. Good. The watcher of the first meta-presence information MPD1 notifies the IM server each time the meta-presence information identified by the meta-presence ID “CA1” (hereinafter simply referred to as meta-presence information CA1) MPD1 is updated. Receive from SA. That is, when viewed from the IM servers SA and SB, the cooperation system CA functions as a presentity for generating the meta-presence information CA1.

(B) Generation Unit Based on the one or more presence information received by the agent unit 11, meta-presence information different from each received presence information is generated. In this example, meta-presence information is generated based on rules stored in a rule table 20 described later.
(C) Rule Table The rule table 20 stores a rule for generating meta-presence information based on presence information managed by the IM servers SA and SB in association with a meta-presence ID. The meta presence ID is an identifier of meta presence information. The rule is expressed by, for example, the following formulas (1) to (4).

(CA1) = (UA1) + (UA2) (1)
(CA2) = (UA1) + (UB2) (2)
(CA3) = (UA1) × (UA2) (3)
(CA4) = predetermined value X (4)
In the above formulas (1) to (4), CA1, CA2, CA3, and CA4 are meta-presence IDs, respectively. Further, the rules are further complicated, and for example, when the value of the presence information PDA1 corresponding to the presence ID “UA1” is within a predetermined range, the meta-presence information can be generated according to the above equation (3).

FIG. 2A is a conceptual explanatory diagram of information accumulated in the rule table 20 of the cooperation system CA. In the rule table 20, a metapresence ID and a rule for generating metapresence information corresponding to the ID are associated one-to-one. In this example, it is assumed that the rule for generating the presence information CA1 by the above formula (1) is defined when the cooperative system CA is set (rule table in the initial state).
By providing the rule table 20, the flexibility and expandability of the cooperative IM system can be enhanced. Meta-presence information to be notified by changing the rule settings stored in the rule table 20 without changing the design of the IM server to which the cooperation system CA is connected or the BPM system in which the IM server is incorporated. This is because it can be easily changed.

(D) Rule addition unit The rule addition unit 13 roughly performs rule reception, notification of meta-presence ID to the IM server, and subscription request to the IM server. For ease of explanation, a case where a rule for generating meta-presence information CA2 based on presence information UA1 and UB2 is added is taken as an example.
The rule adding unit 13 receives a new rule from the user agent of the IM servers SA and SB, for example, the user agent UB1. The received rule is stored in the rule table 20. Further, the rule adding unit 13 receives the ID “CA2” of the meta presence information generated by the rule together with the rule. It is preferable that the rule adder, that is, the user agent UB1 has the right to determine the ID of the meta-presence information that is generated by the rule to be added. This is because the user agent UB1 can request a subscription by specifying the metapresence ID notified by the user agent UB1 after adding the rule.

  The rule adding unit 13 notifies the notified meta presence ID “CA2” to the IM servers SA and SB. This is because a new location for managing presence information is generated in the IM server. The notification destination IM server may be a rule addition request source, that is, an IM server SB to which the user agent UB1 is connected. This is because a user agent to which a rule has been added is likely to be a watcher of meta-presence information generated by the rule. Therefore, it is preferable that the meta presence ID “CA2” includes the network address of the IM server SB.

Further, the rule adding unit 13 refers to the rule and determines presence information UA1 and UB2 used for generating the meta presence information CA2 defined by the added rule. Further, the IM server that manages the presence information is requested to subscribe to the presence information UA1 and UB2. In this example, the rule adding unit 13 requests the IM server SA to subscribe to the presence information UA1, and requests the IM server SB to subscribe to the presence information UB2.
When the notification of the presence information UA1 and UB2 is received in response to the request for subscription, the agent unit 11 notifies the IM server SB of the meta-presence information CA2 and its value MPD2. Note that the rule adding unit 13 may accept deletion or change of rules.

FIG. 2B is a conceptual explanatory diagram showing a state after a new rule is added to the rule table 20 shown in FIG. In this figure, a rule for generating meta-presence information CA2 by the sum of presence information UA1 and presence information UB2 is added.
It is preferable to provide the rule adding unit 13 in the linkage system because the meta-presence information that can be notified can be increased after the linkage system is constructed. By accepting additions, deletions, and changes of rules, meta-presence information to be notified can be flexibly changed according to changes in needs.

(E) Subscribe Permission Unit It is preferable that the cooperation system CA further includes a subscribe permission unit 14. The subscription permission unit 14 is roughly divided into an inquiry reception function and a permission transmission function. For ease of explanation, consider a case where the user agent UB1 requests the IM server SB to subscribe to the meta-presence information CA1.
First, the subscription permission unit 14 receives an inquiry from the IM server SB as to whether or not the meta-presence information CA1 may be notified to the user agent UB1.

Next, the subscribe permission unit 14 transmits a response to the inquiry to the IM server SB. If the response is permission to subscribe, the IM server SB adds the user agent UB1 to the watcher of the meta-presence information CA1 (see the watcher table 102 in FIG. 4A described later).
The subscribe permission unit 14 may inquire of the presentity of the presence information UA1 and UA2 that is the basis of the meta-presence information CA1 whether or not to permit the user agent UB1 to subscribe to UA1 and UA2. . When making this inquiry, in response to the response to the inquiry, the IM server SB is notified as to whether or not to subscribe to the meta-presence information CA1.

By inquiring permission for notification of meta-presence information, security for meta-presence information can be enhanced.
(2) IM server The IM servers SA and SB are presence tables 101a and b, watcher tables 102a and b, presence update units 103a and b, presence notification units 104a and b, subscribe processing units 105a and b, and command processing units 106a. , B and session management units 107a, b. The presence table 101 stores a presence ID and a value of presence information in association with each other. The watcher table 102 stores a presence ID and a watcher ID of presence information specified by the ID in association with each other. The presence update unit 103 updates the presence table 101 based on the notification of presence information from the user agent. The presence notification unit 104 transmits presence information to the watcher. The subscribe processing unit 105 registers and deletes a watcher in the watcher table 102. The command processing unit 106 distributes data from the session management unit 107 to each unit, and passes data from each unit to the session management unit 107. The session management unit 107 transmits and receives data between the IM server and another computer.

The presence table 101 and the watcher table 102 when meta-presence information is distributed will be specifically described with reference to FIGS. For ease of explanation, a case where the watcher of the meta presence information CA1 generated based on the presence information UA1 and UA2 is a user agent UB1 is taken as an example. Further, a case where the watcher of the meta presence information CA2 generated based on the presence information UA1 and UB2 is the user agent UB2.
3 and 4 are conceptual explanatory diagrams of the presence table 101 and the watcher table 102 stored in the IM servers SA and SB.

FIG. 3A corresponds to the case where the meta-presence information CA1 is generated based on the presence information UA1 and UA2 in accordance with the rule table 20 shown in FIG. In the presence table 101a of the IM server SA, a presence ID and a value of presence information are stored in association with each other. On the other hand, the meta presence ID “CA1” is stored in the watcher table 102a as a watcher of the presence information UA1 and UA2.
FIG. 4A corresponds to the case where the meta-presence information CA1 is generated based on the presence information UA1 and UA2 according to the rule table 20 shown in FIG. In the presence table 101b of the IM server SB, a presence ID and a value of presence information are stored in association with each other. The value of presence information MPD1 corresponds to the meta presence ID “CA1”. On the other hand, the watcher table 102a stores a user agent UB1 as a watcher of the meta presence information CA1.

That is, according to the rule table 20 of FIG. 2A and the tables of FIG. 3A and FIG. 4A, the meta-presence information CA1 is generated and distributed as follows. Presence information UA1 and UA2 are transmitted to cooperation system CA, and metapresence information CA1 is generated. The generated meta-presence information CA1 is notified to the IM server SB and is distributed to the watcher UB1 from here.
FIG. 3B shows the presence table 101a and the watcher table 102 after the addition of the rules shown in FIG. Corresponding to the meta presence information CA2 generated based on the presence information UA1 and UB1, the meta presence ID “CA2” is added to the watcher of the presence information UA1.

FIG. 4B shows the presence table 101b and the watcher table 102 after the addition of the rules shown in FIG. The value of the presence information MPD2 corresponds to the meta presence ID “CA2”. Further, corresponding to the meta presence information CA2 generated based on the presence information UA1 and UB1, a user agent UB1 is added to the watcher of the meta presence information CA2. Further, the meta presence ID “CA2” is added to the watcher of the presence information UB1.
That is, according to the rule table 20 of FIG. 2B and the tables of FIG. 3B and FIG. 4B, the meta-presence information CA2 is generated and distributed as follows. Presence information UA1, UB2 is transmitted to cooperation system CA, and metapresence information CA2 is generated. The generated meta-presence information CA2 is notified to the IM server SB and is distributed from here to the watcher UB1.

[Process flow]
Next, the flow of processing performed by the cooperative IM system shown in FIG. 1 will be specifically described with reference to FIGS. The main processes performed by the cooperative IM system are (1) subscribe setting process, (2) notification process, and (3) rule addition process. In the following, for ease of explanation, it is assumed that the rule table 20 shown in FIG. 2A is set in the cooperation system CA.
(1) Subscribe Setting Process FIG. 5 is an explanatory diagram showing an example of the flow of the subscribe setting process. In this process, the subscription of the meta presence information CA1 is set. As an example, consider a case where the IM server SB manages meta-presence information CA1, and the user agent UB1 requests to subscribe to the meta-presence information CA1.

Cooperation system CA has memorized rule table 20 shown in Drawing 2 (a) (# 1). Further, the meta presence ID and its value are registered in the presence table 101b of the IM server IB as shown in FIG.
In this state, the user agent UB1 transmits a subscription request for meta-presence information CA1 to the IM server SB (# 3). This subscription request includes the meta-presence ID “CA1”. The meta presence ID “CA1” includes the network address of the IM server SB.

In response to the subscribe request, the IM server SB transmits an inquiry as to whether or not the user agent UB1 may be registered in the watcher of the meta-presence information CA1 to the cooperation system CA (# 5). This inquiry includes the meta-presence ID “CA1” and the user agent ID “UB1”.
When the cooperation system CA receives the inquiry, the cooperation system CA refers to the rule table 20 (# 7). Next, the cooperation system CA specifies IDs “UA1” and “UA2” of presence information (hereinafter referred to as original presence information) that is the basis of the meta-presence information CA1 requested to be subscribed. When enhancing the security of the meta-presence information CA1, it is preferable that the cooperation system CA requests the IM server SA that manages the original presence information to subscribe to the presence information UA1 and UA2 (# 9).

When the IM server SA receives a subscription request from the cooperation system CA, the IM server SA transmits an inquiry to each of the presentities UA1 and UA2, and updates the watcher list when the subscription is permitted (# 11, # 13). . FIG. 3A described above shows a watcher list in this state. That is, the meta presence ID “CA1” is registered as a watcher of the presence information UA1 and UA2. The IM server SA transmits a subscription permission notification of the presence information UA1 and UA2 to the cooperation system CA (# 15).
When the subscription of the original presence information UA1 and UA2 is permitted, the cooperation system CA transmits a subscription permission notification of the meta presence information CA1 to the IM server SB (# 17).

When the IM server SB is permitted to subscribe to the meta-presence information CA1, the IM server SB updates the watcher list (# 19). FIG. 4A described above shows a watcher list in this state. That is, presence ID “UB1” is registered as a watcher of meta-presence information CA1. Thereafter, the IM server SB transmits a subscribe permission notification of the meta-presence information CA1 to the requesting user agent UB1 (# 21).
In the above example, the present presence information UA1 and UA2 of the original presence information are inquired as to whether or not the respective presence information is allowed to be subscribed, but depending on the level of security required for the meta presence information. You can decide whether to make an inquiry.

Through the above processing, the user agent UB1 is registered as a watcher of the meta presence information CA1 in the watcher list of the IM server SB. That is, the meta-presence information CA1 is managed and distributed as one piece of presence information managed by the IM server using the mechanism of the IM system.
(2) Notification Process FIG. 6 is an explanatory diagram showing an example of the flow of the notification process. In this process, meta-presence information CA1 is notified to the watcher UB1 in accordance with the subscribe setting described above. Various notification timings are conceivable, such as when the cooperation system CA is activated, when the original presence information is updated, or when the watcher UB1 is activated. Here, as an example, the case where the cooperation system CA is activated and the time when a part of the original presence information is updated are cited.

The presentities UA1 and UA2 are connected to the IM server SA and are in a state of notifying the IM server SA of their latest presence information values PDA1 and PDA2 (# 31, # 33). Therefore, the values “PDA1” and “PDA2” are registered for the presence IDs “UA1” and “UA2” in the presence table 101a of the IM server SA.
When the cooperation system CA is activated in this state, it connects to the IM servers SA and SB (# 35).

The IM server SA notifies the activated cooperation system CA of the presence information UA1 and UA2 according to the watcher list (# 37).
The cooperation system CA stores the values of the presence information UA1 and UA2 in the presence buffer 11a (# 39). Further, the cooperation system CA refers to the rule table 20 and determines whether there is meta-presence information based on the received presence information (# 41). In this example, since the meta-presence information CA1 is based on the presence information UA1 and UA2, the cooperation system CA calculates the value of the meta-presence information CA1 according to the rule (# 43). The calculated value of meta-presence information is preferably temporarily stored in the presence buffer 11a. The calculated value of meta-presence information and meta-presence ID are notified to the IM server SB (# 45). Receiving this notification, the IM server SB writes the notified value in the corresponding entry of the presence table 101b.

Then, consider a case where the value of the presence information UA1 is updated, for example. The presentity UA1 notifies the new value PDA1 to the IM server SA (# 49). This value is notified from the IM server SA to the cooperation system CA (# 51).
Cooperation system CA updates value PDA1 of presence information UA1 in presence buffer 11a (# 53). Further, the meta presence information CA1 depending on the presence information UA1 is searched from the rule table 20 (# 56), and the value of the meta presence information CA1 is updated according to the rule (# 57). The values of the original presence information UA1 and UA2 are stored in the presence buffer 11a. The updated value is notified to the IM server SB (# 59), and is further notified to the watcher UB1 of the meta-presence information CA1 (# 61).

By the notification process, the meta-presence information is also updated and notified to the watcher in accordance with the setting and updating of the original presence information. As the notification mechanism, the IM system mechanism is used as it is, and the presence information to be notified is processed independently of the original presence information by the cooperation system CA. Therefore, by connecting the cooperative system CA to the IM server, it is possible to notify various meta-presence information according to needs without making a significant design change of the IM system itself.
(3) Rule addition processing FIG. 7 is an explanatory diagram showing an example of the flow of rule addition processing. Here, a case where a new rule is added to the rule table 20 shown in FIG. 2A and the rule table 20 shown in FIG. 2B is generated is taken as an example. Although any user agent can add a rule, for ease of explanation, a case where the user agent UB1 adds a rule will be described below as an example.

First, the user agent UB1 transmits the rule to be added and the meta-presence information ID generated by the rule to the cooperation system CA (# 71). Here, the metapresence ID is “CA2”. This meta-presence ID is preferably selected by the user agent UB1 from among the plurality of spare IDs prepared for the meta-presence ID by the IM server SB.
Coordination system CA stores the received rule in association with metapresence ID in rule table 20 (# 73). FIG. 2B shows a rule table 20 to which rules are added. Further, the cooperation system CA notifies the meta presence ID “CA2” to the IM server SB (# 75).

In response to the notification of the meta presence ID, the IM server SB adds an entry corresponding to the new meta presence information CA2 to the presence table 101b (# 77). Thereby, the IM server SB can manage the new meta presence information CA2.
Further, the rule adder UB1 requests the IM server SB to subscribe to the metapresence CA2 (# 79).
In response to the request, the IM server SB inquires of the cooperation system CA whether or not the user agent UB1 may be registered as a watcher of the meta-presence information CA2 (# 81).

The cooperation system CA refers to the rule of the meta-presence ID “CA2” inquired and requests the IM servers SA and SB to subscribe to the IDs “UA1” and “UB2” of the original presence information (# 85). .
The IM servers SA and SB inquire to each user agent in response to the request for subscription, update the watcher list according to the answer, and send a permission notice to the cooperation system (# 87 to # 97). FIG. 3B shows a watcher list after the meta-presence ID “CA2” is added as a watcher of the presence information UA1. FIG. 4B shows a watcher list after the meta presence ID “CA2” is added as a watcher of the presence information UB2.

When the cooperation system CA receives the subscription permission from the IM servers SA and SB, it transmits a subscription permission notification of the meta-presence information CA2 by the user agent UB1 to the IM server SB (# 99).
The IM server SB updates the watcher list based on the permission notification from the cooperation system (# 101). FIG. 4B shows a watcher list in which the user agent UB1 is registered as a watcher of the meta-presence information CA2. Thereafter, the IM server SB transmits a permission notice in response to the subscribe request from the user agent UB1 (# 103).

Through the above processing, a new rule can be added from any user agent to the cooperation system CA. Further, in this example, addition of a rule is shown, but in the same manner, the cooperative system CA can accept deletion of a rule, that is, deletion of meta-presence information and change of a rule, that is, change of meta-presence information. Therefore, the expandability and flexibility of the cooperative IM system are further improved. For example, the rule table 20 can be flexibly updated in accordance with addition of a new IM server or deletion of an IM server.
[effect]
If the IM servers SA and SB are provided in two different BPM systems, for example, and meta-presence information is generated based on the presence information acquired from the respective presence servers SA and SB, the meta-presence independent of each BPM system and IM server Information can be generated without significantly affecting the design of each BPM system or IM server. Further, the meta-presence information to be generated can be easily and flexibly changed without greatly affecting the design of each BPM system or IM server. As described above, by connecting the cooperation system of the present invention to a plurality of IM servers, the presence information can be flexibly processed and distributed. Further, the distribution destination of meta-presence information can be changed as appropriate according to who needs meta-presence information.

<Second Embodiment>
FIG. 8 is a block diagram illustrating a functional configuration diagram of the cooperative IM system including the cooperative system according to the second embodiment. In this embodiment, the meta-presence agent 10 and the rule table 20 constituting the cooperation system CA are provided in different computer terminals. Furthermore, in this example, the rule table 20 is provided in one of the IM servers to which the cooperation system CA is connected. As shown in this figure, the meta-presence agent 10 and the rule table 20 constituting the cooperation system CA may be on the same computer or different computers.

For example, an IM server and a CA system can be mounted in one IC chip. Further, for example, the IM server and the meta presence agent 10 can be mounted in one IC chip. Further, for example, a CA system can be mounted in one IC chip. That is, the connection form between the cooperation system and the IM system can be changed as appropriate according to needs. Therefore, it is possible to give the cooperative IM system flexibility and expandability from the viewpoint of the connection form.
<Other embodiment examples>
(A) In the first embodiment and the second embodiment, the linkage system CA is connected to a plurality of IM servers, but the linkage system CA can be applied even if there is only one IM server. In that case, meta-presence information different from the presence information collected by the IM server from the user agent can be distributed from the IM server to the user agent.

  (B) A program for executing the above method and a computer-readable recording medium recording the program are included in the scope of the present invention. Here, examples of the recording medium include a computer readable / writable flexible disk, hard disk, semiconductor memory, CD-ROM, DVD, magneto-optical disk (MO), and others.

  FIG. 9 is a conceptual explanatory diagram of the cooperative IM system according to the first embodiment of the present invention. In the first embodiment, the cooperation system CA is connected to the IM server SA and the IM server SB. The IM server SA manages the inventory rate for each product as presence information of the inventory management system. The IM server SB manages alert information to be notified to company members as presence information. Cooperation system CA acquires the stock shortage rate for each product from IM server SA, and generates an alert message corresponding to the stock shortage rate based on rules 1 to 3. The generated alert message is notified to the IM server SB and subscribed by the management team, manager, or person in charge.

There are three types of alert messages for managers, managers, and persons in charge, and are generated according to rule 1, rule 2, and rule 3, respectively. FIG. 10 shows a description example of Rule 1 for generating an alert message for managers. In this example, the rules are described in XML (eXtensible Markup Language). Rule 1 defines that “if the inventory shortage rate is 30% or more, a management alert message“ occurrence of a serious item shortage ”is generated”.
FIG. 11 shows a description example of rule 2 for generating an alert message for managers. Rule 2 defines that “if the inventory shortage rate is 5% or more and less than 30%, an alert message“ problem level shortage occurs ”for managers is generated”.

FIG. 12 shows a description example of rule 3 for generating an alert message for a person in charge. Rule 2 defines that “if the inventory shortage rate is less than 5%, an alert message“ general level out-of-stock occurrence ”for the person in charge is generated”.
The alert message is meta-presence information newly generated from an inventory shortage rate managed by the IM server SA. At least one and at most three alert messages are generated based on the inventory shortage rate. Not only the inventory shortage rate, which is presence information, but also notifications can be converted into alert messages that are more useful meta-presence information. In addition, the content of the alert message and its notification destination can be adjusted according to the inventory shortage rate. In this way, by processing and converting presence information according to needs, a variety of meta-presence information can be distributed to the subject who needs the information.

  FIG. 13 is a conceptual explanatory diagram of the cooperative IM system according to the second embodiment of the present invention. In the second embodiment, the cooperation system CA is connected to the IM servers SA, SB, and SC. The IM server SA manages the transmission state of the electronic mail shipping slip as presence information of the inventory management system. The IM server SB manages the availability of the mailbox as presence information of the electronic mail system. The IM server SC manages alert information for the person in charge of the delivery company as presence information of the delivery management system. The cooperation system CA acquires a slip state from the IM server SA and a mail box empty state from the IM server SB, and generates an alert message indicating that the shipping slip cannot be sent by e-mail based on the rule.

  FIG. 14 shows a rule description example. As in the first embodiment, the rules are described in XML. This rule defines that “when a shipping slip is sent by e-mail, there is no available mailbox, a“ slip sending error ”message is notified”. The alert message generated by this rule corresponds to meta-presence information generated from the presence information of the IM servers SA and SB. Based on the transmission state of the electronic mail slip and the free state of the electronic mail box, meta-presence information indicating events that the two mean can be generated and distributed.

  FIG. 15 is a conceptual explanatory diagram of the cooperation system according to the third embodiment of the present invention. In the third embodiment, the cooperation system CA is connected to the IM servers SA and SB. The IM server SA manages vehicle system presence information that monitors various sensors mounted on the vehicle. The IM server SB provides presence information of sensors (in this example, engine oil sensor, battery sensor, gasoline sensor) maintained by the company B to the company B that provides maintenance services for various sensors managed by the vehicle system. ing. Cooperation system CA acquires the presence information of a sensor from IM server SA, and converts it into a numerical value in a range of 1 to 10 indicating the health level of the sensor based on a rule. The numerical value of the sound level generated by the cooperation system CA is notified to the IM server SB of company B. Therefore, the employee of company B can always grasp the state of the sensor maintained by the company and can provide a maintenance service suitable for the state of the sensor.

  When the maintenance companies of the various sensors mounted on the vehicle are different, the presence information of the sensors corresponding to the respective maintenance companies can be similarly notified to the respective maintenance companies. Further, if a rule is set for each maintenance company, each maintenance company can acquire presence information desired by the company through the cooperation system CA.

  FIG. 16 is a conceptual explanatory diagram of the cooperation system according to the fourth embodiment of the present invention. In the fourth embodiment, the cooperation system CA is connected to the IM servers SA and SB. The IM server SA is provided in a home server that monitors various electrical devices installed in the home, and manages presence information of the various electrical devices. The IM server SB provides presence information to the M company that provides household electric appliances (in this example, an air conditioner and a refrigerator). Cooperation system CA acquires the presence information of the electric device from IM server SA, and converts it into presence information indicating the state of the electric device provided by company M based on the rule. Further, the IM server SB is notified of the converted presence information of the electric device. Therefore, the employee of company M can always grasp the state of the electric equipment provided by the company and can provide a service suitable for the grasped state. If company M sets the conversion rule for presence information in cooperative system CA, for example, if the refrigerator breaks down, company M can determine the cause from the presence information and provide a quick maintenance service to the customer. Further, in the same manner, according to the rules of each company that provides various electric devices to the home, it is possible to provide each company with the presence information of the products provided by the company.

<Appendix>
The following additional remarks are disclosed for the first, second and other exemplary embodiments and Examples 1-4.
(Appendix 1)
A linked system connected to a first status information management device that manages one or more status information respectively generated by one or more providers and a status identifier that identifies each status information in association with each other;
Status information receiving means for receiving notification of status information corresponding to one or more status identifiers (hereinafter referred to as one or more status information) from the first status information management device;
Generating means for generating first meta-state information different from each received state information based on the one or more received state information;
Status information notification means for notifying the first status information management device of a first meta status identifier for identifying the first meta status information and the first meta status information;
Cooperation system with

(Appendix 2)
Rule storage means for storing a first rule for generating the first meta-state information from the received one or more pieces of state information;
The generation means generates the first meta state information according to the first rule stored in the rule storage means.
The linkage system according to appendix 1.
(Appendix 3)
A rule adding means for receiving a new second rule from an arbitrary first provider connected to the first state information management device, and storing the received second rule in the rule storage means;
Information notification requesting means for requesting the first state information management apparatus to notify the second state information used for generating the second meta state information defined by the added second rule;
Meta status identifier notifying means for notifying the first status information management device of a second meta status identifier for identifying the second meta status information and the second meta status information;
The linkage system according to Appendix 2, wherein the generation unit generates the second meta-state information according to the second rule.

  Since rules can be added in this linkage system, the meta-presence information that can be notified can be increased after the linkage system is constructed. Further, the rule adding means may accept deletion or change of rules. By accepting additions, deletions, and changes of rules, meta-presence information to be notified can be flexibly changed according to changes in needs. The user agent that adds the rule may notify the identifier of the meta-presence information that is generated by the rule together with the notification of the rule. This is because, after the rule is added, the user agent can request a subscription by specifying the meta-presence information identifier notified by the user agent.

(Appendix 4)
When the first status information management apparatus receives a notification request for the first meta status information from any provider, the first status information management apparatus relates to the notification of the first meta status information from the first status information management apparatus to the provider. The apparatus further comprises subscription permission means for receiving an inquiry from the first state information management apparatus and instructing the first state information management apparatus to notify the provider of the first meta state information in response to the inquiry. 1. The cooperation system according to 1.
The user agent UA1 who wants to see the first meta-presence information requests the IM server SA to subscribe. Receiving this, the IM server inquires of the cooperation system whether the first meta presence information may be notified to the user agent UA1. The cooperation system responds, for example, with OK to this inquiry. If the first meta presence information identifier CA1 is included in this response, the IM server registers CA1 in the presence table in response to this response. Further, the IM server SA registers the user agent UA1 as a watcher of the first meta presence information. By asking the cooperation system for permission to distribute meta-presence information, it is possible to increase security for the distribution of meta-presence information.

(Appendix 5)
And further connected to a second status information management device that manages one or more status information respectively generated by one or more providers and a status identifier that identifies each status information in association with each other,
The status information receiving means further receives a notification of status information (hereinafter referred to as 1 or more status information) corresponding to one or more status identifiers from the second status information management device,
The generation means is different from each status information received based on one or more status information received from the first status information management device and / or one or more status information received from the second status information management device. Generating third meta-state information;
The status information notification unit notifies the first status information management device and / or the second status information management device of a third meta status identifier for identifying the first meta status information and the third meta status information. To
The linkage system according to appendix 1.

The cooperation system may acquire presence information from a plurality of IM servers SA and SB and generate meta presence information based on the presence information.
For example, meta-presence information may be generated based on presence information acquired from two presence servers SA and SB provided in two different BPM systems. Since meta-presence information is generated independently of each BPM system or IM server, the presence link method between BPM systems can be flexibly changed without affecting each BPM system or IM server.

The cooperation system connected to the IM servers SA and SB can notify meta-presence information to both or one of the IM servers SA and SB. If either one of them is notified only to, for example, the IM server SA, the user agent UA of the IM server SA can be a watcher for meta presence information. If the notification is made to both IM servers SA and SB, the user agents UA and UB of the IM servers SA and SB can both be meta-presence information watchers.
By connecting the cooperation system to a plurality of IM servers, presence information can be flexibly processed and distributed.

(Appendix 6)
This is a linkage method executed by a linkage system connected to a first status information management device that manages one or more status information generated by one or more providers and a status identifier that identifies each status information in association with each other. And
A state information receiving step of receiving notification of state information corresponding to one or more state identifiers (hereinafter referred to as one or more state information) from the first state information management device;
Generating a first meta-state information different from each received state information based on the one or more received state information;
A status information notification step of notifying the first status information management device of a first meta status identifier for identifying the first meta status information and the first meta status information;
Linking method including.

(Appendix 7)
A linkage program executed by a computer connected to a first status information management apparatus that manages one or more status information generated by one or more providers and a status identifier that identifies each status information in association with each other. ,
Status information receiving means for receiving notification of status information (hereinafter referred to as one or more status information) corresponding to one or more status identifiers from the first status information management device;
Generation means for generating first meta state information different from each received state information based on the received one or more state information, a first meta state identifier for identifying the first meta state information, and the first Status information notification means for notifying the first status information management device of meta status information;
A linkage program for causing the computer to function as

(Appendix 8)
Records a cooperation program executed by a cooperation system connected to a first state information management apparatus that manages one or more state information generated by one or more providers in association with a state identifier that identifies each state information. A computer-readable recording medium,
A state information receiving step of receiving notification of state information corresponding to one or more state identifiers (hereinafter referred to as one or more state information) from the first state information management device;
Generating a first meta-state information different from each received state information based on the one or more received state information;
A status information notification step of notifying the first status information management device of a first meta status identifier for identifying the first meta status information and the first meta status information;
The computer-readable recording medium which recorded the cooperation program which performs this.

Functional configuration diagram of a cooperative IM system to which the cooperative system CA according to the first embodiment is applied (A) Rule table (initial state) stored in the cooperation system CA in FIG. 1 (b) After adding a rule (A) IM server SA presence table and watcher table (initial state) (b) IM server SA presence table and watcher table (after adding rules) (A) IM server SB presence table and watcher table (initial state) (b) IM server SB presence table and watcher table (after adding rules) Explanatory drawing which shows an example of the flow of the subscription setting process which the cooperation IM system of FIG. 1 performs Explanatory drawing which shows an example of the flow of the notification process which the cooperation IM system of FIG. 1 performs Explanatory drawing which shows an example of the flow of the rule addition process which the cooperation IM system of FIG. 1 performs Functional configuration diagram of a cooperative IM system to which a cooperative system CA according to the second embodiment is applied Conceptual explanatory diagram of a cooperative IM system according to the first embodiment Explanatory drawing which shows an example of the rule 1 in FIG. Explanatory drawing which shows an example of the rule 2 in FIG. Explanatory drawing which shows an example of the rule 3 in FIG. Conceptual diagram of a cooperative IM system according to the second embodiment Explanatory drawing which shows an example of the rule in FIG. Conceptual explanatory diagram of a cooperative IM system according to a third embodiment Conceptual explanatory diagram of a cooperative IM system according to the fourth embodiment.

Explanation of symbols

CA: cooperation system 10: meta-presence agent 11: agent part 12: generation part 13: rule addition part 14: subscribe permission part 20: rule table

Claims (6)

A linkage system connected to the first state information management device and the second state information management device,
The first state information management device and the second state information management device correspond to one or more state information generated by each of the providers connected to one or more providers and a state identifier for identifying each state information. Manage,
Status information receiving means for receiving notification of status information corresponding to one or more status identifiers (hereinafter referred to as one or more status information) from the first status information management device;
Generating means for generating first meta-state information different from each received state information based on the one or more received state information;
State information notification means for notifying the second state information management device of a first meta state identifier for identifying the first meta state information and the first meta state information;
In response to an inquiry from the second state information management apparatus that has received the reference request for the first meta state information, the reference request for the one or more state information, which is the source of the first meta state information, Request means for transmitting to the state information management device;
In response to a response from the first status information management apparatus to the one or more status information reference requests, whether or not the first meta status information can be referred is determined through the second status information management apparatus. A notification means for transmitting to the requester of the information reference request;
Cooperation system with Rule storage means for storing a first rule for generating the first meta-state information from the received one or more pieces of state information;
The generation means generates the first meta state information according to the first rule stored in the rule storage means.
The cooperation system according to claim 1. The generation unit receives a second rule for generating second meta state information from the second state information management device, writes the second rule in the rule storage unit, and generates the second meta state information based on the second rule. And
The status information notification means notifies the second status information management device of a second meta status identifier for identifying the second meta status information and the second meta status information.
The cooperation system according to claim 2. A first state information management device and a second state information management device for managing one or more state information generated by each provider connected to one or more providers and a state identifier for identifying each state information in association with each other A linkage method executed by a linkage system connected to
A state information receiving step of receiving notification of state information corresponding to one or more state identifiers (hereinafter referred to as one or more state information) from the first state information management device;
Generating a first meta-state information different from each received state information based on the one or more received state information;
A status information notification step of notifying the second status information management device of a first meta status identifier for identifying the first meta status information and the first meta status information;
In response to an inquiry from the second state information management apparatus that has received the reference request for the first meta state information, the reference request for the one or more state information, which is the source of the first meta state information, A requesting step to send to the state information management device;
In response to a response from the first status information management apparatus to the one or more status information reference requests, whether or not the first meta status information can be referred is determined through the second status information management apparatus. A notification step to send to the requester of the information reference request;
Linking method including. A first state information management device and a second state information management device for managing one or more state information generated by each provider connected to one or more providers and a state identifier for identifying each state information in association with each other A linked program executed by a computer connected to
Status information receiving means for receiving notification of status information (hereinafter referred to as one or more status information) corresponding to one or more status identifiers from the first status information management device;
Generating means for generating first meta-state information different from each received state information based on the one or more received state information;
Status information notification means for notifying the second status information management device of a first meta status identifier for identifying the first meta status information and the first meta status information;
In response to an inquiry from the second state information management apparatus that has received the reference request for the first meta state information, the reference request for the one or more state information, which is the source of the first meta state information, is sent to the first state. A request means for transmitting to the information management device, and whether or not the first meta status information can be referred to in response to a response from the first status information management device to the one or more status information reference requests; A notification means for transmitting to the request source of the reference request for the first meta status information through the status information management device;
A linkage program for causing the computer to function as A first state information management device and a second state information management device for managing one or more state information generated by each provider connected to one or more providers and a state identifier for identifying each state information in association with each other A computer-readable recording medium that records a cooperative program executed by a cooperative system connected to the computer,
A state information receiving step of receiving notification of state information corresponding to one or more state identifiers (hereinafter referred to as one or more state information) from the first state information management device;
Generating a first meta-state information different from each received state information based on the one or more received state information;
A status information notification step of notifying the second status information management device of a first meta status identifier for identifying the first meta status information and the first meta status information;
In response to an inquiry from the second state information management apparatus that has received the reference request for the first meta state information, the reference request for the one or more state information, which is the source of the first meta state information, A requesting step to send to the state information management device;
In response to a response from the first status information management apparatus to the one or more status information reference requests, whether or not the first meta status information can be referred is determined through the second status information management apparatus. A notification step to send to the requester of the information reference request;
The computer-readable recording medium which recorded the cooperation program which performs this.

Images