Image processing system, image processing apparatus and image processing method
Claim Score by NHIP
Abstract
An image processing system includes: a document storage apparatus for storing document data therein; an image processing apparatus connected to the document storage apparatus via a network, for processing the document data in association with the document storage apparatus; a first authenticator for performing user authentication at the time of an access to the document storage apparatus; a second authenticator for performing user authentication at the time of an access to the image processing apparatus; and controller for controlling, based on an authentication result by at least one of the first authenticator and the second authenticator, an authenticating operation by the other authenticator.

Term
2.5 yearsto projected expiry
Projected expiry 22 March 2029, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
29 claims: 5 independent, 24 dependent
- 1An image processing system comprising:a document storage apparatus for storing document data therein;an image processing apparatus connected to the document storage apparatus via a network, for processing the document data in association with the document storage apparatus;a first authenticator for performing user authentication at the time of an access to the document storage apparatus;a second authenticator for performing user authentication at the time of an access to the image processing apparatus;and a controller for controlling, based on an authentication result by at least one of the first authenticator and the second authenticator, an authenticating operation by the other authenticator.
- 9An image processing system comprising:a terminal which uses an application program;an image processing apparatus connected to the terminal via a network, for executing processing according to a file processed by the use of the application program at the terminal;a first authenticator for performing user authentication when the application program is used;a second authenticator for performing user authentication when the image processing apparatus is used;and a controller for controlling an authenticating operation by the second authenticator based on an authentication result by the first authenticator .
- 12An image processing apparatus connected to a document storage apparatus for storing document data therein via a network, for processing the document data in association with the document storage apparatus, the image processing apparatus comprising:an authenticator for performing user authentication;and a controller for controlling an authenticating operation by the authenticator based on a result of the user authentication performed at the time of an access to the document storage apparatus.
- 19An image processing method comprising the steps of:first authenticating a user at the time of an access to a document storage apparatus for storing document data therein;second authenticating a user at the time of an access to an image processing apparatus connected to the document storage apparatus via a network, for processing the document data in association with the document storage apparatus;and controlling, based on an authentication result in at least one of the first authenticating step and the second authenticating step, the contents of the other authenticating step.
- 27Broadest claimClaim Score 85, broad(NHIP)An image processing method comprising the steps of:first authenticating a user at the time of the usage of an application program at a terminal;second authenticating a user at the time of the usage of an image processing apparatus connected to the terminal via a network, for executing processing according to a file processed by the use of the application program at the terminal;and controlling the contents of the second authenticating step based on an authentication result in the first authenticating step.
Independent claims5
203 paragraphs in 4 sections, as filed
0001This application claims priority under 35 U.S.C. § 119 to Japanese Patent Application No. P2004-288341 filed on Sep. 30, 2004, the entire disclosure of which is incorporated herein by reference in its entirety.
BACKGROUND OF THE INVENTION
00021. Field of the Invention
0003The present invention relates to an image processing system, an image processing apparatus and an image processing method, in which a user is authenticated when document data is processed by the use of an MFP (abbreviating a multi-function peripheral) serving as a multi-functional image forming apparatus equipped with the functions of, for example, a copying machine, a printer, a FAX, a scanner and the like or an image processing apparatus such as a printer.
00042. Description of the Related Art
0005The following description sets forth the inventor's knowledge of related art and problems therein and should not be construed as an admission of knowledge in the prior art.
0006In recent years, there has been prevailed an image processing apparatus such as an MFP or a printer, in which a department password or the like is input when the image processing apparatus is used in order to manage the billing by counting the number of printed sheets used per affiliation department.
0007The recent MFP has had the enhanced function of each of a FAX, a printer, a scanner and many functions for processing document data, and further, has had an increased mounted memory capacity. Therefore, the MFP can set a personal document data storing region in itself, so as to manage document data which has been personally used.
0008In the meantime, there have been prevailed services, for example, that more document data are shared within a department by storing document data or the like scanned by the MFP in a server, and that the billing is handled by storing document data or contents in a server installed on a side of a service provider and supplying the document data or the contents via a network.
0009Additionally, there have been increased situations in which multifaceted application programs for processing document data are provided and are used by a previously given license.
0010Moreover, there has been proposed a system capable of calling up documents stored in memories in other MFPs in an MFP activated at present in association with the other MFPs via a network.
0011According to the above-described environmental variations such as the reinforcement of the functions of the MFP, the prevalence of a document storage server, the provision of various application programs and the association with the other MFPs, it has been more necessary to reinforce the management of usage conditions of each of the functions of the MFP, the management of the stored documents, the management of an access to the document storage server and the management of usage conditions of document processing application programs in order to ensure the security.
0012Japanese Unexamined Patent Publication No. 373,070 (2002) discloses, as one of conventional systems for printing a document stored in a web server by accessing the web server from an MFP, a method in which upon inputting of web server authentication information and a document number in the MFP, a request to output a document corresponding to the document number is sent to the server from the MFP, and then, designated document data is transmitted to the MFP from the server, wherein a printing operation is performed by priority of other jobs by inputting the authentication information again in the case where the document data is printed in the MFP.
0013However, in the above-described prior art, a user must be authenticated twice, that is, at the time of the access to the document storage server and the printing operation in the MFP. Therefore, the user has been forced to input a user ID or a password every time, thereby inducing cumbersomeness from the viewpoint of the operation.
0014There has been a possibility that such a burden from the viewpoint of the operation further grows as a usage range of an image input/output function in the MFP is enlarged, and therefore, processing is performed in association with a plurality of servers or application programs or other MFPs.
0015The description herein of advantages and disadvantages of various features, embodiments, methods, and apparatus disclosed in other publications is in no way intended to limit the present invention. Indeed, certain features of the invention may be capable of overcoming certain disadvantages, while still retaining some or all of the features, embodiments, methods, and apparatus disclosed therein.
SUMMARY OF THE INVENTION
0016The preferred embodiments of the present invention have been developed in view of the above-mentioned and/or other problems in the related art. The preferred embodiments of the present invention can significantly improve upon existing methods and/or apparatuses.
0017Among other potential advantages, some embodiments can provide an image processing system capable of improving the operability of a user while ensuring the security of a document processing environment.
0018Among other potential advantages, some embodiments can provide an image processing apparatus which can be suitably used in the above-described system.
0019Among other potential advantages, some embodiments can provide an image processing method capable of improving the operability of a user while ensuring the security of a document processing environment.
0020According to a first aspect of a preferred embodiment of the present invention, an image processing system, comprises:
0021a document storage apparatus for storing document data therein;
0022an image processing apparatus connected to the document storage apparatus via a network, for processing the document data in association with the document storage apparatus;
0023a first authenticator for performing user authentication at the time of an access to the document storage apparatus;
0024a second authenticator for performing user authentication at the time of an access to the image processing apparatus; and
0025a controller for controlling, based on an authentication result by at least one of the first authenticator and the second authenticator, an authenticating operation by the other authenticator.
0026According to a second aspect of a preferred embodiment of the present invention, an image processing system, comprises:
0027a terminal which uses an application program;
0028an image processing apparatus connected to the terminal via a network, for executing processing according to a file processed by the use of the application program at the terminal;
0029a first authenticator for performing user authentication when the application program is used;
0030a second authenticator for performing user authentication when the image processing apparatus is used; and
0031a controller for controlling an authenticating operation by the second authenticator based on an authentication result by the first authenticator.
0032According to a third aspect of a preferred embodiment of the present invention, an image processing apparatus connected to a document storage apparatus for storing document data therein via a network, for processing the document data in association with the document storage apparatus, the image processing apparatus, comprises:
0033an authenticator for performing user authentication; and
0034a controller for controlling an authenticating operation by the authenticator based on a result of the user authentication performed at the time of an access to the document storage apparatus.
0035According to a fourth aspect of a preferred embodiment of the present invention, an image processing method, comprises the steps of:
0036first authenticating a user at the time of an access to a document storage apparatus for storing document data therein;
0037second authenticating a user at the time of an access to an image processing apparatus connected to the document storage apparatus via a network, for processing the document data in association with the document storage apparatus; and,
0038controlling, based on an authentication result in at least one of the first authenticating step and the second authenticating step, the contents of the other authenticating step.
0039According to a fifth aspect of a preferred embodiment of the present invention, an image processing method, comprises the steps of:
0040first authenticating a user at the time of the usage of an application program at a terminal;
0041second authenticating a user at the time of the usage of an image processing apparatus connected to the terminal via a network, for executing processing according to a file processed by the use of the application program at the terminal; and
0042controlling the contents of the second authenticating step based on an authentication result in the first authenticating step.
0043The above and/or other aspects, features and/or advantages of various embodiments will be further appreciated in view of the following description in conjunction with the accompanying figures. Various embodiments can include and/or exclude different aspects, features and/or advantages where applicable. In addition, various embodiments can combine one or more aspect or feature of other embodiments where applicable. The descriptions of aspects, features and/or advantages of particular embodiments should not be construed as limiting other embodiments or the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
0044The preferred embodiments of the present invention are shown by way of example, and not limitation, in the accompanying figures, in which:
0045<figref idref="DRAWINGS">FIG. 1</figref> is a diagram illustrating the arrangement of an image processing system in a preferred embodiment according to the invention;
0046<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating the electric arrangement of an MFP in the image processing system in the preferred embodiment according to the invention;
0047<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart illustrating processing to be executed by a document storage server in the case where document data and authentication information are individually transmitted;
0048<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating a sub-routine of an authenticating processing shown in <figref idref="DRAWINGS">FIG. 3</figref>;
0049<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating a sub-routine of a document displaying processing shown in <figref idref="DRAWINGS">FIG. 3</figref>;
0050<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating a sub-routine of a document selecting processing shown in <figref idref="DRAWINGS">FIG. 3</figref>;
0051<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating a sub-routine of an output destination determining processing shown in <figref idref="DRAWINGS">FIG. 3</figref>;
0052<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart illustrating a sub-routine of a user authentication information transmitting processing shown in <figref idref="DRAWINGS">FIG. 3</figref>;
0053<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart illustrating a sub-routine of a document transmitting processing shown in <figref idref="DRAWINGS">FIG. 3</figref>;
0054<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart illustrating a sub-routine of processing after a document is output, shown in <figref idref="DRAWINGS">FIG. 3</figref>;
0055<figref idref="DRAWINGS">FIG. 11</figref> is a flowchart illustrating processing to be executed by an image processing apparatus (i.e., the MFP);
0056<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart illustrating a sub-routine of an authenticating processing to be executed by the MFP shown in <figref idref="DRAWINGS">FIG. 11</figref>;
0057<figref idref="DRAWINGS">FIG. 13</figref> is a flowchart illustrating processing to be executed by the document storage server in the case where the document data and the authentication information are transmitted together with each other;
0058<figref idref="DRAWINGS">FIG. 14</figref> is a flowchart illustrating a sub-routine of a document transmitting processing shown in <figref idref="DRAWINGS">FIG. 13</figref>;
0059<figref idref="DRAWINGS">FIG. 15</figref> is a flowchart illustrating processing on the side of the image processing apparatus (i.e., the MFP);
0060<figref idref="DRAWINGS">FIG. 16</figref> is a flowchart illustrating a sub-routine of an authenticating processing to be executed by the MFP shown in <figref idref="DRAWINGS">FIG. 15</figref>;
0061<figref idref="DRAWINGS">FIG. 17</figref> is a flowchart illustrating an authenticating processing to be executed by a printer driver at a printing request for an MFP by the use of an application program;
0062<figref idref="DRAWINGS">FIG. 18</figref> is a diagram illustrating a screen for setting a printing mode by the printer driver;
0063<figref idref="DRAWINGS">FIG. 19</figref> is a diagram illustrating a first driver display screen;
0064<figref idref="DRAWINGS">FIG. 20</figref> is a diagram illustrating a second driver display screen;
0065<figref idref="DRAWINGS">FIG. 21</figref> is a diagram illustrating a general arrangement of an image processing system, in which MFPs are used;
0066<figref idref="DRAWINGS">FIG. 22</figref> is a diagram illustrating an example of a hardware configuration of the MFP used in <figref idref="DRAWINGS">FIG. 21</figref>; and
0067<figref idref="DRAWINGS">FIG. 23</figref> is a diagram illustrating an example of a functional configuration of the MFP used in <figref idref="DRAWINGS">FIG. 21</figref>.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
0068In the following paragraphs, some preferred embodiments of the invention will be described by way of example and not limitation. It should be understood based on this disclosure that various other modifications can be made by those in the art based on these illustrated embodiments.
0069<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating the arrangement of an image processing system in a preferred embodiment according to the invention.
0070In <figref idref="DRAWINGS">FIG. 1</figref>, in the image processing system, an MFP <b>21</b> exemplifying an image processing apparatus, a document storage server <b>22</b>, a personal authentication server <b>23</b> and a cellular mobile phone <b>25</b> serving as a user terminal, and a personal computer (hereinafter abbreviated as “a PC”) <b>50</b> serving as another user terminal are connected to each other via a network <b>51</b> (see <figref idref="DRAWINGS">FIG. 2</figref>).
0071In the host PC <b>50</b> is installed an application program <b>50</b><i>a </i>equipped with an authenticating function. An authenticator <b>50</b><i>b </i>is adapted to authenticate a user in using the program <b>50</b><i>a. </i>
0072Here, although there is shown an example in which the application program <b>50</b><i>a </i>is installed in the PC <b>50</b>, the application program <b>50</b><i>a </i>may be stored in an external server or the like, to be used by the host PC <b>50</b>. Otherwise, authentication information, which is obtained not only when the user is authenticated by the authenticator <b>50</b><i>b </i>in usage but also when the user is authenticated in installing the application program <b>50</b><i>b </i>in the host PC <b>50</b>, may be stored in the authenticator <b>50</b><i>b, </i>to be then read out in the usage.
0073The MFP <b>21</b> is a multi-functional image forming apparatus equipped with a copying function, a printing function, a facsimile function, a scanning function and the like, and includes therein an authenticator <b>21</b><i>a </i>having the function of individually managing users or departments which use the MFP <b>21</b>. The authenticator <b>21</b><i>a </i>serves as the second authenticating means when a user accesses the MFP <b>21</b> so as to use document data stored in the document storage server <b>22</b>.
0074A function limiting information storage <b>21</b><i>b </i>stores therein limiting information on each of functions which are set per account user.
0075The MFP <b>21</b> can be logged in from the cellular mobile phone <b>25</b> or the PC <b>50</b> of the user. Incidentally, the telephone rate of the cellular mobile phone <b>25</b> is collected by a cellular mobile phone company <b>27</b>.
0076The document storage server <b>22</b> stores therein the document data (which is a concept including image data) which can be used by the user. At the request from a user that he or she should intend to acquire the document data, the personal authentication server <b>23</b> serving as first authenticating means is allowed to perform an authenticating processing as to whether or not the user is a proper user (i.e., a previously permitted user) of the document storage server <b>22</b>. Furthermore, the authentication information obtained by the personal authentication server <b>23</b> and user identification information are designed to be transmitted to the MFP <b>21</b> after they are added or not added to the document data.
0077Incidentally, first authentication information includes, for example, an authentication result (i.e., a print permitting signal) and the user identification information.
0078<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating the electric arrangement of the MFP <b>21</b>.
0079In <figref idref="DRAWINGS">FIG. 2</figref>, a CPU <b>31</b> and a first memory <b>32</b> (i.e., a work memory) are connected to a bus <b>30</b> via a first bridge <b>33</b>.
0080The CPU <b>31</b> serving as a controller controls not only the entire operation of the MFP <b>21</b> but also an authenticating operation of the second authenticator <b>21</b><i>a </i>according to an authentication result obtained by the first authenticator (i.e., the personal authentication server) <b>23</b> in the present preferred embodiment. Specifically, the CPU <b>31</b> controls to prevent any second authentication in the case where authentication is established in the authentication server <b>23</b> serving as the first authenticator.
0081Moreover, the CPU <b>31</b> permits the user to use the MFP <b>21</b> within a range, in which the functions of the MFP <b>21</b> are limited, based on the added first authentication information.
0082Additionally, the CPU <b>31</b> performs a corresponding account processing in the case where the user identification information used for judging the authentication by the first authenticator (i.e., the personal authentication server) <b>23</b> exists as a destination of a user account in the MFP <b>21</b>: in contrast, the CPU <b>31</b> performs an account processing as a public user in the case where there exists no user identification information.
0083To the bus <b>30</b> are connected devices required for each of the data processing such as a memory controller <b>34</b>, a second bridge <b>37</b>, a raster interface (I/F) <b>41</b> with respect to a scanner <b>40</b>, an image processor <b>42</b> for converting R, G and B signals into Y, M, C and K signals and the authenticator <b>21</b><i>a </i>having a user account.
0084To the memory controller <b>34</b> is connected a second memory <b>35</b> serving as a file memory. To the second bridge <b>37</b> are connected a hard disk (i.e., an HDD) <b>38</b> and an operation panel <b>39</b>.
0085The document data (including the image data) scanned by the scanner <b>40</b> is transferred to the first memory <b>32</b> serving as a main memory through the bus <b>30</b> and the first bridge <b>33</b> via the raster I/F <b>41</b>. The data transferred to the first memory <b>32</b> is further transferred to the image processor <b>42</b> via the bus <b>30</b>, and then, is subjected to a necessary image processing, and finally, is returned to the first memory <b>32</b>.
0086Thereafter, the data is sent to a print engine <b>36</b> through the memory controller <b>34</b>, to be thus printed on a sheet.
0087The MFP <b>21</b> and a network <b>51</b> are connected to each other via an NIC (abbreviating “a network interface card”) <b>43</b>, so that the document data from the document storage server <b>22</b> or the like is received via the NIC <b>43</b> or the document data scanned by the scanner <b>40</b> is transmitted to the document storage server <b>22</b> via the NIC <b>43</b>.
0088In printing, print data is transferred to the first memory <b>32</b> via the NIC <b>43</b>. The transferred data is converted into bit map data, which can be read and printed by the CPU <b>31</b>, and then, is written in the first memory <b>32</b>.
0089The produced bit map data is processed by the image processor <b>42</b>, and thereafter, is transferred to the first memory <b>32</b> as the print data. After that, the print data is sent to the print engine <b>36</b> via the memory controller <b>34</b>.
0090Next, explanation will be made below on the outline of the operation of the image processing system in reference to <figref idref="DRAWINGS">FIG. 1</figref>. Here, the document data stored in the document storage server <b>22</b> is selected, and then, the selected document data is output to the MFP <b>21</b>.
0091(1) First, the user sends account information (i.e., personal information) to the document storage server <b>22</b> by the use of the cellular mobile phone <b>25</b> for the purpose of log-in.
0092(2) The document storage server <b>22</b> sends the sent account information to the personal authentication server <b>23</b>.
0093(3) The document storage server <b>22</b> obtains the user authentication and a user access authority with respect to requested document data from the personal authentication server <b>23</b>.
0094(4) The document storage server <b>22</b> permits the user to log in and access data based on the obtained authentication permissive information and data access authority.
0095(5) The user who can log in and access the data selects, from accessible data, document data which he or she intends to print in the MFP <b>21</b>.
0096Subsequently, a description will be given below of operation as next steps performed by the user, in which the selected document data is output to the designated MFP <b>21</b>, thereby obtaining a print output. Here, the MFP <b>21</b> is managed per department, so that only the user having an account can be permitted to use the MFP <b>21</b>.
0097(6) The user picks up MFP information such as an identification code displayed on the MFP <b>21</b> by using a camera function of the cellular mobile phone <b>25</b> in order to transmit the information on the MFP <b>21</b> as a destination to the document storage server <b>22</b>.
0098(7) The user transmits the picked-up MFP information to the document storage server <b>22</b>.
0099(8) The document storage server <b>22</b>, which has received the MFP information on the MFP <b>21</b> designated as the destination by the user, transmits a print permissive signal to the MFP <b>21</b>.
0100(9) Moreover, the document storage server <b>22</b> transmits the document data corresponding to the print permissive signal, selected by the user, thereby permitting the MFP <b>21</b> to perform a printing operation.
0101(10) The MFP <b>21</b> prints the document data transmitted from the document storage server <b>22</b>.
0102(11) After the completion of the printing operation, the MFP <b>21</b> transmits information on the number of printed sheets to the document storage server <b>22</b>.
0103(12) The document storage server <b>22</b> calculates a billing based on the print information transmitted from the MFP <b>21</b>, and then, transmits the billing to the personal authentication server <b>23</b> in association with the printed user information.
0104(13) The personal authentication server <b>23</b> transmits the personal information and the billing to a billing manager <b>24</b>, thereby giving the billing to the user. As a consequence, the user pays the charge together with the telephone rate to the cellular mobile phone company <b>27</b>.
0105In the case where the data is transmitted from the document storage server <b>22</b> to the MFP <b>21</b>, in which the department or account is managed, and then, is printed out, it has been conventionally necessary to perform authentication for logging in with respect to the MFP <b>21</b> again.
0106In contrast, according to the embodiment, once the authentication is established in the document storage server <b>22</b>, the authenticating operation in the MFP <b>21</b> can be omitted based on the authentication result, thus enhancing operability without any cumbersome work of inputting a password or ID twice by the user.
0107[Individual Transmission of Document Data and Authentication Information from Document Storage Server <b>22</b> to MFP <b>21</b>]
0108Next, processing on the side of the document storage server <b>22</b> will be described below in reference to a flowchart shown in <figref idref="DRAWINGS">FIG. 3</figref>. Incidentally, a step is abbreviated as “S” in the following description and drawings.
0109As shown in <figref idref="DRAWINGS">FIG. 3</figref>, the document storage server <b>22</b> performs an authenticating processing in S<b>101</b>, a document displaying processing in S<b>102</b>, a document selecting processing in S<b>103</b>, an output destination determining processing in S<b>104</b>, a user authentication information transmitting processing in S<b>105</b>, a document transmitting processing in S<b>106</b> and processing after document output in S<b>107</b>.
0110<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating a sub-routine of the authenticating processing (S<b>101</b>). In this authenticating processing, the user who requests the log-in is authenticated.
0111In <figref idref="DRAWINGS">FIG. 4</figref>, it is judged in S<b>1011</b> as to whether or not the log-in is requested for the document storage server <b>22</b>. If there is no log-in request (i.e., the judgment in S<b>1011</b> is NO), a routine is returned without performing any processing. In contrast, if there is a log-in request (i.e., the judgment in S<b>1011</b> is YES), information on the user who requests the log-in is obtained by acquiring log-in information in S<b>1012</b>.
0112In S<b>1013</b>, the authenticating processing, that is, the information on the user who requests the log-in is inquired of the personal authentication server <b>23</b>, and then, its result is obtained. In S<b>1014</b>, it is judged based on the obtained authentication result as to whether or not the document data can be accessed (i.e., permitted). If the document data can be accessed (i.e., the judgment in S<b>1014</b> is YES), an access condition, that is, an authority with respect to each of the document data on the user who requests the log-in is acquired in S<b>1015</b>. Here, the authority with respect to each of the document data signifies an authority for reading the document data, an authority for performing the printing operation, an authority for operating a file and the like.
0113In contrast, if the document data cannot be accessed (i.e., the judgment in S<b>1014</b> is NO), it reveals that the user does not have the log-in authority, so that no access is permitted in S<b>1016</b>, and then, the routine is returned.
0114<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating a sub-routine of the document displaying processing (S<b>102</b>). This document displaying processing is processing of displaying document data for the purpose of selection with respect to the user who requests the log-in.
0115In <figref idref="DRAWINGS">FIG. 5</figref>, it is judged in S<b>1021</b> as to whether or not there is a user who requests log-in at present. If there is a user who requests the log-in (i.e., the judgment in S<b>1021</b> is YES), it is judged in S<b>1022</b> as to whether or not the user requests document display. If the user requests the document display (i.e., the judgment in S<b>1022</b> is YES) in S<b>1023</b>, the document data in accordance with the access condition of the user who requests the log-in, which has been acquired in the authenticating processing in S<b>101</b>, is transmitted to the user who requests the log-in, and then, the routine is returned.
0116In contrast, if there is no user who requests the log-in (i.e., the judgment in S<b>1021</b> is NO), the routine is returned without performing any processing. Furthermore, if the user who requests the log-in does not request the document display (i.e., the judgment in S<b>1022</b> is NO), the routine is returned without performing any processing.
0117<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating a sub-routine of the document selecting processing (S<b>103</b>). In this document selecting processing, the user who requests the log-in selects the document data.
0118In <figref idref="DRAWINGS">FIG. 6</figref>, it is judged in S<b>1031</b> as to whether or not the user who requests the log-in requests the selection of the document data from the display data transmitted in the document displaying processing in S<b>102</b>. If there is a request for the selection of the document data (i.e., the judgment in S<b>1031</b> is YES), the document storage server <b>22</b> determines the document data selected by the user who requests the log-in and acquires that document data in S<b>1032</b>. Thereafter, the routine is returned. In contrast, if there is no request for the selection of the document data (i.e., the judgment in S<b>1031</b> is NO), the routine is returned without performing any processing.
0119<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating a sub-routine of the output destination determining processing (S<b>104</b>). In this output destination determining processing, the MFP <b>21</b> on the network <b>51</b> is specified based on output destination information transmitted from the user who requests the log-in.
0120In <figref idref="DRAWINGS">FIG. 7</figref>, it is judged in S<b>1041</b> as to whether or not the user who requests the log-in instructs the output destination of the selected document data. If there is an output destination instruction (i.e., the judgment in S<b>1041</b> is YES), output destination information (e.g., an IP address) is acquired in S<b>1042</b>. In S<b>1043</b>, a connection request is transmitted to the acquired connection destination, and then, the routine is returned.
0121In contrast, if there is no output destination instruction at present (i.e., the judgment in S<b>1041</b> is NO), it is judged in S<b>1044</b> as to whether or not an output destination response is waited. If no output destination response is waited (i.e., the judgment in S<b>1044</b> is NO), the routine is returned without performing any processing.
0122In contrast, if an output destination response is waited (i.e., the judgment in S<b>1044</b> is YES), it is judged in S<b>1045</b> as to whether or not a timeout occurs. In the case where there is no response from the connection destination after a lapse of a predetermined period of time, that is, the timeout occurs (i.e., the judgment in S<b>1045</b> is YES), it is determined in S<b>1046</b> that the connection cannot be carried out, and then, the routine is returned.
0123In contrast, if no timeout occurs, that is, there is a response from the output destination within the predetermined period of time (i.e., the judgment in S<b>1045</b> is NO), it is judged in S<b>1047</b> as to whether or not the connection is permitted. If the connection is permitted (i.e., the judgment in S<b>1047</b> is YES), the output destination is determined in S<b>1048</b>, and then, the routine is returned. In contrast, if the connection is not permitted (i.e., the judgment in S<b>1047</b> is NO), the routine is returned without performing any processing.
0124<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart illustrating a sub-routine of the user authentication information transmitting processing (S<b>105</b>). In this user authentication information transmitting processing, the authentication information on the user who logs in with respect to the document storage server <b>22</b> is transmitted to the MFP <b>21</b> as the output destination.
0125In <figref idref="DRAWINGS">FIG. 8</figref>, it is judged in S<b>1051</b> as to whether or not a transmission destination is determined. If the transmission destination is determined (i.e., the judgment in S<b>1051</b> is YES), it is judged in S<b>1052</b> as to whether or not the authentication information on the user who logged in has been already transmitted. If the authentication information has been already transmitted (i.e., the judgment in S<b>1052</b> is YES), the routine is returned without performing any processing.
0126In contrast, if the authentication information has not been transmitted yet (i.e., the judgment in S<b>1052</b> is NO), the user authentication information is transmitted to the transmission destination in S<b>1053</b>, and then, the routine is returned. Furthermore, if the transmission destination is not determined (i.e., the judgment in S<b>1051</b> is NO), the routine is returned without performing any processing.
0127<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart illustrating a sub-routine of the document transmitting processing (S<b>106</b>). In this document transmitting processing, the selected document data is transmitted.
0128In <figref idref="DRAWINGS">FIG. 9</figref>, it is judged in S<b>1061</b> as to whether or not the selected document data has-been already transmitted to the output destination. If the document data has been already transmitted (i.e., the judgment in S<b>1061</b> is YES), it is judged in S<b>1062</b> as to whether or not “a notice which notifies that the document data has been output” is delivered (i.e., received) from the output destination. If the notice is delivered (i.e., the judgment in S<b>1062</b> is YES), an output completing processing is performed in S<b>1063</b>, and then, the routine is returned. In contrast, if the notice has not been delivered yet (i.e., the judgment in S<b>1062</b> is NO), the routine is returned without performing any processing.
0129In contrast, if the document data has not been transmitted yet (i.e., the judgment in S<b>1061</b> is NO), it is judged in S<b>1064</b> as to whether or not the output destination responds to the user authentication information transmitted in the user authentication information transmitting processing in S<b>105</b>. If there is a response (i.e., the judgment in S<b>1064</b> is YES), the document data selected by the user is transmitted in S<b>1065</b>, and then, the routine is returned.
0130If there is no response (i.e., the judgment in S<b>1064</b> is NO), it is judged in S<b>1066</b> as to whether or not the timeout occurs at present. If no timeout occurs (i.e., the judgment in S<b>1066</b> is NO), the routine is returned without performing any processing. In contrast, if the timeout occurs (i.e., the judgment in S<b>1066</b> is YES), the transmission of the document data is stopped in S<b>1067</b>, and then, the routine is returned.
0131<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart illustrating a sub-routine of processing after the document output (S<b>107</b>). In this processing after the document output, post-processing in association with a data output such as the billing is performed in accordance with the output information acquired from the output destination.
0132In <figref idref="DRAWINGS">FIG. 10</figref>, it is judged in S<b>1071</b> as to whether or not processing after data output completion has been ended already. If the processing after the data output completion has been ended already (i.e., the judgment in S<b>1071</b> is YES), the routine is returned without performing any processing.
0133In contrast, if the processing after the data output completion has not been ended yet (i.e., the judgment in S<b>1071</b> is NO), it is judged in S<b>1072</b> as to whether or not an output completion notice is delivered from the data transmission destination. If the notice is delivered (i.e., the judgment in S<b>1072</b> is YES), the processing after the data output completion is executed in S<b>1073</b>, and then, the routine is returned. In contrast, if no notice is delivered (i.e., the judgment in S<b>1072</b> is NO), the routine is returned without performing any processing.
0134Next, a description will be given below of the processing in the MFP <b>21</b> as the output destination of the document data in reference to a flowchart shown in <figref idref="DRAWINGS">FIG. 11</figref>.
0135In <figref idref="DRAWINGS">FIG. 11</figref>, it is judged in S<b>201</b> as to whether or not there is an inquiry for determining the output destination from the document storage server <b>22</b> in the MFP <b>21</b>. If there is an inquiry (i.e., the judgment in S<b>201</b> is YES), a reply, for example, “an MFP which can output the data from the document storage server 22” is sent with respect to the inquiry in S<b>202</b>, the routine proceeds to S<b>203</b>. In contrast, if there is no inquiry (i.e., the judgment in S<b>201</b> is NO), the routine proceeds to S<b>203</b> without performing any processing.
0136In S<b>203</b>, it is judged as to whether or not the authentication information on the user who requests the data output-is received from the document storage server <b>22</b>. If the user authentication information is received (i.e., the judgment in S<b>203</b> is YES), the user account information stored in the MFP <b>21</b> is collated with the authentication information from the document storage server <b>22</b> in S<b>204</b>. Thereafter, the collation result is transmitted to the document storage server <b>22</b> in S<b>205</b>, and then, the routine proceeds to S<b>206</b>. If no user authentication information is received (i.e., the judgment in S<b>203</b> is NO), the routine proceeds to S<b>206</b>.
0137In S<b>206</b>, it is judged as to whether or not the document data is received from the document storage server <b>22</b>. If the document data is received (i.e., the judgment in S<b>206</b> is YES), the authentication condition on the user who requests the output is judged in S<b>207</b>. As a result, the routine proceeds to any one of processing, described below. In contrast, if no document data is received (i.e., the judgment in S<b>206</b> is NO), the routine proceeds to S<b>213</b>.
0138(1) The case where the user is authenticated by the document storage server <b>22</b> and the user account exists as account data stored in the MFP <b>21</b>.
0139(2) The case where the user is authenticated by the document storage server <b>22</b> and no user account exists as account data stored in the MFP <b>21</b>.
0140(3) The case where the document storage server <b>22</b> has no authenticating function or the user logs in as a guest user or an anonymous user even if the document storage server <b>22</b> has the authenticating function, wherein the guest user signifies a specified user whom “an owner” having all of control access authorities with respect to the MFP <b>21</b> gives an access authority, and further, the anonymous user signifies a user who is not the guest user but whom “the owner” gives an access authority.
0141The routine proceeds to S<b>208</b> in the case (1). The authentication in the MFP <b>21</b> is skipped, and thereafter, the printing operation is performed in accordance with the user account stored in the MFP <b>21</b> in S<b>211</b>.
0142The routine proceeds to S<b>209</b> in the case (2). The authentication in the MFP <b>21</b> is skipped, and thereafter, the printing operation is performed in accordance with a public user account in S<b>212</b>. Incidentally, in this case, the processing function by the MFP <b>21</b> is restricted (for example, the number of printed sheets is 10 or less) in comparison with the case in S<b>211</b> since security is degraded.
0143The routine proceeds to S<b>210</b> in the case (3). The authenticating processing with respect to the user who requests the log-in is performed on the operation panel <b>39</b> in the MFP <b>21</b>. This authenticating processing will be described later.
0144Subsequently, it is judged in S<b>213</b> as to whether or not the printing operation is completed. If the printing operation is completed (i.e., the judgment in S<b>213</b> is YES), a print completing processing is performed in S<b>214</b> for acquiring information on printing conditions and the number of printed sheets, and thereafter, the acquired print information is transmitted to the document storage server <b>22</b> in S<b>215</b>, thereby leading to an end. In contrast, if the printing operation is being performed or the print completing processing is finished (i.e., the judgment in S<b>213</b> is NO), the routine comes to an end without performing any processing.
0145<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart illustrating a sub-routine of the authenticating processing to be executed by the MFP <b>21</b> (S<b>210</b> shown in <figref idref="DRAWINGS">FIG. 11</figref>).
0146In <figref idref="DRAWINGS">FIG. 12</figref>, an authentication screen is displayed on the operation panel <b>39</b> in the MFP <b>21</b> in S<b>2101</b>. Thereafter, it is judged in S<b>2102</b> as to whether or not the account information is input. If the account information is input (i.e., the judgment in S<b>2102</b> is YES), the routine proceeds to S<b>2103</b>. In contrast, if no account information is input (i.e., the judgment in S<b>2102</b> is NO), the routine is returned without performing any processing.
0147It is judged in S<b>2103</b> as to whether or not there is an account in the MFP <b>21</b>. If there is an account in the MFP <b>21</b> (i.e., the judgment in S<b>2103</b> is YES), the printing operation is performed in S<b>2104</b>, and then, the routine is returned. Also in this case, the number of printed sheets may be restricted. In contrast, if there is no account in the MFP <b>21</b> (i.e., the judgment in S<b>2103</b> is NO), the authentication is prohibited in S<b>2105</b>, and then, the routine is returned.
0148As is clear from the above description, another authentication is skipped on the side of the MFP <b>21</b> in the case where the user is authenticated on the side of the document storage server <b>22</b>. As a consequence, the user need not input the user ID or the like again for the purpose of the authentication on the side of the MFP <b>21</b>, thus simplifying the operation.
0000[Simultaneous Transmission of Document Data and Authentication Information from Document Storage Server <b>22</b> to MFP <b>21</b>]
0149Processing on the side of the document storage server <b>22</b> in this case will be described below in reference to a flowchart shown in <figref idref="DRAWINGS">FIG. 13</figref>.
0150As shown in <figref idref="DRAWINGS">FIG. 13</figref>, the routine is ended after an authenticating processing in S<b>401</b>, a document displaying processing in S<b>402</b>, a document selecting processing in S<b>403</b>, an output destination determining processing in S<b>404</b>, a document transmitting processing in S<b>405</b> and processing after document output in S<b>406</b>.
0151Here, the contents of each of the authenticating processing in S<b>401</b>, the document displaying processing in S<b>402</b>, the document selecting processing in S<b>403</b>, the output destination determining processing in S<b>404</b> and the processing after the document output in S<b>406</b> are the same as those of each of the authenticating processing in S<b>101</b>, the document displaying processing in S<b>102</b>, the document selecting processing in S<b>103</b>, the output destination determining processing in S<b>104</b> and the processing after the document output in S<b>107</b> shown in <figref idref="DRAWINGS">FIG. 3</figref>, respectively. Therefore, the explanation on each of the contents will be omitted below.
0152As is obvious from the comparison between the flowcharts shown in <figref idref="DRAWINGS">FIGS. 3 and 13</figref>, the user authentication information transmitting processing in S<b>105</b> shown in <figref idref="DRAWINGS">FIG. 3</figref> can be omitted in the case of simultaneous transmission of first authentication information and document data. The authentication result is received together with the received document data in the MFP <b>21</b>.
0153<figref idref="DRAWINGS">FIG. 14</figref> is a flowchart illustrating a sub-routine of the document transmitting processing (S<b>405</b>). In the document transmitting processing, a selected document is transmitted.
0154In <figref idref="DRAWINGS">FIG. 14</figref>, it is judged in S<b>4051</b> as to whether or not the selected document data has been already transmitted to the output destination. If the document data has been already transmitted (i.e., the judgment in S<b>4051</b> is YES), it is judged in S<b>4052</b> as to whether or not “a notice which notifies that the document data has been output” is delivered (i.e., received) from the output destination. If the notice is delivered (i.e., the judgment in S<b>4052</b> is YES), an output completing processing is performed in S<b>4053</b>, and then, the routine is returned. In contrast, if no notice is delivered (i.e., the judgment in S<b>4052</b> is NO), the routine is returned without performing any processing.
0155In contrast, if the document data has not been transmitted yet (i.e., the judgment in S<b>4051</b> is NO), it is judged in S<b>4054</b> as to whether or not the output destination is determined. If the output destination is determined (i.e., the judgment in S<b>4054</b> is YES), the selected document data is added with authentication data in S<b>4055</b>. Thereafter, the data are transmitted in S<b>4056</b>, and then, the routine is returned.
0156In contrast, if the output destination is not determined (i.e., the judgment in S<b>4054</b> is NO), it is judged in S<b>4057</b> as to whether or not the timeout occurs at present. If no timeout occurs (i.e., the judgment in S<b>4057</b> is NO), the routine is returned without performing any processing. In contrast, if the timeout occurs (i.e., the judgment in S<b>4057</b> is YES), the transmission of the data is stopped in S<b>4057</b>, and then, the control routine is returned.
0157In this manner, the authentication data can be transmitted in addition to the document data.
0158Next, processing in the MFP <b>21</b> as the output destination of the document data will be described below in reference-to a flowchart shown in <figref idref="DRAWINGS">FIG. 15</figref>.
0159In <figref idref="DRAWINGS">FIG. 15</figref>, it is judged in S<b>501</b> as to whether or not there is an inquiry for determining the output destination from the document storage server <b>22</b> in the MFP <b>21</b>. If there is an inquiry (i.e., the judgment in S<b>501</b> is YES), a reply, for example, “an MFP which can output the data from the document storage server 22” is sent with respect to the inquiry in S<b>502</b>, the routine proceeds to S<b>503</b>. In contrast, if there is no inquiry, the routine proceeds to S<b>503</b> without performing any processing.
0160In S<b>503</b>, it is judged as to whether or not the document data added with the authentication data is received from the document storage server <b>22</b>. If the document data is received (i.e., the judgment in S<b>503</b> is YES), the authentication information is taken out of the received data in S<b>504</b>. Thereafter, the authenticating processing is performed in S<b>505</b>, and then, the routine proceeds to S<b>506</b>. The authenticating processing will be described later. If the document data is not received (i.e., the judgment in S<b>503</b> is NO), the routine proceeds to S<b>506</b> without performing any processing.
0161It is judged in S<b>506</b> as to whether or not the printing operation is completed. If the printing operation is completed (i.e., the judgment in S<b>506</b> is YES), a print completing processing is performed in S<b>507</b> for acquiring information on printing conditions and the number of printed sheets.
0162Thereafter, the acquired print information is transmitted to the document storage server <b>22</b> in S<b>508</b>, thereby leading to an end. In contrast, if the printing operation is being performed or the print completing processing is finished (i.e., the judgment in S<b>506</b> is NO), the routine comes to an end without performing any processing.
0163<figref idref="DRAWINGS">FIG. 16</figref> is a flowchart illustrating a sub-routine of the authenticating processing to be executed by the MFP <b>21</b> (S<b>505</b> shown in <figref idref="DRAWINGS">FIG. 15</figref>).
0164In <figref idref="DRAWINGS">FIG. 16</figref>, it is judged in S<b>5101</b> as to whether or not the authentication information added to the document data includes account information. If the authentication information includes the account information (i.e., the judgment in S<b>5051</b> is YES), the routine proceeds to S<b>5052</b>. In contrast, if the authentication information includes no account information (i.e., the judgment in S<b>5051</b> is NO), the routine is returned without performing any processing.
0165It is judged in S<b>5052</b> as to whether or not there is an account in the MFP <b>21</b>. If there is an account in the MFP <b>21</b> (i.e., the judgment in S<b>5052</b> is YES), the printing operation is performed in S<b>5053</b>, and then, the routine is returned. In contrast, if there is no account in the MFP <b>21</b> (i.e., the judgment in S<b>5052</b> is NO), the authentication is prohibited in S<b>5054</b>, and then, the routine is returned.
0166As described above, also in the case where the authentication information and the document data are transmitted together with each other by adding the authentication information to the document data, when the added authentication information includes the account information, which is stored also in the MFP <b>21</b>, the user can use the function of the MFP <b>1</b> even without another authentication on the side of the MFP <b>21</b>.
0167Next, explanation will be made below on another preferred embodiment according to the invention. In the present preferred embodiment, another authentication is omitted during usage of an MFP <b>21</b> on a PC <b>50</b> serving as a user terminal based on authentication information input by a user when an application program is started (i.e., used).
0168<figref idref="DRAWINGS">FIG. 17</figref> illustrates a flow of processing.
0169A printer driver installed in the PC <b>50</b> executes an authenticating processing shown in <figref idref="DRAWINGS">FIG. 17</figref> as one of processing at a request of a printing operation in accordance with the application program. This authenticating processing is executed upon depressing an “OK” button <b>392</b> on a printing mode setting screen <b>391</b> of the printer driver shown in <figref idref="DRAWINGS">FIG. 18</figref>.
0170In <figref idref="DRAWINGS">FIG. 17</figref>, the printer driver acquires, in S<b>601</b>, the authentication information input at the start of the application program by the user in accordance with the application program which has been instructed to perform the printing operation. It is judged in S<b>602</b> as to whether or not the authentication information is acquired from the application program. If the authentication information is acquired (i.e., the judgment in S<b>602</b> is YES), the authentication information is inquired (i.e., the authentication is confirmed) with respect to the MFP <b>21</b> in S<b>603</b>.
0171Subsequently, it is judged in S<b>604</b> as to whether or not there is authentication information from the MFP <b>21</b>. If there is authentication information (i.e., the judgment in S<b>604</b> is YES), the processing is branched.
0172(1) The case where the authentication information acquired in accordance with the application program is included in an account stored in the MFP <b>21</b>:
0173In this case, a first driver display having an authentication screen <b>393</b> shown in <figref idref="DRAWINGS">FIG. 19</figref> is displayed in S<b>605</b>. As shown, on the screen are displayed connection in accordance with an account acquired based on the application program and the function of the MFP <b>21</b> which can be used in accordance with this account. If the user satisfies the displayed account, he or she merely executes a next processing. In contrast, if the user requires connection in accordance with another account because of the function restriction of the MFP <b>21</b>, a mark in a check box shown in <figref idref="DRAWINGS">FIG. 19</figref> may be cleared such that another account is input.
0174(2) The case where the authentication information acquired in accordance with the application program is not included in the account stored in MFP <b>21</b>:
0175If it is judged that the authentication information cannot be taken out of the application program (i.e., the judgment in S<b>602</b> is NO) or if there is no authentication information from the MFP <b>21</b> (i.e., the judgment in S<b>604</b> is NO), a second driver display having an authentication screen <b>394</b> shown in <figref idref="DRAWINGS">FIG. 20</figref> is displayed in S<b>606</b>, thereby promoting an account input.
0176Also in the present preferred embodiment, another inputting operation of the user ID or password can be omitted during the usage of the MFP <b>21</b> by using the authentication information obtained when the application program is started, thus enhancing operability.
0177Although the preferred embodiments according to the invention have been described above, the invention is not limited to those preferred embodiments. For example, the invention encompasses the following preferred embodiments:
0178(1) The first preferred embodiment has been exemplified by that a second log-in can be omitted in the MFP <b>21</b> when the document storage server <b>22</b> is first logged in, the document is selected from the document storage server <b>22</b>, and then, the transmission to the MFP <b>21</b> leads to the printing operation. However, the log-in in the document storage server <b>22</b> may be omitted in the case where the MFP <b>21</b> is first logged in, the document is scanned, and finally, the scanned document is transmitted to and stored in the document storage server <b>22</b>. It is to be understood that the document to be transmitted from the MFP <b>21</b> should be not only the scanned document but also a document stored in a box in advance.
0179(2) The second preferred embodiment has been exemplified by that the file created in accordance with the application program in the host PC <b>50</b> is transmitted to the MFP <b>21</b>, to be then printed. However, the log-in in the MFP <b>21</b> may be omitted in the case where the file created in the host PC <b>50</b> is transmitted to the MFP <b>21</b>, to be then transmitted to the outside from the MFP <b>21</b> via a FAX by the use of a PC-FAX function. Furthermore, the processing in the MFP <b>21</b> is not limited to this. For example, a document stored in a box in the MFP <b>21</b> in advance may be coupled to an application file, or the application file created in the PC <b>50</b> may be converted by using a file format converting function or a compressing function possessed by the MFP <b>21</b>.
0180Moreover, in the above-described preferred embodiments, the MFP <b>21</b> serving as a multi-functional image forming apparatus is used as the image processing apparatus. However, the image processing apparatus may be a printer having only a printing function or a router.
0181In addition, the document storage server <b>22</b> has functioned as a document storage apparatus in the preferred embodiment shown in <figref idref="DRAWINGS">FIG. 1</figref>. However, in the case where the image forming apparatus such as the MFP is used as a document processing apparatus such that document data is transmitted or received between the MFPs, an authenticating operation of at least one of first authenticator and second authenticator may be controlled based on an authentication result of the other authenticator.
0182<figref idref="DRAWINGS">FIG. 21</figref> is a diagram illustrating a general arrangement of an image processing system, in which MFPs <b>101</b> as described above are used; <figref idref="DRAWINGS">FIG. 22</figref> is a diagram illustrating an example of a hardware configuration of the MFP <b>101</b>; and <figref idref="DRAWINGS">FIG. 23</figref> is a diagram illustrating an example of a functional configuration of the MFP <b>101</b>.
0183As shown in <figref idref="DRAWINGS">FIG. 1</figref>, an image processing system <b>100</b> is constituted of a plurality of MFPs <b>101</b> (<b>101</b>A, <b>101</b>B, <b>101</b>C . . . ), a communication line <b>102</b> and the like. Examples of the communication line <b>102</b> include a LAN, the Internet, a special line and a public line. These MFPs <b>101</b> are connected to each other via the communication line <b>102</b>.
0184Each of the MFPs <b>101</b> is constituted of a control unit <b>111</b>, a print unit <b>112</b>, an image reading unit <b>113</b> and the like, as shown in <figref idref="DRAWINGS">FIG. 22</figref>. The MFP <b>101</b> comprehensively has the functions of a copying machine, a printer, a scanner, a FAX, a document server, and the like.
0185“The document server” functions to give a personal box to each of users or groups, so as to store and manage document data such as an image file in the personal box, to which each of the users or groups belongs. It is also referred to as “a box function”. “The personal box” is a storage region, in which the document data is to be stored, and therefore, it corresponds to “a folder” or “a directory” in a personal computer, which is provided in a hard disk <b>111</b><i>c. </i>An access authority is set with respect to the personal box or data to be stored in the personal box, which can be used by other users accordingly. Hereinafter, the personal box is simply referred to as “the box”.
0186The image reading unit <b>113</b> is constituted of a document table, an image sensor such as a CCD, an automatic document feeder and the like. The image reading unit <b>113</b> optically reads an image of a document, converts it into a digital data, and thus, creates image data. In other words, the image reading unit <b>113</b> is a scanner. The print unit <b>112</b> is a printing device (i.e., a printer or an engine) of a laser type or an ink jet type, for printing the image on a predetermined sheet based on print data.
0187The control unit <b>111</b> is constituted of a controller <b>111</b><i>a, </i>an operation panel <b>111</b><i>b, </i>the hard disk (i.e., the HDD) <b>111</b><i>c, </i>an image processor <b>111</b><i>d, </i>a network interface <b>111</b><i>e, </i>a printer interface <b>111</b><i>f, </i>a scanner interface <b>111</b><i>g </i>and the like, thus controlling the print unit <b>112</b>, the image reading unit <b>113</b> and the like.
0188The network interface <b>111</b><i>e </i>is an interface for transmitting or receiving the data to or from another MFP <b>101</b> via the communication line <b>102</b>. As the network interface <b>111</b><i>e </i>is used a network card (in particular, a network interface card) or a modem. The printer interface <b>111</b><i>f </i>and the scanner interface <b>111</b><i>g </i>are interfaces to be connected to the print unit <b>112</b> and the image reading unit <b>113</b>, respectively.
0189The operation panel <b>111</b><i>b </i>is a user interface (abbreviated as “a UI”) for the user of the MFP <b>101</b>, and is constituted of a liquid crystal display, an operation unit and the like. The liquid crystal display is adapted to display an operation screen or a setting screen. The operation unit includes buttons or keys such as ten keys and a start button. As the operation panel <b>111</b><i>b </i>may be used a touch panel. The user can store the data in the box provided in his or her MFP <b>101</b> or another MFP <b>101</b> or can utilize the data stored already by operating the operation panel <b>111</b><i>b. </i>
0190The image processor <b>111</b><i>d </i>performs the processing of correcting such as image color correction, up-down correction or inclination correction, the processing of converting image data or facsimile data written in a page description language corresponding to the MEP <b>101</b> into bit map data, and the processing of converting the image data obtained by the image reading unit <b>113</b> or the like into the image data or facsimile data written in the page description language.
0191The controller <b>111</b> is constituted of a circuit for controlling a CPU, a RAM and component parts such as the MFP <b>101</b>. In the hard disk <b>111</b><i>c </i>are stored programs for an operating system (abbreviated as “an OS”) and firmware or data. The firmware includes programs for implementing the function of each of a system controller <b>131</b>, a network controller <b>132</b>, an engine controller <b>133</b>, a scanner controller <b>134</b>, a hard disk controller <b>135</b>, a user interface controller <b>136</b> and a management data producer <b>137</b>, as shown in <figref idref="DRAWINGS">FIG. 23</figref>, in addition to programs for executing the processing relevant to the function of each of the copying machine, the printer, the scanner, the FAX and the document server, that is, the basic functions of the MFP <b>101</b>. These programs or data are loaded into the RAM, as required, to be thus executed by the CPU.
0192All or a part of the programs may be stored in the ROM or a non-volatile memory. Alternatively, all or a part of the functions of the component parts shown in <figref idref="DRAWINGS">FIG. 23</figref> may be configured in such a manner as to be implemented by a processor (i.e., a controlling circuit).
0193Hereinafter, a description will be given of the processing contents of each of the component parts shown in <figref idref="DRAWINGS">FIG. 23</figref> by way of an example in which the user uses the document data stored in each of the MFPs <b>101</b> installed in the image processing system <b>100</b> by operating the MFP <b>101</b>A.
0194The system controller <b>131</b> transmits and receives the data to and from each of the network controller <b>132</b>, the engine controller <b>133</b>, the scanner controller <b>134</b>, the hard disk controller <b>135</b>, the user interface controller <b>136</b> and the management data producer <b>137</b>. That is to say, the system controller <b>131</b> controls the entire MFP <b>101</b>.
0195The user interface controller <b>136</b> performs the processing of displaying a log-on screen HG<b>1</b>, a box selecting screen HG<b>2</b> and a document selecting screen HG<b>3</b> on the display screen of the operation panel <b>111</b><i>b. </i>Furthermore, the user interface controller <b>136</b> performs the processing of detecting a position on the display screen of the operation panel <b>111</b><i>b, </i>which is touched (i.e., depressed). These screens are displayed according to the operation by the user in accordance with the following procedures.
0196When the user selects a document list menu on menu screens, not shown, the user interface controller <b>136</b> performs the processing of displaying the log-on screen HG<b>1</b>. Here, the user inputs his or her user ID and password in the text boxes, respectively, by depressing any of buttons displayed on the screen.
0197And then, the network controller <b>132</b> requests the other MFPs <b>101</b> (i.e., <b>101</b>B, <b>101</b>C . . . ) to transmit information relevant to management of a document. At this time, the input user ID and password are transmitted and noticed to each of the MFPs <b>101</b>.
0198The MFP <b>101</b> which accepts the request authenticates the user based on the user ID and password which have been transmitted together with each other. If the user can be confirmed to be proper, document information <b>171</b> representing a document name, a creation date and time, the number of pages, a creator, a stored box and the like of each of the documents stored in the box provided in the MFP <b>10</b>.<b>1</b> and access authority information <b>172</b> representing an access authority to each of the documents, given to the user, are transmitted to the MFP <b>101</b>A, from which the request has been sent.
0199The network controller <b>132</b> in the MFP <b>101</b>A receives document information <b>171</b> and access authority information <b>172</b> from another MFP <b>101</b>. Moreover, the hard disk controller <b>135</b> reads the document information <b>171</b> on each of the documents stored in the box provided in the MFP <b>101</b>A and the access authority information <b>172</b> on the user. And then, the management data producer <b>137</b> produces management data <b>173</b> based on the received or read information. In other words, since the authentication has been already recognized by the MFP <b>101</b>, no authentication is performed in the MFP <b>101</b>A.
0200Management data <b>173</b> includes document identification information and access restriction information. The document identification information is based on the document information <b>171</b>: in contrast, the access restriction information is based on the access authority information <b>172</b>.
0201While the present invention may be embodied in many different forms, a number of illustrative embodiments are described herein with the understanding that the present disclosure is to be considered as providing examples of the principles of the invention and such examples are not intended to limit the invention to preferred embodiments described herein and/or illustrated herein.
0202While illustrative embodiments of the invention have been described herein, the present invention is not limited to the various preferred embodiments described herein, but includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., of aspects across various embodiments), adaptations and/or alterations as would be appreciated by those in the art based on the present disclosure. The limitations in the claims are to be interpreted broadly based on the language employed in the claims and not limited to examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive. For example, in the present disclosure, the term “preferably” is non-exclusive and means “preferably, but not limited to.” In this disclosure and during the prosecution of this application, means-plus-function or step-plus-function limitations will only be employed where for a specific claim limitation all of the following conditions are present in that limitation: a) “means for” or “step for” is expressly recited; b) a corresponding function is expressly recited; and c) structure, material or acts that support that structure are not recited. In this disclosure and during the prosecution of this application, the terminology “present invention” or “invention” may be used as a reference to one or more aspect within the present disclosure. The language present invention or invention should not be improperly interpreted as an identification of criticality, should not be improperly interpreted as applying across all aspects or embodiments (i.e., it should be understood that the present invention has a number of aspects and embodiments), and should not be improperly interpreted as limiting the scope of the application or claims. In this disclosure and during the prosecution of this application, the terminology “embodiment” can be used to describe any aspect, feature, process or step, any combination thereof, and/or any portion thereof, etc. In some examples, various embodiments may include overlapping features. In this disclosure and during the prosecution of this case, the following abbreviated terminology may be employed: “e.g.” which means “for example;” and “NB” which means “note well.”
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 |
|---|---|---|---|
| US2015244902A1 | Cited by | United States of America | Pre-grant |
| US2012158873A1 | Cited by | United States of America | Pre-grant |
| US11575670B2 | Cited by | United States of America | Search report |
| US10171705B2 | Cited by | United States of America | Applicant |
| US10498927B2 | Cited by | United States of America | Applicant |
| US9172845B2 | Cited by | United States of America | Search report |
| US2010235898A1 | Cited by | United States of America | Pre-grant |
| US9307117B2 | Cited by | United States of America | Applicant |
| US2021176242A1 | Cited by | United States of America | Search report |
| US2008174813A1 | Cited by | United States of America | Pre-grant |
| US11064090B2 | Cited by | United States of America | Applicant |
| US2009174900A1 | Cited by | United States of America | Pre-grant |
| US8255784B2 | Cited by | United States of America | Search report |
| US8392974B2 | Cited by | United States of America | Applicant |
| US2010235904A1 | Cited by | United States of America | Pre-grant |
| US2008047020A1 | Cited by | United States of America | Pre-grant |
| JP2008011220A | Cited by | Japan | Search report |
| US10097704B2 | Cited by | United States of America | Applicant |
| US2008057907A1 | Cited by | United States of America | Pre-grant |
| US8505082B2 | Cited by | United States of America | Applicant |
| US9195421B2 | Cited by | United States of America | Search report |
| US9699356B2 | Cited by | United States of America | Applicant |
| US2015178026A1 | Cited by | United States of America | Pre-grant |
| US9641473B2 | Cited by | United States of America | Search report |
| US10223048B2 | Cited by | United States of America | Search report |
| US2002169961A1 | Cites | United States of America | Pre-grant |
| US2004010701A1 | Cites | United States of America | Pre-grant |
| US2004030700A1 | Cites | United States of America | Pre-grant |
| US6163383A | Cites | United States of America | Pre-grant |
| US6421582B1 | Cites | United States of America | Pre-grant |
| US6559967B1 | Cites | United States of America | Pre-grant |
| US6802000B1 | Cites | United States of America | Pre-grant |
| US6859794B2 | Cites | United States of America | Pre-grant |
4 members in 2 offices
Priority claims4
| Document | Office | Kind | Date |
|---|---|---|---|
| 2004288341 | Japan | – | |
| 2004288341 | Japan | A | |
| 2004288341 | – | – | – |
| JP20040288341 | – | – | – |
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2006069918A1 | United States of America | A1 | |
| JP2006102948A | Japan | A | |
| JP4277779B2 | Japan | B2 | |
| US7984481B2 | United States of America | B2 |
66 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Mail Examiner's AmendmentMEX.A | MEX.A | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Affidavit(s) (Rule 131 or 132) or Exhibit(s) ReceivedAF/D | AF/D | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Withdraw Flagged for 5/25W525 | W525 | |
| Flagged for 5/25F525 | F525 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Request for Foreign Priority (Priority Papers May Be Included)RQPR | RQPR | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Initial Exam Team nnIEXX | IEXX |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 20060069918
- Publication, DOCDB
- 2006069918
- Publication, EPODOC
- US2006069918
- Application
- 11232894
- Application, DOCDB
- 23289405
- Application, EPODOC
- US20050232894
Titles
- English
- Image processing system, image processing apparatus and image processing method
Patent term adjustment
- A delay
- +983 daysthe office missed an examination deadline
- B delay
- +650 dayspendency past three years
- Overlap
- −181 daysdelays counted once
- Applicant delay
- −176 days
- Net adjustment
- 1,276 days
Classification
- CPC, 13
- H04N1/00307
- G06F21/40
- G06F21/608
- H04L63/08
- H04N1/00209
- H04N1/00244
- H04N1/2179
- H04N1/2191
- H04N1/4413
- H04N1/4426
- H04N1/4433
- H04N2201/0087
- H04N2201/0094
- IPC, 1
- H04L9 00
- USPC, 1
- 713176000