system

Abstract

We provide the system. [Solution] Methods for obtaining a list of tasks, A means of setting priorities and estimated times for the acquired list of tasks, A means of distributing tasks based on set priorities and estimated time, A means of assigning tasks at the optimal time based on the user's schedule information, A means of monitoring the progress of each task, A system that includes this.

Description

Technical Field

[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, the method including steps of receiving a user utterance, adding the user utterance to a prompt including an instruction sentence related to an explanation of a character of the chatbot, 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 modern business environment, efficient distribution and management of tasks are required. However, in the method of manually distributing tasks, it is difficult to optimize priorities and time, and inefficient task progress has become a problem. Also, it is not easy to check the progress status and manage the schedule, and there is a concern that task delays and errors may occur due to this. To solve these problems, a system that automates the distribution and management of tasks and enables efficient and timely optimal task execution is needed.

Means for Solving the Problems

[0005] The present invention solves the above problems by providing means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for assigning tasks at the optimal timing based on the user's schedule information, and means for monitoring the progress of each task. In particular, the system assigns a unique ID to each task when acquiring the list of tasks, and when a user completes a task, it receives a completion status from the terminal and updates the database, thereby achieving efficient task management and progress confirmation.

[0006] A "task list" is a collection of tasks that a user must perform, and each task is an identifiable individual task.

[0007] "Priority" is an indicator that shows the importance and urgency of each task, and is a criterion for determining the order in which tasks should be carried out.

[0008] "Estimated time" refers to an estimate of the time required to complete each task, and is a factor that influences the scheduling and allocation of tasks.

[0009] "Distribution" refers to the operation or process of assigning tasks to users in the optimal order and timing based on the acquired task list.

[0010] "Schedule information" refers to data related to a user's time management, such as their appointments and free time, and is referenced when assigning tasks.

[0011] "Assignment" is the operation of specifying that a particular task should be performed according to the user's schedule.

[0012] "Progress status" refers to the extent to which a task has been completed, and is an indicator used to check the user's level of work performance.

[0013] "Monitoring" is the process of tracking the progress and completion status of tasks and updating the database as needed.

[0014] A "unique ID" is an identifier that can uniquely identify each business operation and is used to distinguish between operations.

[0015] The "completion status" indicates that a user has completed a specific task, and the database is updated when this information is sent to the server. [Brief explanation of the drawing]

[0016] [Figure 1] This is a conceptual diagram showing an example of the configuration of a data processing system according to the first embodiment. [Figure 2] This is a conceptual diagram showing an example of the essential functions of a data processing device and a smart device according to the first embodiment. [Figure 3] This is a conceptual diagram showing an example of the configuration of a data processing system according to the second embodiment. [Figure 4] This is a conceptual diagram showing an example of the main functions of a data processing device and smart glasses according to the second embodiment. [Figure 5] This is a conceptual diagram showing an example of the configuration of a data processing system according to the third embodiment. [Figure 6] This is a conceptual diagram showing an example of the main functions of a data processing device and a headset-type terminal according to the third embodiment. [Figure 7] This is a conceptual diagram showing an example of the configuration of a data processing system according to the fourth embodiment. [Figure 8] This is a conceptual diagram showing an example of the main functions of a data processing device and a robot according to the fourth embodiment. [Figure 9] This shows an emotion map where multiple emotions are mapped. [Figure 10] This shows an emotion map where multiple emotions are mapped. [Figure 11] This is a sequence diagram showing the processing flow of the data processing system in Example 1. [Figure 12] 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 Embodiment 2 when combined with an emotion engine. [Figure 14] It is a sequence diagram showing the processing flow of the data processing system in Application Example 2 when combined with an emotion engine.

Mode for Carrying Out the Invention

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

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

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

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

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

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

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

[0024] [First Embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

[0037] System Overview

[0038] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system includes functions for obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[0039] Program processing

[0040] The program of this system operates with the server, terminal, and user each fulfilling their respective roles as follows:

[0041] Obtaining a list of tasks

[0042] User: Enters a list of tasks (e.g., report creation, meeting preparation, email reply) into the terminal.

[0043] Terminal: Sends the entered list of tasks to the server.

[0044] Server: Receives the task list and saves it to the database. Assigns a unique ID to each task for management.

[0045] Priority and time settings

[0046] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[0047] Terminal: Saves configuration information in a format that sends it to the server.

[0048] Server: Adds the received configuration information to the task list and updates the database.

[0049] Distribution of tasks

[0050] Server: Retrieves a list of tasks and their configuration information from the database, uses an algorithm to sort the tasks by priority, and prepares them for distribution to each user in the next step.

[0051] Sorting by priority: Tasks with particularly high priority are placed first.

[0052] Distribute tasks efficiently, taking estimated time into consideration.

[0053] Task assignment

[0054] Server: Retrieves user schedule information and assigns each task at the optimal time.

[0055] Server: Sends the assigned work schedule to the terminal.

[0056] Confirmation and acceptance of the work schedule.

[0057] Terminal: Displays received work schedules to the user.

[0058] User: Check the schedule, make any necessary corrections, and resend it to the server.

[0059] Server: Receives the changes and updates the database again.

[0060] Monitoring progress

[0061] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0062] Terminal: Sends completion status to the server.

[0063] Server: Updates the task status in the database and notifies the user if there are tasks to assign next.

[0064] Specific example

[0065] For example, the following task list is entered by the user:

[0066] 1. Report creation (Priority: High, Estimated time: 2 hours)

[0067] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0068] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[0069] Obtaining and setting up the task list

[0070] 1. User: Enter the task list into the terminal (e.g., write a report, prepare for a meeting, reply to emails).

[0071] 2. Terminal: Sends the task list to the server.

[0072] 3. Server: Stores the task list in the database and assigns a unique ID to each task.

[0073] 4. User: Enter priority and estimated time for each task.

[0074] 5. Terminal: Sends configuration information to the server.

[0075] Work distribution and allocation

[0076] 1. Server: Prioritize tasks based on their importance (e.g., report creation → meeting preparation → email reply).

[0077] 2. Server: Assigns the rearranged tasks to each user's schedule at the most opportune time.

[0078] 3. Server: Sends schedule information to the terminal.

[0079] Monitoring of work schedules and progress

[0080] 1. Terminal: Displays the assigned schedule to the user.

[0081] 2. User: Starts tasks one after another and marks them as "completed" on the terminal upon completion.

[0082] 3. Terminal: Sends completion status to the server.

[0083] 4. Server: Updates the database status and notifies users of the next task.

[0084] This allows for efficient task distribution, enabling users to effectively complete their tasks. Furthermore, the server constantly monitors progress and updates the database in real time, simplifying overall project management.

[0085] The following describes the processing flow.

[0086] Step 1:

[0087] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[0088] Step 2:

[0089] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[0090] Step 3:

[0091] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[0092] Step 4:

[0093] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[0094] Step 5:

[0095] Terminal: Sends information about the configured priority and estimated time to the server.

[0096] Step 6:

[0097] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[0098] Step 7:

[0099] Server: Retrieves a list of tasks and their configuration information from the database. After retrieval, it uses an algorithm to sort the tasks in order of priority.

[0100] Step 8:

[0101] Server: Executes a distribution algorithm based on the sorted tasks and distributes them to each user. At this time, it distributes tasks efficiently, taking into account the estimated time for each task.

[0102] Step 9:

[0103] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[0104] Step 10:

[0105] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[0106] Step 11:

[0107] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[0108] Step 12:

[0109] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[0110] Step 13:

[0111] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[0112] Step 14:

[0113] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0114] Step 15:

[0115] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[0116] Step 16:

[0117] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[0118] Step 17:

[0119] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[0120] This series of processing steps ensures that tasks are distributed efficiently, allowing users to proceed with their work systematically. Furthermore, real-time progress management prevents delays and omissions in tasks.

[0121] (Example 1)

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

[0123] Traditional business management systems often require manual prioritization and time estimation for tasks, leaving room for improvement in the efficiency of task allocation and schedule management. In particular, the lack of a function to monitor task progress in real time and update the database based on completion status makes overall task management cumbersome. As a result, individual users may not be able to perform tasks at the optimal time, potentially leading to delays in project progress.

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

[0125] In this invention, the server includes means for acquiring business information, means for setting priorities and estimated times for the acquired business information, means for distributing business based on the set priorities and estimated times, means for assigning business at the optimal timing based on the user's timetable information, means for monitoring the progress of each business, and means for receiving business completion status and updating the database. This enables efficient distribution and management of business, allowing users to perform tasks at the optimal time. Furthermore, the server's real-time monitoring of progress and database updates simplify overall business management.

[0126] "Business information" refers to data that includes detailed information such as the content, purpose, deadline, and person in charge of the work.

[0127] "Priority" is an indicator that shows the importance or urgency of a task, and is usually set on a three-tiered scale: high, medium, and low.

[0128] "Estimated time" refers to a unit of time estimated to be required to complete a specific task.

[0129] "Distributing" refers to the process by which a server assigns tasks to the appropriate personnel and time slots.

[0130] "Timetable information" refers to information that shows the user's schedule data, such as their appointments and free time.

[0131] "Monitoring progress" refers to the act of checking the progress of tasks in real time and updating the database as needed.

[0132] "Completion status" refers to information indicating that a specific task has been completed, and this information is recorded in the database by the server.

[0133] "Modifying a database" refers to the process of updating, deleting, or adding to the contents of a database based on the information received.

[0134] An "identification number" is a unique ID assigned to uniquely identify each business or piece of data.

[0135] System Overview

[0136] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system has the following functions:

[0137] 1. Acquisition of business information

[0138] 2. Setting priorities and estimated times

[0139] 3. Distribution of tasks

[0140] 4. Assignment of tasks

[0141] 5. Monitoring progress

[0142] The server works in conjunction with a database management system (e.g., MySQL®) to store and manage business information and configuration data. The terminal accepts user input and communicates data with the server. Users input business information and report progress via the terminal.

[0143] System details

[0144] Acquisition of business information

[0145] Users input work information into a terminal. This information includes the content and purpose of the work. The terminal packages this information into packets and sends an HTTP request to the server. The server stores the received work information in a database and assigns an identification number to each work.

[0146] Setting Priorities and Estimated Times

[0147] Users set priority levels (e.g., high, medium, low) and estimated time (in hours) for each task on their terminal. The terminal bundles the configuration information into a packet and sends it back to the server. The server receives the configuration information, adds it to the task information, and updates the database.

[0148] Distribution of tasks

[0149] The server retrieves business and configuration information from the database and sorts it by priority using a sorting algorithm within the program. Specifically, programs written in Python or Java (registered trademark) can be used.

[0150] Task assignment

[0151] The server retrieves the user's timetable information and assigns tasks at the optimal time based on that information. The server can use the Google Calendar API or the API of a company's scheduling software to retrieve timetable information. The schedule information for the assigned tasks is sent from the server to the terminal.

[0152] Monitoring of progress

[0153] Users mark each completed task as "completed" on their terminal. The terminal sends the completion status to the server. The server updates its database based on the received completion status and notifies the user if there are any further tasks.

[0154] Specific example

[0155] For example, the following list of tasks is entered by the user.

[0156] Report preparation (Priority: High, Estimated time: 2 hours)

[0157] Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0158] Email reply (Priority: Low, Estimated time: 30 minutes)

[0159] Users enter this information into their terminals and send it from the terminals to the server. The server stores this information in a database and assigns an identification number to it. The user then sets the priority and estimated time and sends it to the server again. The server distributes tasks based on this data, assigns them appropriately according to the user's schedule, and monitors the progress.

[0160] Examples of prompt statements

[0161] For example, here is an example of a prompt message to check the system via a generative AI model:

[0162] "Please use this system to create tomorrow's work schedule. The task list should include the following, along with priority and estimated time."

[0163] 1. Report creation (Priority: High, Estimated time: 2 hours)

[0164] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0165] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[0166] As described above, this system enables efficient distribution and management of tasks, allowing users to perform their tasks at the optimal time. Furthermore, the server monitors progress in real time and updates the database, simplifying overall task management.

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

[0168] Step 1:

[0169] The user enters work information into the terminal.

[0170] Input: Detailed information such as the nature and purpose of the work, and the person in charge.

[0171] Specific actions: The user opens the application on their device, enters work-related information such as "Create Report," "Prepare for Meeting," or "Reply to Email" into a form, and clicks the submit button.

[0172] Output: The entered business information is temporarily stored in the terminal's memory.

[0173] Step 2:

[0174] The terminal sends business information to the server.

[0175] Input: Business information entered by the user.

[0176] Specific operation: The terminal collects the entered business information into a packet and generates an HTTP request to the server. Then, it sends the request to the server.

[0177] Output: Business information is sent to the server.

[0178] Step 3:

[0179] The server receives business information and saves it to the database.

[0180] Input: Business information sent from the terminal.

[0181] Specific operation: The server receives an HTTP request and parses the business information. This information is stored in a database management system (e.g., MySQL), and an identification number is assigned to each business.

[0182] Output: Business information stored in the database and the identification number assigned to it.

[0183] Step 4:

[0184] Users set priorities and estimated timeframes for each task.

[0185] Input: Business information stored in the database.

[0186] Specific operation: The user sets the priority (high, medium, low) and estimated time (in hours) for each task using dropdown menus or input fields on their device. Once the settings are complete, they click the submit button.

[0187] Output: The set priority and estimated time are temporarily stored in the device's memory.

[0188] Step 5:

[0189] The device sends configuration information to the server.

[0190] Input: User-defined priority and estimated time.

[0191] Specific operation: The terminal bundles the configuration information into a packet, generates an HTTP request to the server again, and sends it.

[0192] Output: Configuration information is sent to the server.

[0193] Step 6:

[0194] The server adds the received configuration information to the business information and updates the database.

[0195] Input: Configuration information sent from the device.

[0196] Specific operation: The server analyzes the received configuration information and adds it to existing business information. The corresponding record in the database is then updated.

[0197] Output: Task information, including priority and estimated time, is saved to the database.

[0198] Step 7:

[0199] The server retrieves business information and configuration information from the database and sorts them using an algorithm.

[0200] Input: Business information and configuration information stored in the database.

[0201] Specific operation: The server executes SQL queries to retrieve business information and configuration information. Then, a sorting algorithm is executed within a Python or Java program to sort the business items based on priority.

[0202] Output: A list of tasks sorted by priority.

[0203] Step 8:

[0204] The server retrieves the user's timetable information and assigns tasks at the optimal time.

[0205] Input: A sorted list of tasks and user timetable information.

[0206] Specific operation: The server retrieves timetable information from the Google Calendar API or the company's scheduling software, and then assigns tasks at the appropriate times based on that information.

[0207] Output: A list of tasks assigned to each user at the optimal time.

[0208] Step 9:

[0209] The server sends the assigned work schedule to the terminal.

[0210] Input: A list of tasks assigned to the user at the optimal time.

[0211] Specific operation: The server bundles the work schedule into packets and sends an HTTP response to the user's terminal.

[0212] Output: The work schedule is sent to the terminal.

[0213] Step 10:

[0214] The terminal displays the received work schedule to the user.

[0215] Input: Work schedule sent from the server.

[0216] Specific operation: The application on the terminal analyzes the received schedule data and displays it in the GUI.

[0217] Output: The work schedule displayed to the user.

[0218] Step 11:

[0219] The user checks the schedule, makes corrections if necessary, and resends it to the server.

[0220] Input: Work schedule displayed on the terminal.

[0221] Specific operation: The user makes a modification to the schedule and clicks the resend button to send the changes to the server.

[0222] Output: The corrected schedule information is sent from the terminal to the server.

[0223] Step 12:

[0224] The server receives the changes and updates the database again.

[0225] Input: Modified schedule information submitted by the user.

[0226] Specific operation: The server analyzes the changes and updates the corresponding records in the database.

[0227] Output: The corrected schedule information is saved to the database.

[0228] Step 13:

[0229] The user starts a task and marks it as "completed" on their device each time they finish.

[0230] Input: Progress status of tasks performed by the user.

[0231] Specific action: The user clicks the "Complete" button in the application on their device when they have finished a task.

[0232] Output: The progress of the task is recorded on the terminal.

[0233] Step 14:

[0234] The terminal sends a completion status to the server.

[0235] Input: Progress status of tasks marked as completed by the user.

[0236] Specific operation: The terminal bundles the completion status into a packet, generates an HTTP request to the server, and sends it.

[0237] Output: Completion status is sent to the server.

[0238] Step 15:

[0239] The server updates the database's operational status and notifies the user if there are any new tasks.

[0240] Input: Completion status sent from the terminal.

[0241] Specific operation: The server analyzes the completion status and updates the status of the corresponding record in the database. If there is a task to assign next, it generates and sends a notification message to the user.

[0242] Output: The database's business status is updated, and the next business notification is sent to the user.

[0243] (Application Example 1)

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

[0245] The distribution and progress management of tasks in logistics centers typically rely on manual labor, making them inefficient and prone to errors. Furthermore, it is difficult to appropriately set task priorities and estimated times, and to monitor progress in real time. As a result, delays and disruptions occur, leading to a decline in overall operational efficiency.

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

[0247] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, and means for efficiently monitoring the distribution and progress of each task in the logistics center. This enables efficient and accurate distribution and progress management of tasks in the logistics center, thereby improving overall operational efficiency.

[0248] A "task list" refers to a list that enumerates specific tasks, indicating the work that the user should perform.

[0249] "Priority" is an indicator that shows the importance or urgency of a task, and is expressed in grades such as "high," "medium," and "low."

[0250] "Estimated time" refers to the predicted time required to complete a specific task, and is expressed in hours.

[0251] "Distribution" refers to the process of organizing tasks in the appropriate order and assigning them to each user based on set priorities and estimated timeframes.

[0252] "Schedule information" refers to information that indicates the time slots for each user's individual appointments and tasks, and is used for assigning tasks.

[0253] "Progress status" refers to status information that indicates the stage of a task, and requires real-time monitoring.

[0254] A "logistics center" refers to a facility where operations such as storage, sorting, processing, and shipping of goods are carried out, and it is a place where large-scale inventory management and logistics operations take place.

[0255] "Efficient" refers to a state where there is no waste, and the resources and time required to achieve a goal are minimized.

[0256] "Distribution and progress monitoring" refers to a series of operations that involve appropriately assigning tasks and monitoring their progress in real time.

[0257] "Completion status" refers to information indicating that a specific task has been completed, and this information is reflected in other systems when updated in the database.

[0258] A "database" refers to an information management system that organizes and stores large amounts of data, making it possible to quickly search and use it as needed.

[0259] This invention is a system for efficiently distributing and managing the progress of tasks in a logistics center. The system operates collaboratively among a server, terminals, and users, providing a series of functions including obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[0260] System Configuration

[0261] The system consists of the following main components:

[0262] Server: Stores data, distributes tasks, and monitors progress.

[0263] Terminals (smartphones, robots): These devices handle data input from the user and display the received information.

[0264] User: Enter tasks into the task list, set priorities and estimated times, and check and update progress.

[0265] Hardware and software to use

[0266] Hardware:

[0267] Smartphone (a typical smartphone device)

[0268] Robots (such as automated guided vehicles and picking robots)

[0269] software:

[0270] Server programs (Python, Flask API, etc.)

[0271] Databases (MySQL, PostgreSQL, etc.)

[0272] Client applications (mobile apps, robot control software)

[0273] Specific example

[0274] Obtaining a list of tasks

[0275] The user inputs each operation carried out at the logistics center into the application on the smartphone. For example, there are operations such as picking, packing, and quality inspection. The terminal sends this operation list to the server, and the server saves the list in the database and assigns a unique ID to each operation.

[0276] Setting of priority and estimated time

[0277] The user sets the priority (high, medium, low) and estimated time (in time units) for each operation in the application. The terminal sends this setting information to the server, and the server updates the database based on the received information.

[0278] Assignment and allocation of operations

[0279] The server rearranges the operations based on the set priority and estimated time and allocates them to each user in the optimal order. In particular, since efficient operation allocation is required at the logistics center, the server considers the schedule information of each worker and robot and allocates the operations at an appropriate timing.

[0280] Monitoring of progress

[0281] The user starts the assigned operation and sends the completion status to the server through the terminal when it is completed. The server reflects this information in the database and notifies the user of the next operation, thereby realizing real-time monitoring of the progress.

[0282] Examples of prompt sentences

[0283] Examples of prompt sentences that can be used when explaining this application with a generative AI model are as follows:

[0284] "Please explain the operation distribution system in the logistics center."

[0285] "Please explain in detail how to set the priority and estimated time of tasks and distribute them efficiently."

[0286] "Please explain how the staff and robots in the logistics center monitor tasks and update the progress in real time."

[0287] The flow of the specific process in Application Example 1 will be described using FIG. 12.

[0288] Step 1: Obtaining the task list

[0289] The user inputs each task (such as picking, packing, quality inspection, etc.) in the logistics center into the smartphone application. This input data includes the task name, details, and its related information. The terminal sends this task list to the server. The server saves the received task list in the database and assigns a unique ID to each task. The input data is the task name and details, and the output data is the task list with unique IDs assigned.

[0290] Step 2: Setting the priority and estimated time

[0291] The user sets the priority (high, medium, low) and estimated time (in time units) for each task via the smartphone application. The terminal sends this setting information to the server. The server updates the task list in the database based on the received information. The input data is the priority and estimated time, and the output data is the updated task list.

[0292] Step 3: Task distribution

[0293] The server sorts the tasks based on the set priority and estimated time. In particular, in the logistics center, efficient task distribution is required, so the server considers the schedule information of each worker and determines the optimal order for the next task distribution. The input data is the priority and estimated time, and the output data is the sorted task list.

[0294] Step 4: Assigning tasks

[0295] The server assigns tasks to each user at the optimal time based on their schedule information. The server compares the schedule information with a sorted list of tasks, assigns tasks to each user at their most suitable time, and sends the assignment information to the terminal. Input data consists of schedule information and a sorted list of tasks, while output data is the assignment schedule for each user.

[0296] Step 5: Confirm and accept the work schedule.

[0297] The terminal displays the received work schedule on the user's smartphone. The user can review the schedule and make corrections as needed. The user's corrections are sent back to the server via the terminal. The server updates the database based on the corrections. The input data is the schedule information corrected by the user, and the output data is the updated schedule information.

[0298] Step 6: Monitoring progress

[0299] The user starts the assigned task and sends a "completed" status to the server via their terminal upon completion. The server receives the completion status and updates the task status in the database. If there is another task to assign, the server notifies the user. The input data is the status of the completed task, and the output data is the updated task status and the next task notification.

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

[0301] System Overview

[0302] The present invention realizes optimal task performance according to the user's state by combining an emotion engine that recognizes the user's emotions with a system for efficiently distributing and managing tasks. The server, the terminal, the user, and the emotion engine cooperate to operate, aiming to improve task efficiency and reduce user stress.

[0303] Program processing

[0304] The program of this system operates with the server, the terminal, the user, and the emotion engine each playing their respective roles as follows.

[0305] Obtaining and setting the task list

[0306] User: Input the task list into the terminal. For example, input tasks such as "report creation", "meeting preparation", "email reply".

[0307] Terminal: Transmit the input task list to the server.

[0308] Server: Receive the task list and save it in the database. A unique ID is assigned to each task.

[0309] User: Set the priority (e.g., high, medium, low) and estimated time (in time units) for each task.

[0310] Terminal: Save the setting information in a format for transmission to the server.

[0311] Server: Add the received setting information to the task list and update the database.

[0312] Task distribution and assignment

[0313] Server: Retrieve the task list and its setting information from the database, sort the tasks in order of priority using an algorithm, and distribute the tasks taking into account the input from the emotion engine.

[0314] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[0315] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is under high stress, it will assign lower-priority tasks for relaxation or rest.

[0316] Confirmation and acceptance of the work schedule.

[0317] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[0318] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[0319] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[0320] Server: Updates the database again based on the received correction information.

[0321] Monitoring progress

[0322] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0323] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[0324] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[0325] Specific example

[0326] For example, the following task list is entered by the user:

[0327] 1. Report creation (Priority: High, Estimated time: 2 hours)

[0328] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0329] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[0330] Using an Emotion Engine

[0331] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[0332] 2. Emotion Engine: If the system determines that the user is in a high-stress state, it sends this information to the server.

[0333] 3. Server: Considering the emotion engine data, adjust task priorities and change the next task to be performed to reduce user stress as much as possible. Also, suggest breaks at appropriate times.

[0334] This allows users to receive task assignments that take their emotional state into consideration, enabling a more comfortable work environment. By having the server constantly monitor progress and emotional state, work efficiency can be improved while reducing mental stress.

[0335] The following describes the processing flow.

[0336] Step 1:

[0337] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[0338] Step 2:

[0339] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[0340] Step 3:

[0341] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[0342] Step 4:

[0343] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[0344] Step 5:

[0345] Terminal: Sends information about the configured priority and estimated time to the server.

[0346] Step 6:

[0347] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[0348] Step 7:

[0349] Server: Retrieves a list of tasks and their configuration information from the database, and uses an algorithm to sort the tasks in order of priority.

[0350] Step 8:

[0351] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[0352] Step 9:

[0353] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is in a high-stress state, it assigns lower-priority tasks to encourage relaxation and rest.

[0354] Step 10:

[0355] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[0356] Step 11:

[0357] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[0358] Step 12:

[0359] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[0360] Step 13:

[0361] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[0362] Step 14:

[0363] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[0364] Step 15:

[0365] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0366] Step 16:

[0367] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[0368] Step 17:

[0369] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[0370] Step 18:

[0371] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[0372] This allows for efficient task distribution, enabling users to proceed with their work systematically. Furthermore, real-time management of progress and emotional states improves work efficiency while reducing mental stress.

[0373] (Example 2)

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

[0375] While conventional business management systems can efficiently distribute and manage tasks, they struggle to adjust tasks while considering the user's emotional state. This led to increased mental burden on users and decreased productivity. There was a need for a system that could dynamically adjust task priorities and allocation based on the user's emotional state, thereby improving efficiency and reducing user stress.

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

[0377] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for analyzing the user's emotional state using an emotion engine that recognizes the user's state, means for assigning tasks at the optimal timing based on the user's emotional state and schedule information, means for monitoring the progress of each task, and means for dynamically adjusting the priority and distribution of tasks according to the emotional state. This enables efficient distribution and management of tasks while allowing for flexible task adjustments that take into account the user's emotional state.

[0378] A "task list" is a list of the names and contents of each task that the user is to perform.

[0379] "Priority" is an indicator that shows the order and importance of tasks to be performed.

[0380] "Estimated time" is an estimate of the time a user believes they will need to complete each task.

[0381] "Distribution" is the process of assigning multiple tasks based on specific criteria.

[0382] "User state" refers to the user's emotional state, health status, activity level, etc.

[0383] An "emotion engine" is a device or program that analyzes a user's facial expressions, voice, and behavioral data to recognize their emotional state.

[0384] "Schedule information" refers to time-related information such as the user's appointments and schedules.

[0385] "Progress status" indicates the extent to which each task has been completed.

[0386] "Dynamic adjustment" refers to the act of instantly changing settings and allocations based on real-time data and status.

[0387] A "server" is a central computing system used for data processing, storage, and communication.

[0388] This invention combines a system for the efficient distribution and management of tasks with an emotion engine that recognizes user emotions, thereby achieving optimal task execution according to the user's state. The server, terminal, user, and emotion engine work together to improve work efficiency and reduce user stress.

[0389] System Overview

[0390] This system uses the following hardware and software:

[0391] Server: A central computing system that handles data processing, storage, and communication. It manages task lists, executes algorithms, and processes data from emotion engines, among other things.

[0392] Terminal: A device used by users to input and confirm information (such as a PC, smartphone, or tablet). It is responsible for sending user input to the server and displaying the information from the server to the user.

[0393] Emotion engine: A device or program for recognizing a user's emotional state. It analyzes the user's facial expressions and voice using a camera and microphone to recognize their emotional state in real time.

[0394] Obtaining and setting up the task list

[0395] User: Enters a list of tasks through the terminal interface. Examples of specific tasks include "report creation," "meeting preparation," and "email reply."

[0396] Terminal: Sends the entered task list to the server. The communication module is used to send the task list as a POST request to the specified API endpoint.

[0397] Server: Stores the received list of tasks in the database and assigns a unique ID to each task.

[0398] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[0399] Terminal: Sends the configured information to the server.

[0400] Server: Adds the received configuration information to the task list and updates the database.

[0401] Work distribution and allocation

[0402] Server: Retrieves a list of tasks and their configuration information from the database. The retrieved list of tasks is then sorted by priority using an algorithm.

[0403] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time.

[0404] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state.

[0405] Confirmation and acceptance of the work schedule.

[0406] Server: Assigns tasks at the optimal time, taking into account the user's schedule information.

[0407] Terminal: Displays received work schedules to the user.

[0408] User: Check the schedule and enter any necessary corrections.

[0409] Terminal: Resends correction information to the server.

[0410] Server: Updates the database again based on the received correction information.

[0411] Monitoring progress

[0412] User: Start a task and mark it as "Completed" on the terminal as it is finished.

[0413] Terminal: Notifies the server of the status of completed tasks.

[0414] Server: Based on the received completion status, the server updates the task status in the database and prepares to assign the next task.

[0415] Using an Emotion Engine

[0416] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[0417] 2. Emotion Engine: When it determines that the user is in a high-stress state, it sends that information to the server.

[0418] 3. Server: Considers the emotion engine's data and adjusts task priorities. For example, it might change the next task to be performed to reduce stress and suggest a break.

[0419] This allows users to receive optimal task assignments tailored to their emotional state, enabling them to work comfortably. Furthermore, the server constantly monitors progress and emotional state, improving work efficiency and reducing mental stress.

[0420] Example of a prompt

[0421] The following are specific examples of prompt statements for generative AI models:

[0422] "Please describe an algorithm that adjusts task priorities based on the user's emotional state."

[0423] "Please explain the technical mechanism of an emotion engine that recognizes user emotions in real time, and how it can be applied."

[0424] The above describes the details of embodiments for carrying out the present invention.

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

[0426] Step 1:

[0427] User: Enter the task list into the terminal. For example, specific tasks such as "write a report," "prepare for a meeting," and "reply to emails" are entered using the terminal's dedicated application.

[0428] Input: Job description

[0429] Output: A list of tasks is displayed on the terminal.

[0430] Step 2:

[0431] Terminal: Sends the entered task list to the server. The terminal uses a communication module to send the task list as a POST request to the specified API endpoint.

[0432] Input: User-entered list of tasks

[0433] Output: The server receives the task list.

[0434] Step 3:

[0435] Server: Saves the received list of tasks to the database and assigns a unique ID to each task. Executes an INSERT statement into the database.

[0436] Input: Task list sent from the terminal

[0437] Output: List of tasks and unique IDs stored in the database

[0438] Step 4:

[0439] User: Set priority (high, medium, low) and estimated time (in hours) for each task. Enter detailed information for each task through the terminal interface.

[0440] Input: Task priority and estimated time

[0441] Output: The settings information is reflected on the device.

[0442] Step 5:

[0443] Terminal: Sends user-configured information to the server. The configuration information is sent to the server as a POST request using a communication module.

[0444] Input: Priority and estimated time for the configured task

[0445] Output: The server receives the configuration information.

[0446] Step 6:

[0447] Server: Adds the received configuration information to the task list and updates the database. Executes an UPDATE statement against the database.

[0448] Input: Configuration information sent from the device

[0449] Output: Updated task list in the database

[0450] Step 7:

[0451] Server: Retrieves a list of tasks and their configuration information from the database. Executes a SELECT statement to read the necessary task information.

[0452] Input: Task list and configuration information in the database

[0453] Output: Acquired task list and configuration information

[0454] Step 8:

[0455] Server: The retrieved list of tasks is sorted by priority using an algorithm. The algorithm is implemented in Python or similar languages, and sorts the tasks considering priority and estimated time.

[0456] Input: Task list and its settings information

[0457] Output: Task list sorted by priority

[0458] Step 9:

[0459] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time. The emotion engine acquires and processes data from the camera and microphone.

[0460] Input: User's facial expressions, voice, and behavioral data

[0461] Output: Analysis results of the user's emotional state

[0462] Step 10:

[0463] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. Reads emotion data from storage and applies it to the current task list.

[0464] Input: Emotional state data from the emotion engine

[0465] Output: Adjusted task list

[0466] Step 11:

[0467] Server: Combines user schedule information with other data to assign tasks at the optimal time. Calendar information is also retrieved from the database and applied to task assignments.

[0468] Input: User's schedule information and a list of tasks sorted by priority.

[0469] Output: Assigned work schedule

[0470] Step 12:

[0471] Terminal: Displays received work schedules to the user. Presents the schedule visually through a dedicated interface.

[0472] Input: Work schedule sent from the server

[0473] Output: Schedule displayed on the user's terminal

[0474] Step 13:

[0475] User: Check the schedule and enter any necessary corrections. Enter the correction information using the terminal interface.

[0476] Input: Confirmation and modification of work schedule.

[0477] Output: Input of correction information

[0478] Step 14:

[0479] Terminal: Resends correction information to the server. The correction information is sent to the server as a POST request using the communication module.

[0480] Input: Correction information entered by the user

[0481] Output: The server receives the correction information.

[0482] Step 15:

[0483] Server: Based on the received correction information, update the database again. Execute the UPDATE statement to update the data.

[0484] Input: Correction information sent from the device

[0485] Output: Updated database

[0486] Step 16:

[0487] User: Start a task and mark it as "Completed" on the terminal as it is finished. Click the completion button using a dedicated button or checkbox.

[0488] Input: Mark as completed

[0489] Output: Tasks marked as completed

[0490] Step 17:

[0491] Terminal: Notifies the server of the status of completed tasks. Formats the data and sends it to the server via the communication module.

[0492] Input: User-marked task completion status

[0493] Output: Completion status received by the server

[0494] Step 18:

[0495] Server: Updates the database task status based on the received completion status. Executes an UPDATE statement to change the task status to "Completed". Prepares for assigning the next task.

[0496] Input: Completion status sent from the terminal

[0497] Output: Updated database business status

[0498] The above outlines the specific processing steps of a system that efficiently distributes and manages tasks. This enables flexible task adjustments that take into account the emotional state of users.

[0499] (Application Example 2)

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

[0501] In today's work environment, there is a strong demand for improved work efficiency and reduced worker stress. However, conventional systems focus on improving work efficiency while failing to adequately consider the emotional state and mental burden of workers. As a result, while work efficiency may improve, worker stress and fatigue may increase, potentially leading to a decrease in overall efficiency and productivity. In particular, in workplaces such as factories, excessive stress is a problem as it increases the risk of work errors and accidents. Against this backdrop, there is a need for a system that analyzes the emotional state of workers in real time and dynamically adjusts work accordingly.

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

[0503] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for assigning tasks at the optimal timing based on the user's schedule information, means for monitoring the progress of each task, means for analyzing the user's emotional state in real time using a camera and voice input device, and means for dynamically adjusting the priority and distribution of tasks based on the analyzed emotional state. This makes it possible to monitor the user's emotional state in real time and propose optimal task distribution and breaks based on it.

[0504] A "task list" is a compilation of multiple tasks that a user must perform.

[0505] "Priority" is an indicator that shows the importance and urgency of each task.

[0506] "Estimated time" is an estimate of the time required to complete each task.

[0507] "User schedule information" refers to the timetable and schedule information that users use to carry out their daily activities.

[0508] "Progress status" refers to the state of how far along a task is.

[0509] "Cameras and audio input devices" refer to hardware used to capture the user's facial expressions and voice.

[0510] "Emotional state" refers to a mental state that includes the type and intensity of emotions a user expresses.

[0511] "Dynamic adjustment" refers to changing something in real time according to the situation.

[0512] This invention is a system aimed at improving operational efficiency and reducing worker stress in workplaces such as factories. It involves collaboration between a server, a terminal, and a user. An emotion engine analyzes the user's emotional state in real time and dynamically adjusts tasks based on that analysis.

[0513] The overall system consists of the following elements:

[0514] 1. Server: Plays a central role and manages the database.

[0515] 2. Terminal: Operated by the user, it is used to input task lists and report completion status.

[0516] 3. User: A worker who performs tasks while operating a terminal.

[0517] 4. Emotion Engine: Analyzes the user's facial expressions and voice data to recognize their emotional state.

[0518] Detailed system configuration and functions

[0519] Obtaining and setting up the task list

[0520] User: Use the terminal to enter a list of tasks. For example, enter tasks such as "assembly line work," "quality inspection," and "maintenance work."

[0521] Terminal: Sends the entered list of tasks to the server.

[0522] Server: Receives the task list and saves it to the database. Each task is assigned a unique ID.

[0523] User: Set priority and estimated time for each task.

[0524] Terminal: Sends configuration information to the server.

[0525] Server: Adds the received configuration information to the task list and updates the database.

[0526] Work distribution and allocation

[0527] Server: Retrieves a list of tasks and their configuration information from the database, sorts the tasks by priority using an algorithm, and distributes the tasks while also taking into account input from the emotion engine.

[0528] Emotion Engine: Uses cameras and voice input devices to analyze the user's facial expressions, voice, and behavioral data in real time to recognize their emotional state (e.g., stress, fatigue, satisfaction).

[0529] Server: Receives data from the emotion engine and adjusts task priorities and allocations based on the user's emotional state. If the user is in a high-stress state, it assigns lower-priority tasks or breaks.

[0530] Confirmation and acceptance of the work schedule.

[0531] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[0532] Terminal: Displays received work schedules to the user, who may review and modify the schedule.

[0533] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal sends the correction information to the server.

[0534] Server: Updates the database based on the received correction information.

[0535] Monitoring progress

[0536] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0537] Terminal: Notifies the server that the user has completed their task.

[0538] Server: Based on the received completion status, update the database task status and prepare to assign the next task.

[0539] Specific example

[0540] For example, if a user is performing "assembly line work" (priority: high, estimated time: 120 minutes) in a factory, and the emotion engine detects a high level of stress from the user's facial expressions, it will automatically suggest a "short break." This will result in a notification on the device saying, "Let's take a short break," which can reduce the user's stress.

[0541] Examples of prompts to input into a generative AI model:

[0542] "Please generate code that analyzes a camera's face in real time and suggests taking a break if a stressed state is detected."

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

[0544] Step 1:

[0545] The user inputs a list of tasks via a terminal. The input includes task descriptions such as "assembly line work," "quality inspection," and "maintenance work." The terminal sends this task list to the server. The server receives the task list, assigns a unique ID to each task, and stores it in a database. At this stage, data processing involves mapping the task description to its ID.

[0546] Step 2:

[0547] Users set a priority (high, medium, low) and estimated time (in minutes or hours) for each task. This configuration information is sent from the terminal to the server. The server adds the received configuration information to the task list and updates the database. At this stage, a data calculation is performed to merge the priority and estimated time information into the task list.

[0548] Step 3:

[0549] The server retrieves a list of tasks and their configuration information from the database and uses an algorithm to sort the tasks by priority. Emotional data from the emotion engine is also considered during this process. Tasks are dynamically distributed based on the emotional state data. This emotional data processing includes the user's real-time stress level and fatigue level.

[0550] Step 4:

[0551] The emotion engine uses cameras and voice input devices to analyze the user's facial expressions and voice in real time and recognize their emotional state (stress, fatigue, satisfaction). Specific operations include preprocessing of image and audio data, feature extraction, and emotion recognition through classification models. The user's facial images and voice are provided as input, and emotional states such as "high stress" or "fatigue" are obtained as output.

[0552] Step 5:

[0553] The server receives data from the emotion engine and dynamically adjusts the priority and allocation of tasks based on the user's emotional state. For example, if a user is in a high-stress state, it may assign lower-priority tasks or suggest short breaks. Here, the emotional data is input into the task allocation algorithm, and the output is an adjusted list of tasks.

[0554] Step 6:

[0555] The server assigns tasks at the optimal time, taking into account the user's schedule information. The terminal displays the received task schedule to the user. The user checks the schedule, makes any necessary corrections, and enters the corrections into the terminal. The terminal sends the correction information to the server, and the server updates the database based on the received correction information.

[0556] Step 7:

[0557] The user starts a task and marks it as "completed" on their terminal upon completion. The terminal notifies the server of this completion status. The server updates the task status in the database based on the received completion status and prepares to assign the next task. At this point, as part of the data processing, the completion status is marked in the task list, and the next task is assigned by the server.

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

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

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

[0561] [Second Embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

[0574] System Overview

[0575] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system includes functions for obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[0576] Program processing

[0577] The program of this system operates with the server, terminal, and user each fulfilling their respective roles as follows:

[0578] Obtaining a list of tasks

[0579] User: Enters a list of tasks (e.g., report creation, meeting preparation, email reply) into the terminal.

[0580] Terminal: Sends the entered list of tasks to the server.

[0581] Server: Receives the task list and saves it to the database. Assigns a unique ID to each task for management.

[0582] Priority and time settings

[0583] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[0584] Terminal: Saves configuration information in a format that sends it to the server.

[0585] Server: Adds the received configuration information to the task list and updates the database.

[0586] Distribution of tasks

[0587] Server: Retrieves a list of tasks and their configuration information from the database, uses an algorithm to sort the tasks by priority, and prepares them for distribution to each user in the next step.

[0588] Sorting by priority: Tasks with particularly high priority are placed first.

[0589] Distribute tasks efficiently, taking estimated time into consideration.

[0590] Task assignment

[0591] Server: Retrieves user schedule information and assigns each task at the optimal time.

[0592] Server: Sends the assigned work schedule to the terminal.

[0593] Confirmation and acceptance of the work schedule.

[0594] Terminal: Displays received work schedules to the user.

[0595] User: Check the schedule, make any necessary corrections, and resend it to the server.

[0596] Server: Receives the changes and updates the database again.

[0597] Monitoring progress

[0598] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0599] Terminal: Sends completion status to the server.

[0600] Server: Updates the task status in the database and notifies the user if there are tasks to assign next.

[0601] Specific example

[0602] For example, the following task list is entered by the user:

[0603] 1. Report creation (Priority: High, Estimated time: 2 hours)

[0604] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0605] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[0606] Obtaining and setting up the task list

[0607] 1. User: Enter the task list into the terminal (e.g., write a report, prepare for a meeting, reply to emails).

[0608] 2. Terminal: Sends the task list to the server.

[0609] 3. Server: Stores the task list in the database and assigns a unique ID to each task.

[0610] 4. User: Enter priority and estimated time for each task.

[0611] 5. Terminal: Sends configuration information to the server.

[0612] Work distribution and allocation

[0613] 1. Server: Prioritize tasks based on their importance (e.g., report creation → meeting preparation → email reply).

[0614] 2. Server: Assigns the rearranged tasks to each user's schedule at the most opportune time.

[0615] 3. Server: Sends schedule information to the terminal.

[0616] Monitoring of work schedules and progress

[0617] 1. Terminal: Displays the assigned schedule to the user.

[0618] 2. User: Starts tasks one after another and marks them as "completed" on the terminal upon completion.

[0619] 3. Terminal: Sends completion status to the server.

[0620] 4. Server: Updates the database status and notifies users of the next task.

[0621] This allows for efficient task distribution, enabling users to effectively complete their tasks. Furthermore, the server constantly monitors progress and updates the database in real time, simplifying overall project management.

[0622] The following describes the processing flow.

[0623] Step 1:

[0624] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[0625] Step 2:

[0626] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[0627] Step 3:

[0628] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[0629] Step 4:

[0630] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[0631] Step 5:

[0632] Terminal: Sends information about the configured priority and estimated time to the server.

[0633] Step 6:

[0634] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[0635] Step 7:

[0636] Server: Retrieves a list of tasks and their configuration information from the database. After retrieval, it uses an algorithm to sort the tasks in order of priority.

[0637] Step 8:

[0638] Server: Executes a distribution algorithm based on the sorted tasks and distributes them to each user. At this time, it distributes tasks efficiently, taking into account the estimated time for each task.

[0639] Step 9:

[0640] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[0641] Step 10:

[0642] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[0643] Step 11:

[0644] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[0645] Step 12:

[0646] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[0647] Step 13:

[0648] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[0649] Step 14:

[0650] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0651] Step 15:

[0652] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[0653] Step 16:

[0654] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[0655] Step 17:

[0656] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[0657] This series of processing steps ensures that tasks are distributed efficiently, allowing users to proceed with their work systematically. Furthermore, real-time progress management prevents delays and omissions in tasks.

[0658] (Example 1)

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

[0660] Traditional business management systems often require manual prioritization and time estimation for tasks, leaving room for improvement in the efficiency of task allocation and schedule management. In particular, the lack of a function to monitor task progress in real time and update the database based on completion status makes overall task management cumbersome. As a result, individual users may not be able to perform tasks at the optimal time, potentially leading to delays in project progress.

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

[0662] In this invention, the server includes means for acquiring business information, means for setting priorities and estimated times for the acquired business information, means for distributing business based on the set priorities and estimated times, means for assigning business at the optimal timing based on the user's timetable information, means for monitoring the progress of each business, and means for receiving business completion status and updating the database. This enables efficient distribution and management of business, allowing users to perform tasks at the optimal time. Furthermore, the server's real-time monitoring of progress and database updates simplify overall business management.

[0663] "Business information" refers to data that includes detailed information such as the content, purpose, deadline, and person in charge of the work.

[0664] "Priority" is an indicator that shows the importance or urgency of a task, and is usually set on a three-tiered scale: high, medium, and low.

[0665] "Estimated time" refers to a unit of time estimated to be required to complete a specific task.

[0666] "Distributing" refers to the process by which a server assigns tasks to the appropriate personnel and time slots.

[0667] "Timetable information" refers to information that shows the user's schedule data, such as their appointments and free time.

[0668] "Monitoring progress" refers to the act of checking the progress of tasks in real time and updating the database as needed.

[0669] "Completion status" refers to information indicating that a specific task has been completed, and this information is recorded in the database by the server.

[0670] "Modifying a database" refers to the process of updating, deleting, or adding to the contents of a database based on the information received.

[0671] An "identification number" is a unique ID assigned to uniquely identify each business or piece of data.

[0672] System Overview

[0673] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system has the following functions:

[0674] 1. Acquisition of business information

[0675] 2. Setting priorities and estimated times

[0676] 3. Distribution of tasks

[0677] 4. Assignment of tasks

[0678] 5. Monitoring progress

[0679] The server works in conjunction with a database management system (e.g., MySQL) to store and manage business information and configuration data. The terminal accepts user input and communicates data with the server. Users input business information and report progress via the terminal.

[0680] System details

[0681] Acquisition of business information

[0682] Users input work information into a terminal. This information includes the content and purpose of the work. The terminal packages this information into packets and sends an HTTP request to the server. The server stores the received work information in a database and assigns an identification number to each work.

[0683] Setting Priorities and Estimated Times

[0684] Users set priority levels (e.g., high, medium, low) and estimated time (in hours) for each task on their terminal. The terminal bundles the configuration information into a packet and sends it back to the server. The server receives the configuration information, adds it to the task information, and updates the database.

[0685] Distribution of tasks

[0686] The server retrieves business and configuration information from the database and sorts it by priority using a sorting algorithm within the program. Specifically, Python or Java programs can be used.

[0687] Task assignment

[0688] The server retrieves the user's timetable information and assigns tasks at the optimal time based on that information. The server can use the Google Calendar API or the API of a company's scheduling software to retrieve timetable information. The schedule information for the assigned tasks is sent from the server to the terminal.

[0689] Monitoring of progress

[0690] Users mark each completed task as "completed" on their terminal. The terminal sends the completion status to the server. The server updates its database based on the received completion status and notifies the user if there are any further tasks.

[0691] Specific example

[0692] For example, the following list of tasks is entered by the user.

[0693] Report preparation (Priority: High, Estimated time: 2 hours)

[0694] Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0695] Email reply (Priority: Low, Estimated time: 30 minutes)

[0696] Users enter this information into their terminals and send it from the terminals to the server. The server stores this information in a database and assigns an identification number to it. The user then sets the priority and estimated time and sends it to the server again. The server distributes tasks based on this data, assigns them appropriately according to the user's schedule, and monitors the progress.

[0697] Examples of prompt statements

[0698] For example, here is an example of a prompt message to check the system via a generative AI model:

[0699] "Please use this system to create tomorrow's work schedule. The task list should include the following, along with priority and estimated time."

[0700] 1. Report creation (Priority: High, Estimated time: 2 hours)

[0701] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0702] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[0703] As described above, this system enables efficient distribution and management of tasks, allowing users to perform their tasks at the optimal time. Furthermore, the server monitors progress in real time and updates the database, simplifying overall task management.

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

[0705] Step 1:

[0706] The user enters work information into the terminal.

[0707] Input: Detailed information such as the nature and purpose of the work, and the person in charge.

[0708] Specific actions: The user opens the application on their device, enters work-related information such as "Create Report," "Prepare for Meeting," or "Reply to Email" into a form, and clicks the submit button.

[0709] Output: The entered business information is temporarily stored in the terminal's memory.

[0710] Step 2:

[0711] The terminal sends business information to the server.

[0712] Input: Business information entered by the user.

[0713] Specific operation: The terminal collects the entered business information into a packet and generates an HTTP request to the server. Then, it sends the request to the server.

[0714] Output: Business information is sent to the server.

[0715] Step 3:

[0716] The server receives business information and saves it to the database.

[0717] Input: Business information sent from the terminal.

[0718] Specific operation: The server receives an HTTP request and parses the business information. This information is stored in a database management system (e.g., MySQL), and an identification number is assigned to each business.

[0719] Output: Business information stored in the database and the identification number assigned to it.

[0720] Step 4:

[0721] Users set priorities and estimated timeframes for each task.

[0722] Input: Business information stored in the database.

[0723] Specific operation: The user sets the priority (high, medium, low) and estimated time (in hours) for each task using dropdown menus or input fields on their device. Once the settings are complete, they click the submit button.

[0724] Output: The set priority and estimated time are temporarily stored in the device's memory.

[0725] Step 5:

[0726] The device sends configuration information to the server.

[0727] Input: User-defined priority and estimated time.

[0728] Specific operation: The terminal bundles the configuration information into a packet, generates an HTTP request to the server again, and sends it.

[0729] Output: Configuration information is sent to the server.

[0730] Step 6:

[0731] The server adds the received configuration information to the business information and updates the database.

[0732] Input: Configuration information sent from the device.

[0733] Specific operation: The server analyzes the received configuration information and adds it to existing business information. The corresponding record in the database is then updated.

[0734] Output: Task information, including priority and estimated time, is saved to the database.

[0735] Step 7:

[0736] The server retrieves business information and configuration information from the database and sorts them using an algorithm.

[0737] Input: Business information and configuration information stored in the database.

[0738] Specific operation: The server executes SQL queries to retrieve business information and configuration information. Then, a sorting algorithm is executed within a Python or Java program to sort the business items based on priority.

[0739] Output: A list of tasks sorted by priority.

[0740] Step 8:

[0741] The server retrieves the user's timetable information and assigns tasks at the optimal time.

[0742] Input: A sorted list of tasks and user timetable information.

[0743] Specific operation: The server retrieves timetable information from the Google Calendar API or the company's scheduling software, and then assigns tasks at the appropriate times based on that information.

[0744] Output: A list of tasks assigned to each user at the optimal time.

[0745] Step 9:

[0746] The server sends the assigned work schedule to the terminal.

[0747] Input: A list of tasks assigned to the user at the optimal time.

[0748] Specific operation: The server bundles the work schedule into packets and sends an HTTP response to the user's terminal.

[0749] Output: The work schedule is sent to the terminal.

[0750] Step 10:

[0751] The terminal displays the received work schedule to the user.

[0752] Input: Work schedule sent from the server.

[0753] Specific operation: The application on the terminal analyzes the received schedule data and displays it in the GUI.

[0754] Output: The work schedule displayed to the user.

[0755] Step 11:

[0756] The user checks the schedule, makes corrections if necessary, and resends it to the server.

[0757] Input: Work schedule displayed on the terminal.

[0758] Specific operation: The user makes a modification to the schedule and clicks the resend button to send the changes to the server.

[0759] Output: The corrected schedule information is sent from the terminal to the server.

[0760] Step 12:

[0761] The server receives the changes and updates the database again.

[0762] Input: Modified schedule information submitted by the user.

[0763] Specific operation: The server analyzes the changes and updates the corresponding records in the database.

[0764] Output: The corrected schedule information is saved to the database.

[0765] Step 13:

[0766] The user starts a task and marks it as "completed" on their device each time they finish.

[0767] Input: Progress status of tasks performed by the user.

[0768] Specific action: The user clicks the "Complete" button in the application on their device when they have finished a task.

[0769] Output: The progress of the task is recorded on the terminal.

[0770] Step 14:

[0771] The terminal sends a completion status to the server.

[0772] Input: Progress status of tasks marked as completed by the user.

[0773] Specific operation: The terminal bundles the completion status into a packet, generates an HTTP request to the server, and sends it.

[0774] Output: Completion status is sent to the server.

[0775] Step 15:

[0776] The server updates the database's operational status and notifies the user if there are any new tasks.

[0777] Input: Completion status sent from the terminal.

[0778] Specific operation: The server analyzes the completion status and updates the status of the corresponding record in the database. If there is a task to assign next, it generates and sends a notification message to the user.

[0779] Output: The database's business status is updated, and the next business notification is sent to the user.

[0780] (Application Example 1)

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

[0782] The distribution and progress management of tasks in logistics centers typically rely on manual labor, making them inefficient and prone to errors. Furthermore, it is difficult to appropriately set task priorities and estimated times, and to monitor progress in real time. As a result, delays and disruptions occur, leading to a decline in overall operational efficiency.

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

[0784] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, and means for efficiently monitoring the distribution and progress of each task in the logistics center. This enables efficient and accurate distribution and progress management of tasks in the logistics center, thereby improving overall operational efficiency.

[0785] A "task list" refers to a list that enumerates specific tasks, indicating the work that the user should perform.

[0786] "Priority" is an indicator that shows the importance or urgency of a task, and is expressed in grades such as "high," "medium," and "low."

[0787] "Estimated time" refers to the predicted time required to complete a specific task, and is expressed in hours.

[0788] "Distribution" refers to the process of organizing tasks in the appropriate order and assigning them to each user based on set priorities and estimated timeframes.

[0789] "Schedule information" refers to information that indicates the time slots for each user's individual appointments and tasks, and is used for assigning tasks.

[0790] "Progress status" refers to status information that indicates the stage of a task, and requires real-time monitoring.

[0791] A "logistics center" refers to a facility where operations such as storage, sorting, processing, and shipping of goods are carried out, and it is a place where large-scale inventory management and logistics operations take place.

[0792] "Efficient" refers to a state where there is no waste, and the resources and time required to achieve a goal are minimized.

[0793] "Distribution and progress monitoring" refers to a series of operations that involve appropriately assigning tasks and monitoring their progress in real time.

[0794] "Completion status" refers to information indicating that a specific task has been completed, and this information is reflected in other systems when updated in the database.

[0795] A "database" refers to an information management system that organizes and stores large amounts of data, making it possible to quickly search and use it as needed.

[0796] This invention is a system for efficiently distributing and managing the progress of tasks in a logistics center. The system operates collaboratively among a server, terminals, and users, providing a series of functions including obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[0797] System Configuration

[0798] The system consists of the following main components:

[0799] Server: Stores data, distributes tasks, and monitors progress.

[0800] Terminals (smartphones, robots): These devices handle data input from the user and display the received information.

[0801] User: Enter tasks into the task list, set priorities and estimated times, and check and update progress.

[0802] Hardware and software to use

[0803] Hardware:

[0804] Smartphone (a typical smartphone device)

[0805] Robots (such as automated guided vehicles and picking robots)

[0806] software:

[0807] Server programs (Python, Flask API, etc.)

[0808] Databases (MySQL, PostgreSQL, etc.)

[0809] Client applications (mobile apps, robot control software)

[0810] Specific example

[0811] Obtaining a list of tasks

[0812] Users input each task performed at the logistics center into a smartphone application. Examples of tasks include picking, packing, and quality checks. The terminal sends this task list to a server, which stores the list in a database and assigns a unique ID to each task.

[0813] Setting Priorities and Estimated Times

[0814] Users set priority levels (high, medium, low) and estimated time (in hours) for each task within the application. The terminal sends this configuration information to the server, which updates the database based on the received information.

[0815] Work distribution and allocation

[0816] The server sorts tasks based on configured priorities and estimated times, distributing them to each user in the optimal order. Especially in logistics centers, where efficient task distribution is crucial, the server considers the schedule information of each worker and robot, assigning tasks at the appropriate time.

[0817] Monitoring progress

[0818] Users begin their assigned tasks and, upon completion, send a completion status to the server via their terminal. The server reflects this information in its database and notifies the user of their next task, enabling real-time progress monitoring.

[0819] Example of a prompt

[0820] Examples of prompts that can be used when describing this application with a generative AI model include:

[0821] "Please explain the work distribution system in the logistics center."

[0822] "Please explain in detail how to prioritize tasks, set estimated timeframes, and allocate them efficiently."

[0823] "Please explain how the staff and robots at the logistics center monitor operations and update progress in real time."

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

[0825] Step 1: Obtain the task list

[0826] Users input each task at the logistics center (picking, packing, quality checks, etc.) into a smartphone application. This input data includes the task name, details, and related information. The terminal sends this task list to the server. The server stores the received task list in a database and assigns a unique ID to each task. The input data consists of the task name and details, while the output data is a task list with unique IDs assigned to each task.

[0827] Step 2: Setting priorities and estimated time

[0828] Users set priority levels (high, medium, low) and estimated time (in hours) for each task via a smartphone application. The device sends this configuration information to the server. The server updates the task list in the database based on the received information. The input data is the priority level and estimated time, and the output data is the updated task list.

[0829] Step 3: Distribution of tasks

[0830] The server sorts tasks based on configured priorities and estimated times. Especially in logistics centers where efficient task allocation is crucial, the server considers each worker's schedule information to determine the optimal order for the next task allocation. Input data includes priorities and estimated times, while output data is a sorted list of tasks.

[0831] Step 4: Assigning tasks

[0832] The server assigns tasks to each user at the optimal time based on their schedule information. The server compares the schedule information with a sorted list of tasks, assigns tasks to each user at their most suitable time, and sends the assignment information to the terminal. Input data consists of schedule information and a sorted list of tasks, while output data is the assignment schedule for each user.

[0833] Step 5: Confirm and accept the work schedule.

[0834] The terminal displays the received work schedule on the user's smartphone. The user can review the schedule and make corrections as needed. The user's corrections are sent back to the server via the terminal. The server updates the database based on the corrections. The input data is the schedule information corrected by the user, and the output data is the updated schedule information.

[0835] Step 6: Monitoring progress

[0836] The user starts the assigned task and sends a "completed" status to the server via their terminal upon completion. The server receives the completion status and updates the task status in the database. If there is another task to assign, the server notifies the user. The input data is the status of the completed task, and the output data is the updated task status and the next task notification.

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

[0838] System Overview

[0839] This invention combines a system for the efficient distribution and management of tasks with an emotion engine that recognizes user emotions, thereby achieving optimal task execution according to the user's state. The server, terminal, user, and emotion engine work together to improve work efficiency and reduce user stress.

[0840] Program processing

[0841] The program of this system operates with the server, terminal, user, and emotion engine each fulfilling their respective roles, as follows:

[0842] Obtaining and setting up the task list

[0843] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[0844] Terminal: Sends the entered list of tasks to the server.

[0845] Server: Receives the task list and saves it to the database. Each task is assigned a unique ID.

[0846] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[0847] Terminal: Saves configuration information in a format that sends it to the server.

[0848] Server: Adds the received configuration information to the task list and updates the database.

[0849] Work distribution and allocation

[0850] Server: Retrieves a list of tasks and their configuration information from the database, sorts the tasks by priority using an algorithm, and distributes the tasks while also taking into account input from the emotion engine.

[0851] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[0852] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is under high stress, it will assign lower-priority tasks for relaxation or rest.

[0853] Confirmation and acceptance of the work schedule.

[0854] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[0855] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[0856] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[0857] Server: Updates the database again based on the received correction information.

[0858] Monitoring progress

[0859] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0860] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[0861] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[0862] Specific example

[0863] For example, the following task list is entered by the user:

[0864] 1. Report creation (Priority: High, Estimated time: 2 hours)

[0865] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[0866] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[0867] Using an Emotion Engine

[0868] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[0869] 2. Emotion Engine: If the system determines that the user is in a high-stress state, it sends this information to the server.

[0870] 3. Server: Considering the emotion engine data, adjust task priorities and change the next task to be performed to reduce user stress as much as possible. Also, suggest breaks at appropriate times.

[0871] This allows users to receive task assignments that take their emotional state into consideration, enabling a more comfortable work environment. By having the server constantly monitor progress and emotional state, work efficiency can be improved while reducing mental stress.

[0872] The following describes the processing flow.

[0873] Step 1:

[0874] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[0875] Step 2:

[0876] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[0877] Step 3:

[0878] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[0879] Step 4:

[0880] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[0881] Step 5:

[0882] Terminal: Sends information about the configured priority and estimated time to the server.

[0883] Step 6:

[0884] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[0885] Step 7:

[0886] Server: Retrieves a list of tasks and their configuration information from the database, and uses an algorithm to sort the tasks in order of priority.

[0887] Step 8:

[0888] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[0889] Step 9:

[0890] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is in a high-stress state, it assigns lower-priority tasks to encourage relaxation and rest.

[0891] Step 10:

[0892] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[0893] Step 11:

[0894] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[0895] Step 12:

[0896] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[0897] Step 13:

[0898] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[0899] Step 14:

[0900] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[0901] Step 15:

[0902] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[0903] Step 16:

[0904] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[0905] Step 17:

[0906] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[0907] Step 18:

[0908] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[0909] This allows for efficient task distribution, enabling users to proceed with their work systematically. Furthermore, real-time management of progress and emotional states improves work efficiency while reducing mental stress.

[0910] (Example 2)

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

[0912] While conventional business management systems can efficiently distribute and manage tasks, they struggle to adjust tasks while considering the user's emotional state. This led to increased mental burden on users and decreased productivity. There was a need for a system that could dynamically adjust task priorities and allocation based on the user's emotional state, thereby improving efficiency and reducing user stress.

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

[0914] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for analyzing the user's emotional state using an emotion engine that recognizes the user's state, means for assigning tasks at the optimal timing based on the user's emotional state and schedule information, means for monitoring the progress of each task, and means for dynamically adjusting the priority and distribution of tasks according to the emotional state. This enables efficient distribution and management of tasks while allowing for flexible task adjustments that take into account the user's emotional state.

[0915] A "task list" is a list of the names and contents of each task that the user is to perform.

[0916] "Priority" is an indicator that shows the order and importance of tasks to be performed.

[0917] "Estimated time" is an estimate of the time a user believes they will need to complete each task.

[0918] "Distribution" is the process of assigning multiple tasks based on specific criteria.

[0919] "User state" refers to the user's emotional state, health status, activity level, etc.

[0920] An "emotion engine" is a device or program that analyzes a user's facial expressions, voice, and behavioral data to recognize their emotional state.

[0921] "Schedule information" refers to time-related information such as the user's appointments and schedules.

[0922] "Progress status" indicates the extent to which each task has been completed.

[0923] "Dynamic adjustment" refers to the act of instantly changing settings and allocations based on real-time data and status.

[0924] A "server" is a central computing system used for data processing, storage, and communication.

[0925] This invention combines a system for the efficient distribution and management of tasks with an emotion engine that recognizes user emotions, thereby achieving optimal task execution according to the user's state. The server, terminal, user, and emotion engine work together to improve work efficiency and reduce user stress.

[0926] System Overview

[0927] This system uses the following hardware and software:

[0928] Server: A central computing system that handles data processing, storage, and communication. It manages task lists, executes algorithms, and processes data from emotion engines, among other things.

[0929] Terminal: A device used by users to input and confirm information (such as a PC, smartphone, or tablet). It is responsible for sending user input to the server and displaying the information from the server to the user.

[0930] Emotion engine: A device or program for recognizing a user's emotional state. It analyzes the user's facial expressions and voice using a camera and microphone to recognize their emotional state in real time.

[0931] Obtaining and setting up the task list

[0932] User: Enters a list of tasks through the terminal interface. Examples of specific tasks include "report creation," "meeting preparation," and "email reply."

[0933] Terminal: Sends the entered task list to the server. The communication module is used to send the task list as a POST request to the specified API endpoint.

[0934] Server: Stores the received list of tasks in the database and assigns a unique ID to each task.

[0935] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[0936] Terminal: Sends the configured information to the server.

[0937] Server: Adds the received configuration information to the task list and updates the database.

[0938] Work distribution and allocation

[0939] Server: Retrieves a list of tasks and their configuration information from the database. The retrieved list of tasks is then sorted by priority using an algorithm.

[0940] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time.

[0941] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state.

[0942] Confirmation and acceptance of the work schedule.

[0943] Server: Assigns tasks at the optimal time, taking into account the user's schedule information.

[0944] Terminal: Displays received work schedules to the user.

[0945] User: Check the schedule and enter any necessary corrections.

[0946] Terminal: Resends correction information to the server.

[0947] Server: Updates the database again based on the received correction information.

[0948] Monitoring progress

[0949] User: Start a task and mark it as "Completed" on the terminal as it is finished.

[0950] Terminal: Notifies the server of the status of completed tasks.

[0951] Server: Based on the received completion status, the server updates the task status in the database and prepares to assign the next task.

[0952] Using an Emotion Engine

[0953] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[0954] 2. Emotion Engine: When it determines that the user is in a high-stress state, it sends that information to the server.

[0955] 3. Server: Considers the emotion engine's data and adjusts task priorities. For example, it might change the next task to be performed to reduce stress and suggest a break.

[0956] This allows users to receive optimal task assignments tailored to their emotional state, enabling them to work comfortably. Furthermore, the server constantly monitors progress and emotional state, improving work efficiency and reducing mental stress.

[0957] Example of a prompt

[0958] The following are specific examples of prompt statements for generative AI models:

[0959] "Please describe an algorithm that adjusts task priorities based on the user's emotional state."

[0960] "Could you explain the technical mechanisms and applications of an emotion engine that recognizes user emotions in real time?"

[0961] The above describes the details of embodiments for carrying out the present invention.

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

[0963] Step 1:

[0964] User: Enter the task list into the terminal. For example, specific tasks such as "write a report," "prepare for a meeting," and "reply to emails" are entered using the terminal's dedicated application.

[0965] Input: Job description

[0966] Output: A list of tasks is displayed on the terminal.

[0967] Step 2:

[0968] Terminal: Sends the entered task list to the server. The terminal uses a communication module to send the task list as a POST request to the specified API endpoint.

[0969] Input: User-entered list of tasks

[0970] Output: The server receives the task list.

[0971] Step 3:

[0972] Server: Saves the received list of tasks to the database and assigns a unique ID to each task. Executes an INSERT statement into the database.

[0973] Input: Task list sent from the terminal

[0974] Output: List of tasks and unique IDs stored in the database

[0975] Step 4:

[0976] User: Set priority (high, medium, low) and estimated time (in hours) for each task. Enter detailed information for each task through the terminal interface.

[0977] Input: Task priority and estimated time

[0978] Output: The settings information is reflected on the device.

[0979] Step 5:

[0980] Terminal: Sends user-configured information to the server. The configuration information is sent to the server as a POST request using a communication module.

[0981] Input: Priority and estimated time for the configured task

[0982] Output: The server receives the configuration information.

[0983] Step 6:

[0984] Server: Adds the received configuration information to the task list and updates the database. Executes an UPDATE statement against the database.

[0985] Input: Configuration information sent from the device

[0986] Output: Updated task list in the database

[0987] Step 7:

[0988] Server: Retrieves a list of tasks and their configuration information from the database. Executes a SELECT statement to read the necessary task information.

[0989] Input: Task list and configuration information in the database

[0990] Output: Acquired task list and configuration information

[0991] Step 8:

[0992] Server: The retrieved list of tasks is sorted by priority using an algorithm. The algorithm is implemented in Python or similar languages, and sorts the tasks considering priority and estimated time.

[0993] Input: Task list and its settings information

[0994] Output: Task list sorted by priority

[0995] Step 9:

[0996] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time. The emotion engine acquires and processes data from the camera and microphone.

[0997] Input: User's facial expressions, voice, and behavioral data

[0998] Output: Analysis results of the user's emotional state

[0999] Step 10:

[1000] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. Reads emotion data from storage and applies it to the current task list.

[1001] Input: Emotional state data from the emotion engine

[1002] Output: Adjusted task list

[1003] Step 11:

[1004] Server: Combines user schedule information with other data to assign tasks at the optimal time. Calendar information is also retrieved from the database and applied to task assignments.

[1005] Input: User's schedule information and a list of tasks sorted by priority.

[1006] Output: Assigned work schedule

[1007] Step 12:

[1008] Terminal: Displays received work schedules to the user. Presents the schedule visually through a dedicated interface.

[1009] Input: Work schedule sent from the server

[1010] Output: Schedule displayed on the user's terminal

[1011] Step 13:

[1012] User: Check the schedule and enter any necessary corrections. Enter the correction information using the terminal interface.

[1013] Input: Confirmation and modification of work schedule.

[1014] Output: Input of correction information

[1015] Step 14:

[1016] Terminal: Resends correction information to the server. The correction information is sent to the server as a POST request using the communication module.

[1017] Input: Correction information entered by the user

[1018] Output: The server receives the correction information.

[1019] Step 15:

[1020] Server: Based on the received correction information, update the database again. Execute the UPDATE statement to update the data.

[1021] Input: Correction information sent from the device

[1022] Output: Updated database

[1023] Step 16:

[1024] User: Start a task and mark it as "Completed" on the terminal as it is finished. Click the completion button using a dedicated button or checkbox.

[1025] Input: Mark as completed

[1026] Output: Tasks marked as completed

[1027] Step 17:

[1028] Terminal: Notifies the server of the status of completed tasks. Formats the data and sends it to the server via the communication module.

[1029] Input: User-marked task completion status

[1030] Output: Completion status received by the server

[1031] Step 18:

[1032] Server: Updates the database task status based on the received completion status. Executes an UPDATE statement to change the task status to "Completed". Prepares for assigning the next task.

[1033] Input: Completion status sent from the terminal

[1034] Output: Updated database business status

[1035] The above outlines the specific processing steps of a system that efficiently distributes and manages tasks. This enables flexible task adjustments that take into account the emotional state of users.

[1036] (Application Example 2)

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

[1038] In today's work environment, there is a strong demand for improved work efficiency and reduced worker stress. However, conventional systems focus on improving work efficiency while failing to adequately consider the emotional state and mental burden of workers. As a result, while work efficiency may improve, worker stress and fatigue may increase, potentially leading to a decrease in overall efficiency and productivity. In particular, in workplaces such as factories, excessive stress is a problem as it increases the risk of work errors and accidents. Against this backdrop, there is a need for a system that analyzes the emotional state of workers in real time and dynamically adjusts work accordingly.

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

[1040] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for assigning tasks at the optimal timing based on the user's schedule information, means for monitoring the progress of each task, means for analyzing the user's emotional state in real time using a camera and voice input device, and means for dynamically adjusting the priority and distribution of tasks based on the analyzed emotional state. This makes it possible to monitor the user's emotional state in real time and propose optimal task distribution and breaks based on it.

[1041] A "task list" is a compilation of multiple tasks that a user must perform.

[1042] "Priority" is an indicator that shows the importance and urgency of each task.

[1043] "Estimated time" is an estimate of the time required to complete each task.

[1044] "User schedule information" refers to the timetable and schedule information that users use to carry out their daily activities.

[1045] "Progress status" refers to the state of how far along a task is.

[1046] "Cameras and audio input devices" refer to hardware used to capture the user's facial expressions and voice.

[1047] "Emotional state" refers to a mental state that includes the type and intensity of emotions a user expresses.

[1048] "Dynamic adjustment" refers to changing something in real time according to the situation.

[1049] This invention is a system aimed at improving operational efficiency and reducing worker stress in workplaces such as factories. It involves collaboration between a server, a terminal, and a user. An emotion engine analyzes the user's emotional state in real time and dynamically adjusts tasks based on that analysis.

[1050] The overall system consists of the following elements:

[1051] 1. Server: Plays a central role and manages the database.

[1052] 2. Terminal: Operated by the user, it is used to input task lists and report completion status.

[1053] 3. User: A worker who performs tasks while operating a terminal.

[1054] 4. Emotion Engine: Analyzes the user's facial expressions and voice data to recognize their emotional state.

[1055] Detailed system configuration and functions

[1056] Obtaining and setting up the task list

[1057] User: Use the terminal to enter a list of tasks. For example, enter tasks such as "assembly line work," "quality inspection," and "maintenance work."

[1058] Terminal: Sends the entered list of tasks to the server.

[1059] Server: Receives the task list and saves it to the database. Each task is assigned a unique ID.

[1060] User: Set priority and estimated time for each task.

[1061] Terminal: Sends configuration information to the server.

[1062] Server: Adds the received configuration information to the task list and updates the database.

[1063] Work distribution and allocation

[1064] Server: Retrieves a list of tasks and their configuration information from the database, sorts the tasks by priority using an algorithm, and distributes the tasks while also taking into account input from the emotion engine.

[1065] Emotion Engine: Uses cameras and voice input devices to analyze the user's facial expressions, voice, and behavioral data in real time to recognize their emotional state (e.g., stress, fatigue, satisfaction).

[1066] Server: Receives data from the emotion engine and adjusts task priorities and allocations based on the user's emotional state. If the user is in a high-stress state, it assigns lower-priority tasks or breaks.

[1067] Confirmation and acceptance of the work schedule.

[1068] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[1069] Terminal: Displays received work schedules to the user, who may review and modify the schedule.

[1070] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal sends the correction information to the server.

[1071] Server: Updates the database based on the received correction information.

[1072] Monitoring progress

[1073] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1074] Terminal: Notifies the server that the user has completed their task.

[1075] Server: Based on the received completion status, update the database task status and prepare to assign the next task.

[1076] Specific example

[1077] For example, if a user is performing "assembly line work" (priority: high, estimated time: 120 minutes) in a factory, and the emotion engine detects a high level of stress from the user's facial expressions, it will automatically suggest a "short break." This will result in a notification on the device saying, "Let's take a short break," which can reduce the user's stress.

[1078] Examples of prompts to input into a generative AI model:

[1079] "Please generate code that analyzes a face in real time using a camera and suggests taking a break if a stressed state is detected."

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

[1081] Step 1:

[1082] The user inputs a list of tasks via a terminal. The input includes task descriptions such as "assembly line work," "quality inspection," and "maintenance work." The terminal sends this task list to the server. The server receives the task list, assigns a unique ID to each task, and stores it in a database. At this stage, data processing involves mapping the task description to its ID.

[1083] Step 2:

[1084] Users set a priority (high, medium, low) and estimated time (in minutes or hours) for each task. This configuration information is sent from the terminal to the server. The server adds the received configuration information to the task list and updates the database. At this stage, a data calculation is performed to merge the priority and estimated time information into the task list.

[1085] Step 3:

[1086] The server retrieves a list of tasks and their configuration information from the database and uses an algorithm to sort the tasks by priority. Emotional data from the emotion engine is also considered during this process. Tasks are dynamically distributed based on the emotional state data. This emotional data processing includes the user's real-time stress level and fatigue level.

[1087] Step 4:

[1088] The emotion engine uses cameras and voice input devices to analyze the user's facial expressions and voice in real time and recognize their emotional state (stress, fatigue, satisfaction). Specific operations include preprocessing of image and audio data, feature extraction, and emotion recognition through classification models. The user's facial images and voice are provided as input, and emotional states such as "high stress" or "fatigue" are obtained as output.

[1089] Step 5:

[1090] The server receives data from the emotion engine and dynamically adjusts the priority and allocation of tasks based on the user's emotional state. For example, if a user is in a high-stress state, it may assign lower-priority tasks or suggest short breaks. Here, the emotional data is input into the task allocation algorithm, and the output is an adjusted list of tasks.

[1091] Step 6:

[1092] The server assigns tasks at the optimal time, taking into account the user's schedule information. The terminal displays the received task schedule to the user. The user checks the schedule, makes any necessary corrections, and enters the corrections into the terminal. The terminal sends the correction information to the server, and the server updates the database based on the received correction information.

[1093] Step 7:

[1094] The user starts a task and marks it as "completed" on their terminal upon completion. The terminal notifies the server of this completion status. The server updates the task status in the database based on the received completion status and prepares to assign the next task. At this point, as part of the data processing, the completion status is marked in the task list, and the next task is assigned by the server.

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

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

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

[1098] [Third Embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

[1111] System Overview

[1112] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system includes functions for obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[1113] Program processing

[1114] The program of this system operates with the server, terminal, and user each fulfilling their respective roles as follows:

[1115] Obtaining a list of tasks

[1116] User: Enters a list of tasks (e.g., report creation, meeting preparation, email reply) into the terminal.

[1117] Terminal: Sends the entered list of tasks to the server.

[1118] Server: Receives the task list and saves it to the database. Assigns a unique ID to each task for management.

[1119] Priority and time settings

[1120] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[1121] Terminal: Saves configuration information in a format that sends it to the server.

[1122] Server: Adds the received configuration information to the task list and updates the database.

[1123] Distribution of tasks

[1124] Server: Retrieves a list of tasks and their configuration information from the database, uses an algorithm to sort the tasks by priority, and prepares them for distribution to each user in the next step.

[1125] Sorting by priority: Tasks with particularly high priority are placed first.

[1126] Distribute tasks efficiently, taking estimated time into consideration.

[1127] Task assignment

[1128] Server: Retrieves user schedule information and assigns each task at the optimal time.

[1129] Server: Sends the assigned work schedule to the terminal.

[1130] Confirmation and acceptance of the work schedule.

[1131] Terminal: Displays received work schedules to the user.

[1132] User: Check the schedule, make any necessary corrections, and resend it to the server.

[1133] Server: Receives the changes and updates the database again.

[1134] Monitoring progress

[1135] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1136] Terminal: Sends completion status to the server.

[1137] Server: Updates the task status in the database and notifies the user if there are tasks to assign next.

[1138] Specific example

[1139] For example, the following task list is entered by the user:

[1140] 1. Report creation (Priority: High, Estimated time: 2 hours)

[1141] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1142] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[1143] Obtaining and setting up the task list

[1144] 1. User: Enter the task list into the terminal (e.g., write a report, prepare for a meeting, reply to emails).

[1145] 2. Terminal: Sends the task list to the server.

[1146] 3. Server: Stores the task list in the database and assigns a unique ID to each task.

[1147] 4. User: Enter priority and estimated time for each task.

[1148] 5. Terminal: Sends configuration information to the server.

[1149] Work distribution and allocation

[1150] 1. Server: Prioritize tasks based on their importance (e.g., report creation → meeting preparation → email reply).

[1151] 2. Server: Assigns the rearranged tasks to each user's schedule at the most opportune time.

[1152] 3. Server: Sends schedule information to the terminal.

[1153] Monitoring of work schedules and progress

[1154] 1. Terminal: Displays the assigned schedule to the user.

[1155] 2. User: Starts tasks one after another and marks them as "completed" on the terminal upon completion.

[1156] 3. Terminal: Sends completion status to the server.

[1157] 4. Server: Updates the database status and notifies users of the next task.

[1158] This allows for efficient task distribution, enabling users to effectively complete their tasks. Furthermore, the server constantly monitors progress and updates the database in real time, simplifying overall project management.

[1159] The following describes the processing flow.

[1160] Step 1:

[1161] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[1162] Step 2:

[1163] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[1164] Step 3:

[1165] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[1166] Step 4:

[1167] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[1168] Step 5:

[1169] Terminal: Sends information about the configured priority and estimated time to the server.

[1170] Step 6:

[1171] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[1172] Step 7:

[1173] Server: Retrieves a list of tasks and their configuration information from the database. After retrieval, it uses an algorithm to sort the tasks in order of priority.

[1174] Step 8:

[1175] Server: Executes a distribution algorithm based on the sorted tasks and distributes them to each user. At this time, it distributes tasks efficiently, taking into account the estimated time for each task.

[1176] Step 9:

[1177] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[1178] Step 10:

[1179] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[1180] Step 11:

[1181] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[1182] Step 12:

[1183] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[1184] Step 13:

[1185] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[1186] Step 14:

[1187] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1188] Step 15:

[1189] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[1190] Step 16:

[1191] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[1192] Step 17:

[1193] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[1194] This series of processing steps ensures that tasks are distributed efficiently, allowing users to proceed with their work systematically. Furthermore, real-time progress management prevents delays and omissions in tasks.

[1195] (Example 1)

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

[1197] Traditional business management systems often require manual prioritization and time estimation for tasks, leaving room for improvement in the efficiency of task allocation and schedule management. In particular, the lack of a function to monitor task progress in real time and update the database based on completion status makes overall task management cumbersome. As a result, individual users may not be able to perform tasks at the optimal time, potentially leading to delays in project progress.

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

[1199] In this invention, the server includes means for acquiring business information, means for setting priorities and estimated times for the acquired business information, means for distributing business based on the set priorities and estimated times, means for assigning business at the optimal timing based on the user's timetable information, means for monitoring the progress of each business, and means for receiving business completion status and updating the database. This enables efficient distribution and management of business, allowing users to perform tasks at the optimal time. Furthermore, the server's real-time monitoring of progress and database updates simplify overall business management.

[1200] "Business information" refers to data that includes detailed information such as the content, purpose, deadline, and person in charge of the work.

[1201] "Priority" is an indicator that shows the importance or urgency of a task, and is usually set on a three-tiered scale: high, medium, and low.

[1202] "Estimated time" refers to a unit of time estimated to be required to complete a specific task.

[1203] "Distributing" refers to the process by which a server assigns tasks to the appropriate personnel and time slots.

[1204] "Timetable information" refers to information that shows the user's schedule data, such as their appointments and free time.

[1205] "Monitoring progress" refers to the act of checking the progress of tasks in real time and updating the database as needed.

[1206] "Completion status" refers to information indicating that a specific task has been completed, and this information is recorded in the database by the server.

[1207] "Modifying a database" refers to the process of updating, deleting, or adding to the contents of a database based on the information received.

[1208] An "identification number" is a unique ID assigned to uniquely identify each business or piece of data.

[1209] System Overview

[1210] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system has the following functions:

[1211] 1. Acquisition of business information

[1212] 2. Setting priorities and estimated times

[1213] 3. Distribution of tasks

[1214] 4. Assignment of tasks

[1215] 5. Monitoring progress

[1216] The server works in conjunction with a database management system (e.g., MySQL) to store and manage business information and configuration data. The terminal accepts user input and communicates data with the server. Users input business information and report progress via the terminal.

[1217] System details

[1218] Acquisition of business information

[1219] Users input work information into a terminal. This information includes the content and purpose of the work. The terminal packages this information into packets and sends an HTTP request to the server. The server stores the received work information in a database and assigns an identification number to each work.

[1220] Setting Priorities and Estimated Times

[1221] Users set priority levels (e.g., high, medium, low) and estimated time (in hours) for each task on their terminal. The terminal bundles the configuration information into a packet and sends it back to the server. The server receives the configuration information, adds it to the task information, and updates the database.

[1222] Distribution of tasks

[1223] The server retrieves business and configuration information from the database and sorts it by priority using a sorting algorithm within the program. Specifically, Python or Java programs can be used.

[1224] Task assignment

[1225] The server retrieves the user's timetable information and assigns tasks at the optimal time based on that information. The server can use the Google Calendar API or the API of a company's scheduling software to retrieve timetable information. The schedule information for the assigned tasks is sent from the server to the terminal.

[1226] Monitoring of progress

[1227] Users mark each completed task as "completed" on their terminal. The terminal sends the completion status to the server. The server updates its database based on the received completion status and notifies the user if there are any further tasks.

[1228] Specific example

[1229] For example, the following list of tasks is entered by the user.

[1230] Report preparation (Priority: High, Estimated time: 2 hours)

[1231] Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1232] Email reply (Priority: Low, Estimated time: 30 minutes)

[1233] Users enter this information into their terminals and send it from the terminals to the server. The server stores this information in a database and assigns an identification number to it. The user then sets the priority and estimated time and sends it to the server again. The server distributes tasks based on this data, assigns them appropriately according to the user's schedule, and monitors the progress.

[1234] Examples of prompt statements

[1235] For example, here is an example of a prompt message to check the system via a generative AI model:

[1236] "Please use this system to create tomorrow's work schedule. The task list should include the following, along with priority and estimated time."

[1237] 1. Report creation (Priority: High, Estimated time: 2 hours)

[1238] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1239] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[1240] As described above, this system enables efficient distribution and management of tasks, allowing users to perform their tasks at the optimal time. Furthermore, the server monitors progress in real time and updates the database, simplifying overall task management.

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

[1242] Step 1:

[1243] The user enters work information into the terminal.

[1244] Input: Detailed information such as the nature and purpose of the work, and the person in charge.

[1245] Specific actions: The user opens the application on their device, enters work-related information such as "Create Report," "Prepare for Meeting," or "Reply to Email" into a form, and clicks the submit button.

[1246] Output: The entered business information is temporarily stored in the terminal's memory.

[1247] Step 2:

[1248] The terminal sends business information to the server.

[1249] Input: Business information entered by the user.

[1250] Specific operation: The terminal collects the entered business information into a packet and generates an HTTP request to the server. Then, it sends the request to the server.

[1251] Output: Business information is sent to the server.

[1252] Step 3:

[1253] The server receives business information and saves it to the database.

[1254] Input: Business information sent from the terminal.

[1255] Specific operation: The server receives an HTTP request and parses the business information. This information is stored in a database management system (e.g., MySQL), and an identification number is assigned to each business.

[1256] Output: Business information stored in the database and the identification number assigned to it.

[1257] Step 4:

[1258] Users set priorities and estimated timeframes for each task.

[1259] Input: Business information stored in the database.

[1260] Specific operation: The user sets the priority (high, medium, low) and estimated time (in hours) for each task using dropdown menus or input fields on their device. Once the settings are complete, they click the submit button.

[1261] Output: The set priority and estimated time are temporarily stored in the device's memory.

[1262] Step 5:

[1263] The device sends configuration information to the server.

[1264] Input: User-defined priority and estimated time.

[1265] Specific operation: The terminal bundles the configuration information into a packet, generates an HTTP request to the server again, and sends it.

[1266] Output: Configuration information is sent to the server.

[1267] Step 6:

[1268] The server adds the received configuration information to the business information and updates the database.

[1269] Input: Configuration information sent from the device.

[1270] Specific operation: The server analyzes the received configuration information and adds it to existing business information. The corresponding record in the database is then updated.

[1271] Output: Task information, including priority and estimated time, is saved to the database.

[1272] Step 7:

[1273] The server retrieves business information and configuration information from the database and sorts them using an algorithm.

[1274] Input: Business information and configuration information stored in the database.

[1275] Specific operation: The server executes SQL queries to retrieve business information and configuration information. Then, a sorting algorithm is executed within a Python or Java program to sort the business items based on priority.

[1276] Output: A list of tasks sorted by priority.

[1277] Step 8:

[1278] The server retrieves the user's timetable information and assigns tasks at the optimal time.

[1279] Input: A sorted list of tasks and user timetable information.

[1280] Specific operation: The server retrieves timetable information from the Google Calendar API or the company's scheduling software, and then assigns tasks at the appropriate times based on that information.

[1281] Output: A list of tasks assigned to each user at the optimal time.

[1282] Step 9:

[1283] The server sends the assigned work schedule to the terminal.

[1284] Input: A list of tasks assigned to the user at the optimal time.

[1285] Specific operation: The server bundles the work schedule into packets and sends an HTTP response to the user's terminal.

[1286] Output: The work schedule is sent to the terminal.

[1287] Step 10:

[1288] The terminal displays the received work schedule to the user.

[1289] Input: Work schedule sent from the server.

[1290] Specific operation: The application on the terminal analyzes the received schedule data and displays it in the GUI.

[1291] Output: The work schedule displayed to the user.

[1292] Step 11:

[1293] The user checks the schedule, makes corrections if necessary, and resends it to the server.

[1294] Input: Work schedule displayed on the terminal.

[1295] Specific operation: The user makes a modification to the schedule and clicks the resend button to send the changes to the server.

[1296] Output: The corrected schedule information is sent from the terminal to the server.

[1297] Step 12:

[1298] The server receives the changes and updates the database again.

[1299] Input: Modified schedule information submitted by the user.

[1300] Specific operation: The server analyzes the changes and updates the corresponding records in the database.

[1301] Output: The corrected schedule information is saved to the database.

[1302] Step 13:

[1303] The user starts a task and marks it as "completed" on their device each time they finish.

[1304] Input: Progress status of tasks performed by the user.

[1305] Specific action: The user clicks the "Complete" button in the application on their device when they have finished a task.

[1306] Output: The progress of the task is recorded on the terminal.

[1307] Step 14:

[1308] The terminal sends a completion status to the server.

[1309] Input: Progress status of tasks marked as completed by the user.

[1310] Specific operation: The terminal bundles the completion status into a packet, generates an HTTP request to the server, and sends it.

[1311] Output: Completion status is sent to the server.

[1312] Step 15:

[1313] The server updates the database's operational status and notifies the user if there are any new tasks.

[1314] Input: Completion status sent from the terminal.

[1315] Specific operation: The server analyzes the completion status and updates the status of the corresponding record in the database. If there is a task to assign next, it generates and sends a notification message to the user.

[1316] Output: The database's business status is updated, and the next business notification is sent to the user.

[1317] (Application Example 1)

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

[1319] The distribution and progress management of tasks in logistics centers typically rely on manual labor, making them inefficient and prone to errors. Furthermore, it is difficult to appropriately set task priorities and estimated times, and to monitor progress in real time. As a result, delays and disruptions occur, leading to a decline in overall operational efficiency.

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

[1321] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, and means for efficiently monitoring the distribution and progress of each task in the logistics center. This enables efficient and accurate distribution and progress management of tasks in the logistics center, thereby improving overall operational efficiency.

[1322] A "task list" refers to a list that enumerates specific tasks, indicating the work that the user should perform.

[1323] "Priority" is an indicator that shows the importance or urgency of a task, and is expressed in grades such as "high," "medium," and "low."

[1324] "Estimated time" refers to the predicted time required to complete a specific task, and is expressed in hours.

[1325] "Distribution" refers to the process of organizing tasks in the appropriate order and assigning them to each user based on set priorities and estimated timeframes.

[1326] "Schedule information" refers to information that indicates the time slots for each user's individual appointments and tasks, and is used for assigning tasks.

[1327] "Progress status" refers to status information that indicates the stage of a task, and requires real-time monitoring.

[1328] A "logistics center" refers to a facility where operations such as storage, sorting, processing, and shipping of goods are carried out, and it is a place where large-scale inventory management and logistics operations take place.

[1329] "Efficient" refers to a state where there is no waste, and the resources and time required to achieve a goal are minimized.

[1330] "Distribution and progress monitoring" refers to a series of operations that involve appropriately assigning tasks and monitoring their progress in real time.

[1331] "Completion status" refers to information indicating that a specific task has been completed, and this information is reflected in other systems when updated in the database.

[1332] A "database" refers to an information management system that organizes and stores large amounts of data, making it possible to quickly search and use it as needed.

[1333] This invention is a system for efficiently distributing and managing the progress of tasks in a logistics center. The system operates collaboratively among a server, terminals, and users, providing a series of functions including obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[1334] System Configuration

[1335] The system consists of the following main components:

[1336] Server: Stores data, distributes tasks, and monitors progress.

[1337] Terminals (smartphones, robots): These devices handle data input from the user and display the received information.

[1338] User: Enter tasks into the task list, set priorities and estimated times, and check and update progress.

[1339] Hardware and software to use

[1340] Hardware:

[1341] Smartphone (a typical smartphone device)

[1342] Robots (such as automated guided vehicles and picking robots)

[1343] software:

[1344] Server programs (Python, Flask API, etc.)

[1345] Databases (MySQL, PostgreSQL, etc.)

[1346] Client applications (mobile apps, robot control software)

[1347] Specific example

[1348] Obtaining a list of tasks

[1349] Users input each task performed at the logistics center into a smartphone application. Examples of tasks include picking, packing, and quality checks. The terminal sends this task list to a server, which stores the list in a database and assigns a unique ID to each task.

[1350] Setting Priorities and Estimated Times

[1351] Users set priority levels (high, medium, low) and estimated time (in hours) for each task within the application. The terminal sends this configuration information to the server, which updates the database based on the received information.

[1352] Work distribution and allocation

[1353] The server sorts tasks based on configured priorities and estimated times, distributing them to each user in the optimal order. Especially in logistics centers, where efficient task distribution is crucial, the server considers the schedule information of each worker and robot, assigning tasks at the appropriate time.

[1354] Monitoring progress

[1355] Users begin their assigned tasks and, upon completion, send a completion status to the server via their terminal. The server reflects this information in its database and notifies the user of their next task, enabling real-time progress monitoring.

[1356] Example of a prompt

[1357] Examples of prompts that can be used when describing this application with a generative AI model include:

[1358] "Please explain the work distribution system in the logistics center."

[1359] "Please explain in detail how to prioritize tasks, set estimated timeframes, and allocate them efficiently."

[1360] "Please explain how the staff and robots at the logistics center monitor operations and update progress in real time."

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

[1362] Step 1: Obtain the task list

[1363] Users input each task at the logistics center (picking, packing, quality checks, etc.) into a smartphone application. This input data includes the task name, details, and related information. The terminal sends this task list to the server. The server stores the received task list in a database and assigns a unique ID to each task. The input data consists of the task name and details, while the output data is a task list with unique IDs assigned to each task.

[1364] Step 2: Setting priorities and estimated time

[1365] Users set priority levels (high, medium, low) and estimated time (in hours) for each task via a smartphone application. The device sends this configuration information to the server. The server updates the task list in the database based on the received information. The input data is the priority level and estimated time, and the output data is the updated task list.

[1366] Step 3: Distribution of tasks

[1367] The server sorts tasks based on configured priorities and estimated times. Especially in logistics centers where efficient task allocation is crucial, the server considers each worker's schedule information to determine the optimal order for the next task allocation. Input data includes priorities and estimated times, while output data is a sorted list of tasks.

[1368] Step 4: Assigning tasks

[1369] The server assigns tasks to each user at the optimal time based on their schedule information. The server compares the schedule information with a sorted list of tasks, assigns tasks to each user at their most suitable time, and sends the assignment information to the terminal. Input data consists of schedule information and a sorted list of tasks, while output data is the assignment schedule for each user.

[1370] Step 5: Confirm and accept the work schedule.

[1371] The terminal displays the received work schedule on the user's smartphone. The user can review the schedule and make corrections as needed. The user's corrections are sent back to the server via the terminal. The server updates the database based on the corrections. The input data is the schedule information corrected by the user, and the output data is the updated schedule information.

[1372] Step 6: Monitoring progress

[1373] The user starts the assigned task and sends a "completed" status to the server via their terminal upon completion. The server receives the completion status and updates the task status in the database. If there is another task to assign, the server notifies the user. The input data is the status of the completed task, and the output data is the updated task status and the next task notification.

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

[1375] System Overview

[1376] This invention combines a system for the efficient distribution and management of tasks with an emotion engine that recognizes user emotions, thereby achieving optimal task execution according to the user's state. The server, terminal, user, and emotion engine work together to improve work efficiency and reduce user stress.

[1377] Program processing

[1378] The program of this system operates with the server, terminal, user, and emotion engine each fulfilling their respective roles, as follows:

[1379] Obtaining and setting up the task list

[1380] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[1381] Terminal: Sends the entered list of tasks to the server.

[1382] Server: Receives the task list and saves it to the database. Each task is assigned a unique ID.

[1383] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[1384] Terminal: Saves configuration information in a format that sends it to the server.

[1385] Server: Adds the received configuration information to the task list and updates the database.

[1386] Work distribution and allocation

[1387] Server: Retrieves a list of tasks and their configuration information from the database, sorts the tasks by priority using an algorithm, and distributes the tasks while also taking into account input from the emotion engine.

[1388] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[1389] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is under high stress, it will assign lower-priority tasks for relaxation or rest.

[1390] Confirmation and acceptance of the work schedule.

[1391] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[1392] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[1393] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[1394] Server: Updates the database again based on the received correction information.

[1395] Monitoring progress

[1396] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1397] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[1398] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[1399] Specific example

[1400] For example, the following task list is entered by the user:

[1401] 1. Report creation (Priority: High, Estimated time: 2 hours)

[1402] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1403] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[1404] Using an Emotion Engine

[1405] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[1406] 2. Emotion Engine: If the system determines that the user is in a high-stress state, it sends this information to the server.

[1407] 3. Server: Considering the emotion engine data, adjust task priorities and change the next task to be performed to reduce user stress as much as possible. Also, suggest breaks at appropriate times.

[1408] This allows users to receive task assignments that take their emotional state into consideration, enabling a more comfortable work environment. By having the server constantly monitor progress and emotional state, work efficiency can be improved while reducing mental stress.

[1409] The following describes the processing flow.

[1410] Step 1:

[1411] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[1412] Step 2:

[1413] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[1414] Step 3:

[1415] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[1416] Step 4:

[1417] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[1418] Step 5:

[1419] Terminal: Sends information about the configured priority and estimated time to the server.

[1420] Step 6:

[1421] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[1422] Step 7:

[1423] Server: Retrieves a list of tasks and their configuration information from the database, and uses an algorithm to sort the tasks in order of priority.

[1424] Step 8:

[1425] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[1426] Step 9:

[1427] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is in a high-stress state, it assigns lower-priority tasks to encourage relaxation and rest.

[1428] Step 10:

[1429] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[1430] Step 11:

[1431] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[1432] Step 12:

[1433] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[1434] Step 13:

[1435] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[1436] Step 14:

[1437] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[1438] Step 15:

[1439] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1440] Step 16:

[1441] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[1442] Step 17:

[1443] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[1444] Step 18:

[1445] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[1446] This allows for efficient task distribution, enabling users to proceed with their work systematically. Furthermore, real-time management of progress and emotional states improves work efficiency while reducing mental stress.

[1447] (Example 2)

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

[1449] While conventional business management systems can efficiently distribute and manage tasks, they struggle to adjust tasks while considering the user's emotional state. This led to increased mental burden on users and decreased productivity. There was a need for a system that could dynamically adjust task priorities and allocation based on the user's emotional state, thereby improving efficiency and reducing user stress.

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

[1451] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for analyzing the user's emotional state using an emotion engine that recognizes the user's state, means for assigning tasks at the optimal timing based on the user's emotional state and schedule information, means for monitoring the progress of each task, and means for dynamically adjusting the priority and distribution of tasks according to the emotional state. This enables efficient distribution and management of tasks while allowing for flexible task adjustments that take into account the user's emotional state.

[1452] A "task list" is a list of the names and contents of each task that the user is to perform.

[1453] "Priority" is an indicator that shows the order and importance of tasks to be performed.

[1454] "Estimated time" is an estimate of the time a user believes they will need to complete each task.

[1455] "Distribution" is the process of assigning multiple tasks based on specific criteria.

[1456] "User state" refers to the user's emotional state, health status, activity level, etc.

[1457] An "emotion engine" is a device or program that analyzes a user's facial expressions, voice, and behavioral data to recognize their emotional state.

[1458] "Schedule information" refers to time-related information such as the user's appointments and schedules.

[1459] "Progress status" indicates the extent to which each task has been completed.

[1460] "Dynamic adjustment" refers to the act of instantly changing settings and allocations based on real-time data and status.

[1461] A "server" is a central computing system used for data processing, storage, and communication.

[1462] This invention combines a system for the efficient distribution and management of tasks with an emotion engine that recognizes user emotions, thereby achieving optimal task execution according to the user's state. The server, terminal, user, and emotion engine work together to improve work efficiency and reduce user stress.

[1463] System Overview

[1464] This system uses the following hardware and software:

[1465] Server: A central computing system that handles data processing, storage, and communication. It manages task lists, executes algorithms, and processes data from emotion engines, among other things.

[1466] Terminal: A device used by users to input and confirm information (such as a PC, smartphone, or tablet). It is responsible for sending user input to the server and displaying the information from the server to the user.

[1467] Emotion engine: A device or program for recognizing a user's emotional state. It analyzes the user's facial expressions and voice using a camera and microphone to recognize their emotional state in real time.

[1468] Obtaining and setting up the task list

[1469] User: Enters a list of tasks through the terminal interface. Examples of specific tasks include "report creation," "meeting preparation," and "email reply."

[1470] Terminal: Sends the entered task list to the server. The communication module is used to send the task list as a POST request to the specified API endpoint.

[1471] Server: Stores the received list of tasks in the database and assigns a unique ID to each task.

[1472] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[1473] Terminal: Sends the configured information to the server.

[1474] Server: Adds the received configuration information to the task list and updates the database.

[1475] Work distribution and allocation

[1476] Server: Retrieves a list of tasks and their configuration information from the database. The retrieved list of tasks is then sorted by priority using an algorithm.

[1477] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time.

[1478] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state.

[1479] Confirmation and acceptance of the work schedule.

[1480] Server: Assigns tasks at the optimal time, taking into account the user's schedule information.

[1481] Terminal: Displays received work schedules to the user.

[1482] User: Check the schedule and enter any necessary corrections.

[1483] Terminal: Resends correction information to the server.

[1484] Server: Updates the database again based on the received correction information.

[1485] Monitoring progress

[1486] User: Start a task and mark it as "Completed" on the terminal as it is finished.

[1487] Terminal: Notifies the server of the status of completed tasks.

[1488] Server: Based on the received completion status, the server updates the task status in the database and prepares to assign the next task.

[1489] Using an Emotion Engine

[1490] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[1491] 2. Emotion Engine: When it determines that the user is in a high-stress state, it sends that information to the server.

[1492] 3. Server: Considers the emotion engine's data and adjusts task priorities. For example, it might change the next task to be performed to reduce stress and suggest a break.

[1493] This allows users to receive optimal task assignments tailored to their emotional state, enabling them to work comfortably. Furthermore, the server constantly monitors progress and emotional state, improving work efficiency and reducing mental stress.

[1494] Example of a prompt

[1495] The following are specific examples of prompt statements for generative AI models:

[1496] "Please describe an algorithm that adjusts task priorities based on the user's emotional state."

[1497] "Could you explain the technical mechanisms and applications of an emotion engine that recognizes user emotions in real time?"

[1498] The above describes the details of embodiments for carrying out the present invention.

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

[1500] Step 1:

[1501] User: Enter the task list into the terminal. For example, specific tasks such as "write a report," "prepare for a meeting," and "reply to emails" are entered using the terminal's dedicated application.

[1502] Input: Job description

[1503] Output: A list of tasks is displayed on the terminal.

[1504] Step 2:

[1505] Terminal: Sends the entered task list to the server. The terminal uses a communication module to send the task list as a POST request to the specified API endpoint.

[1506] Input: User-entered list of tasks

[1507] Output: The server receives the task list.

[1508] Step 3:

[1509] Server: Saves the received list of tasks to the database and assigns a unique ID to each task. Executes an INSERT statement into the database.

[1510] Input: Task list sent from the terminal

[1511] Output: List of tasks and unique IDs stored in the database

[1512] Step 4:

[1513] User: Set priority (high, medium, low) and estimated time (in hours) for each task. Enter detailed information for each task through the terminal interface.

[1514] Input: Task priority and estimated time

[1515] Output: The settings information is reflected on the device.

[1516] Step 5:

[1517] Terminal: Sends user-configured information to the server. The configuration information is sent to the server as a POST request using a communication module.

[1518] Input: Priority and estimated time for the configured task

[1519] Output: The server receives the configuration information.

[1520] Step 6:

[1521] Server: Adds the received configuration information to the task list and updates the database. Executes an UPDATE statement against the database.

[1522] Input: Configuration information sent from the device

[1523] Output: Updated task list in the database

[1524] Step 7:

[1525] Server: Retrieves a list of tasks and their configuration information from the database. Executes a SELECT statement to read the necessary task information.

[1526] Input: Task list and configuration information in the database

[1527] Output: Acquired task list and configuration information

[1528] Step 8:

[1529] Server: The retrieved list of tasks is sorted by priority using an algorithm. The algorithm is implemented in Python or similar languages, and sorts the tasks considering priority and estimated time.

[1530] Input: Task list and its settings information

[1531] Output: Task list sorted by priority

[1532] Step 9:

[1533] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time. The emotion engine acquires and processes data from the camera and microphone.

[1534] Input: User's facial expressions, voice, and behavioral data

[1535] Output: Analysis results of the user's emotional state

[1536] Step 10:

[1537] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. Reads emotion data from storage and applies it to the current task list.

[1538] Input: Emotional state data from the emotion engine

[1539] Output: Adjusted task list

[1540] Step 11:

[1541] Server: Combines user schedule information with other data to assign tasks at the optimal time. Calendar information is also retrieved from the database and applied to task assignments.

[1542] Input: User's schedule information and a list of tasks sorted by priority.

[1543] Output: Assigned work schedule

[1544] Step 12:

[1545] Terminal: Displays received work schedules to the user. Presents the schedule visually through a dedicated interface.

[1546] Input: Work schedule sent from the server

[1547] Output: Schedule displayed on the user's terminal

[1548] Step 13:

[1549] User: Check the schedule and enter any necessary corrections. Enter the correction information using the terminal interface.

[1550] Input: Confirmation and modification of work schedule.

[1551] Output: Input of correction information

[1552] Step 14:

[1553] Terminal: Resends correction information to the server. The correction information is sent to the server as a POST request using the communication module.

[1554] Input: Correction information entered by the user

[1555] Output: The server receives the correction information.

[1556] Step 15:

[1557] Server: Based on the received correction information, update the database again. Execute the UPDATE statement to update the data.

[1558] Input: Correction information sent from the device

[1559] Output: Updated database

[1560] Step 16:

[1561] User: Start a task and mark it as "Completed" on the terminal as it is finished. Click the completion button using a dedicated button or checkbox.

[1562] Input: Mark as completed

[1563] Output: Tasks marked as completed

[1564] Step 17:

[1565] Terminal: Notifies the server of the status of completed tasks. Formats the data and sends it to the server via the communication module.

[1566] Input: User-marked task completion status

[1567] Output: Completion status received by the server

[1568] Step 18:

[1569] Server: Updates the database task status based on the received completion status. Executes an UPDATE statement to change the task status to "Completed". Prepares for assigning the next task.

[1570] Input: Completion status sent from the terminal

[1571] Output: Updated database business status

[1572] The above outlines the specific processing steps of a system that efficiently distributes and manages tasks. This enables flexible task adjustments that take into account the emotional state of users.

[1573] (Application Example 2)

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

[1575] In today's work environment, there is a strong demand for improved work efficiency and reduced worker stress. However, conventional systems focus on improving work efficiency while failing to adequately consider the emotional state and mental burden of workers. As a result, while work efficiency may improve, worker stress and fatigue may increase, potentially leading to a decrease in overall efficiency and productivity. In particular, in workplaces such as factories, excessive stress is a problem as it increases the risk of work errors and accidents. Against this backdrop, there is a need for a system that analyzes the emotional state of workers in real time and dynamically adjusts work accordingly.

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

[1577] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for assigning tasks at the optimal timing based on the user's schedule information, means for monitoring the progress of each task, means for analyzing the user's emotional state in real time using a camera and voice input device, and means for dynamically adjusting the priority and distribution of tasks based on the analyzed emotional state. This makes it possible to monitor the user's emotional state in real time and propose optimal task distribution and breaks based on it.

[1578] A "task list" is a compilation of multiple tasks that a user must perform.

[1579] "Priority" is an indicator that shows the importance and urgency of each task.

[1580] "Estimated time" is an estimate of the time required to complete each task.

[1581] "User schedule information" refers to the timetable and schedule information that users use to carry out their daily activities.

[1582] "Progress status" refers to the state of how far along a task is.

[1583] "Cameras and audio input devices" refer to hardware used to capture the user's facial expressions and voice.

[1584] "Emotional state" refers to a mental state that includes the type and intensity of emotions a user expresses.

[1585] "Dynamic adjustment" refers to changing something in real time according to the situation.

[1586] This invention is a system aimed at improving operational efficiency and reducing worker stress in workplaces such as factories. It involves collaboration between a server, a terminal, and a user. An emotion engine analyzes the user's emotional state in real time and dynamically adjusts tasks based on that analysis.

[1587] The overall system consists of the following elements:

[1588] 1. Server: Plays a central role and manages the database.

[1589] 2. Terminal: Operated by the user, it is used to input task lists and report completion status.

[1590] 3. User: A worker who performs tasks while operating a terminal.

[1591] 4. Emotion Engine: Analyzes the user's facial expressions and voice data to recognize their emotional state.

[1592] Detailed system configuration and functions

[1593] Obtaining and setting up the task list

[1594] User: Use the terminal to enter a list of tasks. For example, enter tasks such as "assembly line work," "quality inspection," and "maintenance work."

[1595] Terminal: Sends the entered list of tasks to the server.

[1596] Server: Receives the task list and saves it to the database. Each task is assigned a unique ID.

[1597] User: Set priority and estimated time for each task.

[1598] Terminal: Sends configuration information to the server.

[1599] Server: Adds the received configuration information to the task list and updates the database.

[1600] Work distribution and allocation

[1601] Server: Retrieves a list of tasks and their configuration information from the database, sorts the tasks by priority using an algorithm, and distributes the tasks while also taking into account input from the emotion engine.

[1602] Emotion Engine: Uses cameras and voice input devices to analyze the user's facial expressions, voice, and behavioral data in real time to recognize their emotional state (e.g., stress, fatigue, satisfaction).

[1603] Server: Receives data from the emotion engine and adjusts task priorities and allocations based on the user's emotional state. If the user is in a high-stress state, it assigns lower-priority tasks or breaks.

[1604] Confirmation and acceptance of the work schedule.

[1605] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[1606] Terminal: Displays received work schedules to the user, who may review and modify the schedule.

[1607] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal sends the correction information to the server.

[1608] Server: Updates the database based on the received correction information.

[1609] Monitoring progress

[1610] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1611] Terminal: Notifies the server that the user has completed their task.

[1612] Server: Based on the received completion status, update the database task status and prepare to assign the next task.

[1613] Specific example

[1614] For example, if a user is performing "assembly line work" (priority: high, estimated time: 120 minutes) in a factory, and the emotion engine detects a high level of stress from the user's facial expressions, it will automatically suggest a "short break." This will result in a notification on the device saying, "Let's take a short break," which can reduce the user's stress.

[1615] Examples of prompts to input into a generative AI model:

[1616] "Please generate code that analyzes a face in real time using a camera and suggests taking a break if a stressed state is detected."

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

[1618] Step 1:

[1619] The user inputs a list of tasks via a terminal. The input includes task descriptions such as "assembly line work," "quality inspection," and "maintenance work." The terminal sends this task list to the server. The server receives the task list, assigns a unique ID to each task, and stores it in a database. At this stage, data processing involves mapping the task description to its ID.

[1620] Step 2:

[1621] Users set a priority (high, medium, low) and estimated time (in minutes or hours) for each task. This configuration information is sent from the terminal to the server. The server adds the received configuration information to the task list and updates the database. At this stage, a data calculation is performed to merge the priority and estimated time information into the task list.

[1622] Step 3:

[1623] The server retrieves a list of tasks and their configuration information from the database and uses an algorithm to sort the tasks by priority. Emotional data from the emotion engine is also considered during this process. Tasks are dynamically distributed based on the emotional state data. This emotional data processing includes the user's real-time stress level and fatigue level.

[1624] Step 4:

[1625] The emotion engine uses cameras and voice input devices to analyze the user's facial expressions and voice in real time and recognize their emotional state (stress, fatigue, satisfaction). Specific operations include preprocessing of image and audio data, feature extraction, and emotion recognition through classification models. The user's facial images and voice are provided as input, and emotional states such as "high stress" or "fatigue" are obtained as output.

[1626] Step 5:

[1627] The server receives data from the emotion engine and dynamically adjusts the priority and allocation of tasks based on the user's emotional state. For example, if a user is in a high-stress state, it may assign lower-priority tasks or suggest short breaks. Here, the emotional data is input into the task allocation algorithm, and the output is an adjusted list of tasks.

[1628] Step 6:

[1629] The server assigns tasks at the optimal time, taking into account the user's schedule information. The terminal displays the received task schedule to the user. The user checks the schedule, makes any necessary corrections, and enters the corrections into the terminal. The terminal sends the correction information to the server, and the server updates the database based on the received correction information.

[1630] Step 7:

[1631] The user starts a task and marks it as "completed" on their terminal upon completion. The terminal notifies the server of this completion status. The server updates the task status in the database based on the received completion status and prepares to assign the next task. At this point, as part of the data processing, the completion status is marked in the task list, and the next task is assigned by the server.

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

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

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

[1635] [Fourth Embodiment]

[1636] Figure 7 shows an example of the configuration of the data processing system 410 according to the fourth embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

[1649] System Overview

[1650] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system includes functions for obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[1651] Program processing

[1652] The program of this system operates with the server, terminal, and user each fulfilling their respective roles as follows:

[1653] Obtaining a list of tasks

[1654] User: Enters a list of tasks (e.g., report creation, meeting preparation, email reply) into the terminal.

[1655] Terminal: Sends the entered list of tasks to the server.

[1656] Server: Receives the task list and saves it to the database. Assigns a unique ID to each task for management.

[1657] Priority and time settings

[1658] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[1659] Terminal: Saves configuration information in a format that sends it to the server.

[1660] Server: Adds the received configuration information to the task list and updates the database.

[1661] Distribution of tasks

[1662] Server: Retrieves a list of tasks and their configuration information from the database, uses an algorithm to sort the tasks by priority, and prepares them for distribution to each user in the next step.

[1663] Sorting by priority: Tasks with particularly high priority are placed first.

[1664] Distribute tasks efficiently, taking estimated time into consideration.

[1665] Task assignment

[1666] Server: Retrieves user schedule information and assigns each task at the optimal time.

[1667] Server: Sends the assigned work schedule to the terminal.

[1668] Confirmation and acceptance of the work schedule.

[1669] Terminal: Displays received work schedules to the user.

[1670] User: Check the schedule, make any necessary corrections, and resend it to the server.

[1671] Server: Receives the changes and updates the database again.

[1672] Monitoring progress

[1673] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1674] Terminal: Sends completion status to the server.

[1675] Server: Updates the task status in the database and notifies the user if there are tasks to assign next.

[1676] Specific example

[1677] For example, the following task list is entered by the user:

[1678] 1. Report creation (Priority: High, Estimated time: 2 hours)

[1679] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1680] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[1681] Obtaining and setting up the task list

[1682] 1. User: Enter the task list into the terminal (e.g., write a report, prepare for a meeting, reply to emails).

[1683] 2. Terminal: Sends the task list to the server.

[1684] 3. Server: Stores the task list in the database and assigns a unique ID to each task.

[1685] 4. User: Enter priority and estimated time for each task.

[1686] 5. Terminal: Sends configuration information to the server.

[1687] Work distribution and allocation

[1688] 1. Server: Prioritize tasks based on their importance (e.g., report creation → meeting preparation → email reply).

[1689] 2. Server: Assigns the rearranged tasks to each user's schedule at the most opportune time.

[1690] 3. Server: Sends schedule information to the terminal.

[1691] Monitoring of work schedules and progress

[1692] 1. Terminal: Displays the assigned schedule to the user.

[1693] 2. User: Starts tasks one after another and marks them as "completed" on the terminal upon completion.

[1694] 3. Terminal: Sends completion status to the server.

[1695] 4. Server: Updates the database status and notifies users of the next task.

[1696] This allows for efficient task distribution, enabling users to effectively complete their tasks. Furthermore, the server constantly monitors progress and updates the database in real time, simplifying overall project management.

[1697] The following describes the processing flow.

[1698] Step 1:

[1699] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[1700] Step 2:

[1701] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[1702] Step 3:

[1703] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[1704] Step 4:

[1705] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[1706] Step 5:

[1707] Terminal: Sends information about the configured priority and estimated time to the server.

[1708] Step 6:

[1709] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[1710] Step 7:

[1711] Server: Retrieves a list of tasks and their configuration information from the database. After retrieval, it uses an algorithm to sort the tasks in order of priority.

[1712] Step 8:

[1713] Server: Executes a distribution algorithm based on the sorted tasks and distributes them to each user. At this time, it distributes tasks efficiently, taking into account the estimated time for each task.

[1714] Step 9:

[1715] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[1716] Step 10:

[1717] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[1718] Step 11:

[1719] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[1720] Step 12:

[1721] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[1722] Step 13:

[1723] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[1724] Step 14:

[1725] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1726] Step 15:

[1727] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[1728] Step 16:

[1729] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[1730] Step 17:

[1731] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[1732] This series of processing steps ensures that tasks are distributed efficiently, allowing users to proceed with their work systematically. Furthermore, real-time progress management prevents delays and omissions in tasks.

[1733] (Example 1)

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

[1735] Traditional business management systems often require manual prioritization and time estimation for tasks, leaving room for improvement in the efficiency of task allocation and schedule management. In particular, the lack of a function to monitor task progress in real time and update the database based on completion status makes overall task management cumbersome. As a result, individual users may not be able to perform tasks at the optimal time, potentially leading to delays in project progress.

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

[1737] In this invention, the server includes means for acquiring business information, means for setting priorities and estimated times for the acquired business information, means for distributing business based on the set priorities and estimated times, means for assigning business at the optimal timing based on the user's timetable information, means for monitoring the progress of each business, and means for receiving business completion status and updating the database. This enables efficient distribution and management of business, allowing users to perform tasks at the optimal time. Furthermore, the server's real-time monitoring of progress and database updates simplify overall business management.

[1738] "Business information" refers to data that includes detailed information such as the content, purpose, deadline, and person in charge of the work.

[1739] "Priority" is an indicator that shows the importance or urgency of a task, and is usually set on a three-tiered scale: high, medium, and low.

[1740] "Estimated time" refers to a unit of time estimated to be required to complete a specific task.

[1741] "Distributing" refers to the process by which a server assigns tasks to the appropriate personnel and time slots.

[1742] "Timetable information" refers to information that shows the user's schedule data, such as their appointments and free time.

[1743] "Monitoring progress" refers to the act of checking the progress of tasks in real time and updating the database as needed.

[1744] "Completion status" refers to information indicating that a specific task has been completed, and this information is recorded in the database by the server.

[1745] "Modifying a database" refers to the process of updating, deleting, or adding to the contents of a database based on the information received.

[1746] An "identification number" is a unique ID assigned to uniquely identify each business or piece of data.

[1747] System Overview

[1748] This invention is a system for the efficient distribution and management of tasks, in which the server, terminal, and user cooperate to optimize task execution. This system has the following functions:

[1749] 1. Acquisition of business information

[1750] 2. Setting priorities and estimated times

[1751] 3. Distribution of tasks

[1752] 4. Assignment of tasks

[1753] 5. Monitoring progress

[1754] The server works in conjunction with a database management system (e.g., MySQL) to store and manage business information and configuration data. The terminal accepts user input and communicates data with the server. Users input business information and report progress via the terminal.

[1755] System details

[1756] Acquisition of business information

[1757] Users input work information into a terminal. This information includes the content and purpose of the work. The terminal packages this information into packets and sends an HTTP request to the server. The server stores the received work information in a database and assigns an identification number to each work.

[1758] Setting Priorities and Estimated Times

[1759] Users set priority levels (e.g., high, medium, low) and estimated time (in hours) for each task on their terminal. The terminal bundles the configuration information into a packet and sends it back to the server. The server receives the configuration information, adds it to the task information, and updates the database.

[1760] Distribution of tasks

[1761] The server retrieves business and configuration information from the database and sorts it by priority using a sorting algorithm within the program. Specifically, Python or Java programs can be used.

[1762] Task assignment

[1763] The server retrieves the user's timetable information and assigns tasks at the optimal time based on that information. The server can use the Google Calendar API or the API of a company's scheduling software to retrieve timetable information. The schedule information for the assigned tasks is sent from the server to the terminal.

[1764] Monitoring of progress

[1765] Users mark each completed task as "completed" on their terminal. The terminal sends the completion status to the server. The server updates its database based on the received completion status and notifies the user if there are any further tasks.

[1766] Specific example

[1767] For example, the following list of tasks is entered by the user.

[1768] Report preparation (Priority: High, Estimated time: 2 hours)

[1769] Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1770] Email reply (Priority: Low, Estimated time: 30 minutes)

[1771] Users enter this information into their terminals and send it from the terminals to the server. The server stores this information in a database and assigns an identification number to it. The user then sets the priority and estimated time and sends it to the server again. The server distributes tasks based on this data, assigns them appropriately according to the user's schedule, and monitors the progress.

[1772] Examples of prompt statements

[1773] For example, here is an example of a prompt message to check the system via a generative AI model:

[1774] "Please use this system to create tomorrow's work schedule. The task list should include the following, along with priority and estimated time."

[1775] 1. Report creation (Priority: High, Estimated time: 2 hours)

[1776] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1777] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[1778] As described above, this system enables efficient distribution and management of tasks, allowing users to perform their tasks at the optimal time. Furthermore, the server monitors progress in real time and updates the database, simplifying overall task management.

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

[1780] Step 1:

[1781] The user enters work information into the terminal.

[1782] Input: Detailed information such as the nature and purpose of the work, and the person in charge.

[1783] Specific actions: The user opens the application on their device, enters work-related information such as "Create Report," "Prepare for Meeting," or "Reply to Email" into a form, and clicks the submit button.

[1784] Output: The entered business information is temporarily stored in the terminal's memory.

[1785] Step 2:

[1786] The terminal sends business information to the server.

[1787] Input: Business information entered by the user.

[1788] Specific operation: The terminal collects the entered business information into a packet and generates an HTTP request to the server. Then, it sends the request to the server.

[1789] Output: Business information is sent to the server.

[1790] Step 3:

[1791] The server receives business information and saves it to the database.

[1792] Input: Business information sent from the terminal.

[1793] Specific operation: The server receives an HTTP request and parses the business information. This information is stored in a database management system (e.g., MySQL), and an identification number is assigned to each business.

[1794] Output: Business information stored in the database and the identification number assigned to it.

[1795] Step 4:

[1796] Users set priorities and estimated timeframes for each task.

[1797] Input: Business information stored in the database.

[1798] Specific operation: The user sets the priority (high, medium, low) and estimated time (in hours) for each task using dropdown menus or input fields on their device. Once the settings are complete, they click the submit button.

[1799] Output: The set priority and estimated time are temporarily stored in the device's memory.

[1800] Step 5:

[1801] The device sends configuration information to the server.

[1802] Input: User-defined priority and estimated time.

[1803] Specific operation: The terminal bundles the configuration information into a packet, generates an HTTP request to the server again, and sends it.

[1804] Output: Configuration information is sent to the server.

[1805] Step 6:

[1806] The server adds the received configuration information to the business information and updates the database.

[1807] Input: Configuration information sent from the device.

[1808] Specific operation: The server analyzes the received configuration information and adds it to existing business information. The corresponding record in the database is then updated.

[1809] Output: Task information, including priority and estimated time, is saved to the database.

[1810] Step 7:

[1811] The server retrieves business information and configuration information from the database and sorts them using an algorithm.

[1812] Input: Business information and configuration information stored in the database.

[1813] Specific operation: The server executes SQL queries to retrieve business information and configuration information. Then, a sorting algorithm is executed within a Python or Java program to sort the business items based on priority.

[1814] Output: A list of tasks sorted by priority.

[1815] Step 8:

[1816] The server retrieves the user's timetable information and assigns tasks at the optimal time.

[1817] Input: A sorted list of tasks and user timetable information.

[1818] Specific operation: The server retrieves timetable information from the Google Calendar API or the company's scheduling software, and then assigns tasks at the appropriate times based on that information.

[1819] Output: A list of tasks assigned to each user at the optimal time.

[1820] Step 9:

[1821] The server sends the assigned work schedule to the terminal.

[1822] Input: A list of tasks assigned to the user at the optimal time.

[1823] Specific operation: The server bundles the work schedule into packets and sends an HTTP response to the user's terminal.

[1824] Output: The work schedule is sent to the terminal.

[1825] Step 10:

[1826] The terminal displays the received work schedule to the user.

[1827] Input: Work schedule sent from the server.

[1828] Specific operation: The application on the terminal analyzes the received schedule data and displays it in the GUI.

[1829] Output: The work schedule displayed to the user.

[1830] Step 11:

[1831] The user checks the schedule, makes corrections if necessary, and resends it to the server.

[1832] Input: Work schedule displayed on the terminal.

[1833] Specific operation: The user makes a modification to the schedule and clicks the resend button to send the changes to the server.

[1834] Output: The corrected schedule information is sent from the terminal to the server.

[1835] Step 12:

[1836] The server receives the changes and updates the database again.

[1837] Input: Modified schedule information submitted by the user.

[1838] Specific operation: The server analyzes the changes and updates the corresponding records in the database.

[1839] Output: The corrected schedule information is saved to the database.

[1840] Step 13:

[1841] The user starts a task and marks it as "completed" on their device each time they finish.

[1842] Input: Progress status of tasks performed by the user.

[1843] Specific action: The user clicks the "Complete" button in the application on their device when they have finished a task.

[1844] Output: The progress of the task is recorded on the terminal.

[1845] Step 14:

[1846] The terminal sends a completion status to the server.

[1847] Input: Progress status of tasks marked as completed by the user.

[1848] Specific operation: The terminal bundles the completion status into a packet, generates an HTTP request to the server, and sends it.

[1849] Output: Completion status is sent to the server.

[1850] Step 15:

[1851] The server updates the database's operational status and notifies the user if there are any new tasks.

[1852] Input: Completion status sent from the terminal.

[1853] Specific operation: The server analyzes the completion status and updates the status of the corresponding record in the database. If there is a task to assign next, it generates and sends a notification message to the user.

[1854] Output: The database's business status is updated, and the next business notification is sent to the user.

[1855] (Application Example 1)

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

[1857] The distribution and progress management of tasks in logistics centers typically rely on manual labor, making them inefficient and prone to errors. Furthermore, it is difficult to appropriately set task priorities and estimated times, and to monitor progress in real time. As a result, delays and disruptions occur, leading to a decline in overall operational efficiency.

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

[1859] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, and means for efficiently monitoring the distribution and progress of each task in the logistics center. This enables efficient and accurate distribution and progress management of tasks in the logistics center, thereby improving overall operational efficiency.

[1860] A "task list" refers to a list that enumerates specific tasks, indicating the work that the user should perform.

[1861] "Priority" is an indicator that shows the importance or urgency of a task, and is expressed in grades such as "high," "medium," and "low."

[1862] "Estimated time" refers to the predicted time required to complete a specific task, and is expressed in hours.

[1863] "Distribution" refers to the process of organizing tasks in the appropriate order and assigning them to each user based on set priorities and estimated timeframes.

[1864] "Schedule information" refers to information that indicates the time slots for each user's individual appointments and tasks, and is used for assigning tasks.

[1865] "Progress status" refers to status information that indicates the stage of a task, and requires real-time monitoring.

[1866] A "logistics center" refers to a facility where operations such as storage, sorting, processing, and shipping of goods are carried out, and it is a place where large-scale inventory management and logistics operations take place.

[1867] "Efficient" refers to a state where there is no waste, and the resources and time required to achieve a goal are minimized.

[1868] "Distribution and progress monitoring" refers to a series of operations that involve appropriately assigning tasks and monitoring their progress in real time.

[1869] "Completion status" refers to information indicating that a specific task has been completed, and this information is reflected in other systems when updated in the database.

[1870] A "database" refers to an information management system that organizes and stores large amounts of data, making it possible to quickly search and use it as needed.

[1871] This invention is a system for efficiently distributing and managing the progress of tasks in a logistics center. The system operates collaboratively among a server, terminals, and users, providing a series of functions including obtaining task lists, setting priorities and estimated times, distributing tasks, assigning tasks, and monitoring progress.

[1872] System Configuration

[1873] The system consists of the following main components:

[1874] Server: Stores data, distributes tasks, and monitors progress.

[1875] Terminals (smartphones, robots): These devices handle data input from the user and display the received information.

[1876] User: Enter tasks into the task list, set priorities and estimated times, and check and update progress.

[1877] Hardware and software to use

[1878] Hardware:

[1879] Smartphone (a typical smartphone device)

[1880] Robots (such as automated guided vehicles and picking robots)

[1881] software:

[1882] Server programs (Python, Flask API, etc.)

[1883] Databases (MySQL, PostgreSQL, etc.)

[1884] Client applications (mobile apps, robot control software)

[1885] Specific example

[1886] Obtaining a list of tasks

[1887] Users input each task performed at the logistics center into a smartphone application. Examples of tasks include picking, packing, and quality checks. The terminal sends this task list to a server, which stores the list in a database and assigns a unique ID to each task.

[1888] Setting Priorities and Estimated Times

[1889] Users set priority levels (high, medium, low) and estimated time (in hours) for each task within the application. The terminal sends this configuration information to the server, which updates the database based on the received information.

[1890] Work distribution and allocation

[1891] The server sorts tasks based on configured priorities and estimated times, distributing them to each user in the optimal order. Especially in logistics centers, where efficient task distribution is crucial, the server considers the schedule information of each worker and robot, assigning tasks at the appropriate time.

[1892] Monitoring progress

[1893] Users begin their assigned tasks and, upon completion, send a completion status to the server via their terminal. The server reflects this information in its database and notifies the user of their next task, enabling real-time progress monitoring.

[1894] Example of a prompt

[1895] Examples of prompts that can be used when describing this application with a generative AI model include:

[1896] "Please explain the work distribution system in the logistics center."

[1897] "Please explain in detail how to prioritize tasks, set estimated timeframes, and allocate them efficiently."

[1898] "Please explain how the staff and robots at the logistics center monitor operations and update progress in real time."

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

[1900] Step 1: Obtain the task list

[1901] Users input each task at the logistics center (picking, packing, quality checks, etc.) into a smartphone application. This input data includes the task name, details, and related information. The terminal sends this task list to the server. The server stores the received task list in a database and assigns a unique ID to each task. The input data consists of the task name and details, while the output data is a task list with unique IDs assigned to each task.

[1902] Step 2: Setting priorities and estimated time

[1903] Users set priority levels (high, medium, low) and estimated time (in hours) for each task via a smartphone application. The device sends this configuration information to the server. The server updates the task list in the database based on the received information. The input data is the priority level and estimated time, and the output data is the updated task list.

[1904] Step 3: Distribution of tasks

[1905] The server sorts tasks based on configured priorities and estimated times. Especially in logistics centers where efficient task allocation is crucial, the server considers each worker's schedule information to determine the optimal order for the next task allocation. Input data includes priorities and estimated times, while output data is a sorted list of tasks.

[1906] Step 4: Assigning tasks

[1907] The server assigns tasks to each user at the optimal time based on their schedule information. The server compares the schedule information with a sorted list of tasks, assigns tasks to each user at their most suitable time, and sends the assignment information to the terminal. Input data consists of schedule information and a sorted list of tasks, while output data is the assignment schedule for each user.

[1908] Step 5: Confirm and accept the work schedule.

[1909] The terminal displays the received work schedule on the user's smartphone. The user can review the schedule and make corrections as needed. The user's corrections are sent back to the server via the terminal. The server updates the database based on the corrections. The input data is the schedule information corrected by the user, and the output data is the updated schedule information.

[1910] Step 6: Monitoring progress

[1911] The user starts the assigned task and sends a "completed" status to the server via their terminal upon completion. The server receives the completion status and updates the task status in the database. If there is another task to assign, the server notifies the user. The input data is the status of the completed task, and the output data is the updated task status and the next task notification.

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

[1913] System Overview

[1914] This invention combines a system for the efficient distribution and management of tasks with an emotion engine that recognizes user emotions, thereby achieving optimal task execution according to the user's state. The server, terminal, user, and emotion engine work together to improve work efficiency and reduce user stress.

[1915] Program processing

[1916] The program of this system operates with the server, terminal, user, and emotion engine each fulfilling their respective roles, as follows:

[1917] Obtaining and setting up the task list

[1918] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[1919] Terminal: Sends the entered list of tasks to the server.

[1920] Server: Receives the task list and saves it to the database. Each task is assigned a unique ID.

[1921] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[1922] Terminal: Saves configuration information in a format that sends it to the server.

[1923] Server: Adds the received configuration information to the task list and updates the database.

[1924] Work distribution and allocation

[1925] Server: Retrieves a list of tasks and their configuration information from the database, sorts the tasks by priority using an algorithm, and distributes the tasks while also taking into account input from the emotion engine.

[1926] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[1927] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is under high stress, it will assign lower-priority tasks for relaxation or rest.

[1928] Confirmation and acceptance of the work schedule.

[1929] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[1930] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[1931] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[1932] Server: Updates the database again based on the received correction information.

[1933] Monitoring progress

[1934] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1935] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[1936] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[1937] Specific example

[1938] For example, the following task list is entered by the user:

[1939] 1. Report creation (Priority: High, Estimated time: 2 hours)

[1940] 2. Meeting preparation (Priority: Medium, Estimated time: 1 hour)

[1941] 3. Email reply (Priority: Low, Estimated time: 30 minutes)

[1942] Using an Emotion Engine

[1943] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[1944] 2. Emotion Engine: If the system determines that the user is in a high-stress state, it sends this information to the server.

[1945] 3. Server: Considering the emotion engine data, adjust task priorities and change the next task to be performed to reduce user stress as much as possible. Also, suggest breaks at appropriate times.

[1946] This allows users to receive task assignments that take their emotional state into consideration, enabling a more comfortable work environment. By having the server constantly monitor progress and emotional state, work efficiency can be improved while reducing mental stress.

[1947] The following describes the processing flow.

[1948] Step 1:

[1949] User: Enter the task list into the terminal. For example, enter tasks such as "Create report," "Prepare for meeting," and "Reply to email."

[1950] Step 2:

[1951] Terminal: Sends the list of tasks entered by the user to the server. Each task is then assigned a unique identifier.

[1952] Step 3:

[1953] Server: Receives the task list and saves it to the database. At this time, a unique ID is added to each task for management.

[1954] Step 4:

[1955] User: Set priority (e.g., high, medium, low) and estimated time (in hours) for each task.

[1956] Step 5:

[1957] Terminal: Sends information about the configured priority and estimated time to the server.

[1958] Step 6:

[1959] Server: Adds the received configuration information to the task list and updates the database. The task list and its configuration information are stored there.

[1960] Step 7:

[1961] Server: Retrieves a list of tasks and their configuration information from the database, and uses an algorithm to sort the tasks in order of priority.

[1962] Step 8:

[1963] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state (e.g., stress, fatigue, satisfaction) in real time.

[1964] Step 9:

[1965] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. For example, if a user is in a high-stress state, it assigns lower-priority tasks to encourage relaxation and rest.

[1966] Step 10:

[1967] Server: Retrieves user schedule information and assigns tasks at the optimal time. For example, assigns "report writing" in the morning, "meeting preparation" in the afternoon, and "email replies" later in the day.

[1968] Step 11:

[1969] Server: Sends the assigned work schedule to the terminal. A customized schedule is provided for each user.

[1970] Step 12:

[1971] Terminal: Displays received work schedules to the user. The user checks the schedule and makes corrections if there are any problems.

[1972] Step 13:

[1973] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal then resends the correction information to the server.

[1974] Step 14:

[1975] Server: The database is updated again based on the received correction information. The corrected schedule is then reflected.

[1976] Step 15:

[1977] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[1978] Step 16:

[1979] Terminal: The terminal sends a completion status to the server to notify the server that the user has completed the task.

[1980] Step 17:

[1981] Server: Updates the database task status based on the received completion status. Preparations are made to assign the next task.

[1982] Step 18:

[1983] Server: Notifies the user if there is another task to assign. Allows the user to start the next task.

[1984] This allows for efficient task distribution, enabling users to proceed with their work systematically. Furthermore, real-time management of progress and emotional states improves work efficiency while reducing mental stress.

[1985] (Example 2)

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

[1987] While conventional business management systems can efficiently distribute and manage tasks, they struggle to adjust tasks while considering the user's emotional state. This led to increased mental burden on users and decreased productivity. There was a need for a system that could dynamically adjust task priorities and allocation based on the user's emotional state, thereby improving efficiency and reducing user stress.

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

[1989] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for analyzing the user's emotional state using an emotion engine that recognizes the user's state, means for assigning tasks at the optimal timing based on the user's emotional state and schedule information, means for monitoring the progress of each task, and means for dynamically adjusting the priority and distribution of tasks according to the emotional state. This enables efficient distribution and management of tasks while allowing for flexible task adjustments that take into account the user's emotional state.

[1990] A "task list" is a list of the names and contents of each task that the user is to perform.

[1991] "Priority" is an indicator that shows the order and importance of tasks to be performed.

[1992] "Estimated time" is an estimate of the time a user believes they will need to complete each task.

[1993] "Distribution" is the process of assigning multiple tasks based on specific criteria.

[1994] "User state" refers to the user's emotional state, health status, activity level, etc.

[1995] An "emotion engine" is a device or program that analyzes a user's facial expressions, voice, and behavioral data to recognize their emotional state.

[1996] "Schedule information" refers to time-related information such as the user's appointments and schedules.

[1997] "Progress status" indicates the extent to which each task has been completed.

[1998] "Dynamic adjustment" refers to the act of instantly changing settings and allocations based on real-time data and status.

[1999] A "server" is a central computing system used for data processing, storage, and communication.

[2000] This invention combines a system for the efficient distribution and management of tasks with an emotion engine that recognizes user emotions, thereby achieving optimal task execution according to the user's state. The server, terminal, user, and emotion engine work together to improve work efficiency and reduce user stress.

[2001] System Overview

[2002] This system uses the following hardware and software:

[2003] Server: A central computing system that handles data processing, storage, and communication. It manages task lists, executes algorithms, and processes data from emotion engines, among other things.

[2004] Terminal: A device used by users to input and confirm information (such as a PC, smartphone, or tablet). It is responsible for sending user input to the server and displaying the information from the server to the user.

[2005] Emotion engine: A device or program for recognizing a user's emotional state. It analyzes the user's facial expressions and voice using a camera and microphone to recognize their emotional state in real time.

[2006] Obtaining and setting up the task list

[2007] User: Enters a list of tasks through the terminal interface. Examples of specific tasks include "report creation," "meeting preparation," and "email reply."

[2008] Terminal: Sends the entered task list to the server. The communication module is used to send the task list as a POST request to the specified API endpoint.

[2009] Server: Stores the received list of tasks in the database and assigns a unique ID to each task.

[2010] User: Set priority (high, medium, low) and estimated time (in hours) for each task.

[2011] Terminal: Sends the configured information to the server.

[2012] Server: Adds the received configuration information to the task list and updates the database.

[2013] Work distribution and allocation

[2014] Server: Retrieves a list of tasks and their configuration information from the database. The retrieved list of tasks is then sorted by priority using an algorithm.

[2015] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time.

[2016] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state.

[2017] Confirmation and acceptance of the work schedule.

[2018] Server: Assigns tasks at the optimal time, taking into account the user's schedule information.

[2019] Terminal: Displays received work schedules to the user.

[2020] User: Check the schedule and enter any necessary corrections.

[2021] Terminal: Resends correction information to the server.

[2022] Server: Updates the database again based on the received correction information.

[2023] Monitoring progress

[2024] User: Start a task and mark it as "Completed" on the terminal as it is finished.

[2025] Terminal: Notifies the server of the status of completed tasks.

[2026] Server: Based on the received completion status, the server updates the task status in the database and prepares to assign the next task.

[2027] Using an Emotion Engine

[2028] 1. User: During work, the emotion engine recognizes the user's emotional state in real time through the camera and microphone.

[2029] 2. Emotion Engine: When it determines that the user is in a high-stress state, it sends that information to the server.

[2030] 3. Server: Considers the emotion engine's data and adjusts task priorities. For example, it might change the next task to be performed to reduce stress and suggest a break.

[2031] This allows users to receive optimal task assignments tailored to their emotional state, enabling them to work comfortably. Furthermore, the server constantly monitors progress and emotional state, improving work efficiency and reducing mental stress.

[2032] Example of a prompt

[2033] The following are specific examples of prompt statements for generative AI models:

[2034] "Please describe an algorithm that adjusts task priorities based on the user's emotional state."

[2035] "Could you explain the technical mechanisms and applications of an emotion engine that recognizes user emotions in real time?"

[2036] The above describes the details of embodiments for carrying out the present invention.

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

[2038] Step 1:

[2039] User: Enter the task list into the terminal. For example, specific tasks such as "write a report," "prepare for a meeting," and "reply to emails" are entered using the terminal's dedicated application.

[2040] Input: Job description

[2041] Output: A list of tasks is displayed on the terminal.

[2042] Step 2:

[2043] Terminal: Sends the entered task list to the server. The terminal uses a communication module to send the task list as a POST request to the specified API endpoint.

[2044] Input: User-entered list of tasks

[2045] Output: The server receives the task list.

[2046] Step 3:

[2047] Server: Saves the received list of tasks to the database and assigns a unique ID to each task. Executes an INSERT statement into the database.

[2048] Input: Task list sent from the terminal

[2049] Output: List of tasks and unique IDs stored in the database

[2050] Step 4:

[2051] User: Set priority (high, medium, low) and estimated time (in hours) for each task. Enter detailed information for each task through the terminal interface.

[2052] Input: Task priority and estimated time

[2053] Output: The settings information is reflected on the device.

[2054] Step 5:

[2055] Terminal: Sends user-configured information to the server. The configuration information is sent to the server as a POST request using a communication module.

[2056] Input: Priority and estimated time for the configured task

[2057] Output: The server receives the configuration information.

[2058] Step 6:

[2059] Server: Adds the received configuration information to the task list and updates the database. Executes an UPDATE statement against the database.

[2060] Input: Configuration information sent from the device

[2061] Output: Updated task list in the database

[2062] Step 7:

[2063] Server: Retrieves a list of tasks and their configuration information from the database. Executes a SELECT statement to read the necessary task information.

[2064] Input: Task list and configuration information in the database

[2065] Output: Acquired task list and configuration information

[2066] Step 8:

[2067] Server: The retrieved list of tasks is sorted by priority using an algorithm. The algorithm is implemented in Python or similar languages, and sorts the tasks considering priority and estimated time.

[2068] Input: Task list and its settings information

[2069] Output: Task list sorted by priority

[2070] Step 9:

[2071] Emotion Engine: Analyzes user facial expressions, voice, and behavioral data to recognize the user's emotional state in real time. The emotion engine acquires and processes data from the camera and microphone.

[2072] Input: User's facial expressions, voice, and behavioral data

[2073] Output: Analysis results of the user's emotional state

[2074] Step 10:

[2075] Server: Receives data from the emotion engine and dynamically adjusts task priorities and allocation based on the user's emotional state. Reads emotion data from storage and applies it to the current task list.

[2076] Input: Emotional state data from the emotion engine

[2077] Output: Adjusted task list

[2078] Step 11:

[2079] Server: Combines user schedule information with other data to assign tasks at the optimal time. Calendar information is also retrieved from the database and applied to task assignments.

[2080] Input: User's schedule information and a list of tasks sorted by priority.

[2081] Output: Assigned work schedule

[2082] Step 12:

[2083] Terminal: Displays received work schedules to the user. Presents the schedule visually through a dedicated interface.

[2084] Input: Work schedule sent from the server

[2085] Output: Schedule displayed on the user's terminal

[2086] Step 13:

[2087] User: Check the schedule and enter any necessary corrections. Enter the correction information using the terminal interface.

[2088] Input: Confirmation and modification of work schedule.

[2089] Output: Input of correction information

[2090] Step 14:

[2091] Terminal: Resends correction information to the server. The correction information is sent to the server as a POST request using the communication module.

[2092] Input: Correction information entered by the user

[2093] Output: The server receives the correction information.

[2094] Step 15:

[2095] Server: Based on the received correction information, update the database again. Execute the UPDATE statement to update the data.

[2096] Input: Correction information sent from the device

[2097] Output: Updated database

[2098] Step 16:

[2099] User: Start a task and mark it as "Completed" on the terminal as it is finished. Click the completion button using a dedicated button or checkbox.

[2100] Input: Mark as completed

[2101] Output: Tasks marked as completed

[2102] Step 17:

[2103] Terminal: Notifies the server of the status of completed tasks. Formats the data and sends it to the server via the communication module.

[2104] Input: User-marked task completion status

[2105] Output: Completion status received by the server

[2106] Step 18:

[2107] Server: Updates the database task status based on the received completion status. Executes an UPDATE statement to change the task status to "Completed". Prepares for assigning the next task.

[2108] Input: Completion status sent from the terminal

[2109] Output: Updated database business status

[2110] The above outlines the specific processing steps of a system that efficiently distributes and manages tasks. This enables flexible task adjustments that take into account the emotional state of users.

[2111] (Application Example 2)

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

[2113] In today's work environment, there is a strong demand for improved work efficiency and reduced worker stress. However, conventional systems focus on improving work efficiency while failing to adequately consider the emotional state and mental burden of workers. As a result, while work efficiency may improve, worker stress and fatigue may increase, potentially leading to a decrease in overall efficiency and productivity. In particular, in workplaces such as factories, excessive stress is a problem as it increases the risk of work errors and accidents. Against this backdrop, there is a need for a system that analyzes the emotional state of workers in real time and dynamically adjusts work accordingly.

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

[2115] In this invention, the server includes means for acquiring a list of tasks, means for setting priorities and estimated times for the acquired list of tasks, means for distributing tasks based on the set priorities and estimated times, means for assigning tasks at the optimal timing based on the user's schedule information, means for monitoring the progress of each task, means for analyzing the user's emotional state in real time using a camera and voice input device, and means for dynamically adjusting the priority and distribution of tasks based on the analyzed emotional state. This makes it possible to monitor the user's emotional state in real time and propose optimal task distribution and breaks based on it.

[2116] A "task list" is a compilation of multiple tasks that a user must perform.

[2117] "Priority" is an indicator that shows the importance and urgency of each task.

[2118] "Estimated time" is an estimate of the time required to complete each task.

[2119] "User schedule information" refers to the timetable and schedule information that users use to carry out their daily activities.

[2120] "Progress status" refers to the state of how far along a task is.

[2121] "Cameras and audio input devices" refer to hardware used to capture the user's facial expressions and voice.

[2122] "Emotional state" refers to a mental state that includes the type and intensity of emotions a user expresses.

[2123] "Dynamic adjustment" refers to changing something in real time according to the situation.

[2124] This invention is a system aimed at improving operational efficiency and reducing worker stress in workplaces such as factories. It involves collaboration between a server, a terminal, and a user. An emotion engine analyzes the user's emotional state in real time and dynamically adjusts tasks based on that analysis.

[2125] The overall system consists of the following elements:

[2126] 1. Server: Plays a central role and manages the database.

[2127] 2. Terminal: Operated by the user, it is used to input task lists and report completion status.

[2128] 3. User: A worker who performs tasks while operating a terminal.

[2129] 4. Emotion Engine: Analyzes the user's facial expressions and voice data to recognize their emotional state.

[2130] Detailed system configuration and functions

[2131] Obtaining and setting up the task list

[2132] User: Use the terminal to enter a list of tasks. For example, enter tasks such as "assembly line work," "quality inspection," and "maintenance work."

[2133] Terminal: Sends the entered list of tasks to the server.

[2134] Server: Receives the task list and saves it to the database. Each task is assigned a unique ID.

[2135] User: Set priority and estimated time for each task.

[2136] Terminal: Sends configuration information to the server.

[2137] Server: Adds the received configuration information to the task list and updates the database.

[2138] Work distribution and allocation

[2139] Server: Retrieves a list of tasks and their configuration information from the database, sorts the tasks by priority using an algorithm, and distributes the tasks while also taking into account input from the emotion engine.

[2140] Emotion Engine: Uses cameras and voice input devices to analyze the user's facial expressions, voice, and behavioral data in real time to recognize their emotional state (e.g., stress, fatigue, satisfaction).

[2141] Server: Receives data from the emotion engine and adjusts task priorities and allocations based on the user's emotional state. If the user is in a high-stress state, it assigns lower-priority tasks or breaks.

[2142] Confirmation and acceptance of the work schedule.

[2143] Server: Assigns tasks at the optimal time, taking into account user schedule information.

[2144] Terminal: Displays received work schedules to the user, who may review and modify the schedule.

[2145] User: Check the schedule, make any necessary corrections, and enter the corrections into the terminal. The terminal sends the correction information to the server.

[2146] Server: Updates the database based on the received correction information.

[2147] Monitoring progress

[2148] User: Start a task and mark it as "Completed" on the terminal each time it is finished.

[2149] Terminal: Notifies the server that the user has completed their task.

[2150] Server: Based on the received completion status, update the database task status and prepare to assign the next task.

[2151] Specific example

[2152] For example, if a user is performing "assembly line work" (priority: high, estimated time: 120 minutes) in a factory, and the emotion engine detects a high level of stress from the user's facial expressions, it will automatically suggest a "short break." This will result in a notification on the device saying, "Let's take a short break," which can reduce the user's stress.

[2153] Examples of prompts to input into a generative AI model:

[2154] "Please generate code that analyzes a face in real time using a camera and suggests taking a break if a stressed state is detected."

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

[2156] Step 1:

[2157] The user inputs a list of tasks via a terminal. The input includes task descriptions such as "assembly line work," "quality inspection," and "maintenance work." The terminal sends this task list to the server. The server receives the task list, assigns a unique ID to each task, and stores it in a database. At this stage, data processing involves mapping the task description to its ID.

[2158] Step 2:

[2159] Users set a priority (high, medium, low) and estimated time (in minutes or hours) for each task. This configuration information is sent from the terminal to the server. The server adds the received configuration information to the task list and updates the database. At this stage, a data calculation is performed to merge the priority and estimated time information into the task list.

[2160] Step 3:

[2161] The server retrieves a list of tasks and their configuration information from the database and uses an algorithm to sort the tasks by priority. Emotional data from the emotion engine is also considered during this process. Tasks are dynamically distributed based on the emotional state data. This emotional data processing includes the user's real-time stress level and fatigue level.

[2162] Step 4:

[2163] The emotion engine uses cameras and voice input devices to analyze the user's facial expressions and voice in real time and recognize their emotional state (stress, fatigue, satisfaction). Specific operations include preprocessing of image and audio data, feature extraction, and emotion recognition through classification models. The user's facial images and voice are provided as input, and emotional states such as "high stress" or "fatigue" are obtained as output.

[2164] Step 5:

[2165] The server receives data from the emotion engine and dynamically adjusts the priority and allocation of tasks based on the user's emotional state. For example, if a user is in a high-stress state, it may assign lower-priority tasks or suggest short breaks. Here, the emotional data is input into the task allocation algorithm, and the output is an adjusted list of tasks.

[2166] Step 6:

[2167] The server assigns tasks at the optimal time, taking into account the user's schedule information. The terminal displays the received task schedule to the user. The user checks the schedule, makes any necessary corrections, and enters the corrections into the terminal. The terminal sends the correction information to the server, and the server updates the database based on the received correction information.

[2168] Step 7:

[2169] The user starts a task and marks it as "completed" on their terminal upon completion. The terminal notifies the server of this completion status. The server updates the task status in the database based on the received completion status and prepares to assign the next task. At this point, as part of the data processing, the completion status is marked in the task list, and the next task is assigned by the server.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[2188] Furthermore, the hardware structure of these various processors can more specifically utilize electrical circuits that combine circuit elements such as semiconductor devices. Also, the specific processing described above is merely an example. Therefore, it goes without saying that unnecessary steps can be deleted, new steps added, or the processing order rearranged, as long as it does not deviate from the main purpose.

[2189] The descriptions and illustrations presented above are detailed explanations of the technical aspects of this disclosure and are merely examples of the technical aspects. For example, the above descriptions of the structure, function, operation, and effect are examples of the structure, function, operation, and effect of the technical aspects of this disclosure. Therefore, it goes without saying that you may delete unnecessary parts, add new elements, or replace elements in the descriptions and illustrations presented above, as long as you do not deviate from the essence of the technical aspects of this disclosure. Furthermore, in order to avoid confusion and facilitate understanding of the technical aspects of this disclosure, explanations of common technical knowledge and the like that do not require special explanation to enable the implementation of the technical aspects of this disclosure have been omitted from the descriptions and illustrations presented above.

[2190] All documents, patent applications, and technical standards described herein are incorporated by reference to the same extent as if each individual document, patent application, and technical standard were specifically and individually noted to be incorporated by reference.

[2191] The following is further disclosed regarding the embodiments described above.

[2192] (Claim 1)

[2193] Methods for obtaining a list of tasks,

[2194] A means of setting priorities and estimated times for the acquired list of tasks,

[2195] A means of distributing tasks based on set priorities and estimated time,

[2196] A means of assigning tasks at the optimal time based on the user's schedule information,

[2197] A means of monitoring the progress of each task,

[2198] A system that includes this.

[2199] (Claim 2)

[2200] The system according to claim 1, wherein a unique ID is assigned to each task when obtaining a list of tasks by the means described above.

[2201] (Claim 3)

[2202] The system according to claim 1, which receives a completion status from the terminal and updates the database when the user completes the task by the means described above.

[2203] "Example 1"

[2204] (Claim 1)

[2205] Means of obtaining business information,

[2206] A means for setting priority and estimated time for acquired business information,

[2207] A means of distributing tasks based on set priorities and estimated time,

[2208] A means of assigning tasks at the optimal time based on the user's timetable information,

[2209] A means of monitoring the progress of each task,

[2210] A means to receive the task completion status and modify the database,

[2211] A system that includes this.

[2212] (Claim 2)

[2213] The system according to claim 1, wherein when acquiring business information by the means described above, an identification number is assigned to each business.

[2214] (Claim 3)

[2215] The system according to claim 1, which receives a completion status from the terminal and modifies the database when the user completes the task using the above means.

[2216] "Application Example 1"

[2217] (Claim 1)

[2218] Methods for obtaining a list of tasks,

[2219] A means of setting priorities and estimated times for the acquired list of tasks,

[2220] A means of distributing tasks based on set priorities and estimated time,

[2221] A means of assigning tasks at the optimal time based on the user's schedule information,

[2222] A means of monitoring the progress of each task,

[2223] A means to efficiently manage the distribution and progress monitoring of each task in a logistics center,

[2224] A system that includes this.

[2225] (Claim 2)

[2226] The system according to claim 1, which assigns a unique ID to each task.

[2227] (Claim 3)

[2228] The system according to claim 1, which receives a completion status when each task is completed and updates the database.

[2229] "Example 2 of combining an emotion engine"

[2230] (Claim 1)

[2231] Methods for obtaining a list of tasks,

[2232] A means of setting priorities and estimated times for the acquired list of tasks,

[2233] A means of distributing tasks based on set priorities and estimated time,

[2234] A means of analyzing a user's emotional state using an emotion engine that recognizes the user's state,

[2235] A means of assigning tasks at the optimal time based on the user's emotional state and schedule information,

[2236] A means of monitoring the progress of each task,

[2237] A means of dynamically adjusting the priority and allocation of tasks according to emotional state,

[2238] A system that includes this.

[2239] (Claim 2)

[2240] The system according to claim 1, wherein a unique ID is assigned to each task when obtaining a list of tasks by the means described above.

[2241] (Claim 3)

[2242] The system according to claim 1, which receives a completion status from the terminal and updates the database when the user completes the task by the means described above.

[2243] "Application example 2 of combining emotional engines"

[2244] (Claim 1)

[2245] Methods for obtaining a list of tasks,

[2246] A means of setting priorities and estimated times for the acquired list of tasks,

[2247] A means of distributing tasks based on set priorities and estimated time,

[2248] A means of assigning tasks at the optimal time based on the user's schedule information,

[2249] A means of monitoring the progress of each task,

[2250] A method for analyzing a user's emotional state in real time using cameras and voice input devices,

[2251] A means of dynamically adjusting the priority and allocation of tasks based on analyzed emotional states,

[2252] A system that includes this.

[2253] (Claim 2)

[2254] The system according to claim 1, which includes means for assigning a unique ID to each task when obtaining a list of tasks.

[2255] (Claim 3)

[2256] The system according to claim 1, which includes means for receiving a completion status from a terminal and updating a database when a user completes a task. [Explanation of symbols]

[2257] 10, 210, 310, 410 Data Processing Systems 12 Data Processing Devices 14 Smart Devices 214 Smart Glasses 314 Headset-type terminal 414 Robots< / url:> < / url:> < / url:> < / url:>

Claims

1. Methods for obtaining a list of tasks, A means of setting priorities and estimated times for the acquired list of tasks, A means of distributing tasks based on set priorities and estimated time, A means of assigning tasks at the optimal time based on the user's schedule information, A means of monitoring the progress of each task, A system that includes this.

2. The system according to claim 1, wherein a unique ID is assigned to each task when obtaining a list of tasks by the means described above.

3. The system according to claim 1, which receives a completion status from the terminal and updates the database when the user completes the task by the means described above.

Images