system

Abstract

We provide the system. [Solution] A means of receiving approval request information from each business system, A means of generating an approval request email based on the received approval request information, A means of embedding an approval link and a rejection link in the generated approval request email, A means of sending an approval request email to a manager, A means of receiving requests from approval or rejection links clicked by managers, Means for performing approval or denial processing based on received requests, A system that includes a means of notifying managers of the approval or rejection result via feedback email.

Description

Technical Field

[0005] ,

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

Background Art

[0002] Patent Document 1 discloses a method for controlling a persona chatbot, which is performed by at least one processor, and includes 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 approval system, since a management staff member needs to log in to each business system individually to process approval requests, it is cumbersome and inefficient. In addition, the management staff member receives many approval request emails and needs to process them manually, which may increase working hours and cause mistakes. Furthermore, from the perspective of access control and security, if the operation of individual logins is insufficient, the risk may increase.

Means for Solving the Problems

[0005] The present invention provides a system that receives approval request information from various business systems and generates approval request emails based on that information. To solve the above-mentioned problems, the system described in claim 1 includes means for embedding approval links and denial links in the generated approval request email and sending it to a manager. The system also includes means for receiving requests from approval or denial links clicked by managers, performing approval or denial processing based on those requests, and notifying managers of the results via feedback email. Furthermore, the system described in claim 2 further includes means for generating authentication tokens included in the approval and denial links and verifying the validity of those tokens. The system described in claim 3 further includes means for logging all approval and denial actions by managers and periodically monitoring the logs to detect anomalies.

[0006] "Approval request information" refers to data sent from a business system to a manager requesting some kind of action or decision.

[0007] An "approval request email" is an email generated based on approval request information and sent to a manager.

[0008] An "approval link" is a link included in an approval request email, and it is a URL that allows a manager to perform a specific approval action by clicking it.

[0009] A "denial link" is a link included in an approval request email that, when clicked by a manager, allows them to perform a specific denial action.

[0010] A "manager" refers to a person within an organization who supervises the actions of their subordinates and is in a position to grant necessary approvals and decisions.

[0011] A "request" is an HTTP request sent to the system when a manager clicks an approve or reject link.

[0012] "Approval or denial processing" refers to the process of performing an approval or denial action based on the content of a received request.

[0013] A "feedback email" is an email sent to a manager to inform them of the approval or rejection result of their request.

[0014] An "authentication token" is a one-time, short-term invalid authentication piece of information included in the approve and deny links.

[0015] A "log" is data used to record all approval and rejection actions by managers.

[0016] An "abnormal" behavior refers to a pattern or action that deviates from normal operation, such as a large number of requests occurring in a short period of time.

[0017] A "business system" is a system designed to support various business operations, such as attendance management, account creation, and work management. [Brief explanation of the drawing]

[0018] [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]It is a conceptual diagram showing an example of the configuration of a data processing system according to the fourth embodiment. [Figure 8] It 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] It shows an emotion map to which a plurality of emotions are mapped. [Figure 10] It shows an emotion map to which a plurality of emotions are mapped. [Figure 11] It is a sequence diagram showing the processing flow of the data processing system in Example 1. [Figure 12] It is a sequence diagram showing the processing flow of the data processing system in Application Example 1. [Figure 13] It is a sequence diagram showing the processing flow of the data processing system in Example 2 when an emotion engine is combined. [Figure 14] It is a sequence diagram showing the processing flow of the data processing system in Application Example 2 when an emotion engine is combined.

Mode for Carrying Out the Invention

[0019] 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.

[0020] First, the language used in the following description will be explained.

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

[0022] In the following embodiments, signed RAM (Random Access Memory) is a memory that temporarily stores information and is used as work memory by the processor.

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

[0024] 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).

[0025] 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."

[0026] [First Embodiment]

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

[0028] 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.

[0029] 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).

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

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

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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".

[0039] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[0040] System Configuration Overview

[0041] The system of the present invention consists of the following components:

[0042] Various business systems (e.g., attendance systems, account management systems, business management systems)

[0043] Client terminal

[0044] Central server

[0045] Email clients for managers

[0046] Generating and sending approval request emails

[0047] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. Next, the terminal sends this approval request email to the manager.

[0048] Specific example:

[0049] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[0050] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[0051] The device will send this email to the administrator's email address.

[0052] Processing of approvals and denials

[0053] When a user (manager) clicks an approve or deny link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or denial) to the relevant business system to perform the specific approval or denial process.

[0054] Specific example:

[0055] The user (administrator) clicks the approval link in the email.

[0056] The server receives the request and parses and verifies the authentication token included in the link.

[0057] The server sends a request to the attendance system saying, "This overtime request has been approved."

[0058] Feedback and notifications

[0059] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected).

[0060] Specific example:

[0061] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[0062] Security and log management

[0063] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[0064] Specific example:

[0065] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[0066] In this way, the system of the present invention streamlines the approval and rejection processes and reduces the burden on managers. Furthermore, the system's security is ensured through advanced security measures.

[0067] The following describes the processing flow.

[0068] Program processing flow

[0069] Generating and sending approval request emails

[0070] Step 1:

[0071] The terminal receives approval request information from each business system.

[0072] Specific operation: Retrieve data related to approval requests from business systems via API requests. For example, receive employee overtime application information from the attendance system.

[0073] Step 2:

[0074] The terminal generates an approval request email based on the approval request information it has received.

[0075] Specific actions: The system will embed the received information (applicant's name, application details, reason for application, application date and time, etc.) into an email template and create the email body.

[0076] Step 3:

[0077] The device embeds both an approval link and a denial link in the approval request email.

[0078] Specific operation: The link will be given a parameter containing a one-time authentication token, which will then be inserted into the email body.

[0079] Step 4:

[0080] The device sends an approval request email to the manager.

[0081] Specific operation: Send an email to the administrator's email address via the SMTP server.

[0082] Processing of approvals and denials

[0083] Step 5:

[0084] The user (administrator) clicks the approval or rejection link in the email.

[0085] Specific operation: The manager clicks an approve or reject link in their email client, and the web browser automatically opens the link.

[0086] Step 6:

[0087] The server receives the request when the link is clicked.

[0088] Specific operation: Receives an HTTP request and parses the parameters contained within it (such as authentication tokens and authorization IDs).

[0089] Step 7:

[0090] The server verifies the authentication token included in the link.

[0091] Specific actions: Check the expiration date and one-time use restriction of the authentication token and confirm that it is valid.

[0092] Step 8:

[0093] The server performs the approval or rejection process.

[0094] Specific operation: Depending on the content of the request, an API request is sent to the corresponding business system to perform an approval or rejection operation.

[0095] Feedback and notifications

[0096] Step 9:

[0097] The server receives the approval or rejection result.

[0098] Specific operation: Receive API responses from business systems and analyze the results.

[0099] Step 10:

[0100] The server generates a feedback email for the manager.

[0101] Specific action: Based on the approval or rejection result, create the body of the feedback email.

[0102] Step 11:

[0103] The server sends a feedback email to the manager.

[0104] Specific operation: Send a feedback email to the administrator's email address via the SMTP server.

[0105] Security and log management

[0106] Step 12:

[0107] The server logs all approval and denial actions.

[0108] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[0109] Step 13:

[0110] The server periodically monitors logs and detects any anomalies.

[0111] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors.

[0112] The above is a specific processing flow for a system that allows managers to efficiently approve and reject items using email.

[0113] (Example 1)

[0114] 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."

[0115] The goal is to reduce the effort required for managers to individually log into each business system to approve and reject decisions, thereby streamlining the approval process, while also preventing unauthorized operations and security risks through advanced security measures.

[0116] 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.

[0117] In this invention, the server includes means for receiving approval request information from each information processing system, means for generating an approval request electronic message based on the received approval request information, means for embedding approval links and denial links in the generated approval request electronic message, means for sending the approval request electronic message to an administrator, means for receiving requests from approval links or denial links clicked by the administrator, means for performing approval or denial processing based on the received requests, means for notifying the administrator of the approval or denial result via a feedback electronic message, means for recording all approval and denial actions, monitoring them periodically to detect anomalies, means for generating authentication data included in the approval and denial links and verifying the validity of the authentication data, and means for periodically monitoring the recorded data to detect abnormal operations or security risks. This enables administrators to efficiently perform approval and denial operations without individually logging into business systems, while also improving security.

[0118] An "information processing system" is a system that includes software and hardware for managing and executing all aspects of business operations.

[0119] "Approval request information" refers to information that includes applicant information and other necessary data used to request approval for a specific action or operation within the system.

[0120] An "approval request electronic message" is a message in email format that is generated based on approval request information.

[0121] An "approval link" is a link included in an electronic message requesting approval; clicking it initiates the approval process.

[0122] A "denial link" is a link included in an electronic message requesting approval, and clicking it will initiate the denial process.

[0123] "Authentication data" refers to a one-time token or key embedded in an approve or deny link and used to verify its validity.

[0124] An "administrator" is a user who has the authority to perform the system's approval and rejection processes, and is typically someone in a management position.

[0125] A "feedback electronic message" is a message in the form of an email that notifies the administrator of the outcome of the approval or rejection process.

[0126] A "request" is the request information sent to the server when an administrator clicks an approve or reject link.

[0127] A "log" is a history of data used to record all approval and rejection actions performed within a system.

[0128] This invention provides a system that eliminates the need for administrators to individually log in to each information processing system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[0129] System Configuration

[0130] This system consists of the following components:

[0131] Information processing systems (e.g., attendance management systems, account management systems)

[0132] Client terminal

[0133] Central server

[0134] Administrator's email client

[0135] Receiving approval request information

[0136] The terminal receives approval request information from each information processing system. This information includes the applicant's name, application details, reason for application, and date and time of application.

[0137] Generating an approval request email

[0138] Based on the received approval request information, the terminal generates an electronic approval request message using a pre-prepared email template. This electronic message contains embedded approval and denial links, and these links are associated with one-time authentication data.

[0139] Sending an approval request email

[0140] The terminal generates an electronic approval request message which is then sent to the administrator via email.

[0141] Receiving and parsing requests

[0142] When a user (administrator) clicks an approval or denial link included in an email, the server receives a click request. The server analyzes the authentication data from the received click request and verifies its validity.

[0143] Processing of approval or denial

[0144] The server sends the analysis results (approval or rejection) to the relevant information processing system, which then performs the specific approval or rejection process. For example, it might send a request to the attendance management system stating, "This overtime request has been approved."

[0145] Feedback notification

[0146] Once the approval or rejection process is complete, the server generates and sends an electronic feedback message to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[0147] Log management and security

[0148] The server logs all approval and denial actions. This log includes the date and time of approval / denial, the content of the approval / denial, and the administrator's ID. The server also periodically monitors these logs to check for unusual operations or security risks.

[0149] Examples of specific cases and prompt statements

[0150] Specific example

[0151] 1. The terminal receives information from the attendance management system stating, "An employee has requested 5 hours of overtime." This information includes the employee's name, details of the overtime request, reason for the request, and date and time of the request.

[0152] 2. Based on the information received by the terminal, an electronic approval request message is generated with the message, "An employee has requested 5 hours of overtime. Do you approve it?" This electronic message contains both an approval link and a denial link, and each link is associated with authentication data.

[0153] 3. The terminal sends the generated approval request electronic message to the administrator's email address.

[0154] 4. When the user (administrator) clicks the "approval link" in the email, the server receives the request and parses and verifies the authentication data contained in the link.

[0155] 5. The server sends a request to the attendance management system stating, "The employee's request for 5 hours of overtime has been approved."

[0156] 6. The server generates and sends an electronic feedback message to the administrator stating, "The employee's request for 5 hours of overtime has been approved."

[0157] 7. The server logs all approval and rejection actions and periodically monitors the logs to detect anomalies.

[0158] Example of a prompt

[0159] "An employee has requested 5 hours of overtime. Do you approve it?"

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

[0161] Step 1: Receiving approval request information

[0162] The terminal receives approval request information from the information processing system. The input consists of data such as the applicant's name, application details, reason for application, and application date and time, which are transmitted from the information processing system. The terminal acquires and records this data, converting it into a format usable in the next processing step.

[0163] Step 2: Generating the approval request email

[0164] The terminal generates an electronic approval request message using an email template based on the received approval request information. This generation process embeds the input data (applicant's name, application details, reason for application, application date and time, etc.) into the template, outputting an email message containing approval and rejection links. Each link is accompanied by one-time authentication data.

[0165] Step 3: Sending the approval request email

[0166] The terminal sends the generated approval request electronic message to the administrator's email address. The input is the generated email and the administrator's email address, and the output is the approval request email received in the administrator's email client.

[0167] Step 4: Click the approve or reject link.

[0168] The user (administrator) clicks an approve or reject link included in the email. The input is the link selected by the administrator (approve or reject), and the output is that the click request is sent to the server. At this point, a browser opens and the request is sent.

[0169] Step 5: Analysis and verification of the authentication token

[0170] The server analyzes the received click request and verifies the validity of the authentication data contained in the link. The input is the authentication data contained in the click request, and the output is the verification result of whether or not that data is valid. The server checks the validity of the authentication data and proceeds to the next processing step.

[0171] Step 6: Sending a request to the business system

[0172] The server sends the analysis result (approval or denial) as a request to the relevant information processing system for specific processing. The input is the verification result of the authentication data and the content of approval or denial, and the output is the request sent to the information processing system (for example, "This overtime request has been approved"). The information processing system receives this request and updates the database.

[0173] Step 7: Generate and send the feedback email.

[0174] The server generates and sends an electronic feedback message to the administrator based on the approval or rejection result. The input is the processing result (approval or rejection), and the output is a feedback email. This email contains the approval or rejection result and details.

[0175] Step 8: Logging and Monitoring

[0176] The server logs all approval and denial actions and monitors them regularly to detect anomalies. The input is the details of each operation (e.g., date and time, content, administrator ID), and the output is the recorded log data. The server periodically monitors these logs to detect unusual operations and security risks.

[0177] (Application Example 1)

[0178] 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."

[0179] In factories and other manufacturing sites, approval from managers is often required before various tasks can be performed. This includes situations where human judgment is needed before certain tasks (e.g., production line adjustments or maintenance work) can be carried out. However, with conventional systems, managers must log in to multiple business systems individually and perform the approval process manually, resulting in wasted time and effort. Furthermore, in addition to streamlining the approval process, there is a need to ensure security and log management. This invention aims to solve these problems and streamline the approval process for tasks performed within factories.

[0180] 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.

[0181] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from approval or rejection links clicked by managers, means for performing approval or rejection processing based on the received requests, means for feeding back the approval or rejection results to the business system and instructing whether to proceed, means for notifying managers of the approval or rejection results via feedback email, means for obtaining manager approval before the task is executed by the automated machine, and means for the automated machine to execute the approved task. As a result, managers can efficiently perform task approval work, and business processes within the factory are automated. Furthermore, security is improved and log management is also achieved, improving the reliability of the entire system.

[0182] "Each business system" refers to a system used in factories and manufacturing sites to manage various business processes such as attendance management, account management, and work management.

[0183] "Approval request information" refers to information used to seek approval from a manager in order to perform a specific task or action, and includes the applicant's name, the content of the request, the reason for the request, and the date and time of the request.

[0184] An "approval request email" is an email generated based on approval request information and sent to a manager, containing both an approval link and a rejection link.

[0185] An "approval link" is a link embedded in an approval request email that, when clicked, allows the user to approve a specific task or action.

[0186] A "denial link" is a link embedded in an approval request email that, when clicked, allows the user to deny a specific task or action.

[0187] A "manager" is a person in a position of authority who has the authority to approve the implementation of tasks and actions in a factory or manufacturing site.

[0188] A "request" is a request sent to the server when an administrator clicks an approve or reject link.

[0189] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[0190] "Automated machinery" refers to robots and automated devices used to perform specific tasks in factories and manufacturing sites.

[0191] A "token" is a one-time authentication code included in the accept and reject links, used to verify its validity.

[0192] A "log" is data used to record all approval and rejection actions by managers.

[0193] An "anomaly" refers to unusual operations or security risks detected during the process of monitoring logs.

[0194] This invention provides a system that allows managers to efficiently approve or reject specific tasks before they are performed by automated machines in factories or manufacturing sites. Specific embodiments thereof are described below.

[0195] System Configuration

[0196] This system consists of the following main components:

[0197] Each business system

[0198] Automated machinery

[0199] Client terminal

[0200] Central server

[0201] Email clients for managers

[0202] Generating and sending approval request emails

[0203] The server receives approval request information from each business system. This information includes task details and related information. Based on this information, the server generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, each with a one-time authentication token. The server then sends this approval request email to the manager's email address.

[0204] Processing of approvals and denials

[0205] When a manager clicks an approve or deny link in an email, the server receives the request. The server analyzes the authentication token from the request and verifies its validity. The server then sends the analysis result (approval or denial) to the relevant business system for specific approval or denial processing. If approved, the server instructs automated machines to execute the task.

[0206] Feedback and notifications

[0207] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[0208] Security and log management

[0209] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[0210] Hardware and software to be used

[0211] Hardware: Client terminals (personal computers, smartphones), central server, automated machinery (robots and automated devices)

[0212] Software: Mail server (e.g., Postfix), Python, database (e.g., MySQL®), token generation library (token_generator)

[0213] Specific example

[0214] For example, if an automated machine ID is "12345" and a task ID is "56789" is to be executed, the server will send an approval request email to the administrator as follows:

[0215] Approval link: http: / / example.com / approve?token=abc123&task_id=56789&robot_id=12345

[0216] Denial link: http: / / example.com / deny?token=abc123&task_id=56789&robot_id=12345

[0217] Managers can approve or reject the task by clicking the link in this email.

[0218] Example of a prompt

[0219] "Automated machine ID '12345' is attempting to execute task ID '56789'. Please generate an approval request email and provide an approval link and a denial link."

[0220] This system allows managers to approve tasks efficiently and safely, and to smoothly advance automated processes within the factory.

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

[0222] Step 1:

[0223] The server receives approval request information from each business system. This information includes details of a specific task, the applicant, and the reason for the request. Input data includes, for example, the task ID, robot ID, and the request details. The server parses this information and formats it into the format required for the next processing step. The output is the formatted approval request information.

[0224] Step 2:

[0225] The server generates an approval request email based on the received approval request information. It uses an email template to embed task details and approval and rejection links. The input is the formatted approval request information, and the output is the generated approval request email. Specifically, it populates the data fields of the email template with the approval request information.

[0226] Step 3:

[0227] The server generates a one-time authentication token and attaches it to the accept and reject links. A token generation library is used to create a secure token. The input is the acceptance request email, and the output is the acceptance request email with the token embedded. Specifically, the generated token is appended to the URL of the link.

[0228] Step 4:

[0229] The server sends the generated approval request email to the administrator. It uses the SMTP protocol to deliver the email to the administrator's email address. The input is the approval request email with an embedded token, and the output is the transmission result. Specifically, this involves connecting to the mail server and sending the email.

[0230] Step 5:

[0231] When a manager clicks an approve or reject link, the server receives the request. The input is the request from the manager, and the output is the result of parsing the request. Specifically, the server extracts the token and task information from the request URL and verifies their validity.

[0232] Step 6:

[0233] The server performs approval or rejection processing based on the request. The input is the parsed request information, and the output is the processing result. Specifically, it notifies the business system whether or not the task can be executed.

[0234] Step 7:

[0235] The server notifies the manager of the approval or rejection result via feedback email. The input is the approval or rejection result, and the output is the feedback email. Specifically, the feedback email is generated and sent.

[0236] Step 8:

[0237] The server logs all approval and rejection actions and monitors them periodically. The input is each approval and rejection action, and the output is log data. Specifically, it writes to log files and periodically detects anomalies.

[0238] This series of processing steps allows managers to efficiently approve tasks for factory robots while also ensuring security and log management.

[0239] 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.

[0240] This invention combines an emotion engine with a system that allows managers to efficiently approve and reject requests via email, eliminating the need for them to individually log into each business system. Specific embodiments of this system are described below.

[0241] System Configuration Overview

[0242] The system of the present invention consists of the following components:

[0243] Various business systems (e.g., attendance systems, account management systems, business management systems)

[0244] Client terminal

[0245] Central server

[0246] Email clients for managers

[0247] Emotional Engine

[0248] Generating and sending approval request emails

[0249] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The terminal then sends this approval request email to the manager. Furthermore, the sentiment engine recognizes the manager's emotions and dynamically adjusts the email content as needed.

[0250] Specific example:

[0251] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[0252] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[0253] The emotion engine analyzes the manager's past emotional data and adds appropriate tone and suggestions to the email body.

[0254] The device will send this email to the administrator's email address.

[0255] Processing of approvals and denials

[0256] When a user (manager) clicks an approve or reject link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or rejection) to the relevant business system to perform the specific approval or rejection process. Furthermore, an emotion engine continuously monitors the manager's emotions and provides appropriate feedback if there is stress or dissatisfaction.

[0257] Specific example:

[0258] The user (administrator) clicks the approval link in the email.

[0259] The server receives the request and parses and verifies the authentication token included in the link.

[0260] The server sends a request to the attendance system saying, "This overtime request has been approved."

[0261] The emotion engine detects the manager's current emotions and sets an emotion flag in response to the processing request.

[0262] Feedback and notifications

[0263] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected). Additionally, the sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[0264] Specific example:

[0265] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[0266] The emotion engine analyzes the manager's emotions and adds messages such as, "Thank you for approving this. Let's discuss this at the next meeting," to the feedback email.

[0267] Security and log management

[0268] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[0269] Specific example:

[0270] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[0271] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[0272] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[0273] The following describes the processing flow.

[0274] Specific processing flow of the program

[0275] Generating and sending approval request emails

[0276] Step 1:

[0277] The terminal receives approval request information from each business system.

[0278] Specific operation: Retrieve data related to approval requests (e.g., applicant's name, application details, reason for application) from business systems via API requests. For example, receive overtime application information from the attendance system.

[0279] Step 2:

[0280] The terminal generates an approval request email based on the approval request information it has received.

[0281] Specific operation: Embed the received information into the email template and create the body of the approval request email. The template contains a basic format, and the application information is inserted at a predetermined position.

[0282] Step 3:

[0283] The terminal embeds approval and denial links in the approval request email.

[0284] Specific operation: Add parameters containing an authentication token that can be used only once to the link and insert this into the email body. For example, generate the HTML code for the "Approve" and "Deny" buttons.

[0285] Step 4:

[0286] The emotion engine recognizes the emotions of the management staff and dynamically changes the content of the email.

[0287] [[ID=2,4]]Specific operation: Analyze the emotions based on past approval histories and current status, and add an appropriate tone and proposed content to the email body. For example, if the management staff is feeling stressed, change it to a concise message.

[0288] Step 5:

[0289] The terminal sends the approval request email to the management staff.

[0290] Specific operation: Send the email to the management staff's email address via the SMTP server. Also record the sending log simultaneously.

[0291] Approval and denial processing

[0292] Step 6:

[0293] The user (management staff) clicks on the approval or denial link in the email.

[0294] Specific action: Click the approval or denial link in the mail client, and the web browser will open the link.

[0295] Step 7:

[0296] The server receives the request when the link is clicked.

[0297] Specific action: Receive the HTTP request and analyze the parameters (such as authentication token and approval ID) contained therein.

[0298] Step 8:

[0299] The server verifies the authentication token contained in the link.

[0300] Specific action: Check the expiration date and one-time use limit of the authentication token and confirm that it is valid.

[0301] Step 9:

[0302] The server executes the approval or denial process.

[0303] Specific example: According to the content of the request, send an API request to the corresponding business system and execute the approval or denial operation.

[0304] Feedback and notification

[0305] Step 10:

[0306] The server receives the approval or denial result.

[0307] Specific action: Receive the API response from the business system and analyze the result.

[0308] Step 11:

[0309] The emotion engine generates appropriate feedback email content based on the manager's emotions.

[0310] Specific actions: Dynamically change the tone and content of feedback emails by combining the approval or rejection result with the manager's sentiment data. For example, decide whether to add detailed guidance.

[0311] Step 12:

[0312] The server sends a feedback email to the manager.

[0313] Specific operation: Use the SMTP server to send the generated feedback email to the administrator's email address.

[0314] Security and log management

[0315] Step 13:

[0316] The server logs all approval and denial actions.

[0317] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[0318] Step 14:

[0319] The server periodically monitors logs and detects any anomalies.

[0320] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors. If an anomaly is detected, issue a warning.

[0321] Step 15:

[0322] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed.

[0323] Specific actions: Analyze emotional data and action logs to generate appropriate support messages for managers' emotional states.

[0324] In this way, the system of the present invention, which incorporates an emotion engine, allows managers to efficiently approve and reject requests via email without having to log into each business system. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[0325] (Example 2)

[0326] 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".

[0327] Traditional approval and rejection systems had drawbacks, including low efficiency due to the time and effort required for managers to log in to each business system individually to process requests. Furthermore, the systems relied solely on automated email notifications without considering the emotional state of managers, leading to increased stress and workload. Additionally, insufficient log management of approval and rejection actions raised security concerns.

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

[0329] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from the approval or rejection links clicked by the managers, means for performing approval or rejection processing based on the received requests, means for notifying the managers of the approval or rejection results via feedback email, means for analyzing the managers' past sentiment data and dynamically adjusting the email content, means for detecting the managers' current sentiment and providing appropriate feedback, means for generating authentication tokens included in the approval and rejection links and verifying the validity of the tokens, means for logging all approval and rejection actions by managers and periodically monitoring the logs to detect anomalies, and means for comparing log data and sentiment data and providing appropriate support messages. This eliminates the need for managers to log into each business system and enables efficient approval and rejection via email. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help reduce security risks.

[0330] "Each business system" refers to systems used for purposes such as attendance management, account management, and business management.

[0331] "Approval request information" refers to information used to request approval, such as the applicant's name, application details, reason for application, and application date and time.

[0332] An "approval request email" refers to an email generated based on approval request information and sent to a manager.

[0333] An "approval link" refers to a specific link embedded in an email that, when clicked by a manager, indicates their intention to approve the request.

[0334] A "denial link" refers to a specific link embedded in an email that, when clicked by a manager, indicates an intention to deny the work.

[0335] "Managerial position" refers to a person in a position that has the authority to approve or deny decisions.

[0336] A "request" refers to the request sent to the server when a manager clicks an approve or reject link.

[0337] An "authentication token" refers to a one-time-use identification piece of information included in the approve and deny links.

[0338] A "feedback email" refers to an email sent to a manager to notify them of the approval or rejection of a request.

[0339] The "emotion engine" refers to a function that analyzes managers' past emotional data and current emotional state to dynamically adjust email content and feedback.

[0340] "Logs" refer to records such as approval and rejection actions, date and time of operation, content, and the ID of the manager.

[0341] "Security monitoring" refers to the process of periodically analyzing log data to detect abnormal operations and security risks.

[0342] A "supportive message" refers to an appropriate message that the emotional engine provides when a manager may be experiencing stress or frustration.

[0343] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. This system incorporates an emotion engine to consider the manager's emotional state and reduce stress. Specific embodiments are described below.

[0344] System Configuration Overview

[0345] The system of the present invention consists of the following components:

[0346] Various business systems (e.g., attendance systems, account management systems, business management systems)

[0347] Client terminal

[0348] Central server

[0349] Email clients for managers

[0350] Emotional Engine

[0351] Hardware and software to be used

[0352] Client terminal: Receives approval request information from each business system, generates and sends approval request emails.

[0353] Central Server: Receives approval or denial requests from users and parses authentication tokens.

[0354] Manager's email client: Receives approval request emails and notifies the manager.

[0355] Emotion Engine: Analyzes the emotions of managers and provides functionality to dynamically adjust the tone and content of emails.

[0356] Various business systems: These include attendance management systems, account management systems, and business management systems, among others, that are subject to processing.

[0357] Generating and sending approval request emails

[0358] The terminal receives approval request information from various business systems. The received information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The sentiment engine analyzes the manager's past sentiment data and dynamically adjusts the email content. Next, the terminal sends this approval request email to the manager.

[0359] Specific example

[0360] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[0361] The terminal uses this information to generate an email saying, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[0362] The emotion engine adds messages such as, "Thank you for your approval. Let's discuss this matter at the next meeting."

[0363] The device will send this email to the administrator's email address.

[0364] Processing of approvals and denials

[0365] When a user (manager) clicks an approve or reject link in an email, the server receives the request and parses the authentication token contained in the link. After verifying the validity of the authentication token, the server sends the parsing result (approval or rejection) to the relevant business system and processes the specific approval or rejection. The sentiment engine detects the manager's current sentiment and provides appropriate feedback.

[0366] Specific example

[0367] The user (administrator) clicks the approval link in the email.

[0368] The server receives the request and parses and verifies the authentication token included in the link.

[0369] The server sends a request to the attendance system saying, "This overtime request has been approved."

[0370] The emotion engine detects the manager's current emotions and provides feedback such as, "Approval process complete."

[0371] Feedback and notifications

[0372] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes the approval or rejection result, along with details of the process (which applications were approved and which were rejected). The sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[0373] Specific example

[0374] The server generates an email stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[0375] The emotion engine adds the message, "Thank you for your approval. Let's discuss this matter at the next meeting."

[0376] The server will send this email to the administrator's email address.

[0377] Security and log management

[0378] The server logs all approval and rejection actions. The logs include the date and time of approval / rejection, the content of the approval / rejection, and the manager's ID. The server periodically monitors these logs to check for unusual activity or security risks. The sentiment engine compares past logs with current sentiment data to identify times when managers are particularly stressed and provides appropriate support messages.

[0379] Specific example

[0380] The server records all actions taken by administrators and analyzes the logs weekly to detect anomalies.

[0381] The emotion engine compares past logs with current emotion data to identify periods when managers are likely to be stressed. For example, if a tendency for stress to increase at the end of the month is detected, it will provide messages encouraging relaxation during that period.

[0382] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help to reduce security risks.

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

[0384] Step 1:

[0385] Receiving approval request information

[0386] The terminal receives approval request information from various business systems (e.g., attendance system, account management system).

[0387] Input: Applicant's name, application details, reason for application, date and time of application

[0388] Operation: Retrieves necessary information from the API or database of each business system.

[0389] Output: Approval request information data (Example: "Mr. Tanaka has requested 5 hours of overtime.")

[0390] Step 2:

[0391] Generating an approval request email

[0392] Based on the approval request information received by the device, an approval request email is generated using an email template.

[0393] Input: Approval request information data, email template

[0394] Function: Embed approval request information into email templates and generate and embed approval and rejection links.

[0395] Output: Generated approval request email (Example: "Mr. / Ms. Tanaka has requested 5 hours of overtime. Do you approve it?")

[0396] Step 3:

[0397] Adjusting and sending approval request emails

[0398] The emotion engine analyzes the manager's past emotional data and dynamically adjusts the content of emails.

[0399] Input: Generated approval request email, historical sentiment data

[0400] Function: The emotion engine adjusts the tone and content of the email (e.g., adds words of encouragement).

[0401] Output: Adjusted approval request email

[0402] The device sends this adjusted approval request email to the manager.

[0403] Operation: Sends emails using a mail server.

[0404] Output: Approval request email sent to manager completed.

[0405] Step 4:

[0406] Receiving an approval or rejection request

[0407] The user (administrator) clicks the approval or rejection link in the email.

[0408] Input: Clicking an approve or disapprove link

[0409] Operation: The server receives clicks from the administrator.

[0410] Output: Request data (e.g., click on an approval link)

[0411] Step 5:

[0412] Analysis of authentication tokens

[0413] The server parses the authentication token from the received request.

[0414] Input: Request data, authentication token

[0415] Function: Validates the token and verifies the legitimacy of the request.

[0416] Output: Authentication result (authentication successful or failed)

[0417] Step 6:

[0418] Performing an approval or denial process

[0419] The server sends a processing request to the relevant business system based on the authentication result, and then performs the specific approval or denial process.

[0420] Input: Authentication results, business system data

[0421] Operation: Calls the API of the relevant business system and performs the approval or denial process.

[0422] Output: Processing result (Example: "Overtime request has been approved.")

[0423] The emotion engine detects the manager's current emotions and provides appropriate feedback.

[0424] Input: Current sentiment data of managers

[0425] Operation: Generates feedback content based on emotional data.

[0426] Output: Feedback message

[0427] Step 7:

[0428] Generating and sending feedback emails

[0429] The server generates and sends an email to the manager to provide feedback that the approval or rejection process is complete.

[0430] Input: Processing result data, feedback message

[0431] Operation: Generates a feedback email and sends it using the mail server.

[0432] Output: Feedback email sent to managers completed.

[0433] Step 8:

[0434] Log management and security monitoring

[0435] The server logs all approval and denial actions.

[0436] Input: Approval and denial action data

[0437] Operation: Records operation data to a log file.

[0438] Output: Log file update

[0439] The server periodically monitors logs to check for unusual operations and security risks.

[0440] Input: Log data

[0441] Function: Log data analysis and anomaly detection

[0442] Output: Anomaly detection message

[0443] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[0444] Input: Log data, current sentiment data

[0445] Operation: Comparative analysis of emotion data and log data

[0446] Output: Support message

[0447] (Application Example 2)

[0448] 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".

[0449] Currently, factory managers must log into each business system individually and manually process approvals and rejections. This process is time-consuming and labor-intensive, further increasing manager stress. Furthermore, the lack of consideration for managers' emotional states can hinder efficient work. Additionally, the slow provision of feedback on approval and rejection results reduces overall work efficiency.

[0450] In Application Example 2, the specific processing performed by the specific processing unit 290 of the data processing device 12 is realized by the following means. In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval links and rejection links in the generated approval request emails, means for sending the approval request emails to managers, emotion engine means for recognizing the emotions of managers and dynamically adjusting the email content as needed, means for receiving requests from approval or rejection links clicked by managers, means for executing approval or rejection processing based on the received requests, and means for notifying managers of the approval or rejection result via feedback email. As a result, managers can efficiently approve or reject requests via email without having to log in to individual business systems. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to improved work efficiency and reduced stress.

[0451] "Each business system" refers to systems that process various types of information related to business operations, such as attendance management systems and work instruction systems within a factory.

[0452] "Approval request information" refers to information that includes the details of employee applications for work permits and attendance records.

[0453] An "approval request email" is an email generated based on approval request information and sent to a manager.

[0454] "Approval and rejection links" are links embedded in approval request emails that, when clicked by a manager, send an approval or rejection notification to the server.

[0455] A "manager" is a person in a position of responsibility who is in charge of supervising factory operations and attendance.

[0456] An "emotional engine" is a system that recognizes the emotional state of managers and provides appropriate feedback and dynamic message adjustments based on those emotions.

[0457] A "request" is a request sent to the server after clicking an accept or reject link.

[0458] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[0459] The system for implementing this invention consists of various business systems, client terminals, a central server, an email client for managers, and an emotion engine.

[0460] Each business system processes information related to factory operations, such as attendance management systems and work instruction systems, and generates approval request information. This approval request information includes the applicant's name, application details, reason for application, and application date and time.

[0461] The client terminal receives approval request information from each business system and generates an approval request email using a pre-prepared email template. This email contains embedded approval and rejection links and is issued with a one-time authentication token. The generated email is sent to the manager's email address.

[0462] The emotion engine recognizes the emotions of managers and dynamically adjusts email content by analyzing past emotional data. By adding appropriate tone and suggestions to the email body, it enables communication that takes the manager's emotional state into consideration.

[0463] When a manager clicks an approve or reject link in an email, the central server receives the request. The server parses and verifies the authentication token included in the request and then sends the approval or rejection decision to the relevant business system.

[0464] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes details of the approval or rejection process, and the sentiment engine adds appropriate messages to show consideration for the manager.

[0465] Let's illustrate the operation of the entire system with an example. For instance, consider a scenario where a manager is wearing smart glasses. When this manager receives an email, it displays the message, "Employee A has requested 4 hours of overtime. Do you approve it?" along with links to approve and deny the request. If the manager clicks the approve link, the server receives the request and processes the approval in the relevant business system. The emotion engine analyzes the manager's emotions and generates a feedback email, including an additional message such as, "Thank you for approving. Let's discuss this at the next meeting," and sends it to the manager.

[0466] By using a generative AI model, the emotion engine analyzes managers' past emotional data and dynamically adjusts messages. This leads to increased work efficiency and reduced stress for managers.

[0467] Example of a prompt:

[0468] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[0469] In this way, the system of this invention enables factory managers to approve and reject items quickly and efficiently, ensuring smooth operations and providing responses that take into account the emotional state of managers.

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

[0471] Step 1:

[0472] Each business system generates approval request information, such as work requests and attendance requests, and sends it to the client terminal. Input includes employee name, request details, reason for request, and date and time of request. The client terminal receives this information as output.

[0473] Step 2:

[0474] The terminal generates an approval request email using a pre-prepared email template based on the received approval request information. The input is the approval request information received in Step 1. As data processing, the information is embedded into the template and the email body is generated. The output is the generated approval request email.

[0475] Step 3:

[0476] The device embeds an approval link and a denial link in the generated approval request email. The input is the approval request email generated in step 2. As data processing, a one-time authentication token is generated and attached to the link. The output is the approval request email with the links embedded.

[0477] Step 4:

[0478] The emotion engine recognizes the manager's emotions and dynamically adjusts the email content based on past emotion data. The inputs are the manager's past emotion data and the email generated in step 3. The data calculation adjusts the message according to the manager's emotions. The output is the adjusted approval request email.

[0479] Step 5:

[0480] The terminal sends a pre-configured approval request email to the manager. The inputs are the pre-configured approval request email from step 4 and the manager's email address. The output is the approval request email sent to the manager.

[0481] Step 6:

[0482] A manager clicks an approve or reject link in an email and sends the request to the server. Inputs include the manager's click action and the authentication token contained within the link. Outputs include the request sent to the server.

[0483] Step 7:

[0484] The server parses the received request and verifies the validity of the authentication token included in the link. The inputs are the request and authentication token received in step 6. The data operation involves parsing and verifying the authentication token. The output is the result of the approval or denial process.

[0485] Step 8:

[0486] The server sends the approval or rejection decision to the relevant business system. The input is the processing result obtained in step 7. The output is the approval or rejection request sent to the business system.

[0487] Step 9:

[0488] The server notifies the manager of the approval or rejection result via feedback email. The emotion engine then recognizes the manager's emotions again and dynamically adjusts the content of the feedback email. The inputs are the result processed in step 8 and the manager's current emotional state. The data processing involves generating and adjusting the content of the feedback email. The output is the feedback email sent to the manager.

[0489] As a concrete example, consider a scenario where a manager uses smart glasses to perform an approval process. Enter the following prompt into the generative AI model:

[0490] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[0491] Based on this prompt, the emotion engine makes appropriate adjustments and provides feedback to reduce stress for managers and improve work efficiency.

[0492] 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.

[0493] 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.

[0494] 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.

[0495] [Second Embodiment]

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

[0497] 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.

[0498] 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).

[0499] 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.

[0500] 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.

[0501] 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).

[0502] 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.

[0503] 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.

[0504] 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.

[0505] 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.

[0506] 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.

[0507] 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".

[0508] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[0509] System Configuration Overview

[0510] The system of the present invention consists of the following components:

[0511] Various business systems (e.g., attendance systems, account management systems, business management systems)

[0512] Client terminal

[0513] Central server

[0514] Email clients for managers

[0515] Generating and sending approval request emails

[0516] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. Next, the terminal sends this approval request email to the manager.

[0517] Specific example:

[0518] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[0519] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[0520] The device will send this email to the administrator's email address.

[0521] Processing of approvals and denials

[0522] When a user (manager) clicks an approve or deny link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or denial) to the relevant business system to perform the specific approval or denial process.

[0523] Specific example:

[0524] The user (administrator) clicks the approval link in the email.

[0525] The server receives the request and parses and verifies the authentication token included in the link.

[0526] The server sends a request to the attendance system saying, "This overtime request has been approved."

[0527] Feedback and notifications

[0528] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected).

[0529] Specific example:

[0530] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[0531] Security and log management

[0532] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[0533] Specific example:

[0534] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[0535] In this way, the system of the present invention streamlines the approval and rejection processes and reduces the burden on managers. Furthermore, the system's security is ensured through advanced security measures.

[0536] The following describes the processing flow.

[0537] Program processing flow

[0538] Generating and sending approval request emails

[0539] Step 1:

[0540] The terminal receives approval request information from each business system.

[0541] Specific operation: Retrieve data related to approval requests from business systems via API requests. For example, receive employee overtime application information from the attendance system.

[0542] Step 2:

[0543] The terminal generates an approval request email based on the approval request information it has received.

[0544] Specific actions: The system will embed the received information (applicant's name, application details, reason for application, application date and time, etc.) into an email template and create the email body.

[0545] Step 3:

[0546] The device embeds both an approval link and a denial link in the approval request email.

[0547] Specific operation: The link will be given a parameter containing a one-time authentication token, which will then be inserted into the email body.

[0548] Step 4:

[0549] The device sends an approval request email to the manager.

[0550] Specific operation: Send an email to the administrator's email address via the SMTP server.

[0551] Processing of approvals and denials

[0552] Step 5:

[0553] The user (administrator) clicks the approval or rejection link in the email.

[0554] Specific operation: The manager clicks an approve or reject link in their email client, and the web browser automatically opens the link.

[0555] Step 6:

[0556] The server receives the request when the link is clicked.

[0557] Specific operation: Receives an HTTP request and parses the parameters contained within it (such as authentication tokens and authorization IDs).

[0558] Step 7:

[0559] The server verifies the authentication token included in the link.

[0560] Specific actions: Check the expiration date and one-time use restriction of the authentication token and confirm that it is valid.

[0561] Step 8:

[0562] The server performs the approval or rejection process.

[0563] Specific operation: Depending on the content of the request, an API request is sent to the corresponding business system to perform an approval or rejection operation.

[0564] Feedback and notifications

[0565] Step 9:

[0566] The server receives the approval or rejection result.

[0567] Specific operation: Receive API responses from business systems and analyze the results.

[0568] Step 10:

[0569] The server generates a feedback email for the manager.

[0570] Specific action: Based on the approval or rejection result, create the body of the feedback email.

[0571] Step 11:

[0572] The server sends a feedback email to the manager.

[0573] Specific operation: Send a feedback email to the administrator's email address via the SMTP server.

[0574] Security and log management

[0575] Step 12:

[0576] The server logs all approval and denial actions.

[0577] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[0578] Step 13:

[0579] The server periodically monitors logs and detects any anomalies.

[0580] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors.

[0581] The above is a specific processing flow for a system that allows managers to efficiently approve and reject items using email.

[0582] (Example 1)

[0583] 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."

[0584] The goal is to reduce the effort required for managers to individually log into each business system to approve and reject decisions, thereby streamlining the approval process, while also preventing unauthorized operations and security risks through advanced security measures.

[0585] 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.

[0586] In this invention, the server includes means for receiving approval request information from each information processing system, means for generating an approval request electronic message based on the received approval request information, means for embedding approval links and denial links in the generated approval request electronic message, means for sending the approval request electronic message to an administrator, means for receiving requests from approval links or denial links clicked by the administrator, means for performing approval or denial processing based on the received requests, means for notifying the administrator of the approval or denial result via a feedback electronic message, means for recording all approval and denial actions, monitoring them periodically to detect anomalies, means for generating authentication data included in the approval and denial links and verifying the validity of the authentication data, and means for periodically monitoring the recorded data to detect abnormal operations or security risks. This enables administrators to efficiently perform approval and denial operations without individually logging into business systems, while also improving security.

[0587] An "information processing system" is a system that includes software and hardware for managing and executing all aspects of business operations.

[0588] "Approval request information" refers to information that includes applicant information and other necessary data used to request approval for a specific action or operation within the system.

[0589] An "approval request electronic message" is a message in email format that is generated based on approval request information.

[0590] An "approval link" is a link included in an electronic message requesting approval; clicking it initiates the approval process.

[0591] A "denial link" is a link included in an electronic message requesting approval, and clicking it will initiate the denial process.

[0592] "Authentication data" refers to a one-time token or key embedded in an approve or deny link and used to verify its validity.

[0593] An "administrator" is a user who has the authority to perform the system's approval and rejection processes, and is typically someone in a management position.

[0594] A "feedback electronic message" is a message in the form of an email that notifies the administrator of the outcome of the approval or rejection process.

[0595] A "request" is the request information sent to the server when an administrator clicks an approve or reject link.

[0596] A "log" is a history of data used to record all approval and rejection actions performed within a system.

[0597] This invention provides a system that eliminates the need for administrators to individually log in to each information processing system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[0598] System Configuration

[0599] This system consists of the following components:

[0600] Information processing systems (e.g., attendance management systems, account management systems)

[0601] Client terminal

[0602] Central server

[0603] Administrator's email client

[0604] Receiving approval request information

[0605] The terminal receives approval request information from each information processing system. This information includes the applicant's name, application details, reason for application, and date and time of application.

[0606] Generating an approval request email

[0607] Based on the received approval request information, the terminal generates an electronic approval request message using a pre-prepared email template. This electronic message contains embedded approval and denial links, and these links are associated with one-time authentication data.

[0608] Sending an approval request email

[0609] The terminal generates an electronic approval request message which is then sent to the administrator via email.

[0610] Receiving and parsing requests

[0611] When a user (administrator) clicks an approval or denial link included in an email, the server receives a click request. The server analyzes the authentication data from the received click request and verifies its validity.

[0612] Processing of approval or denial

[0613] The server sends the analysis results (approval or rejection) to the relevant information processing system, which then performs the specific approval or rejection process. For example, it might send a request to the attendance management system stating, "This overtime request has been approved."

[0614] Feedback notification

[0615] Once the approval or rejection process is complete, the server generates and sends an electronic feedback message to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[0616] Log management and security

[0617] The server logs all approval and denial actions. This log includes the date and time of approval / denial, the content of the approval / denial, and the administrator's ID. The server also periodically monitors these logs to check for unusual operations or security risks.

[0618] Examples of specific cases and prompt statements

[0619] Specific example

[0620] 1. The terminal receives information from the attendance management system stating, "An employee has requested 5 hours of overtime." This information includes the employee's name, details of the overtime request, reason for the request, and date and time of the request.

[0621] 2. Based on the information received by the terminal, an electronic approval request message is generated with the message, "An employee has requested 5 hours of overtime. Do you approve it?" This electronic message contains both an approval link and a denial link, and each link is associated with authentication data.

[0622] 3. The terminal sends the generated approval request electronic message to the administrator's email address.

[0623] 4. When the user (administrator) clicks the "approval link" in the email, the server receives the request and parses and verifies the authentication data contained in the link.

[0624] 5. The server sends a request to the attendance management system stating, "The employee's request for 5 hours of overtime has been approved."

[0625] 6. The server generates and sends an electronic feedback message to the administrator stating, "The employee's request for 5 hours of overtime has been approved."

[0626] 7. The server logs all approval and rejection actions and periodically monitors the logs to detect anomalies.

[0627] Example of a prompt

[0628] "An employee has requested 5 hours of overtime. Do you approve it?"

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

[0630] Step 1: Receiving approval request information

[0631] The terminal receives approval request information from the information processing system. The input consists of data such as the applicant's name, application details, reason for application, and application date and time, which are transmitted from the information processing system. The terminal acquires and records this data, converting it into a format usable in the next processing step.

[0632] Step 2: Generating the approval request email

[0633] The terminal generates an electronic approval request message using an email template based on the received approval request information. This generation process embeds the input data (applicant's name, application details, reason for application, application date and time, etc.) into the template, outputting an email message containing approval and rejection links. Each link is accompanied by one-time authentication data.

[0634] Step 3: Sending the approval request email

[0635] The terminal sends the generated approval request electronic message to the administrator's email address. The input is the generated email and the administrator's email address, and the output is the approval request email received in the administrator's email client.

[0636] Step 4: Click the approve or reject link.

[0637] The user (administrator) clicks an approve or reject link included in the email. The input is the link selected by the administrator (approve or reject), and the output is that the click request is sent to the server. At this point, a browser opens and the request is sent.

[0638] Step 5: Analysis and verification of the authentication token

[0639] The server analyzes the received click request and verifies the validity of the authentication data contained in the link. The input is the authentication data contained in the click request, and the output is the verification result of whether or not that data is valid. The server checks the validity of the authentication data and proceeds to the next processing step.

[0640] Step 6: Sending a request to the business system

[0641] The server sends the analysis result (approval or denial) as a request to the relevant information processing system for specific processing. The input is the verification result of the authentication data and the content of approval or denial, and the output is the request sent to the information processing system (for example, "This overtime request has been approved"). The information processing system receives this request and updates the database.

[0642] Step 7: Generate and send the feedback email.

[0643] The server generates and sends an electronic feedback message to the administrator based on the approval or rejection result. The input is the processing result (approval or rejection), and the output is a feedback email. This email contains the approval or rejection result and details.

[0644] Step 8: Logging and Monitoring

[0645] The server logs all approval and denial actions and monitors them regularly to detect anomalies. The input is the details of each operation (e.g., date and time, content, administrator ID), and the output is the recorded log data. The server periodically monitors these logs to detect unusual operations and security risks.

[0646] (Application Example 1)

[0647] 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."

[0648] In factories and other manufacturing sites, approval from managers is often required before various tasks can be performed. This includes situations where human judgment is needed before certain tasks (e.g., production line adjustments or maintenance work) can be carried out. However, with conventional systems, managers must log in to multiple business systems individually and perform the approval process manually, resulting in wasted time and effort. Furthermore, in addition to streamlining the approval process, there is a need to ensure security and log management. This invention aims to solve these problems and streamline the approval process for tasks performed within factories.

[0649] 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.

[0650] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from approval or rejection links clicked by managers, means for performing approval or rejection processing based on the received requests, means for feeding back the approval or rejection results to the business system and instructing whether to proceed, means for notifying managers of the approval or rejection results via feedback email, means for obtaining manager approval before the task is executed by the automated machine, and means for the automated machine to execute the approved task. As a result, managers can efficiently perform task approval work, and business processes within the factory are automated. Furthermore, security is improved and log management is also achieved, improving the reliability of the entire system.

[0651] "Each business system" refers to a system used in factories and manufacturing sites to manage various business processes such as attendance management, account management, and work management.

[0652] "Approval request information" refers to information used to seek approval from a manager in order to perform a specific task or action, and includes the applicant's name, the content of the request, the reason for the request, and the date and time of the request.

[0653] An "approval request email" is an email generated based on approval request information and sent to a manager, containing both an approval link and a rejection link.

[0654] An "approval link" is a link embedded in an approval request email that, when clicked, allows the user to approve a specific task or action.

[0655] A "denial link" is a link embedded in an approval request email that, when clicked, allows the user to deny a specific task or action.

[0656] A "manager" is a person in a position of authority who has the authority to approve the implementation of tasks and actions in a factory or manufacturing site.

[0657] A "request" is a request sent to the server when an administrator clicks an approve or reject link.

[0658] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[0659] "Automated machinery" refers to robots and automated devices used to perform specific tasks in factories and manufacturing sites.

[0660] A "token" is a one-time authentication code included in the accept and reject links, used to verify its validity.

[0661] A "log" is data used to record all approval and rejection actions by managers.

[0662] An "anomaly" refers to unusual operations or security risks detected during the process of monitoring logs.

[0663] This invention provides a system that allows managers to efficiently approve or reject specific tasks before they are performed by automated machines in factories or manufacturing sites. Specific embodiments thereof are described below.

[0664] System Configuration

[0665] This system consists of the following main components:

[0666] Each business system

[0667] Automated machinery

[0668] Client terminal

[0669] Central server

[0670] Email clients for managers

[0671] Generating and sending approval request emails

[0672] The server receives approval request information from each business system. This information includes task details and related information. Based on this information, the server generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, each with a one-time authentication token. The server then sends this approval request email to the manager's email address.

[0673] Processing of approvals and denials

[0674] When a manager clicks an approve or deny link in an email, the server receives the request. The server analyzes the authentication token from the request and verifies its validity. The server then sends the analysis result (approval or denial) to the relevant business system for specific approval or denial processing. If approved, the server instructs automated machines to execute the task.

[0675] Feedback and notifications

[0676] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[0677] Security and log management

[0678] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[0679] Hardware and software to be used

[0680] Hardware: Client terminals (personal computers, smartphones), central server, automated machinery (robots and automated devices)

[0681] Software: Mail server (e.g., Postfix), Python, database (e.g., MySQL), token generation library (token_generator)

[0682] Specific example

[0683] For example, if an automated machine ID is "12345" and a task ID is "56789" is to be executed, the server will send an approval request email to the administrator as follows:

[0684] Approval link: http: / / example.com / approve?token=abc123&task_id=56789&robot_id=12345

[0685] Denial link: http: / / example.com / deny?token=abc123&task_id=56789&robot_id=12345

[0686] Managers can approve or reject the task by clicking the link in this email.

[0687] Example of a prompt

[0688] "Automated machine ID '12345' is attempting to execute task ID '56789'. Please generate an approval request email and provide an approval link and a denial link."

[0689] This system allows managers to approve tasks efficiently and safely, and to smoothly advance automated processes within the factory.

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

[0691] Step 1:

[0692] The server receives approval request information from each business system. This information includes details of a specific task, the applicant, and the reason for the request. Input data includes, for example, the task ID, robot ID, and the request details. The server parses this information and formats it into the format required for the next processing step. The output is the formatted approval request information.

[0693] Step 2:

[0694] The server generates an approval request email based on the received approval request information. It uses an email template to embed task details and approval and rejection links. The input is the formatted approval request information, and the output is the generated approval request email. Specifically, it populates the data fields of the email template with the approval request information.

[0695] Step 3:

[0696] The server generates a one-time authentication token and attaches it to the accept and reject links. A token generation library is used to create a secure token. The input is the acceptance request email, and the output is the acceptance request email with the token embedded. Specifically, the generated token is appended to the URL of the link.

[0697] Step 4:

[0698] The server sends the generated approval request email to the administrator. It uses the SMTP protocol to deliver the email to the administrator's email address. The input is the approval request email with an embedded token, and the output is the transmission result. Specifically, this involves connecting to the mail server and sending the email.

[0699] Step 5:

[0700] When a manager clicks an approve or reject link, the server receives the request. The input is the request from the manager, and the output is the result of parsing the request. Specifically, the server extracts the token and task information from the request URL and verifies their validity.

[0701] Step 6:

[0702] The server performs approval or rejection processing based on the request. The input is the parsed request information, and the output is the processing result. Specifically, it notifies the business system whether or not the task can be executed.

[0703] Step 7:

[0704] The server notifies the manager of the approval or rejection result via feedback email. The input is the approval or rejection result, and the output is the feedback email. Specifically, the feedback email is generated and sent.

[0705] Step 8:

[0706] The server logs all approval and rejection actions and monitors them periodically. The input is each approval and rejection action, and the output is log data. Specifically, it writes to log files and periodically detects anomalies.

[0707] This series of processing steps allows managers to efficiently approve tasks for factory robots while also ensuring security and log management.

[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 combines an emotion engine with a system that allows managers to efficiently approve and reject requests via email, eliminating the need for them to individually log into each business system. Specific embodiments of this system are described below.

[0710] System Configuration Overview

[0711] The system of the present invention consists of the following components:

[0712] Various business systems (e.g., attendance systems, account management systems, business management systems)

[0713] Client terminal

[0714] Central server

[0715] Email clients for managers

[0716] Emotional Engine

[0717] Generating and sending approval request emails

[0718] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The terminal then sends this approval request email to the manager. Furthermore, the sentiment engine recognizes the manager's emotions and dynamically adjusts the email content as needed.

[0719] Specific example:

[0720] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[0721] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[0722] The emotion engine analyzes the manager's past emotional data and adds appropriate tone and suggestions to the email body.

[0723] The device will send this email to the administrator's email address.

[0724] Processing of approvals and denials

[0725] When a user (manager) clicks an approve or reject link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or rejection) to the relevant business system to perform the specific approval or rejection process. Furthermore, an emotion engine continuously monitors the manager's emotions and provides appropriate feedback if there is stress or dissatisfaction.

[0726] Specific example:

[0727] The user (administrator) clicks the approval link in the email.

[0728] The server receives the request and parses and verifies the authentication token included in the link.

[0729] The server sends a request to the attendance system saying, "This overtime request has been approved."

[0730] The emotion engine detects the manager's current emotions and sets an emotion flag in response to the processing request.

[0731] Feedback and notifications

[0732] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected). Additionally, the sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[0733] Specific example:

[0734] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[0735] The emotion engine analyzes the manager's emotions and adds messages such as, "Thank you for approving this. Let's discuss this at the next meeting," to the feedback email.

[0736] Security and log management

[0737] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[0738] Specific example:

[0739] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[0740] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[0741] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[0742] The following describes the processing flow.

[0743] Specific processing flow of the program

[0744] Generating and sending approval request emails

[0745] Step 1:

[0746] The terminal receives approval request information from each business system.

[0747] Specific operation: Retrieve data related to approval requests (e.g., applicant's name, application details, reason for application) from business systems via API requests. For example, receive overtime application information from the attendance system.

[0748] Step 2:

[0749] The terminal generates an approval request email based on the approval request information it has received.

[0750] Specific operation: Embed the received information into an email template and create the body of the approval request email. The template includes a basic format, and application information is inserted in the designated places.

[0751] Step 3:

[0752] The device embeds both an approval link and a denial link in the approval request email.

[0753] Specific operation: The link will be given a parameter containing a one-time authentication token, which will then be inserted into the email body. For example, HTML code for "Approve" and "Deny" buttons will be generated.

[0754] Step 4:

[0755] The emotion engine recognizes the emotions of managers and dynamically modifies the content of emails.

[0756] Specific actions: Analyze emotions based on past approval history and current status, and add appropriate tone and suggestions to the email body. For example, if a manager is feeling stressed, change the message to a more concise one.

[0757] Step 5:

[0758] The device sends an approval request email to the manager.

[0759] Specific operation: Send an email to the administrator's email address via the SMTP server. The sending log will also be recorded simultaneously.

[0760] Processing of approvals and denials

[0761] Step 6:

[0762] The user (administrator) clicks the approval or rejection link in the email.

[0763] Specific action: Click the approve or reject link in your email client, and your web browser will open the link.

[0764] Step 7:

[0765] The server receives the request when the link is clicked.

[0766] Specific operation: Receives an HTTP request and parses the parameters contained within it (such as authentication tokens and authorization IDs).

[0767] Step 8:

[0768] The server verifies the authentication token included in the link.

[0769] Specific actions: Check the expiration date and one-time use restriction of the authentication token and confirm that it is valid.

[0770] Step 9:

[0771] The server performs the approval or rejection process.

[0772] Specific example: Depending on the content of the request, an API request is sent to the corresponding business system to perform an approval or rejection operation.

[0773] Feedback and notifications

[0774] Step 10:

[0775] The server receives the approval or rejection result.

[0776] Specific operation: Receive API responses from business systems and analyze the results.

[0777] Step 11:

[0778] The emotion engine generates appropriate feedback email content based on the manager's emotions.

[0779] Specific actions: Dynamically change the tone and content of feedback emails by combining the approval or rejection result with the manager's sentiment data. For example, decide whether to add detailed guidance.

[0780] Step 12:

[0781] The server sends a feedback email to the manager.

[0782] Specific operation: Use the SMTP server to send the generated feedback email to the administrator's email address.

[0783] Security and log management

[0784] Step 13:

[0785] The server logs all approval and denial actions.

[0786] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[0787] Step 14:

[0788] The server periodically monitors logs and detects any anomalies.

[0789] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors. If an anomaly is detected, issue a warning.

[0790] Step 15:

[0791] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed.

[0792] Specific actions: Analyze emotional data and action logs to generate appropriate support messages for managers' emotional states.

[0793] In this way, the system of the present invention, which incorporates an emotion engine, allows managers to efficiently approve and reject requests via email without having to log into each business system. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[0794] (Example 2)

[0795] 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".

[0796] Traditional approval and rejection systems had drawbacks, including low efficiency due to the time and effort required for managers to log in to each business system individually to process requests. Furthermore, the systems relied solely on automated email notifications without considering the emotional state of managers, leading to increased stress and workload. Additionally, insufficient log management of approval and rejection actions raised security concerns.

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

[0798] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from the approval or rejection links clicked by the managers, means for performing approval or rejection processing based on the received requests, means for notifying the managers of the approval or rejection results via feedback email, means for analyzing the managers' past sentiment data and dynamically adjusting the email content, means for detecting the managers' current sentiment and providing appropriate feedback, means for generating authentication tokens included in the approval and rejection links and verifying the validity of the tokens, means for logging all approval and rejection actions by managers and periodically monitoring the logs to detect anomalies, and means for comparing log data and sentiment data and providing appropriate support messages. This eliminates the need for managers to log into each business system and enables efficient approval and rejection via email. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help reduce security risks.

[0799] "Each business system" refers to systems used for purposes such as attendance management, account management, and business management.

[0800] "Approval request information" refers to information used to request approval, such as the applicant's name, application details, reason for application, and application date and time.

[0801] An "approval request email" refers to an email generated based on approval request information and sent to a manager.

[0802] An "approval link" refers to a specific link embedded in an email that, when clicked by a manager, indicates their intention to approve the request.

[0803] A "denial link" refers to a specific link embedded in an email that, when clicked by a manager, indicates an intention to deny the work.

[0804] "Managerial position" refers to a person in a position that has the authority to approve or deny decisions.

[0805] A "request" refers to the request sent to the server when a manager clicks an approve or reject link.

[0806] An "authentication token" refers to a one-time-use identification piece of information included in the approve and deny links.

[0807] A "feedback email" refers to an email sent to a manager to notify them of the approval or rejection of a request.

[0808] The "emotion engine" refers to a function that analyzes managers' past emotional data and current emotional state to dynamically adjust email content and feedback.

[0809] "Logs" refer to records such as approval and rejection actions, date and time of operation, content, and the ID of the manager.

[0810] "Security monitoring" refers to the process of periodically analyzing log data to detect abnormal operations and security risks.

[0811] A "supportive message" refers to an appropriate message that the emotional engine provides when a manager may be experiencing stress or frustration.

[0812] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. This system incorporates an emotion engine to consider the manager's emotional state and reduce stress. Specific embodiments are described below.

[0813] System Configuration Overview

[0814] The system of the present invention consists of the following components:

[0815] Various business systems (e.g., attendance systems, account management systems, business management systems)

[0816] Client terminal

[0817] Central server

[0818] Email clients for managers

[0819] Emotional Engine

[0820] Hardware and software to be used

[0821] Client terminal: Receives approval request information from each business system, generates and sends approval request emails.

[0822] Central Server: Receives approval or denial requests from users and parses authentication tokens.

[0823] Manager's email client: Receives approval request emails and notifies the manager.

[0824] Emotion Engine: Analyzes the emotions of managers and provides functionality to dynamically adjust the tone and content of emails.

[0825] Various business systems: These include attendance management systems, account management systems, and business management systems, among others, that are subject to processing.

[0826] Generating and sending approval request emails

[0827] The terminal receives approval request information from various business systems. The received information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The sentiment engine analyzes the manager's past sentiment data and dynamically adjusts the email content. Next, the terminal sends this approval request email to the manager.

[0828] Specific example

[0829] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[0830] The terminal uses this information to generate an email saying, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[0831] The emotion engine adds messages such as, "Thank you for your approval. Let's discuss this matter at the next meeting."

[0832] The device will send this email to the administrator's email address.

[0833] Processing of approvals and denials

[0834] When a user (manager) clicks an approve or reject link in an email, the server receives the request and parses the authentication token contained in the link. After verifying the validity of the authentication token, the server sends the parsing result (approval or rejection) to the relevant business system and processes the specific approval or rejection. The sentiment engine detects the manager's current sentiment and provides appropriate feedback.

[0835] Specific example

[0836] The user (administrator) clicks the approval link in the email.

[0837] The server receives the request and parses and verifies the authentication token included in the link.

[0838] The server sends a request to the attendance system saying, "This overtime request has been approved."

[0839] The emotion engine detects the manager's current emotions and provides feedback such as, "Approval process complete."

[0840] Feedback and notifications

[0841] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes the approval or rejection result, along with details of the process (which applications were approved and which were rejected). The sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[0842] Specific example

[0843] The server generates an email stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[0844] The emotion engine adds the message, "Thank you for your approval. Let's discuss this matter at the next meeting."

[0845] The server will send this email to the administrator's email address.

[0846] Security and log management

[0847] The server logs all approval and rejection actions. The logs include the date and time of approval / rejection, the content of the approval / rejection, and the manager's ID. The server periodically monitors these logs to check for unusual activity or security risks. The sentiment engine compares past logs with current sentiment data to identify times when managers are particularly stressed and provides appropriate support messages.

[0848] Specific example

[0849] The server records all actions taken by administrators and analyzes the logs weekly to detect anomalies.

[0850] The emotion engine compares past logs with current emotion data to identify periods when managers are likely to be stressed. For example, if a tendency for stress to increase at the end of the month is detected, it will provide messages encouraging relaxation during that period.

[0851] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help to reduce security risks.

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

[0853] Step 1:

[0854] Receiving approval request information

[0855] The terminal receives approval request information from various business systems (e.g., attendance system, account management system).

[0856] Input: Applicant's name, application details, reason for application, date and time of application

[0857] Operation: Retrieves necessary information from the API or database of each business system.

[0858] Output: Approval request information data (Example: "Mr. Tanaka has requested 5 hours of overtime.")

[0859] Step 2:

[0860] Generating an approval request email

[0861] Based on the approval request information received by the device, an approval request email is generated using an email template.

[0862] Input: Approval request information data, email template

[0863] Function: Embed approval request information into email templates and generate and embed approval and rejection links.

[0864] Output: Generated approval request email (Example: "Mr. / Ms. Tanaka has requested 5 hours of overtime. Do you approve it?")

[0865] Step 3:

[0866] Adjusting and sending approval request emails

[0867] The emotion engine analyzes the manager's past emotional data and dynamically adjusts the content of emails.

[0868] Input: Generated approval request email, historical sentiment data

[0869] Function: The emotion engine adjusts the tone and content of the email (e.g., adds words of encouragement).

[0870] Output: Adjusted approval request email

[0871] The device sends this adjusted approval request email to the manager.

[0872] Operation: Sends emails using a mail server.

[0873] Output: Approval request email sent to manager completed.

[0874] Step 4:

[0875] Receiving an approval or rejection request

[0876] The user (administrator) clicks the approval or rejection link in the email.

[0877] Input: Clicking an approve or disapprove link

[0878] Operation: The server receives clicks from the administrator.

[0879] Output: Request data (e.g., click on an approval link)

[0880] Step 5:

[0881] Analysis of authentication tokens

[0882] The server parses the authentication token from the received request.

[0883] Input: Request data, authentication token

[0884] Function: Validates the token and verifies the legitimacy of the request.

[0885] Output: Authentication result (authentication successful or failed)

[0886] Step 6:

[0887] Performing an approval or denial process

[0888] The server sends a processing request to the relevant business system based on the authentication result, and then performs the specific approval or denial process.

[0889] Input: Authentication results, business system data

[0890] Operation: Calls the API of the relevant business system and performs the approval or denial process.

[0891] Output: Processing result (Example: "Overtime request has been approved.")

[0892] The emotion engine detects the manager's current emotions and provides appropriate feedback.

[0893] Input: Current sentiment data of managers

[0894] Operation: Generates feedback content based on emotional data.

[0895] Output: Feedback message

[0896] Step 7:

[0897] Generating and sending feedback emails

[0898] The server generates and sends an email to the manager to provide feedback that the approval or rejection process is complete.

[0899] Input: Processing result data, feedback message

[0900] Operation: Generates a feedback email and sends it using the mail server.

[0901] Output: Feedback email sent to managers completed.

[0902] Step 8:

[0903] Log management and security monitoring

[0904] The server logs all approval and denial actions.

[0905] Input: Approval and denial action data

[0906] Operation: Records operation data to a log file.

[0907] Output: Log file update

[0908] The server periodically monitors logs to check for unusual operations and security risks.

[0909] Input: Log data

[0910] Function: Log data analysis and anomaly detection

[0911] Output: Anomaly detection message

[0912] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[0913] Input: Log data, current sentiment data

[0914] Operation: Comparative analysis of emotion data and log data

[0915] Output: Support message

[0916] (Application Example 2)

[0917] 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."

[0918] Currently, factory managers must log into each business system individually and manually process approvals and rejections. This process is time-consuming and labor-intensive, further increasing manager stress. Furthermore, the lack of consideration for managers' emotional states can hinder efficient work. Additionally, the slow provision of feedback on approval and rejection results reduces overall work efficiency.

[0919] In Application Example 2, the specific processing performed by the specific processing unit 290 of the data processing device 12 is realized by the following means. In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval links and rejection links in the generated approval request emails, means for sending the approval request emails to managers, emotion engine means for recognizing the emotions of managers and dynamically adjusting the email content as needed, means for receiving requests from approval or rejection links clicked by managers, means for executing approval or rejection processing based on the received requests, and means for notifying managers of the approval or rejection result via feedback email. As a result, managers can efficiently approve or reject requests via email without having to log in to individual business systems. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to improved work efficiency and reduced stress.

[0920] "Each business system" refers to systems that process various types of information related to business operations, such as attendance management systems and work instruction systems within a factory.

[0921] "Approval request information" refers to information that includes the details of employee applications for work permits and attendance records.

[0922] An "approval request email" is an email generated based on approval request information and sent to a manager.

[0923] "Approval and rejection links" are links embedded in approval request emails that, when clicked by a manager, send an approval or rejection notification to the server.

[0924] A "manager" is a person in a position of responsibility who is in charge of supervising factory operations and attendance.

[0925] An "emotional engine" is a system that recognizes the emotional state of managers and provides appropriate feedback and dynamic message adjustments based on those emotions.

[0926] A "request" is a request sent to the server after clicking an accept or reject link.

[0927] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[0928] The system for implementing this invention consists of various business systems, client terminals, a central server, an email client for managers, and an emotion engine.

[0929] Each business system processes information related to factory operations, such as attendance management systems and work instruction systems, and generates approval request information. This approval request information includes the applicant's name, application details, reason for application, and application date and time.

[0930] The client terminal receives approval request information from each business system and generates an approval request email using a pre-prepared email template. This email contains embedded approval and rejection links and is issued with a one-time authentication token. The generated email is sent to the manager's email address.

[0931] The emotion engine recognizes the emotions of managers and dynamically adjusts email content by analyzing past emotional data. By adding appropriate tone and suggestions to the email body, it enables communication that takes the manager's emotional state into consideration.

[0932] When a manager clicks an approve or reject link in an email, the central server receives the request. The server parses and verifies the authentication token included in the request and then sends the approval or rejection decision to the relevant business system.

[0933] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes details of the approval or rejection process, and the sentiment engine adds appropriate messages to show consideration for the manager.

[0934] Let's illustrate the operation of the entire system with an example. For instance, consider a scenario where a manager is wearing smart glasses. When this manager receives an email, it displays the message, "Employee A has requested 4 hours of overtime. Do you approve it?" along with links to approve and deny the request. If the manager clicks the approve link, the server receives the request and processes the approval in the relevant business system. The emotion engine analyzes the manager's emotions and generates a feedback email, including an additional message such as, "Thank you for approving. Let's discuss this at the next meeting," and sends it to the manager.

[0935] By using a generative AI model, the emotion engine analyzes managers' past emotional data and dynamically adjusts messages. This leads to increased work efficiency and reduced stress for managers.

[0936] Example of a prompt:

[0937] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[0938] In this way, the system of this invention enables factory managers to approve and reject items quickly and efficiently, ensuring smooth operations and providing responses that take into account the emotional state of managers.

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

[0940] Step 1:

[0941] Each business system generates approval request information, such as work requests and attendance requests, and sends it to the client terminal. Input includes employee name, request details, reason for request, and date and time of request. The client terminal receives this information as output.

[0942] Step 2:

[0943] The terminal generates an approval request email using a pre-prepared email template based on the received approval request information. The input is the approval request information received in Step 1. As data processing, the information is embedded into the template and the email body is generated. The output is the generated approval request email.

[0944] Step 3:

[0945] The device embeds an approval link and a denial link in the generated approval request email. The input is the approval request email generated in step 2. As data processing, a one-time authentication token is generated and attached to the link. The output is the approval request email with the links embedded.

[0946] Step 4:

[0947] The emotion engine recognizes the manager's emotions and dynamically adjusts the email content based on past emotion data. The inputs are the manager's past emotion data and the email generated in step 3. The data calculation adjusts the message according to the manager's emotions. The output is the adjusted approval request email.

[0948] Step 5:

[0949] The terminal sends a pre-configured approval request email to the manager. The inputs are the pre-configured approval request email from step 4 and the manager's email address. The output is the approval request email sent to the manager.

[0950] Step 6:

[0951] A manager clicks an approve or reject link in an email and sends the request to the server. Inputs include the manager's click action and the authentication token contained within the link. Outputs include the request sent to the server.

[0952] Step 7:

[0953] The server parses the received request and verifies the validity of the authentication token included in the link. The inputs are the request and authentication token received in step 6. The data operation involves parsing and verifying the authentication token. The output is the result of the approval or denial process.

[0954] Step 8:

[0955] The server sends the approval or rejection decision to the relevant business system. The input is the processing result obtained in step 7. The output is the approval or rejection request sent to the business system.

[0956] Step 9:

[0957] The server notifies the manager of the approval or rejection result via feedback email. The emotion engine then recognizes the manager's emotions again and dynamically adjusts the content of the feedback email. The inputs are the result processed in step 8 and the manager's current emotional state. The data processing involves generating and adjusting the content of the feedback email. The output is the feedback email sent to the manager.

[0958] As a concrete example, consider a scenario where a manager uses smart glasses to perform an approval process. Enter the following prompt into the generative AI model:

[0959] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[0960] Based on this prompt, the emotion engine makes appropriate adjustments and provides feedback to reduce stress for managers and improve work efficiency.

[0961] 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.

[0962] 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.

[0963] 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.

[0964] [Third Embodiment]

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

[0966] 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.

[0967] 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).

[0968] 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.

[0969] 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.

[0970] 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).

[0971] 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.

[0972] 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.

[0973] 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.

[0974] 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.

[0975] 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.

[0976] 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".

[0977] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[0978] System Configuration Overview

[0979] The system of the present invention consists of the following components:

[0980] Various business systems (e.g., attendance systems, account management systems, business management systems)

[0981] Client terminal

[0982] Central server

[0983] Email clients for managers

[0984] Generating and sending approval request emails

[0985] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. Next, the terminal sends this approval request email to the manager.

[0986] Specific example:

[0987] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[0988] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[0989] The device will send this email to the administrator's email address.

[0990] Processing of approvals and denials

[0991] When a user (manager) clicks an approve or deny link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or denial) to the relevant business system to perform the specific approval or denial process.

[0992] Specific example:

[0993] The user (administrator) clicks the approval link in the email.

[0994] The server receives the request and parses and verifies the authentication token included in the link.

[0995] The server sends a request to the attendance system saying, "This overtime request has been approved."

[0996] Feedback and notifications

[0997] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected).

[0998] Specific example:

[0999] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[1000] Security and log management

[1001] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[1002] Specific example:

[1003] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[1004] In this way, the system of the present invention streamlines the approval and rejection processes and reduces the burden on managers. Furthermore, the system's security is ensured through advanced security measures.

[1005] The following describes the processing flow.

[1006] Program processing flow

[1007] Generating and sending approval request emails

[1008] Step 1:

[1009] The terminal receives approval request information from each business system.

[1010] Specific operation: Retrieve data related to approval requests from business systems via API requests. For example, receive employee overtime application information from the attendance system.

[1011] Step 2:

[1012] The terminal generates an approval request email based on the approval request information it has received.

[1013] Specific actions: The system will embed the received information (applicant's name, application details, reason for application, application date and time, etc.) into an email template and create the email body.

[1014] Step 3:

[1015] The device embeds both an approval link and a denial link in the approval request email.

[1016] Specific operation: The link will be given a parameter containing a one-time authentication token, which will then be inserted into the email body.

[1017] Step 4:

[1018] The device sends an approval request email to the manager.

[1019] Specific operation: Send an email to the administrator's email address via the SMTP server.

[1020] Processing of approvals and denials

[1021] Step 5:

[1022] The user (administrator) clicks the approval or rejection link in the email.

[1023] Specific operation: The manager clicks an approve or reject link in their email client, and the web browser automatically opens the link.

[1024] Step 6:

[1025] The server receives the request when the link is clicked.

[1026] Specific operation: Receives an HTTP request and parses the parameters contained within it (such as authentication tokens and authorization IDs).

[1027] Step 7:

[1028] The server verifies the authentication token included in the link.

[1029] Specific actions: Check the expiration date and one-time use restriction of the authentication token and confirm that it is valid.

[1030] Step 8:

[1031] The server performs the approval or rejection process.

[1032] Specific operation: Depending on the content of the request, an API request is sent to the corresponding business system to perform an approval or rejection operation.

[1033] Feedback and notifications

[1034] Step 9:

[1035] The server receives the approval or rejection result.

[1036] Specific operation: Receive API responses from business systems and analyze the results.

[1037] Step 10:

[1038] The server generates a feedback email for the manager.

[1039] Specific action: Based on the approval or rejection result, create the body of the feedback email.

[1040] Step 11:

[1041] The server sends a feedback email to the manager.

[1042] Specific operation: Send a feedback email to the administrator's email address via the SMTP server.

[1043] Security and log management

[1044] Step 12:

[1045] The server logs all approval and denial actions.

[1046] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[1047] Step 13:

[1048] The server periodically monitors logs and detects any anomalies.

[1049] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors.

[1050] The above is a specific processing flow for a system that allows managers to efficiently approve and reject items using email.

[1051] (Example 1)

[1052] 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."

[1053] The goal is to reduce the effort required for managers to individually log into each business system to approve and reject decisions, thereby streamlining the approval process, while also preventing unauthorized operations and security risks through advanced security measures.

[1054] 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.

[1055] In this invention, the server includes means for receiving approval request information from each information processing system, means for generating an approval request electronic message based on the received approval request information, means for embedding approval links and denial links in the generated approval request electronic message, means for sending the approval request electronic message to an administrator, means for receiving requests from approval links or denial links clicked by the administrator, means for performing approval or denial processing based on the received requests, means for notifying the administrator of the approval or denial result via a feedback electronic message, means for recording all approval and denial actions, monitoring them periodically to detect anomalies, means for generating authentication data included in the approval and denial links and verifying the validity of the authentication data, and means for periodically monitoring the recorded data to detect abnormal operations or security risks. This enables administrators to efficiently perform approval and denial operations without individually logging into business systems, while also improving security.

[1056] An "information processing system" is a system that includes software and hardware for managing and executing all aspects of business operations.

[1057] "Approval request information" refers to information that includes applicant information and other necessary data used to request approval for a specific action or operation within the system.

[1058] An "approval request electronic message" is a message in email format that is generated based on approval request information.

[1059] An "approval link" is a link included in an electronic message requesting approval; clicking it initiates the approval process.

[1060] A "denial link" is a link included in an electronic message requesting approval, and clicking it will initiate the denial process.

[1061] "Authentication data" refers to a one-time token or key embedded in an approve or deny link and used to verify its validity.

[1062] An "administrator" is a user who has the authority to perform the system's approval and rejection processes, and is typically someone in a management position.

[1063] A "feedback electronic message" is a message in the form of an email that notifies the administrator of the outcome of the approval or rejection process.

[1064] A "request" is the request information sent to the server when an administrator clicks an approve or reject link.

[1065] A "log" is a history of data used to record all approval and rejection actions performed within a system.

[1066] This invention provides a system that eliminates the need for administrators to individually log in to each information processing system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[1067] System Configuration

[1068] This system consists of the following components:

[1069] Information processing systems (e.g., attendance management systems, account management systems)

[1070] Client terminal

[1071] Central server

[1072] Administrator's email client

[1073] Receiving approval request information

[1074] The terminal receives approval request information from each information processing system. This information includes the applicant's name, application details, reason for application, and date and time of application.

[1075] Generating an approval request email

[1076] Based on the received approval request information, the terminal generates an electronic approval request message using a pre-prepared email template. This electronic message contains embedded approval and denial links, and these links are associated with one-time authentication data.

[1077] Sending an approval request email

[1078] The terminal generates an electronic approval request message which is then sent to the administrator via email.

[1079] Receiving and parsing requests

[1080] When a user (administrator) clicks an approval or denial link included in an email, the server receives a click request. The server analyzes the authentication data from the received click request and verifies its validity.

[1081] Processing of approval or denial

[1082] The server sends the analysis results (approval or rejection) to the relevant information processing system, which then performs the specific approval or rejection process. For example, it might send a request to the attendance management system stating, "This overtime request has been approved."

[1083] Feedback notification

[1084] Once the approval or rejection process is complete, the server generates and sends an electronic feedback message to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[1085] Log management and security

[1086] The server logs all approval and denial actions. This log includes the date and time of approval / denial, the content of the approval / denial, and the administrator's ID. The server also periodically monitors these logs to check for unusual operations or security risks.

[1087] Examples of specific cases and prompt statements

[1088] Specific example

[1089] 1. The terminal receives information from the attendance management system stating, "An employee has requested 5 hours of overtime." This information includes the employee's name, details of the overtime request, reason for the request, and date and time of the request.

[1090] 2. Based on the information received by the terminal, an electronic approval request message is generated with the message, "An employee has requested 5 hours of overtime. Do you approve it?" This electronic message contains both an approval link and a denial link, and each link is associated with authentication data.

[1091] 3. The terminal sends the generated approval request electronic message to the administrator's email address.

[1092] 4. When the user (administrator) clicks the "approval link" in the email, the server receives the request and parses and verifies the authentication data contained in the link.

[1093] 5. The server sends a request to the attendance management system stating, "The employee's request for 5 hours of overtime has been approved."

[1094] 6. The server generates and sends an electronic feedback message to the administrator stating, "The employee's request for 5 hours of overtime has been approved."

[1095] 7. The server logs all approval and rejection actions and periodically monitors the logs to detect anomalies.

[1096] Example of a prompt

[1097] "An employee has requested 5 hours of overtime. Do you approve it?"

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

[1099] Step 1: Receiving approval request information

[1100] The terminal receives approval request information from the information processing system. The input consists of data such as the applicant's name, application details, reason for application, and application date and time, which are transmitted from the information processing system. The terminal acquires and records this data, converting it into a format usable in the next processing step.

[1101] Step 2: Generating the approval request email

[1102] The terminal generates an electronic approval request message using an email template based on the received approval request information. This generation process embeds the input data (applicant's name, application details, reason for application, application date and time, etc.) into the template, outputting an email message containing approval and rejection links. Each link is accompanied by one-time authentication data.

[1103] Step 3: Sending the approval request email

[1104] The terminal sends the generated approval request electronic message to the administrator's email address. The input is the generated email and the administrator's email address, and the output is the approval request email received in the administrator's email client.

[1105] Step 4: Click the approve or reject link.

[1106] The user (administrator) clicks an approve or reject link included in the email. The input is the link selected by the administrator (approve or reject), and the output is that the click request is sent to the server. At this point, a browser opens and the request is sent.

[1107] Step 5: Analysis and verification of the authentication token

[1108] The server analyzes the received click request and verifies the validity of the authentication data contained in the link. The input is the authentication data contained in the click request, and the output is the verification result of whether or not that data is valid. The server checks the validity of the authentication data and proceeds to the next processing step.

[1109] Step 6: Sending a request to the business system

[1110] The server sends the analysis result (approval or denial) as a request to the relevant information processing system for specific processing. The input is the verification result of the authentication data and the content of approval or denial, and the output is the request sent to the information processing system (for example, "This overtime request has been approved"). The information processing system receives this request and updates the database.

[1111] Step 7: Generate and send the feedback email.

[1112] The server generates and sends an electronic feedback message to the administrator based on the approval or rejection result. The input is the processing result (approval or rejection), and the output is a feedback email. This email contains the approval or rejection result and details.

[1113] Step 8: Logging and Monitoring

[1114] The server logs all approval and denial actions and monitors them regularly to detect anomalies. The input is the details of each operation (e.g., date and time, content, administrator ID), and the output is the recorded log data. The server periodically monitors these logs to detect unusual operations and security risks.

[1115] (Application Example 1)

[1116] 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."

[1117] In factories and other manufacturing sites, approval from managers is often required before various tasks can be performed. This includes situations where human judgment is needed before certain tasks (e.g., production line adjustments or maintenance work) can be carried out. However, with conventional systems, managers must log in to multiple business systems individually and perform the approval process manually, resulting in wasted time and effort. Furthermore, in addition to streamlining the approval process, there is a need to ensure security and log management. This invention aims to solve these problems and streamline the approval process for tasks performed within factories.

[1118] 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.

[1119] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from approval or rejection links clicked by managers, means for performing approval or rejection processing based on the received requests, means for feeding back the approval or rejection results to the business system and instructing whether to proceed, means for notifying managers of the approval or rejection results via feedback email, means for obtaining manager approval before the task is executed by the automated machine, and means for the automated machine to execute the approved task. As a result, managers can efficiently perform task approval work, and business processes within the factory are automated. Furthermore, security is improved and log management is also achieved, improving the reliability of the entire system.

[1120] "Each business system" refers to a system used in factories and manufacturing sites to manage various business processes such as attendance management, account management, and work management.

[1121] "Approval request information" refers to information used to seek approval from a manager in order to perform a specific task or action, and includes the applicant's name, the content of the request, the reason for the request, and the date and time of the request.

[1122] An "approval request email" is an email generated based on approval request information and sent to a manager, containing both an approval link and a rejection link.

[1123] An "approval link" is a link embedded in an approval request email that, when clicked, allows the user to approve a specific task or action.

[1124] A "denial link" is a link embedded in an approval request email that, when clicked, allows the user to deny a specific task or action.

[1125] A "manager" is a person in a position of authority who has the authority to approve the implementation of tasks and actions in a factory or manufacturing site.

[1126] A "request" is a request sent to the server when an administrator clicks an approve or reject link.

[1127] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[1128] "Automated machinery" refers to robots and automated devices used to perform specific tasks in factories and manufacturing sites.

[1129] A "token" is a one-time authentication code included in the accept and reject links, used to verify its validity.

[1130] A "log" is data used to record all approval and rejection actions by managers.

[1131] An "anomaly" refers to unusual operations or security risks detected during the process of monitoring logs.

[1132] This invention provides a system that allows managers to efficiently approve or reject specific tasks before they are performed by automated machines in factories or manufacturing sites. Specific embodiments thereof are described below.

[1133] System Configuration

[1134] This system consists of the following main components:

[1135] Each business system

[1136] Automated machinery

[1137] Client terminal

[1138] Central server

[1139] Email clients for managers

[1140] Generating and sending approval request emails

[1141] The server receives approval request information from each business system. This information includes task details and related information. Based on this information, the server generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, each with a one-time authentication token. The server then sends this approval request email to the manager's email address.

[1142] Processing of approvals and denials

[1143] When a manager clicks an approve or deny link in an email, the server receives the request. The server analyzes the authentication token from the request and verifies its validity. The server then sends the analysis result (approval or denial) to the relevant business system for specific approval or denial processing. If approved, the server instructs automated machines to execute the task.

[1144] Feedback and notifications

[1145] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[1146] Security and log management

[1147] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[1148] Hardware and software to be used

[1149] Hardware: Client terminals (personal computers, smartphones), central server, automated machinery (robots and automated devices)

[1150] Software: Mail server (e.g., Postfix), Python, database (e.g., MySQL), token generation library (token_generator)

[1151] Specific example

[1152] For example, if an automated machine ID is "12345" and a task ID is "56789" is to be executed, the server will send an approval request email to the administrator as follows:

[1153] Approval link: http: / / example.com / approve?token=abc123&task_id=56789&robot_id=12345

[1154] Denial link: http: / / example.com / deny?token=abc123&task_id=56789&robot_id=12345

[1155] Managers can approve or reject the task by clicking the link in this email.

[1156] Example of a prompt

[1157] "Automated machine ID '12345' is attempting to execute task ID '56789'. Please generate an approval request email and provide an approval link and a denial link."

[1158] This system allows managers to approve tasks efficiently and safely, and to smoothly advance automated processes within the factory.

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

[1160] Step 1:

[1161] The server receives approval request information from each business system. This information includes details of a specific task, the applicant, and the reason for the request. Input data includes, for example, the task ID, robot ID, and the request details. The server parses this information and formats it into the format required for the next processing step. The output is the formatted approval request information.

[1162] Step 2:

[1163] The server generates an approval request email based on the received approval request information. It uses an email template to embed task details and approval and rejection links. The input is the formatted approval request information, and the output is the generated approval request email. Specifically, it populates the data fields of the email template with the approval request information.

[1164] Step 3:

[1165] The server generates a one-time authentication token and attaches it to the accept and reject links. A token generation library is used to create a secure token. The input is the acceptance request email, and the output is the acceptance request email with the token embedded. Specifically, the generated token is appended to the URL of the link.

[1166] Step 4:

[1167] The server sends the generated approval request email to the administrator. It uses the SMTP protocol to deliver the email to the administrator's email address. The input is the approval request email with an embedded token, and the output is the transmission result. Specifically, this involves connecting to the mail server and sending the email.

[1168] Step 5:

[1169] When a manager clicks an approve or reject link, the server receives the request. The input is the request from the manager, and the output is the result of parsing the request. Specifically, the server extracts the token and task information from the request URL and verifies their validity.

[1170] Step 6:

[1171] The server performs approval or rejection processing based on the request. The input is the parsed request information, and the output is the processing result. Specifically, it notifies the business system whether or not the task can be executed.

[1172] Step 7:

[1173] The server notifies the manager of the approval or rejection result via feedback email. The input is the approval or rejection result, and the output is the feedback email. Specifically, the feedback email is generated and sent.

[1174] Step 8:

[1175] The server logs all approval and rejection actions and monitors them periodically. The input is each approval and rejection action, and the output is log data. Specifically, it writes to log files and periodically detects anomalies.

[1176] This series of processing steps allows managers to efficiently approve tasks for factory robots while also ensuring security and log management.

[1177] 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.

[1178] This invention combines an emotion engine with a system that allows managers to efficiently approve and reject requests via email, eliminating the need for them to individually log into each business system. Specific embodiments of this system are described below.

[1179] System Configuration Overview

[1180] The system of the present invention consists of the following components:

[1181] Various business systems (e.g., attendance systems, account management systems, business management systems)

[1182] Client terminal

[1183] Central server

[1184] Email clients for managers

[1185] Emotional Engine

[1186] Generating and sending approval request emails

[1187] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The terminal then sends this approval request email to the manager. Furthermore, the sentiment engine recognizes the manager's emotions and dynamically adjusts the email content as needed.

[1188] Specific example:

[1189] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[1190] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[1191] The emotion engine analyzes the manager's past emotional data and adds appropriate tone and suggestions to the email body.

[1192] The device will send this email to the administrator's email address.

[1193] Processing of approvals and denials

[1194] When a user (manager) clicks an approve or reject link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or rejection) to the relevant business system to perform the specific approval or rejection process. Furthermore, an emotion engine continuously monitors the manager's emotions and provides appropriate feedback if there is stress or dissatisfaction.

[1195] Specific example:

[1196] The user (administrator) clicks the approval link in the email.

[1197] The server receives the request and parses and verifies the authentication token included in the link.

[1198] The server sends a request to the attendance system saying, "This overtime request has been approved."

[1199] The emotion engine detects the manager's current emotions and sets an emotion flag in response to the processing request.

[1200] Feedback and notifications

[1201] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected). Additionally, the sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[1202] Specific example:

[1203] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[1204] The emotion engine analyzes the manager's emotions and adds messages such as, "Thank you for approving this. Let's discuss this at the next meeting," to the feedback email.

[1205] Security and log management

[1206] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[1207] Specific example:

[1208] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[1209] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[1210] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[1211] The following describes the processing flow.

[1212] Specific processing flow of the program

[1213] Generating and sending approval request emails

[1214] Step 1:

[1215] The terminal receives approval request information from each business system.

[1216] Specific operation: Retrieve data related to approval requests (e.g., applicant's name, application details, reason for application) from business systems via API requests. For example, receive overtime application information from the attendance system.

[1217] Step 2:

[1218] The terminal generates an approval request email based on the approval request information it has received.

[1219] Specific operation: Embed the received information into an email template and create the body of the approval request email. The template includes a basic format, and application information is inserted in the designated places.

[1220] Step 3:

[1221] The device embeds both an approval link and a denial link in the approval request email.

[1222] Specific operation: The link will be given a parameter containing a one-time authentication token, which will then be inserted into the email body. For example, HTML code for "Approve" and "Deny" buttons will be generated.

[1223] Step 4:

[1224] The emotion engine recognizes the emotions of managers and dynamically modifies the content of emails.

[1225] Specific actions: Analyze emotions based on past approval history and current status, and add appropriate tone and suggestions to the email body. For example, if a manager is feeling stressed, change the message to a more concise one.

[1226] Step 5:

[1227] The device sends an approval request email to the manager.

[1228] Specific operation: Send an email to the administrator's email address via the SMTP server. The sending log will also be recorded simultaneously.

[1229] Processing of approvals and denials

[1230] Step 6:

[1231] The user (administrator) clicks the approval or rejection link in the email.

[1232] Specific action: Click the approve or reject link in your email client, and your web browser will open the link.

[1233] Step 7:

[1234] The server receives the request when the link is clicked.

[1235] Specific operation: Receives an HTTP request and parses the parameters contained within it (such as authentication tokens and authorization IDs).

[1236] Step 8:

[1237] The server verifies the authentication token included in the link.

[1238] Specific actions: Check the expiration date and one-time use restriction of the authentication token and confirm that it is valid.

[1239] Step 9:

[1240] The server performs the approval or rejection process.

[1241] Specific example: Depending on the content of the request, an API request is sent to the corresponding business system to perform an approval or rejection operation.

[1242] Feedback and notifications

[1243] Step 10:

[1244] The server receives the approval or rejection result.

[1245] Specific operation: Receive API responses from business systems and analyze the results.

[1246] Step 11:

[1247] The emotion engine generates appropriate feedback email content based on the manager's emotions.

[1248] Specific actions: Dynamically change the tone and content of feedback emails by combining the approval or rejection result with the manager's sentiment data. For example, decide whether to add detailed guidance.

[1249] Step 12:

[1250] The server sends a feedback email to the manager.

[1251] Specific operation: Use the SMTP server to send the generated feedback email to the administrator's email address.

[1252] Security and log management

[1253] Step 13:

[1254] The server logs all approval and denial actions.

[1255] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[1256] Step 14:

[1257] The server periodically monitors logs and detects any anomalies.

[1258] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors. If an anomaly is detected, issue a warning.

[1259] Step 15:

[1260] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed.

[1261] Specific actions: Analyze emotional data and action logs to generate appropriate support messages for managers' emotional states.

[1262] In this way, the system of the present invention, which incorporates an emotion engine, allows managers to efficiently approve and reject requests via email without having to log into each business system. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[1263] (Example 2)

[1264] 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."

[1265] Traditional approval and rejection systems had drawbacks, including low efficiency due to the time and effort required for managers to log in to each business system individually to process requests. Furthermore, the systems relied solely on automated email notifications without considering the emotional state of managers, leading to increased stress and workload. Additionally, insufficient log management of approval and rejection actions raised security concerns.

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

[1267] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from the approval or rejection links clicked by the managers, means for performing approval or rejection processing based on the received requests, means for notifying the managers of the approval or rejection results via feedback email, means for analyzing the managers' past sentiment data and dynamically adjusting the email content, means for detecting the managers' current sentiment and providing appropriate feedback, means for generating authentication tokens included in the approval and rejection links and verifying the validity of the tokens, means for logging all approval and rejection actions by managers and periodically monitoring the logs to detect anomalies, and means for comparing log data and sentiment data and providing appropriate support messages. This eliminates the need for managers to log into each business system and enables efficient approval and rejection via email. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help reduce security risks.

[1268] "Each business system" refers to systems used for purposes such as attendance management, account management, and business management.

[1269] "Approval request information" refers to information used to request approval, such as the applicant's name, application details, reason for application, and application date and time.

[1270] An "approval request email" refers to an email generated based on approval request information and sent to a manager.

[1271] An "approval link" refers to a specific link embedded in an email that, when clicked by a manager, indicates their intention to approve the request.

[1272] A "denial link" refers to a specific link embedded in an email that, when clicked by a manager, indicates an intention to deny the work.

[1273] "Managerial position" refers to a person in a position that has the authority to approve or deny decisions.

[1274] A "request" refers to the request sent to the server when a manager clicks an approve or reject link.

[1275] An "authentication token" refers to a one-time-use identification piece of information included in the approve and deny links.

[1276] A "feedback email" refers to an email sent to a manager to notify them of the approval or rejection of a request.

[1277] The "emotion engine" refers to a function that analyzes managers' past emotional data and current emotional state to dynamically adjust email content and feedback.

[1278] "Logs" refer to records such as approval and rejection actions, date and time of operation, content, and the ID of the manager.

[1279] "Security monitoring" refers to the process of periodically analyzing log data to detect abnormal operations and security risks.

[1280] A "supportive message" refers to an appropriate message that the emotional engine provides when a manager may be experiencing stress or frustration.

[1281] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. This system incorporates an emotion engine to consider the manager's emotional state and reduce stress. Specific embodiments are described below.

[1282] System Configuration Overview

[1283] The system of the present invention consists of the following components:

[1284] Various business systems (e.g., attendance systems, account management systems, business management systems)

[1285] Client terminal

[1286] Central server

[1287] Email clients for managers

[1288] Emotional Engine

[1289] Hardware and software to be used

[1290] Client terminal: Receives approval request information from each business system, generates and sends approval request emails.

[1291] Central Server: Receives approval or denial requests from users and parses authentication tokens.

[1292] Manager's email client: Receives approval request emails and notifies the manager.

[1293] Emotion Engine: Analyzes the emotions of managers and provides functionality to dynamically adjust the tone and content of emails.

[1294] Various business systems: These include attendance management systems, account management systems, and business management systems, among others, that are subject to processing.

[1295] Generating and sending approval request emails

[1296] The terminal receives approval request information from various business systems. The received information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The sentiment engine analyzes the manager's past sentiment data and dynamically adjusts the email content. Next, the terminal sends this approval request email to the manager.

[1297] Specific example

[1298] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[1299] The terminal uses this information to generate an email saying, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[1300] The emotion engine adds messages such as, "Thank you for your approval. Let's discuss this matter at the next meeting."

[1301] The device will send this email to the administrator's email address.

[1302] Processing of approvals and denials

[1303] When a user (manager) clicks an approve or reject link in an email, the server receives the request and parses the authentication token contained in the link. After verifying the validity of the authentication token, the server sends the parsing result (approval or rejection) to the relevant business system and processes the specific approval or rejection. The sentiment engine detects the manager's current sentiment and provides appropriate feedback.

[1304] Specific example

[1305] The user (administrator) clicks the approval link in the email.

[1306] The server receives the request and parses and verifies the authentication token included in the link.

[1307] The server sends a request to the attendance system saying, "This overtime request has been approved."

[1308] The emotion engine detects the manager's current emotions and provides feedback such as, "Approval process complete."

[1309] Feedback and notifications

[1310] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes the approval or rejection result, along with details of the process (which applications were approved and which were rejected). The sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[1311] Specific example

[1312] The server generates an email stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[1313] The emotion engine adds the message, "Thank you for your approval. Let's discuss this matter at the next meeting."

[1314] The server will send this email to the administrator's email address.

[1315] Security and log management

[1316] The server logs all approval and rejection actions. The logs include the date and time of approval / rejection, the content of the approval / rejection, and the manager's ID. The server periodically monitors these logs to check for unusual activity or security risks. The sentiment engine compares past logs with current sentiment data to identify times when managers are particularly stressed and provides appropriate support messages.

[1317] Specific example

[1318] The server records all actions taken by administrators and analyzes the logs weekly to detect anomalies.

[1319] The emotion engine compares past logs with current emotion data to identify periods when managers are likely to be stressed. For example, if a tendency for stress to increase at the end of the month is detected, it will provide messages encouraging relaxation during that period.

[1320] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help to reduce security risks.

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

[1322] Step 1:

[1323] Receiving approval request information

[1324] The terminal receives approval request information from various business systems (e.g., attendance system, account management system).

[1325] Input: Applicant's name, application details, reason for application, date and time of application

[1326] Operation: Retrieves necessary information from the API or database of each business system.

[1327] Output: Approval request information data (Example: "Mr. Tanaka has requested 5 hours of overtime.")

[1328] Step 2:

[1329] Generating an approval request email

[1330] Based on the approval request information received by the device, an approval request email is generated using an email template.

[1331] Input: Approval request information data, email template

[1332] Function: Embed approval request information into email templates and generate and embed approval and rejection links.

[1333] Output: Generated approval request email (Example: "Mr. / Ms. Tanaka has requested 5 hours of overtime. Do you approve it?")

[1334] Step 3:

[1335] Adjusting and sending approval request emails

[1336] The emotion engine analyzes the manager's past emotional data and dynamically adjusts the content of emails.

[1337] Input: Generated approval request email, historical sentiment data

[1338] Function: The emotion engine adjusts the tone and content of the email (e.g., adds words of encouragement).

[1339] Output: Adjusted approval request email

[1340] The device sends this adjusted approval request email to the manager.

[1341] Operation: Sends emails using a mail server.

[1342] Output: Approval request email sent to manager completed.

[1343] Step 4:

[1344] Receiving an approval or rejection request

[1345] The user (administrator) clicks the approval or rejection link in the email.

[1346] Input: Clicking an approve or disapprove link

[1347] Operation: The server receives clicks from the administrator.

[1348] Output: Request data (e.g., click on an approval link)

[1349] Step 5:

[1350] Analysis of authentication tokens

[1351] The server parses the authentication token from the received request.

[1352] Input: Request data, authentication token

[1353] Function: Validates the token and verifies the legitimacy of the request.

[1354] Output: Authentication result (authentication successful or failed)

[1355] Step 6:

[1356] Performing an approval or denial process

[1357] The server sends a processing request to the relevant business system based on the authentication result, and then performs the specific approval or denial process.

[1358] Input: Authentication results, business system data

[1359] Operation: Calls the API of the relevant business system and performs the approval or denial process.

[1360] Output: Processing result (Example: "Overtime request has been approved.")

[1361] The emotion engine detects the manager's current emotions and provides appropriate feedback.

[1362] Input: Current sentiment data of managers

[1363] Operation: Generates feedback content based on emotional data.

[1364] Output: Feedback message

[1365] Step 7:

[1366] Generating and sending feedback emails

[1367] The server generates and sends an email to the manager to provide feedback that the approval or rejection process is complete.

[1368] Input: Processing result data, feedback message

[1369] Operation: Generates a feedback email and sends it using the mail server.

[1370] Output: Feedback email sent to managers completed.

[1371] Step 8:

[1372] Log management and security monitoring

[1373] The server logs all approval and denial actions.

[1374] Input: Approval and denial action data

[1375] Operation: Records operation data to a log file.

[1376] Output: Log file update

[1377] The server periodically monitors logs to check for unusual operations and security risks.

[1378] Input: Log data

[1379] Function: Log data analysis and anomaly detection

[1380] Output: Anomaly detection message

[1381] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[1382] Input: Log data, current sentiment data

[1383] Operation: Comparative analysis of emotion data and log data

[1384] Output: Support message

[1385] (Application Example 2)

[1386] 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."

[1387] Currently, factory managers must log into each business system individually and manually process approvals and rejections. This process is time-consuming and labor-intensive, further increasing manager stress. Furthermore, the lack of consideration for managers' emotional states can hinder efficient work. Additionally, the slow provision of feedback on approval and rejection results reduces overall work efficiency.

[1388] In Application Example 2, the specific processing performed by the specific processing unit 290 of the data processing device 12 is realized by the following means. In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval links and rejection links in the generated approval request emails, means for sending the approval request emails to managers, emotion engine means for recognizing the emotions of managers and dynamically adjusting the email content as needed, means for receiving requests from approval or rejection links clicked by managers, means for executing approval or rejection processing based on the received requests, and means for notifying managers of the approval or rejection result via feedback email. As a result, managers can efficiently approve or reject requests via email without having to log in to individual business systems. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to improved work efficiency and reduced stress.

[1389] "Each business system" refers to systems that process various types of information related to business operations, such as attendance management systems and work instruction systems within a factory.

[1390] "Approval request information" refers to information that includes the details of employee applications for work permits and attendance records.

[1391] An "approval request email" is an email generated based on approval request information and sent to a manager.

[1392] "Approval and rejection links" are links embedded in approval request emails that, when clicked by a manager, send an approval or rejection notification to the server.

[1393] A "manager" is a person in a position of responsibility who is in charge of supervising factory operations and attendance.

[1394] An "emotional engine" is a system that recognizes the emotional state of managers and provides appropriate feedback and dynamic message adjustments based on those emotions.

[1395] A "request" is a request sent to the server after clicking an accept or reject link.

[1396] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[1397] The system for implementing this invention consists of various business systems, client terminals, a central server, an email client for managers, and an emotion engine.

[1398] Each business system processes information related to factory operations, such as attendance management systems and work instruction systems, and generates approval request information. This approval request information includes the applicant's name, application details, reason for application, and application date and time.

[1399] The client terminal receives approval request information from each business system and generates an approval request email using a pre-prepared email template. This email contains embedded approval and rejection links and is issued with a one-time authentication token. The generated email is sent to the manager's email address.

[1400] The emotion engine recognizes the emotions of managers and dynamically adjusts email content by analyzing past emotional data. By adding appropriate tone and suggestions to the email body, it enables communication that takes the manager's emotional state into consideration.

[1401] When a manager clicks an approve or reject link in an email, the central server receives the request. The server parses and verifies the authentication token included in the request and then sends the approval or rejection decision to the relevant business system.

[1402] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes details of the approval or rejection process, and the sentiment engine adds appropriate messages to show consideration for the manager.

[1403] Let's illustrate the operation of the entire system with an example. For instance, consider a scenario where a manager is wearing smart glasses. When this manager receives an email, it displays the message, "Employee A has requested 4 hours of overtime. Do you approve it?" along with links to approve and deny the request. If the manager clicks the approve link, the server receives the request and processes the approval in the relevant business system. The emotion engine analyzes the manager's emotions and generates a feedback email, including an additional message such as, "Thank you for approving. Let's discuss this at the next meeting," and sends it to the manager.

[1404] By using a generative AI model, the emotion engine analyzes managers' past emotional data and dynamically adjusts messages. This leads to increased work efficiency and reduced stress for managers.

[1405] Example of a prompt:

[1406] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[1407] In this way, the system of this invention enables factory managers to approve and reject items quickly and efficiently, ensuring smooth operations and providing responses that take into account the emotional state of managers.

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

[1409] Step 1:

[1410] Each business system generates approval request information, such as work requests and attendance requests, and sends it to the client terminal. Input includes employee name, request details, reason for request, and date and time of request. The client terminal receives this information as output.

[1411] Step 2:

[1412] The terminal generates an approval request email using a pre-prepared email template based on the received approval request information. The input is the approval request information received in Step 1. As data processing, the information is embedded into the template and the email body is generated. The output is the generated approval request email.

[1413] Step 3:

[1414] The device embeds an approval link and a denial link in the generated approval request email. The input is the approval request email generated in step 2. As data processing, a one-time authentication token is generated and attached to the link. The output is the approval request email with the links embedded.

[1415] Step 4:

[1416] The emotion engine recognizes the manager's emotions and dynamically adjusts the email content based on past emotion data. The inputs are the manager's past emotion data and the email generated in step 3. The data calculation adjusts the message according to the manager's emotions. The output is the adjusted approval request email.

[1417] Step 5:

[1418] The terminal sends a pre-configured approval request email to the manager. The inputs are the pre-configured approval request email from step 4 and the manager's email address. The output is the approval request email sent to the manager.

[1419] Step 6:

[1420] A manager clicks an approve or reject link in an email and sends the request to the server. Inputs include the manager's click action and the authentication token contained within the link. Outputs include the request sent to the server.

[1421] Step 7:

[1422] The server parses the received request and verifies the validity of the authentication token included in the link. The inputs are the request and authentication token received in step 6. The data operation involves parsing and verifying the authentication token. The output is the result of the approval or denial process.

[1423] Step 8:

[1424] The server sends the approval or rejection decision to the relevant business system. The input is the processing result obtained in step 7. The output is the approval or rejection request sent to the business system.

[1425] Step 9:

[1426] The server notifies the manager of the approval or rejection result via feedback email. The emotion engine then recognizes the manager's emotions again and dynamically adjusts the content of the feedback email. The inputs are the result processed in step 8 and the manager's current emotional state. The data processing involves generating and adjusting the content of the feedback email. The output is the feedback email sent to the manager.

[1427] As a concrete example, consider a scenario where a manager uses smart glasses to perform an approval process. Enter the following prompt into the generative AI model:

[1428] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[1429] Based on this prompt, the emotion engine makes appropriate adjustments and provides feedback to reduce stress for managers and improve work efficiency.

[1430] 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.

[1431] 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.

[1432] 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.

[1433] [Fourth Embodiment]

[1434] Figure 7 shows an example of the configuration of the data processing system 410 according to the fourth embodiment.

[1435] 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.

[1436] 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).

[1437] 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.

[1438] 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.

[1439] 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).

[1440] 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.

[1441] 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.

[1442] 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.

[1443] 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.

[1444] 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.

[1445] 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.

[1446] 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".

[1447] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[1448] System Configuration Overview

[1449] The system of the present invention consists of the following components:

[1450] Various business systems (e.g., attendance systems, account management systems, business management systems)

[1451] Client terminal

[1452] Central server

[1453] Email clients for managers

[1454] Generating and sending approval request emails

[1455] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. Next, the terminal sends this approval request email to the manager.

[1456] Specific example:

[1457] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[1458] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[1459] The device will send this email to the administrator's email address.

[1460] Processing of approvals and denials

[1461] When a user (manager) clicks an approve or deny link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or denial) to the relevant business system to perform the specific approval or denial process.

[1462] Specific example:

[1463] The user (administrator) clicks the approval link in the email.

[1464] The server receives the request and parses and verifies the authentication token included in the link.

[1465] The server sends a request to the attendance system saying, "This overtime request has been approved."

[1466] Feedback and notifications

[1467] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected).

[1468] Specific example:

[1469] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[1470] Security and log management

[1471] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[1472] Specific example:

[1473] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[1474] In this way, the system of the present invention streamlines the approval and rejection processes and reduces the burden on managers. Furthermore, the system's security is ensured through advanced security measures.

[1475] The following describes the processing flow.

[1476] Program processing flow

[1477] Generating and sending approval request emails

[1478] Step 1:

[1479] The terminal receives approval request information from each business system.

[1480] Specific operation: Retrieve data related to approval requests from business systems via API requests. For example, receive employee overtime application information from the attendance system.

[1481] Step 2:

[1482] The terminal generates an approval request email based on the approval request information it has received.

[1483] Specific actions: The system will embed the received information (applicant's name, application details, reason for application, application date and time, etc.) into an email template and create the email body.

[1484] Step 3:

[1485] The device embeds both an approval link and a denial link in the approval request email.

[1486] Specific operation: The link will be given a parameter containing a one-time authentication token, which will then be inserted into the email body.

[1487] Step 4:

[1488] The device sends an approval request email to the manager.

[1489] Specific operation: Send an email to the administrator's email address via the SMTP server.

[1490] Processing of approvals and denials

[1491] Step 5:

[1492] The user (administrator) clicks the approval or rejection link in the email.

[1493] Specific operation: The manager clicks an approve or reject link in their email client, and the web browser automatically opens the link.

[1494] Step 6:

[1495] The server receives the request when the link is clicked.

[1496] Specific operation: Receives an HTTP request and parses the parameters contained within it (such as authentication tokens and authorization IDs).

[1497] Step 7:

[1498] The server verifies the authentication token included in the link.

[1499] Specific actions: Check the expiration date and one-time use restriction of the authentication token and confirm that it is valid.

[1500] Step 8:

[1501] The server performs the approval or rejection process.

[1502] Specific operation: Depending on the content of the request, an API request is sent to the corresponding business system to perform an approval or rejection operation.

[1503] Feedback and notifications

[1504] Step 9:

[1505] The server receives the approval or rejection result.

[1506] Specific operation: Receive API responses from business systems and analyze the results.

[1507] Step 10:

[1508] The server generates a feedback email for the manager.

[1509] Specific action: Based on the approval or rejection result, create the body of the feedback email.

[1510] Step 11:

[1511] The server sends a feedback email to the manager.

[1512] Specific operation: Send a feedback email to the administrator's email address via the SMTP server.

[1513] Security and log management

[1514] Step 12:

[1515] The server logs all approval and denial actions.

[1516] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[1517] Step 13:

[1518] The server periodically monitors logs and detects any anomalies.

[1519] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors.

[1520] The above is a specific processing flow for a system that allows managers to efficiently approve and reject items using email.

[1521] (Example 1)

[1522] 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".

[1523] The goal is to reduce the effort required for managers to individually log into each business system to approve and reject decisions, thereby streamlining the approval process, while also preventing unauthorized operations and security risks through advanced security measures.

[1524] 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.

[1525] In this invention, the server includes means for receiving approval request information from each information processing system, means for generating an approval request electronic message based on the received approval request information, means for embedding approval links and denial links in the generated approval request electronic message, means for sending the approval request electronic message to an administrator, means for receiving requests from approval links or denial links clicked by the administrator, means for performing approval or denial processing based on the received requests, means for notifying the administrator of the approval or denial result via a feedback electronic message, means for recording all approval and denial actions, monitoring them periodically to detect anomalies, means for generating authentication data included in the approval and denial links and verifying the validity of the authentication data, and means for periodically monitoring the recorded data to detect abnormal operations or security risks. This enables administrators to efficiently perform approval and denial operations without individually logging into business systems, while also improving security.

[1526] An "information processing system" is a system that includes software and hardware for managing and executing all aspects of business operations.

[1527] "Approval request information" refers to information that includes applicant information and other necessary data used to request approval for a specific action or operation within the system.

[1528] An "approval request electronic message" is a message in email format that is generated based on approval request information.

[1529] An "approval link" is a link included in an electronic message requesting approval; clicking it initiates the approval process.

[1530] A "denial link" is a link included in an electronic message requesting approval, and clicking it will initiate the denial process.

[1531] "Authentication data" refers to a one-time token or key embedded in an approve or deny link and used to verify its validity.

[1532] An "administrator" is a user who has the authority to perform the system's approval and rejection processes, and is typically someone in a management position.

[1533] A "feedback electronic message" is a message in the form of an email that notifies the administrator of the outcome of the approval or rejection process.

[1534] A "request" is the request information sent to the server when an administrator clicks an approve or reject link.

[1535] A "log" is a history of data used to record all approval and rejection actions performed within a system.

[1536] This invention provides a system that eliminates the need for administrators to individually log in to each information processing system, enabling efficient approval and rejection via email. Specific embodiments of this system are described below.

[1537] System Configuration

[1538] This system consists of the following components:

[1539] Information processing systems (e.g., attendance management systems, account management systems)

[1540] Client terminal

[1541] Central server

[1542] Administrator's email client

[1543] Receiving approval request information

[1544] The terminal receives approval request information from each information processing system. This information includes the applicant's name, application details, reason for application, and date and time of application.

[1545] Generating an approval request email

[1546] Based on the received approval request information, the terminal generates an electronic approval request message using a pre-prepared email template. This electronic message contains embedded approval and denial links, and these links are associated with one-time authentication data.

[1547] Sending an approval request email

[1548] The terminal generates an electronic approval request message which is then sent to the administrator via email.

[1549] Receiving and parsing requests

[1550] When a user (administrator) clicks an approval or denial link included in an email, the server receives a click request. The server analyzes the authentication data from the received click request and verifies its validity.

[1551] Processing of approval or denial

[1552] The server sends the analysis results (approval or rejection) to the relevant information processing system, which then performs the specific approval or rejection process. For example, it might send a request to the attendance management system stating, "This overtime request has been approved."

[1553] Feedback notification

[1554] Once the approval or rejection process is complete, the server generates and sends an electronic feedback message to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[1555] Log management and security

[1556] The server logs all approval and denial actions. This log includes the date and time of approval / denial, the content of the approval / denial, and the administrator's ID. The server also periodically monitors these logs to check for unusual operations or security risks.

[1557] Examples of specific cases and prompt statements

[1558] Specific example

[1559] 1. The terminal receives information from the attendance management system stating, "An employee has requested 5 hours of overtime." This information includes the employee's name, details of the overtime request, reason for the request, and date and time of the request.

[1560] 2. Based on the information received by the terminal, an electronic approval request message is generated with the message, "An employee has requested 5 hours of overtime. Do you approve it?" This electronic message contains both an approval link and a denial link, and each link is associated with authentication data.

[1561] 3. The terminal sends the generated approval request electronic message to the administrator's email address.

[1562] 4. When the user (administrator) clicks the "approval link" in the email, the server receives the request and parses and verifies the authentication data contained in the link.

[1563] 5. The server sends a request to the attendance management system stating, "The employee's request for 5 hours of overtime has been approved."

[1564] 6. The server generates and sends an electronic feedback message to the administrator stating, "The employee's request for 5 hours of overtime has been approved."

[1565] 7. The server logs all approval and rejection actions and periodically monitors the logs to detect anomalies.

[1566] Example of a prompt

[1567] "An employee has requested 5 hours of overtime. Do you approve it?"

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

[1569] Step 1: Receiving approval request information

[1570] The terminal receives approval request information from the information processing system. The input consists of data such as the applicant's name, application details, reason for application, and application date and time, which are transmitted from the information processing system. The terminal acquires and records this data, converting it into a format usable in the next processing step.

[1571] Step 2: Generating the approval request email

[1572] The terminal generates an electronic approval request message using an email template based on the received approval request information. This generation process embeds the input data (applicant's name, application details, reason for application, application date and time, etc.) into the template, outputting an email message containing approval and rejection links. Each link is accompanied by one-time authentication data.

[1573] Step 3: Sending the approval request email

[1574] The terminal sends the generated approval request electronic message to the administrator's email address. The input is the generated email and the administrator's email address, and the output is the approval request email received in the administrator's email client.

[1575] Step 4: Click the approve or reject link.

[1576] The user (administrator) clicks an approve or reject link included in the email. The input is the link selected by the administrator (approve or reject), and the output is that the click request is sent to the server. At this point, a browser opens and the request is sent.

[1577] Step 5: Analysis and verification of the authentication token

[1578] The server analyzes the received click request and verifies the validity of the authentication data contained in the link. The input is the authentication data contained in the click request, and the output is the verification result of whether or not that data is valid. The server checks the validity of the authentication data and proceeds to the next processing step.

[1579] Step 6: Sending a request to the business system

[1580] The server sends the analysis result (approval or denial) as a request to the relevant information processing system for specific processing. The input is the verification result of the authentication data and the content of approval or denial, and the output is the request sent to the information processing system (for example, "This overtime request has been approved"). The information processing system receives this request and updates the database.

[1581] Step 7: Generate and send the feedback email.

[1582] The server generates and sends an electronic feedback message to the administrator based on the approval or rejection result. The input is the processing result (approval or rejection), and the output is a feedback email. This email contains the approval or rejection result and details.

[1583] Step 8: Logging and Monitoring

[1584] The server logs all approval and denial actions and monitors them regularly to detect anomalies. The input is the details of each operation (e.g., date and time, content, administrator ID), and the output is the recorded log data. The server periodically monitors these logs to detect unusual operations and security risks.

[1585] (Application Example 1)

[1586] 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".

[1587] In factories and other manufacturing sites, approval from managers is often required before various tasks can be performed. This includes situations where human judgment is needed before certain tasks (e.g., production line adjustments or maintenance work) can be carried out. However, with conventional systems, managers must log in to multiple business systems individually and perform the approval process manually, resulting in wasted time and effort. Furthermore, in addition to streamlining the approval process, there is a need to ensure security and log management. This invention aims to solve these problems and streamline the approval process for tasks performed within factories.

[1588] 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.

[1589] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from approval or rejection links clicked by managers, means for performing approval or rejection processing based on the received requests, means for feeding back the approval or rejection results to the business system and instructing whether to proceed, means for notifying managers of the approval or rejection results via feedback email, means for obtaining manager approval before the task is executed by the automated machine, and means for the automated machine to execute the approved task. As a result, managers can efficiently perform task approval work, and business processes within the factory are automated. Furthermore, security is improved and log management is also achieved, improving the reliability of the entire system.

[1590] "Each business system" refers to a system used in factories and manufacturing sites to manage various business processes such as attendance management, account management, and work management.

[1591] "Approval request information" refers to information used to seek approval from a manager in order to perform a specific task or action, and includes the applicant's name, the content of the request, the reason for the request, and the date and time of the request.

[1592] An "approval request email" is an email generated based on approval request information and sent to a manager, containing both an approval link and a rejection link.

[1593] An "approval link" is a link embedded in an approval request email that, when clicked, allows the user to approve a specific task or action.

[1594] A "denial link" is a link embedded in an approval request email that, when clicked, allows the user to deny a specific task or action.

[1595] A "manager" is a person in a position of authority who has the authority to approve the implementation of tasks and actions in a factory or manufacturing site.

[1596] A "request" is a request sent to the server when an administrator clicks an approve or reject link.

[1597] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[1598] "Automated machinery" refers to robots and automated devices used to perform specific tasks in factories and manufacturing sites.

[1599] A "token" is a one-time authentication code included in the accept and reject links, used to verify its validity.

[1600] A "log" is data used to record all approval and rejection actions by managers.

[1601] An "anomaly" refers to unusual operations or security risks detected during the process of monitoring logs.

[1602] This invention provides a system that allows managers to efficiently approve or reject specific tasks before they are performed by automated machines in factories or manufacturing sites. Specific embodiments thereof are described below.

[1603] System Configuration

[1604] This system consists of the following main components:

[1605] Each business system

[1606] Automated machinery

[1607] Client terminal

[1608] Central server

[1609] Email clients for managers

[1610] Generating and sending approval request emails

[1611] The server receives approval request information from each business system. This information includes task details and related information. Based on this information, the server generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, each with a one-time authentication token. The server then sends this approval request email to the manager's email address.

[1612] Processing of approvals and denials

[1613] When a manager clicks an approve or deny link in an email, the server receives the request. The server analyzes the authentication token from the request and verifies its validity. The server then sends the analysis result (approval or denial) to the relevant business system for specific approval or denial processing. If approved, the server instructs automated machines to execute the task.

[1614] Feedback and notifications

[1615] Once the approval or rejection process is complete, the server generates and sends a feedback email to the administrator. This feedback email includes the approval or rejection result, along with details of the process.

[1616] Security and log management

[1617] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[1618] Hardware and software to be used

[1619] Hardware: Client terminals (personal computers, smartphones), central server, automated machinery (robots and automated devices)

[1620] Software: Mail server (e.g., Postfix), Python, database (e.g., MySQL), token generation library (token_generator)

[1621] Specific example

[1622] For example, if an automated machine ID is "12345" and a task ID is "56789" is to be executed, the server will send an approval request email to the administrator as follows:

[1623] Approval link: http: / / example.com / approve?token=abc123&task_id=56789&robot_id=12345

[1624] Denial link: http: / / example.com / deny?token=abc123&task_id=56789&robot_id=12345

[1625] Managers can approve or reject the task by clicking the link in this email.

[1626] Example of a prompt

[1627] "Automated machine ID '12345' is attempting to execute task ID '56789'. Please generate an approval request email and provide an approval link and a denial link."

[1628] This system allows managers to approve tasks efficiently and safely, and to smoothly advance automated processes within the factory.

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

[1630] Step 1:

[1631] The server receives approval request information from each business system. This information includes details of a specific task, the applicant, and the reason for the request. Input data includes, for example, the task ID, robot ID, and the request details. The server parses this information and formats it into the format required for the next processing step. The output is the formatted approval request information.

[1632] Step 2:

[1633] The server generates an approval request email based on the received approval request information. It uses an email template to embed task details and approval and rejection links. The input is the formatted approval request information, and the output is the generated approval request email. Specifically, it populates the data fields of the email template with the approval request information.

[1634] Step 3:

[1635] The server generates a one-time authentication token and attaches it to the accept and reject links. A token generation library is used to create a secure token. The input is the acceptance request email, and the output is the acceptance request email with the token embedded. Specifically, the generated token is appended to the URL of the link.

[1636] Step 4:

[1637] The server sends the generated approval request email to the administrator. It uses the SMTP protocol to deliver the email to the administrator's email address. The input is the approval request email with an embedded token, and the output is the transmission result. Specifically, this involves connecting to the mail server and sending the email.

[1638] Step 5:

[1639] When a manager clicks an approve or reject link, the server receives the request. The input is the request from the manager, and the output is the result of parsing the request. Specifically, the server extracts the token and task information from the request URL and verifies their validity.

[1640] Step 6:

[1641] The server performs approval or rejection processing based on the request. The input is the parsed request information, and the output is the processing result. Specifically, it notifies the business system whether or not the task can be executed.

[1642] Step 7:

[1643] The server notifies the manager of the approval or rejection result via feedback email. The input is the approval or rejection result, and the output is the feedback email. Specifically, the feedback email is generated and sent.

[1644] Step 8:

[1645] The server logs all approval and rejection actions and monitors them periodically. The input is each approval and rejection action, and the output is log data. Specifically, it writes to log files and periodically detects anomalies.

[1646] This series of processing steps allows managers to efficiently approve tasks for factory robots while also ensuring security and log management.

[1647] 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.

[1648] This invention combines an emotion engine with a system that allows managers to efficiently approve and reject requests via email, eliminating the need for them to individually log into each business system. Specific embodiments of this system are described below.

[1649] System Configuration Overview

[1650] The system of the present invention consists of the following components:

[1651] Various business systems (e.g., attendance systems, account management systems, business management systems)

[1652] Client terminal

[1653] Central server

[1654] Email clients for managers

[1655] Emotional Engine

[1656] Generating and sending approval request emails

[1657] The terminal receives approval request information from various business systems. This information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The terminal then sends this approval request email to the manager. Furthermore, the sentiment engine recognizes the manager's emotions and dynamically adjusts the email content as needed.

[1658] Specific example:

[1659] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[1660] The terminal uses this information to generate an email that says, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[1661] The emotion engine analyzes the manager's past emotional data and adds appropriate tone and suggestions to the email body.

[1662] The device will send this email to the administrator's email address.

[1663] Processing of approvals and denials

[1664] When a user (manager) clicks an approve or reject link in an email, the server receives the request. The server parses the authentication token from the received request and verifies its validity. The server then sends the parsing result (approval or rejection) to the relevant business system to perform the specific approval or rejection process. Furthermore, an emotion engine continuously monitors the manager's emotions and provides appropriate feedback if there is stress or dissatisfaction.

[1665] Specific example:

[1666] The user (administrator) clicks the approval link in the email.

[1667] The server receives the request and parses and verifies the authentication token included in the link.

[1668] The server sends a request to the attendance system saying, "This overtime request has been approved."

[1669] The emotion engine detects the manager's current emotions and sets an emotion flag in response to the processing request.

[1670] Feedback and notifications

[1671] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. This feedback email includes the approval or rejection result, along with details of the process (e.g., which applications were approved and which were rejected). Additionally, the sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[1672] Specific example:

[1673] The server sends an email to the manager stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[1674] The emotion engine analyzes the manager's emotions and adds messages such as, "Thank you for approving this. Let's discuss this at the next meeting," to the feedback email.

[1675] Security and log management

[1676] The server logs all approval and denial actions. This includes the date and time of approval / denial, the content of the approval / denial, and the ID of the administrator. The server also periodically monitors these logs to check for any unusual operations or security risks.

[1677] Specific example:

[1678] The server records all actions taken by administrators and analyzes the logs at regular intervals to detect anomalies.

[1679] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[1680] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[1681] The following describes the processing flow.

[1682] Specific processing flow of the program

[1683] Generating and sending approval request emails

[1684] Step 1:

[1685] The terminal receives approval request information from each business system.

[1686] Specific operation: Retrieve data related to approval requests (e.g., applicant's name, application details, reason for application) from business systems via API requests. For example, receive overtime application information from the attendance system.

[1687] Step 2:

[1688] The terminal generates an approval request email based on the approval request information it has received.

[1689] Specific operation: Embed the received information into an email template and create the body of the approval request email. The template includes a basic format, and application information is inserted in the designated places.

[1690] Step 3:

[1691] The device embeds both an approval link and a denial link in the approval request email.

[1692] Specific operation: The link will be given a parameter containing a one-time authentication token, which will then be inserted into the email body. For example, HTML code for "Approve" and "Deny" buttons will be generated.

[1693] Step 4:

[1694] The emotion engine recognizes the emotions of managers and dynamically modifies the content of emails.

[1695] Specific actions: Analyze emotions based on past approval history and current status, and add appropriate tone and suggestions to the email body. For example, if a manager is feeling stressed, change the message to a more concise one.

[1696] Step 5:

[1697] The device sends an approval request email to the manager.

[1698] Specific operation: Send an email to the administrator's email address via the SMTP server. The sending log will also be recorded simultaneously.

[1699] Processing of approvals and denials

[1700] Step 6:

[1701] The user (administrator) clicks the approval or rejection link in the email.

[1702] Specific action: Click the approve or reject link in your email client, and your web browser will open the link.

[1703] Step 7:

[1704] The server receives the request when the link is clicked.

[1705] Specific operation: Receives an HTTP request and parses the parameters contained within it (such as authentication tokens and authorization IDs).

[1706] Step 8:

[1707] The server verifies the authentication token included in the link.

[1708] Specific actions: Check the expiration date and one-time use restriction of the authentication token and confirm that it is valid.

[1709] Step 9:

[1710] The server performs the approval or rejection process.

[1711] Specific example: Depending on the content of the request, an API request is sent to the corresponding business system to perform an approval or rejection operation.

[1712] Feedback and notifications

[1713] Step 10:

[1714] The server receives the approval or rejection result.

[1715] Specific operation: Receive API responses from business systems and analyze the results.

[1716] Step 11:

[1717] The emotion engine generates appropriate feedback email content based on the manager's emotions.

[1718] Specific actions: Dynamically change the tone and content of feedback emails by combining the approval or rejection result with the manager's sentiment data. For example, decide whether to add detailed guidance.

[1719] Step 12:

[1720] The server sends a feedback email to the manager.

[1721] Specific operation: Use the SMTP server to send the generated feedback email to the administrator's email address.

[1722] Security and log management

[1723] Step 13:

[1724] The server logs all approval and denial actions.

[1725] Specific actions: Information regarding approval or denial actions (date and time, operation details, user ID, etc.) is recorded in a database or log file.

[1726] Step 14:

[1727] The server periodically monitors logs and detects any anomalies.

[1728] Specific actions: Use log analysis tools and anomaly detection algorithms to detect suspicious patterns and behaviors. If an anomaly is detected, issue a warning.

[1729] Step 15:

[1730] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed.

[1731] Specific actions: Analyze emotional data and action logs to generate appropriate support messages for managers' emotional states.

[1732] In this way, the system of the present invention, which incorporates an emotion engine, allows managers to efficiently approve and reject requests via email without having to log into each business system. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction.

[1733] (Example 2)

[1734] 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".

[1735] Traditional approval and rejection systems had drawbacks, including low efficiency due to the time and effort required for managers to log in to each business system individually to process requests. Furthermore, the systems relied solely on automated email notifications without considering the emotional state of managers, leading to increased stress and workload. Additionally, insufficient log management of approval and rejection actions raised security concerns.

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

[1737] In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval and rejection links in the generated approval request emails, means for sending the approval request emails to managers, means for receiving requests from the approval or rejection links clicked by the managers, means for performing approval or rejection processing based on the received requests, means for notifying the managers of the approval or rejection results via feedback email, means for analyzing the managers' past sentiment data and dynamically adjusting the email content, means for detecting the managers' current sentiment and providing appropriate feedback, means for generating authentication tokens included in the approval and rejection links and verifying the validity of the tokens, means for logging all approval and rejection actions by managers and periodically monitoring the logs to detect anomalies, and means for comparing log data and sentiment data and providing appropriate support messages. This eliminates the need for managers to log into each business system and enables efficient approval and rejection via email. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help reduce security risks.

[1738] "Each business system" refers to systems used for purposes such as attendance management, account management, and business management.

[1739] "Approval request information" refers to information used to request approval, such as the applicant's name, application details, reason for application, and application date and time.

[1740] An "approval request email" refers to an email generated based on approval request information and sent to a manager.

[1741] An "approval link" refers to a specific link embedded in an email that, when clicked by a manager, indicates their intention to approve the request.

[1742] A "denial link" refers to a specific link embedded in an email that, when clicked by a manager, indicates an intention to deny the work.

[1743] "Managerial position" refers to a person in a position that has the authority to approve or deny decisions.

[1744] A "request" refers to the request sent to the server when a manager clicks an approve or reject link.

[1745] An "authentication token" refers to a one-time-use identification piece of information included in the approve and deny links.

[1746] A "feedback email" refers to an email sent to a manager to notify them of the approval or rejection of a request.

[1747] The "emotion engine" refers to a function that analyzes managers' past emotional data and current emotional state to dynamically adjust email content and feedback.

[1748] "Logs" refer to records such as approval and rejection actions, date and time of operation, content, and the ID of the manager.

[1749] "Security monitoring" refers to the process of periodically analyzing log data to detect abnormal operations and security risks.

[1750] A "supportive message" refers to an appropriate message that the emotional engine provides when a manager may be experiencing stress or frustration.

[1751] This invention provides a system that eliminates the need for managers to individually log into each business system, enabling efficient approval and rejection via email. This system incorporates an emotion engine to consider the manager's emotional state and reduce stress. Specific embodiments are described below.

[1752] System Configuration Overview

[1753] The system of the present invention consists of the following components:

[1754] Various business systems (e.g., attendance systems, account management systems, business management systems)

[1755] Client terminal

[1756] Central server

[1757] Email clients for managers

[1758] Emotional Engine

[1759] Hardware and software to be used

[1760] Client terminal: Receives approval request information from each business system, generates and sends approval request emails.

[1761] Central Server: Receives approval or denial requests from users and parses authentication tokens.

[1762] Manager's email client: Receives approval request emails and notifies the manager.

[1763] Emotion Engine: Analyzes the emotions of managers and provides functionality to dynamically adjust the tone and content of emails.

[1764] Various business systems: These include attendance management systems, account management systems, and business management systems, among others, that are subject to processing.

[1765] Generating and sending approval request emails

[1766] The terminal receives approval request information from various business systems. The received information includes the applicant's name, application details, reason for application, and application date and time. Based on the received information, the terminal generates an approval request email using a pre-prepared email template. The generated email contains embedded approval and rejection links, and these links are assigned a one-time authentication token. The sentiment engine analyzes the manager's past sentiment data and dynamically adjusts the email content. Next, the terminal sends this approval request email to the manager.

[1767] Specific example

[1768] The terminal receives information from the attendance system stating, "Mr. Tanaka has requested 5 hours of overtime."

[1769] The terminal uses this information to generate an email saying, "Mr. Tanaka has requested 5 hours of overtime. Do you approve it?" and includes both an approve link and a rejection link.

[1770] The emotion engine adds messages such as, "Thank you for your approval. Let's discuss this matter at the next meeting."

[1771] The device will send this email to the administrator's email address.

[1772] Processing of approvals and denials

[1773] When a user (manager) clicks an approve or reject link in an email, the server receives the request and parses the authentication token contained in the link. After verifying the validity of the authentication token, the server sends the parsing result (approval or rejection) to the relevant business system and processes the specific approval or rejection. The sentiment engine detects the manager's current sentiment and provides appropriate feedback.

[1774] Specific example

[1775] The user (administrator) clicks the approval link in the email.

[1776] The server receives the request and parses and verifies the authentication token included in the link.

[1777] The server sends a request to the attendance system saying, "This overtime request has been approved."

[1778] The emotion engine detects the manager's current emotions and provides feedback such as, "Approval process complete."

[1779] Feedback and notifications

[1780] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes the approval or rejection result, along with details of the process (which applications were approved and which were rejected). The sentiment engine dynamically adjusts the tone and content of the feedback email based on the manager's emotions.

[1781] Specific example

[1782] The server generates an email stating, "Mr. Tanaka's request for 5 hours of overtime has been approved."

[1783] The emotion engine adds the message, "Thank you for your approval. Let's discuss this matter at the next meeting."

[1784] The server will send this email to the administrator's email address.

[1785] Security and log management

[1786] The server logs all approval and rejection actions. The logs include the date and time of approval / rejection, the content of the approval / rejection, and the manager's ID. The server periodically monitors these logs to check for unusual activity or security risks. The sentiment engine compares past logs with current sentiment data to identify times when managers are particularly stressed and provides appropriate support messages.

[1787] Specific example

[1788] The server records all actions taken by administrators and analyzes the logs weekly to detect anomalies.

[1789] The emotion engine compares past logs with current emotion data to identify periods when managers are likely to be stressed. For example, if a tendency for stress to increase at the end of the month is detected, it will provide messages encouraging relaxation during that period.

[1790] In this way, the system of the present invention allows managers to efficiently approve and reject requests via email without having to log in to each business system. Furthermore, the introduction of an emotion engine enables flexible responses that take into account the emotional state of managers, contributing to stress reduction. In addition, enhanced log management and security monitoring functions help to reduce security risks.

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

[1792] Step 1:

[1793] Receiving approval request information

[1794] The terminal receives approval request information from various business systems (e.g., attendance system, account management system).

[1795] Input: Applicant's name, application details, reason for application, date and time of application

[1796] Operation: Retrieves necessary information from the API or database of each business system.

[1797] Output: Approval request information data (Example: "Mr. Tanaka has requested 5 hours of overtime.")

[1798] Step 2:

[1799] Generating an approval request email

[1800] Based on the approval request information received by the device, an approval request email is generated using an email template.

[1801] Input: Approval request information data, email template

[1802] Function: Embed approval request information into email templates and generate and embed approval and rejection links.

[1803] Output: Generated approval request email (Example: "Mr. / Ms. Tanaka has requested 5 hours of overtime. Do you approve it?")

[1804] Step 3:

[1805] Adjusting and sending approval request emails

[1806] The emotion engine analyzes the manager's past emotional data and dynamically adjusts the content of emails.

[1807] Input: Generated approval request email, historical sentiment data

[1808] Function: The emotion engine adjusts the tone and content of the email (e.g., adds words of encouragement).

[1809] Output: Adjusted approval request email

[1810] The device sends this adjusted approval request email to the manager.

[1811] Operation: Sends emails using a mail server.

[1812] Output: Approval request email sent to manager completed.

[1813] Step 4:

[1814] Receiving an approval or rejection request

[1815] The user (administrator) clicks the approval or rejection link in the email.

[1816] Input: Clicking an approve or disapprove link

[1817] Operation: The server receives clicks from the administrator.

[1818] Output: Request data (e.g., click on an approval link)

[1819] Step 5:

[1820] Analysis of authentication tokens

[1821] The server parses the authentication token from the received request.

[1822] Input: Request data, authentication token

[1823] Function: Validates the token and verifies the legitimacy of the request.

[1824] Output: Authentication result (authentication successful or failed)

[1825] Step 6:

[1826] Performing an approval or denial process

[1827] The server sends a processing request to the relevant business system based on the authentication result, and then performs the specific approval or denial process.

[1828] Input: Authentication results, business system data

[1829] Operation: Calls the API of the relevant business system and performs the approval or denial process.

[1830] Output: Processing result (Example: "Overtime request has been approved.")

[1831] The emotion engine detects the manager's current emotions and provides appropriate feedback.

[1832] Input: Current sentiment data of managers

[1833] Operation: Generates feedback content based on emotional data.

[1834] Output: Feedback message

[1835] Step 7:

[1836] Generating and sending feedback emails

[1837] The server generates and sends an email to the manager to provide feedback that the approval or rejection process is complete.

[1838] Input: Processing result data, feedback message

[1839] Operation: Generates a feedback email and sends it using the mail server.

[1840] Output: Feedback email sent to managers completed.

[1841] Step 8:

[1842] Log management and security monitoring

[1843] The server logs all approval and denial actions.

[1844] Input: Approval and denial action data

[1845] Operation: Records operation data to a log file.

[1846] Output: Log file update

[1847] The server periodically monitors logs to check for unusual operations and security risks.

[1848] Input: Log data

[1849] Function: Log data analysis and anomaly detection

[1850] Output: Anomaly detection message

[1851] The emotion engine compares past logs with current emotion data to identify times when managers are particularly stressed and provides appropriate support messages.

[1852] Input: Log data, current sentiment data

[1853] Operation: Comparative analysis of emotion data and log data

[1854] Output: Support message

[1855] (Application Example 2)

[1856] 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".

[1857] Currently, factory managers must log into each business system individually and manually process approvals and rejections. This process is time-consuming and labor-intensive, further increasing manager stress. Furthermore, the lack of consideration for managers' emotional states can hinder efficient work. Additionally, the slow provision of feedback on approval and rejection results reduces overall work efficiency.

[1858] In Application Example 2, the specific processing performed by the specific processing unit 290 of the data processing device 12 is realized by the following means. In this invention, the server includes means for receiving approval request information from each business system, means for generating approval request emails based on the received approval request information, means for embedding approval links and rejection links in the generated approval request emails, means for sending the approval request emails to managers, emotion engine means for recognizing the emotions of managers and dynamically adjusting the email content as needed, means for receiving requests from approval or rejection links clicked by managers, means for executing approval or rejection processing based on the received requests, and means for notifying managers of the approval or rejection result via feedback email. As a result, managers can efficiently approve or reject requests via email without having to log in to individual business systems. Furthermore, the emotion engine enables flexible responses that take into account the emotional state of managers, contributing to improved work efficiency and reduced stress.

[1859] "Each business system" refers to systems that process various types of information related to business operations, such as attendance management systems and work instruction systems within a factory.

[1860] "Approval request information" refers to information that includes the details of employee applications for work permits and attendance records.

[1861] An "approval request email" is an email generated based on approval request information and sent to a manager.

[1862] "Approval and rejection links" are links embedded in approval request emails that, when clicked by a manager, send an approval or rejection notification to the server.

[1863] A "manager" is a person in a position of responsibility who is in charge of supervising factory operations and attendance.

[1864] An "emotional engine" is a system that recognizes the emotional state of managers and provides appropriate feedback and dynamic message adjustments based on those emotions.

[1865] A "request" is a request sent to the server after clicking an accept or reject link.

[1866] A "feedback email" is an email sent to a manager to notify them of the approval or rejection of a request.

[1867] The system for implementing this invention consists of various business systems, client terminals, a central server, an email client for managers, and an emotion engine.

[1868] Each business system processes information related to factory operations, such as attendance management systems and work instruction systems, and generates approval request information. This approval request information includes the applicant's name, application details, reason for application, and application date and time.

[1869] The client terminal receives approval request information from each business system and generates an approval request email using a pre-prepared email template. This email contains embedded approval and rejection links and is issued with a one-time authentication token. The generated email is sent to the manager's email address.

[1870] The emotion engine recognizes the emotions of managers and dynamically adjusts email content by analyzing past emotional data. By adding appropriate tone and suggestions to the email body, it enables communication that takes the manager's emotional state into consideration.

[1871] When a manager clicks an approve or reject link in an email, the central server receives the request. The server parses and verifies the authentication token included in the request and then sends the approval or rejection decision to the relevant business system.

[1872] Once the approval or rejection process is complete, the server generates and sends a feedback email to the manager. The feedback email includes details of the approval or rejection process, and the sentiment engine adds appropriate messages to show consideration for the manager.

[1873] Let's illustrate the operation of the entire system with an example. For instance, consider a scenario where a manager is wearing smart glasses. When this manager receives an email, it displays the message, "Employee A has requested 4 hours of overtime. Do you approve it?" along with links to approve and deny the request. If the manager clicks the approve link, the server receives the request and processes the approval in the relevant business system. The emotion engine analyzes the manager's emotions and generates a feedback email, including an additional message such as, "Thank you for approving. Let's discuss this at the next meeting," and sends it to the manager.

[1874] By using a generative AI model, the emotion engine analyzes managers' past emotional data and dynamically adjusts messages. This leads to increased work efficiency and reduced stress for managers.

[1875] Example of a prompt:

[1876] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[1877] In this way, the system of this invention enables factory managers to approve and reject items quickly and efficiently, ensuring smooth operations and providing responses that take into account the emotional state of managers.

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

[1879] Step 1:

[1880] Each business system generates approval request information, such as work requests and attendance requests, and sends it to the client terminal. Input includes employee name, request details, reason for request, and date and time of request. The client terminal receives this information as output.

[1881] Step 2:

[1882] The terminal generates an approval request email using a pre-prepared email template based on the received approval request information. The input is the approval request information received in Step 1. As data processing, the information is embedded into the template and the email body is generated. The output is the generated approval request email.

[1883] Step 3:

[1884] The device embeds an approval link and a denial link in the generated approval request email. The input is the approval request email generated in step 2. As data processing, a one-time authentication token is generated and attached to the link. The output is the approval request email with the links embedded.

[1885] Step 4:

[1886] The emotion engine recognizes the manager's emotions and dynamically adjusts the email content based on past emotion data. The inputs are the manager's past emotion data and the email generated in step 3. The data calculation adjusts the message according to the manager's emotions. The output is the adjusted approval request email.

[1887] Step 5:

[1888] The terminal sends a pre-configured approval request email to the manager. The inputs are the pre-configured approval request email from step 4 and the manager's email address. The output is the approval request email sent to the manager.

[1889] Step 6:

[1890] A manager clicks an approve or reject link in an email and sends the request to the server. Inputs include the manager's click action and the authentication token contained within the link. Outputs include the request sent to the server.

[1891] Step 7:

[1892] The server parses the received request and verifies the validity of the authentication token included in the link. The inputs are the request and authentication token received in step 6. The data operation involves parsing and verifying the authentication token. The output is the result of the approval or denial process.

[1893] Step 8:

[1894] The server sends the approval or rejection decision to the relevant business system. The input is the processing result obtained in step 7. The output is the approval or rejection request sent to the business system.

[1895] Step 9:

[1896] The server notifies the manager of the approval or rejection result via feedback email. The emotion engine then recognizes the manager's emotions again and dynamically adjusts the content of the feedback email. The inputs are the result processed in step 8 and the manager's current emotional state. The data processing involves generating and adjusting the content of the feedback email. The output is the feedback email sent to the manager.

[1897] As a concrete example, consider a scenario where a manager uses smart glasses to perform an approval process. Enter the following prompt into the generative AI model:

[1898] Please describe in detail the scenario in which Ms. Tanaka uses smart glasses to approve work. Specifically, please explain the flow of email sending, approval / rejection processing, and feedback, including dynamic message management based on the manager's emotions using an emotion engine.

[1899] Based on this prompt, the emotion engine makes appropriate adjustments and provides feedback to reduce stress for managers and improve work efficiency.

[1900] The specific processing unit 290 transmits the result of the specific processing to the robot 414. In the robot 414, the control unit 46A causes the speaker 240 and the controlled object 443 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.

[1901] 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.

[1902] 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 robot 414.

[1903] Furthermore, the emotion identification model 59, acting as an emotion engine, may determine the user's emotion according to a specific mapping. Specifically, the emotion identification model 59 may determine the user's emotion according to a specific mapping, which is an emotion map (see Figure 9). Similarly, the emotion identification model 59 may also determine the robot's emotion, and the identification processing unit 290 may perform identification processing using the robot's emotion.

[1904] Figure 9 shows an emotion map 400 in which multiple emotions are mapped. In the emotion map 400, emotions are arranged in concentric circles radiating from the center. The closer to the center of the concentric circles, the more primitive the emotions are located. Further out of the concentric circles, emotions representing states and actions arising from mental states are located. Emotion is a concept that includes feelings and mental states. On the left side of the concentric circles, emotions that are generally generated from reactions occurring in the brain are located. On the right side of the concentric circles, emotions that are generally induced by situational judgment are located. Above and below the concentric circles, emotions that are generally generated from reactions occurring in the brain and induced by situational judgment are located. In addition, the emotion of "pleasure" is located on the upper side of the concentric circles, and the emotion of "displeasure" is located on the lower side. Thus, in the emotion map 400, multiple emotions are mapped based on the structure in which emotions arise, and emotions that are likely to occur simultaneously are mapped close together.

[1905] These emotions are distributed at the 3 o'clock position on the Emotion Map 400, and usually fluctuate between feelings of security and anxiety. In the right half of the Emotion Map 400, situational awareness takes precedence over internal feelings, resulting in a calm impression.

[1906] The inside of the Emotion Map 400 represents inner thoughts, while the outside represents actions. Therefore, the further you go from the outside of the Emotion Map 400, the more visible (expressed in actions) your emotions become.

[1907] Here, human emotions are based on various balances, such as posture and blood sugar levels. When these balances deviate from the ideal, it results in discomfort, and when they approach the ideal, it results in pleasure. Similarly, in robots, cars, motorcycles, etc., emotions can be created based on various balances, such as posture and battery level. When these balances deviate from the ideal, it results in discomfort, and when they approach the ideal, it results in pleasure. The emotion map can be generated, for example, based on Dr. Mitsuyoshi's emotion map (Research on a system for analyzing brain physiological signals of speech emotion recognition and emotion, Tokushima University, doctoral dissertation: https: / / ci.nii.ac.jp / naid / 500000375379). The left half of the emotion map contains emotions belonging to a region called "response," where sensation is dominant. The right half of the emotion map contains emotions belonging to a region called "situation," where situational awareness is dominant.

[1908] The emotion map defines two emotions that promote learning. One is the emotion around the middle of the negative "repentance" and "reflection" on the situation side. In other words, it is when the robot experiences negative emotions such as "I never want to feel this way again" or "I don't want to be scolded again." The other is the emotion around the positive "desire" on the reaction side. In other words, it is when the robot has positive feelings such as "I want more" or "I want to know more."

[1909] The emotion identification model 59 inputs user input into a pre-trained neural network, obtains emotion values ​​representing each emotion shown in the emotion map 400, and determines the user's emotion. This neural network is pre-trained based on multiple training data sets, which are combinations of user input and emotion values ​​representing each emotion shown in the emotion map 400. Furthermore, this neural network is trained so that emotions located close together have similar values, as shown in the emotion map 900 in Figure 10. Figure 10 shows an example where multiple emotions such as "reassured," "calm," and "confident" have similar emotion values.

[1910] The above description primarily focuses on the functions of the data processing device 12 in relation to this disclosure. However, the system related to this disclosure is not necessarily implemented on a server. The system related to this disclosure may be implemented as a general information processing system. This disclosure may be implemented, for example, as a software program that runs on a personal computer or as an application that runs on a smartphone. The method related to this disclosure may be provided to users in SaaS (Software as a Service) format.

[1911] In the above embodiment, an example was given in which a specific process is performed by a single computer 22. However, the technology of this disclosure is not limited thereto, and a distributed processing of the specific process may be performed by multiple computers, including computer 22. For example, a data generation model 58 may be provided in an external device of the data processing device 12, and the external device may generate data according to the input data.

[1912] In the above embodiment, an example was given in which the specific processing program 56 is stored in the storage 32, but the technology of this disclosure is not limited thereto. For example, the specific processing program 56 may be stored in a portable, computer-readable, non-temporary storage medium such as a USB (Universal Serial Bus) memory. The specific processing program 56 stored in the non-temporary storage medium is installed in the computer 22 of the data processing device 12. The processor 28 executes specific processing according to the specific processing program 56.

[1913] Alternatively, the specific processing program 56 may be stored in a storage device such as a server connected to the data processing device 12 via the network 54, and the specific processing program 56 may be downloaded and installed on the computer 22 in response to a request from the data processing device 12.

[1914] Furthermore, it is not necessary to store the entirety of the specific processing program 56 in a storage device such as a server connected to the data processing device 12 via the network 54, or to store the entirety of the specific processing program 56 in the storage 32; it is acceptable to store only a portion of the specific processing program 56.

[1915] The following types of processors can be used as hardware resources to perform specific processing. Examples of processors include a CPU, a general-purpose processor that functions as a hardware resource to perform specific processing by executing software, i.e., a program. Other examples of processors include dedicated electrical circuits, such as FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), or ASICs (Application Specific Integrated Circuits), which have circuit configurations specifically designed to perform specific processing. All of these processors have built-in or connected memory, and all of them perform specific processing by using memory.

[1916] The hardware resource that performs a specific process may consist of one of these various processors, or it may consist of a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA). Alternatively, the hardware resource that performs a specific process may consist of a single processor.

[1917] Examples of configurations using a single processor include, firstly, a configuration in which one or more CPUs and software are combined to form a single processor, and this processor functions as a hardware resource that performs a specific process. Secondly, there is a configuration using a processor that realizes the functions of the entire system, including multiple hardware resources that perform a specific process, on a single IC chip, as exemplified by SoCs (System-on-a-chip). In this way, a specific process is realized using one or more of the above types of processors as hardware resources.

[1918] Furthermore, the hardware structure of these various processors can more specifically uti...

Claims

1. A means of receiving approval request information from each business system, A means of generating an approval request email based on the received approval request information, A means of embedding an approval link and a rejection link in the generated approval request email, A means of sending an approval request email to a manager, A means of receiving requests from approval or rejection links clicked by managers, Means for performing approval or denial processing based on received requests, A system that includes a means of notifying managers of the approval or rejection result via feedback email.

2. The system according to claim 1, further comprising means for generating authentication tokens included in an approval link and a denial link, and for verifying the validity of the tokens.

3. The system according to claim 1, further comprising means for logging all approval and rejection actions by managers and periodically monitoring the logs to detect anomalies.

Images