JP2008301484A - Structure of syndication data - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To have a manager remotely and centrally monitor updated information on data stored in an image processing device for performing communications with external apparatuses connected to a network. <P>SOLUTION: Information on the addition and modification of data which is stored in the device and dynamically changes is stored in a syndication DB 1705 through an application management interface 1703, when the data is targeted to be monitored. An updated information generation unit 1707 reconstructs and stores entries of the syndication DB periodically or in response to a request as an RSS feed or as XML data compatible with an RSS field standard following a template 2300. The stored XML data includes version information of the XML, version information of the syndication data, information on delivery, and listed updated information. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to the structure of syndication data, and more particularly to the structure of syndication data in markup language notation representing update information that can be used in an information processing apparatus or an image processing apparatus.

  In recent years, in the Web technology field of the Internet centering on information processing apparatuses, XML versions such as RSS versions and Atom used for syndicating the latest news and the like have begun to be widely used (Non-Patent Document 1 or Non-Patent Document). (See 2nd grade). For example, the specification of RSS1.0 (RDF Site Summary) by the RSS-DEV working group is disclosed in Non-Patent Document 1. In the proposal of the present invention, syndication means delivery / notification of update information / summary information.

  In recent years, not only information processing apparatuses such as general-purpose computers but also various embedded systems are connected to a network and can be used or managed remotely via the network. An embedded system is a computer system incorporated in a device for a specific use, and includes peripheral devices and applications specialized for the specific use. For example, various image processing devices such as printers, scanners, faxes, e-mails, and other image communication devices, copiers, document management systems, digital cameras, projectors, etc. are also connected to the network and used or managed remotely via the network. It is becoming possible. For example, Canon printers and multifunction peripherals have a Web server in the apparatus, and have a built-in Web application called “remote UI” for connecting and using a Web browser to remotely use and manage the apparatus.

  An increasing number of managers and users use or manage a plurality of devices via a network. In addition, there are increasing situations in which administrators and users use or manage devices from various nodes on the network.

  In recent years, embedded systems such as image processing apparatuses have come to provide more and higher functions by utilizing built-in CPUs and non-volatile memories (such as hard disks) with high functionality and high performance. . These functions are implemented as an embedded application executed by the built-in CPU, and various settings and data necessary for the operation are held in the built-in nonvolatile memory. Information stored in these devices is updated from time to time in accordance with user operations and device operations.

  In recent years, there has been known an image processing apparatus in which a function usable by a user is added or deleted by installing or uninstalling an application or a license. For example, Canon has commercialized MEAP (Multi-functional Embedded Application Platform) (registered trademark) that can dynamically add and delete embedded applications by incorporating an execution environment of Java (registered trademark) into the multifunction peripheral.

Patent Document 1 discloses an image processing apparatus that can acquire history information of fonts read by a printer in an XML format.
Dan Brickley and 10 others, "RDF Site Summary (RSS) 1.0", [online] May 30, 2001, RSS-DEV Working Group, [Search March 17, 2005], Internet <URL: http: // purl.org/rss/1.0/spec> Edited by M. Nottingham, R. Sayer, “The Atom Syndication Format draft-ietf-atompub-format-03”, [online] October 20, 2004, RSS-DEV Working Group, [Search March 17, 2005] , Internet <URL: http://atompub.org/2004/10/20/draft-ietf-atompub-format-03.html> JP 2004-25455 A

However, an embedded system including a communication unit that is connected to a network and communicates with an external apparatus, particularly an image processing apparatus, cannot realize the following requirements.
(1) The administrator wants to centrally monitor changes (that is, update information) of data stored in a plurality of apparatuses. I want to centralize the update information of multiple devices.
(2) The user wants to grasp the change caused by the other user in the data accumulated in the apparatus shared with the other user. I want to centralize the update information of multiple devices.
(3) I want to get updated information from anywhere (including from remote).
(4) I want to know the update information of the in-device data together with the update information of the Web site.
(5) I want to grasp update information in a form linked with related web pages and web applications.
(6) I want to use the updated information in various ways. For example, the Semantic Web (a technology that Tim Berners-Lee started advocating around 1998. The content of information on the Web that has been judged by the human eye until now is added to computers by adding meaning (semantics) using metadata. Like the concept of the technology that determines the content))), we want the device to provide update information as a knowledge expression that does not limit its use so that it can be used for various purposes later.
(7) To finely control the content and format of the update information supplied by the device.
(8) Further, it is desired to flexibly customize the update information supplied by the device.
(9) In particular, it is desired to grasp a change in an embedded application built in the apparatus and a change in a license permitting use of the embedded application.
(10) In particular, it is desired to grasp update information of documents accumulated in the apparatus.
(11) In particular, it is desired to grasp update information of the address book stored in the apparatus.
(12) I want to know the information that statistically processed the data stored in the device.
(13) It is desired to grasp not only the addition or change of data stored in the apparatus but also the change that the data in the apparatus is deleted.
(14) Further, it is desired to grasp the details of the deleted data for a certain period even after the deletion.
(15) When a change in data stored in the apparatus relates to an image, the user wants to grasp the contents of the image as update information.

  Although Patent Document 1 discloses that the history information of a font is described in XML, it does not disclose a configuration that can be accessed universally by a URI (Uniform Resource Identifier). In addition, the above-mentioned problems such as the type of update information other than the font, the flexibility of the format, and the linkage with other Web resources have not been solved.

  The present invention has been made in view of such problems, and an object of the present invention is to provide a syndication data structure capable of solving the above-described problems and satisfying the above requirements.

  In order to achieve the above object, the present invention comprises the following arrangement.

In the structure of syndication data in markup language notation representing update information that can be used in an information processing apparatus or image processing apparatus,
Declaration of version information of the markup language;
Declaration of version information of the syndication data;
A syndication data structure comprising an element describing information relating to the delivery of the syndication data and an element enumerating the update information,
The syndication data structure is distributed as update information of data stored in an image processing apparatus having a printing unit or an image reading unit connected to a network and communicating with an external device. The structure of the data.

According to the present invention, (1) an administrator can centrally monitor changes (that is, update information) of data stored in a plurality of apparatuses. In addition, there is an effect that update information of a plurality of apparatuses can be grasped in an integrated manner. In addition, any of the following effects (2) to (15) can be obtained.
(2) The user can grasp the change caused by the other user in the data accumulated in the apparatus shared with the other user. In addition, update information of a plurality of devices can be grasped in an integrated manner.
(3) Update information can be obtained from anywhere (including especially from a remote location).
(4) The update information of the in-device data can be grasped centrally together with the update information of the Web site.
(5) Update information can be grasped in cooperation with related web pages and web applications.
(6) The update information can be used in various ways.
(7) The content and format of the update information supplied by the apparatus can be finely controlled.
(8) The update information supplied by the apparatus can be flexibly customized.
(9) A change in a built-in application built in the apparatus and a change in a license that permits use of the built-in application can be grasped.
(10) The update information of the document accumulated in the apparatus can be grasped.
(11) The update information of the address book stored in the apparatus can be grasped.
(12) Information obtained by statistically processing data accumulated in the apparatus can be grasped.
(13) It is possible to grasp not only the addition and change of data stored in the apparatus but also the change that the data in the apparatus is deleted.
(14) The details of the deleted data can be grasped for a certain period even after the data is deleted.
(15) When a change in data stored in the apparatus relates to an image, the contents of the image can be grasped as update information.

<System configuration>
The best mode for carrying out the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing the overall configuration of an image processing system according to an embodiment of the present invention. In FIG. 1, the image processing system includes image processing apparatuses 110, 120, and 130 and a desktop computer 101 connected to each other via a network. The network is configured by a LAN (Local Area Network) 100, for example.

  The image processing apparatus 110 includes a scanner 113 that is an image input device, a printer 114 that is an image output device, a control unit 111, and an operation unit 112 that is a user interface. The image processing apparatus 110 is a so-called digital multi-function peripheral, and can perform functions such as copying, printing, image capturing, image filing, transmission (e-mail / FAX / FTP / file sharing, etc.) using these devices.

  The scanner 113, the printer 114, and the operation unit 112 are each connected to the control unit 111 and controlled by commands from the control unit 111. The control unit 111 is connected to the LAN 100.

  The image processing apparatuses 120 and 130 have the same configuration as the image processing apparatus 110, and the image processing apparatus 120 includes a scanner 123, a printer 124, and an operation unit 122, which are connected to the control unit 121. ing. The image processing apparatus 130 includes a scanner 133, a printer 134, and an operation unit 132, and these are connected to the control unit 131.

  The desktop computer 101 is an information processing apparatus that is used regularly by the user, and stores application programs used by the user, user data, and the like. The desktop computer 101 can also execute distributed applications in cooperation with the image processing apparatuses 110, 120, and 130, a server computer (not shown), and the like via the LAN 100.

<Software configuration of image processing apparatus>
FIG. 2 is a block diagram showing the configuration of software executed by each of the image processing apparatuses 110, 120, and 130.

  A user interface (UI) module 201 is a module that mediates between an apparatus and a user operation when the operator performs various operations / settings on the image processing apparatus. In accordance with the operation of the operator, this module transfers input information to various modules, which will be described later, and requests processing or sets data.

  Reference numeral 202 denotes an address book module, that is, a database module that manages a data transmission destination, a communication destination, and the like. The data managed by the address book module 202 is added, deleted, and acquired in accordance with an operation command from the UI module 201. Further, the address book module 202 gives data transmission / communication destination information to each module described later by an operator's operation.

  A Web server module 203 notifies the Web client of management information of the image processing apparatus in response to a request from the Web client (for example, the desktop computer 101). The management information includes an integrated transmission unit (Universal-Send) module 204, a remote-copy-scan module 209, a remote-copy-print module 210, and a control API (Control-API). ) Acquired via the module 218, and notified to the Web client via the HTTP module 212, the TCP / IP communication module 216, and the network driver (Network-Driver) 217 described later.

  The integrated transmission module (Universal-Send) module 204 is a module that manages data distribution. This module distributes data designated by the operator via the UI module 201 to the communication (output) destination designated in the same manner. When the operator instructs the generation of distribution data using the scanner function of the apparatus, the apparatus is operated via the control API module 218 described later to generate data.

  Reference numeral 205 denotes a P550 module which is included in the integrated transmission module 204 and is executed when a printer is designated as an output destination. Reference numeral 206 denotes an E-mail module. This module is included in the integrated transmission module 204 and is executed when an e-mail address is designated as a communication destination. A DB module 207 is included in the integrated transmission module 204 and is executed when a database is designated as an output destination. A DP module 208 is included in the integrated transmission module 204 and is executed when an image processing apparatus similar to this apparatus is designated as an output destination.

  Reference numeral 209 denotes a remote-copy-scan module. This module reads the image information using the scanner function of the image processing apparatus, and outputs the read image information to another image processing apparatus connected via a network or the like, so that the copy function originally realized by itself Is a module that implements the above using a plurality of image processing apparatuses.

  Reference numeral 210 denotes a remote-copy-print module. This module outputs a plurality of copy functions that are originally realized by outputting image information obtained by other image processing apparatuses connected via a network or the like using the printer function of the image processing apparatus. This module is realized by using the image processing apparatus.

  Reference numeral 211 denotes a Web browser module. This module reads and displays information of various websites (homepages) on the Internet or an intranet. The detailed configuration of the Web browser will be described later.

  Reference numeral 212 denotes an HTTP module. This module is used when the image processing apparatus performs communication using HTTP (HyperText Transfer Protocol), and provides a communication function to the Web server module 203 and the Web browser module 211 using a TCP / IP communication module 216 described later. . This module supports various protocols used in the Web such as HTTP, and also provides a communication function using a protocol corresponding to security.

  Reference numeral 213 denotes an lpr module. This module provides a communication function to the P550 module 205 in the integrated transmission module 204 using a TCP / IP communication module 216 described later.

  Reference numeral 214 denotes an SMTP module. This module provides a communication function to the e-mail module 206 in the integrated transmission module 204 using a TCP / IP communication module 216 described later.

  Reference numeral 215 denotes an SLM (Salutation-Manager) module. This module provides a communication function to the DB module 207, the DP module 208, the remote copy scan module 209, and the remote copy print module 210 in the integrated transmission unit module 204 using a TCP / IP communication module 216 described later.

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

  Reference numeral 218 denotes a control API. This provides an upstream module such as the integrated transmission module 204 with an interface to a downstream module such as a job manager module 219 described later. As a result, the dependency relationship between the upstream and downstream modules is reduced, and the applicability of each can be improved.

  Reference numeral 219 denotes a job manager module. This module interprets various processes instructed from the various modules described above via the control API 218, and gives instructions to the modules (220, 224, 226) described later. The job manager module 219 manages hardware processing executed in the image processing apparatus in an integrated manner.

  Reference numeral 220 denotes a codec manager (CODEC-Manager) module. This module manages and controls various types of data compression / decompression during the process instructed by the job manager module 219.

  Reference numeral 221 denotes an FBE encoder module. This module compresses data read by a scan process executed by the job manager module 219 or a scan manager (Scan-Manager) module 224 described later using the FBE format.

  Reference numeral 222 denotes a JPEG codec (JPEG-CODEC) module. This module performs JPEG compression of read data and JPEG of print data in a scan process executed by the job manager module 219 and the scan manager module 224 or a print process executed by the print manager module 226. The expansion process is performed.

  Reference numeral 223 denotes an MMR codec (MMR-CODEC) module. This module performs MMR compression of read data and MMR expansion processing of print data in a scan process executed by the job manager module 219 or the scan manager module 224 or a print process executed by the print manager module 226. It is.

  Reference numeral 229 denotes an information embedded image codec (IEI-CODEC) module. This module decodes information embedded in the read image data and prints image data in the scan process executed by the job manager module 219 and the scan manager module 224 or the print process executed by the print manager module 226. Information embedding is performed. The information is embedded in the image data using an encoding technique such as a barcode or a digital watermark (digital watermark). In addition, character recognition for recognizing characters in image data by image region separation and OCR technology and converting them to text data is also supported as a kind of decoding technology. Furthermore, conversion from text to image data using a raster image processor and overlay (overlay) of the converted image data and original image data are also supported as a kind of encoding technology (information embedding technology).

  Reference numeral 224 denotes a scan manager module. This module manages and controls scan processing instructed by the job manager module 219.

  A SCSI driver 225 handles communication between the scan manager module 224 and the scanner unit internally connected to the image processing apparatus.

  Reference numeral 226 denotes a print-manager module. This module manages and controls print processing instructed by the job manager module 219.

  Reference numeral 227 denotes an engine interface (Engine-I / F) module. This module provides an interface between the print manager module 226 and the printing unit.

  A parallel port driver 228 provides an I / F for outputting data to an output device (not shown) via the parallel port.

<Hardware configuration of image processing apparatus>
FIG. 3 is a block diagram illustrating a hardware configuration of the image processing apparatus 110. The image processing apparatuses 120 and 130 have the same configuration.

  The control unit 111 is connected to a scanner 113 serving as an image input device and a printer 114 serving as an image output device. On the other hand, the control unit 111 is connected to a LAN 100 or a public line (WAN) to input / output image information and device information. It is.

  The CPU 301 is a controller that controls the entire control unit 111. A RAM 302 is a system work memory used for the CPU 301 to operate. The RAM 302 is also an image memory for temporarily storing image data. A ROM 303 is a boot ROM, and stores a system boot program. An HDD 304 is a hard disk drive and stores system software and image data.

  The operation unit I / F 306 controls an interface with the operation unit (UI) 112 and outputs image data to be displayed on the operation unit 112 to the operation unit 112. Further, it plays a role of transmitting information input by the user via the operation unit 112 to the CPU 301.

  A network interface (Network) 308 manages connection with the LAN 100 and inputs / outputs information to / from the LAN 100. A modem (MODEM) 309 manages connection with the public line and inputs / outputs information to / from the public line. The above devices are arranged on the system bus 307.

  An image bus interface (Image Bus I / F) 305 is a bus bridge that connects a system bus 307 and an image bus 310 that transfers image data at high speed and converts a data structure. The image bus 310 is configured by a PCI bus or I15E1394.

  The following devices are arranged on the image bus 310. A raster image processor (RIP) 311 expands the PDL code transmitted from the network into a bitmap image. A device I / F unit 312 connects the scanner 113 and printer 114, which are image input / output devices, to the control unit 111, and performs synchronous / asynchronous conversion of image data.

  A scanner image processing unit 313 corrects, processes, and edits input image data. The printer image processing unit 314 performs correction, resolution conversion, and the like according to the performance of the printer 114 for the print output image data. An image rotation unit 315 rotates image data. The image compression unit 316 performs JPEG compression / decompression processing on multi-valued image data, and JBIG, MMR, and MH compression / decompression processing on binary image data.

  FIG. 4 is a perspective view illustrating an appearance of the image processing apparatus 110. The image processing apparatuses 120 and 130 also have the same appearance. In the following, the image processing apparatus 110 will be described, but the image processing apparatuses 120 and 130 have the same configuration and perform the same operation.

  A scanner 113, which is an image input device, illuminates an image on paper as a document, and scans a 13D line sensor (not shown) to generate raster image data.

  When the user sets original paper on the tray 406 of the original feeder 405 and instructs the start of reading in the operation unit 112, the CPU 301 of the control unit 111 gives an instruction to the scanner 113, and the original paper set on the tray 406 is The sheets are fed one by one, and the scanner 113 performs a document image reading operation.

  The printer 114, which is an image output device, is a part that prints raster image data on paper. The system includes an electrophotographic system using a photosensitive drum and a photosensitive belt, and an inkjet system in which an image is directly printed on a sheet by ejecting ink from a micro nozzle array, and any system may be used. Note that the printing operation is activated by an instruction from the CPU 301.

  The printer 114 has a plurality of paper feed stages so that different paper sizes or different paper orientations can be selected, and there are paper cassettes 401, 402, and 403 corresponding thereto. The paper discharge tray 404 receives paper that has been printed.

  FIG. 5 is a plan view showing the configuration of the operation unit 112 of the image processing apparatus 110. The operation units of the image processing apparatuses 120 and 130 have the same configuration.

  The LCD display unit 501 has a configuration in which a touch panel sheet 502 is pasted on an LCD (liquid crystal display device), and displays an operation screen and soft keys of the image processing apparatus 110, and a displayed key is pressed. If it is detected, position information indicating the pressed position is transmitted to the CPU 301 of the control unit 111.

  A start key 505 is a key operated when starting a reading operation of a document image. At the center of the start key 505, there is a green and red two-color LED display unit 506, which indicates whether or not the start key 505 can be operated. A stop key 503 is a key operated when it is desired to stop the operation of the image processing apparatus 110 that is operating. The ID key 507 is a key operated when inputting the user ID of the user. The reset key 504 is a key operated when initializing settings from the operation unit 112.

  FIG. 6 is a block diagram showing the internal configuration of the operation unit 112 and the operation unit I / F 306 of the image processing apparatus 110 in correspondence with the internal configuration of the control unit 111. In the following, the image processing apparatus 110 will be described, but there is no problem even if the image processing apparatus 110 is replaced with the image processing apparatus 120 or the image processing apparatus 130.

  As described above, the operation unit 112 is connected to the system bus 307 via the operation unit I / F 306. A CPU 301, RAM 302, ROM 303, and HDD 304 are connected to the system bus 307. The CPU 301 generally controls access to various devices connected to the system bus 307 based on control programs stored in the ROM 303 and the HDD 304. The CPU 301 reads input information from the scanner 113 connected via the device I / F 312 and outputs an image signal as output information to the printer 114 connected via the device I / F 312. A RAM 302 functions as a main memory, work area, and the like for the CPU 301.

  User input information from the touch panel 502 and various hard keys 503, 504, 505, and 507 is passed to the CPU 301 via the input port 601. The CPU 301 generates display screen data based on the contents of the user input information and the control program, and outputs the display screen data to the LCD display unit 501 via the output port 602 that controls the screen output device. Further, the two-color LED display unit 506 is controlled as necessary.

  FIG. 7 is a diagram illustrating an example of a standard operation screen displayed on the operation unit 112 of the image processing apparatus 110. The button group arranged in the uppermost part 701 in FIG. 7 is a button group for selecting one from various functions provided by the image processing apparatus 110.

  The copy function is a function for printing a document image data scanned and read by the scanner 113 by the printer 114 to obtain a copy of the document. The transmission function is a function for transmitting original image data read by the scanner 113 and image data stored in the HDD 304 to various output destinations. As output destinations, there are various output destinations that can be transmitted via the network interface 308 using various protocols, and various output destinations that can be transmitted via the modem 309 using a protocol such as a facsimile. You can select a destination and send it.

  The box function is a function for browsing, editing, printing, and transmitting document files such as image data and code data stored in the HDD 304. Document files stored in the HDD 304 include original image data read by the scanner 113, data downloaded via the network interface 308, data stored from print data received from other devices via the network interface 308, and other data via the modem 309. Facsimile data received from other devices. The box function can be used as an electronic mailbox in the user's office environment. Further, by delaying the print output on the paper until the password is input, it can also be used as a secure print that increases the confidentiality of the PDL print job. The extended function is a function for calling various extended functions such as locking the scanner 113 for use from an external device. The browser function is a function for browsing a Web site.

  An intermediate portion 702 in FIG. 7 displays an operation screen when the copy function is selected. 7 is a status display area, and displays various messages such as information on each function of the image processing apparatus 110 and the apparatus itself to the user regardless of the function selected in the uppermost part 701. To do.

(Distributed application operation by Web browser)
FIG. 8 is a block diagram showing an internal configuration of the Web browser module 211 shown in FIG. The protocol processing unit 801 establishes and communicates with other network nodes via the HTTP module 212. In this communication, an HTTP request is issued to the resource described by the URL, and a response is obtained. In this process, communication data is encoded / decoded according to various encoding formats.

  The content parser 802 receives content data expressed in an expression format such as HTML, XML, and XHTML from the protocol processing unit 801, and performs lexical analysis and syntax analysis to generate an analysis tree.

  The DOM construction unit 803 receives the parse tree from the content parser 802 and constructs a Document Object Model (DOM) corresponding to the content data structure. That is, conventional HTML allows various omissions in the grammar and has a wide variety of variations. Furthermore, content that is actually used is often not well-formed or valid. Therefore, the DOM construction unit 803 infers the correct logical structure of content data that is not grammatically valid, and tries to construct a valid DOM, as in other general Web browsers.

  The DOM processing unit 804 holds and manages the DOM constructed by the DOM construction unit 803 in a memory as a tree structure that expresses a nested relationship of object groups. Various processes of the Web browser are realized centering on this DOM.

  The layout engine 807 recursively determines the representation (presentation) on the display of each object according to the tree structure of the object group held by the DOM processing unit 804, and as a result, obtains the layout of the entire document. The display representation of each object is explicitly specified in a style sheet format such as Cascading Style Sheet (CSS) by a description embedded in the document or a description in another file linked from the document. There is a case.

  The style sheet parser 806 analyzes the style sheet associated with the content document.

  The layout engine 807 determines the document layout by reflecting the analysis result of the style sheet.

  The renderer 808 generates graphical user interface (GUI) data to be displayed on the LCD display unit 501 (FIG. 5) according to the document layout determined by the layout engine 807. The generated GUI data is displayed on the LCD display unit 501 by the user interface (UI) 201.

  The event processing unit 809 receives an event of an operation performed by the user on the touch panel sheet 502 or each key on the operation unit 112, and performs processing corresponding to each event. The event processing unit 809 also receives state transition events such as devices and jobs from the device control API 218, and performs processing corresponding to each event. In the DOM tree structure managed by the DOM processing unit 804, event handlers corresponding to various events are registered for each object class and each object instance. The event processing unit 809 determines an object to be in charge of processing the event from the object group managed by the DOM processing unit 804 according to the event that has occurred, and distributes the event. The object to which the event is distributed executes various processes according to the algorithm of the event handler corresponding to the event. The event handler process includes updating the DOM held by the DOM processing unit 804, redrawing instruction to the layout engine 807, HTTP request issuing instruction to the protocol processing unit 801, and controlling the image processing apparatus function by calling the apparatus control API 218. There is.

  The script interpreter 805 is an interpreter that interprets and executes a script such as Java (registered trademark) Script (ECMA Script). The script is embedded in the document or described in another file linked from the document, and performs operations on the DOM. The content provider can program the dynamic behavior of the provided document using a script.

  FIG. 9 is a diagram showing a configuration of a screen displayed when the Web browser function is selected on the LCD display unit 501 shown in FIG. A tab 901 is a tab for selecting a Web browser function, and by selecting this tab, the screen can be switched from another function (copy, box, transmission, expansion) screen to a display screen for the Web browser function. The URL input field 902 is a field for the user to input a URL of a desired resource. When the user presses the field, a virtual full keyboard (not shown) for inputting characters is displayed. The user can input a desired character string with a soft key simulating a key top arranged on a virtual full keyboard.

  An OK button 903 is a soft key for confirming the URL character string input in the URL input field 902. When the URL is determined, the Web browser module 211 issues an HTTP request for acquiring the resource. A progress bar 904 indicates the progress status of the content acquisition process by the HTTP request response. The content display area 905 is an area where the acquired resource is displayed.

  A return button 906 is a soft key, goes back through the history of content display, and redisplays the content displayed before the content currently displayed. A forward button 907 is a soft key, and returns to the display of the content displayed after the currently displayed content when the content display history is displayed retroactively. A reload button 908 is a soft key, and reacquires and redisplays the content currently displayed. A cancel button 909 is a soft key, and cancels the content acquisition process being executed.

  The status area 910 (bottom part 703) is an area for displaying messages from various functions of the image processing apparatus 110. Even when the Web browser screen is being displayed, a message for alerting the user sent from the scanner 113, the printer 114, or another function is displayed in the status area 910. Similarly, messages from the Web browser function are also displayed in the status area 910. From the Web browser function, a link destination URL character string, a content title character string, a message instructed by a script, and the like are sent.

(Adding and deleting embedded applications)
FIG. 10 is a diagram illustrating management of addition and deletion of embedded applications and a software configuration for executing the management in the image processing apparatus. An application described in JAVA (registered trademark) or the like, which can be added or deleted, is particularly called an additional application. FIG. 2 is a diagram showing a software hierarchy from hardware to the user interface, and is different from FIG.

  The Real Time OS 1101 is a real-time operating system that controls the entire image forming apparatus, and provides various resource management services and frameworks optimized for controlling an embedded system for software that operates on the real-time operating system. A controller 1102 controls the hardware of the image forming apparatus such as a reader unit and a printer unit, and also controls jobs that use printing, scanning, image conversion, and the like. The embedded application 1103 is a function such as copy, box, and transmission that is realized mainly by using the function of the controller 1102, and includes a user interface. The JVM 1104 is a JAVA (registered trademark) virtual machine, and includes an interpreter for operating a JAVA (registered trademark) program on the device.

  The OSGi Framework 1105 is a component that manages the life cycle of an application that operates on the JVM 1104, and manages installation / uninstallation, start / stop, and the like of the application. This mechanism is designed to correspond to a standard technology called “OSGi Framework” which is one of the standard technologies of management services. For details of the OSGi Framework, see “OSGi Service Platform Release 2, October 2001, OSGi”.

  The apparatus control class library 1106 is a library that provides an interface for an additional application to control devices such as a printer and a scanner of the image processing apparatus via the controller 1102. The Utility Class Library 1107 is a library that provides various functions of the image processing apparatus to the additional application. Imaging Class Library 1108, a library that provides basic image processing functions, performs processing such as image size reduction and image format conversion.

  The MIB Agent Class Library 1109 is a library for acquiring and setting MIB (Management Information Base) information set in the image processing apparatus. The Security Class Library 1110 is a library that provides an interface corresponding to a standard cryptographic security package (JCE and JSSE) of JAVA (registered trademark). The USB Common Class Library 1111 is a library that provides a communication function via USB.

  The additional application 1112 is an application that is described by a JAVA (registered trademark) program and can be dynamically added / deleted to / from the image processing apparatus. The additional application is classified into an Applet type that is an application that displays a user interface on the operation unit, a Servlet type that displays a user interface on a Web browser on a network, and an Eplet type that does not have a user interface. By adding an application, the function of the image processing apparatus can be expanded.

  A system interface service (SIS) 1113 is a service that provides an information exchange function between an additional application and the image forming apparatus. It is used to receive a request from the application, for example, to notify the application of an event such as a change in the power state, or to request control of the LED or buzzer from the application to the device.

  Apple Viewer Service 1114 is a service for registering, displaying, and switching Applet type services. Also, an event is notified to an Applet type additional application.

A Service Management Service (SMS) 1115 is a service that provides a user interface for managing additional applications. The SMS has the following functions as application management functions.
・ List display:
List application name, installation date, application ID, status, license status, resource usage status.
・ Installation:
Install the application.
·Uninstall:
Remove the application completely from the device. An application cannot be uninstalled without a license being invalidated.
·start:
Start and start a stopped application.
·Stop:
Stop the application in the start state (running state).

-License installation:
Install the license file for the application that requires a license.
-Invalidation of license:
Deactivate the application license so that the license file can be retrieved from the device onto the PC.
・ License download:
Download the invalidated license (license file) to the PC. Downloaded licenses can only be reinstalled on the same device.
・ Switching authentication application:
Switch authentication application. It is essential to restart the device after switching.
・ Change display order:
Change the display order of applications on the operation unit.
-System information display:
Displays system information.
・ Application information list:
List information including the license contents of the application.
・ Application history list:
Display a list of uninstalled applications.
·change Password:
Change the password when logging in to SMS.

  The HTTP service 1116 is a component that performs communication using HTTP and HTTPS. With this HTTP service function, it is possible to access system applications and additional applications from a Web browser on the network. The login function has been expanded based on the specifications of the HTTP Service defined in the aforementioned “OSGi Framework”.

  FIG. 11 is a diagram showing an example of the SMS login screen displayed on the Web browser on the network. The SMS login screen is displayed when there is an access from an unauthenticated browser. The password input field 1201 is an area for inputting a password. The login button 1202 is a button for sending the password information input in the password input field and logging in to the SMS. Note that the SMS password can be changed by the user. A serial number display 1203 displays a serial number unique to the image processing apparatus.

  FIG. 12 is a diagram showing an example of an SMS application list screen displayed on a Web browser on the network. An install button 1301 is a button for calling an install screen for newly installing an application. A system management button 1302 is a button for calling a system management screen for setting an authentication type, an application display order, and the like. The logout button 1303 is a button for logging out from the SMS, and when this button is pressed, the SMS login screen 12 is displayed. The application list display area 1304 displays a list of applications installed in the image processing apparatus. One application is displayed in a one-line table format, and for each application, a selection radio button, name, installation date, application ID, status, license status, and resource usage status are displayed. The name display is a link text. When the name is selected, an application details screen for displaying more detailed information of the application is displayed.

The uninstall button 1305 is a button for uninstalling the application selected by the radio button. If uninstallation is not possible due to the license status of the selected application, etc., the button is inactivated and cannot be pressed down. In the figure, an inactivated state is shown.
The start button 1306 is a button for starting the application selected by the radio button. The stop button 1307 is a button for stopping the application selected by the radio button. The resource information display area 1308 displays the hard disk capacity, memory, thread, socket, and file descriptor used by the installed application.

FIG. 13 is a diagram illustrating an example of an SMS application installation screen displayed on a Web browser on the network. The application list button 1401 is a button for calling the application list screen of FIG. A system management button 1402 is a button for calling a system management screen for setting an authentication type, an application display order, and the like. A logout button 1403 is a button for logging out from the SMS. When this button is pressed, the SMS login screen 12 is displayed.
The application selection button 1404 is a button for selecting an application file to be installed. When this button is pressed, an OS standard file selection dialog is displayed. The user can select an application to be installed from this dialog. In 1405, the path of the application file selected by the user is displayed.

  A license file selection button 1406 is a button for selecting a license file for an application to be installed. When this button is pressed, an OS standard file selection dialog is displayed. The user can select a license file to install from this dialog. In 1407, the path of the license file selected by the user is displayed. An OK button 1408 is a button for executing installation of an application file and a license file selected by the user. A cancel button 1409 is a button for canceling without performing the installation process.

  FIG. 14 is a diagram showing an example of an SMS application details screen displayed on a Web browser on the network. An application list button 1501 is a button for calling an application list screen (FIG. 12). The install button 1502 is a button for calling an application installation screen (FIG. 13) for newly installing an application. A system management button 1503 is a button for calling a system management screen for setting an authentication type, an application display order, and the like. A logout button 1504 is a button for logging out from the SMS, and when this button is pressed, an SMS login screen (FIG. 11) is displayed.

  The application information display area 1505 displays detailed information of the application. Information to be displayed includes an application ID, an application name, an installation date, a manufacturer, a product version, and the like. A license information display area 1506 displays license information of the application. Information to be displayed includes the license status, serial number, expiration date, counter information, and the like. A license management button 1507 is a button for calling a license management screen (FIG. 15).

  FIG. 15 is a diagram illustrating an example of an SMS license management screen displayed on a browser on the network. Buttons 1601 to 1604 are buttons having the same role as 1501 to 1504 described in FIG. An OK button 1605 is a button for returning to the application detail screen (FIG. 14). The license file selection button 1606 is a button for selecting a license file to be installed. When this button is pressed, an OS standard file selection dialog is displayed. In 1607, the path of the license file selected by the user is displayed. An install button 1608 is a button for executing installation of the license file selected by the user. The invalidation button 1609 is a button for invalidating the license. The download button 1610 is a button for downloading an invalid license file to the PC. A delete button 1611 is a button for deleting an invalid license file. If the download button 1610 and the delete button 1611 cannot be operated depending on the state of the license, the buttons are inactivated and cannot be pressed down.

(Generation and supply of service update information feed data)
FIG. 16 is a block diagram illustrating a software structure for generating and supplying an RSS feed of application-related update information. An administrator 1701 is a user who performs MEAP (registered trademark) application management, and manages the image processing apparatus 110 in order to manage addition, editing, and deletion of applications that are dynamically incorporated into the apparatus and provide services. Manipulate. A user 1702 is a user who accesses the image processing apparatus 110 via the RSS reader 1710 operating on the desktop computer 101 and refers to update information related to the MEAP application. A user 1702 accesses the image processing apparatus 110 via a Web browser 1709 running on the desktop computer 101, and browses resources and Web applications provided by the image processing apparatus 110. The image processing apparatus 110 and the desktop computer 101 are network-connected, and software running on each communicates data with each other according to a protocol such as HTTP or HTTPS.

  Now, the software configuration inside the image processing apparatus 110 will be described. A software structure for generating and supplying an RSS feed of application-related update information includes a JVM 1104, a device control class library 1106, a service management service 1115, and an HTTP service 1116. The inside of the service management service 1115 further includes the following software. Note that the additional application 1112 in FIG. 10 corresponds to an application that can be deleted and added among the applications included in the MEAP application DB in FIG. In FIG. 10, the SMS 1116 and the additional application 1112 are described independently, but the additional application 1112 is managed by the SMS 1116. FIG. 16 shows this relationship as an inclusion relationship.

  The application management interface 1703 provides a management interface for installing, uninstalling, and controlling an application and a license incorporated in the image processing apparatus 110 to provide a service from the outside of the apparatus. The application management interface 1703 is implemented as an SMS 1115 Web application (Servlet service), and can be operated by a manager 1701 from a remote Web browser via network communication (not shown). The application management interface 1703 may be implemented so as to provide the user interface to the operation unit 112 provided locally in the image processing apparatus (Applet service).

  The MEAP application database (DB) 1704 is a database for accumulating and managing a MEAP application group installed in the embedded application platform of the image processing apparatus 110 and its license group 1704A.

  The syndication DB 1705 is a database for accumulating and managing data used for syndication of update information related to an embedded application of the image processing apparatus 110. The data to be stored and managed includes an update information entry that is generated by holding attribute information related to a change event (event) related to the MEAP application and its license each time an event occurs.

  The template DB 1706 is a database for accumulating and managing templates that provide templates of XML files used for syndication (distribution). Data describing the generation rule is also included in the template data. The generation rules include, for example, information (monitoring target information) 1706A that defines whether or not to monitor changes as a target of update information, information (period information) 1706B about a period that is a target of update information, and the like. These will be described later with reference to FIG. 18 and FIG. The XML application for syndication conforms to specifications such as each version of RSS and Atom. A plurality of templates are prepared according to the type of information to be syndicated and the conforming specifications.

  The update information generation unit 1707 includes a template engine. The template engine is based on the data stored and managed in the syndication DB 1705 based on the template group stored and managed in the template DB 1706, and various attributes such as the configuration and state of the image processing apparatus 110 obtained from the device control class library 1106. An XML file used for syndication is generated. The update information generation unit 1707 stores the generated XML file (syndication data file such as RSS or Atom) in the update information (RSS) storage unit 1708.

  An update information (RSS) storage unit 1708 is a storage for accumulating XML files used for syndication. The update information storage unit 1708 holds a plurality of different files depending on the type of information to be syndicated. Also, a plurality of files described in formats such as RSS versions and Atoms are held in accordance with the conforming XML application specifications. The update information storage unit 1708 is mounted as a file system accessible by the HTTP server 1116. Each file of the XML file group stored in the update information storage unit 1708 is specified by a unique URL when viewed from the HTTP client group connected to the HTTP server 1116. When an HTTP client connects to the HTTP server 1116 and requests acquisition of the resource specified by this URL, the HTTP server 1116 reads out an XML file corresponding to the URL specified in the acquisition request from the update information storage unit 1708, and HTTP Send to client.

  In response to a request by HTTP or HTTPS from an HTTP client, the HTTP server 1116 transfers data of various resources (resources) held in the image processing apparatus 110 as a response. Resources accessed by the client by HTTP include static data files such as HTML and images held in a nonvolatile memory inside the image processing apparatus 110 such as the HDD 304 (including XML files held in the update information image storage unit 1708). ) And data dynamically generated by a program executed by the CPU 301. Data generated dynamically in response to HTTP requests includes various Web application groups that MEAP's Servlet-type applications run on the JVM 1104 (for example, the above-mentioned SMS users for remote control from a desktop computer). HTML generated by the interface).

<Computer software configuration>
Next, the software configuration inside the desktop computer 101 will be described. The RSS reader 1710 is an application program for acquiring and formatting an XML format for syndication such as each version of RSS and Atom. Many websites such as news distribution sites, information providing sites, and web logs (weblogs or blogs) on the Internet provide syndication data in addition to site content to syndicate new articles on the site. . Using the RSS reader 1710, the user 1702 can efficiently browse the titles and contents of newly arrived articles on these Internet sites. The RSS reader 1710 can access syndication data not only in the Internet but also in an intranet if it is disclosed as a resource that can be specified and acquired by a URI. When a URI for identifying syndication data stored in the update information storage unit 1708 of the image processing apparatus 110 is specified and an HTTP acquisition request is transmitted from the RSS reader 1710 to the HTTP server 1116, the HTTP server 1116 receives the HTTP acquisition request. As a response, syndication data stored in the update information storage unit 1708 can be received. In some cases, the hyperlink specified by the URI is included in the syndication data that is shaped and displayed by the RSS reader 1710. When the user 1702 selects a specific hyperlink on the display of the RSS reader 1710, the RSS reader 1710 cooperates with the web browser 1709 to acquire and display the URI on the web browser 1709.

  The Web browser 1709 is provided with various resources provided in a form that can be specified by a URI in a Web server on the Internet or an intranet, such as document data in markup languages such as HTML and XHTML, and various multimedia data (still images, Video, audio, etc.), properly shaped, displayed graphically or read aloud. Data acquisition is performed mainly by a communication protocol such as HTTP or FTP. The Web browser 1709 is a client-server model client side in terms of communication protocol, and is positioned as, for example, an HTTP client. When a hyperlink specified by a URI is included in the data that the user 1702 browses, when the user selects an anchor of a specific hyperlink, the Web browser 1709 acquires and displays the resource of the specified URI. . Data may be sent (posted) from the Web browser 1709 to resources on the Web server side using a markup document form specification such as HTML. The user 1702 uses the Web browser 1709 to make an acquisition request by specifying the URI assigned to the Servlet operating on the JVM 1104 of the image processing apparatus 110, for example. The HTTP server 1116 of the image processing apparatus 110 transfers this acquisition request to the corresponding Servlet, and further returns a response such as HTML generated by the Servlet as a processing result to the Web browser 1709.

  In this embodiment, the RSS reader 1710 and the web browser 1709 are each configured as a single application program, but may be configured as a single application program having both functions. The RSS reader 1710 and the Web browser 1709 have been described as operating on the desktop computer 101. However, the RSS reader 1710 and the Web browser 1709 are configured to operate on various general-purpose information processing apparatuses including not only desktop computers but also portable computers such as PDAs. May be. Or you may comprise so that it may operate | move on various built-in apparatuses, such as image processing apparatuses, such as a multifunction machine and a digital camera, such as the image processing apparatuses 120 and 130, and a mobile telephone.

  FIG. 17 is a block diagram showing the data structure of the syndication DB. A systemUrl 1801 is a URI (URL) that identifies the top page of the Web server of the image processing apparatus 110. The top page serves as an entrance to various Web server functions provided by the image processing apparatus 110. The webApplicationName 1802 is a name given to the Web application function provided by the Web server of the image processing apparatus 110. ProductName 1803 is a product name (model name or the like) of the image processing apparatus 110. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it.

  The deviceName 1804 is a unique device name given to the specific image processing apparatus 110. The unique device name is used by the device user (administrator) to specify the device for convenience of use. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. A deviceSerialNumber 1805 is a serial number assigned to a specific image processing apparatus 110. The serial number may be used by the manufacturer of the image processing apparatus 110 to identify an individual machine. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. deviceOptionUnits 1806 is a character string that describes a group of option units attached to the image processing apparatus 110. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. deviceLocation 1807 is a character string that describes the location where the image processing apparatus 110 is installed. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it.

  An administrator 1808 describes a user name in charge of management of the image processing apparatus 110 and its e-mail address. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. messageOfTheDay 1809 describes a message announced by the user in charge of management of the image processing apparatus 110 for other users. This message may be displayed on the operation unit 122 of the image processing apparatus 110 or a Web application (remote UI). The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it.

  mfpStatus 1810 describes the operating state of the image processing apparatus 110 as a multifunction peripheral. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. The printerStatus 1811 describes the operating state of the image processing apparatus 110 as a printer. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. The imageReaderStatus 1812 describes the operation state of the image processing apparatus 110 as an image input apparatus (image scanner, digital camera, etc.). The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. The sendStatus 1813 describes the operation state of the image processing apparatus 110 as a transmission apparatus (fax, IFAX, e-mail, file transfer, etc.). The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. The receiveStatus 1814 describes the operating state of the image processing apparatus 110 as a receiving apparatus (fax, IFAX, e-mail, file transfer, etc.). The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it. The storageStauts 1815 describes the operation state of the image processing apparatus 110 as a storage apparatus. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it.

  lastUpdateDate 1816 describes the date and time when the latest update information entry was registered in the syndication DB 1705. The entry 1817 is a list having a structure for holding a series of update information entries. The structure of each entry included in the list will be described later. The application 1818 is a list having a structure for holding information on application groups and license groups installed in the MEAP application DB 1704. A user 1819 is a list having a structure for holding information of registered users of the image processing apparatus 110. The value of this field is obtained from the controller via the device control class library 1106 and dynamically resolved when the update information generation unit 1707 needs it.

  Now, the structure of each element included in the list 1920 of the entry 1817 will be described. Each element of the list corresponds to an individual update information entry. The entryPermanentLink 1921 describes a URI that identifies a resource for acquiring HTML that describes detailed information of the update information entry. When the user acquires the resource indicated by this URI using the Web browser 1709 or the like, it is possible to obtain a display of detailed information related to this update information. entryDate 1922 describes the date and time when this update information entry occurred. entrySubject 1923 describes the subject of this update information entry. For example, in the case of an entry indicating installation of a new application, information “installation” which is an event category is described.

  The entryDescription 1924 describes the description of this update information entry. The explanation is for the user to read and understand the contents of the update information, and is described in a natural language. It is marked up with HTML or the like, and may include embedding of hypertext links and images. The entryOperator 1925 describes a user who has performed an operation that causes an update event corresponding to this update information entry. When a specific user is not involved in the event occurrence (such as an event automatically generated by a timer or the like), the value of this field is “system” or “timer”. entryApplicationName 1926 describes the name of the application related to this update information entry. If the application is a Web application, it also includes a URI description that identifies it. For example, when the update information is installation of a new application, the related application is the installed application. The entryApplicationDescription 1927 describes the description of the application related to this update information entry. The explanation is for the user to read and understand the contents of the application, and is described in a natural language. It is marked up with HTML or the like, and may include embedding of hypertext links and images.

  The entryApplicationSeeAlso 1928 describes a URI that specifies another information source of the application related to the update information entry. For example, the URL of the application information display screen by SMS, the URL of the application information page of the Web site provided by the application developer, and the like are described. The entryLicenseCondition 1929 describes the license condition and status of the application related to this update information entry. entryIsNewApplication 1930 is true if this update information entry is based on the event of adding a new application that can be used. entryIsApplicationUnavailable 1931 is true when this update information entry is based on an event that occurs when an application becomes unavailable due to uninstallation or the like. entryIsLicenseExpired 1933 is true if this update information entry is based on an event that the license has expired due to aging.

  FIG. 18 is a diagram illustrating an example of a screen for setting a target for monitoring update information. Displays a switch that selects whether to monitor each event for an application and its license. Reference numeral 1901 denotes a switch for setting whether or not application installation / uninstallation is to be monitored. When this switch is set to ON, when the application is installed or uninstalled by the user, the information is recorded in the update information file. To work. Similarly, reference numeral 1902 denotes a switch for setting whether or not to start / stop an application.

  Reference numeral 1903 denotes a switch for setting whether or not the license expiration warning is to be monitored. When this switch is set to ON, when the remaining license expiration date becomes shorter than a predetermined number of days (30 days, 10 days, 5 days, 1 day), the information is recorded in the update information file. To work.

  Reference numeral 1904 denotes a switch for setting whether or not to invalidate the license. When this switch is set to ON, when the license becomes invalid, it is recorded as update information. A license is invalidated when the expiration date has expired or the user has invalidated it.

  Reference numeral 1905 denotes a switch for setting whether or not application counter information is to be monitored. When this switch is set to ON, when the value of the application counter changes, the information is recorded as update information.

  The values set by these switches are stored in the monitoring target information 1706A described with reference to FIG. 16 for each item.

  FIG. 19 is a flowchart of an application management processing procedure in the image processing apparatus. This processing procedure is executed by the CPU 301 of the image processing apparatus 110. This processing algorithm is included in the application management interface 1703, which is a software module of the SMS 1115. The SMS 1115 can configure an operation screen on the operation unit 112 or can be configured as a Web application. When implemented as a Web application, the operation screen is as shown in the example shown in FIGS. 11 to 15 on a remote Web browser.

  In step S2001, an operation selection input by the user is branched according to the type of waiting operation. If the selected operation type is installation (corresponding to 1301 on the operation screen), the process proceeds to step S2002. If the selected operation type is application list (corresponding to 1401 on the operation screen), the process proceeds to step S2007.

  In step S2002, an application file and / or a license file are input. In step S2003, it is determined whether an application file has been input. If it is input, the process proceeds to step S2004, and if it is not input, the process proceeds to step S2005. In step S2004, the input application file is installed in the MEAP application DB 1704. In step S2005, it is determined whether a license file has been input. If it is input, the process proceeds to step S2006, and if it is not input, the process proceeds to step S2012. In step S2006, the input license file is installed in the MEAP application DB 1704. Next, the process proceeds to step S2012.

On the other hand, in step S2007, the application selected by the user is selected from the application list. The following operations are for the selected application.
In step S2008, a condition branch is entered according to the type of waiting operation for the input of the operation selection by the user. If the selected operation type is uninstallation (corresponding to operation screen 1305), the process proceeds to step S2009. If the operation type is start (corresponding to operation screen 1306), the process proceeds to step S2010, and if stopped (corresponding to operation screen 1307). The process proceeds to step S2011.

  In step S2009, the selected application is uninstalled from the MEAP application DB 1704. Next, the process proceeds to step S2012. In step S2010, the operation of the selected application is started. Next, the process proceeds to step S2012.

  In step S2011, the operation of the selected application is stopped. Next, the process proceeds to step S2012.

  In step S2012, an update information entry corresponding to the processing executed in the previous step is generated. That is, an update information entry describing the detailed information of the event is generated in response to an event of application or license installation or uninstallation, or application start or stop. However, at this time, with reference to the monitoring target information 1706A, when the value of the item corresponding to the event indicates that the event is the monitoring target, an update information entry is generated.

  In step S2013, the generated update information entry is stored in the syndication DB 1705. In step S2014, an RSS feed file generation process is called to generate a new RSS feed file from the syndication DB that has been changed by adding a new update information entry.

  FIG. 20 is a flowchart of a processing procedure for monitoring a change in license condition state accompanying the operation of the image processing apparatus. This processing procedure is executed by the CPU 301 of the image processing apparatus 110. This processing algorithm is included in the SMS 1115.

  In step S2101, job execution by the application is monitored. In step S2102, the accumulated resource usage associated with job execution is counted up. In step S2103, it is determined whether the license conditions have expired due to the expiration of the license expiration date or an increase in resource usage. When it expires, it progresses to step S2104, and when it does not expire, it progresses to step S2108.

  In step S2104, the MEAP application DB 1704 is changed to invalidate the license of the application whose license has expired. In step S2105, the operation of the application whose license has expired is stopped. In step S2106, an update information entry describing a license expiration event is generated. However, at this time, with reference to the monitoring target information 1706A, when the value of the item corresponding to the event indicates that the event is the monitoring target, an update information entry is generated. In step S2107, the generated update information entry is stored in the syndication DB 1705. Next, the process proceeds to step S2111.

  On the other hand, in step S2108, the remainder of the expiration date, resource usage limit, and the like are compared with a default value to determine whether or not the license condition is nearly expired. If the revocation is near, the process proceeds to step S2109, and if the remaining is sufficient, the process proceeds to step S2111. In step S2109, an update information entry describing an event that the license is about to expire is generated. However, at this time, with reference to the monitoring target information 1706A, when the value of the item corresponding to the event indicates that the event is the monitoring target, an update information entry is generated. In step S2110, the generated update information entry is stored in the syndication DB 1705. Next, the process proceeds to step S2111.

  In step S2111, job execution monitoring by the application and statistical processing based on the past history are performed. Job execution monitoring by the application and statistical processing based on the past history include calculation of resource usage for each user and user group, calculation of correlation between time zone and job execution, calculation of increase / decrease degree of application usage rate, Various statistical processes such as integration of communication and storage data sizes, running costs of consumables, and maintenance costs specific to image processing apparatuses are useful.

  In step S2112, as an example of the use of statistical processing, it is determined whether the number of uses of the application whose job execution has been monitored has increased rapidly compared to a past fixed period. If the usage is increasing rapidly, the process proceeds to step S2113, and if not, the process proceeds to step S2114. In step S2113, an update information entry describing an event that application usage is rapidly increasing is generated. However, at this time, with reference to the monitoring target information 1706A, when the value of the item corresponding to the event indicates that the event is the monitoring target, an update information entry is generated. In step S2114, the generated update information is stored in the syndication DB 1705.

  In step S2115, an RSS feed file generation process is called to generate a new RSS feed file from the syndication DB that has been changed by adding a new update information entry. Next, the process returns to step S2101 to repeat the application monitoring process.

  FIG. 21 is a diagram illustrating a structure of an example of an XML format (that is, a format of syndication data) used for syndication of update information of the image processing apparatus. An XML file stored in the update information storage unit 1708 and specified by a URI is an XML document that describes various data updates related to the embedded application of the image processing apparatus and information on various events that occur related to the embedded application of the apparatus. It is. This XML document format provides a plurality of types corresponding to various formats used by general Web sites to distribute site update information. The image processing apparatus 110 supports each version of RSS and XML formats such as Atom. Here, description will be given taking RSS 1.0 as an example. In FIG. 21, the inclusion relationship of each block means the inclusion relationship of XML elements.

  The RDF element 2201 is the top element of the XML document. The RDF element includes a channel element 2202, an image element 2203, and item elements 2204, 2205, and 2206. The channel element 2202 describes basic information related to the entire update information. This element corresponds to an RDF-like subject node. The content of the channel element includes a title element 2207, a link element 2208, a description element 2209, an image element 2210, and an items element 2211. A title element 2207 represents the title of this update information. A link element 2208 represents the URI of the site handled by this update information. A description element 2209 describes the contents and functions of the site handled by the update information. The image element 2210 describes a URI that identifies an image resource such as a logo of a site handled by the update information. Details are described in an image element 2203 described later. The items element 2211 provides an index of the item element groups 2204, 2205, and 2206. Each update information URI is indicated by the li element 2213 listed in the contents of the Seq element 2212. The image element 2203 represents an image such as a logo. The content includes a title element 2214, a url element 2215, and a link element 2216. The title element 2214 represents the title of the image and may be used as alternative text for the image. A url element 2215 describes the URI of the image resource. The link element 2216 describes a URI used as a link destination when displaying a hyperlink with this image as an anchor. The item elements 2204, 2205, 2206, etc. are a plurality of elements each representing individual update information. The content includes a title element 2217, a link element 2218, and a description element 2219. The title element 2217 describes the title of the update information. A link element 2218 describes the URI of the update information. A description element 2219 describes the description of the update information.

  FIG. 22 is an example of a template stored in the template DB. The template illustrated in the figure is used to generate an XML file in the RSS 1.0 format. The template data is a plurality of text data describing XML elements, template control instructions, and template variables composed of various syndication vocabularies. The RSS 1.0 format XML vocabulary already described will be given the same reference numerals and description thereof will be omitted.

  There are a plurality of template data stored in the template DB 1706 depending on the format of syndication data to be output (RSS versions, Atoms, etc.). System integrators who build systems that include users, administrators, and image processing devices can easily copy and edit template files and customize them according to the usage environment or prepare multiple template variations. . Since the template is structured text data, it can be easily edited intuitively by a visual editor having a graphical user interface. A template editor (not shown) is provided, and the user or the like can graphically edit the template structure and the correspondence of information to be embedded in the template.

  In generating an RSS file from a template, most text of the template is output to the RSS file as it is, but a pseudo element having a prefix of “TMPL_” (shown in bold in FIG. 22) is a template of the update information generation unit 1707. Specially processed by the engine as template variables and template control instructions.

  The TMPL_VAR pseudo-element is a template variable that is replaced by the template engine with the value of the variable with the name attribute name. That is, the TMPL_VAR pseudo element is a variable that is replaced with an attribute relating to the configuration, setting, or state of the image processing apparatus. The value to be replaced includes information on update information entry in the syndication DB 1706, application information and license information in the MEAP application DB 1704, and configuration information and status of the image processing apparatus obtained from the controller module via the device control class library 1106. Based on information.

  The TMPL_LOOP pseudo-element is a template control instruction that repeatedly processes the contents up to the TMPL_LOOP end tag (</ TMPL_LOOP>) while sequentially selecting the variables included in the list from the list variable having the name attribute name. Variables that are sequentially selected from the list have a structure inside (see the contents of the entry list in FIG. 17), and the name attribute of the TMPL_VAR pseudo element included in the repeated block by TMPL_LOOP is the internal structure of this variable. When a variable is referenced, the TMPL_VAR pseudo-element is replaced with the value of the internal structure variable and output.

  The TMPL_IF pseudo element is a template control instruction, and controls the processing of the template engine by the truth value of the variable having the name attribute name. If the variable is true, the contents up to the end tag (</ TMPL_IF>) of TMPL_IF are processed, but if the variable is false, the start tag to end tag of TMPL_IF are skipped.

  Since the update information feed data for syndication generated by the template of FIG. 22 is an XML application in the RSS 1.0 format, it has module extensibility using an XML namespace. That is, necessary information can be easily added to syndication feed data in combination with other XML vocabularies. For example, the following are combined from the DCMME properties of Dublin Core, which are frequently used as standard metadata description elements. date elements 2301, 2306, subject element 2304, creator element 2305. Also, a generatorAgent element 2302 is combined from the Admin module.

  Thus, one of the great effects of the present embodiment is that it becomes easy to flexibly and strictly expand the data format for feeding update information.

  FIG. 23 is a flowchart showing a processing procedure for syndication data generation by the update information generation unit. This process is executed by the CPU 301 of the image processing apparatus 110. This processing algorithm is included in the update information generation unit 1707. This process is called when the feed file is updated. For example, it is called at the end of application management processing (FIG. 19) or at the end of job monitoring processing by SMS (FIG. 20). Also, it is called in conjunction with the timer and periodically updates the feed file. Alternatively, it may be configured to call when an acquisition of a feed file is requested by an HTTP request from a client and to respond with an updated feed file. In this case, when the apparatus is not operating between the previous feed file generation and the response, the cached feed file may be responded.

  In step S2401, a template used to generate a syndication data file (feed file) is selected and extracted from the template DB 1706. As described above, there are a plurality of templates with variations according to various XML formats and proper use. A system integrator or the like that constructs a system including a user, an administrator, or an image processing apparatus can select a plurality of templates to be selected for generating a feed file by using a user interface (not shown). When a plurality of templates are set, when this processing procedure for generating a feed file is called, a plurality of feed files are generated corresponding to the set templates.

  In step S2402, the template is analyzed and feed data is output. Since the template analysis processing procedure is recursively called, details will be described later (FIG. 24).

  FIG. 24 is a flowchart illustrating a processing procedure of template analysis and syndication data output by the update information generation unit. This process is executed by the CPU 301 of the image processing apparatus 110. This processing algorithm is included in the update information generation unit 1707.

  In step S2501, tokens (lexical characters) obtained by lexical analysis while reading the template data as byte strings are sequentially read. In step S2502, it is determined whether the read token is a template pseudo element. If it is a template pseudo-element, the process proceeds to step S2503, and if it is not a template pseudo-element (that is, if it is a normal XML element to be directly written in the feed file), the process proceeds to step S2513. In step S2503, the template instruction of the template pseudo element is discriminated and a conditional branch is made. If the template pseudo element is a start tag of TMPL_IF, the process proceeds to step S2504. If the template pseudo element is a start tag of TMPL_LOOP, the process proceeds to step S2506. If it is TMPL_VAR, the process proceeds to step S2512.

  In step S2504, a variable with a variable name referred to by the name attribute of the TMPL_IF start tag is evaluated to determine a true / false value. The variable is schema-defined in the syndication DB 1705, and its value is determined based on the update information entry in the syndication DB 1705, the MEAP application DB 1704, and the device control class library 1106. From the device control class library 1106, the configuration and status of the image processing apparatus, job information, and the like are obtained. If the truth value of the variable is false, the process proceeds to step S2505, and if true, the process proceeds to step S2514. In step S2505, since the TMPL_IF condition is false, the template data is skipped until the end tag of TMPL_IF. Next, the process proceeds to step S2514.

  On the other hand, in step S2506, a list variable having the name attribute name of the TMPL_LOOP start tag is read from the syndication DB and evaluated. The TMPL_LOOP control instruction is an instruction for repeatedly processing the contents up to the end tag (</ TMPL_LOOP>) of TMPL_LOOP while sequentially selecting variables included in the list. Here, the case where the list variable is entry will be described.

  In step S2507, each variable included in the list, that is, each update information entry is selected from the entry list read from the syndication DB. Each variable included in the list corresponds to an update information entry and has the internal structure of FIG. When the name attribute of the TMPL_VAR pseudo element included in the subsequent block of TMPL_LOOP refers to a variable of the internal structure of this variable, the TMPL_VAR pseudo element is replaced with the value of the variable of the internal structure and output. Therefore, in each iteration of the TMPL_LOOP block, each update information entry is selected one by one, and template processing based on that information is performed.

  In step S2508, the internal variable entryDate of the read update information entry is compared with the preset update information posting period setting (FIG. 25) to determine whether the read entry is within the syndication feed file posting period. Determine. If it is within the posting period, the process proceeds to step S2508, and if not within the posting period, the process proceeds to step S2511. The determination of the posting period is, for example, comparing the date of the entry with the current date, and if the current date is within the period stored as the period information 1706B in FIG. It can be determined that it is the posting period.

  In step S2509, template analysis processing is performed recursively under the scope of the selected update information entry until the end tag of TMPL_LOOP appears. In step S2510, the selection of the update information entry that has been selected because the loop of the TMPL_LOOP block has been completed is canceled. In step S2511, it is determined whether all update information entries included in the entry list have been processed. If all update information entries have been processed, the loop is terminated and the process proceeds to step S2514. If unprocessed update entries remain, the process proceeds to step 2506 and the process of the TMPL_LOOP block is repeated.

  On the other hand, in step S2512, the variable of the variable name referred to by the name attribute of the TMPL_VAR pseudo element is evaluated and the value is written to the feed file. The variable is schema-defined in the syndication DB 1705, and its value is determined based on the update information entry in the syndication DB 1705, the MEAP application DB 1704, and the device control class library 1106. From the device control class library 1106, the configuration and status of the image processing apparatus, job information, and the like are obtained. Next, the process proceeds to step S2514.

  On the other hand, in step S2513, the read token is directly written in the feed file as the text constituting the normal XML description. Next, the process proceeds to step S2514. In step S2514, it is determined whether all tokens of the template data have been processed. If it has not been processed, the process returns to step S2501 to repeat the series of processing procedures. If it has been processed, the processing procedure returns.

  FIG. 25 is a diagram illustrating an example of a screen for setting a period for placing update information in an update information file. Displays a pull-down that sets the period for each event for the application and its license. For each pull-down, for example, [1 day / 2 days / 3 days / 4 days / 5 days / 6 days / 7 days / 10 days / 15 days / 30 days] can be selected. Reference numerals 2601 to 2605 are used to set a period to be treated as update information after the occurrence of each event of application installation / uninstallation, application start / stop start, license expiration warning, license invalidation, and application counter information. Is a pull-down. For example, in the case of the setting shown in FIG. 25, when a new application is installed, the information is posted in the update information file as update information for 15 days thereafter. When responding to an update information file acquisition request, delete an entry whose expiration date has passed from the update information file. The set period is stored as period information 1706B in FIG.

  FIG. 26 is a diagram illustrating an example of a feed file that syndicates application-related update information. The feed file illustrated in the figure is RSS 1.0 format XML data. This feed file is stored in the update information storage unit 1708 and can be acquired from the outside of the image processing apparatus 110 via the network by specifying the URI. Of the important descriptions, the already explained RSS 1.0 vocabulary is given the same reference numerals and the description thereof is omitted.

  Reference numeral 2307 denotes a declaration of markup language version information, which declares that this syndication data is described in XML 1.0. As described above, the RDF element 2201 is a top-level element of the XML document, and at the same time, declares a version of syndication data, and declares that the syndication data is in the RSS 1.0 format. A channel element 2202 is an element describing information relating to this distribution. The channel element includes a link element 2308 indicating the URI associated with the distribution, a title element 2207 indicating the name of the distribution, and a description element 2308 describing the outline of the distribution. The link element 2308 describes the URI of the top page of the Web application (remote UI) that the image processing apparatus 110 has.

  A date element 2301 describes the date and time when the feed data was generated. A generatorAgent element 2302 describes the software that generated the feed data. A subject element 2304 describes the category of the entry. A creator element 2305 describes a user, that is, an operator, related to entry generation. A date element 2306 describes the date and time when the entry was generated.

  The item element 2204 is an item for listing update data obtained by processing the update information entry. That is, the image processing apparatus 110 outputs the update data in a markup language notation format including a plurality of items. The item element 2204 includes a link element 2218 indicating the URI associated with the update information, a title element 2217 indicating the name of each update information, and a description element 2219 describing the outline of each update information. The link element 2218 describes the URI of a page that displays details of update information corresponding to the entry in the Web application (remote UI) of the image processing apparatus 110.

(Acquisition and use of provided service update information feed data)
FIG. 27 is a sequence diagram illustrating a communication and cooperation sequence in which the client uses the update information feed file provided by the image processing apparatus. An RSS reader 1701 that operates on the desktop computer 101, a Web browser 1709, and an HTTP server 1116 that operates on the image processing apparatus 110 cooperate through communication. The software modules of the RSS reader 1701 and the web browser 1709 are not necessarily provided on the desktop computer 101. For example, it may be deployed on another type of information processing apparatus or embedded apparatus, or may be deployed to operate on the image processing apparatus 110 itself or another image processing apparatus 120 or 130. Since the feed file for syndicating update information is described in a general-purpose XML format and can be specified and acquired by URI, the form, function, and system configuration of clients that use update information can be flexibly combined. be able to. Further, since the syndication data structure described above includes the link element 2308 in the channel element and the link element 2218 in the item element, it is easy to cooperate with the Web page and Web application provided by the image processing apparatus 110.

  In event 1, the user 1702 uses the RSS reader 1701 to select the RSS feed of the image processing apparatus to which attention is paid.

  In event 2, the RSS reader 1701 establishes communication with the HTTP server 1116 and transmits an RSS feed acquisition request. Communication is generally performed using an application protocol such as HTTP or HTTPS.

  In event 3, the HTTP server 1116 returns an update information feed file stored in the image processing apparatus to the RSS reader 1701 as a response to the HTTP request.

  In event 4, the RSS reader 1701 analyzes the acquired feed file, and formats and displays an entry that the user 1702 has not read yet. The displayed update information displays link information defined by the syndication XML format as a selectable anchor. Further, when hypertext such as HTML is included in the description of the update information entry, the hyperlink is displayed as a selectable anchor.

  In event 5, the user selects an anchor of a link included in the entry displayed on the RSS reader 1701.

  In event 6, the RSS reader 1701 performs inter-application communication with the Web browser 1701, and requests display of the resource specified by the URI described in the link.

  In event 7, the Web browser 1709 acquires the requested resource. If the location information of the URI that identifies the given resource points to the HTTP server 1116 of the image processing apparatus 110, communication is established with respect to the HTTP server 1116, and a resource acquisition request is transmitted. Communication is generally performed using an application protocol such as HTTP or HTTPS. For example, an acquisition request is made by designating a URI assigned to a Servlet operating on the JVM 1104 of the image processing apparatus 110.

  In event 8, the HTTP server 1116 returns the requested resource to the Web browser 1709 as a response to the HTTP request. The HTTP server 1116 reads the requested resource from the storage or dynamically generates it by a program. For example, when the resource specified in the acquisition request is Servlet, the acquisition request is transferred to the Servlet, and a response such as HTML generated by the Servlet as a processing result is returned.

  In event 9, the Web browser 1709 formats and displays the acquired resource.

  FIG. 28 is an example of a display screen of an update information feed displayed on a general feed reader. The feed reader shown in the figure is, for example, an RSS reader 1710 that operates on the desktop computer 101. The RSS feed list 2901 is a menu in which feed data of available syndications set in advance in the feed reader or discovered as a result of dynamic search by the feed reader are listed. Each item in the list corresponds to available feed data. When the user selects an item, the feed reader acquires the feed data, expands it, and displays it in the right pane. The highlight of an item indicates that the item has been selected. The feed title 2902 displays the title of the feed data in order to identify the feed data corresponding to the item. The unread number 2903 displays the number of unread entries included in the feed data corresponding to the item.

  Next, the right pane of the figure display screen will be described. In the right pane, information corresponding to the feed data selected in the RSS feed list 2901 is displayed. A feed summary 2904 displays an overall summary of feed data. The displayed information corresponds to the contents of the channel element 2202 in the RSS feed examples of FIGS. A feed title 2905 displays the title of feed data. This corresponds to the title element 2207 in the channel element 2202 in the RSS feed example. The displayed title is a hypertext anchor, and when the user selects it, the URI resource described in the link element 2208 is acquired and displayed in cooperation with the Web browser 1709. In this example, it is an anchor to the top page that provides the entrance of the Web application group of the image processing apparatus 110.

A feed logo image 2906 displays a logo image of feed data. Although omitted in the RSS feed example, it corresponds to the image element 2210 and the image element 2203. The displayed image data is a resource acquired from the URI described in the url element 2215. The displayed image is an anchor, and when the user selects it, the URI resource described in the link element 2216 is acquired and displayed in cooperation with the Web browser 1709. A feed summary 2907 displays a summary description of the feed data. This corresponds to the description element 2209 in the RSS feed example. As shown in this example, it is possible to flexibly design syndicated data by freely combining template variables to be replaced with various types of information held in the image processing apparatus and the format of feed data.
Update information entries 2908, 2909, and 2910 each display update information that is syndicated by a feed file. In the RSS feed example, it is indexed as a list of li elements 2213 of the items element 2211 and corresponds to each element listed in the item elements 2204, 2205, and 2206.

  The entry title 2911 displays the title of the update information entry. In the RSS feed example, it corresponds to the title element 2217. The displayed title is a hypertext anchor, and when the user selects it, the URI resource described in the link element 2218 is acquired and displayed in cooperation with the Web browser 1709. In this example, it is an anchor to the individual entry information page for browsing details of this update information entry. The entry update date 2912 displays the date when the update information entry event occurred. In the RSS feed example, this corresponds to the date element 2306.

  The entry description 2913 describes information on the update information entry. In the RSS feed example, it corresponds to the description element 2219. Since the entry description is structured by using images, quotations, tables, etc. as text marked up in HTML (XHTML), it is shaped and displayed so as to express (presentation) these structures. In addition, links to various resources including Web pages and e-mail addresses are embedded, and their anchors are also displayed. The displayed information is generated based on various information obtained through the template and various databases in the image processing apparatus and the device control class library 1106 in the generation of the RSS feed example. As shown in this example, it is possible to flexibly design syndicated data by freely combining template variables to be replaced with various types of information held in the image processing apparatus and the format of feed data. For example, the anchor described in the value column of the “detail” attribute of the table is a link to the detailed information page of this application. When the user selects this anchor, application detailed information as shown in FIG. 14 is provided. You can easily browse web pages. When the application related to the entry is a Web application, an anchor describing a link to a Web page for operating the application itself is embedded so that the update information can be used from the browsing screen with one action. Constitute.

  With the configuration and operation described above, the image processing apparatus according to the present embodiment, when the state of the designated data changes, shows a changed format and a predetermined format (in this embodiment, RSS1. 0) data is generated and saved. For this reason, it is possible to notify a remote computer of a change in data generated in the image processing apparatus by causing the computer or the like capable of interpreting and processing the data in the predetermined format to read the data. In particular, since the data is compliant with RSS, it is possible to easily and inexpensively monitor the state change of the image processing apparatus by causing a computer to execute a commercially available or free program equipped with an RSS reader function. In addition, the computer can poll the state change at intervals set such as one hour, one day, one week, or can be polled at a designated time. Moreover, since the data is described in XML, the processing is easy.

  Furthermore, as the state of the apparatus, a lot of information such as application installation and uninstallation, application start and stop, license expiration warning, license invalidation, and statistical information can be monitored. Furthermore, the monitoring target can be selected. It is also possible to specify a period for supplying state change information to the computer.

  Of course, the monitored events are not limited to these, and other events can be monitored. For example, setting changes important for security (switching of encryption / non-encryption, change of TCP / IP port settings, etc.) may be monitored.

[Second Embodiment]
FIG. 29 is a diagram showing a display example of a dedicated application that is displayed by performing feed file aggregation and statistical processing. The application shown in the figure runs on the desktop computer 101 or the like. It integrates multiple feed data and processes it together with the accumulation of feed data obtained in the past to generate a more graphical display. In the feed data, a syndication format such as RSS 1.0 is extended using an XML extensibility framework, and a dedicated value such as device counter information is embedded by including uniquely defined elements. The update information provided by the image processing apparatus is described in XML and can be acquired by referring to the URI. Therefore, the update information is applied not only to browsing with a general RSS feed reader but also to various uses such as this example. Can do.

[Third Embodiment]
(Generation and supply of feed data for updated information about boxes)
FIG. 30 is a block diagram illustrating a software structure for generating and supplying an RSS feed of box-related update information. A user 4201 is a user who operates a box, and performs operations such as adding, editing, and deleting a document with respect to a box function that is incorporated in the image processing apparatus 110 and is a document management system. A document input unit 4211 captures a document from the outside of the apparatus into the image processing apparatus 110. The document input unit 4211 adds the image page group read by the user 4201 by operating the scanner of the image processing apparatus 110 as a document file to the box function. Further, the document data transmitted from the remote to the image processing apparatus 110 by a communication protocol such as fax, IFAX, and e-mail is added to the box function as a document file.

  The user 4201 accesses the image processing apparatus 110, which is the same apparatus, via the built-in RSS reader 4210 operating on the image processing apparatus 110, and refers to the update information related to the box. The user 4201 accesses the image processing apparatus 110 that is the same apparatus via the embedded Web browser 211 that runs on the image processing apparatus 110, and browses resources and Web applications provided by the image processing apparatus 110.

  A software configuration for generating and supplying an RSS feed of box-related update information inside the image processing apparatus 110 will be described. A document operation interface 4203 provides an interface for operating the box function of the image processing apparatus 110. A box document management system 4204 is a database for a box function which is an embedded document management system of the image processing apparatus 110. Data stored in the database includes scanned and read document files, document files received by the communication function, document files input from other input paths such as generated by the PDL function, and thumbnail image files of each document. Including.

The syndication DB 4205 is a database for accumulating and managing data used for syndication of update information related to the box function of the image processing apparatus 110. The data to be stored and managed includes an update information entry that is generated by holding attribute information related to a change event (event) related to the structure of the box and a group of documents stored in the box.
The template DB 4206 is a database for accumulating and managing templates that provide templates of XML files used for syndication. The XML application for syndication conforms to specifications such as each version of RSS and Atom. A plurality of templates are prepared according to the type of information to be syndicated and the conforming specifications. Based on the template group stored and managed in the template DB 4206, the update information generation unit 4207 stores various data such as the configuration and status of the image processing apparatus 110 obtained from the data stored and managed in the syndication DB 4205 and the device control class library 1106. A template engine that generates an XML file used for syndication from the attribute is included. The update information generation unit 4207 stores the generated XML file (syndication data file such as RSS or Atom) in the update information (RSS) storage unit 4208.

  The update information (RSS) storage unit 4208 is a storage for accumulating XML files used for syndication. The update information storage unit 4208 holds a plurality of files that differ depending on the type of information to be syndicated. Also, a plurality of files described in formats such as RSS versions and Atoms are held in accordance with the conforming XML application specifications. The update information storage unit 4208 is mounted as a file system accessible by the HTTP server 212. Each file of the XML file group stored in the update information storage unit 4208 is specified by a unique URL when viewed from the HTTP client group connected to the HTTP server 212. When the HTTP client connects to the HTTP server 212 and requests acquisition of the resource specified by this URL, the HTTP server 212 reads out the XML file corresponding to the URL specified in the acquisition request from the update information storage unit 4208, and HTTP Send to client.

  In response to a request by HTTP or HTTPS from an HTTP client, the HTTP server 212 transfers various resource data held in the image processing apparatus 110 as a response. Resources accessed by the client by HTTP include static data files such as HTML and images held in the non-volatile memory inside the image processing apparatus 110 such as the HDD 304 (including XML files held in the update information image storage unit 4208). ) And data dynamically generated by a program executed by the CPU 301. Examples of data dynamically generated in response to an HTTP request include HTML generated by various Web application groups such as a remote UI 4212.

  A remote UI 4212 is a Web application provided by the image processing apparatus 110, and provides a function similar to that of the document operation interface 4203 to a client such as a connected Web browser.

  The embedded RSS reader 4210 is an embedded application program for acquiring and formatting and displaying an XML format for syndication such as each version of RSS and Atom. Display and operation are performed by the operation unit 122 of the image processing apparatus 110. Many websites such as news distribution sites, information providing sites, and web logs (weblogs or blogs) on the Internet provide syndication data in addition to site content to syndicate new articles on the site. . Using the RSS reader 4210, the user 4201 can efficiently browse the titles and contents of newly arrived articles on these Internet sites. The RSS reader 4210 can access syndication data not only in the Internet but also in an intranet as long as it is disclosed as a resource that can be specified and acquired by a URI. When a URI for identifying syndication data stored in the update information storage unit 4208 of the image processing apparatus 110 is specified and an HTTP acquisition request is transmitted from the RSS reader 4210 to the HTTP server 212, the HTTP server 212 receives the HTTP acquisition request. As a response, syndication data stored in the update information storage unit 4208 can be received. In some cases, the hyperlink specified by the URI is included in the syndication data that is displayed by the RSS reader 4210. When the user 4201 selects a specific hyperlink on the display of the RSS reader 4210, the RSS reader 4210 cooperates with the embedded Web browser 211 to acquire and display the URI on the Web browser 211. When the embedded RSS reader 4210 receives a request from another embedded application through inter-application communication within the image processing apparatus 110, the embedded RSS reader 4210 acquires the syndication data of the URI specified in the request and displays it on the operation unit 122 of the image processing apparatus 110. .

  The Web browser 211 is provided with various resources provided in a form that can be specified by a URI in a Web server on the Internet or an intranet, for example, document data in markup languages such as HTML and XHTML, and various multimedia data (still images, Video, audio, etc.), properly shaped, displayed graphically or read aloud. Data acquisition is performed mainly by a communication protocol such as HTTP or FTP. The Web browser 211 is a client-server model client side in terms of communication protocol, and is positioned as an HTTP client, for example. When the hyperlink specified by the URI is included in the data browsed by the user 4201, when the user selects the anchor of the specific hyperlink, the Web browser 211 acquires and displays the resource of the specified URI. . In some cases, data is sent (posted) from the Web browser 211 to resources on the Web server side using a markup document form specification such as HTML. The user 4201 can also use the Web browser 211 to request acquisition by designating a URI that identifies the remote UI 4212 of the image processing apparatus 110 that is the same apparatus, for example. The HTTP server 212 of the image processing apparatus 110 internally transfers this acquisition request to a remote UI 4212 via an interface such as CGI (common gateway interface), and further sends a response such as HTML generated as a processing result by the remote UI 4212 to the Web browser 211. Return it. When the embedded Web browser 211 receives a request from another embedded application through inter-application communication within the image processing apparatus 110, the embedded Web browser 211 acquires the URI resource specified in the request and displays it on the operation unit 122 of the image processing apparatus 110.

  Next, the software configuration inside the desktop computer 101 will be described. The image processing apparatus 110 and the desktop computer 101 are network-connected, and software running on each communicates data with each other according to a protocol such as HTTP or HTTPS. A user 4202 is a user who accesses the image processing apparatus 110 via the RSS reader 4230 operating on the desktop computer 101 and refers to update information related to the box. A user 4202 accesses the image processing apparatus 110 via a Web browser 4229 that runs on the desktop computer 101, and browses resources and Web applications provided by the image processing apparatus 110. The function of the RSS reader 4230 is the same as that of the embedded RSS reader 4210, and the function of the Web browser 4229 is the same as that of the embedded Web browser 211.

  In this embodiment, the RSS reader 4210 and the Web browser 4209, and the RSS reader 4230 and the Web browser 4229 are each configured as a single application program, but are configured as a single application program having both functions. Also good. The RSS reader 4230 and the Web browser 4229 have been described as operating on the desktop computer 101. However, the RSS reader 4230 and the Web browser 4229 are configured to operate on various general-purpose information processing apparatuses including not only desktop computers but also portable computers such as PDAs. May be. Or you may comprise so that it may operate | move on various built-in apparatuses, such as a mobile telephone. A technology for realizing the RSS reader function as a distributed system by combining a front-end Web browser and a back-end Web application is also widely known (for example, Bloglines <http://www.bloglines.com). />). If a Web application providing such an RSS reader function is used, the function of the embedded RSS reader 4210 can be substituted by a combination of the embedded Web browser 211 and the Web application. The Web application that provides the RSS reader function may be configured to run on an external server computer, or may be configured as one of the Web applications that operate inside the image processing apparatus 110 as with the remote UI 4212. The embedded RSS reader 4210 may be configured to read the feed file directly from the update information storage unit 4208 without using network communication when the feed file to be acquired is in the same image processing apparatus 110.

  FIG. 21 is a diagram showing an example of the structure of an XML format used for syndication of update information of the image processing apparatus. An XML file stored in the update information storage unit 1708 and specified by a URI is an XML document that describes various data updates related to the embedded application of the image processing apparatus and information on various events that occur related to the embedded application of the apparatus. It is. This XML document format provides a plurality of types corresponding to various formats used by general Web sites to distribute site update information. The image processing apparatus 110 supports each version of RSS and XML formats such as Atom. Here, description will be given taking RSS 1.0 as an example. In FIG. 21, the inclusion relationship of each block means the inclusion relationship of XML elements.

  The RDF element 2201 is the top element of the XML document. The RDF element includes a channel element 2202, an image element 2203, and item elements 2204, 2205, and 2206. The channel element 2202 describes basic information related to the entire update information. This element corresponds to an RDF-like subject node. The content of the channel element includes a title element 2207, a link element 2208, a description element 2209, an image element 2210, and an items element 2211. A title element 2207 represents the title of this update information. A link element 2208 represents the URI of the site handled by this update information. A description element 2209 describes the contents and functions of the site handled by the update information. The image element 2210 describes a URI that identifies an image resource such as a logo of a site handled by the update information. Details are described in an image element 2203 described later. The items element 2211 provides an index of the item element groups 2204, 2205, and 2206. Each update information URI is indicated by the li element 2213 listed in the contents of the Seq element 2212. The image element 2203 represents an image such as a logo. The content includes a title element 2214, a url element 2215, and a link element 2216. The title element 2214 represents the title of the image and may be used as alternative text for the image. A url element 2215 describes the URI of the image resource. The link element 2216 describes a URI used as a link destination when displaying a hyperlink with this image as an anchor. The item elements 2204, 2205, 2206, etc. are a plurality of elements each representing individual update information. The content includes a title element 2217, a link element 2218, and a description element 2219. The title element 2217 describes the title of the update information. A link element 2218 describes the URI of the update information. A description element 2219 describes the description of the update information.

  FIG. 31 is a flowchart of a box document reading process procedure in the image processing apparatus. In step S4301, a box selection process by the user is accepted. In step S4302, document information input by the user is accepted. Here, the document information is a document name of a document to be read and an explanation for the document, and the user inputs using a button on the operation screen. The input screen appears when “box” is selected from the screen of FIG. In step S4303, it is determined whether the start button has been pressed. If the start button is depressed, the process proceeds to step S4304. If not depressed, the process returns to S4302 to accept input of document information.

  In step S4304, the original is read and stored in the box. In step S4305, the thumbnail image is generated by reducing the resolution of the read image and stored. In step S4306, a box update information entry is generated. That is, an update information entry describing the detailed information of the read document is generated. The update information entry includes the generated thumbnail image. In step S4307, the generated update information entry is stored in the syndication DB. In step S4308, an RSS feed file generation process is called to generate a new RSS feed file from the syndication DB that has been modified by adding a new update information entry.

  FIG. 32 is a flowchart of a box document editing process procedure in the image processing apparatus. In step S4401, a list of documents in the box is displayed. In step S4402, a document selection by the user is accepted. The following operations target the selected document. In step S4403, an operation instruction from the user is accepted. In step S4404, conditional branching is performed according to the type of operation. If the selected operation type is document insertion, the process proceeds to step S4405. If the selected operation type is deletion, the process proceeds to step S4407. If the selected operation type is combined and saved, the process proceeds to step S4411.

  In step S4405, a screen for instructing insertion is displayed. In the insertion instruction screen, the user inputs a document to be inserted, a position to be inserted, a document name after insertion, and the like. In step S4406, a document insertion process is performed to generate a new document. Next, the process proceeds to step S4413. In step S4407, a dialog for confirming to the user whether or not the deletion can be performed is displayed, and the user input is waited for. If the user cancels, the process returns to S4403. If the user is OK, the process proceeds to S4408. In step S4408, the selected document is erased. Next, the process proceeds to step S4409.

  In step S4409, a template used to generate a syndication data file (feed file) is extracted from the template DB 1706, and it is determined whether or not a link to a thumbnail image is included. If the link to the thumbnail image is included, the process proceeds to step S44013. If the link to the thumbnail image is not included, the process proceeds to S4413. In step S4410, the thumbnail image is erased. Next, the process proceeds to step S4413. In step S4411, a screen for instructing combination storage is displayed. In the combination instruction screen, the user inputs a document to be combined, a combination order, a document name after combining, and the like. In step S4412, the combined storage process is performed to generate a new document. Next, the process proceeds to step S4413.

  In step S4413, an update information entry corresponding to the process executed in the previous step is generated. That is, an update information entry describing the detailed information of the event is generated in response to an event such as document insertion, document deletion, and combined storage. In step S4414, the generated update information entry is stored in the syndication DB. In step S4415, an RSS feed file generation process is called to generate a new RSS feed file from the syndication DB that has been modified by adding a new update information entry.

  It is possible to select and set the importance level of [Important / Normal / Low importance] when accumulating or editing a box document, and update information is updated according to the importance. It is possible to set the period for the information file.

  FIG. 33 is a diagram illustrating an example of a screen for setting a period for placing update information in an update information file. Displays a pull-down that sets the period for each document importance. For each pull-down, for example, [1 day / 2 days / 3 days / 4 days / 5 days / 6 days / 7 days / 10 days / 15 days / 30 days] can be selected. 4501 is a document set as [important], 4502 is a document set as [normal], 4503 is a document set as [low importance], and sets a period to be treated as update information after an event occurs This is a pull-down. When responding to an update information file acquisition request, delete an entry whose expiration date has passed from the update information file. In the inbox, it is possible to set a period for placing the update information in the update information file according to the transmission source of the received document. This period information is also stored in the same manner as in the first embodiment and is referred to when generating syndication data.

  FIG. 34 is a diagram showing an example of a screen for setting a period during which the update information of the document in the inbox is placed in the update file. Reference numerals 4601, 4602, and 4603 are areas for inputting a transmission source. When each area is depressed, a soft keyboard screen (not shown) is displayed and the transmission source can be input. Reference numerals 4604, 4605, and 4606 denote pull-down menus for setting a valid period for each transmission source. For each pull-down, for example, [1 day / 2 days / 3 days / 4 days / 5 days / 6 days / 7 days / 10 days / 15 days / 30 days] can be selected. When responding to an update information file acquisition request, delete an entry whose expiration date has passed from the update information file.

  FIG. 35 is a diagram illustrating an example of a feed file (ie, syndication data) for syndicating box-related update information. The feed file illustrated in the figure is RSS 1.0 format XML data. This feed file is stored in the update information storage unit 4208, and can be specified and acquired by the URI from outside or inside the image processing apparatus 110. Of the important descriptions, the already explained RSS 1.0 vocabulary is given the same reference numerals and the description thereof is omitted. The update information feed data for syndication generated by the template in the figure is an XML application in the RSS 1.0 format, and therefore has module extensibility using the XML namespace. That is, necessary information can be easily added to syndication feed data in combination with other XML vocabularies. For example, the following are combined from the DCMME properties of Dublin Core, which are frequently used as standard metadata description elements.

  date elements 4701 and 4706, subject elements 4704, and creator elements 4705. Also, a generatorAgent element 4702 is combined from the Admin module. A date element 4701 describes the date and time when the feed data was generated. A generatorAgent element 4702 describes the software that generated the feed data. A subject element 4704 describes the category of the entry. A creator element 4705 describes a user, that is, an operator, related to entry generation. A date element 4706 describes the date and time when the entry was generated. Thus, one of the great effects of the present embodiment is that it becomes easy to flexibly and strictly expand the data format for feeding update information.

(Get and display update information feed data)
FIG. 36 is an example of a box document update information feed display screen displayed on the operation panel of the image processing apparatus. The RSS feed list 5301 is a menu that lists available syndication feed data that is preset in the feed reader or discovered as a result of a dynamic search by the feed reader. Each item in the list corresponds to available feed data. When the user selects an item, the feed reader acquires the feed data, expands it, and displays it in the right pane. The highlight of an item indicates that the item has been selected.

  In the case of being automatically activated by a box document list display operation, the image processing apparatus itself is activated with the box document feed data selected. At this time, the RSS feed list 5301 area may not be displayed. The feed title 5302 displays the title of the feed data in order to identify the feed data corresponding to the item. The unread number 5303 displays the number of unread entries included in the feed data corresponding to the item. Next, the right pane of the figure display screen will be described. In the right pane, information corresponding to the feed data selected from the RSS feed list 5301 is displayed. A feed summary 5304 displays an overall summary of feed data. The displayed information corresponds to the contents of the channel element 2202 in the RSS feed example of FIG.

  A feed title 5305 displays the title of the feed data. This corresponds to the title element 2207 in the channel element 2202 in the RSS feed example. The displayed title is a hypertext anchor. When the user selects it, the URI resource described in the link element 2208 is acquired and displayed in cooperation with the Web browser. In this example, it is an anchor to the top page that provides the entrance of the Web application group of the image processing apparatus 110. A feed logo image 5306 displays a logo image of feed data. Although omitted in the RSS feed example, it corresponds to the image element 2210 and the image element 2203. The displayed image data is a resource acquired from the URI described in the url element 2215. The displayed image is an anchor, and when the user selects it, the Web browser is activated and the URI resource described in the link element 2216 is acquired and displayed.

  A feed summary 5307 displays a summary description of feed data. This corresponds to the description element 2209 in the RSS feed example. As shown in this example, it is possible to flexibly design syndicated data by freely combining template variables to be replaced with various types of information held in the image processing apparatus and the format of feed data. Update information entries 5308, 5309, and 5310 each display update information that is syndicated by a feed file. In the RSS feed example, it is indexed as a list of li elements 2213 of the items element 2211 and corresponds to each element listed in the item elements 2204, 2205, and 2206.

  The entry title 5311 displays the title of the update information entry. In the RSS feed example, it corresponds to the title element 2217. The displayed title is a hypertext anchor, and when the user selects it, the Web browser is activated and acquires and displays the URI resource described in the link element 2218. In this example, it is an anchor to the individual entry information page for browsing details of this update information entry.

  The entry update date and time 5312 displays the date and time when the event of the update information entry occurred. In the RSS feed example, this corresponds to the date element 2306. The entry description 5313 describes information on the update information entry. In the RSS feed example, it corresponds to the description element 2219. Since the entry description is structured by using images, quotations, tables, etc. as text marked up in HTML (XHTML), it is shaped and displayed so as to express (presentation) these structures. In addition, links to various resources including Web pages and e-mail addresses are embedded, and their anchors are also displayed.

  The displayed information is generated based on various information obtained through the template and various databases in the image processing apparatus and the device control class library 1106 in the generation of the RSS feed example. As shown in this example, it is possible to flexibly design syndicated data by freely combining template variables to be replaced with various types of information held in the image processing apparatus and the format of feed data. In the example of this figure, a document description text and a thumbnail image of the document are displayed.

  FIG. 37 is an example of an inbox update information feed display screen displayed on a general feed reader. The feed reader shown in the figure is, for example, an RSS reader 1710 that operates on the desktop computer 101. Except that the entry description 5414 is the contents of the update information of the inbox, it is the same as FIG. 36 and will not be described in detail here. The entry description includes an event type, a transmission source, and a thumbnail image of the received document.

  FIG. 38 is an example of an update information feed display screen regarding deletion of a box document displayed on a general feed reader. Except that the entry description 5514 is the contents of the deletion information of the box document, it is the same as FIG. 36, and therefore will not be described in detail here. The entry description 5514 includes the name of the user who performed the deletion process and a thumbnail image of the document. The document may be deleted by a user operation, or may be automatically deleted after a preset storage period has elapsed. In either case, the document is recorded as an update information entry.

[Fourth Embodiment]
When the user performs an editing operation such as registration, editing, or deletion on the address book, an update information entry may be created and stored in the syndication DB, and a feed file generation process may be performed. FIG. 39 shows an example of an address book update information feed display screen displayed on the operation panel of the image processing apparatus. Except that the entry description 6014 is the contents of the update information of the address book, it is the same as FIG. 36, and therefore will not be described in detail here. The entry description 6014 includes the name of the user who performed the address book update process and the contents of the change.

[Fifth Embodiment]
An update information entry is created and stored in the syndication DB when the user performs editing operations such as registration, editing, and deletion on the bulletin board function of the image processing apparatus, and feed file generation processing is performed. You can also FIG. 40 is an example of a bulletin board update information feed display screen displayed on the operation panel of the image processing apparatus. The bulletin board function is a function for displaying a set character string on the operation panel and the top page of the remote UI in order to transmit a message from an administrator or the like to other users of the apparatus. Except that the entry description 6514 is the content of the update information on the bulletin board, it is the same as FIG.

[Other Embodiments]
In all of the first to fifth embodiments, a scanner function and a printer function, and a digital composite apparatus (image processing apparatus) having both a copying function, a facsimile function, an electronic file function, etc. using them in combination are described. . That is, in these embodiments, the fact that the data in the apparatus is updated and the function of providing an outline of the update to the computer connected to the apparatus are described. However, not only the image processing apparatus but also other embedded systems connected to the network, that is, network devices, can similarly provide information related to the update of the internal data to the connected computer. For example, among household appliances and the like, some recording apparatuses that perform television recording have a function of making a recording reservation by remote access from a computer. In this apparatus, it is possible to provide information related to recording, for example, the fact of reservation or the completion of recording by means of an RSS feed as a state change in the same manner as in the first to fifth embodiments. Of course, the present invention can be applied not only to these devices but also to devices that can be connected to a network, such as printer scanners, digital still cameras, video cameras, and the like.

  In addition, the image processing apparatus according to the fifth embodiment of the first embodiment provides information indicating a change in state to a computer connected to the same network (LAN). However, since the provision of status (ie, specific data) information in these embodiments is realized in the application layer, it can be realized beyond the network. That is, even if another network (for example, the Internet) is interposed between the computer and the image processing apparatus, the image processing apparatus can provide information to the computer.

  Although the embodiment of the present invention has been described based on RSS 1.0, it is understood that RSS 0.9 (RDF Site Summary), RSS 0.91 (Rich Site Summary), RSS 0.92, RSS 2.0 (Really Simple Syndication). Any other version of RSS such as), Atom, etc., may be used as long as it is a format for distributing and notifying content update information / summary information, and it goes without saying that it includes a format for new syndication derived in the future.

  Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus. It is also achieved by reading and executing the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the novel function of the present invention, and the storage medium and program storing the program code constitute the present invention. The storage medium for supplying the program code is, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW. DVD + RW, magnetic tape, nonvolatile memory card, ROM, etc. can be used. Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. Includes a case where part or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing.

  Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. This includes the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

1 is a block diagram showing an overall configuration of an image processing system according to an embodiment of the present invention. It is a block diagram which shows the structure of the software performed with an image processing apparatus. It is a block diagram which shows the hardware constitutions of an image processing apparatus. It is a perspective view which shows the external appearance of an image processing apparatus. It is a top view which shows the structure of the operation part of an image processing apparatus. It is a block diagram which shows the internal structure of the operation part of an image processing apparatus, and operation part I / F corresponding to the internal structure of a control unit. It is a figure which shows an example of the standard operation screen displayed on the operation part of an image processing apparatus. FIG. 3 is a block diagram illustrating an internal configuration of a Web browser module illustrated in FIG. 2. It is a figure which shows the structure of the screen displayed when a web browser function is selected in the LCD display part shown in FIG. 2 is a diagram illustrating a software configuration for managing embedded applications in an image processing apparatus. FIG. It is a figure showing an example of the SMS login screen displayed on the web browser on a network. It is a figure showing an example of the application list screen of SMS displayed on the web browser on a network. It is a figure showing an example of the application installation screen of SMS displayed on the web browser on a network. It is a figure showing an example of the application detailed screen of SMS displayed on the web browser on a network. It is a figure showing an example of the license management screen of SMS displayed on the browser on a network. FIG. 3 is a block diagram illustrating a software structure for generating and supplying an RSS feed of application related update information. It is a block diagram which shows the data structure of syndication DB. It is a figure which shows the example of the screen for setting the object which monitors update information. It is a flowchart of a processing procedure of application management in the image processing apparatus. 6 is a flowchart of a processing procedure for monitoring a change in a license condition state accompanying an operation of the image processing apparatus. It is a figure which shows the structure of an example of the XML format used for the syndication of the update information of an image processing apparatus. It is an example of the template stored in template DB. It is a flowchart which shows the process sequence of the syndication data production | generation by an update information production | generation part. It is a flowchart which shows the process sequence of the template analysis and syndication data output by an update information generation part. It is a figure which shows the example of the screen which sets the period which puts update information in an update information file. It is a figure which shows an example of the feed file which syndicates application relevant update information. FIG. 10 is a sequence diagram illustrating a communication and cooperation sequence in which a client uses an update information feed file provided by an image processing apparatus. It is a figure which shows an example of the display screen of the update information feed displayed on a general feed reader. It is a figure which shows the example of a display of the exclusive application displayed after performing the aggregation and statistical process of a feed file. FIG. 3 is a block diagram illustrating a software structure for generating and supplying an RSS feed of box related update information. It is a flowchart of a box document reading process procedure in the image processing apparatus. It is a flowchart of a box document editing process procedure in the image processing apparatus. It is a figure which shows the example of the screen which sets the period which puts update information in an update information file. It is a figure which shows the example of the screen which sets the period which places the update information of the document of a receiving box on an update file. It is a figure which shows an example of the feed file which syndicates box related update information. It is a figure which shows an example of the display screen of the box document update information feed displayed on the operation panel of an image processing apparatus. It is a figure which shows an example of the display screen of the update information feed of a receiving box displayed on a general feed reader. It is a figure which shows an example of the display screen of the update information feed regarding the deletion of the box document displayed on a general feed reader. It is a figure which shows an example of the display screen of the address book update information feed displayed on the operation panel of an image processing apparatus. It is a figure which shows an example of the display screen of a bulletin board update information feed displayed on the operation panel of an image processing apparatus.

Explanation of symbols

100 LAN (network)
101 Desktop computer (external device, information processing device)
110, 120, 130 Image processing device 111, 121, 131 Control unit (remote operation means, remote operation request reception means, remote operation start confirmation means, user authentication means)
112, 122, 132 Operation unit (operation means)
113, 123, 133 Scanner 114, 124, 134 Printer 301 CPU
302 RAM
303 ROM
304 HDD
305 Image Bus Interface (Image Bus I / F)
306 Operation unit I / F
307 System bus 308 Network interface (Network, communication means)
309 Modem (MODEM)
310 Image bus 311 Raster image processor (RIP)
312 Device I / F unit 313 Scanner image processing unit 314 Printer image processing unit 315 Image rotation unit 316 Image compression unit

Claims (5)

In the structure of syndication data in markup language notation representing update information that can be used in an information processing apparatus or image processing apparatus,
Declaration of version information of the markup language;
Declaration of version information of the syndication data;
An element describing information related to the delivery of the syndication data;
A syndication data structure having elements for enumerating the update information,
The syndication data is distributed as update information of data stored in an image processing apparatus having a printing unit or an image reading unit connected to a network and communicating with an external device. Construction. The element describing the information related to the delivery is:
A link element indicating a URI associated with the delivery;
A title element representing the name of the distribution;
The syndication data structure according to claim 1, further comprising: at least one element of description elements explaining an outline of the distribution. The element for listing the update information is:
A link element indicating a URI associated with each update information;
A title element representing the name of each update information;
The syndication data structure according to claim 1, further comprising at least one element of description elements explaining an outline of each update information.   4. The syndication data structure according to claim 3, wherein the URI associated with the distribution is a URI of a Web site possessed by the image processing apparatus.   The URI associated with the update information indicates a specific page of the website of the image processing apparatus, and the specific page is a page representing update information of data stored in the image processing apparatus. The structure of the syndication data according to claim 4.