JP5091802B2 - Image forming apparatus and image forming system - Google Patents

Description

  The present invention relates to an image forming apparatus and an image forming system.

  An image forming apparatus such as a multifunction peripheral is provided with an operation panel, and the operation panel includes a display device and an input device. A user interface screen is displayed on the display device. The user interface screen mainly includes components such as buttons (see, for example, Patent Document 1).

Such a user interface screen is displayed by program control. A program for displaying a user interface screen is usually generated by compiling a source file described in a programming language such as C language or JAVA using an API (Application Program Interface) included in the image forming apparatus itself. The The program is stored in advance in the image forming apparatus as an executable program.
JP 2006-92302 A

  As described above, the program for displaying the user interface screen is generated by compiling a source file described in a programming language. Therefore, when customizing the user interface screen, a development environment for generating an executable program from the programming language is required, and it is difficult for a person other than the programmer to change the source file.

  SUMMARY An advantage of some aspects of the invention is that it provides an image forming apparatus and an image forming system capable of easily customizing a user interface screen of the image forming apparatus.

  In order to solve the above problems, the present invention is configured as follows.

An image forming apparatus according to the present invention includes a display device for displaying a user interface screen, a data storage device for storing user interface data in which attributes of components in the user interface screen are described in text, and parsing the user interface data To identify the attributes of the component, and to display the UI interface that reflects the attribute of the component on the display device, the syntax definition of the interface part of the editing service for the user interface data, and the service A message processing unit that parses a message according to service definition data including a protocol specification of the message to be processed, a control unit that executes an editing service according to a request obtained from the message based on a result of the syntax analysis of the message processing unit, And a receiving means for receiving the message via the data network. The user interface data is described in XML according to the syntax definition described in the schema data, the service definition data refers to the schema data, the message processing unit includes service definition data, and service definition Parse the message according to its schema data referenced in the data.

Thus, the user interface can be customized by editing the text-format user interface data. Therefore, the user interface screen of the image forming apparatus can be easily customized. Further, since the image forming apparatus edits user interface data as one of the services, the user interface data can be edited by a message from the outside without directly operating the image forming apparatus. Therefore, the user interface screen of the image forming apparatus can be easily customized.

The image forming apparatus according to the present invention, in addition to the image forming equipment described above may be as follows. In this case, the protocol specified in the service definition data is SOAP, and the receiving means receives the message by HTTP.

  The image forming apparatus according to the present invention may be configured as follows in addition to any of the image forming apparatuses described above. In this case, the service definition data is XML data described in WSDL.

  The image forming apparatus according to the present invention may be configured as follows in addition to any of the image forming apparatuses described above. In this case, the user interface data and the message are described in XML, and the control unit updates the user interface data with the XML text of the component attribute extracted by the message processing unit.

  This eliminates the need to convert the message into user interface data.

An image forming system according to the present invention includes an image forming apparatus connected to a computer network, and a terminal device connected to the computer network. An image forming apparatus includes: a display device that displays a user interface screen; a data storage device that stores user interface data in which attributes of components in the user interface screen are described in text; and a component that parses user interface data A UI data analysis unit that displays a user interface screen reflecting the attribute of the component and reflecting the attribute of the component, a receiving unit that receives a message with a predetermined communication protocol via a computer network, and user interface data and a message processing unit which performs parsing of the message according to the service definition data including the designation of the message to be used in the syntax definition and service interface portion of the editing service protocols against the, as a result of the syntactic analysis of the message processing unit And a control section for executing editing service according to the request obtained from the message. The terminal device has transmission means for transmitting a message with a predetermined communication protocol via a computer network. The user interface data is described in XML according to the syntax definition described in the schema data, the service definition data refers to the schema data, the message processing unit includes service definition data, and service definition Parse the message according to its schema data referenced in the data.

  Thus, the user interface can be customized by editing the text-format user interface data. Further, since the image forming apparatus edits user interface data as one of the services, the user interface data can be edited by a message from the outside without directly operating the image forming apparatus. Therefore, the user interface screen of the image forming apparatus can be easily customized.

In addition to the above-described image forming system, the image forming system according to the present invention may be configured as follows. In this case, the data storage device stores the schema data. The terminal device includes a schema data acquisition unit that acquires part or all of the schema data from the image forming apparatus and identifies one or more items of the attribute of the component. The transmission means transmits a message for setting a value in a part or all of one or a plurality of items specified by the schema data acquisition unit.

  Thereby, the customization can be executed even if the attribute items of the component parts are not held in the terminal device in advance.

In addition to any of the image forming systems described above, the image forming system according to the present invention may be as follows. In this case, the data storage device stores the schema data. The terminal device includes a schema data acquisition unit that acquires a part or all of the schema data from the image forming apparatus and identifies one or a plurality of allowable values for the component attributes. The transmission means transmits a message for setting a value selected from one or more allowable values specified by the schema data acquisition unit as an attribute of the component.

  Thereby, the customization can be executed even if the terminal device does not hold the allowable value of the attribute of the component in advance.

In addition to the above-described image forming system, the image forming system according to the present invention may be configured as follows. In this case, message is written in XML, schema data is XML data described in XML schema, the control unit includes a user interface in XML text attribute of the component extracted by the message processing unit Update the data.

  As a result, customization can be executed even if the terminal device does not hold the syntax definition of the message in advance.

  In addition to the above-described image forming system, the image forming system according to the present invention may be configured as follows. In this case, the data storage device stores a plurality of template files each including default data of the user interface screen. The transmission means designates one template file among a plurality of template files, and sends a message having the default data of the designated template file as data of one user interface screen in the user interface data.

  Thereby, complicated customization can be easily performed by using a template.

  According to the present invention, the user interface screen of the image forming apparatus can be easily customized.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of an image forming system including a multifunction machine 1 as an image forming apparatus according to an embodiment of the present invention. In this system, the multifunction device 1 is connected to a computer network 2 and is used by a user who operates a terminal device 3 connected to the computer network 2 or an operation panel 11 of the multifunction device 1. For this reason, when execution of a service is requested by a user operation, request and response messages are transmitted and received between the terminal device 3 and the multifunction device 1 or inside the multifunction device 1.

  In FIG. 1, the multifunction device 1 includes an operation panel 11, a printing device 12, an image reading device 13, a facsimile device 14, a data storage device 15, a communication device 16, and a computer 17.

  The operation panel 11 is a user interface device having a display device 11a such as a liquid crystal display and an input device 11b that electrically detects a physical user operation. As the input device 11b, a key switch, a transparent touch panel arranged on the screen of the display device, or the like is used.

  The printing device 12 is an internal device that prints a document image based on document data generated by the image reading device 13, document data stored in a document box (not shown), document data received from the terminal device 3, and the like. . The document data is image data in a predetermined format.

  The image reading device 13 irradiates light on one or both sides of a document fed by an automatic document feeder or a document placed by a user and receives reflected light or the like to read an image of the document. An internal device that outputs document data.

  The facsimile apparatus 14 has a modem, generates a facsimile signal from the document data generated by the image reading apparatus 13 or the document data stored in the document box, transmits the facsimile signal via a telephone line, and transmits the facsimile signal. It is an internal device that receives and generates document data from the received signal.

  The data storage device 15 is a device for storing service definition data 15a, schema data 15b, user interface data 15c, template file 15d, a program (not shown) executed by the computer 17, document data, and the like. As the data storage device 15, a device that drives a readable / writable recording medium such as a hard disk drive or a nonvolatile memory is used.

  The service definition data 15a is text data including a syntax definition of an interface part that defines a service call, a return value thereof, and the like, and further includes specification of a protocol of a message used for the service. The service definition data 15a is described in XML (eXtensible Markup Language), for example. Further, the service definition data 15a is described in, for example, WSDL (Web Services Description Language). The service definition data 15a is data including a syntax definition, and is not a message that is actually transmitted / received. The service definition data 15a may be stored as one file or may be stored as a plurality of files. The service definition data 15a uses a schema language for description of syntax definition. In this embodiment, the service definition data 15a uses an XML schema for description of the syntax definition. In the service definition data 15a, the syntax definition is described directly in the XML schema, or an external A reference for reading and indirectly using the schema data 15b is described.

  The schema data 15b is external schema data referred to in the service definition data 15a. The schema data 15b is text data described in a predetermined language. The schema data 15b is stored as one or more data files.

  FIG. 2 is a diagram illustrating an example of the service definition data 15a described in WSDL. FIG. 3 is a diagram showing an example of schema data 15b referred to by service definition data.

  The service definition data 15a shown in FIG. 2 includes the syntax definition of the editing service of the user interface data 15c. In the editing service, it is possible to change, add, and delete components on the user interface screen in the user interface data 15c. The service definition data 15a shown in FIG. 2 includes one WSDL definition element. There is a WSDL types element in the definitions element. In the types element, an include element refers to “panel.xsd” as shown in FIG. 3, which is external schema data 15b. Within the definitions element, the definition of the request message and the response message, which are service interface parts, is described in the WSDL message element and portType element. Further, in the portType element, a plurality of operations that can be requested from the multifunction device 1 are described by a plurality of operation elements. In FIG. 2, an operation element for adding a button is described on the user interface screen. In the operation element, “button_request” is defined as a request message, and “button_response” is defined as a response message. . In addition, an operation element for deleting the button from the user interface screen, an operation element for updating the attribute of the button on the user interface screen, and the like are described. In addition, operation elements for addition, deletion, and update of other components (for example, list box, text box, etc.) included in the user interface screen are included.

  In the definitions element, the protocol of the message used in the service is specified in the WSDL binding element. In the binding element shown in FIG. 2, SOAP is specified as a protocol used for the message.

  Further, the schema data 15b shown in FIG. 3 includes a request message (button_request) syntax definition and a response message syntax definition (not shown), and parameter allowable values used in the message (not shown). )) Is described. The message syntax definition is described as an element element and a complexType element of the XML schema (xsd). The definition of the allowable value of the parameter is described as a simpleType element of the XML schema (xsd). Further, in this embodiment, the schema data 15b describes a syntax definition for describing the attributes of the component parts of the user interface screen in the user interface data 15c. This syntax definition is also used when describing the attributes of the components of the user interface screen in the message. This syntax definition includes an attribute item included in the component and / or a value (allowable value) that can be set in the attribute item.

  Thus, the service definition data 15a is stored in advance for each service. Further, external schema data 15b is stored in advance as required.

In addition, the user interface data 15c describes the attributes of the components in the user interface screen displayed on the display device 11a of the operation panel 11 in text.
When a plurality of user interface screens are used, the attributes of the components included in the user interface screen are described for each user interface screen. The user interface data 15c is described in XML, and is described according to the syntax definition described in the schema data 15b. FIG. 4 is a diagram illustrating an example of a user interface screen. The user interface screen shown in FIG. 4 includes “setting” text, “copy” button, “facsimile” button, and “printer” button as components. FIG. 5 is a part of the user interface data 15c describing the user interface screen shown in FIG. As shown in FIG. 5, one user interface screen is described by one screen element, and as a child element of the screen element, a screen_name element including the name of the user interface screen, a screen_title element including an attribute of “setting” text, and Three button elements including attributes of a “copy” button, a “facsimile” button, and a “printer” button are described. The button element includes, as child elements, an event_button element that includes a display attribute and a procedure_string element that specifies an action to be performed when the button is operated. Further, the event_button element includes a button_name element including button identification information (button name), a button_string element including a button display name, a button_top element including a coordinate value of the upper end of the button in the up-down direction, and a button in the left-right direction. It has a button_left element including the coordinate value of the left end, a button_hight element including the height of the button, and a button_width element including the width of the button.

  The template file 15d is default data in which components of the user interface screen are described in XML. The template file 15d is also described according to the syntax definition described in the schema data 15b. In one template file 15d, attributes for each of one or more components included in one user interface screen are described together with default values. The XML text in the template file 15d is available to the user interface data 15c for customization of the user interface data 15c. 6 to 10 are examples of default screens displayed based on the template file 15d. 6 is a kind of a button selection type screen having buttons and text as components, FIG. 7 is a type of a list type screen having a list as components, and FIG. 8 is a numeric input field as a component. FIG. 9 is a type of text input type screen having a text input field as a component, and FIG. 10 has a numeric increase button, a numeric decrease button, and a numeric field as components. It is a kind of fixed numeric input type screen.

  The communication device 16 is a device connected to the computer network 2 and capable of communicating with other devices (such as the terminal device 3) connected to the computer network 2. A network interface card or the like is used as the communication device 16.

  The computer 17 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and the like (not shown), loads various programs into the RAM, and executes them on the CPU, thereby realizing various processing units. It is a device to do. The computer 17 implements a communication processing unit 21, an XML processing unit 22, a control unit 23, and a driver 24 based on a program (not shown).

  The communication processing unit 21 is a processing unit that controls the communication device 16 and transmits / receives a message via the computer network 2 using a predetermined communication protocol. In this embodiment, since SOAP (Simple Object Access Protocol) is used as a message protocol, TCP / IP (Transmission Control Protocol / Internet Protocol) and HTTP (Hypertext Transfer Protocol) are used as communication protocols.

  The XML processing unit 22 is a processing unit that reads the service definition data 15a described in WSDL and realizes the message generation unit 22a and the message analysis unit 22b. The message generator 22a generates a message such as a response message or a notification message indicating the service result in accordance with the syntax definition described in the service definition data 15a. The message analysis unit 22b performs syntax analysis of a message such as a request message indicating a service request according to the syntax definition described in the service definition data 15a, and specifies a request described in the message. The UI data analysis unit 22c parses the user interface data 15c, specifies the attribute of each component on each user interface screen, and causes the display device 11a to display the user interface screen reflecting the attribute of the component Part. The UI data analysis unit 22c causes the driver 24 to display a user interface screen based on the result of the syntax analysis.

  The control unit 23 controls an internal device having a function for realizing a service, such as the printing device 12, the image reading device 13, or the facsimile device 14, according to the request specified by the XML processing unit 22 and executes the service. The processing unit obtains the service result from the internal device and supplies it to the XML processing unit 22.

  The driver 24 is a driver of the operation panel 11, and sends and receives messages to and from the XML processing unit 22 regarding user operation information input to the operation panel 11 and user interface screen information displayed on the operation panel 11. It is a processing part to perform.

  In FIG. 1, the terminal device 3 includes a communication device 31, a data storage device 32, and a computer 33. For example, a personal computer is used as the terminal device 3.

  The communication device 31 is a device that is connected to the computer network 2 and can communicate with other devices (such as the multifunction device 1) connected to the computer network 2. As the communication device 31, a network interface card or the like is used.

  The data storage device 32 is a device that stores a program executed by the computer 33. The data storage device 32 stores a driver program 32a. As the data storage device 32, a device that drives a readable / writable recording medium such as a hard disk drive or a nonvolatile memory is used.

  The computer 33 is a device that includes a CPU, RAM, ROM, and the like (not shown), implements various processing units by loading a program into the RAM and executing the program by the CPU. The computer 32 implements the communication processing unit 41 and the driver 42 based on a program such as the driver program 33a.

  The communication processing unit 41 is a processing unit that controls the communication device 31 and transmits and receives messages via the computer network 2 using a predetermined communication protocol. In this embodiment, since a SOAP message is used as a message, TCP / IP and HTTP are used as communication protocols. For example, the communication processing unit 41 transmits a request message for editing the user interface data 15c.

  The driver 42 is a driver that controls the MFP 1 via the computer network 2 and is a processing unit that generates and analyzes messages used for services. In addition, the driver 42 controls the communication processing unit 41 to acquire all or part of the service definition data 15a and the schema data 15b to specify the syntax of the message, and to use attribute items and attributes used in the message. Specify the allowable value that can be set for the item.

  Next, display of a user interface screen in the multifunction machine 1 will be described.

  First, in the multifunction device 1, when the computer 17 is started, a program is executed, and the communication processing unit 21, the XML processing unit 22, the control unit 23, and the driver 24 are realized as appropriate.

  After startup, the UI data analysis unit 22c reads the XML text of a predetermined initial screen from the user interface data 15c, parses it, and supplies a command to the driver 24 based on the result. The driver 24 displays an initial screen on the display device 11a according to the command.

  Thereafter, when a user operation is detected by the input device 11 b, the operation information is supplied to the XML processing unit 22 via the driver 24. When the UI data analysis unit 22c determines that a screen transition is necessary by the user operation, the XML data of the next screen is read from the user interface data 15c, parsed, and a command is supplied to the driver 24 based on the result. To do. The driver 24 performs screen transition according to the command, and causes the display device 11a to display the next screen.

  Thereafter, similarly, screen transition is executed when necessary according to a user operation or a change in the state of the multifunction device 1.

  Next, customization of the user interface screen in the multifunction machine 1 will be described. The customization is performed by the user or service person operating the terminal device 3.

  After startup, the XML processing unit 22 reads the service definition data 15a, and implements a message generation unit 22a and a message analysis unit 22b based on the service definition data 15a. At this time, the XML processing unit 22 also reads the schema data 15b referred to from the service definition data 15a.

  On the other hand, in the terminal device 3, the communication processing unit 41 and the driver 42 are realized by the computer 33 executing the driver program 32 a and the like.

  Thereafter, when a predetermined user operation is detected by an input device (not shown) such as a keyboard in the terminal device 3, it is determined that a user has requested a service, and the driver 42 sends a request message to the multifunction device 1. Execute the process to send.

  The driver 42 acquires all or part of the service definition data 15a and schema data 15b for the service that is the target of the user's request from the multi-function device 1. At this time, the driver 42 controls the communication processing unit 41 to transmit an HTTP command to a predetermined URL of the multifunction device 1 and obtains all or part of the service definition data 15a and schema data 15b as a response. . For example, the driver 42 may specify the URL of the data file including the service definition data 15a and the schema data 15b, or the CGI (Common Gate Interface) URL that extracts and returns only the necessary portions of the data 15a and 15b. May be specified. The communication processing unit 21 of the multifunction device 1 has an HTTP server function, receives the HTTP command, and transmits a response to the terminal device 3.

  Based on all or part of the acquired service definition data 15a and schema data 15b, the driver 42 specifies the syntax of the message used for the service and the allowable value of the parameter used in the message. When a service request is made by the user, the driver of the terminal device 3 specifies the name of the message associated with the service, and specifies the message syntax and parameter allowable values corresponding to the name of the message in the service definition data. Based on 15a and schema data 15b.

  Then, the driver 42 displays a list of allowable values of parameters used in the message on a display device (not shown), and then selects a parameter value from the list based on a user operation on an input device (not shown). Generate a request message using the value of the parameter.

  For example, when a user interface screen editing service request for adding a button occurs, the driver 42 acquires part or all of the service definition data 15a and schema data 15b shown in FIGS. Identifies that the parameter “screen_name” (screen_name element), “event_button” (event_button element), and parameter “procedure_string” (procedure_string element) are used in the message “send_request”, and the attributes in the parameter “event_button” Specify that the items are “button_name”, “button_string”, “button_top”, “button_left”, “button_hight”, and “button_width”. Then, the driver 42 causes a display device (not shown) to display a screen for prompting input of parameters and attribute item values. Thereafter, when a text input regarding the value of the parameter and the attribute item is detected by an input device (not shown), the driver 42 uses the value of the selected parameter according to the acquired service definition data 15a and schema data 15b. Then, a request message as shown in FIG. 4 is generated. In this case, the generated message is a SOAP message. FIG. 4 shows only the SOAP envelope part of the SOAP message.

  Thus, since the terminal device 3 acquires the service definition data 15a and the like from the multi-function device 1 that executes the service, it is not necessary to store these data in the terminal device 3 in advance. For example, even if the message syntax differs depending on the model of the multifunction device 1, it is not necessary to store the service definition data 15a or the like in the terminal device 3 for each model of the multifunction device 1, and therefore management of the service definition data 15a or the like is performed. It only needs to be performed for the multifunction device 1.

  Then, the driver 42 causes the communication processing unit 41 to transmit the generated request message to the multifunction device 1. At this time, the communication processing unit 41 controls the communication device 31 to transmit the message to the computer network 2 by HTTP. The transmitted message is received by the communication processing unit 21 of the multifunction device 1 from the computer network 2 via the communication device 16. When receiving the message, the communication processing unit 21 supplies the message to the XML processing unit 22.

  The message analysis unit 22b of the XML processing unit 22 analyzes the syntax of the message in accordance with the service definition data 15a and the schema data 15b, identifies the service that uses the message, and sends a request and parameter value based on the message to the control unit 23. Notice. For example, when the message analysis unit 22b is supplied with the message shown in FIG. 4, the message analysis unit 22b specifies that the message is a send_request message of the user interface screen editing service, and specifies the value of the parameter specified in the message. . Then, the message analysis unit 22b receives the send_request message of the user interface screen editing service and notifies the control unit 23 of the parameter value specified in the message.

  Upon receiving the notification, the control unit 23 controls the internal device to execute the requested service. For example, when receiving the send_request message of the user interface screen editing service and the notification of the value of the parameter specified in the message, the control unit 23 edits the user interface data 15c stored in the data storage device 15. Run. At this time, when adding or updating a component, the control unit 23 sets the description (XML element) of the component described in the received request message to the component of the screen specified by the request message. Is written in the user interface data 15c as it is. For example, the description of the event_button element and the procedure_string element in the message shown in FIG. 11 is added to the user interface data 15c as it is without editing or conversion.

  When the control unit 23 detects that the execution of the service is completed, the control unit 23 notifies the message generation unit 22a of the XML processing unit 22 of the service result.

  When the notification of the service result is received from the control unit 23, the message generation unit 22a generates a response message according to the service definition data 15a and the schema data 15b.

  For example, when the message generation unit 22a receives a transmission request for a send_response message (that is, a response message) of the user interface screen editing service in the service definition data 15a as a notification of the result of the user interface screen editing service, the service definition data 15a and Based on the schema data 15b, the syntax of the response SOAP message is specified, and the SOAP message for the response is generated. For example, when the control unit 23 notifies that the requested user interface screen editing service is successful, a SOAP message as shown in FIG. 5 is generated. FIG. 5 shows only the SOAP envelope part of the SOAP message.

  Then, the XML processing unit 22 causes the communication processing unit 21 to transmit the generated response message to the terminal device 3. At this time, the communication processing unit 21 controls the communication device 16 to transmit the message to the computer network 2 using HTTP. The transmitted message is received by the communication processing unit 41 of the terminal device 3 from the computer network 2 via the communication device 31. When receiving the message, the communication processing unit 41 supplies the message to the driver 42. The driver 42 detects the result for the requested service from the response message. The driver 42 executes processing according to the result. For example, the driver 42 displays the service result on a display device (not shown). Further, for example, in the case of the user interface screen editing service, the multifunction device 1 includes the user interface data 15c for the edited user interface screen in the response message, and the driver 42 of the terminal device 3 includes the user included in the message. The edited user interface screen may be displayed based on the interface data 15c.

  In the user interface screen editing service, the user interface screen may be added or updated using the template file 15d. In this case, for example, a request message designating the user interface screen and the template file 15 d is transmitted from the terminal device 3 to the multifunction device 1. In the multifunction device 1, the user interface data 15c for the specified user interface screen is added or updated with the data included in the template file 15d. The syntax definition of the request message at this time is also included in the service definition data 15a and the schema data 15b. After that, it is possible to edit the components in the user interface screen as described above.

  As described above, according to the above embodiment, the multi-function device 1 stores the display device 11a that displays the user interface screen and the user interface data 15c that describes the attributes of the components in the user interface screen in text. The data storage device 15 includes a UI data analysis unit 22c that parses the user interface data 15c to identify the attribute of the component and displays a user interface screen that reflects the attribute of the component on the display device 11a.

  Thus, the user interface can be customized by editing the user interface data 15c. Therefore, the user interface screen of the multifunction device 1 can be easily customized.

  Further, according to the above embodiment, the multi-function device 1 analyzes the message according to the service definition data including the syntax definition of the interface part of the editing service and the specification of the protocol of the message used for the service for the user interface data 15c. And an XML processing unit 22 for executing the editing service according to a request obtained from the message based on the result of the syntax analysis of the XML processing unit 22.

  As a result, the multifunction device 1 edits the user interface data 15c as one of the services. Therefore, the user interface data 15c can be edited without operating the multifunction device 1 directly by an external message. . Therefore, the user interface screen of the multifunction device 1 can be easily customized.

  Further, according to the above embodiment, in the multifunction device 1, the user interface data 15c and the message are described in XML, and the control unit 23 uses the XML text of the component attribute extracted by the message processing unit 22b. To update the user interface data 15c.

  As a result, when the user interface data 15c is updated, conversion from the message to the user interface data 15c becomes unnecessary.

  According to the above embodiment, in the terminal device 3, the driver 42 acquires part or all of the schema data 15 b from the multi-function device 1, specifies one or more items of component component attributes, and performs communication. The processing unit 41 transmits a message for setting values for some or all of one or more items specified by the driver 42.

  Thus, customization can be executed even if the terminal device 3 does not hold the attribute items of the component parts in advance.

  Further, according to the above-described embodiment, in the terminal device 3, the driver 42 acquires part or all of the schema data 15b from the multi-function device 1 and specifies one or more allowable values for the attribute of the component, The communication processing unit 41 transmits a message for setting a value selected from one or more allowable values specified by the driver 42 as an attribute of the component.

  As a result, customization can be executed even if the terminal device 3 does not hold the allowable value of the attribute of the component in advance.

  Further, according to the above embodiment, the user interface data 15c and the message are described in XML, the schema data 15b is XML data described in the XML schema, and the control unit 23 is the XML processing unit 22. The user interface data is updated with the XML text of the attribute of the component extracted in step (b).

  Thereby, the customization can be executed even if the terminal device 3 does not hold the syntax definition of the message in advance.

  Further, according to the above embodiment, the data storage device 15 stores a plurality of template files 15d each including default data of the user interface screen. The communication processing unit 41 of the terminal device 3 designates one template file out of the plurality of template files 15d, and uses the default data of the designated template file as data of one user interface screen in the user interface data 15c. Send.

  Thereby, complicated customization can be easily performed by using a template.

  The above-described embodiments are preferred examples of the present invention, but the present invention is not limited to these, and various modifications and changes can be made without departing from the scope of the present invention. is there.

  For example, in the above-described embodiment, a multifunction peripheral is described as an example of an image forming apparatus, but a printer, a facsimile machine, a scanner, or the like may be used.

  In the above embodiment, the service definition data 15a may be created for each use case composed of a series of services.

  In the above-described embodiment, the service definition data 15a is described in WSDL, but may be described in another language in which similar description is possible. The schema description in the schema data 15b and the service definition data 15a may be described in a language other than the XML schema. However, even in that case, the service definition data 15a and the schema data 15b are text data that can be easily edited.

  In the above embodiment, the service definition data 15a and / or the schema data 15b are stored in a server device that can be accessed via the computer network 2, and the multifunction device 1 receives the service definition data 15a and the schema data 15a from the server device. Alternatively, the schema data 15b may be downloaded and used.

  In the above embodiment, the attribute information (type, resolution, display color (color / monochrome), etc.) of the display device 11a is included in the service definition data 15a or the schema data 15b, and the information is displayed in the terminal device 3 at the time of customization. Can be displayed. For example, the type of the display device 11a includes a 2 × 2 liquid crystal, a dot matrix display, and an 8.5 inch full color liquid crystal panel.

  In the above embodiment, the procedure_string element may describe an operation command for changing the layout of buttons on the screen. When the command is described, when the button is pressed, another screen such as a button having a different layout is displayed.

  In the above embodiment, the operation command described in the procedure_string element may be the name of a service defined in the service definition data 15a. That is, in the service definition data 15a, a syntax definition of a service provided by the operation of the multifunction device 1, such as a scan service, is described, and when the button is operated, a message according to the syntax is displayed from the operation panel 11. By being transmitted to the XML processing unit 22, the operation for the service is executed by the multifunction device 1. In the above embodiment, a series of operations may be described in XML as a child element of the procedure_string element.

  The present invention is applicable to, for example, a multifunction machine.

1 is a block diagram illustrating a configuration of an image forming system including a multifunction peripheral as an image forming apparatus according to an embodiment of the present invention. It is a figure which shows an example of the service definition data described by WSDL. It is a figure which shows an example of the schema data referred with service definition data. It is a figure which shows an example of a user interface screen. It is a part of user interface data describing the user interface screen shown in FIG. It is an example of the default screen displayed based on a template file. It is an example of the default screen displayed based on a template file. It is an example of the default screen displayed based on a template file. It is an example of the default screen displayed based on a template file. It is an example of the default screen displayed based on a template file. It is a figure which shows an example of the message of the request | requirement in embodiment of this invention. It is a figure which shows an example of the message of the response in embodiment of this invention.

Explanation of symbols

1 MFP (an example of an image forming apparatus)
2 Computer network (an example of a computer network)
3 Terminal device (an example of a terminal device)
11a Display device (an example of a display device)
15a Service definition data (an example of service definition data)
15b Schema data (an example of schema data)
15c User interface data (an example of user interface data)
15d template file (example of template file)
21 Communication processing unit (an example of transmission means)
22 XML processing unit (an example of a message processing unit)
22c UI data analysis unit (an example of UI data analysis unit)
23 Control unit (an example of a control unit)

Claims (9)

A display device for displaying a user interface screen;
A data storage device for storing user interface data in which attributes of components in the user interface screen are described in text;
A UI data analysis unit that parses the user interface data to identify an attribute of the component and displays the user interface screen reflecting the attribute of the component on the display device;
A message processing unit that parses the message according to service definition data including a syntax definition of an interface part of an editing service for the user interface data and a specification of a protocol of a message used for the service;
A control unit that executes the editing service according to a request obtained from the message according to a result of parsing of the message processing unit;
Receiving means for receiving the message via a computer network,
The user interface data is described in XML according to the syntax definition described in the schema data,
The service definition data refers to the schema data,
The message processing unit parses the message according to the service definition data and the schema data referenced in the service definition data;
An image forming apparatus. The protocol specified in the service definition data is SOAP,
The receiving means receives the message by HTTP;
The image forming apparatus according to claim 1 . The service definition data, the image forming apparatus according to claim 1, characterized in that the XML data described in WSDL. Before Symbol message is written in XML,
The control unit updates the user interface data with the XML text of the component attribute extracted by the message processing unit;
The image forming apparatus according to claim 1 . An image forming apparatus connected to a computer network;
A terminal device connected to the computer network,
The image forming apparatus includes:
A display device for displaying a user interface screen;
A data storage device for storing user interface data in which attributes of components in the user interface screen are described in text;
A UI data analysis unit that parses the user interface data to identify an attribute of the component and displays the user interface screen reflecting the attribute of the component on the display device;
Receiving means for receiving a message with a predetermined communication protocol via the computer network;
And a message processing unit which performs parsing of the message according to the service definition data including designation and the message protocol used syntax definition of the interface portion of the editing service against the user interface data and its services,
A control unit that executes the editing service according to a request obtained from the message according to a result of parsing of the message processing unit,
The terminal apparatus, have a transmission means for transmitting the message in a predetermined communication protocol via the computer network,
The user interface data is described in XML according to the syntax definition described in the schema data,
The service definition data refers to the schema data,
The message processing unit parses the message according to the service definition data and the schema data referenced in the service definition data;
An image forming system. Wherein the data storage device, pre-stores kiss schema data,
The terminal device includes a schema data acquisition unit that acquires a part or all of the schema data from the image forming apparatus and identifies one or more items of attributes of the component parts,
The transmission means transmits the message for setting a value in a part or all of the one or more items specified by the schema data acquisition unit;
The image forming system according to claim 5 . Wherein the data storage device, pre-stores kiss schema data,
The terminal device includes a schema data acquisition unit that acquires a part or all of the schema data from the image forming apparatus and identifies one or a plurality of allowable values for the attribute of the component,
The transmission means transmits the message for setting a value selected from the one or more allowable values specified by the schema data acquisition unit as an attribute of the component;
The image forming system according to claim 5 . Before Symbol message is written in XML,
The schema data is XML data described in an XML schema,
The control unit updates the user interface data with the XML text of the component attribute extracted by the message processing unit;
8. The image forming system according to claim 6 or 7, wherein: The data storage device stores a plurality of template files each including default data of a user interface screen,
The transmission means designates one of the plurality of template files, and transmits the message using the default data of the designated template file as data of one user interface screen in the user interface data. To do,
The image forming system according to claim 5 .

Images