JP2015060276A - Program, information processing device, and information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To maintain user-friendliness while suppressing the increase of search processing load and data capacity.SOLUTION: Machine-dependent data 141 and 151 for control of each of machine types of printers are registered with a machine-dependent data registration unit 140 and a handover machine-dependent data registration unit 150, and a use continuation condition 161 being the condition under which machine-dependent data to be left after update of a printer driver 120 which provides a function of controlling a printer by using the machine-dependent data 141 and 151 should be selected is registered with a use continuation condition registration unit 160. When the printer driver 120 is updated, a use state determination unit 123 determines data to be left and data to be deleted out of the machine-dependent data 141 and 151 on the basis of the use continuation condition 161, and a machine type information management unit 124 deletes machine-dependent data of which the deletion is determined.

Description

  The present invention relates to a program, an information processing apparatus, and an information processing system.

In recent years, printer drivers that are compatible with a plurality of models have been used in information processing apparatuses such as PCs (personal computers).
The common printer driver displays a print setting screen corresponding to the printer model of the output destination and accepts settings used for printing from the user. Further, it is possible to execute rendering processing according to the model and generate data for causing the printer of the model to execute printing.

  Therefore, if one user installs a common model driver, the user does not need to install a printer driver for each model even when using a plurality of printer models. For this reason, common printer drivers are often used not only in a stand-alone environment, but also in a server client environment of a large company having a plurality of printers.

  A new version of such a model-common printer driver is usually released when a new model is released from a vendor. A user who wants to use a new model updates the model common printer driver to the new version. In addition, when a new version includes failure handling and new functions, the new model may be updated even if the user does not use it.

On the other hand, the common printer driver has model-dependent files that are used to provide functions for controlling the model by the number of models that the driver supports. Therefore, each time a new model is released, the number of model-dependent files increases by the amount of the new model.
This model-dependent file is distributed in the form of a common printer driver, and is stored in the PC when the common printer driver is installed in the PC. Therefore, as new models are released, the number of model-dependent files that should be stored in the PC also increases.

  If the number of model-dependent files increases in this way, the process of searching for the necessary model-dependent file from among them becomes heavy. In addition, since the total capacity of the model-dependent files increases, there is a problem that processing such as printer driver update and point-and-print installation takes time as the version increases. Further, the increase in the package size of the printer driver is a serious problem for users who use machines with a small capacity.

  To solve these problems, vendors are shifting to discontinue the inclusion of model-dependent files for older models every time a new version is released. However, if this happens, the user may be unable to use the old model by updating to the new model common printer driver with fewer included models.

  For example, consider a case where a version 1.0 driver supports three models, model A, model B, and model C. In this case, in the next version 2.0, the corresponding models may be model B, model C, and model D. That is, in version 2.0, a model-dependent file for model D is newly included, while a model-dependent file for old model A is included.

In such an update, even if the user wants to continue using Model A that is not included in the package, since there is no model dependent file, the model common printer driver displays a UI suitable for the function of Model A. The rendering process cannot be performed.
However, even if there is such a problem, a user who wants to use the new model D is forced to update the model common printer driver to the new version. In addition, there are times when it is updated for reasons such as wanting to solve a bug discovered in the previous version.

In order to cope with such a problem, a technique has been proposed that allows a model that has not been included in an update to be used to some extent.
For example, for models that do not have model-dependent data, it is conceivable to provide a predetermined basic print setting screen and rendering process that do not specify a compatible model. In this way, it is possible to use a printer of any model using the common model printer driver.

However, a print setting screen that does not specify a compatible model can accept only settings related to a very basic print function that almost all models have. Therefore, on this screen, functions specific to the model (such as high resolution and special paper) cannot be set, and the functions that have been used so far cannot be used from the user's perspective. Also, the appearance of the print setting screen is different from that when there is model-dependent data.
When using a function that automatically updates the driver, such as point-and-print, there is such a change without the user's knowledge, and it is considered that confusion is particularly great.

  As another method, it is also conceivable to leave the model-dependent data held by the old version of the driver, extract information as necessary, and provide the same print setting screen and rendering processing as the old version. In Patent Document 1, as a related technology, even after a new version of a printer driver is installed, an old version of the printer driver is left, and an appropriate version of the module is called according to the printer used for printing. It is described that processing is performed.

In this way, even after the version upgrade, it is guaranteed that the models that can be used before the version upgrade can still be used. Therefore, the problem like the method of providing the above basic print setting screen does not occur. However, since the data held by the old version of the driver is retained indefinitely, the problem of increase in search processing load and data capacity cannot be solved.
A similar problem is that even when a function other than printer control is provided, function correspondence information including information for realizing the function is prepared for each of the plurality of functions, and the function correspondence information is referred to. In the case of adopting a configuration that provides a function, the same occurs.

  The present invention has been made in view of such circumstances, and prepares function correspondence information including information for realizing the function for each of a plurality of functions, and functions by referring to the function correspondence information. Even if the updated program does not include some of the function support information included in the previous version, the increase in search processing load and data capacity is suppressed. An object of the present invention is to maintain user convenience.

  In order to achieve the above object, the present invention uses a first registration means for registering function correspondence information including information for realizing the function for each of a plurality of functions, and the function correspondence information. The condition registration means for registering the continuation condition, which is a condition for selecting function correspondence information to be retained even after updating the predetermined program that provides the function, and the continuation condition when the predetermined program is updated. Based on the function correspondence information registered by the first registration means, a discrimination means for discriminating what is left and deleted, and a deletion means for deleting the function correspondence information determined to be deleted by the discrimination means A program is provided.

  According to the above configuration, when the function correspondence information including information for realizing the function is prepared for each of a plurality of functions and the function is provided by referring to the function correspondence information, the update is performed. Even if a later program does not include some of the function support information that was included in the previous version, the convenience of the user can be maintained while suppressing an increase in search processing load and data capacity. be able to.

It is a figure which shows the relationship between PC and printer in embodiment of this invention. It is a figure which shows the hardware constitutions of PC shown in FIG. It is a figure which shows the function structure of PC shown in FIG. FIG. 3 is a diagram for describing printer registration in the PC illustrated in FIG. 1. It is a figure which shows the example of model dependence data. It is a figure which shows the example of a use continuation condition setting screen. It is a figure which shows the example of use continuation conditions. It is a figure which shows the operation | movement relevant to maintenance and deletion of model dependence data which PC shown in FIG. 1 performs. 3 is a flowchart of processing when the printer is used. It is a figure which shows the example of usage history. 2 is a flowchart of processing when a new printer driver is installed, which is executed by the PC shown in FIG. 1. FIG. 12 is a flowchart continued from FIG. 11. 13 is a flowchart continued from FIG. 12. It is a figure which shows the specific example of management of model dependence data.

Hereinafter, embodiments for carrying out the present invention will be specifically described.
Although the present invention will be described with reference to an embodiment in which the present invention is applied to a personal computer (PC) that is an information processing apparatus and a printer driver program for causing the PC to control a printer, the present invention is not limited thereto. This is as described later.

FIG. 1 shows the relationship between a PC and a printer in this embodiment.
In this embodiment, the PC 10 is connected to a plurality of printers 20 via the network 30. These printers 20 may be different models or may include a plurality of the same models. The network 30 can be of any standard regardless of wired radio. All or part of the printer 20 may be connected to a local printer port of the PC 10 without going through the network 30.

In any case, the PC 10 receives print settings used for printing from the user by the function of the printer driver 120 described later, and instructs the printer 20 to execute printing according to the print settings. The printer 20 executes printing according to the instruction.
Note that the printer 20 may be an image processing apparatus having functions other than printing. For example, it is conceivable to configure the printer 20 as an MFP (digital multifunction peripheral) having functions such as scanning, copying, facsimile communication, and document storage.

Next, FIG. 2 shows a hardware configuration of the PC 10.
The PC 10 may be a general computer as hardware. That is, the PC 10 includes a CPU 11, a ROM 12, a RAM 13, an HDD (hard disk drive) 14, a communication I / F (interface) 15, a display unit 16, and an operation unit 17, which are connected via a system bus 18.

Then, the CPU 11 executes the program stored in the ROM 12 or the HDD 14 using the RAM 13 as a work area, thereby controlling the entire PC 10 and realizing various functions including control of the printer 20.
The HDD 14 is a non-volatile storage medium (storage means) and stores various programs executed by the CPU 11 and various data to be described later.
The communication I / F 15 is an interface for communicating with an external device such as the printer 20. The communication standard to be used may be arbitrary regardless of wired or wireless.

The display unit 16 is a display unit such as a display for presenting information to the operator.
The operation unit 17 is an operation means for accepting an operation from an operator, such as a keyboard, a mouse, and a touch panel.
The display unit 16 and the operation unit 17 may be externally attached, or the PC 10 may be able to accept an operation from an external terminal device via a network.

Next, FIG. 3 shows a functional configuration of the PC 10. FIG. 3 mainly shows the configuration of parts related to the features of this embodiment.
As shown in FIG. 3, the PC 10 includes an OS (operating system) 110, a printer driver 120, a takeover model-dependent data registration unit 150, a use continuation condition registration unit 160, a use history registration unit 170, and a use continuation model registration unit 180. Is provided.

Among these functions, the functions of the OS 110 and the printer driver 120 are realized by the CPU 11 executing programs of the OS and the printer driver, respectively.
Then, the OS 110 receives document data to be printed from an application (not shown) having a function of editing or manipulating the document in accordance with a user operation, converts the document data into print data that can be handled by the printer driver 120, and sends the print data to the printer driver 120. API (Application Program Interface) function to pass.

  As will be described later, the OS 110 also has a function of registering a printer used for printing in association with a printer driver used when printing with the printer. When the user tries to perform printing, the printer registered here is presented as an option for the printer to be used. Then, the OS 110 notifies the application of the printer driver corresponding to the printer selected from them as a driver used for printing. Based on the notification, the application may access the UI module of the printer driver used for printing to display a print setting screen, or may request the OS 110 to pass print data to the printer driver used for printing through the API. it can.

Next, the printer driver 120 includes a driver core unit 130 and a model-dependent data registration unit 140, a use condition creation unit 121, a model use management unit 122, a use status determination unit 123, and a model information management unit 124.
Among these, the driver core unit 130 is a part having functions necessary for causing the printer to execute printing, and includes a UI module 131 and a renderer module 132 which are function providing units. In either case, depending on the model of the printer used for printing notified from the OS 110 or the application, the model-dependent data 141 corresponding to the model or the model-dependent data 141 or 151 is selected and operates according to the model-dependent data. At this time, when there is no appropriate model-dependent data in the model-dependent data registration unit 140, the take-over model-dependent data registration unit 150 may be searched.

  The UI module 131 has a function of causing a display unit such as a display to display a print setting screen for receiving print settings used when the printer performs printing. The contents of the print setting screen to be displayed are contents according to the referenced model-dependent data. In the model-dependent data, for example, parameter items and options to be accepted on the print setting screen are described.

  In addition, the UI module 131 has a function of accessing each unit of the use condition creation unit 121 to the model information management unit 124 so that the model-dependent data that is not included in the printer driver 120 due to the update of the printer driver 120 can be continuously used. Also equipped. This point will be described in detail later.

  The renderer module 132 performs a rendering process on the print data passed from the OS 110 according to the print settings received on the print setting screen provided by the UI module 131, and can be processed by the printer 20 of the model used for printing. (Page description language) A function for generating data is provided. In addition, it has a function of sending the generated PDL data to the printer 20 for printing.

The rendering process executed by the renderer module 132 also has contents according to the referenced model-dependent data. The model-dependent data includes, for example, the type of PDL to be used, the type of processing that can be described in the PDL data and executed by the printer 20 (double-sided printing, paper designation, paper discharge tray designation, post-processing, etc.), etc. Is done.
This rendering function itself may be equivalent to a conventional printer driver common to all models. However, the renderer module 132 can also access each of the use condition creation unit 121 to the model information management unit 124 via the UI module 131, and is involved in operations related to management of model-dependent data.

Next, the model-dependent data registration unit 140 has a function of registering the above-described model-dependent data 141. By registering the model-dependent data 141 corresponding to a plurality of models in the model-dependent data registration unit 140, the printer driver 120 can function as a model-common printer driver capable of controlling a plurality of model printers.
Here, a function for controlling a specific printer and executing printing, such as “a function for controlling a printer of model A”, is handled as one unit of the function. Accordingly, the model-dependent data 141 is function correspondence information including information for realizing the function for each of a plurality of functions. However, the unit of function is not limited to this. This point will be described later.

  In FIG. 3, the part included in the frame of the printer driver 120 is a function prepared in the PC 10 by installing the printer driver program. When the printer driver program is updated, it is replaced with a function provided by the updated program. That is, the model-dependent data 141 registered in the model-dependent data registration unit 140 is model-dependent data bundled with the printer driver program. The model-dependent data registration unit 140 corresponds to a second registration unit.

  When the printer driver program is updated, the model-dependent data that is not bundled with the updated printer driver program disappears from the model-dependent data registration unit 140. If it is desired to continue to use such model-dependent data after the update, it is necessary to register it in the model-dependent data registration unit 150 for transfer before the update.

Each unit of the use condition creation unit 121 to the model information management unit 124 provides a function related to registration (and deletion) of the model-dependent data. In FIG. 3, in the arrows between these units and the various registration units 150 to 180, the solid line indicates data writing to the registration unit, and the broken line indicates data reading from the registration unit.
The use condition creating unit 121 has a function of creating a continuation condition for selecting a function that the user wants to continue using after updating. The continuation condition is set by the user on the use continuation condition setting screen 400 (FIG. 6), which will be described later, and the content is registered in the use continuation condition registration unit 160 as the use continuation condition 161.

  The model use management unit 122 copies the model-dependent data registered in the model-dependent data registration unit 140, which is used for the UI module 131 or the renderer module 132, as a model-dependent data candidate that remains after the update. A function of registering in the model dependent data registration unit 150 for transfer is provided. Note that the model-dependent data 151 once registered in the model-dependent data registration unit 150 for transfer does not need to be registered again even when used again. At this time, the model use management unit 122 may determine whether or not the model-dependent data needs to be copied with reference to the use continuation condition 161. In other words, if only conditions unrelated to the use of model-dependent data (functions) are set, there is no point in performing a copy triggered by the use, so the copy may not be performed. The model use management unit 122 described above, together with the takeover model-dependent data registration unit 150, corresponds to the first registration unit.

The model usage management unit 122 also has a function of registering the usage history 171 of the model-dependent data (function) in the usage history registration unit 170. In this case, the model usage management unit 122 and the usage history registration unit 170 function as a history recording unit. Details of the usage history 171 will be described later.
When the printer driver 120 is updated, the usage status determination unit 123 refers to the usage continuation condition 161 and the usage history 171 to determine a model that should continue to be used, and uses that model as a usage continuation model list 181. As a function to be registered in the continued use model registration unit 180. The model that is not registered here is a model whose model-dependent information should be deleted from the model-dependent data registration unit for handover 150 when performing the update. The usage status determination unit 123 corresponds to a determination unit.

When updating the printer driver 120, the model information management unit 124 refers to the list of continued use models 181 and deletes model-dependent information of models not registered here from the takeover model-dependent data registration unit 150. It has a function to do. The model information management unit 124 corresponds to a deletion unit.
On the contrary, if the model-dependent information of the model registered in the continued-use model list 181 is not registered in the takeover model-dependent data registration unit 150, the model information management unit 124 converts this into the model-dependent data registration unit. A function of reading out from 140 and registering in the model-dependent data registration unit 150 for transfer is also provided.
Further, when the UI module 131 or the renderer module 132 uses the model-dependent data 151 registered in the takeover model-dependent data registration unit 150, the model information management unit 124 reads and provides the model-dependent data 151. It also has functions.

  Also, each registration unit of the takeover model-dependent data registration unit 150, the use continuation condition registration unit 160, the use history registration unit 170, and the use continuation model registration unit 180 includes a model-dependent data 151, a use continuation condition 161, and a use history, respectively. 171 and the continued use model list 181 are provided. Each of these registration units registers each data in a storage area that does not affect the data even when the printer driver 120 is upgraded. Further, the positions of those storage areas are made known to each part of the use condition creation unit 121 to the model information management unit 124. It is conceivable to register each of the above data as a predetermined item in the registry or a file having a predetermined path.

Next, printer registration in the PC 10 will be described.
FIG. 4 is a diagram for explaining this.
As described above, in the PC 10, the OS 110 registers the printer used for printing in association with the printer driver used when printing with the printer.
When the user instructs the OS 110 to add a printer to be used, the OS 110 causes the user to select a printer to be used from the printers 20 accessible from the PC 10. This access may be an access via a print server. Alternatively, access through a local port may be used.

  When the user selects a printer, the OS 110 determines the model of the printer. If a printer driver capable of controlling the model is installed, it is registered that printing using the selected printer should be executed using the corresponding printer driver. This is the usage registration 190 shown in FIG. A printer driver that can control a plurality of types of printers, such as the printer driver 120 shown in FIG. 3, can be registered in association with a plurality of types of printers.

When the user intends to perform printing, the OS 110 presents the printer registered as described above as an option for a printer to be used for printing. It can be presented as an icon for each printer or presented using a pull-down menu.
When the user selects a printer, the OS 110 notifies the printer driver 120 of the model and address of the printer used for printing directly or via an application for printing. The printer driver 120 selects model-dependent data corresponding to the printer model based on the notification, and operates the UI module 131 and the renderer module 132. In addition, the renderer module 132 transmits the generated PDF data to the notified address.

Note that when creating the use registration 190, the printer model need not necessarily be specified. The usage registration 190 can be created even under the condition that a printer with a specific address is used, although the individual or model differs depending on the case. The printer C usage registration in FIG. 4 corresponds to this.
In this case, when the use of the corresponding printer is selected for printing, the OS 110 accesses the address, specifies the model of the printer at the address at that time, and notifies the printer driver 120 of it. As long as the model-dependent data is registered in the model-dependent data registration unit 140 or the takeover model-dependent data registration unit 150, the printer driver 120 can handle the model even if the model is not determined in advance.

Next, FIG. 5 shows a specific example of model-dependent data.
5A and 5B show model-dependent data corresponding to different models. There is no difference in format between the model-dependent data 141 registered in the model-dependent data registration unit 140 and the model-dependent data registered in the model-dependent data registration unit 150 for takeover.
In the model-dependent data shown in (a), the value of model indicated by reference numeral 301 is the model of the printer corresponding to the model-dependent data. It can be seen that the model-dependent data is data used for controlling the model “model A”.

The value of the warranty period indicated by reference numeral 302 is the support guarantee period of the printer of the corresponding model by the vendor. It can be seen that the support guarantee period for the model A is February 14, 2013.
The value of feature name indicated by reference numeral 303 is information on one setting item of print settings. The first line is the name of the setting item, and the second and subsequent lines are options that can be selected with the corresponding setting item. In the model A, it can be seen that “color” and “monochrome” can be set for the color setting function. This feature
name is included in the model-dependent data for the number of print setting items.

The format of the model-dependent data shown in (b) is the same as that in (a). It can be seen from the values of model and warranty period that this model-dependent data is used for controlling the model of “model B”, and the support guarantee period for model B is February 14, 2019.
As for feature name, items different from (a) are included, or the same item has different choices. It can be seen that the functions that can be set and the choices of model A and model B are different.

Next, the use continuation condition 161 will be described.
FIG. 6 shows an example of a use continuation condition setting screen for accepting setting of use continuation conditions. FIG. 7 shows a data example of the use continuation condition.
The use continuation condition setting screen 400 in FIG. 6 is a screen in which the UI module 131 acquires necessary data from the use condition creation unit 121 and displays it on the display unit 16 according to a user instruction. The use continuation condition setting screen 400 includes a use model selection unit 401, a custom condition selection unit 402, a predetermined period selection unit 403, a registered model selection unit 404, and a support period selection unit 405 corresponding to the settable conditions. . Further, an OK button 406 and a cancel button 407 are provided.

Among these, the used model selection unit 401 is an area for selecting a “used model” condition, which is a condition that model-dependent data is not deleted for models that have been used so far. If the user selects this, all models that the user has used in the past can continue to be used even if the model-dependent data is not included in the driver due to the update.
Note that the model-dependent printer driver often includes model-dependent data for a large number of successive printers sold by vendors, and it is usually considered that only a few models are used by the user. Therefore, even if all model-dependent data of models that have been used in the past is retained, the search load and data capacity are increased compared to the case where all model-dependent data included in the printer driver before update is retained. It can be reduced.

  The custom condition selection unit 402 is an area for selecting a condition other than the “use model”. The used model selection unit 401 and the custom condition selection unit 402 can be alternatively selected by a radio button on the left side. FIG. 6 shows a state where the custom condition selection unit 402 is selected.

The predetermined period selection unit 403 and the registered model selection unit 404 are positioned below the custom condition selection unit 402 and are effective only when the custom condition selection unit 402 is selected.
Among these, the predetermined period selection unit 403 selects a condition “use within a predetermined period”, which is a condition that the model-dependent data is left without being deleted for the models used within the most recent predetermined period before the update. It is an area. This can be selected by checking the check box on the left side. In addition, the number of days in a predetermined period can be entered in the edit box. In the example of the figure, “90 days” is set.

  This condition has a narrower range for leaving model-dependent data than the “used model”. However, while the most recently used models are likely to be used in the future, those that have been used long ago and not used afterwards are considered to be unlikely to be used in the future. By using the “use within predetermined period” condition, the model-dependent data that is unlikely to be used in this way can be deleted, and the search load and data capacity can be further reduced.

The registered model selection unit 404 is an area for selecting a “registered model” condition, which is a condition that the model-dependent data is not deleted for a printer model registered as a printer to be used for printing. . This can be selected by checking the check box on the left side. If this is selected by the user, all models that have been registered for use as shown in FIG. 4 at the time of the update will not have the model-dependent data shared with the driver, regardless of whether or not they have actually used it. You can continue to use it even if it is packed.
Since it is considered that the models included in the options are likely to be used in the future, there is a strong demand for leaving model-dependent data for such models. If the model is undefined and registered for use, the model of the printer connected at the time of the update is the model that can continue to be used.

  These predetermined period selection unit 403 and registered model selection unit 404 can be selected and deselected independently. If neither the predetermined period selection unit 403 nor the registered model selection unit 404 is selected while the custom condition selection unit 402 is selected, all model-dependent data that is not bundled with the new driver is deleted when the driver is updated. It will be.

  The support period selection unit 405 is an area for selecting a “guarantee period” condition, which is a condition for deleting model-dependent data for models that are not within the vendor's support warranty period. This can be selected by checking the check box on the left side. This condition can be selected and deselected independently of other conditions. If the user selects this, all models whose vendor support has expired at the time of the update will not include the model-dependent data in the driver, regardless of whether other conditions are met. If you do not continue to use.

  If it is not desirable to continue using a model whose support period has expired, it is possible to automatically disable use of the corresponding model by selecting this condition. The model-dependent data 151 registered in the take-up model-dependent data registration unit 150 in accordance with the use continuation condition remains on the PC regardless of whether or not the driver is included in the driver. Therefore, if no action is taken, it will remain even after the support period has expired, which may cause a problem. However, if the “guarantee period” condition is set, it is possible to prevent problems due to the expiration of the support period.

  An OK button 406 is a button for confirming the selection made in each of the above units and generating data of the use continuation condition 161 as shown in FIG. 7 indicating the selected condition. A cancel button 407 is a button for closing the use continuation condition setting screen 400 without changing the previous use continuation condition 161.

In the data example of FIG. 7, “data” indicates that the condition “use within a predetermined period” is set. The number after that indicates the number of days in the predetermined period. “Update” and “warranty” indicate that the conditions of “registered model” and “warranty period” are set, respectively. That is, the data example of FIG. 7 is the use continuation condition 161 corresponding to the screen state of FIG.
Although not shown in FIG. 7, when the “use model” condition is set, this is indicated by the characters “all”.

Next, operations and processes related to maintenance and deletion of model-dependent data when the printer driver 120 is updated in the PC 10 will be described.
In the following description, in order to simplify the description, the operation or process performed by the CPU 11 of the PC 10 by executing some program will be described as the program executing the operation or process.

Here, FIG. 8 shows an outline of operations executed by the PC 10.
In FIG. 8, an existing printer driver 120a is a printer driver before update, and a new printer driver 120b is a printer driver after update. The installer 200 is a program for installing the new printer driver 120b in the PC 10. In FIG. 8, the broken line portion of the lines indicating the operation of each program indicates that the corresponding program is not operating at that timing. The installer 200 may be executed by a device external to the PC 10.

  In FIG. 8, the operation up to the first broken line is the normal operation of the existing printer driver 120a. In this operation, the existing printer driver 120a provides UI and renderer functions using model-dependent data corresponding to the printer model in accordance with a request from the OS 110 or an application (S11). When the function is provided, the usage history 171 is updated by the processing of FIG. 9 described later, and the model-dependent data used in step S11 is registered in the model-dependent data registration unit 150 for transfer as necessary (S12). ).

  The printer driver 120a repeats the operations so far as long as it is installed. As a result, the usage history for each printer model in the existing printer driver 120 a is registered as the usage history 171. The significance of registering the model-dependent data in the model-dependent data registration unit 150 for transfer in step S12 will be described later.

Thereafter, when a new version of the new printer driver 120b is released and the user downloads it and gives an instruction to execute installation, or when installation is automatically started by the point-and-print function or the like, the operation proceeds to steps S13 to S17. move on.
The installer 200 sends an update preparation notification to the existing printer driver 120a to be deleted by the update before starting the installation of the new printer driver 120b (S13). This notification is to be executed at this time if there is a process to be executed by the existing printer driver 120a before being deleted by update.

Upon receiving this notification, the existing printer driver 120a discriminates between the model-dependent data that remains after the upgrade and the model-dependent data that remains after the upgrade, by the processing shown in FIGS. The data registration unit is organized (S14). When this is completed, an update permission response indicating that updating is permitted is transmitted to the installer 200 (S15).
Upon receiving this update permission response, the installer 200 deletes the existing printer driver 120a (S16) and installs a new printer driver 120b (S17). This process is a process of replacing the printer driver 120 in FIG. 3 with the new printer driver 120b.

  Therefore, after step S17, the model-dependent data that is not bundled with the new printer driver 120b is not registered in the model-dependent data registration unit 140. However, if the model-dependent data is registered in the takeover model-dependent data registration unit 150, the new printer driver 120b can continue to maintain the function of controlling the printer of that model.

After the installation of the new printer driver 120b is completed by the above operation, the new printer driver 120b provides the UI and renderer functions using the model-dependent data corresponding to the model of the printer (S18). When the function is provided, the usage history 171 is updated, and the model-dependent data is registered in the takeover model-dependent data registration unit 150 as necessary (S19).
Thereafter, when a new version of the printer driver is released, update is executed in the same manner as in steps S13 to S17.

Next, the process executed by the printer driver 120 in steps S12 (S19) and S14 in FIG. 8 will be described more specifically.
First, FIG. 9 shows a flowchart of processing when the printer is used, which is executed by the printer driver 120 in step S12 (S19) of FIG.

The printer driver 120 starts the process of FIG. 9 when the user provides the function of the printer driver 120 and causes the user to use the printer 20. Here, it is assumed that the printer is used when printing is executed, but the trigger is not limited to this, such as using the printer only by opening the print setting screen. Further, it is assumed that the model of the printer that has performed printing is model P.
In the process of FIG. 9, the printer driver 120 first determines whether or not the model P data is described in the usage history 171 (S21).

FIG. 10 shows an example of the usage history 171. The usage history 171 describes the printer model that the user has used so far and the last usage date that is the date when the printer of that model was last used. It is a thing. Note that the model data is referred to when determining the continuation condition of “use model” and “use within a predetermined period”. The data on the last use date is referred to when making a determination regarding the continuation condition of “use within a predetermined period”.
Note that the last use date is registered here because the information necessary for the determination regarding the continuation condition of “use within a predetermined period” is when the corresponding model was last used. If there is a continuation condition that considers other information such as the number of times of use, the information described in the use history 171 is also changed accordingly.

  Returning to the description of FIG. 9, in the case of Yes in step S <b> 21, the printer driver 120 updates the last use date of the model P in the use history 171 to the current print date (S <b> 22) and ends the processing. This is because it is considered that the model-dependent data 151 is registered in the succeeding model-dependent data registration unit 150 in the process of step S24 for the model described in the usage history 171 when the description is added previously. .

If NO in step S21, the printer driver 120 adds information indicating that the model P has been used to the usage history 171 and adds the current printing date as information on the last usage date (S23). Thereafter, the model-dependent data of the model P is read from the model-dependent data registration unit 140, a copy thereof is registered in the model-dependent data registration unit 150 for takeover (S24), and the process ends.
In the above processing, the CPU 11 functions as a history recording unit in steps S22 and S23, and the CPU 11 functions as a first registration unit in step S24.

  The reason why the model-dependent data is copied in step S24 is to reduce the processing load when updating the driver. The model used may register model-dependent data in the model-dependent data registration unit 150 for takeover at the time of update and leave it after the update. However, if copying is performed at the time of update, it will take time. This is something to go first.

However, when the “use model” or “use within a predetermined period” condition is not set as the use continuation condition 161, there is no particular relationship between using the printer and whether to leave the model-dependent data after the update. Further, when these conditions are not set, the use history 171 is not referred to at the time of update. Therefore, when these conditions are not set, it is not necessary to perform the processing of FIG.
For this reason, when these conditions are not set, the process of FIG. 9 may not be performed. However, since the condition may be changed later, it is preferable to execute the process of FIG. 9 regardless of the condition currently set as the use continuation condition 161.

Next, FIG. 11 to FIG. 13 are flowcharts of processing when installing a new printer driver, which is executed by the printer driver 120 in step S14 of FIG.
When the printer driver 120 detects the update preparation notification in step S13 of FIG. 8, the printer driver 120 starts the processing shown in the flowchart of FIG. In the process up to step S42, based on the use continuation condition 161 and the use history 171, the model that should remain the model-dependent data after the update is discriminated from the model that does not, and the model that should remain is used continuation model list 181. It is a process described in.

  In the process of FIG. 11, the printer driver 120 first determines whether or not the “continuation model 161” is included in the use continuation condition 161 (S31). In the case of Yes, it is further determined whether or not there is a model for which model-dependent data is not included in the new printer driver 120b among the models currently registered for use (S32). Here, in the case of Yes, a model that is not included is added to the continued use model list 181 (S33). In the case of No in step S31 or S32, the process proceeds to step S34 and subsequent steps.

  Note that, in the determination in step S32, the determination as to whether the model should retain the model-dependent data after the update and the model that does not remain is based on “whether or not the model is currently registered for use”. With regard to “the model-dependent data is not included in the new printer driver 120b”, if it is included, the use of the corresponding model can be continued without leaving the model-dependent data in the model-dependent data registration unit 150 for transfer. Therefore, it is not left here. Correspondingly, the corresponding model is not described in the continued use model list 181.

  This is preferable from the viewpoint of the model-dependent data search load and data capacity reduction, but all models that have been determined that model-dependent data should remain even after the update are stored in the model-dependent data registration unit 150 for transfer. It is not impeded to leave the dependency data. The same applies to the determination in step S35. Also, which model-dependent information is included in the new printer driver 120b is notified of the storage location of the new printer driver 120b in the update preparation notification, and the data of the new printer driver 120b is searched to determine the file structure. It can be grasped by referring to it.

  Next, the printer driver 120 determines whether the use continuation condition 161 includes a “use model” or “use within a predetermined period” condition (S34). In the case of Yes, it is further determined whether there is a model that does not include model-dependent data in the new printer driver 120b among the models described in the use history (S35). Here, in the case of Yes, a model that is not bundled is added to the continued use model list 181 (S36). In the case of No in step S34 or S35, the process proceeds to step S37 and subsequent steps.

  Note that, in the determination in step S35, the model that should retain the model-dependent data after the update and the model that does not remain are determined based on “whether or not the model is listed in the use history”. When the condition is “use within a predetermined period”, “whether use within a predetermined period” is also considered in the next process.

  Next, the process proceeds to the portion shown in FIG. 12, and the printer driver 120 determines whether or not the use continuation condition 161 includes a “use within predetermined period” condition (S37). In the case of Yes, it is further determined whether or not there is model information in the usage history 171 that has passed a predetermined period of time defined in the usage continuation condition from the last printing date (S38). Here, in the case of Yes, if the corresponding model is described in the continued use model list 181, this is deleted (S39). In the case of No in step S37 or S38, the process proceeds to step S40 and subsequent steps. Even if this part of the process is “use within a predetermined period”, in step S36, the last print date and time is registered without considering the last print date and time. Thus, it is for leaving a thing that meets the condition of “use within a predetermined period”.

  Next, the printer driver 120 determines whether or not the use continuation condition 161 includes a “guarantee period” condition (S40). In the case of Yes, it is further determined whether or not there is a model that has passed the warranty period described in the model-dependent data in the continued-use model list 181 (S41). Here, in the case of Yes, if the corresponding model is described in the continued use model list 181, this is deleted (S42). In the case of No in step S40 or S41, the process proceeds to step S43 and subsequent steps. This part of the process is for keeping the model-dependent data of the model whose warranty period has passed after the update in accordance with the condition of the “warranty period”.

Next, the process proceeds to the portion shown in FIG. This process is a process for maintaining the takeover model-dependent data registration unit 150 and the use history 171 in accordance with the continued use model list 181 created up to step S42.
In this part of processing, the printer driver 120 first selects a model whose model-dependent data corresponding to the model is not registered in the model-dependent data registration unit 150 for transfer among the models described in the continued use model list 181. It is determined whether or not there is (S43). If this is Yes, the printer driver 120 reads the model-dependent data of the corresponding model from the model-dependent data registration unit 140 and registers a copy thereof in the model-dependent data registration unit 150 for takeover (S44).

If the condition of “registered model” is set in the use continuation condition 161, if there is a model that has been registered for use but has never been used, the model-dependent data for that model is now dependent on the model to be taken over Registered in the data registration unit 150.
The process in step S44 is the same as the process in step S24 in FIG. 9 except that the execution time is different. If No in step S43, the process proceeds to step S45 as it is.

  Next, the printer driver 120 determines whether there is a model that is not listed in the continued use model list 181 among the models whose model-dependent data is registered in the takeover model-dependent data registration unit 150 (S45). If this is Yes, the printer driver 120 deletes the model-dependent data of the corresponding model from the takeover model-dependent data registration unit 150 (S46). This is because there is no need to leave model-dependent data for these models after the update. Some of the model-dependent data to be deleted here is not included in the model-dependent data registration unit for transfer 150 because it is included in the new printer driver 120b.

  Thereafter, the printer driver 120 deletes the description about the model that is not in the continued use model list 181 from the use history 171 (S47), and ends the process. This is because for models that are not in the continued use model list 181, model-dependent data is not left in the model-dependent data registration unit 150 for takeover, so that the usage history is also temporarily reset at the time of update.

  In the above processing, in steps S32, S35, S38, and S41, the CPU 11 functions as a determination unit. In step S44, the CPU 11 functions as a first registration unit. In step S46, the CPU 11 functions as a deleting unit.

  Through the above processing, when the printer driver 120 is updated, the printer driver 120 should be able to continue to be used after the update based on the use continuation condition 161 (model-dependent data that should remain after the update). Can be determined. Then, based on the determination result, only the model-dependent data of the model that should be usable can be left in the model-dependent data registration unit 150 for transfer.

Therefore, the number of model-dependent data registered in the model-dependent data registration unit 150 for transfer is suppressed, the search load and the storage capacity of the model-dependent data are suppressed, and the user convenience is maintained in terms of providing functions. Can do.
Further, since the model-dependent data bundled with the updated printer driver can be used after the update without registering in the model-dependent data registration unit 150 for transfer, the model-dependent data registration unit 150 for transfer is used. Is not registered. Therefore, the model-dependent data registered in the model-dependent data registration unit 150 for transfer can be minimized, and the storage capacity can be reduced.

  Various registration units 150 to 180 are provided outside the printer driver 120 (a storage area that is not directly affected by the update of the printer driver 120). Therefore, even if the installer does not perform special processing when updating the printer driver 120, the model-dependent data as described above can be retained and deleted, and the development load of the installer does not increase.

Next, a specific example of management of model-dependent data in accordance with the processes and operations described so far will be described with reference to FIG.
FIG. 14 shows model-dependent data registered in the model-dependent data registration unit 140, usage history 171, takeover at each time when the events described on the left side occur along the time series from (a) to (f). The model-dependent data registered in the use-model-dependent data registration unit 150 and the model of the printer registered for use are shown.

(A) shows a state when a version 1.0 printer driver is first installed and the user registers printing of printers of models A to C using the printer driver.
It is assumed that the model-dependent data of models A to D is included in version 1.0, and these model-dependent data are registered in the model-dependent data registration unit 140. In addition, the registered models are registered models A to C. At this time, the use history 171 and the model-dependent data registration unit 150 for takeover are empty.

(B) shows a state after the printers of model A and model B are used thereafter. At this time, the use model and the last use date are described in the use history 171 by the process of FIG. In addition, the model-dependent data corresponding to the model A and the model B are registered in the model-dependent data registration unit 150 for transfer when the model A and the model B are used for the first time by the process of step S24 in FIG.
The contents of the model-dependent data registration unit 140 and the registered use model do not change depending on the use of the printer.

(C) shows a state after the printer driver is updated and the version 2.0 printer driver is installed. It is assumed that the use continuation condition 161 at the time of update is “model used”.
In version 2.0, model-dependent data of model A and model B is not included, model-dependent data of model E and model F are newly included, and model-dependent data of models C to F are included as a whole. Suppose that These model-dependent data are registered in the model-dependent data registration unit 140.

  On the other hand, since the model A and the model B that are not included in the package both satisfy the “use model” condition, the model-dependent data is stored in the model-dependent data registration unit 150 for transfer as a result of the processing of FIGS. 11 to 13. Will remain and can be used after the update. The usage history 171 also remains as it is. The registered models are not affected by the update.

(D) shows a state after model D is registered for use and model A is unregistered. In response to this registration and deregistration, information on the registered model used is changed, but other information is not affected by the registration and deregistration.
(E) shows a state after the printers of model B and model D are used thereafter. At this time, the model D information is added to the usage history 171 by the process of FIG.

(F1) shows the state after the printer driver is updated and the version 3.0 printer driver is installed. The usage continuation condition 161 at the time of update is “use within a predetermined period”, and the models B and D are used within a predetermined period, but the use of the model A is assumed to be before the predetermined period.
In version 3.0, model-dependent data of model C is not included, model-dependent data of model G is newly included, and model-dependent data of models D to G is included as a whole. These model-dependent data are registered in the model-dependent data registration unit 140.

On the other hand, the non-enclosed model C does not have a history of use and does not satisfy the condition of “use within a predetermined period”. Therefore, as a result of the processing of FIG. 11 to FIG. Model-dependent data will not be left. In addition, model A for which model-dependent data has been registered in the model-dependent data registration unit for takeover 150 is not used within a predetermined period, so that it becomes a determination result indicating that model-dependent data is not left. The model-dependent data is deleted from the data registration unit 150.
Accordingly, the models A and C that can be used before the update cannot be used after the update. However, it is considered that the model A and the model C are unlikely to be used in the future, and this is not a problem. Note that the model A information is also deleted from the usage history 171.

On the other hand, since the model B satisfies the condition “use within a predetermined period”, the model-dependent data is left in the model-dependent data registration unit 150 for transfer and can be used after the update.
For model D, although the “use within a predetermined period” condition is met, model-dependent data is included in the version 3.0 printer driver. Model-dependent data is deleted. However, even after the update, the control function of the model D can be used using the model-dependent data of the model-dependent data registration unit 140.

With the deletion of the model-dependent data from the model-dependent data registration unit for takeover 150, the model D information is also deleted from the usage history 171 and the history is counted again. However, the history may not be deleted for models that can continue to be used.
The fact that the registered model is not affected by the update is the same as in the case of (c).

(F2) shows an example in which, after (e), an update to version 3.0 is performed under the conditions of “registered model”.
Also in this case, the model-dependent data registered in the model-dependent data registration unit 140 is the same as in the case of (f1).
However, since the model C that is not included is registered for use and satisfies the condition of “registered model”, the model-dependent data is stored in the model-dependent data registration unit 150 for transfer as a result of the processing of FIGS. 11 to 13. Will remain and can be used after the update. However, the information on the model C is not registered in the usage history 171 in response to this.

Handling of model A, model B, and model D is the same as in the case of (f1). However, whether or not to make it usable after the update is determined by whether or not there is a use registration for the corresponding model.
As described above, according to the processing and operation described above, it is possible to use a model that is likely to continue to be used even after the model-dependent data is not included in accordance with the use continuation condition 161. it can. In addition, it is possible to delete model-dependent data of models that are unlikely to be used.

Although the description of the embodiment and the comparative example is finished as described above, in the present invention, the specific configuration of each unit, the processing procedure, the configuration and format of data to be handled, and the like are not limited to those described in the embodiment.
For example, the use continuation condition may be set other than those described in the above embodiment. It has been used more than a predetermined number of times in the most recent predetermined period.

Further, the function unit does not necessarily have a one-to-one correspondence with the model to be controlled. For example, from the model of the device to be controlled, such as “function to control the printer of model A and provide its UI in Japanese” and “function to control the printer of model A and provide its UI in Italian” It is also possible to divide functions into fine units and prepare function correspondence information for each function.
In this way, for example, even if model-dependent data providing an Italian UI from a certain version of the printer driver is not included, the model-dependent data is left in the model-dependent data registration unit 150 for transfer. Will continue to provide Italian UI.

As described above, when providing model-dependent information corresponding to the combination of model and language, the usage history is also registered for each combination of model and language, and whether or not it has been used is also determined by the combination of model and language. It is good to do it to the standard.
Further, the use continuation condition may be set individually for the model and the language. For example, “registered model” is set for the model, “use language” is set for the language, and all the model-dependent data of the language that has been used even once is left for the registered model.

In addition to the language, a driver corresponding to a function included in a device to be controlled, such as “function to control the printer function of model A” and “function to control the scanner function of model A” is distinguished. It is also possible to distinguish the functions provided by.
On the contrary, it is also conceivable that the driver provides a function for controlling a plurality of models by using one function correspondence information, such as “a function for controlling printers of model A and model B”.

Further, the function provided by the program executed by the PC 10 using the function correspondence information is not limited to the control of the image forming apparatus such as a printer, and may be any scanner, facsimile apparatus, MFP, projector, electronic whiteboard, remote conference system, etc. This function may control the device. Alternatively, functions other than device control may be used. In these cases, a module necessary for providing the function is provided instead of or in addition to the renderer module 132.
The apparatus for executing the program is not limited to the PC, and any information processing apparatus may be used as long as the apparatus includes a processor capable of executing the program. The scanner, facsimile apparatus, MFP, projector, electronic whiteboard, remote conference system, and the like may be used. It may be a portable information terminal or a smartphone.

In the above-described embodiment, the processing of FIGS. 11 to 13 has been described as being executed by the existing printer driver 120a, but may be executed by the installer 200.
In the above-described embodiment, the example in which the various registration units 150 to 180 are provided outside the printer driver 120 has been described, but this is not essential. During operation of the printer driver 120, these registration units are provided as a part of the printer driver 120, and when the printer driver 120 is uninstalled, the various registration units 150 to 180 may be evacuated to positions that are not deleted. Good.
In this case, there is no need to distinguish between the model-dependent data registration unit 140 and the takeover model-dependent data registration unit 150.

  The various registration units 150 to 180 may be provided outside the PC 10 as long as they can be referred to from the printer driver 120. It may be provided in a server device in a user environment or a storage device in a cloud environment. In addition, the functions that the PC 10 includes in the above-described embodiment may be provided in a distributed manner in a plurality of information processing apparatuses, and these apparatuses may cooperate to realize the same functions as the PC 10.

A program according to an embodiment of the present invention is a program for realizing a management function of function correspondence information such as the printer driver 120 described above by cooperating one computer or a plurality of computers. Then, by causing the computer to execute such a program, the above-described effects can be obtained.
Such a program may be stored in a ROM or other nonvolatile storage medium (flash memory, EEPROM, etc.) provided in the computer from the beginning. However, it can also be provided by being recorded on an arbitrary nonvolatile recording medium such as a memory card, CD, DVD, or Blu-ray disc. Each procedure described above can be executed by installing the program recorded in the recording medium in a computer and executing the program.

  Furthermore, it is also possible to download from an external device that is connected to a network and includes a recording medium that records the program, or an external device that stores the program in a storage unit, and install and execute the program on a computer.

An information processing system of the present invention is a system including the above-described program and a device controlled by a device control function provided by the program using function correspondence information. By combining the program and the device, the effects described in the embodiment and the modification can be obtained.
Moreover, it is needless to say that the configurations of the embodiment and the modified examples described above can be arbitrarily combined and implemented as long as they do not contradict each other.

10: PC, 11: CPU, 12: ROM, 13: RAM, 14: HDD, 15: Communication I / F, 16: Display unit, 17: Operation unit, 18: System bus, 20: Printer, 30: Network, 110: OS, 120: Printer driver, 120a: Existing printer driver, 120b: New printer driver, 130: Driver core unit, 131: UI module, 132: Renderer module, 140: Model-dependent data registration unit, 141, 151: Model Dependent data, 150: Transfer model dependent data registration unit, 160: Use continuation condition registration unit, 161: Use continuation condition, 170: Use history registration unit, 171: Use history, 180: Use continuation model registration unit, 181: Use Continuous model list, 190: use registration, 200: installer, 400: use continuation condition setting screen, 4 1: for model selection unit, 402: Custom condition selection unit, 403: a predetermined period selection unit, 404: registration model selection unit, 405: supporting period selection unit, 406: OK button 407: Cancel Button

JP 2004-78745 A

Claims (19)

Computer
First registration means for registering function correspondence information including information for realizing the function for each of a plurality of functions;
Condition registration means for registering a continuation condition, which is a condition for selecting function correspondence information that remains even after updating a predetermined program that provides the function using the function correspondence information;
When updating the predetermined program, based on the continuation condition, a determination unit that determines whether to leave or delete the function correspondence information registered by the first registration unit;
A program for functioning as deletion means for deleting function correspondence information determined to be deleted by the determination means. The program according to claim 1,
Said computer further
Function as history recording means for recording the usage history of the function,
The determination means includes a function of performing the determination by applying the use history to the continuation condition. The program according to claim 2,
The condition registering unit can register a condition that, as the continuation condition, a condition that, when a certain function has been used, function correspondence information corresponding to the function is left, can be registered. The program according to claim 2 or 3,
The condition registering unit is capable of registering, as the continuation condition, a condition that a function corresponding information corresponding to a function remains when the function is used within a predetermined period. A program according to any one of claims 1 to 4,
The condition registration means can register a condition that, as the continuation condition, a function correspondence information corresponding to a function registered to be included in an option to be presented to a user is left among the plurality of functions. A program characterized by A program according to any one of claims 1 to 5,
The condition registering unit is capable of registering, as the continuation condition, a condition that the function correspondence information not within the vendor's support guarantee period is deleted. A program according to any one of claims 1 to 6,
The condition registering unit registers the continuation condition according to an instruction from a user. A program according to any one of claims 1 to 7,
The computer,
A function providing means for providing the function using the function correspondence information;
A program for functioning as a second registration means for registering the function correspondence information installed together with the program;
The first registration unit includes a function of registering the function correspondence information when the function provision unit provides a function using the function correspondence information registered by the second registration unit. Program to do. The program according to claim 8, wherein
The first registration unit is a function correspondence information registered by the second registration unit and not yet registered by the first registration unit when the predetermined program is updated. A program having a function of newly registering what is determined to remain based on the continuation condition. First registration means for registering function correspondence information including information for realizing the function for each of a plurality of functions;
Condition registration means for registering a continuation condition, which is a condition for selecting function correspondence information that remains even after updating a predetermined program that provides the function using the function correspondence information;
When updating the predetermined program, based on the continuation condition, a determination unit that determines whether to leave or delete the function correspondence information registered by the first registration unit;
An information processing apparatus comprising: deletion means for deleting function correspondence information determined to be deleted by the determination means. The information processing apparatus according to claim 10,
A history recording means for recording the usage history of the function;
The information processing apparatus according to claim 1, wherein the determination unit performs the determination by applying the use history to the continuation condition. The information processing apparatus according to claim 11,
The information processing apparatus according to claim 1, wherein the condition registering unit can register a condition that, as the continuation condition, a function corresponding information corresponding to a function is left when a function has been used. An information processing apparatus according to claim 11 or 12,
The condition registration means is capable of registering, as the continuation condition, a condition that, when a certain function is used within the most recent predetermined period, the function correspondence information corresponding to the function is left. apparatus. An information processing apparatus according to any one of claims 10 to 13,
The condition registration means can register a condition that, as the continuation condition, a function correspondence information corresponding to a function registered to be included in an option to be presented to a user is left among the plurality of functions. An information processing apparatus characterized by the above. The information processing apparatus according to any one of claims 10 to 14,
The information processing apparatus according to claim 1, wherein the condition registration unit can register a condition that the function correspondence information that is not within a vendor guarantee period is deleted as the continuation condition. The information processing apparatus according to any one of claims 10 to 15,
The information registration apparatus, wherein the condition registration unit registers the continuation condition in accordance with an instruction from a user. An information processing apparatus according to any one of claims 10 to 16,
A function providing means for providing the function using the function correspondence information;
Second registration means for registering the function correspondence information installed together with the predetermined program,
In the first registration unit, the function providing unit provides a function using the function correspondence information registered by the second registration unit and not yet registered by the first registration unit. And an information processing apparatus for registering the function correspondence information. The information processing apparatus according to claim 17,
The first registration unit is a function correspondence information registered by the second registration unit and not yet registered by the first registration unit when the predetermined program is updated. An information processing apparatus for newly registering what is determined to remain based on the continuation condition. The program according to any one of claims 1 to 9, wherein the function is a device control function;
An information processing system comprising a device controlled by the device control function.

Images