JP2007124151A - Image processing apparatus, and image processing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology for performing an image management so that any of stored images can be outputted depending on its purpose of use. <P>SOLUTION: This MFP 101 generates a plurality of kinds of image information items on the basis of acquired images, and generates document information of the XML form for describing respective generated image information items. Upon the receipt of a request from PCs 102 to 104 as to the acquired images, the MFP 101 acquires image information in response to the request by using the document information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an image processing technique.

2. Description of the Related Art Conventionally, an image processing apparatus (hereinafter, MFP) such as a digital copying machine has a function of storing document image data read by a scanner or data transmitted from a host computer in a storage medium such as an MFP hard disk. It has been. The stored data can be output from the printer of its own device as necessary, and can be transmitted via a network, which is very convenient.
JP 2002-059593 A

  However, conventionally, image data stored in the MFP can only be displayed, transmitted, and printed in a predetermined data format, and displayed, transmitted, and printed in another data format desired by the user. Such a thing could not be easily realized. For example, thumbnails for displaying images, JPEG data for transmission, raster data for printing, and the like are determined in advance, and it has not been possible to easily create another data format. For example, it has not been possible to display, transmit, and print only the character code of the character area of the image data.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a technique for performing image management so that a retained image can be output according to the purpose of use.

  In order to achieve the object of the present invention, for example, an image processing apparatus of the present invention comprises the following arrangement.

That is, acquisition means for acquiring an image,
First generation means for generating a plurality of types of image information based on the acquired image;
Second generation means for generating document information in XML format describing each piece of image information generated by the first generation means;
And processing means for acquiring image information corresponding to the request using the document information when a request is received from the outside for the image acquired by the acquisition means.

  In order to achieve the object of the present invention, for example, an image processing method of the present invention comprises the following arrangement.

That is, an acquisition step of acquiring an image,
A first generation step of generating a plurality of types of image information based on the acquired image;
A second generation step of generating document information in XML format describing each piece of image information generated in the first generation step;
A processing step of acquiring image information according to the request using the document information when a request is received from the outside for the image acquired in the acquisition step.

  According to the configuration of the present invention, it is possible to perform image management so that the held image can be output according to the purpose of use.

  Hereinafter, the present invention will be described in detail according to preferred embodiments with reference to the accompanying drawings.

[First Embodiment]
In the present embodiment, a technique for performing the following processing in a system in which a host computer and an image processing apparatus (hereinafter referred to as MFP: MFP) are connected via a transmission medium such as a network will be described. That is, image data (scan data) of a document read by a scanner included in the MFP, data (application data) received from a host computer, and the like are stored in a storage device included in the MFP as XML-format structured document data (XML data). . Then, the XML data is handled using XSLT corresponding to the operation and command from the host computer.

  FIG. 1 is a diagram illustrating a configuration of a system used in the present embodiment. As shown in the figure, the system according to the present embodiment has a configuration in which an MFP 101 having a network communication function and host computers (hereinafter referred to as PCs) 102 to 104 are connected by a transmission medium such as a network 105.

  In the figure, reference numeral 106 denotes a large-capacity information storage device (box) represented by a hard disk drive device, which stores data received from the PCs 102 to 104, image data read by the scanner of the MFP 101, and the like. it can. Note that data input to the MFP 101 in various forms is stored in the storage device 106 as image data. At that time, as indicated by 107, it is stored in the storage device 106 as a set with the assigned unique ID (BOX-ID). Note that the image is stored after being subjected to a specific compression defined in the MFP 101.

  Reference numeral 110 denotes a series of transmission processes for transmitting application data 108 created using an application installed on the PC 102 (for creating a document, creating a table, etc.) to the MFP 101 for printing.

  Reference numeral 111 denotes a series of processing for reading a paper document 109 by a scanner included in the MFP 101 and saving image data as a result of the reading to the storage device 106.

  Reference numeral 112 denotes a series of processes for remotely controlling the MFP 101 using the Remote UI for performing remote operation from the PC 103.

  Reference numeral 113 denotes a series of processes for transmitting image data stored in the storage device 106 to the PC 104 using, for example, the above-described Remote UI. At this time, as described above, since the image data stored in the storage device 106 has been subjected to a specific compression process defined in the MFP 101, the image data is once expanded. Then, for example, compression processing is performed by a general color image compression method (JPEG), and the data is transmitted to the PC 104. The image transmitted to the PC 104 can be viewed with a general-purpose viewer that the PC 104 has.

  Next, the MFP 101 will be described. FIG. 2 is a block diagram illustrating a hardware configuration of the MFP 101. The MFP 101 roughly includes a scanner unit 201 as an image input device, a printer unit 202 as an image output device, a control unit 204 configured with a CPU, a memory, and the like, and an operation unit 203 as a user interface. ing.

  First, the operation unit 203 will be described. The operation unit 203 is, for example, a display device in a touch panel format, and displays various GUIs (graphical user interfaces). When the user instructs on the screen with his / her fingers or pointing tools, the result of the instruction is displayed. The CPU 205 is notified.

  Next, the control unit 204 will be described. The control unit 204 is connected to each of the scanner unit 201, the printer unit 202, and the operation unit 203. On the other hand, it is connected to a LAN 219 and a public line (WAN) 220 which is a general telephone line network. Thereby, the control unit 204 functions as a controller that inputs and outputs image information and device information. Next, each part which comprises the control unit 204 is demonstrated.

  The CPU 205 controls each part of the MFP 101 so as to control the entire MFP 101 and executes processes described below performed by the MFP 101.

  The RAM 206 has an area for temporarily storing various data input from the outside via the scanner unit 201, the network I / F 208, the modem 209, and the like. The RAM 206 also has an area for temporarily storing programs and data loaded from an HDD (Hard Disk Drive Device) 211. The RAM 206 also has a work area used when the CPU 205 executes various processes. As described above, the RAM 206 can provide various areas as appropriate.

  A ROM 210 is a boot ROM, and stores a boot program of the MFP 101, data related to booting, and the like.

  The HDD 211 is a hard disk drive device, and can appropriately store an OS (Operating System) and programs and data for causing the CPU 205 to execute various processes described later. Also, the HDD 211 can store various data input from the outside via the scanner unit 201, the network I / F 208, the modem 209, and the like. The HDD 211 also functions as the storage device 106 shown in FIG.

  The operation unit I / F 207 functions as an interface with the operation unit 203. That is, screen data to be displayed on the operation unit 203 is output to the operation unit 203. In addition, the CPU 205 is notified of instruction information input by the user of the MFP 101 from the operation unit 203.

  The network I / F 208 functions as an interface for connecting the MFP 101 to the LAN 219 and inputting / outputting packet format information.

  A modem 209 functions as an interface for connecting the MFP 101 to the public line 220, performing demodulation / modulation of information, and performing input / output.

  Each unit described above is connected to the system bus 221.

  The image bus I / F 212 is a bus bridge that connects the system bus 221 and the image bus 222 that transfers image data at high speed and converts the data structure. The image bus 222 is composed of, for example, a PCI bus or IEEE1394.

  The following devices are connected on the image bus 222.

  A raster image processor (RIP) 213 analyzes the PDL code and develops it into a bitmap image. The device I / F 214 connects the scanner unit 201 which is an image input / output device via the signal line 223 and the printer unit 202 via the signal line 224 to the control unit 204, respectively. Perform conversion. A scanner image processing unit 215 corrects, processes, and edits input image data. The printer image processing unit 216 performs correction, resolution conversion, and the like according to the printer unit 202 for print output image data to be output to the printer unit 202. The image rotation unit 217 rotates the input image data and outputs it. The image compression unit 218 performs JPEG compression / decompression processing on multi-valued image data or device-specific compression / decompression processing, and JBIG, MMR, and MH compression / decompression processing on binary image data. .

  Next, a software configuration installed in the control unit 204 in FIG. 2 will be described with reference to FIG. Note that software programs and data having the configuration as shown in the figure are stored in the HDD 211, appropriately loaded into the RAM 206, and processed by the CPU 205.

  Reference numeral 301 denotes a user interface (hereinafter referred to as UI), which is a module that mediates between a device and a user operation when the user of the MFP 101 performs various operations / settings on the MFP 101 using the operation unit 203. In accordance with user operations, this module transfers input information to various modules, which will be described later, and requests processing or sets data.

  Reference numeral 302 denotes an address book, which is a database module that manages data transmission destinations, communication destinations, and the like. The contents of the address book 302 are such that operations from the operation unit 203 are detected by the UI 301, data is added, deleted, and acquired, and data sending / communication destination information is given to each module described later by the operator's operation. It is what is used.

  A Web server module 303 is used to notify management information of the MFP 101 in response to a request from a Web client (for example, the PC 102). This management information is read via an integrated transmission unit 304 described later, a remote copy scan module 309 described later, a remote copy print module 310 described later, and a control API 318 described later. Then, the Web client is notified via an HTTP module 312, a TCP / IP communication module 316, and a network driver 317 described later. The Web server module 303 creates information to be passed to the Web client as data in a so-called Web page (homepage) format such as an HTML format. Java (registered trademark), a CGI program, or the like is used as necessary.

  An integrated transmission unit 304 is a module that manages data distribution. The integrated transmission unit 304 distributes data designated by the user via the UI 301 to a designated communication (output) destination. When the user instructs the generation of distribution data using the scanner function of the MFP 101, the scanner 201 is operated via a control API 318 described later to generate data.

  A module 305 is executed when a printer is designated as an output destination in the integrated transmission unit 304. Reference numeral 306 denotes a module that is executed when an E-mail address is designated as a communication destination in the integrated transmission unit 304. A module 307 is executed when a database is designated as an output destination in the integrated transmission unit 304. A module 308 is executed when an MFP similar to the MFP 101 is designated as an output destination in the integrated transmission unit 304.

  Reference numeral 309 denotes a remote copy scan module. That is, the output function of the image information read by the scanner 201 using the scanner function of the MFP 101 is output by a printer of another MFP connected via a network or the like, and the same processing as the copy function realized by the MFP 101 alone is performed. Module to perform.

  Reference numeral 310 denotes a remote copy print module. That is, the image information obtained using the image information read by the scanner of another MFP connected via a network or the like as an input source is output using the printer function of the MFP 101. Accordingly, processing equivalent to the copy function realized by the MFP 101 alone is performed.

  The box module 311 stores the scanned image or PDL print image in the HDD 211. Then, management functions such as printing of the stored image by the printer function, transmission by the integrated transmission function, deletion of the document stored in the HDD 211, grouping (storage in the individual BOX), movement between BOX, and copying between BOX are provided. The box module 311 is provided with a communication function by the HTTP module 312 and the TCP / IP module 316.

  Reference numeral 312 denotes an HTTP module, which is used when the MFP 101 communicates by HTTP, and provides a communication function to the Web server module 303 and the Web pull print module 311 by the TCP / IP communication module 316 described later.

  Reference numeral 313 denotes an lpr module, which provides a communication function to the module 305 in the integrated transmission unit 304 described above by a TCP / IP communication module 316 described later. An SMTP module 314 provides a communication function to the E-mail module 306 in the integrated transmission unit 304 by a TCP / IP communication module 316 described later. Reference numeral 315 denotes an SLM, that is, a Salutation-Manager module. That is, a communication function is provided to the database module 307, the DP module 308, the remote copy scan module 309, and the remote copy print module 310 in the integrated transmission unit 304 by the TCP / IP communication 316 module described later.

  A TCP / IP communication module 316 provides a network communication function to the various modules described above using a network driver 317 described later. Reference numeral 317 denotes a network driver that controls a portion physically connected to the network.

  Reference numeral 318 denotes a control API, which provides an upstream module such as the integrated transmission unit 304 with an interface with a downstream module such as a job manager 319 described later. That is, the dependency relationship between the upstream and downstream modules is reduced, and the respective diversion properties are improved.

  A job manager 319 interprets processing instructed from the various modules described above via the control API 318, and gives instructions to each module (320, 324, 326) described later. The job manager 319 centrally manages various jobs executed in the MFP 101 including control of FAX jobs.

  A CODEC manager 320 manages and controls various compression / decompression of data in the process instructed by the job manager 319. Reference numeral 323 denotes an FBE encoder module which compresses data read by a scan process executed by a job manager 319 and a scan manager 321 described later in the FBE format.

  Reference numeral 324 denotes a JPEG codec module (JPEG-CODEC). That is, in the scan process executed by the job manager 319 and the scan manager 321 and the print process executed by the print manager 322, the JPEG compression of the read data and the JPEG expansion process of the print data are performed.

  Reference numeral 325 denotes an MMR codec (MMR-CODEC). In the scan process executed by the job manager 319 and the scan manager 321 and the print process executed by the print manager 326, MMR compression of data read from the scanner and MMR expansion process of print data to be output to the printer are performed.

  Reference numeral 321 denotes a scan manager, which manages and controls scan processing instructed by the job manager 319. Reference numeral 326 denotes a SCSI driver, which communicates with the scanner unit 201 to which the scan manager 321 and the MFP 101 are internally connected. A print manager 322 manages and controls print processing instructed by the job manager 319.

  Reference numeral 327 denotes an engine interface (Engine I / F) that provides an I / F between the print manager 322 and the printer unit 202. A parallel port driver 328 provides an I / F when the Web pull print 311 outputs data to an output device (not shown) via the parallel port.

  Next, details of the Address-Book 302 will be described. The Address-Book 302 is stored in a non-volatile storage device (non-volatile memory, hard disk, or the like) in the MFP 101, and in this, features of other devices connected to the network are described. For example, those listed below are included.

-Official device name or alias name-Device network address-Device processable network protocol-Device processable document format-Device processable compression type-Device processable image resolution-Printer device Paper size that can be fed, and paper feed stage information-Folder name in which documents can be stored in the case of a server (computer) device Each application described below uses the information described in the above Address-Book 302 to determine the characteristics of the delivery destination Can be determined.

  With reference to the Address-Book 302, the MFP 101 can transmit data. For example, the remote copy application discriminates resolution information that can be processed by the device designated as the distribution destination from the Address-Book 302, and compresses the binary image read by the scanner by using known MMR compression. . Then, it is converted into a known TIFF (Tagged Image File Format), passed through the SLM 315, and transmitted to the printer device on the network. Although not described in detail, the SLM 315 is a kind of network protocol including device control information called a known Salutation-Manager.

  Next, the PCs 102 to 104 in FIG. 1 will be described. FIG. 4 is a block diagram illustrating a hardware configuration of a computer applicable to the PCs 102 to 104. Note that each of the PCs 102 to 104 need not have the same configuration, and may be configured such that additional hardware is added based on the configuration shown in FIG.

  The monitor 401 is composed of a CRT, a liquid crystal screen, and the like, and displays the processing result by the CPU 403 using images, characters, and the like.

  As is well known, the keyboard / mouse 402 can be operated by an operator of the computer to input various instructions to the CPU 403.

  The CPU 403 controls the entire computer using programs and data loaded in the memory 405 and executes each process described below performed by the PCs 102 to 104 to which the computer is applied.

  The hard disk 404 stores programs and data for causing the CPU 403 to execute processes described below performed by the OS and the PCs 102 to 104 to which the computer is applied, and these are loaded into the memory 405 as appropriate under the control of the CPU 403. The

  A network interface 406 is for connecting the computer to the network 105. The computer performs data communication with each device (including the MFP 101) connected to the network 105 via the network interface 406.

  Next, a process for storing image data (scan data) of a document read by the scanner unit 201 of the MFP 101 and data (application data) transmitted from the PCs 102 to 104 in the HDD 211 of the MFP 101 will be described.

  FIG. 5 is a flowchart of processing for storing image data of a document read by the scanner unit 201 of the MFP 101, data transmitted from the PCs 102 to 104, and the like in the HDD 211.

  First, image data of a document read by the scanner unit 201 is acquired in the RAM 206 via the device I / F 214 (step S501). The CPU 205 controls the scanner image processing unit 215 to perform image processing such as color conversion on the image data (step S502). If application data is received from any of the PCs 102 to 104 via the network I / F 208 in step S501, in step S502, image data is created based on this data, and appropriate image processing is performed to the RAM 206. Store again.

  Next, the CPU 205 creates thumbnail image data of the image data using the image data that has been subjected to image processing in step S502 (step S503). The CPU 205 also controls the image compression unit 218 to create compressed image data using the image data that has been subjected to image processing in step S502 (step S504). The compression processing here includes compression processing using a compression method unique to the MFP 101 and compression processing using a compression method that does not depend on the MFP 101. The compression process in step S504 will be described later.

  Next, the CPU 205 creates XML data (step S505). This XML data describes one or more of the data created in steps S503 and S504. Therefore, if the image to be described in the XML data is determined in advance, only this image should be obtained (for example, if the compressed image data is not described in the XML data, the process in step S504 is omitted). May be). The XML data creation process in step S505 will be described later.

  Then, the CPU 205 saves the XML data and the image data (image data described in the XML data) in the HDD 211 (step S506).

  In addition to the image acquisition process in step S501, an image area separation process for specifying a character area, a photograph area, or a graphic area in the acquired image may be performed. Further, a character recognition process (hereinafter referred to as OCR) for recognizing a character code, a vectorization process for generating vector data, a JPEG compression process for generating transmission data in advance, and the like may be performed. When these processes are performed, the respective results are reflected in the XML data, and the XML data can be effectively used later.

  Through the processing described above, the structured document (XML data) in the XML format and the image data are stored in the HDD 211.

  6 to 8 are diagrams illustrating the structure of the XML data created in step S505. Although the three structural examples shown in FIGS. 6 to 8 are shown here, the tagging method of the XML data structure and the hierarchical structure of each element are not limited to this, and can be modified as appropriate. Also good.

  FIG. 6 shows the configuration of XML data in which link information is described for the thumbnail image data created in step S503 and the compressed image data obtained by compressing the image data processed in step S502 in step S504 using the compression method unique to the MFP 101. It is a figure which shows an example.

  This figure shows XML data (test1.xml) 601, thumbnail image data (binary data) 604 created in step S503, and compressed image data (binary data) 605 generated in step S504. In the XML data, link information for binary data 604 is described in a portion indicated by 602, and link information for binary data 605 is described in a portion indicated by 603.

  More specifically, the portion indicated by 602 describes “storage location information (link information) of binary data 604 in HDD 211” enclosed by thumbnail tag <thumbnail>. In a portion indicated by 603, “storage location information (link information) of binary data 605 in the HDD 211” surrounded by the image tag <image> is described.

  Therefore, when the XML data shown in FIG. 6 is created, in step S504, compressed image data is generated by the compression method unique to the MFP 101 for the image data that has undergone image processing in step S502. In step S506, the XML data, thumbnail image data, and compressed image data generated in step S504 are stored in the HDD 211.

  FIG. 7 is a diagram illustrating a configuration example of XML data in which the binary data 604 of the thumbnail image data created in step S503 and the binary data 605 of the compressed image data generated in step S504 are embedded.

  In this case, the XML data is composed of a single file 701 of XML data (test2.xml). In the XML data, binary data 604 is embedded in a portion indicated by 702, and binary data 605 is embedded in a portion indicated by 703.

  More specifically, binary data 604 surrounded by a thumbnail tag <thumbnail> is embedded in a portion indicated by 702. Also, binary data 605 surrounded by an image tag <image> is embedded in a portion indicated by 703.

  Various methods are conceivable for embedding binary data in XML data. For example, a method of describing binary data directly in XML data, a method of embedding binary data by text conversion using base64, and the like are conceivable.

  Therefore, when the XML data shown in FIG. 7 is created, in the flowchart of FIG. 5, in step S504, compressed image data is generated by the compression method unique to the MFP 101 for the image data that has undergone image processing in step S502. In step S506, the binary data of the thumbnail image data is embedded in the XML data, the binary data of the compressed image data obtained in step S504 is embedded, and the XML data in which these are embedded is stored in the HDD 211.

  FIG. 8 is a diagram showing a configuration example of XML data 801 in which character code data and JPEG compressed image data are further embedded in the XML data shown in FIG. That is, the XML data 801 is obtained by performing the following processing in addition to the processing for creating the XML data shown in FIG.

  That is, in the flowchart of FIG. 5, in addition to the image acquisition process in step S501, the character code data of each character in the acquired image is acquired by the OCR process. In step S504, JPEG compression image data is created by JPEG compression of the image data that has been processed in step S502. The generated character code data and JPEG compressed image data are embedded in the XML data.

  In step S506, character code data and JPEG compressed image data are embedded in the XML data in addition to the binary data of thumbnail image data and the binary data of the compressed image data obtained in step S504. Then, the XML data in which these are embedded is stored in the HDD 211.

  In this XML data, binary data 604 is embedded in a portion indicated by 802, and character code data obtained by OCR processing is embedded in a portion indicated by 803. Also, JPEG compressed image data is embedded in a portion indicated by 804, and binary data 605 is embedded in a portion indicated by 805.

  Here, the difference between JPEG compressed image data and binary data 605 will be described. The JPEG compressed image data is also binary image data, similar to the binary data 605. However, as described above, since the binary data 605 has been subjected to device-specific compression processing, for example, this data cannot be directly transmitted to a host computer or the like.

  On the other hand, JPEG compressed image data is data that can be viewed with a general-purpose viewer. Further, the binary data 605 has a feature that can maintain an image quality close to that of the original data (scan data) depending on the capacity of the storage device of the device. However, since the JPEG compressed image data is generated as transmission data, the data size is generally small and the image quality is deteriorated.

  In this way, as shown in FIGS. 6 to 8, when creating XML data in which various image information is embedded in XML data or link information for various image information is described, there are various kinds of image information. There is. Each of them corresponds to a request from the outside described later.

  Therefore, when creating XML data, image information corresponding to the request is first created, and each created image information is embedded in the XML data, or link information for each image information is described in the XML data. .

  In the following description, it is assumed that the XML data 801 shown in FIG. 8 has been created, but the essence of the following description is not limited to handling such XML data 801.

  Next, a description will be given of processing to be performed to acquire information corresponding to an external request among a plurality of types of image information described in the XML data 801 created as described above.

  FIG. 9 shows a process for acquiring image information corresponding to each purpose by converting the XML data 801 into data suitable for each purpose by using XSLT for display, transmission, and printing. It is a figure explaining the flow of.

  Here, “display” represents, for example, an operation of browsing images stored in the storage device 106 of the MFP 101 as thumbnails from the PCs 102 to 104. “Transmission” represents an operation of transmitting an image stored in the storage device 106 of the MFP 101 to the PCs 102 to 104. “Print” represents an operation of printing an image stored in the storage device 106 of the MFP 101 from the printer unit 202 of the MFP 101.

  Reference numeral 901 denotes XML data stored in the storage device 106 of the MFP 101. Reference numeral 902 denotes an XSLT processor, which is a program for performing processing for converting XML data 901 into a desired data format using XSLTs 903 to 905 described later. With this program, it is possible to freely convert an XML document into HTML, plain text, an arbitrary XML document, and the like. Microsoft® MSXML, Apache. org's Xalan and Jim Clarks's XT are known.

  Reference numeral 903 denotes an XSLT for converting the XML data 901 into display data. Reference numeral 904 denotes an XSLT for converting the XML data 901 into transmission data. Reference numeral 905 denotes an XSLT for converting to print data.

  Each of the XSLTs 903 to 905 is stored in the HDD 211 as a data file, and can be updated as appropriate.

  The functions of the respective XSLTs 903 to 905 are shown in FIG.

  As shown in the figure, the display XSLT 903 has a function of converting the XML data 901 in order to obtain display image information among a plurality of types of image information in the XML data 901.

  Therefore, when the CPU 205 executes the XSLT processor 902 using the display XSLT 903, first, a portion surrounded by <thumbnail> is searched in the XML data 901. Then, the binary data of the searched part is acquired. The acquired binary data is formatted in XML or HTML, and is output to the HDD 211 as XML data or HTML data. In FIG. 9, the XML data 906 is this output data. Accordingly, the XML data 906 generated in this way becomes XML data of thumbnail images that can be viewed from the PCs 102 to 104.

  Further, as shown in the figure, the transmission XSLT 904 has a function of converting the XML data 901 in order to acquire transmission image information among a plurality of types of image information in the XML data 901.

  Therefore, when the CPU 205 executes the XSLT processor 902 using the transmission XSLT 904, first, the portion surrounded by <jpeg> is searched in the XML data 901. Then, the binary data of the searched part is acquired. The acquired binary data is formatted in XML or HTML, and is output to the HDD 211 as XML data or HTML data. In FIG. 9, the XML data 907 is this output data. Accordingly, the XML data 907 generated in this way becomes XML data of an image suitable for transmission to the PCs 102 to 104.

  Further, as shown in the figure, the printing XSLT 905 has a function of converting the XML data 901 in order to obtain printing image information among a plurality of types of image information in the XML data 901.

  Therefore, when the CPU 205 executes the XSLT processor 902 using the printing XSLT 905, first, the portion surrounded by <image> is searched in the XML data 901. Then, the binary data of the searched part is acquired. The acquired binary data is formatted in XML or HTML, and is output to the HDD 211 as XML data or HTML data. In FIG. 9, the XML data 908 is the output data, but the output data may be in the form of binary data. Accordingly, the XML data 908 generated in this way becomes XML data of an image suitable for printing in the printer unit 202.

  Next, the Remote UI will be described. As described with reference to FIG. 3, the RemoteUI is a function that realizes remote operation by performing HTTP communication with a Web server included in the MFP 101 using a Web browser of the PC and the PC serving as a Web client. First, the Remote UI of the PC is activated and the connection to the MFP 101 is performed by inputting the IP address of the MFP 101.

  FIG. 14 is a diagram illustrating a screen state when a user box is viewed on the Remote UI at that time. Here, the user box means a box in the storage device 106 of the MFP 101. Each button (display, send, print, delete) 1401 in FIG. 14 indicates an operation / command for a file stored in a box as indicated by 1402. Reference numeral 1402 denotes each file stored in the box and its information, and displays a selection field, a document, a document name, a paper size, a page, a date, and the like. Here, the document names file1 and file2 displayed at 1402 are files corresponding to the BOX-ID 0001 and BOX-ID 0002 of the box data 107 in FIG. 1, respectively.

  Next, when the above-described Remote UI is used, the MFP 101 performs an operation / command (hereinafter, request) such as display, transmission, and printing for a file (image data) stored in the HDD 211 from the PC. Processing will be described with reference to FIG. FIG. 10 is a flowchart of such processing.

  First, the PC user activates the Remote UI of the PC and transmits a request (request) to desired image data among the image data stored in the HDD 211 of the MFP 101. Accordingly, the CPU 205 of the MFP 101 checks whether or not a request has been received from the PC (step S1001). If received, the process proceeds to step S1002 to check whether or not the type of this request is “display”. (Step S1002).

  If the request type is “display”, the process advances to step S1003. Then, the CPU 205 operates the XSLT processor 902 to generate display data (in the case of FIG. 9, XML data 906) from the XML data in which the desired image data is embedded using the display XSLT 903 (step S1003). ). Then, the generated display data is returned to the PC (step S1004).

  On the other hand, if the request type is not “display” in the check process in step S1002, the process proceeds to step S1005 to check whether the request type is “transmission” (step S1005).

  As a result of the check, if the request type is “transmission”, the process advances to step S1006. Then, the CPU 205 operates the XSLT processor 902 to generate transmission data (in the case of FIG. 9, XML data 907) from the XML data in which the desired image data is embedded using the transmission XSLT 904 (step S1006). ). Then, the generated transmission data is returned to the PC (step S1007).

  On the other hand, if it is determined in step S1005 that the request type is not “transmission”, the process advances to step S1008 to check whether the request type is “print” (step S1008).

  As a result of the check, if the request type is “print”, the process advances to step S1009. Then, the CPU 205 operates the XSLT processor 902 to generate print data (in the case of FIG. 9, XML data 908) from the XML data in which the desired image data is embedded using the print XSLT 905 (step S1009). ). The generated print data is output to the printer unit 202 (step S1010).

  As described above, according to the present embodiment, XML data can be easily handled by switching the XSLT in response to an external request.

[Second Embodiment]
In the first embodiment, XML data is converted using XSLTs 903 to 905 stored in the HDD 211. However, there is a problem that only the functions of XSLTs 903 to 905 cannot flexibly cope with a document having a more complicated XML data structure. Therefore, in the present embodiment, for each request from the PC, a new XSLT (XSLT ′) is dynamically generated based on the existing XSLT, and the generated XSLT ′ is used to obtain more XML data. A method for flexible handling will be described.

  FIG. 11 is a diagram illustrating an example of image data used in the present embodiment. Therefore, in the present embodiment, such image data is stored in the HDD 211 as image data of a document read by the scanner unit 201 of the MFP 101 or image data based on data transmitted from the PCs 102 to 104.

  Here, when this image data is stored in the HDD 211, it is assumed that an image area separation process for specifying a character area, a photograph area, and a graphic area in this image is performed. In addition to this, character recognition processing (hereinafter referred to as OCR) for recognizing character codes, vectorization processing for generating vector data, JPEG compression processing for generating transmission data in advance, and the like are performed. It shall be. In the figure, reference numerals 1102 to 1104 denote areas that are identified as a character area, a graphic area, and a photograph area in order in the image area separation process.

  In addition, the rectangle and other information of each area are shown below.

■ Character area 1102
The upper left coordinates (x, y) are (x1, y1)
The region size (width, height) is (w1, h1)
Other OCR information (character code)
■ Graphic area 1103
The upper left coordinate (x, y) is (x2, y2)
Area size (width, height) is (w2, h2)
Other vector information (vector data)
■ Photo area (1104)
The upper left coordinate (x, y) is (x2, y2)
Area size (width, height) is (w2, h2)
Others, JPEG data (Note 1104 JPEG data)
FIG. 12 shows a configuration example of XML data reflecting these processing results. The XML data shown in the figure is assumed to be composed of a single file of an XML file 1201 (test4.xml). In the XML data, binary data of a thumbnail image is embedded in a portion indicated by 1202. In the portion indicated by 1203, the character code of the character area 1102 and information related thereto are embedded. In a portion indicated by 1204, vector data of the graphic area 1103 and information related to the information are embedded. In a portion indicated by 1205, JPEG compressed image data of the photo area 1104 and information related thereto are embedded. In the portions indicated by 1206 to 1208, images in the respective areas 1102 to 1104 and information related thereto are embedded.

  Next, a method for issuing a request (= display) to XML data stored in a box from a PC using the above-described RemoteUI of FIG. When the user selects a file from the selection field 1403 in FIG. 14 and presses a display button 1402, for example, a dialog screen as shown in FIG. 15 is displayed.

  Here, in addition to the normal thumbnail display of the entire area, the user can select items to be displayed for each area. For example, as shown in FIG. 15, it is possible to display only the character code of the character region by selecting the entire region = non-display, the character region = character code, the graphic region = non-display, and the photo region = non-display. It is.

  In the first embodiment, when the request is a display, since the XSLT 903 shown in FIG. 13 is used, only the thumbnail of the entire area can be displayed. Therefore, in the present embodiment, when a request with the designation of displaying the character code of the character area is received, the XSLT 903 ′ having a function of acquiring the character code of the character area from the XML data is dynamically changed based on the XSLT 903. To generate. As a result, the above-described requirement is realized.

  That is, in this example, the XSLT 903 ′ has a function of acquiring binary data surrounded by <thumbnail> tags and a function of acquiring character codes surrounded by <ocr> tags. The function of XSLT 903 'is shown in FIG. The output file inherits the function of XSLT and outputs, for example, HTML data.

  Next, when the above-described Remote UI is used, the MFP 101 performs an operation / command (hereinafter, request) such as display, transmission, and printing for a file (image data) stored in the HDD 211 from the PC. The process will be described with reference to FIG. FIG. 16 is a flowchart of such processing. In the figure, the same parts as those in FIG. 10 are denoted by the same step numbers, and the description thereof is omitted.

  If the request is “display”, the process proceeds to step S1603 via step S1002, and XSLT1 ′ corresponding to the requested display content is created using XSLT1 previously stored in the HDD 211 (step S1003). S1603). In step S1604, display data is created using the created XSLT 1 '(step S1604). Then, the created display data is returned to the PC (step S1605).

  On the other hand, if the request is not “display” but “transmission”, the process proceeds to step S1607 via steps S1002 and S1005. Then, XSLT 2 'corresponding to the requested transmission content is created using XSLT 2 previously held in HDD 211 (step S1607). In step S1608, transmission data is created using the created XSLT 2 '(step S1608). Then, the created transmission data is returned to the PC (step S1609).

  On the other hand, if the request is “print” instead of “display” or “transmission”, the process proceeds to step S1611 via steps S1002, S1005, and S1008. Then, XSLT 3 'corresponding to the requested print content is created using XSLT 3 previously held in HDD 211 (step S1611). In step S1612, print data is created using the created XSLT 3 '(step S1612). The created print data is transmitted to the printer unit 202 (step S1613).

  As described above, according to the present embodiment, for each request from the PC, a new XSLT (XSLT ′) is dynamically generated based on the existing XSLT, and the created XSLT ′ is used. , XML data can be handled more flexibly.

[Third Embodiment]
In the first embodiment, since XML data is created every time it is acquired in the HDD 211, there are problems in that the performance of the MFP 101 is degraded and memory resources are wasted.

  Therefore, in the present embodiment, creation processing of XML data or the like is performed only when the MFP 101 receives each request from the PC. This prevents unnecessary creation of data that does not create XML data as a result. However, once generated XML data or the like is saved.

  In the following description, as an example, when storing image data of a document read by the scanner unit 201 of the MFP 101 or data transmitted from the PCs 102 to 104 in the HDD 211, XML data is not created. Instead, thumbnail image data of this image data and compressed image data compressed by a compression method unique to the MFP 101 are created and stored in the HDD 211.

  FIG. 17 is a flowchart showing the processing performed by the MFP 101 when a transmission command (hereinafter referred to as a request) is issued from the PC to the file (image data) stored in the HDD 211 using the Remote UI. Will be described below.

  When a transmission request is received from the PC, the process proceeds to step S1702 via step S1702, and the CPU 205 reads the compressed image data stored in the HDD 211 and decompresses it (step S1702). Then, JPEG compressed image data is created using the decompressed image data (step S1703). Then, XML data describing link information for the created JPEG compressed image data or XML data in which the created JPEG compressed image data is embedded is created (step S1704). Note that once created XML data may be used later, and in step 1704, the created XML data is further stored in the HDD 211 in order to save the trouble of creating again later.

  Then, the CPU 205 operates the XSLT processor 902 for the created XML data, and creates transmission data using the transmission XSLT (step S1705). Then, the created transmission data is returned to the PC (step S1706).

  As described above, according to the present embodiment, by generating XML data only when the MFP 101 receives each request from the PC, unnecessary XML data is not generated, performance is improved, and Memory resources can be saved.

  Note that processing to be performed at the time of receiving a request from the outside is not limited to this, and processing that need not be performed before receiving the request may be performed after receiving the request.

[Other Embodiments]
Needless to say, the object of the present invention can be achieved as follows. That is, a recording medium (or storage medium) that records a program code of software that implements the functions of the above-described embodiments is supplied to a system or apparatus. Then, the computer (or CPU or MPU) of the system or apparatus reads and executes the program code stored in the recording medium. In this case, the program code itself read from the recording medium realizes the functions of the above-described embodiment, and the recording medium on which the program code is recorded constitutes the present invention.

  Further, by executing the program code read by the computer, an operating system (OS) or the like running on the computer performs part or all of the actual processing based on the instruction of the program code. Needless to say, the process includes the case where the functions of the above-described embodiments are realized.

  Furthermore, it is assumed that the program code read from the recording medium is written in a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer. After that, based on the instruction of the program code, the CPU included in the function expansion card or function expansion unit performs part or all of the actual processing, and the function of the above-described embodiment is realized by the processing. Needless to say.

  When the present invention is applied to the recording medium, program code corresponding to the flowchart described above is stored in the recording medium.

It is a figure which shows the structure of the system used by the 1st Embodiment of this invention. 2 is a block diagram illustrating a hardware configuration of an MFP 101. FIG. It is a block diagram which shows the software structure mounted in the control unit 204 in FIG. FIG. 2 is a block diagram showing a hardware configuration of a computer applicable to PCs 102 to 104. 6 is a flowchart of processing for storing image data of a document read by the scanner unit 201 of the MFP 101, data transmitted from the PCs 102 to 104, and the like in the HDD 211. A configuration example of XML data in which link information is described for the thumbnail image data created in step S503 and the compressed image data obtained by compressing the image data processed in step S502 in step S504 by the compression method unique to the MFP 101 is shown. FIG. It is a figure which shows the structural example of the XML data which embedded the binary data 604 of the thumbnail image data produced | generated by step S503, and the binary data 605 of the compressed image data produced | generated by step S504. FIG. 8 is a diagram illustrating a configuration example of XML data 801 in which character code data and JPEG compressed image data are further embedded in the XML data illustrated in FIG. 7. Describes the flow of processing for acquiring image information according to each purpose by converting the XML data 801 into data suitable for each purpose using XSLT for display, transmission, and printing It is a figure to do. 10 is a flowchart of processing performed by the MFP 101 when an operation / command such as display, transmission, and printing is performed on a file (image data) stored in a box (HDD 211) from a PC using the Remote UI. It is a figure which shows the example of the image data used by the 2nd Embodiment of this invention. It is a figure which shows the structural example of the XML data which concerns on 2nd Embodiment. (A) is a figure which shows the function of XSLT903-905, (b) is a figure which shows the function of XSLT903 '. It is a figure which shows the mode of the screen at the time of browsing a user box on RemoteUI. It is a figure which shows the example of a display of a dialog. 10 is a flowchart of processing performed by the MFP 101 when an operation / command such as display, transmission, and printing is performed on a file (image data) stored in a box (HDD 211) from a PC using the Remote UI. 10 is a flowchart of processing performed by the MFP 101 when a transmission command is issued from a PC to a file stored in the HDD 211 using the Remote UI.

Claims (10)

An acquisition means for acquiring an image;
First generation means for generating a plurality of types of image information based on the acquired image;
Second generation means for generating document information in XML format describing each piece of image information generated by the first generation means;
An image processing apparatus comprising: processing means for acquiring image information corresponding to the request using the document information when a request is received from the outside for the image acquired by the acquisition means . The first generation means includes:
Means for generating a compressed image by compressing the image by a compression method specific to the image processing apparatus as image information used to respond to a print request for the image acquired by the acquisition means;
Means for generating a thumbnail image of the image as image information used to respond to a browsing request for the image acquired by the acquisition means;
Means for generating a compressed image by compressing the image by a JPEG compression method as image information used to respond to a transmission request for the image acquired by the acquisition means;
The image processing apparatus according to claim 1, further comprising: one or more of the above. The second generation unit generates XML format document information describing link information for each piece of image information generated by the first generation unit,
When the processing unit receives a request from the outside for the image acquired by the acquiring unit, the processing unit refers to link information corresponding to the request and acquires image information specified by the referred link information. The image processing apparatus according to claim 1. When a request is received from the outside for the image acquired by the acquisition unit,
The image processing apparatus according to claim 3, wherein the processing unit refers to link information corresponding to the request using XSLT and acquires image information specified by the referenced link information. The second generation unit generates document information in XML format in which the respective image information generated by the first generation unit is embedded,
The image processing apparatus according to claim 1, wherein the processing unit acquires image information corresponding to the request when receiving a request from the outside for the image acquired by the acquisition unit. When a request is received from the outside for the image acquired by the acquisition unit,
The image processing apparatus according to claim 5, wherein the processing unit acquires image information corresponding to the request among image information embedded in the document information using XSLT.   The image processing apparatus according to claim 4, wherein the processing unit uses XSLT converted according to a request from the outside. An acquisition process for acquiring images;
A first generation step of generating a plurality of types of image information based on the acquired image;
A second generation step of generating document information in XML format describing each piece of image information generated in the first generation step;
An image processing method comprising: a processing step of acquiring image information corresponding to the request using the document information when a request is received from the outside for the image acquired in the acquisition step. .   A program for causing a computer to execute the image processing method according to claim 8.   A computer-readable storage medium storing the program according to claim 9.

Images