JP4978264B2 - Image forming apparatus and memory resource securing method - Google Patents

Description

  The present invention relates to an image forming apparatus capable of executing a plurality of types of jobs, and more particularly to an image forming apparatus suitable for overuse of memory resources and a memory resource securing method used therefor.

  A multifunction peripheral, which is a kind of image forming apparatus, uses a common hardware resource for a plurality of types of job execution, so that the cost can be reduced as a whole and space can be saved.

  In the following Patent Document 1, a general-purpose operating system (general-purpose OS) such as UNIX (registered trademark) is used, and common functions of copy, print, scan, and facsimile applications are summarized and a platform is configured with the general-purpose OS. It is disclosed that the number of program steps of each application is reduced and the program development efficiency is increased.

However, in such a multi-function peripheral, a plurality of types of jobs request acquisition of a data area for memory resources, so there may be a case where an area necessary for executing a new job is lost in the memory, and there is sufficient memory in the memory. It was necessary to wait until free space was secured.
JP 2002-84383 A

  An object of the present invention is to provide an image forming apparatus capable of immediately using memory resources by preventing the memory resources from being depleted as the image forming apparatus is multi-functionalized and the image resolution is improved. An object is to provide an image forming method and an application program.

In the first aspect of the image forming apparatus according to the present invention,
Memory where the data area for jobs is reserved,
If the free space in the data area is less than or equal to the first predetermined amount, before starting the execution of the next job, the second predetermined amount of area that is greater than or equal to the first predetermined amount considered necessary for the execution of the next job Resource securing means secured from the data area;
Is provided.

In a second aspect of the image forming apparatus according to the present invention, in the first aspect,
An auxiliary storage device;
The resource securing means reserves the second predetermined amount of area by saving data in the second predetermined amount of area to the auxiliary storage device and creating a free area in the memory.

In a third aspect of the image forming apparatus according to the present invention, in the first or second aspect,
The resource securing unit reserves a part of the area in the memory as the data area in advance when the image forming apparatus is activated.

In a fourth aspect of the image forming apparatus according to the present invention, in any one of the first to third aspects,
The resource securing means reserves the data area in units of blocks at the time of starting, and when all the blocks are used, the data area necessary for execution of the job is transferred from the block in use to the block unit. Secure with.

In the first aspect of the memory resource securing method according to the present invention,
In a memory resource securing method performed in an image forming apparatus including a memory in which a job data area is secured,
If the free space in the data area is less than or equal to the first predetermined amount, before starting the execution of the next job, the second predetermined amount of area that is greater than or equal to the first predetermined amount considered necessary for the execution of the next job Secure from the data area.

  According to the configuration of the first aspect, when the free space in the data area is equal to or less than the first predetermined amount, the first predetermined amount that is considered necessary for the execution of the next job is started before the execution of the next job. Since the second predetermined amount of area is secured from the data area, it is possible to prevent the data area from becoming insufficient at the start of the next job execution, and to use memory resources immediately. Play.

  According to the configuration of the second aspect, the second predetermined amount of area is secured by saving data in the second predetermined amount of area to the auxiliary storage device and creating a free area in the memory. As a result, it is possible to prevent the data in the second predetermined area from being lost.

  According to the configuration of the third aspect, since a part of the area in the memory is reserved in advance as the data area when the image forming apparatus is started up, the part of the area in the memory is used for other purposes by the OS or application. Even if it is used, the data area can always be used.

  Other objects, configurations and effects of the present invention will become apparent from the following description.

[1] Hardware Schematic Configuration FIG. 15 is a schematic block diagram showing a hardware configuration of the image forming apparatus 10 according to the first embodiment of the present invention.

  In the image forming apparatus 10, an EEPROM 13 E 1, EEPROM 13 E 2, DRAM 13 D, HDD 14, operation panel 15, scanner 16 S, printer 16 P, NIC 17, facsimile modem 18, and compression / decompression ASIC 19 are coupled to the MPU 11 via an interface 12. In FIG. 15, a plurality of interfaces are shown as one block for the sake of simplicity.

  The EEPROMs 13E1 and 13E2 are, for example, flash memories. The EEPROM 13E1 stores BIOS (Basic Input Output System). The EEPROM 13E2 stores software described later. The DRAM 13D is for work area, and the HDD 14 as image input / output means is for data storage.

  The operation panel 15 is used for inputting a setting value or an instruction and displaying a setting screen or a state. In the first embodiment, the operation panel 15 is configured by a combination of a touch panel and hardware keys.

  The scanner 16S as image input means is used for image input in scanning, copying, and fax transmission. The printer 16P as an image output means includes a print engine, a fixing device, a paper feeding unit, a transport unit, and a paper discharge unit, and generates an electrostatic latent image on the photosensitive drum of the print engine based on the supplied bitmap data. The toner is formed, developed with toner, transferred to a sheet, fixed, and discharged.

  The NIC 17 as image input / output means is coupled to the host computer 20 via a cable or a wireless communication medium, and is used for print jobs, e-mail transmission / reception, Internet facsimile transmission, and remote operation of the operation panel 15 from a browser. The facsimile modem 18 is for facsimile transmission / reception.

The compression / decompression ASIC 19 is used as a coprocessor of the MPU 11, and has, for example, two ports for image compression and decompression, and can execute up to four in parallel.
[2] Software design concept First, the software design concept will be described.

  A multi-function machine, which is one of conventional image forming apparatuses, has a configuration in which applications corresponding to user services such as printing, copying, and faxing are provided separately. That is, one application corresponds to one of the user services described above, and the multi-function device executes a job to provide the user service.

  However, some applications have common management and control.

  Therefore, in the present invention, a plurality of conventional applications are integrated into one, all services can be provided by one application, all jobs can be executed, and common parts are collected. The following description relates to this integrated application.

  A job is a unit of work that a user causes a computer to execute.

  However, when the number of job types increases with the multifunction of multifunction devices, the number of software components used for job execution increases and the program becomes complicated.

  Therefore, the job is decomposed into basic jobs, and the basic jobs are combined to organize the jobs so that the job layer handles this combination. That is, a combination of basic jobs and their execution order are used as a job scenario, and a job is executed by sequentially executing one or a plurality of basic jobs according to the job scenario. As a result, the complexity of the program corresponding to the job is avoided, and the design change is facilitated when the number of job types is increased or the function needs to be added or changed as the number of functions increases.

  Further, in the present invention, the design change is further facilitated by multilayering the integrated application by function. In the present embodiment, the application is divided into a service layer, a job layer, and an element layer to be multilayered.

  Furthermore, design changes can be facilitated by making the service layer and the job layer more specifically function-specific.

  Furthermore, the middleware layer mainly includes a basic program for enabling the application to be controlled relatively easily (referred to as “operation”) regardless of the model depending on the state of the hardware. This simplifies applications and makes design changes easier.

  However, in order to facilitate the design change in this way, when the number of layers is increased, the relationship between the layers increases.

  Therefore, as described below, depending on the type of service, the service is executed without passing through the job layer (simplification of instruction transmission), the transmission of job information is simplified, and the direction of transmission of instructions and notifications is unified. To make design changes easier.

Hereinafter, an integrated and multi-layered application according to the present invention will be described.
[3] Software Hierarchical Structure FIG. 1 is a schematic block diagram showing the hierarchical structure of a multi-layered application.

  An application layer 50 exists above the OS layer 30 via the middleware layer 40.

  The application layer 50, which is a characteristic part of the present embodiment, includes a common unit 51 and a system management unit 52, a lower element layer 60, an intermediate job layer 70, and an upper service layer 80.

  The service layer 80 receives a user service request and provides a service to the user via the job layer 70 and the element layer 60. As described above, some services received by the service layer 80 are executed by the element layer 60 or the system management unit 52 without going through the job layer 70, and these are called “work” in order to distinguish them from jobs. . Each service corresponds to a job or a work, and the job is executed by the job layer 70. The job is composed of one or a plurality of basic jobs, and the basic job is composed of one or a plurality of job steps. The job steps are executed by the job layer 70 using the element layer 60 as needed.

FIG. 2 shows functional units included in each layer. Each functional unit is composed of one or more program modules. The lines with arrows in FIG. 2 generally indicate the main processing flow.
[4] OS Layer The OS layer 30 includes a hardware-dependent device driver 31 and an OS 32. The device driver 31 is located below the OS 32 and is registered in the OS 32. The OS 32 is general-purpose and its kernel is, for example, Linux (registered trademark).
[5] Middleware layer The middleware layer 40 includes functional units 41 to 43.

  The device control unit 41 controls the operation panel 15, the scanner 16S, the printer 16P, the NIC 17 and the facsimile modem 18 via the device driver 31 and receives status notifications of these devices.

  The image processing unit 42 performs processing such as control of the compression / decompression ASIC 19, image enlargement / reduction or rotation processing, and RIP.

  The resource management unit 43 allocates resources according to the resource request queue for each resource, and releases the allocated resources when they are used.

Hereinafter, the application layer 50 will be described.
[6] Common Unit and System Management Unit The common unit 51 is a program used in common by the system management unit 52, the element layer 60, the job layer 70, and the service layer 80, and whether the setting value depending on the model satisfies the condition. And a program for judging whether or not. The common unit 51 simplifies the programs of the system management unit 52, the element layer 60, the job layer 70, and the service layer 80, and does not depend on the model, thereby facilitating design changes.

The system management unit 52 manages the system status and users. When an error occurs in the system, the system management unit 52 distributes the notification to a necessary part, and performs login processing and service request approval / rejection processing after login. Handle.
[7] Element Layer The element layer 60 includes functional units of a device operation unit 61, an image processing operation unit 62, and an entity unit 63. These functional units 61 or 62 correspond to the functional units 41 or 42 of the middleware layer 40, respectively. The device operation unit 61 and the entity unit 63 are both for controlling or operating the image input unit and the image output unit.

  The device operation unit 61 operates the device control unit 41 according to the state of the device notified from the device control unit 41.

  The image processing operation unit 62 performs processing such as generation of intermediate data, and also performs processing such as image compression, expansion, enlargement, reduction, rotation, and RIP via the image processing unit 42.

The entity unit 63 holds and manages data.
[8] Job Layer The job layer 70 manages job execution and starts a program in one functional unit of the element layer 60 or sequentially starts programs in a plurality of functional units to execute a job. The job execution unit 71, the job control unit 72, the basic job execution unit 73, the input step execution unit 74, the edit step execution unit 75, and the output step execution unit 76 are accessible from these step execution units. Job information 77. For convenience, what includes the job management unit 71 and the job control unit 72 is referred to as an “applied job layer”, and a basic job execution unit 73, an input step execution unit 74, an edit step execution unit 75, and an output step execution unit. Those including 76 are referred to as “basic job layer”.

  In response to a job start request from the service layer 80, the job management unit 71 generates job information 77 that is a copy of the setting information at that time (only the part corresponding to the job type), and the resource management unit 43 Hardware resources necessary for the execution of the basic job constituting the job are acquired, and then a job control instruction such as job execution, change of execution order, interruption, restart or cancellation is given to the job control unit 72. Here, the job information 77 is composed of job setting values and job states, and is a structure common to all jobs regardless of the job type. FIG. 5 is an explanatory diagram of setting values included in the job information.

  In response to the job control instruction, the job control unit 72 executes the job by sequentially instructing the basic job execution unit 73 to execute the basic jobs constituting the job according to the job scenario. Here, the job scenario includes one or more basic jobs and execution order information. This job scenario may include a conditional branch instruction for selecting a basic job according to a condition. For example, when waiting for an output resource, the output resource may be changed according to a user setting in order to rush the output.

  In response to the basic job execution instruction, the basic job execution unit 73 activates the image job execution unit 73a when the basic job includes image processing, and activates the access job execution unit 73b when the basic job does not include image processing.

  The image job execution unit 73a starts the input step execution unit 74, the edit step execution unit 75, or the output step execution unit 76 for each page to be processed according to the basic job scenario, and sequentially executes the job steps. Execute basic jobs. Here, the basic job scenario includes information on a plurality of job steps and their execution order. This scenario can also include a conditional branch instruction as described above.

  The access job execution unit 73b executes a basic job without image processing via the device operation unit 61 or the entity unit 63 in the element layer 60. For example, a specific state change is notified by e-mail via the device operation unit 61, the device control unit 41, the device driver 31, and the NIC 17.

  The input step execution unit 74 executes a job step related to image input via the device operation unit 61 or the entity unit 63. For example, the scanner 16S reads the document image data via the device operation unit 61, the device control unit 41, and the device driver 31. In addition, when the print file held by the entity unit 63 is transmitted by the facsimile modem 18, the print file is acquired from the entity unit 63 as an input step.

  The edit step execution unit 75 executes job steps related to image editing via the image processing operation unit 62. For example, processing such as enlargement, reduction, and rotation is performed on unedited print data via the image processing operation unit 62 and the image processing unit 42.

The output step execution unit 76 executes a job step related to image output via the device operation unit 61 or the entity unit 63. For example, a process for causing the printer 16P to print print data via the device operation unit 61, the device control unit 41, and the device driver 31 is performed.
[9] Service Layer The service layer 80 includes an upper layer user service reception unit 81, a lower layer user service execution unit 82, and a system service execution unit 83.

  The user service reception unit 81 receives a request from the user by an event notification, determines what the user request is, and instructs the user service execution unit 82 to execute the service in response to the request.

  Specifically, a request via the device driver 31, the device control unit 41, and the device operation unit 61 is received from the operation panel 15, the NIC 17, or the facsimile modem 18, and the job scenario identifier (pointer or pointer) corresponding to the user service request is received. (See) is handed over to the user service execution unit 82 to instruct execution of the service. This service request includes copy, fax transmission / reception, e-mail transmission / reception, maintenance, software update, and the like. However, when a simple service request such as display or change of data such as setting information held by the entity unit 63 is received, the execution is not instructed to the user service execution unit 82 in order to avoid complication of the application. The unit 63 is instructed to execute the service directly.

  In response to the service execution instruction, the user service execution unit 82 executes the service by delivering the job scenario identifier to the job management unit and instructing the start of the job.

  The system service execution unit 83 receives a system request from the image forming apparatus 10 via the system management unit 52 and executes the service by calling the job management unit 71. In the present embodiment, only a notification service described later is accepted as a request from the system, but other service requests, for example, a service that automatically performs FAX transmission or maintenance at a predetermined time may be accepted.

  When the system service execution unit 83 receives the notification of the status change of the device or user job from the system management unit 52, the system service execution unit 83 instructs the job management unit 71 to execute the notification job based on the setting information stored in the entity unit 63. To do. The notification job is to notify the user of the occurrence of the event by the set notification means when an error occurs in a user-set event, for example, an ongoing job, or fax transmission is completed. This setting information includes the necessity of notification to the user, events to be notified, notification means such as print and email, and notification destination in the case of email, and can be changed from the operation panel 15.

Hereinafter, a flow in which the above-described software, in particular, the application layer 50 responds to various service requests will be described.
[10] Print Service Execution Flow FIG. 3 is a diagram showing a flow when the print service is executed by connecting the functional units with arrows. In the following, the execution instruction identification codes in the figure are shown in parentheses.

  (A01, A02) By event driven, on the one hand, data from the host computer 20 is stored in the buffer area of the DRAM 13D secured by the resource management unit 43 via the NIC 17 and the device driver 31, and on the other hand, the device control unit 41 The print request and the data identification information are notified to the user service reception unit 81 via the device operation unit 61.

  (A03) In the case of a print request notification, the user service accepting unit 81 passes the identifier of the print job scenario and the identifier of the setting information corresponding to the service to the user service execution unit 82, and at the same time, Execution is instructed (the user service execution unit 82 is activated). This setting information includes the data identification information and the current setting value set in the EEPROM 13E2 for printing.

  In response to this, the user service execution unit 82 executes the service by performing an operation as shown in the sequence diagram of FIG. Hereinafter, this operation will be specifically described.

  (A04) The user service execution unit 82 activates the job management unit 71, and starts execution of the print service by giving an instruction to generate a print job.

  (A05) In response to this, the job management unit 71 generates an instance of the initialized job information 77. This instance has a default value of job information 77. Next, the job management unit 71 assigns a job ID to this job, and writes this and the job type in the job information 77.

  (A06) When the generation and writing of the job information 77 is completed, the job management unit 71 notifies the user service execution unit 82 of the job ID.

  (A07, A08) The user service execution unit 82 writes the setting information received from the user service reception unit 81 into the job information 77, and then hands over the identifier of the print job scenario to the job management unit 71 to print the print job. Instruct to start.

  (A09 to A11) In response, the job management unit 71 notifies the system management unit 52 of the job start together with the job ID, refers to the job scenario based on the identifier of the job scenario, and instructs the resource management unit 43 to A hardware resource acquisition request such as memory and compression / decompression ASIC 19 necessary for executing the basic job is requested, and after acquisition, the job scenario identifier and the job information 77 identifier are delivered to the job control unit 72, and Instructs control of print job.

  (A12) In response, the job control unit 72 refers to the job scenario based on the received job scenario identifier, and delivers the identifier of the job information 77 to the basic job execution unit 73 and executes the basic job accordingly. Instruct. In this embodiment, since the print job is composed of one basic job, the job control unit 72 instructs execution of only this basic job. However, if the print job is composed of a plurality of basic jobs, The control unit 72 instructs to execute a plurality of basic jobs in sequence, such as instructing execution of one basic job according to the job scenario, and instructing execution of the next basic job after completion of the execution.

  Conventionally, after a job is executed, the hardware hierarchy necessary for the job such as a memory is acquired after descending the program hierarchy to the middleware layer 40 in order, so that the resource cannot be acquired and is in a waiting state. If the job is canceled sometimes, the processing up to that point is wasted, but in this embodiment, since the basic job is executed after acquiring the hardware resources, such a waste can be omitted.

  In response to the basic job execution instruction, the basic job execution unit 73 transmits the basic job instructed with the identifier of the job information 77 to the image job execution unit 73a according to the basic job type, and activates the basic job. . In response to this, the image job execution unit 73a refers to the basic job scenario corresponding to the instructed basic job, and in accordance with this, the image input and image processing (omitted from the step execution units 74 to 76) are performed as follows. Sequence control) and image output job steps. That is, the step execution units 74 to 76 are sequentially instructed to execute a plurality of job steps constituting the instructed basic job according to the basic job scenario. Although the case where the job control unit 72 instructs the basic job execution unit 73 to execute and activates the image job execution unit 73a has been described, the job control unit 72 directly activates the image job execution unit 73a. Also good.

  (A13) In the above sequence control, the image job execution unit 73a first transfers the identifier of the job information 77 to the input step execution unit 74 and starts it according to the basic job scenario corresponding to the instructed basic job.

  (A14) In response to this, the input step execution unit 74 reads predetermined setting information from the job information 77 according to the job type (print job) included in the job information 77, and based on this, the image processing operation unit 62 The data identification information included in the job information 77 is passed to and activated.

  (A15 to A18) In response to this, the image processing operation unit 62 delivers the data identification information to the device operation unit 61, and print data in the buffer area secured by the resource management unit 43 is transmitted to the device operation unit. 61, the print data is sequentially analyzed, predetermined information included in the print data is written in the job information 77, and then unedited print output page data is sequentially created via the image processing unit. Each time print output page data for one page is created, the input step execution unit 74 is notified of the creation completion and the identifier of the page data is delivered.

  (A19) In response to this, the input step execution unit 74 notifies the image job execution unit 73a in the basic job execution unit 73 of the completion and delivers the identifier of the page data.

  (A20) In response to this, the image job execution unit 73a delivers the page data identifier and the job information 77 identifier to the edit step execution unit 75 and activates them according to the basic job scenario. Depending on the basic job scenario, the edit step execution unit 75 may not be activated. In this case, the process of step A24 is performed.

  (A21 to A23) In response to this, the edit step execution unit 75 reads predetermined setting information from the job information 77 in accordance with the job type included in the job information 77, and based on this, the image processing operation unit 62 passes the setting information. A corresponding method of the image processing unit 42 is called to perform image editing such as enlargement, reduction, and rotation on the page data. When the editing is completed, the completion is notified to the image job execution unit 73a in the basic job execution unit 73.

  (A24) The image job execution unit 73a delivers the edited page data identifier and the identifier of the job information 77 to the output step execution unit 76 and starts it according to the basic job scenario.

  (A25) In response to this, the output step execution unit 76 reads predetermined setting information from the job information 77 according to the job type included in the job information 77, and activates the device operation unit 61 based on this.

  (A26 to A28) In response to this, the device operation unit 61 calls the common unit 51 to determine whether or not the setting information satisfies a condition depending on the model. Based on the above, a printing process on a sheet is performed via the device control unit 41. Further, when a negative determination is made, the print processing is performed based on the alternative information of the setting information acquired from the common unit 51, or the processing is completed without performing the print processing.

  (A29) When the printing process is completed for all pages, the output step execution unit 76 notifies the completion to the image job execution unit 73a in the basic job execution unit 73.

  (A30) The image job execution unit 73a refers to the basic job scenario, determines that all job steps have been executed, that is, determines that execution of one basic job composed of these has been completed, and performs job control. The unit 72 is notified of the completion of the basic job.

  (A31) In response to this, the job control unit 72 notifies the job management unit 71 of the completion of the basic job together with the job ID.

  (A32-34) In response, the job management unit 71 releases the hardware resources acquired at the start of the job via the resource management unit 43, refers to the job scenario, and completes execution of all the basic jobs. Judgment is made, that is, it is judged that the execution of the print job constituted from this is completed, the job information 77 is discarded, and the job completion is notified to the system management unit 52 and user service execution unit 82 together with the job ID.

  As described above, job information 77 having a data structure common to all job types is provided, and in the programs in the input step execution unit 74, the edit step execution unit 75, and the output step execution unit 76 using the job information 77, job information is provided. Since predetermined setting information is acquired from the job information 77 according to the job type held by the job 77, there is an effect that the configuration is simplified and the design can be easily changed.

Further, since the image job execution unit 73a instructs the step execution units 74 to 76 to execute based on the basic job scenario corresponding to the job, the basic job can be changed without changing the program details in the step execution units 74 to 76. A new job type can be easily created simply by changing the scenario, and the design can be easily changed.
[11] Fax Transmission Service Execution Flow FIG. 6 is a diagram showing a flow when the fax transmission service is executed by connecting the functional units with arrows.

  (B01, B02) The user operates the operation panel 15 to set the fax transmission destination and the like, and presses the start button on the operation panel 15. The device driver 31 detects the key press and supplies the code to the device control unit 41. The device control unit 41 tokenizes the input by performing state transition based on the state and the input key code, and the device operation unit 61 To supply.

  (B03) The device operation unit 61 interprets the request or setting value and supplies it to the user service reception unit 81.

  (B04) In response to this, the user service receiving unit 81 instructs the user service execution unit 82 to execute the fax transmission service by passing the identifier of the fax transmission job scenario and the identifier of the setting value regarding the fax transmission. .

  (B05) In response to this, the user service execution unit 82 activates the job management unit 71 and executes a fax transmission service by instructing the generation of a fax transmission job.

  (B06, B07) In response to this, the job management unit 71 assigns a job ID to this job, generates an instance of the initialized job information 77, writes the job ID and job type to this, The user ID is notified to the user service execution unit 82.

  (B08, B09) The user service execution unit 82 writes the setting value specified by the identifier received from the user service reception unit 81 in the job information 77, and then passes the job scenario identifier to the job management unit 71. Instructs the start of a fax transmission job.

  (B10 to B12) In response to this, the job management unit 71 notifies the system management unit 52 of the job start together with the job ID, refers to the job scenario based on the received job scenario identifier, and first starts the resource management unit 43. Request for acquisition of hardware resources such as the area in the DRAM 13D and the scanner 16S necessary for executing the basic job (ScanToBox basic job described later), and after this acquisition, the identifier of the job scenario and the identifier of the job information 77 Are sent to the job control unit 72 and a fax transmission job control start instruction is issued.

  (B13) In response to this, the job control unit 72 refers to the job scenario based on the received job scenario identifier, and passes the identifier of the job information 77 to the basic job execution unit 73 in accordance with this, and also executes the fax transmission job. Instruct to execute one ScanToBox basic job to be configured.

  Here, the fax transmission job scenario indicates that the Box To Fax basic job is performed after the Scan To Box basic job is performed. That is, the fax transmission job includes a ScanToBox basic job for reading a document image from the scanner 16S and placing the file in a box (directory), a BoxToFax basic job for calling a transmission destination, extracting a file from the box, and transmitting the fax. It is a combination.

  In response to this, the basic job execution unit 73 determines that the basic job instructed to be executed involves image processing, and transmits the identifier of the job information 77 and the basic job instructed to the image job execution unit 73a. Start this. In response to this, the image job execution unit 73a refers to the basic job scenario corresponding to the instructed basic job, and in accordance with this, the image input and image processing (omitted from the step execution units 74 to 76) are performed as follows. Sequence control) and image output job steps. That is, the step execution units 74 to 76 are sequentially instructed to execute a plurality of job steps constituting the instructed basic job according to the basic job scenario.

  (B14) First, the image job execution unit 73a hands over the identifier of the job information 77 to the input step execution unit 74 and starts it according to the basic job scenario corresponding to the instructed basic job.

  (B15-17) In response, the input step execution unit 74 reads predetermined setting information from the job information 77 according to the job type included in the job information 77, and based on this, the device operation unit 61 and the device control unit are read. One page of document image data is read from the scanner 16S via 41 or the like. At this time, the device operation unit 61 operates the device control unit 41 in response to a status notification from the device control unit 41.

  (B18) Upon completion of the above-described processing, the input step execution unit 74 writes page information such as the storage address and range of the original image data in the job information 77, and then the image job execution unit 73a in the basic job execution unit 73. Is notified of the completion.

  (B19) In response to this, the image job execution unit 73a delivers the identifier of the job information 77 to the output step execution unit 76 and activates it according to the basic job scenario.

  (B20, B21) In response to this, the output step execution unit 76 reads predetermined setting information (including the page information) from the job information 77 according to the job type included in the job information 77, and based on this The document image data is stored in the entity unit 63 directly or as a file, and the completion is notified to the image job execution unit 73a in the basic job execution unit 73.

  (B22) In response to this, the image job execution unit 73a refers to the basic job scenario, completes the execution of all job steps, determines that the execution of the ScanToBox basic job is complete, and completes the job control unit 72 with this completion. To be notified.

  (B23) In response to this, the job control unit 72 notifies the job management unit 71 of the completion of the basic job together with the job ID.

  (B24) In response to this, the job management unit 71 releases the hardware resources acquired at the start of the job via the resource management unit 43, and then refers to the job scenario, and the next basic job (BoxToFax basic job) In response, the resource management unit 43 is requested to acquire hardware resources such as the facsimile modem 18 necessary for executing the next basic job.

  (B25 to B27) After acquiring the resource, the job management unit 71 reads the destination FAX number from the job information 77, and directly causes the device control unit 41 to execute destination call control via the device operation unit 61. At this time, the device operation unit 61 operates the device control unit 41 in response to a status notification from the device control unit 41.

  This control is similar to securing resources in the sense that if this call control fails, the process cannot proceed to the next process, and both are the responsibility of the job management unit 71, so that the program structure is organized and the design can be easily changed. Contribute.

  Note that the area in the DRAM 13D necessary for execution of the BoxToFax job and the fax reception job is secured in advance by the initialization process when the image forming apparatus 10 is started up, and it is not necessary to acquire hardware resources at this time.

  (B28 to B30) When the device control unit 41 detects the on-hook of the destination fax, the device control unit 41 notifies the job management unit 71 of this via the device operation unit 61.

  (B31) In response to this, the job management unit 71 instructs the job control unit 72 to perform next control of the job.

  (B32) In response to this, the job control unit 72 refers to the job scenario, passes the identifier of the job information 77 to the basic job execution unit 73 according to the job scenario, and constitutes the fax transmission job. Instructs execution of a BoxToFax basic job which is the next basic job.

  In response to this, the basic job execution unit 73 transmits the identifier of the job information 77 and the instructed basic job to the image job execution unit 73a according to the basic job type, and activates it. In response to this, the image job execution unit 73a refers to the basic job scenario corresponding to the instructed basic job, and in accordance with this, the image input and image processing (omitted from the step execution units 74 to 76) are performed as follows. Sequence control) and image output job steps. That is, the step execution units 74 to 76 are sequentially instructed to execute a plurality of job steps constituting the instructed basic job according to the basic job scenario.

  (B33) First, the image job execution unit 73a hands over the identifier of the job information 77 to the input step execution unit 74 and starts it according to the basic job scenario corresponding to the instructed basic job.

  (B34, B35) In response, the input step execution unit 74 reads predetermined setting information from the job information 77 according to the job type included in the job information 77, and reads a file from the entity unit 63 based on this. The completion of the job step is notified to the image job execution unit 73a.

  (B36) In response to this, the image job execution unit 73a delivers the identifier of the job information 77 to the output step execution unit 76 and starts it to execute the next job step according to the basic job scenario. . In this embodiment, since image processing is omitted, the edit step execution unit 75 is not called. However, when the edit step execution unit 75 is called, the edit step execution unit 75 performs image processing according to the performance of the calling FAX device. Do.

  (B37 to B41) In response to this, the output step execution unit 76 reads predetermined setting information from the job information 77 according to the job type included in the job information 77, and stores it in the entity 63 based on this. The image data or file is acquired, and the device control unit 41 is faxed to the acquired image data or data in the file via the device operation unit 61, and the image job execution unit 73a is notified of the completion of the job step.

  (B42) In response to this, the image job execution unit 73a refers to the basic job scenario and determines that execution of all the job steps has been completed, that is, determines that execution of the BoxToFax basic job composed of these has been completed. Then, the job control unit 72 is notified of the completion of the basic job.

  (B43) In response to this, the job control unit 72 notifies the job management unit 71 of the completion of the basic job together with the job ID.

  (B44 to B46) In response to this, the job management unit 71 releases the hardware resources acquired for executing the BoxToFax basic job via the resource management unit 43, and then refers to the job scenario to determine the basic job. Are executed, and it is determined that the execution of the fax transmission job constituted from this is completed, the job information 77 is discarded, and the job completion is notified to the system management unit 52 and the user service execution unit 82 together with the job ID.

  According to this embodiment, since one or more basic jobs are executed based on the job scenario in the application job layer, it is possible to add or change jobs by combining basic jobs without changing the basic job layer and below. This makes it possible to easily change the design.

Also, since the process from image input to saving of the file is defined as one basic job, a plurality of jobs can be realized by combining this with other basic jobs. For example, as shown in FIG. 7, by defining four basic jobs: (1) ScanToBox, (2) BoxToPrint, (3) BoxToFax, and (4) BoxToE-mail, not only each job but also a combination of these Three jobs,
(5) ScanToBox + BoxToPrint = ScanToPrint
(6) ScanToBox + BoxToFax = ScanToFax
(7) ScanToBox + BoxToE-mail = ScanToE-mail
Can be further defined. Further, if one basic job is changed, a plurality of jobs including the basic job are changed. This enhances the effect of facilitating the design change and further simplifies the configuration of the application.

Further, since the fax transmission job is a combination of the ScanToBox basic job and the BoxToFax basic job, for example, when a jam occurs in the ScanToBox basic job, execution of the BoxToFax basic job is not started, and wasteful processing is performed by starting this. There is an effect that it can be prevented from occurring.
[12] Scan Service Execution Flow FIG. 8 is a diagram illustrating a flow at the time of executing the scan service by connecting the functional units with arrows. This service is realized by the above ScanToBox job. However, in the figure, an image editing process is included between the scan input and the file output.
[13] In-Box File Printing Service Execution Flow FIG. 9 is a diagram showing a flow when the in-box file printing service is executed by connecting the functional units with arrows. This service changes the BoxToFax job to BoxToPrint, and includes an image editing process between file reading and print output.
[14] Flow when Jam Occurs During Scan Service Execution FIG. 10 is a diagram illustrating a flow when a jam occurs during execution of a scan service by connecting the functional units with arrows.

  This scan service generates a scan job. This scan job is composed of one ScanToBox basic job. Hereinafter, the processing by the image job execution unit 73a in the basic job execution unit 73 will be described.

  (E01) The image job execution unit 73a passes the identifier of the job information 77 to the input step execution unit 74 and activates the input step execution unit 74.

  (E02 to E04) In response to this, the input step execution unit 74 reads predetermined setting information from the job information 77 according to the job type included in the job information 77, and based on this, the device operation unit 61 and the device control unit An attempt is made to read one page of document image data from the scanner 16S via 41 or the like.

  (E05, E06) At this time, when a jam occurs in the auto sheet feeder of the scanner 16S, the device control unit 41 notifies the device operation unit 61 of the occurrence of the jam.

  Here, when the notification from the device control unit 41 is an error occurrence or error cancellation, the device operation unit 61 notifies the system management unit 52 of this together with the device identifier and job ID, and in other cases, the notification. It has the responsibility to notify the input step execution unit 74 together with the job ID.

  (E07) Therefore, the device operation unit 61 notifies the start source of the jam occurrence together with the device identifier and the job ID, and in this case, the system management unit 52.

  (E08, E09) Upon receiving an error or error cancellation notification, the system management unit 52 notifies the operation panel program of the device operation unit 61 together with the device identifier, and notifies the job management unit 71 together with the job ID. Have Therefore, the system management unit 52 makes these notifications.

  (E10, E11) In response to this, the device operation unit 61 displays on the operation panel 15 via the device control unit 41 and the device driver 31 that a jam has occurred in the device corresponding to the device identifier.

  (E12) On the other hand, in response to the notification, the job management unit 71 notifies the job control unit 72 of the jam error. The job control unit 72 determines whether the error corresponds to a predetermined interruption reason.

  (E13) The jam error is a reason for interruption, and the job control unit 72 instructs the image job execution unit 73a in the basic job execution unit 73 to interrupt the job.

  (E14 to E17) In response to this, the image job execution unit 73a causes the device control unit 41 to interrupt the operation via the input step execution unit 74 and the device operation unit 61 currently being executed.

  (E18, E19) When the operation of the scanner 16S is interrupted, the device control unit 41 notifies the device operation unit 61 of the operation stop of the scanner 16S.

  (E20) The device operation unit 61 notifies the input step execution unit 74 of the stop.

  (E21 to E23) The input step execution unit 74 notifies the job management unit 71 of this stop via the image job execution unit 73a and the job control unit 72.

  (E24) Since the notification is a job status change, the job management unit 71 notifies the system management unit 52 of this.

  (E25 to E27) Since this notification is a job status change, the system management unit 52 displays an operation stop on the operation panel 15 by notifying the stop via the device operation unit 61 and the device control unit 41. Let The user cancels the jam by looking at the display of the scan cancellation due to the occurrence of the jam error.

  (E28, E29) When this release is detected by the scanner 16S, this is notified to the device operation unit 61 via the device control unit 41.

  (E30) The device operation unit 61 notifies the system management unit 52 of jam error cancellation.

  (E31, E32) The system management unit 52 notifies this cancellation to the operation panel program of the device operation unit 61 on the one hand together with the device identifier, and notifies the job management unit 71 together with the job ID on the other hand to accept job resumption. enable.

  (E33, E34) In response to the release notification, the device operation unit 61 erases the jam error display on the operation panel 15 via the device control unit 41 and the device driver 31.

  (E35 to E37) The user presses the start key on the operation panel 15 to resume the job. This information is supplied to the user service reception unit 81 through the device driver 31, the device control unit 41, and the device operation unit 61 together with the job ID.

  (E38 to E47) In response to this, the user service accepting unit 81 causes the job control unit 72 to resume the ScanToBox basic job via the user service execution unit 82 and the job management unit 71. The job control unit 72 instructs the image job execution unit 73a in the basic job execution unit 73 to restart the basic job. In response to this, the image job execution unit 73a restarts the currently interrupted job step execution unit, in this case, the input step execution unit 74. In response to this, the input step execution unit 74 operates the device control unit 41 via the device operation unit 61. Thereby, the document image reading operation by the scanner 16S is resumed.

According to the present embodiment, when an error occurs or an error is canceled, this is notified from the device operation unit 61 to the job management unit 71 via the system management unit 52, and the operation is sequentially interrupted from the job management unit 71 to the lower layer side. Since the restart instruction is performed, the direction of the instruction between the modules is changed from the upper layer side to the lower layer side regardless of whether there is an error, thereby simplifying the configuration of the program in the job layer 70 and facilitating the design change. .
[15] Notification Service Execution Flow FIG. 11 shows a case in which each functional unit is connected with a line with an arrow and a failure occurs, for example, when paper cannot be fed from the paper cassette 1 of the printer 16P during printing. It is a figure which shows the flow in which a system actively requests | requires notification service, and performs failure occurrence notification service.

  In the following, the operation during printing by the device control unit 41 will be described.

  (F01 to F03) When this failure is detected, the device control unit 41 notifies the device operation unit 61 of this. The device operation unit 61 enters the error identifier in the entity unit 63 and notifies the system management unit 52 of the occurrence of the error event.

  (F04 to F06) In response to this, the system management unit 52 analyzes the error event, determines that the sheet cassette 1 has been invalidated, that is, the sheet cassette 1 has been disconnected, and determines this. The information is displayed on the operation panel 15 via the device operation unit 61 and the device control unit 41.

  (F07) Here, the entity unit 63 includes a notification necessity / unnecessity to the user, an event to be notified (change in device or job status), a notification means such as print or email, and a notification destination in the case of email. Are described as a plurality of notification information. When the system management unit 52 refers to the entity unit 63 and determines that it is necessary to notify the user of the error, the system management unit 52 requests the system service execution unit 83 to notify it with the identifier of the corresponding notification information.

  (F08) Upon receiving this request, the system service execution unit 83 delivers this identifier to the job management unit 71 and generates a notification job to execute the notification service.

  (F09, F10) In response to this, the job management unit 71 acquires the hardware resources such as the memory and the NIC 17 necessary for executing the notification job via the resource management unit 43, and then acquires them to the job control unit 72. The identifier is handed over and a job control instruction is given.

  (F11) In response to this, the job control unit 72 delivers the identifier to the basic job execution unit 73 to instruct basic job execution that constitutes the notification job.

  In response to this, the basic job execution unit 73 transmits the basic job designated as the identifier to the access job execution unit 73b according to the basic job type, and activates it.

  (F12 to F14) In response to this, the access job execution unit 73b transmits an e-mail notifying that the cassette 1 has been detached via the device operation unit 61, the device control unit 43, the device driver 31, and the NIC 17.

Conventionally, such a notification is integrated with the print job. However, in this embodiment, this notification is defined as a notification job independently of a normal job, and responds to the notification service in the same way as a normal job. Since the notification job is executed, the configuration of a program for executing a normal job is simplified, and a new job or an existing job is easily defined by combining the basic job constituting the notification job with other basic jobs. This makes it easy to change the application design.
[16] Address book editing flow If the application layer 50 is made multi-layered in order to facilitate the design change, the relationship between the layers and each functional unit increases and the configuration becomes complicated. In order to avoid this, a device for simplifying the configuration is required.

  FIG. 12 is a diagram showing a flow when editing the address book from the operation panel 15 by connecting the functional units with arrows.

  (G01 to G03) When the operation panel 15 is operated, the information is transmitted to the user service reception unit 81 via the device driver 31, the device control unit 41, and the device operation unit 61 as described above.

  (G04) When this information is an address book editing service request, the user service accepting unit 81 directly executes the address book editing program in the entity unit 63 without passing through the user service executing unit 82 and the job layer 70. Start as.

  (G05 to G08) Thereby, the identifier of the operation screen data for address book editing is supplied from the entity unit 63 to the device operation unit 61 via the user service reception unit 81, and the operation screen data is controlled by the device based on the identifier. The image is supplied to the operation panel 15 via the unit 41 and the device driver 31, and the screen is displayed.

  Thereafter, the address book is interactively edited following such a route.

In this embodiment, the access to the entity unit 63 is unified by receiving a service request at the user service receiving unit 81 and accessing the entity unit 63 directly from the user service receiving unit 81 without going through the job layer 70. Thus, the application layer 50 can be prevented from being complicated, and the configuration of the job layer 70 and the user service execution unit 82 can be simplified. This simplification brings about an effect that the design change of the application layer 50 becomes easy.
[17] Login Execution Flow The user can set whether to validate the authentication / authorization process, and the data is stored in the entity unit 63. In the following description, a case where this process is enabled will be described.

  FIG. 13 is a diagram showing a flow at the time of executing login by connecting the functional units with arrows.

  (H01 to H03) As described above, when information is transmitted from the operation panel 15 to the user service reception unit 81 via the device driver 31, the device control unit 41, and the device operation unit 61, the user service reception unit 81 Interpret service requests.

  (H04) When this information is interpreted as a login request, the user service reception unit 81 directly starts the login program in the system management unit 52 as a work without using the job layer 70.

(H05-H10) In response to this, the system management unit 52 determines whether or not the password input from the operation panel 15 matches that registered in the entity unit 63, and accepts the result as a user service reception. Display on the operation panel 15 via the unit 81, the device operation unit 61, the device control unit 41, and the device driver 31.
[18] Authorization Execution Flow FIG. 14 is a diagram showing a normal service execution flow when each functional unit is connected with a line with an arrow, when authentication / authorization is set valid and login is in progress. .

  (I01 to I03) As described above, information is transmitted from the operation panel 15 to the user service reception unit 81 via the device driver 31, the device control unit 41, and the device operation unit 61.

  (I04) When there is a service request, the user service reception unit 81 instructs the system management unit 52 as an authorization process as a work before instructing the user service execution unit 82 to execute the service.

  (I05-I07) In response to this, the system management unit 52 refers to the data of the entity unit 63 to determine whether the logged-in user can receive this service, and receives the result as a user service reception. Notification to the unit 81.

  (I08-I11) When this is a positive determination notification, the user service reception unit 81 passes the job scenario identifier of the service and the setting value related to the service to the user service execution unit 82, and the user service execution unit 82 Instruct the service to execute. If it is a negative determination notification, the service request is not accepted and a message to that effect is displayed on the operation panel 15 via the device operation unit 61, device control unit 41, and device driver 31.

  Conventionally, authentication / authorization processing is not defined as one of services, and authentication / authorization processing is performed in the upper layer of the service layer 80. However, in this embodiment, authentication / authorization is also considered as one of services. By handling, the processing is unified, and the system management unit 52 is started directly from the user service reception unit 81 without using the user service execution unit 82 and the job layer 70. This makes it possible to avoid complication of the configuration of 70 and to easily change these designs.

  FIG. 16 is a diagram showing a memory map in the DRAM 13D when a plurality of types of basic jobs requiring a data area are executed in parallel processing in the first embodiment.

  In the MFP as in the first embodiment, a plurality of types of jobs commonly use one memory resource as a data area. Therefore, as shown in FIG. 16, an area necessary for executing a new job is stored in the memory. In order to execute a new job that requires a data area in such a case, it is necessary to wait until a sufficient free area is secured in the memory.

  Therefore, in the second embodiment, a method capable of immediately using the data area will be described.

  FIG. 17 is a flowchart of processing when power is turned on. In the following, the step identification codes in the figure are shown in parentheses.

  (S1) The BIOS stored in the EEPROM 13E1 is activated.

  (S2) The BIOS performs hardware initialization processing, software initialization processing, and the like of the image forming apparatus 10.

  (S3) Next, the BIOS activates the OS 32 stored in the EEPROM 13E2.

  FIG. 18 is a diagram showing a memory map of the DRAM 13D after securing the data area.

  (S4) As shown in FIG. 18, the OS 32 divides the empty area of the DRAM 13D into blocks and reserves it as a data area. This one block is an area where image data for one page can be stored, for example. In FIG. 18, an area in the DRAM 13D used by the OS 32 is omitted.

  (S5) After securing this, the OS 32 activates the application described in the first embodiment. In this embodiment, the OS 32 and the application are activated on the EEPROM 13E2, but they may be loaded into the SDRAM or the like and activated from there.

  Thereafter, when the user service execution unit 82 instructs the execution of the job, the resource management unit 43 performs the following processing, for example, in step A10 shown in FIG.

  FIG. 19 is a diagram showing a flowchart of processing of the resource management unit 43 according to the present invention, and FIG. 20 is a diagram for explaining a part of this flowchart. In parentheses are step identification codes in FIG.

  (S10) One of the free blocks secured as the data area in the DRAM 13D shown in FIG. 18 is acquired for executing the basic job (see FIG. 20).

  (S11) It is determined whether there are still empty blocks in the DRAM 13D. If the determination is affirmative, the process ends. If the determination is negative, the process proceeds to the next step S12. Note that the print basic job and the ScanToBox basic job shown in FIG. 20 use one block for one page of data.

  (S12) A save block is determined based on the rule. Here, as a rule, for example, a basic job that uses the largest number of blocks is found, and a block that is processed most recently among these blocks is set as a save block. When there are a plurality of basic jobs using the same number of blocks, one basic job is specified according to a preset priority order, and a save block is determined among them. In addition, a plurality of basic jobs that are waiting are identified as basic jobs including a save block.

  (S13) As shown in FIG. 20, the data in the determined block is temporarily saved in an auxiliary storage device such as an external flash memory (not shown in FIG. 15).

  The data in the saved block is returned to the empty block when, for example, two or more empty blocks are secured in the DRAM 13D.

  In this way, when the resource management unit 43 secures a data area next time, there is always an empty block in the DRAM 13D, so that memory resources are insufficient at the start of job execution. As a result, the empty block can be used as a data area immediately.

  Further, by securing a data area in the DRAM 13D in advance when the power is turned on, the data area can always be used even if a part of the area in the DRAM 13D is used for other purposes by the OS 32 or an application. There is an effect.

  Note that the present invention includes various other modifications.

  For example, in FIG. 2, since the job information 77 is information for each job, it is included in the job layer 70. However, since it is information, it can be arranged outside the job layer 70. For example, the entity part 63, the common part 51, etc. May be included.

  In addition, there is an arbitrary place where the division boundary between the device operation unit 61 and the device control unit 41 in FIG. 2 is set, and the device operation unit 61 uses the device control unit 41 to control the device without depending on the model. Anything to do.

  Furthermore, a plurality of functional units shown in FIG. For example, the user service reception unit 81 and the user service execution unit 82 are set as one user service providing unit, the job control unit 72, the image job execution unit 73a and the access job execution unit 73b are set as one job execution unit, and an input step The execution unit 74, the edit step execution unit 75, and the output step execution unit 76 may be configured as one step execution unit.

  Furthermore, it is arbitrary in which layer 60 to 80 each functional unit shown in FIG. 2 is arranged. For example, the job is divided into one or more basic jobs based on the job scenario, and these are sequentially executed. The job control unit 72 to be instructed may be arranged in the user service execution unit 82 in the service layer 80 above the job layer 70 or in this lower layer. In this case, the job management unit 71 receives an instruction to execute a basic job from the job control unit 72, causes the resource management unit 43 to secure hardware resources necessary for the basic job, and then causes the basic job execution unit 73 to execute the above execution. Communicate instructions. According to this configuration, it is possible to add or change jobs by combining jobs without changing the job layer 70 or lower, thereby providing an effect that design change is facilitated.

  Further, the system management unit 52 shown in FIG. 2 collectively manages both the system state and the user, but manages only one of them, and is a functional unit different from the system management unit 52. May be configured to manage the other. Further, in the user management that is the responsibility of the system management unit 52, the authentication process shown in FIG. 13 or the authorization process shown in FIG.

  Furthermore, the structure which includes a part or all of each function part 41-43 of the middleware layer 40 shown in FIG. 2 as a part of application may be sufficient.

  The basic job scenario only needs to include information on a plurality of job steps and their execution order. For example, the basic job scenario may be a set of arguments (inputKind, editKind, outputKind) of a function fnc (inputKind, editKind, outputKind). Here, inputKind, editKind, and outputKind correspond to the types of image input means, image processing, and image output means, respectively, and processing is performed in this order in the function fnc, and the order of arguments indicates the job step execution order. .

  Similarly, the job scenario only needs to include one or more job types and execution order information, and may be a set of arguments (jobKind1, jobKind2) of the function fnc (jobKind1, jobKind2), for example. Here, jobKind1 and jobKind2 indicate the first and second job types, respectively, and the order of arguments indicates the job execution order.

  Further, the basic job scenario has been described in which the basic job execution unit 73 is determined based on the basic job instructed by the job control unit 72. However, the job control unit 72 has a basic job corresponding to the basic job instructed by itself. A configuration may be adopted in which a job scenario is determined and this identifier is transferred to the basic job execution unit 73.

  Further, the job scenario identifier is determined by the user service accepting unit 81 and transferred to the lower layer. However, the job management unit 71 that requires the job scenario determines the identifier and passes it from here to the lower layer. There may be.

  Furthermore, the notification job executed by the system service execution unit 83 may be a basic job, and may be a single basic job constituting the job executed by the user service execution unit 82.

  Further, the case where the OS 32 and the application are stored in the EEPROM 13E2 has been described. However, all or a part of the OS 32 and the application may be stored in a separate storage unit. For example, the OS 32 and the application may be stored in the HDD 14. May be.

  Further, the BIOS may include a boot loader. In this case, in step S3 shown in FIG. 17, the BIOS activates the boot loader, which activates the OS 32.

  Furthermore, although the configuration in which the data area is secured in step S4 shown in FIG. 17 has been described, the data area may be secured in the step subsequent to step S5.

  Further, as shown in FIG. 19, a configuration has been described in which a save block is always determined when there is no empty block, and this block is saved. However, if there is no basic job using a plurality of blocks, Alternatively, it may be determined that there is no save block, and the process is terminated without performing the processes of S12 and S13.

  Furthermore, in the second embodiment, a configuration has been described in which one save block is determined and saved, but a plurality of save blocks may be determined and saved.

  Furthermore, in the second embodiment, the configuration in which the data area is secured in units of blocks has been described. However, the configuration may be such that a data area in which discontinuous free areas are linked is secured instead of in units of blocks. In this case, “empty block” shown in FIG. 19 is “empty data area”, and “evacuation block” is “evacuation area”.

2 is a schematic block diagram illustrating a software hierarchical structure of the image forming apparatus of the present invention. FIG. It is a block diagram which shows the software program part contained in each layer. FIG. 6 is a diagram illustrating a flow when a print service is executed by connecting functional units with arrows. It is a sequence diagram for demonstrating the one part operation | movement of FIG. It is explanatory drawing of the setting value contained in job information. It is a figure which shows the flow at the time of performing a fax transmission service by connecting between each function part with a line with an arrow. It is explanatory drawing of the some service obtained by a basic job and its combination. It is a figure which shows the flow at the time of scan service execution by connecting between each function part with a line with an arrow. It is a figure which shows the flow at the time of executing the file printing service in a box by connecting between each function part with a line with an arrow. FIG. 10 is a diagram illustrating a flow when a jam occurs during execution of a scan service by connecting each functional unit with a line with an arrow. FIG. 5 is a diagram illustrating a flow in which functional units are connected by arrows with arrows and the system actively requests a notification service and executes the failure occurrence notification service when a failure occurs. It is a figure which shows the flow at the time of connecting each function part with the line with an arrow, and editing an address book from the operation panel. It is a figure which shows the flow at the time of login execution by connecting between each function part with a line with an arrow. It is a figure which shows the flow at the time of normal service execution when connecting between each function part with a line with an arrow, when authentication and authorization are set effectively and it is logging in. 1 is a schematic block diagram illustrating a hardware configuration of an image forming apparatus according to an embodiment of the present invention. FIG. 5 is a diagram illustrating a memory map in a DRAM when a plurality of types of basic jobs that require a data area are executed in parallel processing in the first embodiment. FIG. 10 is a flowchart of processing when power is turned on according to the second embodiment. It is a figure which shows the memory map in DRAM after data area ensuring. FIG. 10 is a diagram illustrating a flowchart of processing of a resource management unit according to the second embodiment. It is a figure explaining a part of flowchart shown in FIG.

Explanation of symbols

10 Image forming apparatus 11 MPU
12 interface 13E1 EEPROM
13E2 EEPROM
13D DRAM
14 Hard disk 15 Operation panel 16S Scanner 16P Printer 17 NIC
18 Facsimile modem 19 Compression / decompression ASIC
30 OS layer 31 Device driver 32 OS
40 middleware layer 41 device control unit 42 image processing unit 43 resource management unit 50 application layer 51 common unit 52 system management unit 60 element layer 61 device operation unit 62 image processing operation unit 63 entity unit 70 job layer 71 job management unit 72 job control Unit 73 Basic job execution unit 73a Image job execution unit 73b Access job execution unit 74 Input step execution unit 75 Edit step execution unit 76 Output step execution unit 77 Job information 80 Service layer 81 User service reception unit 82 User service execution unit 83 System Service execution part

Claims (4)

In response to a service request from the instruction input means, a basic job constituting a job is sequentially executed, and the job is an image composed of two or more basic jobs including a common basic job among a plurality of types of jobs. A forming device,
Memory,
An auxiliary storage device;
When starting up the image forming apparatus, a part of the area in the memory is reserved as a job data area, and a plurality of blocks are secured in units of a predetermined amount of blocks. When a part of the data area is allocated, and there is no empty block in the data area, one block in the data area is saved in the auxiliary storage device, and in response to the memory release request of the basic job When the corresponding block in the data area is released, and there are a plurality of empty blocks in the data area due to the memory release, and there are blocks saved in the auxiliary storage device, the free space in the data area Resource securing means for returning the block saved in the auxiliary storage device to the data area so that the number of blocks becomes one;
The image forming apparatus is characterized in that one block free area is secured in the data area before execution of the next basic job. The image forming apparatus according to claim 1, wherein the resource securing unit selects a block of a job to which the largest number of blocks are allocated as a block to be saved. In response to the service request from the instruction input unit, the computer of the image forming apparatus sequentially executes the basic jobs constituting the image forming job after securing the memory resources, and the job is common to a plurality of types of jobs. It consists of two or more basic jobs including basic jobs, and the computer
When starting up the image forming apparatus, a part of the area in the memory is reserved as a job data area, and a plurality of blocks are secured in units of a predetermined amount, and in response to a basic job memory acquisition request, in units of blocks. When a part of the data area is allocated and there is no free block in the data area, one block in the data area is saved in the auxiliary storage device, and in response to a memory release request of the basic job When the corresponding block in the data area is released, and there are a plurality of empty blocks in the data area due to the memory release, and there are blocks saved in the auxiliary storage device, the free space in the data area The block saved in the auxiliary storage device is returned to the data area so that the number of blocks becomes one.
Thus, a memory resource securing method is characterized in that one block free area is secured in the data area before execution of the next basic job. The computer selects a block of a job to which the most blocks are allocated as a block to be saved.
The memory resource securing method according to claim 3.

Images