JP2005259134A - Information sharing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve a problem wherein, when state information of a user using each client terminal is shared in a network system including a server machine and a plurality of client terminals, only the change of the state information is notified in updating the state information, so that action associated with the state change can not rapidly be carried out. <P>SOLUTION: In this application, when change notification of state information of another user is set, a message to the another user is previously set; and, when an update of state information of the user occurs, the message is notified to the user, whereby the content intended to be reported to the user can immediately be notified in changing the state when the user has changed the state information. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an improvement of a network system for sharing information from a plurality of client terminals by using a common server machine, and in particular, sharing status information such as the presence status of each client terminal individual user, The present invention relates to an information sharing system for improving the efficiency of activities.

  In recent years, with the spread of personal computers and the development of networks, it has become possible to exchange data between terminals, and an environment in which various kinds of information can be shared while living has become widespread.

  Taking the presence status as an example of the status information, the environment is used, the presence status of the user of each client terminal is centrally managed by the server machine, and a function for referring to the information on the client terminal is provided. Therefore, an attendance state management system that can confirm the presence state of another user while staying is proposed.

  An example of such an attendance management system is disclosed in Japanese Patent Laid-Open No. 8-87855.

  The configuration is a system in which a plurality of terminals are connected via a network, and a server machine centrally manages the presence status of users of each client terminal.

When a change in the presence state occurs, the user of each client terminal updates the presence state information on the server machine through the own state setting unit. The server machine changes the presence state of the user and transmits the presence state of the user to the connected client terminal.
Japanese Patent Laid-Open No. 8-87855

  In such a conventional technology, the user knows that the user who has left the seat has returned to the seat, for example, by receiving notification that the status of the other user has been changed, and notifies the user. You can get in touch. However, if the user is absent when receiving a notification that the status of another user has been changed, the opportunity to contact him / her will be missed.

  The above problem is caused only by notifying that the state information is changed when the state information is updated.

  In the present invention, when setting a change notification of the status information of another user, a message for the other user is also set, and when the status information of the user is updated, the user By notifying the message, when the user changes the status information, the contents to be notified to the user can be notified immediately when the status is changed.

  Thus, an action that is desired to be performed in accordance with the state change can be performed in accordance with the state change, and the efficiency of the business can be improved.

    That is, the present invention relates to a message notification method in a network system in which a server machine and a plurality of client terminal devices are connected so as to be able to communicate with each other, and user status information notified from each client terminal is transmitted to each user terminal. And a function for notifying the client terminal of the other user who wishes to refer to the status information of the user of the client terminal, When changing the status information of a user of a client terminal, if a message is registered from the client terminal of another user to the user of the client terminal, the registered message is notified to the client terminal It is characterized by that.

  As described above, in the present invention, in the network system in which the server machine and the plurality of client terminal devices are connected to be able to communicate with each other, the status information of each user can be changed by sharing the status information of each user. It becomes possible to recognize in real time, and further, it is possible to quickly perform an action according to the change of the state information.

  Furthermore, in the invention of claim 3, by performing the status information change notification and the message display at the client terminal, it is possible to reduce the load on the server machine and prevent the delay of the status information change notification and message display. It becomes.

  An embodiment of the present invention will be described by taking an attendance state management system as an example.

  The configuration of an embodiment of the present invention is shown in FIG.

  This configuration includes a plurality of client terminals 20 and 30 and a server machine 10 connecting them, and each client terminal 20 and 30 and the server machine 10 are connected via a LAN (L1).

  The server machine 10 includes an attendance state management table 11 and an attendance state information management unit 12.

  As shown in FIG. 2, the presence status management table 11 stores the presence status information 40 of the users of the client terminals 20 and 30 and request data 50 managed in association with each user. .

  The presence status information 40 manages the following items.

1. User name 41: Name of the user who uses the client terminals 20, 30 Attendance state 42: Not only presence / absence, but also identifies multiple states such as return immediately / meeting / others. In this example, the presence is symbolized as "1", absence is "2", return immediately is "3", the meeting is "4", and others are symbolized as "5". Fig. 2 shows that Mr. Okuyama is present, Mr. Suzuki is absent, and Mr. Tanaka is in a meeting.

3. Memo 43: Information entered by the user such as a simple schedule. Setting date / time 44: Date / time when the presence status information 40 is set / updated. Communication information 45: Phone number, e-mail address, FAX number required for communication execution Request data 50 is managed in association with the user, and is used as a notification condition for presence status information when updating presence status information. .

1. Reference user name 51: Name of the user who is referring to the presence status of the user. 2. Network address 52: Network address of the client terminal 20,30 used by the reference user Status notification flag 53: A notification condition to the reference user when the presence status is changed is set.

                  Based on the application from the reference user, a notification is made when the presence state 42 of the reference partner is changed, or notification is made when the reference partner is in a specific state. In this example, when notifying in any state, the 7th bit is set to “1”, and only when a specific state such as presence / absence / returning immediately / meeting / others is notified In each case, the 0th to 4th bits are set to "1". A plurality of these can be specified at the same time. When only a specific state change is instructed, not only an update of the presence state information but also a message that a change in the presence state has occurred is notified (FIG. 16). In this example, according to the change of Mr. Suzuki's presence status, Mr. Okuyama's client terminal only automatically updates Mr. Suzuki's presence status information and the display on screen 63. As Occupied's presence status information is updated, a message indicating the occurrence of a change is displayed on the screen in any state (FIG. 16). On Mr. Ota's client terminal, only when Mr. Suzuki is in the presence status, A message indicating that a change has occurred is displayed on the screen along with the update (FIG. 16).

    4). Simple message 54: The content of the message that the reference user wants to notify the user is set.

    5). Message notification condition 55: 4. 2. When to display the simple message of the item Store the same contents as the term.

    6). Message confirmation flag 56: 4. Stores whether the simple message of the term has been read by the other party. In this example, the 0th bit is set to “0” when not yet read, and “1” is set to the 0th bit when already read.

  The presence status information management unit 12 performs management of the presence status management table 11 and transmission / reception of presence status information 40 (including request data 50) of each user.

  Each client terminal 20, 30 has a partner state display unit 22, 32, a self state setting unit 21, 31, and further a communication execution unit 23, 33.

  The partner status display units 22 and 32 acquire the presence status information 40 managed by the server machine 10 to display the desired partner's presence status 42 and set the request data 50. It has a function of requesting the communication execution units 23 and 33 to execute communication after confirmation.

  The own state setting units 21 and 31 have a function of notifying the server machine 10 of a user interface for displaying and changing his / her presence state and change information when the own state is changed.

  The communication execution units 23 and 33 have a function of executing various communication means such as telephone / mail / FAX in response to requests from the partner status display units 22 and 32.

  FIG. 3 is a screen example of the own state setting units 21 and 31, the partner state display units 22 and 32, and the communication execution units 23 and 33 in the client terminals 20 and 30.

  The screen 61 displays menus for various operations of the presence status management system. By selecting a menu name with a mouse or the like, a lower menu or a detailed operation screen is displayed.

  The screen 62 is a menu for selecting a communication means. When the desired communication means is selected with a mouse or the like, the communication execution section is activated through the partner status display sections 22 and 32. The same operation can be performed by selecting [Communication] in the menu of the screen 61.

  The screen 63 is a screen on which the presence status of the reference partner is displayed by the partner status display units 22 and 32, and is a picture showing the user name 41 and the presence status 42 for each user registered as the reference partner. And the first line of the memo 43 is displayed. Further, by selecting a reference partner with a mouse or the like, it is possible to refer not only to the first line but also to the contents set in the memo 43. The NEW button 66 at the bottom of the screen is used to instruct the displayed presence status display to be updated. The screen 67 displays the time when the latest state was last referenced.

  The screen 64 is an interface screen for displaying / updating the self status in the self status setting units 21 and 31. A circle or the like to the left of the word indicating the presence status such as presence / absence on the right side is a mouse or the like. By selecting, the present attendance state is set. Depending on the setting of the presence state, registration / update of the presence state 42 is awaited, and a picture representing the set state is displayed on the left side.

  The screen 65 is a screen for the user to input the memo 43 such as his / her schedule, and the memo 43 set on the screen 65 is registered / updated by the memo registration button 68.

  FIG. 5 is an example of the presence status display lists 24 and 34 on the client terminals 20 and 30. The presence status display list includes self information 71 and a partner presence status reference list 72.

  The own information 71 manages the following information.

1. DIRNAME =: Name of the user who uses the client terminal (unique in the system)
2. 2. SERVERNANE =: Name of the server to which the client terminal is connected wtop = and wleft =, wright =, wbottom =: Display position of own state on screen 60 The following information is managed in the partner presence state reference list 72.

    1. awperson1-9: Name of the user referring to the user.

    The name set in [DIRNAME =] of own information 71 is stored. Created from the reference user name 51 of the request data 50. In this example, 9 people are registered, and the integer at the end of awperson is incremented according to the number of people registered.

    2. [Reference user name]: 1. 2. For each reference user name registered in section 3, From item 6. Header to set information up to the term.

    3. name =: Specifies the name to be displayed on the screen 63. How to specify is free.

    4). dirname =: Name of the referee.

    5). args =: Stores the display position on the screen 63.

    6). color =: Specifies the color to be displayed on the screen 63. In this example, “1” is set to display in red, “2” is set to display in green, and “3” is set to display in blue.

    7). awareness: Header to indicate the delimiter of reference partner information.

    8). number =: Stores the number of reference users. In this example, it is shown that there are nine users referring to Mr. Okuyama.

  Prior to detailed description, an information transmission procedure of the present system will be described with reference to FIG.

  FIG. 4 illustrates a case where the user of the client terminal A20 refers to the user of the client terminal B30.

  This system is roughly divided into the following two functions.

1. Opponent status reference function 400
2. Self-state update function 401
First, the partner state reference function 400 will be described.

  The partner status reference function 400 is mainly composed of three functions.

(1) Attendance status reference function 410
(2) Request data setting function 450
(3) Communication execution request function 460
[Attendance status reference function 410]
There are the following three patterns for presence status reference.

(a) First reference 420
(b) Refer to latest status 430
(c) Automatic status notification 440
<First reference 420>
The user of the client terminal A20 on the referencing side makes an application for referring to the user of the client terminal B30, so that the reference partner registration request 421 is sent from the partner state display unit 22 to the presence state information management unit of the server machine 10. Send to 12. In response to a request from the client terminal A20, the presence status information management unit 12 of the server machine 10 registers information about the user of the client terminal A20 in the request data 50 of the user of the client terminal B30 (reference partner registration 422). At the same time, the presence status information 40 and request data 50 of the user of the client terminal B are sent to the partner status display unit 22 of the client terminal A20. The client terminal A20 receives the presence status information 40 and the request data 50 sent from the presence status information management unit 12 of the server machine 10, and displays the presence status of the user of the client terminal B30 (reference partner status) Display 423).

The registered reference partner displays the presence status at the time of reference on the screen 63 in FIG. 3 (however, if the automatic status notification function in (2) above is used, the latest status is always displayed). )
<Refer to latest status 430>
When the user of the client terminal A20 on the reference side refers to the latest attendance state of the user who is performing reference partner registration 422, such as the user of the client terminal B30, the NEW button 66 at the bottom center of the screen in FIG. When the user clicks, for example, the latest status display request 431 is sent from the partner status display unit 22 to the presence status information management unit 12 of the server machine 10. The presence status information management unit 12 of the server machine 10 receives a request from the client terminal A20, and based on the registered request data 50, the presence of all registered reference partners including the user of the client terminal B30. The seat status information 40 is extracted from the presence status management table 11 and sent to the partner status display unit 22 of the client terminal A20 (reference partner status sending 432). The partner status display unit 22 of the client terminal A20 receives the presence status information 40 sent from the presence status information management unit 12 of the server machine 10, and redisplays the presence status of all reference partners of the client terminal A20. (Reference partner status display 433).
<Automatic status notification 440>
When the reference partner is registered, the notification level is designated according to the subsequent change in the presence state of the reference partner (request data setting 450), so that the user of the client terminal B30 is in the presence state. When the information 40 is updated, the updated contents can be sent to the client terminal A20 based on the request data 50. This is because when the user of the client terminal B30 on the reference side changes its own state, the own state setting unit 31 issues the own state update notification 471 to the server machine 10, and the server machine 10 that has received the notification The presence status information management unit 12 updates the presence status information 40 of the user of the client terminal B30 (attention status information update 472), and the request data 50 is sent to the own status setting unit 31 of the client terminal B30. This is realized by (request data transmission 473).

The own state setting unit 31 of the client terminal B30 selects a user to be notified of the update of the presence state based on the request data 50 sent from the server machine 10 (request data confirmation 441). For example, the presence status information 40 of the user of the client terminal B30 is sent to the partner status display unit 22 of the client terminal A20 (status update notification 442). The partner status display unit 22 of the client terminal A20 redisplays the presence status of the user of the client terminal B30 based on the presence status information 40 sent from the client terminal B30 (status update notification display 443).
[Request data setting function 450]
After registering a partner who refers to the presence state, it is possible to know in real time the state change of the set partner by automatically notifying when the presence state of the reference partner is updated. When the user of the client terminal A20 sets the notification level when the user of the client terminal B30 as the reference partner is updated, the partner status display unit 22 sets the request data setting 451 to the presence of the server machine 10. It is sent to the status information management unit 12. The presence status information management unit 12 of the server machine 10 receives the request and sets the applied notification level in the request data 50 in association with the user of the client terminal B30 (request data registration 452). Based on the request data 50, the state automatic notification 440 in the item 3) of the preceding item (1) is performed.
[Communication execution request function 460]
After confirming the presence state, communication such as telephone, e-mail, FAX is performed according to the state. After confirming the presence of the user of the client terminal B30, the user of the client terminal A20 selects, for example, a telephone by selecting a communication means using the [Communication] on the screen 61 in FIG. Then, the user of the client terminal B30 acquires the telephone number 46 from the communication information 45 registered in advance, and requests the communication execution unit 23 to execute it (communication execution request 461). As a result, the communication execution unit 23 is activated, and the user of the client terminal B30 can be called (communication reception 462).

  Next, the self-state update function will be described.

    The self-state update function is mainly composed of two functions.

(1) Attendance status update function 470
(2) Attendance status change notification function 480
[Attendance status update function 470]
The presence status update function will be described starting from the user of the client terminal B30 on the referenced side.

  When the user's presence status changes, the user of the client terminal B30 changes his / her state on the own state update screen of the screen 64 of FIG. Is sent to the presence status information management unit 12. The presence status information management unit 12 of the server machine 10 receives the notification, updates the presence status information 40 of the user of the client terminal B30 (attention status information update 472), and requests data 50 managed in association with it. Is transmitted to the client terminal B30 (request data transmission 473).

[Attendance status change notification function 480]
The own state setting unit 31 of the client terminal B30 selects a user who should be notified of the change of own state based on the request data 50 sent from the presence state information management unit 12 of the server machine 10 (request data). Confirmation 481), in this example, the presence status information 40 is sent directly to the client terminal A20 (status update notification 482). The partner status display unit 22 of the client terminal A20 redisplays the latest status of the reference partner based on the presence status information 40 sent from the own status setting unit 31 of the client terminal B30 (status update notification display 483). . This is a function linked to the state automatic notification 440 in the partner state reference function 410.

  The above is the information transmission procedure of this system.

  Next, each function will be described in detail using a flowchart.

  6, 7, and 8 are flowcharts showing the processing of the own state setting units 21 and 31 of the client terminals 20 and 30, and FIGS. 9, 10, and 11 are the partner state display units 22 and 32 of the client terminals 20 and 30. FIG. 12, FIG. 13, FIG. 14 are processing flowcharts showing processing of the presence status information management unit 12 of the server machine 10.

The user of the client terminal A20 (reference side) in FIGS. 1 and 4 is Mr. Okuyama in the presence management table of FIG. 2, and the user of the client terminal B30 (reference side) is in the presence management table of FIG. Basically, Mr. Suzuki is assumed.
[Activation of presence status information management unit 12]
When the presence status information management unit 12 on the server machine 10 is activated, the presence status information 40 and the request data 50 saved in the backup file 13 are read and expanded in the presence status management table 11 (see FIG. 12 Step 302). Thereafter, it waits for a request from the client terminals 20 and 30 (step 303 in FIG. 12). On the contrary, when the end is instructed, the contents of the presence status management table 11 are stored in the backup file 13 and the process ends (steps 304 and 305 in FIG. 12).
[Activation of self-status setting unit 21, 31]
A description will be given by taking the client terminal A20 as an example. When the own state setting unit 21 of the client terminal A20 is activated, first, in order to obtain the own user name, the value set in [DIRNAME =] of the own information 71 in the presence state display list 24 of FIG. In this example, "Satoshi Okuyama") is read. Here, if the user name is not set in the presence status display list 24, a screen prompting the user to input is displayed (step 102 in FIG. 6). When the own user name is acquired, this is used as a parameter to request the latest attendance state information 40 in the present state from the attendance state information management unit 12 on the server machine 10 (step 103 in FIG. 6). Upon receiving the request, the presence status information management unit 12 of the server machine 10 uses the passed user name as a key and the presence of the user (Mr. Okuyama) of the client terminal A20 from the presence status management table 11. The seat status information 40 is acquired and sent to the client terminal A20 (steps 307 and 308 in FIG. 12). The own state setting unit 21 of the client terminal 20 displays the presence state of the user of the client terminal A20 (Mr. Okuyama) based on the presence state information 40 sent from the server machine 10 (steps 104 and 105 in FIG. 6). . At this time, if there is no presence status information 40 of the user (Mr. Okuyama) of the client terminal A20 in the presence status management table 11 of the server machine 10, the initial value (the presence status 42 is "attended", other information is (None) is set, and a new registration of the own state is requested to the attendance state information management unit 12 on the server machine 10 (steps 104 and 106 in FIG. 6), and at the same time, the own state is displayed (step 107 in FIG. 6). Upon receiving this request, the presence status information management unit 12 of the server machine 10 adds the presence status information 40 to the presence status management table 11 (steps 309 and 310 in FIG. 12). Thereafter, the own state setting unit 21 of the client terminal 20 waits for an update of the own state (step 108 in FIG. 6).

A screen example of the above operation is a screen 64 in FIG. This example is the screen of the client terminal A20, and Mr. Okuyama is registered as the own user. On the screen 64, the name and presence status of Mr. Okuyama who is the user of the client terminal A20 are displayed. The presence status is set by pointing the left side of the presence status type with a mouse or the like. The picture on the left of the presence status type is displayed according to the set presence status.
[Activation of partner status display units 22 and 32]
When the partner status display units 22 and 32 are activated, the presence status display lists 24 and 34 stored in the client terminals 20 and 30 are read (step 202 in FIG. 9). The other party's presence status reference list 72 (Fig. 5) in the presence status display list 24, 34, the user name, and the network address of the client terminal 20, 30 are used as parameters to send the partner status reference request to the server machine 10. It is sent out (step 203 in FIG. 9). The presence status information management unit 12 on the server machine 10 searches the request data 50 associated with the reference partner user in the presence status management table 11 with the passed reference user name, and the user name Is registered (steps 314, 315, and 317 in FIG. 13). If the own user name is registered, the network address 52 of the own client terminal 20 or 30 is updated (steps 318 and 321 in FIG. 13). If not registered, the own user name and own client terminal are entered in the request data 50 column. The network addresses 52 of 20,30 are added (steps 318-319 in FIG. 13). Further, the presence status information 40 of the reference partner is set in the temporary area (steps 320 and 323 in FIG. 13). After confirming that all of the reference partners registered in the partner presence status reference list 72 have been processed (step 315 in FIG. 13), the presence status information 40 of the reference partner set in the temporary area is stored in the client terminal 20. , 30 (step 316 in FIG. 13). The partner status display units 22 and 32 of the client terminals 20 and 30 display the presence status of each reference partner based on the presence status information 40 sent from the server machine 10 (step 204 in FIG. 9). This display example is the screen 63 of FIG. Each partner's appearance is indicated by a picture (the position set by [args =] and the color set by [color =] in Fig. 5) together with the name of the opponent (name set by [name =] in Fig. 5). Displayed. The presence status can also be displayed in text. Below the name, the first line of the contents of the memo 43 input by each user is displayed. When it is desired to refer to all of the memos 43 of each user, a partner is selected with a mouse or the like, and a hop-up display is performed thereon (step 235 in FIG. 11).
[Attendance status update function 470]
On the other hand, when the user referred to, in this example, the user of the client terminal B30 (Mr. Suzuki) changes the presence state, the own state setting unit 31 updates the present state to the presence state information management unit 12 of the server machine 10. Notification 471 is sent out (step 108 in FIG. 6 and step 111 in FIG. 7). The presence status information management unit 12 of the server machine 10 receives the notification, updates the presence status information 40 of the user (Mr. Suzuki) of the client terminal B30 (steps 311-312 in FIG. 12), and uses the client terminal B30. Request data 50 managed in association with the user (Mr. Suzuki) is sent to the client terminal 30 (step 313 in FIG. 12).
[Attendance status change notification 480]
When the own state setting unit 31 of the client terminal B30 receives the request data 50 of the user (Mr. Suzuki) of the client terminal B30 sent from the presence state information management unit 12 of the server machine 10 (step 112 in FIG. 7). First, it is confirmed whether the network address 52 is registered (step 115 in FIG. 7). If it is not registered, the update contents are not sent, and if it is registered, the contents of the status notification flag 53 are further confirmed (FIG. 7). 7 Step 116-117). If only the seventh bit of the status notification flag 53 is specified, that is, only the presence status is automatically changed, only the presence status information 40 is sent to the client terminal A20 (step 118-1 in FIG. 7). If the notification is made when the 0th to 4th bits are designated, that is, when the seating state is changed to a specific seating state, the seating state information 40 and a notification message are transmitted to the client terminal A20 (FIG. 7). Step 118). In the example of FIG. 2, Mr. Okuyama only updates the change of Mr. Suzuki's presence status, and Mr. Tanaka is notified of all changes in Mr. Suzuki's presence status with a message. Is set to be notified with a message only when Mr. Suzuki is present.

  Upon receiving the notification from the client terminal B30 (step 206 in FIG. 9), the partner status display unit 22 of the client terminal A20 updates the partner presence status display list 72 of the user (Mr. Suzuki) of the client terminal B30, and updates it. The contents are displayed again (steps 216 and 217 in FIG. 10). When the user of the client terminal A20 is Mr. Tanaka or Mr. Ota, a status update message is displayed in addition to the update (steps 218-219 in FIG. 10).

  As described above, the presence status of the reference partner can be updated automatically and in accordance with the status change of the partner, and can be realized with a minimum load.

In the screen 65 of FIG. 3, the user of the client terminals 20 and 30 can write a simple memo such as his simple schedule. When a schedule or the like is entered in this field and the memo registration button 68 on the screen is pressed, it is sent to the server machine 10 (step 108 in FIG. 6, step 111 in FIG. 7). The presence status information management unit 12 of the server machine 10 registers the contents of the sent memo in the memo 43 column of the presence status management table 11 (steps 311 and 312 in FIG. 12). The memo 43 is also displayed on the screen on the referrer side by the partner status display units 22 and 32. In the partner status display screen of the screen 63 in FIG. 3, the first line of the memo 43 is displayed below the reference partner user name. To display all the contents of the memo, the user wants to refer to the contents of the memo 43 by clicking on the user with a mouse or the like (step 235 in FIG. 11).
[Refer to latest status 430]
The latest status is displayed by pressing the NEW button 66 at the bottom center of the screen in FIG. 3 (step 227 in FIG. 11) and referring to the user's user name and presence status last together with the partner presence status reference list 72. Using the time (screen 67 in FIG. 3) as a parameter, the server machine 10 is requested for the latest state (step 228 in FIG. 11). The presence status information management unit 12 on the server machine 10 is registered in the partner presence status reference lists 24 and 34 in the client terminals 20 and 30 in the same steps as the acquisition of the partner presence status information 40. The presence status information 40 of all the reference partners who are present is transmitted (steps 315-321 in FIG. 13). At this time, the last referred time (screen 67 in FIG. 3) sent from the client terminals 20 and 30 is compared with the setting date 44 of each user's presence status (step 322 in FIG. 13). The presence status information 40 is sent only when the setting date 44 of the presence status of the person is larger (step 323 in FIG. 13), and the data transmission amount between the server machine 10 and the client terminals 20 and 30 is reduced. It is possible to do.

  For reference, the registration and deletion methods of users to be referenced by the partner status reference function 22 and 32 in this system are described.

  The reference partner is registered by selecting the menu [Awareness] on the screen 61 in FIG. When the menu [Awareness] is opened and [Register] is selected from the menu, a list of users registered in the server machine 10 is displayed. A user to be referred to is selected from there (steps 208 and 209 in FIG. 9). When the selection is completed, the selected partner list is sent to the server machine 10 (step 210 in FIG. 9). The presence status information management unit 12 of the server machine 10 adds the transmitted data as request data 50 to the presence status information 40 of the reference partner (steps 314-323 in FIG. 13). Further, the presence status information 40 of the reference partner is transmitted to the client terminals 20 and 30 (steps 314 to 323 in FIG. 13). The partner status display units 22 and 32 display the presence status of the reference partner on the screen 63 based on the presence status information 40 sent from the server machine 10 (step 210 in FIG. 9).

For deletion, select the reference partner displayed on the screen 63 in FIG. 3, open the menu [Awareness], and select the menu [Delete]. 10 (steps 208-210 in FIG. 9). The presence status information management unit 12 on the server machine 10 searches the request data 50 of the corresponding user using the user name to be deleted sent from the client terminals 20 and 30 as a key, and the network address of the own user name 52 is deleted (steps 324-328 in FIG. 13).
[Communication execution request function]
After confirming the presence status of the reference partner, the communication partner may be selected according to the status, and the reference partner may be accessed. In that case, select the picture of the person you want to access on screen 63 in FIG. 3 and select [Phone], [Mail], [FAX] from [Communication] on screen 61, or use the tool button on screen 62 to select [ Selecting [Telephone], [Mail], [FAX] obtains communication information 45 of the selected partner (phone number 46 for telephone, mail address 47 for mail, FAX number for FAX), and communication execution unit along with the communication type 23 and 33 are requested for processing (steps 211 and 212 in FIG. 9). The communication execution units 23 and 33 execute communication using the corresponding data.
[End presence reference]
When the presence status reference is ended, the server machine is notified of the reference end (step 207 in FIG. 9, step 213 in FIG. 10, step 329-333 in FIG. 14), and the current reference partner is displayed in the partner presence status reference list 72. Save and finish (steps 214 and 215 in FIG. 10). At the same time, the own state setting units 21 and 31 are also terminated. (Fig. 6, steps 109-110).
[Request data setting function 450]
You can set the notification level of the updated content when the status of the reference partner changes when the partner status is referenced or after reference registration.

  Select the person whose notification level is to be set on the screen 63 in FIG. 3, select [Option] in the screen 61, and select the menu [Set notification level] (step 223 in FIG. 11). The setting screen (FIG. 15) is displayed (step 224 in FIG. 11). An example of the notification level setting screen is shown in FIG. By selecting the state types 80 and 81 shown on the notification level setting screen in FIG. 15, it is set whether to notify any state change or only when it changes to a specific state. By sending the setting contents to the server machine 10 (steps 225 and 226 in FIG. 11), the presence status information management unit 12 on the server sets the status notification flag 53 of the presence status management table 11 (FIG. 14). Step 334,335). Based on this information, the self-status setting units 21 and 31 specify the user who should send the updated contents when a change occurs in the presence status of the referrer.

  Also, if you specify that you want to be notified when you change to a specific status, you will receive a notification message that the presence status has changed, so that you can see that the presence status has been updated as well as the presence status update (Step 220 in FIG. 10). An example of the notification message is shown in FIG.

  As described above, when the other party's state changes to the set condition, it can be surely recognized.

Further, when a notification message is displayed, a communication button can also be displayed as shown in FIG. 16 so that appropriate communication can be immediately made to the other party from the state change notification. The communication execution request function is activated by the communication button (steps 221, 222 in FIG. 10). The communication execution request function is the same as described above.
[Simple message function]
In this example, by providing the request data 50 with a simple message 54, a message notification condition 55, and a message confirmation flag 56, it is possible to send a simple message when the partner's presence state is changed.

  After selecting a partner on the screen 63 in FIG. 3, by selecting the menu [Option] on the screen 61 and further selecting the menu [Simple Message Function], the partner status display units 22 and 32 will respond to the selected user. The server 10 is inquired whether there is a simple message that has already been set (steps 230 and 231 in FIG. 11). The presence status information management unit 12 of the server machine 10 searches the request data 50 of the reference partner in the presence status management table 11 and confirms whether a message is set in the simple message 54 (step 336 in FIG. 14). If set, the simple message 54 is sent to the client terminals 20 and 30 (step 337 in FIG. 14). The partner status display units 22 and 32 of the client terminals 20 and 30 that have received the response from the server machine 10 display the message if there is a message, and display a simple message setting screen as shown in FIG. (Figure 11 Step 232). When the user inputs or changes a message, sets display conditions, and operates the send button 93, the message is sent to the presence status information management unit 12 of the server machine 10 (steps 233 and 234 in FIG. 11). The presence status information management unit 12 of the server machine 10 stores the simple message sent from the client terminals 20 and 30 in the request data 50 of the corresponding user in the presence status management table 11 (step 338, FIG. 14). 339). When the seating state is changed on the referenced side, the own state setting units 21 and 31 send a seating state update notification to the seating state information management unit 12 of the server machine 10, whereby the request data 50 is received from the server machine 10. It will be sent out. The self-status setting units 21 and 31 check whether the message notification condition 55 is met (step 119 in FIG. 8). If the message notification condition is met, the contents of the simple message 54 are displayed together with the reference user name 51 as shown in FIG. (Step 120 in FIG. 8).

  As a specific example, Mr. Tanaka will notify Mr. Suzuki on the simple message setting screen shown in FIG. 17 when Mr. Suzuki is in the “Attendance” state with the message “Please check the document today.” It is set. As a result, “1” is set to the 0th bit of the message content and message notification condition 55 in the simple message 54 in the request data 50 of Mr. Suzuki in the attendance state management table 11 of FIG. As a result, when Mr. Suzuki returns to the seat and changes the seating status to “attended”, the simple message 54 set in the request data 50 is displayed as shown in FIG.

  As described above, it is possible to display a message in accordance with the change of the partner's own state.

  Furthermore, a confirmation button 98 is prepared on the simple message display screen (FIG. 18), and when this button is pressed, the own state setting units 21 and 31 notify the server machine 10 that the message is already read, and a simple message display is displayed. The screen is erased (steps 121, 122, and 123 in FIG. 8). Upon receiving the notification, the presence status information management unit 12 of the server machine 10 turns on the message confirmation flag 56 of the request data 50 (sets “1” in the 0th bit) (steps 340 and 341 in FIG. 14). When the user tries to set a simple message for the same person again, the other party's status display units 22 and 32 check the contents of the message confirmation flag 56 together with the simple message contents set as described above. Whether or not is displayed (steps 231, 232 in FIG. 11). In the simple message setting screen of FIG. 17, when the white square on the left side of the read 92 is already read, it becomes a black square.

  When the message content is rewritten and sent 93 or re-notification 94 is selected without rewriting on the screen of FIG. 17, the message confirmation flag 56 is turned off (set to “0” in the 0th bit) (the read state is changed). The message is changed to the unread state) and sent to the server machine 10 together with the message content (steps 233 and 234 in FIG. 11). The presence status information management unit 10 of the server machine 10 updates the request data 50 based on the transmitted information (step 339 in FIG. 14).

  As described above, it is possible to determine whether the other party has seen the set simple message.

  Note that the three processes of the own state setting units 21 and 31 on the client terminals 20 and 30 side, the partner state display units 22 and 32, and the communication execution units 23 and 33 may be included in one program as the same application.

  The attendance status information management unit 12 on the server machine 10 also manages the attendance status management table 11, but the server machine 10 is a file sharing server, and the attendance management table 11 is treated as a file. The functions of the state information management unit 12 may be performed by the own state setting units 21 and 31 and the partner state display units 22 and 32 of the client terminals 20 and 30.

  The request data 50 of the presence status management table 11 is also stored in the same record as the presence status information of the user. However, an item of the user name 41 is added to the request data 50, and the user The presence status information 40 and the request data 50 may be managed as separate tables by enabling association by name.

  The users of the client terminals 20 and 30 may be used by not only one person but plural one, and one user is not only a specific client terminal but also other client terminals. Even if is used, implementation is possible.

  The application for request data 50 from the user is not limited to the application from the client terminals 20 and 30, but the application method is set on the client terminal, such as setting the application from the user at the time of system introduction. Not limited.

Configuration diagram of the present invention Record format example of a server attendance status management table Example screen of the self status setting section and partner status display section Diagram showing information transmission procedure of this system Example of the presence status display list of a client terminal The flowchart which shows the process of the self-state setting part of a client terminal (the 1) The flowchart which shows the process of the self-state setting part of a client terminal (the 2) The flowchart which shows the process of the self-state setting part of a client terminal (the 3) The flowchart which shows the process of the other party status display part of a client terminal (the 1) The flowchart which shows the process of the other party status display part of a client terminal (the 2) The flowchart which shows the process of the other party status display part of a client terminal (the 3) The flowchart which shows the process of the attendance state information management part of a server machine (the 1) The flowchart which shows the process of the attendance state information management part of a server machine (the 2) The flowchart which shows the process of the attendance state information management part of a server machine (the 3) Attendance status notification screen example Message screen example when updating partner presence status Simple message setting screen example Simple message display screen example

Claims (3)

A message notification method in a network system in which a server machine and a plurality of client terminal devices are connected to be able to communicate with each other,
The user status information notified from each client terminal is stored in association with each user, and to the client terminal of another user who wishes to refer to the status information of the user of the client terminal. And has a function to notify the status information change,
When changing the status information of the user of the client terminal, if a message from another user's client terminal is registered to the user of the client terminal, the registered message is notified to the client terminal A message notification method characterized by: A server machine used in a network system in which a server machine and a plurality of client terminal devices are connected to be able to communicate with each other,
Status information storage means for storing the status information of the user notified from the first client terminal in association with the user of the first client terminal;
A message at the end of the first client who wishes to be notified when the status information notified from the second client terminal is changed and a message content to the user of the first client terminal are displayed in the first client terminal. State information change notification setting means for storing in association with other users,
About the 1st client terminal where the change of the status information occurred in the status information storage means, the status information of the first client terminal is stored in the second client terminal stored in association with the status information change notification setting means. State information change notification means for notifying the change of,
A message from the second client terminal stored in association with the state information change notification setting means for the first client terminal in which the state information change has occurred in the state information storage means is sent to the first client terminal. A message notification means for transmitting to the server. A client terminal used in a network system in which a server machine and a plurality of client terminal devices are connected to be able to communicate with each other,
A self-status setting unit that receives input of status information of the user of the client terminal and notifies the server machine;
Status information change notification registration means for accepting input of another client terminal that wishes to receive status information change notification and a message to be notified to the other client terminal, and notifying the server machine;
A status information change notification registration information acquisition means for receiving a registered message from the other client terminal and the terminal referring to its own status from the server machine;
Status information change notification means for sending the status information of the user of the client terminal after the change to other client terminals acquired by the status information change notification registration information acquisition means;
A client terminal comprising message display means for displaying a message from another client terminal acquired by the status information change notification registration method acquisition means on a display unit of the client terminal.