IP Library Granted Patent US 8,667,114
Granted Patent B2
US 8,667,114 · App. 13/372,865 · Granted Mar 4, 2014

Program update management server and program update management method

Inventor: Shoichi Nakajo (Nagano-ken, JP)
Assignee: Seiko Epson Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,667,114
App. No.
13/372,865
Granted
Mar 4, 2014
Kind
B2
Abstract

A program update management server includes a storage unit configured to store an update program for updating a program to be managed, a setting unit configured to set an update timing in accordance with each client in which the program to be managed is installed, an update recommending unit configured to transmit information regarding recommendation of an update so that the client acquires the update program at the update timing, and a program transmitting unit configured to transmit the update program, at the update timing, to the client that receives the information regarding recommendation of an update.

Claims (32)

1. A program update management server comprising:

a storage unit configured to store an update program for updating a program to be managed;

a setting unit configured to automatically set an update timing individually for each client of a plurality of clients in which the program to be managed is installed;

an update recommending unit configured to transmit information regarding recommendation of an update so that the client acquires the update program at the update timing; and

a program transmitting unit configured to transmit the update program, at the update timing, to the client that receives the information regarding recommendation of an update;

wherein the program update management server receives operational data from each client of said plurality of clients and sets the update timing individually for each client based on each client's respective operational data such that the update timings are dispersed;

wherein the setting of update times by the program update management server is further determined from the type of operations more prevalent in the clients as determined from their provided operational data; and

wherein the clients are printers, and if the type of operations more prevalent in a first client are color printing operations as compared to monochrome printing operations and the update program provides a functional change to color printing operations, then the update timing for the first client is set earlier than the update timing of a second client whose color printing operations are not more prevalent than monochrome printing operations.

2. The program update management server according to claim 1 , further comprising:

a reception unit configured to receive, from the client, client information capable of identifying a status of the client, the program to be managed being installed in the client, and

wherein the setting unit sets the update timing in accordance with the status.

3. The program update management server according to claim 2 , further comprising a reception unit configured to receive from the client, client information capable of identifying a version of the program to be managed, wherein the setting unit further sets the update timing in accordance with the version of the program to be managed.

4. The program update management server according to claim 1 ,

further comprising a reception unit configured to receive, from the client, said operational data, wherein said operational data determines a frequency of use of the program to be managed, the program to be managed being installed in the client,

wherein the setting unit sets the update timing in accordance with at least the frequency of use.

5. The program update management server according to claim 4 , wherein

the frequency of use is determined based on the date and time of the last printing.

6. The program update management server according to claim 4 , wherein

the frequency of use is determined based on a time interval between starts of printing.

7. The program update management server according to claim 4 , wherein

the frequency of use is determined based on a time interval between completions of printing.

8. The program update management server according to claim 4 , wherein

the frequency of use is determined based on a cumulative number of printed sheets per period of time.

9. The program update management server according to claim 4 , wherein

the frequency of use is determined from the number of turn-on operations of the client per period of time.

10. The program update management server according to claim 1 , wherein the program transmitting unit transmits the update program in response to a program request received from the client that received the information regarding recommendation of an update.

11. The program update management server according to claim 1 , wherein the timings at which an update is to be recommended are dispersed among the client.

12. The program update management server according to claim 1 , wherein

the update recommending unit transmits the information regarding recommendation of an update, using a first communication protocol;

the program transmitting unit transmits the update program, using a second communication protocol.

13. The program update management server according to claim 1 , wherein the setting of update times by the program update management server is fully automatic without any human intervention.

14. The program update management server according to claim 1 , wherein each client's update timing is automatically reset anew each time the client device is turned on.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 14, 2012
From: NAKAJO, SHOICHI
To: SEIKO EPSON CORPORATION
Reel/Frame 027702/0001 →
Priority Claims (2)
JP 2011-029496 · Feb 15, 2011 · national
JP 2011-029497 · Feb 15, 2011 · national
Continuity (1)
Related Publication 20120209977A1 · Aug 16, 2012