JP2017134541A - Information processing device and software update method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce labor of generation of an update program.SOLUTION: A software update method executed by an information processing device according to one embodiment comprises a step for applying an update program. The step for applying the update program is configured to apply the update program, after returning a state of a software to a state before an individual update program is applied when the update program is applied to the software to which the individual update program is applied. The individual update program is distributed to an information processing device which is used by a first user group of the software. The update program is distributed to an information processing device used by a second user group containing the first user group.SELECTED DRAWING: Figure 5

Description

  The present invention relates to an information processing apparatus and a software update method.

  An update program for updating (updating) software such as an operating system (OS) and applications installed in the information processing apparatus is created and distributed. For example, the user can update the software by applying the distributed update program to the update target software installed in the information processing apparatus.

  In addition, for example, in some software, a problem that affects the work of some users, such as a user belonging to a specific corporation, may be detected. In this case, in order to suppress the impact on the work of some users, apart from distributing the update program for the information processing devices of all users of the software, individual update programs are released quickly to deal with the problems. Sometimes. The individual update program is released at an early timing after, for example, performing a minimum operation check. Therefore, for example, the individual update program is distributed to information processing apparatuses used by some users who are affected by work, and the user The present invention is applied only to software installed in a group of information processing apparatuses.

  In this regard, there is known a technique for returning to a combination of program versions before update even if an error occurs during the update of a plurality of programs. (For example, patent document 1) Moreover, the technique for providing the information storage device which can cope with the accident resulting from the update of a program etc. in a short time, and its download method is known. (For example, patent document 2) The technique for shortening the service stop period accompanying firmware update is known. (For example, Patent Document 3)

JP, 2014-6571, A JP 2001-117780 A JP 2013-161401 A

  As described above, in some software, an individual update program may be quickly released for software installed in an information processing apparatus used by some users to update the software. However, in this case, since the software is modified by applying an individual update program, for example, if a normal update program targeted for information processing apparatuses of all users is applied thereafter, there is a possibility of causing a problem. Therefore, in order to update the software to which the individual update program is applied, another individual update program corresponding to the normal update program may be separately created. As a result, problems such as increased time for creating and verifying the update program and complicated software version management may occur. In one aspect, an object of the present invention is to provide a technique capable of reducing labor for creating an update program.

  The software update method executed by the information processing apparatus according to one aspect of the present invention includes a step of applying an update program. In the step of applying the update program, when the update program is applied to software to which the individual update program is applied, the update program is applied after returning the software to the state before applying the individual update program. The individual update program is distributed to the information processing apparatus used by the first user group of software. The update program is distributed to the information processing apparatus used by the second user group including the first user group.

  The effort for creating the update program can be reduced.

It is a figure which illustrates the update of software. It is a figure which illustrates the case where an individual update program is applied to software. It is a figure which illustrates the functional block structure of the information processing apparatus which concerns on embodiment. It is a figure which illustrates the map of the information memorize | stored in the memory | storage part, and the structure of an application system area | region. It is a figure which illustrates the update process of the software which concerns on embodiment. It is a figure which shows the example of application of embodiment. It is a figure which illustrates the hardware constitutions of the computer for implement | achieving the information processing apparatus which concerns on embodiment.

  Hereinafter, some embodiments of the present invention will be described in detail with reference to the drawings. In addition, the same code | symbol is attached | subjected to the corresponding element in several drawing.

  FIG. 1 is a diagram illustrating software update. In FIG. 1, the version of certain software installed in the information processing apparatus 100 of model name: F-OA is changed from version (V (N-1) updated in the (N-1) th update to N The case of updating to version: V (N) in the second update is illustrated. Note that the information processing apparatus 100 may include, for example, a smartphone, a mobile phone, a tablet terminal, a personal computer (PC), a notebook PC, and the like. The software may be arbitrary software, for example, an OS and an application. The software may be updated using, for example, a FOTA (Firmware On-The-Air) method, or may be updated using another method. For example, the company that provides the software creates an update program from the data difference between the updated version: V (N) software and the pre-update version: V (N-1) software, and uploads it to the server. To distribute (generation / distribution (1) in FIG. 1). In the example of FIG. 1, one update program is created for the (N−1) th to Nth updates. For example, the user of the information processing apparatus 100 downloads a software update program from the server, applies the software to the software, and updates (updates) the software (update (1) in FIG. 1).

  In addition, as described above, an individual update program for software installed in an information processing apparatus used by some users may be quickly released (released) and applied. For example, in a certain software, when a problem that affects the work of some users is detected, the problem is corrected for the information processing apparatus used by the some users in order to suppress the influence on the work. Individual updates are released sooner. Note that some users may be users belonging to a specific corporation, for example. In this case, the update program is distributed only to information processing devices used by some users who are affected by the business, and is applied only to software installed in the information processing devices of the user group. In the following description, an update program distributed only for information processing apparatuses used by some users may be referred to as an individual update program. Further, for example, an update program that is not limited to an information processing apparatus used by some users may be referred to as a normal update program. The normal update program may be distributed to information processing apparatuses for all users, for example.

  FIG. 2 is a diagram illustrating a case where an individual update program is applied to software. FIG. 2 illustrates a case where the Nth normal update program is applied after the N-1th normal update program is applied. The individual update program for company A and the individual update program for company B are released during the release period of these two normal update programs. In this case, for example, the information processing apparatus 100 of a normal user to which the individual update programs other than the company A and the company B are not applied is updated by the application of the N-1th normal update program: V (N -1) Software A is used. Therefore, for a normal user, the software provider provides the version: V (N-1) A data and the version: V (N) A data after application of the N-th normal update program. An update program is created from the difference between the two and distributed (generation / distribution (1) in FIG. 2). Then, the normal user updates the software to version: V (N) A using the distributed update program (update (1) in FIG. 2).

  In addition, the user group belonging to company A uses software of version: V (N-1) B to which the individual update program for company A is applied. Therefore, the software provider, for example, from the difference in software data between V (N-1) B for Company A and V (N) A after application of the Nth normal update program, An individual update program is created and distributed to the user (generation / distribution (2) in FIG. 2). The user of company A updates the software to version: V (N) A using an individual update program distributed to company A (update (1) in FIG. 2).

  Similarly, a user group belonging to company B uses software of version V (N-1) C to which an individual update program for company B is applied. For this reason, the software provider, for example, uses the difference between V (N-1) C for company B and V (N) A software data after application of the N-th normal update program. Individual update programs are created and distributed (generation / distribution (3) in FIG. 2). The user of company B updates the software to version: V (N) A using an individual update program distributed to company B (update (1) in FIG. 2).

  For example, when a new normal update program is released as described above, a separate update program is prepared separately from the normal update program for Company A and Company B to which the individual update program is applied. The Therefore, the number of update programs created for updating the software to version: V (N) A is three. In this way, when an individual update program for an information processing apparatus used by some users is released and then a normal update program is released, another individual update program corresponding to the normal update program is released. May be created. As a result, problems such as increased time for creating and verifying the update program and complicated software version management may occur. Therefore, even when an individual update program is applied to software of an information processing apparatus used by some users, it is desired to provide a technique that can reduce the effort for creating the update program.

  In the embodiment described below, when applying the individual update program to the software, the backward information including the individual update program and the data before the update of the update part of the software updated by the application of the individual update program is, for example, Stored in a storage device. When the information processing apparatus 100 updates the software to which the individual update program is applied with the normal update program, the information processing apparatus 100 uses the backward information stored in the storage device to the state before applying the individual update program. Return the software. Thereafter, the information processing apparatus 100 updates the returned software by applying a normal update program. Therefore, software to which the individual update program is applied can also be updated with a normal update program. Therefore, it is possible to reduce the labor for creating the update program. Hereinafter, embodiments will be described in detail with reference to the drawings.

  FIG. 3 is a diagram illustrating a functional block configuration of the information processing apparatus 100 according to the embodiment. The information processing apparatus 100 includes a control unit 300 and a storage unit 302, for example. The control unit 300 includes functional units such as an update unit 311. Further, the storage unit 302 of the information processing apparatus 100 stores, for example, information on a map 400 described later. Details of these functional units and details of information stored in the storage unit 302 will be described later.

  FIG. 4 is a diagram illustrating a map 400 of information stored in the storage unit 302 included in the information processing apparatus 100 according to the embodiment and the configuration of the application system area 410. The map 400 may be a memory map, for example. In the map 400 of FIG. 4, the application system area 410 includes a plurality of application system files. Unlike the other application system files, the application system file 1 may be a management file including information about software such as a model name, software version, build date and time, for example. The application system file 1 may include information on a plurality of software such as an OS and software installed individually. The application system file 1 is changed, for example, when executing software update. The model name of the application system file 1 may be information for identifying the model of the information processing apparatus 100, for example. Further, the software version of the application system file 1 may be the version of the currently installed software. The build date and time of the application system file 1 may be, for example, the date and time when the update program applied to update the software to the current version is created. The map 400 may further include, for example, an update program download area 401 for downloading an update program and a backward information storage area 402 for storing backward information. In another embodiment, for example, information related to software updates such as model name, software version, and build date / time may be managed by another method, such as being managed by a database held in the storage unit 302. .

  FIG. 5 is a diagram illustrating a software update process according to the embodiment. For example, the control unit 300 of the information processing apparatus 100 may start the process of FIG. 5 when the information processing apparatus 100 is activated.

  In step 501 (hereinafter, step is described as “S”, for example, S501), the control unit 300 of the information processing apparatus 100 distributes the update program, for example, whether a software update program has been released. Query the server. For example, when the update program is distributed by FOTA, the control unit 300 inquires of the server that distributes FOTA whether a new update program has been released when the FOTA polling timing comes. Alternatively, for example, when the user manually inputs a software update confirmation instruction, the control unit 300 may inquire whether the update program has been released.

  In step S <b> 502, the control unit 300 determines whether or not a software update program has been released toward the information processing apparatus 100 based on a response result from the server. If a new version update program has not been released (No in S502), the flow returns to S501. On the other hand, if a new version of the update program has been released (Yes in S502), the flow proceeds to S503.

  The determination as to whether or not a new update program has been released toward the information processing apparatus 100 can be performed as follows, for example. For example, if the update program released to the server is a normal update program, the update program is distributed without restriction of the application target. Therefore, if the version of the update program distributed by the server is newer than the software version of the application system file 1, the control unit 300 may determine Yes in S502.

  When the update program released to the server is an individual update program, the server distributes the update program to a part of the information processing apparatuses 100. Note that this distribution restriction can be performed using, for example, the IMEI of the information processing apparatus 100. IMEI is an abbreviation for International Mobile Equipment Identity. The IMEI is an international identification number assigned to the information processing apparatus 100 such as each mobile phone terminal and mobile data communication terminal. For example, when the application target of the individual update program is limited to the information processing apparatus 100 of the company A, the IMEI of the information processing apparatus 100 shipped to the company A is designated and the individual update program is released from the server. Thereby, it is possible to limit the distribution of the individual update program to the information processing apparatus 100 of company A. In this case, for example, the control unit 300 determines whether the IMEI assigned to the information processing apparatus 100 is included in the IMEI designated as the application target of the released individual update program. If the IMEI of the information processing apparatus 100 is included in the application target and the version of the individual update program is newer than the software version of the application system file 1, the control unit 300 determines Yes in S502. You can do it.

  In S503, the control unit 300 downloads the released new update program. For example, the control unit 300 may store the released new update program in the update program download area 401 of the storage unit 302.

  In S504, the control unit 300 determines whether or not the stored update program is an individual update program. For example, the control unit 300 may check the software version of the downloaded update program and determine whether it is an individual update program. As an example, the software version may be represented in the format Vxxx. Here, xx is a number, and is assumed to be 01 at the time of initial shipment, and thereafter incremented sequentially as 02, 03,... Each time a new normal update program is released. In addition, y is an alphabet, A represents a normal update program, and values other than A, for example, B to Z, represent individual update programs. In this case, the control unit 300 may confirm the version of the downloaded update program, and if it ends with A, it may be determined as a normal update program. Further, the control unit 300 may confirm the version of the downloaded update program, and if it ends with B to Z other than A, it may be determined as an individual update program. For example, by determining the software version according to a predetermined rule in this way, the control unit 300 determines whether the update program is a normal update program or an individual update program from the update program version. Is possible.

  When the update program downloaded in S504 is an individual update program (S504 is Yes), the flow proceeds to S505. In step S <b> 505, the control unit 300 stores backward information including the downloaded individual update program and data before the update of the software updated by the individual update program in the backward information storage area 402 of the storage unit 302. To do. As will be described later, the control unit 300 can return the software to the state before being updated by the individual update program by using the backward information stored in the backward information storage area 402. In step S506, the control unit 300 updates the software by applying the downloaded individual update program to the software, and the flow returns to step S501.

  If the update program downloaded in S504 is not an individual update program (No in S504), the update program is a normal update program. In this case, the flow proceeds to S507. In S <b> 507, the control unit 300 determines whether or not there is a track record that the individual update program has been applied to the software since the last time the normal update program was applied. For example, in the operation flow of FIG. 5, as described in S <b> 511 described later, when the normal update program is applied, the control unit 300 deletes the backward information stored in the backward information storage area 402 of the storage unit 302. To do. Therefore, for example, if the backward information corresponding to the individual update program is not stored in the backward information storage area 402 of the storage unit 302, the control unit 300 may determine No in S507. The process proceeds to S509. On the other hand, for example, if the backward information corresponding to the individual update program is stored in the backward information storage area 402 of the storage unit 302, the control unit 300 may determine Yes in S507. In this case, the flow is The process proceeds to S508.

  In S508, after the normal update program is applied last time, the control unit 300 reverses the software change by the individual update program applied up to the present, and the software is applied after the normal update program is applied last time. Return to the state. For example, the control unit 300 may return the software to the state before applying the individual update program using the backward information stored in the backward information storage area 402 of the storage unit 302 in S505. For example, after a normal update program is applied last time, a plurality of individual update programs may have been applied to the software. In this case, the control unit 300 uses, for example, backward information corresponding to the applied individual update programs with a later order in order, and returns to the state before applying the individual update program, and each of the plurality of individual update programs. Software updates may be reversed.

  In S509, the control unit 300 applies the normal update program downloaded in S503 to the software. The normal update program may include a program that corrects a problem that is corrected by applying the individual update program to software. As a result, the defect that has been corrected by applying the individual update program can be corrected by the normal update program even when the software is returned to the state before the application of the individual update program.

  In S <b> 510, the control unit 300 determines whether backward information is stored in the backward information storage area 402 of the storage unit 302. When the backward information corresponding to the individual update program is not stored in the backward information storage area 402 of the storage unit 302 in S510 (S510: No), the flow returns to S501. On the other hand, when the backward information corresponding to the individual update program is stored in the backward information storage area 402 of the storage unit 302 in S510 (S510: Yes), the flow proceeds to S511. In S511, the control unit 300 deletes the backward information stored in the backward information storage area 402. When a plurality of pieces of backward information is stored in the backward information storage area 402, the control unit 300 deletes the pieces of backward information. Therefore, for example, in the backward information storage area 402 of the storage unit 302, the individual update applied during the period from when the previous normal update program is applied to when the next normal update program is applied Program backward information may be retained. When the control unit 300 deletes the backward information from the backward information storage area 402 of the storage unit 302 in S511, the flow returns to S501.

  In the operation flow of FIG. 5, the control unit 300 operates as, for example, the update unit 311.

  As described above, when the normal update program is released, the control unit 300 applies the previous normal update program and then applies the software individually when the individual update program is applied to the software. Return to the state before applying the update program. Thereafter, the control unit 300 applies the released normal update program to the software. Therefore, for example, even when a software provider releases a normal update program after releasing an individual update program, it is not necessary to generate an update program for each individual update program.

  In the above-described embodiment, when the individual update program is applied to the software, the control unit 300 includes the individual update program and the backward information including the data before update of the update portion updated by the individual update program. Is stored in the storage unit 302. Therefore, according to the embodiment, the control unit 300 can return the software to which the individual update program is applied to the state before the individual update program is applied.

  When the controller 300 returns the software to the state before applying the individual update program using the backward information, the controller 300 deletes the backward information from the storage unit 302. Therefore, for example, the control unit 300 can determine whether or not the individual update program is applied to the software by confirming whether or not the backward information is stored in the storage unit 302. Alternatively, the version name is set according to a predetermined rule so that the version name of the software updated by the update program and the version name of the software updated by the individual update program can be distinguished. Accordingly, the control unit 300 can determine whether or not the individual update program is applied to the software by referring to the application system file 1 and confirming the version name of the current software.

  As described above, according to the above embodiment, when an individual update program is released and then a normal update program is released, an increase in update program creation time and verification time can be suppressed. . In addition, the software version management can be prevented from becoming complicated. Therefore, according to the embodiment, it is possible to reduce labor for creating an update program.

  In the above embodiment, it is determined whether or not the individual update program has been applied to the software up to now since the normal update program was applied last time in S507. However, for example, when there is no application record of a normal update program, for example, immediately after software is installed in the information processing apparatus 100, the control unit 300 determines whether there is an individual update program applied so far in S507. It may be determined whether or not.

  In the above operation flow, the identification of the individual update program applied after the previous normal update program was applied in S507 is based on the backward information stored in the backward information storage area 402 of the storage unit 302. Is going. However, in another embodiment, for example, the control unit 300 stores information such as the application date and time in the storage unit 302 when the applied normal update program and the individual update program are applied. And the control part 300 may specify the separate update program applied after the last normal update program was applied by referring the information.

  Moreover, although said embodiment has illustrated the case where an update program is downloaded via wireless communication, embodiment is not limited to this. For example, the control unit 300 may read an update program stored in a portable storage medium such as an SD card and apply it to software.

  In the above embodiment, for example, a normal update program distributed to information processing apparatuses for all users and an individual update program distributed to information processing apparatuses used by some users are taken as examples. I am explaining. However, the embodiment is not limited to this. For example, an update distributed to an information processing device used by a second user group in software to which an individual update program distributed to the information processing device used by a first user group of a certain software is applied The embodiment can also be applied when a program is applied. Note that the second user group may be a user group that includes the first user group and is larger than the first user group. In this case, the control unit 300 returns information used by the second user group after returning the software to a state before applying the individual update program distributed to the information processing apparatus used by the first user group. Apply the update program distributed to the processing device. Thereby, it is possible to reduce the labor for creating the update program. In this case, the update program distributed to the information processing apparatus used by the second user group may correspond to the normal update program targeted for the above-described information processing apparatuses of all users. However, the update program distributed to the information processing apparatus used by the second user group may be an update program distributed to the information processing apparatuses used by some users instead of all users. The individual update program distributed to the information processing apparatus used by the first user group corresponds to the individual update program distributed to the information processing apparatus used by some users in the above-described embodiment. It's okay.

<Application example>
An application example of the embodiment described above will be described below. FIG. 6 is a diagram illustrating an application example of the embodiment. FIG. 6 exemplifies application of the individual update program to the software updated to version: V02A and the normal update program in the second update by the normal update program.

  First, application of the individual update program to the software of the information processing apparatus 100 of the model name F-0A of company A will be described. Company A is, for example, a company that conducts work related to construction, and stores a large amount of photos in the information processing apparatus 100 in order to record the construction status and state of the building. Further, in the software (version: V02A) of the information processing apparatus 100 of model name: F-0A, when the temperature of the casing exceeds the reference value or the remaining battery level becomes equal to or less than the reference value, the camera suppression process It is a specification that starts and terminates the camera application. Here, if the camera suppression process is activated while photo data captured by the camera is being stored in the storage unit 302, the camera application ends before the photo data is completely saved, Suppose your photo data might be corrupted.

  This failure can be a fatal failure for Company A. Therefore, for example, if the software provider is saving photo data at the start of camera suppression processing, an individual update program (V02B) for correcting specifications so that the application of the camera is not terminated until the saving is completed. Create Then, after performing the minimum operation check, the individual update program (V02B) is released at an early timing. In this case, for example, since only a minimum operation check is performed, the release target is limited to the information processing apparatus 100 of company A. The information processing apparatus 100 to which the individual update program is to be applied can be specified using, for example, the IMEI of the information processing apparatus 100 as described above.

  For example, when the control unit 300 of the information processing apparatus 100 having the model name F-0A confirms that a new update program (V02B) has been released on the server of the software provider, the update program (V02B) Download. When the download is completed, the control unit 300 confirms the software version of the downloaded update program. The version of the update program downloaded here is V02B, and the end is other than A. Therefore, the control unit 300 may determine that the downloaded update program is an individual update program. In this case, the control unit 300 stores backward information including the individual update program and the data before the update of the portion updated by the individual update program in the storage unit 302. Thereafter, the control unit 300 applies the individual update program to the software, and updates the software from the version: V02A to V02B (individual update (1) in FIG. 6).

  Next, application of the individual update program to the software of the information processing apparatus 100 with the model name F-0A of company B will be described. For example, Company B has an office on the 5th floor of a building, and many other companies have offices on the 5th floor. As a result, in the 2.4 GHz band, WiFi (registered trademark) radio waves are concentrated, and there is a problem that the communication speed is slow due to radio wave interference and is not easily connected. The WiFi frequency band can be set to three patterns: automatic, 2.4 GHz fixed, and 5 GHz fixed. Since 5 GHz is restricted for outdoor use, it is usually automatic or fixed to 2.4 GHz. It shall be set. However, Company B uses the information processing apparatus 100 with the WiFi band set to 5 GHz fixed for the reasons described above. However, it is assumed that the software of version: V02A has discovered at a certain timing that there is a problem that communication cannot be performed if the WiFi band is fixed at 5 GHz and used for a long time.

  This problem is a serious problem that hinders the business that B company cannot communicate. Therefore, for example, a software provider creates an individual update program (version: V02C) for correcting this problem, performs a minimum operation check, and releases it at an early timing. In addition, since only a minimum operation check is performed, for example, the application target of software is limited to the IMEI information processing apparatus 100 shipped to the B company.

  For example, when the control unit 300 of the information processing apparatus 100 having the model name F-0A confirms that a new update program (V02C) has been released on the server of the software provider, the update program (V02C) Download. When the download is completed, the control unit 300 confirms the software version of the downloaded update program. The version of the update program downloaded here is V02C, and the end is other than A. Therefore, the control unit 300 may determine that the downloaded update program is an individual update program. Then, the control unit 300 stores backward information including the individual update program and the data before the update of the portion updated by the individual update program in the storage unit 302. Thereafter, the control unit 300 applies the individual update program, and updates the software from the version: V02A to V02C (individual update (2) in FIG. 6).

  Up to this point, the individual update program has been applied to the software of the information processing apparatus 100 of the model name F-0A of company A and company B, and the software versions have been updated to V02B and V02C, respectively. After the individual update, the control unit 300 of the information processing apparatus 100 continues to inquire, for example, whether a new update program has been released from the server of the software provider.

  After the release of the individual update program for Company A and the individual update program for Company B, the software provider performs both the correction of the camera suppression process released to Company A and the correction of WiFi released to Company B. Verify the operation of the software. Then, if the provider confirms that there is no problem as a result of the operation verification, the provider creates a normal update program of version: V03A including both corrections, and installs all information processing apparatuses 100 of model name: F-0A. Distribute to the target (generation / distribution (1) in FIG. 6).

  As described above, the control unit 300 of the information processing apparatus 100 with the model names of Company A and Company B: F-0A continuously checks whether a new update program has been released, and a new update program has been released. If so, download the update. Then, the control unit 300 confirms the software version of the downloaded update program. Here, since the software version of the downloaded update program is V03A and the end is A, the control unit 300 can determine that the update program is a normal update program.

  Then, when applying the normal update program, the control unit 300, if the individual update program is applied after the application of the previous normal update program, sets the location updated by the individual update program as the previous normal update program. Return to the state after applying the update. Then, the control unit 300 applies the normal update program distributed this time.

  For example, the control unit 300 of the information processing apparatus 100 having the model name F-0A of company A uses the backward information stored in the storage unit 302 during the individual update from V02A to V02B, and applies the software to V02A. Return to the state immediately after (backward (1) in FIG. 6). Thereafter, the control unit 300 updates the software by applying a normal update program to V03A to the software that has been returned to the state immediately after the application of V02A (update (1) in FIG. 6). When the update is executed, the control unit 300 may delete the backward information stored in the storage unit 302 when performing the individual update from V02A to V02B.

  Further, in the case of the information processing apparatus 100 having the model name F-0A of Company B, the software immediately after the application of V02A is used by using the backward information stored in the storage unit 302 at the time of the individual update from V02A to V02C. Return to the state (backward (2) in FIG. 6). Thereafter, the control unit 300 updates the software by applying a normal update program to V03A to the software that has been returned to the state immediately after the application of V02A (update (1) in FIG. 6). When the update is executed, the control unit 300 may delete the backward information stored in the storage unit 302 during the individual update from V02A to V02C.

  As described above, the backward update information is used to return the update location by the individual update program to the original state before the update, so that the normal update program can be downloaded even to the software to which the individual update program is applied. Can be applied.

  The example in FIG. 6 describes a case where one individual update program is released for each of the information processing apparatuses of company A and company B between two normal update programs V02A and V03A. . However, for example, even when the release of the individual update program for one company is performed multiple times, by returning to the state before application using backward information in order from the individual update program with the later applied order, Embodiments can be applied.

  For example, after the information processing apparatus 100 of model name F-0A of company C applies a normal update program for V02A to software, the individual update program for V02B and V02C is applied to the software, and then the normal update program for V03A Suppose you apply the update. In this case, the control unit 300 stores the backward information for returning from V02B to V02A in the storage unit 302 when the software is updated to V02B. In addition, the control unit 300 stores backward information for returning from V02C to V02B in the storage unit 302 when the software is updated to V02C.

  When updating the software to V03A, the control unit 300 first returns the software to version: V02B using backward information for returning from V02C to V02B. Subsequently, the control unit 300 returns the software to version: V02A using the backward information for returning from V02B to V02A. Thereafter, the control unit 300 updates the software by applying a normal update program to version: V03A. For example, by executing the processing in this manner, a normal individual update program can be applied even when a plurality of individual update programs are applied to the software of the information processing apparatus 100 of a certain company.

  Although the embodiment has been exemplified above, the embodiment is not limited thereto. For example, the above-described operation flow is an example, and the embodiment is not limited to this. If possible, the operation flow may be executed by changing the order of processing, may include additional processing, or some processing may be omitted. For example, the processes of S505 and S506 in FIG.

  FIG. 7 is a diagram illustrating a hardware configuration of a computer 700 for realizing the information processing apparatus 100 according to the embodiment. The hardware configuration for realizing the information processing apparatus 100 in FIG. 7 includes, for example, a processor 701, a memory 702, a storage device 703, a reading device 704, a communication interface 706, and an input / output interface 707. The processor 701, the memory 702, the storage device 703, the reading device 704, the communication interface 706, and the input / output interface 707 are connected to each other via a bus 708, for example.

  The processor 701 provides a part or all of the functions of each functional unit including the control unit 300 described above by executing a program describing the procedure of the above-described operation flow using the memory 702, for example. The storage unit 302 includes, for example, a memory 702, a storage device 703, and a removable storage medium 705. The processor 701 of the information processing apparatus 100 functions as the update unit 311 by reading and executing a program stored in the storage device 703, for example. For example, information of the map 400 is stored in the memory 702 of the information processing apparatus 100.

  The memory 702 is a semiconductor memory, for example, and may include a RAM area and a ROM area. Note that RAM is an abbreviation for Random Access Memory. ROM is an abbreviation for Read Only Memory. The storage device 703 is, for example, a semiconductor memory such as a hard disk or a flash memory, or an external storage device.

  The reading device 704 accesses the removable storage medium 705 in accordance with instructions from the processor 701. The detachable storage medium 705 includes, for example, a semiconductor device (USB memory or the like), a medium to / from which information is input / output by a magnetic action (a magnetic disk), For example, a DVD). USB is an abbreviation for Universal Serial Bus. CD is an abbreviation for Compact Disc. DVD is an abbreviation for Digital Versatile Disk.

  The communication interface 706 transmits / receives data via the network 720 in accordance with instructions from the processor 701. The input / output interface 707 may be an interface between an input device and an output device, for example. The input device is, for example, a device such as a keyboard or a mouse that receives an instruction from the user. The output device is a display device such as a display and an audio device such as a speaker.

Each program according to the embodiment is provided to the information processing apparatus 100 in the following form, for example.
(1) Installed in advance in the storage device 703.
(2) Provided by the removable storage medium 705.
(3) Provided from a server 730 such as a program server.

  The hardware configuration of the computer 700 for realizing the information processing apparatus 100 described with reference to FIG. 7 is an exemplification, and the embodiment is not limited to this. For example, some or all of the functions of the above-described functional units may be implemented as hardware such as FPGA and SoC. Note that FPGA is an abbreviation for Field Programmable Gate Array. SoC is an abbreviation for System-on-a-chip.

  In the above, several embodiments are described. However, the embodiments are not limited to the above-described embodiments, and should be understood as including various modifications and alternatives of the above-described embodiments. For example, it will be understood that various embodiments can be embodied by modifying the components without departing from the spirit and scope thereof. It will be understood that various embodiments can be implemented by appropriately combining a plurality of components disclosed in the above-described embodiments. Further, various embodiments may be implemented by deleting or replacing some components from all the components shown in the embodiments, or adding some components to the components shown in the embodiments. Those skilled in the art will appreciate that this can be done.

DESCRIPTION OF SYMBOLS 100 Information processing apparatus 300 Control part 302 Storage part 311 Update part 700 Computer 701 Processor 702 Memory 703 Storage apparatus 704 Reading apparatus 705 Removable storage medium 706 Communication interface 707 Input / output interface 708 Bus 720 Network 730 Server

Claims (4)

  An information processing device used by a second user group including the first user group is applied to the software to which an individual update program distributed to the information processing device used by the first user group of software is applied. A method of updating software executed by an information processing apparatus, including a step of applying the update program after returning the software to a state before applying the individual update program when applying an update program distributed to a target . Further, when applying the individual update program to the software, a step of storing in the storage unit backward information including the individual update program and data before the update of the software by the individual update program is updated. Including
The step of applying the update program returns the software to a state before applying the individual update program, using the backward information.
The software update method according to claim 1, wherein:   The step of applying the update program includes the step of applying the individual update after the previous update program distributed to the information processing apparatus used by the second user group before the update program is applied to the software. When the second individual update program distributed to the information processing apparatus used by the program and the first user group is applied to the software, the software is changed to the individual update program and the second individual update program. The software update method according to claim 1, wherein the update program is applied after returning to a state before the update program is applied.   An information processing device used by a second user group including the first user group is applied to the software to which an individual update program distributed to the information processing device used by the first user group of software is applied. An information processing apparatus comprising: an update unit that applies the update program after returning the software to a state before applying the individual update program when applying the update program distributed to a target.

Images