JP2021022166A - Information processing apparatus, control method, and program - Google Patents

Abstract

To provide a more convenient method for handling a situation where an information processing apparatus cannot communicate with a printer.SOLUTION: An information processing apparatus includes: a first acquisition means for acquiring information on a printer over a network; a second acquisition means for acquiring information on print queues managed in the information processing apparatus; and specifying a means for specifying a print queue corresponding to the printer, when there is no print queue which can communicate with the printer in the print queues managed in the information processing apparatus, on the basis of the information acquired by the first acquisition means and the information acquired by the second acquisition means.SELECTED DRAWING: Figure 6

Description

The present invention relates to an information processing device, a control method, and a program.

In an environment in which the information processing device and the printing device are connected to the same network, the information processing device can control the printing device via the network. On the other hand, Patent Document 1 discloses a solution when the information processing device and the printing device cannot communicate with each other via a network.

Japanese Patent No. 4343673

In recent years, as a method for improving a situation in which communication between an information processing device and a printing device has become impossible, a more convenient improvement method is required.

In order to solve the above-mentioned problems, the information processing apparatus of the present invention is an information processing apparatus capable of communicating with a printing apparatus, and is a first acquisition means for acquiring information of the printing apparatus via a network. When there is no print queue that can communicate with the printing device among the second acquisition means for acquiring the information of the print queue managed by the information processing device and the print queue managed by the information processing device, the said Based on the information acquired by the first acquisition means and the information acquired by the second acquisition means, the specific means for specifying the print queue corresponding to the printing device, and the port setting information of the specified print queue. Is provided with a changing means for changing the port setting information capable of communicating with the printing device.

INDUSTRIAL APPLICABILITY According to the present invention, it is possible to improve communication with higher convenience.

It is a figure which shows the example of the apparatus configuration. It is a hardware block diagram of an information processing apparatus. It is a hardware block diagram of a printing apparatus. It is a software configuration diagram of an information processing apparatus. It is a functional block diagram of an application. It is a flowchart which shows the process executed in an information processing apparatus. This is an example of the UI screen of the application. It is a flowchart which shows the comparison process of the information of a printing apparatus and the information of a print queue. This is an example of the UI screen of the application. It is a flowchart which shows the determination process of the print queue to be repaired. This is an example of the UI screen of the application. It is a flowchart which shows the port repair process in 1st Embodiment. This is an example of the UI screen of the application. It is a flowchart which shows the communication possibility determination processing. It is a flowchart which shows the communication possibility determination processing of a WSD port. It is a flowchart which shows the communication possibility determination processing of a host name port. It is a flowchart which shows the determination process of the repair priority. This is an example of the management table of priority determination parameters inside the application. It is a flowchart which shows the port creation process. It is a flowchart which shows the port repair process. It is a flowchart which shows the communication possibility determination processing. This is an example of the UI screen of the application.

Hereinafter, the present embodiment will be described with reference to the accompanying drawings. The configuration shown in the following embodiments is only an example, and the present invention is not limited to the illustrated configuration.

First, the overall configuration of the printing system according to the present embodiment will be described. FIGS. 1A and 1B show the overall configuration of a printing system in which the connection mode between the printing device and the information processing device which is the host device thereof is different.

The printing system shown in FIG. 1 (a) includes three printing devices 101 to 103 having a wireless LAN (Local Area Network) communication function, and two information processing units capable of communicating with these three printing devices via a wireless LAN. It is composed of devices 104 and 105. In FIG. 1A, the printing devices 101 to 103 and the information processing devices 104 and 105 are connected to the wireless LAN via the access point 106, and each information processing device prints via the wireless LAN. The devices 101 to 103 can be controlled.

In the printing system shown in FIG. 1B, three printing devices 101 to 103 and two information processing devices 104 and 105 are connected via a wired LAN cable 107.

<Configuration of printing device>
FIG. 2 is a diagram showing an example of the hardware configuration of the printing devices 101 to 103.

Each printing device is composed of a network interface 201, a USB (Universal Serial Bus) interface 202, a RAM 203, a ROM 204, a CPU 205, and a print engine 206. Then, each of these parts is connected to each other via the system bus 207.

The network interface 201 is an interface that controls the connection to the wireless LAN via the access point 106 or the connection to the wired LAN via the wired LAN cable 107. The USB interface 202 is an interface that controls a USB connection via a USB cable.

The RAM 203 is used as a main memory and a work memory of the CPU 205, and functions as a reception buffer for temporarily storing received print data and a storage area for storing various data. The print engine 206 prints based on the print data stored in the RAM 203. The print engine 206 may perform the printing process by the inkjet method or the printing process by the electrophotographic method. The ROM 204 stores various control programs and data used by each control program, and the CPU 205 controls each part of the printing apparatus according to these control programs. The hardware configuration described above is an example, and the hardware configuration of the printing apparatus is not limited to the above example.

In addition, the printing devices 101 to 103 support the TCP / IP protocol, and also have a protocol function and name resolution (a function of specifying an IP address from a computer name, a domain name, etc.) for setting a connection with another device, for example. ) Can be used. The function of the protocol is, for example, the WS-Discovery function which is one of the functions of WSD (Web Services on Devices) which is a standard protocol of Windows (registered trademark) OS. According to WS-Discovery, it is possible to detect a device connected to a network based on an identifier (UUID (Universally UUID) that can be uniquely identified for each device. Further, for name resolution, for example, DNS (Domain Name System) that manages the correspondence between the IP address and the domain name can be used. Further, LLMNR (Link-Local Multitactic Name Resolution) that can resolve the name of a neighboring network device when DNS does not exist in the network may be used. The WSD function, LLMNR function, and DNS function of the printing devices 101 to 103 can be enabled / disabled by the user directly operating the printing devices 101 to 103. Further, it is assumed that the UUID is set in the printing devices 101 to 103, and the UUID version is "version 1" in which the UUID is composed of the MAC address of the printing devices 101 to 103 and the UUID generation time.

<Configuration of information processing device>
FIG. 3 is a diagram showing an example of the hardware configuration of the information processing apparatus 104/105. The information processing device 104/105 is composed of an input interface 301, a CPU 302, a ROM 303, a RAM 304, an external storage device 305 such as an HDD, an output interface 306, a network interface 307, and a USB interface 308. Then, each of these parts is connected to each other via the system bus 309.

The input interface 301 is an interface that controls the connection with a pointing device 310 such as a mouse and an input device such as a keyboard 311. The output interface 306 is an interface that controls the connection with the display unit 312 of a liquid crystal display or the like. The network interface 307 is an interface that controls the connection to the wireless LAN via the access point 106 or the connection to the wired LAN via the wired LAN cable 107. The USB interface 308 is an interface that controls a USB connection via a USB cable.

The initialization program is stored in the ROM 303, and the application group, the OS (Operating System), the printer driver, and various other data are stored in the external storage device 305. The RAM 304 is used as a work memory when the CPU 302 executes various programs. The above-mentioned hardware configuration is an example, and the hardware configuration of the information processing apparatus 104/105 is not limited to the above-mentioned example.

FIG. 4 is a diagram showing software configurations of the information processing devices 104 and 105 according to the present embodiment. The information processing device 104 includes an application 501 that can be executed in the information processing device 104. The application 501 is software for repairing the destination port setting of the print queue in which the print data cannot be transmitted to the printing devices 101 to 103 due to a defect in the destination port setting. The application 501 queries the available print queue 402 via the print system 401 provided by the OS, and accesses the appropriate print queue 402 _n (n is any of 1 to N) based on the result of the query.

Further, the application 501 queries the available printer driver 405 via the printing system 401, and accesses an appropriate printer driver 405 _p (p is any of 1 to P) based on the result of the query. The printer driver 405 _p includes a support model identifier 406 _p including a model name or a model name of the printing device, and a driver type identifier 407 _p such as GDI, XPS, and FAX as an identifier.

Application 501 queries the available ports 408 via the printing system 401 and accesses the appropriate port 408 _m (m is any of 1 to M) based on the query results. The port 408 _m includes a port type identifier 409 _m such as USB, TCP / IP, and WSD, and a network identifier 410 _m such as an IP address or a host name.

Each print queue 402 _n (n is any of 1 to N) is associated with a printer driver and port. The print queue 402 _n includes printer driver reference information 403 and port reference information 404 for identifying the associated printer driver and port.

In Figure 4, as an example, the printer driver reference information 403 ₁ indicates to be associated with a printer driver 405 _1, port reference information 404 ₁ indicates that associated with port _4081. Note that the printer driver reference information 403 _{1 to} 403 _N are associated with the printer drivers 405 _{1 to} 405 _P , respectively, and the port reference information 404 _{1 to} 404 _N are associated with the ports 408 _{1 to} 408 _M , respectively. Indicates that Further, in the present embodiment, the port may be referred to as port setting information. Then, the application 501 can refer to and acquire the support model identifier 406 _p and the driver type identifier 407 _p , which are the setting information of the printer driver 405 _p specified by the printer driver reference information 403 _n included in the print queue. Further, the application 501 can refer to and acquire the port type identifier 409 _m and the network identifier 410 _m , which are the setting information of the port 408 _m specified by the port reference information 404 _n included in the print queue.

When the port type identifier 409 _m is WSD, the port 408 _m is defined as a "WSD port". For the port defined as the "WSD port", the UUID of the printing device is set to the network identifier 410 _m .

Further, when the port type identifier 409 _m is TCP / IP and the network identifier 410 _m is an IP address, the port 408 _M is defined as a “fixed IP address port”. If the port type identifier 409 _m is TCP / IP and the network identifier 410 _m is the DNS or LLMNR host name, then port 408 _m is defined as the "hostname port". In the present embodiment, the port in the information processing apparatus 104/105 will be described as being classified into any of the above-mentioned "WSD port", "fixed IP address port", and "host name port". However, there is no problem even if the information processing apparatus 104/105 includes other types of ports.

<Application configuration>
FIG. 5 is a block diagram showing a function realized by the CPU 302 of the information processing device 104/105 reading and executing the application 501 stored in the external storage device 305, for example. As an example, the application 501 includes a printing device search function 502 to a repair result output function 511. The CPU 302 executes the subsequent processing by using each function provided in the application 501. The port repair process in the present embodiment is a process of recovering communication with a printing device desired by the user by using a certain print queue 402 _n . By starting a document creation application or a spreadsheet application different from the application 501, the user generates application data, selects a print queue corresponding to a desired printing device, and attempts a printing instruction. At this time, communication with a desired printing device may not be possible depending on the setting information of the print queue selected by the user. Application 501 is used to repair these cases.

<Processing flow>
Hereinafter, the flow of processing executed by the information processing apparatus 104/105 will be described. The processing examples shown below may be used alone or in combination.

The process described below is realized, for example, by the CPU 302 loading the program corresponding to the application 501 stored in the external storage device 305 into the RAM 304 and executing the program.

<First Embodiment>
The processing flow of the application 501 according to the first embodiment of the present invention will be described with reference to the flowchart of FIG. In this embodiment, application 501 is executed by the information processing apparatus 104.

First, in S601, the CPU 302 searches for and detects a printing device connected to the network to which the information processing device 104 is currently connected. For the search of the printing device, for example, a device search function by a TCP / IP protocol such as SNMP (Simple Network Management Protocol) may be used. When the printing device is detected, the CPU 302 displays a list of the detected printing devices on the display unit 312 in a format that can be selected by the user in S602. FIG. 7 shows an example of the UI screen for list display. In FIG. 7, the user selects the check box at the left end of the printing device for which he / she wants to repair, that is, wants to restore communication, and then clicks the [Next] button 701. In this embodiment, it is assumed that the printing device 101 is selected.

When the CPU 302 detects that the [Next] button 701 is pressed, the CPU 302 acquires detailed network setting information of the selected printing device 101 in S603. For example, the IP address, MAC address, serial number, model name, etc. of the printing device 101 are acquired. It should be noted that these pieces of information are acquired in S601 via the network and are stored in the memory of the information processing apparatus 104. Then, the CPU 302 acquires the information corresponding to the selected printing device 101 from the memory, so that the processing of S603 is realized. In S603, the CPU 302 may acquire such information via the network.

Subsequently, the CPU 302 acquires the setting information of all the print queues 402 registered in the information processing apparatus 104 in S604. For example, the CPU 302 acquires the support model identifier 406 _p and the driver type identifier 407 _p from the printer driver reference information 403 _n set in the print queue 402 _n . Further, the CPU 302 acquires the port type identifier 409 _m and the network identifier 410 _m from the port reference information 404 _n . The network setting information of the printing apparatus 101 acquired in S603 includes information corresponding to at least some of the elements of the setting information of the obtained print queue 402 _n in S604. For example, the model name of the printing apparatus 101 corresponds to the supported model identifier 406 _p . Further, the IP address of the printing device 101 corresponds to the network identifier 410 _m when the port 408 _m specified from the port reference information 404 _n is a fixed IP address port. The same result can be obtained even when the execution order of the series of S601 to S603 and S604 described above is reversed.

Next, the CPU 302 sequentially compares the network setting information of the printing device 101 acquired in S603 with the setting information of the printing queue 402 ₁ to the printing queue 402 _N acquired in S604, and these information match. Whether or not it is determined (S605). Note that S605 will be described in detail with reference to the flowchart of FIG.

As a result of the information comparison in S605, when it is determined that the information processing device 104 has a print queue that can be printed by the printing device 101 (YES in S606), the CPU 302 determines that there is a printable print queue in S607. It is displayed on the display unit 312. An example of the UI screen at this time is shown in FIG. 9A. In FIG. 9A, in one example, the CPU 302 indicates to the user that the print queue that can be printed by the printing device 101 has been detected, and the [OK] button 901 is displayed. When the application 501 detects that the [OK] button 901 is pressed, the application 501 terminates the program. Note that FIG. 9A includes a test print button. When the user presses the test print button, the CPU 302 generates print data for test printing using the printer driver associated with the print queue determined to be Yes in S606. Then, the CPU 302 transmits the print data for test printing to the printing apparatus 101 using the port associated with the print queue determined to be Yes in S606. Further, FIG. 9A includes a check box for accepting a specification as to whether or not to set the printer to be normally used. If the print queue determined to be Yes in S606 is not specified as the printer to be normally used, the screen of FIG. 9A in which the check box is checked as the initial value is displayed. On the other hand, when the print queue determined to be Yes in S606 is already specified as the printer to be normally used, the check box and the message "Set as the printer to be normally used" may be hidden. When the OK button 901 is pressed in the state of FIG. 9A, the print queue determined to be Yes in S606 is managed in the OS as a printer to be normally used.

On the other hand, as a result of the information comparison in S605, the process when it is determined that there is no print queue that can be printed by the printing device 101 in the information processing device 104 (NO in S606) will be described. In S608, the CPU 302 detects the print queue to be repaired from all the print queues 402 in the information processing apparatus 104. S608 will be described in detail with reference to the flowchart of FIG.

As a result of the detection in S608, when the CPU 302 cannot detect any print queue to be repaired (NO in S609), the CPU 302 displays on the display unit 312 that there is no printable print queue in S610. .. An example of the UI screen at this time is shown in FIG. 9B. In FIG. 9B, in one example, the CPU 302 indicates to the user that the print queue corresponding to the printing device 101 could not be detected, and the [OK] button 902 is displayed. When the press of the [OK] button 902 is detected, the application 501 terminates the program. In this case, the user starts from the new generation of the print queue of the printing device 101.

On the other hand, when the CPU 302 detects one or more print queues to be repaired as a result of the detection in S608 (YES in S609), the CPU 302 informs the display unit 312 that the print queue settings do not match in S611. Performs display control processing to be displayed. An example of the UI screen at this time is shown in FIG. 9 (c). In FIG. 9C, in one example, the CPU 302 indicates that printing cannot be performed because the print queue settings corresponding to the printing device 101 do not match, and the [Next] button 903 is displayed. Upon detecting the pressing of the [Next] button 903, the CPU 302 displays a list of print queues to be repaired detected in S608 in S612 on the display unit 312 in a format that can be selected by the user. An example of the UI screen at this time is shown in FIG. 11 (a). In FIG. 11A, in one example, the CPU 302 lists the print queues to be repaired in a drop-down list. On this screen, the user clicks the [Next] button 1101 on the screen with the print queue to be repaired selected from the dropdown. When the CPU 302 detects that the [Next] button 1101 is pressed, it identifies the print queue to be repaired. If only one print queue to be repaired is detected, the CPU 302 selects the print queue to be repaired detected in S608 in a format other than the selected format, as shown in FIG. 11B. It may be displayed with. In FIG. 11B, the print queue to be repaired and the [Next] button 1102 are displayed on the screen. When the CPU 302 detects that the [Next] button 1102 is pressed, it identifies the print queue to be repaired. In this embodiment, it is assumed that the print queue 402 ₁ is selected.

When the print queue 402 ₁ to be repaired is specified, the CPU 302 repairs the selected print queue 402 ₁ in S613. S613 will be described in detail with reference to the flowchart of FIG. When a port is created by the process of FIG. 12, which will be described later, the CPU 302 modifies the port reference information 404 ₁ included in the print queue 402 ₁ to be repaired so as to refer to the port created in FIG. To do.

When the repair process of the print queue 402 ₁ is completed, the CPU 302 displays the repair result on the display unit 312 in S614. An example of the UI screen at this time is shown in FIGS. 13 (a) and 13 (b). When the repair failure flag described later in FIG. 19 is enabled, the CPU 302 displays FIG. 13 (b). On the other hand, if the repair failure flag is not enabled, the CPU 302 displays FIG. 13A.

FIG. 13 (a) is displayed when the repair process of the print queue 402 ₁ is successful, and FIG. 13 (b) is displayed when the repair process of the print queue 402 ₁ is unsuccessful. When the repair process is successful, in one example, the CPU 302 indicates that the print queue selected by the user in S612 has been repaired and can be printed by the printing device 101, and the screen including the [OK] button 1301 (FIG. 13 (FIG. 13). a)) is displayed. When the pressing of the [OK] button 1301 is detected, the application 501 terminates the program. When the application 501 is executed again after the repair process is successful, it is determined in S605 that there is a print queue that can be printed by the printing device 101 in the information processing device 104 (YES in S606) according to the above procedure. .. Note that FIG. 13A includes a check box for accepting a specification as to whether or not to set the printer to be normally used. For example, if the print queue to be repaired is not specified as the printer to be normally used, the screen of FIG. 13A with the check box checked as the initial value is displayed. On the other hand, if the print queue to be repaired is already specified as the default printer, the check box and the message "Set as default printer" may be hidden. When the OK button 901 is pressed in the state of FIG. 13A, the print queue to be repaired is managed in the OS as a printer normally used.

In FIG. 13B, in one example, the CPU 302 indicates that the restoration of the print queue selected by the user in S612 has failed, and displays the [OK] button 1302. When the pressing of the [OK] button 1302 is detected, the application 501 terminates the program.

When the repair is completed by the above processing, for example, the user starts another application different from the application 501. Then, when the print queue after restoration is selected and printing is instructed, the printer driver corresponding to the print queue after restoration generates print data based on the data output from other applications and transmits the print data to the printing apparatus 101. It becomes possible to do.

FIG. 8 is a flowchart for explaining the process of S605 of FIG. 6 in detail. The CPU 302 repeats the processes of S802 to S804 shown below for all the print queues 402 in the information processing apparatus 104 (S801).

First, in S802, the CPU 302 compares the model name of the printing device 101 acquired in S603 with the model name included in the support model identifier 406 _p of the print queue 402 _n acquired in S604. If the model name and the model name included in support model identifier 406 _p of the printing apparatus 101 does not match (NO in S802), CPU 302 determines that it is not the print queue the print queue is selected corresponding to the printing apparatus 101. Then, the CPU 302 selects the next print queue 402 _{n + 1} and executes S802 to S804.

On the other hand, the process when the model name of the printing apparatus 101 and the model name included in the supported model identifier 406 _p match (YES in S802) will be described. In S803, the CPU 302 determines whether or not communication with the printing device 101 can be performed using the port 408 _m corresponding to the port reference information 404 _n set in the print queue 402 _n . S803 will be described in detail with reference to the flowchart of FIG.

When it is determined in S803 that communication with the printing apparatus 101 cannot be performed using the port 408 _m (NO in S804), the CPU 302 selects the next print queue 402 _{n + 1} and executes S802 to S804.

On the other hand, when it is determined in S803 that communication with the printing device 101 is possible using the port 408 _m (YES in S804), the CPU 302 exits the loop processing and can print in the information processing device 104 in S805. Determine that there is a print queue.

If there is no print queue determined to be YES in S804 among all the print queues 402 in the information processing device 104, the CPU 302 determines in S806 that there is no printable print queue in the information processing device 104. To do.

FIG. 14 is a flowchart for explaining the process of S803 in FIG. 8 in detail. Here, the processing using the port 408 _m will be described.

First, in S1401, the CPU 302 determines the port type of the port 408 _m . This is determined from the port type identifier 409 _m and the network identifier 410 _m set for the port 408 _m . When the port type identifier 409 _m is WSD, the CPU 302 determines that the port 408 _m is a "WSD port". When the port type identifier 409 _m is TCP / IP and the network identifier 410 _m is an IP address, the CPU 302 determines that the port 408 _m is a “fixed IP address port”. If the port type identifier 409 _m is TCP / IP and the network identifier 410 _m is the DNS or LLMNR host name, the CPU 302 determines that the port 408 _m is the "host name port".

The process when the port type is determined to be "fixed IP address port" in S1401 (YES in S1402) will be described. In S1403, the CPU 302 compares the IP address of the printing apparatus 101 acquired in S603 with the IP address of the port 408 _m acquired in S604, which is the network identifier 410 _m . When the IP address of the printing device 101 and the IP address of the port 408 _m match (YES in S1404), in S1405, the CPU 302 determines that the printing device 101 can communicate with the printing device 101 using the port 408 _m .

On the other hand, when the IP address of the printing device 101 and the IP address of the port 408 _m do not match (NO in S1404), in S1406, the CPU 302 determines that communication with the printing device 101 is impossible using the port 408 _m ---.

When it is determined in S1401 that the port type is "WSD port" (NO in S1402, YES in S1407), the CPU 302 determines in S1408 whether or not it is possible to communicate with the printing device 101 using the WSD port 408 _m. To do. S1408 will be described in detail with reference to the flowchart of FIG.

When it is determined that the WSD port 408 _m can communicate with the printing device 101 (YES in S1409), in S1410, the CPU 302 can communicate with the printing device 101 using the port 408 _m ---. to decide. On the other hand, when it is determined that the WSD port 408 _m cannot communicate with the printing device 101 (NO in S1409), the CPU 302 determines in S1411 that it cannot communicate with the printing device 101 using the port 408 _m. To do.

When it is determined in S1401 that the port type is "host name port" (NO in S1402, NO in S1407), in S1412, the CPU 302 determines whether the LLMNR function of the printing apparatus 101 acquired in S603 is valid / invalid. To do. When the LLMNR function of the printing device 101 is enabled (YES in S1412), in S1413, the CPU 302 determines whether or not the host name port 408 _m can be used to communicate with the printing device 101. Note that S1413 will be described in detail with reference to the flowchart of FIG.

When it is determined that the host name port 408 _m can be used to communicate with the printing device 101 (YES in S1414), in S1415, the CPU 302 determines that the port 408 _m can be used to communicate with the printing device 101. .. On the other hand, the processing when it is determined that communication with the printing device 101 using the host name port 408 _m is impossible (NO in S1414) or when the LLMNR function of the printing device is invalid (NO in S1412) will be described. To do. In S1416, the CPU 302 determines whether the DNS function of the printing device 101 acquired in S603 is valid / invalid.

When the DNS function of the printing device 101 is enabled (YES in S1416), in S1417, the CPU 302 determines whether or not communication with the printing device 101 is possible using the host name port 408 _m . Note that S1417 will be described in detail with reference to the flowchart of FIG.

When it is determined that the host name port 408 _m can be used to communicate with the printing device 101 (YES in S1418), in S1419, the CPU 302 determines that the port 408 _m can be used to communicate with the printing device 101. .. On the other hand, the processing when it is determined that communication with the printing device 101 using the host name port 408 _m is impossible (NO in S1418) or when the DNS function of the printing device is invalid (NO in S1416) will be described. To do. In S1420, the CPU 302 determines that the printing device 101 and-cannot communicate with each other using the port 408 _m . In the above process, the CPU 302 determines whether the LLMNR / DNS function of the printing apparatus 101 is valid / invalid in S1412 and S1416. As a result, it is possible to determine whether or not the host name port can communicate faster when the LLMNR / DNS function of the printing device 101 is disabled, as compared with the case where these determinations are not made. For example, it is assumed that the LLMNR function of the printing device 101 is disabled and the DNS function is enabled. Here, when S1412 is not executed, the CPU 302 first determines whether or not it is possible to communicate with the printing device 101 by the LLMNR. Then, the CPU 302 is determined to be unable to communicate because the LLMNR function of the printing device 101 is disabled. After that, the CPU 302 determines whether or not it is possible to communicate with the printing device 101 by DNS. That is, since it is unknown whether or not the LLMNR of the printing device 101 is invalidated, the CPU 302 may uselessly determine whether or not the LLMNR can communicate with the printing device 101, and communication is performed by this process. There was a risk that the decision on whether or not to accept was prolonged. The process of FIG. 14 solves this point by executing S1412 and S1416. However, even when the determinations of S1412 and S1416 are not performed, NO is determined in S1414 / S1418 when the LLMNR / DNS function of the printing apparatus 101 is invalid. As a result, the result of determining that the LLMNR / DNS cannot communicate with the printing device 101 using the host name port 408 _m is the same.

FIG. 15 is a flowchart for explaining the process of S1408 in FIG. 14 in detail. First, in S1501, the CPU 302 determines whether the WSD function of the printing device 101 acquired in S603 is valid / invalid. When the WSD function of the printing device 101 is invalid (NO in S1501), in S1502, the CPU 302 determines that communication with the printing device 101 is impossible using the WSD port 408 _m . On the other hand, when the WSD function of the printing device 101 is enabled (YES in S1501), in S1503, the CPU 302 acquires the MAC address from the UUID set in the network identifier 410 _m of the WSD port 408 _m . Subsequently, in S1504, the CPU 302 compares the MAC address of the printing device 101 acquired in S603 with the MAC address acquired in S1503. If they do not match (NO in S1505), in S1502, the CPU 302 determines that it cannot communicate with the printing apparatus 101 using the WSD port 408 _m . On the other hand, the process when the MAC address of the printing apparatus 101 and the MAC address acquired in S1503 match (YES in S1505) will be described. In S1506, the CPU 302 uses a search module corresponding to the WSD protocol to search the printing device 101 by unicast communication based on the UUID set in the network identifier 410 _m .

If the printing device 101 is not detected in S1506 (NO in S1507), the CPU 302 determines in S1502 that it cannot communicate with the printing device 101 using the WSD port 408 _m . On the other hand, when the printing device 101 is detected in S1506 (YES in S1507), in S1508, the CPU 302 determines that it can communicate with the printing device 101 using the WSD port 408 _m . In S1501, the information comparison function 506 determines whether the WSD function of the printing device 101 is valid / invalid, so that the WSD when the WSD function of the printing device 101 is invalid as compared with the case where this determination is not made. It is possible to quickly determine whether or not the port can communicate. However, even if this determination is not made, if the WSD function of the printing device 101 is invalid, the printing device 101 will not be searched for in S1506. Therefore, finally, in S1502, the CPU 302 determines that it cannot communicate with the printing device 101 using the WSD port 408 _m .

FIG. 16 is a flowchart for explaining in detail the processes of S1413 and S1417 in FIG. First, in S1601, the CPU 302 sets the LLMNR name (in the case of S1413) or DNS name (in the case of S1417) of the printing device 101 acquired in S603 and the network identifier 410 _m of the host name port 408 _m . Compare names. If they do not match (NO in S1602), in S1603, the CPU 302 determines that it cannot communicate with the printing device 101 using the host name port 408 _m . On the other hand, when the LLMNR name or DNS name of the printing device 101 and the host name set in the network identifier 410 _m of the host name port 408 _m match (YES in S1602), the process of FIG. 16 proceeds to S1604. Then, the CPU 302 attempts name resolution with the host name set in the network identifier 410 _m of the host name port 408 _m . For example, the CPU 302 specifies a host name set in the network identifier 410 _m and transmits an IP address inquiry command by broadcasting via the network. As a result, the printing device 101 corresponding to the host name transmits the IP address as a response command. If the transmission of the inquiry command and the reception of the response command are properly executed, the name resolution is successful, and the CPU 302 can acquire the IP address of the printing device 101.

If the name resolution fails (NO in S1605), in S1603, the CPU 302 determines that it cannot communicate with the printing device 101 using the host name port 408 _m . On the other hand, the case where the name resolution is successful (YES in S1605) will be described. In S1606, the CPU 302 compares the IP address of the printing device 101 acquired in S603 with the IP address acquired by resolving the name with the host name set in the network identifier 410 _m of the host name port 408 _{m in} S1604. .. If they match (YES in S1607), in S1608, the CPU 302 determines that it can communicate with the printing device 101 using the host name port 408 _m . On the other hand, when the IP address of the printing device 101 and the IP address of the host name port 408 _m do not match (NO in S1607), in S1603, the CPU 302 cannot communicate with the printing device 101 using the host name port 408 _m. Judge.

FIG. 10 is a flowchart for explaining the process of S608 in FIG. 6 in detail. The CPU 302 repeats the processes of S1002 to S1004 shown below for all the print queues 402 in the information processing apparatus 104 (S1001).

First, in S1002, the CPU 302 compares the model name of the printing device 101 acquired in S603 with the model name (name information) included in the support model identifier 406 _p of the print queue 402 _n acquired in S604. If the model name and the model name included in support model identifier 406 _p of the printing apparatus 101 does not match (NO in S1002), it is determined not to be the print queue corresponding to the printing device 101 is changed to the next print queue _{402 n + 1} The processes of S1002 to S1004 are executed. On the other hand, when the model name of the printing device 101 and the model name included in the supported model identifier 406 _p match (YES in S1002), in S1003, the CPU 302 determines the repair priority of the print queue 402 _n . S1003 will be described in detail with reference to the flowchart of FIG. When the repair priority of the print queue 402 _n is determined, in S1004, the CPU 302 adds the print queue 402 _n to the list of print queues to be repaired, changes the print queue 402 _{n to the} next print queue 402 _{n + 1} , and performs the processing of S1002 to S1004. Execute. After these processes are performed on all the print queues 402 in the information processing apparatus 104, the processes are terminated. The priority set in S1003 is used when determining the display order in FIG. 11A. For example, the print queues are displayed in order from the top of FIG. 11A in order of priority. Further, there is a case where a plurality of print queues are added to the list in S1004 by the process of FIG. For example, the printing queue for XPS of the printing apparatus 101, the printing queue for GDI of the printing apparatus 101, and the fax queue of the printing apparatus 101 may be managed in the information processing apparatus 104. In such a case, a plurality of print queues are added to the list in S1004.

FIG. 17 is a flowchart for explaining the process of S1003 in FIG. 10 in detail. In this embodiment, the print queue repair priority is determined by the parameters val1 to val3 associated with the print queue. val1 to val3 are numerical parameters whose initial value is "0", and the degree of contribution to the repair priority is in the relationship of val1> val2> val3. In the present embodiment, the parameters for determining the repair priority are described using a printer or the like that is normally used as shown below, but other parameters may be used. For example, the parameters related to the port set in the print queue may be other than those described in the present embodiment, and the number of parameters is not limited to the number of the present embodiment.

First, in S1701, the CPU 302 determines whether the print queue 402 _n to be determined is set as the print queue normally used when printing (hereinafter, “default printer”) by the function of the OS. When the "normally used printer" is set in the print queue 402 _n to be determined (YES in S1701), the CPU 302 sets "1" in val1 of the print queue 402 _{n to be} determined in S1702. On the other hand, when the "normally used printer" is not set in the print queue 402 _n to be determined (NO in S1701), the value of val1 remains the initial value "0".

Next, in S1703, the CPU 302 determines whether or not a print job remains in the print queue 402 _n . When the print job remains (YES in S1703), the CPU 302 sets "1" in the value 2 of the print queue 402 _n to be determined. On the other hand, when there are no print jobs remaining in the print queue 402 _n (NO in S1703), the value of val2 remains the initial value "0".

Subsequently, in S1705, the CPU 302 determines whether the print setting information of the print queue 402 _n such as the print paper type and the print paper size has been changed from the initial settings. In the present embodiment, when the print setting information of the print queue 402 _{n to be} determined is changed from the initial setting, the priority is set higher than that of the other print queues. The reason is that the fact that the user changes the print setting information from the initial setting is because it is predicted that the user frequently uses the print queue 402 _n to be determined. When the print setting information has been changed from the initial setting (YES in S1705), the CPU 302 adds "1" to the value of val2 of the print queue 402 _{n to be} determined. On the other hand, when the print setting information of the print queue 402 _n has not been changed from the initial setting (NO in S1705), the value of val2 is not changed. As an example, the method of acquiring the initial setting of the print setting information of the print queue may be a method in which the application 501 holds a table of initial settings for each model. Alternatively, the application 501 may store the initial settings in the ROM 303 inside the information processing device 104 or the external storage device 305 at the timing when the print queue 402 _n is created, such as when installing the printer driver.

Then, to determine the value of val3 from the driver type identifier 407 _p of the obtained print queue 402 _n at S604. In the present embodiment, as an example, from the viewpoint of high usage rate, the priority order of the driver type identifier according to 407 _p is defined as "GDI">"XPS">"FAX". When the driver type identifier 407 _p of the print queue 402 _n is "GDI" (YES in S1707), in S1708, the CPU 302 sets "3" to the value of val3 of the print queue 402 _n to be determined. When the driver type identifier 407 _p of the print queue 402 _n is "XPS" (NO in S1707, YES in S1709), in S1710, the CPU 302 sets "2" in the value of val3 of the print queue 402 _n to be determined. To do.

When the driver type identifier 407 _p of the print queue 402 _n is "FAX" (NO in S1707, NO in S1709, YES in S1711), in S1712, the CPU 302 sets the value of val3 of the print queue 402 _n to be determined to "NO". 1 ”is set. When the driver type identifier 407 _p of the print queue 402 _n is other than the above (NO in S1707, NO in S1709, NO in S1711), the value of val3 is not changed. After the values of val1 to val3 are determined, in S1713, the CPU 302 determines the repair priority of the print queue 402 _n from the values of val1 to val3. As for the method of determining the repair priority based on the values of val1 to val3, the repair priority determination table shown in FIG. 18 is used.

18 (a) and 18 (b) are examples of the repair priority determination table used in S1713 in FIG. Here, as an example, the application 501 determines the repair priority for the three print queues to be repaired (print queues A to C). The print queue A is a "default printer", but no print job remains and the print settings have not been changed from the initial settings. The print job remains in the print queue B, and the print settings are also changed from the initial settings. In the print queue C, the print job remains, but the print settings have not been changed from the initial settings. The printer driver types of the print queues A to C are "XPS", "FAX", and "GDI", respectively.

In FIG. 18A, the restoration priority of each print queue is determined as the higher the value of the parameter having a higher degree of contribution to the restoration priority among the values of val1 to val3. That is, among the print queues A to C, the print queue A having the highest value of val1 has the repair priority "1", and then the print queue B having the higher value when compared with the value of val2 has the repair priority "2". ". In the print queue C, the value of val3 is the highest among the print queues A to C, but the values of val1 and val2 are lower than the other two, so that the repair priority is "3".

Further, the priority may be set by a method different from that shown in FIG. 18A. For example, in FIG. 18B, the repair priority of each print queue is determined to be high when the total value of the values of val1 to val3 multiplied by a coefficient is high. Here, as an example, the coefficients to be multiplied by val1 to val3 are set to "3", "1.5", and "1", respectively. The coefficient to be applied to each parameter is not limited to this example, and may be a negative value when it is a parameter that lowers the repair priority. Here, the values of val of the print queues A to C are "5", "4", and "4.5", respectively, and the repair priority is "1", "3", and "2", respectively.

The method of setting the priority shown in FIGS. 18A and 18B is an example, and whether or not the print job remains or whether or not the print setting is changed may be used as the highest priority parameter when determining the priority. The method may be such that the priority is determined only by the printer driver type.

FIG. 12 is a flowchart for explaining the process of S613 in FIG. 6 in detail. First, in S1201, the CPU 302 creates a new port 408 _{M + 1} capable of communicating with the printing apparatus 101. S1201 will be described in detail with reference to the flowchart of FIG. After the port 408 _{M + 1} is created, in S1202, the CPU 302 sets the port 408 _{M + 1} as the reference destination of the port reference information 404 ₁ of the print queue 402 ₁ to be repaired. Thus, CPU 302 may be capable of communicating with the printing apparatus 101 by using the print queue 402 ₁ may transmit the print data to the printing apparatus 101 by using the print queue 402 _1. In S1201, as will be described later in FIG. 19, the WSD port and the host name port are preferentially created regardless of the type of port 408 ₁ associated with the port reference information 404 ₁ of the print queue 402 _1. To. As a result, even if the IP address of the printing device 101 is changed after the repair, it is possible to maintain a state in which printing by the printing device 101 using the printing queue 402 ₁ is possible as much as possible.

FIG. 19 is a flowchart for explaining the process of S1201 in FIG. 12 in detail. First, in S1900, the CPU 302 determines whether or not the print queue selected as the restoration target exists. If it is determined in S1900 that the print queue selected as the repair target does not exist, the CPU 302 enables the repair failure flag in S1914 and ends the process of FIG.

On the other hand, when it is determined in S1900 that the print queue selected as the restoration target exists, in S1901, the CPU 302 determines whether the WSD function of the printing device 101 acquired in S603 is valid / invalid. When the WSD function of the printing apparatus 101 is enabled (YES in S1901), in S1902, the CPU 302 creates the WSD port 408 _{M + 1} . Specifically, the CPU 302 creates the print queue of the printing device 101 and the WSD port 408 _{M + 1} by searching the printing device 101 using the WSD protocol. Then, the CPU 302 executes the processing after S1904 using the generated WSD port 408 _{M + 1} .

When the creation of the WSD port 408 _{M + 1} is completed, in S1903, the CPU 302 determines whether or not the WSD port 408 _{M + 1} can be used to communicate with the printing apparatus. Since the details of S1903 are described in the flowchart of FIG. 15 described above, detailed description thereof will be omitted.

When it is determined that communication with the printing apparatus 101 is possible using the WSD port 408 _{M + 1} (YES in S1904), the process ends.

On the other hand, when it is determined that the WSD port 408 _{M + 1} cannot communicate with the printing device 101 (NO in S1904), or the WSD function of the printing device 101 is invalid (NO in S1901), the processing of FIG. 19 is performed. Proceed to S1905. The CPU 302 determines whether the LLMNR function of the printing apparatus 101 acquired in S603 is valid / invalid (S1905). When the LLMNR function of the printing device 101 is enabled (YES in S1905), in S1906, the CPU 302 creates the host name port 408 _{M + 1} using the LLMNR name of the printing device 101. Specifically, the CPU 302 describes TCP / IP as the port type identifier, RAW as the protocol, and port number 9100. Then, the CPU 302 describes the host name acquired from the printing device 101 in the network identifier. By the above processing, the host name port 408 _{M + 1} using the LLMNR name is created.

When the creation of the host name port 408 _{M + 1} is completed, in S1907, the CPU 302 determines whether or not the communication is possible with the printing device 101 using the host name port 408 _{M + 1} . Since the details of S1907 are described in FIG. 16 described above, detailed description thereof will be omitted. When it is determined that communication with the printing device 101 is possible using the host name port 408 _{M + 1} (YES in S1908), the process ends.

On the other hand, when it is determined that communication with the printing device 101 is not possible using the host name port 408 _{M + 1} (NO in S1908), or when the LLMNR function of the printing device 101 is invalid (NO in S1905), FIG. Process proceeds to S1909. The CPU 302 determines whether the DNS function of the printing device 101 acquired in S603 is valid / invalid (S1909). When the DNS function of the printing device 101 is enabled (YES in S1909), in S1910, the CPU 302 creates the host name port 408 _{M + 1} using the DNS name of the printing device 101. Specifically, the CPU 302 describes TCP / IP as the port type identifier, RAW as the protocol, and port number 9100. Further, the CPU 302 describes the DNS host name and the DNS domain name acquired from the printing device 101 in the network identifier. By the above processing, the host name port 408 _{M + 1} using the DNS name is created.

When the creation of the host name port 408 _{M + 1} is completed, in S1911, the CPU 302 determines whether or not the printing device 101 can communicate with the host name port 408 _{M + 1} . Since the details of S1911 are described in the flowchart of FIG. 16 described above, detailed description thereof will be omitted. When it is determined that communication with the printing device 101 is possible using the host name port 408 _{M + 1} (YES in S1912), the process ends.

On the other hand, when it is determined that communication with the printing device 101 is not possible using the host name port 408 _{M + 1} (NO in S1912), or when the DNS function of the printing device 101 is invalid (NO in S1909), FIG. 19 Process proceeds to S1913. The CPU 302 creates a fixed IP address port 408 _{M + 1} using the IP address of the printing device 101 (S1913). Specifically, the CPU 302 describes TCP / IP as the port type identifier, RAW as the protocol, and port number 9100. Further, the CPU 302 describes the IP address acquired from the printing device 101 in the network identifier. By the above processing, the fixed IP address port 408 _{M + 1} is created. That is, even if the IP address of the printing device 101 is changed after the port is generated, the information processing device 104 can automatically use the changed IP address to communicate with the printing device. It is determined whether or not an automatic tracking port can be generated. Then, when it is determined that the automatic tracking port cannot be generated, the information processing device 104 generates a fixed port that fixedly uses the IP address acquired from the printing device 101 as the port of the print queue to be repaired.

It should be noted that the processes of FIG. 19 do not necessarily have to be all executed. For example, S1901 to S1904 may be performed.

In the present embodiment, an example in which WSD is used as a protocol for detecting a device connected to the network has been described, but another protocol having the same function as WSD may be used. Further, in the present embodiment, an example in which LLMNR and DNS are used as protocols having a name resolution function has been described, but another protocol having a name resolution function may be used. Further, in the present embodiment, the priority of the created port type is the order of WSD port and host name port, but the order is not limited to this. Further, the type of the port created may be only one of the WSD port and the host name port. At that time, as an example, the created port may be one that matches the port type of the port 408 ₁ set in the print queue 402 ₁ .

According to this embodiment, the protocol capable of name resolution is preferentially used and the port setting information is set. That is, the automatic tracking port such as the WSD port, the LLMNR port, and the DNS port is preferentially set. As a result, for example, even if the IP address of the printing device is changed after the execution of FIG. 6, the information processing device 104 automatically uses the changed IP address to communicate with the printing device. It becomes possible to do.

By the above processing, the state of the information processing device 104 can be easily changed to a state in which the user can communicate with the printing device selected in FIG. 7, and the convenience of the user can be improved.

<Second embodiment>
In the first embodiment, in S613 in FIG. 6, the CPU 302 creates a new port 408 _{M + 1} as a port to be set for the print queue 402 ₁ to be repaired. In the present embodiment, when a port capable of communicating with the printing device 101 already exists in the information processing device 104, the user convenience is improved by setting the port in the printing queue 402 ₁ .

Hereinafter, the processing flow of the application 501 according to the second embodiment of the present invention will be described with reference to the flowchart of FIG. A detailed description of the same processing as in the first embodiment will be omitted.

FIG. 20 is a flowchart for explaining the process of S613 in FIG. 6 in detail. First, in S2001, the CPU 302 determines whether or not there is a port capable of communicating with the printing device 101 from all the ports 408 of the information processing device 104. S2001 will be described in detail with reference to the flowchart of FIG.

When it is determined that there are ports that can communicate with the printing device 101 (YES in S2002), the CPU 302 repeats the processing of S2004 for all the ports in the information processing device 104 that can communicate with the printing device 101. (S2003). First, in S2004, the CPU 302 determines whether the port 408 _m capable of communicating with the printing device 101 is a fixed IP address port. If it is not a fixed IP address port, that is, if it is a WSD port or a host name port (NO in S2004), in S2005, the CPU 302 sets the port 408 _{m in} the port reference information 404 ₁ of the print queue 402 _{1 to be} repaired. Set the information. At this time, the port type of the port 408 _m may be limited so that the same type of port as the port of the port 408 ₁ set in the print queue 402 ₁ before the repair operation is set. On the other hand, when the port 408 _m is a fixed IP address port (YES in S2004), the CPU 302 changes the target port to the next port 408 _{m + 1} and executes S2004. A case where all the ports capable of communicating with the printing device 101 in the information processing device 104 are determined to be fixed IP address ports will be described. In S2006, the CPU 302 sets the print queue 402 ₁ to be repaired with the setting information of the port that is the first determination target in the determination process of S2004, for example. At this time, the port set in the print queue 402 ₁ may be any of all the ports capable of communicating with the printing device 101.

If it is determined in S2001 that there is no port that can communicate with the printing device 101 (NO in S2002), in S2007, the CPU 302 creates a new port 408 _{M + 1} that can communicate with the printing device 101. Since the details of S2007 are described in FIG. 19 described above, detailed description thereof will be omitted. When the port 408 _{M + 1} is created, in S2008, the CPU 302 sets the setting information of the port 408 _{M + 1} in the port reference information 404 ₁ of the print queue 402 ₁ to be repaired. From the above, the information processing apparatus 104 determines whether or not it is possible to communicate with the printing apparatus by another existing port different from the port of the print queue to be repaired by the printing apparatus 101 (S2002). Then, when it is determined that the other existing port can communicate with the printing device, the information processing device 104 changes the port of the print queue to be repaired to the existing port (S2005). The existing port may be referred to as the existing port setting information. If an existing port that can communicate with the printing device 101 already exists in the information processing device 104, the setting information of one of the existing ports that can communicate is set in the print queue to be repaired to print with the print queue 402 _1. The device 101 is changed to a communicable state. As a result, the CPU 302 can transmit print data to the printing device 101 using the print queue 402 ₁ . As a result, even if the number of ports in the information processing apparatus 104 is the maximum number that can be maintained, the print queue 402 ₁ can be repaired. If the printable port is only the fixed IP address port as a result of the iterative processing of S2003, S2007-S2008 may be performed without setting the port reference information 404 ₁ in S2006. That is, the newly created port setting information may be set in the port reference information 404 ₁ . As a result, the WSD port or the host name port has priority as the port set in the print queue 402 ₁ . Therefore, even if the IP address of the printing device 101 is changed after the repair, the information processing device 104 should maintain a state in which printing by the printing device 101 using the printing queue 402 ₁ is possible as much as possible. Can be done.

FIG. 21 is a flowchart for explaining the process of S2001 in FIG. 20 in detail. First, the CPU 302 repeats the processing of S2102 for all the ports 408 in the information processing device 104 (S2101). Since the details of S2102 are described in the flowchart of FIG. 14 described above, detailed description thereof will be omitted. After this process is performed on all the ports 408 in the information processing apparatus 104, the case where there is at least one port capable of communicating with the printing apparatus 101 (YES in S2103) will be described. In S2104, the CPU 302 determines that the information processing device 104 has a communicable port with the printing device 101. On the other hand, when there is no port capable of communicating with the printing device 101 (NO in S2103), the CPU 302 determines in S2105 that there is no port capable of communicating with the printing device 101 in the information processing device 104.

By the above processing, in the present embodiment, the process of creating a new port 408 _{M + 1} as a port to be set for the print queue 402 ₁ to be repaired can be reduced as much as possible, thus improving user convenience. It becomes possible.

<Third embodiment>
In the first and second embodiments, in S612 and S613 of FIG. 6, only one print queue was to be repaired. However, in a usage environment in which a plurality of print queues are used properly depending on the purpose, there is a possibility that the user desires to repair the plurality of print queues. Therefore, in the present embodiment, a case where there are a plurality of print queues to be repaired will be described.

Hereinafter, an example of the UI screen according to the third embodiment of the present invention will be described with reference to FIG. A detailed description of the same processing as in the first or second embodiment will be omitted.

In this embodiment, an example of the UI screen displayed by the CPU 302 in S612 of FIG. 6 is shown in FIG. 22 (a). In FIG. 22A, the CPU 302 displays a list of print queues to be repaired detected in S608 on the display unit 312 in a selectable format. The user selects the check box at the left end of the print queue that he / she wants to repair, and then clicks the [Next] button 2201. At this time, the user can select a plurality of print queues. When the CPU 302 detects that the [Next] button 2201 is pressed, it identifies a plurality of print queues to be repaired.

It should be noted that repair may be performed on all the print queues to be repaired detected in S608. An example of the UI screen in that case is shown in FIG. 22 (b). The CPU 302 displays a list of print queues to be repaired detected in S608 as shown in FIG. 22B on the display unit 312 in a format other than the selection format. When the CPU 302 detects that the [Next] button 2202 is pressed, it identifies all the print queues displayed in FIG. 22B as the print queues to be repaired.

When a plurality of print queues to be repaired are selected, in S613, the CPU 302 executes a repair process for all the print queues to be repaired. Since the repair process will be described in the first or second embodiment, detailed description thereof will be omitted.

<Other embodiments>
The above-described embodiment is also realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiment is supplied to the system or device via a network or various storage media. Then, the computer (CPU, MPU, processor, etc.) of the system or device reads and executes the program. Further, the program may be executed on one computer or may be executed in conjunction with a plurality of computers. Further, it is not necessary to realize all of the above-mentioned processes by software, and a part or all of the processes may be realized by hardware such as ASIC. Further, the CPU is not limited to one that performs all processing by one CPU, and a plurality of CPUs may perform processing while appropriately coordinating with each other.

402 Print queue 408 ports

Claims (17)

An information processing device that can communicate with a printing device
The first acquisition means for acquiring the information of the printing device via the network, and
A second acquisition means for acquiring information on the print queue managed in the information processing apparatus, and
When there is no print queue that can communicate with the printing device in the print queue managed by the information processing device, the information acquired by the first acquisition means and the information acquired by the second acquisition means are added. Based on the specific means for identifying the print queue corresponding to the printing apparatus,
An information processing device including a changing means for changing the port setting information of the specified print queue to port setting information capable of communicating with the printing device. The information processing device according to claim 1, wherein the specifying means specifies a print queue corresponding to the printing device based on the name information of the printing device acquired by the first acquisition means. The information processing apparatus according to claim 1 or 2, further comprising a display control means for displaying a print queue specified as a print queue corresponding to the printing apparatus. Further, it has a setting means for setting a priority for a plurality of print queues specified as print queues corresponding to the printing device.
The information processing apparatus according to claim 1, wherein the display control means displays the plurality of print queues according to the set priority. When there is a print queue managed as a normally used printer among the plurality of print queues, the setting means causes the print queue managed as the normally used printer to take precedence over other print queues. The information processing apparatus according to claim 4, wherein the priority is set. The setting means is characterized in that the priority is set so that the print queue in which the print job remains among the plurality of print queues has priority over the print queue in which no print job remains. Item 4. The information processing apparatus according to Item 4. The setting means has the priority so that the print queue to which the print setting information changed from the initial setting is associated among the plurality of print queues has priority over the print queue to which the initial setting is associated. The information processing apparatus according to any one of claims 4 to 6, wherein the information processing apparatus is set. Any of claims 4 to 7, wherein the setting means sets the priority so that the print queue for printing has priority over the print queue for fax among the plurality of print queues. The information processing apparatus according to item 1. It ’s a control method,
The first acquisition process for acquiring printing device information via a network,
The second acquisition process to acquire the information of the print queue managed in the information processing device, and
When there is no print queue that can communicate with the printing device among the print queues managed by the information processing device, the information acquired by the first acquisition step and the information acquired by the second acquisition step are added. Based on the specific step of identifying the print queue corresponding to the printing apparatus,
A control method comprising a changing step of changing the port setting information of the specified print queue to port setting information capable of communicating with the printing device. Computer,
The first acquisition means for acquiring information on the printing device via the network,
A second acquisition means for acquiring information on the print queue managed by the information processing device,
When there is no print queue that can communicate with the printing device in the print queue managed by the information processing device, the information acquired by the first acquisition means and the information acquired by the second acquisition means are added. Based on the specific means for identifying the print queue corresponding to the printing apparatus,
A program for functioning as a changing means for changing the port setting information of the specified print queue to the port setting information capable of communicating with the printing device. The program according to claim 10, wherein the specifying means identifies a print queue corresponding to the printing device based on the name information of the printing device acquired by the first acquisition means. The program according to claim 10 or 11, further comprising display control means for displaying a print queue specified as a print queue corresponding to the printing apparatus. Further, it has a setting means for setting a priority for a plurality of print queues specified as print queues corresponding to the printing device.
The program according to claim 10, wherein the display control means displays the plurality of print queues according to the set priority. When there is a print queue managed as a normally used printer among the plurality of print queues, the setting means causes the print queue managed as the normally used printer to take precedence over other print queues. The program according to claim 13, wherein the priority is set in 1. The setting means is characterized in that the priority is set so that the print queue in which the print job remains among the plurality of print queues has priority over the print queue in which no print job remains. Item 13. The program according to item 13 or 14. The setting means has the priority so that the print queue to which the print setting information changed from the initial setting is associated among the plurality of print queues has priority over the print queue to which the initial setting is associated. The program according to any one of claims 13 to 15, characterized in that. Any of claims 13 to 16, wherein the setting means sets the priority so that the print queue for printing has priority over the print queue for fax among the plurality of print queues. The program described in item 1.

Images