JP2018005565A - Software distribution system, and software distribution method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a distribution setting of software to a plurality of devices to be non-competitively conducted without falling operability even in an environment having a distribution of an application and a distribution of an FW mixed.SOLUTION: A distribution system 10 is configured to: upon setting an application distribution and when an application of a distribution object is selected, inquire a distributable application version of a license management system 40 (432 and 433); inquire whether the application version selected according to an inquiry result (434) is applicable to each selected device with respect to the license management system 40 (435 and 436); register (445) an application distribution setting received according to an inquiry result (437); upon setting a FW distribution and when a device distributing the FW is selected, further determine whether the distribution of the FW to the selected device is permitted on the basis of the application distribution setting and the like; and register an FW distribution setting received according to a determination result.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a software distribution system that manages application distribution settings and firmware distribution settings for a plurality of devices, and a software distribution method thereof.

  In a device such as a multifunction peripheral, two types of software, firmware for realizing the intrinsic function of the device and an application installed and used later for each user, can be used. Usually, an application is selected, installed, and activated by a user. An application may require an additional usage fee (license) for use.

  By the way, firmware and applications are upgraded to correct defects and expand functions. In the version upgrade, not only the firmware but also the application may be installed by the device manufacturer or the seller. In particular, in the case of devices such as multifunction peripherals, maintenance contracts with customers are concluded, and there are many forms that are customized for each customer and each device.

In installing software or updating to version-up software, it has been put into practical use that a device is connected to a distribution server via a network to distribute software from a remote location to the device.
The service person is responsible for maintaining many customers and devices. For this reason, there are cases in which a plurality of devices are collectively set for delivery by operation on the network of a service person from a remote location as described above, as well as delivery by operation from the device.

  Patent Document 1 proposes a technique for selecting and controlling a device (forbidden or deleted) after selecting a firmware (version) to be distributed to a device selected at a remote location. In this proposal, the firmware distribution status is displayed on the device selection screen.

JP 2012-212268 A

  In software distribution from a remote place by a service person, it is necessary to consider that distribution reservations of different types of software such as firmware and applications do not compete with each other. For example, since updating the firmware involves rebooting the device, attempting to update the firmware and application at the same time may fail. Therefore, a mode in which exclusive control is performed so that firmware and application distribution settings cannot be performed simultaneously is conceivable. However, in such a configuration, there is a possibility that in the operation of the distribution setting, the distribution setting of the type to be preferentially distributed is overwritten and canceled, or the set distribution setting is prohibited and fails. As a result, the operability of the software distribution setting is lowered.

  Further, since the process for selecting a device to be distributed is common regardless of the type of software to be distributed, it is necessary to support a plurality of software types when selecting a plurality of devices. However, if the device search condition screen corresponding to a plurality of software types is used, the screen becomes complicated and the operability deteriorates.

  In addition, since application software is license-managed, it is necessary to determine whether or not a version upgrade is possible on a device-by-device basis. However, when setting application distribution for multiple devices at the same time, when selecting the application to be distributed, application version, and target device for distribution, performing a version up / down decision every time the screen is updated, the display becomes slow, resulting in operability. Will fall.

  The present invention has been made to solve the above problems. An object of the present invention is to provide a mechanism capable of performing software distribution settings for a plurality of devices without competition even in an environment in which application distribution and firmware distribution are mixed, without reducing operability. is there.

  The present invention is a software distribution system for managing a first distribution setting for reserving application distribution and a second distribution setting for reserving firmware distribution for a plurality of devices, the first distribution setting and the second distribution. Accepting means for accepting selection of which setting to perform, and when performing the first distribution setting, when a distribution target application is selected, a distribution version of the application selected as the distribution target First inquiry means for inquiring information to the license management system, and one or more devices for selecting a version to be distributed and distributing the selected version of the application based on the inquiry result of the first inquiry means First user interface that accepts selection A first providing means for providing the license management system, and inquiring to the license management system whether the version of the application to be distributed selected according to the first user interface is applicable to each of the selected devices. A second inquiry unit and a second distribution unit that accepts a first distribution setting for reserving distribution of the version of the application to be distributed to each device determined to be applicable based on a result of the inquiry from the second inquiry unit; A second providing means for providing a user interface; a first registration means for registering a first distribution setting received in accordance with the second user interface; and one or a plurality of devices for distributing firmware when performing the second distribution setting Is selected, the selected device or devices are selected. Determining whether or not firmware can be distributed to a device based on registration of the first distribution setting for each selected device, and distributing the firmware to each device determined to be able to distribute firmware by the determining unit And a second providing means for providing a third user interface for accepting a second delivery setting for reserving the second delivery setting, and a second registration means for registering the second delivery setting accepted in accordance with the third user interface. .

  According to the present invention, even in an environment where application distribution and firmware distribution coexist, software distribution settings for a plurality of devices can be performed without competition without deteriorating operability.

The block diagram which illustrates the composition of the system which shows one example of the present invention. Hardware configuration diagram of application server of distribution system Functional configuration diagram of distribution system, license management system, and device Sequence diagram showing the flow of application installation Sequence diagram showing the flow of application reservation settings and update Sequence diagram showing the flow of firmware distribution reservation setting and update User interface screen for FW distribution settings User interface screen for FW distribution settings User interface screen for FW distribution settings User interface screen for FW periodic update settings User interface screen for FW periodic update settings User interface screen for app delivery settings User interface screen for app delivery settings User interface screen for app delivery settings User interface screen for app delivery settings User interface screen for app delivery settings Flowchart illustrating FW distribution reservation process Flowchart illustrating FW periodic update setting process Flow chart illustrating application distribution reservation process Flowchart illustrating application distribution availability determination process

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram illustrating the configuration of a system showing an embodiment of the present invention.
As shown in FIG. 1, the distribution system 10 includes a Web server 12, a DB server 13, an application server 11, and the like. The distribution system 10 communicates with the devices (115, 116, 120, 121, 124 to 127, 131) of each customer company (114, 119, 129) and the like via the Web server 12 connected to the Internet 100. . Accordingly, the distribution system 10 is a software distribution system that manages distribution control of application software (hereinafter referred to as “application”) and firmware (hereinafter referred to as “FW”) to devices. Although details will be described later, the distribution system 10 manages distribution settings of software in cooperation with a license management system 40 described later.

  The actual file of the application and FW is in the content server 20, and when the application is installed on the device, the location information of the actual file on the content server 20 is acquired from the distribution system 10, and the application is downloaded from the content server 20. . Thereby, it is possible to distribute the application distribution load of many devices and to distribute the application efficiently. The same applies to the update of the application and FW.

  The content server 20 includes a content management server 21 and file storages (22, 23). The content management server 21 stores or provides file contents, that is, actual files of applications and FWs, according to external requests.

  The license management system 40 also issues and manages licenses for executing applications. The license management system 40 is also connected to the distribution system 10 and the like via the Internet 100 and the like. Like the distribution system 10, the license management system 40 includes a Web server 42, a DB server 43, an application server 41, and the like.

  There are various types of devices such as a multi-function printer (MFP) and a single function printer (SFP), and one or a plurality of functions are mounted for each device model. When the FW for realizing these functions is installed in the device, each function of the device can be used. Further, it is possible to install and execute an app that can be executed for each device model or common to the device model on the device. The user of the device installs the application by selecting a desired application from a plurality of applications that can be used on the device and purchasing the license. Further, when a defect in a device application is corrected, or when a function is improved or added, it can be used by updating the application. The distribution system 10 cooperates with the license management system 40 to determine an application that operates on the device from the viewpoint of license management, and determines an application to be distributed.

  The sales company system 30 sells the device to each customer company (114, 119, 129) so that the device manufacturing company or the device sales company that manages, manages, and operates the application and FW registration and management System. The sales company system 30 includes one or more personal computers (hereinafter referred to as “PCs”) (31, 32) or servers (33, 34). By accessing the distribution system 10 and the content server 20 from the sales company system 30, registration of the application and FW and distribution setting can be performed.

  In the customer system 114 (Company A X office), devices (115, 116) connected to a LAN 118 connected to the Internet 100 are monitored by a monitoring device 117. The monitoring device 117 transmits operation information and the like of the devices (115, 116) to a monitoring system (not shown) via the Internet 100. The devices (115, 116) include a controller for applying FW and applications downloaded from the content server 20.

  In the customer system 119 (company A, Y office), the devices (120, 121, 124 to 127) connected to the LAN 128 are managed by the monitoring devices 122 and 123. The monitoring device 122 manages devices (120, 121, 124 to 127), and the monitoring device 123 manages devices 126 and 127, respectively. The monitoring devices 122 and 123 transmit operation information and the like of the devices (120, 121, 124 to 127) to a monitoring system (not shown) via the Internet 100. The devices (120, 121, 124 to 127) include a controller for applying FW and applications downloaded from the content server 20.

  In the customer system 129 (Company B), the device 131 itself connected to the LAN 130 connected to the Internet 100 transmits its operation information and the like via the Internet 100 to a monitoring system (not shown). The device 131 has the same function as the monitoring devices 117, 122, and 123 described above. The device 131 includes a controller for applying FW and applications downloaded from the content server 20.

FIG. 2 is a block diagram illustrating a hardware configuration of the application server 11 of the distribution system 10.
The application server 11 in this embodiment is connected to the Web server 12 and the DB server 13 via a network interface (Network I / F) 204. The application server 11 includes a CPU 201, a RAM 202, a ROM 203, a network interface 204, an HDD (Hard Disk Drive) 206, and the like connected via a bus 205. Note that another storage device such as an SSD (Solid State Drive) may be provided instead of or in combination with the HDD 206.

  The distribution system 10 is realized by the CPU 201 of the application server 11 reading and executing data and programs recorded in the HDD 206, the ROM 203, and the RAM 202. In addition, the function of the distribution system 10 may be realized by cooperation of functions of a plurality of servers. The network interface 204 is used for function cooperation between servers in the distribution system 10 and is also used for communicating with an external system via the Internet 100. 2 shows the application server 11 correspondingly, the other servers shown in FIG. 1, the controller unit of the PC and the device, and the like have the same hardware configuration.

  FIG. 3 is a block diagram illustrating functional configurations of the distribution system 10, the license management system 40, and the device 400.

  In FIG. 3, reference numeral 400 is an example of a device connected to the distribution system 10. Reference numeral 302 denotes a Web browser which is a client system as an example of a sales company system connected to the distribution system 10. For example, the Web browser 302 is realized by the CPU of the PC 31 of the sales company system 30 executing a Web browser program stored in an HDD or the like.

Next, the functional configuration of the distribution system 10 will be described.
As shown in FIG. 1, the distribution system 10 is composed of a plurality of servers, so that the function is also realized by a combination of a plurality of servers. However, the distribution system 10 is not limited to the configuration shown in FIG. 1, and all functions may be realized by one server, and when high performance is required, it is realized by a combination of more servers. May be. That is, the functional configuration of the distribution system 10 shown in FIG. 3 is realized by the CPU executing a program stored in the HDD or the like in each of one or a plurality of servers configuring the distribution system 10.

  A web interface unit 310 provides an application and FW distribution function for the device 400. The Web interface unit 310 receives various requests from each device 400 and returns a processing result corresponding to the request. For example, when receiving a request for application distribution information, the Web interface unit 310 searches for a location where the target application is stored, and returns a URL for acquiring the application as a response. Details of the request processing will be described later.

Reference numeral 311 denotes a user interface unit for accessing the distribution system 10 from the Web browser 302 and performing application and FW registration, distribution setting, and periodic update setting.
A request reception unit 312 receives a request from the device 400 via the Web interface unit 310. A response return unit 313 returns a response to the device 400 via the Web interface unit 310.

  A distribution setting control unit 314 controls the distribution setting of the FW and the application instructed via the user interface unit 311. The distribution setting control unit 314 controls the device management unit 315, the application distribution setting unit 317, and the FW distribution setting unit 318 to determine the output content of the screen for distribution setting displayed on the user interface unit 311. The device management unit 315 manages devices under the control of the distribution setting control unit 314. The application distribution setting unit 317 performs application distribution settings under the control of the distribution setting control unit 314. The FW distribution setting unit 318 performs FW distribution setting under the control of the distribution setting control unit 314.

  320 is a DB access unit for updating or retrieving data in the table managed by the data management unit 330 according to various processes.

  In the data management unit 330, reference numeral 331 denotes an application file management table (illustrated in Table 6 described later). Reference numeral 333 denotes a registered FW management table (illustrated in Table 7 described later). Reference numeral 334 denotes a device management table (illustrated in Table 8 described later). Reference numeral 335 denotes an installed application management table (illustrated in Table 9 described later). Reference numeral 336 denotes an application distribution management table (illustrated in Table 10 described later). Reference numeral 337 denotes an FW distribution management table. Reference numeral 338 denotes a periodic update setting management table.

Hereinafter, the functional configuration of the device 400 will be described.
The functional configuration of the device 400 shown in FIG. 3 is realized by the CPU of the controller included in the device 400 executing a program stored in a ROM, an HDD, or the like.

  Reference numeral 340 denotes a main processing unit that processes the original functions of the device 400. The main processing unit 340 indicates a main function such as performing an image forming process for a printer, for example. In addition to this main function, the device 400 also has a function for controlling device FW and application distribution, which are shown as functional blocks 341 to 348.

  Reference numeral 341 denotes a Web interface unit for receiving applications and FWs distributed from the distribution system 10 and is connected to the Web interface unit 310 of the distribution system 10. A distribution processing unit 342 processes the distribution of the application and the FW via the Web interface unit 341. Reference numeral 343 denotes an application installation unit that installs the distributed application. An application update unit 344 updates the distributed application. A FW update unit 345 updates the distributed FW. Reference numeral 347 denotes an FW storage unit that stores the distributed FW. An application storage unit 348 stores the distributed application.

Hereinafter, the functional configuration of the license management system 40 will be described.
Since the license management system 40 is composed of a plurality of servers as shown in FIG. 1, it is assumed that the function is also realized by a combination of a plurality of servers. However, the license management system 40 is not limited to the configuration shown in FIG. 1, and all the functions may be realized by one server, and when high performance is required, a combination of more servers can be used. It may be realized. That is, the functional configuration of the license management system 40 shown in FIG. 3 is realized by the CPU executing a program stored in the HDD or the like in each of one or a plurality of servers constituting the license management system 40. .

  A Web interface unit 350 is used by the license management system 40 to connect to the distribution system 10 and exchange information. The web interface unit 350 is connected to the web interface unit 310 of the distribution system. A request reception unit 351 receives a request from the distribution system 10 via the Web interface unit 350. A response return unit 352 returns a response to the distribution system 10 via the Web interface unit 350. A license management unit 353 manages application licenses. A DB access unit 354 is used to update or search data in a table managed by the data management unit 360 according to various processes.

  In the data management unit 360, 361 is a registered application management table (illustrated in Table 1 described later). Reference numeral 362 denotes an application product management table (illustrated in Table 2 described later). Reference numeral 363 denotes an installable version management table (illustrated in Table 3 described later). Reference numeral 364 denotes a license management table (illustrated in Table 4 described later). 365 is a device unit license management table (illustrated in Table 5 described later).

Hereinafter, each table described above will be described.
First, a table managed by the license management system 40 will be described.
Table 1 shows an example of application management information stored in the registered application management table 361.

  As shown in Table 1, the application management information managed by the registered application management table 361 includes a list of combinations of registration numbers, passwords, application IDs, application names, versions, file IDs, and the like. The same application with different versions is uniquely identified by an application ID. A certain version of a certain application is uniquely identified by a registration number. The password is for restricting users who can access the application when accessing the application with a registration number for distribution setting. Further, the file ID is for associating with the storage location of the application corresponding to the registration number. The application name is assigned so that the user can easily identify the name on the display on the user interface. The application management information as described above is input and updated when the person in charge registers the application from the sales company system 30.

  When an app is sold to a customer, it is managed as a product, and the same app can be a different product for different sales forms. Table 2 shows an example of application product management information stored in the application product management table 362.

  As shown in Table 2, the application product management information managed by the application product management table 362 includes a list of combinations of product IDs, product names, application IDs, and the like. The application ID is associated with the application ID in the application management information (Table 1). In the management information of application products, even with the same application ID, different products and product names can be attached and managed.

  Even if the application ID is the same, there are a plurality of different versions of the application. In the management of application products, which version can be used for each application product can be managed independently. Table 3 shows an example of installable version information of the application product stored in the installable version management table 363.

  As shown in Table 3, the installable version information of the application product managed by the installable version management table 363 includes a list of combinations such as a product ID and a registration number. When a combination of a product ID and a registration number is registered in this information, it is possible to install a version of an application with a corresponding registration number for the product corresponding to the product ID.

  The license management system 40 manages the license by associating the customer with the product ID in order to sell the application to the customer. That is, it records which product is licensed to which customer, and associates the license with the product. Table 4 shows an example of the license information stored in the license management table 364.

  As shown in Table 4, the license information managed by the license management table 364 includes a list of combinations of license IDs, customer names, product IDs, and the like. The license ID uniquely identifies the license. The product ID is associated with the product ID in the application product management information (Table 3). From this information, the product ID corresponding to the license ID can be specified.

  In addition, the license management system 40 manages to which device the application corresponding to the license is installed. Table 5 shows an example of device-license association information stored in the device-unit license management table 365.

  As shown in Table 5, the device-license association information managed by the device-unit license management table 365 includes a list of combinations of device IDs and license IDs. The license ID is associated with the license ID in the license information (Table 4). If a combination of a device ID and a license ID is registered in this information, a product corresponding to the license ID can be installed on the device corresponding to the device ID.

Next, a table managed by the distribution system 10 will be described.
Table 6 shows an example of application file management information stored in the application file management table 331.

  As shown in Table 6, the file management information of the application managed by the application file management table 331 includes a list of combinations of file IDs and URLs. The file ID is associated with the file ID in the application management information (Table 1). From this information, it can be seen that the application file corresponding to the file ID is stored in the location indicated by the URL in the content server 20.

  Similar to the application, the distribution system 10 also manages the FW that can be distributed. Table 7 shows an example of FW management information registered in the registered FW management table 333.

  As shown in Table 7, the FW management information managed by the registered FW management table 333 includes a list of combinations of device models, versions, disclosure categories, URLs, and the like. The FW file corresponding to the combination of the device model and the version is stored in the storage location on the content server 20 indicated by the URL. The public classification is either FW that the FW is generally installed on any device (“normal FW”) or FW that is installed only on a specific customer's device such as for negotiations (“specific FW”). Indicate.

  The distribution system 10 manages combinations of updatable FW versions by management information (not shown). For example, information is managed such that updating from Ver1.00 to Ver1.01 is possible and updating from Ver1.00 to Ver1.10 is not possible. Such FW management information is input and updated when the person in charge registers the FW from the sales company system 30.

  The distribution system 10 maintains and manages the status of each device to be distributed. One piece of information indicating the state of the device is the version information of the FW operating on each device. Table 8 shows an example of the device management information stored in the device management table 334.

  As shown in Table 8, the device management information managed by the device management table 334 includes a list of combinations of device ID, device model, version, remote delivery, and the like. The device model is a model of a device identified by a device ID. The version indicates the version of the FW currently operating on the device. Remote distribution indicates whether or not remote distribution setting of the application to the device is permitted. The remote distribution setting refers to a setting for distributing software or the like to a device from a remote location by an operation on a serviceman's network.

  Further, as another information indicating the status of the device, there are an application installed in each device and information on the status. Table 9 shows an example of installed application information of a device stored in the installed application management table 335.

  As shown in Table 9, the installed application information managed by the installed application management table 335 includes a list of combinations of device ID, application ID, application name, version, operation state, and the like. The combination of the device ID, the application ID, and the version indicates that the application indicated by the combination of the application ID and the version is installed in the device indicated by the device ID. The operation state indicates the operation state of the application. This information is updated by a process indicated by 419 in FIG. 4 described later or a process indicated by 457 in FIG. Then, this information is referred to in order to obtain an update application candidate displayed at 600 in FIG.

  Table 10 shows an example of application distribution information stored in the application distribution management table 336.

  As shown in Table 10, the distribution information of the application managed in the application distribution management table 336 is a list of combinations of distribution ID, device ID, application ID, version, file ID, distribution date / time, post-distribution status, distribution status, etc. Consists of. The post-delivery state specifies the post-delivery state of the application distributed to the device based on the distribution information, and can specify any one of “start”, “stop”, and “continue”. The distribution status indicates the distribution status of the application based on the distribution information. Information such as “waiting for distribution”, “during distribution”, “completed”, “failure”, “cancel” is stored according to the distribution status. Is done. The distribution system 10 registers an application distribution reservation based on the application distribution information as described above.

  Table 11 shows an example of FW distribution information stored in the FW distribution management table 337.

  As shown in Table 11, the FW distribution information managed by the FW distribution management table 337 includes a list of combinations of distribution ID, device ID, device model, version, distribution date / time, application date / time, distribution status, and the like. In the distribution system 10, the FW distribution reservation is registered based on the FW distribution information as described above.

  Table 12 shows an example of FW periodic update information stored in the periodic update setting management table 338.

  As shown in Table 12, the FW periodic update information managed by the periodic update setting management table 338 includes distribution ID, device ID, periodic update setting, confirmation time, application time, e-mail address, comment, distribution status, etc. Consists of a list of combinations. The distribution system 10 registers the FW periodic update setting based on the periodic update information as described above.

  Hereinafter, the flow in the case where the distribution setting is performed for the distribution system 10 and the distribution system 10 distributes to the device 400 will be exemplified using the sequence diagrams of FIGS. 4 to 6. In the sequence diagrams shown in FIGS. 4 to 6, the processing of the distribution system 10 is realized by the CPU 201 of the server constituting the distribution system 10 executing a program stored in the HDD 206, the ROM 203, or the like. . Further, the processing of the device 400 is realized, for example, when the CPU of the device 400 executes a program stored in an HDD, a ROM, or the like. The processing of the license management system 40 is realized, for example, when the CPU of the server that constitutes the license management system 40 executes a program stored in an HDD, a ROM, or the like. Further, the processing of the content server 20 is realized, for example, when the CPU of the content management server 21 executes a program stored in an HDD, a ROM, or the like. Further, it is assumed that an operation (update reservation setting operation or the like) to the distribution system 10 by the service person 402 is performed by accessing the distribution system 10 using the Web browser 302.

  FIG. 4 is a sequence diagram illustrating a flow when a device user operates a device to install an application on the device.

  In FIG. 4, 401 is a user who uses the device 400. In order to install a new application on the device 400, the user 401 operates a user interface (such as an operation panel) of the device 400 and issues an application installation instruction (410). At this time, the user 401 instructs information that can identify the application ID and version of the application to be installed.

  In response to the instruction 410, the device 400 sends information (for example, device ID, application ID, version, etc.) specifying the application and version to be installed to the distribution system 10 and requests (requests) the corresponding application ( 411).

  In response to the request (411), the distribution system 10 processes the request (411) by the Web interface unit 310 or the like. Note that when the Web interface unit 310 and other functional units perform processing in cooperation, “Web interface unit 310 processes” is described. The Web interface unit 310 sends the device ID, application ID, and version passed in the request of 411 to the license management system 40, and installs the specified application version in the device 400 that has sent the request. Inquire about whether it is possible (license inquiry; 412).

  In response to this inquiry (412), the license management system 40 may confirm the license corresponding to the device ID included in the inquiry (412) and install the version of the designated application on the device. Determine if you can. Specifically, the license management system 40 identifies the license ID from the device ID (Table 5), identifies the product ID from the license ID (Table 4), identifies the registration number from the product ID (Table 3), and registers The application ID, version, and file ID (Table 1) are specified from the number. As a result, the license management system 40 determines whether or not the specified application version can be installed in the specified device. If the license management system 40 determines that the version of the inquired application can be installed on the device specified by the device ID, the license management system 40 returns a file ID for identifying the file of the application to be installed to the distribution system 10 ( License response; 413).

  When the response (413) indicating that the license management system 40 can be installed is returned, the Web interface unit 310 of the distribution system 10 uses the file ID included in the response, from the application file management table 331 (Table 6). Search for the URL of the app. Further, the Web interface unit 310 returns the retrieved URL to the device 400 as the URL for downloading the program file corresponding to the request 411 together with the license information returned by the license management system 40 (414). Hereinafter, the description is continued assuming that the request from the device 400 processed by the distribution system 10 is also processed by the Web interface unit 310.

  The device 400 accesses the content server 20 with the URL returned in 414 and requests a file of the application to be installed (application request; 415). In response to this request (415), the content server 20 transmits the requested application file to the device 400 (416). The device 400 uses the application file acquired in step 416 to perform application installation processing (417).

  When the installation process (417) is completed and the installed application is activated, the device 400 notifies the distribution system 10 of the completion of the installation of the application and the execution state after the installation (418). At this time, the device 400 notifies the distribution system 10 of the list information of all the apps installed in the device 400 at that time, including the apps newly installed in 417, and their versions.

  Upon receiving the app installation information notification (418) from the device 400, the distribution system 10 records the information in the installed app management table 335 (Table 9) and updates the information of the apps currently installed on the device. (419). Then, the distribution system 10 returns a response to the device 400 after recording the state of the application in 419 (420).

FIG. 5 is a sequence diagram illustrating a flow when a service person makes a distribution reservation setting for updating an application.
In FIG. 5, a service person 402 is a service person who performs a setting operation for remote delivery to the delivery system 10 for the device 400 to update the application and the FW. The service person 402 uses the Web browser 302 to access the user interface unit 311 of the distribution system 10 and make an application update reservation setting (430). For example, it is assumed that the application update reservation setting (430) is made from a UI screen shown in FIG. 11A or FIG. In this embodiment, an application installed on a device is assumed to be an app that can be upgraded by the device.

  The distribution system 10 identifies the application ID of the application installed in the device 400 from the installed application information (Table 9) acquired from the device 400, and sets it as a candidate for the version of the application that distributes the application. Alternatively, the distribution system 10 identifies the version of the application to be distributed according to the registration number that identifies the version of the application input from the service person 402. When the application ID is identified from the installed application information as a candidate for the version of the application to be distributed, the distribution system 10 transmits the application ID identified from the installed application information to the license management system 40, and the version of the application to be distributed Inquire about information (431). When the version of the application to be distributed is specified according to the registration number, the distribution system 10 transmits the input registration number to the license management system 40 and inquires about the information of the version of the application to be distributed (431).

  The license management system 40 corresponds to a list of information on all versions of the application corresponding to the application ID for which the above-mentioned inquiry 431 has been received (a list of information on versions of the application corresponding to the application ID that can be distributed) or a registration number. The application version information to be searched is searched from the registered application management table 361 (Table 1), and the search result is returned to the distribution system 10 (432).

  In 433, the distribution system 10 presents the version list returned from the license management system 40 or information on the version of the application to the service person 402 as a search condition and an updatable version candidate. For example, it is presented as shown in FIG. 11B or FIG. Furthermore, in response to a device search instruction from the service person 402, a list of devices that match the search conditions and the above-described updatable version candidates are presented. For example, it is presented as shown in FIG. Information presentation from the distribution system 10 to the service person 402 is performed from the user interface unit 311 using the Web browser 302.

The service person 402 selects the version of the application to be updated and the distribution target device in accordance with the presentation of 433 (434).
The distribution system 10 sends information about the device specified by the serviceman 402 and the application to be updated in the above 434 to the license management system 40, and inquires whether each device can be updated (applicable) to the application (435).

In response to the inquiry 435, the license management system 40 determines whether each device can be updated to the application, and returns a determination result to the distribution system 10 (436).
In response to the response received at 436, the distribution system 10 presents to the service person 402 a determination result as to whether each device can be updated to the application (437). When the specified application can be updated for all the selected devices, a screen as shown in FIG. 15 to be described later is displayed, and the distribution setting of the selected application can be performed for the selected device. To. On the other hand, in the case where there is a device that cannot update the specified application among the selected devices, the determination result is presented as shown in FIG. Present a screen like this.

In response to the presentation of 437, the service person 402 instructs the distribution system 10 to set and register the distribution setting with the selected device and application (438). For example, the instruction is given as shown in FIG.
The distribution system 10 performs reservation registration for the application update in accordance with the instruction from the serviceman 402 in 438 (445). That is, the distribution system 10 registers application distribution information in the application distribution management table 336 (Table 10) in accordance with the above instruction 438.

  The device 400 periodically inquires the delivery system 10 about delivery setting confirmation to confirm whether the delivery reservation or the update of the periodic update setting is entered (446). When the application update reservation registration (445) is made by the service person 402 by the application update reservation setting (430) by the service person 402, the distribution system 10 determines the distribution setting information according to the subsequent distribution setting confirmation (446) from the device 400. In response to the device 400 (447). The delivery setting information responded at 447 includes delivery date / time information, delivery identification information (delivery ID), updated execution state instruction information (post-delivery state), and the like.

When the delivery reservation date and time (450) designated by the delivery setting information received in 447 is reached, the device 400 sends delivery identification information to the delivery system 10 and requests a corresponding application (451).
In response to the above request 451, the distribution system 10 searches the application distribution management table 336 (Table 10) from the distribution identification information (distribution ID) passed in the request, specifies the application ID and version, and further The URL of the application is retrieved from the file management table 331 (Table 6). The distribution system 10 returns the searched URL to the device 400 as a URL for downloading the program file (452).

  The device 400 accesses the content server 20 using the URL returned in 452 and requests a file of the application to be installed (453). In response to the request 453, the content server 20 responds to the device 400 with the corresponding application file (454).

The device 400 executes an application update process using the application file acquired in 454 (455).
Thereafter, the device 400 notifies the distribution system 10 of the update completion of the application updated in the above-mentioned 455 and the execution state after the update (456). At this time, the distribution system 10 is notified of the list information of the applications and versions installed in the device 400 at that time, including the updated version of the application.
Receiving the application update notification in 456, the distribution system 10 records it and updates the operation state of the target application (457). Then, the distribution system 10 returns a response to the device 400 (458), and this sequence ends.

FIG. 6 is a sequence diagram exemplifying a flow when the serviceman executes FW distribution reservation setting or FW periodic update setting.
The service person 402 performs FW distribution reservation setting or periodic update setting (460). It is assumed that the operation to the distribution system 10 by the service person 402 is performed using the Web browser 302 as described above. For example, it is assumed that the FW update reservation setting (460) is performed from a UI screen shown in FIGS. 7 to 9 or 10A to 10B described later.

  In accordance with the reservation setting of 460, the distribution system 10 records the reservation setting contents in the FW distribution management table 337 (Table 11) in the case of FW distribution reservation in 461. And recorded in the periodic update setting management table 338 (Table 12).

  As in the case shown in FIG. 5, the device 400 periodically issues a distribution setting confirmation inquiry to the distribution system 10 to confirm whether the distribution reservation or the periodic update setting has been updated (446). . When the update reservation is registered by the update reservation setting by the service person 402, the distribution system 10 responds to the device 400 with corresponding distribution setting information according to the subsequent distribution setting confirmation (446) from the device 400 ( 447). In the sequence of FIG. 6, the distribution system 10 responds to the device 400 with the distribution setting information in response to the distribution setting confirmation (446) from the device 400 (447). The distribution setting information to be returned includes distribution date / time information and distribution identification information (distribution ID) in the case of distribution setting. In the case of periodic update setting, the periodic confirmation information (confirmation time) of the periodic update, distribution identification information. (Distribution ID) is included.

  In the case of the distribution setting, when the distribution reservation date / time (distribution date / time) (470) designated by the distribution setting information received in 447 is reached, the device 400 sends the distribution identification information to the distribution system 10 and requests the corresponding FW. (471). In the case of the regular update setting, the device 400 repeats the sequence from 470 at a predetermined cycle (confirmation time) according to the setting.

  In response to the request 471, the distribution system 10 searches the FW distribution management table 337 (Table 11) from the distribution identification information passed in the request, specifies the version, and further registers the FW management table 333 (Table 7). ) URL of FW is retrieved. Then, the distribution system 10 returns the searched URL to the device 400 as a URL for downloading the program file (472).

The device 400 accesses the content server 20 using the URL returned in 472, and requests a FW file to be installed (473). In response to the request 473, the content server 20 responds to the device 400 with the corresponding FW file (474).
The device 400 executes FW update processing using the FW file acquired in 474 (475) and restarts (476).

After the restart, the device 400 transmits an FW update notification including the updated version information updated in 475 to the distribution system 10 (476).
Upon receiving the FW update notification in 476, the distribution system 10 updates the device management table 334 with the updated version information passed by the FW update notification (478). Thereby, the information on the current version of the FW of the device 400 held in the distribution system 10 is updated. Then, the distribution system 10 returns a response to the device 400 (479), and this sequence ends.

Next, with reference to FIGS. 7 to 15, distribution settings by the service person 402 shown in 430 to 438 in FIG. 5 and 460 in FIG. 6 will be described.
FIG. 7 to FIG. 15 are diagrams illustrating user interface screens (UI screens) for distribution setting according to the present embodiment. These UI screens are provided from the distribution system 10 and displayed on the Web browser 302.

  FIG. 7A illustrates a case where a service person 402 uses the Web browser 302 to access the distribution system 10 and designate (select) a device model, and then perform distribution settings for updating an application or FW. It is an example of a UI screen displayed first.

  In FIG. 7A, reference numeral 500 denotes a radio button for selecting the type of distribution setting. In 500, the distribution setting can be selected from three types of FW distribution setting (“FW distribution”), FW periodic update setting (“FW period”), and application distribution setting (“application distribution”).

  FIG. 7A corresponds to the case where “FW distribution” is selected. When “FW regular” is selected in 500, a transition is made to the screen shown in FIG. Further, when “application distribution” is selected in 500, the screen changes to a screen shown in FIG. By selecting the type of 500 on any screen, including the screen described later, the screen transitions to the screens of FIG. 7A, FIG. 10A, and FIG.

First, FW distribution setting will be described with reference to FIGS.
In FIG. 7A, first, in order to select a plurality of target devices for which FW distribution setting is to be performed, search conditions (501 to 503) for narrowing down devices under a specific condition are input.
Reference numeral 501 denotes a check box for designating the current distribution status of each target device. In the example 501 in FIG. 7A, a plurality of distribution statuses can be selected and designated from “waiting for distribution”, “distributing”, “completed”, “failed”, and “cancel”. For example, by selecting “failure” as shown in the figure, it is possible to perform distribution setting only for devices that have failed to be distributed.

Reference numeral 502 denotes a radio button for designating the disclosure category of the FW installed in each target device. The public classification is generally selected from two types: FW that is installed on any device (“normal FW”), and FW that is installed only on a specific customer's device such as for negotiations (“specific FW”). it can.
Reference numeral 503 denotes a drop-down menu for designating a range of FW versions installed in each target device.

  After specifying the conditions of the target device in the above 501 to 503, by pressing the “Search” button 504, the user interface unit 311 of the distribution system 10 changes the screen to the screen of FIG. Then, control is performed to display a device list (target device list) that matches the search condition. When the “reset” button 505 is pressed, the distribution system 10 controls to reset the search condition set in 501 to 503 and return the screen to the initial screen of FIG.

  7B is the same as that in FIG. 7A, and the device list displayed in FIG. 7B can be updated while changing the search condition. Thereby, it is an operation method that can also be selected while searching for a device for distribution setting by trial and error.

  In FIG. 7B, a distribution setting target device is further selected from the device list (target device list) 510 narrowed down by the search condition. The target device list 510 displays the following information in order from the left for a plurality of devices searched under the above conditions. For example, “device ID”, “current FW Ver.”, “Publication category”, “post-application FW Ver.”, “Application status (distribution)”, “application status (setting)”, “delivery reservation date”, “ Information such as “application reservation date / time”, “distribution method”, “FW distribution status”, “FW regular update status”, “application distribution status” is displayed.

  “Device ID” indicates an identifier of the device. “Current FW Ver.” Indicates the version of the FW currently installed in the device. The “public category” indicates the public category of the FW currently installed in the device.

  “Post-application FW Ver.” Indicates the version of the FW distributed and applied (or applied) to the device in the FW distribution setting reserved for the device (eg, 461 in FIG. 6).

  “Applicable status (distribution)” indicates the FW applicability status of the device in the FW distribution setting. That is, it indicates whether there is a FW version that can be distributed to the device. For example, if there is no FW version that can be distributed to the device, “Not applicable” is displayed. If the device information has not been acquired and applicability cannot be determined, “not applicable” is displayed. Otherwise, the device is displayed blank.

  “Applied status (setting)” indicates whether or not the periodic update setting of the device is possible in the FW periodic update setting. For example, if the device information has not been acquired and applicability cannot be determined, “not applicable” is displayed, and otherwise it is displayed blank.

  “Distribution reservation date / time” indicates the FW distribution reservation date / time in the FW distribution setting reserved for the device. “Applied reservation date / time” indicates a reservation date / time at which the FW is updated in the FW distribution setting reserved for the device. “Distribution method” indicates whether the entire FW set is distributed or only an updated module is distributed in the FW distribution setting reserved for the device.

  “FW distribution status” indicates the FW distribution status in the FW distribution setting reserved for the device. “FW periodic update status” indicates the FW periodic update status in the FW periodic update setting reserved for the device. “App distribution status” indicates the distribution status of the application in the application distribution setting reserved for the device (for example, 445 in FIG. 5).

  Furthermore, the target device list 510 includes a check box for selecting a distribution setting target device. By confirming the device information displayed in the target device list 510 and operating the check box in the row of the device to be selected, a plurality of distribution target devices can be selected. At this time, the operator confirms the information displayed in the “FW periodic update status” and “application distribution status” of the target device list 510 at the same time, so that another type of distribution setting (here, application distribution setting) Alternatively, it can be confirmed whether or not the periodic update setting is in progress. In general, updating the FW involves restarting the device, so it is necessary to appropriately shift the update timing between the FW and the application. For this reason, the FW distribution setting and the application distribution setting are configured to be set exclusively.

  In this embodiment, in the distribution system 10, when settings conflict, the screen transitions to the following FIG. 7C, an error is displayed corresponding to each target device, and is excluded from the setting target device group And The case where the settings conflict with each other means, for example, a device that has a reserved FW periodic update setting or application distribution setting (for example, “waiting for distribution” or “being distributed”) at the time of FW distribution setting. Indicates the case where the device is selected. In this case, the distribution system 10 displays an error corresponding to the device whose setting conflicts in FIG. 7C, and performs exclusion control from the setting target device group. This is because the application distribution management table 336 (Table 10) and the periodic update setting management table 338 (Table 12) are set when the FW distribution is set, and the FW distribution management table 337 (Table 11) is set when the application distribution is set. This is determined by referring to the periodic update setting management table 338 (Table 12) and confirming whether there is a setting of a different type for each target device. This determination process is performed at S1008 in FIG. 16, which will be described later, between S1204 and S1205 (not shown) in FIG. 17, and at the timing of S1417 in FIG. With this configuration, according to the present embodiment, it is possible to appropriately determine a device that is being set in conflict with another setting type and select a device.

  In addition, the display in the “FW regular update status” and “application distribution status” does not determine whether or not the distribution system 10 has different types of settings (competition determination) as another example. When there is an existing setting that conflicts with another setting type, this is also effective in an embodiment in which the existing setting is overwritten with a new setting. In other words, the operator is alerted by referring to the display of the “FW periodic update status” and “application distribution status”, and for example, the distribution system 10 determines whether there is a different type of setting (competitive contention). Even when the determination) is not performed, it is possible to prevent the setting from being overwritten by mistake.

  By selecting a plurality of distribution target devices in the target device list 510 and pressing the “Next” button 506, the distribution system 10 determines whether or not distribution setting is possible for each selected device (the above-described conflict). Judgment). Here, when there is a device that cannot be distributed, the distribution system 10 controls to transition to the screen of FIG. On the other hand, if all devices can be distributed, the distribution system 10 controls to transition to the screen shown in FIG.

In FIG. 7C, a list of devices for which distribution setting is determined to be impossible and an error reason that each device cannot be set for distribution are displayed in 520.
After the operator confirms the content of the error, when the “return” button 523 is pressed, the distribution system 10 returns to the screen of FIG. 7A or FIG. Can be encouraged. In addition, in order to confirm the content of the error, by pressing a “result output” button 522, a file outputting a list of devices and reasons for errors can be downloaded to a PC or the like on which the Web browser 302 or the like operates. If there are devices that can be distributed in the selected device group, the “Next” button 521 is enabled, and the list of devices that can be distributed is targeted by pressing the “Next” button 521. As shown in FIG.

  8 and 9 are examples of screens for performing FW distribution settings for the device group selected in FIG. 7B. 8 corresponds to the screen before the FW to be distributed is specified, and FIG. 9 corresponds to the screen after the FW to be distributed is specified. The screen of FIG. 9 is the same screen as FIG. 8 except that the FW to be distributed is specified, and the same number indicates the same function, so FIG. 8 and FIG. 9 will be described together.

  First, on the screen of FIG. 8, the service person designates the version of FW to be distributed to the selected device group. The public section 530 is a radio button for selecting the public section of the FW to be selected. When “Normal FW” 531 is selected, the FW version to be distributed is designated by selecting the FW version from the “Distributed firmware Ver.” Menu. On the other hand, when “specific FW” 532 is selected, an “acquisition ID” specifying the specific FW and a “password” corresponding to the acquisition ID are input to specify the version of the FW to be distributed. In either case, by inputting information specifying the FW version and pressing the “Search” button 533, the distribution system 10 searches for the version of the target FW and makes a transition to the screen shown in FIG.

  In the screen of FIG. 9, 534 and 535 are updated with the information of the FW version searched based on the designation of the above 530 to 532. 534 is the name of the version of FW to be distributed. Reference numeral 535 denotes a version of FW to be distributed. As described above, when the FW version to be distributed is determined and the state of FIG. 9 in which 534 and 535 are displayed, the “Register” button 547 of the FW distribution setting which is invalid in FIG. 8 becomes valid.

  In 545, the list of devices to be distributed is displayed together with the device ID of each device and the current FW version (“Current FW Ver.”), And it is possible to input “distribution date” and “application date” for each target device. It has become. In 545, individual values (distribution date / time, application date / time) can be input for each device, but can also be input to all target devices at once using 540-544.

  Reference numeral 540 denotes a reference delivery date input unit for collectively setting delivery dates. Reference numeral 541 denotes a delivery date and time setting interval for a plurality of devices. By pressing the “apply” button (542) after entering values in 540 and 541, the value of “delivery date” in 545 can be set in a batch.

  Reference numeral 543 denotes an application date and time input unit for collectively setting application dates and times. By pressing the “apply” button (544) after inputting 543, the “applied date and time” values of 545 can be set collectively. After inputting the distribution setting in this way, the registration of the FW distribution setting is completed by pressing the “Register” button 547. That is, the distribution system 10 registers the input FW distribution setting in the FW distribution management table 337 (for example, FW update reservation registration 461 in FIG. 6).

  Reference numeral 546 denotes a “return” button for returning to the previous screen. By depressing a “return” button 546, the screen shown in FIG. 7A is restored and the device can be selected again.

  Reference numeral 548 denotes a “registration deletion” button for registering and deleting the delivery setting of the selected device. By depressing a “registration deletion” button 548, registration of the FW distribution setting of the selected device (that is, each device displayed in 545) can be deleted.

When the FW distribution setting is registered on the screen shown in FIG. 9, the FW distribution information record of the FW distribution management table 337337 (Table 11) is added.
As shown in Table 11, the FW distribution information includes a list of combinations of distribution ID, device ID, device model, version, distribution date / time, application date / time, distribution status, and the like. The distribution ID is set by generating a unique identifier when a record of FW distribution information is added.

Next, FW periodic update setting will be described with reference to FIGS. 10A and 10B.
FIG. 10A (a) shows an example of a screen for performing FW periodic update settings.
In FIG. 10A (a), first, in 551 and 552, in order to select a plurality of target devices for which the FW periodic update setting is to be performed, a search condition for narrowing down devices under a specific condition is input.

Reference numeral 551 denotes a check box for designating a distribution status in the current FW periodic update setting of each target device. Reference numeral 552 denotes a check box for designating the current FW periodic update setting state (whether or not to perform periodic update). After specifying the target device conditions in 551 and 552, by pressing the “Search” button 553, the distribution system 10 changes to the screen of FIG. 10A (b), and the device list that matches the search conditions is changed to 560. Display.
When the “reset” button (554) is pressed, the distribution system 10 resets the search conditions set in 551 and 552 and returns to the initial screen of FIG. 10A (a).

  The operations 500 to 554 in FIG. 10A (b) are the same as those in FIG. 10A (a), and the device list displayed in FIG. 10A (b) can be updated while changing the search conditions. As a result, it is an operation method that allows a user to select a device for which a periodic update is to be set while searching through trial and error.

  In FIG. 10A (b), a device for distribution setting is further selected from the device list (target device list) 560 narrowed down by the search condition. In the target device list 560, the following information of a plurality of devices searched under the above-described conditions is displayed in order from the left. For example, “device ID”, “current FW Ver.”, “Applied FW Ver.”, “Application status (distribution)”, “application status (setting)”, “FW distribution status”, “FW regular update status” , “Application distribution status”, “regular update setting”, “confirmation time”, “application time”, and the like are displayed.

  “Device ID”, “Current FW Ver.”, “After Application FW Ver.”, “Application Status (Distribution)”, “Application Status (Setting)”, “FW Distribution Status”, “FW Regular Update Status” The “application distribution status” is the same as that described as the content displayed in FIG.

  “Regular update setting” indicates the state of the periodic update setting. In “regular update setting”, “ON” is displayed when the setting is to perform periodic update, and “OFF” is displayed when the setting is not. “Confirmation time” indicates a time setting in which the device 400 confirms whether there is an updated FW in the distribution system 10 in the periodic update setting. In the “confirmation time”, a periodic confirmation period, day of the week, and time are displayed, such as “every Monday from 4:00 to 7:00” and “every other Saturday from 22:00 to 1:00”. “Applied time” indicates the installation execution time when the FW is distributed.

  In addition, in the target device list 560, a check box for selecting a periodic update setting target device is added, similarly to 510 in FIG. 7B. In the target device list 560, when a plurality of devices subject to periodic update setting are selected and the “next” button 555 is pressed, the screen transitions to the screen shown in FIG. 10B (c). By pressing the “Next” button 555, the distribution system 10 may determine whether or not the distribution setting is possible for each selected device, as in the case of the FW distribution setting. The determination as to whether or not the distribution setting is possible is made by checking the existence of different types of distribution settings with reference to the FW distribution management table 337, the application distribution management table 336, and the like.

FIG. 10B (c) is an example of a screen for performing regular update settings for the selected device group.
In the regular update setting, at 576, whether or not to perform regular update for each device (“ON” / “OFF”), a periodic check cycle, and mail transmission are set. In “Regular Update Settings”, set whether to perform regular updates (“ON” / “OFF”).

  In "Confirmation time", set the periodic confirmation cycle ("Weekly" / "Biweekly"), day of the week, and confirmation time. Set the installation execution time in "Applicable date and time". In “E-mail address”, a mail transmission destination when FW distribution is carried out is set by periodic confirmation, and in “Comment”, a comment included in the mail content at the time of mail transmission is set.

  Note that these settings can be collectively set for the entire device listed in 576. In 570, whether or not to perform periodic update is set ("ON" / "OFF"). In 571, the periodic confirmation cycle ("every week" / "biweekly"), day of the week, and confirmation time are set. In 572, the installation execution time is set. In 573, a mail transmission destination when FW distribution is performed is set by periodic confirmation, and in 574, a comment included in the mail content at the time of mail transmission is set. When the “Apply” button 575 is pressed after the above settings are made, the same value is collectively set for all the devices displayed as a list in 576. After inputting the regular update settings in this way, the registration of the regular update settings is completed by pressing the “Register” button 578. That is, the distribution system 10 registers the input regular update information in the regular update setting management table 338 (for example, FW update reservation registration 461 in FIG. 6).

  Reference numeral 577 denotes a “return” button for returning to the previous screen. By depressing a “return” button 577, it is possible to return to the screen of FIG. 7A and select a device again.

  Reference numeral 579 denotes a “registration delete” button for registering and deleting the periodic update setting of the selected device. By depressing a “registration deletion” button 579, the registration of the periodic update setting of the selected device (that is, each device displayed in 576) can be deleted.

When the FW periodic update setting is registered on the screen shown in FIG. 10B (c), a record of periodic update information is added to the periodic update setting management table 338 (Table 12).
As shown in Table 12, the periodic update information includes a list of combinations of distribution ID, device ID, periodic update setting, confirmation time, application time, email address, comment, distribution status, and the like. The distribution ID is set by generating a unique identifier when a record of periodic update information is added.

Next, application distribution settings will be described with reference to FIGS.
FIG. 11A shows an example of a screen for performing application distribution settings.
In FIG. 11A, first, in order to select a plurality of target devices for which application distribution settings are to be made, a search condition for narrowing down devices with specific conditions is input.
Reference numeral 580 denotes a check box for designating the distribution status of the current application distribution setting of each target device.

  Reference numerals 581, 600, and 601 are items for inputting search conditions for narrowing down the devices according to the applications and versions installed in the devices. In the present embodiment, the method for specifying the application and version can be selected from two methods: a method by specifying a name and version number, and a method of specifying an application registration number that uniquely specifies the version of the application. Reference numeral 581 denotes a radio button for designating a search type for selecting these methods. When “application name” is selected in 581, the device is narrowed down by designating the name and version of the application on the screen shown in FIG. If “registration number” is selected in 581, the screen shifts to the screen shown in FIG. Further, in the screen shown in FIG. 13A, when “application name” is selected in 581, the screen transits to the screen shown in FIG.

  Reference numeral 600 denotes a drop-down menu for displaying and selecting a list of application names from applications currently installed on the device. Reference numeral 601 denotes a check box for selecting a version corresponding to the application with the name selected in 600. By selecting a plurality of application names and versions in 600 and 601 and then pressing the “Search” button 586, it is possible to narrow down the devices to which the designated application and version are installed. That is, a screen as shown in FIG. 12 described later is displayed.

  In addition, on the screen shown in FIG. 11, a distribution target application is also designated. That is, since the update target application needs to be installed on the device side, specifying the distribution target application also narrows down the devices on which the application is installed. In the screen shown in FIG. 11A, after selecting an application name in 600, pressing the “candidate search” button transitions to the screen shown in FIG.

  In the screen shown in FIG. 11B, in 584, the list information of another version that can be updated returned from the license management system 40 can be selected corresponding to the application name designated by 600. . Reference numeral 584 denotes a drop-down menu for designating the version of the distribution target application. Corresponding to the version of the application selected in 584, the application name managed by the license management system 40 is displayed in 583, and the registration number of the application is displayed in 585.

  After specifying the target device conditions in 580, 581, 600, 601 and pressing the “Search” button 586, the screen shown in FIG. 12 is displayed, and the device list (target device list) that matches the search conditions is 589. Is displayed. When the “reset” button 587 is pressed, the search conditions set in 580, 581, 600, and 601 are reset, and the screen returns to the initial screen in FIG.

  The operations of 580, 581, 600, 601, 586, and 587 in FIG. 12 are the same as those in FIG. 11, and the device list displayed in FIG. 12 can be updated while changing the search conditions. Thereby, it is an operation method capable of selecting a device targeted for application distribution setting while searching through trial and error.

  In FIG. 12, a device targeted for application distribution setting is further selected from the device list (target device list) 589 narrowed down by the search condition. The target device list 589 displays the following information in order from the left for a plurality of devices searched under the above conditions. For example, “device ID”, “current application name: Ver.”, “Application name after application: Ver.”, “Application status (distribution)”, “delivery reservation date / time”, “FW distribution status”, “FW regular update” Information such as “status”, “application delivery status”, “post-delivery status”, “remote delivery”, “FW Ver.”, Etc. is displayed.

  The “device ID” is the same as that described as the content displayed in FIG. “Current application name: Ver.” Indicates a plurality of combinations of names and versions of applications currently installed in the device. “App name after application: Ver.” Indicates one combination of the name and version of the last application distributed and applied to the device.

  “Applied status (distribution)” indicates an app distribution availability status of the device in the app distribution setting. If the app information of the device has not been acquired and it is not possible to determine whether or not distribution is possible, “not applicable” is displayed. Otherwise, it will be displayed blank.

“Distribution reservation date / time” indicates the application distribution reservation date / time in the application distribution setting reserved for the device (for example, 445 in FIG. 5).
The “FW distribution status”, “FW regular update status”, and “application distribution status” are the same as those described as the contents displayed in FIG.
The “post-delivery state” indicates the activation state of the application after the application is distributed to the device in the application distribution setting reserved for the device. As the activation state, one of “activation”, “stop”, and “unknown” is displayed.

  “Remote distribution” indicates whether or not remote distribution setting of an application to the device is permitted. “FW Ver.” Is the same as “Current FW Ver.” Described as the content displayed in FIG.

  In addition, the target device list 589 includes a check box for selecting an application distribution setting target device, as in 510.

  FIG. 13A shows an example of a screen for setting application distribution when a registration number is designated as a search type. Reference numerals 580 and 581 are as described on the screen shown in FIG. In FIG. 13A, reference numeral 582 denotes an item for inputting a search condition for narrowing down a device by an app installed in the device by designating a registration number of the app. In 582, the registration number and password of the application are input, and the “registration number search” button is pressed, so that the screen shown in FIG.

  In the screen shown in FIG. 13B, the application name, version, and registration number corresponding to the application registration number are displayed on 583, 584, and 585. In this state, the distribution target application is designated by the contents displayed in 583, 584, and 585. In addition, a search condition for narrowing down a device in which the designated application is installed is designated. When the “Search” button 586 is pressed here, the screen shown in FIG. 14 is displayed, and a device list that matches the search conditions is displayed in 589. When the “reset” button 587 is pressed, the search conditions set in 580, 581, and 582 are reset, and the screen returns to the initial screen in FIG.

The operations of 580, 581, 582, 586, and 587 in FIG. 14 are the same as those in FIG. 13, and the device list displayed in FIG. 14 can be updated while changing the search conditions. Thereby, it is an operation method capable of selecting a device targeted for application distribution setting while searching through trial and error.
Further, the screen shown in FIG. 14 displays the same information as the content shown in FIG. The only difference is that the search type is a registration number.

  In 589 shown in FIG. 12 or FIG. 14, by selecting a plurality of distribution target devices and pressing the “Next” button 588, the distribution system 10 determines whether or not distribution setting is possible for each selected device. I do. The determination of whether or not the distribution setting is possible is made by checking the existence of different types of distribution settings with reference to the FW distribution management table 337 and the periodic update setting management table, and by inquiring the license management system 40 corresponding to 435 and 436 in FIG. .

  Here, when there is a device that cannot be distributed, the distribution system 10 shifts to the screen of FIG. 7C, while when all the devices can be distributed, the screen shifts to the screen shown in FIG. Let

  In FIG. 7C, as in the case of FW distribution, a list of devices for which distribution setting is determined to be impossible and an error reason that each device cannot be set for distribution are displayed in 520. In this case, after confirming the content of the error, by pressing the “return” button 523, the screen can be returned to the screen of FIG. 14 and the device can be selected again. If there are devices that can be distributed in the selected device group, the “Next” button 521 is enabled, and the list of devices that can be distributed is targeted by pressing the “Next” button 521. As shown in FIG.

FIG. 15 is an example of a screen for performing application distribution settings for a selected device group.
In the application distribution setting, since the distribution target application is determined at the device selection stage, the information is displayed in the application name 590, the version 591, and the registration number 592.

  At 596, for each device, the device ID and the name and version of the target app installed on that device are displayed. Further, in 596, “delivery date”, “delivery time”, and “post-delivery state” can be individually set. As the “post-delivery state”, any of “start”, “stop”, and “continue” can be designated.

  These settings can be collectively set for the entire device listed in 596. In 593, “delivery date” and “delivery time” are set. In 594, “post-delivery state” is set. When the “Apply” button 595 is pressed after setting the above, the same value is collectively set for all devices displayed in a list in 596. After inputting the application distribution setting in this way, pressing 598 completes registration of the application distribution setting. That is, the distribution system 10 registers the input application distribution setting in the application distribution management table 336.

  Reference numeral 597 denotes a “return” button for returning to the previous screen. By depressing a “return” button 597, it is possible to return to the screen of FIG. 7A and select a device again.

  Reference numeral 599 denotes a “registration deletion” button for registering and deleting the application distribution setting of the selected device. By depressing a “registration deletion” button 599, the registration of the application distribution setting of the selected device (that is, each device displayed in 596) can be deleted.

When application distribution settings are registered on the screen shown in FIG. 15, a record of application distribution information in the application distribution management table 336 (Table 10) is added.
As shown in Table 10, the application distribution information includes a list of combinations of distribution ID, device ID, application ID, version, file ID, distribution date and time, post-distribution status, distribution status, and the like. The distribution ID is set by generating a unique identifier when a record of application distribution information is added.

Next, the distribution reservation process of the distribution system will be described with reference to FIGS.
FIG. 16 is a flowchart illustrating FW distribution reservation processing by the distribution system 10. The processing shown in FIG. 16 is the content processed by the distribution setting control unit 314 corresponding to 460 to 461 in the sequence of FIG. 6, and the screen display controlled by the Web browser 302 is shown in FIGS. Corresponds to the screen display shown in.
16 and FIGS. 17 and 18 to be described later are realized by the CPU of the server constituting the distribution system 10 reading and executing the program stored in the HDD or the like.

Corresponding to 460 in the sequence of FIG. 6, the distribution setting control unit 314 starts processing from S1000.
First, in S1001, the distribution setting control unit 314 branches the process based on each distribution setting type corresponding to the input of the setting type 500 on the screen of FIG. When the FW distribution setting is advanced, the distribution setting control unit 314 advances the process to S1004. When the FW periodic update setting is selected, the distribution setting control unit 314 advances the process to S1200. The processing after S1200 will be described later with reference to FIG. If the application distribution setting is selected, the distribution setting control unit 314 advances the process to S1400. The processing after S1400 will be described later with reference to FIG.

  In S1004, the distribution setting control unit 314 determines whether or not the “Search” button 504 in FIG. 7 has been pressed (that is, device search is instructed) (S1004). If it is determined that the “Search” button 504 in FIG. 7 has not been pressed (No in S1004), the distribution setting control unit 314 continues to display FIG. 7 (until the “Search” button 504 is pressed. The search condition input is accepted on the screen as shown in FIG.

On the other hand, when it is determined that the “search” button 504 has been pressed (Yes in S1004), the distribution setting control unit 314 advances the process to S1005.
In step S1005, the distribution setting control unit 314 performs control such that a device list corresponding to the search condition is displayed on the web browser 302 as illustrated in FIG. Here, when the FW has been updated before, a search is performed according to the information acquired from the device in 477 of FIG. 6, and the target device list is displayed.

Next, in S1006, the distribution setting control unit 314 receives an input for device selection on the screen as shown in FIG.
Next, in S1007, the distribution setting control unit 314 determines whether or not the “Next” button 506 in FIG. If it is determined that the “next” button 506 has not been pressed (No in S1007), the distribution setting control unit 314 returns the process to S1006 and accepts an input of device selection.

On the other hand, when it is determined that the “next” button 506 is pressed (Yes in S1007), the distribution setting control unit 314 advances the process to S1008.
In S1008, for each device selected in S1006, the distribution setting control unit 314 has information obtained from the device in 477 in FIG. To determine whether or not delivery setting is possible. For example, it is determined that distribution setting is not possible for a device for which the above information cannot be acquired. Further, it is determined that the distribution setting is not possible for a device for which an application distribution setting or a periodical update setting “waiting for distribution” or “during distribution” is reserved. In addition, it is determined that distribution setting is possible for devices other than those described above. The distribution setting control unit 314 also performs processing for selecting a version of FW that can be updated in common for the selected device group.

  In S1009, the distribution setting control unit 314 determines whether there is a device for which distribution setting is not possible in the determination in S1008. If it is determined that there is a device for which distribution setting is impossible (Yes in S1009), the distribution setting control unit 314 advances the process to S1010.

  In S1010, the distribution setting control unit 314 controls the Web browser 302 to display information about devices for which distribution setting is impossible, as shown in the screen of FIG. If the distribution setting control unit 314 determines that the “Next” button 521 is pressed on the screen of FIG. 7C, the process proceeds to S1011.

  On the other hand, when it is determined that there is no device that cannot be set for distribution (No in S1009), that is, when distribution setting is possible for all selected devices, the distribution setting control unit 314 proceeds to S1011 as it is. Proceed.

  In step S1011, the distribution setting control unit 314 performs control so that a distribution setting screen as illustrated in FIG. At this time, the distribution setting control unit 314 performs control so that the FW version that can be updated in common for the selected device group is a candidate for the firmware version to be distributed.

Next, in S1012, the distribution setting control unit 314 determines whether or not the “delete registration” button 548 is pressed on the screen of FIG.
If it is determined in S1012 that the “registration delete” button 548 has been pressed (Yes in S1012), the distribution setting control unit 314 advances the process to S1213.
In S1013, the distribution setting control unit 314 performs a process of deleting the registration of the distribution setting of the device selected in S1006, and ends the process of this flowchart (S1018).

In S1012, if it is determined that the “registration deletion” button 548 has not been pressed (No in S1012), the distribution setting control unit 314 advances the process to S1214.
In S1014, the distribution setting control unit 314 accepts input of the FW version to be distributed, and when the “Search” button 533 is pressed, the process proceeds to S1015.

In step S1015, the distribution setting control unit 314 displays a distribution setting screen as shown in FIG. 9 on the Web browser 302, and controls to accept an input of distribution settings via the distribution setting screen.
Also, the distribution setting control unit 314 determines whether or not the “Register” button 547 has been pressed (S1016). If it is determined that the “Register” button 547 has not been pressed (No in S1016), the distribution setting control unit 314 returns to S1012 and continues to accept version selection and distribution setting input.

If it is determined that the “Register” button 547 has been pressed (Yes in S1016), the distribution setting control unit 314 advances the process to S1017.
In S1017, the distribution setting control unit 314 performs processing for registering the distribution setting of the FW version to be distributed to the device selected in S1006. If other distribution settings exist for the selected device, the distribution settings here may be registered again after canceling the distribution settings. After the process of S1017, the distribution setting control unit 314 ends the process of this flowchart (S1018).

  FIG. 17 is a flowchart illustrating the FW regular update setting process by the distribution system 10. The processing shown in FIG. 17 is the content processed by the distribution setting control unit 314 corresponding to 460 to 461 in the sequence of FIG. 6, and the screen display controlled by the Web browser 302 is shown in FIGS. 10A and 10B. Corresponds to the screen display shown in.

  When the process proceeds from S1001 in FIG. 16 to S1200, the distribution setting control unit 314 performs control so that the screen as illustrated in FIG. 10A (a) is displayed on the Web browser 302, and the process proceeds to S1201. As described with reference to FIG. 7, it is possible to proceed to the processing of FIG. 16 or 18 by selecting the setting type 500 from FIG. 17, but it is omitted in this flowchart.

  In S1201 of FIG. 17, the distribution setting control unit 314 determines whether the “search” button 553 of FIG. 10A is pressed (that is, device search is instructed). If it is determined that the “Search” button 553 in FIG. 10A has not been pressed (No in S1202), the distribution setting control unit 314 performs the process until the “Search” button 553 is pressed in FIG. 10A (a). Alternatively, control is performed so as to accept input of search conditions on the screen of FIG. 10A (b).

On the other hand, when it is determined that the “Search” button 553 is pressed (Yes in S1201), the distribution setting control unit 314 advances the process to S1202.
In S1202, the distribution setting control unit 314 performs control so that a device list corresponding to the search condition is displayed on the Web browser 302 as in the screen illustrated in FIG. 10A (b). Here, when the FW has been updated before, a search is performed according to the information acquired from the device in 477 of FIG. 6, and the target device list is displayed.

Next, in S1202, the distribution setting control unit 314 accepts an input for device selection on the screen as shown in FIG. 10A (b).
Next, in S1203, the distribution setting control unit 314 determines whether or not the “Next” button 555 in FIG. 10A (b) has been pressed. If it is determined that the “Next” button 555 has not been pressed (No in S1203), the distribution setting control unit 314 returns the process to 1203 and accepts an input of device selection.

  On the other hand, when it is determined that the “next” button 555 has been pressed (Yes in S1204), the distribution setting control unit 314 advances the processing to S1205.

Although not shown, the distribution setting control unit 314 may perform the following processing in steps between S1204 and S1205.
For example, the distribution setting control unit 314 determines whether or not the periodic update setting is possible for each device selected in S1203 according to the presence / absence of different types of distribution settings. For example, it is determined that periodic update setting is not possible for a device for which application distribution setting or FW distribution setting of “waiting for distribution” or “during distribution” is reserved, and periodic update setting is performed for a device whose distribution setting is not reserved. Judge that it is possible. If it is determined that there is a device that cannot be set for regular update, the distribution setting control unit 314 displays information about the device for which regular update setting is not possible, as shown in the screen of FIG. Control to display on browser 302. If the distribution setting control unit 314 determines that the “next” button 521 is pressed on the screen as shown in FIG. 7C, the process advances to step S1205. On the other hand, if the regular update setting is possible for all the selected devices, the process proceeds to S1205 as it is.

In step S1205, the distribution setting control unit 314 performs control so that the periodic update setting screen as illustrated in FIG.
Next, in S1206, the distribution setting control unit 314 determines whether or not the “registration deletion” button 579 is pressed on the regular update setting screen.

If it is determined in S1206 that the “registration delete” button 579 has been pressed (Yes in S1206), the distribution setting control unit 314 advances the process to S1207.
In S1207, the distribution setting control unit 314 performs processing for deleting registration of the distribution setting of the device selected in S1203, and ends the processing of this flowchart (S1211).

If it is determined in S1206 that the “registration deletion” button 548 has not been pressed (No in S1206), the distribution setting control unit 314 advances the process to S1208.
In S1208, the distribution setting control unit 314 performs control so as to accept an input of regular settings via the screen of FIG. 10B (c).
Also, the distribution setting control unit 314 determines whether or not the “Register” button 578 has been pressed (S1209). If it is determined that the “Register” button 578 has not been pressed (No in S1209), the distribution setting control unit 314 returns the process to S1206 and continues to accept input of periodic settings.

If it is determined that the “Register” button 578 has been pressed (Yes in S1209), the distribution setting control unit 314 advances the process to S1210.
In S1210, the distribution setting control unit 314 performs processing for registering the periodic update setting for the device selected in S1203. After the process of S1210, the distribution setting control unit 314 ends the process of this flowchart (S1211).

  FIG. 18 is a flowchart illustrating an application distribution reservation process by the distribution system 10. The processing shown in FIG. 18 is the content processed by the distribution setting control unit 314 corresponding to 440 to 445 in the sequence of FIG. 5, and the screen display controlled by the Web browser 302 is shown in FIGS. Corresponds to the screen display shown in.

  When the process proceeds from S1001 in FIG. 16 to S1400, the distribution setting control unit 314 performs control so that the screen as illustrated in FIG. 11A is displayed on the Web browser 302, and the process proceeds to S1401. As described with reference to FIG. 7, it is possible to proceed to the processing of FIG. 16 or 17 by selecting the setting type 500 from FIG. 18, but it is omitted in this flowchart.

  In S1401, the delivery setting control unit 314 branches to screen processing for each search type corresponding to the input of the search type 581 in FIG. When the search is advanced by the application name, the distribution setting control unit 314 advances the process to S1402. On the other hand, when the search is advanced using the registration number, the distribution setting control unit 314 advances the process to S1409.

  In S1402, the distribution setting control unit 314 displays a menu of a list of application names installed in the device at 600 on the screen of FIG. Here, when an application is updated before, a list of application names is displayed according to the information acquired from the device in 418 of FIG. 4 or 456 of FIG.

Next, in S1403, the distribution setting control unit 314 accepts an application name selection input from 600.
In S1404, the distribution setting control unit 314 determines whether “candidate search” 600 has been pressed. If it is determined that 600 “candidate search” has not been pressed (No in S1404), the distribution setting control unit 314 returns the process to S1403, and continues to accept an application name selection input from 600.

If it is determined in S1404 that “candidate search” of 600 has been pressed (Yes in S1404), the distribution setting control unit 314 advances the process to S1405.
In S1405, the distribution setting control unit 314 passes the application ID of the application name selected in S1403, makes an inquiry to the license management system 40, and acquires all the information of another version of the application with the application ID. This processing corresponds to 431 and 432 in FIG. In response to the inquiry, the license management system 40 searches the registered application management table 361 for information on the application with the matching application ID and returns it to the distribution system 10.

Next, in S1406, the distribution setting control unit 314 displays a menu of the list of versions acquired by the inquiry in S1406 on the screen 584 in the screen of FIG. 11B, and corresponds to the version selected in 584. The app name is displayed in 583, and the registration number is displayed in 585.
In S1407, the distribution setting control unit 314 accepts a version selection input from 584.

In step S1408, the distribution setting control unit 314 determines whether the “search” button 586 has been pressed. If it is determined that the “Search” button 586 has not been pressed (No in S1408), the distribution setting control unit 314 returns the processing to S1407 and continues to accept version selection.
On the other hand, if it is determined in S1408 that the “search” button 586 has been pressed (Yes in S1408), the distribution setting control unit 314 advances the process to S1414. The processing after S1414 will be described later.

  Further, when the search is advanced with the registration number in S1401, the distribution setting control unit 314 controls to display the screen as shown in FIG. 13A on the Web browser 302 in S1409, and FIG. The application registration number and password are received from 582 a).

  In S1410, the delivery setting control unit 314 determines whether “registration number search” 582 has been pressed. If it is determined that “registration number search” in 582 is not pressed (No in S1410), the distribution setting control unit 314 returns to S1409, and continues to input the application registration number and password from 582. Accept.

If it is determined that “registration number search” in 582 has been pressed (Yes in S1410), the distribution setting control unit 314 advances the process to S1411.
In step S1411, the distribution setting control unit 314 passes the registration number and password of the designated application, inquires the license management system 40, and acquires the corresponding application information. This processing corresponds to 431 and 432 in FIG. The license management system 40 searches the registered application management table 361 for information on the application that matches the registration number and password, and returns the information to the distribution system 10.

  In S1412, the distribution setting control unit 314 displays the application name acquired in 583, the version in 584, and the registration number in 585 on the screen of FIG. 13B based on the application information acquired in the inquiry of S1411. Control to do.

In S1413, the distribution setting control unit 314 determines whether the “search” button 586 has been pressed. If it is determined that the “Search” button 586 has not been pressed (No in S1413), the distribution setting control unit 314 returns the process to S1409, and continues to accept registration number input.
On the other hand, when it is determined in S1413 that the “search” button 586 has been pressed (Yes in S1413), the distribution setting control unit 314 advances the process to S1414.

  In S1414, the distribution setting control unit 314 searches and narrows down the search condition specified in FIG. 11B or 13B and the device in which the specified application is installed, and in FIG. 12 or FIG. Control is performed so that a list of devices is displayed on 589 of the illustrated screen. Here, when the application has been updated before, a search is performed according to the information acquired from the device at 418 in FIG. 4 or 456 in FIG. 5, and a target device list is displayed.

Next, in S1415, the distribution setting control unit 314 accepts an input for device selection on the screen illustrated in FIG. 12 or FIG.
In step S1416, the distribution setting control unit 314 determines whether “next” 588 has been pressed. If it is determined that “Next” 588 has not been pressed (No in S1416), the distribution setting control unit 314 returns the process to S1415 and continues to accept input for device selection.

If it is determined that “Next” 588 has been pressed (Yes in S1416), distribution setting control section 314 advances the process to S1417.
In S1417, the distribution setting control unit 314 determines whether or not distribution setting is possible for each device selected in S1415 according to the presence or absence of different types of distribution settings. For example, for a device for which “Waiting for delivery” or “Delivery” FW delivery setting or periodic update setting is reserved, it is determined that delivery setting is impossible, and “Waiting for delivery” or “Waiting” FW delivery setting or periodic It is determined that distribution setting is possible for a device for which update setting is not reserved.

  Furthermore, in S1418, the delivery setting control unit 314 passes the registration number of the app to be delivered and a list of the selected device IDs, makes an inquiry to the license management system 40, and determines whether or not delivery settings are possible for each device ID. Get the result. This processing corresponds to 435 and 436 in FIG. In response to the inquiry in S1418, the license management system 40 performs the processing shown in FIG. 19 and responds to the distribution system 10 with a determination result as to whether or not distribution setting is possible for each device ID.

Next, in S1419, the distribution setting control unit 314 determines whether there is a device that cannot be distributed based on the processing results of S1417 and S1418. If it is determined that there is a device for which distribution setting is impossible (Yes in S1419), the distribution setting control unit 314 advances the process to S1420.
In step S1420, the distribution setting control unit 314 displays information about a device that cannot be distributed as shown in the screen of FIG. If it is determined that the “Next” button 521 has been pressed, the distribution setting control unit 314 advances the process to S1421.

  On the other hand, if it is determined in S1419 that there is no device that cannot be distributed (Yes in S1419), that is, if distribution can be set for all selected devices, the distribution setting control unit 314 does not change the setting. The process proceeds to S1421.

In step S1421, the distribution setting control unit 314 performs control so that the distribution setting screen illustrated in FIG.
In S1422, the distribution setting control unit 314 determines whether or not the “registration delete” button 599 is pressed on the distribution setting screen.

If it is determined in S1422 that the “registration delete” button 599 has been pressed (Yes in S1422), the distribution setting control unit 314 advances the process to S1423.
In S1423, the distribution setting control unit 314 performs a process of deleting registration of the application distribution setting of the device selected in S1415, and ends the process of this flowchart (S1427).

On the other hand, when it is determined in S1422 that the “registration deletion” button 599 has not been pressed (No in S1422), the distribution setting control unit 314 advances the process to S1424.
In S1424, the distribution setting control unit 314 performs control so as to receive an input of application distribution settings.

Also, the distribution setting control unit 314 determines whether or not the “Register” button 598 has been pressed (S1425). If it is determined that the “Register” button 598 has not been pressed (No in S1425), the distribution setting control unit 314 returns the process to S1422 and continues to receive input of distribution settings.
If it is determined that the “Register” button 598 has been pressed (Yes in S1425), the distribution setting control unit 314 advances the process to S1426.

  In S1426, the distribution setting control unit 314 performs processing for registering application distribution settings for the device selected in S1415. If there is another distribution setting for each selected device, the distribution setting may be registered again after canceling the distribution setting. After the process of S1426, the distribution setting control unit 314 ends the process of this flowchart (S1427).

  FIG. 19 is a flowchart illustrating a process for determining whether or not an application can be distributed to a device by the license management system 40. Note that the processing shown in FIG. 19 corresponds to the content processed by the license management unit 353 in response to the inquiry in S1418 of FIG. Further, the processing of FIG. 19 is realized by the CPU of the server constituting the license management system 40 reading and executing a program stored in the HDD or the like.

  In S1600, the license management unit 353 receives a list of registration numbers and device IDs of applications to be distributed in response to an inquiry from the distribution system 10 (for example, 1418 in FIG. 18). The license management unit 353 performs control so that the processes of S1601 to S1608 are repeated for all device IDs received in the list.

In S1601, the license management unit 353 sequentially extracts one unprocessed device ID from the list (hereinafter “currently processed device ID”), and proceeds with the subsequent processing.
In S1602, the license management unit 353 searches the device unit license management table 365 and acquires a list of license IDs from the device IDs currently being processed.

Next, in S1603, the license management unit 353 searches the license management table 364, and acquires a list of product IDs from the list of license IDs acquired in S1602.
In step S1604, the license management unit 353 searches the installable version management table 363, and acquires a list of registration numbers from the list of product IDs acquired in step S1603.

Next, in S1605, the license management unit 353 determines whether or not the registration number passed from the distribution system 10 is included in the list of registration numbers acquired in S1604. If it is determined that the registration number passed from the distribution system 10 is included in the list of registration numbers (Yes in S1605), the license management unit 353 advances the process to S1606.
In S1606, the license management unit 353 adds the device ID currently being processed to the “distributable list”, and advances the process to S1608.

On the other hand, when it is determined that the registration number passed from the distribution system 10 is not included in the list of registration numbers (No in S1605), the license management unit 353 advances the process to S1607.
In S1607, the license management unit 353 adds the device ID currently being processed to the “non-distributable list”, and advances the process to S1608.

  In S1608, the license management unit 353 determines whether or not the processing of S1601 to S1607 has been performed for all device IDs. If it is determined that there is a device ID that has not been processed in S1601 to S1607 yet (No in S1608), the license management unit 353 returns the process to S1601 and processes the next unprocessed device ID. To migrate.

  On the other hand, if it is determined in S1608 that the processing of S1601 to S1607 has been performed for all device IDs (Yes in S1608), the license management unit 353 advances the processing to S1609, and displays “Distributable list” and “Distributable”. Return “List” to distribution system 10.

  As described above, the distribution system of this embodiment that receives distribution settings of different software types has a configuration in which a plurality of devices are selected as target devices on the same screen. However, the search screen for narrowing down devices in order to select a device to which software is to be distributed is configured to switch the screen for each software type. Further, the device list after the refinement search has a configuration for displaying the setting status of each software type for each device. With such a configuration, the setting screen is not complicated for any type of software distribution setting, and it is easy to consider that distribution settings do not conflict between different distribution setting types at the stage of device selection. It becomes. As a result, it is possible to sufficiently improve the operability of distribution settings for different software types by selecting a plurality of devices.

  Note that when a plurality of devices are selected and batch distribution setting is performed, there is a possibility that the distribution settings may conflict because various devices have different distribution settings. In the distribution system of the present embodiment, by displaying the status of various distribution settings in the device list in the distribution settings, it is possible to confirm the display of the device list in the distribution settings, and explicitly cancel, that is, delete the distribution setting registration individually Configure as you can. Thus, in the distribution system of the present embodiment, it is possible to perform distribution setting while appropriately determining the distribution setting status of the device. In the case where the distribution settings conflict, the existing distribution settings may be canceled by overwriting with the distribution settings set later.

  In addition, according to the present embodiment, it is possible to improve the screen display performance when a plurality of devices, such as an app, that have different versions that can be updated for each device are collectively set. For example, if it is determined whether or not distribution is possible for all devices during a search for narrowing down devices, it takes time according to the number of devices. However, as in this example, at the stage of selecting the application and version, the screen display process for selecting the target device is not performed by performing a search only on the application installed on the device, without determining whether or not the device can be distributed. Operability can be improved. Furthermore, at the stage after selecting the target device, it can be set so that only the devices that can be distributed can be distributed as usual without degrading the operability of device selection by determining whether each device can be distributed. Became.

  In the above embodiment, the system for distributing software to an image forming device such as a multifunction peripheral has been described as an example. However, the device for distributing software by the system of the present invention is not limited to an image forming device. Absent. Any device may be used as long as it can receive distribution of plural types of software such as application software and firmware. For example, it may be a network home appliance or an information processing apparatus such as a navigation system, a network camera, or a personal computer.

  As described above, in the target device refinement search, only conditions according to the type of content to be distributed (software, etc.) are displayed and simplified. On the other hand, when selecting the target device, distribution of other content types is performed. The configuration status is displayed at the same time. With such a configuration, even in an environment where distributions of different content types coexist, it is possible to set distribution to a plurality of devices without competition without reducing operability.

In addition, the structure of the various data mentioned above and its content are not limited to this, You may be comprised with various structures and content according to a use and the objective.
Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium. Specifically, the present invention may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.
Moreover, all the structures which combined said each Example are also contained in this invention.

(Other examples)
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in the computer of the system or apparatus read and execute the program This process can be realized. 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 an apparatus composed of one device.
The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and these are excluded from the scope of the present invention. is not. That is, the present invention includes all the combinations of the above-described embodiments and modifications thereof.

Claims (8)

A software distribution system that manages a first distribution setting for reserving application distribution and a second distribution setting for reserving firmware distribution for a plurality of devices,
Accepting means for accepting selection of either the first delivery setting or the second delivery setting;
When performing the first distribution setting, when a distribution target application is selected, a first inquiry unit that inquires a license management system for information on a version that can be distributed of the application selected as the distribution target;
A first user interface that accepts selection of a version to be distributed and selection of one or a plurality of devices that distribute the selected version of the application based on the inquiry result by the first inquiry means. Providing means;
Second inquiry means for inquiring of the license management system whether the version of the application to be distributed selected according to the first user interface is applicable to each of the selected devices;
A second user interface for accepting a first distribution setting for reserving distribution of the version of the distribution target application is provided to each device determined to be applicable based on the inquiry result of the second inquiry means. A second providing means;
First registration means for registering the first distribution setting received in accordance with the second user interface;
When performing the second distribution setting, when one or a plurality of devices for distributing firmware is selected, whether or not the firmware can be distributed to the selected one or more devices is determined based on whether the second device is selected. Determining means for determining based on registration of one distribution setting;
Third providing means for providing a third user interface for accepting a second distribution setting for reserving distribution of firmware for each device determined to be capable of distributing firmware by the determination means;
Second registration means for registering the second delivery setting received in accordance with the third user interface;
A software distribution system comprising:   The first user interface includes means for selecting one of the deliverable versions of the application selected as the distribution target, and each device on which the application selected as the distribution target is installed. The software distribution system of claim 1, further comprising means for presenting information and selecting one or more devices from each device.   The first user interface presents information on the first distribution setting and the second distribution setting registered for each device in which the application selected as the distribution target is installed. The software distribution system according to claim 2, wherein:   The second user interface is capable of accepting each first distribution setting for each selected device determined to be applicable to the version of the application selected as the distribution target, collectively or individually. The software distribution system according to any one of claims 1 to 3.   The said 2nd user interface does not receive the 1st delivery setting with respect to each said selected device judged that the version of the application selected as said delivery object cannot be applied, Any one of Claims 1-4 characterized by the above-mentioned. The software distribution system according to claim 1.   When performing the second distribution setting, selection of one or a plurality of devices for distributing firmware by presenting information on the first distribution setting and the second distribution setting registered for each device 6. The software distribution system according to claim 1, further comprising a fourth providing unit that provides a fourth user interface that receives the information.   The software distribution according to any one of claims 1 to 6, wherein the third user interface does not accept a second distribution setting for each device for which the determination unit determines that the firmware cannot be distributed. system. A software distribution method in a software distribution system for managing a first distribution setting for reserving application distribution and a second distribution setting for reserving firmware distribution for a plurality of devices,
An accepting step of accepting selection of which of the first distribution setting and the second distribution setting to perform;
A first inquiry step of inquiring a license management system for information on a deliverable version of the application selected as the distribution target when the distribution target application is selected when performing the first distribution setting;
A first user interface that accepts selection of a version as a distribution target and selection of one or a plurality of devices that distribute the selected version of the application based on the inquiry result in the first inquiry step. 1 providing step;
A second inquiry step for inquiring of the license management system whether the version of the application to be distributed selected according to the first user interface is applicable to each of the selected devices;
A second user interface that accepts a first distribution setting for reserving distribution of the version of the distribution target application is provided to each device determined to be applicable based on the inquiry result in the second inquiry step. A second providing step,
A first registration step of registering the first distribution setting received in accordance with the second user interface;
When performing the second distribution setting, when one or a plurality of devices for distributing firmware is selected, whether or not the firmware can be distributed to the selected one or more devices is determined based on whether the second device is selected. A determination step for determining based on registration of one distribution setting;
A third providing step of providing a third user interface for accepting a second delivery setting for reserving the delivery of firmware for each device determined to be capable of delivering the firmware in the judging step;
A second registration step of registering the second delivery setting received in accordance with the third user interface;
A software distribution method characterized by comprising:

Images