system

Abstract

Provide a system. [Solution] A means for receiving input contract information; A means for verifying the application status of the policies of the contract information based on the list of policies; a means for verifying the format of the contract code; A means for generating an error message when there is an error in the policy application or contract code; a means for displaying the validation results; A system including:

Description

[Technical Field]

[0001] The technology of the present disclosure relates to a system. [Background technology]

[0002] Patent document 1 discloses a persona chatbot control method performed by at least one processor, the method including the steps of receiving a user utterance, adding the user utterance to a prompt including an instruction sentence related to a description of the chatbot character, encoding the prompt, and inputting the encoded prompt into a language model to generate a chatbot utterance in response to the user utterance. [Prior art documents] [Patent documents]

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

[0004] When registering contract information, if human errors occur, such as missing a policy or entering the wrong contract code, subsequent processing will require corrections, reducing work efficiency. Furthermore, these errors can lead to a decline in the quality of service provided to customers and a loss of trust. It is necessary to solve these problems and improve the accuracy of contract information. [Means for solving the problem]

[0005] The system according to the present invention includes a means for receiving input contract information, a means for verifying the policy application status of the contract information based on a list of policies, a means for verifying the format of the contract code, a means for generating an error message if there is an error in the policy application or contract code, and a means for displaying the verification results. This allows for automatic detection of missed policy applications or contract code input errors before registering contract information, and notifies the user in advance. This reduces the number of subsequent issues, improving business efficiency and service quality.

[0006] The "means for receiving input contract information" is a mechanism by which the system receives contract information input by the user.

[0007] A "list of measures" is a list of a series of measures that the system should apply.

[0008] The "means for verifying the policy application status of the contract information" is a mechanism for checking whether the list of policies entered matches the list of policies required.

[0009] The "means for verifying the format of the contract code" is a mechanism for checking whether the entered contract code complies with the specified format.

[0010] The "means for generating an error message when there is an error in the policy application or contract code" is a mechanism for generating a message to inform the user of the content of any defect in the contract information.

[0011] The "means for displaying the validation results" is a mechanism for visually presenting error messages and validation results to the user. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a conceptual diagram showing an example of the configuration of a data processing system according to a first embodiment. [Figure 2]1 is a conceptual diagram showing an example of main functions of a data processing device and a smart device according to a first embodiment. [Figure 3] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a second embodiment. [Figure 4] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and smart glasses according to a second embodiment. [Figure 5] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a third embodiment. [Figure 6] FIG. 11 is a conceptual diagram showing an example of main functions of a data processing device and a headset-type terminal according to a third embodiment. [Figure 7] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a fourth embodiment. [Figure 8] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and a robot according to a fourth embodiment. [Figure 9] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 10] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 11] FIG. 3 is a sequence diagram showing a processing flow of the data processing system according to the first embodiment. [Figure 12] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 1. [Figure 13] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system according to the second embodiment when an emotion engine is combined. [Figure 14] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 2 when an emotion engine is combined. DETAILED DESCRIPTION OF THE INVENTION

[0013] An example of an embodiment of a system according to the technology of the present disclosure will be described below with reference to the accompanying drawings.

[0014] First, the terms used in the following description will be explained.

[0015] In the following embodiments, a coded processor (hereinafter simply referred to as a "processor") may be a single arithmetic device or a combination of multiple arithmetic devices. Furthermore, a processor may be a single type of arithmetic device or a combination of multiple types of arithmetic devices. Examples of arithmetic devices include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a GPGPU (General-Purpose computing on Graphics Processing Units), and an APU (Accelerated Processing Unit).

[0016] In the following embodiments, a coded RAM (Random Access Memory) is a memory in which information is temporarily stored and is used as a working memory by a processor.

[0017] In the following embodiments, the coded storage is one or more non-volatile storage devices that store various programs, various parameters, etc. Examples of non-volatile storage devices include flash memory (SSD (Solid State Drive)), magnetic disks (e.g., hard disks), and magnetic tapes.

[0018] In the following embodiments, a communication I / F (Interface) with a symbol is an interface including a communication processor, an antenna, etc. The communication I / F controls communication between multiple computers. Examples of communication standards applied to the communication I / F include wireless communication standards including 5G (5th Generation Mobile Communication System), Wi-Fi (registered trademark), Bluetooth (registered trademark), etc.

[0019] In the following embodiments, "A and / or B" is synonymous with "at least one of A and B." In other words, "A and / or B" means that it may be only A, only B, or a combination of A and B. Furthermore, in this specification, the same concept as "A and / or B" is also applied when three or more things are expressed connected by "and / or."

[0020] [First embodiment]

[0021] FIG. 1 shows an example of the configuration of a data processing system 10 according to the first embodiment.

[0022] 1, a data processing system 10 includes a data processing device 12 and a smart device 14. An example of the data processing device 12 is a server.

[0023] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0024] The smart device 14 includes a computer 36, a reception device 38, an output device 40, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The reception device 38, the output device 40, and the camera 42 are also connected to the bus 52.

[0025] The reception device 38 includes a touch panel 38A, a microphone 38B, and the like, and receives user input. The touch panel 38A detects contact with an indicator (for example, a pen or a finger) to receive user input by the touch of the indicator. The microphone 38B detects the user's voice to receive user input by voice. The control unit 46A transmits data indicating the user input received by the touch panel 38A and the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the data indicating the user input.

[0026] The output device 40 includes a display 40A and a speaker 40B, and presents data to the user 20 by outputting the data in a form of expression that the user 20 can perceive (for example, audio and / or text). The display 40A displays visible information such as text and images in accordance with instructions from the processor 46. The speaker 40B outputs audio in accordance with instructions from the processor 46. The camera 42 is a compact digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor.

[0027] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54.

[0028] FIG. 2 shows an example of the main functions of the data processing device 12 and the smart device 14.

[0029] 2, in the data processing device 12, a specific process is performed by the processor 28. A specific processing program 56 is stored in the storage 32. The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific process is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0030] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0031] In the smart device 14, the processor 46 performs the reception output process. The storage 50 stores a reception output program 60. The reception output program 60 is used in conjunction with the specific processing program 56 by the data processing system 10. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0032] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0033] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[0034] 1. System initialization

[0035] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, a code validator for validating the format of the contract code is initialized. Finally, an instance of the RegistrationSystem class is created based on this information. This instance is responsible for validating the contract information and generating error messages.

[0036] 2. Enter a new contract entry

[0037] The user enters contract information on the new contract registration screen. This information includes the list of policies to be applied (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[0038] 3. Submit a new contract entry

[0039] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[0040] 4. Entry Validation

[0041] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[0042] 4.1 Checking the application of measures

[0043] The server verifies that the input action list matches the pre-defined action list, and generates an error message if any missing actions are detected.

[0044] 4.2 Code Validation

[0045] The server checks whether the entered contract code complies with the required format, and generates an error message if the format does not match.

[0046] 5. Sending the verification results

[0047] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the contract information verification was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[0048] Specific examples

[0049] A specific example is shown below.

[0050] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0051] 1. Failure to apply Measure B is detected.

[0052] 2. The contract code is verified to be in a valid format.

[0053] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can apply Measure B additionally to complete the correction.

[0054] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, thereby reducing the number of cases that arise after the fact and improving business efficiency and service quality.

[0055] The processing flow will be explained below.

[0056] Step 1:

[0057] The server sets up a list of policies and a code validator when the system starts up, which prepares the basic information required for validating contract information and initializes an instance of the RegistrationSystem class.

[0058] Step 2:

[0059] The user operates the new contract registration screen and enters contract information. Specifically, the user enters the list of measures to be applied (for example, "Measure A" and "Measure C") and the contract code (for example, "ABC1234567").

[0060] Step 3:

[0061] The user sends the entered contract information to the server. At this time, the contract information is sent from the terminal to the server.

[0062] Step 4:

[0063] The server receives the contract information and calls the validate_entry method, which starts the validation process for the contract information.

[0064] Step 5:

[0065] The server checks the application of policies as part of the validation process. It compares the list of configured policies with the list of policies entered by the user to see if any policies are missing. If any policies are missing, it generates an error message for those policies.

[0066] Step 6:

[0067] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a predetermined format, and generates an error message if the format does not match.

[0068] Step 7:

[0069] The server compiles the results of the policy application and contract code verification and creates a list of error messages. If no error messages exist, it generates a message indicating that the contract information has been entered correctly.

[0070] Step 8:

[0071] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[0072] Step 9:

[0073] The user corrects the contract information as necessary based on the notification from the server, then submits the contract information again and performs verification again.

[0074] In this way, the server can check the appropriateness of new contract information in advance, and users can make necessary corrections based on the verification results, reducing errors. This process is expected to improve the accuracy of contract information and business efficiency.

[0075] Example 1

[0076] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0077] When registering a new contract, there is a possibility that measures may not be applied properly or that contract codes may be entered incorrectly. If these errors are not detected in advance, not only will the amount of work required to deal with them increase, reducing operational efficiency but also the quality of service. There is a need for a system that can solve this problem and detect errors in advance to reduce the number of cases that need to be dealt with.

[0078] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0079] In this invention, the server includes a processor that receives contract information, compares the list of measures included in the contract information with a list of measures to detect missing measures, and checks whether the contract code included in the contract information matches a predetermined format, a processor that verifies the policy application status of the contract information based on the list of measures, a processor that verifies the format of the contract code, a processor that generates and displays an error message on a user terminal if there is an error in the policy application or contract code, and a processor that displays the verification result.This makes it possible to detect and address missing measures and input errors in the contract code when registering a new contract in advance.

[0080] "Contract information" is information required to register a new contract, and includes a policy list and a contract code.

[0081] The "measure list" is a list of measures to be applied to the system, which are set based on specific conditions and rules.

[0082] The "contract code" is a code for uniquely identifying a contract, and is composed of a character string in a predetermined format.

[0083] A "processor" is a computing device that receives, processes, and transmits data and is the primary component for performing various functions of the system.

[0084] An "error message" is a notification that informs the user of any discrepancies or deficiencies detected during the verification process and prompts the user to correct them.

[0085] "User terminal" means a computing device through which a user accesses the system and enters or modifies contract information.

[0086] The "policy application status" is a status indicating whether the necessary policies are being applied based on the input contract information.

[0087] "Verification results" refers to information including conclusions and error messages resulting from the verification of contract information.

[0088] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting incorrect contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[0089] System initialization

[0090] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C"). This information is stored in the system's memory. Next, it sets up a code validator to validate the format of the contract code. The validator contains rules and regular expressions to check the accuracy of the contract code. Based on this information, it creates an instance of the RegistrationSystem class. This instance is responsible for validating the contract information and generating error messages.

[0091] Enter and submit a new contract entry

[0092] The user enters contract information on the device's new contract registration screen. Input fields include a list of measures to be applied (e.g., "Measure A," "Measure C") and a contract code (e.g., "ABC1234567"). This information is temporarily stored on the device, and then sent to the server when the user clicks the "Send" button. Data is generally sent in JSON or XML format.

[0093] Entry validation

[0094] The server executes the validate_entry method to validate the received contract information. First, it compares the entered policy list with the policy list configured in the system to detect any missing policies. For example, if a user selects "Policy A" and "Policy C" but does not apply "Policy B," an error message stating "Missing application: Policy B" is generated. Next, it checks whether the contract code matches the specified format. If the format does not match, an error message stating "Contract code is invalid" is generated.

[0095] Submitting and correcting validation results

[0096] The server compiles the verification results as an error message list. If there are no error messages, it generates a success message (e.g., "Contract information verification was successful") and sends it to the user's terminal. If there are error messages, each error message is listed and sent to the user. The user receives this and makes corrections based on the error content, such as adding measures or re-entering the contract code.

[0097] Specific examples

[0098] For example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server compares the list of measures and detects that "Measure B has not been applied." It also verifies that the contract code format is valid. As a result, an error message "Not applied: Measure B" is generated and sent to the user. The user receives this message, adds "Measure B," and submits the contract information again. After resubmission, if the verification is successful, the message "Contract information verification successful" is displayed.

[0099] Prompt Sentence Examples

[0100] Below are some example prompts for using a generative AI model:

[0101] We have developed a new system. This system aims to detect potential policy oversights and contract code input errors that may occur when registering new contracts, thereby reducing the number of cases we have to deal with. Please explain the process in natural language using the following steps:

[0102] 1. System initialization: When the server starts the system, it sets up the policy list and initializes the contract code validator. It creates an instance of the RegistrationSystem class.

[0103] 2. Entering a new contract entry: The user enters the policy list and contract code on the registration screen.

[0104] 3. Sending new contract entry: The contract information entered by the user is sent from the terminal to the server.

[0105] 4. Validate entry: The server uses the validate_entry method to check policy application and validate the code.

[0106] 5. Sending the verification result: The server sends an error message to the user.

[0107] For example, a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server detects that Measure B has not been applied and checks the format of the contract code. As a result, an error message "Missing application: Measure B" is generated.

[0108] The above is a detailed description of the "Mode for Carrying Out the Invention" of the system according to the present invention. This system makes it possible to detect missed measures and input errors in contract codes that may occur when registering a new contract, thereby improving business efficiency and service quality.

[0109] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0110] Step 1: Initialize the system

[0111] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C") and loads it into memory. Next, it sets up a code validator to verify the format of the contract code. This makes it possible to check the format of the contract code. Finally, it generates an instance of the RegistrationSystem class based on this information. The inputs are the statically defined list of measures and the regular expression pattern for the contract code. The output is that the RegistrationSystem instance is initialized.

[0112] Specific behavior: The server logs the message "Policy list and code validator initialized."

[0113] Step 2: Enter a new contract entry

[0114] The user enters contract information on the new contract registration screen on the terminal. Input items include a list of measures to be applied (e.g., "Measure A", "Measure C") and a contract code (e.g., "ABC1234567"). The input information is temporarily saved on the terminal. The input includes a list of measures selected by the user and a contract code. The output is the input information saved on the terminal.

[0115] Specific operation: The user enters the policy list and contract code on the screen and clicks the "Confirm" button.

[0116] Step 3: Submit a new contract entry

[0117] When the user clicks the "Send" button, the terminal sends the entered contract information to the server. The transmission format is generally JSON or XML. The input is the contract information stored on the terminal. The output is the contract information sent to the server.

[0118] Specific operation: The terminal displays a confirmation message to the server saying "Transmission completed."

[0119] Step 4: Validate your entries

[0120] The server validates the received contract information using the validate_entry method. The following specific processing is performed:

[0121] 1. Check the application of measures:

[0122] The server compares the input action list with a static action list and detects missing actions. For example, if "action A" and "action C" are selected but "action B" is not applied, an error message "Missing application: action B" is generated. The inputs are the action list sent by the user and the server's static action list. The output is a list of missing actions and an error message.

[0123] 2. Code validation:

[0124] The server checks whether the entered contract code matches the specified format. If it does not match, it generates an error message saying "The contract code is invalid." The inputs are the contract code sent by the user and the server's regular expression pattern. The output is the format check result and an error message.

[0125] Specific behavior: The server logs a "verification completed" message and generates a list of error messages.

[0126] Step 5: Submitting the verification results

[0127] The server compiles the verification results into an error message list. If this list is empty, a message stating "Contract information verification was successful" is generated and sent to the user. If error messages exist, each error message is listed and sent to the user. The input is the verification results. The output is either a list of error messages or a success message sent to the user.

[0128] Specific operation: The user terminal displays a confirmation message saying "Verification result received."

[0129] Step 6: Make corrections based on the results

[0130] The user corrects the contract information based on the error message. Specifically, they add missing measures or re-enter the contract code. After making the corrections, they press the "Send" button again to send the new contract information to the server. The inputs are the error message and the user's corrections. The output is that the corrected contract information is sent again to the server.

[0131] Specific behavior: The user makes corrections and clicks the "Submit" button again.

[0132] (Application example 1)

[0133] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0134] With the previous system, there was a problem of work efficiency decreasing when it came to missed policy applications or input errors in contract codes that could occur when registering new contracts. Furthermore, with electronic payment services, there was also the problem of input errors and incorrect information being registered when registering new payment methods. This resulted in a decline in service quality and usability issues.

[0135] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0136] In this invention, the server includes means for receiving input contract information and payment information, means for verifying the policy application status and payment method application status of the contract information based on a list of policies, means for verifying the format of the contract code and payment code, means for generating an error message if there is an error in the policy application or in the contract code or payment code, and means for displaying the verification result. This makes it possible to detect in advance the application of policies or input errors in the contract code or payment code when registering a new contract or new payment method, thereby improving business efficiency and service quality.

[0137] "Contract Information" is data entered by a user containing details of a new contract.

[0138] "Payment Information" means data containing details of a new payment method entered by a user.

[0139] A "list of measures" is a set of measures that are pre-configured in the system.

[0140] A "contract code" is a unique identifier associated with contract information.

[0141] "Payment Code" means a unique identifier associated with a payment method.

[0142] The "policy application status" is an index that indicates the application status of the policy in the contract information.

[0143] "Payment method application status" is an indicator that indicates the application status of the payment method in the payment information.

[0144] An "error message" is a notification to the user that the information they entered is incomplete.

[0145] "Verification results" are the results obtained after verifying the policy application status, contract code, and payment code.

[0146] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and input errors in contract codes and payment codes that occur when registering new contracts and new payment methods. This system is realized by linking a server and terminals.

[0147] 1. System initialization

[0148] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, various validators for verifying the format of the contract code and payment code are initialized. Finally, an instance of the SecurePayValidator class is created based on this information. This instance is responsible for validating the contract information and payment information and generating error messages.

[0149] 2. Entering new contract and settlement entries

[0150] The user enters contract information and payment information on the registration screen for a new contract and a new payment method. This information includes a list of policies to be applied (applied_policies), a list of payment methods (payment_methods), a contract code (contract_code), and a payment code (payment_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567" and payment code "1234567890123456."

[0151] 3. Submitting new contract and settlement entries

[0152] The contract information and payment information entered by the user are sent from the terminal to the server, which then starts the verification process for the contract information and payment information.

[0153] 4. Entry Validation

[0154] The server executes the validate_entry method to validate the received contract information and payment information. This method performs the following processes.

[0155] Checking the application of measures

[0156] The server verifies that the entered policy list and payment method list match the pre-defined list, and generates an error message if a missing policy or payment method is detected.

[0157] Code Validation

[0158] The server checks whether the entered contract code and payment code conform to the specified format. If the format does not match, an error message is generated.

[0159] 5. Sending the verification results

[0160] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the verification of the contract information and payment information was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[0161] Hardware and software used

[0162] Hardware:

[0163] Smartphone devices: iOS or ANDROID (registered trademark) devices

[0164] software:

[0165] Python: Used for backend validation

[0166] Regular Expressions (re module): Validate the format of each code

[0167] Specific examples

[0168] A specific example is shown below.

[0169] Example prompt sentence:

[0170] Enter your credit card details:

[0171] Card number (16 digits): 1234567890123456

[0172] Enter your e-money information:

[0173] Electronic money code (6-12 characters): ABCD-1234

[0174] Are there any omissions in applicable policies? (e.g. credit cards, electronic money)

[0175] Registration failed. Error message: [Invalid format: credit card payment code]

[0176] When a user registers a "credit card" and "electronic money" based on the above prompts, the system verifies whether the card number and electronic money code entered by the user are valid, and immediately notifies the user of an error message if there is any fraud.

[0177] This will enable the system to detect missed measures and input errors in contract codes and payment codes in advance when registering new contracts and new payment methods, improving business efficiency and service quality.

[0178] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0179] Step 1:

[0180] The terminal displays an input screen for the user to register a new contract and a new payment method. This screen displays fields for the user to enter a policy list, a payment method list, a contract code, and a payment code. As input, the user provides "Policy A," "Policy C," "Credit card," and the payment code "1234567890123456."

[0181] Step 2:

[0182] The user enters new contract information and payment information into the input screen. This includes the policy list to be applied, the payment method list, the contract code, and the payment code. The entered data includes the policy list, the payment method list, the contract code "ABC1234567", and the payment code "1234567890123456".

[0183] Step 3:

[0184] The terminal transmits the input contract information and payment information to the server. The input data includes the contract information and payment information input by the user. This data is transmitted to the server.

[0185] Step 4:

[0186] The server analyzes the received contract and payment information and calls the validate_entry method. The input data includes the contract and payment information. Based on this, the server begins validating the policy application status and code.

[0187] Step 5:

[0188] The server verifies the application status of the policies. Specifically, it compares the input policy list and payment method list with the pre-defined policy list and payment method list. If the comparison detects any missing policies or payment methods, it generates an error message.

[0189] Step 6:

[0190] The server validates the format of the contract code and payment code. Specifically, it checks whether each code matches the specified format. The input includes the contract code and payment code. If the formats do not match, an error message is generated.

[0191] Step 7:

[0192] The server compiles the verification results and constructs an error message list. The input includes the implementation status of the measures and the results of the formal verification of the code. If there are error messages, each error message is added to the error message list.

[0193] Step 8:

[0194] The server sends the verification results to the terminal, including as input a list of error messages, which are then communicated to the user, who receives information to make corrections.

[0195] Step 9:

[0196] The terminal displays the verification result received from the server to the user. The verification result from the server is included as input. If there is an error, an error message is displayed to the user, and the user can correct the information accordingly.

[0197] Furthermore, an emotion engine that estimates the user's emotion may be combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59 and perform identification processing using the user's emotion.

[0198] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[0199] 1. System initialization

[0200] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[0201] 2. Enter a new contract entry

[0202] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[0203] 3. Submit a new contract entry

[0204] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[0205] 4. Entry Validation

[0206] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[0207] 4.1 Checking the application of measures

[0208] The server verifies that the input action list matches the pre-defined action list, and generates an error message for any missing action if any is detected.

[0209] 4.2 Code Validation

[0210] The server checks whether the entered contract code conforms to the specified format and generates an error message if the format does not match.

[0211] 5. Emotional Recognition

[0212] The server uses an emotion engine to recognize the emotions the user is expressing while typing. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions.

[0213] 6. Generate feedback

[0214] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user feels confused or frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[0215] 7. Sending the verification results

[0216] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[0217] Specific examples

[0218] A specific example is shown below.

[0219] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0220] 1. Failure to apply Measure B is detected.

[0221] 2. The contract code is verified to be in a valid format.

[0222] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0223] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[0224] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[0225] The processing flow will be explained below.

[0226] Step 1:

[0227] When the system starts up, the server sets up a list of measures, a code validator, and an emotion engine, which prepares the information necessary for validating contract information and recognizing user emotions.

[0228] Step 2:

[0229] The user operates the new contract registration screen and enters contract information, specifically the list of measures to be applied (e.g., "Measure A," "Measure C," etc.) and the contract code (e.g., "ABC1234567").

[0230] Step 3:

[0231] While the user is typing, the device collects data such as the user's facial expressions, voice, and keystrokes in real time and sends this data to the emotion engine.

[0232] Step 4:

[0233] The server receives the contract information sent by the user and invokes the validate_entry method to start the process of validating the contract information.

[0234] Step 5:

[0235] The server verifies the application status of the measures. It compares the input list of measures with the list of pre-defined measures to check whether any measures are missing. If a missing measure is detected, it generates an error message for that measure.

[0236] Step 6:

[0237] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a specified format, and generates an error message if the format does not match.

[0238] Step 7:

[0239] The server uses an emotion engine to recognize the user's emotions. It analyzes data such as facial expressions, voice, and keystrokes to determine whether the user is confused or frustrated. If the emotion engine detects a negative emotion, it generates appropriate feedback.

[0240] Step 8:

[0241] The server integrates the policy application status, the contract code verification results, and the emotion analysis results from the emotion engine to generate final feedback. If there are error messages, the feedback will include them. If negative emotions are detected, additional help information and assistance messages will also be included.

[0242] Step 9:

[0243] The server generates feedback and sends it to the user, which may include error messages to inform the user of what needs to be corrected, and may also display additional help or assistance messages.

[0244] Step 10:

[0245] The user makes the necessary corrections based on the feedback from the server. Once the corrections are complete, the user re-enters the contract information and submits it for verification again.

[0246] In this way, the server can proactively check the appropriateness of contract information and recognize the user's emotions, improving the user experience, reducing errors and increasing work efficiency.

[0247] Example 2

[0248] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0249] In the conventional contract registration system, it was easy for measures to be overlooked or contract codes to be entered incorrectly, and the accompanying error messages were insufficient, causing stress for users. In addition, the system handled issues without regard for user feelings, resulting in a poor user experience.

[0250] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes a means for receiving input contract information, a means for verifying the policy application status of the contract information based on the list of policies, a means for verifying the format of the contract code, a means for generating an error message if there is an error in the policy application or the contract code, a means for recognizing the user's emotions, a means for generating appropriate feedback based on the emotion recognition result, and a means for displaying the verification result and the feedback. This makes it possible to detect missed policy application or input errors in the contract code in advance, and further recognize the user's emotions and provide appropriate feedback.

[0251] "Contract information" refers to information that includes data regarding the establishment or modification of a contract.

[0252] A "measure list" refers to a list of measures and procedures that should be applied to a contract.

[0253] "Contract code" refers to a unique identifier for uniquely identifying contract information.

[0254] An "error message" refers to a warning or notification message that is displayed when the information entered by the user is incorrect.

[0255] "Emotion recognition" refers to the analysis of data such as a user's facial expressions, voice, and keystrokes to identify their emotional state.

[0256] "Feedback" refers to the response message or instructions provided to the user.

[0257] "Verification results" refers to information generated as a result of the system verifying the contract information entered.

[0258] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[0259] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[0260] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, if the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567," the user enters the list of applied policies and the contract code on the registration screen.

[0261] The contract information entered by the user is sent from the terminal to the server. This information is sent as an HTTP request and passed to the server in JSON format.

[0262] The server executes the validate_entry method to validate the received contract information. This method first checks whether the input policy list matches the configured policy list, and generates an error message if a missing policy is detected. Next, it checks whether the contract code conforms to the specified format, and generates an error message if the format does not match.

[0263] The server then uses an emotion engine to recognize the user's emotions as they are being input. It analyzes facial expressions, voice, keystrokes, and other data to identify the user's emotions. For example, it uses an emotion recognition system built using the Python library affectiva or DeepFace.

[0264] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user is feeling frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[0265] The server notifies the user of the validation results and feedback. If there are any error messages, it displays them to the user and prompts them to correct them. If there are no error messages, it displays a message that validation was successful.

[0266] As a concrete example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0267] 1. Failure to apply Measure B is detected.

[0268] 2. The contract code is verified to be in a valid format.

[0269] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0270] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[0271] Prompt sentence for generative AI model

[0272] I applied "Measure A" and "Measure C" and entered the contract code "ABC1234567", but please check for any missed measures or input errors in the contract code. Also, if the user is frustrated, please provide an appropriate help message.

[0273] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[0274] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0275] Step 1: Initialize the system

[0276] The server performs the following initialization process when the system starts up. First, it reads the action list (e.g., "Action A," "Action B," and "Action C") from the database or configuration file and stores this list in memory. Next, it initializes a code validator that uses regular expressions to verify the format of the contract code. Furthermore, it initializes the emotion engine and prepares a model (e.g., affectiva or DeepFace) for analyzing data such as the user's facial expressions, voice, and keystrokes. The input includes the action list, regular expression patterns, and the emotion engine model file, and the initialized various validation modules are obtained as output.

[0277] Step 2: Enter new contract information

[0278] The user enters contract information on the new contract registration screen. The input fields include a list of measures to be applied (e.g., "Measure A" and "Measure C") and a contract code (e.g., "ABC1234567"). The entered information is temporarily stored in the terminal's memory. The input includes the list of measures and the contract code from the user, and the data entered into the terminal is obtained as output.

[0279] Step 3: Submit new contract information

[0280] The terminal sends the contract information entered by the user to the server. This information is constructed as an HTTP request and passed to the server in JSON format. For example, the terminal sends the contract information using a "POST" request. The input contains the contract information entered on the terminal, and the output is the contract information sent to the server.

[0281] Step 4: Verify contract information

[0282] The server executes the validate_entry method to validate the received contract information. This method performs the following processes. First, it compares whether the input policy list matches the configured policy list, and generates an error message if any missing policies are detected. Next, it checks whether the contract code matches the specified format (regular expression pattern), and if it does not match, it generates an error message stating "The contract code is invalid." The input includes the contract information sent to the server, and the output is the policy check results and the contract code format check results.

[0283] Step 5: Recognize emotions

[0284] The server uses an emotion engine to recognize the emotions the user is inputting. For example, the server acquires data from a camera or microphone in real time and inputs it into an emotion recognition model to identify emotions. The input includes real-time data from the camera or microphone, and the output is the user's emotional state.

[0285] Step 6: Generate feedback

[0286] The server generates an appropriate feedback message based on the user's emotion detected by the emotion engine. For example, if the user is feeling frustrated, it generates an additional help message (e.g., "Are you having trouble? Click here for help.") The input includes the user's emotional state, and the output is the generated feedback message.

[0287] Step 7: Viewing validation results and feedback

[0288] The server notifies the user of the validation results and feedback. If there are error messages, the server sends the error messages and feedback messages to the user's terminal and displays them. If there are no error messages, the server displays the message "Validation was successful." The input includes the validation results and feedback messages, and the output is the message displayed on the user's terminal.

[0289] These are the specific processing steps of the program for this system. By clarifying the operations performed at each step and the associated inputs and outputs, it becomes easier to understand the overall flow of the system.

[0290] (Application example 2)

[0291] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0292] In electronic payment services, improving the user experience by preventing omissions in policy application and input errors that occur when registering a new account or entering transaction information is a challenge. In particular, reducing the stress and confusion that users feel while entering information is required. Current systems lack the functionality to detect policy application and input errors in real time, and furthermore, they lack feedback based on the user's emotions, which can lead to reduced user efficiency and satisfaction.

[0293] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0294] In this invention, the server includes means for receiving input transaction information, means for verifying the policy application status of the transaction information based on a list of policies, means for verifying the format of the transaction code, means for generating an error message if there is an error in the policy application or the transaction code, means for recognizing the emotion of the user while inputting the transaction information, means for generating appropriate feedback based on the emotion recognition result, and means for displaying the verification result. This enables early detection and correction of missed policy applications and input errors, and by providing appropriate feedback according to the user's emotions, it is possible to improve the user experience and business efficiency.

[0295] "Transaction information" refers to information related to the registration of a new account or a transaction in an electronic payment service, and is a concept that includes contract information.

[0296] A "policy list" refers to a set of policies or rules that should be applied to transaction information.

[0297] "Transaction code" refers to a formalized code assigned to transaction information for identification purposes.

[0298] "Error Message" means a message intended to notify a user of an error or inconsistency in entering or validating transaction information.

[0299] "Emotion recognition" refers to the process of analyzing data such as a user's facial expressions, voice, and keystrokes to identify their current emotional state.

[0300] "Feedback" refers to responsive messages containing advice or guidance provided to the user while they are typing.

[0301] "Verification result" refers to the pass / fail result obtained by the verification process of the transaction information, the policy list, and the transaction code.

[0302] The system of the present invention aims to improve the user experience by reducing errors in registering new accounts and inputting transaction information in electronic payment services. This system is realized through cooperation between servers, terminals, and users.

[0303] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for validating the format of the transaction code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the validation process and emotion recognition process are executed.

[0304] The user enters transaction information on the new account registration screen. This information includes a list of applied measures and transaction codes. For example, suppose the user applies "Measure A" and "Measure C" and enters transaction code "ABC1234567." This information is sent from the terminal to the server, and the verification process begins.

[0305] The server executes the validate_entry method to validate the received transaction information. First, it verifies whether the input action list matches the pre-defined action list. If a missing action is detected, it generates an error message for that action. Next, it checks whether the input transaction code follows the specified format. If the format does not match, it generates an error message.

[0306] The server also uses an emotion engine to recognize the user's emotions as they are being input. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. This emotion recognition uses a generative AI model using, for example, TENSORFLOW (registered trademark) or OpenCV. If the emotion engine detects the user's confusion or irritation, the server automatically generates additional help information or assistance messages and displays them to the user.

[0307] Specifically, consider the case where a user applies "Measure A" and "Measure C" and enters the transaction code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0308] 1. An omission of "Measure B" from the measure list is detected.

[0309] 2. The transaction code is verified to be in a valid format.

[0310] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0311] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by applying Measure B. In addition, by using the emotion engine, users can input transaction information smoothly and without stress.

[0312] Example prompt sentence:

[0313] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[0314] 1. Happiness

[0315] 2. Anger

[0316] 3. Confused

[0317] 4. Irritation

[0318] example:

[0319] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0320] Step 1:

[0321] The server sets up a policy list when the system starts up. This is the process of defining a series of policies to be applied to the system (e.g., "Policy A," "Policy B," "Policy C"). The input data is the policy list itself, which is output as the initial setting information for the entire system.

[0322] Step 2:

[0323] The server initializes a code validator to validate the format of the transaction code. This is to ensure that the transaction code matches a predefined format (e.g., length, string pattern). The input data is the transaction code format specification, and the code validator is prepared as output.

[0324] Step 3:

[0325] The server configures the emotion engine, which includes a generative AI model that analyzes the user's facial expressions, voice, keystrokes, etc. to identify emotions. The input data is the technology stack and the emotion analysis model itself, and the emotion engine is configured as the output.

[0326] Step 4:

[0327] The user opens a new account registration screen using a terminal and enters transaction information. The input data here is a list of measures and a transaction code. The transaction information entered by the user is output from the terminal and sent to the server.

[0328] Step 5:

[0329] The server executes the validate_entry method based on the received transaction information. First, it verifies whether the entered policy list matches the pre-defined policy list. The input data is the policy list entered by the user, and it is compared with the pre-defined policy list, and any mismatches are output.

[0330] Step 6:

[0331] The server checks whether the entered transaction code matches the specified format. The input data is a transaction code, which is verified using a code validator, and outputs an error message if it does not match.

[0332] Step 7:

[0333] The server recognizes the user's emotions using an emotion engine. Input data includes the user's facial expressions, voice, keystrokes, etc. The server identifies the emotion using the emotion engine and outputs that emotion.

[0334] Step 8:

[0335] The server generates appropriate feedback based on the detected user emotion. For example, if the user is feeling frustrated, it generates an auxiliary help message. The input data is the emotion detected in step 7, and the generated feedback is output.

[0336] Step 9:

[0337] The server notifies the user of all validation results and feedback. The input data are the validation results and feedback up to that point, and presents them to the user together.

[0338] Specifically, the following prompt sentences are used:

[0339] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[0340] 1. Happiness

[0341] 2. Anger

[0342] 3. Confused

[0343] 4. Irritation

[0344] example:

[0345] As a result, users can correct any missed measures or input errors, and receive appropriate support according to their emotions, allowing them to input transaction information smoothly.

[0346] The specific processing unit 290 transmits the result of the specific processing to the smart device 14. In the smart device 14, the control unit 46A causes the output device 40 to output the result of the specific processing. The microphone 38B acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0347] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (registered trademark) (Internet search engine).<URL: https: / / openai.com / blog / chatgpt> ), Gemini (registered trademark) (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0348] In the above embodiment, an example in which the specific process is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific process may be performed by the smart device 14.

[0349] [Second embodiment]

[0350] FIG. 3 shows an example of the configuration of a data processing system 210 according to the second embodiment.

[0351] 3, the data processing system 210 includes the data processing device 12 and smart glasses 214. An example of the data processing device 12 is a server.

[0352] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0353] The smart glasses 214 include a computer 36, a microphone 238, a speaker 240, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, and the camera 42 are also connected to the bus 52.

[0354] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0355] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0356] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0357] Fig. 4 shows an example of the main functions of the data processing device 12 and the smart glasses 214. As shown in Fig. 4, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0358] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0359] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0360] In the smart glasses 214, the processor 46 performs the reception output process. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0361] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the smart glasses 214 will be referred to as the "terminal."

[0362] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[0363] 1. System initialization

[0364] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, a code validator for validating the format of the contract code is initialized. Finally, an instance of the RegistrationSystem class is created based on this information. This instance is responsible for validating the contract information and generating error messages.

[0365] 2. Enter a new contract entry

[0366] The user enters contract information on the new contract registration screen. This information includes the list of policies to be applied (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[0367] 3. Submit a new contract entry

[0368] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[0369] 4. Entry Validation

[0370] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[0371] 4.1 Checking the application of measures

[0372] The server verifies that the input action list matches the pre-defined action list, and generates an error message if any missing actions are detected.

[0373] 4.2 Code Validation

[0374] The server checks whether the entered contract code complies with the required format, and generates an error message if the format does not match.

[0375] 5. Sending the verification results

[0376] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the contract information verification was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[0377] Specific examples

[0378] A specific example is shown below.

[0379] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0380] 1. Failure to apply Measure B is detected.

[0381] 2. The contract code is verified to be in a valid format.

[0382] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can apply Measure B additionally to complete the correction.

[0383] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, thereby reducing the number of cases that arise after the fact and improving business efficiency and service quality.

[0384] The processing flow will be explained below.

[0385] Step 1:

[0386] The server sets up a list of policies and a code validator when the system starts up, which prepares the basic information required for validating contract information and initializes an instance of the RegistrationSystem class.

[0387] Step 2:

[0388] The user operates the new contract registration screen and enters contract information. Specifically, the user enters the list of measures to be applied (for example, "Measure A" and "Measure C") and the contract code (for example, "ABC1234567").

[0389] Step 3:

[0390] The user sends the entered contract information to the server. At this time, the contract information is sent from the terminal to the server.

[0391] Step 4:

[0392] The server receives the contract information and calls the validate_entry method, which starts the validation process for the contract information.

[0393] Step 5:

[0394] The server checks the application of policies as part of the validation process. It compares the list of configured policies with the list of policies entered by the user to see if any policies are missing. If any policies are missing, it generates an error message for those policies.

[0395] Step 6:

[0396] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a predetermined format, and generates an error message if the format does not match.

[0397] Step 7:

[0398] The server compiles the results of the policy application and contract code verification and creates a list of error messages. If no error messages exist, it generates a message indicating that the contract information has been entered correctly.

[0399] Step 8:

[0400] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[0401] Step 9:

[0402] The user corrects the contract information as necessary based on the notification from the server, then submits the contract information again and performs verification again.

[0403] In this way, the server can check the appropriateness of new contract information in advance, and users can make necessary corrections based on the verification results, reducing errors. This process is expected to improve the accuracy of contract information and business efficiency.

[0404] Example 1

[0405] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0406] When registering a new contract, there is a possibility that measures may not be applied properly or that contract codes may be entered incorrectly. If these errors are not detected in advance, not only will the amount of work required to deal with them increase, reducing operational efficiency but also the quality of service. There is a need for a system that can solve this problem and detect errors in advance to reduce the number of cases that need to be dealt with.

[0407] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0408] In this invention, the server includes a processor that receives contract information, compares the list of measures included in the contract information with a list of measures to detect missing measures, and checks whether the contract code included in the contract information matches a predetermined format, a processor that verifies the policy application status of the contract information based on the list of measures, a processor that verifies the format of the contract code, a processor that generates and displays an error message on a user terminal if there is an error in the policy application or contract code, and a processor that displays the verification result.This makes it possible to detect and address missing measures and input errors in the contract code when registering a new contract in advance.

[0409] "Contract information" is information required to register a new contract, and includes a policy list and a contract code.

[0410] The "measure list" is a list of measures to be applied to the system, which are set based on specific conditions and rules.

[0411] The "contract code" is a code for uniquely identifying a contract, and is composed of a character string in a predetermined format.

[0412] A "processor" is a computing device that receives, processes, and transmits data and is the primary component for performing various functions of the system.

[0413] An "error message" is a notification that informs the user of any discrepancies or deficiencies detected during the verification process and prompts the user to correct them.

[0414] "User terminal" means a computing device through which a user accesses the system and enters or modifies contract information.

[0415] The "policy application status" is a status indicating whether the necessary policies are being applied based on the input contract information.

[0416] "Verification results" refers to information including conclusions and error messages resulting from the verification of contract information.

[0417] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting incorrect contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[0418] System initialization

[0419] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C"). This information is stored in the system's memory. Next, it sets up a code validator to validate the format of the contract code. The validator contains rules and regular expressions to check the accuracy of the contract code. Based on this information, it creates an instance of the RegistrationSystem class. This instance is responsible for validating the contract information and generating error messages.

[0420] Enter and submit a new contract entry

[0421] The user enters contract information on the device's new contract registration screen. Input fields include a list of measures to be applied (e.g., "Measure A," "Measure C") and a contract code (e.g., "ABC1234567"). This information is temporarily stored on the device, and then sent to the server when the user clicks the "Send" button. Data is generally sent in JSON or XML format.

[0422] Entry validation

[0423] The server executes the validate_entry method to validate the received contract information. First, it compares the entered policy list with the policy list configured in the system to detect any missing policies. For example, if a user selects "Policy A" and "Policy C" but does not apply "Policy B," an error message stating "Missing application: Policy B" is generated. Next, it checks whether the contract code matches the specified format. If the format does not match, an error message stating "Contract code is invalid" is generated.

[0424] Submitting and correcting validation results

[0425] The server compiles the verification results as an error message list. If there are no error messages, it generates a success message (e.g., "Contract information verification was successful") and sends it to the user's terminal. If there are error messages, each error message is listed and sent to the user. The user receives this and makes corrections based on the error content, such as adding measures or re-entering the contract code.

[0426] Specific examples

[0427] For example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server compares the list of measures and detects that "Measure B has not been applied." It also verifies that the contract code format is valid. As a result, an error message "Not applied: Measure B" is generated and sent to the user. The user receives this message, adds "Measure B," and submits the contract information again. After resubmission, if the verification is successful, the message "Contract information verification successful" is displayed.

[0428] Prompt Sentence Examples

[0429] Below are some example prompts for using a generative AI model:

[0430] We have developed a new system. This system aims to detect potential policy oversights and contract code input errors that may occur when registering new contracts, thereby reducing the number of cases we have to deal with. Please explain the process in natural language using the following steps:

[0431] 1. System initialization: When the server starts the system, it sets up the policy list and initializes the contract code validator. It creates an instance of the RegistrationSystem class.

[0432] 2. Entering a new contract entry: The user enters the policy list and contract code on the registration screen.

[0433] 3. Sending new contract entry: The contract information entered by the user is sent from the terminal to the server.

[0434] 4. Validate entry: The server uses the validate_entry method to check policy application and validate the code.

[0435] 5. Sending the verification result: The server sends an error message to the user.

[0436] For example, a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server detects that Measure B has not been applied and checks the format of the contract code. As a result, an error message "Missing application: Measure B" is generated.

[0437] The above is a detailed description of the "Mode for Carrying Out the Invention" of the system according to the present invention. This system makes it possible to detect missed measures and input errors in contract codes that may occur when registering a new contract, thereby improving business efficiency and service quality.

[0438] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0439] Step 1: Initialize the system

[0440] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C") and loads it into memory. Next, it sets up a code validator to verify the format of the contract code. This makes it possible to check the format of the contract code. Finally, it generates an instance of the RegistrationSystem class based on this information. The inputs are the statically defined list of measures and the regular expression pattern for the contract code. The output is that the RegistrationSystem instance is initialized.

[0441] Specific behavior: The server logs the message "Policy list and code validator initialized."

[0442] Step 2: Enter a new contract entry

[0443] The user enters contract information on the new contract registration screen on the terminal. Input items include a list of measures to be applied (e.g., "Measure A", "Measure C") and a contract code (e.g., "ABC1234567"). The input information is temporarily saved on the terminal. The input includes a list of measures selected by the user and a contract code. The output is the input information saved on the terminal.

[0444] Specific operation: The user enters the policy list and contract code on the screen and clicks the "Confirm" button.

[0445] Step 3: Submit a new contract entry

[0446] When the user clicks the "Send" button, the terminal sends the entered contract information to the server. The transmission format is generally JSON or XML. The input is the contract information stored on the terminal. The output is the contract information sent to the server.

[0447] Specific operation: The terminal displays a confirmation message to the server saying "Transmission completed."

[0448] Step 4: Validate your entries

[0449] The server validates the received contract information using the validate_entry method. The following specific processing is performed:

[0450] 1. Check the application of measures:

[0451] The server compares the input action list with a static action list and detects missing actions. For example, if "action A" and "action C" are selected but "action B" is not applied, an error message "Missing application: action B" is generated. The inputs are the action list sent by the user and the server's static action list. The output is a list of missing actions and an error message.

[0452] 2. Code validation:

[0453] The server checks whether the entered contract code matches the specified format. If it does not match, it generates an error message saying "The contract code is invalid." The inputs are the contract code sent by the user and the server's regular expression pattern. The output is the format check result and an error message.

[0454] Specific behavior: The server logs a "verification completed" message and generates a list of error messages.

[0455] Step 5: Submitting the verification results

[0456] The server compiles the verification results into an error message list. If this list is empty, a message stating "Contract information verification was successful" is generated and sent to the user. If error messages exist, each error message is listed and sent to the user. The input is the verification results. The output is either a list of error messages or a success message sent to the user.

[0457] Specific operation: The user terminal displays a confirmation message saying "Verification result received."

[0458] Step 6: Make corrections based on the results

[0459] The user corrects the contract information based on the error message. Specifically, they add missing measures or re-enter the contract code. After making the corrections, they press the "Send" button again to send the new contract information to the server. The inputs are the error message and the user's corrections. The output is that the corrected contract information is sent again to the server.

[0460] Specific behavior: The user makes corrections and clicks the "Submit" button again.

[0461] (Application example 1)

[0462] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0463] With the previous system, there was a problem of work efficiency decreasing when it came to missed policy applications or input errors in contract codes that could occur when registering new contracts. Furthermore, with electronic payment services, there was also the problem of input errors and incorrect information being registered when registering new payment methods. This resulted in a decline in service quality and usability issues.

[0464] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0465] In this invention, the server includes means for receiving input contract information and payment information, means for verifying the policy application status and payment method application status of the contract information based on a list of policies, means for verifying the format of the contract code and payment code, means for generating an error message if there is an error in the policy application or in the contract code or payment code, and means for displaying the verification result. This makes it possible to detect in advance the application of policies or input errors in the contract code or payment code when registering a new contract or new payment method, thereby improving business efficiency and service quality.

[0466] "Contract Information" is data entered by a user containing details of a new contract.

[0467] "Payment Information" means data containing details of a new payment method entered by a user.

[0468] A "list of measures" is a set of measures that are pre-configured in the system.

[0469] A "contract code" is a unique identifier associated with contract information.

[0470] "Payment Code" means a unique identifier associated with a payment method.

[0471] The "policy application status" is an index that indicates the application status of the policy in the contract information.

[0472] "Payment method application status" is an indicator that indicates the application status of the payment method in the payment information.

[0473] An "error message" is a notification to the user that the information they entered is incomplete.

[0474] "Verification results" are the results obtained after verifying the policy application status, contract code, and payment code.

[0475] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and input errors in contract codes and payment codes that occur when registering new contracts and new payment methods. This system is realized by linking a server and terminals.

[0476] 1. System initialization

[0477] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, various validators for verifying the format of the contract code and payment code are initialized. Finally, an instance of the SecurePayValidator class is created based on this information. This instance is responsible for validating the contract information and payment information and generating error messages.

[0478] 2. Entering new contract and settlement entries

[0479] The user enters contract information and payment information on the registration screen for a new contract and a new payment method. This information includes a list of policies to be applied (applied_policies), a list of payment methods (payment_methods), a contract code (contract_code), and a payment code (payment_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567" and payment code "1234567890123456."

[0480] 3. Submitting new contract and settlement entries

[0481] The contract information and payment information entered by the user are sent from the terminal to the server, which then starts the verification process for the contract information and payment information.

[0482] 4. Entry Validation

[0483] The server executes the validate_entry method to validate the received contract information and payment information. This method performs the following processes.

[0484] Checking the application of measures

[0485] The server verifies that the entered policy list and payment method list match the pre-defined list, and generates an error message if a missing policy or payment method is detected.

[0486] Code Validation

[0487] The server checks whether the entered contract code and payment code conform to the specified format. If the format does not match, an error message is generated.

[0488] 5. Sending the verification results

[0489] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the verification of the contract information and payment information was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[0490] Hardware and software used

[0491] Hardware:

[0492] Smartphone device: iOS or Android device

[0493] software:

[0494] Python: Used for backend validation

[0495] Regular Expressions (re module): Validate the format of each code

[0496] Specific examples

[0497] A specific example is shown below.

[0498] Example prompt sentence:

[0499] Enter your credit card details:

[0500] Card number (16 digits): 1234567890123456

[0501] Enter your e-money information:

[0502] Electronic money code (6-12 characters): ABCD-1234

[0503] Are there any omissions in applicable policies? (e.g. credit cards, electronic money)

[0504] Registration failed. Error message: [Invalid format: credit card payment code]

[0505] When a user registers a "credit card" and "electronic money" based on the above prompts, the system verifies whether the card number and electronic money code entered by the user are valid, and immediately notifies the user of an error message if there is any fraud.

[0506] This will enable the system to detect missed measures and input errors in contract codes and payment codes in advance when registering new contracts and new payment methods, improving business efficiency and service quality.

[0507] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0508] Step 1:

[0509] The terminal displays an input screen for the user to register a new contract and a new payment method. This screen displays fields for the user to enter a policy list, a payment method list, a contract code, and a payment code. As input, the user provides "Policy A," "Policy C," "Credit card," and the payment code "1234567890123456."

[0510] Step 2:

[0511] The user enters new contract information and payment information into the input screen. This includes the policy list to be applied, the payment method list, the contract code, and the payment code. The entered data includes the policy list, the payment method list, the contract code "ABC1234567", and the payment code "1234567890123456".

[0512] Step 3:

[0513] The terminal transmits the input contract information and payment information to the server. The input data includes the contract information and payment information input by the user. This data is transmitted to the server.

[0514] Step 4:

[0515] The server analyzes the received contract and payment information and calls the validate_entry method. The input data includes the contract and payment information. Based on this, the server begins validating the policy application status and code.

[0516] Step 5:

[0517] The server verifies the application status of the policies. Specifically, it compares the input policy list and payment method list with the pre-defined policy list and payment method list. If the comparison detects any missing policies or payment methods, it generates an error message.

[0518] Step 6:

[0519] The server validates the format of the contract code and payment code. Specifically, it checks whether each code matches the specified format. The input includes the contract code and payment code. If the formats do not match, an error message is generated.

[0520] Step 7:

[0521] The server compiles the verification results and constructs an error message list. The input includes the implementation status of the measures and the results of the formal verification of the code. If there are error messages, each error message is added to the error message list.

[0522] Step 8:

[0523] The server sends the verification results to the terminal, including as input a list of error messages, which are then communicated to the user, who receives information to make corrections.

[0524] Step 9:

[0525] The terminal displays the verification result received from the server to the user. The verification result from the server is included as input. If there is an error, an error message is displayed to the user, and the user can correct the information accordingly.

[0526] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[0527] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[0528] 1. System initialization

[0529] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[0530] 2. Enter a new contract entry

[0531] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[0532] 3. Submit a new contract entry

[0533] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[0534] 4. Entry Validation

[0535] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[0536] 4.1 Checking the application of measures

[0537] The server verifies that the input action list matches the pre-defined action list, and generates an error message for any missing action if any is detected.

[0538] 4.2 Code Validation

[0539] The server checks whether the entered contract code conforms to the specified format and generates an error message if the format does not match.

[0540] 5. Emotional Recognition

[0541] The server uses an emotion engine to recognize the emotions the user is expressing while typing. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions.

[0542] 6. Generate feedback

[0543] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user feels confused or frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[0544] 7. Sending the verification results

[0545] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[0546] Specific examples

[0547] A specific example is shown below.

[0548] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0549] 1. Failure to apply Measure B is detected.

[0550] 2. The contract code is verified to be in a valid format.

[0551] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0552] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[0553] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[0554] The processing flow will be explained below.

[0555] Step 1:

[0556] When the system starts up, the server sets up a list of measures, a code validator, and an emotion engine, which prepares the information necessary for validating contract information and recognizing user emotions.

[0557] Step 2:

[0558] The user operates the new contract registration screen and enters contract information, specifically the list of measures to be applied (e.g., "Measure A," "Measure C," etc.) and the contract code (e.g., "ABC1234567").

[0559] Step 3:

[0560] While the user is typing, the device collects data such as the user's facial expressions, voice, and keystrokes in real time and sends this data to the emotion engine.

[0561] Step 4:

[0562] The server receives the contract information sent by the user and invokes the validate_entry method to start the process of validating the contract information.

[0563] Step 5:

[0564] The server verifies the application status of the measures. It compares the input list of measures with the list of pre-defined measures to check whether any measures are missing. If a missing measure is detected, it generates an error message for that measure.

[0565] Step 6:

[0566] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a specified format, and generates an error message if the format does not match.

[0567] Step 7:

[0568] The server uses an emotion engine to recognize the user's emotions. It analyzes data such as facial expressions, voice, and keystrokes to determine whether the user is confused or frustrated. If the emotion engine detects a negative emotion, it generates appropriate feedback.

[0569] Step 8:

[0570] The server integrates the policy application status, the contract code verification results, and the emotion analysis results from the emotion engine to generate final feedback. If there are error messages, the feedback will include them. If negative emotions are detected, additional help information and assistance messages will also be included.

[0571] Step 9:

[0572] The server generates feedback and sends it to the user, which may include error messages to inform the user of what needs to be corrected, and may also display additional help or assistance messages.

[0573] Step 10:

[0574] The user makes the necessary corrections based on the feedback from the server. Once the corrections are complete, the user re-enters the contract information and submits it for verification again.

[0575] In this way, the server can proactively check the appropriateness of contract information and recognize the user's emotions, improving the user experience, reducing errors and increasing work efficiency.

[0576] Example 2

[0577] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0578] In the conventional contract registration system, it was easy for measures to be overlooked or contract codes to be entered incorrectly, and the accompanying error messages were insufficient, causing stress for users. In addition, the system handled issues without regard for user feelings, resulting in a poor user experience.

[0579] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes a means for receiving input contract information, a means for verifying the policy application status of the contract information based on the list of policies, a means for verifying the format of the contract code, a means for generating an error message if there is an error in the policy application or the contract code, a means for recognizing the user's emotions, a means for generating appropriate feedback based on the emotion recognition result, and a means for displaying the verification result and the feedback. This makes it possible to detect missed policy application or input errors in the contract code in advance, and further recognize the user's emotions and provide appropriate feedback.

[0580] "Contract information" refers to information that includes data regarding the establishment or modification of a contract.

[0581] A "measure list" refers to a list of measures and procedures that should be applied to a contract.

[0582] "Contract code" refers to a unique identifier for uniquely identifying contract information.

[0583] An "error message" refers to a warning or notification message that is displayed when the information entered by the user is incorrect.

[0584] "Emotion recognition" refers to the analysis of data such as a user's facial expressions, voice, and keystrokes to identify their emotional state.

[0585] "Feedback" refers to the response message or instructions provided to the user.

[0586] "Verification results" refers to information generated as a result of the system verifying the contract information entered.

[0587] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[0588] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[0589] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, if the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567," the user enters the list of applied policies and the contract code on the registration screen.

[0590] The contract information entered by the user is sent from the terminal to the server. This information is sent as an HTTP request and passed to the server in JSON format.

[0591] The server executes the validate_entry method to validate the received contract information. This method first checks whether the input policy list matches the configured policy list, and generates an error message if a missing policy is detected. Next, it checks whether the contract code conforms to the specified format, and generates an error message if the format does not match.

[0592] The server then uses an emotion engine to recognize the user's emotions as they are being input. It analyzes facial expressions, voice, keystrokes, and other data to identify the user's emotions. For example, it uses an emotion recognition system built using the Python library affectiva or DeepFace.

[0593] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user is feeling frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[0594] The server notifies the user of the validation results and feedback. If there are any error messages, it displays them to the user and prompts them to correct them. If there are no error messages, it displays a message that validation was successful.

[0595] As a concrete example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0596] 1. Failure to apply Measure B is detected.

[0597] 2. The contract code is verified to be in a valid format.

[0598] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0599] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[0600] Prompt sentence for generative AI model

[0601] I applied "Measure A" and "Measure C" and entered the contract code "ABC1234567", but please check for any missed measures or input errors in the contract code. Also, if the user is frustrated, please provide an appropriate help message.

[0602] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[0603] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0604] Step 1: Initialize the system

[0605] The server performs the following initialization process when the system starts up. First, it reads the action list (e.g., "Action A," "Action B," and "Action C") from the database or configuration file and stores this list in memory. Next, it initializes a code validator that uses regular expressions to verify the format of the contract code. Furthermore, it initializes the emotion engine and prepares a model (e.g., affectiva or DeepFace) for analyzing data such as the user's facial expressions, voice, and keystrokes. The input includes the action list, regular expression patterns, and the emotion engine model file, and the initialized various validation modules are obtained as output.

[0606] Step 2: Enter new contract information

[0607] The user enters contract information on the new contract registration screen. The input fields include a list of measures to be applied (e.g., "Measure A" and "Measure C") and a contract code (e.g., "ABC1234567"). The entered information is temporarily stored in the terminal's memory. The input includes the list of measures and the contract code from the user, and the data entered into the terminal is obtained as output.

[0608] Step 3: Submit new contract information

[0609] The terminal sends the contract information entered by the user to the server. This information is constructed as an HTTP request and passed to the server in JSON format. For example, the terminal sends the contract information using a "POST" request. The input contains the contract information entered on the terminal, and the output is the contract information sent to the server.

[0610] Step 4: Verify contract information

[0611] The server executes the validate_entry method to validate the received contract information. This method performs the following processes. First, it compares whether the input policy list matches the configured policy list, and generates an error message if any missing policies are detected. Next, it checks whether the contract code matches the specified format (regular expression pattern), and if it does not match, it generates an error message stating "The contract code is invalid." The input includes the contract information sent to the server, and the output is the policy check results and the contract code format check results.

[0612] Step 5: Recognize emotions

[0613] The server uses an emotion engine to recognize the emotions the user is inputting. For example, the server acquires data from a camera or microphone in real time and inputs it into an emotion recognition model to identify emotions. The input includes real-time data from the camera or microphone, and the output is the user's emotional state.

[0614] Step 6: Generate feedback

[0615] The server generates an appropriate feedback message based on the user's emotion detected by the emotion engine. For example, if the user is feeling frustrated, it generates an additional help message (e.g., "Are you having trouble? Click here for help.") The input includes the user's emotional state, and the output is the generated feedback message.

[0616] Step 7: Viewing validation results and feedback

[0617] The server notifies the user of the validation results and feedback. If there are error messages, the server sends the error messages and feedback messages to the user's terminal and displays them. If there are no error messages, the server displays the message "Validation was successful." The input includes the validation results and feedback messages, and the output is the message displayed on the user's terminal.

[0618] These are the specific processing steps of the program for this system. By clarifying the operations performed at each step and the associated inputs and outputs, it becomes easier to understand the overall flow of the system.

[0619] (Application example 2)

[0620] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0621] In electronic payment services, improving the user experience by preventing omissions in policy application and input errors that occur when registering a new account or entering transaction information is a challenge. In particular, reducing the stress and confusion that users feel while entering information is required. Current systems lack the functionality to detect policy application and input errors in real time, and furthermore, they lack feedback based on the user's emotions, which can lead to reduced user efficiency and satisfaction.

[0622] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0623] In this invention, the server includes means for receiving input transaction information, means for verifying the policy application status of the transaction information based on a list of policies, means for verifying the format of the transaction code, means for generating an error message if there is an error in the policy application or the transaction code, means for recognizing the emotion of the user while inputting the transaction information, means for generating appropriate feedback based on the emotion recognition result, and means for displaying the verification result. This enables early detection and correction of missed policy applications and input errors, and by providing appropriate feedback according to the user's emotions, it is possible to improve the user experience and business efficiency.

[0624] "Transaction information" refers to information related to the registration of a new account or a transaction in an electronic payment service, and is a concept that includes contract information.

[0625] A "policy list" refers to a set of policies or rules that should be applied to transaction information.

[0626] "Transaction code" refers to a formalized code assigned to transaction information for identification purposes.

[0627] "Error Message" means a message intended to notify a user of an error or inconsistency in entering or validating transaction information.

[0628] "Emotion recognition" refers to the process of analyzing data such as a user's facial expressions, voice, and keystrokes to identify their current emotional state.

[0629] "Feedback" refers to responsive messages containing advice or guidance provided to the user while they are typing.

[0630] "Verification result" refers to the pass / fail result obtained by the verification process of the transaction information, the policy list, and the transaction code.

[0631] The system of the present invention aims to improve the user experience by reducing errors in registering new accounts and inputting transaction information in electronic payment services. This system is realized through cooperation between servers, terminals, and users.

[0632] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for validating the format of the transaction code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the validation process and emotion recognition process are executed.

[0633] The user enters transaction information on the new account registration screen. This information includes a list of applied measures and transaction codes. For example, suppose the user applies "Measure A" and "Measure C" and enters transaction code "ABC1234567." This information is sent from the terminal to the server, and the verification process begins.

[0634] The server executes the validate_entry method to validate the received transaction information. First, it verifies whether the input action list matches the pre-defined action list. If a missing action is detected, it generates an error message for that action. Next, it checks whether the input transaction code follows the specified format. If the format does not match, it generates an error message.

[0635] The server also uses an emotion engine to recognize the user's emotions as they are being input. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. This emotion recognition uses generative AI models, such as TensorFlow and OpenCV. If the emotion engine detects the user's confusion or irritation, the server automatically generates additional help information or assistance messages and displays them to the user.

[0636] Specifically, consider the case where a user applies "Measure A" and "Measure C" and enters the transaction code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0637] 1. An omission of "Measure B" from the measure list is detected.

[0638] 2. The transaction code is verified to be in a valid format.

[0639] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0640] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by applying Measure B. In addition, by using the emotion engine, users can input transaction information smoothly and without stress.

[0641] Example prompt sentence:

[0642] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[0643] 1. Happiness

[0644] 2. Anger

[0645] 3. Confused

[0646] 4. Irritation

[0647] example:

[0648] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0649] Step 1:

[0650] The server sets up a policy list when the system starts up. This is the process of defining a series of policies to be applied to the system (e.g., "Policy A," "Policy B," "Policy C"). The input data is the policy list itself, which is output as the initial setting information for the entire system.

[0651] Step 2:

[0652] The server initializes a code validator to validate the format of the transaction code. This is to ensure that the transaction code matches a predefined format (e.g., length, string pattern). The input data is the transaction code format specification, and the code validator is prepared as output.

[0653] Step 3:

[0654] The server configures the emotion engine, which includes a generative AI model that analyzes the user's facial expressions, voice, keystrokes, etc. to identify emotions. The input data is the technology stack and the emotion analysis model itself, and the emotion engine is configured as the output.

[0655] Step 4:

[0656] The user opens a new account registration screen using a terminal and enters transaction information. The input data here is a list of measures and a transaction code. The transaction information entered by the user is output from the terminal and sent to the server.

[0657] Step 5:

[0658] The server executes the validate_entry method based on the received transaction information. First, it verifies whether the entered policy list matches the pre-defined policy list. The input data is the policy list entered by the user, and it is compared with the pre-defined policy list, and any mismatches are output.

[0659] Step 6:

[0660] The server checks whether the entered transaction code matches the specified format. The input data is a transaction code, which is verified using a code validator, and outputs an error message if it does not match.

[0661] Step 7:

[0662] The server recognizes the user's emotions using an emotion engine. Input data includes the user's facial expressions, voice, keystrokes, etc. The server identifies the emotion using the emotion engine and outputs that emotion.

[0663] Step 8:

[0664] The server generates appropriate feedback based on the detected user emotion. For example, if the user is feeling frustrated, it generates an auxiliary help message. The input data is the emotion detected in step 7, and the generated feedback is output.

[0665] Step 9:

[0666] The server notifies the user of all validation results and feedback. The input data are the validation results and feedback up to that point, and presents them to the user together.

[0667] Specifically, the following prompt sentences are used:

[0668] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[0669] 1. Happiness

[0670] 2. Anger

[0671] 3. Confused

[0672] 4. Irritation

[0673] example:

[0674] As a result, users can correct any missed measures or input errors, and receive appropriate support according to their emotions, allowing them to input transaction information smoothly.

[0675] The specific processing unit 290 transmits the result of the specific processing to the smart glasses 214. In the smart glasses 214, the control unit 46A causes the speaker 240 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0676] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0677] In the above embodiment, an example in which the specific processing is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the smart glasses 214.

[0678] [Third embodiment]

[0679] FIG. 5 shows an example of the configuration of a data processing system 310 according to the third embodiment.

[0680] 5, the data processing system 310 includes the data processing device 12 and a headset type terminal 314. An example of the data processing device 12 is a server.

[0681] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0682] The headset type terminal 314 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a display 343. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the display 343 are also connected to the bus 52.

[0683] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0684] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0685] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0686] Fig. 6 shows an example of the main functions of the data processing device 12 and the headset type terminal 314. As shown in Fig. 6, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0687] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0688] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0689] In the headset type terminal 314, a reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0690] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the headset type terminal 314 will be referred to as the "terminal."

[0691] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[0692] 1. System initialization

[0693] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, a code validator for validating the format of the contract code is initialized. Finally, an instance of the RegistrationSystem class is created based on this information. This instance is responsible for validating the contract information and generating error messages.

[0694] 2. Enter a new contract entry

[0695] The user enters contract information on the new contract registration screen. This information includes the list of policies to be applied (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[0696] 3. Submit a new contract entry

[0697] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[0698] 4. Entry Validation

[0699] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[0700] 4.1 Checking the application of measures

[0701] The server verifies that the input action list matches the pre-defined action list, and generates an error message if any missing actions are detected.

[0702] 4.2 Code Validation

[0703] The server checks whether the entered contract code complies with the required format, and generates an error message if the format does not match.

[0704] 5. Sending the verification results

[0705] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the contract information verification was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[0706] Specific examples

[0707] A specific example is shown below.

[0708] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0709] 1. Failure to apply Measure B is detected.

[0710] 2. The contract code is verified to be in a valid format.

[0711] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can apply Measure B additionally to complete the correction.

[0712] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, thereby reducing the number of cases that arise after the fact and improving business efficiency and service quality.

[0713] The processing flow will be explained below.

[0714] Step 1:

[0715] The server sets up a list of policies and a code validator when the system starts up, which prepares the basic information required for validating contract information and initializes an instance of the RegistrationSystem class.

[0716] Step 2:

[0717] The user operates the new contract registration screen and enters contract information. Specifically, the user enters the list of measures to be applied (for example, "Measure A" and "Measure C") and the contract code (for example, "ABC1234567").

[0718] Step 3:

[0719] The user sends the entered contract information to the server. At this time, the contract information is sent from the terminal to the server.

[0720] Step 4:

[0721] The server receives the contract information and calls the validate_entry method, which starts the validation process for the contract information.

[0722] Step 5:

[0723] The server checks the application of policies as part of the validation process. It compares the list of configured policies with the list of policies entered by the user to see if any policies are missing. If any policies are missing, it generates an error message for those policies.

[0724] Step 6:

[0725] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a predetermined format, and generates an error message if the format does not match.

[0726] Step 7:

[0727] The server compiles the results of the policy application and contract code verification and creates a list of error messages. If no error messages exist, it generates a message indicating that the contract information has been entered correctly.

[0728] Step 8:

[0729] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[0730] Step 9:

[0731] The user corrects the contract information as necessary based on the notification from the server, then submits the contract information again and performs verification again.

[0732] In this way, the server can check the appropriateness of new contract information in advance, and users can make necessary corrections based on the verification results, reducing errors. This process is expected to improve the accuracy of contract information and business efficiency.

[0733] Example 1

[0734] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[0735] When registering a new contract, there is a possibility that measures may not be applied properly or that contract codes may be entered incorrectly. If these errors are not detected in advance, not only will the amount of work required to deal with them increase, reducing operational efficiency but also the quality of service. There is a need for a system that can solve this problem and detect errors in advance to reduce the number of cases that need to be dealt with.

[0736] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0737] In this invention, the server includes a processor that receives contract information, compares the list of measures included in the contract information with a list of measures to detect missing measures, and checks whether the contract code included in the contract information matches a predetermined format, a processor that verifies the policy application status of the contract information based on the list of measures, a processor that verifies the format of the contract code, a processor that generates and displays an error message on a user terminal if there is an error in the policy application or contract code, and a processor that displays the verification result.This makes it possible to detect and address missing measures and input errors in the contract code when registering a new contract in advance.

[0738] "Contract information" is information required to register a new contract, and includes a policy list and a contract code.

[0739] The "measure list" is a list of measures to be applied to the system, which are set based on specific conditions and rules.

[0740] The "contract code" is a code for uniquely identifying a contract, and is composed of a character string in a predetermined format.

[0741] A "processor" is a computing device that receives, processes, and transmits data and is the primary component for performing various functions of the system.

[0742] An "error message" is a notification that informs the user of any discrepancies or deficiencies detected during the verification process and prompts the user to correct them.

[0743] "User terminal" means a computing device through which a user accesses the system and enters or modifies contract information.

[0744] The "policy application status" is a status indicating whether the necessary policies are being applied based on the input contract information.

[0745] "Verification results" refers to information including conclusions and error messages resulting from the verification of contract information.

[0746] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting incorrect contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[0747] System initialization

[0748] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C"). This information is stored in the system's memory. Next, it sets up a code validator to validate the format of the contract code. The validator contains rules and regular expressions to check the accuracy of the contract code. Based on this information, it creates an instance of the RegistrationSystem class. This instance is responsible for validating the contract information and generating error messages.

[0749] Enter and submit a new contract entry

[0750] The user enters contract information on the device's new contract registration screen. Input fields include a list of measures to be applied (e.g., "Measure A," "Measure C") and a contract code (e.g., "ABC1234567"). This information is temporarily stored on the device, and then sent to the server when the user clicks the "Send" button. Data is generally sent in JSON or XML format.

[0751] Entry validation

[0752] The server executes the validate_entry method to validate the received contract information. First, it compares the entered policy list with the policy list configured in the system to detect any missing policies. For example, if a user selects "Policy A" and "Policy C" but does not apply "Policy B," an error message stating "Missing application: Policy B" is generated. Next, it checks whether the contract code matches the specified format. If the format does not match, an error message stating "Contract code is invalid" is generated.

[0753] Submitting and correcting validation results

[0754] The server compiles the verification results as an error message list. If there are no error messages, it generates a success message (e.g., "Contract information verification was successful") and sends it to the user's terminal. If there are error messages, each error message is listed and sent to the user. The user receives this and makes corrections based on the error content, such as adding measures or re-entering the contract code.

[0755] Specific examples

[0756] For example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server compares the list of measures and detects that "Measure B has not been applied." It also verifies that the contract code format is valid. As a result, an error message "Not applied: Measure B" is generated and sent to the user. The user receives this message, adds "Measure B," and submits the contract information again. After resubmission, if the verification is successful, the message "Contract information verification successful" is displayed.

[0757] Prompt Sentence Examples

[0758] Below are some example prompts for using a generative AI model:

[0759] We have developed a new system. This system aims to detect potential policy oversights and contract code input errors that may occur when registering new contracts, thereby reducing the number of cases we have to deal with. Please explain the process in natural language using the following steps:

[0760] 1. System initialization: When the server starts the system, it sets up the policy list and initializes the contract code validator. It creates an instance of the RegistrationSystem class.

[0761] 2. Entering a new contract entry: The user enters the policy list and contract code on the registration screen.

[0762] 3. Sending new contract entry: The contract information entered by the user is sent from the terminal to the server.

[0763] 4. Validate entry: The server uses the validate_entry method to check policy application and validate the code.

[0764] 5. Sending the verification result: The server sends an error message to the user.

[0765] For example, a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server detects that Measure B has not been applied and checks the format of the contract code. As a result, an error message "Missing application: Measure B" is generated.

[0766] The above is a detailed description of the "Mode for Carrying Out the Invention" of the system according to the present invention. This system makes it possible to detect missed measures and input errors in contract codes that may occur when registering a new contract, thereby improving business efficiency and service quality.

[0767] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0768] Step 1: Initialize the system

[0769] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C") and loads it into memory. Next, it sets up a code validator to verify the format of the contract code. This makes it possible to check the format of the contract code. Finally, it generates an instance of the RegistrationSystem class based on this information. The inputs are the statically defined list of measures and the regular expression pattern for the contract code. The output is that the RegistrationSystem instance is initialized.

[0770] Specific behavior: The server logs the message "Policy list and code validator initialized."

[0771] Step 2: Enter a new contract entry

[0772] The user enters contract information on the new contract registration screen on the terminal. Input items include a list of measures to be applied (e.g., "Measure A", "Measure C") and a contract code (e.g., "ABC1234567"). The input information is temporarily saved on the terminal. The input includes a list of measures selected by the user and a contract code. The output is the input information saved on the terminal.

[0773] Specific operation: The user enters the policy list and contract code on the screen and clicks the "Confirm" button.

[0774] Step 3: Submit a new contract entry

[0775] When the user clicks the "Send" button, the terminal sends the entered contract information to the server. The transmission format is generally JSON or XML. The input is the contract information stored on the terminal. The output is the contract information sent to the server.

[0776] Specific operation: The terminal displays a confirmation message to the server saying "Transmission completed."

[0777] Step 4: Validate your entries

[0778] The server validates the received contract information using the validate_entry method. The following specific processing is performed:

[0779] 1. Check the application of measures:

[0780] The server compares the input action list with a static action list and detects missing actions. For example, if "action A" and "action C" are selected but "action B" is not applied, an error message "Missing application: action B" is generated. The inputs are the action list sent by the user and the server's static action list. The output is a list of missing actions and an error message.

[0781] 2. Code validation:

[0782] The server checks whether the entered contract code matches the specified format. If it does not match, it generates an error message saying "The contract code is invalid." The inputs are the contract code sent by the user and the server's regular expression pattern. The output is the format check result and an error message.

[0783] Specific behavior: The server logs a "verification completed" message and generates a list of error messages.

[0784] Step 5: Submitting the verification results

[0785] The server compiles the verification results into an error message list. If this list is empty, a message stating "Contract information verification was successful" is generated and sent to the user. If error messages exist, each error message is listed and sent to the user. The input is the verification results. The output is either a list of error messages or a success message sent to the user.

[0786] Specific operation: The user terminal displays a confirmation message saying "Verification result received."

[0787] Step 6: Make corrections based on the results

[0788] The user corrects the contract information based on the error message. Specifically, they add missing measures or re-enter the contract code. After making the corrections, they press the "Send" button again to send the new contract information to the server. The inputs are the error message and the user's corrections. The output is that the corrected contract information is sent again to the server.

[0789] Specific behavior: The user makes corrections and clicks the "Submit" button again.

[0790] (Application example 1)

[0791] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[0792] With the previous system, there was a problem of work efficiency decreasing when it came to missed policy applications or input errors in contract codes that could occur when registering new contracts. Furthermore, with electronic payment services, there was also the problem of input errors and incorrect information being registered when registering new payment methods. This resulted in a decline in service quality and usability issues.

[0793] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0794] In this invention, the server includes means for receiving input contract information and payment information, means for verifying the policy application status and payment method application status of the contract information based on a list of policies, means for verifying the format of the contract code and payment code, means for generating an error message if there is an error in the policy application or in the contract code or payment code, and means for displaying the verification result. This makes it possible to detect in advance the application of policies or input errors in the contract code or payment code when registering a new contract or new payment method, thereby improving business efficiency and service quality.

[0795] "Contract Information" is data entered by a user containing details of a new contract.

[0796] "Payment Information" means data containing details of a new payment method entered by a user.

[0797] A "list of measures" is a set of measures that are pre-configured in the system.

[0798] A "contract code" is a unique identifier associated with contract information.

[0799] "Payment Code" means a unique identifier associated with a payment method.

[0800] The "policy application status" is an index that indicates the application status of the policy in the contract information.

[0801] "Payment method application status" is an indicator that indicates the application status of the payment method in the payment information.

[0802] An "error message" is a notification to the user that the information they entered is incomplete.

[0803] "Verification results" are the results obtained after verifying the policy application status, contract code, and payment code.

[0804] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and input errors in contract codes and payment codes that occur when registering new contracts and new payment methods. This system is realized by linking a server and terminals.

[0805] 1. System initialization

[0806] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, various validators for verifying the format of the contract code and payment code are initialized. Finally, an instance of the SecurePayValidator class is created based on this information. This instance is responsible for validating the contract information and payment information and generating error messages.

[0807] 2. Entering new contract and settlement entries

[0808] The user enters contract information and payment information on the registration screen for a new contract and a new payment method. This information includes a list of policies to be applied (applied_policies), a list of payment methods (payment_methods), a contract code (contract_code), and a payment code (payment_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567" and payment code "1234567890123456."

[0809] 3. Submitting new contract and settlement entries

[0810] The contract information and payment information entered by the user are sent from the terminal to the server, which then starts the verification process for the contract information and payment information.

[0811] 4. Entry Validation

[0812] The server executes the validate_entry method to validate the received contract information and payment information. This method performs the following processes.

[0813] Checking the application of measures

[0814] The server verifies that the entered policy list and payment method list match the pre-defined list, and generates an error message if a missing policy or payment method is detected.

[0815] Code Validation

[0816] The server checks whether the entered contract code and payment code conform to the specified format. If the format does not match, an error message is generated.

[0817] 5. Sending the verification results

[0818] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the verification of the contract information and payment information was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[0819] Hardware and software used

[0820] Hardware:

[0821] Smartphone device: iOS or Android device

[0822] software:

[0823] Python: Used for backend validation

[0824] Regular Expressions (re module): Validate the format of each code

[0825] Specific examples

[0826] A specific example is shown below.

[0827] Example prompt sentence:

[0828] Enter your credit card details:

[0829] Card number (16 digits): 1234567890123456

[0830] Enter your e-money information:

[0831] Electronic money code (6-12 characters): ABCD-1234

[0832] Are there any omissions in applicable policies? (e.g. credit cards, electronic money)

[0833] Registration failed. Error message: [Invalid format: credit card payment code]

[0834] When a user registers a "credit card" and "electronic money" based on the above prompts, the system verifies whether the card number and electronic money code entered by the user are valid, and immediately notifies the user of an error message if there is any fraud.

[0835] This will enable the system to detect missed measures and input errors in contract codes and payment codes in advance when registering new contracts and new payment methods, improving business efficiency and service quality.

[0836] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0837] Step 1:

[0838] The terminal displays an input screen for the user to register a new contract and a new payment method. This screen displays fields for the user to enter a policy list, a payment method list, a contract code, and a payment code. As input, the user provides "Policy A," "Policy C," "Credit card," and the payment code "1234567890123456."

[0839] Step 2:

[0840] The user enters new contract information and payment information into the input screen. This includes the policy list to be applied, the payment method list, the contract code, and the payment code. The entered data includes the policy list, the payment method list, the contract code "ABC1234567", and the payment code "1234567890123456".

[0841] Step 3:

[0842] The terminal transmits the input contract information and payment information to the server. The input data includes the contract information and payment information input by the user. This data is transmitted to the server.

[0843] Step 4:

[0844] The server analyzes the received contract and payment information and calls the validate_entry method. The input data includes the contract and payment information. Based on this, the server begins validating the policy application status and code.

[0845] Step 5:

[0846] The server verifies the application status of the policies. Specifically, it compares the input policy list and payment method list with the pre-defined policy list and payment method list. If the comparison detects any missing policies or payment methods, it generates an error message.

[0847] Step 6:

[0848] The server validates the format of the contract code and payment code. Specifically, it checks whether each code matches the specified format. The input includes the contract code and payment code. If the formats do not match, an error message is generated.

[0849] Step 7:

[0850] The server compiles the verification results and constructs an error message list. The input includes the implementation status of the measures and the results of the formal verification of the code. If there are error messages, each error message is added to the error message list.

[0851] Step 8:

[0852] The server sends the verification results to the terminal, including as input a list of error messages, which are then communicated to the user, who receives information to make corrections.

[0853] Step 9:

[0854] The terminal displays the verification result received from the server to the user. The verification result from the server is included as input. If there is an error, an error message is displayed to the user, and the user can correct the information accordingly.

[0855] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[0856] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[0857] 1. System initialization

[0858] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[0859] 2. Enter a new contract entry

[0860] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[0861] 3. Submit a new contract entry

[0862] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[0863] 4. Entry Validation

[0864] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[0865] 4.1 Checking the application of measures

[0866] The server verifies that the input action list matches the pre-defined action list, and generates an error message for any missing action if any is detected.

[0867] 4.2 Code Validation

[0868] The server checks whether the entered contract code conforms to the specified format and generates an error message if the format does not match.

[0869] 5. Emotional Recognition

[0870] The server uses an emotion engine to recognize the emotions the user is expressing while typing. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions.

[0871] 6. Generate feedback

[0872] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user feels confused or frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[0873] 7. Sending the verification results

[0874] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[0875] Specific examples

[0876] A specific example is shown below.

[0877] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0878] 1. Failure to apply Measure B is detected.

[0879] 2. The contract code is verified to be in a valid format.

[0880] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0881] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[0882] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[0883] The processing flow will be explained below.

[0884] Step 1:

[0885] When the system starts up, the server sets up a list of measures, a code validator, and an emotion engine, which prepares the information necessary for validating contract information and recognizing user emotions.

[0886] Step 2:

[0887] The user operates the new contract registration screen and enters contract information, specifically the list of measures to be applied (e.g., "Measure A," "Measure C," etc.) and the contract code (e.g., "ABC1234567").

[0888] Step 3:

[0889] While the user is typing, the device collects data such as the user's facial expressions, voice, and keystrokes in real time and sends this data to the emotion engine.

[0890] Step 4:

[0891] The server receives the contract information sent by the user and invokes the validate_entry method to start the process of validating the contract information.

[0892] Step 5:

[0893] The server verifies the application status of the measures. It compares the input list of measures with the list of pre-defined measures to check whether any measures are missing. If a missing measure is detected, it generates an error message for that measure.

[0894] Step 6:

[0895] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a specified format, and generates an error message if the format does not match.

[0896] Step 7:

[0897] The server uses an emotion engine to recognize the user's emotions. It analyzes data such as facial expressions, voice, and keystrokes to determine whether the user is confused or frustrated. If the emotion engine detects a negative emotion, it generates appropriate feedback.

[0898] Step 8:

[0899] The server integrates the policy application status, the contract code verification results, and the emotion analysis results from the emotion engine to generate final feedback. If there are error messages, the feedback will include them. If negative emotions are detected, additional help information and assistance messages will also be included.

[0900] Step 9:

[0901] The server generates feedback and sends it to the user, which may include error messages to inform the user of what needs to be corrected, and may also display additional help or assistance messages.

[0902] Step 10:

[0903] The user makes the necessary corrections based on the feedback from the server. Once the corrections are complete, the user re-enters the contract information and submits it for verification again.

[0904] In this way, the server can proactively check the appropriateness of contract information and recognize the user's emotions, improving the user experience, reducing errors and increasing work efficiency.

[0905] Example 2

[0906] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[0907] In the conventional contract registration system, it was easy for measures to be overlooked or contract codes to be entered incorrectly, and the accompanying error messages were insufficient, causing stress for users. In addition, the system handled issues without regard for user feelings, resulting in a poor user experience.

[0908] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes a means for receiving input contract information, a means for verifying the policy application status of the contract information based on the list of policies, a means for verifying the format of the contract code, a means for generating an error message if there is an error in the policy application or the contract code, a means for recognizing the user's emotions, a means for generating appropriate feedback based on the emotion recognition result, and a means for displaying the verification result and the feedback. This makes it possible to detect missed policy application or input errors in the contract code in advance, and further recognize the user's emotions and provide appropriate feedback.

[0909] "Contract information" refers to information that includes data regarding the establishment or modification of a contract.

[0910] A "measure list" refers to a list of measures and procedures that should be applied to a contract.

[0911] "Contract code" refers to a unique identifier for uniquely identifying contract information.

[0912] An "error message" refers to a warning or notification message that is displayed when the information entered by the user is incorrect.

[0913] "Emotion recognition" refers to the analysis of data such as a user's facial expressions, voice, and keystrokes to identify their emotional state.

[0914] "Feedback" refers to the response message or instructions provided to the user.

[0915] "Verification results" refers to information generated as a result of the system verifying the contract information entered.

[0916] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[0917] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[0918] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, if the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567," the user enters the list of applied policies and the contract code on the registration screen.

[0919] The contract information entered by the user is sent from the terminal to the server. This information is sent as an HTTP request and passed to the server in JSON format.

[0920] The server executes the validate_entry method to validate the received contract information. This method first checks whether the input policy list matches the configured policy list, and generates an error message if a missing policy is detected. Next, it checks whether the contract code conforms to the specified format, and generates an error message if the format does not match.

[0921] The server then uses an emotion engine to recognize the user's emotions as they are being input. It analyzes facial expressions, voice, keystrokes, and other data to identify the user's emotions. For example, it uses an emotion recognition system built using the Python library affectiva or DeepFace.

[0922] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user is feeling frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[0923] The server notifies the user of the validation results and feedback. If there are any error messages, it displays them to the user and prompts them to correct them. If there are no error messages, it displays a message that validation was successful.

[0924] As a concrete example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0925] 1. Failure to apply Measure B is detected.

[0926] 2. The contract code is verified to be in a valid format.

[0927] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0928] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[0929] Prompt sentence for generative AI model

[0930] I applied "Measure A" and "Measure C" and entered the contract code "ABC1234567", but please check for any missed measures or input errors in the contract code. Also, if the user is frustrated, please provide an appropriate help message.

[0931] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[0932] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0933] Step 1: Initialize the system

[0934] The server performs the following initialization process when the system starts up. First, it reads the action list (e.g., "Action A," "Action B," and "Action C") from the database or configuration file and stores this list in memory. Next, it initializes a code validator that uses regular expressions to verify the format of the contract code. Furthermore, it initializes the emotion engine and prepares a model (e.g., affectiva or DeepFace) for analyzing data such as the user's facial expressions, voice, and keystrokes. The input includes the action list, regular expression patterns, and the emotion engine model file, and the initialized various validation modules are obtained as output.

[0935] Step 2: Enter new contract information

[0936] The user enters contract information on the new contract registration screen. The input fields include a list of measures to be applied (e.g., "Measure A" and "Measure C") and a contract code (e.g., "ABC1234567"). The entered information is temporarily stored in the terminal's memory. The input includes the list of measures and the contract code from the user, and the data entered into the terminal is obtained as output.

[0937] Step 3: Submit new contract information

[0938] The terminal sends the contract information entered by the user to the server. This information is constructed as an HTTP request and passed to the server in JSON format. For example, the terminal sends the contract information using a "POST" request. The input contains the contract information entered on the terminal, and the output is the contract information sent to the server.

[0939] Step 4: Verify contract information

[0940] The server executes the validate_entry method to validate the received contract information. This method performs the following processes. First, it compares whether the input policy list matches the configured policy list, and generates an error message if any missing policies are detected. Next, it checks whether the contract code matches the specified format (regular expression pattern), and if it does not match, it generates an error message stating "The contract code is invalid." The input includes the contract information sent to the server, and the output is the policy check results and the contract code format check results.

[0941] Step 5: Recognize emotions

[0942] The server uses an emotion engine to recognize the emotions the user is inputting. For example, the server acquires data from a camera or microphone in real time and inputs it into an emotion recognition model to identify emotions. The input includes real-time data from the camera or microphone, and the output is the user's emotional state.

[0943] Step 6: Generate feedback

[0944] The server generates an appropriate feedback message based on the user's emotion detected by the emotion engine. For example, if the user is feeling frustrated, it generates an additional help message (e.g., "Are you having trouble? Click here for help.") The input includes the user's emotional state, and the output is the generated feedback message.

[0945] Step 7: Viewing validation results and feedback

[0946] The server notifies the user of the validation results and feedback. If there are error messages, the server sends the error messages and feedback messages to the user's terminal and displays them. If there are no error messages, the server displays the message "Validation was successful." The input includes the validation results and feedback messages, and the output is the message displayed on the user's terminal.

[0947] These are the specific processing steps of the program for this system. By clarifying the operations performed at each step and the associated inputs and outputs, it becomes easier to understand the overall flow of the system.

[0948] (Application example 2)

[0949] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[0950] In electronic payment services, improving the user experience by preventing omissions in policy application and input errors that occur when registering a new account or entering transaction information is a challenge. In particular, reducing the stress and confusion that users feel while entering information is required. Current systems lack the functionality to detect policy application and input errors in real time, and furthermore, they lack feedback based on the user's emotions, which can lead to reduced user efficiency and satisfaction.

[0951] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0952] In this invention, the server includes means for receiving input transaction information, means for verifying the policy application status of the transaction information based on a list of policies, means for verifying the format of the transaction code, means for generating an error message if there is an error in the policy application or the transaction code, means for recognizing the emotion of the user while inputting the transaction information, means for generating appropriate feedback based on the emotion recognition result, and means for displaying the verification result. This enables early detection and correction of missed policy applications and input errors, and by providing appropriate feedback according to the user's emotions, it is possible to improve the user experience and business efficiency.

[0953] "Transaction information" refers to information related to the registration of a new account or a transaction in an electronic payment service, and is a concept that includes contract information.

[0954] A "policy list" refers to a set of policies or rules that should be applied to transaction information.

[0955] "Transaction code" refers to a formalized code assigned to transaction information for identification purposes.

[0956] "Error Message" means a message intended to notify a user of an error or inconsistency in entering or validating transaction information.

[0957] "Emotion recognition" refers to the process of analyzing data such as a user's facial expressions, voice, and keystrokes to identify their current emotional state.

[0958] "Feedback" refers to responsive messages containing advice or guidance provided to the user while they are typing.

[0959] "Verification result" refers to the pass / fail result obtained by the verification process of the transaction information, the policy list, and the transaction code.

[0960] The system of the present invention aims to improve the user experience by reducing errors in registering new accounts and inputting transaction information in electronic payment services. This system is realized through cooperation between servers, terminals, and users.

[0961] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for validating the format of the transaction code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the validation process and emotion recognition process are executed.

[0962] The user enters transaction information on the new account registration screen. This information includes a list of applied measures and transaction codes. For example, suppose the user applies "Measure A" and "Measure C" and enters transaction code "ABC1234567." This information is sent from the terminal to the server, and the verification process begins.

[0963] The server executes the validate_entry method to validate the received transaction information. First, it verifies whether the input action list matches the pre-defined action list. If a missing action is detected, it generates an error message for that action. Next, it checks whether the input transaction code follows the specified format. If the format does not match, it generates an error message.

[0964] The server also uses an emotion engine to recognize the user's emotions as they are being input. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. This emotion recognition uses generative AI models, such as TensorFlow and OpenCV. If the emotion engine detects the user's confusion or irritation, the server automatically generates additional help information or assistance messages and displays them to the user.

[0965] Specifically, consider the case where a user applies "Measure A" and "Measure C" and enters the transaction code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[0966] 1. An omission of "Measure B" from the measure list is detected.

[0967] 2. The transaction code is verified to be in a valid format.

[0968] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[0969] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by applying Measure B. In addition, by using the emotion engine, users can input transaction information smoothly and without stress.

[0970] Example prompt sentence:

[0971] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[0972] 1. Happiness

[0973] 2. Anger

[0974] 3. Confused

[0975] 4. Irritation

[0976] example:

[0977] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0978] Step 1:

[0979] The server sets up a policy list when the system starts up. This is the process of defining a series of policies to be applied to the system (e.g., "Policy A," "Policy B," "Policy C"). The input data is the policy list itself, which is output as the initial setting information for the entire system.

[0980] Step 2:

[0981] The server initializes a code validator to validate the format of the transaction code. This is to ensure that the transaction code matches a predefined format (e.g., length, string pattern). The input data is the transaction code format specification, and the code validator is prepared as output.

[0982] Step 3:

[0983] The server configures the emotion engine, which includes a generative AI model that analyzes the user's facial expressions, voice, keystrokes, etc. to identify emotions. The input data is the technology stack and the emotion analysis model itself, and the emotion engine is configured as the output.

[0984] Step 4:

[0985] The user opens a new account registration screen using a terminal and enters transaction information. The input data here is a list of measures and a transaction code. The transaction information entered by the user is output from the terminal and sent to the server.

[0986] Step 5:

[0987] The server executes the validate_entry method based on the received transaction information. First, it verifies whether the entered policy list matches the pre-defined policy list. The input data is the policy list entered by the user, and it is compared with the pre-defined policy list, and any mismatches are output.

[0988] Step 6:

[0989] The server checks whether the entered transaction code matches the specified format. The input data is a transaction code, which is verified using a code validator, and outputs an error message if it does not match.

[0990] Step 7:

[0991] The server recognizes the user's emotions using an emotion engine. Input data includes the user's facial expressions, voice, keystrokes, etc. The server identifies the emotion using the emotion engine and outputs that emotion.

[0992] Step 8:

[0993] The server generates appropriate feedback based on the detected user emotion. For example, if the user is feeling frustrated, it generates an auxiliary help message. The input data is the emotion detected in step 7, and the generated feedback is output.

[0994] Step 9:

[0995] The server notifies the user of all validation results and feedback. The input data are the validation results and feedback up to that point, and presents them to the user together.

[0996] Specifically, the following prompt sentences are used:

[0997] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[0998] 1. Happiness

[0999] 2. Anger

[1000] 3. Confused

[1001] 4. Irritation

[1002] example:

[1003] As a result, users can correct any missed measures or input errors, and receive appropriate support according to their emotions, allowing them to input transaction information smoothly.

[1004] The specific processing unit 290 transmits the result of the specific processing to the headset type terminal 314. In the headset type terminal 314, the control unit 46A causes the speaker 240 and the display 343 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[1005] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[1006] In the above embodiment, an example was given in which the specific processing is performed by the data processing device 12, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the headset type terminal 314.

[1007] [Fourth embodiment]

[1008] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.

[1009] 7, a data processing system 410 includes a data processing device 12 and a robot 414. An example of the data processing device 12 is a server.

[1010] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[1011] The robot 414 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a control target 443. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the control target 443 are also connected to the bus 52.

[1012] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[1013] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[1014] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[1015] The control object 443 includes a display device, LEDs in the eyes, and motors for driving the arms, hands, and feet. The posture and gestures of the robot 414 are controlled by controlling the motors of the arms, hands, and feet. Some of the emotions of the robot 414 can be expressed by controlling these motors. In addition, the facial expressions of the robot 414 can also be expressed by controlling the light emission state of the LEDs in the eyes of the robot 414.

[1016] Fig. 8 shows an example of the main functions of the data processing device 12 and the robot 414. As shown in Fig. 8, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[1017] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[1018] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[1019] In the robot 414, the processor 46 performs the reception output process. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[1020] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1021] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[1022] 1. System initialization

[1023] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, a code validator for validating the format of the contract code is initialized. Finally, an instance of the RegistrationSystem class is created based on this information. This instance is responsible for validating the contract information and generating error messages.

[1024] 2. Enter a new contract entry

[1025] The user enters contract information on the new contract registration screen. This information includes the list of policies to be applied (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[1026] 3. Submit a new contract entry

[1027] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[1028] 4. Entry Validation

[1029] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[1030] 4.1 Checking the application of measures

[1031] The server verifies that the input action list matches the pre-defined action list, and generates an error message if any missing actions are detected.

[1032] 4.2 Code Validation

[1033] The server checks whether the entered contract code complies with the required format, and generates an error message if the format does not match.

[1034] 5. Sending the verification results

[1035] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the contract information verification was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[1036] Specific examples

[1037] A specific example is shown below.

[1038] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[1039] 1. Failure to apply Measure B is detected.

[1040] 2. The contract code is verified to be in a valid format.

[1041] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can apply Measure B additionally to complete the correction.

[1042] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, thereby reducing the number of cases that arise after the fact and improving business efficiency and service quality.

[1043] The processing flow will be explained below.

[1044] Step 1:

[1045] The server sets up a list of policies and a code validator when the system starts up, which prepares the basic information required for validating contract information and initializes an instance of the RegistrationSystem class.

[1046] Step 2:

[1047] The user operates the new contract registration screen and enters contract information. Specifically, the user enters the list of measures to be applied (for example, "Measure A" and "Measure C") and the contract code (for example, "ABC1234567").

[1048] Step 3:

[1049] The user sends the entered contract information to the server. At this time, the contract information is sent from the terminal to the server.

[1050] Step 4:

[1051] The server receives the contract information and calls the validate_entry method, which starts the validation process for the contract information.

[1052] Step 5:

[1053] The server checks the application of policies as part of the validation process. It compares the list of configured policies with the list of policies entered by the user to see if any policies are missing. If any policies are missing, it generates an error message for those policies.

[1054] Step 6:

[1055] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a predetermined format, and generates an error message if the format does not match.

[1056] Step 7:

[1057] The server compiles the results of the policy application and contract code verification and creates a list of error messages. If no error messages exist, it generates a message indicating that the contract information has been entered correctly.

[1058] Step 8:

[1059] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[1060] Step 9:

[1061] The user corrects the contract information as necessary based on the notification from the server, then submits the contract information again and performs verification again.

[1062] In this way, the server can check the appropriateness of new contract information in advance, and users can make necessary corrections based on the verification results, reducing errors. This process is expected to improve the accuracy of contract information and business efficiency.

[1063] Example 1

[1064] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1065] When registering a new contract, there is a possibility that measures may not be applied properly or that contract codes may be entered incorrectly. If these errors are not detected in advance, not only will the amount of work required to deal with them increase, reducing operational efficiency but also the quality of service. There is a need for a system that can solve this problem and detect errors in advance to reduce the number of cases that need to be dealt with.

[1066] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[1067] In this invention, the server includes a processor that receives contract information, compares the list of measures included in the contract information with a list of measures to detect missing measures, and checks whether the contract code included in the contract information matches a predetermined format, a processor that verifies the policy application status of the contract information based on the list of measures, a processor that verifies the format of the contract code, a processor that generates and displays an error message on a user terminal if there is an error in the policy application or contract code, and a processor that displays the verification result.This makes it possible to detect and address missing measures and input errors in the contract code when registering a new contract in advance.

[1068] "Contract information" is information required to register a new contract, and includes a policy list and a contract code.

[1069] The "measure list" is a list of measures to be applied to the system, which are set based on specific conditions and rules.

[1070] The "contract code" is a code for uniquely identifying a contract, and is composed of a character string in a predetermined format.

[1071] A "processor" is a computing device that receives, processes, and transmits data and is the primary component for performing various functions of the system.

[1072] An "error message" is a notification that informs the user of any discrepancies or deficiencies detected during the verification process and prompts the user to correct them.

[1073] "User terminal" means a computing device through which a user accesses the system and enters or modifies contract information.

[1074] The "policy application status" is a status indicating whether the necessary policies are being applied based on the input contract information.

[1075] "Verification results" refers to information including conclusions and error messages resulting from the verification of contract information.

[1076] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures or inputting incorrect contract codes that may occur when registering a new contract. This system is realized by linking a server and terminals.

[1077] System initialization

[1078] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C"). This information is stored in the system's memory. Next, it sets up a code validator to validate the format of the contract code. The validator contains rules and regular expressions to check the accuracy of the contract code. Based on this information, it creates an instance of the RegistrationSystem class. This instance is responsible for validating the contract information and generating error messages.

[1079] Enter and submit a new contract entry

[1080] The user enters contract information on the device's new contract registration screen. Input fields include a list of measures to be applied (e.g., "Measure A," "Measure C") and a contract code (e.g., "ABC1234567"). This information is temporarily stored on the device, and then sent to the server when the user clicks the "Send" button. Data is generally sent in JSON or XML format.

[1081] Entry validation

[1082] The server executes the validate_entry method to validate the received contract information. First, it compares the entered policy list with the policy list configured in the system to detect any missing policies. For example, if a user selects "Policy A" and "Policy C" but does not apply "Policy B," an error message stating "Missing application: Policy B" is generated. Next, it checks whether the contract code matches the specified format. If the format does not match, an error message stating "Contract code is invalid" is generated.

[1083] Submitting and correcting validation results

[1084] The server compiles the verification results as an error message list. If there are no error messages, it generates a success message (e.g., "Contract information verification was successful") and sends it to the user's terminal. If there are error messages, each error message is listed and sent to the user. The user receives this and makes corrections based on the error content, such as adding measures or re-entering the contract code.

[1085] Specific examples

[1086] For example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server compares the list of measures and detects that "Measure B has not been applied." It also verifies that the contract code format is valid. As a result, an error message "Not applied: Measure B" is generated and sent to the user. The user receives this message, adds "Measure B," and submits the contract information again. After resubmission, if the verification is successful, the message "Contract information verification successful" is displayed.

[1087] Prompt Sentence Examples

[1088] Below are some example prompts for using a generative AI model:

[1089] We have developed a new system. This system aims to detect potential policy oversights and contract code input errors that may occur when registering new contracts, thereby reducing the number of cases we have to deal with. Please explain the process in natural language using the following steps:

[1090] 1. System initialization: When the server starts the system, it sets up the policy list and initializes the contract code validator. It creates an instance of the RegistrationSystem class.

[1091] 2. Entering a new contract entry: The user enters the policy list and contract code on the registration screen.

[1092] 3. Sending new contract entry: The contract information entered by the user is sent from the terminal to the server.

[1093] 4. Validate entry: The server uses the validate_entry method to check policy application and validate the code.

[1094] 5. Sending the verification result: The server sends an error message to the user.

[1095] For example, a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server detects that Measure B has not been applied and checks the format of the contract code. As a result, an error message "Missing application: Measure B" is generated.

[1096] The above is a detailed description of the "Mode for Carrying Out the Invention" of the system according to the present invention. This system makes it possible to detect missed measures and input errors in contract codes that may occur when registering a new contract, thereby improving business efficiency and service quality.

[1097] The flow of the identification process in the first embodiment will be described with reference to FIG.

[1098] Step 1: Initialize the system

[1099] When the system starts up, the server first sets up a list of measures (e.g., "Measure A," "Measure B," and "Measure C") and loads it into memory. Next, it sets up a code validator to verify the format of the contract code. This makes it possible to check the format of the contract code. Finally, it generates an instance of the RegistrationSystem class based on this information. The inputs are the statically defined list of measures and the regular expression pattern for the contract code. The output is that the RegistrationSystem instance is initialized.

[1100] Specific behavior: The server logs the message "Policy list and code validator initialized."

[1101] Step 2: Enter a new contract entry

[1102] The user enters contract information on the new contract registration screen on the terminal. Input items include a list of measures to be applied (e.g., "Measure A", "Measure C") and a contract code (e.g., "ABC1234567"). The input information is temporarily saved on the terminal. The input includes a list of measures selected by the user and a contract code. The output is the input information saved on the terminal.

[1103] Specific operation: The user enters the policy list and contract code on the screen and clicks the "Confirm" button.

[1104] Step 3: Submit a new contract entry

[1105] When the user clicks the "Send" button, the terminal sends the entered contract information to the server. The transmission format is generally JSON or XML. The input is the contract information stored on the terminal. The output is the contract information sent to the server.

[1106] Specific operation: The terminal displays a confirmation message to the server saying "Transmission completed."

[1107] Step 4: Validate your entries

[1108] The server validates the received contract information using the validate_entry method. The following specific processing is performed:

[1109] 1. Check the application of measures:

[1110] The server compares the input action list with a static action list and detects missing actions. For example, if "action A" and "action C" are selected but "action B" is not applied, an error message "Missing application: action B" is generated. The inputs are the action list sent by the user and the server's static action list. The output is a list of missing actions and an error message.

[1111] 2. Code validation:

[1112] The server checks whether the entered contract code matches the specified format. If it does not match, it generates an error message saying "The contract code is invalid." The inputs are the contract code sent by the user and the server's regular expression pattern. The output is the format check result and an error message.

[1113] Specific behavior: The server logs a "verification completed" message and generates a list of error messages.

[1114] Step 5: Submitting the verification results

[1115] The server compiles the verification results into an error message list. If this list is empty, a message stating "Contract information verification was successful" is generated and sent to the user. If error messages exist, each error message is listed and sent to the user. The input is the verification results. The output is either a list of error messages or a success message sent to the user.

[1116] Specific operation: The user terminal displays a confirmation message saying "Verification result received."

[1117] Step 6: Make corrections based on the results

[1118] The user corrects the contract information based on the error message. Specifically, they add missing measures or re-enter the contract code. After making the corrections, they press the "Send" button again to send the new contract information to the server. The inputs are the error message and the user's corrections. The output is that the corrected contract information is sent again to the server.

[1119] Specific behavior: The user makes corrections and clicks the "Submit" button again.

[1120] (Application example 1)

[1121] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1122] With the previous system, there was a problem of work efficiency decreasing when it came to missed policy applications or input errors in contract codes that could occur when registering new contracts. Furthermore, with electronic payment services, there was also the problem of input errors and incorrect information being registered when registering new payment methods. This resulted in a decline in service quality and usability issues.

[1123] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1124] In this invention, the server includes means for receiving input contract information and payment information, means for verifying the policy application status and payment method application status of the contract information based on a list of policies, means for verifying the format of the contract code and payment code, means for generating an error message if there is an error in the policy application or in the contract code or payment code, and means for displaying the verification result. This makes it possible to detect in advance the application of policies or input errors in the contract code or payment code when registering a new contract or new payment method, thereby improving business efficiency and service quality.

[1125] "Contract Information" is data entered by a user containing details of a new contract.

[1126] "Payment Information" means data containing details of a new payment method entered by a user.

[1127] A "list of measures" is a set of measures that are pre-configured in the system.

[1128] A "contract code" is a unique identifier associated with contract information.

[1129] "Payment Code" means a unique identifier associated with a payment method.

[1130] The "policy application status" is an index that indicates the application status of the policy in the contract information.

[1131] "Payment method application status" is an indicator that indicates the application status of the payment method in the payment information.

[1132] An "error message" is a notification to the user that the information they entered is incomplete.

[1133] "Verification results" are the results obtained after verifying the policy application status, contract code, and payment code.

[1134] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and input errors in contract codes and payment codes that occur when registering new contracts and new payment methods. This system is realized by linking a server and terminals.

[1135] 1. System initialization

[1136] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," "Measure C," etc.) is set. Next, various validators for verifying the format of the contract code and payment code are initialized. Finally, an instance of the SecurePayValidator class is created based on this information. This instance is responsible for validating the contract information and payment information and generating error messages.

[1137] 2. Entering new contract and settlement entries

[1138] The user enters contract information and payment information on the registration screen for a new contract and a new payment method. This information includes a list of policies to be applied (applied_policies), a list of payment methods (payment_methods), a contract code (contract_code), and a payment code (payment_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567" and payment code "1234567890123456."

[1139] 3. Submitting new contract and settlement entries

[1140] The contract information and payment information entered by the user are sent from the terminal to the server, which then starts the verification process for the contract information and payment information.

[1141] 4. Entry Validation

[1142] The server executes the validate_entry method to validate the received contract information and payment information. This method performs the following processes.

[1143] Checking the application of measures

[1144] The server verifies that the entered policy list and payment method list match the pre-defined list, and generates an error message if a missing policy or payment method is detected.

[1145] Code Validation

[1146] The server checks whether the entered contract code and payment code conform to the specified format. If the format does not match, an error message is generated.

[1147] 5. Sending the verification results

[1148] The server compiles the verification results into an error message list. If this list is empty, a message indicating that the verification of the contract information and payment information was successful is sent to the user. If there are error messages, each error message is presented to the user, and the user can make corrections based on the error message.

[1149] Hardware and software used

[1150] Hardware:

[1151] Smartphone device: iOS or Android device

[1152] software:

[1153] Python: Used for backend validation

[1154] Regular Expressions (re module): Validate the format of each code

[1155] Specific examples

[1156] A specific example is shown below.

[1157] Example prompt sentence:

[1158] Enter your credit card details:

[1159] Card number (16 digits): 1234567890123456

[1160] Enter your e-money information:

[1161] Electronic money code (6-12 characters): ABCD-1234

[1162] Are there any omissions in applicable policies? (e.g. credit cards, electronic money)

[1163] Registration failed. Error message: [Invalid format: credit card payment code]

[1164] When a user registers a "credit card" and "electronic money" based on the above prompts, the system verifies whether the card number and electronic money code entered by the user are valid, and immediately notifies the user of an error message if there is any fraud.

[1165] This will enable the system to detect missed measures and input errors in contract codes and payment codes in advance when registering new contracts and new payment methods, improving business efficiency and service quality.

[1166] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1167] Step 1:

[1168] The terminal displays an input screen for the user to register a new contract and a new payment method. This screen displays fields for the user to enter a policy list, a payment method list, a contract code, and a payment code. As input, the user provides "Policy A," "Policy C," "Credit card," and the payment code "1234567890123456."

[1169] Step 2:

[1170] The user enters new contract information and payment information into the input screen. This includes the policy list to be applied, the payment method list, the contract code, and the payment code. The entered data includes the policy list, the payment method list, the contract code "ABC1234567", and the payment code "1234567890123456".

[1171] Step 3:

[1172] The terminal transmits the input contract information and payment information to the server. The input data includes the contract information and payment information input by the user. This data is transmitted to the server.

[1173] Step 4:

[1174] The server analyzes the received contract and payment information and calls the validate_entry method. The input data includes the contract and payment information. Based on this, the server begins validating the policy application status and code.

[1175] Step 5:

[1176] The server verifies the application status of the policies. Specifically, it compares the input policy list and payment method list with the pre-defined policy list and payment method list. If the comparison detects any missing policies or payment methods, it generates an error message.

[1177] Step 6:

[1178] The server validates the format of the contract code and payment code. Specifically, it checks whether each code matches the specified format. The input includes the contract code and payment code. If the formats do not match, an error message is generated.

[1179] Step 7:

[1180] The server compiles the verification results and constructs an error message list. The input includes the implementation status of the measures and the results of the formal verification of the code. If there are error messages, each error message is added to the error message list.

[1181] Step 8:

[1182] The server sends the verification results to the terminal, including as input a list of error messages, which are then communicated to the user, who receives information to make corrections.

[1183] Step 9:

[1184] The terminal displays the verification result received from the server to the user. The verification result from the server is included as input. If there is an error, an error message is displayed to the user, and the user can correct the information accordingly.

[1185] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1186] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[1187] 1. System initialization

[1188] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[1189] 2. Enter a new contract entry

[1190] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, suppose the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567."

[1191] 3. Submit a new contract entry

[1192] The contract information entered by the user is sent from the terminal to the server, which then starts the verification process for the contract information.

[1193] 4. Entry Validation

[1194] The server executes the validate_entry method to validate the received contract information. This method performs the following processes:

[1195] 4.1 Checking the application of measures

[1196] The server verifies that the input action list matches the pre-defined action list, and generates an error message for any missing action if any is detected.

[1197] 4.2 Code Validation

[1198] The server checks whether the entered contract code conforms to the specified format and generates an error message if the format does not match.

[1199] 5. Emotional Recognition

[1200] The server uses an emotion engine to recognize the emotions the user is expressing while typing. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions.

[1201] 6. Generate feedback

[1202] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user feels confused or frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[1203] 7. Sending the verification results

[1204] The server notifies the user of the validation results. If there are any error messages, the server displays them to the user and prompts them to correct them. If there are no error messages, the server displays a message indicating that the validation was successful.

[1205] Specific examples

[1206] A specific example is shown below.

[1207] Consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[1208] 1. Failure to apply Measure B is detected.

[1209] 2. The contract code is verified to be in a valid format.

[1210] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[1211] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[1212] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[1213] The processing flow will be explained below.

[1214] Step 1:

[1215] When the system starts up, the server sets up a list of measures, a code validator, and an emotion engine, which prepares the information necessary for validating contract information and recognizing user emotions.

[1216] Step 2:

[1217] The user operates the new contract registration screen and enters contract information, specifically the list of measures to be applied (e.g., "Measure A," "Measure C," etc.) and the contract code (e.g., "ABC1234567").

[1218] Step 3:

[1219] While the user is typing, the device collects data such as the user's facial expressions, voice, and keystrokes in real time and sends this data to the emotion engine.

[1220] Step 4:

[1221] The server receives the contract information sent by the user and invokes the validate_entry method to start the process of validating the contract information.

[1222] Step 5:

[1223] The server verifies the application status of the measures. It compares the input list of measures with the list of pre-defined measures to check whether any measures are missing. If a missing measure is detected, it generates an error message for that measure.

[1224] Step 6:

[1225] The server validates the format of the contract code. Specifically, it checks whether the entered contract code conforms to a specified format, and generates an error message if the format does not match.

[1226] Step 7:

[1227] The server uses an emotion engine to recognize the user's emotions. It analyzes data such as facial expressions, voice, and keystrokes to determine whether the user is confused or frustrated. If the emotion engine detects a negative emotion, it generates appropriate feedback.

[1228] Step 8:

[1229] The server integrates the policy application status, the contract code verification results, and the emotion analysis results from the emotion engine to generate final feedback. If there are error messages, the feedback will include them. If negative emotions are detected, additional help information and assistance messages will also be included.

[1230] Step 9:

[1231] The server generates feedback and sends it to the user, which may include error messages to inform the user of what needs to be corrected, and may also display additional help or assistance messages.

[1232] Step 10:

[1233] The user makes the necessary corrections based on the feedback from the server. Once the corrections are complete, the user re-enters the contract information and submits it for verification again.

[1234] In this way, the server can proactively check the appropriateness of contract information and recognize the user's emotions, improving the user experience, reducing errors and increasing work efficiency.

[1235] Example 2

[1236] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1237] In the conventional contract registration system, it was easy for measures to be overlooked or contract codes to be entered incorrectly, and the accompanying error messages were insufficient, causing stress for users. In addition, the system handled issues without regard for user feelings, resulting in a poor user experience.

[1238] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes a means for receiving input contract information, a means for verifying the policy application status of the contract information based on the list of policies, a means for verifying the format of the contract code, a means for generating an error message if there is an error in the policy application or the contract code, a means for recognizing the user's emotions, a means for generating appropriate feedback based on the emotion recognition result, and a means for displaying the verification result and the feedback. This makes it possible to detect missed policy application or input errors in the contract code in advance, and further recognize the user's emotions and provide appropriate feedback.

[1239] "Contract information" refers to information that includes data regarding the establishment or modification of a contract.

[1240] A "measure list" refers to a list of measures and procedures that should be applied to a contract.

[1241] "Contract code" refers to a unique identifier for uniquely identifying contract information.

[1242] An "error message" refers to a warning or notification message that is displayed when the information entered by the user is incorrect.

[1243] "Emotion recognition" refers to the analysis of data such as a user's facial expressions, voice, and keystrokes to identify their emotional state.

[1244] "Feedback" refers to the response message or instructions provided to the user.

[1245] "Verification results" refers to information generated as a result of the system verifying the contract information entered.

[1246] The system of the present invention aims to reduce the number of cases by detecting in advance the omission of measures and inputting contract codes that may occur when registering a new contract, and by recognizing the user's emotions and providing appropriate feedback. This system is realized through cooperation between the server, terminals, and users.

[1247] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for verifying the format of the contract code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the verification process and emotion recognition process are executed.

[1248] The user enters contract information on the new contract registration screen. This information includes the list of applied policies (applied_policies) and the contract code (contract_code). For example, if the user applies "Policy A" and "Policy C" and enters contract code "ABC1234567," the user enters the list of applied policies and the contract code on the registration screen.

[1249] The contract information entered by the user is sent from the terminal to the server. This information is sent as an HTTP request and passed to the server in JSON format.

[1250] The server executes the validate_entry method to validate the received contract information. This method first checks whether the input policy list matches the configured policy list, and generates an error message if a missing policy is detected. Next, it checks whether the contract code conforms to the specified format, and generates an error message if the format does not match.

[1251] The server then uses an emotion engine to recognize the user's emotions as they are being input. It analyzes facial expressions, voice, keystrokes, and other data to identify the user's emotions. For example, it uses an emotion recognition system built using the Python library affectiva or DeepFace.

[1252] The server generates appropriate feedback based on the user's emotions detected by the emotion engine. For example, if the user is feeling frustrated, it automatically displays additional help information or assistance messages. This allows the user to receive appropriate instructions and smoothly enter contract information.

[1253] The server notifies the user of the validation results and feedback. If there are any error messages, it displays them to the user and prompts them to correct them. If there are no error messages, it displays a message that validation was successful.

[1254] As a concrete example, consider the case where a user applies "Measure A" and "Measure C" and enters contract code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[1255] 1. Failure to apply Measure B is detected.

[1256] 2. The contract code is verified to be in a valid format.

[1257] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[1258] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by additionally applying Measure B. In addition, by using the emotion engine, the user can smoothly input contract information without feeling stressed.

[1259] Prompt sentence for generative AI model

[1260] I applied "Measure A" and "Measure C" and entered the contract code "ABC1234567", but please check for any missed measures or input errors in the contract code. Also, if the user is frustrated, please provide an appropriate help message.

[1261] As described above, the system of the present invention detects in advance any missed measures or input errors in contract codes when registering new contracts, and furthermore, recognizes the user's emotions and provides appropriate feedback, thereby reducing the number of cases to be handled and improving business efficiency and service quality.

[1262] The flow of the identification process in the second embodiment will be described with reference to FIG.

[1263] Step 1: Initialize the system

[1264] The server performs the following initialization process when the system starts up. First, it reads the action list (e.g., "Action A," "Action B," and "Action C") from the database or configuration file and stores this list in memory. Next, it initializes a code validator that uses regular expressions to verify the format of the contract code. Furthermore, it initializes the emotion engine and prepares a model (e.g., affectiva or DeepFace) for analyzing data such as the user's facial expressions, voice, and keystrokes. The input includes the action list, regular expression patterns, and the emotion engine model file, and the initialized various validation modules are obtained as output.

[1265] Step 2: Enter new contract information

[1266] The user enters contract information on the new contract registration screen. The input fields include a list of measures to be applied (e.g., "Measure A" and "Measure C") and a contract code (e.g., "ABC1234567"). The entered information is temporarily stored in the terminal's memory. The input includes the list of measures and the contract code from the user, and the data entered into the terminal is obtained as output.

[1267] Step 3: Submit new contract information

[1268] The terminal sends the contract information entered by the user to the server. This information is constructed as an HTTP request and passed to the server in JSON format. For example, the terminal sends the contract information using a "POST" request. The input contains the contract information entered on the terminal, and the output is the contract information sent to the server.

[1269] Step 4: Verify contract information

[1270] The server executes the validate_entry method to validate the received contract information. This method performs the following processes. First, it compares whether the input policy list matches the configured policy list, and generates an error message if any missing policies are detected. Next, it checks whether the contract code matches the specified format (regular expression pattern), and if it does not match, it generates an error message stating "The contract code is invalid." The input includes the contract information sent to the server, and the output is the policy check results and the contract code format check results.

[1271] Step 5: Recognize emotions

[1272] The server uses an emotion engine to recognize the emotions the user is inputting. For example, the server acquires data from a camera or microphone in real time and inputs it into an emotion recognition model to identify emotions. The input includes real-time data from the camera or microphone, and the output is the user's emotional state.

[1273] Step 6: Generate feedback

[1274] The server generates an appropriate feedback message based on the user's emotion detected by the emotion engine. For example, if the user is feeling frustrated, it generates an additional help message (e.g., "Are you having trouble? Click here for help.") The input includes the user's emotional state, and the output is the generated feedback message.

[1275] Step 7: Viewing validation results and feedback

[1276] The server notifies the user of the validation results and feedback. If there are error messages, the server sends the error messages and feedback messages to the user's terminal and displays them. If there are no error messages, the server displays the message "Validation was successful." The input includes the validation results and feedback messages, and the output is the message displayed on the user's terminal.

[1277] These are the specific processing steps of the program for this system. By clarifying the operations performed at each step and the associated inputs and outputs, it becomes easier to understand the overall flow of the system.

[1278] (Application example 2)

[1279] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1280] In electronic payment services, improving the user experience by preventing omissions in policy application and input errors that occur when registering a new account or entering transaction information is a challenge. In particular, reducing the stress and confusion that users feel while entering information is required. Current systems lack the functionality to detect policy application and input errors in real time, and furthermore, they lack feedback based on the user's emotions, which can lead to reduced user efficiency and satisfaction.

[1281] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[1282] In this invention, the server includes means for receiving input transaction information, means for verifying the policy application status of the transaction information based on a list of policies, means for verifying the format of the transaction code, means for generating an error message if there is an error in the policy application or the transaction code, means for recognizing the emotion of the user while inputting the transaction information, means for generating appropriate feedback based on the emotion recognition result, and means for displaying the verification result. This enables early detection and correction of missed policy applications and input errors, and by providing appropriate feedback according to the user's emotions, it is possible to improve the user experience and business efficiency.

[1283] "Transaction information" refers to information related to the registration of a new account or a transaction in an electronic payment service, and is a concept that includes contract information.

[1284] A "policy list" refers to a set of policies or rules that should be applied to transaction information.

[1285] "Transaction code" refers to a formalized code assigned to transaction information for identification purposes.

[1286] "Error Message" means a message intended to notify a user of an error or inconsistency in entering or validating transaction information.

[1287] "Emotion recognition" refers to the process of analyzing data such as a user's facial expressions, voice, and keystrokes to identify their current emotional state.

[1288] "Feedback" refers to responsive messages containing advice or guidance provided to the user while they are typing.

[1289] "Verification result" refers to the pass / fail result obtained by the verification process of the transaction information, the policy list, and the transaction code.

[1290] The system of the present invention aims to improve the user experience by reducing errors in registering new accounts and inputting transaction information in electronic payment services. This system is realized through cooperation between servers, terminals, and users.

[1291] The server performs the following initialization process when the system starts up. First, a list of measures to be applied to the system (for example, "Measure A," "Measure B," and "Measure C") is set. Next, a code validator for validating the format of the transaction code is initialized. Furthermore, an emotion engine for recognizing the user's emotions is set. This emotion engine analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. An instance of the RegistrationSystem class is created, and the validation process and emotion recognition process are executed.

[1292] The user enters transaction information on the new account registration screen. This information includes a list of applied measures and transaction codes. For example, suppose the user applies "Measure A" and "Measure C" and enters transaction code "ABC1234567." This information is sent from the terminal to the server, and the verification process begins.

[1293] The server executes the validate_entry method to validate the received transaction information. First, it verifies whether the input action list matches the pre-defined action list. If a missing action is detected, it generates an error message for that action. Next, it checks whether the input transaction code follows the specified format. If the format does not match, it generates an error message.

[1294] The server also uses an emotion engine to recognize the user's emotions as they are being input. It analyzes data such as facial expressions, voice, and keystrokes to identify the user's emotions. This emotion recognition uses generative AI models, such as TensorFlow and OpenCV. If the emotion engine detects the user's confusion or irritation, the server automatically generates additional help information or assistance messages and displays them to the user.

[1295] Specifically, consider the case where a user applies "Measure A" and "Measure C" and enters the transaction code "ABC1234567." When this information is sent to the server, the server performs the following verification:

[1296] 1. An omission of "Measure B" from the measure list is detected.

[1297] 2. The transaction code is verified to be in a valid format.

[1298] 3. The emotion engine analyzes the user's emotions and if the user is feeling frustrated, an additional help message is displayed.

[1299] As a result, an error message "Missing application: Measure B" is generated and notified to the user. Based on this, the user can complete the correction by applying Measure B. In addition, by using the emotion engine, users can input transaction information smoothly and without stress.

[1300] Example prompt sentence:

[1301] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[1302] 1. Happiness

[1303] 2. Anger

[1304] 3. Confused

[1305] 4. Irritation

[1306] example:

[1307] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[1308] Step 1:

[1309] The server sets up a policy list when the system starts up. This is the process of defining a series of policies to be applied to the system (e.g., "Policy A," "Policy B," "Policy C"). The input data is the policy list itself, which is output as the initial setting information for the entire system.

[1310] Step 2:

[1311] The server initializes a code validator to validate the format of the transaction code. This is to ensure that the transaction code matches a predefined format (e.g., length, string pattern). The input data is the transaction code format specification, and the code validator is prepared as output.

[1312] Step 3:

[1313] The server configures the emotion engine, which includes a generative AI model that analyzes the user's facial expressions, voice, keystrokes, etc. to identify emotions. The input data is the technology stack and the emotion analysis model itself, and the emotion engine is configured as the output.

[1314] Step 4:

[1315] The user opens a new account registration screen using a terminal and enters transaction information. The input data here is a list of measures and a transaction code. The transaction information entered by the user is output from the terminal and sent to the server.

[1316] Step 5:

[1317] The server executes the validate_entry method based on the received transaction information. First, it verifies whether the entered policy list matches the pre-defined policy list. The input data is the policy list entered by the user, and it is compared with the pre-defined policy list, and any mismatches are output.

[1318] Step 6:

[1319] The server checks whether the entered transaction code matches the specified format. The input data is a transaction code, which is verified using a code validator, and outputs an error message if it does not match.

[1320] Step 7:

[1321] The server recognizes the user's emotions using an emotion engine. Input data includes the user's facial expressions, voice, keystrokes, etc. The server identifies the emotion using the emotion engine and outputs that emotion.

[1322] Step 8:

[1323] The server generates appropriate feedback based on the detected user emotion. For example, if the user is feeling frustrated, it generates an auxiliary help message. The input data is the emotion detected in step 7, and the generated feedback is output.

[1324] Step 9:

[1325] The server notifies the user of all validation results and feedback. The input data are the validation results and feedback up to that point, and presents them to the user together.

[1326] Specifically, the following prompt sentences are used:

[1327] Recognizes the following emotions based on the user's facial expressions, voice data, and input data:

[1328] 1. Happiness

[1329] 2. Anger

[1330] 3. Confused

[1331] 4. Irritation

[1332] example:

[1333] As a result, users can correct any missed measures or input errors, and receive appropriate support according to their emotions, allowing them to input transaction information smoothly.

[1334] The specific processing unit 290 transmits the result of the specific processing to the robot 414. In the robot 414, the control unit 46A causes the speaker 240 and the control target 443 to output the result of the specific processing. The microphone 238 acquires voice indicating a user input regarding the result of the specific processing. The control unit 46A transmits voice data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the voice data.

[1335] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[1336] In the above embodiment, an example in which the specific processing is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the robot 414.

[1337] The emotion identification model 59 as an emotion engine may determine the user's emotion according to a specific mapping. Specifically, the emotion identification model 59 may determine the user's emotion according to an emotion map (see FIG. 9), which is a specific mapping. Similarly, the emotion identification model 59 may determine the robot's emotion, and the identification processing unit 290 may perform identification processing using the robot's emotion.

[1338] FIG. 9 illustrates an emotion map 400 on which multiple emotions are mapped. In the emotion map 400, emotions are arranged in concentric circles radiating from the center. Emotions closer to the center of the concentric circles are more primitive. Emotions representing states and behaviors arising from a state of mind are arranged on the outer edges of the concentric circles. The concept of emotion includes both affect and mental states. Emotions generally generated from reactions occurring in the brain are arranged on the left side of the concentric circles. Emotions generally induced by situational judgment are arranged on the right side of the concentric circles. Emotions generally generated from reactions occurring in the brain and induced by situational judgment are arranged on the upper and lower sides of the concentric circles. Furthermore, the emotion of "pleasure" is arranged on the upper side of the concentric circles, and the emotion of "discomfort" is arranged on the lower side. In this way, in the emotion map 400, multiple emotions are mapped based on the structure by which emotions are generated, and emotions that tend to occur simultaneously are mapped close to each other.

[1339] These emotions are distributed in the 3 o'clock direction on emotion map 400, and typically fluctuate between relief and anxiety. In the right half of emotion map 400, situational awareness dominates over internal sensations, resulting in a sense of calm.

[1340] The inside of emotion map 400 represents what is going on in the mind, and the outside of emotion map 400 represents behavior, so the further you go outside emotion map 400, the more visible the emotions become (the more they are expressed in behavior).

[1341] Human emotions are based on various balances, such as posture and blood sugar levels. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. Emotions can also be created for robots, automobiles, and motorcycles, based on various balances, such as posture and remaining battery life. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. An emotion map can be generated, for example, based on Dr. Mitsuyoshi's emotion map (Research on Voice Emotion Recognition and Emotional Brain Physiological Signal Analysis Systems, Tokushima University, Doctoral Dissertation: https: / / ci.nii.ac.jp / naid / 500000375379). The left half of the emotion map lists emotions belonging to the "reaction" domain, where sensation is dominant. The right half of the emotion map lists emotions belonging to the "situation" domain, where situational awareness is dominant.

[1342] The emotion map defines two emotions that promote learning. One is a negative emotion on the situation side, around the middle of "repentance" or "reflection." In other words, this occurs when the robot experiences negative emotions such as "I never want to feel this way again" or "I don't want to be scolded again." The other is a positive emotion on the response side, around "desire." In other words, this occurs when the robot experiences positive feelings such as "I want more" or "I want to know more."

[1343] The emotion identification model 59 inputs user input into a pre-trained neural network, obtains emotion values ​​indicating each emotion shown in the emotion map 400, and determines the user's emotion. This neural network is pre-trained based on multiple pieces of training data that are combinations of user input and emotion values ​​indicating each emotion shown in the emotion map 400. Furthermore, this neural network is trained so that emotions that are located close to each other have similar values, as in the emotion map 900 shown in FIG. 10. FIG. 10 shows an example in which multiple emotions, "relieved," "calm," and "reassuring," have similar emotion values.

[1344] The system according to the present disclosure has been described above mainly with respect to the functions of the data processing device 12, but the system according to the present disclosure is not necessarily implemented on a server. The system according to the present disclosure may be implemented as a general information processing system. The present disclosure may be implemented, for example, as a software program running on a personal computer or an application running on a smartphone, etc. The method according to the present disclosure may be provided to users in the form of SaaS (Software as a Service).

[1345] In the above embodiment, an example was given in which the specific processing is performed by one computer 22, but the technology of the present disclosure is not limited to this, and the specific processing may be distributed and performed by a plurality of computers including the computer 22. For example, the data generation model 58 may be provided in an external device of the data processing device 12, and data may be generated in the external device in accordance with input data.

[1346] In the above embodiment, an example in which the specific processing program 56 is stored in the storage 32 has been described, but the technology of the present disclosure is not limited to this. For example, the specific processing program 56 may be stored in a portable, computer-readable, non-transitory storage medium such as a USB (Universal Serial Bus) memory. The specific processing program 56 stored in the non-transitory storage medium is installed in the computer 22 of the data processing device 12. The processor 28 executes the specific processing in accordance with the specific processing program 56.

[1347] Alternatively, the specific processing program 56 may be stored in a storage device such as a server connected to the data processing device 12 via the network 54, and the specific processing program 56 may be downloaded and installed on the computer 22 in response to a request from the data processing device 12.

[1348] It is not necessary to store all of the specific processing program 56 in a storage device such as a server connected to the data processing device 12 via the network 54, or to store all of the specific processing program 56 in the storage 32; only a portion of the specific processing program 56 may be stored.

[1349] The hardware resource for executing a specific process can be any of the following processors: An example of a processor is a CPU, which is a general-purpose processor that functions as a hardware resource for executing a specific process by executing software, i.e., a program. Another example of a processor is a dedicated electrical circuit, such as an FPGA (Field-Programmable Gate Array), a PLD (Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit), which is a processor with a circuit configuration designed specifically for executing a specific process. Each processor has built-in or connected memory, and each processor uses the memory to execute the specific process.

[1350] The hardware resource that executes the specific processing may be configured with one of these various processors, or may be configured with a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA). Also, the hardware resource that executes the specific processing may be a single processor.

[1351] As an example of a system configured with a single processor, first, one processor is configured by combining one or more CPUs and software, and this processor functions as a hardware resource that executes a specific process. Second, there is a system that uses a processor that realizes the functions of an entire system including multiple hardware resources that execute a specific process on a single IC chip, as typified by SoC (System-on-a-chip). In this way, a specific process is realized using one or more of the above-mentioned various processors as hardware resources.

[1352] Furthermore, the hardware structure of these various processors can be, more specifically, an electric circuit that combines circuit elements such as semiconductor devices. The specific processing described above is merely an example. Therefore, it goes without saying that unnecessary steps may be deleted, new steps may be added, or the processing order may be rearranged, without departing from the spirit of the invention.

[1353] The above-described description and illustrations are a detailed explanation of the parts related to the technology of the present disclosure and are merely an example of the technology of the present disclosure. For example, the above description of the configuration, functions, actions, and effects is an explanation of an example of the configuration, functions, actions, and effects of the parts related to the technology of the present disclosure. Therefore, it goes without saying that unnecessary parts may be deleted, new elements may be added, or replacements may be made to the above-described description and illustrations within the scope of the gist of the technology of the present disclosure. Furthermore, to avoid confusion and facilitate understanding of the parts related to the technology of the present disclosure, the above-described description and illustrations omit explanations of common technical knowledge that do not require particular explanation to enable the implementation of the technology of the present disclosure.

[1354] All publications, patent applications, and technical standards mentioned in this specification are herein incorporated by reference to the same extent as if each individual publication, patent application, or technical standard was specifically and individually indicated to be incorporated by reference.

[1355] The following is further disclosed regarding the above embodiment.

[1356] (Claim 1)

[1357] A means for receiving input contract information;

[1358] A means for verifying the application status of the policies of the contract information based on the list of policies;

[1359] a means for verifying the format of the contract code;

[1360] A means for generating an error message when there is an error in the policy application or contract code;

[1361] a means for displaying the validation results;

[1362] A system including:

[1363] (Claim 2)

[1364] 2. The system according to claim 1, wherein the means for verifying the policy application status compares the policy list entered in the contract information with the policy list to detect any missing policies.

[1365] (Claim 3)

[1366] 2. The system according to claim 1, wherein the means for verifying the format of the contract code checks whether it matches a predetermined format and generates an error message if it does not match.

[1367] "Example 1"

[1368] (Claim 1)

[1369] a processor having a function of receiving contract information, comparing a list of measures included in the contract information with a list of measures to detect missing measures, and checking whether a contract code included in the contract information matches a predetermined format;

[1370] a processor that verifies the policy application status of the contract information based on the list of policies;

[1371] a processor for validating the format of the contract code;

[1372] a processor that generates an error message and displays it on a user terminal when there is an error in the policy application or the contract code;

[1373] a processor for displaying the verification results;

[1374] A system including:

[1375] (Claim 2)

[1376] 2. The system of claim 1, wherein the processor for verifying the policy application status compares the policy list entered in the contract information with the policy list, detects any missing policies, and generates an error message.

[1377] (Claim 3)

[1378] 2. The system of claim 1, wherein the processor that verifies the format of the contract code checks whether it matches a predetermined format and generates an error message if it does not match.

[1379] "Application Example 1"

[1380] (Claim 1)

[1381] A means for receiving input contract information and payment information;

[1382] A means for verifying the application status of the policies and the application status of the payment method of the contract information based on the list of policies;

[1383] a means for validating the format of the contract code and the settlement code;

[1384] A means for generating an error message when there is an error in the policy application, contract code, or payment code;

[1385] a means for displaying the validation results;

[1386] A system including:

[1387] (Claim 2)

[1388] The system described in claim 1, wherein the means for verifying the application status of policies and payment methods compares the policy list and payment method list entered in the contract information and payment information with the policy list and payment method list to detect missing policies and payment methods.

[1389] (Claim 3)

[1390] 2. The system according to claim 1, wherein the means for verifying the format of the contract code and payment code checks whether they match a predetermined format and generates an error message if they do not match.

[1391] "Example 2: Combining Emotion Engines"

[1392] (Claim 1)

[1393] A means for receiving input contract information;

[1394] A means for verifying the application status of the policies of the contract information based on the list of policies;

[1395] a means for verifying the format of the contract code;

[1396] A means for generating an error message when there is an error in the policy application or contract code;

[1397] means for recognizing a user's emotion;

[1398] a means for generating appropriate feedback based on the emotion recognition result;

[1399] a means for displaying validation results and feedback;

[1400] A system including:

[1401] (Claim 2)

[1402] 2. The system according to claim 1, wherein the means for verifying the policy application status compares the policy list entered in the contract information with the policy list to detect any missing policies.

[1403] (Claim 3)

[1404] 2. The system according to claim 1, wherein the means for verifying the format of the contract code checks whether it matches a predetermined format and generates an error message if it does not match.

[1405] "Application example 2 when combining emotion engines"

[1406] (Claim 1)

[1407] means for receiving input transaction information;

[1408] means for verifying the application status of the measures to the transaction information based on the list of measures;

[1409] a means for validating the format of the transaction code;

[1410] means for generating an error message in case of an error in the policy application or transaction code;

[1411] means for recognizing a user's emotions while inputting transaction information;

[1412] means for generating appropriate feedback based on the emotion recognition result;

[1413] a means for displaying the validation results;

[1414] A system including:

[1415] (Claim 2)

[1416] 2. The system according to claim 1, wherein the means for verifying the policy application status compares the policy list entered in the transaction information with the policy list to detect any missing policies.

[1417] (Claim 3)

[1418] 2. The system according to claim 1, wherein the means for verifying the format of the transaction code checks whether it matches a predetermined format and generates an error message if it does not match. [Explanation of symbols]

[1419] 10, 210, 310, 410 Data Processing Systems 12 Data Processing Device 14 Smart Devices 214 Smart Glasses 314 Headset-type terminal 414 Robot< / url:> < / url:> < / url:> < / url:>

Claims

1. A means for receiving input contract information; A means for verifying the application status of the policies of the contract information based on the list of policies; a means for verifying the format of the contract code; A means for generating an error message when there is an error in the policy application or contract code; a means for displaying the validation results; A system including:

2. 2. The system according to claim 1, wherein the means for verifying the policy application status compares the policy list entered in the contract information with the policy list to detect any missing policies.

3. 2. The system according to claim 1, wherein the means for verifying the format of the contract code checks whether it matches a predetermined format and generates an error message if it does not match.

Images