JP2005175595A - Image forming apparatus and its production process - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus in which the man-hour required for developing a module is reduced, processing efficiency is enhanced, and hardware resources can be utilized effectively, and to provide its production process. <P>SOLUTION: The image forming apparatus comprising hardware resources for use in image formation processing and one or more applications each performing a process pertaining to image formation is further provided with an image processing succession means executing image processing including image transfer processing in the image forming apparatus being executed when each application performs a process pertaining to image formation, and a transfer sequence means for providing each application with the interface of the image processing succession means for performing a series of processes pertaining to image formation. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to the structure of software related to image formation, and more particularly to an image forming apparatus having a structure in which processes commonly performed in an image forming apparatus are unified, and a method for manufacturing the image forming apparatus.

  In recent years, there has been known an image forming apparatus (hereinafter referred to as a multifunction peripheral) in which functions of apparatuses such as a facsimile machine, a printer, a copy machine, and a scanner are housed in a single casing. In this multi-function apparatus, a display unit, a printing unit, an imaging unit, and the like are provided in one casing, and four types of applications corresponding to a facsimile, a printer, a copy, and a scanner are provided. Operates as a printer, copy and scanner.

  FIG. 15 shows an example of the software structure in the conventional multi-function machine in which a plurality of applications are installed. FIG. 15 shows the structure of software including a copy and printer application as an example.

  As shown in the figure, the copy transfer module includes an image storage control unit, a memory management unit, a driver control unit, and a copy transfer order control unit. The printer transfer module includes an image storage control unit, a memory management unit, an application drawing control unit, and a printer transfer order control unit.

  As shown in these configurations, the copy transfer module and the printer transfer module have a common function for image transfer. In the case of having the same processing as described above, an overlapping number of areas for storing a program for executing the function is required, so that hardware resources are wasted.

  In addition, if the vertical structure is closed by each module, such as the copy transfer module and printer transfer module described above, for example, it is possible to flexibly handle the contents received by e-mail using the printer transfer module. Can not.

  Another problem is that it takes twice time to perform the same function expansion such as adding an image storage format to two different modules.

  The copy transfer module and the printer transfer module described above include the same processing, and the processing for reading and storing different depending on the storage format of the image also includes the same processing except for the format. Providing a plurality of modules including such a process for each process is not preferable because it not only takes time for module development but also reduces processing efficiency and wastes hardware resources.

  In view of such problems, the present invention provides an image forming apparatus capable of reducing the effort of module development, improving processing efficiency, and effectively using hardware resources, and a method for manufacturing the image forming apparatus. For the purpose.

  In order to solve the above problems, the present invention provides an image forming apparatus having hardware resources used in image forming processing and one or more applications for performing processing related to image forming. Image processing inheritance means for executing image processing including image transfer processing in the image forming apparatus, which is executed when performing the processing related to the above, and a series of processing related to image formation to each of the applications And transfer sequence means for providing an interface for the image processing inheritance means.

  In order to solve the above problem, the present invention is characterized in that the series of processes is a combination of any two or more of image reading, printing, and storage.

  In order to solve the above problem, the present invention is characterized in that the image data management means acquires the storage area when the image forming apparatus is activated.

  In order to solve the above-mentioned problem, according to the present invention, the image processing inheriting unit includes a memory securing unit that secures a memory for storing the image, and a memory releasing unit that releases the secured memory. It is characterized by that.

  In order to solve the above problems, the present invention is characterized in that the memory securing means and the memory releasing means secure or release the memory via a memory management means for managing the memory.

  In order to solve the above-mentioned problem, the present invention includes a non-volatile storage unit for storing the image, and stores the image in the non-volatile storage unit in response to a request from the image processing inheritance unit. It has a storing means and an image reading means for reading an image stored in the nonvolatile storage means.

  In order to solve the above-mentioned problem, the present invention is characterized in that the image processing inheritance unit includes a cooperative storage unit that executes the image storage unit and another process in cooperation with each other.

  In order to solve the above-described problem, the present invention is characterized in that the image processing inheritance unit includes a cooperative reading unit that executes the image reading unit and another process in cooperation with each other.

  In order to solve the above-mentioned problem, the present invention is characterized in that the image processing inheritance means includes an image transfer means for outputting an image to the hardware resource or inputting an image from the hardware resource. And

  In order to solve the above-described problem, the present invention is characterized in that the image processing inheritance unit includes a cooperative transfer unit that executes the image transfer unit and another process in cooperation with each other.

  In order to solve the above problem, the present invention is characterized in that the image processing inheritance unit includes a transfer unit that causes the image transfer unit to transfer an image.

  In order to solve the above-described problem, the present invention is characterized in that the image processing inheritance unit includes a completion notification unit that notifies the completion of the image processing.

  In order to solve the above-described problems, the present invention provides a printer application that is a printer application, a copy application that is a copy application, a fax application that is a fax application, and a scanner application. It is one of the scanner applications.

  In order to solve the above problem, the present invention is characterized in that the format of the image stored in the nonvolatile storage means is any one of uncompressed, JPEG, and TIFF formats. .

  In order to solve the above problems, the present invention provides hardware resources used in image forming processing and image transfer processing in the image forming apparatus executed when processing related to image forming is performed. An image forming apparatus comprising: an image processing inheriting unit that executes image processing, and a transfer sequence unit that provides an interface of the image processing inheriting unit for performing a series of processes related to image formation. An image storage means adapted to the interface and performing the process related to the image formation; and an image storage inheriting means which is in a generalized relationship with the image processing inheriting means and storing the image in a nonvolatile storage means for storing the image; The image reading means for reading an image stored in the nonvolatile storage means and the image processing inheritance means are in a generalized relationship, and the image processing Inheritance means and having a driver for using the hardware resources.

  In order to solve the above problem, the present invention is characterized in that the series of processes is a combination of any two or more of image reading, printing, and storage.

  In order to solve the above problems, the present invention provides a printer application that is a printer application, a copy application that is a copy application, a fax application that is a fax application, and a scanner application. It is one of the scanner applications.

  In order to solve the above problem, the present invention is characterized in that the printer application prints or accumulates an image using the image processing inheritance unit.

  In order to solve the above problem, the present invention is characterized in that the copy application prints or scans an image using the image processing inheritance unit.

  In order to solve the above problem, the present invention is characterized in that the format of the image stored in the nonvolatile storage means is any one of uncompressed, JPEG, and TIFF formats. .

  In order to solve the above problem, the present invention is characterized in that the driver inputs an image from the hardware resource or outputs an image to the hardware resource.

  In order to solve the above-described problems, the present invention provides hardware resources used in image forming processing, one or more applications that perform processing relating to image formation, and each application performs processing relating to image formation. An image processing inheritance unit that executes image processing including image transfer processing in the image forming apparatus that is performed at the time of performing the image processing, and the image processing inheritance for performing a series of processing relating to image formation to each application In the manufacturing method of the image forming apparatus having the transfer sequence unit that provides the interface of the unit, the application link that associates the program of the application adapted to the interface provided by the transfer sequence unit and the program of the transfer sequence unit An image program for storing or reading the image; An image program linking stage associating the program of the image processing succeeding unit, and having said hardware resources for utilizing driver, a program and a driver link step of associating the said image processing succeeding unit.

  In order to solve the above problem, the present invention is characterized in that the series of processes is a combination of any two or more of image reading, printing, and storage.

  As described above, according to the present invention, it is possible to obtain an image forming apparatus that can reduce the effort of module development, improve processing efficiency, and effectively use hardware resources, and a method for manufacturing the image forming apparatus. .

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 shows a configuration diagram of an embodiment of an MFP according to the present invention. The MFP 1 is configured to include a software group 2, an MFP activation unit 3, and hardware resources 4.

  The MFP activation unit 3 is executed first when the MFP 1 is turned on, and activates the application layer 5 and the platform layer 6. For example, the MFP activation unit 3 reads the programs of the application layer 5 and the platform layer 6 from a hard disk device (hereinafter referred to as HDD) corresponding to the nonvolatile storage unit, transfers the read programs to the memory area, and activates them. . The hardware resource 4 includes a scanner 25, a plotter 26, and a hardware resource 24 such as an ADF (Auto Document Feeder).

  The software group 2 includes an application layer 5 and a platform layer 6 activated on an operating system (hereinafter referred to as OS) such as UNIX (registered trademark). The application layer 5 includes programs that perform processing unique to user services related to image formation such as printers, copies, faxes, and scanners.

  The application layer 5 includes a printer application 9 that is a printer application, a copy application 10 that is a copy application, a fax application 11 that is a fax application, and a scanner application 12 that is a scanner application.

  The platform layer 6 interprets a processing request from the application layer 5 and generates a hardware resource 4 acquisition request, and manages one or more hardware resources 4 to control the control service layer. 7 includes a system resource manager (hereinafter referred to as “SRM”) 21 that arbitrates acquisition requests from 7 and a handler layer 8 that manages hardware resources 4 in response to acquisition requests from the SRM 21.

  The control service layer 7 includes a network control service (hereinafter referred to as NCS) 13, a delivery control service (hereinafter referred to as DCS) 14, an operation panel control service (hereinafter referred to as OCS) 15, and a fax control service (hereinafter referred to as FCS) 16. , Engine control service (hereinafter referred to as ECS) 17, memory control service (hereinafter referred to as MCS) 18, user control service (hereinafter referred to as UCS) 19, system control service (hereinafter referred to as SCS) 20, etc. It is configured to include service modules.

  The platform layer 6 is configured to have an API 28 that can receive a processing request from the application layer 5 using a predefined function. The OS executes the software of the application layer 5 and the platform layer 6 in parallel as processes.

  The process of the NCS 13 provides a service that can be commonly used for applications that require network I / O. Data received from the network side according to each protocol is distributed to each application, and data from each application. Mediation when sending to the network side.

  For example, the NCS 13 controls data communication with a network device connected via a network by HTTP (HyperText Transfer Protocol Daemon) by HTTP (HyperText Transfer Protocol).

  The process of the DCS 14 performs services such as document distribution. The process of the OCS 15 controls an operation panel serving as information transmission means between the operator and the main body control. The FCS16 process provides APIs for sending and receiving faxes from the application layer 5 using the PSTN or ISDN network, registering / quoting various fax data managed in the backup memory, reading faxes, receiving faxes, etc. To do.

  The process of the ECS 17 controls the engine unit such as the scanner 25, the plotter 26, and other hardware resources 24. The process of the MCS 18 performs memory control such as acquisition and release of memory and use of the HDD. The UCS 19 performs processing related to the user.

  The process of the SCS 20 performs processing such as application management, operation unit control, system screen display, LED display, hardware resource management, and interrupt application control.

  The process of the SRM 21 controls the system and manages the hardware resources 4 together with the SCS 20. For example, the process of the SRM 21 performs arbitration according to an acquisition request from an upper layer that uses the hardware resources 4 such as the scanner 25 and the plotter 26, and controls execution.

  Specifically, the process of the SRM 21 determines whether or not the requested hardware resource 4 is available (whether it is not used by another acquisition request). The higher layer is notified that the resource 4 is available. Further, the process of the SRM 21 performs scheduling for using the hardware resource 4 in response to an acquisition request from an upper layer, and the request contents (for example, paper conveyance and image forming operation by the printer engine, memory allocation, file generation, etc.) Has been implemented directly.

  The handler layer 8 includes a fax control unit handler (hereinafter referred to as FCUH) 22 for managing a fax control unit (hereinafter referred to as FCU), which will be described later, and an image for allocating memory to the process and managing the memory allocated to the process. A memory handler (hereinafter referred to as IMH) 23 is included. The SRM 39 and the FCUH 22 make a processing request for the hardware resource 4 by using an engine I / F 27 that enables transmission of a processing request for the hardware resource 4 by a predefined function.

  The MFP 1 can centrally process processes necessary for each application in the platform layer 6. Next, the hardware configuration of the MFP 1 will be described.

  FIG. 2 shows a hardware configuration diagram of an embodiment of the MFP 1. The MFP 1 includes a controller board 30, an operation panel 39, an FCU 40, and an engine 43. The FCU 40 includes a G3 standard compliant unit 53 and a G4 standard compliant unit 54.

  The controller board 30 includes a CPU 31, an ASIC 36, an HDD 38, a system memory (MEM-P) 32, a local memory (MEM-C) 37, a north bridge (hereinafter referred to as NB) 33, and a south bridge. (Hereinafter referred to as SB) 34, NIC 51 (Network Interface Card), USB device 41, IEEE 1394 device 42, and Centronics device 52.

  The operation panel 39 is connected to the ASIC 36 of the controller board 30. In addition, the SB 34, the NIC 51, the USB device 41, the IEEE 1394 device 42, the Centronics device 52, and the NB 33 are connected by a PCI bus.

  The MLB 45 is a board that is connected to the MFP 1 via the PCI bus. The MLB 45 converts the image data input from the MFP 1 and outputs the converted image data or encoded image data to the MFP 1.

  The FCU 40 and the engine 43 are connected to the ASIC 36 of the controller board 50 via a PCI bus.

  In the controller board 50, the local memory 37, the HDD 38, and the like are connected to the ASIC 36, and the CPU 31 and the ASIC 36 are connected via the NB 33 of the CPU chip set. In this way, if the CPU 31 and the ASIC 36 are connected via the NB 33, it is possible to cope with a case where the interface of the CPU 31 is not disclosed.

  Further, the ASIC 36 and the NB 33 are not connected via a PCI bus, but are connected via an AGP (Accelerated Graphics Port) 67. In this way, in order to control the execution of one or more processes forming the application layer 5 and the platform layer 6 in FIG. 22, the ASIC 36 and the NB 33 are connected via the AGP 35 instead of the low-speed PCI bus, thereby reducing the performance. It is preventing.

  The CPU 31 performs overall control of the MFP 1. The CPU 31 starts and executes NCS 13, DCS 14, OCS 15, FCS 16, ECS 17, MCS 18, UCS 19, SCS 20, SRM 21, FCUH 22, IMH 23, and MEU 44 as processes on the OS, and also executes a printer application 9 that forms the application layer 5, The copy application 10, the fax application 11, and the scanner application 12 are activated and executed.

  The NB 33 is a bridge for connecting the CPU 31, the system memory 32, the SB 34 and the ASIC 36. The system memory 32 is a memory used as a drawing memory of the MFP 1. The SB 34 is a bridge for connecting the NB 33 to the PCI bus and peripheral devices. The local memory 37 is a memory used as a copy image buffer and a code buffer.

  The ASIC 36 is an IC for use in image processing having hardware elements for image processing. The HDD 38 is a storage for storing images, programs, font data, forms, and the like. The operation panel 39 is an operation unit that accepts an input operation from the user and performs display for the user.

  Next, the IMH 23 will be described in detail. FIG. 3 shows how the IMH 23 stores the image transferred from the transfer destination. FIG. 3 shows the SRM 21, the transfer image 101, the IMH 23, the image transfer device 61, the storage image 102, and the memory 60. The transfer image 101 is an image from the transfer destination. The stored image 102 is an image in which the transferred image is stored. The memory may be either the system memory 32 or the local memory 37 shown in FIG.

  As shown in FIG. 3, the IMH 23 acquires the transferred image from the SRM 21, and stores the image in the memory 60 by the image transfer device 61.

  Next, FIG. 4 will be described. The reference numerals shown in FIG. 4 are the same as the reference numerals in FIG. FIG. 4 shows how the IMH 23 transfers the stored image to the transfer destination.

  As shown in FIG. 4, the IMH 23 acquires the transferred image from the memory, and also transfers the image to the SRM 21 by the image transfer unit 61.

  3 and 4 described above, the IMH 23 performs control and storage of input / output of images to / from the memory. 3 and 4, the image is transferred via the SRM 21, but the image may be directly input / output from the application located in the application layer 5 described above.

  Next, a peripheral block diagram related to the IMH 23 will be described with reference to FIG. FIG. 5 shows an application 71, API 28, control service 70, SRM 21, IMH 23, driver group 72, memory 60, and HDD 38.

  The application 71 is any application located in the application layer 5 of FIG. The control service 70 is any control service located in the control service layer 7 of FIG. The driver group 72 is a driver for exchanging with the memory 60 and the HDD 38.

  As shown in FIG. 5, the application 71 may input / output an image via the control service 70 and the SRM 21 or may directly input / output using the driver of the driver group 72.

  Next, a class diagram of a framework for performing transfer processing will be described with reference to FIG. FIG. 6 shows a framework 150 within a dotted line and parts outside the dotted line, and these are configured by classes. First, the framework 150 will be described.

  The framework 150 includes a transfer sequence 151, a transfer image 152, a step 153, a completion notification step 154, a merge step 155, a memory allocation step 156, a memory release step 157, an image storage step 158, and an image reading. Step 159, transfer step 160, link step 161, link storage step 162, link reading step 163, link transfer step 164, IMH memory manager 165, archived image 166, and image transfer device 167 Consists of classes.

  Among these, the transfer sequence 151 corresponds to transfer sequence means. Step 153 corresponds to image processing inheritance means. The memory securing step 156 corresponds to memory securing means. Memory release step 157 corresponds to memory release means. The IMH memory manager 165 corresponds to memory management means. The image storing step 158 corresponds to image storing means. The image reading step 159 corresponds to image reading means. The linked storage step 162 corresponds to linked storage means. The cooperative reading step 163 corresponds to the cooperative reading means. The cooperative transfer step 164 corresponds to cooperative transfer means. The transfer step 160 corresponds to a transfer unit. The image transfer unit 167 corresponds to an image transfer unit. The completion notification step 154 corresponds to completion notification means.

  The components include a copy scan sequence 180, a copy print sequence 181, a printer storage sequence 182, a printer print sequence 183, a copy scan-print sequence 184, a printer storage / print cooperation sequence 185, and an uncompressed image 186. , JPEG image 187, TIFF image 188, image input device driver 189, image output device driver 190, and application drawing control unit 191.

  The class shown in FIG. 6 is indicated by an icon, and the icon is divided into three, an upper stage, a middle stage, and a lower stage. The top row is the name compartment and shows the class name and class type. The middle row shows a list of attributes in the attribute compartment. The lower part shows a list of operations in the operation compartment. If there is no corresponding class, the column is blank.

  In addition, some of the items shown in the middle or lower row are marked with “+” or “−”, which indicates whether they are disclosed or hidden to other classes. Those with "" are public, and those with "-" are hidden.

  Describe the classes in the framework. The transfer sequence 151 has an execution state as an attribute and execution and completion as operations. The transfer sequence 151 provides an interface of step 153 to an application or the like. Providing the interface of step 153 provides the interface of framework 150.

  The transfer image 152 has height and width as attributes. Step 153 has an execution state as an attribute and execution and completion as operations. The completion notification step 154 has execution as an operation. The merge step 155 has the number of branches as an attribute and execution as an operation. The memory allocation step 156 has execution as an operation. The memory release step 157 has execution as an operation. The image storage step 158 has execution as an operation. The image reading step 159 has execution as an operation. The transfer step 160 has execution as an operation. The cooperation step 161 has the step division number as an attribute, and has cooperation start, cooperation execution, and cooperation completion as operations. The cooperation storing step 162 includes execution, cooperation start, cooperation execution, and cooperation completion as operations. The cooperation reading step 163 includes execution, cooperation start, cooperation execution, and cooperation completion as operations. The cooperation transfer step 164 includes execution, cooperation start, cooperation execution, and cooperation completion as operations. The IMH memory administrator 165 has a size as an attribute and secure and release as operations. The stored image 166 has a page ID as an attribute and has accumulation and reading as operations. The image transfer device 167 has a start address and a data length as attributes, and has transfer as an operation.

  Next, the component class will be described. The copy scan sequence 180 is a class for reading in copying. The copy / print sequence 181 is a class for performing printing in copying. The copy scan print sequence 184 is a class for reading and printing in copying. The printer accumulation sequence 182 is a class for accumulating images in the printer. The printer print sequence 183 is a class for performing printing in the printer. The printer accumulation / print sequence 185 is a class for performing accumulation and printing in the printer. With these classes, it is possible to perform processing combining any two of image reading, printing, and storage.

  The uncompressed image 186, the JPEG image 187, and the TIFF image 188 have accumulation and reading as operations, respectively. The image input device driver 189, the image output device driver 190, and the application drawing control unit 191 have a transfer as an operation.

  The classes of the uncompressed image 186, the JPEG image 187, the TIFF image 188, the image input device driver 189, and the image output device driver 190 are in a generalized relationship with the step 153 as shown in the figure.

  Next, the behavior of the framework and components described above will be described. In the following description, the behavior in the four processes will be described using a collaboration diagram. The names of objects shown in the collaboration diagram that match the object names shown in FIG. 6 are shown in FIG. An instance of an object.

  First, the general behavior of the framework will be described using the collaboration diagram shown in FIG. FIG. 7 shows an image user 200, a transfer sequence 201, transfer steps 204, 205, 206, and 207, and workers 401, 402, 403, and 404. Examples of the image user 200 that is an actor include the copy application 10. Further, the actors 401, 402, 403, and 404 that are actors are, for example, the IMH memory manager 165, the stored image 166, and the like.

  Next, these behaviors will be described. In step S <b> 101, the image user 200 notifies the transfer sequence 201 of an execution request. In step S102, the transfer sequence 201 notifies the transfer step 204 of an execution request. The transfer step 204 notifies the execution request to the worker 203 in step S103. When the execution is completed, the worker 203 notifies the transfer step 204 of the completion of the execution in step S104.

  The transfer step 204 notified of the completion notifies the transfer step 205 of the execution request in step S105. In step S106, the transfer step 205 notifies the execution request to the worker 203. When the execution is completed, the worker 203 notifies the transfer step 205 of the completion of the execution in step S107.

  The transfer step 205 notified of completion notifies the transfer request to the transfer step 206 in step S108. The transfer step 206 notifies the execution request to the worker 203 in step S109. When the execution is completed, the worker 203 notifies the transfer step 206 of the completion of the execution in step S110.

  Thereafter, the above steps are repeated an appropriate number of times, and the transfer step 207 notifies the execution request to the worker 203 in step S111. Upon completion of execution, the worker 203 notifies the transfer step 207 of completion of execution in step S112.

  The transfer step 207 notified of completion notifies the transfer sequence 201 of completion in step S113.

  The above is the general behavior of the framework. Next, examples of specific behavior are given. First, the behavior when scanning and accumulating images will be described with reference to FIG. FIG. 8 includes an image user 200, a copy scan sequence 210, a memory reservation step 211, a transfer step 204, an image input device driver 214, an IMH memory administrator 213, an image storage step 208, A TIFF image 212, a memory release step 209, and a completion notification step 215 are shown.

  As shown in FIG. 8, components for scanning and accumulation are a copy scan sequence 210, a TIFF image 212, an image input device driver 214, and a memory securing step 211 as an initial step of the transfer sequence.

  Next, these behaviors will be described. In step S <b> 201, the image user 200 notifies the copy scan sequence 210 of an execution request. In step S202, the copy scan sequence 210 notifies the memory reservation step 211 of the execution request. In step S203, the memory securing step 211 notifies the IMH memory manager 213 of a memory securing request. In step S204, the IMH memory manager 213 notifies the memory allocation step 211 that the memory allocation has been completed.

  The memory securing step 211 notifies the transfer step 204 of the execution request in step S205. In step S206, the transfer step 204 notifies the image input device driver 214 of a transfer request. When the transfer is completed, the image input device driver 214 notifies the transfer step 204 of the transfer completion in step S207.

  The transfer step 204 notifies the image storage step 208 of the execution request in step S208. In step S209, the image storage step 208 notifies the TIFF image 212 of an accumulation request. When the accumulation of the TIFF image 212 is completed, the completion of the accumulation is notified to the image storage step 208 in step S210.

  The image storage step 208 notifies the execution request to the memory release step 209 in step S211. In the memory release step 209, in step S212, the IMH memory manager 213 is requested to release the previously secured memory. When the release of the memory is completed, the IMH memory administrator 213 notifies the memory release step 209 of the completion of the release in step S213.

  In step S214, the memory release step 209 notifies the completion notification step 215 of the execution request. In step S215, the completion notification step 215 notifies the image user 200 of the completion of execution in step S215. The completion notification step 215 notifies the completion of execution to itself in step S216, and notifies the copy scan sequence 210 of completion in step S217.

  In this way, processing is performed sequentially from one step to the next. A table showing the steps from one step to the next will be described with reference to FIG.

  FIG. 9 shows the next step from the current step. Memory reservation is performed first, and the next step is transfer. The next step in the transfer is image storage. The next step in image storage is memory release. The next step of memory release is completion notification. The next to the completion notification is “-”, but this “-” indicates that there is no next step. Therefore, the process ends with the completion notification.

  A cooperative operation of image scanning and printing, which is an example of the next behavior, will be described with reference to FIG. As shown in FIG. 10, the components in the case of the scan and print cooperative operation include a copy scan / print cooperative sequence 220, a memory securing step 211, cooperative transfer steps 221 and 222, an image input device driver 214, and the like. The image output device driver 223, the IMH memory administrator 213, the memory release step 209, the completion notification step 215, and the merge step 224.

  Next, these behaviors will be described. In step S <b> 301, the image user 200 notifies the copy scan / print cooperation sequence 220 of an execution request. In step S302, the copy scan / print cooperation sequence 220 notifies the memory reservation step 211 of the execution request. In step S303, the memory securing step 211 notifies the IMH memory manager 213 of a memory securing request. In step S304, the IMH memory manager 213 notifies the memory allocation step 211 that the memory allocation has been completed. In step S305, the memory securing step 211 notifies the cooperative transfer step 221 of the execution request.

  In the cooperative transfer step 221, first, in step S 306, a transfer request is notified to the image input device driver 214. At the same time, the cooperative transfer step 221 notifies the cooperative transfer step 222 of the start of cooperation in step S307.

  The image input device driver 214 notifies the cooperation transfer step 221 of the completion in step S308. Again, the cooperative transfer step 221 notifies the image input device driver 214 of a transfer request in step S309.

  Also, the cooperative transfer step 221 notifies the cooperative transfer step 222 of the cooperative execution in step S310. In step S311, the cooperative transfer step 222 notifies the image output device driver 223 of a transfer request.

  The image input device driver 214 notifies the cooperation transfer step 221 of the completion in step S312. The cooperative transfer step 221 notifies the image input device driver 214 of a transfer request in step S313.

  The cooperative transfer step 221 notifies the cooperative transfer step 222 of cooperative execution in step S314. In step S315, the image output device driver 223 notifies the cooperation transfer step 222 of the completion. In step S316, the cooperative transfer step 222 notifies the image output device driver 223 of a transfer request. The image input device driver 214 notifies the cooperation transfer step 221 of the completion in step S317.

  In step S318, the cooperative transfer step 221 notifies the cooperative transfer step 222 of the cooperative execution. Thereafter, the cooperative transfer step 221 notifies the cooperative transfer step 222 of the completion of cooperation in step S319. In step S320, the cooperative transfer step 221 notifies the completion notification step 215 of the execution request. Completion notification step 215 notifies completion to image user 200 in step S321. In the completion notification step 215, the execution request is notified to the merging step 224 in step S322.

  In step S323, the image output device driver 223 notifies the cooperation transfer step 222 of completion. In step S324, the cooperative transfer step 222 notifies the image output device driver 223 of the transfer request. In step S325, the image output device driver 223 notifies the cooperation transfer step 222 of completion.

  The cooperative transfer step 222 notifies the memory release step 209 of the execution request in step S326. In step S327, the memory release step 209 notifies the IMH memory manager 213 of a memory release request. When the release of the memory is completed, the IMH memory manager 213 notifies the memory release step 209 of the completion of the release in step S328. In step S329, the memory release step 209 notifies the merge step 224 of the execution request. In step S330, the merge step 224 notifies itself of execution completion, and in step S331, notifies the copy scan / print cooperation sequence 220 of completion.

  Next, similarly to the previous step, a table representing the next step to step will be described with reference to FIG. In addition, the table | surface of FIG. 11 has newly added cooperation engagement Step. This is because cooperation is performed in the cooperation transfer steps 221 and 222.

  Memory reservation is performed first, and the next step is cooperative transfer. The next step of cooperative transfer is completion notification, and further cooperative transfer. The next step in cooperative transfer is memory release. The next step of the completion notification is merging. The next step of memory release is also a merge. The process ends at this merge.

Next, the behavior when printing a printer accumulated image will be described with reference to FIG. For example, in the case of printing one sheet, the image stored in the printer is divided and stored for printing, and printing is performed. For this reason, for example, when one image is divided by n, image transfer processing for n times of accumulation and printing is performed. FIG. 12 shows a case where an image is divided by n.
FIG. 12 shows an image user 200, a printer printing sequence 250, a memory securing step 211, image reading steps 251, 252, 253, transfer steps 254, 255, 256, an IMH memory administrator 213, An uncompressed image 257, an application drawing control unit 258, a memory release step 209, and a completion notification step 215 are shown.

  Next, these behaviors will be described. In step S <b> 401, the image user 200 notifies the printer print sequence 250 of an execution request. In step S402, the printer print sequence 250 notifies the memory reservation step 211 of an execution request. In step S403, the memory securing step 211 notifies the IMH memory manager 213 of a memory securing request. In step S404, the IMH memory manager 213 notifies the memory allocation step 211 that the memory allocation has been completed. In the memory securing step 211, an execution request is notified to the image reading step 251 in step S405.

  In the image reading step 251, a reading request is notified to the uncompressed image 257 in step S 406. The uncompressed image 257 notifies the image reading step 251 of completion in step S407.

  In step S408, the image reading step 251 notifies the transfer step 254 of the execution request. The transfer step 254 notifies the point request to the application drawing control unit 258 in step S409. When the transfer is completed, the application drawing control unit 258 notifies the transfer step 254 of the completion in step S410.

  In the transfer step 254, an execution request is notified to the image reading step 251 in step S411. In step S <b> 412, the image reading step 251 notifies the uncompressed image 257 of a reading request. When reading of the uncompressed image 257 is completed, the completion is notified in step S413. In step S <b> 414, the image reading step 251 notifies the transfer step 255 of an execution request. In step S415, the transfer step 255 notifies the application drawing control unit 258 of a transfer request. When the transfer is completed, the application drawing control unit 258 notifies the transfer step 255 of the completion in step S416.

  The image reading step 253 notifies the uncompressed image 257 of a reading request in step S417. When reading of the uncompressed image 257 is completed, the image reading step 253 is notified of completion in step S418. In the image reading step 253, an execution request is notified to the transfer step 256 in step S419. In step S420, the transfer step 256 notifies the application drawing control unit 258 of a transfer request. When the transfer is completed, the application drawing control unit 258 notifies the transfer step 256 of the completion in step S421.

  In step S422, the transfer step 256 notifies the memory release step 209 of the execution request. In step S423, the memory release step 209 notifies the IMH memory manager 213 of a memory release request. When the release is completed, the IMH memory manager 213 notifies the memory release step 209 of an execution request in step S424.

  In step S425, the memory release step 209 notifies the completion notification step 215 of completion. Completion notification step 215 notifies the image user 200 of the completion of execution in step S426. In step S4270, the completion notification step 215 notifies the completion of execution to itself, and in step S428, notifies the printer print sequence 250 of completion.

  Next, similarly to the previous step, a table representing the next step to step will be described with reference to FIG.

  Memory reservation is performed first, and the next step is image reading. The next step in reading the image is transfer. The next step of transfer is image reading. The next step in reading the image is transfer. The next step of transfer is image reading. Thereafter, image reading and transfer are repeated an appropriate number of times. Then, the last n-th image reading is performed, and the next step is transfer. The next step of the transfer is a memory release since the memory for reading the image is no longer necessary. Next to the memory release is a completion notification.

  An implementation example using the above-described framework will be described with reference to FIG. 14, taking the copy scan sequence 180 as an example.

  FIG. 14 shows a specific example of execution () of the copy scan sequence 180. First, the code 300 indicates exe () that is a member function of the copy scan sequence class. In the code 301, when the pointer the_first_step is other than 0 (NULL), that is, when the pointer the_first_step points to an entity, no processing with this function is performed. The code 301 indicates that when the pointer the_first_step is 0 (NULL), that is, when the pointer the_first_step does not indicate an entity, the entity is secured in the_first_step. The code 303 indicates that exec () that is a member function of the_first_step is executed.

  By adapting the interface in this way, the framework 150 can be used. For example, in the C ++ language, these codes are compiled and linked to manufacture an image forming apparatus having the framework 150. be able to. Various drivers and image classes that are stored or read in each format can be linked in the same way.

1 is a configuration diagram of an embodiment of an MFP according to the present invention. FIG. 1 is a hardware configuration diagram of an embodiment of an MFP according to the present invention. FIG. It is a figure which shows a mode that IMH stores an image. It is a figure which shows a mode that IMH transfers an image. It is a block diagram of the periphery which concerns on IMH. It is a class diagram of a framework. It is a collaboration diagram showing the general behavior of the framework. It is a collaboration diagram showing the behavior when scanning and accumulating images. It is a table | surface which shows the next step. FIG. 5 is a collaboration diagram illustrating a cooperative operation of image scanning and printing. It is a table | surface which shows the next step and a cooperation engagement step. FIG. 10 is a collaboration diagram illustrating a behavior when printing a printer stored image. It is a table | surface which shows the next step. It is a figure which shows the example of mounting. It is a figure which shows a prior art example.

Explanation of symbols

1 MFP
2 Software group 3 MFP start unit 4 Hardware resource 5 Application layer 6 Controller layer 7 Control service layer 8 Handler layer 9 Printer application 10 Copy application 11 Fax application 12 Scanner application 13 Network control service (NCS)
14 Delivery Control Service (DCS)
15 Operation Panel Control Service (OCS)
16 Fax Control Service (FCS)
17 Engine Control Service (ECS)
18 Memory Control Service (MCS)
19 On-demand update service (UCS)
20 System Control Service (SCS)
21 System Resource Manager (SRM)
22 Fax control unit handler (FCUH)
23 Image memory handler (IMH)
24 Other hardware resources 25 Scanner 26 Plotter 27 Engine I / F (PCI)
28 Application Program Interface (API)
30 Controller board 31 CPU
32 System memory (MEM-P)
33 North Bridge (NB)
34 South Bridge (SB)
35 AGP (Accelerated Graphics Port)
36 ASIC
37 Local memory (MEM-C)
38 Hard Disk Drive (HDD)
39 Operation Panel 40 Fax Control Unit (FCU)
41 USB device 42 IEEE 1394 device 43 Engine part 51 NIC
52 Centronics device 60 Memory 61 Image transfer device 70 Control service 71 Application 72 Driver group 101, 152 Transfer image 102 Storage image 150 Framework 151 Transfer sequence 153 Step 154, 215 Completion notification step 155, 224 Merge step 156, 211 Memory reservation step 157, 209 Memory release step 158, 208 Image storage step 159, 251, 252, 253 Image reading step 160, 204, 205, 206, 207, 256 Transfer step 161 Cooperation step 162 Cooperation storage step 163 Cooperation reading step 164, 221 222 Cooperative transfer step 165, 213 IMH memory manager 166 Stored image 167 Image transfer device 180, 210 -Scan sequence 181 Copy print sequence 182, 250 Printer storage sequence 183 Printer print sequence 184 Copy scan-print sequence 185 Printer storage / print linkage sequence 186 Uncompressed image 187 JPEG image 188, 212 TIFF image 189, 214 Image input device driver 190 223 Image output device driver 191 258 Application drawing control unit 200 Image user 201 Transfer sequence 203, 401, 402, 403, 404 Operator 210 Copy scan sequence 220 Copy scan print cooperation sequence 257 Uncompressed image

Claims (22)

In an image forming apparatus having hardware resources used in image forming processing and one or more applications that perform processing related to image forming,
Image processing inheritance means for executing image processing including image transfer processing in the image forming apparatus executed when each application performs processing related to image formation;
An image forming apparatus comprising: transfer sequence means for providing an interface of the image processing inheritance means for performing a series of processes relating to image formation to each application. The image forming apparatus according to claim 1, wherein the series of processes is a combination of any two or more of image reading, printing, and storage. The image processing inheriting means is
Memory securing means for securing a memory for storing the image;
The image forming apparatus according to claim 1, further comprising: a memory releasing unit that releases the secured memory. The image forming apparatus according to claim 3, wherein the memory securing unit and the memory releasing unit secure or release the memory via a memory management unit that manages the memory. Non-volatile storage means for storing the image,
The image storage means for storing the image in the nonvolatile storage means and the image reading means for reading an image stored in the nonvolatile storage means in response to a request from the image processing inheritance means. The image forming apparatus according to 1. The image processing inheriting means is
The image forming apparatus according to claim 5, further comprising a cooperative storage unit configured to execute the image storage unit and another process in cooperation with each other. The image processing inheriting means is
The image forming apparatus according to claim 5, further comprising: a cooperative reading unit that executes the image reading unit and another process in cooperation with each other. The image processing inheriting means is
The image forming apparatus according to claim 1, further comprising an image transfer unit configured to output an image to the hardware resource or input an image from the hardware resource. The image processing inheriting means is
The image forming apparatus according to claim 8, further comprising a cooperative transfer unit configured to execute the image transfer unit and another process in cooperation with each other. The image processing inheriting means is
The image forming apparatus according to claim 8, further comprising a transfer unit that causes the image transfer unit to transfer an image. The image processing inheriting means is
The image forming apparatus according to claim 1, further comprising a completion notification unit that notifies the completion of the image processing. The application is one of a printer application that is an application for a printer, a copy application that is a copy application, a fax application that is a fax application, and a scanner application that is a scanner application. The image forming apparatus according to claim 1, wherein the image forming apparatus is an image forming apparatus. The image according to any one of claims 1 to 11, wherein the format of the image stored in the nonvolatile storage means is any one of uncompressed, JPEG, and TIFF. Forming equipment. Hardware resources used in image forming processing, image processing inheriting means for executing image processing including image transfer processing in the image forming apparatus executed when processing relating to image formation is performed, and image formation An image forming apparatus having transfer sequence means for providing an interface of the image processing inheritance means for performing a series of processes according to
An application that conforms to the interface provided by the transfer sequence means and performs processing related to the image formation;
An image storage means for generalizing the image processing inheritance means, storing the image in a nonvolatile storage means for storing the image, and an image reading means for reading the image stored in the nonvolatile storage means;
An image forming apparatus characterized by having a generalization relationship with the image processing inheriting means, and the image processing inheriting means having a driver for using the hardware resources. The image forming apparatus according to claim 14, wherein the series of processes is a combination of any two or more of image reading, printing, and storage. The application is one of a printer application that is an application for a printer, a copy application that is a copy application, a fax application that is a fax application, and a scanner application that is a scanner application. The image forming apparatus according to claim 14. The image forming apparatus according to claim 16, wherein the printer application prints or accumulates an image using the image processing inheritance unit. The image forming apparatus according to claim 16, wherein the copy application prints or scans an image using the image processing inheritance unit. The image forming apparatus according to claim 14, wherein the format of the image stored in the nonvolatile storage unit is any one of uncompressed, JPEG, and TIFF formats. The image forming apparatus according to claim 14, wherein the driver inputs an image from the hardware resource or outputs an image to the hardware resource. Hardware resources used in image forming processing, one or more applications that perform processing relating to image formation, and images in the image forming apparatus that are executed when each application performs processing relating to image formation Image processing having an image processing inheritance unit that executes image processing including the transfer processing of the image, and a transfer sequence unit that provides an interface of the image processing inheritance unit for performing a series of processes related to image formation to each application In the device manufacturing method,
An application link step for associating the program of the application adapted to the interface provided by the transfer sequence unit with the program of the transfer sequence unit;
An image program link stage for associating the image program for storing or reading the image with the program of the image processing inheriting unit;
A method for manufacturing an image forming apparatus, comprising: a driver link step for associating a driver for using the hardware resource with a program of the image processing inheritance unit. The method of manufacturing an image forming apparatus according to claim 21, wherein the series of processes is a combination of any two or more of image reading, printing, and storage.

Images