JP4490852B2 - Document processing apparatus, image forming apparatus, and document processing program - Google Patents

Description

  The present invention relates to a document processing apparatus, an image forming apparatus, and a document processing program that share document processing, and relates to a technique for setting input / output in response to a user request.

  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 (R), and a plurality of functions are realized while switching execution processes of these applications. .

  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 bundled from each application as a common processing part (platform). The development efficiency is improved.

  In Patent Document 2, print control software installed in a printing apparatus is composed of a plurality of software components based on object-oriented design, and printing processing is performed by cooperative operation of such component groups.

JP 2002-084383 A Japanese Patent Laid-Open No. 11-327883

  However, the invention disclosed in Patent Document 1 shares the processing part that controls the hardware, and does not share the overall internal processing of each application. Since internal processing is not divided into classes according to functions, there is a problem that the development efficiency of internal processing in general is not good. In other words, in order to improve development efficiency, applications on the multifunction peripheral have room for improvement by sharing the internal processing and dividing the characteristic functions into classes.

  For example, when a user inputs a document input from a plurality of input sources such as a fax machine or a scanner from a printer, a local storage, or a fax machine, the input is made by a job included for each application such as a copy or a fax machine. From processing to output, processing is performed with different jobs for each application, and processing for input documents has not been shared.

  The invention disclosed in Patent Document 2 is a print control software composed of a plurality of software parts based on object-oriented design, and the flow of processing that is common until the input document is output. It does not disclose software components to be controlled. Therefore, in a multi-function machine having a plurality of input sources and output destinations due to the multi-function, a software component corresponding to processing until the input document is output by applying the invention disclosed in Patent Document 2 Even if it is created, conventionally, since the user has performed processing with jobs for different applications according to the requested processing, it is not easy to efficiently control processing by sharing processing across all applications.

  For these reasons, a major issue is how to efficiently realize common processing of documents by absorbing the difference between the input source and the output destination in the application installed in the multifunction peripheral. Note that such a problem does not arise only for the multifunction peripheral. For example, after having a plurality of input means and performing a processing such as “2 in 1” on a document input from the input source, The same problem occurs when outputting from one or a plurality of output destinations.

  Furthermore, if the concept of application is abolished and processing is standardized, document processing is performed simply by setting a plurality of input sources and output destinations. In this case, there is a problem that a user who is familiar with the conventional method can think about anything wrong.

  The present invention has been made in order to solve the above-described problems caused by the prior art, absorbs the difference between the input source and the output destination, shares the document processing, and further performs the document processing for the user. An object of the present invention is to provide a document processing apparatus, an image forming apparatus, and a document processing program that can provide an interface that can be easily set.

In order to solve the above-described problems and achieve the object, the invention according to claim 1 controls in a document processing apparatus including a plurality of input means for inputting document information and a plurality of output means for outputting document information. associated with each of the input means to be a plurality generates document information converted into a predetermined format, an input document means making it possible to manage the input by the input document means manages For document information, an input page means for managing information for each page, an input layout means for generating and managing input frame information for determining the layout of the page for each page managed by the input page means, and the input page For each page managed by the means, the input image applied to the page is input-processed according to the input frame information managed by the input layout means. A user image for each area that can form one page is obtained from the input image unit that can be generated from the input document and can manage a plurality of the input images, and the input image managed by the input image unit. The user image means capable of managing a plurality of acquired user images and the output means to be controlled are associated with each other, and output processing is performed based on the user images managed by the user image means. Controls output document means capable of generating and managing a plurality of document information , request information indicating a document processing request received from a user, and the input document means associated with each input means And managing the input document control information indicating whether or not to control the output document control information indicating whether or not to control the output document means associated with each output means. RaKaname required When receiving a broadcast, it received該要 identifies the input document means and said output document means controlled from the determined information and the correspondence, generates and controls the input document means and said output document means identified And a user document means for performing the above.

  Further, the invention according to claim 2 includes the function of the input document means in the invention according to claim 1, including an input paper document means for performing input processing of a paper document, and a function of the input document means, An input electronic document means for input processing of an electronic document stored in a storage medium; and an input communication document means for inputting and processing the electronic document from a communication line, the function including the function of the input document means. Means for requesting document processing received from a user, input paper document control information indicating whether or not to control the input paper document means, and input electronic document control information indicating whether or not to control the input electronic document means And the input communication document control means indicating whether or not to control the input communication document means, and when the user request information is received, the user request information and the correspondence From the input paper document means for controlling, and performing identify and control from any one or more of said input electronic document means and said input communication document means.

  According to a third aspect of the present invention, in the first or second aspect of the invention, the output document means includes the function of the output document means, and the output paper document means for performing output processing as a paper document, and the function of the output document means. Including: an output electronic document means for outputting an electronic document to a storage medium; and an output communication document means for outputting the electronic document to a communication line, including the function of the output document means, and the user document means Includes document processing request information received from a user, output paper document control information indicating whether or not to control the output paper document means, output electronic document control information indicating whether or not to control the output electronic document means, When managing the output communication document control information indicating whether to control the output communication document means in association with the user request information, the user request information and the correspondence From the output paper document means for controlling, and performing identify and control from any one or more of the output electronic document means and the output communication document means.

According to a fourth aspect of the present invention, in an image forming apparatus provided with a plurality of input means for inputting document information and output means for outputting document information, the image forming apparatus is associated with each input means to be controlled. plurality generates document information converted into a predetermined format, an input document means making it possible to manage, for the input document information in which the input document means manages, inputs for managing information for each page For each page managed by the page means, the input page means generates and manages input frame information that defines the layout of the page, and for each page managed by the input page means, the input layout means An input image to be applied to the page is generated from the input processed input document according to the input frame information managed by the It is possible to acquire user images for each area that can constitute one page from the number of input image means that can be managed and the input image managed by the input image means, and to manage a plurality of the acquired user images Generating and managing a plurality of pieces of document information that are associated with each user image unit and each output unit to be controlled and that are output based on the user image managed by the user image unit Output document means capable of enabling, request information indicating a document processing request received from a user, input document control information indicating whether or not to control the input document means associated with each input means, , and manages correspondence, and output document control information indicating whether to control the output document means associated with each of the output means, when receiving a user or RaKaname determined information, accepted該要 required Identifying the input document means and said output document means controlled from the broadcast and the association, with a, a user document means for generating to control the input document means and said output document means identified It is a feature.

The invention according to claim 5 is associated with each input means to be controlled in a document processing program comprising a plurality of input means for inputting document information and output means for outputting document information. plurality generates document information converted into a predetermined format, an input document means making it possible to manage, for the input document information in which the input document means manages, inputs for managing information for each page For each page managed by the page means, the input page means generates and manages input frame information that defines the layout of the page, and for each page managed by the input page means, the input layout means An input image applied to the page is generated from the input processed input document according to the input frame information managed by the A user image for each area that can constitute one page is acquired from an input image means capable of managing a plurality of images and the input image managed by the input image means, and a plurality of the acquired user images are acquired. A plurality of document information that is associated with each manageable user image means and each output means to be controlled and that is output based on the user image managed by the user image means is generated and managed. Output document means that can be performed , request information that indicates a request for document processing received from a user, and input document control that indicates whether or not to control the input document means associated with each input means If information and, and manages correspondence, and output document control information indicating whether to control the output document means associated with each of said output means, accepting the user or RaKaname determined information, Accepted Identifying the input document means and said output document means for controlling the request information and the said association, the user document means for generating to control the identified said input document means and said output document means, It is characterized by having.

According to the first aspect of the present invention, even when input processing is performed from different input means, it is possible to share a processing process for conversion into a predetermined format, document processing request information, input document means information, and output document. Since the means information is associated, the input document means and the output document means used for document processing can be specified from the correspondence relationship regardless of what kind of document processing request is received from the user. On the other hand, it is possible to provide an interface capable of easily setting document processing. Further, since the input document information can be processed for each input image divided by the input frame information for each input page, there is an effect that the processing process becomes easy.

  According to the invention according to claim 2, the input medium is provided with different input paper document means, input electronic document means, and communication input means for each input medium, and these are controlled according to the user's request so that the input medium This makes it possible to perform input processing suitable for the above.

  According to the invention of claim 3, output paper document means, output electronic document means, and communication output means that are different for each output medium are provided, and these are controlled according to the user's request, so that the output medium It is possible to perform output processing suitable for the above.

In addition, according to the invention of claim 4, even when input processing is performed from different input means, it is possible to share a processing process or the like for conversion into a predetermined format, document processing request information, input document means information, and Since the output document means information is associated, the input document means and the output document means used for document processing can be specified from the correspondence relationship regardless of what kind of document processing request is received from the user. It is possible to provide an interface capable of easily setting document processing for a person. Further, since the input document information can be processed for each input image divided by the input frame information for each input page, there is an effect that the processing process becomes easy.

According to the fifth aspect of the present invention, even when input processing is performed from different input means, the processing can be made common in order to convert to a predetermined format, and document processing request information, input document means information, and Since the output document means information is associated, the input document means and the output document means used for document processing can be specified from the correspondence relationship regardless of what kind of document processing request is received from the user. It is possible to provide an interface capable of easily setting document processing for a person. Further, since the input document information can be processed for each input image divided by the input frame information for each input page, there is an effect that the processing process becomes easy.

  Exemplary embodiments of a document processing apparatus, an image forming apparatus, and a document processing program according to the present invention are explained in detail below with reference to the accompanying drawings. In this 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 various apparatuses that perform processing on documents input / output from a plurality of input / output units. Can be applied to.

(First embodiment)
First, an outline of an image forming apparatus (hereinafter referred to as “multifunction machine”) 1 according to a first embodiment of the present invention will be described with reference to FIGS. 1, 2, 3, 4, 21, and 22. FIG. To do. 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 a conceptual diagram for explaining the relationship between software and hardware of the multi-function device 1 shown in FIG. FIG. 4 is a diagram illustrating an example of the operation panel 400 of the multifunction machine 1. FIG. 21 is an explanatory diagram for explaining the transition of the software configuration installed in the multifunction peripheral, and FIG. 22 is an explanatory diagram for explaining the relationship between software and hardware of the conventional multifunction peripheral.

  As shown in FIG. 1, devices such as a PC (Personal Computer) provided in an office or the like are connected to a network such as a LAN (Local Area Network) and can communicate with each other due to recent progress in networking. 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 such a 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 can be obtained. It has evolved to meet various user needs.

  Specifically, in addition to the normal copy function, the multi function device 1 is connected to the server PC by a printer function for printing document data and the like by a print request from the client PC, and by a fax request from the client PC. A fax function for transmitting to a fax machine in another office via a modem, and a storage function for storing a received fax document or a copy document in a built-in hard disk. In order to realize such many functions, the software installed in the conventional multi-function machine becomes large and complicated. Along with this, the man-hours for developing and maintaining such software have increased significantly. Therefore, the software installed in the multifunction machine 1 according to the present embodiment reduces the man-hours for development and maintenance. The configuration of software installed in the multifunction machine 1 will be described later.

  FIG. 2 is a block diagram illustrating a hardware configuration of the multifunction machine 1. As shown in the figure, the multi-function device 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 MFP 1 and controls drawing, communication, and input from the operation unit 20. 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 document data 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 program / data storage memory, and the RAM 12b is a writable / readable memory used as a program / data development memory, a printer drawing memory, or 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 image processing application IC (Integrated Circuit) having hardware elements for image processing, and has a role of a bridge for connecting the AGP 15, the PCI bus, the HDD 18, and the MEM-C 17. The ASIC 16 includes a PCI target and an AGP master, an arbiter (ARB) that forms the core of the ASIC 16, a memory controller that controls the MEM-C 17, a plurality of DMACs (Direct Memory) that perform rotation of image data by hardware logic and the like. Access Controller) and a PCI unit that transfers data 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 device 1, and specifically, an integrated application 110 including a document handling unit 212, which is a characteristic part of the present embodiment to be described later, A hierarchical relationship between the software 100 and the hardware 150 is shown. As shown in the figure, the hardware 150 includes a hardware resource 151, and the hardware resource 151 includes a scanner 151a, a plotter 151b, an HDD (Hard Disk Drive) 151c, a network 151d, and other resources 151e. . The other resources 151e are hardware resources 151 other than 151a to 151d, and indicate input / output devices such as an operation panel, for example.

  FIG. 4 is a diagram illustrating an example of the operation panel 400 of the multifunction machine 1. As shown in the figure, the operation panel 400 includes an initial setting key 401, a copy key 402, a copy server key 403, a printer key 404, a transmission key 405, a ten key 406, a clear / stop key 407, a start key 408, a preheat. A key 409, a reset key 410, a scanner key 411, and a liquid crystal touch panel 420; When the user performs a predetermined operation on the operation panel 400 having such a configuration, an object that materializes each class, which is a feature of the present embodiment, included in the integrated application 110 operates.

  For example, when the initial setting key 401 is touched, a menu for initial setting is displayed on the liquid crystal touch panel 420, and in this menu, a paper size to be stored and the like can be set. Further, when the user wants to make a copy, the copy key 402 is stored. When the copy result is stored in the multifunction device 1, the copy server key 403 is displayed. When the operation related to the printer is performed, the printer key 404 is displayed. When the user wants to transmit an image or the like, touch the transmission key 405 to display a menu corresponding to the liquid crystal touch panel 420.

  Returning to FIG. 3, the software 100 mounted on the hardware 150 is hierarchized, and a service layer 102 is constructed above the operating system 103, and an application layer 101 is constructed above the service layer 102. ing. The service layer 102 corresponds to a driver that controls each hardware resource (151a to 151e). The scanner control unit 102a, the plotter control unit 102b, the accumulation control unit 102c, the distribution / mail transmission / reception control unit 102d, and the FAX transmission / reception control. Unit 102e, network communication control unit 102f, and other 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. 21 and 22. FIG. 21 is an explanatory diagram showing changes in the software configuration installed in the multifunction peripheral. As shown in the pre-service layer separation application 1801 in FIG. 21, the software installed in the multifunctional multifunction peripheral is created as an independent application for each function such as a copy application, a FAX application, and a scanner application, and is shown in FIG. Operating on the operating system 103.

  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 an application 1802 after service layer separation in FIG. 21, the service layer 102 of the application 1801 before service layer separation is bundled into 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 multifunctional functions of multi-function peripherals have further progressed, it has become a problem that a common processing part exists in each application. Specifically, each application of the application layer 101, for example, a copy application or a scanner application, performs processing for communicating with a driver such as the scanner control unit 102a or the accumulation control unit 102c, and the flow of data handled by various functions. Similar processing such as stream control to be controlled was included inside. 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 1803 in FIG. 21, it is 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 an object-oriented application 1804 in FIG. 21, such a 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. 22 is an explanatory diagram showing the configuration of a conventional application at the stage of the service layer separated application 1802 shown in FIG. 21 and the relationship between the application and each driver of the service layer 102. As shown in the figure, the application layer 101A includes a copy application 121, a scanner application 122, a fax application 123, and a printer application 124.

  For example, the copy application 121 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 the copy function. In addition, the fax application 123 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 101A and each driver in the service layer 102 is complicated.

  Returning to 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. 5 is an explanatory diagram showing the internal configuration of the integrated application 110 and the position of the document handling unit 212 which is a characteristic part of the present embodiment to be described later in the integrated application 110. As shown in this figure, the integrated application 110 includes an operation system subsystem 201, a management system subsystem 202, and an execution system subsystem 203.

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

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

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

  The operation system subsystem 201, the management system subsystem 202, and the execution system subsystem 203 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 execution subsystem 203 includes a document handling unit 212, a request management unit 211, and an execution control unit 213, which are features of the present embodiment. The document handling unit 212 receives a request for processing of document data from the request management unit 211 and controls the execution control unit 213 to perform reading control of the scanner 151a, read control from a local storage such as the HDD 151c, or the plotter 151b or local storage. Control to output to the user, and processes the common document data regardless of the input source or the output destination.

  FIG. 6 is a diagram in which each subsystem shown in FIG. 5 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. 6, the integrated application 110 has a plurality of packages, and the integrated application 110 itself is one package. Here, the package is a grouping of each component (symbol) of the UML model, and this package is represented by a folder-type symbol 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. 6, the integrated application 110 is a package having three packages of an operation subsystem 201, a management subsystem 202, and an execution subsystem 203 inside. Further, the execution subsystem 203 is a package having therein a package of a request management unit 211, a document handling unit 212, and an execution control unit 213. A straight line connecting the operation subsystem 201, the management subsystem 202, and the execution subsystem 203 indicates that there is a relationship such as message transmission / reception between the packages. A symbol written at the right end of the tabs of the operation subsystem 201, the management subsystem 202, and the execution subsystem 203 is a UML symbol indicating that the package is a subsystem.

  The document handling unit 212, which is a characteristic part of the present embodiment, will be described in detail. The document handling unit 212 performs processing when a request for processing document data is received from the request management unit 211. Note that the document handling unit 212 is configured based on an object orientation so that an existing model is not simply converted into an object, and functions can be added or modified more easily. The process until the configuration of such an object model is derived will be described.

  Conventionally, in a multifunction peripheral, each application such as the copy application 121 provided in the application layer 101 shown in FIG. 22 performs processing. FIG. 19 is an explanatory diagram showing the types of jobs for each application in a conventional multifunction machine. As shown in this figure, the application in charge to realize the function of the multifunction device performs “read”, “fax reception”, “print”, “accumulation”, or “fax transmission” when inputting as required. And so on. In such a configuration, a job such as “read” needs to be provided for each application. In other words, when the number of input sources or output destinations increases as a function of the multifunction peripheral, it is necessary to expand the function for each application. Therefore, although the processing is shared, there is a problem of what class configuration is generated so that the input / output and the processing can be shared.

  FIG. 20 is an explanatory diagram in which jobs provided for each application in the conventional multifunction peripheral are classified by input and output. As shown in this figure, it can be confirmed that jobs used for input or output are common even when the functions executed for each application are different. For this reason, the concept of providing an application for each function is eliminated, and the object model is configured so that the processing is made common and only the input source and the output destination are selected.

  FIG. 7 is a conceptual diagram showing the concept of processing performed in the document handling unit 212, which is a characteristic part of the present embodiment. As shown in this figure, regardless of whether the input source of the input processed document data is a paper document, an electronic document, or a FAX received document, it can be configured as a page from the input processed document data (hereinafter referred to as an input document). An image to be processed that is divided into possible predetermined sizes is obtained, and document data (hereinafter referred to as a user document) composed of the images to be processed is generated. Then, document data (hereinafter referred to as an output document) obtained by shaping the generated user document in accordance with the output destination is generated, and output such as printing, saving, or FAX transmission is performed. With such a configuration, when the input source and the output destination are changed or added, it is not necessary to modify the program for each of a plurality of provided applications, and the program development is facilitated.

  Also, in order to perform processing in common regardless of the input source or output destination, a format is prepared in advance, and the input document or output document is managed by applying the input document or output document to this format. Regardless of whether or not, it is possible to manage in common, and further, it is possible to easily perform processing.

  FIG. 8 is a conceptual diagram showing a concept of a configuration for managing input documents and output documents in the present embodiment. As shown in the figure, the input document and the output document are managed by being divided for each page. Each page is composed of an image and a layout that determines the arrangement of the images. That is, an input document or an output document is obtained by applying an image divided into a predetermined size that can be configured as a page in order according to a predetermined layout on each page.

  With this configuration, document data can be managed in a common format regardless of the input source or output destination, and processing such as “2 in 1” can be easily performed. .

  That is, an image (hereinafter referred to as an input image) divided according to a layout (hereinafter referred to as an input layout) for each page (hereinafter referred to as an input page) is generated from an input document input from an input source. When processing, an image to be processed (hereinafter referred to as a user image) is generated from the input image, and a user document having these user images is generated. Then, when outputting, an output image is created from the user image included in the user document, and the generated output image is applied to the output layout corresponding to the output destination for each page to generate the output document. FIG. 9 is an explanatory diagram showing a change in configuration from an input document to a user document and an output document used in the document processing according to the present embodiment. As shown in this figure, an input document is managed as a combination of an input page, an input layout, and an input image regardless of the input source, and a user document having only a user image generated from the input image when performing processing to manage. The user document has a user image divided into a predetermined size. Thereby, when outputting as an output document, the output image produced | generated from the user image according to the output layout can be arrange | positioned flexibly according to a user's request | requirement. When an output image is generated from a user image, processing such as enlargement or reduction is performed so as to apply to the output layout.

  Through the object modeling described above, the document handling unit 212 is configured to have an “input document class”, a “user document class”, and an “output document class”. Then, from the configuration shown in FIG. 8, “input document class” holds “input page class”, and “output document class” holds “output page class”. Further, “input page class” holds “input layout class” and “input image class”, and “output page class” holds “output layout class” and “output image class”. The “user document class” holds a “user image”.

  The “input document class” is provided with a subclass for each input source, and the “output document class” is similarly provided with a subclass for each output destination. In this embodiment, the input source is a “paper” document read by a scanner, a “net” document input via a network, and an “LS” document stored in a local storage such as a hard disk. Therefore, “input net document class”, “input paper document class”, and “input LS document class” are provided as subclasses of “input document class”. Similarly, the output destinations are “paper”, “net”, and “LS”, and “output net document class”, “output paper document class”, and “output LS document class” are provided as subclasses of “output document class”. It is done.

  When the document handling unit 212 designed by the object modeling described above receives a request to process document data from the request management unit 211, an input document (for example, a paper document, an electronic document, a FAX received document, etc.) After the input process is performed, a processing process is performed, and an output document (for example, a paper document, an electronic document, or a FAX transmission document) is output and processed. After these processes are performed, the data is output from the hardware resource 151 under the control of the service layer 102 from the active subsystem 203.

  The document handling unit 212 designed by the object modeling described above selects an input processing target from an input document such as a paper document, an electronic document, or a FAX reception document, for example, such as a paper document, an electronic document, or a FAX transmission document. The target of the output process is selected from the output document. In this case, the user who has used the conventional multi-function device 1 is troubled when the multi-function device 1 of the present invention is used. Therefore, the present invention provides an interface that is easy for the user to use. FIG. 10 is a conceptual diagram showing the concept of processing from the request from the user of the multifunction machine 1 according to the present embodiment to the determination of the input source and the output destination. As shown in the figure, by maintaining a correspondence relationship in which an input source and an output destination are determined according to an item selected by the user, an interface according to the user's request can be provided.

  FIG. 11 is a diagram showing the class structure of the document handling unit 212 designed by the above-described object modeling using UML classes. As shown in the figure, the document handling unit 212 includes a document operation scheduler class 1101, an input document class 1111, an input page class 1112, an input layout class 1113, an input image class 1114, and an input net document class 1115. , Input paper document class 1116, input LS document class 1117, user document class 1102, user image class 1103, output document class 1121, output page class 1122, output layout class 1123, and output image class 1124. , Output net document class 1125, output paper document class 1126, and output LS document class 1127. With such a configuration, it is possible to perform common document processing regardless of the input source or the output destination.

  A rectangle indicating each class has three sections, and from the top are 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 section indicating the input document class 1111 indicates that the class name of the class is “input document”, and an attribute section indicates that the attribute of the class is “number of pages”. The operation section indicates that the operations of the class are “input start ()”, “page addition ()”, and “end notification ()”.

  Thus, each class has an attribute section for possessing data (attribute) and an operation section for possessing 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 that materializes the class 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 “input start ()”, and when describing an argument to be passed to the operation, such as “(argument 1, argument 2)” There is also.

  Next, each class included in the document handling unit 212 that is a characteristic part of the present embodiment illustrated in FIG. 11 will be described.

  The document operation scheduler class 1101 is a class for managing and manipulating documents in order to perform document processing corresponding to the request received from the request management unit 211, and generates a subclass object of the user document class 1102 according to the request. Specifically, the document operation scheduler class 1101 has a registration () 1101a as an operation. The document operation scheduler class 1101 schedules document processing requested from the request management unit 211.

  The registration () 1101a receives a document processing request from the request management unit 211, and generates an object of the user document class 1102 corresponding to the received request. The information passed as an argument of the registration () 1101a includes information set by the user for document processing.

  The user document class 1102 is a class for managing processes from input processing of an input document to processing, and output of an output document (for example, a paper document, an electronic document, or a FAX transmission document) to an output destination. Further, the user document class 1102 derives specifications for realizing the user's request from information set when the user uses the multifunction device 1, and the input document class 1111 and the output document class so as to satisfy the derived specifications. Let 1121 be a class that performs control by instructing start or the like. More specifically, the user document class 1102 has user request 1102a, input document type 1102b, output document type 1102c, and input / output timing 1102d as attributes, and a start () 1102 e and end notification () 1102 f as operations. Have. Also, the subclass of the user document class 1102 deletes the objects of the subclass of the input document class 1111 and the subclass of the output document class 1121 after the document processing is completed. It should be noted that the correspondence between the user request 1102a, the input document type 1102b, and the output document type 1102c is input as to whether the request information of the present invention is to be controlled and whether to control the input paper document means. This corresponds to the correspondence between whether to control the communication document means, whether to control the output paper document means, whether to control the output electronic document means, and whether to control the output communication document means.

  The user request 1102a is a document processing request input from a user operation panel 400 or a PC connected via a network. The user document class 1102 includes the user request 1102a, the input document type 1102b indicating the type of the subclass of the input document class 1111 used for the document processing request, and the subclass of the output document class 1121 used for the document processing request. An output document type 1102c indicating the type of the document is stored in association with each other. The user document object 1102A controls the subclass of the input document class 1111 and the subclass of the output document class 1121 specified by the input document type 1102b and the output document type 1102c. That is, the input document type 1102b corresponds to input document control information in other words, and the output document type 1102c corresponds to output document control information in other words.

  FIG. 12 is a diagram showing an example of correspondence between the user request 1102a, the input document type 1102b, and the output document type 1102c held by the user document class 1102 according to this embodiment. In this figure, “input” “paper” indicates the input paper document 1116, “LS” indicates the input LS document class 1117, and “net” indicates the input net document class 1115. Also, “paper” of “output” in this figure indicates the output paper document 1126, “LS” indicates the output LS document class 1127, and “net” indicates the output net document class 1125. As shown in this figure, the subclass of the input document class 1111 and the subclass of the output document class 1121 used for document processing are determined based on the user request received by the user document object 1102A. In addition, “paper”, “LS”, and “net” in “input” in this figure correspond to input paper document control information, input electronic document control information, and input communication document control means. Furthermore, “paper”, “LS”, and “net” in “output” in this figure correspond to output paper document control information, output electronic document control information, and output communication document control means.

  FIG. 13 is a diagram showing a screen example of the liquid crystal touch panel 420 displayed when the copy server key 403 on the operation panel 400 is pressed. As shown in the figure, the liquid layer touch panel 420 displays document data stored in the local storage. When the displayed “document name” field 1301 is pressed to select document data, the color of the document name indicating the name of the document data is inverted. When the document data is selected, the printer key 404 shown in FIG. 4 is pressed to print out the stored image corresponding to the selected document according to the designated printing condition. In this case, “print stored image” is selected as a user request. Then, the objects of the input LS document class 1117 and the output paper document class 1126 are generated from the correspondence shown in FIG. When the “original reading” button 1302 is pressed, “paper original + print accumulated original” is selected as a user request. As a result, objects of the input paper document class 1116, the input LS document class 1117, and the output paper document class 1126 are generated.

  FIG. 14 is a diagram illustrating a screen example of the liquid crystal touch panel 420 displayed when the scanner key 411 of the operation panel 400 is pressed. When the screen shown in the figure is displayed, a sender is selected from the sender display field 1401, a paper document is set by the scanner 151a, and a transmission key 405 is pressed, so that a user request is made. “Send paper original” is selected. Further, when the screen shown in this figure is displayed, the “stored document” button 1402 is pressed to select document data from the stored document data list, and after returning to this screen again. By pressing the transmission key 405, “paper original + accumulated original transmission” is selected as a user request. And the object produced | generated from the correspondence shown in FIG. 12 is determined.

  FIG. 15 is a diagram illustrating an example of a screen displayed on the liquid crystal touch panel 420 in a modification of the present embodiment. In the screen example shown in this figure, by selecting a paper document or an electronic document as a document processing target and selecting an output destination, it is possible to select a suitable user request and perform document processing. When an electronic document is selected, a screen for further setting whether to use local storage or network is displayed. In the screen example shown in this figure, since “electronic document”, “print”, and “save” are already selected, processing for printing and saving an electronic document is performed. In addition, when an electronic document on the local storage is selected on the above detailed setting screen, “print stored original + copy” is selected as a user request. In this way, the subclass of the input document class 1111 and the subclass of the output document class 1121 that are appropriately used for processing are determined regardless of the interface used for document processing.

  In the example shown in FIGS. 13, 14, and 15 described above, it is assumed that which user request is selected when a button is pressed is set in advance.

  The input / output timing 1102d holds timing for starting input to a subclass of the input document class 1111 or starting output to a subclass of the output document class 1121 when document processing is performed. By holding this timing, it is possible to perform input processing from one or more input sources or output processing to one or more output destinations from a user request.

  Note that a subclass having the specification of the user document class 1102 may be provided, and the above-described attributes may be held in the provided subclass.

  A start () 1102 e performs processing for giving a trigger for the user document class 1102 to start document processing. The user document object 1102A generates the input document class generated from the correspondence between the user request 1102a, the input document type 1102b, and the output document type 1102c described above, and the user request passed as an argument at start () 1102e. A subclass of 1111 and a subclass of the output document class 1121 are determined.

  Next, the start () 1102e generates an input net document object 1115A, an input paper document object 1116A, or an input LS document object 1117A based on this determination, and further, based on this determination, the output net document object 1125A, output paper A document object 1126A or an output LS document object 1127A is generated. The start () 1102 e calls the input start () 1111 b of the subclass of the input document class 1111 or the output start () 1121 b of the subclass of the output document class 1121 at the input / output timing 1102 d.

  The end notification () 1102 f performs processing for notifying the user document class 1102 that input processing or output processing has ended.

  The input document class 1111 is a class for managing an input document that has been input from the input source by applying it to a predetermined format common to the input source, in other words, an input page composed of an input image and an input layout. . Examples of the input source include scanners, devices connected via a network, and input means such as FAX reception or local storage. This input document class 1111 is an upper class (super class) of the input net document class 1115, the input paper document class 1116, and the input LS document class 1117, and the input document class 1111 itself is not materialized. The attributes and operations of the document class 1111 are inherited by the input net document class 1115, the input paper document class 1116, and the input LS document class 1117, which are lower classes (subclasses). Specifically, the input document class 1111 has the number of pages 1111a as attributes, input start () 1111b, page addition () 1111c, and end notification () 1111d as operations.

  The page number 1111a holds the page number of the input document subjected to the input process. Further, the input document class 1111 generates input page objects 1112A for the number of retained pages.

  The input start () 1111 b performs processing for giving a trigger for the input document class 1111 to start document processing. This input start () 1111 b is inherited by the input net document class 1115, the input paper document class 1116, and the input LS document class 1117 which are subclasses, and is overridden by specific processing in each subclass. The specific processing will be described in the description of the input net document class 1115, the input paper document class 1116, and the input LS document class 1117 described later.

  The page addition () 1111c adds a page to an input document managed by an object of a subclass of the input document class 1111. For example, it may be called when a page is added to an input document managed by an object of a subclass of the input document class 1111 when the user places the next paper document on the contact glass and performs reading. .

  An end notification () 1111 d notifies the input document class 1111 from the input page class 1112 described later that the processing for each page has ended.

  The input net document class 1115 is a subclass of the input document class 1111. The input document obtained by inputting the document acquired from the input source of the connected network is divided for each page, and an input page object 1112A is generated for each divided page. This class manages the input document by instructing the input page object 1112A to manage the corresponding page.

  Specifically, the input net document class 1115 inherits from the input document class 1111 the page number 1111a as an attribute, input start () 1111b, page addition () 1111c, and end notification () 1111d as operations. Furthermore, the input net document class 1115 holds specifications necessary for performing input processing via the network as attributes, but holds specifications that have been conventionally used, and is omitted in FIG. When an object in which the input net document class 1115 is materialized is generated, the specifications and the number of pages 1111a necessary for performing input processing to be held as attributes are expanded on the RAM 12b. ) Can be written and read.

  The input start () 1111b inherited from the input document class 1111 is a trigger for starting input processing. When called from the user document object 1102A, the input net document class 1115 receives a document via the network, An input document having a different format depending on the input source is input, and after the input processing is performed, the input document is converted into an input document and managed. The format of the input document is a common format regardless of the input source.

  Further, when the input net document object 1115A receives a document via the network in order to perform document input processing by the input start () 1111b, the input net document object 1115A receives a document input via the network from information passed as an argument. It is specified and received after connecting to the network using the FAX transmission / reception control unit 102e or the network communication control unit 102f that can be used via the execution control unit 213.

  The input paper document class 1116 is a subclass of the input document class 1111. The input document obtained by inputting the document read from the scanner 151a is divided into pages, and an input page object 1112A is generated for each divided page. This class manages an input document by instructing the page object 1112A to manage the corresponding page.

  Specifically, the input paper document class 1116 inherits from the input document class 1111 the page number 1111a as an attribute, input start () 1111b, page addition () 1111c, and end notification () 1111d as operations. Further, the input paper document class 1116 has, as attributes, the number of sheets 1116a and settings and specifications for reading an original from the scanner 151a, and has a next original presence confirmation () 1116b as an operation. Note that settings and specifications for reading a document from the scanner 151a are the same as those used in the past, and are omitted in FIG. When an object that materializes the input paper document class 1116 is generated, settings and specifications for reading a document held as attributes and the number of pages 1111a are developed on the RAM 12b. Can be written and read.

  The number of sheets 1116a holds the number of originals set for reading in the multifunction machine 1. Then, the next original presence / absence confirmation () 1116 b requests the execution control unit 213 to input whether or not a paper document to be input to the automatic document feeder is set. Confirm whether or not.

  An input start () 1111b inherited from the input document class 1111 is a trigger for starting input processing. When called from the user document object 1102A, the input paper document class 1116 reads and reads a document with the scanner 151a. Control is performed by converting from an original to an input document for management.

  The input paper document class 1116 reads using the scanner control unit 102a that can be used via the execution control unit 213 when the original is read by the scanner 151a by the input start () 1111b. Even when the input paper document object 1116A reads a manuscript printed on the front and back of the paper, the manuscript read in front and back is converted into the input document, but there is no concept of front and back in the input document. That is, the read original becomes an input document assigned as an input page in the read order, regardless of whether only the front side or both sides are read. As a result, the input document is held in a common format regardless of the characteristics of the medium or the manuscript handling mode of the scanner 151a, so that it is not necessary to perform different processing depending on the difference in the input source, and the processing is easy. It becomes.

  The input LS document class 1117 is a subclass of the input document class 1111. The input LS document class 1117 divides the input document obtained by inputting the electronic document read from the local storage such as a hard disk into pages, and sets the input page object 1112A for each divided page. It is a class that manages the input document by generating and instructing the input page object 1112A to manage the corresponding page.

  Specifically, the input LS document class 1117 inherits the number of pages 1111a held as an attribute from the input document class 1111 and receives input start () 1111b, page addition () 1111c, and end notification () 1111d as operations. Take over. Further, the input LS document class 1117 retains settings and specifications for reading an electronic document from the local storage as attributes, but retains settings and specifications that have been used conventionally, and is omitted in FIG. When an object that materializes the input LS document class 1117 is generated, the page number 1111a as an attribute, the setting and specification for reading an electronic document from the local storage, and the page number 1111a are expanded on the RAM 12b. These data (attributes) can be written and read.

  An input start () 1111 b inherited from the input document class 1111 is a trigger for starting input processing. When called from the user document object 1102 A, the electronic document is read from the local storage and read into the input LS document class 1117. Control is performed by converting the electronic document into an input document.

  The input LS document class 1117 reads using the accumulation control unit 102c that can be used via the execution control unit 213 when the electronic document is read by the input start () 1111b.

  Further, the input document managed by the input net document class 1115, the input paper document class 1116, and the input LS document class 1117 uses the common input page class 1112, input layout class 1113, input image class 1114, etc. regardless of the input source. Therefore, it is possible to perform common processing regardless of the input source. Next, the input page class 1112, the input layout class 1113, and the input image class 1114 will be described.

  The input page class 1112 is a class for managing each page divided from the input document managed by the input document class 1111 as an input page. The input page class 1112 generates an input layout object 1113A and an input image object 1114A, and manages them as a configuration in which the input image is applied to the input layout.

  Further, when setting the input layout for each page, for example, when the user sets a document read by the scanner 151a to be a “2 in 1” consolidated document, the input layout is a layout in which two input images are applied. Thus, an input layout object 1113A that satisfies this condition is generated.

  Specifically, this input page class 1112 has a page number 1112a as an attribute, and has an input start () 1112 b and an end notification () 1112 c as operations. When an object in which the input page class 1112 is materialized is generated, the page number 1112a is developed as an attribute on the RAM 12b, and it is possible to write and read these data (attributes).

  The page number 1112a holds a number indicating a page managed by the input page object 1112A. That is, since the input page object 1112A is generated by the number of pages 1111a held by the subclass object of the input document class 1111, the page number to which the input page object 1112A is allocated is held by the page number 1112a.

  The input start () 1112 b performs a process for giving a trigger for the input page class 1112 to start page processing. When this input start () 1112b is called from an object of a subclass of the input document class 1111 such as the input net document object 1115A, information on the page in the input document corresponding to the page number passed as an argument is acquired. Then, the generation of the input layout object 1113A and the input image object 1114A is started based on the acquired page information.

  Further, when the input start () 1112 b is called, the input page class 1112 acquires information on the page in the corresponding input document from the input document managed by the input document class 1111, and generates the input layout object 1113 A and the input The input page is managed using the image object 1114A.

  The end notification () 1112 c is called when each input image object 1114 </ b> A described later notifies the input page class 1112 that the image processing has ended. When this end notification () 1112 c is called from all the input image objects 1114 A generated by the input page class 1112, the input page class 1112 determines that the processing of all pages has been completed.

  The input layout class 1113 is a class for creating and managing a layout (hereinafter referred to as an input layout) used for applying an input image described later to an input page managed by the input page class 1112. Specifically, this input layout class 1113 has information such as an outer frame, an inner frame, or an offset position as an attribute, but is omitted in FIG. The input layout class 1113 includes a layout creation () 1113a as an operation. Note that when an object that materializes the input layout class 1113 is generated, information such as an outer frame, an inner frame, or an offset position is developed on the RAM 12b as attributes, so that these data (attributes) are written and read out. It becomes possible to do.

  The layout creation () 1113a creates an input layout in which the input layout object 1113A arranges the input image at a suitable position on the input page. When this layout creation () 1113a is called from the input page object 1112A, by setting the outer frame, inner frame or offset position according to the user's request as an attribute from the information passed as an argument, the input A layout is created. Thereby, the number of input images in the input page is determined. That is, the input page can be divided into minimum units of document handling called input images.

  The input image class 1114 is a class for managing an image (hereinafter referred to as an input image) applicable to the arrangement determined by the input layout with respect to the input page. Specifically, the input image class 1114 reads and holds the entity of an image in a range that becomes an input image from an input document generated by an object of a subclass of the input document class 1111 described above. The input image class 1114 has information for specifying the substance of the read image as an attribute, and has an input start () 1114 a as an operation. Note that when an object that materializes the input image class 1114 is generated, information for specifying the substance of the read image is developed on the RAM 12b, so that these data (attributes) may be written and read. It becomes possible.

  The input image refers to an image applied to the input layout, and is an image of a predetermined size, which is an image divided into minimum units for document handling in this embodiment. The minimum unit of document handling means an area that can be configured as one page. For example, if no special setting is made, the entire area of one page becomes an input image and is set to “2 in 1”. If this is the case, each area obtained by dividing one page into two is an input image. In addition, the input image includes not only a simple image but also character information and graphics shown in the above-described area.

  The input start () 1114 a performs processing for giving a trigger for the input image class 1114 to start image processing. When this input start () 1114 a is called from the input page object 1112 A, information for reading the substance of the image in the range determined by the setting of the input layout passed as an argument and specifying the substance of the read image As an attribute, and a user image object 1103A for managing a user image corresponding to the input image is generated.

  The user image class 1103 is a class that manages a user image to be processed from an input image and performs a processing process for generating an output image. Specifically, the user image class 1103 includes information for specifying a user image generated as an attribute, and includes creation () 1103 a and usage () 1103 b as operations. When an object that materializes the user image class 1103 is generated, information for specifying the created image is expanded on the RAM 12b, so that these data (attributes) can be written and read. It becomes.

  The user image is an image to be processed, and is an image of a predetermined size, which is an image divided into the minimum unit of document handling in this embodiment. Since the minimum unit of document handling has been described in the input image, it will be omitted. The user image includes not only a simple image but also character information or a figure shown as a user image in an area of a predetermined size.

  Creation () 1103 a is called from the input image class 1114 and performs processing for generating a user image based on the input image corresponding to the user image class 1103. When the creation () 1103a is called from the input image object 1114A, the entity of the input image is read, and the information specifying the entity of the image is written in the attribute as the user image.

  Usage () 1103 b is called from an output image class 1124 described later, and after processing the entity of the image read in creation () 1103 a so as to be suitable for the output format, it is transmitted to the output image class 1124, and the output image Is generated. As an example of the processing, when it is desired to output “2 in 1” of a document that has been input for each sheet, it may be possible to reduce the user image.

  The output document class 1121 is a class that generates an output document composed of a predetermined format common to all output destinations, in other words, an output page that combines an output image and an output layout, and performs output processing on the output destination. . The output destination may be an output unit such as a plotter, a printer, a device connected via a network, FAX transmission, or local storage. The output document class 1121 is an upper class (super class) of the output net document class 1125, the output paper document class 1126, and the output LS document class 1127, and the output document class 1121 itself is not materialized. The attributes and operations of the document class 1121 are inherited by the output net document class 1125, the output paper document class 1126, and the output LS document class 1127, which are lower classes (subclasses). Specifically, the output document class 1121 has a page number 1121a as an attribute, an output start () 1121b, a page addition () 1121c, and an end notification () 1121d as operations.

  The page number 1121a holds the number of pages of the output document subjected to the output process. The number of pages of the output document can be obtained from the settings made when outputting to the multifunction machine 1 and the number of user images held by the user document object 1102A. Specifically, when the output start () 1121b described later is called, the number of pages is obtained from the number of user images passed as an argument, the output layout determined from the settings for output, and the like. The number is set to 1121a. For example, when the number of user images held by the user document object 1102A is four and the user is set to output “2 in 1”, the page number 1121a is set to “2”. Further, the output document class 1121 generates the output page object 1122A by the number of pages. Further, the page number 1121a is obtained by calling the page addition () 1121c to be described later, even if the page number 1121a has already been determined, the number of pages that have undergone input processing due to reasons such as further input processing being performed. Even when the number increases, the number of pages 1121a can be added.

  The output start () 1121 b performs a process of giving a trigger for the output document class 1121 to start document processing. This output start () 1121 b is inherited by the output net document class 1125, the output paper document class 1126, and the output LS document class 1127 which are subclasses, and is overridden by specific processing in each subclass. The specific processing will be described with reference to an output net document class 1125, an output paper document class 1126, and an output LS document class 1127 described later.

  The page addition () 1121c is called from the user document class 1102 and performs a process of adding the page number 1121a.

  The end notification () 1121 d notifies the output document class 1121, which will be described later, to the output document class 1121 that the processing for each page has ended.

  The output net document class 1125 is a subclass of the output document class 1121, is a class that connects to the output destination of the output document via the network, and instructs the output page object 1122A to perform output processing for each output page of the output document. It is. The output net document class 1125 instructs the execution control unit 213 to control communication according to a different protocol for each output destination, for example, FAX transmission, mail transmission, file transfer, and the like. A corresponding output document format is prepared, and the output document is formatted and output in a format according to the output destination. This format is a well-known format normally used in communications such as FAX transmission.

  Specifically, the output net document class 1125 inherits the page number 1121a as an attribute, the output start () 1121b, the page addition () 1121c, and the end notification () 1121d from the output document class 1121. Furthermore, the output net document class 1125 holds, as attributes, specifications and settings necessary for performing output processing via the network, but is omitted in FIG. Note that when an object that materializes the output net document class 1125 is generated, specifications and settings necessary to perform output processing held as attributes and the number of pages 1121a are expanded on the RAM 12b. It is possible to write and read (attribute).

  The output start () 1121b inherited from the output document class 1121 is a trigger for starting output processing. When called from the user document object 1102A, the output net document class 1125 connects to the output destination via the network. Then, control is performed to generate and output an output document shaped in a format corresponding to the output destination using a user image generated in advance.

  Further, the output net document object 1125A specifies the output destination via the network from the information passed as the argument of the output start () 1121b, and can be used via the execution control unit 213, the FAX transmission / reception control unit 102e or the network communication. By connecting to a network using the control unit 102f and performing processing such as registration of an output document to be output to an output destination, an output document output by an output page class 1122 or an output image class 1124 described later is configured. It is possible to output information such as an output layout and an output image to an output destination.

  The output paper document class 1126 is a subclass of the output document class 1121 and is a class that controls the plotter 151b to instruct the output page object 1122A to perform output processing for each output page of the output document. The output paper document class 1126 instructs the execution control unit 213 to output by controlling the plotter 151b, prepares a format suitable for output by the plotter 151b, and uses the format in which the output document is prepared. Process to output.

  Specifically, the output paper document class 1126 inherits from the output document class 1121 the page number 1121a as an attribute, and the output start () 1121b, page addition () 1121c, and end notification () 1121d as operations. The output paper document class 1126 further has settings and specifications for outputting a document from the plotter 151b as attributes. Note that the settings and specifications for outputting the document from the plotter 151b are the same as those used in the prior art, and are omitted in FIG. When an object that materializes the output paper document class 1126 is generated, settings and specifications for outputting a document as attributes and the number of pages 1111a are developed on the RAM 12b. Writing and reading can be performed.

  The output start () 1121b inherited from the output document class 1121 is a trigger for starting output processing, and when called from the user document object 1102A, the output paper document class 1126 has a format for printing on the plotter 151b. Use to control output document output.

  Further, when the output start () 1121b is called, the output paper document class 1126 performs control to output to the plotter 151b by the plotter control unit 102b that can be used via the execution control unit 213 when printing. Further, it instructs the output page object 1122A to determine a layout suitable for printing and an arrangement of output images. This makes it possible to perform common processing regardless of the characteristics of the medium or the difference in the document handling mode by the plotter 151b. Further, the output paper document class 1126 determines whether to print only on the front side or the back side of the paper based on the settings input by the user, and gives an instruction to control the plotter 151b to follow the determination.

  The output LS document class 1127 is a subclass of the output document class 1121 and is a class that determines a storage location in a local storage such as a hard disk and instructs the output page object 1122A to perform output processing for each output page of the output document. is there. Note that there is no restriction on the format of the electronic document when the output document is stored in the local storage.

  Specifically, the output LS document class 1127 inherits the page number 1121a as an attribute, the output start () 1121b, the page addition () 1121c, and the end notification () 1121d as operations from the output document class 1121. Furthermore, the output LS document class 1127 retains settings and specifications for saving in the local storage as attributes, but is omitted in FIG. 11 because it uses settings and specifications that have been used conventionally. When an object that materializes the output LS document class 1127 is generated, the settings and specifications for saving in the local storage as attributes and the number of pages 1121a are expanded on the RAM 12b. Can be written and read.

  The output start () 1121 b inherited from the output document class 1121 is a trigger for starting output processing. When called from the user document object 1102 A, the output LS document class 1127 specifies the storage location of the local storage, The file name and the like of the electronic document to be saved are registered, and an output document shaped in a format for saving using a user image generated in advance is generated and output.

  Further, the output LS document class 1127 uses the accumulation control unit 102 c that specifies the storage destination and the file name of the electronic document from the information passed as the argument of the output start () 1121 b and can be used via the execution control unit 213. By performing processing such as registration of the output document in the storage location of the local storage, it is possible to output information related to the output document, such as an output layout and an output image, from an output page class 1122 and an output image class 1124 described later.

  The output page class 1122 is a class that generates each page constituting the output document generated by the output document class 1121 as an output page, and outputs settings for each page such as a layout to an output destination. The output page class 1122 generates an output layout object 1123A and an output image object 1124A, which will be described later, and generates an output page with a configuration in which the output image is applied to the output layout.

  Specifically, the output page class 1122 has a page number 1122a as an attribute, and has an output start () 1122 b and an end notification () 1122 c as operations. Note that when an object that materializes the output page class 1122 is generated, the page number 1122a is expanded as an attribute on the RAM 12b, so that these data (attributes) can be written and read.

  The page number 1122a holds a number indicating a page generated by the output page object 1122A. That is, since the output page object 1122A is generated for the number of pages 1121a held by the subclass object of the output document class 1121, the page number 1122a is held to specify the page to which the output page object 1122A is allocated.

  The output start () 1122 b performs a process of giving a trigger for the output page class 1122 to start page processing. When this output start () 1122 b is called from an object of a subclass of the output document class 1121 such as the output net document object 1125 A, the page number determined by the page number passed as an argument and the setting accepted by the user Information is acquired, and an output layout object 1123A and an output image object 1124A are generated based on the acquired page information.

  Further, when the output start () 1122 b is called, the output page class 1122 generates an output generated by acquiring information of a corresponding page (hereinafter referred to as an output page) from an output document managed by the output document class 1121. The layout object 1123A is used to output the setting for each page such as the output layout to the output destination, and then an output image object 1124A that holds the output image applied to the output layout is generated.

  The end notification () 1122 c performs a process in which each output image object 1124 </ b> A notifies the output page class 1122 that the image processing has ended. When this end notification () 1122 c is called from all the output image objects 1124 </ b> A generated by the output page class 1122, the output page class 1122 determines that all page processing has been completed.

  The output layout class 1123 is a class for creating and managing a layout (hereinafter referred to as an output layout) used to apply an output image to an output page generated by the output page class 1122. Specifically, this output layout class 1123 has information such as an outer frame, an inner frame, or an offset position as an attribute, but since it uses information that has been used conventionally, it is omitted in FIG. The output layout class 1123 has a layout creation () 1123a as an operation. When an object that materializes the output layout class 1123 is generated, information such as an outer frame, an inner frame, or an offset position is developed on the RAM 12b as attributes, so that writing and reading of these data (attributes) It becomes possible to do.

  The layout creation () 1123a performs processing for setting the output layout object 1123A so that the output image is arranged at a suitable position on the output page. When this layout creation () 1123a is called from the output page object 1122A, an outer frame, an inner frame, or an offset position as an attribute is set from information passed as an argument. This setting determines the number of output images in the output page. As a result, it is possible to apply a minimum unit of document handling called an output image to the output page.

  The output image class 1124 is a class for generating and outputting an image (hereinafter referred to as an output image) that corresponds to the arrangement determined by the output layout for the output page. Specifically, the output image class 1124 acquires an output image in a format suitable for the output destination generated based on the user image generated by the user image object 1103A described above. The output image class 1124 has information for holding an output image as an attribute, and has an output start () 1124a as an operation. Note that when an object that materializes the output image class 1124 is generated, information for holding the output image is developed on the RAM 12b, so that these data (attributes) can be written and read. It becomes.

  The output image refers to an image applied to the output layout. Like the input image and user image described above, the output image is an image of a predetermined size, in this embodiment, an image divided into the minimum unit for document handling. It becomes. The output image includes not only a simple image but also character information displayed in a frame defined by the output layout, a figure, and the like.

  The output start () 1124a performs processing for giving a trigger for the output image class 1124 to start image processing. When this output start () 1124a is called from the output page object 1122A, the user image corresponding to the information passed as an argument is identified, and the user image object 1103A usage () 1103b is called to call the user An output image processed to fit the output layout is received from the image, and the received output image is output to the output destination.

  FIG. 16 is an explanatory diagram illustrating steps until the document handling unit 212 according to the present embodiment generates a “4 in 1” output document from a “2 in 1” input document. As shown in the figure, the document handling unit 212 can easily perform processing in units of images by using a layout for each page and a combination of images applied to the layout.

  Next, returning to FIG. 11, the relationship between the classes will be described. As shown in this figure, the straight line connecting the rectangles indicating each class indicates that there is a relationship between the classes at both ends, and the characters near the ends of this line indicate the role of the class, and the numbers indicate the class. Each multiplicity is shown. Here, the role is the role and position of the other class as seen from one class at both ends of the line, and the multiplicity is the number of objects generated from the class at both ends of the line. It is a correspondence relationship.

  For example, the role of the user document class 1102 viewed from the document operation scheduler class 1101 is “request”, the role of the document operation scheduler class 1101 viewed from the user document class 1102 is “reception”, and the multiplicity of the document operation scheduler class 1101. Is “1”, and the multiplicity of the user document class 1102 is “0... *”. Here, “0... *” Indicates that the multiplicity of the user document class 1102 is in a range from 0 to no upper limit. For example, when “1..3” is described, the multiplicity of the class is in the range of 1 to 3.

  As shown in the figure, in the scene where the document handling unit 212 is executed, there is only one object in which the document operation scheduler class 1101 is expanded (substantiated) on the RAM 12b. This document operation scheduler class 1101 There are zero or more objects in which the user document class 1102 to be requested for document processing is materialized and there is no upper limit.

  Next, the class relationship between the user document class 1102 and the input document class 1111 will be described. The input document class 1111 has a role as an input document used for generating a user document when viewed from the user document class 1102, while the user document class 1102 is processed according to the input document class 1111. Has a role as a user document. It becomes possible to generate a user document to be processed from a document input by such a class relationship.

  Further, the user document class 1102 is generated for each request from the user, whereas the input document class 1111 is generated and input according to the number of documents necessary for generating the user document. It is a class that performs processing. Therefore, the user document class 1102 and the input document class 1111 have a one-to-many relationship. A case where a plurality of input documents are input when a single user document is generated may be, for example, a case where there is a request to print a fax received document and an electronic document stored in advance together. It is done. It is also possible to output documents having different input sources, such as “paper” documents and “net” documents, in a single manner, or a plurality of documents having the same input source, such as two “net” documents. It is also possible to output the input documents as one.

  Next, the relationship between the input document class 1111, the input net document class 1115, the input paper document class 1116, and the input LS document class 1117 will be described. The input document class 1111 is an upper class (super class) of the input net document class 1115, the input paper document class 1116, and the input LS document class 1117, and the input net document class 1115, the input paper document class 1116, and the input LS document class 1117. Inherits the attributes and operations of the input document class 1111.

  The relationship between the input document class 1111 and the input page class 1112 will be described. The input page class 1112 is generated for each page of the document held by the input document class 1111. Therefore, the input page class 1112 has a role as a page when viewed from the input document class 1111, while the input document class 1111 has a role as a document when viewed from the input page class 1112. .

  The input document class 1111 is generated for each input document to be input processed, whereas the input page class 1112 is a class generated for each page. The class 1112 has a one-to-many relationship. Also, the input page class 1112 has a relationship that is aggregated into the input document class 1111.

  Next, the relationship between the input page class 1112 and the input layout class 1113 will be described. The input page class 1112 is generated for each page, and the input layout class 1113 is a layout determined for each page. In other words, the input layout class 1113 has a role as a frame for each page when viewed from the input page class 1112, while the input page class 1112 has a role as a page when viewed from the input layout class 1113. ing. With this relationship, the input page class 1112 and the input layout class 1113 have a one-to-one relationship.

  The relationship between the input page class 1112 and the input image class 1114 will be described. The input image class 1114 is generated for each area divided according to the page layout held by the input page class 1112. Therefore, the input image class 1114 has a role as an in-frame component applied to the frame of the page when viewed from the input page class 1112, while the input page class 1112 is viewed from the input image class 1114. And has a role as a page.

  Further, the input page class 1112 is generated for each page of the input document, whereas the input image class 1114 is a class generated by the number divided according to the layout of the page. The class 1112 and the input image class 1114 have a one-to-many relationship. Also, the input image class 1114 has a relationship that is aggregated into the input page class 1112.

  Next, the relationship between the input image class 1114 and the user image class 1103 will be described. The input image class 1114 is generated by the number divided according to the frame of the page, and the user image class 1103 is created as a processing target based on the input image. That is, the user image class 1103 has a role as a created object when viewed from the input image class 1114, while the input image class 1114 has a role as an input object when viewed from the user image class 1103. Yes.

  The user image class 1103 is generated based on the input image class 1114, and both the input image class 1114 and the user image class 1103 are divided by the minimum unit of document handling. The user image class 1103 has a one-to-one relationship.

  The relationship between the user document class 1102 and the user image class 1103 will be described. The user image class 1103 is generated for each image serving as a minimum unit of handling constituting the user document held by the user document class 1102. Therefore, the user image class 1103 has a role as a component when viewed from the user document class 1102, while the user document class 1102 has a role as a document when viewed from the user image class 1103. Yes.

  The user image class 1103 is generated for each image constituting the document, whereas the user document class 1102 is a class generated for each document. Therefore, the user document class 1102 and the user image class 1103 has a one-to-many relationship. Also, the user image class 1103 has a relationship that is aggregated into the user document class 1102.

  Next, the class relationship between the user document class 1102 and the output document class 1121 will be described. When viewed from the user document class 1102, the output document class 1121 has a role as an output document output in an output format according to a user request, while the user document class 1102 is viewed from the output document class 1121. And has a role as a user document. With such a class relationship, an output document can be generated from a user document to be processed.

  The user document class 1102 is generated for each document process from the document operation scheduler class 1101, and the output document class 1121 is generated for each document output to an output destination based on a user request. Yes, it is naturally possible to output a plurality of documents based on one user request. That is, the user document class 1102 and the output document class 1121 have a one-to-many relationship. A case where a plurality of documents are output based on a single user request may be a case where the user has made a setting for “printing + accumulating” a document read by a scanner.

  Next, the relationship between the output image class 1124 and the user image class 1103 will be described. The output image class 1124 is generated by using the user images as many as the number applied to the frame of the output page. That is, the output image class 1124 has a role as an output object when viewed from the user image class 1103, while the user image class 1103 has a role as a use object when viewed from the output image class 1124. Yes.

  The output image class 1124 is generated based on the user image class 1103, and both the output image class 1124 and the user image class 1103 are divided by the minimum unit of document handling. In addition, a case where one user image is used for each of a plurality of output documents, or a case where a plurality of one user image is used in one output document can be considered. Therefore, the user image class 1103 and the output image class 1124 have a one-to-many relationship.

  The relationship between the output document class 1121, the output net document class 1125, the output paper document class 1126, and the output LS document class 1127 is as follows: the input document class 1111, the input net document class 1115, the input paper document class 1116, and the input LS document. Since the relationship is the same as that of the class 1117, the description is omitted.

  The relationship between the output document class 1121 and the output page class 1122 is the relationship between the input document class 1111 and the input page class 1112, and the relationship between the output page class 1122 and the output layout class 1123 is the relationship between the input page class 1112 and the input layout class 1113. Since the relationship between the output page class 1122 and the output image class 1124 is the same as the relationship between the input page class 1112 and the input image class 1114, description thereof is omitted.

  As described above, the document operation scheduler class 1101, the input document class 1111, the input page class 1112, the input layout class 1113, the input image class 1114, the input net document class 1115, the input paper document class 1116, the input LS document class 1117, the user document The objects of class 1102, user image class 1103, output document class 1121, output page class 1122, output layout class 1123, output image class 1124, output net document class 1125, output paper document class 1126, and output LS document class 1127 are: The functions necessary for the document handling unit 212 can be realized by interlinking and cooperating with each other. It is possible.

  Next, an example of an execution procedure of each class operation shown in FIG. 11 will be described. First, an example in which the document handling unit 212 performs input processing from a plurality of input means will be described. FIG. 17 is a UML sequence diagram showing a processing procedure until the document handling unit 212 inputs a paper document and an electronic document stored in the local storage.

  Here, the UML sequence diagram will be described. Each rectangle arranged in the upper part of FIG. 17 indicates a class object. 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).

  Horizontal arrows connecting the lifelines indicate execution of operations included in the 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. Further, when the arrow points to its own object, it means that the object calls the operation included in itself.

  As shown in FIG. 17, when the user operates the multi-function device 1 and inputs that the document processing is to be performed, the operation subsystem 201 sends a request indicating the user request for document processing input by the user to the document operation scheduler. The object is registered in the object 1101A (step S1501). Specifically, the request management unit 211 accepts a user request from the operation subsystem 201 as a request request. Then, the request management unit 211 calls the registration () 1101a of the document operation scheduler object 1101A of the document handling unit 212 and passes the user request.

  Since the document operation scheduler object 1101A receives a user request for document processing, the document operation scheduler object 1101A generates an object of the user document class 1102 corresponding to the user request, calls the start () 1102e of the generated user document object 1102A, and performs document processing. The user request is delivered (step S1502). Generation is an operation of all objects, and each object is materialized on the RAM 12b by generation.

  Since the user document object 1102A has received a user request, a subclass of the input document class 1111 to be generated and an output document class 1121 to be generated based on the correspondence between the user request 1102a, the input document type 1102b, and the output document type 1102c. Is determined (step S1503). In this sequence diagram, it is assumed that the input paper document class 1116 and the input LS document class 1117 are determined as subclasses of the input document class 1111 to be generated. In step S1503, a subclass of the output document class 1121 is also determined. Processing performed in the determined subclass of the output document class 1121 will be described with reference to FIG. Then, the user document object 1102A generates a subclass of the determined input document class 1111 and a subclass of the output document class 1121. Note that the timing at which the user document object 1102A is called is determined by the input / output timing 1102d.

  Then, the user document object 1102A calls the input start () 1111b of the input paper document object 1116A and requests the input start (step S1504).

  Next, the input paper document object 1116A controls the scanner 151a through the execution control unit 213 in response to the request, and when it is confirmed that there is a paper document, the page addition () 1111c is called to set the page number to the page number 1111a. It is added (step S1505).

  The input paper document object 1116A generates an input page object 1112A corresponding to the number of added pages, calls the input start () 1112a of the generated input page object 1112A, and starts input processing for each page of the paper document. Is requested (step S1506).

  Next, the input page object 1112A starts page input processing, first generates the input layout object 1113A, calls the layout creation () 1113a of the generated input layout object 1113A, and sets the settings input by the user. Based on this, the attribute of the generated input layout object 1113A is set (step S1507). Then, the input layout object 1113A transmits information on the layout such as the arrangement and number of input images determined for each page as a message to the input page object 1112A.

  Then, the input page object 1112A generates as many input image objects 1114A as the number of input images for each input page determined by the input layout object 1113A, calls the input start () 1114a of the generated input image object 1114A, The input image object 1114A is requested to start input processing of the input image (step S1508).

  Next, the input image object 1114A calls input start () to the paper document input processing unit that manages the image of the paper document that has been input using the scanner 151a, so that the input image object 1114A has a region defined by the input layout. A request to transmit an image is made (step S1509). It is assumed that the paper document input processing unit is provided in the execution subsystem 203. Then, the paper document input processing unit transmits image information of an area defined by the input layout to the input image object 1114A (step S1510). As a result, the input image object 1114A holds the entity of the input image.

  Then, the input image object 1114A generates a user image object 1103A and calls creation () 1103a of the generated user image object 1103A (step S1511). Accordingly, the user image held by the user image object 1103A is created based on the substance of the input image held by the input image object 1114A.

  Then, after creating the user image, the input image object 1114A calls the end notification () 1112c of the input page object 1112A to notify that the image processing has ended (step S1512). Note that the processing from step S1509 to step S1512 is performed for each generated input image object 1114A.

  Next, when the input paper document object 1116A receives the completion of image processing from all the generated input image objects 1114A, the input paper document object 1116A calls the end notification () 1111d of the input paper document object 1116A, and the page processing is performed. Notification of completion is made (step S1513).

  Further, the input paper document object 1116A receives the notification of the presence of a set document from the device information management unit asynchronously with the above-described processing (step S1514).

  When the input paper document object 1116A receives that the processing of the page has been completed from all the generated input page objects 1112A, the input paper document object 1116A calls the next original presence / absence confirmation () 1116b to determine whether there is a paper document to be input processed. Is determined (step S1515). If the notification of the presence of a set original has been received from step S1514, it is determined that there is a paper document to be input, and the input paper document object 1116A calls page addition () 1111c to execute steps S1505 and the subsequent steps. Start the process again.

  If the notification of the presence of a set original has not been received from step S1514, the input paper document object 1116A calls the end notification () 1102f of the user document object 1102A to notify that the paper document input processing has ended. (Step S1516).

  When the user document object 1102A receives a notification indicating that the paper document input processing is completed, the user document object 1102A calls the input start () 1111b of the input LS document object 1117A generated in step S1503 to start input. Is requested (step S1517).

  Next, the input LS document object 1117A generates as many input page objects 1112A as the number of pages held in the electronic document to be input, calls the input start () 1112b of the generated input page object 1112A, and The start of input processing for each page is requested (step S1518). It should be noted that the processing for acquiring the number of pages of the electronic document to be input is performed through the execution subsystem 203.

  Further, the input page object 1112A generated in step S1517 has a relationship to be aggregated into the input LS document object 1117A, whereas the input page object 1112A generated in step S1506 is aggregated to the input paper document object 1116A. It is different in that there is a relationship. Further, the input layout object 1113A and the input image object 1114A generated by the processing described later are in a relationship that is aggregated into the input page object 1112A that is aggregated into the input LS document object 1117A. The object to be aggregated is different from 1114A.

  Next, the input page object 1112A starts page input processing, first generates the input layout object 1113A, calls the layout creation () 1113a of the generated input layout object 1113A, and sets the settings input by the user. Based on this, the attribute of the generated input layout object 1113A is set (step S1519). Then, the input layout object 1113A transmits information on the layout such as the arrangement and number of input images determined for each page as a message to the input page object 1112A.

  Then, the input page object 1112A generates as many input image objects 1114A as the number of input images for each input page determined by the input layout object 1113A, calls the input start () 1114a of the generated input image object 1114A, The input image object 1114A is requested to start input processing of the input image (step S1520).

  Next, the input image object 1114A calls input start () to the accumulated document input processing unit that manages the image of the electronic document stored on the local storage, and displays an image of the area defined by the input layout. A request for transmission is made (step S1521). Note that the stored document input processing unit is provided in the execution subsystem 203. Then, the stored document input processing unit transmits the image information of the area defined by the input layout to the input image object 1114A (step S1522). As a result, the input image object 1114A holds the entity of the input image.

  Then, the input image object 1114A generates a user image object 1103A and calls creation () 1103a of the generated user image object 1103A (step S1523). Accordingly, the user image held by the user image object 1103A is created based on the substance of the input image held by the input image object 1114A. In other words, the user document object 1102A has a relationship that aggregates both the user image object 1103A input from a paper document and the user image object 1103A input from an electronic document.

  Then, after creating the user image, the input image object 1114A calls the end notification () 1112c of the input page object 1112A to notify that the image processing has ended (step S1524). The processing from step S1521 to step S1524 is performed for each generated input image object 1114A.

  Next, when the input page object 1112A receives the end of image processing from all the generated input image objects 1114A, the input page object 1112A calls the end notification () 1111d of the input LS document object 1117A, and the page processing is performed. Notification of completion is made (step S1525).

  When the input LS document object 1117A receives a message indicating that the processing of the page has been completed from all of the generated input page objects 1112A, the input LS document object 1117A calls the end notification () 1102f of the user document object 1102A and the electronic document on the local storage. Is notified that the input process has been completed (step S1526).

  With the processing procedure described above, it is possible to generate a user image that has been input from a paper document and an electronic document. Note that the processing procedure described above shows an example of the input processing according to the present embodiment, and the present invention is not limited to this processing procedure. For example, only one of the paper document and the electronic document may be input. As another example, a paper document and an electronic document on the network are input, an electronic document on the local storage and an electronic document on the network are input, or a paper document, an electronic document on the local storage, and an electronic document on the network All of these may be input processed.

  Next, an example in which the document handling unit 212 performs output processing from a plurality of output means will be described. FIG. 18 is a UML sequence diagram showing a processing procedure until the document handling unit 212 outputs a paper document and an electronic document stored in the local storage. The output process shown in FIG. 18 will be described on the assumption that the processing procedure such as the input process shown in FIG. 17 has been performed.

  Specifically, it is assumed that the subclass of the output document class 1121 used for processing is determined and generated as shown in step S1503 of FIG. Specifically, in the processing procedure shown in FIG. 18, the output document class 1121 subclass used for processing is an output paper document object 1126A and an output LS document object 1127A. Also, the user image object 1103A has already been generated and holds the substance of the user image.

  First, the user document object 1102A calls the output start () 1121b of the output paper document object 1126A based on the input / output timing 1102d as an attribute, and outputs the paper document from the plotter 151b to the output paper document object 1126A. The start of processing is requested (step S1601). When this output start () 1121b is called, the page number 1121a of the output paper document object 1126A is set.

  The output paper document object 1126A confirms whether a paper document can be output by using the plotter control unit 102b that can be used through the execution control unit 213 upon request, and then manages the paper document to be output from the plotter 151b. A document to be output is registered in the output processing unit (step S1602). It is assumed that the paper document output processing unit is provided in the execution system subsystem 203.

  Then, the output paper document object 1126A generates as many output page objects 1122A as the number of pages 1121a, calls the output start () 1122b of the generated output page object 1122A, and starts output processing for each page of the electronic document. Is requested (step S1603).

  Next, the output page object 1122A starts a page output process. First, in order to output in the format input by the user, an output layout object 1123A is generated, the layout creation () 1123a of the generated output layout object 1123A is called, and it is optimal for output in the format input by the user The attribute value is set to the attribute of the generated output layout object 1123A (step S1604).

  Then, the output layout object 1123A transmits information to be transmitted to the output destination computer regarding the number and layout of output images to be applied to the output page object 1122A as a message. Then, the output page object 1122A transmits necessary information of the output page to the paper document output processing unit, and performs page registration (step S1605).

  Then, the output page object 1122A generates as many output image objects 1124A as the number of output images applied to the output page determined by the output layout object 1123A, and calls the output start () 1124a of the generated output image object 1124A. The output image object 1124A is requested to start output processing of the output image (step S1606).

  Next, the output image object 1124A is a user image object 1103A whose correspondence is specified by information passed as an argument of the output start () 1124a, for example, information such as the page number or the number of the output image in the page. Use () 1103b is called (step S1607). Then, the user image object 1103A transmits corresponding image information to the output image object 1124A (step S1608). At that time, the user image object 1103A needs to perform processing such as enlargement or reduction on the substance of the image specified by the image information transmitted in advance so as to be applicable to the output layout. As a result, the output image object 1124A can hold the entity of the image.

  Then, the output image object 1124A starts outputting the received output image substance to the paper document output processing unit (step S1609). Next, when the output process ends, the output image object 1124A calls the end notification () 1122c of the output page object 1122A, and ends the image process (step S1610). Note that the processing in steps S1607 to S1610 is performed for each generated output image object 1124A.

  Next, when the output page object 1122A receives the completion of image processing from all the generated output image objects 1124A, the output page object 1122A calls the end notification () 1121d of the output paper document object 1126A, and the page processing is completed. This is notified (step S1611).

  When the output paper document object 1126A receives information indicating that the page processing has been completed from all the generated output page objects 1122A, the output paper document object 1126A transmits a message indicating that all the output images have been transmitted to the paper document output processing unit. Then, the end notification () 1102f of the user document object 1102A is called to notify that the output processing of the paper document has ended (step S1612). As a result, the paper document output processing unit executes the paper document output processing from the plotter 151b.

  When the user document object 1102A receives a notification indicating that the output processing of the paper document is completed, the user document object 1102A calls the output start () 1121b of the output LS document object 1127A generated in step S1503 in FIG. The output start is requested (step S1613). When this output start () 1121b is called, the page number 1121a of the output LS document object 1127A is set.

  The output LS document object 1127A transmits the file name of the electronic document to be output to the document storage processing unit, and registers the electronic document to be stored in the local storage in the document storage processing unit (step S1614).

  Then, the output LS document object 1127A generates as many output page objects 1122A as the number of pages 1121a, calls the output start () 1122b of the generated output page object 1122A, and starts output processing for each page of the electronic document. Is requested (step S1615).

  Further, the output page object 1122A generated in step S1615 has a relationship to be aggregated in the output LS document object 1127A, whereas the output page object 1122A generated in step S1603 is aggregated in the output paper document object 1126A. It is different in that there is a relationship. Further, the output layout object 1123A and the output image object 1124A generated by the processing described later are in a relationship aggregated in the output page object 1122A that is aggregated in the output LS document object 1127A. The object to be aggregated is different from 1124A.

  Next, the output page object 1122A starts a page output process. First, in order to output in the format input by the user, an output layout object 1123A is generated, the layout creation () 1123a of the generated output layout object 1123A is called, and it is optimal for output in the format input by the user The attribute value is set to the attribute of the generated output layout object 1123A (step S1616).

  Then, the output layout object 1123A transmits information to be transmitted to the output destination computer regarding the number and layout of output images to be applied to the output page object 1122A as a message. Then, the output page object 1122A transmits necessary information of the output page to the document accumulation processing unit and performs page registration (step S1617).

  Then, the output page object 1122A generates as many output image objects 1124A as the number of output images applied to the output page determined by the output layout object 1123A, and calls the output start () 1124a of the generated output image object 1124A. The output image object 1124A is requested to start output processing of the output image (step S1618).

  Next, the output image object 1124A is a user image object 1103A whose correspondence is specified by information passed as an argument of the output start () 1124a, for example, information such as the page number or the number of the output image in the page. Use () 1103b is called (step S1619). Then, the user image object 1103A transmits corresponding image information to the output image object 1124A (step S1620). At that time, the user image object 1103A needs to perform processing such as enlargement or reduction on the substance of the image specified by the image information transmitted in advance so as to be applicable to the output layout. As a result, the output image object 1124A can hold the entity of the image.

  Then, the output image object 1124A starts output processing of the substance of the received output image to the document storage processing unit (step S1621). Next, when the output process ends, the output image object 1124A calls the end notification () 1122c of the output page object 1122A, and ends the image process (step S1622). Note that the processing from step S1619 to step S1622 is performed for each generated output image object 1124A.

  Next, when the output page object 1122A receives the completion of image processing from all the generated output image objects 1124A, the output page object 1122A calls the end notification () 1121d of the output LS document object 1127A, and the processing of the page is completed. This is notified (step S1623).

  When the output LS document object 1127A receives a message indicating that the page processing has been completed from all the generated output page objects 1122A, the output LS document object 1127A transmits a message indicating that all output images have been transmitted to the document storage processing unit. Then, the end notification () 1102 f of the user document object 1102 A is called to notify that the output processing of the electronic document to the local storage has ended (step S 1624). As a result, the electronic document is stored in the local storage from the document storage processing unit.

  Then, the user document object 1102A deletes the generated input paper document object 1116A, input LS document object 1117A, output paper document object 1126A, and output LS document object 1127A, and ends the processing, assuming that the output processing has ended.

  With the processing procedure described above, it becomes possible to output a paper document and an electronic document from the generated user image. The above-described processing procedure shows an example of the output processing according to this embodiment, and the present invention is not limited to this processing procedure. For example, only one of the paper document and the electronic document may be output. Other examples include output processing of paper documents and electronic documents on the network, output processing of electronic documents on the local storage and electronic documents on the network, or paper documents and electronic documents on the local storage and electronic documents on the network. All of these may be output.

  As shown in the sequence diagrams of FIG. 17 and FIG. 18 described above, in this embodiment, when performing document processing, a document operation scheduler class 1101, a user document class 1102, an input document class 1111 and its subclass, An input page class 1112, an input layout class 1113, an input image class 1114, an output document class 1121, this subclass, an output page class 1122, an output image class 1124, an output layout class 1123, and a user image class 1103 By performing from document input processing to output processing with objects generated from each class, processing according to the user's request is facilitated. Further, by constructing the mechanism of the document handling unit 212 by object-oriented design, performing object modeling based on the concept as shown in FIG. 7, and using the above-described classes as classes necessary for document processing, Since the document handling unit 212 is realized, the software developer and software maintenance personnel can easily grasp the configuration and role of the document handling unit 212 and can perform document processing with high versatility and reliability. .

  The document processing program executed by the image forming apparatus according to 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 disc (FD), a CD- You may comprise so that it may record and provide on computer-readable recording media, such as R (CD Recordable) and DVD (Digital Versatile Disk). In this case, the CPU 11 reads out the document processing program from the recording medium and loads it onto the MEM-P 12, thereby causing the image forming apparatus to realize each step, each unit, or each unit described above.

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

  The configuration described above is an example of the document processing apparatus, the image forming apparatus, and the document processing program of the present invention, and is not limited to the configuration described above.

  Further, the present embodiment is not limited to a “paper” document, a “net” document, and an “LS” document, but optical or magnetic (CD-ROM / RAM, DVD-ROM / RAM, magnetic tape, A flexible disk, smart card, magneto-optical disk), infrared (IrDA, etc.), voice, or the like may be used.

  Since the document handling unit 212 of the present embodiment shares the processing regardless of the input source and the output destination, it is not necessary to create an application according to the input source and the output destination, and the burden of creating software is reduced. be able to. Then, although the procedure is different from the conventional procedure when the user uses it because the concept of the application is abolished, the user request 1102a, the input document type 1102b, and the output document type 1102c are changed as shown in the present embodiment. Since it is held in association with each other, it is possible to specify the subclass of the input document class 1111 and the subclass of the output document class 1121 by holding the correspondence relationship in advance for any user request. Since any interface can be provided, user convenience is improved.

  The document handling unit 212 according to the present embodiment is designed to be divided for each object and has the above-described configuration. If this causes a program change, only the corresponding class needs to be changed. For this reason, conventionally, when the function is expanded, the work amount of the designer is proportional to this, but the work amount is reduced by providing the above-described configuration.

  In addition, the conventional document processing part is designed for each application. However, the provision of the above-described configuration eliminates the concept of each application, thereby improving the design efficiency. In addition, when document processing is performed for each application, the layout differs for each output destination due to processing differences for each application even though the same setting is made for each output destination (for more detailed examples, headers or There was a problem that a document with a different footer interval was output. However, since the document handling unit 212 according to the present embodiment has the above-described configuration, the concept of performing processing for each application is eliminated, so that the problem that a document with a different layout is output is solved and reliability is improved. Improved.

  By providing the above-described configuration, when the number of input sources or output destinations increases, conventionally, it has been necessary to add a function related to the input source or output destination for each application. However, the present invention corresponds to the input source or the output destination. The function can be expanded only by adding a subclass of the input document class 1111 or the output document class 1121. This reduces the amount of work when a new function is added. Further, at this time, by correcting the correspondence between the user request 1102a, the input document type 1102b, and the output document type 1102c held by the user document object 1102A, the display corresponding to the user request 1102a in the prevailing correspondence By adding to the interface, it is possible to provide an interface that does not disrupt the user when the function is expanded.

  As described above, the document processing apparatus, the image forming apparatus, and the document processing program according to the present invention are useful as a technique for sharing document processing, and are particularly suitable for users when document processing is shared. It is suitable for technology that provides an interface for processing.

1 is a network diagram for explaining a network environment surrounding a multifunction peripheral according to an embodiment. 1 is a block diagram illustrating a hardware configuration of a multifunction machine according to an embodiment. FIG. 3 is a conceptual diagram for explaining a relationship between software and hardware of a multifunction machine according to an embodiment. FIG. 3 is a diagram illustrating an example of an operation panel of the multifunction peripheral according to the embodiment. 3 is an explanatory diagram illustrating an internal configuration of an integrated application of the multifunction peripheral according to the embodiment and a position of a document handling unit in the integrated application. FIG. It is a UML class diagram about each subsystem shown as an internal structure of the integrated application of the multifunctional device which concerns on embodiment. 3 is a conceptual diagram illustrating a concept of processing performed in a document handling unit included in the multifunction peripheral according to the embodiment. FIG. It is the conceptual diagram which showed the concept of the structure for managing an input document and an output document in embodiment. It is explanatory drawing which showed the change of the structure from the input document used by the document processing which concerns on embodiment to a user document, and an output document. FIG. 5 is a conceptual diagram illustrating a concept of processing from a request from a user of a multifunction peripheral according to an embodiment to determination of an input source and an output destination. It is the figure which showed the class structure of the document handling part designed by object modeling by the class of UML. It is the figure which showed an example of matching with the user request | requirement which the user document class which concerns on embodiment hold | maintains, the kind of input document, and the kind of output document. It is the figure which showed the example of a screen of the liquid crystal touch panel displayed when the copy server key of an operation panel is pressed. It is the figure which showed the example of a screen of the liquid crystal touch panel displayed when the scanner key of an operation panel is pressed down. It is the figure which showed the example of a screen of the liquid crystal touch panel displayed in the modification of this Embodiment. It is explanatory drawing which showed the process until it produces | generates the output document of "4 in 1" from the input document of "2 in 1" in the document handling part which concerns on embodiment. It is a UML sequence diagram showing a processing procedure until the document handling unit according to the embodiment inputs a paper document and an electronic document stored in the local storage. It is a UML sequence diagram showing a processing procedure until the document handling unit according to the embodiment outputs a paper document and an electronic document stored on the local storage. FIG. 10 is an explanatory diagram showing job types for each application in a conventional multifunction peripheral. FIG. 10 is an explanatory diagram in which jobs provided for each application in a conventional multifunction peripheral are classified by input and output. FIG. 6 is an explanatory diagram for explaining a transition of a software configuration installed in a multifunction peripheral. It is explanatory drawing for demonstrating the relationship between the software of the conventional multifunction peripheral, and hardware.

Explanation of symbols

1 MFP 10 Controller 11 CPU
12 System memory (MEM-P)
12a ROM
12b RAM
13 North Bridge (NB)
14 South Bridge (SB)
15 AGP bus 16 ASIC
17 Local memory (MEM-C)
18 Hard disk drive (HDD)
20 Operation unit 30 FCU
40 USB
50 IEEE 1394 interface 60 Engine unit 100, 100A Software 101, 101A Application layer 102 Service layer 102a Scanner control unit 102b Plotter control unit 102c Storage control unit 102d Distribution / mail transmission / reception control unit 102e FAX transmission / reception control unit 102f Network communication control unit 102g Other Control unit 103 Operating system 110 Integrated application 121 Copy application 122 Scanner application 123 Fax application 124 Printer application 150 Hardware 151 Hardware resource 151a Scanner 151b Plotter 151c HDD
151d Network 151e Other Resources 201 Operation Subsystem 202 Management Subsystem 203 Execution Subsystem 211 Request Management Unit 212 Document Handling Unit 213 Execution Control Unit 400 Operation Panel 401 Initial Setting Key 402 Copy Key 403 Copy Server Key 404 Printer Key 405 Transmission key 406 Numeric keypad 407 Clear / stop key 408 Start key 409 Preheating key 410 Reset key 411 Scanner key 420 LCD touch panel 1101 Document operation scheduler class 1101a Registration ()
1101A Document operation scheduler object 1102 User document class 1102 a User request 1102 b Input document type 1102 c Output document type 1102 d Input / output timing 1102 e Start ()
1102f End notification ()
1102A User document object 1103 User image class 1103a Create ()
1103b Use ()
1103A User image object 1111 Input document class 1111a Number of pages 1111b Start input ()
1111c Add page ()
1111d End notification ()
1112 Input page class 1112a Page number 1112b Start input ()
1112c End notification ()
1112A Input page object 1113 Input layout class 1113a Layout creation ()
1113A input layout object 1114 input image class 1114a input start ()
1114A Input Image Object 1115 Input Net Document Class 1115A Input Net Document Object 1116 Input Paper Document Class 1116a Number of Sheets 1116b Check for Next Document ()
1116A Input paper document object 1117 Input LS document class 1117A Input LS document object 1121 Output document class 1121a Number of pages 1121b Start output ()
1121c Add page ()
1121d End notification ()
1122 Output page class 1122a Page number 1122b Start output ()
1122c End notification ()
1122A Output page object 1123 Output layout class 1123a Layout creation ()
1123A Output layout object 1124 Output image class 1124a Output start ()
1124A output image object 1125 output net document class 1125A output net document object 1126 output paper document class 1126A output paper document object 1127 output LS document class 1127A output LS document object 1301 “document name” field 1302 “read original” button 1401 Display field 1402 “Stored document” button 1801 Application before service layer separation 1802 Application after service layer separation 1803 Common routine separation application 1804 Object-oriented application

Claims (5)

In a document processing apparatus provided with a plurality of input means for input processing of document information and output means for output processing of document information,
An input document means that is capable of generating and managing a plurality of pieces of document information associated with each input means to be controlled and converted into a predetermined format;
For the input document information managed by the input document means, input page means for managing information for each page;
For each page managed by the input page means, an input layout means for generating and managing input frame information defining the layout of the page; and
For each page managed by the input page means, in accordance with the input frame information managed by the input layout means, an input image to be applied to the page can be generated from the input processed input document, and a plurality of the input images can be managed. Input image means,
User images for each area that can constitute one page are acquired from the input images managed by the input image means, and user image means capable of managing a plurality of the acquired user images;
Associated with each of the output means to be controlled, the user image unit plurality generates document information output process based on the user image is managed output document means making it possible to manage When,
Request information indicating a document processing request received from a user, input document control information indicating whether or not to control the input document means associated with each input means, and correspondence with each output means the output and output document control information indicating whether to control the document means, and manages association was, when receiving a user or RaKaname determined information, received該要 determined information and the said association Identifying the input document means and the output document means to be controlled from, and generating the specified input document means and the output document means to control the user document means,
A document processing apparatus comprising: An input paper document unit that includes a function of the input document unit and that processes a paper document;
An input electronic document means that includes the function of the input document means, and that processes an electronic document stored in a storage medium;
An input communication document means that includes the function of the input document means and that processes an electronic document from a communication line;
The user document means receives document processing request information received from a user, input paper document control information indicating whether or not to control the input paper document means, and input indicating whether or not to control the input electronic document means. When electronic document control information is managed in association with input communication document control means indicating whether or not to control the input communication document means, and when the user request information is received, the user request information and the correspondence 2. The document processing according to claim 1, wherein control is performed after specifying any one or more of the input paper document unit, the input electronic document unit, and the input communication document unit to be controlled. apparatus. An output paper document unit that includes the function of the output document unit and outputs the paper document;
An output electronic document unit that includes the function of the output document unit and outputs the electronic document to a storage medium;
An output communication document means that includes the function of the output document means, and outputs the electronic document to a communication line;
The user document means receives document processing request information received from a user, output paper document control information indicating whether or not to control the output paper document means, and output indicating whether or not to control the output electronic document means. When electronic document control information and output communication document control information indicating whether to control the output communication document means are managed in association with each other and the user request information is received, the user request information and the correspondence The control is performed after specifying any one or more of the output paper document means, the output electronic document means, and the output communication document means to be controlled. Document processing device. In an image forming apparatus comprising a plurality of input means for inputting document information and output means for outputting document information,
An input document means that is capable of generating and managing a plurality of pieces of document information associated with each input means to be controlled and converted into a predetermined format;
For the input document information managed by the input document means, input page means for managing information for each page;
For each page managed by the input page means, an input layout means for generating and managing input frame information defining the layout of the page; and
For each page managed by the input page means, in accordance with the input frame information managed by the input layout means, an input image to be applied to the page can be generated from the input processed input document, and a plurality of the input images can be managed. Input image means,
User images for each area that can constitute one page are acquired from the input images managed by the input image means, and user image means capable of managing a plurality of the acquired user images;
Associated with each of the output means to be controlled, the user image unit plurality generates document information output process based on the user image is managed output document means making it possible to manage When,
Request information indicating a document processing request received from a user, input document control information indicating whether or not to control the input document means associated with each input means, and correspondence with each output means the output and output document control information indicating whether to control the document means, and manages association was, when receiving a user or RaKaname determined information, received該要 determined information and the said association Identifying the input document means and the output document means to be controlled from, and generating the specified input document means and the output document means to control the user document means,
An image forming apparatus comprising: In a document processing program comprising a plurality of input means for input processing of document information and output means for output processing of document information,
An input document means that is capable of generating and managing a plurality of pieces of document information associated with each input means to be controlled and converted into a predetermined format;
For the input document information managed by the input document means, input page means for managing information for each page;
For each page managed by the input page means, an input layout means for generating and managing input frame information defining the layout of the page; and
For each page managed by the input page means, in accordance with the input frame information managed by the input layout means, an input image to be applied to the page can be generated from the input processed input document, and a plurality of the input images can be managed. Input image means,
User images for each area that can constitute one page are acquired from the input images managed by the input image means, and user image means capable of managing a plurality of the acquired user images;
Associated with each of the output means to be controlled, the user image unit plurality generates document information output process based on the user image is managed output document means making it possible to manage When,
Request information indicating a document processing request received from a user, input document control information indicating whether or not to control the input document means associated with each input means, and correspondence with each output means the output and output document control information indicating whether to control the document means, and manages association was, when receiving a user or RaKaname determined information, received該要 determined information and the said association Identifying the input document means and the output document means to be controlled from, and generating the specified input document means and the output document means to control the user document means,
A document processing program characterized by comprising:

Images