JP2011165021A - Chat monitoring apparatus, chat monitoring method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To properly support identification of a possible person who fails to understand contents of a chat. <P>SOLUTION: An apparatus includes a speaker identification device which identifies, based on log information of a general chat including speaking time in the general chat and identification information of speakers, a speaker who is speaking in the general chat within a predetermined period; a terminal information receiver which receives, from a terminal of each participant to the general chat, identification information of the participant, information showing a utilization period of the general chat and information showing a utilization period of the private chat in the general chat; an extractor which extracts, with respect to non-speakers except the speaker of the participants, a non-speaker in which the ratio of the utilization period of the private chat to the utilization period of the general chat within the predetermined period exceeds a first predetermined value; and an output device which outputs identification information of the non-speaker extracted by the extractor. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a chat monitoring device, a chat monitoring method, and a program, and more particularly, to a chat monitoring device, a chat monitoring method, and a program for monitoring a participant's state in chat via a network.

  One of the means of communication via a network is chat with real-time characteristics. In the chat, communication is performed for each virtual room called a chat room where participants gather. In order to maintain and develop chat rooms, it is necessary to increase the willingness of existing participants and increase the number of new participants.

JP 2009-99088 A

  However, participants who cannot understand the content of the chat tend to lose their willingness to participate in the chat and leave the chat. As an example of not understanding the content of chat, because words that are common sense among older participants or words that only pass between specific participants are used in the chat, and the meaning of the word is not known, This is a case where the content of the entire chat cannot be grasped.

  The present invention has been made in view of the above points, and is a chat monitoring device, a chat monitoring method, and a program capable of appropriately supporting identification of a person who may not understand the content of chat. The purpose is to provide.

  Therefore, in order to solve the above-mentioned problem, the entire chat in which text information is communicated in real time among all the participants and the text information is communicated in real time between some of the participants in the entire chat. A chat monitoring device for monitoring a chat room that provides a private chat, the entire chat within a predetermined period based on log information of the entire chat including a comment time and a speaker identification information in the entire chat From the speaker identification means for identifying the speaker who is speaking in the chat, and the terminal of each participant of the overall chat, the identification information of the participant, the information indicating the usage period of the overall chat, and the overall chat Terminal information receiving means for receiving information indicating the period of use of the private chat in Extraction means for extracting the non-speaker for a non-speaker excluding the reporter, wherein the ratio of the private chat use period to the total chat use period within the predetermined period exceeds a first predetermined value; Output means for outputting identification information of the non-speaker extracted by the extraction means.

  According to the disclosed technique, it is possible to appropriately support identification of a person who may not understand the content of chat.

It is a figure which shows the structural example of the chat system in embodiment of this invention. It is a figure which shows the hardware structural example of the monitoring apparatus in embodiment of this invention. It is a flowchart for demonstrating the process sequence at the time of chat client starting. It is a figure which shows the structural example of a window management table. It is a figure which shows the structural example of a terminal active log | history table. It is a figure which shows the structural example of participation log | history DB. It is a flowchart for demonstrating the process sequence by the event monitoring part according to starting of a new window. It is a flowchart for demonstrating the process sequence by the event monitoring part according to switching of an active window. It is a flowchart for demonstrating the process sequence at the time of leaving a chat room. It is a flowchart for demonstrating the process sequence by the event monitoring part according to closing of a window. It is a flowchart for demonstrating the process outline by a monitoring apparatus. It is a flowchart for demonstrating the specific process of the recent speaker in a whole chat. It is a figure which shows the structural example of parameter DB. It is a figure for demonstrating the start time of the last unit time completed. It is a figure which shows the structural example of whole chat speaker DB. It is a figure for demonstrating the process sequence of a collection process of terminal information. It is a figure which shows the structural example of active log | history DB. It is a flowchart for demonstrating the determination process of a participant's state. It is a figure which shows the structural example of participant state management DB. It is a flowchart for demonstrating the notification process based on the determination result of a participant's state. It is a figure which shows the example of a display of a notification screen.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a chat system according to an embodiment of the present invention. The chat system 1 includes a chat server 10, a monitoring device 20, an administrator terminal 30, a user terminal 40, and the like. Each device is connected via a network such as the Internet or a LAN (Local Area Network).

  The chat server 10 is a computer that provides a chat service on the Internet, for example. In the present embodiment, “chat” refers to communication means for exchanging (communication) short sentences (text information) in real time via a computer network. The monitoring device 20 is a computer that monitors the status of chat participants. The administrator terminal 30 is a terminal such as a PC (Personal Computer) used by the administrator of the chat server 10 (the person in charge of operating the chat service). Chat server 10, monitoring device 20, and manager terminal 30 belong to the operator side of a chat service, for example. Note that the chat server 10 may also serve as the monitoring device 20. That is, the chat server 10 and the monitoring device 20 may be realized by a single computer. However, in the form in which the monitoring device 20 is independent as in the present embodiment, monitoring related to the chat service provided by the plurality of chat servers 10 can be performed centrally.

  The user terminal 40 is a user terminal (PC (Personal Computer), PDA (Personal Digital Assistance), mobile phone, or the like) that uses the chat service provided by the chat server 10. Therefore, the user terminal 40 exists for each user of the chat service.

  In the figure, a chat server 10 includes a chat server unit 11, a chat log storage unit 12, a participant management unit 13, and the like. Each of these units is realized by processing that a program installed in the chat server 10 causes the CPU of the chat server 10 to execute.

  The chat server unit 11 provides the original function of the chat service. For example, the chat server unit 11 provides a chat room, controls information exchange between the user terminals 40 via the chat room, and the like. A chat room is a virtual space (room) where participants gather. Participants in the chat room provided by the chat server unit 11 in the present embodiment can use the whole chat and the private chat. The whole chat is a chat performed between all participants in one chat room. A private chat is a chat performed between some participants in one chat room (for example, between two parties). In the following, when simply referred to as “chat”, there is no distinction between general chat and private chat.

  The chat log storage unit 12 stores a chat history (chat log) using a storage device. That is, when an utterance (writing) is performed in the chat room, the chat server unit 11 records the identification information of the utterer, the time of the utterance, the content of the utterance, etc. in the chat log storage unit 12. The chat log is recorded (accumulated) separately for each whole chat and each private chat.

  The participant management unit 13 manages information related to the chat participants using the storage device.

  The monitoring device 20 includes a server information collection unit 21, a terminal information collection unit 22, a monitoring unit 23, a status notification unit 24, a data management unit 25, and the like. Each of these units is realized by processing that a program installed in the monitoring device 20 causes the CPU of the monitoring device 20 to execute.

  The server information collection unit 21 collects (acquires) information managed in the chat server 10. For example, the server information collection unit 21 includes a participant information collection unit 211, a speaker information collection unit 212, and the like. The participant information collection unit 211 acquires chat participant list information from the participant management unit 13 of the chat server 10 and records it in the data management unit 25. Participants are not just registrants, but users who are actually in the chat room. It is not a requirement for participants to speak (speak). Therefore, users who are simply browsing the chat are also participants. Participants are also referred to as attendees, but in this embodiment, they are unified as “participants”.

  The speaker information collection unit 212 acquires the chat chat log of the entire chat from the chat log storage unit 12 of the chat server 10 and generates speaker list information. That is, a speaker is specified by the speaker information collection unit 212. The speaker information collection unit 212 records the generated speaker list information in the data management unit 25. A speaker is a person who has made a statement among participants. As described above, the identification information of the speaker is recorded in the chat log storage unit 12 for each statement. Therefore, it is possible to specify the speaker based on the chat log.

  The terminal information collection unit 22 collects (receives) information indicating the usage status of the chat service from each user terminal 40.

  The monitoring unit 23 monitors the state of the participant based on the information collected by the server information collection unit 21 and the information collected by the terminal information collection unit 22. As a result of monitoring, the monitoring unit 23 extracts participants who may not understand the content of the current entire chat. The status notification unit 24 performs an extraction result output process by the monitoring unit 23. For example, the status notification unit 24 notifies the administrator terminal 30 that there is a participant who may not understand the content of the entire chat.

  The user terminal 40 includes a chat client unit 41, an event monitoring unit 42, and the like. Each of these units is realized by processing that a program installed in the user terminal 40 causes the CPU of the user terminal 40 to execute.

  The chat client unit 41 displays various windows (screens) for using the chat service on the display device of the user terminal 40, and performs processing according to the input to the windows. For example, the chat client unit 41 displays an entire chat window, a private chat window, and the like. Based on communication with the chat server unit 11, the chat client unit 41 displays the contents of the general chat or the private chat in the general chat window or the private chat window. The chat client unit also sends a sentence (character string) input by the participant to the entire chat window or the private chat window to the chat server unit 11 together with the identification information of the participant as a comment in the entire chat or private chat. Send.

  The event monitoring unit 42 monitors various events in the window system and executes processing corresponding to the event. For example, events such as activation (display) of a new window, switching of an active window, and termination (non-display) of a window are monitored. An active window is a window that is an operation target. In a typical window system, no more than one window is active at any given moment. Note that what is to be monitored is not limited to a window (chat window) displayed by the chat client unit 41. Windows displayed by other applications may also be monitored.

  FIG. 2 is a diagram illustrating a hardware configuration example of the monitoring device according to the embodiment of the present invention. The monitoring device 20 in FIG. 2 includes a drive device 200, an auxiliary storage device 202, a memory device 203, a CPU 204, and an interface device 205 that are connected to each other via a bus B.

  A program that realizes processing in the monitoring device 20 is provided by a recording medium 201 such as a CD-ROM. When the recording medium 201 on which the program is recorded is set in the drive device 200, the program is installed from the recording medium 201 to the auxiliary storage device 202 via the drive device 200. However, it is not always necessary to install the program from the recording medium 201, and the program may be downloaded from another computer via a network. The auxiliary storage device 202 stores the installed program and stores necessary files and data.

  The memory device 203 reads the program from the auxiliary storage device 202 and stores it when there is an instruction to start the program. The CPU 204 executes a function related to the monitoring device 20 in accordance with a program stored in the memory device 203. The interface device 205 is used as an interface for connecting to a network.

  Hereinafter, a processing procedure in the chat system 1 will be described. First, a processing procedure executed in the user terminal 40 will be described.

  FIG. 3 is a flowchart for explaining a processing procedure when the chat client is activated.

  When the chat client unit 41 is activated, for example, it displays a login screen, and accepts input of a user and a room ID via the login screen (S301, S302). The room ID is a chat room identifier. In response to the input of the user ID or the like, the chat client unit 41 transmits a login request including the user ID, the room ID, the IP address of the user terminal 20, and the like to the chat server unit 11. The chat server unit 11 opens a chat session with the chat client unit 41 in response to the login request. The chat server unit 11 records the user ID, room ID, IP address, and the like of the logged-in user in the participant management unit 13.

  Subsequently, the chat client unit 41 displays a window for whole chat (whole chat window) on the display device of the user terminal 40 (S303).

  Subsequently, the chat client unit 41 acquires the handle (identifier) of the currently active window, and acquires the chat type of the window from the window management table 43 based on the handle (S304).

  FIG. 4 is a diagram illustrating a configuration example of the window management table. As shown in the figure, in the window management table 43, a handle and a chat type are registered for each chat window. The chat type is information indicating whether the corresponding window is an entire chat window or a private chat window. In the present embodiment, the chat type of the entire chat window is “M”. The chat type of the private chat window is “P”.

  As will be described later, the record of the window management table 43 is registered by the event monitoring unit 42. At the stage of step S304, at least in accordance with the display (activation) of the entire chat window in step S303, a record related to the entire chat window (record with the chat type “M”) is registered. Accordingly, in step S304, the chat type “M” is acquired.

  Subsequently, the chat client unit 41 records in the terminal active history table 44 that the activated state of the activated entire chat window has been started (S305).

  FIG. 5 is a diagram illustrating a configuration example of the terminal active history table. In the figure, a terminal active history table 44 is a table in which history information of windows that have become active in one user terminal 40 is recorded, and is generated in the storage device of each user terminal 40.

  The terminal active history table 44 includes items such as a room ID, a user ID, an active start time, an active end time, and a chat type. In step S305, one record (row) is generated, and the input room ID and user ID, the active start time, and the chat type acquired in step S304 are recorded in the record. The current time is recorded as the active start time.

  Subsequently, the chat client unit 41 notifies the monitoring device 20 that a new participant has entered (participated) in the chat room (S306). Specifically, the chat client unit 41 transmits a room entry notification including the input room ID and user ID to the terminal information collection unit 22 of the monitoring server 20. The terminal information collection unit 22 records information included in the received entry notification in the participation history DB 251 of the data management unit 25.

  FIG. 6 is a diagram illustrating a configuration example of the participation history DB. As shown in the figure, the participation history DB 251 has items such as room ID, user ID, entry time, and exit time.

  In the process by the terminal information collection unit 22 according to step S306, one record is generated, and the received room ID and user ID, and the room entry time are recorded in the record. The current time is recorded as the entry time.

  For example, when a private chat window is activated by an operation on the menu of the entire chat window, steps S303 to S305 are executed for the private chat window.

  Subsequently, a processing procedure executed by the event monitoring unit 42 in response to the activation of a new window in the user terminal 20 will be described. FIG. 7 is a flowchart for explaining a processing procedure by the event monitoring unit in response to activation of a new window.

  When the event monitoring unit 42 detects a start event of a new window, the event monitoring unit 42 determines whether the window is a chat window (S311). The determination may be performed based on the attribute of the window (for example, title, window name, etc.). For example, when making a determination based on a title, the event monitoring unit 42 knows the title of each chat window in advance, and determines whether the title of the activated window matches a known title. .

  When the activated window is a chat window (Yes in S311), the event monitoring unit 42 acquires a handle of the window (S312). Subsequently, the event monitoring unit 42 determines whether or not the window is a whole chat window (S313). The determination may be performed based on the determination result in step S311. That is, in step S311, when the title of the activated window matches the title of the entire chat window, it is determined that the window is the entire chat window.

  When the activated window is the entire chat window (Yes in S313), the event monitoring unit 42 registers the handle acquired in Step S312 and the chat type “M” in the window management table 43 (FIG. 4). (S314). On the other hand, when the activated window is not the entire chat window (No in S313), the event monitoring unit 42 registers the handle acquired in Step S312 and the chat type “P” in the window management table 43 (S315). . In the present embodiment, there are two types of chat windows: a general chat window and a private window. Accordingly, No in step S313 corresponds to a case where the activated window is a private chat window.

  Next, a processing procedure when an active window is switched on the user terminal 40 will be described. FIG. 8 is a flowchart for explaining a processing procedure by the event monitoring unit in response to switching of an active window.

  When the event monitoring unit 42 detects an active window switching event, the event monitoring unit 42 acquires a handle of the window that was active before switching (original active window), and determines whether or not the handle is registered in the window management table 43. (S321). If the handle is registered in the window management table 43 (Yes in S321), the event monitoring unit 42 records the current time at the active end time of the last record in the terminal active history table 44 (S322).

  Subsequently, the event monitoring unit 42 acquires the handle of the current active window, and determines whether or not the handle is registered in the window management table 43 (S323). When the handle is registered in the window management table 43 (Yes in S323), the start of the active state related to the active window is recorded in the terminal active history table 44 (S324). In addition, the processing content of the said step is the same as that of step S305 of FIG.

  Next, a processing procedure when leaving the chat room will be described. FIG. 9 is a flowchart for explaining a processing procedure when leaving a chat room.

  For example, when leaving the chat room is instructed by operating the menu of the entire chat window, the chat client unit 41 notifies the monitoring device 20 that the participant has left (S331). Specifically, the chat client unit 41 transmits a leaving notice including the room ID and user ID of the participant to the terminal information collecting unit 22 of the monitoring server 20. In the participation history DB 251 (FIG. 6) of the data management unit 25, the terminal information collection unit 22 records the current time as the exit time in a record corresponding to the room ID and user ID included in the received exit notification.

  Next, a processing procedure when the window is closed (closed) will be described. FIG. 10 is a flowchart for explaining the processing procedure by the event monitoring unit in response to the closing of the window.

  When the event monitoring unit 42 detects a window closing event, the event monitoring unit 42 acquires a handle of the closed window (closed window), and determines whether or not the handle is registered in the window management table 43 (S341). When the handle is registered in the window management table 43 (Yes in S341), the event monitoring unit 42 deletes the record including the handle from the window management table 43 (S342).

  Next, a processing procedure in the monitoring device 20 will be described. FIG. 11 is a flowchart for explaining an outline of processing by the monitoring apparatus. The process shown in the figure is started at a predetermined timing after the start of the whole chat. The start of the overall chat may be determined based on the notification from the chat server unit 11. Moreover, the process of the figure is performed per chat room. Therefore, the following process description relates to one chat room that is a process target.

  In step S <b> 11, the speaker information collection unit 212 identifies a participant (speaker) who has recently made a general chat statement (within a predetermined period from the present to the past). Subsequently, the terminal information collection unit 22 collects information indicating the usage status of the chat service from each user terminal 40 (S12). Subsequently, the monitoring unit 23 determines the state of each participant based on the processing results of steps S11 and S12 (S13). Subsequently, the state notification unit 24 notifies (transmits) information based on the determination result by the monitoring unit 23 to the user terminal 40 specified according to the determination result (S14).

  Steps S11 to S14 are repeated at a constant cycle until the entire chat is completed. When the entire chat is finished (Yes in S15), the monitoring unit 23 deletes the work information from each database used for the processing (S16, S17).

  Next, details of step S11 will be described. FIG. 12 is a flowchart for explaining recent speaker specifying processing in the overall chat.

  In step S <b> 101, the speaker information collection unit 212 acquires a unit time from the parameter DB 252 of the data management unit 25.

  FIG. 13 is a diagram illustrating a configuration example of the parameter DB. In the figure, a unit time and a monitoring interval are registered in the parameter DB 252. In step S101, a unit time (10 minutes) is acquired. Note that the monitoring interval indicates a cycle in which steps S11 to S14 in FIG. 11 are repeated. Specifically, after step S14 ends, the speaker information collection unit 212 starts the process of step S11 as the time registered as the monitoring interval elapses.

  Subsequent to step S101, the speaker information collection unit 212 obtains the start time of the last completed unit time when the chat start time to the current time are divided by the unit time based on the chat start time (S102). The last completed unit time means a unit time in which the unit time has completely elapsed.

  FIG. 14 is a diagram for explaining the start time of the last completed unit time. In the figure, an example in which the entire chat is started at 10:00 is shown. The unit time is set to 10 minutes based on FIG. The current time is 10:55. In this case, the last unit time completed is a unit time according to 10:40 to 10:50. This is because the unit time started at 10:50 is in progress. Therefore, in the example of FIG. 14, the start time of the last unit time that is completed is 10:40 indicated by the arrow a.

  As shown in FIG. 14, the period from the start time of the last completed unit time to the current time is hereinafter referred to as “monitoring target period”. Note that the monitoring target period may be a period from the current time to a time traced back by a unit time. In this case, the monitoring target period is from 10:45 to 10:55.

  Subsequently, the speaker information collection unit 212 acquires a chat log including the message time within the monitoring target period from the chat log storage unit 12, and generates speaker list information based on the acquired chat log ( S103). The list information is a list of speaker identification information (user ID) included in the chat log. Note that the overlap of speakers in the list is eliminated.

  Subsequently, the speaker information collection unit 212 registers speaker list information in the overall chat speaker DB 253 of the data management unit 25 (S104).

  FIG. 15 is a diagram illustrating a configuration example of the overall chat speaker DB. As shown in the figure, the entire chat speaker DB 253 registers a list of speaker user IDs for each room ID. The room ID is an identifier of the chat room. In step S104, the room ID of the chat room to be processed is registered. In the figure, an example is shown in which two people with user IDs H002 and H004 are speakers in the monitoring target period.

  Next, details of step S12 in FIG. 11 will be described. FIG. 16 is a diagram for explaining a processing procedure of terminal information collection processing.

  In step S111, the terminal information collection unit 22 acquires the contents of the terminal active history table 44 recorded in the user terminal 20 from the user terminals 20 of the current participants in the chat room. The current participant in the chat room is specified by the user ID of the record in which the room ID for the chat room to be processed is included and the leaving time is not recorded in the participation history DB 251 (FIG. 6). In addition, when the entry notification is received from the user terminal 20, the user terminal 20 of each participant is specified based on the IP address of the user terminal 20 included in the entry notification. Alternatively, the IP address of each participant may be acquired from the participant management unit 13 of the chat server 10 via the participant information collection unit 211.

  Subsequently, the terminal information collection unit 22 registers the acquired information in the active history DB 254 of the data management unit 25 (S112).

  FIG. 17 is a diagram illustrating a configuration example of the active history DB. As shown in the figure, the active history DB 254 has the same items as the terminal active history table 44. This is because the active history DB 254 is a database in which the contents of the terminal active history table 44 of each user terminal 20 are aggregated.

  Next, details of step S13 in FIG. 11 will be described. FIG. 18 is a flowchart for explaining the process of determining the state of the participant.

  In step S121, the monitoring unit 23 identifies a non-speaker who has not made a speech within the monitoring target period in the entire chat. The non-speaker is the user ID registered for the chat room to be processed in the overall chat speaker DB 253 (that is, the user ID of the speaker) based on the participant user ID specified in step S111 in FIG. It is specified by excluding.

  Subsequently, the monitoring unit 23 sets one non-speaker as a processing target (hereinafter referred to as “current non-speaker”) (S122). Subsequently, the monitoring unit 23 determines whether or not the active time of the chat window of the current non-speaker is longer than the non-active time in the monitoring target period (S123). This step is a process for determining whether the reason why the current non-speaker is not speaking is an interest in chat. That is, when the inactive time is longer, it is estimated that the non-speaker spends longer time on the user terminal 20 for work other than chat (work in other applications). Therefore, it is considered that there is a high possibility that interest in chat is lost or busy with other work.

  The active time is calculated based on the active history DB 254. That is, the time that overlaps between the monitoring target period and the period between the active start time and the active end time (active period) is the active time. The inactive time is a time obtained by removing the active time from the monitoring target period. Here, there is no distinction between general chat and private chat. Specifically, in the active history DB 254, it is not distinguished whether the chat type is “M” or “P”. Further, this step does not necessarily have to be executed. However, by executing this step, it is possible to make the identification result of the participant who is finally identified and who may not understand the contents of the entire chat more appropriate. That is, there is a possibility that a participant who hardly uses chat in the monitoring target period does not perform the act of confirming the chat content, which is a premise for understanding the chat content. Note that this step may not be a determination based on a simple comparison of the magnitudes of parameters to be compared. For example, the determination of the step may be performed according to whether the active period is over what percentage (for example, over 40%) of the monitoring target period. In the present embodiment, it is an example in which it is determined whether or not the active period exceeds 50% of the monitoring target period.

  When the active time is longer than the inactive time (that is, when there is a high possibility of being interested in chat) (Yes in S123), the monitoring unit 23 displays the private chat window of the current non-speaker in the monitoring target period. It is determined whether the active time is longer than the active time of the entire chat window (S124). This step is a process for determining whether or not the reason why the current non-speaker is not speaking is because the contents of the whole chat cannot be understood (the whole chat cannot be followed). That is, in general, in the private chat, participants who do not understand the contents of the whole chat ask questions to other participants, or participants who are no longer interested in the contents of the whole chat can chat about other topics. It tends to be used for discussions. In the present embodiment, paying attention to such a tendency, if the use time of the private chat is longer than the use time of the whole chat, it is determined that the contents of the whole chat may not be understood. The use time of the private chat is estimated by the active time of the private chat window, and the use time of the whole chat is estimated by the active time of the whole chat window. Note that this step may not be a determination based on a simple comparison of the magnitudes of parameters to be compared. For example, the determination of this step may be made based on whether or not the active time of the private chat window is more than 10% (for example, more than 40%) of the active time of the entire chat window. In the present embodiment, it can be said that it is determined whether or not the active time of the private chat window exceeds 50% of the active time of the entire chat window.

  When the active time of the private chat window is longer than the active time of the entire chat window (Yes in S124), the monitoring unit 23 records “−1” in the flag of the current non-speaker (S125). The flag is managed in the participant state management DB 255 of the data management unit 25, for example.

  FIG. 19 is a diagram illustrating a configuration example of the participant state management DB. As shown in the figure, the participant state management DB 255 is a database for recording a name, a flag, and a counter for each participant. The name is the name of the participant. The name may be registered in advance as user information, or may be input at the time of login. The name is generally a handle name (nickname). The flag is data for identifying a participant who may not understand the content of the entire chat. The flag of the corresponding participant is “−1”. The initial value of the flag is “0”. The counter will be described later.

  Subsequent to step S125, or in the case of No in step S123, the monitoring unit 23 increments a counter in the participant state management DB 255 for the entire chat speaker (adds 1 to the counter) (S126). That is, the counter indicates the presence of participants who are estimated to be uninterested in the entire chat in the monitoring target period, or participants who may be interested in the entire chat but may not understand the contents of the entire chat. This data shows the weight of responsibility for existence. The reason why the corresponding participant exists is that there is a possibility that there is a problem in the content of the speaker in the overall chat.

  When step S123 and the subsequent steps are completed for all non-speakers in the monitoring target period (“all ends” in S122), the processing in FIG. 18 ends. Through the process of FIG. 18, participants who may not understand the contents of the entire chat are identified. That is, it is a participant whose flag value is “−1” in the participant state management DB 255.

  Next, details of step S14 in FIG. 11 will be described. FIG. 20 is a flowchart for explaining the notification process based on the determination result of the state of the participant.

  In step S <b> 131, the state notification unit 24 acquires the name of the participant whose flag value is “−1” from the participant state management DB 255. Subsequently, the state notification unit 24 acquires one record (hereinafter referred to as “current record”) of the participant state management DB 255 (S132). Subsequently, the status notification unit 24 determines whether or not the participant related to the current record (hereinafter referred to as “current participant”) is a speaker of the entire chat in the monitoring target period (S133). Specifically, it is determined whether or not the user ID of the current record is registered as the user ID for the chat room to be processed in the overall chat speaker DB 253.

  When the current participant is a speaker of the entire chat (Yes in S133), the state notification unit 24 determines whether or not the counter value of the current record exceeds the threshold value (S134). The threshold value may be a fixed value (constant) or a value based on a comparison with other participants. As an example of the latter, an average value of all counter values registered in the participant state management DB 255 can be given. When the value of the current record counter exceeds the threshold (Yes in S134), the state notification unit 24 stores the user ID of the current participant as the user ID of the cause candidate using the memory device 203 (S135). . A causal candidate is a participant (speaker) who may be the cause of the existence of a participant who does not understand the contents of the whole chat or a participant who has lost interest in the whole chat. Say.

  When Steps S132 to S135 are completed for all the records in the participant status management DB 255 ("End of all records" in S132), the status notification unit 24 transmits status notification information to the administrator terminal 30 (S136). The status notification information includes, for example, a list of names acquired in step S131. In addition, a list of names of the participants who are the cause candidates may be included. Subsequently, the state notification unit 24 initializes the values of all the flags in the participant state management DB 255 to “0” (S137).

  The administrator terminal 30 that has received the status notification information transmitted in step S136 displays a notification screen on the display device of the administrator terminal 30.

  FIG. 21 is a diagram illustrating a display example of a notification screen. In the figure, the notification screen 310 displays that there is a user who may not be able to keep up with the content of the current chat (overall chat) and a list of names of the users. The list of names is a list of names acquired in step S131. In addition, the notification screen 310 displays who is unable to keep up with the topic when speaking or who is losing interest. A list of names of users corresponding to “who” is also displayed. The list of names is a list of names of participants who are candidates for causes in step S135. The administrator who has referred to the notification screen 310 may take appropriate measures such as encouraging the participant who is a candidate for cause to improve the content of the statement so that other participants can understand it. it can.

  The notification information may be transferred to the administrator terminal 30 by e-mail. In this case, the administrator terminal 30 does not need to install a dedicated program for receiving and displaying the notification information. The notification information may be transmitted to the cause candidate's user terminal 30. In this case, the cause candidate can recognize that his / her speech content should be improved by referring to the notification information.

  Next, steps S16 and S17 in FIG. 11 will be described. When the chat in the chat room to be processed ends (for example, when all participants leave the room) (Yes in S15), the monitoring unit 23 initializes the counter values of all records in the participant state management DB 255 to “0”. (S16). Subsequently, the monitoring unit 23 deletes the record corresponding to the ended chat room from the entire chat speaker DB 253 (S17).

  Next, a specific example is applied to the processing procedure described above. In the specific example, the room ID of the chat room to be processed is “K001”, the chat start time is 10:00, and the unit time is 10 minutes. The current time is 10:55. Therefore, the period from 10 o'clock to 10:55 is divided as shown in FIG. 14, and the monitoring target period is between 10:40 and 10:55. Assume that the speakers in the monitoring target period are participants related to H002 and H004 as recorded in the overall chat speaker DB 253 of FIG.

  Also, it is assumed that the registration result of the participation history DB 251 from each user terminal 20 is as shown in FIG. It is assumed that the registration result of the active history DB 254 based on the contents of the terminal active history table 44 acquired from each user terminal 20 is as shown in FIG.

  Based on the above, the processing procedure of FIG. 18 will be described. First, in step S121, the participation history DB 251 (FIG. 6) specifies that the current participants are H001, H002, H003, and H004. Further, from the entire chat speaker DB 253 (FIG. 15), it is specified that the speakers in the monitoring target period are H002 and H004. Therefore, it is specified that the non-speaker is a participant related to H001 and H003.

  Subsequently, for example, H001 is set as the current non-speaker (S122). Focusing on H001 in the active history DB 254, the active time in the monitoring target period is 15 minutes from 10:40 to 10:55. Thus, the inactivity time is 0 minutes. Therefore, the determination in step S123 is Yes. That is, H001 is determined to be interested in chat.

  The chat type of the active time is “P”. That is, the active time of the private chat window of H001 is 15 minutes, and the active time of the whole chat window is 0 minutes. Therefore, the determination in step S124 is Yes. That is, it is determined that H001 may not understand the content of the entire chat.

  Therefore, “−1” is recorded in the flag of the record related to H001 in the participant state management DB 255 (S125). Moreover, 1 is added to each counter of H002 and H004 who are the speakers of the entire chat.

  The above steps S123 to S125 are also executed for H003, which is another non-speaker. As a result, the contents of the participant state management DB 255 are as shown in FIG.

  Next, the processing procedure of FIG. 20 will be described for this specific example. In step S131, the name “Taro Yamada” of H001 and the name “Saburo Takenaka” of H003 are acquired. Then, step S134 is performed regarding the record which concerns on H002 among the records of participant state management DB255. Here, the threshold value is (0 + 2 + 0 + 2) / 4 = 1 when the average value of the counter is used. Therefore, the determination in step S134 regarding H002 is Yes based on 2> 1. As a result, H002 is stored as a cause candidate. H004 is also stored as a cause candidate as a result of the execution of step S134.

  From the above, the display content of the notification screen 310 is as shown in FIG. 21, for example.

  As described above, according to the present embodiment, participants (withdrawal candidates) who may not understand the contents of the overall chat are appropriately identified based on the usage status of the overall chat and the private chat. be able to.

  In addition, by removing participants who have less usage time for the entire chat within a predetermined period (monitored period) from the withdrawal candidates, participants who are simply not interested or busy with other work are excluded. It can be excluded from the dropout candidates.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

Regarding the above description, the following items are further disclosed.
(Appendix 1)
A chat room that provides a general chat that communicates text information in real time among all participants and a private chat that communicates text information in real time among some of the participants in the overall chat A chat monitoring device for monitoring
A speaker identification means for identifying a speaker who is speaking in the overall chat within a predetermined period based on log information of the overall chat, including the speech time and the identification information of the speaker in the overall chat;
Terminal information receiving means for receiving identification information of the participants, information indicating a period of use of the whole chat, and information indicating a period of use of the private chat in the whole chat from the terminals of the participants of the whole chat; ,
For the non-speaker excluding the speaker from the participants, the non-speaker whose ratio of the private chat use period to the total chat use period within the predetermined period exceeds a first predetermined value is extracted. Extraction means;
A chat monitoring apparatus comprising: output means for outputting identification information of the non-speaker extracted by the extraction means.
(Appendix 2)
The extraction means is configured such that a ratio of a total usage time of the overall chat and the private chat with respect to the predetermined period exceeds a second predetermined value, and the usage period of the private chat with respect to the usage period of the overall chat within the predetermined period The chat monitoring device according to supplementary note 1, wherein the non-speaker who exceeds the first predetermined value is extracted.
(Appendix 3)
The chat monitoring device according to appendix 1 or 2, wherein the output unit also outputs identification information of the speaker when the non-speaker is extracted by the extraction unit.
(Appendix 4)
The use period of the whole chat is a period in which the screen of the whole chat is an operation target in the terminal, and the use period of the private chat is a period in which the screen of the private chat is an operation target in the terminal. The chat monitoring device according to any one of supplementary notes 1 to 3, wherein:
(Appendix 5)
A chat room that provides a general chat that communicates text information in real time among all participants and a private chat that communicates text information in real time among some of the participants in the overall chat A chat monitoring method in which a computer monitors
A speaker identification procedure for identifying a speaker who is speaking in the overall chat within a predetermined period based on log information of the overall chat, including the speech time and the identification information of the speaker in the overall chat;
A terminal information receiving procedure for receiving identification information of the participant, information indicating a period of use of the whole chat, and information indicating a period of use of the private chat in the whole chat from a terminal of each participant of the whole chat; ,
For the non-speaker excluding the speaker from the participants, the non-speaker whose ratio of the private chat use period to the total chat use period within the predetermined period exceeds a first predetermined value is extracted. Extraction procedure;
A chat monitoring method in which the computer executes an output procedure for outputting the identification information of the non-speaker extracted in the extraction procedure.
(Appendix 6)
In the extraction procedure, a ratio of a total usage time of the whole chat and the private chat with respect to the predetermined period exceeds a second predetermined value, and the use period of the private chat with respect to the use period of the whole chat within the predetermined period 6. The chat monitoring method according to appendix 5, wherein the non-speaker who exceeds the first predetermined value is extracted.
(Appendix 7)
The chat monitoring method according to appendix 5 or 6, wherein when the non-speaker is extracted in the extraction procedure, the output procedure also outputs identification information of the speaker.
(Appendix 8)
The use period of the whole chat is a period in which the screen of the whole chat is an operation target in the terminal, and the use period of the private chat is a period in which the screen of the private chat is an operation target in the terminal. The chat monitoring method according to any one of appendices 5 to 7, which is:
(Appendix 9)
A chat room that provides a general chat that communicates text information in real time among all participants and a private chat that communicates text information in real time among some of the participants in the overall chat A program that causes a computer to monitor
A speaker identification procedure for identifying a speaker who is speaking in the overall chat within a predetermined period based on log information of the overall chat, including the speech time and the identification information of the speaker in the overall chat;
A terminal information receiving procedure for receiving identification information of the participant, information indicating a period of use of the whole chat, and information indicating a period of use of the private chat in the whole chat from a terminal of each participant of the whole chat; ,
For the non-speaker excluding the speaker from the participants, the non-speaker whose ratio of the private chat use period to the total chat use period within the predetermined period exceeds a first predetermined value is extracted. Extraction procedure;
The program for making the said computer perform the output procedure which outputs the identification information of the said non-speaker extracted in the said extraction procedure.
(Appendix 10)
In the extraction procedure, a ratio of a total usage time of the whole chat and the private chat with respect to the predetermined period exceeds a second predetermined value, and the use period of the private chat with respect to the use period of the whole chat within the predetermined period The program according to appendix 9, wherein the non-speaker whose ratio exceeds the first predetermined value is extracted.
(Appendix 11)
The program according to appendix 9 or 10, wherein the output procedure outputs the identification information of the speaker when the non-speaker is extracted in the extraction procedure.
(Appendix 12)
The use period of the whole chat is a period in which the screen of the whole chat is an operation target in the terminal, and the use period of the private chat is a period in which the screen of the private chat is an operation target in the terminal. The program according to any one of appendices 9 to 11, which is:

DESCRIPTION OF SYMBOLS 1 Chat system 10 Chat server 11 Chat server part 12 Chat log memory | storage part 13 Participant management part 20 Monitoring apparatus 21 Server information collection part 22 Terminal information collection part 23 Monitoring part 24 Status notification part 25 Data management part 30 Administrator terminal 40 User Terminal 41 Chat client unit 42 Event monitoring unit 200 Drive device 201 Recording medium 202 Auxiliary storage device 203 Memory device 204 CPU
205 Interface Device 211 Participant Information Collection Unit 212 Speaker Information Collection Unit B Bus

Claims (6)

A chat room that provides a general chat that communicates text information in real time among all participants and a private chat that communicates text information in real time among some of the participants in the overall chat A chat monitoring device for monitoring
A speaker identification means for identifying a speaker who is speaking in the overall chat within a predetermined period based on log information of the overall chat, including the speech time and the identification information of the speaker in the overall chat;
Terminal information receiving means for receiving identification information of the participants, information indicating a period of use of the whole chat, and information indicating a period of use of the private chat in the whole chat from the terminals of the participants of the whole chat; ,
For the non-speaker excluding the speaker from the participants, the non-speaker whose ratio of the private chat use period to the total chat use period within the predetermined period exceeds a first predetermined value is extracted. Extraction means;
A chat monitoring apparatus comprising: output means for outputting identification information of the non-speaker extracted by the extraction means.   The extraction means is configured such that a ratio of a total usage time of the overall chat and the private chat with respect to the predetermined period exceeds a second predetermined value, and the usage period of the private chat with respect to the usage period of the overall chat within the predetermined period The chat monitoring device according to claim 1, wherein the non-speaker whose ratio exceeds the first predetermined value is extracted.   The chat monitoring apparatus according to claim 1, wherein the output unit also outputs identification information of the speaker when the non-speaker is extracted by the extraction unit.   The use period of the whole chat is a period in which the screen of the whole chat is an operation target in the terminal, and the use period of the private chat is a period in which the screen of the private chat is an operation target in the terminal. The chat monitoring device according to any one of claims 1 to 3. A chat room that provides a general chat that communicates text information in real time among all participants and a private chat that communicates text information in real time among some of the participants in the overall chat A chat monitoring method in which a computer monitors
A speaker identification procedure for identifying a speaker who is speaking in the whole chat within a predetermined period based on the log information of the whole chat, including the comment time and the identification information of the speaker in the whole chat;
Terminal information reception procedure for receiving identification information of the participants, information indicating the usage period of the overall chat, and information indicating the usage period of the private chat in the overall chat, from the terminal of each participant of the overall chat;
For the non-speaker excluding the speaker from the participants, the non-speaker whose ratio of the private chat use period to the total chat use period within the predetermined period exceeds a first predetermined value is extracted. Extraction procedure;
A chat monitoring method in which the computer executes an output procedure for outputting the identification information of the non-speaker extracted in the extraction procedure. A chat room that provides a general chat that communicates text information in real time among all participants and a private chat that communicates text information in real time among some of the participants in the overall chat A program that causes a computer to monitor
A speaker identification procedure for identifying a speaker who is speaking in the overall chat within a predetermined period based on log information of the overall chat, including the speech time and the identification information of the speaker in the overall chat;
A terminal information receiving procedure for receiving identification information of the participant, information indicating a period of use of the whole chat, and information indicating a period of use of the private chat in the whole chat from a terminal of each participant of the whole chat; ,
For the non-speaker excluding the speaker from the participants, the non-speaker whose ratio of the private chat use period to the total chat use period within the predetermined period exceeds a first predetermined value is extracted. Extraction procedure;
The program for making the said computer perform the output procedure which outputs the identification information of the said non-speaker extracted in the said extraction procedure.

Images