Patent Publication Number: US-2023154190-A1

Title: Display control system, display control method, and recording medium containing display control program

Description:
INCORPORATION BY REFERENCE 
     This application is based upon and claims the benefit of priority from the corresponding Japanese Patent Application No. 2021-186098 filed on Nov. 16, 2021, the entire contents of which are incorporated herein by reference. 
     BACKGROUND 
     The present disclosure relates to a display control system, a display control method, and a recording medium containing a display control program. 
     In recent years, a video meeting system (online meeting system) for holding a meeting in which voice, video images, files, and the like are transmitted/received at mutually separated places through a network, is used. For example, in the video meeting system, the face images of the participants of a meeting are displayed on each other&#39;s terminals (meeting terminals). In the conventional video meeting system, a technique has been proposed to switch between a captured image and a character image (avatar image) depending on the size of the display area and cause them to be displayed on the meeting terminal. 
     However, with the conventional technique, problems arise when character images are displayed in meetings where it is not appropriate to use character images, or when captured images are displayed in meetings where captured images are not desired. Thus, with the conventional technique, it is difficult to appropriately switch the displayed image in accordance with the content of the meeting. 
     SUMMARY 
     An object of the disclosure is to provide a display control system, a display control method, and a recording medium containing a display control program that can appropriately switch display images displayed on a meeting terminal in accordance with the content of a meeting. 
     A display control system according to an aspect of the disclosure causes an image to be displayed on a meeting terminal during a meeting in which a user participates, the image corresponding to the user, the system including a meeting acquisition processor that acquires meeting information related to the meeting; a video image acquisition processor that acquires video image information corresponding to a video image capturing the user participating in the meeting; a determination processor that determines an image type of the image to be displayed on the meeting terminal based on the meeting information acquired by the meeting acquisition processor; and an output processor that outputs an image corresponding to the video image information acquired by the video image acquisition processor and the image type determined by the determination processor, to the meeting terminal. 
     A display control method according to another aspect of the disclosure causes an image to be displayed on a meeting terminal during a meeting in which a user participates, the image corresponding to the user, the method executed by at least one processor acquiring meeting information related to the meeting; acquiring video image information corresponding to a video image capturing the user participating in the meeting; determining an image type of the image to be displayed on the meeting terminal based on the meeting information acquired by the step of acquiring meeting information; and outputting an image corresponding to the video image information acquired by the step of acquiring video image information and the image type determined by the step of determining, to the meeting terminal. 
     A recording medium according to another aspect of the disclosure contains a display control program that causes an image to be displayed on a meeting terminal during a meeting in which a user participates, the image corresponding to the user, the display control program causing at least one processor to execute: acquisition of meeting information related to the meeting; acquisition of video image information corresponding to a video image capturing the user participating in the meeting; determination of an image type of the image to be displayed on the meeting terminal based on the meeting information acquired by the acquisition of meeting information; and output of an image corresponding to the video image information acquired by the acquisition of video image information and the image type determined by the determination, to the meeting terminal. 
     The disclosure can provide a display control system, a display control method, and a recording medium containing a display control program that can appropriately switch display images displayed on a meeting terminal in accordance with the content of a meeting. 
     This Summary is provided to introduce a selection of concepts in a simplified form that is further described below in the Detailed Description with reference where appropriate to the accompanying drawings. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG.  1    is a schematic diagram illustrating the schematic configuration of a meeting system according to an embodiment of the disclosure. 
         FIG.  2    is a functional block diagram illustrating the configuration of a meeting system according to an embodiment of the disclosure. 
         FIG.  3    is a diagram illustrating an example of meeting information according to an embodiment of the disclosure. 
         FIG.  4    is a diagram illustrating an example of image type information according to an embodiment of the disclosure. 
         FIG.  5    is a diagram illustrating an example of a meeting application screen displayed on a user terminal according to an embodiment of the disclosure. 
         FIG.  6    is a flowchart for explaining an example of a procedure of display control processing of an example 1 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  7    is a flowchart for explaining an example of a procedure of display control processing of an example 2 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  8    is a flowchart for explaining an example of a procedure of display control processing of an example 3 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  9    is a flowchart for explaining an example of a procedure of display control processing of an example 4 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  10    is a flowchart for explaining an example of a procedure of display control processing of an example 5 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  11    is a flowchart for explaining an example of a procedure of display control processing of an example 6 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  12    is a flowchart for explaining an example of a procedure of display control processing of an example 7 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  13    is a flowchart for explaining an example of a procedure of display control processing of an example 8 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  14    is a flowchart for explaining an example of a procedure of display control processing of an example 9 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  15    is a flowchart for explaining an example of a procedure of display control processing of an example 10 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  16    is a flowchart for explaining an example of a procedure of display control processing of an example 11 that is executed in the meeting system according to an embodiment of the disclosure. 
         FIG.  17    is a flowchart for explaining an example of a procedure of display control processing of an example 12 that is executed in the meeting system according to an embodiment of the disclosure. 
     
    
    
     DETAILED DESCRIPTION 
     Embodiments of the disclosure will now be described with reference to the accompanying drawings. Note that the following embodiments are mere examples that embody the disclosure, and are not intended to limit the technical scope of the disclosure. 
     A display control system according to the disclosure can be applied, for example, to a video meeting (online meeting) attended by multiple users at different locations (meeting rooms, office seats, homes, etc.). A meeting system according to the present embodiment is an example of the display control system of the disclosure. The meeting system according to the present embodiment, user terminals used by users participating during a meeting are disposed in, for example, each meeting room. 
     Meeting System  100   
       FIG.  1    is a diagram illustrating the schematic configuration of the meeting system  100  according to an embodiment of the disclosure. The meeting system  100  includes user terminals  1 , camera devices  2  (see  FIG.  2   ), and a schedule server  3 . The meeting system  100  is a system that supports meetings attended by multiple users. The meeting system  100  causes images corresponding to the user to be displayed on a meeting terminal (e.g., a user terminal  1 ) during a meeting attended by the user. 
       FIG.  1    illustrates three different locations. Here is an example of a video meeting attended by users A, B, and C using user terminals  1  at different locations. Each user terminal  1  executes a meeting application installed in the user terminal and sends and receives camera images and audio to and from the other user terminals  1  to conduct video meeting with other user terminals  1 . At each location, a microphone-speaker device, a camera device, etc., are connected to the user terminal  1  to enable bidirectional communication of voice and camera images. The microphone-speaker device and the camera device may be built into the user terminal  1 . 
     The schedule server  3  manages meeting information D 1  related to meeting schedules (reservations). 
       FIG.  3    is a table illustrating an example of the meeting information D 1 . In the meeting information D 1 , meeting reservation information in which the meeting date, the meeting time, the meeting room ID, the meeting name, the subscriber IDs, the meeting URL, the participants, the meeting materials, and the like are associated with each other for each meeting is registered. The meeting room ID is identification information of a meeting room where a meeting is held. The subscriber ID is identification information that identifies a user who reserves a meeting. The meeting URL is access information (connection information) for connecting when a meeting is started. For example, the controller  11  accesses the meeting URL so as to start a meeting application (a general-purpose meeting application) corresponding to the meeting URL and to connect to a destination ID (meeting ID). The meeting materials are the materials used for the meeting. For example, when a meeting is determined to be held, a subscriber operates their own PC (e.g., the user terminal  1 ) to execute a reservation operation of inputting meeting information including each of the aforementioned pieces of information. The controller  11  accesses and registers the meeting reservation information in response to the reservation operation by the subscriber to the meeting information D 1  on the schedule server  3 . 
     The schedule server  3  manages the meeting information D 1  for each user. For example, the schedule server  3  associates the meeting information D 1  with a user ID (e.g., login ID) and registers the meeting information D 1 . 
     In addition to the meeting information D 1 , the schedule server  3  may also manage action schedule information, attendance information, and the like for each user. The above-mentioned action schedule information includes information on planned outings, etc. The attendance information includes information such as working hours, work location (in-house, home, etc.), and vacation schedule. 
     A known server (e.g., cloud server) that provides scheduling services can be used as the schedule server  3  in the present embodiment. 
     User Terminal  1   
     As illustrated in  FIG.  2   , the user terminal  1  includes a controller  11 , a storage  12 , an operation display  13 , a communicator  14 , and the like. The user terminal  1  is an information processing device such as a personal computer (PC), a smartphone, a tablet terminal. The user terminal  1  is an example of a meeting terminal of the present disclosure. Each user terminal  1  has the same configuration. 
     The communicator  14  is a communicator which connects the user terminal  1  to a network N 1  in a wired or wireless manner and executes data communication according to a predetermined communication protocol with other devices, such as other user terminals  1 , other camera devices  2 , the schedule server  3 , and so on via the network N 1 . The user terminal  1  may be connected to meeting equipment (a display, a microphone-speaker device, and the like) via the communicator  14  by a wired LAN or a wireless LAN. 
     The operation display  13  is a user interface including: a display, such as a liquid crystal display and an organic EL display, which displays various kinds of information; and an operation acceptor, such as a mouse, a keyboard, and a touch panel, which receives an operation. The operation display  13  accepts, for example, operations of the user of the user terminal  1 . 
     The storage  12  is a non-volatile storage including a hard disk drive (HDD), a solid state drive (SSD), and a flash memory that stores various types of information. The storage  12  stores a control program, such as a display control program for causing the controller  11  to execute a display control process (refer to  FIG.  6   ), which will be described below. For example, the display control program is temporarily recorded in a computer-readable recording medium such as a CD or a DVD, read by a reading device (not shown) such as a CD drive or a DVD drive included in the user terminal  1 , and stored in the storage  12 . Note that the display control program may be distributed from a cloud server and stored in the storage  12 . 
     The storage  12  stores image type information D 2 , which is information on the image type of the image to be displayed on user terminal  1 .  FIG.  4    illustrates an example of the image type information D 2 . In the image type information D 2 , the output image type according to conditions is registered. The conditions include conditions related to each piece of information contained in the meeting information D 1  (see  FIG.  3   ), the type of meeting application used for the meeting, the type of microphone-speaker device used for the meeting, the communication means for connecting to the meeting (e.g., Wi-Fi). The output image includes a captured image, which is a video image of the user captured by the camera device  2 , and a processed image, which is a processed video image of the user captured by the camera device  2 . The processed image includes a character image (also referred to as an avatar image) an illustration image, a digital human image, and a virtual background image. For example, images  1  to  5  in  FIG.  4    are each an avatar image, an illustration image, a digital human image, a virtual background image, or a 3D avatar image. 
     For example, the controller  11  of the user terminal  1 A of a user A refers to the image type information D 2  to determine type of image that satisfies the conditions related to the meeting information D 1  and is to be displayed on user terminal  1 B of a user B. Specific examples of the method of determining the image type are described below. 
     The controller  11  includes control devices, such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various types of arithmetic processing. The ROM stores in advance control programs such as a BIOS and an OS for causing the CPU to execute various types of processing. The RAM stores various types of information and is used as a temporary storage memory (work area) for the various types of processing executed by the CPU. The controller  11  then controls the user terminal  1  by causing the CPU to execute various types of control programs stored in advance in the ROM or the storage  12 . 
     Specifically, the controller  11  includes various types of processors, such as a meeting acquisition processor  111 , a video image acquisition processor  112 , a determination processor  113 , a generation processor  114 , and an output processor  115 . The controller  11  functions as the various types of processors by executing the various types of processing according to the display control program. Some or all of the processors included in the controller  11  may be configured by an electronic circuit. The display control program may cause a plurality of processor devices to function as the various processors. 
     The meeting acquisition processor  111  acquires the meeting information D 1  (see  FIG.  3   ). For example, when the user A performs a login operation at a user terminal  1 A, the meeting acquisition processor  111  accesses the schedule server  3  to acquire the meeting information D 1  associated with the user ID of the user A. 
     The video image acquisition processor  112  acquires video image information corresponding to the video image capturing the users participating in the meeting. Here, each user terminal  1  is individually connected to a camera device  2 . For example, a camera device  2 A is connected to the user terminal  1 A, and a camera device  2 B is connected to a user terminal  1 B (see  FIG.  2   ). The camera device  2 A captures the user A using the user terminal  1 A, and the camera device  2 B captures the user B using the user terminal  1 B. Each camera device  2  may be built into the corresponding user terminal  1 . 
     The camera device  2  may be a device that outputs the captured video image (captured image) to the user terminal  1 , or it may be a device (e.g., a smartphone) that extracts the feature values of the user&#39;s face on the basis of the captured video image and outputs the extracted feature value data to the user terminal  1 . A single user terminal  1  may be connected to multiple camera devices  2 . In such a case, the captured image and the feature value data may be input to the user terminal  1 . 
     The video image acquisition processor  112  acquires video image information (captured images and feature value data) from the camera device  2  at the start of a meeting, during a meeting, etc. That is, the video image acquisition processor  112  acquires captured image that is a video image of the user captured with the camera device  2  or feature value data extracted from the video image of the user captured by the camera device  2 . 
     The determination processor  113  determines the image type of the image to be displayed on the other user terminals  1  on the basis of the meeting information D 1  acquired by the meeting acquisition processor  111 . Specifically, the determination processor  113  refers to the image type information D 2  (see  FIG.  4   ) to determine the image type that satisfies the conditions related to the meeting information D 1  (see  FIG.  3   ). For example, the determination processor  113  determines the image type on the basis of at least one of the following information contained in the meeting information D 1 : the meeting time, the meeting participants, the content of the meeting, the importance of the meeting, and the location of the users participating in the meeting. 
     The determination processor  113  determines the image type on the basis of at least one of the following information: the type of meeting application used for the meeting, the type of microphone-speaker device used for the meeting, and the communicator for connecting to the meeting. 
     The determination processor  113  determines, as the image type, a captured image that is a processed video image of the user captured with the camera device  2  or a processed image that is a processed image of a user captured with the camera device  2 , on the basis of the meeting information D 1 . The processed image includes at least one of a character image, an illustration image, a digital human image, and a virtual background image. 
     For example, if the meeting attended by the user A is a meeting attended by members outside the company, the determination processor  113  determines “captured image” as the image type. For example, if the meeting attended by the user A is a meeting held outside of working hours, the determination processor  113  determines “processed image (e.g., avatar image)” as the image type. 
     The generation processor  114  generates the processed image from the video image information acquired by the video image acquisition processor  112 . Specifically, the generation processor  114  generates the processed image in accordance with the image type determined by the determination processor  113  for the video image information acquired by the video image acquisition processor  112 . For example, the generation processor  114  generates a character image (avatar image), an illustration image, a digital human image, a virtual background image, etc., on the basis of the image captured by the camera device  2 . The method of generating the processed image from the captured image can adopt known techniques. 
     The output processor  115  outputs the video image information acquired by the video image acquisition processor  112  and an image corresponding to the image type determined by the determination processor  113  to another user terminal  1 . For example, if the meeting attended by the user A is a meeting attended by members outside the company, the output processor  115  of the user terminal  1 A outputs a captured image of the user A to the user terminal  1 B. In such a case, user terminal  1 B causes the image capturing the user A to be displayed on its own operation display  13 . 
     For example, if the meeting attended by the user A is a meeting held outside of working hours, the output processor  115  of the user terminal  1 A outputs an avatar image of the user A to the user terminal  1 B. In such a case, user terminal  1 B causes the avatar image of the user A to be displayed on its own operation display  13 . 
     The user terminals  1 A and  1 B both execute the same process to cause an image Pa of the user A and an image Pb of the user B to be displayed on the user terminals  1 A and  1 B, respectively, as illustrated in the meeting application screen in  FIG.  5   . An icon image Sc of the login user may be displayed on the meeting application screen in  FIG.  5   . The icon image Sc may alternatively be an image representing the user&#39;s status (e.g., on vacation, commuting, working remotely, etc.). 
     The controller  11  performs a meeting process in addition to the above-described processes. Specifically, the controller  11  starts the meeting application and connects to another user terminal  1 . Once each user terminal  1  is connected, the controller  11  starts the meeting by sending and receiving audio, video image, files, and the like. The controller  11  causes the meeting application screen to be displayed (see  FIG.  5   ). 
     The controller  11  accepts various operations (meeting start operation, meeting end operation, screen sharing operation, etc.) by the user on the meeting application screen. 
     Display Control Process 
     An example of a procedure of the display control process executed by the meeting system  100  will now be described below with reference to  FIGS.  6  to  17   . Each of the flowcharts in  FIGS.  6  to  17    illustrates a specific example of the display control process. The display control process executed by the user terminal  1 A used by the user A will now be described. Specifically, the controller  11  of the user terminal  1 A determines the type of image to be displayed on the user terminal  1 B on the basis of specific information such as meeting information, and executes a process of outputting an image of the determined type to the user terminal  1 B. 
     The disclosure can be regarded as a disclosure of a display control method (an example of a display control method of the disclosure) in which one or more steps included in the display control process are executed. The one or more steps included in the display control process described herein may be omitted as appropriate. The order of execution of each step in the display control process may be different to the extent that the same effect is produced. 
     In the example described here, the controller  11  of the user terminal  1  executes each step in the display control process; however, according to another embodiment, one or more processors may decentrally execute each step in the display control process. 
     Example 1 
       FIG.  6    is a flowchart corresponding to the display control process according to Example 1. 
     In step S 11 , the controller  11  acquires the meeting information and video image information. Specifically, when the user A performs the login operation, the controller  11  acquires the meeting information D 1  corresponding to the user A (see  FIG.  3   ) from the schedule server  3 . When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 12 , the controller  11  determines whether or not the current time is within the working hours of the user A. The working hours may be working hours specific to the user A or shared working hours defined within the company to which the user A belongs. If the current time is within the working hours of the user A (S 12 : Yes), the controller  11  causes the process to proceed to step S 13 . If the current time is not within the working hours of the user A (S 12 : No), the controller  11  causes the process to proceed to step S 121 . 
     In step S 121 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image (character image).” After step S 121 , the controller  11  causes the process to proceed to step S 110 . 
     In step S 13 , the controller  11  determines whether or not the current time is within the meeting time of the meeting attended by the user A. If the current time is within the meeting time of the user A (S 13 : Yes), the controller  11  causes the process to proceed to step S 14 . If the current time is not within the meeting time of the user A (S 13 : No), the controller  11  causes the process to proceed to step S 131 . 
     In step S 131 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “illustration image.” After step S 131 , the controller  11  causes the process to proceed to step S 110 . 
     In step S 14 , the controller  11  determines whether or not the meeting participants are only members of the company. If the meeting participants only in-house members (S 14 : Yes), the controller  11  causes the process to proceed to step S 141 . If the meeting participants are not only in-house members, i.e., the meeting participants include members outside the company (S 14 : No), the controller  11  causes the process to proceed to step S 15 . 
     In step S 141 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “digital human image.” After step S 141 , the controller  11  causes the process to proceed to step S 110 . 
     In step S 15 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After step S 15 , the controller  11  causes the process to proceed to step S 16 . 
     In step S 110 , the controller  11  generates an image of the determined type. Here, the controller  11  generates an avatar image, an illustration image, or a digital human image based on the captured image. After step S 110 , the controller  11  causes the process to proceed to step S 16 . 
     In step S 16 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, an avatar image, an illustration image, or a digital human image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the meeting application screen (see  FIG.  5   ). 
     Example 2 
       FIG.  7    is a flowchart corresponding to the display control process according to Example 2. 
     In step S 21 , the controller  11  acquires the meeting information and video image information. Specifically, when the user A performs the login operation, the controller  11  acquires the meeting information D 1  corresponding to the user A (see  FIG.  3   ) from the schedule server  3 . When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 22 , the controller  11  determines whether or not the term “external” is included in the meeting name (title). If the meeting name includes the term “external” (S 22 : Yes), the controller  11  causes the process to proceed to step S 221 . If the meeting name does not include the term “external” (S 22 : No), the controller  11  causes the process to proceed to step S 23 . 
     In step S 221 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After step S 221 , the controller  11  causes the process to proceed to step S 27 . 
     In step S 23 , the controller  11  determines whether or not an external email address is included in the meeting information D 1 . If the meeting information D 1  includes an external email address (S 23 : Yes), the controller  11  causes the process to proceed to step S 221 . If the meeting information D 1  does not include an external email address (S 23 : No), the controller  11  causes the process to proceed to step S 24 . 
     In step S 24 , the controller  11  determines whether or not a meeting flag is set to “important.” If the meeting flag is set to “important” (S 24 : Yes), the controller  11  causes the process to proceed to step S 241 . If the meeting flag is not set to “important” (S 24 : No), the controller  11  causes the process to proceed to step S 25 . 
     In step S 241 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “virtual background image.” After step S 241 , the controller  11  causes the process to proceed to step S 26 . 
     In step S 25 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After step S 25 , the controller  11  causes the process to proceed to step S 26 . 
     In step S 26 , the controller  11  generates an image of the determined type. Here, the controller  11  generates a virtual background image or an avatar image based on the captured image. After step S 26 , the controller  11  causes the process to proceed to step S 27 . 
     In step S 27 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, a virtual background image, or an avatar image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the meeting application screen (see  FIG.  5   ). 
     Example 3 
       FIG.  8    is a flowchart corresponding to the display control process according to Example 3. 
     In step S 31 , the controller  11  acquires the meeting information and video image information. Specifically, when the user A performs the login operation, the controller  11  acquires the meeting information D 1  corresponding to the user A (see  FIG.  3   ) from the schedule server  3 . When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 32 , the controller  11  determines whether or not address information is included in the meeting information D 1 . If the meeting information D 1  includes address information (S 32 : Yes), the controller  11  causes the process to proceed to step S 321 . If the meeting information D 1  does not include address information (S 32 : No), the controller  11  causes the process to proceed to step S 33 . 
     In step S 321 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After step S 321 , the controller  11  causes the process to proceed to step S 37 . 
     In step S 33 , the controller  11  determines whether or not the location corresponding to the address information is a meeting room. If the location corresponding to the address information is a meeting room (S 33 : Yes), the controller  11  causes the process to proceed to step S 321 . If the location corresponding to the address information is not a meeting room (S 33 : No), the controller  11  causes the process to proceed to step S 34 . 
     In step S 34 , the controller  11  determines whether or not the location corresponding to the address information is the user&#39;s seat. If the location corresponding to the address information is the user&#39;s seat (S 34 : Yes), the controller  11  causes the process to proceed to step S 341 . If the location corresponding to the address information is not the user&#39;s seat (S 34 : No), the controller  11  causes the process to proceed to step S 35 . 
     In step S 341 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “digital human image.” After step S 341 , the controller  11  causes the process to proceed to step S 36 . 
     In step S 35 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After step S 35 , the controller  11  causes the process to proceed to step S 36 . 
     In step S 36 , the controller  11  generates an image of the determined type. Here, the controller  11  generates a digital human image or an avatar image based on the captured image. After step S 36 , the controller  11  causes the process to proceed to step S 37 . 
     In step S 37 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, a digital human image, or an avatar image to the user terminal  1 B. 
     Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the meeting application screen (see  FIG.  5   ). 
     Example 4 
       FIG.  9    is a flowchart corresponding to the display control process according to Example 4. 
     In step S 41 , the controller  11  acquires the meeting information and video image information. Specifically, when the user A performs the login operation, the controller  11  acquires the meeting information D 1  corresponding to the user A (see  FIG.  3   ) from the schedule server  3 . When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 42 , the controller  11  determines whether or not the meeting to be started is a meeting pre-registered to the meeting information D 1 . If the meeting to be stated is a meeting pre-registered to the meeting information D 1  (S 42 : Yes), the controller  11  causes the process to proceed to step S 421 . If the meeting to be stated is not a meeting pre-registered to the meeting information D 1  (S 42 : No), the controller  11  causes the process to proceed to step S 43 . 
     In step S 421 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After step S 421 , the controller  11  causes the process to proceed to step S 45 . 
     In step S 43 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “virtual background image.” After step S 43 , the controller  11  causes the process to proceed to step S 44 . 
     In step S 44 , the controller  11  generates an image of the determined type. Here, the controller  11  generates a virtual background image based on the captured image. After step S 44 , the controller  11  causes the process to proceed to step S 45 . 
     In step S 45 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image or a virtual background image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the meeting application screen (see  FIG.  5   ). 
     Example 5 
       FIG.  10    is a flowchart corresponding to the display control process according to Example 5. 
     In step S 51 , the controller  11  acquires the meeting information and video image information. Specifically, when the user A performs the login operation, the controller  11  acquires the meeting information D 1  corresponding to the user A (see  FIG.  3   ) from the schedule server  3 . When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 52 , the controller  11  determines whether or not the application used for video meeting is an application for sales negotiations. If the application used for video meeting is an application for sales negotiations (S 52 : Yes), the controller  11  causes the process to proceed to step S 521 . If the application used for video meeting is not an application for sales negotiations (S 52 : No), the controller  11  causes the process to proceed to step S 53 . 
     In step S 521 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After step S 521 , the controller  11  causes the process to proceed to step S 56 . 
     In step S 53 , the controller  11  determines whether or not the application used for video meeting is an application for seminars. If the application used for video meeting is an application for seminars (S 53 : Yes), the controller  11  causes the process to proceed to step S 531 . If the application used for video meeting is not an application for seminars (S 53 : No), the controller  11  causes the process to proceed to step S 54 . 
     In step S 531 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “virtual background image.” After step S 531 , the controller  11  causes the process to proceed to step S 510 . 
     In step S 54 , the controller  11  determines whether or not the application used for video meeting is an application for meetings. If the application used for video meeting is an application for meetings (S 54 : Yes), the controller  11  causes the process to proceed to step S 541 . If the application used for video meeting is not an application for meetings (S 54 : No), the controller  11  causes the process to proceed to step S 55 . 
     In step S 541 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After step S 541 , the controller  11  causes the process to proceed to step S 510 . 
     In step S 55 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 55 , the controller  11  causes the process to proceed to step S 56 . 
     In step S 510 , the controller  11  generates an image of the determined type. Here, the controller  11  generates a virtual background image or an avatar image based on the captured image. After Step S 510 , the controller  11  causes the process to proceed to step S 56 . 
     In step S 56 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, a virtual background image, or an avatar image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the application screen used for the video meeting (see  FIG.  5   ). 
     Example 6 
       FIG.  11    is a flowchart corresponding to the display control process according to Example 6. 
     In step S 61 , the controller  11  acquires information on the microphone-speaker device connected to the user terminal  1 A. When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 62 , the controller  11  determines whether or not the microphone-speaker device is for a meeting room. If the microphone-speaker device is for a meeting room (S 62 : Yes), the controller  11  causes the process to proceed to step S 621 . If the microphone-speaker device is not for a meeting room (S 62 : No), the controller  11  causes the process to proceed to step S 63 . 
     In step S 621 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 621 , the controller  11  causes the process to proceed to step S 67 . 
     In step S 63 , the controller  11  determines whether or not the microphone-speaker device is for personal use. If the microphone-speaker device is for personal use (S 63 : Yes), the controller  11  causes the process to proceed to step S 631 . If the microphone-speaker device is not for personal use (S 63 : No), the controller  11  causes the process to proceed to step S 64 . 
     In step S 631 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “virtual background image.” After Step S 631 , the controller  11  causes the process to proceed to step S 66 . 
     In step S 64 , the controller  11  determines whether or not the microphone-speaker device is a headset device. If the microphone-speaker device is a headset device (S 64 : Yes), the controller  11  causes the process to proceed to step S 641 . If the microphone-speaker device is not a headset device (S 64 : No), the controller  11  causes the process to proceed to step S 65 . 
     In step S 641 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “digital human image.” After Step S 641 , the controller  11  causes the process to proceed to step S 66 . 
     In step S 65 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After Step S 65 , the controller  11  causes the process to proceed to step S 66 . 
     In step S 66 , the controller  11  generates an image of the determined type. Here, the controller  11  generates a virtual background image, a digital human image, or an avatar image based on the captured image. After Step S 66 , the controller  11  causes the process to proceed to step S 67 . 
     In step S 67 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, an avatar image, a virtual background image, or a digital human image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the meeting application screen (see  FIG.  5   ). 
     Example 7 
       FIG.  12    is a flowchart corresponding to the display control process according to Example 7. 
     In step S 71 , the controller  11  acquires Wi-Fi connection destination information and video image information. Specifically, when the user A performs the login operation, the controller  11  acquires information on the Wi-Fi connection destination (home, in-house, facility, etc.). When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 72 , the controller  11  determines whether or not the Wi-Fi connection destination is one&#39;s home. If the Wi-Fi connection destination is one&#39;s home (S 72 : Yes), the controller  11  causes the process to proceed to step S 721 . If the Wi-Fi connection destination is not one&#39;s home (S 72 : No), the controller  11  causes the process to proceed to step S 73 . 
     In step S 721 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After Step S 721 , the controller  11  causes the process to proceed to step S 710 . 
     In step S 73 , the controller  11  determines whether or not the Wi-Fi connection destination is in-house. If the Wi-Fi connection destination is in-house (S 73 : Yes), the controller  11  causes the process to proceed to step S 731 . If the Wi-Fi connection destination is not in-house (S 73 : No), the controller  11  causes the process to proceed to step S 74 . 
     In step S 731 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “virtual background image.” After Step S 731 , the controller  11  causes the process to proceed to step S 710 . 
     In step S 74 , the controller  11  determines whether or not the Wi-Fi connection destination is a facility (hotel, cafe, etc.). If the Wi-Fi connection destination is a facility (S 74 : Yes), the controller  11  causes the process to proceed to step S 741 . If the Wi-Fi connection destination is not a facility (S 74 : No), the controller  11  proceeds to step S 75 . 
     In step S 741 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “digital human image.” After Step S 741 , the controller  11  causes the process to proceed to step S 710 . 
     In step S 75 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 75 , the controller  11  causes the process to proceed to step S 76 . 
     In step S 710 , the controller  11  generates an image of the determined type. Here, the controller  11  generates an avatar image, a virtual background image, or a digital human image based on the captured image. After Step S 710 , the controller  11  causes the process to proceed to step S 76 . 
     In step S 76 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, an avatar image, a virtual background image, or a digital human image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the application screen used for the video meeting (see  FIG.  5   ). 
     Example 8 
       FIG.  13    is a flowchart corresponding to the display control process according to Example 8. 
     In step S 81 , the controller  11  acquires status icon information and video image information. Specifically, when the user A performs the login operation, the controller  11  acquires information on an icon image Sc representing the status (see  FIG.  5   ). When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 82 , the controller  11  determines whether or not the status icon indicates that the user is on vacation. If the status icon indicates that the user is on vacation (S 82 : Yes), the controller  11  causes the process to proceed to step S 821 . If the status icon does not indicate that the user is on vacation (S 82 : No), the controller  11  causes the process to proceed to step S 83 . 
     In step S 821 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After Step S 821 , the controller  11  causes the process to proceed to step S 810 . 
     In step S 83 , the controller  11  determines whether or not the status icon indicates that the user is commuting. If the status icon indicates that the user is commuting (S 83 : Yes), the controller  11  causes the process to proceed to step S 831 . If the status icon does not indicate that the user is commuting (S 83 : No), the controller  11  causes the process to proceed to step S 84 . 
     In step S 831 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “virtual background image.” After Step S 831 , the controller  11  causes the process to proceed to step S 810 . 
     In step S 84 , the controller  11  determines whether or not the status icon indicates that the user is working remotely. If the status icon indicates that the user is working remotely (S 84 : Yes), the controller  11  causes the process to proceed to step S 841 . If the status icon does not indicate that the user is working remotely (S 84 : No), the controller  11  causes the process to proceed to step S 85 . 
     In step S 841 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “digital human image.” After Step S 841 , the controller  11  causes the process to proceed to step S 810 . 
     In step S 85 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 85 , the controller  11  causes the process to proceed to step S 86 . 
     In step S 810 , the controller  11  generates an image of the determined type. Here, the controller  11  generates an avatar image, a virtual background image, or a digital human image based on the captured image. After Step S 810 , the controller  11  causes the process to proceed to step S 86 . 
     In step S 86 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, an avatar image, a virtual background image, or a digital human image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the application screen used for the video meeting (see  FIG.  5   ). 
     Example 9 
       FIG.  14    is a flowchart corresponding to the display control process according to Example 9. 
     In step S 91 , the controller  11  acquires the status of the meeting support application and video image information. When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     Here, the meeting support application is an application that supports video meeting executed by a general-purpose meeting application. The meeting support application manages the progress of the meeting and accepts user operations. In the meeting support application, the user can set the operation mode to a home mode or an office mode. For example, the user can set the home mode for private meetings and the office mode for work-related meetings. 
     In step S 92 , the controller  11  determines whether or not the operation mode is set to the home mode. If the operation mode is set to the home mode (S 92 : Yes), the controller  11  causes the process to proceed to step S 921 . If the operation mode is set to the office mode (S 92 : No), the controller  11  causes the process to proceed to step S 93 . 
     In step S 921 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After Step S 921 , the controller  11  causes the process to proceed to step S 922 . 
     In step S 922 , the controller  11  generates an image of the determined type. Here, the controller  11  generates an avatar image based on the captured image. After Step S 922 , the controller  11  causes the process to proceed to step S 94 . 
     In step S 93 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 93 , the controller  11  causes the process to proceed to step S 94 . 
     In step S 94 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image or an avatar image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the application screen used for the video meeting (see  FIG.  5   ). 
     Example 10 
       FIG.  15    is a flowchart corresponding to the display control process according to Example 10. 
     In step S 101 , the controller  11  acquires NFC communication history and video image information. Specifically, the user A taps the NFC at the start of the meeting. When the user A taps the NFC, the communication history is stored in the storage  12 . When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In Step S 102 , the controller  11  determines whether or not the NFC has been tapped immediately before the start of the meeting. If the NFC has been tapped immediately before the start of the meeting (S 102 : Yes), the controller  11  causes the process to proceed to step S 106 . If the NFC has not been tapped immediately before the start of the meeting (S 102 : No), the controller  11  causes the process to proceed to step S 103 . 
     In step S 106 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 106 , the controller  11  causes the process to proceed to step S 105 . 
     In step S 103 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After Step S 103 , the controller  11  causes the process to proceed to step S 104 . 
     In step S 104 , the controller  11  generates an image of the determined type. Here, the controller  11  generates an avatar image based on the captured image. After Step S 104 , the controller  11  causes the process to proceed to step S 105 . 
     In step S 105 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image or an avatar image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the application screen used for the video meeting (see  FIG.  5   ). 
     Example 11 
       FIG.  16    is a flowchart corresponding to the display control process according to Example 11. 
     In step S 111 , if the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. 
     In step S 112 , the controller  11  determines whether or not the user A in the captured image is holding a small object. If the user A in the captured image is holding a small object (S 112 : Yes), the controller  11  causes the process to proceed to step S 212 . If the user A in the captured image is not holding a small object (S 112 : No), the controller  11  causes the process to proceed to step S 113 . 
     In step S 212 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 212 , the controller  11  causes the process to proceed to step S 117 . 
     In step S 113 , the controller  11  determines whether or not the user A in the captured image is wearing a business suit. If the user A in the captured image is wearing a business suit (S 113 : Yes), the controller  11  causes the process to proceed to step S 131 . If the user A in the captured image is not wearing a business suit (S 113 : No), the controller  11  causes the process to proceed to step S 114 . 
     In step S 131 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “virtual background image.” After Step S 131 , the controller  11  causes the process to proceed to step S 116 . 
     In step S 114 , the controller  11  determines whether or not the user A in the captured image is wearing a motion capture suit. If the user A in the captured image is wearing a motion capture suit (S 114 : Yes), the controller  11  causes the process to proceed to step S 141 . If the user Ain the captured image is not wearing a motion capture suit (S 114 : No), the controller  11  causes the process to proceed to step S 115 . 
     In step S 141 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “3D avatar image.” After Step S 141 , the controller  11  causes the process to proceed to step S 116 . 
     In step S 115 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After Step S 115 , the controller  11  causes the process to proceed to step S 116 . 
     In step S 116 , the controller  11  generates an image of the determined type. Here, the controller  11  generates a virtual background image, a 3D avatar image, or an avatar image based on the captured image. After Step S 116 , the controller  11  causes the process to proceed to step S 117 . 
     In step S 117 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, a virtual background image, a 3D avatar image, or an avatar image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the meeting application screen (see  FIG.  5   ). 
     Example 12 
       FIG.  17    is a flowchart corresponding to the display control process according to Example 12. 
     In step S 121 , the controller  11  acquires information on an input device connected to the user terminal  1 A. When the user A performs the login operation, the controller  11  acquires the video image information (e.g., captured images) from the camera device  2 A. The input devices include, for example, a camera device  2 . 
     In step S 122 , the controller  11  determines whether or not a camera device  2  is connected. If a camera device  2  is connected (S 122 : Yes), the controller  11  proceeds to step S 221 . If a camera device  2  is not connected (S 122 : No), the controller  11  proceeds to step S 123 . 
     In step S 221 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “captured image.” After Step S 221 , the controller  11  causes the process to proceed to step S 126 . 
     In step S 123 , the controller  11  determines whether or not a device (camera device  2 ) capable of acquiring facial feature values of the user A is connected. The device is, for example, a smartphone. If a device capable of acquiring facial feature values of the user A is connected (S 123 : Yes), the controller  11  proceeds to step S 223 . If a device (camera device  2 ) capable of acquiring facial feature values of the user A is not connected (S 123 : No), the controller  11  proceeds to step S 124 . 
     In step S 223 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is a “digital human image.” After Step S 223 , the controller  11  causes the process to proceed to step S 125 . 
     In step S 124 , the controller  11  determines that the type of the image to be displayed on the user terminal  1 B is an “avatar image.” After Step S 124 , the controller  11  causes the process to proceed to step S 125 . 
     In step S 125 , the controller  11  generates an image of the determined type. Here, the controller  11  acquires the feature value data from the camera device  2  and generates a digital human image based on the feature value data. Here, the controller  11  generates an avatar image based on the captured image. After Step S 125 , the controller  11  causes the process to proceed to step S 126 . 
     In step S 126 , the controller  11  outputs the image of the determined type to the user terminal  1 B. Here, the controller  11  outputs a captured image, a digital human image, or an avatar image to the user terminal  1 B. Upon acquiring the image from user terminal  1 A, the user terminal  1 B causes the acquired image to be displayed on the meeting application screen (see  FIG.  5   ). 
     As described above, the controller  11  determines the type of the image to be displayed on the meeting terminal (user terminal  1 ) on the basis of predetermined conditions (for example, conditions  1  to  5  in  FIG.  4   ) and outputs an image (captured image, processed image, etc.) corresponding to the determined type of image to the meeting terminal. Each of the conditions is a condition corresponding to each of the determination processes included in Examples 1 to 12. 
     According to the above configuration, for example, user-captured images (real video images) can be displayed in meetings where it is not appropriate to use character images, and processed images such as character images can be displayed in private meetings. Thus, it is possible to appropriately switch the image displayed on the meeting terminal in accordance with the content of the meeting. 
     The disclosure is not limited to the above-described embodiments. As another embodiment, the meeting system  100  may include a server connected to each user terminal  1  via a network N 1 . The server may comprise, for example, a cloud server. The server may have the functions of the controller  11  of the user terminal  1  described above. Specifically, the server acquires the meeting information D 1  related to a meeting, acquires video image information corresponding to the video images of the users participating in the meeting, determines the type of image to be displayed on the meeting terminal on the basis of the acquired meeting information, and outputs an image corresponding to the acquired video image information and the determined image type to the meeting terminal. That is, the server may include processors (see  FIG.  2   ) such as a meeting acquisition processor  111 , a video image acquisition processor  112 , a determination processor  113 , a generation processor  114 , and an output processor  115 . 
     The server may also store the meeting information D 1  (see  FIG.  3   ) and the image type information D 2  (see  FIG.  4   ). 
     The server may also store a meeting application. In such a case, each user terminal  1  accesses the server and executes a browser process to run the meeting application. 
     As described above, the display control system of the disclosure may include a single user terminal  1 , a single server, or a combination of a user terminal  1  and the server. 
     It is to be understood that the embodiments herein are illustrative and not restrictive, since the scope of the disclosure is defined by the appended claims rather than by the description preceding them, and all changes that fall within metes and bounds of the claims, or equivalence of such metes and bounds thereof are therefore intended to be embraced by the claims.