system

Abstract

We provide a system that accurately understands user needs, enables efficient work execution, and improves user satisfaction. [Solution] A system comprising: means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recording the answers in a database; means for executing an algorithm that selects the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; and means for sending a completion notification to the user when the contract is completed.

Description

Technical Field

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

Background Art

[0002] Patent Document 1 discloses a persona chatbot control method performed by at least one processor, including steps of receiving a user utterance, adding the user utterance to a prompt including an instruction sentence related to an explanation of a 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

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a conventional contract plan proposal system, users had to manually perform multiple steps, making it difficult to perform business efficiently. Also, it was difficult to accurately grasp users' needs and propose an optimal plan. As a result, the problems were that users' satisfaction and business efficiency decreased.

Means for Solving the Problems

[0005] This invention provides a system that logs in based on authentication information entered by the user, and then conducts interviews with the user through an interactive interface. The user's input information is recorded in a database, and the system selects the most suitable contract plan based on this information. The selected contract plan is displayed to the user, and the contract application is submitted from the terminal. The system integrates with a backend contract management system to automatically process the contract application. In addition, a completion notification is sent to the user upon completion of the contract. This allows for an accurate understanding of user needs, efficient business operations, and improved user satisfaction.

[0006] A "user" is an individual or legal entity that uses this system to enter authentication information and submit a proposal or application for a contract plan.

[0007] "Authentication information" refers to information such as the user ID and password that a user enters to log in to the system.

[0008] A "database" is an information system used to store user authentication information, interview data, contract information, and other similar data.

[0009] An "interactive interface" is an interactive user interface used to receive questions and answers from users.

[0010] An "algorithm" is a calculation method or processing step used to select the optimal contract plan based on user input information.

[0011] A "contract plan" is a plan that includes the terms of use and pricing structure for various services that a user wishes to subscribe to.

[0012] A "contract management system" is a backend system that manages users' contract information and processes contract applications.

[0013] A "completion notice" is a notification message sent to inform the user that the contract has been successfully completed. [Brief explanation of the drawing]

[0014] [Figure 1] This is a conceptual diagram showing an example of the configuration of a data processing system according to the first embodiment. [Figure 2] This is a conceptual diagram showing an example of the essential functions of a data processing device and a smart device according to the first embodiment. [Figure 3] This is a conceptual diagram showing an example of the configuration of a data processing system according to the second embodiment. [Figure 4] This is a conceptual diagram showing an example of the main functions of a data processing device and smart glasses according to the second embodiment. [Figure 5] This is a conceptual diagram showing an example of the configuration of a data processing system according to the third embodiment. [Figure 6] This is a conceptual diagram showing an example of the main functions of a data processing device and a headset-type terminal according to the third embodiment. [Figure 7] This is a conceptual diagram showing an example of the configuration of a data processing system according to the fourth embodiment. [Figure 8] This is a conceptual diagram showing an example of the main functions of a data processing device and a robot according to the fourth embodiment. [Figure 9] This shows an emotion map where multiple emotions are mapped. [Figure 10] This shows an emotion map where multiple emotions are mapped. [Figure 11] This is a sequence diagram showing the processing flow of the data processing system in Example 1. [Figure 12] This is a sequence diagram showing the processing flow of the data processing system in Application Example 1. [Figure 13] This is a sequence diagram showing the processing flow of the data processing system in Example 2, which incorporates an emotion engine. [Figure 14] This is a sequence diagram showing the processing flow of the data processing system in Application Example 2, which combines an emotion engine.

Embodiment for Carrying Out the Invention

[0015] Hereinafter, an example of an embodiment of a system according to the technology of the present disclosure will be described with reference to the accompanying drawings.

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

[0017] In the following embodiments, a labeled processor (hereinafter simply referred to as "processor") may be one arithmetic unit or a combination of a plurality of arithmetic units. Also, the processor may be one type of arithmetic unit or a combination of a plurality of types of arithmetic units. Examples of arithmetic units include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a GPGPU (General-Purpose computing on Graphics Processing Units), an APU (Accelerated Processing Unit), and the like.

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

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

[0020] In the following embodiments, the signed communication interface (I / F) is an interface that includes a communication processor and an antenna, etc. The communication interface manages communication between multiple computers. Examples of communication standards applicable to the communication interface include wireless communication standards such as 5G (5th Generation Mobile Communication System), Wi-Fi (registered trademark), or Bluetooth (registered trademark).

[0021] In the following embodiments, "A and / or B" is synonymous with "at least one of A and B." That is, "A and / or B" means that it may be A alone, or B alone, or a combination of A and B. Furthermore, in this specification, the same concept as "A and / or B" applies when expressing three or more things linked by "and / or."

[0022] [First Embodiment]

[0023] Figure 1 shows an example of the configuration of the data processing system 10 according to the first embodiment.

[0024] As shown in Figure 1, the 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.

[0025] The data processing device 12 comprises a computer 22, a database 24, and a communication interface 26. The computer 22 is an example of a "computer" related to the technology of this disclosure. The computer 22 comprises a processor 28, RAM 30, and storage 32. The processor 28, RAM 30, and storage 32 are connected to a bus 34. The database 24 and the communication interface 26 are also connected to the bus 34. The communication interface 26 is connected to a network 54. An example of the network 54 is a WAN (Wide Area Network) and / or a LAN (Local Area Network).

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

[0027] The reception device 38 is equipped with a touch panel 38A and a microphone 38B, etc., and receives user input. The touch panel 38A receives user input by detecting contact with an object (e.g., a pen or finger). The microphone 38B receives user input by detecting the user's voice. The control unit 46A transmits data indicating the user input received by the touch panel 38A and 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.

[0028] 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 perceptible to the user 20 (e.g., audio and / or text). The display 40A displays visible information such as text and images according to instructions from the processor 46. The speaker 40B outputs audio according to instructions from the processor 46. The camera 42 is a small digital camera equipped with an optical system such as a lens, aperture, and shutter, and an image sensor such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor.

[0029] Communication interface 44 is connected to network 54. Communication interfaces 44 and 26 are responsible for the exchange of various types of information between processor 46 and processor 28 via network 54.

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

[0031] As shown in Figure 2, in the data processing device 12, a specific processing 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" related to the technology of this 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 according to the specific processing program 56 executed on the RAM 30.

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

[0033] In the smart device 14, the processor 46 performs the reception output processing. The storage 50 stores the reception output program 60. The reception output program 60 is used in conjunction with a 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 processing is realized by the processor 46 operating as a control unit 46A according to the reception output program 60 executed on the RAM 48.

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

[0035] This invention relates to a system that allows users to easily and efficiently propose and apply for contract plans. This system logs in based on the user's authentication information, listens to the user's requests and preferences through an interactive interface, and proposes the most suitable contract plan based on that information. Furthermore, it can automatically process the contract application and finally sends a contract completion notification to the user.

[0036] Program processing

[0037] User authentication process

[0038] User: The user enters their authentication information (user ID and password) into the terminal.

[0039] Terminal: The terminal sends the entered authentication information to the server.

[0040] Server: The server compares the received authentication information with the database and determines whether login is permitted. If successful, it returns the user's personal profile to the terminal. If unsuccessful, it returns an error message.

[0041] Device: The device will either display an error message or, if successful, display the user's personal profile.

[0042] Request gathering process

[0043] Terminal: Displays an interactive interface to users who have successfully logged in. It displays initial questions such as, "Are you satisfied with the service you are currently using?"

[0044] User: The user answers the question (e.g., "Insufficient data").

[0045] Terminal: The terminal receives the response and generates and displays the next question (e.g., "How much data do you want?").

[0046] User: The user also answers the following question (e.g., "I would like 20GB per month").

[0047] Terminal: Temporarily saves the answer and sends it to the server.

[0048] Server: Records user responses in the hearing database.

[0049] Plan proposal processing

[0050] Server: Executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users.

[0051] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0052] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0053] Server: We will receive any additional questions or requested changes and recalculate the optimal plan.

[0054] Device: Display the new plan to the user.

[0055] System Integration Processing

[0056] Device: After the user agrees to the proposed plan, a button will be displayed to proceed with the "Subscription Application".

[0057] User: The user clicks the contract application button.

[0058] Server: Receives contract application information and integrates with the backend contract management system. Registers contract information in the contract management database.

[0059] Order completion notification processing

[0060] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or SMS. Sends completion details to the device.

[0061] Terminal: Displays a screen indicating that the order has been completed and provides the user with detailed information such as contract details and service start date.

[0062] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0063] Specific example

[0064] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, the server verifies it against the database, and the login process is initiated. If the login is successful, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server calculates the optimal plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[0065] In this way, the present invention makes it possible to accurately understand user needs and propose and accept efficient and user-friendly contract plans.

[0066] The following describes the processing flow.

[0067] Step 1:

[0068] User: The user enters their authentication information (user ID and password) into the terminal.

[0069] Step 2:

[0070] Terminal: The terminal sends the entered authentication information to the server.

[0071] Step 3:

[0072] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[0073] Step 4:

[0074] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[0075] Step 5:

[0076] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[0077] Step 6:

[0078] Terminal: Displays an interactive interface and presents the user with the question, "Are you satisfied with the service you are currently using?"

[0079] Step 7:

[0080] User: The user enters an answer to the question (e.g., "Insufficient data").

[0081] Step 8:

[0082] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[0083] Step 9:

[0084] User: The user answers the following question (e.g., "I would like 20GB per month").

[0085] Step 10:

[0086] Terminal: The terminal temporarily stores the answer and sends it to the server.

[0087] Step 11:

[0088] Server: The server records the user's responses in the hearing database.

[0089] Step 12:

[0090] Server: The server analyzes the recorded interview data and runs an algorithm to select the optimal contract plan.

[0091] Step 13:

[0092] Server: Sends the selected optimal contract plan to the terminal.

[0093] Step 14:

[0094] Device: The device displays the proposed contract plan to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0095] Step 15:

[0096] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0097] Step 16:

[0098] Terminal: Sends additional questions or requested changes from the user to the server.

[0099] Step 17:

[0100] Server: Receives additional questions or requested changes and runs an algorithm to recalculate the optimal plan.

[0101] Step 18:

[0102] Server: Sends the new contract plan to the device.

[0103] Step 19:

[0104] Device: Display new contract plans to the user.

[0105] Step 20:

[0106] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[0107] Step 21:

[0108] Terminal: Sends contract application information to the server.

[0109] Step 22:

[0110] Server: Receives contract application information and integrates with the backend contract management system.

[0111] Step 23:

[0112] Server: Registers contract information in the contract management database.

[0113] Step 24:

[0114] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[0115] Step 25:

[0116] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[0117] Step 26:

[0118] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0119] (Example 1)

[0120] Next, we will describe Example 1. In the following description, the data processing device 12 will be referred to as the "server," and the smart device 14 will be referred to as the "terminal."

[0121] Conventional contract plan proposal systems failed to adequately reflect user needs and preferences, making it difficult to provide users with the most suitable contract plan quickly and efficiently. In particular, a challenge was the inability to recalculate the plan when users had additional questions or requested changes to the presented plan, resulting in a degraded user experience.

[0122] The identification process performed by the identification processing unit 290 of the data processing device 12 in Example 1 is realized by the following means.

[0123] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recording the answers in a database; means for executing an algorithm to select the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; and means for receiving additional questions or change requests from the user, and recalculating and displaying the optimal contract plan again. This makes it possible to accurately grasp the user's needs and desires, propose the optimal contract plan, and quickly make revised proposals.

[0124] "Authentication information" refers to the information a user needs to log in to a system, and typically consists of a user ID and password.

[0125] A "database" is an organized collection of data, a system for retrieving, storing, and updating information.

[0126] An "interactive interface" is a user interface that allows the user and the system to communicate in both directions.

[0127] "Means for generating questions and answers" refers to a function that creates appropriate questions based on user input and collects user responses to those questions.

[0128] An "algorithm" is a set of procedures or computational methods for solving a specific problem.

[0129] A "contract plan" refers to the terms and conditions of the agreement for a user to use the service.

[0130] "Application information" refers to the necessary data that a user provides when they wish to enter into a contract.

[0131] A "backend contract management system" is a system used for managing and updating contract details.

[0132] A "completion notification" is a notification sent to inform a user that a transaction or procedure has been successfully completed.

[0133] "Additional questions or requested changes" refers to any further information the user would like to know or any changes they would like to make regarding the proposed plan.

[0134] This invention relates to a system for users to easily and efficiently propose and apply for contract plans. This system includes the following processes: user authentication, requirements gathering, plan proposal, system integration, and order completion notification.

[0135] Hardware and software to be used

[0136] The system's hardware includes a server, terminals (e.g., tablet devices), and a database. The server is responsible for processes such as verifying authentication information, executing plan proposal algorithms, and sending notifications. Its software includes a MySQL® or PostgreSQL database, algorithms implemented in Python, and a mail server (e.g., SendGrid). Terminals display the user interface, input user data, and communicate with the server, using a standard web browser or interactive interface software.

[0137] Processing details

[0138] The server first receives the authentication information (user ID and password) entered by the user and compares it with the database. If authentication is successful, the user's personal profile is returned and displayed on the terminal. Next, the terminal displays an interactive interface to hear the user's requests and preferences. A question-and-answer exchange takes place, and this information is sent to the server and recorded in the database.

[0139] The server uses machine learning models and other tools to calculate and select the optimal contract plan based on recorded data. This calculation takes into account the user's usage history and feedback from other users. The selected plan is displayed on the terminal, and the user reviews the proposal and enters additional questions or requests for changes via the terminal as needed. The server receives this new information, recalculates the plan, and displays the result on the terminal.

[0140] If the user agrees to the proposed plan, the device displays a contract application button, and when the user clicks it, the contract application information is sent to the server. The server then integrates this information with the backend contract management system to finalize the contract. Once the contract is complete, the server sends a completion notification to the user's registered email address or via SMS, and the device also displays confirmation of the order completion.

[0141] Specific example

[0142] For example, if a user wishes to change their plan using a tablet terminal installed at a train station's ticket gate, they can follow these steps: The user enters their authentication information into the terminal, the server verifies it against a database, and the login process is initiated. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server uses a machine learning model implemented in Python to calculate the optimal contract plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal. In this way, the present invention enables accurate understanding of user needs and allows for the proposal and application of efficient and user-friendly contract plans.

[0143] Example of a prompt

[0144] "Please describe the system's processing flow for users to change their plan at terminals installed at train station ticket gates. Please include the specific names of the hardware and software used at each step, from user authentication to contract completion notification."

[0145] The flow of the specific processing in Example 1 will be explained using Figure 11.

[0146] Step 1:

[0147] The user enters their authentication information (user ID and password) into the terminal. This input is done using a text field. The input data consists of the user ID and password.

[0148] Step 2:

[0149] The terminal encrypts the entered authentication information and sends it to the server. Specifically, it encrypts and transmits the data using the SSL / TLS protocol. The input is the encrypted authentication information, and the output is the request to the server.

[0150] Step 3:

[0151] The server compares the received authentication information with the database. The database stores the user ID and the hashed password. The server retrieves the password hash corresponding to the user ID from the database and compares it with the input password. The input is encrypted authentication information, and the output is the authentication result (success / failure).

[0152] Step 4:

[0153] The server returns the user's personal profile to the terminal if authentication is successful, and an error message if it fails. The input is the authentication result, and the output is either the personal profile or the error message.

[0154] Step 5:

[0155] The device receives the authentication result and, if the login is successful, displays the user's personal profile; if it fails, it displays an error message. The input is the personal profile or the error message, and the output is the screen display.

[0156] Step 6:

[0157] The terminal displays an interactive interface to users who have successfully logged in, and shows the initial question, "Are you satisfied with the services you are currently using?". The input is the user's personal profile, and the output is the screen display of the question.

[0158] Step 7:

[0159] The user answers a question (e.g., "Insufficient data"). User input is provided through an interactive interface. Input is the user's answer to the question, and output is the transmission of the answer to the terminal.

[0160] Step 8:

[0161] The terminal receives the user's response and generates and displays the next question, "How much data do you need?". The input is the user's initial response, and the output is the screen display for the next question. The terminal temporarily stores this data.

[0162] Step 9:

[0163] The user also answers the following question (e.g., "I want 20GB per month"). This input is done through an interactive interface. The input is the user's answer to the following question, and the output is the transmission of the answer to the terminal.

[0164] Step 10:

[0165] The terminal temporarily stores the response and sends it to the server. The input is the user's response, and the output is the data sent to the server.

[0166] Step 11:

[0167] The server records user responses in a hearing database. The input is the user's response data, and the output is saving it to the database.

[0168] Step 12:

[0169] The server executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users. The inputs are interview data, usage history data, and feedback data, and the output is the optimal contract plan.

[0170] Step 13:

[0171] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is available for XXX yen"). The input is the proposed plan data, and the output is the screen display.

[0172] Step 14:

[0173] The user reviews the proposed plan and enters additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?"). This input is done through an interactive interface. The input consists of additional questions or requests for changes, and the output is the response sent to the device.

[0174] Step 15:

[0175] The server receives additional questions and requested changes and recalculates the optimal plan. The input is the data for the additional questions and requested changes, and the output is the recalculated contract plan.

[0176] Step 16:

[0177] The device displays the new plan to the user. The input is the recalculated contract plan data, and the output is the screen display.

[0178] Step 17:

[0179] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The input is the user's agreement, and the output is the display of the subscription application button.

[0180] Step 18:

[0181] The user clicks the contract application button. The input is the click of the contract application button, and the output is the submission of contract information.

[0182] Step 19:

[0183] The server receives contract application information and interacts with the backend contract management system. The input is the contract application information, and the output is the transmission of data to the contract management system.

[0184] Step 20:

[0185] The server registers contract information in the contract management database. The input is contract application information, and the output is saving it to the database.

[0186] Step 21:

[0187] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input is the contract completion information, and the output is the sending of the completion notification.

[0188] Step 22:

[0189] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The input is the contract completion information, and the output is the screen display.

[0190] Step 23:

[0191] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The input is the completion notification, and the output is the confirmation and instructions for the next steps.

[0192] (Application Example 1)

[0193] Next, we will explain Application Example 1. In the following explanation, the data processing device 12 will be referred to as the "server," and the smart device 14 will be referred to as the "terminal."

[0194] In recent years, with the advancement of e-commerce, users need to select the optimal purchase plan and products from a vast amount of product information, thus requiring a more efficient purchasing experience and personalized suggestions. Conventional systems struggle to fully meet user needs, and in particular, they lack the means to propose the most suitable products in an interactive format and to facilitate a smooth purchasing process. Therefore, to improve user satisfaction, a system is needed that uses an interactive interface to quickly and accurately understand user requests and provide optimal product suggestions and purchasing procedures.

[0195] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 1 is realized by the following means.

[0196] In this invention, the server includes means for matching user authentication information with a database and determining whether or not login is permitted; means for generating questions and answers through an interactive interface based on user input information; means for recording the answers in a database; means for executing an algorithm for selecting the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; means for selecting the optimal purchase plan by referring to usage history and feedback from other users; and means for displaying product suggestions to the user based on the purchase plan and accepting the purchase procedure. This enables the user to efficiently select the optimal product from a large amount of product information and smoothly complete the purchase procedure.

[0197] "User authentication" is a series of processes that compare the authentication information a user provides to log in to a system with a database and determine whether or not they are allowed to log in.

[0198] An "interactive interface" is an interface used to facilitate smooth interaction with users, and it is a mechanism that dynamically generates questions and answers based on user input.

[0199] "Authentication information" refers to information such as user ID and password that a user uses when logging into a system.

[0200] A "database" is an electronic information recording system used to store and manage user information, interview data, contract details, and other similar information.

[0201] An "algorithm" is a set of procedures or calculation methods for achieving a specific objective, and in this system, it is a means of selecting the optimal contract or purchase plan.

[0202] A "backend system" is a system that manages and processes contract and purchase information, separate from the frontend system that interacts directly with users.

[0203] A "contract plan" refers to the specific details of the services or products offered to the user, along with their pricing.

[0204] A "purchase plan" is a plan that proposes the optimal combination of products to be obtained by purchasing them all at once or as a set, based on the user's needs.

[0205] A "completion notification" is a notification sent to the user informing them that the contract or purchase procedure has been successfully completed, and is sent via email, SMS, or other means.

[0206] "Usage history" refers to records of operations, selections, and purchases that a user has made through the system in the past.

[0207] "Feedback" refers to opinions and evaluations provided by users and other users, which are used in selecting plans and proposing products within this system.

[0208] The system for implementing this invention is designed to provide users with efficient and personalized proposals and procedures for contract and purchase plans. The system supports a series of processes in which the user easily authenticates, inputs their needs through an interactive interface, is proposed the most suitable plan, and completes the purchase or contract procedure.

[0209] The system configuration is as follows:

[0210] Hardware and software to use

[0211] Hardware: Smartphone

[0212] Software: Mobile app (iOS and Android®), server-side uses AWS® (Amazon Web Services).

[0213] Database: MySQL or PostgreSQL

[0214] Generative AI model: GPT-4 (registered trademark) (OpenAI (registered trademark))

[0215] User authentication process

[0216] The user launches the smartphone app and enters their ID and password. The app sends this information to the server, which verifies the authentication information against a database. If authentication is successful, the user's personal profile is displayed in the app.

[0217] Request gathering process

[0218] After successful login, the app displays an interactive interface. For example, the first question displayed might be, "Are you satisfied with your recent purchase?" The user answers this question (e.g., "I want a more portable product"), and the app generates and displays the next question. By repeating this process, the app collects the user's requests and sends them to the server. The server records this data in a hearing database.

[0219] Plan proposal processing

[0220] The server uses recorded user responses to run an algorithm to select the optimal contract or purchase plan. Usage history and feedback from other users are also referenced. The calculated plan is presented to the user through the app.

[0221] System Integration Processing

[0222] Once a user agrees to a proposed plan, they can tap a button within the app to complete the contract application or purchase process. The server receives this information, processes it in conjunction with the backend contract management system and order management system, and registers the contract or purchase information in the relevant database.

[0223] Order completion notification processing

[0224] When a contract or purchase is completed, the server sends a completion notification to the user. This notification is sent to the registered email address or via SMS. A completion screen is also displayed in the app, allowing the user to confirm the contract details and purchase information.

[0225] Specific example

[0226] For example, if a user logs into a smartphone app and, in the interactive interface, indicates they are looking for "cooking utensils that are easy to use at a campsite they recently visited," the system will suggest a "lightweight and easy-to-pack camping cooking set," and will also display current discount information and related products. Once the user reviews the suggestion, agrees, and taps to purchase, the order is immediately completed, and an order confirmation notification is sent to their smartphone.

[0227] Example of a prompt

[0228] "I'm looking for easy-to-use cooking utensils at a campsite I recently visited."

[0229] "What type of cooking utensils do you prefer? (e.g., lightweight, portable, set, etc.)"

[0230] "Something lightweight and easy to package."

[0231] "Our recommended product is a lightweight and easy-to-pack camping cooking set. It's currently 30% off. Would you like to purchase it?"

[0232] "yes"

[0233] "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[0234] By implementing this system, we can accurately grasp user needs and achieve efficient, personalized contract and purchasing processes.

[0235] The flow of a specific process in Application Example 1 will be explained using Figure 12.

[0236] Step 1: User Authentication Process

[0237] The user launches the smartphone app and enters their ID and password on the authentication screen. The user ID and password are provided as input.

[0238] The terminal sends the entered authentication information to the server. At this time, the user ID and password are sent to the server as data packets.

[0239] The server compares the received authentication information with the database to determine whether or not the login is permitted. This process involves comparing the user information stored in the database with the entered authentication information.

[0240] The server returns the user's personal profile to the device if authentication is successful, and an error message if it fails. The output upon successful authentication is the user's profile information, while the output upon failure is an error message.

[0241] Based on the received data, the device will display the personal profile screen if successful, or an error message if unsuccessful.

[0242] Step 2: Request gathering process

[0243] The terminal displays an interactive interface to users who have successfully logged in. The system's initial question is, "Are you satisfied with your recent purchases?" The user is then provided with further questions as input.

[0244] The user enters an answer to this question (e.g., "I want a product that is easier to carry"). That answer is then sent to the device.

[0245] The device temporarily stores the user's response and generates and displays the next question (e.g., "What type of product do you prefer?"). The generated question is created by an AI model based on the user's response.

[0246] The server receives response data sent from the terminal and records it in the hearing database. User response data is provided as input, and recorded in the hearing database as output.

[0247] Step 3: Plan Proposal Processing

[0248] The server executes an algorithm to select the optimal contract plan based on recorded user interview data. This algorithm also utilizes usage history and feedback from other users stored in the database. The input to this process is user interview data and usage history, and the output is the selected contract plan.

[0249] The server sends the selected plan to the terminal, and the terminal displays the plan to the user (e.g., "Lightweight and easy-to-pack camping cooking set available at 30% off"). The sent plan is displayed as output.

[0250] Step 4: System Integration Process

[0251] If the user agrees to the proposed plan, they tap the purchase button displayed on their device. The user's consent action is provided as input.

[0252] The server receives the operation information and processes the contract application in cooperation with the backend contract management system. This cooperation process includes registering the user's purchase information in the contract management system. As output, the contract application information is registered in the system.

[0253] The server registers the purchase completion information in the contract management database. Purchase completion data is provided as input.

[0254] Step 5: Order completion notification processing

[0255] The server sends a completion notification to the user's registered email address or via SMS when a contract or purchase is completed. Completion notification data is provided as input, and the completion notification is sent to the user as output.

[0256] The device displays a completion screen to the user, providing contract details and purchase information. The output is the completion screen.

[0257] The user can then confirm the completion notification and proceed to the next step. Specifically, it might display something like, "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[0258] This series of processes allows users to efficiently and personalizedly enter into service contracts and purchase products.

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

[0260] This invention relates to a system that proposes and accepts contract plans while also considering the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[0261] Program processing

[0262] User authentication process

[0263] User: The user enters their authentication information (user ID and password) into the terminal.

[0264] Terminal: The terminal sends the entered authentication information to the server.

[0265] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[0266] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[0267] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[0268] Request gathering process

[0269] Terminal: Displays an interactive interface to users who have successfully logged in. The initial question is, "Are you satisfied with the service you are currently using?"

[0270] User: The user enters an answer to the question (e.g., "Insufficient data").

[0271] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[0272] User: The user answers the following question (e.g., "I would like 20GB per month").

[0273] Terminal: Temporarily saves the answer and sends it to the server.

[0274] Server: Records user responses in the hearing database.

[0275] Emotion recognition processing

[0276] Terminal: Activates an emotion engine to recognize emotions from the user's responses and facial expressions.

[0277] Server: The emotion engine analyzes the user's emotional state and generates emotion data.

[0278] Server: Based on the emotional state, adjust the content and tone of the next question and send it to the terminal.

[0279] Terminal: Displays the adjusted questions and waits for the user's response.

[0280] Plan proposal processing

[0281] Server: Executes an algorithm to select the optimal contract plan based on user interview data and sentiment data. It also refers to usage history and feedback from other users.

[0282] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0283] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0284] Server: Receive additional questions and requests for changes, and execute an algorithm to recalculate the optimal plan.

[0285] Terminal: Display the new plan to the user.

[0286] System cooperation process

[0287] Terminal: After the user agrees to the proposed plan, display a button for "submitting a contract application".

[0288] User: The user clicks the contract application button.

[0289] Server: Receive the contract application information and cooperate with the back-end contract management system.

[0290] Server: Register the contract information in the contract management database.

[0291] Order completion notification process

[0292] Server: Confirm that the contract has been successfully completed, and send a completion notification to the user's registered email address or SMS. Send the details of the completion to the terminal.

[0293] Terminal: Display a screen indicating that the order has been completed, and provide the user with detailed information such as the contract content and the start date of use.

[0294] User: Confirm the order completion notification and receive guidance on the next steps. Also, confirm the contract content.

[0295] Specific example

[0296] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, which the server then compares with the database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the emotion engine is activated and analyzes the user's emotional state. The server analyzes the emotional data along with the interview data to calculate the optimal plan and displays it on the terminal. The user reviews this plan, and if they agree, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[0297] In this way, the present invention makes it possible to propose and accept highly accurate contract plans that take into account the user's emotions, and is expected to improve user satisfaction.

[0298] The following describes the processing flow.

[0299] Step 1:

[0300] User: The user enters their authentication information (user ID and password) into the terminal.

[0301] Step 2:

[0302] Terminal: The terminal sends the entered authentication information to the server.

[0303] Step 3:

[0304] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[0305] Step 4:

[0306] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[0307] Step 5:

[0308] Terminal: The terminal displays an error message or, if the login is successful, the personal profile.

[0309] Step 6:

[0310] Terminal: The terminal displays an interactive interface and presents the user with the first question, "Are you satisfied with the current service you are using?"

[0311] Step 7:

[0312] User: The user enters an answer to the question (e.g., "The data volume is insufficient").

[0313] Step 8:

[0314] Terminal: The terminal receives the user's answer and displays the next question, "How much data volume do you hope for?"

[0315] Step 9:

[0316] ; User: The user answers the next question (e.g., "I hope for 20GB per month").

[0317] Step 10:

[0318] Terminal: The terminal temporarily saves the answer and sends it to the server.

[0319] Step 11:

[0320] Server: The server records the user's answer in the hearing database.

[0321] Step 12:

[0322] Terminal: The terminal activates the emotion engine and captures the user's answer content and expression.

[0323] Step 13:

[0324] Server: The emotion engine analyzes the captured information and recognizes the user's emotional state.

[0325] Step 14:

[0326] Server: The server processes the recognized emotion data and adjusts the content and tone of the next question.

[0327] Step 15:

[0328] Terminal: Displays a prepared question to the user and waits for the user's response.

[0329] Step 16:

[0330] User: The user answers a pre-set question (e.g., "I'm also considering an unlimited plan").

[0331] Step 17:

[0332] Terminal: Sends additional responses from the user to the server.

[0333] Step 18:

[0334] Server: The server runs an algorithm to select the optimal contract plan again based on the additional responses and sentiment data.

[0335] Step 19:

[0336] Server: Sends the selected optimal contract plan to the terminal.

[0337] Step 20:

[0338] Device: Display new contract plans to the user (e.g., "The plan with 20GB of data per month is XXX yen, and the unlimited plan is YYY yen").

[0339] Step 21:

[0340] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[0341] Step 22:

[0342] Terminal: Sends contract application information to the server.

[0343] Step 23:

[0344] Server: Receives contract application information and integrates with the backend contract management system.

[0345] Step 24:

[0346] Server: Registers contract information in the contract management database.

[0347] Step 25:

[0348] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[0349] Step 26:

[0350] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[0351] Step 27:

[0352] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0353] (Example 2)

[0354] Next, we will describe Example 2. In the following description, the data processing device 12 will be referred to as the "server" and the smart device 14 as the "terminal".

[0355] Conventional contract plan proposal systems were limited to basic functions such as login using user authentication information, question generation, and answer recording. However, because they presented questions and plans in a fixed manner without considering the user's emotional state, user satisfaction was low, and improving the contract rate was difficult. Furthermore, they did not cover plan selection using feedback from other users, so optimal proposals were not adequately made.

[0356] The identification processing performed by the identification processing unit 290 of the data processing device 12 in Example 2 is realized by the following means. In this invention, the server includes means for determining whether or not login is permitted by comparing the authentication information entered by the user with the database; means for recognizing emotions based on the user's input information and facial expressions; means for generating and adjusting the next question based on the emotion recognition result; means for recording the answer in the database; means for executing an algorithm that selects the optimal contract plan based on the recorded data and other user information; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with the backend contract management system and processing the contract application; and means for sending a completion notification to the user when the contract is completed. This makes it possible to generate questions and propose plans that take into account the user's emotional state, thereby improving the contract rate and user satisfaction.

[0357] "Authentication information" refers to the information a user enters to identify themselves, specifically their user ID and password.

[0358] A "database" is a system for storing data in an organized and structured manner, and for searching and updating it as needed.

[0359] An "interactive interface" is an interface that allows users to communicate with a system in a two-way manner, and refers to a format where users input answers in response to questions.

[0360] "Means of recognizing emotions" refers to technologies that analyze a user's facial expressions, voice, and text to identify their emotional state.

[0361] An "algorithm" refers to a set of procedures or calculation methods defined to solve a specific problem.

[0362] A "contract plan" refers to a summary of the services and conditions that a user can subscribe to.

[0363] A "backend contract management system" refers to a core system used for managing and processing contract information.

[0364] A "completion notification" refers to a means of communication used to inform the user that a contract has been successfully completed.

[0365] "Usage history" refers to a record of services that a user has used in the past.

[0366] "Feedback" refers to information about opinions and reputations obtained from users.

[0367] "Emotion recognition results" refer to data on the user's emotional state obtained through means of recognizing emotions.

[0368] This invention relates to a system that proposes and accepts contract plans while taking into account the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[0369] As an embodiment of this system, the user authentication process will be described first. The user enters authentication information (user ID and password). The terminal sends the entered authentication information to the server. The server compares the received authentication information with the database and determines whether login is permitted. This database stores the user's authentication information. If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The terminal displays the error message, or displays the personal profile if the login is successful.

[0370] Next, we will explain the request gathering process. The terminal displays an interactive interface to users who have successfully logged in. The first question presented is, "Are you satisfied with the service you are currently using?" The user enters an answer to the question (e.g., "I don't have enough data"). The terminal receives the user's answer and displays the next question, "How much data do you need?" The user answers the next question (e.g., "I need 20GB per month"). The terminal temporarily saves the answer and sends it to the server. The server records the user's answer in the request database.

[0371] In emotion recognition processing, an emotion engine is activated to analyze the user's responses and facial expressions. The terminal uses this emotion engine to analyze the user's emotional state and generate emotion data. The server adjusts the content and tone of the next question based on this emotion data and sends it to the terminal. The terminal displays the adjusted question and waits for the user's response.

[0372] Furthermore, during the plan proposal process, the server executes an algorithm that uses user interview data and sentiment data to select the optimal contract plan. This algorithm also refers to the user's usage history and feedback from other users, and uses a machine learning model. The server sends the optimal plan to the terminal. The terminal displays the proposed plan received from the server to the user, who then reviews and agrees to the plan.

[0373] In the system integration process, after the user agrees to the proposed plan, the terminal displays a button to execute a "contract application." When the user clicks the contract application button, the server receives the contract application information and integrates with the backend contract management system. This registers the contract information in the contract management database.

[0374] During the order completion notification process, the server confirms that the contract has been completed and sends a completion notification to the user's registered email address or via SMS. The device also simultaneously displays a completion screen, providing the user with detailed information such as the contract details and the start date of service. The user confirms this notification and proceeds to the next step.

[0375] As a concrete example, consider a scenario where a user wishes to change their plan at a terminal installed at a train station's ticket gate. When the user enters their authentication information into the terminal, the server verifies it against a database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, an emotion engine is activated to analyze the user's emotional state. Based on this data, the server calculates the optimal plan and displays it on the terminal. Once the user reviews and agrees to the plan, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[0376] This will enable the proposal and application of highly accurate contract plans that take user emotions into consideration, and is expected to improve user satisfaction.

[0377] Examples of prompt statements to input into a generative AI model include the following:

[0378] "Please enter the questions users will use to choose a new data plan."

[0379] "Please generate an error message to display when login fails."

[0380] "Please use the emotion recognition engine to analyze the user's emotional state and input the results."

[0381] The flow of the specific processing in Example 2 will be explained using Figure 13.

[0382] Step 1: User Authentication Process

[0383] The user enters their authentication information (user ID and password) into the terminal. The input data consists of the user ID and password.

[0384] The terminal sends the entered authentication information to the server. The input data is the user ID and password, and the output is the authentication information sent to the server.

[0385] The server compares the received authentication information with the database to determine whether the login is successful or not. The input data consists of the user ID and password; the corresponding information is retrieved from the database and compared with the authentication information. The output is either a successful or unsuccessful login.

[0386] If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The output is either the personal profile or the error message.

[0387] The device will either display an error message or, if the login was successful, display the user's personal profile. The output will be either an error message or the user's personal profile.

[0388] Step 2: Request gathering process

[0389] The terminal displays an interactive interface to users who have successfully logged in. It presents the question, "Are you satisfied with the service you are currently using?". The input data is a successful login, and the output is the display of the question.

[0390] The user enters an answer to a question (e.g., "Insufficient data"). The output is the user's answer.

[0391] The terminal receives the user's response and displays the next question, "How much data do you need?". The input data is the user's response, and the output is the display of the next question.

[0392] The user answers the following question (e.g., "I want 20GB per month"). The output is the user's response.

[0393] The terminal temporarily stores the response and sends it to the server. The input data is the user's response, and the output is the data sent to the server.

[0394] The server records the user's responses in a hearing database. The input data is the user's responses, and the output is the recording in the database.

[0395] Step 3: Emotion Recognition Processing

[0396] The device activates an emotion engine to analyze the user's responses and facial expressions. The input data consists of the user's responses and facial expressions, and the output is the analysis result.

[0397] The server uses an emotion engine to analyze the user's emotional state and generate emotion data. The input data consists of the user's responses and facial expression data, and the output is emotion data.

[0398] The server adjusts the content and tone of the next question based on the emotional state and sends it to the terminal. The input data is emotional data and its analysis results, and the output is the adjusted question content.

[0399] The terminal displays the adjusted question and waits for the user's response. The output is the display of the adjusted question.

[0400] Step 4: Plan Proposal Processing

[0401] The server executes an algorithm that selects the optimal contract plan using user interview data and sentiment data. The input data is interview data and sentiment data, and the output is the optimal plan.

[0402] The server also refers to usage history and feedback from other users. The input data is usage history and feedback, and the output is the optimized calculation result of the algorithm.

[0403] The server sends the optimal plan to the terminal. The input data is the optimal plan, and the output is the data sent to the terminal.

[0404] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen"). The output is the display of the plan.

[0405] The user reviews the proposed plan and enters any additional questions or requested changes as needed (e.g., "Is there a plan with unlimited data usage?"). The output consists of these additional questions and requested changes.

[0406] The server receives additional questions and requested changes and runs an algorithm to recalculate the optimal plan. The input data is the additional questions and requested changes, and the output is the recalculated optimal plan.

[0407] The device displays the new plan to the user. The output is a display of the new plan.

[0408] Step 5: System Integration Process

[0409] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The output is the display of the Subscription Application button.

[0410] The user clicks the contract application button. The output indicates their intention to apply for the contract.

[0411] The server receives contract application information and interacts with the backend contract management system. The input data is the contract application information, and the output is the data to be sent to the contract management system.

[0412] The server registers contract information in the contract management database. The input data is the contract information, and the output is the data registered in the database.

[0413] Step 6: Order completion notification processing

[0414] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input data is the contract completion information, and the output is the completion notification.

[0415] The server sends completion details to the terminal. The input data is contract completion information, and the output is the data sent to the terminal.

[0416] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The output is a display of the completion screen.

[0417] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The output consists of a confirmation of the notification and instructions for the next steps.

[0418] (Application Example 2)

[0419] Next, we will explain application example 2. In the following explanation, the data processing device 12 will be referred to as a "server" and the smart device 14 as a "terminal".

[0420] Traditional e-commerce sites relied primarily on past purchase and search history to determine user preferences. However, this approach failed to consider user emotional states, making it difficult to recommend optimal products. Furthermore, the systems for enabling users to select products and complete purchases smoothly and without stress were inadequate. As a result, improving user satisfaction proved challenging.

[0421] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means.

[0422] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recognizing the user's emotional state based on an image of the user; means for recording the answers and emotional state in a database; means for executing an algorithm to select the optimal product based on the recorded data and emotional data; means for displaying the selected product to the user and accepting the purchase application; means for linking the purchase application information with a backend contract management system and processing the purchase application; and means for sending a completion notification to the user when the purchase is completed. This enables optimal product suggestions that also take into account the user's emotional state and a smooth purchase procedure.

[0423] "User authentication" is the process of verifying whether a user has legitimate access rights based on the authentication information they provide.

[0424] An "interactive interface" is an interface that allows the user and the system to communicate in both directions.

[0425] "Emotion recognition" is a technology that analyzes a user's emotional state based on their images, voice, and text.

[0426] A "database" is a data management system that organizes and stores large amounts of data, making it possible to retrieve it quickly as needed.

[0427] An "algorithm" is a set of specific steps or procedures for solving a particular problem.

[0428] A "contract management system" is a system that centrally manages users' contract information and efficiently processes contracts.

[0429] A "purchase request" is the process by which a user expresses their intention to purchase a selected product and requests that the product be purchased.

[0430] A "completion notice" is a notification that informs that a particular process or procedure has been successfully completed.

[0431] This invention relates to a system that provides product suggestions and facilitates purchases while taking into account the user's emotional state. The system aims to enable users to access e-commerce sites using their smartphones, receive optimal product suggestions through an interactive interface, and complete the purchase process smoothly.

[0432] User Authentication

[0433] When a user enters their authentication information (user ID and password) into the app, the device sends it to the server. The server compares it with the database to determine whether the login is successful. If the login is successful, the server sends the user's personal profile back to the device, and user authentication is complete.

[0434] Interactive interface

[0435] After logging in, the device displays an interactive interface. The first question displayed is, "What kind of products have you been interested in lately?" When the user enters an answer, that answer is sent to the server and the next question is generated. For example, if the user answers "fashion items," the next question displayed will be, "Specifically, what kind of items are you looking for?"

[0436] emotion recognition

[0437] The user's responses, along with image data captured by the device's camera, are sent to the server. The server uses an emotion recognition engine to analyze the user's emotional state. This emotion recognition engine works in conjunction with image processing software such as OpenCV and generates emotion data using a generative AI model.

[0438] Database records

[0439] User responses and emotional data are stored in temporary memory and then recorded in a hearing database. This allows for the accumulation of data that reflects the user's preferences and emotional state.

[0440] Product suggestion

[0441] The server executes an algorithm to suggest the optimal product based on accumulated hearing and sentiment data. This algorithm selects products to suggest, taking into account the user's past purchase history and feedback from other users. The specific product and price are then displayed on the terminal in the format of "This is the perfect fashion item for you."

[0442] Purchase application and completion notification

[0443] When a user agrees to a suggested product and submits a purchase request, the device sends that information to the server. The server then integrates with the backend contract management system to automatically complete the purchase process. Once the purchase is complete, the server sends a completion notification to the user's registered email address or via SMS, and a purchase completion screen is also displayed on the device.

[0444] Specific example

[0445] 1. Example of a prompt:

[0446] Authentication information entry: "Please enter your User ID and password."

[0447] Emotion recognition: "Please take a picture of your face with the camera."

[0448] Suggestions based on purchase history: "Based on your past purchase history and sentiment data, we suggest the following products."

[0449] For example, a user opens the app, enters their ID and password, and logs in. Then, they take a picture of their face with their smartphone camera, and an emotion recognition engine analyzes their emotions. Based on past history and emotion data, the server suggests the most suitable products. The user reviews the suggested products and decides to purchase them.

[0450] This invention enables optimal product recommendations that take into account the user's emotional state and facilitates a smooth purchasing process. This is expected to improve user satisfaction.

[0451] The flow of a specific process in Application Example 2 will be explained using Figure 14.

[0452] Step 1: User Authentication

[0453] The user enters their ID and password into their smartphone. The device sends this authentication information to the server. The server compares it with the user information in the database to determine whether login is permitted. If the login is successful, the server sends the user's personal profile back to the device. The input is the user's authentication information, and the output is the personal profile upon successful login or an error message upon failure.

[0454] Step 2: Display the interactive interface

[0455] When the terminal receives a signal indicating successful login, it displays an interactive interface. The user is presented with the initial question, "What products have you been interested in recently?" Once the user enters their answer, it is sent to the server. The input is the user's response to the question, and the output is the content of the next question.

[0456] Step 3: Emotion Recognition Processing

[0457] When a user answers a question, the device's camera captures a picture of the user's face. The captured image data is sent to a server, where the server's emotion recognition engine analyzes the image. A generative AI model is used to analyze the user's emotions and generate emotion data. The input is the user's face image, and the output is the analyzed emotion data.

[0458] Step 4: Recording responses and emotional data

[0459] The server stores user responses and sentiment data in temporary storage and then records them in the hearing database. This allows data to accumulate. The input is the user's responses and sentiment data, and the output is the data stored in the hearing database.

[0460] Step 5: Run the product suggestion algorithm.

[0461] The server executes a product recommendation algorithm based on data and sentiment data recorded in the hearing database. This algorithm selects the most suitable products by referring to the user's past purchase history, usage history, and feedback from other users. The input is accumulated data and sentiment data, and the output is a list of selected products.

[0462] Step 6: Display the optimal product

[0463] The terminal displays a list of optimal products received from the server to the user. For example, it might show specific products and their prices in a format like, "These are the perfect fashion items for you." The input is a list of products selected by the server, and the output is detailed product information displayed to the user.

[0464] Step 7: Purchase Application

[0465] When a user agrees to a suggested product and submits a purchase request, the terminal sends that information to the server. The server then integrates with the backend contract management system to automatically complete the purchase process. The input is the user's purchase request information, and the output is the information linked to the contract management system.

[0466] Step 8: Purchase Completion Notification

[0467] Once the purchase is complete, the server sends a completion notification to the user's registered email address or via SMS, and also displays a purchase completion screen on the device. The user confirms that the purchase is complete and receives instructions on the next steps. The input is the purchase completion information, and the output is the completion notification and the completion screen displayed on the device.

[0468] 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 user input for the result of the specific processing. The control unit 46A transmits the audio data indicating 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.

[0469] Data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of data generation model 58 is ChatGPT (registered trademark) (Internet search).<URL: https: / / openai.com / blog / chatgpt> ), Gemini (registered trademark) (Internet search) <url: https: gemini.google.com ?hl="ja">Examples of generative AI include the following. The data generation model 58 is obtained by performing deep learning on a neural network. The data generation model 58 is input with prompts containing instructions, and with inference data such as audio data representing speech, text data representing text, and image data representing images. The data generation model 58 infers from the input inference data according to the instructions indicated by the prompts, and outputs the inference results in data formats such as audio data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0470] In the above embodiment, an example was given in which specific processing is performed by the data processing device 12, but the technology of this disclosure is not limited thereto, and the specific processing may also be performed by the smart device 14.

[0471] [Second Embodiment]

[0472] Figure 3 shows an example of the configuration of the data processing system 210 according to the second embodiment.

[0473] As shown in Figure 3, the data processing system 210 includes a data processing device 12 and smart glasses 214. An example of the data processing device 12 is a server.

[0474] The data processing device 12 comprises a computer 22, a database 24, and a communication interface 26. The computer 22 is an example of a "computer" related to the technology of this disclosure. The computer 22 comprises a processor 28, RAM 30, and storage 32. The processor 28, RAM 30, and storage 32 are connected to a bus 34. The database 24 and the communication interface 26 are also connected to the bus 34. The communication interface 26 is connected to a network 54. An example of the network 54 is a WAN (Wide Area Network) and / or a LAN (Local Area Network).

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

[0476] The microphone 238 receives voice signals from the user 20 and receives instructions from the user 20. The microphone 238 captures the voice signals from the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio according to the instructions from the processor 46.

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

[0478] Communication interface 44 is connected to network 54. Communication interfaces 44 and 26 are responsible for the exchange of various information between processor 46 and processor 28 via network 54. The exchange of various information between processor 46 and processor 28 using communication interfaces 44 and 26 is performed in a secure manner.

[0479] Figure 4 shows an example of the main functions of the data processing device 12 and the smart glasses 214. As shown in Figure 4, the data processing device 12 performs specific processing using the processor 28. The storage 32 stores the specific processing program 56.

[0480] The specific processing program 56 is an example of a "program" relating to the technology of this 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.

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

[0482] In the smart glasses 214, the processor 46 performs the reception output processing. The storage 50 stores the reception output program 60. 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 processing is realized by the processor 46 operating as a control unit 46A according to the reception output program 60 executed on the RAM 48.

[0483] Next, the identification processing performed by the identification processing unit 290 of the data processing device 12 will be described. 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".

[0484] This invention relates to a system that allows users to easily and efficiently propose and apply for contract plans. This system logs in based on the user's authentication information, listens to the user's requests and preferences through an interactive interface, and proposes the most suitable contract plan based on that information. Furthermore, it can automatically process the contract application and finally sends a contract completion notification to the user.

[0485] Program processing

[0486] User authentication process

[0487] User: The user enters their authentication information (user ID and password) into the terminal.

[0488] Terminal: The terminal sends the entered authentication information to the server.

[0489] Server: The server compares the received authentication information with the database and determines whether login is permitted. If successful, it returns the user's personal profile to the terminal. If unsuccessful, it returns an error message.

[0490] Device: The device will either display an error message or, if successful, display the user's personal profile.

[0491] Request gathering process

[0492] Terminal: Displays an interactive interface to users who have successfully logged in. It displays initial questions such as, "Are you satisfied with the service you are currently using?"

[0493] User: The user answers the question (e.g., "Insufficient data").

[0494] Terminal: The terminal receives the response and generates and displays the next question (e.g., "How much data do you want?").

[0495] User: The user also answers the following question (e.g., "I would like 20GB per month").

[0496] Terminal: Temporarily saves the answer and sends it to the server.

[0497] Server: Records user responses in the hearing database.

[0498] Plan proposal processing

[0499] Server: Executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users.

[0500] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0501] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0502] Server: We will receive any additional questions or requested changes and recalculate the optimal plan.

[0503] Device: Display the new plan to the user.

[0504] System Integration Processing

[0505] Device: After the user agrees to the proposed plan, a button will be displayed to proceed with the "Subscription Application".

[0506] User: The user clicks the contract application button.

[0507] Server: Receives contract application information and integrates with the backend contract management system. Registers contract information in the contract management database.

[0508] Order completion notification processing

[0509] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or SMS. Sends completion details to the device.

[0510] Terminal: Displays a screen indicating that the order has been completed and provides the user with detailed information such as contract details and service start date.

[0511] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0512] Specific example

[0513] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, the server verifies it against the database, and the login process is initiated. If the login is successful, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server calculates the optimal plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[0514] In this way, the present invention makes it possible to accurately understand user needs and propose and accept efficient and user-friendly contract plans.

[0515] The following describes the processing flow.

[0516] Step 1:

[0517] User: The user enters their authentication information (user ID and password) into the terminal.

[0518] Step 2:

[0519] Terminal: The terminal sends the entered authentication information to the server.

[0520] Step 3:

[0521] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[0522] Step 4:

[0523] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[0524] Step 5:

[0525] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[0526] Step 6:

[0527] Terminal: Displays an interactive interface and presents the user with the question, "Are you satisfied with the service you are currently using?"

[0528] Step 7:

[0529] User: The user enters an answer to the question (e.g., "Insufficient data").

[0530] Step 8:

[0531] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[0532] Step 9:

[0533] User: The user answers the following question (e.g., "I would like 20GB per month").

[0534] Step 10:

[0535] Terminal: The terminal temporarily stores the answer and sends it to the server.

[0536] Step 11:

[0537] Server: The server records the user's responses in the hearing database.

[0538] Step 12:

[0539] Server: The server analyzes the recorded interview data and runs an algorithm to select the optimal contract plan.

[0540] Step 13:

[0541] Server: Sends the selected optimal contract plan to the terminal.

[0542] Step 14:

[0543] Device: The device displays the proposed contract plan to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0544] Step 15:

[0545] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0546] Step 16:

[0547] Terminal: Sends additional questions or requested changes from the user to the server.

[0548] Step 17:

[0549] Server: Receives additional questions or requested changes and runs an algorithm to recalculate the optimal plan.

[0550] Step 18:

[0551] Server: Sends the new contract plan to the device.

[0552] Step 19:

[0553] Device: Display new contract plans to the user.

[0554] Step 20:

[0555] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[0556] Step 21:

[0557] Terminal: Sends contract application information to the server.

[0558] Step 22:

[0559] Server: Receives contract application information and integrates with the backend contract management system.

[0560] Step 23:

[0561] Server: Registers contract information in the contract management database.

[0562] Step 24:

[0563] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[0564] Step 25:

[0565] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[0566] Step 26:

[0567] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0568] (Example 1)

[0569] Next, we will describe Example 1. 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."

[0570] Conventional contract plan proposal systems failed to adequately reflect user needs and preferences, making it difficult to provide users with the most suitable contract plan quickly and efficiently. In particular, a challenge was the inability to recalculate the plan when users had additional questions or requested changes to the presented plan, resulting in a degraded user experience.

[0571] The identification process performed by the identification processing unit 290 of the data processing device 12 in Example 1 is realized by the following means.

[0572] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recording the answers in a database; means for executing an algorithm to select the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; and means for receiving additional questions or change requests from the user, and recalculating and displaying the optimal contract plan again. This makes it possible to accurately grasp the user's needs and desires, propose the optimal contract plan, and quickly make revised proposals.

[0573] "Authentication information" refers to the information a user needs to log in to a system, and typically consists of a user ID and password.

[0574] A "database" is an organized collection of data, a system for retrieving, storing, and updating information.

[0575] An "interactive interface" is a user interface that allows the user and the system to communicate in both directions.

[0576] "Means for generating questions and answers" refers to a function that creates appropriate questions based on user input and collects user responses to those questions.

[0577] An "algorithm" is a set of procedures or computational methods for solving a specific problem.

[0578] A "contract plan" refers to the terms and conditions of the agreement for a user to use the service.

[0579] "Application information" refers to the necessary data that a user provides when they wish to enter into a contract.

[0580] A "backend contract management system" is a system used for managing and updating contract details.

[0581] A "completion notification" is a notification sent to inform a user that a transaction or procedure has been successfully completed.

[0582] "Additional questions or requested changes" refers to any further information the user would like to know or any changes they would like to make regarding the proposed plan.

[0583] This invention relates to a system for users to easily and efficiently propose and apply for contract plans. This system includes the following processes: user authentication, requirements gathering, plan proposal, system integration, and order completion notification.

[0584] Hardware and software to be used

[0585] The system's hardware includes a server, terminals (e.g., tablet devices), and a database. The server is responsible for processes such as verifying authentication information, executing plan proposal algorithms, and sending notifications. The software used includes a MySQL or PostgreSQL database, algorithms implemented in Python, and a mail server (e.g., SendGrid). Terminals handle the display of the user interface, input of user data, and communication with the server, using a standard web browser or interactive interface software.

[0586] Processing details

[0587] The server first receives the authentication information (user ID and password) entered by the user and compares it with the database. If authentication is successful, the user's personal profile is returned and displayed on the terminal. Next, the terminal displays an interactive interface to hear the user's requests and preferences. A question-and-answer exchange takes place, and this information is sent to the server and recorded in the database.

[0588] The server uses machine learning models and other tools to calculate and select the optimal contract plan based on recorded data. This calculation takes into account the user's usage history and feedback from other users. The selected plan is displayed on the terminal, and the user reviews the proposal and enters additional questions or requests for changes via the terminal as needed. The server receives this new information, recalculates the plan, and displays the result on the terminal.

[0589] If the user agrees to the proposed plan, the device displays a contract application button, and when the user clicks it, the contract application information is sent to the server. The server then integrates this information with the backend contract management system to finalize the contract. Once the contract is complete, the server sends a completion notification to the user's registered email address or via SMS, and the device also displays confirmation of the order completion.

[0590] Specific example

[0591] For example, if a user wishes to change their plan using a tablet terminal installed at a train station's ticket gate, they can follow these steps: The user enters their authentication information into the terminal, the server verifies it against a database, and the login process is initiated. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server uses a machine learning model implemented in Python to calculate the optimal contract plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal. In this way, the present invention enables accurate understanding of user needs and allows for the proposal and application of efficient and user-friendly contract plans.

[0592] Example of a prompt

[0593] "Please describe the system's processing flow for users to change their plan at terminals installed at train station ticket gates. Please include the specific names of the hardware and software used at each step, from user authentication to contract completion notification."

[0594] The flow of the specific processing in Example 1 will be explained using Figure 11.

[0595] Step 1:

[0596] The user enters their authentication information (user ID and password) into the terminal. This input is done using a text field. The input data consists of the user ID and password.

[0597] Step 2:

[0598] The terminal encrypts the entered authentication information and sends it to the server. Specifically, it encrypts and transmits the data using the SSL / TLS protocol. The input is the encrypted authentication information, and the output is the request to the server.

[0599] Step 3:

[0600] The server compares the received authentication information with the database. The database stores the user ID and the hashed password. The server retrieves the password hash corresponding to the user ID from the database and compares it with the input password. The input is encrypted authentication information, and the output is the authentication result (success / failure).

[0601] Step 4:

[0602] The server returns the user's personal profile to the terminal if authentication is successful, and an error message if it fails. The input is the authentication result, and the output is either the personal profile or the error message.

[0603] Step 5:

[0604] The device receives the authentication result and, if the login is successful, displays the user's personal profile; if it fails, it displays an error message. The input is the personal profile or the error message, and the output is the screen display.

[0605] Step 6:

[0606] The terminal displays an interactive interface to users who have successfully logged in, and shows the initial question, "Are you satisfied with the services you are currently using?". The input is the user's personal profile, and the output is the screen display of the question.

[0607] Step 7:

[0608] The user answers a question (e.g., "Insufficient data"). User input is provided through an interactive interface. Input is the user's answer to the question, and output is the transmission of the answer to the terminal.

[0609] Step 8:

[0610] The terminal receives the user's response and generates and displays the next question, "How much data do you need?". The input is the user's initial response, and the output is the screen display for the next question. The terminal temporarily stores this data.

[0611] Step 9:

[0612] The user also answers the following question (e.g., "I want 20GB per month"). This input is done through an interactive interface. The input is the user's answer to the following question, and the output is the transmission of the answer to the terminal.

[0613] Step 10:

[0614] The terminal temporarily stores the response and sends it to the server. The input is the user's response, and the output is the data sent to the server.

[0615] Step 11:

[0616] The server records user responses in a hearing database. The input is the user's response data, and the output is saving it to the database.

[0617] Step 12:

[0618] The server executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users. The inputs are interview data, usage history data, and feedback data, and the output is the optimal contract plan.

[0619] Step 13:

[0620] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is available for XXX yen"). The input is the proposed plan data, and the output is the screen display.

[0621] Step 14:

[0622] The user reviews the proposed plan and enters additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?"). This input is done through an interactive interface. The input consists of additional questions or requests for changes, and the output is the response sent to the device.

[0623] Step 15:

[0624] The server receives additional questions and requested changes and recalculates the optimal plan. The input is the data for the additional questions and requested changes, and the output is the recalculated contract plan.

[0625] Step 16:

[0626] The device displays the new plan to the user. The input is the recalculated contract plan data, and the output is the screen display.

[0627] Step 17:

[0628] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The input is the user's agreement, and the output is the display of the subscription application button.

[0629] Step 18:

[0630] The user clicks the contract application button. The input is the click of the contract application button, and the output is the submission of contract information.

[0631] Step 19:

[0632] The server receives contract application information and interacts with the backend contract management system. The input is the contract application information, and the output is the transmission of data to the contract management system.

[0633] Step 20:

[0634] The server registers contract information in the contract management database. The input is contract application information, and the output is saving it to the database.

[0635] Step 21:

[0636] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input is the contract completion information, and the output is the sending of the completion notification.

[0637] Step 22:

[0638] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The input is the contract completion information, and the output is the screen display.

[0639] Step 23:

[0640] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The input is the completion notification, and the output is the confirmation and instructions for the next steps.

[0641] (Application Example 1)

[0642] Next, we will explain Application Example 1. In the following explanation, the data processing device 12 will be referred to as the "server," and the smart glasses 214 will be referred to as the "terminal."

[0643] In recent years, with the advancement of e-commerce, users need to select the optimal purchase plan and products from a vast amount of product information, thus requiring a more efficient purchasing experience and personalized suggestions. Conventional systems struggle to fully meet user needs, and in particular, they lack the means to propose the most suitable products in an interactive format and to facilitate a smooth purchasing process. Therefore, to improve user satisfaction, a system is needed that uses an interactive interface to quickly and accurately understand user requests and provide optimal product suggestions and purchasing procedures.

[0644] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 1 is realized by the following means.

[0645] In this invention, the server includes means for matching user authentication information with a database and determining whether or not login is permitted; means for generating questions and answers through an interactive interface based on user input information; means for recording the answers in a database; means for executing an algorithm for selecting the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; means for selecting the optimal purchase plan by referring to usage history and feedback from other users; and means for displaying product suggestions to the user based on the purchase plan and accepting the purchase procedure. This enables the user to efficiently select the optimal product from a large amount of product information and smoothly complete the purchase procedure.

[0646] "User authentication" is a series of processes that compare the authentication information a user provides to log in to a system with a database and determine whether or not they are allowed to log in.

[0647] An "interactive interface" is an interface used to facilitate smooth interaction with users, and it is a mechanism that dynamically generates questions and answers based on user input.

[0648] "Authentication information" refers to information such as user ID and password that a user uses when logging into a system.

[0649] A "database" is an electronic information recording system used to store and manage user information, interview data, contract details, and other similar information.

[0650] An "algorithm" is a set of procedures or calculation methods for achieving a specific objective, and in this system, it is a means of selecting the optimal contract or purchase plan.

[0651] A "backend system" is a system that manages and processes contract and purchase information, separate from the frontend system that interacts directly with users.

[0652] A "contract plan" refers to the specific details of the services or products offered to the user, along with their pricing.

[0653] A "purchase plan" is a plan that proposes the optimal combination of products to be obtained by purchasing them all at once or as a set, based on the user's needs.

[0654] A "completion notification" is a notification sent to the user informing them that the contract or purchase procedure has been successfully completed, and is sent via email, SMS, or other means.

[0655] "Usage history" refers to records of operations, selections, and purchases that a user has made through the system in the past.

[0656] "Feedback" refers to opinions and evaluations provided by users and other users, which are used in selecting plans and proposing products within this system.

[0657] The system for implementing this invention is designed to provide users with efficient and personalized proposals and procedures for contract and purchase plans. The system supports a series of processes in which the user easily authenticates, inputs their needs through an interactive interface, is proposed the most suitable plan, and completes the purchase or contract procedure.

[0658] The system configuration is as follows:

[0659] Hardware and software to use

[0660] Hardware: Smartphone

[0661] Software: Mobile app (iOS and Android), server-side uses AWS (Amazon Web Services).

[0662] Database: MySQL or PostgreSQL

[0663] Generative AI model: GPT-4 (OpenAI)

[0664] User authentication process

[0665] The user launches the smartphone app and enters their ID and password. The app sends this information to the server, which verifies the authentication information against a database. If authentication is successful, the user's personal profile is displayed in the app.

[0666] Request gathering process

[0667] After successful login, the app displays an interactive interface. For example, the first question displayed might be, "Are you satisfied with your recent purchase?" The user answers this question (e.g., "I want a more portable product"), and the app generates and displays the next question. By repeating this process, the app collects the user's requests and sends them to the server. The server records this data in a hearing database.

[0668] Plan proposal processing

[0669] The server uses recorded user responses to run an algorithm to select the optimal contract or purchase plan. Usage history and feedback from other users are also referenced. The calculated plan is presented to the user through the app.

[0670] System Integration Processing

[0671] Once a user agrees to a proposed plan, they can tap a button within the app to complete the contract application or purchase process. The server receives this information, processes it in conjunction with the backend contract management system and order management system, and registers the contract or purchase information in the relevant database.

[0672] Order completion notification processing

[0673] When a contract or purchase is completed, the server sends a completion notification to the user. This notification is sent to the registered email address or via SMS. A completion screen is also displayed in the app, allowing the user to confirm the contract details and purchase information.

[0674] Specific example

[0675] For example, if a user logs into a smartphone app and, in the interactive interface, indicates they are looking for "cooking utensils that are easy to use at a campsite they recently visited," the system will suggest a "lightweight and easy-to-pack camping cooking set," and will also display current discount information and related products. Once the user reviews the suggestion, agrees, and taps to purchase, the order is immediately completed, and an order confirmation notification is sent to their smartphone.

[0676] Example of a prompt

[0677] "I'm looking for easy-to-use cooking utensils at a campsite I recently visited."

[0678] "What type of cooking utensils do you prefer? (e.g., lightweight, portable, set, etc.)"

[0679] "Something lightweight and easy to package."

[0680] "Our recommended product is a lightweight and easy-to-pack camping cooking set. It's currently 30% off. Would you like to purchase it?"

[0681] "yes"

[0682] "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[0683] By implementing this system, we can accurately grasp user needs and achieve efficient, personalized contract and purchasing processes.

[0684] The flow of a specific process in Application Example 1 will be explained using Figure 12.

[0685] Step 1: User Authentication Process

[0686] The user launches the smartphone app and enters their ID and password on the authentication screen. The user ID and password are provided as input.

[0687] The terminal sends the entered authentication information to the server. At this time, the user ID and password are sent to the server as data packets.

[0688] The server compares the received authentication information with the database to determine whether or not the login is permitted. This process involves comparing the user information stored in the database with the entered authentication information.

[0689] The server returns the user's personal profile to the device if authentication is successful, and an error message if it fails. The output upon successful authentication is the user's profile information, while the output upon failure is an error message.

[0690] Based on the received data, the device will display the personal profile screen if successful, or an error message if unsuccessful.

[0691] Step 2: Request gathering process

[0692] The terminal displays an interactive interface to users who have successfully logged in. The system's initial question is, "Are you satisfied with your recent purchases?" The user is then provided with further questions as input.

[0693] The user enters an answer to this question (e.g., "I want a product that is easier to carry"). That answer is then sent to the device.

[0694] The device temporarily stores the user's response and generates and displays the next question (e.g., "What type of product do you prefer?"). The generated question is created by an AI model based on the user's response.

[0695] The server receives response data sent from the terminal and records it in the hearing database. User response data is provided as input, and recorded in the hearing database as output.

[0696] Step 3: Plan Proposal Processing

[0697] The server executes an algorithm to select the optimal contract plan based on recorded user interview data. This algorithm also utilizes usage history and feedback from other users stored in the database. The input to this process is user interview data and usage history, and the output is the selected contract plan.

[0698] The server sends the selected plan to the terminal, and the terminal displays the plan to the user (e.g., "Lightweight and easy-to-pack camping cooking set available at 30% off"). The sent plan is displayed as output.

[0699] Step 4: System Integration Process

[0700] If the user agrees to the proposed plan, they tap the purchase button displayed on their device. The user's consent action is provided as input.

[0701] The server receives the operation information and processes the contract application in cooperation with the backend contract management system. This cooperation process includes registering the user's purchase information in the contract management system. As output, the contract application information is registered in the system.

[0702] The server registers the purchase completion information in the contract management database. Purchase completion data is provided as input.

[0703] Step 5: Order completion notification processing

[0704] The server sends a completion notification to the user's registered email address or via SMS when a contract or purchase is completed. Completion notification data is provided as input, and the completion notification is sent to the user as output.

[0705] The device displays a completion screen to the user, providing contract details and purchase information. The output is the completion screen.

[0706] The user can then confirm the completion notification and proceed to the next step. Specifically, it might display something like, "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[0707] This series of processes allows users to efficiently and personalizedly enter into service contracts and purchase products.

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

[0709] This invention relates to a system that proposes and accepts contract plans while also considering the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[0710] Program processing

[0711] User authentication process

[0712] User: The user enters their authentication information (user ID and password) into the terminal.

[0713] Terminal: The terminal sends the entered authentication information to the server.

[0714] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[0715] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[0716] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[0717] Request gathering process

[0718] Terminal: Displays an interactive interface to users who have successfully logged in. The initial question is, "Are you satisfied with the service you are currently using?"

[0719] User: The user enters an answer to the question (e.g., "Insufficient data").

[0720] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[0721] User: The user answers the following question (e.g., "I would like 20GB per month").

[0722] Terminal: Temporarily saves the answer and sends it to the server.

[0723] Server: Records user responses in the hearing database.

[0724] Emotion recognition processing

[0725] Terminal: Activates an emotion engine to recognize emotions from the user's responses and facial expressions.

[0726] Server: The emotion engine analyzes the user's emotional state and generates emotion data.

[0727] Server: Based on the emotional state, adjust the content and tone of the next question and send it to the terminal.

[0728] Terminal: Displays the adjusted questions and waits for the user's response.

[0729] Plan proposal processing

[0730] Server: Executes an algorithm to select the optimal contract plan based on user interview data and sentiment data. It also refers to usage history and feedback from other users.

[0731] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0732] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0733] Server: Receives additional questions or requested changes and runs an algorithm to recalculate the optimal plan.

[0734] Device: Display the new plan to the user.

[0735] System Integration Processing

[0736] Device: After the user agrees to the proposed plan, a button will be displayed to proceed with the "Subscription Application".

[0737] User: The user clicks the contract application button.

[0738] Server: Receives contract application information and integrates with the backend contract management system.

[0739] Server: Registers contract information in the contract management database.

[0740] Order completion notification processing

[0741] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or SMS. Sends completion details to the device.

[0742] Terminal: Displays a screen indicating that the order has been completed and provides the user with detailed information such as contract details and service start date.

[0743] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0744] Specific example

[0745] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, which the server then compares with the database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the emotion engine is activated and analyzes the user's emotional state. The server analyzes the emotional data along with the interview data to calculate the optimal plan and displays it on the terminal. The user reviews this plan, and if they agree, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[0746] In this way, the present invention makes it possible to propose and accept highly accurate contract plans that take into account the user's emotions, and is expected to improve user satisfaction.

[0747] The following describes the processing flow.

[0748] Step 1:

[0749] User: The user enters their authentication information (user ID and password) into the terminal.

[0750] Step 2:

[0751] Terminal: The terminal sends the entered authentication information to the server.

[0752] Step 3:

[0753] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[0754] Step 4:

[0755] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[0756] Step 5:

[0757] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[0758] Step 6:

[0759] Terminal: Displays an interactive interface and presents the user with the initial question, "Are you satisfied with the service you are currently using?"

[0760] Step 7:

[0761] User: The user enters an answer to the question (e.g., "Insufficient data").

[0762] Step 8:

[0763] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[0764] Step 9:

[0765] User: The user answers the following question (e.g., "I would like 20GB per month").

[0766] Step 10:

[0767] Terminal: The terminal temporarily stores the answer and sends it to the server.

[0768] Step 11:

[0769] Server: The server records the user's responses in the hearing database.

[0770] Step 12:

[0771] Terminal: The terminal activates the emotion engine and captures the user's responses and facial expressions.

[0772] Step 13:

[0773] Server: The emotion engine analyzes the captured information and recognizes the user's emotional state.

[0774] Step 14:

[0775] Server: The server processes the recognized emotion data and adjusts the content and tone of the next question.

[0776] Step 15:

[0777] Terminal: Displays a prepared question to the user and waits for the user's response.

[0778] Step 16:

[0779] User: The user answers a pre-set question (e.g., "I'm also considering an unlimited plan").

[0780] Step 17:

[0781] Terminal: Sends additional responses from the user to the server.

[0782] Step 18:

[0783] Server: The server runs an algorithm to select the optimal contract plan again based on the additional responses and sentiment data.

[0784] Step 19:

[0785] Server: Sends the selected optimal contract plan to the terminal.

[0786] Step 20:

[0787] Device: Display new contract plans to the user (e.g., "The plan with 20GB of data per month is XXX yen, and the unlimited plan is YYY yen").

[0788] Step 21:

[0789] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[0790] Step 22:

[0791] Terminal: Sends contract application information to the server.

[0792] Step 23:

[0793] Server: Receives contract application information and integrates with the backend contract management system.

[0794] Step 24:

[0795] Server: Registers contract information in the contract management database.

[0796] Step 25:

[0797] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[0798] Step 26:

[0799] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[0800] Step 27:

[0801] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0802] (Example 2)

[0803] Next, we will describe Example 2. 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".

[0804] Conventional contract plan proposal systems were limited to basic functions such as login using user authentication information, question generation, and answer recording. However, because they presented questions and plans in a fixed manner without considering the user's emotional state, user satisfaction was low, and improving the contract rate was difficult. Furthermore, they did not cover plan selection using feedback from other users, so optimal proposals were not adequately made.

[0805] The identification processing performed by the identification processing unit 290 of the data processing device 12 in Example 2 is realized by the following means. In this invention, the server includes means for determining whether or not login is permitted by comparing the authentication information entered by the user with the database; means for recognizing emotions based on the user's input information and facial expressions; means for generating and adjusting the next question based on the emotion recognition result; means for recording the answer in the database; means for executing an algorithm that selects the optimal contract plan based on the recorded data and other user information; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with the backend contract management system and processing the contract application; and means for sending a completion notification to the user when the contract is completed. This makes it possible to generate questions and propose plans that take into account the user's emotional state, thereby improving the contract rate and user satisfaction.

[0806] "Authentication information" refers to the information a user enters to identify themselves, specifically their user ID and password.

[0807] A "database" is a system for storing data in an organized and structured manner, and for searching and updating it as needed.

[0808] An "interactive interface" is an interface that allows users to communicate with a system in a two-way manner, and refers to a format where users input answers in response to questions.

[0809] "Means of recognizing emotions" refers to technologies that analyze a user's facial expressions, voice, and text to identify their emotional state.

[0810] An "algorithm" refers to a set of procedures or calculation methods defined to solve a specific problem.

[0811] A "contract plan" refers to a summary of the services and conditions that a user can subscribe to.

[0812] A "backend contract management system" refers to a core system used for managing and processing contract information.

[0813] A "completion notification" refers to a means of communication used to inform the user that a contract has been successfully completed.

[0814] "Usage history" refers to a record of services that a user has used in the past.

[0815] "Feedback" refers to information about opinions and reputations obtained from users.

[0816] "Emotion recognition results" refer to data on the user's emotional state obtained through means of recognizing emotions.

[0817] This invention relates to a system that proposes and accepts contract plans while taking into account the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[0818] As an embodiment of this system, the user authentication process will be described first. The user enters authentication information (user ID and password). The terminal sends the entered authentication information to the server. The server compares the received authentication information with the database and determines whether login is permitted. This database stores the user's authentication information. If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The terminal displays the error message, or displays the personal profile if the login is successful.

[0819] Next, we will explain the request gathering process. The terminal displays an interactive interface to users who have successfully logged in. The first question presented is, "Are you satisfied with the service you are currently using?" The user enters an answer to the question (e.g., "I don't have enough data"). The terminal receives the user's answer and displays the next question, "How much data do you need?" The user answers the next question (e.g., "I need 20GB per month"). The terminal temporarily saves the answer and sends it to the server. The server records the user's answer in the request database.

[0820] In emotion recognition processing, an emotion engine is activated to analyze the user's responses and facial expressions. The terminal uses this emotion engine to analyze the user's emotional state and generate emotion data. The server adjusts the content and tone of the next question based on this emotion data and sends it to the terminal. The terminal displays the adjusted question and waits for the user's response.

[0821] Furthermore, during the plan proposal process, the server executes an algorithm that uses user interview data and sentiment data to select the optimal contract plan. This algorithm also refers to the user's usage history and feedback from other users, and uses a machine learning model. The server sends the optimal plan to the terminal. The terminal displays the proposed plan received from the server to the user, who then reviews and agrees to the plan.

[0822] In the system integration process, after the user agrees to the proposed plan, the terminal displays a button to execute a "contract application." When the user clicks the contract application button, the server receives the contract application information and integrates with the backend contract management system. This registers the contract information in the contract management database.

[0823] During the order completion notification process, the server confirms that the contract has been completed and sends a completion notification to the user's registered email address or via SMS. The device also simultaneously displays a completion screen, providing the user with detailed information such as the contract details and the start date of service. The user confirms this notification and proceeds to the next step.

[0824] As a concrete example, consider a scenario where a user wishes to change their plan at a terminal installed at a train station's ticket gate. When the user enters their authentication information into the terminal, the server verifies it against a database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, an emotion engine is activated to analyze the user's emotional state. Based on this data, the server calculates the optimal plan and displays it on the terminal. Once the user reviews and agrees to the plan, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[0825] This will enable the proposal and application of highly accurate contract plans that take user emotions into consideration, and is expected to improve user satisfaction.

[0826] Examples of prompt statements to input into a generative AI model include the following:

[0827] "Please enter the questions users will use to choose a new data plan."

[0828] "Please generate an error message to display when login fails."

[0829] "Please use the emotion recognition engine to analyze the user's emotional state and input the results."

[0830] The flow of the specific processing in Example 2 will be explained using Figure 13.

[0831] Step 1: User Authentication Process

[0832] The user enters their authentication information (user ID and password) into the terminal. The input data consists of the user ID and password.

[0833] The terminal sends the entered authentication information to the server. The input data is the user ID and password, and the output is the authentication information sent to the server.

[0834] The server compares the received authentication information with the database to determine whether the login is successful or not. The input data consists of the user ID and password; the corresponding information is retrieved from the database and compared with the authentication information. The output is either a successful or unsuccessful login.

[0835] If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The output is either the personal profile or the error message.

[0836] The device will either display an error message or, if the login was successful, display the user's personal profile. The output will be either an error message or the user's personal profile.

[0837] Step 2: Request gathering process

[0838] The terminal displays an interactive interface to users who have successfully logged in. It presents the question, "Are you satisfied with the service you are currently using?". The input data is a successful login, and the output is the display of the question.

[0839] The user enters an answer to a question (e.g., "Insufficient data"). The output is the user's answer.

[0840] The terminal receives the user's response and displays the next question, "How much data do you need?". The input data is the user's response, and the output is the display of the next question.

[0841] The user answers the following question (e.g., "I want 20GB per month"). The output is the user's response.

[0842] The terminal temporarily stores the response and sends it to the server. The input data is the user's response, and the output is the data sent to the server.

[0843] The server records the user's responses in a hearing database. The input data is the user's responses, and the output is the recording in the database.

[0844] Step 3: Emotion Recognition Processing

[0845] The device activates an emotion engine to analyze the user's responses and facial expressions. The input data consists of the user's responses and facial expressions, and the output is the analysis result.

[0846] The server uses an emotion engine to analyze the user's emotional state and generate emotion data. The input data consists of the user's responses and facial expression data, and the output is emotion data.

[0847] The server adjusts the content and tone of the next question based on the emotional state and sends it to the terminal. The input data is emotional data and its analysis results, and the output is the adjusted question content.

[0848] The terminal displays the adjusted question and waits for the user's response. The output is the display of the adjusted question.

[0849] Step 4: Plan Proposal Processing

[0850] The server executes an algorithm that selects the optimal contract plan using user interview data and sentiment data. The input data is interview data and sentiment data, and the output is the optimal plan.

[0851] The server also refers to usage history and feedback from other users. The input data is usage history and feedback, and the output is the optimized calculation result of the algorithm.

[0852] The server sends the optimal plan to the terminal. The input data is the optimal plan, and the output is the data sent to the terminal.

[0853] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen"). The output is the display of the plan.

[0854] The user reviews the proposed plan and enters any additional questions or requested changes as needed (e.g., "Is there a plan with unlimited data usage?"). The output consists of these additional questions and requested changes.

[0855] The server receives additional questions and requested changes and runs an algorithm to recalculate the optimal plan. The input data is the additional questions and requested changes, and the output is the recalculated optimal plan.

[0856] The device displays the new plan to the user. The output is a display of the new plan.

[0857] Step 5: System Integration Process

[0858] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The output is the display of the Subscription Application button.

[0859] The user clicks the contract application button. The output indicates their intention to apply for the contract.

[0860] The server receives contract application information and interacts with the backend contract management system. The input data is the contract application information, and the output is the data to be sent to the contract management system.

[0861] The server registers contract information in the contract management database. The input data is the contract information, and the output is the data registered in the database.

[0862] Step 6: Order completion notification processing

[0863] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input data is the contract completion information, and the output is the completion notification.

[0864] The server sends completion details to the terminal. The input data is contract completion information, and the output is the data sent to the terminal.

[0865] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The output is a display of the completion screen.

[0866] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The output consists of a confirmation of the notification and instructions for the next steps.

[0867] (Application Example 2)

[0868] Next, we will explain application example 2. In the following explanation, the data processing device 12 will be referred to as the "server," and the smart glasses 214 will be referred to as the "terminal."

[0869] Traditional e-commerce sites relied primarily on past purchase and search history to determine user preferences. However, this approach failed to consider user emotional states, making it difficult to recommend optimal products. Furthermore, the systems for enabling users to select products and complete purchases smoothly and without stress were inadequate. As a result, improving user satisfaction proved challenging.

[0870] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means.

[0871] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recognizing the user's emotional state based on an image of the user; means for recording the answers and emotional state in a database; means for executing an algorithm to select the optimal product based on the recorded data and emotional data; means for displaying the selected product to the user and accepting the purchase application; means for linking the purchase application information with a backend contract management system and processing the purchase application; and means for sending a completion notification to the user when the purchase is completed. This enables optimal product suggestions that also take into account the user's emotional state and a smooth purchase procedure.

[0872] "User authentication" is the process of verifying whether a user has legitimate access rights based on the authentication information they provide.

[0873] An "interactive interface" is an interface that allows the user and the system to communicate in both directions.

[0874] "Emotion recognition" is a technology that analyzes a user's emotional state based on their images, voice, and text.

[0875] A "database" is a data management system that organizes and stores large amounts of data, making it possible to retrieve it quickly as needed.

[0876] An "algorithm" is a set of specific steps or procedures for solving a particular problem.

[0877] A "contract management system" is a system that centrally manages users' contract information and efficiently processes contracts.

[0878] A "purchase request" is the process by which a user expresses their intention to purchase a selected product and requests that the product be purchased.

[0879] A "completion notice" is a notification that informs that a particular process or procedure has been successfully completed.

[0880] This invention relates to a system that provides product suggestions and facilitates purchases while taking into account the user's emotional state. The system aims to enable users to access e-commerce sites using their smartphones, receive optimal product suggestions through an interactive interface, and complete the purchase process smoothly.

[0881] User Authentication

[0882] When a user enters their authentication information (user ID and password) into the app, the device sends it to the server. The server compares it with the database to determine whether the login is successful. If the login is successful, the server sends the user's personal profile back to the device, and user authentication is complete.

[0883] Interactive interface

[0884] After logging in, the device displays an interactive interface. The first question displayed is, "What kind of products have you been interested in lately?" When the user enters an answer, that answer is sent to the server and the next question is generated. For example, if the user answers "fashion items," the next question displayed will be, "Specifically, what kind of items are you looking for?"

[0885] emotion recognition

[0886] The user's responses, along with image data captured by the device's camera, are sent to the server. The server uses an emotion recognition engine to analyze the user's emotional state. This emotion recognition engine works in conjunction with image processing software such as OpenCV and generates emotion data using a generative AI model.

[0887] Database records

[0888] User responses and emotional data are stored in temporary memory and then recorded in a hearing database. This allows for the accumulation of data that reflects the user's preferences and emotional state.

[0889] Product suggestion

[0890] The server executes an algorithm to suggest the optimal product based on accumulated hearing and sentiment data. This algorithm selects products to suggest, taking into account the user's past purchase history and feedback from other users. The specific product and price are then displayed on the terminal in the format of "This is the perfect fashion item for you."

[0891] Purchase application and completion notification

[0892] When a user agrees to a suggested product and submits a purchase request, the device sends that information to the server. The server then integrates with the backend contract management system to automatically complete the purchase process. Once the purchase is complete, the server sends a completion notification to the user's registered email address or via SMS, and a purchase completion screen is also displayed on the device.

[0893] Specific example

[0894] 1. Example of a prompt:

[0895] Authentication information entry: "Please enter your User ID and password."

[0896] Emotion recognition: "Please take a picture of your face with the camera."

[0897] Suggestions based on purchase history: "Based on your past purchase history and sentiment data, we suggest the following products."

[0898] For example, a user opens the app, enters their ID and password, and logs in. Then, they take a picture of their face with their smartphone camera, and an emotion recognition engine analyzes their emotions. Based on past history and emotion data, the server suggests the most suitable products. The user reviews the suggested products and decides to purchase them.

[0899] This invention enables optimal product recommendations that take into account the user's emotional state and facilitates a smooth purchasing process. This is expected to improve user satisfaction.

[0900] The flow of a specific process in Application Example 2 will be explained using Figure 14.

[0901] Step 1: User Authentication

[0902] The user enters their ID and password into their smartphone. The device sends this authentication information to the server. The server compares it with the user information in the database to determine whether login is permitted. If the login is successful, the server sends the user's personal profile back to the device. The input is the user's authentication information, and the output is the personal profile upon successful login or an error message upon failure.

[0903] Step 2: Display the interactive interface

[0904] When the terminal receives a signal indicating successful login, it displays an interactive interface. The user is presented with the initial question, "What products have you been interested in recently?" Once the user enters their answer, it is sent to the server. The input is the user's response to the question, and the output is the content of the next question.

[0905] Step 3: Emotion Recognition Processing

[0906] When a user answers a question, the device's camera captures a picture of the user's face. The captured image data is sent to a server, where the server's emotion recognition engine analyzes the image. A generative AI model is used to analyze the user's emotions and generate emotion data. The input is the user's face image, and the output is the analyzed emotion data.

[0907] Step 4: Recording responses and emotional data

[0908] The server stores user responses and sentiment data in temporary storage and then records them in the hearing database. This allows data to accumulate. The input is the user's responses and sentiment data, and the output is the data stored in the hearing database.

[0909] Step 5: Run the product suggestion algorithm.

[0910] The server executes a product recommendation algorithm based on data and sentiment data recorded in the hearing database. This algorithm selects the most suitable products by referring to the user's past purchase history, usage history, and feedback from other users. The input is accumulated data and sentiment data, and the output is a list of selected products.

[0911] Step 6: Display the optimal product

[0912] The terminal displays a list of optimal products received from the server to the user. For example, it might show specific products and their prices in a format like, "These are the perfect fashion items for you." The input is a list of products selected by the server, and the output is detailed product information displayed to the user.

[0913] Step 7: Purchase Application

[0914] When a user agrees to a suggested product and submits a purchase request, the terminal sends that information to the server. The server then integrates with the backend contract management system to automatically complete the purchase process. The input is the user's purchase request information, and the output is the information linked to the contract management system.

[0915] Step 8: Purchase Completion Notification

[0916] Once the purchase is complete, the server sends a completion notification to the user's registered email address or via SMS, and also displays a purchase completion screen on the device. The user confirms that the purchase is complete and receives instructions on the next steps. The input is the purchase completion information, and the output is the completion notification and the completion screen displayed on the device.

[0917] 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 user input for the result of the specific processing. The control unit 46A transmits the audio data indicating user input acquired by the microphone 238 to the data processing unit 12. In the data processing unit 12, the specific processing unit 290 acquires the audio data.

[0918] Data generation model 58 is a type of so-called generative AI (Artificial Intelligence). One example of data generation model 58 is ChatGPT (Internet Search).<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search) <url: https: gemini.google.com ?hl="ja">Examples of generative AI include the following. The data generation model 58 is obtained by performing deep learning on a neural network. The data generation model 58 is input with prompts containing instructions, and with inference data such as audio data representing speech, text data representing text, and image data representing images. The data generation model 58 infers from the input inference data according to the instructions indicated by the prompts, and outputs the inference results in data formats such as audio data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0919] In the above embodiment, an example was given in which specific processing is performed by the data processing device 12, but the technology of this disclosure is not limited thereto, and the specific processing may also be performed by the smart glasses 214.

[0920] [Third Embodiment]

[0921] Figure 5 shows an example of the configuration of the data processing system 310 according to the third embodiment.

[0922] As shown in Figure 5, the data processing system 310 includes a data processing device 12 and a headset terminal 314. An example of the data processing device 12 is a server.

[0923] The data processing device 12 comprises a computer 22, a database 24, and a communication interface 26. The computer 22 is an example of a "computer" related to the technology of this disclosure. The computer 22 comprises a processor 28, RAM 30, and storage 32. The processor 28, RAM 30, and storage 32 are connected to a bus 34. The database 24 and the communication interface 26 are also connected to the bus 34. The communication interface 26 is connected to a network 54. An example of the network 54 is a WAN (Wide Area Network) and / or a LAN (Local Area Network).

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

[0925] The microphone 238 receives voice signals from the user 20 and receives instructions from the user 20. The microphone 238 captures the voice signals from the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio according to the instructions from the processor 46.

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

[0927] Communication interface 44 is connected to network 54. Communication interfaces 44 and 26 are responsible for the exchange of various information between processor 46 and processor 28 via network 54. The exchange of various information between processor 46 and processor 28 using communication interfaces 44 and 26 is performed in a secure manner.

[0928] Figure 6 shows an example of the main functions of the data processing device 12 and the headset terminal 314. As shown in Figure 6, the data processing device 12 performs specific processing using the processor 28. The storage 32 stores the specific processing program 56.

[0929] The specific processing program 56 is an example of a "program" relating to the technology of this 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.

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

[0931] In the headset terminal 314, the processor 46 performs the reception output processing. The storage 50 stores the reception output program 60. 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 processing is realized by the processor 46 operating as a control unit 46A according to the reception output program 60 executed on the RAM 48.

[0932] Next, the specific processing performed by the specific processing unit 290 of the data processing device 12 will be described. In the following description, the data processing device 12 will be referred to as the "server" and the headset terminal 314 will be referred to as the "terminal".

[0933] This invention relates to a system that allows users to easily and efficiently propose and apply for contract plans. This system logs in based on the user's authentication information, listens to the user's requests and preferences through an interactive interface, and proposes the most suitable contract plan based on that information. Furthermore, it can automatically process the contract application and finally sends a contract completion notification to the user.

[0934] Program processing

[0935] User authentication process

[0936] User: The user enters their authentication information (user ID and password) into the terminal.

[0937] Terminal: The terminal sends the entered authentication information to the server.

[0938] Server: The server compares the received authentication information with the database and determines whether login is permitted. If successful, it returns the user's personal profile to the terminal. If unsuccessful, it returns an error message.

[0939] Device: The device will either display an error message or, if successful, display the user's personal profile.

[0940] Request gathering process

[0941] Terminal: Displays an interactive interface to users who have successfully logged in. It displays initial questions such as, "Are you satisfied with the service you are currently using?"

[0942] User: The user answers the question (e.g., "Insufficient data").

[0943] Terminal: The terminal receives the response and generates and displays the next question (e.g., "How much data do you want?").

[0944] User: The user also answers the following question (e.g., "I would like 20GB per month").

[0945] Terminal: Temporarily saves the answer and sends it to the server.

[0946] Server: Records user responses in the hearing database.

[0947] Plan proposal processing

[0948] Server: Executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users.

[0949] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0950] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0951] Server: We will receive any additional questions or requested changes and recalculate the optimal plan.

[0952] Device: Display the new plan to the user.

[0953] System Integration Processing

[0954] Device: After the user agrees to the proposed plan, a button will be displayed to proceed with the "Subscription Application".

[0955] User: The user clicks the contract application button.

[0956] Server: Receives contract application information and integrates with the backend contract management system. Registers contract information in the contract management database.

[0957] Order completion notification processing

[0958] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or SMS. Sends completion details to the device.

[0959] Terminal: Displays a screen indicating that the order has been completed and provides the user with detailed information such as contract details and service start date.

[0960] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[0961] Specific example

[0962] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, the server verifies it against the database, and the login process is initiated. If the login is successful, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server calculates the optimal plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[0963] In this way, the present invention makes it possible to accurately understand user needs and propose and accept efficient and user-friendly contract plans.

[0964] The following describes the processing flow.

[0965] Step 1:

[0966] User: The user enters their authentication information (user ID and password) into the terminal.

[0967] Step 2:

[0968] Terminal: The terminal sends the entered authentication information to the server.

[0969] Step 3:

[0970] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[0971] Step 4:

[0972] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[0973] Step 5:

[0974] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[0975] Step 6:

[0976] Terminal: Displays an interactive interface and presents the user with the question, "Are you satisfied with the service you are currently using?"

[0977] Step 7:

[0978] User: The user enters an answer to the question (e.g., "Insufficient data").

[0979] Step 8:

[0980] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[0981] Step 9:

[0982] User: The user answers the following question (e.g., "I would like 20GB per month").

[0983] Step 10:

[0984] Terminal: The terminal temporarily stores the answer and sends it to the server.

[0985] Step 11:

[0986] Server: The server records the user's responses in the hearing database.

[0987] Step 12:

[0988] Server: The server analyzes the recorded interview data and runs an algorithm to select the optimal contract plan.

[0989] Step 13:

[0990] Server: Sends the selected optimal contract plan to the terminal.

[0991] Step 14:

[0992] Device: The device displays the proposed contract plan to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[0993] Step 15:

[0994] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[0995] Step 16:

[0996] Terminal: Sends additional questions or requested changes from the user to the server.

[0997] Step 17:

[0998] Server: Receives additional questions or requested changes and runs an algorithm to recalculate the optimal plan.

[0999] Step 18:

[1000] Server: Sends the new contract plan to the device.

[1001] Step 19:

[1002] Device: Display new contract plans to the user.

[1003] Step 20:

[1004] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[1005] Step 21:

[1006] Terminal: Sends contract application information to the server.

[1007] Step 22:

[1008] Server: Receives contract application information and integrates with the backend contract management system.

[1009] Step 23:

[1010] Server: Registers contract information in the contract management database.

[1011] Step 24:

[1012] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[1013] Step 25:

[1014] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[1015] Step 26:

[1016] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[1017] (Example 1)

[1018] Next, we will describe Example 1. 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."

[1019] Conventional contract plan proposal systems failed to adequately reflect user needs and preferences, making it difficult to provide users with the most suitable contract plan quickly and efficiently. In particular, a challenge was the inability to recalculate the plan when users had additional questions or requested changes to the presented plan, resulting in a degraded user experience.

[1020] The identification process performed by the identification processing unit 290 of the data processing device 12 in Example 1 is realized by the following means.

[1021] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recording the answers in a database; means for executing an algorithm to select the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; and means for receiving additional questions or change requests from the user, and recalculating and displaying the optimal contract plan again. This makes it possible to accurately grasp the user's needs and desires, propose the optimal contract plan, and quickly make revised proposals.

[1022] "Authentication information" refers to the information a user needs to log in to a system, and typically consists of a user ID and password.

[1023] A "database" is an organized collection of data, a system for retrieving, storing, and updating information.

[1024] An "interactive interface" is a user interface that allows the user and the system to communicate in both directions.

[1025] "Means for generating questions and answers" refers to a function that creates appropriate questions based on user input and collects user responses to those questions.

[1026] An "algorithm" is a set of procedures or computational methods for solving a specific problem.

[1027] A "contract plan" refers to the terms and conditions of the agreement for a user to use the service.

[1028] "Application information" refers to the necessary data that a user provides when they wish to enter into a contract.

[1029] A "backend contract management system" is a system used for managing and updating contract details.

[1030] A "completion notification" is a notification sent to inform a user that a transaction or procedure has been successfully completed.

[1031] "Additional questions or requested changes" refers to any further information the user would like to know or any changes they would like to make regarding the proposed plan.

[1032] This invention relates to a system for users to easily and efficiently propose and apply for contract plans. This system includes the following processes: user authentication, requirements gathering, plan proposal, system integration, and order completion notification.

[1033] Hardware and software to be used

[1034] The system's hardware includes a server, terminals (e.g., tablet devices), and a database. The server is responsible for processes such as verifying authentication information, executing plan proposal algorithms, and sending notifications. The software used includes a MySQL or PostgreSQL database, algorithms implemented in Python, and a mail server (e.g., SendGrid). Terminals handle the display of the user interface, input of user data, and communication with the server, using a standard web browser or interactive interface software.

[1035] Processing details

[1036] The server first receives the authentication information (user ID and password) entered by the user and compares it with the database. If authentication is successful, the user's personal profile is returned and displayed on the terminal. Next, the terminal displays an interactive interface to hear the user's requests and preferences. A question-and-answer exchange takes place, and this information is sent to the server and recorded in the database.

[1037] The server uses machine learning models and other tools to calculate and select the optimal contract plan based on recorded data. This calculation takes into account the user's usage history and feedback from other users. The selected plan is displayed on the terminal, and the user reviews the proposal and enters additional questions or requests for changes via the terminal as needed. The server receives this new information, recalculates the plan, and displays the result on the terminal.

[1038] If the user agrees to the proposed plan, the device displays a contract application button, and when the user clicks it, the contract application information is sent to the server. The server then integrates this information with the backend contract management system to finalize the contract. Once the contract is complete, the server sends a completion notification to the user's registered email address or via SMS, and the device also displays confirmation of the order completion.

[1039] Specific example

[1040] For example, if a user wishes to change their plan using a tablet terminal installed at a train station's ticket gate, they can follow these steps: The user enters their authentication information into the terminal, the server verifies it against a database, and the login process is initiated. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server uses a machine learning model implemented in Python to calculate the optimal contract plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal. In this way, the present invention enables accurate understanding of user needs and allows for the proposal and application of efficient and user-friendly contract plans.

[1041] Example of a prompt

[1042] "Please describe the system's processing flow for users to change their plan at terminals installed at train station ticket gates. Please include the specific names of the hardware and software used at each step, from user authentication to contract completion notification."

[1043] The flow of the specific processing in Example 1 will be explained using Figure 11.

[1044] Step 1:

[1045] The user enters their authentication information (user ID and password) into the terminal. This input is done using a text field. The input data consists of the user ID and password.

[1046] Step 2:

[1047] The terminal encrypts the entered authentication information and sends it to the server. Specifically, it encrypts and transmits the data using the SSL / TLS protocol. The input is the encrypted authentication information, and the output is the request to the server.

[1048] Step 3:

[1049] The server compares the received authentication information with the database. The database stores the user ID and the hashed password. The server retrieves the password hash corresponding to the user ID from the database and compares it with the input password. The input is encrypted authentication information, and the output is the authentication result (success / failure).

[1050] Step 4:

[1051] The server returns the user's personal profile to the terminal if authentication is successful, and an error message if it fails. The input is the authentication result, and the output is either the personal profile or the error message.

[1052] Step 5:

[1053] The device receives the authentication result and, if the login is successful, displays the user's personal profile; if it fails, it displays an error message. The input is the personal profile or the error message, and the output is the screen display.

[1054] Step 6:

[1055] The terminal displays an interactive interface to users who have successfully logged in, and shows the initial question, "Are you satisfied with the services you are currently using?". The input is the user's personal profile, and the output is the screen display of the question.

[1056] Step 7:

[1057] The user answers a question (e.g., "Insufficient data"). User input is provided through an interactive interface. Input is the user's answer to the question, and output is the transmission of the answer to the terminal.

[1058] Step 8:

[1059] The terminal receives the user's response and generates and displays the next question, "How much data do you need?". The input is the user's initial response, and the output is the screen display for the next question. The terminal temporarily stores this data.

[1060] Step 9:

[1061] The user also answers the following question (e.g., "I want 20GB per month"). This input is done through an interactive interface. The input is the user's answer to the following question, and the output is the transmission of the answer to the terminal.

[1062] Step 10:

[1063] The terminal temporarily stores the response and sends it to the server. The input is the user's response, and the output is the data sent to the server.

[1064] Step 11:

[1065] The server records user responses in a hearing database. The input is the user's response data, and the output is saving it to the database.

[1066] Step 12:

[1067] The server executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users. The inputs are interview data, usage history data, and feedback data, and the output is the optimal contract plan.

[1068] Step 13:

[1069] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is available for XXX yen"). The input is the proposed plan data, and the output is the screen display.

[1070] Step 14:

[1071] The user reviews the proposed plan and enters additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?"). This input is done through an interactive interface. The input consists of additional questions or requests for changes, and the output is the response sent to the device.

[1072] Step 15:

[1073] The server receives additional questions and requested changes and recalculates the optimal plan. The input is the data for the additional questions and requested changes, and the output is the recalculated contract plan.

[1074] Step 16:

[1075] The device displays the new plan to the user. The input is the recalculated contract plan data, and the output is the screen display.

[1076] Step 17:

[1077] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The input is the user's agreement, and the output is the display of the subscription application button.

[1078] Step 18:

[1079] The user clicks the contract application button. The input is the click of the contract application button, and the output is the submission of contract information.

[1080] Step 19:

[1081] The server receives contract application information and interacts with the backend contract management system. The input is the contract application information, and the output is the transmission of data to the contract management system.

[1082] Step 20:

[1083] The server registers contract information in the contract management database. The input is contract application information, and the output is saving it to the database.

[1084] Step 21:

[1085] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input is the contract completion information, and the output is the sending of the completion notification.

[1086] Step 22:

[1087] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The input is the contract completion information, and the output is the screen display.

[1088] Step 23:

[1089] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The input is the completion notification, and the output is the confirmation and instructions for the next steps.

[1090] (Application Example 1)

[1091] Next, we will explain Application Example 1. In the following explanation, 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."

[1092] In recent years, with the advancement of e-commerce, users need to select the optimal purchase plan and products from a vast amount of product information, thus requiring a more efficient purchasing experience and personalized suggestions. Conventional systems struggle to fully meet user needs, and in particular, they lack the means to propose the most suitable products in an interactive format and to facilitate a smooth purchasing process. Therefore, to improve user satisfaction, a system is needed that uses an interactive interface to quickly and accurately understand user requests and provide optimal product suggestions and purchasing procedures.

[1093] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 1 is realized by the following means.

[1094] In this invention, the server includes means for matching user authentication information with a database and determining whether or not login is permitted; means for generating questions and answers through an interactive interface based on user input information; means for recording the answers in a database; means for executing an algorithm for selecting the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; means for selecting the optimal purchase plan by referring to usage history and feedback from other users; and means for displaying product suggestions to the user based on the purchase plan and accepting the purchase procedure. This enables the user to efficiently select the optimal product from a large amount of product information and smoothly complete the purchase procedure.

[1095] "User authentication" is a series of processes that compare the authentication information a user provides to log in to a system with a database and determine whether or not they are allowed to log in.

[1096] An "interactive interface" is an interface used to facilitate smooth interaction with users, and it is a mechanism that dynamically generates questions and answers based on user input.

[1097] "Authentication information" refers to information such as user ID and password that a user uses when logging into a system.

[1098] A "database" is an electronic information recording system used to store and manage user information, interview data, contract details, and other similar information.

[1099] An "algorithm" is a set of procedures or calculation methods for achieving a specific objective, and in this system, it is a means of selecting the optimal contract or purchase plan.

[1100] A "backend system" is a system that manages and processes contract and purchase information, separate from the frontend system that interacts directly with users.

[1101] A "contract plan" refers to the specific details of the services or products offered to the user, along with their pricing.

[1102] A "purchase plan" is a plan that proposes the optimal combination of products to be obtained by purchasing them all at once or as a set, based on the user's needs.

[1103] A "completion notification" is a notification sent to the user informing them that the contract or purchase procedure has been successfully completed, and is sent via email, SMS, or other means.

[1104] "Usage history" refers to records of operations, selections, and purchases that a user has made through the system in the past.

[1105] "Feedback" refers to opinions and evaluations provided by users and other users, which are used in selecting plans and proposing products within this system.

[1106] The system for implementing this invention is designed to provide users with efficient and personalized proposals and procedures for contract and purchase plans. The system supports a series of processes in which the user easily authenticates, inputs their needs through an interactive interface, is proposed the most suitable plan, and completes the purchase or contract procedure.

[1107] The system configuration is as follows:

[1108] Hardware and software to use

[1109] Hardware: Smartphone

[1110] Software: Mobile app (iOS and Android), server-side uses AWS (Amazon Web Services).

[1111] Database: MySQL or PostgreSQL

[1112] Generative AI model: GPT-4 (OpenAI)

[1113] User authentication process

[1114] The user launches the smartphone app and enters their ID and password. The app sends this information to the server, which verifies the authentication information against a database. If authentication is successful, the user's personal profile is displayed in the app.

[1115] Request gathering process

[1116] After successful login, the app displays an interactive interface. For example, the first question displayed might be, "Are you satisfied with your recent purchase?" The user answers this question (e.g., "I want a more portable product"), and the app generates and displays the next question. By repeating this process, the app collects the user's requests and sends them to the server. The server records this data in a hearing database.

[1117] Plan proposal processing

[1118] The server uses recorded user responses to run an algorithm to select the optimal contract or purchase plan. Usage history and feedback from other users are also referenced. The calculated plan is presented to the user through the app.

[1119] System Integration Processing

[1120] Once a user agrees to a proposed plan, they can tap a button within the app to complete the contract application or purchase process. The server receives this information, processes it in conjunction with the backend contract management system and order management system, and registers the contract or purchase information in the relevant database.

[1121] Order completion notification processing

[1122] When a contract or purchase is completed, the server sends a completion notification to the user. This notification is sent to the registered email address or via SMS. A completion screen is also displayed in the app, allowing the user to confirm the contract details and purchase information.

[1123] Specific example

[1124] For example, if a user logs into a smartphone app and, in the interactive interface, indicates they are looking for "cooking utensils that are easy to use at a campsite they recently visited," the system will suggest a "lightweight and easy-to-pack camping cooking set," and will also display current discount information and related products. Once the user reviews the suggestion, agrees, and taps to purchase, the order is immediately completed, and an order confirmation notification is sent to their smartphone.

[1125] Example of a prompt

[1126] "I'm looking for easy-to-use cooking utensils at a campsite I recently visited."

[1127] "What type of cooking utensils do you prefer? (e.g., lightweight, portable, set, etc.)"

[1128] "Something lightweight and easy to package."

[1129] "Our recommended product is a lightweight and easy-to-pack camping cooking set. It's currently 30% off. Would you like to purchase it?"

[1130] "yes"

[1131] "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[1132] By implementing this system, we can accurately grasp user needs and achieve efficient, personalized contract and purchasing processes.

[1133] The flow of a specific process in Application Example 1 will be explained using Figure 12.

[1134] Step 1: User Authentication Process

[1135] The user launches the smartphone app and enters their ID and password on the authentication screen. The user ID and password are provided as input.

[1136] The terminal sends the entered authentication information to the server. At this time, the user ID and password are sent to the server as data packets.

[1137] The server compares the received authentication information with the database to determine whether or not the login is permitted. This process involves comparing the user information stored in the database with the entered authentication information.

[1138] The server returns the user's personal profile to the device if authentication is successful, and an error message if it fails. The output upon successful authentication is the user's profile information, while the output upon failure is an error message.

[1139] Based on the received data, the device will display the personal profile screen if successful, or an error message if unsuccessful.

[1140] Step 2: Request gathering process

[1141] The terminal displays an interactive interface to users who have successfully logged in. The system's initial question is, "Are you satisfied with your recent purchases?" The user is then provided with further questions as input.

[1142] The user enters an answer to this question (e.g., "I want a product that is easier to carry"). That answer is then sent to the device.

[1143] The device temporarily stores the user's response and generates and displays the next question (e.g., "What type of product do you prefer?"). The generated question is created by an AI model based on the user's response.

[1144] The server receives response data sent from the terminal and records it in the hearing database. User response data is provided as input, and recorded in the hearing database as output.

[1145] Step 3: Plan Proposal Processing

[1146] The server executes an algorithm to select the optimal contract plan based on recorded user interview data. This algorithm also utilizes usage history and feedback from other users stored in the database. The input to this process is user interview data and usage history, and the output is the selected contract plan.

[1147] The server sends the selected plan to the terminal, and the terminal displays the plan to the user (e.g., "Lightweight and easy-to-pack camping cooking set available at 30% off"). The sent plan is displayed as output.

[1148] Step 4: System Integration Process

[1149] If the user agrees to the proposed plan, they tap the purchase button displayed on their device. The user's consent action is provided as input.

[1150] The server receives the operation information and processes the contract application in cooperation with the backend contract management system. This cooperation process includes registering the user's purchase information in the contract management system. As output, the contract application information is registered in the system.

[1151] The server registers the purchase completion information in the contract management database. Purchase completion data is provided as input.

[1152] Step 5: Order completion notification processing

[1153] The server sends a completion notification to the user's registered email address or via SMS when a contract or purchase is completed. Completion notification data is provided as input, and the completion notification is sent to the user as output.

[1154] The device displays a completion screen to the user, providing contract details and purchase information. The output is the completion screen.

[1155] The user can then confirm the completion notification and proceed to the next step. Specifically, it might display something like, "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[1156] This series of processes allows users to efficiently and personalizedly enter into service contracts and purchase products.

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

[1158] This invention relates to a system that proposes and accepts contract plans while also considering the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[1159] Program processing

[1160] User authentication process

[1161] User: The user enters their authentication information (user ID and password) into the terminal.

[1162] Terminal: The terminal sends the entered authentication information to the server.

[1163] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[1164] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[1165] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[1166] Request gathering process

[1167] Terminal: Displays an interactive interface to users who have successfully logged in. The initial question is, "Are you satisfied with the service you are currently using?"

[1168] User: The user enters an answer to the question (e.g., "Insufficient data").

[1169] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[1170] User: The user answers the following question (e.g., "I would like 20GB per month").

[1171] Terminal: Temporarily saves the answer and sends it to the server.

[1172] Server: Records user responses in the hearing database.

[1173] Emotion recognition processing

[1174] Terminal: Activates an emotion engine to recognize emotions from the user's responses and facial expressions.

[1175] Server: The emotion engine analyzes the user's emotional state and generates emotion data.

[1176] Server: Based on the emotional state, adjust the content and tone of the next question and send it to the terminal.

[1177] Terminal: Displays the adjusted questions and waits for the user's response.

[1178] Plan proposal processing

[1179] Server: Executes an algorithm to select the optimal contract plan based on user interview data and sentiment data. It also refers to usage history and feedback from other users.

[1180] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[1181] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[1182] Server: Receives additional questions or requested changes and runs an algorithm to recalculate the optimal plan.

[1183] Device: Display the new plan to the user.

[1184] System Integration Processing

[1185] Device: After the user agrees to the proposed plan, a button will be displayed to proceed with the "Subscription Application".

[1186] User: The user clicks the contract application button.

[1187] Server: Receives contract application information and integrates with the backend contract management system.

[1188] Server: Registers contract information in the contract management database.

[1189] Order completion notification processing

[1190] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or SMS. Sends completion details to the device.

[1191] Terminal: Displays a screen indicating that the order has been completed and provides the user with detailed information such as contract details and service start date.

[1192] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[1193] Specific example

[1194] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, which the server then compares with the database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the emotion engine is activated and analyzes the user's emotional state. The server analyzes the emotional data along with the interview data to calculate the optimal plan and displays it on the terminal. The user reviews this plan, and if they agree, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[1195] In this way, the present invention makes it possible to propose and accept highly accurate contract plans that take into account the user's emotions, and is expected to improve user satisfaction.

[1196] The following describes the processing flow.

[1197] Step 1:

[1198] User: The user enters their authentication information (user ID and password) into the terminal.

[1199] Step 2:

[1200] Terminal: The terminal sends the entered authentication information to the server.

[1201] Step 3:

[1202] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[1203] Step 4:

[1204] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[1205] Step 5:

[1206] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[1207] Step 6:

[1208] Terminal: Displays an interactive interface and presents the user with the initial question, "Are you satisfied with the service you are currently using?"

[1209] Step 7:

[1210] User: The user enters an answer to the question (e.g., "Insufficient data").

[1211] Step 8:

[1212] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[1213] Step 9:

[1214] User: The user answers the following question (e.g., "I would like 20GB per month").

[1215] Step 10:

[1216] Terminal: The terminal temporarily stores the answer and sends it to the server.

[1217] Step 11:

[1218] Server: The server records the user's responses in the hearing database.

[1219] Step 12:

[1220] Terminal: The terminal activates the emotion engine and captures the user's responses and facial expressions.

[1221] Step 13:

[1222] Server: The emotion engine analyzes the captured information and recognizes the user's emotional state.

[1223] Step 14:

[1224] Server: The server processes the recognized emotion data and adjusts the content and tone of the next question.

[1225] Step 15:

[1226] Terminal: Displays a prepared question to the user and waits for the user's response.

[1227] Step 16:

[1228] User: The user answers a pre-set question (e.g., "I'm also considering an unlimited plan").

[1229] Step 17:

[1230] Terminal: Sends additional responses from the user to the server.

[1231] Step 18:

[1232] Server: The server runs an algorithm to select the optimal contract plan again based on the additional responses and sentiment data.

[1233] Step 19:

[1234] Server: Sends the selected optimal contract plan to the terminal.

[1235] Step 20:

[1236] Device: Display new contract plans to the user (e.g., "The plan with 20GB of data per month is XXX yen, and the unlimited plan is YYY yen").

[1237] Step 21:

[1238] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[1239] Step 22:

[1240] Terminal: Sends contract application information to the server.

[1241] Step 23:

[1242] Server: Receives contract application information and integrates with the backend contract management system.

[1243] Step 24:

[1244] Server: Registers contract information in the contract management database.

[1245] Step 25:

[1246] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[1247] Step 26:

[1248] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[1249] Step 27:

[1250] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[1251] (Example 2)

[1252] Next, we will describe Example 2. 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."

[1253] Conventional contract plan proposal systems were limited to basic functions such as login using user authentication information, question generation, and answer recording. However, because they presented questions and plans in a fixed manner without considering the user's emotional state, user satisfaction was low, and improving the contract rate was difficult. Furthermore, they did not cover plan selection using feedback from other users, so optimal proposals were not adequately made.

[1254] The identification processing performed by the identification processing unit 290 of the data processing device 12 in Example 2 is realized by the following means. In this invention, the server includes means for determining whether or not login is permitted by comparing the authentication information entered by the user with the database; means for recognizing emotions based on the user's input information and facial expressions; means for generating and adjusting the next question based on the emotion recognition result; means for recording the answer in the database; means for executing an algorithm that selects the optimal contract plan based on the recorded data and other user information; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with the backend contract management system and processing the contract application; and means for sending a completion notification to the user when the contract is completed. This makes it possible to generate questions and propose plans that take into account the user's emotional state, thereby improving the contract rate and user satisfaction.

[1255] "Authentication information" refers to the information a user enters to identify themselves, specifically their user ID and password.

[1256] A "database" is a system for storing data in an organized and structured manner, and for searching and updating it as needed.

[1257] An "interactive interface" is an interface that allows users to communicate with a system in a two-way manner, and refers to a format where users input answers in response to questions.

[1258] "Means of recognizing emotions" refers to technologies that analyze a user's facial expressions, voice, and text to identify their emotional state.

[1259] An "algorithm" refers to a set of procedures or calculation methods defined to solve a specific problem.

[1260] A "contract plan" refers to a summary of the services and conditions that a user can subscribe to.

[1261] A "backend contract management system" refers to a core system used for managing and processing contract information.

[1262] A "completion notification" refers to a means of communication used to inform the user that a contract has been successfully completed.

[1263] "Usage history" refers to a record of services that a user has used in the past.

[1264] "Feedback" refers to information about opinions and reputations obtained from users.

[1265] "Emotion recognition results" refer to data on the user's emotional state obtained through means of recognizing emotions.

[1266] This invention relates to a system that proposes and accepts contract plans while taking into account the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[1267] As an embodiment of this system, the user authentication process will be described first. The user enters authentication information (user ID and password). The terminal sends the entered authentication information to the server. The server compares the received authentication information with the database and determines whether login is permitted. This database stores the user's authentication information. If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The terminal displays the error message, or displays the personal profile if the login is successful.

[1268] Next, we will explain the request gathering process. The terminal displays an interactive interface to users who have successfully logged in. The first question presented is, "Are you satisfied with the service you are currently using?" The user enters an answer to the question (e.g., "I don't have enough data"). The terminal receives the user's answer and displays the next question, "How much data do you need?" The user answers the next question (e.g., "I need 20GB per month"). The terminal temporarily saves the answer and sends it to the server. The server records the user's answer in the request database.

[1269] In emotion recognition processing, an emotion engine is activated to analyze the user's responses and facial expressions. The terminal uses this emotion engine to analyze the user's emotional state and generate emotion data. The server adjusts the content and tone of the next question based on this emotion data and sends it to the terminal. The terminal displays the adjusted question and waits for the user's response.

[1270] Furthermore, during the plan proposal process, the server executes an algorithm that uses user interview data and sentiment data to select the optimal contract plan. This algorithm also refers to the user's usage history and feedback from other users, and uses a machine learning model. The server sends the optimal plan to the terminal. The terminal displays the proposed plan received from the server to the user, who then reviews and agrees to the plan.

[1271] In the system integration process, after the user agrees to the proposed plan, the terminal displays a button to execute a "contract application." When the user clicks the contract application button, the server receives the contract application information and integrates with the backend contract management system. This registers the contract information in the contract management database.

[1272] During the order completion notification process, the server confirms that the contract has been completed and sends a completion notification to the user's registered email address or via SMS. The device also simultaneously displays a completion screen, providing the user with detailed information such as the contract details and the start date of service. The user confirms this notification and proceeds to the next step.

[1273] As a concrete example, consider a scenario where a user wishes to change their plan at a terminal installed at a train station's ticket gate. When the user enters their authentication information into the terminal, the server verifies it against a database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, an emotion engine is activated to analyze the user's emotional state. Based on this data, the server calculates the optimal plan and displays it on the terminal. Once the user reviews and agrees to the plan, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[1274] This will enable the proposal and application of highly accurate contract plans that take user emotions into consideration, and is expected to improve user satisfaction.

[1275] Examples of prompt statements to input into a generative AI model include the following:

[1276] "Please enter the questions users will use to choose a new data plan."

[1277] "Please generate an error message to display when login fails."

[1278] "Please use the emotion recognition engine to analyze the user's emotional state and input the results."

[1279] The flow of the specific processing in Example 2 will be explained using Figure 13.

[1280] Step 1: User Authentication Process

[1281] The user enters their authentication information (user ID and password) into the terminal. The input data consists of the user ID and password.

[1282] The terminal sends the entered authentication information to the server. The input data is the user ID and password, and the output is the authentication information sent to the server.

[1283] The server compares the received authentication information with the database to determine whether the login is successful or not. The input data consists of the user ID and password; the corresponding information is retrieved from the database and compared with the authentication information. The output is either a successful or unsuccessful login.

[1284] If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The output is either the personal profile or the error message.

[1285] The device will either display an error message or, if the login was successful, display the user's personal profile. The output will be either an error message or the user's personal profile.

[1286] Step 2: Request gathering process

[1287] The terminal displays an interactive interface to users who have successfully logged in. It presents the question, "Are you satisfied with the service you are currently using?". The input data is a successful login, and the output is the display of the question.

[1288] The user enters an answer to a question (e.g., "Insufficient data"). The output is the user's answer.

[1289] The terminal receives the user's response and displays the next question, "How much data do you need?". The input data is the user's response, and the output is the display of the next question.

[1290] The user answers the following question (e.g., "I want 20GB per month"). The output is the user's response.

[1291] The terminal temporarily stores the response and sends it to the server. The input data is the user's response, and the output is the data sent to the server.

[1292] The server records the user's responses in a hearing database. The input data is the user's responses, and the output is the recording in the database.

[1293] Step 3: Emotion Recognition Processing

[1294] The device activates an emotion engine to analyze the user's responses and facial expressions. The input data consists of the user's responses and facial expressions, and the output is the analysis result.

[1295] The server uses an emotion engine to analyze the user's emotional state and generate emotion data. The input data consists of the user's responses and facial expression data, and the output is emotion data.

[1296] The server adjusts the content and tone of the next question based on the emotional state and sends it to the terminal. The input data is emotional data and its analysis results, and the output is the adjusted question content.

[1297] The terminal displays the adjusted question and waits for the user's response. The output is the display of the adjusted question.

[1298] Step 4: Plan Proposal Processing

[1299] The server executes an algorithm that selects the optimal contract plan using user interview data and sentiment data. The input data is interview data and sentiment data, and the output is the optimal plan.

[1300] The server also refers to usage history and feedback from other users. The input data is usage history and feedback, and the output is the optimized calculation result of the algorithm.

[1301] The server sends the optimal plan to the terminal. The input data is the optimal plan, and the output is the data sent to the terminal.

[1302] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen"). The output is the display of the plan.

[1303] The user reviews the proposed plan and enters any additional questions or requested changes as needed (e.g., "Is there a plan with unlimited data usage?"). The output consists of these additional questions and requested changes.

[1304] The server receives additional questions and requested changes and runs an algorithm to recalculate the optimal plan. The input data is the additional questions and requested changes, and the output is the recalculated optimal plan.

[1305] The device displays the new plan to the user. The output is a display of the new plan.

[1306] Step 5: System Integration Process

[1307] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The output is the display of the Subscription Application button.

[1308] The user clicks the contract application button. The output indicates their intention to apply for the contract.

[1309] The server receives contract application information and interacts with the backend contract management system. The input data is the contract application information, and the output is the data to be sent to the contract management system.

[1310] The server registers contract information in the contract management database. The input data is the contract information, and the output is the data registered in the database.

[1311] Step 6: Order completion notification processing

[1312] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input data is the contract completion information, and the output is the completion notification.

[1313] The server sends completion details to the terminal. The input data is contract completion information, and the output is the data sent to the terminal.

[1314] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The output is a display of the completion screen.

[1315] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The output consists of a confirmation of the notification and instructions for the next steps.

[1316] (Application Example 2)

[1317] Next, we will explain application example 2. In the following explanation, 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."

[1318] Traditional e-commerce sites relied primarily on past purchase and search history to determine user preferences. However, this approach failed to consider user emotional states, making it difficult to recommend optimal products. Furthermore, the systems for enabling users to select products and complete purchases smoothly and without stress were inadequate. As a result, improving user satisfaction proved challenging.

[1319] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means.

[1320] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recognizing the user's emotional state based on an image of the user; means for recording the answers and emotional state in a database; means for executing an algorithm to select the optimal product based on the recorded data and emotional data; means for displaying the selected product to the user and accepting the purchase application; means for linking the purchase application information with a backend contract management system and processing the purchase application; and means for sending a completion notification to the user when the purchase is completed. This enables optimal product suggestions that also take into account the user's emotional state and a smooth purchase procedure.

[1321] "User authentication" is the process of verifying whether a user has legitimate access rights based on the authentication information they provide.

[1322] An "interactive interface" is an interface that allows the user and the system to communicate in both directions.

[1323] "Emotion recognition" is a technology that analyzes a user's emotional state based on their images, voice, and text.

[1324] A "database" is a data management system that organizes and stores large amounts of data, making it possible to retrieve it quickly as needed.

[1325] An "algorithm" is a set of specific steps or procedures for solving a particular problem.

[1326] A "contract management system" is a system that centrally manages users' contract information and efficiently processes contracts.

[1327] A "purchase request" is the process by which a user expresses their intention to purchase a selected product and requests that the product be purchased.

[1328] A "completion notice" is a notification that informs that a particular process or procedure has been successfully completed.

[1329] This invention relates to a system that provides product suggestions and facilitates purchases while taking into account the user's emotional state. The system aims to enable users to access e-commerce sites using their smartphones, receive optimal product suggestions through an interactive interface, and complete the purchase process smoothly.

[1330] User Authentication

[1331] When a user enters their authentication information (user ID and password) into the app, the device sends it to the server. The server compares it with the database to determine whether the login is successful. If the login is successful, the server sends the user's personal profile back to the device, and user authentication is complete.

[1332] Interactive interface

[1333] After logging in, the device displays an interactive interface. The first question displayed is, "What kind of products have you been interested in lately?" When the user enters an answer, that answer is sent to the server and the next question is generated. For example, if the user answers "fashion items," the next question displayed will be, "Specifically, what kind of items are you looking for?"

[1334] emotion recognition

[1335] The user's responses, along with image data captured by the device's camera, are sent to the server. The server uses an emotion recognition engine to analyze the user's emotional state. This emotion recognition engine works in conjunction with image processing software such as OpenCV and generates emotion data using a generative AI model.

[1336] Database records

[1337] User responses and emotional data are stored in temporary memory and then recorded in a hearing database. This allows for the accumulation of data that reflects the user's preferences and emotional state.

[1338] Product suggestion

[1339] The server executes an algorithm to suggest the optimal product based on accumulated hearing and sentiment data. This algorithm selects products to suggest, taking into account the user's past purchase history and feedback from other users. The specific product and price are then displayed on the terminal in the format of "This is the perfect fashion item for you."

[1340] Purchase application and completion notification

[1341] When a user agrees to a suggested product and submits a purchase request, the device sends that information to the server. The server then integrates with the backend contract management system to automatically complete the purchase process. Once the purchase is complete, the server sends a completion notification to the user's registered email address or via SMS, and a purchase completion screen is also displayed on the device.

[1342] Specific example

[1343] 1. Example of a prompt:

[1344] Authentication information entry: "Please enter your User ID and password."

[1345] Emotion recognition: "Please take a picture of your face with the camera."

[1346] Suggestions based on purchase history: "Based on your past purchase history and sentiment data, we suggest the following products."

[1347] For example, a user opens the app, enters their ID and password, and logs in. Then, they take a picture of their face with their smartphone camera, and an emotion recognition engine analyzes their emotions. Based on past history and emotion data, the server suggests the most suitable products. The user reviews the suggested products and decides to purchase them.

[1348] This invention enables optimal product recommendations that take into account the user's emotional state and facilitates a smooth purchasing process. This is expected to improve user satisfaction.

[1349] The flow of a specific process in Application Example 2 will be explained using Figure 14.

[1350] Step 1: User Authentication

[1351] The user enters their ID and password into their smartphone. The device sends this authentication information to the server. The server compares it with the user information in the database to determine whether login is permitted. If the login is successful, the server sends the user's personal profile back to the device. The input is the user's authentication information, and the output is the personal profile upon successful login or an error message upon failure.

[1352] Step 2: Display the interactive interface

[1353] When the terminal receives a signal indicating successful login, it displays an interactive interface. The user is presented with the initial question, "What products have you been interested in recently?" Once the user enters their answer, it is sent to the server. The input is the user's response to the question, and the output is the content of the next question.

[1354] Step 3: Emotion Recognition Processing

[1355] When a user answers a question, the device's camera captures a picture of the user's face. The captured image data is sent to a server, where the server's emotion recognition engine analyzes the image. A generative AI model is used to analyze the user's emotions and generate emotion data. The input is the user's face image, and the output is the analyzed emotion data.

[1356] Step 4: Recording responses and emotional data

[1357] The server stores user responses and sentiment data in temporary storage and then records them in the hearing database. This allows data to accumulate. The input is the user's responses and sentiment data, and the output is the data stored in the hearing database.

[1358] Step 5: Run the product suggestion algorithm.

[1359] The server executes a product recommendation algorithm based on data and sentiment data recorded in the hearing database. This algorithm selects the most suitable products by referring to the user's past purchase history, usage history, and feedback from other users. The input is accumulated data and sentiment data, and the output is a list of selected products.

[1360] Step 6: Display the optimal product

[1361] The terminal displays a list of optimal products received from the server to the user. For example, it might show specific products and their prices in a format like, "These are the perfect fashion items for you." The input is a list of products selected by the server, and the output is detailed product information displayed to the user.

[1362] Step 7: Purchase Application

[1363] When a user agrees to a suggested product and submits a purchase request, the terminal sends that information to the server. The server then integrates with the backend contract management system to automatically complete the purchase process. The input is the user's purchase request information, and the output is the information linked to the contract management system.

[1364] Step 8: Purchase Completion Notification

[1365] Once the purchase is complete, the server sends a completion notification to the user's registered email address or via SMS, and also displays a purchase completion screen on the device. The user confirms that the purchase is complete and receives instructions on the next steps. The input is the purchase completion information, and the output is the completion notification and the completion screen displayed on the device.

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

[1367] Data generation model 58 is a type of so-called generative AI (Artificial Intelligence). One example of data generation model 58 is ChatGPT (Internet Search).<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search) <url: https: gemini.google.com ?hl="ja">Examples of generative AI include the following. The data generation model 58 is obtained by performing deep learning on a neural network. The data generation model 58 is input with prompts containing instructions, and with inference data such as audio data representing speech, text data representing text, and image data representing images. The data generation model 58 infers from the input inference data according to the instructions indicated by the prompts, and outputs the inference results in data formats such as audio data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

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

[1369] [Fourth Embodiment]

[1370] Figure 7 shows an example of the configuration of the data processing system 410 according to the fourth embodiment.

[1371] As shown in Figure 7, the 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.

[1372] The data processing device 12 comprises a computer 22, a database 24, and a communication interface 26. The computer 22 is an example of a "computer" related to the technology of this disclosure. The computer 22 comprises a processor 28, RAM 30, and storage 32. The processor 28, RAM 30, and storage 32 are connected to a bus 34. The database 24 and the communication interface 26 are also connected to the bus 34. The communication interface 26 is connected to a network 54. An example of the network 54 is a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[1373] The robot 414 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication interface 44, and a controlled object 443. The computer 36 includes a processor 46, RAM 48, and storage 50. The processor 46, RAM 48, and storage 50 are connected to a bus 52. The microphone 238, speaker 240, camera 42, and controlled object 443 are also connected to the bus 52.

[1374] The microphone 238 receives voice signals from the user 20 and receives instructions from the user 20. The microphone 238 captures the voice signals from the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio according to the instructions from the processor 46.

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

[1376] Communication interface 44 is connected to network 54. Communication interfaces 44 and 26 are responsible for the exchange of various information between processor 46 and processor 28 via network 54. The exchange of various information between processor 46 and processor 28 using communication interfaces 44 and 26 is performed in a secure manner.

[1377] The controlled object 443 includes a display device, LEDs in the eyes, and motors that drive 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 robot 414's emotions can be expressed by controlling these motors. Furthermore, the robot 414's facial expressions can also be expressed by controlling the illumination state of the LEDs in its eyes.

[1378] Figure 8 shows an example of the main functions of the data processing device 12 and the robot 414. As shown in Figure 8, the data processing device 12 performs specific processing using the processor 28. The storage 32 stores the specific processing program 56.

[1379] The specific processing program 56 is an example of a "program" relating to the technology of this 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.

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

[1381] In robot 414, the processor 46 performs the reception output processing. The storage 50 stores the reception output program 60. 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 processing is realized by the processor 46 operating as a control unit 46A according to the reception output program 60 executed on the RAM 48.

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

[1383] This invention relates to a system that allows users to easily and efficiently propose and apply for contract plans. This system logs in based on the user's authentication information, listens to the user's requests and preferences through an interactive interface, and proposes the most suitable contract plan based on that information. Furthermore, it can automatically process the contract application and finally sends a contract completion notification to the user.

[1384] Program processing

[1385] User authentication process

[1386] User: The user enters their authentication information (user ID and password) into the terminal.

[1387] Terminal: The terminal sends the entered authentication information to the server.

[1388] Server: The server compares the received authentication information with the database and determines whether login is permitted. If successful, it returns the user's personal profile to the terminal. If unsuccessful, it returns an error message.

[1389] Device: The device will either display an error message or, if successful, display the user's personal profile.

[1390] Request gathering process

[1391] Terminal: Displays an interactive interface to users who have successfully logged in. It displays initial questions such as, "Are you satisfied with the service you are currently using?"

[1392] User: The user answers the question (e.g., "Insufficient data").

[1393] Terminal: The terminal receives the response and generates and displays the next question (e.g., "How much data do you want?").

[1394] User: The user also answers the following question (e.g., "I would like 20GB per month").

[1395] Terminal: Temporarily saves the answer and sends it to the server.

[1396] Server: Records user responses in the hearing database.

[1397] Plan proposal processing

[1398] Server: Executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users.

[1399] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[1400] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[1401] Server: We will receive any additional questions or requested changes and recalculate the optimal plan.

[1402] Device: Display the new plan to the user.

[1403] System Integration Processing

[1404] Device: After the user agrees to the proposed plan, a button will be displayed to proceed with the "Subscription Application".

[1405] User: The user clicks the contract application button.

[1406] Server: Receives contract application information and integrates with the backend contract management system. Registers contract information in the contract management database.

[1407] Order completion notification processing

[1408] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or SMS. Sends completion details to the device.

[1409] Terminal: Displays a screen indicating that the order has been completed and provides the user with detailed information such as contract details and service start date.

[1410] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[1411] Specific example

[1412] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, the server verifies it against the database, and the login process is initiated. If the login is successful, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server calculates the optimal plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[1413] In this way, the present invention makes it possible to accurately understand user needs and propose and accept efficient and user-friendly contract plans.

[1414] The following describes the processing flow.

[1415] Step 1:

[1416] User: The user enters their authentication information (user ID and password) into the terminal.

[1417] Step 2:

[1418] Terminal: The terminal sends the entered authentication information to the server.

[1419] Step 3:

[1420] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[1421] Step 4:

[1422] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[1423] Step 5:

[1424] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[1425] Step 6:

[1426] Terminal: Displays an interactive interface and presents the user with the question, "Are you satisfied with the service you are currently using?"

[1427] Step 7:

[1428] User: The user enters an answer to the question (e.g., "Insufficient data").

[1429] Step 8:

[1430] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[1431] Step 9:

[1432] User: The user answers the following question (e.g., "I would like 20GB per month").

[1433] Step 10:

[1434] Terminal: The terminal temporarily stores the answer and sends it to the server.

[1435] Step 11:

[1436] Server: The server records the user's responses in the hearing database.

[1437] Step 12:

[1438] Server: The server analyzes the recorded interview data and runs an algorithm to select the optimal contract plan.

[1439] Step 13:

[1440] Server: Sends the selected optimal contract plan to the terminal.

[1441] Step 14:

[1442] Device: The device displays the proposed contract plan to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[1443] Step 15:

[1444] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[1445] Step 16:

[1446] Terminal: Sends additional questions or requested changes from the user to the server.

[1447] Step 17:

[1448] Server: Receives additional questions or requested changes and runs an algorithm to recalculate the optimal plan.

[1449] Step 18:

[1450] Server: Sends the new contract plan to the device.

[1451] Step 19:

[1452] Device: Display new contract plans to the user.

[1453] Step 20:

[1454] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[1455] Step 21:

[1456] Terminal: Sends contract application information to the server.

[1457] Step 22:

[1458] Server: Receives contract application information and integrates with the backend contract management system.

[1459] Step 23:

[1460] Server: Registers contract information in the contract management database.

[1461] Step 24:

[1462] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[1463] Step 25:

[1464] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[1465] Step 26:

[1466] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[1467] (Example 1)

[1468] Next, we will describe Example 1. In the following description, the data processing device 12 will be referred to as the "server" and the robot 414 as the "terminal".

[1469] Conventional contract plan proposal systems failed to adequately reflect user needs and preferences, making it difficult to provide users with the most suitable contract plan quickly and efficiently. In particular, a challenge was the inability to recalculate the plan when users had additional questions or requested changes to the presented plan, resulting in a degraded user experience.

[1470] The identification process performed by the identification processing unit 290 of the data processing device 12 in Example 1 is realized by the following means.

[1471] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recording the answers in a database; means for executing an algorithm to select the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; and means for receiving additional questions or change requests from the user, and recalculating and displaying the optimal contract plan again. This makes it possible to accurately grasp the user's needs and desires, propose the optimal contract plan, and quickly make revised proposals.

[1472] "Authentication information" refers to the information a user needs to log in to a system, and typically consists of a user ID and password.

[1473] A "database" is an organized collection of data, a system for retrieving, storing, and updating information.

[1474] An "interactive interface" is a user interface that allows the user and the system to communicate in both directions.

[1475] "Means for generating questions and answers" refers to a function that creates appropriate questions based on user input and collects user responses to those questions.

[1476] An "algorithm" is a set of procedures or computational methods for solving a specific problem.

[1477] A "contract plan" refers to the terms and conditions of the agreement for a user to use the service.

[1478] "Application information" refers to the necessary data that a user provides when they wish to enter into a contract.

[1479] A "backend contract management system" is a system used for managing and updating contract details.

[1480] A "completion notification" is a notification sent to inform a user that a transaction or procedure has been successfully completed.

[1481] "Additional questions or requested changes" refers to any further information the user would like to know or any changes they would like to make regarding the proposed plan.

[1482] This invention relates to a system for users to easily and efficiently propose and apply for contract plans. This system includes the following processes: user authentication, requirements gathering, plan proposal, system integration, and order completion notification.

[1483] Hardware and software to be used

[1484] The system's hardware includes a server, terminals (e.g., tablet devices), and a database. The server is responsible for processes such as verifying authentication information, executing plan proposal algorithms, and sending notifications. The software used includes a MySQL or PostgreSQL database, algorithms implemented in Python, and a mail server (e.g., SendGrid). Terminals handle the display of the user interface, input of user data, and communication with the server, using a standard web browser or interactive interface software.

[1485] Processing details

[1486] The server first receives the authentication information (user ID and password) entered by the user and compares it with the database. If authentication is successful, the user's personal profile is returned and displayed on the terminal. Next, the terminal displays an interactive interface to hear the user's requests and preferences. A question-and-answer exchange takes place, and this information is sent to the server and recorded in the database.

[1487] The server uses machine learning models and other tools to calculate and select the optimal contract plan based on recorded data. This calculation takes into account the user's usage history and feedback from other users. The selected plan is displayed on the terminal, and the user reviews the proposal and enters additional questions or requests for changes via the terminal as needed. The server receives this new information, recalculates the plan, and displays the result on the terminal.

[1488] If the user agrees to the proposed plan, the device displays a contract application button, and when the user clicks it, the contract application information is sent to the server. The server then integrates this information with the backend contract management system to finalize the contract. Once the contract is complete, the server sends a completion notification to the user's registered email address or via SMS, and the device also displays confirmation of the order completion.

[1489] Specific example

[1490] For example, if a user wishes to change their plan using a tablet terminal installed at a train station's ticket gate, they can follow these steps: The user enters their authentication information into the terminal, the server verifies it against a database, and the login process is initiated. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the server uses a machine learning model implemented in Python to calculate the optimal contract plan and displays it on the terminal. The user reviews and agrees to this plan, and the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal. In this way, the present invention enables accurate understanding of user needs and allows for the proposal and application of efficient and user-friendly contract plans.

[1491] Example of a prompt

[1492] "Please describe the system's processing flow for users to change their plan at terminals installed at train station ticket gates. Please include the specific names of the hardware and software used at each step, from user authentication to contract completion notification."

[1493] The flow of the specific processing in Example 1 will be explained using Figure 11.

[1494] Step 1:

[1495] The user enters their authentication information (user ID and password) into the terminal. This input is done using a text field. The input data consists of the user ID and password.

[1496] Step 2:

[1497] The terminal encrypts the entered authentication information and sends it to the server. Specifically, it encrypts and transmits the data using the SSL / TLS protocol. The input is the encrypted authentication information, and the output is the request to the server.

[1498] Step 3:

[1499] The server compares the received authentication information with the database. The database stores the user ID and the hashed password. The server retrieves the password hash corresponding to the user ID from the database and compares it with the input password. The input is encrypted authentication information, and the output is the authentication result (success / failure).

[1500] Step 4:

[1501] The server returns the user's personal profile to the terminal if authentication is successful, and an error message if it fails. The input is the authentication result, and the output is either the personal profile or the error message.

[1502] Step 5:

[1503] The device receives the authentication result and, if the login is successful, displays the user's personal profile; if it fails, it displays an error message. The input is the personal profile or the error message, and the output is the screen display.

[1504] Step 6:

[1505] The terminal displays an interactive interface to users who have successfully logged in, and shows the initial question, "Are you satisfied with the services you are currently using?". The input is the user's personal profile, and the output is the screen display of the question.

[1506] Step 7:

[1507] The user answers a question (e.g., "Insufficient data"). User input is provided through an interactive interface. Input is the user's answer to the question, and output is the transmission of the answer to the terminal.

[1508] Step 8:

[1509] The terminal receives the user's response and generates and displays the next question, "How much data do you need?". The input is the user's initial response, and the output is the screen display for the next question. The terminal temporarily stores this data.

[1510] Step 9:

[1511] The user also answers the following question (e.g., "I want 20GB per month"). This input is done through an interactive interface. The input is the user's answer to the following question, and the output is the transmission of the answer to the terminal.

[1512] Step 10:

[1513] The terminal temporarily stores the response and sends it to the server. The input is the user's response, and the output is the data sent to the server.

[1514] Step 11:

[1515] The server records user responses in a hearing database. The input is the user's response data, and the output is saving it to the database.

[1516] Step 12:

[1517] The server executes an algorithm to select the optimal contract plan based on user interview data. It also refers to usage history and feedback from other users. The inputs are interview data, usage history data, and feedback data, and the output is the optimal contract plan.

[1518] Step 13:

[1519] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is available for XXX yen"). The input is the proposed plan data, and the output is the screen display.

[1520] Step 14:

[1521] The user reviews the proposed plan and enters additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?"). This input is done through an interactive interface. The input consists of additional questions or requests for changes, and the output is the response sent to the device.

[1522] Step 15:

[1523] The server receives additional questions and requested changes and recalculates the optimal plan. The input is the data for the additional questions and requested changes, and the output is the recalculated contract plan.

[1524] Step 16:

[1525] The device displays the new plan to the user. The input is the recalculated contract plan data, and the output is the screen display.

[1526] Step 17:

[1527] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The input is the user's agreement, and the output is the display of the subscription application button.

[1528] Step 18:

[1529] The user clicks the contract application button. The input is the click of the contract application button, and the output is the submission of contract information.

[1530] Step 19:

[1531] The server receives contract application information and interacts with the backend contract management system. The input is the contract application information, and the output is the transmission of data to the contract management system.

[1532] Step 20:

[1533] The server registers contract information in the contract management database. The input is contract application information, and the output is saving it to the database.

[1534] Step 21:

[1535] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input is the contract completion information, and the output is the sending of the completion notification.

[1536] Step 22:

[1537] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The input is the contract completion information, and the output is the screen display.

[1538] Step 23:

[1539] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The input is the completion notification, and the output is the confirmation and instructions for the next steps.

[1540] (Application Example 1)

[1541] Next, we will explain Application Example 1. In the following explanation, the data processing device 12 will be referred to as the "server" and the robot 414 as the "terminal".

[1542] In recent years, with the advancement of e-commerce, users need to select the optimal purchase plan and products from a vast amount of product information, thus requiring a more efficient purchasing experience and personalized suggestions. Conventional systems struggle to fully meet user needs, and in particular, they lack the means to propose the most suitable products in an interactive format and to facilitate a smooth purchasing process. Therefore, to improve user satisfaction, a system is needed that uses an interactive interface to quickly and accurately understand user requests and provide optimal product suggestions and purchasing procedures.

[1543] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 1 is realized by the following means.

[1544] In this invention, the server includes means for matching user authentication information with a database and determining whether or not login is permitted; means for generating questions and answers through an interactive interface based on user input information; means for recording the answers in a database; means for executing an algorithm for selecting the optimal contract plan based on the recorded data; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with a backend contract management system and processing the contract application; means for sending a completion notification to the user when the contract is completed; means for selecting the optimal purchase plan by referring to usage history and feedback from other users; and means for displaying product suggestions to the user based on the purchase plan and accepting the purchase procedure. This enables the user to efficiently select the optimal product from a large amount of product information and smoothly complete the purchase procedure.

[1545] "User authentication" is a series of processes that compare the authentication information a user provides to log in to a system with a database and determine whether or not they are allowed to log in.

[1546] An "interactive interface" is an interface used to facilitate smooth interaction with users, and it is a mechanism that dynamically generates questions and answers based on user input.

[1547] "Authentication information" refers to information such as user ID and password that a user uses when logging into a system.

[1548] A "database" is an electronic information recording system used to store and manage user information, interview data, contract details, and other similar information.

[1549] An "algorithm" is a set of procedures or calculation methods for achieving a specific objective, and in this system, it is a means of selecting the optimal contract or purchase plan.

[1550] A "backend system" is a system that manages and processes contract and purchase information, separate from the frontend system that interacts directly with users.

[1551] A "contract plan" refers to the specific details of the services or products offered to the user, along with their pricing.

[1552] A "purchase plan" is a plan that proposes the optimal combination of products to be obtained by purchasing them all at once or as a set, based on the user's needs.

[1553] A "completion notification" is a notification sent to the user informing them that the contract or purchase procedure has been successfully completed, and is sent via email, SMS, or other means.

[1554] "Usage history" refers to records of operations, selections, and purchases that a user has made through the system in the past.

[1555] "Feedback" refers to opinions and evaluations provided by users and other users, which are used in selecting plans and proposing products within this system.

[1556] The system for implementing this invention is designed to provide users with efficient and personalized proposals and procedures for contract and purchase plans. The system supports a series of processes in which the user easily authenticates, inputs their needs through an interactive interface, is proposed the most suitable plan, and completes the purchase or contract procedure.

[1557] The system configuration is as follows:

[1558] Hardware and software to use

[1559] Hardware: Smartphone

[1560] Software: Mobile app (iOS and Android), server-side uses AWS (Amazon Web Services).

[1561] Database: MySQL or PostgreSQL

[1562] Generative AI model: GPT-4 (OpenAI)

[1563] User authentication process

[1564] The user launches the smartphone app and enters their ID and password. The app sends this information to the server, which verifies the authentication information against a database. If authentication is successful, the user's personal profile is displayed in the app.

[1565] Request gathering process

[1566] After successful login, the app displays an interactive interface. For example, the first question displayed might be, "Are you satisfied with your recent purchase?" The user answers this question (e.g., "I want a more portable product"), and the app generates and displays the next question. By repeating this process, the app collects the user's requests and sends them to the server. The server records this data in a hearing database.

[1567] Plan proposal processing

[1568] The server uses recorded user responses to run an algorithm to select the optimal contract or purchase plan. Usage history and feedback from other users are also referenced. The calculated plan is presented to the user through the app.

[1569] System Integration Processing

[1570] Once a user agrees to a proposed plan, they can tap a button within the app to complete the contract application or purchase process. The server receives this information, processes it in conjunction with the backend contract management system and order management system, and registers the contract or purchase information in the relevant database.

[1571] Order completion notification processing

[1572] When a contract or purchase is completed, the server sends a completion notification to the user. This notification is sent to the registered email address or via SMS. A completion screen is also displayed in the app, allowing the user to confirm the contract details and purchase information.

[1573] Specific example

[1574] For example, if a user logs into a smartphone app and, in the interactive interface, indicates they are looking for "cooking utensils that are easy to use at a campsite they recently visited," the system will suggest a "lightweight and easy-to-pack camping cooking set," and will also display current discount information and related products. Once the user reviews the suggestion, agrees, and taps to purchase, the order is immediately completed, and an order confirmation notification is sent to their smartphone.

[1575] Example of a prompt

[1576] "I'm looking for easy-to-use cooking utensils at a campsite I recently visited."

[1577] "What type of cooking utensils do you prefer? (e.g., lightweight, portable, set, etc.)"

[1578] "Something lightweight and easy to package."

[1579] "Our recommended product is a lightweight and easy-to-pack camping cooking set. It's currently 30% off. Would you like to purchase it?"

[1580] "yes"

[1581] "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[1582] By implementing this system, we can accurately grasp user needs and achieve efficient, personalized contract and purchasing processes.

[1583] The flow of a specific process in Application Example 1 will be explained using Figure 12.

[1584] Step 1: User Authentication Process

[1585] The user launches the smartphone app and enters their ID and password on the authentication screen. The user ID and password are provided as input.

[1586] The terminal sends the entered authentication information to the server. At this time, the user ID and password are sent to the server as data packets.

[1587] The server compares the received authentication information with the database to determine whether or not the login is permitted. This process involves comparing the user information stored in the database with the entered authentication information.

[1588] The server returns the user's personal profile to the device if authentication is successful, and an error message if it fails. The output upon successful authentication is the user's profile information, while the output upon failure is an error message.

[1589] Based on the received data, the device will display the personal profile screen if successful, or an error message if unsuccessful.

[1590] Step 2: Request gathering process

[1591] The terminal displays an interactive interface to users who have successfully logged in. The system's initial question is, "Are you satisfied with your recent purchases?" The user is then provided with further questions as input.

[1592] The user enters an answer to this question (e.g., "I want a product that is easier to carry"). That answer is then sent to the device.

[1593] The device temporarily stores the user's response and generates and displays the next question (e.g., "What type of product do you prefer?"). The generated question is created by an AI model based on the user's response.

[1594] The server receives response data sent from the terminal and records it in the hearing database. User response data is provided as input, and recorded in the hearing database as output.

[1595] Step 3: Plan Proposal Processing

[1596] The server executes an algorithm to select the optimal contract plan based on recorded user interview data. This algorithm also utilizes usage history and feedback from other users stored in the database. The input to this process is user interview data and usage history, and the output is the selected contract plan.

[1597] The server sends the selected plan to the terminal, and the terminal displays the plan to the user (e.g., "Lightweight and easy-to-pack camping cooking set available at 30% off"). The sent plan is displayed as output.

[1598] Step 4: System Integration Process

[1599] If the user agrees to the proposed plan, they tap the purchase button displayed on their device. The user's consent action is provided as input.

[1600] The server receives the operation information and processes the contract application in cooperation with the backend contract management system. This cooperation process includes registering the user's purchase information in the contract management system. As output, the contract application information is registered in the system.

[1601] The server registers the purchase completion information in the contract management database. Purchase completion data is provided as input.

[1602] Step 5: Order completion notification processing

[1603] The server sends a completion notification to the user's registered email address or via SMS when a contract or purchase is completed. Completion notification data is provided as input, and the completion notification is sent to the user as output.

[1604] The device displays a completion screen to the user, providing contract details and purchase information. The output is the completion screen.

[1605] The user can then confirm the completion notification and proceed to the next step. Specifically, it might display something like, "Your purchase is complete. An order confirmation email has been sent to your registered email address."

[1606] This series of processes allows users to efficiently and personalizedly enter into service contracts and purchase products.

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

[1608] This invention relates to a system that proposes and accepts contract plans while also considering the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[1609] Program processing

[1610] User authentication process

[1611] User: The user enters their authentication information (user ID and password) into the terminal.

[1612] Terminal: The terminal sends the entered authentication information to the server.

[1613] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[1614] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[1615] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[1616] Request gathering process

[1617] Terminal: Displays an interactive interface to users who have successfully logged in. The initial question is, "Are you satisfied with the service you are currently using?"

[1618] User: The user enters an answer to the question (e.g., "Insufficient data").

[1619] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[1620] User: The user answers the following question (e.g., "I would like 20GB per month").

[1621] Terminal: Temporarily saves the answer and sends it to the server.

[1622] Server: Records user responses in the hearing database.

[1623] Emotion recognition processing

[1624] Terminal: Activates an emotion engine to recognize emotions from the user's responses and facial expressions.

[1625] Server: The emotion engine analyzes the user's emotional state and generates emotion data.

[1626] Server: Based on the emotional state, adjust the content and tone of the next question and send it to the terminal.

[1627] Terminal: Displays the adjusted questions and waits for the user's response.

[1628] Plan proposal processing

[1629] Server: Executes an algorithm to select the optimal contract plan based on user interview data and sentiment data. It also refers to usage history and feedback from other users.

[1630] Terminal: Displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen").

[1631] User: The user reviews the proposed plan and enters any additional questions or requests for changes as needed (e.g., "Is there a plan with unlimited data usage?").

[1632] Server: Receives additional questions or requested changes and runs an algorithm to recalculate the optimal plan.

[1633] Device: Display the new plan to the user.

[1634] System Integration Processing

[1635] Device: After the user agrees to the proposed plan, a button will be displayed to proceed with the "Subscription Application".

[1636] User: The user clicks the contract application button.

[1637] Server: Receives contract application information and integrates with the backend contract management system.

[1638] Server: Registers contract information in the contract management database.

[1639] Order completion notification processing

[1640] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or SMS. Sends completion details to the device.

[1641] Terminal: Displays a screen indicating that the order has been completed and provides the user with detailed information such as contract details and service start date.

[1642] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[1643] Specific example

[1644] For example, if a user wishes to change their plan at a terminal installed at a train station's ticket gate, the following steps are taken: The user enters their authentication information into the terminal, which the server then compares with the database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, the emotion engine is activated and analyzes the user's emotional state. The server analyzes the emotional data along with the interview data to calculate the optimal plan and displays it on the terminal. The user reviews this plan, and if they agree, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[1645] In this way, the present invention makes it possible to propose and accept highly accurate contract plans that take into account the user's emotions, and is expected to improve user satisfaction.

[1646] The following describes the processing flow.

[1647] Step 1:

[1648] User: The user enters their authentication information (user ID and password) into the terminal.

[1649] Step 2:

[1650] Terminal: The terminal sends the entered authentication information to the server.

[1651] Step 3:

[1652] Server: The server compares the received authentication information with the database to determine whether or not the login is permitted.

[1653] Step 4:

[1654] Server: If login is successful, the server returns the user's personal profile to the device. If it fails, it generates and sends an error message.

[1655] Step 5:

[1656] Device: The device will either display an error message or, if the login is successful, display the personal profile.

[1657] Step 6:

[1658] Terminal: Displays an interactive interface and presents the user with the initial question, "Are you satisfied with the service you are currently using?"

[1659] Step 7:

[1660] User: The user enters an answer to the question (e.g., "Insufficient data").

[1661] Step 8:

[1662] Terminal: The terminal receives the user's response and displays the next question, "How much data do you want?"

[1663] Step 9:

[1664] User: The user answers the following question (e.g., "I would like 20GB per month").

[1665] Step 10:

[1666] Terminal: The terminal temporarily stores the answer and sends it to the server.

[1667] Step 11:

[1668] Server: The server records the user's responses in the hearing database.

[1669] Step 12:

[1670] Terminal: The terminal activates the emotion engine and captures the user's responses and facial expressions.

[1671] Step 13:

[1672] Server: The emotion engine analyzes the captured information and recognizes the user's emotional state.

[1673] Step 14:

[1674] Server: The server processes the recognized emotion data and adjusts the content and tone of the next question.

[1675] Step 15:

[1676] Terminal: Displays a prepared question to the user and waits for the user's response.

[1677] Step 16:

[1678] User: The user answers a pre-set question (e.g., "I'm also considering an unlimited plan").

[1679] Step 17:

[1680] Terminal: Sends additional responses from the user to the server.

[1681] Step 18:

[1682] Server: The server runs an algorithm to select the optimal contract plan again based on the additional responses and sentiment data.

[1683] Step 19:

[1684] Server: Sends the selected optimal contract plan to the terminal.

[1685] Step 20:

[1686] Device: Display new contract plans to the user (e.g., "The plan with 20GB of data per month is XXX yen, and the unlimited plan is YYY yen").

[1687] Step 21:

[1688] User: Once the user agrees to the final plan, they click the "Submit Contract" button.

[1689] Step 22:

[1690] Terminal: Sends contract application information to the server.

[1691] Step 23:

[1692] Server: Receives contract application information and integrates with the backend contract management system.

[1693] Step 24:

[1694] Server: Registers contract information in the contract management database.

[1695] Step 25:

[1696] Server: Confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS.

[1697] Step 26:

[1698] Terminal: Displays a screen indicating completion and provides the user with detailed information such as contract details and service start date.

[1699] Step 27:

[1700] User: Confirm the order completion notification and receive instructions on the next steps. Also, review the contract details.

[1701] (Example 2)

[1702] Next, we will describe Example 2. In the following description, the data processing device 12 will be referred to as the "server" and the robot 414 as the "terminal".

[1703] Conventional contract plan proposal systems were limited to basic functions such as login using user authentication information, question generation, and answer recording. However, because they presented questions and plans in a fixed manner without considering the user's emotional state, user satisfaction was low, and improving the contract rate was difficult. Furthermore, they did not cover plan selection using feedback from other users, so optimal proposals were not adequately made.

[1704] The identification processing performed by the identification processing unit 290 of the data processing device 12 in Example 2 is realized by the following means. In this invention, the server includes means for determining whether or not login is permitted by comparing the authentication information entered by the user with the database; means for recognizing emotions based on the user's input information and facial expressions; means for generating and adjusting the next question based on the emotion recognition result; means for recording the answer in the database; means for executing an algorithm that selects the optimal contract plan based on the recorded data and other user information; means for displaying the selected contract plan to the user and accepting the contract application; means for linking the contract application information with the backend contract management system and processing the contract application; and means for sending a completion notification to the user when the contract is completed. This makes it possible to generate questions and propose plans that take into account the user's emotional state, thereby improving the contract rate and user satisfaction.

[1705] "Authentication information" refers to the information a user enters to identify themselves, specifically their user ID and password.

[1706] A "database" is a system for storing data in an organized and structured manner, and for searching and updating it as needed.

[1707] An "interactive interface" is an interface that allows users to communicate with a system in a two-way manner, and refers to a format where users input answers in response to questions.

[1708] "Means of recognizing emotions" refers to technologies that analyze a user's facial expressions, voice, and text to identify their emotional state.

[1709] An "algorithm" refers to a set of procedures or calculation methods defined to solve a specific problem.

[1710] A "contract plan" refers to a summary of the services and conditions that a user can subscribe to.

[1711] A "backend contract management system" refers to a core system used for managing and processing contract information.

[1712] A "completion notification" refers to a means of communication used to inform the user that a contract has been successfully completed.

[1713] "Usage history" refers to a record of services that a user has used in the past.

[1714] "Feedback" refers to information about opinions and reputations obtained from users.

[1715] "Emotion recognition results" refer to data on the user's emotional state obtained through means of recognizing emotions.

[1716] This invention relates to a system that proposes and accepts contract plans while taking into account the user's emotional state. This system logs in based on the user's authentication information, listens to the user's requests and desires through an interactive interface, and proposes the optimal contract plan based on that. Furthermore, it incorporates an emotion engine that recognizes the user's emotions, allowing it to adjust questions and plans based on the user's emotional state. It also automatically processes the contract application and finally sends a contract completion notification to the user.

[1717] As an embodiment of this system, the user authentication process will be described first. The user enters authentication information (user ID and password). The terminal sends the entered authentication information to the server. The server compares the received authentication information with the database and determines whether login is permitted. This database stores the user's authentication information. If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The terminal displays the error message, or displays the personal profile if the login is successful.

[1718] Next, we will explain the request gathering process. The terminal displays an interactive interface to users who have successfully logged in. The first question presented is, "Are you satisfied with the service you are currently using?" The user enters an answer to the question (e.g., "I don't have enough data"). The terminal receives the user's answer and displays the next question, "How much data do you need?" The user answers the next question (e.g., "I need 20GB per month"). The terminal temporarily saves the answer and sends it to the server. The server records the user's answer in the request database.

[1719] In emotion recognition processing, an emotion engine is activated to analyze the user's responses and facial expressions. The terminal uses this emotion engine to analyze the user's emotional state and generate emotion data. The server adjusts the content and tone of the next question based on this emotion data and sends it to the terminal. The terminal displays the adjusted question and waits for the user's response.

[1720] Furthermore, during the plan proposal process, the server executes an algorithm that uses user interview data and sentiment data to select the optimal contract plan. This algorithm also refers to the user's usage history and feedback from other users, and uses a machine learning model. The server sends the optimal plan to the terminal. The terminal displays the proposed plan received from the server to the user, who then reviews and agrees to the plan.

[1721] In the system integration process, after the user agrees to the proposed plan, the terminal displays a button to execute a "contract application." When the user clicks the contract application button, the server receives the contract application information and integrates with the backend contract management system. This registers the contract information in the contract management database.

[1722] During the order completion notification process, the server confirms that the contract has been completed and sends a completion notification to the user's registered email address or via SMS. The device also simultaneously displays a completion screen, providing the user with detailed information such as the contract details and the start date of service. The user confirms this notification and proceeds to the next step.

[1723] As a concrete example, consider a scenario where a user wishes to change their plan at a terminal installed at a train station's ticket gate. When the user enters their authentication information into the terminal, the server verifies it against a database and initiates the login process. Upon successful login, an interactive interface is displayed, showing the user questions about their current usage and desired plan. After the user answers, an emotion engine is activated to analyze the user's emotional state. Based on this data, the server calculates the optimal plan and displays it on the terminal. Once the user reviews and agrees to the plan, the contract is automatically processed. Finally, a contract completion notification is sent to the user's smartphone, and a completion screen is also displayed on the terminal.

[1724] This will enable the proposal and application of highly accurate contract plans that take user emotions into consideration, and is expected to improve user satisfaction.

[1725] Examples of prompt statements to input into a generative AI model include the following:

[1726] "Please enter the questions users will use to choose a new data plan."

[1727] "Please generate an error message to display when login fails."

[1728] "Please use the emotion recognition engine to analyze the user's emotional state and input the results."

[1729] The flow of the specific processing in Example 2 will be explained using Figure 13.

[1730] Step 1: User Authentication Process

[1731] The user enters their authentication information (user ID and password) into the terminal. The input data consists of the user ID and password.

[1732] The terminal sends the entered authentication information to the server. The input data is the user ID and password, and the output is the authentication information sent to the server.

[1733] The server compares the received authentication information with the database to determine whether the login is successful or not. The input data consists of the user ID and password; the corresponding information is retrieved from the database and compared with the authentication information. The output is either a successful or unsuccessful login.

[1734] If the login is successful, the server returns the user's personal profile to the terminal. If it fails, it generates and sends an error message. The output is either the personal profile or the error message.

[1735] The device will either display an error message or, if the login was successful, display the user's personal profile. The output will be either an error message or the user's personal profile.

[1736] Step 2: Request gathering process

[1737] The terminal displays an interactive interface to users who have successfully logged in. It presents the question, "Are you satisfied with the service you are currently using?". The input data is a successful login, and the output is the display of the question.

[1738] The user enters an answer to a question (e.g., "Insufficient data"). The output is the user's answer.

[1739] The terminal receives the user's response and displays the next question, "How much data do you need?". The input data is the user's response, and the output is the display of the next question.

[1740] The user answers the following question (e.g., "I want 20GB per month"). The output is the user's response.

[1741] The terminal temporarily stores the response and sends it to the server. The input data is the user's response, and the output is the data sent to the server.

[1742] The server records the user's responses in a hearing database. The input data is the user's responses, and the output is the recording in the database.

[1743] Step 3: Emotion Recognition Processing

[1744] The device activates an emotion engine to analyze the user's responses and facial expressions. The input data consists of the user's responses and facial expressions, and the output is the analysis result.

[1745] The server uses an emotion engine to analyze the user's emotional state and generate emotion data. The input data consists of the user's responses and facial expression data, and the output is emotion data.

[1746] The server adjusts the content and tone of the next question based on the emotional state and sends it to the terminal. The input data is emotional data and its analysis results, and the output is the adjusted question content.

[1747] The terminal displays the adjusted question and waits for the user's response. The output is the display of the adjusted question.

[1748] Step 4: Plan Proposal Processing

[1749] The server executes an algorithm that selects the optimal contract plan using user interview data and sentiment data. The input data is interview data and sentiment data, and the output is the optimal plan.

[1750] The server also refers to usage history and feedback from other users. The input data is usage history and feedback, and the output is the optimized calculation result of the algorithm.

[1751] The server sends the optimal plan to the terminal. The input data is the optimal plan, and the output is the data sent to the terminal.

[1752] The terminal displays the proposed plan received from the server to the user (e.g., "A new plan with 20GB of data per month is XXX yen"). The output is the display of the plan.

[1753] The user reviews the proposed plan and enters any additional questions or requested changes as needed (e.g., "Is there a plan with unlimited data usage?"). The output consists of these additional questions and requested changes.

[1754] The server receives additional questions and requested changes and runs an algorithm to recalculate the optimal plan. The input data is the additional questions and requested changes, and the output is the recalculated optimal plan.

[1755] The device displays the new plan to the user. The output is a display of the new plan.

[1756] Step 5: System Integration Process

[1757] The device displays a button to proceed with "Subscription Application" after the user agrees to the proposed plan. The output is the display of the Subscription Application button.

[1758] The user clicks the contract application button. The output indicates their intention to apply for the contract.

[1759] The server receives contract application information and interacts with the backend contract management system. The input data is the contract application information, and the output is the data to be sent to the contract management system.

[1760] The server registers contract information in the contract management database. The input data is the contract information, and the output is the data registered in the database.

[1761] Step 6: Order completion notification processing

[1762] The server confirms that the contract has been successfully completed and sends a completion notification to the user's registered email address or via SMS. The input data is the contract completion information, and the output is the completion notification.

[1763] The server sends completion details to the terminal. The input data is contract completion information, and the output is the data sent to the terminal.

[1764] The terminal displays a screen indicating that the order has been completed and provides the user with detailed information such as the contract details and the start date of service. The output is a display of the completion screen.

[1765] The user confirms the order completion notification and receives instructions on the next steps. They also review the contract details. The output consists of a confirmation of the notification and instructions for the next steps.

[1766] (Application Example 2)

[1767] Next, we will explain application example 2. In the following explanation, the data processing device 12 will be referred to as the "server" and the robot 414 as the "terminal".

[1768] Traditional e-commerce sites relied primarily on past purchase and search history to determine user preferences. However, this approach failed to consider user emotional states, making it difficult to recommend optimal products. Furthermore, the systems for enabling users to select products and complete purchases smoothly and without stress were inadequate. As a result, improving user satisfaction proved challenging.

[1769] The specific processing performed by the specific processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means.

[1770] In this invention, the server includes means for determining whether or not to allow login by comparing authentication information entered by the user with a database; means for generating questions and answers through an interactive interface based on the user's input information; means for recognizing the user's emotional state based on an image of the user; means for recording the answers and emotional state in a database; means for executing an algorithm to select the optimal product based on the recorded data and emotional data; means for displaying the selected product to the user and accepting the purchase application; means for linking the purchase application information with a backend contract management system and processing the purchase application; and means for sending a completion notification to the user when the purchase is completed. This enables optimal product suggestions that also take into account the user's emotional state and a smooth purchase procedure.

[1771] "User authentication" is the process of verifying whether a user has legitimate access rights based on the authentication information they provide.

[1772] An "interactive interface" is an interface that allows the user and the system to communicate in both directions.

[1773] "Emotion recognition" is a technology that analyzes a user's emotional state based on their images, voice, and text.

[1774] A "database" is a data management system that organizes and stores large amounts of data, making it possible to retrieve it quickly as needed.

[1775] An "algorithm" is a set of specific steps or procedures for solving a particular problem.

[1776] A "contract management system" is a system that centrally manages users' contract information and efficiently processes contracts.

[1777] A "purchase request" is the process by which a user expresses their intention to purchase a selected product and requests that the product be purchased.

[1778] A "completion notice" is a notification that informs that a particular process or procedure has been successfully completed.

[1779] This invention relates to a system that provides product suggestions and facilitates purchases while taking into account the user's emotional state. The system aims to enable users to access e-commerce sites using their smartphones, receive optimal product suggestions through an interactive interface, and complete the purchase process smoothly.

[1780] User Authentication

[1781] When a user enters their authentication information (user ID and password) into the app, the device sends it to the server. The server compares it with the database to determine whether the login is successful. If the login is successful, the server sends the user's personal profile back to the device, and user authentication is complete.

[1782] Interactive interface

[1783] After logging in, the dev...

Claims

1. By the user entering their authentication information, A means for comparing the authentication information with a database and determining whether or not to allow login, A means for generating questions and answers through an interactive interface based on user input information, A means for recording the response in a database, A means of executing an algorithm that selects the optimal contract plan based on recorded data, A means of displaying the selected contract plan to the user and accepting contract applications, A means of integrating contract application information with a backend contract management system and processing contract applications, A means of sending a completion notification to the user when the contract is completed, A system that includes this.

2. The system according to claim 1, further comprising means for providing an interactive interface to a user and generating the next question based on the user's response.

3. The system according to claim 1, further comprising means for referring to the user's usage history and feedback from other users when selecting a contract plan.

Images