Systems and methods to establish secure vehicle networks

<u>FIELD</u>

0001Example embodiments relate to systems and methods to establish secure communication networks, and more specifically for intra-vehicle communication for components within a vehicle, and inter-vehicle communications amongst vehicles, for example, amongst agricultural vehicles.

<u>BACKGROUND</u>

0002A vehicle, such as an agricultural vehicle as in a tractor, combine, implement or a construction vehicle, as in a loader or an excavator, includes a plurality of electronic components that are required to communicate with each other.

0003Example electronic components can include engine controllers, transmission controllers, telematics boxes, displays, on-vehicle servers, wireless communication controllers, satellite antenna, steering controllers, window controllers, implement hitch controllers, generators/inverters, brake control modules, seat controllers, etc. A vehicle can have more than one instance of each of the above electronic components. When the components communicate with each other within a vehicle, each such component will be a node within a communication network. An example vehicle might be a planter that can plant multiple rows of seeds at a time. Each row on the planter can have a number of electronic components performing similar functions. Each such electronic component must communicate, and will correspond to a node within a communication network. One node on the planter can receive groundspeed from a tractor pulling the planter, and broadcast the groundspeed to other nodes of the planter so that each of the multiple rows can determine how fast to dispense seeds.

0004Establishing secure communication networks for components within the vehicle and amongst separate vehicles pose a plethora of constraints. In known systems within a vehicle, the time to establish a secure network is constrained by bandwidth of a communications bus, along with the time of verification of additional nodes. Nodes join the network in a serial fashion, broadcasting the desire to join the network.

0005Further, nodes execute these verifications with limited resources. Computation is delegated, for example, to dedicated security hardware, such as a dedicated security core of an embedded microcontroller, or a hardware security chip external to the microcontroller. Similarly, vehicle data transfer rates, for example over a Controller Area Network (CAN) bus, are a limiting factor whereas non-automotive communication might instead rely on a faster network type. Notably, CAN buses are broadcast networks and therefore vehicle nodes may not initially have private communication means to aid in establishing a secure vehicle network.

0006As every node is required to communicate with all nodes to verify all other nodes before establishing a secure network, time and resources may be high. Thus, there is a need for a protocol to establish a secure network within a vehicle and among separate vehicles with reduced time and reduced resources.

<u>SUMMARY</u>

0007At least one example embodiment provides a method of establishing a secure vehicle network including a plurality of nodes, each of the plurality of nodes including a memory storing a leader/ follower field, the method including establishing a communication path from a first node with a value corresponding to "leader" in the leader/follower field to a second node with a value corresponding to "leader" in the leader/follower field, the first node having first information, and communicating from the first node to the second node over the communication path to establish the secure vehicle network by (i) receiving second information from the second node, and (ii) electing the first node to maintain the value corresponding to "leader" in the leader/follower field based on the second information received from the second node.

<u>BRIEF DESCRIPTION OF THE DRAWINGS</u>

0008Example embodiments will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings. <figref idref="f0001 f0002 f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017 f0018 f0019">FIGS. 1-9</figref> represent non-limiting, example embodiments as described herein. <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> is a flowchart describing a method of establishing a secure vehicle network for intra-vehicle communication, according to some example embodiments;</li><li><figref idref="f0002">FIG. 2</figref> is a block representation of a vehicle, according to some example embodiments;</li><li><figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009">FIGS. 3(a)-3(g)</figref> are representative drawings illustrating the establishment of secure vehicle networks on a vehicle for intra-vehicle communication, according to some example embodiments;</li><li><figref idref="f0010 f0011">FIGS. 4(a)-4(b)</figref> are representative drawings illustrating the establishment of secure vehicle networks on a vehicle for intra-vehicle communication, according to some example embodiments;</li><li><figref idref="f0012">FIG. 5</figref> is a table representing the number of secure networks established through each iteration, according to some example embodiments;</li><li><figref idref="f0013 f0014 f0015">FIGS. 6(a)-6(c)</figref> are representative drawings illustrating the establishment of secure vehicle networks amongst vehicles for inter-vehicle communication, according to some example embodiments;</li><li><figref idref="f0016 f0017">FIGS. 7(a)-7(b)</figref> are representative drawings illustrating the establishment of secure vehicle networks amongst vehicles for inter-vehicle communication, according to some example embodiments;</li><li><figref idref="f0018">FIG. 8</figref> shows a example agricultural vehicles according to some example embodiments; and</li><li><figref idref="f0019">FIG. 9</figref> is a representative drawing illustrating a system including a satellite and a vehicle, according to some example embodiments.</li></ul>

<u>DETAILED DESCRIPTION</u>

0009Example embodiments relate to systems and methods to establish secure communication networks, and more specifically for intra-vehicle communication for components within a vehicle, and inter-vehicle communications amongst vehicles, for example, amongst agricultural vehicles.

0010In response to the first node not being elected leader based on the second information received from the second node, the method further includes assigning a value corresponding to "follower" in the leader/follower field of the first node.

0011In response to the first node not being elected leader based on the second information received from the second node, the method further includes assigning a value in an identification number following field in the memory of the first node to correspond to an identifier of the second node.

0012The method may further include, in response to the first node being elected leader, establishing a communication path from the first node to a third node with a value corresponding to "leader" in a leader/follower field of a memory of the third node, and communicating from the first node to the third node over the communication path to establish the secure vehicle network by (i) receiving third information from the third node, and (ii) electing the first node to assign a value corresponding to "follower" to the leader/ follower field based on the third information received from the third node.

0013The electing includes electing the first node to assign a value corresponding to "follower" to the leader/follower field based on an identifier of the first node and an identifier of the second node.

0014The method may further include, in the first node, setting a value corresponding to "leader" in the leader/follower field in response to a reset command performed by the first node.

0015The method may further include, in the first node, setting a value corresponding to "leader" in the leader/follower field in response to a wake-up command performed by the first node.

0016The communicating from the first node to the second node includes communicating over a bus, the bus including at least one of a CAN bus, a wireless bus, a LIN bus, a FlexRay bus, a MOST bus, or an Ethernet bus.

0017The establishing the communication path from the first node to the second node includes, the first node broadcasting a message over the bus, the message including a statement of a desire to join other nodes, and wherein the first node is configured to receive a message from the second node that is broadcast over the bus, the message including a statement of a desire to join other nodes.

0018The first node of the plurality of nodes corresponds to an electronic component, and the electronic component includes at least one of a body controller, an engine controller, a transmission controller, a telematics box, a display, an on-vehicle server, a wireless communication controller, a satellite antenna, a steering controller, a window controller, an implement hitch controller, a generator/inverter, a brake controller, or a seat controller.

0019The first node of the plurality of nodes corresponds to an electronic component of an agricultural vehicle, a mining vehicle, or of a construction vehicle, the agricultural vehicle including one of a tractor, combine, implement, the construction vehicle including one of a loader or an excavator.

0020The method may further include changing a logical network topology of the vehicle secure network by selecting one of the plurality of nodes having a value corresponding to "follower" in the leader/follower field, and assigning a value in the identification number following field of the selected node to a value corresponding to the identification number corresponding to the one of the plurality of nodes.

0021At least one example embodiment provides a method of communicating among a plurality of vehicles, at least one of the plurality of vehicles including at least one electronic component, the at least one electronic component including a memory storing a leader/ follower field, the method includes sending a first protected message from an electronic component in a first vehicle to an electronic component in a second vehicle, the leader/follower field of the at least one of the electronic components of the first vehicle having a value corresponding to "network leader", and receiving a second protected message from the second vehicle.

0022The first vehicle may include a combine, and the second vehicle includes a tractor with a grain cart, and the first vehicle performs a message authentication of each communication from the second vehicle.

0023The first vehicle may communicate to the second vehicle over a wireless communication path.

0024A first electronic component of a first one of the plurality of vehicles includes a value corresponding to "remote guidance leader" in the leader/follower field, and a second electronic component of a second one of the plurality of electronic vehicles has a value corresponding to "remote guidance follower" in the leader/follower field, and the first electronic component sends a message to the second electronic components, the message including information on how the second one of the plurality of electronic components should be driven.

0025The first vehicle includes a tractor, and the second vehicle includes a planter having a plurality of rows, each of the plurality of rows including a respective one of the electronic components, and the first electronic component in the first vehicle having a value corresponding to "remote guidance leader" in the leader/ follower field is configured to broadcast a speed of the tractor, and the second electronic component in the second vehicle having a value corresponding to "remote guidance follower" in the leader/follower field is configured to broadcast the speed of the tractor to the other electronic components in the second vehicle.

0026At least one example embodiment provides an agricultural vehicle including at least one electronic component configured to communicate with other electronic components over a communication bus, the at least one electronic component including a memory configured to (i) store an identification number, (ii) store a leader/follower field indicating whether the electronic component is a leader or a follower, and (ii) store an identification number following field indicating an identification number associated with a node to which the electronic component delegates joining vehicle secure communication networks, a node having a value of "leader" in the leader/follower field configured to join vehicle secure communication networks on behalf of other electronic components having a value of "follower" in the leader/follower field, a value of the identification number following field in the other nodes having a value of "follower" in the leader/ follower field corresponding to a value of the identification number stored in the identification number field of the node having a value of "leader" in the leader/follower field.

0027A first electronic component having a value corresponding to "leader" in the leader/follower field is configured to communicate to a second electronic component having a value corresponding to "leader" in the leader/follower field, the first electronic component is configured to communicate to the second electronic component to elect the first electronic component to change the value in the leader/follower field to "follower."

0028At least one of the plurality of electronic components is configured to perform one of the methods.

0029At least one of the plurality of electronic components having a value corresponding to "follower" in the leader/follower field does not broadcast a message to other nodes indicating a desire to join a vehicle secure network.

0030A vehicle, for example an agricultural vehicle, includes a plurality of machinery, such as tractor and other attached agricultural implements. Such implements may include cultivators, rotors, spreaders, etc.; however, inventive concepts are not limited thereto.

0031The tractor and the other implements includes at least one electronic component. These electronic components communicate with each other through some communication path, e.g. some physical communication path. The communication path is used in establishing the secure vehicle network. For example, individual electronic components may communicate over a communication path including a CAN bus or some other physical bus, for example some other bus over twisted pair communication and/or RS/232 communication; however, inventive concepts are not limited thereto. For example, individual electronic components may communicate over a communication path that is wireless. Further, individual electronic components can communicate over a communication path including a Local Interconnected Network (LIN) bus, or over a communication path including an Ethernet bus; inventive concepts are not limited thereto.

0032According to the example embodiments described herein, the communication among the electronic components is made secure. Individual components may join the secure vehicle network. A system of individual electronic components communicating over the secure vehicle network can be established according to example embodiments.

0033Some example embodiments will now be described more fully with reference to the accompanying drawings in which some example embodiments are illustrated.

0034Accordingly, while example embodiments are capable of various modifications and alternative forms, embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit example embodiments to the particular forms disclosed, but on the contrary, example embodiments are to cover all modifications, equivalents, and alternatives falling within the scope of the claims. Like numbers refer to like elements throughout the description of the figures.

0035It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

0036It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.).

0037The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.

0038It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

0039Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. It will be further understood that terms, e.g., those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

0040Portions of example embodiments and corresponding detailed description are presented in terms of software, or algorithms and symbolic representations of operation on data bits within a computer memory. These descriptions and representations are the ones by which those of ordinary skill in the art effectively convey the substance of their work to others of ordinary skill in the art. An algorithm, as the term is used here, and as it is used generally, is conceived to be a self-consistent sequence of steps leading to a result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of optical, electrical, or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

0041In the following description, illustrative embodiments will be described with reference to acts and symbolic representations of operations (e.g., in the form of flowcharts) that may be implemented as program modules or functional processes including routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types and may be implemented using existing hardware. Such existing hardware may include one or more Central Processing Units (CPUs), Digital Signal Processors (DSPs), Application-Specific-Integrated-Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), computers or the like.

0042It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, or as is apparent from the discussion, terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical, electronic quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

0043In this application, including the definitions below, the term 'module' or the term 'controller' may be replaced with the term 'circuit.' The term 'module' may refer to, be part of, or include processor hardware (shared, dedicated, or group) that executes code and memory hardware (shared, dedicated, or group) that stores code executed by the processor hardware.

0044The module may include one or more interface circuits. In some examples, the interface circuits may include wired or wireless interfaces that are connected to a local area network (LAN), the Internet, a wide area network (WAN), or combinations thereof. The functionality of any given module of the present disclosure may be distributed among multiple modules that are connected via interface circuits.

0045Further, at least one embodiment of the invention relates to a non-transitory computer-readable storage medium comprising electronically readable control information stored thereon, configured such that when the storage medium is used in a controller, at least one embodiment of the method is carried out.

0046Even further, any of the aforementioned methods may be embodied in the form of a program. The program may be stored on a non-transitory computer readable medium and is adapted to perform any one of the aforementioned methods when run on a computer device (a device including a processor). Thus, the non-transitory, tangible computer readable medium is adapted to store information and is adapted to interact with a data processing facility or computer device to execute the program of any of the above-mentioned embodiments and/or to perform the method of any of the above-mentioned embodiments.

0047The computer readable medium or storage medium may be a built-in medium installed inside a computer device main body or a removable medium arranged so that it can be separated from the computer device main body. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium is therefore considered tangible and non-transitory. Furthermore, various information regarding stored images, for example, property information, may be stored in any other form, or it may be provided in other ways.

0048The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. Shared processor hardware encompasses a single microprocessor that executes some or all code from multiple modules. Group processor hardware encompasses a microprocessor that, in combination with additional microprocessors, executes some or all code from one or more modules. References to multiple microprocessors encompass multiple microprocessors on discrete dies, multiple microprocessors on a single die, multiple cores of a single microprocessor, multiple threads of a single microprocessor, or a combination of the above.

0049Shared memory hardware encompasses a single memory device that stores some or all code from multiple modules. Group memory hardware encompasses a memory device that, in combination with other memory devices, stores some or all code from one or more modules.

0050The term memory hardware is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium is therefore considered tangible and non-transitory. Non-limiting examples of the non-transitory computer-readable medium include, but are not limited to, rewriteable non-volatile memory devices (including, for example flash memory devices, erasable programmable read-only memory devices, or a mask read-only memory devices); volatile memory devices (including, for example static random access memory devices or a dynamic random access memory devices); magnetic storage media (including, for example an analog or digital magnetic tape or a hard disk drive); and optical storage media (including, for example a CD, a DVD, or a Blu-ray Disc). Examples of the media with a built-in rewriteable non-volatile memory, include but are not limited to memory cards; and media with a built-in ROM, including but not limited to ROM cassettes; etc. Furthermore, various information regarding stored images, for example, property information, may be stored in any other form, or it may be provided in other ways.

0051As referred to herein, a vehicle may network include, for example, a plurality of individual nodes within a vehicle, such as an automotive vehicle and/or an agricultural vehicle and/or a mining vehicle. Non-limiting example vehicles may include tractors, planters, sprayers, bulldozers, backhoe loaders, forklifts, steam rollers, cranes, haul truck, underground graders, rock breakers, etc.; inventive concepts are not limited thereto. A secure network may include nodes that communicate securely.

0052In accordance with example embodiments, each node will be designated as either a "follower node" or a "leader node." A follower node is a node on a secure network that delegates to a leader node the action to join other secure networks. A leader node is a node with zero or more follower nodes, authorized by the follower nodes to join other secure networks on behalf of the follower nodes. As described below in more detail, by distinguishing between "leader nodes" and "follower nodes" with specific roles, the establishment of secure vehicle networks will be efficient.

0053Furthermore, as referred to herein, a network leader node is a leader node that does not delegate the action to join other secure networks.

0054<figref idref="f0001">FIG. 1</figref> is a flowchart describing a method of establishing a secure vehicle network, for example for intra-vehicle communication, according to some example embodiments.

0055Herein, a vehicle, such as an agricultural vehicle, has a plurality of electronic control units, e.g. electronic components. These electronic control units/ components will be nodes within the secure vehicle network. Each electronic component includes a memory that stores a table 250, to be described in more detail below with reference to <figref idref="f0002">FIG. 2</figref>. The table 250 includes a field, herein described as a "leader/follower" field, which indicates whether the corresponding node is a leader or a follower.

0056Referring to <figref idref="f0001">FIG. 1</figref>, at step S100, the method of establishing a secure vehicle network begins.

0057At step S200, there are more electronic components (nodes) that are to join the secure vehicle network. As an example, a vehicle can be started up or powered on, and thus each electronic component will be turned on. Thus, a vehicle network needs to be created so that each such component/node can communicate. Electronic components that have been woken up, or have been reset, will set the "leader/ follower" field to "leader."

0058At step S300, the first electronic component broadcasts a message, for example over a CAN bus within the vehicle. The broadcasted message will indicate that the electronic component is a leader, and is looking for another electronic component that is also a leader.

0059For example, by following CAN protocol J1939, there is a feature called "address claim." Nodes on the CAN bus can request the "source address" of other nodes on the bus. Nodes can thus discover one another by leveraging address claims.

0060Nodes with a value of "leader" in the leader/follower field may communicate with other nodes with a value of "leader" in the leader/follower field. A request message directed at another node, and a confirmation message from the other node, may result in a "handshake" where one node verifies another. This handshake may establish a secure communication.

0061In step S400, a determination is made as to whether there is another node in the network having a value corresponding to "leader" in the leader/ follower field.

0062If, upon broadcasting the message, there are no other leader nodes in the network, the electronic component ends the method in step S700.

0063However, if there is another, second, electronic component with a "leader" value in the leader/follower field, then at step S500, the first electronic component and the second electronic component engage in a decision protocol/election, to be described in more detail below, to decide which of the first electronic component and the second electronic component will maintain the role of the leader, and keep a value corresponding to "leader" in the leader/follower field. As described below in more detail, because only leader nodes are authorized by the follower nodes to join other secure networks on behalf of the follower nodes, the establishment of secure vehicle networks will be efficient.

0064In step S600, if, as an outcome of the election, the first electronic component is elected leader, the first electronic component, the method returns to step S400.

0065However, if, as an outcome of the election, the first electronic component is not elected leader, the first electronic component may update/change the leader/follower field to correspond to "follower" in step S800.

0066Upon changing the leader/follower field to correspond to "follower," the method may end in step S700. Because nodes communicate and handshake securely, a secure vehicle network will be established.

0067The example method described with reference to <figref idref="f0001">FIG. 1</figref> is not limited thereto. One of ordinary skill in the art may modify the method of <figref idref="f0001">FIG. 1</figref> in various ways. For example, during the communication, a comparison of a digital certificate may be performed. Communication may not be performed to other nodes that do not satisfy requirements of the digital certificate.

0068<figref idref="f0002">FIG. 2</figref> is an illustration of a vehicle 200, according to some example embodiments.

0069Referring to <figref idref="f0002">FIG. 2</figref>, the vehicle 200 includes a first electronic component 210 along with a plurality of other electronic components 211, 212, 213, etc. There is a communication bus 270 connecting each electronic component. The communication bus 270 may be a CAN bus. As mentioned above, the first electronic component 210 may be or include a body controller, an engine controller, a transmission controller, a telematics box, etc.; however, inventive concepts are not limited thereto. The first electronic component 210 includes hardware including a memory 225 that contains a table 250. The table 250 may be contiguous within the memory 225, or may be non-contiguous; inventive concepts are not limited thereto.

0070The table 250 stored in the memory 225 of the electronic component 210 includes a field containing an identification number 251 or another identifier of the electronic component 210. The identification number 251 of the electronic component includes an identifier for the electronic component. For example, the identification number 251 may be a unique identifier, unique to the specific electronic component. For example, the identification number 251 may correspond to a hardware media access control physical address associated with the specific electronic component; however, inventive concepts are not limited thereto, and the identification number 251 may correspond to any other identifier, or any other unique identifier. For example, the identification number 251 may correspond to a serial number associated with the specific electronic component. For example, the identification number 251 may be a numeric string, an alphanumeric string, or a alphabetical string. As a non-limiting example, the identification number may be the "NAME" field as defined by the J1939 Network Management protocol/ standard/ recommended practice.

0071Furthermore, the table 250 also includes a leader/follower field 252. The leader/follower field 252 indicates whether the electronic component 210 is a leader or a follower in the secure vehicle network.

0072Additionally, the table 250 also includes an identification number following field 253 corresponding to an identification number or other identifier of another node to which the electronic component 210 is following. For example, if, after an election between the first electronic component 210 and a second electronic component (not shown) in step S600 in the method described above with reference to <figref idref="f0001">FIG. 1</figref>, the first electronic component 210 is not elected a leader, then the identification number following field in the table 250 may include and/or correspond to the identification number of the second electronic component.

0073If, however, the first electronic component 210 is elected a leader, then the identification number following field 253 may be or correspond to "NULL," or may be the identification number of the first electronic component 210; however, inventive concepts are not limited thereto.

0074The memory 225 of the electronic component 210 may include other fields. For example, other fields may be or include a symmetric key for secure communication, a list of addresses to which a leader leads, a symmetric key between the node and the node of the leader, and/or a public key for the network.

0075<figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009">FIGS. 3(a)-3(g)</figref> are illustrations of intra-vehicle secure vehicle networks, according to example embodiments.

0076Referring to <figref idref="f0003">FIG. 3(a)</figref>, a plurality of nodes 301, 302, 303, 304, 305, 306, 307 are within a vehicle 300. Each node corresponds to an electronic component. Each of the plurality of nodes 301, 302, 303, 304, 305, 306, 307 includes the memory 225 described above with reference to <figref idref="f0002">FIG. 2</figref>.

0077There will be some method of physical communication between each of the plurality of nodes 301, 302, 303, 304, 305, 306, 307. For example, each of the plurality of nodes 301, 302, 303, 304, 305, 306, 307 may be able to broadcast and communicate to others of the plurality of nodes 301, 302, 303, 304, 305, 306, 307 over a CAN bus, such as the communication bus 270 described above with reference to <figref idref="f0002">FIG. 2</figref>, or over some wireless communication; however, inventive concepts are not limited thereto.

0078The state of the vehicle 300 illustrated in <figref idref="f0003">FIG. 3(a)</figref> corresponds to a state in which each of the plurality of nodes 301, 302, 303, 304, 305, 306, 307 has been reset or woken up.

0079Upon each of the plurality of nodes 301, 302, 303, 304, 305, 306, 307 being reset (or woken up), each of the plurality of nodes 301, 302, 303, 304, 305, 306, 307 may have a value corresponding to "leader" in the field corresponding to the leader/follower field 252 shown in <figref idref="f0002">FIG. 2</figref>.

0080Each of, or at least some of, the plurality of nodes 301, 302, 303, 304, 305, 306, 307, will broadcast or send out a message along a communication channel such as the communication bus 270, requesting other nodes to join in creating a secure vehicle network. For example, each of the nodes 301, 302, 303, 304, 305, 306, and 307 can broadcast a message over a CAN bus; the message may include a message stating that they wish to join a network. Some vehicles may greatly benefit from parallelism, for example if nodes are limited by computational resources and/or other operations cannot be, or cannot easily, be done in parallel.

0081A CAN bus allows only one node to send a message at any time. For example, a vehicle with a CAN bus may have one or more pairs of nodes executing verifications on embedded security hardware in parallel with a pair of nodes communicating back and forth over a CAN bus.

0082Each node with a value corresponding to "leader" in the leader/follower field 252 that has broadcast a message stating a desire to join a secure vehicle network attempts to pair up with another node with a value corresponding to "leader" in the leader/follower field 252 that has also broadcast a message stating a desire to join a secure vehicle network. For example, as illustrated in <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009">FIG. 3</figref>, nodes 301 and 302 communicate a desire to join; similarly, nodes 303 and 304, and nodes 306 and 307.

0083Each node may establish a secure network with the first node that is available to do so. Upon agreeing to join to another node with a value corresponding to "leader" in the leader/follower field 252, nodes may not send other messages requesting to pair up with another node, and instead may engage in an election to determine a leader and a follower, after pairing. Alternatively, a node may indicate a desire to pair with a specific other node chosen from the address claim process as in the J1939 protocol, in which case the nodes may not broadcast. However, inventive concepts are not limited thereto.

0084For example, nodes 301 and 302 may pair up because nodes 301 and 302 were the first to respond to each other's broadcast message; nodes 303 and 304 may pair up because nodes 303 and 304 were the first to respond to each other's broadcast message; and nodes 306 and 307 may pair up because nodes 306 and 307 were the first to respond to each other's broadcast message. However, node 305 may not yet be able to pair up. Further, nodes may have a desire to pair up to specific other nodes; for example, an engine controller may attempt to pair with a transmission controller.

0085For example, on a J1939 CAN bus, there are two kinds of message targets: broadcast and point-to-point. A first node, e.g. node 301, may broadcast a "want to join" message over the CAN bus, and a second node, e.g. node 302, may send a point-to-point message to node 301 agreeing to join.

0086Alternatively, a preferred node may request joining the networks as well. For example, an engine controller may prefer to join secure networks with a transmission controller. Such electronic components may know to do this based on the J1939 address claims where nodes broadcast an address claimed message (PGN) containing "NAME" message.

0087<figref idref="f0004">FIG. 3(b)</figref> is an illustration of a vehicle 300, according to an example embodiment.

0088Referring to <figref idref="f0004">FIG. 3(b)</figref>, each pair of the plurality of nodes may engage in an election to determine which element will remain a leader, and which element will change the leader/follower field 252 to correspond to "follower."

0089Determining which node is a leader and which node is a follower may be performed through any method. For example, the leader may be determined as the node with the lower identification number 251, or with the lower hash, such as the lower SHA256 hash, of the identification number 251. Thus, any node may be the leader of the secure network, unless otherwise restricted by a specific implementation. Thus, even if nodes within the secure vehicle network may change, a leader may not change.

0090Upon determination of the leader, the node that was not determined to be a leader will change the leader/follower field 252 to a value corresponding to "follower," and will change the identification number following field 253 to a value corresponding to the identification number of the node that was determined to be leader.

0091As an illustration, suppose nodes 301 and 302 agree to join in a secure network. Nodes 301 and 302 compare their respective identification numbers 251. Suppose node 301 has a lower identification number than node 302. Suppose, accordingly, node 301 is determined to be the leader. Node 301 will maintain a value corresponding to "leader" in the leader/follower field 252; node 302 will change the respective leader/follower field to correspond to "follower," and will change the identification number following field 253 to correspond to the identification number of node 301.

0092Similarly, as illustrated in <figref idref="f0004">FIG. 3(b)</figref>, nodes 303 and 304 engage in a communication to determine that node 304 is a leader with node 303 following. Nodes 306 and 307 engage in a communication to determine that node 306 is a leader.

0093Further, nodes within the network that have a value corresponding to "leader" in the leader/follower field 252 may broadcast another message to determine other nodes that have a value corresponding to "leader" in the leader/follower field 252.

0094For example, as illustrated in <figref idref="f0004">FIG. 3(b)</figref>, nodes 301 and 304 can broadcast a desire to communicate and join in a secure network. Likewise, nodes 305 and 306 may broadcast a desire to communicate and join in a secure network.

0095Some implementations may rely on, or include, some counter to help manage some steps. For example, according to some example embodiments, some method of synchronizing the pairing of nodes may be achieved with a counter, thus creating a concept of a round, or round robin. For example, a round may allow nodes to organize pairing to minimize or reduce the total number of rounds to establish the secure vehicle network.

0096<figref idref="f0005">FIG. 3(c)</figref> is an illustration of a vehicle 300, according to an example embodiment.

0097Referring to <figref idref="f0005">FIG. 3(c)</figref>, nodes 304 and 305 have a value corresponding to "leader" in the leader/follower field 252. Furthermore, nodes 301, 302, 303, 306, and 307 have a value corresponding to "follower" in the leader/follower field 252. Still further, node 302 has the identification number 251 of node 301 in the identification number following field 253; nodes 301 and 303 have the identification number 251 of node 304 in the respective identification number following field 253; node 307 has the identification number 251 of node 306 in the identification number following field 253; and node 306 has the identification number 251 of node 305 in the identification number following field 253.

0098Nodes 304 and 305, which have a value corresponding to "leader" in the respective leader/follower field 252, may communicate a message to join and pair up.

0099<figref idref="f0006">FIG. 3(d)</figref> is an illustration of a vehicle 300, according to an example embodiment.

0100Referring to <figref idref="f0006">FIG. 3(d)</figref>, upon pairing of nodes 304 and 305, node 305 will be elected as a leader while node 305 will be the follower. Thus, node 304 may have a value corresponding to "leader" in the leader/follower field 252, while node 305 may have a value corresponding to "follower" in the leader/follower field 252. Further, node 305 may have a value corresponding to the identification number of the leader node 304 in the identification number following field 253.

0101Thus, the state of the vehicle 300, as illustrated in <figref idref="f0006">FIG.3(d)</figref>, will correspond to a data structure such as a tree. The root of the tree corresponds to node 304 while internal nodes of the tree may correspond to nodes 301, 305, and 306, while leaves of the tree correspond to nodes 302, 303, and 307.

0102<figref idref="f0007">FIG. 3(e)</figref> is an illustration of the contents of the memory 225 of each node in the secure vehicle network illustrated in <figref idref="f0006">FIG. 3(d)</figref>, according to an example embodiment.

0103Referring to <figref idref="f0007">FIG. 3(e)</figref>, each of nodes 301, 302, 303, 304, 305, 306, and 307 has a memory 225. The memory 225 includes a table with fields as shown.

0104For example, as illustrated in <figref idref="f0007">FIG. 3(e)</figref>, node 301 may have a value corresponding to "304" in the identification number following field 253. Likewise, node 304 may have a value of "NULL" in the identification number following field. Alternatively, node 304 may have a value corresponding to the identification number corresponding to node 304 in the identification number following field 253. For example, node 304 may have a self-referential identification number following field 253.

0105<figref idref="f0008">FIG. 3(f)</figref> is an illustration of a vehicle 300, according to an example embodiment.

0106Comparing <figref idref="f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017 f0018 f0019">FIG. 3(f) to FIG. 3(d)</figref>, the logical network topology is different. Further steps can be performed by nodes in the vehicle network to restructure the network topology to a more efficient topology. There may be a communication between follower nodes to change the identification number following field 253. For example, a node, e.g. node 305, with a follower in the leader/follower field 252, may broadcast a message corresponding to the respective identification number following field 253. All nodes that follow node 305, e.g. nodes 306 and 307, may update their respective identification number following field 253 to correspond to those of node 305. Thus, the network topology may change. The vehicle network illustrated in <figref idref="f0008">FIG. 3(f)</figref> may simplify or speed up some operations, as compared to the vehicle network illustrated in <figref idref="f0006">FIG. 3(d)</figref>. A message from the leader to followers to change topology should be secure. For example, the current leader may tell all internal nodes and leaf nodes to change topology. Further, a network leader may broadcast a proof of leadership.

0107Similar to <figref idref="f0007">FIG. 3(e)</figref>, <figref idref="f0009">FIG. 3(g)</figref> illustrates that node 304 has a value corresponding to "leader" in the leader/follower field 252. However, nodes 301, 302, 303, 305, 306, and 307 all have the identification number corresponding to node 304 in the identification number following field 253. This corresponds to such a restructuring of the network topology.

0108<figref idref="f0009">FIG. 3(g)</figref> is an illustration of the contents of the memory 225 of each node of <figref idref="f0008">FIG. 3(f)</figref>, according to an example embodiment.

0109Referring to <figref idref="f0009">FIG. 3(g)</figref>, the contents of the memory 225 of each node are similar to those illustrated in <figref idref="f0007">FIG. 3(e)</figref>. However, because each follower node illustrated in <figref idref="f0007">FIG. 3(e)</figref> directly follows node 304, the contents of each follower node's identification number following field 253 contains, or corresponds to, the identification number corresponding to leader node 304.

0110As illustrated in <figref idref="f0007">FIGS. 3(e)</figref> and <figref idref="f0009">3(g)</figref>, leader node 304 may also be a network leader node. Such a network leader node does not delegate the action to join other secure networks.

0111Such a network leader node may securely distribute a shared key to nodes in the secure network for securely communicating with other nodes on the vehicle network. For example, the network leader node 304 in <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009">FIG. 3</figref> might distribute a shared secure CAN bus key for broadcasting messages that may be verified by recipient nodes to detect for potential message tampering.

0112Inventive concepts are not limited to pairing network leaders. For example, according to some example embodiments, a third node may be required, for example as required by the network topology.

0113Furthermore, example embodiments may contain gateway nodes that are connected to multiple vehicle networks. According to example embodiments, such a gateway node might treat the secure networks independently, for example, the node might be a leader on one secure network and a follower on another.

0114Example embodiments are not limited to the above network topologies. For example, other network topologies may include a binary tree. Such a binary tree may be implemented with a version of a round robin protocol.

0115According to some example embodiments, a remote node, that is, a node not on the vehicle, may be required to cross-verify during the pairing of secure networks. For example, the vehicle 300 may require communication with a remote internet server (not shown).

0116For instance, consider an anhydrous ammonia applicator implement with a control valve controlled by an attached tractor. To prevent tampering in response to a terrorist action, a tractor leader node might require a trusted remote computer to also verify the implement leader node or vise-versa as a precondition to opening the control value.

0117Furthermore, an example embodiment may have nodes with a cached state from prior verification sequences. For example, previously verified certificates could be stored in a compact form or in a way which is faster to verify.

0118<figref idref="f0010">FIG. 4(a)</figref> is an illustration of a vehicle 400, according to some example embodiments.

0119According to some example embodiments, network leader nodes may delegate verification to one or more follower nodes.

0120As illustrated in <figref idref="f0010">FIG. 4(a)</figref>, network leader nodes 401, 402, and 406 had previously established a shared key with their respective follower nodes. Network leader nodes 401, 402, and 407 might use the secure key to securely communicate to follower nodes to enable the follower nodes to perform verifications. If two network leader nodes, for example network leader nodes 401 and 402, are determined where follower nodes have made progress on verifying the other network leader node, for example node 406, the time to establish a secure vehicle network may be reduced. For example, if vehicle verification computation resources were constrained, such a time may be reduced.

0121As shown in <figref idref="f0010">FIG. 4(a)</figref>, the non-pairing network leader node 407 has enough follower nodes 405 and 406 to ensure follower nodes will have made progress verifying the eventual new network leader node of the pairing nodes. This may be coordinated intentionally.

0122<figref idref="f0011">FIG. 4(b)</figref> illustrates a subsequent secure network pairing wherein each network leader node 402, 407 retrieves a verification from a follower node. The time to establish the secure network in <figref idref="f0010">FIGS. 4(a)</figref> and <figref idref="f0011">4(b)</figref> may therefore be reduced even if the follower nodes merely had not yet fully completed the verification ahead of time.

0123<figref idref="f0012">FIG. 5</figref> illustrates a number of iterations needed to establish a secure network, according to some example embodiments.

0124As an example, consider a vehicle, such as the vehicle 300 illustrated above, that has a plurality of electronic components, such as the electronic component 210. Each such electronic component follows the method illustrated in <figref idref="f0001">FIG. 1</figref> to establish a vehicle network, consolidating nodes with each iteration.

0125Each node within the vehicle network executes such a method illustrated in <figref idref="f0001">FIG. 1</figref> in parallel. Accordingly, each such execution of the method illustrated in <figref idref="f0001">FIG. 1</figref> might approximately double the size of an individual network, and reduce the number of networks in half for each such iteration. Thus, given N individual nodes (where N is a natural number), the time taken to securely define a network may be O(log(N)).

0126In contrast, if instead every node is required to communicate with all nodes to verify all other nodes before establishing a secure network, such a secure network might take approximately O(N²) time to verify the security. Thus, O(N²) time may be detrimental if, for example, the time to compute the verification were the limiting factor of establishing the security for the network. Further, some nodes may not have enough memory to store verification information for all nodes, and may exclude some nodes from otherwise participating in the secure network or causing verification information to be redundantly transmitted on the vehicle network while establishing the secure network. If the vehicle network were on a CAN bus, redundant messages sent in series would exacerbate the time required to establish the secure vehicle network.

0127<figref idref="f0013 f0014 f0015">FIGS. 6(a)-6(c)</figref> illustrates secure inter-vehicle networks, according to example embodiments. Example embodiments may be advantageous for a vehicle to form a secure vehicle network with multiple other vehicles, or with different vehicles over time.

0128In the context of <figref idref="f0013 f0014 f0015">FIGS. 6(a)-6(c)</figref>, a leader may correspond to a lead vehicle that establishes a lead guidance path, and a follower may correspond to vehicle or vehicles track or generally follow the lead vehicle guidance path. The path may include offsets in one or more dimensions, such as: (1) lateral offset to allow for cultivating, tilling, leveling, earth-moving, planting, spraying, harvesting, treating, or processing of crop or ground. in adjacent or row-skipping operations and (2) longitudinal offset in the direction of travel of one or more vehicles for collision avoidance, clearance during turning operations, and a delay or lag for tracking/ guidance of the follower vehicle or vehicles to track the lead vehicle.

0129Additionally in the context of <figref idref="f0013 f0014 f0015">FIGS. 6(a)-6(c)</figref>, during operations in the field or worksite, the follower vehicle or lead vehicle may switch roles or reverse roles for efficiency or other reasons, such as resetting or re-establishing of a secure network after expiration of a timer or within a certain geographical zone, defined by a series of coordinates. An operator (not shown) may force the lead vehicle to be a lead vehicle within a certain zone, field or worksite, such as a vehicle that a foreman or project lead directs for a particular project; this lead vehicle may be transitioned at the end of a work shift or to bring a vehicle offline for service or maintenance or to reallocate a lead vehicle to another worksite or area.

0130Referring to <figref idref="f0013">FIG. 6(a)</figref>, two vehicles might form a secure inter-vehicle network with each other. A first vehicle might be an agricultural combine 1100 and a second vehicle might be a tractor with a grain cart 1150; however, inventive concepts are not limited thereto.

0131The combine 1100 includes a plurality of electronic components/nodes 1101(a), 1101(b), ... 1110 that have formed a secure vehicle network, according to the methods described above. Node 1110 is a leader or a network leader, with the other nodes 1101(a), 1101(b), ... being followers.

0132Similarly, the tractor with grain cart 1150 may include a plurality of electronic components/nodes 1151(a), 1151(b), ... 1160 that have formed a secure vehicle network, according to the methods described above. Node 1160 is a leader or a network leader with other nodes 1151(a), 1151(b), ... being followers.

0133Supposing that the agricultural combine 1100 sends data wirelessly to the tractor with grain cart 1150, such that the tractor with grain cart 1150 attempts to drive in tandem with the combine 1100 so that the combine 1100 can transfer material to the tractor with grain cart 1150. To accomplish this, the agricultural combine 1100 might use the methods described in <figref idref="f0001">FIG. 1</figref> to form a secure network with the tractor with grain cart 1150. Further, the combine 1100 and the tractor with grain cart 1150 might establish a secure communication between each other.

0134<figref idref="f0014">FIG. 6(b)</figref> illustrates a state of an inter-secure vehicle network, according to example embodiments.

0135As shown in <figref idref="f0014">FIG. 6(b)</figref>, protected messages may be sent between leader node 1110 and network leader node 1160. For example, the combine 1100 may encrypt and add a message authentication (MAC) for each of the tractor with grain cart 1150's messages. Accordingly, owing to the encryption, the only entity that can see the decrypted data may be the tractor with grain cart 1150. Further, owing to the MAC, the tractor with grain cart 1150 can verify if messages received are from the combine 1100, and act on them accordingly.

0136There may not be a prevention of any denial of service (DOS), and further there may not be protection over other exploits such as stack overflow. But, assuming if the network's verification is cryptographically strong, example embodiments would be able to detect untrusted identities and choose not to establish secure vehicle networks with those entities. Nodes should not establish keys for authentication or confidentiality with entities other than those with which they have established a secure vehicle network.

0137Further, according to some example embodiments, vehicles may identify properties of the other vehicle's nodes. Some properties might include the vehicle type, permissions, features, limitations, etc.; however, example embodiments are not limited thereto.

0138Some secure vehicle networks may choose to reorganize the node topology to facility a better leader node when forming a secure vehicle network for inter-vehicle communication.

0139<figref idref="f0015">FIG. 6(c)</figref> illustrates an inter-vehicle communication network, according to an example embodiment.

0140As illustrated in <figref idref="f0015">FIG. 6(c)</figref>, one node, e.g. node 1120, of the combine 1100 is capable of remote, e.g. wireless, communication with other vehicles. Further, another node, e.g. node 1161, of the tractor with grain cart 1150. Even though the network leader of the combine 1100 may be node 1120, while the network leader of the tractor with grain cart 1150 may be node 1161, node 1110 may be the remote guidance leader while node 1160 may be the remote guidance follower. The remote guidance leader will inform the remote guidance follower how to drive/travel.

0141As a non-limiting example embodiment, the combine 1100 and the tractor with grain cart 1150 establish a secure vehicle network, and use digital certificates to verify each vehicle's network leader node. However, in addition to the secure vehicle network for intra-vehicle communications established in the combine 1100, and the secure vehicle network for intra-vehicle communications established in the tractor with grain cart 1150, there can be another gateway communication for inter-vehicle communications established between the combine 1100 and the tractor with grain cart 1150.

0142As a non-limiting example embodiment, consider the tractor with grain cart 1150 driving up to the combine 1100; there may be thus an inter-vehicle secure communication formed between the two vehicles. An example wherein this may be advantageous would be if the tractor with grain cart 1150 were returning from dropping off a prior load of grain.

0143Further, there may be a safety interlock when appropriate. For example, perhaps the operators of the combine 1100 and the tractor with grain cart 1150 must approve prior to secure vehicle network formation, for example with a prompt on respective displays on the vehicles.

0144Additionally, secure vehicle networks may be changed at runtime. For example, suppose a tractor forms a secure inter-vehicle network with a first implement, such as the tractor with grain cart 1150. After some time, the tractor may physically disconnect from the implement; for example, the tractor may disconnect from the grain cart because the grain cart is full. A node on the tractor which may correspond to the network leader node between the tractor and the grain cart, may detect the event, and would no longer be a leader node of the grain cart.

0145According to example embodiments, there may be an advantage for special nodes in the system to differ from the network leader node.

0146Suppose further the same tractor connects to a second implement. Establishing a secure vehicle network with the second implement may start as a new sequence of the method. Afterwards, a secure vehicle network is formed between the tractor and the second implement.

0147<figref idref="f0016">FIGS. 7(a)</figref> and <figref idref="f0017">7(b)</figref> illustrate an inter-vehicle secure vehicle network amongst a plurality of vehicles and a plurality of implements.

0148Referring to <figref idref="f0016">FIG. 7(a)</figref>, a first combine 1400 may have a plurality of follower nodes 1401, a network leader node 1405, and a remote guidance leader 1410. A first grain cart 1420 may have a plurality of follower nodes 1421, a network leader node 1425, and a remote guidance follower 1430. A second combine 1440 may have a plurality of follower nodes 1441, a network leader node 1445, and a remote guidance leader 1450. A second grain cart 1460 may have a plurality of follower nodes 1461, a network leader node 1465, and a remote guidance follower 1470.

0149Suppose combine 1400 is not physically connected, e.g. connected over a CAN bus, with grain cart 1460. Similarly, suppose combine 1440 is not physically connected, e.g. connected over a CAN bus, with grain cart 1420.

0150However, there may be a secure communication between the first grain cart 1420 and the first combine 1400. Similarly, there may be a secure communication between the second grain cart 1460 and the second combine 1440.

0151Referring to <figref idref="f0017">FIG. 7(b)</figref>, suppose after some time grain cart 1420 is full and needs to unload the grain. According to some example embodiments, there may be coordination in disconnecting, for example by a request from either the combine 1400 or the grain cart 1420.

0152Referring to <figref idref="f0017">FIG. 7(b)</figref>, in an example embodiment the first combine 1400 and the first grain cart 1420 may be chosen to be remote on a secure vehicle network if possible, and may establish a second vehicle network comprising the first combine 1400 and the second grain cart 1460. However, inventive concepts are not limited thereto.

0153According to some example embodiments, remote guidance nodes may try to maintain a secure vehicle network with multiple other vehicles if possible. For example, each combine may try to maintain a secure vehicle network with each grain cart, and vice versa. Similarly, each vehicle may try to maintain a secure vehicle network with every other vehicle.

0154According to some example embodiments, there may be a detection, or a detection and a verification, of the first grain cart 1420 physically out of the way before the second grain cart 1460 takes the place of the first grain cart 1420. Alternatively or additionally, there may be a safety interlock, e.g. an operator confirmation.

0155According to some example embodiments, a secure vehicle network may automate a transition from the first grain cart 1420's departure and the second grain cart's 1460 arrival. For example, there may be a synchronous departure.

0156According to some example embodiments, the first grain cart 1420 may return, having unloaded the grain. The first grain cart 1420 may try to establish a secure vehicle network with one or more vehicles in the system. The first grain cart may have been kept in a cache in components of the secure vehicle networks while the first grain cart 1420 was away unloading grain. For example, a key previously established between the first grain cart 1420 and other vehicles may still be valid and reused, rather than using the method described in <figref idref="f0001">FIG. 1</figref> to reestablish the secure vehicle network.

0157<figref idref="f0018">FIG. 8</figref> shows example agricultural vehicles according to an example embodiment.

0158As shown in <figref idref="f0018">FIG. 8</figref>, a tractor 800 may drive a planter 850. The planter 850 may include a plurality of rows 850a, 850b, 850z.

0159The tractor 800 may include a plurality of electronic components. Each of the plurality of rows 850a, 850b, 850z may include one of, or a plurality of electronic components.

0160The plurality of electronic components included in the plurality of rows 850a, 850b, 850z may engage in the method illustrated in <figref idref="f0001">FIG. 1</figref> to establish an intra-vehicle secure network. After establishing the vehicle secure network, one of the plurality of electronic components included in the plurality of rows 850a, 850b, 850z may have a value corresponding to "leader" in the leader/follower field, while the other of the plurality of electronic components included in the plurality of rows 850a, 850b, 850z may have a value corresponding to "follower" in the leader/follower field.

0161The tractor 800 and the planter 850 may engage in the methods illustrated in <figref idref="f0013 f0014 f0015 f0016 f0017">FIGS. 6(a)-7(b)</figref> to communicate in an inter-vehicle secure network.

0162One of the plurality of electronic components included in the tractor 800 may communicate with one of the plurality of electronic components included in the planter 850, informing the planter of the speed of the tractor.

0163The electronic component included in the planter 850 that receives communication from the tractor 800 may broadcast the speed of the tractor to other electronic components included in the planter 850, to inform the rows 850a, 850b, 850z of the planter 850 how fast to dispense seed.

0164<figref idref="f0019">FIG. 9</figref> is a representative drawing illustrating a system including a satellite and a vehicle, according to some example embodiments, according to some example embodiments.

0165As illustrated in <figref idref="f0019">FIG. 9</figref>, a vehicle 900 may include a location-determining receiver 910, a wireless transceiver 920, and a data processing system 960 including a path planner 950 and a guidance-tracker 970. The location-determining receiver 910, the wireless transceiver 920, and the data processing system 960 may be connected over a bus 901. The vehicle 900 may correspond to one or more of the vehicles as described with regards to <figref idref="f0016 f0017">FIGS. 7(a)-7(b)</figref>.

0166The location-determining receiver 910 may receive location information from a satellite 990. The location-determining receiver 910 may be or correspond to a satellite navigation receiver, such as a Global Navigation Satellite System (GNSS) receiver. The location information received from the satellite 990 may include at least one of position, velocity and heading data for the vehicle 900. The location-determining receiver 910 may also receive altitude information including at least one of roll angle, tilt angle, and yaw angle (heading) of the vehicle 900.The wireless transceiver 920 may enable communication with other vehicles in the vehicle secure network. For example, the vehicle 900 may correspond to the combine 1400 described above with reference to <figref idref="f0016">FIG. 7(a)</figref>, and may communicate over the wireless transceiver 920 with another vehicle, such as grain cart 1420, described above with reference to <figref idref="f0016">FIG. 7(a)</figref>, so as to coordinate respective guidance paths.

0167If the vehicle 900 is designated a leader, the vehicle 900 may track a lead path plan, whereas other follower vehicles may track a follower path plan. The follower path plan may be a derivative of the lead path plan.

0168The data processing system 960 may include one or more processors configured to execute machine-readable instructions that, when executed, cause the one or more processors to perform various actions. In some non-limiting example embodiments, the data processing system 960 may include the path planner 950 and the guidance tracker 970. The path planner 950 and the guidance tracker 970 may be embodied as hardware and/or software that, when executed by the one or more processors, cause the processor to perform various actions.

0169For example, the path planner 950 may determine the path plan, based on inputs received from the location-determining receiver 910. The guidance tracker 970 may track a path taken by the vehicle 900 in response to information received from the location-determining transceiver 910.

0170The data processing system may receive information from, and transmit information through, the wireless transceiver 920. For example, if the vehicle 900 corresponds to the combine 1400, then the vehicle 900 may communicate with the grain cart 1420 to track set and track paths.

0171Systems and methods for establishing a secure vehicle network according to example embodiments may be performed with reduced or minimized speed. Further, a number of independent verifications may be reduced or minimized while nodes perform verifications in parallel. Further, redundant vehicle messages may be reduced or minimized. Still further, the systems and methods are robust to situations when a vehicle, or components within a vehicle, are reset.

0172Example embodiments being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of example embodiments, and all such modifications as would be obvious to one of ordinary skill in the art are intended to be included within the scope of the claims.