Information processing device, information processing system, task management method and program

Abstract

To easily create tasks and manage the task by associating with a person in charge.SOLUTION: An information processing apparatus that is capable of communicating, via a network, with a user terminal used by a user, comprises: a screen transmitting unit configured to initially display at least a last message in a dialogue upon receiving an acquisition request transmitted in response to an operation on a dialogue screen for mutually transmitting and receiving messages between a plurality of users, and transmit screen data for displaying a registration screen in which a task and a person in charge can be entered to the user terminal; and a task registration unit configured to, upon receiving a registration request transmitted in response to an operation on the registration screen, store, in a storage unit, the task and the person in charge in association with each other.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing system, a task management method, and a program. [Background technology]

[0002] In recent years, information processing devices that allow users to send and receive messages to each other via a communication network for the purpose of information sharing, communication, etc. in companies or private settings have been used. In addition, information processing devices that manage tasks that users must perform have also been used.

[0003] For example, Patent Document 1 discloses an invention for sharing and managing task statuses between users of terminals. In the invention disclosed in Patent Document 1, an information processing device extracts content to be managed as a task from a message received from a first terminal, transmits a task based on the extracted content to a second terminal, and updates the task status based on information received from the first terminal or the second terminal. Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional technologies have the problem that the information required for task management is sometimes registered without being clear. For example, tasks requested during a conversation between users may be buried in messages that are added one after another in chronological order, and may not be managed strictly. This can lead to oversights or delays in tasks due to differences in understanding between the two parties.

[0005] Furthermore, since the main focus is on dialogue, if you cannot quickly and easily create a task when you realize that a message is a task, you may forget about it.

[0006] In view of the above technical problems, an embodiment of the present invention aims to enable tasks to be easily created and to manage tasks in association with persons in charge. [Means for solving the problem]

[0007] In order to solve the above problem, one embodiment of the information processing device is an information processing device that can communicate with a user terminal used by a user via a network, and is equipped with a screen sending unit that, upon receiving an acquisition request sent in response to an operation on an interactive screen for sending and receiving messages between multiple users, initially displays at least the final message in the interaction and sends screen data to the user terminal that displays a registration screen on which a task and a person in charge can be input, and a task management unit that, upon receiving a registration request sent in response to an operation on the registration screen, associates the task with the person in charge and stores them in a memory unit. [Effects of the Invention]

[0008] According to one embodiment of the present invention, tasks can be easily created, and tasks can be managed in association with people in charge. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of an information processing system according to an embodiment; [Figure 2] FIG. 1 is a diagram illustrating an example of a hardware configuration of a computer according to an embodiment. [Figure 3] FIG. 1 is a diagram illustrating an example of a hardware configuration of a smartphone according to an embodiment. [Figure 4] FIG. 1 is a diagram illustrating an example of a functional configuration of an information processing system according to an embodiment. [Figure 5] FIG. 10 is a diagram illustrating a processing procedure of a task management method according to an embodiment. [Figure 6] FIG. 10 is a diagram illustrating a processing procedure of a task management method according to an embodiment. [Figure 7] FIG. 10 illustrates an example of an interactive screen in one embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of a registration screen according to an embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of a confirmation screen according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a confirmation screen according to an embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of a details confirmation screen according to an embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of a message sending screen according to an embodiment. [Figure 13] FIG. 10 illustrates an example of an interactive screen in one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the drawings, components having the same functions are designated by the same reference numerals, and duplicated explanations will be omitted.

[0011] [Embodiment] <Overall configuration of information processing system> The configuration of the information processing system according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a conceptual diagram showing an example of the overall configuration of the information processing system according to this embodiment.

[0012] 1, the information processing system 1 in this embodiment includes a communication management server 10 and two or more user terminals 20. Hereinafter, when distinguishing between the multiple user terminals 20, they will be referred to using sub-numbers such as "user terminal 20-1" and "user terminal 20-2."

[0013] The communication management server 10 and the user terminal 20 are each connected to a communication network N1. The communication network N1 is configured so that the devices connected thereto can communicate with each other.

[0014] The communication network N1 is constructed by a network using wired communication, such as the Internet, a local area network (LAN), or a wide area network (WAN). The communication network N1 may include not only wired communication but also wireless communication such as a wireless LAN or short-range wireless communication, or a network using mobile communication such as WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), or 5G (5th Generation).

[0015] The communication management server 10 is an information processing device that provides, via a communication network N1, a communication service that enables a plurality of user terminals 20 to communicate with each other. The communication service in this embodiment is a service that combines a dialogue management function and a task management function.

[0016] The dialogue management function is a function for managing dialogues between multiple users. The dialogue management function in this embodiment can be used for one-on-one dialogues between two users, or for dialogues in a group including three or more users.

[0017] In this embodiment, a dialogue is realized by mutually sending and receiving messages between multiple users. A message in this embodiment may be composed of text, images, audio, video, or a combination thereof. Examples of dialogue in this embodiment include text chat, audio calls, and video conferences.

[0018] The task management function is a function for registering work to be performed by a user as a task and managing detailed information, progress, etc. In this embodiment, a task is an independent work that occurs at the request of another user while performing daily work. However, the task in this embodiment is not limited to this, and may be, for example, a subdivided work assigned to each user in a project to achieve a single objective.

[0019] The communication service of this embodiment can register tasks that arise during a dialogue by linking the dialogue management function with the task management function. Furthermore, the communication service of this embodiment can share and manage detailed information and progress of registered tasks between users.

[0020] The communication management server 10 may be realized by one information processing device, or may be an information processing system realized by a plurality of information processing devices.

[0021] The user terminal 20 is an information processing terminal operated by a user of a communication service. The user terminal 20-1 is a user terminal used by a first user. The user terminal 20-2 is a user terminal used by a second user different from the first user.

[0022] A user can interact with other users by operating an interactive screen provided by the communication management server 10. A user can also launch a registration screen by operating the interactive screen, and can register a task by operating the registration screen. Furthermore, a user can check and edit information about a registered task using a confirmation screen provided by the communication management server 10.

[0023] An example of the communication management server 10 and the user terminal 20 is a computer. Another example of the user terminal 20 is a smartphone. Note that the communication management server 10 and the user terminal 20 are not limited to information processing devices as long as they are devices equipped with a communication function.

[0024] The communication management server 10 and the user terminal 20 may be, for example, an output device such as a PJ (Projector), an IWB (Interactive White Board: an electronic white board with a blackboard function that allows mutual communication), digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, network home appliances, automobiles (Connected Cars), notebook PCs (Personal Computers), mobile phones, smartphones, tablet terminals, game consoles, PDAs (Personal Digital Assistants), digital cameras, wearable PCs or desktop PCs.

[0025] <Hardware configuration of information processing system> The hardware configurations of the communication management server 10 and the user terminal 20 included in the information processing system of this embodiment will be described with reference to FIGS. 2 and 3. FIG.

[0026] <Computer hardware configuration> FIG. 2 is a diagram showing an example of a hardware configuration when the communication management server 10 or the user terminal 20 is realized by a computer.

[0027] As shown in FIG. 2, the computer in this embodiment includes a CPU 501, a ROM 502, a RAM 503, a HD 504, an HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, a bus line 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.

[0028] Of these, the CPU 501 controls the operation of the entire computer. The ROM 502 stores programs used to drive the CPU 501, such as the IPL. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 under the control of the CPU 501.

[0029] The display 506 displays various types of information such as a cursor, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various types of external devices. In this case, the external devices are, for example, USB (Universal Serial Bus) memories or printers. The network I / F 509 is an interface for data communication using the communication network N1. The bus line 510 is an address bus, a data bus, or the like for electrically connecting the components such as the CPU 501 shown in FIG. 2.

[0030] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 514 controls reading and writing of various data from a DVD-RW 513, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I / F 516 controls reading and writing (storing) of data from a recording medium 515, such as a flash memory.

[0031] <Smartphone hardware configuration> FIG. 3 is a diagram showing an example of a hardware configuration when the user terminal 20 is realized by a smartphone.

[0032] As shown in FIG. 3, the smartphone in one embodiment includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a CMOS sensor 405, an image sensor I / F 406, an acceleration / direction sensor 407, a media I / F 409, and a GPS receiver 411.

[0033] Of these, the CPU 401 controls the overall operation of the smartphone. The ROM 402 stores the CPU 401 and programs used to drive the CPU 401, such as the IPL. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads and writes various data, such as smartphone programs, under the control of the CPU 401. The CMOS (Complementary Metal Oxide Semiconductor) sensor 405 is a type of built-in imaging means that captures an image of a subject (mainly a self-portrait) under the control of the CPU 401 to obtain image data. Note that instead of a CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may also be used.

[0034] The imaging element I / F 406 is a circuit that controls the driving of the CMOS sensor 405. The acceleration / azimuth sensor 407 is a variety of sensors, such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I / F 409 controls the reading and writing (storage) of data from and to a recording medium 408, such as a flash memory. The GPS receiver 411 receives GPS signals from GPS satellites.

[0035] The smartphone also includes a long-distance communication circuit 412, a CMOS sensor 413, an image sensor I / F 414, a microphone 415, a speaker 416, an audio input / output I / F 417, a display 418, an external device connection I / F (Interface) 419, a short-distance communication circuit 420, an antenna 420a of the short-distance communication circuit 420, and a touch panel 421.

[0036] Of these, the long-distance communication circuit 412 is a circuit that communicates with other devices via the communication network N1. The CMOS sensor 413 is a type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 401. The image sensor I / F 414 is a circuit that controls the driving of the CMOS sensor 413. The microphone 415 is a built-in circuit that converts sound into an electrical signal. The speaker 416 is a built-in circuit that converts an electrical signal into physical vibrations to generate sound such as music or voice. The sound input / output I / F 417 is a circuit that processes the input and output of sound signals between the microphone 415 and the speaker 416 under the control of the CPU 401.

[0037] The display 418 is a type of display means such as a liquid crystal display or organic electroluminescence (EL) display that displays an image of a subject, various icons, etc. The external device connection I / F 419 is an interface for connecting various external devices. The short-range communication circuit 420 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 421 is a type of input means that allows a user to operate the smartphone by pressing the display 418.

[0038] The smartphone also includes a bus line 410. The bus line 410 is an address bus, a data bus, or the like for electrically connecting the components such as the CPU 401 shown in FIG.

[0039] <Functional configuration of information processing system> An example of the functional configuration of the information processing system in this embodiment will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the functional configuration of the information processing system in this embodiment.

[0040] <Communication management server functional configuration> As shown in FIG. 4, the communication management server 10 in this embodiment includes a dialogue management unit 101, a screen transmission unit 102, a task management unit 103, a dialogue history storage unit 111, a screen data storage unit 112, and a task information storage unit 113.

[0041] When the communication management server 10 is realized by a computer, the dialogue management unit 101, the screen transmission unit 102, and the task management unit 103 are realized, for example, by a program expanded from HD 504 to RAM 503 shown in Figure 2 and executed by the CPU 501, the HDD controller 505, or the network I / F 509.

[0042] When the communication management server 10 is realized by a computer, the dialogue history storage unit 111, the screen data storage unit 112, and the task information storage unit 113 are realized, for example, using the HD 504 shown in Fig. 2. Reading or writing of data stored in the HD 504 is performed, for example, via the HDD controller 505.

[0043] The dialogue history storage unit 111 stores history information (hereinafter also referred to as "dialogue history") related to dialogues managed by the dialogue management unit 101. The dialogue history in this embodiment includes, for example, identification information for identifying the dialogue (hereinafter also referred to as "dialogue ID"), identification information for identifying a user participating in the dialogue (hereinafter also referred to as "user ID") or identification information for identifying a group (hereinafter also referred to as "group ID"), messages sent and received within the dialogue, identification information for identifying the messages (hereinafter also referred to as "message ID"), information indicating the date and time when the messages were sent, and the user ID of the user who sent the messages.

[0044] The screen data storage unit 112 stores in advance the screen data to be transmitted to the user terminal 20 by the screen transmission unit 102. Each piece of screen data stored in the screen data storage unit 112 is, for example, screen data written in HTML (HyperText Markup Language) or the like, and may include an application written in JavaScript (registered trademark) or the like.

[0045] The screen data in this embodiment is, for example, screen data that displays an interactive screen, a registration screen, or a confirmation screen. The interactive screen is a screen for dialogue between multiple users. The registration screen is a screen for inputting information about a task (hereinafter also referred to as "task information") and registering the task. The confirmation screen is a screen for confirming and editing registered task information.

[0046] The task information storage unit 113 stores task information managed by the task management unit 103. The task information in this embodiment includes, for example, identification information for identifying the task (hereinafter also referred to as "task ID"), the content of the task (subject, tag information, and detailed content), importance, start date, deadline date, user ID representing the person in charge, user ID representing the requester, message ID of the message that requested the task (hereinafter also referred to as "requester message"), completion status (completed or uncompleted), read status (read or unread), etc.

[0047] The dialogue management unit 101 manages dialogues between multiple users. For example, when a dialogue is taking place between a first user and a second user, the dialogue management unit 101 transmits a message received from user terminal 20-1 to user terminal 20-2, and transmits a message received from user terminal 20-2 to user terminal 20-1. The dialogue management unit 101 also stores a dialogue history related to messages sent and received within the dialogue in the dialogue history storage unit 111.

[0048] In response to a request from the user terminal 20, the screen transmission unit 102 reads out the screen data stored in the screen data storage unit 112 and transmits it to the user terminal 20. The screen data transmitted by the screen transmission unit 102 is, for example, screen data that displays an interactive screen, a registration screen, a confirmation screen, etc.

[0049] In response to a request from the user terminal 20, the task management unit 103 stores task information in the task information storage unit 113. In response to a request from the user terminal 20, the task management unit 103 reads out task information from the task information storage unit 113 and transmits it to the user terminal 20.

[0050] <<Functional configuration of user terminal>> As shown in FIG. 4, the user terminal 20 in this embodiment includes a dialogue request unit 201, a screen request unit 202, a registration request unit 203, and a display control unit 204.

[0051] When the user terminal 20 is realized by a smartphone, the interaction request unit 201, the screen request unit 202, the registration request unit 203, and the display control unit 204 are realized, for example, by a program expanded from the EEPROM 404 shown in FIG. 3 onto the RAM 403, which is executed by the CPU 401 and the long-distance communication circuit 412.

[0052] The dialogue request unit 201 transmits a dialogue start request to the communication management server 10 in response to a user's operation on the dialogue screen. The start request includes identification information that identifies the dialogue partner. The dialogue partner may be a single user or a group including multiple users. If the dialogue partner is a single user, the start request includes a user ID. If the dialogue partner is a group, the start request includes a group ID.

[0053] In response to a user operation, the screen request unit 202 transmits a screen acquisition request to the communication management server 10. The acquisition request includes information indicating the screen to be acquired. The screen requested by the screen request unit 202 may be, for example, an interactive screen, a registration screen, a confirmation screen, etc.

[0054] In response to a user's operation on the registration screen, the registration request unit 203 transmits a task registration request to the communication management server 10. The registration request includes task information generated based on the information input by the user on the registration screen.

[0055] The display control unit 204 displays a screen on a display unit such as the display 418 based on the screen data received from the communication management server 10. The screens displayed by the display control unit 204 include, for example, an interactive screen, a registration screen, and a confirmation screen.

[0056] <Task management procedure> An example of the processing procedure of a task management method executed by the information processing system in this embodiment will be described with reference to Fig. 5 and Fig. 6. Fig. 5 and Fig. 6 are sequence diagrams showing an example of the processing procedure of the task management method in this embodiment.

[0057] In step S1, the display control unit 204 included in the user terminal 20-1 displays an interactive screen on a display unit such as the display 418 based on screen data for displaying the interactive screen. The screen data for displaying the interactive screen may be stored in advance in a storage unit such as the EEPROM 404 included in the user terminal 20-1, or may be obtained from the communication management server 10.

[0058] If the screen data of the interactive screen is stored in the storage unit, the display control unit 204 reads the screen data from the storage unit, and then displays the interactive screen on the display unit based on the read screen data.

[0059] When acquiring screen data of an interactive screen from the communication management server 10, the screen request unit 202 transmits an acquisition request for the interactive screen to the communication management server 10. In the communication management server 10, the screen transmission unit 102 reads out the screen data of the interactive screen from the screen data storage unit 112 and transmits it to the user terminal 20-1. The display control unit 204 displays the interactive screen on the display unit based on the screen data received from the communication management server 10.

[0060] In step S2, the dialogue request unit 201 included in the user terminal 20-1 accepts a dialogue start operation on the dialogue screen by the first user. The dialogue start operation is performed by specifying a dialogue partner. Next, in response to the dialogue start operation, the dialogue request unit 201 transmits a dialogue start request to the communication management server 10. The start request includes a user ID or group ID that identifies the dialogue partner. Here, it is assumed that the second user or a group including the second user is specified as the dialogue partner.

[0061] In step S3, the dialogue management unit 101 included in the communication management server 10 receives a dialogue start request from the user terminal 20-1. Next, the dialogue management unit 101 transmits a dialogue start notification to the user terminal 20-2 used by the dialogue partner based on the identification information of the dialogue partner included in the start request.

[0062] In step S4, the display control unit 204 included in the user terminal 20-2 receives a notification of the start of the dialogue from the communication management server 10. Next, the display control unit 204 displays the dialogue screen on the display unit based on screen data for displaying the dialogue screen. The screen data for displaying the dialogue screen may be stored in advance in a storage unit, as in the case of the user terminal 20-1, or may be obtained from the communication management server 10.

[0063] In step S5, a dialogue begins between user terminal 20-1 and user terminal 20-2. The dialogue management unit 101 included in the communication management server 10 transmits a message received from user terminal 20-1 to user terminal 20-2, and transmits a message received from user terminal 20-2 to user terminal 20-1. At the same time, the dialogue management unit 101 stores a dialogue history related to messages transmitted and received between user terminal 20-1 and user terminal 20-2 in the dialogue history storage unit 111.

[0064] <Dialogue screen> The dialogue screen in this embodiment will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the dialogue screen in this embodiment. The dialogue screen shown in Fig. 7 is an example of a dialogue screen for dialogue by text chat.

[0065] 7, the dialogue screen 1000 in this embodiment has a dialogue partner display field 1001, a message display area 1002, a message input field 1003, and a task management button 1004. The message display area 1002 has one or more message display fields 1002-n (=1, 2, . . .).

[0066] The dialogue partner display field 1001 displays information (such as name) that represents the dialogue partner. The message display area 1002 displays messages sent and received between the dialogue partner in chronological order. The message display area 1002 displays one or more message display fields 1002-n (=1, 2, . . .) that display the content of each message. In this embodiment, the message displayed in the message display field 1002-3 is called the "final message" in the dialogue. If a message is added after this, the added message becomes the "final message."

[0067] If message display fields 1002-n relating to all messages sent and received between the conversation partner cannot be displayed in message display area 1002, then as many message display fields 1002-n as possible may be displayed in order, starting with the most recently sent and received message, in message display area 1002. In this case, message display fields 1002-n relating to past messages may be displayed by scrolling message display field 1002.

[0068] A message to be sent to the conversation partner is entered in the message input field 1003. The message entered in the message input field 1003 is sent to the user terminal 20-2 used by the conversation partner via the communication management server 10. At the same time, a message display field 1002-n that displays the content of the sent message is added to the message display area 1002.

[0069] When the user presses the task management button 1004, a context menu for managing tasks is displayed. The context menu includes a task registration menu for registering tasks. When the task registration menu is selected by the user, the screen request unit 202 accepts an operation to launch a registration screen.

[0070] Returning to FIG. 5, the following explanation will be given. In step S6, the screen request unit 202 included in the user terminal 20-1 accepts an operation by the first user to launch a registration screen for the interactive screen. The operation to launch the registration screen is performed by specifying a requesting message. If the user does not specify a requesting message, the most recently sent or received message is specified as the requesting message. Next, in response to the operation to launch the registration screen, the screen request unit 202 transmits a request to acquire the registration screen to the communication management server 10. The request to acquire the registration screen includes information related to the dialogue ID of the dialogue and the requesting message.

[0071] In step S7, the screen transmission unit 102 included in the communication management server 10 receives a request to acquire a registration screen from the user terminal 20-1. Next, the screen transmission unit 102 acquires one or more messages including at least the final message in the dialogue from the dialogue history storage unit 111 based on the dialogue ID included in the request to acquire the registration screen.

[0072] In step S8, the screen transmission unit 102 included in the communication management server 10 reads out the screen data of the registration screen from the screen data storage unit 112. Next, the screen transmission unit 102 embeds one or more messages including at least the final message in the screen data of the registration screen. Then, the screen transmission unit 102 transmits the screen data of the registration screen to the user terminal 20-1.

[0073] In step S9, the screen request unit 202 included in the user terminal 20-1 receives the screen data of the registration screen from the communication management server 10. Next, the display control unit 204 displays the registration screen on the display unit based on the screen data of the registration screen.

[0074] <<Registration screen>> The registration screen in this embodiment will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the registration screen in this embodiment.

[0075] As shown in FIG. 8, the registration screen 1100 in this embodiment has a subject input field 1101, an importance input field 1102, a start date input field 1103, a deadline input field 1104, a person in charge input field 1105, a tag information input field 1106, a detailed content input field 1107, a requester input field 1108, and a registration button 1109.

[0076] The subject of the task is entered in the subject input field 1101. In this embodiment, a part of the requester's message included in the acquisition request is initially displayed in the subject input field 1101. The part of the requester's message may be, for example, a predetermined number of characters from the beginning, or a summary of the requester's message.

[0077] The importance of a task is input into the importance input field 1102. In this embodiment, the importance is a truth value representing whether or not the task is important. In this embodiment, the importance input field 1102 is configured with a toggle button that allows selection of whether or not the task is important. However, the importance in this embodiment is not limited to this, and may be a score that represents the degree of importance. In this case, the importance input field 1102 may be configured with a text box or a slider bar that allows a numerical value to be input.

[0078] The start date of the task is input in the start date input field 1103. The start date of the task is the date on which the task occurred (i.e., the date on which a message requesting a task was sent and received between users). In this embodiment, the current date is initially displayed in the start date input field 1103.

[0079] The deadline input field 1104 is where the deadline of the task is entered. The deadline of the task is the date by which the task should be completed. In this embodiment, the field is initially displayed as blank. However, the deadline is not limited to this, and the date obtained by adding a predetermined number of days to the current date may also be initially displayed.

[0080] The person in charge of the task is input in the person in charge input field 1105. The person in charge may be selected from users participating in the dialogue (if the dialogue is in a group, all users included in the group), or may be selected from users not participating in the dialogue. Multiple users may be set as the person in charge.

[0081] The tag information of a task is input in the tag information input field 1106. The tag information is information that indicates the type of task. The tag information may be selected from predetermined tag information, or an arbitrary character string may be input, or tag information input by another user may be selected. Multiple pieces of tag information may be set.

[0082] Detailed task content is entered in the detailed content input field 1107. At least the final message included in the acquisition request is initially displayed in the detailed content input field 1107. In this embodiment, the entire final message included in the acquisition request is initially displayed.

[0083] The requester of the task is input in the requester input field 1108. The requester is selected from the users participating in the dialogue (if the dialogue is in a group, all users included in the group). One user is set as the requester.

[0084] When the user presses the registration button 1109, the registration request unit 203 accepts the task registration operation. The registration request unit 203 generates task information based on the information entered in each input field of the registration screen 1100, and transmits a task registration request including the generated task information to the communication management server 10.

[0085] Returning to FIG. 5, in step S10, the registration request unit 203 included in the user terminal 20-1 accepts a task registration operation on the registration screen by the first user. Next, the registration request unit 203 generates task information in response to the task registration operation. The task information is generated based on the information entered on the registration screen 1100. Next, the registration request unit 203 transmits a task registration request to the communication management server 10. The registration request includes the task information.

[0086] In step S11, the task management unit 103 included in the communication management server 10 receives a task registration request from the user terminal 20-1. Next, the task management unit 103 stores the task information included in the registration request in the task information storage unit 113. The task information includes information about the content of the task (subject, importance, tag information, detailed content, etc.) and information for managing the task (start date, deadline date, person in charge, and requester). In other words, the task information storage unit 113 stores information about the content of the task and information for managing the task in association with each other.

[0087] 6 will be described. In step S12, the screen request unit 202 included in the user terminal 20-1 accepts an operation to launch a confirmation screen by the first user. The operation to launch the confirmation screen is, for example, an operation on a main menu provided by the communication management server 10. Next, in response to the operation to launch the confirmation screen, the screen request unit 202 transmits a request to acquire the confirmation screen to the communication management server 10. The acquisition request includes the user ID of the user who performed the launch operation (here, the first user).

[0088] In step S13, the screen transmission unit 102 included in the communication management server 10 receives a request to acquire a confirmation screen from the user terminal 20-1. Next, the task management unit 103 reads task information related to the user from the task information storage unit 113 based on the user ID included in the acquisition request. The task information related to the user includes task information related to tasks for which the user is registered as the person in charge (hereinafter also referred to as "assigned tasks") and task information related to tasks for which the user is registered as the requester (hereinafter also referred to as "requested tasks"). The task management unit 103 sends the read task information to the screen transmission unit 102.

[0089] In step S14, the screen transmission unit 102 included in the communication management server 10 reads out screen data of the confirmation screen from the screen data storage unit 112. Next, the screen transmission unit 102 receives task information from the task management unit 103. Subsequently, the screen transmission unit 102 embeds the task information in the screen data of the confirmation screen. Then, the screen transmission unit 102 transmits the screen data of the confirmation screen in which the task information is embedded to the user terminal 20-1.

[0090] In step S15, the screen request unit 202 included in the user terminal 20-1 receives screen data for the confirmation screen from the communication management server 10. Next, the display control unit 204 displays the confirmation screen on the display unit based on the screen data for the confirmation screen.

[0091] <Confirmation screen> The confirmation screen in this embodiment will be described with reference to Fig. 9 and Fig. 10. Fig. 9 is a diagram showing an example of the confirmation screen in this embodiment. The confirmation screen shown in Fig. 9 is an example of a confirmation screen when confirming assigned tasks.

[0092] 9, the confirmation screen 1200 in this embodiment has an assigned task tab 1201, a requested task tab 1202, an incomplete tab 1203, a completed tab 1204, a search button 1205, and a task display area 1206. The task display area 1206 has one or more task display columns 1206-n (=1, 2, . . .). When checking assigned tasks, the assigned task tab 1201 can be displayed.

[0093] When a user opens the incomplete tab 1203, information about tasks that have not been completed among the tasks for which the user is registered as the person in charge is displayed in the task display area 1206. When a user opens the completed tab 1204, information about tasks that have been completed among the tasks for which the user is registered as the person in charge is displayed in the task display area 1206. In this embodiment, the confirmation screen 1200 is initially displayed with the incomplete tab 1203 open.

[0094] When the user presses the search button 1205, a search area for inputting search criteria is displayed in the confirmation screen 1200 (for example, at the bottom of the screen). Search criteria that can be input in the search area include, for example, the subject, deadline (within this week, within this month, expired, etc.), person in charge, tag information, completion status (completed or incomplete), read status (read or unread), importance, etc.

[0095] When the user enters search criteria, task information that matches the search criteria is displayed in the task display area 1206. Among the search criteria, the subject, tag information, and person in charge are searched for partial matches. For example, if a person in charge is specified as a search condition, task information that includes the specified user as a person in charge among task information that is set up for multiple people is displayed in the task display area 1206.

[0096] The task display area 1206 displays one or more task display columns 1206-n (=1, 2, . . . ) that display the contents of each task. The task display column 1206-n displays the subject, deadline, importance, tag information, requester, etc. of the task. The task display column 1206-n also has a completion button 1210.

[0097] In the task display column 1206-n, for a task that is displayed for the first time since being newly registered, an indicator 1207 indicating that the task is unread is added. In addition, for a task whose deadline has passed, an indicator 1208 indicating that the deadline has passed is added to the task display column 1206-n. In addition, for a task that has been registered as important, an indicator 1209 indicating that the task is important is added to the task display column 1206-n.

[0098] The status of a task may be updated by a user's operation on the task display column 1206-n. For example, when the user presses the completion button 1210, the task management unit 103 updates the completion status of the task to completed. Also, for example, when the user performs a predetermined operation on the task display column 1206-n (for example, an operation of swiping off the screen), a delete button may be displayed, and when the user presses the delete button, the task management unit 103 may delete the task.

[0099] When the user performs an operation to select a task display column 1206-n (for example, by tapping, double-clicking, etc.), the display control unit 204 displays a details confirmation screen that displays the contents of the task corresponding to that task display column 1206-n.

[0100] Fig. 10 is a diagram showing an example of a confirmation screen in this embodiment. The confirmation screen shown in Fig. 10 is an example of a confirmation screen when confirming a requested task.

[0101] As shown in FIG. 10, when checking requested tasks, the requested tasks tab 1202 can be displayed.

[0102] The task display column 1206-n when checking a requested task differs from the task display column 1206-n when checking a responsible task in that it does not have an indicator 1207 indicating that the task is unread, does not have a complete button 1210, and cannot display a delete button. When checking a requested task, the task display column 1206-n has an indicator 1211 added to it indicating that the task is unread for tasks that have not been checked by the user set as the responsible user.

[0103] <Details confirmation screen> The details confirmation screen in this embodiment will be described with reference to Fig. 11. Fig. 11 is a diagram showing an example of the details confirmation screen in this embodiment.

[0104] As shown in FIG. 11, the detail confirmation screen 1400 in this embodiment has a subject display field 1401, a completion status input field 1402, an importance display field 1403, a start date display field 1404, a deadline display field 1405, a person in charge display field 1406, a tag information display field 1407, a detailed content display field 1408, a history display field 1409, an edit button 1410, a work date setting button 1411, and a start dialogue button 1412.

[0105] The subject of the task information is displayed in a subject display field 1401. The completion state of the task information is displayed in a completion state input field 1402. The completion state input field 1402 is displayed so that the completion state can be input. In this embodiment, the completion state input field 1402 is a toggle button that can select whether the task is complete or not.

[0106] The importance display field 1403 displays the importance of the task information. The start date display field 1404 displays the start date of the task information. The deadline display field 1405 displays the deadline date of the task information. The person in charge display field 1406 displays the person in charge of the task information. The tag information display field 1407 displays tag information for the task information. The detailed content display field 1408 displays detailed content of the task information.

[0107] A plurality of messages including the requester message are displayed in the history display field 1409. The history display field 1409 displays the requester message in a distinguishable manner. For example, the history display field 1409 displays the requester message in a background color different from that of other messages.

[0108] When the user selects any of the messages displayed in the history display field 1409, the display control unit 204 displays the dialogue history including the selected message on the dialogue screen 1000. On the dialogue screen 1000, it is possible to refer to messages that follow the selected message. Also, on the dialogue screen 1000, it is possible to resume the dialogue with the dialogue partner.

[0109] When the user presses the edit button 1410, the registration request unit 203 accepts the task editing operation. As a result, on the details confirmation screen 1400, the subject display field 1401, importance display field 1403, start date display field 1404, deadline display field 1405, person in charge display field 1406, tag information display field 1407, and detailed content display field 1408 become editable.

[0110] When the user presses the work date setting button 1411, the display control unit 204 displays a calendar screen. When the user performs an operation to select a date on the calendar screen, the registration request unit 203 sets a work date for the task. The work date is the date on which the person in charge is scheduled to actually perform the task.

[0111] When the user presses the dialogue start button 1412, the display control unit 204 displays a message sending screen. When the user performs an operation to send a message on the message sending screen, a message related to the task can be sent to another user.

[0112] Returning to FIG. 6, the following description will be given. In step S16, the registration request unit 203 included in the user terminal 20-1 accepts a task editing operation on the details confirmation screen by the first user. Next, the registration request unit 203 generates edited task information in accordance with the task editing operation. The edited task information is generated based on the information edited on the details confirmation screen 1400. Next, the registration request unit 203 transmits a task editing request to the communication management server 10. The edit request includes the edited task information.

[0113] In step S17, the task management unit 103 included in the communication management server 10 receives a task editing request from the user terminal 20-1. Next, the task management unit 103 updates the task information stored in the task information storage unit 113 with the edited task information included in the editing request.

[0114] Specifically, based on the task ID included in the edited task information, the task management unit 103 identifies task information stored in the task information storage unit 113. Next, the task management unit 103 overwrites each piece of information included in the identified task information with each piece of information included in the edited task information.

[0115] <Message sending screen> 12 is a diagram showing an example of a message sending screen in this embodiment. As shown in Fig. 12, a message sending screen 1500 in this embodiment has a stamp selection area 1501, a message input field 1502, and a send button 1503.

[0116] Stamp images available to the user are displayed in the stamp selection area 1501. The stamp images may be registered in advance by an administrator of the information processing system 1 or the user may select an image that has been acquired and registered.

[0117] A message is entered in a message input field 1502. When a stamp image is selected in the stamp selection area 1501, or when a message is entered in the message input field 1502, a send button 1503 becomes pressable. Either the selection of a stamp image or the entry of a message may be performed, or both may be performed.

[0118] When the user presses the send button 1503, the dialogue request unit 201 accepts an operation to start a dialogue. The start operation includes the stamp image selected in the stamp selection area 1501 and the message input in the message input field 1502.

[0119] In step S18, the dialogue request unit 201 included in the user terminal 20-1 accepts a dialogue start operation on the message sending screen by the first user. Next, in response to the dialogue start operation, the dialogue request unit 201 transmits a dialogue start request to the communication management server 10. The start request includes a user ID or group ID that identifies the dialogue partner.

[0120] In the dialogue start operation on the message sending screen, a dialogue partner is designated based on the task information displayed on the detail confirmation screen. For example, if the first user is registered as a person in charge in the task information, the dialogue partner may be designated as a user registered as a requester in the task information. Also, for example, if the first user is registered as a requester in the task information, the dialogue partner may be designated as a user registered as a person in charge in the task information. Furthermore, the dialogue partner may be designated as a group that conducted the dialogue in which the requesting message was sent and received.

[0121] In step S19, the dialogue management unit 101 included in the communication management server 10 receives a dialogue start request from the user terminal 20-1. Next, the dialogue management unit 101 transmits a dialogue start notification to the user terminal 20-2 used by the dialogue partner based on the identification information included in the start request.

[0122] In step S20, the display control unit 204 included in the user terminal 20-2 receives a notification of the start of the dialogue from the communication management server 10. Next, the display control unit 204 displays the dialogue screen on the display unit based on the screen data for displaying the dialogue screen.

[0123] In step S21, a dialogue begins between the user terminal 20-1 and the user terminal 20-2. When the dialogue begins, the dialogue request unit 201 included in the user terminal 20-1 transmits the stamp image and message input on the message transmission screen to the communication management server 10.

[0124] In the communication management server 10, the dialogue management unit 101 receives the stamp image and the message from the user terminal 20-1, and then transmits the stamp image and the message to the user terminal 20-2.

[0125] <Dialogue screen> Fig. 13 is a diagram showing an example of a dialogue screen in this embodiment. The dialogue screen shown in Fig. 13 is an example of a dialogue screen after the stamp image and message input on the message sending screen shown in Fig. 12 have been sent and received.

[0126] As shown in FIG. 13, a dialogue screen 1000 in this embodiment has a dialogue partner display field 1001, a message display area 1002, a message input field 1003, a task management button 1004, and the like.

[0127] In the interactive screen 1000 shown in FIG. 13, a message display area 1002-4 based on the stamp image and message input on the message transmission screen 1500 shown in FIG.

[0128] <Effects of the embodiment> The communication management server in this embodiment transmits screen data for displaying a registration screen to a user terminal in response to operations on the interactive screen. The interactive screen in this embodiment allows multiple users to have a dialogue in which they send and receive messages to each other. The registration screen in this embodiment is configured to initially display at least the final message in the dialogue and to allow input of a task and a person in charge. The communication management server in this embodiment associates the task with the person in charge and stores them in a memory unit in response to operations on the registration screen. Therefore, the communication management server in this embodiment makes it possible to easily create tasks and to associate and manage tasks with people in charge.

[0129] The registration screen in this embodiment may be configured to allow input of the requester in addition to the person in charge. Therefore, the communication management server in this embodiment can manage tasks in association with the person in charge and the requester.

[0130] The dialogue screen in this embodiment may be used for sending and receiving messages between groups including multiple users. The registration screen in this embodiment may allow users in the group to be selected as the person in charge or the requester. Therefore, the communication management server in this embodiment can manage tasks requested by users participating in the dialogue.

[0131] The dialogue screen in this embodiment may be used for sending and receiving messages between groups including multiple users. The registration screen in this embodiment may allow a user who is not included in the group to be selected as the person in charge or the requester. Therefore, the communication management server in this embodiment can manage tasks requested by users who are not participating in the dialogue.

[0132] The communication management server in this embodiment transmits screen data for displaying a confirmation screen for displaying information about tasks to the user terminal. The confirmation screen in this embodiment displays information about tasks for which the user is associated as a requester or information about tasks for which the user is associated as a person in charge. Therefore, the communication management server in this embodiment allows the user to separately check tasks that they have requested and tasks that have been requested to them.

[0133] The communication management server in this embodiment stores a message specified in a task creation operation in association with the task, and transmits screen data to the user terminal for displaying dialogue history information including the message on the dialogue screen in response to an operation on the confirmation screen. Therefore, the communication management server in this embodiment allows the user to easily check how the task was requested and to easily resume dialogue with other users related to the task.

[0134] [supplement] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and conventional circuit modules designed to perform each of the above-described functions.

[0135] The devices described in the example are merely one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, the communication management server 10 includes multiple computing devices, such as a server cluster, configured to communicate with each other over any type of communication link, including a network, shared memory, etc., and to perform the processes disclosed herein.

[0136] Although the embodiments of the present invention have been described in detail above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention described in the claims. [Explanation of symbols]

[0137] 1. Information Processing Systems 10. Communication Management Server 101 Dialogue Management Department 102 Screen transmission unit 103 Task Management Department 111 Dialogue history memory unit 112 Screen data storage unit 113 Task information storage unit 20 User terminal 201 Dialogue request section 202 Screen request section 203 Registration Request Section [Prior art documents] [Patent documents]

[0138] [Patent Document 1] Japanese Patent Application Publication No. 2017-97782

Claims

1. An information processing device capable of communicating with a user terminal used by a user via a network, a screen sending unit that, upon receiving an acquisition request sent in response to an operation on an interactive screen for mutually sending and receiving messages between a plurality of users, initially displays at least the final message in the interaction and sends screen data to the user terminal that displays a registration screen on which a task, a person in charge, and a requester can be input; a task management unit that, upon receiving a registration request transmitted in response to an operation on the registration screen, associates the task with the person in charge and the requester and stores the association in a storage unit; Equipped with the screen transmission unit transmits to the user terminal screen data displaying a confirmation screen having a first tab displaying information related to the task for which the user is registered as the person in charge and a second tab displaying information related to the task for which the user is registered as the requester; In response to pressing of a dialogue start button on the confirmation screen, when the information relating to the task for which the user is registered as the person in charge is displayed, a send screen for sending a message to the requester designated as a dialogue partner is displayed, and when the information relating to the task for which the user is registered as the requester is displayed, a send screen for sending a message to the person in charge designated as a dialogue partner is displayed. Information processing device.

2. 2. The information processing device according to claim 1, The registration screen further allows the user to input a deadline. Information processing device.

3. 3. The information processing device according to claim 2, The interactive screen transmits and receives the message in a group including a plurality of users; The registration screen allows the person in charge or the requester to be selected from users included in the group. Information processing device.

4. 3. The information processing device according to claim 2, The interactive screen transmits and receives the message in a group including a plurality of users; the registration screen allows the person in charge or the requester to be selected from users not included in the group; Information processing device.

5. 2. The information processing device according to claim 1, the task management unit associates the message identified by the operation of transmitting the acquisition request with the task and stores the message in the storage unit; Information processing device.

6. 6. The information processing device according to claim 5, the screen transmission unit transmits, to the user terminal, screen data for displaying history information including the message associated with the task on the interactive screen in response to an operation on the confirmation screen. Information processing device.

7. An information processing system in which a user terminal used by a user and an information processing device can communicate with each other via a network, The user terminal a display control unit that displays on the display unit a confirmation screen including an interactive screen for mutually sending and receiving messages between a plurality of users, a registration screen that initially displays at least the final message in the interaction, and allows input of a task, a person in charge, and a requester, a first tab that displays information about the task for which the user is registered as the person in charge, and a second tab that displays information about the task for which the user is registered as the requester; a screen request unit that transmits an acquisition request to the information processing device in response to an operation on the interactive screen; a registration request unit that transmits a registration request to the information processing device in response to an operation on the registration screen; Equipped with The information processing device includes: a screen transmission unit that, upon receiving the acquisition request, transmits screen data for displaying the registration screen to the user terminal; a task management unit that, upon receiving the registration request, associates the task with the person in charge and the requester and stores the association in a storage unit; Equipped with In response to pressing of a dialogue start button on the confirmation screen, when the information relating to the task for which the user is registered as the person in charge is displayed, a send screen for sending a message to the requester designated as a dialogue partner is displayed, and when the information relating to the task for which the user is registered as the requester is displayed, a send screen for sending a message to the person in charge designated as a dialogue partner is displayed. Information processing system.

8. A computer that can communicate with a user terminal used by a user via a network, a step of receiving an acquisition request transmitted in response to an operation on an interactive screen for mutually transmitting and receiving messages between a plurality of users, and transmitting to the user terminal screen data for initially displaying at least the final message in the interaction and displaying a registration screen on which a task, a person in charge, and a requester can be input; a step of storing, in a storage unit, a registration request transmitted in response to an operation on the registration screen, the task, the person in charge, and the requester in association with each other, when the registration request is received; transmitting screen data to the user terminal, the screen data displaying a confirmation screen having a first tab displaying information about the task for which the user is registered as the person in charge, and a second tab displaying information about the task for which the user is registered as the requester; Run In response to pressing of a dialogue start button on the confirmation screen, when the information relating to the task for which the user is registered as the person in charge is displayed, a send screen for sending a message to the requester designated as a dialogue partner is displayed, and when the information relating to the task for which the user is registered as the requester is displayed, a send screen for sending a message to the person in charge designated as a dialogue partner is displayed. Task management methods.

9. A computer that can communicate with the user terminal used by the user via a network, a step of receiving an acquisition request transmitted in response to an operation on an interactive screen for mutually transmitting and receiving messages between a plurality of users, and transmitting to the user terminal screen data for initially displaying at least the final message in the interaction and displaying a registration screen on which a task, a person in charge, and a requester can be input; a step of storing, in a storage unit, a registration request transmitted in response to an operation on the registration screen, the task, the person in charge, and the requester in association with each other, when the registration request is received; transmitting screen data to the user terminal, the screen data displaying a confirmation screen having a first tab displaying information about the task for which the user is registered as the person in charge, and a second tab displaying information about the task for which the user is registered as the requester; Execute In response to pressing of a dialogue start button on the confirmation screen, when the information relating to the task for which the user is registered as the person in charge is displayed, a send screen for sending a message to the requester designated as a dialogue partner is displayed, and when the information relating to the task for which the user is registered as the requester is displayed, a send screen for sending a message to the person in charge designated as a dialogue partner is displayed. program.

Images