System, user terminal and method

Abstract

To provide a server device and a control program thereof in which a user can efficiently understand a failure situation.SOLUTION: A server device comprises: communication means; information storage means; and output means. The communication means communicates with an information processing apparatus comprising: a display unit that displays a symbol; and a transmission unit that transmits information associated with a failure of its own device. The information storage means stores information associated with the failure transmitted from the information processing apparatus. The output means outputs the information associated with the failure stored in an access destination identified by the symbol on a failure situation screen 200 of a user terminal in which the symbol is read.SELECTED DRAWING: Figure 15

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a server device and a control program therefor. [Background technology]

[0002] Conventional information processing devices such as MFPs (digital multi-functional peripherals) have a function that notifies the user of the status of a malfunction when a malfunction occurs. To use this function, the user must register an email address or other destination in advance with the information processing device. In other words, the user cannot grasp the status of the malfunction unless the destination is registered. Users who have registered a destination are notified of the status of the malfunction every time. For this reason, some users who have registered a destination but do not use the information processing device frequently find the notification of the status of the malfunction every time annoying. Therefore, there is a demand for a system that allows users to grasp the status of a malfunction efficiently. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-212958 Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a server device and a control program therefor that allow a user to efficiently grasp the state of a failure. [Means for solving the problem]

[0005] The server device includes a communication means, an information storage means, and an output means. The communication means communicates with an information processing device that includes a display unit that displays a symbol and a transmission unit that transmits information related to a failure of the device itself. The information storage means stores the information related to the failure transmitted from the information processing device. The output means outputs the information related to the failure stored in the access destination specified by the symbol to the user terminal that reads the symbol. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a schematic diagram showing a schematic configuration of an information processing system according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing the main circuit configuration of the MFP according to an embodiment. [Figure 3] FIG. 2 is a block diagram showing the main circuit configuration of a web server. [Figure 4] FIG. 4 is a schematic diagram showing an example of an image table. [Figure 5] FIG. 4 is a schematic diagram showing an example of a management table. [Figure 6] FIG. 4 is a schematic diagram showing an example of a destination table. [Figure 7] FIG. 2 is a block diagram showing the main circuit configuration of a user terminal. [Figure 8] 4 is a flowchart showing a control procedure for a main part of a processor in the MFP. [Figure 9] 10 is a flowchart showing a control procedure for a main part of a processor in a Web server. [Figure 10] 10 is a flowchart showing a control procedure of a main part of a processor in an information terminal. [Figure 11] 10 is a flowchart showing a control procedure for a main part of a processor in a Web server. [Figure 12] 10 is a flowchart showing a control procedure for a main part of a processor in a Web server. [Figure 13] 10 is a flowchart showing a control procedure for a main part of a processor in a Web server. [Figure 14] FIG. 10 is a schematic diagram showing an example of an access screen. [Figure 15] FIG. 10 is a schematic diagram showing an example of a failure status screen. DETAILED DESCRIPTION OF THE INVENTION

[0007] An embodiment will be described below with reference to the drawings.

[0008] FIG. 1 is a schematic diagram showing a general configuration of an information processing system 1 according to an embodiment. The information processing system 1 includes multiple MFPs 10 and a Web server 20. The MFPs 10 are an example of an information processing device. The Web server 20 is a server device for managing the MFPs 10. The MFPs 10 and the Web server 20 are connected to a dedicated communication network 2. The dedicated communication network 2 is typically a digital leased line, an ISDN (Integrated Services Digital Network) line, or the like. The Web server 20 provides services to multiple user terminals 30 from the dedicated communication network 2 via a wide area network 3 such as the Internet. The user terminals 30 are terminals owned by users who use the MFPs 10. The user terminals 30 are well-known Internet-enabled portable terminals. For example, smartphones, tablet terminals, etc. are used as the user terminals 30.

[0009] 2 is a block diagram showing a schematic configuration of an MFP 10 according to an embodiment. The MFP 10 includes a scanner 11, a printer 12, a control system 13, and an operation panel 14. The scanner 11, the printer 12, and the operation panel 14 are connected to the control system 13.

[0010] The scanner 11 is a device that optically reads an image of a document and converts it into image information in response to an operational instruction from the control system 13. The scanner 11 outputs the read image information of the document to the control system 13.

[0011] The printer 12 prints an image on paper based on image information supplied from the control system 13 under various printing conditions specified by the control system 13. The printer 12 may be, for example, an electrophotographic printer, or may be an inkjet printer or a thermal transfer printer.

[0012] The control system 13 comprehensively controls the operations of each section, such as the scanner 11, printer 12, and operation panel 14. The control system 13 also executes various processes, such as image processing. The control system 13 includes a processor 131, a RAM (random-access memory) 132, a ROM (read-only memory) 133, a data memory 134, an image memory 135, an image processing unit 136, a FAX (facsimile) interface (I / F) 137, and a communication interface (I / F) 138.

[0013] The processor 131 executes processes such as calculations and controls in accordance with a program. The processor 131 realizes various processing functions by executing a program stored in the ROM 133 or the data memory 134. The RAM 132 is a working memory. The RAM 132 is, for example, a volatile memory. The ROM 133 is a program memory. The ROM 133 is, for example, a non-volatile memory.

[0014] The data memory 134 stores control data, control programs, setting information, etc. The data memory 134 is, for example, a non-volatile memory. The image memory 135 is configured with a hard disk drive, page memory, etc. The image memory 135 stores image information. The image processing unit 136 performs image processing on the image information.

[0015] The FAX interface 137 is an interface for performing FAX communication. The communication interface 138 is an interface for performing data communication with an external device via a network such as the dedicated communication network 2.

[0016] The operation panel 14 is a user interface. The operation panel 14 includes a touch panel 141 and an input device 142. The touch panel 141 is configured by stacking a display, such as a liquid crystal display or an organic electroluminescence (EL) display, and a sensing device that detects touch input. The input device 142 is, for example, a button, a keyboard, a keypad, or a touchpad.

[0017] The MFP 10 stores a device ID in the data memory 134. The device ID is a unique code assigned to each MFP 10 in order to identify the MFP 10.

[0018] 3 is a block diagram showing the main circuit configuration of the Web server 20. The Web server 20 includes a processor 21, a main memory 22, an auxiliary storage device 23, a clock 24, a communication interface 25, and a system transmission path 26. The system transmission path 26 includes an address bus, a data bus, control signal lines, etc. The Web server 20 connects the processor 21, the main memory 22, the auxiliary storage device 23, the clock 24, and the communication interface 25 to the system transmission path 26. In the Web server 20, the processor 21, the main memory 22, the auxiliary storage device 23, and the system transmission path 26 that connects them together constitute a computer.

[0019] The processor 21 controls each unit to realize various functions of the Web server 20 in accordance with an operating system or application programs.

[0020] The main memory 22 includes a nonvolatile memory area and a volatile memory area. The main memory 22 stores an operating system or application programs in the nonvolatile memory area. The main memory 22 stores data required for the processor 21 to execute processes for controlling each part in the volatile memory area. The above data may also be stored in the nonvolatile memory area. The main memory 22 uses the volatile memory area as a work area where data can be rewritten by the processor 21 as appropriate. The nonvolatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0021] The auxiliary storage device 23 is, for example, an EEPROM (registered trademark) (electric erasable programmable read-only memory), an HDD (hard disk drive), or an SSD (solid state drive). The auxiliary storage device 23 stores data used by the processor 21 when performing various processes, or data created by the processes in the processor 21. The auxiliary storage device 23 may also store the above-mentioned application programs.

[0022] The clock 24 functions as a time information source for the Web server 20. The processor 21 keeps track of the current date and time based on the time information kept by the clock 24.

[0023] The communication interface 25 is an interface circuit for transmitting and receiving data to and from the MFP 10 connected via the dedicated communication network 2 in accordance with a predetermined communication protocol.

[0024] The Web server 20 configured as described above stores a management database 231, an image table 232 (see FIG. 4), a management table 233 (see FIG. 5), and a destination table 234 (see FIG. 6) in the auxiliary storage device 23. The management database 231 saves an MFP data record created for each MFP 10. The MFP data record includes items such as a device ID, a name, an installation location, a model number, a toner status, and contact information for a service person or administrator. The toner status indicates the usage status of the toner amounts of cyan, magenta, yellow, black, and other toners. The contact information for a service person or administrator indicates the telephone number of a service person or administrator to be contacted in the event of a malfunction of the MFP 10. The storage destination of the management database 231, the image table 232, the management table 233, and the destination table 234 is not limited to the auxiliary storage device 23. The management database 231, the image table 232, the management table 233, and the destination table 234 may also be stored in a volatile memory area of ​​the main memory 22.

[0025] FIG. 4 is a schematic diagram showing an example of the image table 232. As shown in FIG. 4, the image table 232 is a data table consisting of a device ID, image data, and a URL (uniform resource locator). The image data is image data of a Web page screen that displays information related to the failure status of the MFP 10 corresponding to the device ID. The Web page screen is hereinafter referred to as a failure status screen. Details of the failure status screen will be described later. In this embodiment, the image data of the failure status screen is assumed to be managed in advance by an administrator of the Web server 20 in association with the device ID. That is, the administrator updates and saves the image data each time the MFP 10 fails. The image data is updated when any change occurs in the information related to the failure status, such as when a service technician repairs the MFP 10 or when the planned recovery date is changed. The URL is a unique address assigned to the device ID and the image data. The URL specifies the access destination for the information related to the failure status, i.e., the failure status screen. The URL is valid from the time the URL is generated until the time the failed MFP 10 is restored. It should be noted that the image table 232 is not limited to the items shown in FIG.

[0026] FIG. 5 is a schematic diagram showing an example of management table 233. As shown in FIG. 5, management table 233 is a data table consisting of a device ID, a failure date, an update date, a failure content, a URL, a recovery flag, and the like. The failure date is the date on which MFP 10 failed. The update date is the date on which image data was updated. The failure content is the reason for the failure, such as a failure of scanner 11, control system 13, or operation panel 14. The recovery flag is one-bit data for identifying whether or not the failed MFP 10 has recovered. In this embodiment, the recovery flag is in its initial state of "0" until MFP 10 is recovered, and is set to "1" when MFP 10 is recovered. Note that management table 233 is not limited to the items shown in FIG. 5.

[0027] Fig. 6 is a schematic diagram showing an example of destination table 234. As shown in Fig. 6, destination table 234 is a data table for storing, for each device ID, the destination of a user who wishes to receive an update notification of information related to the failure status of the MFP 10 corresponding to that device ID. The user destination is, for example, the user's email address. Note that destination table 234 is not limited to the items shown in Fig. 6.

[0028] Fig. 7 is a block diagram showing the main circuit configuration of the user terminal 30. As shown in Fig. 7, the user terminal 30 includes a processor 31, an internal memory 32, an external memory 33, a touch panel 34, a camera 35, a wide area network interface 36, and a system transmission path 37. The system transmission path 37 includes an address bus, a data bus, a control signal line, etc. The user terminal 30 connects the processor 31, the internal memory 32, the external memory 33, the touch panel 34, the camera 35, and the wide area network interface 36 to the system transmission path 37. The processor 31, the internal memory 32, and the external memory 33 are connected by the system transmission path 37 to form a computer that performs information processing for controlling the user terminal 30.

[0029] The processor 31 controls each unit in accordance with an operating system or an application program to realize various functions of the user terminal 30. The processor 31 is, for example, a CPU.

[0030] The built-in memory 32 includes a non-volatile memory area and a volatile memory area. The built-in memory 32 stores an operating system or application programs in the non-volatile memory area. The built-in memory 32 stores data required for the processor 31 to execute processes for controlling each component in the volatile memory area. The built-in memory 32 also uses the volatile memory area as a work area where data can be rewritten by the processor 31 as needed. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0031] The external memory 33 is, for example, an SD memory card, a USB memory, etc. The external memory 33 stores data used by the processor 31 when performing various processes, or data created by the processes in the processor 31. The external memory 33 may also store the above-mentioned application programs.

[0032] The touch panel 34 is a device that serves as both an input device and a display device of the user terminal 30. The touch panel 34 detects a touch position on a displayed image and outputs the touch position information to the processor 31.

[0033] The camera 35 is an imaging device built into the user terminal 30. The camera 35 operates as a still or video image capturing device or as a scanning device for data codes DC such as barcodes and two-dimensional codes, depending on an application program installed in the user terminal 30. The camera 35 is an example of a code reader.

[0034] The wide area network interface 36 is a device for wirelessly communicating data with the Web server 20 connected via the wide area network 3 in accordance with a predetermined wireless communication protocol.

[0035] Fig. 8 is a flowchart showing the main information processing procedures executed by processor 131 of MFP 10 according to a control program. Fig. 9 and Figs. 11 to 13 are flowcharts showing the main information processing procedures executed by processor 21 of Web server 20 according to a control program. Fig. 10 is a flowchart showing the main information processing procedures executed by processor 31 of user terminal 30 according to a control program. The operation of information processing system 1 will be described below using these figures. Note that the operation procedures and their contents described below are merely examples. The procedures and contents are not limited as long as similar results are obtained.

[0036] In ACT1, the processor 131 of the MFP 10 waits to see if a failure has occurred. If a failure has occurred, the processor 131 determines YES in ACT1 and proceeds to ACT2. In ACT2, the processor 131 controls the communication interface 138 to send a failure command to the Web server 20. This control causes the failure command to be sent via the communication interface 138. The failure command includes the device ID, the failure date, and the details of the failure, all of which are stored in the data memory 134.

[0037] Upon receiving the failure command, the processor 21 of the Web server 20 starts a command reception process according to the procedure shown in the flowchart of FIG.

[0038] Processor 21 detects the device ID from the failure command in ACT11. Then, processor 21 authenticates MFP 10 identified by that device ID in ACT12. Specifically, processor 21 checks whether an MFP data record including that device ID exists in management database 231. If the corresponding MFP data record exists in management database 231, processor 21 determines that MFP authentication is valid. On the other hand, if the corresponding MFP data record does not exist in management database 231, processor 21 determines that MFP authentication is invalid.

[0039] Processor 21 checks the result of MFP authentication in ACT13. If the MFP authentication result is invalid, processor 21 determines NO in ACT13 and treats it as an error. In the case of an error, processor 21 controls communication interface 25 to send an error command to MFP 10, the source of the failure command. This control causes the error command to be sent via communication interface 25. Processor 131 of MFP 10 that received the error command causes an error screen to be displayed on touch panel 141.

[0040] If the MFP authentication result is valid, the processor 21 determines YES in ACT 13 and proceeds to ACT 14. In ACT 14, the processor 21 creates a URL that specifies image data of a failure status screen that is the access destination for information related to the failure status and that is associated in advance with the device ID included in the failure command.

[0041] In ACT15, the processor 21 stores a URL corresponding to the above-mentioned device ID and image data in the image table 232. In ACT16, the processor 21 stores in the management table 233 the device ID, the date of failure, and the details of the failure that were included in the failure command, as well as the URL created in the processing of ACT14.

[0042] Processor 21 controls communication interface 25 as ACT 17 to send a display command to MFP 10, the source of the failure command. This control causes the display command to be sent via communication interface 25. The display command includes screen data for access screen 100 (see FIG. 14). With this, processor 21 ends the failure command reception process.

[0043] FIG. 14 is a schematic diagram showing an example of an access screen 100. As shown in FIG. 14, the access screen 100 is composed of a data code, which is a symbol, and text data notifying the user that the fault condition can be confirmed by reading the data code. The data code is, for example, a two-dimensional barcode. The data code includes a URL created in the processing of ACT14 in FIG. 9. Note that the content and image of the text data displayed in FIG. 14 are merely examples.

[0044] Returning to the explanation of Figure 8. The processor 131 of the MFP 10, which controlled the transmission of the failure command in ACT2, waits for a display command from the Web server 20 in ACT3. If a display command is received from the Web server 20, the processor 131 determines YES in ACT3 and proceeds to ACT4. In ACT4, the processor 131 causes the touch panel 141 to display the access screen 100. With this, the processor 131 ends the information processing of the procedure shown in the flowchart of FIG. 8.

[0045] Now, the user of MFP 10 checks access screen 100 displayed on touch panel 141 and starts the dedicated application of user terminal 30. Then, processor 31 starts information processing of the procedure shown in the flowchart of FIG.

[0046] The processor 31 activates the camera 35 as ACT21. When the camera 35 is activated, the processor 31 displays a camera screen on the touch panel 34. The camera screen displays an image showing the reading area of ​​a data code of a two-dimensional code system. After checking the camera screen, the user points the lens of the camera 35 at the data code so that the data code fits within the image.

[0047] In ACT 22, the processor 31 waits for the data code to be read by the camera 35. When the data code fits within the image, the processor 31 determines that the data code has been read. The processor 31 determines YES in ACT 22 and proceeds to ACT 23.

[0048] The processor 31 extracts the URL included in the data code as ACT 23. The processor 31 controls the wide area network interface 36 as ACT 24 to send the URL to the Web server 20.

[0049] Upon receiving the URL, the processor 21 of the Web server 20 starts a URL reception process according to the procedure shown in the flowchart of FIG.

[0050] As ACT41, processor 21 refers to image table 232 and extracts image data corresponding to the received URL. As ACT42, processor 21 controls communication interface 25 to send a status command to user terminal 30, the source of the URL. Through this control, the status command is sent via communication interface 25. The status command is received by user terminal 30 via wide area network 3. The status command includes the device ID and screen data of failure status screen 200 (see FIG. 15). With this, processor 21 ends the URL receiving process.

[0051] FIG. 15 is a schematic diagram showing an example of a failure status screen 200. As shown in FIG. 15, the failure status screen 200 displays device information (such as the name, installation location, model number, toner status, and contact information for a service technician or administrator), a message informing the user of the failure, the progress of the failure, and the expected recovery date. The failure status screen 200 displays a destination input field 201 along with text data prompting a user who wishes to receive update notifications regarding the failure status of the MFP 10 to enter a destination. The user's destination may be, for example, an email address. The failure status screen 200 also displays an image of a send button 202 and an image of a close button 203. If the user wishes to receive update notifications, the user enters a destination in the destination input field 201 and then touches the send button 202. If the user does not wish to receive update notifications, the user touches the close button 203. Note that even if multiple different users access the failure status screen 200, the same screen is displayed for all users. However, previously entered user destinations are not displayed. The contents and images of the text data displayed in FIG. 15 are just an example.

[0052] Returning to the explanation of Figure 10. The processor 31 of the user terminal 30, which controlled the URL transmission in ACT24, waits for a status command from the Web server 20 in ACT25. If a status command is received from the Web server 20, the processor 31 determines YES in ACT25 and proceeds to ACT26. In ACT26, the processor 31 displays a failure status screen 200 on the touch panel 34.

[0053] If the user who has checked the failure status screen 200 wishes to receive an update notification of information relating to the failure status of the MFP 10 , the user enters an email address in the destination input field 201 and touches the send button 202 .

[0054] In ACT 27, the processor 31 checks whether the send button 202 has been touched. If the send button 202 has not been touched, the processor 31 determines NO in ACT 27 and proceeds to ACT 30. If the send button 202 has been touched, the processor 31 determines YES in ACT 27 and proceeds to ACT 28. In ACT 28, the processor 31 checks whether an email address has been entered in the destination input field 201.

[0055] If an email address is not entered in the destination input field 201, the processor 31 determines NO in ACT28 and proceeds to ACT 30. If an email address is entered in the destination input field 201, the processor 31 determines YES in ACT28 and proceeds to ACT 29.

[0056] The processor 31 controls the wide area network interface 36 as ACT 29 so as to send a destination command to the Web server 20. This control causes the destination command to be sent from the wide area network interface 36. The destination command is received by the Web server 20 via the wide area network 3. The destination command includes the device ID included in the status command and screen data of the failure status screen 200 on which the email address has been entered.

[0057] In ACT 30, the processor 31 checks whether the close button 203 has been touched. If the close button 203 has not been touched, the processor 31 determines NO in ACT 30 and returns to ACT 27. That is, the user can re-enter the email address. In this embodiment, the processor 31 sends a destination command every time the user enters an email address in the destination input field 201 and touches the send button 202. If the close button 203 has been touched, the processor 31 determines YES in ACT 30 and proceeds to ACT 31.

[0058] In ACT 31, the processor 31 closes the failure status screen 200 that has been displayed on the touch panel 34. With this, the processor 31 ends the information processing of the procedure shown in the flowchart of FIG.

[0059] Upon receiving the destination command, the processor 21 of the Web server 20 starts a destination command reception process according to the procedure shown in the flowchart of FIG.

[0060] The processor 21 detects the device ID from the destination command as ACT 51. The processor 21 extracts the destination table 234 corresponding to the device ID as ACT 52.

[0061] The processor 21 stores the email address in the destination table 234 based on the screen data of the failure status screen 200 included in the destination command as ACT53. When the processor 21 receives a destination command from the same user multiple times, the processor 21 overwrites and stores the latest email address in the destination table 234. With this, the processor 21 ends the destination command reception process.

[0062] Now, the Web server 20 waits for an administrator or the like to update the image data in accordance with the failure situation in ACT61 of Fig. 13. If the image data has been updated, the processor 21 determines YES in ACT61 and proceeds to ACT62.

[0063] The processor 21 acquires the updated image data as ACT 62. The processor 21 references the image table 232 and acquires the device ID corresponding to the updated image data as ACT 63. The processor 21 references the destination table 234 corresponding to the device ID and extracts all registered destinations as ACT 64.

[0064] In ACT65, the processor 21 notifies the destination extracted in the processing of ACT64 that the information related to the failure status of the MFP 10 has been updated. The notification content may be, for example, "Restored," or "The planned restoration date has been changed to July 22nd."

[0065] The processor 21 checks in ACT66 whether the notification content is a recovery notification. A recovery notification is a notification that the failed MFP 10 has been recovered. The above-mentioned "Recovered" is an example. If the MFP 10 is not a recovery notification, the processor 21 determines NO in ACT66 and proceeds to ACT68. The processing of ACT68 will be described later.

[0066] If it is a recovery notification, the processor 21 determines YES in ACT66 and proceeds to ACT67. In ACT67, the processor 21 refers to the management table 233 and updates the recovery flag in the same row as the device ID to "1". When the recovery flag is set to "1", all items in the same row as the recovery flag are invalidated. That is, due to the recovery of the MFP 10, the user will no longer be able to access the failure status screen 200 associated with the failure of the MFP 10. In addition, the destination table 234 corresponding to the invalidated device ID is also invalidated. That is, notifications will no longer be sent to users who have requested update notifications of information related to the failure status of the MFP 10. The processor 21 updates the update date in the management table 233 in ACT68. With this, the processor 21 ends the information processing of the procedure shown in the flowchart of FIG. 13.

[0067] As is clear from the above explanation, Web server 20, which is an example of a server device, constitutes a communication means by executing the processes of ACT1 to ACT4 in Fig. 8. That is, Web server 20 communicates with an information processing device, i.e., MFP 10, which is equipped with a display unit that displays symbols and a transmission unit that transmits information related to a failure in the device itself.

[0068] The processor 21 of the Web server 20 constitutes an information storage unit by executing the process of ACT16 in Fig. 9. That is, the Web server 20 stores the information related to the failure transmitted from the MFP 10.

[0069] The processor 21 of the Web server 20 constitutes an output means by executing the processes of ACT41 and ACT42 in Fig. 11. That is, the Web server 20 outputs information related to the fault stored in the access destination specified by the symbol to the user terminal 30 that reads the symbol.

[0070] As described above, according to this embodiment, by reading the data code of the access screen 100 displayed on the touch panel 141 of the MFP 10 with the user terminal 30, the failure status screen 200 is displayed on the touch panel 34. Therefore, the user can easily understand the failure status of the MFP 10 without performing complicated operations. Furthermore, the failure status screen 200 displays a destination input field 201. Therefore, the user can select whether or not he or she wishes to receive update notification of information related to the failure status of the MFP 10.

[0071] Furthermore, processor 21 of Web server 20 configures destination storage means by executing the processing of ACT53 in Fig. 12. That is, Web server 20 stores destinations. Processor 21 of Web server 20 configures transmission means by executing the processing of ACT61 to ACT65 in Fig. 13. That is, when information related to a failure of MFP 10 is updated, Web server 20 transmits the updated information related to the failure to the destination stored in destination storage means.

[0072] In this embodiment, when the information related to the failure status of the MFP 10 is updated, a user who inputs a destination in the destination input field 201 on the failure status screen 200 and touches the send button 202 is notified of the update. Therefore, the user does not need to read the data code on the access screen 100 every time to access the failure status screen 200, which reduces the user's workload. Furthermore, because only users who wish to be notified of updates to the information related to the failure status of the MFP 10 are notified, users who do not wish to be notified can be prevented from feeling annoyed by the notification.

[0073] Although the embodiment of the server device and the control program therefor has been described above, the embodiment is not limited to this.

[0074] In the above embodiment, the information processing device is the MFP 10. However, the information processing device is not limited to the MFP 10. For example, it may be a copier, a printer, or the like.

[0075] In the above embodiment, a two-dimensional barcode, which is a symbol, is displayed on the access screen 100. The symbol is not limited to a two-dimensional barcode. For example, it may be an image such as a figure including a URL.

[0076] In the above embodiment, the case where the Web server 20 creates a URL was exemplified. For example, the MFP 10 may create a URL and transmit it to the Web server 20 together with the device ID, the date of the failure, and the details of the failure stored in the data memory 134. Also, in the above embodiment, the case where a URL is created for each failure was exemplified. For example, a URL may be set for each MFP 10.

[0077] In the above embodiment, the management database 231 is stored in the auxiliary storage device 23 of the Web server 20. For example, the management database 231 may be stored in the MFP 10.

[0078] The above embodiment illustrates a case where a user's address is notified that information related to the failure status of the MFP 10 has been updated. For example, a URL may be sent to the user terminal 30, and the user may access the failure status screen 200 by touching the URL.

[0079] In the above embodiment, an example has been given of a case where, when a recovery flag is set to "1," the user is unable to access the failure status screen 200 of the MFP 10 corresponding to the recovery flag. For example, when a recovery flag is set to "1," a message such as "Recovered" may be displayed on the failure status screen 200.

[0080] In the above embodiment, when a destination command is received multiple times from the same user, the processor 21 of the Web server 20 overwrites and stores the latest email address in the destination table 234. For example, each time a destination command is received multiple times from the same user, the email address may be stored in the destination table 234. In other words, the user can register multiple email addresses.

[0081] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims.

[0082] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0083] 1...information processing system, 2...dedicated communication network, 3...wide area network, 10...MFP, 11...scanner, 12...printer, 13...control system, 14...operation panel, 20...web server, 21, 31, 131...processor, 22...main memory, 23...auxiliary storage device, 24...clock, 25, 138...communication interface, 26, 37...system transmission path, 30...user terminal, 32...built-in memory, 33...external memory, 34, 141...touch panel, 35...camera, 36...wide area network interface, 132...RAM, 133...ROM, 134...data memory, 135...image memory, 136...image processing unit, 137...FAX interface, 142...input device, 231...management database, 232...image table, 233...management table, 234...destination table

Claims

1. a communication means for communicating with the information processing device, the communication means including a display unit for displaying a symbol and a transmission unit for transmitting information relating to a failure of the device itself; an information storage means for storing the information relating to the failure transmitted from the information processing device; an output means for outputting the information relating to the fault stored in the access destination specified by the symbol to a user terminal that reads the symbol; A server device comprising:

2. the output means further outputs a field for inputting a destination to receive an update notification of the information related to the failure together with the information related to the failure. The server device according to claim 1.

3. a destination storage means for storing the destination; a transmitting means for transmitting, when the information relating to the failure of the information processing device is updated, the updated information relating to the failure to the destination stored in the destination storage means; 3. The server device according to claim 2, further comprising:

4. the symbol is a two-dimensional code including a URL specifying an access destination for information related to the fault; The server device according to claim 1.

5. a computer having a communication means for communicating with an information processing device having a display unit for displaying a symbol and a transmission unit for transmitting information relating to a failure of the device itself; an information storage means for storing the information relating to the failure transmitted from the information processing device; and an output means for outputting the information relating to the fault stored in the access destination specified by the symbol to the user terminal that reads the symbol; A control program that functions as a

Images