JP6882060B2 - Information processing device, driver installation method and program - Google Patents

Description

The present invention relates to a device driver installation technique.

The types of device drivers installed on a computer can be broadly classified into two types. One is a driver provided by the device manufacturer, which is referred to as an Outbox driver. The other is a driver provided by the OS, which is called an Inbox driver. In general, the Outbox driver has better features than the Inbox driver, and device manufacturers recommend using the Outbox driver.

The Windows® OS provides a PnP-X (Plug and Play Extension for Network Connected Device) function. The Windows OS detects the device based on its PnP-X function and automatically installs the Inbox driver associated with the device on the computer. That is, the Inbox driver is automatically installed on the computer simply by connecting the computer and the device via the network.

If the Outbox driver is installed after the Inbox driver is installed, the PnP-X function does not automatically detect the device. Therefore, the user may delete the Inbox driver and then install the Outbox driver. In this case, for example, the Inbox driver can be deleted by applying the method of Patent Document 1. Patent Document 1 discloses a method of selectively deleting a printer driver installed in a computer by referring to the unique deletion information added to the printer driver.

Japanese Patent No. 3346997

The latest OS, Windows 10 (registered trademark), is equipped with a driver for Microsoft Mobile Print (hereinafter referred to as "MMP") as standard equipment, and this MMP driver has specifications common to all device manufacturers.

Therefore, when the Outbox driver is installed after the MMP driver is deleted, there is a problem that even the print queue of the MMP driver associated with another device from a different manufacturer is unintentionally deleted.

The present invention has been made in view of the above problems. That is, the purpose is to generate the print queue of the driver provided by the manufacturer of the device while deleting the print queue of the general-purpose driver provided by the OS, which is generated in association with the device.

The information processing device of the present invention includes a registration means for registering a driver provided by a device manufacturer, an acquisition means for acquiring a PnP-X ID using the UUID of the device and a print port name of the information processing device. When the print queue of the driver installed in the information processing apparatus is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver. The print queue is deleted, and the print queue of the registered driver is assigned to the WSD communication port to generate the print queue.

According to the present invention, it is possible to generate the print queue of the driver provided by the manufacturer of the device while deleting the print queue of the general-purpose driver provided by the OS, which is generated in association with the device.

This is a configuration example of the information processing system according to the first embodiment. This is an example of a computer hardware configuration according to the first embodiment. This is a hardware configuration example of the device according to the first embodiment. This is an example of a functional configuration of software in the first embodiment. It is a flowchart which shows the processing procedure of the driver installer in Embodiment 1. FIG. It is a flowchart which shows the generation procedure of the print queue in Embodiment 1. FIG. It is a flowchart which shows the generation procedure of the print queue in Embodiment 2. It is a figure which shows an example of the confirmation window of a device setting in Embodiment 1. FIG.

[Embodiment 1]
Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. However, the configurations described in this embodiment are merely examples, and are not intended to limit the scope of the present invention to them.

(Configuration of information processing system)
FIG. 1 is a block diagram showing a configuration example of an information processing system according to the present embodiment. The information processing system 1 of the present embodiment includes a computer 100 and devices 200 and 400. As shown in FIG. 1, the sub-network A to which the computer 100 and the device 200 belong and the sub-network B to which the device 400 belongs are connected via the router 300. The computer 100 is an information processing device such as a PC (personal computer) or a tablet. The devices 200 and 400 are peripheral devices such as printers, copiers, facsimiles, and scanners, or devices having a combined function thereof. The devices 200 and 400 support the TCP / IP protocol and also support WSD (Web Services on Devices), which is a network protocol of the Microsoft Windows OS standard. The configuration of the information processing system 1 is an example, and is not limited to the configuration of the information processing system 1 of FIG. For example, the number of computers and devices belonging to each of the sub-network A and the sub-network B is not limited to the configuration of the information processing system 1 of FIG. 1, and may be a plurality.

(Computer hardware configuration)
FIG. 2 is a block diagram showing a hardware configuration example of the computer 100 according to the present embodiment. The computer 100 includes a CPU 101, a RAM 102, a ROM 103, a graphic controller 104, a display unit 105, and an auxiliary storage device 106. Further, the computer 100 includes an external connection interface 107 (hereinafter, the interface is referred to as "I / F") and a network I / F 108, and each component is communicably connected via a bus 109. The CPU 101 is composed of an arithmetic circuit and controls the computer 100 in an integrated manner. The CPU 101 reads the program stored in the ROM 103 or the auxiliary storage device 106 into the RAM 102, and executes various processes. The ROM 103 stores system software such as a BIOS used for controlling the computer 100. The graphic controller 104 generates a screen for displaying on the display unit 105. The display unit 105 is composed of an LCD (liquid crystal display) or the like, and displays a screen generated by the graphic controller 104. Further, the display unit 105 may have a touch screen function. In that case, the user instruction that has received the input via the display unit 105 can be treated as the input to the computer 100. The auxiliary storage device 106 has a function as a storage area, and stores an OS (operating system), a device driver for controlling various devices, an application program that executes various processes, and the like. The auxiliary storage device 106 is an example of a storage device, and can be configured by an SSD (solid state drive) or the like in addition to the HDD (hard disk drive). The device driver stored in the auxiliary storage device 106 includes driver software used to control various devices including the devices 200 and 400. Such driver software includes, for example, a scanner driver, a printer driver, a facsimile driver, and the like. The external connection I / F 107 is an interface for connecting various devices to the computer 100. For example, a pointing device such as a keyboard or a mouse can be connected via an external connection I / F 107. The network I / F 108 communicates with the devices 200 and 400 via the network under the control of the CPU 101.

The auxiliary storage device 106 of the present embodiment also stores the driver installer required for installing the driver software (hereinafter, may be simply referred to as “driver”) on the target device. In the present embodiment, the target device means a device to which the device is installed. This driver installer has a device search function using the TCP / IP protocol and a device search function using the WSD protocol. In the present embodiment, the driver installer has shown a configuration including a device search function by the TCP / IP protocol and a device search function by the WSD protocol, but the embodiment is not limited to the configuration shown above. In another embodiment, the auxiliary storage device 106 may store a dedicated module having a device search function by the TCP / IP protocol and a dedicated module having a device search function by the WSD. In that case, the device driver or application may call these dedicated modules to execute device search.

(Hardware configuration of device)
FIG. 3 is a block diagram showing a hardware configuration example of the devices 200 and 400 according to the present embodiment. The devices 200 and 400 include a CPU 201, a RAM 202, a ROM 203, a graphic controller 204, a display unit 205, and an operation unit 206. Further, the devices 200 and 400 include a network I / F 207 and a printing unit 208, and each component unit is communicably connected via a bus 209. The CPU 201 is composed of an arithmetic circuit and controls the devices 200 and 400 in an integrated manner. The CPU 201 reads the program stored in the ROM 203 into the RAM 202 and executes various processes. The ROM 203 stores programs and data used for controlling the devices 200 and 400. The graphic controller 204 generates a screen for displaying on the display unit 205. The display unit 205 is composed of an LCD (liquid crystal display) or the like, and displays a screen generated by the graphic controller 204. The operation unit 206 is composed of a touch panel, hardware keys, and the like, and can receive user instructions. The network I / F 207 communicates with an external device via the network under the control of the CPU 201. The printing unit 208 forms characters and images on a recording medium such as paper based on the print job transmitted from the computer 100 and the image data read by the devices 200 and 400 themselves. The configuration of the devices 200 and 400 shown in FIG. 3 is a configuration when the devices 200 and 400 are printers. When the devices 200 and 400 are scanners, the devices 200 and 400 further include a reading unit for reading characters and images formed on a recording medium such as paper.

(Software function configuration)
FIG. 4 is a block diagram showing a software functional configuration of the computer 100 according to the present embodiment. The function of each block shown in FIG. 4 is realized by the CPU 101 reading the program code of the application (driver installer) 110 into the RAM 102 and executing it.

The application 110 searches for a device connected to the network and installs a driver associated with the device selected by the user from the searched devices on the computer 100. The application 110 installs the printer driver 122 on the computer 100 if the device selected by the user is a printer. If the device selected by the user is a scanner, the scanner driver 123 is installed on the computer 100. Further, the utility 124 is appropriately installed on the computer 100 according to the type of the device selected by the user.

The device detection unit 111 acquires the device driver information from the driver INF file 121. The driver information includes the driver name.

The TCP / IP device search unit 112 searches for a device connected to the computer 100 via a network by the TCP / IP protocol. The application 110 displays information about the device detected by the above search on the display unit 105. In the present embodiment, the device name, IP address, MAC address, and the like are displayed on the display unit 105 as information about the device. The information about these devices is information that can be used to identify the target device. Further, the application 110 registers the driver used for controlling the selected device among the information about the device displayed on the display unit 105 in the computer 100.

The WSD device search unit 113 searches for the selected device from the devices connected to the same subnetwork as the subnetwork to which the computer 100 belongs by the WSD protocol. Due to the WSD specifications, the WSD protocol search cannot search for devices from subnetworks beyond the router 300. Therefore, to explain using FIG. 1 as an example, the WSD device search unit 113 can search for the device 200 connected to the sub-network A, but cannot search for the device 400 connected to the sub-network B. When the WSD device search unit 113 detects a device connected to the same subnetwork as the subnetwork to which the computer 100 belongs, the application 110 determines that the device can communicate with the WSD protocol.

The UUID acquisition unit 114 acquires the UUID of the device detected by the WSD device search unit 113.

The Inbox driver detection unit 115 acquires a list of print ports included in the computer 100, and acquires a PnP-X ID from the port monitor using the UUID and the print port name. Next, the Inbox driver detection unit 115 acquires a list of print queues installed on the computer 100, and determines whether or not each print queue is assigned to the print port from which the PnP-X ID has been acquired. In the present embodiment, it is determined whether or not the print queue is assigned to the WSD communication port by determining whether or not the PnP-X ID is assigned to the acquired print port. Further, the Inbox driver detection unit 115 determines whether or not the driver corresponding to the print queue matches the driver registered by the application 110. The PnP-X ID is an abbreviation for PnP-X Identity, and is an identifier that uniquely identifies the detection result of the device by the PnP-X function.

If it does not match the registered driver, the WSD device registration unit 116 deletes the target device from the association database (Association Database) controlled by the OS and used for device management. When the target device is deleted from the association database, the OS deletes the print queue of the Inbox driver (general-purpose driver provided by the OS) associated with the target device.

The WSD device registration unit 116 registers the target device in the OS database again. When the target device is registered in the OS database again, the PnP-X function of the OS is triggered, and the print queue of the registered driver is assigned to the WSD communication port and generated.

(Driver installer processing procedure)
FIG. 5 is a flowchart showing a processing procedure of the driver installer in this embodiment. The processing of the flowchart shown in FIG. 5 is performed by the CPU 101 expanding the program code of the application 110 into the RAM 102 and executing it. Each of the following symbols S means a step in the flowchart. These are the same for the flowcharts after FIG.

In S501, the device detection unit 111 acquires the driver information of the device from the driver INF file 121. The driver information includes the driver name.

In S502, the TCP / IP device search unit 112 searches for a device connected to the same subnet as the subnet to which the computer 100 belongs by the TCP / IP protocol. Further, the TCP / IP device search unit 112 searches for a device connected to the subnet beyond the router 300.

In S503, it is determined whether or not a device matching the device name acquired from the driver INF file 121 is detected by the device search by the TCP / IP protocol. If a matching device is detected (S503: YES), the process proceeds to S504. If no matching device is detected (S503: NO), the process proceeds to S512.

In S504, information about the device detected in S503 is displayed on the display unit 105. In the present embodiment, the device name, IP address, MAC address, and the like are displayed on the display unit 105 as information about the device. The information about these devices is information that can be used to identify the target device. When a plurality of devices are detected in S503, information on the plurality of devices is displayed in a list.

In S505, the driver used to control the selected device among the information about the device displayed on the display unit 105 is registered in the computer 100. In the present embodiment, the device is selected based on the user instruction input to the display unit 105 having the touch panel function. In the present embodiment, the Outbox driver provided by the manufacturer of the device 200 is registered in the computer 100.

In S506, the WSD device search unit 113 searches for the device selected in S505 from the devices connected to the same subnet as the subnet to which the computer 100 belongs by the WSD protocol.

In S507, the device search by the WSD protocol determines whether or not the device selected in S505 is detected from a device connected to the same subnet as the subnet to which the computer 100 belongs. If a device is detected (S507: YES), the process proceeds to S508. If the device is not detected (S507: NO), the process proceeds to S510.

When the device is detected (S507: YES), it is determined that the computer 100 and the device can communicate with each other by the WSD protocol. Then, in S508, the communication port used for communication with the device is determined to be a WSD communication port capable of communicating by the WSD protocol.

In S509, the UUID acquisition unit 114 acquires the UUID of the device detected in S507.

In S600, application 110 creates a print queue for the driver used to control the device detected in S507. The details of S600 will be described later. When the processing of S600 is completed, the processing of this flowchart ends.

If the device is not detected (S507: NO), it is determined that communication by the WSD protocol is impossible between the computer 100 and the device. Then, in S510, the communication port used for communication between the computer 100 and the device is determined to be a TCP / IP communication port capable of communicating by the TCP / IP protocol.

In S511, application 110 creates a print queue for the driver used to control the device detected in S507. More specifically, the application 110 allocates the print queue of the driver registered in S505 to the TCP / IP communication port and generates it. When the process of S511 is completed, the process of this flowchart ends.

Further, when the device matching the driver information is not detected by the device search by the TCP / IP protocol (S503: NO), in S512, the device setting confirmation window is displayed on the display screen of the display unit 105.

FIG. 8 is a diagram showing an example of a device setting confirmation window in the present embodiment. The confirmation window 801 of this embodiment includes a message that a device matching the driver information (device name) acquired from the driver INF file 121 was not detected. Then, when the input to the retry button 802 in the confirmation window 801 is accepted (S513: YES), the process returns to S502 again. On the other hand, when the input to the stop button 803 in the confirmation window 801 is accepted (S513: NO), the processing of this flowchart ends.

(Procedure for generating a print queue)
FIG. 6 is a flowchart showing details of the print queue generation procedure (S600) in the present embodiment. Hereinafter, a detailed description will be given with reference to FIG.

In S601, the Inbox driver detection unit 115 acquires a list of print ports included in the computer 100.

In S602, it is determined whether or not the processing is completed for all the print ports. If the processing is not completed for all the print ports (S602: NO), the process proceeds to S603. When the processing is completed for all the print ports (S602: YES), the process exits the processing loop of S602 to S603 and shifts to S604.

In S603, the PnP-X ID is acquired from the port monitor by using the UUID acquired in S509 and the print port name of the computer 100. The process of acquiring the PnP-X ID from the port monitor is from the print port name described at the top of the above list to the print port name described at the bottom of the above list for each processing loop of S602 to S603. It is executed in order. When the process of S603 is completed, the process returns to the determination process of S602 again. In this embodiment, it is assumed that the port monitor function is provided by the OS of the computer 100.

In S604, a list of print queues installed on the computer 100 is acquired. Specifically, when various drivers are installed on the computer 100, a list of print queues generated by the installer is acquired.

In S605, it is determined whether or not the processing is completed for all the print queues. If the processing is not completed for all the print queues (S605: NO), the process proceeds to S606. When the processing is completed for all the print queues (S605: YES), the process exits the processing loop of S605 to S607 and proceeds to S610.

In S606, it is determined whether or not the print queue is assigned to the print port from which the PnP-X ID has been acquired. The determination process of S606 is executed in order for each processing loop of S605 to S607, from the print queue name described at the top of the list to the print queue name described at the bottom of the list. In the present embodiment, it is determined whether or not the print queue is assigned to the WSD communication port by determining whether or not the PnP-X ID is assigned to the acquired print port. When the print queue is assigned to the print port from which the PnP-X ID has been acquired (S606: YES), the process proceeds to S607. If it is not assigned (S606: NO), the process returns to the determination process of S605 again.

In S607, the Inbox driver detection unit 115 determines whether or not the driver corresponding to the print queue matches the driver registered in S505. If the driver matches the registered driver (S607: YES), the process returns to the determination process of S605 again. On the other hand, if the driver does not match the registered driver (S607: NO), the process exits the processing loop of S605 to S607 and the process proceeds to S608.

In S608, the WSD device registration unit 116 deletes the target device from the OS database.

In S609, when the target device is deleted from the database of the OS (S608), the print queue of the Inbox driver (general-purpose driver provided by the OS) associated with the target device is deleted by the OS. In order to delete the print queue of the Inbox driver, a method of directly specifying the name of the print queue to be deleted can be considered, but such a method is not applied in the present embodiment. This is because the name of the print queue can be freely changed, and the print queue to be deleted may not be specified by the name of the print queue.

In S610, the WSD device registration unit 116 registers the target device in the OS database again.

In S611, when the target device is registered in the OS database again (S610), the PnP-X function of the OS is triggered, and the print queue of the driver registered in S505 is assigned to the WSD communication port and generated. When the process of S611 is completed, the process of this flowchart is finished, and the process returns to the flowchart of FIG. 5 again.

As described above, according to the driver installation method of the present embodiment, the print queue is generated in consideration of the characteristics of the general-purpose driver provided by the OS. Therefore, the driver installation method of the present embodiment can generate the print queue of the driver provided by the device manufacturer while deleting the print queue of the general-purpose driver provided by the OS, which is generated in association with the device. ..

[Embodiment 2]
According to the first embodiment, the print queue of the driver (Outbox driver) provided by the manufacturer of the device is generated while deleting the print queue of the general-purpose driver (Inbox driver) provided by the OS, which is generated in association with the device. be able to. However, the method of Embodiment 1 causes problems in the following use cases. That is, when a plurality of Outbox drivers are already installed and a part of the plurality of Outbox drivers is updated, the print queue of the Outbox driver to be non-updated is deleted. In view of the above problem, the driver installation method of the second embodiment can update the update target Outbox driver while maintaining the print queue of the non-update target Outbox driver. Hereinafter, the parts common to the first embodiment will be simplified or omitted, and the following will mainly explain the points peculiar to the present embodiment.

(Procedure for generating a print queue)
Since S601 to S605 are the same as those in the first embodiment, the description thereof will be omitted.
In S701, the determination result of S606 is stored in a storage area such as the auxiliary storage device 106. That is, the print queue name assigned to the print port from which the PnP-X ID has been acquired is stored for each processing loop of S605 to S702. The print queue name stored in S701 is referred to in the determination process of S703 described later.

Since S607 is the same as that of the first embodiment, the description thereof will be omitted.
In S702, the determination result of S607 is stored in a storage area such as the auxiliary storage device 106. That is, the print queue name determined to match the registered driver (for example, the Outbox driver) is stored in each processing loop of S605 to S702. The print queue name stored in S702 is referred to in the determination process of S703 described later. When the processing is completed for all the print queues (S605: YES), the process proceeds to S703, and it is determined whether or not to delete the target device from the database of the OS.

In S703, the determination result stored in S701 is referred to, and it is determined whether or not there is at least one print queue assigned to the print port from which the PnP-X ID has been acquired. If there is at least one print queue that satisfies the condition (S703: YES), the process proceeds to S704. If there is no print queue that satisfies the conditions (S703: NO), S704 to S609 are skipped and the process proceeds to S610.

In S704, the determination result stored in S702 is referred to, and it is determined whether or not all the drivers corresponding to the print queue satisfying the condition of S703 match the driver registered in S505. If none of them match the registered driver (S704: YES), the process proceeds to S608. If there is a print queue that matches the registered driver (S704: NO), S608 to S609 are skipped and the process proceeds to S610.
Since S608 to S611 are the same as those in the first embodiment, the description thereof will be omitted. When the process of S611 is completed, the present flowchart is terminated, and the process returns to the flowchart of FIG. 5 again.

As described above, according to the driver installation method in the present embodiment, the update target Outbox driver can be updated while maintaining the print queue of the non-update target Outbox driver.

Hereinafter, the case where the GDI driver to be updated and the XPS driver to be non-updated are already installed in the computer 100 will be described as a specific example of the target device 200. It is assumed that both the GDI driver and the XPS driver are Autobox drivers, and these print queues are assigned to the WSD communication port. In this case, in the method of the first embodiment, it is determined that the XPS driver to be non-updated does not match the registered driver (S607: NO), so that the print queue of the XPS driver is determined to be the print key to be deleted. .. On the other hand, in the method of the present embodiment, since the determination process (S703 to S704) considering a plurality of Outbox drivers (including the GDI driver and the XPS driver) is executed, the print queue of the XPS driver to be non-updated is deleted. It is not determined as the target print key. With such a configuration, in the method of the present embodiment, the Outbox driver to be updated can be updated while holding the print queue of the Outbox driver to be updated.

(Other Examples)
The present invention supplies a program that realizes one or more functions of the above-described embodiment to a system or device via a network or storage medium, and one or more processors in the computer of the system or device reads and executes the program. It can also be realized by the processing to be performed. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

1 ... Information processing system 100 ... Computer 200 ... Device 400 ... Device 110 ... Application (installer)
111 ... Device detection unit 112 ... TCP / IP device search unit 113 ... WSD device search unit 114 ... UUID acquisition unit 115 ... Inbox driver detection unit 116 ... WSD device registration unit

Claims (12)

It is an information processing device
A registration method for registering drivers provided by the device manufacturer, and
An acquisition means for acquiring a PnP-X ID using the UUID of the device and the print port name of the information processing device.
When the print queue of the driver installed in the information processing device is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver. , A deletion means for deleting the print queue,
An information processing apparatus comprising: a generation means for allocating a print queue of the registered driver to a WSD communication port to generate the print queue. It is an information processing device
A registration method for registering drivers provided by the device manufacturer, and
An acquisition means for acquiring a PnP-X ID using the UUID of the device and the print port name of the information processing device.
If there is at least one print queue assigned to the print port from which the PnP-X ID has been acquired, and none of the drivers corresponding to the print queue match the registered driver, the above. Deletion means to delete the print queue,
An information processing apparatus comprising: a generation means for allocating a print queue of the registered driver to a WSD communication port to generate the print queue. 1. The deletion means is characterized in that the print queue of the driver associated with the device is deleted in response to the information indicating the device being deleted from the database used for managing the device. Or the information processing apparatus according to 2. 3. The generation means according to claim 3, wherein the generation means allocates the print queue of the registered driver to the WSD communication port in response to the registration of information indicating the device in the database. Information processing device. The information processing device according to any one of claims 1 to 4, wherein the acquisition means acquires the PnP-X ID from a port monitor, which is a function provided by the OS of the information processing device. How to install the driver in the information processing device
A registration step to register the driver provided by the device manufacturer, and
An acquisition step of acquiring a PnP-X ID using the UUID of the device and the print port name of the information processing device, and
When the print queue of the driver installed in the information processing device is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver. , A delete step to delete the print queue,
A method for installing a driver, which comprises a generation step of allocating a print queue of the registered driver to a WSD communication port to generate the print queue. How to install the driver in the information processing device
A registration step to register the driver provided by the device manufacturer, and
An acquisition step of acquiring a PnP-X ID using the UUID of the device and the print port name of the information processing device, and
If there is at least one print queue assigned to the print port from which the PnP-X ID has been acquired, and none of the drivers corresponding to the print queue match the registered driver, the above. With the delete step to delete the print queue,
A method for installing a driver, which comprises a generation step of allocating a print queue of the registered driver to a WSD communication port to generate the print queue. A program for functioning as an information processing device
A registration method for registering drivers provided by the device manufacturer, and
An acquisition means for acquiring a PnP-X ID using the UUID of the device and the print port name of the information processing device.
When the print queue of the driver installed in the information processing device is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver. , A deletion means for deleting the print queue,
A program for functioning as an information processing device having a generation means for allocating and generating a print queue of the registered driver to a WSD communication port. A program for functioning as an information processing device
A registration method for registering drivers provided by the device manufacturer, and
An acquisition means for acquiring a PnP-X ID using the UUID of the device and the print port name, and
If there is at least one print queue assigned to the print port from which the PnP-X ID has been acquired, and none of the drivers corresponding to the print queue match the registered driver, the above. Deletion means to delete the print queue,
A program for functioning as an information processing device having a generation means for allocating and generating a print queue of the registered driver to a WSD communication port. 8. The deletion means deletes the print queue of the driver associated with the device in response to the deletion of information indicating the device from the database used to manage the device. Or the program described in 9. 10. The generation means according to claim 10, wherein the generation means allocates the print queue of the registered driver to the WSD communication port in response to the information indicating the device being registered in the database. Program. The program according to any one of claims 8 to 11, wherein the acquisition means acquires the PnP-X ID from a port monitor, which is a function provided by the OS of the information processing apparatus.

Images