JP4100895B2 - Network system, information processing apparatus, method, and control program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a network system, an information processing apparatus, a method, and a computer-readable storage medium, and relates to a display and management of PCs and peripheral devices shared on a network.
[0002]
[Prior art]
In recent years, with the spread of peripheral devices such as personal computers (hereinafter referred to as PCs), printers, scanners, digital cameras and the like, networks such as LANs have also spread, and printers, modems, scanners, etc. by a plurality of PCs on the network. The need to share is also increasing. Many drivers for using these peripheral devices have also been provided, and installation methods have also been provided.
[0003]
[Problems to be solved by the invention]
However, when the driver of the peripheral device is upgraded due to a function upgrade or the like, the user himself has to upgrade the driver. When the user upgrades the driver himself / herself, the new driver information is stored in a specific folder on a PC (server PC, etc.) shared on the network, and the driver information is used on each PC that upgrades the driver. It was common to upgrade each version.
[0004]
However, when the version is upgraded by these methods, there are the following problems. That is, user information set as property information for each driver, such as layout information and font information, or device option information set in common in the network system, is set to the initial state of the driver. It is a problem. For this reason, after all, it is necessary to set the property information of the driver that returns to the initial state at the time of installation. For these reasons, not only is the operation of setting the driver property information after installing the driver complicated, but the items to be set are becoming more complicated, which may cause a setting error. There is a problem.
[0005]
Therefore, it is possible to upgrade the driver automatically in the future. For example, the system administrator upgrades the drivers on a plurality of PCs at a time by issuing instructions from the server PC or the like. The upgrade can be performed without the user being aware of the folder in which new driver information is stored on each PC.
[0006]
However, driver installation, version upgrade, and setup procedures vary from device to device. In addition, the type of driver must be selected according to the environment of the device or client device, and the operation is complicated. In addition, complicated processing such as addition or change of drivers based on instructions in the client device and setting of driver property information must be executed in each client, resulting in a problem of very poor work efficiency.
[0007]
As described above, when the user of each PC or the setting of software of the PC is left to the system administrator, there is a problem that the system administrator is loaded and the work efficiency is deteriorated. Furthermore, in recent years, there are many cases where installation is performed on a large number of PCs in a large-scale system. After driver installation for a large number of PCs, it is necessary to set complicated driver properties on a large number of PCs. Under such circumstances, there is a problem that the user's labor and a system administrator for setting a large number of PCs are required, and setting errors often occur.
[0008]
[Means for Solving the Problems]
The present invention has been made in view of the above points, and an object thereof is to provide a mechanism that enables property information to be updated by a simple operation on a network.
[0009]
In addition, when upgrading the version of a driver installed in a client, the driver property information is distributed from the server device and set in the client device in order to reduce the setting effort of the driver property information and reduce setting errors. The purpose is to provide a mechanism to perform the mechanism.
[0010]
Furthermore, in order to reduce the burden of driver installation and property information setting processing that has been performed in each client, a mechanism for performing driver information push installation according to a setup instruction from the server device and performing property information setting processing for the driver The purpose is to provide.
[0011]
In order to achieve the above object, the following means are provided in the embodiment of the present application.
[0012]
In an information processing apparatus that communicates with a client apparatus,
Recognition means for recognizing a plurality of client devices to install driver information; Regardless of whether there is a designation that property information should be transmitted in the user interface that can specify that property information should be sent and property information should not be sent, A process of transmitting driver information without waiting for a driver information transmission request from the client device; Only in the user interface that can specify that property information should be sent and that property information should not be sent, if property information should be sent. Involved in the printing process of the driver information Information that is a combination of multiple print setting items. Property information Select from multiple property information Processing to send to the client device, an instruction to control installation of the driver information in the client device, and the property information related to the print setting is recognized in the driver information in response to the driver information being incorporated in the client device And processing for transmitting a setup instruction including an instruction to the plurality of client devices. Do Transmission control means
Information processing apparatus characterized by having , A method applicable to the apparatus, a control program, and the like are disclosed.
[0024]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of a network system, an information processing apparatus, a method, and a computer-readable storage medium according to the present invention will be described with reference to the drawings.
[0025]
FIG. 1 is a block diagram illustrating the configuration of the apparatus according to the present embodiment. In FIG. 1, reference numeral 1 denotes a system bus, and the following constituent blocks are connected via the system bus 1.
[0026]
Reference numeral 2 denotes a CPU (Central Processing Unit). Reference numeral 3 denotes a program memory (hereinafter referred to as PMEM). A program for processing to be described later is appropriately selected / read from the hard disk 10 and executed by the CPU 2. Data input from the keyboard 12 is stored as code information in the PMEM which is also a text memory.
[0027]
A communication control unit 4 controls input / output data in the communication port 5. A signal output from the communication port 5 is transmitted via a communication line 6 to a communication port of another device on the network (reference numeral 7 in FIG. 1). Exchanges with printers, scanners, etc. shared on the network are performed via this communication control unit 4. In the present embodiment, a network such as a LAN will be described, but it goes without saying that the present invention is applicable even if the communication port 5 and the communication line 6 connected to the communication control unit 4 are general public lines. .
[0028]
Reference numeral 8 denotes an external storage device control unit. 9 and 10 are data file disks, for example, 9 is a floppy disk FD, and 10 is a hard disk HD.
[0029]
An input control unit 11 is connected to input devices such as a keyboard 12 and a mouse 13. The user can issue a system operation command by operating the keyboard 12. In addition, the mouse 13 functions as a pointing device PD for instructing to process image information on the CRT 16, and thereby the cursor on the CRT 16 is moved arbitrarily in the X and Y directions to select a command icon on the command menu. In addition to instructing processing, it is also possible to instruct editing targets, instruct drawing positions, and the like.
[0030]
14 is a video image memory (VRAM), 15 is a display output control unit, and 16 is a CRT (Cathode-Ray Tube). Data displayed on the CRT 16 is expanded as bitmap data on the VRAM 14.
[0031]
Reference numeral 17 denotes a printer control unit which controls data output to the connected printer 18. Reference numeral 1A denotes an image reading device control unit that controls the connected image reading device 1B.
[0032]
Note that the program stored in the PMEM 3 in the present embodiment may be stored in a storage medium such as the hard disk 10 or the floppy disk 9. Furthermore, it may be stored on another device connected to the network.
[0033]
(First embodiment)
Hereinafter, a first embodiment of the present embodiment will be described with reference to FIGS. FIG. 2 is a flowchart showing the processing operation of the PC functioning as the server apparatus. First, in step S201, the server apparatus acquires connection information of all PCs and peripheral devices on the network and stores the information.
[0034]
Next, in step S202, the server apparatus acquires driver setup information, which is a preferable example of peripheral device driver information in each PC. The peripheral device driver is a driver of a printer, a scanner, a digital camera, a FAX, or the like. As a setup information acquisition method, for example, it is conceivable that information is collected by starting a module that acquires driver information installed in the own machine on each PC, and the information is transmitted and received through a network. . In step S203, the server apparatus displays connection information of all PCs and peripheral devices on the network based on the acquired information. In the following, an embodiment using a driver information structure will be described.
[0035]
FIG. 3 is a diagram illustrating an example of a driver information structure that has been set up. It consists of a PC name, an IP address, an OS type, a user name, the number of device drivers, information on each device driver, and property information. Each device driver information includes a device type such as a printer or a scanner, a driver name, version information, an output port, a shared name, a driver information address, a property information name, and a property information address. For example, for the first registered printer, the driver name is LASER830, version is 1.00.00, output port is local, shared name is LASER830, driver information address is 0x10000, property information name is standard setting, property information The address is 0x50000. This information is recorded for each PC.
[0036]
FIG. 4 is a diagram illustrating an example of a property information structure. This example is property information of the printer driver. In this embodiment, an example in which page settings, finishing settings, paper feed settings, and print quality settings are set is shown. The property information includes information that is referred to by the driver module when performing print processing. This structure differs depending on the driver type and version. Property information can also be held in the OS registry. It is also possible to input information to the driver and output the input information as an external file of property information by the driver.
[0037]
Here, FIG. 14 is a diagram showing a driver setting screen. Hereinafter, generation of property information by the driver and external file output processing will be described. Displayed on the CRT of the server device, the user operates a GUI (graphical user interface) on the screen using a pointing device or a keyboard. In the property information, finishing processing represented by the presence or absence of stapling, print quality, paper feed information for operating the device, and the like can be set. Here, as an example, the property information selection tab 1401 is in a state where the page setting tab is selected. Reference numeral 1402 denotes a favorite selection unit for the user to select favorite property information. Reference numeral 1403 denotes a property information addition instruction unit. When the user designates 1403, a property information addition screen (to be described later) shown in FIG. 15 appears. Reference numeral 1404 denotes a property information editing unit. When 1404 is instructed, a favorite edit screen shown in FIG. 17 to be described later appears. Reference numerals 1406 to 1413 denote parameter instruction units for instructing parameters stored in the property information. Output paper size 1406, number of copies 1407, page orientation 1408, 2in1 and other page layouts 1408, page layout arrangement order 1410, presence / absence of stamps 1412 including watermark printing embedded in print data, type of stamp 1411, presence / absence of stapling and sorting Device control information 1413 such as the above method (for example, face-up / face-down) can be designated. Reference numeral 1414 denotes a property information confirmation unit. When the user presses 1414, a screen (not shown) on which the content of the property information parameter can be confirmed is displayed.
[0038]
The administrator operates 1401 to 1421 to store the above parameters as property information in the driver of the server device.
[0039]
FIG. 15 is a diagram showing a property information addition screen. Reference numeral 1501 denotes a name input unit 1501 for inputting the name of property information. An icon designation unit 1502 designates an icon corresponding to property information. A comment input unit 1503 can input a comment related to the property information. Reference numeral 1504 denotes a property information display switching unit. Reference numeral 1506 denotes a property information display unit. Reference numeral 1507 denotes a screen switching button. When OK is pressed, the parameters currently set in the driver (partially displayed in 1506) are registered as property information. In the example of FIG. 15, the property information is stored with the property information name “Procurement Division Order Form”. When the saving process is completed, the screen shown in FIG. 16 which is a property information setting screen is displayed. As shown in FIG. 16, “Procurement Division Order Form” is configured as property information and can be selected 1422. From the next time, when the property information selection unit 1402 is used to specify the property information name “Procurement Division Order Form”, the parameters set earlier in the driver are called, and the parameters are applied to perform printing processing. Can do.
[0040]
FIG. 17 is a property information editing screen. On this screen, the property information instruction unit 1701 can select the name of the property information to be deleted and press the delete button to delete the property information. Similarly, the selected property information can be output to an external file by pressing a 1705 button. Further, by pressing a read button 1705 and selecting a desired external file (not shown), printing parameters can be read from an external file in which print parameters are defined and newly defined as property information.
[0041]
FIG. 18 is an example of a process in which the administrator registers property information in the install server device. Hereinafter, the process of FIG. 18 will be described. The administrator designates and selects parameters relating to the print processing to be stored on the screen of FIG. 14 (S1801). Then, the property information addition instruction unit 1403 is pressed (S1802) to display FIG. Then, a property information name 1501, an icon 1502, and a comment 1503 are input (S1803), an OK button 1507, which is a property information registration instruction, is pressed (S1804), and the property information is registered in the driver (screen in FIG. 14). Back to). When the property information editing unit 1404 is pressed in FIG. 14 (S1805), the screen shown in FIG. 17 is displayed next. When the administrator presses the file save button 1706 in FIG. 17, the driver automatically outputs the property information as an external file to a predetermined directory (S1806). Hereinafter, the externally output file of this property information is referred to as an external file. The administrator creates one or a plurality of property information for each client to be set or for each different printer set for the same client. One or more of these files are created in a predetermined directory. The external file is preferably an external file name associated with the client device name, printer name, or the like. These external files are transmitted to another information processing apparatus and read by a driver or registered in the OS to utilize setting information.
[0042]
FIG. 5 is a diagram showing an example of a screen displaying PCs and peripheral devices on the network. Reference numeral 301 denotes a menu, 302 denotes a toolbar, and 303 denotes a main window on which icons representing PCs and peripheral devices are displayed. 302 a to 302 i are icons representing functions performed by operating the PC and peripheral devices on the toolbar 302. For example, 302a is an icon for executing a copy function for reading image data from a selected scanner and outputting the image data to a selected printer. 302b is a FAX function, 302c is an image data reading function, 302d is a function for reading image data and performing OCR processing, 302e is a function for managing FAX reception data and distribution data, 302f is a display switching function, and 302g is a display screen editing function. , 302h is a function for performing an information update process, and 302i is an icon for executing a function for canceling the update process.
[0043]
303a to 303q are icons representing PCs and peripheral devices shared on the network. These icons 303a to 303q are displayed with the icons changed depending on the device type such as PC, printer, scanner, FAX modem, or status such as “processing in progress” or “error occurred”. 303c is an icon representing the own device, and 303b is an icon representing the domain to which the own device is logged on. Since the own device is a special device, it is displayed at the top in distinction from other PCs. Other PCs are displayed in ascending or descending order in alphabetical order.
[0044]
In addition, a PC and peripheral devices that are shared on the network like the icon 303p but have no driver installed are displayed in gray. A “+” mark is displayed when there is a connected device such as the icon 303j but it is not expanded and displayed, and a “−” mark is displayed when it is expanded as the icons 303h, 303k, and 303n. Is done. If there is no connected device like the icon 303q, no mark is added.
[0045]
In this way, it is possible to confirm the connection status and status of all PCs and peripheral devices on the network on the screen. In this example, not all icons are displayed for the convenience of the screen, but all PCs and peripheral devices can be confirmed using a scroll bar arranged on the side of the screen.
[0046]
FIG. 6 is a diagram showing an example of a screen that displays the driver setup status of each PC on the network, and is displayed based on the driver information structure acquired from each PC. In the figure, the drivers installed in “My PC” are six printers and two scanners. Among these, for example, a printer named “INKJET-10V” has a driver name “INKJET-10V”, a version number “1.00.00”, property information “standard setting”, and “INKJET-10V”. ”Indicates that the printer driver is shared on the network set to be shared.
[0047]
Returning to the flowchart of FIG. 2, in step S204, the setup program including the installer in the server apparatus determines whether property information is requested. Here, if the property information is not requested, the process is terminated. When the setup program in the server apparatus determines that the property information is requested, the process proceeds to step S205. As a method for requesting property information, it is conceivable to display a menu by operating the mouse on each device and request the property information of the corresponding driver from the server.
[0048]
In step S205, the setup program in the server device determines whether there is property information of the requested driver. Then, if there is no property information, the setup program in the server device notifies that there is no corresponding property information and ends the process. If there is corresponding property information, the setup program in the server apparatus proceeds to step S206. Even if the same device is used, supported functions may differ depending on the version. Therefore, the presence / absence of driver property information may be determined based on the device type, driver name, and version information. Judgment is made by comparing whether or not all the information matches.
[0049]
In step S206, a corresponding property information list is transmitted to the requested PC. Here, it is possible to reduce traffic on the network by transmitting the minimum information necessary for the user to select instead of transmitting all information to the requested PC.
[0050]
Further, in step S207, the setup program in the server apparatus determines whether or not there is a request for property information from the PC. If there is no request, the process is terminated. If there is a request, the process proceeds to step S208, and the setup program in the server apparatus requests the OS in the server apparatus to transmit the property information of the requested driver, and ends the process.
[0051]
On the other hand, FIG. 7 is a flowchart showing the processing operation of the PC functioning as the client device. First, in step S601, it is determined whether or not to acquire driver property information from the server apparatus. Here, when not acquiring, a process is complete | finished.
[0052]
In the case of acquisition, the setup program in the server apparatus moves to step S602 and requests the server apparatus for a list of property information of the corresponding driver. When requesting, the device type, driver name, and version information are transmitted.
[0053]
In step S603, the setup program in the server apparatus determines whether or not the driver property information list has been acquired. If the driver property information corresponding to the server device is not available, the processing is terminated.
[0054]
When the property information list can be acquired, the process proceeds to step S604, and it is determined whether or not the property information is acquired. If the driver property information is not acquired, the process ends.
[0055]
When acquiring the property information of the driver, the process proceeds to step S605, and a property information acquisition request is transmitted to the server device. In step S606, it is determined whether property information has been acquired. If it cannot be obtained, the process returns to step S605 and continues to wait until it can be obtained.
[0056]
If the property information can be acquired, the process proceeds to step S607, and the corresponding driver is updated based on the acquired property information.
[0057]
(Second Embodiment)
In the flowcharts shown in FIGS. 2 and 7, all of the driver property information is centrally managed by the server device. In this case, large-size information is exchanged on the network. Therefore, in order to prevent an increase in traffic, only minimum information is registered and managed in the server device, the property information body is managed by each PC, and when property information is required, a request from the server device A method of receiving and transmitting to a designated PC is also conceivable.
[0058]
FIG. 8 is a flowchart showing the processing operation of the server device when each client device manages the property information of the driver installed in the own device, and FIG. 9 is a flowchart showing the processing operation of the client device. Steps S1101 to S1107 in FIG. 8 are the same as steps S201 to S207 in the flowchart of FIG.
[0059]
In step S1108, the device type, driver name, version information, property information, and PC information to be transmitted are transmitted to the PC that manages the property information of the driver, and the property information is transmitted to the designated PC. Instruct to send.
[0060]
On the other hand, as shown in FIG. 9, the client device determines whether there is a property information transmission request from the server device in step S1201. If there is no request, the process is terminated.
[0061]
If there is a transmission request, the process proceeds to step S1202, and the property information of the instructed driver is read from the management data. As the structure of the management data, a structure similar to the structure shown in FIG. 3 can be considered. In step 1203, the property information is transmitted to the designated PC.
[0062]
(Third embodiment)
In the first and second embodiments described above, the case where there is a request from the client device has been described, but it is also conceivable to perform an operation from the server device to the corresponding client device. 10 and 11 are flowcharts showing processing operations of the server device and the client device in that case.
[0063]
FIG. 10 is a flowchart showing the processing operation of the server apparatus. Steps S701 to S703 are the same as steps S201 to S203 in the flowchart of FIG.
[0064]
In step S704, the setup module in the client device determines whether to update the property information of the client device. If there is no update instruction, the process ends. If there is an update instruction, the process proceeds to step S705. As an operation method here, for example, it is conceivable to select a certain driver and instruct update / setup of property information. The update / setup instruction is preferably realized by using Remote Precure Call (remote procedure call, hereinafter referred to as RPC) or SOAP (Simple Object Access Protocol) which is an example implemented by XML using object orientation. . For example, as an example of the update instruction from the server device, there is RPC that remotely calls the update processing module of the client device.
[0065]
In step S705, based on the information acquired in step S702, it is recognized whether there is a client device in which the instructed driver is installed. If there is no corresponding client device because the corresponding PC is turned off or the driver has been deleted, the processing is terminated. If there are corresponding PCs, those PCs are displayed. FIG. 12 shows an example of a screen when there is a corresponding PC. Here, the PC whose property information is to be updated is selected.
[0066]
In step S706, the setup module in the client apparatus controls the OS to transmit a property information update notification to the PC instructed to update. In step S707, the setup module in the client device determines whether there is a property information transmission request from each client device. If there is no transmission request, the process proceeds to step S709. If there is a transmission request, the process proceeds to step S708, and the setup module in the client device generates an instruction for controlling the OS to transmit the designated property information to the requested PC. Here, the property information is a file described in a predetermined data format. In the client PC on which the driver is installed, the property information can be input or output by the user instructing the driver.
[0067]
In step S709, the setup module in the client apparatus determines whether there is a response from all the PCs that have made the update notification. Here, if there is a response from all the PCs, the process is terminated. If there is no response from all the PCs, the process returns to step S708 to continue the process.
[0068]
On the other hand, FIG. 11 is a flowchart showing the processing operation of the client device. First, in step S901, it is determined whether a property information update notification has been received from the server device. If there is no notification, the process ends.
[0069]
If there is a notification, the process moves to step S902 to determine whether or not to update the property information. FIG. 13 is an example of a message displayed in that case. Here, when “No” is selected to cancel the update, the server apparatus is notified that the update is not performed, and the process ends. If “Yes” is selected and the update is performed, the process proceeds to step S903, a request for transmitting property information is sent to the server, and the process proceeds to step S904.
[0070]
In step S904, the setup module in the client apparatus determines whether property information and setup information have been acquired from the server apparatus. If not acquired, the process returns to step S903 and continues to wait until acquisition is possible. If the property information and the setup information can be acquired, the process proceeds to step S905, and the property information of the driver designated based on the acquired information is updated and set according to the setup instruction included in the setup information.
[0071]
Here, the setup instruction controls, for example, a process in which the setup module in the client apparatus calls the API of the OS in the client apparatus and registers the received property information in the registry area of the OS. Further, the setup instruction may control a process for issuing an instruction for instructing the driver setup module to read property information to the driver.
[0072]
In this example, the confirmation message is displayed in step S902. However, the update process may be automatically performed without displaying the message.
[0073]
As described above, in this embodiment, the PC and peripheral devices shared on the network are displayed in the window, and the property information of the peripheral driver is shared on the network. Property information can be updated. Also, common property information can be set for each client device from the server device. Further, by distributing property information management to client devices and exchanging information as necessary, traffic on the network can be minimized.
[0074]
(Fourth embodiment)
In the third embodiment, the setting or updating of the driver property information has been described. However, in this embodiment, when the server device side newly adds or updates the driver of the client device, the client device actively This is a process for distributing the driver without waiting for the request. In the present embodiment, parts different from the above-described embodiment will be described. The setup program in the install server device 385 calls the API or system call of the OS without waiting for the driver information transmission request from the client device, and controls the driver setup instruction and the process of distributing the driver. In parallel, the setup program sends the driver property information to be transmitted to the client device either spontaneously from the installation server or after waiting for a client request after the driver is installed. Control.
[0075]
FIG. 20 is a diagram illustrating an example of a printing system according to the present embodiment. A client apparatus A indicated by 381 which is a preferable example of a client, a client apparatus B indicated by 382, a client apparatus C indicated by 383, an install server apparatus 385 which is a preferable example of a server apparatus, and a web server apparatus 386 are suitable for a network. They are connected via a LAN (local area network) 380 as an example. In the present embodiment, the install server device 385 and the web server 386 are client devices 381 to 383 each including a PC as a preferred example of an information processing device, and the internal structure thereof is the same as that shown in FIG.
[0076]
FIG. 23 is a diagram illustrating a software module as a preferred example in each client apparatus.
[0077]
FIG. 23 is a diagram illustrating a module configuration of the client apparatus. An example of installation processing in the driver client will be described with reference to FIG. An OS is installed in the client device. The area of the software module in each client device is divided into a user area 377 and an OS area 378. The driver installation module 371 is prepared as an application that runs on the OS. The system program 379 manages the driver name, printer name, and driver directory stored in the client device by registering them in the registry 376.
[0078]
The driver installation module 371 calls the system installer 374 via an API (Application Programming Interface). The system installer is prepared as a function of the OS. In response to a command from the driver installation module 371, the driver 372 installed from the outside and stored in the user area 376 is copied or moved to the system file area 375. . A part of the system file area has a registry area 376 for registering various types of information on devices using the driver. In addition, the driver installer module 371 can call the system installer 374 to store the driver setup information and property information in the registry area. A registry may be prepared for each user.
[0079]
Here, the driver installation module 371 calls the OS API for registering the property information in the registry 376 according to the setup instruction received from the external device, or calls the driver installed in the system file to obtain the property information. Perform the process to read. For example, for each printer registered in the OS of the client device, the driver property information can store favorite print settings as property information in the registry area of the OS.
[0080]
The driver property information may be received from the installation server apparatus in the external file format described with reference to FIG. 14 and read into the file system in the user area 376. In this case, the driver property information in the file format can be automatically read by the driver installer, passed to the driver, and the driver property information can be reflected in the driver settings.
[0081]
FIG. 19 is a diagram illustrating an example of processing in which the install server device distributes the driver to the client device and sets property information. In the present embodiment, as described above with reference to FIG. 14, the driver property information is information output by the administrator in the installation server device as an external file. This process is started when a setup program having a remote installation function installed in the installation server device 385 is activated. In the processing of FIG. 19, the setup program in the installation server device 385 distributes the driver by push installation without waiting for a request from the client device. The setup program (management means) in the install server device 385 manages the property information for each printing device registered in the OS, and distributes the property information suitable for the function and option for each model of the printer. It is also conceivable to perform the distribution process of property information by controlling the OS.
[0082]
The OS of each client device that has received the driver and setup information from the install server device via the network inputs the property information of the driver and the property information setup instruction to the driver installer (input means). Based on the setup instruction, the installer installs the property information in the OS in the install server device 385 so that the driver in the install server device 385 can recognize the property information. For example, upon receiving a setup instruction command, the driver installer causes the driver to recognize the property information input from the OS by inputting the property information to the driver. In response to the setup instruction, the driver installer calls the API of the OS and registers the property information in the OS registry, and the driver recognizes the property information via the OS.
[0083]
The operation of the installer in the install server device 385 will be described below. Hereinafter, the client device A, the client device B, and the client device C are collectively referred to as “each client device”.
[0084]
The description of the processing in FIG. First, in step S1901, the setup program in the install server device 385 determines whether or not a remote installation instruction has been issued to each client device for a driver. For example, when the user operates the mouse 13 or the keyboard 12 with reference to the graphical user interface displayed on the CRT 16 of the installation server device 385 in FIG. 1, the setup instruction is issued in response to the operation. Input to the input control unit 11. Here, if the setup program in the install server device 385 does not determine that there is no instruction for remote installation, the process ends. On the other hand, if it is determined in S1901 that the setup program in the installation server device 385 has instructed remote installation, the process advances to step S1902 to create setup information of the driver to be remotely installed. The driver setup information includes information such as a driver name to be installed, a driver main body, a printer name, an output port name, and a module for making the port available. The printer name is registered and managed in the OS registry of each client device.
[0085]
Here, the process of S1902 will be described in detail with reference to FIG. FIG. 21 is an example of a screen for setting driver information displayed on the CRT of the install server device. The administrator uses the setting screen to create setup information including a setup instruction. Reference numeral 331 denotes a printer name instruction unit. The printer name instruction unit 331 can select or input a printer name to be registered in each client device. A plurality of printers searched on the network may be designated by the printer name designation unit 331. Reference numeral 332 denotes a port designation unit. In the port designation section, a port can be added by pressing the 334 port addition instruction section with a mouse. In the setting example of FIG. 21, the IP address as information indicating the location of the printer on the network, the fact that lpr is used as the printing protocol, and the logical ports associated with these are created. Show. lpr is a traditional print management program, but of course, other print management programs may be used. Further, a network protocol different from TCP / IP may be used. Reference numeral 333 denotes a driver designation unit for instructing a driver to be installed in each client device. A driver can be specified by operating the driver addition instruction unit 335. The above is an example of creating a port when printing is performed for a network printer using TCP / IP and lpr. Ports can also be created for local printers. For example, when setting a local printer of a client device, a COM port or an LPD port may be designated and setup information may be created based on this. In addition, a port can be set to indicate printing via a print server. For example, if the print server name of the print server 387 is “SVPC1” and the printer name of the printer 384 is LASER 950, if the port is specified as “¥¥ SVPC1 ¥ LASER950”, printing is performed on the LASER 950 with the SVPC1 as the print server. The port to perform is set
When the OK button on the screen of FIG. 21 is pressed, FIG. 22 is displayed, and the flow proceeds to S1903 and S1904.
[0086]
In step S1903, the setup program in the installation server device 385 selects a client device for installing the selected driver on the setting screen shown in FIG. It is also possible to select a plurality of distribution destination client devices at the same time.
[0087]
FIG. 22 is an example of a client device that sets up the driver used in the processing of FIG. 19 and a screen for instructing setting of property information. It is also possible to select a plurality of client devices at the same time. Also, the property information distribution setting unit 221 can set ON / OFF of property information setting processing execution. Using the property information file selection unit 222, the property information file created using the setting screen of FIG. 17 and desired to be distributed to each client device is selected. FIG. 22 shows a state in which property information A is selected. In this example, one or a plurality of client devices in the domain are selected, but designation across the same domain is also possible.
[0088]
In S 1904, the setup program in the installation server device 385 specifies whether or not to distribute the property information based on the input from the property information distribution setting unit 221, and further receives the input from the property information file selection unit 222. Specify the property information name to be distributed based on this.
[0089]
In step S1905, the setup program in the installation server device 385 determines whether the setup program is set to execute the driver property information setting processing when the driver installation is completed on each client device. If the setup program in the install server device 385 determines that the driver property information is not set to be set in the client, the process of step S1907 is performed. If it is set to execute the property information setting process in the property information setting process client, the process advances to step S1906. In S1906, the setup program in the install server device 385 automatically reads the external file corresponding to the property information name specified in S1904 including the property information. Here, the external output file is created by the administrator, is automatically read from the directory in the install server device 385 where the file specified in S1904 is stored, and the property information body and the property information to be distributed are set up as setup information. Add additional memory.
[0090]
In step S1907, the setup program (recognition means) in the server device 385 recognizes the driver setup information including the setup instruction set and recognized in the above-described process, and the driver to be installed. Further, the setup program determines and recognizes the client device that installs one or more drivers instructed in S1903, instructs the OS via the API to distribute to the determined client device, and performs processing. finish. It is preferable that the install server device 385 starts the distribution process of the property information in the install server device 385 in response to the driver installation start instruction input.
[0091]
In the processing of FIG. 19, the OS type and OS version are automatically determined by the install server device 385 based on the information of each client device collected and stored in the install server device 385 in advance. . However, if it is not possible to automatically determine the OS installed in each client device, before the setup program generates the setup information in S1902, the user can change the OS type and version, and the graphical user interface shown in FIG. You may change so that a kind and the architecture of CPU can be designated. In the processing of FIG. 19, the property information is actively distributed without waiting for a request from the server, but the installation server device 385 responds to the property information transmission request from each client device. The property information may be transmitted.
[0092]
The property information is output as an external file by the driver, distributed from the install server device 385, and used in each client device. Each client device automatically reads property information from the external file acquired from the install server device 385 outside each client device, and inputs the read property information into a driver in each client device to be read.
[0093]
As described above, according to the embodiment of the present invention, push installation is performed from the installation server device to the client device, and property information is set at the same time. Therefore, driver installation and update processing, and property information Settings can be made at once. Therefore, there is an effect that the labor of driver installation / update / setting processing can be reduced as a whole. When this processing is performed for a plurality of client devices, there is an effect that a significant labor can be reduced.
[0094]
(Other embodiments)
Software program for realizing the functions of the above-described embodiment for an apparatus or a computer in the system connected to the various devices so as to operate the various devices to realize the functions of the above-described embodiments. What was implemented by supplying the code and operating the various devices in accordance with a program stored in a computer (CPU or MPU) of the system or apparatus is also included in the scope of the present invention.
[0095]
In this case, the program code itself of the software realizes the functions of the above-described embodiment, and the program code itself and means for supplying the program code to the computer, for example, the program code are stored. The recorded medium constitutes the present invention. As a recording medium for storing the program code, for example, a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.
[0096]
Further, by executing the program code supplied by the computer, not only the functions of the above-described embodiments are realized, but also the OS (operating system) or other application software in which the program code is running on the computer. Needless to say, the program code is also included in the embodiment of the present invention even when the functions of the above-described embodiment are realized in cooperation with the above.
[0097]
Further, after the supplied program code is stored in the memory provided in the function expansion board of the computer or the function expansion unit connected to the computer, the CPU provided in the function expansion board or function expansion unit based on the instruction of the program code Needless to say, the present invention also includes the case where the functions of the above-described embodiment are realized by performing part or all of the actual processing.
[0098]
It should be noted that the shapes and structures of the respective parts shown in the above embodiments are merely examples of implementation in carrying out the present invention, and these limit the technical scope of the present invention. It should not be interpreted. That is, the present invention can be implemented in various forms without departing from the spirit or the main features thereof.
[0099]
【The invention's effect】
As described above, according to the present invention, the driver property information can be shared on the network, so that the driver property information can be updated with a simple operation. Also, common property information can be set for each client device from the server device.
[0100]
Also, in the driver installed in the client, the driver property information is distributed from the server device and set in the client device, so that the effort for setting the driver property information can be reduced and setting errors can be reduced. .
[0101]
Furthermore, push installation of the driver is performed according to the setup instruction from the server device, and the property information setting processing for the driver is performed, so that the burden of driver installation and property information setting processing performed on each client is reduced. Can do.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a schematic configuration of an apparatus according to an embodiment.
FIG. 2 is a flowchart showing a processing operation of a PC functioning as a server device.
FIG. 3 is a diagram illustrating an example of a driver information structure.
FIG. 4 is a diagram illustrating an example of a property information structure.
FIG. 5 is a diagram illustrating an example of a screen displaying a PC and peripheral devices on a network.
FIG. 6 is a diagram showing an example of a screen that displays the driver setup status of each PC on the network.
FIG. 7 is a flowchart showing a processing operation of a PC functioning as a client device.
FIG. 8 is a flowchart showing the processing operation of the server device.
FIG. 9 is a flowchart showing processing operations of the client device.
FIG. 10 is a flowchart showing a processing operation of the server apparatus.
FIG. 11 is a flowchart showing a processing operation of the client device.
FIG. 12 is a diagram illustrating an example of a screen for selecting a PC for updating property information.
FIG. 13 is a diagram illustrating an example of a screen displayed when a property information update notification is received.
FIG. 14 illustrates a driver setting screen.
FIG. 15 is a diagram showing a property information addition screen.
FIG. 16 is a diagram showing a property information setting screen.
FIG. 17 is a diagram showing a property information editing screen.
FIG. 18 is a diagram illustrating an example of processing in which an administrator registers property information in an install server device.
FIG. 19 is a diagram illustrating an example of a process in which an install server device distributes a driver to a client device and sets property information.
FIG. 20 is a diagram illustrating an example of a printing system according to the present exemplary embodiment.
FIG. 21 is a diagram showing an example of a screen for setting driver information displayed on the CRT of the install server device.
FIG. 22 is a diagram illustrating an example of a client device that sets up a driver used in the process of FIG. 19 and a screen that instructs setting of property information.
FIG. 23 is a diagram showing a software module as a preferred example in each client device;
[Explanation of symbols]
1 System bus
2 CPU
3 Program memory
4 communication control section
5 Communication port
6 Communication line
7 Other devices on the network
8 External storage controller
9 Floppy disk
10 Hard disk
11 Input control unit
12 Keyboard
13 mouse
14 Video image memory
15 Display output controller
16 CRT
17 Printer control unit
18 Printer
1A Image reading device controller
1B Image reading device
221 Property information distribution setting section
222 Property information file selection section
331 Printer name instruction section
332 Port designation part
333 Driver specification part
334 Port addition instruction section
335 Driver addition instruction section
371 Driver installation module
372 driver
373 API
374 System Installer
375 System file area
376 Registry
377 User area
378 OS area
379 system program
380 LAN
381 Client device A
382 Client device B
383 Client device C
385 Install server device
386 Web server device
1401 Property information selection tab
1402 Favorite selection section
1403 Property information addition instruction section
1404 Property information editing section
1406 Paper size instruction section
1407 Number of copies instruction section
1408 Print direction indicator
1409 Page layout instruction section
1410 Page layout arrangement order instruction section
1411 Stamp type designation section
1412 Stamp presence / absence instruction section
1413 Device control information instruction section
1414 Property information confirmation part
1501 Name input part
1502 Icon designation part
1503 Comment input part
1504 Property information display switching section
1506 Property information display area
1507 Screen switching button
1701 Property information instruction section
1705 File reading instruction section
1706 External file save instruction section

Claims (19)

In an information processing apparatus that communicates with a client apparatus,
The recognition means for recognizing a plurality of client devices on which driver information is to be installed, and the user interface capable of specifying that property information should be transmitted and that property information should not be transmitted, that property information should be transmitted Regardless of whether or not there is a specification, a process for transmitting driver information without waiting for a driver information transmission request from the client device, and a specification that property information should be transmitted and property information should not be transmitted In a user interface capable of printing, a property that is information related to the print processing of the driver information and is a combination of a plurality of print setting items only when the property information is to be transmitted. information, the client instrumentation selected from among a plurality of property information An instruction to control the installation of the driver information in the client device and an instruction to make the driver information recognize the property information related to the print settings in response to the driver information being incorporated in the client device. and transmission control means for controlling the process of transmitting the setup instructions to the plurality of client devices including
An information processing apparatus comprising: The transmission control unit distributes the created property information to a plurality of client devices recognized by the recognition unit in response to a setup start instruction in the information processing apparatus. The information processing apparatus described.   The information processing apparatus according to claim 1, wherein the setup instruction includes a setup instruction for controlling the client apparatus so that the client apparatus registers the property information in an OS.   2. The management unit for managing the property information for each printing apparatus registered in an OS, wherein the transmission control unit controls processing for distributing property information corresponding to the printing apparatus. The information processing apparatus according to any one of 1 to 3.   5. The transmission control unit according to claim 1, wherein the information processing apparatus controls processing of distributing the property information in response to an input of a driver setting start instruction in the information processing apparatus. The information processing apparatus described in 1. The set-up instructions, the information processing apparatus according to any one of claims 1 to 5, characterized in that it is realized by the simple object access protocol. Said transmission control means, the information processing apparatus according to any one of claims 1 to 6, wherein the controller controls the process of transmitting the property information in response to the setup start instruction in said information processing apparatus . It said transmission control means, together with the driver information processing apparatus according to any one of claims 1 to 7, characterized in that to control the process of transmitting the property information to the client device. Said transmission control means is responsive to a transmission request property information from the client apparatus, information processing apparatus according to any one of claims 1 to 8, characterized in that controlling the process of transmitting the property information . In an information processing apparatus that communicates with a client apparatus,
In the recognition process for recognizing a plurality of client devices to install driver information, and in a user interface that can specify that property information should be sent and property information should not be sent, property information should be sent Regardless of whether or not there is a specification, a process for transmitting driver information without waiting for a driver information transmission request from the client device, and a specification that property information should be transmitted and property information should not be transmitted In a user interface capable of printing , only when it is specified that property information should be transmitted, information related to the print processing of the driver information, which is information combining a plurality of print setting items. information, the client instrumentation selected from among a plurality of property information An instruction to control the installation of the driver information in the client device and an instruction to make the driver information recognize the property information related to the print settings in response to the driver information being incorporated in the client device. and a transmit control step to control braking and processing for transmitting the setup instructions to a plurality of the client devices
An information processing method comprising: In the transmission control step, to a plurality of client devices the recognition means recognizes, the property information created in claim 10, characterized in that the bulk distribution according to the setup start instruction in said information processing apparatus The information processing method described. 12. The information processing method according to claim 10, wherein the setup instruction includes a setup instruction for controlling the client apparatus so that the client apparatus registers the property information in an OS. Further comprising a management step of managing for each printing device to be registered with the property information in OS, the transmission control step, according to claim 10, characterized by controlling the process of distributing the property information corresponding to the printing device 13. An information processing method according to any one of 12 to 12 . The information processing according to claim 10 , wherein the transmission control step controls a process of distributing the property information in response to an input of a driver setting start instruction in the information processing apparatus. Method.   15. The information processing method according to claim 10, wherein the setup instruction is realized by a simple object access protocol. The transmission control information processing method according to any one of claims 10 to 15 in response to the setup start instruction before the SL information processing apparatus and controls the process of transmitting the property information. 17. The information processing method according to claim 10 , wherein the transmission control step controls a process of transmitting the property information to the client device together with the driver information. 18. The information processing method according to claim 10 , wherein the transmission control step controls a process of transmitting the property information in response to a property information transmission request from the client device. . In a control program capable of controlling an information processing device communicating with a client device,
In the recognition process for recognizing a plurality of client devices to install driver information, and in a user interface that can specify that property information should be sent and property information should not be sent, property information should be sent Regardless of whether or not there is a specification, a process for transmitting driver information without waiting for a driver information transmission request from the client device, and a specification that property information should be transmitted and property information should not be transmitted In a user interface capable of printing , only when it is specified that property information should be transmitted, information related to the print processing of the driver information, which is information combining a plurality of print setting items. information, the client instrumentation selected from among a plurality of property information An instruction to control the installation of the driver information in the client device and an instruction to make the driver information recognize the property information related to the print settings in response to the driver information being incorporated in the client device. control program characterized Rukoto to execute a transmit control step of controlling the process of transmitting the setup instructions to a plurality of the client device to a computer, including.

Images