JP2021152875A - Information processing system, information processing apparatus, user terminal, information processing method, and program - Google Patents

Abstract

To provide an information processing system that can display action item candidates and playback information in video recording data or sound recording data of the action item candidates.SOLUTION: An information processing system 1 has a plurality of user terminals and a cooperative work support system (collaboration system 10) that supports cooperative work performed by a plurality of users who operate the user terminals. The cooperative work support system has transmission means that transmits, to the user terminals, action item candidates based on voice text data converted from video recording data or sound recording data and playback information in video recording data or sound recording data of the action item candidates. The user terminals each comprise: receiving means that receives the action item candidates and the playback information from the cooperative work support system; and display control means that displays the received action item candidates and the playback information on a display.SELECTED DRAWING: Figure 1

Description

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

Conventionally, the content of important remarks is shown by converting the voice spoken by the meeting attendees into text, referring to multiple rule information for identifying important remarks, and detecting important remarks from the text. There is known a conference support device that extracts and presents to conference attendees (see, for example, Patent Document 1).

In recent years, tools (collaboration tools) that support collaborative work in groups by providing functions such as communication functions and information sharing functions to multiple users who work in groups or teams have been used. Has been done. In the collaboration tool, multiple users who form a group or team for collaborative work can use communication functions such as chat function and voice call function and information sharing function to make online meetings and users physical. You can hold a meeting that gathers in the same place.

In a meeting using a communication function or an information sharing function, the recorded data or recorded data of a plurality of users who form a group or a team and perform collaborative work includes action item candidates to be assigned to the user and executed. May be. However, the conventional collaboration tool does not have a mechanism for displaying the action item candidate included in the recorded data or the recorded data and the playback information in the recorded data or the recorded data of the action item candidate.

An object of the embodiment of the present invention is to provide an information processing system capable of displaying an action item candidate and recorded data of the action item candidate or playback information in the recorded data.

In order to achieve the above-mentioned problems, claim 1 of the present application is an information processing system including a plurality of user terminals and a collaborative work support system that supports collaborative work by a plurality of users who operate the user terminals. The collaborative work support system uses the user terminal to obtain an action item candidate based on the recorded data or voice text data converted from the recorded data, and the recorded data of the action item candidate or the reproduction information in the recorded data. The user terminal has a transmitting means for transmitting the action item candidate and the reproduction information to the receiving means for receiving the action item candidate and the reproduction information from the collaborative work support system, and a display unit for receiving the action item candidate and the reproduction information. It is characterized by having a display control means for displaying on the screen.

According to the embodiment of the present invention, the action item candidate and the recorded data of the action item candidate or the reproduction information in the recorded data can be displayed.

It is a block diagram of an example of an information processing system which concerns on this embodiment. It is a hardware block diagram of an example of the computer which concerns on this embodiment. It is a figure which shows the software structure of a user terminal. It is a functional block diagram of an example of an information processing system which concerns on this embodiment. It is a conceptual diagram which shows the user authentication management table. It is a conceptual diagram which shows the access management table. It is a conceptual diagram which shows the schedule management table. It is a conceptual diagram which shows the execution event management table. It is a conceptual diagram which shows the content management table. It is a conceptual diagram which shows the action item candidate management table. It is a conceptual diagram which shows the user authentication management table. It is a conceptual diagram which shows the user management table. It is a conceptual diagram which shows the union management table. It is a conceptual diagram which shows the union reservation management table. It is a conceptual diagram which shows the event management table. It is a conceptual diagram which shows the server authentication management table. It is a conceptual diagram which shows the project member management table. It is a conceptual diagram which shows the execution event history management table. It is a conceptual diagram which shows the execution event management table. It is a conceptual diagram which shows the related information management table. It is a conceptual diagram which shows the action item management table. It is a sequence diagram which showed the registration process of a schedule. It is the figure which showed the sign-in screen. This is an example of the initial screen of the user terminal. It is a figure which showed the schedule input screen. It is a sequence diagram which showed the start processing of an event. It is a sequence diagram which showed the start processing of an event. It is a figure which showed the reservation list screen of a union. It is the figure which showed the project list screen. It is a figure which showed the detailed information screen of an event. It is a sequence diagram which showed the registration process of the execution event history. It is a flowchart which showed the voice-to-text conversion process. It is a flowchart which showed the process of detecting an action item candidate. It is the figure which showed a part of the execution event history screen. It is the figure which showed a part of the execution event history screen. It is the figure which showed a part of the execution event history screen. It is the figure which showed a part of the execution event history screen. It is the figure which showed a part of the execution event history screen. It is the figure which showed a part of the execution event history screen. It is the figure which showed a part of the task management screen. It is a sequence diagram which showed the browsing process of the execution event history. It is a sequence diagram which showed the browsing process of the execution event history. It is a figure which showed the execution event list screen. It is the figure which showed a part of the execution event history screen. It is a functional block diagram of an example of an information processing system which concerns on this embodiment. It is the figure which showed a part of the execution event history screen.

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 collaborative work is called a project, and users belonging to the project are called members of the project. Further, in the present embodiment, the work assigned to a member and executed is called an action item as an example, but it may also be called a task or a follow-up item. The "file" described in this embodiment indicates an "electronic file".

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

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 network by wireless communication 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 to perform one work together. As an example of a collaboration system, a place where people gather to give opinions and consultations for a specific purpose (including the case where the user terminals are physically separated but connected to each other via a network). ), Using a PC, mobile terminal, electronic blackboard, projector, conference tool, etc., voice call, video call, chat, screen sharing (projection), information sharing, agenda review, document creation and compilation, schedule setting, action It is a system used for deciding items, etc. The collaboration system 10 has the same meaning as the collaborative work support system. The collaboration system 10 provides a collaboration tool that supports collaborative work by project members. The collaboration tool is a means, function, or tool for supporting a plurality of people to perform one work together. Collaborative work means that multiple people work together on one task. Collaboration tools include functions such as communication function, schedule management function, information sharing function, and action item management function.

The functions of the collaboration tools provided by the collaboration system 10 do not have to be the same. Therefore, in FIG. 1, the server configurations of the two collaboration systems 10 are different. 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 a schedule management function to the members of the project. The voice-to-text conversion server 13 converts recorded data or recorded data in which utterances by project members are recorded (recorded or recorded) into text data. The voice-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 the action item management function to the members of the project. An action item is a work that needs to be assigned to a user and executed. As shown in the information processing system 1 of FIG. 1, the action item management server 14 may be provided in the action item management system 20 separate from the collaboration system 10. The action item management system 20 provides an action item management function to a user who operates a user terminal 40. The action item management function is a function that accepts registration of an action item from a user and manages the action item. The action item management function is composed of at least one function or means in the action item management server 14 of FIG. Of course, all the functions and means in the action item management server 14 may be included. The action management function has the same meaning as the action management means.

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

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: projector), an IWB (Interactive White Board: a white board having an electronic whiteboard function capable of intercommunication), an output device such as a digital signage, a HUD (Head Up Display) device, and the like. Industrial machines, image pickup devices, sound collectors, medical devices, network home appliances, automobiles (Connected Cars), notebook PCs (Personal Computers), mobile phones, smartphones, tablet terminals, game machines, PDA (Personal Digital Assistant), digital cameras, It may be a wearable PC, a desktop PC, or the like.

Further, the shared support server 11, the schedule management server 12, the voice 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 sharing support server 11, the schedule management server 12, the voice-text conversion server 13, and the action item management server 14 are integrated. good.

Further, each of the shared support server 11, the schedule management server 12, the voice-text conversion server 13, and the action item management server 14 may be configured to distribute and realize each function among a plurality of computers.

Further, the shared support server 11, the schedule management server 12, the voice-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 a computer in an on-premises environment. There may be. As described above, the information processing system 1 of FIG. 1 is an example.

The collaboration system 10, the sharing support server 11, the schedule management server 12, the voice-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 are devices having a communication function. No.

The collaboration system 10, the sharing support server 11, the schedule management server 12, the voice-text conversion server 13, the action item management server 14, and the action item management system 20 include, for example, output devices such as PJs, IWBs, and digital signage, HUD devices, and the like. It may be an industrial machine, an imaging device, a sound collecting device, a medical device, a network home appliance, an automobile, a notebook PC, a mobile phone, a smartphone, a tablet terminal, a game machine, a PDA, a digital camera, a wearable PC, a desktop PC, or the like.

The collaboration information provided by the collaboration system 10 to the project members by the collaboration tool includes synchronous collaboration information and asynchronous collaboration information. Synchronous collaboration information is information that is exchanged in real time during a place where people gather to give opinions and consultations for a specific purpose (for example, a meeting). Synchronous collaboration information includes, for example, voice calls, video calls, screens shared on PCs, mobile terminals, electronic blackboards, etc. (texts and charts input from PCs, mobile terminals, etc., handwritten input contents on screens such as electronic blackboards, etc.) , Including), 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 in the venue before and after a venue (for example, a meeting) where people gather to give opinions and consultations on a specific purpose. Asynchronous collaboration information includes, for example, chat, messages, content, scheduling, action items, recording / recording content, and the like. An action item is an operation that determines an executor and causes the executor to execute the action item.

These terms are also described in the conference solution report (“Magic Quadrant Meeting Solutions”, published in September 2019) provided by Gartner.

<Hardware configuration>
The collaboration system 10, the sharing support server 11, the schedule management server 12, the voice-text conversion server 13, the action item management server 14, the action item management system 20, and the user terminal 40 of FIG. 1 have, for example, the hardware configuration shown in FIG. It is realized by the computer 500. FIG. 2 is a hardware configuration diagram of an example of a computer according to the present embodiment.

As shown in FIG. 2, the computer 500 includes a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, a RAM (Random Access Memory) 503, an HD504, an HDD (Hard Disk Drive) controller 505, and a 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.

Of these, the CPU 501 controls the operation of the entire computer 500 according to a program. The ROM 502 stores a program used to drive the CPU 501 such as an IPL. The RAM 503 is used as a work area of the CPU 501. The HD504 stores various data such as programs. The HDD controller 505 controls reading or writing of various data to the HD 504 according to the control of the CPU 501.

The display 506 displays various information such as a cursor, a menu, a window, a character, or an image. 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. The network I / F 509 is an interface for data communication using the network 16. The data bus 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501.

The keyboard 511 is a kind of input means including a plurality of keys for inputting characters, numerical values, various instructions, and the like. The 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. The DVD-RW drive 514 controls reading or writing of various data to the DVD-RW 513 as an example of the removable recording medium. In addition, it is not limited to DVD-RW, and may be DVD-R or the like. The media I / F 516 controls reading or writing (storage) of data to a recording medium 515 such as a flash memory.

Each of the above programs may be a file in an installable format or an executable format, and may be recorded and distributed on a computer-readable recording medium. Examples of recording media include CD-R (Compact Disc Recordable), DVD (Digital Versatile Disk), Blu-ray Disc, SD card and the like. In addition, the recording medium can be provided domestically or internationally as a program product.

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

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

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

<< Functional configuration of shared support server >>
The shared support server 11 includes a transmission / reception unit 61, an authentication unit 62, a creation unit 63, a generation unit 64, a determination unit 65, a detection unit 66, and a storage / reading processing unit 69. Each of these parts functions or functions as any of the components shown in FIG. 2 operates by an instruction from the CPU 501 according to the sharing support program developed on the RAM 503 from the HD 504. It is a means. Further, the shared support server 11 has a storage unit 6000 constructed by the HD504 or the like shown in FIG.

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

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

The schedule management server 12 manages a plurality of schedulers, and the schedulers used may differ depending on the organization. Therefore, management by the access management table of FIG. 6 is required.

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

Of these, the scheduled event ID is identification information for identifying a 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 event that is actually executed or an event that is being executed among the reserved events.

The execution event ID is an example of execution event identification information for identifying an executed event or an executed event. The reservation person's name is the name of the person who reserved the union such as the conference room. A union is an object, service, space (room), place or information shared by multiple people or groups. A conference room is an example of a union shared by a plurality of users. If the union is a conference room, for example, the name of the organizer. The scheduled start time indicates the scheduled start time 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 reservation person.

The user IDs of other participants are identification information for identifying participants other than the reservation person. The 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 in the event corresponding to the scheduled event ID registered by the user. The file data is data in a predetermined file format created by 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. In the storage unit 6000, an execution event management DB 6004 configured by an execution event management table as shown in FIG. 8 is constructed. In this execution event management table, the execution event ID is associated and managed for each project ID.

The project ID is identification information for identifying the project (an example of the project identification information). A project represents a group, team, or group of users configured to achieve a particular goal, plan, or project. Members belonging to the same project can share the execution event history such as the minutes of the event associated with the project ID. The project ID is assigned to each project. The project ID may 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. In the storage unit 6000, a content management DB 6005 composed of a content management table as shown in FIG. 9 is constructed. In this content management table, the content processing ID, the type of content processing, the content of the content, and the start date and time and the end date and time of the content processing are managed in association with each execution event ID.

Here, the content is the content of an execution event that occurred at an event such as a meeting in a certain project, or the material used at the event. Types of content processing include recording, snapshots, voice-to-text conversion, action item generation, recording, chat, material sending, and the like. Further, the content processing ID is identification information for identifying the processing of the content generated in each event.

The content includes historical information indicating the execution content of the event and action items generated by the executed event. The history information indicating the execution content of the event is data such as recorded data, image data, audio text data, text data, recorded data, or materials. The voice text data is recorded data or text data obtained by converting the recorded data into voice text. The remark text data is the recorded data or the voice text data converted into voice text from the recorded data, and the input text data input for chat or message.

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

When the type of content processing is "recording", the content of the content includes a URL indicating a storage destination of the recorded recording data. When the type of content processing is "recording", the content of the content includes a URL indicating a storage destination of the recorded recorded data. When the type of content processing is "snapshot", the content of the content includes a URL indicating a save destination of the image data of the screen acquired by the snapshot (capture). The capture is to save the image (still image, moving image) displayed on the display 506 as image data. When the type of content processing is "voice-text conversion", the content of the content includes the recorded data or a URL indicating the storage destination of the voice-text data converted from the recorded data.

An action item indicates the content of an action that occurs at an event such as a meeting in a certain project and should be handled by a person related to the event. When the type of content processing is "action item occurrence", the content content includes the user ID of the performer of the action item, the deadline date for completing the action item, and the storage destination of the text data representing the content of the action item. Includes the URL to indicate.

(Action item candidate management table)
FIG. 10 is a conceptual diagram showing an action item candidate management table. In the storage unit 6000, an action item candidate management DB 6006 configured by an action item candidate management table as shown in FIG. 10 is constructed. In this action item candidate management table, the statement text data ID, the content processing ID, the playback position information, the content, and the action item ID are associated and managed.

The remark text data ID is identification information for identifying the remark text data of the action item candidate detected from the voice text data identified by the content processing ID. The action item candidate is utterance text data that may be registered (highly likely) as an action item detected from the contents of utterances or text input by project members at an event such as an online conference. As an example of an action item candidate, there is a statement text data containing at least two elements of "who", "what", and "by when". The reproduction position information represents the reproduction position (for example, the elapsed time from the beginning of the recorded data or the recorded data) in the recorded data or the recorded data of the spoken text data of the action item candidate identified by the spoken text data ID. The playback position information may include the remark time of the action item candidate. The content represents the content of the action item candidate. The action item ID represents the action item when the action item candidate is registered as an action item, and is blank if the action item candidate is not registered as an action item.

(Each function configuration of the shared support server)
Next, each functional configuration of the shared support server 11 will be described in detail. In the following description of each functional configuration of the shared support server 11, among the constituent elements shown in FIG. 2, the main constituent elements for realizing each functional configuration of the shared support server 11 are used. The relationship is also explained.

The transmission / reception unit 61 of the shared support server 11 shown in FIG. 4 is realized by the instruction from the CPU 501 shown in FIG. 2 and the network I / F 509 shown in FIG. The transmission / reception 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. The transmission / reception unit 61 is an example of a transmission means or a reception means.

The authentication unit 62 is realized by the command from the CPU 501 shown in FIG. 2, and the information (user ID, organization ID, and password) sent from the user terminal 40 is registered in the user authentication management DB 6001 in advance. Authentication is performed by determining whether the information is provided.

The creation unit 63 is realized by the instruction from the CPU 501 shown in FIG. 2, and includes, for example, the reservation information sent from the schedule management server 12, the image data of the reservation list screen based on the schedule information, and various screens. Create image data for.

The generation unit 64 is realized by the instruction from the CPU 501 shown in FIG. 2, and generates the execution event ID, the content processing ID, and the URL of the storage destination. The determination unit 65 is realized by an instruction from the CPU 501 shown in FIG. 2 and makes various determinations. This determination will be described later. The detection unit 66 is realized by the command from the CPU 501 shown in FIG. 2, and detects the recording data or the speech text data of the action item candidate described later from the voice text data of the user who converted the recording data.

Further, the detection unit 66 detects the recorded data of the remark text data of the action item candidate or the reproduction position information in the recorded data. The playback position information is necessary to start playback from the position of the action item candidate's speech text data (or shortly before that position) when playing back the recorded data or the recorded data of the action item candidate's speech text data. Information. For example, the reproduction position information is represented by the recorded data or the elapsed time from the beginning of the recorded data. Further, the playback position information may include the remark time of the action item candidate.

The storage / reading processing unit 69 is realized by the command from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. 2, and various data can be stored in the storage unit 6000 or stored in the storage unit 6000. Performs processing such as reading various stored data.

<< Functional configuration of schedule management server >>
The schedule management server 12 has a transmission / reception unit 81, an authentication unit 82, a generation unit 83, and a storage / reading processing unit 89. Each of these parts functions or functions as any of the components shown in FIG. 2 operates by an instruction from the CPU 501 according to a schedule management program developed on the RAM 503 from the HD 504. It is a means. Further, the schedule management server 12 has a storage unit 8000 constructed by the HD 504 shown in FIG.

(User authentication management table)
FIG. 11 is a conceptual diagram showing a user authentication management table. In the storage unit 8000, a user authentication management DB 8001 configured by a user authentication management table as shown in FIG. 11 is constructed. In this user authentication management table, a user ID for identifying a user is managed by associating an organization ID for identifying an organization to which the user belongs and a password.

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

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

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

The scheduled start date and time indicates the scheduled start date and time 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 the year, month, day, hour, minute, second, and time zone. Each date and time in FIG. 14 is represented up to year, month, day, hour, and minute due to space limitations.

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

Of these, the scheduled start date and time of the event indicates the scheduled start date and time when the event is 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 the year, month, day, hour, minute, second, and time zone. Each date and time in FIG. 15 is represented up to year, month, day, hour, and minute due to space limitations. Further, in the event management table of FIG. 15, the file data of the material file used in the event shown in the schedule information is managed in association with the schedule event ID.

(Server authentication management table)
FIG. 16 is a conceptual diagram showing a server authentication management table. In the storage unit 8000, a server authentication management DB 8006 configured by a server authentication management table as shown in FIG. 16 is constructed. In this server authentication management table, an access ID and an access password are associated and managed. 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. 17 is a conceptual diagram showing a project member management table. A project member management DB 8007 composed of a project member management table as shown in FIG. 17 is constructed in the storage unit 8000. In this project member management table, the project ID, the project name, and the user ID of each project member are associated and managed for each organization ID.

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

The execution event history management DB 8008 manages a part of 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 content is the same, except that the notation method (http: // or c: //) of the save destination of the content data is different.

(Execution event management table)
FIG. 19 is a conceptual diagram showing an execution event management table. In the storage unit 8000, an execution event management DB 8009 configured by an execution event management table as shown in FIG. 19 is constructed. In this execution event management table, the event name, the start date and time of the event, and the end date and time are associated with the execution event ID and managed. The execution event management DB 8009 manages the information related to the event actually executed among the schedule information managed in the event management DB 8005.

(Related information management table)
FIG. 20 is a conceptual diagram showing a related information management table. In the storage unit 8000, a related information management DB 8010 configured by a related information management table as shown in FIG. 20 is constructed. In this related information management table, related information in a state in which each information (data) is associated is managed for each project ID and execution event ID. The related information is managed in association with the time zone in which the content is generated, the recording / recording data, the voice text data, and the screen data.

The content occurrence time zone indicates the elapsed time from the start date and time of the event at the time when the content is generated in the executed event. The content generation 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 time zone in which the content is generated is an example of time information.

Further, the recording / recorded data includes a content processing ID and a type of content processing. The voice text data and the screen data include a content processing ID, a content processing type, and a sequence number. The sequence No. indicates the order of occurrence time when the content processing occurs in each of the voice text data and the screen data.

(Each function configuration of schedule management server)
Next, each functional configuration of the schedule management server 12 will be described in detail. In the following description, in explaining each functional configuration of the schedule management server 12, among the constituent elements shown in FIG. 2, the main constituent elements for realizing each functional configuration of the schedule management server 12 are used. The relationship is also explained.

The transmission / reception unit 81 of the schedule management server 12 shown in FIG. 4 is realized by the instruction from the CPU 501 shown in FIG. 2 and the network I / F 509 shown in FIG. The transmission / reception 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 the command from the CPU 501 shown in FIG. 2, and the information (user ID, organization ID, and password) sent from the user terminal 40 is registered in the user authentication management DB 8001 in advance. Authentication is performed by determining whether the information is provided. Further, the authentication unit 82 authenticates by determining whether the information (access ID and access password) sent from the shared support server 11 is the information registered in advance in the server authentication management DB 8006.

The generation unit 83 is a function of generating related information registered in the related information management DB 8010, which is realized by an instruction from the CPU 501 shown in FIG.

The storage / reading processing unit 89 is realized by the command from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. 2, and stores various data in the storage unit 8000 or stores various data in the storage unit 8000. Performs processing such as reading various stored data.

<< Functional configuration of voice-to-text conversion server >>
The voice-text conversion server 13 has a transmission / reception unit 91, a conversion unit 93, and a storage / reading processing unit 99. Each of these parts is a function or a functioning means realized by operating any of the components shown in FIG. 2 by an instruction from the CPU 901 according to a program developed on the RAM 503 from the HD 504. .. Further, the voice-to-text conversion server 13 of FIG. 4 has a storage unit 9000 constructed by the HD 504 shown in FIG.

(Voice-text conversion server function configuration)
Next, each functional configuration of the voice-to-text conversion server 13 will be described in detail. In the following, in explaining each functional configuration of the voice-text conversion server 13, among the constituent elements shown in FIG. 2, the main constituent elements for realizing each functional configuration of the voice-text conversion server 13. The relationship with is also explained.

The transmission / reception unit 91 of the voice-to-text conversion server 13 shown in FIG. 4 is realized by the command from the CPU 501 shown in FIG. 2 and the network I / F 509 shown in FIG. The transmission / reception unit 91 transmits / receives various data (or information) to / from another server, another system, or the like via the communication network 50.

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

The storage / reading processing unit 99 is realized by the command from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. 2, and various data can be stored in the storage unit 9000 or stored in the storage unit 9000. Performs processing such as reading various stored data.

<< Functional configuration of action item management server >>
The action item management server 14 shown in FIG. 4 has a transmission / reception unit 101, an authentication unit 102, a creation unit 103, a registration unit 104, an action unit 105, and a storage / reading processing unit 109. Each of these parts has a function realized by operating any of the components shown in FIG. 2 by an instruction from the CPU 501 according to an action item management program developed on the RAM 503 from the HD 504. It is a means of functioning. Further, the action item management server 14 has a storage unit 10000 constructed by the HD504 or the like shown in FIG.

(User authentication management table)
In the storage unit 10000, a user authentication management DB 10001 composed of a user authentication management table as shown in FIGS. 5 and 11 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, and an organization for identifying the organization to which the user belongs. The ID and password are associated and managed.

(Action item management table)
FIG. 21 is a conceptual diagram showing an action item management table. In the storage unit 10000, an action item management DB 10002 configured by an action item management table as shown in FIG. 21 is constructed. In this action item management table, the action item ID, the state, the user ID of the performer of the action item, the expiration date of the action item, the content of the action item, the content processing ID, and the playback position information are managed in association with each other. .. The state indicates whether the action item has been completed or not completed. Further, the action item management server 14 identifies the recorded data or the recorded data that detected the speech text data of the action item based on the content processing ID and the playback position information of the action item management table of FIG. 21, and the speech text data of the action item. The recorded data or the playback position in the recorded data can be specified.

(Each function 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, in explaining each function configuration of the action item management server 14, among the components shown in FIG. 2, the main components for realizing each function configuration of the action item management server 14 are used. The relationship is also explained.

The transmission / reception unit 101 of the action item management server 14 shown in FIG. 4 is realized by the instruction from the CPU 501 shown in FIG. 2 and the network I / F 509 shown in FIG. The transmission / reception 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 the command from the CPU 501 shown in FIG. 2, and the information (user ID, organization ID, and password) sent from the user terminal 40 is registered in advance in the user authentication management DB 10001. Authentication is performed by determining whether or not the information is available.

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

The registration unit 104 is realized by a command from the CPU 501 shown in FIG. 2, for example, receives an action item registration request from a user terminal 40 or the like, and registers the action item in the action item management table shown in FIG. The action unit 105 is realized by an instruction from the CPU 501 shown in FIG. The action unit 105 receives, for example, a notification of completion of an action item from a user terminal 40 or the like, and updates the state of the action item management table shown in FIG. 21 from "incomplete" to "completed" according to the notification of completion.

Further, when the action unit 105 receives an inquiry request for the state of the action item from, for example, the sharing support server 11 or the user terminal 40, the action unit 105 reads the state of the action item corresponding to the inquiry request from the action item management table shown in FIG. And respond. As a result, the shared support server 11, the user terminal 40, and the like can confirm the completion / incompleteness of the action item.

Further, the storage / reading processing unit 109 is realized by the command from the CPU 501 shown in FIG. 2 and the HDD controller 505 shown in FIG. 2, and stores various data in the storage unit 10000 or is stored in the storage unit. A process of reading various data stored in 10000 is performed.

<< Functional configuration of user terminal >>
The user terminal 40 has a transmission / reception unit 51, a reception unit 52, a display control unit 54, a request unit 55, a generation unit 56, a reproduction unit 57, a sound control unit 58, and a storage / reading processing unit 59. Each of these parts is a function or a functioning means realized by operating any of the components shown in FIG. 2 by an instruction from the CPU 501 according to a program developed on the RAM 503 from the HD 504. .. Further, the user terminal 40 has a storage unit 5000 constructed by the HD 504 shown in FIG.

(Each function configuration of the user terminal)
Next, each component of the user terminal 40 will be described. The transmission / reception unit 51 is realized by the command from the CPU 501 and the network I / F 509 shown in FIG. 2, and transmits / receives various data (or information) to / from another server or another system via the communication network 50. .. The transmission / reception unit 51 is an example of a transmission means or a reception means.

The reception unit 52 is mainly realized by the instructions from the CPU 501 shown in FIG. 5, the keyboard 511, and the pointing device 512, and receives various inputs by the user. The reception unit 52 is an example of reception means. Further, the display control unit 54 is realized by a command 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 the browser 5502b running on the OS 5501 shown in FIG. .. Then, the display control unit 54 downloads a Web APP (Web Application) including, for example, HTML (HyperText Markup Language) and includes CSS (Cascading Style Sheets) or JAVA SCRIPT (registered trademark), and various types generated by the Web APP. The image data is displayed on the display 506. Further, the display control unit 54 displays image data generated by "HTML5" including data in, for example, XML (Extensible Markup Language), JSON (JavaScript Object Notation) or SOAP (Simple Object Access Protocol) format on the display 506. Let me. The display control unit 54 is an example of the display control means.

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

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

The generation unit 56 generates image data related to the text data which is the content image data in order to render the text data which is the content data and display the rendered data, for example. Rendering is a process of interpreting data described in a language for describing a Web page (HTML, CSS, XML, etc.) and calculating the arrangement of characters, image data, and the like actually displayed on the screen.

The reproduction unit 57 is realized by a command from the CPU 501 shown in FIG. 2, and displays various screens on the display 506. For example, the reproduction unit 57 reproduces the recorded data or the recorded data by starting and executing the reproduction application 5502c running on the OS 5501 shown in FIG. By designating the reproduction position, the reproduction application 5502c can start the reproduction of the recorded data or the recorded data from the reproduction position.

The sound control unit 58 is a function realized by a command from the CPU 501 shown in FIG. 5 and outputs a sound signal from the speaker. The sound control unit 58 sets the sound data to be output from the speaker, and outputs the sound signal related to the set sound data from the speaker to reproduce the sound data.

The storage / reading processing unit 59 is executed by an instruction from the CPU 501 shown in FIG. 2 and an HDD controller 505 or the like, and is a process of storing various data in the storage unit 5000 or reading various data from the storage unit 5000. I do.

Each of the above IDs is an example of identification information. In addition, the organization ID includes a company name, a business establishment name, a department name, an 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, the processing or operation of each embodiment will be described.

<< Schedule registration process >>
Here, a process in which the reservation person A (Rikotaro) registers his / her own schedule from the user terminal 40 to the schedule management server 12 will be described. FIG. 22 is a sequence diagram showing the schedule registration process. FIG. 23 is a diagram showing a sign-in screen. FIG. 24 is an example of the initial screen of the user terminal. FIG. 25 is a diagram showing a schedule input screen.

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

On the sign-in screen 530, an input field 531 for inputting a user ID and an organization ID of a user, an input field 532 for inputting a password, a sign-in button 538 pressed when signing in, and sign-in are displayed. It includes a cancel button 539 that is pressed when canceling. Here, the user ID and the organization ID are the e-mail addresses of the user A. The user name part of the e-mail address is the user ID, and the domain name part is the organization ID. The input field 531 may be an input field for separately inputting the user ID and the organization ID instead of the e-mail address.

Next, when the user A inputs his / her user ID and organization ID in the input field 531, enters his / her password in the input field 532, and presses the sign-in button 538, the reception unit 52 signs in. (Step S12).

Then, the transmission / reception unit 51 of the user terminal 40 transmits the sign-in request information indicating the 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) received in step S12. As a result, 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 by using the user ID, the organization ID, and the password (step S14). Specifically, the storage / reading processing unit 89 has a user ID, an organization, and an organization corresponding to the set of the user ID, the organization ID, and the password received in step S13 in the user authentication management DB 8001 (see FIG. 10). Search for ID and password pairs.

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 unjust (illegal) user. If it is not valid, the transmission / reception unit 81 notifies the user terminal 40 that it is not valid. Here, the case where it is valid will be continued. Next, the transmission / reception unit 81 transmits the authentication result to the user terminal 40 (step S15). As a result, the transmission / reception unit 51 of the user terminal 40 receives the authentication result.

Next, when the generation unit 56 of the user terminal 40 receives the authentication result to the effect that it is valid in step 15, the generation unit 56 generates the initial screen 540 as shown in FIG. 24 (step S16). Then, the display control unit 54 of the user terminal 40 displays the initial screen 540 as shown in FIG. 24 on the display 506 (step S17).

The initial screen 540 includes a "schedule registration" button 541 that is pressed when registering a schedule, and a "execution event history browsing" button 543 that is pressed when viewing the execution event history.

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

Next, the storage / reading processing unit 89 of the schedule management server 12 searches the user management DB 8002 (see FIG. 12) using the organization ID received in step S13 as a search key, and thereby all the corresponding user IDs and Read out all user names (step S20). Then, the transmission / reception unit 81 transmits the 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.

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

Next, in the user terminal 40, the generation unit 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 displays the schedule input screen 550 as shown in FIG. 25 on the display 506 (step S23).

On the schedule input screen 550, an input field 551 for inputting an event name, an input field 552 for inputting a union ID or a union name to be used, and an input for inputting a scheduled start date and time of event execution. Field 553, input field 554 for inputting the scheduled end date and time of event execution, input field 555 for inputting memos such as agenda, display area 556 for displaying the name of the reserved person, other than the reserved person Selection menu 557 for selecting a participant's participant name, "OK" button 558 pressed when registering a reservation, "CANCEL" button 559 pressed when entering or canceling entered content It is included. It is not essential to enter the union ID or union name in the input field 552, and it will be blank when the union is not used.

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

Next, after the user A inputs a predetermined item in the input fields 551 to 555 and selects the name (user name) of the user who wants to participate in the event from the selection menu 557 using the pointer p1. Press the "OK" button 558. As a result, the reception unit 52 receives the input of the schedule information (step S24). Then, the transmission / reception unit 51 transmits the schedule information to the schedule management server 12 (step S25).

This schedule information includes an event name, a union ID (or union name), a scheduled start date and time, a scheduled end date and time, a user ID of each participant, and a memo. When the union ID is input in the input field 552 on the schedule input screen 550, the union ID is transmitted. If a union name is entered in the input field 552, the union name is transmitted. Further, on the schedule input screen 550, the user name is selected in the selection menu 557, but since the user ID is also received in step S21, the user ID corresponding to the user name is transmitted. As a result, 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 responds by searching the union management DB 8003 (see FIG. 13) using the received union ID as a search key. Read the union name (or union ID) to be used (step S26).

Next, the storage / reading 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. 14) (step S27). The storage / reading processing unit 89 adds reservation information for one record to the union reservation management table of the union reservation management DB 8004 managed by the scheduler registered in advance. The reservation information is configured based on the schedule information received in step S25 and the union name (or union ID) read in step S26. The scheduled start date and time in the union reservation management DB 8004 corresponds to the scheduled start date and time in the schedule information. Further, 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.

Further, the storage / reading processing unit 89 stores the schedule information in the event management DB 8005 (see FIG. 15) (step S28). The storage / reading processing unit 89 adds schedule information for one record to the event management table of the event management DB 8005 managed by the scheduler registered in advance.

The schedule information is configured 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. Further, the scheduled event end date and time 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 processing >>
Here, a process of having a conference with other participants using the user terminal 40 in the conference room X reserved by the reservation person A (Rikotaro) will be described. 26 and 27 are sequence diagrams showing the event start processing. FIG. 28 is a diagram showing a reservation list screen of the union. FIG. 29 is a diagram showing a project list screen. FIG. 30 is a diagram showing a detailed information screen of the event.

First, when the user A presses the power switch of the user terminal 40, the reception unit 52 of the user terminal 40 receives the 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, the user A inputs his / her own e-mail address and password on the sign-in screen, and the reception unit 52 accepts the sign-in request (step S33). The transmission / reception unit 51 transmits the sign-in request information indicating the 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) received in step S33. As a result, the transmission / reception unit 61 of the sharing support server 11 receives the sign-in request information.

Next, the authentication unit 62 of the shared support server 11 authenticates the user A by using the user ID, the organization ID, and the password of the user A received in step S34 (step S35). Specifically, the storage / reading processing unit 69 uses the user ID, organization ID, and password of the user A received in step S34 as search keys in the user authentication management DB 6001 (see FIG. 5) in step. The set of the user ID, the organization ID, and the password corresponding to the set of the user ID, the organization ID, and the password of the user A received in S34 is searched.

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 unjust (illegal) user. If it is not valid, the transmission / reception unit 61 notifies the user terminal 40 that it is not valid. Here, the case where it is valid will be continued.

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

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

Specifically, the storage / reading processing unit 89 searches the server authentication management DB 8006 (see FIG. 16) for the 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 requesting shared support server 11 is a legitimate accessor. If there is no corresponding pair, the authentication unit 82 determines that the requesting shared support server 11 is an unjust (illegal) accessor. If it is not valid, the transmission / reception unit 81 notifies the shared support server 11 that it is not valid. Here, the case where it is valid will be continued.

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

Further, the storage / reading processing unit 89 responds by searching the event management DB 8005 (see FIG. 15) managed by the scheduler using the user ID of the user A received in step S37 as a search key. Read the schedule information (step S40).

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

Next, the storage / reading processing unit 89 searches the project member management DB 8007 (see FIG. 17) using the user ID of the user A received in step S37 as a search key, and thereby the user of the user A. Read out the project IDs and project names of all the projects including the IDs (step S41).

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

Next, the creation unit 63 of the sharing support server 11 creates a reservation list based on the reservation information and the schedule information received in step S42 (step S43). Then, the transmission / reception unit 61 transmits the reservation list information indicating the contents 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 unit 54 displays the reservation list screen 230 as shown in FIG. 28 on the display 506 (step S45). The reservation list screen 230 includes a display area 231 for displaying a union name (here, a place name) and a display area 232 for displaying today's date and time. Further, the reservation list screen 230 displays event information 235 to 237 and the like indicating an event using today's union (here, conference room X). Each event information includes the scheduled start / end time of the union, the event name, and the name of the person who made the reservation for the union (reservation person name) for each event. The event information includes start buttons 235s to 237s and the like that are pressed when the user identifies an event to be started.

Next, in FIG. 27, when the user A presses the start button 235s on the pointing device 512 or the like, the reception unit 52 accepts 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. 29 on the display 506 based on the project ID and the project name received in step S44 (step S52).

The project list screen 240 includes project icons 241 to 246 indicating each project. Further, the project list screen 240 includes an "OK" button 248 pressed when confirming the selected project icon, and a "CANCEL" button 249 pressed when canceling the selection of the project icon.

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

Next, the transmission / reception 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 shared support server 11. (Step S54). The process of step S54 is the process of requesting the transmission of the execution event identification information. As a result, the transmission / reception unit 61 of the shared support server 11 receives the selected scheduled event ID and the selected project ID.

Next, in the shared support server 11, the generation unit 64 generates a unique execution event ID (step S55). Then, the storage / reading processing unit 69 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 in association with each other (step). S56).

The user ID and organization ID of the reservation person, and the event information are IDs and information based on the reservation information and the schedule information received in step S42. At this point, there is no entry in the participation / non-participation column in the reservation management table (see FIG. 7).

Next, the storage / reading 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 transmission / reception unit 61 transmits the file data transmission request information indicating the transmission request of the file data registered in the schedule management server 12 to 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 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 / reading processing unit 89 of the schedule management server 12 searches the event management DB 8005 (see FIG. 15) using the scheduled event ID received in step S58 as a search key, and thus a file associated with the scheduled event ID. Read the data (step S59). Then, the transmission / reception unit 81 transmits the file data read in step S59 to the sharing support server 11 (step S60). As a result, the transmission / reception unit 61 of the sharing support server 11 receives the file data.

Next, the storage / reading processing unit 69 of the shared support server 11 schedules 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 the user A (step S62). As a result, the transmission / reception unit 51 of the user terminal 40 of the user A receives the execution event ID and the file data. The transmission / reception unit 61 transmits a participation request notification to the event to the user terminals 40 of other participants. The participation request notification for this event includes various information for participating in the event started by the user A. As a result, other participants use the event participation request notification to notify the shared support server 11 of participation in the event from their own user terminal 40, such as an online conference started by user A. You can participate in the event.

Next, in the user terminal 40, the storage / reading 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 shared support server 11 is stored in a specific storage area of the storage unit 5000. As a result, the user terminal 40 accesses the specific storage area during the execution of the event, so that the display control unit 54 displays the file data stored in the specific storage area on the display 506.

Here, the specific storage area is a temporary storage destination of 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 the configuration provided inside the user terminal 40, but is provided in an external storage device connected to the user terminal 40, or a local server existing in the on-premises environment and capable of communicating with the user terminal 40. It may be.

Next, the display control unit 54 displays the detailed information screen 250 of the selected event on the display 506 as shown in FIG. 30 (step S64). The detailed information screen 250 of this event includes a display area 251 for the event name, a display area 252 for the scheduled event implementation time (scheduled start time and scheduled end time), and a display area 253 for the reserved person name. 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 a file stored in a specific storage area of the storage unit 5000 are displayed. A display area 258 for displaying identification information (for example, a file name) for identifying data is displayed.

In the display area 257, the name of the reserved person shown by FIG. 25 and the names of other selected participants are displayed. Further, in the display area 258, the file data stored in the specific storage area of the storage unit 6000, that is, the file name of the file data downloaded from the shared support server 11, is displayed, and the file data is downloaded from the shared support server 11. The file name of the file data inside is also displayed. Further, the lower right side of the event detailed information screen 250 includes a "close" button 259 that is pressed when the detailed information screen 250 is closed.

Next, the other participants who have received the participation request notification notify the shared support server 11 of participation in the event from their user terminal 40, and participate in an event such as an 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 an event such as an online conference started by the user A. Next, the shared support server 11 stores and manages the presence / absence of participation in the participation presence / absence column that has not been entered in the schedule management DB 6003 (step S67).

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

≪Registration and display processing of execution event history≫
Subsequently, the registration and display processing of the execution event history will be described. FIG. 31 is a sequence diagram showing the registration process of the execution event history. Further, FIG. 32 is a flowchart showing the voice-to-text conversion process.

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

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

Next, the transmission / reception unit 51 transmits the registration request information indicating the registration request of the generated content to the sharing support server 11 (step S72). In this case, the transmission / reception unit 51 automatically transmits the registration request information each time the content is generated. The 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 sender, content data, and content processing type information. As a result, the transmission / reception unit 61 of the sharing support server 11 receives the registration request information.

Next, the determination unit 65 of the sharing support server 11 determines the type of content processing received 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 sharing support server 11 transmits the recorded data, which is the content data, to the voice-to-speech conversion server 13 ( 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 the recorded data, which is the content data, to the voice-to-speech conversion server 13 ( Step S74).

As a result, the transmission / reception unit 91 of the voice-to-text conversion server 13 receives the recorded data or the recorded data. When the type of content processing is other than "recording function / recording function", the sharing support server 11 shifts to the processing of step S77 without performing the processing of steps S74 to S76.

Next, the conversion unit 93 of the voice-text conversion server 13 converts the recorded data or recorded data received by the transmission / reception unit 91 into text data with time stamp information (recorded data or elapsed time from the beginning of the recorded data). (Step S75). The processing in step S75 may be real-time processing or batch processing. Here, the voice-text conversion process in the voice-text conversion server 13 will be described with reference to FIG. 32.

First, the conversion unit 93 acquires the recorded data or information indicating the date and time when 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 shared support server 11 received the recorded data or the recorded data or the date and time when the shared support server 11 transmitted the recorded data or the recorded data. .. In this case, the transmission / reception unit 91 of the voice-to-text conversion server 13 receives the recording data or the recording data transmitted from the sharing support server 11 and the information indicating the date and time in step S74.

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

When it is determined that the text conversion process is completed, the conversion unit 93 generates the recorded data or the voice text data with the time stamp information converted from the recorded data (step S75-4). As a result, the voice-text conversion server 13 can convert the recorded data or the recorded data transmitted from the sharing support server 11 into voice-text data with type stamp information.

The information processing system 1 repeatedly executes the text conversion process of the recorded data or the recorded data generated in the user terminal 40 by repeating the processes shown above (steps S71 to S76).

When the transmission / reception unit 91 of the voice / text conversion server 13 completes the text conversion of the recorded data or the recorded data by the conversion unit 93, the transmission / reception unit 91 transmits the voice text data with the time stamp information to the sharing support server 11 (step S76). As a result, the transmission / reception unit 61 of the sharing support server 11 receives the voice text data with the time stamp information transmitted from the voice text conversion server 13.

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

Next, the detection unit 66 detects the remark text data of the action item candidate with the reproduction position information from the voice text data with the time stamp information received in step S76 as follows (step S80). FIG. 33 is a flowchart showing a process of detecting an action item candidate.

First, the detection unit 66 divides the voice text data received in step S76 into speech text data sentence by sentence. Note that, based on the time stamp information of the first character or word included in the statement text data of one sentence, the reproduction position information is added to the statement text data. (Step S80-1).

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

For example, the element [who] may extract a noun representing [personal name]. Also, for example, the element [by when] is considered in the composition of A part + B part,
Part A: [Date], [Day of the week], [Number + x days later], [Words representing the date and time (tomorrow, the day after tomorrow, etc.)] and phrases that indicate the position on the calendar B part: [By (ha)], A phrase that expresses a deadline, such as [by delivery date],
Should be extracted. In addition, the element [what] is considered in the composition of A part + B part,
Part A: [Noun] + (particles, particles)
Part B: You can extract phrases that represent requests such as [verb] + [do it], [request], and [finish it]. Here, it is permissible that the order of the A part and the B part is reversed (inverted) and spoken.

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

For example, an action item is generally composed of three elements, "who", "what", and "by when", but the above three elements are included in the statement text data of a sentence intended as an action item. It may not be available. Therefore, for example, when there is an element of the following combination in the statement text data of one sentence, the detection unit 66 detects it as an action item candidate.

(Example of combination element)
Element [Who] + [What] ... <Example: Mr. Tanaka, please call company Z. ＞
Element [By when] + [What] ... <Example: Call Company Z by Friday. ＞
Element [Who] + [By when] + [What] ... <Example: Mr. Tanaka, please call Company Z by Friday. ＞
In the above combination element example, the element [what] is indispensable for being established as an action item. When there is an element of the above combination in the one-sentence utterance text data (YES in step S80-4), the detection unit 66 detects the one-sentence utterance text data read in step S80-2 as an action item candidate (YES in step S80-4). Step S80-5).

When there is no element of the above combination in the statement text data of one sentence (NO in step S80-4), the detection unit 66 skips the process of step S80-5 and the statement of one sentence read 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 all the reading of the speech text data divided into sentences in step S80-1 is completed.

According to the process of detecting the action item candidate shown in FIG. 33, the detection unit 66 can detect the remark text data of the action item candidate with the reproduction position information from the voice text data. In detecting action item candidates, a predictive search technique may be used. As an example, when "Mr. Tanaka", which is an element [who] of the comment text data, appears, the comment text data following "Mr. Tanaka" is predicted as an action item candidate and responded. The "elements of a predetermined combination that are likely to be action items" used for detecting the action item candidates shown in steps S80-4 to S80-5 of FIG. 33 may be updated by machine learning.

For example, an action item candidate that detects the above "elements of a predetermined combination that tends 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, a sentence of remark text data that could not detect the above-mentioned "elements of a predetermined combination that tends to be an action item" as a basic rule may be registered as an action item by a member of the project.

In such a case, the action item candidate that was not registered as an action item by the project member and the sentence of the statement text data registered as the action item by the project member are subjected to machine learning from the statement text data. The detection accuracy of action item candidates can be improved.

Here, machine learning is a technique for making a computer acquire learning ability like a human being, and the computer autonomously generates an algorithm necessary for judgment such as data identification from learning data taken in advance. , Refers to a technology that applies this to predict new data.

The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-teacher learning, intensive learning, or deep learning, and may be a learning method that combines these learning methods, and is a machine. The learning method for learning does not matter.

Next, returning to FIG. 31, the transmission / reception unit 61 of the sharing support server 11 transmits data according to the content processing generated in step S71 to the user terminal 40 which is a member of the project (step S81). For example, when the recorded data or the recorded data is generated as the content in step S71, the transmission / reception unit 61 transmits the recorded data or the recorded data, as well as the remark text data with the reproduction position information detected as the action item candidate.

Further, when the input text data input for chat or message in step S71 is generated as content, the transmission / reception unit 61 may transmit the comment text data detected as an action item candidate in addition to the input text data. ..

As a result, the user terminal 40 of the project member shares the content of the project member's utterance or text input at an event such as an online conference, as well as the statement text data of the action item candidate detected from the content, as a sharing support server. Can be received from 11.

The display control unit 54 of the user terminal 40 of the project member is the content that the project member said by utterance or text input in an event such as an online conference transmitted from the sharing 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. 34, for example.

FIG. 34 is a diagram showing a part of the execution event history screen. On the execution event history screen 260 of FIG. 34, the content (meeting memo) spoken by the project members in text or voice at an event such as an online meeting using the communication function is displayed in full screen. The display button 262 and the statement text data 264 detected as action item candidates from the contents of the meeting memo are included.

The conference memo is, for example, an utterance record in which the content spoken by a member of the project is converted into recorded data or recorded data into text data by using existing voice recognition technology. The meeting memo is an utterance record of what the project members said by text input.

In the execution event history screen 260 of FIG. 34, an example in which the remark text data 264 of the action item candidate received from the shared support server 11 is a sentence of "Mr. Yamashita corrects and submits document 1 by tomorrow". Although shown, there may be more than one. If the remark text data 264 of the action item candidate is recorded data or text data converted from the recorded data, for example, a playback link 265 is displayed next to it. The playback link 265 is a link that starts playback from the recorded data or the position (time offset) of the recorded data or the recorded data detected by the voice recognition of the action item candidate speech text data 264 based on the playback position information of the speech text data 264. be. As described above, the reproduction link 265 incorporates seek information for starting reproduction from the recorded data or the position of the recorded data detected by the speech text data 264 of the action item candidate by voice recognition. The seek information is information indicating the playback position (playback location) of the recorded data or the recorded data during the total playback time.

Note that the playback link 265 may not be able to understand the context when the remark text data 264 of the action item candidate starts playback from the recorded data or the position of the recorded data detected by voice recognition. Therefore, for example, from the location indicated by the playback position information. For example, the reproduction may be started about 30 seconds before. Further, the reproduction link 265 may include the remark time (9:57 as an example) of the action item candidate. Further, the playback link 265 may display the speaking time (9:57 as an example) as shown in FIG.

When the reproduction link 265 is clicked, the reproduction unit 57 of the user terminal 40 reproduces the recorded data or the recorded data associated with the reproduction link 265 from the position based on the reproduction position information. For example, the reproduction unit 57 may newly open a recorded data associated with the reproduction link 265 or a Web page in which the recorded data is stored. On the newly opened Web page, the user can reproduce the recorded data or the recorded data in which the speech text data 264 is detected by voice recognition from the position based on the reproduction position information. Further, when the playback unit 57 has a video control 276 as shown in FIG. 46 in the same conference memo thread, the video control 276 records the speech text data 264 detected by voice recognition from the position based on the playback position information. Play back the data or recorded data. By moving the seek bar in the video control 276 to the left or right, it is possible to freely play back from the start of recording / recording to the end of recording / recording. Further, in the moving image control 276, it is possible to raise or lower the volume of the reproduced data and to fast-forward / rewind the reproduced data. The recorded data or the recorded data associated with the reproduction link 265 is acquired from the storage destination shown in the item "content content" of the content management table of FIG. The speech time displayed on the reproduction link 265 in FIG. 46 may be always displayed together with the reproduction link. Further, the user may accept the selection of the playback link 265 and display the playback link 265 in accordance with the display of the moving image control 276. By displaying the current time at the same timing (step) as the display of the video control 276, even after the user moves the seek bar in the video control 276 to the left or right, the action item candidate linked to the playback link 265 is said. The time can be easily grasped, and the user can easily and quickly return to the playback position information using the seek bar.

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

FIG. 35 is a diagram showing a part of the execution event history screen. On the execution event history screen 260 of FIG. 35, the remark text data 264 of the action item candidate received from the shared support server 11 is "Mr. Yamashita will correct and submit Document 1 by tomorrow" and "Mr. Riko within this month." Shows an example of three sentences, "to create document 2" and "to TEL to company A".

In the execution event history screen 260 of FIG. 35, the remark text data 264 of the action item candidates of "Mr. Yamashita corrects and submits document 1 by tomorrow" and "TEL to company A" is recorded data or recording. Since it is text data converted from the data, for example, the playback link 265 is displayed next to it.

On the other hand, on the execution event history screen 260 of FIG. 35, the remark text data 264 of the action item candidate of "Mr. Riko creates document 2 within this month" is not the recorded data or the text data converted from the recorded data. For example, the playback link 265 is not displayed next to it. For example, if the remark text data 264 is created based on the content input by the participants as a memo during the meeting, the playback link 265 is not displayed. When the remark text data 264 is created based on the text data in the material used in the meeting, a link to the storage destination in which the material is stored may be displayed.

For example, a project member (hereinafter referred to as a registered member) who wants to register the statement text data 264 of the action item candidate on the execution event history screen 260 of FIG. 34 as an action item in the action item management server 14 is his / her own user as follows. Operate the terminal 40.

Note that the comment text data 264 of the action item candidate on the execution event history screen 260 is not registered in the action item management function of the action item management server 14, for example, unless the operation of registering it as an action item is performed. Since the utterance text data 264 is displayed as an utterance record, it may be buried in other utterances and the operation of registering it as an action item may be forgotten. Therefore, the statement text data 264 of the action item candidate that has not been registered as an action item may be posted again as a new statement. The reposting of the remark text data 264 is performed, for example, by a bot (bot: application software that executes an automated task). As for the posted action item candidate remark text data 264, if the recorded data or the text data converted from the recorded data is the same as in FIG. 34, the playback link 265 is displayed next to it.

First, the registered member sets the action button groups 266 and 268 as shown in FIGS. 36 and 37 by, for example, hovering (mouse over) the pointer of the pointing device 512 on the position of the statement text data 264 of the action item candidate. It is displayed on the execution event history screen 260. 36 and 37 are views showing a part of the execution event history screen.

In the examples of FIGS. 36 and 37, the action button group 268 of FIG. 37 is displayed by hovering the mouse over the three-point button “...” of the action button group 266 of FIG. The action button groups 266 and 268 of FIGS. 36 and 37 are examples, and may be one or three or more action button groups.

By selecting the "set executor" button 270 of the action button group 268 of FIG. 37, the registered member causes the executor input field 272 to be displayed on the execution event history screen 260 as shown in FIG. 38. FIG. 38 is a diagram showing a part of the execution event history screen. In the executor input field 272, candidates for the executor of the action item are displayed so as to be selectable.

In addition, the members of the project (members who participated and members who were absent) convened in the online meeting are preferentially displayed as candidates for executing the action item. The candidates for the performers of the action items may be narrowed down and displayed not only for the members of the project but also for the candidates for the performers of the action items according to the viewing authority classification (team, channel, etc.) on this collaboration system. For example, as a candidate for executing an action item, a reservation person such as a conference organizer (an example of a group organizer) and a member having a higher authority among project members (an example of an example of a higher authority user who joined a group) are described above. It is possible to narrow down by referring to various tables. The performer of the action item is not limited to one person, and may be assigned to a plurality of people.

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

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

In addition, although the example in which the registered member sets the executor and inputs the deadline date has been described above, the action item candidate example shown in FIG. 34 and the like "Mr. Yamashita corrects and submits document 1 by tomorrow. When the three elements of "who", "what", and "by when" are prepared like "thing", the action item management of the action item management server 14 is automatically performed without the above manual operation. You may register it in the function.

For example, the request unit 55 of the user terminal 40 may determine "who" from the statement regarding "who" included in the statement text data 264 of the action item candidate. Further, the requesting unit 55 can determine "who", and can identify the only user on the information processing system 1 in the case where the statement text data 264 of the action item candidate includes one "person's name". Only in the following cases, the "who" judgment may be made automatically. The following cases consider judgment priorities. If the performer of the action item cannot be set automatically in the following cases, the registered member may set it manually.

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

Priority 2: "Who" is <Tanaka>, and some users who are absent from the online conference have "Tanaka" as part of their first and last names.

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

Further, for example, the requesting unit 55 of the user terminal 40 may determine "until" from the statement regarding "until" included in the statement text data 264 of the action item candidate. In addition, the requesting unit 55 of the user terminal 40 may make a judgment of "until" from the schedule of the next meeting that can be judged from the meeting attributes. For example, in the "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 requesting unit 55 of the user terminal 40 can specify the dates of "tomorrow" and "the day after tomorrow" on the calendar. It is not necessary to target the wording that corresponds to the "past" from the wording that expresses time or meeting.

The registered members who request the registration of action items are limited to, for example, the speakers of the action item candidate's remark text data 264, the reservation person such as the conference organizer, and the members with higher authority among the project members. You may.

The registration unit 104 of the action item management server 14 that has received the action item registration request manages the action items in the action item management table as shown in FIG. Further, 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.

Further, 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 content 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 the task management screen 271 as shown in FIG. 40, for example. FIG. 40 is a diagram showing a part of the task management screen. On the task management screen 271 of FIG. 40, the action item 273 of "Mr. Yamashita corrects and submits the document 1 by tomorrow" registered from the execution event history screen 260 is displayed. The action item 273 includes a reproduction link 275 having the same effect as the reproduction link 265 as shown in FIG. 34 and the like. When the reproduction link 275 is clicked, the reproduction unit 57 of the user terminal 40 reproduces the recorded data or the recorded data associated with the reproduction link 275 from the position based on the reproduction position information.

As described above, in the information processing system 1 according to the present embodiment, it is easy to reproduce the recorded data or the recorded data of the scene where the action item candidate's remark text data 264 or the action item 273 is born. Therefore, in the information processing system 1 according to the present embodiment, the action item 273 can be registered or executed after confirming the scene where the action item candidate's remark text data 264 or the action item 273 is born.

≪Browsing process of execution event history≫
Next, the browsing process of the execution event history will be described. 41 and 42 are sequence diagrams showing the browsing process of the execution event history. Since the processing of steps S111 to S117 of FIG. 41 is the same as the processing of steps S11 to S17 of FIG. 22, the description thereof will be omitted.

When the user presses the "execution event history viewing" button 543 on the initial screen 540 shown in FIG. 24, the reception unit 52 accepts the viewing of the execution event history (step S118).

Then, the transmission / reception unit 51 transmits the execution event history browsing request information indicating the execution event history browsing request to the schedule management server 12 (step S119). As a result, the transmission / reception unit 81 of the schedule management server 12 receives the execution event history viewing request information. Next, the storage / reading processing unit 89 of the schedule management server 12 searches the project member management DB 8007 using the user ID and the organization ID received in step S113 as the search key, and obtains the corresponding project ID and project name. Read (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 the 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 of FIG. 29.

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

Next, the transmission / reception unit 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). As a result, the schedule management server 12 receives the project ID.

Next, in the schedule management server 12, the storage / reading 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 / reading processing unit 89 reads out all the execution event IDs associated with the project ID received in step S125. Then, the storage / reading processing unit 89 reads the corresponding execution event start / end information by searching the execution event management DB 8009 using the execution event ID read in step S126 as a search key (step S127). The execution event start / end information includes the execution event ID, the event name, the start date / time, and the end date / time.

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

Next, the generation unit 56 of the user terminal 40 uses the data received in step S128 to generate the execution event list screen 570 as shown in FIG. 43 (step S129). FIG. 43 is a diagram showing an execution event list screen. Then, in the user terminal 40, the display control unit 54 displays the execution event list screen 570 generated by the generation unit 56 on the display 506 (step S130). As shown in FIG. 43, the execution event list screen 570 includes information 571 to 573 indicating the execution event.

For example, the information 571 to 573 indicating the execution event includes the execution event name, the start date and time of the event, and the end date and time. The information 571 to 573 indicating the execution event is an example of the history information selection area that accepts the selection for displaying the history information indicating the execution content of the event. Further, the lower right portion of the execution event list screen 570 includes a "close" button 575 that is pressed when the execution event list screen 570 is closed.

Further, the lower left portion of the execution event list screen 570 includes an "action item" button 577 that is pressed when the action item is browsed. The “action item” button 577 is an example of an action item selection area that accepts selections for displaying an action item.

Next, the reception unit 52 of the user terminal 40 accepts the selection of the execution event included in the execution event list screen 570 (step S131). Specifically, when the user selects the information indicating the execution event included in the execution event list screen 570, the reception unit 52 accepts the selection of the information indicating the 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). As a result, the transmission / reception unit 81 of the schedule management server 12 receives the execution event ID.

Next, the storage / reading 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 out the corresponding execution event history information (step S133). .. The execution event history information includes the content processing ID, the type of content processing, the start date and time of the content processing, and the end date and time.

Further, the storage / reading 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 a content generation time zone, a content processing ID, a content processing type, and a sequence number. The time zone in which the content included in the related information occurs is an example of the time information.

Then, the storage / reading processing unit 89 reads out the content data indicating the content of the execution event history from the storage destination of the content data indicating the content of the execution event history read in step S133 (step S135). Then, the transmission / reception unit 81 transmits the read related information and content data to the user terminal 40 (step S136). As a result, the transmission / reception unit 51 of the user terminal 40 receives the related information and the content data.

Next, the request unit 55 of the user terminal 40 makes an inquiry request for the state of the action item to the action item management server 14 (step S137). When an inquiry request for the state of an action item is received from the user terminal 40, the action unit 105 of the action item management server 14 reads the state of the action item corresponding to the inquiry request from the action item management table shown in FIG. 21 (step). S138).

Then, the request unit 55 of the user terminal 40 receives the state information of the action item from the action item management server 14 (step S140). The generation unit 56 of the user terminal 40 uses the related information and content data received in step S136 and the state information of the action item received in step S140 to generate the execution event history screen 260. The display control unit 54 of the user terminal 40 can display the execution event history screen 260 such as FIG. 34 or FIG. 35 generated by the generation unit 56 on the display 506 (step S142).

As shown in FIG. 44, the execution event history screen 260 includes an overall display button 267 for displaying an action item registered with any member of the project as the executor among the three statements of the action item candidate, and a user. A personal display button 269 for displaying an action item registered as an executor of a member operating the terminal 40 is included.

On the execution event history screen 260, the member who operates the user terminal 40 is the action item of the project assigned to any member of the project and the action item of the project assigned to himself / herself among the remark text data 264 of the action item candidate. Can be switched and displayed.

According to the information processing system 1 according to the present embodiment, when an action item candidate is detected from the contents of remarks between project members using the communication function provided by the collaboration tool and registered in the action item management function. , Can assist in confirming the scene where the action item candidate's remark was made.

[Other Embodiments]
The information processing system 1 of FIG. 4 is an example, and may have a configuration as shown in FIG. 45, for example. FIG. 45 is a functional configuration diagram of an example of the information processing system according to the present embodiment. In the information processing system 1 of FIG. 45, the request unit 55 of the user terminal 40 in FIG. 4 is replaced with the request unit 67 of the shared support server 11.

Therefore, various requests such as an action item registration request to the action item management server 14 and an action item status inquiry request made by the request unit 55 are made from the request unit 67 of the shared support server 11. Further, the image data of the screen such as the execution event history screen to be displayed on the display control unit 54 of the user terminal 40 is also created by the creation unit 63 of the sharing support server 11.

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

The present invention is not limited to the above-described embodiment disclosed specifically, and various modifications and modifications can be made without departing from the scope of claims. For example, a configuration in which the first embodiment and other embodiments are combined is also possible. It goes without saying that the information processing system 1 described in the present embodiment is an example, and there are various system configuration examples depending on the application and purpose.

Each function of the embodiment described above can be realized by one or more processing circuits. Here, the "processing circuit" in the present specification is a processor programmed to execute each function by software such as a processor implemented by an electronic circuit, or a processor designed to execute each function described above. It shall include devices such as ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array) and conventional circuit modules.

The group of devices described in the examples merely represents one of a plurality of computing environments for implementing the embodiments disclosed herein.

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

Further, the sharing support server 11, the schedule management server 12, the voice-text conversion server 13, the action item management server 14, and the user terminal 40 can be configured to share the above-disclosed processing steps in various combinations. For example, a process executed by a given unit can be executed by another unit. Similarly, the function of a given unit can be performed by another unit. Further, each element of the shared support server 11, the schedule management server 12, the voice 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 Shared support server 12 Schedule management server 13 Voice-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 57 Playback unit 61 Transmission / reception unit 63 Creation unit 65 Judgment unit 66 Detection unit 67 Request unit 260 Execution event history screen 265 Playback link

International Publication No. 2011/099086

Claims (12)

An information processing system including a plurality of user terminals and a collaborative work support system that supports collaborative work by a plurality of users who operate the user terminals.
The collaborative work support system
A transmission means for transmitting an action item candidate based on the recorded data or audio text data converted from the recorded data, and the recorded data of the action item candidate or the reproduction information in the recorded data to the user terminal.
Have,
The user terminal is
A receiving means for receiving the action item candidate and the reproduction information from the collaborative work support system, and
A display control means for displaying the received action item candidate and the reproduction information on the display unit, and
Information processing system with. The display control means is characterized in that, based on the reproduction information, the recorded data or a link incorporating the information for starting the recorded data is displayed on the display unit in association with the action item candidate. The information processing system described in 1. The display control means is characterized in that a link incorporating the recorded data or information incorporating information a predetermined time before the start of the recorded data is displayed on the display unit in association with the action item candidate. Item 2. The information processing system according to item 2. The user terminal further
An action item from the action item candidate, an executor who executes the action item, and a reception means for accepting a registration operation of the deadline of the action item.
A request means for making a registration request for the action item that has received the registration operation, an executor that executes the action item, and a deadline for the action item to the action item management means that manages the action item.
The information processing system according to any one of claims 1 to 3. Based on the reproduction information, the display control means associates the recorded data or a link incorporating the information for starting the recorded data with the action item for which the registration request has been made to the action item management means. The information processing system according to claim 4, wherein the information processing system is displayed on the display unit. The fourth or fifth aspect of the present invention, wherein the display control means displays a list of the action items for which the registration request has been made to the action item management means for all or individually of the plurality of users. Information processing system. The collaborative work support system further
The action item candidate and the recorded data of the action item candidate or the reproduction information in the recorded data are detected from the voice text data, the action item candidate is subjected to morphological analysis processing, and the content of the action item and the action are described. A detection means for detecting the action item in a sentence containing at least two combinations of elements that may represent the deadline of the action item, or the performer who executes the item, as the action item candidate.
The information processing system according to any one of claims 4 to 6. An information processing device capable of communicating with a plurality of user terminals and supporting joint work by a plurality of users who operate the user terminals.
Creation of creating screen image data for displaying action item candidates based on recorded data or audio text data converted from recorded data, and the recorded data of the action item candidates or playback information in the recorded data on the display unit. Means and
A transmission means for transmitting the image data to the user terminal, and
Information processing device with. A user terminal that can communicate with a collaborative work support system that supports collaborative work by multiple users.
A receiving means for receiving an action item candidate based on the recorded data or audio text data converted from the recorded data, and the recorded data of the action item candidate or the reproduction information in the recorded data from the collaborative work support system.
A display control means for displaying the received action item candidate and the reproduction information on the display unit, and
User terminal with. An information processing method executed by a user terminal capable of communicating with a collaborative work support system that supports collaborative work by multiple users.
A reception step of receiving an action item candidate based on the recorded data or audio text data converted from the recorded data, and the recorded data of the action item candidate or the reproduction information in the recorded data from the collaborative work support system.
A display control step for displaying the received action item candidate and the reproduction information on the display unit, and
Information processing method to execute. An information processing device that can communicate with a plurality of user terminals and supports joint work by a plurality of users who operate the user terminals.
Creation of creating screen image data for displaying action item candidates based on recorded data or audio text data converted from recorded data, and the recorded data of the action item candidates or playback information in the recorded data on the display unit. means,
A transmission means for transmitting the image data to the user terminal,
A program to function as. A user terminal that can communicate with a collaborative work support system that supports collaborative work by multiple users.
A receiving means for receiving an action item candidate based on the recorded data or audio text data converted from the recorded data, and the recorded data of the action item candidate or the reproduction information in the recorded data from the collaborative work support system.
A display control means for displaying the received action item candidate and the reproduction information on the display unit,
A program to function as.

Images