Systems and servers

Abstract

To provide a system and a server which are convenient and generally useful for the purpose of integrating and centrally managing a plurality of message applications.SOLUTION: The present system comprises: operation unit display means which, when there is a plurality of message applications linked to the system by linkage management means, displays on a user terminal an operation part (main function display button 140) capable of accepting operation to display on a user terminal a specific screen (main function screen 18) capable of collectively displaying information (thread information icon 183) that indicates a specific unit (thread) pertaining to the exchanging of various messages of the plurality of message applications; and specific screen display means for causing the specific screen to be displayed on the user terminal due to that said operation is performed when the specific screen is not displayed on the user terminal.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a system and a server for integrating and centrally managing a plurality of message applications. [Background technology]

[0002] Recently, various communication tools, such as email, chat, and messengers, have been developed. Furthermore, various types of applications (messaging applications) have been developed for each communication tool. However, when a user uses a messaging application with another user, the messaging application may need to match the type of application used by the other user. As a result, a user may need to use different messaging applications depending on the type of communication.

[0003] When using a messaging application on a communication device such as a PC or smartphone, an icon corresponding to the messaging application is displayed on the display screen of the communication device, and by operating that icon, the messaging application corresponding to that icon is launched and becomes available for use. Therefore, when switching messaging applications, it is necessary to close the open screen once and then operate the icon of the next messaging application to be used again. While this operation is not too troublesome if it is performed only once, it becomes very time-consuming if it is performed multiple times. Furthermore, when sending image data received from one person to another, if the person uses a different messaging application, the operation becomes troublesome.

[0004] Conventionally, a centralized message management system has been developed that centrally manages multiple types of message applications (see Patent Document 1). In the centralized message management system described in Patent Document 1, when the system is accessed, a screen first displays multiple icons associated with keywords, and when an icon is selected, the screen switches to the screen associated with that icon. On the screen, email messages or chat messages containing the keyword associated with the selected icon are displayed in a list by subject. Also, this screen displays a speech bubble button, and when this button is selected, a new chat message display screen is created within the screen. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent No. 5960277 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the message unified management system described in Patent Document 1 is primarily intended for use by a company or organization, and the emails and chats that are unified managed by the system are fixed.

[0007] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a system and a server for integrating and centrally managing multiple message applications that are highly convenient and versatile. [Means for solving the problem]

[0008] One aspect of the present invention made to solve the above problem is: A system capable of centrally managing multiple types of message applications, a linkage management means for linking the message application to the system in response to a linkage request from a user terminal to the message application; an operation unit display means for displaying, on the user terminal, an operation unit capable of accepting an operation to display a specific screen on the user terminal that can collectively display information indicating specific units related to message exchanges of each of the plurality of message applications, when there are a plurality of message applications that are linked to the system by the link management means, on the condition that the user terminal is logged in; The present invention is characterized in that it comprises a specific screen display means for displaying the specific screen on the user terminal when the operation unit is operated while the specific screen is not being displayed on the user terminal.

[0009] In addition, one aspect of the present invention made to solve the above problem is: A server capable of centrally managing multiple types of message applications, In response to a request for linking a message application from a user terminal, linking an external device related to the message application with the server; When there are a plurality of external devices related to message applications linked to the server, an operation unit capable of receiving an operation for displaying a specific screen on the user terminal that can collectively display information indicating specific units related to message exchanges of each of the plurality of message applications is displayed on the user terminal; When the specific screen is not displayed on the user terminal, the specific screen is displayed on the user terminal by operating the operation unit. [Effects of the Invention]

[0010] The system and server for integrating and centrally managing a plurality of message applications according to the present invention can enhance convenience and versatility. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a schematic diagram illustrating the overall configuration of a system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing the main functional configuration of a management server that constitutes the system. [Figure 3] 2 is a diagram schematically illustrating a table registered in a database provided in a management server that constitutes the system. FIG. [Figure 4] FIG. 10 is a diagram illustrating an example of the configuration of a user information table. [Figure 5] 10A is a diagram showing a specific example of a window displayed when starting to use an application, FIG. 10B is a diagram showing a specific example of a window displayed when registering a user, and FIG. 10C is a diagram showing a specific example of a top window. [Figure 6] 10A is a diagram showing a specific example of an application cooperation window related to application E, and FIG. 10B is a diagram showing a specific example of an application use window when cooperation with application E is being performed. [Figure 7] 10A is a diagram showing a specific example of a top window when linked with application E, and FIG. 10B is a diagram showing a specific example of a window when linked with application C. FIG. [Figure 8] 13 is a diagram illustrating a specific example of a window displayed when an application is used in cooperation with application E and application C. FIG. [Figure 9] 13 is a diagram illustrating a specific example of a window displayed when an application is used in cooperation with application E and application C. FIG. [Figure 10] 13 is a diagram illustrating a specific example of a window displayed when an application is used in cooperation with application E and application C. FIG. [Figure 11] (A) is a diagram showing a specific example of the top window when linked with app E and app C, (B) is a diagram showing a specific example of the top window displaying the final confirmation window for terminating app linkage, and (C) is a diagram showing a specific example of the top window when linked with app C. [Figure 12](A) is a diagram showing a specific example of an application cooperation window related to application E, and (B) and (C) are diagrams showing specific examples of an application use window when cooperation with application E is performed. [Figure 13] 10A is a diagram showing a specific example of a top window when linked with application E, and FIG. 10B is a diagram showing a specific example of a window when linked with application C. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0012] (First embodiment) A first embodiment of the present invention will be described below. In this specification, "information" and "data" are synonymous and are used without any particular distinction. Furthermore, when "information" and "data" are written, the number and format thereof are not limited. Furthermore, data stored or stored in a storage medium in a so-called table format is also included in the "information" and "data" referred to here.

[0013] (Overall configuration of messaging app unified management system 1) 1 is a schematic diagram showing the overall configuration of a message application unified management system 1 according to this embodiment. This message application unified management system 1 is used by a user to centrally manage multiple message applications in an integrated manner. A message application is application software (system) that uses the Internet and enables one-on-one message exchange (conversation, chat) between two users or between three or more users.

[0014] The types (communication methods) of multiple message applications that can be centrally managed by the message application centralized management system 1 are set to include email, messenger, and chat. Note that some SNS (Social Networking Services) such as Twitter and Instagram also allow for message exchange, so SNS with such functionality is also considered to be included in the message application. Furthermore, email and webmail are included in the message application.

[0015] Furthermore, the message app unified management system 1 can centrally manage multiple message apps that use the same communication method but are of different types (display format or layout), as well as multiple message apps that use different communication formats, such as an email application and a messenger application. As will be described in detail later, by receiving authentication permission from an external message app, the message app unified management system 1 can link with the external message app and centrally manage the external message app.

[0016] In the following, the message application unified management system 1 may be simply referred to as "system 1." In the present embodiment, it is assumed that eight existing message applications, message application A to message application H, are set as message applications that can be centrally managed by system 1. In the following, the various message applications may be simply referred to as "applications."

[0017] As shown in Fig. 1, system 1 has a management server 2 managed by the operator of system 1 and a user terminal 3 used by a user. Management server 2 and user terminal 3 are connected via a communication network 4 so as to be able to send and receive information (data) between them. Communication network 4 may be configured, for example, with the Internet, a LAN, a telephone line, a mobile communication network, Wi-Fi (Wireless Fidelity) (registered trademark), other communication lines, or a combination thereof, and may be wired or wireless.

[0018] The management server 2 and the user terminal 3 are also connected via the communication network 4 to a server 5A that manages an application A that can be centrally managed by the system 1 so as to be able to send and receive information (data) to and from each other. Similarly, the management server 2 and the user terminal 3 are also connected via the communication network 4 to servers 5B to 5H that manage applications B to H so as to be able to send and receive information (data) to and from each other. However, the servers 5A to 5H are not included in the system 1. In other words, the servers 5A to 5H do not constitute the system 1. In the following, the servers 5A to 5H may be collectively referred to as "servers 5."

[0019] The management server 2 is configured as a general information processing device, and although not shown, includes a CPU (Central Processing Unit) that controls the entire system, RAM (Random Access Memory) that functions as the CPU's work area, ROM (Read Only Memory) that stores various programs, a storage device that stores various data, an input unit including a keyboard and mouse, a display unit that displays images, and a transmission / reception unit that communicates with external devices. However, the management server 2 may be configured as a single information processing device (one physical computer), or may be configured so that multiple information processing devices (multiple physical computers) can work together to perform its functions (it may also be configured in a cloud environment). Details of the management server 2 will be described later.

[0020] Although a block diagram showing the configuration of the user terminal 3 is omitted, the user terminal 3 is configured as a general communication terminal and includes a CPU that controls the entire device, RAM that functions as a work area for the CPU, ROM that stores various programs, a storage device that stores various data, an input unit including a keyboard and mouse, a display unit that displays images, and a transmission / reception unit that communicates with external devices. Specifically, the user terminal 3 can be a smartphone, a tablet terminal, a laptop computer (notebook), a PDA (Personal Digital Assistant), a desktop computer, or the like. In this embodiment, the user terminal 3 is configured as a laptop computer.

[0021] (Management Server 2) Next, we will explain the management server 2. Fig. 2 is a block diagram showing the characteristic functional configuration of the management server 2. The management server 2 includes a server communication unit 21, a server control unit 22, and a server storage unit 23, and transmits and receives information (data) to and from the user terminal 3 and the server 5, thereby providing a service for centrally managing applications A to H.

[0022] The server communication unit 21 is configured with an interface that communicates with external devices (user terminal 3 and server 5) and transmits and receives information (data). Note that the communication format of the server communication unit 21 with the external devices may be either wireless or wired.

[0023] The server storage unit 23 is configured with a storage device such as a semiconductor memory or a disk drive provided by a storage area of ​​a physical device that is a computer-readable recording medium. Furthermore, the server storage unit 23 stores various programs including an operating system program and a driver program, as well as various data used during the execution of these programs.

[0024] The server storage unit 23 also stores a management program 23a to be executed by the server control unit 22, which will be described later. The server storage unit 23 also includes a database 23b that stores and accumulates various data used during the execution of the management program 23a.

[0025] The database 23b has a plurality of tables. Fig. 3 is a diagram schematically showing a plurality of tables registered in the database 23b. The plurality of tables includes a user information table 24a and a thread information table 24b. The various tables are described below. Note that the configuration of the various tables is not limited to the contents described below and may be changed as appropriate.

[0026] The user information table 24a is a table that stores information about users (hereinafter referred to as "user information"). The user information includes a user ID, which is the user's ID, as well as an email address and a password. Storing (memorizing) user information about a certain user in the user information table 24a is referred to as "user registration" for that user.

[0027] An example of the configuration of the user information table 24a is shown in Fig. 4. As shown in Fig. 4, the user information table 24a stores email addresses and passwords in association with user IDs. As will be described later, when the user terminal 3 accesses the management server 2 for the first time, the management server 2 causes the user terminal 3 to display a screen for inputting the email address and password.

[0028] The thread information table 24b is a table that stores information about threads (hereinafter referred to as "thread information") and is generated for each thread. Note that a thread may be called something other than "thread," such as "room" or "talk," depending on the type of messaging app, but it is the totality of a series of message exchanges, and there are threads formed by one-on-one exchanges between two people and threads formed by mutual exchanges between three or more people.

[0029] The thread information table 24b associates a user ID, the type of message application in which the thread is deployed, and a thread ID that is the ID of the thread. Each thread information table 24b also includes each message that makes up the thread, the date and time the message was sent, and the sender.

[0030] Next, we will explain the server control unit 22. The server control unit 22 is a processor, that is, a processing device that performs operations, processing, and transfer of data, executes programs, and controls other devices, and is composed of a CPU and various registers.

[0031] The server control unit 22 centrally controls the management server 2 by executing various programs stored in the server storage unit 23. Furthermore, by executing the management program, the server control unit 22 cooperates with the user terminal 3 and the servers 5A to 5H to realize a centralized management function for various messaging apps.

[0032] The following describes each functional block realized by the server control unit 22. As shown in Fig. 2, the server control unit 22 has an authentication management unit 22a, a cooperation management unit 22b, a display switching management unit 22c, and a message information update management unit 22d. Each of the units 22a to 22d corresponds to a function that can be realized by the server control unit 22. Note that the configuration of each of the units 22a to 22d corresponding to the functions of the server control unit 22 is not limited to this, and each of the units 22a to 22d may be integrated as appropriate, and each of the units 22a to 22d may be further subdivided as appropriate.

[0033] When accessed from a user terminal 3, the authentication management unit 22a checks the user ID to log in. As will be described later, when a user is registered, a user ID is assigned to the user terminal 3 (user) that has accessed the management server 2, and when the user terminal 3 accesses the management server 2 after user registration, the user ID is also sent to the management server 2 as header information. Therefore, when accessed from a user terminal 3, if a user ID is included, the authentication management unit 22a subsequently determines whether or not the user ID is registered in the management server 2. If the user ID is registered, the authentication management unit 22a logs in the user terminal 3 and displays a top window 1C, which will be described later. On the other hand, if the user terminal 3 is not registered, an error message indicating that the login has failed is displayed on the user terminal 3 (not shown).

[0034] Furthermore, when a user terminal 3 accesses the management server 2 and the user ID is not included, the authentication management unit 22a causes the user terminal 3 to display a screen (a user registration screen 12, described later) on which the user can enter an email address and password. When an email address and password are sent to the management server 2 by a predetermined operation on the user terminal 3, the authentication management unit 22a appropriately issues a user ID for the email address and password, and stores (stores) the email address and password in the user information table 24a in association with the user ID. Furthermore, the authentication management unit 22a sends the issued user ID to the user terminal 3, and thereafter, whenever the user terminal 3 accesses the management server 2, the user ID is always sent as header information. Note that the user registration method is not limited to this and may be changed as appropriate.

[0035] The cooperation management unit 22b is capable of performing processing to start cooperation with the servers 5A to 5H that are positioned as external devices for the system 1. Although some explanation will be omitted below, when the cooperation management unit 22b receives a request from the user terminal 3 to start cooperation with the applications A to H (the servers 5A to 5H), the cooperation management unit 22b performs processing (OAuth2.0) to request permission for general authority.

[0036] When a type of message app requesting the start of collaboration is sent to the management server 2 by a predetermined operation on the user terminal 3, the collaboration management unit 22b causes (redirects) the user terminal 3 to display a login screen (an app login screen 17, described later) related to the message app. Then, when a login operation related to the message app is performed on the user terminal 3, the collaboration management unit 22b accesses the server 5 related to the message app to request collaboration permission. Here, the server 5 determines whether collaboration is permitted, and if collaboration permission is successful, the collaboration management unit 22b stores information about the user on the server 5 in the thread information table 24c (registers information about the user related to the message app that is the target of collaboration).

[0037] Furthermore, the cooperation management unit 22b can perform processing to terminate cooperation with the servers 5A to 5H. Specifically, when a type of message app for which cooperation is requested to be terminated is transmitted to the management server 2 by a predetermined operation on the user terminal 3, the cooperation management unit 22b causes the user terminal 3 to display a screen (an application cooperation termination final confirmation window 19, described later) for final confirmation of terminating cooperation with the message app. While this screen is displayed, the user terminal 3 can perform an operation to approve the termination of cooperation, and when the approval operation is performed, the cooperation management unit 22b requests the server 5 related to the message app to terminate cooperation. In response to this, the server 5 terminates cooperation with the system 1. Furthermore, the cooperation management unit 22b deletes information related to the message app of the user from the database 23b.

[0038] The display switching management unit 22c changes the display content of the screen related to the system 1 displayed on the user terminal 3 by performing a predetermined operation on the user terminal 3 while the user terminal 3 is logged in to the system 1. Although details will be described later, this predetermined operation can be performed at the player's discretion, and by performing this predetermined operation, the message app to be used can be easily switched while the screen related to the system 1 (a window 10 for the message app unified management system described later) is displayed (while the software related to the system 1 is open).

[0039] The message information update management unit 22d performs processing related to updating information related to messages for each user ID. Specifically, the message information update management unit 22d accesses each server 5 at predetermined time intervals (for example, every minute), acquires the latest data related to messages for each user ID, and performs processing to update each thread information table 24b. In addition, when information related to a message app on a main function screen 18 (described later) is displayed, the information related to the message app is updated in real time.

[0040] Next, a specific example of a user using the system 1 using a user terminal 3 will be described. It is assumed that the user has installed software (program) for using the system 1 on his / her own user terminal 3 by downloading it from a predetermined site, etc. When the software related to the system 1 is installed on the user terminal 3, the user terminal 3 itself functions as a local server for the system 1. After installation, browsing on the user terminal 3 performs various processes related to the system 1. In this embodiment, the user terminal 3 is assumed to be a laptop computer. Therefore, various images are displayed on the display, and predetermined input operations are performed using a mouse and keyboard.

[0041] When software related to the system 1 is started on the user terminal 3 in a situation where a user has not registered with the system 1, the user terminal 3 displays a window related to the system 1 (a window 10 for the message app unified management system, hereinafter simply referred to as "window 10") on the display. The display content of window 10 changes depending on the situation. Specifically, the display content and layout of window 10 differ when the software related to the system 1 is started in a situation where a user has not registered, when a user is registered, when user registration is completed and no message app is being used, when user registration is completed and linkage with any message app is being used, and when user registration is completed and any message app is being used. In the following, window 10 when software related to system 1 is launched without user registration will be referred to as "window 1A when starting app use," window 10 when registering a user will be referred to as "window 1B when registering a user," window 10 when none of the message apps are being used after user registration is complete will be referred to as "top window 1C," window 10 when linking with any of the message apps is being performed after user registration is complete will be referred to as "window 1D when linking with app," and window 10 when none of the message apps is being used after user registration is complete will be referred to as "window 1E when using app."

[0042] The window 10 is composed of a fixed display area 10A formed in a strip shape at the top end and a variable display area 10B formed in a rectangular shape just below it, which can occupy most of the window. As will be described in detail later, even if the status related to the system 1 subsequently changes in various ways, the fixed display area 10A continues to be displayed as is while the user terminal 3 is connected to the system 1 (while the software related to the system 1 is open). Meanwhile, the content displayed in the variable display area 10B (the functions available in the system 1) changes in response to the various changes in the status related to the system 1.

[0043] FIG. 5A shows a specific example of an application usage start window 1A. As shown in FIG. 5A, the application usage start window 1A is divided into a fixed display area 10A formed in a strip shape at the top edge and a variable display area 10B formed in a rectangular shape directly below the fixed display area 10A and occupying most of the application usage start window 1A. As will be described later, the fixed display area 10A is formed in common with the application usage start window 1A, user registration window 1B, top window 1C, application linkage window 1D, and application usage window 1E, and the content displayed in the fixed display area 10A does not change. On the other hand, the content displayed in the variable display area 10B differs between the application usage start window 1A, user registration window 1B, top window 1C, application linkage window 1D, and application usage window 1E.

[0044] The fixed display area 10A is configured with a so-called "title bar." For example, the name of the system 1 ("〇△□▽" in FIG. 5(A)) is displayed on the left edge of the fixed display area 10A. A start screen 11 corresponding to the application usage start window 1A is displayed in the variable display area 10B of the application usage start window 1A. The start screen 11 displays a start button 111 for starting full-scale use of the system 1, in other words, for user registration. When the start button 111 is operated, the application usage start window 1A is switched to a user registration window 1B for user registration for the system 1.

[0045] FIG. 5(B) shows a specific example of the user registration window 1B. As shown in FIG. 5(B), the user registration window 1B is partitioned into a fixed display area 10A and a variable display area 10B, similar to the application usage start window 1A. The fixed display area 10A has a title bar, similar to the application usage start window 1A. Meanwhile, the variable display area 10B displays a user registration screen 12 for performing user registration (new registration) related to the system 1. That is, when the start button 111 is operated, the content displayed in the variable display area 10B is essentially switched from the start screen 11 to the user registration screen 12.

[0046] The user registration screen 12 is configured to allow input of user registration information. In this embodiment, the user registration information consists of an email address and a password. Therefore, the user registration screen 12 is formed with an email address input field 121 for inputting an email address and a password input field 122 for inputting a password. The method of inputting an email address into the email address input field 121 and the method of inputting a password into the password input field 122 can be set as appropriate. In this embodiment, the user terminal 3 is configured as a laptop computer. Therefore, for example, when the email address input field 121 or the password input field 122 is clicked, a cursor is displayed there and a state in which input is possible using a keyboard (not shown), and an email address and a password are input into the email address input field 121 or the password input field 122 in response to operation of the keyboard. Note that if the user terminal 3 is configured as a smartphone or a tablet, for example, when the email address input field 121 or the password input field 122 is tapped, a cursor may be displayed there and a predetermined software keyboard (not shown) may be superimposed on the user registration screen 12. An email address and a password may be entered into the email address entry field 121 and the password entry field 122 by operating a predetermined software keyboard.

[0047] The user registration screen 12 also has a registration execution button 123 for executing user registration, in other words, for making a user registration request to the management server 2. When the registration execution button 123 is operated, the information (email address) entered in the email address input field 121 and the information (password) entered in the password input field 122 are associated with each other and sent to the management server 2. The associated email address and password are referred to as "user registration information." When the registration execution button 123 is operated, a command requesting user registration (user registration request command) is also sent to the management server 2 along with the user information.

[0048] Then, upon receiving the user registration request command and the user registration information, the management server 2 stores the user registration information in the user information table 24a, thereby registering the user registration information (performing user registration). In particular, upon receiving the user registration request, the management server 2 issues information (user ID) for appropriately identifying the user, and stores the email address and password in the user information table 24a in association with the user ID. Furthermore, upon registering the user registration information, the management server 2 causes the user terminal 3 to switch from the user registration window 1B to the top window 1C. The top window 1C is a window (screen) that serves as the starting point for the user who has registered the user, and thereafter, when the software related to the system 1 is started in a state in which it is not running, the top window 1C is displayed. However, as will be described later, the display content of the top window 1C varies depending on the situation.

[0049] FIG. 5C shows a specific example of a top window 1C that is displayed upon completion of user registration. As shown in FIG. 5C, the top window 1C has a fixed display area 10A that forms a title bar, similar to the application usage start window 1A and the user registration window 1B. However, unlike the application usage start window 1A and the user registration window 1B, the variable display area 10B of the top window 1C is further divided into a left pane 10BL and a right pane 10BR. As will be described later, when an application login screen 17 or a main function screen 18 of various messaging applications is displayed, the variable display area 10B is also divided into a left pane 10BL and a right pane 10BR, similar to the top window 1C. The content displayed in the left pane 10BL is basically the same in the top window 1C, the application linkage window 1D, and the application usage window 1E, but the content displayed in the right pane 10BR is different in the top window 1C, the application linkage window 1D, and the application usage window 1E.

[0050] The left pane 10BL associated with the top window 1C displays a right pane switching operation screen 14 for switching the content displayed in the right pane 10BR, and the right pane 10BR associated with the top window 1C displays a message app list screen 15 for displaying a list of message apps that can be linked to the system 1. The left pane 10BL is formed in a vertically elongated rectangular shape at the left end of the variable display area 10B, and the right pane 10BR is formed in a horizontally elongated rectangular shape in most of the variable display area 10B except for the left pane 10BL. In this embodiment, the right pane 10BR is formed several times larger than the left pane 10BL.

[0051] The right-side pane switching operation screen 14 displays, in a vertical row, a main function display button 140 that can accept an operation to display the main function screen 18 in the right-side pane 10BR, a message application list display button 141 that can accept an operation to display the message application list screen 15 in the right-side pane 10BR, and a setting screen display button 142 that can accept an operation to display a screen for making various settings in the right-side pane 10BR.

[0052] The main function display button 140 is used when the right pane 10BR displays a message application list screen 15, an application login screen 17 related to various message applications described below, or a screen for performing various settings (not shown) and the user wishes to switch to the main function screen 18. When the main function display button 140 is operated, the main function screen 18 is displayed in the right pane 10BR. Note that when the system 1 is not linked to any message application, operation of the main function display button 140 is disabled.

[0053] The message app list display button 141 is not particularly used when the message app list screen 15 is displayed in the right pane 10BR, but is used when the main function screen 18, the app login screen 17 related to various message apps, or a screen for performing various settings (not shown) is displayed in the right pane 10BR and it is desired to switch to the message app list screen 15. When the message app list display button 141 is operated, the message app list screen 15 is displayed in the right pane 10BR.

[0054] Although not shown here, when the settings screen display button 142 is operated while the main function screen 18, the message application list screen 15, or the application login screen 17 related to various message applications is displayed in the right pane 10BR, a screen for performing various settings is displayed in the right pane 10BR. Although not described here, the screen for performing various settings is configured to be able to accept operations for setting various items.

[0055] The message application list screen 15 displays a list of message applications that can be linked with the system 1. Images (message application images 16) individually representing applications A to H are displayed appropriately on the message application list screen 15. Here, the message application image 16 representing application A will be referred to as "application A image 16A." Similarly, the message application images 16 representing applications B to H will be referred to as "application B image 16B" to "application H image 16H."

[0056] In this embodiment, each message application image 16 has the same shape and size regardless of the type of application. Note that the overall shape and size of the message application image 16 can be set as appropriate, but in this embodiment, the message application images 16 are formed in a vertically long rectangular shape and arranged in two rows, top and bottom, with four message application images in each row lined up horizontally on the message application list screen 15.

[0057] A logo and name representing the application are displayed in approximately the upper two-thirds of the vertical area of ​​each message application image 16. Furthermore, a button (application cooperation operation screen display button 161) that can accept an operation to display a screen (application cooperation operation screen) for performing an operation to cooperate with the system 1 is provided in approximately the lower one-third of the vertical area of ​​each message application image 16. Here, the application cooperation operation screen display button 161 for application A will be referred to as the "application cooperation operation screen display button 161A." Similarly, the application cooperation operation screen display buttons 161 for applications B to H will be referred to as the "application B cooperation operation screen display button 161B" to "application H cooperation operation screen display button 161H."

[0058] When the application A cooperation operation screen display button 161A is operated, a command indicating a request to start cooperation with application A (application A cooperation start request command) is sent together with the user ID to the management server 2. When the management server 2 receives the application A cooperation start request command, it causes the user terminal 3 to display a login screen for application A (redirects to application A and causes the login screen for application A to be displayed on the user terminal 3). In other words, the management server 2 switches from the top window 1C to an application cooperation window 1D including the login screen for application A.

[0059] Furthermore, similarly to when the application A cooperation operation screen display button 161A is operated, when the application B cooperation operation screen display button 161B through application H cooperation operation screen display button 161H are operated, commands indicating a request to start cooperation with applications B through H (application B cooperation start request command through application H cooperation start request command) are transmitted to the management server 2 together with the user ID. Upon receiving the application B cooperation start request command through application H cooperation start request command, the management server 2 causes the user terminal 3 to display login screens for applications B through H (redirects to applications B through H and causes the login screens for applications B through H to be displayed on the user terminal 3). In other words, the management server 2 switches from the top window 1C to the application cooperation window 1D including the login screens for applications B through H.

[0060] Note that since these are login screens for apps A to H, it is basically assumed that the user has already been registered for apps A to H. In the following, the login screens for apps A to H will be referred to as "app A login screen 17A" to "app H login screen 17H," and "app A login screen 17A" to "app H login screen 17H" will be collectively referred to as "app login screen 17."

[0061] Furthermore, in this embodiment, in order to link the system 1 with applications A to H, the management server 2 switches from the top window 1C to the application linking window 1D and displays the application login screen 17 related to the application on the user terminal 3. However, since the application login screen 17 is displayed by redirection, the application A login screen 17A to the application H login screen 17H are provided by the applications A to H (servers 5A to H). Therefore, the display contents (screen configuration, layout, or type) of the application A login screen 17A to the application H login screen 17H differ depending on the type of message application.

[0062] The user terminal 3 displays the application login screen 17 in the right pane 10BR. Here, it is assumed that the application E cooperation operation screen display button 161E is operated in the situation of Fig. 5(C). As a result, the application E login screen 17E is displayed in the right pane 10BR of the variable display area 10B in the application cooperation window 1D.

[0063] Fig. 6(A) shows a specific example of an app linking window 1D including an app E login screen 17E. As shown in Fig. 6(A), app E login screen 17E has an email address input field 171E for inputting an email address and a password input field 172E for inputting a password. This indicates that the information required to log in to app E is an email address and a password. Note that the information required to log in and the configuration of each app login screen 17 differ depending on the messaging app.

[0064] The method of inputting an email address into email address input field 171E and the method of inputting an email address into password input field 172E can be set appropriately in the same way as the method of inputting an email address into email address input field 121 and the method of inputting a password into password input field 122, so explanation will be omitted.

[0065] Then, when the email address registered in app E is entered in email address input field 171E, the password registered in app E is entered in password input field 172E, and the cursor is displayed in email address input field 171E or password input field 172E, and the "ENTER / Execute" button on the keyboard of user terminal 3 is operated, user terminal 3 associates this information (app E login information) with each other and transmits it to app E server 5E.

[0066] When the app E server 5E receives the app E login information transmitted from the user terminal 3, it determines whether the user is registered in app E, and if the user is registered, it grants permission for collaboration to the system 1 via the user terminal 3. When collaboration is granted, the management server 2 finally accesses the app E server 5E to acquire data related to the user, and stores the data in association with the user ID of the user in the server storage unit 23. That is, the app E server 5E provides the data related to the user to the system 1. This initiates collaboration between app E and the system 1.

[0067] The content of the data provided by app E depends on the messaging app, but at least includes information about messages. The content of the information about messages is basically set appropriately by the messaging app. For example, information about messages is divided into threads (including talks or chats), and each thread (including talks or chats) further includes data for each message. The data for each message includes the date and time the message was sent, the sender, and the specific content of the message (text, image, audio), which are associated with each other. Note that, below, data for each message consisting of the date and time the message was sent, the sender, and the specific content of the message, which are associated with each other, is referred to as "message data." Furthermore, information for each thread that includes one or more message data is referred to as "thread data."

[0068] As mentioned above, the server memory unit 23 stores thread information tables 24b on a per-thread basis, so the management server 2 generates a thread information table 24b that associates the user ID of the user with app E based on the thread data obtained from server 5E.

[0069] Furthermore, when the management server 2 receives permission for collaboration from app E and generates a thread information table 24b associating user IDs with app E, it causes the user terminal 3 to display, in the right-hand pane 10BR, a main function screen 18 that allows app E to be used in the system 1, based on the thread information table 24b. Therefore, the user terminal 3 switches the display content in the right-hand pane 10BR from the app E login screen 17E that was displayed immediately before collaboration permission was granted, to the main function screen 18. The main function screen 18 will be described later.

[0070] Returning to the description of the application linkage window 1D including the application E login screen 17E, as shown in Fig. 6(A), the application E login screen 17E is displayed in the right pane 10BR of the application linkage window 1D, but the variable display area 10B of the application linkage window 1D is divided into a left pane 10BL and a right pane 10BR, similar to the top window 1C. Also, similar to the top window 1C, the left pane 10BL displays a right pane switching operation screen 14.

[0071] In the right pane switching operation screen 14 of the application cooperation window 1D, a main function display button 140, a message application list display button 141, and a setting screen display button 142 are displayed in the same positions as in the top window 1C.

[0072] Next, the main function screen 18 will be described. Fig. 6(B) shows a specific example of an application usage window 1E including the main function screen 18. As shown in Fig. 6(B), the main function screen 18 is displayed in the right pane 10BR of the variable display area 10B. The main function screen 18 is further divided into a left side and a right side. Both the left side and the right side are formed in a vertically long rectangle.

[0073] The left side of the main function screen 18 is functionally divided into three areas along the vertical direction. Specifically, a horizontally long rectangular thread search area 18A is formed at the top end of the left side of the main function screen 18, a horizontally long rectangular displayed application switching operation area 18B is formed directly below the thread search area 18A, and a vertically long rectangular thread information list display area 18C is formed directly below the displayed application switching operation area 18B.

[0074] The thread search area 18A is provided with a search information input field 181 for searching threads. A detailed description of the search information input field 181 will be omitted, but information for searching threads, such as keywords, can be input into the search input field 181, and threads can be searched for based on the keywords, etc., input into the search information input field 181.

[0075] Display application switching operation area 18B displays buttons (display content specification buttons) 182 for specifying the display content of thread information list display area 181C. Display content specification buttons 182 include an all display button 182Z for displaying information about threads of all message applications linked with system 1, and an individual display button 182K for displaying information about threads of one message application among the message applications linked with system 1.

[0076] The individual display button 182K is set for each message application, and the individual display button 182K includes an application A individual display button 182KA to an application H individual display button 182KH associated with the message applications A to H, respectively.

[0077] If there is at least one message app linked with the system 1, an entire display button 182Z is ​​displayed, and further, an individual display button 182K associated with the message app linked at that time is also displayed. Note that Fig. 6(B) shows the situation immediately after the system 1 is first linked with message app E, so Fig. 6(B) displays entire display button 182Z and app E individual display button 182KE. Furthermore, with regard to the display positions of the display content specification buttons 182, the entire display button 182Z is ​​displayed at the left end of the displayed app switching operation area 18B, and to the right of it, the individual display buttons 182K are displayed lined up from left to right in the order of linkage.

[0078] Also, each of the display content specification buttons 182 is configured to be able to accept a selection operation, but only one of the display content specification buttons 182 can be selected at any one time. However, when the main function screen 18 is displayed, the whole display button 182Z is ​​assumed to be in a selected state.

[0079] The thread information list display area 181C displays a list of information about a certain number of threads (six in this embodiment). Information about threads is set for each thread, and information about one thread is made up of a horizontally long rectangular icon (thread information icon) 183. All thread information icons 183 have the same size and shape, and are displayed in order from top to bottom in the order in which the threads were updated.

[0080] At the left end of the thread information icon 183, a circular image is displayed representing participants (parties) of the thread corresponding to the thread information icon 183 other than the user. If the thread is formed between the user and one other person, a circular image representing the other person is displayed. If the thread is formed between the user and two or more other people, a circular image representing one of the other two people is placed in the center, and the remaining circular images are displayed partially offset from the central circular image and in the background.

[0081] A circular image representing the type of message application is displayed at the right end of the thread information icon 183. Since Fig. 6(B) shows the situation immediately after the system 1 is first linked with the message application E, only the thread information icon 183 relating to the message application E is displayed in Fig. 6(B). Therefore, in Fig. 6(B), a circular image representing the message application E is displayed at the right end of all the thread information icons 183. Specifically, the letter "E" representing the message application E is displayed inside the circular image representing the type of message application.

[0082] In the upper part of the center part of the thread information icon 183, excluding both ends, the name of the other person in the case where the thread is formed by two people including the user, or the name of the group in the case where the thread is formed by a group, is displayed. In the lower part of the center part of the thread information icon 183, excluding both ends, content according to the message app is displayed. Specifically, if the message app is configured to include a subject like email, the subject is displayed, and if it is configured not to include a subject like chat, the opening part of the latest message (in this embodiment, 12 characters: latest simplified message) and its sender are displayed.

[0083] Furthermore, the thread information icons 183 are configured to be able to accept a selection operation, and a detailed history of messages related to the selected thread information icon 183 is displayed in a preview display area 185, which will be described later. When the main function screen 18 is displayed, the thread information icon 183 displayed at the top, in other words, the thread information icon 183 corresponding to the thread that was most recently updated (the thread to which a message was sent), is in a selected state.

[0084] Next, the right side of the main function screen 18 will be described. The right side of the main function screen 18 is divided into three sections in the vertical direction. Specifically, a horizontally long rectangular thread target display area 184 is formed at the top end of the right side of the main function screen 18, a horizontally long rectangular message sending operation area 186 is formed at the bottom end, and a vertically long rectangular preview display area 185 is formed in the vertical center between the thread target display area 184 and the message sending operation area 186.

[0085] A circular image representing something other than the user of the thread related to the preview display area 185 (the thread target, the thread partner: individual name or group name) is displayed at the left end of the thread target display area 184, and a character string representing the thread target (individual name or group name: in FIG. 6(B) , the group name "XX Company Sales Department") is displayed to the right of the circular image. That is, information other than the latest simplified message in the thread information icon 183 is displayed in the thread target display area 184.

[0086] Message exchanges are displayed in preview display area 185. The most recently sent message is displayed at the bottom of preview display area 185, and messages exchanged from there are displayed chronologically from top to bottom. The display format of messages is not particularly limited and can be set as appropriate, but in this embodiment, messages are displayed in speech bubbles, and speech bubbles representing messages sent by the user in question are displayed right-justified, while speech bubbles representing messages sent by someone other than the user in question (the target of the thread, the other party in the thread) are displayed left-justified.

[0087] Message sending operation area 186 is provided with message input field 186A for inputting a message to be sent by the user, and send button 186B for sending the message input in message input field 186A. The specific configuration of message sending operation area 186 can be set as appropriate, but in this embodiment, send button 186B is configured in the shape of a right arrow and is located at the right end of message sending operation area 186. On the other hand, message input field 186A is formed in the shape of a horizontally long rectangle and is located to the left of send button 186B.

[0088] The method for inputting a message into message input field 186A can be set as appropriate, but in this embodiment, since user terminal 3 is configured as a personal computer, for example, a message can be input into message input field 186A by displaying a cursor in message input field 186A and then operating a keyboard. Send button 186B is configured to be able to accept operations. The operation and processing contents when send button 186B is operated will be described later.

[0089] The main function screen 18 has the same screen configuration and design whether the full display button 182Z is ​​selected or whether any of the individual display buttons 182K (app A individual display button 182KA to app G individual display button KG) is selected; in other words, whether the thread information icons 183 related to all linked message apps are displayed together or whether the thread information icon 183 related to one specific message app is displayed. However, the screen configuration and design do not have to be completely identical; for example, the screen configuration and design may be different when the full display button 182Z is ​​selected and when the individual display button 182K is selected. Furthermore, the screen configuration and design may be set for each message app type (email, messenger).

[0090] Here, for example, assume that the message application list display button 141 is operated in the situation shown in FIG. 6(B). As described above, this message application list display button 141 is a button for displaying the message application list screen 15 in the right pane 10BR of the variable display area 10B. Therefore, when the message application list display button 141 is operated, the user terminal 3 transmits to the management server 2 the user ID of the user terminal 3 and a command (message application list screen display request command) indicating a request for displaying the message application list screen 15. Upon receiving the message application list screen display request command, the management server 2 displays on the user terminal 3 a top window 1C including the message application list screen 15 with content corresponding to the current situation of the user identified by the user ID. Here, the "content corresponding to the current situation of the user" differs depending on whether the user is linked to each message app.

[0091] 7(A) is a diagram showing a specific example of a top window 1C that is displayed in response to the operation of the message application list display button 141 in the situation shown in FIG. 6(B). As described above, since the system 1 is currently linked to the application E, there is no need to newly link the system 1 to the application E. Therefore, as shown in FIG. 7(A), the application E image 16E displayed on the message application list screen 15 in the situation where the system 1 is linked to the application E has a button (application E linkage cancellation button 162E) that can accept an operation to cancel the linkage with the application E, instead of the application E linkage operation screen display button 161E. The operation of the system 1 when the application E linkage cancellation button 162E is operated will be described later.

[0092] In the situation shown in FIG. 7(A), for example, when the application C collaboration operation screen display button 161C is operated, an application C collaboration start request command is sent to the management server 2, and just as when the application E collaboration operation screen display button 161E is operated, the top window 1C is switched to the application collaboration window 1D as shown in FIG. 7(B), and the application C login screen 17C is displayed in the right pane 10BR of the application collaboration window 1D.

[0093] The application C login screen 17C includes an email address / phone number input field 171C for inputting an email address or a phone number, and a password input field 172C for inputting a password. That is, in this embodiment, the email address or the phone number and the password constitute the information required to log in to application C. The application C login screen 17C also includes a login button 173C for executing login.

[0094] When the login button 173C is operated, the user terminal 3 transmits the email address or telephone number as authentication information and the password (application C login information) to the application C server 5C, just as when the application E login screen 17E is displayed.

[0095] When the app C server 5C receives the app C login information transmitted from the user terminal 3, it determines whether the user is registered in app C, and if the user is registered, it grants permission for collaboration to the system 1 via the user terminal 3. When collaboration is granted, similar to when collaboration with app E is initiated, the management server 2 finally accesses the app C server 5C to acquire data related to the user, and stores the data in the server storage unit 23 in association with the user ID of the user. That is, the app C server 5C provides the data related to the user to the system 1. This initiates collaboration between app C and the system 1. Furthermore, in response to the start of collaboration with app C, the management server 2 switches from the app C login screen 17C to the main function screen 18.

[0096] Fig. 8(A) is a diagram showing an application usage window 1E including a main function screen 18 immediately after the system 1 is linked with the application C. Since the system 1 is linked with the application C after the application E, as shown in Fig. 8(A), an application C individual display button 182KC associated with the application C is displayed to the right of the application E individual display button 182KE.

[0097] 8(A) shows the situation immediately after switching to the main function screen 18, so the full display button 182Z is ​​selected. Therefore, the thread information list display area 181C can display thread information icons 183 related to all message apps linked with the system 1 (apps E and C in this situation).

[0098] The thread information icon 183 related to application C is a thread information icon 183 having the letter "C" displayed at the right end, which represents application C. Therefore, in the situation shown in FIG. 8(A), the thread information icon 183 related to application C, the thread information icon 183 related to application C, the thread information icon 183 related to application E, the thread information icon 183 related to application E, the thread information icon 183 related to application C, and the thread information icon 183 related to application E are displayed in this order from top to bottom.

[0099] In the situation shown in FIG. 8(A), the six most recently updated threads include those related to app E and those related to app C, so thread information icon 183 related to app E and thread information icon 183 related to app C are displayed. However, if all of the six most recently updated threads are related to one of the apps, only thread information icon 183 related to that app will be displayed.

[0100] 8(A), it is assumed that the application C individual display button 182KC associated with application C is operated. Then, as shown in FIG. 8(B), only the thread information icon 183 related to application C is displayed in the thread information list display area 181C, and the message exchange of the most recently updated thread related to application C is displayed in the preview display area 185. In other words, the operation of selecting the application C individual display button 182KC constitutes a request to display the main function screen 18 related to application C (dedicated to application C).

[0101] When an operation to select the application C individual display button 182KC is performed, the user terminal 3 transmits, together with the user ID, a command (application C main function screen display request command) indicating a request to display the main function screen 18 related to application C (dedicated to application C) to the management server 2. Upon receiving the application C main function screen display request command, the management server 2 causes the user terminal 3 to display the main function screen 18 related to application C (dedicated to application C).

[0102] When the management server 2 receives the application C main function screen display request command, it accesses the server 5C of application C to obtain data related to the thread related to the user in application C, and further updates the data related to application C related to the user in the server memory unit 23 (thread information table 24b), and then switches the display contents of the thread information list display area 181C, the thread target display area 184, and the preview display area 185 to those related to application C in accordance with the data.

[0103] 8(A) or 8(B), suppose that the app E individual display button 182KE associated with app E is operated. Then, as shown in Fig. 8(C), only the thread information icon 183 related to app E is displayed in the thread information list display area 181C, and the message exchange of the most recently updated thread related to app E is displayed in the preview display area 185. In other words, the operation of selecting the app E individual display button 182KE constitutes a request to display the main function screen 18 related to app E (dedicated to app E).

[0104] When an operation to select the app E individual display button 182KE is performed, the user terminal 3 transmits, together with the user ID, a command (app E main function screen display request command) indicating a request to display the main function screen 18 related to app E (dedicated to app E) to the management server 2. Upon receiving the app E main function screen display request command, the management server 2 causes the user terminal 3 to display the main function screen 18 related to app E (dedicated to app E).

[0105] When the management server 2 receives the application E main function screen display request command, it accesses the server 5E of application E to obtain data related to the thread related to the user in application E, and further updates the data related to application E related to the user (thread information table 24b) in the server memory unit 23, and then switches the display contents of the thread information list display area 181C, the thread target display area 184, and the preview display area 185 to those related to application E in accordance with the data.

[0106] In addition, when the full display button 182Z is ​​operated in the situation shown in FIG. 8(B) or the situation shown in FIG. 8(C), the main function screen 18 relating to the currently linked app E and app C, as shown in FIG. 8(A), is displayed.

[0107] As described above, each thread information icon 183 displayed in the thread information list display area 181C is configured to be able to accept a selection operation. When an operation to select a thread information icon 183 is performed, detailed information about the thread corresponding to that thread information icon 183 is displayed on the right side of the main function screen 18. In other words, the operation to select a thread information icon 183 constitutes a request to display detailed information about the thread corresponding to that thread information icon 183.

[0108] When an operation to select the thread information icon 183 is performed, the user terminal 3 associates the target of the thread related to the thread information icon 183 with the user ID and sends them to the management server 2, and also sends a command (thread detailed information display request command) indicating a request to display thread detailed information to the management server 2.

[0109] When the management server 2 receives a thread detail information display request command, it accesses the server 5 of the application related to the thread, acquires data related to the thread, and further updates the data related to the thread (thread information table 24b) in the data related to the application related to the user in the server memory unit 23, and then switches the display contents of the thread target display area 184 and the preview display area 185 to those related to the thread in accordance with the data.

[0110] For example, in the situation shown in Figure 8(C), when the thread information icon 183 relating to the second app E from the top is operated, the display content of the thread target display area 184 and the display content of the preview display area 185 are switched to that of the thread relating to that thread information icon 183, as shown in Figure 9(A).

[0111] Here, the exchange (sending and receiving) of messages in app E via system 1 will be described. For example, in the situation shown in FIG. 9(A), if the text "Thank you" is entered in message input field 186A, the result will be as shown in FIG. 9(B). In this situation, when send button 186B is operated, user terminal 3 transmits the content entered in message input field 186A (text: Thank you) to management server 2 in association with the user ID of user terminal 3, the target of the thread displayed in thread target display area 184, and the type of message app (app E). Note that the information transmitted to management server 2, specifically, the content entered in message input field 186A, the user ID, the target of the thread, and the type of message app (app E) will be collectively referred to as "transmitted message information."

[0112] When the management server 2 receives the sent message information, it updates the thread information table 24b for the thread in the server storage unit 23 so that the sent message information is reflected. Specifically, in the thread information table 24b for the application E associated with the user ID included in the sent message information, which includes the target of the thread, the management server 2 newly stores the message content in association with the current date and time and the user as the sender in the thread information table 24b that includes the target of the thread. The management server 2 also transmits the sent message information to the server 5E of the application E. This allows the server 5E of the application E to update data related to the thread consisting of the user and the target of the thread.

[0113] Furthermore, when management server 2 receives the transmitted message information, it updates preview display area 185 so that the transmitted message information is reflected. Therefore, as shown in Figures 9(A) and 9(B), until send button 186B is operated, the message "Got it" sent by the subject of the thread (YMD) was displayed at the bottom of preview display area 185, and this message was the most recent message, but by operating send button 186B, as shown in Figure 10(A), a speech bubble representing "Thank you" sent by the user is displayed at the bottom of preview display area 185, and the speech bubbles representing the other displayed messages are shifted up by the amount of the newly displayed speech bubble.

[0114] Also, as shown in FIG. 10(A), when the main function screen 18 is displayed, if the target of the thread displayed in the thread target display area 184 (in FIG. 10(A), "YMD-san") sends a message to the user related to the user terminal 3 using app E (if the message is sent to the server 5E of app E), the server 5E of app E first transmits to the management server 2 the sender of the message (in FIG. 10(A), "YMD-san"), the message destination (the user related to the user terminal 3), the content of the message, and the date and time the message was sent.

[0115] When the management server 2 receives the information transmitted from the server 5E of the application E, it updates the server storage unit 23 so that the information is reflected. Specifically, the management server 2 identifies the user ID by checking the information indicating the destination of the message included in the information transmitted from the server 5E of the application E against the user information table 24a, and stores the content of the message in association with the date and time of the message and the sender of the message as the sender in the thread information table 24b for the application E related to the user ID and the thread formed with the target of the thread.

[0116] Furthermore, when management server 2 receives information transmitted from server 5E of application E, it updates preview display area 185 to reflect the information. Here, assuming that the transmitted message is the text "You're welcome," as shown in Figures 10(A) and 10(B), until a message is transmitted from the target of the thread (YMD), the message "Thank you" transmitted by the user is displayed at the bottom of preview display area 185, and this message is the most recent message. However, as a result of the target of the thread (YMD) transmitting a message, a speech bubble representing "You're welcome" transmitted by the target of the thread is displayed at the bottom of preview display area 185, and the speech bubbles representing the other displayed messages are shifted up by the amount of the newly displayed speech bubble.

[0117] 9 and 10 have described message exchange (sending and receiving) in app E via the system 1 when the main function screen 18 for app E is displayed (when the app E individual display button 182KE is selected), but message exchange (sending and receiving) in app E via the system 1 when the main function screens 18 for all linked message apps are displayed (when the full display button 182Z is ​​selected) is also performed for the selected thread information icon 183 in the same manner as in Fig. 9 and 10. That is, for a specific message app, message exchange (sending and receiving) via the system 1 can be performed in the same manner by selecting the thread information icon 183 for the same thread when the main function screen 18 for that app is displayed (when the individual display button 182K associated with that app is selected) and when the main function screens 18 for all linked message apps including that app are displayed (when the full display button 182Z is ​​selected).

[0118] Although not described in detail, when the individual display button 182K is selected and the main function screen 18 related to one specific message app is displayed as in the situation shown in Fig. 8(B) and the situations shown in Fig. 8(C) and Fig. 9, and the main function display button 140 is operated, the entire display button 182Z transitions to a selected state, and thread information icons 183 related to all message apps linked to the system 1 (apps E and C in this situation) are displayed. Furthermore, even when the thread information icons 183 related to all message apps linked to the system 1 (apps E and C in this situation) are displayed as in the situation shown in Fig. 8(A), it is assumed that messages can be exchanged and updated in real time for all linked message apps, as exemplified in Figs. 9 and 10.

[0119] 10(B), when the message application list display button 141 is operated, the management server 2 causes the user terminal 3 to switch from the application usage window 1E including the main function screen 18 to the top window 1C. Fig. 11(A) is a diagram showing a specific example of the top window 1C in this case.

[0120] 11(A), a message application list screen 15 is displayed in the right pane 10BR of the top window 1C. However, in this situation, since the system 1 has completed linking with applications C and E, the application C image 16C displays a button for accepting an operation to cancel linking with application C (application C link cancel button 162C), and the application E image 16E displays a button for accepting an operation to cancel linking with application E (application E link cancel button 162E).

[0121] Here, for example, assume that the app E linkage cancellation button 162E is operated. When the app E linkage cancellation button 162E is operated, the user terminal 3 transmits to the management server 2 a command (app E linkage termination request command) indicating a request to terminate linkage with app E, along with the user ID. When the management server 2 receives the app E linkage termination request command, it causes the user terminal 3 to display a window (app linkage termination final confirmation window 19) for prompting the user to make a final confirmation to terminate linkage with the message app. The app linkage termination final confirmation window 19 is displayed superimposed on the message app list screen 15.

[0122] Fig. 11(B) is a diagram showing a specific example of a final confirmation window for ending application collaboration 19. As shown in Fig. 11(B), the final confirmation window for ending application collaboration 19 is formed in a horizontally long rectangular shape, but the specific display content of the final confirmation window for ending application collaboration 19 can be changed as appropriate.

[0123] In addition, the final confirmation window 19 for terminating application integration displays an explanatory message (in FIG. 11(B) , "The tab will be deleted. Are you sure?") for final confirmation of terminating integration with the application, as well as a button for executing the termination of integration (execute integration termination button 191) and a button for canceling the termination of integration (cancel integration termination button 192).

[0124] When the linkage termination cancellation button 192 is operated, the user terminal 3 transmits, together with the user ID, a command (application linkage termination cancellation request command) indicating a request to cancel the termination of linkage with application E to the management server 2. Upon receiving the application linkage termination cancellation request command, the management server 2 causes the user terminal 3 to close the application linkage termination final confirmation window 19.

[0125] On the other hand, when the collaboration termination execution button 191 is operated, the user terminal 3 transmits a command (an application collaboration termination execution request command) indicating a request to terminate collaboration with application E, together with the user ID, to the management server 2. Upon receiving the application collaboration termination execution request command, the management server 2 transmits a command indicating that a request to terminate collaboration has been made, together with user information based on the user ID, to the server 5E of application E. In response, the server 5E of application E terminates collaboration with the system 1 for the user, based on the user information.

[0126] The management server 2 also deletes data related to the user's app E from the server storage unit 23. Furthermore, the management server 2 causes the user terminal 3 to delete the final confirmation window 19 for terminating app linkage, switch the app E linkage cancellation button 162E to the app E linkage operation screen display button 161E, and restore the app E image 16E to its state before linkage. The management server 2 also deletes the app E login button 143E from the right-side pane switching operation screen 14, and appropriately changes the display position of the app C login button 143C that was displayed after it.

[0127] Although a specific example where the app E linkage cancellation button 162E is operated has been described here, linkage is also terminated when the app C linkage cancellation button 162C is operated, just as when the app E linkage cancellation button 162E is operated. This process is also the same for other message apps. In this embodiment, the same final app linkage termination confirmation window 19 is displayed for all message apps. However, the display content of the final app linkage termination confirmation window 19 may be changed depending on the type of message app.

[0128] The system 1 (management server 2) configured as described above is a system capable of centrally managing multiple types of message applications (apps A to H), and includes a linkage management means (linkage management unit 22b) that links a message application to the system 1 (management server 2) in response to a linkage request for the message application from a user terminal 3, and when there are multiple message applications linked to the system by the linkage management means, information about threads (thread information icons 183) related to all linked message applications can be displayed together, provided that the user is logged in to the user terminal 3. This improves the convenience and versatility of integrating and centrally managing multiple message applications. Furthermore, even when a screen other than the main function screen 18 for using a message app in the system 1 (such as the message app list screen 15 or the app login screen 17) is displayed in the right pane 10BR, the main function display button 140 is permanently displayed, and when the main function display button 140 is operated, information about threads (thread information icons 183) related to all linked message apps can be displayed all at once.In other words, the main function screen 18 is displayed with the full display button 182Z selected, further improving convenience and versatility.

[0129] Furthermore, even when information about threads (thread information icon 183) related to all linked message apps can be displayed all at once, as long as the app usage window 1E is displayed, individual display button 182K is constantly displayed, and when individual display button 182K is operated, information about threads (thread information icon 183) related to that message app is displayed, further improving convenience. Conversely, as long as information about a thread (thread information icon 183) related to one of the linked message apps is displayed, whole display button 182Z is ​​constantly displayed, and when whole display button 182Z is ​​operated, information about threads (thread information icon 183) related to all linked message apps can be displayed together, further improving convenience.

[0130] (Modification of the first embodiment) Next, a description will be given of modified examples of the pachinko gaming machine PY1 according to the first embodiment. Note that the modified examples described below can be combined as appropriate.

[0131] In the first embodiment, the whole display button 182Z and the individual display button 182K for switching the display content of information related to threads of linked message apps (thread information icon 183, thread target display area 184, preview display area 185) were permanently displayed in the right pane 10BR of the app usage window 1E, but instead of or in addition to this, the whole display button 182Z and the individual display button 182K, or buttons with equivalent functions, may be permanently displayed not only in the app usage window 1E but also in the left pane 10BL of the top window 1C and the app collaboration window 1D.

[0132] Furthermore, in the first embodiment, when an input operation on the application login screen 17 initiates collaboration between the system 1 and the message application related to the application login screen 17, the right-side pane 10BR switches from the application login screen 17 to the main function screen 18 with the whole display button 182Z selected, but it may also be configured to switch from the application login screen 17 to the main function screen 18 with the individual display button 182K related to the message application selected.

[0133] Furthermore, in the first embodiment, when the main function display button 140 is operated, the main function screen 18 is switched to a state in which the whole display button 182Z is ​​selected, but it may also be switched to a state in which the individual display button 182K related to any of the apps is selected, such as a state in which the individual display button 182K related to the first linked app or a state in which the individual display button 182K related to the last linked app is selected.

[0134] (Second embodiment) Next, a second embodiment of the present invention will be described. Note that the same reference numerals and terms may be used for the same or similarly corresponding components as those in the first embodiment.

[0135] In the second embodiment, the main function display button 140 in the first embodiment is not provided, and unlike the first embodiment, information (thread information icons 183) relating to threads related to multiple types of message applications linked to the system 1 is not displayed together. In the second embodiment, information (thread information icons 183) relating to threads is displayed for each message application, as in the state in which the individual display button 182K in the first embodiment is selected. Furthermore, in the second embodiment, the whole display button 182Z and the individual display button 182K are not provided.

[0136] In the second embodiment, the application usage start window 1A and the user registration window 1B are configured in the same manner as in the first embodiment. Furthermore, for the top window 1C, the application linkage window 1D, and the application usage window 1E, the variable display area 10B is divided into a left pane 10BL and a right pane 10BR, as in the first embodiment. Furthermore, the start screen 11, the user registration screen, the message application list screen 15, and the application login screen 17 are also configured in the same manner as in the first embodiment. That is, the method of user registration and the method of linking with various message applications in the system 1 are configured in the same manner as in the first embodiment.

[0137] As will be described later, in the second embodiment, a screen on which various message apps are used in the system 1, like the main function screen 18 in the first embodiment, is referred to as an "app usage screen 50." The app usage screen 50 is displayed in the right pane 10BR, like the main function screen 18. The app usage screen 50 is a general term for screens on which various message apps are used in the system 1, and is set for each app, like the app login screen 17 in the first embodiment. Therefore, the app usage screen 50 includes app A usage screen 50A for app A to app usage screen 50H for app H.

[0138] Here, for example, if the app E cooperation operation screen display button 161E is operated while the message application list screen 15 is displayed, the app E login screen 17E is displayed in the right pane 10BR, as in the first embodiment, as shown in FIG. 12(A). However, the left pane 10BL displays something that was not displayed in the first embodiment. Specifically, the app E login button 143E is displayed. The app E login button 143E is displayed in response to the operation of the app E cooperation operation screen display button 161E.

[0139] The app E login button 143E has the same function as the app E individual display button 182KE in the first embodiment, and is an operation means for displaying the app usage screen 50 for app E (app E usage screen 50E) in the right-side pane 10BR. Also, like the app E login button 143E, when the app cooperation operation screen display button 161 for another app is operated, the app login button 143 for that app is displayed. In other words, the app login button 143 is a general term for an operation means for displaying the app usage screen 50, and the app login button 143 includes an app A login button 143A for app A to an app G login button 143G for app G.

[0140] The design (shape, pattern, display content) of the app login button 143 can be set as appropriate, but in this embodiment, the app login button 143 is formed in the same size and shape as the message app list display button 141 and the setting screen display button 142, and a logo mark representing the app that was also displayed in the message app image 16 corresponding to the app is displayed inside the button.

[0141] The display position of the application login button 143 can also be set as appropriate, but in this embodiment, the applications are displayed below the setting screen display button 142, from top to bottom in the order in which they were linked.

[0142] When an input operation on the application login screen 17 starts cooperation between the application and the system 1, an operation on the application login button 143 for the application becomes valid. When a screen for a message application other than the application usage screen 50 for the application (application login screen 17, application usage screen 50) is displayed in the right-side pane 10BR, if the application login button 143 for the application is operated, the display content in the right-side pane 10BR is switched to the application usage screen 50 for the application. In other words, an operation on the application login button 143 constitutes a request to log in to (access) the application while using the system 1.

[0143] When the application login button 143 is operated, the user terminal 3 transmits a command (application login request command) indicating a request to log in to the application together with the user ID of the user terminal 3 to the management server 2. Upon receiving the application login request command, the management server 2 requests the server 5 of the application to synchronize the data related to the user, updates the data related to the user (stores the data related to the user held by the server 5 in the server storage unit 23), and causes the user terminal 3 to display the application usage screen 50 reflecting the latest information related to the application.

[0144] In the situation shown in Fig. 12(A), if collaboration with app E is performed by an input operation on app E login screen 17E, app E usage screen 50E is displayed in right pane 10BR. Fig. 12(B) shows a specific example of app usage window 1E including app E usage screen 50E. As shown in Fig. 12(B), app E usage screen 50E is roughly divided into left and right sides. Both the left and right sides are formed as vertically elongated rectangles.

[0145] The left side of the screen 50E for using app E is divided into three sections along the vertical direction. Specifically, a horizontally long rectangular title display area 50E1 is formed at the top end of the left side of the screen 50E for using app E, a horizontally long rectangular thread search area 50E2 is formed directly below the title display area 50E1, and a vertically long rectangular thread information list display area 50E3 is formed directly below the thread search area 50E2.

[0146] The title display area 50E1 displays, as a title, a character string representing the name of the message exchange related to the app E ("Conversation" in this embodiment). The thread search area 50E2 is provided with a search information input field 51 for searching threads. Although a detailed description of the search information input field 51 will be omitted, the search information input field 51 can be used to input information for searching threads, such as keywords, and threads can be searched based on the keywords and the like input into the search information input field 51. In other words, the search information input field 51 has the same function as the search information input field 181 of the first embodiment.

[0147] The thread information list display area 50E3 displays a list of information about a certain number of threads (eight in this embodiment). Information about threads is set for each thread, and information about one thread is made up of an icon 53E (thread information icon 53E) formed in a horizontally long rectangle. As in the first embodiment, the thread information icons 53E are displayed in order from top to bottom in order of most recently updated.

[0148] The display contents inside the thread information icon 53E are configured in the same manner as the thread information icon 183E in the first embodiment. Furthermore, the thread information icon 53E is configured to be able to accept a selection operation, like the thread information icon 183E in the first embodiment. When the app E usage screen 50E is displayed, the thread information icon 53E associated with the most recently updated thread is selected.

[0149] The display content on the right side of the app E usage screen 50E is configured in the same manner as the right side of the main function screen 18 in the first embodiment. For example, when the thread information icon 53E displayed second from the top in the situation shown in Fig. 12(B) is selected, the display content on the right side of the app E usage screen 50E switches from the content corresponding to the thread information icon 53E displayed at the top to the content corresponding to the thread information icon 53E displayed second from the top, as shown in Figs. 12(B) to 12(C).

[0150] Furthermore, when the message application list display button 141 is operated in the situation shown in Fig. 12(C), the right pane 10BR switches from the application E use screen 50E to the message application list screen 15, as shown in Fig. 13(A). Note that, since application E is linked with the system 1 in this case, an application E link cancellation button 162E is displayed on the application E image 16E, similar to the situation in Fig. 7(A) of the first embodiment.

[0151] 13(A), when the message application list display button 141 is operated, and then the application C cooperation operation screen display button 161C is operated, the right-side pane 10BR switches from the message application list screen 15 to the application C login screen 17C, as shown in FIG. 13(B). Furthermore, just as when the application E login screen 17E is displayed, a new application C login button 143C is added. Then, when the system 1 starts cooperation with application C by an input operation on the application C login screen 17C thereafter, the right-side pane 10BR switches from the application C login screen 17C to the application C use screen 50C.

[0152] Explanation of the screen configuration of the app C usage screen 50C will be omitted, but unlike the first embodiment, in the second embodiment, the app usage screen 50 is set appropriately according to the app, and the screen configurations of the app A usage screen 50A to app G usage screen 50G are different from each other.

[0153] Also, for example, when the application C usage screen 50C is displayed in the right pane 10BR, if the application E login button 143E is operated, the right pane 10BR switches from the application C usage screen 50C to the application E usage screen 50E.

[0154] In this way, according to the system 1 of the second embodiment, the app login button 143 for the message app that is permanently linked is displayed in the left pane 10BL. Therefore, when the app usage screen 50 for the message app is not displayed in the right pane 10BR, the app login button 143 for the message app can be operated to instantly display the app usage screen 50 for the message app in the right pane 10BR, and the message app can be used in the system 1.

[0155] The system is provided with a selection screen display means (management server 2 that displays top window 1C, application linkage window 1D, and application usage window 1E on user terminal 3) that displays on user terminal 3 a selection screen (right pane switching operation screen 14) that can accept an operation to select a message application to use from the plurality of message applications, and a usage screen display means (display switching management unit) that displays on the user terminal the usage screen (application usage screen 50) of the message application that corresponds to the message application selected by operation on the selection screen, thereby improving convenience and versatility in integrating and centrally managing multiple message applications.

[0156] Furthermore, when the usage screen for any one of the multiple message applications is displayed on the user terminal 3, a selection screen is displayed, and when the usage screen for a certain message application from the multiple message applications is displayed on the user terminal 3 and another message application from the multiple message applications is selected by operating the selection screen, the selection screen display means switches from the usage screen for the certain message application to the usage screen for the other message application, thereby improving the convenience and versatility of integrating and centrally managing multiple message applications.

[0157] (Other change examples) Furthermore, the first and second embodiments described above are merely examples and do not limit the present invention in any way, and it goes without saying that various improvements and modifications are possible within the scope of the gist of the present invention.

[0158] For example, since the user terminal 3 was configured as a personal computer, the management server 2 displayed the message app unified control system window 10 on the user terminal 3. However, if the user terminal 3 is configured as a smartphone or tablet, the display content of the message app unified control system window 10 may be displayed on the entire screen (display unit) of the smartphone or tablet, rather than being displayed as a window on the smartphone or tablet. Furthermore, in this case, the screen configuration (layout) and design of the message app unified control system window 10 may be adjusted appropriately depending on the shape and size of the smartphone or tablet screen (display unit).

[0159] In the above embodiment, the system 1 is configured to be able to cooperate with eight types of messaging apps, apps A to H, but the types of messaging apps that can be cooperated with may be changed as appropriate. Furthermore, it may be possible to add or delete messaging apps that can be cooperated with as appropriate by performing a predetermined operation on the management server 2.

[0160] Furthermore, in the above-described embodiment, because application login screen 17 is provided by server 5, the screen configuration (layout) of application login screen 17 differs depending on the type of messaging application, but the screen configuration (layout) of application login screen 17 may be standardized. Furthermore, in the first embodiment, the screen configuration (layout) of main function screen 18 in a state in which individual display button 182K is selected is standardized regardless of the type of messaging application, but like application login screen 17, main function screen 18 may be configured to be redirected and provided from server 5 (servers 5A to 5H), and the screen configuration (layout) of main function screen 18 may be configured to differ depending on the type of messaging application.

[0161] Furthermore, in the above-described embodiment, the management server 2 (collaboration management unit 22b) initiates collaboration with apps A to H (servers 5A to 5H) through a process (OAuth2.0) for requesting permission for general authority, but the control content for initiating collaboration with apps A to H (servers 5A to 5H) is not limited to OAuth2.0 and may be changed as appropriate.

[0162] Furthermore, in the second embodiment, right-side pane switching operation screen 14 is permanently displayed, and when user terminal 3 is logged in to system 1 (management server 2), it is possible to switch to another app main screen at any time, but right-side pane switching operation screen 14, message app list display button 141, and app login button 143 are not permanently displayed. For example, when app linkage window 1D and / or app usage window 1E are displayed, operating a certain button may display right-side pane switching operation screen 14, message app list display button 141, and app login button 143. Note that, due to differences in conditions such as screen size, for example, if user terminal 3 is configured as a personal computer, right-side pane switching operation screen 14 may be permanently displayed as in the second embodiment, and if user terminal 3 is configured as a smartphone or tablet, operating a certain button may display right-side pane switching operation screen 14, message app list display button 141, and app login button 143.

[0163] Furthermore, in the above-described embodiment, the server control unit 22 realizes various functions based on various programs and information stored in the server memory unit 23 provided in the management server 2, but the various programs stored in the server memory unit 23 may also be stored in a cloud base connected to the management server 2 via the communication network 4.

[0164] Furthermore, the processes disclosed in the above-described embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. Also, the processes disclosed in the above-described embodiments may be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method.

[0165] The preceding paragraphs of this "Mode for Carrying Out the Invention" disclose the following Inventions A to D. In the explanation of Inventions A to D, the names and expressions of the corresponding components in the above-mentioned modes for carrying out the invention and the symbols used in the drawings are added in parentheses for reference. However, the elements such as the means constituting each invention are not limited to these additions.

[0166] The system according to invention A is A system capable of centrally managing multiple types of message applications, a linkage management unit (linkage management unit 22b) for linking a message application to the system in response to a linkage request from a user terminal; an operation unit display unit (display switching management unit 22c) that displays a top window 1C, an application cooperation window 1D, and an application use window 1E on the user terminal 3) that displays an operation unit (main function display button 140) on the user terminal when there are multiple message applications that are cooperated with the system by the cooperation management unit, on the condition that the user is logged in to the user terminal, to display a specific screen (main function screen 18) that can collectively display information (thread information icon 183) that indicates specific units (threads) related to the exchange of messages for each of the multiple message applications; The system is characterized by comprising a specific screen display means (a display switching management unit 22c that displays the main function screen 18 on the user terminal 3) that displays the specific screen on the user terminal when the operation unit is operated when the specific screen is not displayed on the user terminal (for example, when the top window 1C is displayed).

[0167] The system according to invention B is A system according to Invention A, When the specific screen is displayed on the user terminal, an overall display operation section (overall display button 182Z) capable of accepting an operation for collectively displaying information indicating the specific unit relating to the entire plurality of message applications, and an individual display operation section (individual display buttons 182K: application A individual display button 182KA to application H individual display button 182KH) capable of accepting an operation for displaying information indicating the specific unit for each message application are displayed; the individual display operation unit is displayed in association with each of the plurality of message applications, When the overall display operation unit is operated, information indicating the specific unit relating to all of the plurality of message applications is displayed collectively; When the individual display unit is operated, information indicating the specific unit related to a message application associated with the individual display operation unit is displayed.

[0168] The server according to the invention C is A server capable of centrally managing multiple types of message applications, In response to a request for linking a message application from a user terminal, linking an external device related to the message application with the server; When there are a plurality of external devices related to message applications linked to the server, an operation unit (main function display button 140) capable of accepting an operation for displaying on the user terminal a specific screen (main function screen 18) capable of collectively displaying information (thread information icon 183) indicating specific units (threads) related to the exchange of messages of each of the plurality of message applications is displayed on the user terminal; A server characterized in that the specific screen is displayed on the user terminal by operating the operation unit when the specific screen is not displayed on the user terminal (for example, when the top window 1C is displayed).

[0169] The server according to the invention D is A server according to Invention C, When the specific screen is displayed on the user terminal, an overall display operation section (overall display button 182Z) capable of accepting an operation for collectively displaying information indicating the specific unit relating to the entire plurality of message applications, and an individual display operation section (individual display buttons 182K: application A individual display button 182KA to application H individual display button 182KH) capable of accepting an operation for displaying information indicating the specific unit for each message application are displayed; the individual display operation unit is displayed in association with each of the plurality of message applications, When the overall display operation unit is operated, information indicating the specific unit relating to all of the plurality of message applications is displayed collectively; When the individual display unit is operated, the server displays information indicating the specific unit related to a message application associated with the individual display operation unit. [Explanation of symbols]

[0170] 1. Message app unified management system 2...Administrative server 3...User terminal 4. Communication Network 5...Server 10...Message app centralized management system window 10A… App start window 10B...User registration window 10C…Top window 10D…App link window 10E…Window when using the app 12...User registration screen 14...Right pane switching operation screen 15...Message app list screen 16... Message app image 17...App login screen 18...App function screen 21...Server communication section 22...Server control unit 22a...Authentication Management Department 22b…Collaboration Management Department 22c...Display switching management section 22d...Message information update management section 23...Server storage unit 23b...Database 24a...User information table 24b...Thread information table 50...App main screen 140...Main function display button 141...Message app list display button 143...App login button 161...App link operation screen display button 182Z...Show all button 182K…Individual display button 183...Thread information icon

Claims

1. A system capable of centrally managing multiple types of message applications, a linkage management means for linking the message application to the system in response to a linkage request from a user terminal to the message application; an operation unit display means for displaying, on the user terminal, an operation unit capable of accepting an operation to display a specific screen on the user terminal that can collectively display information indicating specific units related to message exchanges of each of the plurality of message applications, when there are a plurality of message applications that are linked to the system by the link management means, on the condition that the user terminal is logged in; A system characterized by comprising a specific screen display means for displaying the specific screen on the user terminal when the operation unit is operated when the specific screen is not displayed on the user terminal.

2. 10. The system of claim 1, When the specific screen is displayed on the user terminal, an overall display operation unit capable of accepting an operation for collectively displaying information indicating the specific unit relating to all of the plurality of message applications, and an individual display operation unit capable of accepting an operation for displaying the information indicating the specific unit for each of the message applications are displayed; the individual display operation unit is displayed in association with each of the plurality of message applications, When the overall display operation unit is operated, information indicating the specific unit relating to all of the plurality of message applications is displayed collectively; When the individual display operation unit is operated, information indicating the specific unit related to a message application associated with the individual display operation unit is displayed.

3. A server capable of centrally managing multiple types of message applications, In response to a request for linking a message application from a user terminal, linking an external device related to the message application with the server; When there are a plurality of external devices related to message applications linked to the server, an operation unit capable of receiving an operation for displaying a specific screen on the user terminal that can collectively display information indicating specific units related to message exchanges of each of the plurality of message applications is displayed on the user terminal; A server that displays the specific screen on the user terminal by operating the operation unit when the specific screen is not displayed on the user terminal.

4. 4. The server according to claim 3, When the specific screen is displayed on the user terminal, an overall display operation unit capable of accepting an operation for collectively displaying information indicating the specific unit relating to all of the plurality of message applications, and an individual display operation unit capable of accepting an operation for displaying the information indicating the specific unit for each of the message applications are displayed; the individual display operation unit is displayed in association with each of the plurality of message applications, When the overall display operation unit is operated, information indicating the specific unit relating to all of the plurality of message applications is displayed collectively; When the individual display operation unit is operated, the server displays information indicating the specific unit related to a message application associated with the individual display operation unit.

Images