JP2006155675A - Method and apparatus for notifying group state, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To notify a network state, the network being mutually shared by users for conducting conversations. <P>SOLUTION: A table showing a correlation between a predetermined network state and an icon indicating each network state is prepared in a storage section 51. A determination section 52 detects a predetermined event on the network, and determines a new network state every time an event occurs. When the network state changes, a display control section 53 displays an icon indicating a new network state. For example, an icon indicates utterance of a keyword designated by a user, and another indicates that a key person designated by the user participates in the network. A setting section 54 receives the designation of the keyword and the key person, and stores them in the storage section 51. When looking at the icon at a glance, the user can determine whether a conversation necessary for him or her is conducted, or whether a conversation should be checked. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

The present invention relates to a technique for improving user convenience in a conversation system in which users share a virtual space and have a text-based conversation.
In the present invention, the conversation system is a system in which a plurality of users can transmit and receive text messages (hereinafter simply referred to as messages) in real time by sharing a virtual space and display the transmitted and received messages. To tell.

  The chat system refers to a conversation system constructed in accordance with the IRC (Internet Relay Chat) protocol (RFC 1459) and configured by connecting a chat server and a chat client via the Internet. The chat server broadcasts messages from chat clients in the channel to other chat clients. The chat client sends and receives messages to and from other chat clients via the chat server.

  A channel refers to a virtual space shared by chat clients in a chat system. A nickname is an identifier for uniquely identifying a user in a chat system. A topic refers to the topic of conversation in each channel. Mode refers to the characteristics of the channel.

  In recent years, conversation systems that allow users on a computer network to communicate in real time on a text basis have become widespread. An example of such a conversation system is a chat system that includes a chat server and a chat client. Generally, a chat server manages multiple channels, and a chat client participates in several channels selected by the user. The user designates one of the participating channels as the channel that the user is paying attention to (hereinafter referred to as the current channel).

  FIG. 19 is an example of a screen displayed by the chat client. The screen mainly includes a conversation window 192, a speech window 193, a channel monitor window 194, a user list window 195, and a channel list window 196. In addition, a current channel field 191 is provided at the top of the screen, and the current channel name is displayed.

  The conversation window 192 displays a message on the current channel. The user inputs a message in the comment window 193 and speaks on the current channel. In the channel monitor window 194, messages in participating channels (hereinafter referred to as participating channels) are displayed together. Some chat systems do not have a channel monitor window 194. The participating channels are listed in the channel list window 196. In the channel list, predetermined information such as the number of participating users and topics may be displayed in addition to the channel name.

In the chat system, participating users, the purpose of the channel, and the like are different for each channel. Therefore, each channel is highly independent. A user who is participating in a plurality of channels at the same time can view a conversation on the current channel in the conversation window 192. However, it is difficult to understand what kind of conversation is being conducted in other participating channels and whether it is necessary to know the content of the conversation.

Specifically, when the channel monitor window 194 is displayed, the conversation on the participating channel may be grasped by looking at the channel monitor window 194. However, in the channel monitor window 194, messages in each participating channel are mixedly displayed. For this reason, if the speech becomes active simultaneously in a plurality of participating channels, the user cannot follow the conversation content of each channel, and it becomes difficult to grasp the conversation content for each channel.
If the channel monitor window is not displayed, the user cannot know the conversation in the participating channel unless the current channel is changed and the conversation in the channel is displayed in the conversation window 192.

In any case, however, the user must determine the necessity of the conversation after watching the conversation contents one by one. This makes it difficult for users participating in a plurality of channels to easily acquire information necessary for them. Similar problems arise with conversation systems other than chat systems.
An object of the present invention is to provide a technique for notifying a user of a network state such as a channel and allowing the user to easily select information. For example, an object is to provide information for facilitating determination as to whether or not it is better for the user to look at the content of the conversation, and to easily refer to the network.

In order to solve the above-described problems, the first invention of the present application provides a group status notification method executed by a computer terminal capable of conversation by sharing the same virtual space and transmitting and receiving text messages. The method includes the following steps.
A virtual space state assumed in advance and a representation representing the virtual space state are stored in association with each other,
-The determination condition for determining the virtual space state assumed in advance is stored in association with the event and the virtual space that generate the assumed virtual space state,
-It is detected that an event has occurred in the virtual space, and based on the detected event and the determination condition associated with the virtual space, the state of the virtual space in which the event has occurred is changed to the presumed virtual space state. Determine whether or not
When it is determined that the virtual space state has become a virtual space state assumed in advance, a representation corresponding to the virtual space state is acquired and displayed.

For example, the state of whether a topic that the user is interested in is spoken, the user is called, or an important person is participating in the virtual space is represented by a representation. The user can grasp the approximate virtual space state by observing whether or not the representation is displayed, a change in representation, and the like.
The second invention of the present application provides a group status notification device used together with a conversation device capable of conversation by sharing the same virtual space and transmitting and receiving text messages. This apparatus includes the following components.
A state table that stores a virtual space state assumed in advance and a representation representing the virtual space state in association with each other;
A condition storage means for storing a determination condition for determining the presumed virtual space state in association with an event that generates the assumed virtual space state and a virtual space;
-It is detected that an event has occurred in the virtual space, and based on the detected event and the determination condition associated with the virtual space, the state of the virtual space in which the event has occurred is changed to the presumed virtual space state. Determining means for determining whether or not
Notification means for acquiring and displaying a representation corresponding to the virtual space state when it is determined that the state of the virtual space has become a virtual space state assumed in advance.

  As a representation representing a virtual space state, for example, an icon corresponding to each state may be displayed, or a character message may be output on a display screen. Examples of the predetermined event include, without limitation, remarks of text messages, changes in users participating in the virtual space, changes in the virtual space that the user is paying attention to, and notifications of will from the users. it can.

  When the event occurs, the determination unit determines how the virtual space state after the event has changed. For example, when a statement occurs, the determination unit determines whether or not a keyword specified by the user is included. If it is included, it is determined that “the message including the keyword has been spoken”. The notifying unit displays a representation associated with the state determined by the determining unit, and notifies the user of the virtual space state. For example, the display of icons can be changed or a text message can be displayed.

  In the present invention, the conversation device can independently display a function-specific window and a call window that accepts a call to each window, and the notifying unit displays the representation in at least one of the function-specific window or the call window. And the virtual space may be displayed in association with each other. For example, the call window is provided with a button for receiving a call for each window. Examples of the window include the aforementioned conversation window, channel list window, user list window, and the like. In addition, a list of participating channel names and the like is displayed in the calling window and the channel list window. Each channel name is displayed with an icon and other symbols. Therefore, the user can grasp the approximate state of the channel only by displaying the calling window and the channel list window.

  In addition to the conversation device, the group state notification device of the present invention is used together with a state detection device capable of detecting a predetermined user state and transmitting / receiving each other's user state via the conversation device and displaying the user state. It may be. In this device, the state detection device can display the user state in at least one of the function-specific window or the calling window, and the notifying unit is configured to display the representation and the user according to the new virtual space state. It is preferable that the display of the state can be changed.

  The state detection device in the group state notification device displays, for example, the user state of conversation devices sharing a virtual space with each other in the call window. The state detection device can also display the state of a user who has not participated in the virtual space but has been registered in the user DB 22 in advance. Consider a case where user B calls user A in virtual space N1. In the status notification device that operates on the information terminal of user A, the notification means displays an icon indicating “called status” on the calling window for the virtual space N1. Furthermore, the notification means blinks the status display of the user B displayed on the calling window. User A can recognize at a glance who is calling. Therefore, it can be easily determined whether to immediately see the conversation in the virtual space N1 or to postpone it.

The third invention of the present application provides a computer-readable recording medium on which a group status notification program is recorded, which is used for a computer terminal capable of conversation by sharing the same virtual space and transmitting and receiving text messages. The program performs the following steps:
A step of storing a virtual space state assumed in advance and a representation representing the virtual space state in association with each other;
Storing the determination condition for determining the virtual space state assumed in advance in association with the event and the virtual space that generate the assumed virtual space state;
-It is detected that an event has occurred in the virtual space, and based on the detected event and the determination condition associated with the virtual space, the state of the virtual space in which the event has occurred is changed to the presumed virtual space state. The stage of determining whether or not
A step of acquiring and displaying a representation corresponding to the virtual space state when it is determined that the state of the virtual space has become a virtual space state assumed in advance;

  It has the same effect as the second invention.

  By using the present invention, it is possible to grasp the state of the network without referring to the conversation in the network shared by users. By visually displaying the network status, the user can easily determine whether or not it is necessary to refer to the conversation in the network.

Next, the group status notification device of the present invention will be specifically described with reference to the drawings.
<First embodiment>
[Constitution]
FIG. 1 is an overall configuration diagram of a chat system 1 including a group status notification device according to a first embodiment of the present invention. The chat system 1 includes a chat server 2 and a chat client 31 connected via the Internet 4. The group status notification device 5 according to the present embodiment is provided in the user terminal 3 in which the chat client 31 can operate. In the present embodiment, an example in which the chat client 31 constituting the chat system 1 is used as a conversation device is shown, but the present device can be applied to other conversation devices. Although only one user terminal 3 is shown, a plurality of user terminals 3 can be connected to the chat server 2.

[Chat system]
The chat system 1 has a user state detection system in addition to the chat server 2 and the chat client 31. Specifically, the user DB 22 and the state management unit 21 are provided in the chat server 2, and the state detection unit 32 is provided in the chat client 31, respectively. In the user DB 22, a predetermined user is registered in advance for each channel as a user configuring a channel (hereinafter referred to as a channel configuration user). The state management unit 21 manages the user DB 22. The state detection unit 32 monitors changes in the user state based on the state of the user terminal 3 and predetermined data. When the user state changes, the state detection unit 32 notifies the state management unit 21 of a new user state via the chat client 31. In response to this notification, the user status in the user DB 22 is changed. Furthermore, the new user status is notified to users in the same channel via the input / output unit 33 via the chat client 31. In this example, the user state detection system operates in conjunction with the chat system 1, but may be configured independently of the chat system 1.

  Further, the chat client 31 can independently output a function-specific window and a tool palette window (call window) for calling each window to the input / output unit 33. FIG. 2 is an explanatory diagram showing that the function-specific windows are displayed independently and called by the tool palette window. 2A shows a tool palette window, FIG. 2B shows a conversation window including a speech window and a user list window, FIG. 2C shows a channel monitor window, and FIG. 2D shows a channel list window, which are displayed independently. ing. A user list is displayed as an icon in the left part of the conversation window, and a speech window is displayed in the lower right part. The icon of the user list indicates the status of the constituent users of the current channel.

  The tool palette window is provided with a self-status setting button 201, a call button 202, a function button 203, and a status window 204. The own state setting button 201 receives the setting of the own state. The call button 202 receives a call for a conversation window, a channel monitor window, and a channel list window. The function button 203 is a button for receiving a message or file transmitted when the user is absent. The status window 204 is a window for displaying the user status and the participating channel status. The user state is displayed by the state detection unit 32. The participation channel state is displayed by the group state notification device 5 as described later.

[Group status notification device]
In the user terminal 3, the group status notification device 5 can operate in conjunction with the chat client 31. The group status notification device 5 includes a storage unit 51, a determination unit 52, a display control unit 53, and a setting unit 54.
The storage unit 51 holds data necessary for predetermined processing. Specifically, the storage unit 51 holds the tables shown in FIGS. FIG. 3 is an explanatory conceptual diagram of the channel state table. In the channel state table, predetermined channel states and icons are associated and registered. In this embodiment, the following 1) to 16) are prepared as predetermined channel states. However, the channel state is not limited to the following example, and can be set according to needs.

1) current channel, 2) participating channel,
3) many users connected, 4) recently said,
5) The user is called, 6) The keyword is spoken,
7) Documents were submitted, 8) Many users spoke,
9) Key persons are participating, 10) Atmosphere of approval,
11) Opposite atmosphere, 12) Other atmosphere,
13) Many users are present, 14) Many users are away,
15) Many busy users 16) Many users on a business trip Each channel status has an icon for each status. The channel state is indicated by displaying an icon along with the channel name on the screen. For example, in the tool palette window shown in FIG. 2A, an icon indicating the “current channel” state is displayed for the channel #chocolat. In the channel list window of FIG. 2D, icons indicating the “participating channel” state are displayed for the channels # ume3 and #icctest. For the channels #islab and #icc, an icon indicating the “keyword is spoken” state is displayed. Further, for the channel #chocolat, an icon indicating the “current channel” state is displayed as described above. In the present embodiment, an icon is used as a form indicating the channel state, but other display forms are possible. For example, a text message can be displayed. It is also possible to display a plurality of states for one channel.

  FIG. 4A is a conceptual explanatory diagram of a connected user table. In the connected user table, channel names, registered users, connected users, and connection ratios are stored in association with each other. In this embodiment, the channel name of the participating channel is registered in “Channel name”. The same applies to the following tables. In “Registered Users”, the number of users registered in advance in the user DB 22 as channel configuration users is registered. In “connected users”, the number of users connected to the chat server 2 is registered. As the connection ratio, the ratio of the number of connected users to the number of channel configuration users is registered. If the connection ratio is equal to or greater than a predetermined value, an icon indicating the “multiple users connected” state of the channel state is displayed.

  FIG. 4B is a conceptual explanatory diagram of the keyword table. In the keyword table, channel names, topic flags, and keywords are associated and registered. “Channel name” is the same as that in the connected user table. In the “topic flag”, a value of “1” or “0” is registered. If the topic flag is “1”, it indicates that the keyword specified by the user in advance is spoken in the channel, and the user has not yet referred to the channel. If the topic flag is “0”, it indicates that the keyword does not appear in the channel. In the “keyword”, a character string designated for each channel by the user is registered.

  FIG. 4C is a conceptual explanatory diagram of a name table. In the call name table, channel names, call flags, and call names are associated and registered. “Channel name” is the same as that in the connected user table. A value of “1” or “0” is registered in the “call flag”. If the call flag is “1”, it indicates that the call name designated by the user in the channel is being spoken. If the call flag is “0”, it indicates that the call name is not spoken. In the “call name”, a character string designated by the user is registered. This character string is usually the user's name, the user's nickname, “all” indicating a call to all users, and so on.

  FIG. 4D is a conceptual explanatory diagram of the material table. In the material table, channel names, material flags, and materials are registered in association with each other. “Channel name” is the same as that in the connected user table. In the “material flag”, “1” or “0” is registered. If the material flag is “1”, it indicates that the material is provided in the channel and the material is not viewed by the user. If the material flag is “0”, it indicates that there is no unviewed material in the channel. In the “material”, information for identifying a resource spoken in the channel is registered. For example, an address and file name of a document file, an address of a web page, and the like.

  FIG. 5 is a conceptual explanatory diagram of the statement management table. In the message management table, a message flag, an active flag, a central user, a user name, a last message time, and the number of messages are registered in association with each channel. “Channel name” is the same as that in the connected user table. In the “speak flag”, a value of “1” or “0” is registered. If the speech flag is “1”, it indicates that a predetermined time has not yet elapsed from the last speech time in the channel. If the speech flag is “0”, it indicates that there is no speech even if a predetermined time elapses from the last speech time in the channel.

  In the “active flag”, a value of “1” or “0” is registered. If the active flag is “1”, it indicates that the number of users who have spoken in the past predetermined time is greater than or equal to the predetermined ratio. Further, if the active flag is “0”, it indicates that the number of users who have spoken in the past predetermined time is less than the predetermined ratio. “Central user” describes an identifier that identifies a user who has the largest number of utterances among the users registered in the utterance management table. In FIG. 5, the central user in channel #chocolat is USER-A. In addition, a user nomination, a nickname, etc. can be used as an identifier which identifies a user. In this embodiment, a nickname is used.

  In “user name”, a nickname of a user participating in the channel is described. When the number of users registered in the user name reaches a predetermined number, the “active flag” becomes “1”. The “last speech time” describes the last time when the user made a speech on the channel. “Number of utterances” indicates the number of times the user registered in this table has made a utterance in the channel. For example, in FIG. 5, the last speech time of USER-A is 11:14, and the speech count is 5 times. However, the user name, the last utterance time, and the number of utterances are registered when the user utters, and are deleted when no utterance occurs even after a predetermined time has elapsed. For example, in FIG. 5, when the predetermined time is 10 minutes, the entry of USER-B is deleted at 11:22.

  FIG. 6A is a conceptual explanatory diagram of a key person table. In the key person table, a channel name, a participation flag, and a key person are registered in association with each other. “Channel name” is the same as that in the connected user table. In the “participation flag”, a value of “1” or “0” is registered. If the participation flag is “1”, it indicates that a user who has been designated as a key person in advance is participating in the channel. The key person is designated by the user as an important person in the channel among the users registered in the user DB 22 as channel configuration users. Normally, a key person is designated for each channel because different users are considered to be different users if the channel is different. If the participation flag is “0”, it indicates that the key person is not participating in the channel. In the “key person”, the nickname of the designated user is registered.

  FIG. 6B is a conceptual explanatory diagram of the user status table. In the user status table, channel names, the number of seated users, the number of away users, the number of busy users, the number of business trip users, and the status are stored in association with each other. “Channel name” is the same as that in the connected user table. “Number of attended users” indicates the number of users who are present among channel configuration users. Similarly, “number of away users” indicates the number of users who are away from the seat, “number of busy users” indicates the number of busy users, and “number of users on a business trip” indicates the number of users on a business trip. . The user state can be acquired from the state detection unit 32. Further, the user state is not limited to the above-described example, and the user state that can be detected by the user state detection system can be targeted. The “state” is determined by the ratio of the number of users in each state to the number of channel configuration users in the channel. For example, if the number of attended users is 50% or more, a “presence” state is set, and a predetermined ratio is determined in advance. In FIG. 6, channel #icc and channel #chocolat are in the “attended” state, and channel #ume is in the “busy” state.

The determination unit 52 waits for the occurrence of a predetermined event, and determines the channel state after the event occurs. In the present embodiment, the case where the predetermined event is the following 1) to 8) will be described as an example. However, the event is not limited to the following example, and can be set according to needs.
1) Message remarks,
2) User participation and withdrawal from the channel,
3) User status change,
4) Application launch,
5) Current channel change,
6) Click on the icon indicating the channel,
7) Receiving the will notification described later
8) Timeout notification When the event occurs, the determination unit 52 determines whether or not the channel state has changed. If it is determined that the change has occurred, the determination unit 52 notifies the display control unit 53 of the channel and the channel state.

The display control unit 53 displays, changes, or deletes icons in the tool palette window of FIG. 2A and the channel list window of FIG. 2D in accordance with the notification from the determination unit 52.
The setting unit 54 displays a setting window and accepts registration in the keyword table, key person table, and name table. FIG. 7 is an explanatory diagram showing an example of a window for setting a call name. The user inputs his name in the keyword character string and presses the OK button. In the figure, USER-A sets four names. The set call name is registered as “call name” in the call name table of FIG. Keywords and key persons are also registered in the same way. In this example, the name is common to all channels, but can be set for each channel.

  In addition, the setting unit 54 displays a predetermined will setting window, receives the setting of the will, and sends a will notification through the chat system 1. The will notification is detected as an event by itself and other group status notification devices 5. FIG. 8 is an explanatory diagram illustrating an example of a will setting window displayed by the setting unit 54. For example, when a proposal in the channel is being discussed, each user opens his / her will setting window in FIG. 8 to notify his / her will. The determination of the user's will in the channel is performed by the determination unit 52. If there are many “agree” as a result of the aggregation, the channel status is displayed in “agree”. Thereby, the trend of channel configuration users can be grasped. It is preferable that a plurality of types of intention setting windows are prepared in advance, and those according to the topic of the channel can be used.

[Process flow]
(1) Main Routine Next, the flow of processing performed by the group status notification device 5 will be specifically described. FIG. 9 and FIG. 10 are flowcharts showing the flow of main routine processing performed by the group status notification device 5. When the chat client 31 is activated, the following processing is started.

First, in step S1, the determination unit 52 waits for the occurrence of a predetermined event. When an event occurs, the determination unit 52 proceeds to step S2.
In step S2, the determination unit 52 identifies the channel in which the event has occurred.
In step S <b> 3, the determination unit 52 determines whether or not the generated event is a connection or disconnection of the other chat client 31 to the chat server 2. If "Yes" is determined, the process proceeds to step S4, and if "No" is determined, the process proceeds to step S8 described later.

  In step S4, the determination unit 52 updates the connected user table of FIG. Specifically, when another chat client 31 connects to the chat server 2, the number of connected users of the channel in which the chat client 31 is a constituent user is increased. Conversely, if the connection with the chat server 2 is disconnected, the number of connected users is reduced. Further, as the number of connected users changes, the channel connection ratio is calculated and written to the connected user table.

In step S5, the determination unit 52 determines whether or not to change the channel connection state based on the new connection ratio. If "Yes" is determined, the process proceeds to step S6. If "No" is determined, the process proceeds to step S7 described later. That is, when the connection ratio is equal to or higher than the predetermined connection ratio, the process proceeds to step S6.
In step S6, the determination unit 52 notifies the display control unit 53 of the channel and the new state of the channel and instructs to change the display of the channel state. In accordance with this instruction, an icon indicating the channel connection state is displayed or deleted.

In step S7, the determination unit 52 determines whether or not the chat client 31 has ended. If the determination is "No", the determination unit 52 returns to step S1 and repeats the above processing. If “Yes” is determined, the process is terminated.
If "No" is determined in step S3, the process proceeds to step S8. In step S8, the determination unit 52 determines whether or not the event that has occurred is a message. If "Yes" is determined, the process proceeds to step S9. If "No" is determined, the process proceeds to step S14 described later.

In step S9, the determination unit 52 executes a keyword subroutine described later.
In step S10, the determination unit 52 executes a call subroutine described later.
In step S11, the determination unit 52 executes an unread subroutine to be described later.
In step S12, the determination unit 52 executes a speech management subroutine to be described later.
In step S13, the determination unit 52 executes an after-mentioned speech subroutine. Thereafter, the process returns to step S7 and the same processing as described above is repeated.

If “No” is determined in step S8, the process proceeds to step S14. In step S <b> 14, the determination unit 52 determines whether the generated event is participation or withdrawal of the chat client 31 from the channel. If "Yes" is determined, the process proceeds to step S15. If "No" is determined, the process proceeds to step S16 described later.
In step S15, the determination unit 52 executes a later-described key person subroutine. Thereafter, the process proceeds to step S7.

If “No” is determined in step S14, the process proceeds to step S16. In step S16, the determination unit 52 determines whether or not the generated event is a change in the user state. If "Yes" is determined, the process proceeds to step S17. If "No" is determined, the process proceeds to step S20 described later.
In step S17, the determination unit 52 updates the user status table (FIG. 6B). Further, the determination unit 52 aggregates the changed user state, that is, the new user state, and determines a new channel state. For example, when the user status “busy” becomes a predetermined ratio or more as a result of the aggregation, the new channel status is determined to be “busy”.

In step S18, the determination unit 52 determines whether or not the new channel state has changed from the previous channel state. If "Yes" is determined, the process proceeds to step S19. If "No" is determined, the process proceeds to step S7.
In step S19, the determination unit 52 notifies the new channel state and channel name, and instructs the display control unit 53 to change the display of the channel state. The display control unit 53 changes the display of the channel state in accordance with the instruction. For example, when the channel state changes from “at present” to “busy”, the display control unit 53 deletes the icon indicating the state of “there are many users at present”. Then, an icon indicating the “busy” state is displayed.

  If “No” is determined in step S16, the process proceeds to step S20. In step S20, the determination unit 52 determines whether or not the event that has occurred is the activation of an application. If "Yes" is determined, the process proceeds to step S21. If "No" is determined, the process proceeds to step S22 described later. The application activation includes, for example, a case where a document editing application is activated or a browser is activated in order to open a file presented in a statement.

In step S21, the determination unit 52 executes a read subroutine to be described later. Thereafter, the process returns to step S7.
If “No” is determined in step S20, the process proceeds to step S22 in FIG. In step S22, the determination unit 52 determines whether the generated event is a change in the current channel. If "Yes" is determined, the process proceeds to step S23, and if "No" is determined, the process proceeds to step S24 described later.

In step S23, the determination unit 52 executes a current channel subroutine to be described later, and proceeds to step S7.
If “No” is determined in step S22, the process proceeds to step S24. In step S24, the determination unit 52 determines whether or not an icon indicating a channel state is double-clicked in a predetermined window. If "Yes" is determined, the process proceeds to step S25. If "No" is determined, the process proceeds to step S26 described later. The predetermined window is, for example, a list window in the tool palette window shown in FIG.

  In step S25, the determination unit 52 instructs the chat client 31 to change the current channel. In addition, the determination unit 52 notifies the display control unit 53 of a new current channel, and instructs to change the display of the channel state. In response to this instruction, the display control unit 53 displays an icon indicating the “current channel” state on the double-clicked channel. In addition, an icon indicating the “participating channel” state is displayed on the previous current channel.

If "No" is determined in step S24, the process proceeds to step S26. In step S <b> 26, the determination unit 52 determines whether the generated event is the intention notification. If "Yes" is determined, the process proceeds to step S27. If "No" is determined, the process proceeds to step S30 described later.
In step S <b> 27, the determination unit 52 calculates the will using the received will notification and determines the atmosphere of the entire channel. For example, the determination unit 52 calculates the ratio to the channel configuration user for each of “Yes”, “No”, and “Other”. The determination unit 52 determines which channel state is based on the calculation result.

In step S28, the determination unit 52 determines whether or not the channel state has changed. If the determination is “Yes”, the process proceeds to step S29. If "No" is determined, the process proceeds to step S7.
In step S29, the determination unit 52 notifies the channel name and the new channel state, and instructs the display control unit 53 to change the display. Thereby, the display of the channel state is changed. For example, when the channel state changes from the “agree” state to the “reverse” state, an icon indicating the “opposite” state is displayed instead of the icon indicating the “agree” state. It should be noted that it is preferable to set a predetermined time limit for counting of will notifications.

If "No" is determined in step S26, the process proceeds to step S30. In step S30, the determination unit 52 determines whether or not the event that has occurred is the timeout notification. If “Yes”, the process proceeds to step S31. If “No”, the process proceeds to step S7.
In step S31, the determination unit 52 updates the message management table of FIG. Specifically, the determination unit 52 rewrites the message flag of the channel for which the timeout notification has been made from “1” to “0”.

In step S <b> 32, the determination unit 52 notifies the channel name and instructs the display control unit 53 to change the display of the channel state based on the change of the speech flag. As a result, the icon indicating the “recently spoken” state is deleted for the channel in which the event has occurred.
(2) Keyword Subroutine FIG. 11 is a flowchart showing the flow of processing of the keyword subroutine. When the process proceeds to step S9 in the main routine, the process described later is started. In step S91, the determination unit 52 determines whether or not a predetermined keyword is included in the received message. This determination is made by referring to the keyword table shown in FIG. If “Yes” is determined, the process proceeds to step S92. If “No” is determined, the process returns to the main routine.

In step S92, the determination unit 52 determines whether the topic flag of the channel is already “1”. If "No" is determined, the process proceeds to step S93, and if "Yes" is determined, the process returns to the main routine.
In step S93, the determination unit 52 updates the keyword table. Specifically, the topic flag of the channel in which the keyword is spoken is rewritten from “0” to “1”.

In step S94, the display control unit 53 displays an icon indicating the “keyword has been spoken” state on the corresponding channel based on an instruction from the determination unit 52. This icon is displayed until the corresponding channel becomes the current channel. Thereafter, the process returns to the main routine.
(3) Calling subroutine FIG. 12 is a flowchart showing the flow of processing of the calling subroutine. When the process proceeds to step S10 in the main routine, the following processing is executed.

First, in step S101, the determination unit 52 determines whether or not a call name designated by the user is included in the message that has been said. This determination is made based on the name table of FIG. If "Yes" is determined, the process proceeds to step S102. If "No" is determined, the process returns to the main routine.
In step S102, the determination unit 52 determines whether the call flag of the channel on which the call name is spoken is already “1”. If "Yes" is determined, the process returns to the main routine. If "No" is determined, the process proceeds to step S103.

In step S103, the determination unit 52 updates the call name table. Specifically, the determination unit 52 rewrites the call flag of the corresponding channel from “0” to “1”.
In step S104, the display control unit 53 displays an icon indicating the “user called” state on the corresponding channel. This icon is displayed until the corresponding channel becomes the current channel. Thereafter, the process returns to the main routine.

(4) Unread Subroutine FIG. 13 is a flowchart showing the flow of processing performed in the unread subroutine. When the process proceeds to step S11 in the main routine, the following processing is executed.
First, in step S111, the determination unit 52 determines whether or not material is provided in the remarked message. For example, it is determined whether the address of the web page, the file name, and the address are included in the speech. If "Yes" is determined, the process proceeds to step S112. If "No" is determined, the process returns to the main routine.

In step S112, the determination unit 52 updates the material table of FIG. Specifically, the address and material name of the material that has been spoken are registered as “material” of the corresponding channel in the material table. If there is material already written, add new material.
In step S113, the determination unit 52 determines whether the material flag of the channel for which the material is provided is already “1”. If “Yes” is determined, the process returns to the main routine. If "No" is determined, the process proceeds to step S114.

In step S114, the determination unit 52 rewrites the material flag of the corresponding channel from “0” to “1”.
In step S115, the display control unit 53 displays an icon indicating the “document has been submitted” state on the corresponding channel based on an instruction from the determination unit 52. This icon is displayed until all materials in the channel are browsed. Thereafter, the process returns to the main routine.

(5) Message Management Subroutine FIG. 14 is a flowchart showing the flow of processing performed in the message management subroutine. When proceeding to step S12 of the main routine, the following processing is executed.
In step S121, the determination unit 52 determines whether the user who has made a statement is already registered in the statement management table of FIG. If "Yes" is determined, the process proceeds to step S126 described later. If “No” is determined, the process proceeds to step S122.

In step S122, the determination unit 52 updates the statement management table. Specifically, the determination unit 52 writes the nickname, the utterance time, and the number of utterances of the user who uttered the message in the utterance management table. The number of utterances is “1”.
In step S123, the determination unit 52 calculates the ratio of the number of users registered in the speech management table with respect to the number of channel configuration users. That is, the ratio of users who have spoken continuously within a predetermined time interval is calculated. The determination unit 52 determines the value of the active flag based on the ratio of the speaking users.

In step S124, the determination unit 52 determines whether or not the active flag is changed. That is, if the active flag changes from “0” to “1” due to an increase in the number of speaking users, it is determined that the active flag is changed. If "Yes" is determined, the process proceeds to step S125. If "No" is determined, the process returns to the main routine.
In step S125, the display control unit 53 displays an icon indicating a “many users speak” state on the corresponding channel.

If “Yes” is determined in step S121, the process proceeds to step S126. In step S126, the determination unit 52 updates the speech time of the user who made the speech.
In step S127, the determination unit 52 increments the number of utterances of the uttered user.
In step S128, the determination unit 52 specifies the central user in the channel. That is, the determination unit 52 sets a user having the largest number of utterances in the utterance management table as a central user.

In step S129, the determination unit 52 determines whether or not the central user changes. If "Yes" is determined, the new central user is written in the message management table, and the process proceeds to step S130. If “No” is determined, the process returns to the main routine.
In step S130, the display control unit 53 displays a new central user. For example, when the user icon is displayed in the tool palette window, the user icon is blinked. It is also possible to provide a new field for displaying the central user in the channel list window and display the nickname of the central user in that field. Thereafter, the process returns to the main routine.

(6) Statement Subroutine FIG. 15 is a flowchart showing the flow of processing executed in the statement subroutine. When the process proceeds to step S13 in the main routine, the following processing is executed.
In step S131, the determination unit 52 resets the timer for the channel on which the speech has been made. The timer measures the elapsed time from the last speech time in each channel for each channel.

In step S132, the determination unit 52 refers to the message management table of FIG. 3 and determines whether or not the message flag of the channel that made the message is “1”. If "Yes" is determined, the process proceeds to step S135 described later. If "No" is determined, the process proceeds to step S133. If "Yes" is determined, the process proceeds to step S135 described later.
In step S133, the determination unit 52 rewrites the speech flag from “0” to “1” for the channel in which the speech has been made.

In step S134, the display control unit 53 displays an icon indicating the “recently uttered” state on the corresponding channel.
In step S135, the determination unit 52 starts a timer and starts measuring an elapsed time from a new speech time. Thereafter, the process returns to the main routine.
Note that the determination unit 52 sends a timeout notification when the timer exceeds a predetermined time. In other words, this is a case where the elapsed time from the last speech time in the channel exceeds a predetermined time. As described above, the message flag is changed from “1” to “0” by the time-out notification (step S31), and the icon display is changed (step S32).

Further, the determination unit 52 performs a process of deleting, from the speech management table, a user entry for which there is no next speech even after a predetermined time has elapsed since the last speech. Thereby, only the user who speaks continuously within the predetermined time interval is registered in the speech management table.
(7) Key Person Subroutine FIG. 16 is a flowchart showing the flow of processing performed in the key person subroutine. When the process proceeds to step S15 in the main routine, the following processing is executed.

In step S151, the determination unit 52 determines whether the user who has joined or left the channel is designated as a key person. This determination is made based on the key person table of FIG. If "Yes" is determined, the process proceeds to step S152. If “No” is determined, the process returns to the main routine.
In step S152, the determination unit 52 determines whether or not the event that has occurred is the participation of a key person. If “Yes”, that is, it is determined that the key person participates, the process proceeds to step S153. If “No”, that is, it is determined that the key person has left, the process proceeds to step S154.

In step S153, the determination unit 52 changes the participation flag in the key person table to “1”.
In step S154, the determination unit 52 changes the participation flag in the key person table to “0”.
In step S155, the display control unit 53 changes the display of the channel state based on an instruction from the determination unit 52. For example, when the participation flag changes from “0” to “1”, an icon indicating the “participating key person” state is displayed on the corresponding channel. Thereafter, the process returns to the main routine.

(8) Read Subroutine FIG. 17 is a flowchart showing the flow of processing of the read subroutine. When proceeding to step S21 of the main routine, the following processing is executed.
First, in step S <b> 211, the determination unit 52 determines whether a predetermined material has been acquired by the user terminal 3. That is, the determination unit 52 determines whether any material described in the “material” field of the material table in FIG. 4D has been acquired. If "Yes" is determined, the process proceeds to step S212. If "No" is determined, the process returns to the main routine.

In step S212, the determination unit 52 updates the material table. Specifically, the determination unit 52 deletes the material acquired by the application from the “material” field of the material table.
In step S213, the determination unit 52 determines whether there is any material that has not been opened among materials submitted to the same channel. This determination is made based on whether or not the “material” field from which the material acquired in step S212 is deleted is empty. If “No” is determined, the process proceeds to step S214, and if “Yes” is determined, the process returns to the main routine.

In step S214, the determination unit 52 updates the material table. Specifically, the determination unit 52 rewrites the material flag of the channel in which the “material” field is empty from “1” to “0”.
In step S 215, the display control unit 53 deletes the icon indicating the “material has been submitted” state for the corresponding channel based on the instruction from the determination unit 52. Thereafter, the process returns to the main routine.

(9) Current Channel Subroutine FIG. 18 is a flowchart showing the flow of processing of the current channel subroutine. When the process proceeds to step S23 in the main routine, the following processing is executed.
First, in step S231, the determination unit 52 determines whether or not the keyword flag of the channel that has newly become the current channel is “1”. This determination is made based on the keyword table shown in FIG. If "Yes" is determined, the process proceeds to step S232, and if "No" is determined, the process proceeds to step S234 described later.

In step S232, the determination unit 52 updates the keyword table. Specifically, the determination unit 52 rewrites the keyword flag of the new current channel from “1” to “0”.
In step S233, the display control unit 53 displays an icon indicating the “current channel” state for the new current channel. Further, an icon indicating the “participating channel” state is displayed for the previous current channel.

In step S234, the determination unit 52 determines whether or not the new current channel call flag is “1”. This determination is made based on the name table of FIG. If “Yes” is determined, the process proceeds to step S235, and if “No” is determined, the process returns to the main routine described above.
In step S235, the determination unit 52 updates the call name table. Specifically, the determination unit 52 rewrites the new current channel call flag from “1” to “0”.

In step S236, the display control unit 53 deletes the display of the icon indicating the “user called” state for the new current channel based on the instruction from the determination unit 52. Then return to the main routine.
<Another embodiment>
(A) In the first embodiment, the case where only participating channels are displayed in the tool palette window has been described as an example. However, it is also possible to accept registration of a channel that the user likes by the group status notification device 5 and display the favorite channel in the tool palette window. In that case, “favorite” is added to the channel state of the channel state table of FIG. 3 and the corresponding icon is registered. A new table for storing favorite channels is also provided. This table is not cleared even when the user terminal 3 ends. The setting unit 54 displays a screen for accepting registration of a favorite channel, and stores the input favorite channel in the storage unit 51.

  For example, when the chat client 31 is activated, the determination unit 52 acquires the status of the favorite channel via the chat client 31. The status of the favorite channel is displayed as an icon in the tool palette window. For example, when the chat client 31 participates in the favorite channel simultaneously with the activation, the group status notification device 5 can determine the status of the favorite channel. In this case, the favorite channel is not displayed in the channel list window. As a result, it is possible to display the user as if the channel status of the favorite channel not participating is notified. It is convenient for the user to enable participation in the favorite channel by double-clicking on the favorite channel in the tool palette window.

  (B) In the first embodiment, the case where the chat client 31 can display the function-specific windows independently has been described. However, the present invention can also be applied when the chat client 31 displays the fixed window shown in FIG. In this case, since the tool palette window is not displayed, the channel state may be displayed in the channel list window.

  (C) In the first embodiment, the case where the user state detection system is operable with the chat client 31 has been described. However, the present invention is applicable even when a user state detection system is not provided. In that case, an icon indicating the user state is not displayed in the tool palette window. Further, the channel state based on the user state is not displayed. Other channel states can be displayed in the same manner as in the first embodiment.

  The present invention can be applied to a conversation system in which users share a virtual space and have a conversation.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an overall configuration diagram of a group status notification device and device according to a first embodiment of the present invention. Explanatory drawing which shows that a function-specific window is displayed independently. FIG. 3 is an explanatory conceptual diagram of a channel state table. (A) Conceptual explanatory diagram of a connected user table. (B) Conceptual explanatory diagram of the keyword table (c) Conceptual explanatory diagram of the name table (d) Conceptual explanatory diagram of the material table. The conceptual explanatory view of a statement management table. (A) Conceptual explanatory diagram of a key person table. (B) A conceptual explanatory diagram of a user state table. Explanatory drawing which shows an example of a setting window. Explanatory drawing which shows an example of a will setting window. The flowchart (the 1) which shows the flow of a process of the main routine which a group status notification apparatus performs. The flowchart (the 2) which shows the flow of a process of the main routine which a group status notification apparatus performs. The flowchart which shows the flow of a process of a keyword subroutine. The flowchart which shows the flow of a process of a calling subroutine. The flowchart which shows the flow of the process performed in an unread subroutine. The flowchart which shows the flow of the process performed in a speech subroutine. The flowchart which shows the flow of the process performed in a speech management subroutine. The flowchart which shows the flow of the process performed in a key person subroutine. The flowchart which shows the flow of a process of a read subroutine. The flowchart which shows the flow of a process of a current channel subroutine. Explanatory drawing which shows an example of the screen displayed by a chat client.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1; Chat system including group status notification device 2; Chat server 3; User terminal 4; Internet 5; Group status notification device 31; Chat client 32;

Claims (3)

A group status notification method executed by a computer terminal capable of talking by transmitting and receiving text messages while sharing the same virtual space,
A virtual space state assumed in advance and a representation representing the virtual space state are stored in association with each other,
A determination condition for determining the virtual space state assumed in advance is stored in association with an event and a virtual space that generate the assumed virtual space state,
Based on the detected event and the determination condition associated with the detected virtual space, the state of the virtual space in which the event has occurred becomes the virtual space state assumed in advance. Whether or not
When it is determined that the state of the virtual space has become a virtual space state assumed in advance, a representation corresponding to the virtual space state is acquired and displayed.
Group status notification method. It is used with a conversation device that allows conversation by sharing the same virtual space and sending and receiving text messages,
A state table for storing a virtual space state assumed in advance and a representation representing the virtual space state in association with each other;
A condition storage means for storing a determination condition for determining the virtual space state assumed in advance in association with an event that generates the assumed virtual space state and a virtual space;
Based on the detected event and the determination condition associated with the detected virtual space, the state of the virtual space in which the event has occurred becomes the virtual space state assumed in advance. Determining means for determining whether or not
When it is determined that the state of the virtual space has become a virtual space state assumed in advance, a notification unit that acquires and displays a representation corresponding to the virtual space state;
A group status notification device. A computer-readable recording medium on which a group status notification program is recorded, which is used in a computer terminal capable of talking by transmitting and receiving character messages while sharing the same virtual space,
Storing a virtual space state assumed in advance and a representation representing the virtual space state in association with each other;
Storing the determination condition for determining the presumed virtual space state in association with the event and the virtual space for generating the assumed virtual space state;
Based on the detected event and the determination condition associated with the detected virtual space, the state of the virtual space in which the event has occurred becomes the virtual space state assumed in advance. Determining whether or not
When it is determined that the state of the virtual space has become a virtual space state assumed in advance, obtaining and displaying a representation corresponding to the virtual space state;
A recording medium on which a group status notification program for executing is recorded.

Images