JP2021190956A - Information processing system, method for controlling installation data management apparatus, method for controlling device, and program - Google Patents

Abstract

To provide an information processing system, a method for controlling an installation data management apparatus, a method for controlling a device, and a program with which after the completion of initial installation, an operator can complete initial installation operations on a device without directly editing destination related items.SOLUTION: In order to set a destination to destination related items, a method includes an installation data management apparatus issuing a temporary destination ID when a destination is newly created, and a device creates a destination ID when taking in a destination including the temporary destination ID thereto and replaces the temporary destination ID with the value of a permanent destination ID.SELECTED DRAWING: Figure 12

Description

The present invention relates to an information processing system capable of efficiently installing a device such as a multifunction device connected to a server on a network, a control method of an installed data management device, a device control method, and a program.

Generally, when a device such as a multifunction device is newly introduced, an initial installation work of changing the device setting information according to the customer environment is required. The initial installation of the device takes a lot of time and effort. Therefore, when performing the same initial installation work for multiple devices, installation information is prepared in advance, and the initial installation worker (hereinafter referred to as "worker") operates the device and the setting information. An initial installation system has been proposed that applies. The installation information is created in advance by the creator of the installation information (hereinafter referred to as the "creator") using the installation data editing tool.
Some setting information, such as an address book, is formed by collecting a large number of items (destination).

In such setting information, the device issues a unique ID within the device to distinguish each item and associates it with the item. For example, in an address book, a unique destination ID is issued within a device to identify an individual destination.
On the other hand, in the setting information, there are many setting items (hereinafter referred to as "destination-related items") for setting a destination for sending some data, such as specifying a destination for a report. .. Generally, in the destination-related items, the destination ID of the address book is set as a value without directly inputting an e-mail address or the like. Destination attributes (values such as destination name, email address, fax number, etc.) are often changed during operation of the device in the customer environment. Since it is inefficient to change the values of many destination-related items one by one each time, the values of the destination-related items are set via the destination ID instead of directly inputting the e-mail address or the like. It is common to link with the address book.

However, when a destination is added or deleted, the cooperation with the destination-related item via the destination ID is interrupted due to the change, so the destination ID set as the value of the destination-related item is changed. There must be. When the device detects that the value of the destination has been changed, it searches for a destination-related item having the destination ID of the destination as a value, and changes the value to the new destination ID (see, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2016-54431

By the way, the destination ID can be generated only by the device. That is, even if a new destination is created by the installation data editing tool, the installation data editing tool cannot assign a destination ID to the new destination. Therefore, if the creator wants to use the newly created destination as the value of the destination-related item, the creator cannot set the value "destination ID" required by the device in the destination-related item.
In such cases, the creator cannot edit the destination-related items with the installation data editing tool, so the worker had to edit the destination-related items directly on the device after the initial installation. ..
The present invention is for solving the above-mentioned problems, and even if the destination is newly created by the creator with the installation data editing tool, the creator sets the value of the destination-related item on the installation data editing tool. The purpose is to provide an initial installation system that enables this.

In order to solve the above problems, the information processing system of the present invention has the following features.
An information processing system in which an installation data management device that creates and manages installation data including device setting information and address book information including a first identifier as a destination, and a device that reflects the installation data are connected by a network. The installation data management device issues a second identifier when a new destination is added to the address book information by the creator, and when the creator selects the new destination as the destination. The device has an acquisition means for acquiring the installation data from the installation data management device and an acquisition means for acquiring the installation data by setting the second identifier as a destination and creating the setting information. When the second identifier is set in the setting information of the installation data, the first identifier is issued, and the second identifier of the destination of the setting information is the issued first. It is characterized by having a reflection means for reflecting the installation data on the device by substituting with the identifier of.

Even if the destination is newly created by the creator with the installation data editing tool, the creator can set it as the value of the destination-related item on the installation data editing tool. Therefore, after the initial installation is completed, the worker can complete the initial installation work without directly editing the destination-related items on the device.

Information processing system configuration diagram of the embodiment of the present invention Hardware configuration diagram of installation data management device and multifunction device Software configuration diagram of installation data management device and content management device The figure which shows the software composition of a multifunction device Diagram showing an example of the software configuration and UI of a multifunction device Diagram showing the table configuration managed by the reflection policy storage unit The figure which shows the table structure managed by the installation data management apparatus of an Example. The figure which shows the table structure managed by the installation data management apparatus of an Example. A diagram showing an example of the table configuration and UI managed by the content information storage unit. Figure showing an example of setting information file Diagram showing an example of a script Diagram showing an example of the UI screen of the installation data management device of the embodiment Diagram showing an example of the UI screen of the installation data management device of the embodiment Flow chart of the installation data management device of the embodiment Flow chart of the installation data management device of the embodiment Flowchart of the target machine of the embodiment The figure which shows the example of the UI screen of the installation data management apparatus of another Example. Flowchart of installation data management device of other embodiments Flowchart of installation data management device of another embodiment Flowchart of target machine of another embodiment

1. 1. Hardware configuration
1-1. Overall Configuration of the System Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.
FIG. 1 shows the overall configuration of the information processing system according to the embodiment of the present invention.
The installation data management device 101 creates and manages installation data including setting information. The creator creates installation data using the installation data management device 101. In this embodiment, a set of "setting items" and "setting values" may be referred to as "setting information", and a file of the "setting information file" may be referred to. An address book containing one or more destinations is also part of the setting information. Furthermore, general data used in the initial installation, such as contents such as firmware and setting information files, may be referred to as "installation data".
The content management device 102 manages content such as firmware.
In this embodiment, the installation data management device 101 and the content management device 102 are realized by different devices, but they may be realized in the same device.
The installation data management device 101 and the content management device 102 are connected to the LAN 103 so as to be able to communicate with each other, and are further connected to the Internet 104.
The reference machine 105 is a device for which the initial installation work has been completed, and the target machine 106 is a device for initial installation. In this embodiment, as an example of these devices, a multifunction device having a printing function, a scanning function, a network communication function, and the like is assumed, but the present invention is not limited thereto. In addition, all of these devices are communicably connected to LAN 107 and further connected to Internet 104.
In this embodiment, the installation data management device 101 and the content management device 102 are connected to the Internet 104 via the LAN 103, but each of them is directly connected to the Internet 104. May be good. Similarly, the reference machine 105 and the target machine 106 may be directly connected to the Internet 104 without going through the LAN 107.

1-2. Hardware Configuration of Management Device First, with reference to FIG. 2A, the hardware configuration of the information device on which the program functioning as the installation data management device 101 and the content management device 102 is executed will be described.
The hard disk (HDD) 212 stores the installation data management program according to the present embodiment, which is the main operating body in all the explanations described later.
Unless otherwise specified, the CPU 201 is the main body of execution on the hardware in all the explanations described later. On the other hand, the main body of control on the software is the installation data management program stored in the hard disk (HDD) 212.
The ROM 202 stores the BIOS and the boot program.
The RAM 203 functions as a main memory, a work area, and the like of the CPU 201.
The keyboard controller (KBC) 205 controls instruction input from the keyboard (KB) 209, the pointing device (PD) 210, and the like.
The display controller (DSPC) 206 controls the display of the display (DSP) 211.
The disk controller (DKC) 207 controls access to a storage device such as a hard disk (HDD) 212 or a CD-ROM (CD) 213. The hard disk (HDD) 212, the CD-ROM (CD) 213, and the like store a boot program, an operating system, a database, an installation data management program, a content management program, and their data.
The interface controller (IFC) 208 sends and receives information to and from other network devices via the LAN.
Each of these components is located on the system bus 204.
The installation data management program according to this embodiment may be supplied in a form of being stored in a storage medium such as a CD-ROM. In that case, the program is read from the storage medium by the CD-ROM (CD) 213 or the like shown in FIG. 2A, and is installed in the hard disk (HDD) 212.

1-3. Hardware Configuration of Reference Machine and Target Machine Next, using FIG. 2B, the internal configuration of the multifunction device will be described using the reference machine 105 and the target machine 10 as examples.
The CPU 251 controls the entire multifunction device, and the ROM 252 stores a serial number and the like.
The RAM 253 is used for the work area of the CPU 251, the receive buffer, and the image drawing.
The hard disk (HDD) 254 records firmware, extension programs, font data, and the like.
The operation unit 255 is composed of various switches and buttons, and a liquid crystal display unit for displaying messages.
The network interface 256 is for connecting to a network, and transmits / receives information to / from other network devices via a LAN.
The printer engine 257 prints on recording paper, the scanner 258 reads the document, and the facsimile communication unit 259 sends and receives facsimiles.
Each of these components is located on the system bus 260.

2. 2. Software functional configuration
2-1. Software of the installation data management device Next, the functional configuration of the installation data management program 300 operated by the installation data management device 101 will be described with reference to FIG. 3A.
The following functions are realized by the CPU 201 executing this program.
The UI control unit 301 provides a graphical user interface for the creator to operate the program. The graphical user interface is configured as a Web page that can be displayed on another PC using HTTP (HyperText Transfer Protocol). Alternatively, it may be configured to be displayed on the display 211 provided in the installation data management device 101.
The control unit 302 instructs each function in the installation data management program 300 to perform various processes described later in accordance with the instruction of the UI control unit 301 and the request received by the communication unit 305.
The installation data creation unit 303 generates installation data including setting information according to the instruction of the control unit 302 based on the input information from the UI control unit 301.
The script creation unit 304 creates a script for installation work that can be analyzed by the automatic installation program 450 shown in FIG. 4B (c) based on the installation data generated by the installation data creation unit 303 according to the instructions of the control unit 302. Generate. (Hereinafter, FIGS. 4A and 4B are collectively referred to as "FIG. 4".)
The communication unit 305 receives the request from the target machine 106 and transmits the request content to the control unit 302. Further, the processing result for the request is received from the control unit 302, the response data for the request is created, and the response is transmitted to the request sender. Further, the communication unit 305 controls the HTTP communication, and sends the Web page received from the UI control unit 301 to another PC as needed.
The installation data management unit 306 instructs the installation data storage unit 307 to store, delete, update, and acquire the installation data according to the instruction of the control unit 302.
The installation data storage unit 307 is a database that holds installation data.
The specification management unit 308 instructs the specification storage unit 309 to store, delete, update, and acquire the specification information described later in accordance with the instructions of the control unit 302. The specification information is a file that manages the specifications of all the setting items included in the firmware of the device. The details of the setting specifications will be described later together with FIG. 5 (B), but include an ID for uniquely identifying the setting items, a setting item name, a setting item type, a value range, an initial value, and the like.
The specification storage unit 309 is a database that holds device specification information.

2-2. Software of the content management device FIG. 3B is a diagram showing an example of the functional configuration of the content management program 350 operated by the content management device 102.
Each function is realized by the CPU 201 executing the program.
The UI control unit 351 provides a graphical user interface for the creator to operate the program. The graphical user interface is configured as a Web page that can be displayed on another PC using HTTP (HyperText Transfer Protocol). Alternatively, it may be configured to be displayed on the display 211 provided in the content management device 102.
The control unit 352 instructs each function in the content management program 350 to perform various processes described later in accordance with the instruction of the UI control unit 351 and the request received by the communication unit 354.
The input / output unit 353 receives input / output of contents according to the instruction of the control unit 302.
The communication unit 354 receives the request from the target machine 106 and transmits the request content to the control unit 352. Further, the communication unit 354 receives the processing result for the request from the control unit 352, creates the response data for this request, and sends the response to the request transmission source. Further, the communication unit 354 controls the HTTP communication and, if necessary, transmits the Web page received from the UI control unit 351 to another PC.
The content information management unit 355 instructs the content information storage unit 356 to store, delete, update, and acquire the content according to the instruction of the control unit 352. The content information storage unit 356 is a database operated by the content management device 102.
By executing the program by the CPU 201, the functions of the installation data management device 101 and the content management device 102 are realized. The contents of the data managed by the installation data storage unit 307, the specification storage unit 309, and the content information storage unit 356 will be described later with reference to FIGS. 6A and 6B (hereinafter collectively referred to as “FIG. 6”) and FIG. 7.

2-3. Software of the multifunction device FIG. 4 (a) is a diagram showing an example of the software configuration of the multifunction device.
In the multifunction device software 400 of the multifunction device, the native program 401 of the control program originally provided such as a printer, a fax machine, and a scanner is running on the OS410. In addition, the extended program execution platform 402, which is an extended program execution platform, is also in operation. Further, the firmware update service 403, the function activation service 404, and the setting management service 405 are operating on the native program 401. In addition, the extension program system service 406 and the extension program 407 are running on the extension program execution platform 402.
The firmware update service 403 is a service that provides various functions for updating the firmware. For example, the firmware update service 403 refers to the firmware specified by the creator and determines whether or not the device firmware needs to be updated. Then, the firmware update service 403 updates the firmware via the native program 401.
The function activation service 404 is a service for activating a function pre-installed in the native program 401. The function activation service 404 identifies and activates the function specified by the function license file specified by the worker.
The setting management service 405 is a service for managing various settings such as printers and scanners and setting information such as an address book. The setting management service 405 has a UI, and the operator can instruct the setting change via the operation unit 255 of the multifunction device. In addition, the setting management service 405 also provides a function of rewriting the setting information of the native program 401 when the setting information file in the format described later is specified by the worker. In particular, when rewriting the address book, the setting management service 405 issues at least a new identifier for uniquely identifying the destination in the device, and manages the address book together with the identifier. The details of this operation will be described later together with FIG. Further, the setting management service 405 converts the setting information into a data file and provides it as a setting information file in response to a request from the extension program 407. Requests from extension program 407 to configuration management service 405 are executed through extension program system service 406.
Extension program system service 406 is a utility library commonly used by extension programs and is provided by the system. By calling the function of the extension program system service 406 from the extension program 407, it is possible to save the trouble of developing the extension program.
The extension program 407 can access each module of the multifunction device such as another extension program 407 only through the extension program execution platform 402 or the extension program system service 406. Further, the extension program 407 having a UI can display an icon on the main menu screen displayed on the operation unit 255 of the multifunction device. When the operator selects this icon, the operation unit 255 transmits to that effect to the CPU 251. After that, the CPU 251 displays the UI of the extension program selected by the operator on the operation unit 255.
It should be noted that this software configuration describes only the basic part, and may include other services depending on the implementation environment. In addition, there may be no unnecessary services for reasons such as limiting the settings.

Configuring a functional configuration of the management service configuration management service 405 with reference to FIG. 4 (b), it will be described in detail below.
The designated data analysis unit 421 analyzes the setting information file received by the setting management service 405. Specifically, the serial number, the model name, and the setting information, which are information uniquely identifying the device included in the setting information file, are extracted and temporarily stored in the RAM 253 or HDD 254.
The reflection policy judgment unit 422 uses the serial number and model name of the setting information file extracted by the designated data analysis unit 421 and the serial number and model name of the multifunction device itself, and each setting information in the setting information file is the multifunction device. Judge whether it can be reflected in.
The reflection policy storage unit 423 manages the import condition table 500 and the setting specification management table 510 shown in FIGS. 5A and 5B. The reflection policy refers to a policy for deciding whether or not to import each setting item included in the setting information file into the device.
The reflection unit 424 writes the setting information determined by the reflection policy determination unit 422 to be able to be reflected in the native program 401.

- a functional configuration of an automatic installation program with reference to FIG. 4 (c) while explaining the operation in the automatic installation program MFP. In this embodiment, the automatic installation program 450 is implemented as one of the extension programs 407 of the multifunction device, but may be implemented as one of the native programs 401, for example.
Each function is realized by the CPU 251 executing a program corresponding to each function.
The UI control unit 451 provides a UI for operating the automatic installation program 450 to the operator through the operation unit 255, and accepts the operator's operation.
The communication unit 452 acquires various data from the installation data management device 101 and the content management device 102 via the extended program system service 406 and the network I / F 256. The acquired data includes installation data applied to the multifunction device. Similarly, the communication unit 452 transmits various data to the installation data management device 101 and the content management device 102.
The processing execution unit 453 performs various processes according to the instructions of the UI control unit 451 and the script analysis unit 454.
The script analysis unit 454 analyzes the script included in the installation data acquired by the communication unit 452, and determines the processing and order to be executed by the processing execution unit 453.

FIG. 4 (d) shows an example of the UI screen of the UI control unit 451 of the automatic installation program 450.
The UI screen 470 is the screen that is displayed first after the operator starts the automatic installation program 450 on the device and executes the authentication process as necessary.
A value is input to the input area 471 (installation data ID) of the UI screen 470 in order to uniquely identify the installation data applied to the device by the installation data management device 101.
When the [OK] button 472 is pressed, the automatic installation program 450 sends the value of the input area 471 (installation data ID) to the installation data management device 101. The details of this operation will be described later together with FIG.
When the [Cancel] button 473 is pressed, the UI screen 470 is terminated.

2-4 table
-Tables stored in the multifunction device FIGS. 5 (a) to 5 (c) are examples of tables managed by the reflection policy storage unit 423 and are referenced by the setting management service 405. The table configuration in FIGS. 5A to 5C is an example, and the table configuration may be different from that of this example.
(Import condition table)
The capture condition table 500 shown in FIG. 5A is composed of columns 501 to 502. Here, the import condition is a condition used when deciding whether or not to import each setting item included in the setting information file into the device. In this table, the conditions that can be stored in the column 517 (condition ID) of the setting specification management table 510 described later are listed.
The column 501 (condition ID) is an identifier for uniquely identifying the "condition".
Column 502 (condition) is a condition for determining whether or not the reflection policy determination unit 422 captures the setting information. Here, "serial number match", "model name match", and "no condition" are exemplified as "conditions", but other conditions may be used.

(Setting specification management table)
The setting specification management table 510 shown in FIG. 5B is composed of columns 511 to 517. One record represents one setting information and its specifications.
Column 511 (setting item ID) is an identifier for uniquely identifying the setting item of the device.
Column 512 (setting item name) is a name used when displaying this setting item on the operation unit 255.
Column 513 (type) is the data type of the setting item. Here, "enumeration type" for inputting one of multiple options, "IP address type" for inputting a character string in IP address format, "character string type" for inputting a character string, and destination ID are input. "Destination ID type" and "file type" for inputting a file name are exemplified.
Column 514 (value range) is a range of values that the setting item can take. For example, if column 513 (type) is an "enumerated type", column 514 (value range) stores discrete numbers and predefined constants. When column 513 (type) is "character string type" or "file type", the character string length is stored in column 514 (value range).
It is a column 515 (value display name), and when the column 514 (value range) is an "enumeration type" or a "file type", the name to be displayed in the operation unit 255 is stored. For example, in the first record, since the value of column 513 (type) is "enumerated type", "1,5,10" is stored as column 514 (value range), and each column 515 (value) is stored. The display name) is "1 minute, 5 minutes, 10 minutes". Further, in the fifth record, since the value of column 513 (type) is "file type", "0-256 characters" is stored as the "value range". The specification of column 515 (value display name) is defined to display "yes" when the file name is stored as a value and "none" when nothing is stored.
Column 516 (initial value) stores the initial value of the setting item.
Column 517 (condition ID) stores the import condition of the setting item. The stored value is one of the values of each record in column 501 (condition ID) of the import condition table 500.
When the setting information is reflected in the multifunction device, the reflection policy judgment unit 422 acquires the condition corresponding to the value of "condition" from the column 502 (condition) of the import condition table 500, and whether or not to reflect each setting information. Is determined.

(Address book definition table)
FIG. 5C is an address book definition table 520 for defining the specifications of the destination included in the address book, and is composed of columns 521 to 526. Each record defines a destination attribute.
Column 521 (attribute) stores the attributes of the destination. The destination of this embodiment has a "destination ID", a "destination name", a "destination type", and a "destination value".
Column 522 (type) is a data type of each of the above attributes.
Column 523 (value range) is a range of values that each attribute can take. Since the relationship between the column 522 (type) and the column 523 (value range) is the same as that of the column 513 (type) and the column 514 (value range), the description thereof will be omitted.
The column 524 (value display name) stores the name to be displayed in the operation unit 255 for each listed value when the column 523 (value range) is an enumerated type. For example, in column 521 (attribute) "destination type" (third record), "E", "F", and "I" are stored in column 523 (value range), and the display names of each are stored. Corresponds to "email", "FAX", and "I-FAX".
Column 525 (initial value) stores the initial value of each attribute.
In column 526 (tag name), the tag name described in the address book file 840 described later is stored.
The attribute "destination ID" (first record) is a definition for defining a value issued by the device so that it is unique within the device at least. In this embodiment, a simple value such as "A1" is used, but it is desirable to use, for example, a GUID (Global Unique Identifier).

-Tables stored in the installation data management device Figures 6 (a) to 6 (d) are examples of tables managed by the specification storage unit 309.
(Import condition table)
The import condition table 620 shown in FIG. 6 (a) is the same as the import condition table 500 in FIG.
(Model identification table)
The model identification table 630 shown in FIG. 6B is composed of columns 631 to 633.
Column 631 (model ID) stores an identifier for uniquely identifying the combination of the model name and the firmware version.
The "model name" and "firmware version" are stored in the column 632 (model name) and the column 633 (firmware version), respectively.
By combining the "model name" and the "firmware version", it is possible to uniquely identify the substance of the firmware.

(All setting specification management table)
The all-setting specification management table 650 shown in FIG. 6 (c) is composed of columns 651 to 658. One record represents one setting information. The installation data management device 101 determines the set value of the target machine 106 according to these setting specifications.
In column 651 (model ID), the value of any record of column 631 (model ID) of the model identification table 630 is stored.
Columns 652 to 658 are the same as columns 511 to 517 of the setting specification management table 510 in FIG. The all setting specification management table 650 is the setting specification management table 510 to which the column 651 (model ID) is added. When the installation data management device 101 acquires the setting specification management file from the content management device 102 in the flowchart of FIG. 10 described later, the column 651 (model ID) is added and then stored in the specification storage unit 309.
When the value of column 654 (type) is "destination ID type", the values of column 655 (value range) and column 656 (value display name) are shown in the address book table 660 (FIG. 6 (g)) described later. It will be linked with the stored value. Specifically, the value of column 655 (value range) is the value of column 662 (destination ID) in each record of the address book table 660 or the value of column 666 (temporary destination ID) set as an alternative attribute when there is no destination ID. Is equal to. Further, the value of column 656 (value display name) is equal to the value of column 663 (destination name) in each record of the address book table 660.
In this embodiment, the specification management unit 308 decomposes the specification information into records for each setting information and stores it in the all setting specification management table 650, but even if the substance of the specification information for each model ID is stored as it is. good. Further, only the path to the entity of the specification information for each model ID may be stored. In this case, the entity of the specification information for each model ID is placed as a file in another location.

(All address book definition table)
The all address book definition table 670 shown in FIG. 6 (d) is composed of columns 671 to 677. Each record defines a destination attribute. The installation data management device 101 manages the destination of the target machine 106 according to these address book definitions.
In column 671 (model ID), the value of any record in column 631 (model ID) is stored.
Columns 672 to 677 are the same as columns 521 to 526 of the address book definition table 520 of FIG.
Here, the all address book definition table 670 has a column indicating the model ID and a record indicating the attribute of the temporary destination ID added to the address book definition table 520. The temporary destination ID is set in the installation data management device 101 as an alternative attribute of the destination ID set by the device. When the installation data management device 101 acquires the address book definition file from the content management device 102 in the flowchart of FIG. 10 described later, it adds a column 671 indicating the model ID and a record indicating the attribute of the temporary destination ID, and then the specification storage unit 309. Store in.
In this embodiment, the specification management unit 308 decomposes the address book definition into records for each attribute and stores it in the all address book definition table 670, but stores the actual address book definition for each model ID as it is. You may. Further, only the path to the entity of the address book definition for each model ID may be stored. In this case, the entity of the address book definition for each model ID is placed as a file in another location.

6 (e) to 6 (g) are examples of tables managed by the installation data storage unit 307, which are created and referenced by the installation data management program 300.
(Installation data management table)
The installation data management table 600 shown in FIG. 6 (e) is composed of columns 601 to 607. This table is a table that stores the outline of installation data. One record represents one installation data.
The column 601 (installation data ID) is an identifier given to the installation data when the installation data is generated by the installation data management program 300. The value of this identifier is a unique value for all installation data, and in this example, it is described as a simple value such as "1" for easy understanding, but for example, GUID (Global Unique Identifier) etc. is described. It is desirable to use it.
Column 602 (installation data name) represents the name of the installation data.
Column 603 (model name) represents the model name of the device to which the installation data is applied.
Column 604 (firmware version) represents the firmware version applied to the device.
Column 605 (setting information ID) is an identifier for uniquely identifying the setting information described later.
In this embodiment, one installation data is configured to include only one type of model. Therefore, when installing a plurality of models of devices in the customer environment, the creator creates a plurality of installation data for each model.
Column 606 (script) stores the script created by the installation data management device 101. In this embodiment, it is assumed that the script entity is stored in the column 606, but only the path to the script entity may be stored in the column 606. In this case, the script entity is configured to be placed as a file in another location.
Column 607 (processing result) stores the result of processing the script stored in column 606 by the target machine 106. A file of the processing result may be stored.

(Setting information management table)
The setting information management table 610 shown in FIG. 6 (f) is composed of columns 611 to 617. One record represents the setting information for one installation data.
Column 611 (setting information ID) is an identifier for uniquely identifying the setting information. The value of any record in this column is stored in the above-mentioned column 605 (setting information ID).
Columns 613 to 617 list examples of setting information. The setting information is not limited to the one illustrated here.
The column 616 stores the value of the column 662 (destination ID) or the column 666 (temporary destination ID) of the address book table 660 described later. When the value of column 666 (temporary destination ID) is stored, "tmp:" indicating that it is a temporary destination ID is added before the value. For example, the value of the first record in column 616 is "tmp: 1", and it can be seen that the value is a temporary destination ID of "1".
In column 617 (address book ID), the value of column 661 (address book ID) of the address book table 660 described later is stored.
Here, the setting information IDs of the setting items are assigned to each column after column 613 of the table, but the substance of the setting information file created in the format as shown in FIGS. 8A (a) and 8A (b) described later. It may be configured to store. (Hereinafter, FIGS. 8A and 8B are collectively referred to as “FIG. 8”.) Further, the path to the entity may be stored instead of storing the entity. In this case, the entity will be placed as a file in another location.

(Address book table)
FIG. 6 (g) is an address book table 660, which is composed of columns 661 to 666. One record represents one destination.
Column 661 (address book ID) is an identifier for uniquely identifying the address book. The value of any record in this column is stored in the above-mentioned column 617 (Address).
The column 662 (destination ID) is an identifier given to the destination by the device when a new destination is added to the device, and is at least a unique value within the device. In this example, a simple value such as "A1" is used for easy understanding, but it is desirable to use, for example, a GUID (Global Unique Identifier). The specification of "destination ID" that can be stored in this column is defined in the first record (record whose attribute is "destination ID") of all address book definition table 670.
Column 663 (destination name) represents the display name of the destination. The specification of the destination name that can be stored in this column is defined in the second record (record whose attribute is "destination name") in the all address book definition table 670.
Column 664 (destination type) represents what kind of destination the value stored in the "destination value" of column 665 is. The specification of the destination type that can be stored in this column is defined in the third record (record whose attribute is "destination type") in the all address book definition table 670.
Column 665 (destination value) stores the value of the destination according to the destination type stored in the "destination type" of column 664. The specification of the destination value that can be stored in this column is defined in the 4th record (record whose attribute is "destination value") of all address book definition table 670.
In column 666 (temporary destination ID), when a new destination is added on the installation data management device 101, the installation data management device 101 does not store the identifier in the "destination ID" of column 662, but temporarily stores the identifier. Issue and store in this column. The value of column 666 (temporary destination ID) is unique at least within the installation data management device 101. The specifications of the destination ID that can be stored in this column are defined in the fifth record (record whose attribute is "temporary destination ID") in the all address book definition table 670.
The address book table 660 is filed by the installation data management device 101 for each "address book ID", and the file name is stored in the column 617 (Address).

2-4. Table stored in the content management device FIG. 7A is an example of a table managed by the content information storage unit 356 of the content management device. The table configuration of FIG. 7A is an example, and the table configuration may be different from that of the present embodiment.
(Firmware management table)
The firmware management table 700 is a table that stores information about the firmware, and is composed of columns 701 to 704. One record represents one firmware information.
For column 701 (model name), a model to which the firmware registered in the firmware management table 700 can be applied is specified.
The column 702 (firmware version) stores the version information of the firmware registered in the column 703 (firmware).
The column 703 (firmware) stores the actual firmware registered in the content management device 102.
Column 704 (specification information) stores the substance of the specification information registered in the content management device 102 and the substance of the address book definition. The substance of the specification information is a file of the setting specification management table 510 shown in FIG. 5 (B). The substance of the address book definition is a file of the address book definition table 520 shown in FIG. 5 (C). Hereinafter, a file of specification information is referred to as a specification information file. A file of the address book definition is called an address book definition file. In the example of FIG. 7A, the specification information file and the address book definition file are zipped like "Specification 1_100.zip" and combined into one file.
In this embodiment, it is assumed that the firmware is stored in column 703, the entity of the specification information file and the entity of the address book definition file are stored in column 704, but only the path to each entity is stored in each column. You may. In this case, each entity is placed as a file in a different location.

・ UI (content management)
7 (b) and 7 (c) are examples of UI screens of the UI control unit 351 of the content management program 350.
The values of column 701 (model name) and column 702 (firmware version) of the firmware management table 700 are displayed in column 721 (model name) and column 722 (firmware version) of the firmware list screen 720 in FIG. 7 (b), respectively. Will be done.
When the [Add] button 723 is pressed by the creator, the addition screen 740 (FIG. 7 (c)) is displayed.
When the [Delete] button 724 is pressed by the creator to select an arbitrary line in the firmware list, the data of the corresponding record in the firmware management table 700 is deleted.
When the [Exit] button 725 is pressed by the creator, the UI control unit 351 exits the firmware list screen 720.

Figure 7 (c) shows the additional screen 740.
In the firmware file input area 741, the file path of the actual firmware to be added to the content management device 102 by the creator is input. Something like a file reference dialog display button (not shown) may be provided to facilitate input. In this embodiment, it is assumed that the firmware specified in the firmware file input area 741 includes the specification information and the address book definition, but they may be different. In that case, an input area for inputting the specification information and the file path of the address book definition is provided on the additional screen 740.
When the [OK] button 742 is pressed by the operator, the content management program 350 adds the firmware specified in the firmware file input area 741 to the firmware management table 700. At that time, specify the firmware model name and firmware version from the firmware attribute information, etc., and set them in column 701 (model name) and column 702 (firmware version). Further, the firmware is registered in the column 703 (firmware), and the specification information and the address book definition included in the firmware are taken out and registered in the column 704 (specification information). After that, the additional screen 740 is closed.
When the [Cancel] button 743 is pressed, the edited result of the additional screen 740 is discarded, and the additional screen 740 ends.
-Setting information file FIGS. 8 (a) and 8 (b) are diagrams illustrating the setting information file handled in this embodiment.
FIG. 8A shows an example of the XML format setting information file 800.
The control information area 801 includes a model name (<Model> tag), a firmware version (<FWV> tag), and a serial number (<SN> tag).
The setting information area 802 enumerates the setting information to be set in the device. In this embodiment, each tag name of the setting information is defined to be the same as the value of the "setting item ID" in columns 511 and 652. For example, the tag that stores the file name of the address book file 840 described later is expressed as (<Address> tag).
In this example, the transmission destination (<Destination>) of the data to be set is used as one example, but if multiple destinations are required depending on the type of data to be transmitted, the destinations are correspondingly. An area (tag) may be provided. In this embodiment, the data file is expressed in XML (Extensible Markup Language) format, but may be expressed in JSON (JavaScript Object Notation) format, for example.

FIG. 8B shows an example of the setting information file. This is a setting information file created specifically for the address book, and is called an "address book file". This is an example of the address book file 840 in XML format.
The destination areas 841 to 843 are portions enclosed in <Address> tags and represent individual destinations as a whole. In this figure, the destination ID (<AdID> tag), destination name (<AdName> tag), destination type (<AdType> tag), destination value (<AdValue> tag), and temporary destination ID are set in the destination areas 841 to 843. Each attribute of (<TmpAdID> tag) is stored. Each attribute corresponds to columns 662 to 666 of the address book table 660.
In this embodiment, the data file is expressed in XML (Extensible Markup Language) format, but may be expressed in JSON (JavaScript Object Notation) format, for example.
In this embodiment, the setting information file 800 and the address book file 840 are collectively referred to as a "setting information file".

-Installation process script Figure 8 (c) is an example of a script that describes the installation procedure for automatically executing the installation process of the target machine 106.
The script 820 is acquired by the communication unit 452 of the automatic installation program 450, and is analyzed by the script analysis unit 454 via the processing execution unit 453. The script 820 analyzed by the script analysis unit 454 is subsequently executed by the process execution unit 453. The script 820 is described in XML format, and is composed of an installation data identification unit 821, a model identification unit 822, and a processing description unit 830. Although the script is expressed in XML format in this figure, the script is not limited to this and may be written in a shell script or the like.
The installation data identification unit 821 is composed of a <setupID> tag, and an installation data ID for identifying the installation data is described. The same value as the "installation data ID" of column 601 of the installation data management table 600 is described.
The model identification unit 822 is composed of a <Model> tag, and the model name for identifying the model of the target machine 106 to be installed is described. The value of "model name" of column 603 of the installation data management table 600 is described.
The processing description unit 830 describes the processing group required for the installation processing. The processing description unit 830 is composed of a firmware update processing unit 831, a setting information processing unit 832, and a restart processing unit 833. The order attribute is included in the tag indicating each process. The order attribute specifies the order of processing.
The firmware update processing unit 831 is a process for updating the firmware via the firmware update service 403. This processing unit defines the processing by describing the <updateFirmwareCommand> tag, and specifies the path to the server where the actual firmware exists by the <path> tag. Furthermore, the firmware version is specified in the <firmwareVersion> tag.
The setting information processing unit 832 is a process of changing the setting information of the device via the setting management service 405. This processing unit defines the process by describing the <deviceConfigCommand> tag, and specifies the value of "setting information ID" in column 605 of the setting information file to be applied to the target machine 106 by using the <confFileID> tag.
The reboot processing unit 833 is composed only of the <rebootCommand> tag, and is a process for restarting the device and reflecting the setting information on the device after the entire installation process is completed.
The description of the script shown in this figure does not limit the processing required for installing the device, and the processing may be duplicated or increased or decreased as necessary.

・ UI screen (setting information, editing address book)
(A) to (e) of FIGS. 9A and 9B are examples of UI screens of the UI control unit 301 of the installation data management program 300 (hereinafter, FIGS. 9A and 9B are collectively referred to as “FIG. 9”). ..
A list of installation data is displayed on the list screen 900 of FIG. 9A. The list of installation data consists of column 901 (installation data ID), column 902 (installation data name), column 903 (model name), and column 904 (firmware version). The values of column 601, column 602, column 603, and column 604 of the installation data management table 600 are displayed, respectively.
When the [New] button 905 is pressed by the creator, the edit screen 920 (FIG. 9 (b)) is displayed.
The [Edit] button 906 displays the edit screen 920 when the creator selects an arbitrary line in the installation data list (list consisting of columns 901 to 904) and presses this button. At that time, the UI control unit 301 acquires information related to the installation data selected from the installation data management table 600 and the setting information management table 610 and displays it on the edit screen 920. Further, when the installation data includes the setting information file, the UI control unit 301 acquires the setting information ID and the setting information file and temporarily holds the setting information file in the installation data storage unit 307.
When the creator selects an arbitrary row in the installation data list and presses this button, the [Delete] button 907 is a record associated with the installation data ID from the installation data management table 600 and the setting information management table 610. Is deleted.
When the [Exit] button 908 is pressed, the UI control unit 301 exits the list screen 900.

The edit screen 920 of FIG. 9B has an input area 921 (installation data name), an input area 922 (model name), and an input area 923 (firmware version). When both the input area 922 (model name) and the input area 923 (firmware version) are input, each item of the button 924,926,928,929 and the input area 925 is activated.
The [New] button 924 can be pressed when "None" is displayed in the area 927. When this button is pressed, the setting information editing screen 940 (FIG. 9 (c)) is displayed. At this time, the initial value of each setting item displayed on the setting information editing screen 940 is determined by referring to each table of the specification storage unit 309. Details will be described later.
In the file specification area 925, enter the actual file path of the setting information file acquired by the creator from the reference machine 105. There may be something like a file reference dialog display button (not shown) to facilitate input.
When the [Read] button 926 is pressed, the setting information file specified in the file specification area 925 is read and temporarily held in the installation data storage unit 307.
In the area 927 that displays the presence / absence of the setting information file, when the setting information file is read and temporarily held in the installation data storage unit 307, "Yes" is displayed in this area. Also, if the installation data selected on the list screen 900 includes the setting information file from the beginning, "Yes" is displayed in this area. Otherwise, "None" is displayed.
The [Edit] button 928 can be pressed only when "Yes" is displayed in the area 927. When the creator presses this button, the setting information edit screen 940 is displayed. At this time, the setting value of the setting information file temporarily held in the installation data storage unit 307 is applied to the initial value of each setting item displayed on the setting information editing screen 940. Details will be described later.
When the [Delete] button 929 is pressed, the setting information file temporarily held in the installation data storage unit 307 is deleted, and "None" is displayed in the area 927.
When the [OK] button 930 is pressed, the installation data management program 300 generates a script that can be analyzed by the automatic installation program 450, and stores the edited result in each table of the installation data storage unit 307. After that, the edit screen 920 is closed.
When the [Cancel] button 931 is pressed, the editing result of the editing screen 920 is discarded and the editing screen 920 is terminated.

The setting information editing screen 940 of FIG. 9 (c) has an input area 941 (sleep transition time), an input area 942 (IP address), an input area 943 (installation location), and an input area 944 (destination). A check box is added to the beginning of each setting item, and the creator can select the setting item that he / she wants to apply to the target machine 106.
In the area 945 for displaying the presence / absence of the address book, if the setting information file includes the address book, "Yes" is displayed in this area.
The [New] button 946 can be pressed only when the value of the area 945 is "None". When the creator presses this button, the address book management screen 960 is displayed in the initial state.
The [Edit] button 947 can be pressed only when the value of the area 945 is "Yes". When the creator presses this button, the address book management screen 960 (Fig. 9 (d)) is displayed. At that time, the UI control unit 301 acquires the destination information from the address book table 660 and displays it on the address book management screen 960.
When the [Delete] button 948 is pressed, all the records in the address book table 660 are deleted, and "None" is displayed in the area 945.
When the [OK] button 949 is pressed, the installation data management program 300 temporarily holds the edited result in the installation data storage unit 307. After that, the setting information editing screen 940 is closed.
When the [Cancel] button 950 is pressed, the edited result of the setting information editing screen 940 is discarded and the setting information editing screen 940 is closed.

A list of address books is displayed on the address book management screen 960 of FIG. 9 (d). The address book list consists of column 961 (destination ID), column 962 (destination name), column 963 (destination type), column 964 (destination value), and column 965 (temporary destination ID). Among the values of column 662, column 663, column 664, column 665, and column 666 of the address book table 660, the value of the record related to the setting information to be edited is displayed. For example, when the setting information of the first record of the setting information management table 610 is the editing target, the value of the column 617 (Address) is "AB01". The address book management screen 960 displays the value of the record in which the value of column 661 (address book ID) is "AB01" in the address book table 660.
When the creator presses this button, the [Add] button 966 displays the destination edit screen 980.
The [Edit] button 967 displays the destination edit screen 980 when the creator selects an arbitrary line in the address book list (list consisting of 961 to 965) and presses this button. At that time, the UI control unit 301 acquires information about the selected destination from the address book table 660 and displays it on the destination edit screen 980.
When the creator selects an arbitrary line in the address book list and presses this button, the [Delete] button 968 deletes the destination selected from the address book list on the address book management screen 960.
When the [OK] button 969 is pressed, the installation data management program 300 temporarily holds the edited result of the address book in the installation data storage unit 307. After that, the address book management screen 960 is closed.
When the [Cancel] button 970 is pressed, the installation data management program 300 discards the edited result of the address book management screen 960 and exits the address book management screen 960.

The destination edit screen 980 of FIG. 9E has an input area 981 “destination name”, an input area 982 (destination type), and an input area 983 (destination value).
When the [Add] button 966 of the address book management screen 960 is pressed to display this screen, the values in column 676 (initial value) of the all address book definition table 670 are displayed in the input areas 981 to 983. .. When the [Edit] button 967 on the address book management screen 960 is pressed to display this screen, the values in columns 663 to 665 of the address book table 660 are displayed in the input areas 981 to 983. Since column 662 (destination ID) is a value that can be generated / changed only by the device, it is not displayed on the destination edit screen 980. Further, since the column 666 (temporary destination ID) is also a value that can be generated / changed only by the installation data editing device 101, it is not displayed on the destination editing screen 980.
The specifications of the values that can be entered in the input area 981 (destination name), input area 982 (destination type), and input area 983 (destination value) follow the contents of the corresponding records in the all address book definition table 670.
When the [OK] button 984 is pressed, the installation data management program 300 temporarily holds the edited result of the destination in the installation data storage unit 307. After that, the destination edit screen 980 is closed.
When the [Cancel] button 985 is pressed, the installation data management program 300 discards the edited result of the destination edit screen 980 and exits the destination edit screen 980.

2-5. Installation data creation process Next, the installation data creation process will be described with reference to the flowcharts of FIGS. 10 and 11.
First, when the creator starts the installation data management program 300 in order to create the installation data and register it in the installation data management device 101, the list screen 900 (FIG. 9A) is displayed. Further, when the [New] button 905 or the [Edit] button 906 is pressed on this screen, the installation data management device 101 displays the edit screen 920 (FIG. 9 (b)). Here, when the creator inputs appropriate values in the input area 922 (model name) and the input area 923 (firmware version) and presses the [New] button 924 or the [Edit] button 928, the installation data management device 101 The flowchart of FIG. 10 is executed. Hereinafter, the values input to the input area 922 (model name) and the input area 923 (firmware version) are referred to as device information.
In the S1001, the installation data creation unit 303 acquires the specification information file (setting information file, address book file) corresponding to the device information from the content management device 102.
Specifically, the installation data creation unit 303 transmits a specification information acquisition request to the communication unit 354 of the content management device 102 via the communication unit 305. The control unit 352 receives this request via the communication unit 354, and acquires the specification information file from the content information storage unit 356 via the content management unit 355. After that, the control unit 352 returns the specification information file to the communication unit 305 via the communication unit 354. When the installation data creation unit 303 receives the specification information file via the communication unit 305, the installation data creation unit 303 passes the specification information to the specification management unit 308. The specification management unit 308 registers the model name and firmware version in the model identification table 630 of the specification storage unit 309. After that, the specification management unit 308 registers the specification information in the all setting specification management table 650 and the all address book definition table 670 using the value of the assigned column 631 (model ID).

In the S1002, the UI control unit 301 uses the specification information file to set the setting information editing screen 940 (Fig. 9 (c)), address book management screen 960 (Fig. 9 (d)), and destination editing screen 980 (Fig. 9 (e)). ) Is created. Specifically, the UI control unit 301 acquires the value of column 631 (model ID) corresponding to the device information from the model identification table 630, and has all the records having that value as the value of column 651 (model ID). Extract from management table 650.
Next, each setting information is displayed on the setting information editing screen 940 using the values of column 653 (setting item name), column 654 (type), and column 655 (value range) in the record. For example, column 653 (setting item name) is used to display the item name of the setting information. Column 654 (type) is used to verify whether the setting value entered by the creator matches the type of the setting information. Column 655 (value range) is used to verify whether the set value entered by the creator is within the range of the setting information.
Similarly, the UI control unit 301 arranges each setting information on the address book management screen 960 and the destination editing screen 980 using the all address book definition table 670.
Here, in particular, as an example in which the all setting specification management table 650 and the address book table 660 are linked, the operation when the "destination ID type" is included as the value of the column 654 (type) will be described. In the setting item of the setting information edit screen 940, the input area 944 (destination) is the "destination ID type". When the value of column 654 (type) is "destination ID type", the UI control unit 301 sets the values of column 662 (destination ID) and column 666 (temporary destination ID), which are column 655 (value range), in the address book. Get from table 660. Here, "A1", "A2" (or more, the value of column 662 (destination ID)), "1" (or more, the value of column 666 (temporary destination ID)) are acquired. As described in the description of the setting information management table 610 of FIG. 6 (f), "tmp:" is added to indicate that the value of the column 666 (temporary destination ID) is the temporary destination ID. Also, the value of column 663 (destination name) is acquired as column 656 (value display name). Here, "customer A", "administrator A", and "service person in charge" are acquired. Finally, the input area 944 (destination) is represented by a drop-down list in which these three options can be selected.

In the S1003, the installation data creation unit 303 determines whether or not the setting information file temporarily held in the installation data storage unit 307 exists.
If it is determined that the setting information file has been read, proceed to S1004.
If not, proceed to S1007.
In the S1004, the installation data creation unit 303 reads the setting information from the setting information file and determines whether or not the setting information exists in the specification information file.
The setting information file 800 will be described as an example. The installation data creation unit 303 acquires the value of the column 631 (model ID) that matches the device information from the model identification table 630. Next, the installation data creation unit 303 reads the setting information from the setting information area 802. Here, it is assumed that the read setting information is the <SleepTime> tag and its value "10". In the installation data creation unit 303, there is a record in the all setting specification management table 650 in which the value of column 631 (model ID) and the model ID match, and the column 652 (setting item ID) matches the tag name "SleepTime". Determine if it is.
The installation data creation unit 303 executes the same processing for the address book file 840 by using the all address book definition table 670.
If it is determined that the setting information contained in the setting information file 800 or the address book file 840 exists in the specification information file, the process proceeds to S1005.
If not, proceed to S1007.

In S1005, the UI control unit 301 generates the setting value for UI display from the setting information read by the installation data creation unit 303 in S1004. Here, the <Destination> tag of the setting information file 800 and its value "tmp: 1" are taken as an example.
First, the UI control unit 301 acquires the value of the column 631 (model ID) that matches the device information from the model identification table 630. Next, a record having that value as the value of column 651 (model ID) and whose column 652 (setting item ID) matches the tag name "Destination" is selected from the all setting specification management table 650. Since the column 654 (type) in the selected record is the "destination ID type", the UI control unit 301 sets the value "tmp: 1" of the <Destination> tag to the column 662 (destination ID) or column of the address book table 660. Search from 666 (temporary destination ID). As a result, the third record in the address book table 660 matches. Therefore, the UI control unit 301 takes out the value of column 663 (destination name) as the setting value for UI display and generates the "service person in charge". After that, the UI control unit 301 reflects the set value generated on the setting information editing screen 940.
The installation data creation unit 303 also uses the address book definition table 670 for the address book file 840 to generate setting values for UI display. After that, the UI control unit 301 reflects the set values generated on the address book management screen 960 and the destination edit screen 980.
In the S1006, the UI control unit 301 determines whether or not the setting item whose value is not reflected exists in the setting information editing screen 940, the address book management screen 960, and the destination editing screen 980.
If there is a blank setting item, proceed to S1007.
If not, proceed to S1008.

In the S1007, the UI control unit 301 reads out the initial value of the setting information whose value is not reflected on the screen from the specification information file. In addition, the setting value for UI display is generated from the read initial value, and the generated setting value is reflected on the corresponding screen. Specifically, the UI control unit 301 acquires the value of the device information column 631 (model ID) from the model identification table 630. Next, the record having the value as the value of the column 651 (model ID) is extracted from the all setting specification management table 650 or all the address book definition table 670. Finally, the initial value for UI display is generated using the value of each record in each column required for UI display.
By executing these steps, the installation data management device 101 can generate a UI screen and display the value or the initial value described in the setting information file as the value of each setting item.
This is the end of the explanation of this flowchart.

Now, when the creator executes the editing process of the setting information on the various editing screens generated by executing the flowchart of FIG. 10, the installation data management device 101 executes the flowchart of FIG.
In the S1101, the UI control unit 301 determines whether or not the editing is performed by the creator on the setting information editing screen 940, the address book management screen 960, and the destination editing screen 980.
If it is determined that editing has been performed, proceed to S1102.
If not, proceed to S1108.
In S1102, the UI control unit 301 determines whether or not a new destination has been added on the destination edit screen 980. When a value is input to the input area 981 (destination name), input area 982 (destination type), and input area 983 (destination value) by the creator and the [OK] button 984 is pressed, the destination is set to the UI control unit 301. Determine that it was newly added.
If it is determined that a new destination has been added, the process proceeds to S1103.
If not, proceed to S1104.
In S1103, the installation data creation unit 303 issues a temporary destination ID to the destination added in S1102. After that, it returns to S1101 and the editing work on various editing screens is continued.
In S1104, the UI control unit 301 refers to the all setting specification management table 650 and determines whether or not the setting item whose value in the column 654 (type) is the "destination ID type" has been edited. For example, on the setting information editing screen 940, it can be seen that the type of the column 944 (destination) is the "destination ID type" by referring to the all setting specification management table 650 of FIG.
If it is determined that the setting item (for example, column 944 (destination)) that is the “destination ID type” has been edited, the process proceeds to S1105.
If not, return to S1101 and continue editing work on various editing screens.
In S1105, the UI control unit 301 determines whether or not the destination ID is assigned to the destination selected in the setting item edited in S1104.
By the processing of S1002 and S1005 in FIG. 10, "customer A", "administrator A", and "service person in charge" are displayed in the input area 944 (destination). When the creator selects "customer A" or "administrator A", the values are "A1" and "A2", so that it can be determined that the destination ID is assigned. On the other hand, when "service person in charge" is selected, the value is "tmp: 1", so it can be determined that the temporary destination ID is assigned.
If it is determined that the destination ID is assigned, the process proceeds to S1106.
If not, proceed to S1107.
In S1106, the UI control unit 301 holds the value of the destination ID of the destination selected in the setting item edited in S1104 as the value of the setting item.
In S1107, the UI control unit 301 holds the value of the temporary destination ID of the destination selected in the setting item edited in S1104 as the value of the setting item. At that time, the value obtained by adding "tmp:" to the temporary destination ID is retained to indicate that it is a temporary destination ID.

In S1108, the UI control unit 301 determines whether or not the [OK] button 949 is pressed. If it is determined that the [OK] button 949 is pressed, the process proceeds to S1110.
If not, proceed to S1109.
In S1109, the UI control unit 301 determines whether or not the [Cancel] button 950 has been pressed.
When it is determined that the [Cancel] button 950 is pressed, the UI control unit 301 discards the editing results of the setting information editing screen 940 and the destination editing screen 980, and exits the setting information editing screen 940.
If not, return to S1101 and continue editing work on various editing screens.
In S1110, the UI control unit 301 acquires the setting information and the destination input to various edit screens by the creator. On the setting information management screen 940, the setting item name and setting value of the setting information for which the check box is selected ON are acquired.
In S1111, the installation data creation unit 303 receives the setting information of S1110 from the UI control unit 301. It then uses the device information to create files such as configuration information file 800 and address book file 840. In order for the installation data creation unit 303 to create the setting information file 800, the installation data creation unit 303 acquires the value of the column 631 (model ID) corresponding to the device information from the model identification table 630. Next, the record having the value as the value of the column 651 (model ID) is extracted from the all setting specification management table 650. A record whose value in column 653 (setting item name) of the record matches the setting item name in the setting information of S1110 is described in the setting information file 800 from column 655 (value range) and column 656 (value display name). Derive the set value to be. Further, the value of the column 652 (setting item ID) is acquired, and the tag name to be described in the setting information file 800 is determined. Furthermore, the model name and firmware version values are acquired from the device information and used as the values of the <Model> tag and <FWV> tag.
In order for the installation data creation unit 303 to create the address book file 840, the value of column 631 (model ID) is acquired in the same manner as above. Next, the record having that value as the value of column 671 (model ID) is extracted from all the address book definition table 670. Records whose value in column 672 (attribute) of the record matches the setting item name in the setting information of S1110 should be described in the address book file 840 from column 674 (value range) and column 675 (value display name). Derive the set value. In addition, the value of column 677 (tag name) is acquired, and the tag name to be described in the address book file 840 is determined.
The created setting information file is temporarily held in the installation data storage unit 307.
This is the end of the explanation of this flowchart.
After executing this flowchart, the UI control unit 301 displays the edit screen 920. When the [OK] button 930 is pressed here, the installation data creation unit 303 inputs the information input to the edit screen 920 and various edit screens to the installation data management table 600 and the setting information management table 610 via the installation data management unit 306. Register with. If the setting information ID is temporarily stored in the installation data storage unit 307 when the [Edit] button 906 is pressed, the installation data creation unit 303 registers the setting information file in the record matching the ID. If not, create a new record in the setting information management table 610 and register the setting information file.
Further, the UI control unit 301 passes the information input to the various edit screens and the edit screen 920 by the creator to the script generation unit 304, and requests the generation of the script as shown in FIG. 8 (c). When creating the <deviceConfigCommand> tag of the setting information processing unit 832, the script generation unit 304 describes the corresponding value of the column 611 (setting information ID) in the <confFileID> tag.
After that, the installation data creation unit 303 receives the script from the script creation unit 304 and registers it in the column 606.

2-5 Automatic installation process (target machine)
When the initial installation of the target machine 106 is performed using the installation data created by executing the flowcharts of FIGS. 10 and 11, the target machine 106 executes the flowchart of FIG. 12.
When the automatic installation program 450 is started on the target machine 106, the UI screen 470 is displayed. When the [OK] button 472 is pressed with the installation data ID input in the installation data ID input area 471 on this screen, S1201 is executed.
In S1201, the processing execution unit 453 transmits a script acquisition request to the installation data management device 101 via the communication unit 452 together with the value of the installation data ID. Further, the communication unit 452 receives the script returned from the installation data management unit 101 and passes it to the script analysis unit 454. Further, the script analysis unit 454 analyzes the script and passes it to the processing execution unit 453. For example, the initial installation process described in script 820 is (1) firmware update process, (2) setting information processing, and (3) restart process. Looking at the order attribute of each process, it can be seen that the process order is (1), (2), (3). Further, in (2) setting information processing, the value of the setting information ID is "S001".
In S1202, the processing execution unit 453 determines whether or not the setting information processing is included in the script analysis result of S1201.
If it is determined that the setting information processing is included, proceed to S1203.
If not, proceed to S1209.
In S1203, the processing execution unit 453 transmits a setting information acquisition request to the installation data management device 101 via the communication unit 452 together with the value of the setting information ID. In the example of script 820, the value of the setting information ID is "S001". The installation data management device 101 identifies the setting information from the setting information ID, converts it into a file, and returns it. The communication unit 452 receives the setting information file returned from the installation data management unit 101 and temporarily holds it in the RAM 253 or HDD 254.

In S1204, the processing execution unit 453 determines whether or not the address book file 840 is included in the setting information file acquired in S1203.
If it is determined that the address book is included, proceed to S1205. If not, proceed to S1209.
In S1205, the processing execution unit 453 determines whether or not there is a destination for which a temporary destination ID is set in the address book file 840. Specifically, the processing execution unit 453 examines the <TmpAdID> tag of each destination of the address book file 840, and determines whether or not any value is contained. In the case of the address book 840 of FIG. 8 (b), since the value of the <TmpAdID> tag of the destination 843 is "1", it can be seen that the temporary destination ID is set.
If it is determined that a destination for which a temporary destination ID is set exists, the process proceeds to S1206.
If not, proceed to S1209.
In S1206, the processing execution unit 453 issues a destination ID to the above destination, and sets the destination ID for the corresponding destination in the address book file 840. Further, the processing execution unit 453 associates the issued destination ID with the temporary destination ID. Here, it is assumed that "A3" is issued as the destination ID. In this case, the processing execution unit 453 sets the value "A3" in the <AdID> tag of the destination 843 of the address book file 840. In this way, the association between the temporary destination ID and the destination ID for each destination can be confirmed by examining the <TmpAdID> tag and the <AdID> tag of each destination in the address book file 840.
In S1207, the processing execution unit 453 detects a destination ID type setting item from the setting information file 800, and determines whether or not a temporary destination ID is set as the value. Specifically, the processing execution unit 453 confirms the specifications of the setting items included in the setting information area 802 on the setting specification management table 510. As a result, it can be seen that the value of the <Destination> tag is the destination ID type. Next, the processing execution unit 453 acquires the value "tmp: 1" of the <Destination> tag. This value includes "tmp:" indicating that it is a temporary destination ID. Therefore, the process execution unit 453 can determine that the setting information file 800 includes a setting item having a temporary destination ID as a value.
If it is determined that the setting item for which the temporary destination ID is set exists, the process proceeds to S1208.
If not, proceed to S1209.

In S1208, the processing execution unit 453 replaces the value of the setting item detected in S1207 according to the association generated in S1206. Specifically, the processing execution unit 453 replaces the value "tmp: 1" of the <Destination> tag in the setting information file 800 with "A3". Here, the value "A3" is the value of the <AdID> tag of the destination in which the value of the <TmpAdID> tag of the address book file 840 is "1". Here, when the processing execution unit 453 confirms the value of the <TmpAdID> tag for each destination, "tmp:" indicating that it is a temporary destination ID and "1" removed must be used.

In S1209, the process execution unit 453 executes various processes using the script analysis result of S1201. In this embodiment, three processes of (1) firmware update process, (2) setting information processing, and (3) restart process are executed.
(1) Firmware update process In the firmware update process, the process execution unit 453 acquires the model name described in the <Model> tag and the value of the firmware version described in the <firmwareVersion> tag. After that, a firmware acquisition request is transmitted to the content management device 102 via the communication unit 452 together with these values. Further, the communication unit 452 receives the firmware returned from the content management device 102 and holds it in the RAM 253 or the HDD 254. After that, the processing execution unit 453 calls the firmware update service 403 to update the firmware.
(2) Setting information processing In the setting information processing, the processing execution unit 453 passes the setting information file to the setting management service 405 via the extension program system service 406. The setting management service 405 rewrites the setting information of the native program 401.
Taking the <IP Address> tag of the setting information file 800 as an example, the process of rewriting the setting information by the setting management service 405 will be specifically described.
First, as described in the explanation of FIG. 4B, the designated data analysis unit 421 of the setting information service 405 analyzes the setting information file and extracts the serial number and the model name. In addition, the <IP Address> tag is extracted as an example of setting information.
The reflection policy determination unit 422 acquires the serial number and model name of the target machine 106 via the native program 407 and compares them with the serial number and model name. That is, it compares which of the conditions "serial number match", "model name match", and "no condition" registered in the setting specification management table 510 is satisfied. For example, when the serial number and the model name match, all the conditions of "serial number match", "model name match", and "no condition" are satisfied. If the serial numbers do not match and the model names match, the comparison results are "model name match" and "no condition". Assuming that the serial number and the model name match in this embodiment, it can be seen from the import condition table 500 that the values of the condition ID 501 are "1", "2", and "3". This indicates that the reflection unit 424 can reflect the setting information in which the column 517 (condition ID) of the setting specification management table 510 is "1", "2", "3".
On the other hand, in this embodiment, since each tag name of the setting information file 800 is the same as the value of column 511 (setting item ID), the reflection unit 424 uses the tag name "IPAddress" as a key in the setting specification management table. 510 can be searched. When the record whose setting item ID 511 is "IPAddress" is searched, the reflection unit 424 detects the second record. The value of the condition ID 517 of this record is "1". In this embodiment, the setting information in which the value of the column 517 (condition ID) is "1" is written in the native program 401. That is, the value "1.2.3.4" set in the <IP Address> tag of the setting information file 800 is written to the native program 401.
(3) Restart process Finally, the process execution unit 453 executes the restart process and reflects the changed settings on the target machine 106.

Next, in S1210, the processing result of S1209 is transmitted to the installation data management device 101. The installation data management device 101 stores the received processing result in the processing result 607.
If the destination ID issued by the device can also be used by another device such as a GUID, the address book information in which the temporary destination ID is replaced with the destination ID issued by the device is also transmitted to the installation data management device. This is the end of the explanation of this flowchart.
By executing S1103 and S1107 in the above flowchart, the installation data management device 101 can set the newly added destination on itself as the destination-related item.
Further, by executing S1206 and S1208, the target machine 106 can reflect the setting information file including the destination-related items to which the destination newly added by the installation data management device 101 is set. ..

In the first embodiment, the process when the creator newly adds a destination to the address book on the installation data management device and then sets the destination as the value of the destination-related item is described.
In this embodiment, an example will be described in which the destination-related item can be set correctly even when the creator directly inputs the destination in the destination-related item instead of adding the destination to the address book.
Hereinafter, the parts different from those of the first embodiment will be mainly described.
FIG. 13 is a setting information editing screen 1300 of the second embodiment.
The part different from the setting information editing screen 940 described with reference to FIG. 9C will be mainly described.
Since the destination 944 of the edit screen 940 of the first embodiment displays and selects each destination of the address book table 660, it is realized by the drop-down list.
However, the destination of this embodiment is realized by a combo box.
A combo box is a combination of a drop-down list and a text box, and the author can select a value from the drop-down or enter it directly.
The destination input area 1301 is realized by a combo box.
The operation when the creator changes the set value on the destination input area 1301 by using the dropdown instead of the text box of the combo box is the same as that of the first embodiment.
By the way, similarly to the first embodiment, when the creator executes the editing process of the setting information on the various editing screens generated by executing the flowchart of FIG. 10, the installation data management device 101 executes the flowchart of FIG. do.
In this flowchart, S1101 to S1104 are the same as the processes described in the first embodiment, and thus the description thereof will be omitted.

In S1401, the UI control unit 301 determines whether or not the value is directly input to the setting item in which the value of the type 654 is the "destination ID type".
If it is determined that the value has been directly input, the process returns to S1101 and the editing work on various editing screens is continued.
If not, proceed to S1105.
Since S1105 to S1109 are the same as the processes described in the first embodiment, the description thereof will be omitted.
In the S1402, the UI control unit 301 determines whether or not the value is directly input to the setting item in which the value of the column 654 (type) is the "destination ID type" as in the S1401.
If it is determined that a direct value has been entered, proceed to S1403.
If not, proceed to S1110.
In S1403, the installation data creation unit 303 receives the value directly input from the UI control unit 301 to the setting item in which the value of the type 654 is the "destination ID type", and adds it to the address book as a new destination. Also, a temporary destination ID is issued. Specifically, the UI control unit 301 acquires the value of the destination 1301. Here, it is assumed that "user@xx.yy" is acquired. The installation data creation unit 303 receives this value from the UI control unit 301. Next, the installation data creation unit 303 adds one new record to the address book table 660 and stores "user@xx.yy" as the column 665 (destination value). Further, the installation data creation unit 303 analyzes the format of the value stored in the column 665 (destination value) and determines the destination type. The destination type can be analyzed by the installation data creation unit 303 holding in advance a format that can be set for each destination type in the form of a regular expression or the like. In the case of this example, the destination type is parsed as "email". Therefore, the installation data creation unit 303 determines the value of the column 664 (destination type) of this record as "email". Moreover, since it is possible to store an arbitrary character string in the value of column 663 (destination name), the installation data creation unit 303 stores the value "user@xx.yy" of column 665 (destination value) as it is. I will do it. Finally, the installation data creation unit 303 issues a temporary destination ID. Here, it is assumed that "2" is issued. The installation data creation unit 303 stores "2" as the value of the column 666 (temporary destination ID).

In S1404, the UI control unit 301 acquires the temporary destination ID of the destination newly added in S1403, and holds it as a value to be written to the setting information file of the setting item whose column 654 (type) value is "destination ID type". .. For example, "user@xx.yy" is displayed for the destination 1301, but the value to be written to the setting information file is "2".
Since S1110 and S1111 are the same as the process described in the first embodiment, the description thereof will be omitted.
This is the end of the explanation of this flowchart.
Since the processing of the automatic installation program 450 of the target machine 106 is the same as that of the first embodiment, the description thereof will be omitted.
By executing S1401 to S1404 of the above embodiment, the installation data management device 101 has the same settings as in the first embodiment even when a destination that does not exist in the address book is directly input to the destination-related item. You will be able to create information files. Therefore, the target machine 106 can correctly reflect the installation data including the destination-related items to itself as in the first embodiment.

In the first and second embodiments, in order to write the new destination set in the destination-related item to the setting information file and correctly reflect it on the target machine 106, the installation data management device replaces the destination ID that can be issued only by the device. Introduced a temporary destination ID that can be issued.
In this embodiment, an example in which the new destination set in the destination-related item can be correctly reflected in the target machine 106 without issuing the temporary destination ID will be described.
In this embodiment, the record whose value in column 672 (attribute) is "temporary destination ID" is deleted from the all address book definition table 670 of the first embodiment. Also, the column 666 of the address book table 660 is deleted. Furthermore, the <TmpAdID> tag in the address book file 840 and the column 965 (temporary destination ID) of the address book management screen 960 are also deleted.
By the way, similarly to the second embodiment, when the creator executes the editing process of the setting information on the various editing screens generated by executing the flowchart of FIG. 10, the installation data management device 101 executes the flowchart of FIG. do. Hereinafter, the difference from the flowchart of FIG. 14 will be mainly described.
In this flowchart, S1101 is the same as the process described in the first embodiment, and thus the description thereof will be omitted. Further, since S1103 is not executed in this flowchart, if it is determined that a new destination has been added in S1102, the process returns to S1101 and the editing work on various editing screens is continued.
Since S1104 to S1106 and S1401 are the same as the processes described in Example 1 and Example 2 except that they proceed to S1501 where they should proceed to S1107 in S1105, the description thereof will be omitted.
In S1501, the UI control unit 301 holds the destination value (value of column 665 (destination value)) of the destination selected in the setting item edited in S1104 as the value of the setting item.
Since S1108, S1109, and S1402 are the same as the processes described in Example 1 and Example 2 except that they proceed to S1502 where they should proceed to S1403 in S1402, the description thereof will be omitted.

S1502 is almost the same as S1403 of the second embodiment, except that the process related to the temporary destination ID is not executed. Specifically, the UI control unit 301 acquires the value of the destination 1301. Here, it is assumed that "user@xx.yy" is acquired. The installation data creation unit 303 receives this value from the UI control unit 301. Next, the installation data creation unit 303 adds one new record to the address book table 660 and stores "user@xx.yy" as the column 665 (destination value). Further, the installation data creation unit 303 analyzes the format of the value stored in the column 665 (destination value) and determines the destination type. The destination type can be analyzed by the installation data creation unit 303 holding in advance a format that can be set for each destination type in the form of a regular expression or the like. In the case of this example, the destination type is parsed as "email". Therefore, the installation data creation unit 303 determines the value of the column 664 (destination type) of this record as "email". Moreover, since it is possible to store an arbitrary character string in the value of column 663 (destination name), the installation data creation unit 303 stores the value "user@xx.yy" of column 665 (destination value) as it is. I will do it. Unlike the second embodiment, the process related to the installation data creation unit 303 temporary destination ID is not executed.
In S1503, the UI control unit 301 acquires the destination value of the destination newly added in S1403, and holds it as a value to be written to the setting information file of the setting item in which the value of column 654 (type) is "destination ID type". For example, "user@xx.yy" is displayed for the destination 1301, but the value in column 665 (setting value) is also "user@xx.yy", so the value written to the setting information file is "user@". xx.yy ”.
Since S1110 and S1111 are the same as the process described in the first embodiment, the description thereof will be omitted.
Note that, unlike the first and second embodiments, the address book file 840 created in S1111 does not include the <TmpAdID> tag indicating the temporary destination ID. On the other hand, the installation data management device 101 is executing a process of creating a destination. As a result, the installation data creation unit 303 of this embodiment creates the address book file 840 in which the value of the <AdID> tag indicating the destination ID is blank.
This is the end of the explanation of this flowchart.

FIG. 16 is a flowchart executed by the target machine 106 of this embodiment.
In this flowchart, S1201 to S1204 are the same as the processes described in the first embodiment, and thus the description thereof will be omitted.
In S1601, the processing execution unit 453 determines whether or not there is a destination whose destination ID value is empty in the address book file 840. For the value of the destination ID, check the value of the <AdID> tag of each destination.
If it is determined that there is a destination whose destination ID is empty, the process proceeds to S1602.
If not, proceed to S1209.
In S1602, the processing execution unit 453 issues a destination ID to the above destination, and sets the destination ID for the corresponding destination in the address book file 840. Here, it is assumed that "A3" is issued as the destination ID. In this case, the processing execution unit 453 sets the value "A3" in the <AdID> tag of the destination 843 of the address book file 840.
In the S1603, the processing execution unit 453 detects a destination ID type setting item from the setting information file 800, and determines whether or not the destination value is set as the value. Specifically, the processing execution unit 453 confirms the specifications of the setting items included in the setting information area 802 on the setting specification management table 510. As a result, it can be seen that the value of the <Destination> tag is the destination ID type. Next, the processing execution unit 453 acquires the value "user@xx.yy" of the <Destination> tag. This value is not the destination ID issued by the device. Therefore, the processing execution unit 453 can determine that the setting information file 800 includes the setting item of the destination ID type in which the destination value is set as the value.
If it is determined that there is a destination ID type setting item for which the destination value is set as a value, the process proceeds to S1604.
If not, proceed to S1209.

In S1604, the processing execution unit 453 uses the description in the address book file 840 generated in S1602 to replace the value of the setting item detected in S1603. Specifically, the processing execution unit 453 replaces the value "user@xx.yy" of the <Destination> tag in the setting information file 800 with "A3". Here, the value "A3" is the value of the <AdID> tag of the destination where the value of the <AdValue> tag of the address book file 840 is "user@xx.yy".
Since S1209 and S1210 are the same as the process described in the first embodiment, the description thereof will be omitted.
By executing S1501 to S1503 of the above embodiment, the installation data management device 101 can specify a destination whose destination ID is empty in the destination-related item. Further, by executing S1601 to S1604, even if a destination with an empty destination ID is set in the destination-related item, the target machine 106 correctly sets the installation data to itself as in the first embodiment. It will be possible to reflect.

(Other examples)
The present invention supplies a program that realizes one or more functions of the above-described embodiment to a system or device via a network or storage medium, and one or more processors in the computer of the system or device reads and executes the program. It can also be realized by the processing to be performed. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.
Further, the present invention may be applied to a system composed of a plurality of devices or a device composed of one device. The present invention is not limited to the above embodiments, and various modifications (including organic combinations of each embodiment) are possible based on the gist of the present invention, and these are excluded from the scope of the present invention. is not it. That is, all the configurations in which each of the above-described examples and modifications thereof are combined are also included in the present invention.

Claims (11)

An information processing system in which an installation data management device that creates and manages installation data including device setting information and address book information including a first identifier as a destination and a device that reflects the installation data are connected by a network. hand,
The installation data management device is
When the creator adds a new destination to the address book information, a second identifier is issued, and when the creator selects the new destination as the destination, the second identifier is used as the destination. It has a creation means for setting and creating the setting information.
The device is
An acquisition means for acquiring the installation data from the installation data management device, and
When the second identifier is set in the setting information of the installation data acquired by the acquisition means, the first identifier is issued and the second identifier of the destination of the setting information is used. A reflection means for reflecting the installation data on the device by substituting with the issued first identifier,
An information processing system characterized by having. The information processing system according to claim 1, wherein the first identifier is issued by the device. The information processing system according to claim 1 or 2, wherein the specification information relating to the specification of the setting information of the device is managed by another management device connected by a network. The information processing system according to any one of claims 1 to 3, wherein the creator sets a destination by selecting an arbitrary destination from the destinations included in the address book information. The creation means is
When the value related to the new destination is directly input by the creator in the destination setting item, the value related to the new destination is added to the address book information as the new destination, a second identifier is issued, and the second identifier is used as the destination. The information processing system according to claim 1, wherein the setting information is set and the setting information is created. An installation data management device that creates and manages installation data including address book information including the device setting information and the first identifier as the destination.
An information processing system in which the device that reflects the installation data is connected via a network.
The installation data management device is
When the creator directly inputs a value related to a new destination in the destination setting item, the value related to the new destination is added to the address book information as the new destination, and the value related to the new destination is set as the destination, and the setting information is set. Have a creation means to create,
The device is
An acquisition means for acquiring the installation data from the installation data management device, and
If there is a record in which the first identifier is not set in the address book information of the installation data acquired by the acquisition means, the first identifier is issued and the destination of the setting information of the installation data is issued. A reflection means for reflecting the installation data on the device by replacing the value related to the new destination with the issued first identifier.
An information processing system characterized by having. The reflection means
The information processing system according to any one of claims 1 to 6, wherein the installation data is reflected on the device by executing the script acquired as the installation data. Installation in an information processing system in which an installation data management device that creates and manages installation data including address book information including device setting information and a first identifier related to a destination and a device that reflects the installation data are connected by a network. It is a control method for data management devices.
A control method for an installation data management device, comprising a storage step of generating a second identifier and storing it in the setting information when the creator sets a new destination in the address book information. A device in an information processing system in which an installation data management device that creates and manages installation data including address book information including device setting information and a first identifier related to a destination and a device that reflects the installation data are connected by a network. It is a control method of
The acquisition step of acquiring the installation data from the installation data management device, and
When the second identifier is set in the address book information of the installation data acquired in the acquisition step, the first identifier is issued and the issued first identifier is the second identifier. The reflection step to be reflected on the device by replacing the identifier of
A method of controlling a device, characterized by having. A program for causing a computer to execute the control method of the installation data management device according to claim 8. A program for causing a computer to execute the device control method according to claim 9.

Images