JP2023025792A - Information processing program, information processing method, and information processing device - Google Patents

Abstract

To acquire information for allowing detection of specification change of an operation object at non-execution time of an RPA robot.SOLUTION: An RPA robot 11 automatically executes operation with respect to an operation object 4. A processing unit 20 of an information processing device 2 executes operation processing which executes at least a part of the operation which the RPA robot 11 executes with respect to the operation object 4, during a time zone when the RPA robot 11 is not executed. In the operation processing, the processing unit 20, when an execution error of the operation with respect to the operation object 4 occurs, collects error information indicating contents of the execution error, and transmits the collected error information to a predetermined transmission destination device.SELECTED DRAWING: Figure 1

Description

The present invention relates to an information processing program, an information processing method, and an information processing apparatus.

RPA (Robotic Process Automation) is a technology for automating business processes using software-type robots (RPA robots), and is attracting attention as a measure to improve business efficiency and address labor shortages. For example, a user's operation that has been conventionally performed on a computer can be automated by having an RPA robot operating on the computer memorize the user's operation.

In addition, regarding the maintenance of the RPA system, there are the following proposals. For example, the following RPA system has been proposed, which has a configuration in which an RPA server receives information input to a user terminal and processes the information. In this RPA system, when an error occurs when an RPA server executes an operation specified in an operation content holding unit, it acquires and analyzes resources such as a web page that is the target of the operation in which the error occurred. By doing so, it is determined whether or not there is a change to the resource. A system has also been proposed in which an RPA maintenance support server acquires log data indicating the processing results of RPA software from a log database of a client computer, and outputs maintenance information indicating application changes based on this log data. .

Japanese Patent Application Laid-Open No. 2020-13400 JP 2019-159556 A

Examples of tasks to be automated by the RPA robot include input operations for applications made by other companies and input operations for external websites. However, if the specifications of these third-party applications or external websites are changed, an execution error may occur in the RPA robot, and in that case, there is a possibility that the work will be stopped. There is a problem that it is difficult for users to know in advance the specification changes of applications made by other companies and websites outside the company, and it is not easy to prevent the occurrence of execution errors in RPA robots due to specification changes.

In one aspect, an object of the present invention is to provide an information processing program, an information processing method, and an information processing apparatus capable of acquiring information that enables detection of a specification change of an operation target when an RPA robot is not executed.

In one proposal, the computer executes operation processing for executing at least a part of the operation that the RPA robot performs on the operation target during a time period when the RPA robot is not executed, and in the operation processing, the operation on the operation target is performed. Provided is an information processing program that, when an execution error occurs, collects error information indicating the content of the execution error and transmits the collected error information to a predetermined destination device.

In one proposal, an information processing method is provided in which a computer executes processing similar to the processing based on the information processing program described above.
Furthermore, one proposal provides an information processing apparatus that executes the same processing as the processing based on the above information processing program.

In one aspect, information can be obtained when the RPA robot is not running that makes it possible to detect specification changes of the manipulated object.

1 illustrates a configuration example and a processing example of an information processing system according to a first embodiment; FIG. It is a figure which shows the structural example of the information processing system which concerns on 2nd Embodiment. It is a figure which shows the hardware structural example of a crawler execution machine. It is a figure which shows the motion of the whole information processing system which concerns on 2nd Embodiment. It is a figure which shows the relationship between a robot and a crawler. 2 is a diagram showing a configuration example of processing functions provided in each device of the information processing system; FIG. It is a figure which shows the example of the data memorize|stored in the memory|storage part of a crawler execution machine. FIG. 4 is a diagram illustrating an example of data stored in a storage unit of an RPA management server; FIG. FIG. 10 is a sequence diagram showing an example of a processing procedure when a crawler is executed; An example of an operation screen to be operated by a robot and a crawler is shown. It is a figure which shows the robot and crawler in 3rd Embodiment. FIG. 13 is a diagram showing a configuration example of processing functions provided in each device of an information processing system according to a fourth embodiment; It is a figure which shows the relationship between the robot and crawler in 4th Embodiment. It is a figure which shows about programming of a robot and a crawler. It is a sequence diagram showing an example of a processing procedure when a crawler is executed in the fourth embodiment. FIG. 13 is a diagram showing a robot agent in the fifth embodiment; FIG.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[First embodiment]
FIG. 1 is a diagram illustrating a configuration example and a processing example of an information processing system according to the first embodiment. The information processing system shown in FIG. 1 includes information processing devices 1 and 2 and a management device 3 .

The information processing device 1 executes the RPA robot 11 . The RPA robot 11 is a software robot that automatically executes operations on the operation target 4 . The operation target 4 is, for example, an application or a web server. If the operation target 4 is an application, this application may be executed inside the information processing device 1 .

Here, there are cases where the specifications of the operation target 4 are changed unexpectedly. For example, when the operation target 4 is an application made by another company or an external Web server, it is difficult for the operation manager of the RPA robot 11 to recognize the specification change of the operation target 4 in advance. For this reason, an unexpected change in the specification of the operation target 4 may cause an error in the execution of the operation of the RPA robot 11 during work using the RPA robot 11 . In this case, business may stop.

Therefore, in the present embodiment, the information processing device 2 executes the processing for acquiring information that enables detection of the specification change of the operation target 4 outside business hours.
The information processing device 2 includes a processing unit 20 . The processing unit 20 is implemented as, for example, a processor. The processing unit 20 executes the following processing. The processing of steps S1 and S2 below may be executed by the operation of the RPA robot 21 for collecting information.

The processing unit 20 executes at least part of the operation that the RPA robot 11 executes on the operation target 4 (step S1). In this operation processing, for example, among the operations on the operation target 4 by the RPA robot 11, execution of each operation of data registration, data update, and data deletion is skipped, and other operations are executed. Alternatively, in the operation process, all operations by the RPA robot 11 may be performed using input data different from input data used for inputting to the operation target 4 when the RPA robot 11 is executed.

The processing unit 20 executes such operation processing during a time period when the RPA robot 11 is not executed. Note that when the operation target 4 by the processing unit 20 is an application, this application may be executed in both the information processing apparatuses 1 and 2 .

In the operation process described above, when an operation execution error occurs with respect to the operation target 4, the processing unit 20 collects error information indicating the details of the execution error, and transmits the collected error information to a predetermined destination device. (step S2). Assume that the collected error information is transmitted to the management device 3 in the present embodiment. Also, as the error information, for example, information indicating the operation in which the execution error occurred, image data of the operation screen when the error occurred, and the like are collected.

By analyzing the error information collected in this way, the operation manager can recognize the specification change of the operation target 4 in advance and modify the operation contents of the RPA robot 11 accordingly. becomes possible. By performing the work using the RPA robot 11 whose operation content has been corrected, it is possible to reduce the possibility that an error in the execution of the operation by the RPA robot 11 will occur and the work will stop.

As described above, through the processing of the information processing device 2, it becomes possible to acquire information that enables detection of a specification change of the operation target 4 during a period in which the RPA robot 11 is not being executed.
Note that the processes of steps S1 and S2 described above may be executed by a device in which the RPA robot 11 is executed. For example, when the processing of steps S1 and S2 is executed by the operation of the RPA robot 21 for collecting information, the RPA robots 11 and 21 may operate by the same device.

[Second embodiment]
FIG. 2 is a diagram illustrating a configuration example of an information processing system according to the second embodiment. The information processing system shown in FIG. 2 includes robot execution machines 100-1, 100-2, . These devices are interconnected via a network 400 .

In this information processing system, robot execution machines 100-1, 100-2, . . . operate (execute) RPA robots, which are software robots. For example, the RPA robots automatically perform operations on the desktop screens of the corresponding robot execution machines 100-1, 100-2, .

The RPA robots executed by the robot execution machines 100-1, 100-2, . . . automate operations for actual business. In the following description, simply referring to "robots" refers to RPA robots for actual work executed by the robot execution machines 100-1, 100-2, . . . In the following description, the robot execution machines 100-1, 100-2, .

The crawler execution machine 200 executes crawlers under the control of the RPA management server 300 . The crawler is an RPA robot that exhaustively executes robot operations executed by the robot execution machines 100-1, 100-2, . The crawler periodically executes such operations in a time zone different from the time zone in which the robot is executed (work time zone), thereby monitoring whether there have been any specification changes or version upgrades in the target operated by the robot. . If an error occurs during execution of an operation, the crawler determines that there may have been a specification change or version upgrade, collects information about the content of the error and the operation in which the error occurred, and sends it to the RPA management server 300. Send.

The RPA management server 300 manages execution of robots in the robot execution machines 100-1, 100-2, . For example, the RPA management server 300 causes a corresponding robot execution machine to execute a robot in response to a robot execution request from an operations manager or a person in charge of operations. A robot execution request is transmitted from a terminal device such as the operator terminal 420 to the RPA management server 300 in response to an operation on the terminal device, for example.

Also, the RPA management server 300 manages crawler execution in the crawler execution machine 200 . Furthermore, the RPA management server 300 receives information collected by the crawler and notifies the operation manager of the received information.

The external server 410 is an example of a server device that provides a service to be operated by a robot. For example, the external server 410 provides a website for users to use various services. In this case, the robot uses the service and automatically executes the work by operating the GUI (Graphical User Interface) of the website.

The operator terminal 420 is a terminal device used by the operation manager. For example, the operation manager can use the operator terminal 420 to check the content of the information sent from the RPA management server 300 to him/herself.

FIG. 3 is a diagram illustrating an example hardware configuration of a crawler execution machine. The crawler execution machine 200 is implemented as a computer as shown in FIG. 3, for example. The crawler execution machine 200 shown in FIG. A communication interface (I/F) 207 is provided.

The processor 201 centrally controls the crawler execution machine 200 as a whole. The processor 201 is, for example, a CPU (Central Processing Unit), MPU (Micro Processing Unit), DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), or PLD (Programmable Logic Device). Also, processor 201 may be a combination of two or more of CPU, MPU, DSP, ASIC, and PLD.

A RAM 202 is used as the main storage device of the crawler execution machine 200 . The RAM 202 temporarily stores at least part of an OS (Operating System) program and application programs to be executed by the processor 201 . Also, the RAM 202 stores various data necessary for processing by the processor 201 .

The HDD 203 is used as an auxiliary storage device for the crawler execution machine 200 . The HDD 203 stores an OS program, application programs, and various data. Other types of non-volatile storage devices such as SSDs (Solid State Drives) can also be used as auxiliary storage devices.

A display device 204 a is connected to the GPU 204 . The GPU 204 causes the display device 204a to display an image according to instructions from the processor 201 . Examples of the display device 204a include a liquid crystal display and an organic EL (ElectroLuminescence) display.

An input device 205 a is connected to the input interface 205 . The input interface 205 transmits signals output from the input device 205 a to the processor 201 . The input device 205a includes a keyboard, pointing device, and the like. Pointing devices include mice, touch panels, tablets, touch pads, trackballs, and the like.

A portable recording medium 206a is attached to and detached from the reading device 206 . The reading device 206 reads the data recorded on the portable recording medium 206 a and transmits the read data to the processor 201 . As the portable recording medium 206a, there are an optical disk, a semiconductor memory, and the like.

The communication interface 207 transmits and receives data to and from other devices such as the RPA management server 300 via the network 400 .
With the above hardware configuration, the processing functions of the crawler execution machine 200 can be realized. The robot execution machine 100, the RPA management server 300, the external server 410, and the operator terminal 420 can also be implemented as computers having the hardware configuration shown in FIG.

By the way, targets of operations automated by the robot include applications on the robot execution machine 100 executed by the robot, websites of external servers, and the like. When specifications are changed or upgraded in such applications and websites, robot operations may be affected. For example, when the configuration of the GUI is changed due to specification change or version upgrade, unless the operation procedure of the robot is changed accordingly, an operation error may occur in the robot and the work may stop.

Here, if the application is developed by the customer (company) who operates the robot, or the website is operated by the customer, the customer should notify the customer of the specification change or version upgrade in advance. can be known to Therefore, the customer can modify the operation procedure of the robot in advance according to the contents of the specification change or version upgrade so as not to stop the work.

However, there are cases where the robot's operation target is an application made by another company or a website outside the company. In this case, it is difficult for the customer to know in advance the details of specification changes and version upgrades of applications and websites. For this reason, there is a possibility that an operation error of the robot will occur due to specification change or version upgrade during the execution of the work using the robot, and the work will be stopped.

As one method for solving such a problem, for example, a method of periodically monitoring information on specification changes and version upgrades of an application to be operated or a website is conceivable. Specifically, the website of the application development vendor and the website management vendor is periodically accessed to acquire information on specification changes and version upgrades. However, it takes a lot of time and effort to perform such processing manually, and even if it is performed by a computer, there is a problem that the processing load is high. Also, even if there is a specification change or a version upgrade, if there is no change in the configuration of the GUI or a change in the specifications of functions related thereto, no error will occur during execution of the robot. There is also the problem that it is not easy to accurately determine only such changes related to the GUI by the above monitoring.

Therefore, in the present embodiment, a crawler that exhaustively executes robot operations is prepared, and the crawler executes operations on applications and websites during non-business hours. When an operation execution error occurs, the crawler collects information about the details of the error and the operation target in which the error occurred, and notifies the RPA management server 300 of the information. Based on the information collected in this way, operation managers and business personnel can recognize the details of specification changes and version upgrades of applications and websites, and adjust the operation details of the robot so that the operation of the robot does not stop. It becomes possible to change.

FIG. 4 is a diagram showing the movement of the entire information processing system according to the second embodiment. In FIG. 4, the robot execution machine 100 executes the robot 110 under the management of the RPA management server 300 . In FIG. 4, it is assumed that an application 501 and a website 502 are to be operated by the robot 110 . An application 501 is a third-party application provided by a company other than the customer. Although the application 501 is shown outside the robot execution machine 100 in FIG. 4, the application 501 is actually installed on the robot execution machine 100 . The website 502 is an external site operated by a company other than the customer, and is provided by the external server 410 shown in FIG. 2, for example.

Further, in the present embodiment, a crawler 210 that exhaustively executes operations of the robot 110 is created. The crawler 210 has a function of notifying the RPA management server 300 of information necessary for analysis when determining that there is a possibility that the robot 110 is not simply duplicated, but that the specifications of the operation target have been changed or upgraded. . Furthermore, the crawler 210 also has a function of skipping execution of operations such as registration, update, and deletion of data that may interfere with operations.

In this embodiment, the crawler 210 is executed by the crawler execution machine 200, but the device for executing the crawler 210 is not limited. 210 may be performed.

The crawler 210 is periodically executed in response to instructions from the RPA management server 300 during non-business hours (processing P1). The crawler 210 automatically executes an operation on an operation target in order to monitor specification changes and version upgrades of the application 501 and website 502 that are the operation target (process P2).

When an operation execution error occurs, the crawler 210 collects information about the contents of the error and the operation in which the error occurred, and notifies the RPA management server 300 (process P3). For example, information indicating the content of the error, information about the operation target in which the error occurred (for example, screen information of the application 501 or website 502), etc. are collected and notified to the RPA management server 300. FIG. The RPA management server 300 notifies the operation manager 421 of the notified collected information by e-mail, for example (process P4).

The operations manager 421 analyzes the notified collected information and maintains the robot 110 based on the analysis results (process P5). That is, the operation manager 421 modifies the processing procedure of the robot 110 in accordance with the specification change or version upgrade of the application 501 or website 502 . In addition, before starting work, the operation manager 421 notifies the business person 431 of information such as the occurrence of a specification change or version upgrade of the application 501 or the website 502 and the content thereof, for example, by e-mail. (Processing P6).

Thereafter, the RPA management server 300 instructs the robot execution machine 100 to execute the robot 110 (process P7). In response to this execution instruction, the robot 110 is activated and automatically operates the application 501 and the website 502 (process P8). Since the operation details of the robot 110 have already been corrected in accordance with the details of the specification change or version upgrade, the possibility of an operation execution error occurring by the robot 110 during work can be suppressed.

FIG. 5 is a diagram showing the relationship between the robot and the crawler. The crawler 210 can comprehensively perform operations of multiple robots. For example, in FIG. 5, robot 110-1 runs on robot execution machine 100-1 and robot 110-2 runs on robot execution machine 100-2. In this case, the crawler 210 exhaustively executes the operations of the robots 110-1 and 110-2.

For example, the robot 110-1 automatically executes an operation based on a script 111-1 describing the details of the operation. Also, the robot 110-2 automatically executes an operation based on a script 111-2 describing the details of the operation. In this case, creation of the crawler 210 is performed, for example, as follows.

First, information indicating the operation content is extracted from the scripts 111-1 and 111-2. Then, the operations are classified for each operation screen (for example, the same page on the website), and the contents of the classified operations are described in the script for the crawler 210 (crawler script 211). At this time, the contents of the operation are described so that the operation for the same input position does not overlap. For example, when the robot 110-1 inputs data A into an input field on a Web page, and the robot 110-2 inputs data B into the same input field on the same Web page, the crawler script 211 Only the operation of inputting data A or data B to the input field should be described. By operating based on the crawler script 211 created in this way, the crawler 210 can comprehensively execute the operations of the robots 110-1 and 110-2.

Here, if the crawler 210 executes all the operations executed by the robots 110-1 and 110-2, there is a possibility that business will be hindered. For example, among the operations executed by the robots 110-1 and 110-2, if the crawler 210 executes data registration, update, and deletion operations, data inconsistencies and errors in registered data may occur during work. may occur. Therefore, among the operations described in the crawler script 211, the crawler 210 skips execution of operations that may interfere with operations, such as data registration, update, and deletion.

FIG. 6 is a diagram showing a configuration example of processing functions provided in each device of the information processing system.
First, the robot execution machine 100 has a storage unit 120 , a robot agent 130 , an application 141 and a web browser 142 .

The storage unit 120 is implemented by a storage area of a storage device (not shown) included in the robot execution machine 100 . The storage unit 120 stores, for example, data necessary for processing of the robot agent 130 . As an example, a script (corresponding to either script 111-1 or 111-2 in FIG. 5) describing the operation content of the robot 110 is stored in the storage unit 120. FIG.

The processes of the robot agent 130, the application 141, and the web browser 142 are realized, for example, by a processor (not shown) provided in the robot execution machine 100 executing a predetermined program.

The robot agent 130 implements actions of the robot 110 based on scripts stored in the storage unit 120 . The entity of the robot 110 is an agent program that implements the robot agent 130, and "execution of the robot 110" means execution of the agent program.

The application 141 and the web browser 142 are processing functions to be directly operated by the robot 110 . The application 141 provides a GUI and executes processing according to the operation of the robot 110 on this GUI. This application 141 is a third-party application provided by a company other than the customer. The web browser 142 displays a web page provided by a web server and transmits data to the web server according to an operation on the web page. In this embodiment, the external server 410 operates as a web server, and provides the web browser 142 with a GUI screen as a web page for using services provided by the external server 410 . Then, the external server 410 executes processing corresponding to the service according to the operation of the robot 110 on this GUI screen.

The crawler execution machine 200 comprises a storage unit 220 , a crawler agent 230 , an application 241 and a web browser 242 .
The storage unit 220 is implemented by a storage area of a storage device provided in the crawler execution machine 200, such as the RAM 202 and the HDD 203. FIG. The storage unit 220 stores, for example, a crawler script (corresponding to the crawler script 211 in FIG. 5) describing the operation content of the crawler 210, and error information created when an operation execution error occurs by the crawler 210. is stored.

The processing of the crawler agent 230, the application 241 and the web browser 242 is realized by the processor 201 executing a predetermined program.
The crawler agent 230 realizes the operation of the crawler 210 based on the crawler script stored in the storage unit 220 . Also, when an operation execution error occurs, the crawler agent 230 stores error information about the error in the storage unit 220 and then transmits the error information to the RPA management server 300 .

The application 241 and the web browser 242 are processing functions to be directly operated by the crawler 210 . The application 241 can execute processing similar to that of the application 141 of the robot execution machine 100 . The web browser 242 can execute processing similar to that of the web browser 142 of the robot execution machine 100 . 5, when the crawler 210 executes operations of a plurality of robots 110, the crawler execution machine 200 has processing functions corresponding to respective operation targets of those robots 110. FIG.

The RPA management server 300 includes a storage unit 310 , a robot execution management unit 321 and a crawler execution management unit 322 .
The storage unit 310 is implemented by a storage area of a storage device (not shown) included in the RPA management server 300 . The storage unit 310 stores, for example, information for managing the crawler 210, error information collected from the crawler 210, and the like.

The processes of the robot execution management unit 321 and the crawler execution management unit 322 are realized, for example, by a processor (not shown) provided in the RPA management server 300 executing a predetermined program. The robot execution management unit 321 manages execution of the robot 110 on the robot execution machine 100 . For example, the robot execution management unit 321 instructs execution of the robot 110 in response to a robot execution request from a terminal device such as the operator terminal 420 .

The crawler execution management unit 322 manages execution of the crawler 210 on the crawler execution machine 200 . For example, the crawler execution management unit 322 instructs the crawler 210 to execute according to the execution schedule information of the crawler 210 stored in the storage unit 120 . In addition, the crawler execution management unit 322 stores the error information transmitted from the crawler 210 in the storage unit 220, and based on the error information, sends information such as the occurrence of an error and the details of the error using e-mail or the like. Notify the operations manager.

FIG. 7 is a diagram showing an example of data stored in the storage unit of the crawler execution machine. The storage unit 220 of the crawler execution machine 200 stores an error information management table 221 in addition to the crawler script described above. The error information management table 221 stores error information created when an operation execution error by the crawler 210 occurs. The error information management table 221 is created and stored in the storage unit 220 each time an operation execution error occurs. That is, the error information management table 221 is created for each operation in which an execution error has occurred.

As shown in FIG. 7, each record of the error information management table 221 registers an error information type and a file name. The error information type indicates the type of corresponding error information. File name indicates the name of the file in which the error information is described. The storage unit 220 separately stores the error information file indicated by the file name.

As the error information, for example, crawler error messages, screen capture data, application names, application error messages, site URLs (Uniform Resource Locators), and the like are created. The crawler error message indicates information indicating an operation by the crawler 210 when an error occurs (for example, information indicating an operation name, an operation position on the GUI, etc.). The screen capture data indicates image data of the GUI screen when an error occurs. The application name indicates identification information of the application that was the operation target when the error occurred. The application error message indicates information (for example, an error message returned from the application) indicating the content of an error that occurred during operation of the application. The site URL indicates the URL of the web page that was the operation target when the error occurred.

Crawler error messages and screen capture data are registered in the storage unit 220 regardless of whether the operation target is an application or a website. The application name and application error message are registered in storage unit 220 only when the operation target is an application. The site URL is registered in the storage unit 220 only when the operation target is a website.

FIG. 8 is a diagram depicting an example of data stored in the storage unit of the RPA management server; As shown in FIG. 8, the storage unit 310 of the RPA management server 300 stores, for example, a crawler management table 311, a process management table 312, a schedule management table 313, a notification information management table 314, and a collection information management table 315. .

Records corresponding to crawlers managed by the RPA management server 300 are registered in the crawler management table 311 . As in the example of FIG. 8 , when there are multiple crawlers to be managed, multiple records corresponding to individual crawlers are registered in the crawler management table 311 . In each record of the crawler management table 311, a crawler ID indicating crawler identification information is registered in association with a crawler name indicating the name of the crawler (RPA robot name indicating the crawler).

Records corresponding to processes executed by crawlers are registered in the process management table 312 . A process is a unit of processing executed by an RPA robot. When causing an RPA robot to execute an operation, the RPA management server 300 identifies the RPA robot and designates a process to the RPA robot to start executing the operation.

In each record of the process management table 312, a process ID indicating process identification information is registered in association with a process name and an operating crawler ID. The process name indicates the name of the process. The active crawler ID indicates the crawler ID of the crawler on which the process is executed.

Execution schedule information for each crawler is registered in the schedule management table 313 . In each record of the schedule management table 313, an execution period, an execution time, an execution day, and an execution date are registered for a crawler ID indicating a crawler. The execution cycle indicates in what cycle the crawler is executed periodically. Execution time indicates the time at which the crawler is executed. The execution day indicates the day of the week on which the crawler is executed when the crawler is executed on a weekly basis (when "weekly" is registered in the execution cycle). The date of execution indicates the day on which the crawler is to be executed, not periodically but on a specific day. It should be noted that the execution of the crawler is scheduled so as to be performed at least in a different time zone from the time zone in which the corresponding robot is executed.

In the notification information management table 314, information of a user (operation manager, etc.) to be notified of error information collected and transmitted by the crawler is registered. In each record of the notification information management table 314, a notification destination e-mail address indicating a notification destination of error information is registered for a user name that identifies a notification destination user.

The collected information management table 315 is a table for managing error information collected and transmitted by the crawler. In each record of the collected information management table 315, a file name indicating the error information is registered with respect to the crawler ID indicating the crawler that sent the error information. Here, as an example, it is assumed that the error information collected by the crawler is compiled into one file and sent to the RPA management server 300 . In this case, a file indicating error information is stored in the storage unit 310, and a file name indicating the file is registered in the collected information management table 315 in association with the crawler ID.

FIG. 9 is a sequence diagram showing an example of a processing procedure when the crawler is executed.
[Step S11] The RPA management server 300 executes preprocessing for crawler execution. For example, the execution schedule information of the crawler 210 is registered in the schedule management table 313 according to the setting operation by the operation manager from the operator terminal 420 .

[Step S<b>12 ] The crawler execution management unit 322 of the RPA management server 300 determines whether the execution time for the crawler 210 has come, based on the execution schedule information for the corresponding crawler 210 registered in the schedule management table 313 . When the execution time has not come (when the current time is not the execution time), the process of step S12 is re-executed after a certain period of time. On the other hand, when the execution time has come (when the current time is the execution time), the process proceeds to step S13.

[Step S13] The crawler execution management unit 322 transmits an execution instruction of the crawler 210 to the crawler execution machine 200 on which the crawler 210 is executed. Actually, the process to be executed by the crawler 210 is designated based on the process management table 312 .

[Step S14] The crawler execution machine 200 activates the crawler agent 230 in response to receiving the execution instruction. Thereby, automatic execution of the operation by the crawler 210 is started.

[Step S15] The crawler agent 230 acquires information about an operation to be executed next, for example, from a crawler script in the storage unit 220, and determines whether this operation is data registration, data update, or data deletion. do. If the operation is neither of these, the process proceeds to step S16, and if the operation is any of these, the process proceeds to step S20. In the latter case, execution of the operation (step S16) will be skipped.

[Step S16] The crawler agent 230 executes an operation.
[Step S17] The crawler agent 230 determines whether an operation execution error has occurred. If an execution error occurs, the process proceeds to step S18, and if no execution error occurs, the process proceeds to step S20.

[Step S18] The crawler agent 230 collects error information regarding execution errors that have occurred. The crawler agent 230 creates an error information management table 221 in the storage unit 220 and registers the collected error information in this error information management table 221 .

[Step S<b>19 ] The crawler agent 230 acquires error information from the error information management table 221 , creates an error information file in which an execution error has occurred, and transmits it to the RPA management server 300 .

Although not shown, upon receiving the error information file, the crawler execution management unit 322 of the RPA management server 300 stores the received error information file in the storage unit 310 . Along with this, the crawler execution management unit 322 registers the file name of the error information file in the collected information management table 315 in association with the crawler ID of the crawler 210 .

[Step S20] The crawler agent 230 determines whether the processing of the crawler 210 is finished. If there is no operation to be executed next, it is determined that the process is finished. When continuing the processing of the crawler 210, the processing proceeds to step S15, and the processing regarding the next operation is executed. On the other hand, when ending the processing of the crawler 210, the processing proceeds to step S21.

[Step S21] The crawler agent 230 sends a completion notification indicating that the operation by the crawler 210 is completed to the RPA management server 300, and ends the operation. This completes the execution of crawler 210 .

[Step S22] The crawler execution management unit 322 of the RPA management server 300 refers to the collected information management table 315 and determines whether an error information file corresponding to the crawler 210 whose operation has been completed is registered. Here, if it is determined that the information is registered, the crawler execution management unit 322 identifies the notification destination address of the information from the notification information management table 314 and creates an e-mail addressed to the notification destination address. This e-mail describes that an error occurred during execution of an operation by the crawler 210 and the content of error information extracted from the error information file. As for the error information file, the information indicating the storage location may be described in the e-mail instead of describing the contents thereof in the e-mail.

The crawler execution management unit 322 transmits the created e-mail to the notification destination address. As a result, the operation manager is notified of the occurrence of an operation execution error and the content of the error.

FIG. 10 shows an example of an operation screen to be operated by the robot and the crawler. An example of a specific operation procedure for each of the robot and the crawler will be described below using the operation screen 510 illustrated in FIG. 10 .

The operation screen 510 is a web page for registering questionnaire information in the external server 410 and obtaining the registered questionnaire information from the external server 410, and is specified by one URL. This operation screen 510 includes an item display area 511 and an information input/display area 512 . The item display area 511 displays a plurality of input item names, and the information input/display area 512 displays input/display columns for inputting and displaying registration information corresponding to each input item.

Operation screen 510 further includes save button 513 , update button 514 , cancel button 515 and end button 516 . When the save button 513 is pressed, the information input to the information input/display area 512 is registered in the external server 410 . When the update button 514 is pressed, the information entered in the information input/display area 512 is used to update the information registered in the external server 410 . When the cancel button 515 is pressed, the operation screen 510 is closed without registering the information input to the information input/display area 512 or updating the information. When the end button 516 is pressed, the operation screen 510 is closed.

Here, as an example, it is assumed that the robot 110-1 performs the following information registration operation. When an operation to open the operation screen 510 is performed, the robot 110-1 sequentially selects the input/display columns of the information input/display area 512 from the first row, and displays information prepared in advance in the selected input/display columns. input. When robot 110-1 completes input to all input/display fields, robot 110-1 presses save button 513 to register the entered information in external server 410, and finally presses end button 516 to close operation screen 510. close.

Furthermore, it is assumed that the robot 110-2 performs the following information acquisition operation. When an operation to open the operation screen 510 is performed, the robot 110-2 sequentially selects the input/display columns of the information input/display area 512 from the first row, and displays the information displayed in the selected input/display columns. , along with corresponding metadata (ie, corresponding input items). When the robot 110 - 2 acquires all the registration information together with the metadata, the robot 110 - 2 presses the end button 516 to close the operation screen 510 .

The following operations are described in the crawler script indicating the operation procedure of the crawler 210 corresponding to such robots 110-1 and 110-2.
(1) Open the operation screen 510 .

(2) The input/display columns in the information input/display area 512 are sequentially selected from the first row, and information prepared in advance is entered in the selected input/display columns.
(3) The input/display fields in the information input/display area 512 are sequentially selected from the first row, and the information displayed in the selected input/display fields is acquired together with the corresponding metadata.

(4) Press the save button 513 .
(5) Press the end button 516 .
However, in the actual processing of the crawler 210 based on the crawler script, only the data registration operation (4) "pressing the save button 513" is skipped.

According to the example of FIG. 10 and the process shown in FIG. 9, in the process of the crawler 210, among the corresponding operations of each robot 110, the data registration operation, update operation, and deletion operation are skipped, and the other operations are skipped. only executed. For this reason, registration information used for business will not be altered by non-business operations by the crawler 210, and it is possible to detect specification changes and version upgrades of the operation target before actual business is performed without interfering with business. Become.

[Third Embodiment]
Next, a description will be given of a third embodiment in which part of the processing in the second embodiment is modified.

FIG. 11 is a diagram showing the robot and crawlers in the third embodiment. In the third embodiment, the crawler 210 corresponding to the robot 110 operates as in the second embodiment. Although the device on which the crawler 210 is executed is not limited, it is assumed in FIG. 11 that the crawler 210 is executed by the crawler execution machine 200 as an example. The crawler 210 exhaustively executes the operations of the robot 110 .

In the example of FIG. 11, the robot execution machine 100-1 executes the robot 110-1, and the robot execution machine 100-2 executes the robot 110-2, as in FIG. The crawler 210 comprehensively executes the operations of the robots 110-1 and 110-2. For example, the robot 110-1 executes an operation based on a script 111-1 describing the details of the operation, and the robot 110-2 executes an operation based on a script 111-2 describing the details of the operation. Suppose. In this case, operations described in the scripts 111-1 and 111-2 are classified for each operation screen, and the contents of the classified operations are described in the crawler script 211, as in the second embodiment.

Here, in the above-described second embodiment, the crawler 210 skips the data registration operation, update operation, and deletion operation among the operations described in the crawler script 211, thereby causing problems in business. It prevents such modification of registration information. On the other hand, in the third embodiment, the crawler 210 executes all operations described in the crawler script 211 . Instead, crawler 210 performs registration, update, and delete operations using crawler-specific data. As a result, it is possible to prevent alteration of the registered information that would hinder business operations.

For example, the storage unit 120 of the robot execution machine 100-1 stores a registration information database (DB) 122-1 that stores data that the robot 110-1 uses when registering or updating data. The storage unit 120 of the robot execution machine 100-2 also stores a registration information database (DB) 122-2 that stores data that the robot 110-2 uses when registering or updating data. On the other hand, the storage unit 220 of the crawler execution machine 200 stores a registration information database (DB) 222 for the crawler 210 that stores data that the crawler 210 uses when registering or updating data.

The registration information database 222 for the crawler contains, for example, user IDs and passwords for using applications and user IDs and passwords for logging in to Web server services, which are used by the robots 110-1 and 110-2. Data different from the data is registered. Thereby, the crawler 210 operates applications and websites as a user different from the robots 110-1 and 110-2. In this case, data other than the above user ID and password may be registered in the crawler registration information database 222 as in the robot registration information databases 122-1 and 122-2.

In this way, the crawler 210 uses the data registered in the crawler registration information database 222 as input data in the input fields of the operation screen, and executes all the operations executed by the robots 110-1 and 110-2. do. This makes it possible to detect specification changes and version upgrades of the operation target before the actual work is performed without interfering with the work.

[Fourth Embodiment]
Next, a fourth embodiment in which part of the processing in the second embodiment is modified will be described. The fourth embodiment differs from the second embodiment in that robot agents that implement both robots and their corresponding crawlers are created separately for each robot.

FIG. 12 is a diagram illustrating a configuration example of processing functions provided in each device of the information processing system according to the fourth embodiment.
The robot execution machine 100 has a robot agent 130a that implements both a robot and a crawler instead of the robot agent 130 shown in FIG. That is, the robot agent 130a includes a robot execution unit 131 that implements robot processing, and a crawler execution unit 132 that implements crawler processing.

On the other hand, the crawler execution machine 200 has the same robot agent 130a as the robot execution machine 100 instead of the crawler agent 230 shown in FIG. This robot agent 130a also has a robot execution unit 131 and a crawler execution unit 132, like the robot execution machine 100. FIG.

Any robot agent 130 a can selectively operate the robot execution unit 131 and the crawler execution unit 132 according to instructions from the RPA management server 300 . Although the device on which the crawler is executed is not particularly limited, in this embodiment, as an example, the robot is executed by the robot execution machine 100 and the crawler is executed by the crawler execution machine 200 as in the second embodiment. shall be performed. In this case, the robot execution unit 131 operates in the robot execution machine 100 and the crawler execution unit 132 operates in the crawler execution machine 200 according to instructions from the RPA management server 300 .

FIG. 13 is a diagram showing the relationship between the robot and crawlers in the fourth embodiment. As described above, in this embodiment, robot agents that implement both the robot and its corresponding crawler are created separately for each robot. If the robot and crawler are run on separate devices as shown in FIG. 12, the same robot agent that implements the robot and crawler is installed on each device. Furthermore, if there are multiple robots, robot agents corresponding to each robot are created separately.

In the example of FIG. 13, different robots are executed by the robot execution machine 100-1 and the robot execution machine 100-2. Both the crawler corresponding to the robot on the robot execution machine 100-1 and the crawler corresponding to the robot on the robot execution machine 100-2 are executed by the same crawler execution machine 200. FIG. In this case, the crawler execution machine 200 is also provided with both the robot agent 130a-1 provided in the robot execution machine 100-1 and the robot agent 130a-2 provided in the robot execution machine 100-2.

Here, each robot agent can selectively execute robots and crawlers according to instructions from the RPA management server 300 . In this embodiment, as an example, the robot agent selectively executes either the robot or the crawler according to the value of the execution argument specified by the RPA management server. Hereinafter, it is assumed that the robot is executed when the execution argument is 1, and the crawler is executed when the execution argument is 0.

In FIG. 13, the robot agent 130a-1 has a robot execution unit 131-1 and a crawler execution unit 132-1. Execution argument=1 is specified from the RPA management server 300 to the robot agent 130a-1 of the robot execution machine 100-1. As a result, the robot execution unit 131-1 is activated in the robot execution machine 100-1 to operate the robot. On the other hand, for the robot agent 130a-1 of the crawler execution machine 200, the RPA management server 300 specifies execution argument=0. As a result, in the crawler execution machine 200, the crawler execution unit 132-1 is activated and the crawler operates.

The robot execution unit 131-1 of the robot execution machine 100-1 automatically executes an operation based on, for example, a script 111-1 describing the content of the operation. The same script 111-1 is also stored in the crawler execution machine 200, and the crawler execution unit 132-1 of the crawler execution machine 200 automatically executes operations based on this script 111-1. However, as in the second embodiment, the crawler execution unit 132-1 skips data registration, update, and deletion operations among robot operations.

Similarly, the robot agent 130a-2 comprises a robot execution unit 131-2 and a crawler execution unit 132-2. Execution argument=1 is specified from the RPA management server 300 to the robot agent 130a-2 of the robot execution machine 100-2. As a result, the robot execution unit 131-2 is activated in the robot execution machine 100-2 to operate the robot. On the other hand, for the robot agent 130a-2 of the crawler execution machine 200, the RPA management server 300 specifies execution argument=0. As a result, in the crawler execution machine 200, the crawler execution unit 132-2 is activated and the crawler operates.

The robot execution unit 131-2 of the robot execution machine 100-2 automatically executes an operation based on, for example, a script 111-2 describing the content of the operation. The same script 111-2 is also stored in the crawler execution machine 200, and the crawler execution unit 132-2 of the crawler execution machine 200 automatically executes operations based on this script 111-2. However, as in the second embodiment, the crawler execution unit 132-2 skips data registration, update, and deletion operations among robot operations.

As described above, in this embodiment, even when a plurality of robots are in operation, the robots and the crawlers are in one-to-one correspondence. Therefore, when error information is collected by the execution of the crawler, transmitted to the RPA management server 300, and further transmitted to the operations manager, the operations manager classifies the error information for each robot corresponding to the crawler. recognizable. Therefore, based on the error information, the operation manager can easily and clearly recognize which robot the operation in which the execution error occurred corresponds to.

FIG. 14 is a diagram showing programming of robots and crawlers. Here, as an example, it is assumed that a robot agent program 133 that implements a robot and a crawler is created in developer terminal 600 operated by the developer. This robot agent program 133 includes, for example, a script describing the contents of the operation.

The developer terminal 600 has a robot creation unit 601 that creates the robot agent program 133 . The processing of the robot creating unit 601 is implemented by, for example, a processor (not shown) included in the developer terminal 600 executing a predetermined program.

When a program for operating the robot is created according to the developer's operation, the robot creation unit 601 automatically creates a program for operating the crawler corresponding to the robot. For example, in the present embodiment, reference is made to a framework (crawler framework 602) that automatically creates crawler processing by wrapping robot processing.

The crawler framework 602 is a resource file applied to a development environment for developing RPA robots. For example, the crawler framework 602 may be implemented as a pluggable library or shell of a robot source file. When the robot creation unit 601 creates a robot program (a program that realizes a robot execution unit) using the crawler framework 602 according to the developer's operation, the corresponding crawler program (crawler execution unit automatically create a program that realizes

13 and 14, each processing function of the robot and the crawler included in the robot agent 130 is divided into a robot execution unit 131 and a crawler execution unit 132 for easy understanding. However, if a program (robot agent program 133) that implements the robot agent 130 is created using the crawler framework 602, the crawler processing is actually included in the robot processing. Become. As an example, a crawler code that is executed only when the execution argument=0 is added to the code of the program that implements the processing of the robot. Examples of such crawler code include code for skipping operations when the operation to be executed is one of registration, update, or deletion of data, or code for skipping an operation when an operation execution error occurs. It contains code for collecting information, and code for sending collected error information to the RPA management server 300 at the end of the entire operation.

As described above, by using the crawler framework 602, it is possible to automatically create a corresponding crawler program when creating a robot program. Therefore, it is possible to reduce the labor of the developer of the robot agent 130, improve the development efficiency, and reduce the development cost.

FIG. 15 is a sequence diagram illustrating an example of a processing procedure when a crawler is executed in the fourth embodiment; In FIG. 15, the same step numbers are assigned to the same processes as in FIG. As shown in FIG. 15, when the crawler is executed in this embodiment, steps S13a and S14a are executed instead of steps S13 and S14 in FIG.

[Step S13a] When the crawler execution time comes (Step S12: Yes), the crawler execution management unit 322 of the RPA management server 300 instructs the crawler execution machine 200 to execute the RPA robot by specifying the execution argument=0. to send.

[Step S14a] The robot agent 130a of the crawler execution machine 200 activates the crawler execution unit 132 based on the designated execution argument=0. This starts the automatic execution of the operation by the crawler.

The processing of steps S15 to S21 after this is executed by the crawler execution unit 132. FIG.
[Fifth Embodiment]
Next, a description will be given of a fifth embodiment in which part of the processing in the fourth embodiment is modified.

FIG. 16 is a diagram showing a robot agent according to the fifth embodiment. In the fifth embodiment, as in the fourth embodiment, robot agents that implement both the robot and its corresponding crawler are created separately for each robot. In FIG. 16, as in FIG. 13, different robots are executed by robot execution machines 100-1 and 100-2. Also, a crawler corresponding to each robot is executed by the crawler execution machine 200 .

In this case, the robot execution machine 100-1 has a robot agent 130a-1 that realizes a robot and a crawler, and the crawler execution machine 200 also has a similar robot agent 130a-1. The robot execution machine 100-2 also has a robot agent 130a-2 that implements a robot and a crawler, and the crawler execution machine 200 also has a similar robot agent 130a-2.

As in FIG. 13, the robot agent 130a-1 has a robot execution unit 131-1 and a crawler execution unit 132-1. Execution argument=1 is specified from the RPA management server 300 to the robot agent 130a-1 of the robot execution machine 100-1. As a result, the robot execution unit 131-1 is activated in the robot execution machine 100-1 to operate the robot. On the other hand, for the robot agent 130a-1 of the crawler execution machine 200, the RPA management server 300 specifies execution argument=0. As a result, in the crawler execution machine 200, the crawler execution unit 132-1 is activated and the crawler operates.

Similarly, the robot agent 130a-2 comprises a robot execution unit 131-2 and a crawler execution unit 132-2. Execution argument=1 is specified from the RPA management server 300 to the robot agent 130a-2 of the robot execution machine 100-2. As a result, the robot execution unit 131-2 is activated in the robot execution machine 100-2 to operate the robot. On the other hand, for the robot agent 130a-2 of the crawler execution machine 200, the RPA management server 300 specifies execution argument=0. As a result, in the crawler execution machine 200, the crawler execution unit 132-2 is activated and the crawler operates.

Here, in the above-described fourth embodiment, the crawler skips the data registration operation, update operation, and deletion operation among the operations described in the script of the corresponding robot, thereby causing trouble in the business. It prevents such modification of registration information. On the other hand, in the fifth embodiment, the crawler executes all the operations described in the script of the corresponding robot. Instead, the crawler performs registration, update, and delete operations using crawler-specific data. As a result, it is possible to prevent alteration of the registered information that would hinder business operations.

For example, in the storage unit 120 of the robot execution machine 100-1 and the storage unit 220 of the crawler execution machine 200, a registration information database ( and a crawler registration information database (DB) 222a-1 in which data used by the crawler execution unit 132-1 when registering or updating data is stored. The registration information database 222a-1 for the crawler contains, for example, a user ID and password for using an application, and a user ID and password for logging in to a Web server service, which the robot execution unit 131-1 uses. Data different from the data is registered. As a result, the crawler execution unit 132-1 operates applications and websites as a user different from the robot execution unit 131-1. In this case, the crawler registration information database 222a-1 may contain the same data as the robot registration information database 122a-1 except for the above user ID and password.

When the RPA management server 300 designates the execution argument=1 and instructs the execution of the RPA robot, the robot agent 130a-1 activates the robot execution unit 131-1. The robot execution unit 131-1 automatically executes an operation while referring to the robot registration information database 122a-1. In the example of FIG. 16, such processing is executed by the robot execution machine 100-1. On the other hand, when the RPA management server 300 designates the execution argument=0 and instructs the execution of the RPA robot, the robot agent 130a-1 activates the crawler execution unit 132-1. The crawler execution unit 132-1 automatically executes operations while referring to the crawler registration information database 222a-1. In the example of FIG. 16, such processing is executed by the crawler execution machine 200. FIG.

Similarly, the storage unit 120 of the robot execution machine 100-2 and the storage unit 220 of the crawler execution machine 200 have a registration information database in which data used by the robot execution unit 131-2 when registering or updating data is stored. (DB) 122a-2, and a crawler registration information database (DB) 222a-2 in which data used by the crawler execution unit 132-2 when registering or updating data is stored.

When the RPA management server 300 designates the execution argument=1 and instructs the execution of the RPA robot, the robot agent 130a-2 activates the robot execution part 131-2. The robot execution unit 131-2 automatically executes operations while referring to the robot registration information database 122a-2. In the example of FIG. 16, such processing is executed by the robot execution machine 100-2. On the other hand, when the RPA management server 300 designates the execution argument=0 and instructs the execution of the RPA robot, the robot agent 130a-2 activates the crawler execution unit 132-2. The crawler execution unit 132-2 automatically executes operations while referring to the crawler registration information database 222a-2. In the example of FIG. 16, such processing is executed by the crawler execution machine 200. FIG.

Thus, the crawler uses the data registered in the registration information database for the crawler as input data to the input fields of the operation screen, and executes all the operations that the corresponding robot executes. This makes it possible to detect specification changes and version upgrades of the operation target before the actual work is performed without interfering with the work.

Also in the fifth embodiment, when creating a robot agent program, by using the crawler framework 602 shown in FIG. can be created in

Note that the devices shown in the above embodiments (for example, the information processing devices 1 and 2, the management device 3, the robot execution machine 100, the crawler execution machine 200, the RPA management server 300, the external server 410, the operator terminal 420, The processing functions of the developer terminal 600) can be implemented by a computer. In that case, a program describing the processing contents of the functions that each device should have is provided, and the above processing functions are realized on the computer by executing the program on the computer. A program describing the processing content can be recorded in a computer-readable recording medium. Computer-readable recording media include magnetic storage devices, optical disks, semiconductor memories, and the like. Magnetic storage devices include hard disk drives (HDD) and magnetic tapes. Optical discs include CDs (Compact Discs), DVDs (Digital Versatile Discs), Blu-ray Discs (BD, registered trademark), and the like.

When distributing a program, for example, portable recording media such as DVDs and CDs on which the program is recorded are sold. It is also possible to store the program in the storage device of the server computer and transfer the program from the server computer to another computer via the network.

A computer that executes a program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. The computer then reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Also, the computer can execute processing according to the received program every time the program is transferred from a server computer connected via a network.

1, 2 information processing device 3 management device 4 operation target 11, 21 RPA robot 20 processing unit S1, S2 step

Claims (8)

to the computer,
an RPA (Robotic Process Automation) robot performing an operation process for performing at least a part of an operation performed on an operation target during a time period when the RPA robot is not performed;
collecting error information indicating details of the execution error when an execution error occurs in the operation target in the operation processing;
transmitting the collected error information to a predetermined destination device;
An information processing program that causes a process to be executed. In the operation processing, among the operations performed by the RPA robot on the operation target, execution of each operation of data registration, data update, and data deletion is skipped.
The information processing program according to claim 1. In the operation process, all operations by the RPA robot are executed using input data different from input data used for inputting to the operation target when the RPA robot is executed.
The information processing program according to claim 1. Each of the operation processing and the error information collection and transmission processing is executed as processing of another RPA robot associated with the RPA robot,
The information processing program according to any one of claims 1 to 3. The information processing program is
causing the computer to selectively execute the processing of the RPA robot and the processing of the other RPA robot in accordance with input execution instruction information;
The information processing program according to claim 4. The program code indicating the processing procedure of the other RPA robot is automatically created using a predetermined framework when the program code indicating the processing procedure of the RPA robot is created.
6. The information processing program according to claim 4 or 5. the computer
performing an operation process for performing at least part of an operation performed by an RPA robot on an operation target during a time period when the RPA robot is not performed;
collecting error information indicating details of the execution error when an execution error occurs in the operation target in the operation processing;
transmitting the collected error information to a predetermined destination device;
An information processing method that performs processing. performing an operation process for performing at least part of an operation performed by an RPA robot on an operation target during a time period when the RPA robot is not performed;
collecting error information indicating details of the execution error when an execution error occurs in the operation target in the operation processing;
a processing unit that transmits the collected error information to a predetermined destination device;
Information processing device having

Images