DE112020004859T5 - UPDATE MANAGEMENT FOR TRANSPORT SOFTWARE - Google Patents

Abstract

An example operation may include one or more of the following: receiving a software update in a conveyance of a subset of conveyances, validating the software update based on one or more of: a time period in which the software update is deployed, and a number of usages of the software update by the subset of conveyances, propagating the software update based on the validating to another subset of conveyances, wherein the further subset of conveyances is greater than the subset of conveyances.

Description

BACKGROUND

Vehicles or conveyances, such as automobiles, motorcycles, trucks, airplanes, trains, etc., generally meet the transportation needs of passengers and/or goods in a variety of ways. Functions related to conveyances can be identified and used by various computing devices, such as a smartphone or a computer or a tablet.

Software updates for conveyances are generally performed from a central server that pushes the software updates to each individual conveyance client computer. This generally requires a network connection to the cloud. However, extensive use of a WAN to distribute software updates is inefficient and may not be secure. In addition, the software update may not be tested by a sufficiently large number of vehicles to the extent necessary before it is sent through the server. There is no centralized system that can capture and securely and efficiently track software update-related information from millions of vehicles.

Accordingly, there is a need for an assured distribution of software updates for conveyances based on extensive testing by a large number of conveyances. There is also a need for a record of software update related information in shared storage.

EXECUTIVE SUMMARY

An example embodiment may provide a method, comprising one or more of: receiving a software update in a conveyance of a subset of conveyances; validating the software update based on one or more of: a time period in which the software update is deployed and a number of usages of the software update by the subset of conveyances; propagating the software update based on the validating to another subset of conveyances, wherein the further subset of conveyances is greater than the subset of conveyances.

Another exemplary embodiment may provide a method comprising one or more of: sending, by a master vehicle, a first portion of a software update to a vehicle of a first subset of vehicles, sending, by a master vehicle, a second part of the software update to a means of transport of a further subset of means of transport if a first means of transport of the subset of means of transport and a second means of transport of the further subset of means of transport are in the vicinity: causing the first means of transport to carry out the first part of the software update sends to the second conveyance, and causing the second conveyance to send the second portion of the software update to the first conveyance.

Another example embodiment may provide a method comprising one or more of: receiving a software update in a conveyance, performing a first validation of the software update in a first environment, the first environment including a lowest set of potential interactions, and if the first validation succeeds, performing further validation of the software update in a further environment, wherein the further environment includes a greater set of potential interactions than the first environment.

Another exemplary embodiment may provide a system comprising a processor and memory, wherein the processor of a vehicle of a subset of vehicles is configured to perform one or more of: receiving a software update; validating the software update based on one or more of: a time period in which the software update is deployed and a number of usages of the software update by the subset of conveyances; propagating the software update based on the validating to another subset of conveyances, wherein the further subset of conveyances is greater than the subset of conveyances.

Another example embodiment may provide a system comprising a processor and memory, wherein the processor of a master vehicle is configured to perform one or more of: sending a first portion of a software update to a vehicle of a first subset of conveyances, sending a second part of the software update to a conveyance of a further subset of conveyances if a first conveyance of the subset of conveyances and a second conveyance of the further subset of Proximity conveyances are: causing the first conveyance to send the first part of the software update to the second conveyance, and causing the second conveyance to send the second part of the software update to the first conveyance.

Another example embodiment may provide a system comprising a processor and memory, the processor configured to perform one or more of: receiving a software update in a conveyance, performing an initial validation of the software update in a vehicle first environment, wherein the first environment includes a lowest set of potential interactions, and if the first validation succeeds, performing further validation of the software update in a further environment, wherein the further environment includes a greater set of potential interactions than the first environment .

Another exemplary embodiment provides a non-transitory computer-readable medium comprising instructions that, when read by a processor of a vehicle of a subset of vehicles, cause the processor to perform one or more of the following: receive a software update , validating the software update based on one or more of: a time period in which the software update is used and a number of times the software update is used by the subset of conveyances; propagating the software update based on the validating to another subset of conveyances, wherein the further subset of conveyances is greater than the subset of conveyances.

Another exemplary embodiment provides a non-transitory computer-readable medium comprising instructions that, when read by a processor, cause the processor to perform one or more of the following: send a first portion of a software update to a conveyance of a first subset of conveyances, sending a second part of the software update to a conveyance of a further subset of conveyances when a first conveyance of the subset of conveyances and a second conveyance of the further subset of conveyances are nearby: causing the first conveyance send the first part of the software update to the second conveyance, and cause the second conveyance to send the second part of the software update to the first conveyance.

Another exemplary embodiment provides a non-transitory computer-readable medium comprising instructions that, when read by a processor, cause the processor to perform one or more of: receiving a software update, performing an initial validation of the software - updates in a first environment, the first environment comprising a lowest set of potential interactions, and if the first validation is successful, performing further validation of the software update in a further environment, the further environment comprising a larger set of potential interactions as the first environment.

character list

• 1A 12 illustrates a conveyance network diagram in accordance with exemplary embodiments.
• 1B 12 illustrates an example network diagram that includes a conveyance node, according to example embodiments.
• 1C 12 illustrates another example network diagram that includes a conveyance node, according to example embodiments.
• 1D 12 illustrates another example network diagram that includes a conveyance node, according to example embodiments.
• 2A 1 illustrates a blockchain architecture layout according to example embodiments.
• 2 B FIG. 11 illustrates another blockchain configuration, according to example embodiments.
• 2C 10 illustrates a blockchain configuration for storing blockchain transaction data, according to example embodiments.
• 3A Figure 12 illustrates a flow chart according to example embodiments.
• 3B Figure 12 illustrates another flow chart according to example embodiments.
• 3C Figure 12 illustrates another flow chart according to example embodiments.
• 3D Figure 12 illustrates another flow chart according to example embodiments.
• 3E Figure 12 illustrates another flow chart according to example embodiments.
• 3F FIG. 11 illustrates another flow chart according to example embodiments.
• 4A 12 illustrates an example blockchain vehicle configuration for managing blockchain transactions associated with a vehicle, according to example embodiments.
• 4B 12 illustrates another example blockchain vehicle configuration for managing blockchain transactions between a service center and a vehicle, according to example embodiments.
• 4C FIG. 12 illustrates another example blockchain vehicle configuration for managing blockchain transactions conducted between different vehicles, according to example embodiments.
• 5 12 illustrates example data blocks according to example embodiments.
• 6 illustrates an example system that supports one or more of the example implementations.

DETAILED DESCRIPTION

It should be understood that the present components, as generally described and illustrated in the figures herein, can be arranged and configured in a wide variety of different configurations. Therefore, the following detailed description of the embodiments of at least one method, apparatus, non-transitory computer-readable medium, and system as illustrated in the accompanying figures is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments.

Present features, structures, or characteristics as described in this specification may be combined in any suitable manner in one or more embodiments. For example, use of the phrase "exemplary implementations," "some embodiments," or other similar language throughout the specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment , may be included in at least one embodiment. As such, appearances in this specification of the phrases "example embodiments," "in some embodiments," "in other embodiments," or other similar language are not necessarily all referring to the same group of embodiments, and the feature, structure, or characteristic described may refer to any appropriate one Way be combined in one or more embodiments. In the diagrams, each connection between elements may allow for one-way and/or two-way communication, even if the connection shown is represented by a one-way or a two-way arrow. In the present application, a conveyance can be one or more of automobiles, trucks, motorcycles, scooters, bicycles, boats, recreational vehicles, airplanes, and any object that can be used to move people and/or goods from one location to another.

Furthermore, while the term "message" can be used in the description of embodiments, the application can be applied to many types of network data, such as a packet, a frame, a datagram, etc. The term "message" also includes packet , frame, datagram and any equivalent thereof. Furthermore, while particular types of messages and signaling may be illustrated in example embodiments, they are not limited to any particular type of message and the application is not limited to any particular type of signaling.

Example embodiments provide methods, systems, components, non-transitory computer-readable media, devices, and/or networks that provide at least one of the following: a conveyance (also referred to herein as a vehicle), a data collection system, a data monitoring system, a verification system authorization system, and a vehicle data distribution system. The vehicle status condition data, received in the form of communication update messages, such as wireless data network communication and/or wired communication messages, may be received and processed to identify vehicle/conveyance status conditions and provide feedback regarding condition changes of a conveyance. In one example, a user profile can be applied to a particular conveyance/vehicle to indicate a current vehicle event, service stops Authorize gas stations and subsequent vehicle rental services.

Within the communications infrastructure, a decentralized database is a distributed storage system that includes multiple nodes that communicate with each other. A blockchain is an example of a decentralized database that includes an immutable, addition-only data structure (i.e., a distributed ledger) that is set up to maintain records between untrusted parties. The untrusted parties are referred to herein as peers, nodes or peer-nodes. Each peer maintains a copy of the database records, and no single peer can modify the database records without consensus being reached among the distributed peers. For example, the peers can run a consensus protocol to validate blockchain memory entries, group the memory entries into blocks, and build a hash chain across the blocks. This process forms the ledger by ordering the memory entries as necessary to ensure consistency. Anyone can participate in a public or permissionless blockchain without a specific identity. Public blockchains can include cryptocurrencies and use consensus based on various protocols such as Proof of Work (PoW). On the other hand, a permission-based blockchain database provides a system that can secure interactions between a group of entities that share a common goal but do not or cannot fully trust each other, such as businesses that hold funds, goods, information, and the like exchange. The present application can function in a permission-based and/or a permissionless blockchain environment.

“Smart contracts” are trusted distributed applications that synergistically leverage tamper-resistant properties of the shared or distributed ledger database (that is, the ledger may be in the form of a blockchain) and an underlying agreement between member nodes, which is known as a “Endorsement” or “Endorsement Policy”. In general, blockchain entries are "endorsed" before being committed to the blockchain, while entries that are not endorsed are ignored. A typical endorsement policy allows the executable code of a smart contract to specify endorsers for an entry in the form of a set of peer nodes required for the endorsement function. When a client sends the entry to the peers specified in the endorsement policy, the entry is run to validate the entry. After validation, entries enter an ordering phase in which a consensus protocol is used to create an ordered sequence of endorsed entries grouped into blocks.

Nodes are the communication units of the blockchain system. A "node" can perform a logical function in the sense that multiple nodes of different types can operate on the same physical server. Nodes are grouped into trust domains and are associated with logical entities that control them in various ways. Nodes can be of various types, such as a client or template client node that submits an entry request to an advocate (e.g., peer) and broadcasts entry proposals to an ordering service (e.g., ordering node). Another type of node is a peer node that can receive entries submitted by a client, submit the entries, and maintain a status and copy of the ledger of blockchain entries. Peers can also have an advocate role, although this is not a requirement. A stewardship node or steward is a node that performs the communications service for all nodes and that implements a delivery guarantee, such as broadcasting to each of the peer nodes in the system when it submits entries and modifies a world state of the blockchains that another Name for the initial blockchain entry, which typically includes control and setup information.

A ledger is a sequenced, tamper-proof record of all state transitions in a blockchain. State transitions may result from calls (ie, entries) of smart contract executable code communicated by involved parties (e.g., client nodes, ordering nodes, advocate nodes, peer nodes, etc.). An entry can result in a set of asset key-value pairs being passed to the ledger as one or more operands, such as creates, updates, deletes, etc. The ledger comprises a blockchain (also known as a chain) used to store an immutable, sequenced record in blocks. The ledger also includes a state database that maintains a current state of the blockchain. Usually there is one ledger per channel. Each peer node maintains a copy of the ledger for each channel to which it belongs.

A chain is a log of entries structured as hashed blocks, and each block comprises a sequence of N entries, where N min at least one is. The block header includes a hash of the block's entries and a hash of the previous block's header. In this way, all entries in the ledger can be sequenced and cryptographically linked. Accordingly, it is not possible to manipulate the ledger's data without breaking the hash links. A hash of a recently added blockchain block represents every entry in the chain that came before it, which can ensure that all peer nodes are in a consistent and trusted state. The chain can be stored in a peer node file system (i.e. local, attached storage, cloud, etc.), efficiently supporting the append-only nature of the blockchain workload additions allowed).

The current state of the immutable ledger represents the most recent values for all keys contained in the chain entry log. Because the current state represents the most recent key values known to a channel, it is sometimes referred to as the world state. Calls to smart contract executable code execute entries based on the current state data of the ledger. In order to make these interactions with executable code of a smart contract efficient, the most recent values of the keys can be stored in a state database. The state database can simply be an indexed view of the chain's entry log, so it can be regenerated from the chain at any time. The state database can be restored automatically (or generated on demand) when the peer node starts up and before any entries are accepted.

A blockchain differs from a traditional database in that the blockchain is not a central store, but rather a decentralized, immutable, and secure store where the nodes must all participate in changes to the records in the store. Some properties inherent in the blockchain that help to implement the blockchain include, but are not limited to, an immutable ledger, smart contracts, security, privacy, decentralization, consensus, advocacy, accessibility, and the like.

Example embodiments provide a way to provide a vehicle service to a particular vehicle and/or a requesting user associated with a user profile applied to the vehicle. For example, a user may be the owner of a vehicle or the operator of a vehicle owned by another party. The Vehicle may require service at certain intervals and service requirements may require authorization before the Services can be accessed. Additionally, service centers may offer services to nearby vehicles based on the vehicle's current route plan and a relative level of service needs (e.g., immediate, heavy, medium, light, etc.). Vehicle needs may be monitored via one or more sensors that report the sensor data to a central controller computing device in the vehicle, which in turn is forwarded to a management server for review and action.

A sensor may be located in one or more of an interior of the vehicle, an exterior of the vehicle, a solid object outside the vehicle, and another vehicle proximate to the vehicle. The sensor may also be associated with vehicle speed, vehicle braking, vehicle acceleration, fuel level, service requirements, vehicle gear shifting, vehicle steering, and the like. A device, for example a mobile device, is also conceivable as a “sensor”. In addition, sensor information may be used to determine whether the vehicle is operating safely and whether the vehicle operator has induced unexpected vehicle conditions, such as during the vehicle boarding phase. Vehicle information collected before, during and/or after operation of a vehicle may be identified and stored in a shared/distributed ledger transaction; this can be generated by a permitting consortium, and thus in a “decentralized” way, such as via a blockchain stakeholder group, and submitted to the immutable ledger. Any interested party (i.e. company, government agency, etc.) may wish to restrict disclosure of private information, which is why the blockchain and its immutability can restrict disclosure and manage permissions for each concrete user vehicle profile. A smart contract can be used to provide compensation, quantify a user profile score/ranking/review, apply vehicle event permits, determine when service is needed, identify a collision and/or degradation event, identify a safety-related event to identify parties to the event and distribute to registered entities seeking access to such vehicle event data. Also, the results can be identified and the necessary information can be shared between the registered companies and/or individuals based on a “consensus” approach linked to the blockchain. Such an approach could not be implemented in a traditional centralized database.

Every autonomous driving system is based on an entire software package and an array of sensors. Machine learning, lidar projectors, radar and ultrasonic sensors all work together to create a living map of the world for a self-driving car to navigate. Most companies entering the race to full autonomy rely on the same technological foundations of lidar + radar + cameras + ultrasound, with a few notable exceptions.

In another embodiment, GPS, maps, and other cameras and sensors are used in an autonomous vehicle without lidar, since lidar is often considered expensive and unnecessary. Researchers have found that stereo cameras are a cost-effective alternative to more expensive lidar functionality.

The present application, in certain embodiments, includes authorizing a vehicle for a service via an automated and rapid authentication regime. For example, approaching a charging station or fuel pump can be performed by a vehicle operator and authorization to receive charge or fuel can be done without delays, provided authorization is received by the fuel station. A vehicle may provide a communication signal that serves as an identification of a vehicle having a currently active profile associated with an account authorized to accept vehicle service that may later be paid for through a fee. Additional measures can be taken to perform further authentication. For example, another identifier can be wirelessly sent from the user's device to the service center to replace or supplement the initial authorization process between the conveyance and the service center with an additional authorization process.

Shared and received data can be stored in a database that manages data in a single database (e.g., a database server) and generally in a single dedicated location. This location is often a central computer, such as a desktop central processing unit (CPU), server CPU, or mainframe. Information stored in a centralized database can typically be accessed from several different points. A centralized database is easy to manage, maintain and control, especially for security purposes, as it is in a single location. Within a centralized database, data redundancy is minimized because a single location for all data also means that any given record has only a single primary record.

According to the exemplary embodiments, the distribution of a software update to vehicles is provided without using WAN technology. An exemplary embodiment allows the software update to be propagated through a first set of conveyances only after a test has been performed. The test can be run over a period of time or over a number of executions of the software update code. If a test of the software fails, the conveyances are alerted and the software in the conveyances can be rolled back to a previous software version.

In another embodiment, a master conveyance system may provide additional security in propagating software updates to vehicles by splitting the software update into at least two parts and sending the parts of the software update at different times and/or from different sources . In an exemplary embodiment, the software update may be sent first from a master conveyance system. The exemplary embodiment may provide decentralized distribution of the software updates with authentication of the update via blockchain technology.

According to the exemplary embodiments, a master conveyance can be determined based on the characteristics of the conveyance (for example, the security level of the conveyance, the age of the conveyance, the hardware in the conveyance that is set up to run the software properly, the state of the conveyance, the characteristics of the users/occupants of the conveyance, the use of functional features in or in connection with the conveyance) determine which part of the software update which means of transport is sent. The update may be provided based on the likely usage of the update, for example which means of transport is better able to test/use the software update. In an example, a vehicle 1 may receive a first part of the update (ABC) and a vehicle 2 another part of the update (ABC') from the same master conveyance. The software update can be divided into more than 2 parts. For example, some conveyances may receive 2 pieces, some 3 pieces, and some n pieces. The master conveyance may have a higher security level than the subset of conveyances and the further subset of conveyances. Any problems with the software update can be reported back to the master vehicle (which can report them back to a central server). If a problem occurs with any part or with the composite first and second parts of the update, the master vehicle can be brought into close proximity to the problematic vehicle and can monitor the vehicle to determine and solve the problem.

In another exemplary embodiment, after the software updates are received, assembled, and implemented, the vehicle continues to operate with the old software version and intermittently uses the new updated software in potentially least problematic situations. For example, if the update is to update braking software, the vehicle may use the updated software when the driving environment is very light traffic (and no pedestrians and/or objects are present). Once the updated software is validated in that driving environment, the vehicle may use the updated software in another potentially problematic driving environment (e.g., with more traffic, pedestrians, and/or objects). According to the exemplary embodiment, the vehicle driver may not be aware of the functionality of the software update management application. The vehicle system can gradually test the software updates in different environments and can revert to the previous version of the software if necessary.

In another embodiment, the master conveyance determines based on the characteristics of the conveyance (e.g., the security level of the conveyance, the age of the conveyance, the hardware in the conveyance that is set up to run the software properly, the state of the conveyance, the characteristics of the user/occupants of the means of transport, the use of functional features in or in connection with the means of transport), which part is sent to which means of transport. The update may be based on the likely usage of the update, for example which means of transport is better able to test/use the software.

In another embodiment, different vehicles may assemble the pieces of software based on the time or date of their submission or based on characteristics of the vehicle and/or the software and/or the user. For example, vehicle 1 may receive a first part (ABC) and the same next transmission to vehicle 2 may receive a first part (ABC') from the same master conveyance (ie the first part may be different).

In another embodiment, the software update can be divided into more than 2 parts. Some conveyances could get 2 parts, some 3, some n.

In a further embodiment, the master carriage comprises one or more of a security level higher than the subset of carriages and the further subset of carriages, the first part of the software update and the second part of the software update.

In another embodiment, any problems with the software are reported back to the master vehicle (which can report them back to a central server).

In a further embodiment, when a problem occurs with a part of the update or with the assembled first and second parts, the master vehicle can be located in a vicinity of the problem vehicle and monitor and access the problem.

1A 12 illustrates a conveyance network diagram 100 in accordance with the exemplary embodiments. According to an exemplary embodiment, the processor 104' of a conveyance of a subset of conveyances (e.g. 105) may be configured to receive a software update. The software update may be provided by a master conveyance node (e.g., 102). The processor 104' may validate the software update based on a time period in which the software update is provided by the carrier agent (e.g. 105) is used. In one example, the processor 104' may validate the software update based on a number of usages of the software update by the subset of conveyances (e.g., 105). The processor 104' may propagate the software update to another subset of conveyances (e.g., 107) based on the validating. The subset of means of transport 107 is larger than the subset of means of transport 105.

According to another exemplary embodiment, the processor 104 of a master conveyance 102 may be configured to send a first part of a software update to a conveyance of a first subset of conveyances 105 . The processor 104 of the master carriage 102 may send a second portion of the software update to a carriage of another subset of carriages 107 . Then, when a first conveyance of the subset of conveyances 105 and a second conveyance of the further subset of conveyances 107 are in proximity, the processor 104 can send a command to the first conveyance 105, the first part of the software update to the second Transport 107 to send. The processor 104 can then send a command to the second conveyance to send the second part of the software update to the first conveyance 105 . In this way, the processors 104' and 104'' of the respective conveyances 105 and 107 can compile a complete software update.

According to another exemplary embodiment, the processor 104' (or 104'') may be configured to receive a software update (e.g., from the master conveyance node 102) and perform a first validation of the software update in a first environment The first environment may include a minimal amount of potential interactions (minimal traffic, no pedestrians, normal weather conditions, etc.). Then the processor 104' (or 104") may perform another validation of the software update if the first validation is in another environment is successful. The wider environment may include a greater amount of potential interactions than the first environment (e.g., more traffic, pedestrians, difficult weather conditions, etc.).

1B illustrates a network diagram for managing software updates. Referring to 1B the network diagram 111 comprises a subset of conveyance nodes 102 connected to another subset of conveyance nodes 105 via a blockchain network 106 . Conveyance nodes 102 and 105 may represent conveyances/vehicles. The blockchain network 106 may include a ledger 108 for storing data, such as software update-related data, including timestamps of the software updates. The conveyance node 102 may be connected to other subsets of conveyance nodes (not shown).

Although this example only details a single conveyance node 102, multiple such nodes may be connected to the blockchain 106 as well. It is understood that the carriage node 102 may include additional components and that some of the components described herein may be omitted and/or modified without departing from the scope of the carriage node 102 disclosed herein. Conveyor node 102 may comprise a computing device or server computer, or the like, and may include a processor 104, which may be a semiconductor-based microprocessor, a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and/or may be another hardware device. Although only a single processor 104 is shown, it should be understood that the conveyance node 102 may include multiple processors, multiple cores, or the like without departing from the scope of the conveyance node system 102 .

Conveyance node 102 may also include a non-transitory computer-readable medium 112 on which machine-readable instructions executable by processor 104 may be stored. Examples of machine-readable instructions are shown as 114-118 and are discussed in more detail below. Examples of non-transitory computer-readable medium 112 may be an electronic, magnetic, optical, or other physical storage device that includes or stores executable instructions. For example, the non-transitory computer-readable medium 112 may be random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a hard disk, an optical disk, or another type of storage device.

The processor 104 can execute the machine-readable instructions 114 to receive a software update in the vehicle 104 . Each of the conveyances 102 and 105 can function as a network peer (i.e. node) in a Blockchain 106 serve. As discussed above, the blockchain ledger 108 can store software update related transactions. The blockchain 106 network may be configured to use one or more smart contracts residing on the conveyances (ie, nodes) 102 that may manage transactions for other participating conveyance nodes 105 . The conveyance node 102 may transmit the information to the blockchain 106 for storage in the ledger 108 .

The processor 104 can execute the machine-readable instructions 116 to validate the software update. The software update may be validated based on a time period during which the software update is used and a number of uses of the software update by the conveyance subset 102 . The processor 104 may execute the machine-readable instructions 118 to propagate the software update to another subset of conveyances (e.g., 105) based on the validation. The further subset of means of transport 105 is larger than the subset of means of transport 102.

1C Figure 12 illustrates a network diagram for managing conveyance software updates. Referring to 1C For example, network diagram 121 includes a conveyance node 102 serving as a master conveyance node and connected to other conveyance nodes 105 and 107 via a blockchain network 106 having a ledger 108 for storing software update-related transactions 110. The conveyance nodes 102, 105 and 107 can also serve as blockchain 106 peers. Although this example only details a single master conveyance node 102, multiple such nodes may be connected to the blockchain 106 as well. It is understood that the master carriage node 102 may include additional components and that some of the components described herein may be omitted and/or modified without departing from the scope of the master carriage node 102 disclosed herein. The master haulage node 102 may comprise a computing device or server computer, or the like, and may include a processor 104, which may be a semiconductor-based microprocessor, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and /or other hardware device. Although only a single processor 104 is shown, it should be understood that the master shipping node 102 may include multiple processors, multiple cores, or the like without departing from the scope of the master shipping node 102 .

Master conveyance node 102 may also include a non-transitory computer-readable medium 112' on which machine-readable instructions executable by processor 104 may be stored. Examples of machine-readable instructions are shown as 113-117 and are discussed in more detail below. Examples of the non-transitory computer-readable medium 112' may be an electronic, magnetic, optical, or other physical storage device that includes or stores executable instructions. For example, the non-transitory computer-readable medium 112' may be random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), hard disk, optical disk, or other type of storage device.

The processor 104 can execute the machine-readable instructions 112 ′ to send a first part of a software update to a conveyance of a first subset of conveyances 113 . Blockchain 106 may be configured to use one or more smart contracts that manage transactions for multiple participating nodes (e.g., 105 and 107). The master conveyance node 102 can transmit software update related information to the blockchain 106 and this transaction can be stored in the ledger 108 .

Processor 104 may execute machine-readable instructions 115 to send a second portion of the software update to a vehicle of another subset of vehicles (e.g., 107). Processor 104 may execute machine-readable instructions 117 to, when a first conveyance of subset of conveyances 105 and a second conveyance of another subset of conveyances 107 are in proximity: cause the first conveyance to apply the first portion of the software update send the second conveyance and cause the second conveyance 107 to send the second part of the software update to the first conveyance 105 .

1D Figure 12 illustrates a network diagram for managing conveyance software updates. Referring to 1D For example, network diagram 130 includes a conveyance node 102 (e.g., a vehicle) connected to other conveyance nodes 105 via a blockchain network 106 that includes a ledger 108 for storing software validation data and Transactions 110 has. Conveyance nodes 102 and 105 may also serve as blockchain 106 peers. Although this example only details a single conveyance node 102, multiple such nodes may be connected to the blockchain 106 as well. It is understood that the carriage node 102 may include additional components and that some of the components described herein may be omitted and/or modified without departing from the scope of the carriage node 102 disclosed herein. Conveyor node 102 may comprise a computing device or server computer, or the like, and may include a processor 104, which may be a semiconductor-based microprocessor, a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and/or may be another hardware device. Although only a single processor 104 is shown, it should be understood that the conveyance node 102 may include multiple processors, multiple cores, or the like without departing from the scope of the conveyance node 102 .

Conveyor node 102 may also include a non-transitory computer-readable medium 112'' on which may be stored machine-readable instructions executable by processor 104. Examples of machine-readable instructions are shown as 132-136 and are discussed in further detail below. Examples for the non-transitory computer-readable medium 112" may be an electronic, magnetic, optical, or other physical storage device that includes or stores executable instructions. For example, the non-transitory computer-readable medium 112'' may be random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), hard disk, optical disk, or other type of storage device.

The processor 104 can execute the machine-readable instructions 132 to receive a software update in the vehicle 102 . Blockchain 106 may be configured to use one or more smart contracts that manage transactions for multiple participating conveyance nodes 105 . The conveyance 102 can transmit software update related validation information to the blockchain 106 and this transaction can be stored in the ledger 108 .

The processor 104 may execute the machine-readable instructions 134 to perform a first validation of the software update in a first environment, the first environment including a lowest amount of potential interactions. The processor 104 may execute the machine-readable instructions 136 to perform further validation of the software update in another environment if the first validation is successful. The wider environment may include a greater amount of potential interactions than the first environment.

2A FIG. 2 illustrates a blockchain architecture design 200 according to example embodiments. Referring to 2A For example, the blockchain architecture 200 may include certain blockchain elements, for example a group of blockchain participating nodes 202-206, as part of a blockchain group 210. In an exemplary embodiment, a permitted blockchain is not accessible to all parties, but only to those parties with permitted access to the blockchain data. The blockchain nodes engage in a number of activities such as adding blockchain entries and the validation (consensus) process. One or more of the blockchain nodes may endorse entries based on an endorsement policy and provide an ordering service for all blockchain nodes. A blockchain node can initiate a blockchain action (such as authentication) and attempt to write to an immutable blockchain ledger that is stored on the blockchain, a copy of which can also be stored on the underlying physical infrastructure.

The blockchain transactions 220 are stored in the memory of computers as the transactions are received and approved through the consensus model dictated by the nodes of the participants. Approved transactions 226 are stored in current blocks of the blockchain and committed to the blockchain by a provisioning method that includes hashing the data contents of the transactions in a current block and reverting to a previous hash of a previous block. One or more smart contracts 230 may exist within the blockchain, defining the terms of transaction agreements and actions embodied in executable smart contract application code 232, such as registered recipients, vehicle characteristics, requirements, permissions, sensor thresholds, etc. The code may be configured to identify whether requesting entities are registered to receive vehicle services, which service features they may/must receive according to their profile status, and whether their actions at subsequent events are to be monitored. For example, when a service event occurs and a user rides in the conveyance, monitoring of the sensor data can be triggered and a determination can be made that a particular parameter, such as a vehicle's state of charge, has been above or below for a specified period of time is a certain threshold. The result may then be a change in the current state, requiring an alert to be sent to the managing party (i.e. vehicle owner, vehicle operator, server, etc.) in order for the service to be recognized and stored for reference can. The collected vehicle sensor data may be based on types of sensor data used to collect information about the status of the vehicle. The sensor data can also be the basis for vehicle event data 234, such as locations to reach, average speed, maximum speed, acceleration rates, whether there have been collisions, whether the expected route was taken, what the next destination is, whether safety measures are in place, whether the vehicle has enough charge/fuel, etc. All of this information can form the basis of the smart contract 230 terms, which are then stored in a blockchain. For example, the sensor thresholds stored in the smart contract can be used as a basis for determining whether a detected service is necessary and when and where the service should be performed.

2 B 12 illustrates a shared ledger design according to example embodiments. Referring to 2 B example blockchain logic 250 includes a blockchain application interface 252 as an API or plug-in application that interfaces with the computing device and execution platform for a particular transaction. The blockchain embodiment 250 may include one or more applications that interface with application programming interfaces (APIs) to access and execute stored program/application code (e.g., executable code for smart contracts, smart contracts, etc.) and implemented in accordance with can be created in a customization desired by participants and can maintain their own state, control their own assets and receive external information. This can be used as one entry and installed on all blockchain nodes by adding it to the distributed ledger.

The smart contract application code 254 forms a basis for the blockchain transactions by generating application code which, when executed, causes the terms and conditions of the transaction to become active. The smart contract 230, when executed, causes certain authorized transactions 226 to be generated, which are then forwarded to the blockchain platform 262. The platform includes security/authorization 268, computing devices that perform transaction management 266, and a storage section 264 as a store that stores transactions and smart contracts on the blockchain.

The blockchain platform may include various layers of blockchain data, services (e.g., cryptographic trust services, virtual execution environment, etc.), and underlying physical computing infrastructure used to receive and store new entries and provide access to validators looking for data entries want to access can be used. The blockchain can offer an interface that allows access to the virtual execution environment required for processing the program code and using the physical infrastructure. Cryptographic trust services can be used to verify entries such as asset exchange entries and to protect the privacy of information.

The blockchain architecture design 2A and 2 B may process and execute program/application code via one or more interfaces and services provided by the blockchain platform. As a non-limiting example, smart contracts may be created to execute reminders, updates, and/or other notifications , which are subject to changes, updates, etc. The smart contracts themselves can be used to identify rules associated with authorization and access requirements and usage of the ledger. For example, the information may include a new entry that may be processed by one or more processing units (e.g., processors, virtual machines, etc.) included in the blockchain layer. The outcome may include a decision to reject or approve the new entry based on the criteria defined in the smart contract and/or consensus of the peers. The physical infrastructure can be used to retrieve any of the data or information described herein.

Within the executable code of a smart contract, a smart contract created via a non-specific application and programming language and then written to a block in the blockchain. The smart contract may include executable code that is registered, stored, and/or replicated with a blockchain (e.g., a distributed network of blockchain peers). An entry is an execution of smart contract code that may be executed in response to the satisfaction of conditions associated with the smart contract. Execution of the smart contract may trigger one or more trusted modifications of a state of a blockchain digital ledger. The blockchain ledger modifications caused by the execution of the smart contract can be automatically replicated throughout the distributed network of blockchain peers through one or more consensus protocols.

The smart contract can write data to the blockchain in the format of key-value pairs. In addition, smart contract code can read the values stored in a blockchain and use them in application operations. Smart contract code can write the output of various logic operations to the blockchain. The code can be used to create a temporary data structure in a virtual machine or other computing platform. Data written to the blockchain may be public and/or may be encrypted and kept private. The temporary data used/generated by the smart contract is kept in memory by the provided execution environment and then deleted once the data needed for the blockchain has been identified.

Executable smart contract code may include smart contract code interpretation with additional features. As described herein, the smart contract executable code may be program code used on a computer network where it is executed and validated by chain validators together during a consensus process. The smart contract executable code receives a hash and retrieves from the blockchain a hash associated with the data template created using a previously stored feature extractor. If the hash of the hashed identifier and the hash created from the stored identifier template data match, then the smart contract executable code sends an authorization key to the requested service. The smart contract executable code can write to the blockchain data associated with the cryptographic details.

2C 10 illustrates a blockchain configuration for storing blockchain transaction data, according to example embodiments. Referring to 2C For example, the example embodiment 270 provides for the vehicle 272 , the user device 274 , and a server 276 to share information with a distributed ledger (ie, the blockchain) 278 . The server may represent a service provider entity querying a vehicle service provider to share user profile rating information if a known and established user profile attempts to rent a vehicle with a specified rated profile. Server 276 may receive and process data related to a vehicle's service requirements. When the service events occur, such as when the vehicle sensor data indicates a need for fuel/charging, maintenance service, etc., a smart contract can be used to invoke rules, thresholds, sensor information collection, etc. that are used can be used to invoke the vehicle service event. The blockchain transaction data 280 is stored for each transaction, such as the access event, subsequent updates to a vehicle's service status, event updates, etc. The transactions may include: the parties, the requirements (e.g., age 18, eligible candidate, valid driver's license, etc.), compensation levels, distance driven during the event, registered recipients who are allowed to access the event and host a vehicle service, rights/permissions granted, sensor data retrieved during the vehicle event process, details of the next service event to log and identify a vehicle's health status, and thresholds used to determine whether the service event has completed and whether the vehicle's health status has changed.

3A FIG. 3 illustrates a flow chart 300 according to example embodiments. Referring to 3A For example, an example method may be performed by conveyance node 102 (see FIG 1B) . It is understood that the in 3A The method 300 shown may include additional operations and that some of the operations described therein may be omitted and/or modified without departing from the scope of the method 300. The description of the method 300 is also made with reference to the features that are 1B are shown for illustrative purposes. Especially processor 104 of conveyance node 102 may perform some or all of the operations included in method 300.

In relation to 3A At block 302, the processor 104 may receive a software update in the conveyance. At block 304, the processor 104 may validate the software update based on one or more of: a period of time that the software update is deployed and a number of usages of the software update by the conveyance subset. At block 306, the processor 104 may propagate the software update to another subset of conveyances based on the validation. The further subset of the means of transport can be larger than the subset of the means of transport.

3B 3 illustrates a flow chart 320 of an example method according to example embodiments. Referring to 3B the method 320 may also include one or more of the following steps. At block 322, processor 104 may propagate the software update to a set of all remaining conveyances, where the set of all remaining conveyances is greater than the further subset of conveyances. The subset of conveyances, the further subset of conveyances, and the set of all remaining conveyances are based on one or more of the following: existing software, existing hardware, a geographic location, an ambient temperature, a conveyance brand, a conveyance model, a conveyance condition, a road condition, and a means of transport destination.

At block 324, if a negative result is determined based on the validation, the processor 104 may perform one or more of the following: changing one or more of the subset of conveyances, the further subset of conveyances, and the set of all remaining conveyances and resetting one or more of the subset of conveyances, the further subset of conveyances and the set of all remaining conveyances to one or more of an original software version and a previous software update. At block 326, the processor 104 may use the software update for: a first period of time by the subset of conveyances and a second period of time by the another subset of conveyances, the first period of time being greater than the second period of time. The subset of conveyances may belong to a blockchain network. At block 328, the processor 104 may execute a blockchain network smart contract to validate the software update and propagate the software update through multiple of the vehicles.

3C Figure 3 illustrates a flow chart 330 according to example embodiments. Referring to 3C For example, an example method may be performed by the master conveyance node 102 (see FIG 1C ). It is understood that the in 3C The method 330 shown may include additional operations and that some of the operations described therein may be omitted and/or modified without departing from the scope of the method 330. Method 330 is also described with reference to the features contained in 1C are shown for illustrative purposes. In particular, processor 104 of master conveyance node 102 may perform some or all of the operations included in method 330 .

In relation to 3C For example, in block 333 processor 104 may send a first portion of a software update to a vehicle of a first subset of vehicles. At block 335, processor 104 may send a second portion of the software update to a vehicle of another subset of vehicles. At block 337, if a first carriage of the subset of carriages and a second carriage of the further subset of carriages are in proximity, the processor 104 may cause the first carriage to send the first portion of the software update to the second carriage, and cause the second conveyance to send the second portion of the software update to the first conveyance.

3D 3 illustrates a flow chart 340 of an example method according to example embodiments. Referring to 3D the method 340 may also include one or more of the following steps. At block 342, the processor 104 may determine the first portion and the second portion of the software update prior to transmission to the subset of conveyances and the further subset of conveyances. At block 344, processor 104 may direct the master conveyance to a geographic area if the subset of conveyances and the further subset of conveyances do not receive one or more of the first portion and second portion of the software update and do not receive one or more of the run the first part and the second part of the software update.

At block 346, the processor 104 may move the first conveyance to a proximity of the second conveyance if a period of time has elapsed since receipt of the first portion of the software update, and may direct the second conveyance to a proximity of the first conveyance if a period of time has elapsed since receipt of the first portion of the software update. At block 348, the processor 104 may transmit the first portion and the second portion of the software update through a transceiver in the master vehicle, may transmit the first portion and the second portion of the software update through a transceiver in one or more of the first vehicle and the second conveyance, may store the first portion and the second portion of the software update in a memory in one or more of the first conveyance and the second conveyance, and may process, by processors in the first conveyance and the second conveyance, the first portion and the combine second part.

It should be noted that the master conveyance, the subset of conveyances and the further subset of conveyances may be connected via a blockchain network. At block 350, the processor 104 may execute a smart contract to exchange portions of the software updates between the vehicles.

3E Figure 3 illustrates a flow chart 360 according to example embodiments. Referring to 3E For example, an example method may be performed by conveyance node 102 (see FIG 1D ). It is understood that the in 3E The method 360 shown may include additional operations and that some of the operations described therein may be omitted and/or modified without departing from the scope of the method 360. Method 360 is also described with reference to the features contained in 1D are shown for illustrative purposes. In particular, processor 104 of conveyance node 102 may perform some or all of the operations included in method 360 .

In relation to 3E At block 362, the processor 104 may receive a software update in a vehicle. At block 364, the processor 104 may perform a first validation of the software update in a first environment, the first environment including a lowest amount of potential interactions. At block 366, if the first validation succeeds, the processor 104 may perform another validation of the software update in another environment. The wider environment may include a greater amount of potential interactions than the first environment.

3F 3 illustrates a flowchart 380 of an example method according to example embodiments. Referring to 3F the method 380 may also include one or more of the following steps. At block 382, processor 104 may revert to a previous software version if one or more of the first validation and the second validation fails. At block 384, processor 104 may receive further validation of the software update from another vehicle. At block 386, processor 104 may invoke the software update based on an analysis of the wider environment. At block 388, the processor 104 may receive confirmations of further validation of the software update from multiple vehicles. The acknowledgments may represent a consensus on a blockchain to which the conveyances belong. At block 390, processor 104 may execute a smart contract to record at least one block of data reflecting the validated software update on a ledger of the blockchain.

4A 4 illustrates an example blockchain vehicle configuration 400 for managing blockchain transactions associated with a vehicle, according to example embodiments. Referring to 4A For example, a particular conveyance/vehicle 425 is involved in transactions, such as asset transfer transactions (e.g., access key exchanges, vehicle service, dealer transactions, delivery/pickup, transportation services, etc.). The vehicle 425 may receive assets 410 and/or deliver/transfer assets 412 according to one or more transactions defined by smart contracts. The transaction module 420 can record information such as parties, balances, service descriptions, date, time, location, results, notifications, unexpected events, etc remote servers and/or managed by remote blockchain peers, among which the vehicle 425 itself may be a blockchain participant and/or blockchain peer. In other embodiments, the blockchain 430 resides in the vehicle 425. The assets received and/or transmitted may be based on location and consensus as described herein.

4B 4 illustrates an example blockchain vehicle design 440 for managing blockchain transactions between a service node (e.g., gas station, service center, body shop, rental center, car dealership, a local service station, a delivery/pickup center, etc.) and a vehicle according to example embodiments. In this example, the vehicle 425 may have self-directed to a service node 442 because the vehicle requires service and/or needs to stop at a specific location. The service node 442 can perform a service (e.g., refueling) or can call the vehicle 425 for a service at a specific time, with a specific strategy, such as an oil change, battery charge or change, tire change or replacement, and register any other transport-related service. The services 444 provided may be provided based on a smart contract downloaded or accessed via the blockchain 430 and identified for permission to provide such services at a particular exchange rate. The services can be logged in the transaction log of the transaction module 420, the credits 412 are transferred to the service center 442 and the blockchain can log transactions to show all information regarding the most recent service. In other embodiments, the blockchain 430 resides in the vehicle 425 and/or on the service center server. In one example, a transportation event may require refueling or other vehicle service, and the occupants may then be responsible for increasing the asset value for such service. The service can be provided via a blockchain notification, which is then used to distribute asset value to inmates via their respective asset values. Responsibility for the activities of the service center can be based on the asset transfer described here.

4C 4 illustrates an example blockchain vehicle configuration 450 for managing blockchain transactions conducted between different vehicles, in accordance with the example embodiments. The vehicle 425 may communicate with another vehicle 408 to perform various actions such as sharing access keys, transferring keys, capturing service calls, etc. when the vehicle has reached a status at which the assets must be shared with another vehicle. For example, the vehicle 408 may need a battery charge and/or may have a problem with a tire and be en route to pick up a package for delivery. The vehicle 408 may notify another vehicle 425 that is on its network and that is providing its blockchain participation service. The vehicle 425 may then receive the information via a wireless communication request to perform the package pickup from the vehicle 408 and/or from a server (not shown). The transactions are logged in the transaction modules 452 and 420 of both vehicles. The assets are transferred from the vehicle 408 to the vehicle 425 and the record of the asset transfer is logged in the blockchain 430/454 assuming that the blockchains are different from each other, or is logged in the same blockchain shared by all parties is being used. Responsibility for the transferred assets may be based on asset values (e.g. access keys) as described here.

5 5 illustrates blockchain blocks 500 that may be added to a distributed ledger and contents of block structures 502A through 502n, according to exemplary embodiments. Referring to 5 Clients (not shown) can submit entries to blockchain nodes to initiate activities on the blockchain. As an example, clients can be applications that act on behalf of a requestor, such as a device, person, or entity, to propose entries for the blockchain. The multiple blockchain peers (eg, blockchain nodes) can maintain a state of the blockchain network and a copy of the distributed ledger. Various types of blockchain nodes/peers may exist in the blockchain network, including endorsing peers, which simulate and endorse entries proposed by clients, and committing peers, which verify endorsements, validate entries, and submit entries transfer the distributed ledger. In this example, the blockchain nodes can play the role of endorser node, committer node, or both.

The present system includes a blockchain that stores immutable, sequenced records in blocks, and a state database (current world state) that maintains a current state of the blockchain. One distributed ledger can exist per channel and each peer maintains its own copy of the distributed ledger for each channel to which it belongs. The present blockchain is an entry log structured as hashed blocks, each block containing a sequence of N entries. The blocks can include various components, such as those in 5 shown. The concatenation of the blocks can be generated by adding a hash of a previous block's header inside a current block's block header will. This way, all entries in the blockchain are sequenced and cryptographically linked together, preventing tampering with the blockchain data without breaking the hash links. Furthermore, because of the links, the youngest block in the blockchain represents each entry that precedes it. The present blockchain can be stored in a peer file system (local or attached storage) that supports an append-only blockchain workload.

The current state of the blockchain and the distributed ledger can be stored in the state database. The current state data represents the most recent values for all keys that have ever been included in the chain entry log of the blockchain. Smart contract executable code calls make entries against the current state in the state database. In order to make these interactions of executable code of a smart contract as efficient as possible, the latest values of all keys are stored in the state database. The state database can include an indexed view of the blockchain's entry log, so it can be regenerated off-chain at any time. The state database can be restored automatically (or generated on demand) when the peer starts before accepting entries.

Endorsing nodes receive entries from clients and endorse the entry based on simulated results. Promoting nodes store smart contracts that simulate the entry proposals. When an endorsing node endorses an entry, the endorsing node creates an entry endorsement, which is a signed response from the endorsing node to the client application indicating endorsement of the simulated entry. The method of endorsing an entry depends on an endorsement policy, which may be specified in executable code of the smart contract. An example of an endorsement policy is: "The majority of endorsement peers must endorse the entry." Different channels may have different endorsement policies. Approved entries are forwarded to a stewardship service by the client application.

The stewardship service accepts approved entries, arranges them into a block, and transmits the blocks to the providing peers. For example, the security service can initiate a new block when a threshold of entries has been reached, a timer expires, or some other condition. In this example, the blockchain node is a committing peer that has received a block of data 602A for storage on the blockchain. The security service can consist of a cluster of folders. The security service does not process entries or smart contracts, nor does it manage the shared ledger. Rather, the security service can accept the approved entries and specify the order in which these entries are committed to the distributed ledger. The architecture of the blockchain network can be designed in such a way that the specific implementation of the “Order” (e.g. Solo, Kafka, BFT, etc.) becomes a pluggable component.

Entries are written to the distributed ledger in a consistent order. The order of the entries is set to ensure that the state database updates are valid when pushed out to the network. Unlike a cryptocurrency blockchain system (e.g., bitcoin, etc.) where ordering occurs by solving a cryptographic puzzle or by data mining (mining), in this example, the distributed ledger parties can choose the ordering mechanism that that best fits this network.

Referring to 5 For example, a block 502A (also referred to as a data block) stored on the blockchain and/or distributed ledger may include multiple data segments, such as a block header 504A-504n, transaction-specific data 506A-506n, and block metadata 508A-508A 508n. It should be noted that the various blocks shown and their contents, such as block 502A and its contents, are for example purposes only and are not intended to limit the scope of the example implementations. In some cases, both the block header 504A and the block metadata 508A may be smaller than the transaction-specific data 506A storing input data; however, this is not a requirement. Block 502A may store transaction information of N entries (e.g., 100, 500, 1000, 2000, 3000, etc.) within block data 510A through 510n. Block 502A may also include a link to an earlier block (e.g., in the blockchain) within block header 504A. In particular, the block header 504A may include a hash of the header of a previous block. The block header 504A may also include a unique block number, a hash of the block data 510A of the current block 502A, and the like. The block number of block 502A can be unique and in an incremental/sequential order, starting from zero. The first block in the blockchain can be referred to as an origin block, which includes information about the blockchain, its participants, the data stored on it, and so on.

The block data 510A can store entry information of each entry recorded within the block. For example, the entry data may include one or more of the following: a type of entry, a version, a timestamp, a distributed ledger channel ID, an entry ID, an epoch, a payload visibility, a path for an intelligent executable code contract (deploy tx), a name for the smart contract executable code, a version of smart contract executable code, inputs (smart contract executable code and functions), a client (producer) identification, such as a public Keys and a certificate, a signature of the client, identities of proponents, proponent signatures, a proposal hash, events of smart contract executable code, response status, namespace, a read set (list of keys and version read by the entry , etc.), a write set (list of keys and values, etc.), a seed key, an en dkey, a list of keys, a hash tree query summary, and the like. The entry data can be stored for each of the N entries.

In some embodiments, block data 510A may also store transaction-specific data 506A, adding additional information to the hashed chain of blocks in the blockchain. Accordingly, the data 506A may be stored in an immutable log of blocks in the distributed ledger. Some of the benefits of storing such data 506A are reflected in the various embodiments disclosed and illustrated herein. The block metadata 508A can store multiple fields of metadata (e.g., as a byte array, etc.). The metadata fields may include a signature when the block was created, a reference to a last configuration block, an entry filter identifying valid and invalid entries within the block, the last surviving offset of an ordering service that ordered the block, and the like. The signature, the last configuration block and the folder metadata can be added by the security service. Furthermore, a provider of the block (e.g., a blockchain node) may add validity/invalid information based on an endorsement policy, verification of read/write records, and the like. The entry filter may include a byte array of a size equal to the number of entries in the block data 510A and a validation code indicating whether an entry was valid/invalid.

The other blocks 502B through 502n in the blockchain also have headers, files, and values. However, unlike the first block 502A, each of the headers 504A through 504n in the other blocks includes the hash value of an immediately preceding block. The hash of the immediately previous block need only be the hash of the header of the previous block, or may be the hash of the entire previous block. By including the hash value of a previous block in each of the remaining blocks, a block-by-block traceback from the Nth block back to the originating block (and its original file) can be performed, as indicated by arrows 512, around a verifiable and immutable chain of custody to build.

The above embodiments may be implemented in hardware, in a computer program executed by a processor, in firmware, or in a combination of the above. A computer program may be embodied on a computer-readable medium, such as a storage medium. For example, a computer program may reside in random access memory ("RAM"), flash memory, read-only memory ("ROM"), erasable programmable read-only memory ("EPROM"), electrically erasable programmable read-only memory ("EEPROM"), registers , hard drive, removable media, compact disk read-only memory ("CD-ROM"), or any other form of storage media known in the art.

An example storage medium can be coupled to the processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium can be integrated into the processor. The processor and storage medium may reside in an application specific integrated circuit (“ASIC”). Alternatively, the processor and the storage medium can also exist as discrete components. For example illustrated 6 an exemplary computer system architecture 600, which may represent or be integrated with any of the components described above, etc.

6 is not intended to limit the scope of application or functionality of any embodiment described herein men imply. Notwithstanding, the compute node 600 may be implemented with and/or perform any of the functions set forth above.

Within the computer node 600 is a computer system/server 602 that can operate in numerous other general purpose or special purpose computer system environments or configurations. Examples of known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 602 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems , set-top boxes, programmable consumer electronics, network personal computers, minicomputer systems, mainframe systems, and distributed cloud computing environments incorporating any of the above systems or devices, and the like.

Computer system/server 602 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. In general, program modules can include routines, programs, objects, components, or data structures, and so on, that perform specific tasks or implement specific abstract data types. Computer system/server 602 may be practiced in distributed cloud computing environments where tasks are performed by remote devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media, including memory devices.

As in 6 As shown, computer system/server 602 in cloud computing node 600 is shown in the form of a general purpose computing device. The components of the computer system/server 602 may include, among other things, one or more processors or processing units 604, a system memory 606, and a bus that couples various system components, including the system memory 606, to the processor 604.

The bus represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of different bus architectures. These architectures include, for example, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MCA) bus, the Enhanced ISA (EISA) bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnects (PCI) bus.

The computer system/server 602 typically includes a variety of media readable by the computer system. Such media can be any available media that can be accessed by computer system/server 602 and includes both volatile and non-volatile media, removable and non-removable media. The system memory 606, in one embodiment, implements the flowcharts of the other figures. System memory 606 may include computer system-readable media in the form of volatile memory, such as random access memory (RAM) 608 and/or cache memory 610. Computer system/server 602 may further include other removable/non-removable, volatile/non-volatile computer system storage media. For example only, memory 606 may be configured to read from and write to a non-removable, non-volatile magnetic medium (not shown and typically referred to as a "hard drive"). Although not shown, a magnetic disk drive for reading and writing a removable, non-volatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading and writing a removable, non-volatile optical disk, such as for example a CD-ROM, DVD-ROM or other optical medium. In such cases, each may be connected to the bus via one or more data carrier interfaces. As shown and described below, memory 606 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of various embodiments of the application.

By way of example and without limitation, a program/utility having a set (at least one) of program modules may be stored in memory 606, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating systems, one or more application programs, other program modules, and program data, or a combination thereof, may comprise an implementation of a network environment. Program modules generally perform the functions and/or methodologies differently ner embodiments of the application as described herein.

As will be appreciated by those skilled in the art, aspects of the present application may be embodied as a system, method, or computer program product. Accordingly, aspects of the present application may take the form of a hardware-only embodiment, a software-only embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which are discussed herein can be referred to generically as a "circuit", a "module" or a "system". Furthermore, aspects of the present application may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.

Computer system/server 602 may also interface with one or more external devices via an I/O adapter 612, such as a keyboard, pointing device, display, etc., with one or more devices that enable a user interact with computer system/server 602, and/or communicate with any devices (e.g., network card, modem, etc.) that enable computer system/server 602 to communicate with one or more other computing devices. Such communication may occur via adapter 612 I/O interfaces. Furthermore, computer system/server 602 may communicate with one or more networks, such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via a network adapter. As shown, adapter 612 communicates with the other components of computer system/server 602 over a bus. It should be understood that although not shown, other hardware and/or software components could be used in connection with the computer system/server 602 as well. Examples include but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives and data archiving systems, etc.

Although an exemplary embodiment of at least one of a system, a method, and a non-transitory computer-readable medium has been shown in the accompanying drawings and described in the foregoing detailed description, it should be understood that the application is not limited to the disclosed embodiments, but rather that numerous rearrangements, modifications and substitutions can be made as set forth and defined by the following claims. For example, the capabilities of the system of the various figures may be implemented by one or more of the modules or components described herein, or in a distributed architecture, and may include a transmitter, a receiver, or a pair of both. For example, all or a portion of the functionality performed by each module may be performed by one or more of those modules. Furthermore, the functionality described herein may be performed at different times and in relation to different events, inside or outside the modules or components. Additionally, information sent between different modules may be sent between modules over at least one of a data network, the Internet, a voice network, an Internet Protocol network, a wireless device, a wired device, and/or multiple protocols. Additionally, the messages sent or received by any of the modules may be sent or received directly and/or through one or more of the other modules.

Those skilled in the art will appreciate that a "system" can be embodied as a personal computer, server, console, personal digital assistant (PDA), cell phone, tablet computing device, smartphone, or other suitable computing device or combination of devices can. The depiction of the functions described above as being performed by a "system" is not intended in any way to limit the scope of the present application, but is intended to provide a specific example of many embodiments. Rather, the methods, systems, and apparatus disclosed herein may be implemented in localized and distributed forms consistent with computing technology.

It should be noted that some of the system features described in this specification have been presented as modules to emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising special purpose Very Large Scale Integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in programmable hardware devices, such as field programmable gate arrays, more programmable array logic, programmable logic devices, graphics processing units, or the like.

A module can also be implemented, at least in part, in software for execution by various types of processors. An identified unit of executable code may include, for example, one or more physical or logical blocks of computer instructions, which may be organized as an object, a procedure, or a function, for example. Notwithstanding, the executable elements of an identified module need not be physically co-located, but may comprise disparate instructions stored in different locations which, when logically linked together, form the module and achieve the stated purpose for the module. Additionally, modules may be stored on a computer-readable medium, such as a hard drive, flash device, random access memory (RAM), tape, or any other medium used to store data.

A module of executable code can be virtually a single instruction or many instructions, and can even be distributed across multiple different code segments, between different programs, and across multiple storage devices. Similarly, operational data herein may be identified and illustrated within modules and may be embodied in any suitable form and organized in any suitable type of data structure. The operational data may be collected as a single set of data, or may be distributed across different locations, including across different storage devices, and need exist—at least in part—only as an electronic signal in a system or network.

It should be understood that the components of the application, as generally described and illustrated in the figures herein, can be arranged and configured in a wide variety of different configurations. The detailed description of the embodiments is therefore not intended to limit the scope of protection of the application as claimed, but is merely representative of selected embodiments of the application.

One of ordinary skill in the art will readily appreciate that the above embodiments may be practiced using steps in a different order and/or using hardware elements in configurations other than those disclosed. Therefore, while the application has been described in terms of these preferred embodiments, those skilled in the art will recognize that certain modifications, variations, and alternative constructions are possible.

While preferred embodiments of the present application have been described, it should be understood that the described embodiments are illustrative only and that the scope of the application is defined solely by the appended claims, which should be considered in light of the full breadth of their equivalents and modifications (e.g., protocols, hardware devices, software platforms, etc.).

Claims (10)

System comprising: a processor of a vehicle of a subset of vehicles; and a memory communicatively coupled to the processor, the processor: receives a software update in the conveyance; validates the software update based on one or more of the following: a period in which the software update is used, and a number of uses of the software update by the subset of conveyances; propagates the software update to a further subset of conveyances based on the validation, wherein the further subset of conveyances is greater than the subset of conveyances. system after claim 1 , wherein the processor propagates the software update to a set of all remaining conveyances, the set of all remaining conveyances being greater than the further subset of conveyances. system after claim 1 wherein one or more of the subset of conveyances, the further subset of conveyances, and the set of all remaining conveyances are based on one or more of: existing software; existing hardware; a geographic location; an ambient temperature; a means of transport brand; a vehicle model; a vehicle condition; a road condition; and a conveyance destination. system after claim 1 , wherein the processor changes one or more of the subset of conveyances, the further subset of conveyances, and the set of all remaining conveyances if a negative result is determined based on the validation. system after claim 1 , wherein the processor reverts one or more of the subset of conveyances, the further subset of conveyances and the set of all remaining conveyances to one or more of an original software version and a previous software update if, based on the validation, a negative result is determined. system after claim 1 wherein the processor uses the software update for: a first period of time through the subset of conveyances; and a second length of time through the further subset of conveyances, the first length of time being greater than the second length of time. system after claim 1 , where the subset of conveyances belongs to a blockchain network. system after claim 6 wherein the processor executes a blockchain network smart contract to validate the software update and propagate the software update through multiple of the vehicles. system after claim 1 , wherein the processor performs a first validation of the software update in a first environment, the first environment including a least amount of potential interactions, and performs a further validation of the software update in a further environment if the first validation is successful, wherein the wider environment includes a greater amount of potential interactions than the first environment. system after claim 9 , wherein the processor receives further validation of the software update from another conveyance.

Images