Method for mounting parts on carrier, method and apparatus for recording information for parts

Abstract

The present disclosure relates to an interlocking blockchain for aircraft part history and current aircraft configuration. Specifically, it relates to methods and devices for recording information for a part, such as historical information for an aircraft part. A part history blockchain network includes a part history blockchain for the part configured to record information for the part. Configuration and activity history information for a vehicle is recorded in a vehicle configuration and activity history blockchain for the vehicle in the vehicle configuration and activity history blockchain network. A part installation notification is received by the part history blockchain network. The part installation notification identifies the part and indicates that the part is installed on the vehicle. In response to receiving the part installation notification, the part history blockchain for the part is locked, thereby preventing information for the part from being added to the part history blockchain for the part as long as the part is installed on the vehicle.

Description

Technical Field

[0001] The present disclosure generally relates to systems and methods for maintaining, modifying, and tracking the operation of aircraft and other vehicles and parts for aircraft and other vehicles. More specifically, the present disclosure relates to systems and methods for using interlocking blockchains for the maintenance, modification, and activity tracking of aircraft and other vehicles and parts for aircraft and other vehicles. Background Art

[0002] The current configuration or state of an aircraft includes all systems and parts currently installed on the aircraft. It is desirable to accurately know the current configuration of an aircraft. For example, it is desirable for maintenance personnel to know the current configuration of an aircraft before performing maintenance operations on the aircraft or making other modifications to the aircraft.

[0003] There is no standardized or uniform method for tracking the current configuration of aircraft used by airlines and other aircraft operators. Some airlines and other aircraft operators may take a personal, homegrown approach to strictly determining the configuration of an aircraft when first receiving the aircraft and then tracking any changes made to the aircraft. Other airlines and other aircraft operators may not make a significant effort to continuously track the current configuration of an aircraft. In such cases, an airline or other operator of an aircraft may determine the current configuration of an aircraft by inspecting the aircraft when work is to be performed on the aircraft or when the current configuration of the aircraft is needed for some other reason.

[0004] It is also desirable to have accurate information about parts that may be installed on an aircraft, are installed on an aircraft, or have been installed on an aircraft. For example, it may be desirable to have accurate information about the creation of a part, the use of a part, the repair of a part, the modification of a part, the destruction of a part, or other final disposition or other event or combination of events that affects a part for use in an aircraft.

[0005] A blockchain is a continuously growing list of records called blocks that are linked and secured using cryptography. Each block in a blockchain typically contains a cryptographic hash of the previous block, a timestamp, and transaction data. The blockchain is inherently resistant to modifying the data stored in the blockchain. The blockchain can be used as a decentralized, distributed, and public or private authority-based digital ledger for recording transactions across many computers. The blockchain is typically managed by a peer-to-peer network that jointly adheres to a protocol for validating new blocks. Once recorded, the data in any given block cannot be retroactively changed without changing all subsequent blocks, which requires consensus from the blockchain network.

[0006] Therefore, there may be a need for methods and apparatus that take into account at least some of the issues discussed above, as well as other possible issues. Summary of the invention

[0007] The exemplary embodiments provide a method of installing a part on a carrier. Information related to the installation of a part on a carrier is received. The information for the part is recorded in a part history blockchain for the part in a part history blockchain network. The information related to the installation of the part is recorded in a vehicle configuration and activity history blockchain for the vehicle in a vehicle configuration and activity history blockchain network. The part history blockchain for the part is locked to prevent information for the part from being added to the part history blockchain for the part as long as the part is installed on the carrier.

[0008] The exemplary embodiments also provide a method for recording information for a part. The part history blockchain network includes a part history blockchain for the part configured to record information for the part. Configuration and activity history information for a carrier is recorded in a carrier configuration and activity history blockchain for the carrier in the carrier configuration and activity history blockchain network. A part installation notification is received by the part history blockchain network. The part installation notification identifies the part and indicates that the part is installed on the carrier. In response to receiving the part installation notification, the part history blockchain for the part is locked, thereby preventing information for the part from being added to the part history blockchain for the part as long as the part is installed on the carrier.

[0009] The exemplary embodiment also provides a device for recording information for a part. A data processing system in a part history blockchain network is configured to receive a part installation notification. The part installation notification identifies the part and indicates that the part is installed on a carrier. The part history blockchain network includes a part history blockchain for the part configured to record information for the part. Configuration and activity history information for the carrier is recorded in a carrier configuration and activity history blockchain for the carrier in the carrier configuration and activity history blockchain network. The data processing system is configured to lock the part history blockchain for the part in response to receiving a part installation notification, thereby preventing information for the part from being added to the part history blockchain for the part as long as the part is installed on the carrier.

[0010] The features and functions can be achieved independently in various embodiments of the present disclosure or may be combined in yet other embodiments, in which further details can be seen with reference to the following description and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The novel features which are believed to be characteristic of the exemplary embodiments are set forth in the appended claims. However, the exemplary embodiments and their preferred modes of use, further objects and features will be apparent from and will be understood in conjunction with the appended claims. Figure 1 The present disclosure is best understood when read with reference to the following detailed description of exemplary embodiments of the present disclosure, in which:

[0012] Figure 1 is a diagram of an interlocking blockchain network according to an exemplary embodiment;

[0013] Figure 2 is a diagram of a vehicle configuration and activity history tracking system according to an exemplary embodiment;

[0014] Figure 3 is a diagram of a part history tracking system according to an illustrative embodiment;

[0015] Figure 4 is a diagram of a flow chart of a process for installing a part on a carrier using an interlocking part history and carrier configuration and activity history blockchain according to an illustrative embodiment;

[0016] Figure 5 is a diagram of a flow chart of a process for removing a part from a carrier using an interlocking part history and a carrier configuration and activity history blockchain according to an illustrative embodiment;

[0017] Figure 6 is a diagram of a flow chart of a process for storing part information for a part using an interlocking part history and carrier configuration and activity history blockchain according to an illustrative embodiment; and

[0018] Figure 7 is a diagram of a block diagram of a data processing system according to an illustrative embodiment. DETAILED DESCRIPTION

[0019] The illustrative embodiments recognize and take into account different considerations. For example, the illustrative embodiments recognize and take into account the following: When an aircraft is first delivered from the aircraft manufacturer to the operator of the aircraft, the configuration of the aircraft may be known and documented. However, after delivery, as changes are made to the aircraft for maintenance, repairs, or upgrades, the current aircraft configuration may not be known with certainty. If records are not kept consistent, the reliability of the current aircraft configuration information may be questionable. If the current aircraft configuration information cannot be relied upon to be accurate, maintenance personnel may have to spend time inspecting the aircraft before performing work on the aircraft, and then studying and reviewing the actual parts installed on the aircraft.

[0020] Related problems may occur when an aircraft is transferred from one operator to another. For example, an airline receiving an aircraft from another airline may require extensive inspection work to confirm the current configuration of the received aircraft if the current aircraft configuration record cannot be relied upon.

[0021] The illustrative embodiments also recognize and take into account that currently, depending on the nature of the parts supplier, the history and status of the aircraft's parts may be unclear or questionable. In some cases, the history and status records of aircraft parts may be tampered with or otherwise inaccurate. For example, the history and status records for a part provided by a supplier for installation on an aircraft may actually be records for another part that is currently already installed on the aircraft.

[0022] Exemplary embodiments use interlocking blockchains to improve the accuracy and reliability of records related to the configuration and activity history of aircraft and other vehicles, and the history of parts used for aircraft and other vehicles. Exemplary embodiments provide systems and methods whereby records in one blockchain are locked when a transition occurs with respect to an item tracked by another blockchain or with respect to another item in another blockchain.

[0023] For example, the exemplary embodiments provide an interlocking blockchain network for vehicle configuration and activity history and part history records. Information describing events that change a vehicle or otherwise affect a vehicle is recorded in a vehicle configuration and activity history blockchain in the vehicle configuration and activity history blockchain network. Information describing events that change a part or otherwise affect a part is recorded in a part history blockchain in the part history blockchain network.

[0024] Information related to the installation of a part on a carrier may be recorded in a carrier configuration and activity history blockchain in a carrier configuration and activity history blockchain network and in a part history blockchain for the part in a part history blockchain network. In response to the installation of the part on the carrier, the part history blockchain for the part in the part history blockchain network is locked so that no changes to the part history for the part can be recorded in the part history blockchain. The part history blockchain remains locked as long as the part is installed on the carrier. Information related to the removal of the part from the carrier may be recorded in the carrier configuration and activity history blockchain in the carrier configuration and activity history blockchain network. In response to the removal of the part from the carrier, the part history blockchain for the part in the part history blockchain network may be unlocked so that information related to the removal of the part from the carrier and information related to subsequent events that change or otherwise affect the part can be recorded in the part history blockchain for the part in the part history blockchain network.

[0025] The parts history blockchain and blockchain network and the vehicle configuration and activity history blockchain and blockchain network according to the exemplary embodiments are based on blockchain technology that allows for distributed record maintenance with easy data transactions and high data authenticity. The exemplary embodiments can be implemented in a cloud computing environment and widely distributed to use interlocking blockchains for maintaining aircraft configuration and activity history records and aircraft parts history records that are highly accessible to airlines, other aircraft operators, and maintenance, repair, and operation providers and systems. The exemplary embodiments can interoperate with existing maintenance, repair, and operation systems via, for example, application programming interface calls.

[0026] Go to Figure 1 , depicts a diagram of an interlocking blockchain network according to an exemplary embodiment. The interlocking blockchain network 100 includes a vehicle configuration and activity history blockchain network 102 and a parts history blockchain network 104.

[0027] The vehicle configuration and activity history blockchain network 102 is configured to maintain a record of information related to events that affect the configuration of an aircraft or other vehicle or otherwise affect an aircraft or other vehicle. The vehicle configuration and activity history blockchain network 102 includes a plurality of nodes. A vehicle configuration and activity history blockchain network according to an exemplary embodiment may include any suitable number of nodes. In this example, the vehicle configuration and activity history blockchain network 102 includes nodes 108, 110, 112, 114, 116, 118, and 120. A vehicle configuration and activity history blockchain network according to an exemplary embodiment may have more than one node. Figure 1 Instantiate more or fewer nodes.

[0028] Information for events that affect the configuration of a vehicle or otherwise affect a vehicle may be recorded in a vehicle configuration and activity history blockchain for the vehicle in the vehicle configuration and activity history blockchain network 102. Each node 108, 110, 112, 114, 116, 118, and 120 in the vehicle configuration and activity history blockchain network 102 may store a full copy of the vehicle configuration and activity history blockchain for the vehicle. Figure 2 A more detailed description of an example of a vehicle configuration and activity history blockchain network 102 is presented.

[0029] The part history blockchain network 104 is configured to maintain a record of information related to events that change or otherwise affect parts for an aircraft or other vehicle. The part history blockchain network 104 includes a plurality of nodes. A part history blockchain network according to an exemplary embodiment may include any suitable number of nodes. In this example, the part history blockchain network 104 includes nodes 128, 130, 132, 134, 136, 138, and 140. A part history blockchain network according to an exemplary embodiment may have more than one node. Figure 1 Instantiate more or fewer nodes.

[0030] Information about events that change or otherwise affect a part may be recorded in a part history blockchain for the part in the part history blockchain network 104. Each node 128, 130, 132, 134, 136, 138, and 140 in the part history blockchain network 104 may store a full copy of the part history blockchain for the part. Figure 3 A more detailed description of an example of a part history blockchain network 104 is presented.

[0031] The part history for a particular part may be maintained in a part history blockchain for the part in the part history blockchain network 104. When the part is installed in a vehicle in a vehicle configuration and activity history blockchain in the vehicle configuration and activity history blockchain network 102, in which configuration and activity history information is maintained, a lock transaction 142 may be implemented. As part of the lock transaction 142, a token 144 representing the part may be passed from the part history blockchain network 104 to the vehicle configuration and activity history blockchain network 102 to indicate that the part is now installed on or otherwise associated with a particular vehicle. As part of the lock transaction 142, the part history blockchain for the part in the part history blockchain network 104 is locked. Assuming the part is installed on the vehicle, when the part history blockchain for the part is locked, no additional transactions or events that may change the part history blockchain for the part will be identified. The part history blockchain for the part in the part history blockchain network 104 may remain locked as long as the part is installed on the vehicle.

[0032] When the part is removed from the carrier, an unlock transaction 146 may be implemented. As part of the unlock transaction 146, a credential 144 representing the part may be transferred from the carrier configuration and activity history blockchain network 102 back to the part history blockchain network 104. As part of the unlock transaction 146, a part history blockchain for the part in the part history blockchain network 104 is unlocked. When the part history blockchain for the part is unlocked, information for events that change or otherwise affect the part may be recorded in the part history blockchain for the part. For example, the first transaction that the part history blockchain for the part may accept after the part history blockchain is unlocked by the unlock transaction 146 may be a record of information related to the removal of the part from the carrier.

[0033] Figure 1 The diagram of the interlocking blockchain network 100 in is not meant to imply limitations on the manner in which the illustrative embodiments may be implemented. Other components in addition to or in place of the illustrated components may be used. Some components may be optional. Likewise, blocks may be presented to illustrate some functional components. When implemented in the illustrative embodiments, one or more of these blocks may be combined, divided, or combined and divided into different blocks.

[0034] Go to Figure 2 , depicts a diagram of a vehicle configuration and activity history tracking system according to an illustrative embodiment. The vehicle configuration and activity history tracking system 200 is configured to track the exact current configuration 202 of a vehicle 204. The vehicle configuration and activity history tracking system 200 can be configured for the current configuration 202 of any suitable number of various types of vehicles.

[0035] For example and without limitation, vehicle configuration and activity history tracking system 200 may be an aircraft configuration and activity history tracking system configured to track current configuration 202 of aircraft 205. Vehicle configuration and activity history tracking system 200 may be used to track current configuration 202 of vehicles 204 other than aircraft 205. In alternative embodiments, vehicle configuration and activity history tracking system 200 may be used to track current configuration of fixed or mobile platforms other than vehicles.

[0036] Aircraft 205 may be any suitable type of aircraft that may be configured to perform any suitable operation or mission. For example and without limitation, aircraft 205 may be a commercial airliner, a cargo aircraft, a military aircraft, a personal aviation aircraft, or any other suitable type of aircraft. Aircraft 205 may be a fixed-wing aircraft, a rotary-wing aircraft, or a lighter-than-air aircraft. Aircraft 205 may be a manned aircraft or an unmanned aerial vehicle.

[0037] The vehicle configuration and activity history tracking system 200 includes a vehicle configuration and activity history blockchain network 206. The vehicle configuration and activity history blockchain network 206 is Figure 1 206 is a blockchain network configured to store and maintain configuration and activity history information for a number of vehicles. For example and without limitation, the vehicle configuration and activity history blockchain network 206 may be a blockchain network configured to store and maintain aircraft configuration and activity history information for the aircraft 205. In this case, the vehicle configuration and activity history blockchain network 206 may be an aircraft configuration and activity history blockchain network.

[0038] The vehicle configuration and activity history blockchain network 206 includes a plurality of nodes. The vehicle configuration and activity history blockchain network according to an exemplary embodiment may include any suitable number of nodes. In this example, the vehicle configuration and activity history blockchain network 206 includes nodes 208, 210, 212, 214, 216, 218, and 220. The vehicle configuration and activity history blockchain network according to an exemplary embodiment may have more than Figure 2 More or fewer nodes are illustrated. Each node 208, 210, 212, 214, 216, 218, and 220 in the vehicle configuration and activity history blockchain network 206 may be controlled by an entity that has agreed to participate in the operation and use of the vehicle configuration and activity history blockchain network 206 in order to accurately track the configuration and activity history of an aircraft 205 or other vehicle 204 over time.

[0039] The vehicle configuration and activity history information is stored in a blockchain in the vehicle configuration and activity history blockchain network 206. A unique vehicle configuration and activity history blockchain may be created for each aircraft 205 and other vehicle 204 for which configuration and activity history information is to be tracked in the vehicle configuration and activity history blockchain network 206. A copy of the vehicle configuration and activity history blockchain for each vehicle 204 may be maintained at each node 208, 210, 212, 214, 216, 218, and 220 in the vehicle configuration and activity history blockchain network 206. For example, each node 208, 210, 212, 214, 216, 218, and 220 in the vehicle configuration and activity history blockchain network 206 may be configured to store a full copy of the vehicle configuration and activity history blockchain 222 for the vehicle 204. For example and without limitation, each node 208, 210, 212, 214, 216, 218, and 220 in the vehicle configuration and activity history blockchain network 206 may be configured to store a full copy of the vehicle configuration and activity history blockchain 222 for the aircraft 205. In this case, the vehicle configuration and activity history blockchain 222 is an aircraft configuration and activity history blockchain.

[0040] Only trusted entities 224 may have permission to access the vehicle configuration and activity history blockchain network 206 to read information from and submit changes to the vehicle configuration and activity history blockchain 222 for the vehicle 204. For example and without limitation, the trusted entity 224 may be the owner or operator of the vehicle 204 or any other suitable trusted entity. For example and without limitation, the trusted entity 224 may be an airline or other operator or owner of the aircraft 205 that may have permission to read information from and submit changes to the vehicle configuration and activity history blockchain 222 for the aircraft 205. Another trusted entity 224, such as the manufacturer of the aircraft 205, a provider of maintenance and repair operations for the aircraft 205, or another suitable entity may also have permission to read information from and submit changes to the vehicle configuration and activity history blockchain 222 for the aircraft 205. Another trusted entity 224 may receive permission to access the vehicle configuration and activity history blockchain network 206 for the vehicle 204 from the owner of the vehicle 204.

[0041] The trusted entity 224 may use the configuration and activity history tracking software 225 to access the vehicle configuration and activity history blockchain 222 at one or more nodes 208, 210, 212, 214, 216, 218, and 220 of the vehicle configuration and activity history blockchain network 206. The configuration and activity history tracking software 225 may be configured to run on a data processing system to provide various functions for accessing the vehicle configuration and activity history blockchain 222, reading information from the vehicle configuration and activity history blockchain 222, using information read from the vehicle configuration and activity history blockchain 222, and storing new information in the vehicle configuration and activity history blockchain 222 in the vehicle configuration and activity history blockchain network 206. The configuration and activity history tracking software 225 may be implemented in any suitable manner to perform the functions described herein.

[0042] The vehicle configuration and activity history blockchain 222 includes several blocks. A first block 230 in the vehicle configuration and activity history blockchain 222 may be created when the vehicle configuration and activity history blockchain 222 for the vehicle 204 is added to the vehicle configuration and activity history blockchain network 206. For example and without limitation, when the aircraft 205 is a new aircraft to be delivered from the aircraft manufacturer to the aircraft operator, the vehicle configuration and activity history blockchain 222 for the aircraft 205 may be added to the vehicle configuration and activity history blockchain network 206. In this case, the first block 230 in the vehicle configuration and activity history blockchain 222 for the aircraft 205 may include a record 232 of an initial configuration information location where information identifying the initial configuration of the aircraft 205 may be found. The initial configuration information available at the initial configuration information location may describe both the initial parts installed in the aircraft 205 and any known inconsistencies in the aircraft 205 at the end of production of the aircraft 205 and before delivery from the manufacturer of the aircraft 205 to the operator.

[0043] In the case of a vehicle configuration and activity history blockchain for an in-service aircraft or other vehicle that is not newly added to the vehicle configuration and activity history blockchain network 206, the first block 230 in the vehicle configuration and activity history blockchain 222 may include a record 232 of the location of the initial configuration information for the known current configuration of the aircraft 205 or other vehicle 204. In any case, the first block 230 of the vehicle configuration and activity history blockchain 222 may identify the location of the initial configuration information recorded in the vehicle configuration and activity history blockchain 222 for the known first current configuration state of the aircraft 205 or other vehicle 204.

[0044] The first block 230 in the vehicle configuration and activity history blockchain 222 may be created and encrypted 233 using a conventional hash value. Subsequent blocks 242, 244, and 246 in the vehicle configuration and activity history blockchain 222 may be created and encrypted 243, 245, 247, respectively, using a hash value and each new block referencing the previous block in the vehicle configuration and activity history blockchain 222. As blocks are added to the vehicle configuration and activity history blockchain 222, the robustness of the encryption increases because the encryption of each subsequent block is based on the previous block. Therefore, it becomes exponentially more difficult to fraudulently change any of the blocks 230, 242, 244, or 246 in the vehicle configuration and activity history blockchain 222 without being detected.

[0045] A trusted entity 224 having appropriate authority to access the vehicle configuration and activity history blockchain network 206 to provide updates to the vehicle configuration and activity history blockchain 222 for the vehicle 204 may submit a transaction 254 to the vehicle configuration and activity history blockchain network 206. The transaction 254 may include new information related to the vehicle 204. The transaction 254 may be generated in response to the occurrence of an event 256 that may affect the configuration of the vehicle 204 or involve an operation of the vehicle 204 that is desired to be recorded in the vehicle configuration and activity history blockchain network 206. The information included in the transaction 254 for recording in the vehicle configuration and activity history blockchain network 206 may include appropriate information describing the event 256.

[0046] For example, the information included in the transaction 254 for recording in the vehicle configuration and activity history blockchain network 206 may include maintenance information, modification information, activity information, or any other suitable information or combination of information related to the configuration or operation of the vehicle 204. The maintenance information may include information describing the maintenance operation performed on the vehicle 204. For example and without limitation, the maintenance information may include information related to the inspection of a part on the vehicle 204, the repair of a part, or the replacement of a part. The modification information may identify changes to the vehicle 204 other than those performed by the maintenance operation. The activity information may include information identifying the operation of the vehicle 204. For example and without limitation, when the vehicle 204 is an aircraft 205, the activity information may identify operations performed by the aircraft 205, such as completed takeoffs and landings, flight time, changes in ownership, or other activities involving the aircraft 205.

[0047] The information included in any new transaction 254 added to the vehicle configuration and activity history blockchain 222 in the vehicle configuration and activity history blockchain network 206 is propagated 258 across the vehicle configuration and activity history blockchain network 206 to all nodes 208, 210, 212, 214, 216, 218, and 220 in the vehicle configuration and activity history blockchain network 206. At each node 208, 210, 212, 214, 216, 218, and 220, a new block 246 may be added to the internally maintained copy of the vehicle configuration and activity history blockchain 222 to include a record 252 of the new information provided by the transaction 254 related to the vehicle 204.

[0048] According to an exemplary embodiment, the event 256 may be the installation of a part on the carrier 204. In this case, the transaction 254 may include information identifying the part installed on the carrier 204, which is stored in the carrier configuration and activity history blockchain 222 for the carrier 204 in the carrier configuration and activity history blockchain network 206. The historical information for the part installed on the carrier 204 may be recorded in the part history blockchain network 260. In this case, the configuration and activity history tracking software 225 may be configured to send a part installation notification 262 to the part history blockchain network 260 to notify the part history blockchain network 260 that the part has been installed on the carrier 204. The part installation notification 262 may be provided to the part history blockchain network 260 in any suitable format and by any suitable method.

[0049] In response to receiving part installation notification 262, part history blockchain network 260 may send credential 264 to aircraft configuration and activity history blockchain network 206 and may lock the part history blockchain for the part in part history blockchain network 260 to prevent any additional changes to the information recorded in part history blockchain network 260 for the part. The part history blockchain for the part may remain locked until credential 264 is returned to part history blockchain network 260.

[0050] Later, event 256 may be the removal of a part from carrier 204. In this case, transaction 254 may include information indicating that a part has been removed from carrier 204, which is stored in carrier configuration and activity history blockchain 222 for carrier 204 in carrier configuration and activity history blockchain network 206. In this case, configuration and activity history tracking software 225 may be configured to send part removal notification 266 to part history blockchain network 260 to notify part history blockchain network 260 that a part installed on carrier 204 has been removed. Part removal notification 266 may be provided to part history blockchain network 260 in any suitable format and by any suitable method.

[0051] The voucher 264 may be returned to the part history blockchain network 260 along with or as part of the part removal notification 266. In response to receiving the voucher 264, the part history blockchain network 260 may unlock the part history blockchain for the part in the part history blockchain network 260 to allow changes to the information recorded in the part history blockchain network 260 for the part.

[0052] A trusted entity 224 having appropriate permissions to access the vehicle configuration and activity history blockchain 222 for the vehicle 204 will be able to access the vehicle configuration and activity history blockchain network 206 and read information 268 from the vehicle configuration and activity history blockchain 222 for the vehicle 204. The first block 230 in the vehicle configuration and activity history blockchain 222 for the vehicle 204 provides a record 232 that identifies location information of the initial configuration of the vehicle 204 when the vehicle 204 joins the vehicle configuration and activity history blockchain network 206. Each of the subsequent blocks 242, 244, and 246 includes a record 248, 250, 252, respectively, of each subsequent transaction submitted to the vehicle configuration and activity history blockchain network 206 for the vehicle 204. Thus, the trusted entity 224 can determine the current configuration of the vehicle 204 from this information.

[0053] The authenticity of the data for the vehicle configuration and activity history blockchain 222 at the nodes 208, 210, 212, 214, 216, 218, and 220 in the vehicle configuration and activity history blockchain network 206 may be verified by checking the equivalent vehicle configuration and activity history blockchain at other nodes in the vehicle configuration and activity history blockchain network 206 and comparing the hash value of the last block in the blockchain. For example, to confirm the authenticity of the data from the vehicle configuration and activity history blockchain 222 obtained from the node 208 of the vehicle configuration and activity history blockchain network 206, the trusted entity 224 may compare the hash value of the last block 246 in the vehicle configuration and activity history blockchain 222 with the hash value of the last block in the corresponding vehicle configuration and activity history blockchain in one or more other nodes 210, 212, 214, 216, 218, or 220 in the vehicle configuration and activity history blockchain network 206.

[0054] Figure 2The diagram of vehicle configuration and activity history tracking system 200 in the example is not meant to imply limitations on the manner in which the illustrative embodiments may be implemented. Other components in addition to or in place of the illustrated components may be used. Some components may be optional. Likewise, blocks may be presented to illustrate some functional components. One or more of these blocks may be combined, divided, or combined and divided into different blocks when implemented in the illustrative embodiments.

[0055] Go to Figure 3 , depicts a diagram of a part history tracking system according to an illustrative embodiment. Part history tracking system 300 is configured to accurately track the history of part 302. Part history tracking system 300 may be configured to track the history of any suitable number of any suitable various types of parts.

[0056] The part history tracking system 300 may be a carrier part history tracking system configured to track the history of a carrier part 304. The carrier part 304 may be any suitable part for any suitable carrier. For example, the carrier part 304 may be a carrier part for a Figure 2 For example and without limitation, part history tracking system 300 may be an aircraft part history tracking system configured to track the history of aircraft part 305. Aircraft part 305 may be any suitable part for any suitable aircraft. For example, aircraft part 305 may be a part for Figure 2 In an alternative embodiment, part history tracking system 300 may be configured to track the history of parts for a fixed or mobile platform other than a vehicle.

[0057] The part history tracking system 300 includes a part history blockchain network 306. The part history blockchain network 306 is Figure 1 Parts in the History Blockchain Network 104 and Figure 2 306 is an example of a possible implementation of part history blockchain network 260 in FIG. Part history blockchain network 306 is a blockchain network configured to store and maintain historical information for a number of parts. For example and without limitation, part history blockchain network 306 may be a blockchain network configured to store and maintain aircraft part history information for aircraft part 305. In this case, part history blockchain network 306 may be an aircraft part history blockchain network.

[0058] The part history blockchain network 306 includes a plurality of nodes. A part history blockchain network according to an exemplary embodiment may include any suitable number of nodes. In this example, the part history blockchain network 306 includes nodes 308, 310, 312, 314, 316, 318, and 320. A part history blockchain network according to an exemplary embodiment may have more than one node. Figure 3 More or fewer nodes are illustrated. Each node 308, 310, 312, 314, 316, 318, and 320 in the part history blockchain network 306 may be controlled by an entity that has agreed to participate in the operation and use of the part history blockchain network 306 for the purpose of accurately tracking the history of the part 302 over time.

[0059] The part history information is stored in a blockchain in the part history blockchain network 306. A part history blockchain may be created for each part 302 for which history information is to be tracked in the part history blockchain network 306. A copy of the part history blockchain for each part 302 may be maintained at each node 308, 310, 312, 314, 316, 318, and 320 in the part history blockchain network 306. For example, each node 308, 310, 312, 314, 316, 318, and 320 in the part history blockchain network 306 may be configured to store a full copy of the part history blockchain 322 for the part 302. For example and without limitation, each node 308, 310, 312, 314, 316, 318, and 320 in the part history blockchain network 306 may be configured to store a full copy of the part history blockchain 322 for the aircraft part 305. In this case, the part history blockchain 322 is an aircraft part history blockchain.

[0060] Only trusted entities 324 may have permission to access part history blockchain network 306 to read information from and submit changes to part history blockchain 322 for part 302. For example, trusted entity 324 may be the owner of part 302 or any other entity that controls part 302. For example and without limitation, trusted entity 324 may be a supplier of part 302 or the owner of a vehicle to which vehicle part 304 may be installed. For example, trusted entity 324 may be an airline or other operator or owner of an aircraft to which aircraft part 305 may be installed. Another trusted entity 324, such as a manufacturer of an aircraft or other vehicle, a provider of maintenance and repair operations for an aircraft or other vehicle, or another appropriate entity may also have permission to read information from and submit changes to part history blockchain 322 for part 302. Another trusted entity 324 may receive permission to access part history blockchain network 306 for part 302 from the owner of part 302.

[0061] Trusted entity 324 may use part history tracking software 325 to access part history blockchain 322 at one or more nodes 308, 310, 312, 314, 316, 318, and 320 of part history blockchain network 306. Part history tracking software 325 may be configured to run on a data processing system to provide various functions for accessing part history blockchain 322, reading information from part history blockchain 322, using information read from part history blockchain 322, and storing new information in part history blockchain 322 in part history blockchain network 306. Part history tracking software 325 may be implemented in any suitable manner to perform the functions described herein.

[0062] The part history blockchain 322 includes several blocks. A first block 330 in the part history blockchain 322 may be created when the part history blockchain 322 for part 302 is added to the part history blockchain network 306. For example and without limitation, the part history blockchain 322 for part 302 may be added to the part history blockchain network 306 when part 302 is initially created. In this case, the first block 330 in the part history blockchain 322 for part 302 may include: information describing the creation of part 302, information describing part 302 at the time of creation, or other appropriate initial information or various combinations of information for part 302. Alternatively, the part history blockchain 322 for part 302 may be added to the part history blockchain network 306 at some later time after the part 302 is created. In any case, the first block 330 in the part history blockchain 322 for part 302 may include: information describing part 302 when the part history blockchain 322 for part 302 is added to the part history blockchain network 306.

[0063] The first block 330 in the part history blockchain 322 may be created and encrypted 333 using a conventional hash value. Subsequent blocks 342, 344, and 346 in the part history blockchain 322 may be created and encrypted 343, 345, 347, respectively, using a hash value and each new block referencing the previous block in the part history blockchain 322. As blocks are added to the part history blockchain 322, the robustness of the encryption increases because the encryption of each subsequent block is based on the previous block. Therefore, it becomes exponentially more difficult to fraudulently alter any of the blocks 330, 342, 344, or 346 in the part history blockchain 322 without being detected.

[0064] A trusted entity 324, having appropriate authority to access the part history blockchain network 306 to provide updates to the part history blockchain 322 for the part 302, may submit a transaction 354 to the part history blockchain network 306. The transaction 354 may include new information related to the part 302. For example and without limitation, the transaction 354 may be generated in response to the occurrence of an event 356 that may change or otherwise affect or involve the part 302, and it is desired to record the event in the part history blockchain network 306. The information included in the transaction 354 for recording in the part history blockchain network 306 may include appropriate information describing the event 356. For example, the information included in the transaction 354 for recording in the part history blockchain network 306 may include information related to the creation, use, inspection, rework, destruction, or other disposition of the part 302.

[0065] Information included in any new transaction 354 added to the part history blockchain 322 in the part history blockchain network 306 is propagated 358 across the part history blockchain network 306 to all nodes 308, 310, 312, 314, 316, 318, and 320 in the part history blockchain network 306. At each node 308, 310, 312, 314, 316, 318, and 320, a new block 346 may be added to the internally maintained copy of the part history blockchain 322. New information about the part 302, as represented in the transaction 354, may be stored in the newly added block 346 as a record 352 of such information.

[0066] According to an exemplary embodiment, event 356 may be: installation of part 302 on a vehicle whose configuration and activity history information is recorded in vehicle configuration and activity history blockchain network 360. For example, event 356 may be: installation of vehicle part 304 on a vehicle whose configuration and activity history information is recorded in vehicle configuration and activity history blockchain network 360. Figure 2 304 in the vehicle configuration and activity history blockchain network 206 in the vehicle configuration and activity history blockchain network 206. In this case, the part history blockchain network 306 may receive a part installation notification 362 from the vehicle configuration and activity history blockchain network 360 or from another suitable source. The part installation notification 362 may identify the part 302 installed on the vehicle and may include any other suitable information related to the installation of the part 302. In this case, the transaction 354 may include any suitable information related to the installation of the part 302 on the vehicle to be recorded in the part history blockchain 322 for the part 302.

[0067] In response to receiving part installation notification 302 or other information indicating the installation of part 302, part history blockchain network 306 may send voucher 364 to aircraft configuration and activity history blockchain network 360 and may lock part history blockchain 322 for part 302 in part history blockchain network 306 to prevent any additional changes to the information recorded in part history blockchain network 306 for part 302. Part history blockchain 322 for part 302 may remain locked until voucher 364 is returned to part history blockchain network 306, which indicates the removal of the part from the vehicle in which part 302 was installed. Thus, the information related to the installation of part 302 in record 352 in part history blockchain 322 may be the most current information for part 302 added to part history blockchain network 306 until the part is removed from the vehicle in which part 302 was installed and part history blockchain network 306 is unlocked to allow additional information related to part 302 to be recorded internally.

[0068] Subsequently, event 356 may be the removal of part 302 from the carrier to which part 302 was installed. In this case, part history blockchain network 306 may receive part removal notification 366 from carrier configuration and activity history blockchain network 360 or from another suitable source. Part removal notification 366 may indicate the removal of the part from the carrier to which part 302 was installed, and may include any other suitable information related to the removal of part 302 from the carrier.

[0069] Voucher 364 may be returned to part history blockchain network 306 along with or as part of part removal notification 366. In response to receiving voucher 364, part history blockchain network 306 may unlock part history blockchain 322 for part 302 in part history blockchain network 306 to allow changes to information recorded in part history blockchain network 306 for part 302. In this case, first transaction 354 that adds new information for part 302 to part history blockchain network 306 after unlocking part history blockchain 322 for part 302 may include information related to the removal of part 302 from a carrier on which part 302 is mounted.

[0070] A trusted entity 324 having appropriate permissions to access the part history blockchain 322 for part 302 will be able to access the part history blockchain network 306 and read information 368 for part 302 from the part history blockchain 322. Blocks 330, 342, 344, and 346 in the part history blockchain 322 include records 332, 348, 350, and 352, respectively, of information related to part 302, activities involving part 302, or both that have been submitted to the part history blockchain network 306. Thus, the trusted entity 324 can determine the current state of the part 302 from the information.

[0071] The authenticity of the data for the part history blockchain 322 at the nodes 308, 310, 312, 314, 316, 318, and 320 in the part history blockchain network 306 can be verified by checking the equivalent part history blockchain at other nodes in the part history blockchain network 306 and comparing the hash value for the last block in the blockchain. For example, to confirm the authenticity of the data from the part history blockchain 322 obtained from the node 308 of the part history blockchain network 306, the trusted entity 324 can compare the hash value for the last block 346 in the part history blockchain 322 with the hash value of the last block in the corresponding blockchain in one or more other nodes 310, 312, 314, 316, 318, or 320 in the part history blockchain network 306.

[0072] Figure 3 The diagram of the part history tracking system 300 in the example is not meant to imply limitations on the manner in which the illustrative embodiments may be implemented. Components other than or in place of the illustrative components may be used. Some components may be optional. Likewise, blocks may be presented to illustrate some functional components. One or more of these blocks may be combined, divided, or combined and divided into different blocks when implemented in the illustrative embodiments.

[0073] Go to Figure 4 , depicts a diagram of a flow chart of a process for installing a part on a carrier using an interlocking part history and a carrier configuration and activity history blockchain, according to an illustrative embodiment. The process 400 may be performed in, for example, Figure 1 Vehicle configuration and activity history in blockchain network 102 or Figure 2 The vehicle configuration and activity history tracking system 200 is implemented in.

[0074] Process 400 may begin by receiving information related to the installation of a part on a carrier, wherein part history information for the part is recorded in a part history blockchain network (operation 402). The received information may identify the part installed on the carrier and may include other information related to the installation of the part on the carrier. The information related to the installation of the part on the carrier may be recorded in a carrier configuration and activity history blockchain for the part in the carrier configuration and activity history blockchain network (operation 404).

[0075] A part installation notification may be sent to a part history blockchain network that records part history information for the part (operation 406). The part installation notification may identify the installed part and indicate that the part is installed on the carrier. The part history blockchain network may internally lock the part history blockchain for the part to prevent any new information for the part from being recorded in the part history blockchain network as long as the part is installed on the carrier. The part history blockchain network may send a credential to the vehicle configuration and activity history blockchain network. The part history blockchain for the part in the part history blockchain network may remain locked to prevent the addition of new information for the part until the credential is returned to the part history blockchain network. Thus, the credential may be received and saved by the vehicle configuration and activity history blockchain network (operation 408), with the process terminating thereafter.

[0076] Go to Figure 5 , depicts a diagram of a flow chart of a process for removing a part from a carrier using an interlocking part history and a carrier configuration and activity history blockchain, according to an illustrative embodiment. The process 500 may be performed in, for example, Figure 1 Vehicle configuration and activity history in blockchain network 102 or Figure 2 The process 500 may be implemented in the vehicle configuration and activity history tracking system 200 in the embodiment of the present invention. Figure 4 The parts, vehicles, parts history blockchain network, and vehicle configuration and activity history blockchain network mentioned in the description of process 500 can be connected to Figure 4 The same as mentioned in the description of process 400 in FIG.

[0077] Process 500 may begin by receiving information related to removal of a part from a carrier, wherein part history information for the part is recorded in a part history blockchain network (operation 502). The received information may identify the part removed from the carrier and may include other information related to the removal of the part from the carrier. The information related to the removal of the part from the carrier may be recorded in a carrier configuration and activity history blockchain for the part in the carrier configuration and activity history blockchain network (operation 504).

[0078] A part removal notification may be sent to a part history blockchain network that records part history information for the part (operation 506). The part removal notification may identify the part that was removed and indicate that the part was removed from the carrier on which the part was installed. The credential received from the part history blockchain network may also be returned to the part history blockchain network (operation 508), with the process terminating thereafter. In response to receiving the credential, the part history blockchain network may internally unlock the part history blockchain for the part to allow new information for the part to be recorded in the part history blockchain network.

[0079] Go to Figure 6 , depicts a diagram of a flow chart of a process for storing part information for a part using an interlocking part history and a carrier configuration and activity history blockchain, according to an illustrative embodiment. The process 600 may be performed in, for example, Figure 1 Parts in the history blockchain network 104 or Figure 3 The part history tracking system 300 is implemented in the part history tracking system 300.

[0080] Process 600 may begin by receiving a part installation notification for a part installed on a vehicle, wherein configuration and activity history information for the vehicle is recorded in a vehicle configuration and activity history blockchain network for the vehicle (operation 602). The part installation notification may identify the part, indicate that the part is installed on the vehicle, and provide other appropriate information related to the installation of the part on the vehicle. The part installation notification may be provided by the vehicle configuration and activity history blockchain network or by another appropriate source.

[0081] Information related to the installation of the part on the carrier may be recorded in a part history blockchain for the part in the part history blockchain network (operation 604). The part history blockchain for the part in the part history blockchain network may then be locked (operation 606) to prevent any additional additions of information for the part from being recorded in the part history blockchain network. A certificate recording information for the carrier on which the part was installed may be sent to the carrier configuration and activity history blockchain network (operation 608).

[0082] The part history blockchain network will remain locked to prevent the addition of information related to the part until a credential is returned indicating that the part has been removed from the carrier in which the part was installed. From this, it can be determined whether the credential was received back from the carrier configuration and activity history blockchain network (operation 610). In response to determining that the credential has been returned, the part history blockchain for the part in the part history blockchain network can be unlocked (operation 612) to allow additional information for the part to be added thereto.

[0083] A part removal notification may be received (operation 614). The part removal notification may include information related to the removal of the part from the carrier. The part removal notification may be provided from a carrier configuration and activity history blockchain network that records information of the carrier from which the part was removed. The information related to the removal of the part from the carrier may be recorded in a part history blockchain for the part in the part history blockchain network (operation 616), with the process terminating thereafter. Thus, the information related to the removal of the part may be the first information related to the part recorded in the part history blockchain network after the part history blockchain network is unlocked at operation 612.

[0084] Go to Figure 7 , depicts a block diagram of a data processing system according to an illustrative embodiment. Data processing system 700 is an example of one possible implementation of a data processing system for performing the functions of an interlocking blockchain as described herein. For example and not limitation, data processing system 700 is a system for implementing Figure 1 An example of one possible implementation of a data processing system for the vehicle configuration and activity history blockchain network 102 and the parts history blockchain network 104 in FIG.

[0085] In this illustrative example, data processing system 700 includes communications fabric 702. Communications fabric 702 provides communications between processor unit 704, memory 706, persistent storage 708, communications unit 710, input / output (I / O) unit 712, and display 714. Memory 706, persistent storage 708, communications unit 710, input / output (I / O) unit 712, and display 714 are examples of resources that may be accessible to processor unit 704 via communications fabric 702.

[0086] Processor unit 704 is used to run instructions for software that may be loaded into memory 706. Processor unit 704 may be a number of processors, a multi-processor core, or some other type of processor, depending on the particular implementation. Further, processor unit 704 may be implemented using a number of heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, processor unit 704 may be a symmetric multi-processor system containing multiple processors of the same type.

[0087] Memory 706 and permanent storage 708 are examples of storage 716. A storage device is any hardware capable of temporarily or permanently storing information such as, for example and without limitation, data, program code in functional form, and / or other suitable information. Storage 716 may also be referred to as a computer-readable storage device in these examples. Memory 706 may be, for example, a random access memory or any other suitable volatile or non-volatile storage device in these examples. Persistent storage 708 may take various forms depending on the specific implementation.

[0088] For example, permanent storage 708 may include one or more components or devices. For example, permanent storage 708 may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or a combination thereof. The medium used by permanent storage 708 may also be removable. For example, a removable hard drive may be used for permanent storage 708.

[0089] Communications unit 710, in these examples, provides communications with other data processing systems or devices. In these examples, communications unit 710 is a network interface card. Communications unit 710 may provide communications using either or both physical and wireless communications links.

[0090] Input / output (I / O) unit 712 allows for input and output of data using other devices that may be connected to data processing system 700. For example, input / output (I / O) unit 712 may provide a connection for user input via a keyboard, a mouse, and / or some other suitable input device. Further, input / output (I / O) unit 712 may send output to a printer. Display 714 provides a mechanism for displaying information to a user.

[0091] Instructions for the operating system, applications, and / or programs may be located in storage devices 716, which are in communication with processor unit 704 via communications fabric 702. In these illustrative examples, the instructions are in functional form on persistent storage 708. These instructions may be loaded into memory 706 for execution by processor unit 704. The processes of the different embodiments may be performed by processor unit 704 using computer implemented instructions, which may be located in a memory, such as memory 706.

[0092] These instructions are referred to as program instructions, program code, computer usable program code, or computer readable program code that can be read and executed by a processor in processor unit 704. The program code in different embodiments may be embodied on different physical or computer readable storage media, such as memory 706 or persistent storage 708.

[0093] Program code 718 is located in a functional form on a selectively removable computer readable medium 720 and can be loaded onto or transferred to data processing system 700 for execution by processor unit 704. Program code 718 and computer readable medium 720 form a computer program product 722 in these examples. In one example, computer readable medium 720 may be computer readable storage medium 724 or computer readable signal medium 726.

[0094] Computer-readable storage media 724 may include, for example, an optical or magnetic disk that is inserted or placed into a drive or other device that is part of persistent storage 708 for transfer to a storage device (such as a hard drive) that is part of persistent storage 708. Computer-readable storage media 724 may also take the form of a persistent storage, such as a hard drive, thumb drive, or flash memory that is connected to data processing system 700. In some cases, computer-readable storage media 724 may not be removable from data processing system 700.

[0095] In these examples, computer-readable storage media 724 is a physical or tangible storage device for storing program code 718, rather than a medium for propagating or transmitting program code 717. Computer-readable storage media 724 is also referred to as a computer-readable tangible storage device or a computer-readable physical storage device. In other words, computer-readable storage media 724 is a medium that a person can touch.

[0096] Alternatively, program code 718 can be transferred to data processing system 700 using computer readable signal media 726. Computer readable signal media 726 can be, for example, a propagated data signal containing program code 718. For example, computer readable signal media 726 can be an electromagnetic signal, an optical signal, and / or any other suitable type of signal. These signals can be transmitted via a communication link (such as a wireless communication link, an optical cable, a coaxial cable, an electric wire, and / or any other suitable type of communication link). In other words, the communication link and / or connection can be physical or wireless in the illustrative examples.

[0097] In some exemplary embodiments, program code 718 may be downloaded to persistent storage 708 from another device or data processing system via a network via computer readable signal media 726 used within data processing system 700. For example, program code stored in a computer readable storage medium in a server data processing system may be downloaded from the server to data processing system 700 via a network. The data processing system providing program code 718 may be a server computer, a client computer, or some other device capable of storing and transmitting program code 718.

[0098] The different components illustrated for data processing system 700 are not meant to provide architectural limitations to the manner in which the different illustrative embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system including other components in addition to or in place of those illustrated for data processing system 700. Figure 7 Other components shown may be different from the illustrative examples shown. Various embodiments may be implemented using any hardware device or system capable of running program code. As an example, data processing system 700 may include organic components integrated with inorganic components, and / or may be composed entirely of organic components excluding humans. For example, a storage device may be composed of an organic semiconductor.

[0099] In another illustrative example, processor unit 704 may take the form of a hardware unit having circuits manufactured or configured for specific use. Such hardware may perform operations without requiring program code loaded into memory from a storage device that would be configured to perform the operations.

[0100] For example, when processor unit 704 takes the form of a hardware unit, processor unit 704 can be a circuit system, an application specific integrated circuit (ASIC), a programmable logic device, or some other suitable type of hardware configured to perform several operations. With respect to programmable logic devices, the device is configured to perform several operations. The device can be reconfigured later or can be permanently configured to perform several operations. Examples of programmable logic devices include, for example, programmable logic arrays, programmable array logic, field programmable logic arrays, field programmable gate arrays, and other suitable hardware devices. With respect to this implementation, program code 718 can be omitted because the processes for different implementations are implemented in hardware units.

[0101] In yet another illustrative example, processor unit 704 may be implemented using a combination of processors found in computers and hardware units. Processor unit 704 may have several hardware units and several processors configured to run program code 718. With respect to the depicted example, some of the processes may be implemented in several hardware units, while other processes may be implemented in several processors.

[0102] In another example, a bus system can be used to implement the communication architecture 702, and the bus system can be composed of one or more buses (such as a system bus or an input / output bus). Of course, any suitable type of architecture that provides data transfer between different components or devices attached to the bus system can be used to implement the bus system.

[0103] In addition, the communication unit 710 may include several devices for sending data, receiving data, or both. The communication unit 710 may be, for example, a modem or a network adapter, two network adapters, or some combination thereof. Further, the memory may be, for example, the memory 706 or a cache, such as the memory found in an interface and storage controller hub that may be present in the communication architecture 702.

[0104] The flow charts and block diagrams described herein illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various illustrative embodiments. In this regard, each block in the flow chart or block diagram may represent a module, a fragment or a part of a code including one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions annotated in the block may occur outside the order annotated in the accompanying drawings. For example, the functions of the two blocks shown in succession may be performed roughly simultaneously, or the functions of the blocks may sometimes be performed in reverse order, depending on the functions involved.

[0105] The description of different illustrative embodiments is presented for the purpose of illustration and description and is not intended to be exhaustive or limited to the embodiments in the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. Further, different illustrative embodiments may provide different features than other desirable embodiments. The selected embodiments are chosen and described in order to best illustrate the principles of the embodiments, the practical application, and to enable others of ordinary skill in the art to understand the various embodiments of the present disclosure, as well as various modifications suitable for the specific use contemplated.

[0106] Further, the present disclosure includes implementations according to the following clauses:

[0107] Clause 1. A method for mounting a part on a carrier, the method comprising the following steps:

[0108] receiving information related to the installation of the part on the carrier,

[0109] wherein information for the part is recorded in a part history blockchain for the part in a part history blockchain network;

[0110] Recording information related to the installation of the part in a vehicle configuration and activity history blockchain for the vehicle in the vehicle configuration and activity history blockchain network; and

[0111] The part history blockchain for the part is locked to prevent information for the part from being added to the part history blockchain for the part as long as the part is mounted on the vehicle.

[0112] Clause 2. The method of clause 1, wherein locking the part history blockchain for the part comprises: sending a part installation notification to a part history blockchain network, wherein the part installation notification identifies the part and indicates that the part is installed on the vehicle, and wherein the part history blockchain network locks the part history blockchain for the part in response to receiving the part installation notification.

[0113] Clause 3. The method of any one of clauses 1 to 2, further comprising the following steps:

[0114] receiving information related to removal of the part from the carrier;

[0115] recording information related to the removal of the part from the vehicle in a vehicle configuration and activity history blockchain for the vehicle in the vehicle configuration and activity history blockchain network; and

[0116] Unlocking the part history blockchain for the part to allow information for the part to be added to the part history blockchain for the part in the part history blockchain network.

[0117] Clause 4. The method of Clause 3 further includes the following steps: sending a part removal notification to the part history blockchain network, wherein the part removal notification identifies the part and indicates that the part is removed from the carrier.

[0118] Clause 5. The method of any one of clauses 1 to 4, further comprising the step of receiving a credential from a part history blockchain network, wherein the part history blockchain for the part will remain locked until the credential is returned to the part history blockchain network.

[0119] Clause 6. The method of clause 5, further comprising the following steps:

[0120] receiving information related to removal of the part from the carrier;

[0121] recording information related to the removal of the part from the vehicle in a vehicle configuration and activity history blockchain for the vehicle in the vehicle configuration and activity history blockchain network; and

[0122] The credential is sent back to the part history blockchain network to unlock the part history blockchain for the part to allow information for the part to be added to the part history blockchain for the part in the part history blockchain network.

[0123] Clause 7. The method of any one of clauses 1 to 6, wherein the vehicle is an aircraft and the part is an aircraft part for the aircraft.

[0124] Clause 8. A method of recording information for a part, the method comprising the steps of:

[0125] receiving, by a part history blockchain network, a part installation notification, wherein the part installation notification identifies the part and indicates that the part is installed on the vehicle, wherein the part history blockchain network includes a part history blockchain for the part configured to record information for the part, and wherein configuration and activity history information for the vehicle is recorded in a vehicle configuration and activity history blockchain for the vehicle in the vehicle configuration and activity history blockchain network; and

[0126] The part history blockchain for the part is locked in response to receiving the part installation notification, thereby preventing information for the part from being added to the part history blockchain for the part as long as the part is installed on the vehicle.

[0127] Clause 9. The method of clause 8, wherein the part installation notification includes information related to the installation of the part on the carrier, and the method further includes the following steps: before locking the part history blockchain for the part, the information related to the installation of the part on the carrier is recorded in the part history blockchain for the part.

[0128] Clause 10. The method of any one of clauses 8 to 9, further comprising the following steps:

[0129] receiving, by the part history blockchain network, a part removal notification, wherein the part removal notification identifies the part and indicates removal of the part from the carrier; and

[0130] In response to receiving the part removal notification, unlocking the part history blockchain for the part to allow information for the part to be added to the part history blockchain for the part in the part history blockchain network.

[0131] Clause 11. The method of clause 10, wherein the part removal notification includes information related to the removal of the part from the carrier, and the method further comprises the following steps: recording the information related to the removal of the part from the carrier in the part history blockchain for the part after unlocking the part history blockchain for the part.

[0132] Clause 12. The method of any one of clauses 8 to 11 further comprises the following steps: sending a credential from the part history blockchain network to the vehicle configuration and activity history blockchain network, wherein the part history blockchain for the part will remain locked until the credential is returned to the part history blockchain network.

[0133] Clause 13. The method of clause 12, further comprising the following steps:

[0134] Reclaiming credentials from the vehicle configuration and activity history blockchain networks by the parts history blockchain network; and

[0135] In response to reclaiming the credential from the vehicle configuration and activity history blockchain network, the part history blockchain for the part is unlocked.

[0136] Clause 14. The method of any one of clauses 8 to 13, wherein the vehicle is an aircraft and the part is an aircraft part for the aircraft.

[0137] Clause 15. An apparatus for recording information for a part, the apparatus comprising a data processing system in a part history blockchain network, the part history blockchain network being configured to:

[0138] receiving a part installation notification, wherein the part installation notification identifies the part and indicates that the part is installed on the vehicle, wherein the part history blockchain network includes a part history blockchain for the part configured to record information for the part, and wherein configuration and activity history information for the vehicle is recorded in a vehicle configuration and activity history blockchain for the vehicle in the vehicle configuration and activity history blockchain network; and

[0139] The part history blockchain for the part is locked in response to receiving the part installation notification, thereby preventing information for the part from being added to the part history blockchain for the part as long as the part is installed on the vehicle.

[0140] Clause 16. The apparatus of clause 15, wherein the part installation notification includes information related to the installation of the part on the carrier, and wherein the data processing system is configured to: record the information related to the installation of the part on the carrier in the part history blockchain for the part before locking the part history blockchain for the part.

[0141] Clause 17. The apparatus of any one of clauses 15 to 16, wherein the data processing system is configured to:

[0142] receiving a part removal notification, wherein the part removal notification includes information related to removal of a part from a carrier, wherein the information related to removal of the part from the carrier identifies the part and indicates removal of the part from the carrier;

[0143] In response to receiving the part removal notification, unlocking the part history blockchain for the part to allow information for the part to be added to the part history blockchain for the part in the part history blockchain network; and

[0144] After unlocking the part history blockchain for the part, information related to the removal of the part from the carrier is recorded in the part history blockchain for the part.

[0145] Clause 18. The apparatus of any of clauses 15 to 17, wherein the data processing system is configured to: send a credential from the part history blockchain network to the vehicle configuration and activity history blockchain network, wherein the part history blockchain for the part will remain locked until the credential is returned to the part history blockchain network.

[0146] Clause 19. The apparatus of clause 18, wherein the data processing system is configured to:

[0147] Reclaim credentials from the vehicle configuration and activity history blockchain network; and

[0148] In response to reclaiming the credential from the vehicle configuration and activity history blockchain network, the part history blockchain for the part is unlocked.

[0149] Clause 20. The apparatus of any one of clauses 15 to 19, wherein the vehicle is an aircraft and the part is an aircraft part for the aircraft.

Claims

1. A method for mounting a part (302) on a carrier (204), the method comprising the following steps: receiving information related to the installation of the part (302) on the carrier (204), wherein the information for the part (302) is recorded in a part history blockchain (322) for the part (302) in a part history blockchain network (306); Recording information related to the installation of the part (302) in a vehicle configuration and activity history blockchain (222) for the vehicle (204) in the vehicle configuration and activity history blockchain network (206); and The part history blockchain (322) for the part (302) is locked, thereby preventing information for the part (302) from being added to the part history blockchain (322) for the part (302) as long as the part (302) is mounted on the carrier (204).

2. The method according to claim 1, wherein: Locking the part history blockchain (322) for the part (302) includes: sending a part installation notification (262) to the part history blockchain network (306), wherein the part installation notification (262) identifies the part (302) and indicates that the part (302) is installed on the carrier (204), and wherein the part history blockchain network (306) locks the part history blockchain (322) for the part (302) in response to receiving the part installation notification (262).

3. The method according to claim 1 or 2, further comprising the following steps: receiving information related to removal of the part (302) from the carrier (204); recording information related to the removal of the part (302) from the carrier (204) in a carrier configuration and activity history blockchain (222) for the carrier (204) in the carrier configuration and activity history blockchain network (206); as well as Unlocking the part history blockchain (322) for the part (302) to allow information for the part (302) to be added to the part history blockchain (322) for the part (302) in the part history blockchain network (306).

4. The method according to claim 3, further comprising the steps of: A part removal notification (266) is sent to the part history blockchain network (306), wherein the part removal notification (266) identifies the part (302) and indicates that the part (302) is removed from the carrier (204).

5. The method according to claim 1 or 2, further comprising the following steps: A credential (264) is received from the part history blockchain network (306), wherein the part history blockchain (322) for the part (302) remains locked until the credential (264) is returned to the part history blockchain network (306).

6. A method of recording information for a part (302), the method comprising the steps of: receiving a part installation notification (362) by a part history blockchain network (306), wherein the part installation notification (362) identifies the part (302) and indicates that the part (302) is installed on the vehicle (204), wherein the part history blockchain network (306) includes a part history blockchain (322) for the part (302) configured to record information for the part (302), and wherein configuration and activity history information for the vehicle (204) is recorded in the vehicle configuration and activity history blockchain (222) for the vehicle (204) in the vehicle configuration and activity history blockchain network (206); and In response to receiving the part installation notification (362), the part history blockchain (322) for the part (302) is locked, thereby preventing information for the part (302) from being added to the part history blockchain (322) for the part (302) as long as the part (302) is installed on the carrier (204).

7. The method according to claim 6, wherein: The part installation notification (362) includes information related to the installation of the part (302) on the carrier (204), and the method further The method comprises the following steps: before locking the part history blockchain (322) for the part (302), recording information related to the installation of the part (302) on the carrier (204) in the part history blockchain (322) for the part (302).

8. The method according to any one of claims 6 to 7, further comprising the following steps: receiving, by the part history blockchain network (306), a part removal notification (366), wherein the part removal notification identifies the part (302) and indicates removal of the part (302) from the carrier (204); and In response to receiving the part removal notification (366), unlocking the part history blockchain (322) for the part (302) to allow information for the part (302) to be added to the part history blockchain (322) for the part (302) in the part history blockchain network (306).

9. The method according to claim 8, wherein: The part removal notification (366) includes information related to the removal of the part (302) from the carrier (204), and the method also includes the following steps: after unlocking the part history blockchain (322) for the part (302), recording the information related to the removal of the part (302) from the carrier (204) in the part history blockchain (322) for the part (302).

10. An apparatus for recording information for a part (302), the apparatus comprising a data processing system (700) in a part history blockchain network (306), the part history blockchain network (306) being configured to: Receiving a part installation notification (362), wherein: The part installation notification (362) identifies the part (302) and indicates that the part (302) is installed on the vehicle (204), wherein the part history blockchain network (306) includes a part history blockchain (322) for the part (302) configured to record information for the part (302), and wherein configuration and activity history information for the vehicle (204) is recorded in the vehicle configuration and activity history blockchain (222) for the vehicle (204) in the vehicle configuration and activity history blockchain network (206); and In response to receiving the part installation notification (362), the part history blockchain (322) for the part (302) is locked, thereby preventing information for the part (302) from being added to the part history blockchain (322) for the part (302) as long as the part (302) is installed on the carrier (204).

Images