Program, information processing method, and information processing apparatus

Abstract

To provide a program and the like that can register a rule to be notified and the reason or the process of the rule.SOLUTION: A program according to one aspect causes a computer to execute processing of receiving input of a rule to be notified and the reason or the process of the rule, and storing the received rule and reason or process in a storage unit in association with each other. This makes it possible to register the rule to be notified and the reason or the process of the rule.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a program, an information processing method, and an information processing device. [Background technology]

[0002] In recent years, there has been active development of systems that support business-related rules, issues (problems), discussions, etc. For example, Patent Document 1 discloses an improvement information management system that considers measures to deal with new problems by referring to measures to deal with past problems in a database that stores improvement information data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2023-059114 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention of Patent Document 1 has a problem in that it is not possible to register the rules to be notified and the reasons or background for the rules.

[0005] One aspect of the present invention is to provide a program or the like that can register notification rules and the reasons or circumstances for the rules. [Means for solving the problem]

[0006] A program according to one aspect causes a computer to execute a process of accepting input of a rule to be notified and a reason or history for the rule, and storing the accepted rule and the reason or history in a memory unit in association with each other. [Effects of the Invention]

[0007] In one aspect, it is possible to register rules for notification and the reasons or circumstances for the rules. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram illustrating an overview of a rule registration system. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of a server. [Figure 3] FIG. 10 is an explanatory diagram illustrating an example of a record layout of a rule DB. [Figure 4] FIG. 2 is a block diagram showing an example of the configuration of a manager terminal and an employee terminal. [Figure 5] FIG. 10 is an explanatory diagram illustrating a rule registration (storage) process and a notification transmission process. [Figure 6] FIG. 10 is an explanatory diagram showing an example of a new notification creation screen. [Figure 7] 10 is a flowchart showing a processing procedure for registering a notification rule. [Figure 8] 10 is a flowchart showing a processing procedure when a registered rule is notified. [Figure 9] 10 is a flowchart showing a processing procedure when access information to a rule corresponding to basis information is output. [Figure 10] FIG. 10 is a block diagram showing an example of the configuration of a server in the second embodiment. [Figure 11] FIG. 10 is an explanatory diagram illustrating a process of outputting a dialogue based on a discussion model. [Figure 12] 10 is a flowchart showing a processing procedure for outputting a conversation between a supporter avatar and an opponent avatar. [Figure 13] 10 is a flowchart showing a processing procedure when a response by a minority avatar is output. [Figure 14] 10 is a flowchart showing a processing procedure for extracting a rule and a reason or a process. DETAILED DESCRIPTION OF THE INVENTION

[0009] The present invention will be described in detail below with reference to the drawings showing embodiments thereof.

[0010] (Embodiment 1) The first embodiment relates to a form of registering rules to be notified and the reasons or background of the rules. The rules are business operation rules or legal amendments of each department that are notified when issuing internal notices, formulating rules, registering business, updating business content, or at meetings (e.g., national councils), etc. Notification methods include methods that other users (e.g., employees) can access, such as publishing on an internal information sharing site, email, or using a social networking service (SNS) application. SNSs include LINE (registered trademark), Twitter (registered trademark), Instagram (registered trademark), Facebook (registered trademark), etc.

[0011] 1 is an explanatory diagram showing an overview of a rule registration system. The system of this embodiment includes an information processing device 1, an information processing terminal 2, and an information processing terminal 3, and each device transmits and receives information via a network N such as the Internet.

[0012] The information processing device 1 is an information processing device that processes, stores, transmits, and receives various types of information. The information processing device 1 is, for example, a server device, a personal computer, or a general-purpose tablet PC (personal computer). In this embodiment, the information processing device 1 is assumed to be a server device, and will be referred to as server 1 below for simplicity.

[0013] The information processing terminal 2 is a terminal device for a person in charge that receives and transmits input of rules and the reasons or background for the rules. The information processing terminal 2 is an information processing device such as a wearable device such as a smartphone, a mobile phone, or a smartwatch, a tablet, or a personal computer terminal. For simplicity, the information processing terminal 2 will be referred to as the person in charge terminal 2 below.

[0014] The information processing terminal 3 is a terminal device for employees that receives and displays rules and the reasons or background for the rules. The information processing terminal 3 is an information processing device such as a wearable device such as a smartphone, a mobile phone, or a smartwatch, a tablet, or a personal computer terminal. For simplicity, the information processing terminal 3 will be referred to as the employee terminal 3 below.

[0015] The server 1 according to this embodiment accepts input of a rule to be notified and the reason or background of the rule through the manager terminal 2. The server 1 stores the accepted rule and the reason or background in a storage unit in association with each other.

[0016] 2 is a block diagram showing an example of the configuration of the server 1. The server 1 includes a control unit 11, a storage unit 12, a communication unit 13, a reading unit 14, and a large-capacity storage unit 15. Each component is connected by a bus B.

[0017] The control unit 11 includes an arithmetic processing device such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field Programmable Gate Array), a DSP (Digital Signal Processor), or a quantum processor. The control unit 11 reads and executes a control program 1P (program product) stored in the storage unit 12, thereby performing various information processing and control processing related to the server 1.

[0018] The control program 1P can be deployed to run on a single computer, or on multiple computers located at one site, or distributed across multiple sites and interconnected by a communications network. While the control unit 11 is illustrated in FIG. 2 as a single processor, it may also be a multiprocessor.

[0019] The storage unit 12 includes memory elements such as RAM (Random Access Memory) and ROM (Read Only Memory), and stores the control program 1P or data required for the control unit 11 to execute processing. The storage unit 12 also temporarily stores data required for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing communication-related processing, and transmits and receives information to and from the manager terminal 2 or employee terminal 3, etc., via the network N.

[0020] The reading unit 14 reads a portable storage medium 1a including a CD (Compact Disc)-ROM or a DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 14 and store it in the mass storage unit 15. Alternatively, the control unit 11 may download the control program 1P from another computer via a network N or the like and store it in the mass storage unit 15. Furthermore, the control unit 11 may read the control program 1P from the semiconductor memory 1b.

[0021] The mass storage unit 15 includes a recording medium such as a hard disk drive (HDD) or a solid state drive (SSD). The mass storage unit 15 includes a rule database (DB) 151. The rule DB 151 stores rules and the reasons or background of the rules.

[0022] In this embodiment, the storage unit 12 and the large-capacity storage unit 15 may be configured as an integrated storage device. Furthermore, the large-capacity storage unit 15 may be configured by a plurality of storage devices. Furthermore, the large-capacity storage unit 15 may be an external storage device connected to the server 1.

[0023] The server 1 may execute various information processing and control processing on a single computer, or may execute the processing in a distributed manner on multiple computers. The server 1 may also be realized by multiple virtual machines provided in a single server, or may be realized by using a cloud server.

[0024] 3 is an explanatory diagram showing an example of a record layout of the rule DB 151. The rule DB 151 includes a rule ID column, a title column, a rule content column, a rule link column, a date and time column, an information type column, a reason and history column, a reason and history link column, a basis information column, a basis information update date and time column, and a responsible person column.

[0025] The rule ID column stores a unique rule ID to identify each rule. The title column stores the rule's title (e.g., "Revision of Intellectual Property-Related Provisions (Designs and Utility Models)"). The rule content column stores the rule's content. The rule link column stores the path or URL (Uniform Resource Locator) of the file containing the rule's content. The date and time column stores the date and time when the rule was established, revised, or updated.

[0026] The information type column stores the recorded information type, including text, audio, image, or video. The reason / history column stores the reason or history of the rule for each recorded information type. The reason / history link column stores a link (e.g., a file path or URL) for accessing the reason or history. The basis information column stores the basis information for the rule (e.g., the rule's related regulations, laws, or ordinances, research results, expert opinions, or past cases). The basis information update date / time column stores the date and time when the basis information was updated. The responsible person column stores the ID or name of the person responsible for the establishment, revision, or update of the rule.

[0027] The storage format of each DB described above is an example, and other storage formats may be used as long as the relationships between the data are maintained.

[0028] FIG. 4 is a block diagram showing an example of the configuration of the manager terminal 2 and the employee terminal 3. As shown in FIG. The manager terminal 2 includes a control unit 21 , a storage unit 22 , a communication unit 23 , an input unit 24 , a display unit 25 , a microphone 26 , and an image capturing unit 27 .

[0029] The control unit 21 includes an arithmetic processing unit such as a CPU or an MPU, and reads and executes a control program 2P (program product) stored in the storage unit 22 to perform various information processing and control processing related to the manager's terminal 2. Note that although the control unit 21 is described in FIG. 4 as being a single processor, it may be a multiprocessor.

[0030] The storage unit 22 includes memory elements such as RAM or ROM, and stores the control program 2P or data required for the control unit 21 to execute processing. The storage unit 22 also temporarily stores data required for the control unit 21 to execute arithmetic processing.

[0031] The communication unit 23 is a communication module for performing communication-related processing, and transmits and receives information to and from the server 1, etc. via the network N. The input unit 24 may be a keyboard, a mouse, or a touch panel integrated with the display unit 25. The display unit 25 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to instructions from the control unit 21.

[0032] The microphone 26 is a device that converts sound into an electrical signal. The microphone 26 may be a headset connected to the manager terminal 2 via a short-range wireless communication method such as BLUETOOTH (registered trademark). The image capturing unit 27 is an image capturing device such as a CCD (Charge Coupled Device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera. The image capturing unit 27 may not be built into the manager terminal 2, but may be externally connected directly to the manager terminal 2 and configured to be capable of capturing images.

[0033] The employee terminal 3 includes a control unit 31, a memory unit 32, a communication unit 33, an input unit 34, a display unit 35, and a speaker 36. Note that the control unit 31, the memory unit 32, the communication unit 33, the input unit 34, and the display unit 35 are similar to the control unit 21, the memory unit 22, the communication unit 23, the input unit 24, and the display unit 25 of the manager terminal 2, and therefore their description will be omitted. The speaker 36 is a device that converts electrical signals into sound. Note that the speaker 36 may be a headset connected to the employee terminal 3 via a short-range wireless communication method such as BLUETOOTH.

[0034] FIG. 5 is an explanatory diagram illustrating the rule registration (storage) process and the notification transmission process. First, the rule registration process will be described. The server 1 generates a new notification creation screen (FIG. 6) including a rule to be notified, a first icon for inputting the reason or background of the rule, and a second icon for inputting the basis information for the rule.

[0035] The first icon includes a character registration icon 11d, a voice registration icon 11e, or a video registration icon 11f in Fig. 6, which will be described later, etc. The second icon is a basis information registration icon 11g in Fig. 6, which will be described later.

[0036] The server 1 transmits the generated new notification creation screen (FIG. 6) to the person in charge terminal 2. The person in charge terminal 2 receives input of information about the rule to be registered through the new notification creation screen (FIG. 6) transmitted from the server 1.

[0037] Information about rules includes the title of the rule, a description of the rule (e.g., "We have recently established regulations for work-related inventions related to designs"), a link corresponding to the rule (e.g., the URL of a document containing the contents of the rule), the date and time when the rule was established, revised, or updated, the reason or history for the rule for each recorded information type, a link (e.g., a URL) to access the reason or history, information on the basis for the rule, or the responsible person's responsible ID or name, etc.

[0038] The person in charge terminal 2 transmits the information on the accepted rules to the server 1. The server 1 receives the information on the rules transmitted from the person in charge terminal 2. The server 1 stores the rules included in the received information on the rules in the rule DB 151 in association with the reason or background.

[0039] Specifically, the server 1 assigns a rule ID to the received information about the rule. The server 1 stores the following information in the rule DB 151 as a single record, in association with the assigned rule ID: the title of the received rule, the content of the rule, the link corresponding to the rule, the date and time, the reason or history of the rule for each recorded information type, the link for accessing the reason or history, the basis information for the rule, the update date and time of the basis information, and the responsible person ID.

[0040] Next, the notification transmission process of the registered rule will be described. Based on the rule ID of the rule to be notified, the server 1 acquires the content of the corresponding rule and a link (e.g., a URL) for accessing the reason or history associated with the rule from the rule DB 151. The server 1 transmits the acquired content of the rule and the link for accessing the reason or history associated with the rule to the employee terminal 3.

[0041] The employee terminal 3 receives the content of the rule and the link to the reason or background sent from the server 1. The employee terminal 3 displays the received content of the rule and the link to the reason or background on the screen. When the employee terminal 3 receives a touch operation on the link to the reason or background, it acquires the reason or background posted on the file path, site, etc. specified in the received link to the reason or background. The employee terminal 3 displays the acquired reason or background on the screen.

[0042] 6 is an explanatory diagram showing an example of a new notification creation screen. The new notification creation screen is a screen for registering the rule to be notified and the reason or background of the rule. The screen includes a title input field 11a, a description input field 11b, a document attachment field 11c, a character registration icon 11d, an audio registration icon 11e, a video registration icon 11f, a basis information registration icon 11g, a notification send button 11h, and a cancel button 11i.

[0043] The title input field 11a is a field for accepting input of the title of the rule. The explanation input field 11b is a field for accepting input of an explanation for the rule. The document attachment field 11c is a field for accepting upload of a document (file) that describes the content of the rule.

[0044] The character registration icon 11d is an icon for accepting input of text (character string) data for the reason or background of a rule. The audio registration icon 11e is an icon for accepting audio data for the reason or background of a rule. The video registration icon 11f is an icon for accepting image data or video data for the reason or background of a rule. Note that the character registration icon 11d, audio registration icon 11e, or video registration icon 11f may accept both the reason and background of a rule.

[0045] The reason and the process may be accepted separately. In this case, a character registration icon, a voice registration icon, and a video registration icon are provided for the reason, and a character registration icon, a voice registration icon, and a video registration icon are provided for the process.

[0046] The basis information registration icon 11g is an icon for accepting registration of basis information for a rule.

[0047] In this embodiment, the character registration icon 11d, the voice registration icon 11e, the video registration icon 11f, and the basis information registration icon 11g are described as examples of icons, but they are not limited to this and may be, for example, buttons.

[0048] The notification button 11h is a button for sending the registered rule and the reason or history of the rule to the employee terminal 3. If the reason or history of the rule has not been entered, the notification button 11h may be set to an inactive state and may not be pressed. The cancel button 11i is a button for returning from the screen to the previous screen (for example, the menu screen) without registering the rule and the reason or history of the rule.

[0049] When the person in charge terminal 2 receives an input operation in the title input field 11a, it acquires the title of the input rule. When the person in charge terminal 2 receives an input operation in the explanation input field 11b, it acquires the explanation of the input rule.

[0050] When the manager terminal 2 receives a touch operation on the document attachment field 11c, it receives an upload of a file (document) containing the content of the rule from the storage unit 12 or an external recording medium connected to the manager terminal 2. The recording medium is, for example, a portable memory such as an SD (Secure Digital) card, a micro SD card, or a CompactFlash (registered trademark).

[0051] When the manager terminal 2 receives a touch operation of the character registration icon 11d, it receives input of text data about the reason or background of the rule. When the manager terminal 2 receives a touch operation of the voice registration icon 11e, it receives voice data about the reason or background of the rule through the microphone 26. When the manager terminal 2 receives a touch operation of the video registration icon 11f, it receives image data or video data about the reason or background of the rule through the shooting unit 27.

[0052] When the manager terminal 2 receives a touch operation on the basis information registration icon 11g, it receives input of basis information for the rule. The basis information may be a file in which the basis is described.

[0053] When the manager terminal 2 receives a touch operation of the notification transmission button 11h, it transmits information about the rule, including the entered rule title, description, uploaded rule file, reason or history of the rule, and grounds information for the rule, to the server 1. The reason or history of the rule includes text data, audio data, image data, video data, etc., or a combination of these. The server 1 stores the information about the rule transmitted from the manager terminal 2 in the rule DB 151.

[0054] When the manager terminal 2 receives a touch operation of the cancel button 11i, the manager terminal 2 returns from the screen to the previous screen (for example, the menu screen).

[0055] 7 is a flowchart showing the processing procedure for registering a rule to be notified. The control unit 11 of the server 1 generates a new notification creation screen including the rule to be notified, a first icon for inputting the reason or background of the rule, and a second icon for inputting the basis information for the rule (step S101). The control unit 11 transmits the generated new notification creation screen to the manager terminal 2 via the communication unit 13 (step S102).

[0056] The control unit 21 of the manager terminal 2 receives the new notification creation screen transmitted from the server 1 via the communication unit 23 (step S201). The control unit 21 displays the received new notification creation screen on the display unit 25 (step S202). The control unit 21 accepts input of the rule to be notified, the reason or background of the rule, and the basis information for the rule, etc., via the new notification creation screen (step S203).

[0057] The reason or background of the rule includes text data, audio data, image data, video data, etc., or a combination of these. Specifically, control unit 21 accepts input of text data of the reason or background of the rule via input unit 24. Control unit 21 accepts audio data of the reason or background of the rule via microphone 26.

[0058] The control unit 21 receives image data or video data of the reason or background of the rule from the shooting unit 27. The control unit 21 may also receive uploads of image data or video data of the reason or background of the rule from the storage unit 12 or an external recording medium connected to the manager terminal 2. The control unit 21 receives input of grounds information for the rule from the input unit 24.

[0059] The control unit 21 transmits the accepted rule, reason or history, and basis information to the server 1 via the communication unit 23 (step S204). The control unit 11 of the server 1 receives the rule, reason or history, and basis information transmitted from the manager terminal 2 via the communication unit 13 (step S103).

[0060] The control unit 11 associates the received rule with the reason or history and the basis information and stores them in the rule DB 151 of the mass storage unit 15 (step S104). Specifically, the control unit 11 assigns a rule ID. The control unit 11 stores the received rule, the reason or history of the rule for each recorded information type (text data, audio data, image data, or video data), the basis information for the rule, and the update date and time of the basis information as one record in the rule DB 151, associated with the assigned rule ID. The control unit 11 then terminates the process.

[0061] 8 is a flowchart showing the processing steps when a registered rule is notified. Based on the rule ID of the rule to be notified, the control unit 11 of the server 1 acquires the content of the rule and a link for accessing the reason or history associated with the rule from the rule DB 151 in the mass storage unit 15 (step S111). The control unit 11 transmits the acquired content of the rule and a link for accessing the reason or history to the employee terminal 3 via the communication unit 13 (step S112).

[0062] The control unit 31 of the employee terminal 3 receives the content of the rule and the link to the reason or background transmitted from the server 1 via the communication unit 33 (step S311). The control unit 31 displays the received content of the rule and the link to the reason or background on the display unit 35 (step S312). The control unit 31 accepts a touch operation on the link to the reason or background via the input unit 34 (step S313).

[0063] The control unit 31 acquires the reason or history posted on the file path or site specified by the link of the received reason or history via the communication unit 33 (step S314). The control unit 31 displays the acquired reason or history on the display unit 35 (step S315). The control unit 31 ends the process.

[0064] Next, a process for outputting access information for accessing a rule corresponding to the basis information in response to a change in the basis information will be described.

[0065] 9 is a flowchart showing the processing procedure when outputting access information to a rule corresponding to the basis information. The control unit 11 of the server 1 determines whether or not there is a change in the stored basis information (step S121). For example, the control unit 21 of the person in charge terminal 2 receives a change in the basis information for the rule to be notified via the input unit 24. The control unit 21 transmits the received changed basis information to the server 1 via the communication unit 23 in association with the rule ID. The control unit 11 of the server 1 receives the rule ID and the changed basis information transmitted from the person in charge terminal 2. The control unit 11 updates the changed basis information in the rule DB 151 of the mass storage unit 15 based on the received rule ID, and determines that there is a change in the basis information.

[0066] Alternatively, the control unit 11 acquires the update date and time of the basis information from the rule DB 151 in the mass storage unit 15 based on the rule ID. The control unit 11 compares the update date and time of the acquired basis information with the update date and time of the previous basis information stored in the storage unit 12, for example, to determine whether or not there has been a change in the basis information.

[0067] Furthermore, the control unit 11 may determine whether or not there has been a change to the stored basis information by using the change history of the basis information. For example, when the change history of the basis information is stored in the memory unit 12 or the mass storage unit 15, the control unit 11 acquires the change history of the basis information from the memory unit 12 or the mass storage unit 15. The change history includes, for example, a rule ID, a historical version of the basis information, or change details corresponding to each historical version. The control unit 11 determines whether or not there has been a change to the basis information from the acquired change history of the basis information.

[0068] When the control unit 11 determines that there is no change in the stored basis information (NO in step S121), it waits. When the control unit 11 determines that there is a change in the stored basis information (YES in step S121), it transmits access information (for example, a file path or a URL) for accessing the rule corresponding to the basis information to the manager terminal 2 via the communication unit 13 (step S122). Note that the control unit 11 may also transmit access information for accessing the rule corresponding to the basis information to the employee terminal 3.

[0069] The control unit 21 of the manager terminal 2 receives the access information to the rule transmitted from the server 1 via the communication unit 23 (step S221). The control unit 21 displays the received access information to the rule on the display unit 25 (step S222). The control unit 21 accepts a touch operation for the access information to the rule via the input unit 24 (step S223).

[0070] Control unit 21 acquires the rule (the content of the rule, or a file containing the content of the rule, etc.) posted on the file path or site specified in the received access information to the rule via communication unit 23 (step S224). Control unit 21 displays the acquired rule on display unit 25 (step S225). Control unit 21 then terminates the process.

[0071] Furthermore, the control unit 21 of the person in charge terminal 2 may accept, in accordance with the changed basis information, a change to the rule by the person in charge, or the reason or history of the rule, etc., via the input unit 24. In this case, the control unit 21 transmits the accepted changed rule, the reason or history of the rule, etc., to the server 1 in association with a rule ID.

[0072] The control unit 11 of the server 1 receives the rule ID, the changed rule, the reason or history of the rule, etc. sent from the manager terminal 2. The control unit 11 updates the rule DB 151 with the changed rule, the reason or history of the rule, etc., in association with the received rule ID. The control unit 11 sends the changed rule, the reason or history of the rule, etc. to the employee terminal 3, similar to the notification transmission process described above.

[0073] According to this embodiment, it is possible to store the notification rule and the reason or background of the rule in association with each other.

[0074] According to this embodiment, it is possible to output to the employee terminal 3 a link for accessing the reason or background associated with the rule.

[0075] According to this embodiment, when it is determined that there is a change in the basis information, it is possible to output to the employee terminal 3 information for accessing the rule corresponding to the basis information.

[0076] (Embodiment 2) The second embodiment relates to a form in which a language model is used to output a dialogue including opinions for or against a rule to be notified. Note that a description of the contents that overlap with the first embodiment will be omitted.

[0077] Fig. 10 is a block diagram showing an example of the configuration of the server 1 in embodiment 2. Note that the same reference numerals are used to denote the same parts as in Fig. 2, and the description thereof will be omitted. The mass storage unit 15 includes a discussion model 152. The discussion model 152 is an output device (predictor) that outputs a dialogue including opinions for or against a rule based on the rule to be notified, and is a trained model generated by machine learning.

[0078] 11 is an explanatory diagram illustrating the process of outputting a dialogue using the argument model 152. The argument model 152 is a language model that uses the rules to be notified and the reasons or circumstances for the rules, and is used as a program module that is part of artificial intelligence software.

[0079] The discussion model 152 is a constructed language model (language generation model) that takes as input the rule to be notified and a prompt including the reason or history of the rule, and outputs a dialogue between a supporter avatar (first avatar) set with role information in favor of the rule and an opponent avatar (second avatar) set with role information in opposition to the rule.

[0080] The argument model 152 is a language model constructed by pre-training using large-scale text data (dataset). As the argument model 152, for example, large language models (LLMs) such as Transformer, ALBERT (A Lite BERT), GPT (Generative Pre-trained Transformer)-2, GPT-3, GPT-4, LLaVA (Large Language and Vision Assistant), MiniGPT-4, or BERT (Bidirectional Encoder Representations from Transformers) can be used.

[0081] Instead of storing the argument model 152 in the mass storage unit 15, the server 1 may access an external language processing server or language processing platform and read it out.

[0082] A prompt is an instruction or input sentence that is created in a format that can be understood by argument model 152 and is given as input to argument model 152. Argument model 152 interprets the input prompt and outputs an appropriate response (e.g., a dialogue between a pro- and anti-argument avatar).

[0083] As an example, the argument model 152 divides the prompt into tokens to convert it into a format that can be processed by the argument model 152. The argument model 152 performs context understanding processing by calculating the relationship of each token to other tokens in the prompt.

[0084] The argument model 152 generates a response to the prompt based on linguistic knowledge acquired through prior learning and fine-tuning. For example, the argument model 152 selects the optimal token using a generation method such as greedy decoding, beam search, or sampling. The argument model 152 decodes the selected token to return it to text format, and generates a conversation between a support avatar and an opposing avatar, which serves as output data.

[0085] Based on the rule ID, the server 1 acquires the rule to be discussed, the reason or history of the rule, or the basis information from the rule DB 151. The server 1 generates a prompt including the acquired rule, the reason or history of the rule, the basis information, role information of a supporter avatar who supports the rule, role information of an opponent avatar who opposes the rule, or an instruction (instruction) on the viewpoint of the discussion for the supporter avatar or the opponent avatar. The prompt may also include national guidelines, past issues, similar cases from other companies, etc.

[0086] As an example, the generated prompt is: "You are two avatars, one in favor of the following rules and one against them. Please engage in a discussion, referring to the reasons and history below, external sources (national guidelines and examples from other companies), internal company rules, or issues that have arisen in the past. Those in favor should discuss the issue from a paperless perspective. Those who are opposed should point out the problems with computerization. Rules: Rules for the transfer of patent rights Reason or background: Until now, when transferring the right to obtain a patent to a company, the procedure was to stamp a paper transfer certificate, but after considering whether paper was necessary, we decided to replace it with just consent in the approval workflow. Basis information: XXX" is also acceptable.

[0087] The server 1 inputs the generated prompt into the argument model 152 and generates a conversation between the pro- and anti-pro-avatars.

[0088] As shown, for example, the conversation output from argument model 152 is: "Rules: Rules for the Transfer of Patent Rights Reason and background: Until now, when transferring the right to obtain a patent to a company, the procedure was to stamp a paper transfer certificate, but after considering whether paper was necessary, we decided to replace it with simply consent in the approval workflow. · Pro Avatar: As paperless processes are being implemented in other areas as well, such as handling invoices electronically, this should also be done paperlessly. · Opposition Avatar: If the only thing that is agreed to is the workflow, the inventor is not clearly aware of what he or she has agreed to. · Pro-Avatar: The concerns would be alleviated if we considered providing displays and links that make it easier to check the details of the inheritance. Opposition Avatar: XXX ..." is also acceptable.

[0089] 12 is a flowchart showing the processing steps when outputting a conversation between a supporter avatar and an opponent avatar. Based on the rule ID, the control unit 11 of the server 1 acquires the rule to be discussed and notified, the reason or history of the rule, or the basis information for the rule from the rule DB 151 of the mass storage unit 15 (step S131). Note that the control unit 11 may also acquire past issues related to the rule or similar cases of other companies from the storage unit 12, the mass storage unit 15, an external information processing device, or the like.

[0090] The control unit 11 generates a prompt including the acquired rule, the reason or history of the rule, the basis information, the role information of the supporter avatar who supports the rule, the role information of the opponent avatar who opposes the rule, or instructions on the viewpoint of the discussion for the supporter avatar or the opponent avatar (step S132).

[0091] The control unit 11 inputs the generated prompt into the argument model 152 (step S133) and outputs the conversation between the supporter avatar and the opponent avatar (step S134). The control unit 11 transmits the output conversation between the supporter avatar and the opponent avatar to the manager terminal 2 or the employee terminal 3 via the communication unit 13 (step S135). The control unit 11 ends the process.

[0092] Furthermore, based on discussions on rules acquired from a plurality of users, the discussion model 152 can output a response by a minority avatar (third avatar) to which minority role information is set.

[0093] Specifically, the server 1 acquires discussions about the rule from multiple users (such as managers or employees). For example, the server 1 acquires discussions about the rule from multiple target manager terminals 2 or employee terminals 3. Note that the server 1 may also acquire discussions about the rule from multiple users (for example, pro- and anti- avatars) based on a conversation between a pro- and anti- avatar output from the discussion model 152.

[0094] The server 1 determines whether each user is in favor or against the rule based on the content of the discussion on the acquired rule, for example, using natural language processing (NLP) or machine learning (ML). The server 1 identifies the user with the fewer number of users between the number of users in favor and the number of users against as the minority. For example, if the server 1 determines that there are four users in favor and one user against, it identifies the user who is against as the minority.

[0095] The server 1 generates a prompt including the rule, the reason or history of the rule, the basis information, the ratio information of supporters and opponents, the role information of the specified minority, or an instruction on the viewpoint (position) of the discussion for the minority.

[0096] As an example, the generated prompt is: "The number of supporters and opponents was 4 to 1. Since there are few opponents, you should participate in the discussion from the opposing side's perspective. Engage in a dialogue, referencing the reasons and circumstances below, external sources (national guidelines and examples from other companies), internal company rules, and past issues. Since you are opposed, point out the problems with digitization. Rules: Rules for the transfer of patent rights Reason or background: Until now, when transferring the right to obtain a patent to a company, the procedure was to stamp a paper transfer certificate, but after considering whether paper was necessary, we decided to replace it with just consent in the approval workflow. Basis information: XXX" is also acceptable.

[0097] The server 1 inputs the generated prompt into the discussion model 152, and generates a response by a minority avatar to which minority role information has been set.

[0098] For example, the response of the minority avatar output from argument model 152 is: "Rules: Rules for the Transfer of Patent Rights Reason and background: Until now, when transferring the right to obtain a patent to a company, the procedure was to stamp a paper transfer certificate, but after considering whether paper was necessary, we decided to replace it with simply consent in the approval workflow. · Pro Avatar: As paperless processes are being implemented in other areas as well, such as handling invoices electronically, this should also be done paperlessly. · Opposition Avatar: If the only thing that is agreed to is the workflow, the inventor is not clearly aware of what he or she has agreed to. · Pro-Avatar: The concerns would be alleviated if we considered providing displays and links that make it easier to check the details of the inheritance. Pro-Avatar: XXX Pro-Avatar: XXX · Opposition avatar: It seems like there are many in favor, but there have been lawsuits like this in the past with other companies, so I think it should be considered carefully."

[0099] 13 is a flowchart showing the processing steps when a response by a minority avatar is output. Based on the rule ID, the control unit 11 of the server 1 acquires the rule to be discussed, the reason or history of the rule, or the basis information for the rule from the rule DB 151 in the mass storage unit 15 (step S141). The control unit 11 acquires discussions on the rule from the multiple manager terminals 2 or employee terminals 3 via the communication unit 13 (step S142).

[0100] The control unit 11 determines whether each user is in favor or against the rule based on the content of the discussion on the acquired rule, for example, by using natural language processing or machine learning (step S143). The control unit 11 identifies the smaller number of users as the minority out of the number of users who are in favor or who are against the rule (step S144).

[0101] The control unit 11 generates a prompt including the rule, the reason or history of the rule, the basis information, the ratio information of supporters and opponents, the role information of the identified minority, or an instruction on the viewpoint of the discussion to the minority (step S145). The control unit 11 inputs the generated prompt into the discussion model 152 (step S146) and outputs a response by the minority avatar (step S147).

[0102] The control unit 11 transmits the conversation between the supporter avatar and the opponent avatar, including the output response by the minority avatar, to the manager terminal 2 or the employee terminal 3 via the communication unit 13 (step S148). The control unit 11 then ends the process.

[0103] Next, a process for extracting rules and reasons or circumstances from historical data of a meeting using the discussion model 152 will be described.

[0104] 14 is a flowchart showing the processing steps for extracting a rule and a reason or background. The control unit 11 of the server 1 acquires historical data of the meeting (step S151). The historical data is text data or audio recording data, etc., and includes the date and time of the meeting, participants, minutes (detailed records of the discussions at the meeting), decisions made, etc. The historical data may be stored in the memory unit 12 or mass memory unit 15 of the server 1, for example, or may be acquired from the manager terminal 2 or employee terminal 3.

[0105] The control unit 11 generates a prompt from the acquired history data (step S152). The prompt includes items of the history data (such as the date and time of the meeting, participants, minutes or decisions, etc.), content corresponding to each item, and instructions for extracting rules and reasons or circumstances.

[0106] As an example, the generated prompt is: "Based on the historical data from the following meetings, extract the rules and the reasons or circumstances behind them. Meeting date and time: XXX Participants:××× Minutes: XXX It can also be "Decision: XXX".

[0107] The control unit 11 inputs the generated prompt into the discussion model 152 (step S153) and outputs the rule and the reason or history (step S154). The control unit 11 stores the reason or history in the rule DB 151 of the mass storage unit 15 in association with the output rule (step S155). Specifically, the control unit 11 assigns a rule ID. The control unit 11 stores the output rule and the reason or history as one record in the rule DB 151 in association with the assigned rule ID. The control unit 11 then terminates the processing.

[0108] In addition to historical data from meetings, the server 1 may also use voice recognition technology to analyze video or audio recordings of interviews with veterans (experienced people) to extract rules and the reasons or circumstances. Meeting minutes recording discussions, decisions, action items, etc., or audio or video recordings of meetings can also be used. In this case, the server 1 extracts rules and the reasons or circumstances from the minutes, audio or video recordings, etc. This makes it possible to collect and analyze important information related to discussions or decision-making in meetings or interviews without relying on veterans.

[0109] According to this embodiment, the discussion model 152 can output a dialogue between a supporter avatar and an opponent avatar regarding a rule.

[0110] According to this embodiment, the discussion model 152 can output a response from a minority avatar, whichever has fewer users who agree or disagree.

[0111] According to this embodiment, by providing history data to the discussion model 152, it is possible to extract rules and reasons or circumstances.

[0112] The embodiments disclosed herein are illustrative in all respects and should not be considered limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.

[0113] The matters described in each embodiment can be combined with each other. Furthermore, the independent claims and dependent claims described in the claims can be combined with each other in any and all combinations, regardless of the reference format. Furthermore, the claims use a format in which a claim references two or more other claims (multiple claim format), but this is not limited to this. A multiple claim (multi-multi claim) that references at least one other multiple claim may also be used. [Explanation of symbols]

[0114] 1. Information processing device (server) 11 Control section 12 Storage section 13 Communications Department 14 Reading unit 15 Mass storage 151 Rule DB 152 Argument Model 1a Portable storage media 1b semiconductor memory 1P control program 2. Information processing terminal (person in charge terminal) 21 Control section 22 Memory section 23 Communications Department 24 Input section 25 Display section 26. Mike 27 Photography Department 2P control program 3. Information processing terminals (employee terminals) 31 Control Unit 32 Storage section 33 Communications Department 34 Input section 35 Display section 36 Speaker 3P control program

Claims

1. Accepts input of the rule to be notified and the reason or history of the rule; The accepted rule is stored in the storage unit in association with the reason or circumstances. A program that causes a computer to perform a process.

2. A first icon for inputting the reason or the circumstances and a second icon for inputting the basis information for the rule are output in association with the rule. The program according to claim 1.

3. determining whether there is a change in the stored basis information; If it is determined that a change exists, information for accessing the rule corresponding to the basis information is output. The program according to claim 2.

4. A dialogue between a first avatar, to which role information indicating support for the rule is set, and a second avatar, to which role information indicating opposition to the rule is set, is output by a language model using the rule. The program according to claim 1 or 2.

5. Obtaining discussions on the rule from a plurality of users; Each user decides whether to agree or disagree with the rule; Identify the smaller number of users as the minority out of the number of users who support the idea and the number of users who oppose it, A response by a third avatar to which the role information of the identified minority is set is output by a language model using the rule. The program according to claim 1.

6. Obtain historical data on the meeting; The acquired history data is fed to the language model to extract rules and reasons or circumstances; The reason or circumstances for the extraction are stored in the storage unit in association with the extracted rule. The program according to claim 4.

7. Accepts input of the rule to be notified and the reason or history of the rule; The accepted rule is stored in the storage unit in association with the reason or circumstances. An information processing method in which processing is performed by a computer.

8. An information processing device including a control unit, The control unit Accepts input of the rule to be notified and the reason or history of the rule; The accepted rule is stored in the storage unit in association with the reason or circumstances. Information processing device.

Images