JP2024025318A - Information processing apparatus, information processing system, task management method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: 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

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to an information processing device, an information processing system, a task management method, and a program.

2. Description of the Related Art In recent years, information processing apparatuses that allow users to send and receive messages to each other via communication networks have been used for the purpose of information sharing or communication in companies or private settings. Further, information processing apparatuses are used that manage work to be performed by a user as a task.

For example, Patent Document 1 discloses an invention for sharing and managing task states among 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 sends a task based on the extracted content to a second terminal. The state of the task is updated based on information received from one terminal or a second terminal.

However, the conventional technology has a problem in that information necessary for managing tasks may be registered without being clear. For example, tasks requested during dialogue between users may be buried in messages that are added one after another in chronological order, and may not be strictly managed. Delays may occur.

Furthermore, since dialogue is the main activity, if you are not able to quickly and easily create a task when you realize that a message is a task, you may end up forgetting it.

In view of the above-mentioned technical problems, an embodiment of the present invention aims to enable tasks to be easily created and to manage tasks by associating them with persons in charge.

In order to solve the above problems, an information processing device that is an embodiment of the present invention is an information processing device that can communicate with a user terminal used by a user via a network, and is capable of communicating with a user terminal used by a user via a network. When receiving an acquisition request sent in response to an operation on a dialogue screen for sending and receiving messages, at least the last message in the dialogue is initially displayed, and screen data is displayed that displays a registration screen where tasks and persons in charge can be entered. The present invention includes a screen transmission unit that transmits data to a user terminal, and a task management unit that associates a task with a person in charge and stores it in a storage unit upon receiving a registration request transmitted in response to an operation on the registration screen.

According to an embodiment of the present invention, tasks can be easily created, and tasks and persons in charge can be associated and managed.

1 is a diagram illustrating the overall configuration of an information processing system in one embodiment. FIG. 2 is a diagram illustrating the hardware configuration of a computer in one embodiment. FIG. 2 is a diagram illustrating the hardware configuration of a smartphone in one embodiment. FIG. 1 is a diagram illustrating a functional configuration of an information processing system in an embodiment. FIG. 2 is a diagram illustrating a processing procedure of a task management method in an embodiment. FIG. 2 is a diagram illustrating a processing procedure of a task management method in an embodiment. FIG. 3 is a diagram illustrating an interaction screen in one embodiment. FIG. 3 is a diagram illustrating a registration screen in one embodiment. It is a figure which illustrates the confirmation screen in one embodiment. It is a figure which illustrates the confirmation screen in one embodiment. It is a figure which illustrates the detail confirmation screen in one embodiment. FIG. 3 is a diagram illustrating a message transmission screen in one embodiment. FIG. 3 is a diagram illustrating an interaction screen in one embodiment.

Embodiments of the present invention will be described in detail below with reference to the drawings. Note that in the drawings, components having the same functions are designated by the same numbers, and redundant explanation will be omitted.

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

As shown in FIG. 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 each of the plurality of user terminals 20, they will be expressed using branch numbers such as "user terminal 20-1" and "user terminal 20-2."

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

The communication network N1 is constructed, for example, by a wired communication network such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network). The communication network N1 includes not only wired communication but also wireless communication such as wireless LAN or short-range wireless communication, WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), 5G (5th Generation), etc. This may include a mobile communication network.

The communication management server 10 is an information processing device that provides a communication service through which a plurality of user terminals 20 communicate with each other via the communication network N1. The communication service in this embodiment is a service that combines a dialogue management function and a task management function.

The dialogue management function is a function that manages dialogue between multiple users. The dialogue management function in this embodiment allows two users to have a one-on-one dialogue, or a group including three or more users to have a dialogue.

Dialogue in this embodiment is realized by mutually sending and receiving messages between a plurality of users. The message in this embodiment may be composed of text, image, audio, video, a combination thereof, or the like. An example of the interaction in this embodiment is a text chat, a voice call, a video conference, or the like.

The task management function is a function for registering work to be performed by a user as a task and managing its detailed information, progress status, and the like. A task in this embodiment is an independent work that is generated based on a request between users while performing daily work. However, the tasks in this embodiment are not limited to these, and may be, for example, subdivided tasks assigned to each user in a project for achieving one purpose.

The communication service in this embodiment can register tasks that occur during dialogue by linking the dialogue management function and the task management function. Furthermore, the communication service in this embodiment can share and manage detailed information and progress status of registered tasks among users.

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.

The user terminal 20 is an information processing terminal operated by a communication service user. 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.

The user can interact with other users by operating the dialog screen provided by the communication management server 10. Further, the user can activate the registration screen by operating the dialog screen, and register a task by operating the registration screen. Furthermore, the user can use the confirmation screen provided by the communication management server 10 to confirm and edit information regarding registered tasks.

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.

The communication management server 10 and the user terminals 20 include, for example, a PJ (Projector), an IWB (Interactive White Board: a whiteboard with an electronic blackboard function that allows mutual communication), an output device such as a digital signage, and a HUD (Head). up display) equipment, industrial machinery, imaging devices, sound collection devices, medical equipment, network home appliances, connected cars, personal computers, mobile phones, smartphones, tablets, game consoles, personal digital assistants (PDAs) ), a digital camera, a wearable PC, a desktop PC, etc.

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

≪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 implemented by a computer.

As shown in FIG. 2, the computer in this embodiment includes a CPU 501, ROM 502, RAM 503, HD 504, HDD (Hard Disk Drive) controller 505, display 506, external device connection I/F (Interface) 508, and network I/F (Interface) 508. /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.

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

The display 506 displays various information such as a cursor, menu, window, characters, or images. External device connection I/F 508 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a printer, or the like. 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, etc. for electrically connecting each component such as the CPU 501 shown in FIG. 2.

Further, the keyboard 511 is a type of input means that includes a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The DVD-RW drive 514 controls reading and writing of various data on a DVD-RW 513, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may be DVD-R or the like. The media I/F 516 controls reading or writing (storage) of data to a recording medium 515 such as a flash memory.

≪Hardware configuration of smartphone≫
FIG. 3 is a diagram illustrating an example of a hardware configuration when the user terminal 20 is implemented as a smartphone.

As shown in FIG. 3, the smartphone in one embodiment includes a CPU 401, ROM 402, RAM 403, EEPROM 404, CMOS sensor 405, image sensor I/F 406, acceleration/direction sensor 407, media I/F 409, and GPS receiving unit 411. It is equipped with

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

The image sensor I/F 406 is a circuit that controls driving of the CMOS sensor 405. The acceleration/direction sensor 407 is a variety of sensors such as an electronic magnetic compass, a gyro compass, and an acceleration sensor that detect geomagnetism. A media I/F 409 controls reading or writing (storage) of data to a recording medium 408 such as a flash memory. GPS receiving section 411 receives GPS signals from GPS satellites.

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, a sound input/output I/F 417, a display 418, an external device connection I/F (Interface) 419, and a short distance It includes a communication circuit 420, an antenna 420a of the short-range communication circuit 420, and a touch panel 421.

Among 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 images a subject and obtains image data under the control of the CPU 401. The image sensor I/F 414 is a circuit that controls driving of the CMOS sensor 413. Microphone 415 is a built-in circuit that converts sound into electrical signals. The speaker 416 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and voice. The sound input/output I/F 417 is a circuit that processes input/output of sound signals between the microphone 415 and the speaker 416 under the control of the CPU 401 .

The display 418 is a type of display means such as a liquid crystal or organic EL (Electro Luminescence) that displays images of the subject, various icons, and the like. The external device connection I/F 419 is an interface for connecting various external devices. The near field 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 by which the user operates the smartphone by pressing the display 418.

The smartphone also includes a bus line 410. The bus line 410 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 401 shown in FIG. 3.

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

≪Functional configuration of communication management server≫
As shown in FIG. 4, the communication management server 10 in this embodiment includes a dialogue management section 101, a screen transmission section 102, a task management section 103, a dialogue history storage section 111, a screen data storage section 112, and a task information storage section. 113.

When the communication management server 10 is realized by a computer, the dialogue management section 101, the screen transmission section 102, and the task management section 103 are configured such that, for example, the program developed from the HD 504 shown in FIG. This is realized by processing executed by the controller 505 or network I/F 509.

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

The dialogue history storage unit 111 stores history information regarding dialogues managed by the dialogue management unit 101 (hereinafter also referred to as “dialogue history”). The dialogue history in this embodiment includes, for example, identification information that identifies the dialogue (hereinafter also referred to as "dialogue ID"), identification information that identifies the user participating in the dialogue (hereinafter also referred to as "user ID"), or Identification information that identifies the group (hereinafter also referred to as "group ID"), messages sent and received within the conversation, identification information that identifies the message (hereinafter also referred to as "message ID"), date and time when the message was sent. , and the user ID of the user who sent the message.

The screen data storage unit 112 stores in advance screen data to be transmitted to the user terminal 20 by the screen transmission unit 102. Each 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.

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

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"), 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 Includes status (read or unread), etc.

The dialogue management unit 101 manages dialogues between multiple users. For example, when a first user and a second user are having a dialogue, the dialogue management unit 101 transmits a message received from the user terminal 20-1 to the user terminal 20-2, and sends a message to the user terminal 20-2. The message received from -2 is sent to user terminal 20-1. The dialogue management unit 101 also stores a dialogue history regarding messages sent and received during the dialogue in the dialogue history storage unit 111.

The screen transmitter 102 reads out screen data stored in the screen data storage section 112 and transmits it to the user terminal 20 in response to a request from the user terminal 20 . The screen data transmitted by the screen transmitter 102 is, for example, screen data for displaying a dialogue screen, a registration screen, a confirmation screen, and the like.

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 task information from the task information storage unit 113 in response to a request from the user terminal 20 and transmits it to the user terminal 20.

≪Functional configuration of user terminal≫
As shown in FIG. 4, the user terminal 20 in this embodiment includes a dialogue request section 201, a screen request section 202, a registration request section 203, and a display control section 204.

When the user terminal 20 is realized by a smartphone, the dialogue requesting unit 201, the screen requesting unit 202, the registration requesting unit 203, and the display control unit 204, for example, execute a program expanded from the EEPROM 404 to the RAM 403 shown in FIG. is realized by processing executed by the CPU 401 and the long-distance communication circuit 412.

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 conversation partner. The conversation partner may be a single user or a group including multiple users. If the conversation partner is one user, the start request includes the user ID. If the conversation partner is a group, the start request includes the group ID.

The screen requesting unit 202 transmits a screen acquisition request to the communication management server 10 in response to a user's operation. The acquisition request includes information representing the screen to be acquired. The screens requested by the screen requesting unit 202 are, for example, a dialogue screen, a registration screen, a confirmation screen, and the like.

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

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, a dialogue screen, a registration screen, a confirmation screen, and the like.

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

In step S1, the display control section 204 included in the user terminal 20-1 displays the dialog screen on a display section such as the display 418 based on screen data for displaying the dialog screen. The screen data for displaying the dialogue 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.

If the screen data of the dialog screen is stored in the storage unit, the display control unit 204 reads the screen data from the storage unit. Next, the display control unit 204 displays an interaction screen on the display unit based on the read screen data.

When acquiring screen data of a dialog screen from the communication management server 10 , the screen requesting unit 202 transmits a dialog screen acquisition request to the communication management server 10 . In the communication management server 10, the screen transmission section 102 reads screen data of the dialog screen from the screen data storage section 112 and transmits it to the user terminal 20-1. The display control unit 204 displays an interaction screen on the display unit based on the screen data received from the communication management server 10.

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

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 dialogue partner's identification information included in the start request.

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

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 messages received from the user terminal 20-1 to the user terminal 20-2, and transmits messages received from the user terminal 20-2 to the user terminal 20-1. At the same time, the dialogue management unit 101 stores the dialogue history regarding messages sent and received between the user terminals 20-1 and 20-2 in the dialogue history storage unit 111.

≪Dialogue screen≫
The dialog screen in this embodiment will be described with reference to FIG. 7. FIG. 7 is a diagram showing an example of a dialog screen in this embodiment. The dialog screen shown in FIG. 7 is an example of a dialog screen for carrying out a dialog using text chat.

As shown in FIG. 7, the dialogue screen 1000 in this embodiment includes a dialogue partner display field 1001, a message display area 1002, a message input field 1003, a task management button 1004, and the like. The message display area 1002 has one or more message display columns 1002-n (=1, 2, . . . ).

The dialogue partner display field 1001 displays information (name, etc.) representing the dialogue partner. In the message display area 1002, messages sent and received with the conversation partner are displayed in chronological order. The message display area 1002 displays one or more message display fields 1002-n (=1, 2, . . . ) that display the contents of each message. In this embodiment, the message displayed in the message display field 1002-3 is called the "final message" in the dialogue. Note that if a message is added after this, the added message becomes the "last message."

If the message display field 1002-n for all messages sent and received with the dialogue partner cannot be displayed in the message display area 1002, message display fields 1002-n as many as possible are displayed in order from the most recently sent and received messages. It may be displayed in area 1002. At this time, by scrolling the message display field 1002, a message display field 1002-n related to past messages may be displayed.

In the message input field 1003, a message to be sent to the conversation partner is input. The message entered in the message input field 1003 is transmitted via the communication management server 10 to the user terminal 20-2 used by the conversation partner. At the same time, a message display field 1002-n for displaying the contents of the transmitted message is added to the message display area 1002.

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 requesting unit 202 receives an operation to start the registration screen.

The explanation will be returned to FIG. 5. In step S6, the screen requesting unit 202 included in the user terminal 20-1 receives an operation by the first user to start a registration screen for an interaction screen. The activation operation of the registration screen is performed by specifying the request source message. If the request source message is not specified by the user, the message sent and received immediately before is specified as the request source message. Next, the screen requesting unit 202 transmits a registration screen acquisition request to the communication management server 10 in response to the registration screen activation operation. The registration screen acquisition request includes information regarding the conversation ID of the conversation and the requesting message.

In step S7, the screen transmitting unit 102 included in the communication management server 10 receives a registration screen acquisition request from the user terminal 20-1. Next, the screen transmitting unit 102 acquires at least one message including at least the last message in the conversation from the conversation history storage unit 111 based on the conversation ID included in the registration screen acquisition request.

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

In step S9, the screen request unit 202 included in the user terminal 20-1 receives 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.

≪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 a registration screen in this embodiment.

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

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

The importance level of the task is input into the level of importance input field 1102. The degree of importance in this embodiment is a truth value indicating whether something is important or not. The importance input field 1102 in this embodiment includes toggle buttons that allow selection of whether or not something is important. However, the degree of importance in this embodiment is not limited to this, and may be a score representing the degree of importance. In this case, the importance input field 1102 may be configured with a text box, a slider bar, or the like into which a numerical value can be input.

In the start date input field 1103, the start date of the task is input. The start date of a task is the date on which the task occurred (that is, the date on which messages requesting work were sent and received between users). In this embodiment, the current date is initially displayed in the start date input field 1103.

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

In the person in charge input field 1105, the person in charge of the task is input. The person in charge can be selected from the users who are participating in the dialogue (if the dialogue is in a group, all users included in the group), or from the users who are not participating in the dialogue. good. The person in charge may set up multiple users.

In the tag information input field 1106, tag information of a task is input. Tag information is information representing the type of task. The tag information may be selected from predetermined tag information, an arbitrary character string may be input, or tag information input by another user may be selected. A plurality of pieces of tag information may be set.

In the detailed content input field 1107, detailed content of the task is input. The detailed content input field 1107 initially displays at least the final message included in the acquisition request. In this embodiment, the entire final message included in the acquisition request is initially displayed.

In the requester input field 1108, the requester of the task is input. The requester is selected from the users participating in the dialogue (if the dialogue is in a group, all users included in the group). The requester sets one user.

When the user presses the registration button 1109, the registration request unit 203 accepts a 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.

The explanation will be returned to FIG. 5. In step S10, the registration request unit 203 included in the user terminal 20-1 receives a task registration operation on the registration screen by the first user. Next, the registration requesting unit 203 generates task information in response to the task registration operation. Task information is generated based on information input on the registration screen 1100. Subsequently, the registration request unit 203 transmits a task registration request to the communication management server 10. The registration request includes task information.

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 regarding the contents of the task (subject, importance level, tag information, detailed content, etc.), information for managing the task (start date, deadline date, person in charge, requester), and the like. That is, the task information storage unit 113 stores information regarding the contents of a task and information for managing the task in association with each other.

The explanation will proceed to FIG. In step S12, the screen request unit 202 included in the user terminal 20-1 receives an operation to start a confirmation screen by the first user. The activation operation of the confirmation screen is, for example, an operation on the main menu provided by the communication management server 10. Next, the screen requesting unit 202 transmits a confirmation screen acquisition request to the communication management server 10 in response to the confirmation screen activation operation. The acquisition request includes the user ID of the user (here, the first user) who performed the startup operation.

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

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

In step S15, the screen requesting unit 202 included in the user terminal 20-1 receives screen data of the confirmation screen from the communication management server 10. Next, the display control unit 204 displays a confirmation screen on the display unit based on the screen data of the confirmation screen.

≪Confirmation screen≫
The confirmation screen in this embodiment will be explained with reference to FIGS. 9 and 10. FIG. 9 is a diagram showing an example of a confirmation screen in this embodiment. The confirmation screen shown in FIG. 9 is an example of a confirmation screen when confirming the assigned task.

As shown in FIG. 9, the confirmation screen 1200 in this embodiment includes a responsible 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 the assigned tasks, the assigned tasks tab 1201 may be displayed.

When the user opens the uncompleted tab 1203, information regarding uncompleted tasks among the tasks for which the user is registered as the person in charge is displayed in the task display area 1206. When the user opens the completion tab 1204, information regarding completed tasks 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.

When the user presses the search button 1205, a search area for inputting search conditions is displayed within the confirmation screen 1200 (for example, at the bottom of the screen). Search conditions that can be entered in the search area include, for example, subject, deadline date (within this week, within this month, deadline has passed, etc.), person in charge, tag information, completion status (completed or uncompleted), read status (read or unread), importance, etc.

When the user inputs search conditions, task information matching the search conditions is displayed in task display area 1206. Among the search conditions, the subject, tag information, and person in charge are searched based on partial matches. For example, when a person in charge is specified as a search condition, task information that includes the specified user as a person in charge is displayed in the task display area 1206, among task information in which a plurality of persons in charge are set.

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 field 1206-n displays the subject, deadline, importance, tag information, requester, etc. of the task. Further, the task display field 1206-n has a completion button 1210.

In the task display field 1206-n, an indication 1207 indicating that the task is unread is added to the task that is displayed for the first time after being newly registered. Further, in the task display field 1206-n, for tasks whose deadlines have passed, a display 1208 indicating that the deadline has passed is added. Further, in the task display column 1206-n, an indication 1209 indicating that the task is important is added to the task registered as important.

The status of the task may be updated by the user operating the task display field 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 complete. Further, for example, when the user performs a predetermined operation (for example, swiping off the screen) on the task display field 1206-n, a delete button is displayed, and when the user presses the delete button, the task management unit 103 However, the task may be deleted.

When the user performs an operation (for example, tapping, double-clicking, etc.) to select a task display field 1206-n, the display control unit 204 displays a detailed confirmation screen to display the contents of the task corresponding to the task display field 1206-n. Display the screen.

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.

As shown in FIG. 10, when confirming the requested task, the requested task tab 1202 may be displayed.

The task display field 1206-n when checking the requested task does not have the display 1207 indicating unread and the completion button 1210, and does not have the delete button, compared to the task display field 1206-n when checking the task in charge. The difference is that it cannot be displayed. In the task display column 1206-n when confirming a requested task, a display 1211 indicating that the task has not been read is added for a task that has not been confirmed by the user set as the person in charge.

≪Details confirmation screen≫
The details confirmation screen in this embodiment will be explained with reference to FIG. 11. FIG. 11 is a diagram showing an example of a detailed confirmation screen in this embodiment.

As shown in FIG. 11, the details confirmation screen 1400 in this embodiment includes a subject display field 1401, a completion status input field 1402, an importance display field 1403, a start date display field 1404, a deadline date display field 1405, a person in charge It has a user 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 dialogue start button 1412.

A subject display field 1401 displays the subject of task information. The completion status input field 1402 displays the completion status of the task information. The completion status input field 1402 is displayed so that the completion status can be input. The completion status input field 1402 in this embodiment is a toggle button that allows selection of completion or incompleteness.

The importance level display column 1403 displays the importance level of task information. The start date display field 1404 displays the start date of the task information. The deadline date display field 1405 displays the deadline date of the task information. The person in charge display column 1406 displays the person in charge of the task information. Tag information of task information is displayed in the tag information display field 1407. The detailed content display field 1408 displays detailed content of the task information.

A history display column 1409 displays a plurality of messages including a request source message. The history display column 1409 displays the requester's message in a manner that is distinguishable. For example, the history display column 1409 displays the requester's message in a background color different from that of other messages.

When the user selects one 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 dialog screen 1000, it is possible to refer to messages that precede and follow the selected message. Furthermore, on the dialogue screen 1000, it is possible to restart the dialogue with the dialogue partner.

When the user presses the edit button 1410, the registration request unit 203 accepts a 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 date display field 1405, person in charge display field 1406, tag information display field 1407, and detailed contents display field 1408 are displayed. Editable changes.

When the user presses the work day 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 actually executes the task.

When the user presses the dialogue start button 1412, the display control unit 204 displays a message transmission screen. When a 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.

The explanation will be given by returning to FIG. 6. In step S16, the registration request unit 203 included in the user terminal 20-1 receives a task editing operation on the details confirmation screen by the first user. Next, the registration requesting unit 203 generates edited task information in response to the task editing operation. The edited task information is generated based on the information edited on the details confirmation screen 1400. Subsequently, the registration requesting unit 203 transmits a task editing request to the communication management server 10. The editing request includes the edited task information.

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.

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

≪Message sending screen≫
FIG. 12 is a diagram showing an example of a message transmission screen in this embodiment. As shown in FIG. 12, a message sending screen 1500 in this embodiment includes a stamp selection area 1501, a message input field 1502, and a send button 1503.

Stamp images available to the user are displayed in the stamp selection area 1501. The stamp image may be registered in advance by the administrator of the information processing system 1, or an image acquired and registered by the user may be selected.

A message is input into the message input field 1502. When a stamp image is selected in the stamp selection area 1501, or when a message is input in the message input field 1502, the send button 1503 can be pressed. Either one of the stamp image selection and the message input may be performed, or both may be performed.

When the user presses the send button 1503, the dialogue requesting unit 201 accepts an operation to start 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.

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

In the dialog start operation on the message sending screen, a dialog partner is specified based on the task information displayed on the detailed confirmation screen. For example, if the first user is registered as the person in charge in the task information, the user registered as the requester in the task information may be specified as the conversation partner. Further, for example, if the first user is registered as a requester in the task information, the user registered as the person in charge in the task information may be designated as the conversation partner. Further, as the conversation partner, a group with which the request source message was sent and received and the conversation took place may be designated.

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.

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

In step S21, a dialogue begins between user terminal 20-1 and user terminal 20-2. When the dialogue starts, 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.

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

≪Dialogue screen≫
FIG. 13 is a diagram showing an example of the dialog screen in this embodiment. The dialog screen shown in FIG. 13 is an example of the dialog screen after the stamp image and message input on the message transmission screen shown in FIG. 12 have been sent and received.

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

In the dialog screen 1000 shown in FIG. 13, a message display area 1002-4 based on the stamp image and message input on the message sending screen 1500 shown in FIG. 12 is displayed in the message display area 1002.

<Effects of embodiment>
The communication management server in this embodiment transmits screen data for displaying a registration screen to a user terminal in response to an operation on an interaction screen. The dialog screen in this embodiment allows a plurality of users to interact by sending and receiving 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 the task and person in charge. The communication management server in this embodiment associates a task with a person in charge and stores the task and the person in charge in the storage unit according to the operation on the registration screen. Therefore, according to the communication management server of this embodiment, tasks can be easily created and tasks and persons in charge can be associated with each other and managed.

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

The dialog screen in this embodiment may allow a group including a plurality of users to send and receive messages. The registration screen in this embodiment may allow users included in the group to be selected as the person in charge or the requester. Therefore, according to the communication management server in this embodiment, it is possible to manage tasks requested between users participating in a dialogue.

The dialog screen in this embodiment may allow a group including a plurality of users to send and receive messages. The registration screen in this embodiment may allow users who are not included in the group to be selected as the person in charge or the requester. Therefore, according to the communication management server in this embodiment, it is possible to manage tasks requested with users who are not participating in the dialogue.

The communication management server in this embodiment transmits screen data for displaying a confirmation screen for displaying information regarding a task to a user terminal. The confirmation screen in this embodiment displays information regarding a task with which the user is associated as a requester or information regarding a task with which the user is associated as a person in charge. Therefore, according to the communication management server of this embodiment, the user can separately check the tasks requested by the user and the tasks requested by the user.

The communication management server in this embodiment stores the message specified in the task creation operation in association with the task, and displays the history information of the dialogue including the message on the dialogue screen in response to the operation on the confirmation screen. Send screen data to the user terminal. Therefore, according to the communication management server of this embodiment, it is possible to easily confirm the circumstances in which a task was requested, and it is possible to easily resume dialogue with other users related to the task.

[supplement]
Each function of the embodiments described above can be realized by one or more processing circuits. Here, the term "processing circuit" as used herein refers to a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function explained above. This includes equipment such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules.

The devices described in the examples are merely indicative of one of several computing environments for implementing the embodiments disclosed herein. In some embodiments, communications management server 10 includes multiple computing devices, such as a server cluster. The plurality of computing devices are configured to communicate with each other via any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein.

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 or variations can be made within the scope of the gist of the present invention as described in the claims. Changes are possible.

1 Information processing system 10 Communication management server 101 Dialogue management section 102 Screen transmission section 103 Task management section 111 Dialogue history storage section 112 Screen data storage section 113 Task information storage section 20 User terminal 201 Dialogue request section 202 Screen request section 203 Registration request section

JP2017-97782A

Claims (10)

An information processing device capable of communicating with a user terminal used by a user via a network,
When receiving an acquisition request sent in response to an operation on a dialog screen for mutually sending and receiving messages between multiple users, at least the last message in the dialog is initially displayed, and the task and person in charge can be entered. a screen transmitter that transmits screen data for displaying a screen to the user terminal;
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 stores it in a storage unit;
An information processing device comprising: The information processing device according to claim 1,
The registration screen further allows input of at least one of a requester and a deadline.
Information processing device. The information processing device according to claim 2,
The dialog screen allows a group including a plurality of users to send and receive the message;
On the registration screen, the person in charge or the requester can be selected from the users included in the group.
Information processing device. The information processing device according to claim 2,
The dialog screen allows a group including a plurality of users to send and receive the message;
On the registration screen, the person in charge or the requester can be selected from users who are not included in the group.
Information processing device. The information processing device according to any one of claims 2 to 4,
The screen transmission unit sends screen data for displaying a confirmation screen for displaying information regarding the task with which the user is associated as the requester or information regarding the task with which the user is associated as the person in charge. to the user terminal,
Information processing device. The information processing device according to claim 5,
The task management unit stores the message identified by the operation of transmitting the acquisition request in the storage unit in association with the task.
Information processing device. The information processing device according to claim 6,
The screen transmitting unit transmits screen data for displaying history information including the message associated with the task on the dialog screen to the user terminal in response to an operation on the confirmation screen.
Information processing device. An information processing system in which a user terminal used by a user and an information processing device can communicate via a network,
The user terminal is
a display control unit that initially displays an interaction screen for mutually sending and receiving messages between a plurality of users, and at least the final message in the interaction, and displays on the display a registration screen that allows input of tasks and persons in charge;
a screen requesting unit that transmits an acquisition request to the information processing device in response to an operation on the dialog 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 transmitting 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 stores it in a storage unit;
An information processing system equipped with. A computer that can communicate with the user terminal used by the user via the network,
When receiving an acquisition request sent in response to an operation on a dialog screen for mutually sending and receiving messages between multiple users, at least the last message in the dialog is initially displayed, and the task and person in charge can be entered. a step of transmitting screen data for displaying a screen to the user terminal;
a step of, upon receiving a registration request transmitted in response to an operation on the registration screen, associating the task with the person in charge and storing it in a storage unit;
How to manage tasks. A computer that can communicate with the user terminal used by the user via the network,
When receiving an acquisition request sent in response to an operation on a dialog screen for mutually sending and receiving messages between multiple users, at least the last message in the dialog is initially displayed, and the task and person in charge can be entered. a step of transmitting screen data for displaying a screen to the user terminal;
a step of, upon receiving a registration request transmitted in response to an operation on the registration screen, associating the task with the person in charge and storing it in a storage unit;
A program to run.

Images