system

Abstract

We provide a system that automates a wide range of operational tasks efficiently and reliably. [Solution] A system including a means for automatically executing scheduled routine tasks, a means for notifying non-routine tasks and responding manually or automatically, a means for accepting and executing tasks requested by users, a means for conducting an account inventory and identifying unnecessary accounts, a means for monitoring the status of the system and automatically responding when an incident occurs, a means for initializing the system based on a template, a means for managing maintenance schedules and coordinating maintenance personnel, a means for collecting system performance data and analyzing it in real time, a means for automating the release of new software and changes, a means for automatically responding to user inquiries, a means for automatically managing and updating contracts, and a means for managing budget usage and detecting abnormal risks of budget overruns.

Description

[Technical Field]

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

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

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

[0004] Modern system operations involve a wide variety of management tasks that must be processed efficiently and reliably. Many tasks, including routine and non-routine tasks, requested work, account management, incident response, initial setup, maintenance schedule management, performance analysis, release work, inquiry response, contract management, and budget management, are performed manually, resulting in increased human error and delays. Furthermore, these tasks require a significant amount of time and effort, resulting in increased costs. Given this background, there is a demand for systems that can automate these diverse operational tasks efficiently and reliably. [Means for solving the problem]

[0005] To solve the above-mentioned problems, the present invention provides a system for automating various operational tasks. This system includes: means for automatically executing scheduled routine tasks; means for notifying non-routine tasks and manually or automatically responding to them; means for accepting and executing user-requested tasks; means for conducting an account inventory and identifying unnecessary accounts; means for monitoring the system status and automatically responding to incidents; means for initializing the system based on templates; means for managing maintenance schedules and coordinating maintenance personnel; means for collecting and analyzing system performance data in real time; means for automating the release of new software and changes; means for automatically responding to user inquiries; means for automatically managing and renewing contracts; and means for managing budget usage and detecting abnormal budget overrun risks. This system automates a wide range of operational tasks, reducing human error, improving work efficiency, and reducing management costs.

[0006] "Scheduling" is the process of planning a specific job or task to be performed at a predetermined time or date, and then automatically executing the job or task based on that plan.

[0007] "Regular operations" refers to repetitive tasks that are performed daily in system operation, such as taking backups and collecting logs.

[0008] "Non-routine tasks" refer to special tasks that occur irregularly during system operation, such as applying emergency patches or responding to system problems.

[0009] "Resources" refers to hardware and software elements such as computing power, memory, storage, and network bandwidth required for system operation.

[0010] A "requested operation" refers to the process in which a user requests a specific task or work from the system, and examples include creating a new account or extracting specific data.

[0011] "Account inventory" is the process of periodically checking the usage status of user accounts registered in the system and deleting unnecessary accounts as necessary.

[0012] An "incident" refers to a failure or problem that interferes with the normal operation of a system, including security breaches and server outages.

[0013] A "template" refers to a set of predefined standard procedures and parameters for performing specific tasks or settings, and is used to automatically configure and execute tasks.

[0014] A "maintenance schedule" refers to a timetable or schedule for carrying out regular inspections and maintenance work on a system.

[0015] "Performance Data" means data used to evaluate system performance, examples of which include CPU usage, memory usage, and network traffic.

[0016] "Release operations" refers to the process of rolling out a new software or system version, including testing, deployment, and configuration changes.

[0017] "Inquiry handling" is the process of providing appropriate answers and support to users' questions and reported problems.

[0018] "Contract management" is the process of concluding, renewing, and managing contracts related to system operations (licenses, service contracts, etc.).

[0019] "Budget control" is the process of monitoring the costs associated with system operation and ensuring that operations are being carried out appropriately within budget. [Brief explanation of the drawings]

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

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

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

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

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

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

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

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

[0028] [First embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

[0041] The system of the present invention automates and streamlines a wide range of tasks in system operation, and includes various programs for this purpose. Below, we will explain in natural language how the programs in this system work, using concrete examples.

[0042] Executing scheduled routine tasks

[0043] The server automatically performs routine tasks (e.g., daily backups) based on scheduling information set by the system administrator. At the set time, the server launches the backup process and begins backing up data. When the task is complete, a notification is sent to the user via the terminal, and the backup status can be checked on the dashboard.

[0044] Notification and response to non-routine operations

[0045] Users can request non-routine tasks (e.g., installing emergency patches) from the system. The request is sent to the server via the terminal. When the server receives the request, it analyzes and executes the appropriate response procedure. Once the response is completed, a completion notification is sent to the user via the terminal.

[0046] Automatic processing of requested work

[0047] When a user requests the creation of a new account, the device sends the request to the server, which analyzes the request and executes the appropriate program to automatically create the account. The result of this operation is notified to the user via the device, and the user confirms that the new account was successfully created.

[0048] Conducting an account inventory

[0049] The server periodically collects and analyzes the usage status of all accounts. It identifies unused and unnecessary accounts and generates a report of the inventory results. This report is displayed on the terminal, and the user can instruct the server to delete unnecessary accounts. The server deletes the unnecessary accounts based on the instructions and records the results in a log.

[0050] Automated Incident Response

[0051] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, but if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[0052] Template-based initial configuration

[0053] When a new system needs initial setup, the user selects a template and sends a request to the system. The server executes the initial setup procedure based on the template. Once the setup is complete, the terminal notifies the user of the progress and completion.

[0054] Maintenance schedule management

[0055] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, the schedule is notified to the person in charge via the terminal. When the maintenance work is completed, the server records the results in a log and notifies the user.

[0056] Performance data collection and analysis

[0057] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is issued and the user is notified via their terminal. The user can check the performance analysis results on a dashboard and make any necessary adjustments.

[0058] Automating release tasks

[0059] When a user registers a new release or change in the system, the server analyzes the procedure and schedules it. The release process is carried out automatically, and the user is notified via their terminal once it is complete.

[0060] Chatbot for inquiries

[0061] When a user makes a query, the device sends the query to the server, which uses an AI chatbot to generate an appropriate response and send it to the user. If necessary, the server also escalates the query.

[0062] Automated contract management

[0063] The server monitors contract data and manages expiration dates and renewal timing. When a contract is due for renewal, it sends an alert to the user via their device, urging them to take the necessary measures.

[0064] Streamlined budget management

[0065] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal risk of budget overrun is detected, the terminal notifies the user and provides necessary countermeasures.

[0066] As described above, the system of the present invention can automate and streamline a wide range of operational tasks, significantly improving the reliability and cost efficiency of system operation.

[0067] The processing flow will be explained below.

[0068] Executing scheduled routine tasks

[0069] Step 1:

[0070] The server reads the schedule information for regular tasks set by the system administrator.

[0071] Step 2:

[0072] The server will automatically launch the backup process at the specified time.

[0073] Step 3:

[0074] The server executes the backup operation and stores the created backup data.

[0075] Step 4:

[0076] The server generates and stores a log of the backup operation.

[0077] Step 5:

[0078] The terminal notifies the user that the backup is complete.

[0079] Step 6:

[0080] Users can view the status of their backups on the dashboard.

[0081] Notification and response to non-routine operations

[0082] Step 1:

[0083] A user requests a non-routine task, such as installing an emergency patch.

[0084] Step 2:

[0085] The terminal sends the request to the server.

[0086] Step 3:

[0087] The server analyzes the request and determines how to handle it.

[0088] Step 4:

[0089] The server prepares the necessary resources and executes the non-routine tasks.

[0090] Step 5:

[0091] The server generates and stores logs as work is completed.

[0092] Step 6:

[0093] The terminal notifies the user that the task is complete.

[0094] Step 7:

[0095] The user checks the results of the work and provides feedback if necessary.

[0096] Automatic processing of requested work

[0097] Step 1:

[0098] A user requests the system to create a new account.

[0099] Step 2:

[0100] The terminal sends a request to the server.

[0101] Step 3:

[0102] The server analyzes the request and executes the necessary program.

[0103] Step 4:

[0104] The server will automatically create a new account.

[0105] Step 5:

[0106] The server stores the results of the account creation and generates a notification.

[0107] Step 6:

[0108] The terminal notifies the user that the account creation is complete.

[0109] Step 7:

[0110] The user confirms that the new account was created successfully.

[0111] Conducting an account inventory

[0112] Step 1:

[0113] The server periodically collects all account information in the system.

[0114] Step 2:

[0115] The server analyzes the account usage history and identifies unnecessary accounts.

[0116] Step 3:

[0117] The server generates a report of the inventory results.

[0118] Step 4:

[0119] The terminal displays the inventory results to the user.

[0120] Step 5:

[0121] The user instructs the deletion of unnecessary accounts.

[0122] Step 6:

[0123] The server deletes unnecessary accounts according to the user's instructions.

[0124] Step 7:

[0125] The server generates and stores a log of the deletion activity.

[0126] Step 8:

[0127] The terminal notifies the user that the deletion process is complete.

[0128] Step 9:

[0129] The user confirms that the inventory work is complete.

[0130] Automated Incident Response

[0131] Step 1:

[0132] The server monitors the system status in real time.

[0133] Step 2:

[0134] The server issues an alert when it detects an anomaly.

[0135] Step 3:

[0136] The server initiates automated response procedures and analyzes the problem.

[0137] Step 4:

[0138] The server will initiate the repair process if an automatic repair is possible.

[0139] Step 5:

[0140] If the server is unable to repair the problem, it will escalate it to the appropriate person.

[0141] Step 6:

[0142] The terminal notifies the user of the occurrence of an incident and the status of the response.

[0143] Step 7:

[0144] The user may check the response status and issue additional instructions.

[0145] Step 8:

[0146] The server generates a log when an incident is resolved and records the response history.

[0147] Step 9:

[0148] The terminal notifies the user that the incident response has been completed.

[0149] Step 10:

[0150] The user checks the incident response results.

[0151] Template-based initial configuration

[0152] Step 1:

[0153] The user requests the initial setup of a new system.

[0154] Step 2:

[0155] The terminal sends a request to the server.

[0156] Step 3:

[0157] The server parses the initialization procedure based on the template.

[0158] Step 4:

[0159] The server prepares the necessary resources and begins the initialization.

[0160] Step 5:

[0161] Once the configuration process is complete, the server records and saves the results in a log.

[0162] Step 6:

[0163] The terminal notifies the user that the initial settings are complete.

[0164] Step 7:

[0165] The user checks whether the initial settings have been performed correctly.

[0166] Maintenance schedule management

[0167] Step 1:

[0168] The server manages the maintenance schedule for the system.

[0169] Step 2:

[0170] The server automatically assigns maintenance personnel according to a schedule.

[0171] Step 3:

[0172] The terminal notifies the relevant personnel of the maintenance schedule.

[0173] Step 4:

[0174] The user checks the notification content and makes a request to adjust the schedule as necessary.

[0175] Step 5:

[0176] The server generates and stores a log when maintenance work is completed.

[0177] Step 6:

[0178] The terminal notifies the user that the maintenance work has been completed.

[0179] Step 7:

[0180] The user checks the maintenance results and provides necessary feedback.

[0181] Performance data collection and analysis

[0182] Step 1:

[0183] The server collects system performance data in real time.

[0184] Step 2:

[0185] The server analyzes the collected data to identify performance trends.

[0186] Step 3:

[0187] If the server detects an abnormal value, it issues an alert.

[0188] Step 4:

[0189] The terminal visualizes performance data and analysis results (e.g., graphs).

[0190] Step 5:

[0191] The user instructs system adjustments based on the visualized data.

[0192] Step 6:

[0193] The server follows the user's instructions and performs the necessary adjustments.

[0194] Step 7:

[0195] The terminal notifies the user of the adjustment result.

[0196] Step 8:

[0197] The user checks whether the adjustment was made correctly.

[0198] Automating release tasks

[0199] Step 1:

[0200] Users register new releases and changes in the system.

[0201] Step 2:

[0202] The terminal transmits the registration details to the server.

[0203] Step 3:

[0204] The server analyzes the release procedure and sets a schedule.

[0205] Step 4:

[0206] The server will automatically start the release process at the set time.

[0207] Step 5:

[0208] The server logs and stores the results once the work is complete.

[0209] Step 6:

[0210] The terminal notifies the user of the completion of the release work.

[0211] Step 7:

[0212] The user may check the release results and perform additional verification work.

[0213] Chatbot for inquiries

[0214] Step 1:

[0215] A user registers a query with the system.

[0216] Step 2:

[0217] The terminal transmits the inquiry to the server.

[0218] Step 3:

[0219] The server uses an AI chatbot to analyze the query and generate an appropriate answer.

[0220] Step 4:

[0221] The terminal displays the chatbot's response to the user.

[0222] Step 5:

[0223] The user checks the response and makes another inquiry if the problem is not resolved.

[0224] Step 6:

[0225] The server will notify the responsible party if escalation is required.

[0226] Step 7:

[0227] The terminal notifies the user of the progress of the escalation.

[0228] Step 8:

[0229] The user confirms the escalation result.

[0230] Automated contract management

[0231] Step 1:

[0232] The server collects the contract data and inputs it into the management system.

[0233] Step 2:

[0234] The server monitors contract expiration and renewal timing and sets alerts.

[0235] Step 3:

[0236] The server will alert you when updates or purchases are required.

[0237] Step 4:

[0238] The terminal displays the contract status and alerts to the user.

[0239] Step 5:

[0240] The user checks the alerts and carries out the necessary renewal and purchase procedures.

[0241] Step 6:

[0242] The server records the details of the procedure and saves the updated contract information.

[0243] Step 7:

[0244] The terminal notifies the user that the contract renewal has been completed.

[0245] Step 8:

[0246] The user rechecks the contract information and makes corrections if necessary.

[0247] Streamlined budget management

[0248] Step 1:

[0249] The server collects cost data related to system operation.

[0250] Step 2:

[0251] The server analyzes the collected data and visualizes the budget usage status.

[0252] Step 3:

[0253] The server issues an alert if it detects an abnormal risk of exceeding the budget.

[0254] Step 4:

[0255] The terminal displays budget usage and alerts to the user.

[0256] Step 5:

[0257] The user checks the budget situation and indicates any necessary adjustments.

[0258] Step 6:

[0259] The server reallocates the budget based on the adjustment instructions.

[0260] Step 7:

[0261] The terminal notifies the user that the adjustment is complete.

[0262] Step 8:

[0263] The user checks whether the budget has been managed correctly.

[0264] The above is a detailed explanation of the program processing for each business operation, broken down into specific steps. By describing the processing in detail step by step like this, you can clearly understand how each process progresses.

[0265] Example 1

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

[0267] Modern information systems require a wide range of operations and numerous management tasks, making manual management and maintenance extremely complex and time-consuming. Furthermore, when an emergency response is required or when there are numerous user inquiries, the absence of an automated response system can easily lead to a decline in operational efficiency. Furthermore, with multiple important tasks such as system performance, account management, and backup work, there is a high risk of incorrect operation or delayed response. To address these issues, a solution that can automate system operations and efficiently manage them is needed.

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

[0269] In this invention, the server includes means for automatically executing scheduled routine tasks, means for notifying non-routine tasks and manually or automatically responding to them, means for accepting and executing user-requested tasks, means for conducting an account inventory and identifying unnecessary accounts, means for monitoring the system status and automatically responding when an incident occurs, means for initializing the system based on a template, means for managing maintenance schedules and coordinating maintenance personnel, means for collecting and analyzing system performance data in real time, means for automating the release of new software and changes, means for automatically responding to user inquiries, means for automatically managing and updating contracts, means for managing budget usage and detecting abnormal budget overrun risks, means for analyzing request content and executing appropriate response procedures, means for initiating a backup process and saving data, means for automatically creating new accounts, means for identifying and deleting unused accounts, means for performing initial configuration using a template, means for detecting abnormalities and issuing alerts, and means for escalating to a responsible person when automatic repair is not possible. This improves the reliability and efficiency of system operation, and by automating business processes, reduces human error and enables timely responses.

[0270] A "scheduled routine task" is a task that is automatically executed at a set time or timing on a daily, weekly, or monthly basis.

[0271] "Non-routine work" refers to work that arises suddenly or that requires an emergency response, and is not included in the regular schedule.

[0272] A "user-requested task" is a task that a system user requests the system to perform based on a specific request.

[0273] "Account inventory" means periodically checking the usage status of all accounts and identifying and managing unused or unnecessary accounts.

[0274] An "incident" refers to the occurrence of an abnormal condition or problem in a system, which may disrupt normal operation.

[0275] "Template-based system initialization" is the process of automatically configuring a new system according to a predefined configuration template.

[0276] "Maintenance work schedule management" refers to setting a schedule for planning and carrying out system maintenance work and managing its progress.

[0277] "Performance data" refers to various data relating to the operating status and performance of a system, and is collected in real time.

[0278] "Release automation" is the process of automating new software releases and configuration changes.

[0279] "Automatic response to inquiries" is a mechanism in which the system automatically provides answers to inquiries from users.

[0280] "Contract management and renewal" means that the system monitors contract information and automatically manages renewal dates and deadlines.

[0281] "Budget usage management" refers to the real-time monitoring of expenses related to system operation and the detection and management of abnormal budget consumption.

[0282] "Analysis of request content" refers to analyzing a request from a user and determining an appropriate response procedure based on the content of the request.

[0283] "Initiating a backup process" refers to the execution of a backup operation for the purpose of safely storing data.

[0284] "Automatic account creation" refers to the automatic generation of a new account based on a user request.

[0285] "Identifying unused accounts" refers to identifying and managing accounts that have not been used for a certain period of time.

[0286] "Anomaly detection" means monitoring the state of a system and discovering abnormalities or errors that are out of the ordinary.

[0287] "Issuing an alert" means sending a notification when an abnormality is detected and warning the user or administrator.

[0288] "Automatic remediation escalation" means handing over an issue to the appropriate personnel when automatic remediation is not possible.

[0289] The purpose of this invention is to automate and streamline a wide range of tasks in system operation. In this system, the roles of the server, terminal, and user are clearly divided, and specific programs and processing procedures are executed for each role.

[0290] Executing scheduled routine tasks

[0291] The server automatically executes regular tasks (e.g., daily backups) on a regular basis based on schedule information set by the system administrator. The hardware used is a general-purpose server, and the software used is backup software.

[0292] Specific examples

[0293] Hardware used: General server

[0294] Software used: Backup software

[0295] Example prompt:

[0296] "Perform daily backups on standard servers using backup software according to the backup schedule set by the server administrator."

[0297] Notification and response to non-routine operations

[0298] A user requests a non-routine task, such as installing an emergency patch, through a terminal. This request is sent to the server, which analyzes and executes the appropriate response.

[0299] Specific examples

[0300] Hardware used: General server

[0301] Software used: Patch management software

[0302] Example prompt:

[0303] "When a user requests the installation of an emergency patch, please apply the patch using patch management software on a standard server and notify the user when the installation is complete."

[0304] Automatic processing of requested work

[0305] A user requests the creation of a new account through a terminal, and based on this request, the server automatically creates the account using the appropriate account management tools.

[0306] Specific examples

[0307] Hardware used: General server

[0308] Software used: Account Management Tool

[0309] Example prompt:

[0310] When a new account creation request is received, please use an account management tool on a standard server to automatically create the account and notify the user.

[0311] Conducting an account inventory

[0312] The server periodically collects and analyzes the usage status of all accounts and identifies unused accounts. This information is displayed as a report on the device, and the user can instruct the deletion of unnecessary accounts.

[0313] Specific examples

[0314] Hardware used: General server

[0315] Software used: LDAP

[0316] Example prompt:

[0317] Use LDAP to periodically analyze account usage on your general servers, identify unused accounts, and generate reports.

[0318] Automated Incident Response

[0319] The server monitors the system status in real time and immediately takes action when an abnormality is detected. If automatic repair is not possible, the issue is escalated to the person in charge.

[0320] Specific examples

[0321] Hardware used: General server

[0322] Software used: Monitoring tools

[0323] Example prompt:

[0324] "Monitor the health of your systems in real time and, when anomalies are detected, auto-remediate or escalate as necessary."

[0325] Template-based initial configuration

[0326] The user selects a template and sends a request to the system, and the server performs the initial setup of the system based on the template.

[0327] Specific examples

[0328] Hardware used: General server

[0329] Software used: Configuration management tools

[0330] Example prompt:

[0331] "When a user selects a template and submits a request, please use a configuration management tool on the general server to automatically perform the initial setup and notify the progress and completion status."

[0332] Maintenance schedule management

[0333] The server manages the maintenance schedule and coordinates the maintenance personnel. When the maintenance work is completed, it records the results in a log and notifies the user.

[0334] Specific examples

[0335] Hardware used: General server

[0336] Software used: Schedule management software

[0337] Example prompt:

[0338] "Manage maintenance schedules and notify personnel and users before and after maintenance work."

[0339] Performance data collection and analysis

[0340] The server collects and analyzes system performance data in real time and issues an alert if it detects any abnormal values.

[0341] Specific examples

[0342] Hardware used: General server

[0343] Software used: Performance monitoring tool

[0344] Example prompt:

[0345] "Collect and analyze various system performance data in real time, and issue alerts if an abnormality is detected."

[0346] Automating release tasks

[0347] Users request new software or changes, and the server automatically performs the release process.

[0348] Specific examples

[0349] Hardware used: General server

[0350] Software used: Continuous integration tools

[0351] Example prompt:

[0352] When a new software release or change is registered, use a continuous integration tool to automatically execute the release and notify us when it is complete.

[0353] Chatbot for inquiries

[0354] When a user makes a query, the device sends the details to the server, and the AI ​​chatbot generates an appropriate answer.

[0355] Specific examples

[0356] Hardware used: General server

[0357] Software used: AI chatbot

[0358] Example prompt:

[0359] "Please process user inquiries via the server using an AI chatbot, generate appropriate answers, and send them."

[0360] Automated contract management

[0361] The server monitors contract data and issues an alert when the renewal date approaches, prompting the user to take action.

[0362] Specific examples

[0363] Hardware used: General server

[0364] Software used: Contract management tool

[0365] Example prompt:

[0366] "Monitor contract data and issue alerts to notify users when renewals are approaching."

[0367] Streamlined budget management

[0368] The server collects cost data related to system operation, and if it detects an abnormal risk of exceeding the budget, the terminal notifies the user.

[0369] Specific examples

[0370] Hardware used: General server

[0371] Software used: Budgeting tools

[0372] Example prompt:

[0373] "Manage system operation-related costs and notify users if an abnormal risk of overspending is detected."

[0374] As described above, the system of the present invention automates a wide range of operational tasks, improving overall operational efficiency and reliability, thereby facilitating system management and reducing operational costs.

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

[0376] Executing scheduled routine tasks

[0377] Step 1:

[0378] The server references the configured schedule information (e.g., the time of the daily backup). The schedule information is obtained from cron jobs or scheduling software. The input is the schedule data, and the output is the backup timing information.

[0379] Specific operation:

[0380] Analyzes the cron job configuration file.

[0381] Queries the schedule database to get the backup execution time.

[0382] Step 2:

[0383] The server starts the backup process based on the acquired schedule. The software used here is a backup tool. The input is backup timing information, and the output is an instruction to start the backup process.

[0384] Specific operation:

[0385] Run the batch script "backup_tool start" from the command line.

[0386] Step 3:

[0387] The server copies the data directory to the specified backup destination. The input is the data directory and the backup destination information, and the output is the backup file.

[0388] Specific operation:

[0389] Use filesystem calls to copy the specified directory to the backup destination (e.g., using rsync or scp).

[0390] Step 4:

[0391] When the server completes the backup, it sends a notification to the user via the terminal. The input is the backup completion information, and the output is a notification message.

[0392] Specific operation:

[0393] Send notification emails using a mail server.

[0394] Display a backup completion message on the dashboard.

[0395] Notification and response to non-routine operations

[0396] Step 1:

[0397] A user requests a non-routine task (e.g., installing an emergency patch) through a terminal. The input is the request information from the user, and the output is the request data.

[0398] Specific operation:

[0399] Receive requests via web forms or APIs.

[0400] Step 2:

[0401] The server analyzes the request content. The input is the request data and the output is the analysis result.

[0402] Specific operation:

[0403] Parse the request data and extract the necessary information.

[0404] Step 3:

[0405] The server downloads and installs the necessary patches based on the analysis results. The software used is a patch management tool. The input is the analysis results and patch information, and the output is the completion of the installation.

[0406] Specific operation:

[0407] Use the CLI to run the command "patch_tool apply -patch_id".

[0408] Step 4:

[0409] When the installation is complete, the server sends a notification to the user via the terminal. The input is the installation completion information, and the output is the notification message.

[0410] Specific operation:

[0411] Send reports via email and system notifications.

[0412] Automatic processing of requested work

[0413] Step 1:

[0414] A user requests the creation of a new account through a terminal. The input is the request information from the user, and the output is the request data.

[0415] Specific operation:

[0416] Use the Web API to receive requests.

[0417] Step 2:

[0418] The server analyzes the request content. The input is the request data and the output is the analysis result.

[0419] Specific operation:

[0420] Parse the JSON format and obtain the required fields.

[0421] Step 3:

[0422] The server uses the account management tool to create a new account. The input is the parsed result, and the output is the new account information.

[0423] Specific operation:

[0424] Run the PowerShell script and use the command "New-ADUser".

[0425] Step 4:

[0426] When the account creation is completed, the server sends a notification to the user via the terminal. The input is the account creation completion information, and the output is a notification message.

[0427] Specific operation:

[0428] Notifications will be sent via email and dashboard.

[0429] Conducting an account inventory

[0430] Step 1:

[0431] The server uses LDAP to collect all account usage information: the input is an LDAP query and the output is account usage information.

[0432] Specific operation:

[0433] Run an LDAP query to get the last login time for each account.

[0434] Step 2:

[0435] The server analyzes the acquired data and identifies unused accounts. The input is account usage information, and the output is a list of unused accounts.

[0436] Specific operation:

[0437] Query the database to extract accounts that have not logged in for a specified period of time.

[0438] Step 3:

[0439] The server generates a report on unused accounts and displays it on a terminal. The input is a list of unused accounts, and the output is the report data.

[0440] Specific operation:

[0441] Use the report generator to create reports in PDF and spreadsheet formats.

[0442] Step 4:

[0443] The user instructs the deletion of unnecessary accounts based on the report, and the server executes the deletion and records the result in a log. The input is the user's instruction, and the output is the deletion completion information.

[0444] Specific operation:

[0445] Run the PowerShell script to delete the target account.

[0446] Automated Incident Response

[0447] Step 1:

[0448] The server monitors the system status in real time. The input is real-time system data, and the output is anomaly detection information.

[0449] Specific operation:

[0450] Use monitoring tools to analyze system logs.

[0451] Step 2:

[0452] When the server detects an anomaly, it immediately starts to take action. The input is the anomaly detection information, and the output is the response result information.

[0453] Specific operation:

[0454] Run the automatic repair script.

[0455] Step 3:

[0456] If automatic repair is not possible, the server escalates the issue to the person in charge. The input is the response result information, and the output is an escalation notification.

[0457] Specific operation:

[0458] Use a mail server to send escalation notifications.

[0459] Step 4:

[0460] When the incident response is completed, the server sends a notification to the user via the terminal. The input is the response completion information, and the output is a notification message.

[0461] Specific operation:

[0462] The results will be notified to the user via email or system notification.

[0463] (Application example 1)

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

[0465] There is a need to efficiently manage and automate the numerous tasks and incident responses required in factory operations, improving operational reliability and cost efficiency. Traditionally, a wide range of management tasks, such as monitoring the status of factory equipment and robots, responding when anomalies occur, and executing routine tasks, have often been performed manually, resulting in potential work delays and human error. Furthermore, insufficient notification of task progress and completion can lead to insufficient information sharing among staff, resulting in a decline in work efficiency. A system that can solve these issues is needed.

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

[0467] In this invention, the server includes a means for monitoring the status of equipment in the factory in real time and automatically responding when an abnormality is detected, a means for automatically executing routine tasks, and a means for notifying users of progress and completion, thereby making it possible to improve the efficiency and reliability of operations in factory management.

[0468] "Regular tasks" are tasks that are performed periodically at specific times or cycles.

[0469] "Non-routine work" refers to work carried out to respond to emergencies or unexpected situations.

[0470] A "requested task" is a task that is performed based on a specific request from a user.

[0471] "Account inventory" is the process of checking the usage status of registered accounts and identifying and deleting unnecessary accounts.

[0472] An "incident" is an abnormality or failure that occurs during the operation of a system or equipment.

[0473] A "template" is a set of predefined procedures used to efficiently perform a particular task or setting.

[0474] "Maintenance work" refers to the maintenance work carried out to maintain the normal operation of systems and equipment.

[0475] "Performance data" refers to data that indicates the operational status of a system or device, and includes, for example, availability rate and response time.

[0476] "Release work" refers to the work of introducing new software or updating existing software.

[0477] "Inquiry response" refers to the task of providing a response to a question or request from a user.

[0478] "Contract management" refers to the task of managing contract contents and deadlines, and carrying out renewal procedures and confirmations.

[0479] "Budget usage status" is data that indicates the status of expenses related to system operation.

[0480] "Real-time monitoring" means constantly monitoring the status of systems and equipment and instantly detecting abnormalities.

[0481] "Escalation" is a procedure for notifying the person in charge or a higher-level manager when a problem occurs and urging them to take action.

[0482] This invention is a system aimed at automating and streamlining factory operations. This system is comprised of multiple pieces of hardware and software, centered around a server, and is accessible to users via smartphones or head-mounted displays (HMDs).

[0483] The server automatically executes scheduled routine tasks and performs regular backups and system updates, preventing human error and improving operational reliability.

[0484] The system also monitors incidents in real time, responds immediately if an abnormality is detected, and automatically escalates the incident and notifies the responsible person if it is difficult to handle.

[0485] Furthermore, the server analyzes user requests and automatically initiates tasks such as creating a new account or starting a specific work process, thereby improving response speed and user convenience.

[0486] Template-based system initial setup is also possible, allowing for efficient configuration of various settings required when introducing new equipment or systems. Templates contain predefined procedures, allowing for quick and reliable initial setup.

[0487] It also manages the schedule for maintenance work and notifies maintenance personnel as necessary. When the maintenance work is completed, the results are recorded in a log and the user is notified.

[0488] The system collects and analyzes performance data in real time, and if abnormal behavior is detected, it immediately issues an alert to notify the user, who can then view this data on a dashboard and make any necessary adjustments.

[0489] The application also automates release processes, making it easy to deploy new software or update existing systems. Users can monitor the progress of releases and receive notifications when they are complete.

[0490] The system uses a chatbot that uses a generative AI model to respond to inquiries, providing quick and accurate answers to user questions and escalating cases as needed.

[0491] Contract management and renewals are also automated, with users notified when deadlines approach and prompted to take necessary measures.

[0492] In addition, it also manages budget usage and notifies users if an abnormal risk of budget overrun is detected, and provides countermeasures.

[0493] As a concrete example, the following prompt sentence is used:

[0494] Template name: "New Robot Installation Settings"

[0495] 1. Enter the basic information about your robot.

[0496] 2. Select a work area.

[0497] 3. Configure the sensor settings.

[0498] 4. Conduct a test drive.

[0499] The server displays prompts via the smartphone or HMD interface, and the entire process can be carried out smoothly by the user following the procedure. This system therefore contributes greatly to improving the efficiency and reliability of factory operations.

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

[0501] Step 1:

[0502] Scheduling and executing routine tasks

[0503] The server schedules regular tasks based on the scheduling information. When the scheduled time arrives, the target task is automatically executed. Specifically, if a daily backup is required, the server automatically starts the backup process and backs up the specified data. The input is the schedule information for the regular tasks, and the output is the status indicating that the backup has been completed.

[0504] Step 2:

[0505] Real-time incident monitoring and response

[0506] The server monitors various sensors and system logs, and if an abnormality is detected, it initiates a real-time response. For example, if an abnormality in equipment performance is detected, an automatic repair process is initiated. Once the repair is complete, a notification is sent to the user. The input is data from sensors and logs, and the output is the incident response status.

[0507] Step 3:

[0508] Acceptance and execution of user-requested work

[0509] When a user requests a new task, the task request is sent to the server via the terminal. The server analyzes the request and takes appropriate action. For example, if a request is made to create a new account, the server automatically creates the account based on the required data. The input is the task request from the user, and the output is a notification that the task has been completed.

[0510] Step 4:

[0511] Template-based system initialization

[0512] The user selects a template through the terminal and requests initial setup from the system. The server automatically performs various setup procedures based on the template. For example, the setup procedure when a new robot is introduced is performed using this template. The input is the template selection and initial setup request, and the output is a notification that the setup is complete.

[0513] Step 5:

[0514] Maintenance work schedule management

[0515] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, a notification is sent to the person in charge via the terminal. When the maintenance work is completed, the results are recorded in a log and the user is notified. The input is the maintenance schedule information, and the output is a notification that the maintenance has been completed.

[0516] Step 6:

[0517] Performance data collection and analysis

[0518] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is immediately issued and the user is notified. The input is performance data, and the output is an anomaly detection alert.

[0519] Step 7:

[0520] Automating release tasks

[0521] When a user registers a new release in the system, the server analyzes the procedure and schedules it. The release process is automatically performed and a notification is sent to the user upon completion. The input is the release procedure information, and the output is a notification of release completion.

[0522] Step 8:

[0523] Inquiry response

[0524] A user's inquiry is sent to the server via the terminal. The server uses an AI chatbot to generate an appropriate response and sends it to the user. It also escalates the case as needed. The input is the user's inquiry, and the output is the response to the inquiry.

[0525] Step 9:

[0526] Automated contract management

[0527] The server monitors the contract data and notifies the user when the renewal date is approaching. Necessary renewal procedures can also be carried out automatically. The input is the contract data, and the output is a notification when renewal occurs and a notification when renewal is complete.

[0528] Step 10:

[0529] Managing budget usage

[0530] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal budget over-risk is detected, it notifies the user and provides countermeasures. The input is cost data, and the output is an alert of the budget over-risk.

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

[0532] The system of the present invention combines the automation functions of conventional operational tasks with an emotion engine that recognizes user emotions and optimizes responses. This system operates as follows, and performs various operational tasks efficiently and user-friendly.

[0533] Executing scheduled routine tasks

[0534] The server reads the schedule information for regular operations set by the system administrator. It automatically starts the backup process at the specified time and starts backing up data. When the operation is complete, a backup completion notification is sent to the user via the terminal. The user can check the backup status on the dashboard.

[0535] Notification and response to non-routine operations

[0536] A user requests a non-routine task, such as installing an emergency patch, from the system. The request is sent to the server via a terminal. Upon receiving the request, the server analyzes and executes the appropriate response procedure. Once the task is completed, a completion notification is sent to the user via the terminal.

[0537] Automatic processing of requested work

[0538] When a user requests the creation of a new account, the device sends the request to the server, which analyzes the request and executes the appropriate program to automatically create the account. The result of this operation is notified to the user via the device, and the user confirms that the new account was successfully created.

[0539] Conducting an account inventory

[0540] The server periodically collects and analyzes the usage status of all accounts. It identifies unused and unnecessary accounts and generates a report of the inventory results. This report is displayed on the terminal, and the user can instruct the server to delete unnecessary accounts. The server deletes the unnecessary accounts based on the instructions and records the results in a log.

[0541] Automated Incident Response

[0542] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, and if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[0543] Template-based initial configuration

[0544] When a new system needs initial setup, the user selects a template and sends a request to the system. The server executes the initial setup procedure based on the template. Once the setup is complete, the terminal notifies the user of the progress and completion.

[0545] Maintenance schedule management

[0546] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, the schedule is notified to the person in charge via the terminal. When the maintenance work is completed, the server records the results in a log and notifies the user.

[0547] Performance data collection and analysis

[0548] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is issued and the user is notified via their terminal. The user can check the performance analysis results on a dashboard and make any necessary adjustments.

[0549] Automating release tasks

[0550] When a user registers a new release or change in the system, the server analyzes the procedure and schedules it. The release process is carried out automatically, and the user is notified via their terminal once it is complete.

[0551] Chatbot for inquiries

[0552] When a user makes a query, the device sends the query to the server, which uses an AI chatbot to generate an appropriate response and send it to the user. If necessary, the server also escalates the query.

[0553] Automated contract management

[0554] The server monitors contract data and manages expiration dates and renewal timing. When a contract is due for renewal, it sends an alert to the user via their device, urging them to take the necessary measures.

[0555] Streamlined budget management

[0556] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal risk of budget overrun is detected, the terminal notifies the user and provides necessary countermeasures.

[0557] Introducing an emotion engine that recognizes user emotions

[0558] The system incorporates an emotion engine that recognizes the user's emotions and optimizes the response.

[0559] Example 1: Using an emotion engine in response to inquiries

[0560] When a user makes a query, the server uses an emotion engine to identify the user's emotional state based on context and linguistic analysis. For example, if the user expresses strong dissatisfaction, the emotion engine will recognize the situation and the server will be configured to escalate the query to a human agent more quickly. The tone and content of the response will also be adjusted according to the user's emotion.

[0561] Example 2: Using emotion engines in incident response

[0562] When an incident occurs, the server uses an emotion engine to analyze the user's actions and comments when checking the response status within the system, and if the user feels strong stress or anxiety, it quickly escalates the situation and provides further support.The emotion engine also has a function to send follow-up notifications after the incident is resolved based on the user's emotional data.

[0563] Example 3: Using the emotion engine in routine and non-routine notifications

[0564] In notifications sent upon the completion of routine or non-routine tasks, an emotion engine can be used to analyze the user's emotional state, and, for example, a message of encouragement can be sent to a user who is feeling tired, or a message of gratitude to a user who is feeling satisfied.

[0565] In this way, by recognizing the user's emotions and adjusting the response appropriately, it is possible to increase the satisfaction of system users and provide a better user experience.

[0566] The processing flow will be explained below.

[0567] Use of emotion engines in inquiries

[0568] Step 1:

[0569] A user enters a query into the system.

[0570] Step 2:

[0571] The terminal sends the inquiry to the server.

[0572] Step 3:

[0573] The server analyzes the query received by the emotion engine and identifies the user's emotional state (e.g., dissatisfaction, satisfaction, stress).

[0574] Step 4:

[0575] The server generates optimized responses and responses based on the results of the emotion engine.

[0576] Step 5:

[0577] If the user expresses strong dissatisfaction, the server automatically escalates the response process and notifies a human agent.

[0578] Step 6:

[0579] The terminal displays the answer to the user.

[0580] Step 7:

[0581] The user checks the response and makes another inquiry if necessary.

[0582] Using Emotion Engines in Incident Response

[0583] Step 1:

[0584] The server monitors the system status in real time and issues an alert if an abnormality is detected.

[0585] Step 2:

[0586] A user accesses the system to check the status of an incident and tries to understand the situation.

[0587] Step 3:

[0588] The server uses an emotion engine to analyze the user's actions and comments within the system.

[0589] Step 4:

[0590] The server identifies the user's emotional state (e.g., stress, anxiety) and optimizes response procedures.

[0591] Step 5:

[0592] If the user shows signs of high stress, the server automatically initiates an escalation procedure and notifies personnel.

[0593] Step 6:

[0594] After the incident is resolved, the server sends follow-up notifications taking into account the user's emotional state.

[0595] Step 7:

[0596] The device displays the notification content to the user.

[0597] Using emotion engines to inform routine and non-routine tasks

[0598] Step 1:

[0599] The server executes routine and non-routine tasks and logs the completion status.

[0600] Step 2:

[0601] The server prepares the notification content and uses an emotion engine to analyze the user's past reactions and current situation.

[0602] Step 3:

[0603] The server optimizes the notification content based on the user's emotional state (e.g., an encouraging message for a user who is feeling tired, a thank you message for a user who is feeling satisfied).

[0604] Step 4:

[0605] The terminal sends the notification content to the user.

[0606] Step 5:

[0607] The user receives a notification and checks the status.

[0608] These are the detailed steps of each process that incorporates the emotion engine, which enables the system to take the user's emotional state into consideration and provide the most appropriate response.

[0609] Example 2

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

[0611] Conventional systems individually performed tasks such as automating routine tasks, notifying and responding to non-routine tasks, account management, incident response, initial system setup, maintenance schedule management, performance data collection and analysis, release work, inquiry response, contract management, and budget management, but because they did not take user emotions into consideration, there were limitations to improving the user experience.In addition, they did not generate prompts using an emotion engine or generative AI model, making it difficult to provide flexible and individual responses.

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

[0613] In this invention, the server includes means for automatically executing scheduled routine tasks, means for notifying non-routine tasks and responding to them manually or automatically, means for accepting and executing tasks requested by users, means for conducting account inventory and identifying unnecessary accounts, means for monitoring system status and automatically responding when an incident occurs, means for initializing the system based on templates, means for managing maintenance schedules and coordinating maintenance personnel, means for collecting and analyzing system performance data in real time, means for automating the release of new software and changes, means for automatically responding to user inquiries, means for automatically managing and renewing contracts, means for managing budget usage and detecting abnormal budget overrun risks, means for recognizing user emotions and optimizing responses, means for analyzing inquiry content and supporting incident response using an emotion engine, and means for generating prompt sentences according to the user's emotional state using a generative AI model. This enables flexible and optimal system responses that take user emotions into account.

[0614] A "scheduled routine task" is a task that is automatically executed periodically according to a schedule set in advance by a system administrator.

[0615] "Non-routine tasks" are tasks that occur infrequently and are difficult to predict, such as installing emergency patches.

[0616] A "user-requested task" is a task in which a user requests a specific action from the system.

[0617] "Account inventory" is the process of periodically examining all accounts registered in the system and identifying and managing unused and unnecessary accounts.

[0618] An "incident" refers to the occurrence of an unexpected problem, such as a system abnormality or failure.

[0619] "Initial system configuration based on a template" refers to the procedure for initializing a new system or application using a pre-prepared configuration format.

[0620] "Managing maintenance work schedules" refers to planning and coordinating system maintenance work and carrying it out at the appropriate time.

[0621] "System performance data" refers to information about the operating status of the system, such as CPU usage, memory usage, and disk I / O.

[0622] "Release operations" is the process for applying new software or system changes to a production environment.

[0623] An "inquiry" refers to a question or request made by a user to the system for information or problem resolution.

[0624] "Contract management" refers to managing the content and expiration dates of contracts related to system operation, and handling matters such as renewals and cancellations.

[0625] "Budget utilization" refers to the management of costs associated with operating the system and the monitoring of planned budgets and actual expenditures.

[0626] An "emotion engine" is a system for analyzing and identifying a user's emotional state from their text and behavior.

[0627] A "generative AI model" is an artificial intelligence system that uses natural language processing and machine learning to generate appropriate prompts and responses based on the user's emotions and requests.

[0628] The system of the present invention is designed to automate a wide range of operational tasks, recognize user emotions, and optimize responses. Next, a specific method for running the program of this system will be described.

[0629] Executing scheduled routine tasks

[0630] The server reads the schedule information for regular tasks set by the system administrator. This information is obtained from a database (e.g., MySQL (registered trademark)). When the specified time arrives, the server automatically starts the backup process. Using backup software (e.g., Acronis Backup), the data is saved to the server's storage (e.g., NAS). When the backup is complete, the server sends a completion notification to the user via their device (e.g., Windows PC or MacBook), and the user can check the backup status on the management screen (e.g., web application).

[0631] Notification and response to non-routine operations

[0632] A user requests a non-routine task, such as installing an emergency patch, from the system. This request is sent from the terminal to the server, and communication is carried out using an HTTP request. The server receives the request, analyzes the appropriate response procedure, and executes a script. For example, an automation tool such as Ansible is used to install an emergency patch. After the task is completed, the server sends a completion notification to the user via the terminal.

[0633] Automatic processing of requested work

[0634] When a user requests the creation of a new account, the device sends the request to the server. This communication uses the HTTPS protocol, and the request data is sent in JSON format. The server receives the request and automatically creates a new account using LDAP or Active Directory. A completion notification is sent to the user via the device, and the user can view the details of the new account by email or on the system dashboard.

[0635] Conducting an account inventory

[0636] The server periodically collects usage information for all accounts from LDAP or Active Directory and analyzes it using Python scripts and data analysis libraries (e.g., Pandas, Matplotlib). It identifies unnecessary accounts and generates a report. This report is displayed on the terminal, and the user can instruct the deletion of unnecessary accounts. The server deletes the accounts based on the instructions and records the operation log in a database (e.g., MySQL).

[0637] Automated Incident Response

[0638] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, and if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[0639] Introducing an emotion engine that recognizes user emotions

[0640] This system incorporates an emotion engine that recognizes user emotions and optimizes responses. For example, it analyzes the content of inquiries and the user's actions and comments during incident response, and uses an emotion engine (e.g., IBM Watson (registered trademark) NLU) to identify the user's emotional state.

[0641] Example: Using an emotion engine in customer inquiries

[0642] When a user makes an inquiry, the server uses an emotion engine to identify the user's emotional state. If the inquiry is "I'm having trouble using the service!", the emotion engine will emphasize the "trouble" part and quickly escalate the situation. The generative AI model uses this information to generate a prompt.

[0643] Example prompt sentence:

[0644] "If a user is having trouble using the service, escalate it quickly."

[0645] In this way, the system can provide flexible and optimal responses that take into account the user's emotions, improving the user experience.

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

[0647] Executing scheduled routine tasks

[0648] Step 1:

[0649] The server reads the schedule information for regular tasks set by the system administrator from a database (e.g., MySQL).

[0650] Input: Schedule information from the database

[0651] Output: Loaded schedule information

[0652] Specific operation: The server executes an SQL query to retrieve schedule information using a SELECT statement.

[0653] Step 2:

[0654] When the specified time arrives, the server will automatically launch the backup process.

[0655] Input: Specified time according to schedule information

[0656] Output: Backup process starts

[0657] What it does: Run Acronis Backup software using a cron job or task scheduler.

[0658] Step 3:

[0659] When the backup is complete, the server sends a completion notification to the terminal.

[0660] Input: Backup completion status

[0661] Output: Completion notification message

[0662] Specific operation: The server sends a notification email via the mail server, or sends a notification to the device using the web application API.

[0663] Notification and response to non-routine operations

[0664] Step 1:

[0665] A user requests a non-routine task, such as installing an emergency patch, from the system.

[0666] Input: Non-routine work request from user

[0667] Output: The request is sent from the terminal to the server.

[0668] Specific operation: The user enters a request through a web form or API, and the device sends this request in JSON format to the server.

[0669] Step 2:

[0670] The server receives the request, analyzes it, and determines the appropriate course of action.

[0671] Input: Non-routine work request data

[0672] Output: Action steps

[0673] What happens: The server runs a Python script, analyzes the request, and decides which tool (e.g., Ansible) to use.

[0674] Step 3:

[0675] The server performs non-routine tasks according to the determined response procedures.

[0676] Input: Response procedure

[0677] Output: Results of non-routine tasks

[0678] What it does: Runs an Ansible playbook to apply an emergency patch.

[0679] Step 4:

[0680] When the work is completed, the server sends a completion notification to the user via the terminal.

[0681] Input: Non-routine task execution completion status

[0682] Output: Completion notification

[0683] Specific operation: The server sends a notification to the user via the mail server or web application API.

[0684] Automatic processing of requested work

[0685] Step 1:

[0686] When a user requests the creation of a new account, the device sends the request to the server.

[0687] Input: Account creation request

[0688] Output: The request is sent to the server

[0689] How it works: The user enters a request through a web form or API, and the device sends it to the server using the HTTPS protocol.

[0690] Step 2:

[0691] The server receives the request, analyzes it, and creates a new account.

[0692] Input: Account creation request data

[0693] Output: Account creation status

[0694] What it does: The server runs a Python script to automatically create new accounts using LDAP or Active Directory.

[0695] Step 3:

[0696] Once the account creation is complete, the server notifies the user of the results via the terminal.

[0697] Input: Account creation completion status

[0698] Output: Completion notification

[0699] Specific operation: The server sends a notification to the user via the mail server or web application API.

[0700] Conducting an account inventory

[0701] Step 1:

[0702] The server periodically collects all account usage information from LDAP or Active Directory.

[0703] Input: Account data

[0704] Output: Collected usage data

[0705] What it does: The server runs a Python script that queries and collects account usage information from LDAP and Active Directory.

[0706] Step 2:

[0707] The server analyzes the collected data and identifies unnecessary accounts.

[0708] Input: Usage data

[0709] Output: List of unnecessary accounts

[0710] What it does: Use Python scripts and data analysis libraries (e.g., Pandas) to analyze account usage frequency and last login time.

[0711] Step 3:

[0712] The server generates a report of unnecessary accounts and displays it on the terminal.

[0713] Input: List of unnecessary accounts

[0714] Output: Report

[0715] Specific operation: Use Pandas and Matplotlib to generate analysis results in report format (e.g. PDF or HTML).

[0716] Step 4:

[0717] The user instructs the deletion of unnecessary accounts.

[0718] Input: User deletion instructions

[0719] Output: Delete instruction data

[0720] Specific operation: The user enters deletion instructions via a web form or API, and the device sends them to the server.

[0721] Step 5:

[0722] The server deletes the account based on the user's instructions and records the operation log.

[0723] Input: Data for deletion instructions

[0724] Output: Deletion completion status, operation log

[0725] Specific operation: The server deletes the account using a Python script and records the operation log in the MySQL database using an INSERT statement.

[0726] (Application example 2)

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

[0728] Conventional operational automation systems were unable to recognize the user's emotional state and respond accordingly, making it difficult to improve the user experience. Furthermore, content distribution services were unable to recommend appropriate content based on the user's emotions, resulting in a decline in user satisfaction. Technology to address this issue is needed.

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

[0730] In this invention, the server includes: means for automatically executing scheduled routine tasks; means for notifying non-routine tasks and manually or automatically responding to them; means for accepting and executing tasks requested by users; means for taking account inventories and identifying unnecessary accounts; means for monitoring the system status and automatically responding when an incident occurs; means for initializing the system based on templates; means for managing maintenance schedules and coordinating maintenance personnel; means for collecting and analyzing system performance data in real time; means for automating the release of new software and changes; means for automatically responding to inquiries from users; means for automatically managing and renewing contracts; means for managing budget usage and detecting abnormal budget overrun risks; and means for analyzing user emotions using an emotion engine that recognizes user emotions and optimizes responses, and recommending content corresponding to the user's emotional state. This makes it possible to improve the user experience by recognizing user emotions and providing optimal responses.

[0731] A "scheduled routine task" is a task that is planned in advance and executed periodically based on a preset schedule.

[0732] "Non-routine work" refers to temporary work that is not performed regularly according to a specific schedule, but occurs as needed.

[0733] A "requested work" is a specific job or task that is performed based on a request from a user.

[0734] "Account inventory" is the process of checking the usage status of all accounts and identifying unnecessary accounts.

[0735] "Monitoring the system status" means monitoring the operating status and performance of the entire system in real time.

[0736] An "incident" is an event in which a problem such as an abnormality or failure occurs in a system.

[0737] "Performing initial system settings based on a template" means automatically performing initial system settings on a new system according to a predetermined setting pattern.

[0738] "Managing maintenance work schedules" means planning and coordinating maintenance work such as system maintenance and updates, and managing the schedule.

[0739] "Collecting system performance data and analyzing it in real time" means collecting data on the system's operating status and performance and analyzing it immediately.

[0740] "Automating the release of new software and changes" means automating the introduction of new software and the modification of existing software.

[0741] "Automatically responding to inquiries from users" means that the system automatically provides appropriate answers to questions or requests submitted by users.

[0742] "Automatically managing and updating contracts" means that the system automatically checks and updates the contract contents.

[0743] "Manage budget usage and detect abnormal budget overspending risks" means monitoring how the budget is used and detecting the risk of excessive budget usage.

[0744] The "emotion engine" is an engine that analyzes the user's emotions in real time and responds optimally according to their emotional state.

[0745] "User's emotional state" refers to the type and intensity of emotion that a user is feeling at a particular point in time.

[0746] "Recommending content" means presenting optimal content that matches the user's interests and emotional state.

[0747] MODE FOR CARRYING OUT THE INVENTION

[0748] The present invention provides a system for recognizing a user's emotions and taking an optimal response accordingly. Specific embodiments will be described below.

[0749] The server manages scheduled routine tasks, automatically executing them at designated times, such as backup processes and routine maintenance tasks. The server also accepts requests for non-routine tasks and responds appropriately, such as installing emergency patches or allocating additional resources.

[0750] A user's request is sent to the server via the device, which then analyzes the request and automatically executes the corresponding procedure, such as creating a new account or updating an existing account.

[0751] The server periodically monitors account usage and identifies unnecessary accounts. This information is generated as a report and notified to the user. The user can then instruct the server to delete unnecessary accounts.

[0752] Additionally, the server monitors the system status in real time and automatically initiates a remediation process if an incident occurs, or escalates to a responsible party if it is not possible. The server also includes a means to initially configure new systems based on templates.

[0753] The server manages the maintenance schedule and notifies the maintenance personnel of the schedule. Performance data is collected and analyzed in real time, and an alert is issued if an abnormal value is detected.

[0754] When a user requests a new software release or change, the server analyzes the procedure and performs the release in an automated manner, and also automatically responds to user inquiries using an AI chatbot.

[0755] The server also automatically manages contracts and budgets. It monitors contract expirations and renewals and sends alerts to users. Budget usage is also monitored in real time, and if an abnormal risk of budget overruns is detected, a notification is sent.

[0756] Of particular note is the introduction of an emotion engine. The server uses the emotion engine to analyze the user's emotional state in real time. For example, when a user is watching content or posting a review, the server identifies the user's emotion based on context and linguistic analysis. Based on this emotional state, the server recommends the most appropriate content and notifies the user.

[0757] Hardware / Software Used

[0758] This system mainly uses the following hardware and software:

[0759] Hardware: Smartphone (ANDROID (registered trademark) / iOS), server

[0760] Software: Python, EmotionRecognition library, Requests library, RESTful API

[0761] Specific examples

[0762] Example 1: If a user types, "I've been very busy today, I want to relax," the emotion engine will recognize "stress" and recommend relaxing content (e.g., videos of nature scenes).

[0763] Prompt Sentence Examples

[0764] 1. Example prompt:

[0765] User input text: "Today has been very busy, I want to relax."

[0766] Process: Request emotion analysis from the emotion engine to detect "stress." Retrieve "relaxing videos" from the recommended content API and notify the user.

[0767] In this way, the present invention significantly improves the user experience by recognizing the user's emotions and automatically providing optimal content corresponding to those emotions.

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

[0769] Processing Steps

[0770] Step 1: Receiving User Input

[0771] The user enters a sentence about their feelings into a text field in the system, such as "I'm really tired today. I don't feel like doing anything." This input is collected by the device and sent to the next step.

[0772] Step 2: Sentiment Analysis

[0773] The server sends the user's text received from the device to the emotion engine. The emotion engine uses natural language processing technology to analyze the text and identify the user's emotion. The data processing performed at this time involves tokenizing the text and assigning emotion labels, resulting in emotion labels such as "stress" and "satisfaction."

[0774] Step 3: Sending emotion labels

[0775] The server retrieves the emotion labels obtained from the emotion engine and sends them to the content recommendation system. This data is sent via a RESTful API.

[0776] Step 4: Content Recommendation

[0777] The content recommendation system provides the server with the optimal content according to the emotion label. The system uses past user data and a matching algorithm to select the content that best suits the user's emotion. The data calculation involves searching for the appropriate content ID from the database using the emotion label as a key. The output is information about the recommended content.

[0778] Step 5: Notification of recommended content

[0779] The server transmits the recommended content information obtained from the content recommendation system to the terminal. The terminal receives this information and notifies the user. Specifically, it displays a notification screen and presents the recommended content to the user along with a message such as "Here is the recommended content."

[0780] Adding specific examples

[0781] For example, if a user types "I'm having a great time today," the processing steps would be:

[0782] Step 1: The device receives user input such as "I'm having a great time today."

[0783] Step 2: The server sends this sentence to the emotion engine and gets the emotion label "joy."

[0784] Step 3: The server sends the emotion label of “joy” to the content recommendation system.

[0785] Step 4: The content recommendation system recommends entertaining content suitable for "pleasure" (e.g., comedy movies).

[0786] Step 5: The server sends this content information to the terminal, which then notifies the user.

[0787] Through the above steps, the present invention can provide a content recommendation function that is adapted to the user's emotions, thereby improving the user experience.

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

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

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

[0791] [Second embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

[0804] The system of the present invention automates and streamlines a wide range of tasks in system operation, and includes various programs for this purpose. Below, we will explain in natural language how the programs in this system work, using concrete examples.

[0805] Executing scheduled routine tasks

[0806] The server automatically performs routine tasks (e.g., daily backups) based on scheduling information set by the system administrator. At the set time, the server launches the backup process and begins backing up data. When the task is complete, a notification is sent to the user via the terminal, and the backup status can be checked on the dashboard.

[0807] Notification and response to non-routine operations

[0808] Users can request non-routine tasks (e.g., installing emergency patches) from the system. The request is sent to the server via the terminal. When the server receives the request, it analyzes and executes the appropriate response procedure. Once the response is completed, a completion notification is sent to the user via the terminal.

[0809] Automatic processing of requested work

[0810] When a user requests the creation of a new account, the device sends the request to the server, which analyzes the request and executes the appropriate program to automatically create the account. The result of this operation is notified to the user via the device, and the user confirms that the new account was successfully created.

[0811] Conducting an account inventory

[0812] The server periodically collects and analyzes the usage status of all accounts. It identifies unused and unnecessary accounts and generates a report of the inventory results. This report is displayed on the terminal, and the user can instruct the server to delete unnecessary accounts. The server deletes the unnecessary accounts based on the instructions and records the results in a log.

[0813] Automated Incident Response

[0814] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, but if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[0815] Template-based initial configuration

[0816] When a new system needs initial setup, the user selects a template and sends a request to the system. The server executes the initial setup procedure based on the template. Once the setup is complete, the terminal notifies the user of the progress and completion.

[0817] Maintenance schedule management

[0818] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, the schedule is notified to the person in charge via the terminal. When the maintenance work is completed, the server records the results in a log and notifies the user.

[0819] Performance data collection and analysis

[0820] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is issued and the user is notified via their terminal. The user can check the performance analysis results on a dashboard and make any necessary adjustments.

[0821] Automating release tasks

[0822] When a user registers a new release or change in the system, the server analyzes the procedure and schedules it. The release process is carried out automatically, and the user is notified via their terminal once it is complete.

[0823] Chatbot for inquiries

[0824] When a user makes a query, the device sends the query to the server, which uses an AI chatbot to generate an appropriate response and send it to the user. If necessary, the server also escalates the query.

[0825] Automated contract management

[0826] The server monitors contract data and manages expiration dates and renewal timing. When a contract is due for renewal, it sends an alert to the user via their device, urging them to take the necessary measures.

[0827] Streamlined budget management

[0828] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal risk of budget overrun is detected, the terminal notifies the user and provides necessary countermeasures.

[0829] As described above, the system of the present invention can automate and streamline a wide range of operational tasks, significantly improving the reliability and cost efficiency of system operation.

[0830] The processing flow will be explained below.

[0831] Executing scheduled routine tasks

[0832] Step 1:

[0833] The server reads the schedule information for regular tasks set by the system administrator.

[0834] Step 2:

[0835] The server will automatically launch the backup process at the specified time.

[0836] Step 3:

[0837] The server executes the backup operation and stores the created backup data.

[0838] Step 4:

[0839] The server generates and stores a log of the backup operation.

[0840] Step 5:

[0841] The terminal notifies the user that the backup is complete.

[0842] Step 6:

[0843] Users can view the status of their backups on the dashboard.

[0844] Notification and response to non-routine operations

[0845] Step 1:

[0846] A user requests a non-routine task, such as installing an emergency patch.

[0847] Step 2:

[0848] The terminal sends the request to the server.

[0849] Step 3:

[0850] The server analyzes the request and determines how to handle it.

[0851] Step 4:

[0852] The server prepares the necessary resources and executes the non-routine tasks.

[0853] Step 5:

[0854] The server generates and stores logs as work is completed.

[0855] Step 6:

[0856] The terminal notifies the user that the task is complete.

[0857] Step 7:

[0858] The user checks the results of the work and provides feedback if necessary.

[0859] Automatic processing of requested work

[0860] Step 1:

[0861] A user requests the system to create a new account.

[0862] Step 2:

[0863] The terminal sends a request to the server.

[0864] Step 3:

[0865] The server analyzes the request and executes the necessary program.

[0866] Step 4:

[0867] The server will automatically create a new account.

[0868] Step 5:

[0869] The server stores the results of the account creation and generates a notification.

[0870] Step 6:

[0871] The terminal notifies the user that the account creation is complete.

[0872] Step 7:

[0873] The user confirms that the new account was created successfully.

[0874] Conducting an account inventory

[0875] Step 1:

[0876] The server periodically collects all account information in the system.

[0877] Step 2:

[0878] The server analyzes the account usage history and identifies unnecessary accounts.

[0879] Step 3:

[0880] The server generates a report of the inventory results.

[0881] Step 4:

[0882] The terminal displays the inventory results to the user.

[0883] Step 5:

[0884] The user instructs the deletion of unnecessary accounts.

[0885] Step 6:

[0886] The server deletes unnecessary accounts according to the user's instructions.

[0887] Step 7:

[0888] The server generates and stores a log of the deletion activity.

[0889] Step 8:

[0890] The terminal notifies the user that the deletion process is complete.

[0891] Step 9:

[0892] The user confirms that the inventory work is complete.

[0893] Automated Incident Response

[0894] Step 1:

[0895] The server monitors the system status in real time.

[0896] Step 2:

[0897] The server issues an alert when it detects an anomaly.

[0898] Step 3:

[0899] The server initiates automated response procedures and analyzes the problem.

[0900] Step 4:

[0901] The server will initiate the repair process if an automatic repair is possible.

[0902] Step 5:

[0903] If the server is unable to repair the problem, it will escalate it to the appropriate person.

[0904] Step 6:

[0905] The terminal notifies the user of the occurrence of an incident and the status of the response.

[0906] Step 7:

[0907] The user may check the response status and issue additional instructions.

[0908] Step 8:

[0909] The server generates a log when an incident is resolved and records the response history.

[0910] Step 9:

[0911] The terminal notifies the user that the incident response has been completed.

[0912] Step 10:

[0913] The user checks the incident response results.

[0914] Template-based initial configuration

[0915] Step 1:

[0916] The user requests the initial setup of a new system.

[0917] Step 2:

[0918] The terminal sends a request to the server.

[0919] Step 3:

[0920] The server parses the initialization procedure based on the template.

[0921] Step 4:

[0922] The server prepares the necessary resources and begins the initialization.

[0923] Step 5:

[0924] Once the configuration process is complete, the server records and saves the results in a log.

[0925] Step 6:

[0926] The terminal notifies the user that the initial settings are complete.

[0927] Step 7:

[0928] The user checks whether the initial settings have been performed correctly.

[0929] Maintenance schedule management

[0930] Step 1:

[0931] The server manages the maintenance schedule for the system.

[0932] Step 2:

[0933] The server automatically assigns maintenance personnel according to a schedule.

[0934] Step 3:

[0935] The terminal notifies the relevant personnel of the maintenance schedule.

[0936] Step 4:

[0937] The user checks the notification content and makes a request to adjust the schedule as necessary.

[0938] Step 5:

[0939] The server generates and stores a log when maintenance work is completed.

[0940] Step 6:

[0941] The terminal notifies the user that the maintenance work has been completed.

[0942] Step 7:

[0943] The user checks the maintenance results and provides necessary feedback.

[0944] Performance data collection and analysis

[0945] Step 1:

[0946] The server collects system performance data in real time.

[0947] Step 2:

[0948] The server analyzes the collected data to identify performance trends.

[0949] Step 3:

[0950] If the server detects an abnormal value, it issues an alert.

[0951] Step 4:

[0952] The terminal visualizes performance data and analysis results (e.g., graphs).

[0953] Step 5:

[0954] The user instructs system adjustments based on the visualized data.

[0955] Step 6:

[0956] The server follows the user's instructions and performs the necessary adjustments.

[0957] Step 7:

[0958] The terminal notifies the user of the adjustment result.

[0959] Step 8:

[0960] The user checks whether the adjustment was made correctly.

[0961] Automating release tasks

[0962] Step 1:

[0963] Users register new releases and changes in the system.

[0964] Step 2:

[0965] The terminal transmits the registration details to the server.

[0966] Step 3:

[0967] The server analyzes the release procedure and sets a schedule.

[0968] Step 4:

[0969] The server will automatically start the release process at the set time.

[0970] Step 5:

[0971] The server logs and stores the results once the work is complete.

[0972] Step 6:

[0973] The terminal notifies the user of the completion of the release work.

[0974] Step 7:

[0975] The user may check the release results and perform additional verification work.

[0976] Chatbot for inquiries

[0977] Step 1:

[0978] A user registers a query with the system.

[0979] Step 2:

[0980] The terminal transmits the inquiry to the server.

[0981] Step 3:

[0982] The server uses an AI chatbot to analyze the query and generate an appropriate answer.

[0983] Step 4:

[0984] The terminal displays the chatbot's response to the user.

[0985] Step 5:

[0986] The user checks the response and makes another inquiry if the problem is not resolved.

[0987] Step 6:

[0988] The server will notify the responsible party if escalation is required.

[0989] Step 7:

[0990] The terminal notifies the user of the progress of the escalation.

[0991] Step 8:

[0992] The user confirms the escalation result.

[0993] Automated contract management

[0994] Step 1:

[0995] The server collects the contract data and inputs it into the management system.

[0996] Step 2:

[0997] The server monitors contract expiration and renewal timing and sets alerts.

[0998] Step 3:

[0999] The server will alert you when updates or purchases are required.

[1000] Step 4:

[1001] The terminal displays the contract status and alerts to the user.

[1002] Step 5:

[1003] The user checks the alerts and carries out the necessary renewal and purchase procedures.

[1004] Step 6:

[1005] The server records the details of the procedure and saves the updated contract information.

[1006] Step 7:

[1007] The terminal notifies the user that the contract renewal has been completed.

[1008] Step 8:

[1009] The user rechecks the contract information and makes corrections if necessary.

[1010] Streamlined budget management

[1011] Step 1:

[1012] The server collects cost data related to system operation.

[1013] Step 2:

[1014] The server analyzes the collected data and visualizes the budget usage status.

[1015] Step 3:

[1016] The server issues an alert if it detects an abnormal risk of exceeding the budget.

[1017] Step 4:

[1018] The terminal displays budget usage and alerts to the user.

[1019] Step 5:

[1020] The user checks the budget situation and indicates any necessary adjustments.

[1021] Step 6:

[1022] The server reallocates the budget based on the adjustment instructions.

[1023] Step 7:

[1024] The terminal notifies the user that the adjustment is complete.

[1025] Step 8:

[1026] The user checks whether the budget has been managed correctly.

[1027] The above is a detailed explanation of the program processing for each business operation, broken down into specific steps. By describing the processing in detail step by step like this, you can clearly understand how each process progresses.

[1028] Example 1

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

[1030] Modern information systems require a wide range of operations and numerous management tasks, making manual management and maintenance extremely complex and time-consuming. Furthermore, when an emergency response is required or when there are numerous user inquiries, the absence of an automated response system can easily lead to a decline in operational efficiency. Furthermore, with multiple important tasks such as system performance, account management, and backup work, there is a high risk of incorrect operation or delayed response. To address these issues, a solution that can automate system operations and efficiently manage them is needed.

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

[1032] In this invention, the server includes means for automatically executing scheduled routine tasks, means for notifying non-routine tasks and manually or automatically responding to them, means for accepting and executing user-requested tasks, means for conducting an account inventory and identifying unnecessary accounts, means for monitoring the system status and automatically responding when an incident occurs, means for initializing the system based on a template, means for managing maintenance schedules and coordinating maintenance personnel, means for collecting and analyzing system performance data in real time, means for automating the release of new software and changes, means for automatically responding to user inquiries, means for automatically managing and updating contracts, means for managing budget usage and detecting abnormal budget overrun risks, means for analyzing request content and executing appropriate response procedures, means for initiating a backup process and saving data, means for automatically creating new accounts, means for identifying and deleting unused accounts, means for performing initial configuration using a template, means for detecting abnormalities and issuing alerts, and means for escalating to a responsible person when automatic repair is not possible. This improves the reliability and efficiency of system operation, and by automating business processes, reduces human error and enables timely responses.

[1033] A "scheduled routine task" is a task that is automatically executed at a set time or timing on a daily, weekly, or monthly basis.

[1034] "Non-routine work" refers to work that arises suddenly or that requires an emergency response, and is not included in the regular schedule.

[1035] A "user-requested task" is a task that a system user requests the system to perform based on a specific request.

[1036] "Account inventory" means periodically checking the usage status of all accounts and identifying and managing unused or unnecessary accounts.

[1037] An "incident" refers to the occurrence of an abnormal condition or problem in a system, which may disrupt normal operation.

[1038] "Template-based system initialization" is the process of automatically configuring a new system according to a predefined configuration template.

[1039] "Maintenance work schedule management" refers to setting a schedule for planning and carrying out system maintenance work and managing its progress.

[1040] "Performance data" refers to various data relating to the operating status and performance of a system, and is collected in real time.

[1041] "Release automation" is the process of automating new software releases and configuration changes.

[1042] "Automatic response to inquiries" is a mechanism in which the system automatically provides answers to inquiries from users.

[1043] "Contract management and renewal" means that the system monitors contract information and automatically manages renewal dates and deadlines.

[1044] "Budget usage management" refers to the real-time monitoring of expenses related to system operation and the detection and management of abnormal budget consumption.

[1045] "Analysis of request content" refers to analyzing a request from a user and determining an appropriate response procedure based on the content of the request.

[1046] "Initiating a backup process" refers to the execution of a backup operation for the purpose of safely storing data.

[1047] "Automatic account creation" refers to the automatic generation of a new account based on a user request.

[1048] "Identifying unused accounts" refers to identifying and managing accounts that have not been used for a certain period of time.

[1049] "Anomaly detection" means monitoring the state of a system and discovering abnormalities or errors that are out of the ordinary.

[1050] "Issuing an alert" means sending a notification when an abnormality is detected and warning the user or administrator.

[1051] "Automatic remediation escalation" means handing over an issue to the appropriate personnel when automatic remediation is not possible.

[1052] The purpose of this invention is to automate and streamline a wide range of tasks in system operation. In this system, the roles of the server, terminal, and user are clearly divided, and specific programs and processing procedures are executed for each role.

[1053] Executing scheduled routine tasks

[1054] The server automatically executes regular tasks (e.g., daily backups) on a regular basis based on schedule information set by the system administrator. The hardware used is a general-purpose server, and the software used is backup software.

[1055] Specific examples

[1056] Hardware used: General server

[1057] Software used: Backup software

[1058] Example prompt:

[1059] "Perform daily backups on standard servers using backup software according to the backup schedule set by the server administrator."

[1060] Notification and response to non-routine operations

[1061] A user requests a non-routine task, such as installing an emergency patch, through a terminal. This request is sent to the server, which analyzes and executes the appropriate response.

[1062] Specific examples

[1063] Hardware used: General server

[1064] Software used: Patch management software

[1065] Example prompt:

[1066] "When a user requests the installation of an emergency patch, please apply the patch using patch management software on a standard server and notify the user when the installation is complete."

[1067] Automatic processing of requested work

[1068] A user requests the creation of a new account through a terminal, and based on this request, the server automatically creates the account using the appropriate account management tools.

[1069] Specific examples

[1070] Hardware used: General server

[1071] Software used: Account Management Tool

[1072] Example prompt:

[1073] When a new account creation request is received, please use an account management tool on a standard server to automatically create the account and notify the user.

[1074] Conducting an account inventory

[1075] The server periodically collects and analyzes the usage status of all accounts and identifies unused accounts. This information is displayed as a report on the device, and the user can instruct the deletion of unnecessary accounts.

[1076] Specific examples

[1077] Hardware used: General server

[1078] Software used: LDAP

[1079] Example prompt:

[1080] Use LDAP to periodically analyze account usage on your general servers, identify unused accounts, and generate reports.

[1081] Automated Incident Response

[1082] The server monitors the system status in real time and immediately takes action when an abnormality is detected. If automatic repair is not possible, the issue is escalated to the person in charge.

[1083] Specific examples

[1084] Hardware used: General server

[1085] Software used: Monitoring tools

[1086] Example prompt:

[1087] "Monitor the health of your systems in real time and, when anomalies are detected, auto-remediate or escalate as necessary."

[1088] Template-based initial configuration

[1089] The user selects a template and sends a request to the system, and the server performs the initial setup of the system based on the template.

[1090] Specific examples

[1091] Hardware used: General server

[1092] Software used: Configuration management tools

[1093] Example prompt:

[1094] "When a user selects a template and submits a request, please use a configuration management tool on the general server to automatically perform the initial setup and notify the progress and completion status."

[1095] Maintenance schedule management

[1096] The server manages the maintenance schedule and coordinates the maintenance personnel. When the maintenance work is completed, it records the results in a log and notifies the user.

[1097] Specific examples

[1098] Hardware used: General server

[1099] Software used: Schedule management software

[1100] Example prompt:

[1101] "Manage maintenance schedules and notify personnel and users before and after maintenance work."

[1102] Performance data collection and analysis

[1103] The server collects and analyzes system performance data in real time and issues an alert if it detects any abnormal values.

[1104] Specific examples

[1105] Hardware used: General server

[1106] Software used: Performance monitoring tool

[1107] Example prompt:

[1108] "Collect and analyze various system performance data in real time, and issue alerts if an abnormality is detected."

[1109] Automating release tasks

[1110] Users request new software or changes, and the server automatically performs the release process.

[1111] Specific examples

[1112] Hardware used: General server

[1113] Software used: Continuous integration tools

[1114] Example prompt:

[1115] When a new software release or change is registered, use a continuous integration tool to automatically execute the release and notify us when it is complete.

[1116] Chatbot for inquiries

[1117] When a user makes a query, the device sends the details to the server, and the AI ​​chatbot generates an appropriate answer.

[1118] Specific examples

[1119] Hardware used: General server

[1120] Software used: AI chatbot

[1121] Example prompt:

[1122] "Please process user inquiries via the server using an AI chatbot, generate appropriate answers, and send them."

[1123] Automated contract management

[1124] The server monitors contract data and issues an alert when the renewal date approaches, prompting the user to take action.

[1125] Specific examples

[1126] Hardware used: General server

[1127] Software used: Contract management tool

[1128] Example prompt:

[1129] "Monitor contract data and issue alerts to notify users when renewals are approaching."

[1130] Streamlined budget management

[1131] The server collects cost data related to system operation, and if it detects an abnormal risk of exceeding the budget, the terminal notifies the user.

[1132] Specific examples

[1133] Hardware used: General server

[1134] Software used: Budgeting tools

[1135] Example prompt:

[1136] "Manage system operation-related costs and notify users if an abnormal risk of overspending is detected."

[1137] As described above, the system of the present invention automates a wide range of operational tasks, improving overall operational efficiency and reliability, thereby facilitating system management and reducing operational costs.

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

[1139] Executing scheduled routine tasks

[1140] Step 1:

[1141] The server references the configured schedule information (e.g., the time of the daily backup). The schedule information is obtained from cron jobs or scheduling software. The input is the schedule data, and the output is the backup timing information.

[1142] Specific operation:

[1143] Analyzes the cron job configuration file.

[1144] Queries the schedule database to get the backup execution time.

[1145] Step 2:

[1146] The server starts the backup process based on the acquired schedule. The software used here is a backup tool. The input is backup timing information, and the output is an instruction to start the backup process.

[1147] Specific operation:

[1148] Run the batch script "backup_tool start" from the command line.

[1149] Step 3:

[1150] The server copies the data directory to the specified backup destination. The input is the data directory and the backup destination information, and the output is the backup file.

[1151] Specific operation:

[1152] Use filesystem calls to copy the specified directory to the backup destination (e.g., using rsync or scp).

[1153] Step 4:

[1154] When the server completes the backup, it sends a notification to the user via the terminal. The input is the backup completion information, and the output is a notification message.

[1155] Specific operation:

[1156] Send notification emails using a mail server.

[1157] Display a backup completion message on the dashboard.

[1158] Notification and response to non-routine operations

[1159] Step 1:

[1160] A user requests a non-routine task (e.g., installing an emergency patch) through a terminal. The input is the request information from the user, and the output is the request data.

[1161] Specific operation:

[1162] Receive requests via web forms or APIs.

[1163] Step 2:

[1164] The server analyzes the request content. The input is the request data and the output is the analysis result.

[1165] Specific operation:

[1166] Parse the request data and extract the necessary information.

[1167] Step 3:

[1168] The server downloads and installs the necessary patches based on the analysis results. The software used is a patch management tool. The input is the analysis results and patch information, and the output is the completion of the installation.

[1169] Specific operation:

[1170] Use the CLI to run the command "patch_tool apply -patch_id".

[1171] Step 4:

[1172] When the installation is complete, the server sends a notification to the user via the terminal. The input is the installation completion information, and the output is the notification message.

[1173] Specific operation:

[1174] Send reports via email and system notifications.

[1175] Automatic processing of requested work

[1176] Step 1:

[1177] A user requests the creation of a new account through a terminal. The input is the request information from the user, and the output is the request data.

[1178] Specific operation:

[1179] Use the Web API to receive requests.

[1180] Step 2:

[1181] The server analyzes the request content. The input is the request data and the output is the analysis result.

[1182] Specific operation:

[1183] Parse the JSON format and obtain the required fields.

[1184] Step 3:

[1185] The server uses the account management tool to create a new account. The input is the parsed result, and the output is the new account information.

[1186] Specific operation:

[1187] Run the PowerShell script and use the command "New-ADUser".

[1188] Step 4:

[1189] When the account creation is completed, the server sends a notification to the user via the terminal. The input is the account creation completion information, and the output is a notification message.

[1190] Specific operation:

[1191] Notifications will be sent via email and dashboard.

[1192] Conducting an account inventory

[1193] Step 1:

[1194] The server uses LDAP to collect all account usage information: the input is an LDAP query and the output is account usage information.

[1195] Specific operation:

[1196] Run an LDAP query to get the last login time for each account.

[1197] Step 2:

[1198] The server analyzes the acquired data and identifies unused accounts. The input is account usage information, and the output is a list of unused accounts.

[1199] Specific operation:

[1200] Query the database to extract accounts that have not logged in for a specified period of time.

[1201] Step 3:

[1202] The server generates a report on unused accounts and displays it on a terminal. The input is a list of unused accounts, and the output is the report data.

[1203] Specific operation:

[1204] Use the report generator to create reports in PDF and spreadsheet formats.

[1205] Step 4:

[1206] The user instructs the deletion of unnecessary accounts based on the report, and the server executes the deletion and records the result in a log. The input is the user's instruction, and the output is the deletion completion information.

[1207] Specific operation:

[1208] Run the PowerShell script to delete the target account.

[1209] Automated Incident Response

[1210] Step 1:

[1211] The server monitors the system status in real time. The input is real-time system data, and the output is anomaly detection information.

[1212] Specific operation:

[1213] Use monitoring tools to analyze system logs.

[1214] Step 2:

[1215] When the server detects an anomaly, it immediately starts to take action. The input is the anomaly detection information, and the output is the response result information.

[1216] Specific operation:

[1217] Run the automatic repair script.

[1218] Step 3:

[1219] If automatic repair is not possible, the server escalates the issue to the person in charge. The input is the response result information, and the output is an escalation notification.

[1220] Specific operation:

[1221] Use a mail server to send escalation notifications.

[1222] Step 4:

[1223] When the incident response is completed, the server sends a notification to the user via the terminal. The input is the response completion information, and the output is a notification message.

[1224] Specific operation:

[1225] The results will be notified to the user via email or system notification.

[1226] (Application example 1)

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

[1228] There is a need to efficiently manage and automate the numerous tasks and incident responses required in factory operations, improving operational reliability and cost efficiency. Traditionally, a wide range of management tasks, such as monitoring the status of factory equipment and robots, responding when anomalies occur, and executing routine tasks, have often been performed manually, resulting in potential work delays and human error. Furthermore, insufficient notification of task progress and completion can lead to insufficient information sharing among staff, resulting in a decline in work efficiency. A system that can solve these issues is needed.

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

[1230] In this invention, the server includes a means for monitoring the status of equipment in the factory in real time and automatically responding when an abnormality is detected, a means for automatically executing routine tasks, and a means for notifying users of progress and completion, thereby making it possible to improve the efficiency and reliability of operations in factory management.

[1231] "Regular tasks" are tasks that are performed periodically at specific times or cycles.

[1232] "Non-routine work" refers to work carried out to respond to emergencies or unexpected situations.

[1233] A "requested task" is a task that is performed based on a specific request from a user.

[1234] "Account inventory" is the process of checking the usage status of registered accounts and identifying and deleting unnecessary accounts.

[1235] An "incident" is an abnormality or failure that occurs during the operation of a system or equipment.

[1236] A "template" is a set of predefined procedures used to efficiently perform a particular task or setting.

[1237] "Maintenance work" refers to the maintenance work carried out to maintain the normal operation of systems and equipment.

[1238] "Performance data" refers to data that indicates the operational status of a system or device, and includes, for example, availability rate and response time.

[1239] "Release work" refers to the work of introducing new software or updating existing software.

[1240] "Inquiry response" refers to the task of providing a response to a question or request from a user.

[1241] "Contract management" refers to the task of managing contract contents and deadlines, and carrying out renewal procedures and confirmations.

[1242] "Budget usage status" is data that indicates the status of expenses related to system operation.

[1243] "Real-time monitoring" means constantly monitoring the status of systems and equipment and instantly detecting abnormalities.

[1244] "Escalation" is a procedure for notifying the person in charge or a higher-level manager when a problem occurs and urging them to take action.

[1245] This invention is a system aimed at automating and streamlining factory operations. This system is comprised of multiple pieces of hardware and software, centered around a server, and is accessible to users via smartphones or head-mounted displays (HMDs).

[1246] The server automatically executes scheduled routine tasks and performs regular backups and system updates, preventing human error and improving operational reliability.

[1247] The system also monitors incidents in real time, responds immediately if an abnormality is detected, and automatically escalates the incident and notifies the responsible person if it is difficult to handle.

[1248] Furthermore, the server analyzes user requests and automatically initiates tasks such as creating a new account or starting a specific work process, thereby improving response speed and user convenience.

[1249] Template-based system initial setup is also possible, allowing for efficient configuration of various settings required when introducing new equipment or systems. Templates contain predefined procedures, allowing for quick and reliable initial setup.

[1250] It also manages the schedule for maintenance work and notifies maintenance personnel as necessary. When the maintenance work is completed, the results are recorded in a log and the user is notified.

[1251] The system collects and analyzes performance data in real time, and if abnormal behavior is detected, it immediately issues an alert to notify the user, who can then view this data on a dashboard and make any necessary adjustments.

[1252] The application also automates release processes, making it easy to deploy new software or update existing systems. Users can monitor the progress of releases and receive notifications when they are complete.

[1253] The system uses a chatbot that uses a generative AI model to respond to inquiries, providing quick and accurate answers to user questions and escalating cases as needed.

[1254] Contract management and renewals are also automated, with users notified when deadlines approach and prompted to take necessary measures.

[1255] In addition, it also manages budget usage and notifies users if an abnormal risk of budget overrun is detected, and provides countermeasures.

[1256] As a concrete example, the following prompt sentence is used:

[1257] Template name: "New Robot Installation Settings"

[1258] 1. Enter the basic information about your robot.

[1259] 2. Select a work area.

[1260] 3. Configure the sensor settings.

[1261] 4. Conduct a test drive.

[1262] The server displays prompts via the smartphone or HMD interface, and the entire process can be carried out smoothly by the user following the procedure. This system therefore contributes greatly to improving the efficiency and reliability of factory operations.

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

[1264] Step 1:

[1265] Scheduling and executing routine tasks

[1266] The server schedules regular tasks based on the scheduling information. When the scheduled time arrives, the target task is automatically executed. Specifically, if a daily backup is required, the server automatically starts the backup process and backs up the specified data. The input is the schedule information for the regular tasks, and the output is the status indicating that the backup has been completed.

[1267] Step 2:

[1268] Real-time incident monitoring and response

[1269] The server monitors various sensors and system logs, and if an abnormality is detected, it initiates a real-time response. For example, if an abnormality in equipment performance is detected, an automatic repair process is initiated. Once the repair is complete, a notification is sent to the user. The input is data from sensors and logs, and the output is the incident response status.

[1270] Step 3:

[1271] Acceptance and execution of user-requested work

[1272] When a user requests a new task, the task request is sent to the server via the terminal. The server analyzes the request and takes appropriate action. For example, if a request is made to create a new account, the server automatically creates the account based on the required data. The input is the task request from the user, and the output is a notification that the task has been completed.

[1273] Step 4:

[1274] Template-based system initialization

[1275] The user selects a template through the terminal and requests initial setup from the system. The server automatically performs various setup procedures based on the template. For example, the setup procedure when a new robot is introduced is performed using this template. The input is the template selection and initial setup request, and the output is a notification that the setup is complete.

[1276] Step 5:

[1277] Maintenance work schedule management

[1278] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, a notification is sent to the person in charge via the terminal. When the maintenance work is completed, the results are recorded in a log and the user is notified. The input is the maintenance schedule information, and the output is a notification that the maintenance has been completed.

[1279] Step 6:

[1280] Performance data collection and analysis

[1281] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is immediately issued and the user is notified. The input is performance data, and the output is an anomaly detection alert.

[1282] Step 7:

[1283] Automating release tasks

[1284] When a user registers a new release in the system, the server analyzes the procedure and schedules it. The release process is automatically performed and a notification is sent to the user upon completion. The input is the release procedure information, and the output is a notification of release completion.

[1285] Step 8:

[1286] Inquiry response

[1287] A user's inquiry is sent to the server via the terminal. The server uses an AI chatbot to generate an appropriate response and sends it to the user. It also escalates the case as needed. The input is the user's inquiry, and the output is the response to the inquiry.

[1288] Step 9:

[1289] Automated contract management

[1290] The server monitors the contract data and notifies the user when the renewal date is approaching. Necessary renewal procedures can also be carried out automatically. The input is the contract data, and the output is a notification when renewal occurs and a notification when renewal is complete.

[1291] Step 10:

[1292] Managing budget usage

[1293] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal budget over-risk is detected, it notifies the user and provides countermeasures. The input is cost data, and the output is an alert of the budget over-risk.

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

[1295] The system of the present invention combines the automation functions of conventional operational tasks with an emotion engine that recognizes user emotions and optimizes responses. This system operates as follows, and performs various operational tasks efficiently and user-friendly.

[1296] Executing scheduled routine tasks

[1297] The server reads the schedule information for regular operations set by the system administrator. It automatically starts the backup process at the specified time and starts backing up data. When the operation is complete, a backup completion notification is sent to the user via the terminal. The user can check the backup status on the dashboard.

[1298] Notification and response to non-routine operations

[1299] A user requests a non-routine task, such as installing an emergency patch, from the system. The request is sent to the server via a terminal. Upon receiving the request, the server analyzes and executes the appropriate response procedure. Once the task is completed, a completion notification is sent to the user via the terminal.

[1300] Automatic processing of requested work

[1301] When a user requests the creation of a new account, the device sends the request to the server, which analyzes the request and executes the appropriate program to automatically create the account. The result of this operation is notified to the user via the device, and the user confirms that the new account was successfully created.

[1302] Conducting an account inventory

[1303] The server periodically collects and analyzes the usage status of all accounts. It identifies unused and unnecessary accounts and generates a report of the inventory results. This report is displayed on the terminal, and the user can instruct the server to delete unnecessary accounts. The server deletes the unnecessary accounts based on the instructions and records the results in a log.

[1304] Automated Incident Response

[1305] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, and if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[1306] Template-based initial configuration

[1307] When a new system needs initial setup, the user selects a template and sends a request to the system. The server executes the initial setup procedure based on the template. Once the setup is complete, the terminal notifies the user of the progress and completion.

[1308] Maintenance schedule management

[1309] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, the schedule is notified to the person in charge via the terminal. When the maintenance work is completed, the server records the results in a log and notifies the user.

[1310] Performance data collection and analysis

[1311] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is issued and the user is notified via their terminal. The user can check the performance analysis results on a dashboard and make any necessary adjustments.

[1312] Automating release tasks

[1313] When a user registers a new release or change in the system, the server analyzes the procedure and schedules it. The release process is carried out automatically, and the user is notified via their terminal once it is complete.

[1314] Chatbot for inquiries

[1315] When a user makes a query, the device sends the query to the server, which uses an AI chatbot to generate an appropriate response and send it to the user. If necessary, the server also escalates the query.

[1316] Automated contract management

[1317] The server monitors contract data and manages expiration dates and renewal timing. When a contract is due for renewal, it sends an alert to the user via their device, urging them to take the necessary measures.

[1318] Streamlined budget management

[1319] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal risk of budget overrun is detected, the terminal notifies the user and provides necessary countermeasures.

[1320] Introducing an emotion engine that recognizes user emotions

[1321] The system incorporates an emotion engine that recognizes the user's emotions and optimizes the response.

[1322] Example 1: Using an emotion engine in response to inquiries

[1323] When a user makes a query, the server uses an emotion engine to identify the user's emotional state based on context and linguistic analysis. For example, if the user expresses strong dissatisfaction, the emotion engine will recognize the situation and the server will be configured to escalate the query to a human agent more quickly. The tone and content of the response will also be adjusted according to the user's emotion.

[1324] Example 2: Using emotion engines in incident response

[1325] When an incident occurs, the server uses an emotion engine to analyze the user's actions and comments when checking the response status within the system, and if the user feels strong stress or anxiety, it quickly escalates the situation and provides further support.The emotion engine also has a function to send follow-up notifications after the incident is resolved based on the user's emotional data.

[1326] Example 3: Using the emotion engine in routine and non-routine notifications

[1327] In notifications sent upon the completion of routine or non-routine tasks, an emotion engine can be used to analyze the user's emotional state, and, for example, a message of encouragement can be sent to a user who is feeling tired, or a message of gratitude to a user who is feeling satisfied.

[1328] In this way, by recognizing the user's emotions and adjusting the response appropriately, it is possible to increase the satisfaction of system users and provide a better user experience.

[1329] The processing flow will be explained below.

[1330] Use of emotion engines in inquiries

[1331] Step 1:

[1332] A user enters a query into the system.

[1333] Step 2:

[1334] The terminal sends the inquiry to the server.

[1335] Step 3:

[1336] The server analyzes the query received by the emotion engine and identifies the user's emotional state (e.g., dissatisfaction, satisfaction, stress).

[1337] Step 4:

[1338] The server generates optimized responses and responses based on the results of the emotion engine.

[1339] Step 5:

[1340] If the user expresses strong dissatisfaction, the server automatically escalates the response process and notifies a human agent.

[1341] Step 6:

[1342] The terminal displays the answer to the user.

[1343] Step 7:

[1344] The user checks the response and makes another inquiry if necessary.

[1345] Using Emotion Engines in Incident Response

[1346] Step 1:

[1347] The server monitors the system status in real time and issues an alert if an abnormality is detected.

[1348] Step 2:

[1349] A user accesses the system to check the status of an incident and tries to understand the situation.

[1350] Step 3:

[1351] The server uses an emotion engine to analyze the user's actions and comments within the system.

[1352] Step 4:

[1353] The server identifies the user's emotional state (e.g., stress, anxiety) and optimizes response procedures.

[1354] Step 5:

[1355] If the user shows signs of high stress, the server automatically initiates an escalation procedure and notifies personnel.

[1356] Step 6:

[1357] After the incident is resolved, the server sends follow-up notifications taking into account the user's emotional state.

[1358] Step 7:

[1359] The device displays the notification content to the user.

[1360] Using emotion engines to inform routine and non-routine tasks

[1361] Step 1:

[1362] The server executes routine and non-routine tasks and logs the completion status.

[1363] Step 2:

[1364] The server prepares the notification content and uses an emotion engine to analyze the user's past reactions and current situation.

[1365] Step 3:

[1366] The server optimizes the notification content based on the user's emotional state (e.g., an encouraging message for a user who is feeling tired, a thank you message for a user who is feeling satisfied).

[1367] Step 4:

[1368] The terminal sends the notification content to the user.

[1369] Step 5:

[1370] The user receives a notification and checks the status.

[1371] These are the detailed steps of each process that incorporates the emotion engine, which enables the system to take the user's emotional state into consideration and provide the most appropriate response.

[1372] Example 2

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

[1374] Conventional systems individually performed tasks such as automating routine tasks, notifying and responding to non-routine tasks, account management, incident response, initial system setup, maintenance schedule management, performance data collection and analysis, release work, inquiry response, contract management, and budget management, but because they did not take user emotions into consideration, there were limitations to improving the user experience.In addition, they did not generate prompts using an emotion engine or generative AI model, making it difficult to provide flexible and individual responses.

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

[1376] In this invention, the server includes means for automatically executing scheduled routine tasks, means for notifying non-routine tasks and responding to them manually or automatically, means for accepting and executing tasks requested by users, means for conducting account inventory and identifying unnecessary accounts, means for monitoring system status and automatically responding when an incident occurs, means for initializing the system based on templates, means for managing maintenance schedules and coordinating maintenance personnel, means for collecting and analyzing system performance data in real time, means for automating the release of new software and changes, means for automatically responding to user inquiries, means for automatically managing and renewing contracts, means for managing budget usage and detecting abnormal budget overrun risks, means for recognizing user emotions and optimizing responses, means for analyzing inquiry content and supporting incident response using an emotion engine, and means for generating prompt sentences according to the user's emotional state using a generative AI model. This enables flexible and optimal system responses that take user emotions into account.

[1377] A "scheduled routine task" is a task that is automatically executed periodically according to a schedule set in advance by a system administrator.

[1378] "Non-routine tasks" are tasks that occur infrequently and are difficult to predict, such as installing emergency patches.

[1379] A "user-requested task" is a task in which a user requests a specific action from the system.

[1380] "Account inventory" is the process of periodically examining all accounts registered in the system and identifying and managing unused and unnecessary accounts.

[1381] An "incident" refers to the occurrence of an unexpected problem, such as a system abnormality or failure.

[1382] "Initial system configuration based on a template" refers to the procedure for initializing a new system or application using a pre-prepared configuration format.

[1383] "Managing maintenance work schedules" refers to planning and coordinating system maintenance work and carrying it out at the appropriate time.

[1384] "System performance data" refers to information about the operating status of the system, such as CPU usage, memory usage, and disk I / O.

[1385] "Release operations" is the process for applying new software or system changes to a production environment.

[1386] An "inquiry" refers to a question or request made by a user to the system for information or problem resolution.

[1387] "Contract management" refers to managing the content and expiration dates of contracts related to system operation, and handling matters such as renewals and cancellations.

[1388] "Budget utilization" refers to the management of costs associated with operating the system and the monitoring of planned budgets and actual expenditures.

[1389] An "emotion engine" is a system for analyzing and identifying a user's emotional state from their text and behavior.

[1390] A "generative AI model" is an artificial intelligence system that uses natural language processing and machine learning to generate appropriate prompts and responses based on the user's emotions and requests.

[1391] The system of the present invention is designed to automate a wide range of operational tasks, recognize user emotions, and optimize responses. Next, a specific method for running the program of this system will be described.

[1392] Executing scheduled routine tasks

[1393] The server reads the schedule information for regular tasks set by the system administrator. This information is obtained from a database (e.g., MySQL). When the specified time arrives, the server automatically starts the backup process. Backup software (e.g., Acronis Backup) is used to save the data to the server's storage (e.g., NAS). When the backup is complete, the server sends a completion notification to the user via their device (e.g., Windows PC or MacBook), and the user can check the backup status on a management screen (e.g., a web application).

[1394] Notification and response to non-routine operations

[1395] A user requests a non-routine task, such as installing an emergency patch, from the system. This request is sent from the terminal to the server, and communication is carried out using an HTTP request. The server receives the request, analyzes the appropriate response procedure, and executes a script. For example, an automation tool such as Ansible is used to install an emergency patch. After the task is completed, the server sends a completion notification to the user via the terminal.

[1396] Automatic processing of requested work

[1397] When a user requests the creation of a new account, the device sends the request to the server. This communication uses the HTTPS protocol, and the request data is sent in JSON format. The server receives the request and automatically creates a new account using LDAP or Active Directory. A completion notification is sent to the user via the device, and the user can view the details of the new account by email or on the system dashboard.

[1398] Conducting an account inventory

[1399] The server periodically collects usage information for all accounts from LDAP or Active Directory and analyzes it using Python scripts and data analysis libraries (e.g., Pandas, Matplotlib). It identifies unnecessary accounts and generates a report. This report is displayed on the terminal, and the user can instruct the deletion of unnecessary accounts. The server deletes the accounts based on the instructions and records the operation log in a database (e.g., MySQL).

[1400] Automated Incident Response

[1401] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, and if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[1402] Introducing an emotion engine that recognizes user emotions

[1403] This system incorporates an emotion engine that recognizes user emotions and optimizes responses. For example, it analyzes the content of inquiries and the user's actions and comments during incident response, and uses an emotion engine (e.g., IBM Watson NLU) to identify the user's emotional state.

[1404] Example: Using an emotion engine in customer inquiries

[1405] When a user makes an inquiry, the server uses an emotion engine to identify the user's emotional state. If the inquiry is "I'm having trouble using the service!", the emotion engine will emphasize the "trouble" part and quickly escalate the situation. The generative AI model uses this information to generate a prompt.

[1406] Example prompt sentence:

[1407] "If a user is having trouble using the service, escalate it quickly."

[1408] In this way, the system can provide flexible and optimal responses that take into account the user's emotions, improving the user experience.

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

[1410] Executing scheduled routine tasks

[1411] Step 1:

[1412] The server reads the schedule information for regular tasks set by the system administrator from a database (e.g., MySQL).

[1413] Input: Schedule information from the database

[1414] Output: Loaded schedule information

[1415] Specific operation: The server executes an SQL query to retrieve schedule information using a SELECT statement.

[1416] Step 2:

[1417] When the specified time arrives, the server will automatically launch the backup process.

[1418] Input: Specified time according to schedule information

[1419] Output: Backup process starts

[1420] What it does: Run Acronis Backup software using a cron job or task scheduler.

[1421] Step 3:

[1422] When the backup is complete, the server sends a completion notification to the terminal.

[1423] Input: Backup completion status

[1424] Output: Completion notification message

[1425] Specific operation: The server sends a notification email via the mail server, or sends a notification to the device using the web application API.

[1426] Notification and response to non-routine operations

[1427] Step 1:

[1428] A user requests a non-routine task, such as installing an emergency patch, from the system.

[1429] Input: Non-routine work request from user

[1430] Output: The request is sent from the terminal to the server.

[1431] Specific operation: The user enters a request through a web form or API, and the device sends this request in JSON format to the server.

[1432] Step 2:

[1433] The server receives the request, analyzes it, and determines the appropriate course of action.

[1434] Input: Non-routine work request data

[1435] Output: Action steps

[1436] What happens: The server runs a Python script, analyzes the request, and decides which tool (e.g., Ansible) to use.

[1437] Step 3:

[1438] The server performs non-routine tasks according to the determined response procedures.

[1439] Input: Response procedure

[1440] Output: Results of non-routine tasks

[1441] What it does: Runs an Ansible playbook to apply an emergency patch.

[1442] Step 4:

[1443] When the work is completed, the server sends a completion notification to the user via the terminal.

[1444] Input: Non-routine task execution completion status

[1445] Output: Completion notification

[1446] Specific operation: The server sends a notification to the user via the mail server or web application API.

[1447] Automatic processing of requested work

[1448] Step 1:

[1449] When a user requests the creation of a new account, the device sends the request to the server.

[1450] Input: Account creation request

[1451] Output: The request is sent to the server

[1452] How it works: The user enters a request through a web form or API, and the device sends it to the server using the HTTPS protocol.

[1453] Step 2:

[1454] The server receives the request, analyzes it, and creates a new account.

[1455] Input: Account creation request data

[1456] Output: Account creation status

[1457] What it does: The server runs a Python script to automatically create new accounts using LDAP or Active Directory.

[1458] Step 3:

[1459] Once the account creation is complete, the server notifies the user of the results via the terminal.

[1460] Input: Account creation completion status

[1461] Output: Completion notification

[1462] Specific operation: The server sends a notification to the user via the mail server or web application API.

[1463] Conducting an account inventory

[1464] Step 1:

[1465] The server periodically collects all account usage information from LDAP or Active Directory.

[1466] Input: Account data

[1467] Output: Collected usage data

[1468] What it does: The server runs a Python script that queries and collects account usage information from LDAP and Active Directory.

[1469] Step 2:

[1470] The server analyzes the collected data and identifies unnecessary accounts.

[1471] Input: Usage data

[1472] Output: List of unnecessary accounts

[1473] What it does: Use Python scripts and data analysis libraries (e.g., Pandas) to analyze account usage frequency and last login time.

[1474] Step 3:

[1475] The server generates a report of unnecessary accounts and displays it on the terminal.

[1476] Input: List of unnecessary accounts

[1477] Output: Report

[1478] Specific operation: Use Pandas and Matplotlib to generate analysis results in report format (e.g. PDF or HTML).

[1479] Step 4:

[1480] The user instructs the deletion of unnecessary accounts.

[1481] Input: User deletion instructions

[1482] Output: Delete instruction data

[1483] Specific operation: The user enters deletion instructions via a web form or API, and the device sends them to the server.

[1484] Step 5:

[1485] The server deletes the account based on the user's instructions and records the operation log.

[1486] Input: Data for deletion instructions

[1487] Output: Deletion completion status, operation log

[1488] Specific operation: The server deletes the account using a Python script and records the operation log in the MySQL database using an INSERT statement.

[1489] (Application example 2)

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

[1491] Conventional operational automation systems were unable to recognize the user's emotional state and respond accordingly, making it difficult to improve the user experience. Furthermore, content distribution services were unable to recommend appropriate content based on the user's emotions, resulting in a decline in user satisfaction. Technology to address this issue is needed.

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

[1493] In this invention, the server includes: means for automatically executing scheduled routine tasks; means for notifying non-routine tasks and manually or automatically responding to them; means for accepting and executing tasks requested by users; means for taking account inventories and identifying unnecessary accounts; means for monitoring the system status and automatically responding when an incident occurs; means for initializing the system based on templates; means for managing maintenance schedules and coordinating maintenance personnel; means for collecting and analyzing system performance data in real time; means for automating the release of new software and changes; means for automatically responding to inquiries from users; means for automatically managing and renewing contracts; means for managing budget usage and detecting abnormal budget overrun risks; and means for analyzing user emotions using an emotion engine that recognizes user emotions and optimizes responses, and recommending content corresponding to the user's emotional state. This makes it possible to improve the user experience by recognizing user emotions and providing optimal responses.

[1494] A "scheduled routine task" is a task that is planned in advance and executed periodically based on a preset schedule.

[1495] "Non-routine work" refers to temporary work that is not performed regularly according to a specific schedule, but occurs as needed.

[1496] A "requested work" is a specific job or task that is performed based on a request from a user.

[1497] "Account inventory" is the process of checking the usage status of all accounts and identifying unnecessary accounts.

[1498] "Monitoring the system status" means monitoring the operating status and performance of the entire system in real time.

[1499] An "incident" is an event in which a problem such as an abnormality or failure occurs in a system.

[1500] "Performing initial system settings based on a template" means automatically performing initial system settings on a new system according to a predetermined setting pattern.

[1501] "Managing maintenance work schedules" means planning and coordinating maintenance work such as system maintenance and updates, and managing the schedule.

[1502] "Collecting system performance data and analyzing it in real time" means collecting data on the system's operating status and performance and analyzing it immediately.

[1503] "Automating the release of new software and changes" means automating the introduction of new software and the modification of existing software.

[1504] "Automatically responding to inquiries from users" means that the system automatically provides appropriate answers to questions or requests submitted by users.

[1505] "Automatically managing and updating contracts" means that the system automatically checks and updates the contract contents.

[1506] "Manage budget usage and detect abnormal budget overspending risks" means monitoring how the budget is used and detecting the risk of excessive budget usage.

[1507] The "emotion engine" is an engine that analyzes the user's emotions in real time and responds optimally according to their emotional state.

[1508] "User's emotional state" refers to the type and intensity of emotion that a user is feeling at a particular point in time.

[1509] "Recommending content" means presenting optimal content that matches the user's interests and emotional state.

[1510] MODE FOR CARRYING OUT THE INVENTION

[1511] The present invention provides a system for recognizing a user's emotions and taking an optimal response accordingly. Specific embodiments will be described below.

[1512] The server manages scheduled routine tasks, automatically executing them at designated times, such as backup processes and routine maintenance tasks. The server also accepts requests for non-routine tasks and responds appropriately, such as installing emergency patches or allocating additional resources.

[1513] A user's request is sent to the server via the device, which then analyzes the request and automatically executes the corresponding procedure, such as creating a new account or updating an existing account.

[1514] The server periodically monitors account usage and identifies unnecessary accounts. This information is generated as a report and notified to the user. The user can then instruct the server to delete unnecessary accounts.

[1515] Additionally, the server monitors the system status in real time and automatically initiates a remediation process if an incident occurs, or escalates to a responsible party if it is not possible. The server also includes a means to initially configure new systems based on templates.

[1516] The server manages the maintenance schedule and notifies the maintenance personnel of the schedule. Performance data is collected and analyzed in real time, and an alert is issued if an abnormal value is detected.

[1517] When a user requests a new software release or change, the server analyzes the procedure and performs the release in an automated manner, and also automatically responds to user inquiries using an AI chatbot.

[1518] The server also automatically manages contracts and budgets. It monitors contract expirations and renewals and sends alerts to users. Budget usage is also monitored in real time, and if an abnormal risk of budget overruns is detected, a notification is sent.

[1519] Of particular note is the introduction of an emotion engine. The server uses the emotion engine to analyze the user's emotional state in real time. For example, when a user is watching content or posting a review, the server identifies the user's emotion based on context and linguistic analysis. Based on this emotional state, the server recommends the most appropriate content and notifies the user.

[1520] Hardware / Software Used

[1521] This system mainly uses the following hardware and software:

[1522] Hardware: Smartphone (Android / iOS), server

[1523] Software: Python, EmotionRecognition library, Requests library, RESTful API

[1524] Specific examples

[1525] Example 1: If a user types, "I've been very busy today, I want to relax," the emotion engine will recognize "stress" and recommend relaxing content (e.g., videos of nature scenes).

[1526] Prompt Sentence Examples

[1527] 1. Example prompt:

[1528] User input text: "Today has been very busy, I want to relax."

[1529] Process: Request emotion analysis from the emotion engine to detect "stress." Retrieve "relaxing videos" from the recommended content API and notify the user.

[1530] In this way, the present invention significantly improves the user experience by recognizing the user's emotions and automatically providing optimal content corresponding to those emotions.

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

[1532] Processing Steps

[1533] Step 1: Receiving User Input

[1534] The user enters a sentence about their feelings into a text field in the system, such as "I'm really tired today. I don't feel like doing anything." This input is collected by the device and sent to the next step.

[1535] Step 2: Sentiment Analysis

[1536] The server sends the user's text received from the device to the emotion engine. The emotion engine uses natural language processing technology to analyze the text and identify the user's emotion. The data processing performed at this time involves tokenizing the text and assigning emotion labels, resulting in emotion labels such as "stress" and "satisfaction."

[1537] Step 3: Sending emotion labels

[1538] The server retrieves the emotion labels obtained from the emotion engine and sends them to the content recommendation system. This data is sent via a RESTful API.

[1539] Step 4: Content Recommendation

[1540] The content recommendation system provides the server with the optimal content according to the emotion label. The system uses past user data and a matching algorithm to select the content that best suits the user's emotion. The data calculation involves searching for the appropriate content ID from the database using the emotion label as a key. The output is information about the recommended content.

[1541] Step 5: Notification of recommended content

[1542] The server transmits the recommended content information obtained from the content recommendation system to the terminal. The terminal receives this information and notifies the user. Specifically, it displays a notification screen and presents the recommended content to the user along with a message such as "Here is the recommended content."

[1543] Adding specific examples

[1544] For example, if a user types "I'm having a great time today," the processing steps would be:

[1545] Step 1: The device receives user input such as "I'm having a great time today."

[1546] Step 2: The server sends this sentence to the emotion engine and gets the emotion label "joy."

[1547] Step 3: The server sends the emotion label of “joy” to the content recommendation system.

[1548] Step 4: The content recommendation system recommends entertaining content suitable for "pleasure" (e.g., comedy movies).

[1549] Step 5: The server sends this content information to the terminal, which then notifies the user.

[1550] Through the above steps, the present invention can provide a content recommendation function that is adapted to the user's emotions, thereby improving the user experience.

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

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

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

[1554] [Third embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

[1567] The system of the present invention automates and streamlines a wide range of tasks in system operation, and includes various programs for this purpose. Below, we will explain in natural language how the programs in this system work, using concrete examples.

[1568] Executing scheduled routine tasks

[1569] The server automatically performs routine tasks (e.g., daily backups) based on scheduling information set by the system administrator. At the set time, the server launches the backup process and begins backing up data. When the task is complete, a notification is sent to the user via the terminal, and the backup status can be checked on the dashboard.

[1570] Notification and response to non-routine operations

[1571] Users can request non-routine tasks (e.g., installing emergency patches) from the system. The request is sent to the server via the terminal. When the server receives the request, it analyzes and executes the appropriate response procedure. Once the response is completed, a completion notification is sent to the user via the terminal.

[1572] Automatic processing of requested work

[1573] When a user requests the creation of a new account, the device sends the request to the server, which analyzes the request and executes the appropriate program to automatically create the account. The result of this operation is notified to the user via the device, and the user confirms that the new account was successfully created.

[1574] Conducting an account inventory

[1575] The server periodically collects and analyzes the usage status of all accounts. It identifies unused and unnecessary accounts and generates a report of the inventory results. This report is displayed on the terminal, and the user can instruct the server to delete unnecessary accounts. The server deletes the unnecessary accounts based on the instructions and records the results in a log.

[1576] Automated Incident Response

[1577] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, but if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[1578] Template-based initial configuration

[1579] When a new system needs initial setup, the user selects a template and sends a request to the system. The server executes the initial setup procedure based on the template. Once the setup is complete, the terminal notifies the user of the progress and completion.

[1580] Maintenance schedule management

[1581] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, the schedule is notified to the person in charge via the terminal. When the maintenance work is completed, the server records the results in a log and notifies the user.

[1582] Performance data collection and analysis

[1583] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is issued and the user is notified via their terminal. The user can check the performance analysis results on a dashboard and make any necessary adjustments.

[1584] Automating release tasks

[1585] When a user registers a new release or change in the system, the server analyzes the procedure and schedules it. The release process is carried out automatically, and the user is notified via their terminal once it is complete.

[1586] Chatbot for inquiries

[1587] When a user makes a query, the device sends the query to the server, which uses an AI chatbot to generate an appropriate response and send it to the user. If necessary, the server also escalates the query.

[1588] Automated contract management

[1589] The server monitors contract data and manages expiration dates and renewal timing. When a contract is due for renewal, it sends an alert to the user via their device, urging them to take the necessary measures.

[1590] Streamlined budget management

[1591] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal risk of budget overrun is detected, the terminal notifies the user and provides necessary countermeasures.

[1592] As described above, the system of the present invention can automate and streamline a wide range of operational tasks, significantly improving the reliability and cost efficiency of system operation.

[1593] The processing flow will be explained below.

[1594] Executing scheduled routine tasks

[1595] Step 1:

[1596] The server reads the schedule information for regular tasks set by the system administrator.

[1597] Step 2:

[1598] The server will automatically launch the backup process at the specified time.

[1599] Step 3:

[1600] The server executes the backup operation and stores the created backup data.

[1601] Step 4:

[1602] The server generates and stores a log of the backup operation.

[1603] Step 5:

[1604] The terminal notifies the user that the backup is complete.

[1605] Step 6:

[1606] Users can view the status of their backups on the dashboard.

[1607] Notification and response to non-routine operations

[1608] Step 1:

[1609] A user requests a non-routine task, such as installing an emergency patch.

[1610] Step 2:

[1611] The terminal sends the request to the server.

[1612] Step 3:

[1613] The server analyzes the request and determines how to handle it.

[1614] Step 4:

[1615] The server prepares the necessary resources and executes the non-routine tasks.

[1616] Step 5:

[1617] The server generates and stores logs as work is completed.

[1618] Step 6:

[1619] The terminal notifies the user that the task is complete.

[1620] Step 7:

[1621] The user checks the results of the work and provides feedback if necessary.

[1622] Automatic processing of requested work

[1623] Step 1:

[1624] A user requests the system to create a new account.

[1625] Step 2:

[1626] The terminal sends a request to the server.

[1627] Step 3:

[1628] The server analyzes the request and executes the necessary program.

[1629] Step 4:

[1630] The server will automatically create a new account.

[1631] Step 5:

[1632] The server stores the results of the account creation and generates a notification.

[1633] Step 6:

[1634] The terminal notifies the user that the account creation is complete.

[1635] Step 7:

[1636] The user confirms that the new account was created successfully.

[1637] Conducting an account inventory

[1638] Step 1:

[1639] The server periodically collects all account information in the system.

[1640] Step 2:

[1641] The server analyzes the account usage history and identifies unnecessary accounts.

[1642] Step 3:

[1643] The server generates a report of the inventory results.

[1644] Step 4:

[1645] The terminal displays the inventory results to the user.

[1646] Step 5:

[1647] The user instructs the deletion of unnecessary accounts.

[1648] Step 6:

[1649] The server deletes unnecessary accounts according to the user's instructions.

[1650] Step 7:

[1651] The server generates and stores a log of the deletion activity.

[1652] Step 8:

[1653] The terminal notifies the user that the deletion process is complete.

[1654] Step 9:

[1655] The user confirms that the inventory work is complete.

[1656] Automated Incident Response

[1657] Step 1:

[1658] The server monitors the system status in real time.

[1659] Step 2:

[1660] The server issues an alert when it detects an anomaly.

[1661] Step 3:

[1662] The server initiates automated response procedures and analyzes the problem.

[1663] Step 4:

[1664] The server will initiate the repair process if an automatic repair is possible.

[1665] Step 5:

[1666] If the server is unable to repair the problem, it will escalate it to the appropriate person.

[1667] Step 6:

[1668] The terminal notifies the user of the occurrence of an incident and the status of the response.

[1669] Step 7:

[1670] The user may check the response status and issue additional instructions.

[1671] Step 8:

[1672] The server generates a log when an incident is resolved and records the response history.

[1673] Step 9:

[1674] The terminal notifies the user that the incident response has been completed.

[1675] Step 10:

[1676] The user checks the incident response results.

[1677] Template-based initial configuration

[1678] Step 1:

[1679] The user requests the initial setup of a new system.

[1680] Step 2:

[1681] The terminal sends a request to the server.

[1682] Step 3:

[1683] The server parses the initialization procedure based on the template.

[1684] Step 4:

[1685] The server prepares the necessary resources and begins the initialization.

[1686] Step 5:

[1687] Once the configuration process is complete, the server records and saves the results in a log.

[1688] Step 6:

[1689] The terminal notifies the user that the initial settings are complete.

[1690] Step 7:

[1691] The user checks whether the initial settings have been performed correctly.

[1692] Maintenance schedule management

[1693] Step 1:

[1694] The server manages the maintenance schedule for the system.

[1695] Step 2:

[1696] The server automatically assigns maintenance personnel according to a schedule.

[1697] Step 3:

[1698] The terminal notifies the relevant personnel of the maintenance schedule.

[1699] Step 4:

[1700] The user checks the notification content and makes a request to adjust the schedule as necessary.

[1701] Step 5:

[1702] The server generates and stores a log when maintenance work is completed.

[1703] Step 6:

[1704] The terminal notifies the user that the maintenance work has been completed.

[1705] Step 7:

[1706] The user checks the maintenance results and provides necessary feedback.

[1707] Performance data collection and analysis

[1708] Step 1:

[1709] The server collects system performance data in real time.

[1710] Step 2:

[1711] The server analyzes the collected data to identify performance trends.

[1712] Step 3:

[1713] If the server detects an abnormal value, it issues an alert.

[1714] Step 4:

[1715] The terminal visualizes performance data and analysis results (e.g., graphs).

[1716] Step 5:

[1717] The user instructs system adjustments based on the visualized data.

[1718] Step 6:

[1719] The server follows the user's instructions and performs the necessary adjustments.

[1720] Step 7:

[1721] The terminal notifies the user of the adjustment result.

[1722] Step 8:

[1723] The user checks whether the adjustment was made correctly.

[1724] Automating release tasks

[1725] Step 1:

[1726] Users register new releases and changes in the system.

[1727] Step 2:

[1728] The terminal transmits the registration details to the server.

[1729] Step 3:

[1730] The server analyzes the release procedure and sets a schedule.

[1731] Step 4:

[1732] The server will automatically start the release process at the set time.

[1733] Step 5:

[1734] The server logs and stores the results once the work is complete.

[1735] Step 6:

[1736] The terminal notifies the user of the completion of the release work.

[1737] Step 7:

[1738] The user may check the release results and perform additional verification work.

[1739] Chatbot for inquiries

[1740] Step 1:

[1741] A user registers a query with the system.

[1742] Step 2:

[1743] The terminal transmits the inquiry to the server.

[1744] Step 3:

[1745] The server uses an AI chatbot to analyze the query and generate an appropriate answer.

[1746] Step 4:

[1747] The terminal displays the chatbot's response to the user.

[1748] Step 5:

[1749] The user checks the response and makes another inquiry if the problem is not resolved.

[1750] Step 6:

[1751] The server will notify the responsible party if escalation is required.

[1752] Step 7:

[1753] The terminal notifies the user of the progress of the escalation.

[1754] Step 8:

[1755] The user confirms the escalation result.

[1756] Automated contract management

[1757] Step 1:

[1758] The server collects the contract data and inputs it into the management system.

[1759] Step 2:

[1760] The server monitors contract expiration and renewal timing and sets alerts.

[1761] Step 3:

[1762] The server will alert you when updates or purchases are required.

[1763] Step 4:

[1764] The terminal displays the contract status and alerts to the user.

[1765] Step 5:

[1766] The user checks the alerts and carries out the necessary renewal and purchase procedures.

[1767] Step 6:

[1768] The server records the details of the procedure and saves the updated contract information.

[1769] Step 7:

[1770] The terminal notifies the user that the contract renewal has been completed.

[1771] Step 8:

[1772] The user rechecks the contract information and makes corrections if necessary.

[1773] Streamlined budget management

[1774] Step 1:

[1775] The server collects cost data related to system operation.

[1776] Step 2:

[1777] The server analyzes the collected data and visualizes the budget usage status.

[1778] Step 3:

[1779] The server issues an alert if it detects an abnormal risk of exceeding the budget.

[1780] Step 4:

[1781] The terminal displays budget usage and alerts to the user.

[1782] Step 5:

[1783] The user checks the budget situation and indicates any necessary adjustments.

[1784] Step 6:

[1785] The server reallocates the budget based on the adjustment instructions.

[1786] Step 7:

[1787] The terminal notifies the user that the adjustment is complete.

[1788] Step 8:

[1789] The user checks whether the budget has been managed correctly.

[1790] The above is a detailed explanation of the program processing for each business operation, broken down into specific steps. By describing the processing in detail step by step like this, you can clearly understand how each process progresses.

[1791] Example 1

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

[1793] Modern information systems require a wide range of operations and numerous management tasks, making manual management and maintenance extremely complex and time-consuming. Furthermore, when an emergency response is required or when there are numerous user inquiries, the absence of an automated response system can easily lead to a decline in operational efficiency. Furthermore, with multiple important tasks such as system performance, account management, and backup work, there is a high risk of incorrect operation or delayed response. To address these issues, a solution that can automate system operations and efficiently manage them is needed.

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

[1795] In this invention, the server includes means for automatically executing scheduled routine tasks, means for notifying non-routine tasks and manually or automatically responding to them, means for accepting and executing user-requested tasks, means for conducting an account inventory and identifying unnecessary accounts, means for monitoring the system status and automatically responding when an incident occurs, means for initializing the system based on a template, means for managing maintenance schedules and coordinating maintenance personnel, means for collecting and analyzing system performance data in real time, means for automating the release of new software and changes, means for automatically responding to user inquiries, means for automatically managing and updating contracts, means for managing budget usage and detecting abnormal budget overrun risks, means for analyzing request content and executing appropriate response procedures, means for initiating a backup process and saving data, means for automatically creating new accounts, means for identifying and deleting unused accounts, means for performing initial configuration using a template, means for detecting abnormalities and issuing alerts, and means for escalating to a responsible person when automatic repair is not possible. This improves the reliability and efficiency of system operation, and by automating business processes, reduces human error and enables timely responses.

[1796] A "scheduled routine task" is a task that is automatically executed at a set time or timing on a daily, weekly, or monthly basis.

[1797] "Non-routine work" refers to work that arises suddenly or that requires an emergency response, and is not included in the regular schedule.

[1798] A "user-requested task" is a task that a system user requests the system to perform based on a specific request.

[1799] "Account inventory" means periodically checking the usage status of all accounts and identifying and managing unused or unnecessary accounts.

[1800] An "incident" refers to the occurrence of an abnormal condition or problem in a system, which may disrupt normal operation.

[1801] "Template-based system initialization" is the process of automatically configuring a new system according to a predefined configuration template.

[1802] "Maintenance work schedule management" refers to setting a schedule for planning and carrying out system maintenance work and managing its progress.

[1803] "Performance data" refers to various data relating to the operating status and performance of a system, and is collected in real time.

[1804] "Release automation" is the process of automating new software releases and configuration changes.

[1805] "Automatic response to inquiries" is a mechanism in which the system automatically provides answers to inquiries from users.

[1806] "Contract management and renewal" means that the system monitors contract information and automatically manages renewal dates and deadlines.

[1807] "Budget usage management" refers to the real-time monitoring of expenses related to system operation and the detection and management of abnormal budget consumption.

[1808] "Analysis of request content" refers to analyzing a request from a user and determining an appropriate response procedure based on the content of the request.

[1809] "Initiating a backup process" refers to the execution of a backup operation for the purpose of safely storing data.

[1810] "Automatic account creation" refers to the automatic generation of a new account based on a user request.

[1811] "Identifying unused accounts" refers to identifying and managing accounts that have not been used for a certain period of time.

[1812] "Anomaly detection" means monitoring the state of a system and discovering abnormalities or errors that are out of the ordinary.

[1813] "Issuing an alert" means sending a notification when an abnormality is detected and warning the user or administrator.

[1814] "Automatic remediation escalation" means handing over an issue to the appropriate personnel when automatic remediation is not possible.

[1815] The purpose of this invention is to automate and streamline a wide range of tasks in system operation. In this system, the roles of the server, terminal, and user are clearly divided, and specific programs and processing procedures are executed for each role.

[1816] Executing scheduled routine tasks

[1817] The server automatically executes regular tasks (e.g., daily backups) on a regular basis based on schedule information set by the system administrator. The hardware used is a general-purpose server, and the software used is backup software.

[1818] Specific examples

[1819] Hardware used: General server

[1820] Software used: Backup software

[1821] Example prompt:

[1822] "Perform daily backups on standard servers using backup software according to the backup schedule set by the server administrator."

[1823] Notification and response to non-routine operations

[1824] A user requests a non-routine task, such as installing an emergency patch, through a terminal. This request is sent to the server, which analyzes and executes the appropriate response.

[1825] Specific examples

[1826] Hardware used: General server

[1827] Software used: Patch management software

[1828] Example prompt:

[1829] "When a user requests the installation of an emergency patch, please apply the patch using patch management software on a standard server and notify the user when the installation is complete."

[1830] Automatic processing of requested work

[1831] A user requests the creation of a new account through a terminal, and based on this request, the server automatically creates the account using the appropriate account management tools.

[1832] Specific examples

[1833] Hardware used: General server

[1834] Software used: Account Management Tool

[1835] Example prompt:

[1836] When a new account creation request is received, please use an account management tool on a standard server to automatically create the account and notify the user.

[1837] Conducting an account inventory

[1838] The server periodically collects and analyzes the usage status of all accounts and identifies unused accounts. This information is displayed as a report on the device, and the user can instruct the deletion of unnecessary accounts.

[1839] Specific examples

[1840] Hardware used: General server

[1841] Software used: LDAP

[1842] Example prompt:

[1843] Use LDAP to periodically analyze account usage on your general servers, identify unused accounts, and generate reports.

[1844] Automated Incident Response

[1845] The server monitors the system status in real time and immediately takes action when an abnormality is detected. If automatic repair is not possible, the issue is escalated to the person in charge.

[1846] Specific examples

[1847] Hardware used: General server

[1848] Software used: Monitoring tools

[1849] Example prompt:

[1850] "Monitor the health of your systems in real time and, when anomalies are detected, auto-remediate or escalate as necessary."

[1851] Template-based initial configuration

[1852] The user selects a template and sends a request to the system, and the server performs the initial setup of the system based on the template.

[1853] Specific examples

[1854] Hardware used: General server

[1855] Software used: Configuration management tools

[1856] Example prompt:

[1857] "When a user selects a template and submits a request, please use a configuration management tool on the general server to automatically perform the initial setup and notify the progress and completion status."

[1858] Maintenance schedule management

[1859] The server manages the maintenance schedule and coordinates the maintenance personnel. When the maintenance work is completed, it records the results in a log and notifies the user.

[1860] Specific examples

[1861] Hardware used: General server

[1862] Software used: Schedule management software

[1863] Example prompt:

[1864] "Manage maintenance schedules and notify personnel and users before and after maintenance work."

[1865] Performance data collection and analysis

[1866] The server collects and analyzes system performance data in real time and issues an alert if it detects any abnormal values.

[1867] Specific examples

[1868] Hardware used: General server

[1869] Software used: Performance monitoring tool

[1870] Example prompt:

[1871] "Collect and analyze various system performance data in real time, and issue alerts if an abnormality is detected."

[1872] Automating release tasks

[1873] Users request new software or changes, and the server automatically performs the release process.

[1874] Specific examples

[1875] Hardware used: General server

[1876] Software used: Continuous integration tools

[1877] Example prompt:

[1878] When a new software release or change is registered, use a continuous integration tool to automatically execute the release and notify us when it is complete.

[1879] Chatbot for inquiries

[1880] When a user makes a query, the device sends the details to the server, and the AI ​​chatbot generates an appropriate answer.

[1881] Specific examples

[1882] Hardware used: General server

[1883] Software used: AI chatbot

[1884] Example prompt:

[1885] "Please process user inquiries via the server using an AI chatbot, generate appropriate answers, and send them."

[1886] Automated contract management

[1887] The server monitors contract data and issues an alert when the renewal date approaches, prompting the user to take action.

[1888] Specific examples

[1889] Hardware used: General server

[1890] Software used: Contract management tool

[1891] Example prompt:

[1892] "Monitor contract data and issue alerts to notify users when renewals are approaching."

[1893] Streamlined budget management

[1894] The server collects cost data related to system operation, and if it detects an abnormal risk of exceeding the budget, the terminal notifies the user.

[1895] Specific examples

[1896] Hardware used: General server

[1897] Software used: Budgeting tools

[1898] Example prompt:

[1899] "Manage system operation-related costs and notify users if an abnormal risk of overspending is detected."

[1900] As described above, the system of the present invention automates a wide range of operational tasks, improving overall operational efficiency and reliability, thereby facilitating system management and reducing operational costs.

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

[1902] Executing scheduled routine tasks

[1903] Step 1:

[1904] The server references the configured schedule information (e.g., the time of the daily backup). The schedule information is obtained from cron jobs or scheduling software. The input is the schedule data, and the output is the backup timing information.

[1905] Specific operation:

[1906] Analyzes the cron job configuration file.

[1907] Queries the schedule database to get the backup execution time.

[1908] Step 2:

[1909] The server starts the backup process based on the acquired schedule. The software used here is a backup tool. The input is backup timing information, and the output is an instruction to start the backup process.

[1910] Specific operation:

[1911] Run the batch script "backup_tool start" from the command line.

[1912] Step 3:

[1913] The server copies the data directory to the specified backup destination. The input is the data directory and the backup destination information, and the output is the backup file.

[1914] Specific operation:

[1915] Use filesystem calls to copy the specified directory to the backup destination (e.g., using rsync or scp).

[1916] Step 4:

[1917] When the server completes the backup, it sends a notification to the user via the terminal. The input is the backup completion information, and the output is a notification message.

[1918] Specific operation:

[1919] Send notification emails using a mail server.

[1920] Display a backup completion message on the dashboard.

[1921] Notification and response to non-routine operations

[1922] Step 1:

[1923] A user requests a non-routine task (e.g., installing an emergency patch) through a terminal. The input is the request information from the user, and the output is the request data.

[1924] Specific operation:

[1925] Receive requests via web forms or APIs.

[1926] Step 2:

[1927] The server analyzes the request content. The input is the request data and the output is the analysis result.

[1928] Specific operation:

[1929] Parse the request data and extract the necessary information.

[1930] Step 3:

[1931] The server downloads and installs the necessary patches based on the analysis results. The software used is a patch management tool. The input is the analysis results and patch information, and the output is the completion of the installation.

[1932] Specific operation:

[1933] Use the CLI to run the command "patch_tool apply -patch_id".

[1934] Step 4:

[1935] When the installation is complete, the server sends a notification to the user via the terminal. The input is the installation completion information, and the output is the notification message.

[1936] Specific operation:

[1937] Send reports via email and system notifications.

[1938] Automatic processing of requested work

[1939] Step 1:

[1940] A user requests the creation of a new account through a terminal. The input is the request information from the user, and the output is the request data.

[1941] Specific operation:

[1942] Use the Web API to receive requests.

[1943] Step 2:

[1944] The server analyzes the request content. The input is the request data and the output is the analysis result.

[1945] Specific operation:

[1946] Parse the JSON format and obtain the required fields.

[1947] Step 3:

[1948] The server uses the account management tool to create a new account. The input is the parsed result, and the output is the new account information.

[1949] Specific operation:

[1950] Run the PowerShell script and use the command "New-ADUser".

[1951] Step 4:

[1952] When the account creation is completed, the server sends a notification to the user via the terminal. The input is the account creation completion information, and the output is a notification message.

[1953] Specific operation:

[1954] Notifications will be sent via email and dashboard.

[1955] Conducting an account inventory

[1956] Step 1:

[1957] The server uses LDAP to collect all account usage information: the input is an LDAP query and the output is account usage information.

[1958] Specific operation:

[1959] Run an LDAP query to get the last login time for each account.

[1960] Step 2:

[1961] The server analyzes the acquired data and identifies unused accounts. The input is account usage information, and the output is a list of unused accounts.

[1962] Specific operation:

[1963] Query the database to extract accounts that have not logged in for a specified period of time.

[1964] Step 3:

[1965] The server generates a report on unused accounts and displays it on a terminal. The input is a list of unused accounts, and the output is the report data.

[1966] Specific operation:

[1967] Use the report generator to create reports in PDF and spreadsheet formats.

[1968] Step 4:

[1969] The user instructs the deletion of unnecessary accounts based on the report, and the server executes the deletion and records the result in a log. The input is the user's instruction, and the output is the deletion completion information.

[1970] Specific operation:

[1971] Run the PowerShell script to delete the target account.

[1972] Automated Incident Response

[1973] Step 1:

[1974] The server monitors the system status in real time. The input is real-time system data, and the output is anomaly detection information.

[1975] Specific operation:

[1976] Use monitoring tools to analyze system logs.

[1977] Step 2:

[1978] When the server detects an anomaly, it immediately starts to take action. The input is the anomaly detection information, and the output is the response result information.

[1979] Specific operation:

[1980] Run the automatic repair script.

[1981] Step 3:

[1982] If automatic repair is not possible, the server escalates the issue to the person in charge. The input is the response result information, and the output is an escalation notification.

[1983] Specific operation:

[1984] Use a mail server to send escalation notifications.

[1985] Step 4:

[1986] When the incident response is completed, the server sends a notification to the user via the terminal. The input is the response completion information, and the output is a notification message.

[1987] Specific operation:

[1988] The results will be notified to the user via email or system notification.

[1989] (Application example 1)

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

[1991] There is a need to efficiently manage and automate the numerous tasks and incident responses required in factory operations, improving operational reliability and cost efficiency. Traditionally, a wide range of management tasks, such as monitoring the status of factory equipment and robots, responding when anomalies occur, and executing routine tasks, have often been performed manually, resulting in potential work delays and human error. Furthermore, insufficient notification of task progress and completion can lead to insufficient information sharing among staff, resulting in a decline in work efficiency. A system that can solve these issues is needed.

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

[1993] In this invention, the server includes a means for monitoring the status of equipment in the factory in real time and automatically responding when an abnormality is detected, a means for automatically executing routine tasks, and a means for notifying users of progress and completion, thereby making it possible to improve the efficiency and reliability of operations in factory management.

[1994] "Regular tasks" are tasks that are performed periodically at specific times or cycles.

[1995] "Non-routine work" refers to work carried out to respond to emergencies or unexpected situations.

[1996] A "requested task" is a task that is performed based on a specific request from a user.

[1997] "Account inventory" is the process of checking the usage status of registered accounts and identifying and deleting unnecessary accounts.

[1998] An "incident" is an abnormality or failure that occurs during the operation of a system or equipment.

[1999] A "template" is a set of predefined procedures used to efficiently perform a particular task or setting.

[2000] "Maintenance work" refers to the maintenance work carried out to maintain the normal operation of systems and equipment.

[2001] "Performance data" refers to data that indicates the operational status of a system or device, and includes, for example, availability rate and response time.

[2002] "Release work" refers to the work of introducing new software or updating existing software.

[2003] "Inquiry response" refers to the task of providing a response to a question or request from a user.

[2004] "Contract management" refers to the task of managing contract contents and deadlines, and carrying out renewal procedures and confirmations.

[2005] "Budget usage status" is data that indicates the status of expenses related to system operation.

[2006] "Real-time monitoring" means constantly monitoring the status of systems and equipment and instantly detecting abnormalities.

[2007] "Escalation" is a procedure for notifying the person in charge or a higher-level manager when a problem occurs and urging them to take action.

[2008] This invention is a system aimed at automating and streamlining factory operations. This system is comprised of multiple pieces of hardware and software, centered around a server, and is accessible to users via smartphones or head-mounted displays (HMDs).

[2009] The server automatically executes scheduled routine tasks and performs regular backups and system updates, preventing human error and improving operational reliability.

[2010] The system also monitors incidents in real time, responds immediately if an abnormality is detected, and automatically escalates the incident and notifies the responsible person if it is difficult to handle.

[2011] Furthermore, the server analyzes user requests and automatically initiates tasks such as creating a new account or starting a specific work process, thereby improving response speed and user convenience.

[2012] Template-based system initial setup is also possible, allowing for efficient configuration of various settings required when introducing new equipment or systems. Templates contain predefined procedures, allowing for quick and reliable initial setup.

[2013] It also manages the schedule for maintenance work and notifies maintenance personnel as necessary. When the maintenance work is completed, the results are recorded in a log and the user is notified.

[2014] The system collects and analyzes performance data in real time, and if abnormal behavior is detected, it immediately issues an alert to notify the user, who can then view this data on a dashboard and make any necessary adjustments.

[2015] The application also automates release processes, making it easy to deploy new software or update existing systems. Users can monitor the progress of releases and receive notifications when they are complete.

[2016] The system uses a chatbot that uses a generative AI model to respond to inquiries, providing quick and accurate answers to user questions and escalating cases as needed.

[2017] Contract management and renewals are also automated, with users notified when deadlines approach and prompted to take necessary measures.

[2018] In addition, it also manages budget usage and notifies users if an abnormal risk of budget overrun is detected, and provides countermeasures.

[2019] As a concrete example, the following prompt sentence is used:

[2020] Template name: "New Robot Installation Settings"

[2021] 1. Enter the basic information about your robot.

[2022] 2. Select a work area.

[2023] 3. Configure the sensor settings.

[2024] 4. Conduct a test drive.

[2025] The server displays prompts via the smartphone or HMD interface, and the entire process can be carried out smoothly by the user following the procedure. This system therefore contributes greatly to improving the efficiency and reliability of factory operations.

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

[2027] Step 1:

[2028] Scheduling and executing routine tasks

[2029] The server schedules regular tasks based on the scheduling information. When the scheduled time arrives, the target task is automatically executed. Specifically, if a daily backup is required, the server automatically starts the backup process and backs up the specified data. The input is the schedule information for the regular tasks, and the output is the status indicating that the backup has been completed.

[2030] Step 2:

[2031] Real-time incident monitoring and response

[2032] The server monitors various sensors and system logs, and if an abnormality is detected, it initiates a real-time response. For example, if an abnormality in equipment performance is detected, an automatic repair process is initiated. Once the repair is complete, a notification is sent to the user. The input is data from sensors and logs, and the output is the incident response status.

[2033] Step 3:

[2034] Acceptance and execution of user-requested work

[2035] When a user requests a new task, the task request is sent to the server via the terminal. The server analyzes the request and takes appropriate action. For example, if a request is made to create a new account, the server automatically creates the account based on the required data. The input is the task request from the user, and the output is a notification that the task has been completed.

[2036] Step 4:

[2037] Template-based system initialization

[2038] The user selects a template through the terminal and requests initial setup from the system. The server automatically performs various setup procedures based on the template. For example, the setup procedure when a new robot is introduced is performed using this template. The input is the template selection and initial setup request, and the output is a notification that the setup is complete.

[2039] Step 5:

[2040] Maintenance work schedule management

[2041] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, a notification is sent to the person in charge via the terminal. When the maintenance work is completed, the results are recorded in a log and the user is notified. The input is the maintenance schedule information, and the output is a notification that the maintenance has been completed.

[2042] Step 6:

[2043] Performance data collection and analysis

[2044] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is immediately issued and the user is notified. The input is performance data, and the output is an anomaly detection alert.

[2045] Step 7:

[2046] Automating release tasks

[2047] When a user registers a new release in the system, the server analyzes the procedure and schedules it. The release process is automatically performed and a notification is sent to the user upon completion. The input is the release procedure information, and the output is a notification of release completion.

[2048] Step 8:

[2049] Inquiry response

[2050] A user's inquiry is sent to the server via the terminal. The server uses an AI chatbot to generate an appropriate response and sends it to the user. It also escalates the case as needed. The input is the user's inquiry, and the output is the response to the inquiry.

[2051] Step 9:

[2052] Automated contract management

[2053] The server monitors the contract data and notifies the user when the renewal date is approaching. Necessary renewal procedures can also be carried out automatically. The input is the contract data, and the output is a notification when renewal occurs and a notification when renewal is complete.

[2054] Step 10:

[2055] Managing budget usage

[2056] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal budget over-risk is detected, it notifies the user and provides countermeasures. The input is cost data, and the output is an alert of the budget over-risk.

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

[2058] The system of the present invention combines the automation functions of conventional operational tasks with an emotion engine that recognizes user emotions and optimizes responses. This system operates as follows, and performs various operational tasks efficiently and user-friendly.

[2059] Executing scheduled routine tasks

[2060] The server reads the schedule information for regular operations set by the system administrator. It automatically starts the backup process at the specified time and starts backing up data. When the operation is complete, a backup completion notification is sent to the user via the terminal. The user can check the backup status on the dashboard.

[2061] Notification and response to non-routine operations

[2062] A user requests a non-routine task, such as installing an emergency patch, from the system. The request is sent to the server via a terminal. Upon receiving the request, the server analyzes and executes the appropriate response procedure. Once the task is completed, a completion notification is sent to the user via the terminal.

[2063] Automatic processing of requested work

[2064] When a user requests the creation of a new account, the device sends the request to the server, which analyzes the request and executes the appropriate program to automatically create the account. The result of this operation is notified to the user via the device, and the user confirms that the new account was successfully created.

[2065] Conducting an account inventory

[2066] The server periodically collects and analyzes the usage status of all accounts. It identifies unused and unnecessary accounts and generates a report of the inventory results. This report is displayed on the terminal, and the user can instruct the server to delete unnecessary accounts. The server deletes the unnecessary accounts based on the instructions and records the results in a log.

[2067] Automated Incident Response

[2068] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, and if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[2069] Template-based initial configuration

[2070] When a new system needs initial setup, the user selects a template and sends a request to the system. The server executes the initial setup procedure based on the template. Once the setup is complete, the terminal notifies the user of the progress and completion.

[2071] Maintenance schedule management

[2072] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, the schedule is notified to the person in charge via the terminal. When the maintenance work is completed, the server records the results in a log and notifies the user.

[2073] Performance data collection and analysis

[2074] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is issued and the user is notified via their terminal. The user can check the performance analysis results on a dashboard and make any necessary adjustments.

[2075] Automating release tasks

[2076] When a user registers a new release or change in the system, the server analyzes the procedure and schedules it. The release process is carried out automatically, and the user is notified via their terminal once it is complete.

[2077] Chatbot for inquiries

[2078] When a user makes a query, the device sends the query to the server, which uses an AI chatbot to generate an appropriate response and send it to the user. If necessary, the server also escalates the query.

[2079] Automated contract management

[2080] The server monitors contract data and manages expiration dates and renewal timing. When a contract is due for renewal, it sends an alert to the user via their device, urging them to take the necessary measures.

[2081] Streamlined budget management

[2082] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal risk of budget overrun is detected, the terminal notifies the user and provides necessary countermeasures.

[2083] Introducing an emotion engine that recognizes user emotions

[2084] The system incorporates an emotion engine that recognizes the user's emotions and optimizes the response.

[2085] Example 1: Using an emotion engine in response to inquiries

[2086] When a user makes a query, the server uses an emotion engine to identify the user's emotional state based on context and linguistic analysis. For example, if the user expresses strong dissatisfaction, the emotion engine will recognize the situation and the server will be configured to escalate the query to a human agent more quickly. The tone and content of the response will also be adjusted according to the user's emotion.

[2087] Example 2: Using emotion engines in incident response

[2088] When an incident occurs, the server uses an emotion engine to analyze the user's actions and comments when checking the response status within the system, and if the user feels strong stress or anxiety, it quickly escalates the situation and provides further support.The emotion engine also has a function to send follow-up notifications after the incident is resolved based on the user's emotional data.

[2089] Example 3: Using the emotion engine in routine and non-routine notifications

[2090] In notifications sent upon the completion of routine or non-routine tasks, an emotion engine can be used to analyze the user's emotional state, and, for example, a message of encouragement can be sent to a user who is feeling tired, or a message of gratitude to a user who is feeling satisfied.

[2091] In this way, by recognizing the user's emotions and adjusting the response appropriately, it is possible to increase the satisfaction of system users and provide a better user experience.

[2092] The processing flow will be explained below.

[2093] Use of emotion engines in inquiries

[2094] Step 1:

[2095] A user enters a query into the system.

[2096] Step 2:

[2097] The terminal sends the inquiry to the server.

[2098] Step 3:

[2099] The server analyzes the query received by the emotion engine and identifies the user's emotional state (e.g., dissatisfaction, satisfaction, stress).

[2100] Step 4:

[2101] The server generates optimized responses and responses based on the results of the emotion engine.

[2102] Step 5:

[2103] If the user expresses strong dissatisfaction, the server automatically escalates the response process and notifies a human agent.

[2104] Step 6:

[2105] The terminal displays the answer to the user.

[2106] Step 7:

[2107] The user checks the response and makes another inquiry if necessary.

[2108] Using Emotion Engines in Incident Response

[2109] Step 1:

[2110] The server monitors the system status in real time and issues an alert if an abnormality is detected.

[2111] Step 2:

[2112] A user accesses the system to check the status of an incident and tries to understand the situation.

[2113] Step 3:

[2114] The server uses an emotion engine to analyze the user's actions and comments within the system.

[2115] Step 4:

[2116] The server identifies the user's emotional state (e.g., stress, anxiety) and optimizes response procedures.

[2117] Step 5:

[2118] If the user shows signs of high stress, the server automatically initiates an escalation procedure and notifies personnel.

[2119] Step 6:

[2120] After the incident is resolved, the server sends follow-up notifications taking into account the user's emotional state.

[2121] Step 7:

[2122] The device displays the notification content to the user.

[2123] Using emotion engines to inform routine and non-routine tasks

[2124] Step 1:

[2125] The server executes routine and non-routine tasks and logs the completion status.

[2126] Step 2:

[2127] The server prepares the notification content and uses an emotion engine to analyze the user's past reactions and current situation.

[2128] Step 3:

[2129] The server optimizes the notification content based on the user's emotional state (e.g., an encouraging message for a user who is feeling tired, a thank you message for a user who is feeling satisfied).

[2130] Step 4:

[2131] The terminal sends the notification content to the user.

[2132] Step 5:

[2133] The user receives a notification and checks the status.

[2134] These are the detailed steps of each process that incorporates the emotion engine, which enables the system to take the user's emotional state into consideration and provide the most appropriate response.

[2135] Example 2

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

[2137] Conventional systems individually performed tasks such as automating routine tasks, notifying and responding to non-routine tasks, account management, incident response, initial system setup, maintenance schedule management, performance data collection and analysis, release work, inquiry response, contract management, and budget management, but because they did not take user emotions into consideration, there were limitations to improving the user experience.In addition, they did not generate prompts using an emotion engine or generative AI model, making it difficult to provide flexible and individual responses.

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

[2139] In this invention, the server includes means for automatically executing scheduled routine tasks, means for notifying non-routine tasks and responding to them manually or automatically, means for accepting and executing tasks requested by users, means for conducting account inventory and identifying unnecessary accounts, means for monitoring system status and automatically responding when an incident occurs, means for initializing the system based on templates, means for managing maintenance schedules and coordinating maintenance personnel, means for collecting and analyzing system performance data in real time, means for automating the release of new software and changes, means for automatically responding to user inquiries, means for automatically managing and renewing contracts, means for managing budget usage and detecting abnormal budget overrun risks, means for recognizing user emotions and optimizing responses, means for analyzing inquiry content and supporting incident response using an emotion engine, and means for generating prompt sentences according to the user's emotional state using a generative AI model. This enables flexible and optimal system responses that take user emotions into account.

[2140] A "scheduled routine task" is a task that is automatically executed periodically according to a schedule set in advance by a system administrator.

[2141] "Non-routine tasks" are tasks that occur infrequently and are difficult to predict, such as installing emergency patches.

[2142] A "user-requested task" is a task in which a user requests a specific action from the system.

[2143] "Account inventory" is the process of periodically examining all accounts registered in the system and identifying and managing unused and unnecessary accounts.

[2144] An "incident" refers to the occurrence of an unexpected problem, such as a system abnormality or failure.

[2145] "Initial system configuration based on a template" refers to the procedure for initializing a new system or application using a pre-prepared configuration format.

[2146] "Managing maintenance work schedules" refers to planning and coordinating system maintenance work and carrying it out at the appropriate time.

[2147] "System performance data" refers to information about the operating status of the system, such as CPU usage, memory usage, and disk I / O.

[2148] "Release operations" is the process for applying new software or system changes to a production environment.

[2149] An "inquiry" refers to a question or request made by a user to the system for information or problem resolution.

[2150] "Contract management" refers to managing the content and expiration dates of contracts related to system operation, and handling matters such as renewals and cancellations.

[2151] "Budget utilization" refers to the management of costs associated with operating the system and the monitoring of planned budgets and actual expenditures.

[2152] An "emotion engine" is a system for analyzing and identifying a user's emotional state from their text and behavior.

[2153] A "generative AI model" is an artificial intelligence system that uses natural language processing and machine learning to generate appropriate prompts and responses based on the user's emotions and requests.

[2154] The system of the present invention is designed to automate a wide range of operational tasks, recognize user emotions, and optimize responses. Next, a specific method for running the program of this system will be described.

[2155] Executing scheduled routine tasks

[2156] The server reads the schedule information for regular tasks set by the system administrator. This information is obtained from a database (e.g., MySQL). When the specified time arrives, the server automatically starts the backup process. Backup software (e.g., Acronis Backup) is used to save the data to the server's storage (e.g., NAS). When the backup is complete, the server sends a completion notification to the user via their device (e.g., Windows PC or MacBook), and the user can check the backup status on a management screen (e.g., a web application).

[2157] Notification and response to non-routine operations

[2158] A user requests a non-routine task, such as installing an emergency patch, from the system. This request is sent from the terminal to the server, and communication is carried out using an HTTP request. The server receives the request, analyzes the appropriate response procedure, and executes a script. For example, an automation tool such as Ansible is used to install an emergency patch. After the task is completed, the server sends a completion notification to the user via the terminal.

[2159] Automatic processing of requested work

[2160] When a user requests the creation of a new account, the device sends the request to the server. This communication uses the HTTPS protocol, and the request data is sent in JSON format. The server receives the request and automatically creates a new account using LDAP or Active Directory. A completion notification is sent to the user via the device, and the user can view the details of the new account by email or on the system dashboard.

[2161] Conducting an account inventory

[2162] The server periodically collects usage information for all accounts from LDAP or Active Directory and analyzes it using Python scripts and data analysis libraries (e.g., Pandas, Matplotlib). It identifies unnecessary accounts and generates a report. This report is displayed on the terminal, and the user can instruct the deletion of unnecessary accounts. The server deletes the accounts based on the instructions and records the operation log in a database (e.g., MySQL).

[2163] Automated Incident Response

[2164] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, and if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[2165] Introducing an emotion engine that recognizes user emotions

[2166] This system incorporates an emotion engine that recognizes user emotions and optimizes responses. For example, it analyzes the content of inquiries and the user's actions and comments during incident response, and uses an emotion engine (e.g., IBM Watson NLU) to identify the user's emotional state.

[2167] Example: Using an emotion engine in customer inquiries

[2168] When a user makes an inquiry, the server uses an emotion engine to identify the user's emotional state. If the inquiry is "I'm having trouble using the service!", the emotion engine will emphasize the "trouble" part and quickly escalate the situation. The generative AI model uses this information to generate a prompt.

[2169] Example prompt sentence:

[2170] "If a user is having trouble using the service, escalate it quickly."

[2171] In this way, the system can provide flexible and optimal responses that take into account the user's emotions, improving the user experience.

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

[2173] Executing scheduled routine tasks

[2174] Step 1:

[2175] The server reads the schedule information for regular tasks set by the system administrator from a database (e.g., MySQL).

[2176] Input: Schedule information from the database

[2177] Output: Loaded schedule information

[2178] Specific operation: The server executes an SQL query to retrieve schedule information using a SELECT statement.

[2179] Step 2:

[2180] When the specified time arrives, the server will automatically launch the backup process.

[2181] Input: Specified time according to schedule information

[2182] Output: Backup process starts

[2183] What it does: Run Acronis Backup software using a cron job or task scheduler.

[2184] Step 3:

[2185] When the backup is complete, the server sends a completion notification to the terminal.

[2186] Input: Backup completion status

[2187] Output: Completion notification message

[2188] Specific operation: The server sends a notification email via the mail server, or sends a notification to the device using the web application API.

[2189] Notification and response to non-routine operations

[2190] Step 1:

[2191] A user requests a non-routine task, such as installing an emergency patch, from the system.

[2192] Input: Non-routine work request from user

[2193] Output: The request is sent from the terminal to the server.

[2194] Specific operation: The user enters a request through a web form or API, and the device sends this request in JSON format to the server.

[2195] Step 2:

[2196] The server receives the request, analyzes it, and determines the appropriate course of action.

[2197] Input: Non-routine work request data

[2198] Output: Action steps

[2199] What happens: The server runs a Python script, analyzes the request, and decides which tool (e.g., Ansible) to use.

[2200] Step 3:

[2201] The server performs non-routine tasks according to the determined response procedures.

[2202] Input: Response procedure

[2203] Output: Results of non-routine tasks

[2204] What it does: Runs an Ansible playbook to apply an emergency patch.

[2205] Step 4:

[2206] When the work is completed, the server sends a completion notification to the user via the terminal.

[2207] Input: Non-routine task execution completion status

[2208] Output: Completion notification

[2209] Specific operation: The server sends a notification to the user via the mail server or web application API.

[2210] Automatic processing of requested work

[2211] Step 1:

[2212] When a user requests the creation of a new account, the device sends the request to the server.

[2213] Input: Account creation request

[2214] Output: The request is sent to the server

[2215] How it works: The user enters a request through a web form or API, and the device sends it to the server using the HTTPS protocol.

[2216] Step 2:

[2217] The server receives the request, analyzes it, and creates a new account.

[2218] Input: Account creation request data

[2219] Output: Account creation status

[2220] What it does: The server runs a Python script to automatically create new accounts using LDAP or Active Directory.

[2221] Step 3:

[2222] Once the account creation is complete, the server notifies the user of the results via the terminal.

[2223] Input: Account creation completion status

[2224] Output: Completion notification

[2225] Specific operation: The server sends a notification to the user via the mail server or web application API.

[2226] Conducting an account inventory

[2227] Step 1:

[2228] The server periodically collects all account usage information from LDAP or Active Directory.

[2229] Input: Account data

[2230] Output: Collected usage data

[2231] What it does: The server runs a Python script that queries and collects account usage information from LDAP and Active Directory.

[2232] Step 2:

[2233] The server analyzes the collected data and identifies unnecessary accounts.

[2234] Input: Usage data

[2235] Output: List of unnecessary accounts

[2236] What it does: Use Python scripts and data analysis libraries (e.g., Pandas) to analyze account usage frequency and last login time.

[2237] Step 3:

[2238] The server generates a report of unnecessary accounts and displays it on the terminal.

[2239] Input: List of unnecessary accounts

[2240] Output: Report

[2241] Specific operation: Use Pandas and Matplotlib to generate analysis results in report format (e.g. PDF or HTML).

[2242] Step 4:

[2243] The user instructs the deletion of unnecessary accounts.

[2244] Input: User deletion instructions

[2245] Output: Delete instruction data

[2246] Specific operation: The user enters deletion instructions via a web form or API, and the device sends them to the server.

[2247] Step 5:

[2248] The server deletes the account based on the user's instructions and records the operation log.

[2249] Input: Data for deletion instructions

[2250] Output: Deletion completion status, operation log

[2251] Specific operation: The server deletes the account using a Python script and records the operation log in the MySQL database using an INSERT statement.

[2252] (Application example 2)

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

[2254] Conventional operational automation systems were unable to recognize the user's emotional state and respond accordingly, making it difficult to improve the user experience. Furthermore, content distribution services were unable to recommend appropriate content based on the user's emotions, resulting in a decline in user satisfaction. Technology to address this issue is needed.

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

[2256] In this invention, the server includes: means for automatically executing scheduled routine tasks; means for notifying non-routine tasks and manually or automatically responding to them; means for accepting and executing tasks requested by users; means for taking account inventories and identifying unnecessary accounts; means for monitoring the system status and automatically responding when an incident occurs; means for initializing the system based on templates; means for managing maintenance schedules and coordinating maintenance personnel; means for collecting and analyzing system performance data in real time; means for automating the release of new software and changes; means for automatically responding to inquiries from users; means for automatically managing and renewing contracts; means for managing budget usage and detecting abnormal budget overrun risks; and means for analyzing user emotions using an emotion engine that recognizes user emotions and optimizes responses, and recommending content corresponding to the user's emotional state. This makes it possible to improve the user experience by recognizing user emotions and providing optimal responses.

[2257] A "scheduled routine task" is a task that is planned in advance and executed periodically based on a preset schedule.

[2258] "Non-routine work" refers to temporary work that is not performed regularly according to a specific schedule, but occurs as needed.

[2259] A "requested work" is a specific job or task that is performed based on a request from a user.

[2260] "Account inventory" is the process of checking the usage status of all accounts and identifying unnecessary accounts.

[2261] "Monitoring the system status" means monitoring the operating status and performance of the entire system in real time.

[2262] An "incident" is an event in which a problem such as an abnormality or failure occurs in a system.

[2263] "Performing initial system settings based on a template" means automatically performing initial system settings on a new system according to a predetermined setting pattern.

[2264] "Managing maintenance work schedules" means planning and coordinating maintenance work such as system maintenance and updates, and managing the schedule.

[2265] "Collecting system performance data and analyzing it in real time" means collecting data on the system's operating status and performance and analyzing it immediately.

[2266] "Automating the release of new software and changes" means automating the introduction of new software and the modification of existing software.

[2267] "Automatically responding to inquiries from users" means that the system automatically provides appropriate answers to questions or requests submitted by users.

[2268] "Automatically managing and updating contracts" means that the system automatically checks and updates the contract contents.

[2269] "Manage budget usage and detect abnormal budget overspending risks" means monitoring how the budget is used and detecting the risk of excessive budget usage.

[2270] The "emotion engine" is an engine that analyzes the user's emotions in real time and responds optimally according to their emotional state.

[2271] "User's emotional state" refers to the type and intensity of emotion that a user is feeling at a particular point in time.

[2272] "Recommending content" means presenting optimal content that matches the user's interests and emotional state.

[2273] MODE FOR CARRYING OUT THE INVENTION

[2274] The present invention provides a system for recognizing a user's emotions and taking an optimal response accordingly. Specific embodiments will be described below.

[2275] The server manages scheduled routine tasks, automatically executing them at designated times, such as backup processes and routine maintenance tasks. The server also accepts requests for non-routine tasks and responds appropriately, such as installing emergency patches or allocating additional resources.

[2276] A user's request is sent to the server via the device, which then analyzes the request and automatically executes the corresponding procedure, such as creating a new account or updating an existing account.

[2277] The server periodically monitors account usage and identifies unnecessary accounts. This information is generated as a report and notified to the user. The user can then instruct the server to delete unnecessary accounts.

[2278] Additionally, the server monitors the system status in real time and automatically initiates a remediation process if an incident occurs, or escalates to a responsible party if it is not possible. The server also includes a means to initially configure new systems based on templates.

[2279] The server manages the maintenance schedule and notifies the maintenance personnel of the schedule. Performance data is collected and analyzed in real time, and an alert is issued if an abnormal value is detected.

[2280] When a user requests a new software release or change, the server analyzes the procedure and performs the release in an automated manner, and also automatically responds to user inquiries using an AI chatbot.

[2281] The server also automatically manages contracts and budgets. It monitors contract expirations and renewals and sends alerts to users. Budget usage is also monitored in real time, and if an abnormal risk of budget overruns is detected, a notification is sent.

[2282] Of particular note is the introduction of an emotion engine. The server uses the emotion engine to analyze the user's emotional state in real time. For example, when a user is watching content or posting a review, the server identifies the user's emotion based on context and linguistic analysis. Based on this emotional state, the server recommends the most appropriate content and notifies the user.

[2283] Hardware / Software Used

[2284] This system mainly uses the following hardware and software:

[2285] Hardware: Smartphone (Android / iOS), server

[2286] Software: Python, EmotionRecognition library, Requests library, RESTful API

[2287] Specific examples

[2288] Example 1: If a user types, "I've been very busy today, I want to relax," the emotion engine will recognize "stress" and recommend relaxing content (e.g., videos of nature scenes).

[2289] Prompt Sentence Examples

[2290] 1. Example prompt:

[2291] User input text: "Today has been very busy, I want to relax."

[2292] Process: Request emotion analysis from the emotion engine to detect "stress." Retrieve "relaxing videos" from the recommended content API and notify the user.

[2293] In this way, the present invention significantly improves the user experience by recognizing the user's emotions and automatically providing optimal content corresponding to those emotions.

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

[2295] Processing Steps

[2296] Step 1: Receiving User Input

[2297] The user enters a sentence about their feelings into a text field in the system, such as "I'm really tired today. I don't feel like doing anything." This input is collected by the device and sent to the next step.

[2298] Step 2: Sentiment Analysis

[2299] The server sends the user's text received from the device to the emotion engine. The emotion engine uses natural language processing technology to analyze the text and identify the user's emotion. The data processing performed at this time involves tokenizing the text and assigning emotion labels, resulting in emotion labels such as "stress" and "satisfaction."

[2300] Step 3: Sending emotion labels

[2301] The server retrieves the emotion labels obtained from the emotion engine and sends them to the content recommendation system. This data is sent via a RESTful API.

[2302] Step 4: Content Recommendation

[2303] The content recommendation system provides the server with the optimal content according to the emotion label. The system uses past user data and a matching algorithm to select the content that best suits the user's emotion. The data calculation involves searching for the appropriate content ID from the database using the emotion label as a key. The output is information about the recommended content.

[2304] Step 5: Notification of recommended content

[2305] The server transmits the recommended content information obtained from the content recommendation system to the terminal. The terminal receives this information and notifies the user. Specifically, it displays a notification screen and presents the recommended content to the user along with a message such as "Here is the recommended content."

[2306] Adding specific examples

[2307] For example, if a user types "I'm having a great time today," the processing steps would be:

[2308] Step 1: The device receives user input such as "I'm having a great time today."

[2309] Step 2: The server sends this sentence to the emotion engine and gets the emotion label "joy."

[2310] Step 3: The server sends the emotion label of “joy” to the content recommendation system.

[2311] Step 4: The content recommendation system recommends entertaining content suitable for "pleasure" (e.g., comedy movies).

[2312] Step 5: The server sends this content information to the terminal, which then notifies the user.

[2313] Through the above steps, the present invention can provide a content recommendation function that is adapted to the user's emotions, thereby improving the user experience.

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

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

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

[2317] [Fourth embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

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

[2331] The system of the present invention automates and streamlines a wide range of tasks in system operation, and includes various programs for this purpose. Below, we will explain in natural language how the programs in this system work, using concrete examples.

[2332] Executing scheduled routine tasks

[2333] The server automatically performs routine tasks (e.g., daily backups) based on scheduling information set by the system administrator. At the set time, the server launches the backup process and begins backing up data. When the task is complete, a notification is sent to the user via the terminal, and the backup status can be checked on the dashboard.

[2334] Notification and response to non-routine operations

[2335] Users can request non-routine tasks (e.g., installing emergency patches) from the system. The request is sent to the server via the terminal. When the server receives the request, it analyzes and executes the appropriate response procedure. Once the response is completed, a completion notification is sent to the user via the terminal.

[2336] Automatic processing of requested work

[2337] When a user requests the creation of a new account, the device sends the request to the server, which analyzes the request and executes the appropriate program to automatically create the account. The result of this operation is notified to the user via the device, and the user confirms that the new account was successfully created.

[2338] Conducting an account inventory

[2339] The server periodically collects and analyzes the usage status of all accounts. It identifies unused and unnecessary accounts and generates a report of the inventory results. This report is displayed on the terminal, and the user can instruct the server to delete unnecessary accounts. The server deletes the unnecessary accounts based on the instructions and records the results in a log.

[2340] Automated Incident Response

[2341] The server monitors the system status in real time and immediately initiates a response if an abnormality is detected. If automatic repair is possible, a repair process is initiated, but if not, the issue is escalated to the appropriate person. Once the incident response is complete, the user is notified of the results via their terminal.

[2342] Template-based initial configuration

[2343] When a new system needs initial setup, the user selects a template and sends a request to the system. The server executes the initial setup procedure based on the template. Once the setup is complete, the terminal notifies the user of the progress and completion.

[2344] Maintenance schedule management

[2345] The server manages the maintenance schedule and coordinates the maintenance personnel. When maintenance is scheduled, the schedule is notified to the person in charge via the terminal. When the maintenance work is completed, the server records the results in a log and notifies the user.

[2346] Performance data collection and analysis

[2347] The server collects and analyzes system performance data in real time. If an abnormal value is detected, an alert is issued and the user is notified via their terminal. The user can check the performance analysis results on a dashboard and make any necessary adjustments.

[2348] Automating release tasks

[2349] When a user registers a new release or change in the system, the server analyzes the procedure and schedules it. The release process is carried out automatically, and the user is notified via their terminal once it is complete.

[2350] Chatbot for inquiries

[2351] When a user makes a query, the device sends the query to the server, which uses an AI chatbot to generate an appropriate response and send it to the user. If necessary, the server also escalates the query.

[2352] Automated contract management

[2353] The server monitors contract data and manages expiration dates and renewal timing. When a contract is due for renewal, it sends an alert to the user via their device, urging them to take the necessary measures.

[2354] Streamlined budget management

[2355] The server collects cost data related to system operation and manages budget usage in real time. If an abnormal risk of budget overrun is detected, the terminal notifies the user and provides necessary countermeasures.

[2356] As described above, the system of the present invention can automate and streamline a wide range of operational tasks, significantly improving the reliability and cost efficiency of system operation.

[2357] The processing flow will be explained below.

[2358] Executing scheduled routine tasks

[2359] Step 1:

[2360] The server reads the schedule information for regular tasks set by the system administrator.

[2361] Step 2:

[2362] The server will automatically launch the backup process at the specified time.

[2363] Step 3:

[2364] The server executes the backup operation and stores the created backup data.

[2365] Step 4:

[2366] The server generates and stores a log of the backup operation.

[2367] Step 5:

[2368] The terminal notifies the user that the backup is complete.

[2369] Step 6:

[2370] Users can view the status of their backups on the dashboard.

[2371] Notification and response to non-routine operations

[2372] Step 1:

[2373] A user requests a non-routine task, such as installing an emergency patch.

[2374] Step 2:

[2375] The terminal sends the request to the server.

[2376] Step 3:

[2377] The server analyzes the request and determines how to handle it.

[2378] Step 4:

[2379] The server prepares the necessary resources and executes the non-routine tasks.

[2380] Step 5:

[2381] The server generates and stores logs as work is completed.

[2382] Step 6:

[2383] The terminal notifies the user that the task is complete.

[2384] Step 7:

[2385] The user checks the results of the work and provides feedback if necessary.

[2386] Automatic processing of requested work

[2387] Step 1:

[2388] A user requests the system to create a new account.

[2389] Step 2:

[2390] The terminal sends a request to the server.

[2391] Step 3:

[2392] The server analyzes the request and executes the necessary program.

[2393] Step 4:

[2394] The server will automatically create a new account.

[2395] Step 5:

[2396] The server stores the results of the account creation and generates a notification.

[2397] Step 6:

[2398] The terminal notifies the user that the account creation is complete.

[2399] Step 7:

[2400] The user confirms that the new account was created successfully.

[2401] Conducting an account inventory

[2402] Step 1:

[2403] The server periodically collects all account information in the system.

[2404] Step 2:

[2405] The server analyzes the account usage history and identifies unnecessary accounts.

[2406] Step 3:

[2407] The server generates a report of the inventory results.

[2408] Step 4:

[2409] The terminal displays the inventory results to the user.

[2410] Step 5:

[2411] The user instructs the deletion of unnecessary accounts.

[2412] Step 6:

[2413] The server deletes unnecessary accounts according to the user's instructions.

[2414] Step 7:

[2415] The server generates and stores a log of the deletion activity.

[2416] Step 8:

[2417] The terminal notifies the user that the deletion process is complete.

[2418] Step 9:

[2419] The user confirms that the inventory work is complete.

[2420] Automated Incident Response

[2421] Step 1:

[2422] The server monitors the system status in real time.

[2423] Step 2:

[2424] The server issues an alert when it detects an anomaly.

[2425] Step 3:

[2426] The server initiates automated response procedures and analyzes the problem.

[2427] Step 4:

[2428] The server will initiate the repair process if an automatic repair is possible.

[2429] Step 5:

[2430] If the server is unable to repair the problem, it will escalate it to the appropriate person.

[2431] Step 6:

[2432] The terminal notifies the user of the occurrence of an incident and the status of the response.

[2433] Step 7:

[2434] The user may check the response status and issue additional instructions.

[2435] Step 8:

[2436] The server generates a log when an incident is resolved and records the response history.

[2437] Step 9:

[2438] The terminal notifies the user that the incident response has been completed.

[2439] Step 10:

[2440] The user checks the incident response results.

[2441] Template-based initial configuration

[2442] Step 1:

[2443] The user requests the initial setup of a new system.

[2444] Step 2:

[2445] The terminal sends a request to the server.

[2446] Step 3:

[2447] The server parses the initialization procedure based on the template.

[2448] Step 4:

[2449] The server prepares the necessary resources and begins the initialization.

[2450] Step 5:

[2451] Once the configuration process is complete, the server records and saves the results in a log.

[2452] Step 6:

[2453] The terminal notifies the user that the initial settings are complete.

[2454] Step 7:

[2455] The user checks whether the initial settings have been performed correctly.

[2456] Maintenance schedule management

[2457] Step 1:

[2458] The server manages the maintenance schedule for the system.

[2459] Step 2:

[2460] The server automatically assigns maintenance personnel according to a schedule.

[2461] Step 3:

[2462] The terminal notifies the relevant personnel of the maintenance schedule.

[2463] Step 4:

[2464] The user checks the notification content and makes a request to adjust the schedule as necessary.

[2465] Step 5:

[2466] The server generates and stores a log when maintenance work is completed.

[2467] Step 6:

[2468] The terminal notifies the user that the maintenance work has been completed.

[2469] Step 7:

[2470] The user checks the maintenance results and provides necessary feedback.

[2471] Performance data collection and analysis

[2472] Step 1:

[2473] The server collects system performance data in real time.

[2474] Step 2:

[2475] The server analyzes the collected data to identify performance trends.

[2476] Step 3:

[2477] If the server detects an abnormal value, it issues an alert.

[2478] Step 4:

[2479] The terminal visualizes performance data and analysis results (e.g., graphs).

[2480] Step 5:

[2481] The user instructs system adjustments based on the visualized data.

[2482] Step 6:

[2483] The server follows the user's instructions and performs the necessary adjustments.

[2484] Step 7:

[2485] The terminal notifies the user of the adjustment result.

[2486] Step 8:

[2487] The user checks whether the adjustment was made correctly.

[2488] Automating release tasks

[2489] Step 1:

[2490] Users register new releases and changes in the system.

[2491] Step 2:

[2492] The terminal transmits the registration details to the server.

[2493] Step 3:

[2494] The server analyzes the release procedure and sets a schedule.

[2495] Step 4:

[2496] The server will automatically start the release process at the set time.

[2497] Step 5:

[2498] The server logs and stores the results once the work is complete.

[2499] Step 6:

[2500] The terminal notifies the user of the completion of the release work.

[2501] Step 7:

[2502] The user may check the release results and perform additional verification work.

[2503] Chatbot for inquiries

[2504] Step 1:

[2505] A user registers a query with the system.

[2506] Step 2:

[2507] The terminal transmits the inquiry to the server.

[2508] Step 3:

[2509] The server uses an AI chatbot to analyze the query and generate an appropriate answer.

[2510] Step 4:

[2511] The terminal displays the chatbot's response to the user.

[2512] Step 5:

[2513] The user checks the response and makes another inquiry if the problem is not resolved.

[2514] Step 6:

[2515] The server will notify the responsible party if escalation is required.

[2516] Step 7:

[2517] The terminal notifies the user of the progress of the escalation.

[2518] Step 8:

[2519] The user confirms the escalation result.

[2520] Automated contract management

[2521] Step 1:

[2522] The server collects the contract data and inputs it into the management system.

[2523] Step 2:

[2524] The server monitors contract expiration and renewal timing and sets alerts.

[2525] Step 3:

[2526] The server will alert you when updates or purchases are required.

[2527] Step 4:

[2528] The terminal displays the contract status and alerts to the user.

[2529] Step 5:

[2530] The user checks the alerts and carries out the necessary renewal and purchase procedures.

[2531] Step 6:

[2532] The server records the details of the procedure and saves the updated contract information.

[2533] Step 7:

[2534] The terminal notifies the user that the contract renewal has been completed.

[2535] Step 8:

[2536] The user rechecks the contract information and makes corrections if necessary.

[2537] Streamlined budget management

[2538] Step 1:

[2539] The server collects cost data related to system operation.

[2540] Step 2:

[2541] The server analyzes the collected data and visualizes the budget usage status.

[2542] Step 3:

[2543] The server issues an alert if it detects an abnormal risk of exceeding the budget.

[2544] Step 4:

[2545] The terminal displays budget usage and alerts to the user.

[2546] Step 5:

[2547] The user checks the budget situation and indicates any necessary adjustments.

[2548] Step 6:

[2549] The server reallocates the budget based on the adjustment instructions.

[2550] Step 7:

[2551] The terminal notifies the user that the adjustment is complete.

[2552] Step 8:

[2553] The user checks whether the budget has been managed correctly.

[2554] The above is a detailed explanation of the program processing for each business operation, broken down into specific steps. By describing the processing in detail step by step like this, you can clearly understand how each process progresses.

[2555] Example 1

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

[2557] Modern information systems require a wide range of operations and numerous management tasks, making manual management and maintenance extremely complex and time-consuming. Furthermore, when an emergency response is required or when there are numerous user inquiries, the absence of an automated response system can easily lead to a decline in operational efficiency. Furthermore, with multiple important tasks such as system performance, account management, and backup work, there is a high risk of incorrect operation or delayed response. To address these issues, a solution that can automate system operations and efficiently manage them is needed.

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

[2559] In this invention, the server includes means for automatically executing scheduled routine tasks, means for notifying non-routine tasks and manually or automatically responding to them, means for accepting and executing user-requested tasks, means for conducting an account inventory and identifying unnecessary accounts, means for monitoring the system status and automatically responding when an incident occurs, means for initializing the system based on a template, means for managing maintenance schedules and coordinating maintenance personnel, means for collecting and analyzing system performance data in real time, means for automating the release of new software and changes, means for automatically responding to user inquiries, means for automatically managing and updating contracts, means for managing budget usage and detecting abnormal budget overrun risks, means for analyzing request content and executing appropriate response procedures, means for initiating a backup process and saving data, means for automatically creating new accounts, means for identifying and deleting unused accounts, means for performing initial configuration using a template, means for detecting abnormalities and issuing alerts, and means for escalating to a responsible person when automatic repair is not possible. This improves the reliability and efficiency of system operation, and by automating business processes, reduces human error and enables timely responses.

[2560] A "scheduled routine task" is a task that is automatically executed at a set time or timing on a daily, weekly, or monthly basis.

[2561] "Non-routine work" refers to work that arises suddenly or that requires an emergency response, and is not included in the regular schedule.

[2562] A "user-requested task" is a task that a system user requests the system to perform based on a specific request.

[2563] "Account inventory" means periodically checking the usage status of all accounts and identifying and managing unused or unnecessary accounts.

[2564] An "incident" refers to the occurrence of an abnormal condition or problem in a system, which may disrupt normal operation.

[2565] "Template-based system initialization" is the process of automatically configuring a new system according to a predefined configuration template.

[2566] "Maintenance work schedule management" refers to setting a schedule for planning and carrying out system maintenance work and managing its progress.

[2567] "Performance data" refers to various data relating to the operating status and performance of a system, and is collected in real time.

[2568] "Release automation" is the process of automating new software releases and configuration changes.

[2569] "Automatic response to inquiries" is a mechanism in which the system automatically provides answers to inquiries from users.

[2570] "Contract management and renewal" means that the system monitors contract information and automatically manages renewal dates and deadlines.

[2571] "Budget usage management" refers to the real-time monitoring of expenses related to system operation and the detection and management of abnormal budget consumption.

[2572] "Analysis of request content" refers to analyzing a request from a user and determining an appropriate response procedure based on the content of the request.

[2573] "Initiating a backup process" refers to the execution of a backup operation for the purpose of safely storing data.

[2574] "Automatic account creation" refers to the automatic generation of a new account based on a user request.

[2575] "Identifying unused accounts" refers to identifying and managing accounts that have not been used for a certain period of time.

[2576] "Anomaly detection" means monitoring the state of a system and discovering abnormalities or errors that are out of the ordinary.

[2577] "Issuing an alert" means sending a notification when an abnormality is detected and warning the user or administrator.

[2578] "Automatic remediation escalation" means handing over an issue to the appropriate personnel when automatic remediation is not possible.

[2579] The purpose of this invention is to automate and streamline a wide range of tasks in system operation. In this system, the roles of the server, terminal, and user are clearly divided, and specific programs and processing procedures are executed for each role.

[2580] Executing scheduled routine tasks

[2581] The server automatically executes regular tasks (e.g., daily backups) on a regular basis based on schedule information set by the system administrator. The hardware used is a general-purpose server, and the software used is backup software.

[2582] Specific examples

[2583] Hardware used: General server

[2584] Software used: Backup software

[2585] Example prompt:

[2586] "Perform daily backups on standard servers using backup software according to the backup schedule set by the server administrator."

[2587] Notification and response to non-routine operations

[2588] A user requests a non-routine task, such as installing an emergency patch, through a terminal. This request is sent to the server, which analyzes and executes the appropriate response.

[2589] Specific examples

[2590] Hardware used: General server

[2591] Software used: Patch management software

[2592] Example prompt:

[2593] "When a user requests the installation of an emergency patch, please apply the patch using patch management software on a standard server and notify the user when the installation is complete."

[2594] Automatic processing of requested work

[2595] A user requests the creation of a new account through a terminal, and based on this request, the server automatically creates the account using the appropriate account management tools.

[2596] Specific examples

[2597] Hardware used: General server

[2598] Software used: Account Management Tool

[2599] Example prompt:

[2600] When a new account creation request is received, please use an account management tool on a standard server to automatically create the account and notify the user.

[2601] Conducting an account inventory

[2602] The server periodically collects and analyzes the usage status of all accounts and identifies unused accounts. This information is displayed as a report on the device, and the user can instruct the deletion of unnecessary accounts.

[2603] Specific examples

[2604] Hardware used: General server

[2605] Software used: LDAP

[2606] Example prompt:

[2607] Use LDAP to periodically analyze account usage on your general servers, identify unused accounts, and generate reports.

[2608] Automated Incident Response

[2609] The server monitors the system status in real time and immediately takes action when an abnormality is detected. If automatic repair is not possible, the issue is escalated to the person in charge.

[2610] Specific examples

[2611] Hardware used: General server

[2612] Software used: Monitoring tools

[2613] Example prompt:

[2614] "Monitor the health of your systems in real time and, when anomalies are detected, auto-remediate or escalate as necessary."

[2615] Template-based initial configuration

[2616] The user selects a template and sends a request to the system, and the server performs the initial setup of the system based on the template.

[2617] Specific examples

[2618] Hardware used: General server

[2619] Software used: Configuration management tools

[2620] Example prompt:

[2621] "When a user selects a template and submits a request, please use a configuration management tool on the general server to automatically perform the initial setup and notify the progress and completion status."

[2622] Maintenance schedule management

[2623] The server manages the maintenance schedule and coordinates the maintenance personnel. When the maintenance work is completed, it records the results in a log and notifies the user.

[2624] Specific examples

[2625] Hardware used: General server

[2626] Software used: Schedule management software

[2627] Example prompt:

[2628] "Manage maintenance schedules and notify personnel and users before and after maintenance work."

[2629] Performance data collection and analysis

[2630] The server collects and analyzes system performance data in real time and issues an alert if it detects any abnormal values.

[2631] Specific examples

[2632] Hardware used: General server

[2633] Software used: Performance monitoring tool

[2634] Example prompt:

[2635] "Collect and analyze various system performance data in real time, and issue alerts if an abnormality is detected."

[2636] Automating release tasks

[2637] Users request new software or changes, and the server automatically performs the release process.

[2638] Specific examples

[2639] Hardware used: General server

[2640] Software used: Continuous integration tools

[2641] Example prompt:

[2642] When a new software release or change is registered, use a continuous integration tool to automatically execute the release and notify us when it is complete.

[2643] Chatbot for inquiries

[2644] When a user makes a query, the device sends the details to the server, and the AI ​​chatbot generates an appropriate answer.

[2645] Specific examples

[2646] Hardware used: General server

[2647] Software used: AI chatbot

[2648] Example prompt:

[2649] "Please process user inquiries via the server using an AI chatbot, generate appropriate answers, and send them."

[2650] Automated contract management

[2651] The server monitors contract data and issues an alert when the renewal date approaches, prompting the user to take action.

[2652] Specific examples

[2653] Hardware used: General server

[2654] Software used: Contract management tool

[2655] Example prompt:

[2656] "Monitor contract data and issue alerts to notify users when renewals are approaching."

[2657] Streamlined budget management

[2658] The server collects cost data related to system operation, and if it detects an abnormal risk of exceeding the budget, the terminal notifies the user.

[2659] Specific examples

[2660] Hardware used: General server

[2661] Software used: Budgeting tools

[2662] Example prompt:

[2663] "Manage system operation-related costs and notify users if an abnormal risk of overspending is detected."

[2664] As described above, the system of the present invention automates a wide range of operational tasks, improving overall operational efficiency and reliability, thereby facilitating system management and reducing operational costs.

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

[2666] Executing scheduled routine tasks

[2667] Step 1:

[2668] The server references the configured schedule information (e.g., the time of the daily backup). The schedule information is obtained from cron jobs or scheduling software. The input is the schedule data, and the output is the backup timing information.

[2669] Specific operation:

[2670] Analyzes the cron job configuration file.

[2671] Queries the schedule database to get the backup execution time.

[2672] Step 2:

[2673] The server starts the backup process based on the acquired schedule. The software used here is a backup tool. The input is backup timing information, and the output is an instruction to start the backup process.

[2674] Specific operation:

[2675] Run the batch script "backup_tool start" from the command line.

[2676] Step 3:

[2677] The server copies the data directory to the specified backup destination. The input is the data directory and the backup destination information, and the output is the backup file.

[2678] Specific operation:

[2679] Use filesystem calls to copy the specified directory to the backup destination (e.g., using rsync or scp).

[2680] Step 4:

[2681] When the server completes the backup, it sends a notification to the user via the terminal. The input is the backup completion information, and the output is a notification message.

[2682] Specific operation:

[2683] Send notification emails using a mail server.

[2684] Display a backup completion message on the dashboard.

[2685] Notification and response to non-routine operations

[2686] Step 1:

[2687] A user requests a non-routine task (e.g., installing an emergency patch) through a terminal. The input is the request information from the user, and the output is the request data.

[2688] Specific operation:

[2689] ...

Claims

1. means for automatically executing scheduled routine tasks; A means of notifying and manually or automatically responding to non-routine activities; A means for accepting and executing a task requested by a user; A means of conducting an account inventory and identifying unnecessary accounts; A means of monitoring the system status and automatically responding when an incident occurs; means for initializing the system based on a template; a means for managing the schedule of maintenance work and coordinating maintenance personnel; A means of collecting and analyzing system performance data in real time; A means to automate the process of releasing new software or changes, and a means for automatically responding to user inquiries; an automated means of managing and renewing contracts; Manage budget usage and detect abnormal budget overrun risks. A system including:

2. 10. The system of claim 1, further comprising means for notifying a user when a scheduled routine is performed.

3. The system according to claim 1 , further comprising means for escalating an incident to a responsible person if the incident cannot be repaired during the incident response.

Images