JP5732889B2 - Program update management server and program update management method - Google Patents

Description

  The present invention relates to a program update management server and a program update management method, and more particularly to a technology for automatically updating a computer program executed on an electronic device.

  2. Description of the Related Art Conventionally, a technique for realizing automatic update of a computer program (hereinafter simply referred to as a program) by polling update information provided by a server is known. For example, when a program installed on a PC (Personal Computer) ends or when a preset date and time arrives, the PC accesses the server via the network, and the latest version of the program installed on the PC Get information that can be specified. If the program installed on the PC is not the latest, the PC automatically downloads the latest program from the server.

JP 2006-243915 A JP 2007-213370 A

However, when the polling cycle is set to be long, there is a problem that the update timing is delayed. On the other hand, if the polling cycle is set short, the download to a large number of clients is concentrated in a short period of time immediately after the latest program can be downloaded, resulting in an increase in network traffic and server load.
The present invention was created to solve this problem, and an object thereof is to automatically update a program efficiently at an appropriate timing.

  (1) A program update management server for achieving the above object has a storage means for storing an update program for updating a program to be managed, and an update recommendation timing distributed to each client in which the program to be managed is installed Setting means for setting the update recommendation timing, update recommendation means for sending update recommendation information to the client corresponding at the update recommendation timing, and sending the update program to the client receiving the update recommendation information Program transmission means.

  According to the present invention, since the update program is transmitted to the client in accordance with the update recommendation timing set by the program update management server, the client program can be automatically updated efficiently at an appropriate timing.

(2) In the program update management server for achieving the above object, the setting means specifies the use frequency of the management target program installed in the client based on status information received from the client, and uses the use The update recommendation timing may be set according to the frequency.
According to the present invention, it is possible to adjust the timing for transmitting the update program to the client according to the frequency of use of the program.

(3) In the program update management server for achieving the above object, the setting means receives client information from the client that is the difference between the version of the management target program installed in the client and the version of the update program. The update recommendation timing may be set based on the difference.
According to the present invention, it is possible to adjust the timing for transmitting an update program to a client in accordance with the version of a program installed on the client.

(4) In the program update management server for achieving the above object, the program transmission means may transmit the update program in response to a program request received from the client.
According to the present invention, the update program can be transmitted while avoiding the timing when the client is in a state where it is not desirable to execute other processing such as a busy state.

  Note that the function of each means described in the claims is realized by hardware resources whose function is specified by the configuration itself, hardware resources whose function is specified by a program, or a combination thereof. Further, the functions of these means are not limited to those realized by hardware resources that are physically independent of each other. For example, the server recited in the claims is not limited to that realized by a single computer, and the server may be realized as a group of combinations of a plurality of computers each sharing each means. Furthermore, the present invention can be realized as a method, a computer program for causing the server and printer to realize the above functions, and a recording medium for the program. Of course, the recording medium of the computer program may be a magnetic recording medium, a magneto-optical recording medium, or any recording medium to be developed in the future.

FIG. 1A is a block diagram showing a program update management server and a client, and FIG. 1B is a data structure diagram showing a client database. It is a sequence diagram which shows a setup sequence. It is a sequence diagram which shows the flow of the setting of an update recommendation timing. It is a sequence diagram which shows the flow of the setting of an update recommendation timing. It is a sequence diagram which shows the flow of transmission of an update program.

Embodiments of the present invention will be described below with reference to the accompanying drawings. In addition, the same code | symbol is attached | subjected to the corresponding component in each figure, and the overlapping description is abbreviate | omitted.
1. Configuration FIG. 1A is a block diagram showing a program update management server 1 as an embodiment of the present invention. The program update management server 1 is a server computer that manages the update of a specific program (managed program) installed in each of the plurality of clients 2, 3, 4.

  The program update management server 1 includes a storage unit 11 including a nonvolatile storage medium such as a hard disk, a communication unit 13 connected to a data communication line, a CPU (Central Processing Unit), a RAM (Random Access Memory) and an input (not shown). And a control unit 12 having an output interface. By executing the program update management program installed in the storage unit 11, the control unit 12 stores the update program and client information in a predetermined area of the storage unit 11, or sets an update recommendation timing based on the client information. Or, update recommendation information or an update program is transmitted to the client 2 via the Internet. A client database 211 shown in FIG. 1B is stored in a predetermined area of the storage unit 11. The client database 211 includes an XMPP JID and an XMPP password for communicating with the client 2 via XMPP, identification information of a management target program installed in the client 2, a power status indicating the power status of the client 2, and the client 2 This is a database in which the last printing date and time, the update recommendation timing of the client 2 and the like are registered in association with the client ID which is identification information unique to each client 2. The update recommendation timing is data indicating the date and time.

  Each client 2, 3, 4 has a storage unit 21 including a nonvolatile storage medium such as a hard disk and a flash memory, a communication unit 23 connected to a data communication line, a control including a CPU, a RAM, and an input / output interface (not shown). An electronic device such as a PC, a printer, a facsimile, a mobile phone terminal, etc., provided with the unit 22. The control unit 22 controls the storage unit 21, the communication unit 23, and other devices (not shown) by executing various programs stored in the storage unit 21. Further, the control unit 22 updates the program corresponding to the installer by executing the installer installed in the storage unit 21. Hereinafter, the clients 2, 3, and 4 are printers connected to the Internet, and a print control program as a management target program and an installer for updating the print control program are stored in the storage unit 21. Processing for updating the print control program of the client (printer) 2 will be described.

2. Setup Sequence The print control program installed in the printer 2 becomes a management target program to which an update program is provided from the program update management server 1 when the printer 2 is registered in the program update management server 1. FIG. 2 is a diagram showing a setup sequence for registering the printer 2 in the program update management server 1.

  First, as a registration request corresponding to the printer 2, the printer 2 transmits the model ID and serial number of the printer 2 to the URL of the program update management server 1 corresponding to the registration request using HTTP (S100). This registration request may be automatically activated during setup of the printer 2, may be activated by a user operating an operation panel (not shown) provided in the printer 2, or is connected to the printer 2. It may be activated by the user operating the PC.

  The program update management server 1 that has received the registration request registers the printer 2 in the program update management server 1 based on the registration request (S102). Specifically, the client ID, XMPP JID, and XMPP login password corresponding to the model-specific ID and serial number of the printer 2 included in the registration request are referred to the registration information of other printers that have already been registered. However, it is assigned to the printer 2 so as not to overlap with other printers. Subsequently, the program update management server 1 registers the XMPP JID and the XMPP login password in the client database 211 as registration information in association with the client ID. By assigning the client ID based on the model-specific ID and serial number of the printer 2, even when the serial number is assigned to the printer in a different system for each model, it is ensured that a different client ID is used for each printer body. It can be assigned to the printer 2. The XMPP JID may be assigned by combining the XMPP domain name of the program update management server 1 and the client ID.

  The program update management server 1 that has registered the printer 2 transmits the registration information of the printer 2 to the printer 2 that is the transmission source of the registration request using HTTP (S104). The registration information includes a client ID assigned to the printer 2, an XMPP JID, and an XMPP login password.

  The printer 2 that has received the registration information stores the client ID, XMPP JID, and XMPP login password assigned to the printer 2 in the storage unit 21 (S106).

3. Program update management method The management target program update process is executed at the update recommendation timing that is set when the registered printer 2 is powered on and when a new update program is stored in the program update management server 1 Is done.
FIG. 3 is a sequence diagram showing the flow of processing from when the printer 2 is powered on until it is shut off.

  When the power is turned on, the printer 2 transmits the XMPP JID and the XMPP login password as client information to the program update management server 1 (S200). This process is automatically executed immediately after setup.

  The program update management server 1 that has received the XMPP JID and the XMPP login password establishes an XMPP connection with the printer 2 (S202). Since the XMPP connection is established based on the XMPP JID and the XMPP login password transmitted immediately after the power is turned on, the XMPP JID and the XMPP login password are information for specifying the power status of the printer 2.

  The printer 2 that has established the XMPP connection with the program update management server 1 transmits the client ID and the identification information of the program to be managed to the program update management server 1 as client information using HTTP or XMPP (S204). The identification information of the management target program is information that can uniquely specify the type of the print control program, the version of the print control program, the printer menu type, the printer submenu type, the printer language, and the like. If the client ID can be uniquely specified based on the XMPP JID or the like, it is not necessary to send the client ID from the printer 2, and the printer menu type, printer submenu type, printer language, etc. are updated recommendation timing. If the information does not affect the information, it is not necessary to transmit them.

  When receiving the client ID and the management target program identification information, the program update management server 1 stores the management target program identification information in association with the client ID (S206). Specifically, the program update management server 1 registers the received identification information in the client database 211 in association with the client ID of the printer 2 and updates the power status to ON.

  Next, the program update management server 1 sets an update recommendation timing for the printer 2 based on the received identification information of the management target program (S207). That is, every time the client is turned on, an update recommendation timing is set for the client that has been turned on. The program update management server 1 is registered with reference to the latest update program version stored in the storage unit 11 of the program update management server 1 and the update recommendation timing of other printers registered in the client database 211. The update recommendation timings of the printer 2 are set so that the update recommendation timings of the plurality of printers that have been distributed are distributed. Specifically, the update recommendation timing of the printer 2 is set such that the higher the usage frequency of the printer 2 is, the faster it is, and the earlier the version of the management target program that is the management target is, the earlier it is. That is, if the printer 2 is frequently used and the version of the management target program is old, the earlier timing among the settable timings is set for the printer 2 as the update recommendation timing. The later timing may be set as the update recommendation timing. The timing that can be set here is an update recommendation per fixed time, rather than the number set as the upper limit of the number of printers that make an update recommendation per fixed time in consideration of the load of the program update management server 1 and the concentration of network traffic. The number of printers for which timing is set is smaller. The usage frequency may be determined to be higher as the last print date is later. Further, it may be determined that the use frequency is higher as the printing start or print end interval is shorter, or the use frequency is higher as the cumulative number of printed sheets is larger. The set update recommendation timing is registered in the client database 211 in association with the client ID of the printer 2. If the version of the management target program is the latest, that is, if the version of the print control program installed in the printer 2 matches the version of the latest update program stored in the program update management server 1. , A value meaning undecided is set as the update recommendation timing. Since the update program is sent to the printer 2 due to the arrival of the update recommendation timing, the update program transmission processing is distributed by distributing the update recommendation timing, and the load of the program update management server 1 and the concentration of network traffic And can be relaxed.

  When the printer 2 is turned on and an event such as printing start, printing end, print setting change or the like occurs, the program update management server 1 displays status information corresponding to the generated event together with the client ID of the printer 2. Is transmitted using HTTP or XMPP (S208). For example, status information indicating the print start date and time is transmitted when printing is started, status information indicating the print end date and time is notified when printing is completed, and status information indicating the print setting after the change is displayed when the print setting is changed. Be notified.

  The program update management server 1 that has received the status information stores the status information in the client database 211 in association with the client ID (S210). At this time, when status information corresponding to the end of printing is received, the program update management server 1 registers the print end date and time in the client database 211 in association with the client ID as the last print date and time. When receiving the number of prints and print settings in response to the end of printing, these may be registered in the client database 211. The program update management server 1 can determine the usage frequency of the printer 2 by storing the last printing date and time. The usage frequency of the printer 2 is indexed by information based on the usage history of the printer 2 that can be specified from the status information, such as the print start or print end interval, the accumulated number of prints, etc., in addition to the last print date and time. You can also.

When the printer 2 receives an operation to shut off the power, the printer 2 transmits a logout notification for ending the XMPP connection to the program update management server 1 (S212).
The program update management server 1 that has received the logout notification terminates the XMPP connection with the printer 2 (S214). At this time, the program update management server 1 updates the client database 211 by changing the power status of the printer 2 whose XMPP connection is terminated to OFF.

FIG. 4 is a sequence diagram showing an operation in which the latest update program is stored in the program update management server 1 and the update recommendation timing is set.
An update program for updating the management target program is stored in the storage unit 11 of the program update management server 1 in accordance with a predetermined operation by the administrator (S300). At this time, the identification information of the update program stored in the storage unit 11 is stored in the storage unit 11 separately from the update program. In this embodiment, the update program is the latest version of the compressed data of the print control program.

  The program update management server 1 storing the latest update program refers to the client database 211 and sets update recommendation timings for all printers whose power status is on (S302). Specifically, the program update management server 1 acquires the program identification information and the last print date and time for all printers whose power status is on from the client database 211, and sets the update recommendation timing in a distributed manner. . Specifically, the update recommendation timing is set for all printers whose power status is turned on relatively earlier as the version of the managed program is earlier, so that the higher the frequency of use, the earlier . At this time, the update recommendation timing is set so as not to exceed the number determined as the upper limit of the number of printers that make the update recommendation per fixed time in consideration of the load of the program update management server 1 and the concentration of network traffic. Further, the program update management server 1 can specify a usage pattern other than the usage frequency of the printer 2 based on the status information received from the printer 2 and set an update recommendation timing according to the specified usage pattern. For example, if the latest update program changes the function of color printing, the recommended update timing for printers that have a higher number of prints in color than in color or monochrome is set to the recommended update timing for printers that have monochrome print settings. You may set earlier than the update recommendation timing of a printer with a large number of monochrome prints. The program update management server 1 may set the update recommendation timing according to the printer 2 and the shipping destination (region, country) of the management target program. The shipping destination of the printer 2 and the management target program can be specified by the identification information of the management target program, the printer model ID, the printer serial number, and the like. In this way, the update recommendation timing can be set in consideration of various factors, but the factors that determine the update recommendation timing for individual printers include the type of installed managed program, print settings, and power status. In a broad sense, the status of each printer and usage history are included.

FIG. 5 is a sequence diagram showing a flow of transmitting an update program from the program update management server 1.
The program update management server 1 determines whether or not the update recommendation timing has arrived at regular time intervals (S400). Specifically, the program update management server 1 compares the earliest update recommendation timing registered in the client database 211 with the current time at regular intervals, and when the comparison results match, the update recommendation timing has arrived. Is determined.

  When the update recommendation timing has arrived, the program update management server 1 transmits update recommendation information to the printer at which the update recommendation timing has arrived using XMPP (S401). The update recommendation information may be any information as long as the printer that receives the update information can specify that the management target program needs to be updated. In this embodiment, the update recommendation information is updated from the program update management server 1. Assume that a URL for downloading is transmitted as update recommendation information. By transmitting the update recommendation information using XMPP, it is possible to notify the printer 2 that the print control program needs to be updated as soon as the update recommendation timing arrives. If the update recommendation timing has arrived and the printer 2 is busy, such as printing or error processing, the update recommendation timing is reset without sending update recommendation information. May be. Whether or not the printer 2 is busy can be determined based on the client database 211.

  Upon receiving the update recommendation information, the printer 2 requests the program update management server 1 for an update program for the print control program, which is a management target program, using HTTP (S402). Specifically, the printer 2 requests data transmission using HTTP for the URL received as the update recommendation information. Note that the printer 2 may request an update program immediately after receiving the update recommendation information, or may request the update program after completion of processing such as printing.

  When requested for an update program, the program update management server 1 transmits the requested update program to the requesting printer 2 using HTTP (S404). Specifically, the latest version of the compressed data of the print control program is transmitted to the printer 2.

  Upon receiving the update program, the printer 2 updates the print control program that is a management target program (S406). Specifically, for example, the installer of the printer 2 terminates the print control program and deletes it from the storage unit 21, expands the update program, and stores it in the storage unit 21. Furthermore, the installer activates the updated print control program after updating various settings for executing the updated print control program. The update program may be a difference between the latest version of the print control program and the pre-update print control program. In this case, the pre-update print control program is not deleted from the storage unit 21 and is updated. Will be changed based on. Then, the printer 2 notifies the program update management server 1 of the version information of the print control program after update or update completion together with the client ID. When the program update management server 1 receives the updated version information of the print control program or the update completion notification, the program update management server 1 updates the identification information of the management target program in association with the client ID. Specifically, the program update management server 1 updates the version of the print control program registered in the client database 211 in association with the received client ID of the printer 2 to the updated latest version.

  According to the embodiment described above, the update program is transmitted to the printer according to the update recommendation timing set according to the client information, so that the printer print control program can be automatically updated efficiently at an appropriate timing. Is possible.

4). Other Embodiments The technical scope of the present invention is not limited to the above-described embodiments, and various combinations are possible without departing from the gist of the present invention, such as by combining one or more of the following modifications. Of course, changes can be made.
For example, the program update management server 1 may be configured by a plurality of physically independent computers, or may be configured by a single computer.
The update recommendation timing may be set only when the latest update program is stored in the program update management server 1. In this case, the update recommendation timing may be set without referring to the client information. As a method for setting the update recommendation timing without referring to the client information, for example, the update recommendation timing may be set at regular time intervals.
Further, when the printer requests an update program in S403, the client ID is notified, and the program update management server 1 issues an update program request until a predetermined time elapses from the update recommendation timing based on the client ID. If not received, it may be determined that an error has occurred, and the update recommendation timing may be reset. Similarly, if the program update management server 1 has not received the updated version information of the print control program or the notification of the completion of the update until a predetermined time has elapsed from the update recommendation timing based on the client ID, an error occurs. It may be determined that the update has occurred, and the update recommendation timing may be reset.

  Further, as a communication protocol between the printer 2 and the program update management server 1, another communication protocol may be used. For example, the update recommendation information is a push communication protocol other than SMPP, such as SIP (Session Initiation Protocol) or SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions). May be transmitted using a pull-type communication protocol such as HTTP (a protocol in which processing from the server to the client is always executed in response to a request from the client). When sending update recommendation information using the pull-type communication protocol, the amount of data communication increases due to polling, but the update program transmission timing can be distributed by setting the update recommendation timing, so the program update management server The effect of suppressing load 1 and suppressing network traffic can be expected sufficiently.

In the above embodiment, an example has been described in which an update program is transmitted from the program update management server 1 after receiving a program request from a printer that has received update recommendation information, but the update program is transmitted to the printer together with the update recommendation information. You may do it. For example, the update program may be transmitted from the program update management server 1 to the printer 2 using XMPP when the update recommendation timing arrives.
In the above embodiment, the program update management server 1 transmits update recommendation information to the printer at the update recommendation timing. When the printer receives the update recommendation information, the program update management server 1 requests the update program. Set the update timing instead of the recommendation timing, send update recommendation information including the update timing to the printer in order according to the setting, and when the printer receives the update recommendation information, wait until the update timing comes, and when the update timing comes The printer may request an update program. Of course, both the update recommendation timing and the update timing may be set, and the program update management server 1 may transmit the update recommendation information including the update timing at the update recommendation timing.

DESCRIPTION OF SYMBOLS 1 ... Program update management server, 2, 3, 4 ... Client (printer), 11 ... Memory | storage part, 12 ... Control part, 13 ... Communication part, 21 ... Memory | storage part, 22 ... Control part, 23 ... Communication part, 211 ... Client database

Claims (7)

Storage means for storing an update program for updating the management target program;
Setting means for setting the update recommendation timing so that the update recommendation timing is distributed for each client in which the management target program is installed;
Update recommendation means for transmitting update recommendation information to the corresponding client at the update recommendation timing;
Program transmission means for transmitting the update program to a client that receives the update recommendation information,
The setting means specifies a difference between a version of a management target program installed in the client and a version of the update program based on client information received from the client, and determines the update recommendation timing based on the difference. Program update management server characterized by setting. Storage means for storing an update program for updating the management target program;
Setting means for setting the update timing so that the update timing is distributed for each client in which the management target program is installed;
Update recommendation means for transmitting update recommendation information including the update timing to the client;
Program transmission means for transmitting the update program to a client that receives the update recommendation information,
The setting means specifies a difference between a version of a management target program installed in the client and a version of the update program based on client information received from the client, and sets the update timing based on the difference A program update management server. The setting means specifies a use frequency of a management target program installed in the client based on status information received from the client, and sets the update recommendation timing according to the use frequency;
The program update management server according to claim 1. The setting means specifies a use frequency of a management target program installed in the client based on status information received from the client, and sets the update timing according to the use frequency;
The program update management server according to claim 2. The program transmission means transmits the update program in response to a program request received from the client.
The program update management server according to any one of claims 1 to 4. Stores the update program for updating the managed program,
The update recommendation timing is set so that the update recommendation timing is distributed for each client in which the managed program is installed,
Sending update recommendation information to the corresponding client at the update recommendation timing;
Sending the update program to the client receiving the update recommendation information;
When setting the update recommendation timing, the difference between the version of the managed program installed on the client and the version of the update program is specified based on client information received from the client, and based on the difference Program update management method to be performed. Stores the update program for updating the managed program,
Set the update timing so that the update timing is distributed to each client where the managed program is installed,
Sending update recommendation information including the update timing to the client;
When setting the update timing, the difference between the version of the managed program installed on the client and the version of the update program is specified based on the client information received from the client, and the update timing is set based on the difference. ,
A program update management method for transmitting the update program to a client that receives the update recommendation information.

Images