Systems, methods, and apparatus for performing vehicle communications using area architecture

Abstract

An example method includes interpreting a vehicle network performance description; determining a regional architecture value in response to the vehicle network performance description and the vehicle performance network impact description; and integrating the multi-area network on the vehicle in response to the area architecture value.

Description

[0001] Cross - reference to related applications

[0002] This application claims priority to U.S. Patent Application No. 17 / 570,738 (SONA - 0007 - U01 - C01), entitled "SYSTEM, METHOD, AND APPARATUS TO EXTRAVEHICLE COMMUNICATIONS CONTROL", filed on January 7, 2022, and is a partial continuation of that patent application.

[0003] U.S. Patent Application No. 17 / 570,738 (SONA - 0007 - U01 - C01) is a continuation of U.S. Patent Application Serial No. 17 / 027,187 (SONA - 0007 - U01), entitled "SYSTEM, METHOD, AND APPARATUS TO EXTRA VEHICLE COMMUNICATIONS CONTROL", filed on September 21, 2020, and claims priority thereto, and is now issued as U.S. Patent 11,228,496.

[0004] Application 17 / 027,187 (SONA-0007-U01) claims the priority benefit of the following provisional applications: U.S. Application No. 62 / 903,462 (SONA-0001-P01), filed September 20, 2019, entitled "SYSTEM, METHOD AND APPARATUS FOR A MIXED VEHICLE NETWORK"; U.S. Application No. 62 / 911,249 (SONA-0002-P01), filed October 5, 2019, entitled "SYSTEM, METHOD AND APPARATUS FOR A MIXED VEHICLE NETWORK"; U.S. Application No. 62 / 911,248 (SONA-0003-P01), filed October 5, 2019, entitled "SYSTEM, METHOD AND APPARATUS FOR CLOUD-BASED INTERACTIONS WITH A MIXED VEHICLE NETWORK"; U.S. Application No. 62 / 986,444 (SONA-0004-P01), filed March 6, 2020, entitled "SYSTEM, METHOD AND APPARATUS FOR IMPLEMENTING CONFIGURABLE DATA COLLECTION FOR A VEHICLE"; and U.S. Application No. 63 / 024,383 (SONA-0005-P01), filed May 13, 2020, entitled "SYSTEM, METHOD AND APPARATUS TO TEST AND VERIFY A VEHICLE NETWORK".

[0005] This application claims the priority of U.S. Provisional Application Serial No. 63 / 404,918 (SONA-0015-P01), filed September 8, 2022, entitled "ZONAL ARCHITECTURE FOR A VEHICLE".

[0006] For all purposes, each of the foregoing applications is hereby incorporated by reference in its entirety. BACKGROUND OF THE INVENTION

[0007] Vehicles and mobile applications are increasingly relying on computing devices distributed around the vehicle to perform electronic control functions. For example, modern passenger vehicles typically have over 100 independent electronic control devices distributed around the vehicle. These devices cooperate and communicate with each other to perform various vehicle functions. Prior known systems typically connect devices on networks organized around specific vehicle functions. As a result, various networks are densely distributed around the vehicle, with multiple connection paths, which leads to much more hardware than is required to simply connect the devices (e.g., cables and routing devices). Vehicles are increasingly facing high design costs for integrating all the connections, as well as security risks from the various types of multiple networks that provide potential access points on the vehicle. Due to the dependence on electronic devices (which is expected to only increase) and the growth in the vehicle's ability to act autonomously and provide more and more capabilities to the electronic devices, the consequences of security vulnerabilities or other security issues on the vehicle are increasing. In addition, there is a range of devices and capabilities, from modern electronic devices that can communicate on high-speed networks using modern communications, to simple electronic devices that utilize older networks that can be based on very simple protocols or industrial standards.

[0008] Accordingly, vehicles have a wide variety of networks that have different security capabilities, multiple overlapping communication paths based on vehicle functions, and the consequent difficulties in designing, monitoring, or updating the various networks or the devices thereon. SUMMARY OF THE INVENTION

[0009] In some aspects, the techniques described herein relate to a system including: a vehicle having a multi-region network including a plurality of network regions, each network region including at least one region manager; wherein the plurality of network regions are arranged according to a network topology description of a selected region architecture; and a network management controller including: region implementation circuitry configured to interpret a partition architecture communication scheme; region manager command circuitry configured to, in response to the partition architecture communication scheme, interpret a region manager command description for each of the at least one region manager; and region execution circuitry configured to provide a corresponding region manager command description to each of the at least one region manager; and wherein each of the at least one region manager responds to the corresponding region manager command description to control communication between endpoints of the corresponding network region and endpoints of at least one other region among the plurality of network regions.

[0010] In some aspects, the techniques described herein relate to a system wherein the network topology description includes a communicatively coupled arrangement of a plurality of network regions.

[0011] In some aspects, the techniques described herein relate to a system wherein the network topology description includes a logically coupled arrangement of a plurality of network regions.

[0012] In some aspects, the techniques described herein relate to a system in which the region implementation circuitry is also configured to interpret a partitioned architecture communication scheme in response to a policy provided by an external device.

[0013] In some aspects, the techniques described herein relate to a system in which the policy includes a profile for network communication on a vehicle.

[0014] In some aspects, the techniques described herein relate to a system in which a network management controller is at least partially located on a central gateway regional controller, where the central gateway regional controller includes one of the regional managers.

[0015] In some aspects, the techniques described herein relate to a system in which the regional manager command circuitry is also configured to interpret a regional manager command description for each regional manager in at least one regional manager by parsing a policy that includes a profile.

[0016] In some aspects, the techniques described herein relate to a system in which the region execution circuitry is also configured to provide a corresponding regional manager command description to each regional manager by updating a local profile of each regional manager.

[0017] In some aspects, the techniques described herein relate to a system in which each corresponding regional manager command description includes at least one value selected from the following: a communication allowed value; a communication sampling rate value; a communication configuration value; or a communication destination value.

[0018] In some aspects, the techniques described herein relate to a system, the system further comprising: where the network management controller further includes hardware redundancy implementation circuitry configured to: determine that a hardware non-nominal event has occurred; and in response to the hardware non-nominal event, adjust at least one regional manager command description.

[0019] In some aspects, the techniques described herein relate to a system, the system further comprising: where the network management controller further includes control redundancy implementation circuitry configured to: determine that a control non-nominal event has occurred; and in response to the control non-nominal event, adjust at least one regional manager command description.

[0020] In some aspects, the techniques described herein relate to a method, including: interpreting a vehicle network performance description; determining a regional architecture value in response to the vehicle network performance description and a vehicle performance network impact description; and integrating a multi-regional network on the vehicle in response to the regional architecture value.

[0021] In some aspects, the techniques described herein relate to a method in which a vehicle network performance description includes at least one of the following: a latency value between at least two endpoints of a multi - area network; a bandwidth value between at least two endpoints of a multi - area network; a hardware redundancy description of a multi - area network; or a control redundancy description of a multi - area network.

[0022] In some aspects, the techniques described herein relate to a method in which a vehicle performance network impact description includes at least one of the following: an installed hardware cost value of a multi - area network; a task - ability description of a multi - area network; a redundancy - ability description of a multi - area network; or a reliability description of a multi - area network.

[0023] In some aspects, the techniques described herein relate to a method in which a regional architecture value includes a network topology description.

[0024] In some aspects, the techniques described herein relate to a method in which a regional architecture value further includes a regional manager distribution description.

[0025] In some aspects, the techniques described herein relate to a method in which a regional architecture value further includes a network type value for each region of a multi - area network.

[0026] In some aspects, the techniques described herein relate to a method in which a regional architecture value further includes a network protocol value for each region of a multi - area network.

[0027] In some aspects, the techniques described herein relate to a method in which a regional architecture value further includes a specification value of at least one hardware component of a multi - area network.

[0028] In some aspects, the techniques described herein relate to a method in which integrating a multi - area network on a vehicle includes installing a multi - area network configured according to the regional architecture value.

[0029] In some aspects, the techniques described herein relate to a method in which integrating a multi - area network on a vehicle includes installing a multi - area network configured according to the network topology description of the regional architecture value.

[0030] In some aspects, the techniques described herein relate to a method in which integrating a multi - area network on a vehicle includes installing a multi - area network configured according to the regional manager distribution description of the regional architecture value.

[0031] In some aspects, the techniques described herein relate to a method that includes: interpreting a plurality of vehicle network performance descriptions, each vehicle network performance description corresponding to one of a plurality of selected vehicle classes; determining a regional architecture value in response to the plurality of vehicle network performance descriptions and a vehicle performance network impact description for each of the plurality of selected vehicle classes; and integrating a multi-regional network on each of a first vehicle and a second vehicle in response to the regional architecture value, where the first vehicle includes a member of a first one of the plurality of selected vehicle classes and where the second vehicle includes a member of a second one of the plurality of selected vehicle classes.

[0032] In some aspects, the techniques described herein relate to a method where each of the plurality of vehicle network performance descriptions includes at least one of the following: a latency value between at least two endpoints of a multi-regional network corresponding to one of the plurality of selected vehicle classes; a bandwidth value between at least two endpoints of a multi-regional network corresponding to one of the plurality of selected vehicle classes; a hardware redundancy description of a multi-regional network corresponding to one of the plurality of selected vehicle classes; or a control redundancy description of a multi-regional network corresponding to one of the plurality of selected vehicle classes.

[0033] In some aspects, the techniques described herein relate to a method where the vehicle performance network impact description corresponding to each of the plurality of selected vehicle classes includes at least one of the following: an installed hardware cost value of a multi-regional network corresponding to one of the plurality of selected vehicle classes; a task capability description of a multi-regional network corresponding to one of the plurality of selected vehicle classes; a redundancy capability description of a multi-regional network corresponding to one of the plurality of selected vehicle classes; or a reliability description of a multi-regional network corresponding to one of the plurality of selected vehicle classes.

[0034] In some aspects, the techniques described herein relate to a method where the regional architecture value includes a network topology description.

[0035] In some aspects, the techniques described herein relate to a method where the regional architecture value further includes a regional manager distribution description.

[0036] In some aspects, the techniques described herein relate to a method where integrating a multi-regional network on each of the first vehicle and the second vehicle includes installing a multi-regional network configured according to the regional architecture value on each of the first vehicle and the second vehicle.

[0037] In some aspects, the techniques described herein relate to a method where integrating a multi-regional network on each of the first vehicle and the second vehicle includes installing a multi-regional network configured according to the network topology description of the regional architecture value on each of the first vehicle and the second vehicle.

[0038] In some aspects, the techniques described herein relate to a method in which a multi - area network integrated on each of a first vehicle and a second vehicle includes installing, on each of the first vehicle and the second vehicle, a multi - area network configured according to a distribution description of area managers based on area architecture values.

[0039] In some aspects, the techniques described herein relate to a system including: a vehicle having a multi - area network including a plurality of network areas, each network area including at least one area manager; wherein the plurality of network areas are arranged according to a network topology description of a selected area architecture, the selected area architecture being determined in response to a vehicle network risk description and a vehicle performance network impact description; and a network management controller including: area implementation circuitry configured to interpret a partitioned architecture communication scheme; area manager command circuitry configured to interpret, in response to the partitioned architecture communication scheme, an area manager command description for each of the at least one area manager; and area execution circuitry configured to provide a corresponding area manager command description to each of the at least one area manager; and wherein each of the at least one area manager controls communication between endpoints of a corresponding network area and endpoints of at least one other area among the plurality of network areas in response to the corresponding area manager command description.

[0040] In some aspects, the techniques described herein relate to a system in which the selected area architecture includes a star arrangement, in which one of the plurality of network areas includes a central area having a central area manager.

[0041] In some aspects, the techniques described herein relate to a system in which the plurality of network areas further include: two forward areas, each communicatively coupled to the central area; and one rearward area communicatively coupled to the central area.

[0042] In some aspects, the techniques described herein relate to a system in which the selected area architecture includes a mesh area arrangement.

[0043] In some aspects, the techniques described herein relate to a system in which the plurality of network areas further include: two forward areas; one central area; one rearward area; and wherein each of the plurality of network areas is communicatively coupled to all other network areas of the plurality of network areas.

[0044] In some aspects, the techniques described herein relate to a system in which the selected area architecture includes a ring area arrangement.

[0045] In some aspects, the techniques described herein relate to a system in which multiple network regions further include, in sequence: a central region having a central region manager and communicatively coupled to a first forwarding region; a first forward region communicatively coupled to a second forward region; a second forward region communicatively coupled to a backward region; and a backward region communicatively coupled to the central region.

[0046] In some aspects, the techniques described herein relate to a system in which a selected region architecture includes a two-node topology, where each node of the two-node topology corresponds to one of the multiple network regions.

[0047] In some aspects, the techniques described herein relate to a system in which a selected region architecture includes a three-node topology, where each node of the three-node topology corresponds to one of the multiple network regions.

[0048] In some aspects, the techniques described herein relate to a system in which a selected region architecture includes a four-node topology, where each node of the four-node topology corresponds to one of the multiple network regions.

[0049] In some aspects, the techniques described herein relate to a system in which at least one of the multiple regions includes a virtual network region.

[0050] In some aspects, the techniques described herein relate to a method including: interpreting a vehicle network risk description; determining a region architecture value in response to the vehicle network risk description and a vehicle performance network impact description; and integrating a multi-region network on the vehicle in response to the region architecture value.

[0051] In some aspects, the techniques described herein relate to a method in which the vehicle network risk description includes a hardware redundancy value.

[0052] In some aspects, the techniques described herein relate to a method in which the vehicle network risk description includes a control redundancy value.

[0053] In some aspects, the techniques described herein relate to a method in which the vehicle network risk description includes a critical process description.

[0054] In some aspects, the techniques described herein relate to a method in which the vehicle network risk description includes a critical application description.

[0055] In some aspects, the techniques described herein relate to a method in which the vehicle network risk description includes a critical communication connection description.

[0056] In some aspects, the techniques described herein relate to a method in which the vehicle network risk description includes a failure mode description.

[0057] In some aspects, the techniques described herein relate to a method in which a vehicle performance network impact description includes a performance estimate of a multi-region network including a vehicle network risk description.

[0058] In some aspects, the techniques described herein relate to a system including: a vehicle having a multi-region network including a plurality of network regions, each network region including at least one region manager, and wherein one of the at least one region managers includes a central region manager; wherein the plurality of network regions are arranged according to a network topology description of a selected region architecture, and wherein the central region manager is directly communicatively coupled to each other region manager; and a network management controller including: a region implementation circuit configured to interpret a partitioned architecture communication scheme; a region manager command circuit configured to interpret, in response to the partitioned architecture communication scheme, a region manager command description for each of the at least one region managers; and a region execution circuit configured to provide a corresponding region manager command description to each of the at least one region managers; and wherein each of the at least one region managers responds to the corresponding region manager command description to control communication between endpoints of a corresponding network region and endpoints of at least one other region among the plurality of network regions.

[0059] In some aspects, the techniques described herein relate to a system in which the network management controller is at least partially located on the central region manager.

[0060] In some aspects, the techniques described herein relate to a system further including: wherein the partitioned architecture communication scheme further includes a central region manager succession scheme; and wherein the region execution circuit is further configured to determine a non-nominal condition of the central region manager and, in response to the central region manager succession scheme, migrate the central region manager responsibilities to another one of the at least one region managers.

[0061] In some aspects, the techniques described herein relate to a system in which the non-nominal condition includes a lost communication condition.

[0062] In some aspects, the techniques described herein relate to a system in which the non-nominal condition includes at least one of a loss or degradation of a network region associated with the central region manager.

[0063] In some aspects, the techniques described herein relate to a system in which the network topology description includes a communicatively coupled arrangement of a plurality of network regions.

[0064] In some aspects, the techniques described herein relate to a system in which the communicatively coupled arrangement includes a star arrangement.

[0065] In some aspects, the techniques described herein relate to a system in which a central area manager includes a central node arranged in a star configuration.

[0066] In some aspects, the techniques described herein relate to a system in which a communicatively coupled arrangement includes a mesh arrangement.

[0067] In some aspects, the techniques described herein relate to a system in which a communicatively coupled arrangement includes a ring arrangement.

[0068] In some aspects, the techniques described herein relate to a method that includes: interpreting a partitioned architecture communication scheme for a vehicle having a multi-area network that includes a plurality of network areas, each network area including at least one area manager, and wherein one of the at least one area managers includes a central area manager; in response to the partitioned architecture communication scheme, interpreting an area manager command description for each of the at least one area managers; providing a corresponding area manager command description to each of the at least one area managers; and in response to the corresponding area manager command description, operating each of the at least one area managers to control communication between endpoints of a corresponding network area and endpoints of at least one other area among the plurality of network areas.

[0069] In some aspects, the techniques described herein relate to a method that further includes where interpreting the area manager command description further includes interpreting a central area manager command description for the central area manager.

[0070] In some aspects, the techniques described herein relate to a method that further includes: interpreting a central area manager succession scheme; determining a non-nominal condition of the central area manager; and in response to the central area manager succession scheme, migrating central area manager responsibilities to another area manager among the at least one area managers.

[0071] In some aspects, the techniques described herein relate to a system that includes: a vehicle having a multi-region network that includes a plurality of network regions, each network region including at least one region manager, and wherein one of the at least one region managers includes a central region manager; wherein the plurality of network regions are arranged according to a network topology description of a selected region architecture; and wherein the central region manager includes a network management controller that includes: a region implementation circuit configured to interpret a partition architecture communication scheme, wherein the partition architecture communication scheme includes a network security description and a network connectivity description; a region manager command circuit configured to, in response to the partition architecture communication scheme, interpret a region manager command description for each of the at least one region managers; and a region execution circuit configured to provide a corresponding region manager command description to each of the at least one region managers; and wherein each of the at least one region managers responds to the corresponding region manager command description to control communication between endpoints of the corresponding network region and endpoints of at least one other region among the plurality of network regions.

[0072] In some aspects, the techniques described herein relate to a system in which the central region manager is directly communicatively coupled to each other region manager.

[0073] In some aspects, the techniques described herein relate to a system that further includes: wherein the region implementation circuit is further configured to interpret a partition architecture communication scheme update; wherein the region manager command circuit is further configured to, in response to the updated partition architecture communication scheme, interpret the region manager command description for each region manager of the at least one region managers; and wherein the region execution circuit is further configured to provide a corresponding updated region manager command description to each of the at least one region managers.

[0074] In some aspects, the techniques described herein relate to a system that further includes wherein the region implementation circuit is further configured to interpret a partition architecture communication scheme update by receiving a policy from an external device.

[0075] In some aspects, the techniques described herein relate to a system in which the network security description includes a permission value associated with at least one of the following: a network region among the plurality of network regions; traffic of the vehicle; an application of the vehicle; a function of the vehicle; or an endpoint of one of the plurality of network regions.

[0076] In some aspects, the techniques described herein relate to a system in which the permission value includes at least one permission selected from the following: a communication bandwidth permission; a data provider permission; a data receiver permission; a service subscription permission; a service provider permission; a service visibility permission; a service publication permission; or an endpoint communication permission.

[0077] In some aspects, the techniques described herein relate to a system in which a network connectivity description includes a connectivity scheme between at least two of a plurality of network regions.

[0078] In some aspects, the techniques described herein relate to a system in which the connectivity scheme defines at least one of the following: a communication rate value; a communication protocol value; a communication encapsulation description; a sampling rate value; a communication header value; a communication metadata value; a communication unit value; or a communication timestamp description.

[0079] In some aspects, the techniques described herein relate to a system in which the network connectivity description further includes a connectivity scheme based on at least one of an origin endpoint value or a destination endpoint value.

[0080] In some aspects, the techniques described herein relate to a system in which the network connectivity description further includes a connectivity scheme based on at least one of an origin network type or a destination network type.

[0081] In some aspects, the techniques described herein relate to a method including: interpreting a partitioned architecture communication scheme for a multi-region network of a vehicle including a plurality of network regions, each network region including at least one region manager and wherein one of the at least one region managers includes a central region manager, the partitioned architecture communication scheme including a network security description and a network connectivity description; in response to the partitioned architecture communication scheme, interpreting a region manager command description for each of the at least one region managers; providing a corresponding region manager command description to each of the at least one region managers; and in response to the region manager command description, controlling communication between endpoints of each of the plurality of network regions.

[0082] In some aspects, the techniques described herein relate to a method in which interpreting the partitioned architecture communication scheme includes receiving a policy at the central region manager from an external device.

[0083] In some aspects, the techniques described herein relate to a method in which interpreting the region manager command description includes parsing the policy and determining a relevant region manager command description for each of the plurality of region managers in response to the policy.

[0084] In some aspects, the techniques described herein relate to a method in which providing a corresponding region manager command description includes transmitting the corresponding region manager command description from the central region manager to each individual region manager of the plurality of region managers.

[0085] In some aspects, the techniques described herein relate to a method, further comprising: interpreting a partitioned architecture communication scheme update; in response to the updated partitioned architecture communication scheme, interpreting a zone manager command description for each of the at least one zone manager; and providing a corresponding updated zone manager command description to each of the at least one zone manager.

[0086] In some aspects, the techniques described herein relate to a method, further comprising controlling communication between endpoints in each of a plurality of network zones in response to an updated zone manager command description.

[0087] In some aspects, the techniques described herein relate to a method, further comprising controlling communication in response to an updated zone manager command description immediately after the update.

[0088] In some aspects, the techniques described herein relate to a method, further comprising controlling communication in response to an updated zone manager command description in response to a subsequent vehicle start event.

[0089] In some aspects, the techniques described herein relate to a method, further comprising determining an implementation scheme in response to an updated zone manager command description, and further controlling communication in response to the updated zone manager command description in response to the implementation scheme.

[0090] In some aspects, the techniques described herein relate to a method, wherein the implementation scheme includes at least one of a runtime scheme, a startup scheme, or a hybrid scheme.

[0091] In some aspects, the techniques described herein relate to a system, comprising: a vehicle having a multi-zone network including a plurality of network zones, each network zone including at least one zone manager; wherein the plurality of network zones are arranged according to a network topology description of a selected zone architecture; and a network management controller, comprising: a zone implementation circuit configured to interpret a partitioned architecture communication scheme, wherein the partitioned architecture communication scheme includes a network security description and a network connectivity description; a zone manager command circuit configured to, in response to the partitioned architecture communication scheme, interpret a zone manager command description for each of the at least one zone manager; and a zone execution circuit configured to provide a corresponding zone manager command description to each of the at least one zone manager; and wherein each of the at least one zone manager controls cross-zone communication in response to the corresponding zone manager command description, the cross-zone communication including communication zones of the multi-zone network.

[0092] In some aspects, the techniques described herein relate to a system, further comprising wherein the network connectivity description includes a bandwidth description between two zones of the plurality of network zones.

[0093] In some aspects, the techniques described herein relate to a system in which a bandwidth description is further defined in response to at least one element involved in cross-region communication, where the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0094] In some aspects, the techniques described herein relate to a system further including a network connectivity description including a network routing value for cross-region communication.

[0095] In some aspects, the techniques described herein relate to a system in which a network routing value is further defined in response to at least one element involved in cross-region communication, where the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0096] In some aspects, the techniques described herein relate to a system in which a network connectivity description further includes a priority value for cross-region communication.

[0097] In some aspects, the techniques described herein relate to a system in which a priority value is further defined in response to at least one element involved in cross-region communication, where the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0098] In some aspects, the techniques described herein relate to a system in which a priority value is further defined in response to an operating condition of a vehicle.

[0099] In some aspects, the techniques described herein relate to a system in which a network security description includes a permission value for cross-region communication.

[0100] In some aspects, the techniques described herein relate to a system in which a permission value is further defined in response to at least one element involved in cross-region communication, where the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0101] In some aspects, the techniques described herein relate to a system in which the permission value includes at least one of a sampling rate description, a data resolution description, or a data latency description.

[0102] In some aspects, the techniques described herein relate to a system in which a permission value is further defined in response to at least one element involved in cross-region communication, where the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0103] In some aspects, the techniques described herein relate to a system in which a permission value is further defined in response to an operating condition of a vehicle.

[0104] In some aspects, the techniques described herein relate to a method, including: interpreting a partitioned architecture communication scheme for a multi-region network of a vehicle including a plurality of network regions, each network region including at least one region manager, wherein the partitioned architecture communication scheme includes a network security description and a network connectivity description; in response to the partitioned architecture communication scheme, interpreting a region manager command description for each of the at least one region manager; providing the corresponding region manager command description to each of the at least one region manager; and in response to the region manager command description, controlling cross-region communication between network regions in the plurality of network regions.

[0105] In some aspects, the techniques described herein relate to a method, wherein the network connectivity description includes a bandwidth description between two regions in the plurality of network regions, and the method further includes determining the bandwidth description in response to at least one element involved in the cross-region communication, wherein the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0106] In some aspects, the techniques described herein relate to a method, wherein the network connectivity description includes a network routing value for cross-region communication, and the method further includes determining the network routing value in response to at least one element involved in the cross-region communication, wherein the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0107] In some aspects, the techniques described herein relate to a method, wherein the network connectivity description includes a priority value for cross-region communication, and the method further includes determining the priority value in response to at least one element involved in the cross-region communication, wherein the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0108] In some aspects, the techniques described herein relate to a method, wherein the network connectivity description includes a priority value for cross-region communication, and the method further includes determining the priority value in response to the operating condition of the vehicle.

[0109] In some aspects, the techniques described herein relate to a method, wherein the network connectivity description includes a permission value for cross-region communication, and the method further includes determining the permission value in response to at least one element involved in the cross-region communication, wherein the at least one element includes at least one of an endpoint, a flow, a function, or an application.

[0110] In some aspects, the techniques described herein relate to a method, wherein the network connectivity description includes a permission value for cross-region communication, and the method further includes determining the permission value in response to the operating condition of the vehicle.

[0111] In some aspects, the techniques described herein relate to a system including: a vehicle having a multi-zone network including a plurality of network zones, each network zone including at least one zone manager; wherein the plurality of network zones are arranged according to a network topology description of a selected zone architecture; and a service management controller including: a service registration circuit configured to maintain a service registry including a plurality of services and service descriptions for each of the plurality of services; a service publishing circuit configured to, in response to a service publish request, present to a requester source at least one service from the plurality of services; a service subscription circuit configured to register a requester source with the at least one service in response to a service subscription request and update the service registry in response to the registration; a network management controller including: a zone implementation circuit configured to interpret a partitioned architecture communication scheme; a zone manager command circuit configured to, in response to the partitioned architecture communication scheme, interpret a zone manager command description for each of the at least one zone managers; and a zone execution circuit configured to provide a corresponding zone manager command description to each of the at least one zone managers; and wherein each of the at least one zone managers responds to the corresponding zone manager command description and the service registry to control communication between endpoints of the corresponding network zone and endpoints of at least one other zone among the plurality of network zones.

[0112] In some aspects, the techniques described herein relate to a system in which the service management controller is at least partially located on a central zone manager of the plurality of zone managers.

[0113] In some aspects, the techniques described herein relate to a system in which the central zone manager is directly communicatively coupled to each other zone manager.

[0114] In some aspects, the techniques described herein relate to a system in which the network management controller is at least partially located on a central zone manager of the plurality of zone managers.

[0115] In some aspects, the techniques described herein relate to a system in which the central zone manager is directly communicatively coupled to each other zone manager.

[0116] In some aspects, the techniques described herein relate to a system in which each of the plurality of services includes at least one of the following: a data value; a mathematical function; a processing function; a communication function; or a data storage function.

[0117] In some aspects, the techniques described herein relate to a system in which each of the plurality of services includes at least one of the following: an actuator function; a command function; or a control function.

[0118] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to expose at least one service by listing the service in a data structure provided to a requester source.

[0119] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to expose at least one service by listing the service in a data structure available to a requester source.

[0120] In some aspects, the techniques described herein relate to a system in which the requester source includes an external device.

[0121] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to: interpret a service publishing request for a new service from a new service provider; determine a new service description in response to the service publishing request and the new service provider; and maintain a service registry by adding the new service as one of a plurality of services.

[0122] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to add a new service in response to a permission value associated with the new service provider.

[0123] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to maintain a service registry by removing a service from a plurality of services in response to a service publishing request.

[0124] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to remove the service from a plurality of services by deleting an associated entry from the service registry.

[0125] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to remove the service from a plurality of services by setting an inactive flag in an associated entry from the service registry.

[0126] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to maintain a service registry by deprecating a service from a plurality of services in response to a service publishing request.

[0127] In some aspects, the techniques described herein relate to a system in which a service subscription circuit is also configured to block new subscriptions to a deprecated service.

[0128] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to maintain a service registry by removing the service from a plurality of services in response to determining that at least one aspect of the service is no longer available.

[0129] In some aspects, the techniques described herein relate to a system in which a service publishing circuit is also configured to remove the service from a plurality of services by setting an inactive flag in an associated entry in a service registry.

[0130] In some aspects, the techniques described herein relate to a system in which, for each service of a plurality of services, the service registry includes at least one of the following: a service identifier; a service provider description; a service license description; or a service capability description.

[0131] In some aspects, the techniques described herein relate to a system in which, for each service of a plurality of services, the service registry further includes at least one of the following: a service input description; a service active or inactive flag; a service deprecation flag; a service registrar description; or a service participant description.

[0132] In some aspects, the techniques described herein relate to a system in which the service license description includes at least one of the following: a service publishing license; a service subscription license; or a service visibility license.

[0133] In some aspects, the techniques described herein relate to a system further including storing the service registry on an external device.

[0134] In some aspects, the techniques described herein relate to a method including: maintaining, on a vehicle having a multi-region network including a plurality of network regions, a service registry including a plurality of services and service descriptions for each of the plurality of services, each network region including at least one region manager, wherein the plurality of network regions are arranged according to a network topology description of a selected region architecture; in response to a service publishing request, presenting at least one service from the plurality of services to a requester source; in response to a service subscription request, registering the at least one service with a requester source, and in response to the registration, updating the service registry; interpreting a partitioned architecture communication scheme; in response to the partitioned architecture communication scheme, interpreting a region manager command description for each of the at least one region manager; providing a corresponding region manager command description to each of the at least one region manager; and in response to the corresponding region manager command description and the service registry, controlling communication between endpoints of a corresponding network region and endpoints of at least one other region of the plurality of network regions.

[0135] In some aspects, the techniques described herein relate to a method further including presenting at least one service by listing the service in a data structure provided to a requester source.

[0136] In some aspects, the techniques described herein relate to a method further including presenting at least one service by listing the service in a data structure available to a requester source.

[0137] In some aspects, the techniques described herein relate to a method that further includes: interpreting a service publishing request for a new service from a new service provider; determining a new service description in response to the service publishing request and the new service provider; and maintaining a service registry by adding the new service as one of a plurality of services.

[0138] In some aspects, the techniques described herein relate to a method that further includes adding a new service in response to a permission value associated with the new service provider.

[0139] In some aspects, the techniques described herein relate to a method that further includes maintaining a service registry by removing a service from a plurality of services in response to a service publishing request.

[0140] In some aspects, the techniques described herein relate to a method that further includes removing the service from the plurality of services by deleting an associated entry from the service registry.

[0141] In some aspects, the techniques described herein relate to a method that further includes removing the service from the plurality of services by setting an inactive flag in an associated entry from the service registry.

[0142] In some aspects, the techniques described herein relate to a method that further includes maintaining a service registry by deprecating a service from a plurality of services in response to a service publishing request.

[0143] In some aspects, the techniques described herein relate to a method that further includes preventing new registrations for a deprecated service.

[0144] In some aspects, the techniques described herein relate to a method that further includes maintaining a service registry by removing a service from a plurality of services in response to determining that at least one aspect of the service is no longer available.

[0145] In some aspects, the techniques described herein relate to a method that further includes removing the service from the plurality of services by setting an inactive flag in an associated entry from the service registry.

[0146] In some aspects, the techniques described herein relate to a system including: a vehicle having a multi-zone network including a plurality of network zones, each network zone including at least one zone manager; a network management controller including: a zone implementation circuit configured to interpret a partitioned architecture communication scheme, the partitioned architecture communication scheme including a time management scheme; a zone manager command circuit configured to interpret, in response to the partitioned architecture communication scheme, a zone manager command description for each of the at least one zone manager, the zone manager command description further including a time management implementation; and a zone execution circuit configured to provide a corresponding zone manager command description to each of the at least one zone manager; and wherein each of the at least one zone manager responds to the corresponding zone manager command description to control communication between endpoints of a corresponding network zone and endpoints of at least one other zone among the plurality of network zones.

[0147] In some aspects, the techniques described herein relate to a system wherein the time management scheme further includes designating one of the at least one zone manager as a Precision Time Protocol (PTP) grandmaster operation for the multi-zone network.

[0148] In some aspects, the techniques described herein relate to a system wherein the other zone managers are designated as boundary clocks for corresponding network zones.

[0149] In some aspects, the techniques described herein relate to a system wherein the zone implementation circuit is further configured to operate a best master clock algorithm to determine one of the at least one zone manager as a PTP grandmaster operation.

[0150] In some aspects, the techniques described herein relate to a system further including: wherein the zone execution circuit is further configured to determine a PTP grandmaster timing event; and wherein, the zone implementation circuit is further configured to operate a best master clock algorithm to determine an alternate zone manager among the at least one zone manager as a PTP grandmaster operation; and wherein the zone execution circuit is further configured to designate the alternate zone manager among the at least one zone manager as a PTP grandmaster to operate.

[0151] In some aspects, the techniques described herein relate to a system wherein one of the zone managers includes a central zone manager, and wherein the central zone manager is designated as a PTP grandmaster.

[0152] In some aspects, the techniques described herein relate to a system further including: wherein, the zone execution circuit is further configured to determine a PTP grandmaster timing event and, in response to the PTP grandmaster timing event, designate an alternate zone manager among the zone managers as a PTP grandmaster.

[0153] In some aspects, the techniques described herein relate to a system in which a time management scheme also includes a designated controller including an endpoint on one of a plurality of network regions to operate as a Precision Time Protocol (PTP) grandmaster for a multi-region network.

[0154] In some aspects, the techniques described herein relate to a system in which one of the plurality of network regions includes a central network region.

[0155] In some aspects, the techniques described herein relate to a system in which a time management scheme also includes a designated boundary controller for each of the other network regions of the plurality of network regions, where each designated boundary controller includes an endpoint on a corresponding network region and operates as a boundary clock for the corresponding network region.

[0156] In some aspects, the techniques described herein relate to a system in which a time management scheme also includes a primary network region and a designated controller, the designated controller including a regional controller of the primary network region or one of the endpoints on the primary network region, where the designated controller operates as a Precision Time Protocol (PTP) grandmaster for a multi-region network.

[0157] In some aspects, the techniques described herein relate to a system in which the primary network region is selected based on the criticality of the function of at least one endpoint on the primary network region.

[0158] In some aspects, the techniques described herein relate to a system in which the primary network region is selected based on the time sensitivity of the function of at least one endpoint on the primary network region.

[0159] In some aspects, the techniques described herein relate to a system in which the regional controller is also configured to apply a common PTP timestamp to at least a portion of the communications provided on a corresponding one of the plurality of network regions.

[0160] In some aspects, the techniques described herein relate to a system in which the regional controller is also configured to remove local timestamps from at least a portion of the communications provided on a corresponding one of the plurality of network regions.

[0161] In some aspects, the techniques described herein relate to a system in which the regional controller is also configured to facilitate applying a common PTP timestamp to at least a portion of the communications provided on a corresponding one of the plurality of network regions.

[0162] In some aspects, the techniques described herein relate to a system in which the regional controller is also configured to facilitate removing local timestamps from at least a portion of the communications provided on a corresponding one of the plurality of network regions.

[0163] In some aspects, the techniques described herein relate to a system where the partitioned architecture communication scheme further includes a communication priority scheme.

[0164] In some aspects, the techniques described herein relate to a system where each of at least one zone manager controls communication between endpoints of a corresponding network zone and endpoints of at least one other zone among a plurality of network zones in response to a communication priority value and a communication priority scheme.

[0165] In some aspects, the techniques described herein relate to a system where the communication priority scheme includes a network routing value.

[0166] In some aspects, the techniques described herein relate to a system where the communication priority scheme includes a communication scheduling value.

[0167] In some aspects, the techniques described herein relate to a system where each of at least one zone manager further controls communication between endpoints of a corresponding network zone and endpoints of at least one other zone among a plurality of network zones in response to a vehicle operating condition.

[0168] In some aspects, the techniques described herein relate to a method including: interpreting a partitioned architecture communication scheme for a multi-zone network of a vehicle including a plurality of network zones, each network zone including at least one zone manager, where the partitioned architecture communication scheme includes a time management scheme; in response to the partitioned architecture communication scheme, interpreting a zone manager command description for each of the at least one zone manager, the zone manager command description further including a time management implementation; providing the corresponding zone manager command description to each of the at least one zone manager; and in response to the zone manager command description, controlling communication between endpoints of a corresponding network zone and endpoints of at least one other zone among a plurality of network zones.

[0169] In some aspects, the techniques described herein relate to a method further including designating one of the at least one zone manager to operate as a Precision Time Protocol (PTP) grandmaster for the multi-zone network.

[0170] In some aspects, the techniques described herein relate to a method further including designating other zone managers as boundary clocks for corresponding network zones.

[0171] In some aspects, the techniques described herein relate to a method where designating one of the at least one zone manager to operate as a PTP grandmaster includes operating a best master clock algorithm.

[0172] In some aspects, the techniques described herein relate to a method that further includes: determining a PTP master clock loss of time event; and operating a best master clock algorithm to designate an alternate domain manager in at least one domain manager as the PTP master clock operation.

[0173] In some aspects, the techniques described herein relate to a method that further includes: one of the domain managers includes a central domain manager; and designating the central domain manager as the PTP master clock.

[0174] In some aspects, the techniques described herein relate to a method that further includes: determining a PTP master clock loss of time event; and in response to the PTP master clock loss of time event, designating an alternate domain manager in the domain manager as the PTP master clock.

[0175] In some aspects, the techniques described herein relate to a method, wherein the time management scheme further includes a master network domain, and the method further includes selecting a designated controller, the designated controller including a domain controller of the master network domain or one of the endpoints on the master network domain, and operating the designated controller as a Precision Time Protocol (PTP) master clock for a multi-domain network.

[0176] In some aspects, the techniques described herein relate to a method that further includes selecting a master network domain based on the criticality of the functions of at least one endpoint on the master network domain.

[0177] In some aspects, the techniques described herein relate to a method that further includes selecting a master network domain based on the time sensitivity of the functions of at least one endpoint on the master network domain.

[0178] In some aspects, the techniques described herein relate to a method that further includes applying a common PTP timestamp to at least a portion of the communications provided on a multi-domain network.

[0179] In some aspects, the techniques described herein relate to a method that further includes removing local timestamps from at least a portion of the communications provided on a multi-domain network.

[0180] In some aspects, the techniques described herein relate to a method that further includes: wherein the partitioned architecture communication scheme further includes a communication priority scheme; determining a communication priority value for communications on a multi-domain network; and in response to the communication priority scheme and the communication priority value, controlling the communications on the multi-domain network.

[0181] In some aspects, the techniques described herein relate to a method, wherein controlling the communications includes adjusting network routing values in response to the communication priority value.

[0182] In some aspects, the techniques described herein relate to a method, wherein controlling the communications includes adjusting communication scheduling values in response to the communication priority value.

[0183] In some aspects, the techniques described herein relate to a method in which controlling communications includes adjusting at least one of a communication priority scheme or a communication priority value in response to a vehicle operating condition.

[0184] In some aspects, the techniques described herein relate to a system including: a vehicle multi-zone architecture configuration platform including: a build environment circuit configured to provide a virtual network build environment to a user interface; a network modeling circuit configured to build a virtual multi-zone network model of a vehicle in response to user input on the user interface, the virtual multi-zone network model including zone controllers located on each zone of the virtual multi-zone network model; an endpoint modeling circuit configured to populate the virtual multi-zone network model with endpoints based on a vehicle control model; wherein the network modeling circuit is further configured to build the virtual multi-zone network model by applying a partitioned architecture communication scheme; a network execution circuit configured to simulate runtime operation of the vehicle's multi-zone network in response to the virtual multi-zone network model, the vehicle control model, and the partitioned architecture communication scheme; and a partitioned architecture evaluation circuit configured to provide a network operation report in response to the simulation.

[0185] In some aspects, the techniques described herein relate to a system in which the partitioned architecture communication scheme includes at least one of a network security description, a network connectivity description, a time management scheme, or a communication priority scheme.

[0186] In some aspects, the techniques described herein relate to a system in which the vehicle control model includes a model of endpoints of a multi-zone network that simulates vehicle control operations.

[0187] In some aspects, the techniques described herein relate to a system in which the vehicle control model includes a model of endpoints of a multi-zone network that operates actual vehicle control instructions.

[0188] In some aspects, the techniques described herein relate to a system in which the network execution circuit is further configured to simulate runtime operation of the multi-zone network by simulating non-nominal conditions.

[0189] In some aspects, the techniques described herein relate to a system in which the network execution circuit is further configured to simulate non-nominal conditions by simulating at least one condition selected from: endpoint loss, network component loss, a selected vehicle operating condition, or a selected operator behavior.

[0190] In some aspects, the techniques described herein relate to a system in which the network modeling circuit is further configured to build the virtual multi-zone network model of the vehicle by applying a network topology description.

[0191] In some aspects, the techniques described herein relate to a system in which applying a network topology description includes applying a selected network topology for regions of a multi-region network and assigning region controllers to regions of the multi-region network.

[0192] In some aspects, the techniques described herein relate to a system in which applying a network topology description includes applying the network topology description in response to user input on a user interface.

[0193] In some aspects, the techniques described herein relate to a system in which a network operation report includes an operation capability value.

[0194] In some aspects, the techniques described herein relate to a system in which a network operation report includes a vehicle network performance description.

[0195] In some aspects, the techniques described herein relate to a system in which the vehicle network performance description includes at least one of the following: a latency value between at least two endpoints of a multi-region network; a bandwidth value between at least two endpoints of a multi-region network; a hardware redundancy description of the multi-region network; or a control redundancy description of the multi-region network.

[0196] In some aspects, the techniques described herein relate to a system in which a network operation report includes a vehicle performance network impact description.

[0197] In some aspects, the techniques described herein relate to a system in which the vehicle performance network impact description includes at least one of the following: an installed hardware cost value of a multi-region network; a task capability description of the multi-region network; an integration cost description of the multi-region network; an operation cost description of the multi-region network; a redundancy capability description of the multi-region network; or a reliability description of the multi-region network.

[0198] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is further configured to build a virtual multi-region network model of a vehicle by pre-populating a virtual multi-region network model.

[0199] In some aspects, the techniques described herein relate to a system in which the pre-populating includes prompting a user for at least one basic network selection value and building an initial model in response to a user response to the at least one basic network selection value.

[0200] In some aspects, the techniques described herein relate to a system in which each of the at least one basic network selection value includes at least one of the following: a network topology selection; a network region distribution selection; a network type selection; a communication protocol selection; a cross-network sampling scheme; a cross-network encapsulation scheme; a region manager distribution scheme; a central region manager selection; or a cross-network routing scheme.

[0201] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is also configured to build a virtual multi-region network model of a vehicle by interpreting redundant descriptions of at least one component of a multi-region network.

[0202] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is also configured to build a vehicle environment model, and in which a network execution circuit is also configured to simulate runtime operation of a multi-region network in response to the vehicle environment model.

[0203] In some aspects, the techniques described herein relate to a system in which the vehicle environment model includes a model of at least one of the following: a temperature environment model; a vibration environment model; an electromagnetic interference model; or a water intrusion model.

[0204] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is also configured to build a network hardware model, and in which a network execution circuit is also configured to simulate runtime operation of a multi-region network in response to the network hardware model.

[0205] In some aspects, the techniques described herein relate to a system in which the network hardware model includes a model of at least one of the following: a connector of at least one component of a multi-region network; a cable description of at least one component of a multi-region network; a cooling description of at least one component of a multi-region network; or a shielding description of at least one component of a multi-region network.

[0206] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is also configured to build a virtual multi-region network model of a vehicle by interpreting a time management scheme of a multi-region network.

[0207] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is also configured to build a virtual multi-region network model of a vehicle by interpreting a communication priority scheme.

[0208] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is also configured to build a virtual multi-region network model of a vehicle by interpreting a network security description.

[0209] In some aspects, the techniques described herein relate to a system in which a network modeling circuit is also configured to build a virtual multi-region network model of a vehicle by interpreting a network connectivity description.

[0210] In some aspects, the techniques described herein relate to a system in which a vehicle multi-region architecture configuration platform further includes a partition architecture call-out circuit configured to build a partition architecture communication scheme in response to a user operation on an interface.

[0211] In some aspects, the techniques described herein relate to a system where the partitioned architecture callout circuit is further configured to transmit a partitioned architecture communication scheme to a network management controller of a target vehicle.

[0212] In some aspects, the techniques described herein relate to a method that includes: providing a virtual network building environment to a user interface; constructing a virtual multi - zone network model of a vehicle in response to user input on the user interface, the virtual multi - zone network model including zone controllers located on each zone of the virtual multi - zone network model; populating the virtual multi - zone network model with endpoints based on a vehicle control model; wherein constructing the virtual multi - zone network model further includes applying a partitioned architecture communication scheme; simulating runtime operations of the multi - zone network of the vehicle in response to the virtual multi - zone network model, the vehicle control model, and the partitioned architecture communication scheme; and providing a network operation report in response to the simulation.

[0213] In some aspects, the techniques described herein relate to a method where the partitioned architecture communication scheme includes at least one of a network security description, a network connectivity description, a time management scheme, or a communication priority scheme.

[0214] In some aspects, the techniques described herein relate to a method where the vehicle control model includes a model of endpoints of a multi - zone network that simulates vehicle control operations.

[0215] In some aspects, the techniques described herein relate to a method where the vehicle control model includes a model of endpoints of a multi - zone network that operates actual vehicle control instructions.

[0216] In some aspects, the techniques described herein relate to a method where simulating the runtime operations of the multi - zone network further includes simulating non - nominal conditions.

[0217] In some aspects, the techniques described herein relate to a method where simulating non - nominal conditions includes simulating at least one condition selected from the following: endpoint loss, network component loss, a selected vehicle operating condition, or a selected operator behavior.

[0218] In some aspects, the techniques described herein relate to a method where constructing the virtual multi - zone network model of the vehicle includes applying a network topology description.

[0219] In some aspects, the techniques described herein relate to a method where applying a network topology description includes applying a selected network topology to a zone of the multi - zone network and assigning zone controllers to zones of the multi - zone network.

[0220] In some aspects, the techniques described herein relate to a method where applying a network topology description includes applying the network topology description in response to user input on the user interface.

[0221] In some aspects, the techniques described herein relate to a method in which a network operation report includes an operation capability value.

[0222] In some aspects, the techniques described herein relate to a method in which a network operation report includes a vehicle network performance description.

[0223] In some aspects, the techniques described herein relate to a method in which the vehicle network performance description includes at least one of the following: a latency value between at least two endpoints of a multi-region network; a bandwidth value between at least two endpoints of a multi-region network; a hardware redundancy description of a multi-region network; or a control redundancy description of a multi-region network.

[0224] In some aspects, the techniques described herein relate to a method in which a network operation report includes a vehicle performance network impact description.

[0225] In some aspects, the techniques described herein relate to a method in which the vehicle performance network impact description includes at least one of the following: an installed hardware cost value of a multi-region network; a task capability description of a multi-region network; an integration cost description of a multi-region network; an operation cost description of a multi-region network; a redundancy capability description of a multi-region network; or a reliability description of a multi-region network.

[0226] In some aspects, the techniques described herein relate to a method in which constructing a virtual multi-region network model of a vehicle further includes pre-filling the virtual multi-region network model.

[0227] In some aspects, the techniques described herein relate to a method in which pre-filling includes prompting a user for at least one basic network selection value and constructing an initial model in response to a user response to the at least one basic network selection value.

[0228] In some aspects, the techniques described herein relate to a method in which each of the at least one basic network selection value includes at least one of the following: a network topology selection; a network area distribution selection; a network type selection; a communication protocol selection; a cross-network sampling scheme; a cross-network encapsulation scheme; a regional manager distribution scheme; a central regional manager selection; or a cross-network routing scheme.

[0229] In some aspects, the techniques described herein relate to a method in which constructing a virtual multi-region network model of a vehicle further includes interpreting a redundancy description of at least one component of the multi-region network.

[0230] In some aspects, the techniques described herein relate to a method that further includes constructing a vehicle environment model, and in which simulating the runtime operation of the multi-region network further responds to the vehicle environment model.

[0231] In some aspects, the techniques described herein relate to a method in which a vehicle environment model includes a model of at least one of the following: a temperature environment model; a vibration environment model; an electromagnetic interference model; or a water intrusion model.

[0232] In some aspects, the techniques described herein relate to a method further including constructing a network hardware model, and wherein simulating the runtime operation of a multi-region network also responds to the network hardware model.

[0233] In some aspects, the techniques described herein relate to a method in which the network hardware model includes a model of at least one of the following: a connector of at least one component of the multi-region network; a cable description of at least one component of the multi-region network; a cooling description of at least one component of the multi-region network; or a shielding description of at least one component of the multi-region network.

[0234] In some aspects, the techniques described herein relate to a method in which constructing a virtual multi-region network model of a vehicle further includes interpreting a time management scheme of the multi-region network.

[0235] In some aspects, the techniques described herein relate to a method in which constructing a virtual multi-region network model of a vehicle further includes interpreting a communication priority scheme.

[0236] In some aspects, the techniques described herein relate to a method in which constructing a virtual multi-region network model of a vehicle further includes interpreting a network security description.

[0237] In some aspects, the techniques described herein relate to a method in which constructing a virtual multi-region network model of a vehicle further includes interpreting a network connectivity description.

[0238] In some aspects, the techniques described herein relate to a method further including constructing a partitioned architecture communication scheme in response to a user operation on an interface.

[0239] In some aspects, the techniques described herein relate to a method further including transmitting the partitioned architecture communication scheme to a network management controller of a target vehicle.

[0240] In some aspects, the techniques described herein relate to a system including: a vehicle multi-region monitoring platform including: a network layout circuit configured to interpret a virtual network layout of a vehicle having a multi-region network; a network characterization circuit configured to interpret network activity of the vehicle; and a network analysis circuit configured to determine a virtual network map in response to the virtual network layout and the network activity and provide the virtual network map to a user interface.

[0241] In some aspects, the techniques described herein relate to a system in which the virtual network map includes an interactive depiction of network activity.

[0242] In some aspects, the techniques described herein relate to a system in which a network analysis circuit is also configured to provide network detail values in response to a user selection on a user interface.

[0243] In some aspects, the techniques described herein relate to a system in which the network detail values include at least one of the following: a network traffic description; a partitioned architecture communication scheme; a network statistic value; or a network event notification.

[0244] In some aspects, the techniques described herein relate to a system in which a vehicle multi-zone monitoring platform further includes a network configuration circuit configured to interpret a network adjustment value and update a virtual network map in response to the network adjustment value.

[0245] In some aspects, the techniques described herein relate to a system in which a network analysis circuit is also configured to determine a network impact value in response to a network adjustment value and provide the network impact value to a user interface.

[0246] In some aspects, the techniques described herein relate to a system in which a vehicle multi-zone monitoring platform further includes a partitioned architecture retrieval circuit configured to construct a partitioned architecture communication scheme in response to a network adjustment value.

[0247] In some aspects, the techniques described herein relate to a system in which the partitioned architecture retrieval circuit is also configured to transmit the partitioned architecture communication scheme to a network management controller of at least one of a vehicle or an off-vehicle.

[0248] In some aspects, the techniques described herein relate to a method including: interpreting a virtual network layout of a vehicle having a multi-zone network; interpreting network activity of the vehicle; determining a virtual network map in response to the virtual network layout and the network activity; and providing the virtual network map to a user interface.

[0249] In some aspects, the techniques described herein relate to a method further including providing the virtual network map as an interactive network activity depiction.

[0250] In some aspects, the techniques described herein relate to a method further including providing network detail values in response to a user selection on a user interface.

[0251] In some aspects, the techniques described herein relate to a method in which the network detail values include at least one of the following: a network traffic description; a partitioned architecture communication scheme; a network statistic value; or a network event notification.

[0252] In some aspects, the techniques described herein relate to a method further including interpreting a network adjustment value and updating a virtual network map in response to the network adjustment value.

[0253] In some aspects, the techniques described herein relate to a method that further includes determining a network impact value in response to a network adjustment value and providing the network impact value to a user interface.

[0254] In some aspects, the techniques described herein relate to a method that further includes constructing a partitioned architecture communication scheme in response to a network adjustment value.

[0255] In some aspects, the techniques described herein relate to a method that further includes transmitting the partitioned architecture communication scheme to a network management controller of at least one of a vehicle or an offset vehicle.

[0256] In some aspects, the techniques described herein relate to a system that includes: a vehicle having a multi-region network that includes a plurality of network regions, each network region including at least one region manager; a network monitoring controller that includes: a network layout circuit configured to interpret a partitioned architecture communication scheme and a network layout of the vehicle; a network characterization circuit configured to interpret network activity of the vehicle and determine a network performance event in response to the network activity; and a network reaction circuit configured to perform a network event action in response to the network performance event.

[0257] In some aspects, the techniques described herein relate to a system in which the network event action includes: collecting event information in response to a network performance event; and transmitting the event information to an external device.

[0258] In some aspects, the techniques described herein relate to a system in which the network reaction circuit is further configured to collect event information as a post-event activity.

[0259] In some aspects, the techniques described herein relate to a system in which the network reaction circuit is further configured to collect event information by capturing network activity used to determine a network performance event.

[0260] In some aspects, the techniques described herein relate to a system in which the network event action includes performing a network test.

[0261] In some aspects, the techniques described herein relate to a system in which the network event action includes performing a diagnosis.

[0262] In some aspects, the techniques described herein relate to a system in which the network event action includes adjusting a partitioned architecture communication scheme.

[0263] In some aspects, the techniques described herein relate to a system in which the network event action includes implementing redundancy planning.

[0264] In some aspects, the techniques described herein relate to a system in which the network event action includes adjusting control responsibility of at least one endpoint on a multi-region network.

[0265] In some aspects, the techniques described herein relate to a method that includes: interpreting a partitioned architecture communication scheme and network layout for a vehicle having a multi-region network that includes a plurality of network regions, each network region including at least one region manager; interpreting network activity of the vehicle; in response to the network activity, determining a network performance event; and in response to the network performance event, performing a network event action.

[0266] In some aspects, the techniques described herein relate to a method wherein the network event action includes: collecting event information in response to the network performance event; and transmitting the event information to an external device.

[0267] In some aspects, the techniques described herein relate to a method wherein collecting event information includes collecting the event information as a post-event activity.

[0268] In some aspects, the techniques described herein relate to a method wherein collecting event information includes collecting the event information by capturing network activity used to determine the network performance event.

[0269] In some aspects, the techniques described herein relate to a method wherein performing the network event action includes performing a network test.

[0270] In some aspects, the techniques described herein relate to a method wherein performing the network event action includes performing a diagnosis.

[0271] In some aspects, the techniques described herein relate to a method wherein performing the network event action includes adjusting the partitioned architecture communication scheme.

[0272] In some aspects, the techniques described herein relate to a method wherein performing the network event action includes implementing a redundancy plan.

[0273] In some aspects, the techniques described herein relate to a method wherein performing the network event action includes adjusting control responsibility of at least one endpoint on the multi-region network.

[0274] These and other systems, methods, objects, features, and advantages of the present disclosure will be apparent to those skilled in the art from the following detailed description of the preferred embodiments and the accompanying drawings.

[0275] All documents mentioned herein are hereby incorporated by reference in their entirety. References to singular items should be construed to include plural items and vice versa, unless otherwise expressly stated or clear from the text. Grammatical conjunctions are intended to express any and all disjunctive and conjunctive combinations of the connected clauses, sentences, words, etc., unless otherwise stated or clear from the context. BRIEF DESCRIPTION OF THE DRAWINGS

[0276] The following detailed description of the present disclosure and its specific embodiments can be understood by referring to the following drawings:

[0277] Figure 1 is a schematic diagram illustrating a previously known network arrangement.

[0278] Figure 2 is a schematic diagram illustrating an embodiment of the present disclosure.

[0279] Figure 3 is a block diagram depicting certain considerations of a star topology according to certain embodiments of the present disclosure.

[0280] Figure 4 is a block diagram depicting certain considerations of a ring topology according to certain embodiments of the present disclosure.

[0281] Figure 5 is a block diagram depicting certain considerations of a mesh topology according to certain embodiments of the present disclosure.

[0282] Figures 6A - 6B is a block diagram depicting an example dual - region network according to certain embodiments of the present disclosure.

[0283] Figure 7 is a block diagram depicting an example conceptual hierarchical arrangement according to certain embodiments of the present disclosure.

[0284] Figure 8 is a block diagram depicting an example physical packaging arrangement according to certain embodiments of the present disclosure.

[0285] Figure 9 is a block diagram depicting an example partition with three regions according to certain embodiments of the present disclosure.

[0286] Figure 10 is a block diagram depicting an example data traffic type according to certain embodiments of the present disclosure.

[0287] Figure 11 is a block diagram depicting an example central network controller according to certain embodiments of the present disclosure.

[0288] Figure 12 is a block diagram depicting an example time synchronization operation according to certain embodiments of the present disclosure.

[0289] Figures 13 - 14 is a block diagram depicting an example embodiment of a partitioned architecture for controlling messages with mixed criticality levels thereon according to certain embodiments of the present disclosure.

[0290] Figures 15 - 17 is a schematic depiction of an example hardware layer for implementing an SOA communication embodiment on a vehicle according to certain embodiments of the present disclosure.

[0291] Figure 18 Another embodiment of implementing SOA on a vehicle is schematically depicted in accordance with certain embodiments of the present disclosure.

[0292] Figure 19 An embodiment of implementing SOA on a vehicle is schematically depicted in accordance with certain embodiments of the present disclosure.

[0293] Figure 20 Multiple capabilities of embodiments herein are schematically depicted in accordance with certain embodiments of the present disclosure, including embodiments utilizing containerized applications.

[0294] Figure 21 It is a block diagram depicting an implementation example of a regional architecture in accordance with certain embodiments of the present disclosure.

[0295] Figure 22 It is a block diagram depicting another implementation example of a regional architecture in accordance with certain embodiments of the present disclosure.

[0296] Figures 23 - 23B It is a block diagram depicting an example software stack for a regional architecture on a vehicle in accordance with certain embodiments of the present disclosure.

[0297] Figure 24 It is a block diagram depicting an implementation example of a regional architecture and certain associated features and considerations in accordance with certain embodiments of the present disclosure.

[0298] Figure 25 It is a block diagram depicting an implementation example of a regional architecture in accordance with certain embodiments of the present disclosure.

[0299] Figure 26 It is a block diagram depicting an implementation example of a regional architecture with an SOA implementation in accordance with certain embodiments of the present disclosure.

[0300] Figure 27 It is a block diagram depicting another example software stack and / or logic layer for a regional architecture on a vehicle in accordance with certain embodiments of the present disclosure.

[0301] Figure 28 It is a block diagram depicting a regional controller in accordance with certain embodiments of the present disclosure.

[0302] Figure 29 It is a block diagram depicting a network manager controller in accordance with certain embodiments of the present disclosure.

[0303] Figure 30 It is a block diagram depicting a regional manager command description in accordance with certain embodiments of the present disclosure.

[0304] Figure 31 It is a block diagram depicting a (one or more) network topology description in accordance with certain embodiments of the present disclosure.

[0305] Figure 32 is a process for integrating a multi - zone network on a vehicle according to certain embodiments of the present disclosure.

[0306] Figure 33 is according to certain embodiments of the present disclosure Figure 32 Another process, in which a multi - zone network is installed.

[0307] Figure 34 is according to certain embodiments of the present disclosure Figure 32 Another process, in which a multi - zone network is installed.

[0308] Figure 35 is according to certain embodiments of the present disclosure Figure 32 Another process, in which a multi - zone network is installed.

[0309] Figure 36 is a block diagram depicting a vehicle network performance description according to certain embodiments of the present disclosure.

[0310] Figure 37 is a block diagram depicting a vehicle performance network impact description according to certain embodiments of the present disclosure.

[0311] Figure 38 is a block diagram depicting (one or more) zone architecture values according to certain embodiments of the present disclosure.

[0312] Figure 39 is a process for integrating a multi - zone network on each of a first and a second vehicle according to certain embodiments of the present disclosure.

[0313] Figure 40 is according to certain embodiments of the present disclosure as Figure 39 Another process for integrating a multi - zone network on each of a first and a second vehicle as in

[0314] Figure 41 is according to certain embodiments of the present disclosure as Figure 39 Another process for integrating a multi - zone network on each of a first and a second vehicle as in

[0315] Figure 42 is according to certain embodiments of the present disclosure as Figure 39 Another process for integrating a multi - zone network on each of a first and a second vehicle as in

[0316] Figure 43 is a process for utilizing currently proposed zone architecture values according to certain embodiments of the present disclosure.

[0317] Figure 44 is a block diagram depicting a vehicle network risk description according to certain embodiments of the present disclosure.

[0318] Figure 45 is a process for integrating a multi - zone network on a vehicle according to certain embodiments of the present disclosure.

[0319] Figure 46 is a block diagram depicting a network management controller according to certain embodiments of the present disclosure.

[0320] Figure 47 is a block diagram depicting a partitioned architecture communication scheme according to certain embodiments of the present disclosure.

[0321] Figure 48 is a process for operating a zone manager according to certain embodiments of the present disclosure.

[0322] Figure 49 is another process step in operating a zone manager according to certain embodiments of the present disclosure.

[0323] Figure 50 is a process for migrating central zone manager responsibilities according to certain embodiments of the present disclosure.

[0324] Figure 51 is a block diagram depicting a network security description according to certain embodiments of the present disclosure.

[0325] Figure 52 is a block diagram depicting one or more license values according to certain embodiments of the present disclosure.

[0326] Figure 53 is a block diagram depicting a connectivity scheme according to certain embodiments of the present disclosure.

[0327] Figure 54 is a process for controlling communication between endpoints of a multi - zone network according to certain embodiments of the present disclosure.

[0328] Figure 55 is according to certain embodiments of the present disclosure as Figure 54 another process portion for controlling communication between endpoints of a multi - zone network as in

[0329] Figure 56 is according to certain embodiments of the present disclosure as Figure 54 another process portion for controlling communication between endpoints of a multi - zone network as in

[0330] Figure 57 is a process for providing an updated zone manager command description according to certain embodiments of the present disclosure.

[0331] Figure 58 is a process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0332] Figure 59 is another process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0333] Figure 60 is another process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0334] Figure 61 is another process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0335] Figure 62 is a block diagram depicting a network connectivity description according to certain embodiments of the present disclosure.

[0336] Figure 63 is a process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0337] Figure 64 is another process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0338] Figure 65 is another process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0339] Figure 66 is another process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0340] Figure 67 is a block diagram depicting a service manager controller according to certain embodiments of the present disclosure.

[0341] Figure 68 is a system depicting a process of a service management controller according to certain embodiments of the present disclosure.

[0342] Figure 69 is a block diagram depicting an aspect of a zone architecture according to certain embodiments of the present disclosure.

[0343] Figure 70 is a sample service registry according to certain embodiments of the present disclosure.

[0344] Figure 71 is a process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0345] Figure 72 is a process for maintaining a service registry according to certain embodiments of the present disclosure.

[0346] Figure 73 is a block diagram depicting a network management controller according to certain embodiments of the present disclosure.

[0347] Figure 74 is a block diagram depicting a partitioned architecture communication scheme according to certain embodiments of the present disclosure.

[0348] Figure 75 is a process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0349] Figure 76 is a process for controlling communication between endpoints in a multi - zone network according to certain embodiments of the present disclosure.

[0350] Figure 77 is a block diagram depicting a vehicle multi - zone architecture configuration platform according to certain embodiments of the present disclosure.

[0351] Figure 78 is a block diagram process depiction of a vehicle multi - zone architecture configuration platform according to certain embodiments of the present disclosure.

[0352] Figure 79 is a block diagram depicting a vehicle multi - zone architecture configuration platform according to certain embodiments of the present disclosure.

[0353] Figure 80 is a block diagram depicting a partitioned architecture communication scheme according to certain embodiments of the present disclosure.

[0354] Figure 81 is a block diagram depicting a network operation report according to certain embodiments of the present disclosure.

[0355] Figure 82 is a block diagram depicting a vehicle network performance description according to certain embodiments of the present disclosure.

[0356] Figure 83 is a block diagram depicting a vehicle performance network impact description according to certain embodiments of the present disclosure.

[0357] Figure 84 is a block diagram depicting a basic network selection value according to certain embodiments of the present disclosure.

[0358] Figure 85 is a block diagram depicting a vehicle environment model according to certain embodiments of the present disclosure.

[0359] Figure 86 is a block diagram depicting a network hardware model according to certain embodiments of the present disclosure.

[0360] Figure 87is a process for providing network operation reports according to certain embodiments of the present disclosure.

[0361] Figure 88 is a process for transmitting a partitioned architecture communication scheme according to certain embodiments of the present disclosure.

[0362] Figure 89 is a block diagram depicting a vehicle multi - zone monitoring platform according to certain embodiments of the present disclosure.

[0363] Figure 90 is a block diagram depicting network detail values according to certain embodiments of the present disclosure.

[0364] Figure 91 is a process for providing a virtual network map to a user interface according to certain embodiments of the present disclosure.

[0365] Figure 92 is a process for constructing a partitioned architecture communication scheme according to certain embodiments of the present disclosure.

[0366] Figure 93 is a block diagram depicting a network monitoring controller according to certain embodiments of the present disclosure.

[0367] Figure 94 is a block diagram depicting network event actions according to certain embodiments of the present disclosure.

[0368] Figure 95 is a process for performing network event actions according to certain embodiments of the present disclosure. Detailed Description

[0369] Without limiting any other aspects of the present disclosure, the aspects disclosed herein provide an implementation of a partitioned network architecture on a vehicle, where each zone includes a portion of the endpoints on the vehicle, and where each zone can include multiple network types, e.g., some endpoints communicate on a CAN network architecture while other endpoints communicate on an Ethernet architecture, a LIN architecture, etc. The utilization of the partitioned architecture provides many benefits over previously known systems, such as allowing endpoints to be communicatively coupled to the network and other devices based on physical location rather than the function of the endpoints, reducing the run length of electrical connections, allowing redundancy in the connection options for endpoints (e.g., to accommodate loss of connection infrastructure due to wear, failure, vehicle damage, etc.), increasing network control and security, allowing more options for controller distribution (e.g., reducing the number of required controllers, allowing controller - to - controller redundancy), and dynamic configuration of vehicle applications, connectivity between endpoints, data collection operations, and / or data provision options (e.g., making data available from one endpoint to any other endpoint).

[0370] Example embodiments utilize policies to implement security, authorization, and / or configuration options. For example, a policy can include a data structure that defines which endpoints are allowed to request data, which endpoints are allowed to provide data, priorities associated with the endpoints, data configurations associated with the endpoints (e.g., units, sampling rate, latency, priority, resolution, etc.), and so on. In some embodiments, the policy is a file or other data structure that can be dynamically updated, allowing configuration changes without changing firmware, changing software, etc., allowing dynamic updates without having to power down, increasing the risk of incomplete updates that may disable the controller, and so on.

[0371] Certain aspects of the present disclosure include various operations for controlling communications in a vehicle network environment, including providing communications between devices or endpoints on different network regions and / or different network types, providing control without requiring communicators to have specific knowledge of the actual addresses or locations of other devices on the network, using policies or profiles to update network control parameters, and so on. Additionally, certain aspects of the present disclosure include controlling two-way communications between vehicle devices and external devices. Additionally, certain aspects of the present disclosure include adjusting communication routing on the network, whether between independent devices on the network or between devices on the network and external devices. Without being limited to any aspect of the present disclosure, some tools that, in combination with the present disclosure, can be used to tactically implement certain operations herein, and descriptions that can enhance the understanding of some terms used herein (such as, policies, endpoints, external devices, network protocols, network types, etc.) can be found in one or more of the following U.S. patents or patent applications: U.S. Application No. 17 / 027,167 (SONA-0006-U01), filed on September 21, 2020, and titled "SYSTEM, METHOD, AND APPARATUS TO SUPPORT MIXED NETWORK COMMUNICATIONS ON A VEHICLE"; U.S. Application No. 17 / 027,187 (SONA-0007-U01), filed on September 21, 2020, and titled "SYSTEM, METHOD, AND APPARATUS TO EXTRA VEHICLE COMMUNICATIONS CONTROL"; U.S. Application No. 17 / 195,589 (SONA-0010-U01), filed on March 8, 2021, and titled "SYSTEM, METHOD, AND APPARATUS FOR MANAGING VEHICLE DATA COLLECTION"; and U.S. Application No. 17 / 833,614 (SONA-0012-U01), filed on June 6, 2022, and titled "SYSTEM, METHOD, AND APPARATUS FOR MANAGING VEHICLE DATA COLLECTION", each of which is incorporated herein by reference in its entirety for all purposes. Embodiments throughout the present disclosure may be embodied, at least in part, using controllers, circuits, components, processors, and / or operations, such as those set forth in one or more of the foregoing patents or patent applications.For example, operations for managing in-vehicle and / or inter-vehicle communications, including adjusting management based on changes such as policies, can utilize the embodiments described in Application '167; operations for managing communications between any endpoint and an external device, including adjusting management based on changes such as policies, can utilize the embodiments described in Application '187; operations for managing data collection operations, including adjusting data collection, formatting, and / or data configuration, data lifecycle management, and communication of the collected data, can utilize the embodiments described in Application '589; and / or operations for implementing, executing, and otherwise managing autonomous vehicle operations, including operations that can be achieved without software or firmware updates, can utilize the embodiments described in Application '614.

[0372] Certain aspects of the present disclosure are described as controllers, circuits, computing devices, processors, electronic computing units (ECUs), managers (e.g., with reference to Figure 22 and related descriptions), management devices (e.g., with reference to Figure 8 and related descriptions), adapters (e.g., with reference to Figure 19 and related descriptions), platforms, or any other components with similar language and configured to perform certain operations and / or having a structure for performing certain operations. In the remainder of this paragraph, any such device is referred to as a "circuit or similar term". Without being limited to any other aspect of the present disclosure, the circuit or similar term utilized herein can be embodied as any one or more of the following: a computing device having computing resources (e.g., processing, memory, communication interface, etc.) and configured and capable of performing aspects of the operations; any hardware interface element, such as a mouse, keyboard, microphone, display device, etc.; a sensor configured to provide the data elements and / or provide information from which the data elements can be determined, estimated, or inferred; an actuator configured to provide the operations; instructions stored on a computer-readable medium such that a processor, in response to the instructions, performs one or more of the described operations; a hardware component configured to perform one or more operations in response to an operating condition (e.g., valves, springs, switches, gear assemblies, etc., configured to perform one or more of the described operations); and / or a logic circuit configured and / or programmed to perform one or more of the described operations. For the sake of clarity in this specification, the circuit or similar term is depicted as a single device in the embodiments herein. The circuit or similar term can be distributed, e.g., parts of the circuit are located on different computing devices and / or at least partially embodied on various hardware devices, where the distributed parts cooperate to perform the described functions. In certain embodiments, the distribution of the circuit or similar term can vary according to the current operating condition, such as the build environment circuit 9804 (with reference to Figure 77A portion of (and related descriptions) may be located on the user interface and / or user device during certain operations, such as to make the operations more responsive to the user and / or enhance the security of communication between the user and the vehicle multi - zone architecture configuration platform (in this example). Additionally, a device embodying a circuit or similar terms may vary depending on the operating conditions and / or the operations being performed. In another example of using the build environment circuit 9804, a user may connect to the platform with a first device (e.g., a laptop computer) at a first time and with a second device (e.g., a mobile phone) at a second time, where the elements embodying the build environment circuit 9804 may be different, such as a portion of the build environment circuit 9804 being located on the user device during certain operations. In another example, the central area manager may be migrated during certain operations, e.g., when another area controller is designated as the central area manager in response to a non - nominal event, and thus, the specific hardware device embodying the central area manager may be different at different times, under different operating conditions, and / or depending on the specific operations being performed by the system. The use of the term circuit or other similar terms in this document is provided for the clarity of this specification, and any device configured to operably perform the operations set forth herein is contemplated. Exemplary and non - limiting specific arrangements are described herein to provide clarity of description and context to illustrate the operations and benefits of the present disclosure, but any other arrangement capable of and configured to perform the described operations is specifically contemplated herein.

[0373] The various embodiments herein are presented as programs, methods, or other operational descriptions to perform certain actions embodying aspects of the present disclosure. Such operations will be referred to as "programs" for the remainder of this paragraph. Any such program may vary in the order of operations, be executed as a loop or repeating operation (where relevant, and in whole or in part), the described operations may be divided into parts, and / or the operations may be combined (in whole or in part). In certain embodiments, the program may be executed in whole or in part by any hardware device (including any circuit, controller, computing device, etc.) having the ability to execute the example process operations set forth throughout this disclosure.

[0374] Figure 1 An example of a previously known system 100 is illustrated, including various networks and endpoints distributed around a vehicle. Figure 1 The example of [the system] is simplified to illustrate the differences from the system of the present disclosure, but actual examples of previously known systems are even more complex and intricate than the depicted system. Figure 2The example of FIG. 0 schematically depicts an example system 200 of the present disclosure. The network is divided into regions selected based on cost (e.g., reduced cabling, docking, and configuration as such) and risk management (e.g., reduced exposure of network paths to various vehicle risks, increased security due to a small number of network area managers being able to monitor network areas and enforce security protocols). Other embodiments of the present disclosure maintain cost reduction and risk management, but may further support capabilities such as providing redundant control and / or hardware operation, e.g., creating a system robust to failures, based on the ability to retain selections in case of failures. Thus, the systems of the present disclosure have a reduced likelihood of failure and excellent response capabilities in case of failures.

[0375] Figures 3 - 5 Illustrated are example basic topologies 300, 400, and 500 supported by embodiments herein. The example topologies are non-limiting and include a star topology (e.g., all regions communicate through a central region), a ring topology (e.g., communication traverses a serial link through all regions in a selected order, adjacent regions are able to communicate directly, and remote regions communicate using hops through intermediate regions), and / or a mesh topology (e.g., each region is communicatively coupled to every other region). In some embodiments, a combination of one or more of these, and / or a partial implementation of one or more of these (e.g., a mesh topology with some connections omitted) may be utilized. Note that the topologies herein represent network connections between network regions and the region managers of each network region, rather than connections between endpoints. In a highly distributed system of over 100 devices with a hybrid overlapping network, the terms mesh, star, or ring topology will indicate something completely different from Figures 3 - 5 the network region layout. Also note that the depicted network region selections and locations are non-limiting examples. The region layout may be selected based on the cost of designing, maintaining, and integrating the resulting network regions, and the region layout may also be selected to support redundancy. The reduction in the number of extended connections throughout the vehicle allows embodiments of the present disclosure to improve routing, e.g., path selection through low-risk regions of the vehicle, and reduce the consequences of any one of those paths suffering an adverse event. For example, if the vehicle is damaged at a certain location, it is likely that such damage will not affect the network at all, or will only damage a single region connection, rather than damaging several networks and causing the loss of many devices distributed around the vehicle. Additionally, by allowing the network to be organized near the devices, rather than near the functions, the natural risk management of the vehicle may support the risk management of the network. For example, the battery pack of an electric vehicle is typically in a protected space. In previously known systems, multiple network links associated with the battery pack may be distributed around the vehicle, resulting in unexpected failure scenarios, e.g., damage to another remote region of the vehicle may cause the loss of battery pack functionality (e.g., the ability to automatically disconnect the battery in case of an accident), reducing the value of the effort to protect the battery pack.

[0376] Figure 3 Illustrates certain considerations of a star topology with four network regions in this example. The star topology is a low-cost implementation where the number of required wirings, I / O between regions, and other benefits are significantly reduced, such as reducing implementation costs, e.g., the implementation cost of network management features necessary to obtain some benefits of other topologies. The star topology includes certain drawbacks, such as a single point of failure in the central region controller - which would disable connectivity between other network regions, lack of redundancy if communication between a region and the central region is lost, and the need for a high-performance central region controller. However, embodiments such as Figure 3 are feasible, for example, if the high-performance central region controller is located in a protected area.

[0377] Figure 4 Illustrates certain considerations of a ring topology 400 with four network regions in this example. The ring topology significantly reduces the number of required wirings, although less than the star topology, and reduces I / O between regions. The ring topology may introduce some latency, such as the latency between two high-demand endpoints located in remote regions. The ring topology does provide some redundancy, e.g., the system can still operate if any single connection between regions fails or is lost. It should be understood that network management can be performed to support redundancy, e.g., reroute communication if a link between two regions is lost. In certain embodiments, fault analysis can be utilized to determine the arrangement and sequencing of the ring, e.g., to ensure that two critical regions are not separated by too many "hops" in the event of a connection failure between any two regions in the system. In certain embodiments, the ring topology can be enhanced with separate connections between critical regions, such as having additional direct connections between those regions, and / or connections between those regions and the "central" region. Embodiments herein generally include the central region concept. While various design considerations may drive the central region to be generally geometrically central, the central region concept utilized herein refers to logical centrality, e.g., in many embodiments, the central region includes a single point for communicating with external devices, for monitoring the network, and for receiving and distributing updates.

[0378] Figure 5Illustrates certain considerations of the mesh topology 500. The mesh topology provides an embodiment with the highest redundancy and the lowest latency. In certain embodiments, the mesh topology can be enhanced with additional connections, such as dual connections between two critical regions and / or between a critical region and the central region. In terms of the reduction in wires and connections required compared to previously known systems, for example, systems that may have 100+ endpoints coupled to various network devices, where the wiring is configured according to the function of the endpoints without considering the physical location of those endpoints, the mesh topology still does bring significant cost savings. The mesh topology requires managing communication to realize the benefits of available redundancy and avoid duplicate communication that utilizes network bandwidth, etc.

[0379] Figure 6A Depicts an example 2 - region network 600. For example, endpoints in the front of the vehicle are connected to a first region, and endpoints in the rear of the vehicle are connected to a second region. Figure 6A Examples include two independent connection paths that allow communication to continue if one of the paths is disrupted. Figure 6B Depicts an example 3 - region network 601, where the regions are depicted as front, rear, and central. The terms herein related to front, rear, central, or other similar terms are not limited to the physical location of the vehicle but refer to logical connections, which may correspond to the physical location but do not need to. For example, the endpoints in many vehicles are more heavily burdened in the front of the vehicle, so the 3 - region network can include two regions in the front (one is the "front" region and one is the "central" region), and a single region in the rear. The choice of region location can be based on the physical location of the endpoints required to support a particular arrangement, the capabilities of the regional controllers, etc., the functions of the endpoints (including the inter - relationships of the functions), the inter - region communication (such as quantity, content, communication rate, message size, latency requirements, etc.).

[0380] Figure 7 Depicts an example conceptual hierarchical arrangement 700 of the embodiments herein. Figure 7 Examples of the hierarchy include a hardware layer (e.g., the actual physical layout of regions, networks, connections to endpoints, etc.), a physical component layer that supports communication (e.g., switches, controllers, edge gateways, storage devices, etc.), an application layer (e.g., control modules and functions that support operations, such as network management, data management, service - oriented architecture (SOA) management, automation management (e.g., supporting automated vehicle functions, service operations, vehicle testing, etc.), and / or security management (e.g., encrypting messages, storing data, etc., and managing communication and / or data permissions of endpoints)), and a vehicle function layer (e.g., specific vehicle functions supported by a set of distributed endpoints across regions, such as the control software of the vehicle, infotainment support, autonomous driving assistance support, etc.).

[0381] Figure 8Depicts an example physical packaging arrangement 800 of an example embodiment, where endpoints communicate to specific regions, and communication between regions enables cross-region communication between endpoints.

[0382] Figure 9 Depicts an example partitioned embodiment 900, in which there are three regions in this example, and considerations for implementing a partitioned architecture on a vehicle. The example endpoint group 306 is a CAN device coupled to one of the network regions. The present disclosure allows any type of endpoint to connect to a given network region, and seamless communication between endpoints on different regions, regardless of the underlying network type specific to the endpoints. For example, a CAN device on a first network region can easily communicate with a LIN device on another network region. Additionally, a user (authorized) accessing the vehicle can refer to the devices on the system without the user having to know anything about the device location or even the network type to which the device is connected. Additionally, the user can request or collect available data from the devices without having to know anything about the devices, their network location or type, or even whether the data is provided by a specific device or by some other determination (e.g., virtual sensor). Figure 9 Examples include a central region manager 302 and two region managers 304 for the other two regions.

[0383] Figure 10 Depicts example 1000 data traffic types that may exist on an example vehicle having a partitioned architecture, depicted in the context of a region manager 304 (or region controller). Network management control that can be implemented on a central region controller and / or distributed across more than one region controller includes managing network bandwidth, permissions, priorities of messages, etc., to ensure that critical vehicle functions are supported and other functions are supported in a desired manner and / or at a desired service level, consistent with the support required by critical vehicle functions.

[0384] Figure 11 Depicts example 1100 central network controller 302, where considerations for the vehicle's central network controller and network management configuration are taken into account.

[0385] Figure 12 Depicts example 1200 time synchronization operations of the embodiments herein. Example synchronization operations include operations such as ensuring that time-sensitive messages are provided within an expected window (e.g., latency, arrival time, etc.), timestamping according to a recognized specification that allows control operations at endpoints to utilize data in an expected manner, etc. In some embodiments, time synchronization can be relative (e.g., ensuring that all relevant endpoints can utilize data as expected, regardless of the relationship of the synchronization to some absolute reference time), absolute (e.g., ensuring that all relevant endpoints can associate data values with an absolute reference time), or a combination of these. Figure 34Depicts additional or alternative time synchronization operations of embodiments herein.

[0386] Figures 13 - 14 Depicts an example embodiment of a 3 - zone network including various communication routing options for different systems. The routing options can be determined based on, but not limited to, source or destination endpoints, content of the message, associated flow of the message, application, function, etc., current operating condition of the vehicle, and / or to support redundant operations (e.g., replace or mitigate loss or degradation of hardware components and / or controllers). System 1300 depicts various routing paths 1302, 1304 for different messages. System 1400 depicts various alternative routing paths 1402, 1404 with respect to Figure 13 which may be due to different underlying configurations in response to message standards and / or in response to the vehicle operating condition.

[0387] Figure 15 Is a schematic depiction of a service - oriented architecture (SOA) implementation 1500 that allows endpoints to subscribe to services (e.g., collect desired data, provide actuator commands, etc.), publish services, and / or restrict service access based on permissions (e.g., as set forth in a policy or similar implementation). Figure 16 Is a schematic depiction of an example hardware layer 1600 for implementing SOA communication embodiments on a vehicle. Using SOA for network communication on a vehicle provides many benefits, including ease of dynamically changing network configurations and secure control of endpoints for accessing and / or publishing data. Figure 17 and 18 Schematically depict embodiments 1700, 1800 for implementing SOA on a vehicle. Figure 19 Schematically depicts an embodiment 1900 for implementing SOA on a vehicle using an SOA adapter, which can be included on - region and / or with a regional controller, e.g., on a central regional controller.

[0388] Figure 20 Schematically depicts multiple capabilities of embodiments herein, including embodiments using containerized applications 2006 (e.g., containerized network control, time synchronization management 2008, automation management 2004, SOA support 2010, endpoint control 2002, vehicle functions, etc.). Figure 21 Depicts an example implementation consideration for containerized network management of a regional architecture.

[0389] Figure 21 Depicts an example implementation 2100 of a regional architecture that supports endpoints of various network types docking with the region. Figure 22 Depicts another example implementation 2200 of a regional architecture. Divided into Figure 23A and 23B of Figure 23Depicts an example software stack 2300 for an in-vehicle zonal architecture, from the hardware layer 2306 at the bottom, through the control layer 2304 in the middle, up through cloud communication 2302 at the top.

[0390] Figure 24 Depicts an example implementation 2400 of a zonal architecture, along with certain features and considerations associated therewith. Figure 24 Examples include a central zone 2402 hosting multiple applications 2408, communication with a cloud server 2406, endpoints 306 of the central zone 2402, and a second zone 2404 having a zone controller.

[0391] Divided into Figure 25A and 25B of Figure 25 Schematically depicts a zone controller 2500, which can serve as a central zone manager for various embodiments of the present disclosure.

[0392] Figure 26 Depicts an example zonal arrangement 2600 with two zones, where multiple applications are supported on a first zone and multiple endpoints are supported on a second zone.

[0393] Figure 27 Depicts a control hierarchy 2700 having a core services layer 2706, a services layer 2704, and an applications layer 2702. The control hierarchy 2700 can be implemented or coordinated by a controller (such as a central zone manager) in the system.

[0394] Figure 28 Depicts a zone controller 302 with example network traffic types that can exist on a vehicle having a partitioned architecture, which can be considered for various embodiments herein, including at least a selected zonal arrangement, mixed criticality message management, SOA implementation, etc.

[0395] Without being limited to any other aspects of the present disclosure, embodiments herein provide systems and processes for implementing a zonal network architecture on a vehicle to improve reliability, installation cost, operating cost, operational performance, and / or the ability to avoid or mitigate network risks, failures, or degradations and the consequent impact on vehicle tasks.

[0396] Referring to Figure 29 , an example system 5000 includes a vehicle having a multi-zonal network that includes a plurality of network zones, each network zone including at least one zone manager. Throughout the present disclosure, a zone manager may alternatively be referred to as a zone controller. The vehicle is not depicted in Figure 29 but Figure 29The system 5000 may be included, in whole or in part, in any of the embodiments described herein, including vehicles having a multi-zone network. For an example system 5000, network zones are arranged according to a network topology description of a selected zone architecture, where the network topology description includes any one or more aspects set forth throughout this disclosure (e.g., with reference to Figure 31 and 38 and related descriptions). In some embodiments, each network zone includes a zone manager configured to perform control operations on that zone, e.g., permitting communication with other zones, restricting utilization of bandwidth or other resources, implementing prioritization among messages, and / or performing any other operations of the zone manager (or zone controller) as described herein.

[0397] The example system 5000 also includes a network management controller 5002. The example network management controller 5002 includes a zone implementation circuit 5004 that interprets a partitioned architecture communication scheme 5014, a zone manager command circuit 5006 that interprets a zone manager command description 5016 of each zone manager in response to the partitioned architecture communication scheme 5014, and a zone execution circuit 5008 that provides the corresponding zone manager command description 5016 to each zone manager. For example, the partitioned architecture communication scheme 5014 may be embodied as part of a policy, e.g., passed to the network management controller 5002 by an external device, that defines various aspects of managing network communication on and between zones on a vehicle.

[0398] Some communication management may apply to different endpoints on different zones, and the user creating the policy (e.g., an employee of a vehicle manufacturer) may not know the specific arrangement. In this example, the zone manager command circuit 5006 determines the responsibility of each zone manager in response to the partitioned architecture communication scheme 5014 and determines the zone manager command description 5016 to implement the portion of the partitioned architecture communication scheme 5014 that is relevant to that particular zone manager, e.g., based on endpoints (e.g., sensors, actuators, controllers, etc.), flows, functions, applications, etc. served by or embodied on that zone. The zone execution circuit 5008 then distributes the zone manager command description 5016 to the respective zone managers. The individual zone managers utilize a local version of the zone manager command description 5016 (e.g., as a local configuration file) to permit the system to implement updates to zone communication control immediately after vehicle startup, and / or even permit updates during runtime operation, depending on the desired behavior of the system and / or the type of change in the zone manager command description 5016 update.

[0399] Accordingly, embodiments of the present disclosure allow users with specific expertise (e.g., in risk management or fault analysis) to configure the zonal architecture communication scheme 5014 according to their expertise, without requiring them to understand the specific arrangement of endpoints and the control responsibilities on the vehicle. Thus, embodiments of the present disclosure improve the results, such as allowing appropriate experts to build the system to optimize the risk profile of the network, and also introduce improvements by reducing development time and turnaround time. In addition, embodiments of the present disclosure reduce costs by allowing zonal collaboration and seamless switching of data without loss (and generally improving) security or communication capabilities.

[0400] One result of the zonal architecture arrangement of the present disclosure - which allows the zonal architecture to be arranged for various purposes (e.g., system cost, system reliability, providing redundancy, etc.) in addition to the functions of the endpoints at the zone - is that for many vehicle functions, the supporting endpoints will be distributed across more than one zone. The utilization of the zone manager command description 5016 allows those endpoints to seamlessly collaborate to perform the underlying vehicle functions, while having a consistent implementation for those endpoints with respect to communication latency, applicable security, data quality, etc. Prior art systems grouped network zones according to the functions of the vehicle (e.g., a network providing communication between powertrain components) where separate zones existed completely, to enhance the security of communication with the hardware layer (e.g., providing separate public and private CANs), or grouped network zones based on the responsible party for a particular endpoint (e.g., the motor supplier). Thus, prior art systems resulted in an expensive and redundant hardware layer, such as where multiple parallel network cables traversed the same extensive area of the vehicle, and exposed multiple systems to all risks distributed around the vehicle. Embodiments of the present disclosure utilize planning management of risks, redundancy, security applications, etc., significantly reducing the cost of overall network support, and can be built based on the designer's priorities, through a selected combination of enhanced capabilities, reduced risks, reduced costs, and enhanced security.

[0401] In Figure 29 the example, each zone manager responds to the corresponding zone manager command description 5016 to control the communication between the endpoints of the corresponding network zone and the endpoints of at least one other zone of the network zone.

[0402] The network topology description may include any aspect of the network topology set forth throughout the present disclosure. Refer to Figure 31, Example aspects of network topology description include, but are not limited to: a communicatively coupled arrangement 5204 of regions (e.g., which regions are directly coupled to a particular region, which can be in a star, mesh, ring, or other arrangement); or a logically coupled arrangement 5206 of regions (e.g., the sequencing and ordering of communications between regions, such as where communications pass through another intermediate region, the priorities between regions, and / or a description of regions that can be virtual regions, e.g., some communications are shared on the same hardware layer but are separate in terms of which endpoints can see or understand the various communications).

[0403] The example region implementation circuit 5004 interprets the partitioned architecture communication scheme 5014 in response to a policy provided by an external device. An example policy is a profile for network communications on a vehicle, e.g., for at least some embodiments or update operations, allowing an update to the region manager command description 5016 without changing the vehicle's underlying software, reducing the risk of an incomplete update (which could completely disable the vehicle) and reducing the operational impact of the update (e.g., no need to shut down, suspend operational capabilities, and / or perform dedicated maintenance operations). The example region manager command circuit parses the policy including the profile to determine the region manager command description 5016. In some embodiments, the region manager command description 5016 is embodied as a local profile that is transmitted to and utilized by the corresponding region manager. In some embodiments, the region manager command description 5016 is embodied as an update to the local profile of one or more region managers, and the region execution circuit 5008 provides the corresponding region manager command description 5016 to each region manager by updating the local profile of the relevant region manager.

[0404] Reference Figure 30 , Example and non - limiting region manager command descriptions 5016 include one or more aspects, such as: a communication allowance value 5102 (e.g., which endpoints, flows, applications, functions, network regions, etc. are allowed to communicate with others among these, which can be provided as an inclusive and / or exclusive description); a communication sampling rate value 5104 (e.g., how fast endpoints, flows, applications, functions, network regions are allowed to request or provide messages, and / or an absolute or relative description of the allowed bandwidth utilization, including by region, etc.); a communication configuration value 5106 (e.g., message information such as headers, cells, byte depth, metadata, message encapsulation, and / or forced latency parameters (e.g., maximum or minimum latency values)); and / or a communication destination value 5108 (e.g., the endpoints, regions, addresses, etc. to which messages from endpoints, flows, applications, functions, network regions are allowed to send messages, and / or a routing description, such as "Region 1 can send messages generated by Flow A directly to Region 2, while all other messages to Region 2 will be routed through Region 3" - e.g., to conserve bandwidth on critical network regions, to balance workload and utilization, etc.).

[0405] The example network management controller 5002 also includes a hardware redundancy implementation circuit 5010 that supports the implementation of a hardware redundancy scheme. The example hardware redundancy implementation circuit 5010 determines that a hardware non-nominal event 5018 has occurred (e.g., an endpoint, a network area, a zone manager, etc. has lost communication and / or is experiencing performance degradation), and in response to the hardware non-nominal event 5018, adjusts at least one zone manager command description 5016. For example, the system 5000 may have a defined redundancy scheme where if zone manager A fails, zone manager B changes its operation to at least partially fulfill the responsibilities of zone manager A. The available hardware redundancy of a given system 5000 depends on the zone layout and connectivity, and further depends on the planning for the hardware failures under discussion, as reflected in the partitioned architecture communication scheme 5014. In another example, if zone manager A fails, endpoint Z on zone A may perform a specific vehicle function that becomes unavailable. The response may depend on the type of failure. For example, if zone manager B can communicate with endpoint Z, zone manager B may simply perform the network control responsibilities previously performed by zone manager A, and all system capabilities may remain available. However, if the failure of zone manager A removes all communication to zone A, the response may include migrating control responsibility from zone A to an endpoint on another area of the vehicle, and zone manager B may be configured to further notify an endpoint that performs alternative operations to replace the function of endpoint z. In some embodiments, other changes may also be implemented, such as considering different network traffic patterns, etc., which may affect more than just zone B, so the change to the zone manager command description 5016 for a zone A manager failure may extend beyond just the duty update of zone manager B. In some embodiments, the lost function may be fully replaced, e.g., in the case where another endpoint in the system is fully capable of replacing all operations of endpoint z. In some embodiments, the lost function may be partially replaced, e.g., a less capable endpoint may perform some critical functions of endpoint Z, allowing for a potentially degraded continuous operation. In some embodiments, the function replacement may be very limited but still may be important, e.g., allowing the vehicle to continue operating in a limp-home mode to allow the operator to move the vehicle to a safe location, and / or allowing some functions, such as the battery disconnect operation previously performed by endpoint Z, which is limited and even task-disabling but may be important in a catastrophic failure scenario (e.g., an accident of the vehicle disables a significant portion of the entire network hardware layer). The utilization of the hardware non-nominal event 5018 and the update to the zone manager command description 5016 allow for a hierarchical response to various hardware failures while preserving vehicle operation as much as possible and minimizing the impact on the operator.

[0406] The example network management controller 5002 includes a control redundancy implementation circuit 5012 that determines that a control non - nominal event 5020 has occurred and adjusts the area manager command description 5016 in response to the control non - nominal event 5020. For example, if an endpoint controller in the system fails, the hardware connections to that area and other endpoints may still exist, but the functions performed by that endpoint will be lost. In this example, the control non - nominal event 5020 adjusts the area management command 5016 to shift the responsibility for the lost control function to another endpoint (or endpoints) on the vehicle. In some embodiments, the control non - nominal event 5020 can be a performance degradation, a suspect performance (e.g., a stalled or slow response value), and / or a control non - nominal event 5020 determined by a fault code or diagnostic operation. The consideration for the control non - nominal event 5020 is similar to the consideration for the hardware non - nominal event 5018, where various endpoints, area managers, and network areas may be affected by the response operation. It will be understood that some events may not be easily classifiable as either a hardware event or a control event. The operations described herein generally apply to non - nominal events regardless of the specific cause of the event, and the specific terms of hardware events and control events are used to clearly describe specific operations. The terms utilized are not restrictive, and non - nominal events can be handled even if the true cause or classification of the event may not be known.

[0407] Reference Figure 32 , schematically depicts an example process 5300 for implementing an area architecture on a vehicle. The example process 5300 includes an operation of interpreting a vehicle network performance description 5702 (reference Figure 36 ). The example vehicle network performance description 5702 includes performance criteria for the vehicle network, which can include minimum acceptable values (e.g., performing vehicle tasks and / or meeting specifications), target values or desired values, maximum values (e.g., performance values above which no commercial gain is achieved and / or above which the gain is considered to stop increasing), statistical descriptions (e.g., mean, time - average, variability description, etc.), and / or any other type of performance criteria description. In some embodiments, aspects of the vehicle network performance description 5702 are utilized in an index, such as comparing costs and / or benefits between two or more area architecture values.

[0408] Example vehicle network performance description 5702 includes latency values 5704, such as maximum or minimum allowable latency, average latency description, latency trajectory, or duty cycle (e.g., describing burst behavior, etc.). In some embodiments, latency values 5704 may be considered for various endpoints, flows, features, applications, etc., and / or between specific endpoints, network regions, etc. Example vehicle network performance description 5702 includes bandwidth values 5706, such as describing the bandwidth of one or more regions that will be reserved, implemented, available for use, etc. In some embodiments, bandwidth values 5706 are associated with regions or endpoints. Example vehicle network performance description 5702 includes hardware redundancy description 5708, including, for example, aspects of network hardware that should have available backup operations, and / or descriptions of the acceptable capabilities of those backup operations. Example vehicle network performance description 5702 includes control redundancy description 5710, including, for example, control aspects of the network and / or its endpoints that should have available backup operations, and / or descriptions of the acceptable capabilities of those backup operations.

[0409] Example process 5300 further includes operation 5304 to determine a regional architecture value in response to vehicle network performance description 5702 and vehicle performance network impact description 5802 (refer to Figure 37 ). Example vehicle performance network impact description 5802 includes the impact of network capabilities on the regional architecture values being considered, given the vehicle configuration and given which network impacts are important for a particular system.

[0410] Example vehicle performance network impact description 5802 includes installed hardware cost value 5804, which can include any cost type consideration of the regional architecture value under consideration. Example hardware cost value 5804 includes aspects such as: hardware physical cost (e.g., the cost of controllers, regional managers, cables, connectors, shields, etc. used to physically implement the regional architecture value); installed physical footprint (e.g., how much space, weight, number and type of integration interfaces (such as brackets), routing, integration difficulty and / or sensitivity, test requirements for verifying installation, etc.); installed control cost (e.g., the engineering work required to code the solution, the test cost for verifying that any code works as planned, the bandwidth utilization for implementing the solution, the processor utilization for implementing the solution, the memory utilization for implementing the solution, etc.; these can consider any basic control changes to the vehicle, such as by combining endpoints and / or changing the way vehicle control operations are performed, and / or regional manager operations); and / or installed service cost (e.g., the impact on service procedures and / or physical access to vehicle parts affected by the installation, the ability to replace components, any test or verification procedures driven into the service procedures by the installation, the complexity of service tools for performing service procedures that may be affected by the installation, etc.). The installed hardware cost value 5804 can generally be considered the "cost" part of a given regional architecture value, for example, used in an optimization routine to determine acceptable, improved, and / or optimized regional architecture values.

[0411] Example vehicle performance network impact description 5802 includes mission capability description 5806, such as a description of the ability of the regional architecture value under consideration to meet the performance criteria for basic vehicle operations within the entire defined space, e.g., under all normal operating conditions, environmental conditions, etc. Example vehicle performance network impact description 5802 includes redundancy capability description 5808, including a description of the ability of the regional architecture value under consideration to meet hardware and / or control redundancy descriptions. Example vehicle performance network impact description 5802 includes reliability description 5810, including a description of the possible impact of the regional architecture value under consideration on reliability factors, such as estimated maintenance schedules, failure rates and costs, downtime costs, etc. These estimates can be based on temperature, vibration, EMI, and / or water ingress factors related to the vehicle, and can depend on the physical routing of network cables, the location and environment of network components (e.g., regional managers), and the physical components selected, such as cable type, shielding used, connector type, cooling parameters (e.g., heat sinks for controllers, size and power utilization, etc.).

[0412] The operation 5304 of determining the regional architecture value in response to the vehicle network performance description 5702 and the vehicle performance network impact description 5802 may include any decision-making algorithm or optimization route understood in the art. For example, the parameters of the vehicle network performance description 5702 are typically used as a "benefit" function, and the parameters of the vehicle performance network impact description 5802 are typically used as a "cost" function. In some embodiments, the vehicle network performance description 5702 is determined by user input and / or based on the specifications of the vehicle, and the vehicle performance network impact description 5802 is determined in response to the network routing layout, network topology, location of network components, partition architecture communication scheme, and known information about the vehicle and the possible operating environment. In some embodiments, the initial regional architecture value is used as a starting point, which may be: a design input by the user, the design of the previous model year of the vehicle, the design of a similar vehicle, and / or a simple baseline design used as a general starting point. In some embodiments, the process 5300 and / or the operations of similar design processes described in the present disclosure (e.g., but not limited to, Figure 43 , 45, the processes set forth and / or supported in the embodiments and related descriptions in 77 and 93) include working with a set of basic regional architecture values (e.g., star, mesh, ring, 2-node, 3-node, 4-node, etc.) and using the best results from those sets of basic regional architecture values as the initial regional architecture value. If the initial regional architecture value is acceptable, operation 5304 may include using the initial regional architecture value as the determined regional architecture value, potentially highlighting or notifying any aspects of interest, such as the highest cost contributor, the lowest performance parameter, etc. In certain embodiments, the regional architecture value may be adjusted to improve the low performance parameter and / or reduce the highest cost parameter until an acceptable regional architecture value is determined, and / or according to a convergence criterion (e.g., further adjustment achieves improvement below a threshold rate). In certain embodiments, a threshold may be utilized, such as using a baseline installation as a marker and ensuring that the selected regional architecture value has a cost / benefit ratio better than or equal to the baseline (e.g., this will implement continuous improvement over time and / or between model years while minimizing the cycle time to find a regional architecture value solution). In certain embodiments, aspects of the vehicle network performance description 5702 and the vehicle performance network impact description 5802 may be used for indexing or other standardized comparisons, including weighting of the various aspects. In certain embodiments, operation 5304 includes minimizing cost, minimizing certain aspects of cost (e.g., compared to the cost of installed hardware, a luxury vehicle may prioritize low failure rate and high redundancy capabilities), maximizing benefit, maximizing certain aspects of benefit, including similarity to an offset vehicle in a cost / benefit analysis (e.g., biasing the regional architecture values of two different vehicle models to be similar). In certain embodiments, the sensitivity to parameters may be considered in operation 5304, e.g., if the estimation or uncertainty of certain parameters (e.g., vibration distribution) has a high sensitivity to the overall performance or cost of the selected regional architecture value, another alternative of the regional architecture value with slightly worse original cost / benefit characteristics may be selected if that alternative has lower sensitivity (e.g., the risk that the estimated cost / benefit will not be achieved is lower).

[0413] Example process 5300 further includes operation 5306 to integrate a multi-region network on a vehicle in response to the regional architecture value. Refer to Figure 33 , example operation 5306 includes installing a multi-region network configured according to the regional architecture value (e.g., following the regional architecture value as the installed design). Refer to Figure 34 , example operation 5306 includes installing a multi-region network configured according to the network topology description of the regional architecture value (e.g., following the regional architecture value for topology decisions, but potentially varying other aspects, such as accommodating minor differences in supplied components, changes in available space on the vehicle, changes in the actual vehicle environment compared to the estimate, etc.). Refer to Figure 35, Example operation 5306 includes installing a multi-region network configured according to a regional manager distribution description of a regional architecture value (e.g., following the main aspects of the regional architecture value, such as selecting a central regional manager and regional managers for regions, but potentially varying other aspects).

[0414] Reference Figure 38 , Example and non-limiting aspects of the regional architecture value 5902 include: network topology description 5202 (e.g., the number and arrangement of network regions), regional manager distribution description 5904 (e.g., the location and responsibilities of regional managers, including using high-capability endpoints as one or more regional managers, and / or using dedicated regional managers), network type value 5906 (e.g., the type of network to be used, speed capabilities, industrial standards compliance, etc.), network protocol value 5908 (e.g., specific protocol selection, and / or selection of headers, metadata, communication protocols, synchronization selection, etc.) and / or specification values of hardware components 5910 (e.g., capabilities of processors and network communication devices, cable specifications, connector specifications, etc.).

[0415] Reference Figure 39 , An example process 6000 for implementing a regional architecture across more than one vehicle category is schematically depicted. The operations of process 6000 allow vehicle categories to benefit from the generality of the regional architecture design while balancing the costs and benefits of cross-vehicle decisions. Example process 6000 includes operation 6002 for interpreting multiple vehicle network performance descriptions for multiple vehicle categories (e.g., one for each vehicle category), and operation 6004 for determining a regional architecture value in response to the vehicle network performance descriptions and vehicle performance network impact descriptions for each vehicle category (e.g., based on the specific environmental and operating characteristics of each category). Operation 6004 can include any of the considerations elaborated for operation 5304, and in appropriate cases, separate considerations for each vehicle category. The overall cost / benefit analysis can consider the number of vehicles in each category, the economic impact of each category of vehicles (e.g., vehicle cost, downtime cost, specific applications of the category - e.g., ambulance category vehicles may have a different risk acceptance compared to other vehicles). Example process 6000 includes operation 6006 to integrate the multi-region network on vehicles from each vehicle category. As used herein, vehicle category represents any relevant group of vehicles that have common aspects among them for network planning purposes, such as vehicles from the same brand and model year, vehicles for the same application, vehicles targeted at a common geographical region, vehicles belonging to a specific fleet, etc. Process 6000 allows leveraging the flexibility of using a regional architecture to benefit multiple vehicle categories simultaneously while maintaining generality among the vehicles.

[0416] Reference Figure 40, Example operation 6006 includes installing a multi - zone network configured according to the zone architecture value on each of the first vehicle and the second vehicle. Refer to Figure 41 , Example operation 6006 includes installing a multi - zone network configured according to the network topology description of the zone architecture value on each of the first vehicle and the second vehicle (e.g., allowing for variations in specific vehicle classes while leveraging the benefits of the selected topology). Refer to Figure 42 , Example operation 6006 includes installing a multi - zone network configured according to the zone manager distribution description of the zone architecture value on each of the first vehicle and the second vehicle (again allowing for differences between vehicle classes).

[0417] Not limited to any other aspect of the present disclosure, embodiments herein provide systems and processes for implementing a zone network architecture on a vehicle to avoid or mitigate physical system risks, such as due to environmental issues, e.g., temperature, vibration, electromagnetic interference (EMI), road splash (or general water ingress), etc. Additionally or alternatively, the setup and configuration of the zone network architecture on the vehicle can avoid negative consequences and / or improve system results with respect to failure modes, including any failure modes of interest, such as loss of network components (e.g., endpoint failure, communication loss, cable loss, etc.), physical damage to the vehicle that may affect the network (e.g., damage due to an accident, incorrect connection of a tow vehicle, damage to a cable during a service event, electrical damage to the vehicle, etc.).

[0418] Referring again to Figure 29 , Example system 5000 includes a selected zone architecture determined in response to a vehicle network risk description and a vehicle performance network impact description (e.g., the selected zone architecture determined in any of the ways described throughout the present disclosure, e.g., according to Figure 32 or Figure 43 operations). Refer to Figure 43 , An example process 6400 for determining a zone architecture value includes an operation 6402 of determining a vehicle network risk description, e.g., defining the risks of the vehicle network that should be managed and the criteria for determining how well they are managed. Refer to Figure 44, examples and non-limiting aspects of vehicle network risk description 6502 include: hardware redundancy value 6504 (e.g., the hardware components for which redundancy should be provided, and / or the acceptable performance level under redundant hardware operation, e.g., whether the total loss of a network area should be managed with zero capacity degradation); control redundancy value 6506 (e.g., the control components and / or specific endpoints or area managers for which redundancy should be provided, and / or the acceptable performance level under redundant control operation); critical flow description 6508 (e.g., a set of related operations representing a critical flow, and the acceptable redundant performance if lost - note that a given flow may be related to multiple endpoints, and redundancy may be prohibited for each endpoint. Redundancy management for such cases may include aspects such as consolidating control from various endpoints, replacing utilized sensor values with available substitutes (e.g., estimates of lost sensors or virtual sensors), duplicating control capabilities across more than one endpoint, and / or the critical flow description 6508 can be a powerful lever in the location and distribution of network areas); critical application description 6510 (e.g., the applications or features of the vehicle for which redundancy should be available, and the acceptable performance if lost, note that an application can include any relevant functional group, any functional group encapsulated for any purpose, e.g., providing a specific operator experience (e.g., applications for HVAC management, audio-visual system control, navigation, etc.), and in some cases an application may also be considered a flow); critical communication connection description 6512 (e.g., the backbone between two critical network areas, e.g., in the case where powertrain control is distributed between area A and B, then the area A - B communication connection can be considered critical; the critical communication connection description 6512 can include connections between areas, endpoints, controllers, etc.); and / or failure mode description 6514. The failure mode description 6514 can include any scenario, use case, event, etc., that constitutes the failure mode to be protected, and can be determined based on the usage history of similar vehicles, defined by regulations, provided in vehicle specifications, analyzed in a failure mode effects analysis (FMEA), etc. For example, the failure mode description 6514 can include "the front 18 inches of the vehicle are damaged in a collision" and a description of the acceptable performance level after the failure mode. Examples and non-limiting failure mode descriptions 6514 include: specific event descriptions, elimination (loss) of specific components, loss of any component of a single type (e.g., loss of any connector in the system should not result in a function loss greater than XYZ), occurrence of a specific electrical event (e.g., cable XYZ shorted to ground), and / or any type of defined event (e.g., the case where an ECU breaks during a maintenance event; one wire from the network is cut / removed; the vehicle is exposed to a specific intensity of EM field (e.g., near a high-voltage power line), etc.).

[0419] The exemplary process 6400 further includes an operation 6404 to apply the vehicle network risk description 6502 to the currently proposed regional architecture value and determine the vehicle performance network impact description. For example, in operation 6404, the criteria from the failure mode description 6514 are compared to determine the degradation of the vehicle network performance based on the failure mode, and the degraded performance is compared to an acceptable performance level.

[0420] The exemplary process 6400 includes an operation 6406 to determine whether the performance criteria for the regional architecture value have converged. For example, operation 6406 may determine yes if the adjustment of a selected number of regional architecture values does not result in improved performance relative to the vehicle network risk description, and / or the rate of improvement has fallen below a threshold. In some embodiments, for example, where the performance relative to the vehicle network risk description is acceptable, operation 6406 may still be determined to be yes even if further improvement is available, or even if further improvement may be available. In some embodiments, the performance relative to the vehicle network risk description may be forced to be an improvement relative to a baseline (e.g., the previous model year of the vehicle), or at least not a degradation, for example to ensure the pursuit of continuous improvement. In some embodiments, operation 6406 may utilize a complete optimization routine, and / or may include a cost analysis, where the performance relative to the vehicle network risk description is used as the convergence threshold, and as part of operation 6406, the cost is minimized, improved relative to the baseline, and / or kept not exceeding the threshold.

[0421] In response to operation 6406 determining yes, process 6400 includes an operation 6408 to utilize the currently proposed regional architecture value as the regional architecture value. In response to operation 6406 determining no, process 6400 includes an operation 6410 to adjust the regional architecture value based on the performance deficiencies and / or improvement opportunities relative to the vehicle network risk description and / or cost analysis. After operation 6410 that adjusts the proposed regional architecture value, process 6400 returns to operation 6404. In some embodiments, for example, after multiple iterations of operation 6410, and / or after the design space has been fully explored (e.g., the major reasonable network topologies have been considered, etc.) without convergence, process 6400 may determine to exit, for example, providing a notification of the operating parameters (e.g., the attempted regional architecture values, the best results, the gap indication preventing convergence, etc.), for example, allowing the user to consider whether a certain constraint can be relaxed and / or whether the cost limit needs to be adjusted.

[0422] Process 6400 includes an operation 6402 of determining a vehicle network risk description, and a convergence operation 6406 determined based on performance against the vehicle network risk description. In some embodiments, process 6400 may utilize a vehicle network performance description as the value determined in 6402 and for determining the convergence operation 6406, such as to select a regional architecture value to enhance a performance criterion rather than a risk criterion of the vehicle network risk description, or to enhance a performance criterion in addition to the risk criterion of the vehicle network risk description. Similarly, process 6400 may utilize a vehicle performance network impact description as the value determined in 6402 and for determining the convergence operation 6406, such as to select a regional architecture value to enhance a cost criterion rather than a risk criterion of the vehicle network risk description, or to enhance a cost criterion in addition to the risk criterion of the vehicle network risk description. Additionally or alternatively, process 6400 may operate on multiple vehicle classes simultaneously, similar to Figure 39 and the operations described in the related description, e.g., where it would be valuable to drive some commonality into the regional architecture values for different vehicle classes, and / or to utilize common technologies to solve difficult risk management or fault management problems.

[0423] Example system 5000 includes a selected regional architecture in a star arrangement (e.g., refer to Figure 3 and the related description), where one of the network regions includes a central region having a central region manager 302. Example system 5000 includes a selected regional architecture in a mesh arrangement (e.g., refer to Figure 5 and the related description), and may include a central region manager 302. Example system 5000 includes a selected regional architecture in a ring arrangement (e.g., refer to Figure 4 and the related description), and may include a central region manager 302.

[0424] Example system 5000 includes a selected regional architecture in a star arrangement having a total of four regions, including a central region, two forward regions each communicatively coupled to the central region, and a rearward region communicatively coupled to the central region (e.g., refer to Figure 3 and the related description).

[0425] Example system 5000 includes a selected regional architecture in a mesh arrangement having a total of four regions, including a central region (in this example, the central region is the region associated with the central region manager 302 having its responsibilities and is independent of the geometric location of the central region), two forward regions, and a rearward region, where each of the four regions is communicatively coupled to all other regions (e.g., refer to Figure 5 and the related description).

[0426] Example system 5000 includes a selected region architecture that is a ring arrangement, a ring arrangement having a total of four regions that are communicatively coupled in the following order: a central region having a central region manager (in this example, the central region need not also be, but can be, a geometrically central region) is coupled to a first forward region, the first forward region is coupled to a second forward region, the second forward region is coupled to a backward region, and the backward region is communicatively coupled to the central region (e.g., refer to Figure 4 and the associated description).

[0427] Example system 5000 includes a selected region architecture that is a two-node topology, where one of the two nodes is a central region (e.g., refer to Figure 6A and the associated description). Example system 5000 includes a selected region architecture that is a three-node topology, where one of the three nodes is a central region (e.g., refer to Figure 6B and the associated description).

[0428] Example system 5000 includes a selected region architecture that includes at least one of a plurality of regions provided as virtual network regions. Without being limited to any other aspect of the present disclosure, the utilization of one or more virtual network regions provides additional degrees of freedom in the configuration space for the available region architecture values. It will be seen that in most cases, the utilization of virtual network regions reduces the hardware cost value, assuming that there are appropriately located hardware-based network regions on the vehicle that are capable of managing the additional communication load from the messages on the virtual network regions without hardware modifications (e.g., higher-grade cables, network communication devices, shielding requirements, etc.). However, there will be some trade-offs within the design space, such as increased traffic and risks on the hardware-based network regions serving two logical network regions of the vehicle, which may increase the risk associated with failures related to that region, and which may reduce the redundancy options available to respond to certain failure modes or risks. By considering the availability of the additional degrees of freedom of virtual network regions, the results of the convergence operation and / or the overall performance with respect to risk-based, cost-based, or performance-based convergence criteria will be improved, although the utilization of virtual network regions may not be selected for a given vehicle or vehicle class.

[0429] Refer to Figure 45 , which schematically depicts an example process 6600 for integrating a multi-region network on a vehicle. Example process 6600 includes an operation 6602 of interpreting a vehicle network risk description, and an operation 6604 of determining a region architecture value in response to the vehicle network risk description and a vehicle performance network impact description. Example process 6600 also includes an operation 6606 to integrate a multi-region network on the vehicle in response to the region architecture value.

[0430] Without being limited to any other aspect of the present disclosure, embodiments herein provide a system and process for implementing a zonal network architecture on a vehicle to avoid or mitigate system risks involving the loss or degradation of network control components, such as allowing for the selection and / or migration of control responsibility for a zonal network.

[0431] Referring Figure 46 , example system 6700 includes a vehicle having a multi-zonal network that includes a plurality of network zones, each network zone including at least one zone manager, and wherein one of at least one of the zone managers includes a central zone manager (not shown, but system 6700 may be located in any vehicle arrangement set forth throughout the present disclosure). The plurality of network zones are arranged according to a network topology description of a selected zonal architecture. In Figure 46 certain embodiments of the example, in response to a central zone manager non-nominal condition 6702 (e.g., loss of communication with the central zone manager and / or degradation of the central zone manager's capabilities, loss of communication with an endpoint of the central zone and / or degradation of the endpoint's capabilities of the central zone, loss of communication with the central zone and / or degradation of the central zone's capabilities, presence of a fault condition associated with the central zone, etc.), the responsibilities of the central zone manager are migrated. In certain embodiments, system 6700 includes a central zone that is directly communicatively coupled to at least two other zone managers, and in certain embodiments, the central zone is directly communicatively coupled to each other zone manager.

[0432] Example system 6700 includes a network management controller 5002 that includes a zone implementation circuit 5004 that interprets a partitioned architecture communication scheme 5014, a zone manager command circuit 5006 that interprets a zone manager command description 5016 of each zone manager in response to the partitioned architecture communication scheme 5014, and a zone execution circuit 5008 that provides a corresponding zone manager command description 5016 to each zone manager. Example system 6700 includes each zone manager that responds to a corresponding zone manager command description 5016 to control communication between endpoints of a corresponding network zone and endpoints of at least one other zone of the network zone. Example system 6700 includes a network management controller 5002 that is at least partially located on the central zone manager.

[0433] Example partitioned architecture communication scheme 5014 includes a central area manager succession scheme, which can include information such as which central area manager non-nominal condition 6702 indicates that the central area manager responsibilities should be moved to another area controller, and which central area manager responsibilities should be included in the move. For example, in some embodiments, the central area manager can have responsibilities such as the following: operating as the area manager of the central area; distributing area manager command descriptions 5016 to other area managers; maintaining a service registry and / or managing the publication and registration of a service-oriented architecture (SOA, e.g., refer to Figures 67 - 72 and related descriptions); operating as the PTP master for network time management operations (e.g., refer to Figures 73 - 76 and related descriptions); and / or hosting one or more or all aspects of the network management controller 5002. In some embodiments, some of these responsibilities (if any) can migrate to an alternative area controller in response to the central area manager non-nominal condition 6702, but others do not. For example, in a given embodiment, one or more of these responsibilities may not be performed by the central area manager. In another example, a designated successor area manager may perform a set of responsibilities (e.g., distributing area manager command descriptions 5016), but may not be the best fit for another set of responsibilities (e.g., operating as the PTP master). In some embodiments, the central area manager succession scheme can include migrating some responsibilities to a first area controller and other responsibilities to one or more other area controllers. In another example, some responsibilities of the central area manager may not be available for migration, such as operating as the area controller of the central area, e.g., in the case of a loss of communication with the central area as part of the central area manager non-nominal condition 6702. It will be seen that for certain responsibilities of the central area manager, the ability to migrate responsibilities will not be available if the successor area manager does not already have some available data that may be stored on the central area manager and may thus potentially become unavailable as part of the central area manager non-nominal condition 6702. For example, if the central area manager maintains a service registry, the service registry may be lost with the central area manager. Therefore, in some embodiments, the central area manager succession scheme of the partitioned architecture communication scheme 5014 includes, in some embodiments, data that the successor area manager maintains as a backup at all times, and / or maintains a backup that is updated regularly. Examples of such backup data include, but are not limited to, policies, policy portions related to the partitioned architecture communication scheme, and / or service registries.

[0434] The example area execution circuit 5008 determines a non-nominal condition 6702 of the central area manager and, in response to a central area manager succession scenario, migrates the central area manager responsibilities to another area manager (e.g., by providing an area manager migration command 6704 to the successor area(s)). In some embodiments, the operation of providing the area manager migration command 6704 may instead be performed by the hardware redundancy implementation circuit 5010 or the control redundancy implementation circuit 5012.

[0435] Reference Figure 47 , the example partition architecture communication scenario 5014 includes one or more aspects, such as: area manager communication responsibilities 6802 (and / or a subset of those responsibilities intended for migration); area manager security responsibilities 6804 (e.g., registration services, permissions to communicate with external devices, and / or permitted or prohibited external addresses, as well as security parameters for each area and area manager); area manager local profiles 6806; area manager global profiles 6808 (e.g., configuration aspects that are common to area managers and apply to all network areas, which are, for example, parsed from policies as stored records and / or facilitate future parsing operations for policy updates, etc.); central area manager succession scenarios 6810 (e.g., criteria for determining the non-nominal condition 6702 of the central area manager, responsibilities to be migrated, and successor local managers); network security descriptions 6812 (e.g., security policies that are globally applied and / or specific to central area manager responsibilities); and / or network connectivity descriptions 6814 (e.g., communication routes for messages from endpoints, areas, flows, applications, etc., including redundancy descriptions to be utilized during various non-nominal events in the network).

[0436] In some embodiments, the network topology description includes a communicatively coupled arrangement of network areas. Example and non-limiting network topology descriptions include communicatively coupled arrangements as star arrangements, mesh arrangements, and / or ring arrangements. It will be understood that in a pure star arrangement (e.g., where there are no backup connections between areas, such as unused or rarely used backup connections, where in operation, even with additional hardware connections, a multi-area network operates logically as a star arrangement), if the central area manager is also the hub area of the star arrangement, the loss of the central area manager will prevent the migration of most of the central area manager's responsibilities because the network areas will become isolated. In some embodiments, even in the case where the network areas become isolated, some operations of the vehicle are possible, depending on the redundancy planning of the system and the ability of the independent areas to operate using these redundancy plans without any cross-network communication. If another area manager acts as the hub area of the star arrangement, then the loss of the central area manager in the star arrangement will allow the migration of the central area manager's responsibilities.

[0437] Reference Figure 48 illustrates, schematically, an example process 6900 for operating a multi - zone network on a vehicle. The example process 6900 includes an operation 6902 of interpreting an operation of a partitioned architecture communication scheme, an operation 6904 of responding to the partitioned architecture communication scheme to interpret a zone manager command description for each zone manager, an operation 6906 of providing the zone manager command description to the zone manager, and an operation 6908 of operating each zone manager in response to a corresponding zone manager communication description (e.g., controlling communication between endpoints on different network zones). Reference Figure 49 , the example operation 6904 includes, in response to the partitioned architecture communication scheme, interpreting a central zone manager command description of a central zone manager, e.g., where the central zone manager command description includes one or more central zone manager responsibilities.

[0438] Reference Figure 50 , the example process 7100 includes the process 6900 and further includes an operation 7102 of interpreting a central zone manager succession scheme (e.g., according to the partitioned architecture communication scheme), an operation 7104 of determining a non - nominal condition of the central zone manager, and an operation 7106 of migrating one or more central zone manager responsibilities to another zone manager(s) in response to the central zone manager succession scheme.

[0439] Without being limited to any other aspects of the present disclosure, embodiments herein provide systems and processes for implementing a zone network architecture on a vehicle to enhance system security, including providing the ability to physically or logically isolate critical endpoints or communications from non - critical endpoints to provide enhanced capabilities and greater control of features to more parties involved with the vehicle (e.g., owner, dealer, fleet manager, service personnel), while still maintaining the ability to secure communications and manage critical communications for network - managed vehicle tasks. Additionally, security responsibilities can be assigned, allowing for rapid updates, immediate response to changes, etc., while maintaining the simplicity and security of centralized control.

[0440] Again referring Figure 29 , the example system 5000 includes a vehicle having a multi - zone network including a plurality of network zones, each network zone including at least one zone manager, and where at least one of the at least one zone managers includes a central zone manager. The network zones are arranged according to a network topology description of a selected zone architecture; and the central zone manager includes a network management controller 5002. The network management controller 5002 includes a zone implementation circuit 5004 that interprets a partitioned architecture communication scheme 5014, where the partitioned architecture communication scheme 5014 includes a network security description 6812 (reference Figure 51) and network connectivity description. The network management controller 5002 also includes a zone manager command circuit 5006 and a zone execution circuit 5008. The zone manager command circuit 5006 interprets the zone manager command description 5016 of each zone manager in response to the partition architecture communication scheme 5014, and the zone execution circuit 5008 provides the corresponding zone manager command description 5016 to each zone manager. The example system 5000 includes each zone manager that responds to the corresponding zone manager command description 5016 to control communication between the endpoints of the corresponding network zone and the endpoints of at least one other zone. In certain embodiments, the central zone manager is directly communicatively coupled to each other zone (e.g., in a star configuration, a mesh configuration, or a hybrid configuration).

[0441] The example system 5000 includes a zone implementation circuit 5004 that interprets a partition architecture communication scheme update (e.g., as a new partition architecture communication scheme 5014), wherein the zone manager command circuit 5006 further interprets the zone manager command description 5016 of each zone manager in response to the updated partition architecture communication scheme 5014, and wherein the zone execution circuit 5008 provides the corresponding updated zone manager command description 5016 to each zone manager. In certain embodiments, the zone execution circuit 5008 provides the corresponding updated zone manager command description 5016 during runtime operation (e.g., once a partition architecture communication scheme update is received). In certain embodiments, the updated zone manager command description 5016 is implemented immediately, e.g., in the case where the updated zone manager command description 5016 is a configuration file without software changes, and in the case where the operations represented within the updated zone manager command description 5016 allow runtime changes. In certain embodiments, the updated zone manager command description 5016 includes a flag indicating whether they should be implemented immediately or upon the next vehicle startup event, where the flag may be provided as part of the partition architecture communication scheme 5014, and / or may be determined by the zone manager command circuit 5006 (e.g., by filtering certain types of changes indicating that immediate runtime changes should not be implemented). In the case where the updated zone manager command description 5016 is implemented during a subsequent startup event, the operation of the system 5000 still contributes to the ease and speed of updates relative to previously known systems, since each zone manager already has the appropriate commands available for immediate implementation.

[0442] Reference Figure 51 , the example network security description 6812 includes permission values for aspects of the network control operations described herein. Figure 51The permissions depicted are actor-based permissions, or permissions based on associated actors (e.g., applications, flows, endpoints, network regions, functions, etc.). Examples and non-limiting permission values for network security description 6812 include: network region permission value 7202 (e.g., permissions associated with a network region, including, for example, data permitted on the region, including from various sources such as endpoints, flows, applications, functions; bandwidth permissions for the region and / or various sources, including absolute and / or relative bandwidth permissions; inter-region communication restrictions including data rates to or from the region, and / or various sources permitted to communicate between specified regions; and / or types of traffic permitted on the region, such as highly sensitive data, audiovisual data, etc.); flow permission value 7204 (e.g., permissions associated with a flow, including whether the actor of the flow is the source or destination of a message, where flow permissions can relate to permissions on a specific region, between specified regions, etc., and where the actor of the flow is an endpoint, application (e.g., an algorithm operating on a controller, where the algorithm is part of the flow, but the controller may not be, e.g., in an embodiment with a containerized control element)); application permission value 7206 (e.g., permissions associated with an application); function permission value 7208 (e.g., permissions associated with the operation of certain logical groupings that can be performed between various sources and are logically grouped into applications, such as "vehicle traction management"); and / or endpoint permission value 7210 (e.g., permissions associated with endpoints such as sensors, actuators, controllers, etc., present on the network as endpoints on a network region). It will be seen that a given message can have multiple tags that are at least conceptually available, e.g., a message provided from endpoint A can also be part of flow B and application C. Arbitration of these instances can be performed according to the policies and / or criteria set forth in the partitioning architecture communication scheme and can follow rules such as "the highest permission association wins" or "the lowest permission association wins". The rules can be more complex, e.g., certain applications can make their permission values decisive regardless of other associated flags. In another example, a message associated with a certain application can have a high permission value if provided by a first endpoint, but a low permission value if provided by another endpoint. Additionally or alternatively, all flags can be available with the message (e.g., based on metadata), and / or only the winning flag can be retained in the message. The utilization of permission values and arbitration between competing permission values can be determined based on the security scheme of the system and the purpose of arbitrating permission values. Generally, rules and arbitration schemes will be selected to ensure that critical messages for important functions or applications will be sent from the appropriate source or to the appropriate destination each time, but they will not be available to inappropriate sources or destinations.

[0443] Reference Figure 52 , depicts example and non-limiting permission value 7302. Figure 51Examples allow the permission to be based on the source or destination of the message (actor-based permission), while Figure 52 Examples provide that the permission values can be used for actions to be performed or restricted and can be applied to any actor-based permission. Example and non-limiting permission values include one or more of the following: data provider permission 7306 (e.g., whether the actor is allowed to make the data available as a provider of the data); data recipient permission 7308 (e.g., whether the actor is allowed to receive the data); communication bandwidth permission 7304 (e.g., whether the actor is allowed to consume bandwidth resources such as network areas, area managers, etc.); service subscription permission 7310 (e.g., whether the actor is allowed to subscribe to a service); service provider permission 7312 (e.g., whether the actor is allowed to provide a service); service visibility permission 7314 (e.g., whether the actor is allowed to make the service visible, where it is possible that the actor can make the service visible but not provide it, or provide the service but not make it visible, such as a deprecated service - refer to Figure 47 and 50 , and related descriptions); service publication permission 7316 (e.g., whether the actor is allowed to publish a service, which is a concept similar but different from the visibility of the service); and / or endpoint communication permission 7318 (e.g., whether a given endpoint is allowed to send a message to or receive a message from another specified endpoint or another class of endpoints). In some embodiments, the permission can further be based on the category of the actor - for example, the service publication permission 7316 can specify that the actor is allowed to publish a service to other actors with permission category A, but not to actors with permission category B. Figure 51 and 52 All permissions depicted in

[0444] refer to Figure 53, depicts an example connectivity scheme 7402, provided, for example, as part of a network connectivity scheme. The example connectivity scheme 7402 can relate to connectivity between network regions, e.g., the connectivity scheme can apply to inter-region communication between network regions A and B, where the associated region manager applies the region manager command description 5016 to implement the corresponding connectivity scheme 7402. Note that any connectivity scheme 7402 can be anisotropic, e.g., A→B communication can have a first rate limit while B→A communication can have a different rate limit (e.g., network region A can be a critical network region that is allowed to control outgoing utilization while restricting incoming utilization). Further note that any connectivity scheme 7402 can be based on an origin endpoint value and / or a destination endpoint value, e.g., a particular controller on the network can have a particular criterion for a message to be sent there, where the criterion for that endpoint can override and / or adjust one or more aspects of the connectivity scheme 7402. For example, communication from region A→B can have a general scheme using SI units for messages, where endpoint Z has a requirement for US engineering units, which can override the general scheme for messages destined for endpoint Z (e.g., depending on how the partitioned architecture communication scheme is constructed, permissions associated with endpoint Z or related applications or flows, etc.). Further note that any connectivity scheme 7402 can be based on the (one or more) network types involved, e.g., A→B communication and A→C communication can have different values of the connectivity scheme 7402 based on the network types of B and C. In another example, D→A communication and E→A communication can have different values of the connectivity scheme 7402 based on the network types of D and E.

[0445] Example and non-limiting connectivity scheme 7402 includes one or more of the following: a communication rate value 7404 (e.g., the data rate permitted between network regions, including burst rate and / or time-averaged rate); a communication protocol value 7406 (e.g., the communication protocol to be applied or followed for messages between regions); a sampling rate value 7408 (e.g., the message rate to be utilized, and / or the dynamics to be reflected in the data, which can be adjusted through upsampling or downsampling operations, e.g., providing a 20 millisecond vehicle speed value on a CAN with limited capabilities to an endpoint that expects 20 millisecond data and does not have the ability to parse the time data from the message); a communication header value 7410 (e.g., the form, size, and content of the header information of the message); a communication metadata value 7412 (e.g., the form, size, and content of the metadata of the message); a communication unit value 7414 (e.g., units such as SI units, US engineering units, etc., and / or the scaling of unitless data, e.g., for fixed-point data; in some embodiments, the byte depth and / or type of the data can be specified in the connectivity scheme 7402); a communication encapsulation description 7416 (e.g., specifying whether the communication should be encapsulated, e.g., retaining the original CAN message in an Ethernet message to allow CAN-CAN communication through an intervening network, retaining the original metadata in the message for monitoring or later analysis, etc.); and / or a communication timestamp description 7418 (e.g., the size, location, and format of the timestamp, the utilization of a PTP timestamp, the retention or elimination of any local timestamp previously associated with the message, etc.).

[0446] Reference Figure 54 , schematically depicts an example process 7500 for controlling communication between endpoints of a multi-region network of a vehicle. Example process 7500 includes operations 7502 for interpreting the operation of a partition architecture communication scheme of a multi-region network of a vehicle including a plurality of network regions, operations 7504 for responding to the partition architecture communication scheme to interpret the region manager command descriptions of each region manager, operations 7506 for providing corresponding region manager command descriptions to each region manager, and operations 7508 for controlling communication between endpoints of each of the plurality of network regions in response to the region manager command descriptions.

[0447] Reference Figure 55 , example operations 7504 include operations 7602 for parsing the policy including the partition architecture communication scheme, and operations 7604 for determining the relevant region manager command descriptions of each region manager in response to the policy. Reference Figure 56 , example operations 7506 include transmitting the corresponding command descriptions from a central region manager to each individual region manager.

[0448] Reference Figure 57, the example process 7800 includes process 7500 and further includes an operation 7802 to explain the update of the partition architecture communication scheme, an operation 7804 to explain the updated area manager command descriptions of each area manager in response to the update of the partition architecture communication scheme, and an operation 7806 to provide the corresponding updated area manager command descriptions to each area manager. Refer to Figure 58 , the example process 7900 further includes an operation 7902 to control the communication between the endpoints of each network area in response to the updated area manager command descriptions. Refer to Figure 59 , the example process 8000 further includes an operation 8002 to immediately start controlling the communication between the endpoints of the network area in response to the updated manager command descriptions. Refer to Figure 60 , the example process 8100 further includes an operation 8102 to start controlling the communication between the endpoints of the network area in response to the updated manager command descriptions and a subsequent vehicle start event. Refer to Figure 61 , the example process 8200 further includes an operation 8202 and an operation 8204. The operation 8202 determines the implementation solution in response to the updated area manager command descriptions, and the operation 8204 starts controlling the communication between the endpoints of each network area in response to the updated area manager command descriptions and further in response to the implementation solution.

[0449] Without being limited to any other aspects of the present disclosure, the embodiments herein provide systems and processes for implementing a regional network architecture to simplify and enhance network communication control in the regional network architecture. For example, the systems and processes herein provide embodiments that allow endpoints with different communication payloads, metadata, device capabilities, etc. on different regions to communicate in a secure manner, which is operable and easily configurable given the additional complexity of the partitioned network environment. The systems and processes herein protect the ability of the regional network architecture to perform critical functions and support flexible additional functions, such as by balancing the load and utilization of network components such as the backbone and area controllers.

[0450] Refer to Figure 29 , the example system 5000 includes a partition architecture communication scheme 5014, which includes a network security description and a network connectivity description. Refer to Figure 62, an example network connectivity description 6814 includes one or more of the following: an inter-region bandwidth description 8302 (e.g., the permitted bandwidth between selected regions, which can be anisotropic); an inter-region network routing value 8304 (e.g., some communications passed between regions can be routed through other regions first, and / or some communications passed between regions can have multiple available routes, and the inter-region network routing value 8304 provides the route to be utilized, and the route can be anisotropic and can vary depending on the message and the actors involved in the message); an inter-region priority value 8306 (e.g., the priority of messages between regions based on such regions, and / or routing or other connectivity aspects depending on the priority of the message and / or the priority associated with the actors involved in the message); and / or an inter-region permission value 8308 (e.g., the permission associated with a message based on such regions associated with the message, and / or the permission associated with the message depending on the permission associated with the message and / or the actors involved in the message). In some embodiments, any one or more of the network connectivity descriptions 6814 can be further determined in response to the operating condition of the vehicle. For example, a message can be of low priority and / or routed in a first manner in a first operating condition (e.g., parked vehicle condition), and high priority and / or routed in a second manner in a second operating condition (e.g., driving vehicle condition). The inter-region permission value 8308 can include any aspect of the permission values set forth throughout the present invention, including but not limited to sampling rate description, data resolution description, or data latency description.

[0451] Reference Figure 63 , an example process 8400 includes: an operation 7502 for interpreting a partitioned architecture communication scheme of a multi-region network of a vehicle including a plurality of network regions, the partitioned architecture communication scheme including a network security description and a network connectivity description; an operation 8402 for determining a bandwidth description of the network connectivity description of at least one element (e.g., an endpoint, a flow, a function, or an application); and an optional operation 8404 for further determining the bandwidth description in response to the vehicle operating condition.

[0452] Reference Figure 64 , an example process 8500 includes: an operation 7502 for interpreting a partitioned architecture communication scheme of a multi-region network of a vehicle including a plurality of network regions, the partitioned architecture communication scheme including a network security description and a network connectivity description; an operation 8502 for determining a network routing value of the network connectivity description of at least one element (e.g., an endpoint, a flow, a function, or an application); and an optional operation 8504 for further determining the network routing value in response to the vehicle operating condition.

[0453] Reference Figure 65, example process 8600 includes: operation 7502 for interpreting a partitioned architecture communication scheme of a multi-area network of a vehicle including multiple network areas, the partitioned architecture communication scheme including a network security description and a network connectivity description; operation 8602 for determining a priority value for the network connectivity description of at least one element (e.g., an endpoint, a flow, a function, or an application); and an optional operation 8604 for further determining the priority value in response to a vehicle operating condition.

[0454] Reference Figure 66 , example process 8700 includes: operation 7502 for interpreting a partitioned architecture communication scheme of a multi-area network of a vehicle including multiple network areas, the partitioned architecture communication scheme including a network security description and a network connectivity description; operation 8702 for determining a permission value for the network connectivity description of at least one element (e.g., an endpoint, a flow, a function, or an application); and an optional operation 8704 for further determining the permission value in response to a vehicle operating condition.

[0455] Without being limited to any other aspect of the present disclosure, embodiments herein provide systems and processes for implementing a regional network architecture to simplify and enhance network communication control in the regional network architecture. For example, the systems and processes herein provide embodiments implementing security and permission schemes for network selection without requiring the user to fully understand the location of all endpoints on the network and / or all data within the network. In addition, embodiments herein allow the user to create or adjust the security and permission schemes of the entire regional network through simple operations on a single access point, and to adjust mitigation plans such as redundancy implementation and / or succession of responsibility through simple operations on the single access point.

[0456] Reference Figure 67 , example system 8800 is used to operate a service-oriented architecture of a vehicle (not shown) having a multi-area network including multiple network areas, each network area including at least one area manager, and wherein the multiple network areas are arranged according to a network topology description of a selected area architecture. System 8800 includes a service management controller 8802, including: a service registration circuit 8806 that maintains a service registry 8902 including multiple services and service descriptions for each service (Reference Figure 68) ; A service publishing circuit 8810 that presents at least one service from multiple services to a requester source 8908 in response to a service publishing request 8906; and a service subscription circuit 8808 that registers the requester source 8908 (e.g., it can be the same or a different source. The requester source 8908 is the source of a given request for at least one service (which can be a publishing request and / or a subscription request) in response to a service subscription request 8904, and updates the service registry 8902 in response to the registration. The system 8800 also includes a network management controller 8804, including: a region implementation circuit 8812 that interprets the partition architecture communication scheme 5014, a region manager command circuit 8814 that interprets each region manager command description 5016 of the partition architecture communication scheme in response to the partition architecture communication scheme, and a region execution circuit 8816 that provides the corresponding region manager command description 5016 to each region manager. The region manager controls the communication between the endpoints of the corresponding network region and the endpoints of at least one other region in the multiple network regions in response to the corresponding region manager command description 5016 and the service registry 8902.

[0457] The example system 8800 includes a service management controller 8802 that is at least partially located on a central region manager of the region manager. The example central region manager is directly communicatively coupled to each other region manager. The example system 8800 includes a network management controller 8804 that is at least partially located on the central manager.

[0458] Reference Figure 69, schematically depicts a non - limiting example of service 9002. Example service 9002 includes any data values available on the system and / or determinable from data available on the system, and additionally or alternatively may include any functionality, available actions, etc. The service can be provided by any actor on the vehicle, typically from an endpoint that makes the service available for registration, where another actor on the vehicle can use the service once registered (e.g., start receiving messages, exercising functionality, etc.). Permissions can be associated with any aspect of the service, for example, permissions can be applied to provide the service, make the service visible, publish the service (including the scope of visibility or publication), check if the service is available, register for the service, etc. Examples of service 9002 include: data value 9004, mathematical function 9006 (e.g., providing mathematical functions that may be helpful or commonly utilized on the vehicle, where using the function as a service can allow transfer of processing resources between devices in the system, and / or allow an actor on the system to provide the function as a black box, where other actors can call the function and obtain a return value, but the actual operations being performed need not be visible. Example functions include any moderately complex functions, such as mean determination, trigonometric expressions, and / or functions that may require access to certain system aspects that are not normally available, such as a random number generator based on system time or another sub - parameter), processing function 9008 (e.g., providing a complex processing function that can be utilized, which can again transfer processing resources within the system, hide proprietary functions in a black box, and / or allow complex operations that are rarely used to be centralized and managed from a single location).Example functions include dynamic processing of data streams, such as upsampling or downsampling operations and / or dynamic filtering operations for smoothing, feature detection, and / or frequency bands, interpolation, spline fitting, Fourier or other frequency analysis operations, operations on target search or optimization algorithms for an input set, operations on lookup tables and / or conversion of lookup tables to analysis models, data compression operations, sparse data reconstruction, operations on compensation algorithms for aging or degraded sensors, etc.); communication functions (e.g., encapsulating communication for use elsewhere in the system, especially, for example, for low-capability devices and / or area managers or switches, performing encapsulation operations for communication (e.g., encapsulating, adding or deleting headers, metadata, timestamps, etc.) will be "expensive" operationally); data storage functions (e.g., allowing subscribers to check in, check out, change stored values, retrieve stored values, etc.; for example, allowing low-capability devices to borrow data storage from higher-capability devices with low implementation overhead, and / or using such storage for infrequent but potentially large data operations, such as intermediate data temporarily stored during calculations, short-term storage buffers, etc., for many applications, such data storage services will be "expensive" in terms of capability and implementation cost, but useful in a mixed environment of high-capability and low-capability legacy devices, which may stay in the system for several years, with the possibility of replacement at any point, and the replacement will likely roll out gradually across a set of vehicle categories); actuator functions 9014 (e.g., allowing a device to control an actuator, a service providing actuator control can limit the scope and / or dynamics of actuator control through this service, e.g., relative to the basic control of the available actuator; in addition, the service can divide priorities among multiple registrants of the service, e.g., by forcing "checkout" of the actuator, applying hysteresis between multiple requests to prevent jitter or other potentially undesirable operations, and / or being utilized by higher-priority users over lower-priority users); command functions 9016 (e.g., allowing various system command services, such as requesting system status (e.g., which vehicle governor is currently active), setting the status of some parameters - e.g., headlights on, retrieving diagnostic values or status, etc.); and / or control functions 9018 (e.g., allowing access to some control parameters, such as for observing potential adjustments, which can be within the allowed range depending on the actor requesting the service, e.g., a vehicle owner convenience application allowing a user to adjust the cruise control minimum speed can have a different range of capabilities from an engineering tool application using the same service, in another example, a parent can allow a teenage driver to adjust the vehicle maximum power or maximum speed, but within a limited range, etc.). It will be seen that some parameters accessed or adjusted by service 9002 can be understood as data values, command functions, or control functions (e.g., setting the headlight value to request the headlights to be on can be understood as a control function, a command function, or an actuator function).The specific categories of Service 9002 are not important; together, these categories illustrate various aspects of vehicles, networks, endpoints, applications, etc. that can be implemented by using Service 9002. In some embodiments, Service 9002 can be a complex function, such as participating in an ADAS system, requesting an automated parallel parking operation, etc., while other Services 9002 can be very simple services that extend the capabilities of low-capability devices, transfer processing resources within the system, simplify repetitive or complex tasks, and / or reduce the development and maintenance of common processes at a single location.

[0459] Reference Figure 70 , schematically depicts an example illustrative data structure of a service registry 8902. In some embodiments, the service registry 8902 keeps track of the services available on the system, whether the services are published, who registered the services, etc. Some fields in the service registry 8902 can be informational rather than active, such as a service capability description that can be a text field for display on a user device (e.g., services available to the user, such as displayed on a service tool, engineering tool, mobile device, etc.), where other fields can be active, such as a service ID that can be an actual identifier, e.g., used by a service management controller 8802 to specifically identify and track Service 9002. For each of the multiple services, the example service registry 8902 includes at least one of the following: a service identifier; a service provider description; a service license description; or a service capability description. For each of the multiple services, the example service registry 8902 also includes at least one of the following: a service input description; a service active or inactive flag; a service deprecation flag; a service registrar description; or a service participant description (e.g., other endpoints, controllers, applications, etc. that are accessed by the service provider as part of the service operation).

[0460] The example service publishing circuit 8810 exposes one or more Services 9002 by listing the service registry 8902 in a data structure provided to a requester source. For example, the requester source can request a list of Services 9002, and / or can be periodically provided with a list of Services 9002. The data structure provided to the requester source is based on the service registry 8902, but will be limited to the services that the requester source has the right to view and / or subscribe to, and / or the Services 9002 that the requester source may be interested in.

[0461] The example service publishing circuit 8810 presents one or more services 9002 by listing the services 9002 at a known location (e.g., a memory location accessible to actors on the network). In some embodiments, multiple data structures with service listings may be provided, e.g., based on the common permission categories of actors on the network. For example, a first permission category may allow access to a first table that lists only services for accessing low-security data or functions, while a second permission category may allow access to a second table that lists services for accessing more sensitive data or functions. There may be any number of permission categories. In some embodiments, a service listing may be created in response to a request, where the services are filtered according to the overall permission scheme applicable to the requester source. The requester source may be any actor on the system (e.g., an endpoint, an application, a flow, a controller, etc.), and / or may include actors outside the system (e.g., a user interacting with an external device, such as a tool in the cloud or a service tool communicating with a vehicle, that requests a service for providing data or allowing the user to access a function), and will similarly be subject to the appropriate permission scheme applicable to the user, the external device, and / or the tool used to request the service. In some embodiments, the service provider may be an external device, e.g., allowing in-vehicle actors to access data, processing functions, or any other service aspect provided by the external device (again subject to the publication and other permissions applicable to the external device).

[0462] The example service publishing circuit 8810 interprets a service publishing request 8906 for a new service from a new service provider (e.g., a provider of a new service, which may be a new requester source or a requester source that publishes a new service), determines a new service description in response to the service publishing request 8906 and the new service provider (e.g., determined from data fields in the service publishing request 8906, and / or interpreted from the operations performed by the service), and maintains a service registry 8902 by adding the new service 9002 as one of the services in the registry.

[0463] The example service publishing circuit 8810 also adds the new service to the service registry 8902 in response to a permission value associated with the new service provider, e.g., denying the request, adding the service to the service registry 8902 but not publishing the service, and / or by making an appropriate entry in the permission field of the service registry 8902 (e.g., specifying the visibility of the service and / or the registered permissions).

[0464] The example service publishing circuit 8810 maintains the service registry 8902 by removing a service from among multiple services in response to a service publishing request 8906. The service publishing request 8906 can include deleting an associated entry from the service registry 8902, adjusting the service registry entry such that the service is no longer visible or published, and / or setting an inactive flag in the associated entry from the service registry 8902 (e.g., thereby allowing tracking of services that have been available, and / or simplifying the process of later reactivating the service).

[0465] The example service publishing circuit 8810 maintains the service registry by deprecating a service from the services in the service registry in response to a service publishing request 8906 (e.g., in the case where the service publishing request 8906 is a request to stop publishing the service). As used herein, deprecating a service allows registered actors registered at the time of deprecation to continue to utilize the service, but does not allow new requesters to see or utilize the service 9002, and prevents further registration of the service. The deprecation operation allows the service to be phased out of the system according to established rules as registered actors stop using the service 9002. As used herein, making the service 9002 inactive does not necessarily remove the registration status of the requester, but the service 9002 will not be utilized unless and until the service is reactivated.

[0466] The example service publishing circuit 8810 also maintains the service registry 8902 by removing a service from the available services in response to determining that at least one aspect of the service is no longer available (e.g., the endpoint used by the service no longer exists, the service registrant no longer receives the benefits of the service, and / or the service provider appears unresponsive to the service 9002). In some embodiments, removing the service from the available services includes setting an inactive flag and / or deleting the entry for the service 9002 from the service registry 8902.

[0467] Once a service is active, a registrant can participate in the service either actively or passively, depending on the nature and configuration of the service. For example, utilizing the service 9002 can involve passively receiving data, which can be sent directly from the service provider to the registrant as a data communication, and / or the data can be sent to the service management controller 8802 for storage at a location accessible to the registrant when needed or convenient. In another example, the service can involve a call from the registrant, such as passing data parameters for a notification service - e.g., numbers passed to the service provider and function values returned after the call, parameters for actuator settings requested by the registrant, and / or data blocks for processing (e.g., a stream of data values on which the service operates). In some embodiments, the service registry 8902 stores service call formatting and information, which can then be used by the registrant to utilize the service 9002.

[0468] In some embodiments, the service license description includes a service publishing license, a service subscription license, and / or a service visibility license. In some embodiments, the service registry 8902 may be stored on an external device that may be attached to a local version of the service registry 8902. In some embodiments, the service registry 8902 stored on the external device may be different from the local version, e.g., having only the actively listed services externally, and / or having the services listed on the external device removed from the local version.

[0469] Reference Figure 71 , example process 9200 includes: operation 9202 for maintaining a service registry on a vehicle having a multi-region network including a plurality of network regions and including a plurality of services and service descriptions for each of the plurality of services; operation 9204 for presenting to a requester source at least one service from the plurality of services in response to a service publishing request; operation 9206 for registering the requester source with at least one service in response to a service subscription request and updating the service registry in response to the registration; operation 9208 for interpreting a partitioned architecture communication scheme; operation 9210 for interpreting, in response to the partitioned architecture communication scheme, a region manager command description for each of the at least one region manager (e.g., adjusting the region manager command description based on activities performed for the service); operation 9212 for providing a corresponding region manager command description to each of the at least one region manager; and operation 9214 for controlling communication between endpoints of a corresponding network region and endpoints of at least one other region of the plurality of network regions in response to the corresponding region manager command description and the service registry.

[0470] Example operation 9204 of presenting at least one service includes: listing the service in a data structure provided to the requester source; and / or listing the service in a data structure available to the requester source.

[0471] Reference Figure 72 , example process 9300 includes process 9200 and further includes: operation 9202 for interpreting a service publishing request for a new service from a new service provider; operation 9204 for determining a new service description in response to the service publishing request and the new service provider; and operation 9206 for maintaining the service registry by adding the new service as one of the plurality of services.

[0472] Without being limited to any other aspect of the present disclosure, embodiments herein provide systems and processes for implementing a regional network architecture for time management to control communication on a network, including time management for control purposes (e.g., operation synchronization between distributed controllers) and / or for data analysis (e.g., comparing data streams to detect events, planning or implementing diagnostic or troubleshooting operations, etc.).

[0473] ReferenceFigure 73 , example system 9400 includes a vehicle (not shown) having a multi-zone network including multiple network zones, each network zone including at least one zone manager; and a network management controller 5002, including: a zone implementation circuit 5004 that interprets a partitioned architecture communication scheme 5014, the partitioned architecture communication scheme 5014 including a time management scheme 9502 (refer to Figure 74 ); a zone manager command circuit 5006 that, in response to the partitioned architecture communication scheme 5014, interprets a zone manager command description 5016 for each of the at least one zone manager, the zone manager command description 5016 further including a time management implementation 9402; and a zone execution circuit 5008 that provides a corresponding zone manager command description 5016 to each of the at least one zone manager; and wherein each of the at least one zone manager responds to the corresponding zone manager command description 5016 to control communication between endpoints of the corresponding network zone and endpoints of at least one other zone among the multiple network zones.

[0474] Example system 9400 includes a time management scheme that includes designating one of the zone managers as the Precision Time Protocol (PTP) grandmaster operation for the multi-zone network. Example system 9400 may also include other zone managers designated as boundary clocks for the corresponding network zones. In some embodiments, the central zone manager may act as the PTP grandmaster operation for the multi-zone network, but any other zone manager may act as the PTP grandmaster operation, where the central zone manager operates as the boundary clock for the central zone.

[0475] In some embodiments, one or more endpoints may instead operate as clocks for a given zone, including as the PTP grandmaster for the multi-zone network, and one or more endpoints may operate as boundary clocks for their respective zones. In some embodiments, a selected mix of endpoints and / or zone managers may operate as clocks, including the PTP grandmaster and / or boundary clock for each zone.

[0476] The example system includes a zone implementation circuit 5004 that operates an optimal master clock algorithm to determine a designated one (or more) of the zone managers and / or endpoints to act as the PTP grandmaster operation. In some embodiments, the zone implementation circuit 5004 may also operate the optimal master clock algorithm for endpoints and zone managers of a given zone to determine and designate the boundary clock for the given zone. In some embodiments, the optimal master clock algorithm may operate remote from the vehicle, such as at Figure 78 and 93and operate in the construction environment and / or monitoring environment depicted in the relevant description to determine the optimal PTP grandmaster and / or boundary clock. In some embodiments, the optimal PTP grandmaster and / or boundary clock can be determined based on certain criteria, such as, based on the criticality of the functions performed on a given area (e.g., important and / or high-rate functions, such as powertrain control can drive the selection of the PTP grandmaster for that area), and / or based on the sensitivity of the functions performed on a given area (e.g., functions with extreme time sensitivity can drive the selection of the PTP grandmaster for that area).

[0477] The example area execution circuit 5008 further determines the PTP grandmaster out-of-time event 9404, the area implementation circuit 5004 further operates the optimal master clock algorithm to determine an alternative area manager in at least one area manager as the PTP grandmaster operation, and the area execution circuit 5008 further designates the alternative area manager in the area manager as the PTP grandmaster operation. In some embodiments, an alternative optimal PTP grandmaster is specified in the time management scheme, where the area execution circuit 5008 further determines the PTP grandmaster out-of-time event 9404, and designates the specified alternative one in the area manager as the PTP grandmaster to operate. In some embodiments, the PTP grandmaster can be any one of the area manager or the endpoint, where the area execution circuit 5008 further determines the PTP grandmaster out-of-time event 9404, where the area implementation circuit 5004 further operates the optimal master clock algorithm to determine an alternative endpoint and / or area manager operating at the PTP grandmaster, and the area execution circuit 5008 further designates the determined alternative endpoint and / or area manager as the PTP grandmaster operation. In some embodiments, the PTP grandmaster can be any one of the area manager or the endpoint, where the alternative optimal PTP grandmaster is specified as any one of the area manager or the endpoint in the time management scheme, where the area execution circuit 5008 further determines the PTP grandmaster out-of-time event 9404, and designates the specified alternative one in the area manager or the endpoint as the PTP grandmaster.

[0478] The example system 9400 includes an area controller that applies a common PTP timestamp to at least a portion of the communications provided over a corresponding network area. The example system 9400 includes an area controller that instructs to apply a common PTP timestamp to at least a portion of the communications provided over a corresponding network area.

[0479] Example system 9400 includes a regional controller that removes local timestamps from at least a portion of the communications provided on a corresponding one of a plurality of network regions. Example system 9400 includes a regional controller that instructs the removal of local timestamps from at least a portion of the communications provided on a corresponding network region. In some embodiments, the local timestamp is retained and / or moved to a different part of the message. Retaining the original local timestamp allows for certain post-processing operations, performance of the PTP master, and selected acknowledgments, detection of system issues in the overall timing and synchronization scheme, etc.

[0480] Reference Figure 74 , example partitioned architecture communication scheme 5014 includes a communication priority scheme 9504. Example system 9400 includes a regional manager that, in response to a communication priority value (e.g., associated with the communication and / or with an actor associated with the communication) and communication priority scheme 9504, controls the communication between endpoints of a corresponding network region and endpoints of at least one other region among a plurality of network regions.

[0481] Example communication priority scheme 9504 includes a network routing value 9506, e.g., providing a short path, a less active path, and / or a faster travel time path for high-priority communications, and a longer path, a more active path, and / or a longer travel time path for low-priority communications. Example communication priority scheme 9504 includes a communication scheduling value 9508, e.g., providing a higher-priority schedule for high-priority communications and a lower-priority schedule for lower-priority communications, including potentially "as available as possible" or "best effort" scheduling. In some embodiments, credit-based scheduling can be utilized to differentiate the priority of high-priority communications while allowing some lower-priority communications to proceed.

[0482] In some embodiments, vehicle operating conditions are utilized to determine the scheduling and / or routing of high- and low-priority messages, and / or to determine or adjust the priority of messages. For example, during normal operation, due to the time sensitivity of AV messages, AV messages can be high-priority messages, but during certain operating conditions, e.g., when the critical network traffic of control messages is high and / or the network is degraded, AV messages can be considered low-priority messages until vehicle operation returns to normal and / or the degradation is resolved.

[0483] Reference Figure 75, example process 9600 includes: operation 9602 to interpret a partitioned architecture communication scheme for a vehicle's multi - area network, where the partitioned architecture communication scheme includes a time management scheme; operation 9604 to interpret, in response to the partitioned architecture communication scheme, a region manager command description for each of the at least one region manager, the region manager command description also including time management implementation; operation 9606 to provide the corresponding region manager command description to each of the at least one region manager; and operation 9608 to control communication between endpoints of a corresponding network area and endpoints of at least one other area among a plurality of network areas in response to the region manager command description.

[0484] Reference Figure 76 , example process 9700 includes process 9600, and operation 9702 to determine a PTP grandmaster lost - time event, operation 9704 to designate an alternative PTP grandmaster, and operation 9706 to continue controlling communication between endpoints of a corresponding network area.

[0485] In some embodiments, process 9600 includes designating an endpoint and / or a region manager as a boundary clock for each region, where one endpoint and / or region manager is designated as the PTP grandmaster. In some embodiments, process 9600 includes operating the best master clock algorithm to designate an endpoint and / or a region manager as the PTP grandmaster. In some embodiments, process 9700 includes operating the best master clock algorithm to designate an alternative PTP grandmaster. In some embodiments, designating the PTP grandmaster, the alternative PTP grandmaster, and / or the boundary clock includes determining the PTP grandmaster, the alternative PTP grandmaster, and / or the alternative clock based on the master region where the most critical and / or most time - sensitive operations occur.

[0486] Without being limited to any other aspect of the present disclosure, the embodiments herein provide systems and processes for configuring and / or adjusting a regional network architecture, whether in the design phase (e.g., planning a regional network architecture for a new vehicle) or in the runtime phase (e.g., monitoring, validating, or troubleshooting operations in an existing vehicle). The embodiments herein include tools for quickly designing a new system, validating expected operations, diagnosing abnormal operations, comparing different configurations, leveraging lessons learned and configuration options between vehicles, and rolling out updated configurations, with a high degree of confidence that the updated configuration will operate as expected and will not cause downtime.

[0487] Reference Figure 77 , schematically depicts an example system 9800, system 9800 includes a vehicle multi - area architecture configuration platform 9802, including: a build environment circuit 9804, which provides a virtual network build environment 9908 (reference Figure 78 ) to a user interface 9904 (reference Figure 78); a network modeling circuit 9806 that constructs a virtual multi - zone network model 10004 of a vehicle in response to a user input on a user interface 9904 (see Figure 79 ). The virtual multi - zone network model 10004 includes zone controllers located on each zone of the virtual multi - zone network model 10004. The vehicle for which the virtual multi - zone network model 10004 is constructed can be an existing vehicle or a prospective vehicle (e.g., planning the zone network architecture of a new vehicle, a new model of a vehicle, upgrades and / or recall planning of an existing vehicle, etc.).

[0488] Example system 9800 includes an endpoint modeling circuit 9808 that populates the virtual multi - zone network model 10004 with endpoints based on a vehicle control model 10006. In some embodiments, the endpoint modeling circuit 9808 is empirical and / or low - resolution and populates the endpoints with a data provider that, for example, simulates traffic on a vehicle network at a realistic rate based on monitoring data from vehicles in service. In some embodiments, the endpoint modeling circuit 9808 is based on high - resolution and / or first principles, such as using actual applications, flows, endpoints, etc., installed on the vehicle (and / or representative installations), thereby allowing for realistic generation of traffic in response to inputs including environmental parameters, sensors, and / or operator inputs. In some embodiments, both low - resolution and high - resolution models can be utilized, e.g., using a low - resolution realistic network traffic emulator to detect overall network problems and then using a high - resolution full - endpoint model for granular diagnosis of network performance, testing whether new control algorithms or updates will cause any unexpected problems, etc. In some embodiments, operator inputs, sensor inputs, etc., can be fully simulated, e.g., using a software interface to simulate the vehicle interior and controls available to the operator, and / or using actual hardware components docked with the vehicle multi - zone architecture configuration platform 9802 to simulate operator inputs. In some embodiments, a simple interface screen depicting available switches and operator inputs can be utilized, having numerical or graphical selections at the location of operator inputs.

[0489] The exemplary vehicle multi - zone architecture configuration platform 9802 includes a network modeling circuit 9806. The network modeling circuit 9806 further constructs a virtual multi - zone network model 10004 by applying a partitioned architecture communication scheme 10008. The partitioned architecture communication scheme 10008 is, for example, an actual full - zone manager control scheme according to the embodiments herein, and it can also have a low - resolution simplified version and a high - resolution real or actual version to comprehensively test the vehicle's planning control environment. The exemplary vehicle multi - zone architecture configuration platform 9802 includes a network execution circuit 9810, which simulates the runtime operation of the vehicle multi - zone network in response to the virtual multi - zone network model 10004, the vehicle control model 10006, and / or the partitioned architecture communication scheme 10008. Depending on which aspects of the zone architecture design, multi - zone network, and / or vehicle control, one or more aspects of the virtual multi - zone network model 10004, the vehicle control model 10006, and / or the partitioned architecture communication scheme 10008 can be provided in low - resolution or high - resolution mode. Additionally or alternatively, vehicle operation can be performed according to digital feedback operations, such as using driving operations, torque feedback, environmental conditions, and through digital - specified sequence operations (e.g., simulating driving routes, certain tests, diagnostics, network monitoring operations, etc., aimed at testing control features and / or exercising the network under selected conditions), through the operator's manual input operations (e.g., using the virtual vehicle interior, and / or including some elements of the actual hardware in the loop). The exemplary vehicle multi - zone architecture configuration platform 9802 includes a partitioned architecture evaluation circuit 9812, and the partitioned architecture evaluation circuit 9812 provides a network operation report 10010 in response to the simulation.

[0490] Reference Figure 78 , schematically depicts a system 9900, including a vehicle 9902, which can be simulated in whole or in part and can represent an actual vehicle or an expected vehicle. The system 9900 includes a vehicle multi - zone architecture configuration platform 9802 that provides a virtual network construction environment 9908 to a user interface 9904. The user interacts with the user interface 9904 using a user device 9906, and the user device 9906 can be a laptop computer, a desktop computer, a mobile computing device, a terminal communicatively coupled to the vehicle multi - zone architecture configuration platform 9802, and / or a dedicated engineering tool or station for virtual modeling of the multi - zone network, and / or as Figures 78 - 88The network configuration operations described in the accompanying drawings. In some embodiments, for example, in the case of having hardware components in a loop, aspects of the vehicle 9902 (e.g., switches, pedals, and / or other vehicle controls) can themselves be part of the user device 9906, including, for example, in the case of using dedicated engineering tools or stations in the system 9900. In some embodiments, the user interface 9904 is provided on the user device 9906, for example, as a proprietary application on the user device 9906 that performs display and interaction operations for the vehicle multi - zone architecture configuration platform 9802, and / or as a mobile application on a mobile device (e.g., a phone, a tablet, or a thin laptop). In some embodiments, the user device 9906 is provided via a web portal, operated in a web browser (e.g., as a javascript implant), or otherwise using an Internet connection, and / or via a direct networking connection over, for example, a LAN, WLAN, using a tunneling application, via a VPN, etc.

[0491] In some embodiments, the operation of building the virtual multi - zone network model 10004 includes allowing the user to start with a pre - built model that can be selected from a list or menu of base network selection values 10502 (e.g., refer to Figure 84)。Some available example basic network selection values 10502 include network topology selection 10504 (e.g., selecting a schematic picture of the topology selection and / or selecting a topology from a drop-down menu, such as 2-node, 3-node, or 4-node, including variations in the arrangement, and / or selecting an "n"-node arrangement and specifying a star, mesh, and / or ring arrangement); network area distribution selection 10506 (e.g., weighting areas to the front or rear of the vehicle, allocating a central area and a central area manager, and / or allocating redundancy parameters, such as an area manager that acts as a central area manager in response to a hardware or control non-nominal event, adjusting the connections between areas from the default layout applied by the topology selection, if used, otherwise making or removing connections as desired); network type selection 10508 (e.g., Ethernet, speed grade, cable, and / or connector type, if applicable, and / or how many ports are available for area managers and / or switches in the system, any network based on other systems such as CAN, LIN, etc.); communication protocol selection 10510 (e.g., the protocol used for communication, industrial standards compliance, etc.); cross-network sampling scheme 10512 (e.g., upsampling or downsampling operations for certain cross-area communications, forced sampling rates for certain network areas and / or endpoints, etc.); cross-network encapsulation scheme 10514 (e.g., encapsulation operations performed for communication between certain areas and / or endpoints); area manager distribution scheme 10516 (e.g., defining elements such as the hardware and location of an area manager); central area manager selection (e.g., specifying a central area manager, e.g., if the default central area manager is to be changed, and / or if this is not done using the network area distribution selection 10506); and / or cross-network routing scheme 10520 (e.g., setting connections between areas, and / or defining routes for endpoints, data types, etc., which may be different from simply following the shortest route). The listed basic network selection values 10502 are non-limiting examples, some of these may overlap, and not all of these may be present in a given embodiment. In some embodiments, the available basic network selection values 10502 may be user-defined and / or may vary according to the characteristics of the user device 9906, the user interface 9904, and / or the version of the vehicle multi-area architecture configuration platform 9802.

[0492] In some embodiments, a user can add elements by dragging the elements onto the virtual network building environment 9908, such as dragging a zone manager, a switch, an endpoint, a network connection, etc. onto the virtual network building environment 9908, and / or inserting elements onto the virtual network building environment 9908 using menu selections and / or keyboard shortcuts. In some embodiments, typical interface elements are provided on the virtual network building environment 9908, such as allowing a user to select devices and drag them to different locations, alternately selecting devices (e.g., using a right click, a shift click, a hold click, etc.) to obtain a property menu of the device, and so on. In some embodiments, the devices will be populated with actual example hardware, such as including actual device capabilities and characteristics (e.g., ports, processing capabilities, memory, communication rates, etc.) and / or the cost of the device. In some embodiments, endpoints can be configured as, for example, sensors, actuators, and computing devices (e.g., ECUs), which can alternatively be selected from a menu of actual devices, with user-defined and / or default properties. In some embodiments, the model is populated with actual network hardware and runs a high-resolution network hardware model 10014, such as including (refer to Figure 86 ) a connector 10702, a cable description 10704, a shielding description 10706, and / or a cooling description 10708 for potentially temperature-sensitive components (e.g., based on heat sinks, nearby environments, surrounding conditions, etc.).

[0493] In some embodiments, endpoints, zone managers, or other components can be populated with actual controls, such as specifying a software build from a configuration library, which can be synchronized with an actual production and / or engineering database for high-resolution simulation. In some embodiments, for example, even when a complete software build is integrated into the virtual network building environment 9908, the selection of the simulation resolution can allow switching between simple network traffic modeling or modeling during actual vehicle operation. In some embodiments, the selection can include environmental modeling (e.g., a vehicle environment model 10012), such as determining the temperature, vibration distribution, water intrusion, or road splash, etc. of network components, including models for temperature generation, heat rejection, preheating, and / or cooling operations for controllers and nearby vehicle devices (e.g., engines, electric motors, turbochargers, radiators, wheels, and brakes, etc.) and models for environmental heat transfer. Refer to Figure 85 , an example vehicle environment model 10012 includes one or more of the following: a temperature environment model 10602, a vibration environment model 10604, a water intrusion model 10606, and / or an EMI model 10608.

[0494] In some embodiments, the user may select a previous build, a build from an actual vehicle, etc. In some embodiments, the vehicle may be schematically depicted (e.g., as an outline, which may or may not have proper relative dimensions), completely omitted, and / or realistically depicted (e.g., from a CAD file, a drawing prepared for the purpose of the platform, etc.). In some embodiments, the vehicle may be depicted as a shell with major components in place (e.g., powertrain components, engine, tires, vehicle interior, etc.), and / or as a high-resolution model of the vehicle (e.g., for footprint analysis, high-resolution determination of installation feasibility, modeling of environmental parameters, and / or integration challenges). The example network modeling circuit 9806 constructs a virtual multi-zone network model of the vehicle by pre-populating the virtual multi-zone network model 10004.

[0495] Reference Figure 80 , at least in full-resolution mode, the example partitioned architecture communication scheme 10008 includes at least one of a network security description 10102, a network connectivity description 10104, a time management scheme 10108, and / or a communication priority scheme 10106.

[0496] The example vehicle control model 10006 includes a model of the endpoints of a multi-zone network that simulates vehicle control operations, including actual network traffic, vehicle responses, and / or actual vehicle control commands and data.

[0497] The example network execution circuit 9810 simulates the runtime operation of a multi-zone network by simulating non-nominal conditions, such as certain hardware, control, and / or operation failures. The example network execution circuit 9810 simulates non-nominal conditions by simulating at least one condition selected from: endpoint loss, network component loss, a selected vehicle operating condition, or a selected operator behavior.

[0498] The example network modeling circuit 9806 constructs the virtual multi-zone network model 10004 of the vehicle by applying a network topology description. The example network topology description includes a network topology selected for the application of the zones of the multi-zone network and the assignment of zone controllers to the zones of the multi-zone network. The example network modeling circuit 9806 applies the network topology description in response to user input on a user interface.

[0499] The example network operation report 10010 includes operation capability values (e.g., describing simulation results, comparison with expectations and / or specifications, etc.), a vehicle network performance description 10202 (e.g., reference Figure 81 ), and / or a vehicle performance network impact description 10204. Reference Figure 82, the exemplary vehicle network performance description 10202 includes at least one of the following: a latency value 10302 between at least two endpoints of a multi-area network; a bandwidth value 10304 between at least two endpoints of a multi-area network; a hardware redundancy description 10308 of the multi-area network (e.g., the ability and / or performance to meet hardware redundancy goals); or a control redundancy description 10306 of the multi-area network (e.g., the ability and / or performance to meet control redundancy goals).

[0500] Reference Figure 83 , the exemplary vehicle performance network impact description 10204 includes at least one of the following: an installed hardware cost value 10402 of the multi-area network (e.g., determined based on a parts list of actual network components); a task ability description 10404 of the multi-area network (e.g., determined based on an overview of performance relative to a target or specification and / or actual performance values); an integration cost description 10406 of the multi-area network (e.g., based on interfaces, installation difficulty estimates, etc.); an operation cost description 10408 of the multi-area network (e.g., based on processing resources, power consumption, and / or maintenance operations estimated from simulations); a redundancy ability description 10410 of the multi-area network (e.g., comparison of redundancy ability and / or performance against redundancy goals and / or specifications); and / or a reliability description 10412 of the multi-area network (e.g., based on wear models, temperature environment, vibration environment, and / or water impact on network components).

[0501] In certain embodiments, the high-resolution simulation of network operation includes the network modeling circuit 9806 constructing a virtual multi-area network model 10004 by performing one or more of the following (Reference Figure 80 ): interpreting a partition architecture communication scheme 10008 for the multi-area network, interpreting a time management scheme 10108 for the multi-area network, interpreting a communication priority scheme 10106 for the multi-area network, interpreting a network security description 10102 for the multi-area network, and / or interpreting a network connectivity description 10104 for the multi-area network.

[0502] The exemplary vehicle multi - zone architecture configuration platform 9802 further includes a partition architecture call - out circuit 9814 that constructs a partition architecture communication scheme 10008 in response to user operations on the interface and / or simulation results. The exemplary partition architecture call - out circuit 9814 transmits the partition architecture communication scheme 10008 to the network management controller of the target vehicle, thereby allowing the vehicle multi - zone architecture configuration platform 9802 to directly implement the partition architecture call - out circuit 9814. In some embodiments, the partition architecture call - out circuit 9814 may provide communication or final outputs including a virtual multi - zone network model 10004, a vehicle control model 10006, a vehicle environment model 10012, a network hardware model 10014, a schematic of the constructed environment, a network operation report 10010, a bill of materials for network components, and any aspects of any simulation parameters, configurations, or results.

[0503] Reference Figure 87 , the exemplary process 10800 includes an operation 10802 of providing a virtual network construction environment to a user interface, an operation 10804 of constructing a virtual multi - zone network model of the vehicle in response to user input on the user interface, the virtual multi - zone network model including zone controllers located on each zone of the virtual multi - zone network model; an operation 10806 of populating the virtual multi - zone network model with endpoints based on a vehicle control model; wherein the operation 10804 of constructing the virtual multi - zone network model further includes an operation 10808 of applying a partition architecture communication scheme; an operation 10809 of simulating the runtime operation of the vehicle multi - zone network in response to the virtual multi - zone network model, the vehicle control model, and the partition architecture communication scheme; and an operation 10810 of providing a network operation report in response to the simulation.

[0504] Reference Figure 88 , the exemplary process 10900 includes the process 10800 and further includes an operation 10902 of constructing a partition architecture communication scheme in response to a user operation on the user interface, and an operation 10904 of transmitting the partition architecture communication scheme to the network management controller of the target vehicle.

[0505] Without being limited to any other aspect of the present disclosure, the embodiments herein provide a system and process for monitoring and / or analyzing a regional network architecture and / or an expected regional network architecture to perform diagnostics, identify problems, respond to problems, plan mitigation actions for problems, perform fault tree analysis, plan updates or recalls, develop a deeper understanding of the vehicle impact of activities and / or possible or actual failures or non - nominal operations on a vehicle, etc. using network monitoring and / or analysis.

[0506] Reference Figure 89, An example system includes a vehicle multi - area monitoring platform 11002, including: a network layout circuit 11004 that interprets a virtual network layout 11010 of a vehicle having a multi - area network; a network characterization circuit 11006 that interprets network activities 11012 of the vehicle; and a network analysis circuit 11008 that determines a virtual network map 11014 in response to the virtual network layout 11010 and the network activities 11012 and provides the virtual network map 11014 to a user interface. In some embodiments, the network characterization circuit 11006 interprets the network activities 11012 of the vehicle via direct communication with the vehicle, such as using a high - rate data connection that performs sniffing operations on the network areas of the vehicle. Additionally or alternatively, the network characterization circuit 11006 interprets the network activities 11012 of the vehicle via data collection operations, such as collecting data from a mirror port of the vehicle network to determine network and / or network activities on its selected areas.

[0507] An example virtual network map 11014 includes an interactive depiction of network activities, such as a graphical depiction having traffic flows between endpoints and / or network areas, a description of bandwidth utilization, statistics such as lost packets, a comparison with expected values, etc. In some embodiments, the virtual network map 11014 can include any data or depictions, such as those depicted in Figures 22 - 27 U.S. Patent Application 17 / 570,738 (SONA - 0007 - U01 - C01). An example virtual network map 11014 includes a color - coded schematic layout of the network, such as identifying components (e.g., endpoints, area managers, network areas, etc.) that are suspicious, non - compliant, over - worked (e.g., having problems but seemingly operating within design parameters), and / or having active faults or fault conditions.

[0508] An example network analysis circuit 11008 also provides network detail values 11018 in response to a user selection on the user interface (refer to Figure 90)。Example and non - limiting network detail values include: network traffic description 11102; partition architecture communication scheme 11104; network statistic values 11106; and / or network event notifications 11108. The example vehicle multi - zone monitoring platform 11002 also includes a network configuration circuit 11016 that interprets network adjustment values 11020 and updates the virtual network map 11014 in response to the network adjustment values 11020. In some embodiments, the network adjustment values 11020 include user - input adjustments and / or automatically calculated adjustments, where the adjustments are in response to observed problems and / or in response to capacity adjustments or upgrades to meet the multi - zone network. Example and non - limiting network adjustment values 11020 include any one or more of the following: different hardware components, adjustments to the partition architecture communication scheme 10008, adjustments to the zone manager command description, timing scheme adjustments, connectivity scheme adjustments, and / or permission value adjustments. In some embodiments, the network adjustment values 11020 can include adjustments to any configuration, command value, or scheme value, as set forth throughout this disclosure. The example network analysis circuit 11008 determines a network impact value 11022 in response to the network adjustment values 11020 and provides the network impact value 11022 to a user interface (e.g., as confirmation of the expected success of the adjustment and / or to record any gaps, uncertainties, or un - estimable values). In some embodiments, the network analysis circuit 11008 utilizes the vehicle multi - zone architecture configuration platform 9802 to operate a high - resolution model of the virtual network layout 11010, e.g., using an API interface and / or employing the user interface 9904 and the virtual network construction environment 9908 to perform at least a portion of the determination of the network impact value 11022.

[0509] The vehicle multi - zone monitoring platform 11002 also includes a partition architecture retrieval circuit 9814 that constructs the partition architecture communication scheme 10008 in response to the network adjustment values 11020. The example partition architecture retrieval circuit 9814 also transmits the partition architecture communication scheme 10008 to a network management controller of the vehicle or an offset vehicle (e.g., as part of upgrading an offset vehicle, the offset vehicle can be within the same vehicle class and / or share relevant similarities in the network configuration).

[0510] Reference Figure 91, Example process 11200 includes an operation 11202 of explaining the virtual network layout of a vehicle having a multi - area network, an operation 11204 of explaining the network activities of the vehicle, an operation 11206 of determining a virtual network map in response to the virtual network layout and network activities, and an operation 11208 of providing the virtual network map to a user interface, which may be provided as an interactive network activity description, thereby allowing the user to make adjustments, adjust the displayed results and / or layout, and / or perform simulations. In some embodiments, the interactive network activity depicts operating as an interface to a virtual network construction environment 9908, thereby providing to a user on a vehicle multi - area monitoring platform 11002 any capabilities as Figures 77 - 88 and set forth in the related description. In some embodiments, process 11200 includes an operation (not shown) of providing network detail values in response to a user selection on the user interface. Example network detail values include one or more of network traffic descriptions, partition architecture communication schemes, network statistic values, and / or network event notifications.

[0511] Reference Figure 92 , Example process 11300 includes process 11200 and further includes an operation 11302 of explaining network adjustment values and updating the virtual network map in response to the network adjustment values, an operation 11304 of determining network impact values in response to the network adjustment values and providing the network impact values to the user interface, and an operation 11306 of constructing a partition architecture communication scheme in response to the network adjustment values and transmitting the partition architecture communication scheme to a network management controller of at least one of the vehicle or an off - vehicle.

[0512] Without being limited to any other aspects of the present disclosure, embodiments herein provide systems and processes for monitoring and / or analyzing area network architectures, where such monitoring may operate on a vehicle and quickly identify and respond to problems experienced on the vehicle in a quick response or even an immediate and / or automatic response. Response actions include, but are not limited to, implementing redundancy planning, changing the configuration of area network operations (e.g., prioritizing critical communications and operations, and / or changing the routing or configuration of communications), migrating the responsibility for security and / or control operations, and / or providing notifications and / or related data to a selected off - vehicle location.

[0513] Reference Figure 93, the example system 11400 includes a vehicle (not shown) having a multi-zone network including multiple network zones, each network zone including at least one zone manager; a network monitoring controller 11402 including: a network layout circuit 11004 that interprets the partitioned architecture communication scheme 10008 and the network layout 11406 of the vehicle; a network characterization circuit 11006 that interprets the network activity 11012 of the vehicle and determines a network performance event 11408 in response to the network activity 11012; and a network reaction circuit 11404 that performs a network event action 11410 in response to the network performance event 11408. Example network event actions include collecting event information 11412 in response to the network performance event 11408 (e.g., collecting information to determine that an event has occurred, traffic information of endpoints, flows, applications, network zones, etc. related to the event, a basic set of characterization information typically collected for network events, such as system information, the operating state of the vehicle, fault code information, vehicle speed, load, environmental conditions, time since startup or last shutdown, and / or a set of planning information based on event identifiers), and transmitting the event information to an external device.

[0514] The example network reaction circuit 11404 collects one or more aspects of the event information as post-event activities. The example network reaction circuit 11404 collects one or more aspects of the event information as pre-event information, such as captured from a rolling buffer and / or captured from non-transient information (e.g., status or fault codes) that survived the event cycle. The example network reaction circuit 11404 collects the event information by capturing the network activity 11012 used to determine the network performance event 11408. Reference Figure 94 , example non-limiting network event actions 11410 include one or more actions, such as: collecting event information 11502, performing a network test 11504, performing a diagnosis 11506, adjusting the partitioned architecture communication scheme 11508, implementing a redundancy plan 11510 (e.g., switching the responsibilities of endpoints, controllers, zone managers, etc. in the system, which may also include disabling one or more components, testing the one or more components, and / or placing the one or more components in a restricted operating condition), and / or adjusting the control responsibility of an endpoint 11512.

[0515] Reference Figure 95 , the example process 11600 includes: an operation 11602 of interpreting the partitioned architecture communication scheme and the network layout of a vehicle having a multi-zone network including multiple network zones, each network zone including at least one zone manager; an operation 11604 of interpreting the network activity of the vehicle; an operation 11606 of determining a network performance event in response to the network activity; and an operation 11608 of performing a network event action in response to the network performance event.

[0516] The methods and systems described herein may be deployed, in whole or in part, by a machine having a computer, computing device, processor, circuitry, and / or server that executes computer-readable instructions, program code, instructions, and / or includes hardware configured to functionally perform one or more operations of the methods and systems described herein. As used herein, the terms computer, computing device, processor, circuitry, and / or server (“computing device”) should be understood broadly.

[0517] Example computing devices include any type of computer capable of accessing instructions stored in communication therewith, such as instructions stored on a non-transitory computer-readable medium, such that the computer performs the operations of the computing device when executing the instructions. In some embodiments, such instructions themselves comprise the computing device. Additionally or alternatively, the computing device may be a stand-alone hardware device, one or more computing resources distributed across hardware devices, and / or may include aspects such as: logic circuitry, embedded circuitry, sensors, actuators, input and / or output devices, networks, and / or communication resources, any type of memory resource, any type of processing resource, and / or a hardware device configured to functionally perform one or more operations of the systems and methods described herein in response to a determined condition.

[0518] Networks and / or communication resources include, without limitation, local area networks, wide area networks, wireless networks, the Internet, or any other known communication resources and protocols. Example and non-limiting hardware and / or computing devices include, without limitation, general purpose computers, servers, embedded computers, mobile devices, virtual machines, and / or emulated computing devices. The computing device may be a distributed resource included as an aspect of several devices, included as a set of interoperable resources that perform the functions of the computing device such that the distributed resources operate together to perform the operations of the computing device. In some embodiments, each computing device may be on separate hardware, and / or one or more hardware devices may include aspects of more than one computing device, such as separate executable instructions stored on the device, and / or as aspects of a logical partitioning of a set of executable instructions, where some aspects include a portion of one of the first computing devices and some aspects include a portion of another computing device.

[0519] A computing device can be a server, a client, network infrastructure, a mobile computing platform, a fixed computing platform, or part of other computing platforms. A processor can be any kind of computing or processing device capable of executing program instructions, code, binary instructions, etc. The processor can be or include a signal processor, a digital processor, an embedded processor, a microprocessor, or any variant, such as a coprocessor (mathematical coprocessor, graphics coprocessor, communication coprocessor, etc.) that can directly or indirectly facilitate the execution of program code or program instructions stored thereon. Additionally, the processor can enable the execution of multiple programs, threads, and code. Threads can be executed simultaneously to enhance the performance of the processor and facilitate the simultaneous operation of applications. By implementation, the methods, program code, program instructions, etc. described herein can be implemented in one or more threads. These threads can spawn other threads that have been assigned priorities associated with them; the processor can execute these threads based on the priorities or any other order of instructions provided in the program code. The processor can include a memory that stores the methods, code, instructions, and programs described herein and elsewhere. The processor can access a storage medium through an interface, and the storage medium can store the methods, code, and instructions described herein and elsewhere. The storage medium associated with the processor for storing methods, programs, code, program instructions, or other types of instructions that can be executed by a computing or processing device can include, but is not limited to, one or more of CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache, etc.

[0520] The processor can include one or more cores, which can enhance the speed and performance of the multi-processor. In an embodiment, the process can be a dual-core processor, a quad-core processor, other chip-level multi-processors, etc. that combine two or more independent cores (referred to as dies).

[0521] The methods and systems described herein can be deployed in part or in whole by a machine that executes computer-readable instructions on a server, a client, a firewall, a gateway, a hub, a router, or other such computer and / or network hardware. The computer-readable instructions can be associated with a server, which can include a file server, a print server, a domain server, an Internet server, an intranet server, and other variants, such as an auxiliary server, a host server, a distributed server, etc. The server can include one or more of the following: a memory, a processor, a computer-readable transient and / or non-transient medium, a storage medium, ports (physical and virtual), a communication device, and an interface capable of accessing other servers, clients, machines, and devices through wired or wireless media. The methods, programs, or code described herein and elsewhere can be executed by the server. Additionally, other devices required to execute the methods described in this application can be considered part of the infrastructure associated with the server.

[0522] The server can provide interfaces to other devices, which, without limitation, include clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers, etc. Additionally, the coupling and / or connection can facilitate the remote execution of instructions across a network. The networking of some or all of these devices can facilitate the parallel processing of program code, instructions, and / or programs at one or more locations without departing from the scope of the present disclosure. Further, all devices attached to the server via an interface can include at least one storage medium capable of storing methods, program code, instructions, and / or programs. A central repository can provide program instructions to be executed on different devices. In this implementation, a remote repository can act as a storage medium for methods, program code, instructions, and / or programs.

[0523] The methods, program code, instructions, and / or programs can be associated with a client, which can include a file client, a print client, a domain client, an Internet client, an intranet client, and other variants such as an auxiliary client, a host client, a distributed client, etc. The client can include one or more of the following: a memory, a processor, a computer-readable transient and / or non-transitory medium, a storage medium, ports (physical and virtual), a communication device, and an interface capable of accessing other clients, servers, machines, and devices via wired or wireless media. The methods, program code, instructions, and / or programs described herein and elsewhere can be executed by the client. Additionally, other devices required to execute the methods described in this application can be considered part of the infrastructure associated with the client.

[0524] The client can provide interfaces to other devices, which, without limitation, include servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers, etc. Additionally, the coupling and / or connection can facilitate the remote execution of methods, program code, instructions, and / or programs across a network. The networking of some or all of these devices can facilitate the parallel processing of methods, program code, instructions, and / or programs at one or more locations without departing from the scope of the present disclosure. Further, all devices attached to the client via an interface can include at least one storage medium capable of storing methods, program code, instructions, and / or programs. A central repository can provide program instructions to be executed on different devices. In this implementation, a remote repository can act as a storage medium for methods, program code, instructions, and / or programs.

[0525] The methods and systems described herein can be deployed, in whole or in part, via a network infrastructure. The network infrastructure can include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices, and other active and passive devices, modules, and / or components known in the art. Among other components, the associated computing and / or non-computing devices of the network infrastructure can include storage media such as flash memory, buffers, stacks, RAM, ROM, etc. The methods, program code, instructions, and / or programs described herein and elsewhere can be executed by one or more network infrastructure elements.

[0526] The methods, program code, instructions, and / or programs described herein and elsewhere can be implemented over a cellular network having multiple cells. The cellular network can be a frequency division multiple access (FDMA) network or a code division multiple access (CDMA) network. The cellular network can include mobile devices, cell sites, base stations, repeaters, antennas, towers, and so on.

[0527] The methods, program code, instructions, and / or programs described herein and elsewhere can be implemented on or via a mobile device. The mobile device can include a navigation device, cellular phone, mobile phone, mobile personal digital assistant, laptop computer, palmtop computer, netbook, pager, e-book reader, music player, etc. Among other components, these devices can include storage media such as flash memory, buffers, RAM, ROM, and one or more computing devices. The computing device associated with the mobile device can be enabled to execute the methods, program code, instructions, and / or programs stored thereon. Alternatively, the mobile device can be configured to cooperate with other devices to execute instructions. The mobile device can communicate with a base station, which interfaces with a server and is configured to execute the methods, program code, instructions, and / or programs. The mobile device can communicate over a peer-to-peer network, grid network, or other communication network. The methods, program code, instructions, and / or programs can be stored on a storage medium associated with the server and executed by a computing device embedded within the server. The base station can include a computing device and a storage medium. The storage device can store the methods, program code, instructions, and / or programs executed by the computing device associated with the base station.

[0528] The method, program code, instructions, and / or program may be stored and / or accessed on a machine-readable transient and / or non-transient medium, which may include: computer components, devices, and recording media that retain digital data for a period of time for computing; semiconductor storage devices known as random access memory (RAM); large-capacity storage devices, typically used for more permanent storage, such as optical discs, magnetic storage forms, such as hard disks, tapes, drums, cards, and other types; processor registers, caches, volatile memory, non-volatile memory; optical storage devices, such as CDs, DVDs, removable media, such as flash memory (e.g., USB sticks or keys), floppy disks, tapes, paper tapes, punched cards, standalone RAM disks, Zip drives, removable large-capacity storage devices, offline, etc.; other computer memories, such as dynamic memory, static memory, read / write storage devices, variable storage devices, read-only storage devices, random access memory, sequential access memory, location-addressable, file-addressable, content-addressable storage devices, network-attached storage, storage area networks, barcodes, magnetic ink, etc.

[0529] Certain operations described herein include interpreting, receiving, and / or determining one or more values, parameters, inputs, data, or other information (“receiving data”). Operations for receiving data include, without limitation: receiving data via user input; receiving data over any type of network; reading a data value from a memory location communicating with the receiving device; using a default value as the received data value; estimating, calculating, or deriving a data value based on other information available to the receiving device; and / or updating any of these in response to a later received data value. In certain embodiments, as part of receiving a data value, the data value may be received by a first operation and later updated by a second operation. For example, when communication is down, intermittent, or interrupted, a first receiving operation may be performed, and when communication resumes, an updated receiving operation may be performed.

[0530] This disclosure provides certain logical groupings of operations—such as the methods or procedures of the present disclosure—to illustrate aspects of the present disclosure. The operations described herein are schematically described and / or depicted, and the operations may be combined, divided, reordered, added, or removed in a manner consistent with the disclosure herein. It should be understood that the context in which the operations are described may require ordering of one or more operations, and / or the order for one or more operations may be explicitly disclosed, but the order of operations should be understood broadly, where any equivalent grouping of operations that provides an equivalent result of the operations is specifically contemplated herein. For example, if a value is used in an operation step, in some contexts (e.g., where the time delay of the data for the operation to achieve a certain effect is important), it may be necessary to determine the value prior to that operation step, but in other contexts (e.g., where using the value from a previous execution cycle of the operation would be sufficient for those purposes), it may not be necessary to determine the value prior to that operation step. Thus, in certain embodiments, the order and grouping of operations as described are specifically contemplated herein, and in certain embodiments, reordering, subdivision, and / or different groupings of operations are specifically contemplated herein.

[0531] The methods and systems described herein may transform physical and / or intangible items from one state to another state. The methods and systems described herein may also transform data representing physical and / or intangible items from one state to another state.

[0532] The methods and / or processes and their steps described above may be implemented in hardware, program code, instructions, and / or programs suitable for a particular application or any combination of hardware and methods, program code, instructions, and / or programs. The hardware may include a dedicated computing device or a particular computing device, a particular aspect or component of a particular computing device, and / or an arrangement of hardware components and / or logic circuits to perform one or more operations of the method and / or system. The process may be implemented in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors, or other programmable devices along with internal and / or external memory. The process may also or alternatively be embodied in a special-purpose integrated circuit, a programmable gate array, a programmable array logic, or any other device or combination of devices that can be configured to process electronic signals. It will be further appreciated that one or more processes may be implemented as computer-executable code capable of being executed on a machine-readable medium.

[0533] Computer-executable code can be created using a structured programming language such as C, an object-oriented programming language such as C++, or any other high-level or low-level programming language, including assembly language, hardware description language, and database programming languages and techniques, which can be stored, compiled, or interpreted to run on one of the above devices, as well as on a processor, a heterogeneous combination of processor architectures, or a combination of different hardware and computer-readable instructions, or any other machine capable of executing program instructions.

[0534] Thus, in one aspect, each of the above methods and combinations thereof can be embodied in computer-executable code that, when executed on one or more computing devices, performs its steps. In another aspect, the method can be embodied in a system that performs its steps and can be distributed across devices in a variety of ways, or all functionality can be integrated into a dedicated stand-alone device or other hardware. In yet another aspect, the apparatus for performing the steps associated with the above process can include any of the above hardware and / or computer-readable instructions. All such arrangements and combinations are intended to fall within the scope of the present disclosure.

[0535] Although the present disclosure has been shown and described in detail in connection with specific embodiments, various modifications and improvements thereto will become apparent to those skilled in the art. Accordingly, the scope of the present disclosure is not limited by the foregoing examples, but should be understood in the broadest sense permitted by law.

Claims

1. A method, comprising: interpreting a vehicle network performance description; determining a regional architecture value in response to the vehicle network performance description and a vehicle performance network impact description; and integrating a multi - regional network on the vehicle in response to the regional architecture value.

2. The method according to claim 1, wherein the vehicle network performance description includes at least one of the following: a latency value between at least two endpoints of a multi - regional network; a bandwidth value between at least two endpoints of a multi - regional network; a hardware redundancy description of a multi - regional network; or a control redundancy description of a multi - regional network.

3. The method according to claim 1, wherein the vehicle performance network impact description includes at least one of the following: an installation hardware cost value of a multi - regional network; a task capability description of a multi - regional network; a redundancy capability description of a multi - regional network; or a reliability description of a multi - regional network.

4. The method according to claim 1, wherein the regional architecture value includes a network topology description.

5. The method according to claim 4, wherein the regional architecture value further includes a regional manager distribution description.

6. The method according to claim 5, wherein the regional architecture value further includes a network type value for each region of the multi - regional network.

7. The method according to claim 6, wherein the regional architecture value further includes a network protocol value for each region of the multi - regional network.

8. The method according to claim 1, wherein the regional architecture value further includes a specification value of at least one hardware component of the multi - regional network.

9. The method according to claim 1, wherein integrating a multi - regional network on the vehicle includes installing a multi - regional network configured according to the regional architecture value.

10. The method according to claim 1, wherein integrating a multi - regional network on the vehicle includes installing a multi - regional network configured according to the network topology description of the regional architecture value.

11. The method according to claim 1, wherein integrating a multi - regional network on the vehicle includes installing a multi - regional network configured according to the regional manager distribution description of the regional architecture value.

12. A method, comprising: interpreting a plurality of vehicle network performance descriptions, each corresponding to one of a plurality of selected vehicle classes; determining a regional architecture value in response to the plurality of vehicle network performance descriptions and a vehicle performance network impact description for each of the plurality of selected vehicle classes; and integrating a multi - regional network on each of a first vehicle and a second vehicle in response to the regional architecture value, wherein the first vehicle includes a member of the first of the plurality of selected vehicle classes and wherein the second vehicle includes a member of the second of the plurality of selected vehicle classes.

13. The method according to claim 12, wherein each of the plurality of vehicle network performance descriptions includes at least one of the following: a latency value between at least two endpoints of a multi - regional network corresponding to one of the plurality of selected vehicle classes; a bandwidth value between at least two endpoints of a multi - regional network corresponding to one of the plurality of selected vehicle classes; a hardware redundancy description of a multi - regional network corresponding to one of the plurality of selected vehicle classes; or Description of control redundancy for a multi - area network corresponding to one of a plurality of selected vehicle classes.

14. The method according to claim 12, wherein the vehicle performance network impact description corresponding to each of the plurality of selected vehicle classes includes at least one of the following: The installation hardware cost value of a multi - area network corresponding to one of the plurality of selected vehicle classes; The task capability description of a multi - area network corresponding to one of the plurality of selected vehicle classes; The redundancy capability description of a multi - area network corresponding to one of the plurality of selected vehicle classes; or The reliability description of a multi - area network corresponding to one of the plurality of selected vehicle classes.

15. The method according to claim 12, wherein the regional architecture value includes a network topology description.

16. The method according to claim 15, wherein the regional architecture value further includes a regional manager distribution description.

17. The method according to claim 12, wherein integrating the multi - area network on each of the first vehicle and the second vehicle includes installing a multi - area network configured according to the regional architecture value on each of the first vehicle and the second vehicle.

18. The method according to claim 12, wherein integrating the multi - area network on each of the first vehicle and the second vehicle includes installing a multi - area network configured according to the network topology description of the regional architecture value on each of the first vehicle and the second vehicle.

19. The method according to claim 12, wherein integrating the multi - area network on each of the first vehicle and the second vehicle includes installing a multi - area network configured according to the regional manager distribution description of the regional architecture value on each of the first vehicle and the second vehicle.

20. A system, comprising: A vehicle having a multi - area network including a plurality of network regions, each network region including at least one regional manager; wherein the plurality of network regions are arranged according to the network topology description of a selected regional architecture, the selected regional architecture being determined in response to a vehicle network risk description and a vehicle performance network impact description; and A network management controller, comprising: A region implementation circuit configured to interpret a partitioned architecture communication scheme; A regional manager command circuit configured to interpret, in response to the partitioned architecture communication scheme, a regional manager command description for each of the at least one regional manager; and A region execution circuit configured to provide a corresponding regional manager command description to each of the at least one regional manager; and wherein each of the at least one regional manager responds to the corresponding regional manager command description to control communication between endpoints of the corresponding network region and endpoints of at least one other region among the plurality of network regions.

21. The system according to claim 20, wherein the selected regional architecture includes a star arrangement, wherein one of the plurality of network regions includes a central region having a central regional manager.

22. The system according to claim 21, wherein the plurality of network regions further comprise: Two forward regions, each forward region communicatively coupled to the central region; and One rearward region communicatively connected to the central region.

23. The system according to claim 20, wherein the selected area architecture includes a grid area arrangement.

24. The system according to claim 23, wherein the plurality of network areas further comprise: two forward areas; one central area; one backward area; and wherein each of the plurality of network areas is communicatively coupled to all other network areas of the plurality of network areas.

25. The system according to claim 20, wherein the selected area architecture includes a ring area arrangement.

26. The system according to claim 25, wherein the plurality of network areas further sequentially comprise: a central area, having a central area manager and communicatively coupled to a first forward area; the first forward area, communicatively coupled to a second forward area; the second forward area, communicatively coupled to the backward area; and the backward area, communicatively coupled to the central area.

27. The system according to claim 20, wherein the selected area architecture includes a two-node topology, wherein each node of the two-node topology corresponds to one of the plurality of network areas.

28. The system according to claim 20, wherein the selected area architecture includes a three-node topology, wherein each node of the three-node topology corresponds to one of the plurality of network areas.

29. The system according to claim 20, wherein the selected area architecture includes a four-node topology, wherein each node of the four-node topology corresponds to one of the plurality of network areas.

30. The system according to claim 20, wherein at least one of the plurality of areas includes a virtual network area.

31. A method, comprising: interpreting a vehicle network risk description; determining an area architecture value in response to the vehicle network risk description and a vehicle performance network impact description; and integrating a multi-area network on the vehicle in response to the area architecture value.

32. The method according to claim 31, wherein the vehicle network risk description includes a hardware redundancy value.

33. The method according to claim 31, wherein the vehicle network risk description includes a control redundancy value.

34. The method according to claim 31, wherein the vehicle network risk description includes a critical flow description.

35. The method according to claim 31, wherein the vehicle network risk description includes a critical application description.

36. The method according to claim 31, wherein the vehicle network risk description includes a critical communication connection description.

37. The method according to claim 31, wherein the vehicle network risk description includes a failure mode description.

38. The method according to claim 31, wherein the vehicle performance network impact description includes a performance estimate of the multi-area network with respect to the vehicle network risk description.

39. A system, comprising: a vehicle having a multi-area network including a plurality of network areas, each network area including at least one area manager, and wherein one of the at least one area managers includes a central area manager; wherein the plurality of network areas are arranged according to a network topology description of a selected area architecture; and wherein the central area manager includes a network management controller, and the network management controller includes: A region implementation circuit configured to interpret a partitioned architecture communication scheme, where the partitioned architecture communication scheme includes a network security description and a network connectivity description; A region manager command circuit configured to, in response to the partitioned architecture communication scheme, interpret a region manager command description for each of the at least one region managers; and A region execution circuit configured to provide a corresponding region manager command description to each of the at least one region managers; and wherein each of the at least one region managers responds to the corresponding region manager command description to control communication between endpoints of a corresponding network region and endpoints of at least one other region among the plurality of network regions.

40. The system according to claim 39, wherein the central region manager is directly communicatively coupled to each other region manager.

41. The system according to claim 39, further comprising: wherein the region implementation circuit is further configured to interpret a partitioned architecture communication scheme update; wherein the region manager command circuit is further configured to, in response to the updated partitioned architecture communication scheme, interpret a region manager command description for each region manager among the at least one region managers; and wherein the region execution circuit is further configured to provide a corresponding updated region manager command description to each of the at least one region managers.

42. The system according to claim 41, further comprising, wherein the region implementation circuit is further configured to interpret a partitioned architecture communication scheme update by receiving a policy from an external device.

43. The system according to claim 39, wherein the network security description includes a permission value associated with at least one of the following: A network region among the plurality of network regions; A flow of the vehicle; An application of the vehicle; A function of the vehicle; or An endpoint of one of the plurality of network regions.

44. The system according to claim 43, wherein the permission value includes at least one permission selected from the following: A communication bandwidth permission; A data provider permission; A data receiver permission; A service subscription permission; A service provider permission; A service visibility permission; A service publication permission; or An endpoint communication permission.

45. The system according to claim 39, wherein the network connectivity description includes a connectivity scheme between at least two of the plurality of network regions.

46. The system according to claim 45, wherein the connectivity scheme defines at least one of the following: A communication rate value; A communication protocol value; A communication encapsulation description; A sampling rate value; A communication header value; A communication metadata value; A communication unit value; or A communication timestamp description.

47. The system according to claim 45, wherein the network connectivity description further includes a connectivity scheme based on at least one of an origin endpoint value or a destination endpoint value.

48. The system according to claim 45, wherein the network connectivity description further includes a connectivity scheme based on at least one of an origin network type or a destination network type.

49. A system, comprising: A vehicle having a multi-region network including a plurality of network regions, each network region including at least one region manager; wherein the plurality of network regions are arranged according to a network topology description of a selected region architecture; and a service management controller, comprising: a service registration circuit configured to maintain a service registry including a plurality of services and service descriptions for each of the plurality of services; a service publishing circuit configured to present at least one service from the plurality of services to a requester source in response to a service publishing request; a service subscription circuit configured to register the requester source with the at least one service in response to a service subscription request and update the service registry in response to the registration; a network management controller, comprising: a region implementation circuit configured to interpret a partition architecture communication scheme; a region manager command circuit configured to interpret a region manager command description for each of the at least one region managers in response to the partition architecture communication scheme; and a region execution circuit configured to provide a corresponding region manager command description to each of the at least one region managers; and wherein each of the at least one region managers controls communication between endpoints of a corresponding network region and endpoints of at least one other region among the plurality of network regions in response to a corresponding region manager command description and the service registry.

50. The system according to claim 49, wherein the service management controller is at least partially located on a central region manager of the plurality of region managers.

51. The system according to claim 50, wherein the central region manager is directly communicatively coupled to each other region manager.

52. The system according to claim 49, wherein the network management controller is at least partially located on a central region manager of the plurality of region managers.

53. The system according to claim 52, wherein the central region manager is directly communicatively coupled to each other region manager.

54. The system according to claim 49, wherein each of the plurality of services includes at least one of the following: a data value; a mathematical function; a processing function; a communication function; or a data storage function.

55. The system according to claim 49, wherein each of the plurality of services includes at least one of the following: an actuator function; a command function; or a control function.

56. The system according to claim 49, wherein the service publishing circuit is further configured to publish the at least one service by listing the at least one service in a data structure provided to the requester source.

57. The system according to claim 49, wherein the service publishing circuit is further configured to present the at least one service by listing the at least one service in a data structure available to the requester source.

58. The system according to claim 49, wherein the requester source includes an external device.

59. The system according to claim 49, wherein the service publishing circuit is further configured to: interpret a service publishing request for a new service from a new service provider; determine a new service description in response to the service publishing request and the new service provider; and maintain the service registry by adding the new service as one of the plurality of services.

60. The system according to claim 59, wherein the service publishing circuit is further configured to add the new service in response to a permission value associated with the new service provider.

61. The system according to claim 49, wherein the service publishing circuit is further configured to maintain the service registry by removing a service from a plurality of services in response to a service publishing request.

62. The system according to claim 61, wherein the service publishing circuit is further configured to remove the service from the plurality of services by deleting an associated entry from the service registry.

63. The system according to claim 61, wherein the service publishing circuit is further configured to remove the service from the plurality of services by setting an inactive flag in an associated entry from the service registry.

64. The system according to claim 49, wherein the service publishing circuit is further configured to maintain the service registry by deprecating a service from the plurality of services in response to a service publishing request.

65. The system according to claim 64, wherein the service subscription circuit is further configured to block new registrations for a deprecated service.

66. The system according to claim 49, wherein the service publishing circuit is further configured to maintain the service registry by removing the service from the plurality of services in response to determining that at least one aspect of the service is no longer available.

67. The system according to claim 66, wherein the service publishing circuit is further configured to remove the service from the plurality of services by setting an inactive flag in an associated entry from the service registry.

68. The system according to claim 49, wherein for each service of the plurality of services, the service registry includes at least one of the following: A service identifier; A service provider description; A service permission description; or A service capability description.

69. The system according to claim 68, wherein for each service of the plurality of services, the service registry further includes at least one of the following: A service input description; A service active or inactive flag; A service deprecation flag; A service registrar description; or A service participant description.

70. The system according to claim 68, wherein the service permission description includes at least one of the following: A service publishing permission; A service subscription permission; or A service visibility permission.

71. The system according to claim 49, further comprising storing the service registry on an external device.

72. A system, comprising: A vehicle multi-region architecture configuration platform, comprising: A build environment circuit configured to provide a virtual network build environment to a user interface; A network modeling circuit configured to build a virtual multi-region network model of a vehicle in response to user input on the user interface, the virtual multi-region network model including a regional controller located on each region of the virtual multi-region network model; An endpoint modeling circuit configured to populate the virtual multi-region network model with endpoints based on a vehicle control model; wherein the network modeling circuit is further configured to build the virtual multi-region network model by applying a partitioned architecture communication scheme; A network execution circuit configured to simulate the runtime operation of a vehicle's multi - area network in response to a virtual multi - area network model, a vehicle control model, and a partitioned architecture communication scheme; and A partitioned architecture evaluation circuit configured to provide a network operation report in response to the simulation.

73. The system according to claim 72, wherein the partitioned architecture communication scheme includes at least one of the following: a network security description, a network connectivity description, a time management scheme, or a communication priority scheme.

74. The system according to claim 72, wherein the vehicle control model includes a model of an endpoint of the multi - area network that simulates vehicle control operations.

75. The system according to claim 72, wherein the vehicle control model includes a model of an endpoint of the multi - area network that operates actual vehicle control instructions.

76. The system according to claim 72, wherein the network execution circuit is further configured to simulate the runtime operation of the multi - area network by simulating non - nominal conditions.

77. The system according to claim 76, wherein the network execution circuit is further configured to simulate non - nominal conditions by simulating at least one condition selected from the following: endpoint loss, network component loss, a selected vehicle operation condition, or a selected operator behavior.

78. The system according to claim 72, wherein the network modeling circuit is further configured to construct a virtual multi - area network model of the vehicle by applying a network topology description.

79. The system according to claim 78, wherein applying the network topology description includes applying a selected network topology to a region of the multi - area network and assigning a regional controller to a region of the multi - area network.

80. The system according to claim 78, wherein applying the network topology description includes applying the network topology description in response to user input on a user interface.

81. The system according to claim 72, wherein the network operation report includes an operation ability value.

82. The system according to claim 72, wherein the network operation report includes a vehicle network performance description.

83. The system according to claim 82, wherein the vehicle network performance description includes at least one of the following: A latency value between at least two endpoints of the multi - area network; A bandwidth value between at least two endpoints of the multi - area network; A hardware redundancy description of the multi - area network; or A control redundancy description of the multi - area network.

84. The system according to claim 72, wherein the network operation report includes a vehicle performance network impact description.

85. The system according to claim 84, wherein the vehicle performance network impact description includes at least one of the following: An installation hardware cost value of the multi - area network; A task ability description of the multi - area network; An integration cost description of the multi - area network; An operation cost description of the multi - area network; A redundancy ability description of the multi - area network; or A reliability description of the multi - area network.

86. The system according to claim 72, wherein the network modeling circuit is further configured to construct a virtual multi - area network model of the vehicle by pre - populating the virtual multi - area network model.

87. The system according to claim 86, wherein the pre-populating includes prompting a user for at least one basic network selection value and constructing an initial model in response to a user response to the at least one basic network selection value.

88. The system according to claim 87, wherein each of the at least one basic network selection values includes at least one of the following: Network topology selection; Network area distribution selection; Network type selection; Communication protocol selection; Cross-network sampling scheme; Cross-network encapsulation scheme; Area manager distribution scheme; Central area manager selection; or Cross-network routing scheme.

89. The system according to claim 72, wherein the network modeling circuit is further configured to construct a virtual multi-area network model of the vehicle by interpreting redundant descriptions of at least one component of the multi-area network.

90. The system according to claim 72, wherein the network modeling circuit is further configured to construct a vehicle environment model, and wherein the network execution circuit is further configured to simulate runtime operations of the multi-area network in response to the vehicle environment model.

91. The system according to claim 90, wherein the vehicle environment model includes a model of at least one of the following: Temperature environment model; Vibration environment model; Electromagnetic interference model; or Water intrusion model.

92. The system according to claim 90, the network modeling circuit is further configured to construct a network hardware model, and wherein the network execution circuit is further configured to simulate runtime operations of the multi-area network in response to the network hardware model.

93. The system according to claim 92, wherein the network hardware model includes a model of at least one of the following: Connectors of at least one component of the multi-area network; Cable descriptions of at least one component of the multi-area network; Cooling descriptions of at least one component of the multi-area network; or Shielding descriptions of at least one component of the multi-area network.

94. The system according to claim 72, wherein the network modeling circuit is further configured to construct a virtual multi-area network model of the vehicle by interpreting a time management scheme of the multi-area network.

95. The system according to claim 72, wherein the network modeling circuit is further configured to construct a virtual multi-area network model of the vehicle by interpreting a communication priority scheme.

96. The system according to claim 72, wherein the network modeling circuit is further configured to construct a virtual multi-area network model of the vehicle by interpreting a network security description.

97. The system according to claim 72, wherein the network modeling circuit is further configured to construct a virtual multi-area network model of the vehicle by interpreting a network connectivity description.

98. The system according to claim 72, wherein the vehicle multi-area architecture configuration platform further includes a partition architecture call-out circuit configured to construct a partition architecture communication scheme in response to a user operation on an interface.

99. The system according to claim 98, wherein the partition architecture call-out circuit is further configured to transmit the partition architecture communication scheme to a network management controller of a target vehicle.

100. A system, comprising: A vehicle multi - area monitoring platform, comprising: A network layout circuit configured to interpret a virtual network layout of a vehicle having a multi - area network; A network characterization circuit configured to interpret the network activities of the vehicle; and A network analysis circuit configured to determine a virtual network map in response to the virtual network layout and the network activities, and provide the virtual network map to a user interface.

101. The system according to claim 100, wherein the virtual network map includes an interactive network activity description.

102. The system according to claim 101, wherein the network analysis circuit is further configured to provide network detail values in response to a user selection on the user interface.

103. The system according to claim 102, wherein the network detail values include at least one of the following: A network traffic description; A partition architecture communication scheme; Network statistical values; or A network event notification.

104. The system according to claim 100, wherein the vehicle multi - area monitoring platform further includes a network configuration circuit configured to interpret network adjustment values and update the virtual network map in response to the network adjustment values.

105. The system according to claim 104, wherein the network analysis circuit is further configured to determine a network impact value in response to the network adjustment values and provide the network impact value to the user interface.

106. The system according to claim 104, wherein the vehicle multi - area monitoring platform further includes a partition architecture retrieval circuit configured to construct a partition architecture communication scheme in response to the network adjustment values.

107. The system according to claim 106, wherein the partition architecture retrieval circuit is further configured to transmit the partition architecture communication scheme to at least one of a network management controller of the vehicle or an off - vehicle.

108. A method, comprising: Interpret a virtual network layout of a vehicle having a multi - area network; Interpret the network activities of the vehicle; Determine a virtual network map in response to the virtual network layout and the network activities; and Provide the virtual network map to a user interface.

109. The method according to claim 108, further comprising providing the virtual network map as an interactive network activity depiction.

110. The method according to claim 109, further comprising providing network detail values in response to a user selection on the user interface.

111. The method according to claim 110, wherein the network detail values include at least one of the following: A network traffic description; A partition architecture communication scheme; Network statistical values; or A network event notification.

112. The method according to claim 108, further comprising interpreting network adjustment values and updating the virtual network map in response to the network adjustment values.

113. The method according to claim 112, further comprising determining a network impact value in response to the network adjustment values and providing the network impact value to the user interface.

114. The method according to claim 112, further comprising constructing a partition architecture communication scheme in response to the network adjustment values.

115. The method according to claim 114, further comprising transmitting a zonal architecture communication scheme to a network management controller of at least one of a vehicle or an off-vehicle.

116. A system, comprising: a vehicle having a multi-zone network including a plurality of network zones, each network zone including at least one zone manager; a network monitoring controller, comprising: a network layout circuit configured to interpret a zonal architecture communication scheme and a network layout of the vehicle; a network characterization circuit configured to interpret network activity of the vehicle and determine a network performance event in response to the network activity; and a network reaction circuit configured to perform a network event action in response to the network performance event.

117. The system according to claim 116, wherein the network event action comprises: collecting event information in response to the network performance event; and transmitting the event information to an external device.

118. The system according to claim 117, wherein the network reaction circuit is further configured to collect the event information as a post-event activity.

119. The system according to claim 117, wherein the network reaction circuit is further configured to collect the event information by capturing the network activity used to determine the network performance event.

120. The system according to claim 116, wherein the network event action includes performing a network test.

121. The system according to claim 116, wherein the network event action includes performing a diagnosis.

122. The system according to claim 116, wherein the network event action includes adjusting the zonal architecture communication scheme.

123. The system according to claim 116, wherein the network event action includes implementing redundancy planning.

124. The system according to claim 116, wherein the network event action includes adjusting control responsibility of at least one endpoint on the multi-zone network.

Images