Source: http://www.google.com/patents/US20050044248?dq=5920316
Timestamp: 2016-07-24 22:37:36
Document Index: 607162634

Matched Legal Cases: ['art 112', 'art 112', 'art 112', 'art 112', 'art 112', 'art 112', 'art 112']

Patent US20050044248 - User authentication method, image forming apparatus, and user authentication ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA user authentication method is applicable to an image forming apparatus connectable via a network to an authentication apparatus that performs authentication of a user and including authentication set information that sets whether to perform authentication in the authentication apparatus. The user authentication...http://www.google.com/patents/US20050044248?utm_source=gb-gplus-sharePatent US20050044248 - User authentication method, image forming apparatus, and user authentication programAdvanced Patent SearchPublication numberUS20050044248 A1Publication typeApplicationApplication numberUS 10/891,154Publication dateFeb 24, 2005Filing dateJul 15, 2004Priority dateJul 24, 2003Also published asEP1501002A2, EP1501002A3Publication number10891154, 891154, US 2005/0044248 A1, US 2005/044248 A1, US 20050044248 A1, US 20050044248A1, US 2005044248 A1, US 2005044248A1, US-A1-20050044248, US-A1-2005044248, US2005/0044248A1, US2005/044248A1, US20050044248 A1, US20050044248A1, US2005044248 A1, US2005044248A1InventorsSachiko Mihira, Tatsuo ItoOriginal AssigneeSachiko Mihira, Tatsuo ItoExport CitationBiBTeX, EndNote, RefManPatent Citations (16), Referenced by (112), Classifications (11), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetUser authentication method, image forming apparatus, and user authentication program
The “ABCDEFG=” is an example, which indicates whether or not the user is authenticated. [0152] Next, referring to the sequence diagram of FIG. 13, a description is given below of processes in which the user who has logged in performs copying and logs out. [0153] In step S201, the operation panel 53 notifies the copy application 21 of a copy start request. [0154] In step S202, the copy application 21 notifies the LCS 39 of starting of copying. On this occasion, the user information, a job ID, and print information set by the user are also provided to the LCS 39. The set information is, for example, information related to printing such as color copying. [0155] In step S203, the copy application 21 notifies the operation panel 53 of a copy reception screen display request. Thereby, copying is performed. [0156] When copying ends, the copy application 21 notifies the LCS 39 in step S204 that the copying ends. On this occasion, the user information, the job ID, the print information of actual output are provided to the LCS 39. Additionally, in step S205, the copy application 21 notifies the operation panel 53 of a copying end screen display request. [0157] Then, when the user presses down the logout button 119 (see FIG. 7), the operation panel 53 notifies the copy application 21 in step S206 of a logout request. In step S207, the copy application 21 notifies the CCS 38 of a ticket destroy request together with an authentication ticket. In step S208, the CCS 38 notifies the LCS 39 of a logout notice together with the user information, and the process ends. [0158] In the aforementioned processes, the user who has logged in performs copying and logs out. [0159] A description is given below of processes in the case where the user directory WS 93 is used in the aforementioned processes. The user directory WS 93 is used in the usage limitation confirmation request in step S110 of FIG. 8. [0160] Referring to the sequence diagram of FIG. 14, a specific description is given of the processes in the above-mentioned case. [0161] It should be noted that the sequence diagram of FIG. 14 only shows processes corresponding to steps S110 and S111 of FIG. 8, since the sequence diagram of FIG. 14 shows the processes in the case where the usage limitation confirmation request in step S110 of FIG. 8 is performed by using the user directory WS 93. [0162] The sequence diagram of FIG. 14 is described below. In step S301, the copy application 21 notifies the UCS 36 of the usage limitation confirmation request. On this occasion, the user information and the application name are also provided to the UCS 36. [0163] In step S302, the UCS 36 notifies the WSC 83 of the request transmission request. On this occasion, in a case where the usage limitation of the user is performed by the copy application 21 or the UCS 36, the user information, the URL of the user directory WS 93, and a method name of the WS are also provided to the WSC 83. Additionally, in a case where the usage limitation of the user is performed by the user directory WS 93, the user information, a machine name, the application name, the URL of the user directory WS 93, and a method name of the WS are provided to the WSC 83. Here, the machine name is information specifying the multi-functional apparatus 100, and may be the IP address of the multi-functional apparatus 100, for example. [0164] In step S303, the WSC 83 notifies the user directory WS 93 of the usage limitation confirmation request. The usage limitation confirmation request is provided in a SOAP message. In a case where the usage limitation of the user is performed by the copy application 21 or the UCS 36, the information provided with the usage limitation confirmation request is the user information. Additionally, in a case where the usage limitation of the user is performed by the user directory WS 93, the information provided with the usage limitation confirmation request is the user information, the machine name, and the application name. [0165] In step S304, the response to the usage limitation confirmation request in step S303 is provided to the WSC 83 in a SOAP message. In a case where the usage limitation of the user is performed by the copy application 21 or the UCS 36, the information provided in step S304 is the user information. Additionally, in a case where the usage limitation of the user is performed by the user directory WS 93, the information provided in step S304 is permission for execution by the user. [0166] In step S305, the WSC 83 notifies the UCS 36 of the information transmitted from the user directory WS 93. In a case where the usage limitation of the user is performed by the copy application 21 or the UCS 36, the information provided in step S305 is the user information. Additionally, in a case where the usage limitation of the user is performed by the user directory WS 93, the information provided in step S305 is permission for execution by the user. [0167] In step S306, the UCS 36 notifies the copy application 21 of the response to the usage limitation confirmation request in step S301. In a case where the usage limitation of the user is performed by the copy application 21, the information provided in step S306 is the user information. Additionally, in a case where the usage limitation of the user is performed by the UCS 36 or the user directory WS 93, the information provided in step S306 is permission for execution by the user. [0168] In the aforementioned manner, the processes in the case where the user directory 93 is used are performed. [0169] Next, a description is given below of processes in the case where the user does not log out after performing copying as mentioned above and subsequently uses the FAX function. The description is given with reference to interfaces (operation panels) 150 through 153 shown in FIG. 15. In FIG. 15, those parts that are the same as those corresponding parts in FIG. 7 are designated by the same reference numerals, and a description thereof is omitted. [0170] First, the operation panel 150 is the login screen, which is described above with reference to FIG. 7. When the user logs in, the login screen makes a transition to a screen that allows copying as shown in the display part 112 of the operation panel 151. Thus, it is possible for the user to perform copying. [0171] Then, when the user presses down the FAX button 111, the display part 112 of the operation panel 151 makes a transition to the display part 112 of the operation panel 152. In the display part 112 of the operation panel 152, a destination list button 120 for displaying the destinations of a FAX by a list is displayed. [0172] In the display part 112 of the operation panel 152, when the user sends a FAX and presses down the logout button 119, the screen shown in the display part 112 of the operation panel 152 makes a transition to the login screen as shown in the display part 112 of the operation panel 153. [0173] FIG. 16 shows a destination list screen, which is displayed when the destination list button 120 is pressed down. In the destination list screen, an address book name 161 and a group of destination selection buttons 160 are displayed. The address book name 161 represents whose address book the displayed destination list is based on. The group of destination selection buttons 160 are displayed based on the address book information (see FIG. 6). By selecting a destination selection button 160 to which the user desires to send a FAX from among the group of destination selection buttons 160, it is possible for the user to send a FAX to the corresponding destination. [0174] Next, referring to the sequence diagram of FIG. 17, a description is given below of the processes in the case where the user sends a FAX after copying as shown in FIG. 15. [0175] In step S401, the operation panel 53 notifies the FAX application 22 of a FAX application display request. In step S402, the FAX application 22 notifies the CCS 38 of a login screen display request. [0176] On this occasion, the CCS 38 generates an authentication ticket since the user is logging in. Then, in step S403, the CCS 38 notifies the FAX application 22 of the authentication ticket and user information. [0177] In step S404, the FAX application 22 notifies the UCS 36 of a usage limitation confirmation request together with the user information. The response to the usage limitation confirmation request is provided to the FAX application 22 in step S405. When the FAX function is available, the FAX application 22 notifies the operation panel 53 in step S406 of a FAX application screen display request. [0178] When the user starts using the FAX function, the operation panel 53 notifies the FAX application 22 in step S407 of a FAX transmission request. In step S408, the FAX application 22 notifies the LCS 39 that FAX transmission is started. On this occasion, the user information, a job ID, and a FAX transmission condition are also provided to the LCS 39. The FAX transmission condition is a condition related to transmission of a FAX, such as a destination. [0179] In step S409, the FAX application 22 notifies the operation panel 53 of a FAX transmission reception screen display request. When the FAX transmission ends, the FAX application 22 notifies the LCS 39 in step S410 that the FAX transmission ends. On this occasion, the user information, the job ID, and the FAX transmission condition are also provided to the LCS 39. [0180] In step S411, the FAX application 22 notifies the operation panel 53 of a FAX transmission end screen display request, and the process ends. [0181] The login processes and the FAX transmission processes described above are all performed in the multi-functional apparatus 100. The login processes described below with reference to FIG. 18 are processes in which the user logs in from a PC. [0182] FIG. 18 shows processes performed among the PC 90, the Web server 85 (see FIG. 4), the copy application 21, and the CCS 38. [0183] In step S501, the PC 90 notifies the Web server 85 of a copy application display request. In step S502, the Web server 85 notifies the copy application 21 of the copy application display request. In step S503, the copy application 21 notifies the CCS 38 of an authentication information obtaining request. [0184] In step S504, the CCS 38 notifies the Web server 85 of a login screen display request. In step S505, the Web server 85 notifies the PC 90 of the login screen display request. [0185] When the user inputs the user name and the password, and presses down, for example, a confirm button displayed on the PC 90, the PC 90 notifies the Web server 85 in step S506 of a login request. On this occasion, the user name and the password are also notified to the Web server 85. [0186] Subsequently, the processes of steps S105 through S112 and the process of step S114, which are described above with reference to FIG. 8, are performed. [0187] In step S508, the copy application 21 notifies the Web server 85 of a login result display request. In step S509, the Web server 85 notifies the PC 90 of the login result display request. [0188] The authentication in the above-mentioned processes is password authentication. It is also possible to perform authentication by ticket authentication instead of password authentication. In ticket authentication, a ticket for authentication is obtained by connecting a PC to an authentication WS, and login to a multi-functional apparatus is performed by using the ticket. [0189] A description is given below of the contents provided to the PC and the multi-functional apparatus in ticket authentication. [0190] FIG. 19 is a diagram showing the contents of a user authentication request in ticket authentication. As represented by an XML sentence 142 of FIG. 19, a ticket “XYZZZZZ=” is provided in the following format. <ticket xsi:type=“xsd:base64Binary”>XYZZZZZ=</ticket> [0192] In addition, FIG. 20 shows the contents of a user authentication response in ticket authentication. As represented by a XML sentence 143 of FIG. 20, a response “ABCDEFG=” is provided in the following format. <returnValue xsi:type=“xsd:base64Binary”>ABCDEFG=</returnValue > [0194] Next, a description is given below of settings related to authentication. [0195] The authentication DB and the directory DB described above with reference to FIGS. 5 and 6 are not necessarily provided in the authentication WS and the user directory WS, respectively, and may be provided in a multi-functional apparatus. [0196] By providing the authentication DB and the directory DB in a multi-functional apparatus, it is possible to save in the DBs provided therein information related to, for example, a temporary user who uses the same multi-functional apparatus only for a week. Hence, it is possible to avoid unnecessary updating of the authentication DB provided in the authentication WS or the directory DB provided in the user directory WS, which is used by a lot of multi-functional apparatuses. [0197] In a case where the authentication DB and the directory DB are provided in a multi-function apparatus as mentioned above, it is possible to set which DB is to be used. FIG. 21 shows an authentication set screen for setting of authentication. The authentication set screen includes set items 170 and check boxes 171. [0198] The set items 170 include “prioritize external authentication”, “prioritize internal authentication”, “only external authentication” and “only internal authentication”. The “external authentication” represents authentication in the authentication WS. The “internal authentication” represents authentication by using the authentication DB provided in a multi-functional apparatus used by a user. “Prioritize” means that authentication is performed by prioritized authentication, but when the prioritized authentication cannot be used, authentication is performed by the other authentication. “Only” means authentication is performed by only one of the internal authentication and the external authentication. [0199] The user can perform setting of authentication by checking the one of the check boxes 171 corresponding to a set item selected among the four set items 170. [0200] Further, when setting a user directory, a set screen obtained by replacing “authentication” with “user directory” in the screen of FIG. 21 is displayed. [0201] The contents of authentication setting thus set are saved in a bit field shown in FIG. 22. The bit field shown in FIG. 22 is a bit sequence of 8 bits: the lowest bit through fourth bit are used for authentication setting, and the fifth bit through the eighth bit are used for saving a user directory. Each bit corresponds to the above-mentioned eight set items, and the value of the bit corresponding to the checked set item is “1”. [0202] By using the bit field, a multi-functional apparatus determines which DB is to be used and performs authentication. This process is described below with reference to the flowchart of FIG. 23. [0203] It is assumed that user authentication information, the authentication type, the kind of authentication means, and information specifying authentication means (authentication means specifying information) are already obtained before the processes shown in the flowchart of FIG. 23. Among these, the kind of authentication means represents the above-mentioned authentication setting and, specifically, NT authentication or LDAP authentication, for example, may be specified. [0204] In step S601, confirmation of the user authentication means, which is set by using the above-mentioned bit field, is performed. Step S601 corresponds to an authentication party determination step. In step S602, whether user authentication succeeds is determined. Step S602 corresponds to an authentication step. When it is determined that user authentication succeeds (SUCCESS in step S602), the process ends. When it is determined that user authentication fails (FAILURE in step S602), it is determined in step S603 by using the bit field whether there is alternative means. Step S603 corresponds to an alternative authentication determination step. [0205] When the setting of the bit field is “only external authentication” or “only internal authentication”, it is determined that there is no alternative means (NO in step S603) and the process ends assuming that authentication fails. [0206] When it is determined that there is alternative means (YES in step S603), the set alternative user authentication means is confirmed in step S604. In step S605, it is determined whether alternative user authentication succeeds or fails. When the alternative user authentication succeeds (SUCCESS in step S605), the process ends assuming that the user authentication succeeds. When the alternative user authentication fails (FAILURE in step S605), the process ends assuming that the user authentication fails. [0207] Here, a description is given of steps S602 and S605. In addition to the case where user authentication fails, which is an original failure, the cases where it is determined that authentication fails include, for example: the case where the user identification information and/or the authentication type cannot be handled by an authentication party; the case where the authentication means is different from that specified in the authentication means specifying information; and the case where the system of an authentication party is busy. [0208] The present invention is not limited to the specifically disclosed embodiments, and variations and modifications may be made without departing from the scope of the present invention. [0209] The present application is based on Japanese priority applications No. 2003-200958 filed on Jul. 24, 2003 and No. 2004-177053 filed on Jun. 15, 2004, the entire contents of which are hereby incorporated by reference. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5418889 *Dec 1, 1992May 23, 1995Ricoh Company, Ltd.System for generating knowledge base in which sets of common causal relation knowledge are generatedUS5633932 *Dec 19, 1995May 27, 1997Intel CorporationApparatus and method for preventing disclosure through user-authentication at a printing nodeUS5774551 *Aug 7, 1995Jun 30, 1998Sun Microsystems, Inc.Pluggable account management interface with unified login and logout and multiple user authentication servicesUS5933584 *May 14, 1997Aug 3, 1999Ricoh Company, Ltd.Network system for unified businessUS6612928 *Jul 17, 2001Sep 2, 2003Sierra Design GroupPlayer identification using biometric data in a gaming environmentUS6880091 *Jun 29, 2000Apr 12, 2005Hewlett-Packard Development Company, L.P.System and method for authentication of a user of a multi-function peripheralUS7219231 *Jan 30, 2002May 15, 2007Hewlett-Packard Development Company, L.P.Extensible authentication system and methodUS7312884 *Mar 3, 2000Dec 25, 2007Canon Kabushiki KaishaImage reading apparatus selectively connectable to image forming apparatuses via a networkUS20020042880 *Sep 28, 2001Apr 11, 2002Tomoaki EndohPeripheral equipment and management method thereofUS20020144257 *Dec 26, 2001Oct 3, 2002Hiroyuki MatsushimaImage formation system, software acquisition method, and computer productUS20020184217 *Apr 19, 2001Dec 5, 2002Bisbee Stephen F.Systems and methods for state-less authenticationUS20030046535 *Sep 6, 2001Mar 6, 2003Nelson Dean S.System and method for authenticating use of a network applianceUS20030145219 *Jan 30, 2002Jul 31, 2003Cossel Travis MyronParameter verification in an authentication system and methodUS20030145220 *Jan 30, 2002Jul 31, 2003Cossel Travis MyronExtensible authentication system and methodUS20040027601 *Sep 21, 2001Feb 12, 2004Tatsuo ItoDocument acquiring device, document filing system, and electronic document notarizing systemUS20040078425 *Oct 18, 2002Apr 22, 2004Sandfort Patrick O?Apos;NeilSystem and method for tracking print system utilization* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7684074Oct 21, 2005Mar 23, 2010Sharp Laboratories Of America, Inc.Methods and systems for imaging device metadata managementUS7738808Jul 29, 2005Jun 15, 2010Sharp Laboratories Of America, Inc.Methods and systems for imaging device concurrent account use with remote authorizationUS7826081Nov 2, 2010Sharp Laboratories Of America, Inc.Methods and systems for receiving localized display elements at an imaging deviceUS7870185Jan 11, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification administrationUS7873553Jan 18, 2011Sharp Laboratories Of America, Inc.Methods and systems for authorizing imaging device concurrent account useUS7873718Jan 18, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting server recoveryUS7920101Apr 5, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device display standardizationUS7934217Jul 29, 2005Apr 26, 2011Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access to an imaging deviceUS7941743Aug 18, 2006May 10, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device form field managementUS7966396Jun 21, 2011Sharp Laboratories Of America, Inc.Methods and systems for administrating imaging device event notificationUS7969596Jun 28, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device document translationUS7970813Jun 28, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification administration and subscriptionUS7978618Jul 12, 2011Sharp Laboratories Of America, Inc.Methods and systems for user interface customizationUS8001183Aug 16, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device related event notificationUS8001586 *Aug 16, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential management and authenticationUS8001587Jul 29, 2005Aug 16, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential managementUS8006176Aug 23, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging-device-based form field managementUS8006292 *Jul 29, 2005Aug 23, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submission and consolidationUS8006293 *Jul 29, 2005Aug 23, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential acceptanceUS8014502 *Aug 30, 2006Sep 6, 2011Ricoh Company, Ltd.Communication deviceUS8015234 *Sep 30, 2005Sep 6, 2011Sharp Laboratories Of America, Inc.Methods and systems for administering imaging device notification access controlUS8018610Sep 13, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device remote application interactionUS8023130Sep 20, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data maintenanceUS8024792 *Jul 29, 2005Sep 20, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submissionUS8032579 *Sep 30, 2005Oct 4, 2011Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device notification access controlUS8032608Oct 4, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device notification access controlUS8035831Oct 11, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device remote form managementUS8049677Nov 1, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device display element localizationUS8051125 *Sep 30, 2005Nov 1, 2011Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device event notification subscriptionUS8051140Nov 1, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device controlUS8056126 *Nov 8, 2011Konica Minolta Business Technologies, Inc.Authentication system for instruction processing apparatus, image forming apparatus, authentication control method, and authentication control programUS8060921 *Nov 15, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential authentication and communicationUS8060930 *Jul 29, 2005Nov 15, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential receipt and authenticationUS8065384Sep 30, 2005Nov 22, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification subscriptionUS8065524Feb 22, 2007Nov 22, 2011Panasonic CorporationAuthentication processing apparatus and authentication processing methodUS8106922Jan 31, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device data displayUS8115944Jul 29, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and systems for local configuration-based imaging device accountingUS8115945Aug 31, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device job configuration managementUS8115946Aug 31, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and sytems for imaging device job definitionUS8115947Sep 30, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and systems for providing remote, descriptor-related data to an imaging deviceUS8120793Jul 29, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for displaying content on an imaging deviceUS8120797Jul 29, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for transmitting content to an imaging deviceUS8120798Sep 30, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for providing access to remote, descriptor-related data at an imaging deviceUS8120799Sep 30, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for accessing remote, descriptor-related data at an imaging deviceUS8125666Oct 8, 2004Feb 28, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device document managementUS8156424Sep 22, 2005Apr 10, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device dynamic document creation and organizationUS8171299 *Aug 29, 2005May 1, 2012Canon Kabushiki KaishaData communication apparatus, data communication method, data communication program, and storage medium storing the programUS8171404Mar 12, 2007May 1, 2012Sharp Laboratories Of America, Inc.Methods and systems for disassembly and reassembly of examination documentsUS8171526Oct 3, 2005May 1, 2012Ricoh Company, Ltd.Service providing system, information processing apparatus, service providing server and service providing methodUS8201077Jun 12, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device form generation and form field data managementUS8213034Jul 29, 2005Jul 3, 2012Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access on an imaging deviceUS8230328Sep 22, 2005Jul 24, 2012Sharp Laboratories Of America, Inc.Methods and systems for distributing localized display elements to an imaging deviceUS8237946Jul 29, 2005Aug 7, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting server redundancyUS8270003Aug 18, 2006Sep 18, 2012Sharp Laboratories Of America, Inc.Methods and systems for integrating imaging device display contentUS8332958 *Dec 11, 2012Kyocera Document Solutions Inc.Image forming systemUS8341716Dec 25, 2012Fuji Xerox Co., Ltd.Information processing device, information processing method, and storage media storing user certification programUS8345272Sep 28, 2006Jan 1, 2013Sharp Laboratories Of America, Inc.Methods and systems for third-party control of remote imaging jobsUS8384925Feb 26, 2013Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data managementUS8428484Apr 23, 2013Sharp Laboratories Of America, Inc.Methods and systems for peripheral accountingUS8601559Apr 29, 2008Dec 3, 2013Konica Minolta Business Technologies, Inc.Image output authentication system, image output authentication server, and image output authentication methodUS8695065Mar 29, 2012Apr 8, 2014Canon Kabushiki KaishaData communication apparatus, data communication method, data communication program, and storage medium storing the programUS9098716Sep 21, 2011Aug 4, 2015Konica Minolta Business Technologies, Inc.Authentication system for instruction processing apparatus, image forming apparatus, authentication control method, and authentication control programUS9183366 *Jan 27, 2014Nov 10, 2015Microsoft Technology Licensing, LlcRequest-specific authentication for accessing Web service resourcesUS9361051 *Aug 14, 2014Jun 7, 2016Canon Kabushiki KaishaImage forming apparatus that transmits and receives maintenance work data to and from information processing apparatus, method of controlling the same, and storage mediumUS9389816 *Aug 14, 2014Jul 12, 2016Canon Kabushiki KaishaImage forming apparatus that transmits and receives maintenance work data to and from information processing apparatus, method of controlling the same, and storage mediumUS20060044609 *Aug 29, 2005Mar 2, 2006Canon Kabushiki KaishaData communication apparatus, data communication method, data communication program, and storage medium storing the programUS20060064753 *Dec 23, 2004Mar 23, 2006Konica Minolta Business Technologies, Inc.Authentication system for instruction processing apparatus, image forming apparatus, authentication control method, and authentication control programUS20060075474 *Oct 3, 2005Apr 6, 2006Sachiko TakeuchiService providing system, information processing apparatus, service providing server and service providing methodUS20060077119 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for receiving content at an imaging deviceUS20060077414 *Oct 21, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device controlUS20060077422 *Oct 8, 2004Apr 13, 2006Rono MathiesonMethods and systems for imaging device remote form managementUS20060077423 *Oct 8, 2004Apr 13, 2006Rono MathiesonMethods and systems for imaging device remote application interactionUS20060077426 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential receipt and authenticationUS20060077427 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for local configuration-based imaging device accountingUS20060077428 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for displaying content on an imaging deviceUS20060077429 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential management and authenticationUS20060077430 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submissionUS20060077431 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device concurrent account useUS20060077432 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data managementUS20060077433 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data maintenanceUS20060077434 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submission and consolidationUS20060077435 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting server redundancyUS20060077436 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting server recoveryUS20060077437 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential authentication and communicationUS20060077438 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential managementUS20060077439 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for distributing localized display elements to an imaging deviceUS20060077440 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for receiving localized display elements at an imaging deviceUS20060077442 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device display element localizationUS20060077443 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device display coordinationUS20060077446 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device event notification subscriptionUS20060077447 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device notification access controlUS20060077450 *Sep 30, 2005Apr 13, 2006Reddy Amarender R KMethods and systems for accessing remote, descriptor-related data at an imaging deviceUS20060077454 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification administration and subscriptionUS20060077464 *Oct 8, 2004Apr 13, 2006Rono MathiesonMethods and systems for imaging device document managementUS20060080124 *Aug 31, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and sytems for imaging device job definitionUS20060080129 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for providing access to remote, descriptor-related data at an imaging deviceUS20060080731 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential acceptanceUS20060085430 *Jul 29, 2005Apr 20, 2006Sharp Laboratories Of America, Inc.Methods and systems for accessing a remote file structure from an imaging deviceUS20060090128 *Jul 29, 2005Apr 27, 2006Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access to an imaging deviceUS20060103873 *Jul 29, 2005May 18, 2006Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access on an imaging deviceUS20060106803 *Oct 18, 2005May 18, 2006Sachiko TakeuchiInformation management system, an information processor, and an information management methodUS20060119883 *Jul 29, 2005Jun 8, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential consolidationUS20060279474 *Aug 18, 2006Dec 14, 2006Lum Joey PMethods and Systems for Imaging Device Data DisplayUS20070071199 *Aug 30, 2006Mar 29, 2007Shinichiro OzekiCommunication deviceUS20070077405 *Sep 30, 2005Apr 5, 2007Basf CorporationInorganic/organic-filled styrenic thermoplastic door skinsUS20070091010 *Nov 21, 2006Apr 26, 2007Richardson Tanna MMethods and Systems for User Interface CustomizationUS20070208939 *Feb 22, 2007Sep 6, 2007Matsushita Electric Industrial Co., Ltd.Authentication processing apparatus and authentication processing methodUS20090025072 *Apr 29, 2008Jan 22, 2009Konica Minolta Business Technologies, Inc.Image output authentication system, image output authentication server, and image output authentication methodUS20100036796 *Jul 16, 2009Feb 11, 2010Takeshi KajikawaImage forming apparatus, log storing method, and computer program productUS20100185858 *Jul 22, 2010Kyocera Mita CorporationImage Forming SystemUS20110075179 *Sep 29, 2010Mar 31, 2011Canon Kabushiki KaishaImage processing apparatus that performs authentication, authentication method therefor, and storage mediumUS20150049363 *Aug 14, 2014Feb 19, 2015Canon Kabushiki KaishaImage forming apparatus that transmits and receives maintenance work data to and from information processing apparatus, method of controlling the same, and storage medium* Cited by examinerClassifications U.S. Classification709/229International ClassificationG06F21/00, B41J29/00, G09C1/00, G06F15/16, G06F21/20, G06F15/00, G06F1/00Cooperative ClassificationG06F21/31, G06F2221/2115European ClassificationG06F21/31Legal EventsDateCodeEventDescriptionNov 8, 2004ASAssignmentOwner name: RICOH COMPANY, LTD., JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MIHIRA, SACHIKO;ITO, TATSUO;REEL/FRAME:015971/0735;SIGNING DATES FROM 20040804 TO 20040809RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services