JP7782829B2 - Systems and servers - Google Patents

Description

The present invention relates to a system and server for integrating and centrally managing multiple messaging applications.

Recently, various communication tools have been developed, including email, chat, and messengers. Furthermore, various types of applications (messaging applications) have been developed for each communication tool. However, when a user uses a messaging application to communicate with another user, the user's messaging application may need to match the type of application used by the other user. As a result, some users may need to use different messaging applications depending on the person they are communicating with.

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, to switch messaging applications, you must close the open screen and then operate the icon of the next messaging application you want to use. 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, if you want to send image data received from one person to another, the operation can be cumbersome if each person uses a different messaging application.

Unified message management systems that centrally manage multiple types of messaging applications have been developed (see Patent Document 1). In the unified message management system described in Patent Document 1, when the system is accessed, multiple icons associated with keywords are displayed on the screen first, and when an icon is selected, the screen switches to the screen associated with that icon. The screen displays a list of email messages or chat messages, sorted by subject, that contain the keyword associated with the selected icon. This screen also displays a speech bubble button, and when this button is selected, a new chat message display screen is created within the screen.

Patent No. 5960277

However, the centralized message management system described in Patent Document 1 is primarily intended for use by a single company or organization, and the emails and chats centrally managed by the system are fixed.

The present invention was made in light of the above circumstances. Its objective is to provide a system and server for integrating and centrally managing multiple messaging applications that are highly convenient and versatile.

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.

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.

The system and server according to the present invention for integrating and centrally managing multiple messaging applications can enhance convenience and versatility.

1 is a schematic diagram illustrating the overall configuration of a system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the main functional configuration of a management server that constitutes the system. 2 is a diagram schematically illustrating a table registered in a database provided in a management server that constitutes the system. FIG. FIG. 10 is a diagram illustrating an example of the configuration of a user information table. 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. 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 application E is being used in cooperation with application E. FIG. 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. FIG. 10 is a diagram illustrating a specific example of a window for using an application when linked with application E and application C. FIG. 10 is a diagram illustrating a specific example of a window for using an application when linked with application E and application C. FIG. 10 is a diagram illustrating a specific example of a window for using an application when linked with application E and application C. (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. 10A is a diagram showing a specific example of an application cooperation window for application E, and FIGS. 10B and 10C are diagrams showing specific examples of an application use window when application E is cooperated with. 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.

(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 used, the number and format thereof are not limited. Furthermore, data stored in a storage medium in a so-called table format are also included in the "information" and "data" referred to here.

(Overall configuration of message 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. 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.

Email, messenger, and chat are set as types of multiple message apps (communication methods) that can be centrally managed by the message app unified management system 1. Note that some SNS (Social Networking Services) such as Twitter and Instagram also allow for the exchange of messages, so SNS with such functionality are also considered to be included in message apps. Furthermore, email and webmail are included in mail.

The message app unified management system 1 can also centrally manage multiple message apps that use the same communication method but are of different types (display formats and layouts), as well as multiple message apps that use different communication formats, such as email applications and messenger applications. As will be described in more detail below, 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.

In the following, the message app unified management system 1 may also be referred to simply as "system 1." In addition, in this embodiment, it is assumed that eight existing message apps, message app A to message app H, are set as message apps that can be centrally managed by system 1. In the following, the various message apps may also be referred to simply as "apps."

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 communications network 4 so that they can send and receive information (data) to each other. Communications network 4 may be composed of, for example, the Internet, a LAN, a telephone line, a mobile communications network, Wi-Fi (Wireless Fidelity) (registered trademark), other communications lines, or a combination of these, and may be wired or wireless.

Furthermore, management server 2 and user terminal 3 are connected via communication network 4 to server 5A, which manages app A, which can be centrally managed by system 1, so that they can send and receive information (data) to and from each other. Similarly, management server 2 and user terminal 3 are connected via communication network 4 to servers 5B to 5H, which manage apps B to H, so that they can send and receive information (data) to and from each other. However, servers 5A to 5H are not included in system 1. In other words, servers 5A to 5H do not constitute system 1. Note that, hereinafter, servers 5A to 5H may be collectively referred to as "server 5."

Management server 2 is composed of a general information processing device, and although not shown, it is equipped with 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, management server 2 may be composed of a single information processing device (one physical computer), or may be configured so that multiple information processing devices (multiple physical computers) work together to perform its functions (it may also be configured in a cloud environment). Details of management server 2 will be provided below.

While a block diagram showing the configuration of the user terminal 3 is omitted, the user terminal 3 is configured as a typical communications terminal and includes a CPU for overall control, RAM that functions as the CPU's work area, 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 transmitter/receiver unit that communicates with external devices. Specifically, the user terminal 3 can be a smartphone, tablet, laptop computer, PDA (Personal Digital Assistant), or desktop computer. In this embodiment, the user terminal 3 is configured as a laptop computer.

(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 provides a service for centrally managing apps A to H by mutually sending and receiving information (data) with the user terminal 3 and the server 5.

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

The server storage unit 23 is composed of a storage device such as a semiconductor memory or disk drive provided by the storage area of a physical device consisting of a computer-readable recording medium. Furthermore, the server storage unit 23 stores various programs, including operating system programs and driver programs, as well as various data used during the execution of these programs.

The server storage unit 23 also stores a management program 23a that is executed by the server control unit 22, which will be described later. Furthermore, 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.

Database 23b has multiple tables. Figure 3 is a diagram showing a schematic representation of the multiple tables registered in database 23b. These tables include 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 that described below and may be modified as appropriate.

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

Figure 4 shows an example of the configuration of the user information table 24a. As shown in Figure 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 entering an email address and password.

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

Thread information table 24b associates a user ID, the type of message application in which the thread is deployed, and a thread ID, which 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.

Next, we will explain the server control unit 22. The server control unit 22 is a processor, i.e., a processing device that performs data calculations, processing, and transfers, executes programs, and controls other devices, and is composed of a CPU and various registers.

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 servers 5A-5H to realize the centralized management function of various messaging apps.

The following describes each functional block realized by the server control unit 22. As shown in Figure 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 unit 22a-22d corresponds to a function that the server control unit 22 can realize. Note that the configuration of each unit 22a-22d corresponding to the function of the server control unit 22 is not limited to this; these units 22a-22d may be integrated as appropriate, and each unit 22a-22d may be further subdivided as appropriate.

When accessed from a user terminal 3, the authentication management unit 22a checks the user ID to log in. As described below, when a user is registered, a user ID is assigned to the accessing user terminal 3 (user), and when accessed from that user terminal 3 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 then determines whether the user ID is registered with the management server 2. If the user ID is registered, the authentication management unit 22a logs in the user terminal 3 and displays the top window 1C described below. On the other hand, if the user is not registered, an error message indicating that login has failed is displayed on the user terminal 3 (not shown).

Furthermore, when accessed from a user terminal 3, if the user ID is not included, the authentication management unit 22a causes the user terminal 3 to display a screen (user registration screen 12, described below) on which the email address and password can be entered. Then, when an email address and password are sent to the management server 2 through a predetermined operation on the user terminal 3, the authentication management unit 22a issues a user ID for the email address and password as appropriate, and stores (memorizes) 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.

The collaboration management unit 22b is capable of performing processing to initiate collaboration with servers 5A to 5H, which are positioned as external devices to the system 1. Although some of the details will be omitted below, when the collaboration management unit 22b receives a request from the user terminal 3 to initiate collaboration with apps A to H (servers 5A to 5H), it performs processing (OAuth 2.0) to request general authorization.

When a type of message app requesting the start of collaboration is sent to the management server 2 through a predetermined operation on the user terminal 3, the collaboration management unit 22b displays (redirects) a login screen for that message app (app login screen 17, described below) on the user terminal 3. Then, when a login operation for that message app is performed on the user terminal 3, the collaboration management unit 22b accesses the server 5 for that message app to request collaboration permission. Here, the server 5 makes a decision on whether to allow collaboration, 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 (registering information about the user related to the message app that is the target of the collaboration).

The collaboration management unit 22b can also perform processing to terminate collaboration with servers 5A-5H. Specifically, when a type of message app requesting termination of collaboration is sent to the management server 2 through a predetermined operation on the user terminal 3, the collaboration management unit 22b displays a screen on the user terminal 3 for final confirmation of terminating collaboration with the message app (a final confirmation window 19 for terminating app collaboration, described below). While this screen is displayed, the user terminal 3 can be operated to approve the termination of collaboration, and when this approval operation is performed, the collaboration management unit 22b requests the server 5 related to that message app to terminate collaboration. In response, the server 5 terminates collaboration with system 1. Furthermore, the collaboration management unit 22b erases information related to that message app for that user from database 23b.

When the user terminal 3 is logged in to system 1, the display switching management unit 22c changes the display content of the screen related to system 1 displayed on the user terminal 3 through a predetermined operation on the user terminal 3. Furthermore, as will be described in detail below, this predetermined operation can be performed at the player's discretion, and this predetermined operation allows the player to easily switch the message app to be used while the screen related to system 1 (the message app unified management system window 10 described below) is displayed (while the software related to system 1 is open).

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 (e.g., every minute) to obtain the latest data related to messages for each user ID and perform processing to update each thread information table 24b. In addition, when information related to a message app is displayed on the main function screen 18 (described below), the information related to that message app is updated in real time.

Next, we will explain a specific example of a user using System 1 using a user terminal 3. It is assumed that the user has installed software (programs) for using System 1 on their user terminal 3, for example by downloading them from a specific site. When the software related to System 1 is installed on the user terminal 3, the user terminal 3 itself functions as a local server for System 1. After installation, browsing on the user terminal 3 performs various processes related to 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 specific input operations are performed using the mouse and keyboard.

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

Window 10 is composed of a fixed display area 10A formed in a strip at the top and a variable display area 10B formed in a rectangular shape directly below it, which can take up most of the window. Details will be described later, but even if the status related to system 1 subsequently changes, fixed display area 10A will continue to be displayed as is as long as the user terminal 3 is connected to system 1 (as long as software related to system 1 is open). Meanwhile, the content displayed in variable display area 10B (functions available on system 1) changes in response to the various changes in the status related to system 1.

Figure 5(A) shows a specific example of an app usage start window 1A. As shown in Figure 5(A), the app usage start window 1A is divided into a fixed display area 10A, which is a strip-shaped area at the top, and a variable display area 10B, which is rectangular and occupies most of the app usage start window 1A, directly below it. As will be described later, the fixed display area 10A is shared by the app usage start window 1A, user registration window 1B, top window 1C, app linkage window 1D, and app usage window 1E, and the content displayed in fixed display area 10A does not change. On the other hand, the content displayed in variable display area 10B differs between the app usage start window 1A, user registration window 1B, top window 1C, app linkage window 1D, and app usage window 1E.

The fixed display area 10A is composed of a so-called "title bar." For example, the name of the system 1 ("◯△□▽" in Figure 5(A)) is displayed on the left edge of the fixed display area 10A. Furthermore, the variable display area 10B of the app usage start window 1A displays a start screen 11 corresponding to the app usage start window 1A. The start screen 11 displays a start button 111 for fully commencing use of the system 1, in other words, for user registration. Operating the start button 111 switches from the app usage start window 1A to a user registration window 1B for user registration for the system 1.

Figure 5 (B) shows a specific example of the user registration window 1B. As shown in Figure 5 (B), the user registration window 1B, like the app usage start window 1A, is divided into a fixed display area 10A and a variable display area 10B. Similarly to the app usage start window 1A, the fixed display area 10A forms a title bar. Meanwhile, the variable display area 10B displays a user registration screen 12 for user registration (new registration) related to the system 1. In other words, when the start button 111 is operated, the content displayed in the variable display area 10B essentially switches from the start screen 11 to the user registration screen 12.

The user registration screen 12 is configured to allow entry of user registration information. In this embodiment, the user registration information consists of an email address and a password. Accordingly, the user registration screen 12 includes an email address input field 121 for entering an email address and a password input field 122 for entering a password. The method of entering an email address into the email address input field 121 and the method of entering a password into the password input field 122 can be configured 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 appears there and becomes available for input using a keyboard (not shown). The email address and password are entered into the email address input field 121 and the password input field 122 in response to keyboard operation. Note that if the user terminal 3 is configured as a smartphone or tablet, for example, when the email address input field 121 or the password input field 122 is tapped, a cursor may appear there and a predetermined software keyboard (not shown) may be superimposed on the user registration screen 12. An email address and password may then be entered into the email address input field 121 and password input field 122 by operating a specified software keyboard.

The user registration screen 12 also has a registration execution button 123 for executing user registration, in other words, for requesting user registration from the management server 2. When the registration execution button 123 is operated, the information entered in the email address input field 121 (email address) and the information entered in the password input field 122 (password) are associated with each other and sent to the management server 2. This 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.

When the management server 2 receives the user registration request command and user registration information, it registers the user registration information (performs user registration) by storing the user registration information in the user information table 24a. In detail, when the management server 2 receives the user registration request, it 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, after 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 the starting window (screen) for the user who has registered the user, and thereafter, when the software related to the system 1 is started while it is not running, the top window 1C is displayed. However, as described below, the display content of the top window 1C varies depending on the situation.

Figure 5(C) shows a specific example of a top window 1C that is displayed upon completion of user registration. As shown in Figure 5(C), the top window 1C has a fixed display area 10A that forms a title bar, similar to the app usage start window 1A and user registration window 1B. However, unlike the app usage start window 1A and 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 app login screen 17 or a main function screen 18 of various messaging apps 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 app linkage window 1D, and the app usage window 1E, but the content displayed in the right pane 10BR differs between the top window 1C, the app linkage window 1D, and the app usage window 1E.

The left pane 10BL of 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 of the top window 1C displays a message app list screen 15 that displays a list of message apps that can be linked to the system 1. The left pane 10BL is formed in a vertically long rectangular shape at the left end of the variable display area 10B, and the right pane 10BR is formed in a horizontally long rectangular shape over 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.

The right-side pane switching operation screen 14 displays, arranged vertically, 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 app list display button 141 that can accept an operation to display the message app list screen 15 in the right-side pane 10BR, and a settings screen display button 142 that can accept an operation to display a screen for making various settings in the right-side pane 10BR.

The main function display button 140 is used when the right pane 10BR displays the message app list screen 15, the app login screen 17 for various message apps described below, or a screen for making various settings (not shown) 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 operation of the main function display button 140 is disabled when the system 1 is not linked to any message apps.

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 you want to switch to the message app list screen 15 when the main function screen 18, the app login screen 17 for various message apps, or a screen for making various settings (not shown) is displayed in the right pane 10BR. When the message app list display button 141 is operated, the message app list screen 15 is displayed in the right pane 10BR.

In addition, although not shown here, when the settings screen display button 142 is operated while the main function screen 18, message app list screen 15, or app login screen 17 related to various message apps is displayed in the right pane 10BR, a screen for making various settings is displayed in the right pane 10BR. Although not explained here, the screen for making various settings is configured to be able to accept operations for setting various items.

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

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

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

When the app A collaboration operation screen display button 161A is operated, a command requesting the start of collaboration with app A (app A collaboration start request command) is sent to the management server 2 along with the user ID. When the management server 2 receives the app A collaboration start request command, it displays a login screen for app A on the user terminal 3 (it redirects to app A and displays the login screen for app A on the user terminal 3). In other words, the management server 2 switches from the top window 1C to the app collaboration window 1D including the login screen for app A.

Furthermore, just as when the app A cooperation operation screen display button 161A is operated, when the app B cooperation operation screen display button 161B through app H cooperation operation screen display button 161H are operated, commands requesting the start of cooperation with apps B through H (app B cooperation start request command through app H cooperation start request command) are sent to the management server 2 along with the user ID. When the management server 2 receives the app B cooperation start request command through app H cooperation start request command, it causes the user terminal 3 to display the login screens for apps B through H (redirects to apps B through H and causes the login screens for apps 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 app cooperation window 1D including the login screens for apps B through H.

Note that since these are login screens for apps A to H, it is assumed that the user has already been registered for apps A to H. Furthermore, hereinafter, 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."

Furthermore, in this embodiment, in order to link the system 1 with apps A to H, the management server 2 switches from the top window 1C to the app linking window 1D and displays the app login screen 17 for the app on the user terminal 3. However, since the app login screen 17 is displayed by redirection, the app A login screen 17A to app H login screen 17H are provided by apps A to H (servers 5A to H). Therefore, the display content (screen configuration, layout, or type) of the app A login screen 17A to app H login screen 17H differs depending on the type of messaging app.

The user terminal 3 displays the app login screen 17 in the right pane 10BR. Here, it is assumed that the app E linkage operation screen display button 161E is operated in the situation shown in Figure 5 (C). This causes the app E login screen 17E to be displayed in the right pane 10BR of the variable display area 10B in the app linkage window 1D.

Figure 6 (A) shows a specific example of an app linking window 1D including an app E login screen 17E. As shown in Figure 6 (A), the app E login screen 17E has an email address input field 171E for entering an email address and a password input field 172E for entering 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.

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

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 the user terminal 3 is operated, the user terminal 3 associates this information (app E login information) with each other and transmits it to app E's server 5E.

When the app E server 5E receives the app E login information sent from the user terminal 3, it determines whether the user is registered with app E, and if the user is registered, it grants permission for collaboration to the system 1 via the user terminal 3. If collaboration is granted, the management server 2 ultimately accesses the app E server 5E to obtain data related to the user, and stores the data in the server storage unit 23 in association with the user ID of the user. In other words, the app E server 5E provides the data related to the user to the system 1. This initiates collaboration between app E and system 1.

The content of the data provided by app E depends on the messaging app, but it will at least include 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. Message-based data includes the date and time the message was sent, the sender, and the specific content of the message (text, image, audio), which are all associated with each other. Note that below, message-based data consisting of the date and time the message was sent, the sender, and the specific content of the message, which are all associated with each other, will be referred to as "message data." Thread-based information containing one or more message data will be referred to as "thread data."

As mentioned above, the server storage unit 23 stores thread information tables 24b for each thread, so the management server 2 generates a thread information table 24b that associates the user ID of the user and app E based on the thread data acquired from server 5E.

Furthermore, when the management server 2 receives permission for collaboration from app E and generates a thread information table 24b associating the user ID with app E, it causes the user terminal 3 to display, in the right-hand pane 10BR, a main function screen 18 in which app E can 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.

Let's return to the explanation of the app linkage window 1D, which includes the app E login screen 17E. As shown in FIG. 6(A), the app E login screen 17E is displayed in the right pane 10BR of the app linkage window 1D, but the variable display area 10B of the app linkage window 1D is divided into a left pane 10BL and a right pane 10BR, just like the top window 1C. And, just like the top window 1C, the right pane switching operation screen 14 is displayed in the left pane 10BL.

On the right-side pane switching operation screen 14 of the application linking window 1D, the main function display button 140, message application list display button 141, and settings screen display button 142 are displayed in the same positions as in the top window 1C.

Next, we will explain the main function screen 18. Figure 6 (B) shows a specific example of an app usage window 1E that includes the main function screen 18. As shown in Figure 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 then further divided into a left and right side. Both the left and right sides are formed as vertically long rectangles.

The left side of the main function screen 18 is functionally divided into three sections 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 display 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 display application switching operation area 18B.

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 entered in the search input field 181, and threads can be searched for based on the keywords entered in the search information input field 181.

The display app switching operation area 18B displays buttons (display content specification buttons) 182 for specifying the display content of the thread information list display area 181C. The display content specification buttons 182 include an all display button 182Z, which displays information about threads in all message apps linked to the system 1, and an individual display button 182K, which displays information about threads in one of the message apps linked to the system 1.

An individual display button 182K is set for each message app, and the individual display buttons 182K include app A individual display buttons 182KA to app H individual display buttons 182KH, which are associated with message apps A to H, respectively.

If there is at least one message app linked with the system 1, the full display button 182Z is displayed, and also the individual display button 182K associated with the currently linked message app. Note that Figure 6(B) shows the situation immediately after the system 1 is first linked with message app E, so Figure 6(B) displays the full 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 full display button 182Z is displayed at the left end of the display app switching operation area 18B, and to its right, the individual display buttons 182K are displayed in the order in which they were linked, from left to right.

Furthermore, 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 switching to the main function screen 18, the whole display button 182Z is assumed to be in a selected state.

The thread information list display area 181C displays a list of information about a certain number of threads (six in this embodiment). Thread information is set on a thread-by-thread basis, and information about one thread is made up of a horizontally elongated rectangular icon (thread information icon) 183. All thread information icons 183 are the same size and shape, and are displayed in order from top to bottom in the order in which the thread was updated.

At the left end of the thread information icon 183, a circular image is displayed representing participants (parties) of the thread corresponding to that thread information icon 183 other than the user. If the thread is formed between the user and one other person, a circular image representing that 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 circular images of the remaining people are displayed partially offset from the central circular image and in the background.

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

The upper part of the center of the thread information icon 183, excluding both ends, displays the name of the other person in the thread if the thread is formed by two people including the user, or the name of the group if the thread is formed by a group. The lower part of the center of the thread information icon 183, excluding both ends, displays content according to the message app. 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 beginning of the most recent message (in this embodiment, 12 characters: the most recent abbreviated message) and its sender are displayed.

The thread information icons 183 are also configured to be able to accept selection operations, 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 one to which a message was sent), is assumed to be selected.

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.

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 on the left edge of the thread target display area 184, and a character string representing the thread target (individual name or group name: in Figure 6 (B) the group name "XX Company Sales Department") is displayed to the right of the circular image. In other words, information other than the latest simplified message in the thread information icon 183 is displayed in the thread target display area 184.

The preview display area 185 displays the message exchange. The most recently sent message is displayed at the bottom of the preview display area 185, and messages exchanged from there are displayed chronologically from top to bottom. The message display format 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.

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

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

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 for all linked message apps are displayed together or whether the thread information icon 183 for a 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).

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

Figure 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 app list display button 141 in the situation shown in Figure 6 (B). As mentioned above, since system 1 is currently linked to app E, there is no need to newly link system 1 to app E. Therefore, as shown in Figure 7 (A), the app E image 16E displayed on the message app list screen 15 in a situation where linkage with app E is established is provided with a button that can accept an operation to cancel linkage with app E (app E linkage cancellation button 162E) instead of the app E linkage operation screen display button 161E. The operation of system 1 when the app E linkage cancellation button 162E is operated will be described later.

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

The app C login screen 17C includes an email address/phone number input field 171C for entering an email address or phone number, and a password input field 172C for entering a password. In other words, in this embodiment, the email address or phone number and the password constitute the information required to log in to app C. The app C login screen 17C also includes a login button 173C for executing the login.

When the login button 173C is operated, the user terminal 3 sends the email address or phone number as authentication information and the password (app C login information) to the app C server 5C, just as if the app E login screen 17E were displayed.

When the app C server 5C receives the app C login information sent from the user terminal 3, it determines whether the user is registered with app C, and if the user is registered, it grants permission for collaboration to the system 1 via the user terminal 3. If collaboration is permitted, as when collaboration with app E is initiated, the management server 2 ultimately accesses the app C server 5C to obtain data related to the user, and stores the data in the server storage unit 23 in association with the user ID of the user. In other words, 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, the management server 2 switches from the app C login screen 17C to the main function screen 18 in response to the start of collaboration with app C.

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

In addition, Figure 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 to the system 1 (in this situation, apps E and C).

The thread information icon 183 related to app C is a thread information icon 183 with the letter "C" representing app C displayed on the right edge. Therefore, in the situation shown in FIG. 8 (A), from top to bottom, the thread information icon 183 related to app C, the thread information icon 183 related to app C, the thread information icon 183 related to app E, the thread information icon 183 related to app E, the thread information icon 183 related to app C, and the thread information icon 183 related to app E are displayed.

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

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

When the app C individual display button 182KC is selected, the user terminal 3 sends the user ID and a command (app C main function screen display request command) indicating a request to display the main function screen 18 related to app C (dedicated to app C) to the management server 2. When the management server 2 receives the app C main function screen display request command, it causes the user terminal 3 to display the main function screen 18 related to app C (dedicated to app C).

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

Also, suppose that the app E individual display button 182KE associated with app E is operated in the situation shown in FIG. 8(A) or the situation shown in FIG. 8(B). 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 preview display area 185 displays the message exchange for the most recently updated thread related to app E. 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).

When the app E individual display button 182KE is selected, the user terminal 3 sends the user ID and a command (app E main function screen display request command) indicating a request to display the main function screen 18 for app E (dedicated to app E) to the management server 2. When the management server 2 receives the app E main function screen display request command, it causes the user terminal 3 to display the main function screen 18 for app E (dedicated to app E).

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

Note that 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 for the currently linked apps E and C, as shown in FIG. 8(A), is displayed.

Furthermore, as mentioned 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 a thread information icon 183 is selected, 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 of selecting a thread information icon 183 constitutes a request to display detailed information about the thread corresponding to that thread information icon 183.

When an operation to select a 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 transmits them to the management server 2, and also transmits a command (thread detailed information display request command) indicating a request to display thread detailed information to the management server 2.

When the management server 2 receives a thread detail information display request command, it accesses the server 5 of the app related to that thread, acquires data related to that thread, and then updates the data related to that thread (thread information table 24b) in the data related to the app related to that user in the server storage unit 23. Then, in accordance with that data, it switches the display content of the thread target display area 184 and the display content of the preview display area 185 to that related to that thread.

For example, in the situation shown in FIG. 8(C), when the thread information icon 183 relating to the second-from-the-top app E 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 FIG. 9(A).

Here, we will explain the exchange (sending and receiving) of messages in app E via system 1. For example, in the situation shown in Figure 9(A), if the text "Thank you" is entered into message input field 186A, the result will be as shown in Figure 9(B). In this situation, when send button 186B is operated, the user terminal 3 associates the content entered into message input field 186A (text: Thank you) with the user ID of the user terminal 3, the target of the thread displayed in thread target display area 184, and the type of message app (app E), and transmits it to the management server 2. Note that the information transmitted to the management server 2, specifically the content entered into 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 "sent message information."

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 app E associated with the user ID included in the sent message information, which includes the target of the thread, the message content is newly stored in association with the current date and time and the user as the sender. The management server 2 also transmits the sent message information to the server 5E for app E. This allows the server 5E for app E to also update the data related to the thread consisting of the user and the target of the thread.

Furthermore, when management server 2 receives the sent message information, it updates the preview display area 185 to reflect the sent message information. 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) is displayed at the bottom of preview display area 185, and that message is the most recent message. However, when send button 186B is operated, a speech bubble representing "Thank you" sent by that user is displayed at the bottom of preview display area 185, as shown in Figure 10(A), and the speech bubbles representing the other displayed messages are shifted up to accommodate the newly displayed speech bubble.

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 ("YMD" in FIG. 10(A)) sends a message to the user related to the user terminal 3 using app E (if the message is sent to app E's server 5E), app E's server 5E first transmits to the management server 2 the sender of the message ("YMD" in FIG. 10(A)), the message destination (the user related to the user terminal 3), the message content, and the date and time the message was sent.

When the management server 2 receives information transmitted from the server 5E of app E, it updates the server storage unit 23 to reflect that information. Specifically, it compares the information indicating the message destination contained in the information transmitted from the server 5E of app E with the user information table 24a to identify the user ID, and stores the message content in association with the date and time and the sender of the message as the originator in the thread information table 24b for the thread formed between the target of the thread and the app E associated with that user ID.

Furthermore, when management server 2 receives information transmitted from server 5E of app E, it updates preview display area 185 to reflect that information. Let's assume that the transmitted message is the text "You're welcome." As shown in FIGS. 10(A) and 10(B), until the target of the thread (YMD) transmitted a message, the message "Thank you." transmitted by that user was displayed at the bottom of preview display area 185, making that message the most recent message. However, once the target of the thread (YMD) transmitted 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 size of the newly displayed speech bubble.

9 and 10 have described message exchange (sending and receiving) for app E via system 1 when the main function screen 18 for app E is displayed (when the app E individual display button 182KE is selected). However, message exchange (sending and receiving) for app E via 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 FIGS. 9 and 10. That is, for a specific message app, message exchange (sending and receiving) via 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).

In addition, although details will not be explained, when the individual display button 182K is selected and the main function screen 18 for a 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 for all message apps linked to the system 1 (in this situation, app E and app C) are displayed. Furthermore, even when thread information icons 183 for all message apps linked to the system 1 (in this situation, app E and app C) are displayed, as in the situation shown in FIG. 8(A), it is possible to exchange messages in real time and update messages for all linked message apps, as illustrated in FIG. 9 and FIG. 10.

Furthermore, in the situation shown in FIG. 10(B), when the message app list display button 141 is operated, the management server 2 causes the user terminal 3 to switch from the app usage window 1E, which includes 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.

As shown in FIG. 11(A), the message app 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 apps C and E, the app C image 16C displays a button for accepting an operation to cancel linking with app C (app C link cancellation button 162C), and the app E image 16E displays a button for accepting an operation to cancel linking with app E (app E link cancellation button 162E).

Here, for example, suppose the app E linkage cancellation button 162E is operated. When the app E linkage cancellation button 162E is operated, the user terminal 3 sends 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 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.

Figure 11 (B) is a diagram showing a specific example in which the final confirmation window 19 for terminating app integration is displayed. As shown in Figure 11 (B), the final confirmation window 19 for terminating app integration is formed in a horizontally long rectangle, but the specific display content of the final confirmation window 19 for terminating app integration can be changed as appropriate.

The final confirmation window 19 for terminating app integration also displays an explanatory message (in Figure 11 (B) it reads, "The tab will be deleted. Are you sure?") for final confirmation that you want to terminate integration with the app, 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).

When the link termination cancellation button 192 is operated, the user terminal 3 sends the user ID and a command (app link termination cancellation request command) indicating a request to cancel the termination of linkage with app E to the management server 2. When the management server 2 receives the app link termination cancellation request command, it causes the user terminal 3 to close the app link termination final confirmation window 19.

On the other hand, when the link termination execution button 191 is operated, the user terminal 3 sends the user ID and a command (app link termination execution request command) indicating a request to terminate linkage with app E to the management server 2. When the management server 2 receives the app link termination execution request command, it sends a command indicating that a request to terminate linkage has been made to the app E server 5E along with user information based on the user ID. The app E server 5E then terminates linkage with the system 1 for the user based on the user information.

The management server 2 also erases data related to app E of the user in the server storage unit 23. Furthermore, the management server 2 causes the user terminal 3 to erase the final confirmation window 19 for terminating app integration, and switches the app E integration cancellation button 162E to the app E integration operation screen display button 161E, restoring the app E image 16E to its state before integration. The management server 2 also erases 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, which was displayed after it.

Note that while a specific example where the app E linkage cancellation button 162E is operated has been described here, linkage also ends 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 similar for other message apps. Note that 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.

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 system 1 (management server 2) in response to a linkage request for the message application from a user terminal 3. When there are multiple message applications linked to the system by the linkage management means, information about threads related to all linked message applications (thread information icon 183) can be displayed all at once, 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 message apps on the system 1 (such as the message app list screen 15 or app login screen 17) is displayed in the right pane 10BR, the main function display button 140 is constantly 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.

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

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

In the first embodiment, the right-hand pane 10BR of the app usage window 1E permanently displayed an entire display button 182Z and an individual display button 182K for switching the display content of information related to threads of linked messaging apps (thread information icon 183, thread target display area 184, preview display area 185). However, instead of or in addition to this, the entire display button 182Z and 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-hand pane 10BL of the top window 1C and the app usage window 1D.

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

Furthermore, in the first embodiment, when the main function display button 140 is operated, the main function screen 18 switches to a state in which the whole display button 182Z is selected. However, it may also be configured to switch to a state in which the main function screen 18 switches to a state in which the individual display button 182K for one of the apps is selected, such as a state in which the individual display button 182K for the first linked app or a state in which the individual display button 182K for the last linked app is selected.

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.

In the second embodiment, the main function display button 140 present in the first embodiment is not provided, and information (thread information icons 183) relating to threads related to multiple types of message apps linked to the system 1 is not displayed together as in the first embodiment. In the second embodiment, information (thread information icons 183) relating to threads is displayed on a message app basis, just as in the state when the individual display button 182K in the first embodiment is selected. Furthermore, in the second embodiment, the full display button 182Z and the individual display button 182K are not provided.

In the second embodiment, the app usage start window 1A and the user registration window 1B are configured in the same way as in the first embodiment. Furthermore, for the top window 1C, app linkage window 1D, and app usage window 1E, the variable display area 10B is divided into a left pane 10BL and a right pane 10BR, just as in the first embodiment. Furthermore, the start screen 11, user registration screen, message app list screen 15, and app login screen 17 are also configured in the same way as in the first embodiment. In other words, the user registration method and linkage method with various message apps related to the system 1 are configured in the same way as in the first embodiment.

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 also 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.

Here, for example, if the app E linked operation screen display button 161E is operated while the message app 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 linked operation screen display button 161E.

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-hand pane 10BR. Also, like the app E login button 143E, when the app linkage 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 buttons 143 include the app A login button 143A for app A through the app G login button 143G for app G.

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 settings screen display button 142, and displays inside it the logo mark representing the app that was also displayed in the message app image 16 corresponding to that app.

The display position of the app login button 143 can also be set as appropriate, but in this embodiment, the apps are displayed below the settings screen display button 142, from top to bottom in the order in which they were linked.

When an input operation on the app login screen 17 initiates collaboration between the app and system 1, operation of the app login button 143 for the app becomes valid. When a screen for a messaging app other than the app usage screen 50 for the app (app login screen 17, app usage screen 50) is displayed in the right-hand pane 10BR and the app login button 143 for the app is operated, the display content in the right-hand pane 10BR is switched to the app usage screen 50 for the app. In other words, operation of the app login button 143 constitutes a request to log in (access) to the app while using system 1.

When the app login button 143 is operated, the user terminal 3 sends a command (app login request command) indicating a request to log in to the app, along with the user ID associated with that user terminal 3, to the management server 2. Upon receiving the app login request command, the management server 2 requests the server 5 of that app to synchronize 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 an app usage screen 50 reflecting the latest information related to the app.

In the situation shown in Figure 12(A), if collaboration with app E is established by inputting an operation into the app E login screen 17E, the app E usage screen 50E will be displayed in the right pane 10BR. Figure 12(B) shows a specific example of the app usage window 1E including the app E usage screen 50E. As shown in Figure 12(B), the 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.

The left side of the App E usage screen 50E is divided into three sections vertically. Specifically, a horizontally long rectangular title display area 50E1 is formed at the top of the left side of the App E usage screen 50E, 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.

The title display area 50E1 displays a character string representing the name of the message exchange related to app E (in this embodiment, "Conversation") as the title. The thread search area 50E2 has a search information input field 51 for searching threads. A detailed description of the search information input field 51 will be omitted, but 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 entered in 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 in the first embodiment.

The thread information list display area 50E3 displays a list of information about a certain number of threads (eight in this embodiment). Thread information is set on a thread-by-thread basis, and information about one thread is composed of a horizontally long rectangular icon 53E (thread information icon 53E). As in the first embodiment, the thread information icons 53E are displayed in order of most recently updated, from top to bottom.

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

The display content on the right side of the app E usage screen 50E is configured in the same way 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 topmost thread information icon 53E to the content corresponding to the second most thread information icon 53E, as shown in FIGS. 12(B) to 12(C).

Furthermore, when the message app list display button 141 is operated in the situation shown in FIG. 12(C), the right pane 10BR switches from the app E usage screen 50E to the message app list screen 15, as shown in FIG. 13(A). Note that in this case, since app E is linked with system 1, the app E image 16E displays the app E link release button 162E, similar to the situation in FIG. 7(A) in the first embodiment.

When the message app list display button 141 is operated in the situation shown in FIG. 13(A), operating the app C collaboration operation screen display button 161C causes the right-hand pane 10BR to switch from the message app list screen 15 to the app C login screen 17C, as shown in FIG. 13(B). Furthermore, a new app C login button 143C is added, just as when the app E login screen 17E is displayed. Then, when the system 1 starts collaboration with app C by subsequently operating the app C login screen 17C, the right-hand pane 10BR switches from the app C login screen 17C to the app C usage screen 50C.

We will not explain the screen configuration of the app C usage screen 50C, but unlike the first embodiment, in the second embodiment, the app usage screen 50 is set appropriately depending on the app, and the screen configurations of the app A usage screen 50A to app G usage screen 50G are different from each other.

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

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

The system is equipped with a selection screen display means (management server 2 that displays top window 1C, app linkage window 1D, and app usage window 1E on the user terminal 3) that displays a selection screen (right-side pane switching operation screen 14) on the user terminal 3 that can accept an operation to select a message application to use from the multiple message applications, and a usage screen display means (display switching management unit) that displays on the user terminal the usage screen (app 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 when integrating and centrally managing multiple message applications.

In addition, when the usage screen for any of the multiple message applications is displayed on the user terminal 3, a selection screen is displayed. 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.

(Other examples of changes)
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.

For example, since the user terminal 3 was configured as a personal computer, the management server 2 displayed the message app unified management 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 management 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 management system window 10 may be adjusted appropriately depending on the shape and size of the smartphone or tablet screen (display unit).

In addition, in the above-described embodiment, the system 1 is configured to be able to link with eight types of messaging apps, apps A to H, but the types of messaging apps that can be linked may be changed as appropriate. Furthermore, it may be possible to add or delete messaging apps that can be linked as appropriate by performing a predetermined operation on the management server 2.

In addition, in the above-described embodiment, the app login screen 17 is provided by the server 5, so the screen configuration (layout) of the app login screen 17 differs depending on the type of message app, but the screen configuration (layout) of the app login screen 17 may be standardized. In the first embodiment, the screen configuration (layout) of the main function screen 18 when the individual display button 182K is selected is standardized regardless of the type of message app, but like the app login screen 17, the main function screen 18 may be configured to be redirected and provided from the server 5 (servers 5A to 5H), and the screen configuration (layout) of the main function screen 18 may differ depending on the type of message app.

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 (OAuth 2.0) for requesting general authorization, but the control content for initiating collaboration with apps A to H (servers 5A to 5H) is not limited to OAuth 2.0 and may be changed as appropriate.

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

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 on a cloud base connected to the management server 2 via the communication network 4.

Furthermore, the processes disclosed in the above-described embodiments may be executed by hardware such as a single CPU, multiple CPUs, or an ASIC, or a combination of these. Furthermore, 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.

The preceding paragraphs of this "Mode for Carrying Out the Invention" disclose the following Inventions A through D. In the description of Inventions A through D, the names and expressions of the corresponding components in the above-mentioned modes for carrying out the invention, as well as 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.

The system according to the invention A comprises:
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 for the message application from a user terminal;
an operation unit display unit (display switching management unit 22c) that displays, on the user terminal 3, an operation unit (main function display button 140) that can accept an operation to display a specific screen (main function screen 18) on the user terminal that can collectively display information (thread information icons 183) that indicates specific units (threads) related to message exchanges of each of the multiple message applications when the user is logged in to the user terminal, if there are multiple message applications linked to the system by the linkage management unit; and
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).

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 button 182K: app A individual display button 182KA to app 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.

The server according to Invention C comprises:
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 icons 183) indicating specific units (threads) related to the exchange of messages of each of the plurality of message applications,
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).

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 button 182K: app A individual display button 182KA to app 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.

1... Message application unified management system 2... Management server 3... User terminal 4... Communication network 5... Server 10... Message application unified management system window 10A... App usage start window 10B... User registration window 10C... Top window 10D... App cooperation window 10E... App use window 12... User registration screen 14... Right pane switching operation screen 15... Message application list screen 16... Message application image 17... App login screen 18... App function screen 21... Server communication unit 22... Server control unit 22a... Authentication management unit 22b... Cooperation management unit 22c... Display switching management unit 22d... Message information update management unit 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 application list display button 143... App login button 161... App cooperation operation screen display button 182Z... Display all button 182K... Individual display button 183... Thread information icon

Claims (4)

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. 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. 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. 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.