Information processing device, collaborative operation method

Abstract

This system enables coordinated operation even when multiple mobile units each have different pre-installed software components. [Solution] The information processing device 100 of the present disclosure includes a third computer 103 that transmits pre-stored software parts to the other mobile body and receives software parts owned by the other mobile body when it is necessary to execute a mission related to cooperative operation with another mobile body, and a second computer 102 that selects software parts to be used for executing the mission related to cooperative operation from among the pre-stored software parts and the software parts received from the third computer.

Description

Technical Field

[0001] This disclosure relates to an information processing apparatus.

Background Art

[0002] As a conventional information processing apparatus, Patent Document 1 discloses one including a library, a reception module, and a proxy server. In Patent Document 1, the reception module receives software parts from a supplier and transmits them to the library. Also, the proxy server communicates with the library and distributes software to a plurality of aircraft clients.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the above-described conventional information processing apparatus, when performing a cooperative operation of software with a plurality of moving bodies, there is a problem that the cooperative operation cannot be performed because the software previously possessed by each moving body is different.

[0005] This disclosure has been made to solve the above-described problems, and an object thereof is to operate in cooperation when software parts previously possessed by a plurality of moving bodies are different.

Means for Solving the Problems

[0006] The information processing apparatus of this disclosure is when execution of a mission related to a cooperative operation with another moving body is required, a third computer that transmits software parts saved in advance to the other moving body and receives software parts possessed by the other moving body from the other moving body, A second computer that selects software parts necessary for executing the mission from among the pre-stored software parts and software parts received from the third computer, It is equipped with. [Effects of the Invention]

[0007] The information processing device disclosed herein can operate in cooperation even when each of multiple mobile objects has different software parts pre-installed. [Brief explanation of the drawing]

[0008] [Figure 1] This is a diagram showing the configuration of the information processing device in Embodiment 1. [Figure 2] This diagram shows the operation of the information processing device in Embodiment 1. [Figure 3] This diagram shows the operation of the information processing device in Embodiment 1. [Figure 4] This diagram shows the configuration of the information processing device in the second embodiment. [Figure 5] This diagram shows the operation of the information processing device in the second embodiment. [Figure 6] This diagram shows the operation of the information processing device in the second embodiment. [Modes for carrying out the invention]

[0009] Traditionally, the functions of mobile devices have been primarily realized through hardware. However, in recent years, there has been a trend towards realizing functions through software that is easy to update and install after hardware manufacturing. Software updates or installations on mobile devices are mainly performed at the manufacturing plant or repair plant, or, as described in Patent Document 1, remotely using wireless communication. Furthermore, the installed software may be uniquely customized for each owner or operating region.

[0010] In recent years, mobile units are not only operated individually, but also in coordinated operations involving multiple units. However, if the software components installed on each mobile unit are different, coordinated operation becomes impossible. Software components refer to groups of parts that divide software into functional units, as well as groups of setting parameter files used for software operation.

[0011] The information processing device disclosed herein enables coordinated operation by sharing software parts necessary for coordinated operation among mobile devices, even if the software parts installed on each mobile device are different, and by temporarily using the shared software parts.

[0012] Furthermore, the information processing device disclosed herein includes a function to delete software parts that were not present before the start of the cooperative operation after the cooperative operation has started, and the system is restored to its original state before the cooperative operation. This makes it possible to share software parts that have sensitive functions or specifications that you do not want to be permanently stored on the other party's mobile device.

[0013] Embodiments of this disclosure will be described below with reference to the drawings. In the following description, similar components will be denoted by the same reference numerals, and their names and functions will be the same or similar. Therefore, detailed descriptions of them may be omitted.

[0014] Embodiment 1. ***Explanation of the structure*** The configuration of the information processing device 100 and the information processing device 110 in Embodiment 1 will be explained with reference to Figure 1. The information processing device 100 is mounted on a mobile unit 10. In addition to the information processing device 100, the mobile unit 10 includes an input / output device 200 connected to the information processing device 100.

[0015] The information processing device 110 is mounted on the mobile body 11. In addition to the information processing device 110, the mobile body 11 is equipped with an input / output device 210 connected to the information processing device 110. Mobile bodies 10 and 11 are aircraft, ships, automobiles, and other mobile devices.

[0016] The information processing apparatus 100 includes a first computer 101, a second computer 102, a third computer 103, a storage for normal operation 104, and a storage for temporary operation 105.

[0017] The first computer 101, the second computer 102, and the third computer 103 are realized by, for example, a processor. The storage for normal operation 104 or the storage for temporary operation 105 is realized by, for example, an HDD (Hard Disk Drive) or a flash memory.

[0018] The first computer 101 holds mission data 301. The mission data 301 is information including the name and content of the mission planned by the mobile object 10 and a list of software parts required for the execution of the mission. The mission includes a cooperative operation between the mobile object 10 and the mobile object 11.

[0019] Here, the cooperative operation is an operation in which a plurality of mobile objects execute the optimal functions for achieving the same mission objective indicated in the mission data (mission data 301 and mission data 311) held by each mobile object. The optimal functions for achieving the mission objective and the processing targets of the functions may be different between the mobile objects.

[0020] For example, the following cooperative operations are conceivable. (1) When the mobile object 10 and the mobile object 11 perform cooperative imaging around the mobile object, the mobile object 10 and the mobile object 11 execute the same imaging function. The processing target of the function (imaging direction) may be specified according to the content of the mission included in the mission data 301 or the mission data. On the other hand, the imaging directions of the mobile object 10 and the mobile object 11 are coordinated so as not to overlap for efficiency.

[0021] (2) When the mobile body 10 images the area around it and the mobile body 11 processes the data from the imaging results, the mobile body 10 performs the imaging function and the mobile body 11 performs the data processing function, each performing a different function. Which mobile body performs imaging or data processing may be specified by the content of the mission included in the mission data 301.

[0022] The second computer 102 holds the version check application 401. The version check application 401 runs the software required to perform the mission.

[0023] The third computer 103 holds the data transmission application 501. It transmits data received from other mobile devices to the first computer 101 and the second computer 102. It also transmits data to other mobile devices.

[0024] The normal operation storage 104 stores software parts 601 and mobile unit installation information 701 that the mobile unit 10 normally uses when performing missions other than coordinated operations. Hereafter, operations performed according to mission data 301 during normal operations will be referred to as normal operations. Software parts 601 are a group of components that divide the software into functional units, and a group of setting parameter files used for the operation of the software. Mobile unit installation information 701 is a list of software parts stored in the normal operation storage 104.

[0025] The temporary operation storage 105 stores software parts 611 and 612 that are used during coordinated operations when the mobile location 10 executes a mission related to coordinated operations.

[0026] The input / output device 200 receives input from the user and displays information presented to the user by the information processing device 100. The input / output device 200 is, for example, a touch panel. The input / output device 200 may also be a keyboard, mouse or other input device and a display or other output device.

[0027] The information processing device 110 includes a first computer 111, a second computer 112, a third computer 113, a storage device for normal operation 114, and a storage device for temporary operation 115.

[0028] The first computer 111, the second computer 112, and the third computer 113 are implemented, for example, by processors. The storage for normal operation 114 or the storage for temporary operation 115 are implemented, for example, by HDDs (Hard Disk Drives) or flash memory.

[0029] The first computer 111 holds mission data 311. Mission data 311 is information including the name of the mission planned by the mobile unit 11 and the software parts required to execute the mission. The mission includes coordinated operation between the mobile unit 10 and the mobile unit 11.

[0030] The second computer 112 holds a version check application 411. The version check application 411 determines whether coordinated operation is necessary based on the mission data 311. The version check application 411 also selects the software parts required for mission execution from the software parts pre-stored in the normal operation storage and the software parts received from other mobile devices, and executes the selected software.

[0031] Furthermore, the version check app 411 determines whether the collaborative operation can continue. If the version check app 411 determines that the collaborative operation cannot continue, it deletes the software parts received from the other mobile device from the temporary operation storage 115.

[0032] The third computer 113 holds the data transmission application 511. The data transmission application 511 transmits data received from other mobile devices to the first computer 111 and the second computer 112. It also transmits data to other mobile devices.

[0033] The normal operation storage 114 stores software parts 611, software parts 612, and mobile unit installation information 711 that the mobile unit 11 uses during normal operation or cooperative operation.

[0034] The temporary operation storage 115 stores software parts that are used only during coordinated operations when the mobile location 11 executes a mission related to coordinated operations.

[0035] Here, software part 601 stored in the normal operation storage 104 and software part 611 stored in the normal operation storage 114 are assumed to be the same or corresponding software parts related to function A. Furthermore, software part 61 and software part 601 are assumed to be different versions, with software part 601 being version 1.0 and software part 611 being version 2.0, which is an improved version of version 1.0.

[0036] The software part 612 stored in the normal operation storage 114 is a software part related to function B, which is different from function A, and is version 1.0. Functions A and B may be used simultaneously or sequentially. For example, function A may be an imaging function around a moving object, and function B may be a function for processing the imaging data.

[0037] ***Explanation of operation*** The operation of the information processing device 100 will be explained using Figure 2. Figure 2 is a diagram showing the operation of the information processing device 100. The operation of the information processing device 100 corresponds to each step of the cooperative operation method. In Embodiment 1, the mobile body 10 and the mobile body 11 are assumed to execute missions related to the cooperative operation.

[0038] (S101: Mission data storage process) The first computer 301 stores the mission data 301. The mission data 301 is pre-registered by the user.

[0039] (S102: Mission data transmission process) The first computer 101 sends the mission data 301 to the version check application 401.

[0040] (S103: Process for determining whether coordinated operation is necessary) The second computer 102 runs the version check application 401 to determine whether a coordinated operation is necessary. At this time, the second computer 102 determines that a coordinated operation is necessary if the mission data 301 includes a mission related to the coordinated operation, and determines that a coordinated operation is unnecessary if the mission data 301 does not include a mission related to the coordinated operation. If a coordinated operation is necessary, the process proceeds to S104. If a coordinated operation is unnecessary, the process proceeds to S115.

[0041] (S104: Preparation process for sending software parts) The second computer 102, via the version check application 401, transmits the software parts stored in the normal operation storage 104 to the data transmission application 501. In Embodiment 1, the data transmission application 501 acquires the software parts 601 and mobile device installation information 701.

[0042] (S105: Software Part Transmission Process) The third computer 103 transmits the software parts and mobile device installation information acquired in S104 to the other mobile device, which is the partner in the collaborative operation, via the data transmission application 501. In Embodiment 1, the third computer 103 transmits the software parts 601 and mobile device installation information 701 to the data transmission application 511 of the mobile device 11. At this time, the third computer 103 may transmit the software parts after mutually authenticating with the other mobile device that the communication is correct.

[0043] (S106: Software parts receiving process) The third computer 103 receives software parts owned by the mobile device 11 from the data transmission application 511 via the data transmission application 501 and sends them to the version check application 401. In Embodiment 1, the data transmission application 501 receives software part 611, software part 612, and mobile device installation information 711 and sends them to the version check application 401.

[0044] (S107: Software Parts Candidate Selection Process) The second computer 102 uses the version check application 401 to select candidate software parts required to execute the missions included in the mission data 301. In Embodiment 1, software parts 601 and 611 related to function A and software part 612 related to function B are selected.

[0045] (S108: Selection process for software components for coordinated operation) The second computer 102, using the version check application 401, selects software parts to be used for executing the mission included in the mission data 301 from among the software parts stored in the normal operation storage 104 and software parts received from other mobile devices. In Embodiment 1, the version check application 401 selects software parts 611 and 612 from among software parts 601, 611, and 612 as software to be used for executing the mission related to cooperative operation.

[0046] In cases where there are multiple software parts related to the same function, the version check application 401 may select the newer version. Furthermore, the criteria for software part selection by the version check application 401 are predetermined by the user of the information processing device 100.

[0047] (S109: Installation necessity determination process) The second computer 102 uses the version check application 401 to refer to the mobile installation information 701 and determine whether or not to install the software parts. At this time, if a software part that is not stored in the normal operation storage 104 is selected in S108, the version check application 401 determines that it is necessary to install it. If only stored software parts are selected, the version check application 401 determines that it is not necessary to install it.

[0048] In Embodiment 1, at S108, software parts 611 and 612, which are not stored in the normal operation storage 104, are selected, so the version check application 401 determines that installation is required.

[0049] (S110: Software parts transfer process) The third computer 103, using the data transmission application 501, transfers software parts selected in S108 that are not stored in the normal operation storage 104 to the temporary operation storage 105.

[0050] In other words, the third computer 103, via the data transmission application 501, transfers the software parts selected in S108 from the software parts received in S106 to the temporary operation storage 105. In Embodiment 1, the data transmission application 501 transfers software parts 611 and 612 to the temporary operation storage 105.

[0051] (S111: Software parts installation process) The second computer 102 installs the software parts transferred to the temporary operation storage 105 using the version check application 401. In Embodiment 1, the second computer 102 transfers software parts 611 and 612 to the temporary operation storage 105 using the version check application 401. The configuration for transferring the software parts may differ. The timing of the installation will be determined according to other design aspects. For example, it may be after a certain period of time has elapsed since the software parts were transferred to the temporary operation storage 105.

[0052] (S112: Execute collaborative action) The second computer 102 executes the software selected in S108 using the version check application 401. As a result, the mobile unit 10 performs coordinated operation with the mobile unit 11. When starting the coordinated operation, for example, communication may occur between each mobile unit performing the coordinated operation, and one of the mobile units may take overall control to start the coordinated operation of all mobile units. In Embodiment 1, the version check application 401 executes the software using software parts 611 and 612.

[0053] Furthermore, if only software parts stored in the normal operation storage 104 are selected in S108, the version check application 401 will execute the software using the software parts stored in the normal operation storage 104.

[0054] (S113: Process for determining whether to continue coordinated operation) The second computer 102 uses the version check application 401 to determine whether the collaborative operation can continue. If it determines that the collaborative operation cannot be continued, the version check application 401 proceeds to S114. If it determines that the collaborative operation can be continued, the version check application 401 continues the collaborative operation in S112.

[0055] The criteria for determining that collaborative operation cannot be continued in S113 may be, for example, the following: (1) If a specified time has elapsed since communication with the other party was lost. (2) If the other party has notified in advance that communication will be impossible for a certain period of time, and communication is still impossible after that period has elapsed. (3) When coordination with the other party is only possible within a certain distance, and the distance to the other party's location exceeds the distance within which coordination is possible.

[0056] (S114: Temporary operation storage data deletion process) The second computer 102 deletes the software parts stored in the temporary operation storage 105 using the version check application 401. As a result, the information processing device 100 returns to the state of S111.

[0057] (S115: Normal operation execution process) If S103 determines that coordinated operations are unnecessary, the second computer 102 executes the normal operations included in the mission data 301 using the version check application 401.

[0058] The information processing device 110 performs the operations shown in Figure 3 in parallel with the operation of the information processing device 100 described above. Figure 3 is a diagram showing the operation of the information processing device 110. The operation of the information processing device 110 in Embodiment 1 will be described below.

[0059] (S101: Mission data storage process) The first computer 311 stores the mission data 311. The mission data 311 is pre-registered by the user.

[0060] (S102: Mission data transmission process) The first computer 111 sends mission data 311 to the version check application 411.

[0061] (S103: Process for determining whether coordinated operation is necessary) The second computer 112 runs the version check application 411 to determine whether a coordinated operation is necessary. At this time, the second computer 112 determines that a coordinated operation is necessary if the mission data 311 includes a mission related to the coordinated operation, and determines that a coordinated operation is unnecessary if the mission data 311 does not include a mission related to the coordinated operation. If a coordinated operation is necessary, the process proceeds to S104. If a coordinated operation is unnecessary, the process proceeds to S115.

[0062] (S104: Preparation process for sending software parts) The third computer 113 retrieves software parts stored in the normal operation storage 114 using the data transmission application 511. In Embodiment 1, the data transmission application 511 retrieves software part 611, software part 612, and mobile device installation information 711.

[0063] (S105: Software Part Transmission Process) The third computer 113 transmits the software parts and mobile device installation information acquired in S104 to the other mobile device, which is the partner in the collaborative operation, via the data transmission application 511. In Embodiment 1, the third computer 113 transmits the software parts 611, software parts 612, and mobile device installation information 711 to the data transmission application 501 of the mobile device 10. At this time, the third computer 113 may transmit the software parts after mutually authenticating with the other mobile device that the communication is correct.

[0064] (S106: Software parts receiving process) The third computer 113 receives software parts owned by the mobile device 10 from the data transmission application 501 via the data transmission application 511 and transmits them to the version check application 411. In Embodiment 1, the data transmission application 511 receives the software parts 601 and mobile device installation information 701 and transmits them to the version check application 411.

[0065] (S107: Software Parts Candidate Selection Process) The second computer 112 uses a version check application 411 to select candidate software parts required to execute the missions included in the mission data 311. In Embodiment 1, software parts 601 and 611 related to function A and software part 612 related to function B are selected.

[0066] (S108: Selection process for software components for coordinated operation) The second computer 112, using the version check application 411, selects software parts to be used for executing the mission included in the mission data 311 from among the software parts stored in the normal operation storage 114 and software parts received from other mobile devices. In Embodiment 1, the version check application 411 selects software parts 611 and 612 from among software parts 601, 611, and 612 as software to be used for executing the mission related to cooperative operation.

[0067] (S109: Installation necessity determination process) The second computer 112 uses the version check application 411 to refer to the mobile installation information 711 and determine whether or not to install the software parts. If a software part that is not stored in the normal operation storage 114 is selected in S108, the version check application 411 determines that it is necessary to install it. If only stored software parts are selected, it determines that it is not necessary to install it.

[0068] In Embodiment 1, at S108, only the software stored in the normal operation storage 114 was selected, so the version check application 411 determined that installation was unnecessary. Subsequently, the information processing device 110 performed the operations from S112 onward.

[0069] (S112: Execute collaborative action) The second computer 112 executes the software selected in S108 using the version check application 411. As a result, the mobile unit 11 performs coordinated operation with the mobile unit 10. In Embodiment 1, the version check application 411 executes the software using software parts 611 and 612.

[0070] (S113: Process for determining whether to continue coordinated operation) The second computer 112 uses the version check application 411 to determine whether the collaborative operation can continue. If it determines that the collaborative operation cannot be continued, the version check application 411 proceeds to S114. If it determines that the collaborative operation can be continued, the version check application 411 continues the collaborative operation in S112.

[0071] (S114: Temporary operation storage data deletion process) The second computer 112 deletes the software parts stored in the temporary operation storage 115 using the version check application 411. As a result, the information processing device 100 returns to the state before execution of S101 and enters a standby state.

[0072] (S115: Normal operation execution process) If S103 determines that coordinated operations are unnecessary, the second computer 112 executes the normal operations included in the mission data 311 using the version check application 411.

[0073] Furthermore, the information processing device may send and receive software parts with multiple information processing devices. In this case, the information processing device 110 sends software parts to all mobile devices that are partners in the coordinated operation of the mobile device 10 in step S105: software parts transmission step. It also receives software parts from all of the mobile devices in step S106: software parts reception step.

[0074] ***Explanation of Effects*** Thus, When it is necessary to execute a mission involving coordinated operation with other mobile units, a third computer 103 transmits pre-stored software parts to the other mobile unit and receives software parts held by the other mobile unit from the other mobile unit, The second computer 102 selects software parts necessary for executing the mission related to the cooperative operation from among the pre-stored software parts and the software parts received by the third computer 103. The information processing device 100, equipped with the above, sends and receives software parts with other mobile devices that perform cooperative operations, and selects the software parts necessary for executing the mission from among the software parts it has previously acquired and the software parts it has received from other mobile devices.

[0075] This allows for coordinated operation, as the same software parts can be used to operate even if the pre-existing software parts differ from those of other mobile devices.

[0076] Furthermore, because software parts are sent and received from each other, even if one of the mobile units does not possess the software corresponding to the functions to be executed in the mission involving coordinated operation before the start of operation, coordinated operation can be performed after the start of operation.

[0077] Similarly, even if the execution of a mission is decided before the start of operations, if a new version of the software parts is not available before one of the mobile units leaves the manufacturing plant, if the mobile units have different owners and the other mobile unit possesses higher-performance software parts, or if it is not desirable to share software parts with other mobile units that have different owners in advance, the system will still be able to operate in cooperation using the same software parts after the start of operations.

[0078] Furthermore, in the case of an information processing device that deletes software parts received from other mobile devices from among the selected software parts when the second computer 102 determines that it is not possible to continue the cooperative operation, the software parts can be shared among multiple mobile devices only during cooperative operation. This prevents, for example, mobile devices with different owners from constantly possessing highly confidential software parts.

[0079] Embodiment 2. ***Explanation of the structure*** The configurations of the information processing devices 100b and 110b in Embodiment 2 will be explained with reference to Figure 4. In Figure 4, the same reference numerals as in Figure 1 indicate the same or equivalent configurations. The information processing device 100b is mounted on the mobile unit 10. The mobile unit 10 is operated by the mobile unit operator 1000. The mobile unit operator 1000 may be a ground station or an equivalent configuration of an artificial satellite.

[0080] The information processing device 110b is mounted on the mobile unit 11. The mobile unit 11 is operated by the mobile unit operator 1100. Mobile units 10 and 11 are aircraft, ships, automobiles, or other mobile units. The mobile unit operator 1100 may be a ground station or a corresponding satellite configuration.

[0081] The information processing device 100b includes a first computer 101b, a second computer 102b, a third computer 103, a fourth computer 107, a storage device for normal operation 104, and a storage device for temporary operation 105.

[0082] The first computer 101b, the second computer 102b, the third computer 103, and the fourth computer 107 are implemented, for example, by processors. The storage for normal operation 104 or the storage for temporary operation 105 are implemented, for example, by HDDs (Hard Disk Drives) or flash memory.

[0083] The mobile unit operator 1000 maintains mission data 1001. Mission data 1001 is information including the name and content of the mission planned by the mobile unit 10, and a list of software parts required to execute the mission. The mission content may also include whether coordinated operation is required, the devices used by the mobile unit 10 or the mobile unit of the coordinating partner, or the operation details. The mission includes coordinated operation between the mobile unit 10 and the mobile unit 11.

[0084] Here, coordinated operation refers to the operation in which multiple mobile units perform the optimal function to achieve the same mission objective, as indicated in the mission data (mission data 1001 and mission data 1011) of each mobile unit. The optimal function to achieve the mission objective, and the target of processing for that function, may differ among the mobile units.

[0085] For example, the following coordinated actions are possible. (1) When mobile bodies 10 and 11 perform coordinated imaging of the area around the mobile bodies through coordinated operation, mobile bodies 10 and 11 perform the same imaging function. The processing target of the function (imaging direction) may be specified by the mission data 1001 or the contents of the mission included in the mission data. On the other hand, the imaging directions of mobile bodies 10 and 11 are coordinated so as not to overlap for efficiency.

[0086] (2) When the mobile body 10 images the area around it and the mobile body 11 processes the data from the imaging results, the mobile body 10 performs the imaging function and the mobile body 11 performs the data processing function, each performing a different function. Which mobile body performs imaging or data processing may be specified by the content of the mission included in the mission data 1001.

[0087] The first computer 101b holds the version suggestion application 301b in place of the mission data 301 of the first computer 100. The version suggestion application 301b is, for example, a GUI. The version suggestion application 301b proposes missions and software parts to be executed to the mobile operator 1000.

[0088] The second computer 102b holds version check application 401b, replacing version check application 401 of the second computer 102. Version check application 401b creates a list of software parts necessary for executing the mission and a list of mission functions that can be executed using those software parts.

[0089] The third computer 103 holds a data transmission application 501. The data transmission application 501 transmits data received from other mobile devices to the first computer 101, the second computer 102, and the fourth computer 107. It also transmits data to other mobile devices.

[0090] The fourth computer 107 holds the integrity verification application 801. The integrity verification application 801 verifies the integrity of the software parts received from other mobile devices and the temporary storage 105.

[0091] The normal operation storage 104 stores software parts 601 and mobile unit installation information 701 that the mobile unit 10 normally uses when performing missions other than coordinated operations. Hereafter, operations performed according to mission data 1001 during normal operations will be referred to as normal operations. Software parts 601 are a group of components that divide the software into functional units, and a group of setting parameter files used for the operation of the software. Mobile unit installation information 701 is a list of software parts stored in the normal operation storage 104.

[0092] The temporary operation storage 105 stores software parts 611 and 612 that are used during coordinated operations when the mobile location 10 executes a mission related to coordinated operations.

[0093] The information processing device 110b includes a first computer 111b, a second computer 112b, a third computer 113, a fourth computer 117, a storage device 114 for normal operation, and a storage device 115 for temporary operation.

[0094] The first computer 111b, the second computer 112b, the third computer 113, and the fourth computer 117 are implemented, for example, by processors. The normal operation storage 114 or the temporary operation storage 115 are implemented, for example, by HDDs (Hard Disk Drives) or flash memory.

[0095] The mobile unit operator 1100 holds mission data 1011. Mission data 1011 is information including the name of the mission planned by the mobile unit 11 and the software parts required to execute the mission. The mission content may also include whether coordinated operation is required, the devices used by the mobile unit 10 or the mobile unit of the coordinating partner, or the operation details. The mission includes coordinated operation between the mobile unit 10 and the mobile unit 11.

[0096] The first computer 111b holds the version suggestion application 311b in place of the mission data 311 of the first computer 111. The version suggestion application 311b is a GUI. The version suggestion application 311b proposes missions and software parts to be executed to the mobile operator.

[0097] The second computer 112b holds version check application 411b instead of version check application 411 of the second computer 112. Version check application 411b determines whether coordinated operation is necessary based on mission data 1011. Version check application 411b also selects the software parts required for mission execution from the software parts pre-stored in the normal operation storage and the software parts received from other mobile devices, and executes the selected software.

[0098] Furthermore, the version check application 411b determines whether the collaborative operation can continue. If the version check application 411 determines that the collaborative operation cannot continue, it deletes the software parts received from the other mobile device from the temporary operation storage 115.

[0099] The third computer 113 holds the data transmission application 511. The data transmission application 511 transmits data received from other mobile devices to the first computer 111, the second computer 112, and the fourth computer 117. It also transmits data to other mobile devices.

[0100] The normal operation storage 114 stores software parts 611, software parts 612, and mobile unit installation information 711 that the mobile unit 11 uses during normal operation or cooperative operation.

[0101] The temporary operation storage 115 stores software parts that are used only during coordinated operations when the mobile location 11 executes a mission related to coordinated operations.

[0102] Here, software part 601 stored in the normal operation storage 104 and software part 611 stored in the normal operation storage 114 are assumed to be the same or corresponding software parts related to function A. Furthermore, software part 611 and software part 601 are assumed to be different versions, with software part 601 being version 1.0 and software part 611 being version 2.0, which is an improved version of version 1.0.

[0103] The software part 612 stored in the normal operation storage 114 is a software part related to function B, which is different from function A, and is version 1.0. Functions A and B may be used simultaneously or sequentially. For example, function A may be an imaging function around a moving object, and function B may be a function for processing the imaging data.

[0104] ***Explanation of operation*** The operation of the information processing device 100b will be explained using Figure 5. Figure 5 is a diagram showing the operation of the information processing device 100b. The operation of the information processing device 100b corresponds to each step of the cooperative operation method. In Embodiment 2, the mobile body 10 and the mobile body 11 are assumed to execute missions related to the cooperative operation.

[0105] (S201: Mission data storage process) Mobile operator 1000 saves mission data 1001 to computer 101b.

[0106] (S202: Mission data transmission process) The first computer 101b sends mission data 1001 to the version check application 401b.

[0107] (S203: Process for determining whether coordinated operation is necessary) The second computer 102b runs the version check application 401b to determine whether a coordinated operation is necessary. At this time, the second computer 102b determines that a coordinated operation is necessary if the mission data 1001 contains missions that require a coordinated operation, and determines that a coordinated operation is unnecessary if the mission data 1001 does not contain missions that require a coordinated operation. If a coordinated operation is necessary, the process proceeds to S204. If a coordinated operation is unnecessary, the process proceeds to S220.

[0108] (S204: Preparation process for sending installation information) The second computer 102b, via the version check application 401b, transmits the installation information stored in the normal operation storage 104 to the data transmission application 501 of the third computer 103. In Embodiment 2, similar to Embodiment 1, the data transmission application 501 acquires the mobile device installation information 701.

[0109] (S205: Installation information transmission process) The third computer 103 transmits the mobile device installation information acquired in S104 to the other mobile device that is the partner in the collaborative operation, using the data transmission application 501. In Embodiment 2, the third computer 103 transmits the mobile device installation information 701 to the data transmission application 511 of the mobile device 11.

[0110] (S206: Installation information reception process) The third computer 103 receives installation information held by the mobile device 11 from the data transmission application 511 via the data transmission application 501 and sends it to the version check application 401. In Embodiment 2, the data transmission application 501 receives the mobile device installation information 711 and sends it to the version check application 401b.

[0111] (S207: Mission Function List Creation Process) The second computer 102b, using the version check application 401b, creates a mission solution which is a list of software parts required to execute the mission included in the mission data 1001 and a list of mission functions that can be executed by those software parts. In Embodiment 2, the mission solution 1101 is created.

[0112] (S208: Mission Solution Proposal Process) The first computer 102b proposes the created mission solution to the mobile operator 1000 using the version suggestion application 301b. In Embodiment 2, the first computer 102b displays and proposes the mission solution 1101.

[0113] (S209: Proposed Mission Solution Acceptance Decision Process) Mobile operator 1000 selects and approves or rejects the mission solution 1101 proposed by the version suggestion application 301b of the first computer 102b. At this time, if mobile operator 1000 determines that there is a suitable mission solution 1110 among those created in S207 for the mission data 1001, it approves it. If it determines that it is unsuitable, it rejects it.

[0114] In Embodiment 2, it was determined that there was a mission solution created in S207 that was suitable for mission data 1001, and therefore, mission solution 1011 was approved.

[0115] (S210: Mission Requirements Transmission Preparation Process) The second computer 102b, using the version check application 401b, creates a mission requirement 1201, which is a request to transfer the software parts owned by the mobile unit 20, and sends it to the data transmission application 501 of the third computer 103. Here, the mission requirement requests that all software parts owned by the mobile unit 20 that can be used for coordinated operation be transferred.

[0116] (S211: Mission Requirements Transmission Process) The third computer 103 transmits the mission requirement 1201 to the mobile device 20's data transmission application 511 using the data transmission application 501.

[0117] (S212: Software part, authentication token reception process) The third computer 103 receives software parts 611, 612 and an authentication token 1401 from the mobile device 20's data transmission application 511 via the data transmission application 501.

[0118] (S213: Consistency confirmation process) The fourth computer 107 uses the integrity verification application 801 to verify the integrity of the software parts 611 and 612 received in S212, and to check for unauthorized tampering with the temporary operation storage 105, thereby determining the integrity of the received information. If the software parts are consistent and the temporary operation storage 105 has not been tampered with, it determines that the information is consistent. Otherwise, it determines that the information is inconsistent. If consistency is confirmed, the process proceeds to S214. If inconsistency is determined, the process proceeds to S220.

[0119] Here, unauthorized tampering with the temporary operation storage 105 refers, for example, to an action that affects the temporary operation storage 105 or other components mounted on the mobile device 10 by saving software parts.

[0120] (S214: Software part, authentication token transfer process) The third computer 103, via the data transmission application 501, transfers the authentication token 1401 received in S212 and the software parts that are not stored in the normal operation storage 104 to the temporary operation storage 105. In Embodiment 2, the data transmission application 501 transfers the authentication token 1401, software part 611, and software part 612 to the temporary operation storage 105.

[0121] (S215: Selection process for software components for coordinated operation) The second computer 102b uses the version check application 401b to select the software parts to be used for mission execution from among the software parts stored in the normal operation storage 104 and the software parts received from other mobile units. Here, if the mission solution 1101 approved by the mobile unit operator 1000 in S209 cannot be executed due to a failure of other components or equipment of the mobile unit 10, or other factors, the second computer 102b may select the software parts excluding those used in that mission.

[0122] In Embodiment 2, the version check application 401b selects software part 611 and software part 612 from among software part 601, software part 611, and software part 612 as software to be used in executing a mission related to coordinated operation.

[0123] In cases where there are multiple software parts related to the same function, the version check application 401b may select the newer version. Furthermore, the criteria for software part selection by the version check application 401b are predetermined by the mobile operator 1000.

[0124] (S216: Software parts installation process) The second computer 102b installs the software parts selected in S215 into the temporary operation storage 105 using the version check application 401b. In Embodiment 2, the second computer 102b transfers and installs software parts 611 and 612 into the temporary operation storage 105 using the version check application 401b.

[0125] Note that the configuration for transferring software components may differ. Furthermore, the timing of installation should be determined according to other design considerations. For example, it may be after a certain period of time has elapsed since the software components were transferred to the temporary storage 105.

[0126] (S217: Execute collaborative action) The second computer 102b executes the software selected in S215 using the version check application 401b. This allows mobile unit 10 to perform coordinated operations with mobile unit 11. When starting the coordinated operations, for example, communication may take place between each mobile unit performing the coordinated operations, and one of the mobile units may take overall control to start the coordinated operations of all mobile units.

[0127] In Embodiment 2, the version check application 401b executes the software using software parts 611 and 612. If only software parts stored in the normal operation storage 104 are selected in S215, the version check application 401b executes the software using the software parts stored in the normal operation storage 104.

[0128] (S218: Process for determining periodic receipt of authentication tokens) When the linked operation is started in S217, the second computer 102, using the version check application 401b, creates an authentication token requirement that requests the authentication token 1401 at regular intervals and sends it to the data transmission application 501 of the third computer 103.

[0129] When the data transmission application 501 receives the authentication token requirement, it sends the authentication token requirement to the data transmission application 511 of the mobile device 20. The third computer 103 receives the authentication token 1401 from the data transmission application 511 of the mobile device 20 via the data transmission application 501.

[0130] Furthermore, the version check app 401b determines whether the collaborative operation can continue. If the version check app 401b has been unable to receive the authentication token 1401 at predetermined intervals for a certain period of time, it determines that the collaborative operation cannot be continued and proceeds to S219. If the authentication token 1401 is received periodically, the version check app 401b determines that the collaborative operation can be continued and proceeds to the collaborative operation in S212.

[0131] In addition, the criteria for determining that collaborative operation cannot be continued may be, for example, the following, or a combination of the above-mentioned methods and one or more of the following methods may be used. (1) If a specified time has elapsed since communication with the other party was lost. (2) If the other party has notified in advance that communication will be impossible for a certain period of time, and communication is still impossible after that period has elapsed. (3) When coordination with the other party is only possible within a certain distance, and the distance to the other party's location exceeds the distance within which coordination is possible.

[0132] (S219: Temporary operation storage data deletion process) The second computer 102b deletes the software parts stored in the temporary operation storage 115 using the version check application 401b. As a result, the information processing device 100b returns to the state before execution of S201 and enters a standby state.

[0133] (S220: Normal operation execution process) If S203 determines that coordinated operation is unnecessary, if S209 determines that there is no suitable mission solution, or if consistency is not checked in S212, the second computer 102b will execute the normal operation included in the mission data 1001 using the version check application 401b.

[0134] Furthermore, the information processing device may send and receive software parts with multiple information processing devices. In this case, the information processing device 100b sends software parts to all mobile devices that are partners in the coordinated operation of the mobile device 10 in step S205: software parts transmission step. It also receives software parts from all of the mobile devices in step S206: software parts reception step.

[0135] The operation of the information processing device 110b will be explained using Figure 6. Figure 6 is a diagram showing the operation of the information processing device 110b. The operation of the information processing device 110b corresponds to each step of the cooperative operation method. In Embodiment 2, the mobile body 10 and the mobile body 11 are assumed to execute missions related to the cooperative operation.

[0136] (S301: Mission data storage process) The mobile operator 1100 saves the mission data 1011 to the computer 111b.

[0137] (S302: Mission data transmission process) The first computer 111b sends mission data 1011 to the version check application 411b.

[0138] (S303: Process for determining whether coordinated operation is necessary) The second computer 112b executes the version check application 411b to determine whether a coordinated operation is necessary. At this time, the second computer 112b determines that a coordinated operation is necessary if the mission data 1011 includes a mission related to the coordinated operation, and determines that a coordinated operation is unnecessary if the mission data 1011 does not include a mission related to the coordinated operation. If a coordinated operation is necessary, the process proceeds to S304. If a coordinated operation is unnecessary, the process proceeds to S322.

[0139] (S304: Preparation process for sending installation information) The second computer 112b, via the version check application 411b, transmits the installation information stored in the normal operation storage 114 to the data transmission application 511 of the third computer 113. In Embodiment 2, the data transmission application 511 acquires the mobile device installation information 711.

[0140] (S305: Installation information transmission process) The third computer 113 transmits the mobile device installation information acquired in S304 to the other mobile device, which is the partner in the collaborative operation, via the data transmission application 511. In Embodiment 2, the third computer 113 transmits the mobile device installation information 711 to the data transmission application 501 of the mobile device 10.

[0141] (S306: Installation information reception process) The third computer 113 receives installation information held by the mobile device 10 from the data transmission application 501 via the data transmission application 511 and transmits it to the version check application 411b. In Embodiment 2, the data transmission application 511 receives the mobile device installation information 701 and transmits it to the version check application 411b.

[0142] (S307: Mission Function List Creation Process) The second computer 112b, using the version check application 411b, creates a mission solution 1111, which is a list of software parts required to execute the mission included in the mission data 1011 and a list of mission functions that can be executed by those software parts.

[0143] (S308: Mission Solution Proposal Process) The first computer 112b proposes the created mission solution to the mobile operator 1100 using the version suggestion application 311b. In Embodiment 2, the version suggestion application 311b displays the mission solution 1111 and proposes it to the mobile operator 1110.

[0144] (S309: Proposed Mission Solution Acceptance Decision Process) Mobile operator 1100 determines whether to select and accept the mission solutions proposed by the first computer 111b from the version suggestion application 311b. At this time, if mobile operator 1100 determines that there is a suitable mission solution among those created in S307 for the mission data 1011, it approves it. If it determines that it is unsuitable, it rejects it.

[0145] In Embodiment 2, it was determined that there was a mission solution created in S307 that was suitable for mission data 1011, and therefore, mission solution 1111 was approved.

[0146] (S310: Request reception process) The third computer 113 receives the mission requirement 1201 from the data transmission application 501 of the third computer 103 of the mobile unit 10 via the data transmission application 511.

[0147] (S311: Requirements notification process) The first computer 111b's version proposal application 311b notifies the mobile operator 1100 that a mission requirement 1201 has been transmitted.

[0148] (S312: Requirements Acceptance, Authentication Token Creation Process) Mobile operator 1100 uses the version proposal application 311b of the first computer 111b to create a request acceptance 1301 and an authentication token 1401. After creation, it sends the request acceptance 1301 and the authentication token 1401 to the version check application 411b of the second computer 112b.

[0149] (S313: Requirements Acceptance, Authentication Token Storage Process) The version check application 411 of the second computer 112 stores the requirement acceptance 1301 and the authentication token 1401 in the normal operation storage 114.

[0150] (S314: Request Acceptance, Preparation Process for Sending Authentication Token) The normal operation storage 114 transmits software parts 611, 612 and an authentication token 1401 to the data transmission application 511 of the third computer 113.

[0151] (S315: Request Acceptance, Authentication Token Transmission Process) The data transmission application 511 of the third computer 113 transmits software parts 611, 612 and an authentication token 1401 to the data transmission application 501 of the third computer 103 of the mobile device 10.

[0152] (S316: Selection process for software parts for coordinated operation) The second computer 112b, using the version check application 411b, selects software parts to be used for executing missions included in the mission solution 1111 from the software parts stored in the normal operation storage 114, while taking into account the state of its own machine. In Embodiment 2, the version check application 411 selects software parts 611 and 612 from among software parts 611 and 612 as software to be used for executing missions related to coordinated operation.

[0153] (S317: Execute collaborative action) The second computer 112b executes the software selected in S216 using the version check application 411b. As a result, the mobile unit 10 performs coordinated operation with the mobile unit 11. In Embodiment 2, the version check application 411 executes the software using software parts 611 and 612.

[0154] (S318: Process of sending periodically updated authentication tokens) After the start of the coordinated operation, the mobile operator 1100 uses the version suggestion application 311b on the first computer 111b to create an authentication token 1401 at regular intervals. The version suggestion application 311b sends the created authentication token 1401 to the version check application 411b on the second computer 112b. The version check application 411b sends the received authentication token 1401 to the data transmission / reception application 511 on the third computer 113.

[0155] Each time the third computer 113 receives an authentication token 1401 from the data transmission application 511, the third computer 113 of the mobile device 10 continues to send it to the data transmission application 501.

[0156] (S319: Process for determining whether to continue coordinated operation) The second computer 112b uses the version check application 411b to determine whether the collaborative operation can continue. If it determines that the collaborative operation cannot be continued, the version check application 411 proceeds to S321. If it determines that the collaborative operation can be continued, the version check application 401 continues the collaborative operation in S319.

[0157] (S320: Completion of authentication token transmission process) The third computer 113 terminates the transmission of the authentication token by the data transmission application 511.

[0158] In Embodiment 2, the mobile unit 20 possessed the necessary software parts for the mission solution 1111 approved in S309, and therefore did not perform the operations corresponding to S210-S215. However, if the mobile unit 20 did not possess the necessary software parts, it may perform the operations corresponding to S210-S215 after S309 and proceed to S316, and then perform the operations corresponding to S216 between S316 and S317.

[0159] ***Explanation of Effects*** Even with an information processing device configured in this way, it can operate in cooperation with other devices even if each of the multiple mobile devices has different software parts pre-installed.

[0160] Furthermore, because software parts are sent and received from each other, even if one of the mobile units does not possess the software corresponding to the functions to be executed in the mission involving coordinated operation before the start of operation, coordinated operation can be performed after the start of operation.

[0161] Similarly, even if the execution of a mission is decided before the start of operations, if a new version of the software parts is not available before one of the mobile units leaves the manufacturing plant, if the mobile units have different owners and the other mobile unit possesses higher-performance software parts, or if it is not desirable to share software parts with other mobile units that have different owners in advance, the system will still be able to operate in cooperation using the same software parts after the start of operations.

[0162] Furthermore, in the case of an information processing device that deletes software parts received from other mobile devices from among the selected software parts when the second computer 102 determines that it is not possible to continue the cooperative operation, the software parts can be shared among multiple mobile devices only during cooperative operation. This prevents, for example, mobile devices with different owners from constantly possessing highly confidential software parts.

[0163] Furthermore, the information processing device of Embodiment 2 is When it is necessary to execute a mission involving coordinated operation with other mobile units, a third computer 103 transmits pre-stored software parts to the other mobile unit and receives software parts held by the other mobile unit from the other mobile unit, The second computer 102 selects software parts necessary for executing the mission solution related to the cooperative operation from among the pre-stored software parts and the software parts received by the third computer 103, The system includes a fourth computer 107 that verifies the integrity of the software parts received by the third computer.

[0164] As a result, the information processing device 100b of the second embodiment can enhance security by verifying the consistency of software parts transmitted and received by the fourth computer 107.

[0165] Furthermore, in cases where the second computer selects software parts excluding those used for missions that cannot be executed due to a malfunction in the mobile unit 10, it is possible to prevent the processing load and the strain on the capacity of the temporary operation storage 105 caused by installing unnecessary software parts. In addition, it is possible to reduce the security risks associated with such unnecessary software parts.

[0166] In the embodiments described herein, the relative arrangement of each component may be described, but these are illustrative in all respects and are not limited to those described in each embodiment. Therefore, countless variations not illustrated are conceivable within the scope of each embodiment. For example, this includes modifying, adding, or omitting any component, or even extracting at least one component from at least one embodiment and combining it with a component from another embodiment. In other words, it is possible to freely combine each embodiment, and to modify or omit each embodiment as appropriate.

[0167] Furthermore, to the extent that it does not create a contradiction, a component described as being provided as "one" in each of the above embodiments may be provided as "one or more." In addition, each component is a conceptual unit, including cases where one component is composed of multiple structures, and cases where one component corresponds to a part of a structure.

[0168] The various aspects of this disclosure are summarized below as an appendix.

[0169] (Note 1) A third computer transmits pre-stored software parts to the other mobile device and receives software parts from the other mobile device when it is necessary to perform a mission involving coordinated operation with other mobile devices. A second computer that selects software parts to be used for executing the mission related to the cooperative operation from among the pre-stored software parts and software parts received from the third computer, An information processing device equipped with the following features. (Note 2) The second computer is an information processing device as described in Appendix 1, which performs the selection using mission data, which is information including a list of software parts required for the execution of a planned mission by the mobile body. (Note 3) The information processing device described in Appendix 1 or 2, wherein the second computer, when selecting software parts required for executing the mission, selects a newer version of the software parts from among the pre-stored software parts and software parts received by the third computer having functions equivalent to the pre-stored software parts. (Note 4) The second computer, when it is determined that the cooperative operation cannot be continued, deletes the software parts from the selected software parts that were received from the other mobile device, as described in any one of the appendices 1 to 3, the information processing device. (Note 5) The second computer is an information processing device as described in Appendix 4, which determines that the cooperative operation cannot be continued if a predetermined time has elapsed since communication with the other mobile body was interrupted. (Note 6) The second computer, as described in Appendix 4, determines that the cooperative operation cannot be continued if it receives prior notification from the other mobile body that communication will be impossible for a certain period of time, and communication with the other mobile body is still impossible after the elapsed period of time. (Note 7) The information processing device described in Appendix 4, wherein the second computer can only perform coordinated operations with other moving objects within a certain distance, and determines that the coordinated operation cannot be continued if the distance between the second computer and the other moving object performing the coordinated operation exceeds the certain distance. (Note 8) When it is necessary to perform a mission involving coordinated operation with other mobile units, a software part transmission step is performed to transmit pre-stored software parts to the other mobile units. A software part receiving step, which involves receiving software parts from the aforementioned other mobile body, A software parts selection step for collaborative operation, which involves selecting software parts to be used for executing the mission related to the collaborative operation from among the pre-stored software parts and the received software parts, A method of coordinated operation that includes this. (Note 9) The information processing apparatus described in Appendix 1 further comprises a fourth computer for verifying the integrity of software parts received by the third computer. (Note 10) The information processing device described in Appendix 1, wherein the second computer selects a newer version of a software part to be used for executing the mission related to the cooperative operation when the software part received from the third computer has a function equivalent to the previously stored software part. (Note 11) The third computer receives an authentication token from the other mobile device at predetermined intervals. The second computer is an information processing device as described in Appendix 1, which determines that it is impossible to continue cooperative operation with the other mobile device after a certain period of time has elapsed since the third computer stopped being able to receive the authentication token at predetermined intervals. (Note 12) The third computer receives an authentication token from the other mobile device at predetermined intervals. The second computer is an information processing device as described in Appendix 1, which determines that the cooperative operation cannot be continued if the distance from the other moving object exceeds the certain distance, in cases where cooperation is only possible within a certain distance. (Note 13) The second computer, if there is a mission that cannot be executed due to a malfunction of the mobile device, selects software parts excluding the software parts used for the mission that cannot be executed, and installs the selected software parts, as described in Appendix 1. (Note 14) The system further comprises a first computer that creates a mission solution, which is a list of software parts required to execute a mission included in mission data indicating a mission planned by a mobile object, and a list of mission functions that can be executed by the software parts included in the software parts list. The information processing device described in Appendix 1. (Note 15) The linked operation method according to Appendix 8, further comprising a consistency verification step in which the consistency of information received from the other mobile body is confirmed in the software part receiving step. [Explanation of symbols]

[0170] (10, 11) Mobile unit, (100, 100b, 110, 111b) Information processing unit, (101, 101b, 111, 111b) First computer, (102, 102b, 112, 112b) Second computer, (103, 113) Third computer, (104, 114) Normal operation storage, (107, 117) Fourth computer, (105, 115) Temporary operation storage, (200, 201) Input / output device, (301, 311, 1001, 1100) Mission data, (401, 401b, 411, 411b) Version check application, (501, 511) Data transmission / reception application, (601, 611, 612) software parts, (701, 711) mobile device installation information, (1000, 1100) mobile device operator, (1101, 1111) mission solution, 1201 mission requirements, 1301 requirements acceptance, 1401 authentication token.

Claims

1. A third computer transmits pre-stored software parts to the other mobile device and receives software parts from the other mobile device when it is necessary to perform a mission involving coordinated operation with other mobile devices. A second computer that selects software parts to be used for executing the mission related to the cooperative operation from among the software parts that have been previously stored and the software parts that have been received from the third computer, An information processing device equipped with the following features.

2. The information processing device according to claim 1, wherein the second computer performs the selection using mission data, which is information including a list of software parts required for the execution of a planned mission by the mobile body.

3. The information processing apparatus according to claim 1, wherein the second computer, when selecting software parts required for executing the mission, selects a newer version of the software parts from among the pre-stored software parts and software parts received by the third computer having functions equivalent to the pre-stored software parts.

4. The information processing apparatus according to claim 1, wherein the second computer deletes the software parts received from the other mobile device from the selected software parts when it is determined that the cooperative operation cannot be continued.

5. The information processing apparatus according to claim 4, wherein the second computer determines that the cooperative operation cannot be continued if a predetermined time has elapsed since communication with the other mobile body was interrupted.

6. The information processing device according to claim 4, wherein the second computer receives prior notification from the other mobile body that communication will be impossible for a certain period of time, and if communication with the other mobile body is still impossible after the elapsed period of time, it determines that the cooperative operation cannot be continued.

7. The information processing apparatus according to claim 4, wherein the second computer determines that the cooperative operation cannot be continued if the distance between it and the other mobile body with which it is performing the cooperative operation exceeds the aforementioned certain distance, in cases where the cooperative operation is only possible with other mobile bodies within a certain distance.

8. When it is necessary to perform a mission involving coordinated operation with other mobile units, a software part transmission step is performed to transmit pre-stored software parts to the other mobile units. A software part receiving step, which involves receiving software parts from the aforementioned other mobile body, A software parts selection step for collaborative operation, which involves selecting software parts to be used for executing the mission related to the collaborative operation from among the pre-stored software parts and the received software parts, A method of coordinated operation that includes this.

9. The information processing apparatus according to claim 1, further comprising a fourth computer for verifying the integrity of software parts received by the third computer.

10. The information processing apparatus according to claim 1, wherein the second computer selects a newer version of the software part to be used for executing the mission related to the cooperative operation when the software part received from the third computer has a function corresponding to the previously stored software part.

11. The third computer receives an authentication token from the other mobile device at predetermined intervals. The information processing apparatus according to claim 1, wherein the second computer determines that it is impossible to continue cooperative operation with the other mobile device after a certain period of time has elapsed since the third computer stopped being able to receive the authentication token at predetermined intervals.

12. The third computer receives an authentication token from the other mobile device at predetermined intervals. The information processing device according to claim 1, wherein the second computer determines that the cooperative operation cannot be continued if the distance to the other moving object exceeds the certain distance, in cases where cooperation is only possible within a certain distance.

13. The information processing apparatus according to claim 1, wherein the second computer, if there is a mission that cannot be executed due to a malfunction of the mobile device, selects software parts excluding the software parts used for the mission that cannot be executed, and installs the selected software parts.

14. The system further comprises a first computer that creates a mission solution, which is a list of software parts required to execute a mission included in mission data indicating a mission planned by a mobile object, and a list of mission functions that can be executed by the software parts included in the software parts list. The information processing apparatus according to claim 1.

15. The linked operation method according to claim 8, further comprising a consistency verification step in which the consistency of information received from the other mobile body is confirmed in the software part receiving step.

Images