JP2010198630A - Program management system - Google Patents

Program management system Download PDF

Info

Publication number
JP2010198630A
JP2010198630A JP2010094707A JP2010094707A JP2010198630A JP 2010198630 A JP2010198630 A JP 2010198630A JP 2010094707 A JP2010094707 A JP 2010094707A JP 2010094707 A JP2010094707 A JP 2010094707A JP 2010198630 A JP2010198630 A JP 2010198630A
Authority
JP
Japan
Prior art keywords
program
update
data
data processing
management
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP2010094707A
Other languages
Japanese (ja)
Other versions
JP5123979B2 (en
Inventor
Yoshiro Tanaka
義朗 田中
Original Assignee
Sharp Corp
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sharp Corp, シャープ株式会社 filed Critical Sharp Corp
Priority to JP2010094707A priority Critical patent/JP5123979B2/en
Publication of JP2010198630A publication Critical patent/JP2010198630A/en
Application granted granted Critical
Publication of JP5123979B2 publication Critical patent/JP5123979B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Abstract

<P>PROBLEM TO BE SOLVED: To surely and efficiently update and manage a control program in a data processor. <P>SOLUTION: This program management system is constituted so that a plurality of data processors 2 and a program management device 1 which supplies the control program 23 of the data processor 2 are connected to a network 3. The program management device 1 transmits program updating data including setting of updating program data, updating time, an updating time limit, and holding time limit of an updating program to the data processor before the updating time. The data processor 2 stores the received program updating data in a storage device 24, executes update in timing when the data processor does not operate in an update period from the updating time to the updating time limit, and transmits information regarding a program which is used and held to the program management device 1. The program being used is renewed to one of held programs before update if necessary. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a program management system for a data processing apparatus that manages supply, update, and deletion of a control program for the data processing apparatus.

  As a data processing apparatus, for example, a digital multi-function peripheral has a plurality of functions such as a printer, a scanner, a copy, and a FAX, and firmware or software program data for controlling these functions is stored in a storage means such as a flash memory. Has been. When the function needs to be changed or the function needs to be changed, a service person or the like replaces it with a new function board or rewrites the program data.

Regarding such work, for example, Patent Document 1 discloses a data processing apparatus and the like that can efficiently add and change functions at preset timings.
Patent Document 2 discloses a network management apparatus that manages a program of each device connected to a network and updates the program as necessary.
Further, Patent Document 3 discloses a printer management system or the like that enables a plurality of firmware to be automatically updated together when updating printer firmware.

Japanese Patent Laid-Open No. 9-167094 JP 2001-243155 A JP 2004-110396 A

However, in the related art as described above, since it is time to update the program, the program is acquired from the outside. For example, when the update program is acquired from the management server via the network, the status of the management server Depending on the network status, it may not be available in a timely manner.
For example, if the data processing apparatus is processing a large amount of data or the power is not turned on, the program may not be acquired and updated in a timely manner.
Further, since there is no mechanism for holding the old version of the program, if the control program is updated to the latest version, it is necessary to acquire the previous program again when returning to the previous program.

  In view of such a current situation, the present invention provides a program management system for a data processing apparatus that can reliably and efficiently update and manage a control program in the data processing apparatus.

  In order to solve the above problems, the present invention comprises the following technical means.

  According to a first technical means, a plurality of data processing devices and a program management device for supplying a control program to the data processing devices are connected to a network, and the program management device is connected to the data processing device at least with update program data The program update data including the update date and time, the update date, and the retention date setting of the update program are transmitted before the update date and time, and a program deletion request stored in the data processing device is transmitted. A control program management unit that acquires and stores information about a control program used and held in each data processing device transmitted from the data processing device; and the data processing device updates the program from the program management device When data is transmitted, the data is stored in a storage device, and the data The control program is updated at a predetermined timing when the data processing apparatus is not operating within the update period from the new date and time to the update date, and the control program before the update is held, and the control program is used and held When the information is stored, the information is transmitted to the program management device, can be renewed to any of the pre-update programs holding the program used as necessary, and the program deletion request is received A control program that deletes a program requested to be deleted when the retention period has passed, and deletes the retained control program based on the retention period when the capacity of the storage device is insufficient A program management system including an updating unit is characterized.

  According to a second technical means, in the first technical means, the program update data transmitted from the program management device to the data processing device includes designation of a data processing device as a transfer destination to which the program update data is transferred, The control program update unit of the apparatus includes an update data transfer processing unit that transfers the received program update data to a designated transfer destination.

According to the present invention, when the time for updating the program is reached by the data processing apparatus acquiring and holding the program data for update in advance, not when the program is updated, the program is surely executed. It becomes possible to update.
Therefore, as before, when trying to acquire a program after it is time to update the program, the status of the network or management server, or the data processing device is acquiring the program update data correctly because the print job is being executed. The problem of not being eliminated.

Further, according to the present invention, by setting an update condition for a time zone other than nighttime for the update timing of the program, the data processing device can be kept turned on even after the work end time as in the past. It is possible to reduce wasteful power consumption as compared with a method in which the update process is performed all at once at the night.
Even if the updatable period is the daytime period, the update process is executed at predetermined intervals for each data processing apparatus, so that all data processing apparatuses cannot be used for program update. There is no.

  Further, according to the present invention, the program before update is stored in a storage device such as a hard disk, so that even if a failure occurs in the latest program, the program can be executed without supplying the program from the host device again. You can revert to the original version.

  Even if it is necessary to change the printer control program to the previous version due to the usage status of the printer driver in the personal computer, it is easy even if the version program is not sent as program update data from the host device. Version down can be done.

  In addition, according to the present invention, since the program update data sent from the program management device to the data processing device can be transferred to another data processing device, a large number of data processing devices are connected to a network such as an intranet. Data traffic can be reduced in an environment or in an environment where a host device and a data processing device are connected to a long-distance network (Internet connection).

  Further, according to the present invention, even when the storage area is small when acquiring the program update data, the program update data is surely deleted because the end date is deleted from the program based on the storage expiration information. Can be imported.

It is a schematic structure figure showing the whole program management system in an embodiment of the present invention. FIG. 2 is a module configuration diagram of a printer control program update unit in FIG. 1. FIG. 2 is a module configuration diagram of a printer control program management unit in FIG. 1. FIG. 10 is a diagram illustrating a display example of a screen when a printer and each job are selected in the program management apparatus. It is a figure which shows the example of a display of the "add program" screen in a program management apparatus. It is a figure which shows the example of a display of the "deletion of program" screen in a program management apparatus. It is a figure which shows the example of a display of the "program update" screen in a program management apparatus. It is a figure which shows the data structural example of program update data. It is a figure which shows the flowchart of the main process in a printer control program update part. It is a figure which shows the flowchart of the received data analysis process in FIG. It is a figure which shows the flowchart of the acquisition process of the program update data of FIG. It is a figure which shows the flowchart of the starting screen process in a program management apparatus. It is a figure which shows the flowchart of the "add program" screen process in a program management apparatus. It is a figure which shows the flowchart of the "program update" screen process in a program management apparatus.

Hereinafter, an embodiment of the present invention will be described using a printer as an example of a data processing apparatus.
FIG. 1 is a schematic configuration diagram showing an entire program management system in which a program management device 1 and a printer 2 having a data transmission / reception function and a storage device as a data processing device are connected to a network 3. The transmission / reception unit 11 and a program management unit 12 that manages the control program of the printer 2 are provided. The printer 2 includes a data transmission / reception unit 21, a printer control program update unit 22, a printer control unit 23, and a storage device 24.

  FIG. 2 shows the module configuration of the printer control program management unit 12 of the printer management apparatus 1. The program update data generation unit 12-1, the update data management unit 12-2 of the printer control program 23, and the program update data distribution process Section 12-3 and printer control program storage section 12-4.

  FIG. 3 shows the module configuration of the printer control program update unit 22 of the printer 2. The program update data acquisition unit 22-1, the update data management unit 22-2 of the printer control program 23, and the printer control program holding unit 22- 3, a program update data transfer processing unit 22-4, a program update processing unit 22-5, and a program deletion processing unit 22-6.

Next, the program management apparatus 1 in the present embodiment will be described based on screen display examples in each process.
FIG. 4 shows a display example of a screen when the control program of the printer 2 connected to the network is added, deleted, and updated in the program management apparatus 1. The screen displays a list of printer names, current version information, printer location, and IP address as the output destination for the printers connected to the network. Jobs for "Add", "Delete", and "Update" are displayed. Displayed with a button to select.

On this display screen, the cursor (not shown) is put on the printer to be processed and a check is made, and the “add”, “delete” or “update” button is clicked to switch to the processing screen for the selected job. Here, the job contents of “addition”, “deletion”, and “update” on the program management apparatus side will be described. “Addition” means that the entire control program of the current version is replaced with a new version of the program and updated. This is a process to send the latest version program file for so-called major version upgrade to the corresponding printer. “Delete” is no longer necessary for the old version of the program stored in the printer storage device. Is updated to supply a printer with an update data file for so-called minor version upgrade, which partially changes or modifies the current control program. It is a process and includes a process related to a change in update conditions.
Since the control program is updated for each same model number, when the number of printers is large, it is more efficient to select the printer by the model number of the printer.

  FIG. 5 shows a screen in the case of performing an “add” job, which is displayed by selecting one printer on the screen of FIG. 4 and clicking the “add” button. In this screen, the administrator inputs the control program of the selected printer to a new version for each file, for example, a program file name for updating, a retention period, an update date, an update date, and a transfer destination of the program. The latest version of the program file for update is already stored in the storage device of the program management device provided by the manufacturer on the website or other methods. It may be automatically input using it. In addition, the contents currently set by default may be automatically input as a transfer destination of a program to be described later.

  In this embodiment, as information about the selected printer in the upper left part a of the screen shown in FIG. 5A, the printer name and installation location, the version information (* mark) of the current program, its update deadline, update date and time, The version information and update history information of the control program stored in the storage device 24 of the printer are displayed as shown in FIG. This allows the administrator to input parameters such as update conditions while referring to the printer information.

  Note that the same can be said for the “delete” and “update” processes described below. However, when there are a large number of printers to be managed on the network, the printer selection on the screen of FIG. After selecting all printers of the same model number by specifying and clicking “Add”, all the parameters such as the program file, update timing conditions (update date and time, update date), retention date, etc. are automatically entered. You may do it.

The update timing is set on the same floor, for example, so that when all the same time is set, update processing is started at that time, and no printers can be used during that time. It is also possible to set the update timing for a plurality of printers at a predetermined interval. The same applies to the update timing at the program transfer destination. That is, it is set so that at least the printers on the same floor, including the selected printer and the transfer destination printer, are not simultaneously updated at the same timing.
As a condition for determining the update timing, it is also possible to set a predetermined day of the week and time, or a combination of a predetermined day of the week and an operating state of the apparatus (for example, immediately before shifting to the sleep mode).

  FIG. 6 shows an example of a display screen for deleting from the storage device 24 a program that no longer needs to be saved among the versions of the program held by the printer. This is displayed by selecting the printer to be selected and clicking the “Delete” button. On this screen, if the version to be deleted is checked and “OK” is selected, a deletion command is transmitted to the corresponding printer. Note that version 2.00 is not checked so that the current version is not selected by mistake.

FIG. 7 shows an example of a display screen when rewriting a part of the program, that is, a so-called minor version upgrade or update condition change. In the screen of FIG. It is displayed by clicking the "" button. Also in this case, the update data is already stored in the program management apparatus, and the update data file name is automatically input to the program file name input area by specifying the printer. In the update condition input area, the update conditions set in the current version of the program are displayed on the left side. Enter the program retention period, update date / time, update date, and transfer destination into the corresponding fields in the change field on the right side, and click the “OK” button. The program update data specified by the program file name and the right side Information relating to the update entered in is sent to the corresponding printer.
Note that the history information of FIG. 5B may be displayed in the upper left part b of the screen, as in the case of “add”.
FIG. 8 shows the contents of the program update data sent to the printer apparatus.

Next, a processing flow in the printer control program update unit 22 of the printer 2 will be described based on a flowchart.
FIG. 9 shows a flowchart of the main process of the printer control program update unit.
In the following description, program update data including update program data, update timing determination conditions (update date and time, update date), and update related information such as a storage time limit has already been sent from the program management apparatus 1 to the printer apparatus. It is assumed that The “update” in the printer control program update unit (hereinafter referred to as “program update unit”) is a major version upgrade by the new version program file by “addition” explained in the program management apparatus and the current update. Includes both minor version upgrades that make partial changes and modifications to the control program.

If any event occurs in step S1, it is determined in step S2 whether or not it is data reception. If data reception, the process proceeds to step S3, a received data analysis process described later is executed, and the event is waited again. If the generated event is not data reception, the process proceeds to step S4, and if it is a program update request due to the arrival of the program update timing, the process proceeds to step S5. If the generated event is due to the expiration of the program retention period, the process proceeds from step S6 to step S7, the corresponding program is deleted, and the process returns to step S1.
In step S5, even if it is a program update request, if the update due date has passed, the program returns to step S1 without executing the program update process.
If the program update request is before the update due date, a program update process is executed in step S9, program update completion information is transmitted to the program management apparatus 1 in step S10, and the process returns to step S1.
In step S1, if the event is a program end request, the process proceeds to step S9 and ends.
As for the automatic program deletion, other than the retention period, for example, an upper limit of the number of retained programs may be set, and the oldest program may be deleted when exceeded.

Although not shown in the flowchart of FIG. 9, for example, if program update timing has arrived and a program update request event has occurred, but no program update data has been sent from the host device, step S10 is performed. You may make it pass and return to step S1.
In addition, if the program update does not complete normally, the program will return to the original version with an interrupt, and the host device will be notified that the update did not complete normally. It may be. Alternatively, the status signal may be output to a main control unit that controls the entire apparatus (multifunction machine), and the information may be notified from the main control unit to the program management unit.

FIG. 10 shows a flowchart of the received data analysis process in step S3 of FIG. In step S11, the type of the job is acquired. If the job is a print job, the process proceeds to step S19, where the normal printer printing control process is executed and the process ends.
If the job is program update data in step S11, the process proceeds from step S13 to step S14, and the program update data acquisition process described below is executed and the process ends.
If the job is a program deletion request, the process proceeds from step S15 to step S16, where a program retention time limit event is issued and the process ends.
If the job is a transmission request for program storage information from the program management apparatus 1, the process proceeds from step S17 to step S18, the program storage information list is transmitted to the program management apparatus 1 and the process ends.

FIG. 11 shows a flowchart of the program update data acquisition process described above. If the program update data is acquired in step S21, the process proceeds to step S22, and if it has not been received, the process proceeds to step S23. Based on the data size information of the program, a program storage area for storing the program in the storage device is obtained. It is determined whether there is a shortage. If there is a shortage, the program having the closest retention period is deleted in step S24.
If the received program update data has already been acquired, the program discarding process is executed in step S25, and the process proceeds to step S27.
If the storage area for the update program is secured in step S23, the process proceeds to step S26, and the acquired program is temporarily stored in the storage device.

In step S27, if there is a change in the program update date / time in the update related information included in the program update data sent this time, the timer is set at the program update date / time specified in step S28, and step S29 If there is a change in the program retention period, the timer is set to the program retention period specified in step S30.
Furthermore, if the program transfer destination is specified in the update related information in step S31, the program transfer process is executed in step S32, and the program update data acquisition process is terminated.

FIG. 12 shows a flowchart of screen processing for printer selection and job selection in the printer control program management unit 12 shown in FIG.
In step S41, the printer connected to the network is searched. In step S42, the printer information list of the searched printer is displayed. In step S43, the “add”, “delete”, and “update” buttons are not selected. Display and wait for an event in step S44.
Here, if the “close” button is selected without selecting a printer, the process ends from step S45.

When a printer is selected while waiting for an event in step S44, the process proceeds from step S46 to step S47, the selected printer is highlighted, and the buttons "ADD", "DELETE", and "UPDATE" are selected and displayed. In S48, the event is waited.
When the “add” button is selected on the screen of FIG. 4, the process proceeds from step S49 to step S50, the program addition process screen of FIG. 5 is displayed, and the program addition process can be executed. When the program addition process is completed, the process returns to step S42 and the screen shown in FIG. 4 is displayed again. In step S43, the “add”, “delete”, and “update” buttons are deselected and the event waits again in step S44. It becomes.

  When the “delete” button is selected on the screen of FIG. 4, the process proceeds from step S46 to step S51, the screen for program deletion processing of FIG. 6 is displayed, and the program deletion processing can be executed. When the “update” button is selected on the screen, the process proceeds from step S46 to step S52, the program update process screen of FIG. 7 is displayed, and the program update process can be executed. After the process is completed, as in the case of “add”, the process returns to step S42 and the screen of FIG. 4 is displayed. In step S43, the “add”, “delete”, and “update” buttons are deselected and displayed. In step S44, the event waits again.

  When re-selecting the printer, by clicking the “return” button in step S49, the process returns to step S44 to wait for a printer selection event. In this case, although not shown in the flowchart, the highlighted display of the printer is returned to the normal display, and each job button is also non-selected.

FIG. 13 is a flowchart showing the screen processing of “program addition processing” in step S50 in the flowchart of FIG.
When the screen of FIG. 5 is displayed in step S61 and the program file name for update or each parameter in the update related information described above is input in step S62, the process waits for an event in step S63. Here, when the “Cancel” button is clicked, the process ends from step S64. When the necessary parameters are input and the “OK” button is clicked, the process proceeds from step S65 to step S66. If the input parameters are appropriate, the process proceeds to step S67, and the program including the added new version program file and update related information. The update data is transmitted to the corresponding printer, and the program addition process is terminated.
If the parameter input in step S62 is inappropriate, the process proceeds from step S66 to step S68, an error message is displayed, and the process returns to step S62.

FIG. 14 is a flowchart showing the screen processing of “program update processing” in step S52 in the flowchart of FIG.
In step S71, parameters such as the program file name of the current version and update conditions are acquired, the screen of FIG. 7 described above is displayed in step S72, and when the update condition parameters are input in step S73, the process waits for an event in step S74. It becomes. Here, when the “cancel” button is clicked, the process is ended from step S75. When the necessary parameters are input and the “OK” button is clicked, the process proceeds from step S76 to step S77. If the input parameters are appropriate, the process proceeds to step S78, and the program update data or the update data of only the changed update condition is applied. Then, the program update process is terminated.
If the input parameter is inappropriate, the process proceeds from step S77 to step S79, an error message is displayed, and the process returns to step S73 to wait for re-input of the parameter.

  In this update process, it is possible not only to upgrade with new update data, but also to downgrade the printer control program back to the previous version stored in the storage device. That is, a plurality of control programs stored in the storage device of the printer are managed by the program management device in association with the update information. For example, the version of the printer driver incorporated in each personal computer It is also possible to deal with the case where it is necessary to revert to the previous version due to usage conditions.

  Regarding the update timing of the control program in the data processing device, the above-mentioned “date and time” is merely an example, and the operating status of the data processing device may be used in addition to the date and time. From the viewpoint of energy, the printer is often set to enter the sleep mode if no print data is received from the personal computer for a certain period of time. Therefore, the state immediately before entering the sleep mode is used as the update timing condition. Anyway. In the case of the above-described embodiment in which the example of “date and time” is shown as the update timing, step S27 and step S28 in the flowchart of FIG. 11 correspond to the update timing determination unit.

  Also, using the version management information of the printer driver of the personal computer that is used in the program management apparatus, an update command is issued from the program management apparatus when the printer driver reaches a predetermined version for all personal computers. It may be. Unless both the printer program and the printer driver of the personal computer are updated, the program update method is effective in the case where a new function does not operate.

The present invention can further take the following embodiments.
That is, the program management apparatus can be provided with a function of separately transmitting an update command to a data processing apparatus that does not transmit an update completion notification even when the update due date has passed.
Also, a function for transmitting a command for returning the control program to the program before update stored in the storage device of the data processing apparatus to the program management apparatus to the data processing apparatus in which a failure has occurred in the control program after update You may make it have.
In this case, the printer side is provided with a function for transmitting a failure to the control program after the update to the program management apparatus and a function for returning to the control program before the update by a command from the program management apparatus.
As described above with reference to FIG. 9, in recent digital multi-function peripherals, for example, even when the update of the control program in the printer section does not end normally, the main control unit that controls the entire apparatus causes It is possible to notify the information.

DESCRIPTION OF SYMBOLS 1 ... Program management apparatus, 2 ... Data processing apparatus, 3 ... Network, 11, 21 ... Data transmission / reception part, 12 ... Printer control program management part, 21 ... Data transmission / reception part, 22 ... Printer control program update part, 23 ... Printer control Program, 24 ... storage device.

Claims (2)

  1. A plurality of data processing devices and a program management device that supplies a control program to the data processing devices are connected to a network,
    The program management device transmits, to the data processing device, program update data including at least update program data, update date and time, update date, and retention date setting of the update program before the update date and time, and Send a request to delete the program held in the data processing device;
    A control program management unit for acquiring and storing information about a control program used and held in each data processing device transmitted from the data processing device;
    When the program update data is transmitted from the program management device, the data processing device stores the data in a storage device, and the data processing device is operating within an update period from the update date to the update date. Update the control program at a predetermined timing,
    Holds the control program before update, stores information about the used and held control program, sends the information to the program management device,
    If necessary, it can be renewed to one of the pre-update programs that holds the program being used,
    When receiving a deletion request for the program, delete the program when the deletion requested program has passed the retention period,
    A program management system comprising: a control program update unit that deletes a retained control program based on a retention period when the storage device has insufficient capacity.
  2. The program update data transmitted by the program management device to the data processing device includes designation of a data processing device as a transfer destination to which the program update data is transferred,
    2. The program management system according to claim 1, wherein the control program update unit of the data processing apparatus includes an update data transfer processing unit that transfers the received program update data to a designated transfer destination.
JP2010094707A 2010-04-16 2010-04-16 Program management system Active JP5123979B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2010094707A JP5123979B2 (en) 2010-04-16 2010-04-16 Program management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2010094707A JP5123979B2 (en) 2010-04-16 2010-04-16 Program management system

Related Child Applications (1)

Application Number Title Priority Date Filing Date
JP2006219289 Division 2006-08-11

Publications (2)

Publication Number Publication Date
JP2010198630A true JP2010198630A (en) 2010-09-09
JP5123979B2 JP5123979B2 (en) 2013-01-23

Family

ID=42823227

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2010094707A Active JP5123979B2 (en) 2010-04-16 2010-04-16 Program management system

Country Status (1)

Country Link
JP (1) JP5123979B2 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012103935A (en) * 2010-11-11 2012-05-31 Brother Ind Ltd Terminal device and program
JP2012213991A (en) * 2011-04-01 2012-11-08 Konica Minolta Business Technologies Inc Image forming system
JP2014527677A (en) * 2011-08-29 2014-10-16 富士通株式会社 System and method for installing patches on a computer system
WO2015068518A1 (en) * 2013-11-05 2015-05-14 株式会社リコー Communication device, communication system, communication method, and communication program
WO2015068460A1 (en) * 2013-11-05 2015-05-14 株式会社リコー Communication device, communication system, communication method and communication program
JP2017013396A (en) * 2015-07-02 2017-01-19 セイコーエプソン株式会社 Printer and control method of the same
JP2017016453A (en) * 2015-07-02 2017-01-19 セイコーエプソン株式会社 Printer, program update system, and control method for printer
US10127031B2 (en) 2013-11-26 2018-11-13 Ricoh Company, Ltd. Method for updating a program on a communication apparatus

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH09167094A (en) * 1995-10-11 1997-06-24 Canon Inc Data processor, its control method storage medium and compound image processor
JPH1083285A (en) * 1996-06-24 1998-03-31 Fujitsu Ltd Electronic computer system and remote maintenance system
JP2000172509A (en) * 1998-09-30 2000-06-23 Matsushita Electric Ind Co Ltd Program collaborative execution device
JP2001243155A (en) * 2000-02-25 2001-09-07 Canon Inc Network control unit, information processing unit, control method and recording medium
JP2002007255A (en) * 2000-06-27 2002-01-11 Nec Corp Method for managing distribution destination of downloading
JP2002055856A (en) * 2000-05-31 2002-02-20 Matsushita Electric Ind Co Ltd Receiving terminal to receive and store broadcasted contents and to make contents as usable state according to request of user
JP2002204327A (en) * 2000-12-28 2002-07-19 Ricoh Co Ltd Compound machine system and compound machine used for the system
JP2002278767A (en) * 2001-03-16 2002-09-27 Kenwood Corp Network communication system, server device, portable terminal, communicating method and program
JP2004110396A (en) * 2002-09-18 2004-04-08 Ricoh Co Ltd Printer monitor system, printer monitoring method, printer monitoring program, and recording medium
JP2004206260A (en) * 2002-12-24 2004-07-22 Aioi Insurance Co Ltd Program delivery system
JP2005037987A (en) * 2003-07-15 2005-02-10 Shinko Electric Ind Co Ltd Software distribution system, distribution server, receiving client, and software distribution method

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH09167094A (en) * 1995-10-11 1997-06-24 Canon Inc Data processor, its control method storage medium and compound image processor
JPH1083285A (en) * 1996-06-24 1998-03-31 Fujitsu Ltd Electronic computer system and remote maintenance system
JP2000172509A (en) * 1998-09-30 2000-06-23 Matsushita Electric Ind Co Ltd Program collaborative execution device
JP2001243155A (en) * 2000-02-25 2001-09-07 Canon Inc Network control unit, information processing unit, control method and recording medium
JP2002055856A (en) * 2000-05-31 2002-02-20 Matsushita Electric Ind Co Ltd Receiving terminal to receive and store broadcasted contents and to make contents as usable state according to request of user
JP2002007255A (en) * 2000-06-27 2002-01-11 Nec Corp Method for managing distribution destination of downloading
JP2002204327A (en) * 2000-12-28 2002-07-19 Ricoh Co Ltd Compound machine system and compound machine used for the system
JP2002278767A (en) * 2001-03-16 2002-09-27 Kenwood Corp Network communication system, server device, portable terminal, communicating method and program
JP2004110396A (en) * 2002-09-18 2004-04-08 Ricoh Co Ltd Printer monitor system, printer monitoring method, printer monitoring program, and recording medium
JP2004206260A (en) * 2002-12-24 2004-07-22 Aioi Insurance Co Ltd Program delivery system
JP2005037987A (en) * 2003-07-15 2005-02-10 Shinko Electric Ind Co Ltd Software distribution system, distribution server, receiving client, and software distribution method

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012103935A (en) * 2010-11-11 2012-05-31 Brother Ind Ltd Terminal device and program
JP2012213991A (en) * 2011-04-01 2012-11-08 Konica Minolta Business Technologies Inc Image forming system
JP2014527677A (en) * 2011-08-29 2014-10-16 富士通株式会社 System and method for installing patches on a computer system
WO2015068518A1 (en) * 2013-11-05 2015-05-14 株式会社リコー Communication device, communication system, communication method, and communication program
WO2015068460A1 (en) * 2013-11-05 2015-05-14 株式会社リコー Communication device, communication system, communication method and communication program
JPWO2015068460A1 (en) * 2013-11-05 2017-03-09 株式会社リコー Communication device, communication system, communication method, and communication program
JPWO2015068518A1 (en) * 2013-11-05 2017-03-09 株式会社リコー Communication device, communication system, communication method, and communication program
US10067756B2 (en) 2013-11-05 2018-09-04 Ricoh Company, Ltd. Communication apparatus, communication system, and communication method
US10127031B2 (en) 2013-11-26 2018-11-13 Ricoh Company, Ltd. Method for updating a program on a communication apparatus
JP2017013396A (en) * 2015-07-02 2017-01-19 セイコーエプソン株式会社 Printer and control method of the same
JP2017016453A (en) * 2015-07-02 2017-01-19 セイコーエプソン株式会社 Printer, program update system, and control method for printer

Also Published As

Publication number Publication date
JP5123979B2 (en) 2013-01-23

Similar Documents

Publication Publication Date Title
CN101604230B (en) Printing device, printing system
JP3770268B2 (en) Information processing system, information processing method and information processing program used therefor
JP4849968B2 (en) Program update management device
US7380243B2 (en) Image forming apparatus of which programs are remotely updatable
JP5038163B2 (en) Distribution apparatus, system, information processing method, and program
US8755068B2 (en) Image processing device with executable hardware key and server
JP5691605B2 (en) Image processing apparatus, screen control method, screen control program, and recording medium
DE19832768B4 (en) Combination engine, server, combination machine server system and program recording medium
KR101245392B1 (en) Printing control apparatus and printing control method
US8805961B2 (en) Reading device and communication system
JP5527146B2 (en) Terminal device and program
JP5665437B2 (en) Network device management system, network device management device, client device and method thereof
JP3682777B2 (en) Image forming apparatus and remote management system
JP5240141B2 (en) Program download system, program download method, image forming apparatus, program distribution server, and download program
JP4344203B2 (en) Image forming apparatus and information display method
JP4415810B2 (en) Image processing apparatus, control method thereof, and control program
US8286167B2 (en) Image processing apparatus, job management method, and storage medium
JP4403135B2 (en) Web service utilization system
JP2008071085A (en) Image processor and log transfer method
EP2141584B1 (en) Job processing apparatus, method for managing job log in the job processing apparatus
JP5864467B2 (en) Information processing apparatus, firmware update method, and computer program
JP5870714B2 (en) Image processing system, information processing apparatus, screen display method, and program
US20050028173A1 (en) Information processing apparatus, information processing method, and control program
JPH11105381A (en) Printing system and printer
JP4449445B2 (en) Image forming apparatus

Legal Events

Date Code Title Description
A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20120726

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20120731

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20120912

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20121002

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20121026

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20151102

Year of fee payment: 3

R150 Certificate of patent or registration of utility model

Ref document number: 5123979

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150

Free format text: JAPANESE INTERMEDIATE CODE: R150