JP7173179B2 - Information processing system, information processing device, user terminal, and program - Google Patents

Description

The present invention relates to an information processing system, an information processing device, a user terminal , and a program.

Conventionally, the content of important remarks is indicated by converting the voices of meeting attendees into text, referring to multiple rule information for identifying important remarks, and detecting important remarks from the text. is known for extracting and presenting it to conference attendees (see, for example, Patent Document 1).

In recent years, tools (collaboration tools) that support joint work in groups, etc., have been used by providing functions such as communication functions and information sharing functions to multiple users who work in groups or teams. It is With collaboration tools, multiple users who form groups or teams for joint work can use communication functions such as chat functions and voice call functions, as well as information sharing functions, to facilitate online meetings and physical communication between users. You can hold a meeting that will generally meet at the same place.

In meetings that use communication functions and information sharing functions, multiple users who form groups or teams to work together may be required to assign and execute tasks that need to be assigned to users in terms of what they say in text or voice. may contain. However, conventional collaboration tools do not have a mechanism for supporting the registration of action items, which are tasks that need to be assigned to users and executed, which are included in the content of remarks made in meetings.

An object of the present invention is to provide an information processing system capable of supporting registration of action items based on user's utterance data.

In order to achieve the above problems, claim 1 of the present application is an information processing system having a plurality of user terminals and a joint work support system for supporting joint work by a plurality of users operating the user terminals. the user terminal includes: registration means for registering one or more management tools including a scheduler; reception means for receiving action item candidates based on the user's utterance data from the joint work support system; Display control for causing the display unit to display the action item candidates and to display a screen for accepting a registration request for an action item from the action item candidates, a performer who executes the action item, and a deadline for the action item on the display unit. means, a first receiving means for receiving a registration operation of an action item from the action item candidates, an executor who executes the action item, and a deadline of the action item, and the action item and the action which received the registration operation A request for registration of an executor who executes the item and a time limit of the action item is made to action item management means for managing the action item , and the action item and the action item are executed on the utterance data of the user. a request means for making the registration request to an action item management means for managing the action item without the manual registration operation when the action item includes a executor and a time limit of the action item ; a second receiving means for receiving a selection of one management tool from among the one or more management tools registered as a transfer destination of the action item; and the one management tool whose selection has been received by the second receiving means. is a scheduler, display means for displaying the action item at a position on the scheduler corresponding to the time limit of the action item, wherein the joint work support system transmits the action item candidate to the user terminal and transmitting means for transmitting.

According to the embodiment of the present invention, it is possible to support the registration of action items based on the user's utterance data.

1 is a configuration diagram of an example of an information processing system according to an embodiment; FIG. 1 is a hardware configuration diagram of an example of a computer according to the embodiment; FIG. It is a figure which shows the software configuration of a user terminal. 1 is a functional configuration diagram of an example of an information processing system according to an embodiment; FIG. 4 is a conceptual diagram showing a user authentication management table; FIG. 4 is a conceptual diagram showing an access management table; FIG. 4 is a conceptual diagram showing a schedule management table; FIG. 4 is a conceptual diagram showing an execution event management table; FIG. 4 is a conceptual diagram showing a content management table; FIG. 4 is a conceptual diagram showing a user authentication management table; FIG. 4 is a conceptual diagram showing a user management table; FIG. 4 is a conceptual diagram showing a union management table; FIG. FIG. 4 is a conceptual diagram showing a union reservation management table; 4 is a conceptual diagram showing an event management table; FIG. 4 is a conceptual diagram showing a server authentication management table; FIG. 4 is a conceptual diagram showing a project member management table; FIG. FIG. 4 is a conceptual diagram showing an execution event history management table; 4 is a conceptual diagram showing an execution event management table; FIG. 4 is a conceptual diagram showing a related information management table; FIG. FIG. 4 is a conceptual diagram showing an action item management table; FIG. 10 is a sequence diagram showing schedule registration processing; It is the figure which showed the sign-in screen. It is an example of the initial screen of the user terminal. It is the figure which showed the schedule input screen. FIG. 10 is a sequence diagram showing event start processing; FIG. 10 is a sequence diagram showing event start processing; FIG. 13 illustrates a reservation list screen for a union; It is the figure which showed the project list screen. It is the figure which showed the detailed information screen of the event. FIG. 10 is a sequence diagram showing execution event history registration processing; 4 is a flowchart showing speech-to-text conversion processing; It is the flowchart which showed the process which detects an action item candidate. FIG. 10 is a diagram showing part of an execution event history screen; FIG. 10 is a diagram showing part of an execution event history screen; FIG. 10 is a diagram showing part of an execution event history screen; FIG. 10 is a diagram showing part of an execution event history screen; FIG. 10 is a diagram showing part of an execution event history screen; It is the figure which showed a part of task management screen. FIG. 10 is a diagram showing part of an execution event history screen; FIG. 10 is a diagram showing part of an execution event history screen; FIG. 10 is a diagram showing part of an execution event history screen; FIG. 10 is a diagram showing part of an execution event history screen; FIG. 11 is a sequence diagram showing execution event history browsing processing; FIG. 11 is a sequence diagram showing execution event history browsing processing; FIG. 10 is a diagram showing an execution event list screen; 1 is a functional configuration diagram of an example of an information processing system according to an embodiment; FIG. FIG. 10 is a diagram showing part of an execution event history screen; It is the figure which showed a part of screen of a task management tool. It is the figure which showed a part of screen of a task management tool. FIG. 4 is a diagram showing a part of the screen of the scheduler tool; FIG. 10 is a diagram illustrating management tool cooperation of action item candidates; FIG. 10 is a diagram illustrating how to present a user interface by registering action item candidates;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. In this embodiment, a group or team of users gathered for joint work is called a project, and users belonging to the project are called members of the project. Also, in the present embodiment, work that needs to be assigned to a member and executed is called an action item, but it may also be called a task or a follow-up matter. "File" described in this embodiment indicates "electronic file".

[First embodiment]
<System configuration>
FIG. 1 is a configuration diagram of an example of an information processing system according to this embodiment. In the information processing system 1 of FIG. 1, a collaboration system 10, a speech-to-text conversion server 13, an action item management system 20, and a user terminal 40 are connected via a communication network 50 so as to be able to communicate with each other.

The communication network 50 is constructed by the Internet, a mobile communication network, a LAN (Local Area Network), or the like. The communication network 50 may include not only wired communication but also a wireless communication network such as 3G (3rd Generation), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution).

The collaboration system 10 is a system that supports a plurality of people working together on one task. As an example of a collaboration system, it is a place where people gather to discuss opinions and consult for a specific purpose (including cases where the user terminals are physically the same, and where user terminals are physically separated but connected via a network). ), using PCs, mobile terminals, electronic blackboards, projectors, conference tools, etc., voice calls, video calls, chats, screen sharing (projection), information sharing, discussion of agenda, creation and compilation of materials, schedule setting, action It is a system used for deciding items, etc. The collaboration system 10 has the same meaning as a joint work support system. The collaboration system 10 provides a collaboration tool that supports joint work by project members. A collaboration tool is a means, a function, or a tool for assisting a plurality of people to perform one work together. Also, joint work means that a plurality of people perform one work together. Collaboration tools include functions such as communication functions, schedule management functions, information sharing functions, and action item management functions.

Note that the functions of the collaboration tools provided by the collaboration system 10 may not be the same. Therefore, in FIG. 1, the two collaboration systems 10 have different server configurations. The sharing support server 11 of the collaboration system 10 provides project members with, for example, a communication function and an information sharing function.

The schedule management server 12 provides schedule management functions to project members. The speech-to-text conversion server 13 converts speech data by project members into text data. Note that the speech-to-text conversion server 13 may be provided separately from the collaboration system 10 as shown in the information processing system 1 of FIG.

The action item management server 14 provides action item management functions to project members. An action item is a task that needs to be assigned to a user and executed. The action item management server 14 may be provided in the action item management system 20 separate from the collaboration system 10, as shown in the information processing system 1 of FIG. The action item management system 20 provides an action item management function to the user operating the user terminal 40 . The action item management function is a function for accepting registration of action items from users and managing the action items. The action item management function is composed of at least one function or means within the action item management server 14 of FIG. Of course, all functions and means within the action item management server 14 may be included. Action management function is synonymous with action management means.

The user terminal 40 is, for example, an information processing terminal, and is operated by users including project members. A user can use the collaboration system 10 and the action item management system 20 from the user terminal 40 .

Note that the user terminal 40 is not limited to a PC as long as it is a device having a communication function. The user terminal 40 includes, for example, a PJ (Projector), an IWB (Interactive White Board), an output device such as a digital signage, a HUD (Head Up Display) device, Industrial machinery, imaging devices, sound collectors, medical equipment, network appliances, automobiles (connected cars), notebook PCs (personal computers), mobile phones, smartphones, tablet terminals, game consoles, PDAs (Personal Digital Assistants), digital cameras, It may be a wearable PC, a desktop PC, or the like.

Further, the sharing support server 11, the schedule management server 12, the voice-to-text conversion server 13, and the action item management server 14 are realized by, for example, one or more information processing devices. The collaboration system 10 may be one or more computers in which all or part of the functions of the shared support server 11, the schedule management server 12, the speech-to-text conversion server 13, and the action item management server 14 are aggregated. good.

Further, each of the sharing support server 11, the schedule management server 12, the speech-to-text conversion server 13, and the action item management server 14 may be configured to be realized by distributing each function to a plurality of computers.

Furthermore, the shared support server 11, the schedule management server 12, the speech-to-text conversion server 13, and the action item management server 14 may be configured to be realized by a computer in a cloud environment, or may be realized by a computer in an on-premises environment. There may be. Thus, the information processing system 1 of FIG. 1 is an example.

Note that the collaboration system 10, the shared support server 11, the schedule management server 12, the speech-to-text conversion server 13, the action item management server 14, and the action item management system 20 are limited to PCs as long as they have communication functions. do not have.

The collaboration system 10, the shared support server 11, the schedule management server 12, the speech-to-text conversion server 13, the action item management server 14, and the action item management system 20 include, for example, output devices such as PJ, IWB, and digital signage, HUD devices, Industrial machines, imaging devices, sound collectors, medical equipment, network appliances, automobiles, notebook PCs, mobile phones, smartphones, tablet terminals, game machines, PDAs, digital cameras, wearable PCs, desktop PCs, and the like.

The collaboration information provided by the collaboration system 10 to the members of the project using the collaboration tool includes synchronous collaboration information and asynchronous collaboration information. Synchronous collaboration information is information that is exchanged in real time in the middle of a place (for example, a meeting) where people gather to discuss opinions and discuss a specific purpose. Synchronous collaboration information includes, for example, voice calls, video calls, screens shared on PCs, mobile terminals, electronic blackboards, etc. (text and charts input from PCs, mobile terminals, etc., handwritten input content on screens such as electronic blackboards , etc.).

Asynchronous collaboration information is information that is input and shared on the network. Asynchronous collaboration information also includes information that can be shared and referenced by participants before and after a place (for example, a conference) where people gather to discuss opinions and discuss a specific purpose. Information for asynchronous collaboration includes, for example, chats, messages, content, scheduling, action items, recording/recording content, and the like.

Note that these terms are also described in a meeting solutions report (“Magic Quadrant Meeting Solutions”, published in September 2019) provided by Gartner.

<Hardware configuration>
The collaboration system 10, shared support server 11, schedule management server 12, speech-to-text conversion server 13, action item management server 14, action item management system 20, and user terminal 40 shown in FIG. It is implemented by computer 500 . FIG. 2 is a hardware configuration diagram of an example of a computer according to this embodiment.

As shown in FIG. 2, the computer 500 includes a CPU (Central Processing Unit) 501, ROM (Read Only Memory) 502, RAM (Random Access Memory) 503, HD 504, HDD (Hard Disk Drive) controller 505, and display 506. , external device connection I/F (Interface) 508 , network I/F 509 , data bus 510 , keyboard 511 , pointing device 512 , DVD-RW (Digital Versatile Disk Rewritable) drive 514 , and media I/F 516 .

Among these, the CPU 501 controls the operation of the entire computer 500 according to programs. The ROM 502 stores programs used to drive the CPU 501 such as IPL. A 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 reading or writing of various data to/from the HD 504 under the control of the CPU 501 .

A display 506 displays various information such as cursors, menus, windows, characters, and images. The 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. A network I/F 509 is an interface for data communication using the network 16 . A data bus 510 is an address bus, a data bus, or the like for electrically connecting components such as the CPU 501 .

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

Each of the above programs may be recorded in a computer-readable recording medium in an installable or executable format and distributed. Examples of recording media include CD-Rs (Compact Disc Recordable), DVDs (Digital Versatile Disks), Blu-ray discs, SD cards, and the like. Also, the recording medium can be provided domestically or internationally as a program product.

<Software configuration>
Next, software installed in the user terminal 40 will be described with reference to FIG. FIG. 3 is a diagram showing the software configuration of the user terminal. As shown in FIG. 3, an OS 5501, minutes application 5502a, and browser 5502b operate on a work area 5500 of the RAM 503. FIG. The OS 5501 is basic software that provides basic functions of the user terminal 40 and manages the user terminal 40 as a whole.

The minutes application 5502a and browser 5502b are applications for generating and displaying an execution event history screen, which will be described later. On the execution event history screen, for example, minutes of an event such as an online conference executed using various data transmitted from the schedule management server 12 are displayed. Although FIG. 3 shows an example in which two external applications, the minutes application 5502a and the browser 5502b, are installed in the user terminal 40, the present invention is not limited to this. The number of external applications installed in the user terminal 40 may be other than two. Also, the minutes application 5502a and the browser 5502b may be downloaded and installed from a server provided in the collaboration system 10 or the like, or a server provided in the cloud or on-premises, for example.

<Functional configuration>
The information processing system 1 according to this embodiment is realized by a functional configuration as shown in FIG. 4, for example. FIG. 4 is a functional configuration diagram of an example of an information processing system according to this embodiment. In the functional configuration of FIG. 4, configurations unnecessary for the explanation of this embodiment are omitted as appropriate.

<<Functional configuration of shared support server>>
The sharing support server 11 has a transmission/reception section 61 , an authentication section 62 , a creation section 63 , a generation section 64 , a determination section 65 , a detection section 66 and a storage/read processing section 69 . Each of these units is realized or functions by any one of the components shown in FIG. It is a means. The sharing support server 11 also has a storage unit 6000 constructed by the HD 504 and the like shown in FIG.

(User authentication management table)
FIG. 5 is a conceptual diagram showing a user authentication management table. A user authentication management DB 6001 configured by a user authentication management table as shown in FIG. 5 is constructed in the storage unit 6000 . In this user authentication management table, user IDs for identifying users, user names, organization IDs for identifying organizations to which users belong, and passwords are associated and managed. The organization ID also includes a domain name representing a group or organization for managing multiple computers on the communication network 50 .

(Access control table)
FIG. 6 is a conceptual diagram showing an access management table. An access management DB 6002 configured by an access management table as shown in FIG. 6 is constructed in the storage unit 6000 . In this access management table, organization IDs, access IDs and access passwords required for authentication when accessing the schedule management server 12 are associated and managed. The access ID and access password are services provided by the schedule management server 12 via the Web API or the like by the sharing support server 11 using HTTP (Hypertext Transfer Protocol) or HTTPS (Hypertext Transfer Protocol Secure) protocol. It is necessary to use (function).

The schedule management server 12 manages a plurality of schedulers, and different organizations may use different schedulers, so management using the access management table shown in FIG. 6 is necessary.

(schedule management table)
FIG. 7 is a conceptual diagram showing a schedule management table. A schedule management DB 6003 configured by a schedule management table as shown in FIG. 7 is constructed in the storage unit 6000 . In this schedule management table, for each scheduled event ID and execution event ID, the organization ID, user ID of the person who made the reservation, presence or absence of participation of the person who made the reservation, name of the person who made the reservation, scheduled start time, scheduled end time, event name, etc. The user IDs of the participants, presence/absence of participation of other participants, names of other participants, and file data are associated and managed.

Of these, the scheduled event ID is identification information for identifying the reserved event. The scheduled event ID is an example of scheduled event identification information for identifying an event scheduled to be executed. The execution event ID is identification information for identifying an actually executed event or an event being executed among reserved events.

The execution event ID is an example of execution event identification information for identifying an executed event or an event being executed. The reservation name is the name of a person who has reserved a shared space such as a conference room. A community is a thing, service, space (room), place, or information that is shared by multiple people or groups. A conference room is an example of a shared space shared by multiple users. For example, if the union is a conference room, it is the name of the organizer. The scheduled start time indicates the scheduled start time of use of the union. The scheduled end time indicates the scheduled end time of use of the union. The event name indicates the name of the event scheduled to be executed by the subscriber.

The user IDs of other participants are identification information for identifying participants other than the reservation person. Other participant names are the names of participants other than the reservation person. The file data is the file data of the material file used for the event corresponding to the scheduled event ID registered by the user. File data is data in a predetermined file format created using various applications. The file format of the file data is, for example, a file for presentation software, a file for spreadsheet software, or the like.

(execution event management table)
FIG. 8 is a conceptual diagram showing an execution event management table. An execution event management DB 6004 configured by an execution event management table as shown in FIG. 8 is constructed in the storage unit 6000 . In this execution event management table, an execution event ID is associated with each project ID and managed.

A project ID is identification information (an example of project identification information) for identifying a project. A project refers to a group, team, or group of users organized to achieve a particular goal, plan, project, or the like. Members belonging to the same project can share execution event history, such as minutes of events associated with the project ID. A project ID is assigned to each project. A project ID may also be referred to as a group ID or a team ID.

(content management table)
FIG. 9 is a conceptual diagram showing a content management table. A content management DB 6005 configured by a content management table as shown in FIG. 9 is constructed in the storage unit 6000 . In this content management table, the content processing ID, the type of content processing, the details of the content, and the start date and time and end date and time of the content processing are associated with each execution event ID and managed.

Here, the content is the content of an execution event that occurred at an event such as a meeting in a certain project, or materials used at the event. Types of content processing include recording, snapshotting, voice-to-text conversion, generating action items, chatting, and sending materials. Types of content processing may include recording. The content processing ID is identification information for identifying content processing that occurred in each event.

The content includes history information indicating the execution details of the event and action items caused by the executed event. The history information indicating the execution details of the event is data such as recorded data, recorded data, snapshots, statement text data, or materials. Speech text data includes recorded data or voice-text data obtained by voice-to-text conversion from recorded data, and input text data input for chats and messages. The utterance data includes utterance text data and voice data. Voice data is used in a method of extracting action items by voice recognition without being converted into text.

A snapshot is a process of acquiring a display screen as image data at a certain time of an event being executed. Note that snapshots are also referred to as capture or image recognition, for example.

When the type of content processing is "recording", the details of the content include a URL indicating the storage destination of recorded sound data. Further, when the type of content processing is “snapshot”, the contents of the content include a URL indicating the save destination of the image data of the screen acquired by the snapshot (capture). Capturing is to save an image (still image, moving image) displayed on the display 506 as image data. When the type of content processing is "speech-to-text conversion," the content includes a URL indicating a storage destination of text data of received audio data.

An action item is generated at an event such as a meeting in a certain project, and indicates the content of action to be taken by persons involved in the event. When the type of content processing is "occurrence of an action item", the details of the content include the user ID of the action item executor, the deadline for completing the action item, and the storage location of the text data representing the content of the action item. Contains the URL to point to.

(Each functional configuration of the sharing support server)
Next, each functional configuration of the sharing support server 11 will be described in detail. In describing each functional configuration of the sharing support server 11, the main components for realizing each functional configuration of the sharing support server 11 among the components shown in FIG. Also explain the relationship.

The transmitting/receiving unit 61 of the shared support server 11 shown in FIG. 4 is implemented by commands from the CPU 501 shown in FIG. 2 and the network I/F 509 shown in FIG. The transmitting/receiving unit 61 transmits/receives various data (or information) to/from the user terminal 40, another server, another system, or the like via the communication network 50. FIG. The transmitting/receiving unit 61 is an example of transmitting means or receiving means.

The authentication unit 62 is realized by commands from the CPU 501 shown in FIG. Authentication is performed by determining whether the information is

The creating unit 63 is realized by commands from the CPU 501 shown in FIG. Create image data for

The generation unit 64 is implemented by a command from the CPU 501 shown in FIG. 2, and generates an execution event ID, a content process ID, and a storage destination URL. The determination unit 65 is implemented by commands from the CPU 501 shown in FIG. 2, and performs various determinations. This determination will be described later. The detection unit 66 is implemented by a command from the CPU 501 shown in FIG. 2, and detects speech text data of action item candidates, which will be described later, from the user's speech text data.

The storage/read processing unit 69 is implemented by commands from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. It performs processing such as reading out various stored data.

<Functional configuration of the schedule management server>
The schedule management server 12 has a transmission/reception section 81 , an authentication section 82 , a generation section 83 , and a storage/read processing section 89 . These units are realized or function by any of the components shown in FIG. It is a means. The schedule management server 12 also has a storage unit 8000 constructed by the HD 504 shown in FIG.

(User authentication management table)
FIG. 10 is a conceptual diagram showing a user authentication management table. A user authentication management DB 8001 configured by a user authentication management table as shown in FIG. 10 is constructed in the storage unit 8000 . In this user authentication management table, user IDs for identifying users are managed in association with organization IDs for identifying organizations to which the users belong, and passwords.

(User management table)
FIG. 11 is a conceptual diagram showing a user management table. A user management DB 8002 configured by a user management table as shown in FIG. 11 is constructed in the storage unit 8000 . In this user management table, the user ID and the name of the user indicated by the user ID (user name) are associated with each organization ID and managed.

(union management table)
FIG. 12 is a conceptual diagram showing a union management table. A union management DB 8003 configured by a union management table as shown in FIG. 12 is constructed in the storage unit 8000 . In this union management table, a union ID for identifying a union and a union name (union name) are associated with each organization ID and managed.

(Union reservation management table)
FIG. 13 is a conceptual diagram showing a union reservation management table. A union reservation management DB 8004 configured by a union reservation management table as shown in FIG. 13 is constructed in the storage unit 8000 . In this union reservation management table, reservation information in which each piece of information is associated is managed. The reservation information includes, for each organization ID, a union ID, a union name, a user ID of a person who made a reservation, a scheduled start date and time of use, a scheduled end date and time of use, and an event name.

The scheduled start date and time of use indicates the scheduled start date and time of use of the union. The scheduled end date and time of use indicates the scheduled end date and time of use of the union. Each date and time indicates year, month, day, hour, minute, second, and time zone. Each date and time in FIG. 13 represents the year, month, day, hour, and minute due to space limitations.

(event management table)
FIG. 14 is a conceptual diagram showing an event management table. An event management DB 8005 configured by an event management table as shown in FIG. 14 is constructed in the storage unit 8000 . In this event management table, schedule information in which each piece of information is associated is managed. In the schedule information, an organization ID, a user ID, a user name, a scheduled event start date and time, a scheduled event end date and time, and an event name are associated with each scheduled event ID and managed.

Of these, the scheduled start date and time of the event indicates the scheduled start date and time when the event is to be executed. The scheduled end date and time of the event indicates the scheduled end date and time when the event is executed. Each date and time indicates year, month, day, hour, minute, second, and time zone. Each date and time in FIG. 14 represents the year, month, day, hour, and minute due to space limitations. In the event management table of FIG. 14, the file data of the material file used in the event indicated by the schedule information is managed in association with the scheduled event ID.

(Server authentication management table)
FIG. 15 is a conceptual diagram showing a server authentication management table. A server authentication management DB 8006 configured by a server authentication management table as shown in FIG. 15 is constructed in the storage unit 8000 . Access IDs and access passwords are associated and managed in this server authentication management table. The access ID and access password have the same concept as the access ID and access password managed by the access management DB 6002 of the shared support server 11 .

(Project member management table)
FIG. 16 is a conceptual diagram showing a project member management table. A project member management DB 8007 configured by a project member management table as shown in FIG. 16 is constructed in the storage unit 8000 . In this project member management table, a project ID, a project name, and a user ID of each project member are associated with each organization ID and managed.

(execution event history management table)
FIG. 17 is a conceptual diagram showing an execution event history management table. An execution event history management DB 8008 configured by an execution event history management table as shown in FIG. 17 is constructed in the storage unit 8000 . In this execution event history management table, for each project ID and execution event ID, a content processing ID, type of content processing, details of content, and start date and time and end date and time of content processing are associated and managed.

The execution event history management DB 8008 manages partly the same data as the content management DB 6005 . The same data is the execution event ID, the content processing ID, the type of content processing, the start date and time of the content processing, and the end date and time. The contents are stored in the same storage location except for the notation method (http:// or c://) of the storage location of the content data.

(execution event management table)
FIG. 18 is a conceptual diagram showing an execution event management table. An execution event management DB 8009 configured by an execution event management table as shown in FIG. 18 is constructed in the storage unit 8000 . In this execution event management table, an execution event ID is managed in association with an event name, an event start date and time, and an event end date and time. This execution event management DB 8009 manages information on actually executed events among the schedule information managed in the event management DB 8005 .

(Related information management table)
FIG. 19 is a conceptual diagram showing a related information management table. A related information management DB 8010 configured by a related information management table as shown in FIG. 19 is constructed in the storage unit 8000 . In this related information management table, related information in which each piece of information (data) is associated with each project ID and execution event ID is managed. The relevant information is managed in association with the generation time zone of the content, sound data, voice text data, and screen data.

The content occurrence time zone indicates the elapsed time from the start date and time of the event when the content occurred in the executed event. The content occurrence time zone is generated by the generation unit 83 based on the event start date and time stored in the event management DB 8005 and the content processing start date and time and end date and time stored in the execution event history management DB 8008 . The content generation time zone is an example of time information.

The sound data also includes a content processing ID and content type. The voice text data and screen data include content processing ID, content type, and sequence number. Sequence No. indicates the order of occurrence time in which content processing occurred in each of the voice text data and the screen data.

(Each functional configuration of the schedule management server)
Next, each functional configuration of the schedule management server 12 will be described in detail. In describing each functional configuration of the schedule management server 12, the main components for realizing each functional configuration of the schedule management server 12 among the components shown in FIG. Also explain the relationship.

The transmission/reception unit 81 of the schedule management server 12 shown in FIG. 4 is implemented by commands from the CPU 501 shown in FIG. 2 and the network I/F 509 shown in FIG. The transmitting/receiving unit 81 transmits/receives various data (or information) to/from the user terminal 40 , another server, another system, or the like via the communication network 50 .

The authentication unit 82 is realized by commands from the CPU 501 shown in FIG. Authentication is performed by determining whether the information is The authentication unit 82 also performs authentication by determining whether the information (access ID and access password) sent from the shared use support server 11 is information registered in advance in the server authentication management DB 8006 .

The generation unit 83 is implemented by a command from the CPU 501 shown in FIG. 2 and has a function of generating related information registered in the related information management DB 8010 .

The storage/read processing unit 89 is implemented by commands from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. It performs processing such as reading out various stored data.

<<Functional configuration of speech-to-text conversion server>>
The speech-to-text conversion server 13 has a transmission/reception section 91 , a conversion section 93 , and a storage/read processing section 99 . Each of these units is a function or a means of functioning realized by any one of the components shown in FIG. . Moreover, the speech-to-text conversion server 13 of FIG. 4 has a storage unit 9000 constructed by the HD 504 shown in FIG.

(Each functional configuration of the speech-to-text conversion server)
Next, each functional configuration of the speech-to-text conversion server 13 will be described in detail. In the following description of each functional configuration of the speech-to-text conversion server 13, main components for realizing each functional configuration of the speech-to-text conversion server 13 among the components shown in FIG. Also explain the relationship between

The transmission/reception unit 91 of the speech-to-text conversion server 13 shown in FIG. 4 is implemented by commands from the CPU 501 shown in FIG. 2 and the network I/F 909 shown in FIG. The transmitting/receiving unit 91 transmits/receives various data (or information) to/from other servers or other systems via the communication network 50 .

The conversion unit 93 is realized by commands from the CPU 501 shown in FIG. 2, and converts voice data (sound data) received by the transmission/reception unit 91 via the communication network 50 into voice text data.

The storage/read processing unit 99 is realized by commands from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. It performs processing such as reading out various stored data.

<<Functional configuration of the action item management server>>
Action item management server 14 shown in FIG. Each of these units is a function realized by any of the components shown in FIG. It is a means that works. The action item management server 14 also has a storage unit 10000 constructed by the HD 504 or the like shown in FIG.

(User authentication management table)
In the storage unit 10000, a user authentication management DB 10001 configured by user authentication management tables as shown in FIGS. 5 and 10 is constructed. In this user authentication management table, a user ID for identifying a user who can use the action item management function provided by the action item management server 14, a user name, an organization for identifying an organization to which the user belongs, IDs and passwords are associated and managed.

(Action item management table)
FIG. 20 is a conceptual diagram showing an action item management table. An action item management DB 10002 configured by an action item management table as shown in FIG. 20 is constructed in the storage unit 10000 . In this action item management table, action item IDs, states, user IDs of executors of action items, expiration dates of action items, and details of action items are associated and managed. The status indicates whether the action item has been completed or not completed.

(Each functional configuration of the action item management server)
Next, each functional configuration of the action item management server 14 will be described in detail. In the following description of each functional configuration of the action item management server 14, main components for realizing each functional configuration of the action item management server 14 among the components shown in FIG. Also explain the relationship.

The transmission/reception unit 101 of the action item management server 14 shown in FIG. 4 is implemented by commands from the CPU 501 shown in FIG. 2 and the network I/F 509 shown in FIG. The transmitting/receiving unit 101 transmits/receives various data (or information) to/from the user terminal 40 , another server, another system, or the like via the communication network 50 .

The authentication unit 102 is realized by commands from the CPU 501 shown in FIG. Authentication is performed by determining whether the information is

The creation unit 103 is realized by a command from the CPU 501 shown in FIG. 2, and creates image data of a screen for displaying action items registered in, for example, an action item management table. The image data of the screen created by the creating unit 63 causes the user terminal 40 or the like to display action items of the user operating the user terminal 40 or the members of the project to which the user belongs.

The registration unit 104 is implemented by commands from the CPU 501 shown in FIG. 2, receives an action item registration request from, for example, the user terminal 40, and registers the action item in the action item management table shown in FIG. The action unit 105 is implemented by commands from the CPU 501 shown in FIG. For example, the action unit 105 receives an action item completion notification from the user terminal 40 or the like, and updates the status of the action item management table shown in FIG. 20 from "uncompleted" to "completed" according to the completion notification.

Also, when the action unit 105 receives an action item status inquiry request from, for example, the shared support server 11 or the user terminal 40, it reads the action item status corresponding to the inquiry request from the action item management table shown in FIG. to respond. Thereby, the sharing support server 11, the user terminal 40, or the like can confirm whether the action item has been completed or not.

The storage/read processing unit 109 is implemented by commands from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. 10000 is used to read various data stored in the memory.

<<Functional configuration of user terminal>>
The user terminal 40 has a transmission/reception section 51 , a reception section 52 , a display control section 54 , a request section 55 , a generation section 56 , a sound control section 58 , and a storage/read processing section 59 . Each of these units is a function or a means of functioning realized by any one of the components shown in FIG. . The user terminal 40 also has a storage unit 5000 constructed by the HD 504 shown in FIG.

(Each functional configuration of the user terminal)
Next, each component of the user terminal 40 will be described. The transmission/reception unit 51 is implemented by commands from the CPU 501 and the network I/F 509 shown in FIG. . The transmitting/receiving unit 51 is an example of transmitting means or receiving means.

The reception unit 52 is mainly realized by commands from the CPU 501, the keyboard 511, and the pointing device 512 shown in FIG. 5, and receives various inputs from the user. The receiving unit 52 is an example of receiving means. The display control unit 54 is implemented by commands from the CPU 501 shown in FIG. 2, and causes the display 506 to display various screens.

For example, the display control unit 54 accesses the shared support server 11, the schedule management server 12, or the action item management server 14 by starting and executing the minutes application 5502a or browser 5502b that operates on the OS 5501 shown in FIG. . Then, the display control unit 54 downloads WebAPP (WebApplication) including at least HTML (HyperText Markup Language), CSS (Cascading Style Sheets), JAVA SCRIPT (registered trademark), etc., and displays various images generated by the WebAPP. The image data is displayed on display 506 . In addition, the display control unit 54 displays image data generated by “HTML5” including data in XML (Extensible Markup Language), JSON (JavaScript Object Notation), SOAP (Simple Object Access Protocol) format, etc. on the display 506. Let The display control unit 54 is an example of display control means.

The request unit 55 is realized by commands from the CPU 501 shown in FIG. 5, and makes various requests such as a request for registration of an action item to the action item management server 14 and a request for inquiry about the state of the action item.

The generation unit 56 is realized by commands from the CPU 501 shown in FIG. 5 and has a function of generating image data of various screens to be displayed on the display 506 . The generation unit 56 uses the content data received by the transmission/reception unit 51 to generate image data for various screens.

The generation unit 56 renders, for example, text data, which is content data, and generates image data related to the text data, which is content image data, in order to display the rendered data. Rendering is a process of interpreting data described in a Web page description language (HTML, CSS, XML, etc.) and calculating the layout of characters and image data actually displayed on the screen. A sound control unit 58 is realized by a command from the CPU 501 shown in FIG. 5, and has a function of outputting a sound signal from a speaker. The sound control unit 58 sets sound data to be output from the speaker, and reproduces the sound data by outputting a sound signal related to the set sound data from the speaker.

The storage/read processing unit 59 is executed by commands from the CPU 501 shown in FIG. I do.

Each of the above IDs is an example of identification information. Also, the organization ID includes a company name, office name, department name, area name, and the like. The user ID includes an employee number, a driver's license number, my number in Japan's social security/tax number system, and the like.

<Processing or operation of the embodiment>
Hereinafter, processing or operation of each embodiment will be described.

《Schedule registration processing》
Here, a process of registering the schedule of the reservation person A (Taro Riko) from the user terminal 40 to the schedule management server 12 will be described. FIG. 21 is a sequence diagram showing schedule registration processing. FIG. 22 is a diagram showing a sign-in screen. FIG. 23 is an example of the initial screen of the user terminal. FIG. 24 is a diagram showing a schedule input screen.

First, when the user A operates the keyboard 511 of the user terminal 40 or the like, the display control unit 54 of the user terminal 40 displays a signature for signing in on the display 506 as shown in FIG. The in-screen 530 is displayed (step S11).

This sign-in screen 530 includes an entry field 531 for entering the user ID and organization ID of the user, an entry field 532 for entering a password, a sign-in button 538 to be pressed when signing in, and a sign-in button. It includes a cancel button 539 that is pressed to cancel. Here, the user ID and the organization ID are the user A's e-mail address. The user name portion of the e-mail address is the user ID, and the domain name portion indicates the organization ID. Note that the input field 531 may be an input field for separately inputting a user ID and an organization ID instead of an e-mail address.

Next, when User A enters his/her own user ID and organization ID in the input field 531, his/her password in the input field 532, and presses the sign-in button 538, the reception unit 52 prompts the user to sign in. request is accepted (step S12).

Then, the transmission/reception unit 51 of the user terminal 40 transmits sign-in request information indicating a sign-in request to the schedule management server 12 (step S13). The sign-in request information includes the information (user ID, organization ID, and password) accepted in step S12. Thereby, the transmission/reception unit 81 of the schedule management server 12 receives the sign-in request information.

Next, the authentication unit 82 of the schedule management server 12 authenticates the user A using the user ID, organization ID, and password (step S14). Specifically, the storage/read processing unit 89 stores the user ID, organization ID, and organization ID corresponding to the set of the user ID, organization ID, and password received in step S13 in the user authentication management DB 8001 (see FIG. 10). Search for a set of ID and password.

If there is a corresponding pair, the authentication unit 82 determines that the requesting user A is a legitimate user. If there is no corresponding pair, the authentication unit 82 determines that the user A is an unauthorized (unauthorized) user. If not valid, the transmitting/receiving unit 81 notifies the user terminal 40 to that effect. Here, the explanation is continued for the case where it is valid. Next, the transmitter/receiver 81 transmits the authentication result to the user terminal 40 (step S15). Thereby, the transmitting/receiving unit 51 of the user terminal 40 receives the authentication result.

Next, when the authentication result indicating validity is received in step 15, the generation unit 56 of the user terminal 40 generates an initial screen 540 as shown in FIG. 23 (step S16). Then, the display control unit 54 of the user terminal 40 displays an initial screen 540 as shown in FIG. 23 on the display 506 (step S17).

This initial screen 540 includes a "schedule registration" button 541 that is pressed when registering a schedule, and a "execution event history view" button 543 that is pressed when viewing an execution event history.

Here, when the user presses the "schedule registration" button 541, the reception unit 52 receives schedule registration (step S18). Then, the transmission/reception unit 51 transmits the schedule registration request information to the schedule management server 12 (step S19). Thereby, the transmission/reception unit 81 of the schedule management server 12 receives the schedule registration request information.

Next, the storage/read processing unit 89 of the schedule management server 12 searches the user management DB 8002 (see FIG. 11) using the organization ID received in step S13 as a search key, thereby obtaining all corresponding user IDs and All user names are read (step S20). Then, the transmitting/receiving section 81 transmits schedule input screen information to the user terminal 40 (step S21). The transmission/reception unit 51 of the user terminal 40 receives the schedule input screen information.

This schedule input screen information includes all user IDs and all user names read in step S20. All the user names also include the name of the reservation person who is the user A who made the input for sign-in in step S12.

Next, in the user terminal 40, the generator 56 generates the schedule input screen 550 using the schedule input screen information received in step S21. (Step S22). Then, the display control unit 54 of the user terminal 40 causes the display 506 to display a schedule input screen 550 as shown in FIG. 24 (step S23).

This schedule input screen 550 includes an input field 551 for inputting an event name, an input field 552 for inputting a union ID or union name to be used, and an input field 552 for inputting the scheduled start date and time of execution of the event. A field 553, an input field 554 for inputting the scheduled end date and time of the execution of the event, an input field 555 for inputting a memo such as an agenda, a display area 556 for displaying the name of the person who made the reservation, and other information other than the person who made the reservation. A selection menu 557 for selecting a participant name of a participant, an "OK" button 558 that is pressed when registering a reservation, and a "CANCEL" button 559 that is pressed when canceling input contents. It is included. Note that it is not essential to enter a union ID or a union name in the input field 552, and the field is left blank when the union is not used.

The name of the reservation person is the name of the user who entered the sign-in to the user terminal 40 in step S12. The schedule input screen 550 also displays a pointer p1 of the pointing device 512 such as a mouse pointer.

Next, user A enters predetermined items in input fields 551 to 555, and selects the name of the user (user name) that the user wants to participate in the event from selection menu 557 using pointer p1. "OK" button 558 is pressed. Thereby, the receiving unit 52 receives the input of the schedule information (step S24). The transmitter/receiver 51 then transmits the schedule information to the schedule management server 12 (step S25).

This schedule information includes event name, union ID (or union name), scheduled start date and time, scheduled end date and time, user ID of each participant, and a memo. When a union ID is entered in the entry field 552 on the schedule entry screen 550, this union ID is transmitted. Also, when a union name is entered in the input field 552, this union name is transmitted. Also, on the schedule input screen 550, the user name is selected in the selection menu 557, but since the user ID has also been received in step S21, the user ID corresponding to the user name is transmitted. Thereby, the transmission/reception unit 81 of the schedule management server 12 receives the schedule information.

Next, when the schedule management server 12 receives the union ID (or union name) in step S25, it searches the union management DB 8003 (see FIG. 12) using the received union ID as a search key. The union name (or union ID) to be used is read out (step S26).

Next, the storage/read processing unit 89 stores the reservation information for the union name (or union ID) read in step S26 in the union reservation management DB 8004 (see FIG. 13) (step S27). The storage/read processing unit 89 adds one record of reservation information to the union reservation management table of the union reservation management DB 8004 managed by the pre-registered scheduler. The reservation information is constructed based on the schedule information received at step S25 and the union name (or union ID) read at step S26. The scheduled start date and time of use in the union reservation management DB 8004 corresponds to the scheduled start date and time in the schedule information. Also, the scheduled end date and time of use in the union reservation management DB 8004 corresponds to the scheduled end date and time in the schedule information.

Furthermore, the storage/read processing unit 89 stores the schedule information in the event management DB 8005 (see FIG. 14) (step S28). The storage/read processing unit 89 adds one record of schedule information to the event management table of the event management DB 8005 managed by the pre-registered scheduler.

The schedule information is constructed based on the schedule information received in step S25. The scheduled event start date and time in the event management DB 8005 corresponds to the scheduled start date and time in the schedule information. Also, the scheduled end date and time of the event in the event management DB 8005 corresponds to the scheduled end date and time in the schedule information. As described above, the user A can register his/her own schedule in the schedule management server 12 .

<<Event start process>>
Here, a process of holding a conference with other participants using the user terminal 40 in the conference room X reserved by the reservation person A (Taro Riko) will be described. 25 and 26 are sequence diagrams showing event start processing. FIG. 27 is a diagram showing a union reservation list screen. FIG. 28 is a diagram showing a project list screen. FIG. 29 is a diagram showing an event detailed information screen.

First, when the user A presses the power switch of the user terminal 40, the reception unit 52 of the user terminal 40 receives power ON from the user (step S31). The display control unit 54 of the user terminal 40 displays a sign-in screen for signing in on the display 506 (step S32).

Next, User A inputs his/her e-mail address and password on the sign-in screen, and the accepting unit 52 accepts a sign-in request (step S33). The transmitting/receiving unit 51 transmits sign-in request information indicating a sign-in request to the shared support server 11 (step S34). The sign-in request information includes the information (user ID, organization ID, and password) accepted in step S33. Thereby, the transmission/reception unit 61 of the shared support server 11 receives the sign-in request information.

Next, the authentication unit 62 of the shared use support server 11 uses the user ID, organization ID, and password of user A received in step S34 to authenticate user A (step S35). Specifically, using the user ID, organization ID, and password of user A received in step S34 as search keys, the storage/read processing unit 69 performs step A set of user ID, organization ID, and password corresponding to the set of user A's user ID, organization ID, and password received in S34 is retrieved.

If there is a corresponding pair, the authentication unit 62 determines that the requesting user A is a legitimate user. If there is no corresponding pair, the authentication unit 62 determines that the requesting user A is an unauthorized (unauthorized) user. If not valid, the transmitting/receiving unit 61 notifies the user terminal 40 of the invalidity. Here, the explanation is continued for the case where it is valid.

Next, the storage/read processing unit 69 of the sharing support server 11 retrieves the corresponding access ID by searching the access management DB 6002 (see FIG. 6) using the organization ID of user A received in step S34 as a search key. And the access password is read (step S36).

Next, the transmitter/receiver 61 transmits reservation request information indicating a request for reservation information of the union and schedule request information indicating a request for user's schedule information to the schedule management server 12 (step S37). The reservation request information and schedule request information include the user ID, organization ID, and password of user A received in step S34, and the access ID and access password read out in step S36. The transmission/reception unit 81 of the schedule management server 12 receives reservation request information and schedule request information. Next, the authentication unit 82 of the schedule management server 12 authenticates the sharing support server 11 using the access ID and the access password (step S38).

Specifically, the storage/read processing unit 89 searches the server authentication management DB 8006 (see FIG. 15) for a set of access ID and access password corresponding to the set of access ID and access password received in step S37. .

If there is a corresponding pair, the authentication unit 82 determines that the shared use support server 11 that made the request is an authorized accessor. If there is no corresponding pair, the authentication unit 82 determines that the shared use support server 11 that is the source of the request is an unauthorized (unauthorized) accessor. If not, the transmitting/receiving unit 81 notifies the sharing support server 11 of the fact that it is not valid. Here, the explanation is continued for the case where it is valid.

The storage/read processing unit 89 of the schedule management server 12 searches the union reservation management DB 8004 (see FIG. 13) managed by the scheduler using the union ID received in step S37 as a search key. The reservation information to be performed is read out (step S39). In this case, the storage/read processing unit 89 reads out the reservation information whose scheduled use start date and time is today.

Further, the storage/read processing unit 89 searches the event management DB 8005 (see FIG. 14) managed by the scheduler using the user ID of the user A received in step S37 as a search key, thereby responding to the event. Schedule information is read (step S40).

In this case, the storage/read processing unit 89 reads the schedule information in which the scheduled event start date and time is today. When the schedule management server 12 is located in a different country or region from the user terminal 40, the time zone is adjusted to match the country or region where the user terminal 40 is installed based on the time zone information.

Next, the storage/read processing unit 89 searches the project member management DB 8007 (see FIG. 16) using the user ID of the user A received in step S37 as a search key to obtain the user information of the user A. The project IDs and project names of all projects including IDs are read (step S41).

Next, the transmitting/receiving unit 81 sends the reservation information read out in step S39, the schedule information read out in step S40, and all project IDs and all projects read out in step S41 to the shared support server 11. The first name is transmitted (step S42). As a result, the transmission/reception unit 61 of the sharing support server 11 receives the reservation information, schedule information, all project IDs, and all project names.

Next, the creation unit 63 of the shared support server 11 creates a reservation list based on the reservation information and schedule information received in step S42 (step S43). Then, the transmitting/receiving section 61 transmits reservation list information indicating the content of the reservation list, all project IDs, and all project names to the user terminal 40 (step S44). The transmission/reception unit 51 of the user terminal 40 receives the reservation list information, all project IDs, and all project names.

Next, in the user terminal 40, the display control section 54 causes the reservation list screen 230 as shown in FIG. 27 to be displayed on the display 506 (step S45). The reservation list screen 230 includes a display area 231 for displaying union names (here, place names) and a display area 232 for displaying today's date and time. Further, on the reservation list screen 230, event information 235 to 237, etc., indicating events using this common area (here, conference room X) for today are displayed. Each event information includes, for each event, the expected start/end time of use of the community, the event name, and the name of the person who reserved the community (reserver name). The event information includes start buttons 235s to 237s that are pressed when the user specifies an event to start.

Next, in FIG. 26, when the user A presses the start button 235s with the pointing device 512 or the like, the reception unit 52 receives the selection of the event indicated by the event information 235 (step S51). Then, the display control unit 54 displays the project list screen 240 as shown in FIG. 28 on the display 506 based on the project ID and project name received in step S44 (step S52).

Project list screen 240 includes project icons 241 to 246 that indicate each project. The project list screen 240 also includes an "OK" button 248 that is pressed to confirm the selected project icon, and a "CANCEL" button 249 that is pressed to cancel the selection of the project icon.

Next, in FIG. 28, when the user A presses the project icon 241 with the pointing device 512 or the like, the reception unit 52 receives selection of the project indicated by the project icon 241 (step S53).

Next, the transmitting/receiving unit 51 of the user terminal 40 transmits the scheduled event ID indicating the scheduled event selected in step S51 and the project ID indicating the project selected in step S53 to the sharing support server 11. (step S54). The process of step S54 is a process of requesting transmission of execution event identification information. Thereby, the transmission/reception unit 61 of the sharing support server 11 receives the selected scheduled event ID and the selected project ID.

Next, in the sharing support server 11, the generation unit 64 generates a unique execution event ID (step S55). Then, the storage/read processing unit 69 associates and manages the execution event ID generated in step S55, the reservation event ID received in step S54, the user ID and organization ID of the reservation person, and the event information (step S56).

Note that the user ID and organization ID of the reserving person and the event information are IDs and information based on the reservation information and schedule information received in step S42. At this time, there is no entry in the participation presence/absence column in the reservation management table (see FIG. 7).

Next, the storage/read processing unit 69 stores and manages the project ID received in step S54 and the execution event ID generated in step S55 in association with each other (step S57).

Next, in the sharing support server 11, the transmitting/receiving section 61 transmits to the schedule management server 12 file data transmission request information indicating a transmission request for file data registered in the schedule management server 12 (step S58). The file data transmission request information includes the scheduled event ID received in step S54, the user ID and organization ID of user A received in step S34, and the access ID and access password read out in step S36. ing. As a result, the transmission/reception unit 81 of the schedule management server 12 receives the file data transmission request information.

Next, the storage/read processing unit 89 of the schedule management server 12 searches the event management DB 8005 (see FIG. 14) using the scheduled event ID received in step S58 as a search key, and retrieves the file associated with the scheduled event ID. Data is read (step S59). Then, the transmitting/receiving section 81 transmits the file data read out in step S59 to the shared support server 11 (step S60). As a result, the transmission/reception unit 61 of the shared support server 11 receives the file data.

Next, the storage/read processing unit 69 of the sharing support server 11 stores the file data received in step S60 in association with the scheduled event ID received in step S54 and the execution event ID generated in step S55. It is stored and managed in the management DB 6003 (see FIG. 7) (step S61).

The transmission/reception unit 61 transmits the execution event ID generated in step S55 and the file data received in step S60 to the user terminal 40 of user A (step S62). Thereby, the transmission/reception unit 51 of the user terminal 40 of the user A receives the execution event ID and the file data. The transmitting/receiving unit 61 transmits a request for participation in the event to the user terminals 40 of other participants. This event participation request notification includes various information for participation in the event initiated by User A. FIG. As a result, other participants use the event participation request notification to notify the shared support server 11 of their participation in the event from their own user terminals 40, and participate in the online conference or the like started by the user A. You can participate in events.

Next, in the user terminal 40, the storage/read processing unit 59 stores the execution event ID and the file data in the storage unit 5000 (step S63). Here, the file data transmitted from the sharing support server 11 is stored in a specific storage area of the storage unit 5000. FIG. As a result, the user terminal 40 accesses the specific storage area during the execution of the event, thereby causing the display control unit 54 to display the file data stored in the specific storage area on the display 506 .

Here, the specific storage area is a temporary storage destination for data provided for each event being executed, and is a storage area specified by an arbitrary path (character string) indicating the location in the storage unit 5000. be. The specific storage area is not limited to a configuration provided inside the user terminal 40, but a configuration provided in an external storage device connected to the user terminal 40, or a local server that exists in an on-premises environment and can communicate with the user terminal 40. may be

Next, the display control unit 54 causes the detailed information screen 250 of the selected event to be displayed on the display 506 as shown in FIG. 29 (step S64). The event detailed information screen 250 includes an event name display area 251, an event scheduled time (scheduled start time and end time) display area 252, and a reservation person name display area 253. FIG. Further, on the event detailed information screen 250, a display area 256 for displaying the contents of the memo, a display area 257 for displaying the names of prospective participants, and files stored in a specific storage area of the storage unit 5000 are displayed. A display area 258 is displayed for displaying identification information (for example, file name) for identifying data.

Display area 257 displays the name of the reserved person and the names of other selected participants shown by FIG. Display area 258 displays the file data stored in a specific storage area of storage unit 2000 , that is, the file name of the file data downloaded from shared support server 11 . The file name of the file data inside is also displayed. Furthermore, the lower right side of the event detailed information screen 250 includes a “close” button 259 that is pressed to close the detailed information screen 250 .

Next, other participants who have received the participation request notification send a notification of participation in the event from their own user terminal 40 to the shared support server 11, and participate in the event such as the online conference started by user A ( step S66). As a result, the transmission/reception unit 61 of the sharing support server 11 receives the user IDs of other participants who have participated in the event such as the online conference started by the user A. Next, the sharing support server 11 stores and manages the presence or absence of participation in the participation presence/absence field that has not been entered in the schedule management DB 6003 (step S67).

As described above, the user A and other participants can start an event (here, an online conference) using the shared space (here, the conference room X) and the user terminal 40 . The display control unit 54 causes the display 506 to display the event execution screen.

<<Registration and display of execution event history>>
Next, the execution event history registration and display processing will be described. FIG. 30 is a sequence diagram showing execution event history registration processing. Also, FIG. 31 is a flow chart showing the voice-to-text conversion process.

First, in an event that has been started, user A, who is a member of a project for joint work, and other participants hold an online conference using a voice call function, a video call function, a chat function, and the like. User A or another participant of the user terminal 40 uses, for example, a recording/recording function, a chat function, or a message function, and content processing of a type corresponding to each function is executed.

For example, in the case of the recording/recording function, content processing is executed in which recorded data or recorded data is generated as content. In the case of a chat function or a message function, content processing is performed in which input text data is generated as content.

Next, the transmitting/receiving unit 51 transmits registration request information indicating the generated content registration request to the sharing support server 11 (step S72). In this case, the transmitting/receiving section 51 automatically transmits registration request information each time content is generated. A format for transmitting the content may be a file format or a stream format. The registration request information includes an execution event ID, a user ID of a content transmission source, content data, and content processing type information. Thereby, the transmission/reception unit 61 of the shared support server 11 receives the registration request information.

Next, the determination unit 65 of the shared use support server 11 determines the type of received content processing based on the content processing type information included in the registration request information received by the transmission/reception unit 61 (step S73).

Then, when the determination unit 65 determines that the type of content processing is the “recording function”, the transmission/reception unit 61 of the shared use support server 11 transmits sound (recorded) data, which is content data, to the speech-to-text conversion server 13 . Send (step S74). Further, when the determination unit 65 determines that the type of content processing is the "recording function", the transmission/reception unit 61 of the sharing support server 11 transmits recorded data, which is content data, to the speech-to-text conversion server 13 ( step S74).

Thereby, the transmission/reception unit 91 of the speech-to-text conversion server 13 receives the sound data or the recorded data. If the type of content processing is other than "recording function/recording function", the sharing support server 11 proceeds to the process of step S77 without performing the processes of steps S74 to S76.

Next, the conversion unit 93 of the speech-to-text conversion server 13 converts the sound data or recorded data received by the transmission/reception unit 91 into text data (step S75). The processing in step S75 may be real-time processing or batch processing. Here, the speech-to-text conversion processing in the speech-to-text conversion server 13 will be described with reference to FIG.

First, the conversion unit 93 acquires information indicating the date and time when the sound data or the recorded data was received by the transmission/reception unit 91 (step S75-1). The information acquired in step S75-1 may be information indicating the date and time when the sharing support server 11 received the sound data or the recorded data or the date and time when the sharing support server 11 transmitted the sound data or the recorded data. . In this case, the transmitting/receiving unit 91 of the speech-to-text conversion server 13 receives the sound data or the recorded data transmitted from the shared support server 11 and the information indicating the date and time in step S74.

Next, the conversion unit 93 executes text conversion processing of the sound data or recorded data received by the transmission/reception unit 91 (step S75-2). Then, when the text conversion processing of the sound data or the recorded data is completed (YES in step S75-3), the conversion unit 93 shifts the processing to step S75-4. On the other hand, the conversion unit 93 repeats the process of step S75-2 until the text conversion process of the sound data or recorded data is completed.

When it is determined that the text conversion process is completed, the conversion section 93 generates voice text data converted from the sound data or recorded data (step S75-4). As a result, the speech-to-text conversion server 13 can convert the sound data or the recorded data transmitted from the shared support server 11 into speech-to-text data.

The information processing system 1 repeats the processing described above (steps S71 to S76), thereby repeatedly executing the text conversion processing of the recorded data or the recorded data generated in the user terminal 40. FIG.

When the converting unit 93 completes text conversion of the sound data or the recorded data, the transmitting/receiving unit 91 of the voice-to-text conversion server 13 transmits the voice-to-text data to the shared support server 11 (step S76). As a result, the transmission/reception unit 61 of the shared support server 11 receives the voice-text data transmitted from the voice-to-text conversion server 13 .

Next, the generation unit 64 generates a unique content processing ID for identifying the content processing caused by the event (step S77). In addition, the generation unit 64 generates a URL of content data indicating the details of the content (step S78). The storage/read processing unit 69 stores the content management DB 6005 (see FIG. 9) for each execution event ID received in step S72, the type of content processing, the start date and time and the end date and time of the content processing, and the event generated in step S77. The generated content processing ID and the details of the content are associated and managed (step S79).

Next, the detection unit 66 detects the speech text data of the action item candidate from the speech text data including the voice text data received in step S76 and the input text data received in step S72, for example, as follows. FIG. 32 is a flowchart showing processing for detecting action item candidates.

First, the detection unit 66 divides the speech text data received in step S76 and the utterance text data including the input text data received in step S72 into sentences (step S80-1).

Next, the detection unit 66 reads the statement text data of one sentence from the statement text data divided into sentences (step S80-2). The detection unit 66 performs a morphological analysis on the read one-sentence utterance text data, and decomposes it by taking into consideration the extraction of three elements, for example, "who", "what", and "by when" (step S80-3). . In this embodiment, an example of morphological analysis of Japanese has been described, but it can also be applied to languages other than Japanese, such as Chinese and Arabic, where one sentence continues and needs to be divided into sentences. be.

For example, for the element [who], a noun representing [person's name] should be extracted. Also, for example, the element [by when] is considered in the composition of A part + B part,
Part A: Phrases that express dates and times and positions on the calendar, such as [date], [day of the week], [number + x days later], [words that express dates and times (tomorrow, the day after tomorrow, etc.)] Part B: [by (wa)], Phrases that express deadlines such as [by delivery date],
should be extracted. Also, the element [what] is considered in the composition of A part + B part,
Part A: [noun] + (particle, adverb)
Part B: [Verb] + [Please do], [Please], [Please finish], etc., can be extracted. Here, it is also allowed that the order of the A part and the B part is reversed (inverted).

Next, based on the result of the morphological analysis, the detection unit 66 determines whether there is a predetermined combination of elements that are likely to be an action item in the speech text data of one sentence (step S80-4).

For example, an action item is generally composed of three elements: "who", "what", and "by when". They may not match. Therefore, the detecting unit 66 detects as an action item candidate when, for example, one sentence of utterance text data includes the following combination of elements.

(Example of combination elements)
Element [Who] + [What] ... <Example: Mr. Tanaka, make a phone call to Company Z. ＞
Elements [By when] + [What] ... <Example: Make sure to call Company Z by Friday. ＞
Elements [who] + [by when] + [what] <Example: Mr. Tanaka, please call Z company by Friday to confirm. ＞
It should be noted that the example of the combination of elements described above is an example in which the element [what] is required to be established as an action item. If the one-sentence statement text data includes the above combination of elements (YES in step S80-4), the detection unit 66 detects the one-sentence statement text data read out in step S80-2 as an action item candidate ( step S80-5).

If there is no element of the above combination in the utterance text data of one sentence (NO in step S80-4), the detection unit 66 skips the processing of step S80-5, and the sentence of the utterance read out in step S80-2 Do not detect text data as action item candidates. The detection unit 66 repeats steps S80-2 to S80-6 until reading of all the utterance text data divided into sentences in step S80-1 is completed.

According to the processing for detecting action item candidates shown in FIG. 32, the detection unit 66 can detect statement text data of action item candidates from statement text data. It should be noted that the “predetermined combination of elements likely to be action items” used for detecting action item candidates shown in steps S80-4 and S80-5 of FIG. 32 may be updated by machine learning.

For example, an action item candidate detected based on the above-mentioned "predetermined combination of elements likely to be an action item" as a basic rule may not be registered as an action item by a project member or the like. In addition, there are cases where a sentence in the statement text data that cannot be detected based on the basic rule of "predetermined combination of elements likely to be an action item" is registered as an action item by a member of the project.

In such a case, by applying machine learning to an action item candidate that has not been registered as an action item by a project member and a sentence of remark text data that has been registered as an action item by a project member, Detection accuracy of action item candidates can be improved.

Here, machine learning is a technology that enables a computer to acquire human-like learning ability, in which the computer autonomously generates algorithms necessary for making judgments such as data identification from learning data taken in advance. , is a technology that applies this to new data and makes predictions.

The learning method for machine learning may be supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or deep learning, or may be a learning method combining these learning methods. Any learning method for the sake of learning does not matter.

Next, returning to FIG. 30, the transmission/reception unit 61 of the sharing support server 11 transmits data corresponding to the content processing that occurred in step S71 to the user terminals 40 of the project members (step S81). For example, when sound recording data or video recording data is generated as content in step S71, the transmitter/receiver 61 transmits speech text data detected as an action item candidate in addition to the sound recording data or video recording data.

Further, when input text data input for chat or message is generated as content in step S71, the transmitting/receiving section 61 transmits remark text data detected as an action item candidate in addition to the input text data.

As a result, the user terminals 40 of the project members can transmit the text data of action item candidates detected from the contents of the project members' utterances and text input at events such as online meetings to the shared support server. 11 can be received.

The display control unit 54 of the user terminal 40 of the project member receives the content of the project member's speech or text input in an event such as an online conference transmitted from the shared support server 11, and the action detected from the content. The utterance text data of the item candidate is displayed on the execution event history screen 260 on the display 506 as shown in FIG. 33, for example.

FIG. 33 is a diagram showing part of the execution event history screen. On the execution event history screen 260 of FIG. 33, there is a "memo in full screen display" that displays the content (memo) of the project member in text or voice at an event such as an online conference using the communication function in full screen display. button 262 and statement text data 264 detected as action item candidates from the content of the meeting memo. Also, there may be a plurality of action item candidates. As an example, below "Mr. Yamashita will correct and submit document 1 by tomorrow" described in the remark text data 264, another action item candidate "Mr. Suzuki will create document 2 within this month" is displayed. ” may be displayed.

A meeting memo is, for example, an utterance record obtained by converting voice data of the contents of a project member's speech into text data using an existing voice recognition technology. Also, the meeting memo is a transcript of what the members of the project said by text input.

In the execution event history screen 260 of FIG. 33, an example in which the statement text data 264 of the action item candidate received from the shared support server 11 is a sentence "Mr. Yamashita corrects and submits the document 1 by tomorrow" is shown. Although shown, there may be more than one.

For example, a project member (hereinafter referred to as a registered member) who wants to register the action item candidate statement text data 264 in the execution event history screen 260 of FIG. Operate the terminal 40 .

First, the registered member, for example, puts the pointer of the pointing device 512 on the position of the utterance text data 264 of the action item candidate, thereby clicking the action button groups 266 and 268 as shown in FIGS. Displayed on the execution event history screen 260 . 34 and 35 are diagrams showing part of the execution event history screen.

In the example of FIGS. 34 and 35, the action button group 268 of FIG. 35 is displayed by mousing over the three-point button "..." of the action button group 266 of FIG. Note that the action button groups 266 and 268 in FIGS. 34 and 35 are examples, and one or three or more action button groups may be provided.

The registered member selects the "set executor" button 270 in the action button group 268 of FIG. 35 to display the executor input field 272 on the execution event history screen 260 as shown in FIG. FIG. 36 is a diagram showing part of the execution event history screen. In the performer input field 272, candidates for the performer of the action item are displayed so as to be selectable.

It should be noted that project members (participating members and non-attending members) summoned to the online conference are preferentially displayed as action item executor candidates. Candidates for action item executors may be narrowed down and displayed according to not only members of the project but also viewing authority divisions (teams, channels, etc.) on this collaboration system. For example, as a candidate for the action item executor, the reservation person such as the meeting organizer (an example of the organizer of the group), the member with the highest authority among the members of the project (an example of the high authority user who participated in the group) Narrowing down is possible by referring to various tables. The executor of the action item is not limited to one person, and may be assigned to multiple persons.

The registered member can set the executor of the action item from the executor input field 272 in FIG. When the executor of the action item is set by the registered member, a time limit input field 274 is displayed on the execution event history screen 260 as shown in FIG. FIG. 37 is a diagram showing part of the execution event history screen. A calendar for entering a deadline is displayed in the deadline input field 274 so that the deadline can be entered. The registered member can enter the expiration date of the action item from the expiration entry field 274 in FIG.

The utterance text data of the action item candidate for which the executor has been set and the deadline date has been input as described above is used as the action item of the set executor from the user terminal 40 of the registered member to the action item of the same collaboration system 10. It is registered in the action item management function of the management server 14 . Note that the action item registration request to the action item management server 14 can be made using, for example, an API (Application Programming Interface) that the action item management server 14 publishes.

In the above, an example in which a registered member sets an executor and inputs a deadline date has been described, but an action item candidate example shown in FIG. When the three elements of "who", "what", and "by when" are complete, the action item management server 14 automatically manages the action item without manual operation as described above. You can register for the function.

For example, the requesting unit 55 of the user terminal 40 may determine "who" from the statement regarding "to whom" included in the statement text data 264 of the action item candidate. In addition, the requesting unit 55 determines "who" when the statement text data 264 of the action item candidate includes one "person's name" and is able to identify the only user on the information processing system 1. Only in the following cases, "to whom" may be determined automatically. The following cases consider judgment priority. In the following cases, if the executor of the action item could not be set automatically, the registered member should set it manually.

Priority 1: "Who" is <Tanaka>, and there is a user who is a part of the name of "Tanaka" as a participant in the online conference.

Priority 2: “Who” is <Tanaka>, and there is a user who has “Tanaka” as part of his or her first and last name as an absentee in the online conference.

Priority 3: "Who" is <Tanaka>, and there is a user on the information processing system 1 who has "Tanaka" as part of his/her name.

Further, for example, the requesting unit 55 of the user terminal 40 may determine "until" based on the statement regarding "until" included in the statement text data 264 of the action item candidate. In addition, the request unit 55 of the user terminal 40 may determine "until" from the schedule of the next meeting that can be determined from the meeting attribute. For example, for "next time", the cycle interval of the meeting can be acquired from the schedule management server 12 and the date can be specified on the calendar. Similarly, the request unit 55 of the user terminal 40 can specify the date of "tomorrow" or "the day after tomorrow" on the calendar. Phrases that correspond to the "past" from phrases that express time and meetings do not have to be targeted.

Registered members who request the registration of an action item are limited to, for example, the speaker of the action item candidate remark text data 264, a reservation person such as a conference organizer, and a member of the project having a higher level of authority. may

Upon receiving the action item registration request, the registration unit 104 of the action item management server 14 manages the action item using an action item management table as shown in FIG. Also, the action unit 105 of the action item management server 14 manages the state of the action item according to the notification from the user terminal 40 .

Furthermore, when the action unit 105 of the action item management server 14 receives an inquiry request from the user terminal 40, it responds with the contents of the action item corresponding to the inquiry request and the state of the action item.

As a result, the display control unit 54 of the user terminal 40 causes the display 506 to display a task management screen 271 as shown in FIG. 38, for example. FIG. 38 is a diagram showing part of the task management screen. On the task management screen 271 of FIG. 38, an action item 273 of "Mr. Yamashita corrects and submits the document 1 by tomorrow" registered from the execution event history screen 260 is displayed.

As described above, in the information processing system 1 according to the present embodiment, it is possible to easily register an action item in the action item management server 14 from the execution event history screen 260 .

Note that the information processing system 1 of FIG. 1 is configured to have a plurality of action item management servers 14 . Therefore, the user terminal 40 may receive the selection of the action item management server 14 for registering the action item from the registered member. The selection of the action item management server 14 for registering the action item may be received from the execution event history screen 260 shown in FIGS. 39 and 40, for example.

39 and 40 are diagrams showing part of the execution event history screen. The registered member selects the "transfer action item" button 276 in the action button group 268 of FIG. 39 to display an action item transfer destination selection field 278 on the execution event history screen 260 as shown in FIG. The transfer destination of the action item is displayed in the action item transfer destination selection field 278 so as to be selectable.

By selecting the transfer destination of the action item from the action item transfer destination selection column 278 in FIG. Action items can also be registered in other functions and action item management servers 14 other than the same collaboration system 10 . The status of the action item registered in the other action item management server 14 can be obtained by making an inquiry request to the other action item management server 14 .

Further, it would be convenient if the execution event history screen 260 could confirm the completion or incompleteness of the action item registered in the action item management server 14 from the execution event history screen 260 as described above. Therefore, in the information processing system 1 of the present embodiment, as shown in FIG. 41 or FIG. 42 , the incomplete action item is associated with the statement text data 264 of the execution event history screen 260 registered as the action item. or an icon 282 representing that the action item has been completed may be displayed in conjunction with the action item management server 14 . 41 and 42 are diagrams showing part of the execution event history screen.

The action item management server 14 of the collaboration system 10 manages the action item status "completed" or "uncompleted" in an action item management table as shown in FIG. The status of the action item management table in FIG. 20 changes from "uncompleted" to "completed" when, for example, a user who has completed an action item performs an operation for notifying completion of the action item from the user terminal 40 or the like. Updated.

Therefore, as shown in FIG. 41 or 42, an icon 280 indicating that the action item is incomplete or completed is associated with the statement text data 264 of the execution event history screen 260 registered as the action item. icon 282 can be displayed in conjunction with the action item management server 14 .

The state of the action item management table of FIG. 20 is, for example, the action item of another action item management server 14 (for example, the action item management server 14 of the action item management system 20) selected from the execution event history screen 260 of FIG. You may make it interlock|cooperate with a state. When a user who has completed an action item on another action item management server 14 performs an operation from the user terminal 40 or the like to notify completion of the action item, the status of the action item management table in FIG. Updated to "completed".

Therefore, as shown in FIG. 41 or 42, it is associated with the remark text data 264 of the execution event history screen 260 registered in the other action item management server 14 as an action item to indicate that the action item is incomplete. An icon 280 representing an action or an icon 282 representing completion can be displayed in conjunction with the action item management server 14 .

≪Browsing process of execution event history≫
Next, the browsing process of the execution event history will be explained. 43 and 44 are sequence diagrams showing execution event history viewing processing. Note that the processing of steps S111 to S117 in FIG. 43 is the same as the processing of steps S11 to S17 in FIG. 21, so the description thereof will be omitted.

When the user presses the "view execution event history" button 543 on the initial screen 540 shown in FIG. 23, the receiving unit 52 receives viewing of the execution event history (step S118).

Then, the transmission/reception unit 51 transmits execution event history viewing request information indicating an execution event history viewing request to the schedule management server 12 (step S119). Thereby, the transmission/reception unit 81 of the schedule management server 12 receives the execution event history viewing request information. Next, the storage/read processing unit 89 of the schedule management server 12 retrieves the corresponding project ID and project name by searching the project member management DB 8007 using the user ID and organization ID received in step S113 as search keys. Read out (step S120). Then, the transmission/reception unit 81 transmits the project ID and the project name to the user terminal 40 (step S121).

Next, the generation unit 56 of the user terminal 40 generates a project list screen using the project ID and project name received in step S121 (step S122). Then, in the user terminal 40, the display control unit 54 displays the project list screen generated by the generation unit 56 on the display 506 (step S123). This project list screen displays the same contents as the project list screen 240 in FIG.

Next, in FIG. 44, when the user A presses the project icon 241 with, for example, a mouse, the reception unit 52 receives selection of the project indicated by the project icon 241 (step S124).

Next, the transmitter/receiver 51 of the user terminal 40 transmits the project ID of the project selected in step S124 to the schedule management server 12 (step S125). Thereby, the schedule management server 12 receives the project ID.

Next, in the schedule management server 12, the storage/read processing unit 89 reads out the corresponding execution event ID by searching the execution event history management DB 8008 using the project ID received in step S125 as a search key (step S126). ).

In this case, the storage/read processing unit 89 reads all execution event IDs associated with the project ID received in step S125. Then, the storage/read processing unit 89 searches the execution event management DB 8009 using the execution event ID read out in step S126 as a search key, thereby reading the corresponding execution event start/end information (step S127). This execution event start/end information includes an execution event ID, event name, start date and time, and end date and time.

Then, the transmission/reception unit 81 transmits the execution event ID, the event name, the start date and time, and the end date and time read in step S127 to the user terminal 40 (step S128). Thereby, the transmission/reception unit 51 of the user terminal 40 receives the execution event ID, the event name, the start date and time, and the end date and time.

Next, the generation unit 56 of the user terminal 40 uses the data received in step S128 to generate an execution event list screen 570 as shown in FIG. 45 (step S129). FIG. 45 shows an execution event list screen. Then, in the user terminal 40, the display control unit 54 causes the execution event list screen 570 generated by the generation unit 56 to be displayed on the display 506 (step S130). As shown in FIG. 45, execution event list screen 570 includes information 571 to 573 indicating execution events.

For example, the information 571 to 573 indicating the execution event includes the name of the execution event, the start date and time of the event, and the end date and time of the event. Information 571 to 573 indicating execution events is an example of a history information selection area for receiving a selection for displaying history information indicating execution details of an event. In addition, the lower right portion of execution event list screen 570 includes a “close” button 575 that is pressed to close execution event list screen 570 .

Further, the lower left portion of execution event list screen 570 includes an “action item” button 577 that is pressed when viewing action items. The “action item” button 577 is an example of an action item selection area that receives a selection for displaying action items managed by the action item management server 14 of the collaboration system 10 with which the user has signed in. The action item management server 14 of the collaboration system 10 to which the user has signed in manages registered action items using FIGS.

Next, the reception unit 52 of the user terminal 40 receives selection of an execution event included in the execution event list screen 570 (step S131). Specifically, when the user selects information indicating an execution event included in execution event list screen 570, reception unit 52 receives selection of information indicating an execution event. Then, the transmission/reception unit 51 of the user terminal 40 transmits the execution event ID of the execution event selected by the reception unit 52 to the schedule management server 12 (step S132). Thereby, the transmission/reception unit 81 of the schedule management server 12 receives the execution event ID.

Next, the storage/read processing unit 89 of the schedule management server 12 searches the execution event history management DB 8008 using the execution event ID received in step S132 as a search key, and reads the corresponding execution event history information (step S133). . This execution event history information includes a content processing ID, type of content processing, start date and time of content processing, and end date and time.

Also, the storage/read processing unit 89 of the schedule management server 12 reads out the corresponding related information by searching the related information management DB 8010 using the execution event ID received in step S132 as a search key (step S134). This related information includes the content generation time zone, content processing ID, type of content processing, and sequence number. The occurrence time zone of content included in related information is an example of time information.

Then, the storage/read processing unit 89 reads out the content data indicating the details of the execution event history from the storage location of the content data indicating the details of the execution event history read in step S133 (step S135). Then, the transmitting/receiving section 81 transmits the related information and content data read out to the user terminal 40 (step S136). Thereby, the transmitting/receiving section 51 of the user terminal 40 receives the related information and the content data.

Next, the request unit 55 of the user terminal 40 requests the action item management server 14 of the signed-in collaboration system 10 to inquire about the state of the action item (step S137). Upon receiving an action item status inquiry request from the user terminal 40, the action unit 105 of the action item management server 14 reads the action item status corresponding to the inquiry request from the action item management table shown in FIG. 20 (step S138).

Then, the request unit 55 of the user terminal 40 receives the action item status information from the action item management server 14 (step S140). The generation unit 56 of the user terminal 40 uses the related information and the content data received in step S136 to generate the statement text data 264 of the execution event history screen 260, and the state of the action item received in step S140. The information is used to generate icon 280 or 282 of execution event history screen 260 described above. The display control unit 54 of the user terminal 40 can display the execution event history screen 260 such as FIG. 41 or 42 generated by the generation unit 56 on the display 506 (step S142).

According to the information processing system 1 according to the present embodiment, it is possible to support registration in the action item management function from the content of remarks between project members using the communication function provided by the collaboration tool.

[Second embodiment]
The action item transfer destination selection field 278 shown in FIG. 40 may display, for example, a "task management tool" button 284 shown in FIG. 47 so that it can be further selected. The registered member selects the "task management tool" button 284 as the transfer destination of the action item from the action item transfer destination selection field 278 of FIG. An action item can be registered in the task management tool, which is an example of the function.

For example, when the user signs in to the task management tool of the action item management server 14 other than the same collaboration system 10, the action item registered in the task management tool is displayed as task 291 on screen 290 in FIG. 48, for example. be done. Task 291 includes the action item, the performer of the action item, and the due date of the action item.

Further, when the "Schedule" tab 292 is selected on the screen 290 of FIG. 48, the task management tool screen 290 of FIG. 48 transitions to a scheduler screen 300 as shown in FIG. The screen 300 of the scheduler in FIG. 49 displays the task 291 with the deadline "2019/09/19" of the task 291 displayed on the screen 290 in FIG. When the "board" tab 293 on the screen 300 of the scheduler shown in FIG. 49 is selected, the screen transitions to the screen 290 shown in FIG.

According to the screen 300 of FIG. 49, the action item is displayed at the position on the scheduler according to the time limit of the action item, so that it is possible to easily grasp what action item should be dealt with by when. The administrator of the action item can confirm the progress status of the action item by the executor at a glance.

[Third embodiment]
The action item transfer destination selection field 278 shown in FIG. 40 may display, for example, a button that enables selection of the scheduler tool. The registered member can register the action item in the scheduler tool, which is an example of the schedule management function of the same collaboration system 10, by selecting, for example, a button that enables selection of the scheduler tool from the action item transfer destination selection field 278.

On the screen 310 of the scheduler tool shown in FIG. 50, the action item 311 is displayed in the action item deadline "2019/09/19" of the scheduler of the action item executor. Note that the list of action items displayed in the scheduler may be traced from the link of the meeting displayed in the scheduler. The manager's scheduler may also display a list of action items for the meeting.

A new window 312 may be displayed by the executor of the action item operating (for example, right-clicking) the area of the action item 311 displayed in the scheduler. Window 312 includes an “edit” button 313 . The executor of the action item can update the progress (state) of the action item from "uncompleted" to "completed" by clicking the "edit" button 313, for example.

According to the screen 310 of FIG. 50, the action item is displayed at the position on the scheduler according to the time limit of the action item, so that it is possible to easily grasp what action item should be dealt with by when. Also, since the status of action items can be updated, it is possible to easily reflect which action items are being worked on and which action items have been completed.

[Other embodiments]
The information processing system 1 in FIG. 4 is an example, and may have a configuration as shown in FIG. 46, for example. FIG. 46 is a functional configuration diagram of an example of an information processing system according to this embodiment. In the information processing system 1 of FIG. 46, the request section 55 of the user terminal 40 in FIG.

Therefore, various requests such as a request for registering an action item to the action item management server 14 and an inquiry request for the state of the action item, which have been made by the request unit 55 , are made by the request unit 67 of the shared support server 11 . The creation unit 63 of the common use support server 11 also creates image data for screens such as execution event history screens to be displayed on the display control unit 54 of the user terminal 40 .

In addition, in the information processing system 1 of FIG. 4, the user terminal 40 may be provided with the detection unit 66 included in the sharing support server 11 in FIG. In this case, the user terminal 40 detects action item candidates from the user's utterance text data.

Since the action item candidates automatically extracted by voice recognition from the voice data included in the utterance data are action item candidates extracted by utterances during the meeting, there is a possibility that action item candidates that do not need to be registered as action items will be included. There is Therefore, in another embodiment, it is possible to select action item candidates that need to be registered and action item candidates that do not need to be registered by the following screen transition that calls the task setting screen from the action item candidate list screen. , the user can share only action items that should be registered as correspondence items with the executor.

FIG. 51 is a diagram for explaining management tool cooperation of action item candidates. As shown in FIG. 51, the action items automatically extracted by speech recognition are extracted as memoranda of proceedings (speech text data) after the meeting in about one sentence. As an example, on the execution event history screen 260, the display control unit 54 indicates that "Mr. A should correct and submit the document 1 by tomorrow", "Please do not forget to submit the document 2", and "Current Please tell the story to Mr. B." is displayed in the vertical direction on the screen. Only one piece of statement text data may be displayed, or a plurality of pieces of the statement text data may be displayed. The execution event history screen 260 is an example of a list display screen. The display control unit 54 is an example of first display control means. By selecting the "set performer" button 270 of the action button group 268 for each extracted action item, it is possible to cooperate with the task management function. The registered member, for example, puts the pointer of the pointing device 512 on the position of the statement text data of the action item candidate (mouse over it). In response to this operation, the display control unit 54 causes the action button groups 266 and 268 to be displayed on the execution event history screen 260 . In the example of FIG. 51, an action button group 268 is displayed by mousing over the three-point button "..." of the action button group 266 of FIG. Note that the action button groups 266 and 268 are examples, and one or three or more action button groups may be used. Speech text data of action item candidates and action button groups 266 and 268 are examples of selection components.

Note that the "set performer" button 270 in FIG. 51 is an example, and the names of the buttons, such as the "task registration" button and the "action item setting" button, imply the registration and setting of the action item. I wish I had. These buttons are also examples of selection components.

When the "set performer" button 270 of the action button group 268 is selected, the display control unit 54 causes the task setting screen 400 to be displayed. In the task setting screen 400, if the contents of the document automatically extracted by speech recognition specify "to whom", "action item", and "when", they are automatically set. It is also possible to manually change the extracted wording on the task setting screen 400 . The registered user confirms or inputs (selects) “who”, “action item”, and “when” on the task setting screen 400 . The registered user registers the action item by clicking (selecting) the register button 410 in FIG. By clicking (selecting) the registration button 410 , the request unit 55 transmits an action item registration request to the action item management server 14 . The task setting screen 400 is an example of a setting screen. The display control unit 54 is an example of second display control means. The request unit 55 is an example of request means.

FIG. 52 is a diagram for explaining how to present a user interface by registering action item candidates. When the task is registered, a progress display is added beside the action item candidate, as shown in FIG. Here, the progress status mark 286 is taken as an example, but a user icon for executing the action item, information on the scheduled completion date, or all of them may be displayed.

There is no problem as long as the automatically extracted action item candidate is displayed in a form that allows the user to recognize it as a formal action item. Also, action item candidates that have not been selected as action items may be deleted or expressed in a form that indicates that they are not action items.

The invention is not limited to the specifically disclosed embodiments above, but various modifications and changes are possible without departing from the scope of the claims. For example, a configuration that combines the first embodiment and the second embodiment, a configuration that combines the first embodiment and the third embodiment, a configuration that combines the second embodiment and the third embodiment, and a configuration that combines the first embodiment and the third embodiment. A configuration in which at least one of the first to third embodiments is combined with other embodiments is also possible. Note that the information processing system 1 described in the present embodiment is only an example, and it goes without saying that there are various system configuration examples according to usage and purpose.

Each function of the embodiments described above may be implemented by one or more processing circuits. Here, the "processing circuit" in this specification means a processor programmed by software to perform each function, such as a processor implemented by an electronic circuit, or a processor designed to perform each function described above. devices 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 representative of one of several computing environments for implementing the embodiments disclosed herein.

In one embodiment, sharing support server 11 and schedule management server 12 include multiple computing devices such as a server cluster. The multiple computing devices are configured to communicate with each other over any type of communication link, including communication network 50, shared memory, etc., to perform the processes disclosed herein.

Further, shared support server 11, schedule management server 12, speech-to-text server 13, action item management server 14, and user terminal 40 can be configured to share the above-disclosed processing steps in various combinations. For example, processes performed by a given unit may be performed by other units. Likewise, the functions of a given unit can be performed by other units. Further, each element of the shared support server 11, the schedule management server 12, the voice-to-text conversion server 13, and the action item management server 14 may be integrated into one device, or may be divided into a plurality of devices. .

1 information processing system 10 collaboration system 11 sharing support server 12 schedule management server 13 speech text conversion server 14 action item management server 20 action item management system 40 user terminal 50 communication network 51 transmission/reception unit 52 reception unit 54 display control unit 55 request unit 56 Generation unit 61 Transmission/reception unit 63 Creation unit 65 Judgment unit 66 Detection unit 67 Request unit 260 Execution event history screen

WO2011/099086

Claims (22)

An information processing system having a plurality of user terminals and a joint work support system for supporting joint work by a plurality of users operating the user terminals,
The user terminal is
registration means for registering one or more management tools including a scheduler;
receiving means for receiving, from the collaborative work support system, action item candidates based on the user's utterance data;
Displaying the received action item candidate on the display unit, and displaying on the display unit a screen for receiving a request for registering an action item from the action item candidate, a performer who executes the action item, and a time limit of the action item. display control means;
a first receiving means for receiving a registration operation of an action item from the action item candidates, an executor who executes the action item, and a deadline of the action item;
requesting action item management means for managing the action item to register the action item for which the registration operation has been accepted, the executor who executes the action item, and the time limit of the action item ; An action item that manages the action item without the manual registration operation when the statement data includes the action item, the performer who executes the action item, and the time limit of the action item. requesting means made to the managing means ;
a second receiving means for receiving a selection of one management tool from among the one or more management tools registered as transfer destinations of the action items;
display means for displaying an action item at a position on the scheduler corresponding to a time limit of the action item when the one management tool whose selection is received by the second reception means is a scheduler;
has
The collaborative work support system includes:
transmitting means for transmitting the action item candidate to the user terminal;
An information processing system having An information processing system having a plurality of user terminals and a joint work support system for supporting joint work by a plurality of users operating the user terminals,
The user terminal is
registration means for registering one or more management tools including a scheduler;
receiving means for receiving, from the collaborative work support system, action item candidates based on the user's utterance data;
Displaying the received action item candidate on the display unit, and displaying on the display unit a screen for receiving a request for registering an action item from the action item candidate, a performer who executes the action item, and a time limit of the action item. display control means;
a first receiving means for receiving a registration operation of an action item from the action item candidates, an executor who executes the action item, and a deadline of the action item;
transmitting the action item for which the registration operation has been accepted, the executor who executes the action item, and the time limit of the action item to the collaborative work support system; and a deadline of the action item, the action item, the performer who executes the action item, and the deadline of the action item can be registered without the manual registration operation. a transmitting means for transmitting to the joint work support system ;
a second receiving means for receiving a selection of one management tool from among the one or more management tools registered as transfer destinations of the action items;
display means for displaying an action item at a position on the scheduler corresponding to a time limit of the action item when the one management tool whose selection is received by the second reception means is a scheduler;
has
The collaborative work support system includes:
a transmitting means for transmitting the action item candidate to the user terminal;
receiving means for receiving the action item that has received the registration operation, the performer who executes the action item, and the deadline of the action item, which are transmitted from the user terminal;
action item management for managing the action item, requesting registration of the action item for which the registration operation received by the receiving means, a performer who executes the action item, and a deadline of the action item; Request means made to the means;
An information processing system having The joint work support system further comprises:
detection means for detecting the action item candidate based on the user's utterance data including voice-text data converted from the user's voice data or input text data input by the user;
3. The information processing system according to claim 1, comprising: The detection means performs morphological analysis processing on the user's utterance data, and combines at least two elements that may represent the content of the action item, the performer who executes the action item, or the time limit of the action item. 4. The information processing system according to claim 3, wherein said user's utterance data of one sentence containing is detected as said action item candidate. The detection means detects the action item candidate from the input user's utterance data using a learned model that has undergone machine learning so as to detect the action item candidate from the input user's utterance data. detect and
The learned model is a result of whether or not the detected action item candidate has been registered in the action item management means, and a result of whether or not the undetected action item candidate has been registered in the action item management means. 5. The information processing system according to claim 3 or 4, wherein the update is performed by machine learning based on . The display control means refers to the data table to narrow down the speaker of the action item candidate who accepts the registration request, the high-ranking authority user who participated in the group for supporting the joint work, or the organizer of the group, A screen for accepting the registration request from a speaker of the action item candidate, a high-ranking authority user who participated in the group for supporting the joint work, or the organizer of the group is displayed on the display unit. Item 6. The information processing system according to any one of Items 1 to 5. The display control means receives from the action item management means completion or non-completion information of the registered action item, and displays completion or non-completion information of the action item registered in the action item management means to the display section. 2. The information processing system according to claim 1, wherein the information processing system is displayed on the . 3. The information processing system according to claim 2, wherein said request means issues said registration request to said action item management means using an API (Application Programming Interface). 9. The information processing system according to claim 1, wherein said action item management means is included in an action item management system different from said joint work support system. An information processing device capable of communicating with a plurality of user terminals and supporting joint work by a plurality of users operating the user terminals,
Image data of a screen for displaying action item candidates based on said user's utterance data on a display unit, and accepting an operation for registering an action item from said action item candidates, a performer who executes said action item, and a time limit for said action item. a creating means for creating a
transmitting means for transmitting the image data to the user terminal;
receiving from the user terminal the action item, the performer who executes the action item, and the time limit of the action item for which the registration operation has been received from the action item candidate in the user terminal displaying the screen on the display unit; receiving means for
action item management for managing the action item, requesting registration of the action item for which the registration operation received by the receiving means, a performer who executes the action item, and a deadline of the action item; means, and further, when the user's utterance data includes the action item, the performer who executes the action item, and the time limit of the action item, the registration is performed without the manual registration operation. request means for making a request to action item management means for managing the action item ;
has
The creating means accepts selection of one management tool from among one or a plurality of management tools registered as a transfer destination of the action item, and when the one management tool accepted for selection is a scheduler, the action An information processing apparatus, wherein image data of a screen for displaying an action item at a position on the scheduler corresponding to a deadline of the item is created. detection means for detecting the action item candidate based on the user's utterance data including voice-text data converted from the user's voice data or input text data input by the user;
11. The information processing apparatus according to claim 10, further comprising: The detection means performs morphological analysis processing on the user's utterance data, and combines at least two elements that may represent the content of the action item, the performer who executes the action item, or the time limit of the action item. 12. The information processing apparatus according to claim 11, wherein the user's utterance data of one sentence containing is detected as the action item candidate. The detection means detects the action item candidate from the input user's utterance data using a learned model that has undergone machine learning so as to detect the action item candidate from the input user's utterance data. detect and
The learned model is a result of whether or not the detected action item candidate has been registered in the action item management means, and a result of whether or not the undetected action item candidate has been registered in the action item management means. 13. The information processing apparatus according to claim 11 or 12, wherein the update is performed by machine learning based on . 14. The information processing apparatus according to any one of claims 10 to 13, wherein the requesting means issues the registration request to the action item managing means using an API (Application Programming Interface). 15. The information processing apparatus according to claim 10, wherein said action item management means is included in an information processing apparatus different from said information processing apparatus. An information processing device capable of communicating with a plurality of user terminals and supporting joint work by a plurality of users operating the user terminals,
Image data of a screen for displaying action item candidates based on said user's utterance data on a display unit, and accepting an operation for registering an action item from said action item candidates, a performer who executes said action item, and a time limit for said action item. a creating means for creating a
transmitting means for transmitting the image data to the user terminal;
receiving from the user terminal the action item, the performer who executes the action item, and the time limit of the action item for which the registration operation has been received from the action item candidate in the user terminal displaying the screen on the display unit; receiving means for
Action item management means for managing action items, wherein the action item for which the registration operation received by the receiving means is received, the performer who executes the action item, and the time limit of the action item are stored as action items. and further, when the user's utterance data includes the action item, the performer who executes the action item, and the time limit of the action item, the action item can be executed without the manual registration operation. , an action item management means for storing an executor who executes the action item and a deadline of the action item in the storage unit ;
has
The creating means accepts selection of one management tool from among one or a plurality of management tools registered as a transfer destination of the action item, and when the one management tool accepted for selection is a scheduler, the action An information processing apparatus, wherein image data of a screen for displaying an action item at a position on the scheduler corresponding to a deadline of the item is created. A user terminal capable of communicating with a joint work support system that supports joint work by a plurality of users,
registration means for registering one or more management tools including a scheduler;
receiving means for receiving, from the collaborative work support system, action item candidates based on the user's utterance data;
Displaying the received action item candidate on the display unit, and displaying on the display unit a screen for receiving a request for registering an action item from the action item candidate, a performer who executes the action item, and a time limit of the action item. display control means;
a first receiving means for receiving a registration operation of an action item from the action item candidates, an executor who executes the action item, and a deadline of the action item;
requesting action item management means for managing the action item to register the action item for which the registration operation has been accepted, the executor who executes the action item, and the time limit of the action item ; An action item that manages the action item without the manual registration operation when the statement data includes the action item, the performer who executes the action item, and the time limit of the action item. requesting means made to the managing means ;
a second receiving means for receiving a selection of one management tool from among the one or more management tools registered as transfer destinations of the action items;
display means for displaying an action item at a position on the scheduler corresponding to a time limit of the action item when the one management tool whose selection is received by the second reception means is a scheduler;
A user terminal having a A user terminal capable of communicating with a joint work support system that supports joint work by a plurality of users,
registration means for registering one or more management tools including a scheduler;
receiving means for receiving, from the collaborative work support system, action item candidates based on the user's utterance data;
Displaying the received action item candidate on the display unit, and displaying on the display unit a screen for receiving a request for registering an action item from the action item candidate, a performer who executes the action item, and a time limit of the action item. display control means;
a first receiving means for receiving a registration operation of an action item from the action item candidates, an executor who executes the action item, and a deadline of the action item;
In order for the collaborative work support system to register the action item for which the registration operation has been accepted, the executor who executes the action item, and the deadline of the action item in action item management means for managing action items, the collaboration When the action item, the executor who executes the action item, and the time limit of the action item are included in the user's utterance data, and the action item is transmitted to the work support system, the operation can be performed without the manual registration operation. transmission means for transmitting an action item, a performer who executes the action item, and a deadline of the action item to the collaborative work support system ;
a second receiving means for receiving a selection of one management tool from among the one or more management tools registered as transfer destinations of the action items;
display means for displaying an action item at a position on the scheduler corresponding to a time limit of the action item when the one management tool whose selection is received by the second reception means is a scheduler;
A user terminal having a A user terminal that can communicate with a joint work support system that supports joint work by multiple users,
registration means for registering one or more management tools including a scheduler;
receiving means for receiving, from the collaborative work support system, action item candidates based on the user's utterance data;
Displaying the received action item candidates on a display unit, and displaying on the display unit a screen for accepting an operation for registering an action item from the action item candidates, a performer who executes the action item, and a time limit for the action item. display control means;
a first receiving means for receiving a registration operation of an action item from the action item candidates, an executor who executes the action item, and a deadline of the action item;
requesting action item management means for managing the action item to register the action item for which the registration operation has been accepted, the executor who executes the action item, and the time limit of the action item ; An action item that manages the action item without the manual registration operation when the statement data includes the action item, the performer who executes the action item, and the time limit of the action item. Request means made to the management means ,
second receiving means for receiving a selection of one management tool from among the one or more management tools registered as transfer destinations of the action items;
display means for displaying an action item at a position on the scheduler corresponding to a time limit of the action item when the one management tool whose selection is received by the second reception means is a scheduler;
A program to function as A user terminal that can communicate with a joint work support system that supports joint work by multiple users,
registration means for registering one or more management tools including a scheduler;
receiving means for receiving, from the collaborative work support system, action item candidates based on the user's utterance data;
Displaying the received action item candidate on the display unit, and displaying on the display unit a screen for receiving a request for registering an action item from the action item candidate, a performer who executes the action item, and a time limit of the action item. display control means;
a first receiving means for receiving a registration operation of an action item from the action item candidates, an executor who executes the action item, and a deadline of the action item;
In order for the collaborative work support system to register the action item for which the registration operation has been accepted, the executor who executes the action item, and the deadline of the action item in action item management means for managing action items, the collaboration When the action item, the executor who executes the action item, and the time limit of the action item are included in the user's utterance data, and the action item is transmitted to the work support system, the operation can be performed without the manual registration operation. transmission means for transmitting an action item, a performer who executes the action item, and a deadline of the action item to the collaborative work support system ;
second receiving means for receiving a selection of one management tool from among the one or more management tools registered as transfer destinations of the action items;
display means for displaying an action item at a position on the scheduler corresponding to a time limit of the action item when the one management tool whose selection is received by the second reception means is a scheduler;
A program to function as The display control means is
A first display for displaying, on the user terminal, a list display screen for displaying the action item candidates, the list display screen including selection components for accepting selection of an action item to be registered from the action item candidates. a display control means of
a second display control means for displaying, on the user terminal, a setting screen for accepting setting of the action item to be registered in accordance with the selection of the selected component displayed on the display unit;
has
21. The program according to claim 19, wherein said accepting means accepts said registration operation via said setting screen. 22. The program according to any one of claims 19 to 21, wherein said action item management means is included in an information processing device connected via a network.

Images