JP2009237841A - Output data management device, data output device, output data management system, output data management method, and its program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage output data for output to a predetermined data output device while flexibly reflecting a user's output feasibility. <P>SOLUTION: A printer PRT 1 monitors operations from which user printing feasibility can be estimated, while associating the operations with user names authenticated by an authentication mechanism 57; when predetermined notification requirements are met, a history of the operations is sent to a server SV as operation information as it is associated with the user names. The server SV retains print jobs in a job storage area 71 and manages information such as related user names or the like in a job information table 72. Upon receiving the operation information, the server SV records and/or updates its content in an operation information table 73. When the content of operations in the operation information table 73 meets job deletion requirements, the server SV deletes from the job storage area 71 any print job for which the operations meeting the deletion requirements match user names. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technique for managing output data output by a predetermined data output device.

  In the authenticated printing system, when a user issues a print command on a client such as a personal computer, a print job is temporarily spooled on a server connected to the client via a network. When the user moves to the installation location of the printer connected to the server via the network, authenticates with an authentication device attached to the printer, and performs a print execution operation, the printer receives a print job from the server. Printing is executed.

  In such a system, if printing is not executed even though a print command is issued at the client, the server holds the print job indefinitely. When such print jobs accumulate, Since the storage capacity is finite, a new print job cannot be held in the end. Such a problem is not limited to the authentication printing system, but is a problem common to various management systems that hold and manage output data. For such a problem, various techniques for managing output data have been developed.

  For example, Patent Document 1 below discloses a technique in a print system in which a client transmits print job retention time limit information together with a print job to a server, and the server deletes a print job whose retention time limit has expired. In addition, a technique is disclosed in which a user can change the retention period by providing a deletion grace period so that the server does not delete print jobs excessively.

  Patent Document 2 below discloses a technique in which a large amount of image data is stored in an image forming apparatus, an upper limit is set such as the number of times the stored image data is read, and image data that reaches the upper limit is deleted. .

JP 2006-127429 A JP 2004-122657 A

  However, the technique of Patent Document 1 merely deletes a print job that is unlikely to be printed based on a holding period designated in advance, and flexibly increases the possibility that the user executes printing. It was not possible to manage the retention of print jobs. Further, the user can extend the holding period of the print job by manual operation, but such operation is troublesome and burdens the user.

  Further, in the technique of Patent Document 2, since it is determined whether or not to delete image data based only on the operation performed on the accumulated image data, the user has an opportunity to operate the image forming apparatus. However, it is impossible to reflect the circumstances such as not accessing the predetermined image data, and it is not possible to manage the retention of image data by flexibly reflecting the possibility that the user will perform printing. It was.

  Based on the above-described problems, the problem to be solved by the present invention is to manage output data to be output to a predetermined data output device while flexibly reflecting the output feasibility of the user.

  SUMMARY An advantage of some aspects of the invention is to solve at least a part of the problems described above, and the invention can be implemented as the following forms or application examples.

Application Example 1 An output data management device that manages output data output by a predetermined data output device,
Storage means for holding the output data;
Acquisition means for receiving, from the data output device, operation information that is information relating to an operation history of the data output device;
An output data management device comprising: a changing unit that changes handling related to holding of output data that is not output in the data output device among the held output data based on the received operation information.

  The output data management apparatus having such a configuration receives the operation information of the data output apparatus, and changes the handling of the output data not yet output based on the operation information. Therefore, the possibility of output execution by the user can be changed as the handling of output unexecuted data can be changed according to the possibility that output data that has not been output is output in the future, which is assumed from the operation history of the data output device. The output data can be managed flexibly. In addition, it is possible to improve the usability of the capacity of the storage means that is finite, reflecting the possibility of user output execution flexibly. Here, “change the handling regarding holding” is a concept including deferring the handling depending on the contents of the operation information.

Application Example 2 The output data management device according to Application Example 1, wherein the operation information is a history of authentication performed in an authentication device associated with the data output device.

  In the output data management apparatus having such a configuration, if the operation information is an authentication history for the data output apparatus, the opportunity for performing the authentication for the data output apparatus can be regarded as an opportunity to output the output data. Therefore, it is possible to guess the user's output execution possibility based on the history, and to manage the output data flexibly.

[Application Example 3] The output data management apparatus according to Application Example 1 or Application Example 2, wherein the operation information is stored in the data output apparatus even though the first output data held by the storage means is output. , Different from the first output data, is a history indicating that the second output data held by the storage means is not output, and the changing means is configured to change the second output data based on the operation information. An output data management device that changes the handling of retention.

  In the output data management apparatus having such a configuration, if the operation information is a history indicating that the second output data has not been output even though the first output data has been output, The opportunity to output the output data can be considered as an opportunity to output the second output data, so the history of the output can be estimated by the user, and flexible output data management Can be done.

[Application Example 4] The output data management device according to any one of Application Example 1 to Application Example 3, wherein the operation information is an instruction to delete the first output data held by the storage means in the data output device. This is a history indicating that the deletion instruction of the second output data held by the storage means, which is different from the first output data, has not been received, but the change means is based on the operation information. An output data management device that changes the handling of the second output data.

  In the output data management apparatus configured as described above, the operation information is a history indicating that the instruction to delete the first output data is received but the instruction to delete the second output data is not received. For example, since the opportunity to instruct the deletion of the first output data can be regarded as an opportunity to instruct the deletion of the second output data, the possibility of the user's output execution can be estimated from the history. Flexible output data management.

Application Example 5 The output data management apparatus according to any one of Application Example 1 to Application Example 3, in which the change in handling related to holding is to delete or save the output data held by the storage unit.

  The output data management apparatus having such a configuration can delete the held output data when it is estimated that the user's output execution possibility is low based on the operation information. Therefore, it is possible to manage output data by flexibly reflecting the user's output feasibility and improving the availability of a limited storage means capacity.

[Application Example 6] The output data management apparatus according to any one of Application Example 1 to Application Example 5, wherein the change of the handling related to the holding is to change a predetermined holding period of the output data held by the storage unit.

  The output data management apparatus having such a configuration can shorten the retention period of the output data when it is estimated that the user's output execution possibility is small based on the operation information. When it is estimated that the output data is large, the output data holding period can be extended. Therefore, it is possible to manage output data by flexibly reflecting the user's output feasibility and improving the availability of a limited storage means capacity.

Application Example 7 The output data management apparatus according to any one of Application Example 1 to Application Example 6, in which the change of the handling related to holding is to change the data format of the output data held by the storage unit.

  The output data management apparatus having such a configuration holds the format of the output data in a format in which the data capacity is small when it is estimated that the user's output execution possibility is small based on the operation information. Can be held in a format that increases the data capacity. Therefore, it is possible to manage output data by flexibly reflecting the user's output feasibility and improving the availability of a limited storage means capacity. The format in which the data capacity is reduced and the format in which the data capacity is increased may be a combination of data formats having relatively different data capacities, such as a compressed format and a non-compressed format, or an irreversible compression format and a lossless compression format.

[Application Example 8] The output data management apparatus according to any one of Application Example 1 to Application Example 7, in which the changing unit changes the received operation information when a predetermined condition is satisfied.

  Since the output data management device having such a configuration changes the handling of holding the output data when the received operation information satisfies a predetermined condition, the output data according to the content and degree of the history of the data output device It is possible to change the handling related to retention of data, and to perform flexible management of output data.

[Application Example 9] The output data management according to any one of Application Example 1 to Application Example 8 in which the changing unit performs a change when the ability to hold new output data in the storage unit has reached a predetermined state. apparatus.

  The output data management apparatus having such a configuration changes the handling for holding output data when the ability to hold new output data in the storage unit reaches a predetermined state. Therefore, for example, when the ability to hold new output data is small, the handling can be changed to holding that can reduce the total capacity of the output data to be held (for example, shortening the holding period of output data), or a new When the capacity to hold the output data is large, the output data is changed such that the total capacity of the output data to be held can be increased (for example, the holding period of the output data is extended). Can be managed flexibly.

[Application Example 10] The output data management apparatus according to any one of Application Example 1 to Application Example 9, wherein the changing unit changes the content or degree of the change according to the ability to hold new output data in the storage unit.

  The output data management apparatus having such a configuration changes the content or degree of change in accordance with the ability to store new output data in the storage means. Therefore, for example, when the ability to hold the output data is small, the content or level of the change is such that the total capacity of the output data to be held can be reduced (for example, the reduction time of the output data holding period is lower than usual) When the ability to hold output data is large, the content or extent of the change may be such that the total capacity of the output data to be held may be increased (for example, extending the holding period of the output data) It is possible to perform flexible management of output data, such as making the time longer than usual.

[Application Example 11] The output data management apparatus according to any one of Application Example 1 to Application Example 10, wherein the storage means sets the output data to the attribute of the first user who is a user related to the output data. The operation history is a history associated with the attribute of the second user who is the user who operated the data output device, and the changing means is the second user associated with the received operation information. An output data management apparatus that changes the handling of holding output data associated with an attribute of a first user corresponding to an attribute.

  Since the output data management apparatus having such a configuration changes the handling of the output data associated with the second user attribute corresponding to the first user attribute associated with the operation information, a plurality of users can Even when the data output device is used, only the operation history of the data output device related to the predetermined user can be reflected to change the handling of the output data related to the user. In addition, when there are a plurality of data output devices, regardless of which data output device is operated by the user, the handling of the output data related to the user can be changed to reflect the operation history. . Note that one or both of the first user and the second user may be a group.

Application Example 12 In the output data management device according to any one of Application Example 1 to Application Example 11, the operation history is a history associated with the attribute of the user who operated the data output device, and the changing unit includes An output data management apparatus that changes the content or degree of change according to the user attribute associated with the received operation information.

  The output data management apparatus having such a configuration changes the content or degree of change according to the user attribute associated with the operation information. Therefore, flexible management of output data can be performed according to user attributes. The user may be a group.

Application Example 13 A data output device that receives output data from the output data management device and outputs the output data, operation grasping means for grasping a predetermined operation related to the data output device, and grasped operation history A data output device comprising: providing means for providing the operation information as described above to the data management device.

  Since the data output device having such a configuration provides the data management device with operation information that is a history of a predetermined operation related to the data output device, the data management device can flexibly manage output data based on the operation information. It can be carried out.

Application Example 14 In the data output device according to Application Example 13, whether the state of the data output device when a predetermined operation is performed is a state in which the data output device can output predetermined data A data output apparatus comprising: a determination means for determining whether or not, wherein the providing means provides the data management apparatus with operation information including only a history of the operation of the data output apparatus performed in an outputable state.

  The data output apparatus having such a configuration provides the data management apparatus with operation information including only an operation history performed in a state where the data output apparatus can output. Therefore, since the data management device can estimate the user's output execution possibility only from the operation history in the state that the data output device can output, the data output device is not helpful in estimating the user's output execution possibility. Compared to a case where an operation history in a state where output is not possible is included, the accuracy of the user's estimation of output feasibility can be increased.

  In addition to the configuration as an output data management device and a data output device, the present invention can also be used as an output data management system, an output data management method, a computer program, a storage medium, etc. provided with an output data management device and a data output device. Can be realized.

Examples of the present invention will be described.
A. First embodiment:
A-1. Output data management system configuration:
A configuration of an output data management system 20 as an embodiment of the present invention is shown in FIG. The output data management system 20 is configured by connecting a computer PC, a server SV, and printers PRT1 and PRT2 to a local area network LAN. In this embodiment, the computer PC, the server SV, and the printers PRT1 and PRT2 are connected by a local area network LAN. However, these may be connected by a communicable communication means such as the Internet. The server SV and the printers PRT1, PRT2 may be locally connected by a USB cable or the like.

  The output data management system 20 is a so-called authenticated printing system, and its outline is as follows. The computer PC is a general-purpose personal computer, and the server SV is a print server that spools print jobs. The printers PRT1 and PRT2 are printers with an authentication function. When the user issues a print instruction using the PC, the PC transmits the print job to the server SV in association with the user of the computer PC. When the server SV receives a print job from the computer PC, the server SV temporarily spools the print job. When the user moves to a desired printer, for example, the installation site of the printer PRT1, and authenticates with an authentication device associated with the printer PRT1, the printer PRT1 prints a print job associated with the authenticated user. Is received from the server SV and printing is executed.

A-2. Printer configuration:
A schematic configuration of the printer PRT1 is shown in FIG. The printer PRT1 is a so-called multifunction printer. As shown in the figure, the printer PRT1 includes a CPU 30, an EEPROM 40, a ROM 51, a RAM 52, an input mechanism 53, a printing mechanism 54, a scanner 55, a FAX transmission mechanism 56, an authentication mechanism 57, and an interface 58, which are connected by a bus. ing. The printer PRT2 has the same configuration as the printer PRT1, and a description thereof will be omitted.

  The CPU 30 manages the entire printer PRT1 by developing the firmware and OS stored in the EEPROM 40 and the ROM 51 in the RAM 52 and executing them. The CPU 30 functions as an operation grasping unit 31, an operation determining unit 32, and an information providing unit 33 by executing a program stored in the EEPROM 40. Details of this functional unit will be described later.

  The EEPROM 40 is a writable nonvolatile memory, and an operation history storage area 42 for storing a history of a predetermined operation of the printer PRT1 is secured. The printing mechanism 54 is a laser type printing mechanism in this embodiment. The input mechanism 56 includes a keyboard and a display for displaying a UI. By operating the UI, the state of the PRT 1 is changed to “print mode” for executing printing, “copy mode” for executing copying, and image scanning. “Scan mode” and “FAX mode” for performing FAX transmission can be selected. In the “print mode”, a print job list, which is a list indicating print jobs spooled in the server SV, is received from the server SV and displayed on the display. Among the displayed print jobs, a desired print job is displayed. An operation for an instruction to execute printing or an instruction to delete a desired print job from the server SV is possible.

  The authentication mechanism 57 is an IC card type authentication device. The user can log in the printer PRT1 by reading the authentication information of the IC chip into the authentication mechanism 57. Note that the authentication method is not limited to the IC card method, and may be another method such as a password method or a biometric method. The interface 58 is an interface for connecting the printer PRT1 to the local area network LAN. The printer PRT1 is connected to the local area network LAN via the interface 58.

A-3. Server configuration:
A schematic configuration of the server SV is shown in FIG. The server SV includes a CPU 60, a hard disk drive 70, a ROM 81, a RAM 82, and an interface 88, which are connected by a bus.

  The CPU 60 manages the entire server SV by deploying and executing firmware and OS stored in the hard disk drive 70 and the ROM 81 in the RAM 82. Further, the CPU 60 functions as a storage unit 61, an acquisition unit 62, and a change unit 63 by executing a program stored in the hard disk drive 70. Details of this functional unit will be described later.

  The hard disk drive 70 stores the above-described OS and program, and a job storage area 71 for spooling a print job received from the computer PC. The hard disk drive 70 also stores a job information table 72, an operation information table 73, and a change condition table 74. Details of these will be described later.

  The interface 88 is an interface for connecting to the local area network LAN, and the server SV is connected to the local area network LAN via the interface 88.

A-4. Print job management processing:
The print job management process in the output data management system 20 will be described with reference to FIG. In this embodiment, the print job management process is a process in which the server SV receives a print job from the computer PC, spools it, receives information about the operation history of the printer PRT1 from the printer PRT1 at a predetermined timing, and based on the information. This is a process for deleting a spooled print job, which is unlikely to be printed in the future. A similar process is performed between the server SV and the printer PRT2, but the description thereof is omitted.

  In the printer PRT1, when this process is started by the user authenticating using the authentication mechanism 57, first, in the printer PRT1, the CPU 30 sets a predetermined process for the printer PRT1 as the process of the operation grasping unit 31. The predetermined operation is monitored, and the result is stored in the operation history storage area 42 as operation information indicating the operation history of the printer PRT1 in association with the logged-in user name (step S110). In this embodiment, the operation information is associated with the logged-in user name, but it is not necessarily associated with the user name.

  As the predetermined operation monitored here, for example, “login”, “automatic logout (occurred when a predetermined period of time during which no operation is performed after login)”, which is the operation shown in the second column of FIG. “Login accumulated time”, “idle accumulated time”, “print mode shift”, and “execution of printing” can be set as “a print job that has not been printed in the received print job list”. These operations are associated with notification IDs “0” to “5” shown in the first column of FIG. The operation set here is an operation that can be estimated that the print job spooled by the server SV is unlikely to be printed in the future. For example, if a predetermined user frequently logs in to the printer PRT1 or operates in the “print mode” but a predetermined print job is not executed, the user In the future, it can be estimated that the possibility of printing an unprinted print job is low. Note that the predetermined operation shown in FIG. 5 is merely an example, and it may be an operation that can be inferred that the possibility of printing is small. For example, when the printer PRT1 can detect that the user is approaching by RFID (Radio Frequency IDentification), the detection may be a predetermined operation.

  Then, the CPU 30 determines whether or not a predetermined notification condition is satisfied (step S120). As the notification condition here, for example, as shown in the third column of FIG. 5, “whether logged in”, “logged out”, “whether a predetermined event occurred”, or “predetermined time is constant. For example, has time passed?

  In this embodiment, for the operation “login”, the notification condition “logged in”, for the operation “automatic logout”, the notification condition “logged out”, and for the operation “accumulated login time”, the notification condition “predetermined” For a certain period of time (here, login accumulated time) ", for operation" idle accumulated time ", for notification condition" predetermined time (here, accumulated idle time), a certain time has elapsed ”, Operation“ print mode shift ”, notification condition“ predetermined event (print mode shift in this case) has occurred ”, operation“ print job that has not been printed out of received print job list ” For “Yes”, the notification condition “whether you have logged out” is used as the notification condition. Note that the combination of the above-described operation and the notification condition is an example, and various combinations may be set as appropriate. In addition, the notification condition is not limited to this example, and various conditions such as “whether a predetermined event has occurred a predetermined number of times”, “whether a predetermined time has passed since the previous notification condition was satisfied” or the like can be set as appropriate. Good.

  As a result of the determination of the predetermined notification condition, when the notification condition is satisfied (step S120: YES), the CPU 30 uses the operation information stored in the operation history storage area 42 as a process of the information providing unit 33 as a server. It transmits to SV (step S130). Here, the content of the operation information to be transmitted is a notification ID indicating the content of the operation. Depending on the content of the operation, a user name associated with the operation or information indicating the details of the operation (such as the number of operations) is included. Added. Also, other information such as the model name of the printer PRT1 and the operation occurrence time may be added.

  Specifically, for example, as shown in the fourth column of FIG. 5, if the operation information to be transmitted relates to the operation of the notification ID “0” or the notification ID “1”, the notification ID, the user name, can do. In addition to the notification ID and the user name, the cumulative time of the operation can be used as long as it relates to the operation of the notification ID “2” or the notification ID “3”. In addition to the notification ID and the user name, the number of operations of the operation can be set as long as it relates to the operation of the notification ID “4”. If the operation is related to the operation of the notification ID “5”, the notification ID, the job ID corresponding to the print job that has not been printed, and the number of operations of the operation can be used.

  If the operation information stored in the operation history storage area 42 is not associated with the user name, the transmitted operation information may not include the user name.

  Further, the operation information transmitted in step S130 may include one type of operation history or may include a plurality of types of operation history. For example, in the example of FIG. 5, when the operation information is transmitted by the user login, the operation information including the notification ID “0” and the corresponding user name is transmitted. In the case of transmitting information, operation information including a notification ID “1”, a notification ID “5”, and a user name corresponding to the notification ID “1” is transmitted.

  On the other hand, if the notification condition is not satisfied (step S120: NO), the CPU 30 returns the process to step S110 and continues monitoring the operation of the printer PRT1.

  On the other hand, in the server SV, when a print job is received from the computer PC, the CPU 60 stores the print job in the job storage area 71 as processing of the storage unit 61 and stores various information related to the print job in the job information table 72. Stores and manages print jobs (not shown). In the present embodiment, information relating to a print job stored in the job information table 72 includes a job ID that is an identification number of the print job, a transmission user name of the print job, and a printer model name (output destination is specified). Print job reception time and file path.

  When the print job is received and the print job management process is started, the CPU 60 determines whether or not operation information has been received from the printer PRT1 as a process of the acquisition unit 62 (step S210). As a result, if not received (step S210: NO), the CPU 60 waits for reception and receives operation information (step S210: YES). Based on the received operation information, the corresponding operation information table 73 is obtained. Record and update information in

  The operation information table 73 is a table that records a history of operations of printers (here, printers PRT1 and PRT2) on the local area network LAN where the server SV can spool print jobs. In the present embodiment, information recorded in the operation information table 73 includes an event ID that is an identification number of the operation information, a job ID, a notification ID, and other information (operation count, time, etc.) corresponding to the received operation information. did.

  Specifically, in step S210, for example, a print job managed as a job ID “P1” and a user name “A” is stored in the job storage area 71 in the job information table 72 and stored in the operation information table 73. When the operation number of the notification ID “0” associated with the job ID “P1” is recorded as “1”, the operation information of the notification ID “0” and the user name “A” is newly received. The CPU 60 matches the notification ID “0” and changes the number of operations related to the job ID “P1” associated with the user name “A” included in the operation information from “1” to “2”. It will be updated.

  In this embodiment, as described above, the information in the job information table 72 is updated for the print job associated with the user name included in the received operation information. With this configuration, when a plurality of authentication printers are installed on the LAN, regardless of which of the plurality of authentication printers is operated by the user, the operation is performed by printing a print job spooled in the server SV. Since it can be reflected as an operation of estimating that the execution is not performed, the accuracy of the estimation can be increased. Further, even when a plurality of users use the printer PRT1, only the operation history of the printer PRT1 related to the predetermined user can be reflected as an operation for estimating that the print job is not executed. The accuracy of estimation can be increased.

  However, the update of the information in the job information table 72 is not limited to such a configuration, and various configurations can be employed. For example, if the operation information transmitted from the printer PRT1 includes a user name and a model name, the information may be updated for a print job in which both match. In this way, for example, a print job for color printing is not deleted based on an operation history in a printer that supports only monochrome printing, so the accuracy of estimating that the print job will not be executed can be increased. Can be increased. Alternatively, when the operation information transmitted from the printer PRT1 includes the user name and the printer name, and the job information table 72 also manages the name of the printer to be printed, both of them are stored. The information may be updated for the matching print job.

  Conversely, the information may be updated for all print jobs having the same user name regardless of the model name or printer name. By doing so, it is effective when the possibility that a predetermined user executes printing is small for all print jobs.

  When the operation information table 73 is recorded / updated, the CPU 60 determines whether the recorded / updated information satisfies the deletion condition of the spooled print job (step S230). The determination criteria here are predetermined, and the contents are recorded in the change condition table 74.

  A specific example of the change condition table 74 is shown in FIG. As illustrated, the change condition table 74 stores a condition for deleting a print job in association with each notification ID that may be included in the operation information transmitted by the printer PRT1. For example, the deletion condition corresponding to the notification ID “0” is “10 times”, the operation information including the notification ID “0” associated with the predetermined user name is received 10 times, and the notification ID of the operation information table 73 is received. When the number of operations of “0” is “10”, the CPU 60 determines in step S230 that the deletion condition is satisfied.

  As a result, if the deletion condition is satisfied (step S230: YES), the CPU 60 deletes the print job corresponding to the job ID that satisfies the deletion condition from the job storage area 71 as a process of the changing unit 63. Information corresponding to the print job is deleted from the job information table 72 and the operation information table 73 (step S240), and the processing is returned to the original. On the other hand, if the deletion condition is not satisfied (step S230: NO), the CPU 60 returns the process to step S210.

  Such a print job management process will be described with reference to FIG. 7 with a specific example including the preceding stage of the print job management process. In this example, the printer PRT1 monitors the operation “There is a print job that has not been printed in the received print job list” among the operations shown in FIG. 5 (corresponding to step S110). The notification condition in step S120 is set to “logged out”. In addition, in the change condition table 74 illustrated in FIG. 6, the deletion condition “twice” is recorded for the notification ID “5”.

  As shown in the drawing, when the user A issues a print execution instruction for the print job P1 on the computer PC, the computer PC transmits the print job P1 to the server SV (step S311). In response to this, the server SV saves the print job P1 in the job storage area 71 and also saves information on the print job P1 transmitted from the computer PC in the job information table 72 (step S321). Similarly, when the computer PC transmits the print job P2 (step S312), the server SV stores the print job P2 and the like (step S322).

  At this time, the job information table 72 stores information about the print job P1 and the print job P2, as shown in FIG. At this time, since the server SV has not yet received the operation information from the printer PRT1, there is no information stored in the operation information table 73 as shown in FIG.

  When the user A moves to the printer PRT1 to execute printing and authenticates using the authentication mechanism 57, the printer PRT1 transmits a print job list request including the user name (user A) to the server SV. (Step S342). In response to this, the server SV refers to the job information table 72, creates a print job list for the print job P1 and the print job P2 associated with the user A, and transmits the print job list to the printer PRT1 (step S323).

  On the other hand, since the printer PRT1 displays the received print job list on the display of the printing mechanism 54, the user A operates the printing mechanism 54 to instruct the printing execution of the printing job P1. The printer PRT1 receives this instruction (step S342), and requests the server SV to transmit the print job P1 (step S343). In response to this, the server SV transmits the print job P1 to the printer PRT1 (step S324).

  The printer PRT1 receives the print job P1, executes printing (step S344), and transmits a print completion notification of the print job P1 to the server SV (step S345). Upon receiving the print completion notification for the print job P1, the server SV deletes the corresponding print job P1 from the job storage area 71 and deletes the information corresponding to the print job P1 from the job information table 72 (step S325). ).

  Here, the printer PRT1 performs the print job management process shown in FIG. 4 (step S346). The contents of the processing here are as follows. If the printer PRT1 detects the operation “There is a print job that has not been printed in the received print job list” in step S110, and determines that the notification condition “logged out” is satisfied in step S120, the printer PRT1 performs step In 130, the operation information is transmitted to the server SV (step S347). This operation information includes a notification ID “5” associated with the operation “There is a print job that has not been printed in the received print job list”, and a print job that indicates a print job that has not been printed. The ID “P2” is included. Here, the operation information does not include the number of operations, but if the notification condition is “whether the predetermined time has passed” or the like, the operation may have occurred a plurality of times. The number of operations is also included.

  On the other hand, the server SV performs the print job management process shown in FIG. 4 (step S326), and the following process is performed. Upon receiving the operation information, the server SV records / updates the operation information table 73 based on the received operation information in step S220 of FIG. The information in the job information table 72 and the operation information table 73 here is as shown in FIG. Since the information corresponding to the print job P1 is deleted from the job information table 72 in step S325, only the information corresponding to the print job P2 is stored in the job information table 72. In addition, the event information “E1” is issued in the operation information table 73, and the contents of the received operation information are stored in association with the event ID “E1”. In this example, since the operation information does not include the number of operations, “1” corresponding to the number of received operation information is recorded as the “number of operations”.

  In this embodiment, the CPU 60 of the server SV interprets that printing of the print job P2 has not been executed because the print job ID “P2” is included in the operation information transmitted by the printer PRT1. However, the printer PRT1 transmits the operation information without including the print job ID, and the server SV transmits the print job list among the print jobs described in the transmitted print job list, and then the operation information. A configuration may be adopted in which a print job that has not been printed is interpreted by determining whether or not there is a print job that has not been transmitted during the period until the message is received.

  In step S230, the server SV determines whether or not the deletion condition is satisfied. Here, since the number of operations recorded in the operation information table 73 is “1” and the deletion condition “2” is not satisfied, the process returns to step S210, that is, the print job P2 is held. Become.

  Further, when the user A returns to the computer PC and issues a print instruction for the print job P3, and the computer PC transmits the print job P3 (step S313), the server SV stores the print job P3 and the like (step S327). At this time, the job information table 72 stores information on the print job P2 and the print job P3 as shown in FIG. The operation information table 73 records the same information as in FIG.

  When the user A authenticates with the printer PRT1, the printer PRT1 transmits a print job list request including the user name (user A) to the server SV (step S348). In response to this, the server SV creates a print job list for the print job P2 and the print job P3, and transmits it to the printer PRT1 (step S328).

  On the other hand, the printer PRT1 receives a print execution instruction for the print job P3 by the operation of the user A (step S349), and requests the server SV to transmit the print job P3 (step S350). In response to this, the server SV transmits the print job P3 to the printer PRT1 (step S329).

  The printer PRT1 receives the print job P3, executes printing (step S351), and transmits a print completion notification of the print job P3 to the server SV (step S352). The server SV deletes the corresponding print job P3 from the job storage area 71 and deletes the information corresponding to the print job P3 from the job information table 72 (step S325).

  Here, the printer PRT1 performs the print job management process shown in FIG. 4 (step S353). The processing here is the same as in step S353 described above, and the printer PRT1 transmits operation information including the notification ID “5” and the print job ID “P2” to the server SV (step S354).

  On the other hand, the server SV performs the print job management process shown in FIG. 4 (step S331), and the following processes are performed. Upon receiving the operation information, the server SV records / updates the operation information table 73 based on the received operation information in step S220 of FIG. The information in the job information table 72 and the operation information table 73 here is as shown in FIG. The job information table 72 stores information corresponding to the print jobs P2 and P3. In the operation information table 73, the number of operations corresponding to the notification ID “5” and the print job ID “P2” included in the received operation information is updated from “1” to “2”.

  In step S230, the server SV determines whether or not the deletion condition is satisfied. Here, since the number of operations recorded in the operation information table 73 is “2” and the deletion condition “2” is satisfied, the server SV advances the process to step S240 and stores the print job P2 in the job storage. In addition to deleting from the area 71, information corresponding to the print job P <b> 2 is deleted from the job information table 72 and the operation information table 73.

  In the output data management system 20 having such a configuration, the printer PRT1 can estimate that there is a low possibility that printing of an unprinted print job will be executed. provide. On the other hand, the server SV receives the operation information from the printer PRT1, determines the possibility that an unprinted print job assumed from the operation history included in the operation information will be printed in the future, and may be printed. When the print job is smaller, the print job that has not been executed and is stored in the job storage area 71 is deleted. Therefore, it is possible to manage print jobs by flexibly reflecting the user's ability to execute printing and improving the availability of the limited capacity of the job storage area 71.

  In the output data management system 20 having such a configuration, the server SV deletes the held print job when the received operation information satisfies the conditions of the change condition table 74, so the printer PRT1 included in the operation information. The print job can be managed flexibly, reflecting the possibility of printing an unprinted print job that fluctuates depending on the type and number of operation histories.

B. Second embodiment:
In the first embodiment, in the print job management process shown in FIG. 4, the server SV deletes the print job held in the job storage area 71 based on the operation information received from the printer PRT1. However, the second embodiment shows a configuration for changing the retention period of the print job held in the job storage area 71 based on the operation information.

  In the server SV in the second embodiment, a holding period for holding a print job is determined, and a print job that has passed the holding period is deleted even if printing is not executed. Here, it is assumed that 6 hours is set as the retention period.

  FIG. 9 shows a flow of print job management processing as the second embodiment. The difference from the first embodiment shown in FIG. 4 is that, in the process of the server SV, the process of step S420 is performed instead of steps S220 to S240. The same reference numerals as in FIG. First, in step S110, the printer PRT1 monitors a predetermined operation as in the first embodiment. The operation monitored in this example is as shown in the second column of FIG. 10. In the operation shown in FIG. 5, in the operation of deleting a print job, “deletion of received print job list is not executed. There is an operation of “There is a print job” (corresponding to the notification ID 6).

  The operation set here is an operation that can be presumed that the print job spooled by the server SV is unlikely to be printed in the future or that the print job is likely to be executed. is there. For example, if a predetermined user performs a print job deletion operation on the printer PRT1 and the predetermined print job is not deleted, the user prints a print job that has not been printed in the future. The possibility is great.

  In the operation illustrated in FIG. 10, the operations of the notification IDs “0” to “5” are operations that can be presumed that printing is unlikely to be performed, as in the first embodiment. The operation of the notification ID “6” is an operation that can be estimated that printing is likely to be performed.

  Then, as in the first embodiment, the CPU 30 determines whether or not a predetermined notification condition is satisfied in step S120. Here, the notification conditions for the operations of the notification IDs “0” to “5” are the same as in the first embodiment, and for the operation of the notification ID “6”, the notification condition is set to “logged out”. ing.

  As a result of the determination of the predetermined notification condition, if the notification condition is satisfied (step S120: YES), the CPU 30 stores the operation information stored in the operation history storage area 42 as a server as in the first embodiment. It transmits to SV (step S130).

  The operation information transmitted here is information shown in the fourth column of FIG. Here, as for the operations related to the notification IDs “0” and “1”, the notification ID and the user name are used as in the first embodiment. Also, regarding the operations of the notification IDs “2” and “3”, “cumulative time” is omitted as compared with the first embodiment. Further, the operations related to the notification IDs “4” and “5” omit the “number of operations” compared to the first embodiment, and the notification ID “6” includes the notification ID and the job ID. As described above, the “cumulative time” and the “number of operations” are omitted in the second embodiment. In this case, the server SV does not include the period of the print job held in the job storage area 71 regardless of the information. It is because it is set as the structure which changes. Details thereof will be described later.

  On the other hand, when the server SV receives a print job from the computer PC, the CPU 60 stores the print job in the job storage area 71 as well as the print job held in the job storage area 71 as in the first embodiment. Corresponding information is stored in the job information table 72. However, in the second embodiment, no information is stored in the operation information table 73. A specific example of information stored in the job information table 72 is shown in FIG. In this example, in addition to the information in the job information table 72 shown in FIG. 8A as the first embodiment, the deletion time of the held print job is stored. As described above, since the print job holding period is 6 hours, for example, the deletion time of the print job P1 received at “12:00 on January 28, 2008” is “18:00 on January 28, 2008”. is there.

  If the operation information is received from the printer PRT1 (step S210: YES), the CPU 60 refers to the change condition table 74 in which the change time of the retention period is determined for each notification ID as the process of the change unit 63. For the print job corresponding to the received operation information, the holding period is changed by the change time set in the change condition table 74 (step S420), and the process is returned to the original. A specific example of the change condition table 74 is shown in FIG. In this example, for the notification IDs “0” to “5” corresponding to operations that can be estimated that printing is less likely to be performed, a shortened value of the retention period is defined. Further, for the notification ID “6” corresponding to the operation that can be estimated that printing is likely to be performed, an extension value of the retention period is set.

  For example, using the example shown in FIG. 11, when the CPU 60 receives operation information including the notification ID “1” and the user name “A” in step S420, the print corresponding to the user name “A” is performed. The holding periods of the jobs P1 and P2 are reduced by 0.5 hours, which is the change time corresponding to the notification ID “1”. That is, the deletion time of the print job P1 is changed to “January 28, 2008, 17:30”, and the deletion time of the print job P2 is changed to “January 28, 2008, 17:31”. When the operation information including the notification ID “6” and the job ID “P2” is received, the retention period of the print job P2 corresponding to the job ID “P2” is changed by the change time corresponding to the notification ID “6”. That is, it is extended by a certain 6 hours, that is, the deletion time of the print job P2 is changed to “January 29, 2008 00:01”.

  In the second embodiment, the CPU 60 of the server SV is configured to always change the retention period of the print job held in the corresponding job storage area 71 when the operation information is received. However, the present invention is not limited to such a configuration. For example, instead of the configuration in which the holding period is changed every time operation information is received, the holding period may be changed every time a predetermined notification ID is received a predetermined number of times. In such a case, in the change condition table 74, in addition to the reduction value or the extension value shown in FIG. As in the first embodiment, each time operation information is received, information in the operation information table 73 is recorded / updated, and each time the operation count of the operation information table 73 satisfies the change condition of the retention period of the change condition table 74, The holding period may be changed.

  In the second embodiment, the server SV is configured to shorten or extend the retention period of the print job according to the operation information received from the printer PRT1. It is good also as a structure which performs only.

  In the output data management system 20 having such a configuration, the printer PRT1 uses the operation history of the printer PRT1 that can be estimated that the possibility of printing is small or the possibility of printing is large as the operation information. Information to the server SV. On the other hand, when the server SV receives the operation information from the printer PRT1 and determines from the operation history included in the operation information that the print job that has not been printed is unlikely to be printed in the future, the server SV stores the operation information in the job storage area 71. The holding period of the print job that has not been printed is shortened, and when it is determined that there is a high possibility of printing, the holding period is extended. Therefore, it is possible to manage print jobs by flexibly reflecting the possibility of user output execution and improving the availability of the limited capacity of the job storage area 71.

C. Third embodiment:
The flow of the print job management process as the third embodiment is substantially the same as the print job management process as the first embodiment shown in FIG. The difference from the first embodiment is that the operation information transmitted from the printer PRT1 in step S130 is similar to the operation illustrated in FIG. And an operation that can be inferred that the possibility of being executed is high. In addition, when it is determined that the condition of the change condition table 74 is satisfied (step 230: YES), in step S240, instead of deleting the print job, the data format of the held print job is changed.

  Specifically, when the condition corresponding to the operation (in the example of FIG. 10, notification IDs “0” to “5” in the example of FIG. 10) that is estimated to be less likely to be printed by the user is satisfied in step S230. In step S240, the corresponding print job held in the job storage area 71 is reversibly compressed using a compression circuit included in the server SV, and is held in a compressed data format. The compression method is not particularly limited, and various known compression methods such as the LZ method, the ZIP method, and the CAB method can be used.

  On the other hand, in step S230, when the condition corresponding to the operation that the user is likely to perform printing (the operation of the notification ID “6” in the example of FIG. 10) is satisfied, the job is processed in step S240. When the corresponding print job held in the storage area 71 is held in the compressed data format, the print job is decompressed using the decompression circuit provided in the server SV and retained in the decompressed data method. To do.

  Even with such a configuration, print jobs can be managed by flexibly reflecting the user's ability to execute printing, improving the availability of the limited capacity of the job storage area 71. In this embodiment, the data format of the held print job is changed between the lossless compression format and the non-compression format. However, the data format to be changed is not limited to such a configuration. Any configuration that changes between data formats having relatively different data capacities may be used. For example, the structure which changes between a lossy compression format and a lossless compression format may be sufficient. In this embodiment, the print job is compressed or expanded, but only the compression may be performed.

D. Fourth embodiment:
The flow of the print job management process as the fourth embodiment is the same as the print job management process as the first embodiment shown in FIG. The difference from the first embodiment is that when it is determined that the condition of the change condition table 74 is satisfied (step 230: YES), in step S240, instead of deleting the print job, the held print job is transferred to another storage medium. Output from the job storage area 71. Here, the other storage medium may be an area other than the job storage area 71 in the hard disk drive 70, an external storage medium connected to the server SV, or another terminal connected on the local area network LAN. Or a storage medium of a server.

  When the CPU 60 receives from the printer PRT1 operation information related to an operation that can be estimated to have a high possibility of performing printing as exemplified in the operation of the notification ID “6” in FIG. The print job saved in the medium is read again, or the transmission request for the saved print job is sent to another terminal or server to acquire the print job again, and the saved print job is stored in the job storage area 71. You may return the job.

  Even with such a configuration, print jobs can be managed by flexibly reflecting the user's ability to execute printing, improving the availability of the limited capacity of the job storage area 71.

E. Variations:
A modification of the above-described embodiment will be described.
E-1. Modification 1:
In the embodiment, in the print job management process, the server SV is configured to perform a uniform process regardless of the state of the job storage area 71. However, the ability to hold a new print job in the job storage area 71 is predetermined. Only when the status is reached, the handling of the held print job may be changed.

  Specifically, in the first embodiment, the following configuration can be realized. When the CPU 60 of the server SV determines in step S230 that the conditions set in the change condition table 74 are satisfied, it further grasps the free capacity of the job storage area 71 and determines whether the free capacity is equal to or less than a predetermined value. Judging. As a result, only when the free space is equal to or less than a predetermined value (absolute value or ratio), the process proceeds to step S230, the corresponding print job is deleted, and when the free space is larger than the predetermined value, The process returns to step S210.

  Note that the determination to be added in step S230 is not limited to whether or not the free capacity of the job storage area 71 is less than or equal to a predetermined value, but may be whether or not the free capacity of the job storage area 71 is greater than or equal to a predetermined value. Good. For example, if there is a free space, processing such as extending the retention period of the print job can be performed. The “predetermined state” is not limited to the state specified by the absolute value or the ratio of the storage capacity. For example, the “predetermined state” is whether the number of print jobs held in the job storage area 71 is a predetermined number or more. May be.

  According to this configuration, print jobs can be managed more flexibly according to the ability to hold a new print job in the job storage area 71.

E-2. Modification 2:
The server SV may be configured to change the content and degree of change in the handling of the print job to be held according to the ability to hold a new print job in the job storage area 71. Specifically, the configuration for changing the content of the change in the handling of the held print job can be realized as the following configuration, for example. The hard disk drive 70 of the server SV has a change condition table 74a in which deletion conditions for print jobs are defined, a change condition table 74b in which conditions for shortening the retention period of print jobs are defined, and compression conditions for print jobs. The change condition table 74c is stored. Then, after updating the operation information table 73 in step S220, the CPU 60 grasps the free capacity of the job storage area 71. If the grasped free capacity is smaller than the predetermined value Th1 in step S230, the change condition With reference to the table 74a, if the condition is satisfied, the print job is deleted. If the grasped free capacity is between the predetermined values Th1 and Th2, the change condition table 74b is referred to, and when the condition is satisfied, the print job holding period is shortened. When the grasped free space is between the predetermined value Th2 and the predetermined value TH3, the print job is compressed when the conditions are satisfied with reference to the change condition table 74c. Then, if the grasped free capacity is larger than the predetermined value TH3, the handling regarding the holding of the print job is not changed even if the condition is satisfied. In other words, according to the margin of the job storage area 71, the handling for holding the print job is changed.

  Further, if the configuration for changing the degree of change in the handling of the print job to be held is the second embodiment, it can be realized as the following configuration, for example. The hard disk drive 70 of the server SV has a change condition table 74d in which the shortening time of the print job retention period corresponding to the case where the free capacity of the job storage area 71 is relatively large and the case where the free capacity is relatively small. A corresponding change condition table 74e in which the shortening time of the print job holding period is reduced is stored. Then, after updating the operation information table 73 in step S220, the CPU 60 grasps the free capacity of the job storage area 71, and in step S230, refers to the change condition table 74d or 74e corresponding to the grasped free capacity. It is determined whether or not the print job deletion condition is satisfied.

  Even with the above-described configuration, it is possible to more flexibly manage print jobs according to the ability to hold new print jobs in the job storage area 71.

E-3. Modification 3:
In the embodiment, the server SV is configured to manage the print job and the user name received together with the print job from the computer PC in the job information table 72 in association with each other. Further, in the operation information table 73, the server SV associates and manages the user name included together with the operation (notification ID) of the printer PRT1 depending on the type of notification ID included in the operation information received from the printer PRT1. It was set as the structure to do. When a predetermined operation stored in the operation information table 73 satisfies a predetermined condition, if the user name associated with the operation matches the user name associated with the print job, the print job The configuration is such that the handling of holding is changed.

  However, the user information managed in association with the print job or operation in the job information table 72 or the operation information table 73 is not limited to the user name, and any user attribute may be used. If there is a correspondence between the attribute of the user and the attribute of the user associated with the print job, the handling of the print job can be changed. For example, one or both of the user attributes associated with the operation and the print job may be used as the group name. In this case, the user attributes may be in correspondence with each other as long as both attributes match or are in an inclusive relationship. Even with such a configuration, print jobs can be managed more flexibly.

E-4. Modification 4:
In the second modification, the server SV is configured to change the content and degree of change in the handling of the print job to be held according to the ability to hold a new print job in the job storage area 71. Depending on the user attributes managed by the job information table 72 and the operation information table 73, the content or degree of change may be changed. In such a case, the change condition table 74 may be set for each user attribute. Even with such a configuration, print jobs can be managed more flexibly.

  Further, the server SV may change the content or degree of change according to the capacity of the print job held in the job storage area 71. In such a case, the change condition table 74 may be set for each stage of job capacity. Even with such a configuration, print jobs can be managed more flexibly.

E-5. Modification 5:
In the embodiment, when the history of a single operation (for example, the operation of the notification ID “5”) satisfies the condition of the change condition table 74, the handling for holding the print job is changed. A configuration may be adopted in which handling of a print job is changed when a plurality of operation histories are comprehensively determined and a predetermined condition is satisfied. For example, the server SV performs a predetermined weighting on a plurality of operation histories managed in the operation information table 73 to convert the score, and when the score reaches a predetermined value, the handling of the print job is changed. May be. In this way, it is possible to perform management that more accurately reflects the print execution possibility of a print job.

E-6. Modification 6:
In the embodiment, the printer PRT1 is configured to always record the operation in the operation history storage area 42 and transmit the contents as operation information to the server SV when a predetermined operation occurs. The operation history to be performed may be limited to that performed in a state where the printer PRT1 can print a predetermined print job. Specifically, for example, the CPU 30 of the printer PRT1 performs processing of the operation determination unit 32, and its own operation state is a state in which a predetermined print job can be printed, for example, the printer PRT1 is out of paper, out of toner, or cover open. It is determined whether it is in a state where it is not in an error state, or in a state where printing of a print job of a user different from the user who is going to execute printing is not being executed, and in a state where a predetermined print job can be printed. Only a history of a predetermined operation performed when it is determined to be present is recorded in the operation history storage area 42 in step S110 of FIG. 4, and based on this, operation information is transmitted in step S130. . With such a configuration, it is possible to improve the accuracy of estimation of the user's ability to execute printing, as compared with the case where the server SV manages print jobs, reflecting all operation histories.

E-7. Modification 7:
In the embodiment, the printer PRT1 that is a data output device and the server SV that is a data management device are installed separately, but may be installed together. For example, the printer PRT1 may have a server function.

E-8. Modification 8:
In the embodiment, the printer PRT1 uses the authentication mechanism 57 to grasp the attribute of the user who operates the printer PRT1, and includes this in the operation information. However, the user attribute is grasped by other methods. Also good. For example, the configuration may be such that the user who operates the printer PRT1 inputs his / her attributes using the input mechanism 56.

E-9. Modification 9:
In the embodiment, the server SV manages the operation history of the printers PRT1 and PRT2 using the operation information table 73. However, the printer PRT1 manages the operation history information, and performs a predetermined timing, for example, a deletion condition. When the above is satisfied, the operation information or the deletion instruction may be transmitted to the server SV.

E-10. Modification 10:
In the embodiment, a configuration in which only one server SV is connected on the local area network LAN has been described. However, a plurality of server SVs may be provided. In such a case, the printer PRT1 may be configured to transmit the same operation information to a plurality of servers SV. The server SV that transmits the operation information may be a plurality of predetermined SVs, or may be a server SV searched by SNMP (Simple Network Management Protocol) or the like.

  For example, when the user logs in to the printer PRT1, the user can execute printing for both the print job held in the server SV1 and the print job held in the server SV2 by the printer PRT1. Therefore, the operation information affects the estimation of print feasibility for a print job held in either the server SV1 or the server SV2. That is, since the operation information of the printer PRT1 is useful for a plurality of servers SV, if the operation information is transmitted to the plurality of servers SV, the print jobs can be flexibly managed by the plurality of servers SV.

  As mentioned above, although embodiment of this invention was described, this invention is not limited to such embodiment, Of course, in the range which does not deviate from the summary of this invention, it can implement in a various aspect. For example, the present invention shows a configuration example of a printer as a data output device. However, the data output device is not limited to a printer, and outputs data to a storage medium drive or display device that outputs data to a storage medium. It can be realized as various data output devices such as terminals, and the data management device can be realized as a data management device for managing output data output by these output devices. Further, the present invention is not limited to the configuration as the output data management system, the data output device, and the data management device shown in the embodiments, but can be realized in the form of an output data management method, a program, a storage medium, and the like.

2 is an explanatory diagram showing a schematic configuration of an output data management system 20. FIG. FIG. 3 is an explanatory diagram illustrating a schematic configuration of a printer PRT1. It is explanatory drawing which shows schematic structure of server SV. 6 is a flowchart illustrating a flow of a print job management process as the first embodiment. It is explanatory drawing, such as the content of the operation information which printer PRT1 in 1st Example transmits, and the notification conditions of operation information. It is explanatory drawing which shows the specific example of the change condition table 74 in 1st Example. FIG. 6 is an explanatory diagram illustrating a flow of a print job management process and a preceding process. It is explanatory drawing which shows the specific example of the job information table 72 and the operation | movement information table 73 in 1st Example. 10 is a flowchart illustrating a flow of a print job management process as a second embodiment. It is explanatory drawing of the content of the operation information which printer PRT1 in a 2nd Example transmits, the notification condition of operation information, etc. It is explanatory drawing which shows the specific example of the job information table 72 in 2nd Example. It is explanatory drawing which shows the specific example of the change condition table 74 in 2nd Example.

Explanation of symbols

20 ... Output data management system 30 ... CPU
31 ... Operation grasping unit 32 ... Operation judging unit 33 ... Information providing unit 40 ... EEPROM
42 ... Operation history storage area 51 ... ROM
52 ... RAM
53 ... Input mechanism 54 ... Printing mechanism 55 ... Scanner 56 ... FAX transmission mechanism 57 ... Authentication mechanism 58 ... Interface 60 ... CPU
61 ... Storage unit 62 ... Acquisition unit 63 ... Change unit 70 ... Hard disk drive 71 ... Job storage area 72 ... Job information table 73 ... Operation information table 74 ... Change Condition table 81 ... ROM
82 ... RAM
88 ... Interface PC ... Computer SV ... Server PRT1, PRT2 ... Printer LAN ... Local Area Network

Claims (19)

An output data management device for managing output data output by a predetermined data output device,
Storage means for holding the output data;
Acquisition means for receiving, from the data output device, operation information that is information relating to an operation history of the data output device;
An output data management device comprising: a changing unit that changes handling related to holding of output data that is not output in the data output device among the held output data based on the received operation information.   The output data management apparatus according to claim 1, wherein the operation information is a history of authentication performed in an authentication apparatus associated with the data output apparatus. The output data management apparatus according to claim 1 or 2,
The operation information is different from the first output data in the data output device, although the first output data held by the storage means is output. 2 is a history indicating that the output data of 2 has not been output,
The change means is an output data management device that changes the handling relating to holding of the second output data based on the operation information. An output data management device according to any one of claims 1 to 3,
The operation information is different from the first output data in the data output device, although the instruction to delete the first output data held by the storage means is received. It is a history indicating that an instruction to delete the second output data to be held is not accepted,
The change means is an output data management device that changes the handling relating to holding of the second output data based on the operation information.   The output data management apparatus according to any one of claims 1 to 3, wherein the change in the handling related to the holding is to delete or save the output data held by the storage unit.   The output data management apparatus according to any one of claims 1 to 5, wherein the change of the handling related to the holding is to change a predetermined holding period of the output data held by the storage unit.   The output data management apparatus according to claim 1, wherein the change of the handling related to the holding is to change a data format of the output data held by the storage unit.   8. The output data management apparatus according to claim 1, wherein the change unit performs the change when the received operation information satisfies a predetermined condition.   The output data management apparatus according to any one of claims 1 to 8, wherein the change unit performs the change when an ability to hold new output data in the storage unit has reached a predetermined state.   The output data management apparatus according to any one of claims 1 to 9, wherein the changing unit changes a content or a level of the change in accordance with an ability to hold new output data in the storage unit. The output data management device according to any one of claims 1 to 10,
The storage means holds the output data in association with an attribute of a first user who is a user related to the output data,
The operation history is a history associated with an attribute of a second user who is a user who operates the data output device,
The output means is an output data management device that changes handling related to retention of output data associated with a first user attribute corresponding to the second user attribute associated with the received operation information. An output data management device according to any one of claims 1 to 11,
The operation history is a history associated with the attribute of the user who operated the data output device,
The output data management device, wherein the changing means changes the content or degree of the change according to a user attribute associated with the received operation information. A data output device that receives output data from an output data management device and outputs the output data,
Operation grasping means for grasping a predetermined operation relating to the data output device;
A data output device comprising: providing means for providing the data management device with operation information, which is the grasped operation history. The data output device according to claim 13, wherein
Furthermore, the data output device when the predetermined operation is performed includes a determination unit that determines whether or not the data output device is in a state in which the data output device can output predetermined data.
The providing means provides the data management device with operation information including only a history of operations of the data output device performed in the output enabled state. An output data management system comprising a data output device that outputs predetermined data, and an output data management device that manages output data output by the data output device,
Storage means for holding the output data;
Operation grasping means for grasping a predetermined operation relating to the data output device;
An output data management comprising: a changing unit that changes handling of holding the output data that is not executed by the data output device among the held output data based on the grasped operation history system. An output data management method in which an output data management device manages output data to be output to a predetermined data output device,
Holding the output data,
Obtaining operation information which is information relating to the operation history of the data output device;
An output data management method for changing the handling of the output data that has not been output by the data output device, out of the held output data, based on the acquired operation information. A computer program for managing output data to be output to a predetermined data output device,
A storage function for holding the output data;
An acquisition function for receiving, from the data output device, operation information that is information related to the operation history of the data output device;
A program that causes a computer to implement a change function that changes handling of output data that has not been output by the data output device, out of the held output data, based on the received operation information. A computer program for providing the output data management device with information for managing output data by the output data management device,
An operation grasping function for grasping a predetermined operation relating to the data output device;
A program for causing a computer to realize a providing function of providing information related to the grasped operation history to the data management apparatus.   A recording medium in which the program according to claim 17 or 18 is recorded so as to be readable by a computer.

Images