JP2004252785A - Printer unit information setting method, picture printing system and computer readable storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a picture printing system for reducing responsibility of a manager by automating a configuration data acquiring tool. <P>SOLUTION: In the picture printing system, a client terminal, a printer and a server having a printer driver of the printer are connected on a network. A method for setting unit information of the printer in the printer driver is provided with a storage step for storing unit information on the printer, which the server or the client terminal acquires, a collection step for collecting specified information for specifying the printer connected onto the network by using the configuration data acquiring tool, a unit information acquiring step for acquiring unit information stored in the server based on a request from the printer driver based on collected specified information specifying the printer and a unit information reflecting step for transferring unit information to the printer driver. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an image printing system in which device information of a printer is reflected in a printer driver on a server in an environment (for example, a metaframe environment) in which an application program is installed only on a server, and in particular, a configuration data acquisition tool. The present invention relates to a printer device information setting method capable of reducing the burden on an administrator by automating a (device information acquisition tool).
[0002]
[Prior art]
In order to solve the problem of the conventional client / server system, there is a system in which an application program is installed and operated only on a server without being installed in a client terminal. Such a method includes, for example, a method called a meta frame.
FIG. 1 is a diagram illustrating an example of an image printing system in a metaframe environment. The application program runs on the metaframe server 1 shown in FIG. 1, and the client terminal 2 displays only the execution result of the application program running on the metaframe server 1.
When the printer 3 is used in the metaframe environment, for example, a printer driver is installed in the metaframe server 1 in advance, and when the client terminal 2 using the printer 3 logs in to the metaframe server 1, the printer 3 A logical printer is automatically created (AutoCreate) using a printer driver. When printing is performed from the client terminal 2, print data is generated in the metaframe server 1, the print data is transmitted to the printer 3 via the client terminal 2, and the printer 3 performs printing.
However, in the printer system using the above-described metaframe environment, there is a problem that even though the option setting is performed on the client terminal 2 side, the setting is not reflected in the printer driver in the metaframe server 1.
That is, the option setting in the logical printer remains in the state of 'HIDXOW'. For example, despite the presence of the double-sided tray, the setting value on the logical printer is no double-sided. Further, the settings of the paper size and paper type of the tray are also unknown. Such a problem occurs for the following reasons.
[0003]
In a normal configuration including the client terminal 2 and the printer 3 as shown in FIG. 2, option information such as a double-sided tray in the printer driver of the printer 3 in the client terminal 2 usually includes both the client terminal 2 and the printer 3. The client terminal 2 obtains the information by performing bidirectional communication. The two-way communication is performed, for example, by the configuration shown in FIG. In this configuration, the network communication module 6 acquires information specified by the two-way communication module 5 that is a part of the printer driver 4 from the printer 3 via a network using a protocol such as SNMP.
However, since the bidirectional communication as described above cannot be performed between the metaframe server 1 and the printer 3, the option information cannot be reflected on the printer driver. Therefore, the above problem occurs.
In order to solve this, in the invention by the present applicant (Japanese Patent Application No. 2002-233528), in a network environment as shown in FIG. Configuration information) is acquired from the client terminal 2 by a configuration data acquisition tool, and the configuration data is stored in the metaframe server 1 (hereinafter, device information such as tray information is also referred to as configuration data. May also be referred to as communication data).
Then, by accessing this data in the metaframe server 1, the printer driver 4 can acquire the device information, which can be reflected in the option settings of the automatically created logical printer.
Further, as a conventional technique of a configuration of a printer system in a metaframe environment, there is a technique described in, for example, US Patent Publication US2002 / 0018234A1. U.S. Patent Publication US2002 / 0018234A1 describes a universal printer driver that can be used in a metaframe environment.
[Patent Document 1] US2002 / 0018234A1
[Patent Document 2] US2002 / 0018234A1
[Patent Document 3] Japanese Patent Application No. 2002-233528
[0004]
[Problems to be solved by the invention]
However, the above technique has the following problems.
That is, the configuration data acquisition tool must be used to create configuration data for each printer, thereby increasing the burden on the administrator.
In addition, resources must be wasted because the printer must be registered in the client terminal before using the configuration data acquisition tool.
In addition, when the device information of the printer changes, the administrator must re-create the configuration data of the target printer, so that there is no real-time property and the burden on the administrator increases. For example, when the paper size is changed in the paper feed tray, it is necessary to re-create the configuration data using the configuration data acquisition tool.
In addition, when a large number of printers are used, the amount of configuration data is large, and resources are wasted.
An object of the present invention is to provide an image printing system that can reduce the burden on an administrator by automating a configuration data acquisition tool.
[0005]
[Means for Solving the Problems]
In order to achieve the above object, the invention according to claim 1 provides an image printing system in which a client terminal, a printer, and a server having a printer driver for the printer are connected on a network. A method for setting device information, comprising: a storing step of storing device information of the printer obtained by the server or the client terminal; and a device information obtaining tool for specifying information for specifying a printer connected on the network. And a device information obtaining step of obtaining device information stored in the server based on a specific information specifying the collected printer based on a request from the printer driver, and the printer driver Device information reflecting step of passing the device information to the And it features.
Therefore, by automating the device information acquisition tool, the burden on the administrator is reduced, and it is not necessary to register the printer in the client terminal.
According to a second aspect of the present invention, in the printer device information setting method according to the first aspect, an application for periodically obtaining device information of the printer is prepared, and the application is installed on the server. It is characterized in that the device information is updated periodically.
Therefore, the latest device information of the printer can be acquired, real-time property can be maintained, and the administrator does not need to recreate the device information.
According to a third aspect of the present invention, there is provided an image printing system in which a client terminal, a printer, and a server having a printer driver of the printer are connected on a network, for setting printer device information in a printer driver. A method for storing device information of the printer obtained by the server or the client terminal, and a collecting step of collecting specific information for specifying a printer connected on the network by using a device information obtaining tool An access information acquisition step of acquiring access information of the printer based on a request from the printer driver based on identification information for identifying the collected printer; and storing the access information in the server based on a request from the printer driver. Of the acquired printer And having a device information reflecting step of the device information acquiring step of acquiring Seth information based passes the device information to the printer driver.
Therefore, the amount of device information is reduced, and the storage capacity can be saved.
According to a fourth aspect of the present invention, in the image printing system, the program of the printer device information setting method according to the first, second, or third aspect is executed.
The invention according to claim 5 is characterized in that the computer readable storage medium stores the program for the printer device information setting method according to claims 1, 2, and 3.
[0006]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
FIG. 1 is a diagram illustrating an example of a metaframe environment. An application program is operated on the metaframe server 1 shown in FIG. 1, and only the execution result of the application program operated on the metaframe server 1 is displayed on the client terminal 2 operated by the client.
When the printer 3 is used in the metaframe environment, for example, a printer driver is installed in the metaframe server 1 in advance, and when the client terminal 2 using the printer 3 logs in to the metaframe server 1, the printer 3 A logical printer is automatically created (AutoCreate) using a printer driver. When printing is performed from the client terminal 2, print data is generated in the metaframe server 1, transmitted to the printer 3 via the client terminal 2, and printed by the printer 3.
Here, in the network environment shown in FIG. 1, device information (option configuration information) such as tray information of the printer 3 that cannot be obtained by bidirectional communication is transmitted from the client terminal 2 to a configuration data obtaining tool (device information). Acquisition tool) and stores the configuration data in the metaframe server 1 (hereinafter, device information such as tray information is also referred to as configuration data, but may also be referred to as pseudo-two-way communication data). .
Then, by accessing this data in the metaframe server 1, the printer driver 4 can acquire the device information, which can be reflected in the option settings of the automatically created logical printer.
FIG. 4 shows a module configuration of software according to the present invention in the metaframe server 1. The same components have the same reference numbers.
As shown in the figure, in the present invention, a pseudo network communication module 7 is used instead of a normally used network communication module 6. As a result, the printer driver 4 acquires the device information from the pseudo bidirectional communication data 8 stored in advance via the pseudo network communication module 7.
In the present embodiment, the configuration data acquisition tool (device information acquisition tool) is automated as described below to reduce the burden on the administrator.
[0007]
Next, the flow of processing in the first embodiment of the present invention will be described in more detail with reference to FIGS. The same components have the same reference numbers.
FIG. 5 is a diagram for explaining acquisition of configuration data. As shown in the figure, a client terminal running a configuration data acquisition tool acquires configuration data.
In this case, for example, by selecting a printer driver installed in the client terminal on a screen as shown in FIG. 6 on the client terminal side, a printer from which device information is to be acquired is designated (in this case, Printer A).
When the client terminal selects "collect printers on the network" as shown in FIG. 6, the configuration data is created in the following procedure.
1. The port names of the printers 3 (printer A, printer B, and printer C in FIG. 5) on the network are collected (for example, the IP address of the printer 3). That is, a port name is collected as specific information for specifying the printer 3.
2. Device information (eg, paper feed tray information, option information, etc.) is acquired from the collected port names of the printer 3.
3. The collected printer 3 (for example, the IP address of the printer 3) and device information are created as configuration data.
[0008]
FIG. 7 is an operation flowchart of a process of acquiring configuration data and reflecting the configuration data in driver settings. The process of acquiring the configuration data and reflecting the configuration data in the driver settings will be described with reference to FIG.
In FIG. 7, first, the printer driver outputs an option information acquisition request to the bidirectional communication module 5. The option information acquisition request is information including an instruction on which device information to acquire, such as tray information (step 1). Next, the two-way communication module 5 checks whether the pseudo network communication module 7 exists (Step 2). If the pseudo network communication module 7 does not exist (No in Step 3), it notifies the bidirectional module 5 that the processing has failed (Step 4), and ends the processing. If the pseudo network communication module 7 exists (Yes in step 3), the pseudo network communication module 7 is called, and based on the port name of the printer 3 (for example, the IP address of the printer 3) collected as described above. Information that matches the option information acquisition request is acquired from the previously stored configuration data file 8 (step 5), and the read data is output to the bidirectional module 5 (step 6). Then, the data is reflected on the settings of the printer driver (step 7).
As described above, in the related art, the configuration data acquisition tool must be used to create configuration data for each printer, so that the burden on the administrator is increased, or the configuration data acquisition tool is used. Previously, printers had to be registered in the client terminal in advance, so that resources were wasted. However, according to the first embodiment, the burden on the administrator is reduced by automating the configuration data acquisition tool. This reduces the need for registering a printer in the client terminal.
[0009]
Next, a second embodiment of the present invention will be described with reference to FIGS. 8, 9, and 10. FIG. The same components have the same reference numbers.
FIG. 8 shows a module configuration of software according to the second embodiment in the metaframe server 1.
As shown in FIG. 8, in the second embodiment, the pseudo network communication module 7 is used without using the normally used network communication module 6. As a result, the printer driver 4 acquires the device information from the pseudo bidirectional communication data 8 stored in advance via the pseudo network communication module 7. Further, a pseudo bidirectional communication data updating module 9 is provided between the printer 3 and the pseudo network communication module 7.
FIG. 9 is an operation flowchart of a pseudo two-way communication data update process according to the second embodiment.
When the pseudo two-way communication data update module is activated in step 10 of FIG. 9, the screen shown in FIG. 10 is displayed, and the update method is set on this screen.
For example, in FIG. 10, one of weekly, daily, and hourly is selected. That is, for example, every week is selected, and the configuration data is updated at 20:00 on Monday.
Alternatively, the configuration data may be selected every day and the configuration data may be updated at 20:00, or may be selected every hour and the configuration data may be updated every hour.
After that, in step 11, when the update time is reached, access information (eg, IP address) to the device is obtained from the configuration data, and device information is obtained from the device based on the access information (steps 12, 13). . Then, in step 14, the configuration data is updated based on the acquired device information.
As described above, in the related art, when there is a change in the device information of the printer, the administrator has to recreate the configuration data of the target printer, so there is no real-time property, and the burden on the administrator increases. However, according to the second embodiment, the latest device information of the printer can be obtained, real-time property can be maintained, and the administrator does not need to recreate the device information.
[0010]
Next, a third embodiment of the present invention will be described with reference to FIGS.
In the third embodiment, access information to the same device as the IP address is extracted from the configuration data based on the port name of the printer 3 (for example, the IP address of the printer 3), and the device is extracted based on the access information. And outputs the received device information to the bidirectional module 5 and reflects the data in the settings of the printer driver.
FIG. 11 is an operation flowchart of a process of acquiring configuration data and reflecting the configuration data in the driver setting according to the third embodiment. The process of acquiring configuration data and reflecting it on driver settings according to the third embodiment will be described with reference to FIG. The same operation has the same step number.
In FIG. 11, first, the printer driver outputs an option information acquisition request to the bidirectional communication module 5. The option information acquisition request is information including an instruction on which device information to acquire, such as tray information (step 1). Next, the two-way communication module 5 checks whether the pseudo network communication module 7 exists (Step 2). If the pseudo network communication module 7 does not exist (No in Step 3), it notifies the bidirectional module 5 that the processing has failed (Step 4), and ends the processing. If the pseudo network communication module 7 exists (Yes in step 3), the pseudo network communication module 7 is called, and based on the port name of the printer 3 (for example, the IP address of the printer 3), the IP from the configuration data is used. The access information to the same device as the address is extracted (step 20). Next, device information is obtained from the device based on the access information (step 21), the received device information is output to the bidirectional module 5 (step 22), and the data is reflected on the settings of the printer driver. (Step 7).
As described above, in the related art, when a large number of printers are used, the amount of configuration data increases, and there is a problem that resources are wasted. However, according to the third embodiment, the configuration data amount is reduced. And the storage capacity can be saved.
The operating methods of the first, second, and third embodiments shown in FIGS. 7, 9, and 11 can be stored as programs in a recording medium such as a CD-R or an image file. .
[0011]
【The invention's effect】
As understood from the above description, in the related art, the configuration data acquisition tool must be used to create configuration data for each printer, so that the burden on the administrator is increased. Prior to using the acquisition tool, the printer must be registered in the client terminal in advance, which wastes resources. However, according to the present invention, by automating the configuration data acquisition tool, the burden on the administrator is reduced. This reduces the need for registering a printer in the client terminal.
Also, in the prior art, when there is a change in the device information of the printer, the administrator has to recreate the configuration data of the target printer, so there is no real-time property, and the burden on the administrator increases. According to the present invention, device information of a recent printer can be acquired, real-time properties can be maintained, and an administrator does not need to recreate device information.
Further, in the prior art, when a large number of printers are used, the amount of configuration data becomes large and resources are wasted. However, according to the present invention, the amount of configuration data becomes small and the storage capacity is reduced. Can save.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating an example of an image printing system in a metaframe environment.
FIG. 2 is a diagram illustrating a configuration of a normal image printing system including a client terminal 2 and a printer 3;
FIG. 3 is a diagram for explaining two-way communication in the related art.
FIG. 4 is a diagram showing a module configuration of the software of the present invention in the metaframe server 1.
FIG. 5 is a diagram for describing acquisition and use of configuration data.
FIG. 6 is a diagram illustrating a screen display example of a configuration data acquisition tool.
FIG. 7 is an operation flowchart of a process of acquiring configuration data and reflecting it on driver settings in the first embodiment.
FIG. 8 is a diagram showing a module configuration of software according to the second embodiment in the metaframe server 1.
FIG. 9 is an operation flowchart of a pseudo two-way communication data update process according to the second embodiment.
FIG. 10 is a diagram illustrating a screen display example of an update setting of a configuration data acquisition tool.
FIG. 11 is an operation flowchart of a process of acquiring configuration data and reflecting the configuration data in a driver setting according to the third embodiment.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Metaframe server, 2 ... Client terminal, 3 ... Printer, 4 ... Printer driver, 5 ... Bidirectional communication module, 6 ... Network communication module, 7 ... Pseudo network communication module, 8 ... Pseudo bidirectional communication data, 9 … Data update module for pseudo two-way communication

Claims (5)

A method for setting device information of a printer in a printer driver in an image printing system in which a client terminal, a printer, and a server having a printer driver of the printer are connected on a network,
Storing the device information of the printer obtained by the server or the client terminal;
A collection step of collecting specific information for specifying a printer connected on the network using a device information acquisition tool,
A device information obtaining step of obtaining device information stored in the server based on a request from the printer driver based on specific information for specifying the collected printer;
A device information reflecting step of transferring the device information to the printer driver. 2. The printer device information setting method according to claim 1, wherein an application for periodically obtaining device information of the printer is prepared, the application is installed on the server, and the device information is periodically updated. And a printer device information setting method. A method for setting device information of a printer in a printer driver in an image printing system in which a client terminal, a printer, and a server having a printer driver of the printer are connected on a network,
Storing the device information of the printer obtained by the server or the client terminal;
A collection step of collecting specific information for specifying a printer connected on the network using a device information acquisition tool,
An access information obtaining step of obtaining access information of the printer based on a specific information specifying the collected printer based on a request from the printer driver,
A device information acquisition step of acquiring device information stored in the server based on a request from the printer driver based on the acquired access information of the printer, and a device information reflection step of passing the device information to the printer driver. A printer device information setting method, comprising: 4. An image printing system for executing a program of the printer device information setting method according to claim 1, 2 or 3. A computer-readable storage medium storing a program for the printer device information setting method according to claim 1.

Images