JP2008538241A - System and method for managing documents by multiple network applications - Google Patents

Abstract

Method and system for managing documents. The system includes a document manager server connected to an image processing apparatus and an application via a network. The document manager server receives the identification information from the image processing apparatus and transmits information regarding the network application to the image processing apparatus. This information is then used to change the function of the image processing apparatus.

Description

  The present invention relates to a method and computer-based system for managing documents or files between a multifunction peripheral and various back-end network applications.

  Over the past few years there has been an increase in the number and type of document related applications available over the network. Such applications may include a document management system, such as a document management system specialized in managing documents of various specific content (eg, medical, legal, finance, marketing, science, education, etc.). Other applications include various distribution systems such as electronic mail servers, facsimile servers, and / or regular mail delivery. Still other applications include document processing systems such as format conversion and optical character recognition. Further applications include document management systems that are used to store, organize, and manage various documents. The foregoing application is hereinafter referred to as a “back end” application.

  Various systems have been devised that access the aforementioned network applications from image processing devices (eg, scanners, printers, copiers, cameras). One system associates a computer with each image processing device that manages documents through a network application. The computer communicates with various network applications to enable the use of the aforementioned applications by the user of the image processing device. For example, the computer requests and receives information from the network application about data format and content necessary for the application to manage the document. The computer processes this information to provide the correct format and content and configures the image processing device.

  However, the system described above has a number of drawbacks, especially when considered within a relatively large office environment having a significant number of image processing devices using various network document applications that can change over time. In particular, the requirement to have a computer for each image processing device increases cost and reduces flexibility. This requirement places a burden on computer maintenance, protection and upgrades. As new applications are integrated in the system, each computer and / or each image processing device must be updated to be compatible with the new network application. The task of updating each local computer and / or each image processing device introduces a costly burden on the system administrator and significantly increases traffic on the corporate network. This increase in traffic can slow down the entire enterprise network.

  There is a need for more efficient and dynamic management of documents simultaneously between image processing devices and various network applications. The present invention provides a method and system that meets this need.

  The system of the present invention includes at least one image processing apparatus (such as a multifunction peripheral), but preferably includes several image processing apparatuses, a document manager server connected to the image processing apparatus, and a document manager server. Includes connected network applications. The document manager server functions as an agent of the image processing apparatus and as a gateway to the network application.

  The document manager server receives the identification information from the image processing device, examines the profile, and transmits the profile to the image processing device. The above-described image processing apparatus can be realized as one or a plurality of various multifunction peripherals (MFDs). The profile contains information about applications connected to the document manager server via the network. This information may be in the form of specific parameters that identify the various backend network applications available by the MFD. Based on this profile information, the MFD receives a software plug-in (corresponding to a specific background network application) sent from the document manager server. The MFD functionality can then be changed or customized based on this received plug-in information. In particular, based on the profile and plug-in information, the image processing device can adjust its user interface and corresponding functions available to the user to interact with the network application. The document manager server can receive job information (eg, a document) from the image processing device, process the job information, and send the processed information to an application connected to the document manager server. Software plug-ins allow the user to add specific indexing and processing instructions to the image file before it is actually scanned. The software plug-in also allows the user to perform a specialized login function to gain access to backend applications that require additional authentication levels. Applications may include, for example, an email server, fax server, file format conversion system, optical character recognition system, document management system, or file storage system. The system also provides a way for the image processing device to determine if a particular backend application requires user authentication if the user is already logged into the network domain.

  Effectively, the system and method of the present invention allows an image processing device to be automatically updated with information that enables the use of newly incorporated applications on the network. The update of the image processing apparatus can be efficiently performed by the document manager server based on profile information available to the image processing apparatus. Certain software plug-ins can be stored on the document manager server and accessed by the target MFD that corresponds to the particular back-end application incorporated into the system. The server profile sent to the image processing device also allows the user interface to be tailored so that the user can select various available processing functions from the image processing device. The server profile allows various instructions, indexes or processing instructions to be added to the image data before it is processed by the MFD. The MFD then appends the above instructions to the scanned image before it is sent to the document manager server. Thus, individual image processing devices do not have to be upgraded with new firmware (which is expensive and time consuming). The document manager server can efficiently manage various aspects of the relationship between the image processing device and the network application. For example, the document manager server can manage the security of the global directory server, and the financial relationship between the image processing device and the network application (eg, billing, accounting, and licensing issues). The image processing apparatus and the network application, the document can be processed, and the image data can be modified. It may also be possible for a user of the device to log into various applications.

  In addition, the document manager server is easily customized and can include various plug-ins for each newly installed network application. The plug-in allows the image processing device to implement customized functions that are specific to each network application and specifically to the back-end application. The document manager server can send the plug-in to the image processing device, and the image processing device customizes the processing based on the received plug-in. The plug-in causes the image processing device to ask the user for additional authentication information (if necessary) for logging into the network application. Another configuration enabled by the system is the ability of the image processing device to identify whether a user has already been authenticated against a particular user authentication system. Plug-ins also allow users to include or add specific processing instructions to scanned or processed documents before the documents are sent to the document manager server for later processing by back-end applications Become.

  A more thorough understanding of the present invention and the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description considered in conjunction with the accompanying drawings.

  Referring now to the accompanying drawings, like reference numerals designate identical or corresponding parts throughout the several views. FIG. 1 illustrates how a document manager server 40 manages documents and files by managing information according to the present invention, and in particular processing information about applications that can be grouped into various groups I-III. Figure 2 is a block diagram of a system 5 that enables. The system 5 includes a network 100 that interconnects at least one (but preferably multiple) image processing devices, which can be implemented as multifunction peripherals (MFD) 10-30, to a document manager server 40. Network 100 preferably uses TCP / IP (Transmission Control Protocol / Internet Protocol), but any other desired network protocol (eg, IPX / SPX (inter-network packet exchange / sequential packet exchange), NetBEUI (NetBIOS extended user interface) and NetBIOS (network basic input / output system) are also possible. Network 100 may be a local area network, a wide area network, or any type of network (such as an intranet, extranet, the Internet, or a combination thereof). Other communication links (virtual dedicated network or wireless link, or any other suitable alternative) may also be used for the network 100.

  As shown in FIG. 1, the devices 10-30 can be multi-function peripherals (ie, “MFD”). MFDs can incorporate multiple scanners, copiers, printers, fax machines, digital cameras, other office machines, and combinations thereof, or multiple scanners, copiers, printers, fax machines, digital It can be any of cameras, other office machines, and combinations thereof. Any or a combination of the aforementioned devices is commonly referred to as MFD. Various MFDs are generally known in the art and share common configurations and hardware with the MFD of the present invention. In one embodiment of the present invention, the MFD is a portable device (such as a digital camera) that can be connected to the Internet via a wired or wireless connection. The aforementioned MFD combines digital imaging and Internet functions, so it can capture still images, sound or video and share the aforementioned multimedia using wired or wireless connections from various locations. is there. With MFD, it is possible to create web pages, send and receive emails with attachments, edit images, FTP files, surf the Internet, send or receive faxes. In another embodiment, the MFD is a plurality of scanners, photocopiers and printers, as will be described in further detail below with corresponding FIGS. 11-12.

  As shown in FIG. 1, the document manager server 40 is connected to a directory / address book server 60 (or “directory server” or “global directory”). Directory server 60 may include information such as names, addresses, network addresses, email addresses, telephone / fax numbers, other types of destination information, and personal authentication. Other information can also be included in the directory server 60. Examples of directory servers 60 that are compatible with the present invention include directory servers enabled by Lotus Notes ™, Microsoft Exchange ™, LDAP (“Lightweight Directory Access Protocol”). Including but not limited to. LDAP is a software protocol that allows users to locate organizations, individuals, files, and devices in a network. The document manager server 40 can also be connected to a network domain controller 50 that controls the authentication of MFD users.

  The network domain controller 50 is, for example, a server that responds to a security authentication request (such as login) in the domain. The network domain controller 50 can be backed up by one or more backup network domain controllers that can optionally also handle security authentication. Examples of directory server 60 and network domain controller 50 are described in US patent application Ser. No. 10 / 243,645, filed Sep. 16, 2002, the entire contents of which are incorporated herein by reference and claims. Is disclosed.

  Briefly, the system 5 provides access to information stored in the directory server 60 through the user's document manager server 40 of the MFD 10-30. The user can request a search of the corporate global directory stored in the directory server 60. The document manager server 40 can forward the search request to the directory server 60 and can receive the search results (eg, email address and / or fax number) from the directory server 60. . The document manager server 40 can transfer the search result to the MFD 20. The MFD 20 can temporarily store and display it. The user can select the displayed result (eg, email address or fax number), scan the document, and request the sending of the scanned document, email and / or fax delivery to the selected destination It is.

  The document manager server 40 can be configured to function as an intermediate agent or gateway between a plurality of network applications 50, 60, 70, 80 and 90 and the MFD. Applications 70, 80, and 90 may include, for example, an email server, fax server, file format conversion system, optical character recognition (OCR) system, document management system, file storage system, and combinations thereof. The document management server 40 can support a plurality of back-end systems such as various document management systems and file storage systems. In the preferred embodiment, the email server is incorporated into the document manager server 40. Email servers may include, but are not limited to, Lotus Notes ™ email servers, Microsoft Exchange ™ email servers, and SMTP (“Simple Mail Transfer Protocol”) email servers. Not. In the preferred embodiment, the fax server is a Captoris Light Fax ™ server. However, other suitable fax servers can be implemented with the present invention. The file format conversion system can be configured to convert a document from one format (eg, TIFF “Tag Image File Format”) to another format (eg, PDF “Portable Document Format”). Examples of document management systems include U.S. Patent Application No. 09 / 795,438, filed March 1, 2001, and April 5, 2002, the entire contents of which are incorporated herein by reference and claims. No. 10 / 116,162, dated application. Other document management systems include systems specialized for managing documents having specific content. As an example, the document management system is a system implemented by the Federal Public Insurance System Administration Center that manages medical and insurance records provided under the Health Insurance Interoperability and Accountability Act (HIPAA). possible. Documentum is an exemplary brand of digital file management system used to manage, store and various other file management processes for stored documents / records / multimedia files. Other systems for managing and / or storing documents such as legal, finance, marketing, science, education, etc. can be connected to the document manager server 40.

  As described above, the document management server 40 can simultaneously support a plurality of the aforementioned systems. As will be described later, a profile can be configured to support a plurality of systems via software plug-ins, and the functions and user interfaces of the image processing apparatuses 10, 20, and 30 are based on the aforementioned plug-ins. It can be customized.

  The aforementioned applications can be grouped into groups I to III, for example. Group I may be a distribution system group including an email server and a fax server. Group II may be an intermediate processing group including a file format conversion system and an optical character recognition system. Group III can be a back-end system group including a document management system and a file storage system. Groups I-II may include multiple devices from each category. For example, the document management server 40 can be connected to a plurality of applications from each group. The document manager server 40 can send documents to several applications in each group. In the preferred embodiment, the document manager server 40 distributes documents to some of the applications in the distribution system, but to one or more applications in the intermediate processing group and to one of the backend systems. Deliver documents to one or more applications. For example, the document manager server 40 can distribute documents to an email server and fax server, an OCR system, and a document management system. Other combinations are possible in other embodiments.

  In the preferred embodiment, the MFDs 10-30 and the document manager server 40 exchange data using HTTP ("Hypertext Transfer Protocol") or HTTPS (HTTP Over Secure Sockets Layer) protocols. Other protocols (eg, TCP / IP, IPX / SPX, NetBEUI, NetBIOS, etc.) can be used in the present invention as well. Preferably, the MFDs 10-30 and the document manager server 40 exchange data using XML format ("Extensible Markup Language"). Other formats such as HTML can be used in the present invention as well.

  In the preferred embodiment, document manager server 40 may include an MFD profiler 280 (shown in FIG. 2) that manages the profiles of MFDs 10-30. The administrator of the system 5 can create, modify and maintain profiles via the profile manager server 40 profile user interface. The profile includes information (for example, parameters) sent from the document manager server 40 to the MFD. Based on this information, the MFD can adjust its user interface and functionality to properly interface with the document manager server 40. This information may also include software plug-ins processed by the MFD to allow it to modify the operation of the MFD based on the presence or introduction of the backend system. The document manager server 40 includes a software plug-in corresponding to a back-end application connected to the document manager server 40. For example, the MFD displays options that allow the user to select options (eg, specific delivery systems, intermediate processing systems, and back-end systems) available to the MFD via the document manager server 40. Is possible. The information included in the profile may be identification information of various applications 70 to 90 connected to the document manager server 40. The profiler 280 receives identification information (for example, serial number) from the MFD, and uses this identification information to register the MFD in a register (for example, a data table stored in the memory of the document manager server 40). Check whether it is done. If registered, the profiler sends the profile assigned to the MFD to the MFD. If the MFD is not registered, the profiler can register the MFD and send the profile to the MFD. The profiler can store more than one profile. In the preferred embodiment, one profile is assigned to each MFD, and more than one MFD can share the same profile. Although the term “software plug-in” has been used, it is possible to modify the operation of the MFD using any type of software, programming or chip.

Examples of parameters in the profile include
Profile ID that identifies the profile,
An LDAP enable parameter indicating whether LDAP tree search is enabled on the document manager server 40 using the directory server 60;
A basic domain name (DN) parameter that provides a default search field in the LDAP tree when LDAP search is enabled,
A network authentication parameter indicating whether network authentication is enabled using the network domain controller 40;
A timeout parameter indicating the period of time that elapses before the MFD resets and prompts the user for login information;
A maximum result count parameter that determines the maximum number of LDAP query results returned,
A fax option parameter indicating whether a fax server is connected to the document manager server 40;
Post-scan processing parameters indicating a post-scan processing system connected to the document manager server 40 (which may include, for example, an email server, a file format conversion system, an optical character conversion system, etc.);
Backend parameters indicating a backend system (which may include a document management system or file storage system, or another similar type system) connected to the document manager server 40 and accessible by MFD, and software Includes, but is not limited to, plug-ins (exemplary code represented in FIG. 7 including executable files that allow the image processing device to perform specific processing tasks for the backend application).

  Other parameters can also be included in the profile. For example, a specific user ID, paper default size, scan resolution setting, document feeder status, department code for billing of image processing steps, additional scan job parameters for a specific user ID, or any additional Can be used.

  The backend parameter may also indicate that the user needs to log into the backend system after the user has already logged into the network. In addition, the backend parameters can also initiate an authentication process to determine if the user is already logged into the network and is automatically authenticated to operate the backend system based on network authentication. it can. If the backend parameters indicate that a software plug-in is required to properly interface with the backend application and the MFD, the MFD sends data to the document manager server 40 requesting receipt of the software plug-in. Send.

  FIG. 2 illustrates a browser 25 of the MFD 20 configured to exchange information between the MFD 20 and the document manager server 40 according to one embodiment of the present invention. An example of browser 25 is disclosed in US patent application Ser. No. 10 / 243,643 filed Sep. 16, 2002, the entire contents of which are incorporated herein by reference. Further details of the browser 25 are described below. FIG. 2 shows the software components of the document manager server 40 (including the authentication device 260 configured to perform the authentication function). The document manager server 40 also includes a management device 265 that allows a system administrator to manage the system 5. For example, the system administrator can access the profiler 280 via the management device 265 to set up user profiles and / or MFD profiles for the MFDs 10-30 connected to the document manager server 40. is there. A directory gateway 270 is also included in the document manager server 40. Directory gateway 270 is configured to communicate with directory server 60. The document manager server 40 also includes a document router 275 configured to route documents received from the MFD to the appropriate applications 70, 80 and 90.

  As shown in FIG. 2, the MFD 20 includes, for example, an engine control service (ECS) 200 that controls the scanning engine of the MFD 20. A memory control service (MCS) 205 controls access to the memory of the MFD 20. The operation panel control service (OCS) 215 generates an output to be displayed on the touch panel type liquid crystal display (LCD) of the MFD 20. The display and user interface of the MFD 20 is not limited to an LCD display, but any other suitable device (LCD, light emitting diode (LED) display, cathode ray tube (CRT) display, plasma display, keypad, and / or Or a keyboard or the like), or a combination of devices. The OCS 215 can generate, for example, a normal menu for MFD operation and the menu shown in FIGS. 3A to 3D. A system control service (SCS) 225 controls and / or monitors the sensors in the MFD 20. For example, the SCS 225 controls touch screen sensors, paper jam sensors, and scan processing sensors. Therefore, the SCS 225 can manage the state of the MFD 20 based on information from the sensor. A network control service (NCS) 220 controls communication between the browser 25 and the document manager server 40. Optionally, a secure socket layer (SSL) in the form of a communication formatting device or routine provides additional security for communication between the NCS 220 and the browser 25. A command input service (CIS) 240 processes input information from, for example, the LCD touch panel and / or keypad of the MFD 20. MFD users can enter information and commands using the LCD touch panel and keypad. The CIS 240 can process the aforementioned information and commands entered by the user (eg, forwarded to the CIS 240 by the SCS 225). The CIS 240 can generate a command (eg, a display command) based on the process described above and send the command to other components of the MFD (eg, to the OCS 215 for displaying graphics on the LCD). It is. The CIS 240 can also exchange information and commands with the NCS 220 for processing with the browser 25 with respect to the server 40.

  A normal MFD includes ECS, MCS, OCS, NCS, SCS, and CIS, which are firmwares that implement and control each hardware component of the MFD. However, in the present invention, the NCS 220 is configured to communicate with the browser 25. For example, the NCS 220 has a further function of communicating using the HTTP protocol. NCS 220 is also configured to communicate with server 40 such that NCS 220 exchanges data between browser 25 and server 40. For example, the NCS 220 can send identification information to the server 40 and receive a profile, can receive a selected email address from the server 40, or the NCS 220 can receive login information. Can be transmitted to the server 40 and a user authentication confirmation can be received from the server 40 (and the directory server 60) during the authentication process. The NCS 220 can also receive plug-in information from the document manager server 40 that can activate the authentication procedure or change the user interface depicted in FIGS. 3A-3D.

  The browser 25 includes an HTTP command processor 235 that communicates with a network control service (NCS) 220 of the MFD 20. For example, a request for an email address entered by the user via the MFD keypad, or a request for display of information on the LCD (such as FIGS. 3A-3D) is sent from the NCS 220 to the browser 25 by the HTTP command processor 235. It is possible to transfer. The HTTP command processor 235 can exchange data in the HTML format with the HTML parser 250 of the browser, and can exchange data in the XML format with the XML parser 255. The parsers 250 and 255 can check the syntax of the data from the HTTP command processor 235 and process the data of the HTTP command processor 235. The present invention may include a conventional parser that is normally included as part of a compiler.

  The HTTP command processor 235 can comprise program code or software plug-ins that implement a specific application (such as a user authentication process that can be implemented by the directory service of the server 40). HTTP command processor 235 can process information based on the definition of a particular application. For example, the HTTP command processor 235 can process information (user name, password, etc.) given by the user and generate an HTTP request to the server 40 based on this process. The HTTP command processor 235 can send this HTTP request to be sent to the server 40 to the NCS 220. The HTTP command processor 235 can also receive plug-in information regarding specific back-end system functions. The above plug-in allows the user to add processing instructions, metadata, and other index information to the image file transmitted to the document manager server 40.

  The HTTP command processor 235 can also process information received from the server 40 (via the NCS 220). For example, the HTTP command processor 235 can receive an HTTP response generated by the server 40 that includes a profile having parameters or software plug-ins that operate the MFD. The HTTP command processor 235 can process this information and generate commands to control the MFD with the information (eg, display a menu with appropriate buttons, or scan job for a particular user ID). -It is possible to request the MFD to scan by parameters). As another example, the HTTP command processor 235 can generate an LCD panel graphic drawing command. The HTTP command processor 235 can send the command to be executed to the appropriate MFD firmware (eg, OCS 215). For example, the OCS 215 can do this by receiving a graphic drawing command and displaying a graphic (eg, FIGS. 3A-3D) on the LCD panel.

  3A-3D illustrate user interfaces 300-303 for providing instructions to the user and touch sensitive buttons (eg, buttons 305-330) for providing user input to the system shown in FIG. An example is shown. As described above, the user interfaces 300-303 are preferably LCD touch panels, but any combination of display and input devices (LCD, LED, CRT, plasma display, keypad, and / or keyboard, etc.) But is not limited to these).

  FIG. 3A represents a user interface 300 that is displayed when a user login is activated or when a tab 305 is selected by the user. The “login” user interface 300 prompts the user to enter a login “username” 311, a “password” 312, and a “domain” 313 corresponding to the network domain the user is trying to access. including. When selected, the user is also presented with a “login” button 350 that causes the document manager server 40 to initiate the sending of the user's username and domain name to the network domain controller 50. When selected, each field is also presented with a “Reset” 355 button that clears the data entered by the user. The purpose of defining a domain name is to allow a user to log on to a specific network that can provide the user with a specific service or connectivity.

  When the user selects the tab 310, the MFD displays the user interface 301 depicted in FIG. 3B. This allows the user to enter appropriate information, thereby allowing the user to email the processed image. When the user selects the tab 315, the MFD displays the user interface 302 shown in FIG. 3C. This allows the user to enter information to send the processed image by facsimile. When the user selects the “Documentum” tab 320, the MFD displays the user interface 303 depicted in FIG. 3D. This allows the user to enter specific parameters and enable specialized authentication procedures for the specified backend application. The documentum is represented as an example of a back-end system, but various additional user interfaces for a particular back-end system can be similarly customized and displayed. Selecting tab 325 causes the MFD to display a user interface that allows the user to enter document scan settings. When the user selects tab 300, the MFD displays a user interface that displays a job log that records parameters appropriate for the preceding job performed by the MFD.

  The user interfaces 300-303 depicted in FIGS. 3A-3D also include a system display portion 360 that displays system messages (such as time and date, error messages, or instructions to the user). For example, an error message is displayed if the user cannot be authenticated to the network or application. The user interfaces 300-303 can be configured in several ways based on the applications available to users of the MFD.

  FIG. 3B shows a user interface 301 that is displayed when the user selects the “Email” tab 310. The user interface 301 includes a “Subject” line 301 that allows the user to enter the subject of an email sent by the user. The interface further includes a “To:” field 360 and a “CC:” field 365 in which the email address for which the email is to be received is displayed. The “BC:” field or the “BCC:” field can also be displayed and edited by the user. The user interface 301 also includes an “add name” button 339 and an “exclude” button 341 for easily modifying and editing the email address to which the message is sent. Also included in the user interface 301 is a “logout” tab 306 that allows the user to logout and terminate the image processing.

  FIG. 3C shows the user interface 302 that is displayed when the user selects the “Light Fax” tab 310. Although Light Fax is represented as an exemplary embodiment of a facsimile processing server, any other suitable facsimile processing server can be implemented as well. Facsimile user interface 302 is similar to the email interface depicted in FIG. 3B, but includes a “billing code” field 366 instead of “CC:” field 365 and “To:” field 360 instead of “To:” field 360. It includes a “Fax Number” field 367. The “Billing Code” field can be used to enter a billing code associated with the job being processed and can be stored in a database to properly track the billing information for the faxed job. Also included in the user interface 302 is a “logout” tab 306 that allows the user to logout and terminate image processing. The sending process for sending a facsimile will be described in more detail below with reference to FIG.

  FIG. 3D shows a user interface 303 that is displayed when the user selects the “Documentum” tab 320. Documentum is an exemplary brand of digital file management system used to manage, store, and perform various other file management processes on stored documents / records / multimedia files. When the user selects the “Documentum” tab 320, the user interface is displayed and the user is prompted to log in to the “Documentum” system. The user interface 303 includes prompts for “user name” 375, “password” 380, and “dock base” 385. The system also includes a “Login to Documentum” button 369 and a “Reset” button 370. The “Login to Documentum” button triggers the sending of user login information to the documentum system, thereby allowing the user to authenticate and gain access to the documentum system. When the user gains access to the document system, the document can be stored in a specific location, the document can be retrieved for printing, and the retrieved document can be sent to the specified recipient. It is possible to send an e-mail. Other functions can also be performed based on the selected back-end application. Also included in the user interface 303 is a “logout” tab 306 that allows the user to logout and terminate the image processing. Although “documentum” is represented as an example of a back-end system, any other back-end application can be treated similarly. In addition, the user interface can be customized to increase or decrease the user options included depending on the number of backend applications supported. The sending process for sending the scanned image to the backend system is described in further detail below with reference to FIG.

  FIGS. 4A and 4B and FIGS. 5 through 11 are flowcharts illustrating steps performed in a method used to manage documents by the document manager server 40 in accordance with various embodiments of the invention.

  The process shown in FIG. 4A shows a method performed by the document manager server 40. In step 400, the document manager server 40 receives a request for a profile from an image processing device or MFD. This request may include identification information identifying the request MFD. The identification information may include an MFD serial number and / or MFD group identification information and other identification information. The group identification information is, for example, that the MFD belongs to a specific department of the organization, and the group has a specific function (eg, legal, accounting, marketing) or a specific location (eg, floor, building, town, state) , Country), or a specific security level, etc. Alternatively, the identification information allows the document manager server 40 to check for additional identification information (department, group, etc.) as described above, or any other additional information.

  In step 405, the document manager server 40 checks whether the MFD is registered, for example, by checking the identification information in the register storing the registered MFD. If the MFD is registered, at step 410, the document manager server 40 searches for a profile assigned to the MFD. If the MFD is not registered, at step 415, the document manager server 40 can compare the number of registered MFDs with a predetermined number. This predetermined number may be, for example, the maximum number of devices licensed to use a particular application connected to the document manager server 40. This predetermined number (and information identifying its associated application) can be stored in the document manager server 40, for example, depending on the license agreement between the network application and the organization that benefits from the MFD. 5, 25, 100, or any desired number. License information can also be included in the MFD profile so that the MFD can change its user interface and functionality accordingly. If the number of registered image processing devices is less than the predetermined number, the document manager server 40 can register the MFD at step 420 and search for a profile assigned to the MFD at step 410. If the number of registered image processing devices is equal to the predetermined limit, the document manager server 40 can send a message to the MFD at step 425. This message can be an error message indicating that the services available to the document manager server are not available to the MFD because the maximum number of licensed MFDs has been reached.

  At step 430, the document manager server 40 determines available delivery options (eg, fax server, email server) and adds this information to the profile. In step 435, the document manager server 40 determines available intermediate processing systems and adds this information to the profile. In step 440, the document manager server 40 checks for available back-end systems and adds this information to the profile. This process optionally includes the addition of plug-ins that allow the MFD to implement customized functions that allow it to work with a particular backend system. In step 445, the document manager server 40 sends the profile and any plug-ins to the registered image processing apparatus.

  The document manager server 40 can repeat the above process for several image processing apparatuses. If the image processing devices belong to the same group in the organization, the document manager server 40 can transmit the same profile to each image processing device. After the MFD receives the profile from the document manager server 40, the MFD may display the initial display user based on various parameters provided in the profile and corresponding plug-ins, as described next with reference to FIG. 4B.・ It is possible to create an interface.

  The process shown in FIG. 4B illustrates a method performed by an image processing device (eg, MFD) and may begin, for example, when the image processing device is turned on by a user. In step 450, the MFD sends a request for the profile to the document manager server 40. As described above, this request may include identification information such as a serial number of the image processing apparatus. In step 455, the MFD queries whether a profile has been received from the document management server 40. If the profile was not received, but instead an error message was received from the document manager server 40, the MFD displays a message at step 460. If a profile is received, the MFD processes the received profile at step 465. Next, at step 467, the MFD determines whether the backend application that requires the software plug-in is enabled by the reception profile. If a software plug-in is required, at step 468, the MFD sends a message to the document manager server, and the document manager server sends the required plug-in to the MFD. Plug-ins can be used by the MFD to assist in creating or customizing the user interfaces 3A-3D necessary to interface with available back-end systems. The software plug-in may also be received in conjunction with profile information or simultaneously or at any other time. As part of this process, the MFD can generate a display as a function of profile parameters. For example, the MFD may generate a specific menu or user interface based on the backend processing system and intermediate processing system identified in the profile. The aforementioned user interface or menu can be generated from additional plug-in information corresponding to the backend and intermediate processing system received at the MFD from the document manager server. This step of customizing the user interface based on the received profile and plug-in information allows the user or user corresponding to the backend processing system or intermediate processing system to which the MFD is not authorized to access the user interface or menu Prevents MFD from presenting options. In step 465, the MFD can also display graphics on its LCD based on the default settings.

  The parameters supplied in the profile may correspond to arbitrary functions in the case of MFD. Other functions are enabled by default in the MFD so that the MFD automatically displays the graphics corresponding to the available functions without querying whether the profile indicates that the default functions are enabled. Is done. The parameter corresponding to the above default function may not be part of the profile. In the example shown in FIG. 4B, the login function, fax function and LDAP function are optional, so the MFD queries for its enablement by reviewing the parameters included in the profile. Furthermore, in this example, the email function is enabled by default, so the MFD does not query for the aforementioned function. The invention is not limited to this example, and other combinations of arbitrary / default functions are within the scope of the invention.

  In step 470, the MFD queries whether the profile indicates whether the login function is enabled. If the login function is enabled, the MFD displays a login button on its LCD panel at step 475. If the login function is not enabled, the MFD jumps to step 480. Step 480 queries whether the profile indicates whether the fax option is enabled. If the fax function is enabled, the MFD displays or enables the fax tab 315 on the LCD at step 485. If the fax option is not enabled, the MFD jumps to step 490. In step 490, the MFD sets an MFD automatic logout timer based on the timer value provided in the profile.

  In step 495, the MFD queries whether the profile indicates whether the LDAP option is enabled. If the LDAP option is enabled, at step 497, the MFD sets the base distinguished name (DN) of the LDAP query provided as part of the profile. Unless a narrower search field is required, the base DN will have a default search field where an LDAP search is performed. If the LDAP option is not enabled, the MFD skips step 497. After performing the above steps, the MFD has completed the initial user interface of the MFD (such as the user interface shown in FIGS. 3A-3D). The present invention is not limited to the order of the steps shown in FIGS. 4A to 4B.

  Using the initial user interface and other menus displayed by the MFD, the MFD user can access various services available on the network via the document management server 40. In general, the document manager server 40 receives job information from the image processing apparatus, processes the job information in the document manager server 40, and transmits the processed information to an application connected to the document manager server 40.

  FIG. 5 illustrates a method performed by the MFDs 10-30 to authenticate a user according to one embodiment of the present invention. In step 505, the MFD queries whether a command to display a login user interface is received from the user. For example, the user can press a login button on the LCD of the MFD 20 (such as the “login” button 305 of the user interface 300 shown in FIG. 3A). In step 510, the MFD 20 displays a login user interface if a command is received. In step 515, the MFD 20 queries whether login information is received from the user. For example, the MFD 20 can query whether the user has entered a username, password, and domain name.

  When the login information is received, the MFD 20 sends the login information to the document manager server 40. The document manager server 40 receives the login information, processes it, and sends the processed login information to the network domain controller 50. The domain controller 50 verifies the login information, sends an authentication confirmation to the document manager server 40, and the document manager server transfers the confirmation to the MFD 20. At step 525, the MFD 20 queries whether an authentication confirmation has been received from the document manager server 40. When the MFD 20 receives the user authentication, in step 530, the MFD 20 downloads from the document manager server 40 to display the user's home page. The user's home page may be a default (portal) page initially displayed after authentication. In the present invention, this home page can be generated based on the result of user authentication and the corresponding plug-in received for the received profile information. Although the term “homepage” is used, the present invention can display any desired information. In the preferred embodiment, a “help” button and / or an “about” button may be provided on the user's home page to provide instructions and information for using the system of the present invention. As will be described later, the user can also log in to the back-end application from the MFD 20.

  FIG. 6 shows a method for user authentication of the MFD 20 after the user has already logged into the network domain. In step 601, the user activates the network login procedure shown in FIG. 5 by pressing the “Login” tab. The user then enters login information at step 602 and initiates transfer of login information as described above in FIG. If the login was successful at step 603, the document manager server sends the profile, plug-in and other necessary information to the MFD 20 at step 604. Thus, the user's customized interface is displayed, including the tabs described with respect to FIGS. 3B-3D. Once the customized interface is displayed, the user can select from a number of available options.

  When the “e-mail” tab is pressed in step 605, a process for sending an e-mail from the MFD is started. If this option is selected, the user is allowed to modify the user interface 301 depicted in FIG. 3B at step 606 (the list of recipients and the subject of the sent email at step 607). ) Is presented. Once the user has entered the appropriate information, the start key is enabled on the MFD at step 608, and the user can trigger scanning of the image and subsequent email delivery. The user is then prompted at step 609 with an option to perform further processing operations. If the user desires further processing, processing returns to step 604. If the user makes a selection at step 609 indicating that he no longer wishes to perform further processing, the image processing is terminated at step 610.

  If the user selects the “Light Fax” tab at step 611, processing proceeds to step 612. In step 612, a profile received by the MFD from the document manager server, associated plug-in information and other related information is used by the MFD to require another authentication process to access the facsimile application. Determine whether. If authentication is not required, a “light fax” user interface 302 is displayed at step 614. However, if user authentication is required to access the fax application, a login user interface is displayed at step 613. When the user inputs the requested authentication information and sends it to the facsimile server, the facsimile server checks the user authentication against the registered user database. If the user is authenticated by the facsimile server, the “light fax” user interface 302 is displayed and enabled at step 614. However, if user authentication is not successful, an error message is displayed to the user (eg, in the system message area 360). Once the user is authenticated, at step 615, the user can enter a billing code, fax number, subject of the outgoing fax, and any additional optional information. Once this information is entered, the user activates scanning by pressing a “start” key at step 608 to activate subsequent facsimile transmission (described below) of the image. The user is then prompted at step 609 with an option to perform further processing operations. If the user desires further processing, processing returns to step 604. If the user selects No in step 609, the image processing ends.

  A software plug-in (and other information) received by the MFD from the document manager server 40 if the “Documentum” tab 320, or a tab representing any other backend application, is pressed in step 617. Is used in step 618 to determine if a subsequent authentication process is required for the user to gain access to the back-end system. If user authentication is required, a “documentum” login user interface 303 is displayed at step 619. The user is then prompted to enter a “user name”, “password” and “dock base” and send the aforementioned parameters to the back-end system. The back-end system then authenticates the user against the registered user's database and determines whether the user has been granted access to the system. However, if user authentication is not successful, an error message is displayed, for example, in the system message area 360, and the user is denied access to the system.

  Once the user has been granted access to the document backend application, the images can be processed by MFD, and management, storage, retrieval, and other file management operations can be performed at the back displayed in step 620. It can be done on the processed image using the end application interface. In step 621, the user can also send index information, metadata, and other customized processing information regarding the processing of the scanned image. Once the appropriate information is entered by the user, the start key is enabled at step 608 and the user can launch the backend process as described below. The user is then prompted at step 609 with an option to perform further processing operations. If the user desires further processing, processing returns to step 604. If the user decides to terminate the process in step 609, the image processing is terminated in step 610. For any other suitable back-end application, the processing described for the documentum application can be similarly performed and the user interface can be similarly customized.

  In addition, MFD users document the routing of documents to applications connected to a document manager server (such as a fax server, email server, file format conversion system, OCR system, document management system, and file storage system). It is possible to make a request to the manager server 40. In this case, the job information includes a document and a request for routing the document to the application.

  FIG. 7 is an example of code included in the software plug-in sent from the document manager server to the MFD. Once the plug-in is received and processed by the MFD, the MFD will allow the user to add specific processing instructions, index data or metadata to the image file before being processed by the image processing device. Can be done. The software plug-in is optionally not sent to the MFD until the MFD receives the back-end parameters and determines the back-end application enabled by the MFD. The MFD then sends a message to the document manager server indicating that the particular backend application is enabled. The document manager server responds by sending a software plug-in to the MFD that allows all necessary modifications to the MFD user interface and corresponding functions. Plug-ins also allow the MFD to make decisions regarding the type of user authentication required for a user to gain access to a particular network application. In addition, the software plug-in determines whether the user is authenticated on another system and determines whether the authentication procedure allows the user to have access to a particular application. Enable the device. The user interface and MFD can also be customized based on the aforementioned information and plug-ins to allow user access to specific functions of specific backend systems. The above functions are described in further detail below.

  FIG. 8 shows an example of how a document is sent by the document manager server 40 using MFD to the backend system. As described above, the back-end system can be, for example, a document management system or a scan file system. The MFD user can log in to the network as described above in FIG. 5 at step 800, and the MFD user can select a back-end system, such as a document management system, at step 805. . The MFD then examines the information received from the document manager server 40 (eg, profiles, plug-ins, etc.) and determines at step 807 whether the user is required to log in to the backend system. If user login is not required, processing continues at step 810. If login is required, the user logs into the back-end system at step 809, as previously described in FIG. In step 810, the MFD user can select a document type using the MFD input device. For example, a menu of document types can be displayed such that the user can select one of the types using the MFD touch-sensitive user interface. The document type can be used as index information when storing the document in the backend system. At step 815, the MFD user can select a destination folder where the document is stored in the back-end system. Again, this can be done by selecting a folder from a list displayed on the user interface, or the destination folder can be entered using the keyboard. At step 820, the MFD user can enter a document name and / or other index information. In step 825, the user can enter an account number. The account number can be used for administrative purposes (billing, accounting, activity monitoring, etc.) by the document manager server 40 and / or the backend system. In step 830, the user can select the amount on the invoice if the document type is invoice. Other fields can be displayed on the MFD display, prompting the user to enter information (eg, numeric values) for various documents.

  In step 835, the document can be set on the MFD scanning surface. At step 840, the document is scanned. In step 845, the job information is sent to the document manager server 40, for example, as an XML file. The job information may in this case include the selected back-end system, scanned document, request to route the document to the back-end system, document type, destination folder, document name, account number and amount. In step 850, the document manager server 40 processes the job information received from the MFD. In one embodiment, the document manager server 40 sends the document to the intermediate processing system based on the selected backend system. That is, the document manager server 40 can recognize that the selected back-end system requires a specific file format. The document manager server 40 automatically ensures that the document received from the MFD is in the proper format before sending it to the backend system. In step 855, the document manager server 40 sends at least a portion of the processed job information (eg, a document) to the backend system.

  FIG. 9 shows an example of a method for sending a fax by the document manager server 40 using MFD. In step 900, the MFD user can log in as described above in FIG. At step 905, the MFD user can press a fax button, such as fax button 315 shown in FIGS. 3A-3D. The MFD then examines the information received from the document manager server 40 (eg, plug-ins, profiles, etc.) and determines in step 907 whether the user is required to log in to the facsimile server. If user login is not required, processing continues at step 910. If login is required, the user logs into the facsimile server at step 909 as previously described in FIG. If the login was successful, at step 910, the MFD user can enter the fax number using an MFD input device such as a touch screen or keypad. Alternatively, the fax number can be displayed and selected after accessing the global directory 60. At step 915, the MFD user enters a fax memo. This fax memo is sent with the document being faxed. The user can input a fax memo using the MFD input device. In steps 920-925, the user can enter a billing code, if necessary, to fax the document from the MFD. Whether a billing code needs to be input can be determined by profile parameters. The billing code corresponds to the entity that is billed for the fax service.

  In step 930, the document can be set on the MFD scanning surface. In step 935, the scan settings can be changed if desired, for example, by accessing a scan settings menu displayed on the user interface. At step 940, the document is scanned. In step 945, the job information is sent to the document manager server 40, for example, as an XML file. The job information may in this case include the scanned document, the request to route the document to the fax server, the scanning parameters, and the specified fax number. In step 950, the document manager server 40 processes the job information received from the MFD. At step 955, the document manager server 40 sends at least a portion of the processed job information to the fax server to complete the fax transmission.

  FIG. 10 shows an example of a method for sending a document processed by the intermediate processing system to the back-end system by the document manager server 40 using MFD. As described above, the intermediate processing system can be, for example, a file format conversion system or an OCR system. At step 1000, the MFD user can log in as previously described in FIG. Furthermore, in order to begin this process step, if necessary, it must already be authenticated against the identified back-end system, as described above in FIGS. In step 1005, the MFD user can select an intermediate processing system (such as an OCR system and / or a PDF conversion system). For example, the user touches the button 320 shown in FIG. 3A (the tab is labeled “Documentum”, but any other backend application can be labeled as appropriate), A file format screen that allows the user to select a conversion / recognition system is displayed. In another embodiment, the file format screen can be displayed automatically by the MFD, based on its profile, or based on back-end system selection. In step 1010, the document can be set on the MFD scanning surface. At step 1015, the document is scanned. In step 1020, the job information is sent to the document manager server 40, for example, as an XML file. The job information may then include a request to route the document to the selected intermediate processing system, scanned document, intermediate processing system, and other systems (if desired). In step 1025, the document manager server 40 processes the job information received from the MFD.

  In step 1030, the document manager server 40 transmits at least a portion of the processed job information (eg, a document) to the intermediate processing system. At step 1035, the intermediate processing system processes the document. In step 1037, an authentication step is performed to determine if user authentication is required to process the scanned document by the backend system. If user authentication is required, the user must log into the backend system as described above in FIG. At step 1040, the intermediate processing system sends the processed document to the document manager server 40. At step 1045, the document manager server 40 receives the processed document, and at step 1050, sends the processed document to the back-end system.

  FIG. 11 shows an example of a method for sending a document to the back-end system and printing the document by the document manager server 40 in the MFD. As described above, the back-end system can be, for example, a document management system or a scan file system. In this example, the document management system manages confidential documents (such as medical and insurance records) and requires specific information to record the document requester and reason. At step 1100, the MFD user can log in as described above in FIG. At step 1105, the MFD user can select a back-end system, such as a medical records document management system. For example, the user can touch the button 320 shown in FIGS. 3A to 3D. At step 1110, the MFD user is prompted to enter the name of the document requester. The MFD then examines the information received from the document manager server 40 and determines at step 1112 whether the user is required to log in to the backend system. If login is required, the user logs in to the back-end system at step 1114 as previously described in FIG. At step 1115, the MFD user can enter the reason for the document request. This step can be performed by selecting a reason from a list displayed on the user interface, or the reason can be entered using a keyboard. At step 1120, the MFD user can enter a document type, and at step 1125, the user can enter document description information and / or other index information.

  In step 1130, the document can be set on the MFD scanning surface. In step 1035, the scan settings can be changed if desired. At step 1140, the document is scanned. In step 1145, the job information is sent to the document manager server 40, for example, as an XML file. The job information may in this case include the scanned document, the name of the requester, the reason for the document request, the document type, and the document description. In step 1150, the document manager server 40 processes the job information received from the MFD. In step 1155, the document manager server 40 sends at least a portion of the processed job information to the MFD and backend system. For example, the document manager server 40 can send the document to the MFD again for printing and send it to the document management system for storage.

  12 and 13 show an example of the MFD 20 including a central processing unit (CPU) 931 and various components connected to the CPU 931 by an internal bus 932. The CPU 931 processes a plurality of tasks while monitoring the state of the MFD 20. Components connected to the CPU 931 may accept read only memory (ROM) 933, random access memory (RAM) 934, hard disk drive (HDD) 935, floppy disk 907. A floppy disk drive 936, a communication interface (I / F) 938, and a modem device 939. Further, the control panel 937, the scanner device 940, the printer device 941, and the image processing device 942 can be connected to the CPU 931 via the bus 932. Both the I / F 938 and the modem device 939 are connected to the communication network 100.

  In the preferred embodiment, the MFD 20 program code instructions are stored on the HDD 935 via an ID card. Alternatively, the program code instructions can be read by the FDD 936, transferred to the RAM 934, and stored on the floppy 907 so that the instructions can be executed and executed by the CPU 931. . The aforementioned instruction may be an instruction for performing the aforementioned MFD function. The aforementioned commands allow the MFD 20 to interact with the document manager server 40 via the browser 25 and control the control panel 937 and the image processing apparatus of the MFD 20.

  During startup of the MFD 20, program code instructions can be read by the CPU 931, transferred to RAM, and executed by the CPU 931. Alternatively, program code instructions can be loaded into ROM 933. Therefore, in the present invention, any one of the floppy (registered trademark) disk 907, HHD935, RAM934, and ROM933 corresponds to a computer-readable storage medium that can store program code instructions. Other devices and media capable of storing instructions according to the present invention include, for example, magnetic disks, optical disks (including DVDs), magneto-optical disks (such as MOS), and semiconductor memory cards (PC cards, compact). -Flash cards, smart media, memory sticks, etc.).

  In the preferred embodiment, the control panel 937 provides a user interface (such as the user interfaces 300-303 shown in FIGS. 3A-3D) that displays information that allows the user of the MFD 20 to interact with the document manager server 40. )including. The display screen can be an LCD, a plasma display device, or a cathode ray tube CRT display. While the display screen may or may not be integrated with the control panel 937, it can simply be coupled to the control panel 937 by a wired or wireless connection. The control panel 937 may include keys for entering information or for requesting various actions. Alternatively, the control panel 937 and the display screen can be a keyboard, mouse, remote control, display screen touch, voice recognition, or eye movement tracking, or a combination thereof.

  FIG. 14 shows a block diagram of a server 40 according to an embodiment of the present invention. FIG. 15 is a schematic diagram of the server 40. Server 40 includes a central processing unit 1000 (CPU) that communicates with a number of other devices via system bus 1500. The server 40 includes a random access memory (RAM) 1900 that hosts temporary stored values that are used to implement document authentication, routing, and management functions.

  A normal personal computer or computer workstation with sufficient memory and processing capabilities can also be configured to operate as the server 40. The central processing unit 1000 is configured to send large amounts of data and perform a significant number of numerical calculations in communications and database searches. A Pentium® 4 microprocessor (such as 3.4 GHz Pentium® 4 manufactured by Intel) or an Athlon 64 3.5 GHz processor from Advanced Micro Devices (AMD) may be used for the CPU 1000. Other suitable processors and multiple processors or workstations can also be used.

  ROM 1800 is preferably included in semiconductor form, but other read-only memory forms including optical media can be used to host the host application software and temporary results. ROM 1800 connects to system bus 1500 for use by CPU 1000. ROM 1800 includes computer readable instructions that can be executed by CPU 1000 to perform the various authentication, routing, and management functions described above associated with scanned documents from MFDs. The input controller 1600 is connected to the system bus 1500 and includes an interface with various peripheral devices (including a keyboard 1610 and a pointing device such as a mouse 1620). The input controller 1600 may include various ports such as a PS2 port or a mouse port in the form of a universal serial bus (USB) port, for example. The keyboard port of the input controller 1600 is in the form of a mini-DIN port, but other connectors can be used. The input controller 1600 includes a sound card connection that allows a user to attach a microphone speaker or external sound source via an external jack on the sound card. The input controller 1600 may further include a serial port or a parallel port.

  The disk controller 1400 is in the form of an IDE controller, and via a ribbon cable, a floppy disk drive 1410, a hard disk drive 1420, a CD-ROM drive 1180, and a compact -Connect to disk 1190. In addition, a PCI expansion slot is provided on the disk controller 1400 that hosts the CPU 1000 or on the motherboard. Expansion graphics port An expansion slot is provided to provide 3D graphics with fast access to main memory. Hard disk 1210 may also include a CD-ROM that may be readable and writable. The communication controller 1300 comprises a connection via an Ethernet connection to the network 1310, which can be, for example, the network 100. In one embodiment, the connection to the network 1310 and the communication controller 1300 is made by a plurality of connections (including cable modem connections, DSL connections, dial-up model connections, and the like) that connect to the communication controller 1300.

  The I / O controller 1200 is not limited to TCP / IP, IPX, IPX / SPX, or NetBEUI, but can be connected to external components such as an external hard disk 1210 and printer 1220 (for example, MFD 10 to 30). It is provided by an RS232 port, SCSI bus, Ethernet, or other network connection that supports any desired network protocol, including:

  A display controller 1100 interconnects the system bus 1500 to a display device (such as a cathode ray tube (CRT) 1110). Although a CRT is shown, various other display devices (such as LCD and plasma display devices) can be used.

  The mechanisms and processes described herein may be implemented using a conventional general purpose microprocessor programmed according to the teachings herein, as will be appreciated by those skilled in the art. Appropriate software coding can be readily created by skilled programmers based on the teachings of the present disclosure, as will also be apparent to those skilled in the software art. In particular, computer programs for authenticating, routing, and managing documents according to the present invention include several, including but not limited to C, C ++, Fortran, and basic, as will be appreciated by those skilled in the art. Can be described in the computer language. The present invention can also be implemented by making an application specific integrated circuit or by interconnecting appropriate network of normal circuit components, as will be readily apparent to those skilled in the art.

  The present invention thus also includes computer-based products that can include instructions that can be hosted on a storage medium and that can be used to program a computer to perform processing according to the present invention. This storage medium can be any type of disk (floppy (registered trademark) disk, optical disk, CD-ROM, magneto-optical disk, ROM, RAM, EPROM, EEPROM, flash memory, magnetic card or optical card, or electronic Including, but not limited to, any type of media suitable for storing general instructions).

  Effectively, the present invention includes U.S. patent application Ser. No. 09 / 795,438, filed Mar. 1, 2001, US 2002/2002, the entire contents of which are incorporated herein by reference. Document management system disclosed in US patent application Ser. No. 10 / 243,645 filed on Sep. 16, 2000 and U.S. Patent Application No. 10 / 294,607 filed on Nov. 15, 2002 And methods can be incorporated.

  Obviously, numerous additional modifications and variations of the present invention are possible in light of the above teachings. Thus, it is to be understood that, within the scope of the appended claims, the invention may be practiced otherwise than as specifically described herein.

  This application is based on US priority application Ser. No. 11 / 092,836, filed Mar. 30, 2005, the contents of which are incorporated herein by reference.

1 is a block diagram showing an overall system configuration according to an embodiment of the present invention. It is a block diagram which shows the browser of the image processing apparatus by one Example of this invention. FIG. 6 is a diagram illustrating an example of a login user interface displayed on the image processing apparatus according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of an email scan user interface displayed on an image processing device according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of a fax scan user interface displayed on an image processing device according to an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of a back-end system scan user interface displayed on an image processing device according to an embodiment of the present invention. 4 is a flowchart illustrating a process of obtaining profile information by a multifunction peripheral according to an embodiment of the present invention. 4 is a flowchart illustrating a process performed by a multifunction peripheral when profile information is received according to an embodiment of the present invention. 4 is a flowchart illustrating steps performed in user authentication according to an embodiment of the present invention. 7 is a flowchart illustrating a user authentication process of a further network application after a user logs into the network according to an embodiment of the present invention. FIG. 3 illustrates exemplary code for a plug-in associated with a bank end application, according to one embodiment of the invention. 4 is a flowchart illustrating steps performed when sending a document to a back-end system, according to one embodiment of the invention. FIG. 6 illustrates steps performed in sending a fax by a document manager server according to one embodiment of the present invention. 6 is a flowchart illustrating steps performed when sending a document processed by an intermediate processing system to a backend system, according to one embodiment of the invention. FIG. 6 is a flowchart illustrating steps performed in a process for sending a document to a back-end system and printing the document according to one embodiment of the present invention. FIG. 1 is a block diagram illustrating an image processing apparatus according to an embodiment of the present invention. 1 is a schematic diagram illustrating an image processing apparatus according to an embodiment of the present invention. FIG. 3 is a block diagram illustrating a document manager server according to one embodiment of the present invention. FIG. 2 is a schematic diagram illustrating a document manager server according to an embodiment of the present invention.

Claims (74)

A method for managing documents,
Transmitting identification data from the image processing apparatus to the server;
Retrieving information corresponding to a plurality of network applications based on the identification data by the server;
Transmitting the information from the server to the image processing apparatus;
Receiving the information in the image processing apparatus;
Changing the function of the image processing device based on the received information. The method of claim 1, wherein the step of transmitting the identification data comprises
A method comprising the step of transmitting identification data corresponding to the identification of the image processing apparatus. The method according to claim 2, wherein the step of transmitting the identification data comprises:
A method comprising the step of transmitting a serial number of the image processing apparatus. The method of claim 1, wherein the step of transmitting the identification data comprises
A method comprising the step of transmitting identification data corresponding to the identity of a user of the image processing apparatus. The method according to claim 4, wherein the step of transmitting the identification data comprises:
A method comprising sending a username and password. The method of claim 1, wherein the step of retrieving the information comprises:
A method comprising a step of retrieving profile information corresponding to the image processing apparatus. 7. The method according to claim 6, wherein the step of retrieving the information includes
Retrieving profile information including identification information for each of the plurality of network applications. The method of claim 1, wherein
Determining that the image processing apparatus is not registered in the server based on received identification data;
Registering the image processing device at the server when the license information stored by the server indicates that an unregistered image processing device can be registered. The method of claim 1, wherein the step of retrieving the information comprises:
Retrieving at least one executable file corresponding to each of the plurality of network applications. The method according to claim 1, wherein the step of changing the function of the image processing apparatus includes:
Changing the user interface of the image processing apparatus based on the received information. The method of claim 1, wherein
Receiving the information comprises receiving an executable file corresponding to at least one of the plurality of network applications;
The step of changing the function of the image processing device includes the step of executing the executable file, and the step of changing the function of the image processing device based on the execution of the executable file. . The method of claim 1, wherein
A method further comprising selecting information to be transmitted to the image processing device based on a network application connected to the server. The method of claim 1, wherein
A method further comprising determining whether user authentication is required for at least one of the plurality of network applications based on the information received by the image processing device. The method of claim 1, wherein
A method further comprising authenticating a user of the image processing device to one of the plurality of network applications by transmitting authentication information from the image processing device to the server. The method of claim 1, wherein
Determining whether the user of the image processing device is currently authenticated on a server and whether subsequent user authentication is required to access at least one of the plurality of network applications. Method. The method of claim 1, wherein
Transmitting user authentication information from the image processing apparatus to the server;
Authenticating a user to the plurality of network applications using the user authentication information. The method of claim 1, wherein
A method further comprising storing information corresponding to each network application connected to the server in the server. The method of claim 17, wherein
The method further comprising the step of transmitting the stored information corresponding to each network application connected to the server to a plurality of image processing devices connected to the server. The method according to claim 1, wherein the step of transmitting the information to the image processing apparatus includes:
Only when the profile stored in the server corresponding to the image processing device indicates that the image processing device is authorized to access the plurality of network applications, the information is sent to the image processing device. A method comprising the step of transmitting. The method of claim 1, wherein
Receiving job information from the image processing apparatus at the server;
Processing the job information at the server;
Transmitting processed job information from the server to at least one of the plurality of network applications connected to the server. The method of claim 20, comprising
The step of receiving job information comprises the step of receiving job information relating to a document processed by the image processing apparatus;
The method of transmitting processed job information comprises the step of transmitting the job information to a document management system. The method according to claim 20, wherein the step of transmitting the processed job information includes:
Transmitting the processed job information to the plurality of network applications. The method of claim 20, comprising
A method further comprising adding index information to the image before the image is processed by the image processing device. The method of claim 23, wherein adding index information to the image comprises
A method comprising adding index information from a user interface before the image is processed by the image processing device. The method of claim 20, comprising
A method further comprising adding processing instructions to the image before the image is processed by the image processing device. The method of claim 25, wherein adding processing instructions to the image comprises
Adding instructions from a user interface to the image before the image is processed by the image processing device. A system for managing documents,
An image processing apparatus having an interface unit;
A server having a module and an interface connected to the interface unit of the image processing apparatus;
The interface unit of the image processing device is configured to transmit identification data from the image processing device to the server;
The module of the server is configured to retrieve information stored in the server corresponding to a plurality of network applications based on the identification data received from the interface unit of the image processing device;
The interface of the server is configured to transmit the information from the server to the image processing device;
The interface unit of the image processing device is configured to receive the information in the image processing device;
The system configured to change a function of the image processing device based on the received information. 28. The system of claim 27, wherein
The system configured such that the interface unit of the image processing apparatus transmits identification data including information corresponding to the identification of the image processing apparatus. The system of claim 28, wherein
The system configured such that the interface unit of the image processing apparatus transmits identification data including a serial number of the image processing apparatus. 28. The system of claim 27, wherein
The system configured such that the interface unit of the image processing apparatus transmits identification data including information corresponding to the identity of the user of the image processing apparatus. 30. The system of claim 30, wherein
A system in which the interface unit of the image processing apparatus is configured to transmit identification data including a user name and a password. 28. The system of claim 27, wherein
The system configured to retrieve the information stored in the server, including profile information corresponding to the image processing device. A system according to claim 32, wherein
A system wherein the module is configured to retrieve the information stored on the server, including identity of the plurality of network applications. 28. The system of claim 27, wherein
The server is configured to determine that the image processing apparatus is not registered in the server based on received identification data;
A system configured to register the image processing device when the licensing information stored by the server indicates that the server can register an unregistered image processing device. A system according to claim 32, wherein
A system configured to retrieve the information stored on the server, wherein the module includes at least one executable file corresponding to each of the plurality of network applications. 28. The system of claim 27, wherein
The system of the image processing device is configured to change a user interface of the image processing device based on the information received from the server. 28. The system of claim 27, wherein
The interface unit of the image processing device is configured to receive an executable file corresponding to at least one of the plurality of network applications;
A system in which the processor is configured to execute the executable file and change the function of the image processing device based on the execution of the executable file. 28. The system of claim 27, wherein
A system wherein the interface of the server is configured to transmit information including the identity of a network application connected to the server. 28. The system of claim 27, wherein
A system configured to determine, based on the information received by the image processing device, that the processor of the image processing device requires user authentication for at least one of the plurality of network applications. 40. The system of claim 39, wherein
A system configured to authenticate a user to one of the plurality of network applications by transmitting authentication information from the image processing device to the server, the interface unit of the image processing device. 28. The system of claim 27, wherein
The processor determines based on the received information whether the user is currently authenticated on the server and whether subsequent user authentication is required to access at least one of the plurality of network applications. Configured system. 28. The system of claim 27, wherein
The interface unit of the image processing apparatus is configured to transmit user authentication data to the server;
The server is configured to authenticate a user to the plurality of network applications using identification information. 28. The system of claim 27, wherein
A system in which the server is configured to store information corresponding to each network application connected to the server. 44. The system of claim 43, wherein
A system in which the interface of the server is configured to transmit the stored information corresponding to each network application connected to the server to a plurality of image processing devices connected to the server. 28. The system of claim 27, wherein
The interface of the server only when the profile stored in the server corresponding to the image processing device indicates that the image processing device is authorized to access the plurality of network applications. A system configured to transmit the information to an image processing device. 28. The system of claim 27, wherein
The interface of the server configured to receive job information from the interface unit of the image processing apparatus;
A processor of the server configured to process the job information;
The system further comprising: the server interface configured to transmit processed job information from the server to at least one of the plurality of network applications connected to the server. The system of claim 46, wherein
A system in which the application connected to the server is a document management system, and the job information is a document. The system of claim 46, wherein
The system wherein the interface of the server is configured to send the processed job information to the plurality of network applications connected to the server. The system of claim 46, wherein
Further comprising a user interface portion of the image processing device configured to allow a user to input index data information;
A system in which a processor of the image processing device is configured to add the index information to an image before the image is processed by the image processing device. The system of claim 46, wherein
Further comprising a user interface portion of the image processing device configured to allow a user to input processing instructions;
A system in which a processor of the image processing device is configured to add the instructions to an image before the image is processed by the image processing device. A system for managing documents,
Means for transmitting identification data from the image processing apparatus to the server;
Means for retrieving, by the server, information corresponding to a plurality of network applications based on the identification data;
Means for transmitting the information from the server to the image processing device;
Means for receiving the information in the image processing apparatus;
And a means for changing the function of the image processing device based on the received information. 52. The system of claim 51, wherein
The means for transmitting the identification data is a system for transmitting identification data including identification of the image processing apparatus. 53. The system of claim 52, wherein
The means for transmitting identification data is a system for transmitting identification data including a serial number of the image processing apparatus. 52. The system of claim 51, wherein
The means for transmitting the identification data is a system for transmitting identification information including identification of the user of the image processing apparatus. The system of claim 54, wherein
The means for transmitting the identification data is a system for transmitting identification information including a user name and a password. 52. The system of claim 51, wherein
The system for extracting the information includes the information including profile information corresponding to the image processing apparatus. 57. The system of claim 56, wherein
The means for extracting information extracts the information including profile information, and the profile information includes identification information of each of the plurality of network applications. 52. The system of claim 51, wherein
The server is configured to determine that the image processing apparatus is not registered in the server based on the reception identification data;
A system configured to register the image processing device when the licensing information stored by the server indicates that the server can register an unregistered image processing device. 52. The system of claim 51, wherein
The system for retrieving the information, wherein the means for retrieving information includes at least one executable file corresponding to each of the plurality of network applications. 52. The system of claim 51, wherein
The means for changing the function of the image processing apparatus changes the user interface of the image processing apparatus based on the received information. 52. The system of claim 51, wherein
The means for receiving receives an executable file corresponding to at least one of the plurality of network applications;
A system in which the changing means executes the executable file and changes the function of the image processing apparatus based on the execution of the executable file. 52. The system of claim 51, wherein
The system further comprising means for modifying the information transmitted to the image processing device based on a network application connected to the server. 52. The system of claim 51, wherein
A system further comprising means for determining whether user authentication is required for at least one of the plurality of network applications based on the information received by the image processing device. 52. The system of claim 51, wherein
A system further comprising means for authenticating a user of the image processing apparatus by sending authentication information to one of the plurality of network applications to the server. 52. The system of claim 51, wherein
The system further comprising means for determining whether a user of the image processing device is currently authenticated on a server and whether subsequent user authentication is required to access at least one of the plurality of network applications. 52. The system of claim 51, wherein
The system further comprising means for authenticating a user on a plurality of network applications by transmitting authentication data to the server and authenticating the user to the plurality of network applications using the user authentication information. 52. The system of claim 51, wherein
The system further comprises means for storing information corresponding to each network application connected to the server, and the stored information is accessible from a plurality of image processing devices connected to the server. 52. The system of claim 51, wherein
The means for transmitting the information is only when the profile stored in the server corresponding to the image processing device indicates that the image processing device is authorized to access the plurality of network applications. A system for transmitting the information to the image processing apparatus. 52. The system of claim 51, wherein
Means for receiving job information from the image processing device at the server;
Means for processing the job information at the server;
Means for transmitting processed job information from the server to at least one of the plurality of network applications connected to the server. 70. The system of claim 69, comprising:
Means for receiving job information receives job information relating to a document to be processed by the image processing apparatus;
A system in which means for transmitting processed job information transmits the job information to a document management system. 70. The system of claim 69, comprising:
A system in which the means for transmitting the processed job information transmits the processed job information to the plurality of network applications. 70. The system of claim 69, comprising:
The system further comprising means for adding index information to the image before the image is processed by the image processing device. 70. The system of claim 69, comprising:
A system further comprising means for adding processing instructions to an image before the image is processed by the image processing device. A computer program,
A procedure for transmitting identification data from the image processing apparatus to the server;
A procedure for causing a server to retrieve information corresponding to a plurality of network applications based on the identification data;
Receiving the information in the image processing apparatus;
A computer storage medium storing computer program code for causing a computer to execute a procedure for managing a document, including a procedure for changing a function of the image processing device based on the received information. A computer program provided.

Images