JP7504439B2 - Online Dialogue System - Google Patents

Description

The present invention relates to an online dialogue system, and in particular to a technique for mutually presenting, exchanging and sharing information such as characters, voices and images (including still images, videos and other moving images; the same applies below) via information communication means.

Online dialogue systems (including systems known as television conferencing systems, video conferencing systems, web conferencing systems, etc.) are known that enable people to participate in conferences, meetings, lessons, etc. (hereinafter simply referred to as "meetings") from physically distant locations by mutually presenting, exchanging, and sharing perceptual information such as text, voice, and images (hereinafter such actions may be referred to as "dialogue") via information and communication means.

By using an online dialogue system, it is possible to hold and participate in meetings even from remote locations, which is expected to lead to more efficient meeting management in terms of reducing travel time and costs.

One such system is the videoconferencing system disclosed in Cited Document 1. This system is configured to identify the speaker based on voice data obtained from the terminals of the conference participants, and to visually distinguish between the speaker and non-speakers among the images of the conference participants displayed on each terminal. (See paragraphs [0037], [0045]-[0055], Figures 7, 9, 11, 12, 13, 15, 17, 19, and 21 of Patent Document 1.)

By configuring it in this way, the speaker can let the other participants know that they are the current speaker without even realizing it, and other participants can also know who the speaker is in real time, making it possible for all participants to concentrate on the meeting.

However, such systems place too much emphasis on keeping all participants focused on the meeting, and do not anticipate private conversations, which can make participants feel overly tense and restricted compared to a real meeting. As a result, participants may feel more tired and lose concentration, which could actually hinder the efficiency of the meeting.

Furthermore, in recent years, as long as one has access to an information and communications network such as the Internet, it is easy to participate in a video conference using a personal computer or smartphone. This means that it is possible that many people will participate in a single conference. As the number of participants in a conference increases, it is thought that the number of participants who are not very interested in what the speaker is saying will also increase proportionately, which is also an obstacle to efficient conference management.

In particular, when using such a system for purposes other than meetings (such as online drinking parties or other gatherings aimed at encouraging participants to socialize), conventional videoconferencing systems make participants feel excessively tense and restricted, making it difficult to hold a meeting smoothly.

JP 2003-299051 A

An object of the present invention is to provide an online dialogue system that can solve such conventional problems and realize efficient and smooth meeting operation regardless of the number of participants in the meeting.

The online dialogue system according to the present invention is an online dialogue system having a group of information processing devices including a plurality of client devices capable of communicating information via an information communication means, each client device being configured to belong to a virtual group configured to be in a state in which it can communicate with other client devices belonging to the same group, and all groups being configured to belong to one virtual dialogue room, and the information processing device being characterized in that it has a dialogue control unit including an inter-group movement control unit configured to, when it detects a signal generated in the client device, a request for movement to another group that belongs to the dialogue room and includes a designation of a group other than the group to which the client device belongs, add the client device as a component of the other group and control the client device to leave the group to which it previously belonged.

The features of the present invention can be broadly described as above, but the configuration and contents, as well as the purpose and features, will become more clear from the following disclosure in consideration of the drawings.

In each invention related to this application, "a client device becomes capable of interacting with other client devices" means "a user currently using a client device becomes capable of interacting with a user currently using another client device via each client device." Therefore, in order to avoid complicating the explanation, "a client device becomes capable of interacting with other client devices" will be expressed as "a user of a client device (sometimes simply referred to as "user"; the same applies below) becomes capable of interacting with other users" as appropriate.

In addition, in each invention related to this application, "each client device belongs to one of the virtual groups" means "a user currently using each client device belongs to one of the groups." Therefore, to avoid complicating the explanation, "each client device belongs to one of the virtual groups" will be expressed as "a user of each client device (sometimes simply referred to as a "user"; the same applies below) belongs to one of the groups" as appropriate.

The online dialogue system according to the first invention of the present application is an online dialogue system having a group of information processing devices including a plurality of client devices capable of communicating information via an information communication means, each client device being configured to belong to one of the virtual groups configured to be in a state in which it can communicate with other client devices belonging to the same group, and all groups being configured to belong to one virtual dialogue room, and the information processing device being characterized in that it has a dialogue control unit including an inter-group movement control unit configured to, when it detects a signal generated in the client device, a request for movement to another group that belongs to the dialogue room and includes a designation of a group other than the group to which the client device belongs, add the client device as a component of the other group and control the client device to leave the group to which it previously belonged.

In this way, by dividing one virtual conversation room into multiple virtual groups and configuring the configuration so that users of client devices can only converse within the same group, each user can concentrate on the conversation within their own group without worrying about the conversations of other groups.

By configuring the system so that users can freely move to other groups, each user can freely join a group that is discussing a topic that interests them, even if they are in the middle of a meeting.

Therefore, if this system is applied to meetings such as subcommittee-style meetings or so-called online drinking parties, it will be possible to ensure that the meeting is run efficiently and smoothly overall, regardless of the number of participants.

The online dialogue system according to the second invention of the present application is characterized in that, in the online dialogue system according to the first invention of the present application, the dialogue control unit includes an other group dialogue content display control unit that, when it detects an other group dialogue content display request signal, which is a signal generated in a client device and which requests the display of dialogue content in another group that belongs to the dialogue room and includes a designation of a group other than the group to which the user belongs, controls the client device to display the dialogue content of the other group on the client device without causing the client device to leave the group to which the client device currently belongs.

By configuring it in this way, a user can learn the content of the conversation in another group, for example, perceptual information such as images, audio, text, etc., showing the state of the conversation in the other group, without moving to the other group.

Therefore, if a user is most interested in the content of the conversations in their own group, but also has some interest in the content of the conversations in other groups, they can remain in their own group and participate in the conversations in other groups, for example as an observer with no right to speak in the other groups.

In addition, by configuring it in this way, the user can know the content of conversations in other groups that interest him or her before moving to that other group. As a result, it is possible for the user to move between groups accurately, and unnecessary movement between groups can be reduced.

The online dialogue system according to the third invention of the present application is characterized in that, in the online dialogue system according to any one of the first and second inventions of the present application, the dialogue control unit is provided with a new group generation control unit configured to generate a new group including the client device as a component when the dialogue control unit detects a group generation request signal, which is generated in a client device and requests the generation of a new group belonging to the dialogue room, and to control the client devices constituting the new group to leave the group to which they previously belonged.

By configuring it in this way, if a user, for example, is not particularly interested in the content of conversations in any of the groups, including the group to which the user belongs, but does not want to or is unable to leave the conversation room, the user can create a new group within the conversation room and join that group, thereby making effective use of meetings (especially making effective use of the time spent in meetings; same below).

The online dialogue system according to the fourth invention of the present application is characterized in that, in the online dialogue system according to the third invention of the present application, the group generation request signal is configured to include a group generation proposal signal that proposes the generation of a new group that includes the designation of another client device generated in one client device, and a group generation acceptance signal that accepts the proposal to generate a new group generated in the designated other client device in response to the group generation proposal signal.

With this configuration, a user can propose to other users that they create a new group, and if the other users accept the proposal, a new group can be launched with these users as its members.

As a result, users can set up groups that discuss new topics that are not limited to the content of conversations in existing groups, or groups made up of like-minded users, allowing them to make effective use of meetings.

The online dialogue system according to the fifth aspect of the present invention is characterized in that in the online dialogue system according to the third aspect of the present invention, the group generation request signal is a single-element group generation request signal generated in a client device, requesting the generation of a new group whose only component is the client device.

This configuration allows users to start new groups that consist only of themselves.

As a result, even if a user does not want to or is unable to leave a conversation room, they can still make the most of the meeting by creating a new group for themselves, without needing to converse with anyone.

The online dialogue system according to the sixth invention of the present application is characterized in that, in the online dialogue system according to any one of the first to fifth inventions of the present application, the dialogue control unit is provided with a specific client dialogue control unit configured to control the specific client devices to allow dialogue between them without causing them to leave the group to which they currently belong, when the dialogue control unit detects a specific client dialogue request signal, which is generated in a client device and includes a designation of other client devices belonging to the dialogue room, to allow dialogue between the specific client devices.

This configuration allows users to communicate privately with only specific users without having to move to another group.

Therefore, users can have private conversations (so-called private conversations) with other specific users, for example, about topics that go more in-depth with the main content of the conversation in their group, or about topics that are unrelated to the main content of the conversation in the group.

As a result, participants are not forced to feel overly tense or constrained, and the meeting can be run efficiently and smoothly overall.

The information processing device according to the seventh aspect of the present invention is characterized in that it is used in an online dialogue system according to any one of the first to sixth aspects of the present invention.

Therefore, by using these information processing devices in an online dialogue system, the same effect as any one of the first to sixth inventions described above can be achieved.

The program according to the eighth aspect of the present invention is a program for causing a computer to function as a dialogue control unit of an information processing device according to the seventh aspect of the present invention.

Therefore, by executing the program on a computer, the same effect as the seventh aspect of the invention described above can be achieved.

The recording medium according to the ninth aspect of the present invention is a recording medium storing the program according to the eighth aspect of the present invention.

Therefore, by having a computer execute the program stored in the recording medium, the same effect as the eighth aspect of the invention can be achieved.

The online dialogue method according to the tenth aspect of the present application is an online dialogue method performed using a group of information processing devices including a plurality of client devices capable of communicating information via an information communication means, in which each client device is configured to belong to a virtual group configured to be in a state in which it can communicate with other client devices belonging to the same group, and all groups are configured to belong to one virtual dialogue room, and the information processing device is characterized in that it includes a dialogue control step including an inter-group movement control step configured to add the client device as a component of the other group and control the client device to leave the group to which it previously belonged when the information processing device detects an inter-group movement request signal, which is generated in the client device and which requests a movement to another group that belongs to the dialogue room and includes a designation of a group other than the group to which the client device belongs.

Therefore, by using this method with a group of information processing devices including a plurality of client devices capable of communicating information via information communication means, the same effects as those of the first aspect of the invention can be achieved.

FIG. 1 is a block diagram showing the configuration of an online dialogue system 2 according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating the configuration of the server device 4. FIG. 3 is a block diagram illustrating the configuration of each client device 6. As shown in FIG. FIG. 4 is a block diagram showing an example of the hardware configuration of the server device 4 shown in FIG. 2 and the client device 6 shown in FIG. 3, and is an example in which one computer is used as each of the server device 4 and the client device 6. FIG. 5 is a diagram showing a schematic example of the configuration of a virtual dialogue room realized in the online dialogue system 2. As shown in FIG. FIG. 6 is a flowchart showing an example of the flow of processing in the server device 4 constituting the online dialogue system 2, and is a drawing for explaining mainly the processing related to the transmission and reception of various control data. FIG. 7 is a flow chart showing an example of a process flow in each client device 6 constituting the online dialogue system 2. As shown in FIG. FIG. 8 is a flow chart showing an example of a process flow in each client device 6 constituting the online dialogue system 2. As shown in FIG. FIG. 9 is a diagram showing an example of the user management table 21. As shown in FIG. FIG. 10 is a diagram showing an example of the server-side dialogue management table 22. As shown in FIG. FIG. 11 is a diagram showing an example of the client-side dialogue management table 41, and is a diagram for explaining the transition of the dialogue situation of each user. FIG. 12 is a diagram showing an example of the client-side dialogue management table 41, and is a diagram for explaining the transition of the dialogue situation of each user. 13A and 13B are diagrams showing an example of the client-side dialogue management table 41, and are diagrams for explaining the transition of the dialogue situation of each user. 14A and 14B are diagrams showing an example of the client-side dialogue management table 41, and are diagrams for explaining the transition of the dialogue situation of each user. 15A and 15B are diagrams showing an example of the client-side dialogue management table 41, and are diagrams for explaining the transition of the dialogue situation of each user. 16A and 16B are diagrams showing an example of a display screen 80 displayed on the LCD 70 of the client device 6 during processing in the online dialogue system 2. FIG. 17A and 17B are diagrams showing an example of a display screen 80 displayed on the LCD 70 of the client device 6 during processing in the online dialogue system 2. FIG. 18A and 18B are diagrams showing an example of a display screen 80 displayed on the LCD 70 of the client device 6 during processing in the online dialogue system 2. FIG. 19A and 19B are diagrams showing an example of a display screen 80 displayed on the LCD 70 of the client device 6 during processing in the online dialogue system 2. FIG. 20A and 20B are diagrams showing an example of a display screen 80 displayed on the LCD 70 of the client device 6 during processing in the online dialogue system 2. FIG.

(1. System Configuration)
FIG. 1 is a block diagram showing the configuration of an online dialogue system 2 according to an embodiment of the present invention.

The online dialogue system 2 includes a server device 4 and a number of client devices 6, 6, ... as information processing devices, and information such as text, voice, images, and control signals can be communicated between the server device 4 and each client device 6, and between the client devices 6, ... via information communication means 8 as appropriate.

Note that hereinafter, perceptual information (text, sound, images, etc.) to be displayed on the client device 6 may be referred to as "content data". Furthermore, information such as control signals (excluding content data) used to execute each process in the system 2 may be referred to as "control data". "Content data" and "control data" may be collectively referred to as "content data, etc."

Figure 2 is a block diagram illustrating the configuration of the server device 4.

As shown in FIG. 2, the server device 4 includes a server-side dialogue control unit 10 and a server-side memory unit 20.

The server-side dialogue control unit 10 is a dialogue control unit provided in the server device 4 as an information processing device, and includes a communication control unit 11 and a room management unit 12.

The communication control unit 11 controls the smooth communication of content data, etc. between the client devices 6, etc. Depending on the communication format, it also relays content data, etc.

The room management unit 12 manages the configuration of virtual dialogue rooms, virtual groups belonging to the dialogue rooms, and users of client devices 6 belonging to the groups.

The server-side storage unit 20 includes a user management table 21 and a server-side dialogue management table 22. The server-side storage unit 20 further stores a program (server-side program) that is executed on the server device 4 side in the system 2.

The user management table 21 is a table that stores user attributes, etc. FIG. 9 is a diagram showing an example of the user management table 21. In this example, the attributes of each user who uses the system 2 are stored as a "user ID" that is an identification indicator of the user, the user's "name," "affiliation," and a "password" for logging in to the system 2.

The user attributes stored in the user management table 21 are not limited to the above, and can be configured to include, for example, the user's gender, age, address, etc.

The server-side dialogue management table 22 is a table provided on the server device 4 side to manage (understand) the dialogue status of users. FIG. 10 is a diagram showing an example of the server-side dialogue management table 22. In this example, the following information is stored as information indicating the current dialogue status of each user: a "user ID," "destination information" indicating the destination for sending (uploading) content data, etc. to the user, a "group ID" which is an identification marker for the group to which the user belongs, and a "room ID" which is an identification marker for the dialogue room to which the user belongs.

Of these, "User ID" is the same as the information indicated in the item of the same name stored in the user management table 21.

Figure 3 is a block diagram illustrating the configuration of each client device 6.

As shown in FIG. 3, the client device 6 includes a client-side dialogue control unit 30 and a client-side memory unit 40.

The client-side dialogue control unit 30 is a dialogue control unit provided in a client device 6 serving as an information processing device, and includes a transmission/reception control unit 31, a display control unit 32, an inter-group movement control unit 33, a display control unit for other groups' dialogue content 34, a new group generation control unit 35, and a specific client dialogue control unit 36.

The transmission/reception control unit 31 controls the transmission of content data, etc. to other client devices 6 and the server device 4, and the reception of content data, etc. transmitted from other client devices 6 and the server device 4.

The display control unit 32 controls the display of the received content data according to predetermined specifications. Images from the content data are displayed, for example, by being drawn on the LCD 70 of the client device 6 (see FIG. 16A). Sound is displayed, for example, by being output as audio information from the speaker 71 of the client device 6 (see FIG. 16A; includes earphones, headphones, etc.; same below). Characters are displayed, for example, by being drawn on the LCD 70 of the client device 6 or output as audio information from the speaker 71 of the client device 6.

During the above display process, the display control unit 32 controls the content data received from each client device 6 (directly or indirectly via the server device 4) to be integrated and edited and then displayed on the client device 6, or the content data that has already been integrated and edited on the server device 4 to be displayed on the client device 6 either as is or with some processing.

When the inter-group movement control unit 33 detects an inter-group movement request signal, which is generated in the client device 6 and includes a designation of another group (a group that belongs to the dialogue room to which the user belongs but is other than the group to which the user belongs) and requests a movement to that other group, the inter-group movement control unit 33 is configured to add the user of the client device 6 as a component of that other group and to control the user of the client device 6 to leave the group to which the user previously belonged.

In this embodiment, the inter-group transfer request signal is generated in one client device 6, and the processing in the inter-group transfer control unit 33 is also configured to be executed in that client device 6.

The other group dialogue content display control unit 34 is configured to, when it detects an other group dialogue content display request signal, which is generated in the client device 6 and includes a designation of another group (a group that belongs to the dialogue room to which the user belongs but is other than the group to which the user belongs) requesting the display of dialogue content in that other group, control the display of the dialogue content of that other group on the client device 6 without causing the user of the client device 6 to leave the group to which the user currently belongs.

In this embodiment, the other group dialogue content display request signal is generated in one client device 6, and the processing in the other group dialogue content display control unit 34 is also configured to be executed in that client device 6.

When the new group generation control unit 35 detects a group generation request signal, which is generated in the client device 6 and requests the generation of a new group belonging to the dialogue room to which the client device 6 belongs, the new group is generated including the user of the client device 6 as a component, and is configured to control the users of the client device 6 who make up the new group to leave the group to which they previously belonged.

In this embodiment, the group generation request signal is generated in one or more client devices 6, and the processing in the new group generation control unit 35 is also configured to be executed in these client devices 6.

For example, the group generation request signal can be configured to include a group generation proposal signal that proposes the generation of a new group generated in one client device 6 including a designation of a user of another client device 6, and a group generation acceptance signal that accepts the proposal to generate a new group generated in the designated other client device 6 in response to the group generation proposal signal.

The group generation request signal can also be configured to be a single-element group generation request signal that requests the generation of a new group generated in one client device 6, the group having as its only component the user of that client device 6.

The specific client dialogue control unit 36 is configured to, when it detects a specific client dialogue request signal, which is generated in the client device 6 and which requests dialogue between users of a specific number of client devices 6 including the specification of other client devices 6 belonging to the dialogue room to which the client device 6 belongs, control the specific client dialogue control unit 36 to allow dialogue between users of the specific number of client devices 6 without causing the users of the specific number of client devices 6 to leave the group to which they currently belong.

In this embodiment, the specific client interaction request signal is generated in at least one of the specific client devices 6, and the processing in the specific client interaction control unit 36 is configured to be executed in the specific client devices 6.

The client-side storage unit 40 includes a client-side dialogue management table 41. The client-side storage unit 40 further stores a program (client-side program) to be executed on the client device 6 side in the system 2.

The client-side dialogue management table 41 is a table provided on the client device 6 side to manage (understand) the dialogue status of the user. Figures 11 to 15B are diagrams showing an example of the client-side dialogue management table 41, and are diagrams for explaining the transition of the dialogue status of each user.

In this example, the following information is stored to indicate the current dialogue status of each user: "User ID", "Destination Information", "Group ID", "Speaker Flag" indicating the current speaker (indicated by flag '1'), "Other Group Dialogue Content Display" indicating the group ID of the other group currently specified in the other group dialogue content display request signal, "Specific Client Dialogue Designation Destination" indicating the user ID of the user currently specified in the specific client dialogue request signal, and "Specific Client Dialogue Designation Source" indicating the user ID of the user currently issuing the specific client dialogue request signal. Note that in this table, '-' indicates that the information does not exist.

Of the information shown in the client-side dialogue management table 41, "user ID," "destination information," and "group ID" are the same as the information shown in the items of the same name stored in the server-side dialogue management table 22.

Figure 4 is a block diagram showing an example of the hardware configuration of the server device 4 shown in Figure 2 and the client device 6 shown in Figure 3, and is an example in which one computer is used as each of the server device 4 and the client device 6.

The server device 4 is not particularly limited, but in this example, it has the same configuration as a general server computer.

The server device 4 is a recording medium that stores the server device 4 side program of the online dialogue system 2, and is equipped with an auxiliary storage device 55 such as an HDD (hard disk drive) with a hard disk that is also the server side memory unit 20, a main storage device 54 into which the program stored in the auxiliary storage device 55 is loaded, a CPU 51 corresponding to the server side dialogue control unit 10 that executes the program loaded into the main storage device 54, a display device 52 such as an LCD (liquid crystal display device), an input device 53 such as a keyboard, mouse, trackpad, and a communication interface 56 for communicating with the client device 6 via the information communication means 8.

The client device 6 is not particularly limited, and may be, for example, a personal computer, a tablet computer, a portable information terminal device, or a mobile phone such as a smartphone.

The client device 6 is a recording medium that stores the client device 6 side program of the online dialogue system 2, and is equipped with an auxiliary storage device 65 such as an SSD (solid state drive) equipped with a flash memory that also serves as the client side memory unit 40, a main storage device 64 into which the program stored in the auxiliary storage device 65 is loaded, a CPU 61 corresponding to the client side dialogue control unit 30 that executes the program loaded into the main storage device 64, a display device 62 such as an LCD (liquid crystal display device) or speaker, an input device 63 such as input keys, a touch panel, a microphone (hereinafter sometimes abbreviated as "mic"), a camera, and a communication interface 66 for communicating with the server device 4 and other client devices 6 via information communication means 8.

The information communication means 8 is a communication means for transmitting information converted into electrical signals, optical signals, etc., and may be wired or wireless. Examples of information communication means 8 include computer networks such as WANs (Wide Area Networks) represented by the Internet and LANs (Local Area Networks), telephone lines (including mobile phone lines), communication lines such as dedicated lines, direct connections using communication cables or infrared rays, or combinations of these.

Figure 5 is a diagram showing a schematic example of the configuration of a virtual dialogue room realized in the online dialogue system 2. This diagram shows the status of dialogue room R01 (room ID: R01) shown in the server-side dialogue management table 22 shown in Figure 10 and the client-side dialogue management table 41 shown in Figure 11.

In this example, the dialogue room R01 is currently composed of four groups: group GA, group GB, group GC, and group GD. The users who compose one group, for example, user U01, user U02, user U03, and user U04 who compose group GA, are in principle capable of interacting with other users who belong to the same group (i.e., group GA), but are configured to be unable to interact with users who belong to other groups (i.e., groups GB, GC, and GD). Group GD is a single-element group whose only component is user U10. The current speaker of each group in the dialogue room R01 is hatched.

(2. Processing in this System)
Fig. 6 is a flow chart showing an example of a process flow in the server device 4 constituting the online dialogue system 2, and is a drawing for explaining mainly the process related to the transmission and reception of various control data. Fig. 7 and Fig. 8 are flow charts showing an example of a process flow in each client device 6 constituting the online dialogue system 2.

Figures 16A to 20B are diagrams showing examples of a display screen 80 displayed on the LCD 70 of a client device 6 (a smartphone in this example) during processing in the online dialogue system 2.

As shown in FIG. 16A etc., the client device 6 includes a display device 62 such as an LCD 70 and a speaker 71, and an input device 63 such as a microphone 72, a camera 73 and a touch panel 74.

An example of a processing procedure in the online dialogue system 2 will be described with reference to Figures 6 to 20B. The overall processing in the online dialogue system 2 is referred to as online dialogue processing.

(2-1. Login-related processing)
As shown in FIG. 7, the client device 6 monitors the login input entered from the input device 63 of the client device 6 (step S11).

When a user wishes to open a new dialogue room, the contents of the login input are not particularly limited, but can be configured to include, for example, the user's user ID and password, as well as a request to open a dialogue room.

On the other hand, if a user wishes to enter an existing dialogue room, the contents of the login input are not particularly limited, but can be configured to include, for example, the user's user ID and password, as well as the room ID and password of the dialogue room.

When login input is detected, the client device 6 executes the login request process (step S12).

In the login request process, the client device 6 sends a login request signal to the server device 4, notifying the server device 4 that a login input has been made and including the contents of the login input.

As shown in FIG. 6, the server device 4 monitors the login request signal from each client device 6 (step S1), and when it receives a login request signal from any of the client devices 6, it executes the login process (step S2).

In the login process, first, a user authentication process is executed. In the user authentication process, the server device 4 refers to the user management table 21 (see FIG. 9), and if the combination of the user ID and password included in the login request signal is registered in the user management table 21, it determines that the user is a registered member of the system and ends the user authentication process. However, the user authentication method is not limited to this, and for example, an authentication method using a public key and a private key can also be used.

The user authentication process does not necessarily have to be performed strictly. For example, even if a user is not registered in the user management table 21, the user authentication process can be considered successful after a predetermined process (e.g., a process such as provisional registration) is performed.

If the user authentication process is successful (including the case where it is deemed successful), then if the login request signal includes a request to open a dialogue room, a dialogue room setting process is executed. In the dialogue room setting process, the server device 4 opens a new virtual dialogue room with the user as the host, sets a room ID (e.g., R1) and a password for the dialogue room, associates these and stores them in the server-side storage unit 20 (not shown), and notifies the user of this information.

The host user can inform other users of the room ID and password of the chat room by some means (e.g., email) and invite them to participate in the chat room.

On the other hand, if the login request signal includes the room ID and password of an existing dialogue room, a dialogue room entry permission process is executed. In the dialogue room entry permission process, the server device 4 determines whether the room ID and password included in the login request signal match the information stored in the server-side storage unit 20, and if it determines that they match, it permits the user to log in (enter) the dialogue room.

In addition, the host user can be configured to be automatically allowed to enter the existing dialogue room after the dialogue room setting process is executed, without having to enter a login request that includes a request to enter the existing dialogue room again.

For users who are permitted to enter a dialogue room, their user ID is associated with the room ID of the dialogue room and stored in the server-side dialogue management table 22 (see Figure 10).

In the login process (step S2), the group assignment process and the communication mode determination process are then executed.

In the group assignment process, the server device 4 determines the group to which a user who is permitted to log in should initially belong within the dialogue room.

The method of group allocation is not particularly limited, but for example, a group (e.g., group GA) can be opened in the dialogue room, and users allowed to log in are assigned to the same group until the number of users reaches a predetermined expected capacity (e.g., four people), and after the expected capacity of the group is reached, another group (e.g., group GB) is opened, and users allowed to log in thereafter are assigned to the other group, and the same process can be repeated thereafter.

Alternatively, multiple groups can be set up in the conversation room in advance, and the group to which a user permitted to log in should belong can be assigned based on the user's attributes (e.g., affiliation, gender, age, address, etc.), based on each user's preferences, or randomly.

The group allocation method can be configured to be preset in the server device 4, or can be configured so that a user, particularly the organizer user, can specify the group allocation method to the server device 4 as appropriate.

For a user to whom a group is assigned, the user ID is associated with the group ID of the group and stored in the server-side dialogue management table 22 (see Figure 10).

Next, the communication mode determination process will be described. In the communication mode determination process, the server device 4 performs a process to determine the communication mode (communication path, communication standard, etc.) in which content data, etc. generated (or input, the same applies below) in each client device 6 will be communicated between other client devices 6 and the server device 4.

The communication format in this system 2 is not particularly limited, but in this embodiment, we will explain an example in which communication is performed using WebRTC (Web Real-Time Communication), a technology that enables real-time communication of content data, etc., via a web browser.

In this example, when using WebRTC, the communication formats assumed are a P2P (Peer to Peer) type, in which content data and the like is transmitted and received between client devices 6 directly (or in a state considered to be direct), and a SFU (Selective Forwarding Unit) type, in which communication is performed indirectly via the server device 4, and the server device 4 decides which communication format to use.

In a P2P type communication format, content data etc. generated in one client device 6 is sent individually to all other client devices 6, and content data etc. generated in the other client devices 6 is received individually from those other client devices 6. Therefore, if the number of other client devices 6 is n, there will be n routes for both upload and download. As a result, if the number n of client devices 6 with which to communicate becomes large, there is a risk that the communication load on the client devices 6 will become excessive.

On the other hand, in the SFU type communication mode, content data etc. generated in other client devices 6 are received individually from other client devices 6, just like in the P2P type communication mode, but content data etc. generated in one client device 6 only needs to be sent to the server device 4. Therefore, while there are n routes for downloading, there is only one route for uploading. As a result, even if the number of client devices 6 with which communication is possible increases, the communication load on the client device 6 does not become as large as in the P2P type communication mode.

In order to implement a P2P type communication format using WebRTC, in this embodiment, the server device 4 has a function as a Web server, a function as a signaling server, a function as a STUN (Session Traversal Utilities for NAT) server, and a function as a TURN (Traversal Using Relay around NAT) server.

The web server is used to provide the web browser of the client device 6 with web pages and the like for using the system 2.

The signaling server is used to exchange destination information (e.g., IP address and port number) between communication partners in order to carry out P2P type communication.

STUN servers and TURN servers are used to traverse so-called NATs and firewalls in order to carry out P2P type communication when the client device 6 is protected by a NAT (Network Address Translation) or a firewall.

In addition, in this embodiment, in order to execute an SFU type communication format using WebRTC, the server device 4 also has the functionality of an SFU server.

The SFU server is used to relay content data etc. received from each client device 6 and forward it directly to each client device 6.

The method of determining the communication type is not particularly limited, but for example, it can be configured to use P2P type when the number of participating members in one dialogue room is a predetermined number (e.g., 5 people) or less, and SFU type when it exceeds this number. It can also be configured to detect the communication load of the client device 6 and the processing load of the server device 4, and switch between P2P type and SFU type based on the detection results. Furthermore, it can be configured to forcibly switch to SFU type if there is a specified request from the client device 6 (e.g., a request to leave a recording or audio of the dialogue on the server device 4).

When the communication mode is determined in the communication mode determination process, the server device 4 writes the destination information of each user corresponding to the determined communication mode into the server-side dialogue management table 22 (see FIG. 10).

When the determined communication format is a P2P type communication format, the upload destination of the content data, etc. from the client device 6 is another client device 6, so for example, the IP addresses and port numbers of those client devices are written as the destination information for each user.

On the other hand, if the determined communication format is an SFU type communication format, the upload destination of the content data from the client device 6 is the SFU server equivalent part of the server device 4, so for example, an IP address indicating the SFU server equivalent part is written as the destination information for each user.

Finally, the server device 4 transmits the "user IDs,""destinationinformation," and "group IDs" of all users constituting the dialogue room stored in the server-side dialogue management table 22 (hereinafter, these data may be referred to as "server-side dialogue information," meaning information used for dialogue processing stored in the server device 4) to the client devices 6 of all users constituting the dialogue room (e.g., dialogue room R01), and completes the login process (Figure 6, step S2).

(2-2. Interaction information setting/update processing)
Next, as shown in FIG. 7, the client device 6 executes a dialogue information setting/update process (step S13).

In the dialogue information setting/update process, the client device 6 sets or updates the dialogue information on the client device 6 side based on the server-side dialogue information received from the server device 4.

The dialogue information on the client device 6 side (hereinafter, sometimes referred to as "client-side dialogue information", meaning information stored in the client device 6 and used for dialogue processing) is the data indicated in the items "User ID", "Destination information", and "Group ID" among the data listed in the client-side dialogue management table 41 shown in FIG. 11.

That is, in the dialogue information setting/update process, the “client-side dialogue information” in the client-side dialogue management table 41 is synchronized with the “server-side dialogue information” in the server-side dialogue management table 22 .

(2-3. Dialogue processing)
Next, the client device 6 executes an interactive process (step S14). A detailed example of the interactive process is shown in FIG.

(2-3-1. Data transmission/reception and display processing)
In the interactive processing, the client device 6 executes data transmission/reception and display processing (i.e., data transmission/reception processing and display processing (step S21).

In the data transmission/reception process, the client device 6 transmits content data, etc., input from the input device 63 (microphone 72, camera 73, touch panel 74, etc.) of the client device 6 or stored in the client-side memory unit 40 of the client device 6 to another client device 6 according to the current communication mode.

The destination (upload destination) when sending content data, etc. to each client device 6 is stored as "destination information" in the client-side dialogue management table 41, and this "destination information" corresponds to the current communication format (in this embodiment, P2P type or SFU type). Therefore, if content data, etc. is sent according to the "destination information", the data can be sent to other client devices 6 regardless of the communication format.

In the data transmission and reception process, a client device 6 receives content data, etc. transmitted from another client device 6 via a predetermined communication path corresponding to the current communication mode. In this embodiment, regardless of the communication path via which the data is received, the content data, etc. uploaded by each client device 6 is received by the other client device 6 as is, without being integrated, edited, or otherwise processed.

In the display process, the client device 6 is configured to integrate, edit, and otherwise process the content data generated in its own client device 6 and the content data received from other client devices 6, generate a display screen 80 and display it on the LCD 70 (this type of display process may hereinafter be referred to as "display process using a screen"), and output sound via the speaker 71 (this type of display process may hereinafter be referred to as "display process using sound").

First, we will explain the display process that uses a screen.

Figures 16A, 16B, 17A, 17B, 18A, 18B, 19A, 19B, 20A and 20B are drawings showing an example of the external appearance of a client device 6, and are used to explain the transition of the display screen 80 of the client device 6 in the present system 2. Note that hereafter, when it is necessary to particularly specify a user, the client device 6 used by user U01 may be referred to as client device 6a, the client device 6 used by user U03 as client device 6b, and so on.

As shown in FIG. 16A, a display screen 80 generated by a screen display process in the client device 6 is displayed on the LCD 70 of the client device 6. The configuration of the display screen 80 is not particularly limited, but in this example, the display screen 80 is configured to include a self-group display section 81 and an other group display section 86.

The self-group display section 81 displays the dialogue status of the group to which the user belongs (hereinafter sometimes referred to as the "self-group"; in this example, group GA). The configuration of the self-group display section 81 is not particularly limited, but in this example, it is configured so that user-specific display sections 82, which individually display images of each user constituting the group, are arranged in a row equal to the number of users constituting the group. In addition, a display showing the group ID of the group ("Group GA" in this example) is displayed in part of the self-group display section 81.

In addition, each user-specific display section 82 is configured to display the user's user ID (or the user's name) together with the user's image.

A speaker mark 83 indicating the current speaker in the own group is displayed in a part of the user-specific display section 82 corresponding to the user who is the speaker or in its vicinity. In this example, the outer frame of the user-specific display section 82 that has been changed to a specific color (e.g., blue) corresponds to the speaker mark 83.

The current speaker in each group is indicated by the "speaker flag" in the client-side dialogue management table 41 (see FIG. 11). The user whose "speaker flag" is set to '1' is the current speaker. The speaker mark 83 is displayed based on this "speaker flag".

In this embodiment, the user-specific display section 82 in which the image of the user (user U01 in this example) is displayed is configured to be displayed in a state that is distinguishable from other users belonging to the user's group. The "distinguishable state" is not particularly limited, but includes, for example, being placed in a specific position within the display screen 80. In this example, the user-specific display section 82 in which the image of the user is displayed is configured to always be placed in the upper left corner of the user's group display section 81. In addition, as a "distinguishable state," the size of the user-specific display section 82 in which the image of the user is displayed can also be made different from that of other users.

Next, the configuration of the other group display unit 86 will be described. The other group display unit 86 displays the dialogue status of groups other than the own group (in this example, groups GB, GC, and GD. Hereinafter, these may be collectively referred to as "other groups").

In this embodiment, the other group display unit 86 is configured to display the "unmanned group" in addition to the dialogue status of the "other groups." The "unmanned group" will be described later.

The configuration of the other group display section 86 is not particularly limited, but in this example, it is configured to have one group-specific display section 87 that displays images of other groups that belong to the dialogue room to which the user belongs (dialogue room R01 in this example) individually on a group basis.

The display method of the group-specific display section 87 is not particularly limited, but for example, the groups displayed in the group-specific display section 87 can be configured to be changed as appropriate. The method of changing the groups displayed in the group-specific display section 87 is also not limited, but for example, the groups can be displayed in the order of group GB, group GC, group GD, and unmanned group at regular intervals, and this can be repeated thereafter.

It is also possible to display a forward button 88 at a predetermined position (on the right and left sides in this example) near the group-based display section 87, and configure it so that when the forward button 88 is tapped, the group displayed in the group-based display section 87 changes. It is also possible to configure it so that when the group-based display section 87 is swiped, the group displayed in the group-based display section 87 changes.

The method of changing the groups displayed in the group-by-group display section 87 is not limited to the above-mentioned method. For example, the group displayed in the group-by-group display section 87 can be changed by performing a predetermined operation on the client device 6, such as performing a predetermined operation on the display screen 80 or operating a predetermined input key (not shown) on the client device 6. Furthermore, the above-mentioned group changing methods can also be used in combination.

The content of the image of the other group displayed in the group display section 87 is not particularly limited, but the image of the other group can be configured to use, for example, an image of a user who represents the other group.

The user who represents the other group is not particularly limited, but in this example, if there is a current speaker in the other group, the speaker is configured to be the user who represents the other group.

In this case, as described above, the current speaker in each group, including other groups, is indicated by the "speaker flag" in the client-side dialogue management table 41 (see FIG. 11). The image to be displayed in the group-specific display section 87 is determined based on the contents of this "speaker flag."

In addition, a display (in this example, "Group GB") showing the group ID of the other group currently displayed in the group-specific display section 87 is displayed in a part of the other group display section 86 (in this example, near the bottom end of the group-specific display section 87).

The group display section 87 is also configured to display the user ID (or name) of the user who represents the other groups currently being displayed, along with the image of that user.

The other group display unit 86 can also be configured, for example, to have a plurality of group-specific display units 87 arranged in the other group display unit 86. In this case, by arranging a number of group-specific display units 87 equivalent to the total number of all other groups (group GB, group GC, group GD) and unmanned groups (four in this example), the status of these groups can be displayed simultaneously.

In this embodiment, of the self-group display section 81 and the other-group display section 86 that constitute the display screen 80, the self-group display section 81 displays the dialogue status of the self-group in detail, while the other-group display section 86 displays the dialogue status of the other groups in a simplified manner compared to the dialogue status of the self-group.

Also, as shown in FIG. 16A, on the display screen 80, the self-group display section 81 is disposed above the other group display section 86, and in addition, the area occupied by the self-group display section 81 is configured to be larger than the area occupied by the other group display section 86.

In other words, in this embodiment, the display process on the screen is configured to primarily display the dialogue status of the own group, and additionally display the dialogue status of other groups. Of course, the configuration of the display process on the screen is not limited to this.

Next, we will explain the display process using audio.

The display method in the audio display process is not particularly limited, but similar to the above-mentioned screen display process, it is preferable to configure it so that mainly the audio of the dialogue in the own group (own group dialogue audio) is output, and additionally the audio of the dialogue in other groups (other group dialogue audio) is output.

When outputting other group dialogue voice from speaker 71, it is preferable to configure it so that one of the other groups is selected and output. For example, when one group-specific display section 87 is arranged in other group display section 86 (see FIG. 16A), it is possible to configure it so that only the dialogue voice of the other group (group GB in this example) currently displayed in group-specific display section 87 is output as other group dialogue voice.

Incidentally, the dialogue voice of a group, whether it is the self-group dialogue voice or the other-group dialogue voice, is in principle configured to be obtained by simply mixing the voices of all members belonging to the group using a known method, except when a specific process (for example, the specific client dialogue process described below) is being executed.

As a specific example of audio display processing, for example, it can be configured to output only the self-group dialogue voice from speaker 71, or it can be configured to output other-group dialogue voice from speaker 71 simultaneously with the self-group dialogue voice.

It can also be configured so that the other group dialogue voice and the own group dialogue voice can be switched and output from the speaker 71 alternatively, or the own group dialogue voice can be constantly output from the speaker 71 while allowing the user to select whether or not to output the other group dialogue voice from the speaker 71.

When the self-group dialogue voice and the other-group dialogue voice are configured to be output from the speaker 71 either simultaneously or by switching between them, it is preferable to configure the volume of the other-group dialogue voice to be lower than the volume of the self-group dialogue voice.

It is also possible to configure the ratio between the volume of the other group dialogue voice and the volume of the self group dialogue voice to be changeable. In this case, for example, the volume of the other group dialogue voice can be configured to be changeable between approximately 4/5 times and 0 times the volume of the self group dialogue voice. More preferably, the volume of the other group dialogue voice can be configured to be changeable between approximately 1/2 times and 0 times the volume of the self group dialogue voice.

Instead of outputting the other group dialogue voice from the speaker 71, or in addition to outputting the other group dialogue voice from the speaker 71, the other group dialogue voice converted into text (textualized other group dialogue voice) can be configured to be displayed in an appropriate position on the display screen 80, for example, in the other group display section 86. The textualized other group dialogue voice may be the other group dialogue voice directly converted into text, or it may be the other group dialogue voice that has been summarized and then converted into text.

In this manner, the data transmission/reception and display processing is executed (FIG. 8, step S21). However, if various interrupts (steps S22 to S27) are detected during the execution of the data transmission/reception and display processing, the client device 6 executes processing corresponding to these interrupts (steps S32 to S37).

(2-3-2. Speaker change processing)
The client device 6 monitors changes in speakers in its own group and other groups (step S22), and when it detects a change in the speaker, it updates the information in the "speaker flag" in the client-side dialogue management table 41 shown in Fig. 11 and changes the display related to the speaker on the display screen 80 of the client device 6 (step S32). This is called a speaker change process.

The method for detecting a change in the speaker in one's own group or another group is not particularly limited, but the following methods are possible, for example:

In other words, each client device monitors the voice level input from the microphone 72 of its own client device 6, and if the voice level exceeds a predetermined value and the voice level of the most recent speaker in the group (a user other than itself) is below the predetermined value, the client device 6 detects that the speaker in the group has changed to the user of its own client device 6.

Then, the client device 6 transmits a new speaker notification signal, which notifies the other client devices 6 that the user of the client device 6 has become the new speaker in the group, as control data. By receiving the new speaker notification signal, the other client devices 6 detect the change in the speaker in their own group or in the other groups.

In both the client device 6 that sent the new speaker notification signal and the client device 6 that received the new speaker notification signal, the information in the "speaker flag" in the client-side dialogue management table 41 is updated, and the display content of the display screen 80 of each client device 6 is updated based on the updated "speaker flag."

For example, if the speaker in group GA changes from user U02 to user U01, and the speaker in group GB changes from user U06 to user U07, the client-side dialogue management table 41 is updated by executing step S32, and the contents of the "speaker flag" change from FIG. 11 to FIG. 12.

For example, the display screen 80 of the client device 6 of user U01 changes from FIG. 16A to FIG. 16B. It can be seen that the display position of the speaker mark 83 in the self-group display section 81 has been changed from the user-specific display section 82 representing user U02 to the user-specific display section 82 representing user U01.

It can also be seen that the image showing the speaker of group GB displayed in the group-specific display section 87 of the other group display section 86 in the client device 6 has been changed from an image showing user U06 to an image showing user U07.

(2-3-3. Processing for displaying dialogue content of other groups)
The client device 6 monitors the other group dialogue content display request signal (i.e., a signal requesting display of dialogue content in another group that belongs to the dialogue room to which the client device 6 belongs and that includes a designation of a group other than the client device 6) generated in the client device 6 (step S23), and when the signal is detected, the dialogue content of the other group is displayed on the client device 6 without causing the user of the client device 6 to leave the group to which the user currently belongs (step S33). This is called the other group dialogue content display process.

The method for generating the other group dialogue content display request signal is not particularly limited, but the following method is conceivable, for example. As an example, a case will be described in which user U01 of group GA, who is a user of client device 6, requests to display the dialogue content in another group, group GB.

As shown in FIG. 16A, it is assumed that an image of group GB is currently displayed in the group-specific display section 87 of the other group display section 86 constituting the display screen 80 displayed on the client device 6.

According to this method, when user U01 selects, for example by tapping, the group-specific display section 87 on which the image of group GB of client device 6 shown in FIG. 16A is displayed, a request signal for displaying the contents of the dialogue of other groups specifying group GB is generated.

When a client device 6 detects a request signal to display other group dialogue content generated in its own client device 6, it stores the group ID (GB) of the other group specified in the request signal to display other group dialogue content as information related to itself (user U01) in the "display of other group dialogue content" in the client-side dialogue management table 41, as shown in FIG. 13A.

Based on the information in "Display of dialogue content of other groups" in the client-side dialogue management table 41, the client device 6 displays the dialogue content of the other group, group GB, on its own client device 6 without causing the user U01 to leave the group GA to which the user currently belongs.

The method of displaying the dialogue content of the other group on one's own client device 6 is not particularly limited, but for example, the dialogue voice of the other group (the dialogue voice of the other group) specified in the other group dialogue content display request signal can be configured to be output from the speaker 71 at a predetermined volume.

In this case, it is preferable to configure the volume of the other group dialogue voice output in this process (step S33) to be louder than the volume of the other group dialogue voice output in the normal display process (step S21).

When other group dialogue voice is output from speaker 71, it may be configured to output only the other group dialogue voice from speaker 71, or it may be configured to output both the other group dialogue voice and the self group dialogue voice from speaker 71.

When both the other group dialogue voice and the self group dialogue voice are configured to be output from speaker 71, the volume ratio between the two voices is not particularly limited, but the volume of the self group dialogue voice can be configured to be equal to the volume of the other group dialogue voice or lower than the volume of the other group dialogue voice.

Furthermore, it can be configured so that the ratio of the volume of the self-group dialogue voice to the volume of the other group dialogue voice can be adjusted.

As a method for displaying the dialogue content of the other group on one's own client device 6, instead of outputting the dialogue voice of the other group from the speaker 71, or in accordance with the various methods described above, the dialogue voice of the other group can be output from the speaker 71 and the dialogue voice of the other group converted into text (textualized dialogue voice of the other group) can be displayed on the other group display section 86 of the display screen 80. The textualized dialogue voice of the other group can be the dialogue voice of the other group directly converted into text, or the dialogue voice of the other group can be summarized and then converted into text.

In addition, in this embodiment, the content of the conversation with the other group is displayed on the client device 6 in this manner, and as shown in FIG. 17A, an other group designation mark 89 is displayed on or near a part of the group-specific display section 87 on the display screen 80. The other group designation mark 89 is a mark indicating that the other group has been designated in order to display the content of the conversation with the other group on the client device 6. In this example, the outer frame of the group-specific display section 87, which has been changed to a specific color (e.g., red), corresponds to the other group designation mark 89.

At the same time, a cancel button 90 and a move button 91 are displayed near the other group designation mark 89.

In the normal display process (step S21 described above), even if the groups (in this case, groups GB, GC, GD, and the unmanned group) to be displayed on the group-specific display section 87 of the client device 6 are configured to automatically switch at regular intervals, such automatic switching operation is not performed while the other group dialogue content display process is being executed, and only the dialogue content of the group (in this case, group GB) that is the target of the other group dialogue content display process is displayed on the client device 6.

The other group dialogue content display process can be terminated by operating the cancel button 90, for example by tapping it. The move button 91 will be described later.

The method of terminating the other group conversation content display process is not limited to the above method. For example, the other group conversation content display process can be terminated by performing a predetermined operation on the display screen 80, such as swiping the group-specific display section 87 shown in FIG. 17A or tapping the forward button 88, or by operating a predetermined input key (not shown) on the client device 6, or by performing a predetermined action on the client device 6.

In addition to or in combination with the above-mentioned termination method, it is also possible to configure the process to automatically terminate after a certain period of time has elapsed since the start of the other group dialogue content display process.

In this way, when a request signal for displaying other group conversation contents is detected (step S23), the client-side conversation management table 41 is updated by executing step S33, the contents of the "displaying other group conversation contents" change from FIG. 11 to FIG. 13A, and the other group conversation contents display process is started in the client device 6. When the other group conversation contents display process ends, the contents of the "displaying other group conversation contents" return to the contents shown in FIG. 11.

Then, the display screen 80 of the client device 6 is updated by the execution of step S33, and changes from Fig. 16A to Fig. 17A. When the other group conversation content display process ends, the display screen 80 of the client device 6 returns to the state shown in Fig. 16A.

(2-3-4. Inter-group transfer processing)
The client device 6 monitors the inter-group transfer request signal (i.e., a signal requesting transfer to another group that belongs to the dialogue room to which the client device 6 belongs and includes a designation of a group other than the group to which the client device 6 belongs) generated in the client device 6 itself (step S24), and when the signal is detected, the client device 6 adds the user of the client device 6 to a component of the other group and controls the user to leave the group to which the client device 6 belonged immediately before (step S34). This is called inter-group transfer processing.

The method for generating an inter-group transfer request signal is not particularly limited, but the following method is conceivable, for example. As an example, a case will be described in which user U01 of group GA, who is a user of client device 6, requests to transfer to another group, group GB.

As shown in FIG. 17A, the above-mentioned other group dialogue content display process (step S33) is executed on the client device 6.

According to this method, when user U01 operates, for example by tapping, a move button 91 displayed near the group-specific display section 87 of a client device 6 that is executing a process for displaying the contents of a dialogue between other groups, an inter-group move request signal specifying group GB is generated.

When the client device 6 detects the inter-group transfer request signal generated in its own client device 6, as shown in FIG. 13B, as information relating to itself (user U01) in the "group ID" of the client-side dialogue management table 41, it stores the group ID (GB) of the other group specified in the inter-group transfer request signal, instead of the group ID (GA) of the group to which the user immediately belonged.

As a result, user U01 is added as a member of group GB and leaves group GA, to which he previously belonged.

In this way, when an inter-group transfer request signal is detected (step S24), the client-side dialogue management table 41 is updated by executing step S34, and the contents of the "group ID" change from FIG. 11 to FIG. 13B via FIG. 13A.

Then, the display screen 80 of the client device 6 is updated by executing step S34, and changes from FIG. 16A through FIG. 17A to FIG. 17B. As shown in FIG. 17B, the self-group display section 81 of the display screen 80 displays four user-specific display sections 82 that display images of each user constituting the group GB to which user U01 has been moved (including user U01 who has become a new member of the group).

On the other hand, in FIG. 17A, it can be seen that the other group designation mark 89, the cancel button 90, and the move button 91 that were displayed in the other group display section 86 of the display screen 80 have been erased. Also, in the group-specific display section 87 of the other group display section 86, images of groups (in this example, group GA) other than the group (group GB) to which user U01 will newly belong are displayed.

The client device 6 sends a group change notification indicating that the client device 6 (user U01) has moved to another group (group GB) through the inter-group movement process to the server device 4 as control data, and also sends the group change notification to other client devices 6 directly or via the server device 4.

The processing in the other client devices 6 and server device 4 that receive the control data will be described later.

In this manner, in this embodiment, the process is configured to execute the inter-group transfer process (step S34) after the other group dialogue content display process (step S33). This configuration is convenient because it allows the user to know the dialogue content in the group to which the user is to be transferred before transferring between groups.

However, it is also possible to configure the inter-group transfer process to be executed without going through the other group dialogue content display process. For example, in cases where the dialogue content of other groups (subcommittee discussion topics) is known in advance, such as in the case of an online meeting in a subcommittee format, there is little need to go through the other group dialogue content display process.

In addition, when performing the inter-group movement process, it is possible to select whether or not to go through the other group conversation content display process.

(2-3-5. Interactive processing between specific clients)
The client device 6 monitors the specific inter-client dialogue request signal (i.e., a signal requesting dialogue among users of the specific multiple client devices including the designation of users of other client devices belonging to the dialogue room) generated in the client device 6 (step S25), and when the signal is detected, the client device 6 controls the specific multiple client devices to allow dialogue among the users of the specific multiple client devices without causing the users of the specific multiple client devices to leave the group to which they currently belong (step S35). This is called specific inter-client dialogue processing.

The method for generating a specific client interaction request signal is not particularly limited, but the following method is conceivable, for example. As an example, a case will be described in which user U01 of group GA, who is a user of client device 6, requests interaction with user U03, who is also a user in the same group.

As shown in FIG. 16A, a self-group display section 81 constituting a display screen 80 displayed on a client device 6 has four user-specific display sections 82 that display images of each user constituting group GA. A speaker mark 83 indicating the current speaker in group GA is displayed in the user-specific display section 82 representing user U02.

According to this method, when user U01, who is a user who is not the current speaker (hereinafter sometimes referred to as a "non-speaking user"), selects, for example by tapping, the user-specific display section 82 showing user U03, who is displayed as a non-speaking user, in the self-group display section 81 of his/her own client device 6 shown in FIG. 16A, a specific client dialogue request signal designating user U03 is generated.

When a client device 6 detects a specific client-to-client dialogue request signal generated in its own client device 6, as shown in FIG. 14A, it stores the user ID (U03) of the user specified in the specific client-to-client dialogue request signal as information relating to itself (user U01) in the "specific client-to-client dialogue designation destination" of the client-side dialogue management table 41, and stores the user ID (U01) of the user who generated the specific client-to-client dialogue request signal as information relating to user U03 in the "specific client-to-client dialogue designation source."

The fact that a specific client interaction request signal was generated in client device 6 and the contents of that signal are shared with other client devices.

In this way, sharing the fact that a signal was generated in one information processing device (e.g., client device 6) and the contents of that signal with another information processing device (e.g., another client device 6) can simply be referred to as "sharing a signal."

The method of sharing signals is not particularly limited, but for example, an information processing device that generates a signal can be configured to transmit the contents of the signal as (part of) control data to another information processing device. The information processing device that receives the signal interprets the contents of the signal and performs the necessary processing, such as rewriting its own table.

In addition, each information processing device can be configured to store tables or the like with the same content (or with some of the same content), and the tables of each information processing device can be configured to be synchronized in whole or in part via the information communication means 8 as appropriate.

Now, the client device 6a of user U01 displays a dialogue destination mark 84 indicating the user (hereinafter sometimes referred to as the "dialogue destination user") designated in the specific client dialogue request signal in an appropriate portion of the display screen 80 of the client device 6a as shown in FIG. 18A, based on information relating to itself (user U01) in the "specific client dialogue destination" of the client-side dialogue management table 41 shown in FIG. 14A. In this example, the dialogue destination mark 84 is configured by changing the outer frame of the user-specific display section 82 relating to the designated user (U03) to a specific color (e.g. red).

On the other hand, in the client device 6b of user U03, who is the user specified in the specific client-to-client dialogue request signal, the specific client-to-client dialogue request signal is shared as described above, and the client-side dialogue management table 41 is configured to have the same contents as that shown in FIG. 14A.

Based on information related to itself (user U03) in the "specific client dialogue designator" field in its own client-side dialogue management table 41 (see FIG. 14A), the client device 6b of user U03 displays a dialogue designator mark 85 indicating the user who generated the specific client dialogue request signal (hereinafter sometimes referred to as the "dialogue designator user") in an appropriate portion of the display screen 80 of its own client device 6b, as shown in FIG. 18B. In this example, the dialogue designator mark 85 is configured by changing the outer frame of the user-specific display section 82 related to the designator user (U01) to a specific color (e.g. red).

Based on the information in the "specific client dialogue destination" and "specific client dialogue source" in the client-side dialogue management table 41, client device 6a and client device 6b respectively control users U01 and U03 to allow dialogue between them without causing them to leave the group GA to which they currently belong.

The method of dialogue between users of the specific client devices in the specific client dialogue process (hereinafter, this may be referred to as "specific client dialogue") is not particularly limited, but in this embodiment, the voice of the specific client dialogue (specific client dialogue voice) is output only from the speakers 71 of the specific client devices 6, and is not output from the speakers 71 of other client devices 6. In other words, the self-group dialogue voice in the above-mentioned audio display process (step S21) is configured not to include the specific client dialogue voice.

This configuration makes it possible to prevent interactions between specific clients from interfering with normal interactions (interactions between users other than the users of the specific client devices) in the group to which the specific client device 6 belongs.

In addition, the voice input from the specific client devices 6 in the specific inter-client dialogue is configured not to be subject to the speaker change process (FIG. 8, steps S22 and S32). By configuring in this way, it is possible to prevent the "current speaker" in the group to which the specific client device 6 belongs from being changed by the specific inter-client dialogue.

In addition, in the specific inter-client dialogue processing, there are no particular limitations on how the dialogue voice output from the speaker 71 of the specific multiple client devices 6 is configured, but for example, it can be configured so that the dialogue voice output from the speaker 71 of the specific multiple client devices 6 in the processing can include self-group dialogue voice.

In this case, the system may be configured to output both the specific client dialogue voice and the self-group dialogue voice from the speaker 71, or it may be configured to allow a choice between outputting both the specific client dialogue voice and the self-group dialogue voice from the speaker 71, or outputting only the specific client dialogue voice from the speaker 71.

When both the specific client dialogue voice and the self-group dialogue voice are output from speaker 71, the volume ratio between the two voices is not particularly limited, and can be configured to change the ratio, for example.

Furthermore, in the client device 6a of the dialogue specifying user (in this case, user U01), for example, the volume of the self-group dialogue voice can be configured to be equal to the volume of the dialogue voice between specific clients, or to be lower than the volume of the dialogue voice between specific clients.

On the other hand, in the client device 6b of the designated dialogue user (user U03 in this case), for example, the volume of the self-group dialogue voice can be configured to be equal to the volume of the dialogue voice between specific clients or to be louder than the volume of the dialogue voice between specific clients.

In addition, in the specific client dialogue processing, as a method for displaying the self-group dialogue voice or the specific client dialogue voice on the client device 6 of the dialogue designating user and/or the dialogue designated user, instead of outputting these voices from the speaker 71 of the client device 6, or in accordance with the various methods described above, it is also possible to configure the device to output these voices from the speaker 71 and display these voices converted into text on the display screen 80. The voices converted into text may be the self-group dialogue voice or the specific client dialogue voice converted directly into text, or may be the voices converted into text after being summarized.

For example, in a dialogue process between specific clients, a method for displaying self-group dialogue voice on the client device 6a of the dialogue specifying user can be configured such that, instead of outputting the voice from the speaker 71 of the client device 6a, or in accordance with the various methods described above, the voice is output from the speaker 71 and the voice converted into text is displayed on the display screen 80.

In addition, in the specific client dialogue processing, as a method for displaying the specific client dialogue voice on the client device 6b of the dialogue designated user, instead of outputting the voice from the speaker 71 of the client device 6b, or according to the various methods described above, the voice can be output from the speaker 71 and the voice converted into text can be displayed on the display screen 80.

As shown in FIG. 18A, the display screen 80 of the client device 6a of the dialogue specifying user displays a cancel button 92 together with the dialogue destination mark 84 displayed in the self group display section 81.

On the other hand, on the display screen 80 of the client device 6b of the dialogue destination user, as shown in FIG. 18B, a cancel button 93 and a move button 94 are displayed together with the dialogue designation source mark 85 displayed in the self group display section 81.

The cancel button 92 or the cancel button 93 can be configured to end the specific client interaction process by operating it, such as by tapping it. The move button 94 will be described later.

The method of terminating the specific inter-client dialogue process is not limited to the above method. For example, the specific inter-client dialogue process can be terminated by performing a specific operation on the client device 6a or the client device 6b, such as performing a specific operation on the display screen 80 of the client device 6a or the client device 6b, or operating a specific input key (not shown) of the client device 6a or the client device 6b.

In addition to or in combination with the above termination method, it is also possible to configure the process to automatically terminate after a certain time has elapsed since the start of the specific client dialogue process, or to configure the process to automatically terminate when the specific client dialogue sound remains at or below a certain level (e.g., silent) for a certain period of time during the specific client dialogue process.

In this way, on condition that a specific inter-client dialogue request signal (step S25) is detected, the client-side dialogue management table 41 is updated by executing step S35, the contents of the "specific inter-client dialogue designated destination" and "specific inter-client dialogue designated source" change from FIG. 11 to FIG. 14A, and specific inter-client dialogue processing is started between a specific number of client devices. When the specific inter-client dialogue processing ends, the contents of the "specific inter-client dialogue designated destination" and "specific inter-client dialogue designated source" return to the contents shown in FIG. 11.

Then, the display screen 80 of the client device 6a is updated by executing step S35, changing from the state shown in FIG. 16A to the state shown in FIG. 18A, and when the specific inter-client dialogue process ends, the display screen 80 of the client device 6a returns to the state shown in FIG. 16A. The display screen 80 of the client device 6b is updated by executing step S35, changing from a state similar to FIG. 16A (not shown) to the state shown in FIG. 18B, and when the specific inter-client dialogue process ends, the display screen 80 of the client device 6b returns to the state similar to FIG. 16A.

In this example, a non-utterance user who is the dialogue designation source user designates another non-utterance user who is the dialogue designation destination user in the same group, and a specific client-to-client dialogue is carried out between the two users. However, the specific client-to-client dialogue process is not limited to this.

For example, a non-uttering user who is the user who specified the dialogue can specify two or more other non-uttering users who are the dialogue destination users within the same group, allowing specific client-to-client dialogue between the three or more users.

It is also possible to configure the system so that even if the dialogue designation source user and/or the dialogue designation destination user are the speakers in the group, they can start a specific inter-client dialogue process. However, it is only after these dialogue designation source users and/or dialogue designation destination users become non-speaking users that they are actually able to have a specific inter-client dialogue.

In addition, if the interaction specifying user and the interaction specified user belong to the same interaction room, it is possible to configure the system so that specific client interaction processing can be performed between these users even if they belong to different groups.

(2-3-6. New group generation process)
The client device 6 monitors group generation request signals (i.e., signals requesting the generation of a new group belonging to the dialogue room to which the client device 6 belongs) generated in one or more client devices 6 including the client device 6 itself (step S26), and when the client device 6 detects the signal, it generates a new group including the one or more client devices 6 as constituent elements, and controls the client devices constituting the new group to leave the group to which they previously belonged (step S36). This is called a new group generation process.

The new group generation process will be explained separately as a multiple element group generation process that generates a new group whose components are multiple users, and a single element group generation process that generates a new group whose components are one user.

(2-3-6-1. Multiple element group generation process)
The form of the group generation request signal in the multi-element group generation process is not particularly limited, but for example, the group generation request signal can be configured to include a group generation proposal signal proposing the generation of a new group generated in one client device 6 including the designation of other client devices 6, and a group generation acceptance signal accepting the proposal for the generation of a new group generated in the designated other client devices 6 in response to the group generation proposal signal.

The method of generating the group creation proposal signal and the group creation acceptance signal is not particularly limited, but the following method is conceivable, for example. As an example, a case will be described in which user U01 of group GA, who is a user of client device 6a, specifies user U03 of client device 6b who belongs to the same group, and requests the creation of a new group with both users as components.

As shown in Figures 18A and 18B, the specific client interaction process (step S35) is executed between client device 6a and client device 6b.

According to this method, the specific client interaction request signal that specifies user U03 and that is generated in the specific client interaction process (step S35) also serves as a group generation proposal signal that specifies user U03. Therefore, the group generation proposal signal is generated in client device 6a and shared with client device 6b.

When the user U03 operates the move button 94 (see FIG. 18B) displayed on the display screen 80 of the client device 6b that is executing the specific inter-client dialogue process, for example by tapping the move button 94, a group creation acceptance signal is generated. The group creation acceptance signal is shared with the client device 6a by any of the above methods.

When client device 6a detects the group generation proposal signal generated in its own client device 6a and the group generation acceptance signal generated in client device 6b, as shown in FIG. 14B, it stores the group ID (GE) of the group newly generated in the multi-element group generation process as information related to itself (user U01) and user U03 in the "Group ID" of client-side dialogue management table 41, in place of the group ID (GA) of the group to which it immediately belonged. In client device 6b, the same process as that in client device 6a is also performed.

As a result, a new group GE is generated whose members are users U01 and U03, and users U01 and U03 leave the group GA to which they previously belonged.

In this way, when client device 6a detects a group generation request signal including a group generation proposal signal and a group generation acceptance signal (step S26), client-side dialogue management table 41 is updated by executing step S36, and the contents of the "group ID" change from FIG. 11 to FIG. 14B via FIG. 14A. The same is true for client device 6b.

The display screen 80 of the client device 6a is updated by executing step S36, and changes from the state shown in FIG. 16A, via FIG. 18A, to FIG. 19A.

Meanwhile, the display screen 80 of the client device 6b is updated by executing step S36, and changes from a state similar to that shown in FIG. 16A, via FIG. 18B, to FIG. 19B.

Client device 6a and/or client device 6b transmit a group change notification indicating that a new group (group GE) has been generated by the multi-element group generation process, the new group having itself (user U01) and user U03 as components, to server device 4 as control data, and also transmits the notification to other client devices 6 directly or via server device 4.

The processing in the other client devices 6 and server device 4 that receive the control data will be described later.

In this manner, in this embodiment, the specific client interaction process (step S35) is followed by a multiple element group generation process (step S36) as a new group generation process. This configuration is advantageous because it allows a user to have a dialogue beforehand with other users who may become components of a new group, for example, about the purpose of generating the new group, before generating the new group.

However, it is also possible to configure the system to execute the multiple element group generation process without going through the specific client interaction process. For example, if multiple users who may become members of a new group are familiar with each other's way of thinking, there is little need to go through the specific client interaction process.

It can also be configured so that when executing the multiple element group generation process, you can choose whether or not to go through specific client interaction processing.

In this example, a non-talking user designates another non-talking user in the same group to generate a new group with these two users as components, but the multi-element group generation process is not limited to this.

For example, a non-active user can specify two or more other non-active users in the same group to generate a new group with those three or more users as components.

In addition, if all of the multiple users who are to be components of a newly generated group belong to the same dialogue room, it is possible to configure the system so that a new multi-element group can be generated by these users even if some or all of the multiple users belong to different groups.

Also, it is possible to configure so that the multiple-element group generation process can be started even if any or all of the multiple users who are to become constituent elements of the newly generated group are speakers in the group to which they currently belong. However, the speakers do not actually become constituent elements of the new multiple-element group until these users become non-speaking users.

(2-3-6-2. Single element group generation process)
The method for generating a single-element group is not particularly limited, but the following method may be considered, for example: As an example, a case will be described in which a user U01 of a group GA, who is a user of a client device 6a, requests the generation of a new group having himself as the only element.

This method generates a single element group using the same procedure as the inter-group movement process (step S34) described above.

As shown in FIG. 16A, the above display process (step S21) is assumed to be executed on the client device 6a.

In the display process (step S21), it is assumed that an image showing an "unmanned group" is currently displayed in the group-specific display section 87 of the other group display section 86 constituting the display screen 80 of the client device 6a (not shown).

An "unmanned group" is a group that has zero component users and is a dummy group used when executing the single-element group generation process, but is configured to be treated the same as "other groups" in the display process (step S21), other group dialogue content display process (step S33), and inter-group movement process (step S34).

In this state, when user U01 selects, for example by tapping, the group-specific display section 87 in which the image of the unmanned group is displayed, a request signal for displaying the dialogue content of other groups specifying the unmanned group (hereinafter sometimes referred to as the "unmanned group designation signal") is generated.

When client device 6a detects an unmanned group designation signal generated in its own client device 6, it stores the group ID (NULL) of the unmanned group designated in the unmanned group designation signal as information related to itself (user U01) in the "display of dialogue content of other groups" in the client-side dialogue management table 41, as shown in FIG. 15A.

The client device 6a is configured to display an other group designation mark 89 in or near a part of the group-specific display section 87 of the display screen 80, as shown in FIG. 20A, based on the information in the "other group dialogue content display" in the client-side dialogue management table 41. The other group designation mark 89 displayed based on the unmanned group designation signal may be specifically referred to as the unmanned group designation mark 89.

The unmanned group designation mark 89 is a mark indicating that an unmanned group has been designated by an unmanned group designation signal. In this example, the outer frame of the group-specific display section 87, which has been changed to a specific color (e.g., red), corresponds to the unmanned group designation mark 89.

At the same time, a cancel button 90 and a move button 91 are displayed near the unmanned group designation mark 89.

The single element group generation process can be terminated by operating the cancel button 90, for example by tapping it.

Then, when user U01 operates the move button 91 shown in FIG. 20A, for example by tapping it, an inter-group move request signal specifying an unmanned group is generated. When user U01 moves to the unmanned group, a new single-element group is generated. Therefore, in this method, the inter-group move request signal specifying an unmanned group corresponds to a single-element group generation request signal.

When the client device 6a detects the single-element group generation request signal generated in the client device 6a itself, as shown in FIG. 15B, as information relating to itself (user U01) in the "group ID" of the client-side dialogue management table 41, the client device 6a stores the group ID (GF) of the group newly generated by the single-element group generation request signal in place of the group ID (GA) of the group to which the client device 6a previously belonged, as information relating to the client device 6a itself (user U01).

As a result, a new single-element group, group GF, is generated whose only component is user U01, and user U01 leaves group GA, to which he previously belonged.

In this way, when the client device 6a detects a single-element group generation request signal as a group generation request signal (step S26), the client-side dialogue management table 41 is updated by executing step S36, and the contents of the "group ID" change from FIG. 11 to FIG. 15B via FIG. 15A.

The display screen 80 of the client device 6a is updated by executing step S36, and changes from a state similar to that shown in FIG. 16A, via FIG. 20A, to FIG. 20B.

The client device 6a sends a group change notification to the server device 4 as control data indicating that a new single-element group (group GF) has been generated by the single-element group generation process, the group change notification including only the client device 6a (user U01) as a component, and also sends the group change notification to other client devices 6 directly or via the server device 4.

The processing in the other client devices 6 and server device 4 that receive the control data will be described later.

In this manner, in this embodiment, a single element group is generated using a procedure similar to that of the inter-group movement process (step S34). By configuring in this manner, it is possible to simplify the processing configuration of the entire system.

However, a different procedure can also be used, for example, to display a button for generating a single element group on the display screen 80 of the client device 6 and generate a single element group by operating that button.

Now, the user's client device 6 constituting a single element group can be configured to output a specified sound, image and/or text. In this case, it can be configured to output, for example, music as sound. It can be configured so that the user can select whether or not to output sound, or the content of the sound to be output.

The same applies when outputting images and/or text. When outputting images and/or text, the display screen 80 of the client device 6 can be configured to change from the state shown in FIG. 20B. For example, the image and/or text can be configured to be displayed in the self-group display section 81. In this case, the user-specific display section 82 already displayed in the self-group display section 81 can also be configured to be hidden temporarily or until the single-element group is dissolved.

In addition, the client device 6 of a user who constitutes a single element group can also perform similar processes (e.g., displaying the content of conversations with other groups, moving between groups, etc.) to those of the client device 6 of a user who constitutes a multiple element group under the same conditions as those of the client device 6 of a user who constitutes a multiple element group.

(2-3-7. Logout process)
The client device 6 monitors the logout input input from the input device 63 of the client device 6 (step S27).

When the logout input is detected, the client device 6 transmits a logout notification indicating that the client device 6 will log out of the dialogue room as control data to the server device 4, and also transmits the control data to the other client devices 6 directly or via the server device 4, and then terminates the online dialogue processing in the client device 6 (step S37). As a result, the user of the client device 6 leaves the dialogue room to which the user belonged.

The processes in the other client devices 6 and the server device 4 that receive the control data will be described later.

(2-4. Other processing)
6, the server device 4 monitors the communication mode in the present system 2 and various notifications sent in the form of control data or the like from each client device 9, and executes a predetermined process based on the results of these monitoring (steps S1 to S8). The processes shown in steps S1 and S2 are as described above.

On the other hand, as shown in FIG. 7, each client device 6 monitors various notifications sent in the form of control data or the like from the server device 4 or other client devices 6 (steps S15 to S17), and performs processing such as updating dialogue information based on the results of these monitoring (step S13).

That is, as shown in FIG. 6, the server device 4 monitors changes in the communication mode (in this embodiment, P2P type or SFU type) in the system 2 determined by the server device 4 (step S3), and when a change in the communication mode is detected, it executes a communication mode change process (step S4).

In the communication mode change process, the server device 4 changes the information stored in the "destination information" in the server-side dialogue management table 22 to information corresponding to the changed communication mode, and generates a communication mode change notification including information that the communication mode has been changed and the information stored in the changed "destination information", and transmits this notification to each client device 6.

On the other hand, as shown in FIG. 7, the client device 6 monitors whether or not a communication mode change notification has been received (step S15), and if such a notification has been received, executes the necessary update process of the dialogue information (step S13).

In this case, in the process of updating the dialogue information, the client device 6 changes the information stored in the "destination information" in the client-side dialogue management table 41 to information indicating the "destination information" described in the communication form change notification.

As shown in FIG. 6, the server device 4 also monitors group change notifications sent from the client device 6 (step S5), and when it detects receipt of such a notification, it executes a group change process (step S6).

The group change notifications to be monitored include those sent by the relevant user during the inter-group transfer process (Figure 8, step S34) or the new group creation process (Figure 8, step S36).

In the group change process, the server device 4 rewrites the information related to the user in the "group ID" in the server-side dialogue management table 22 to the changed information, and, if necessary, forwards the received group change notification to other client devices 6.

On the other hand, as shown in FIG. 7, the client device 6 monitors whether a group change notification has been received from the server device 4 or another client device 6 (step S16), and if such a notification has been received, executes the necessary update process of the dialogue information (step S13).

In this case, in the process of updating the dialogue information, the client device 6 rewrites the information related to the user in the "group ID" field of the client-side dialogue management table 41 to the updated information.

As shown in FIG. 6, the server device 4 also monitors the logout notification sent from the client device 6 (step S7), and when it detects receipt of the notification, it executes the logout process (step S8).

During the logout process, the server device 4 deletes the column (row) related to the corresponding user from the server-side dialogue management table 22, and, if necessary, forwards the received logout notification to another client device 6.

On the other hand, as shown in FIG. 7, the client device 6 monitors whether a logout notification has been received from the server device 4 or another client device 6 (step S17), and if such a notification is received, executes the necessary update process of the dialogue information (step S13).

In this case, in the dialogue information update process, the client device 6 deletes the column (row) related to the corresponding user from the client-side dialogue management table 41.

Note that steps S1 to S8 shown in FIG. 6 correspond to the room management unit 12 of the server-side dialogue control unit 10 of the server device 4 in FIG. 2.

Steps S11 to S17 shown in FIG. 7 (including steps S21 to S27 and steps S32 to S37 shown in FIG. 8, which constitute step S14) correspond to the client-side dialogue control unit 30 of the client device 6 in FIG. 3.

Of these, step S21 shown in FIG. 8 corresponds to the transmission/reception control unit 31 and the display control unit 32 of the client-side dialogue control unit 30.

8 correspond to the other group dialogue content display control unit 34 of the client-side dialogue control unit 30. Steps S24 and S34 correspond to the inter-group movement control unit 33. Steps S25 and S35 correspond to the specific client dialogue control unit 36. Steps S26 and S36 correspond to the new group creation control unit 35.

3. Other Embodiments
In the above embodiment, an example is given in which the client device is responsible for all of the functions of the display control unit 32 (see FIG. 3) in this system, but it is also possible to configure the system so that a server device is responsible for some of the functions of the display control unit in this system.

In this case, for example, the server device can be configured to handle the function of integrating and editing the content data received from each client device. To achieve such a configuration, for example, the server device can be configured to have the functionality of an MCU (Multipoint Control Unit) server.

In addition, in the above embodiment, an example is described in which all of the functions of the inter-group movement control unit 33, other group dialogue content display control unit 34, new group generation control unit 35, and specific client dialogue control unit 36 (see Figure 3) in this system are handled by a client device as an information processing device, but it is also possible to configure the system so that all or part of the functions of the inter-group movement control unit, other group dialogue content display control unit, new group generation control unit, and specific client dialogue control unit are handled by a server device as an information processing device.

In addition, in the above embodiment, an example is described in which the system executes all of the functions of the inter-group movement control unit 33, the other group dialogue content display control unit 34, the new group generation control unit 35, and the specific client dialogue control unit 36 (see FIG. 3), but the system can be configured to execute only some of the functions of the inter-group movement control unit, the other group dialogue content display control unit, the new group generation control unit, and the specific client dialogue control unit.

For example, if the present system is configured to execute only the function of a specific client-to-client dialogue control unit among the above functions, and a virtual dialogue room is composed of only one virtual group, i.e., the virtual dialogue room and the virtual group are regarded as the same, then the online dialogue system executing only that function can be understood as Invention A shown below.

[Invention A]
An online dialogue system including a group of information processing devices including a plurality of client devices capable of communicating information via an information communication means,
Each of the client devices is configured to belong to a virtual interaction room configured to be in an interactive state with other client devices belonging to the interaction room;
The information processing device includes:
a specific client interaction control unit configured to, when detecting a specific client interaction request signal, which is generated in the client device and which requests an interaction between a specific plurality of client devices including a designation of other client devices belonging to the interaction room, control the specific plurality of client devices to allow an interaction between the specific plurality of client devices without causing the specific plurality of client devices to leave the interaction room to which they currently belong;
Having the following features:
An online dialogue system.

In addition, in each of the above-described embodiments, the server device and the client device are each configured using one computer, but the present invention is not limited to this. The server device can also be configured using two or more computers. In this case, the two or more computers can be connected via the information communication means 8.

The client device can also be configured with two or more computers. In this case, the two or more computers can also be connected via the information communication means 8.

In addition, in this embodiment, a hard disk mounted in an HDD is exemplified as a recording medium storing a program on the server device 4 side of the online dialogue system 2, and a flash memory mounted in an SSD is exemplified as a recording medium storing a program on the client device 6 side, but the recording medium storing the program is not limited to these, and for example, an external memory card, CD-ROM, DVD-ROM, flexible disk, or magnetic tape can also be used as a recording medium storing a program. Furthermore, a main memory device can also be used as a recording medium storing a program.

The manner in which the program is distributed is not particularly limited, and the program may be distributed in a state in which it is stored on a recording medium, or the program may be distributed via wired or wireless information communication means.

The manner in which the program is recorded is not particularly limited. In addition to being stored or distributed on a recording medium in a form that can be directly executed, it can also be stored or distributed on a recording medium in a compressed form that can be decompressed for use.

In each of the above-described embodiments, the functions of Figures 2 and 3 are implemented using a computer, but some or all of these functions may be implemented using hardware logic.

Furthermore, the above-mentioned block diagrams, hardware configurations, flow charts, table (database) configurations, display screen configurations, etc. are given as examples, and the present invention is not limited to these.

It is also possible to configure some or all of the data that makes up a table (database) to be stored individually as variables.

In the above, the present invention has been described as a preferred embodiment, but each term is used for explanation, not for limitation, and can be modified within the scope of the appended claims without departing from the scope and spirit of the present invention. In addition, in the above, only some typical embodiments of the present invention have been described in detail, but those skilled in the art will easily recognize that many modifications can be made in the above typical embodiments without departing from the novel teachings and advantages of the present invention. Therefore, all such modifications are intended to be included in the scope of the present invention.

6: Client device 30: Client-side dialogue control unit 33: Inter-group movement control unit

Claims (8)

An online dialogue system including a plurality of client devices and/or a server device capable of communicating information via an information communication means,
Each of the client devices is configured to belong to a virtual group configured to be able to interact with other client devices belonging to the same group, and all of the groups are configured to belong to one virtual interaction room;
The client device and/or the server device ,
a dialogue control unit including a new group generation control unit configured to, when detecting a group generation request signal, which is generated in the client device, requesting the generation of a new group belonging to the dialogue room, generate a new group including the client device as a constituent element, and to control the client devices constituting the new group to leave the group to which they previously belonged;
Equipped with
the group generation request signal is configured to include a group generation proposal signal, generated in one client device, proposing the generation of a new group including the designation of another client device, and a group generation acceptance signal, generated in response to the group generation proposal signal, proposing the generation of a new group in the designated other client device;
An online dialogue system. 2. The online dialogue system of claim 1,
The dialogue control unit includes:
an other group dialogue content display control unit that, when detecting an other group dialogue content display request signal generated in the client device and requesting display of dialogue content in another group that belongs to the dialogue room and includes a designation of a group other than the group to which the client device belongs, controls the client device to display the dialogue content of the other group on the client device without causing the client device to leave the group to which the client device currently belongs;
Having the following features:
An online dialogue system. In the online dialogue system according to any one of claims 1 to 2,
The dialogue control unit includes:
an inter-group movement control unit configured to, when detecting an inter-group movement request signal, which is generated in the client device and which requests a movement to another group that belongs to the dialogue room and includes a designation of a group other than the group to which the client device belongs, add the client device as a constituent element of the other group and cause the client device to leave the group to which the client device previously belonged;
Having the following features:
An online dialogue system. In the online dialogue system according to any one of claims 1 to 3 ,
The dialogue control unit includes:
a specific inter-client dialogue control unit configured to, when detecting a specific inter-client dialogue request signal, which is generated in the client device and which requests dialogue among a specific plurality of client devices including designation of other client devices belonging to the dialogue room, control the specific plurality of client devices to permit dialogue among the specific plurality of client devices without causing the specific plurality of client devices to leave a group to which they currently belong;
Having the following features:
An online dialogue system. 5. The client device and/or the server device used in the online dialogue system according to claim 1 . A program for causing a computer to function as the dialogue control unit of the client device and/or the server device of claim 5 . A computer-readable recording medium storing the program according to claim 6 . An online interaction method using a plurality of client devices and/or a server device capable of communicating information via an information communication means, comprising:
Each of the client devices is configured to belong to a virtual group configured to be able to interact with other client devices belonging to the same group, and all of the groups are configured to belong to one virtual interaction room;
a dialogue control step including a new group generation control step configured to, when the client device and/or the server device detects a group generation request signal, which is generated in the client device, requesting the generation of a new group belonging to the dialogue room, generate a new group including the client device as a constituent element, and control the client devices constituting the new group to leave the group to which they previously belonged ;
the group generation request signal is configured to include a group generation proposal signal, generated in one client device, proposing the generation of a new group including the designation of another client device, and a group generation acceptance signal, generated in response to the group generation proposal signal, proposing the generation of a new group in the designated other client device;
An online interaction method, comprising:

Images