JP2007174315A - Apparatus and application management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an apparatus capable of easily performing function addition and repair, and efficiently attaining a mechanism of general-purpose application management. <P>SOLUTION: The apparatus capable of executing a plurality of applications has an apparatus state managing means for judging the acceptance or rejection of application usage on the basis of a state of the apparatus in response to an application execution request, an application configuration managing means for managing a configuration of applications, and an application state managing means for managing state information to be a factor of acceptance or rejection judgement to use a corresponding application for each application. The application configuration managing means has an application managing means for judging the acceptance or rejection to use an application on the basis of the state of the application and manages the configuration of applications having a plurality of functions by a hierarchical structure of the application managing means. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a device and an application management program, and more particularly to a device and an application management program capable of executing a plurality of applications.

  2. Description of the Related Art Conventionally, there has been known a multi-function machine in which a plurality of functions such as a printer, a copy, and a scanner are stored in a single casing. In such a multifunction device, a plurality of applications called a printer application, a copy application, and a scanner application are mounted on a general-purpose OS such as UNIX (registered trademark), and a plurality of functions are realized while switching execution processes of these applications. It was.

  However, since the printer application, the copy application, and the scanner application perform engine control, memory control, system control, and the like separately, wasteful duplication processing has occurred.

For this reason, in Patent Document 1, the applications such as engine control, memory control, and system control, which have been performed by a plurality of applications installed in the multifunction peripheral, are grouped from each application as a common processing part (platform). The development efficiency is improved.
JP 2002-084383 A

  However, the invention disclosed in Patent Document 1 shares a processing part for controlling hardware, and does not share all internal processes of each application. For this reason, there is still room for improvement in the application on the multifunction peripheral in order to improve the development efficiency.

  For example, in the application management process that manages the operation settings of each application such as a printer application and a copy application, it is necessary to perform the setting process for each application after performing processing such as acquiring the usage rights of the setting screen and changing the power state . These processes are common to each application installed in the MFP, but are not directly controlled by the hardware, so they are implemented separately for each application and can be shared. It is.

  Also, in recent multifunction devices, it is possible to perform setting processing of each application from a terminal device via a network. When performing setting processing by directly operating the multifunction device, setting processing via a network is possible. In many cases, the item to be set is changed. Furthermore, the users who perform the setting process include general users and maintenance personnel (service persons), and it is necessary to change items to be set for each of these users.

  For these reasons, it has become a major issue how to implement application management processing of applications installed in multifunction peripherals in a versatile and efficient manner. Such a problem does not occur only for the multifunction peripheral, but also occurs for an application management apparatus that performs application management processing.

  The present invention has been made to solve the above-described problems caused by the prior art, and can easily add or modify functions, and can efficiently realize a general-purpose application management mechanism. An object is to provide a device and application management program.

  Therefore, in order to solve the above-described problem, the present invention provides a device status management device that can execute a plurality of applications, and determines whether the application can be used based on the status of the device in response to an execution request of the application. An application configuration management unit that manages the configuration of the application, and an application status management unit that manages status information that is a factor for determining whether or not the application can be used for each application. Has application management means for determining whether or not the application can be used based on the state of each application, and manages the configuration of the application having a plurality of functions by the hierarchical structure of the application management means. And

  In such a device, functions can be easily added and modified, and a general-purpose application management mechanism can be efficiently realized.

  Moreover, in order to solve the said subject, this invention is good also as an application management program for functioning the said apparatus as said each means.

  According to the present invention, it is possible to provide a device and an application management program that can easily add or modify functions and can efficiently realize a general-purpose application management mechanism.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the present embodiment, the case where the present invention is applied to an image forming apparatus will be described. However, the present invention is not limited to this, and can be applied to various apparatuses that perform application management.

  First, an outline of an image forming apparatus (hereinafter referred to as “multifunction machine”) 1 according to the present embodiment will be described with reference to FIGS. 1, 2, 3, 9, and 10. FIG. 1 is a network diagram for explaining a network environment surrounding the MFP 1 according to the present embodiment, and FIG. 2 is a block diagram showing a hardware configuration of the MFP 1 shown in FIG. FIG. 3 is an explanatory diagram for explaining a relationship between software and hardware of the multifunction machine 1 shown in FIG. FIG. 9 is an explanatory diagram for explaining the transition of the software configuration installed in the multifunction device 1, and FIG. 10 is an explanatory diagram for explaining the relationship between software and hardware of a conventional multifunction device. is there.

  As shown in FIG. 1, with the recent progress of networking, devices such as personal computers (PCs) provided in offices are connected to a network such as a LAN (Local Area Network) and can communicate with each other. It became normal. For example, as shown in the figure, a client PC, an SMTP (Simple Mail Transfer Protocol) server, an FTP (File Transfer Protocol) server, a server PC, etc. are connected to such a network to send and receive e-mails and transfer files. The modem-connected delivery server can communicate with a fax machine outside the office.

  With the progress of such networking, the multifunction device 1 is also connected to the network and can communicate with a device such as a PC. By incorporating a storage device such as a hard disk, a so-called network multifunction device is achieved. It has evolved to meet the various needs of users.

  For example, in addition to the normal copy function, the multifunction device 1 includes a printer function for printing document data or the like in response to a print request from the client PC, and a modem connected to the server PC for document data or the like in response to a fax request from the client PC. It has a fax function that sends it to fax machines in other offices via the Internet, and a storage function that stores received fax documents and copy documents on a built-in hard disk.

  In this way, in order to realize many functions required by the progress of compounding and networking, the software installed in the compound machine 1 is large and complicated. Along with this, the man-hours for developing and maintaining such software have also increased significantly.

  FIG. 2 is a block diagram illustrating a hardware configuration of the multifunction machine 1. As shown in the figure, the multifunction machine 1 has a configuration in which a controller 10 and an engine unit (Engine) 60 are connected by a PCI (Peripheral Component Interconnect) bus. The controller 10 is a controller that controls the entire multifunction device 1 and controls drawing, communication, and input from an operation unit (not shown). The engine unit 60 is a printer engine that can be connected to a PCI bus, and is, for example, a monochrome plotter, a one-drum color plotter, a four-drum color plotter, a scanner, or a fax unit. The engine unit 60 includes an image processing part such as error diffusion and gamma conversion in addition to a so-called engine part such as a plotter.

  The controller 10 includes a CPU 11, a north bridge (NB) 13, a system memory (MEM-P) 12, a south bridge (SB) 14, a local memory (MEM-C) 17, and an ASIC (Application Specific Integrated Circuit). 16 and a hard disk drive (HDD) 18, and the north bridge (NB) 13 and the ASIC 16 are connected by an AGP (Accelerated Graphics Port) bus 15. The MEM-P 12 further includes a ROM (Read Only Memory) 12a and a RAM (Random Access Memory) 12b.

  The CPU 11 performs overall control of the multifunction machine 1 and includes a chip set including the NB 13, the MEM-P 12, and the SB 14, and is connected to other devices via the chip set.

  The NB 13 is a bridge for connecting the CPU 11 to the MEM-P 12, SB 14, and AGP 15, and includes a memory controller that controls reading and writing to the MEM-P 12, a PCI master, and an AGP target.

  The MEM-P 12 is a system memory used as a memory for storing programs and data, a memory for developing programs and data, a memory for drawing a printer, and the like, and includes a ROM 12a and a RAM 12b. The ROM 12a is a read-only memory used as a memory for storing programs and data, and the RAM 12b is a writable and readable memory used as a program / data development memory, a printer drawing memory, and the like.

  The SB 14 is a bridge for connecting the NB 13 to a PCI device and peripheral devices. The SB 14 is connected to the NB 13 via a PCI bus, and a network interface (I / F) unit and the like are also connected to the PCI bus.

  The ASIC 16 is an IC (Integrated Circuit) for image processing applications having hardware elements for image processing, and has a role of a bridge for connecting the AGP 15, PCI bus, HDD 18 and MEM-C 17. The ASIC 16 includes a PCI target and an AGP master, an arbiter (ARB) that is the core of the ASIC 16, a memory controller that controls the MEM-C 17, and a plurality of DMACs (Direct Memory) that perform rotation of image data by hardware logic. Access Controller) and a PCI unit that performs data transfer between the engine unit 60 via the PCI bus. An FCU (Fax Control Unit) 30, a USB (Universal Serial Bus) 40, and an IEEE 1394 (the Institute of Electrical and Electronics Engineers 1394) interface 50 are connected to the ASIC 16 via a PCI bus.

  The MEM-C 17 is a local memory used as an image buffer for copying and a code buffer, and an HDD (Hard Disk Drive) 18 is a storage for storing image data, programs, font data, and forms. It is.

  The AGP 15 is a bus interface for a graphics accelerator card proposed for speeding up graphics processing. The AGP 15 speeds up the graphics accelerator card by directly accessing the MEM-P 12 with high throughput. .

  FIG. 3 is a conceptual diagram showing the hardware and software configurations of the multifunction machine 1, and specifically, an integrated application 110 including an application management unit 111b, which is a characteristic part of the present embodiment to be described later, A hierarchical relationship between the software 100 and the hardware 200 is shown. As shown in the figure, the hardware 200 includes a hardware resource 201. The hardware resource 201 includes a scanner 201a, a plotter 201b, an HDD (Hard Disk Drive) 201c, a network 201d, and other resources 201e. . The other resource 201e is a hardware resource 201 other than 201a to 201d, and indicates an input / output device such as an operation panel, for example.

  The software 100 installed in the hardware 200 is hierarchized, and a service layer 102 is constructed above the operating system 103, and an application layer 103 is constructed above the service layer 102. The service layer 102 corresponds to a driver that controls each hardware resource (201a to 201e). The scanner control unit 102a, plotter control unit 102b, storage control unit 102c, distribution / mail transmission / reception control unit 102d, FAX transmission / reception It has a control unit 102e, a network communication control unit 102f, and another control unit 102g.

  Here, how the software 100 shown in FIG. 3 has taken such a hierarchical structure will be described with reference to FIGS. 9 and 10. FIG. FIG. 9 is an explanatory diagram showing the transition of the software configuration installed in the multifunction machine 1. As shown in the pre-service layer separation application 501 in FIG. 9, the software installed in the multifunctional multifunction device 1 is created as an independent application for each function such as a copy application, a FAX application, and a scanner application. It was operating on the operating system 103 shown.

  However, since these applications include a driver (service layer 102) that controls hardware resources, duplicate processing exists in each application. As a result, the scale of each application has become large.

  Therefore, as shown in the post-service layer separation application 502 in FIG. 9, the portion corresponding to the service layer 102 of the pre-service layer separation application 501 is defined as the service layer 102, and each application is an upper layer of the service layer 102. The application layer 101 is constructed. By adopting such a hierarchical structure, each application has been streamlined and development effort has been reduced.

  However, as the networking and multi-functionalization of the multifunction machine 1 further advance, it has become a problem that a common processing part exists in each application. Specifically, each application in the application layer 101, for example, a copy application or a scanner application, internally has similar processing such as processing for communicating with a driver such as the scanner control unit 102a or the accumulation control unit 102c. It was. As described above, when each application has the same processing, the development scale of each application is increased, and the improvement scale of each application with respect to the specification change of the service layer is increased.

  In order to solve this problem, as shown in the common routine separation application 503 in FIG. 9, it has been considered that such a similar process (common processing part) is bundled as a common routine. However, since such a common routine is intended to share slightly different processing in each application, the processing inside the common routine becomes complicated. For example, when adding a new application such as a printer application, it is necessary to modify the common routine in order to adapt to the new application.

  However, since the internal processing of the common routine is complicated, it became difficult for repair personnel to grasp the processing, and there were concerns about the increase in the scale of repair and the impact on other applications due to repair mistakes.

  Therefore, as shown in the object-oriented application 504 in FIG. 9, the plurality of applications are integrated into the integrated application 110 by an object-oriented design method (object modeling). Specifically, a common processing part of each application is extracted as an object model, and the integrated application 110 is configured from the collection of object models. The functions such as the conventional copy function and scanner function are realized by the cooperative relationship of the object model.

  By adopting such a configuration, for example, addition of a new function such as a printer function can be dealt with by subclassing a class belonging to the object model. For this reason, a repair part becomes clear and the influence on other functions by repair can be made small. In addition, the object modeling program is easier to grasp the process than the conventional procedural program, so it is easier for the repair staff to grasp the process, reducing the scale of the repair, and other applications due to mistakes in the repair. The influence on can be reduced.

  FIG. 10 is an explanatory diagram showing the configuration of a conventional application at the stage of the service layer separated application 502 shown in FIG. 9 and the relationship between the application and each driver of the service layer 102. As shown in the figure, the application layer 101 includes a copy application 120, a scanner application 130, a fax application 140, and a printer application 150.

  For example, the copy application 120 transmits / receives data to / from the scanner control unit 102a, the plotter control unit 102b, the accumulation control unit 102c, and the other control unit 102g in order to realize a copy function. In addition, the fax application 140 performs data transmission / reception with the plotter control unit 102b, the accumulation control unit 102c, the FAX transmission / reception control unit 102e, the network communication control unit 102f, and the other control unit 102g in order to realize the fax function. As described above, communication between each application in the application layer 101 and each driver in the service layer 102 is complicated.

  Returning to the description of FIG. 3, a plurality of applications existing in the application layer 101 are integrated into the integrated application 110 by the object modeling described above. The communication processing with each driver, which has been performed by each application overlappingly, is configured to be performed by a predetermined object model that configures the integrated application 110, so that the application of the application layer 101 and the service layer 102 of Communication between the drivers is simpler than that shown in FIG.

  Next, the internal configuration of the integrated application 110 will be described. FIG. 4 is a block diagram showing the internal configuration of the integrated application 110. As shown in the figure, the integrated application 110 has an operation subsystem 111, a management subsystem 112, and an execution subsystem 113.

  The operation subsystem 111 is a software group in charge of man-machine interface and application management. Specifically, the operation subsystem 111 performs a process for accepting a user request, a process for instructing execution of the request, and a process for providing the user with information about the execution status and execution result of the request. .

  The management subsystem 112 is a software group that manages the resources of the multifunction machine 1. Specifically, the management subsystem 112 performs a service for managing the hardware resource 201 and the data state held by the hardware resource 201.

  The execution subsystem 113 is a software group in charge of executing a request from a user. Specifically, the execution subsystem 113 performs processing from reading a document to outputting a product when a copy request is made.

  The operation system subsystem 111, the management system subsystem 112, and the execution system subsystem 113 mutually request processing as necessary and send the results. In this way, the subsystems cooperate to provide services required for the multifunction device 1 as the integrated application 110 as a whole.

  The operation subsystem 111 further includes an operation control unit 111a in charge of a man-machine interface and an application management unit 111b that is a characteristic part of the present embodiment. The application management unit 111b is a processing unit that manages a state for determining the behavior of an application to be managed, and determines whether or not to shift the state and performs a process associated with the transition.

  FIG. 5 is a diagram in which each subsystem shown in FIG. 4 is replaced with a UML (Unified Modeling Language) class diagram (UML class diagram). Here, UML is a system modeling language for which specifications are formulated by OMG (Object Management Group), and defines a notation for describing the results of modeling. This UML is widely used in the design of object-oriented software.

  As shown in FIG. 5, the integrated application 110 has a plurality of packages, and the integrated application 110 itself is one package. Here, the package is a group of components (symbols) of the UML model, and is expressed by a symbol in the form of a folder with a tab on the upper left. A straight line connecting the packages indicates that there is a relationship such as a processing request between the packages.

  As shown in FIG. 5, the integrated application 110 is a package having three packages of an operation subsystem 111, a management subsystem 112, and an execution subsystem 113 inside. Furthermore, the operation system subsystem 111 is a package that includes an operation control unit 111a and an application management unit 111b that is a characteristic part of the present embodiment.

  A straight line connecting the operation subsystem 111, the management subsystem 112, and the execution subsystem 113 indicates that there is a relationship such as a processing request (for example, message transmission / reception) between the packages. A symbol written at the right end of the tabs of the operation subsystem 111, the management subsystem 112, and the execution subsystem 113 is a UML symbol indicating that the package is a subsystem.

  Next, the application management unit 111b, which is a characteristic part of the present embodiment, will be described in detail. In addition, when designing based on object orientation, the application management unit 111b configures an object model so that existing processing is not simply converted into an object and functions can be added or modified more easily.

  FIG. 6 is a UML class diagram showing a class configuration of the application management unit 111b.

  First, the class description method in the class and UML class diagram will be described. A class is a concept that corresponds to a blueprint for the objects that make up an object-oriented system. It defines the attributes and processing that an object has and defines relationships with other classes, such as inheritance and aggregation relationships. It is.

  The class in the UML class diagram is described as a rectangle having three sections. From the top, each section is called a name section indicating a class name, an attribute section indicating data (attribute) included in the class, and an operation section indicating processing (operation) included in the class. For example, a rectangular name block indicating the device class 311 indicates that the class name of the class is “device”, and an attribute block indicates that the attribute of the class is “operating state”. The section indicates that the operation of the class is “setting start ()”.

  In this way, each class has an attribute section for holding data (attribute) and an operation section for holding processing (operation) for writing and reading such an attribute. Since these classes are included as a part of the program (integrated application 110), when this program stored in the ROM 12a in advance is executed, each class is materialized in a predetermined area of the RAM 12b and included in the attribute section. Each data (attribute) is expanded on the RAM 12b. Therefore, the object in which the class is materialized can write and read each data (attribute) on the RAM 12b.

  In addition, if a "-" symbol is attached to the left side of a class element such as attribute or operation, this indicates that the element is private to external classes, and if a "+" symbol is attached, this element Indicates that it is open to external classes. Also, for operations, it is customary to add a “()” symbol, such as “setting start ()”, and when describing an argument to be passed to the operation, such as “(argument 1, argument 2)” There is also.

  Next, an outline of the class of the application management unit 111b, which is a characteristic part of the present embodiment, will be described. As shown in FIG. 6, the application management unit 111 b is roughly divided into a device state management unit 310, an application configuration management unit 320, and an application state management unit 330.

  The device status management unit 310 manages status information that affects the entire MFP 1, and includes a device class 311 and an energy saving class 312. The application configuration management unit 320 mainly manages the configuration of the application, and includes an application class 321, a single application class 322, and a composite application class 323. The application state management unit 330 manages the state of each application, and includes a setting information class 331, an SP (Service Program) setting information class 332, an UP (User Program) setting information class 333, and a screen class 334. Each of these classes will be described below.

  The device class 311 is a class in which one instance corresponds to one device (multifunction device 1), manages the state related to the use restriction of the multifunction device 1, and arbitrates between the power state and the application state. The device class 311 has a state 311a as an attribute and an application usage () 312b as an operation.

  The state 311a holds a use restriction state for the multifunction device 1 such as whether the multifunction device 1 provides a function or whether some kind of use restriction is imposed on the multifunction device 1.

  The application usage () 312b is an operation for accepting an application usage request, and determines whether or not the MFP 1 can be used at an overall level of granularity in response to a call. Execute the process. For example, the power state or the like in the multifunction device 1 is a material for determining availability.

  The energy saving class 312 is a class that knows the current power state of the device and performs switchability determination and switching processing in response to the power state switching request. The energy saving class 312 has a state 312a as an attribute and a release () 312b as an operation.

  The state 312a holds the current power state of the multifunction device 1. The power state includes, for example, a plurality of stages such as a normal standby state and a power saving state, and the power supply state is different in each stage. The normal standby state refers to a state in which the multifunction device 1 is on standby in a state where service can be provided. The power saving state refers to a state where power supply to a predetermined location is stopped or suppressed in order to reduce power consumption. For example, in this power saving state, the operation panel is hidden. Note that a plurality of stages may be further provided in this power saving state.

  Cancel () 312 b is called from the device object 311 A that materializes the device class 311, and performs processing to cancel the power saving state and return to the normal standby state.

  The application class 321 is a class that manages the operation restriction state of each application and performs processing such as determining whether or not the application can be used when an application use request is made. The application class 321 has a state 321a and a type 321b as attributes, and a use () 321c as an operation.

  The state 321a holds an operation restriction state indicating whether or not there is a restriction on an operation that can be provided by the application. When the value of the state 321a is “none”, this indicates a state in which the application provides a function without degenerating the function. On the other hand, when the value of the state 321a is “present”, it indicates a state in which the application provides the function by degenerating the function. The operation restriction state changes depending on factors such as setting of setting information.

  The type 321b holds information for identifying the type of each application. For example, values such as “copy application”, “transmission application”, “printer application”, or “composite application” are stored.

  The use () 321 c executes the requested function using the function currently provided by the application. Since it is necessary to use a screen (operation panel) and setting information in order to execute the function, message exchange between the screen class 334 and the setting information class 331 occurs when the function is executed.

  The single application class 322 is a subclass of the application class 321 and corresponds to an application having a single function (hereinafter referred to as “single application”).

  The composite application class 323 is a subclass of the application class 321 and corresponds to an application in which a plurality of functions are combined (for example, an application such as the integrated application 110 described above, hereinafter referred to as “composite application”).

  The setting information class 331 represents setting information required for the operation of the application, and manages the current usage state of the setting information. The setting information class 331 has a state 331a and a reference number 331b as attributes, and a reference () 331c as an operation.

  The state 331a holds an editing state of the setting information such as whether the setting information is currently referenced or edited.

  The reference number 331b holds the number of users currently referring to the setting information.

  The reference () 331 c performs processing necessary for referring to the setting information of the application.

  The SP setting information class 332 is a subclass of the setting information class 331, and manages setting information specialized for a service person.

  The UP setting information class 333 is a subclass of the setting information class 331, and manages setting information specialized for general users.

  The screen class 334 manages the holding state of the right (operation unit usage right) for exclusive use of the operation panel for the application to communicate with the user, and responds to a request for switching the holding state of the operation unit usage right. This class performs switchability determination and switching processing. The screen class 334 has a state 334a as an attribute and an acquisition () 334b as an operation.

  The state 334a holds the usage right state indicating whether or not the operation unit usage right is acquired. The usage right status “Yes” indicates that the operation unit usage right has been acquired, and the usage right status “No” indicates that the operation unit usage right is acquired without the need to acquire the operation unit usage right. It represents a state that is not. That is, when a user operates the multifunction device 1 to use an arbitrary function, an application that provides the function needs to acquire an operation unit usage right. Since the multifunction device 1 according to the present embodiment is equipped with one operation panel, two or more applications cannot acquire the operation unit usage right at the same time.

  The acquisition () 334 b performs a process for acquiring the operation unit usage right when the operation unit usage right is not acquired.

  Next, the relationship between the classes shown in FIG. 6 will be described. As shown in the figure, in the UML class diagram, when there is some relationship between classes, rectangles representing those classes are connected by a straight line. The numbers near the ends of this line represent the multiplicity of the class. Multiplicity is the number of objects generated in association with the other class of objects connected by a straight line.

  For example, in the relationship between the device class 311 and the energy saving class 312 in the figure, the multiplicity of the device class 311 is “1”, and the multiplicity of the energy saving class 312 is “1”. This means that the device object 311A that is an instance of the device class 311 and the energy saving object 312A that is an instance of the energy saving class 312 are associated one-to-one.

  First, the class relationship between the device class 311 and the energy saving class 312 will be described. Since the energy saving class 312 is a class for managing the power state of the multifunction device 1, there is only one in the multifunction device 1. Further, as described above, only one device class 311 exists in the multifunction device 1. Therefore, one device object 311A aggregates one energy saving object 312A.

  Next, the class relationship between the device class 311 and the application class 321 will be described. The application class 321 has a one-to-one correspondence with each application in the multifunction device 1. Further, only one instance of the device class 311 (device object 311A) exists in the multi-function peripheral 1, and all instances of the application class 321 (application object 321A) are managed. Accordingly, one device object 311A aggregates 0 to n application objects 321A.

  By the way, since the application class 321 is an abstract class, strictly speaking, an instance of the application class 321 is not generated. Therefore, in the present embodiment, “instance of application class 321” or “application object 321A” refers to an instance of a subclass of application class 321 (single application class 322 or composite application class 323).

  Next, the class relationship between the application class 321 and the screen class 334 will be described. Each application can acquire only one operation unit usage right. Therefore, one application object 321A aggregates one screen object 334A.

  Next, the class relationship between the application class 321 and the setting information class 331 will be described. One application requires zero or more setting information. Therefore, one application object 321A aggregates 0 to n setting information objects 331A.

  By the way, since the setting information class 331 is an abstract class, strictly speaking, an instance of the setting information class 331 is not generated. Therefore, in the present embodiment, when “instance of setting information class 331” or “setting information object 331A” is referred to, it is an instance of a subclass (SP setting information class 332 or UP setting information class 333) of setting information class 331. Say.

  Since the single application class 322 and the composite application class 323 are subclasses of the application class 321, the properties (attributes, operations, associations, etc.) of the application class 321 are inherited. Further, the SP setting information class 332 and the UP setting information class 333 are subclasses of the setting information class 331, and therefore inherit the properties of the setting information class 331.

  By the way, the composite application class 323 not only inherits the application class 321 but also aggregates the application classes 321 by the association r1. According to the multiplicity of the association r1, one composite application object 323A aggregates two or more and n or less application objects 321. The hierarchical structure of the composite application is expressed by this relation r1. As used herein, the hierarchical structure refers to a hierarchical structure configured when applications are classified according to their functional aspects.

  FIG. 7 is a diagram for explaining an example of a hierarchical structure of applications in the multifunction peripheral. FIG. 7 shows that two applications, an integrated application and a printer application, are installed when viewed from the multifunction machine 1. Here, since the integrated application is a composite application, it includes two or more applications. In the figure, the copy application and the transmission application are included in the integrated application. Furthermore, since the transmission application is a composite application, it includes a normal transmission application and a remote transmission application.

  When the hierarchical structure of FIG. 7 is applied to the class diagram of FIG. 6, the integrated application is instantiated as a composite application object 323A. The composite application object 323A aggregates a single application object 322A corresponding to the copy application and a composite application object 323A corresponding to the transmission application. Furthermore, the composite application object 323A corresponding to the transmission application aggregates two single application objects 322 corresponding to the normal transmission application and the remote transmission application, respectively.

  As described above, the class structure in the application configuration management unit 320 can appropriately represent the hierarchical structure of the application in the multi-function device 1 by the association of objects.

  Next, an example of the execution procedure of each class operation shown in FIG. 6 will be described. FIG. 8 is a UML sequence diagram for explaining an example of a processing procedure when the application management unit receives an application use request.

  Here, the UML sequence diagram will be described. Each rectangle arranged in the upper part of FIG. 8 represents an instance (object) of a class. A line extending downward from each object is a line (lifeline) indicating that each object is alive, and time is considered to flow from the top to the bottom. An elongated rectangle present on this line indicates a period during which the object is actually active (active period). And the horizontal arrow which connects between each lifeline shows execution of operation contained in an object. Specifically, this arrow indicates that the original object of the arrow calls an operation included in the object at the end of the arrow.

  The device object 311A receives a user application use request by calling the application use () 312b from the operation control unit 111a of the operation subsystem 111 (S101). The device object 311A knows that in order to start using the application, the multifunction device 1 is not in use restriction, and the power state of the multifunction device 1 must be changed. Accordingly, it is determined whether or not the application can be used as the granularity of the entire multifunction device 1.

  First, the device object 311A refers to the state 311a to determine whether or not the multifunction device 1 is currently restricted in use. If the usage is not restricted, the device object 311A requests the energy saving object 312A to cancel the power saving state by calling the energy saving object 312A cancellation () 312b (S102).

  The energy saving object 312A refers to the state 312a. If the energy saving object 312A is in the power saving state, the energy saving object 312A performs a return process to the normal standby state, and returns to the device object 311A whether the normal standby state has been restored. When the normal standby state can be restored, the energy saving object 312A changes the value of the state 312a to the normal standby state.

  When the multifunction device 1 is not being restricted in use and the power state is in the normal standby state, the device object 311A determines that the application is available at the level of the multifunction device 1, and the application corresponding to the application requested to be used. Use of the object 321A () 321c is called (S103).

  When the application object 321A for which the usage () 321c is called is an instance of the composite application class 323, the application object 321A calls the usage 321c of the application object 321A aggregated by itself (S104). Therefore, the following processing implemented in the usage () 321 c is executed hierarchically according to the hierarchical structure of the application.

  In the usage () 321 c, the application object 321 </ b> A executes usage availability determination processing at the application level.

  First, the application object 321A refers to its state 321a and determines whether or not the operation is currently restricted. If the operation is not limited, the application object 321A calls the acquisition () 334b of the screen object 334A that the application object 321A has and requests acquisition of the operation unit use right (S105).

  The screen object 334A refers to its own state 334a and confirms whether or not the operation unit usage right is present. When there is no operation unit usage right, the screen object 334A executes processing for acquiring the operation unit usage right, and returns success or failure of acquisition to the application object 321A.

  Subsequently, the application object 321A requests the reference of the setting information for the application by calling the reference () 331c of the setting information object 331A (S106). The setting information object 331A refers to its own state 331a. If the setting information object 331A is not being edited, the setting information object 331A performs a process for referring to the setting information, and returns the success or failure to the application object 321A.

  The application object 321A determines whether or not the application can be used based on its own state 321a, success or failure of acquisition of the operation unit usage right, and reference or failure of reference to the setting information, and uses the application according to the determination result. Execute the process to make it.

  As described above, in the MFP 1 according to the present embodiment, applications are managed by a model based on an object-oriented design that can classify applications hierarchically based on their functions and appropriately express such hierarchical classification. Part 111b is mounted. Therefore, it is possible to flexibly cope with various application configurations, and a general-purpose application management mechanism can be efficiently realized.

  Therefore, maintenance for addition / deletion of application functions can be easily performed, and reduction of man-hours such as development work and maintenance work can be expected.

  The program executed by the multifunction machine 1 of the present embodiment is a file in an installable format or an executable format, and is a CD-ROM (Compact Disc Read Only Memory), a flexible disk (FD), a CD-R ( You may comprise so that it may record and provide on computer-readable recording media, such as CD Recordable (DVD Record) and DVD (Digital Versatile Disk). In this case, the CPU 11 reads the program from the storage medium and loads it on the MEM-P 12 to cause the multifunction device to realize each step, each unit, or each unit described above.

  Further, the program may be provided by being stored on a computer connected to a network such as the Internet and downloaded via the network. Furthermore, the program may be provided or distributed via a network such as the Internet.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to the specific embodiment which concerns, In the range of the summary of this invention described in the claim, various deformation | transformation * It can be changed.

1 is a network diagram showing a network environment surrounding a multifunction peripheral. FIG. 3 is an explanatory diagram for explaining hardware of a multifunction peripheral. FIG. 3 is an explanatory diagram for explaining a hierarchical structure of hardware and software in a multifunction peripheral. It is explanatory drawing for demonstrating the structure of an integrated application. It is a UML class diagram showing the configuration of an integrated application. It is a UML class diagram which shows the class structure of an application management part. FIG. 3 is a diagram for explaining an example of a hierarchical structure of applications in a multifunction peripheral. It is a UML sequence diagram for demonstrating an example of the process sequence when an application management part receives the utilization request of an application. FIG. 6 is an explanatory diagram illustrating a transition of a software configuration installed in a multifunction peripheral. It is explanatory drawing for demonstrating the hierarchical structure of the hardware and software in the conventional multifunction machine.

Explanation of symbols

1 Image forming device (multifunction machine)
10 Controller 11 CPU
12 MEM-P
12a ROM
12b RAM
13 NB
14 SB
15 AGP
16 ASIC
17 MEM-C
18 HDD
20 Keyboard (Operation panel)
30 FCU
40 USB
50 IEEE1394
60 Engine
DESCRIPTION OF SYMBOLS 100 Software 101 Application layer 102 Service layer 102a Scanner control part 102b Plotter control part 102c Accumulation control part 102d Delivery / mail transmission / reception control part 102e FAX transmission / reception control part 102f Network communication control part 102g Other control part 103 Operating system 110 Integrated application 111 Operation System Subsystem 111a Operation Control Unit 111b Application Management Unit 112 Management System Subsystem 113 Execution Subsystem 120 Copy Application 130 Scanner Application 140 Fax Application 150 Printer Application 200 Hardware 201 Hardware Resource 201a Scanner 201b Plotter 201c HDD
201d network 201e other resources 310 device state management unit 311 device class 311A device object 311a state 311b application use ()
312 Energy saving class 312A Energy saving object 312a State 312b Canceled ()
320 Application configuration management unit 321 Application class 321A Application object 321a Status 321b Type 321c Use ()
322 single application class 322A single application object 323 composite application class 323A composite application object 330 application state management unit 331 setting information class 331A setting information object 331a state 331b reference number 331c reference ()
332 SP setting information 333 UP setting information 334 Screen class 334A Screen object 334a Status 334b Acquisition ()

Claims (8)

A device that can execute multiple applications,
Device status management means for determining whether or not to use the application based on the status of the device in response to the execution request of the application;
Application configuration management means for managing the configuration of the application;
Application status management means for managing status information that is a factor for determining whether or not the application can be used for each application;
The application configuration management unit includes an application management unit that determines whether or not the application can be used based on a state of each application, and the configuration of the application having a plurality of functions is determined by a hierarchical structure of the application management unit. Equipment characterized by management. The application configuration management means includes the application management means corresponding to a single application having a single function, and the application management means corresponding to a composite application having a plurality of functions.
2. The apparatus according to claim 1, wherein the application management means corresponding to the composite application is associated with another single application or two or more application management means corresponding to the composite application. The device state management means includes
Usage status management means for managing status related to usage restrictions of the device;
Power state management means for managing the power state of the device,
The device according to claim 1, wherein whether to use the application is determined based on a state related to the use restriction and the power state. The application state management means
Operation unit use right management means for managing whether the application has a right to use the operation panel of the device;
4. The device according to claim 1, further comprising setting information management means for managing an editing state of setting information for the application. A device that can run multiple applications
Device status management means for determining whether or not to use the application based on the status of the device in response to the execution request of the application;
Application configuration management means for managing the configuration of the application;
An application management program for causing each application to function as application state management means for managing state information that is a factor in determining whether or not the application can be used.
The application configuration management unit includes an application management unit that determines whether or not the application can be used based on a state of each application, and the configuration of the application having a plurality of functions is determined by a hierarchical structure of the application management unit. An application management program characterized by management. The application configuration management means includes the application management means corresponding to a single application having a single function, and the application management means corresponding to a composite application having a plurality of functions.
6. The application management program according to claim 5, wherein the application management unit corresponding to the composite application is associated with another single application or two or more of the application management units corresponding to the composite application. The device state management means includes
Usage status management means for managing status related to usage restrictions of the device;
Power state management means for managing the power state of the device,
The application management program according to claim 5 or 6, wherein the application management program determines whether or not the application can be used based on the state related to the use restriction and the power state. The application state management means
Operation unit use right management means for managing whether the application has a right to use the operation panel of the device;
8. The application management program according to claim 5, further comprising setting information management means for managing an editing state of setting information for the application.

Images