JP4071587B2 - Peripheral equipment management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a client-server type peripheral device management system having a configuration in which a peripheral device and an information processing apparatus are connected via a network.
[0002]
[Prior art]
Conventionally, a peripheral device management system has been proposed in which a peripheral device and an information processing device are connected to a network and the peripheral device is managed by the information processing device. Among the peripheral device management systems in recent years, a system in which a printer is connected as a peripheral device responds to a print request from an information processing apparatus (hereinafter referred to as “client”) such as a PC (Personal Computer) operating as a client. Peripheral device management system that aggregates information such as “when, where, what, and how much has been printed” to ascertain the status of printing and to impose a printing fee attributable to the print job issuer. Has been. This peripheral device management system is designed to reduce the amount of wasted paper for the purpose of reducing TCO (Total cost of ownership) and acquiring ISO (International Organization for Standardization) 4001. It is for tackling such issues as Therefore, it is desirable to be able to grasp as accurately as possible the status of printing in the printer including the printing time.
As a conventional technique in this regard, a technique related to a system that simply sets time information to print log data has been proposed even for inexpensive peripheral devices that do not hold a clock (see, for example, Patent Document 1). .
[0003]
[Patent Document 1]
JP 2001-325083 A (first page)
[0004]
[Problems to be solved by the invention]
Specifically, in the system described in Patent Document 1, the time information generated by the client is added to the print job, so that the printing apparatus extracts the time information from the print job and converts it into print log data. The method of including is used. As a result, even in a printing apparatus that does not hold clock information, it is possible to leave the print time in the print history.
However, referring to the time information generated by the client as in this prior art, if there are a plurality of clients constituting the system and variations occur in the time of each client, the usage status of the peripheral device (printer) (job In other words, it is impossible to grasp the implementation status of the print log at a unified time, and the order of the print log generation times cannot be managed accurately. This becomes a fatal problem as the number of clients constituting the system increases.
[0005]
The present invention has been made to solve the above-described problems. In a peripheral device management system including an information processing apparatus that operates as a client and peripheral devices, the present invention is influenced by a time lag measured by the client. The purpose is to manage the job execution time at a unified time, and to correctly grasp the job execution status in the peripheral device.
[0006]
[Means for Solving the Problems]
In order to achieve the above object, the present invention provides a client having means for generating job record information representing job execution records including job execution time, and transfer means for transferring the job record information to the outside, A peripheral device management system for managing a job execution status in a peripheral device by a server having means for accumulating the job record information transferred from the client, wherein the client time measured by the client and the server Using the time correction data calculating means for calculating time correction data representing the difference between the measured server times and the time correction data calculated by the means, the execution time included in the job record information is set as the server time. only set a correcting means for correcting, the time correction data calculating means, calculate the time correction data And means for acquiring the server time from the server and calculating and holding the time correction data when it is determined that the time correction data has not been calculated by the means. And means for obtaining the server time from the server and updating the held time correction data even after the transfer of the job record information by the transfer means .
The peripheral device management system includes means for determining whether or not the server time can be acquired from the server, and when the means determines that the server time cannot be acquired, the time correction data calculation means performs the following from the client. The time correction data may be calculated using the server time acquired from the server immediately before transferring the job record information.
[0007]
Also, means for determining whether or not the job record information can be transferred by the transfer means is provided, and when the means determines that transfer is not possible, the time correction data calculating means receives the job record information from the server immediately before the next transfer of the job record information. The server time may be acquired and the time correction data may be updated.
Further, a means for determining whether or not the client time has been changed after calculating the time correction data, and when the means determines that there is a change, the correction means then determines the client time for the most recent job recording information. The execution time may be corrected using the time correction data calculated before the change, and the transfer unit may transfer the corrected job record information.
[0008]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram of a peripheral device management system 1 according to the present invention. The peripheral device management system 1 includes a plurality of clients and peripheral devices, and includes a first client 2, a second client 3, a time management server 4, a first peripheral device 5, 2 peripheral devices 6, each connected to a network 7 (for example, the Internet).
The first and second clients 2 and 3 are information processing apparatuses such as personal computers, and are computers having a function of connecting to and communicating with the network 7 and have the same configuration. For example, in the case of the first client 2, the first and second clients 2 and 3 are, as shown in FIG. 2, a CPU (Central Processing Unit) 2a, a ROM (Read Only Memory) 2b, and a communication control device. 2c and a clock 2d for measuring time, the CPU 2a operates according to a program stored in the ROM 2b, and issues jobs to the first and second peripheral devices 5 and 6, for example, first and second Functions as means for issuing a print job requesting the peripheral devices 5 and 6 to print, and means for generating job record information (for example, a print log) representing job execution records including job execution times such as print jobs And the generated job record information is transmitted to the time management server 4 connected via the network 7 by the communication control device 2c. To realize the function as a transfer means for feeding.
[0009]
The time management server 4 is an information processing apparatus such as a computer having means for connecting to the network 7 for communication, and has a clock for measuring a reference time in the system, and includes first and second clients. Means for collecting and accumulating job record information transferred from 2 and 3 and execution records of each operation job of printing, copying, facsimile communication, and scanner performed by the first and second peripheral devices 5 and 6; Have.
The first and second peripheral devices 5 and 6 include means for realizing at least one of a print function, a copy function, a facsimile communication function, and a scanner function, and a means for performing communication by connecting to the network 7. It is a device that has.
Next, the operation content of the peripheral device management system 1 configured as described above will be described with reference to the flowchart shown in FIG. The flowchart shown in FIG. 3 is a flowchart showing a procedure of correction processing for correcting the execution time of a print job (hereinafter, this time is referred to as “print time”) executed in each of the first and second clients 2 and 3. is there. In the following description, a print job is issued from the first and second clients 2 and 3 to the first and second peripheral devices 5 and 6, and time management is performed using the print job record information as job record information. It is transferred to the server 4.
[0010]
First, in the peripheral device management system 1 shown in FIG. 1, when the standard time in Japan is “10:00”, the time (client time) indicated by the clock 2d of the first client 2 is “9:00”. The time (client time) indicated by the clock of the second client 3 is “11:00”, and the time (server time) indicated by the clock of the time management server 4 is “10:00”. That is, it is assumed that the clocks of the first and second clients 2 and 3 and the time management server 4 have different current times.
At this time (standard time), when the user designates a printing operation in each of the first and second clients 2 and 3, the printing time by each CPU (the first client 2 is the CPU 2a). The correction process starts and proceeds to step 1. In step 1, the first and second clients 2 and 3 generate a print request by designating the print operation, and the first and second clients 2 and 3 issue a print job. Here, it is assumed that the print job is issued simultaneously from the first and second clients 2 and 3. At this point, the client times of the first and second clients 2 and 3 that issued the print job are adopted as the print times included in the print log that is the job record information, and the values are held.
[0011]
After the print job is issued, the CPU proceeds to step 2 for both the first and second clients 2 and 3 to determine whether the time correction data has been calculated. If uncalculated, proceed to step 3. When the process proceeds to step 3, the CPU communicates with the time management server 4 via the network 7 and acquires the server time from the time management server 4. In the subsequent step 4, each of the CPUs of the first and second clients 2 and 3 operates as time correction data calculation means, and calculates time correction data. This time correction data is data representing the difference between the client time and the server time acquired from the time management server 4. In the above description, the client times of the first and second clients 2 and 3 are “9:00” and “11:00”, respectively, and the server time is “10:00”. Since the client times of the clients 2 and 3 are “1 hour delay” and “1 hour advance” respectively with respect to the server time, the time correction calculated by the first and second clients 2 and 3 is performed. The data is “−10: 00” and “+10: 00”, respectively (“−”: minus means time delay, “+”: plus means time advance). However, if both the first and second clients 2 and 3 have already calculated the time correction data when the previous print job is issued and hold the time correction data, this processing is not performed.
[0012]
Subsequently, the process proceeds to step 5, and the first and second clients 2, 3 correct the print time included in the print log using the time correction data calculated in step 4 by the CPU operating as the correction unit. In subsequent step 6, the CPU communicates with the time management server 4 via the network 7 and transfers the corrected print log to the time management server 4.
Here, since the client time of the first client 2 is “9:00” and the client time of the second client 3 is “11:00”, each client time is used as it is as the printing time. When the print log is transferred, the time management server 4 corrects the execution status (time) of the print job due to the shift in the print time due to the shift in the client time even if the print log is collected and accumulated. It becomes impossible to manage.
Therefore, in this peripheral device management system 1, the print log is transferred to the time management server 4 after correcting the print time as follows.
[0013]
That is, in the case of the first client 2, the calculated time correction data is “−1: 00”, so that “1:00” is added to its own client time (9:00) and the printing time is set to “10”. : 00 ". On the other hand, since the time correction data of the second client 3 is “+10: 00”, “1:00” is subtracted from its own client time (11:00), and the printing time is set to “10:00”. To do. These mean that the print time is corrected to the server time using the time correction data. By this correction, the first and second clients 2 and 3 adopt the server time of the time management server 4 serving as a reference in the system as the printing time.
In step 7, the first and second clients 2 and 3 wait for an ACK from the time management server 4 for transferring the print log to the time management server 4. move on. In step 8, the server time is acquired from the ACK of the time management server 4. Further, the first and second clients 2 and 3 calculate time correction data again from the client time and the server time acquired at step 8 in the subsequent step 9, and thereby the time is calculated using the latest server time. Update correction data. The process is completed as described above.
As described above, in the peripheral device management system 1, since the client corrects the client time using the server time of the time management server as a reference, there are a plurality of clients, and even if there is a difference in each client time, The time order of the print log can be correctly grasped and unifiedly managed at a unified time without being influenced by the time difference between the clients.
[0014]
However, when acquiring the server time from the time management server 4, the time management server 4 has been changed for some reason, such as the network address (for example, IP address) of the time management server 4 has changed or the time management server 4 has gone down. It may be assumed that the server time cannot be acquired from the server 4. In that case, the first and second clients 2 and 3 operate the CPU as means for determining whether or not the server time can be acquired, and when it is determined that the CPU cannot acquire the server time, the CPU again operates after a predetermined time has elapsed. It is preferable to acquire the server time from the time management server 4, create time correction data using the acquired server time, correct the printing time, and retransfer the print log to the time management server 4.
For example, in the system configuration shown in FIG. 1, it is assumed that the client time of the first client 2 when a print job is issued is “11:00” and the server time of the time management server 4 is “12:00”. Then, the CPU 2a of the first client 2 tries to retransfer the print log after a certain time elapses, for example, 15 minutes elapses when the server time cannot be acquired. However, since the server time cannot be acquired and the time correction data has not been calculated, the client time “11:00” of the first client 2 is held as the print time of the print log. Therefore, the CPU 2a of the first client 2 executes the server time acquisition again from the time management server 4 immediately before performing the retransfer, and calculates time correction data using the acquired server time. For example, when 15 minutes have elapsed, the client time of the first client 2 when performing this re-transfer is “11:15”, and the server time of the time management server 4 is “12:15”. The correction data is calculated as “−1: 00”. Therefore, by using the time correction data “−10: 00”, the printing time becomes “12:00” by correcting “+10: 00” to the client time “11:00”. It matches the server time “12:00” of the server 4.
[0015]
In addition, the first and second clients 2 and 3 may be unable to transfer the print log due to an error in data communication via the network 7 for some reason. In this case, the CPU is operated as a means for determining whether or not the print log can be transferred. When the CPU determines that the print log cannot be transferred, the transfer of the print log is temporarily suspended and the next print log is transferred. When the server time is acquired again from the time management server 4 immediately before, the time correction data is calculated again from each client time using the acquired server time, and the time correction data is updated using the latest server time. Good.
Further, the first and second clients 2 and 3 operate the CPU as means for determining whether or not the client time after the time correction data is calculated, and the CPU determines that the client time has been changed after the time correction data is calculated. At that time, for the first (most recent) print log thereafter, the print time may be corrected using the time correction data calculated before the change of the client time, and the corrected print log may be transferred to the time management server 4. it can.
As described above, the accuracy and consistency of the printing time can be more accurately maintained. As a result, even if there are a plurality of clients such as the first and second clients 2 and 3, and the client time held by each of them is misaligned, the printing time order and the printing status can be correctly grasped. Is possible.
[0016]
【The invention's effect】
As described above, according to the present invention, it is possible to correctly grasp and centrally manage job execution times at a unified time without being affected by a time difference measured by the client.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram of a peripheral device management system according to the present invention.
FIG. 2 is a block diagram showing an internal configuration of a first client.
FIG. 3 is a flowchart illustrating a procedure of correction processing for printing time.
[Explanation of symbols]
1: Peripheral device management system 2: First client 2a: CPU
2b: ROM 3: second client 4: time management server 5: first peripheral device 6: second peripheral device 7: network

Claims (4)

A client having means for generating job record information representing job execution records including job execution time and a transfer means for transferring the job record information to the outside, and storing the job record information transferred from the client A peripheral device management system for managing a job execution status in a peripheral device with a server having means for
Time correction data calculating means for calculating time correction data representing a difference between a client time measured by the client and a server time measured by the server;
Using the time correction data calculated by said means, set a correction means for correcting the execution time included in the job record information to the server time,
The time correction data calculating means determines whether or not the time correction data has been calculated, and if it is determined that the time correction data has not been calculated by the means, the server time is calculated from the server. Means for obtaining and calculating and holding the time correction data; and after transferring the job record information by the transfer means, acquiring the server time from the server and updating the held time correction data. peripheral management system characterized by comprising a means for. The peripheral device management system according to claim 1,
Means for determining whether the server time can be acquired from the server;
When the means determines that the server time could not be acquired, the time correction data calculating means uses the server time acquired from the server immediately before transferring the next job record information from the client. Peripheral device management system characterized by calculating data. The peripheral device management system according to claim 1,
Means for determining whether or not the job record information can be transferred by the transfer means;
When the means determines that transfer is not possible, the time correction data calculation means acquires the server time from the server immediately before transferring the next job record information, and updates the time correction data. Peripheral device management system. The peripheral device management system according to claim 1,
Means for determining whether or not to change the client time after calculating the time correction data;
When the means determines that there is a change, the correction means corrects the execution time using the time correction data calculated before the change of the client time for the most recent job recording information, and the transfer means The peripheral device management system, wherein the job record information after the correction is transferred.

Images