Information processing device, method, program

Abstract

There is a need for technology that makes it easier to prepare contracts to be concluded based on the content of meetings. [Solution] A program is provided for operating a computer equipped with one or more computer processors. The program causes one or more computer processors to perform the following steps: acquire meeting minutes data; analyze the meeting minutes data to identify the contract terms relating to the meeting; and output contract data based on the identified contract terms.

Description

Technical Field

[0004] , , , , , , ,

[0006] , , , ,

[0005] , , , , , , ,

[0001] The present disclosure relates to an information processing apparatus, method, and program.

Background Art

[0002] Meetings are held between parties, and after reaching an agreement on contract terms and the like, the process proceeds to conclude the contract.

[0003] In Patent Document 1, as a problem, while pointing out "appropriately supporting the progress of a meeting and reducing the labor of creating minutes", as technical means for solving the problem, "analyzing a minutes template representing a prototype of the input minutes to create a meeting map in graph format with at least the meeting name and topics of the meeting as nodes", "acquiring the speech recognition result in the meeting", "judging the distance between words in the meeting based on the speech recognition result, updating the meeting map according to the words and the distance between words in the meeting, and displaying it on an image output unit, and when the discussion diverges due to the large distance between words, displaying a notice prompting the convergence of the discussion on the image output unit", and "creating minutes according to the minutes template based on the meeting map and the speech recognition result" are described for a "support device".

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, after a meeting, preparing a contract document to be concluded based on the content of the meeting is burdensome.

[0006] Therefore, there is a need for technology that makes it easier to prepare contracts to be concluded based on the content of meetings. [Means for solving the problem]

[0007] According to one embodiment, a program is provided for operating a computer having one or more computer processors. The program causes one or more computer processors to perform the steps of: acquiring meeting minutes data; identifying the contract terms of the agreement relating to the meeting by analyzing the meeting minutes data; and outputting contract data based on the identified contract terms. [Effects of the Invention]

[0008] This disclosure makes it even easier to prepare the contract to be concluded based on the content of the meeting. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows the configuration of System 1. [Figure 2] Figure 2 shows the configuration of server 20. [Figure 3] Figure 3 shows the configuration of terminal 10. [Figure 4] Figure 4 shows the data structure of the user database 211. [Figure 5] Figure 5 shows the data structure of the template database 212. [Figure 6] Figure 6 shows the data structure of the approval request database 213. [Figure 7] Figure 7 shows the data structure of the review history database 214. [Figure 8] Figure 8 shows the data structure of the contract signing database 215. [Figure 9] Figure 9 shows the data structure of the document management database 216. [Figure 10] Figure 10 shows the data structure of the meeting minutes management database 217. [Figure 11] Figure 11 shows the process flow for generating a contract based on meeting minutes data and sending a request to conclude the contract. [Figure 12] Figure 12 shows an example of an operation screen where the user can review the meeting minutes data and the generated contract data, and then proceed with the steps required to conclude the contract. [Modes for carrying out the invention]

[0010] The embodiments of this disclosure will be described below with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference numerals, and repeated explanations are omitted. The following embodiments are not intended to unduly limit the content of this disclosure as described in the claims. Not all components shown in the embodiments are necessarily essential components of this disclosure. Also, each drawing is a schematic diagram and is not necessarily a strict illustration.

[0011] Furthermore, in the following description, "processor" refers to one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be another type of processor such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core.

[0012] Furthermore, at least one processor may be a broad-sense processor, such as a hardware circuit that performs some or all of the processing (e.g., an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)).

[0013] In the following description, the expression "xxx table" may be used to describe information from which an output can be obtained for an input. This information may be data of any structure or a learning model such as a neural network that generates an output for an input. Therefore, "xxx table" can be referred to as "xxx information".

[0014] In the following description, the configuration of each table is an example. One table may be divided into two or more tables, or all or part of two or more tables may be combined into one table.

[0015] In the following description, the "program" may be used as the subject to describe a process. Since the program is executed by a processor to perform a defined process while appropriately using a storage unit and / or an interface unit, etc., the subject of the process may be the processor (or a device such as a controller having the processor).

[0016] The program may be installed in a device such as a computer or may be in, for example, a program distribution server or a computer-readable (e.g., non-transitory) recording medium. In the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0017] In the following description, an identification number is used as identification information for various objects, but identification information of other types (e.g., an identifier including letters and symbols) may be adopted.

[0018] In the following description, when describing elements of the same type without distinction, reference signs (or common signs among reference signs) are used, and when describing elements of the same type while distinguishing them, the identification numbers (or reference signs) of the elements may be used.

[0019] Furthermore, in the following explanation, only control lines and information lines deemed necessary for the explanation are shown, and not all control lines and information lines in the product are necessarily shown. All components may be interconnected.

[0020] <Outline of the Embodiment> The embodiments will be described below.

[0021] (1) Facilitating the creation of contracts based on the content of meetings. The process of documenting the discussions held by participants in meetings and then drafting a contract is burdensome. This can lead to delays in preparing the contract after the meeting, potentially delaying the entire contract signing process.

[0022] (2) Extraction of contract terms according to the content of the meeting Even if verbal agreements are made during a meeting, they may not be fully reflected in the contract, potentially leading to issues being pointed out during contract review, or the contract being signed without the contract terms being properly reflected.

[0023] Furthermore, there is a risk that verbal promises made during meetings will not be recorded, and therefore may not be fulfilled.

[0024] A technical configuration that addresses at least some of the above-mentioned problems will be described in the following embodiments.

[0025] For example, this describes a technique for creating a draft contract based on audio data of a meeting, including transcription and summarization, and determining the type of contract based on the audio data. More specifically, it describes proposing a contract template based on the meeting transcript, and generating the contract by applying the contract terms extracted from the meeting transcript to that template.

[0026] This allows for immediate acquisition of necessary contracts during meetings, enabling a swift transition to the agreement and signing of contracts.

[0027] <First Embodiment> <1.1 System Configuration Diagram> Figure 1 shows the configuration of System 1.

[0028] System 1, shown in Figure 1, includes a contract signing and document management service server 20, a user terminal 10, a business support system service server 92, a document review service server 93, an artificial intelligence (large-scale language model) service server 95, a document creation service server 96, and a sales support system service server 97. These devices are connected via a network 80.

[0029] In the illustrated example, terminal 10 is shown as the terminal used by users of the contract signing and document management service provided by server 20, but each user operates their own terminal.

[0030] Server 20 is a device that provides services for concluding contracts electronically and for managing document data concluded electronically. It should be noted that in System 1, the contract conclusion service provided by Server 20 and the document data management service may be provided by separate devices or different service providers. For example, Server 20 provides a document management service and, in addition to electronically signed contract data, may also optically scan paper contracts with seals to extract information such as the contract period and whether the contract is automatically renewed, and manage this information along with the scanned contract data. This allows for notifications to be sent to the user when the contract period expires.

[0031] Server 20 may also be a server that provides services to support tasks such as submitting approval requests to organizations (business companies, etc.) that conduct business activities. For example, Server 20 provides a service to users that enables them to design a workflow for obtaining budget approval with multiple users.

[0032] Terminal 10 is a device operated by the user.

[0033] The business support system service server 92 provides users with tools that can be used for the organization's business operations. The business support system service server 92 provides users with a system for submitting approval requests as part of the organization's business operations. The business support system service server 92 may also communicate with server 20 to provide server 20 with data accumulated by the approval request service.

[0034] The document review service server 93 accepts document data such as contracts and term sheets that define contract terms, and provides users with information on whether each clause is advantageous or disadvantageous to the company, whether there are any missing clauses, and the importance of the review items, thereby supporting the review of the document data. The document review service server 93 provides the above review support service using rule-based or pre-trained models. As a rule-based approach, for example, it may be possible to perform rule-based reviews of document data by associating specific wording or expressions with pre-defined information on whether the conditions are advantageous or disadvantageous, and explanations. Alternatively, for example, it may be possible to provide the above review service by generating a pre-trained model that responds with review results to document data input, using data from expert reviews of contracts, term sheets, etc., as training data. Furthermore, the document review service server 93 can also summarize the contents of contracts and generate review comments using a large-scale language model, and provide the results to the user. For example, the document review service server 93 may prompt the large-scale language model service server 95 with the document data to be reviewed (such as contract data) and information indicating the review criteria, and instruct the server 95 to perform the review according to the review criteria. By receiving the output of the large-scale language model service server 95, the server 93 may generate review comments for the document data. The document review service server 93 may also communicate with server 20 to provide the server 20 with data accumulated by the document review service.

[0035] Server 95 of the Large-Scale Language Model Service is a server that executes language processing tasks using language models built through learning processes including artificial intelligence (AI). An LLM (Large Language Model) is a model that has been pre-trained on large amounts of data (such as text data), for example, a large amount of web content on the internet, or a large amount of data stored in a designated database, and can perform various language processing tasks by being given a task.

[0036] The AI ​​service server 95 (sometimes referred to as the "large-scale language model service server 95") accepts prompt input in the form of text, images, audio, etc., and generates and responds with answers to those prompts. Examples of LLMs include GPT-3 and GPT-4 developed by OpenAI, and BERT developed by Google.

[0037] The document creation service server 96 provides a service for managing document data such as meeting minutes in organizations conducting business activities. Server 96 can issue URLs (Uniform Resource Locators) for accessing document data, and for example, if the user account of a user of the document creation service has access rights to the document data, the document data can be accessed via the URL. The document creation service server 96 may also be linked with a server that provides a schedule management service with calendar functionality, so that user accounts are common to both services. For example, having a user account may allow access to both the schedule management service and the document creation service. In this case, if document data from the document creation service is associated with a schedule, access rights to that document data may be set for users participating in the schedule.

[0038] The document creation service server 96 may communicate with server 20 to provide server 20 with data accumulated by the document creation service.

[0039] The sales support system service server 97 provides services to support sales activities. For example, the sales support system service server 97 provides the following to the user: • For each sales project, manage information such as the client, transaction details (amount, goods), transaction history (memos, meeting minutes, etc.), and responsible parties (our company, the other party, etc.). • Provide analysis results of sales performance for each sales team (e.g., trends in closing rates). The server 97 of the sales support system service may communicate with the server 20 to provide the server 20 with the data accumulated by the sales support system service.

[0040] In this embodiment, each device (terminal device, server, etc.) can also be considered as an information processing device. That is, the collection of each device can be considered as a single "information processing device," and System 1 may be formed as a collection of multiple devices. The way in which the multiple functions required to realize System 1 according to this embodiment are distributed to one or more hardware can be appropriately determined in view of the processing capacity of each hardware and / or the specifications required for System 1.

[0041] Terminal 10 can be implemented, for example, as follows: • Handheld mobile devices such as smartphones and tablets • Stationary PCs (Personal Computers), Laptop PCs • Wearable devices worn by the user (watch-type, glasses-type, etc.) Terminal 10 includes a communication interface (IF) 12, an input device 13, an output device 14, memory 15, storage 16, and a processor 19.

[0042] The communication interface 12 is an interface for inputting and outputting signals so that terminal 10 can communicate with an external device.

[0043] The input device 13 is a device for receiving input operations from the user (for example, a touch panel, touchpad, pointing device such as a mouse, keyboard, etc.).

[0044] The output device 14 is a device (such as a display or speaker) for presenting information to the user.

[0045] Memory 15 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0046] Storage 16 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0047] The processor 19 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

[0048] The server 20 includes a communication interface 22, an input / output interface 23, memory 25, storage 26, and a processor 29.

[0049] Communication IF22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0050] Input / Output IF23 functions as an interface between an input device for receiving user input operations and an output device for presenting information to the user.

[0051] Memory 25 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0052] Storage 26 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0053] The processor 29 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

[0054] <1.2 Functional Configuration of Server 20> Figure 2 shows the configuration of server 20. As shown in Figure 2, server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0055] The communications unit 201 performs processing to enable the server 20 to communicate with external devices.

[0056] The memory unit 202 stores various databases, such as the user database 211, template database 212, approval request database 213, review history database 214, contract signing management database 215, document management database 216, and meeting minutes management database 217.

[0057] User database 211 is a database for managing users.

[0058] User database 211 contains information necessary for using the services provided by server 20, such as the user's name and employee number. Further details will be provided later.

[0059] Template Database 212 is a database that manages templates for documents used in transactions between parties, such as contracts. Further details will be provided later.

[0060] The approval request database 213 is a database that manages applications for approval, such as those for concluding contracts. For example, server 20 communicates with server 92 of the business support system service to obtain information related to the approval request and update the approval request database 213. Further details will be described later.

[0061] Review History Database 214 is a database that manages the history of reviews performed on document data such as contracts. Further details will be provided later.

[0062] The contract signing management database 215 is a database that manages the contract signing process carried out by the electronic contract service provided by server 20. Further details will be described later.

[0063] The document management database 216 is a database for managing document data and includes information for managing document data concluded through the electronic contract service provided by server 20. Further details will be described later.

[0064] The meeting minutes management database 217 is a database that manages data on meeting minutes and data on contracts generated based on those minutes. Further details will be provided later.

[0065] The control unit 203 is realized when the processor 29 reads a program stored in the memory unit 202 and executes instructions contained in the program. By operating according to the program, the control unit 203 performs the functions shown as the reception control module 2041, transmission control module 2042, user management module 2043, contract signing processing module 2044, document management module 2045, approval processing module 2046, LLM utilization module 2047, review processing module 2048, template management module 2049, and contract creation processing module 2050.

[0066] The receive control module 2041 controls the process by which the server 20 receives signals from external devices according to a communication protocol.

[0067] The transmission control module 2042 controls the process by which the server 20 transmits signals to external devices according to a communication protocol.

[0068] The user management module 2043 is a module for managing information for each user using System 1. Specifically, the user management module 2043 accepts registration of each user's information and updates the user database 211.

[0069] The contract signing module 2044 controls the process of parties approving document data as part of the process of concluding a contract electronically. Specifically, the contract signing module 2044 notifies each user approving the document data and updates the contract signing management database 215 in response to the operation of approving the document data.

[0070] The document management module 2045 controls the process of managing document data by referring to the document management database 216. Specifically, based on the contract period information set in the document data, the document management module 2045 notifies the user of whether to renew the contract upon the expiration of the contract period, and updates the document management database 216 in response to user actions (such as renewing the contract).

[0071] The approval processing module 2046 receives an operation from a user to submit an approval request and controls the process by which approvers approve the request. Specifically, the approval processing module 2046 notifies each user who approves the request and updates the approval request database 213 in response to the operation to approve the request.

[0072] The LLM utilization module 2047 is a program module that performs processing related to the use of LLM, such as generating prompts to send to the server 95 of the large-scale language model service, sending the generated prompts as instructions to the server 95 of the large-scale language model service, receiving the results output by the server 95 of the large-scale language model service in response to the instructions (prompts), and performing processing using the received results.

[0073] The review processing module 2048 records reviews of the document data to be reviewed (for example, each clause of a contract) and updates the review history database 214. The review processing module 2048 communicates with the document review service server 93 and sends the document data to be reviewed, causing the server 93 to perform the review process. The module receives the results and updates the review history database 214. The review processing module 2048 also accepts operations from the user performing the review (for example, operations to input comments in association with the entire contract or each clause of the contract) and updates the review history database 214.

[0074] The template management module 2049 is a program module that performs template management processes, such as extracting document templates managed in the template database 212 that require changes and updating the change target management database 217, accepting operations to edit templates, and notifying each user about edited templates.

[0075] The contract creation processing module 2050 is a program module that generates contract data based on the content of a meeting and updates the meeting minutes management database 217.

[0076] <1.3 Configuration of Terminal 10> Figure 3 shows the configuration of terminal 10.

[0077] As shown in Figure 3, terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units corresponding to each antenna (first communication unit 120, second communication unit 121), an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a storage unit 180, and a control unit 190. Terminal 10 also has functions and configurations not specifically shown in Figure 3 (for example, a battery for maintaining power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in Figure 3, each block included in terminal 10 is electrically connected by a bus or the like.

[0078] Antenna 111 radiates signals emitted by terminal 10 as radio waves. Antenna 111 also receives radio waves from space and provides the received signals to first communication unit 120.

[0079] Antenna 112 radiates signals emitted by terminal 10 as radio waves. Antenna 112 also receives radio waves from space and provides the received signals to the second communication unit 121.

[0080] The first communication unit 120 performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 111 in order to communicate with other wireless devices. The second communication unit 121 also performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 112 in order to communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are a communication module that includes a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, etc. The first communication unit 120 and the second communication unit 121 perform modulation and demodulation, frequency conversion, etc., of the wireless signals transmitted and received by the terminal 10, and provide the received signal to the control unit 190.

[0081] The input device 130 has a mechanism for receiving user input operations. Specifically, the input device 130 is configured as a touchscreen and includes a touch-sensitive device 131. The touch-sensitive device 131 receives user input operations of the terminal 10. The touch-sensitive device 131 detects the user's contact position with the touch panel, for example, by using a capacitive touch panel. The touch-sensitive device 131 outputs a signal indicating the user's contact position detected by the touch panel to the control unit 190 as an input operation.

[0082] The display 132 displays data such as images, videos, and text in accordance with the control of the control unit 190. The display 132 is implemented by, for example, an LCD or an organic EL display.

[0083] The audio processing unit 140 modulates and demodulates the audio signal. The audio processing unit 140 modulates the signal received from the microphone 141 and provides the modulated signal to the control unit 190. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is implemented, for example, by an audio processing processor. The microphone 141 receives an audio input and provides the audio signal corresponding to that audio input to the audio processing unit 140. The speaker 142 converts the audio signal received from the audio processing unit 140 into sound and outputs the sound to the outside of the terminal 10.

[0084] The location information sensor 150 is a sensor that detects the location of the terminal 10, and is, for example, a GPS (Global Positioning System) module. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current location of the terminal 10, which is equipped with a GPS module, is detected based on the received signals.

[0085] Camera 160 is a device that receives light using a photodetector and outputs it as an image. Camera 160 is, for example, a depth camera that can detect the distance from camera 160 to the object being photographed.

[0086] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10.

[0087] The storage unit 180 is composed of, for example, flash memory and stores data and programs used by the terminal 10. The various types of information stored in the storage unit 180 will be described later.

[0088] The control unit 190 controls the operation of the terminal 10 by reading the program stored in the memory unit 180 and executing the instructions contained in the program. The control unit 190 is, for example, an application processor. By operating according to the program, the control unit 190 performs the functions of an operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, a notification control unit 194, and a memory control unit 195.

[0089] The operation reception unit 191 processes input operations from the user to an input device such as a touch-sensitive device 131. Based on the coordinate information of the touch-sensitive device 131 where the user's finger or the like has made contact, the operation reception unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation.

[0090] The transmitting / receiving unit 192 performs processing to enable the terminal 10 to send and receive data with an external device such as a server 20 in accordance with a communication protocol.

[0091] The data processing unit 193 performs calculations on the data received as input by the terminal 10 according to the program and outputs the calculation results to memory or other locations.

[0092] The notification control unit 194 performs the following processes: displaying the display image on the display 132, outputting sound to the speaker 142, and generating vibrations.

[0093] The memory control unit 195 controls the storage of data to the memory unit 180.

[0094] The various types of information stored by the memory unit 180 will now be explained. In a given situation, the memory unit 180 stores various types of information, such as user information 181.

[0095] User information 181 is information about a user who uses the services of server 20. User information 181 includes, for example, the user's employee number, name, and other information.

[0096] <2 Data Structure> Figure 4 shows the data structure of the user database 211. The user database 211 includes the fields "User ID", "Business ID", "Name", "Email Address", "Department", "Position", "Date of Employment", "Date of Resignation", and "Qualifications Held".

[0097] The "User ID" field is information that identifies each user.

[0098] The "Business ID" field contains information that identifies each business.

[0099] The "Name" field contains the user's name information.

[0100] The "Email Address" field is information that identifies the user and serves as their contact information.

[0101] The "Department" field contains information about the user's department.

[0102] Specifically, the "Department" field may include the following information about the department to which the user belongs: • Departments that do not primarily handle legal affairs, such as business divisions and sales divisions. • Departments that primarily handle legal affairs, such as legal affairs departments and intellectual property departments. The "Job Title" field contains information about the user's job title.

[0103] The "Date of Joining" field contains information about the date the user joined the organization.

[0104] The "Resignation Date" field contains information about the date the user left the organization.

[0105] The "Qualifications Held" item contains information about the qualifications the user holds.

[0106] Specifically, the item "Qualifications Held" includes the following information regarding the qualifications held by the user. • Qualifications that demonstrate the expectation of possessing the knowledge necessary to review contracts, similar to that of a lawyer. • Qualifications that demonstrate knowledge of business activities, such as a Certified Management Consultant for Small and Medium Enterprises. • Qualifications such as Certified Public Accountant and Tax Accountant, which indicate that the individual possesses the necessary knowledge in accounting, taxation, and related fields. Figure 5 shows the data structure of the template database 212. The template database 212 includes the following items: "Contract template ID", "Contract document type", "Contract data", "Related legal tags", "Related issue tags", "Links to explanations of related laws and issues", "Status", "Start date of use", and "End date of use".

[0107] The item "Contract Template ID" is information that identifies each contract template managed by server 20.

[0108] The item "Contract Document Type" contains information about the type of contract template.

[0109] The item "Contract Document Type" may include contract templates and the following: Typical contract • Atypical contracts Term sheet template The item "Contract Data" contains information about the data file for the contract template.

[0110] More specifically, the item "Contract Data" is a data file in an editable format.

[0111] The item "Related Legal Tags" contains information about the types of laws and regulations related to the contract template.

[0112] The item "Related Legal Tags" may include the following as types of laws related to the contract template: • Information identifying the clauses in the contract template (for example, clauses such as "Article 3" or clauses such as "Article 4, Paragraph 2"), and relevant legal information for each clause. • Information on the entire contract (including the type of contract, such as a "non-disclosure agreement") and relevant laws and regulations. The item "Related Issue Tags" contains information about the types of issues related to the contract template.

[0113] The item "Related Issue Tags" may include the following as types of issues related to the contract template: • Information identifying the clauses in the contract template (for example, clauses such as "Article 3" or clauses such as "Article 4, Paragraph 2"), along with information on related issues for each clause. • Information on the entire contract (including the type of contract, such as a "non-disclosure agreement") and related issues. The item "Links to Explanations of Relevant Laws and Issues" contains reference information that includes explanations of laws and issues related to the contract.

[0114] The item "Links to explanations of related laws and issues" may include the following as reference information: • Information on links to books included in the book browsing service provided by server 99. This may also include information on links to sections in the book that explain the relevant laws and issues. • Information on links to articles posted on information media that provide legal information on websites. • Information on links to explanatory articles about laws or precedents, provided by Server 94 and other servers of the Legal and Case Law Information Provision Service. • Links to guidelines, standards, etc. issued by public institutions. The "Status" field indicates whether the contract template is available for use.

[0115] The "Status" field may include the following information regarding availability: • In use: Available as a template • Before use: A template is provided, but it is not yet usable. For example, it may become usable after a legal amendment is applied. • Under revision: The template is currently being revised. It may be considered unusable as a template, or it may be considered usable. • Termination of Use: Not currently used as a template. For example, its use as a template may be terminated due to the application of legal revisions. The item "Start Date of Use" contains information about when the template began to be used.

[0116] The item "Usage Termination Date" contains information about when the template will no longer be used.

[0117] Figure 6 shows the data structure of the approval request database 213. The approval request database 213 includes the fields "Approval Request ID", "Applicant ID", "Approver ID", "Application Date", "Approval Date", "Application Details", and "Contract ID".

[0118] The item "Approval Request ID" is information that identifies each approval request.

[0119] The "Applicant ID" field is information that identifies the user who submitted the approval request.

[0120] Specifically, the item "Applicant ID" may be associated with user information (User ID) managed in the user database 211.

[0121] The "Approver ID" field is information that identifies the user who is the approver of the proposal.

[0122] Specifically, the item "Approver ID" may be associated with user information (User ID) managed in the user database 211.

[0123] The "Application Date" field contains information about the date and time when the system received the operation from the user who will be submitting the approval request data, in order to request approval of the approval request data from each user.

[0124] The "Approval Date" field contains information about the date and time when the user approved the data in the approval request.

[0125] The item "Application Details" contains information that shows the content of the approval request.

[0126] Specifically, the item "Application Details" includes the following types of approval requests. • Conclusion of a contract • Budget approval • Expense claim The item "Contract Signing ID" is information that identifies each step in the contract signing process.

[0127] Specifically, the item "Contract Signing ID" may be associated with information (Contract Signing ID) that identifies each contract signing procedure, which is managed in the contract signing management database 215. This links the approval application data in the approval application database 213 with the contract signing data in the contract signing management database 215.

[0128] Figure 7 shows the data structure of the review history database 214. The review history database 214 includes the following items: "Review ID", "Document Data", "Document Management ID", "Review Date and Time", "Reviewing User", "Review Content", and "Review Requester's Rating".

[0129] The "Review ID" field is information that identifies each review performed on the document data.

[0130] The item "Document Data" contains information about the document data that will be reviewed.

[0131] The "Document Management ID" field is information that identifies each document data being managed.

[0132] Specifically, the item "Document Management ID" may be associated with information (Document Management ID) that identifies each document data managed in the document management database 216.

[0133] The "Review Date and Time" field contains information about the date and time the review was performed.

[0134] The item "Reviewing User" contains information about the user who conducted the review.

[0135] The item "Review Content" contains information that shows the results of the review.

[0136] Specifically, the item "Review Content" may include the following as a result of the review: • Results of the review by server 93 of the document review service (e.g., advantages / disadvantages of conditions, importance, proposed revisions) • Comments and suggested revisions entered by users (including information about the user who entered the review comment) The item "Review Requester's Rating" is information that shows the user's rating of the reviewer's review content.

[0137] Specifically, the item "Review Requester's Rating" includes the results of the user who requested the review evaluating the reviewer based on the actions they took with respect to the review results, and may include the following: • The user who requested the review sets a score for the review results. • The number of "likes" and other reactions on posts made using messaging tools, etc., to inform users about reviewing the product. Figure 8 shows the data structure of the contract management database 215. The contract management database 215 includes the following fields: "Contract ID", "Sender ID", "Recipient ID", "Contract Target Data", "First Email Address", "Second Email Address", "Sending Date and Time", "User Signature Date and Time", "Contract Completion Date and Time", and "Status".

[0138] The item "Contract Signing ID" is information that identifies each step in the contract signing process.

[0139] Specifically, the item "Contract ID" includes identification information issued by server 20 when a new registration is accepted for the process of concluding an electronic contract by specifying an approver for document data that is subject to approval by the parties.

[0140] The "Sender ID" field is information that identifies the party who will be sending the document data when the party approves it.

[0141] Specifically, the item "Sender ID" may be associated with information about a business operator (Business ID) or information about a user (User ID) managed in the user database 211.

[0142] The "Recipient ID" field is information that identifies the recipient when they approve document data.

[0143] Specifically, the item "Recipient ID" is information that identifies the party designated as the recipient by the sender's user, and like the sender ID, it may be associated with information about a business operator (business operator ID) or information about a user (user ID) managed in the user database 211.

[0144] The item "Data Subject to Agreement" refers to the document data that the parties are required to approve.

[0145] Specifically, the item "Data subject to conclusion" refers to data (files such as PDFs) of transaction documents such as contracts, application forms, and quotations.

[0146] The item "First Email Address" is information that identifies the user who will be the sender in the process of concluding a contract by approving document data, and is the email address that serves as the contact address for that user.

[0147] Specifically, the item "First Email Address" is the email address of the user who performs the operation of sending the document data as the sender.

[0148] The item "Second Email Address" is information that identifies the user who approves the document data as the recipient in the process of concluding a contract by approving the document data, and is the email address that serves as the contact address for that user.

[0149] Specifically, the item "Second Email Address" is the email address of the user who approves the document data as the recipient. Note that there may be multiple users approving the document on each party's side, and if the user sending the document data specifies the email addresses of multiple users who will approve the document data, the contract management database 215 will also manage each of the specified email addresses.

[0150] The "Sending Date and Time" field contains information about the date and time when the sender, a user, initiated the process of requesting approval of the document data from each user.

[0151] The "User Signature Date and Time" field contains information about the date and time when the user performed an approval operation on the document data.

[0152] Specifically, the item "User Signature Date and Time" includes information about the timing when a user who has been requested to approve the document data reviews and approves the document data, and the server 20 accepts this operation, thereby electronically signing the document data. The server 20 electronically signs the document data each time a user performs the approval operation, and stores the timing information in the signing management database 215.

[0153] The item "Date and Time of Contract Completion" contains information about the date and time when the contract was completed.

[0154] Specifically, the item "Contract Completion Date and Time" is recorded in the contract management database 215 when the contract is concluded using the electronic contract service provided by server 20. The contract is considered concluded when all users designated to approve the document data complete the approval process.

[0155] The "Status" field indicates the stage in the contract signing process.

[0156] Specifically, the item "Status" may include the following as stages in the contract signing process: • Before sending: Indicates that the document data has been registered on server 20 by the sender, but has not yet been sent to the recipient. • In Progress: Indicates that the document data has been sent, but approval by each user has not yet been completed. • Completed: Indicates that the contract has been finalized. • Rejected, Returned: Indicates a situation where the contract was not finalized due to circumstances such as the user not approving the document data, or a timeout occurring after a certain period of time had elapsed before approval was complete. Figure 9 shows the data structure of the document management database 216. The document management database 216 includes the following items: "Document Management ID", "Contract Signing ID", "Document Title", "Contract Start Date", "Contract Expiration Date", "Automatic Renewal Status", and "Viewing Permission".

[0157] The "Document Management ID" field is information that identifies each document data being managed.

[0158] The "Contract Signing ID" field is information that identifies each contract signing procedure performed by the parties to approve the document data.

[0159] Specifically, the item "Contract Signing ID" may be associated with information (Contract Signing ID) that identifies each contract signing, which is managed in the contract signing management database 215.

[0160] The "Document Title" field contains information about the title of the document data being managed.

[0161] Specifically, the item "Document Title" may be a term used as the type or name of a contract, such as a confidentiality agreement, a sales agreement, or a license agreement.

[0162] The item "Contract Start Date" is the information shown in the document data as the contract start date.

[0163] Specifically, the item "Contract Start Date" may be set to the following value: • When the contract is finalized, Server 20 reads the contract start date from the contract data. • Information received from the user as the contract start date The same applies to the following items: "Contract Expiration Date" and "Automatic Renewal Status".

[0164] The item "Contract Expiration Date" is the information shown in the document data as the contract's expiration date.

[0165] The item "Automatic Renewal Status" indicates, in the document data, whether or not the contract period will be automatically extended (automatically renewed) without the parties specifically renegotiating a new contract upon the expiration of the contract period.

[0166] The item "Viewing Permission" is information about users who are set to have viewing permission for documents (e.g., contracts) managed in the document management database 216. Server 20 may allow users set as stakeholders of a document to view the document, and may not allow users who are not set to view the document to view it.

[0167] Specifically, the "Viewing Permissions" item may be used to manage the following users as stakeholders in the document data. - Users recorded in the contract management database 215 as users who approve document data. Note that the server 20 may identify the parties involved in the document data by referring to the users who approved the document data in the contract management database 215, rather than retaining the information of the parties involved in the document management database 216. • In the contract signing service provided by Server 20, in addition to the user who approves the document data, the server also accepts the designation of users to whom the data will be shared once the contract is signed. These designated users (the users to whom the data is transferred) are the ones specified. For example, in the case of minutes of a board meeting, a director may approve the document data, and then share the approved minutes with other users such as executive officers. • Other users designated by users who approve the document data, users who have permission to view the document data, etc. Furthermore, the "Viewing Permissions" item may be configured to include information that identifies departments or divisions within an organization, rather than individuals. For example, it may be possible to configure information corresponding to the "Department" item in user database 211. In other words, by defining which departments or divisions can view documents, users in those departments or divisions within the organization can view the documents.

[0168] Figure 10 shows the data structure of the meeting minutes management database 217. The meeting minutes management database 217 includes the following items: "Meeting Minutes ID", "Schedule ID", "Meeting Participants", "Meeting Minutes Title", "Meeting Video Data", "Transcript Data", "Meeting Memo Data", "Contract Terms Extraction Result", "Template Extraction Result", "Contract Data", and "Signing ID".

[0169] The item "Meeting Minutes ID" is information that identifies each meeting's minutes.

[0170] The "Schedule ID" field is information that identifies each meeting schedule.

[0171] In the illustrated example, the item "Schedule ID" indicates information that identifies the meeting schedule and may be associated with information such as the date and time of the meeting and the meeting room.

[0172] The item "Meeting Participants" is information that identifies the participants in the meeting covered by the meeting minutes.

[0173] The item "Meeting Participants" may be associated with the item "User ID" in user database 211.

[0174] The item "Meeting Minutes Title" contains information about the name of the meeting minutes.

[0175] More specifically, the item "Meeting Minutes Title" is a title that meeting participants arbitrarily set for the meeting minutes data, or a title set from the schedule title, etc.

[0176] The item "Meeting Video Data" contains information about the video data files related to the meeting.

[0177] More specifically, the item "Meeting Video Data" refers to information that identifies video data recorded using online meeting tools, etc. (such as a URL for accessing the video data). Video data files related to meetings may include those saved on the device or cloud storage by the online meeting tool, as well as video data files recorded on devices operated by meeting participants.

[0178] The item "Transcript Data" refers to the data file containing transcripts of the audio recordings of participants during the meeting.

[0179] More specifically, the item "transcribed data" refers to data transcribed using an automatic transcription function or similar method, based on the audio data of a meeting (for example, audio included in video data) using an online meeting tool or the speech recognition tool on a device. For example, if the names of the parties, contract terms, etc., are discussed during the meeting, this information may be included in the transcribed data.

[0180] The item "Meeting Minutes Data" contains information from the data file containing meeting minutes taken by the meeting participants.

[0181] More specifically, the item "Meeting Minutes Data" is information that identifies the data in a document that is entered and saved by each meeting participant in a document tool, etc. (such as a URL for accessing the document).

[0182] The item "Contract Terms Extraction Results" contains information on contract terms extracted from the meeting content.

[0183] The item "Contract Terms Extraction Results" may include the following as information on contract terms extracted from the meeting content: • Extraction results obtained by targeting the transcript data shown in the item "Transcript Data" and extracting information that will be reflected in the contract (for example, sections that are optionally filled in in the contract template). For example, the following may be possible.

[0184] (1) Information about the parties to the contract, such as their names and addresses. At meetings, the parties may introduce themselves to each other, and the names of the parties in the contract, the names of the representatives to be listed in the contract, etc., may be confirmed. The names of the parties may be extracted from the transcript data by extracting proper nouns using morphological analysis, etc., or the server 95 of the large-scale language model service may be prompted to identify the information of the parties, such as the names of the parties to conclude the contract, from the transcript data, and the output result of the server 95 may be obtained.

[0185] (2) Information on the terms and conditions of the transaction between the parties. For example, the unit price, quantity, transaction period, contract period, etc. of the goods or services being traded may be confirmed at the meeting. Information on the goods or services being traded, their unit price, and quantity may be extracted from the transcribed data by extracting numbers and nouns, etc., before and after those numbers, or the server 95 of the large-scale language model service may be prompted to summarize the information on the goods or services being traded, their unit price, and quantity from the transcribed data, and the output of the server 95 may be obtained. Server 20 may also extract contract terms information as described above, targeting the documents indicated in the item "Meeting Minutes Data".

[0186] The item "Template Extraction Results" contains information on contract templates that correspond to the content of the meeting.

[0187] The item "Template Extraction Result" may be associated with the item "Contract Template ID" in the template database 212. The server 20 determines the type of contract based on the contents of the meeting, for example, the items "Transcript Data", "Meeting Memo Data", "Meeting Minutes Title", and "Contract Condition Extraction Result" in the minutes management database 217. For example, during a meeting, the type of contract to be concluded (concluding a non-disclosure agreement) and the workflow (sending the contract, etc.) may be confirmed. Also, if a transaction is to be conducted during the meeting, and the type of contract, such as whether it is a sales contract, a contract for work, or a mandate contract, is confirmed, the server 20 may determine the type of contract based on that information. Furthermore, the server 20 may determine the type of contract according to the content of the transaction (e.g., wanting to transfer goods, wanting to request work, etc.).

[0188] The server 20 identifies a contract template corresponding to the determined type of contract by referring to the template database 212. For example, the contract template may be identified by comparing it with the "Contract Document Type" item of each template in the template database 212.

[0189] The item "Contract Data" contains the information of the generated contract.

[0190] More specifically, the item "Contract Data" is the contract information generated by applying the information extracted in the item "Contract Conditions Extraction Results" to the contract template shown in the item "Template Extraction Results". In this way, the server 20 generates a contract by embedding the information extracted from the meeting audio (information about the parties, information about transaction conditions such as amount and period) into the contract template extracted from the meeting audio.

[0191] The item "Contract Signing ID" is information that identifies the contract signing when the generated contract is concluded by the service performed by Server 20.

[0192] The item "Contract ID" may be associated with the item "Contract ID" in the contract management database 215.

[0193] <3 operations> Figure 11 shows the process flow for generating a contract based on meeting minutes data and sending a request to conclude the contract.

[0194] In step S1121, the contract creation processing module 2050 of the server 20 outputs an operation screen for managing meeting minutes to the terminal 10. Here, the server 20 stores data for multiple types of contract templates in the template database 212.

[0195] In step S1111, terminal 10 receives an operation from the user to specify the meeting minutes data to be used for creating the contract.

[0196] In step S1123, the contract creation processing module 2050 of the server 20 analyzes the meeting minutes data specified by the user of terminal 10 to determine the type of contract relating to the meeting, identifies a contract template corresponding to the determined type of contract, and updates the meeting minutes management database 217. The contract creation processing module 2050 analyzes the meeting minutes data to identify the contract terms and updates the meeting minutes management database 217.

[0197] In this way, the contract creation processing module 2050 obtains meeting minutes data by referring to the meeting minutes management database 217. The contract creation processing module 2050 identifies the contract terms related to the meeting by analyzing the obtained meeting minutes data.

[0198] More specifically, the contract creation processing module 2050 analyzes the meeting minutes data to determine the type of contract related to the meeting, and then reads the contract template data corresponding to the determined type of contract from the template database 212.

[0199] Here, the contract creation processing module 2050 may determine the type of contract relating to the meeting, as follows:

[0200] (1) The contract creation processing module 2050 may analyze the meeting minutes data by referring to the meeting minutes management database 217 and determining the type of contract or identifying the contract terms from the transcript data obtained by transcribing the meeting audio. For example, the type of contract may be determined by breaking down the content of the conversation shown in the transcript data into individual words and comparing the decomposed words with the type of contract (the purpose of the contract, such as confidentiality or sales). Alternatively, the type of contract may be determined by referring to the meeting minutes management database 217 and comparing the transcript data to be analyzed with past transcript data, and reading information on the template that served as the basis for the contract for concluding the contract, which is associated with past transcript data that has a similarity of a certain degree or higher. Furthermore, regarding the contract terms, words corresponding to the contract terms (for example, the object of the transaction, the unit price of the transaction, the quantity of the transaction, etc.) included in the transcript data of the conversation may be extracted.

[0201] (2) The contract creation processing module 2050 may generate a prompt that includes meeting minutes data managed in the meeting minutes management database 217 and an instruction to determine at least one of the type of contract or the contract terms from the meeting minutes data. The LLM utilization module 2047 provides the generated prompt to the server 95 of the large-scale language model service and receives at least one of the results of determining the type of contract or the results of determining the contract terms from the server 95 of the large-scale language model service.

[0202] In step S1125, the contract creation processing module 2050 of the server 20 reads a contract template corresponding to the type of contract from the template database 212. The contract creation processing module 2050 applies the contract terms information identified in step S1123 to the read contract template. As a result, the contract creation processing module 2050 outputs the contract data.

[0203] In step S1127, the contract creation processing module 2050 of the server 20 outputs an operation screen to the terminal 10 that allows the user to confirm the contract data generated in step S1125.

[0204] In this way, the contract creation processing module 2050 outputs contract data based on the specified contract terms.

[0205] Here, the contract creation processing module 2050, in outputting contract data, may also output the contract template data read in step S1125 to terminal 10, in addition to what was described in steps S1123 and S1125 above (generating contract data by applying contract terms to a contract template). This allows obtaining a contract template from the meeting content, and the user may be provided with an operation screen that accepts user input for items to be entered in the template (names of parties, terms of the transaction, etc.), and the contract data may be output according to the content entered by the user.

[0206] Furthermore, the contract creation processing module 2050 may display the meeting minutes data and the contract data output in step S1125 (or a contract template identified from the meeting content as described above) side by side, and may accept an operation from the user to confirm the displayed contract data. This makes it easy for the user to confirm the contents of the output contract while confirming the contents of the meeting. Here, the operation to confirm the contract data may be accepted as an operation to finalize the contents of the contract, and the generated contract data in step S1125 may be presented to the user, allowing for modifications, and then the operation to finalize the contents of the contract may be accepted. This makes it easy to create a contract from the contents of the meeting.

[0207] In step S1113, terminal 10 displays the meeting minutes data and the contract data. Terminal 10 confirms the contract data and accepts an operation from the user to send a request to conclude the contract.

[0208] In step S1129, the contract creation processing module 2050 of the server 20 receives an operation from the user to conclude a contract using a predetermined method such as an electronic contract system provided by the server 20, such as an electronic contract and document management service (where an approver performs an operation to approve the document data, thereby performing an electronic signature and managing the document data). The conclusion processing module 2044 sends an approval request to approve the contract data to the approver of the contract data. The conclusion processing module 2044 receives the operation to approve the contract data from the approver and manages the contract data as approved in the document management database 216, etc.

[0209] Here, the approvers to whom the request for approval of the contract data is sent may be as follows:

[0210] For example, with respect to the contract data output in step 1127 above, the meeting participants managed in the minutes management database 217 may be set as those who will approve the contract data, and the signing processing module 2044 may send an approval request to approve the said contract data. The signing processing module 2044 may accept the operation of the meeting participant, who is the approver, to approve the approval request, and manage the contract data in the document management database 216 as having been approved.

[0211] As described above, the contract creation processing module 2050 may accept an operation by the user to confirm the contract data output in step S1125. The signing processing module 2044 sends an approval request to the approver of the contract data to approve the contract data. The signing processing module 2044 accepts the operation by the approver to approve the approval request and manages the contract data in the document management database 216 as approved.

[0212] <4. Screen Example> Figure 12 shows an example of an operation screen where the user can review the meeting minutes data and the generated contract data, and then proceed with the steps required to conclude the contract.

[0213] The contract operation screen 1200 is an operation screen that accepts requests to generate a contract based on the contents of a meeting.

[0214] The minutes display area 1202 is the area that displays the content of the meeting for which the contract will be generated.

[0215] The minutes display area 1202 corresponds to each of the processes in steps S1121, S1111, S1123, etc. in Figure 11.

[0216] The analysis target designation unit 1204 is an operating component that accepts the designation of a meeting to be used as the target for generating a contract.

[0217] In the illustrated example, the analysis target designation unit 1204 refers to the meeting minutes management database 217 and displays the meeting schedule, meeting participants, meeting minutes title, meeting data (video data, transcript data, meeting memo data), etc., making it easy for the user to identify the meeting to be used for generating the contract.

[0218] The template confirmation operation unit 1206 is an operation component that accepts operations to confirm a list of contract templates.

[0219] In the illustrated example, the template confirmation operation unit 1206 displays a list of various templates managed in the template database 212 in response to user operations, and displays a screen for displaying the template to be confirmed in response to user operations to confirm the details of a template.

[0220] The creation operation unit 1208 is an operation component that accepts the operation to create a contract for a meeting specified by the user in the template confirmation operation unit 1206.

[0221] The generated contract display area 1210 is an area that displays the contract generated based on the specified meeting.

[0222] The generated contract display area 1210 corresponds to each process such as steps S1127 and S1113 in Figure 11.

[0223] The meeting content display area 1212 is an area that displays transcript data based on the voices of the participants during the meeting.

[0224] In the illustrated example, the meeting content display area 1212 displays transcript data, but it can also display data managed in the meeting minutes management database 217 (for example, the "Meeting Minutes Data" item, a preview of the video data for the "Meeting Video Data" item, etc.) to make it easier for the user to recognize the meeting content that forms the background of the contract displayed in the contract display area 1214, which will be described later. As a result, the user can easily check the meeting content and easily judge whether the content of the contract displayed in the contract display area 1214 is appropriate or not, thereby encouraging the creation of the contract.

[0225] The contract display area 1214 is the area that displays the contract generated by analyzing the contents of the meeting.

[0226] In the illustrated example, the contract display area 1214 is shown to be displayed on the same screen as the meeting content display area 1212. This allows users to easily verify whether the contents of the contract (information of the parties, terms of trade, etc.) are appropriate while simultaneously reviewing the contents of the contract and the contents of the meeting that formed its background. In the illustrated example, the contract display area 1214 may also accept an operation to edit the contract displayed therein. For example, the contract creation processing module 2050 accepts an operation from the user to modify the contract if the contents of the generated contract are not what was intended.

[0227] The original template viewing operation unit 1216 is an operating component that accepts operations to check the contract template that served as the basis for creating the contract.

[0228] In the illustrated example, the original template viewing operation unit 1216 displays the template (in the illustrated example, "Sales Contract") that was used to create the contract displayed in the contract display area 1214, in response to user operations.

[0229] The analysis result display area 1218 is an area that displays the contract terms of the agreement related to the meeting, extracted based on data such as meeting minutes.

[0230] In the illustrated example, the analysis result display area 1218 displays information on contract terms extracted from meeting minutes, etc., as shown in the "Contract Terms Extraction Results" item of the meeting minutes management database 217. In this way, the original template viewing operation unit 1216 makes it easy to check the information of the contract template that was used to create the contract and the contract terms extracted from the meeting minutes, making it easy to check the contract displayed in the contract display area 1214.

[0231] Section 1220 of the application highlights sections of the contract template where information regarding contract terms has been added to suit the specific circumstances of each case.

[0232] In the illustrated example, application location 1220 shows that information about the contracting parties, information about the terms and conditions of the transaction related to the contract, etc., is being applied to the template.

[0233] Reference section 1222 highlights the corresponding section in the meeting transcript data regarding the information on contract terms applied to the contract template.

[0234] In the illustrated example, reference section 1222 highlights the sentences and paragraphs before and after the section corresponding to the contract terms applicable to the contract template (in the illustrated example, the transaction price). The server 95 of the large-scale language model service may be used to identify the section corresponding to the contract terms from the transcript data, etc.

[0235] The contract confirmation operation unit 1224 is an operation component that accepts operations to confirm the contents of the contract that has been output based on the content of the meeting.

[0236] In the illustrated example, the contract confirmation operation unit 1224 displays the contract in the contract display area 1214 as "confirmed" in response to the user's operation, indicating that the user has confirmed the contents of the contract.

[0237] The contract signing process display area 1226 is an area that displays the process by which the parties sign a contract that has been generated and whose contents have been finalized.

[0238] The approver designation unit 1228 is an operating component that accepts the designation of an approver who will approve the contract.

[0239] The approver designation unit 1228 displays candidates for approvers of the contract and accepts designations from the user, and may include the following: • Display meeting participants as potential approvers. • Users with access to view and edit meeting minutes data (meeting video data, transcript data, meeting notes, etc.) will be displayed as candidates for approver. In addition, the approver designation section 1228 may allow the user to specify any candidate approver.

[0240] The contract signing request operation unit 1230 is an operating component that receives an operation to send a contract approval request to an approver.

[0241] In the illustrated example, the contract signing request operation unit 1230 notifies the approver designated in the approver designation unit 1228 to approve the contract displayed in the contract display area 1214 using the contract signing service provided by the server 20. If the contents of the contract have been finalized through an operation to the contract confirmation operation unit 1224 (for example, if one or more users confirm the contents of the contract), the approval processing module 2046, etc., may proceed with the approval process for contract signing and update the approval application database 213. Alternatively, if the contents of the contract have been finalized through an operation to the contract confirmation operation unit 1224, the transmission of the contract signing request by the contract signing request operation unit 1230 may be accepted, but if the contents of the contract have not been finalized, the transmission of the contract signing request by the contract signing request operation unit 1230, etc., may not be accepted.

[0242] (modified version) The above description of the embodiment explained an example in which meeting minutes information is managed in the meeting minutes management database 217 based on document information stored in the document creation service server 96. In addition, it is also possible to extract contract terms information from data stored in other services, such as the sales support system service server 97, and create a contract. For example, if the document data contains a link to information managed by the sales support system service server 97, the contract terms may be extracted by referring to the information at the link destination and a contract may be created. Furthermore, if applying the contract terms extracted from the meeting minutes to the template is insufficient (there is still information that should be applied to the template), the system may notify each user of this fact. This makes it easy for users to recognize that the creation of the contract is not yet complete.

[0243] Alternatively, contract terms may be extracted from information stored in messaging tools that allow users to send and receive messages. For example, the content of posts made by users who participated in a meeting may be extracted from the messaging tool. Or, contract terms may be extracted from messages sent in the messaging tool to users or departments that handle contract work, such as legal affairs personnel. For example, if applying contract terms extracted from meeting minutes is insufficient (i.e., there is insufficient information to apply to the template), the relevant posts may be identified by referring to the messaging tool, etc., and the contract terms may be extracted from the identified posts.

[0244] In the above description of the embodiment, an example was described in which, for a created contract, participants in a meeting or users with viewing and editing rights to the document are selected as candidates for approvers, and the system accepts their designation as recipients of approval requests. Alternatively, users who have reviewed the created contract may be selected as candidates for approvers, and the system may accept their designation as recipients of approval requests and send the approval requests.

[0245] A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0246] Furthermore, by distributing all or part of each hardware configuration across multiple computers and connecting them to each other via a network, computer 90 can be virtually realized. Thus, the concept of a computer includes not only computers housed in a single enclosure or case, but also virtualized computer systems.

[0247] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters.

[0248] Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.

[0249] Furthermore, by storing data, various programs, and various databases in the memory unit, the information processing device and information processing system related to this disclosure can be considered to have been manufactured.

[0250] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.

[0251] Furthermore, each of the above-mentioned configurations, functions, processing units, processing means, etc., may be implemented in hardware, either partially or entirely, by designing them as integrated circuits, for example. The present invention can also be implemented by software program code that realizes the functions of the embodiment. In this case, a storage medium on which the program code is recorded is provided to a computer, and the processor of that computer reads the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the embodiment described above, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media used to supply such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, and the like.

[0252] Furthermore, the program code that implements the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, Perl, Shell, PHP, and Java (registered trademark).

[0253] Furthermore, the program code for the software that implements the functions of the embodiment may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the computer's processor may read and execute the program code stored in the storage means or storage medium.

[0254] The functions realized by the components described herein may be implemented in a circuit or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the functions described herein. A processor is considered to be a circuit or processing circuitry, including transistors and other circuits. A processor may be a programmed processor that executes a program stored in memory.

[0255] In this specification, circuitry, unit, and means are hardware programmed to perform or execute the functions described herein. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to perform or execute the functions described herein.

[0256] If the hardware is a processor that is considered to be a type of circuitry, then the circuitry, means, or unit is a combination of hardware and software used to constitute the hardware and / or processor.

[0257] As described above, some embodiments of the present disclosure have been explained. However, these embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are to be included in the scope and gist of the invention, and are also to be included in the invention described in the claims and the scope equivalent thereto.

[0258] (Supplementary Note) The matters described in each of the above embodiments are appended below.

[0259] (Supplementary Note 1)

[0260] (Supplementary Note 1) A program for operating a computer including one or more computer processors, the program causing the one or more computer processors to perform steps of acquiring data of minutes of a meeting, specifying contract terms of a contract related to the meeting by analyzing the data of the minutes, and outputting data of a contract document based on the specified contract terms. Program.

[0261] (Supplementary Note 2) In a storage unit, data of templates of a plurality of types of contract documents are stored. In the specifying step, by analyzing the data of the minutes, the type of the contract related to the meeting is discriminated, and data of the template of the contract document corresponding to the discriminated type of the contract is read out. In the outputting step, the data of the template of the contract document read out is output. The program according to Supplementary Note 1.

[0262] (Supplementary Note 3) In the outputting step, data of a contract document generated by applying the specified contract terms to the data of the template of the contract document read out is output. The program according to Supplementary Note 2.

[0263] (Supplementary Note 4) The program described in Appendix 3, which, in the identification step, analyzes meeting minutes data to determine the type of contract or to identify the contract terms from the transcript data obtained by transcribing the meeting audio.

[0264] (Note 5) In the identification step, A program as described in any of Appendix 2 to 4, which generates a prompt containing meeting minutes data and instructions to determine the type of contract from the meeting minutes data; receives the result of determining the type of contract from a large-scale language model by providing the generated prompt to a large-scale language model; and reads out contract template data corresponding to the received result of determining the type of contract.

[0265] (Note 6) The program is one of the programs described in any of Appendix 1 to 5, which further sends an approval request to the meeting participants for the contract data output in the output step, and accepts the operation of the participants approving the approval request and manages the contract data as approved.

[0266] (Note 7) The program is one of the programs described in any of Appendix 1 to 6, which further displays meeting minutes data and contract data output in the output step side by side on one or more computer processors, accepts an operation from the user to confirm the displayed contract data, sends an approval request to the approver of the contract data upon receiving the confirmation operation, accepts an operation from the approver to approve the approval request, and manages the contract data as approved.

[0267] (Note 8) A method for operating a computer having one or more computer processors, wherein the program performs the steps of: one or more computer processors acquiring meeting minutes data; analyzing the meeting minutes data to identify the contract terms relating to the meeting; and outputting contract data based on the identified contract terms.

[0268] (Note 9) An information processing device wherein the control unit of the information processing device performs the steps of: acquiring meeting minutes data; identifying the contract terms of a contract relating to the meeting by analyzing the meeting minutes data; and outputting contract data based on the identified contract terms.

Claims

1. A program for operating a computer having one or more computer processors, The program is configured on one or more computer processors. Steps to obtain meeting minutes data, The steps include: analyzing the data from the meeting minutes to identify the contract terms of the agreement relating to the meeting; The process involves outputting contract data based on the specified contract terms and conditions, and then executing the following steps: program.

2. The memory unit stores data for multiple types of contract templates. In the aforementioned identification step, the type of contract relating to the meeting is determined by analyzing the data of the meeting minutes, The process involves reading the data of the contract template corresponding to the identified type of contract, The program according to claim 1, wherein in the output step, it outputs the data of the template contract that was read.

3. The program according to claim 2, wherein in the output step, it outputs contract data generated by applying the specified contract terms to the data of the read contract template.

4. The program according to claim 3, wherein in the step of identification, the program analyzes the data of the minutes and determines the type of contract or identifies the terms of the contract from the transcript data obtained by transcribing the audio of the meeting.

5. In the aforementioned step of identification, The process involves generating a prompt that includes the data of the minutes and an instruction to determine the type of contract from the data of the minutes, The generated prompt is provided to a large-scale language model, and the result of the large-scale language model determining the type of contract is received. The program according to claim 2, which reads out data of a template of the contract corresponding to the result of determining the type of contract received.

6. The program further provides the following to one or more computer processors: With respect to the contract data output in the output step, an approval request is sent to the participants of the meeting to approve the contract data, The program according to claim 1, which receives an operation in which the participant approves the approval request and manages the contract data as approved.

7. The program further provides the following to one or more computer processors: Displaying the meeting minutes data and the contract data output in the output step side by side, The system accepts requests from users to confirm the data of the contract that is displayed, By accepting the aforementioned confirmation operation, an approval request for the approval of the contract data is sent to the approver of the contract data, The program according to claim 1, which receives an operation in which the approver approves the approval request and manages the contract data as approved.

8. A method for operating a computer having one or more computer processors, The program is performed by the one or more computer processors, Steps to obtain meeting minutes data, The steps include: analyzing the data from the meeting minutes to identify the contract terms of the agreement relating to the meeting; A method for performing the steps of outputting contract data based on specified contract terms.

9. An information processing device, The control unit of the information processing device, Steps to obtain meeting minutes data, The steps include: analyzing the data from the meeting minutes to identify the contract terms of the agreement relating to the meeting; An information processing device that performs the step of outputting contract data based on specified contract terms.

Images