Recording medium for recording printing programs and printing system for confidential printing
Summary by NHIP
Confidential Printing Job Processor
The system examines requests for confidential printing and alters document names within job data headers before release. Distinctive steps include encrypting names or moving them from original areas while displaying status without the altered identifiers.
Claim Score by NHIP
Abstract
A method of processing a printing job data is provided in which the secrecy of a job data required for the confidential printing can be ensured in the display of a status data indicative of a printing state of the job data. The method includes examining whether the confidential printing for a job data to be printed out is requested or not; when the confidential printing is requested, deleting or altering the document name contained in the job data; and releasing the job data from which the document name has been deleted or altered.

Term
Term ended
Expired 26 May 2024, 2.3 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
14 claims: 4 independent, 10 dependent
- 1A computer readable medium storing a computer program for a printer driver is, the computer program causing a computer to carry out a process comprising the steps of:examining whether a confidential printing is requested for a job data to be printed out or not;when the confidential printing is requested, deleting or altering only a document name contained in a header of the job data;releasing the job data from which the document name has been deleted or altered;and displaying on a display a status of the job data for the confidential printing without the document name of the job data for the confidential printing and displaying a status of the job data for a non confidential printing with the document name of the job data.
- 5Broadest claimClaim Score 74, broad(NHIP)A method of processing a printing job data in a data processor for transmitting the printing job data to a printer, the method comprising the steps of:examining whether a confidential printing is requested for a job data to be printed out or not;when the confidential printing is requested, deleting or altering only the document name contained in a header of the job data;releasing the job data from which the document name has been deleted or altered;and displaying on a display a status of the job data for the confidential printing without the document name of the job data for the confidential printing and displaying a status of the job data for a non confidential printing with the document name of the job data.
- 8An apparatus for data processing having a display and arranged for transmitting a processed printing job data to a printer, comprising:a setter for setting a confidential printing for the job data;a transmitter controller for transmitting the job data to the printer;a receiver controller for receiving from the printer a status data indicative of a processing state of the job;and a display controller for displaying the received status data on a display, wherein the display controller displays a status condition of the job data for the confidential printing without the document name of the job data for the confidential printing and displays a status condition of the job data for a non confidential printing with the document name of the job data.
- 10A printing system having at least one data processor equipped with a display and a printer for carrying out a printing action according to a job data received from the data processor, the data processor comprising:a setter for setting a confidential printing for the job data;a first transmitter controller for transmitting the job data to the printer;a receiver controller for receiving from the printer a status data indicative of a processing state of the job;and a display controller for displaying the received status data on a display, wherein the display controller displays a status condition of the job data for the confidential printing without the document name of the job data for the confidential printing and displays a status condition of the job data for a non confidential printing with the document name of the job data.
Independent claims4
89 paragraphs in 4 sections, as filed
0001This application is based on application No. 2000-279796 filed in Japan, the contents of which is hereby incorporated by reference.
BACKGROUND OF THE INVENTION
0002The present invention relates to a printing system for printing job data and a method implemented with the printing system.
0003In a printing system comprising a printer and a data processor (referred to as a PC hereinafter) for providing the printer with job data such as image data or text data, a printer driver is commonly installed on the PC for allowing the PC to control the printer in order to identify the printer to which the job data is delivered. The printing conditions including the time of print output and the number of prints can be arbitrarily determined by the user on the printer driver, and the information for the printing conditions is transmitted together with the job data to the printer for controlling the printing action. There is a known technique in which the information for the printer including the current action mode (for example, paper feeding, printing, or paper discharging), the printing state of the job data, the error (for example, feeding error), and the information for optional equipments (e.g. a duplex printing unit and a finisher) including the existence of the optional equipment connected to the printer, the errors can be obtained by the printer driver during communicating with the printer, and the informations can be displayed as status information for the printer and the optional equipments. In such a technique, the document name, the owner name, and the printing registration time at the printer for the job data may also be displayed together with the printing state of the job data (printing or waiting).
0004The printing system has a secret printing function where a job data which is confidential is tagged with a password by the user operating the printer driver and can thus be printed out only when the password is entered on the printer. In the prior art, the status data such as the document name and the owner name of the job, the printing registration time of the printer are displayed on the printer driver in case of the confidential printing as well as case of common printing. This may deteriorate the secrecy of the job data by guessing its content from the document name.
0005The present invention has been developed in view of the above technical drawback and its object is to maintain the secrecy of a job data required for the confidential printing in the display of a status data indicative of a printing state of the job data.
SUMMARY OF THE INVENTION
0006In an aspect of the present invention, there is provided a recording medium in which a program for a printer driver is stored and can be read out by a computer, the program comprising the steps of: examining whether the confidential printing for a job data to be printed out is requested or not; when the confidential printing is requested, deleting or altering the document name contained in the job data; and releasing the job data from which the document name has been deleted or altered.
0007The program may further comprises a step of requesting the confidential printing for the job data through the entry action of a user. The step of deleting or altering the document name may include a sub-step of encrypting the document name. Also, the step of deleting or altering the document name may include a sub-step of storing the document name in a data area other than its original data area. The program may further comprise a step of displaying on a display a status data indicative of a processing state of the job data on a printer. The status data displayed may contain the document name.
0008In another aspect of the present invention, there is provided a method of processing a printing job data in a data processor on which a printer driver is installed, comprising the steps of: examining whether the confidential printing for a job data to be printed out is requested or not; when the confidential printing is requested, deleting or altering the document name contained in the job data; and releasing the job data from which the document name has been deleted or altered.
0009The step of deleting or altering the document name may include a sub-step of encrypting the document name. Also, the step of deleting or altering the document name may include a sub-step of storing the document name in a data area other than its original data area. The method of processing a printing job data may further comprise a step of displaying on a display a status data indicative of a processing state of the job data on a printer. The status data displayed may contain the document name.
0010In a further aspect of the present invention, there is provided an apparatus for data processing having a display and arranged for transmitting a processed printing job data to a printer, comprising: a setter for setting the confidential printing for a job data; a transmitter controller for transmitting the job data to the printer; a receiver controller for receiving from the printer a status data indicative of a processing state of the job; and a display controller for displaying the received status data on a display, wherein the display controller allows the job data for the confidential printing to display its status data excluding the document name and the job data for no confidential printing to display its status data including the document name.
0011The apparatus for data processing may further comprise a data processing controller for deleting or altering he document name contained in the job data when the confidential printing is requested, wherein the transmitter controller transmits to the printer the job data in which the document name is deleted or altered.
0012In a still further aspect of the present invention, there is provided a printing system having at least one data processor equipped with a display and a printer for carrying out a printing action according to a job data received from the data processor. The data processor comprises: a setter for setting the confidential printing for the job data; a first transmitter controller for transmitting the job data to the printer; a receiver controller for receiving from the printer a status data indicative of a processing state of the job; and a display controller for displaying the received status data on a display, wherein the display controller allows the job data for the confidential printing to display its status data excluding the document name and the job data for no confidential printing to display its status data including the document name.
0013The data processor may further comprise a data processing controller for deleting or altering the document name contained in the job data when the confidential printing is requested. Also, the data processor may further comprise a second transmitter controller for transmitting a command for transmission of the status data to the printer while the printer includes a third transmitter controller for transmitting the status data to the data processor when receiving the command for transmission. It may be arranged that the second transmitter controller transmits the identification data of a user along with the command for transmission of the status data and the third transmitter controller transmits the status data based on the identification data of the user. Moreover, it may be arranged that the first transmitter controller transmits to the printer the job data added with an IP address of the data processor, the second transmitter controller transmits the IP address along with the command for transmission of the status data, and the third transmitter controller transmits the status data of a job data added with an IP address which is identical to the IP address received from the second transmitter controller.
BRIEF DESCRIPTION OF THE DRAWINGS
0014<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram showing a printing system according to the first embodiment of the present invention;
0015<figref idref="DRAWINGS">FIG. 2</figref> is a view of a setting screen for a printer driver installed in a PC provided in the printing system;
0016<figref idref="DRAWINGS">FIG. 3</figref> is a view of a status display screen on a printer controlled by the printer driver;
0017<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart showing procedure based on functions of the printer driver;
0018<figref idref="DRAWINGS">FIG. 5</figref> is a diagram showing a data structure of the job data produced by the printer driver;
0019<figref idref="DRAWINGS">FIG. 6</figref> is a diagram schematically illustrating functions of the printer driver;
0020<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart showing a procedure of actions of the printer driver installed on a PC provided in a printing system according to the second embodiment of the present invention;
0021<figref idref="DRAWINGS">FIG. 8</figref> is a diagram schematically illustrating functions of the printer driver according to the second embodiment;
0022<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart showing a procedure of printing actions of a printer according to the second embodiment;
0023<figref idref="DRAWINGS">FIG. 10</figref> is a diagram showing a data structure of the job data produced by the printer driver according to the second embodiment;
0024<figref idref="DRAWINGS">FIG. 11</figref> is an explanatory view showing an encryption process and a decryption process in the printing system of the second embodiment;
0025<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart showing a procedure of status data displaying actions of the printer driver installed on a PC provided in a printing system according to the third embodiment of the present invention;
0026<figref idref="DRAWINGS">FIG. 13</figref> is a flowchart showing a procedure of status data transmitting actions of a printer according to the third embodiment;
0027<figref idref="DRAWINGS">FIG. 14</figref> illustrates an example of the status data screen displayed on a display of the PC according to the third embodiment;
0028<figref idref="DRAWINGS">FIG. 15</figref> illustrates another example of the status data screen displayed on the display of the PC according to the third embodiment;
0029<figref idref="DRAWINGS">FIG. 16</figref> illustrates a further example of the status data screen displayed on the display of the PC according to the third embodiment;
0030<figref idref="DRAWINGS">FIG. 17</figref> illustrates a still further example of the status data screen displayed on the display of the PC according to the third embodiment;
0031<figref idref="DRAWINGS">FIG. 18</figref> is a flowchart showing a procedure of actions of the printer driver installed on a PC provided in a printing system according to the fourth embodiment of the present invention;
0032<figref idref="DRAWINGS">FIG. 19</figref> is a flowchart showing a procedure of printing actions of a printer according to the fourth embodiment;
0033<figref idref="DRAWINGS">FIG. 20</figref> is a flowchart showing a procedure of printing actions of the printer controlled by the action of the printer driver shown in <figref idref="DRAWINGS">FIG. 18</figref>;
0034<figref idref="DRAWINGS">FIG. 21</figref> is a flowchart showing a procedure of status data displaying actions of the PC according to the fourth embodiment;
0035<figref idref="DRAWINGS">FIG. 22</figref> is a flowchart showing a procedure of printing actions of the printer controlled by the status data displaying action of the PC shown in <figref idref="DRAWINGS">FIG. 21</figref>; and
0036<figref idref="DRAWINGS">FIG. 23</figref> illustrates an example of the status data screen.
DETAILED DESCRIPTION OF THE INVENTION
0037Some embodiments of the present invention will be described referring to the accompanying drawings.
First Embodiment
0038<figref idref="DRAWINGS">FIG. 1</figref> illustrates a network including a printing system according to the first embodiment of the present invention. The printing system in the network <b>1</b> comprises a plurality of personal computers <b>10</b>, <b>40</b>, and <b>50</b> (referred to as PCs hereinafter) and a printer <b>20</b> for releasing as prints a job data received from the PCs. In the printing system, the single printer <b>20</b> is shared by the PCs <b>10</b>, <b>40</b>, and <b>50</b>, and a printer driver is installed on each of PCs for allowing each PC to set a variety of printing conditions and to control the printer <b>20</b> in order to identify the printer <b>20</b> to which the job data is delivered. The printer driver is a software for controlling the action of the printer which converts text and image data received from an application or OS into a data interpretable with the printer and transmits the interpreted data while monitoring the status of the printer.
0039As the PC <b>10</b> is illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, the other PCs <b>40</b> and <b>50</b> are identical to the PC <b>10</b> and their description will be omitted.
0040Each of the PCs <b>10</b>, <b>40</b>, and <b>50</b> in the printing system comprises a CPU <b>11</b> for sequentially controlling the PC, a ROM <b>12</b> for recording a program of the sequential control by CPU <b>11</b>, a RAM <b>13</b> used as a buffer area for a work area required for executing the program, an interface (denoted by I/F throughout the drawings) <b>14</b> for receiving/transmitting data from/to the printer <b>20</b>, and a display <b>15</b> for displaying a setting screen and a data screen determined by the printer driver.
0041The printer <b>20</b> comprises a CPU <b>21</b> for sequentially controlling the printer, a ROM <b>22</b> for recording a program of the sequential control by CPU <b>21</b>, a RAM <b>23</b> used as a work area required for the program and a buffer area for the job data received from the PCs <b>10</b>, <b>40</b>, and <b>50</b>, an interface (denoted by I/F throughout the drawings) <b>24</b> for receiving/transmitting data from/to the PC <b>10</b>, a printing unit <b>25</b> for producing paper prints according to the job data, and a data processor <b>26</b> for processing the data with a variety of data processing such as color spatial conversion or binarization.
0042When the printer driver installed on each of the PCs <b>10</b>, <b>40</b>, and <b>50</b> starts its action in response to the printing command in an application software, the setting screen such as shown in <figref idref="DRAWINGS">FIG. 2</figref> is displayed on the display <b>15</b>. This allows the user to set the printing conditions including the paper size to be used (“PAPER SIZE” in <figref idref="DRAWINGS">FIG. 2</figref>) and the image orientation (“ORIENTATION” in <figref idref="DRAWINGS">FIG. 2</figref>). This also allows the user to select a confidential printing. If the confidential printing is selected, the user may tag the job data with a password, and then the job data is transmitted to printer <b>20</b>. Accordingly, when printer <b>20</b> is provided with the same password entered, its printing action will start. In the state as shown in <figref idref="DRAWINGS">FIG. 2</figref>, the check blank in front of “LOCK JOB” is checked to select the confidential printing mode. At the confidential printing mode, the password is typed in the blank behind “LOCK JOB”. On the illustrated setting screen, the check blank in front of “LOCK JOB” is not checked by default, and therefore “common printing” will be performed on printer <b>20</b>.
0043The printer driver may obtain through the network <b>1</b> the data indicative of status for the printer <b>20</b> including its action mode, the printing state of the job data, and the error, and the data indicative of status for optional equipments (e.g. a duplex printing unit and a finisher) including the existence of optional equipments connected to printer <b>20</b> and the errors. The status data for the printer <b>20</b> and optional equipments may be displayed on the display <b>15</b> of each PC <b>10</b>, <b>40</b>, or <b>50</b> if desired by the user. One of screens representing the status data for printer <b>20</b> and optional equipments (a status data screen) is the screen representing the printing state of the job data transmitted from the PC <b>10</b>, <b>40</b>, or <b>50</b> as shown in <figref idref="DRAWINGS">FIG. 3</figref>. The screen exhibits the document data (the name of a data file such as the printing or image data), the owner name (the name of a user requesting the printing of the job), and the printing registration time for the job data as well as the printing state (printing or standby). As will be described later in more detail, in this embodiment, if the confidential printing has been selected on the setting screen of printer driver, the status data screen can be controlled such that the document name of the job data is deleted on the status data screen.
0044<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart showing procedure based on functions of the printer driver installed on the PC <b>10</b> according to the first embodiment of the present invention. The procedure starts with a common function of the printer driver initialized in response to the printing command of an application software, which is based on the setting conditions determined by the user (S <b>11</b>). As a result of this function, the job data having the data structure as shown in <figref idref="DRAWINGS">FIG. 5</figref> is obtained. The job data is composed of the document name and the image data received from the application software, and the printing conditions (e.g. the number of prints), which are determined by the user at the setting screen of the printer driver. An architecture of the job data comprises a header containing the data indicative of “owner name”, “document name”, and “original size”, and a main field containing the image data.
0045This is followed by S<b>12</b> where it is examined whether a command for the confidential printing is provided or not on the setting screen. When so, the document name is deleted from the job data (S<b>13</b>) and the job data is transmitted to a device driver (S<b>14</b>). If it is judged at S<b>12</b> that the command for the confidential printing is not provided or a common printing is setting, the procedure goes to S<b>14</b> where the job data is transmitted to the device driver without deleting the document name. Then, the device driver transmits the job data to the printer <b>20</b> and the procedure is terminated.
0046<figref idref="DRAWINGS">FIG. 6</figref> is an explanatory view schematically illustrating the procedure of the flowchart of <figref idref="DRAWINGS">FIG. 4</figref>. When the common printing is setting, the printer driver installed on each PC <b>10</b>, <b>40</b>, or <b>50</b> transmits the job data <b>2</b> received from an application software without deleting the document name to the device driver. Alternatively, when the confidential printing is setting, the document name is deleted and then a job data <b>2</b>A including no document name is transmitted to the device driver.
0047As a result, the display <b>15</b> of each PC <b>10</b>, <b>40</b>, or <b>50</b> exhibits a status data screen (<figref idref="DRAWINGS">FIG. 3</figref>) where assuming that the three PCs <b>10</b>, <b>40</b>, and <b>50</b> are operated by three individuals, Suzuki, Satoh, and Tanaka, the common printing is conducted by Suzuki and Tanaka while both the common and confidential printings are conducted by Satoh. The status data screen indicates the document names, owner names, and printing registration times of the job data provided by the PCs <b>10</b>, <b>40</b>, and <b>50</b> to the printer <b>20</b> and arranged in an order of printing. The job data No.1 is provided by Suzuki and now in printing (“PRINTING”). The job data No.1 is set with the common printing mode and “TEXT 1” is displayed as its document name.
0048Similarly, the job data No.2 to No.4 are provided by Satoh, Tanaka, and Satoh respectively as in a waiting state (“WAITING”). The job data No.2 is set with the confidential printing mode and its document name is not displayed. The job data No.3 and No.4 are set with the common printing mode and “TEXT 3” and “TEXT 4” are displayed as their document names respectively.
0049Therefore, the job data provided by a PC for the confidential printing can be inhibited from exhibiting its document name on the status data screen. The job data will not be estimated from its document name, thus being improved in the secrecy.
Second Embodiment
0050A printing system according to the second embodiment of the present invention is adapted where when the confidential printing is selected by the printer driver in a PC, the document name of a job data is encrypted by the printer driver before the job data is transmitted to the printer, and is decrypted at the printer. This action will now be explained in more detail. The printing system of the second embodiment is substantially identical to that of the first embodiment and will thus be described referring to <figref idref="DRAWINGS">FIG. 1</figref>.
0051This printing system has a function provided in each PC <b>10</b>, <b>40</b>, or <b>50</b> for encrypting the document name of a particular job selected for the confidential printing by the user operating the printer driver. In turn, the printer <b>20</b> has a program stored in the ROM <b>22</b> for decryption of the document name.
0052<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart showing a procedure of actions of the printer driver in the PC <b>10</b> according to the second embodiment. The procedure starts with the printer driver initiated in response to the printing command of an application software to carry out a common action determined by the user operating the printer driver (S<b>21</b>). It is then examined at S<b>22</b> whether the command for the confidential printing is received or not on the printer driver setting screen (See <figref idref="DRAWINGS">FIG. 2</figref>). When so, the document name of the job is encrypted (S<b>23</b>) and transmitted to the device driver (S<b>24</b>). If it is judged at S<b>22</b> that the command for the confidential printing is not received or the common printing mode is selected, the procedure jumps to S<b>24</b> where the job data is directly transmitted to the device driver without encrypting its document name. Then, the job data is transmitted from the device driver to the printer <b>20</b> and this procedure is terminated.
0053<figref idref="DRAWINGS">FIG. 8</figref> is an explanatory view schematically showing the procedure of the flowchart of <figref idref="DRAWINGS">FIG. 7</figref>. When receiving from an application software a job data <b>2</b> provided for the common printing, the printer driver installed on each PC <b>10</b>, <b>40</b>, or <b>50</b> transmits it with document name as it is to the device drive without encrypting its document name. Alternatively, when the job data is provided for the confidential printing, its document name is encrypted and a job data <b>2</b>B is transmitted to the device driver.
0054<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart illustrating a printing procedure of the printer <b>20</b> controlled by the printer driver shown in <figref idref="DRAWINGS">FIG. 7</figref>. This procedure starts with receiving a job data (S<b>31</b>) and examining whether or not it is provided for the confidential printing (S<b>32</b>). When the job data is provided for the confidential printing, its document name is decrypted (S<b>33</b>) and the procedure goes to S<b>34</b>. When it is judged at S<b>32</b> that the job data is provided not for the confidential printing, the procedure jumps to S<b>34</b>. At S<b>34</b>, the printing process is carried out and it is then examined at S<b>35</b> whether another job data is received or not. If not, the procedure is terminated. When it is judged that the another job data is received, the procedure returns back to S<b>31</b> and repeats the above described steps.
0055In the second embodiment, the document name of a job data may be encrypted by Caesar encoding. The Caesar encoding permits each original character in a text such as an Alphabet, a Japanese Hiragana, or a numeral to be replaced by another character which shifts backward from the original character by a given number of characters. For example, when the Caesar encoding is made by shifting two characters backward, “CAP” is expressed by “ECR”.
0056Like the first embodiment, an image data and its document name received from an application software are accompanied with relevant printing conditions such as the number of prints which are entered by the user through the print setting screen of the printer driver thus to construct a job data having a data structure shown in <figref idref="DRAWINGS">FIG. 10</figref>. The job data according to the second embodiment has a header arranged to contain the data indicative of “owner name”, “document name”, “original size” and an extra data of “NUM” indicative of the shift number of characters for the Caesar encoding. The “document name” in the header is encrypted by shifting the characters of the name according to “NUM”.
0057In the second embodiment, the “NUM” may arbitrarily be determined by the user. When the common printing is desired, the “NUM” is automatically turned to zero. In case that the encryption is based on the ASCII coding or the JIS coding, the characters of the document name are not limited to the Alphabets, the Japanese Hiraganas, or the numerals but may be symbols or Chinese characters.
0058<figref idref="DRAWINGS">FIG. 11</figref> illustrates actions for encryption by the Caesar encoding in the PC and for decryption of the encrypted document name such as “TEXT 2” of the ASCII coding in the printer. In the PC, the document name “TEXT 2” of the ASCII coding is converted by the function of the printer driver into an ASCII code “54 45 58 54 32” when the confidential printing is selected. When having been converted, the ASCII code is shifted by two based on “NUM”. The document name is hence encrypted to “56 67 7A 76 34”. The document name is expressed by “VGZV4” on the ASCII coding. The document name in the encrypted form is then transmitted from the PC to the printer.
0059At the printer, the document name “56 47 60 56 34” is returned back to its original ASCII form “54 45 58 54 32” by the subtraction of two based on “NUM”. As the result, the document name “TEXT 2” in the ASCII form is reconstructed. Then, the printer receives the document name “TEXT 2”.
0060Therefore, the document name of a job data is encrypted by the printer driver in the PC when the confidential printing is desired and then transmitted to the printer where it is duly decrypted. While the encrypted form of its document name is conveyed from the PC to the printer, the job data will be hardly guessed. Accordingly, the secrecy of the job data can be maintained.
0061While the document name is subjected to the encryption in the second embodiment, it may simply be modified to another name without being encrypted.
Third Embodiment
0062In a printing system of the third embodiment of the present invention, a job data provided in the printer <b>20</b> for the confidential printing can, while being displayed on the status data screen, be modified by any viewer at the PC <b>10</b>, <b>40</b>, or <b>50</b>, such as the owner of the job data, another user, or a manager for the printer. As will be described referring to <figref idref="DRAWINGS">FIGS. 12 to 17</figref>, the modification is carried out at the action mode which is displayed in the status data screen as classified into two modes, “owner & manager mode” selected when the viewer is either the owner of the job data or the manager for the printer <b>20</b>, and “normal mode” selected in any other case. The “owner & manager mode” further includes a function for the user entering “user name” and “password”. In the printer <b>20</b>, it is examined from the display mode, user name, and password determined at the PC <b>10</b>, <b>40</b>, or <b>50</b> whether the viewer demanding the status data screen is the owner of the job data, the other user, or the manager for the printer. The status data screen for exhibiting corresponding requirements can thus be received by the owner of the job data, the other user, or the manager for the printer at the PC <b>10</b>, <b>40</b>, or <b>50</b>.
0063<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart showing a procedure of status data displaying actions at the printer <b>20</b> according to the third embodiment of the present invention. The procedure starts with transmitting a command for acquisition of the status data from the PC <b>10</b>, <b>40</b>, or <b>50</b> to the printer <b>20</b> (S<b>41</b>). As the status data is received from the printer <b>20</b> (S<b>42</b>), its status data screen is displayed on the display <b>30</b> of the PC <b>10</b>, <b>40</b>, or <b>50</b> (S<b>43</b>). It is then examined whether a command for changing the display mode in the status data screen is provided or not (S<b>44</b>). If not, the procedure is terminated. When it is judged that the command for changing the display mode is provided, the procedure goes to S<b>45</b> for examining whether the display mode in the status data screen is “owner & manager mode” or not. When it is judged that the display mode is “owner & manager mode”, the procedure advances to S<b>46</b> where the user name and the password entered at the setting of “owner & manager mode” are identified. The user name and the password are then transmitted to the printer <b>20</b> together with the command for acquisition of the status data screen (S<b>47</b>). The procedure returns back to S<b>42</b> and the above described steps are repeated. When it is judged at S<b>45</b> that the display mode is not “owner & manager mode” (but “normal mode”), the command for acquisition of the status data screen is transmitted to the printer <b>20</b> (S<b>48</b>). The procedure returns back to S<b>42</b> and the same steps are repeated.
0064<figref idref="DRAWINGS">FIG. 13</figref> is a flowchart showing a procedure of status data transmitting actions at the printer <b>20</b> according to the third embodiment. The procedure starts with receiving the command for acquisition of the status data from the PC <b>10</b>, <b>40</b>, or <b>50</b> (S<b>51</b>). It is then examined from the display mode, user name, and password determined by the PC <b>10</b>, <b>40</b>, or <b>50</b> whether the display mode is “manager mode” or not (S<b>52</b>). It is judged that the display mode is “manager mode” only when the user name and the password entered at the setting of “owner & manager mode” in the PC <b>10</b>, <b>40</b>, or <b>50</b> are identical to the manager name for the printer <b>20</b> and its password registered in the RAM <b>23</b> of the printer <b>20</b>.
0065When it is judged at S<b>52</b> that the display mode is “manager mode”, the procedure goes to S<b>53</b> where the status data of all job data in printing and waiting in the printer <b>20</b> are produced. Simultaneously, the document name of the job data provided for the confidential printing is deleted. This is followed by S<b>57</b>. When it is judged at S<b>52</b> that the display mode is not “manager mode”, the procedure goes to S<b>54</b> for examining whether the display mode is “owner mode” or not. It is judged that the display mode is “owner mode” only when the user name and the password entered at the setting of “owner & manager mode” in the PC <b>10</b>, <b>40</b>, or <b>50</b> are identical to the owner name of the PC and its password registered in the RAM <b>23</b> of the printer <b>20</b>.
0066When it is judged at S<b>54</b> that the display mode is “owner mode”, the procedure goes to S<b>55</b> where the status data of the job data in printing and waiting in the printer <b>20</b> are generated. The status data of all the job data provided for the common printing and of the owner provided for the confidential printing are generated. This is followed by S<b>57</b>. When it is judged at S<b>54</b> that the display mode is not “owner mode” (but “normal mode”), the status data of the job data provided for the common printing are produced at S<b>56</b>. Then, the procedure advances to S<b>57</b>.
0067At S<b>57</b>, the status data of the job data generated at each of the steps S<b>53</b>, S<b>55</b>, and S<b>56</b> are transmitted to the PC which provides the command for acquisition of the status data. At S<b>58</b>, it is then examined whether the command for acquisition of the status data from the PC <b>10</b>, <b>40</b>, or <b>50</b> is duly received or not. When so, the procedure returns back to S<b>51</b> and the foregoing steps are repeated. When it is judged at S<b>57</b> that the command is not received, the procedure is terminated.
0068Assuming that the PCs <b>10</b>, <b>40</b>, and <b>50</b> are operated by three individuals, Suzuki, Satoh, and Tanaka respectively with the printer <b>20</b> receiving the job data for both the common printing and the confidential printing, examples of the status data screen displayed on the display <b>13</b> of each of the PCs <b>10</b>, <b>40</b>, and <b>50</b> will be explained referring to <figref idref="DRAWINGS">FIGS. 14 to 17</figref>. The printer <b>20</b> receives the three job data No.1, No.2 and No.3. More specifically, the job data No.1 for the common printing is provided by Suzuki operating the PC <b>10</b> and its document name is “TEXT 1”. Similarly, the job data No.2 for the confidential printing is provided by Suzuki operating the PC <b>10</b> and its document name is “TEXT 2”. The job data No.3 for the confidential printing is provided by Satoh operating the PC <b>40</b> and its document name is “TEXT 3”.
0069<figref idref="DRAWINGS">FIG. 14</figref> illustrates an example of the status data screen at the normal mode displayed on the PC <b>10</b> as arranged accessible to Suzuki. As the screen at the normal mode is determined by the printer <b>20</b> to be accessible to the user, not the owner or the manager, it only displays the job data No.1 for the common printing.
0070<figref idref="DRAWINGS">FIG. 15</figref> illustrates an example of the status data screen at the owner & manager mode displayed on the PC <b>10</b> as arranged accessible to Suzuki. As the screen at the owner & manager mode with the user name and the password filled is determined by the printer <b>20</b> to be accessible to the owner, it displays the job data No.1 for the common printing and the job data No.2 for the confidential printing requested by the owner (i.e. Suzuki). The sign “LOCK” in front of “Status” indicates that the job data is provided for the confidential printing.
0071<figref idref="DRAWINGS">FIG. 16</figref> illustrates an example of the status data screen at the owner & manager mode displayed on the PC <b>50</b> as arranged accessible to Tanaka. As the job data for Tanaka doesn't exist and it is determined by printer <b>20</b> that viewer is not owner or manager while the owner & manager mode is selected and user name and the password are entered, the status data screen displays the job data No.1 for the common printing.
0072<figref idref="DRAWINGS">FIG. 17</figref> illustrates an example of the status data screen at the owner & manager mode displayed on the PC as arranged accessible to the manager for the printer <b>20</b> but not Suzuki, Satoh, or Tanaka. As the owner & manager mode is set and the user name and the password are entered, and it is determined by printer <b>20</b> that viewer is the manager for printer <b>20</b>, the status data screen displays the job data No.1 to No.3. The document names of the job data No.1 and No.2 provided for the confidential printing are not displayed.
0073Therefore, the job data provided for the confidential printing is displayed only when the viewer for the status data screen is the owner or the manager. When the viewer is the manager, the document name of each job data is not displayed. As no document name of the job data is accessible by any other viewer than the owner, the contents of the job data will be hardly guessed. Accordingly, the secrecy of the job data will be improved.
Fourth Embodiment
0074A printing system according to the fourth embodiment of the present invention allows the printer driver of each PC to assign the document name of a job data to another form when the confidential printing is selected in the printer driver. More particularly, the document name of the job data is moved from its original storage area to another area in the data structure and it can be retrieved in the printer to which the job data has been transmitted. In the fourth embodiment, the IP address of each PC is added to the job data produced by the printer driver of the PC and when the IP address of a confidential print is identical to that of the PC, the status data is displayed on the display of the PC. Those functions will be described in more detail.
0075<figref idref="DRAWINGS">FIG. 18</figref> is a flowchart showing a procedure of functions of the printer driver in the PC <b>10</b> according to the fourth embodiment. The procedure starts with carrying a common action of the printer driver, which is initiated in response to the printing command of an application software, according to the conditions determined by the user (S<b>61</b>). A job data having a predetermined construction is produced from the document name and the image data received from the application software and the printing conditions such as the number of prints determined by the user operating the printer driver at the setting screen.
0076It is then examined at S<b>62</b> whether a command for the confidential printing is provided or not on the setting screen of the printer driver. When so, the document name of the job data is moved from its original area for the common printing to another area in the data structure of the job data (S<b>63</b>). Also, the IP address is inserted into the job data (S<b>64</b>). As a result, the data structure of the job data is modified as shown in <figref idref="DRAWINGS">FIG. 19</figref>. “NUM” in the job data is used for examining at S<b>62</b> whether the command for the confidential printing is provided or not. When the “NUM” is 0, the common printing is selected. When the “NUM” is 1, the confidential printing is required. As the confidential printing is selected, the document name of the job data is shifted from its original area denoted by “document name” to another area of the data structure denoted by “DOC” as shown in <figref idref="DRAWINGS">FIG. 19</figref>. Also, the area denoted by “IP address” in the data structure contains the IP address of the PC. When the common printing is desired, the document name of the job data remains held in the “document name” area and the IP address of the PC is not provided.
0077After the IP address of the PC is inserted into the job data at S<b>64</b>, the job data is transmitted to the device driver (S<b>65</b>). If it is judged at S<b>62</b> that the confidential printing is not commanded or the common printing is desired, the procedure jumps to S<b>65</b> for transmitting the job data to the device driver. Then, when the job data has been transmitted from the device driver to the printer <b>20</b>, the procedure is terminated.
0078Therefore, the document name of the job data is moved from its original area for the common printing to another area of the data structure when the confidential printing is selected before the job data is transmitted to the printer <b>20</b>. This inhibits the document name of the job data from being identified while being conveyed from the PC <b>10</b>, <b>40</b>, or <b>50</b> to the printer <b>20</b>. Accordingly, the contents of the job data will be hardly guessed from its document name and its secrecy can thus be ensured.
0079<figref idref="DRAWINGS">FIG. 20</figref> is a flowchart showing a procedure of printing actions of the printer <b>20</b> carried out according to the action of the printer driver shown in <figref idref="DRAWINGS">FIG. 18</figref>. The procedure starts with receiving a job data (S<b>71</b>) and examining whether the confidential printing is selected or not (S<b>72</b>). When so, the document name and the IP address in the job data are obtained (S<b>73</b>) and the procedure goes to S<b>74</b>. When it is judged at S<b>72</b> that the confidential printing not required, the procedure jumps to S<b>74</b>. At S<b>74</b>, the printing is carried out. It is then examined at S<b>75</b> whether another job data is received or not. If not, the procedure is terminated. When it is judged that the another job data is received, the procedure returns back to S<b>71</b> for repeating the foregoing steps.
0080<figref idref="DRAWINGS">FIG. 21</figref> is a flowchart showing a procedure of PC status data displaying actions according to the fourth embodiment. The procedure starts with transmitting a command for acquisition of the IP address and status data of the PC from the PC <b>10</b>, <b>40</b>, or <b>50</b> to the printer <b>20</b> (S<b>81</b>). When the status data is received from the printer <b>20</b> (S<b>82</b>), the status data screen is displayed on the display <b>13</b> of the PC <b>10</b>, <b>40</b>, or <b>50</b> (S<b>83</b>). The procedure is then terminated.
0081<figref idref="DRAWINGS">FIG. 22</figref> is a flowchart showing a procedure of printing actions of the printer <b>20</b> controlled by the status data displaying action of the PC shown in <figref idref="DRAWINGS">FIG. 21</figref>. The procedure starts with receiving a command for acquisition of the status data from the PC (S<b>91</b>) and generating the status data of a job data for the common printing (S<b>92</b>). The IP address received from the PC along with the command for acquisition of the status data is compared with the IP address of the job data determined for the confidential printing and stored in the printer <b>20</b> (S<b>93</b>). It is then examined from the result of the comparison whether the job data for the confidential printing is provided or not (S<b>94</b>). When it is judged that the job data for the confidential printing is provided, the status data of the job data for the confidential printing is produced (S<b>95</b>) and the procedure goes to S<b>96</b>. When it is judged that the job data for the confidential printing is not provided at S<b>94</b>, the procedure jumps to S<b>96</b>. At S<b>96</b>, the status data produced at S<b>92</b> and S<b>95</b> are transmitted to the PC which delivers the command for acquisition of the status data. It is further examined whether another command for acquisition of the status data is received from the PC <b>10</b>, <b>40</b>, or <b>50</b>. When so, the procedure returns to S<b>91</b> for repeating the above steps. When it is judged at S<b>97</b> that a command is not received, the procedure is terminated.
0082<figref idref="DRAWINGS">FIG. 23</figref> illustrates an example of the status data screen displayed on the PC <b>10</b> as arranged accessible to Suzuki. The screen displays the job data No.1 for the common printing and the job data No2 for the confidential printing of which the owner is Suzuki. The job data for the confidential printing determined by other users than Suzuki are not displayed.
0083Therefore, the status data of a job data for the confidential printing is produced only when the IP address of the job data is identical to the IP address received by the printer along with a command for acquisition of the status data. Otherwise, no status data is displayed and the secrecy of each job data for the confidential printing can be ensured. While the status data screen for the manager for the printer is not provided in the fourth embodiment, a job data for the confidential printing may be produced when the IP address of the manager for the printer registered in advance is found identical to the IP address received together with a command for acquisition of the status data. In this case, the document name of the job data for the confidential printing is not displayed.
0084The actions and steps illustrated in the flowcharts of the foregoing embodiments are conducted and controlled by the operating programs installed in the PCs <b>10</b>, <b>40</b>, and <b>50</b> and the printer <b>20</b>. More specifically, the operating programs are stored in the ROMs <b>12</b> of the PCs <b>10</b>, <b>40</b>, and <b>50</b> and the ROM <b>22</b> of the printer <b>20</b> (See <figref idref="DRAWINGS">FIG. 1</figref>). The storing means for storing the programs are not limited to the ROMs but may be any other external recording mediums such as a CD-ROM <b>17</b> or a floppy disk <b>18</b> arranged readable by the PC <b>10</b>.
0085It would be understood that the present invention is not limited to the foregoing embodiments but various modifications and changes are possible without departing the scope of the present invention.
Contents4
23 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2010002248A1 | Cited by | United States of America | Pre-grant |
| US2009015866A1 | Cited by | United States of America | Pre-grant |
| US2009244596A1 | Cited by | United States of America | Pre-grant |
| US8564804B2 | Cited by | United States of America | Applicant |
| US8111413B2 | Cited by | United States of America | Search report |
| US7735143B2 | Cited by | United States of America | Search report |
| US9513857B2 | Cited by | United States of America | Applicant |
| US8797563B2 | Cited by | United States of America | Applicant |
| US9311031B2 | Cited by | United States of America | Applicant |
| US2009213395A1 | Cited by | United States of America | Pre-grant |
| US8081327B2 | Cited by | United States of America | Search report |
| US2006020820A1 | Cited by | United States of America | Pre-grant |
| US8395811B2 | Cited by | United States of America | Applicant |
| US2009244594A1 | Cited by | United States of America | Pre-grant |
| US2006279773A1 | Cited by | United States of America | Pre-grant |
| US2010202006A1 | Cited by | United States of America | Pre-grant |
| US2009244595A1 | Cited by | United States of America | Pre-grant |
| US2002054109A1 | Cites | United States of America | Search report |
| US2002064280A1 | Cites | United States of America | Search report |
| US5258998A | Cites | United States of America | Search report |
| US5633932A | Cites | United States of America | Search report |
| US6894792B1 | Cites | United States of America | Search report |
| US6943907B1 | Cites | United States of America | Search report |
| US7003667B1 | Cites | United States of America | Search report |
| JPH06237389A | Cites | Japan | Applicant |
| JPH08314659A | Cites | Japan | Applicant |
3 members in 2 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 2000279796 | Japan | – | |
| 2000279796 | Japan | A | |
| 2000279796 | Japan | A | |
| 2000279796 | – | – | – |
| JP20000279796 | – | – | – |
Members3
| Document | Office | Kind | |
|---|---|---|---|
| US2002036790A1 | United States of America | A1 | |
| JP2002091742A | Japan | A | |
| US7271925B2This record | United States of America | B2 |
61 transactions on the USPTO file
Allowed after 3 non-final rejections, 1 final rejection and 1 RCE.
- Non-final rejections
- 3
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | |
|---|---|
| Expire Patent | |
| Maintenance Fee Reminder Mailed | |
| Recordation of Patent Grant Mailed | |
| Patent Issue Date Used in PTA CalculationAllowed | |
| Issue Notification MailedAllowed | |
| Dispatch to FDC | |
| Application Is Considered Ready for Issue | |
| Issue Fee Payment Verified | |
| Issue Fee Payment Received | |
| Mail Notice of AllowanceAllowed | |
| Mail Examiner's Amendment | |
| Notice of Allowance Data Verification CompletedAllowed | |
| Examiner's Amendment Communication | |
| Interview Summary Record | |
| Date Forwarded to Examiner | |
| Response after Non-Final Action | |
| Mail Non-Final RejectionNon-final rejection | |
| Non-Final RejectionNon-final rejection | |
| Case Docketed to Examiner in GAU | |
| Date Forwarded to Examiner | |
| Date Forwarded to Examiner | |
| Disposal for a RCE / CPA / R129 | |
| Request for Continued Examination (RCE) | |
| Workflow - Request for RCE - Begin | |
| Case Docketed to Examiner in GAU | |
| Mail Final Rejection (PTOL - 326)Final rejection | |
| Final RejectionFinal rejection | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Date Forwarded to Examiner | |
| New or Additional Drawing Filed | |
| Response after Non-Final Action | |
| Mail Non-Final RejectionNon-final rejection | |
| Non-Final RejectionNon-final rejection | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Date Forwarded to Examiner | |
| Request for Foreign Priority (Priority Papers May Be Included) | |
| New or Additional Drawing Filed | |
| Response after Non-Final Action | |
| Request for Extension of Time - Granted | |
| Mail Examiner Interview Summary (PTOL - 413) | |
| Interview Summary Record | |
| Mail Non-Final RejectionNon-final rejection | |
| Non-Final RejectionNon-final rejection | |
| IFW TSS Processing by Tech Center Complete | |
| Case Docketed to Examiner in GAU | |
| Miscellaneous Incoming Letter | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Application Dispatched from OIPE | |
| Application Is Now Complete | |
| Information Disclosure Statement considered | |
| Information Disclosure Statement (IDS) Filed | |
| Information Disclosure Statement (IDS) Filed | |
| Notice Mailed--Application Incomplete--Filing Date Assigned | |
| Correspondence Address Change | |
| IFW Scan & PACR Auto Security Review | |
| Request for Foreign Priority (Priority Papers May Be Included) | |
| Initial Exam Team nn |
8 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 07271925
- Publication, DOCDB
- 7271925
- Publication, EPODOC
- US7271925
- Application
- 9949615
- Application, DOCDB
- 94961501
- Application, EPODOC
- US20010949615
Titles
- English
- Recording medium for recording printing programs and printing system for confidential printing
Patent term adjustment
- A delay
- +1,015 daysthe office missed an examination deadline
- Applicant delay
- −28 days
- Net adjustment
- 987 days
Classification
- CPC, 1
- G06F21/608
- IPC, 4
- G06K15 00
- G06F3 12
- B41J5 30
- G06F21 00
- USPC, 2
- 358001140
- 358001150