Management program, information processing device, and management method

Abstract

To reduce a data communication amount of an information processing device.SOLUTION: A management program causes a control part included in a portable terminal 3 to execute application registration processing. A management system 1 includes a management device 2 for managing a plurality of printers 4, a plurality of portable terminals 3 configured to be able to perform data communication with the plurality of printers 4, and a cloud server 5 configured to be able to perform data communication with the management device 2 and the plurality of portable terminals 3. The application registration processing registers printer acquisition information in the cloud server 5. The printer acquisition information includes printer identification information, printer setting information, and acquisition date information. The printer setting information is information related to setting of a connected printer. The acquisition date information shows an acquisition date when setting applied to the connected printer is acquired.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a technique for managing a terminal device. [Background technology]

[0002] Patent Document 1 describes that a mobile terminal configured to be able to perform data communication with an external server and a printer downloads firmware from the external server and installs the firmware in the printer. [Prior art documents] [Patent documents]

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

[0004] In this way, in an information processing device configured to relay data between a server and a terminal device (for example, a printer), it is desirable to reduce the amount of data communication. The present disclosure aims to reduce the amount of data communication in an information processing device. [Means for solving the problem]

[0005] One aspect of the present disclosure is a management program used in a management system that manages a plurality of terminal devices, configured to cause a control unit included in an information processing device to execute application registration processing.

[0006] The management system includes a management device that manages a plurality of terminal devices, a plurality of information processing devices configured to be able to communicate data with the plurality of terminal devices, and a storage device configured to be able to communicate data with the management device and the plurality of information processing devices.

[0007] The application registration process registers device registration information in a storage device, the device registration information including device identification information that identifies a connected terminal device, which is a terminal device connected to an information processing device so that data communication is possible, device setting information regarding device settings, which are settings of the connected terminal device, and application date information indicating the application date, which is the date on which the device settings are applied to the connected terminal device.

[0008] The management program of the present disclosure, configured in this manner, can prevent device registration information with an application date earlier than the date indicated by the application date information from being unnecessarily registered in the storage device, based on the application date information contained in the device registration information already registered in the storage device, thereby reducing the amount of data communication between the storage device and the information processing device.

[0009] Another aspect of the present disclosure is an information processing device used in a management system that manages a plurality of terminal devices, configured to execute application registration processing. The information processing device of the present disclosure is a device controlled by the management program of the present disclosure, and can obtain the same effects as the management program of the present disclosure.

[0010] Yet another aspect of the present disclosure is a management method executed by an information processing device in a management system that manages multiple terminal devices, in which device registration information including device identification information, device setting information, and application date information is registered in a storage device.

[0011] The management method of the present disclosure is a method executed by the management program of the present disclosure, and by executing this method, it is possible to obtain the same effects as the management program of the present disclosure. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a management system. [Figure 2] FIG. 2 is a block diagram showing the configuration of a management device and a mobile terminal. [Figure 3] FIG. 2 is a block diagram showing the configuration of a printer and a cloud server. [Figure 4] 4 is a flowchart showing an installation process according to the first embodiment. [Figure 5] FIG. 10 is a diagram illustrating a method for installing firmware. [Figure 6] 10 is a flowchart showing a setting registration process. [Figure 7] 10A and 10B are diagrams illustrating registration and discarding of printer setting information. [Figure 8] 10 is a diagram showing two examples of registration of printer acquisition information. [Figure 9] 10 is a flowchart showing an installation process according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] [First embodiment] A first embodiment of the present disclosure will be described below with reference to the drawings. (1) Overall structure As shown in Figure 1, the management system 1 of this embodiment is a network system configured in which a management device 2 manages multiple printers 4 located at multiple locations via multiple mobile terminals 3 and a cloud server 5.

[0014] A plurality of mobile terminals 3 located at a first location and a plurality of printers 4 located at the first location are configured to be able to communicate with each other via short-range wireless communication in accordance with the Bluetooth standard or via wired communication using USB. USB is an abbreviation for Universal Serial Bus. Bluetooth is a registered trademark.

[0015] Similarly, a plurality of mobile terminals 3 located at a second location and a plurality of printers 4 located at a second location are configured to be able to communicate with each other via short-range wireless communication in accordance with the Bluetooth standard or via wired communication using USB.

[0016] The management device 2 and the plurality of mobile terminals 3 are configured to be able to communicate with a cloud server 5 via a wide area network. In the management system 1 of this embodiment, for example, the management device 2 can collect information from a plurality of printers 4, and the management device 2 can change the settings of a plurality of printers 4.

[0017] (2) Equipment configuration 2, the management device 2 is a personal computer, and includes a control unit 11, a communication unit 12, a display unit 13, an input unit 14, and a storage unit 15. The control unit 11 includes a CPU 21 and a memory 22. The CPU 21 as a processor executes processing in accordance with a computer program stored in the storage unit 15. The memory 22 is used as a work memory when the above processing is executed.

[0018] The storage unit 15 includes storage such as a solid state drive and a hard disk drive, and stores various computer programs and data. A management program 15a is stored in the storage unit 15. The management program 15a is a computer program that causes the CPU 21 to implement the management functions that should be implemented by the management device 2.

[0019] The communication unit 12 communicates data with the cloud server 5 via a wide area network. The display unit 13 includes a display device (not shown) and displays various images on the display device. The input unit 14 outputs input operation information for identifying input operations performed by a user (i.e., an administrator) of the management device 2 via a keyboard and mouse.

[0020] The portable terminal 3 is assigned to each worker who performs work using the printer 4 and is carried by the worker. The portable terminal 3 includes a control unit 31, a communication unit 32, a display unit 33, an input unit 34, and a storage unit 35. The control unit 31 includes a CPU 41 and a memory 42. The CPU 41 as a processor executes processing in accordance with a computer program stored in the storage unit 35. The memory 42 is used as a work memory when the above processing is executed.

[0021] The memory unit 35 includes storage such as a solid state drive and a hard disk drive, and stores various computer programs and data. A management program 35a is stored in the memory unit 35. The management program 35a is a computer program that causes the CPU 41 to implement management functions that should be implemented by the mobile terminal 3.

[0022] The communication unit 32 performs data communication with the cloud server 5 via a wide area network. The communication unit 32 also performs data communication with the printer 4 by short-range wireless communication in accordance with the Bluetooth standard or by wired communication using USB.

[0023] The display unit 33 includes a display device (not shown) and displays various images on the display device. The input unit 34 includes a touch panel installed on the display screen of the display unit 33 and switches installed around the periphery of the display screen of the display unit 33. The input unit 34 outputs input operation information for identifying input operations performed by the worker via the touch panel and the switches.

[0024] The printer 4 is a small, lightweight mobile printer that can be carried by the operator. As shown in Fig. 3, the printer 4 includes a control unit 51, a communication unit 52, a display unit 53, an input unit 54, and a printing unit 55.

[0025] The control unit 51 includes a CPU 61 and a memory 62. The CPU 61 executes programs stored in the memory 62, thereby realizing various functions of the printer 4. The communication unit 52 performs data communication with the mobile terminal 3 by short-distance wireless communication in accordance with the Bluetooth standard or by wired communication using USB.

[0026] The display unit 53 includes a display device (not shown) and displays various images on the display device. The input unit 54 includes switches arranged around the periphery of the display screen of the display unit 53. The input unit 54 outputs input operation information for identifying the input operation performed by the worker via the switches.

[0027] The printing unit 55 has a thermal printing mechanism and can print images on thermal roll paper. Note that the printing unit 55 may be configured to be able to print on cut paper, or may be configured to be able to print using a well-known recording method other than the thermal method (for example, an inkjet method).

[0028] The cloud server 5 includes a control unit 71, a communication unit 72, a first storage 73, and a second storage 74. The control unit 71 includes a CPU 81 and a memory . The CPU 81 as a processor executes processes in accordance with computer programs stored in the memory 82. The processes executed by the CPU 81 include processes for causing the cloud server 5 to function as cloud storage.

[0029] The cloud storage includes a table storage and an object storage. When the control unit 71 executes the above process, the first storage 73 functions as a table storage, and the second storage 74 functions as an object storage.

[0030] The exemplary first storage 73 functions as a NoSQL data store and is configured to be able to store tables each made up of a group of schema-less entities. The exemplary second storage 74 functions as an object storage that can read and write any text file and binary file as an object from the outside using the HTTP / HTTPS protocol.

[0031] Microsoft Azure is a well-known cloud service that provides the above-mentioned table storage and object storage. The cloud server 5 can operate in the same manner as such a cloud service. Azure is a registered trademark.

[0032] (3) Processing Executed on the Mobile Terminal 3 Next, a description will be given of the procedure of the installation process executed by the control unit 31 of the mobile terminal 3. The installation process is a process that is repeatedly executed while the mobile terminal 3 is in operation.

[0033] When the installation process is executed, the CPU 41 of the control unit 31 first determines whether a preset firmware acquisition condition is met in S10, as shown in Fig. 4. In this embodiment, the firmware acquisition condition is, for example, the passage of a preset firmware acquisition period.

[0034] If the firmware acquisition condition is not met, the CPU 41 ends the installation process. On the other hand, if the firmware acquisition condition is met, the CPU 41 downloads, in S20, all firmware that has not been acquired by the mobile terminal 3 from the firmware uploaded to the second storage 74 of the cloud server 5. The management device 2 uploads firmware for all models of printers 4 managed by the management system 1 to the second storage 74 of the cloud server 5.

[0035] Next, in S30, the CPU 41 determines whether the firmware downloaded in S20 includes firmware that corresponds to the model of the printer 4 (hereinafter, the connected printer) connected to the mobile terminal 3. If there is no firmware that corresponds to the model of the connected printer, the CPU 41 ends the installation process.

[0036] On the other hand, if firmware corresponding to the model of the connected printer is available, the CPU 41 accesses the installation table T1 of the first storage 73 of the cloud server 5 in S40 to acquire firmware installation information for the connected printer.

[0037] 5, the installation table T1 stores firmware installation information for each of the multiple printers 4 managed by the management system 1. The firmware installation information includes printer identification information that identifies the printer 4, firmware identification information, and installation date information.

[0038] The firmware identification information is information for identifying the firmware applied to the printer 4. The firmware identification information includes information indicating the model that the firmware is compatible with and information indicating the version of the firmware.

[0039] The installation date information indicates the date on which the firmware installation was completed. The installation date information may include the time (i.e., hour, minute, and second) in addition to the date.

[0040] When the processing of S40 ends, the CPU 41 determines in S50 whether the firmware for the connected printer (hereinafter referred to as compatible firmware) from the firmware downloaded in S20 is already installed in the connected printer, based on the firmware installation information acquired in S40, as shown in Fig. 4. Specifically, if the CPU 41 acquires firmware installation information in S40 that includes printer identification information that matches the connected printer and firmware identification information that matches the model and version of the compatible firmware, it determines that the compatible firmware is already installed in the connected printer.

[0041] If the compatible firmware has already been installed in the connected printer, the CPU 41 displays an application completion message in S60 and terminates the installation process. Specifically, in S60, the CPU 41 displays an application completion window W1 on the display screen of the display unit 33, as shown in FIG. 5, indicating that the settings corresponding to the compatible firmware have been applied.

[0042] On the other hand, if the compatible firmware is not installed in the connected printer, the CPU 41 displays an application instruction in S70, as shown in Fig. 4. Specifically, in S70, the CPU 41 displays an application instruction window W2, which instructs the application of settings corresponding to the compatible firmware, on the display screen of the display unit 33, as shown in Fig. 5. The application instruction window W2 includes an apply button B1 that is operated by the operator to instruct the start of installation.

[0043] When the process of S70 ends, the CPU 41 determines whether or not an apply operation has been performed in S80, as shown in Fig. 4. Specifically, the CPU 41 determines that an apply operation has been performed when input operation information indicating that the apply button B1 has been operated is output from the input unit 14.

[0044] If the application operation has not been performed, the CPU 41 repeats the process of S80 to wait until the application operation is performed. Then, when the application operation is performed, the CPU 41 installs, in S90, the firmware for the connected printer, which was downloaded in S20, into the connected printer.

[0045] Then, in S100, the CPU 41 registers the firmware installation information in the installation table T1 of the first storage 73 of the cloud server 5, and ends the installation process. Note that if firmware installation information including the same printer identification information as that of the connected printer has already been registered in the installation table T1, the CPU 41 registers the new firmware installation information by overwriting the already registered firmware installation information. The firmware installation information registered in S100 includes printer identification information that identifies the connected printer, firmware identification information that indicates the model and version of the firmware installed in S90, and installation date information that indicates the date the firmware was installed in the connected printer in S90.

[0046] Here, the installation of firmware when two mobile terminals 3 are connected to the same printer 4 on different days will be described. 5, first, it is assumed that the mobile terminal 3a is connected to the printer 4 having printer identification information “ZZZ” (hereinafter referred to as printer ZZZ). Then, it is assumed that the mobile terminal 3a downloads the latest firmware compatible with the model of printer ZZZ from the cloud server 5.

[0047] In this case, because firmware installation information for the latest firmware corresponding to the model of Printer ZZZ is not registered in the installation table T1, the mobile terminal 3a displays an application instruction window W2. When the worker operates the apply button B1 in the application instruction window W2, the latest firmware corresponding to the model of Printer ZZZ is installed on Printer ZZZ. In FIG. 5, the installation of the latest firmware for Printer ZZZ is represented as "Setting X2."

[0048] When the installation is complete, the mobile terminal 3a registers firmware installation information FI1 with the cloud server 5, as indicated by arrow L1. In the firmware installation information FI1 in Figure 5, the printer identification information of printer ZZZ is "ZZZ," the firmware model and version are "X2," and the date the installation was completed is "2021-08-01."

[0049] Thereafter, the mobile terminal 3b is connected to the printer ZZZ. The mobile terminal 3b then downloads from the cloud server 5 the latest firmware compatible with the model of the printer ZZZ.

[0050] In this case, as indicated by arrow L2, mobile terminal 3b accesses installation table T1 of first storage 73 of cloud server 5 and acquires firmware installation information FI1 of the connected printer. Because firmware installation information FI1 of the latest firmware corresponding to the model of printer ZZZ is registered in installation table T1, mobile terminal 3b displays applied window W1 on the display screen of display unit 33 and does not install the firmware.

[0051] Next, a description will be given of the procedure of the setting registration process executed by the control unit 31 of the mobile terminal 3. The setting registration process is a process that is repeatedly executed while the mobile terminal 3 is in operation. When the setting registration process is executed, the CPU 41 of the control unit 31 first determines whether a preset setting acquisition condition is met in S210, as shown in Fig. 6. In this embodiment, the setting acquisition condition is, for example, the passage of a preset setting acquisition period.

[0052] If the setting acquisition period has not been established, the CPU 41 proceeds to S240. On the other hand, if the setting acquisition period has been established, the CPU 41 acquires printer setting information from the connected printer in S220. The printer setting information is information related to the settings of the connected printer, and includes, for example, the number of prints, the firmware version, etc.

[0053] Then, in S230, the CPU 41 registers the printer acquisition information in the setting table T2 of the first storage 73 of the cloud server 5, and proceeds to S240. Note that if printer acquisition information including the same printer identification information as that of the connected printer has already been registered in the setting table T2, the CPU 41 registers the new printer acquisition information by overwriting the already registered printer acquisition information. As shown in FIG. 7, the setting table T2 stores printer acquisition information for each of the multiple printers 4 managed by the management system 1. The printer acquisition information includes printer identification information, printer setting information, acquisition date information, and registration date information.

[0054] The acquisition date information indicates the date when the printer setting information was acquired from the connected printer. The registration date information indicates the date when the printer acquisition information was registered in the setting table T2. The acquisition date information and registration date information may include the time in addition to the date.

[0055] When the process proceeds to S240, the CPU 41 determines whether or not there is any printer setting information that has failed to be registered, as shown in Fig. 6. If there is no printer setting information that has failed to be registered, the CPU 41 ends the setting registration process.

[0056] On the other hand, if there is any printer setting information that has failed to be registered, the CPU 41 determines in S250 whether a preset re-registration condition has been met. In this embodiment, the re-registration condition is, for example, the elapse of a preset re-registration period.

[0057] If the re-registration condition is not met, the CPU 41 ends the setting registration process. On the other hand, if the re-registration condition is met, the CPU 41 accesses the setting table T2 of the first storage 73 of the cloud server 5 in S260 to acquire printer acquisition information of the connected printer.

[0058] Then, in S270, the CPU 41 determines whether or not it is necessary to register the printer setting information that failed to be registered. Specifically, the CPU 41 determines that it is necessary to register the printer setting information that failed to be registered if the acquisition date indicated by the acquisition date information in the printer acquisition information acquired in S260 is earlier than the acquisition date of the printer setting information that failed to be registered.

[0059] Here, if it is necessary to register the printer setting information that failed to be registered, the CPU 41 registers the printer acquisition information including the printer setting information that failed to be registered in the setting table T2 of the first storage 73 of the cloud server 5 in S280, and terminates the setting registration process.

[0060] On the other hand, if it is not necessary to register the printer setting information that failed to be registered, the CPU 41 discards the printer setting information that failed to be registered in S290 and ends the setting registration process. Here, the registration of printer acquisition information in a case where two mobile terminals 3 are connected to the same printer 4 on different days will be described.

[0061] As shown in FIG. 7, first, assume that mobile terminal 3b connects to printer ZZZ on July 31, 2021. Then, assume that mobile terminal 3b acquires printer setting information from printer ZZZ. Furthermore, assume that mobile terminal 3b attempts to register printer acquisition information including the acquired printer setting information on cloud server 5, but fails to register due to a network problem or the like. Therefore, mobile terminal 3b temporarily stores the printer setting information acquired from printer ZZZ together with acquisition date information in the storage unit 35 of mobile terminal 3b.

[0062] 7 includes printer setting information and acquisition date information acquired from printer ZZZ. In the internal storage information M1 in FIG. 7, the printer setting information acquired by the mobile terminal 3b from printer ZZZ is represented as "abcde", and the acquisition date is represented as "2021-07-31".

[0063] Then, on August 1, 2021, the mobile terminal 3a connects to the printer ZZZ. The mobile terminal 3a acquires the printer setting information from the printer ZZZ. The mobile terminal 3a then attempts to register the printer acquisition information including the acquired printer setting information on the cloud server 5, but fails to register due to a network problem or the like.

[0064] Then, on August 2, 2021, the mobile terminal 3a registers printer acquisition information PR1, which includes printer setting information acquired from printer ZZZ, in the setting table T2 of the first storage 73 of the cloud server 5, as shown by arrow L3.

[0065] Furthermore, on August 3, 2021, when the mobile terminal 3b re-registers the printer acquisition information including the printer setting information acquired from printer ZZZa in the cloud server 5 based on the internal storage information M1, it accesses the setting table T2 of the cloud server 5 as shown by arrow L4 and acquires the printer acquisition information PR1.

[0066] Here, the portable terminal 3b discards the internally stored information M1 because the acquisition date indicated by the acquisition date information of the printer acquisition information PR1 is later than the acquisition date of the internally stored information M1. Also, the mobile terminal 3b temporarily stores internal storage information M2 of the printer 4 (hereinafter referred to as the WWW printer) whose printer identification information is "WWW" in the storage unit 35 of the mobile terminal 3b. In the internal storage information M2, the printer setting information acquired from the WWW printer is written as "vwxyz" and the acquisition date is written as "2021-08-03".

[0067] Then, when the mobile terminal 3b re-registers the printer acquisition information of the WWW printer in the cloud server 5 based on the internal storage information M2, it acquires the printer acquisition information PR2 of the WWW printer. Here, since the acquisition date indicated by the acquisition date information of the printer acquisition information PR2 is earlier than the acquisition date of the internally stored information M2, the mobile terminal 3b registers the printer acquisition information based on the internally stored information M2 in the setting table T2 of the cloud server 5.

[0068] Next, two examples of registration of printer acquisition information when two mobile terminals 3a and 3b are connected to printer ZZZ on different days will be described. 8, mobile terminal 3a is connected to printer ZZZ on August 1st and acquires printer setting information from printer ZZZ. However, mobile terminal 3a fails to register the printer acquisition information in setting table T2 of cloud server 5. The solid circles SC1 and SC2 in chart C1 indicate that the printer setting information was acquired but the registration of the printer acquisition information in cloud server 5 failed.

[0069] Furthermore, the mobile terminal 3b is connected to the printer ZZZ on August 2nd and acquires the printer setting information from the printer ZZZ. However, the mobile terminal 3b fails to register the printer acquisition information in the setting table T2 of the cloud server 5.

[0070] Thereafter, on the same day, the mobile terminal 3b re-registers the printer acquisition information in the cloud server 5. The white circle OC1 in the chart C1 indicates that the printer acquisition information has been registered in the cloud server 5.

[0071] Furthermore, when the mobile terminal 3a re-registers the printer acquisition information in the cloud server 5 on August 3rd, the acquisition date of the printer acquisition information registered in the cloud server 5 is later than the acquisition date when the mobile terminal 3a acquired the printer setting information from the printer ZZZ, so the mobile terminal 3a discards the printer setting information acquired from the printer ZZZ.

[0072] 8, mobile terminal 3a is connected to printer ZZZ on August 1st and acquires printer setting information from printer ZZZ. However, mobile terminal 3a fails to register the printer acquisition information in setting table T2 of cloud server 5. The solid circles SC3 and SC4 in chart C2 indicate that the printer setting information was acquired but the registration of the printer acquisition information in cloud server 5 failed.

[0073] Furthermore, the mobile terminal 3b is connected to the printer ZZZ on August 2nd and acquires the printer setting information from the printer ZZZ. However, the mobile terminal 3b fails to register the printer acquisition information in the setting table T2 of the cloud server 5.

[0074] Then, the mobile terminal 3a re-registers the printer acquisition information in the cloud server 5 on August 3. The white circles OC2 and OC3 in chart C2 indicate that the printer acquisition information has been registered in the cloud server 5.

[0075] Furthermore, when mobile terminal 3b re-registers the printer acquisition information in cloud server 5 on August 4th, the acquisition date of the printer acquisition information registered in cloud server 5 is earlier than the acquisition date when mobile terminal 3b acquired the printer setting information from printer ZZZ, so mobile terminal 3b re-registers the printer acquisition information in cloud server 5.

[0076] (4) Effects The management program 35a configured in this manner is used in the management system 1 that manages a plurality of printers 4, and is configured to cause the control unit 31 included in the mobile terminal 3 to execute application registration processing.

[0077] The management system 1 includes a management device 2 that manages multiple printers 4, multiple mobile terminals 3 that are configured to be able to communicate data with the multiple printers 4, and a cloud server 5 that is configured to be able to communicate data with the management device 2 and the multiple mobile terminals 3.

[0078] The application registration process registers firmware installation information in the cloud server 5. The firmware installation information includes printer identification information that identifies the connected printer, which is the printer 4 connected to the mobile terminal 3 so that data communication is possible, firmware identification information that identifies the firmware applied to the printer 4, and installation date information that indicates the installation date when the firmware was installed in the connected printer.

[0079] The application registration process also registers printer acquisition information in the cloud server 5. The printer acquisition information includes printer identification information, printer setting information, and acquisition date information. The printer setting information is information about the settings of the connected printer. The acquisition date information indicates the acquisition date when the settings applied to the connected printer were acquired.

[0080] Such a management program 35a can prevent firmware installation information with an installation date earlier than the date indicated by the installation date information from being unnecessarily registered on the cloud server 5, based on the installation date information contained in the firmware installation information already registered on the cloud server 5, thereby reducing the amount of data communication between the cloud server 5 and the mobile terminal 3.

[0081] In addition, the management program 35a can prevent printer acquisition information with an acquisition date earlier than the date indicated by the acquisition date information from being unnecessarily registered on the cloud server 5 based on the acquisition date information contained in the printer acquisition information already registered on the cloud server 5, thereby reducing the amount of data communication between the cloud server 5 and the mobile terminal 3.

[0082] The printer acquisition information further includes registration date information indicating the registration date, which is the date on which the printer acquisition information is registered on the cloud server 5. This allows the management program 35a to make the management device 2 and the multiple mobile terminals 3 check the registration date of the printer acquisition information.

[0083] The management program 35a is also configured to cause the control unit 31 to further execute a re-execution process and an execution prohibition process. The re-execution process is a process of executing the application registration process again when the printer acquisition information could not be registered in the cloud server 5 in the application registration process.

[0084] The execution prohibition process obtains printer acquisition information corresponding to the connected printer from the cloud server 5 before executing the re-execution process, and prohibits the execution of the re-execution process if the acquisition date indicated by the acquisition date information included in the acquired cloud server 5 is later than the acquisition date indicated by the acquisition date information included in the acquisition date information that was attempted to be registered in the application registration process.

[0085] Such a management program 35a can prevent printer acquisition information with an acquisition date earlier than the date indicated by the acquisition date information from being unnecessarily registered on the cloud server 5 based on the acquisition date information contained in the printer acquisition information already registered on the cloud server 5, thereby reducing the amount of data communication between the cloud server 5 and the mobile terminal 3.

[0086] In the embodiment described above, the printer 4 corresponds to a terminal device, the mobile terminal 3 corresponds to an information processing device, and the cloud server 5 corresponds to a storage device. In addition, printer identification information corresponds to device identification information, firmware identification information and printer setting information correspond to device setting information, installation date information and acquisition date information correspond to application date information, and firmware installation information and printer acquisition information correspond to device registration information.

[0087] Furthermore, S100 and S230 correspond to application registration processing, S280 corresponds to re-execution processing, and S260 and S270 correspond to execution prohibition processing. [Second embodiment] A second embodiment of the present disclosure will be described below with reference to the drawings. In the second embodiment, only the parts that are different from the first embodiment will be described. The same reference numerals will be used to designate common components.

[0088] The management system 1 of the second embodiment differs from the first embodiment in that the installation process has been changed. As shown in FIG. 9, the installation process of the second embodiment differs from that of the first embodiment in that the processes of S40 and S50 are omitted and that the processes of S45 and S55 are added.

[0089] That is, if firmware corresponding to the model of the connected printer is available in S30, the CPU 41 accesses the connected printer in S45 and checks whether the corresponding firmware has already been installed in the connected printer.

[0090] Then, in S55, the CPU 41 determines whether the compatible firmware has been installed in the connected printer based on the confirmation result in S45. If the compatible firmware has been installed, the CPU 41 proceeds to S60. On the other hand, if the compatible firmware has not been installed, the CPU 41 proceeds to S70.

[0091] The management device 2 of the management system 1 configured in this way is configured to upload firmware indicating the changed printer settings to the cloud server 5 when changing the printer settings of multiple printers 4.

[0092] When the mobile terminal 3 downloads the firmware from the cloud server 5, the mobile terminal 3 is configured to execute a setting change process for changing the printer settings of the connected printer based on the firmware.

[0093] The management program 35a is configured to cause the control unit 31 to further execute a setting confirmation process and a change prohibition process. The setting confirmation process determines whether the printer settings corresponding to the firmware downloaded from the cloud server 5 are applied to the connected printer by performing data communication with the connected printer.

[0094] The change prohibition process prohibits the execution of the setting change process when it is determined in the setting confirmation process that the printer settings corresponding to the downloaded firmware are applied to the connected printer.

[0095] Such a management program 35a can prevent the occurrence of a situation in which the setting change process is executed unnecessarily, and can reduce the processing load on the mobile terminal 3. In the embodiment described above, the firmware corresponds to the setting change information, S90 corresponds to the setting change process, S45 corresponds to the setting confirmation process, and S55 corresponds to the change prohibition process.

[0096] Although one embodiment of the present disclosure has been described above, the present disclosure is not limited to the above embodiment and can be implemented in various modifications. For example, in the above embodiment, the terminal device of the present disclosure is the printer 4. However, the terminal device of the present disclosure may be any device that is connected to the end of a network and has the function of communicating with other devices, and may be, for example, a multifunction device, a copier, or a facsimile machine that has a scanner function for reading an image from a document.

[0097] In the above embodiments, multiple functions of one component may be realized by multiple components, or one function of one component may be realized by multiple components. Furthermore, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, part of the configuration of the above embodiments may be omitted. Furthermore, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

[0098] In addition to the mobile terminal 3 described above, the present disclosure can also be realized in various forms, such as a system that includes the mobile terminal 3 as a component, a program for causing a computer to function as the mobile terminal 3, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a management method. [Explanation of symbols]

[0099] 1... management system, 2... management device, 3... mobile terminal, 4... printer, 5... cloud server, 31... control unit, 35a... management program

Claims

1. A management program used in a management system that manages a plurality of terminal devices, The management system includes: a management device that manages the plurality of terminal devices; a plurality of information processing devices configured to be able to perform data communication with the plurality of terminal devices; a storage device configured to be able to perform data communication with the management device and the plurality of information processing devices; The management program is configured to cause a control unit of the information processing device to: and executing an application registration process for registering, in the storage device, device registration information including device identification information for identifying a connected terminal device that is the terminal device connected to the information processing device so as to be able to perform data communication, device setting information relating to device settings that are settings of the connected terminal device, and application date information indicating an application date that is a date on which the device settings are applied to the connected terminal device, The device registration information further includes registration date information indicating a registration date, which is a date on which the device registration information is registered in the storage device.

2. A management program used in a management system that manages multiple terminal devices, The management system includes: a management device that manages the plurality of terminal devices; a plurality of information processing devices configured to be able to perform data communication with the plurality of terminal devices; a storage device configured to be able to perform data communication with the management device and the plurality of information processing devices; The management program is configured to cause a control unit of the information processing device to: an application registration process for registering, in the storage device, device registration information including device identification information for identifying a connected terminal device that is the terminal device connected to the information processing device so as to be able to perform data communication, device setting information relating to device settings that are settings of the connected terminal device, and application date information indicating an application date that is the date on which the device setting is applied to the connected terminal device; a re-execution process for re-executing the application registration process when the device registration information cannot be registered in the storage device in the application registration process; an execution prohibition process of acquiring the device registration information corresponding to the connected terminal device from the storage device before executing the re-execution process, and prohibiting execution of the re-execution process if the application date indicated by the application date information included in the acquired device registration information is later than the application date indicated by the application date information included in the device registration information that was to be registered in the application registration process; The management program that is configured to run

3. 3. The management program according to claim 1, the management device is configured to, when changing the device settings of the plurality of terminal devices, upload setting change information indicating the changed device settings to the storage device; the information processing device is configured to, when downloading the setting change information from the storage device, execute a setting change process for changing the device setting of the connected terminal device based on the setting change information; The control unit further includes: a setting confirmation process configured to determine whether the device settings corresponding to the setting change information downloaded from the storage device are applied to the connection terminal device by performing data communication with the connection terminal device; a change prohibition process for prohibiting execution of the setting change process when it is determined in the setting confirmation process that the device setting corresponding to the downloaded setting change information is applied to the connected terminal device; The management program that is configured to run

4. An information processing device used in a management system that manages a plurality of terminal devices, The management system includes: a management device that manages the plurality of terminal devices; a plurality of the information processing devices configured to be able to perform data communication with a plurality of the terminal devices; a storage device configured to be able to perform data communication with the management device and the plurality of information processing devices; The control unit of the information processing device is configured to execute an application registration process for registering, in the storage device, device registration information including device identification information for identifying a connected terminal device that is the terminal device connected to the information processing device so as to be able to perform data communication, device setting information relating to device settings that are settings of the connected terminal device, and application date information indicating an application date that is a date on which the device settings are applied to the connected terminal device, The information processing device, wherein the device registration information further includes registration date information indicating a registration date that is a date on which the device registration information is registered in the storage device.

5. An information processing device used in a management system that manages multiple terminal devices, The management system includes: a management device that manages the plurality of terminal devices; a plurality of the information processing devices configured to be able to perform data communication with a plurality of the terminal devices; a storage device configured to be able to perform data communication with the management device and the plurality of information processing devices; The control unit of the information processing device an application registration process for registering, in the storage device, device registration information including device identification information for identifying a connected terminal device that is the terminal device connected to the information processing device so as to be able to perform data communication, device setting information relating to device settings that are settings of the connected terminal device, and application date information indicating an application date that is the date on which the device setting is applied to the connected terminal device; a re-execution process for re-executing the application registration process when the device registration information cannot be registered in the storage device in the application registration process; an execution prohibition process of acquiring the device registration information corresponding to the connected terminal device from the storage device before executing the re-execution process, and prohibiting execution of the re-execution process if the application date indicated by the application date information included in the acquired device registration information is later than the application date indicated by the application date information included in the device registration information that was to be registered in the application registration process; An information processing device configured to execute the above.

6. A management method executed by an information processing device in a management system that manages a plurality of terminal devices, The management system includes: a management device that manages the plurality of terminal devices; a plurality of the information processing devices configured to be able to perform data communication with a plurality of the terminal devices; a storage device configured to be able to perform data communication with the management device and the plurality of information processing devices; The management method includes: registering, in the storage device, device registration information including device identification information for identifying a connected terminal device that is the terminal device connected to the information processing device so as to be able to perform data communication, device setting information relating to device settings that are settings of the connected terminal device, and application date information indicating an application date that is a date on which the device settings are applied to the connected terminal device; The device registration information further includes registration date information indicating a registration date, which is a date on which the device registration information is registered in the storage device.

7. A management method executed by an information processing device in a management system that manages a plurality of terminal devices, comprising: The management system includes: a management device that manages the plurality of terminal devices; a plurality of the information processing devices configured to be able to perform data communication with a plurality of the terminal devices; a storage device configured to be able to perform data communication with the management device and the plurality of information processing devices; The management method includes: executes an application registration process to register, in the storage device, device registration information including device identification information for identifying a connected terminal device that is the terminal device connected to the information processing device so as to be able to perform data communication, device setting information relating to device settings that are settings of the connected terminal device, and application date information indicating an application date that is a date on which the device settings are applied to the connected terminal device; If the device registration information cannot be registered in the storage device in the application registration process, a re-execution process is executed to re-execute the application registration process; A management method in which, before executing the re-execution process, the device registration information corresponding to the connected terminal device is obtained from the storage device, and if the application date indicated by the application date information included in the obtained device registration information is later than the application date indicated by the application date information included in the device registration information that was attempted to be registered in the application registration process, an execution prohibition process is executed to prohibit the execution of the re-execution process.

Images