Information processing device, information processing method, and program

The information processing system addresses the inefficiency of traditional contracts by electronically generating and managing contracts with invariant and variable terms, enhancing convenience and reducing manual effort in contract conclusion.

JP2025128308APending Publication Date: 2025-09-02DAYZ INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2025097970
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-02-28
Filing Date
2025-06-11
Publication Date
2025-09-02

AI Technical Summary

Technical Problem

Conventional contract technologies primarily focus on preventing tampering and managing signatures but fail to enhance the convenience of concluding contracts, requiring parties to manually review and adjust every word and phrase, making the process cumbersome and inefficient.

Method used

An information processing system that generates and manages contracts using a rules generation mechanism, separating invariant and variable information, allowing parties to negotiate and agree on variable terms electronically, storing and managing agreement information in a database.

Benefits of technology

Facilitates convenient contract conclusion by electronically managing and storing agreement information, reducing manual effort and time, and enabling efficient management of multiple contracts without relying on physical documents.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025128308000001_ABST
    Figure 2025128308000001_ABST
Patent Text Reader

Abstract

To improve convenience when parties execute a contract with a proper content.SOLUTION: The present invention improves convenience when parties execute a contract with a proper content without depending on a business contract. A convention generation unit 62 generates conventions or the like including an invariable portion and a variable portion among information that is necessary in a prescribed contract, the invariable portion to which invariable information is added and the variable portion to which variable information, of which the content is variable by negotiations between a convention presenter and a convention consenter, is added. A convention providing unit 63 provides, to a convention consenter's terminal 3, the conventions or the like and a user interface that receives a variable information adding operation for attaching, to the variable portion, the negotiation result between the convention presenter and the convention consenter as the variable information, and a consent operation for consenting to the conventions or the like. When the consent operation is received, a convention management unit 64 stores, to a convention DB 51, and manages convention consent information including the invariable information, the variable information, and person identification information through which the convention consenter can be identified.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a technique for assigning classification information to products. [Background technology]

[0002] Conventionally, techniques for making electronic contracts using contract documents have been proposed (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-285592 Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional technologies including those disclosed in Patent Document 1 can only prevent contract tampering and manage signatures, and do not sufficiently improve the convenience of the act of concluding a contract. In other words, the parties to a contract must confirm and adjust every word and phrase of the entire contract, and then the contract is concluded by mutually signing, etc. As such, as long as contracts are used, it is difficult to improve the convenience of concluding contracts.

[0005] The present invention has been made in consideration of such circumstances, and aims to improve convenience when concluding a contract with content appropriate for both parties without relying on a written contract. [Means for solving the problem]

[0006] In order to achieve the above object, an information processing device according to one aspect of the present invention comprises: An information processing device that communicates with a first terminal operated by a terms presenter who presents terms and conditions related to a specified contract, and a second terminal operated by a terms accepter who concludes the specified contract with the terms presenter by agreeing to the terms and conditions, a rules generation means for generating rules and the like having an invariant portion to which first information whose content is invariant is attached and a variable portion to which second information whose content is variable through negotiation between the rules proposer and the rules acceptor, among the information necessary for the predetermined contract; a terms provision means for providing the second terminal with a user interface that accepts a first operation for attaching the terms and the result of negotiation between the terms proposer and the terms acceptor to the variable part as the second information, and a second operation for agreeing to the terms and the like; a rules management means for, when the second operation is accepted, storing and managing information including the first information attached to the immutable part, the second information attached to the variable part by the first operation, and personal identification information capable of identifying the person who agreed to the rules in a predetermined database as rules agreement information; Equipped with.

[0007] An information processing method and a program according to one aspect of the present invention are respectively an information processing method and a program corresponding to the information processing device according to the above-described one aspect of the present invention. [Effects of the Invention]

[0008] According to the present invention, it is possible to improve convenience when concluding a contract with content appropriate for the parties involved, without relying on a written contract. [Brief explanation of the drawings]

[0009] [Figure 1] A diagram showing patterns of agreements that can be concluded using this service. [Figure 2] FIG. 2 is a diagram showing an example of an extended contract that can be created using this service, out of the contract patterns shown in FIG. 1. [Figure 3] FIG. 1 is a diagram showing an overview of an example of the flow of this service. [Figure 4]FIG. 4 is a diagram showing an example of a list of the variable parts of the agreement information of multiple agreement agreeees managed by the service shown in FIG. 3. [Figure 5] 1 is a diagram showing an example of the configuration of an information processing system to which a server according to an embodiment of the information processing apparatus of the present invention is applied; [Figure 6] FIG. 6 is a block diagram showing an example of the hardware configuration of a server in the information processing system shown in FIG. 5. [Figure 7] 7 is a functional block diagram showing an example of a functional configuration for executing a rule generation process, a rule conclusion process, and a rule confirmation process, among the functional configurations of the server of FIG. 6 constituting the information processing system of FIG. 5; [Figure 8] FIG. 10 is a diagram showing an example of a website production contract as a specific example of the terms and conditions and a predetermined user interface displayed on the terminal of a person who agrees to the terms and conditions. [Figure 9] FIG. 10 is a diagram showing an example of a website production contract as a specific example of the terms and conditions and a predetermined user interface displayed on the terminal of a person who agrees to the terms and conditions. [Figure 10] FIG. 10 is a diagram showing an example of an employment contract as a specific example of the terms and conditions and a predetermined user interface displayed on the terminal of a person who agrees to the terms and conditions. [Figure 11] FIG. 10 is a diagram showing an example of an employment contract as a specific example of the terms and conditions and a predetermined user interface displayed on the terminal of a person who agrees to the terms and conditions. [Figure 12] FIG. 10 is a diagram showing the functional configuration of a server of a second embodiment of an information processing device according to the present invention. [Figure 13] 13 is a diagram showing a detailed configuration of a survival status management unit in the functional configuration of the server in FIG. 12. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0011] First, an overview of a service to which an embodiment of an information processing device of the present invention is applied (hereinafter referred to as "this service") will be described with reference to FIGS.

[0012] This service is provided by the service provider to parties who enter into a specified contract based on terms and conditions. In this specification, the term "rules, etc." refers to rules, regulations, rules, and rules.

[0013] Specifically, this service focuses on the management and operation of regulations, etc. The methods for forming a contract, that is, the methods for aligning the intentions of both parties, can be broadly divided into the traditional method of exchanging a "contract" (hereinafter referred to as the "contract method") and the method that uses "other terms and conditions, etc." (hereinafter referred to as the "terms and conditions method"). This service uses the terms and conditions method. Below, we will further explain the terms and conditions adopted by this service, comparing them with traditional contract methods.

[0014] Unless a contract is a formal contract, it is formed solely by the agreement of the parties' intentions (the agreement between the expression of intention to offer and the expression of intention to accept). In this sense, in traditional contract methods, the parties' intentions are agreed upon when a contract is created. In other words, although it depends on business practices, in Japan it is common for both parties to sign and seal a contract as evidence of the "agreement of the parties' intentions" mentioned above, and the Civil Procedure Act also recognizes that private documents bearing a seal have special evidentiary force.

[0015] However, the creation of a contract is not a requirement for the formation of a contract, and under the "principle of private autonomy," the method for forming a contract is generally left to the discretion of the parties. In the Terms and Conditions method adopted by the Service, one of the parties will establish the Terms and Conditions, present them to the other party, and ask for the other party's consent. Hereinafter, the party that establishes and presents the Terms and Conditions will be referred to as the "Terms Presenter," and the other party whose consent is sought from the Terms Presenter will be referred to as the "Terms Accepter." Here, the content of the terms and conditions cannot usually be changed, and the only options are to agree or not. Therefore, under Japanese law, the "presentation" of the terms and conditions constitutes an "offer," and "agreeing" to them constitutes an "indication of intent to accept." Therefore, when both the presentation and consent to the terms and conditions coincide, a contractual relationship in accordance with the content of the terms and conditions is created (a contract is concluded). In that sense, terms and conditions, like a contract, are valid under Japanese law as an agreement between both parties, i.e., a "consent of the parties." Therefore, under Japanese law, it is possible to establish almost all contracts using the "terms and conditions method," except for those that require the conclusion of a contract in paper form (i.e., the formal contracts mentioned above). Here, the methods for obtaining consent from users who agree to the terms and conditions can be broadly divided into "explicit consent" and "implicit consent." This service is compatible with both "explicit consent" and "implicit consent."

[0016] For the sake of convenience, the following explanation will be given using the rules as an example. However, anything written about rules below applies to other rules as well.

[0017] FIG. 1 shows patterns of agreements that can be concluded using this service. As shown in Figure 1, the patterns of terms and conditions that can be created using this service can be broadly divided into patterns that keep a log of consent from those who agree to the terms and conditions, and patterns that do not keep a log of consent. Examples of patterns that do not leave a log of consent from users who agree to the terms include privacy policies and terms of use (posting only). In contrast, the pattern of keeping a log of agreements from those who agree to the terms and conditions can be broadly divided into a pattern in which individual negotiations are not conducted and a pattern in which individual negotiations are conducted. An example of a pattern where individual negotiations are not conducted is terms of use (with consent confirmation). An example of a pattern for individual negotiations is shown in Figure 2.

[0018] FIG. 2 is a diagram showing an example of an extended contract that can be created by this service, among the contract patterns shown in FIG. As shown in Figure 2, an extended agreement is an agreement that has an immutable part KF, which is made up of information whose content remains unchanged (hereinafter referred to as "immutable information"), and a variable part KK, which is made up of information whose content changes through negotiations between the agreement proposer and the agreement acceptor (hereinafter referred to as "variable information"). The example in Figure 2 shows the extended terms and conditions for use by a specific company in an employment contract. That is, in the example of FIG. 2, a specific company (employer) is the terms proposer, and a person employed by the specific company (employee) is the terms acceptor. For this reason, the contents of the rules that are equally required for all employees are attached to the invariant part KF as immutable information and presented to those who agree to the rules. On the other hand, as shown in Figure 2, conditions that vary from person to person, such as employment period, duties, salary (hourly rate), probationary period, holidays, etc., which are determined through negotiations between the employer (those who propose the terms) and the employee (those who agree to the terms), are attached to the variable part KK as variable information.

[0019] The flow of this service when a specified contract is concluded based on such extended terms will be described below with reference to FIG. FIG. 3 is a diagram showing an outline of an example of the flow of this service.

[0020] This service uses software provided online (SaaS), that is, an information processing system (database management system) that creates new terms and conditions, updates and revises the terms and conditions on a server 1 managed by the service provider SA.

[0021] Specifically, for example, the terms presenter KT uses the service by operating an information processing device 2 such as a personal computer, tablet, or smartphone (hereinafter referred to as the "terms presenter terminal 2"). Furthermore, the terms and conditions consenter KD uses the service by operating an information processing device 3 such as a personal computer, tablet, or smartphone (hereinafter referred to as the "terms and conditions consenter terminal 3"). The terms presenter terminal 2 and the terms accepter terminal 3 can each use this service by using a browser function or the like to access the SaaS managed by server 1, and the terms presenter KT and the accepter KD can each use this service.

[0022] In other words, among the conventional contract methods, the method of concluding a contract using a contract in an electronic contract service involved the parties signing a file (PDF, etc.) online. In contrast, in this service, which employs the terms and conditions method, the terms and conditions presenter KT operates the terms and conditions presenter terminal 2 to access the SaaS, generates terms and conditions whose text is entirely or partially standardized (i.e., extended terms and conditions), and presents them to the terms and conditions consenter KD via the terms and conditions consenter terminal 3. That is, the terms and conditions consenter KD operates the terms and conditions consenter terminal 3 to access the SaaS and consent to the presented terms and conditions. This generates information (hereinafter referred to as "terms and conditions consent information") that can identify the terms and conditions agreed to, including "what terms," ​​"when," "who," and "where." This terms and conditions consent information is stored in DB 51 (hereinafter referred to as "terms and conditions DB 51") managed by the service provider SA, thereby recording evidence of the agreement between the terms and conditions presenter KT and the terms and conditions consenter KD (the contract indicated by the terms and conditions consent information is concluded). Here, this service can link and manage the consent of multiple KDs who agree to the terms of use for one set of terms. In other words, unlike the conventional "contract method," this service, which adopts the "terms and conditions method," has the functionality to support fileless 1-to-N (N is any integer value greater than or equal to 1) consent.

[0023] If necessary, dedicated application software having the same functions as the above-mentioned SaaS may be installed on each of the terms presenter terminal 2 and the terms acceptor terminal 3. This allows each of the terms presenter KT and the terms acceptor KD to use the Service using the terms presenter terminal 2 and the terms acceptor terminal 3 on which the application software is installed.

[0024] The flow of this service is explained in detail below. As shown in Figure 3, the variable part KK before the variable information is added will be specifically referred to as the "variable part KKB", and the variable part KK after the variable information is added will be specifically referred to as the "variable part KKA". Accordingly, the extension rules for the state of the variable part KKB will be hereinafter referred to as the "rules KB", and the extension rules for the state of the variable part KKA will be hereinafter referred to as the "rules K".

[0025] As shown in FIG. 3, in step S1, the terms and conditions presenter KT operates the terms and conditions presenter terminal 2 to access the SaaS of the server 1, thereby creating the terms and conditions KB (data).

[0026] In step S2, the terms agreeer KD operates the terms agreeer terminal 3 to access the SaaS of the server 1, and is provided with the terms KB and a predetermined user interface. Here, the predetermined user interface accepts an operation (hereinafter referred to as a "variable information addition operation") for attaching information indicating the result of negotiation between the terms proposer KT and the terms agreeer KD to the variable part KKB as variable information. The predetermined user interface also accepts an operation (hereinafter referred to as an "agreement operation") for the terms agreeer KD to agree to the terms KB.

[0027] In steps S3KT and S3KG, the policy presenter KT and the policy agreeer KD negotiate to determine variable information. Here, "negotiating" is a broad concept that includes not only negotiations in which both parties communicate simultaneously, but also cases in which the terms proposer KT presents a variable information proposal in advance, and then the terms acceptor KD adopts the variable information proposal, thereby confirming the variable information proposal as variable information. Below, we will explain an example in which the latter concept of "negotiating" is adopted. That is, when creating the rules KB in step S1, the rules proposer KT, for example, operates the rules proposer terminal 2 to provide options in a predetermined user interface that allow the rules agreeer KD to select a desired proposal from multiple variable information proposals, and blank spaces in which desired content can be entered, in the variable part KKB, in step S3KT. Furthermore, the rules proposer KT can also input (attach) a proposal that he or she desires to the variable part KKB in advance, as necessary. In step S3KD, the terms and conditions agreeee KD, who has been provided with the prescribed user interface together with the terms and conditions KB in step S2, performs a variable information addition operation for the options and blank spaces provided in the prescribed user interface using the terms and conditions agreeee terminal 3. That is, the terms and conditions agreeee KD selects the desired variable information proposal from the options, or inputs the desired content (variable information proposal) into the blank spaces. As a result, a variable part KKA with the variable information added is generated.

[0028] The agreement agreeer KD performs the variable information addition operation as described above using the agreement agreeer terminal 3, and then agrees to the agreement K by performing an agreement operation in step S4. As mentioned above, consent can be either explicit consent or implicit consent. The terms and conditions consenter KD can give explicit consent by performing, for example, an operation that explicitly indicates consent (for example, pressing the "Agree button DBM" in FIG. 9, which will be described later) as a consent operation. The terms and conditions consenter KD can also give implicit consent by performing, for example, an operation for a different purpose (for example, pressing the "Next button DBA" in FIG. 11, which will be described later, to perform the next operation, etc.).

[0029] In step S5, the server 1 (SaaS) stores information including the invariant information added to the invariant part KF, the variable information added to the variable part KKA by the variable part addition operation, and information that can identify the agreement consenter KD (hereinafter referred to as "person identification information") as agreement information for the terms, etc. in the agreement DB 51. This results in the conclusion of a contract identified by the agreement information for the terms, etc. In this way, the agreement information on the rules and the like is stored in the rules DB 51 and managed.

[0030] Here, although only one person is shown as the agreement consenter KD in the example of FIG. 3, the number is not limited to one, and may be multiple. Specifically, for example, the store manager of a store that has concluded a franchise agreement with the head office will act as the terms presenter KT and enter into employment contracts with 10 part-time staff members. In other words, each of the 10 part-time staff members will become a KD who agrees to the terms and conditions. Of the 10 part-time staff, let's say that Mr. A is a part-timer with 5 years of service who works 5 days a week. Mr. B is a part-timer who has recently increased his shifts (from 1 day a week to 4 days a week). Mr. C is a student hired for a short period (3 months) during the busy season. Mr. D is a Taiwanese person on a working holiday visa who has been working for 3 months and will be returning to his home country next year. Ms. E is a housewife who is scheduled to be hired next month and wants to work within the dependents' allowance. There are also five other staff members: Mr. F, Mr. G, Mr. H, Mr. I, and Mr. J.

[0031] Before introducing this service, the store was constantly short-staffed, with a high turnover of part-time staff. Part-time staff varied in many areas, including age, experience, contract content and duration, and level of understanding of the contract. As a result, the store manager's work was limited to simply informing the part-time staff and preparing the necessary paperwork. The store manager also had doubts about the franchise agreement, but didn't have time to check it, so he left it unattended. Furthermore, the store manager was too busy to focus on the tasks he should be doing, such as improving operations and supporting part-time staff. As a result, the store's sales remained flat, part-time staff were not retained, and the store manager was unable to do his job. This was a vicious cycle.

[0032] For example, the store manager had to handle all the administrative work for the store by himself, since everyone else was a part-time staff member. The store manager wanted to increase the number of part-time staff, but the management of them would be difficult, which was a problem for him. In addition, there were constant problems with part-time staff and contracts with the head office. For example, Mr. A complained, "I thought your hourly wage was going to increase soon?" Mr. B asked, "I'd like to take paid leave at the end of the year, but how many days of paid leave do I have left?" Mr. C claimed, "I'll do the work in the hall, but I won't do anything else because it's outside of my contract" (although in reality the contract calls for him to do other things as well), and Mr. D confessed, "I had a motorcycle accident." Many other issues were raised. However, all of these problems could be resolved if both parties had mutually understood the contents of the contract. However, before the introduction of this service, the traditional contract method was used. With the traditional contract method, there were individual contracts with many pages (each of which was very long and had a lot of characters) for each of A, B, C, and D. Therefore, it was very time-consuming and took a long time to find the parts of these contracts that were necessary to solve the problems for each of A, B, C, and D. In particular, when finding different conditions for two or more part-time staff, it was necessary to compare all of the contracts for each of the two or more part-time staff (which were very long and had a lot of characters), which required an even greater amount of time and effort. In this way, with the traditional contract method, the contracts that were signed with each part-time staff member were not being used, and were wasted.

[0033] Therefore, the store manager decided to introduce this service and conclude employment contracts with extended terms for each part-time staff member. In most cases, the traditional contracts for such stores are written in fixed language, with the exception of parameters such as hourly wages that should be individually determined. Therefore, the store manager can operate the terms and conditions presenter terminal 2 to access the server 1 (SaaS), create an invariable part KF with the "fixed text" attached as invariable information, and create a variable part KK with the "content (parameters) that should be individually determined, such as hourly wage" attached as variable information, thereby easily and quickly creating the terms and conditions KB (see example in Figure 2). In this example, since there was a "fixed text" in the existing contract, this was adopted as immutable information. However, creating new immutable information from scratch would be time-consuming and laborious for the restaurant manager (terms submitter KT). Therefore, this service provides templates of "fixed text" typically used in various industries and fields, such as small restaurants. By using these templates, the term submitter KT can easily and quickly add immutable information to the immutable part KF. Furthermore, the store manager (the person who proposes the terms and conditions KT) can clearly distinguish and see the parts that will be changed (i.e., the variable part KK) from the parts that will not be changed (i.e., the invariant part KF), making management easy. In particular, when reviewing the contract, the part that should be applied to all part-time staff can be modified by the invariant part KF, and the part that should be applied to each part-time staff can be modified by the variable part KK, which varies depending on the person, which is convenient for the store manager (the person who proposes the terms and conditions KT). Naturally, when concluding an employment contract with E, who will be hired next month, that is, when creating new terms and conditions K, the store manager (terms proposer KT) can reuse the invariant part KF from another part-time staff member (for example, A), and only add the variable part KK specifically for E after negotiation (in practice, E can enter it). In other words, creating new terms and conditions K can be done easily and quickly.

[0034] Furthermore, agreement information such as rules is stored and managed in the rules DB 51 for each part-time staff member. Therefore, the store manager can operate the terms and conditions presenter terminal 2 to access the server 1 (SaaS) to extract only the variable information of at least some of the part-time staff (terms and conditions agreeees KD) (for example, Mr. A, Mr. B, Mr. C, Mr. D, and Mr. E) from the terms and conditions DB 51, and easily view the list as shown in Figure 4. FIG. 4 shows an example of a list of the variable parts of the agreement information of multiple agreement acceptors managed by the service shown in FIG. The store manager can easily compare the different parts (variable information attached to the variable part KK) for each part-time staff member by simply operating the terms and conditions presenter terminal 2 to access the server 1 (SaaS) and visually viewing the list shown in Figure 4. In this way, the store manager can easily determine the areas that tend to cause trouble with each part-time staff member (variable information that indicates different conditions depending on the person).In addition, since the store manager can use this service on the cloud (SaaS), he can check it whenever he is concerned, and there is no risk of losing it like with paper contracts, so he can feel safe. In other words, by using this service, store managers will be able to centrally manage the employment contract details of part-time staff members, each with different conditions, thereby solving all of the problems mentioned above that arose with the traditional contract method. More specifically, for the store manager, this means fewer problems, and if any issues arise, they can refer back to the terms of the employment contract and make a decision, allowing them to resolve the issue immediately.As a result, they have more time and peace of mind, and can concentrate on their main duties.

[0035] In summary, by applying this service to employment contracts, the employer (the store manager in the example above) can stipulate the employment contract and manage only the content (variable information) that should be individually determined for each employee as "differences." This reduces the speed at which employment contracts are concluded, contributing to lower costs for the employer.

[0036] However, the application of this service is not limited to employment contracts, and can be applied to a wide variety of contracts.

[0037] For example, this service can be applied to a contract for ordering the creation of a website. For example, suppose a website is created by a freelance individual business owner who is contracted or commissioned by a business. In addition, although a detailed contract should be signed, the ordering party (business owner) has no intention of signing a contract. In such a case, the ordering party (business operator) may create the rules KB in step S1 of FIG. 3 as a rules presenter KT. On the other hand, a freelance individual business owner can simply follow steps S2 to S5 in FIG. 3 when submitting a quote to obtain mutual agreement on basic business terms. This allows the ordering party (business operator) to obtain consent, such as by regarding the freelance individual business owner as having agreed to the terms and conditions when placing an order. By obtaining consent under such terms and conditions, it is possible to eliminate work that does not constitute evidence, such as verbal promises.

[0038] For example, this service can also be adopted by corporate legal departments. In other words, when a company enters into a contract from scratch, the company's legal department or other relevant department needs to provide full support. Therefore, if a company's legal department, etc., can use this service to create regulations and collect consent logs, they will be able to treat part of the regulations as business conditions in the immutable part KF, and leave negotiations on the transaction conditions as variable information to the business department that actually deals with customers (have the business department attach it to the variable part KK). This will reduce legal costs and speed up contract signing. Furthermore, if a custom-made contract is required, existing electronic contract services (traditional contract methods) can be used, while this service can be used for other contracts that can be made into templates. Furthermore, the division of roles between legal issues, which should be handled by the legal department, and transaction terms, which should be handled by the business department, will become clearer, shortening the lead time until agreement and eliminating unnecessary internal coordination.

[0039] In this way, this service can improve convenience when entering into a contract with content appropriate for the parties (between the terms proposer KT and N terms acceptors KD) without relying on a contract document. Therefore, this service is best suited for use primarily by the legal department or legal personnel who are responsible for contracts. Furthermore, as this service expands, it is possible that the department in charge of communication design that connects with consumers will take control of the terms and conditions, etc. In this case, it would be ideal for the marketing department or similar department to use this service. Furthermore, this service can be targeted at everyone, from freelancers (sole proprietors) to small businesses and enterprises with a large number of one-to-many contracts.

[0040] Next, with reference to FIG. 5, a description will be given of the configuration of an information processing system that realizes the provision of the above-described service, that is, an information processing system to which the server 1 according to an embodiment of the information processing device of the present invention is applied. FIG. 5 is a diagram showing an example of the configuration of an information processing system to which a server according to an embodiment of the information processing device of the present invention is applied.

[0041] The information processing system shown in FIG. 5 is configured to include a server 1, a terms presenter terminal 2, and terms agreeer terminals 3-1 to 3-n (n is an integer value of 1 or more). The server 1, the terms presenter terminal 2, and the terms agreeer terminals 3-1 to 3-n are connected to one another via a predetermined network N such as the Internet.

[0042] The server 1 is an information processing device managed by the service provider S. The server 1 executes various processes for realizing this service by SaaS while appropriately communicating with the terms presenter terminal 2 and the terms agreeer terminals 3-1 to 3-n.

[0043] The terms presenter terminal 2 is an information processing device operated by the terms presenter KT. As described above, the terms presenter terminal 2 is configured as a personal computer, tablet, smartphone, etc. The terms presenter terminal 2, for example, accepts input operations of various information by the terms presenter KT and transmits it to the server 1 (SaaS), or receives and displays various information transmitted from the server 1 (SaaS). Note that although only one terms presenter terminal 2 is depicted in Figure 5, this is a simplification for ease of understanding. In reality, there may be as many terms presenter terminals 2 as there are terms presenters KT.

[0044] Each of the terms agreeer terminals 3-1 to 3-n is an information processing device operated by each of the n terms agreeers KD. As described above, the terms agreeer terminal 3 is configured as a personal computer, tablet, smartphone, or the like. In the following, when there is no need to distinguish between the individual contract agreement terminals 3-1 to 3-n, they will be collectively referred to as the "contract agreement terminal 3" as described above with reference to FIG. The terms and conditions consenter terminal 3, for example, accepts input operations of various information by the terms and conditions consenter KD and transmits the information to the server 1 (SaaS), or receives and displays various information transmitted from the server 1 (SaaS).

[0045] FIG. 6 is a block diagram showing an example of a hardware configuration of a server in the information processing system shown in FIG.

[0046] The server 1 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a bus 14, an input / output interface 15, an input unit 16, an output unit 17, a memory unit 18, a communication unit 19, and a drive 20.

[0047] The CPU 11 executes various processes according to a program recorded in the ROM 12 or a program loaded from the storage unit 18 into the RAM 13 . The RAM 13 also stores data and the like necessary for the CPU 11 to execute various processes.

[0048] The CPU 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output interface 15 is also connected to this bus 14. An input unit 16, an output unit 17, a memory unit 18, a communication unit 19, and a drive 20 are connected to the input / output interface 15.

[0049] The input unit 16 is configured with, for example, a keyboard and is used to input various information. The output unit 17 is configured with a display such as a liquid crystal display, a speaker, etc., and outputs various information as images and sounds. The storage unit 18 is configured with a DRAM (Dynamic Random Access Memory) or the like, and stores various data. The communication unit 19 communicates with other devices (for example, the terms presenter terminal 2 and terms agreeer terminals 3-1 to 3-n in FIG. 5) via a network N including the Internet.

[0050] Removable media 31, such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory, is appropriately attached to the drive 20. A program read from the removable media 31 by the drive 20 is installed in the storage unit 18 as necessary. Furthermore, the removable media 31 can also store various data stored in the storage unit 18 in the same manner as the storage unit 18.

[0051] Although not shown, the terms presenter terminal 2 and terms agreeer terminal 3 in Fig. 5 can also have a configuration that is basically similar to the hardware configuration shown in Fig. 6. Therefore, a description of the hardware configuration of the terms presenter terminal 2 and terms agreeer terminal 3 will be omitted.

[0052] 6, various processes including the agreement generation process, the agreement conclusion process, and the agreement confirmation process can be executed, and as a result, the above-described service can be provided. The "rules generation process" refers to a process of generating rules K based on the operation of the rules presenter KT on the rules presenter terminal 2. For example, in the example of Fig. 1 described above, the process of step S1 corresponds to the rules generation process. The "rules conclusion process" refers to a series of processes from when the rules agreeee KD agrees to the rules K generated by the rules generation process based on the rules agreeee KD's rules agreeee terminal 3, to when the rules agreement information is generated and stored in the rules DB 51. For example, in the example of Figure 1 above, the series of processes from steps S2 to S5 corresponds to the rules conclusion process. The "terms and conditions confirmation process" is a process in which at least a portion of the terms and conditions agreement information is displayed on the terms and conditions presenter terminal 2 or the terms and conditions agreeer terminal 3, and at least a portion of the terms and conditions agreement information is confirmed by the terms and conditions presenter KT or the terms and conditions agreeer KD. The following describes the functional configuration for executing the agreement generation process, agreement conclusion process, and agreement confirmation process executed in the server 1 of FIG. 6 that constitutes the information processing system of FIG.

[0053] FIG. 7 is a functional block diagram showing an example of the functional configuration of the server of FIG. 6 constituting the information processing system of FIG. 5, for executing the agreement generation process, the agreement conclusion process, and the agreement confirmation process.

[0054] As shown in FIG. 7, when the server 1 executes the rule creation process, a rule processing control unit 61 and a rule creation unit 62 function in the CPU 11. When the server 1 executes the agreement conclusion process, the CPU 11 further functions as a agreement processing control unit 61, a agreement providing unit 63, and a agreement management unit 64. When the server 1 executes the rule confirmation process, the CPU 11 causes a rule list presentation unit 65 and a rule search and extraction unit 66 to function.

[0055] The above-mentioned rules DB 51 is provided in one area of ​​the storage unit 18 of the server 1. The rules DB 51 stores and manages agreement information such as concluded rules for each version.

[0056] The agreement processing control unit 61 controls the execution of the agreement creation process, agreement conclusion process, and agreement confirmation process. That is, when executing the convention generation process, the convention processing control unit 61 puts the convention generation unit 62 into operation. When executing the agreement conclusion process, the agreement processing control unit 61 causes the agreement providing unit 63 and the agreement management unit 64 to function. When executing the rules confirmation process, the rules processing control unit 61 causes the rules list presentation unit 65 and the rules search and extraction unit 66 to function.

[0057] The rules generation unit 62 executes rules generation processing under the control of the rules processing control unit 61 . That is, the terms generation unit 62 generates a terms KB (see the example in Figure 3) that has, of the information required for a specified contract, an invariant part KF to which invariant information is attached, and a variable part KK to which variable information whose content changes through negotiation between the terms presenter KT and the terms agreeer KD.

[0058] The rules providing unit 63 and the rules management unit 64 execute rules conclusion processing under the control of the rules processing control unit 61 .

[0059] That is, the rules providing unit 63 provides the rules KB and a predetermined user interface to the rules agreeee terminal 3. The predetermined user interface accepts a variable information addition operation and an agreement operation. As described above, the variable information addition operation is an operation for attaching information indicating the result of negotiation between the terms presenter KT and the terms agreeer KD to the variable part as variable information. The consent operation is an operation for consenting to the rule K, as described above. Here, if the consent operation is an operation to have the agreement agreeee KD execute explicit consent, the agreement processing control unit 61 recognizes that explicit consent has been given by the agreement agreeee KD when the consent operation is accepted. On the other hand, if the consent operation is an operation that the agreement agreeee KD performs for a different purpose, the agreement processing control unit 61 recognizes that implicit consent has been given by the agreement agreeee KD when the agreement operation is accepted. Here, the form of consent operation is not particularly limited, and may be, for example, sending an email, pressing a number via telephone, voice input, or expressing one's intention using SMS, LINE (registered trademark), MESSENGER (registered trademark), Zoom (registered trademark), or other video call. Specific examples of a predetermined user interface for receiving such a variable information addition operation and an agreement operation will be described later with reference to FIGS.

[0060] When the above-mentioned consent operation is accepted, the regulations management unit 64 stores and manages information including the invariant information attached to the invariant part KF, the variable information attached to the variable part KK by the variable information addition operation, and personal identification information that can identify the regulations consenter KD in the regulations DB 51 as regulations etc. consent information. Here, the inclusion of person identification information in the agreement information for the terms and conditions means that an agreement log is obtained that identifies the person who agreed to the terms and conditions as the agreement agreeee KD. Furthermore, agreement information on rules and regulations can be said to be data that combines the variable part KK and the immutable part KF of rules K after separating them. Therefore, by implementing a user interface (one that displays the list described below) that extracts and displays the variable part KK, it is possible to clearly display the parts that are specific to the log (rules K) (i.e., the important parts). In this way, the agreement conclusion process is completed, and a predetermined contract based on the contents of the agreement K is concluded between the agreement presenter KT and the agreement agreeer KD. As explained above, by executing the contract conclusion process, it is possible to improve the convenience of concluding a contract with content appropriate for the parties (between the terms presenter KT and the terms accepter KD) without relying on a contract document.

[0061] For example, it is assumed that a set of rules and regulations (such as working conditions and confidentiality) exists for a given contract. In this case, when an agreement operation for a predetermined rule is received, the rule processing control unit 61 can recognize that the rule agreeee KD has agreed to the rule set. In this way, it becomes possible to realize a grouping function that allows consent to multiple terms and conditions to be obtained at once (for example, a function that allows consent to "working conditions" and "confidentiality" as a set).

[0062] Hereinafter, the state in which a predetermined contract is concluded will be referred to as a "contract state." On the other hand, a state in which the specified contract is no longer concluded due to a specified reason after the "contract state" is hereinafter referred to as a "no-contract state." There are three types of specified grounds for nullifying a contract: cancellation, termination, and consent termination, depending on the content of the specified contract. Termination means that when a predetermined event or breach of contract occurs, one party unilaterally (regardless of the other party's wishes) exercises the right to terminate the contract, thereby invalidating the contract from its inception. Termination means the future termination of a contract. Cancellation of consent (termination) refers to a new agreement (the content of which varies depending on the agreement) to invalidate the contract. In this service, the following steps are taken to change from a "contracted" state to a "non-contracted" state. That is, when an agreement operation is received for the first agreement for a specific contract, the agreement management unit 64 manages the specific contract as being in a "contracted state" in association with the agreement information for the contract, etc. In this case, when at least one of the terms proposer KT and the terms agreer KD wishes to enter into a "no contract state," the terms proposer KT and the terms agreer KD will negotiate a specific contract to enter into a "no contract state." In other words, first, an agreement is formed offline. Next, the terms and conditions generating unit 62 generates second terms and conditions for canceling, terminating, or terminating consent to a specific contract in accordance with the operation performed on the terms and conditions presenter terminal 2 by the terms and conditions presenter KT. The terms provision unit 63 provides the second terms and a user interface for accepting an agreement operation for agreeing to the second terms to the terms agreeee terminal 3. When the agreement operation for agreeing to the second agreement is accepted by the agreement agreeee terminal 3 from the agreement agreeee KD, the agreement management unit 64 manages the information on agreement to the agreement etc., indicating that the specified contract is in a "no contract state." As a result, the state of the specified contract transitions from "contracted state" to "non-contracted state."

[0063] The rules list presentation unit 65 and rules search and extraction unit 66 execute rules confirmation processing under the control of the rules processing control unit 61 .

[0064] For example, suppose there are multiple people (KD) who agree to the terms and conditions (in the example of the employment contract by the store manager mentioned above, there are a total of 10 people, including Mr. A, Mr. B, Mr. C, Mr. D, and Mr. E). In this case, the rules management unit 64 increments the version of the rules consent information each time one of the multiple rules consenters KD performs the consent operation, and stores and manages the rules consent information for each version in the rules DB 51. The terms and conditions list presentation unit 65 lists the contents of the variable information added to the variable part KK of the terms and conditions agreement information (for example, the employment period, person in charge, wage, probationary period, and holidays in Figure 4) and the terms and conditions agreeees identified by the person identification information (for example, Mr. A, Mr. B, Mr. C, Mr. D, and Mr. E in Figure 4) by version (for example, as shown in Figure 4) and presents it to the terms and conditions presenter terminal 2.

[0065] The terms and conditions search and extraction unit 66 searches for and extracts terms and conditions agreement information from the terms and conditions DB 51 based on a specified operation on the terms and conditions presenter terminal 2 by the terms and conditions presenter KT, or a specified operation on the terms and conditions agreeer terminal 3 by the terms and conditions agreeer KD, and controls the transmission of the information to the terms and conditions presenter terminal 2 or the terms and conditions agreeer terminal 3. Here, the form of transmission is not particularly limited, and can be email, telephone, SMS, LINE (registered trademark), MESSENGER (registered trademark), Slack (registered trademark), video calls such as Zoom (registered trademark), etc.

[0066] Next, with reference to FIGS. 8 to 11, a concrete example of the terms KB and a predetermined user interface displayed on the terms agreeer terminal 3 will be described.

[0067] 8 and 9 show an example of a website production contract as a specific example of the terms and conditions and a predetermined user interface displayed on the terminal of the person who agrees to the terms and conditions.

[0068] The upper portions of FIGS. 8 and 9 show the variable part KK of the rules KB and a user interface KIF for accepting variable information addition operations. The variable information to be attached (entered) to the variable part KK includes the client, the business content (as defined in Article 2, Paragraph 1 of the immutable information), the business commission fee (excluding consumption tax), matters related to subcontracting (as defined in Article 11 of the immutable information), liability for non-compliance with the contract (as defined in Article 13 of the immutable information), the validity period, and any special notes.

[0069] Here, the client and the first part of the work content, "Creation of Dayz Co., Ltd.'s homepage (corporate website)", are attached (input) by the terms and conditions presenter KT (here, Dayz Co., Ltd.) when generating the terms and conditions KB (corresponding to step S3KT in step S1 of Figure 3).

[0070] As a user interface KIF for adding the expected number of pages of the business content, a pull-down menu that allows the user to select a desired number from a plurality of numbers is displayed on the terminal 3 of the agreement agreeee to the agreement, and is presented to the agreement agreeee KD. As a user interface KIF for selecting whether or not to include in the scope of work the following services: homepage design, content creation within the homepage, server construction, and domain acquisition and configuration, radio buttons (options to select only one) indicating "Include," "Do not include," and "Other (specified in special notes)" are displayed on the Terms and Conditions Acceptor Terminal 3 and presented to the Terms and Conditions Acceptor KD. As part of the business content, a user interface KIF for selecting the browser to perform the performance test is provided to the terms and conditions consenter KD by displaying radio buttons (multiple selectable options) indicating each of the various browsers on the terms and conditions consenter terminal 3.

[0071] As a user interface KIF for determining the outsourcing fee (excluding consumption tax), an input box in which the agreement consenter KD can freely write is displayed on the agreement consenter terminal 3 and presented to the agreement consenter KD.

[0072] As a user interface KIF for determining matters related to subcontracting (Article 11), radio buttons (options to select only one) indicating "Subcontracting requires Party A's prior consent" and "Party B may subcontract at its own risk" are displayed on the Terms and Conditions Acceptor Terminal 3 and presented to the Terms and Conditions Acceptor KD.

[0073] As a user interface KIF that determines the starting point of liability for non-conformity of the contract (Article 13), radio buttons (options to select only one) indicating "From the date Party A becomes aware of the non-conformity" and "From the date inspection and repair is completed" are displayed on the Terms Acceptor Terminal 3 and presented to the Terms Acceptor KD. As a user interface KIF for determining the period of liability for non-conformity with the contract (Article 13), radio buttons (options to select only one) indicating each of the three periods and an input box for entering a specific period (numerical value) are displayed on the Terms Acceptor Terminal 3 and presented to the Terms Acceptor KD.

[0074] As a user interface KIF for determining the validity period (Article 17), an input box for inputting a specific period (numerical value) is displayed on the agreement consenter terminal 3 and presented to the agreement consenter KD.

[0075] As a user interface KIF for inputting special notes, an input box in which the agreement consenter KD can freely write is displayed on the agreement consenter terminal 3 and presented to the agreement consenter KD. In addition, there may be special notes that are added (input) in advance by the terms presenter KT (here, Dayz Co., Ltd.) when the terms KB is generated (corresponding to the content of the negotiation in step S3KT in step S1 of Figure 3).

[0076] An operation of inputting various kinds of variable information into such a user interface KIF is an example of a variable information adding operation. After completing the variable information addition operation, the agreement agreeee KD can view the invariant information attached to the invariant part KF shown at the bottom of Figure 9 by scrolling the screen of the agreement agreeee terminal 3, etc. After viewing the immutable information attached to the immutable part KF, the agreement consenter KD can press the consent button DBM as a consent operation. Here, the terms and conditions agreeer KD visually recognizes the word "Agree" displayed on the agreement button DBM and then presses the agreement button DBM. In other words, the operation of pressing the agreement button DBM is an example of an operation of explicit agreement.

[0077] When such consent operation is accepted, the regulations management unit 64 stores and manages the information including the invariant information attached to the invariant part KF at the bottom of Figure 9, the variable information attached to the variable part KK at the top of Figures 8 and 9, and personal identification information that can identify the regulations consenter KD in the regulations DB 51 as regulations etc. consent information. This completes the agreement conclusion process, and a predetermined contract is concluded between the agreement presenter KT and the agreement agreeer KD according to the contents of the agreement K shown in FIGS.

[0078] 10 and 11 show examples of employment contracts as specific examples of the terms and conditions and predetermined user interfaces displayed on the terminal of the person who agrees to the terms and conditions.

[0079] FIG. 10 shows the variable part KK of the rules KB and a user interface KIF for accepting variable information addition operations. The variable information to be added (entered) in the variable section KK includes: 1. employee name, 2. employee address, 3. employment period, 4. whether renewal is planned, 5. place of work, 6. job content, 7. start time, 8. end time, 9. working days, and 10. monthly wage.

[0080] As a user interface KIF for inputting 1. the employee name and 2. the employee address, an input box in which the agreement consenter KD can freely write is displayed on the agreement consenter terminal 3 and presented to the agreement consenter KD.

[0081] 3. As a user interface KIF for determining whether or not the employment term is fixed, radio buttons (options to select only one) indicating whether or not the term is fixed are displayed on the terms and conditions consenter terminal 3 and presented to the terms and conditions consenter KD. Then, only if "Yes" is selected in 3, radio buttons indicating "Yes" and "No" (options to select only one) are displayed on the terms and conditions consenter terminal 3 and presented to the terms and conditions consenter KD as a user interface KIF for deciding whether or not to renew 4.

[0082] 5. As a user interface KIF for selecting a place of work, a pull-down menu that allows the user to select a desired place from a plurality of places is displayed on the terminal 3 of the person who agrees to the terms and conditions and is presented to the person who agrees to the terms and conditions KD.

[0083] 6. As a user interface KIF for determining the business content, an input box in which the agreement consenter KD can freely write is displayed on the agreement consenter terminal 3 and presented to the agreement consenter KD.

[0084] As a user interface KIF for determining 7. start time and 8. end time, a pull-down menu that allows the user to select the desired time (number) from multiple times (numbers) is displayed on the terms and conditions consenter terminal 3 and presented to the terms and conditions consenter KD.

[0085] 9. As a user interface KIF for selecting working days, radio buttons (multiple options available) indicating each of Sunday through Saturday are displayed on the agreement agreeee terminal 3 and presented to the agreement agreeee KD.

[0086] 10. As a user interface KIF for determining the monthly wage, an input box in which the agreement consenter KD can freely write is displayed on the agreement consenter terminal 3 and presented to the agreement consenter KD.

[0087] An operation of inputting various kinds of variable information into such a user interface KIF is an example of a variable information adding operation. After completing the variable information addition operation, the agreement agreeee KD can view the invariant information added to the invariant part KF shown in FIG. 11 by scrolling the screen of the agreement agreeee terminal 3, for example. After viewing the immutable information attached to the immutable part KF, the agreement consenter KD can press the next button DBA as a consent operation. Here, the agreement agreeee KD visually recognizes the words "Next" displayed on the Next button DBA and presses the agreement button DBA with the intention of transitioning to the next screen, etc. (i.e., for another purpose). However, transitioning to the next screen, etc. after viewing the immutable information can be understood as implicit agreement to the contents of the agreement shown in Figures 10 and 11. That is, the operation of pressing the next button DBA is an example of an operation of implicit consent.

[0088] When such consent operation is accepted, the regulations management unit 64 stores and manages information including the invariant information attached to the invariant part KF of Figure 11, the variable information attached to the variable part KK of Figure 10, and personal identification information that can identify the regulations consenter KD in the regulations DB 51 as regulations etc. consent information. This completes the agreement conclusion process, and a predetermined contract is concluded between the agreement presenter KT and the agreement agreeer KD according to the contents of the agreement K shown in FIGS.

[0089] Next, a second embodiment will be described. After the contract is concluded, there are seven possible states for the contract, for example: 1. "Active" (during the initial period), 2. "Active" (currently being automatically renewed), 3. "Active" (currently being manually renewed), 4. "Contract period expired" (automatic), 5. "Agreed termination" (consent required), 6. "Cancellation / cancellation" (can be set unilaterally by the administrator), and 7. "Contents changed" (consent required). However, these statuses generally cannot be determined simply by referring to the original contract, whether it is paper or electronic, and it is difficult to understand the correct contract status without also referring to the accompanying information.

[0090] For example, a contract exists on paper with a signature and seal, and the intention to terminate the contract is expressed by email. A contract is concluded electronically, but later it becomes necessary to change the contents of the contract, and a new memorandum for the change is concluded electronically. In such cases, if the original contract and actions taken after the original contract was concluded (in the above case, the email expressing the intention to terminate and the amendment memorandum concluded electronically) are linked together and managed in some way, it is possible to manage the status of the series of contracts. On the other hand, if no special measures are taken and this linking is not made, there is a risk that when a person other than the parties to the contract later checks the series of contracts in question, they may refer only to the original contract, for example, and make an incorrect judgment about the status of the contract.

[0091] Therefore, in the second embodiment, a function for managing the alive or dead state of a contract is provided in the configuration of the first embodiment (see FIG. 7). Hereinafter, a second embodiment of the server of the information processing device according to the present invention will be specifically described with reference to FIGS. FIG. 12 is a diagram showing the functional configuration of a server of the second embodiment of the information processing device according to the present invention. FIG. 13 is a diagram showing a detailed configuration of a survival status management unit in the functional configuration of the server shown in FIG. In the second embodiment, when the server 1 executes a process for managing the survival status of the rules, a survival status management unit 67 functions as shown in Fig. 12. In Fig. 12, the same elements as those in the functional configuration of Fig. 7 are assigned the same reference numerals, and the description thereof will be omitted.

[0092] When the operation of the functional configuration shown in Figure 7 is applied to "Contract A" in Figure 13, when a specific contract such as "Contract A" shown in Figure 13 is concluded, a consent request is made from the terms presenter KT to the terms agreeer KD (step S11), and if the terms agreeer KD agrees to this consent request (step S12), the consent information for the concluded terms etc. is stored in the terms DB51.

[0093] In this case, the survival status management unit 67 manages which of a plurality of statuses the status of "Contract A" is, including an active "contract status" and an inactive "no contract status." For example, the survival status management unit 67 monitors the current status of the concluded "Contract A" and monitors the status of the "Contract A" by controlling the maintenance or transition of the status of the "Contract A" based on the monitoring results. Specifically, the survival status management unit 67 checks the agreement information such as the terms and conditions of the concluded "Contract A" stored for each target person (terms presenter KT and term agreeer KD) in the terms and conditions DB 51 at a predetermined timing such as at startup or constantly. The contents of the check include, for example, whether the contract period of the concluded terms and conditions has expired, whether it has been renewed, whether there has been a change in the contract contents, whether the contract has been terminated, etc.

[0094] As a specific functional configuration of the life status management unit 67, as shown in FIG. 13, an automatic status determination unit 71, an automatic update unit 72, a period change unit 73, an update unit 74, a cancellation unit 75, etc. function.

[0095] The automatic status determination unit 71 determines the contract status of "Contract A" based on the contract period. Specifically, the automatic status determination unit 71 references the contract period in the agreement information of the target person's "Contract A" such as the terms and conditions stored in the terms and conditions DB 51, and automatically compares the contract period with the check date to determine whether the contract is active (the contract status is maintained) or inactive (the contract period has expired). Then, the automatic status determination unit 71 manages the status by reflecting the determination result in the status flag of the relevant item (item of contract status) in, for example, a status management table stored in the regulations DB 51. In the example of Fig. 13, the status is automatically deactivated on the contract expiration date. For example, if it is in an active state, the status flag is maintained at "1," and if it is inactive, the status flag is changed to "0," etc. Note that although flags of "1" and "0" are used here as an example of status management, other flags may also be used.

[0096] The automatic renewal unit 72 executes automatic renewal processing of the contract period based on the contract period automatic renewal flag. Specifically, the automatic renewal unit 72 references the automatic renewal flag in the target person's agreement information on the terms and conditions, etc., stored in the terms and conditions DB 51, and automatically renews the contract period if a valid automatic renewal flag is set. In the example of Figure 13, if there is no agreement to terminate the contract on the contract expiration date, the contract is automatically renewed.

[0097] The period change unit 73 executes a process for changing the contract period instructed by a manual operation. Specifically, when the period change unit 73 executes a change to the contract period in response to a contract period change operation by the terms presenter KT on the terms presenter terminal 2, it transmits a request for consent to the contract period change to the terms agreeer terminal 3, and executes the contract period renewal process after obtaining consent to the contract period change from the terms agreeer KD as well. In the example of Fig. 13, it is also possible to change or shorten the contract period, for example by extending the contract end date by one year.

[0098] The update unit 74 changes the contract contents by manual operation. Specifically, when the update unit 74 changes the contract contents in response to a change operation of the contract contents by the terms presenter KT at the terms presenter terminal 2, the update unit 74 transmits a request for consent to the contract contents change to the terms agreeer terminal 3, and executes the contract contents change process after obtaining consent to the contract contents change from the terms agreeer KD as well. A log (history) of the results of the contract change process is stored in the contract DB 51. As a log, the new contract (such as "Contract A'" in FIG. 13) is managed as a separate contract from the original contract (such as "Contract A"), and the original contract (such as "Contract A") is deactivated.

[0099] The cancellation unit 75 executes processing to cancel the contract by manual operation. Specifically, when canceling the contract in response to a contract cancellation operation by the terms provider KT at the terms provider terminal 2, the cancellation unit 75 transmits a request for consent to the change of the contract contents to the terms agreeer terminal 3, receives a reply of consent from the terms agreeer KD, and executes the contract cancellation processing after obtaining consent to the contract cancellation from the terms agreeer KD. In the example of FIG. 13, the "Terms A" is deactivated when the contract is canceled by the cancellation unit 75. Furthermore, the cancellation unit 75 executes a process of forcibly canceling / cancelling the contract through manual operation. Specifically, when a violation of the contract is confirmed and the contract is to be cancelled, the cancellation unit 75 executes a process of changing the contract status to "cancelled / cancelled" in response to a manual operation by the terms presenter KT in the terms presenter terminal 2. In this case, consent from the terms agreeer KD is not required. In addition, the status of the contract after conclusion, managed by each of the above-mentioned parts as being active or inactive, may be displayed on a status management screen or the like for each of the seven states "1." to "7." above, an alarm may be issued for each change in status when a change in status is detected, and the status of each state may be displayed in response to a display operation by the user (at the user's request).

[0100] According to the second embodiment, the state of the contract after the contract is concluded is systematically managed as a status indicating which of multiple states, including active or inactive, the state is, so that users such as the terms and conditions presenter KT can correctly understand the state of the contract. To give an example, when terms and conditions are created in PDF format, it can be difficult to determine whether the contract is valid or invalid in cases where the contract period has already expired or the terms and conditions have been overwritten midway through the contract, which can lead to incorrect understanding. However, by managing the contract's validity status as described above, users can correctly understand the status of the contract. The function of managing the contract status as described above can be applied not only to extended contracts having variable parts but also to general contracts, and can also be applied to contracts.

[0101] In addition, it is possible to print out the terms and conditions, the status of each state, etc., or output them as a PDF file. Also, timestamp authentication can be performed on the DB dump (daily differential). In addition, from a business perspective, insurance may be taken out against the regulations.

[0102] Although one embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and modifications, improvements, etc. within the scope of achieving the object of the present invention are considered to be included in the present invention.

[0103] For example, in the above embodiment, the explanation was given using rules as an example, but as mentioned above, this applies to all rules and the like.

[0104] Furthermore, for example, the location where the terms and conditions to which this service applies are presented is merely an example in the above embodiment, and various other locations can be adopted as follows. Specifically, for example, the consent process may be bundled when digital documents such as proposals, purchase orders, estimates, invoices, and delivery notes are issued or sent / received as online presentation locations. Also, for example, the consent process may be bundled when a transfer of funds occurs or is completed in a financial account such as a bank, securities, or insurance account. For example, after receiving a job offer on a job site or the recruitment page of a company or organization, the process of agreeing to working conditions and confidentiality in accordance with regulations, etc. may be linked to this service.

[0105] In the above embodiment, an example of a terms consenter terminal 3 was described as an information processing device operated by the terms consenter KD, but consent may also be given at a terminal installed in a convenience store, for example. Furthermore, for example, "where" (or "when") consent is obtained is not limited to the above-described embodiment, and as described above, it is sufficient if the form is such that it is possible to switch between an ON state of a switch indicating a contracted state and an OFF state of a switch indicating no contracted state, and various forms can be adopted, such as online, offline that is close to digital, IoT, metaverse, etc. Specifically, for example, the timing can be when a smart lock is unlocked or when entering or exiting through a door. The timing can be when the power is plugged in (i.e., when power is supplied). The timing can be when the ignition of a car is turned on or off. In a taxi, the timing can be when the car door is opened or when the person gets in. The timing can be when the purchase button on a vending machine is pressed. The timing can be when the person passes through a ticket gate at a station. The timing can be when a phone call is made or received (when the person presses the dial button). The timing can be when the person is photographed by a camera (when the person appears as a subject in a still or video). The timing can be when the person turns on a faucet. The timing can be when a reservation is made on a reservation website. The timing can be when a unique domain (e.g., an IP address) is accessed. The timing can be when verbal consent is given during a video call. The timing can be when the conversation on the video conferencing system is automatically transcribed after the video call ends, and consent is obtained when the person leaves the room. The timing can be when biometric authentication, such as facial recognition, fingerprint recognition, voiceprint recognition, or iris recognition, is performed. By using the timing of biometric authentication, issues of identity can be resolved. It can be used when shaking hands, fist bumping, or high-fiving. It can be used when sending emojis in chat. It can be used when issuing or sending files such as estimates.

[0106] Furthermore, for example, the application of this service is not limited to the above-described embodiment, and this service can be applied to a variety of businesses. For example, this service can be widely applied to businesses based on consent logs for terms and conditions (consent information for terms and conditions, etc.) (businesses that combine legal and financial services). Specifically, for example, this service can be applied to a business (hereinafter referred to as "Business A") that collects and pays receivables by shortening or extending loan contracts and payment terms after confirming agreement, consent formation, and the existence of receivables in terms and conditions, etc. For example, this service can be applied to a business (hereinafter referred to as "Business B") that enters into an insurance contract after confirming consent, consent formation, and the existence of a claim in terms and conditions, etc. This service can also be applied when the database is made available to a third party in order to carry out business A or business B, and consent to this is obtained from users of this service. Furthermore, this service can be applied to businesses that acquire figures for potential liabilities (contingent liabilities) arising from agreements or consent formation in terms and conditions, etc. Specifically, in the case of a recruitment agency, this service can be applied to businesses that acquire information such as the number (amount) of dismissals (refunds) during the probationary period, or the number (amount) of contracts for which liability exists. For example, this service can be applied to businesses that segment users based on terms and conditions and conduct A / B testing on users. In other words, traditionally, the terms and conditions agreed to for a web service are the same, but in order to make adjustments to the service, the service provider provides a tuned screen to only a portion of users, measures the degree of impact, and conducts AB testing. The question arises as to whether it is acceptable to run AB tests silently without obtaining user consent or paying any commercial compensation. This service can be applied to solve such problems. For example, if user consent is covered by terms and conditions, create attributes of consenting users that are grouped from the beginning so that AB testing can be performed in accordance with the original terms and conditions. Then, separating the attributes by terms and conditions makes it easier to perform AB testing on those users.

[0107] Furthermore, the system configuration shown in FIG. 5 and the hardware configuration of the server 1 shown in FIG. 6 are merely examples for achieving the object of the present invention, and are not particularly limited.

[0108] Furthermore, the functional block diagram shown in Fig. 7 is merely an example and is not particularly limited. That is, it is sufficient if the information processing system in Fig. 5 is provided with a function that can execute the above-described processing as a whole, and the functional blocks and databases used to realize this function are not particularly limited to the example in Fig. 7.

[0109] Furthermore, the locations of the functional blocks and databases are not limited to those shown in FIG. 7 and may be arbitrary. In the example of FIG. 7, all processes are configured to be performed under the control (SaaS) of the CPU 11 of the server 1 of FIG. 6 that constitutes the information processing system of FIG. 5, but the present invention is not limited to this. For example, at least some of the functional blocks and databases arranged on the server 1 side may be provided on the terms presenter terminal 2 side, the terms acceptor terminal 3 side, or another information processing device (not shown).

[0110] The above-described series of processes can be executed by hardware or software. Furthermore, one functional block may be configured as a single piece of hardware, a single piece of software, or a combination thereof.

[0111] When a series of processes is executed by software, the programs that make up the software are installed into a computer or the like from a network or a recording medium. The computer may be a computer built on dedicated hardware. The computer may also be a computer capable of executing various functions by installing various programs, such as a server, a general-purpose smartphone, or a personal computer.

[0112] The recording medium containing such a program may be composed not only of a removable medium (not shown) that is distributed separately from the device main body in order to provide the program to the user, but also of a recording medium that is provided to the user in a state that is pre-installed in the device main body.

[0113] In this specification, the steps describing the program to be recorded on the recording medium include not only processes that are performed in chronological order, but also processes that are not necessarily performed in chronological order but are performed in parallel or individually.

[0114] To sum up, the information processing device to which the present invention is applied is sufficient as long as it has the following configuration, and can take on a variety of different embodiments. That is, an information processing device to which the present invention is applied (for example, the server 1 in FIG. 5) An information processing device that communicates with a first terminal (e.g., the terms presenter terminal 2 in FIG. 3 or FIG. 5) operated by a terms presenter (e.g., the terms presenter KT in FIG. 3) who presents terms and conditions related to a predetermined contract, and a second terminal (e.g., the terms agreeer terminal 3 in FIG. 3 or FIG. 5) operated by a terms agreeer (e.g., the terms agreeer KD in FIG. 3) who concludes the predetermined contract with the terms presenter by agreeing to the terms and conditions, a rules generating means (for example, rules generating unit 62 in FIG. 7) for generating rules (for example, rules KB in FIG. 3) having an invariable part (for example, invariable part KF in FIG. 2) to which first information (for example, the above-mentioned invariable information) whose content is invariable is attached, and a variable part (for example, variable part KK in FIG. 2) to which second information (for example, the above-mentioned variable information) whose content changes depending on negotiation between the rules proposer and the rules agreeer; a terms provision means (e.g., the terms provision unit 63 in FIG. 7) that provides the second terminal with a user interface (e.g., the user interface KIF in FIGS. 8, 9, and 10) that accepts a first operation (e.g., the variable information addition operation described above) for attaching the terms, etc. and the negotiation result between the terms proposer and the terms agreeer to the variable part as the second information, and a second operation (e.g., the agreement operation described above) for agreeing to the terms, etc.; a rules management means (e.g., rules management unit 64 in FIG. 7) that, when the second operation is accepted, stores and manages information including the first information attached to the immutable part, the second information attached to the variable part by the first operation, and person identification information that can identify the person who agreed to the rules in a predetermined database (e.g., rules DB 51 in FIG. 7) as rules and other agreement information; Equipped with. This improves convenience when the parties (between the terms proposer KT and the terms acceptor KD) enter into a contract with content appropriate for them without relying on a written contract.

[0115] There are multiple people who agree to the terms and conditions (for example, in the example above where an employment contract is concluded with the store manager, there are 10 people, including A, B, C, D, and E). the rules management means increments the version of the agreement information for the rules, etc., each time any one of the plurality of agreement persons performs the second operation, and stores and manages the agreement information for the rules, etc., for each version in the predetermined database; A terms and conditions content presentation means (for example, the terms and conditions list presentation unit 65 in FIG. 7) that lists the content of the second information (for example, the employment period, person in charge, wage, trial period, and holidays in FIG. 4) and the terms and conditions consenters (for example, Mr. A, Mr. B, Mr. C, Mr. D, and Mr. E) identified by the person identification information among the terms and conditions consent information for each version and presents the list (for example, presents the list in FIG. 4) on the first terminal. The sensor may further include:

[0116] A search and extraction means (e.g., the rules search and extraction unit 66 in FIG. 7) that searches and extracts the agreement information from the predetermined database based on a predetermined operation on the first terminal by the rules presenter or a predetermined operation on the second terminal by the rules agreeer and executes control to transmit the information to the first terminal or the second terminal. The sensor may further include:

[0117] a contract processing control means (e.g., a contract processing control unit 61 in FIG. 7) that controls the execution of a series of processes from when the contract provision means provides the second terminal with the contract, etc. and the user interface, to when the second operation is accepted and the contract, etc. agreement information is stored in the predetermined database (e.g., the processes from steps S2 to S5 in FIG. 3, the above-mentioned "contract conclusion process"); The sensor may further include:

[0118] The second operation is an operation for making the person who agrees to the terms execute explicit agreement (for example, pressing the agreement button DBM in FIG. 9), When the second operation is accepted, the agreement processing control means can recognize that explicit agreement has been given by the agreement agreeee.

[0119] The second operation is an operation that the person who agrees to the terms and conditions performs for another purpose (for example, pressing the Next button DBA in FIG. 11 ), When the second operation is accepted, the agreement processing control means can recognize that implicit agreement has been given by the agreement agreeee.

[0120] When the second operation is accepted for the first contract etc. of the predetermined contract, the rules management means further manages the fact that the predetermined contract is in a "contracted state" in association with the agreement information of the rules etc., As a process for making the specified contract into a "no contract state," The rules generation means generates second rules or the like for terminating, cancelling, or terminating the specified contract, the terms and conditions providing means provides the second terminal with the second terms and conditions and a user interface that accepts the second operation for agreeing to the second terms and conditions, and When the second operation is accepted for the second contract, the agreement management means manages the fact that the predetermined contract is in a "no contract state" in association with the agreement information for the contract, etc. It is possible.

[0121] For the specified contract, there exists a set of rules and regulations consisting of the rules and regulations and one or more other rules and regulations, When the second operation is accepted, the rules processing control means can recognize that the rules agreeee has agreed to the set of rules, etc.

[0122] a contract state management means (e.g., the existence state management unit 67 in FIG. 13 ) for managing which of a plurality of states including the “contract state” (active) and the “no contract state” (inactive) the state of the predetermined contract (e.g., Contract A in FIG. 13 ); It can be equipped with:

[0123] The contract status management means (for example, the existence status management unit 67 in FIG. 13) monitoring the current state of the predetermined contract, and controlling the maintenance or transition of the state of the predetermined contract based on the monitoring result, thereby monitoring the state of the predetermined contract; It is possible. [Explanation of symbols]

[0124] 1. Server, 2. Terms presenter terminal, 3, 3-1 to 3-n. Terms acceptor terminal, 11. CPU, 12. ROM, 13. RAM, 14. Bus, 15. Input / output interface, 16. Input unit, 17. Output unit, 18. Storage unit, 19. Communication unit, 20. Drive, 31. Removable media, 51. Terms DB, 61. Terms processing control unit, 62. Terms generation unit, 63 ···Term provider, 64···Term management unit, 65···Term list presentation unit, 66···Term search and extraction unit, 67···Lifetime status management unit, 71···Automatic status determination unit, 72···Automatic update unit, 73···Term change unit, 74···Update unit, 75···Cancellation unit, KF···Invariant part, KK···Variable part, KT···Term presenter, KD···Term acceptor, KB···Terms, KIF···User interface, DBM···Agreement button

Claims

[Claim 1] An information processing device that communicates with a first terminal operated by a terms presenter who presents terms, etc., which are at least any one of terms, conditions, regulations, and rules related to a predetermined contract, and a second terminal operated by a terms accepter who concludes the predetermined contract with the terms presenter by agreeing to the terms, etc. a rules generation means for generating rules and the like having an invariant portion to which first information whose content is invariant is attached and a variable portion to which second information whose content is variable through negotiation between the rules proposer and the rules acceptor, among the information necessary for the predetermined contract; a terms provision means for providing the second terminal with the terms, etc., and a user interface for accepting a first operation by the terms acceptor to input the results of negotiation between the terms proposer and the terms acceptor into the variable portion as the second information, and a second operation for agreeing to the terms, etc.; a rules management means for, when the second operation is accepted, storing and managing information including the first information attached to the immutable part, the second information attached to the variable part by the first operation, and personal identification information capable of identifying the person who agreed to the rules in a predetermined database as rules agreement information; An information processing device comprising:

Citation Information

Patent Citations

  • Contract alteration preventing system, and contract alteration preventing method

    JP2006285592A