JP2004110731A - Image forming apparatus and memory storage area securing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus and a storage area securing method which secure more memory areas in a memory area which is managed by application software. <P>SOLUTION: The image forming apparatus has a hardware resource to be used in image formation processing, a process for executing processing regarding image formation based on a program and an operating system which manages execution of the program and the hardware resource. The image forming apparatus has a storage area existing outside management of the operating system and a storage area releasing means which releases the storage area allocated to the process. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an image forming apparatus and a storage area securing method.
[0002]
[Prior art]
2. Description of the Related Art In recent years, an image forming apparatus (hereinafter, referred to as a multifunction peripheral) in which functions of respective apparatuses such as a printer, a copier, a facsimile, and a scanner are housed in a single housing has been known. This multifunction machine includes a display unit, a printing unit, an imaging unit, and the like in a single housing, and provides four types of applications corresponding to a printer, a copy, a facsimile, and a scanner, respectively. It operates as a copy, facsimile and scanner.
[0003]
Such a multi-function device is provided with a memory in which programs are loaded and image data is loaded. In general, this memory is mounted with a minimum necessary storage capacity in order to reduce costs and the like.
[0004]
The memory is used by securing or releasing memory when an application or the like executes processing. An operating system (hereinafter, referred to as an OS) manages a storage area (hereinafter, referred to as a memory area) in securing and releasing.
[0005]
As described above, conventionally, a memory managed by the OS is used with a minimum necessary storage capacity.
[0006]
[Problems to be solved by the invention]
However, in general, if more memory can be secured, more processing can be executed. In particular, data handled by the multifunction machine is image data that is relatively large data, and there is also large data such as a program downloaded via a network in order to update a program of the multifunction machine.
[0007]
In addition, the system call provided by the OS performs basic processing related to the memory and is provided by the core part of the OS. Therefore, application software such as applications and modules which are software other than the OS must independently manage the system call. There is a limit.
[0008]
SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and has as its object to provide an image forming apparatus and a storage area securing method for securing a larger memory area in a memory area managed by application software.
[0009]
[Means for Solving the Problems]
In order to solve the above-described problems, the present invention manages hardware resources used in image forming processing, a process of executing processing related to image formation based on a program, execution of the program, and the hardware resources. In an image forming apparatus having an operating system, the image forming apparatus includes a storage area that is not managed by the operating system and a storage area release unit that releases the storage area allocated to the process.
[0010]
Further, in order to solve the above problems, the present invention provides a hardware resource used in image forming processing, a process of executing processing related to image formation based on a program, execution of the program, and the hardware resource. In an image forming apparatus having an operating system to manage, a storage area outside the management of the operating system, a storage area management unit to manage the storage area, and an offline unit to restrict execution of processing to the process. Storage area releasing means for releasing the storage area allocated to the process whose execution is restricted.
[0011]
Further, in order to solve the above problems, the present invention provides a hardware resource used in image forming processing, a process of executing processing related to image formation based on a program, execution of the program, and the hardware resource. A method for securing a storage area of an image forming apparatus having an operating system to be managed, wherein the storage area is outside the management of the operating system and is allocated to the process.
[0012]
Further, in order to solve the above problems, the present invention provides a hardware resource used in image forming processing, a process of executing processing related to image formation based on a program, execution of the program, and the hardware resource. A method for reserving a storage area of an image forming apparatus having an operating system to be managed, comprising: an offline stage for restricting execution of a process to the process; and a process execution being restricted outside the management of the operating system. Releasing a storage area allocated to the process.
[0013]
As described above, according to the present invention, it is possible to obtain an image forming apparatus and a storage area securing method for securing a larger memory area in a memory area managed by application software.
[0014]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0015]
FIG. 1 shows a configuration diagram of an embodiment of a multifunction peripheral according to the present invention. The multifunction device 1 is configured to include a software group 2, a multifunction device activation unit 3, and hardware resources 4.
[0016]
The multifunction peripheral starting unit 3 is first executed when the power of the multifunction peripheral 1 is turned on, and activates the application layer 5 and the platform 6. For example, the multifunction peripheral starting unit 3 reads the programs of the application layer 5 and the platform 6 from a hard disk device (hereinafter referred to as HDD) or the like, and transfers each read program to a memory area to start. The hardware resources 4 include a black and white laser printer (B & W LP) 11, a color laser printer (Color LP) 12, and hardware resources 13 such as a scanner and a facsimile.
[0017]
Further, the software group 2 includes an application layer 5 and a platform 6 activated on an operating system (hereinafter referred to as an OS) such as UNIX (registered trademark). The application layer 5 includes a program that performs processing specific to a user service related to image formation, such as a printer, a copy, a facsimile, a scanner, and a net file.
[0018]
The application layer 5 uses a printer application 21 that is a printer application, a copy application 22 that is a copy application, a fax application 23 that is a fax application, a scanner application 24 that is a scanner application, and a network. Includes a net file application 25 that provides document services.
[0019]
Further, the platform 6 interprets the processing request from the application layer 5 and generates a request for acquiring the hardware resource 4, and manages one or more hardware resources 4 to control the control service layer 9. And a handler layer 10 for managing the hardware resources 4 in response to the acquisition request from the SRM 39.
[0020]
The control service layer 9 includes a network control service (hereinafter, referred to as NCS) 31, a delivery control service (hereinafter, referred to as DCS) 32, an operation panel control service (hereinafter, referred to as OCS) 33, and a fax control service (hereinafter, referred to as FCS) 34. , An engine control service (hereinafter referred to as ECS) 35, a memory control service (hereinafter referred to as MCS) 36, a user information control service (hereinafter referred to as UCS) 37, a system control service (hereinafter referred to as SCS) 38, a remote service (hereinafter referred to as SCS). , RS) 42, an on-demand update service (hereinafter, OUS) 33, etc. That.
[0021]
In addition, the platform 6 is configured to have an API 53 that can receive a processing request from the application layer 5 by a function defined in advance. The OS executes each software of the application layer 5 and the platform 6 as a process in parallel.
[0022]
The process of the NCS 31 provides a service that can be used in common to applications that require network I / O, and distributes data received from the network by each protocol to each application, or distributes data from each application. Mediation when sending to the network side.
[0023]
For example, the NCS 31 controls data communication with a network device connected via a network by HTTP (HyperText Transfer Protocol Daemon) by HTTP (HyperText Transfer Protocol).
[0024]
The NCS 31 is also used to download an update program from a network.
[0025]
The process of the DCS 32 controls the distribution of stored documents and the like. The process of the OCS 33 controls an operation panel serving as information transmission means between the operator and the main body control. The operation panel is also an input unit for the operator to operate the multifunction machine 1. The FCS 34 process provides an API from the application layer 5 for performing fax transmission / reception using the PSTN or ISDN network, registration / quotation of various fax data managed in a backup memory, fax reading, fax reception printing, and the like. I do.
[0026]
The process of the ECS 35 controls engine units such as the black and white laser printer 11, the color laser printer 12, and the hardware resources 13. The process of the MCS 36 performs memory control such as acquisition and release of a memory and use of an HDD. The process of the UCS 37 manages user information. The process of the RS 42 controls a remote service. The OUS 33 process performs various processes related to download, such as expanding the downloaded update program in a memory.
[0027]
The process of the SCS 38 performs processes such as application management, operation unit control, system screen display, LED display, hardware resource management, and interrupt application control.
[0028]
The process of the SRM 39 controls the system and manages the hardware resources 4 together with the SCS 38. For example, the process of the SRM 39 performs arbitration in accordance with an acquisition request from an upper layer using the hardware resources 4 such as the monochrome laser printer 11 and the color laser printer 12, and controls execution.
[0029]
Specifically, the process of the SRM 39 determines whether the requested hardware resource 4 is available (whether the hardware resource 4 is not used by another acquisition request). The upper layer is notified that the resource 4 is available. The process of the SRM 39 performs scheduling for using the hardware resource 4 in response to an acquisition request from the upper layer, and the content of the request (for example, paper transport and image forming operation by the printer engine, memory reservation, file generation, etc.). Is implemented directly.
[0030]
Further, the handler layer 10 includes a fax control unit handler (hereinafter, referred to as FCUH) 40 that manages a fax control unit (hereinafter, referred to as FCU) described below, and a storage that manages the memory allocated to the process and the memory allocated to the process. An image memory handler (hereinafter, referred to as IMH) 41 as an area management unit. The SRM 39 and the FCUH 40 make a processing request to the hardware resource 4 using the engine I / F 54 that can transmit a processing request to the hardware resource 4 by a function defined in advance.
[0031]
The multifunction device 1 can perform processing required in common by each application on the platform 6 in a unified manner. Next, the hardware configuration of the MFP 1 will be described.
[0032]
FIG. 2 shows a hardware configuration diagram of an embodiment of the multifunction peripheral 1 according to the present invention. The MFP 1 includes a controller 60, an operation panel 70, an FCU 80, a USB device 90, an IEEE 1394 device 100, and an engine unit 110.
[0033]
The controller 60 includes a CPU 61, a system memory (MEM-P) 62, a north bridge (hereinafter, referred to as NB) 63, a south bridge (hereinafter, referred to as SB) 64, an ASIC 66, and a local memory (MEM-C). ) 67, an HDD 68, and a flash memory 69.
[0034]
The operation panel 70 is connected to the ASIC 66 of the controller 60. The FCU 80, the USB device 90, the IEEE 1394 device 100, and the engine unit 120 are connected to the ASIC 66 of the controller 60 via a PCI bus.
[0035]
In the controller 60, the local memory 67, the HDD 68, and the like are connected to the ASIC 66, and the CPU 61 and the ASIC 66 are connected via the NB 63 of the CPU chipset. In this way, if the CPU 61 and the ASIC 66 are connected via the NB 63, it is possible to cope with a case where the interface of the CPU 61 is not disclosed.
[0036]
The flash memory 69 stores programs for executing the applications and modules, and the downloaded update program is stored in the flash memory 64.
[0037]
The ASIC 66 and the NB 63 are not connected via the PCI bus, but are connected via an AGP (Accelerated Graphics Port) 65. As described above, in order to control the execution of one or more processes forming the application layer 5 and the platform 6 of FIG. 1, the ASIC 66 and the NB 63 are connected not through the low-speed PCI bus but through the AGP 65, thereby preventing the performance from deteriorating. In.
[0038]
The CPU 61 performs overall control of the multifunction peripheral 1. The CPU 61 activates and executes the NCS 31, DCS 32, OCS 33, FCS 34, ECS 35, MCS 36, UCS 37, SCS 38, SRM 39, FCU H 40, RS 42, OUS 43 and IMH 41 as processes on the OS, and executes a printer application for forming the application layer 5. 21, a copy application 22, a fax application 23, and a scanner application 24 are activated and executed.
[0039]
The NB 63 is a bridge for connecting the CPU 61, the system memory 62, the SB 64, and the ASIC 66. The system memory 62 is a memory used as a drawing memory or the like of the multifunction peripheral 1. The SB 64 is a bridge for connecting the NB 63 to a ROM, a PCI bus, and peripheral devices. The local memory 67 is a memory used as a copy image buffer and a code buffer.
[0040]
The ASIC 66 is an IC for image processing having hardware components for image processing. The HDD 68 is a storage for storing image data, storing document data, storing programs, storing font data, storing forms, and the like. The operation panel 70 is an operation unit that receives an input operation from the operator and performs display for the operator.
[0041]
Next, in order to explain the process of securing the memory area, a process of downloading an update program performed when updating the program of the multifunction peripheral 1 will be described as an example. Prior to the description, the following description will be made. Describe the processes and applications used.
[0042]
In the present embodiment, expressions such as application, module, and process are used. Since the process generally represents a running program, applications and modules are included in the process. Therefore, there is no essential difference in any of the expressions, but in the present embodiment, the expressions are appropriately used depending on the description contents. Deleting a process (application or module) means releasing a memory area allocated to the process.
[0043]
In a memory area allocated to the process, information necessary for the process to execute a process, such as a program executed by the process and information temporarily used by the process, are loaded.
[0044]
Further, in the present embodiment, the program acquired by downloading is used as the update program, but this update program is not only a program that updates the entire conventional program of the MFP 1 but also merges with the conventional program. Includes difference programs that update programs and parts of conventional programs.
[0045]
Hereinafter, an outline of the process of downloading the update program will be described.
[0046]
Upon receiving a notification from the server provided by, for example, the developer of the multifunction peripheral 1 that the program is to be updated, the multifunction peripheral 1 releases a memory area allocated to the process to expand the update program. Is performed and the update program is expanded in the memory area. Therefore, first, the memory area will be described.
[0047]
In the memory area, which area is allocated to which process is determined in advance. Therefore, the contents of the memory area are usually indicated using a memory map.
[0048]
The memory area will be described using this memory map. FIG. 3 shows a memory map 71 of the system memory 62, which is a volatile storage device, and a memory map 72 obtained by enlarging the shared memory shown in the memory map 71. The memory area VM75 is a memory area managed by the OS.
[0049]
By using the memory area outside the management of the OS in this way, the developer of the MFP 1 can not only perform memory management according to the specifications and characteristics of the MFP 1, but also generate a problem such as a memory leak. The cause can be suppressed.
[0050]
In the memory map 71, a memory area is divided into a shared memory, a printer emulation work memory, a page memory, print data, and the like.
[0051]
Among these, the shared memory is a memory that is used for expanding a program being executed and for a process that is the program being executed to perform processing. Since the memory map 72 shown in FIG. 3 shows a state before the program is expanded, all of the areas are empty areas.
[0052]
When the processes are activated from this state, as shown in the memory map 73 in FIG. 4, the memory areas in the shared memory allocated to the respective processes are used. FIG. 5 is a diagram showing the process operation status at this time. The operation status of the process shown in FIG. 5 is a status in which all processes are performing normal processing.
[0053]
Thus, for example, as shown in FIG. 6, it is assumed that a memory area allocated to each application or a part of the process of the service layer module is released. As a result, as shown in the memory map 74 of FIG. 7, all the areas other than the memory area allocated to the service layer module that has not been released become free areas.
[0054]
This makes it possible to secure a larger memory area in the memory area managed by the application software.
[0055]
The obtained free area is used as a memory area for expanding the downloaded update program. The downloaded update program is stored in the flash memory 69 as a new program.
[0056]
In FIG. 6, the NCS 31 and the SCS 38 are off-line, but the off-line state indicates that the process is restricted from being executed. More specifically, although it is possible to receive an engine state notification, a notification of occurrence of an abnormality, and the like, it is a state in which an execution operation for an external event is prohibited. Therefore, as shown in FIG. 6, a process whose execution is restricted is refused an execution request from another process.
[0057]
Next, the disappearance of the process will be described by taking the SCS 38 and the application as examples. As shown in FIG. 8, the process of the SCS 38 and the process configuring the application mutually register an error handler at the time of startup. In this case, the error handlers confirm each other's existence. Therefore, as shown in FIG. 9, when the application process disappears, the error handler of the SCS 38 recognizes that the application process has disappeared, and an error occurs.
[0058]
Therefore, in order to avoid an error, the SCS 38 stops the application error handler in advance and then kills the application process, as shown in FIG. By doing so, the SCS 38 can avoid occurrence of an error because the application error handler is stopped even if the application process disappears. Note that “KILL” shown in the figure means a command for extinguishing a process.
[0059]
The details of the process related to the download described above will be described with reference to a sequence diagram and a flowchart.
[0060]
FIG. 11 is a sequence diagram illustrating a process in which the multifunction peripheral 1 deletes two applications (applications A81 and B82), downloads an update program, and updates the program stored in the flash memory 69. This process is performed by the NCS 31, the OUS 43 corresponding to the data expanding unit, the SCS 38 corresponding to the storage area releasing unit, the off-run unit, and the restarting unit, and the engine firmware 55.
[0061]
Hereinafter, the sequence diagram will be described. In step S101, the NCS 31 receives a program update start notification from the network, and in step S102, notifies the OUS 43 of a program update start notification indicating the start of program update. The OUS 43 notified of the start of the program update notifies the SCS 38 of an application offline request in step S103. The application offline request is a request for bringing the application to the offline state described above. Note that the off-line request in this sequence diagram also includes a request for extinguishing the application after the off-line state.
[0062]
The application offline request is notified to the application via the SCS 38, but the application notified of this request must shift to the offline state unless the application is operating.
[0063]
The “operation as an application” will be specifically described using the copy application 22 as an example. The “operation as an application” refers to, for example, an operation of executing a copy process in the copy application 22.
[0064]
Therefore, unless the copy application 22 is executing a copy process which is an operation as a copy application, it must operate in an offline state.
[0065]
In addition, the process that is operating in the off-line state can execute the restricted process by removing the restriction on the execution of the process of prohibiting the execution operation for an external event. Therefore, even when the application is operating in the offline state, the content notified from another application or the like is retained, and based on the content retained when the restriction on the execution of the process is released. Processing can be restarted.
[0066]
Returning to the description of the sequence diagram, the SCS 38 notified of the application offline request from the OUS 43 notifies the application A81 and the application B82 of the application offline shift request in steps S104 and S105.
[0067]
When the application A81 and the application B82, which have been notified of the application offline shift request, can each shift to the offline state, they notify the SCS 38 of an application offline response (OK). In the case of this sequence diagram, since both the application A81 and the application B82 can shift to the offline state, the application A81 and the application B82 notify the SCS38 of the application offline response (OK) in step S106 and step S107, respectively. ing.
[0068]
The SCS 38 notified of the application offline response (OK) executes the disappearance of the application A81 and the application B82.
[0069]
In step S108, the SCS 38 that has executed the disappearance of the application notifies the OUS 43 of the completion of the disappearance of the application in step S108 as an application offline determination (completion of the process KILL). The OUS 43 notified of the application offline determination downloads the update program and expands the update program in a memory area obtained by the disappearance of the application.
[0070]
Next, in step S109, the OUS 43 notifies the SCS 38 of a remote ROM update start request that is a program update start request. The SCS 38 notified of the remote ROM update start request masks a key event. The mask of the key event is a process of not accepting an event generated when a key displayed on the operation panel 70 is pressed.
[0071]
Next, the SCS 38 transmits the downloaded update program to the engine firmware 55 in step S110 in order to perform a program update process. The engine firmware 55 updates the program, and notifies the SCS 38 of the result in step S111.
[0072]
When notified of the result of updating the program, the SCS 38 issues a reboot preparation request to the engine firmware 55 in step S112. Then, when notified of the completion of the reboot preparation from the engine firmware 55 in step S113, the SCS 38 performs a forced reboot and ends the program update process.
[0073]
As described above, the SCS 38 releases the memory area allocated to the process, and the OUS 43 downloads the update program for updating the program using the NCS 31, and expands the update program in the memory area released by the SCS 38.
[0074]
Next, details of the processing of the OUS 43 and the SCS 38 will be described with reference to flowcharts.
[0075]
First, the processing of the OUS 43 will be described with reference to the flowchart of FIG. In step S201, the OUS 43 is notified of the start of the program update from the NCS 31. In the next step S202, the OUS 43 checks the SUM value for checking whether the received program update start notification itself is normal data. If the program update start notification is not normal data, the OUS 43 executes step S203. Then, the program update process ends.
[0076]
If it is determined in step S202 that the program update start notification is normal data, the OUS 43 notifies the SCS 38 of an application offline request for causing the application to go offline and disappear in step S204. Upon receiving the app offline determination as a response to the app offline request in step S205, the OUS 43 determines in step S206 whether the execution of the app offline has been completed. The process in step S206 is a process for ending the program update process in step S203 when notified that the application offline has not been determined.
[0077]
When the OUS 43 determines in step S206 that the execution of the application offline has been completed, in step S207, the OUS 43 determines whether the update program can be expanded in the memory area secured by deleting the application.
[0078]
If the update program cannot be expanded, the OUS 43 sets the secured memory area to a state in which the program is not updated in step S209. Then, the OUS 43 notifies the SCS 38 of a remote ROM update start request, which is a program update start request, in step S210, and ends the processing. In this case, since the memory area is set so as not to execute the program update, the program update process is not executed.
[0079]
When the OUS 43 determines that the update program can be expanded in Step S207, the OUS 43 expands the update program in the memory area in Step S208. Then, the OUS 43 notifies the SCS 38 of a remote ROM update start request, which is a program update start request, in step S210, and ends the processing.
[0080]
Next, the processing of the SCS 38 will be described with reference to the flowchart of FIG. In step S301, the SCS 38 receives an application offline request from the OUS 43. In step S302, the SCS 38 notified of the application offline request notifies each application of the application offline shift request.
[0081]
In the next step S303, if the responses from all the applications are not the application offline responses (OK), in step S304, the SCS 38 notifies each application of the release of the application offline. As a result, the application can execute the restricted processing. Next, the SCS 38 notifies the OUS 43 that the application did not go offline in step S305, and ends the processing.
[0082]
If the responses from all the applications are application off-line responses (OK) in step S303, the SCS 38 deletes the applications in step S306. Then, in step S307, the SCS 38 notifies the OUS 43 of the determination of the application offline.
[0083]
Next, in step S308, the SCS 38 receives a remote ROM update start request, which is a program update start request, from the OUS 43. In step S309, the SCS 38 masks the key / touch panel operation event on the operation panel 70 to mask the key event. Do.
[0084]
In this way, when the program is updated, by invalidating the operation panel 70, the update process can be performed promptly, and unrestricted functions can be executed. It can be executed even during program update.
[0085]
Next, in step S310, the SCS 38 executes a program update process, executes a reboot in step S311 to restart the MFP 1, and ends the process.
[0086]
Next, the details of the process of eliminating the process of step S306 will be described with reference to the flowchart of FIG. In step S401, the SCS 38 masks a process disappearance error detection process prepared in a kernel which is a core part of the OS. Then, the SCS 38 stops the error processing of the inter-process communication in step S402. Then, in step S403, the SCS 38 deletes the application process. Next, the SCS 38 deletes the application registration information stored in the SCS 38 in step S404, and ends the processing.
[0087]
Next, apart from the above-described processing, a processing for deleting an application according to the size of the update program downloaded by the OUS 43 will be described with reference to a sequence diagram and a flowchart.
[0088]
FIG. 15 is a sequence diagram illustrating a process of deleting an application according to the size of an update program to be downloaded.
[0089]
In step S501, the NCS 31 receives the program update start notification from the network, and in step S502, notifies the OUS 43 of the program update start notification indicating the start of the program update. The OUS 43 notified of the start of the program update notifies the SCS 38 of an application offline request in step S503.
[0090]
The SCS 38 notified of the application offline request from the OUS 43 notifies the application A81 and the application B82 of the application offline shift request in steps S504 and S505.
[0091]
When the application A81 and the application B82, which have been notified of the application offline shift request, can each go offline, the application A81 and the application B82 notify the SCS 38 of an application offline response (OK). In the case of this sequence diagram, since both the application A81 and the application B82 can be in the offline state, the application A81 and the application B82 notify the SCS38 of the application offline response (OK) in steps S506 and S507, respectively. ing.
[0092]
In step S508, the SCS 38 notified of the application offline response (OK) notifies the OUS 43 of an application offline determination indicating that the application has gone offline.
[0093]
The OUS 43 notified of the offline determination of the application notifies the SCS 38 of the memory release request in step S509 to release the memory area used by the application whose execution is restricted. The memory area requested to be released by the memory release request is a memory area used when an application temporarily stores image information or stores information on a current operation, and is allocated to a process. Part of the memory area.
[0094]
The SCS 38 notified of the memory release request notifies the application A 81 and the application B 82 of the memory release request in steps S510 and S511. The application A81 and the application B82 which have been notified of the memory release request release the memory areas, respectively, and notify the SCS 38 of a memory release completion response in steps S512 and S513.
[0095]
The SCS 38 notified of the memory release completion response notifies the OUS 43 of a memory release completion response indicating that the memory release has been completed in step S514.
[0096]
The OUS 43 notified of the memory release completion response performs a memory size check for checking the free space of the memory. Then, at this point, since there is not enough memory available for expanding the update program to be downloaded, the OUS 43 notifies the SCS 38 of the process KILL request for deleting the process constituting the application to the SCS 38 in step S515. I do.
[0097]
The SCS 38 notified of the request for the process KILL first deletes the application B82. Then, in step S516, the SCS 38 sends a process KILL completion response to the OUS 43.
[0098]
Therefore, the OUS 43 checks the memory size again. However, since there is not enough memory available for expanding the update program to be downloaded, the OUS 43 again notifies the SCS 38 of the process KILL request in step S517.
[0099]
The SCS 38 notified of the process KILL request again deletes the application A81. Then, in step S518, the SCS 38 notifies the OUS 43 of a process KILL completion response.
[0100]
The OUS 43 notified of the process KILL completion response checks the memory size. OUS43 downloads and deploys the update program since the memory of the memory for expanding the update program to be downloaded is obtained by the disappearance of the application A81.
[0101]
Then, in step S519, the OUS 43 notifies the SCS 38 of a remote ROM update start request. The SCS 38 notified of the remote ROM update start request masks a key event.
[0102]
Next, in step S520, the SCS 38 transmits the downloaded update program to the engine firmware 55 in order to perform a program update process. The engine firmware 55 updates the program, and notifies the SCS 38 of the result in step S521.
[0103]
When notified of the result of updating the program, the SCS 38 issues a reboot preparation request to the engine firmware 55 in step S522. Then, in step S523, when notified of the completion of the reboot preparation from the engine firmware 55, the SCS 38 performs a forced reboot, and the program update process ends.
[0104]
In this manner, the SCS releases the memory area allocated to the process according to the size of the update program to be downloaded.
[0105]
Next, details of the processing of the OUS 43 and the SCS 38 will be described with reference to flowcharts.
[0106]
First, the process of the OUS 43 will be described with reference to the flowchart of FIG. In step S601, the OUS 43 is notified from the NCS 31 of the start of the program update. In the next step S602, the OUS 43 checks the SUM value for checking whether the received program update start notification itself is normal data. If the program update start notification is not normal data, the OUS 43 executes step S603. Then, the program update process ends.
[0107]
If it is determined in step S602 that the program update start notification is normal data, the OUS 43 notifies the SCS 38 of an application offline request in step S604. In step S605, when the OUS 43 receives the app off-line determination which is a response to the app off-line request, in step S606, the OUS 43 determines whether the execution of the app off-line has been completed.
[0108]
If the OUS 43 determines that the application offline has not been determined in step S606, the process of updating the program ends in step S603.
[0109]
If the OUS 43 determines in step S606 that the execution of the application offline has been completed, the OUS 43 notifies the SCS 38 of a memory release request in step S607. Then, in step S608, upon receiving the memory release completion from the SCS 38, the OUS 43 determines in step S609 whether a memory area required for developing the update program has been secured.
[0110]
When the OUS 43 determines that the memory area could not be secured, the OUS 43 determines in step S610 whether or not the processes can be deleted in a predetermined priority order.
Here, the prescribed priority order will be described. First, the extinction of a process is to release the memory area to which the process is allocated, as described above.
[0111]
Therefore, first, as for the memory area allocated to the application or the like, as shown in the memory map 73 (see FIG. 4), the area is allocated to the memory for each application or module. The allocated memory area is further composed of two areas. In the present embodiment, one of these memory areas is a fixed area, and the other is a variable area described above. The fixed area is an area for storing information required regardless of whether each application executes a job, such as storing a status notification of the engine unit 110 (see FIG. 2). If the state of the engine unit 110 is not stored in the information, for example, when the offline state is released and the process executes the process again, the actual state of the engine unit 110 cannot be grasped. May cause operation.
[0112]
The memory map representing the fixed area described above will be described with reference to FIG. FIG. 19 shows a memory map 76 representing a fixed area, and shows a memory area allocated to each application and its size.
[0113]
In FIG. 19, for example, the fixed area for the copy application is located at the head in the shared memory, and its size is 5 MB (Mega Byte). Similarly, the assigned positions and the sizes of the other applications are indicated.
[0114]
The free areas 77a, 77b, 77c, 77d, and 77e are variable areas of each application, and in the memory map 76, are free areas because they have already been released.
[0115]
The order of the processes to be deleted is determined in advance based on the memory area allocated in this way and the priority of the process. As shown in FIG. 17, the order may be, for example, a “default” order defined according to the priority of the process in the multi-function peripheral 1 or a “memory size” which is the size of the memory area allocated to the process. ”Or the order of priority determined by the order of the start address of the memory area allocated to the process in the“ shared memory ”(see FIG. 4).
[0116]
In this case, the “default” order is an order in which, in the multifunction peripheral 1, an application having a higher use frequency and a higher priority is deleted last.
[0117]
The “memory size” order is an order determined according to the size of the allocated memory area. As shown in the memory map 76, the size of the memory area specifically allocated to each application is such that the fixed area for the copy application 22 is 5 MB, the fixed area for the printer application 21 is 3.5 MB, The fixed area for the FAX application 23 is 4.5 MB, the fixed area for the scanner application 24 is 3 MB, and the fixed area for the net file application 25 is 4 MB. Therefore, when releasing the allocated memory areas in descending order of the size, the order of the “memory size” is the order shown in FIG.
[0118]
The order of the "shared memory" is determined according to the position of the storage area allocated to the process, such as the order of the start address of the memory area, as described above. Accordingly, in the memory map 76, the head address of the memory area displayed on the memory map 76 becomes smaller, so that the order is as shown in FIG.
[0119]
If the processes can be deleted in any order described above, the OUS 43 notifies the SCS 38 of the process KILL request in step S611. When the OUS 43 receives the completion of the process KILL from the SCS 38 in step S612, the OUS 43 performs the determination in step S609 again.
[0120]
Returning to the process of step S610, if the OUS 43 determines that the processes cannot be eliminated in the specified priority order, the OUS 43 determines in step S615 whether to execute a reboot. The process of step 615 is a process of determining whether to execute the reboot based on whether the application has been deleted at least once.
[0121]
If the OUS 43 has not deleted the application even once, in step S617, the OUS 43 notifies the SCS 38 of the release of the application offline, and ends the processing. As a result, the application returns to a state where the restricted processing can be executed.
[0122]
If the OUS 43 has deleted the application at least once, the OUS 43 notifies the SCS 38 of a reboot request in step S616, and ends the processing.
[0123]
Returning to the processing of step S609, if the OUS 43 can secure a memory area necessary for developing the update program, the OUS 43 expands the update program in the memory area in step S613. Then, the OUS 43 notifies the SCS 38 of the remote ROM update start request in step S614, and ends the processing.
[0124]
Next, the processing of the SCS 38 will be described with reference to the flowchart of FIG. In step S701, the SCS 38 is notified of the application offline request from the OUS 43. In step S702, the SCS 38 notified of the application offline request requests each application to shift to the application offline.
[0125]
In the next step S703, when the responses from all the applications are not the application offline responses (OK), in step S704, the SCS 38 notifies each application of the release of the application offline. Then, in step S705, the SCS 38 notifies the OUS 43 that the application has not gone offline, and ends the processing.
[0126]
If the responses from all the applications are application offline responses (OK) in step S703, the SCS 38 notifies the OUS 43 of the application offline determination in step S706.
[0127]
Next, when the memory release request is notified from the OUS 43 in step S707, the SCS 38 causes the application to execute the memory release processing in step S708, and notifies the OUS 43 of the memory release completion in step S709.
[0128]
When the SCS 38 notifies the OUS 43 of the completion of the memory release, the processing branches according to the request of the OUS 43. First, when the SCS 38 is notified of the process KILL request from the OUS 43, the SCS 38 branches from step S710 to step S711, and the application is deleted. Then, the SCS 38 notifies the OUS 43 of the completion of the process KILL in step S712, and performs the process of step S710 again.
[0129]
If the SCS 38 has not been notified of the process KILL request in step S710, the SCS 38 branches from step S710 to step S713, and determines whether a remote ROM update start request has been notified from the OUS 43.
[0130]
If the SCS 38 is notified of the remote ROM update start request in step S713, the SCS 38 masks the key / touch panel operation event and masks the key event in step S714. Then, the SCS 38 executes a step S715 program update process. Further, in the next step S716, the start of the download, the update status of the program, and the like are notified from the RS 42 (see FIG. 1) to the service center or the like via the network, and in step S717, the process is rebooted and the process is terminated. Note that the service center is, for example, a server provided at a manufacturer for performing maintenance or inspection of the multifunction peripheral 1 or a server provided at a distributor of an update program. The status information of each application or module may be transmitted to the service center, or the service center may record the log.
[0131]
If the SCS 38 has not received the remote ROM update start request in step S713, the SCS 38 determines whether a reboot request has been received from the OUS 43 in step S718.
[0132]
If the notification from the OUS 43 is not a reboot request, the SCS 38 performs the process of step S710 again. If the notification from the OUS 43 is a reboot request, the SCS 38 notifies the service center or the like via the network from the RS 42 that the download has failed in step S719 and performs the reboot process in step S719, performs the reboot in step S717, and ends the process. I do.
[0133]
Next, a process in which the IMH 41 releases a variable area used by an application will be described.
[0134]
First, a process in which the IMH 41 releases a variable area used by an application will be described with reference to a sequence diagram of FIG.
[0135]
The sequence diagram shown in FIG. 20 shows the process from step S509 to step S514, which is a portion changed by the process of the IMH 41 in the sequence diagram of FIG.
[0136]
In step S509, as in FIG. 15, the OUS 43 notifies the SCS 38 of a memory release request. The SCS 38 that has been notified of the memory release request notifies the IMH 41 of the memory release request in step S1, unlike FIG. The IMH 41 notified of the memory release request releases the variable area of each application, and notifies the SCS 38 of a memory release completion response in step S2. The SCS 38 notified of the memory release completion response from the IMH 41 notifies the OUS 43 of the memory release completion response in step S514, as in FIG.
[0137]
Next, a flowchart of the IMH 41 that performs this processing will be described with reference to FIG.
[0138]
In step S801, the application starts, and in step S802, the application secures a memory for a fixed area. At that time, the IMH 41 holds fixed area information, which is storage area information, in step S803.
[0139]
Next, when the application secures the memory for the variable area in step S804, the IMH 41 holds the variable area information as the storage area information in step S805.
[0140]
As described above, the storage area information including the variable area and the fixed area has a structure shown in FIG. In FIG. 26, for example, the storage area information of the fixed area of the application A81 includes four pieces of information: a fixed area start address 0x100000, a fixed area end address 0x1FFFFF, a variable area start address 0x200000, and a fixed area end address 0x24FFFF. . The same applies to other applications. The above address is displayed in hexadecimal. When the fixed area and the variable area are continuous, the variable area end address is not particularly required. Furthermore, when the areas allocated to each application are continuous, the fixed area end address is not particularly required.
[0141]
By holding the storage area information, the IMH 41 can release the memory area used by the application based on the held storage area information.
[0142]
Returning to the description of the flowchart, when the IMH 41 receives the memory release request from the SCS 38 in step S806, the IMH 41 releases the variable area of each application in step S807. Then, in step S808, the IMH 41 notifies the SCS 38 of a memory release completion response.
[0143]
As described above, when the IMH 41 receives the online release from the SCS 38 in step S809 with the variable area released, the IMH 41 again retains the variable area information of each application in step S810.
[0144]
【The invention's effect】
As described above, according to the present invention, it is possible to obtain an image forming apparatus and a storage area securing method for securing a larger memory area in a memory area managed by application software.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of an embodiment of a multifunction peripheral according to the present invention.
FIG. 2 is a hardware configuration diagram of an embodiment of the multifunction peripheral according to the present invention.
FIG. 3 is a diagram showing a memory map.
FIG. 4 is a diagram showing a memory map of a shared memory.
FIG. 5 is a diagram showing a process operation status.
FIG. 6 is a diagram showing a process disappearance state.
FIG. 7 is a diagram showing a memory map.
FIG. 8 is a diagram showing a state of registration of an error handler.
FIG. 9 is a diagram showing an error caused by the disappearance of a process.
FIG. 10 is a diagram illustrating a state in which an error is avoided.
FIG. 11 is a sequence diagram illustrating a process of updating a program.
FIG. 12 is a flowchart illustrating OUS processing.
FIG. 13 is a flowchart illustrating processing of the SCS.
FIG. 14 is a flowchart showing a process of extinguishing a process.
FIG. 15 is a sequence diagram illustrating a process of updating a program.
FIG. 16 is a flowchart showing OUS processing.
FIG. 17 is a diagram showing the order of disappearance.
FIG. 18 is a flowchart showing processing of SCS.
FIG. 19 is a diagram showing a memory map representing a fixed area.
FIG. 20 is a sequence diagram showing an IMH process.
FIG. 21 is a flowchart illustrating IMH processing.
FIG. 22 is a diagram showing storage area information.
[Explanation of symbols]
1. Fusion machine
2. Software group
3. Fusion machine starter
4 ... Hardware resources
5. Application layer
6 ... Platform
9 ... Control service layer
10 Handler layer
11 Black and white laser printer (B & W LP)
12 ... Color laser printer (Color LP)
13 ... Hardware resources
21 ... Printer application
22 ... Copy application
23 ... Fax application
24 ... Scanner application
25 ... Net file application
31 Network Control Service (NCS)
32: Delivery control service (DCS)
33 ... Operation panel control service (OCS)
34: Fax control service (FCS)
35 ... Engine Control Service (ECS)
36 ... Memory control service (MCS)
37 ... User Information Control Service (UCS)
38 ... System control service (SCS)
39 ... System Resource Manager (SRM)
40: Fax control unit handler (FCUH)
41 ... Image memory handler (IMH)
42 ... Remote service (RS)
43… On-demand update service (OUS)
53 ... Application program interface (API)
54 ... Engine I / F
55 ... Engine farm
60 ... Controller
61 ... CPU
62: System memory (MEM-P)
63… North Bridge (NB)
64 ... South Bridge (SB)
65 ... AGP (Accelerated Graphics Port)
66… ASIC
67: Local memory (MEM-C)
68 ... Hard disk drive (HDD)
69… Flash memory
70 ... Operation panel
71, 72, 73, 74, 76 ... memory map
75 ... VM
80: Fax control unit (FCU)
81: Application A
82: Application B
90 ... USB device
100 ... IEEE1394 device
110 ... Engine part

Claims (25)

An image forming apparatus comprising: a hardware resource used in an image forming process; a process of executing a process related to image forming based on a program; and an operating system that executes the program and manages the hardware resource.
A storage area outside the control of the operating system;
An image forming apparatus comprising: a storage area release unit that releases the storage area allocated to the process. 2. The image forming apparatus according to claim 1, further comprising a data expansion unit that uses the storage area released by the storage area release unit as a storage area for expanding data. The image forming apparatus according to claim 2, wherein the storage area release unit releases a storage area allocated to the process according to a size of a storage area used by the data development unit. The image forming apparatus according to claim 1, wherein the storage area release unit releases the storage area allocated to the process in a predetermined order. The image forming apparatus according to claim 4, wherein the order is determined according to a priority of the process. The image forming apparatus according to claim 4, wherein the order is determined according to a size of a storage area allocated to the process. The image forming apparatus according to claim 4, wherein the order is determined according to a position of a storage area allocated to the process. The image forming apparatus according to claim 2, further comprising: a restart unit configured to restart the image forming apparatus when the data development unit finishes using the storage area. The image forming apparatus according to claim 1, wherein the storage area is provided in a volatile storage device. An image forming apparatus comprising: a hardware resource used in an image forming process; a process of executing a process related to image forming based on a program; and an operating system that executes the program and manages the hardware resource.
A storage area outside the control of the operating system;
Storage area management means for managing the storage area;
Offline means for restricting the execution of processing for the process,
An image forming apparatus comprising: a storage area release unit that releases the storage area allocated to the process whose execution is restricted. 2. The image forming apparatus according to claim 1, wherein the storage area management unit holds storage area information regarding a storage area used by the process. 12. The image forming apparatus according to claim 11, wherein the storage area management unit releases a storage area used by the process based on the stored storage area information. The image forming apparatus according to claim 10, wherein, when the execution of the process is restricted, the offline unit releases a storage area used by the process whose execution is restricted. 14. The image forming apparatus according to claim 13, wherein the off-line unit causes the storage area management unit to release a storage area used by a process whose execution is restricted. 11. The image forming apparatus according to claim 10, wherein the process whose execution has been restricted can execute the restricted processing when the offline unit releases the restriction. The image forming apparatus according to claim 10, further comprising a data expansion unit that uses the storage area released by the storage area release unit. 17. The image forming apparatus according to claim 16, wherein the storage area release unit releases a storage area allocated to the process according to a size of a storage area used by the data development unit. 18. The image forming apparatus according to claim 10, wherein the storage area release unit releases storage areas allocated to the processes in a predetermined order. 19. The image forming apparatus according to claim 18, wherein the order is determined according to a priority of the process. 19. The image forming apparatus according to claim 18, wherein the order is determined according to a size of a storage area allocated to the process. 19. The image forming apparatus according to claim 18, wherein the order is determined according to a position of a storage area allocated to the process. 17. The image forming apparatus according to claim 16, further comprising a restart unit that restarts the image forming apparatus when the data development unit ends use of the storage area. The image forming apparatus according to claim 10, wherein the storage area is provided in a volatile storage device. Securing a storage area of an image forming apparatus having hardware resources used in image forming processing, a process of executing processing related to image formation based on a program, and an operating system for executing the program and managing the hardware resources The method,
A method for reserving a storage area, which is outside the control of the operating system and releases a storage area allocated to the process. Securing a storage area of an image forming apparatus having hardware resources used in image forming processing, a process of executing processing related to image formation based on a program, and an operating system for executing the program and managing the hardware resources The method,
An off-line step of restricting the execution of the processing for the process;
A storage area releasing step of releasing a storage area allocated to the process which is outside the control of the operating system and whose execution of processing is restricted.

Images