Program and information processing device

Abstract

To provide a technology for a program capable of controlling an image processing device that appropriately utilizes device information of the image processing device.SOLUTION: An integrated application 22 causes a CPU 11 of a PC 1 to use at least one piece of first device information 223 associated with the integrated application 22 and stored in a memory 12 and causes the PC1 to control devices identified by the device information. The integrated application 22 acquires second device information 231 associated with a status monitor 23, which is a program different from the integrated application 22, and stored in the memory 12, and if the devices identified by the acquired second device information 231 include an untargeted device not included in the devices identified by the first device information 223, the application causes a notification of the untargeted device to be made using a user IF 13 of the PC 1.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technical field disclosed in this specification relates to a program and an information processing device that communicate with an image processing device. [Background technology]

[0002] Conventionally, there are known programs that communicate with and control image processing devices. For example, Patent Document 1 discloses a configuration in which a status monitor installed in a personal computer (PC) communicates with a printer, acquires the remaining amount of sheets and ink from the printer, and notifies the user about these. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-207138 Summary of the Invention [Problem to be solved by the invention]

[0004] In some cases, multiple programs capable of controlling the image processing device, such as the status monitor described above, exist in the same information processing device. In such cases, it is desirable for each program to appropriately utilize the device information of the image processing device. [Means for solving the problem]

[0005] The program developed to solve this problem is a first program executable by a computer of an information processing device having a memory unit and a communication unit, and the first program is configured to cause the computer to execute the following: a control process for controlling an image processing device identified by the first device information from the information processing device using at least one of multiple first device information stored in the memory unit in association with the first program; an acquisition process for acquiring second device information stored in the memory unit in association with a second program different from the first program; and a notification process for, if the image processing device identified by the second device information acquired in the acquisition process includes a specific image processing device that is not included in the image processing devices identified by the first device information, issuing a notification about the specific image processing device using a user interface of the information processing device.

[0006] The first program disclosed in this specification causes a computer of an information processing device to notify a specific image processing device that is not associated with the second program when the image processing device associated with the second program includes the specific image processing device. This allows a user to recognize that there is a specific image processing device that is not associated with the first program. As a result, for example, by storing device information indicating the specific image processing device in association with the first program, it is expected that the specific image processing device can be controlled by the first program.

[0007] An information processing device incorporating the program, a computer-readable storage medium storing the program, and a control method for realizing the functions of the program are also novel and useful. [Effects of the Invention]

[0008] According to the technology disclosed in this specification, a technology is realized in which a program capable of controlling an image processing device appropriately utilizes device information of the image processing device. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is an explanatory diagram illustrating a schematic configuration of an information processing device. [Figure 2] 10 is a flowchart showing the procedure of an integration process. [Figure 3] FIG. 10 is an explanatory diagram illustrating an example of a home screen. [Figure 4] 10 is a flowchart illustrating a procedure for a device control process. [Figure 5] 10 is a flowchart showing the procedure of an addition process. [Figure 6] FIG. 10 is an explanatory diagram showing an example of a dialog. [Figure 7] 10 is a flowchart illustrating a procedure for a device monitoring process. DETAILED DESCRIPTION OF THE INVENTION

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A program executed by an information processing apparatus connectable to a plurality of image processing apparatuses will be described in detail below with reference to the accompanying drawings.

[0011] As shown in FIG. 1, a personal computer (hereinafter referred to as "PC") 1 of this embodiment includes a controller 10 including a CPU 11 and a memory 12. The PC 1 is an example of an information processing device. The controller 10 is an example of a computer, and the memory 12 is an example of a storage unit. The PC 1 also includes a user interface (hereinafter referred to as "user IF") 13 and a communication interface (hereinafter referred to as "communication IF") 14, which are electrically connected to the controller 10. The communication IF 14 is an example of a communication unit. Note that the controller 10 in FIG. 1 is a collective term for hardware and software used to control the PC 1, and does not necessarily represent a single piece of hardware that actually exists in the PC 1.

[0012] The CPU 11 executes various processes in accordance with programs read from the memory 12 and based on user operations. The memory 12 stores various programs and various data. The memory 12 includes an auxiliary storage device such as a ROM or HDD, and a main storage device such as a RAM. The various programs are stored in, for example, the auxiliary storage device of the memory 12. The CPU 11 loads the various programs from the auxiliary storage device to the main storage device, and executes various processes in accordance with the loaded programs.

[0013] The memory 12 is also used as a work area when various processes are executed. A buffer provided in the CPU 11 is also an example of a memory. The memory 12 is not limited to a ROM, RAM, HDD, etc. built into the PC 1, but may also be a storage medium readable and writable by the CPU 11, such as a CD-ROM, DVD-ROM, or other recording medium.

[0014] The user IF 13 includes hardware for displaying a screen for notifying the user of information and hardware for accepting user operations. The user IF 13 may include a combination of a display capable of displaying information and a mouse, keyboard, or the like having an operation acceptance function, or may include a touch panel having a display function and an operation acceptance function.

[0015] The communication IF 14 includes hardware for communicating with external devices. The communication IF 14 is compatible with a communication standard such as Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The PC 1 may include multiple communication IFs 14 compatible with multiple communication standards.

[0016] The PC 1 of this embodiment can be connected to one or more devices 3 via the communication IF 14, for example, as shown in FIG. 1. Each device 3 is a device capable of printing or reading an image, and is an example of an image processing device. The devices 3 are, for example, a printer, scanner, copier, multifunction device, or facsimile machine. Note that the devices 3 may be the same model or different models.

[0017] The PC 1 and each device 3 communicate wirelessly in accordance with the Wi-Fi standard via, for example, an access point 100. The form of communication between the PC 1 and each device 3 may be wired LAN communication, direct wireless communication without going through the access point 100, wired communication based on the USB standard, or remote communication via the Internet. FIG. 1 shows a state in which devices A and B are connected to the PC 1, and a device C is about to be newly connected to the PC 1.

[0018] 1, for example, an operating system (hereinafter referred to as "OS") 21, an integrated application 22, and a status monitor 23 are stored in the memory 12 of the PC 1. The OS 21 is, for example, Windows (registered trademark), macOS (registered trademark), Linux (registered trademark), iOS (registered trademark), or Android (registered trademark).

[0019] The integrated application 22 includes a device monitoring program 221, a device control program 222, integrated application device information (hereinafter referred to as "first device information") 223, and a non-target list 224. The integrated application 22 is an example of a first program. The first device information 223 is information stored in the memory 12 in association with the integrated application 22, and indicates devices that can be controlled by the integrated application 22. The first device information 223 is an example of first device information.

[0020] The status monitor 23 includes device information for the status monitor (hereinafter referred to as "second device information") 231. The status monitor 23 is an example of a second program. The second device information 231 is information stored in the memory 12 in association with the status monitor 23, and is information indicating each device set as a source from which the status is acquired by the status monitor 23. The second device information 231 is an example of second device information.

[0021] The first device information 223 and the second device information 231 include information that identifies each device and that identifies the device. Examples of information that can identify each device include a model name, an IP address, a MAC address, and a serial number. The first device information 223 and the second device information 231 may be stored in the memory 12 in association with the respective programs. For example, if the OS 21 is Windows, the first device information 223 and the second device information 231 may be information registered in a data storage area called a "registry," or may be information included in a file stored in a directory assigned to each program.

[0022] The memory 12 also stores driver programs for controlling each device 3 connected to the PC 1. Specifically, the memory 12 stores a driver program 31 for device A (hereinafter referred to as "A driver") and a driver program 32 for device B (hereinafter referred to as "B driver"). When device C is newly connected to the PC 1, a driver program 33 for device C (hereinafter referred to as "C driver") is installed in the PC 1. Each of the driver programs 31, 32, and 33 is, for example, a printer driver or a scanner driver, and is a program capable of generating data for causing the corresponding device 3 to execute image processing, and is an example of a second program.

[0023] The device monitoring program 221 of the integrated application 22 is a program that periodically communicates with all devices 3 identified by the first device information 223 among one or more devices 3 connected to the PC 1, and acquires status information indicating the current status from each device 3. The status information acquired by the device monitoring program 221 includes, for example, capability information indicating the capabilities of the device 3, operation information indicating the operating status, remaining amount information indicating the remaining amount of consumables, connection information indicating the connection status, and setting information indicating the currently set setting values. The status information may also include page count information indicating the number of pages printed and support information regarding support. The device monitoring program 221 is a resident program that is automatically started when the OS 21 is started and performs predetermined processing in the background while the OS 21 is running.

[0024] The device control program 222 of the integrated application 22 is a program that realizes a function of controlling one device 3 out of the multiple devices 3 identified by the first device information 223. The device control program 222 can accept, for example, a user instruction to specify a device 3 to be used to execute a job. The device control program 222 can then cause the PC 1 to output, to the specified device 3, an instruction to execute a job related to image processing such as printing or scanning, or an instruction to change print settings or scan settings, for example. The device control program 222 is a non-resident program that is activated by, for example, a user operation.

[0025] The status monitor 23 is a resident program that periodically communicates with all devices 3 identified by the second device information 231 among one or more devices 3 connected to the PC 1, and acquires status information from each device 3. The status information that can be acquired by the status monitor 23 includes the same information as the status information that can be acquired by the device monitoring program 221 of the integrated application 22, and may also include some different information.

[0026] The status monitor 23 is a program provided by the same vendor as the integrated application 22, and can set the same device 3 as the control target. The integrated application 22 supports more functions than the status monitor 23, and is provided as a new program different from the status monitor 23, rather than as an upgraded version of the status monitor 23. Therefore, the integrated application 22 and the status monitor 23 can coexist. The integrated application 22 can set the device 3 as the control target independently of the status monitor 23, and the first device information 223 and the second device information 231 are information independent of each other.

[0027] However, monitoring one device 3 with both the device monitoring program 221 and the status monitor 23 is wasteful and increases the processing load. Therefore, it is preferable to monitor one device with only one of the programs. For example, if the first device information 223 includes information indicating device A and information indicating device B, it is preferable that the second device information 231 does not include information indicating device A or information indicating device B. For example, if the second device information 231 stores information indicating device A and information indicating device B, and the integrated application 22 is installed, the installer of the integrated application 22 may store the information indicating device A and information indicating device B in the first device information 223 and delete the information indicating device A and information indicating device B from the second device information 231.

[0028] Next, the procedure of the integration process, which is a process based on the device control program 222 of the integrated application 22, will be described with reference to the flowchart in Fig. 2. The integration process is executed by the CPU 11 of the PC 1 upon receiving an instruction to start the device control program 222. Note that each process and each step in the following description basically indicates processing by the CPU 11 in accordance with instructions written in the program.

[0029] In the integration process, the CPU 11 determines whether the status monitor 23 is running (S101). If it is determined that the status monitor 23 is running (S101: YES), the CPU 11 acquires device information stored in the second device information 231 (S102). S102 is an example of the acquisition process. If the status monitor 23 is running, information indicating the devices controlled by the status monitor 23 is stored in the second device information 231. The device control program 222 knows where the second device information 231 is stored. That is, the CPU 11 can acquire the second device information 231 by, for example, referring to a memory area allocated to the status monitor 23, such as a registry.

[0030] Since the status monitor 23 is a resident program, it is highly likely that the status monitor 23 is running if the PC 1 is running, but it may be able to accept an instruction to stop it. In that case, in S101, the CPU 11 may determine whether the status monitor 23 is installed, instead of determining whether the status monitor 23 is running. The CPU 11 may also determine whether the second device information 231 includes information on one or more devices.

[0031] Then, the CPU 11 determines whether there is a non-target device, which is a device whose information is included in the second device information 231 but not included in the first device information 223 (S103). A device whose information is not included in the first device information 223 is not a control target of the integrated application 22 even if it can be set as a control target of the device monitoring program 221. A non-target device is a device that is a control target of the status monitor 23 but is not a control target of the integrated application 22.

[0032] For example, if a new device C is connected to the PC 1 after the integrated application 22 is installed, a C driver 33 (see FIG. 1) for the device C is installed on the PC 1. If the device C and the C driver 33 are sold before the integrated application 22, the installer for the C driver 33 may store information about the device C in the PC 1 as a control target of the status monitor 23, but may not store the device C as a control target of the integrated application 22. In other words, a situation may arise in which information about the device C is stored in the second device information 231 but not in the first device information 223. In this case, the device C is an example of a specific image processing device.

[0033] Furthermore, when it is determined that the status monitor 23 is not running (S101: NO), the CPU 11 may make the determination in S103 based on, for example, whether or not information about a device whose information is not included in the first device information 223 is stored in the memory 12. For example, the CPU 11 may make the determination in S103 based on whether or not a device driver for a device whose information is not included in the first device information 223 is installed in the PC 1.

[0034] Even if a new device C is connected to the PC 1 after the integrated application 22 is installed, if the status monitor 23 has been uninstalled or is stopped, the C driver 33 for the device C cannot register information about the device C in the status monitor 23. In this case, information about the device C is not stored in either the second device information 231 or the first device information 223, but is stored in a storage area of ​​the memory 12 allocated to the C driver 33, such as a registry, as information about devices to be controlled by the C driver 33. Therefore, the CPU 11 may obtain information held by the C driver 33 and determine the presence or absence of non-target devices based on the information.

[0035] When it is determined that there is a non-target device (S103: YES), the CPU 11 determines whether information about the non-target device is registered in the non-target list 224 (S105). The non-target list 224 is a list of devices for which an instruction not to include the device in the control targets of the integrated application 22 has been accepted. The non-target list 224 is an example of a confirmed list. Even if a device can be controlled by the integrated application 22, the user can issue an instruction not to include the device in the control targets of the integrated application 22, for example, when controlling the device using another program. The procedure for registering the device in the non-target list 224 will be described later.

[0036] If it is determined that the device is not registered in the non-target list 224 (S105: NO), the CPU 11 adds a badge to the "Add Product" button (S106) and causes the user IF 13 to display a home screen (S107). The home screen is an initial screen that is displayed first when the device control program 222 is started. For example, as shown in FIG. 3, a home screen 70 includes a print icon 71, a scan icon 72, a device name display field 73, a status display field 74, a remaining ink level display field 75, an "Add Product" button 76, and the like. S107 is an example of a display process, and the combination of S106 and S107 is an example of a notification process. The "Add Product" button 76 is an example of a specific operation object.

[0037] The print icon 71 is used when causing the device to be controlled to print. The scan icon 72 is used when causing the device to be controlled to read an image. The device name display field 73 displays the model name of the selected device as well as its IP address. The device name display field 73 may also be configured as a pull-down menu, and may display a list of devices whose information is included in the first device information 223. The CPU 11 can accept the selection of one device from the listed devices, thereby accepting the designation of the device to be controlled by the device control program 222.

[0038] The "Add Product" button 76 is a button that accepts an instruction to add a device whose information is not included in the first device information 223 as a device that can be controlled by the integrated application 22. Since the badge has been added in S106, the "Add Product" button 76 is displayed in a display mode in which a badge 761 is attached, as shown in FIG. 3. An operation on the "Add Product" button 76 in a state in which the badge 761 is attached is an example of a specific operation, and the home screen 70 including the "Add Product" button 76 in a state in which the badge 761 is displayed is an example of a screen that can accept a specific operation.

[0039] By adding and displaying badge 761, CPU 11 can notify the user that there is information on "Add Product" button 76 that should draw the user's attention, and can prompt the user to operate "Add Product" button 76. In other words, by adding badge 761, CPU 11 can notify the user that there is an addable device. Note that, instead of adding badge 761, CPU 11 may, for example, add and display a speech bubble, change the color of button 76, or cause button 76 to blink. Furthermore, instead of adding and displaying badge 761 or the like on "Add Product" button 76, CPU 11 may add and display a dedicated button on home screen 70.

[0040] Then, the CPU 11 accepts an operation on the displayed home screen 70. The CPU 11 determines whether the accepted instruction is an instruction to terminate the device control program 222 (S108). If it is determined that an instruction to terminate has not been accepted (S108: NO), the CPU 11 executes device control processing (S111). The procedure of the device control processing will be described with reference to the flowchart of FIG. 4.

[0041] In the device control process, the CPU 11 determines whether the location on the home screen 70 where the operation was received is the device name display field 73, an icon indicating an instruction to start image processing such as the print icon 71 or the scan icon 72, or the "Add product" button 76 (S201). Note that the home screen 70 includes various other objects in addition to these, but in this specification, a description of the procedure when an operation on another object is received will be omitted.

[0042] When it is determined that an operation on the "Add Product" button 76 has been accepted (S201: Add Product), the CPU 11 determines whether or not a badge has been added to the "Add Product" button 76 (S211). When it is determined in the above-described integration process (see FIG. 2) that there is a non-target device that is not registered in the non-target list 224 (NO in S105), the CPU 11 adds a badge 761 to the "Add Product" button 76 in S106.

[0043] If it is determined that a badge has been added (S211: YES), the CPU 11 executes an addition process (S212). The procedure of the addition process will be described with reference to the flowchart of FIG.

[0044] In the addition process, the CPU 11 displays a dialog box overlaid on the home screen 70 (S301). For example, as shown in FIG. 6, the CPU 11 displays the dialog box 80 including a message indicating that there is a non-target device, an "Add" button 81, and a "Do not add" button 82. The "Add" button 81 is a button for receiving an instruction to add the non-target device to the control targets of the integrated application 22. The "Do not add" button 82 is a button for receiving an instruction not to add the non-target device to the control targets of the integrated application 22. The dialog box 80 may also display information indicating the non-target device.

[0045] Then, the CPU 11 receives a user instruction on whether or not to add the non-target device as a control target of the integrated application 22 through an operation on the displayed dialog 80 (S302). S302 is an example of a selection receiving process. Whether or not to add the non-target device as a control target of the integrated application 22 is determined through a user operation. Therefore, unlike the case where the non-target device is automatically added, it is possible to prevent the non-target device from being added at a timing unintended by the user and to prevent a device unintended by the user from being set as a control target of the integrated application 22.

[0046] When it is determined that an operation on the "Add" button 81 has been accepted (S302: Add), the CPU 11 adds information about the non-target device to the first device information 223 (S305). S305 is an example of a first storage process. By adding the information about the non-target device to the first device information 223, the non-target device becomes one of the devices that can be controlled by the integrated application 22.

[0047] As a result, this non-target device is included in the devices to be displayed by operating the device name display field 73 on the home screen 70 (see FIG. 3), and can be specified as a device to execute a job by the device control program 222. Furthermore, this non-target device is included in the devices to be controlled by the device monitoring program 221, and is constantly monitored. Note that the device monitoring program 221 may read the first device information 223 when the PC 1 is restarted and update the devices to be monitored, or may periodically read the first device information 223 and automatically update the devices to be monitored.

[0048] After executing S305, the CPU 11 deletes the information of the non-target device that was added to the first device information 223 from the second device information 231 (S306). As a result, the non-target device is excluded from the control targets of the status monitor 23. S306 is an example of exclusion processing. In other words, the CPU 11 moves the information of the non-target device from the first device information 223 to the second device information 231. After this, the non-target device will not be subject to monitoring by the status monitor 23.

[0049] It should be noted that the CPU 11 skips S306 if the information on the non-target device is not included in the second device information 231. The CPU 11 leaves the information on the device to be controlled by the device driver stored in the memory 12, for example.

[0050] On the other hand, if it is determined that an operation on the "Do not add" button 82 has been accepted (S302: Do not add), the CPU 11 registers information about the non-target device in the non-target list 224 (S308). S308 is an example of a second storage process. The information about the non-target device in this case is an example of specified device information. In this case, even if information about the non-target device is stored in the second device information 231, the CPU 11 does not delete that information. Therefore, the non-target device will continue to be a target for monitoring by the status monitor 23 thereafter.

[0051] As described above, the CPU 11 does not subject a device registered in the non-target list 224 to additional processing even if the device is a non-target device. The CPU 11 does not recheck a device for which the CPU 11 has received a user instruction not to subject the device to control by the integrated application 22, thereby reducing the possibility of the user feeling uncomfortable.

[0052] After S306 or S308, the CPU 11 hides the badge 761 added to the "Add Product" button 76 (S311). If an operation on the "Add Product" button 76 with the badge added is accepted, there is no need to issue a warning again. Furthermore, the CPU 11 closes the dialog 80 displayed in S301 (S312), ends the addition process, and returns to the device control process.

[0053] Returning to the description of the device control process in Fig. 4, if it is determined that an operation on the "Add Product" button 76 has been accepted when no badge has been added (S211: NO), the CPU 11 performs a device search (S213). Specifically, the CPU 11 causes the PC 1 to transmit a device search signal and receive a response signal.

[0054] A device that can be controlled by the integrated application 22 can transmit a response signal in response to a device search signal transmitted from the PC 1. Based on the received response signal, the CPU 11 can determine whether there is a device whose information is not included in the first device information 223. If there is a device whose information is not included in the first device information 223, the CPU 11 may automatically add the device, or may display a dialog box such as that shown in FIG. 6 to allow the user to select whether or not to add the device.

[0055] Furthermore, when it is determined that an operation on the device name display field 73 on the home screen 70 has been accepted (S201: device name), the CPU 11 displays a list of all devices whose information is stored in the first device information 223 (S221), and accepts the user's designation for one of the devices (S222). S222 is an example of designation processing. The CPU 11 determines the device designated by the user as the device that will execute image processing in accordance with subsequent instructions.

[0056] If the specified device is changed from the previously specified device, the CPU 11 changes the display in the status display field 74 and the ink level display field 75 on the home screen 70 to display information about the newly specified device. When the CPU 11 receives a device designation, it may acquire status information from the specified device, even if not periodically.

[0057] Furthermore, when it is determined that an operation on an icon indicating an instruction to start image processing has been accepted (S201: Icon), the CPU 11 determines whether an instruction to execute image processing has been accepted (S231). Note that after accepting an operation on each icon and starting the image processing procedure, the CPU 11 may be able to accept an instruction to change, for example, print settings or scan settings. In this case, after accepting an operation on each icon, the user can perform an operation to change the settings, confirm the settings, and then input an execution instruction.

[0058] If it is determined that an instruction to execute image processing has been received (S231: YES), the CPU 11 transmits a command to the specified device to instruct the device to execute the image processing (S232). Upon receiving the command, the device executes a job related to the instructed image processing. S232 is an example of job execution processing and an example of control processing.

[0059] After any one of S212, S213, S222, and S232, the CPU 11 ends the device control process and returns to the integration process.

[0060] Returning to the description of the integration process in Fig. 2, after the device control process in S111, the CPU 11 proceeds to S107 and displays the home screen 70 (see Fig. 3) again. If an operation on the "Add Product" button 76 has been accepted in the device control process, the CPU 11 displays the home screen 70 without the badge 761 added.

[0061] Furthermore, if it is determined that there are no non-target devices (S103: NO), or if it is determined that information about a non-target device is registered in the non-target list 224 (S105: YES), the CPU 11 displays the home screen 70 in a state where the badge 761 has not been added (S107). Even on the home screen 70 in a state where the badge 761 has not been added, the CPU 11 can accept an operation by the user, and can execute processing based on the user operation, as described in the device control processing (see FIG. 4).

[0062] If it is determined that the end instruction has been received on the currently displayed home screen 70 (S108: YES), the CPU 11 hides the home screen 70 and ends the integration process. That is, the CPU 11 ends the processing of the device control program 222.

[0063] Next, the procedure of the device monitoring process by the device monitoring program 221 will be described with reference to the flowchart in Fig. 7. As described above, the device monitoring program 221 is a resident program in the integrated application 22. That is, this device monitoring process is executed by the CPU 11 of the PC 1 based on the device monitoring program 221 when the PC 1 is started up.

[0064] In the device monitoring process, the CPU 11 determines whether it is a regular interval (S401). If it is determined that it is a regular interval (S401: YES), the CPU 11 acquires status information from each device whose information is stored in the first device information 223 (S402). S402 is an example of a status acquisition process.

[0065] The periodic timing for acquiring the status information may be different for each device or may be the same for each device. The time interval for acquiring the status information may be uniform or may be different for each device. The CPU 11 acquires the status information for all devices whose information is stored in the first device information 223 at the respective timings.

[0066] After S402, or if it is determined that it is not a regular timing (S401: NO), the CPU 11 determines whether there is information that needs to be notified to the user (S405). For example, if status information could not be acquired or an error or warning has occurred in the device, the CPU 11 determines that a notification is necessary.

[0067] If it is determined that notification is necessary (S405: YES), the CPU 11 displays notification information as a pop-up (S406). After S406, or if it is determined that notification is not necessary (S405: NO), the CPU 11 proceeds to S401 and repeats the determinations of S401 and S405. The device monitoring process is an example of monitoring processing and an example of control processing.

[0068] As described above in detail, when a device that is not included in the first device information 223 is stored in the second device information 231 in association with the status monitor 23, the integrated application 22 causes the PC 1 to notify the user of the non-target device. This allows the user to recognize that there is a device that is not associated with the integrated application 22. As a result, for example, if a non-target device that is not associated with the integrated application 22 is stored in association with the integrated application 22, it can be expected that the non-target device will be controllable by the integrated application 22.

[0069] It should be noted that the present embodiment is merely an example and does not limit the present invention in any way. Therefore, the technology disclosed in this specification can naturally be improved and modified in various ways without departing from the spirit of the present invention. For example, an example of an information processing device may be, instead of a PC 1, a tablet computer or a smartphone.

[0070] Furthermore, the display screens illustrated in the embodiments are merely examples and are not limited to the illustrated examples. For example, the number of devices that can be controlled by the integrated application 22 and the status monitor 23 is not limited to three.

[0071] In the embodiment, all devices whose information is stored in the first device information 223 are set as monitoring targets by the device monitoring program 221. However, it is also possible to accept a designation of whether or not to set each device stored in the first device information 223 as a monitoring target. Regarding the monitoring targets by the status monitor 23, it is also possible to accept a designation of whether or not to set each device stored in the second device information 231 as a monitoring target. Furthermore, the first device information 223 and the second device information 231 do not need to include information indicating the device. In other words, there may be no devices controlled by the integrated application 22 or the status monitor 23.

[0072] Also, for example, in the embodiment, the CPU 11 starts the execution of the integration process (see FIG. 2) when the device control program 222 is started, and determines whether or not there are any non-target devices (S103), but the timing for determining whether or not there are any non-target devices is not limited to this. The process may be executed when a predetermined condition is met, for example, every day, every predetermined number of times the program is started, or a predetermined time has passed since the previous execution, or may be executed in response to a user instruction.

[0073] Furthermore, in the embodiment, when a non-target device is present, the PC 1 notifies the user by using a badge or the like, and then stores the non-target device in the first device information 223 based on a user instruction in the dialog 80 (see FIG. 6). However, the dialog 80 may not be displayed and the instruction may not be received. For example, the CPU 11 may store the non-target device in the first device information 223 upon receiving a user operation on a button to which a badge has been added. In that case, the addition process (see FIG. 5) may consist of only S305, S306, and S311. Alternatively, when a non-target device is present, the CPU 11 may automatically store information about the device in the first device information 223 and then notify the user.

[0074] Furthermore, for example, the integrated application 22 and the status monitor 23 may have different device models that can be set as control targets. For example, if a device connected to the PC 1 is a model that can be set as a control target of the status monitor 23 but cannot be set as a control target of the integrated application 22, it is desirable to include information about the device in the second device information 231, not in the first device information 223. When the CPU 11 determines YES in S103 of the integration process (see FIG. 2), the CPU 11 may determine whether the model can be set as a control target of the integrated application 22 based on the model information of the non-target device. When the CPU 11 determines that the model cannot be set as a control target of the integrated application 22, the CPU 11 may register the device in the non-target list 224 and determine YES in S105.

[0075] Furthermore, for example, the device monitoring program 221 and the device control program 222 may be one program. For example, the device monitoring program 221 may also have a function for displaying the home screen 70.

[0076] Furthermore, in any flowchart disclosed in the embodiments, the execution order of multiple processes in any multiple steps can be changed or they can be executed in parallel as long as no contradiction occurs in the processing content.

[0077] The processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. The processes disclosed in the embodiments may be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method. [Explanation of symbols]

[0078] 1 PC 3 Devices 11 CPU 12 Memory 13 User Interface 14 Communication Interface

Claims

1. A first program executable by a computer of an information processing device having a storage unit and a communication unit, The first program causes the computer to a control process for controlling, from the information processing device, an image processing device identified by the first device information by using at least one of a plurality of pieces of first device information stored in the storage unit in association with the first program; an acquisition process of acquiring second device information stored in the storage unit in association with a second program different from the first program; a notification process for performing a notification regarding a specific image processing device using a user interface of the information processing device when the image processing devices identified by the second device information acquired in the acquisition process include a specific image processing device that is not included in the image processing devices identified by the first device information; Execute The first program is configured as follows.

2. 2. A first program according to claim 1, the control process includes a job execution process for causing a designated image processing device to execute a job related to image processing; The first program causes the computer to a first storage process of storing first device information corresponding to the specific image processing device in the storage unit in association with the first program; a designation process for accepting designation of an image processing device to execute the job from among the image processing devices identified by the plurality of pieces of first device information; Execute The first program is configured as follows.

3. 2. A first program according to claim 1, the control process includes a monitoring process for monitoring an image processing device set as a control target; The first program causes the computer to executes a first storage process of storing first device information corresponding to the specified image processing device in the storage unit in association with the first program; the monitoring process includes a status acquisition process of acquiring information indicating a status from the image processing devices identified by the plurality of pieces of first device information stored in the storage unit; The first program is configured as follows.

4. The first program according to claim 3, In the acquisition process, acquiring the second device information indicating each image processing device set as a status acquisition source of the second program capable of causing the computer to acquire the status of the image processing device; The first program is configured as follows.

5. The first program according to claim 4, The first program causes the computer to after the first storage process is executed, an exclusion process is executed to exclude the specific image processing device from the control targets of the second program; The first program is configured as follows.

6. 2. A first program according to claim 1, The first program causes the computer to When the specific image processing device is present, a selection receiving process can be executed to receive, via the user interface, a selection of whether or not to add the specific image processing device; when the selection of adding the specific image processing device is accepted in the selection accepting process, a first storage process is executed to store first device information corresponding to the specific image processing device in the storage unit in association with the first program; When the selection of not adding the specific image processing device is accepted in the selection accepting process, the first storage process is not executed. The first program is configured as follows.

7. 7. A first program according to claim 6, The first program causes the computer to When the selection acceptance process accepts the selection of not adding the specific image processing device, the first storage process is not executed, and a second storage process is executed to store specific device information indicating the specific image processing device in a confirmed list; The first program further includes: When the specific image processing device is included in the image processing devices identified by the second device information acquired in the acquisition process, If the specified device information is not registered in the confirmed list, the selection acceptance process is executed. If the specified device information is registered in the confirmed list, the selection acceptance process is not executed. The first program is configured as follows.

8. 7. A first program according to claim 6, The first program causes the computer to Executing a display process for displaying a screen capable of accepting a specific operation using the user interface; executes the selection receiving process when the specific operation is received via the user interface in a state where the specific image processing device is included in an image processing device identified by the second device information acquired in the acquisition process; When the selection of adding the specific image processing device is accepted in the selection accepting process, the first storage process is executed; When the selection of not adding the specific image processing device is accepted in the selection accepting process, the first storage process is not executed. The first program is configured as follows.

9. The first program according to claim 8, the specific operation is an operation on a specific operation object included on the screen, In the notification process, a display mode in which a badge is attached to the specific operation object to notify that the specific image processing device can be added; The first program is configured as follows.

10. 2. A first program according to claim 1, In the acquisition process, acquiring the second device information indicating each image processing device set as a status acquisition source of the second program capable of causing the computer to acquire the status of the image processing device; The first program is configured as follows.

11. 2. A first program according to claim 1, In the acquisition process, acquiring the second device information stored in the storage unit in association with the second program capable of generating data for causing the image processing device to execute image processing; The first program is configured as follows.

12. 12. An information processing apparatus comprising: the storage unit in which the first program according to claim 1 is stored.

Images