Source: http://www.google.es/patents/US20050044248?dq=flatulence
Timestamp: 2013-05-23 12:32:03
Document Index: 33246857

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

Patente US20050044248 - User authentication method, image forming apparatus, and user authentication ... - Google PatentesB�squeda Im�genes Maps Play YouTube Noticias Gmail Drive M�s » B�squeda avanzada de patentes | Historial web | Iniciar sesi�n B�squeda avanzada de patentesPatentesA 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.es/patents/US20050044248?utm_source=gb-gplus-sharePatente US20050044248 - User authentication method, image forming apparatus, and user authentication program N�mero de publicaci�nUS20050044248 A1Tipo de publicaci�nSolicitud N�mero de solicitud10/891,154 Fecha de publicaci�n24 Feb 2005 Fecha de presentaci�n15 Jul 2004 Fecha de prioridad24 Jul 2003Tambi�n publicado comoEP1501002A2EP1501002A3 N�mero de publicaci�nUS 2005/0044248 A1US2005/0044248A1 InventoresTatsuo ItoSachiko Mihira Cesionario originalRicoh Company, Ltd. Clasificaci�n de EE.UU.709/229 Clasificaci�n internacionalG06F21/00B41J29/00G09C1/00G06F15/16G06F21/20G06F15/00G06F1/00 Clasificaci�n cooperativaG06F21/31G06F2221/2115 Clasificaci�n europeaG06F 21/31Referencias Citada por (17)Enlaces externosUSPTO Cesi�n de USPTO EspacenetUser authentication method, image forming apparatus, and user authentication programUS 20050044248 A1 Resumen A 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 method includes: a user authentication information obtaining step of obtaining user authentication information for performing authentication of the user; an authentication party determination step of determining whether to perform authentication of the user in the authentication apparatus or in the image forming apparatus based on the authentication set information; an authentication step of performing authentication of the user in an authentication party determined in the authentication party determination step by using the user authentication information; an authentication result obtaining step of obtaining a result of the authentication in the authentication step; and an authentication result specifying step of specifying the obtained authentication result to the user. Dibujos(21) Reclamaciones
1. A user authentication method 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, said user authentication method comprising: a user authentication information obtaining step of obtaining user authentication information for performing the authentication of the user; an authentication party determination step of determining whether to perform the authentication of the user in the authentication apparatus or in the image forming apparatus based on the authentication set information; an authentication step of performing the authentication of the user in an authentication party determined in the authentication party determination step by using the user authentication information; an authentication result obtaining step of obtaining a result of the authentication of the user in the authentication step; and an authentication result specifying step of specifying the obtained authentication result to the user. 2. The user authentication method as claimed in claim 1, further comprising: an alternative authentication determination step of determining, when the authentication result in the authentication step is an authentication failure, whether to perform authentication in another authentication party based on the authentication set information. 3. The user authentication method as claimed in claim 1, further comprising: a user related information obtaining step of obtaining user related information that is information related to the user. 4. The user authentication method as claimed in claim 3, wherein the user related information obtaining step obtains the user related information from a user related information storing apparatus storing the user related information via a network. 5. The user authentication method as claimed in claim 3, wherein the user related information includes information representing an image formation function available to the user. 6. The user authentication method as claimed in claim 3, wherein the user authentication information obtaining step obtains the user related information via a network. 7. 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, said image forming apparatus comprising: a user authentication information obtaining part configured to obtain user authentication information for performing the authentication of the user; an authentication party determination part configured to determine whether to perform the authentication of the user in the authentication apparatus or in the image forming apparatus based on the authentication set information; an authentication part configured to perform the authentication of the user in an authentication party determined by the authentication party determination part by using the user authentication information; an authentication result obtaining part configured to obtain a result of the authentication of the user by the authentication party; and an authentication result specifying part configured to specify the obtained result to the user. 8. The image forming apparatus as claimed in claim 7, wherein, when the result of the authentication is an authentication failure, the authentication part determines whether to perform authentication in another authentication party based on the authentication set information. 9. The image forming apparatus as claimed in claim 7, further comprising: a user related information obtaining part configured to obtain user related information that is information related to the user. 10. The image forming apparatus as claimed in claim 9, wherein the information obtaining part obtains the user related information from a user related information storing apparatus storing the user related information via a network. 11. The image forming apparatus as claimed in claim 9, wherein the user related information includes information representing an image formation function available to the user. 12. The image forming apparatus as claimed in claim 9, wherein the user authentication information obtaining part obtains the user related information via a network. 13. A user authentication program causing a computer to carry out a user authentication method 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, said user authentication method comprising: a user authentication information obtaining step of obtaining user authentication information for performing the authentication of the user; an authentication party determination step of determining whether to perform the authentication of the user in the authentication apparatus or in the image forming apparatus based on the authentication set information; an authentication step of performing the authentication of the user in an authentication party determined in the authentication party determination step by using the user authentication information; an authentication result obtaining step of obtaining a result of the authentication of the user in the authentication step; and an authentication result specifying step of specifying the obtained authentication result to the user.
The �ABCDEFG=� is an example, which indicates whether or not the user is authenticated. 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. In step S201, the operation panel 53 notifies the copy application 21 of a copy start request. 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. In step S203, the copy application 21 notifies the operation panel 53 of a copy reception screen display request. Thereby, copying is performed. 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. 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. In the aforementioned processes, the user who has logged in performs copying and logs out. 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. Referring to the sequence diagram of FIG. 14, a specific description is given of the processes in the above-mentioned case. 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. 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. 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. 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. 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. 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. 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. In the aforementioned manner, the processes in the case where the user directory 93 is used are performed. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. In step S411, the FAX application 22 notifies the operation panel 53 of a FAX transmission end screen display request, and the process ends. 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. FIG. 18 shows processes performed among the PC 90, the Web server 85 (see FIG. 4), the copy application 21, and the CCS 38. 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. 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. 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. 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. 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. 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. A description is given below of the contents provided to the PC and the multi-functional apparatus in ticket authentication. 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> 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 > Next, a description is given below of settings related to authentication. 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. 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. 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. 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. 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. Further, when setting a user directory, a set screen obtained by replacing �authentication� with �user directory� in the screen of FIG. 21 is displayed. 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�. 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. 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. 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. 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. 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. 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. 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. 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. Citada por Patente citante Fecha de presentaci�n Fecha de publicaci�n Solicitante T�tuloUS800158629 Jul 200516 Ago 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential management and authenticationUS800629229 Jul 200523 Ago 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submission and consolidationUS800629329 Jul 200523 Ago 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential acceptanceUS801450230 Ago 20066 Sep 2011Ricoh Company, Ltd.Communication deviceUS801523430 Sep 20056 Sep 2011Sharp Laboratories Of America, Inc.Methods and systems for administering imaging device notification access controlUS802479229 Jul 200520 Sep 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submissionUS803257930 Sep 20054 Oct 2011Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device notification access controlUS805112530 Sep 20051 Nov 2011Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device event notification subscriptionUS805612623 Dic 20048 Nov 2011Konica Minolta Business Technologies, Inc.Authentication system for instruction processing apparatus, image forming apparatus, authentication control method, and authentication control programUS806092129 Jul 200515 Nov 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential authentication and communicationUS806093029 Jul 200515 Nov 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential receipt and authenticationUS806552422 Feb 200722 Nov 2011Panasonic CorporationAuthentication processing apparatus and authentication processing methodUS817129929 Ago 20051 May 2012Canon Kabushiki KaishaData communication apparatus, data communication method, data communication program, and storage medium storing the programUS81715263 Oct 20051 May 2012Ricoh Company, Ltd.Service providing system, information processing apparatus, service providing server and service providing methodUS83329581 Oct 200911 Dic 2012Kyocera Document Solutions Inc.Image forming systemUS834171613 Jun 200825 Dic 2012Fuji Xerox Co., Ltd.Information processing device, information processing method, and storage media storing user certification programUS201001858581 Oct 200922 Jul 2010Kyocera Mita CorporationImage Forming SystemGirarImagen originalP�gina principal de Google - Sitemap - Descargas masivas de USPTO - Pol�tica de privacidad - Condiciones de servicio - Acerca de Google Patentes - Danos tu opini�nDatos proporcionados por IFI CLAIMS Patent Services©2012 Google