JPH1040317A - Information sharing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent useless transmission of state information and to reduce the load on a server machine by sending request data related to updated state information to a client terminal and transmitting the state information directly from a client terminal to another client terminal. SOLUTION: A presence state information managing part 12 in the server machine 10 receives a request from a client terminal A20, extracts the presence state information of all registered reference parties including a user for a client terminal B30 from a presence state managing table 11 and sends the extracted information to an opposite party state displaying part 22 in the terminal A20. Own state setting part 31 in the terminal B30 selects a user to be informed of the updating of a presence state based on the request data sent from the machine 10 and the presence state information of a user for the terminal B30 is sent to the display part 22 in the terminal A20.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an improvement of a network system in which a plurality of client terminals share information by using a common server machine, and more particularly to a state such as a state of a user of each client terminal. The present invention relates to an information sharing system for sharing information and improving the efficiency of office activities.

[0002]

2. Description of the Related Art 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 types of information can be shared while staying at home has become widespread. Taking the presence status as an example of the status information, using the environment, the presence status of the user of each client terminal is centrally managed by the server machine, and the client terminal is provided with a function of referring to the information. As a result, there has been proposed a seating state management system capable of checking the seating state of another user while staying there.

[0003] An example of such a presence management system is disclosed in Japanese Patent Application Laid-Open No. Hei 8-87885. 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 the user of each client terminal. Then, when a change in the presence status occurs, the user of each client terminal updates the presence status information on the server machine through the own status setting unit. The server changes the presence status of the user and transmits the presence status of the user to all connected client terminals.

[0004]

In such a conventional technique, state information is transmitted to all client terminals unconditionally regardless of the necessity of the user, so that useless transmission processing occurs. . In addition, since the processing for transmitting the state information to each client terminal is entirely concentrated on the server, the load on the server increases. For this reason, if update processing occurs frequently or other processing overlaps, processing wait occurs, and it may not be possible to confirm the user's state information in real time even though the state information has changed. .

[0005]

The object of the present invention is to unconditionally transmit state information to all client terminals connected to a server at the time of updating state information, and
This is because the transmission processing is performed collectively by the server machine. According to the present invention, when the status information is updated, the associated request data is sent to the client terminal, so that the client terminal can directly transmit the status information to another client terminal.

[0006] This makes it possible to prevent unnecessary transmission of the status information and reduce the load on the server machine. That is, in a network system including a server and a plurality of specified client terminals, each client terminal is provided with a display unit for displaying status information of another user, and a self-state setting unit for inputting own status information is provided. And the self-state setting unit notifies the server machine of the inputted self-state information, and responds to the request data by referring to request data from another user registered in the server machine in advance. The state information of the own device is directly transmitted to another selected client terminal.

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described by taking a state management system as an example. FIG. 1 shows the configuration of an embodiment of the present invention. This configuration includes a plurality of client terminals 20, 30 and a server device 10 for connecting the client terminals 20, 30, and the client terminals 20, 30 and the server device 10 are connected by a LAN (L1).

The server machine 10 has a presence status management table 11 and a presence status information management unit 12. Presence state management table
As shown in FIG. 2, 11 stores the presence status information 40 of the user of each of the client terminals 20 and 30, and request data 50 managed in association with each user. Presence information
40 manages the following items.

1. User name 41: Client terminal 20, 30
1. Name of the user who uses Presence state 42: Not only presence / absence, but also a plurality of states such as return immediately / in a meeting / others are identified. In this example, the presence is symbolized as "1", the absence is represented as "2", the immediate return is represented as "3", the conference is represented as "4", and the others are represented as "5". FIG. 2 shows that Okuyama is present, Suzuki is absent, and Tanaka is in a meeting.

[0010] 3. Memo 43: Information entered by the user, such as a simple schedule 4. Set date and time 44: Date and time when the presence status information 40 was set / updated. Communication information 45: telephone number, e-mail address, FAX number required for executing communication The request data 50 is managed in association with the user, and is used as a notification condition of the presence status information when the presence status information is updated. .

1. 1. Reference user name 51: The name of the user who is referring to the presence status of the user. 2. Network address 52: Network address of client terminal 20, 30 used by reference user Status notification flag 53: Sets the notification condition to the reference user when the presence status is changed. The notification is made based on the request from the reference user, whether the notification is made when the presence state 42 of the reference partner changes to any state or when the state changes to a specific state. In this example, the 7th bit is set to "1" when the notification is made regardless of the change to any state, and the notification is made only when a specific state such as presence / absence / immediate return / meeting / other is established. In this case, the first to fourth 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 a notification of the update of the presence state information but also a notification that the change of the presence state has occurred is notified by a message (FIG. 16). In this example, in response to the change of Mr. Suzuki's presence status, only Mr. Okuyama's client terminal automatically updates the presence status information of Mr. Suzuki and the display of the screen 63. As shown in FIG. 16, a message indicating that a change has occurred is displayed on the screen along with the update of the presence status information of Mr. Ota (FIG. 16). A message indicating that a change has occurred is displayed on the screen along with the update (Fig. 1
6) I do so.

4. Simple message 54: Set the content of the message that the reference user wants to notify the user. 5. Message notification condition 55: 4. 2. When to display the simple message of the item Store with the same contents as the item.

6. Message confirmation flag 56: 4. Stores whether the simple message of the item was read by the other party. In this example, the 0th bit is set to “0” if unread, and 0 if read.
Set "1" to the bit. Attendance status information management unit 12
Performs management of the presence status management table 11 and transmission / reception of the presence status information 40 (including request data 50) of each user.

Each of the client terminals 20 and 30 has partner status display units 22 and 32, own status setting units 21 and 31, and communication execution units 23 and 33. Partner status display section 22, 32
Has a function of acquiring the presence state information 40 managed by the server machine 10 and displaying the presence state 42 of a desired partner and a function of setting request data 50, and executing communication after confirming the presence state. It has a function to request the communication execution units 23 and 33.

The own state setting sections 21 and 31 have a user interface for displaying and changing their own state and a function of notifying the server machine 10 of 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 shows examples of screens 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, respectively. The screen 61 displays a menu for various operations of the presence management system. By selecting a menu name with a mouse or the like, a lower-level 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 screen 62 is displayed.
The communication execution unit is activated through 2,32.
The same operation can be performed by selecting [Communication] in the menu on the screen 61. Screen 63 is the partner status display
This is a screen that displays the presence status of the reference partner according to 22, 32. For each user registered as a reference partner, a picture showing the user name 41 and the presence status 42 and the first line of the memo 43 are displayed. Have been. In addition, by selecting the reference partner with a mouse or the like, the contents set in the memo 43 can be referred to not only in the first line but also in all. NEW button at the bottom of the screen
Reference numeral 66 indicates that the displayed presence status is updated to the latest status. The screen 67 displays the time when the latest state was last referred.

The screen 64 is an interface screen when the own state is displayed / updated by the own state setting units 21 and 31. The screen 64 is on the right side of the word indicating the presence state, such as presence / absence.
By selecting the mark with a mouse or the like, the user's current presence status is set. According to the setting of the presence state, the registration / update of the presence state 42 is waited, and a picture representing the set state is displayed on the left side.

The screen 65 is a screen for the user to input a memo 43 such as his / her own schedule. The memo 43 is used to register / update the memo 43 set on the screen 65. FIG.
Is an example of the presence status display lists 24 and 34 on the client terminals 20 and 30. The presence status display list contains the own information 71
From the partner presence state 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) SERVERNANE =: The name of the server to which the client terminal is connected. wtop = and wleft =, wright =, wbottom =: The following information is managed in the display position of the self-state on the screen 60 and the partner presence state reference list 72.

1. awperson1-9: Name of the user who refers to the user The name set in [DIRNAME =] of the self-information 71 is stored.
It is created from the reference user name 51 of the request data 50. In this example, nine people are registered, and the integer at the end of awperson is incremented according to the number of registered persons.

2. [Reference User Name]: 1. 2. For each reference user name registered in section 3. From paragraph 6. Header for setting 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 reference partner.

5. args =: The display position on the screen 63 is stored. 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 for indicating the delimiter of reference partner information.

8. number =: Stores the number of reference users. In this example, nine users are referring to Mr. Okuyama. Before starting a 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. Partner status reference function 400 2. Own state update function 401 First, the partner state reference function 400 will be described. The partner state reference function 400 is roughly composed of three functions.

(1) Presence state reference function 410 (2) Request data setting function 450 (3) Communication execution request function 460 [Presence state reference function 410]
There is a pattern.

First time reference 420 Latest state reference 430 Automatic state notification 440 <First time reference 420> The user of the client terminal A20 on the referrer side displays the partner state by applying to refer to the user of the client terminal B30. The reference destination registration request 421 is transmitted from the unit 22 to the presence status information management unit 12 of the server machine 10. Upon receiving the 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, it sends the presence status information 40 and the request data 50 of the user of the client terminal B to the partner status display unit 22 of the client terminal A20. Client terminal A20 is a server machine
The client terminal B receives the presence status information 40 and the request data 50 sent from the presence status information management unit 12 of the client terminal B.
Display the presence status of 30 users (reference partner status display 42)
3).

The registered reference partner is displayed on the screen 63 of FIG. 3 at the time of reference. (However, if the status automatic notification function described in (2) above is used, the latest status is always displayed.) Displayed). <Latest state reference 430> When the user of the client terminal A20 on the reference side refers to the latest presence state of the user who has performed the reference partner registration 422 such as the user of the client terminal B30, the lower center of the screen in FIG. Is clicked with a mouse or the like, 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.
Sent to The presence status information management unit 12 of the server machine 10
In response to a request from the client terminal A20, based on the registered request data 50, the presence status information 40 of all registered reference partners including the user of the client terminal B30.
Is retrieved from the presence status management table 11 and sent to the partner status display unit 22 of the client terminal A20 (reference partner status transmission 432). Opponent status display section 22 of 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 the reference partners of the client terminal A20 (reference partner status display 43).
3). <Automatic status notification 440> By registering a reference partner, by specifying the notification level according to the subsequent change in the presence status of the reference partner (request data setting 450),
When the user of the client terminal B30 updates the presence status information 40, the updated content can be sent to the client terminal A20 based on the request data 50. This is because the user of the referred client terminal B30 changes his / her own state, the own state setting unit 31 issues an own state update notification 471 to the server machine 10, and receives the server apparatus
The ten state information management unit 12 updates the state information 40 of the user of the client terminal B30 (the state information update).
472), and the self-state setting unit 31 of the client terminal B30.
Request data 50 is sent to the user (request data send 473)
This is achieved by:

The self-state setting unit 31 of the client terminal B30 selects a user to be notified of the update of the seating state based on the request data 50 sent from the server machine 10 (request data confirmation 441). If so, client terminal A20
The status information 40 of the user of the client terminal B30 is sent to the other party's status display unit 22 (status update notification 442). The partner status display unit 22 of the client terminal A20 displays the presence status information 40 sent from the client terminal B30 based on the presence status information 40.
The presence status of the user of the client terminal B30 is displayed again (status update notification display 443). [Request data setting function 450] After registering the person who refers to the presence status, by automatically notifying when the presence status of the reference partner is updated, the status change of the setting partner can be changed in real time. It becomes possible to know. When the user of the client terminal A 20 sets the notification level when the user of the client terminal B 30 of the reference partner is updated, the partner status display unit 22 sets the request data setting 451 to the presence of the server 10. It is sent to the state information management unit 12. The presence status information management unit 12 of the server machine 10 receives the request and sets the requested 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 status automatic notification 440 of the item (1) is performed. [Communication execution request function 460] After confirming the presence status, call, e-mail, F
Communication such as AX. The user of the client terminal A20 checks the presence status of the user of the client terminal B30, and then selects a communication means by using [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 the communication number (communication execution request 461). As a result, the communication execution unit 23 is activated and 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) Status update function 470 (2) Status change notification function 480 [Status update function 470] The status update function will be described starting from the user of the referenced client terminal B30. .

The user of the client terminal B30 changes his / her status on the self-status update screen of the screen 64 in FIG. 3 when the presence status changes, and sends a self-status update notification 471 from the self-status setting unit 21. It is sent 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 the notification, updates the presence status information 40 of the user of the client terminal B30 (presence status information update 472), and also associates the request data 50 which is managed in association with it. To client terminal B30
(Request data transmission 473). [Presence state change notification function 480] The own state setting unit 31 of the client terminal B30 is the presence state information management unit 12 of the server machine 10.
Based on the request data 50 sent from the user, the user to be notified of the change of his / her status is selected (request data confirmation 481),
In this example, the presence status information is provided to the client terminal A20.
40 is sent directly (status update notification 482). In the partner status display section 22 of the client terminal A20, the client terminal B
The presence status information 40 sent from the self status setting unit 31 of 30
, The latest status of the reference partner is displayed again (status update notification display 483). This is a function linked to the automatic state notification 440 in the partner state reference function 410.

The above is the information transmission procedure of the present system. Next, each function will be described in detail using a flowchart. 6, 7, and 8 show the client terminals 20, 30.
9, 10, and 11 are flowcharts showing the processing of the own state setting units 21 and 31, and FIGS. 9, 10, and 11 are flowcharts showing the processing of the partner state display units 22 and 32 of the client terminals 20 and 30.
FIG. 13 and FIG. 14 are processing flowcharts showing the 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 FIG.
Basically, Mr. Suzuki in the attendance management table in the table is assumed. [Activation of the presence status information management unit 12] When the presence status information management unit 12 on the server machine 10 is activated, a backup file is created.
13 is read and the presence data 40 and the request data 50 are read and expanded in the presence management table 11 (FIG. 1).
2 Step 302). After that, the client terminals 20, 30
(Step 303 in FIG. 12). Conversely,
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 (FIG. 12).
Steps 304,305). [Activation of Own State Setting Units 21 and 31] The client terminal A20 will be described as an example. When the self-state setting unit 21 of the client terminal A20 is activated, first, in order to acquire the own user name,
[DIRNAME =] of own information 71 in the presence status display list 24 of FIG.
(In this example, "Satoshi Okuyama") is read.
If the user name is not set in the presence status display list 24, a screen prompting the user to input is displayed (FIG. 6).
Step 102). When the own user name is obtained, the latest user's own state information 40 of the own state is requested to the state information manager 12 on the server machine 10 using this as a parameter (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,
The presence status information 40 of the user (Mr. Okuyama) of the client terminal A20 is acquired from the presence status management table 11, and transmitted to the client terminal A20 (FIG. 12, steps 307 and 30).
8). The self status setting unit 21 of the client terminal 20 displays the presence status of the user (Mr. Okuyama) of the client terminal A20 based on the presence status information 40 sent from the server machine 10 (steps 104 and 105 in FIG. 6). . At this time, if the presence status information 40 of the user (Mr. Okuyama) of the client terminal A20 is not present in the presence status management table 11 of the server machine 10, the initial value (the presence status 42 is "present" and the other information is None)
The new registration of the own status is performed by the presence status information management unit on the server machine 10.
At the same time as requesting to the user 12 (steps 104 and 106 in FIG. 6), the self-state is displayed (step 107 in FIG. 6). 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 (FIG. 12, steps 309, 310). Thereafter, the self-state setting unit 21 of the client terminal 20 waits for an update of the self-state (step 1 in FIG. 6).
08).

A screen example of the above operation is a screen 64 in FIG.
This example is a screen of the client terminal A20, in which Mr. Okuyama is registered as his own user. On the screen 64, the name and the presence status of Mr. Okuyama who is a user of the client terminal A20 are displayed. The presence status is set by pointing the circle on the left 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, 32] Partner status display units 22, 32
Is activated, the presence status display lists 24 and 34 stored in the client terminals 20 and 30 are read (step 202 in FIG. 9). Using the other party's presence state reference list 72 (FIG. 5) in the presence state display lists 24 and 34, the own user name, and the network addresses of the own client terminals 20 and 30 as parameters, the other party state reference request is sent to the server machine 10. It is transmitted (step 203 in FIG. 9). Presence state information management unit 12 on server machine 10
Is the presence status management table with the passed reference user name
The request data 50 associated with the eleventh reference partner user is searched to confirm whether the own 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, 30 is updated (steps 318, 321 in FIG. 13). If not, the own user name, own client terminal The network addresses 52 of 20, 30 are added (steps 318-319 in FIG. 13). Further, the presence state information 40 of the reference partner is set in the temporary area (steps 320 and 323 in FIG. 13). It is confirmed that the processing of all the reference persons registered in the other party presence state reference list 72 has been completed (step 315 in FIG. 13), and the presence state information 40 of the reference person set in the temporary area is transmitted to the client terminal 20. , 30 (FIG. 13, step 316). The partner status display sections 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 in FIG. The state of each partner is shown by a picture (the position set by [args =] and the color set by [color =] in FIG. 5) together with the partner's name (the name set by [name =] in FIG. 5). Is displayed. The occupancy status can be displayed in characters. Below the name, the first line of the contents of the memo 43 entered by each user is displayed. When the user wants to refer to the entire memo 43 of the user, the other party is selected by a mouse or the like, and a hop-up is displayed thereon (step 235 in FIG. 11). [Presence state update function 470] On the other hand, when the referred user, in this example, the user of the client terminal B30 (Mr. Suzuki) changes the presence state, the self-state setting unit 31 sets the presence state of the server machine 10. The self status update notification 471 is sent to the information management unit 12 (step 108 in FIG. 6, 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. The request data 50 managed in association with the person (Mr. Suzuki) is transmitted to the client terminal 30 (step 313 in FIG. 12). [Presence state change notification 480] The own state setting unit 31 of the client terminal B30 transmits the request data 50 of the user (Mr. Suzuki) of the client terminal B30 transmitted from the presence state information management unit 12 of the server machine 10. Upon receipt (Fig. 7 Step 11
2) First, check whether the network address 52 is registered (step 115 in FIG. 7). If the network address 52 is not registered, the update content is not sent. If the network address 52 is registered, the status notification flag 53 is further checked. (Figure 7 Step 1
16-117). Only the 7th bit of the status notification flag 53 is specified,
In other words, if only the presence status is automatically changed, the presence status information
Only 40 is sent to the client terminal A20 (step 118-1 in FIG. 7), and a notification is made when the status notification flag 53 is designated from the 0th bit to the 4th bit, that is, when the status is changed to a specific presence status. If so, the presence status information 40 and the notification message are sent to the client terminal A20 (step 118 in FIG. 7). In the example shown in FIG. 2, Okuyama only updates Suzuki's presence status automatically, and Tanaka has Suzuki's presence status changed with a message. Is set to notify you with a message only when Mr. Suzuki is present.

The partner status display section 22 of the client terminal A 20
Receives the notification from the client terminal B30 (step 206 in FIG. 9), updates the partner presence status display list 72 of the user (Mr. Suzuki) of the client terminal B30, and redisplays the updated contents (step FIG. 10). 216,217). If the user of the client terminal A20 is Mr. Tanaka or Mr. Ota, a message of status update as well as update is displayed (steps 218-219 in FIG. 10).

As described above, the presence state of the reference partner can be updated automatically and the display can be performed in accordance with the change of the partner's state, and can be realized with a minimum load. The screen 65 in FIG. 3 allows the user of the client terminals 20 and 30 to write a simple memo such as his own simple schedule. When a schedule or the like is entered in this field and the memo registration button 68 on the screen is pressed, the memo 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 content of the sent memo in the memo 43 column of the presence status management table 11 (steps 311 and 312 in FIG. 12). This memo 43 is also displayed on the screen of the referrer by the partner state display units 22 and 32. The first line of the memo 43 is displayed below the reference partner user name on the partner state display screen of the screen 63 of FIG.
When displaying all the contents of the memo, the user who wants to see is clicked with a mouse or the like, and the contents of the memo 43 are hopped up (step 235 in FIG. 11). [Refer to latest state 430] The latest state is displayed by pressing the NEW button 66 at the lower center of the screen in FIG.
Step 227), along with the other party's presence reference list 72,
The last time the user's name and presence status were referenced (Fig. 3
The latest state is requested to the server machine 10 using the screen 67) of FIG. 11 as a parameter (step 228 in FIG. 11). The presence state information management unit 12 on the server machine 10 registers the other party's presence state reference lists 24 and 34 on the client terminals 20 and 30 in the same steps as the acquisition of the above-mentioned presence state information 40 of the other party. Send out the presence status information 40 of all the referees (step 3 in FIG. 13)
15-321). At this time, the last reference time (the screen 67 in FIG. 3) transmitted from the client terminals 20 and 30 is compared with the set date and time 44 of the presence status of each user (step in FIG. 13).
322), the presence status information 40 is transmitted only when the set date / time 44 of the presence status of each user is larger (FIG. 13).
Step 323), the server machine 10 and the client terminals 20, 3
It is possible to reduce the amount of data transmission between 0.

For reference, a method of registering and deleting a user referred to by the partner state reference function 22, 32 in the present system will be described. The registration of the reference partner can be performed by using the menu on the screen 61 in FIG.
This is done by selecting [Awareness]. Menu [Awa
Open [reness] and select [Registration] in the menu, a list of users registered in the server machine 10 is displayed. From there, the user who wants to refer is selected (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 to the presence status information 40 of the reference partner as request data 50 (FIG. 13, steps 314-323). Further, the presence state information 40 of the reference partner is transmitted to the client terminals 20 and 30 (steps 314-323 in FIG. 13). Partner status display section 2
2, 32 is the presence status information 4 sent from the server machine 10.
Based on 0, the presence status of the reference partner is displayed on the screen 63 (FIG. 9, step 210). To delete, select the reference partner displayed on the screen 63 of FIG. 3, open the menu [Awareness], and select the menu [Delete].
The name of the user to be deleted is sent to the server machine 10 together with the name of the user (steps 208 to 210 in FIG. 9). The presence state information management unit 12 on the server machine 10 searches the request data 50 of the corresponding user using the name of the user to be deleted sent from the client terminals 20 and 30 as a key, and searches for the network address of the own user name. 52 is deleted (FIG. 13, steps 324-328). [Communication execution request function] After confirming the presence state of the reference partner, there is a case where the communication means is selected and the reference partner is accessed according to the state. In that case, select the picture of the person you want to access on the screen 63 in FIG.
From [Communication] on screen 61, select [Phone], [Email],
Select [FAX], or select [Telephone], [Email], or [FAX] using the tool button on the screen 62, and the communication information 45 of the selected partner (phone number 46 for telephone, mail address 47 for mail, It acquires the FAX number (if FAX), and requests the communication execution units 23 and 33 to perform processing together with the communication type (steps 211 and 212 in FIG. 9). The communication execution units 23 and 33 execute communication using the corresponding data. [End of presence state reference] To end the presence state reference, the server machine is notified of the end of reference (step 207 in FIG. 9, FIG. 1).
0 Step 213, FIG. 14 Steps 329-333), saves the current reference partner in the partner presence state reference list 72, and ends (Steps 214, 215 in FIG. 10). At the same time, the self-state setting units 21 and 31 also end. (Fig. 6, steps 109-110). [Request Data Setting Function 450] When the presence status of the reference partner changes when the partner status is referenced or after reference registration, the notification level of the update content can be set.

When a partner whose notification level is to be set is selected on the screen 63 of FIG. 3, an [Option] on the screen 61 is selected, and a menu [Setting of notification level] is selected (step 223 in FIG. 11). Then, the notification level setting screen (FIG. 15) is displayed (FIG. 11, step 224). FIG. 15 shows an example of the notification level setting screen. By selecting the status types 80 and 81 shown in the notification level setting screen of FIG. 15, it is set whether to notify all the status changes or only when a specific status is changed. By transmitting 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 sends the presence status management table.
11. Set the status notification flag 53 of FIG.
34,335). Based on this information, the own state setting units 21 and 31 specify the user to whom the updated content should be sent when the presence state of the referrer changes.

When a notification is given when the state is changed to a specific state, not only the presence state is updated, but also a notice indicating that the state is changed so that the user can know that the state has been updated. Display the message (Figure 10 Step 2
20). FIG. 16 shows an example of the notification message. As described above, when the state of the partner changes to the set condition, it can be reliably recognized.

Further, when displaying the notification message,
As shown in FIG. 16, a communication button may also be displayed so that appropriate communication can be immediately made to the other party from the status change notification. The communication button 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, the request data 50 is provided with a simple message 54, a message notification condition 55, and a message confirmation flag 56, so that a simple message can be transmitted when the presence status of the partner is changed. I have.

After selecting the other party on the screen 63 of FIG. 3, by selecting the menu [Option] on the screen 61 and further selecting the menu [simple message function], the other party status display sections 22 and 3 are selected.
2 inquires the selected user of the server machine 10 whether there is a simple message already set (FIG. 11).
Steps 230,231). The presence status information management unit 12 of the server machine 10 stores the request data of the reference partner in the presence status management table 11.
50 is searched, and it is confirmed 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 terminal 2
It is sent to 0,30 (FIG. 14, step 337). Server machine 1
The partner status display sections 22 and 32 of the client terminals 20 and 30 receiving the answer from 0 display a simple message setting screen as shown in FIG. 17 with a message if there is a message, or an initial value if there is no message (FIG. 17). 11 Step 232). When the user inputs or changes a message, sets display conditions, and operates the transmission button 93, the message is transmitted to the presence status information management unit 12 of the server machine 10 (steps 233 and 23 in FIG. 11).
Four). The presence status information management unit 12 of the server machine 10 stores the simple message transmitted from the client terminals 20 and 30 in the request data 50 of the corresponding user in the presence status management table 11 (FIG. 14, step 338). , 339). When the presence state is changed on the referred side, the own state setting units 21 and 31 send the presence state update notification to the presence state information management unit 12 of the server machine 10, and the request data 50 is transmitted from the server machine 10. Will be sent out. The own state setting units 21 and 31 determine whether the message notification condition 55
(Step 119 in FIG. 8), and if the message notification condition is satisfied, the contents of the simple message 54 are displayed together with the reference user name 51 as shown in FIG. 18 (Step in FIG. 8).
120).

As a specific example, on the simple message setting screen shown in FIG. 17, Tanaka sends a message to Suzuki, "Material, please check it out today," when Suzuki enters the "Attendance" state. Set to notify. As a result, the contents of the message and “1” are set to the 0th bit of the message notification condition 55 in the simple message 54 in the request data 50 of Mr. Suzuki in the presence status management table 11 of FIG. As a result, when Mr. Suzuki returns to his / her seat and changes his / her status to "Available", a simple message 54 set in the request data 50 is displayed as shown in FIG.

As described above, a message can be displayed according to the change of the partner's own state. Further, when a confirmation button 98 is prepared on the simple message display screen (FIG. 18) and pressed, the self-state setting units 21 and 31 notify the server machine 10 that the message is in the read state and display the simple message display. The screen is erased (steps 121, 122, 123 in FIG. 8). Server machine
Upon receipt of the notification, the ten status information management units 12
Turn on message confirmation flag 56 of 50 ("
("1" is set) (steps 340 and 341 in FIG. 14). When the user tries to set a simple message to the same partner again, the partner status display sections 22 and 32 display the contents of the simple message set as described above. The message confirmation flag 56 is checked, and whether or not the message has been read is also displayed (steps 231 and 232 in FIG. 11) In the simple message setting screen of FIG. Become a square.

On the screen shown in FIG. 17, when message 93 is rewritten and transmission 93 or re-notification 94 is selected without rewriting, message confirmation flag 56 is turned off ("0"
0 ”(set the read state to the unread state) and send it to the server machine 10 together with the message content (FIG. 11).
Steps 233,234). The presence status information management unit 10 of the server machine 10 sends request data 50 based on the transmitted information.
Is updated (step 339 in FIG. 14).

As described above, it is possible to determine whether the other party has seen the set simple message. In addition, the self-state setting units 21 and 31 of the client terminals 20 and 30 and the partner state display units 22 and 3
2. The three processes of the communication execution units 23 and 33 are:
One program may be included as the same application. The presence status information management unit 12 on the server 10 also manages the presence status management table 11, but the server 10 is a file sharing server, and the presence management table 11 is treated as a file. State information management unit 12
Function of the self-state setting units 21 and 31 of the client terminals 20 and 30
Alternatively, the other party's state display units 22 and 32 may perform the processing.

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.
May be added to enable the association by the user name, so that the presence status information 40 and the request data 50 may be managed as separate tables. Client terminal 20,3
0 users may use one device instead of one, and one user may use not only a specific client terminal but also other client terminals. However, implementation is possible.

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

[0049]

As described above, according to the present invention, when sharing the status information of each user in a network system including a server machine and a plurality of specified client terminals, the status information of each user is added to the status information of each user in advance. By linking and managing the request data registered in the application from the user, when the status information of the user is updated, the request data is referred to and selected according to the request data. It is possible to directly transmit the user status information to another client terminal.

Thus, it is possible to appropriately grasp the status information of the other party while reducing the load on the server machine.

[Brief description of the drawings]

FIG. 1 is a block diagram of the present invention.

FIG. 2 shows an example of a record format of a presence status management table of a server machine.

FIG. 3 is a screen example of a self-state setting unit and a partner state display unit.

FIG. 4 is a diagram showing an information transmission procedure of the present system.

FIG. 5 shows an example of a presence display list of a client terminal.

FIG. 6 is a flowchart illustrating processing of a self-state setting unit of the client terminal (part 1);

FIG. 7 is a flowchart showing processing of a self-state setting unit of the client terminal (part 2);

FIG. 8 is a flowchart (part 3) showing processing of the self-state setting unit of the client terminal;

FIG. 9 is a flowchart (part 1) illustrating a process performed by a partner status display unit of the client terminal;

FIG. 10 is a flowchart (part 2) illustrating processing of a partner state display unit of the client terminal;

FIG. 11 is a flowchart (part 3) showing the processing of the partner status display unit of the client terminal;

FIG. 12 is a flowchart (part 1) showing the processing of the presence status information management unit of the server machine;

FIG. 13 is a flowchart (part 2) illustrating the processing of the presence status information management unit of the server machine;

FIG. 14 is a flowchart (part 3) illustrating the processing of the presence status information management unit of the server machine;

FIG. 15 is an example of a presence status notification setting screen

FIG. 16 shows an example of a message screen at the time of updating the presence status of the other party.

FIG. 17 is an example of a simple message setting screen

FIG. 18 is an example of a simple message display screen

Continued on the front page (72) Inventor Junyo Okada 4-1-1, Kamidadanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture Inside Fujitsu Limited (72) Ai Manabe 4-1-1, Kamikodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Fujitsu Limited

Claims (1)

[Claims] In a network system including a server and a plurality of specified client terminals, each client terminal is provided with a display unit for displaying status information of another user, and a self-state for inputting own status information. A setting unit, and the self-state setting unit notifies the server unit of the inputted self-state information, and refers to request data from another user registered in the server unit in advance to perform the request. An information sharing system, wherein said own status information is directly transmitted to another client terminal selected according to data.