JP2007207174A - Document processor and image forming device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce the burden of architect work by applying the NET Framework to the architecture of a document processor and an image forming device containing the document processor. <P>SOLUTION: CPU 1 operates various kinds of functional parts in the image forming device by the architecture called NET Framework. This net architecture is constituted by a presentation layer 21 which takes charge of a user interface, a business layer 22 which takes charge of business logics, a data layer 23 which takes charge of input to/output from a data source, a security part 24 which takes charge of security principles, authentication, recognition, safe communications, profile management, and audit, an operation management part 25 which takes charge of exception management, monitoring, setting, metadata, service location management, a communication part 26 which takes charge of selection of a communication model, synchronization, formatting, schema, and protocols. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a document processing apparatus and an image forming apparatus, and more particularly, to a document processing apparatus and an image forming apparatus having a function of processing a document using a net architecture.

  2. Description of the Related Art A multifunction peripheral including a document processing apparatus and an image forming apparatus in recent years includes a plurality of applications and has a huge function. The software constituting these applications has been increasing in scale and complexity. In addition, the multifunction peripherals provide new value in cooperation with WEB and other devices by supporting not only stand-alone but also distributed environments.

As conventional techniques related to the document processing apparatus and the image forming apparatus as described above, for example, techniques described in Patent Documents 1 and 2 are known. Patent Document 1 discloses a technique for a system and a method for printing a document by a user having a mobile computing device, and Patent Document 2 discloses a resource transfer system and a resource transfer method. Techniques related to this are disclosed.
JP 2004-062889 A JP 2004-355504 A

  In such a situation, when developing an application system for a multifunction machine, it is essential to define an appropriate architecture at an early stage of development. However, designing an architecture for a distributed environment application is a daunting task. That is, the worker is required to have various knowledge and skills such as security, transaction, user interface, distributed object, component, data, messaging, naming service, and directory. In order to reduce such an architect's work, an architecture called NET Framework is known as a distributed application implementation base.

  An object of the present invention is to apply the above-described NET Framework to a document processing apparatus and an architecture of an image forming apparatus including the document processing apparatus, thereby reducing the work of an architect and an image forming apparatus. To provide an apparatus.

  The first means of the present invention for solving the above object is a CPU for centrally controlling each unit, a ROM in which fixed data such as programs are stored in advance, a RAM in which various data are stored in a rewritable manner, data NVRAM, which is a non-volatile RAM stored without erasing data, a communication control unit that controls connection to the network, an operation panel that controls the interface with the user, and a memory that is used for storing and storing image data and control programs In a document processing apparatus in which a modem that enables data communication with an apparatus and an external device is connected via a bus, the CPU controls each component constituting the document processing apparatus by a net architecture. However, the net architecture is a presentation that takes charge of the user interface. Application layer, business layer in charge of business logic, data layer in charge of input / output to / from data source, security principle, authentication, authorization, secure communication, profile management, security department in charge of audit, exception management, monitoring, setting And an operation management unit in charge of managing the location of metadata and services, and a communication unit in charge of selection, synchronization, format, schema, and protocol of communication models.

  According to a second means of the present invention, in the first means, the net architecture further includes a device layer for performing conversion of image information, grasping a device status, and scheduling a processing request according to the device capability. It is characterized by having.

  The third means of the present invention is characterized in that, in the second means, a plug-in can be installed in each layer and each part constituting the net architecture.

  According to a fourth means of the present invention, in the third means, the plug-in installed in the device layer has a function of setting and controlling an optional device to be connected. .

  According to a fifth means of the present invention, in the third means, the plug-in installed in the business layer has a function of processing a document.

  The sixth means of the present invention is a CPU for centrally controlling each unit, a ROM for storing fixed data such as programs in advance, a RAM for storing various data in a rewritable manner, without erasing the data. NVRAM that is stored non-volatile RAM, communication control unit that controls connection to the network, operation panel that controls user interface, scan / print that causes the scanner unit and printer unit to execute input / output of image data In an image forming apparatus in which an engine, a storage device used for storing and storing image data and control programs, and a modem that enables data communication with an external device are connected via a bus, the CPU includes: A network architecture is used to control each component constituting the image forming apparatus and The technology is the presentation layer responsible for the user interface, the business layer responsible for the business logic, the data layer responsible for input / output to the data source, the security principles, authentication, authorization, secure communication, profile management, security responsible for auditing Department, exception management, monitoring, setting, metadata, operation management section in charge of service location management, communication model selection, synchronization, format, schema, communication section in charge of protocol Features.

  According to a seventh means of the present invention, in the sixth means, the network architecture further controls the device handling paper, converts image information, grasps the status of the device, and requests processing according to the capability of the device. And a device layer for performing scheduling.

  According to an eighth means of the present invention, in the seventh means, a plug-in can be installed in each layer and each part constituting the net architecture. According to a ninth means of the present invention, in the eighth means, the plug-in installed in the device layer has a function of setting and controlling an optional device to be connected. .

  The tenth means of the present invention is the ninth means characterized in that the plug-in installed in the business layer has a function of processing a document.

  According to the present invention, it is possible to construct a document processing apparatus and an image forming apparatus that are compatible with a distributed environment, and it is possible to ensure high quality by adopting a proven architecture.

  Hereinafter, embodiments of a document processing apparatus and an image forming apparatus according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of an image forming apparatus according to an embodiment of the present invention. The image forming apparatus shown in FIG. 1 includes a document processing apparatus.

  The image forming apparatus shown in FIG. 1 is a so-called microcomputer and includes a CPU 1 that centrally controls each unit. The CPU 1 includes a ROM 3 in which fixed data such as programs are stored in advance via the image bus 2, a RAM 4 in which various data are stored in a rewritable manner, and a nonvolatile RAM in which data is stored without being deleted. An NVRAM 5 is connected. In addition, the image bus 2 has an image through the communication control unit 7 that controls connection with the network 6, an operation panel 9 that has an LCD touch panel that controls an interface with the user through the panel control unit 8, and an image through the engine control unit 10. Used to store and store image data and control programs via the scan / print engine 11 and the disk driver 12 that cause the scanner unit and printer unit to execute data input / output (reading paper originals and printing on transfer paper). A HDD 13 is connected to a storage device 13 and a modem 14 that enables data communication with an external device through a public line. In the above description, the document processing apparatus is configured by removing the engine control unit 10 and the scan / print engine 11.

  Since the processing operation of the image forming apparatus configured as described above is well known and does not constitute the gist of the present invention, the description thereof is omitted here.

  FIG. 2 is a diagram illustrating the configuration of an architecture called “NET Framework” in which the CPU 1 operates various functional units in the image forming apparatus.

  The illustrated net architecture includes a presentation layer 21 responsible for a user interface, a business layer 22 responsible for business logic, a data layer 23 responsible for input / output to a data source, security principles, authentication, authorization, secure communication, profile management, Security unit 24 in charge of audit, exception management, monitoring, setting, metadata, operation management unit 25 in charge of service location management, communication unit 26 in charge of communication model selection, synchronization, format, schema, protocol Composed.

  When the net architecture as described above is applied to an image forming apparatus including a document processing apparatus, the roles of the above-described layers are as follows.

Presentation layer 21
Responsible for system windows via operation panel, browser, WEB service, etc. Then, the business layer is used to grasp the requirements for the system and realize the requirements. In addition, feedback information from the business layer is presented to the requester.

Business layer 22
Responsible for business logic (upper functions) of document processing. This layer keeps track of the logic of the document manipulation application. A workflow is presented to the user of the system, and a series of processes necessary for document operations such as operation reception, authentication, document input / output processing, and accounting are in charge.

  Furthermore, for document operations, scheduling is performed to logically change the processing order. In addition, understand the contents of data handled by the document manipulation application and take charge of them in a batch. Data handled by the document operation application includes information such as an account, a stored document, an address book, a device configuration / capability, setting information, and image data. The storage location (local / remote) is known, and data input / output to / from the actual physical device is delegated to the data layer.

Data layer 23
Responsible for I / O to local / remote storage areas. Then, a service for accessing the local / remote data storage area is provided. In addition, the device status is grasped, and processing requests are scheduled according to the device capabilities.

Security section 24
Responsible for authentication, access control, encryption, and security log control. A mechanism for providing common security to users, services, data resources, device resources, and the like is provided. It also leaves security history information.

Operation management unit 25
Responsible for controlling plug-ins, date and time management, memory management, timers, debugging, history, power, and reports. A mechanism for easily realizing addition, change, and deletion of functions is provided. Also, it provides a mechanism that the entire application and other policies use in common.

Communication unit 26
Responsible for control of network, FAX, and WEB services. Then, data is transmitted and received according to the protocol with the external system.

  FIG. 3 is a diagram for explaining another configuration example of an architecture called “NET Framework” in which the CPU 1 operates various programs in the image forming apparatus.

  The net architecture described with reference to FIG. 2 is basically an architecture for a PC application applied to the document processing apparatus according to the present invention. In the embodiment of the present invention, however, in order to control the device further, As shown in FIG. 3, a hierarchy “device layer” 27 specific to the document processing apparatus is added as a hierarchy specific to the embedded application.

  The device layer 27 is in charge of controlling a device that handles paper such as a scanner and a plotter in order to read a document and print a document, and is also in charge of conversion (processing, format conversion, etc.) of image information. The device layer 27 is used by the business layer when grasping the status of the device, scheduling processing requests according to the capabilities of the device, and realizing document operations.

  FIG. 4 is a diagram for explaining the installation of plug-ins in each layer and each part of the net architecture shown in FIG.

  As shown in FIG. 4, each of the presentation layer 21, business layer 22, data layer 23, device layer 27, security unit 24, operation management unit 25, and communication unit 26 constituting the net architecture has various functions. Plugins can be installed.

  A plug-in for the device layer 27 can easily or automatically perform various settings after an ADF (Auto Documents Feeder) as an optional device, an image processing system device, or the like is physically connected. This can eliminate the need for complicated manual settings.

  Further, a plug-in for document processing can be installed as a plug-in for the business layer 22. By using document processing plug-ins, general application usage of plug-ins, such as customization of document operations and individual sales of plug-ins (download from the Internet, media, etc.) should be applied to document processing. Is possible.

  Further, although connection is omitted here, various plug-ins can be installed in layers other than the layers described above and each function unit in order to add optional functions.

  FIG. 5 is a diagram for explaining the functions of each layer and each part constituting the net architecture and the mutual use relationship.

  In FIG. 5, the presentation layer 21 receives a request from the user, uses the business layer 22, and the business layer 22 uses the data layer 23. The security unit 24, the operation management unit 25, and the communication unit 26 are used from all layers. Specifically, the presentation layer 21 authenticates the user with respect to the business layer 22, processing for starting and ending operations, processing for setting operation conditions, processing for executing operations, processing for registering, referring to, and editing information. The business layer 22 notifies the presentation layer 21 of the results of these processes. The business layer 22 instructs the data layer 23 to read data and write data, and the data layer 23 notifies the business layer 22 of the results of these processes. The business layer 22 instructs the device layer 27 to perform data reading processing, printing processing, and image processing processing, and the device layer 27 notifies the business layer 22 of the results of these processing.

  In addition, the security unit 24 performs processing for confirming the user authority. The operation management unit 25 executes processing for fetching plug-ins, processing for removing plug-ins, processing for enabling functions, processing for disabling functions, processing for registering history, and processing for creating report images. The communication unit 26 performs data transmission and reception processing.

  FIG. 6 is a flowchart for explaining an operation example of image reading processing in the net architecture. Next, this will be described.

  Upon receiving an image reading request from the user, the presentation layer 21 requests the business layer to execute an image reading operation (step 61). The business layer 22 causes the device layer 27 to read an image (step 62). The device layer 27 performs an image reading process. If a plug-in exists in this process, the plug-in is caused to execute a reading process (step 63). After the reading is completed, the plug-in notifies the device layer 27 of the execution result (step 64). The device layer 27 notifies the business layer 22 of the read result (step 65). The business layer 22 notifies the presentation layer 21 of the execution result (step 66).

  In the foregoing, what is plugged in is, for example, a function for controlling an image reading device such as an optional device such as ADF.

  FIG. 7 is a flowchart for explaining an operation example of image processing in the net architecture. Next, this will be described.

  Upon receiving an image processing request from the user, the presentation layer 21 requests the business layer 22 to execute an image processing operation (step 71). The business 22 layer causes the device layer 27 to perform image processing (step 72). The device layer 27 performs image processing (step 73). If a plug-in exists in the process of step 73, the plug-in is caused to execute image processing (step 74). After completing the image processing, the plug-in notifies the device layer 27 of the execution result (step 75). The device layer 27 notifies the business layer 22 of the image processing result (step 76). The business layer 22 notifies the execution result to the presentation layer 21 (step 77).

  In the foregoing, what is plugged in is, for example, a control function of the image processing device.

  FIG. 8 is a flowchart for explaining an operation example of the print processing in the net architecture, which will be described next.

  Upon receiving a print request from the user, the presentation layer 21 requests the business layer 22 to execute a print operation (step 81). The business layer 22 causes the device layer 27 to perform printing (step 82). The device layer 27 performs a printing process (step 83). If a plug-in exists in the process of step 83, the plug-in is caused to execute a printing process (step 84). After printing, the plug-in notifies the device layer 27 of the execution result (step 85). The device layer 27 notifies the printing result to the business layer 22 (step 86). The business layer 22 notifies the execution result to the presentation layer 21 (step 87).

  In the foregoing, what is plugged in is, for example, a printing device control function.

  The processes of the flowcharts illustrated in FIGS. 6 to 8 can be combined and executed as a single operation. For example, if the operations are executed in the order of FIGS. 6, 7, and 8, a document can be copied. When operations are executed in combination, the request for operation execution from the presentation layer 21 to the business layer 22 may be performed a plurality of times or may be combined once.

  The image reading process, the image processing process, and the printing process described above can be combined with an image accumulation process that does not use a device layer, a transmission process, a reception process, and the like. Thereby, operations such as reading image accumulation, reading image transmission, and reception image printing can be realized. Also, there may be a plurality of plug-ins in each process (reading, image processing, printing). In that case, which plug-in is used in each process, and which plug-in is used in combination. Determine whether.

  FIG. 9 is a flowchart for explaining an example of the processing operation for setting the operating condition in the net architecture, which will be described next.

  Upon receiving the operation condition setting request from the user, the presentation layer 21 requests the business layer 22 to set the operation condition (step 91). The business layer 22 performs an operation condition setting process (step 92). When a plug-in is used during the process of step 92, the plug-in is caused to execute an operation condition setting process (step 93). After the operation condition setting process, the plug-in notifies the business layer 22 of the execution result (step 94). The business layer 22 notifies the setting result to the presentation layer 21 (step 95).

  In the foregoing, what is plugged in is, for example, an operating condition setting control function. The operation condition setting is an operation setting such as reading, image processing, and printing, and includes setting of the number of copies, aggregation setting, density setting, and the like.

  If the plug-in is, for example, a stamp printing function, when the user selects stamp printing setting, the business layer 22 executes the stamp printing function plug-in (step 93).

  Also, for example, when the aggregation setting is a default function (that is installed as a standard), when the user selects the aggregation setting, the business layer 22 is aggregated only by setting processing (step 92) in the business layer 22. Setting may be performed, or a plug-in called aggregation setting may be installed as a standard, and the business layer 22 may execute aggregation setting as a plug-in (step 93).

  There may also be a plurality of operating condition setting plug-ins. In this case, it is determined in the setting process which plug-in is used and which plug-in is used in combination.

  FIG. 10 is a flowchart for explaining an example of the information registration processing operation in the net architecture, which will be described next.

  When the presentation layer 21 receives a request for information registration from the user, the presentation layer 21 requests the business layer 22 to register information (step 101). The business layer 22 performs information registration processing (step 102). If a plug-in is used in the processing of step 102, the plug-in is caused to execute registration processing (step 103). The plug-in writes data to be registered in the data layer 23 (step 104). After the writing is completed, the data layer 23 notifies the plug-in of the result (Step 105). The plug-in notifies the business layer 22 of the execution result (step 106). The business layer 22 notifies the presentation layer 21 of the registration result (step 107).

  In the foregoing, information refers to user information, address book information, stored document information, and the like. The plug-in used may differ depending on the information, but the flowchart is the same.

  In the above, what is plugged in is, for example, a control function of information management. When registering user information, the standard user information is only the user name and password, and extended user information (shortcut button for each individual) When the user registers the extended user information, the business layer 22 executes the extended user information management function as a plug-in (step 103). .

  Further, for example, when a user registers standard user information, the business layer 22 may perform only the information registration process (step 102) in the business layer, or a standard user information management plug-in is standard. As an installed configuration, the business layer 22 may execute a standard user information management function that is a plug-in (step 103).

  FIG. 11 is a flowchart for explaining another example of the information registration processing operation in the net architecture, which will be described next. The example described here is an example in the case of registering information in a remote data storage area.

  When the presentation layer 21 receives a request for information registration from the user, the presentation layer 21 requests the business layer 22 to register information (step 111). The business layer 22 performs information registration processing (step 112). If a plug-in is used in the process of step 112, the plug-in is caused to execute a registration process (step 113). The plug-in writes data to be registered in the data layer 23 (step 114). The data layer 23 transmits data to be registered to the communication unit 26 (step 115). The communication unit 26 notifies the transmission result to the data layer 23 (step 116), and the data layer 23 notifies the plug-in of the business layer 22 of the end of writing (step 117). The plug-in notifies the business layer 22 of the execution result (step 118). The business layer 22 notifies the presentation layer 21 of the registration result (step 119).

  In the above, what is plugged in is, for example, an information management control function. For example, when registering information, standard information registration is performed in the local data storage area, and is performed in the remote data storage area. If the thing is a plug-in, the business layer 22 executes the plug-in when the user wants to register in the remote data storage area (step 113).

  Further, for example, when the user registers in the local data storage area, the business layer 22 may perform only the information registration process (step 112) in the business layer, or a standard information management plug-in is standard. As a mounted configuration, the standard information management function in which the business layer 22 is a plug-in may be executed (step 113).

  FIG. 12 is a flowchart for explaining an example of the information reference processing operation in the net architecture, which will be described next.

  When the presentation layer 21 receives a request for information reference from the user, the presentation layer 21 requests the business layer 22 to refer to the information (step 121). The business layer 22 performs information reference processing (step 122). If a plug-in is used in the process of step 122, the plug-in is caused to execute a reference process (step 123). The plug-in reads data to be referred to the data layer 23 (step 124). After completing the reading, the data layer 23 notifies the result to the plug-in of the business layer 22 (step 125). The plug-in notifies the business layer 22 of the execution result (step 126). The business layer 22 notifies the presentation layer 21 of the result information (step 127).

  In the foregoing, information refers to user information, address book information, stored document information, and the like. The plug-in used may differ depending on the information, but the flowchart is the same.

  Also, what is plugged in in this process is an information management control function. For example, when referring to user information, the standard user information is only the user name and password, and extended user information (shortcut buttons for each person, operation screens for each person, etc.) is used as a plug-in. When referring to typical user information, the business layer 22 executes an extended user information management function as a plug-in (step 123).

  Further, for example, when the user refers to standard user information, the business layer 22 may perform only the information reference processing (step 122) in the business layer, or a standard user information management plug-in is standard. As an installed configuration, the standard user information management function in which the business layer 22 is a plug-in may be executed (step 123).

  FIG. 13 is a flowchart for explaining another example of the information reference processing operation in the net architecture, which will be described next. The example described here is an example of referring to information in a remote data storage area.

  When receiving a request for information reference from the user, the presentation layer 21 requests the business layer 22 to refer to the information (step 131). The business layer 22 performs information reference processing (step 132). If a plug-in is used in the process of step 132, the plug-in is caused to execute a reference process (step 133). The plug-in reads data to be referred to the data layer 23 (step 134). The data layer 23 transmits a data acquisition request to the communication unit 26 (step 135). The communication unit 26 acquires the transmission result information and notifies the data layer 23 of the transmission result (step 136). The data layer 23 notifies the result information to the plug-in of the business layer 22 (step 137). The plug-in notifies the business layer 22 of the execution result (step 138). The business layer 22 notifies the presentation layer 21 of the result information (Step 139).

  In the foregoing, what is plugged in is an information management control function. For example, when referring to information, if the standard information reference is to the local data storage area and the remote data storage area is a plug-in, the user wants to reference the information in the remote data storage area The business layer 22 executes the plug-in (step 133).

  Further, for example, when the user refers to information in the local data storage area, the business layer 22 may perform only the information reference processing (step 132) in the business layer, or a plug-in called standard information management may be provided. As a configuration installed as a standard, the business layer 22 may execute a standard information management function in which plug-ins are executed (step 133).

  FIG. 14 is a flowchart for explaining an example of the information editing processing operation in the net architecture, which will be described next.

  When the presentation layer 21 receives a request for editing information from the user, the presentation layer 21 requests the business layer 22 to edit information (step 141). The business layer 22 performs information editing processing (step 142). If a plug-in is used in the process of step 142, the plug-in is caused to execute an editing process (step 143). The plug-in reads the data to be edited to the data layer 23 (step 144). After acquiring the data read result information, the data layer 23 notifies the plug-in of the business layer 22 of the result (step 145). The plug-in writes the edited data to the data layer 23 (step 146). After completing the writing, the data layer 23 notifies the plug-in of the business layer 22 of the result (step 147). The plug-in notifies the business layer 22 of the execution result (step 148). The business layer 22 notifies the editing result to the presentation layer 21 (step 149).

  In the foregoing, information refers to user information, address book information, stored document information, and the like. The plug-in used may differ depending on the information, but the flowchart is the same.

  What is plugged in in this process is an information management control function. For example, when editing user information, the standard user information is limited to the user name and password, and extended user information (shortcut button for each individual, operation screen for each individual, etc.) is used as a plug-in. When editing general user information, an extended user information management function in which the business layer is a plug-in is executed (step 143).

  For example, when the user edits standard user information, the business layer 22 may perform only the information editing process (step 142) in the business layer, or a plug-in called standard user information management is standard. As an installed configuration, a standard user information management function in which the business layer is a plug-in may be executed (step 143).

  FIG. 15 is a flowchart for explaining another example of the information editing processing operation in the net architecture, which will be described next. The example described here is an example of editing information in a remote data storage area.

  When the presentation layer 21 receives a request for editing information from the user, the presentation layer 21 requests the business layer 22 to edit information (step 151). The business layer 22 performs information editing processing (step 152). If a plug-in is used in the process of step 152, the plug-in is caused to execute an editing process (step 153). The plug-in reads data to be edited into the data layer (step 154). The data layer 23 transmits a data acquisition request to the communication unit (step 155). The communication unit 26 acquires request transmission result information, and notifies the data layer 23 of the transmission result (step 156). The data layer 23 notifies the result information to the plug-in of the business layer 22 (step 157). The plug-in writes the edited data to the data layer 23 (step 158). The data layer 23 transmits the edited data to the communication unit 26 (step 159). After receiving the transmission result, the communication unit 26 notifies the data layer 23 of the transmission result (step 15A). The data layer 23 notifies the end of writing to the plug-in of the business layer 22 (step 15B). The plug-in notifies the business layer 22 of the execution result (step 15C). The business layer 22 notifies the presentation layer 21 of the registration result (step 15D).

  In the foregoing, what is plugged in is an information management control function. For example, when editing information, if the standard information editing is performed in the local data storage area and the remote data storage area is a plug-in, the user wants to edit the information in the remote data storage area. Sometimes the business layer 22 executes the plug-in (step 153).

  For example, when the user edits information in the local data storage area, the business layer 22 may perform only the information editing process (step 152) in the business layer, or a plug-in called standard information management may be provided. As a standard configuration, the business layer 22 may execute a standard information management function in which plug-ins are executed (step 153).

  There may be a plurality of information management plug-ins described in FIGS. 10 to 15 described above. In that case, during each process (information registration process, reference process, edit process), it is determined which plug-in is used and which plug-in is used in combination.

  FIG. 16 is a flowchart for explaining an example of the processing operation of user authentication in the net architecture, which will be described next.

  Upon receiving a user authentication request from the user, the presentation layer 21 requests user authentication from the business layer 22 (step 161). The business layer 22 performs user authentication processing (step 162). If a plug-in is used in the process of step 162, the plug-in is caused to execute an authentication process (step 163). After authentication, the plug-in notifies the execution result to the business layer 22 (step 164). The business layer 22 notifies the authentication result to the presentation layer 21 (step 165).

  In the foregoing, what is plugged in is a user authentication control function. For example, when user authentication is performed, standard user authentication is performed using a user name and password, and authentication using other authentication (eg, vein authentication, fingerprint authentication, IC card authentication, etc.) is a plug-in. When authenticating using the latter, the business layer 22 executes the plug-in (step 163).

  Further, for example, when authenticating using the former (user name, password), the business layer 22 may perform only the user authentication processing (step 162) in the business layer, or a standard authentication plug-in is standard. As a configuration installed in the standard authentication, the business layer may perform standard authentication as a plug-in (step 163).

  There may be a plurality of user authentication plug-ins. In that case, it is determined in the user authentication process which plug-in is used and which plug-in is used in combination.

  Each process in the embodiment of the present invention described above is configured by a program and can be executed by a CPU provided in the image forming apparatus, and these programs are stored in a recording medium such as an FD, a CDROM, and a DVD. It can also be provided by digital information via a network.

  According to the above-described embodiment of the present invention, by setting an appropriate architecture, it is possible to set a development framework, improve reusability of parts, facilitate system integration, and It is possible to obtain an effect that the communication becomes easier. In addition, according to the embodiment of the present invention, it is possible to construct a document processing apparatus and an image forming apparatus that are compatible with a distributed environment, and to ensure high quality by adopting a proven architecture. Can do.

  Furthermore, according to the embodiment of the present invention, it becomes easy to use hardware attached to the apparatus, and by applying a plug-in, there is no need to perform complicated settings when an optional device is connected. In addition, it is possible to easily perform customization processing for document operations.

1 is a block diagram illustrating a configuration of an image forming apparatus according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an architecture configuration called a NET Framework in which a CPU operates various functional units in an image forming apparatus. FIG. 10 is a diagram illustrating another configuration example of an architecture called a NET Framework in which a CPU operates various programs in an image forming apparatus. It is a figure explaining installing a plug-in in each layer and each part of the net architecture shown in FIG. It is a figure explaining the function of each layer and each part which comprise a net architecture, and a mutual use relationship. 6 is a flowchart for explaining an operation example of image reading processing in a net architecture. It is a flowchart explaining the example of an operation | movement of the image process in a net architecture. 10 is a flowchart for explaining an operation example of print processing in a net architecture. It is a flowchart explaining the example of the processing operation of the operation condition setting in a net architecture. It is a flowchart explaining the example of the processing operation of the information registration in a net architecture. It is a flowchart explaining another example of the processing operation of the information registration in a net architecture. It is a flowchart explaining the example of the processing operation of the information reference in a net architecture. It is a flowchart explaining another example of the processing operation of the information reference in a net architecture. It is a flowchart explaining the example of the processing operation of the information edit in a net architecture. It is a flowchart explaining another example of the processing operation of the information editing in a net architecture. It is a flowchart explaining the example of the processing operation | movement of the user authentication in a net architecture.

Explanation of symbols

1 CPU
2 Image bus 3 ROM
4 RAM
5 NVRAM
6 Network 7 Communication control unit,
8 Panel control unit,
9 Operation Panel 10 Engine Control Unit 11 Scan / Print Engine 12 Disk Driver 13 Storage Device 21 Presentation Layer 22 Business Layer 23 Data Layer 24 Security Unit 25 Operation Management Unit 26 Communication Unit 27 Device Layer

Claims (10)

CPU that centrally controls each unit, ROM that stores fixed data such as programs in advance, RAM that stores various data in a rewritable manner, NVRAM that is a nonvolatile RAM that stores data without erasing it, A communication control unit that controls connection to the network, an operation panel that controls the interface with the user, a storage device that is used for storing and storing image data and control programs, and a modem that enables data communication with external devices In a document processing apparatus configured to be connected via
The CPU controls the constituent elements constituting the document processing apparatus by a net architecture,
The network architecture is responsible for the presentation layer responsible for the user interface, the business layer responsible for business logic, the data layer responsible for input / output to and from the data source, security principles, authentication, authorization, secure communication, profile management, and auditing. Security section, exception management, monitoring, setting, metadata, operation management section in charge of service location management, communication model selection, synchronization, format, schema, communication section in charge of protocol A document processing apparatus.   The document processing apparatus according to claim 1, wherein the network architecture further includes a device layer that performs conversion of image information, grasps a status of a device, and schedules a processing request according to a device capability.   3. The document processing apparatus according to claim 2, wherein a plug-in can be installed in each layer and each part of the net architecture.   4. The document processing apparatus according to claim 3, wherein the plug-in installed in the device layer has a function of setting and controlling an optional device to be connected.   4. The document processing apparatus according to claim 3, wherein the plug-in installed in the business layer has a function of processing a document. CPU that centrally controls each unit, ROM that stores fixed data such as programs in advance, RAM that stores various data in a rewritable manner, NVRAM that is a nonvolatile RAM that stores data without erasing it, Communication control unit that controls connection to the network, operation panel that controls the interface with the user, scan / print engine that causes the scanner unit and printer unit to execute input / output of image data, storage and storage of image data and control programs, etc. In an image forming apparatus configured to be connected to a storage device used for a data communication with an external device via a bus,
The CPU controls the constituent elements constituting the image forming apparatus by a net architecture,
The network architecture is responsible for the presentation layer responsible for the user interface, the business layer responsible for business logic, the data layer responsible for input / output to and from the data source, security principles, authentication, authorization, secure communication, profile management, and auditing. Security section, exception management, monitoring, setting, metadata, operation management section in charge of service location management, communication model selection, synchronization, format, schema, communication section in charge of protocol An image forming apparatus.   7. The network architecture according to claim 6, further comprising a device layer for controlling a device handling paper, converting image information, grasping a device status, and scheduling a processing request according to a device capability. Image forming apparatus.   8. The image forming apparatus according to claim 7, wherein a plug-in can be installed in each layer and each part of the net architecture.   9. The image forming apparatus according to claim 8, wherein the plug-in installed in the device layer has a function of setting and controlling an optional device connected thereto.   The image forming apparatus according to claim 9, wherein the plug-in installed in the business layer has a function of processing a document.

Images