System and server

JP2026021624A5Pending Publication Date: 2026-05-15ONECHAT CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
ONECHAT CO LTD
Filing Date
2025-11-19
Publication Date
2026-05-15

AI Technical Summary

Technical Problem

Existing messaging applications require users to switch between different applications frequently, leading to time-consuming operations and cumbersome data transfer, especially when using multiple messaging platforms.

Method used

A system and server that centrally manage multiple messaging applications, allowing seamless integration and management through a unified interface, enabling users to access and switch between various messaging apps efficiently.

Benefits of technology

Enhances convenience and versatility by allowing users to manage and switch between multiple messaging applications with ease, reducing operational overhead and improving data transfer efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide a system and a server with convenience and versatility for integrating and unitarily managing a plurality of message applications.SOLUTION: When there are a plurality of message applications linked to the system by a linkage management means, the system includes an operation part display means for displaying an operation part (main function display button 140) capable of receiving an operation for displaying a specific screen (main function screen 18) capable of collectively displaying information (thread information icon 183) indicating a specific unit (thread) related to message exchange of each of the plurality of message applications on a user terminal, and a specific screen display means for displaying the specific screen on the user terminal by operating the operation part when the specific screen is not displayed on the user terminal.SELECTED DRAWING: Figure 8
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention provides a system for integrating and centrally managing multiple message applications. , and regarding the server. [Background technology]

[0002] Nowadays, there are many different forms of communication such as email, chat, and messengers. Furthermore, various communication tools have been developed. However, various types of applications (messaging applications) have been developed. However, if a user uses a messaging application with another user, If so, it may be tailored to the type of application the other user is using. As a result, some users find it necessary to use different messaging applications depending on the person they are talking to. There is a need.

[0003] Message applications are used on communication devices such as PCs and smartphones. When using the app, an icon corresponding to the message app will be displayed on the display screen of the communication device. An icon will be displayed, and by manipulating the icon, the corresponding message app will be displayed. The messaging application will then be launched and ready to use. To switch between the different options, close the open screen and then open the next message you want to use. You need to operate the icon of the application for the message. However, if such an operation is performed repeatedly, it becomes very time-consuming. Also, when sending image data received from one party to another party, Therefore, if you use different messaging apps, the operation can be cumbersome.

[0004] In addition, in the past, messaging applications were used to centrally manage multiple types of messaging applications. A message unified management system has been developed (see Patent Document 1). In the centralized management system, when you first access the system, a screen will appear with keywords corresponding to the When an icon is selected, the corresponding icon is displayed. The screen will switch to the corresponding screen. On the screen, the keyword associated with the selected icon will be displayed. All email messages and chat messages containing the code are listed by subject. On this screen, a speech bubble button is displayed, and when this button is selected, A new message display screen for chatting is created within the screen. [Prior art documents] [Patent documents]

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

[0006] However, the message unified management system described in Patent Document 1 mainly has the following features: It is assumed that this system will be used by companies and organizations that have a centralized management system for email. and chat was pinned.

[0007] The present invention has been made in view of the above circumstances. It is a convenient and versatile messaging application that can be integrated and managed centrally. The objective of the project is to provide a system and server for this purpose. [Means for solving the problem]

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

[0009] In addition, one aspect of the present invention made to solve the above problem is: A server capable of centrally managing multiple types of message applications, In response to a message application link request from a user terminal, the message application Linking an external device related to the application to the server, If there are multiple external devices related to the message application linked to the server, In this case, a specific unit relating to the exchange of messages of each of the plurality of message applications an operation for displaying a specific screen on the user terminal that can collectively display information indicating the position of the user; Displaying an acceptable operation unit on the user terminal; The operation unit is operated when the specific screen is not displayed on the user terminal. The specific screen is displayed on the user terminal by the above method. [Effects of the Invention]

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

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

[0012] (First embodiment) The first embodiment of the present invention will be described below. "Data" and "information" are synonymous and will be used without any distinction. If it is described, the number and format are not limited. Data stored or saved on a storage medium is also included in the "information" and "data" referred to here.

[0013] (Overall configuration of messaging app unified management system 1) FIG. 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 allows a user to manage multiple messages. It is used to centrally manage messaging apps. Message exchange (conversation, chat) between users one-to-one or between three or more users Internet-based application software (system) that can This refers to the system.

[0014] Message app centralized management system 1 can centrally manage multiple message app types The communication methods are email, messenger, and chat. , and on social networking services (SNS) such as Twitter and Instagram. However, some of them allow you to exchange messages, so if you have such a function, The SNS that you have is also included in the messaging app. and webmail.

[0015] In addition, the message application unified management system 1 has the same communication method but different types (display format) In addition to multiple messaging apps with different formats and layouts, there is also an email application and a There are also multiple messaging apps with different communication formats, such as messenger applications. It can be managed centrally. Details will be described later, but the message app centralized management system 1 is By receiving authentication from an external messaging app, By linking with the app, it will be possible to centrally manage external messaging apps.

[0016] In the following, the message app unified management system 1 will be simply referred to as "System 1 In this embodiment, messages that can be managed in a unified manner by the system 1 are also referred to as "messages." As an app, there are eight existing messaging apps, from Message App A to Message App H. In the following, we will refer to various messaging apps simply as " It is also called an "app."

[0017] As shown in FIG. 1, the system 1 includes a management server 2 managed by the operator of the system 1, The management server 2 and the user terminal 3 are connected via a communication network. They are connected via the network 4 so that they can send and receive information (data) with each other. Network 4 includes, for example, the Internet, LAN, telephone lines, mobile communication networks, Wi-Fi, etc. i (Wireless Fidelity) (registered trademark), other communication lines, or a combination thereof It may be configured in any way, and it does not matter whether it is wired or wireless.

[0018] The management server 2 and the user terminal 3 communicate with each other via a communication network 4. 1 can send and receive information (data) to and from server 5A, which manages application A that can be centrally managed. Similarly, the management server 2 and the user terminal 3 are connected to each other via a communication network. Through the network 4, the servers 5B to 5H that manage the applications B to H are also connected to each other. Servers 5A to 5H are connected so that they can send and receive information (data). Server 5A to Server 5H are not included in System 1. In other words, Server 5A to Server 5H are not included in System 1. In the following, servers 5A to 5H are referred to as "servers 5." It is sometimes referred to collectively as

[0019] The management server 2 is configured as a general information processing device, and although not shown, it is a C The PU (Central Processing Unit) and RAM (Random Access Memory) function as the CPU's working area. It consists of a ROM (Read Only Memory) that stores various programs, a ROM (Read Only Memory) that stores various programs, and a The device consists of a storage device that stores data, an input section including a keyboard and mouse, and a display that displays images. The management server 2 includes a communication unit and a transmission / reception unit for communicating with an external device. Even if it is composed of an information processing device (one physical computer), it may be composed of multiple information processing devices. It is configured so that multiple computers (physically multiple computers) can work together to perform their functions. The management server 2 may be configured in a cloud environment. Details of the management server 2 will be described later.

[0020] Although a block diagram showing the configuration of the user terminal 3 is omitted, the user terminal 3 is a general It consists of a communication terminal, a CPU that controls the whole system, and RAM that functions as the CPU's working area. ROM that stores various programs, a storage device that stores various data, a keyboard, An input unit including a mouse, a display unit for displaying images, and a transmission / reception unit for communicating with external devices Specifically, the user terminal 3 may be a smartphone, a tablet terminal, a notebook computer, or the like. laptops (notebooks), PDAs (Personal Digital Assistants), and desk In this embodiment, the user terminal 3 may be a laptop computer. It is assumed that the system is composed of a single computer.

[0021] (Management Server 2) Next, the management server 2 will be described. FIG. 2 shows 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 The server 5 includes a storage unit 23 and transmits and receives information (data) to and from the user terminal 3 and the server 5. By trusting this, we provide a service that centrally manages apps A to H.

[0022] The server communication unit 21 communicates with external devices (user terminal 3 and server 5) and transmits information (data). The server communication unit 21 is configured with an interface for transmitting and receiving data. The communication may be wireless or wired.

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

[0024] The server storage unit 23 also stores a management program 22 to be executed by the server control unit 22 (to be described later). Furthermore, the server storage unit 23 stores the management program 23a. It is provided with a database 23b in which various data to be used is stored and accumulated.

[0025] The database 23b has a plurality of tables. FIG. 1 is a diagram showing a schematic representation of a plurality of registered tables. There are a user information table 24a and a thread information table 24b. The configuration of the various tables is not limited to the contents described below and may be changed as appropriate. You can change it to.

[0026] The user information table 24a stores information about users (hereinafter referred to as "user information"). This is a table that stores user information, such as the user ID, email address, and so on. The user information for a user includes the email address and password. Storing (memorizing) the user information in the user information table 24a is considered to be "user registration" for the user. It is called "Record."

[0027] An example of the configuration of the user information table 24a is shown in Fig. 4. As shown in Fig. 4, In Bull 24a, the email address and password are stored in association with the user ID. As will be described later, when the user terminal 3 accesses the management server 2 for the first time, At this time, the management server 2 displays a screen on the user terminal 3 for inputting an email address and a password. Display the face.

[0028] The thread information table 24b contains information about threads (hereinafter referred to as "thread information"). This table is generated for each thread. Depending on the type of message app, names other than "threads" such as "rooms" or "talks" may be used. A thread is a series of messages exchanged between two people. Threads are formed by one-on-one interactions between people, and threads are formed by mutual interactions between three or more people. There is a thread that is created.

[0029] The thread information table 24b contains the user ID, the message in which the thread is expanded, The type of application and the thread ID of the thread are associated. Each thread information table 24b contains information about each message that constitutes a thread. , the date and time the message was sent, and the sender.

[0030] Next, the server control unit 22 will be described. The server control unit 22 is a processor, i.e., A processing device that performs data calculations, processing, and transfer, executes programs, and controls other devices. It consists of a CPU and various registers.

[0031] The server control unit 22 executes various programs stored in the server storage unit 23. The server control unit 22 centrally controls the management server 2. By executing this, various messages are sent in cooperation with the user terminal 3 and the servers 5A to 5H. It provides centralized management of applications.

[0032] Each functional block realized by the server control unit 22 will be described below. As described above, the server control unit 22 includes an authentication management unit 22a, a cooperation management unit 22b, a display switching management unit 22c, and a Each of the units 22a to 22d is a server The control unit 22 corresponds to the functions that can be realized. The configuration of each of the units 22a to 22d is not limited to this, and these units 22a to 22d may be integrated as appropriate. Furthermore, each of the sections 22a to 22d may be appropriately subdivided.

[0033] When the authentication management unit 22a is accessed from the user terminal 3, the authentication management unit 22a As will be described later, once a user is registered, the accessing user's ID is confirmed. A user ID is assigned to terminal 3 (user), and after user registration, the user terminal 3 When accessed from the management server 2, the user ID is also sent as header information. Therefore, when the authentication management unit 22a is accessed from the user terminal 3, the authentication management unit 22a receives a message including the user ID. If the user ID is registered, it is then determined whether the user ID is registered in the management server 2. If the user is registered, the authentication management unit 22a logs in to the user terminal 3. On the other hand, if the user is not registered, the top window 1C will be displayed. An error message indicating that login has failed is displayed on the user terminal 3 (not shown).

[0034] Furthermore, when the authentication management unit 22a is accessed from the user terminal 3, the authentication management unit 22a If not, the user can enter the email address and password into the user terminal 3. Then, the user terminal 3 is displayed with a screen (a user registration screen 12 to be described later). When the email address and password are sent to Management Server 2 by the setting operation, authentication is The management unit 22a issues a user ID for the email address and password as appropriate. The email address and password associated with the user ID are entered in the user information table. Furthermore, the authentication management unit 22a stores (memorizes) the issued user ID in the table 24a. The user terminal 3 then transmits the information to the management server 2. The user ID must be sent as header information. It is not limited to this and may be changed as appropriate.

[0035] The cooperation management unit 22b manages the servers 5A to 5C, which are positioned as external devices for the system 1. It is possible to perform processing to start cooperation with the robot 5H. Although a partial description will be omitted, the cooperation management unit 22b manages applications A to H from the user terminal 3. When you are requested to start collaboration with (Server 5A to Server 5H), you will be asked to grant general permissions. Execute the process (OAuth2.0) to authenticate the user.

[0036] The cooperation management unit 22b requests the start of cooperation by a predetermined operation on the user terminal 3. When the type of the messaging app is transmitted to the management server 2, the login information relating to the messaging app is sent to the management server 2. A login screen (application login screen 17 to be described later) is displayed on the user terminal 3 (redirection Then, the user terminal 3 is requested to perform a login operation related to the message application. When this is done, the cooperation management unit 22b accesses the server 5 related to the message application. Here, the server 5 makes a decision on whether to permit cooperation, and if the cooperation is permitted, If successful, the cooperation management unit 22b will add information about the user in the server 5 to the thread information. The information is stored in the information table 24c (the user related to the messaging app that is the target of the linkage). (Register information about the

[0037] Furthermore, the cooperation management unit 22b performs processing to terminate cooperation with the servers 5A to 5H. Specifically, the cooperation management unit 22b can perform the following by performing a predetermined operation on the user terminal 3: When the type of message app requesting termination of the link is sent to the management server 2, A screen to confirm that you want to terminate the connection with the messaging app (see below for details on the app connection). A final confirmation window 19) for terminating the mobile phone is displayed on the user terminal 3. When this occurs, an operation to approve the termination of cooperation becomes possible on the user terminal 3, and the approval When the operation is performed, the cooperation management unit 22b notifies the server 5 related to the message application of the cooperation. In response to this, the server 5 terminates the link with the system 1. The cooperation management unit 22b stores information related to the message application of the user in the database 23. Delete from b.

[0038] When the user terminal 3 is logged in to the system 1, the display switching management unit 22c By performing a predetermined operation on the user terminal 3, the system 1 displayed on the user terminal 3 is The display contents of the screen relating to the above will be changed. This can be done arbitrarily, and by this predetermined operation, the screen related to the system 1 (described later) While the message app centralized management system window 10 is displayed (system Easily switch between messaging apps (while the software related to System 1 is open) It can be replaced.

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

[0040] Next, a specific example in which a user uses the system 1 via the user terminal 3 will be described. The premise is that users can download the software from a designated site. The software (program) for using the system 1 is installed on the user's own user terminal 3. The software related to the system 1 is installed on the user terminal 3. Then, the user terminal 3 itself functions as a local server of the system 1. After the installation, the browsing of the user terminal 3 performs various processes related to the system 1. In this embodiment, the user terminal 3 is assumed to be a notebook computer. Therefore, various images are displayed on the screen, and the user inputs the required information using the mouse and keyboard. A force operation is assumed to be performed.

[0041] In a situation where a user is not registered with System 1, software related to System 1 is used by the user. When the user terminal 3 starts up the system 1, the user terminal 3 displays a window related to the system 1 on its display. Dou (message app centralized management system for Windows 10, hereinafter simply referred to as "Windows 10" The display contents of window 10 change depending on the situation. Specifically, if you start up software related to System 1 without registering as a user, When registering as a user, and after completing user registration, which messaging app When the app is not in use, or after user registration is complete and any messaging app is in use, When linking with the app, or when any messaging app is used after user registration is completed. The display contents and layout of Window 10 differ depending on whether it is in the Window 1 when starting software related to System 1 without user registration 0 is called "Window 1A when starting to use the app" and Window 10 when registering as a user. This is called "User Registration Window 1B", and is the window that appears after user registration is complete and any message is displayed. When the Sage app is not in use, the window 10 is called the "top window 1C." However, after user registration is complete, the linking process with any messaging app is being performed. Window 10 when the user registration is completed is called "Window 1D when the application is linked." After installing any messaging app, you can turn Windows 10 into an app When in use it is called "Window 1E".

[0042] The window 10 has a fixed display area 10A formed in a strip shape at the top and a rectangular display area 10B just below it. The display area 10B is formed in a rectangular shape and can occupy most of the display area. However, even if the status of the system 1 changes after this, the user terminal 3 will not While connected to System 1 (while the software related to System 1 is open), The area 10A continues to be displayed as it is. Meanwhile, the status of the system 1 changes in various ways. The contents displayed in the variable display area 10B are displayed in accordance with the function available in the system 1. changes.

[0043] FIG. 5(A) shows a specific example of a window 1A that appears when starting to use an application. The window 1A at the start of application use has a fixed display area 10A formed in a strip shape at the top. And just below that, when you start using the app, it may be formed in a rectangular shape, occupying most of the window 1A. As will be described later, the application start window 1A is ,User registration window 1B, Top window 1C, App integration window 1D, When the application is in use, a fixed display area 10A is formed in common with the window 1E, and the fixed display The content displayed in the area 10A also remains unchanged. On the other hand, the content displayed in the variable display area 10B Window 1A is the window when you start using the app, Window 1B is the window when you register as a user, and Window 1C is the top window. Window 1C, window 1D when connecting with the app, and window 1E when using the app are different from each other. become.

[0044] The fixed display area 10A is configured with a so-called "title bar." For example, The name of System 1 (in Figure 5(A) it is "〇△□▽") is displayed on the left side of area 10A. In addition, the variable display area 10B of the application use start window 1A displays the application use start time. A start screen 11 corresponding to the start window 1A is displayed. Then, the start screen 11 In order to start using System 1 in earnest, in other words, to register users, When the start button 111 is pressed, the app From the window 1A when starting to use the system, you can register as a user of System 1. Switch to Window 1B.

[0045] FIG. 5(B) shows a specific example of the user registration window 1B. As shown in FIG. 5(B), Window 1B for user registration is a fixed display area, just like Window 1A for starting to use the app. The fixed display area 10A is divided into a fixed display area 10B and a variable display area 10C. When you start using the app, the title bar is configured in the same way as window 1A. The display area 10B displays a user registration screen for performing user registration (new registration) related to the system 1. In other words, when the start button 111 is operated, the screen 12 is displayed. The content displayed in the change display area 10B is switched from the start screen 11 to the user registration screen 12. Replace.

[0046] The user registration screen 12 is configured so that user registration information can be input. The user registration information consists of an email address and a password. The registration screen 12 has an email address input field 121 for inputting an email address and a password. A password input field 122 for inputting a password is formed. How to enter your email address in 1 and your password in the password field 122 The method can be set appropriately. In this embodiment, the user terminal 3 is configured as a notebook computer. For example, the email address input field 121 and the password input field 122 are clicked. When the cursor is clicked, it will be displayed and you can enter text using the keyboard (not shown). The email address entry field 121 and password entry field 122 are displayed in response to keyboard operation. The email address and password are entered in the email address entry field 122. When configured as a smartphone or tablet, for example, email address input field 121 and password When the word input field 122 is tapped, a cursor is displayed there and a predetermined software A software keyboard (not shown) is displayed superimposed on the user registration screen 12. And, by operating the designated software keyboard, you can input email addresses. Enter your email address and password in field 121 and password field 122. That's fine.

[0047] The user registration screen 12 also displays a screen for executing user registration, in other words, for the management server 2. A registration execution button 123 is provided for requesting user registration. When the button 123 is operated, the information entered in the email address entry field 121 (email The information (address) entered in the password entry field 122 corresponds to the information (password) entered in the password entry field 122. The email address is then sent to the management server 2. The password and the password are referred to as "user registration information." When the command is executed, a command requesting user registration (user registration request command) is sent along with the user information. The data (e.g., the password) is also sent to the management server 2.

[0048] Then, the management server 2 receives the user registration request command and the user registration information. The user registration information is stored in the user information table 24a. In detail, the management server 2 receives the request for user registration. When the user enters the password, the system issues information (user ID) to identify the user appropriately, and The email address and password are stored in the user information table 24a. In addition, when the management server 2 registers the user registration information, the management server 2 sends the user registration information to the user terminal 3. Switch from window 1B to top window 1C. Top window 1C is This is the starting window (screen) for registered users, and will be used from then on in System 1. If you start the software when it is not running, the top window 1C will be displayed. However, as will be described later, the contents displayed in the top window 1C may differ depending on the situation. do.

[0049] Figure 5(C) shows the top window 1C that is displayed when user registration is completed. A specific example is shown below. As shown in FIG. 5(C), the top window 1C displays a message when the application is started. The fixed title bar is the same as in the case of Window 1A and Window 1B when the user is registered. However, the window 1A when starting to use the application and the user registration window 1B are formed. Unlike the time window 1B, the variable display area 10B of the top window 1C is It is further divided into left and right panes 10BL and 10BR. The login screen17 and main function screen18 of various messaging apps are displayed. In this case, the variable display area 10B is also displayed in the left pane 10B in the same manner as in the case of the top window 1C. The left pane 10BL is divided into a right pane 10BR and a left pane 10BL. The contents are basically the top window 1C, the application link window 1D, and When using the app, the screen is the same as in window 1E, but it is displayed in the right pane 10BR. The contents displayed are the top window 1C, the application link window 1D, and the application When in use, it differs from window 1E.

[0050] The left pane 10BL of the top window 1C displays the information to be displayed in the right pane 10BR. The right pane switching operation screen 14 is displayed, allowing you to switch the contents of the top The right pane 10BR of Window 1C displays a message app that can be linked to System 1. The message app list screen 15 is displayed. The left pane 10BL is The left end of the variable display area 10B is formed in a vertically long rectangular shape, and the right pane 10BR is The majority of the variable display area 10B except for the left pane 10BL is formed in a horizontally long rectangular shape. In this embodiment, the right pane 10BR is several times larger than the left pane 10BL. It has been completed.

[0051] The right pane switching operation screen 14 displays a main function screen 18 on the right pane 10BR. The main function display button 140 can accept operations for the A message app list display button that can accept an operation to display the message app list screen 15 You can accept operations to display the screen for various settings on the right pane 10BR. A setting screen display button 142 that can be used to display the setting screen is displayed next to the top and bottom.

[0052] The main function display button 140 is displayed on the right pane 10BR. 5. The login screen 17 for various messaging apps described below, or various settings When the screen for the function (not shown) is displayed, you want to switch to the main function screen 18. When the main function display button 140 is operated, the right pane 10BR displays The main function screen 18 is displayed. Note that the system 1 can be linked to any messaging app. If not, the operation of the main function display button 140 is invalid.

[0053] The message app list display button 141 displays the message app list in the right pane 10BR. It is not particularly used when the list screen 15 is displayed, but it is displayed in the right pane 10BR. , a main function screen 18, an application login screen 17 for various messaging applications, or each When the screen for setting the type (not shown) is displayed, This is used when you want to switch to the screen 15. The message app list display button 141 is operated. Then, a message app list screen 15 is displayed in the right pane 10BR.

[0054] Although not shown here, the right pane 10BR displays the main function screen 18, message A list screen 15 of messaging apps or a login screen 17 for various messaging apps is displayed. When the setting screen display button 142 is operated while the setting screen is displayed, each A screen for making various settings will be displayed. Although we will not explain it here, The screen for setting various items is configured to be able to accept operations for setting various items.

[0055] The message app list screen 15 lists message apps that can be linked with System 1. On the message app list screen 15, apps A to H are displayed individually. An image (message app image 16) representing app A is displayed appropriately. The message application image 16 is referred to as an "application A image 16A." Message app image 16 representing B to H is called "App B Image 16B" to "App It is called "16H 16H Image".

[0056] In this embodiment, each message application image 16 is The overall shape of the message app image 16 is the same. The size can be set as appropriate, but in this embodiment, the message application image 16 is vertically oriented. The message application list screen 15 is formed in a rectangular shape, and has two rows, one above the other, and each row has two rows, one below the other. They are arranged in a row of four on each side.

[0057] The upper two-thirds of each message app image 16 is The logo and name representing each message app are displayed. The lower third of the screen is where you can link the application to System 1. A button that can accept operations to display the screen for application linkage operations (application linkage operation screen) A screen display button 161) is provided. The display button 161 is referred to as the "application A cooperative operation screen display button 161A." The application cooperation operation screen display button 161 for application B to application H is referred to as “application B Linked operation screen display button 161B" to "App H linked operation screen display button 161H" do.

[0058] When the application A cooperation operation screen display button 161A is operated, cooperation with application A is started. A command requesting the initiation of collaboration with the application A (application A collaboration start request command) is sent together with the user ID. The command is sent to the management server 2. The management server 2 receives the application A cooperation start request command. Then, the login screen for application A is displayed on the user terminal 3 (redirected to application A). (The login screen for application A is displayed on the user terminal 3.) Then, the management server 2 displays a message including a login screen for the application A from the top window 1C. Switch to 1D window when connecting with the app.

[0059] In addition, in the same way as when the application A cooperation operation screen display button 161A is operated, the application B When the link operation screen display button 161B to the app H link operation screen display button 161H are operated, When this happens, a command requesting that collaboration with apps B to H be started (app B collaboration) is sent. The application H collaboration start request command is sent to the management server together with the user ID. Management server 2 sends the application B collaboration start request command to application H collaboration start request command to application H collaboration start request command. When the request command is received, the login screens for the applications B to H are displayed on the user terminal 3. (Redirect to app B to app H and display the logs related to app B to app H) (The user terminal 3 displays the home screen.) In other words, the management server 2 From Window 1C, the application linking window including the login screen for applications B to H appears. Switch to 1D.

[0060] In addition, since this is a login screen for apps A to H, basically, It is assumed that users have already registered for apps A to H. Therefore, the login screens for apps A to H are referred to as "app A login screen 17A." ~ "App H login screen 17H" and "App A login screen 17A" ~ "App "H Login Screen 17H" is collectively referred to as "App Login Screen 17".

[0061] In this embodiment, in order to link the system 1 with the applications A to H, a management server Server 2 switches from top window 1C to application link window 1D, and An application login screen 17 relating to the application is displayed on the user terminal 3. Login screen 17 is displayed by redirection, so App A login screen 17A to App H Login screen 17H is provided by apps A to H (servers 5A to H). Therefore, the display contents of the application A login screen 17A to the application H login screen 17H are (Screen configuration, layout, or type) may vary depending on the type of messaging app. do.

[0062] The user terminal 3 displays an application login screen 17 in the right pane 10BR. In the situation of FIG. 5(C), when the application E cooperation operation screen display button 161E is operated, In this case, the right side of the variable display area 10B in the application cooperation window 1D is Pane 10BR displays app E login screen 17E.

[0063] FIG. 6(A) shows a specific example of an application linking window 1D including an application E login screen 17E. As shown in FIG. 6(A), the login screen 17E of the application E does not require the user to enter an email address. Enter your email address in the email input field 171E and your password in the password input field 17 This means that the information required to log in to app E is stored in the The information required for login and The configuration of each application login screen 17 differs depending on the messaging application.

[0064] How to enter your email address in the email address entry field 171E and password entry field 1 The input method for 72E is the same as the input method for the email address input field 121. This can be set appropriately in the same way as the password input method in the password input field 122. The explanation will be omitted.

[0065] Then, the email address registered in App E will be displayed in the email address input field 171E. The password registered in the application E is entered in the password input field 172E. At the same time, the cursor is placed in the email address input field 171E or the password input field 172E. When the "ENTER / Execute" button on the keyboard of user terminal 3 is operated while is displayed. When the application E login information is created, the user terminal 3 associates the information (application E login information) with each other. and sends it to the server 5E of the application E.

[0066] The server 5E of the application E receives the application E login information transmitted from the user terminal 3. When the user sends a message, it determines whether the user is registered in app E, and if so, The user issues permission to cooperate with the system 1 via the user terminal 3. When cooperation is permitted, the system The management server 2 accesses the server 5E of the application E and acquires data related to the user. The server storage unit 23 associates the data with the user ID of the user. That is, the server 5E of the application E stores the data about the user in the system 1. This starts the collaboration between App E and System 1.

[0067] The content of the data provided by app E depends on the messaging app, but at least The information about the message is basically For example, information about a message is stored in the It is divided into threads (including talks or chats) and each thread (talk, In the case of messages (including chats), data is also included on a message-by-message basis. Message-level data includes the date and time the message was sent, the sender, and the specifics of the message. The content (text, images, and audio) is linked to each other. The following are the message sending dates, senders, and message Data in units of messages consisting of specific content is called "message data." Information on a thread basis containing one or more message data is called "thread data." It is called.

[0068] As described above, the server storage unit 23 stores thread information table 2 4b is stored, the management server 2 uses the thread data acquired from the server 5E. Based on this, a thread information table that associates the user ID of the user and application E is created. Generate 24b.

[0069] In addition, the management server 2 receives cooperation permission from the application E and stores the user ID and the application E. When the thread information table 24b is generated, the thread information table 24b is Based on this, a main function screen 11 on which the application E can be used in the system 1 is displayed on the user terminal 3. 8 in the right pane 10BR. Therefore, the user terminal 3 displays the right pane 10B The display content in R has been changed from the App E login screen 17E that was displayed just before the link permission was granted. Then, the screen switches to the main function screen 18. The main function screen 18 will be described later.

[0070] Returning to the explanation of the application linking window 1D including the application E login screen 17E, see FIG. 6( As shown in A), the right pane 10BR of the application link window 1D displays the application E-logo. The application window 17E is displayed, but the variable display area 10 of the application window 1D is displayed. B is the left pane 10BL and the right pane 10BR, as in the case of the top window 1C. And, just like the top window 1C, the left pane 10 The right pane switching operation screen 14 is displayed on the BL.

[0071] When connecting to an app, the top window is displayed on the right pane switching operation screen 14 of the window 1D. The main function display button 140 and message app list display are in the same position as in the Dou 1C. A button 141 and a setting screen display button 142 are displayed.

[0072] Next, the main function screen 18 will be described. The main function screen 18 is shown in FIG. 6(B). A specific example of the window 1E when using the application is shown in FIG. 6B. 18 is displayed in the right pane 10BR of the variable display area 10B. 18 is further divided into a left side and a right side. Both the left and right sides are formed in a vertically long rectangle. It is being done.

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

[0074] The thread search area 18A is provided with a search information input field 181 for searching threads. Although a detailed description of the search information input field 181 will be omitted, the search input field 181 contains It is possible to enter information to search for threads, such as keywords, in the search information input field 181. You can search for threads based on keywords entered in the.

[0075] The display application switching operation area 18B displays the display contents of the thread information list display area 181C. A button for specifying the display content (display content specification button) 182 is displayed. 182 contains information about all message app threads linked to the system 1. and a message display button 182Z for displaying the information related to the system 1. Individual threads that display information about a single message thread in a message app. There is a display button 182K.

[0076] The individual display button 182K is set for each message app, and the individual display button The 182K has apps associated with each of the message apps A to H. There are individual display buttons for Pre-A 182KA to App-H 182KH.

[0077] If there is at least one messaging app linked to the system 1, click the full view button 182Z will be displayed, and it will be associated with the messaging app that is currently linked. The individual display button 182K is also displayed. This shows the situation immediately after linking with messaging app E, so Figure 6(B) shows the overall table. A display button 182Z and an individual display button 182KE for application E are displayed. As the display position of each of the display content specifying buttons 182, a whole display button 182Z is ​​displayed. The individual display button 182K is displayed on the left edge of the application switching operation area 18B, and is connected to the right of the individual display button 182K. They are displayed in the order they were added, from left to right.

[0078] Also, each of the display content specification buttons 182 is configured to be able to accept a selection operation. However, 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 Assume that Tan 182Z is ​​selected.

[0079] The thread information list display area 181C displays a certain number of threads (six in this embodiment). Information about threads is displayed in a list. Information about threads can be set on a per-thread basis. The information about one thread is displayed as a horizontally rectangular icon (Thread Thread information icons 183 are all the same size. The threads are displayed in the order they were updated, from top to bottom. are.

[0080] At the left end of the thread information icon 183, a message corresponding to the thread information icon 183 is displayed. A circular image is displayed that represents a participant (party) in the thread other than the user in question. If the thread is formed between the user and one other person, a circle representing the other person will appear. The image is displayed. Also, if the thread is formed between the user and two or more other people, If there is a circle, one of the other two people will be placed in the center, and the remaining people will be placed in the center. Part of the image is shifted from the central circular image and displayed behind it.

[0081] At the right end of the thread information icon 183, there is a circular image that indicates the type of message app. Figure 6(B) shows the system 1 first linked with messaging app E. Since this shows the situation immediately after the message, FIG. 6(B) shows thread information related to the message application E. Only icon 183 is displayed. Therefore, in FIG. 6(B), all threads A circular image representing the message app E is displayed at the right end of the red information icon 183. Specifically, the message app E is displayed inside a circular image that represents the type of message app. The letter "E" is displayed.

[0082] At the top of the center part of the thread information icon 183, excluding both ends, the thread If the thread is formed by two people, including the user, the name of the other person, or the name of the group If the thread is formed by a group, the group name is displayed. The content corresponding to the message app will be displayed at the bottom of the central part excluding the part. , if your messaging app is configured to include a subject, like email, the subject will be displayed. If configured not to include a subject, like in chat, the most recent message is displayed. The beginning of the message (in this embodiment, 12 characters: the latest simplified message) and its sender It is displayed.

[0083] The thread information icon 183 is configured to be able to accept a selection operation, and when selected, A detailed history of messages related to the thread information icon 183 is displayed in the preview window described later. When the main function screen 18 is displayed, The thread information icon 183 shown above, in other words the most recently updated ( The thread info icon 183 corresponding to the thread in which the message was sent is selected. It is assumed that the device is in a state where it is in use.

[0084] Next, the right side of the main function screen 18 will be described. The main function screen 18 is divided into three sections along the bottom. A horizontally long rectangular thread target display area 184 is formed in the bottom edge of the A message sending operation area 186 is formed, and the thread target display area 184 and the message sending area 186 are formed. A vertically long rectangular preview display area 185 is located in the vertical center between the communication operation area 186. It is formed.

[0085] At the left end of the thread target display area 184, the thread related to the preview display area 185 is displayed. Represents something other than the user (the subject of the thread, the other party of the thread: individual name or group name) A circular image is displayed, and to the right of the image is a string that indicates the subject of the thread (such as a person's name or group name). Loop name: In Figure 6(B), the group name "XX Company Sales Department" is displayed. That is, information other than the latest simplified message in the thread information icon 183 is displayed for the thread. The image is displayed in the elephant display area 184.

[0086] The preview display area 185 displays the message exchange. The messages are displayed at the bottom of the preview display area 185, and are exchanged from there. The messages are displayed in chronological order from top to bottom. Although it is not limited and can be set appropriately, in this embodiment, the message is displayed in a speech bubble. The speech bubbles representing messages sent by the user are displayed right-justified, and messages sent by other users are displayed The speech bubbles representing messages sent by the thread target or thread recipient are left-aligned. It will be displayed as

[0087] A message sending operation area 186 is used for inputting a message to be sent by the user. The message input field 186A and the message input in the message input field 186A A send button 186B is provided for sending a message. The specific configuration of the send button 186B can be set as appropriate, but in this embodiment, the send button 186B is It is composed of a stamp figure and is located at the right end of the message sending operation area 186. The message input field 186A is formed in a horizontally long rectangle and is located to the left of the send button 186B. are.

[0088] The method of inputting a message into the message input field 186A can be set as appropriate. In this embodiment, the user terminal 3 is configured as a personal computer, so for example, After displaying the cursor on the 186A, you can operate the keyboard to change the message. A message can be entered in the input field 186A. A send button 186B accepts the operation. The operation and processing contents when the send button 186B is operated will be explained later. Describe.

[0089] The main function screen 18 is in a state where the whole display button 182Z is ​​selected. Also, any individual display button 182K (app A individual display button 182KA to app G individual display button 182KA) In other words, even if the Display button KG is selected, all linked The thread information icon 183 related to the message app was in a mixed state and could be displayed. However, the thread information icon 183 related to one specific message app is displayed. Even if the screen layout and design are the same, they may not be completely identical. For example, when the whole display button 182Z is ​​selected, and when the individual display button 182 The screen configuration and design may be different when K is selected. You can set the screen layout and design for each messaging app type (email, messenger). stomach.

[0090] Here, for example, in the situation shown in FIG. 6(B), if the message application list display button 141 is As described above, the message app list display button 141 is a variable display. A message application list screen 15 is displayed in the right pane 10BR of the display area 10B. Therefore, the user terminal 3 displays the message application list display button 141 as When operated, the user ID of the user terminal 3 and the message application list screen 15 are displayed. A command indicating the request (message app list screen display request command) is sent to management server 2. When the management server 2 receives the message app list screen display request command, A message app list screen 15 containing content according to the current status of the user indicated by the user ID is included. A top window 1C is displayed on the user terminal 3. The "content" varies depending on whether the user is linked to each messaging app. .

[0091] FIG. 7(A) shows a state in which the message application list display button 141 is operated in the situation shown in FIG. 6(B). 10 is a diagram showing a specific example of a top window 1C that is displayed in response to the above-mentioned As shown above, System 1 is currently linked to App E, so if you add System 1 to App E, Therefore, as shown in Figure 7(A), In the situation where the message app list screen 15 is displayed, the app image 16E is An operation to cancel cooperation with app E instead of the app E cooperation operation screen display button 161E A button (app E linkage cancellation button 162E) that can accept this is provided. The operation of the system 1 when the E cooperation cancellation button 162E is operated will be described later.

[0092] In the situation shown in FIG. 7(A), for example, when the application C cooperation operation screen display button 161C is operated, When the application C is started, a command to request the start of application C cooperation is sent to the management server 2, and the application E cooperation operation screen is displayed. As in the case where the face display button 161E is operated, the top window is displayed as shown in FIG. 7(B). Window 1C will switch to Window 1D when connecting to the app. The right pane 10BR displays the app C login screen 17C.

[0093] The login screen for App C 17C allows you to enter your email address or phone number. A telephone number input field 171C and a password input field 172C for inputting a password are provided. That is, in this embodiment, an email address or a phone number and a password are formed. The password and the password constitute the information required to log in to application C. The login screen 17C also includes a login button 173C for executing login. It has been done.

[0094] When the login button 173C is operated, the user terminal 3 displays the application E login screen 17 As with the case where E is displayed, you will need to enter your email address or phone number as authentication information. The application C sends the application C login information and password to the application C server 5C.

[0095] The application C server 5C receives the application C login information transmitted from the user terminal 3. When the user sends a message, it checks whether the user is registered in application C, and if so, The user terminal 3 allows the system 1 to cooperate with the application E. Finally, the management server 2 starts the cooperation with the server 5C of the application C. accesses the server to acquire data relating to the user, and stores the data in the server storage unit 23. The data is stored in association with the user ID of the user. C provides data about its users to System 1. This allows the app C and System 1 to In response to the start of collaboration with application C, management server 2 Then, switch from the application C login screen 17C to the main function screen 18.

[0096] FIG. 8(A) shows an application including a main function screen 18 immediately after the system 1 is linked with the application C. FIG. 1 shows a window 1E when the system 1 is using app E and then app C. Since the app is linked, as shown in FIG. 8(A), , an application C individual display button 182KC associated with application C is displayed.

[0097] Also, FIG. 8(A) shows the situation immediately after switching to the main function screen 18. The full display button 182Z is ​​selected. Therefore, the thread information list display area 181C includes all messaging apps (in this situation) linked to the system 1. , thread information icons 183 relating to application E and application C can be displayed.

[0098] The thread information icon 183 for application C has the letter "C" representing application C at the right end. The thread information icon 183 is displayed. Therefore, in the situation shown in FIG. Now, from the top, the thread information icon 183 related to application C, the thread information icon 184 related to application C, a thread information icon 183 relating to application E, a thread information icon 183 relating to application E, and a thread information icon 183 relating to application E. Red information icon 183, thread information icon 183 related to app C, and thread information icon 183 related to app E A thread information icon 183 is displayed.

[0099] In the situation shown in Figure 8(A), the six most recently updated threads include application E. Since there were threads related to app E and threads related to app C, the thread information icon 1 related to app E The thread information icon for 83 and app C is displayed, but the most recently updated If all six threads belong to one of the apps, the thread information for that app will be displayed. Only icon 183 will be displayed.

[0100] In the situation shown in FIG. 8A, the application C individual display button associated with application C is Suppose 182KC is operated. Then, as shown in Figure 8(B), the thread information In the list display area 181C, only the thread information icon 183 related to the application C is displayed. The preview display area 185 displays the most recently updated threads related to application C. The message exchanges are displayed. That is, when you select the App C individual display button 182KC, The operation of selecting constitutes a request to display the main function screen 18 related to the application C (dedicated to the application C). Complete.

[0101] When an operation to select the application C individual display button 182KC is performed, the user terminal 3 The main function screen 18 related to application C (dedicated to application C) is displayed together with the user ID. A command indicating a request for displaying the main function screen of application C (a command requesting display of the main function screen of application C) is sent to management server 2. When the management server 2 receives the application C main function screen display request command, The main function screen 18 related to the application C (dedicated to the application C) is displayed on the user terminal 3. do.

[0102] When the management server 2 receives the application C main function screen display request command, Access server 5C and retrieve data related to threads related to the user in application C. The acquired data is stored in the server storage unit 23. After updating the thread information table 24b), the thread information list table is updated according to the data. The display contents of the thread target display area 181C, the display contents of the thread target display area 184, and the preview The display content of the display area 185 is switched to that relating to the application C.

[0103] In addition, in the situation shown in FIG. 8(A) and the situation shown in FIG. 8(B), Assume that the Pre-E individual display button 182KE is operated. Then, as shown in FIG. 8(C), In this way, the thread information list display area 181C displays thread information icon 1 related to the application E. Only the thread 83 related to the application E is displayed, and the preview display area 185 shows the thread The most recently updated messages are displayed. The operation of selecting the button 182KE is to display the main function screen related to the application E (dedicated to the application E). Constitutes 18 display requests.

[0104] When an operation to select the application E individual display button 182KE is performed, the user terminal 3 The main function screen 18 related to the application E (dedicated to the application E) is displayed together with the user ID. A command indicating a request for displaying the main function screen of the application E is sent to the management server 2. When the management server 2 receives the application E main function screen display request command, The main function screen 18 related to the application E (dedicated to the application E) is displayed on the user terminal 3. do.

[0105] When the management server 2 receives the application E main function screen display request command, Access server 5E and retrieve data related to threads related to the user in application E. The acquired data is stored in the server storage unit 23. The acquired data is stored in the server storage unit 23. After updating the thread information table 24b), the thread information list table is updated according to the data. The display contents of the thread target display area 181C, the display contents of the thread target display area 184, and the preview The display content of the display area 185 is switched to that relating to the application E.

[0106] In the situation shown in FIG. 8(B) or the situation shown in FIG. 8(C), the whole display button 182Z is ​​operated. When the application is created, it is displayed in the linked application E and application C as shown in Figure 8(A). The main function screen 18 is displayed.

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

[0108] When an operation to select the thread information icon 183 is performed, the user terminal 3 displays the thread information. The thread target related to the thread information icon 183 is associated with the user ID and sent to the management server. The thread detail information is sent to the server 2 and a command (thread detail information) is sent to the server 2. The management server 2 then sends a notification display request command.

[0109] When the management server 2 receives the thread detailed information display request command, it accesses the server 5 of the application to acquire data related to the thread, and The data relating to the thread in the data relating to the application relating to the user in the storage unit 23 After updating the data (thread information table 24b), the thread pair is The display contents of the image display area 184 and the display contents of the preview display area 185 are displayed in accordance with the thread. Switch to the one related to the code.

[0110] For example, in the situation shown in FIG. 8(C), the thread information item related to the second application E from the top is When the control 183 is operated, the thread target display area 184 is displayed as shown in FIG. The displayed content and the displayed content in the preview display area 185 are displayed in accordance with the thread information icon 18 You can switch to the thread related to 3.

[0111] Here, we will explain how messages are exchanged (sent and received) in App E via System 1. For example, in the situation shown in FIG. 9(A), if you enter "Thank you" in the message input field 186A, If you enter the text, it will look like the one shown in Figure 9(B). In this situation, pressing the send button 18 When 6B is operated, the user terminal 3 displays the content input in the message input field 186A. (Text: Thank you.) to the user ID of the user terminal 3, thread target display The target of the thread displayed in area 184 and the type of the message app (app The information transmitted to the management server 2 is sent in association with the information E). Specifically, the content entered in the message input field 186A, the user ID, the thread The target of the message and the type of message app (app E) are combined to form "Sent Message Information" It is called "News."

[0112] When the management server 2 receives the transmission message information, the transmission message information is reflected. In this way, the thread information table 24b relating to the thread in the server storage unit 23 is updated. Specifically, the message sent by the application E related to the user ID included in the message sent by the application E is updated. The thread information table 24b containing the target of the thread 24b, the content of the message, the date and time, and the user as the sender. The management server 2 stores the transmitted message information in association with the application. As a result, the server 5E of the application E also receives the user and the server 5E. It can update data about threads that consist of red targets.

[0113] Furthermore, when the management server 2 receives the transmission message information, the transmission message information is reflected The preview display area 185 is updated so that the image shown in FIGS. As shown in (B), until the send button 186B is operated, the subject (Y The message "Got it" sent by MD is displayed at the top of the preview display area 185. The message is displayed at the bottom, and the message is the latest message, but the send button 186B is As a result of this operation, the message "Thank you" sent by the user is deleted as shown in FIG. 10(A). A speech bubble saying "I'm going to show you the preview." is displayed at the bottom of the preview display area 185. , and the other displayed message bubbles will be replaced by the newly displayed bubble. Shift up by minutes.

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

[0115] When the management server 2 receives the information transmitted from the server 5E of the application E, the management server 2 Specifically, the server 5E of the application E updates the server storage unit 23 to reflect the information. The information indicated by the destination of the message included in the information sent from the user information table 24a to identify the user ID, and the thread related to the application E related to the user ID In the information table 24b, the thread related to the thread formed with the target of the thread In the message information table 24b, the contents of the message are displayed along with the date and time of the message. The sender of the message is stored in association with the originator.

[0116] Furthermore, when the management server 2 receives the information transmitted from the server 5E of the application E, The preview display area 185 is updated to reflect this information. Let's assume the message you received was "You're welcome." As shown in Figure 10(A) to Figure 10(B), a message was sent from the thread target (YMD). Until the message is sent, the message "Thank you" sent by the user will be previewed. The message is displayed at the bottom of the display area 185, and the message is the most recent message. However, the subject of the thread (YMD) sent a message, The speech bubble saying "You're welcome" sent by the target of the message appears in the preview area 18 It is displayed at the bottom of the 5, and the other displayed messages are displayed in speech bubbles. , and shift up by the amount of the newly displayed speech bubble.

[0117] 9 and 10, the main function screen 18 relating to the application E is displayed. When (when the App E Individual Display Button 182KE is selected) via System 1 I explained about message exchange (sending and receiving) in the application E, but When the main function screen 18 for all message applications is displayed, Messages and messages in App E via System 1 (with App 182Z selected) For sending and receiving, the selected thread information icon 183 is displayed as shown in Figure 18 9 and 10. That is, for a specific messaging app: When the main function screen 18 relating to the application is displayed (when the application is associated with the application), When the individual display button 182K is selected) and the linked app When the main function screen 18 for all message apps is displayed (when the full display button is pressed), When the thread information icon 182Z is ​​selected, the thread information icon 182Z is ​​displayed for the same thread. Similarly, by selecting 83, you can exchange messages (send and receive) via System 1. The device is configured to be able to perform the following operations:

[0118] Although the details will not be described, the situation shown in FIG. 8(B), and the situations shown in FIG. 8(C) and FIG. In this case, when the individual display button 182K is selected, messages related to a specific message app are displayed. When the main function display button 140 is operated while the main function screen 18 is displayed, The full display button 182Z is ​​switched to the selected state, and all the systems linked to the system 1 are displayed. The thread information icon for all messaging apps (in this case, App E and App C) Furthermore, as shown in FIG. 8(A), the system All messaging apps linked to System 1 (in this case, App E and App C) Even when the thread information icon 183 is displayed, as illustrated in FIGS. For all linked messaging apps, you can see the status of messages in real time. It is assumed that messages can be retrieved and updated.

[0119] In addition, in the situation shown in FIG. 10(B), when the message application list display button 141 is operated, When the application is created, the management server 2 displays the application use screen including the main function screen 18 on the user terminal 3. The time window 1E is switched to the top window 1C. 10 is a diagram illustrating a specific example of a top window 1C in this case.

[0120] As shown in FIG. 11(A), the right pane 10BR of the top window 1C displays a message. The page application list screen 15 is displayed. However, in this situation, System 1 and Application C, Since the link with app E has been completed, app C image 16C shows the link with app C. A button to accept the operation to cancel the connection (App C disconnection button 162C) is displayed, The app E image 16E includes a button (app E) the unlink button 162E) is displayed.

[0121] Here, for example, it is assumed that the application E cooperation cancellation button 162E is operated. When the application E linkage cancellation button 162E is operated, the management server 2 is notified of the user ID. At the same time, a command indicating a request to terminate collaboration with application E (application E collaboration termination request) is sent. The management server 2 sends the application E cooperation end request command to the management server 2. When the user terminal 3 receives the message, the user terminal 3 is notified of the final termination of the link with the message application. A confirmation window (final confirmation window 19 for ending app integration) will be displayed. The final confirmation window 19 for ending the app link is superimposed on the message app list screen 15. It will be displayed.

[0122] FIG. 11(B) shows a specific example in which a final confirmation window 19 for ending application linkage is displayed. As shown in FIG. 11(B), the final confirmation window 19 for ending application linkage is horizontally long. Although it is rectangular, the specific contents of the final confirmation window 19 for ending app integration are as follows: can be changed appropriately.

[0123] In addition, the final confirmation window for ending app integration 19 asks if you want to end the integration with the app. The final confirmation message (Figure 11(B)) reads, "Delete the tab. Are you sure?" ") is displayed, and a button to end the connection (Connection End Execution Button 19) 1), and a button to cancel the termination of the link (Cancel Link Termination button 192) are displayed. is shown.

[0124] When the link termination cancellation button 192 is operated, the user terminal 3 Then, a command indicating a request to cancel the termination of the link with app E (app link termination The management server 2 sends a cancellation command to the management server 2. When the request command is received, a final confirmation window for ending application linkage is displayed on the user terminal 3. Eliminate 19.

[0125] On the other hand, when the link termination execution button 191 is operated, the user terminal 3 Both commands indicate a request to terminate collaboration with app E (application collaboration termination execution). The management server 2 sends an application link termination execution request command to the management server 2. When the command is received, a request to terminate the link is sent along with user information based on the user ID. The server 5E of application E sends a command indicating that the application has been The server 5E, based on the user information, establishes a link with the system 1 for the user. Terminate.

[0126] In addition, the management server 2 stores data related to the application E of the user in the server storage unit 23. Furthermore, the management server 2 sends a final confirmation message to the user terminal 3 to end the application linkage. The window 19 is closed, and the application E linkage cancellation button 162E is pressed to cancel the application E linkage. Switch to the operation screen display button 161E to return the app E image 16E to the state before linking. In addition, the management server 2 can also select the application E login button from the right-side pane switching operation screen 14. The login button 143E is deleted and the login button 143E of the application C that was displayed later is also deleted. Change the display position of 3C as appropriate.

[0127] Here, a specific example of when the app E linkage cancellation button 162E is operated will be described. However, even if the app C link cancellation button 162C is operated, the app E link cancellation button 16 The link ends just like when 2E is operated. Also, this process is not applicable to other messages. The same applies to the application. In this embodiment, for any message application, The same final confirmation window 19 for ending app integration will be displayed. The display content of the final confirmation window 19 for terminating app integration changes depending on the type of Sage app. It may be arranged so that

[0128] According to the system 1 (management server 2) configured as above, multiple types of messages can be A system that can centrally manage applications (applications A to H) In response to a request for cooperation of the message application from the user terminal 3, A linkage management means (linkage management) that links the application to the system 1 (management server 2) a management unit 22b) and a message application linked to the system by a linkage management means If there are multiple applications, the linked applications will be displayed on the condition that the user is logged in to the user terminal 3. Information about all messaging threads (thread info icon 18) 3) can be displayed all at once. Therefore, multiple message applications The convenience and versatility of integrating and centrally managing these is improved. 10BR, other than the main function screen 18 for using the message app in the system 1 screen (message app list screen 15, app login screen 17, etc.) is displayed. Even when the main function display button 140 is inactive, the main function display button 140 is always displayed. When 40 is operated, information about threads related to all linked messaging apps will be displayed. In other words, you can display all the thread information (thread information icon 183) at once. When the full display button 182Z is ​​selected, the main function screen 18 is displayed. Furthermore, convenience and versatility are improved.

[0129] In addition, information about threads related to all linked messaging apps (thread Even if the app information icon 183) can be displayed all at once, the window As long as 1E is displayed, the individual display button 182K is always displayed, and the individual When the separate display button 182K is operated, information about the thread related to the message application is displayed. The thread information icon 183 is displayed, which further improves the convenience. , information about threads related to one of the linked messaging apps (thread information As long as the notification icon 183) is displayed, the full display button 182Z is ​​always When the full view button 182Z is ​​pressed, all linked messages are displayed. Information about threads related to the app (Thread Information Icon 183) can be displayed together. This will further improve convenience.

[0130] (Modification of the first embodiment) Next, a modified example of the pachinko gaming machine PY1 according to the first embodiment will be described. The modifications described below can also be combined as appropriate.

[0131] In the first embodiment, the right pane 10BR of the application use window 1E includes a link Display information related to the thread of the message app (Thread information icon 1 83, thread target display area 184, preview display area 185) The body display button 182Z and the individual display button 182K are constantly displayed. Alternatively, or in addition, when using the app, not only window 1E but also top window 1C and In the left pane 10BL of the application link window 1D, the full view button 182Z, and individual display button 182K, or buttons with equivalent functions are permanently displayed. It may be so arranged that the information is displayed.

[0132] In the first embodiment, the system 1 is connected to the application login screen 17 by inputting an input operation. When the link with the message app related to the app login screen 17 is started, the right pay On the login screen 17 of the application, the full display button 182Z is ​​selected. The main function screen 18 is displayed in the state where the application login screen 17 is displayed. Main function screen 1 with individual display button 182K related to the message app selected It may be possible to switch to 8.

[0133] Furthermore, in the first embodiment, when the main function display button 140 is operated, the whole display button The screen switches to the main function screen 18 with button 182Z selected. When the individual display button 182K related to the linked app is selected, or when the When an individual display button 182K relating to a linked app is selected, The main function screen 18 is displayed with the individual display button 182K relating to the item selected. It is also possible to do so.

[0134] (Second embodiment) Next, a second embodiment of the present invention will be described. In some cases, the same reference numerals and terms may be used to refer to corresponding components.

[0135] In the second embodiment, the main function display button 140 in the first embodiment is not provided. As in the first embodiment, multiple types of message accounts linked to the system 1 are Information about threads related to the application (thread information icon 183) is displayed together. In the second embodiment, when the individual display button 182K in the first embodiment is selected, As if it were a thread, information about the thread (thread information app) is displayed on a per-message app basis. In the second embodiment, the whole display button 182Z and The individual display button 182K is also not provided.

[0136] In the second embodiment, a window 1A for starting application use and a window 1B for user registration are The top window 1B is configured in the same manner as in the first embodiment. , Window 1D when connecting with the app, and Window 1E when using the app are the first implementation. As in the embodiment, the variable display area 10B is divided into a left pane 10BL and a right pane 10B. In addition, the start screen, user registration screen, and message app The list screen 15 and the application login screen 17 are configured in the same manner as in the first embodiment. That is, the method of user registration related to the system 1 and the method of linking with various messaging apps is configured in the same manner as in the first embodiment.

[0137] As will be described later, in the second embodiment, the main function screen 1 according to the first embodiment 8, the screen where various messaging apps are used in the system 1 is called "App Use". The app usage screen 50 is referred to as the "app usage screen 50." The app usage screen 50, like the main function screen 18, is The application use screen 50 is displayed on the system 10BR. This is a general term for the screens that use the application, such as the application login screen 17 in the first embodiment. Therefore, the application usage screen 50 displays the application A-related There are a pre-A use screen 50A to an application use screen 50H relating to application H.

[0138] Here, for example, when the message application list screen 15 is displayed, When the mobile operation screen display button 161E is operated, the first As in the embodiment, the application E login screen 17E is displayed in the right pane 10BR. However, the left pane 10BL does not display the image data that was not displayed in the first embodiment. Specifically, the app E login button 143E is displayed. The Pre-E login button 143E is displayed when the App-E cooperation operation screen display button 161E is operated. It is displayed according to what has happened.

[0139] The application E login button 143E corresponds to the application E individual display button 182K in the first embodiment. The right pane 10BR has the same functions as the app E, and the app usage screen 5 for the app E is displayed. 0 (application E use screen 50E). As with the in button 143E, an application cooperation operation screen display button 161 for other applications is When the button is operated, the application login button 143 related to the application is displayed. That is, the application login button 143 is an operation means for displaying the application usage screen 50. The application login button 143 is a general term for the application A login button related to the application A. There is an application G login button 143A to an application G login button 143G.

[0140] The design (shape, pattern, display content) of the application login button 143 can be set appropriately. However, in this embodiment, the application login button 143 is not displayed in the message application list. The display button 141 and the setting screen display button 142 are formed in the same size and shape. In the part, the app that was also displayed in the message app image 16 corresponding to the app A logo representing the pre-

[0141] The display position of the application login button 143 can also be set appropriately. Now, under the setting screen display button 142, the applications are displayed in the order in which they were linked, from top to bottom. are displayed side by side.

[0142] By inputting an input operation on the application login screen 17, the application is linked to the system 1. When the application starts, operation on the application login button 143 related to the application becomes valid. In the right pane 10BR, the app usage screen 50 related to the app is displayed. When the relevant screen (application login screen 17, application usage screen 50) is displayed, When the application login button 143 relating to the application is operated, The display content is switched to the application use screen 50 related to the application. The operation of the login button 143 is to log in to the application while using the system 1. Configure (access) requests.

[0143] When the application login button 143 is operated, the user terminal 3 A command indicating a login request to the app (app login request) along with the user ID The management server 2 sends the application login request command When receiving the request, the application server 5 requests synchronization of the data related to the user. and update the data relating to the user (the data relating to the user held by the server 5) The server stores the information in the server storage unit 23, and the application usage screen reflects the latest information about the application. The surface 50 is displayed on the user terminal 3.

[0144] In the situation shown in FIG. 12(A), an input operation on the login screen 17E of the application E is performed. If collaboration with E is performed, the right pane 10BR displays the app E usage screen 50E. FIG. 12(B) shows an example of an application use window 1E including an application E use screen 50E. As shown in FIG. 12(B), the application E usage screen 50E is roughly divided into left and right areas. Both the left and right sides are formed in a vertically long rectangle.

[0145] The left side of the application E usage screen 50E is divided into three sections along the vertical direction. At the top left corner of the application E screen 50E, a horizontally long rectangular title display area 50E1 is displayed. A horizontally long rectangular thread search area 50E2 is formed directly below the title display area 50E1. A vertically long rectangular thread information list display area 50E2 is formed directly below the thread search area 50E2. 0E3 is formed.

[0146] The title display area 50E1 displays a character string indicating the name of the message exchange related to the application E. (In this embodiment, "Conversation") is displayed as the title. Thread search area 50E2 In the search information input field 51, a search information input field 51 is provided for searching threads. Although a detailed description of 1 will be omitted, the search information input field 51 is used to search for threads such as keywords. It is possible to input information to be searched, such as keywords entered in the search information input field 51. In other words, the search information input field 51 is It has the same function as the search information input field 181 in the form.

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

[0148] In addition, the display contents inside the thread information icon 53E are the same as those in the first embodiment. It is configured similarly to the information icon 183E. In addition, the thread information icon 53 E can accept a selection operation in the same way as the thread information icon 183E in the first embodiment. When the application E use screen 50E is displayed, The thread information icon 53E associated with the most recently updated thread is selected. It is assumed that the state is as follows.

[0149] The display content on the right side of the application E usage screen 50E is the same as the main function screen 1 in the first embodiment. 8. For example, in the situation shown in FIG. 12(B), When the thread information icon 53E displayed second is selected, the application E screen is displayed. The display contents on the right side of the surface 50E are displayed at the top as shown in FIGS. 12(B) to 12(C). The thread information icon 53E is displayed second from the top. The content changes to that corresponding to the thread information icon 53E.

[0150] Furthermore, when the message application list display button 141 is operated in the situation shown in FIG. 12(C), 13(A), the right pane 10BR is switched from the application E use screen 50E to the application E use screen 50F. The screen switches to the message app list screen 15. In this case, app E is connected to system 1. Since they are linked, the application E image 16E is displayed in the same manner as in the situation of FIG. 7(A) in the first embodiment. An app E link cancellation button 162E is displayed.

[0151] Then, when the message application list display button 141 is operated in the situation shown in FIG. 13(A), In this case, when the application C cooperation operation screen display button 161C is operated, the screen shown in FIG. 13(B) is displayed. So, the right pane 10BR goes from the message app list screen 15 to the app C login screen It will switch to 17C. In addition, just as when the App E login screen 17E is displayed, A new App C login button 143C is added. When System 1 starts to link with App C by inputting an operation on the application screen 17C, In 10BR switches from the App C login screen 17C to the App C usage screen 50C.

[0152] Although the description of the screen configuration of the application C use screen 50C will be omitted, unlike the first embodiment, In the second embodiment, the application use screen 50 is appropriately set according to the application. The screen configurations of the application A use screen 50A to the application G use screen 50G are different from each other. do.

[0153] For example, when the app C usage screen 50C is displayed in the right pane 10BR, When the app E login button 143E is operated, the right pane 10BR displays the app C login screen. The screen 50C is switched to the app E usage screen 50E.

[0154] In this way, according to the system 1 of the second embodiment, the left pane 10BL is always connected to the left pane 10BL. The app login button 143 for the messaging app you are using will be displayed. If the app usage screen 50 relating to the message app is not displayed on the pane 10BR, In this case, operate the app login button 143 related to the message app, and The application usage screen 50 for the message application is immediately displayed on the 10BR. You can use the messaging app on System 1.

[0155] A message application to be used from among the plurality of message applications A selection screen (right pane switching operation screen 14) that can accept an operation to select Selection screen display means to be displayed (top window 1C, application link window 1D, A management server (2) that displays a window (1E) on a user terminal (3) when using the application, and a selection screen The message application corresponding to the message application selected by the operation A usage screen display method for displaying an application usage screen (application usage screen 50) on a user terminal. It also has a display switching management section, so multiple message applications can be integrated into one This improves convenience and versatility in terms of centralized management.

[0156] In addition, the user terminal 3 may be configured to select any one of the plurality of message applications. Even when the usage screen for the application is displayed, the selection screen is displayed and the user A message application among multiple message applications is installed on user terminal 3. When the usage screen for the application is displayed, multiple messages may appear by operating the selection screen. When another messaging application is selected in the application, the selection screen appears. The means is for transmitting a message from a usage screen related to one message application to another message application. It will switch to the application screen, so you can integrate multiple messaging applications. This will improve convenience and versatility by centrally managing the data.

[0157] (Other change examples) Furthermore, the first and second embodiments described above are merely examples, and the present invention is not limited to these. The present invention is not limited to the above, and various improvements and modifications are possible within the scope of the present invention. Of course.

[0158] For example, since the user terminal 3 is configured as a personal computer, the management server 2 3 displayed a window 10 for the centralized management system of messaging apps, but If the device is a smartphone or tablet, Instead of displaying it as a window on the screen of the smartphone or tablet, (Display section) Overall, display contents related to the window 10 for the message application unified management system In this case, the shape of the screen (display) of the smartphone or tablet may be Depending on the state and size, the screen configuration of the window 10 for the message application unified management system may be The layout and design may be adjusted as appropriate.

[0159] In the above embodiment, the system 1 has eight types of message apps, apps A to H. However, the types of messaging apps that can be linked can be changed as needed. Furthermore, by performing a predetermined operation on the management server 2, it is possible to It may be possible to add or delete them as needed.

[0160] In the above embodiment, the application login screen 17 is provided by the server 5. The layout of the app login screen 17 varies depending on the type of messaging app. However, the screen configuration (layout) of the application login screen 17 may be made common. In the first embodiment, the main function screen 182 is displayed with the individual display button 182K selected. The screen layout of the 8 was standardized regardless of the type of messaging app. , as well as the application login screen 17, the main function screen 18 is redirected to the server 5 (Server 5A to Server 5H), and the screen configuration of the main function screen 18 The layout may be different depending on the type of message app.

[0161] In the above embodiment, the management server 2 (the cooperation management unit 22b) is configured to grant general authority. The process to request permission (OAuth2.0) is performed for applications A to H (server 5A) To start collaboration with App A to App H (Server 5A to Server 5H), The control content for starting collaboration with OAuth 2.0 is not limited to OAuth 2.0 and can be changed as appropriate. is also good.

[0162] In the second embodiment, the right pane switching operation screen 14 is constantly displayed, and the right pane switching operation screen 14 is always displayed on the user terminal. Whenever the third user is logged in to System 1 (Management Server 2), the third user can access another application. You can switch to the main screen, but you cannot switch to the right pane switching operation screen14 or the message app. The pre-list display button 141 and the application login button 143 are not permanently displayed. , window 1D when connecting with the app and / or window 1E when using the app are displayed. When you press a button, the right pane switching operation screen 14 or a message Even if you set the app list display button 141 and app login button 143 to be displayed, It is good. In addition, due to differences in conditions such as screen size, the user terminal 3 may be configured as a personal computer. If the right pane switching operation screen 14 is permanently displayed as in the second embodiment, If the user terminal 3 is a smartphone or a tablet, a certain button When you operate the button, the right pane switching operation screen 14 or the message app list display button 1 41 and an application login button 143 may be displayed.

[0163] In the above embodiment, the server control unit 22 is a server storage unit provided in the management server 2. 23 realizes various functions based on various programs and information stored in it, The various programs stored in the server storage unit 23 are managed via the communication network 4. Alternatively, the information may be stored in a cloud base connected to the management server 2.

[0164] Furthermore, the processes disclosed in the above embodiments may be implemented using a single CPU, multiple CPUs, or AS. The present invention may be implemented in hardware such as an IC, or a combination thereof. The processes disclosed in the embodiments are recorded on a recording medium that records a program for executing the processes. The present invention can be realized in various ways, such as by a medium or a method.

[0165] The preceding paragraphs in this [Mode for Carrying Out the Invention] include the following Inventions A to D. In the description of inventions A to D, the corresponding embodiments of the inventions are as follows: The names and expressions of the components and the symbols used in the drawings are added in parentheses for reference. However, the elements such as means constituting each invention are not limited to these appendices.

[0166] The system according to invention A is A system capable of centrally managing multiple types of message applications. , In response to a message application link request from a user terminal, the message application a linkage management unit (linkage management unit 22b) for linking an application to the system; The message application linked to the system by the linkage management means If there are multiple messages, the multiple messages can be read on the condition that the user is logged in to the user terminal. Indicates a specific unit (thread) related to each message exchange in a page application. Information (Thread Information Icon 183) can be displayed all at once on a specific screen (Main Function Screen 1 8) on the user terminal, and an operation unit (main function display button 140) on the user terminal. The application link window 1D and the application use window 1E are displayed on the user terminal 3. a display switching management unit 22c); When the specific screen is not displayed on the user terminal (for example, the top window When the operation unit is operated (when the specific screen is displayed), the specific screen is A specific screen display means for displaying the main function screen 18 on the user terminal 3 and a display switching management unit (22c) that switches the display mode.

[0167] The system according to invention B is A system according to Invention A, When the specific screen is displayed on the user terminal, the plurality of message applications and accepting an operation to collectively display information indicating the specific unit relating to the entire application. and an overall display operation section (overall display button 182Z) that can display information indicating the specific unit. Individual display operations that can accept operations to display messages on a per-message application basis (Individual display button 182K: App A individual display button 182KA ~ App H individual display button Tan 182KH) and The individual display operation unit displays a message in association with each of the plurality of message applications. is shown, When the whole display operation unit is operated, a message relating to all of the plurality of message applications is displayed. displaying information indicating the specific units collectively; When the individual display unit is operated, a message application associated with the individual display operation unit is displayed. and displaying information indicating the specific unit related to the application.

[0168] The server according to the invention C is A server capable of centrally managing multiple types of message applications, In response to a message application link request from a user terminal, the message application Linking an external device related to the application to the server, If there are multiple external devices related to the message application linked to the server, In this case, a specific unit relating to the exchange of messages of each of the plurality of message applications A specific screen that can display information (thread information icon 183) indicating the position (thread) of the thread an operation capable of accepting an operation for displaying a main function screen 18 on the user terminal; a main function display button 140) on the user terminal; When the specific screen is not displayed on the user terminal (for example, the top window When the operation unit is operated (when the specific screen is displayed), the specific screen is A server that displays the information on the user terminal.

[0169] The server according to the invention D is A server according to Invention C, When the specific screen is displayed on the user terminal, the plurality of message applications and accepting an operation to collectively display information indicating the specific unit relating to the entire application. and an overall display operation section (overall display button 182Z) that can display information indicating the specific unit. Individual display operations that can accept operations to display messages on a per-message application basis (Individual display button 182K: App A individual display button 182KA ~ App H individual display button Tan 182KH) and The individual display operation unit displays a message in association with each of the plurality of message applications. is shown, When the whole display operation unit is operated, a message relating to all of the plurality of message applications is displayed. displaying information indicating the specific units collectively; When the individual display unit is operated, a message application associated with the individual display operation unit is displayed. a server that displays information indicating the specific unit related to the application. [Explanation of symbols]

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

Claims

1. A system that can centrally manage multiple types of messaging applications, A linkage management means that links a messaging application to the system in response to a linkage request from a user terminal, If there are multiple messaging applications linked to the system by the aforementioned linkage management means, the user terminal is provided with an operation unit display means that, provided the user terminal is logged in, can display an operation unit on the user terminal that can accept an operation to display a specific screen on the user terminal that can display information indicating a specific unit related to the message exchange of each of the multiple messaging applications in a single location. A system characterized by comprising a specific screen display means that causes the specific screen to be displayed on the user terminal when the operation unit is operated.

2. A system that can centrally manage multiple types of messaging applications, A linkage management means that links a messaging application to the system in response to a linkage request from a user terminal, If there are multiple messaging applications linked to the system by the aforementioned linkage management means, the user terminal displays an operation unit that can receive an operation to display a specific screen on the user terminal that can display information indicating a specific unit related to the message exchange of each of the multiple messaging applications in a single display. A system characterized by comprising a specific screen display means that causes the specific screen to be displayed on the user terminal when the operation unit is operated while the specific screen is not displayed on the user terminal.

3. A server capable of centrally managing multiple types of messaging applications, In response to a request from a user terminal to connect a messaging application, the external device related to the messaging application is connected to the server. If there are multiple external devices related to the messaging application linked to the server, an operation unit capable of receiving an operation to display a specific screen on the user terminal that can display information indicating a specific unit related to the messaging exchange of each of the multiple messaging applications in a single display, A server characterized in that the operation unit is operated to display the specific screen on the user terminal.

4. A server capable of centrally managing multiple types of messaging applications, In response to a request for integration from a messaging application, the external device related to that messaging application is connected to the server. If there are multiple external devices related to the messaging application linked to the server, an operation unit capable of receiving an operation to display a specific screen on the user terminal that can display information indicating a specific unit related to the messaging exchange of each of the multiple messaging applications in a single display, A server characterized in that, when the operation unit is operated while the specific screen is not displayed on the user terminal, the specific screen is displayed on the user terminal.