Software update systems, electronic devices and software update programs

Abstract

To provide a software update system, electronic equipment, and software update program that can improve the possibility of updating software of an electronic equipment at a timing desired by a user. [Solution] The system comprises an image processing device 20 and an application management system 30 that manages the application programs of the image processing device 20, and the image processing device 20 sets the timing for updating the application program in accordance with instructions from a user, and when the current date and time reaches the timing, the image processing device 20 obtains an update application for updating the application program from the application management system 30 and updates the application program using the update application (S274).

Description

[Technical Field]

[0001] The present invention relates to a software update system for updating software in an electronic device, an electronic device, and a software update program. [Background technology]

[0002] BACKGROUND ART Conventionally, it has been known that software of an image forming apparatus can be updated by a service person on-site or remotely (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-187377 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional technology, when updating software on an image forming device, the software to be updated needs to be stopped on the image forming device, which poses a problem in that the timing of the software update on the image forming device needs to be coordinated between the user of the electronic device and the service person.

[0005] Therefore, an object of the present invention is to provide a software update system, an electronic device, and a software update program that can improve the possibility of updating the software of an electronic device at a timing desired by the user. [Means for solving the problem]

[0006] The software update system of the present invention comprises an electronic device and a software management system that manages the software of the electronic device, wherein the electronic device sets the timing of updating specific software as the specific software in accordance with instructions from a user, and when the current date and time reaches the timing, the electronic device obtains update software as the software for updating the specific software from the software management system and updates the specific software using the update software.

[0007] With this configuration, in the software update system of the present invention, when the current date and time reaches the timing set in accordance with instructions from the user, the electronic device obtains update software for updating the specific software from the software management system, and the electronic device updates the specific software using the update software, thereby improving the possibility of updating the software of the electronic device at the timing desired by the user.

[0008] In the software update system of the present invention, the software is assigned a software ID as identification information, the electronic device transmits the software ID of the specific software and the version of the specific software to the software management system, and the software management system identifies the update software so that the software ID transmitted from the electronic device and the software ID of the update software are the same and the version of the update software is newer than the version transmitted from the electronic device.

[0009] With this configuration, the software update system of the present invention reduces the possibility of an electronic device updating specific software with inappropriate update software, since the software management system identifies the update software so that the software ID of the specific software sent from the electronic device to the software management system is the same as the software ID of the update software, and the version of the update software is newer than the version of the specific software sent from the electronic device to the software management system.

[0010] In the software update system of the present invention, the electronic device may transmit a system user ID as identification information of a user of the software management system to the software management system, and the software management system may identify the update software so that the system user ID transmitted from the electronic device is within the range of system user IDs targeted by the update software.

[0011] With this configuration, the software update system of the present invention has the software management system identify the update software so that the system user ID sent from the electronic device to the software management system is within the range of system user IDs targeted by the update software, thereby reducing the possibility of the electronic device updating specified software with inappropriate update software.

[0012] In the software update system of the present invention, the electronic device may transmit the destination of the electronic device to the software management system, and the software management system may identify the update software so that the destination transmitted from the electronic device is included in an area in which the update software can be deployed.

[0013] With this configuration, the software update system of the present invention reduces the possibility of an electronic device updating specified software using inappropriate update software, since the software management system identifies the update software so that the destination of the electronic device sent from the electronic device to the software management system is included in the area in which the update software can be deployed.

[0014] In the software update system of the present invention, the electronic device may issue a notice in advance of the specific software update before the specific software update.

[0015] With this configuration, the software update system of the present invention issues a notice informing the user of an upcoming update of specific software before the specific software is updated, thereby reducing the possibility of updating the software of an electronic device at an inappropriate time.

[0016] In the software update system of the present invention, the electronic device may notify the result of updating the specific software.

[0017] With this configuration, the software update system of the present invention notifies the user of the results of updating specific software, thereby improving convenience.

[0018] In the software update system of the present invention, the software management system may notify the electronic device of a one-time URL, in which at least one of an expiration date and the number of downloads is set, as a URL for downloading the update software.

[0019] With this configuration, the software update system of the present invention reduces the possibility of illegally downloading update software, since the software management system notifies the electronic device of a one-time URL for downloading the update software, which has at least one of an expiration date and the number of downloads set.

[0020] The electronic device of the present invention is characterized in that the timing of updating specific software as specific software is set in accordance with instructions from a user, and when the current date and time reaches said timing, update software as the software for updating the specific software is obtained from a software management system that manages the software, and the specific software is updated using the update software.

[0021] With this configuration, when the current date and time reaches the timing set in accordance with instructions from the user, the electronic device of the present invention obtains update software for updating the specific software from the software management system and updates the specific software using the update software, thereby improving the possibility of updating the software of the electronic device at the timing desired by the user.

[0022] The software update program of the present invention is characterized in that it causes an electronic device to perform the following operations: set the timing of updating specific software as specific software in accordance with instructions from a user; and, when the current date and time reaches the timing, obtain update software as the software for updating the specific software from a software management system that manages the software, and update the specific software using the update software.

[0023] With this configuration, when the current date and time reaches the timing set in accordance with instructions from the user, the electronic device that executes the software update program of the present invention obtains update software for updating the specific software from the software management system and updates the specific software with the update software, thereby improving the possibility of updating the software of the electronic device at the timing desired by the user. [Effects of the Invention]

[0024] The software update system, electronic device, and software update program of the present invention can improve the possibility that the software of the electronic device can be updated at the timing desired by the user. [Brief explanation of the drawings]

[0025] [Figure 1] 1 is a block diagram of a system according to an embodiment of the present invention. [Figure 2] 2 is a block diagram of an example of the image processing device shown in FIG. 1 when configured as an MFP. [Figure 3] 3 is a diagram showing an example of device management information shown in FIG. 2. FIG. [Figure 4] FIG. 3 is a diagram illustrating an example of application management information illustrated in FIG. [Figure 5] 3 is a diagram showing an example of device user management information shown in FIG. 2. FIG. [Figure 6] FIG. 3 is a diagram showing an example of an update condition shown in FIG. 2. [Figure 7]FIG. 2 is a block diagram of an example of the application management system shown in FIG. 1 when configured by one computer. [Figure 8] FIG. 8 is a diagram showing an example of application information shown in FIG. 7. [Figure 9] 3 is a flowchart of the operation of the image processing device shown in FIG. 2 when a device user logs in. [Figure 10] 3 is a sequence diagram of the operation of the image processing device shown in FIG. 2 when generating a system user ID. [Figure 11] FIG. 2 is a sequence diagram of the operation of the system shown in FIG. 1 when the use of an update service is registered. [Figure 12] FIG. 2 is a sequence diagram of the operation of the system shown in FIG. 1 when presenting information about recommended applications. [Figure 13] FIG. 2 is a sequence diagram of the operation of the system shown in FIG. 1 when a URL for installing a recommended application is presented. [Figure 14] FIG. 2 is a sequence diagram of the operation of the system shown in FIG. 1 when a recommended application is installed in the image processing device. [Figure 15] 3 is a sequence diagram of the operation of the image processing device shown in FIG. 2 when setting update conditions. FIG. [Figure 16] FIG. 16 is a diagram showing an example of an update condition setting screen displayed in the operation shown in FIG. 15. [Figure 17] 10 is a flowchart of the operation of the image processing device shown in FIG. 2 when a pre-update notification is executed. [Figure 18] FIG. 2 is a sequence diagram of the operation of the system shown in FIG. 1 when an update service is being executed. [Figure 19] FIG. 19 is a sequence diagram of the "update application download" shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

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

[0027] First, the configuration of a software updating system according to an embodiment of the present invention will be described.

[0028] FIG. 1 is a block diagram of a system 10 according to the present embodiment.

[0029] 1, the system 10 includes an image processing device 20 as an electronic device that processes images. The system 10 may also include at least one other image processing device similar to the image processing device 20. The image processing device may be configured, for example, by an MFP (Multifunction Peripheral).

[0030] The system 10 includes an application management system 30 as a software management system that manages application programs as software for the image processing device. The application management system 30 may be configured with a single computer such as a PC (Personal Computer), or may be configured with multiple computers. For example, the application management system 30 may be configured on a cloud.

[0031] FIG. 2 is a block diagram of an example of the image processing device 20 when configured as an MFP.

[0032] As shown in Figure 2, the image processing device 20 is a computer that includes an operation unit 21, which is an operation device such as a button through which various operations are input; a display unit 22, which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a printer 23, which is a printing device that prints images on a recording medium such as paper; a scanner 24, which is a reading device that reads images from a document; a communication unit 25, which is a communication device that communicates with an external device via a network such as a LAN (Local Area Network) or the Internet, or directly via a wired or wireless connection without using a network; a fax communication unit 26, which is a fax device that communicates with an external facsimile device (not shown) via a communication line such as a public telephone line; a memory unit 27, which is a non-volatile memory device such as a semiconductor memory or an HDD (Hard Disk Drive) that stores various information; and a control unit 28 that controls the entire image processing device 20.

[0033] The storage unit 27 stores an image processing program 27a for processing images. The image processing program 27a may be installed in the image processing device 20 during the manufacturing stage of the image processing device 20, or may be additionally installed in the image processing device 20 from an external storage medium such as a USB (Universal Serial Bus) memory, or may be additionally installed in the image processing device 20 from a network. The image processing program 27a is also a program for updating an application program as software for the image processing device, and constitutes a software update program of the present invention.

[0034] The storage unit 27 can store an application program 27b that can be added as an add-on to extend the functions of the image processing device 20. The storage unit 27 can store at least one other application program that can be added as an add-on to extend the functions of the image processing device 20, in addition to the application program 27b.

[0035] The storage unit 27 can store device management information 27c that manages information about the image processing device 20.

[0036] FIG. 3 is a diagram showing an example of the device management information 27c.

[0037] The device management information 27c shown in Fig. 3 includes the serial number of the image processing device 20, the MAC (Media Access Control) address of the image processing device 20, and the destination of the image processing device 20. The destination may be, for example, Japan, America, Europe, Asia, etc. The device management information 27c shown in Fig. 3 is drawn with some information omitted.

[0038] As shown in FIG. 2, the storage unit 27 can store application management information 27d for managing information on all application programs installed in the image processing device 20.

[0039] FIG. 4 is a diagram showing an example of the application management information 27d.

[0040] The application management information 27d shown in Fig. 4 includes, for each application program, an application ID as identification information for the application program, the region in which the application program can be deployed (hereinafter referred to as the "deployment-enabled region"), the application program version, the version on which the application program is based (i.e., the root version), and the application program type. The deployment-enabled regions include, for example, Japan, America, Europe, and Asia. There are two types of application programs: resident applications that are always deployed in RAM (Random Access Memory), and non-resident applications that are deployed in RAM in response to a user instruction. The application management information 27d shown in Fig. 4 is illustrated with some information omitted.

[0041] As shown in FIG. 2, the storage unit 27 can store device user management information 27e for managing users of the image processing device 20 (hereinafter referred to as "device users").

[0042] FIG. 5 is a diagram showing an example of the device user management information 27e.

[0043] The device user management information 27e shown in Fig. 5 includes, for each device user, a user name as identification information of the device user, a password of the device user, and a role of the device user. Roles include, for example, a general user as a general user of the image processing device 20, and an administrator of the image processing device 20 (hereinafter referred to as a "device administrator"). The device user management information 27e shown in Fig. 5 is drawn with some information omitted. The device user management information 27e can be edited, for example, by the device administrator operating the operation unit 21.

[0044] 2, the storage unit 27 can store an email address 27f for receiving notifications related to the management of application programs. The email address 27f can be input by, for example, a device administrator operating the operation unit 21.

[0045] The storage unit 27 can store identification information (hereinafter referred to as "system user ID") 27g of a user (hereinafter referred to as "system user") of the application management system 30 (see FIG. 1).

[0046] The storage unit 27 can store an update condition 27h for an application program (hereinafter referred to as an "update condition"). The storage unit 27 may be able to store at least one update condition other than the update condition 27h.

[0047] FIG. 6 is a diagram showing an example of the update condition 27h.

[0048] The update condition 27h shown in FIG. 6 includes the timing of an application program update (hereinafter referred to as "update timing"), the application program to be updated (hereinafter referred to as "update target application"), pre-update notification information indicating whether a notification before an application program update (hereinafter referred to as "pre-update notification") is valid, and update result notification information indicating whether a notification of the result of the application program update (hereinafter referred to as "update result notification") is valid. The update timing includes a type of update timing and a specific value of the update timing. The update timing types include a specific periodic update that attempts to update the application program at a specific period, a specific date update that attempts to update the application program on a specific day, and a specific date and time update that attempts to update the application program at a specific date and time. The update condition 27h shown in FIG. 6 is drawn with some information omitted.

[0049] 2 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) that serves as a memory used as a work area for the CPU of control unit 28. The CPU of control unit 28 executes programs stored in storage unit 27 or the ROM of control unit 28.

[0050] By executing image processing program 27a, control unit 28 realizes: user operation unit 28a that controls input from operation unit 21 and display on display unit 22; device function unit 28b that executes functions inherent to image processing device 20; application execution management unit 28c that manages the execution state of application programs, such as starting and stopping application programs; application update management unit 28d that manages updates to application programs; and device information management unit 28e that manages device management information 27c and application management information 27d. The functions inherent to image processing device 20 include, for example, a copy function that prints images scanned by scanner 24 using printer 23; a print function that prints using printer 23 based on print data received via communication unit 25; and a fax transmission function that sends faxes via fax communication unit 26. Application update management unit 28d monitors whether or not there are any applications to be updated and can update the applications to be updated when necessary.

[0051] FIG. 7 is a block diagram of an example of the application management system 30 when configured by one computer.

[0052] As shown in FIG. 7, the application management system 30 includes an operation unit 31, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 32, which is a display device such as an LCD that displays various information; a communication unit 33, which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via a wired or wireless connection without using a network; a memory unit 34, which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information; and a control unit 35 that controls the entire application management system 30.

[0053] The storage unit 34 can store an application management program 34a for managing application programs of the image processing device. The application management program 34a may be installed in the application management system 30 during the manufacturing stage of the application management system 30, or may be additionally installed in the application management system 30 from an external storage medium such as a USB memory, or may be additionally installed in the application management system 30 from a network.

[0054] The storage unit 34 stores an application program 34b to be installed in the image processing device. The storage unit 34 may be capable of storing at least one other application program to be installed in the image processing device in addition to the application program 34b.

[0055] The storage unit 34 is capable of storing information 34c about application programs (hereinafter referred to as "application information").

[0056] FIG. 8 is a diagram showing an example of the application information 34c.

[0057] 8 includes, for each application program, the system user ID of the system user who manages the image processing device in which the application program is installed, the application ID of the application program, the version of the application program, and the destination of the image processing device in which the application program is installed. Some information is omitted from the application information 34c shown in FIG.

[0058] 7, the storage unit 34 can store a system user ID 34d. The storage unit 34 may also be capable of storing at least one system user ID other than the system user ID 34d. The storage unit 34 can store a system user ID for each system user.

[0059] The control unit 35 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM as memory used as a work area for the CPU of the control unit 35. The CPU of the control unit 35 executes programs stored in the storage unit 34 or the ROM of the control unit 35.

[0060] By executing the application management program 34a, the control unit 35 realizes an application management unit 35a that manages the application programs of the image processing device, an application information management unit 35b that manages application information 34c, and a download information generation AI (Artificial Intelligence) 35c that generates information for the image processing device to download the application program.

[0061] The operation of the system 10 will now be described.

[0062] In the following, the image processing device 20 will be described as a representative example of image processing devices. However, image processing devices other than the image processing device 20 can also perform the same operations as the image processing device 20.

[0063] First, the operation of the image processing device 20 when a device user logs in will be described.

[0064] FIG. 9 is a flowchart showing the operation of the image processing device 20 when a device user logs in.

[0065] A device user can instruct the image processing device 20 to display a login screen via the operation unit 21 of the image processing device 20. When the user operation unit 28a of the image processing device 20 is instructed to display the login screen, the user operation unit 28a instructs the device function unit 28b to display the login screen. When the device function unit 28b of the image processing device 20 is instructed to display the login screen, the device function unit 28b executes the operation shown in FIG.

[0066] 9, the device function unit 28b causes the display unit 22 to display a login screen via the user operation unit 28a (S101). Therefore, the device user can input the user name and password of the device user into the login screen displayed on the display unit 22 via the operation unit 21 and the user operation unit 28a.

[0067] When the process of S101 ends, the device function unit 28b determines whether or not a user name and a password have been input on the login screen until it determines that a user name and a password have been input on the login screen (S102).

[0068] If the device function unit 28b determines in S102 that a user name and password have been entered on the login screen, it performs authentication based on the combination of the user name and password entered on the login screen (S103). Specifically, if the combination of the user name and password entered on the login screen is included in the device user management information 27e, the device function unit 28b determines that the authentication has been successful. On the other hand, if the combination of the user name and password entered on the login screen is not included in the device user management information 27e, the device function unit 28b determines that the authentication has failed.

[0069] After the process of S103 is completed, the device function unit 28b determines whether the authentication executed in S103 is successful (S104).

[0070] If the device function unit 28b determines in S104 that the authentication has been successful, it displays permission for the device user's login on the display unit 22 via the user operation unit 28a (S105), and ends the operation shown in FIG.

[0071] If the device function unit 28b determines in S104 that the authentication has failed, it displays on the display unit 22 via the user operation unit 28a that the device user's login is not permitted (S106), and ends the operation shown in FIG.

[0072] Next, the operation of the image processing device 20 when generating a system user ID will be described.

[0073] FIG. 10 is a sequence diagram of the operation of the image processing device 20 when generating a system user ID.

[0074] When the device administrator has already logged in to the image processing device 20, the device administrator can instruct the image processing device 20 to generate a system user ID via the operation unit 21. Note that the image processing device 20 does not permit a general user to instruct the image processing device 20 to generate a system user ID.

[0075] When the user operation unit 28a of the image processing device 20 is instructed to generate a system user ID, the user operation unit 28a instructs the application update management unit 28d to generate a system user ID, as shown in FIG. 10 (S121).

[0076] Upon receiving the instruction in S121, the application update management unit 28d generates a system user ID based on the email address 27f (S122).

[0077] When the process of S122 is completed, the application update management unit 28d notifies the user operation unit 28a of the system user ID generated in S122 (S123).

[0078] Upon receiving the notification in S123, the user operation unit 28a displays the system user ID notified in S123 on the display unit 22 (S124).

[0079] Therefore, the device administrator can recognize the system user ID.

[0080] Next, the operation of the system 10 when the use of an application program update service (hereinafter referred to as "update service") is registered will be described.

[0081] FIG. 11 is a sequence diagram of the operation of the system 10 when the use of the update service is registered.

[0082] If the device administrator has already logged in to the image processing device 20, the device administrator can specify the system user ID displayed in S124 and then instruct the image processing device 20 to register for use of the update service via the operation unit 21. Note that the image processing device 20 does not permit general users to instruct the image processing device 20 to register for use of the update service.

[0083] When the user operation unit 28a of the image processing device 20 is instructed to register for use of the update service, the user operation unit 28a instructs the application update management unit 28d to register for use of the update service (S141), as shown in Fig. 11. Here, the user operation unit 28a includes the system user ID designated by the device administrator in the instruction in S141.

[0084] Upon receiving the instruction in S141, the application update management unit 28d instructs the device information management unit 28e to register the system user ID included in the instruction in S141 (S142).

[0085] Upon receiving the instruction in S142, the device information management unit 28e stores the system user ID included in the instruction in S142 as the system user ID 27g in the storage unit 27 (S143).

[0086] When the process of S143 ends, the device information management unit 28e notifies the application update management unit 28d of the completion of the registration of the system user ID (S144).

[0087] When the process of S142 ends, the application update management unit 28d instructs the application management system 30 to register the system user ID included in the instruction in S141 (S145).

[0088] Upon receiving the instruction in S145, the application information management unit 35b of the application management system 30 stores the system user ID included in the instruction in S145 as the system user ID 34d in the storage unit 34 (S146).

[0089] When the process of S146 ends, the application information management unit 35b notifies the image processing device 20 of the completion of the registration of the system user ID (S147).

[0090] When the application update management unit 28d of the image processing device 20 receives both the notification in S144 and the notification in S147, the application update management unit 28d starts the update service (S148).

[0091] When the process of S148 ends, the application update management unit 28d instructs the user operation unit 28a to display a screen indicating that registration for use of the update service has been completed (hereinafter referred to as a "registration completion screen") (S149).

[0092] Upon receiving the instruction in S149, user operation unit 28a displays a registration completion screen on display unit 22 in accordance with the instruction in S149 (S150).

[0093] Next, the operation of the system 10 when installing an application program in the image processing device 20 will be described.

[0094] FIG. 12 is a sequence diagram of the operation of the system 10 when the application management system 30 presents information on application programs recommended by the system 10 (hereinafter referred to as "recommended applications").

[0095] When the device administrator has already logged in to the image processing device 20, the device administrator can specify the content of the application program desired by the device administrator (hereinafter referred to as "desired content") and then instruct the image processing device 20 to present information about recommended apps via the operation unit 21. Note that the image processing device 20 does not allow general users to instruct the image processing device 20 to present information about recommended apps.

[0096] When the user operation unit 28a of the image processing device 20 is instructed to present information about recommended applications, the user operation unit 28a instructs the application update management unit 28d to present information about recommended applications (S161), as shown in Fig. 12. Here, the user operation unit 28a includes desired content specified by the device administrator in the instruction in S161.

[0097] Upon receiving the instruction in S161, the application update management unit 28d instructs the application management system 30 to present information about recommended applications (S162). Here, the application update management unit 28d includes the desired content included in the instruction in S161 in the instruction in S162.

[0098] Upon receiving the instruction in S162, the application information management unit 35b of the application management system 30 instructs the application management unit 35a to present information on recommended applications (S163). Here, the application information management unit 35b includes the desired content included in the instruction in S162 in the instruction in S163.

[0099] Upon receiving the instruction in S163, the application management unit 35a instructs the download information generation AI 35c to present information about recommended applications (S164). Here, the application management unit 35a includes the desired content included in the instruction in S163 in the instruction in S164.

[0100] Upon receiving the instruction in S164, the download information generation AI 35c identifies recommended applications that correspond to the desired content included in the instruction in S164 from among the application programs on the storage unit 34 (S165).

[0101] When the process of S165 is completed, the download information generation AI 35c notifies the application management unit 35a of the information on the application program identified in S165 as information on recommended applications (S166).

[0102] Upon receiving the notification in S166, the application management unit 35a notifies the application information management unit 35b of the information on the recommended applications notified in S166 (S167).

[0103] Upon receiving the notification in S167, the application information management unit 35b notifies the image processing device 20 of the information on the recommended applications notified in S167 (S168).

[0104] Upon receiving the notification in S168, the application update management unit 28d of the image processing device 20 notifies the user operation unit 28a of the information on the recommended application notified in S168 (S169).

[0105] Upon receiving the notification in S169, the user operation unit 28a displays the information about the recommended applications notified in S169 on the display unit 22 (S170).

[0106] FIG. 13 is a sequence diagram of the operation of the system 10 when a URL for installing a recommended application is presented.

[0107] The device administrator can request the image processing device 20 via the operation unit 21 to send a Uniform Resource Locator (URL) for downloading the recommended application displayed on the display unit 22 in S170.

[0108] When a URL for downloading a recommended application is requested, the user operation unit 28a of the image processing device 20 requests the URL for downloading the recommended application from the application update management unit 28d, as shown in FIG. 13 (S181).

[0109] Upon receiving the request in S181, the application update management unit 28d requests the application management system 30 for the URL for downloading the recommended application requested in S181 (S182).

[0110] When the application information management unit 35b of the application management system 30 receives the request in S182, it requests the application management unit 35a for the URL for downloading the recommended application requested in S182 (S183).

[0111] Upon receiving the instruction in S183, the application management unit 35a requests the download information generation AI 35c to send the URL for downloading the recommended application requested in S183 (S184).

[0112] Upon receiving the request in S184, the download information generation AI 35c generates a URL for downloading the recommended app requested in S184 and a message for installing the recommended app (S185). The download information generation AI 35c may generate a one-time URL in S185, in which at least one of an expiration date and the number of downloads is set. The download information generation AI 35c may manage the URL generated in S185 by linking it to, for example, the system user ID of the image processing device 20 and the recommended app. For example, the download information generation AI 35c may generate the URL in S185 based on at least one of the system user ID of the image processing device 20, the app ID of the recommended app, the version of the recommended app, the base version of the recommended app, and the destination of the image processing device 20.

[0113] When the process of S185 is completed, the download information generation AI 35c notifies the application management unit 35a of the URL and message generated in S185 (S186).

[0114] Upon receiving the notification in S186, the application management unit 35a notifies the application information management unit 35b of the URL and message notified in S186 (S187).

[0115] Upon receiving the notification in S187, the application information management unit 35b notifies the image processing device 20 of the URL and message notified in S187 (S188).

[0116] Upon receiving the notification in S188, the application update management unit 28d of the image processing device 20 notifies the user operation unit 28a of the URL and message notified in S188 (S189).

[0117] Upon receiving the notification in S189, user operation unit 28a displays the URL and message notified in S189 on display unit 22 (S190).

[0118] FIG. 14 is a sequence diagram of the operation of the system 10 when a recommended application is installed in the image processing device 20. In FIG.

[0119] The device administrator can issue an instruction to install the recommended application by clicking the URL displayed on the display unit 22 via the operation unit 21 in S190.

[0120] When a URL displayed on the display unit 22 is clicked, the user operation unit 28a notifies the application update management unit 28d of the clicked URL, as shown in FIG. 14 (S201).

[0121] Upon receiving the notification in S201, the application update management unit 28d requests the recommended application indicated by the URL notified in S201 from the application management system 30 (S202).

[0122] Upon receiving the request in S202, the application management unit 35a of the application management system 30 transmits the recommended applications requested in S202 to the image processing device 20 (S203).

[0123] When the application update management unit 28d of the image processing device 20 receives the recommended applications transmitted in S203, the application update management unit 28d installs the received recommended applications in the image processing device 20 (S204).

[0124] When the process of S204 ends, the application update management unit 28d requests the device information management unit 28e to record the application ID, version, base version, and type of the recommended application installed in S204 (S205).

[0125] Upon receiving the request in S205, the device information management unit 28e stores the application ID, version, base version, and type of the recommended application, the recording of which was requested in S205, in the application management information 27d (S206).

[0126] Next, the operation of the image processing device 20 when setting update conditions will be described.

[0127] FIG. 15 is a sequence diagram of the operation of the image processing device 20 when setting update conditions.

[0128] When the device administrator has already logged in to the image processing device 20, the device administrator can instruct the image processing device 20 to start the process of setting update conditions via the operation unit 21. Note that the image processing device 20 does not permit a general user to instruct the image processing device 20 to start the process of setting update conditions.

[0129] When the user operation unit 28a of the image processing device 20 is instructed to start the process of setting update conditions, it requests the application IDs of all application programs installed in the image processing device 20 from the application update management unit 28d, as shown in FIG. 15 (S221).

[0130] Upon receiving the request in S221, the application update management unit 28d requests the application IDs of all application programs installed in the image processing device 20 from the device information management unit 28e (S222).

[0131] Upon receiving the request in S222, the device information management unit 28e notifies the application update management unit 28d of the application IDs of all application programs installed in the image processing device 20, the destination of the image processing device 20, and the system user ID 27g (S223). Here, the application update management unit 28d identifies the application IDs of all application programs installed in the image processing device 20 based on the application management information 27d. The application update management unit 28d also identifies the destination of the image processing device 20 based on the device management information 27c.

[0132] Upon receiving the notification in S223, the application update management unit 28d instructs the user operation unit 28a to display a screen for setting update conditions (hereinafter referred to as an "update condition setting screen") (S224). The update condition setting screen is generated by the application update management unit 28d.

[0133] When the user operation unit 28a receives the instruction in S224, it displays the update condition setting screen 50 (see, for example, FIG. 16) on the display unit 22 (S225).

[0134] FIG. 16 is a diagram showing an example of the update condition setting screen 50. As shown in FIG.

[0135] 16 includes a radio button 51a for specifying "specific periodic update" as the type of update timing, a radio button 51b for specifying "specific date update" as the type of update timing, a radio button 51c for specifying "specific date and time update" as the type of update timing, a drop-down list 52 for specifying a specific update period for the specific periodic update, a drop-down list 53 for specifying a specific update date for the specific date update, drop-down lists 54a and 54b for specifying a specific update date and time for the specific date and time update, a drop-down list 55 for specifying an application to be updated, a check box 56 for enabling pre-update notification, a check box 57 for enabling update result notification, and a register button 58 for registering the settings specified on the update condition setting screen 50. Only one of the radio buttons 51a to 51c is always selected. The options in the drop-down list 55 are the application IDs notified by the device information management unit 28e in S223.

[0136] As shown in FIG. 15, when the registration button 58 is pressed after the processing of S225 is completed, the user operation unit 28a instructs the application update management unit 28d to register the update conditions that were specified on the update condition setting screen 50 at the time the registration button 58 was pressed (S226).

[0137] Upon receiving the instruction in S226, the application update management unit 28d stores the update conditions instructed to be registered in S226 in the storage unit 27 (S227). Here, the application update management unit 28d stores the update conditions instructed to be registered in S226 in the storage unit 27 in association with the system user ID, application ID, and destination notified in S223.

[0138] When the process of S227 ends, the application update management unit 28d restarts the update service so that the update conditions registered in S227 are used in the update service (S228).

[0139] Next, the operation of the image processing device 20 when executing pre-update notification will be described.

[0140] FIG. 17 is a flowchart showing the operation of the image processing device 20 when executing pre-update notification.

[0141] When the update service is being executed, the application update management unit 28d executes the operation shown in FIG.

[0142] As shown in FIG. 17, the application update management unit 28d determines whether or not the time is a specific period before any of the update timings indicated in the update conditions for which the value of the pre-update notification information stored in the memory unit 27 is valid, until it determines that the time is a specific period before any of the update timings indicated in the update conditions for which the value of the pre-update notification information stored in the memory unit 27 is valid (S241).

[0143] If the application update management unit 28d determines in S241 that the value of the pre-update notification information stored in the memory unit 27 is valid within a specific period of time before any of the update timings indicated in the update conditions, the application update management unit 28d sends an email to the email address 27f to notify that an update of the application program will be performed after the specific period of time (S242), and executes the process of S241.

[0144] Next, the operation of the system 10 when an update service is running will be described.

[0145] 18 is a sequence diagram of the operation of the system 10 when the update service is being executed. FIG. 19 is a sequence diagram of "downloading an application for update" shown in FIG.

[0146] When the current date and time reaches any of the update timings indicated in the update conditions stored in the memory unit 27, the application update management unit 28d requests the application execution management unit 28c to stop the application program (hereinafter referred to as the "target application" in the description of the operation shown in Figures 18 and 19) that is the target of the update condition for which the current date and time has reached the update timing, as shown in Figures 18 and 19 (S261).

[0147] Upon receiving the request in S261, if the target application is running at the time of receiving the request in S261, the application execution management unit 28c stops the target application in accordance with the request in S261 (S262).

[0148] If the target application has already been stopped at the time of receiving the request in S261, or if the stopping of the target application in S262 has been completed, the application execution management unit 28c notifies the application update management unit 28d of the success of stopping the target application (S263).

[0149] Upon receiving the notification in S263, the application update management unit 28d requests a URL for downloading an application program for updating the target application (hereinafter referred to as the "update application") from the application management system 30 (S264). The application update management unit 28d includes in the request in S264 the system user ID 27g, the application ID of the target application, the version of the target application, the base version of the target application, and the destination of the image processing device 20.

[0150] Upon receiving the request at S264, the application information management unit 35b of the application management system 30 identifies an application to be updated from among the application programs stored in the storage unit 34, based on the information included in the request at S264 (S265). For example, the application information management unit 35b may identify the application to be updated so that the system user ID included in the request at S264 falls within the range of system user IDs targeted by the application to be updated. Alternatively, the application information management unit 35b may identify the application to be updated so that the application ID included in the request at S264 is the same as the application ID assigned to the application to be updated. Alternatively, the application information management unit 35b may identify the application to be updated so that the version of the application to be updated is newer than the version included in the request at S264. Alternatively, the application information management unit 35b may identify the application to be updated so that the destination included in the request at S264 falls within the deployment area of ​​the application to be updated.

[0151] When the process of S265 ends, the application information management unit 35b requests the application management unit 35a for the URL for downloading the update application identified in S265 (S266).

[0152] Upon receiving the request in S266, the application management unit 35a requests the download information generation AI 35c to provide the URL for downloading the update application requested in S266 (S267).

[0153] Upon receiving the request in S267, the download information generation AI 35c generates a URL for downloading the update application and a message for updating the target application, as requested in S267 (S268). The download information generation AI 35c may generate a one-time URL in S268, in which at least one of an expiration date and the number of downloads is set. The download information generation AI 35c may manage the URL generated in S268 by linking it to, for example, the system user ID of the image processing device 20 and the update application. For example, the download information generation AI 35c may generate the URL in S268 based on at least one of the system user ID of the image processing device 20, the application ID of the update application, the version of the update application, the base version of the update application, and the destination of the image processing device 20.

[0154] When the process of S268 is completed, the download information generation AI 35c notifies the application management unit 35a of the URL and message generated in S268 (S269).

[0155] Upon receiving the notification in S269, the application management unit 35a notifies the application information management unit 35b of the URL and message notified in S269 (S270).

[0156] Upon receiving the notification in S270, the application information management unit 35b notifies the image processing device 20 of the URL and message notified in S270 (S271).

[0157] Upon receiving the notification in S271, the application update management unit 28d of the image processing device 20 requests the application for update indicated by the URL notified in S271 from the application management system 30 (S272). Note that, although not shown, upon receiving the notification in S271, the application update management unit 28d causes the message notified in S271 to be displayed on the display unit 22 via the user operation unit 28a.

[0158] Upon receiving the request in S272, the application management unit 35a of the application management system 30 transmits the application for update requested in S272 to the image processing device 20 (S273).

[0159] When the application update management unit 28d of the image processing device 20 receives the application for update transmitted in S273, the application update management unit 28d installs the received application for update in the image processing device 20, thereby updating the target application (S274).

[0160] After the process of S274 ends, if the target application is a resident application, the application update management unit 28d requests the application execution management unit 28c to start the target application updated in S274 (S275).

[0161] Upon receiving the request in S275, the application execution management unit 28c starts the target application (S276).

[0162] After the processing of S274 is completed, if the target application is not a resident application, or if the processing of S275 is completed, the application update management unit 28d requests the device information management unit 28e to update the record of the version of the target application so that the version of the target application stored in the application management information 27d becomes the version of the update application (S277).

[0163] Upon receiving the request in S277, the device information management unit 28e updates the version of the target application in the application management information 27d (S278).

[0164] In addition, if the value of the update result notification information in the update conditions that are the target of the operations shown in Figures 18 and 19 is valid, when the operations shown in Figures 18 and 19 are completed, the application update management unit 28d sends an email to email address 27f indicating that the application program has been updated.

[0165] As described above, in the system 10, when the current date and time reaches the timing set in accordance with instructions from the user, the image processing device 20 obtains an update application for updating the application program from the application management system 30 (S264 to S273), and the image processing device 20 updates the application program using the update application (S274), thereby improving the possibility of updating the software of the image processing device 20 at the timing desired by the user.

[0166] In the system 10, the soft ID of the application program transmitted from the image processing device 20 to the application management system 30 is the same as the soft ID of the update application, and the application management system 30 identifies the update application (S265) so that the version of the update application is newer than the version of the application program transmitted from the image processing device 20 to the application management system 30, thereby reducing the possibility that the image processing device 20 will update the application program using an inappropriate update application.

[0167] In the system 10, the application management system 30 identifies the update application so that the system user ID sent from the image processing device 20 to the application management system 30 is included in the range of system user IDs targeted by the update application (S265), thereby reducing the possibility that the image processing device 20 will update an application program using an inappropriate update application.

[0168] In the system 10, the application management system 30 identifies the update application so that the destination of the image processing device 20 sent from the image processing device 20 to the application management system 30 is included in the region where the update application can be deployed (S265), thereby reducing the possibility that the image processing device 20 will update the application program using an inappropriate update application.

[0169] The system 10 issues a notice in advance of an application program update before the application program is updated (S242), thereby reducing the possibility of updating the software of the image processing device 20 at an inappropriate time.

[0170] The system 10 notifies the result of updating the application program, thereby improving convenience.

[0171] In the system 10, the application management system 30 notifies the image processing device 20 of a one-time URL for downloading the update application, in which at least one of an expiration date and the number of downloads is set (S268 to S271), thereby reducing the possibility of the update application being illegally downloaded.

[0172] In this embodiment, the software of the present invention is an application program. However, the software of the present invention may be software other than an application program. For example, the software of the present invention may be firmware for an image processing device.

[0173] In this embodiment, the electronic device of the present invention is an image processing device, but the electronic device of the present invention may be an electronic device other than an image processing device. [Explanation of symbols]

[0174] 10 System (Software Update System) 20 Image processing device (electronic device) 27a Image processing program (software update program) 27b Application Programs (Software) 27g System User ID 30 App Management System (Software Management System) 34b Application Program 34d System User ID

Claims

1. Electronic devices and a software management system for managing software of the electronic device; Equipped with the electronic device sets the timing of updating the specific software as the specific software in response to an instruction from a user; A software update system characterized in that, when the current date and time reaches the timing, the electronic device obtains update software as the software for updating the specific software from the software management system and updates the specific software using the update software.

2. The software is assigned a soft ID as identification information, The electronic device transmits the software ID of the specific software and the version of the specific software to the software management system; The software update system described in claim 1, characterized in that the software management system identifies the update software so that the software ID sent from the electronic device is the same as the software ID of the update software, and the version of the update software is newer than the version sent from the electronic device.

3. The electronic device transmits a system user ID as identification information of the user of the software management system to the software management system, The software update system described in claim 1, characterized in that the software management system identifies the update software so that the system user ID transmitted from the electronic device is within the range of the system user ID targeted by the update software.

4. The electronic device transmits the destination of the electronic device to the software management system; The software update system of claim 1, characterized in that the software management system identifies the update software so that the destination sent from the electronic device is included in an area in which the update software can be deployed.

5. 2. The software update system according to claim 1, wherein the electronic device issues a notice informing the user of the specific software update before the specific software update.

6. 2. The software update system according to claim 1, wherein the electronic device notifies the user of the result of updating the specific software.

7. 2. The software update system according to claim 1, wherein the software management system notifies the electronic device of a one-time URL, which is set with at least one of an expiration date and a number of downloads, as a URL for downloading the update software.

8. The timing of updating specific software as specific software is set according to instructions from the user, When the current date and time reaches the timing, an electronic device obtains update software as the software for updating the specific software from a software management system that manages the software, and updates the specific software using the update software.

9. An operation of setting the timing of updating the specific software in accordance with an instruction from a user; When the current date and time reaches the timing, an operation of obtaining update software as the software for updating the specific software from a software management system that manages the software, and updating the specific software with the update software; A software update method characterized by causing an electronic device to execute the above.

Images