Systems, methods, and apparatus for supporting hybrid network communications on vehicle
Through hybrid network systems and converged network equipment to transmit and convert communications between different transportation network networks, the performance and security problems of existing transportation communication networks when the number of equipment and data rates increase are solved, and safe and efficient data are achieved Management and access reduce overall costs.
Patent Information
- Application Number
- CN202411076635.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2020-05-13
- Filing Date
- 2020-09-21
- Publication Date
- 2024-11-12
AI Technical Summary
Existing vehicle communication networks are difficult to meet performance and security requirements when facing increased equipment quantity and data rates, and data management complexity and cost increase, especially in terms of data collection, storage and access.
Adopt a hybrid network system to transmit and convert communication between different networks through converged network devices (CND), manage and monitor network status, realize secure, scalable data management and access, and support collaborative operation of multiple network types. and monitoring.
It reduces the physical risks and costs of network systems, improves the security and efficiency of data management, reduces the complexity and cost of data access and storage, and enhances the scalability and flexibility of transportation networks.
Smart Images

Figure CN118945010A_ABST
Abstract
Description
[0001] This application is a divisional application. The name of the invention of the parent case is "System, method and device for supporting hybrid network communication on a vehicle", the application date is September 21, 2020, and the application number is 202080080424.7.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of priority to the following provisional applications: U.S. Application Serial No. 62 / 903,462, filed on September 20, 2019, entitled SYSTEM, METHOD AND APPARATUS FOR A MIXED VEHICLE NETWORK (SONA-0001-P01); U.S. Application Serial No. 62 / 911,249, filed on October 5, 2019, entitled SYSTEM, METHOD AND APPARATUS FOR A MIXED VEHICLE NETWORK (SONA-0002-P01); and U.S. Application Serial No. 62 / 911,249, filed on October 5, 2019, entitled SYSTEM, METHOD AND APPARATUS FORCLOUD-BASED INTERACTIONS WITHAMIXED U.S. application serial number 62 / 911,248, entitled "SYSTEM, METHOD AND APPARATUS FOR IMPLEMENTING CONFIGURABLE DATA COLLECTION FOR AVEHICLE" (SONA-0004-P01), filed on March 6, 2020; and U.S. application serial number 63 / 024,383, entitled "SYSTEM, METHOD AND APPARATUS TOTEST AND VERIFY AVEHICLE NETWORK" (SONA-0005-P01), filed on May 13, 2020.
[0003] Each of the above applications is incorporated herein by reference in its entirety. Background Art
[0004] Vehicle communication networks are utilized to connect sensors, actuators, controllers, and communication devices throughout a vehicle. Recent trends have been increasing the burden on these vehicle communication networks, with more devices connected, more data transferred between devices, lower latency requirements to meet vehicle performance, safety, and transmission requirements, and added vehicle features. Furthermore, consumers expect increased connectivity and features that place a greater burden on vehicle communication networks. These trends are expected to continue and accelerate for the foreseeable future.
[0005] Traditional vehicle communication networks (CAN, LIN, FlexRay, MOST, LVDS, etc.) suffer from a number of shortcomings and challenges. These vehicle communication networks have been developed to meet the specific challenges of the vehicle environment and have accordingly evolved independently from other networks, such as computer local area networks, wide area networks, large-scale interconnected networks (e.g., the Internet), and wireless networks. Most vehicle networks consist of a data link layer and an application layer, utilizing robust and specialized equipment (such as the Controller Area Network (CAN) bus), with dedicated or shared wiring between devices utilizing specific data protocols (e.g., J1939, OBD, etc.). Modern vehicles may have multiple network buses with specific commands and communications available, as well as limited customization and data speeds available. For example, the CAN bus typically operates at up to approximately 1 Mbps, with the high-capacity CAN bus operating at up to approximately 10 Mbps. In addition, depending on the configuration, the amount of traffic on the CAN, the priority of specific messages, etc., the CAN bus experiences delays greater than 25 ms and typically higher, ranging from approximately 60 ms to 500 ms.
[0006] As the number of devices and the data rate requirements from the devices increase, traditional vehicle communication networks require the implementation of higher performance buses. Because the automotive industry is a high-volume industry with very low tolerance for component failures, automakers utilize the same components for a long time and across a wide range of vehicles - including sharing components across manufacturers. In addition, changes to nominally more capable components may introduce risk, integration costs, the burden of re-qualification for a given application, or have other undesirable consequences for the system. Accordingly, even if the vehicle communication network transitions to a higher-capability network configuration, it is desirable to keep the network type isolated in the system and to keep a large number of legacy devices (e.g., CAN-compatible) in the system for a long period of time.
[0007] The collection of data from vehicles includes several additional challenges. For example, data collection operations are subject to regulatory and liability risks, particularly with respect to the collection of data that may include private information, personally identifiable information, and / or liability-related information. Data collectors, including entities that may have ownership or possession of sensitive data, are subject to risks in retaining the data, for example, in the event of inadvertent or malicious access to the data. With respect to collecting vehicle data, a large amount of data may be collected, and there may be a large number of purposes for collecting the data, thereby increasing the risk relative to other general data storage applications. Accordingly, it may be desirable to control data collection, storage, and access to reduce risk, and it may be further desirable to include verification of data access, partitioning, or other data exclusion when data is not in use, etc.
[0008] The amount and type of data to be transmitted between vehicles and external devices further complicates data collection for vehicles, where the vehicle's network system is constrained by mobile applications, expenses, and / or bandwidth limitations caused by high data rates and / or large data transmission. Even considering the above, customer demand, market expectations, increasing demands for efficiency in vehicle operation, and improved functional capabilities for data-related applications are continuing to cause a surge in the total amount of data to be transmitted, the number of off-vehicle applications that utilize the transmitted data, the number of purposes for which the data can be used, and the number of users or entities with legitimate needs for portions of the transmitted data. In addition, applications that utilize data continue to improve in sophistication and capability, thereby increasing the demand for data against limited available transmission resources and increasing the cost and complexity of logistical control and storage of the transmitted data. For example, higher-capacity routing or operating algorithms associated with vehicles, increased automation of vehicle functions, increased demand for prognostic determination and / or maintenance support, and increased media streams (both the number of media streams and the quality of those media streams) all drive increased demands for data rates, the amount of data stored, and the number of entities or applications that access the stored data. Summary of the Invention
[0009] As a non-limiting example and for the sake of clarity of this description, the description herein refers to a vehicle application. However, the embodiments herein are applicable to other applications with similar challenges and / or implementations. Without being limited to any other application, the embodiments herein are applicable to any application with multiple endpoints, including multiple data sources, controllers, sensors and / or actuators, and may further include endpoints present in different or distributed network environments, and / or the embodiments herein are applicable to applications with a history or traditional networking or communication system that can be transformed (within a given system, as a system class and / or as an industry) to a newer and / or more capable networking or communication system. Examples and non-limiting embodiments include one or more of the following: industrial equipment; robotic systems (including at least mobile robots, autonomous vehicle systems and / or industrial robots); mobile applications (which may or may not be considered "vehicles") and / or manufacturing systems. It should be understood that certain features, aspects, and / or advantages of the present disclosure may be applicable to any one or more of these applications and not to others of these applications, and that the applicability of certain features, aspects, and / or advantages of the present disclosure may vary depending on the operating conditions, constraints, cost parameters (e.g., operating costs, integration costs, operational costs, data communication and / or storage costs, service costs, and / or downtime costs) of a particular application. Accordingly, wherever the present disclosure references a vehicle, a vehicle system, a mobile application, an industrial equipment, a robotic system, and / or a manufacturing system, each of these is also contemplated herein and may be applicable in certain embodiments or not applicable in certain other embodiments, as will be understood by those skilled in the art having the benefit of this disclosure.
[0010] As reflected in the described embodiments, the disclosure herein has recognized that the aforementioned complexities and other challenges have a synergistic effect that makes the complexity of the vehicle data environment even greater than the sum of the individual contributions from each challenge.
[0011] As an example, an increased number of entities or applications accessing data increases the likelihood that an individual data request will overlap, for example, with multiple entities requesting the same or similar data. Further, an increased number of entities or applications accessing data increases the likelihood that members of an access group will share similar authorization levels, such that data access for individual members of the entity or application group will benefit from data management.
[0012] In another example, regulations relating to sensitive data are increasing, which generally increases the data management requirements of the system, but also increases the possibility that data management may be subject to multiple constraints at a given time, and / or constraints that change over time as regulations change, and / or based on relevant jurisdictions that may change as the location of the vehicle changes.
[0013] In yet another example, the complex environment of currently known and evolving vehicle network architectures (e.g., vehicles with mixed network types and / or partitioned networks) increases the complexity of data access for individual entities, which, without certain aspects of the present disclosure, may otherwise require individual entities to determine request parameter specifications for specific data elements and update those request parameters as the vehicle network architecture evolves. Given the increasing number of entities requesting data access, the overall cost of supporting the automotive market increases non-linearly, as each of the entities incurs the cost of tracking the request parameter specifications. Additionally, the trajectory of additional entities requesting data access moves toward entities located further away from core automotive functionality in the technical knowledge space, and accordingly, the intricacies and idiosyncrasies of vehicles and / or automotive applications, including on-vehicle network configurations, specific data descriptions, data request and communication protocols, industry standards or conventions for presenting information, and so forth, are becoming less well-known on average for each incremental new entity, further increasing the cost volume function (e.g., the cost over time to provide a given entity with desired data collection deliverables, where a given entity may be an automotive manufacturer, and / or a vehicle market, a geographic market, and / or an industry such as the automotive industry, the passenger car industry, etc.). For example, consider a nominal cost volume function such as: COST = number of entities * basic learning cost * adaptation of transformation trajectory * data trajectory cost * adaptation cost of regulation * data access / storage responsibility cost.
[0014] The COST function described is a non-limiting, nominal example that demonstrates how various challenges and complexities with currently known systems interact and combine to increase the cost of meeting future data collection capabilities for vehicle applications. The cost parameters described are not intended to cover all costs associated with the challenges that exist for the automotive data collection industry or currently known systems. Parameters can be averages or other complex functions, and the values of specific parameters are generally not known specifically. Additionally, the units of COST can be expressed in monetary terms, as resources to meet data collection goals over time (e.g., engineering hours, computing time, etc.), as another non-monetary unit such as equivalent issuance, customer satisfaction, risk incurred, public perceived loss or gain, etc. The number of entity parameters generally reflects the number of entities accessing vehicle data over time; base learning costs reflect the details of data collection requirements and protocols for new entities to learn for specific vehicles, vehicle types, markets, etc.; adaptation to the transition cost trajectory reflects the cost of adapting to changing vehicle network configurations, which includes network types and organization and interactions with endpoints or devices on those networks; data trajectory costs reflect the increasing demand for data collection from relevant vehicles over time, including data communications, storage and resulting functional consequences, such as the cost of not being able to support desired applications or enhancing data communications infrastructure; adaptation costs of regulations reflect the costs associated with the increased number of regulations, the increased number of regulatory frameworks and / or the increased number of regulatory entities; and data access / storage liability costs reflect the costs incurred for compliance and security of data and / or losses incurred due to data breaches, unauthorized use, premature expiration of data, etc.
[0015] Without limitation to any other aspects of the present disclosure, aspects of the disclosure herein reduce and / or eliminate any one or more of the following: the cost per entity added to the data collection system, the basic learning cost for new entities to implement applications using the collected data, the adaptation cost of changing vehicle network configurations, the cost incurred to meet the increased demand for data collection, the cost of adapting to the changed regulatory environment, and / or the cost of losses to security data and / or to violations or unauthorized use. Certain embodiments and / or aspects of the disclosure herein can address one or more of the described cost parameters. Certain embodiments and / or aspects of the disclosure herein can increase one or more given cost parameters, but are beneficial by reducing the overall cost function for the target vehicle, vehicle type, entity, industry, etc. Certain embodiments and / or aspects of the disclosure herein can increase one or more given cost parameters, but provide other advantages such as improved functionality. In certain embodiments, the improved functionality can be achieved at an increased cost but at a lower cost than previously known systems configured to achieve similar improved functionality.
[0016] Without limitation to any other aspects of the present disclosure, embodiments herein provide for the operation of a system having multiple networks thereon, wherein endpoint devices are distributed across the networks, and embodiments herein provide for the operation of utilizing data, communications, and / or commands with endpoint devices without requiring specific knowledge of the location, capabilities, and / or data configuration of at least some of the applications, circuits, and / or other operators within the system. Embodiments herein provide for configuration of network management, thereby allowing for changes in the location of endpoint devices within the system, adaptation to system failures or non-nominal operation, and / or updates to the system that may occur during stages of manufacturing, body construction, service, assembly or upgrades, parts replacement, maintenance, advertising campaigns, changes in parts, and / or changes in industry standards. Embodiments herein provide for monitoring of network status and / or performance of networks on a vehicle, including monitoring when the vehicle is intermittently connected to an external device. Embodiments herein provide for configuration changes to monitoring operations, including changes in the monitored networks, monitored parameters, execution of monitored events, and the like. Embodiments herein provide for monitoring operations of endpoint devices, network communications, communications between specific endpoints (on the same or different networks), and configurations of these. Embodiments herein provide for network traffic control, regulation, and / or support both on a specific network and between networks. Embodiments herein provide for selected distributions of network management, monitoring, and control functions, including providing for incorporation of functions within existing controllers, distributing functions between controllers, providing for redundancy and support for non-nominal operations, variations of these between similar systems while supporting full functionality, and combinations of these. Embodiments herein provide for monitoring operations of endpoint devices, network communications, and communications between specific endpoints, wherein a monitoring application or device communicates with a first network and monitors a second network. Embodiments herein provide for monitoring any network, network zone, flow, device group, virtual group, and the like that may exist within a system.
[0017] Embodiments herein include the operation of a hybrid network system that provides application task support, and the operation includes control, monitoring, data collection, configuration and / or update.Embodiments herein include allowing active control of devices, endpoints, controllers, streams, device groups, vehicle functions, vehicle applications, etc., which can be distributed on any network of a vehicle and / or across more than one network of a vehicle and from devices, applications or controllers that can communicate with any network of the system. Additionally or alternatively, embodiments herein can support active control of devices after changes to controlled devices, endpoints, controllers, streams, device groups, vehicle functions and / or vehicle applications, with a selected level of knowledge of the changes by the controlling device, application or controller, including without any knowledge of the changes.Embodiments herein include allowing active monitoring, service event execution, and / or testing execution of devices, endpoints, controllers, streams, device groups, vehicle functions, vehicle applications, etc., which can be distributed on any network of a vehicle and / or across more than one network of a vehicle and from devices, applications or controllers that can communicate with any network of the system. Additionally or alternatively, embodiments herein may support active monitoring, service event execution, and / or test execution of devices following changes to controlled devices, endpoints, controllers, flows, groups of devices, vehicle functions, and / or vehicle applications, with a selected level of knowledge of the changes by the controlling device, application, or controller, including without any knowledge of the changes.
[0018] Embodiments herein support hybrid and / or scalable network topologies, including hybrid networks and / or multiple instances of a given network type (e.g., separate and / or partially separate networks). The number and arrangement of networks can be provided to support any aspect of vehicle design, operation, and life cycle management, including at least: allowing mixing of legacy equipment with newer equipment; separating network physical locations and functions; changes to vehicles during service, maintenance, upgrades, and / or model changes; and / or reduction and / or compartmentalization of design effort and / or integration effort. Without limitation, embodiments herein support dual-zone network architectures and / or n-zone network architectures.
[0019] Embodiments herein support the consolidation of controls that might otherwise be distributed around a system, e.g., to reduce the number of controllers and / or processing devices that must be installed, integrated, and / or interfaced between, reduce physical risk to the network system, reduce the cost of the network system, and / or reduce the footprint of the network system (e.g., reducing the overall footprint of a vehicle and / or allowing the footprint to be relocated, in whole or in part, to another system of the vehicle). Embodiments herein support data management and access in hybrid network vehicles, including abstracting data providers from data consumers, enabling data authorization, security, and compartmentalization, reducing network traffic, and managing capability differences between endpoints, devices, controllers, flows, groups of devices, networks, and the like.
[0020] Embodiments herein provide configurations of hybrid network control devices, including interfaces that allow configuration of network management, network control, and network monitoring applications. Embodiments herein provide configurations of hybrid network control subcomponents, which include interfaces for them, such as interfaces for devices that interface between networks, and embodiments herein facilitate generating, packaging, and / or processing communications from a first network to communications on a second network. Embodiments herein provide configurations of hybrid network control devices and / or subcomponents that selectively utilize external tools (e.g., service tools, manufacturing tools, diagnostic tools, consumer devices, etc.), which can be coupled to the hybrid network control device using a direct connection, a wireless connection, a cellular connection, or other communication connection. In certain embodiments, the configuration tool herein can be an external tool, a web application, a mobile application, a dedicated or proprietary application, or a combination of these.
[0021] For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the accompanying drawings and described in the following written specification. It should be understood that no limitation to the scope of the present disclosure is intended thereby. It should be further understood that the present disclosure encompasses any changes and modifications to the illustrated embodiments, and includes further applications of the principles disclosed herein, as would normally occur to one skilled in the art to which the present disclosure pertains. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] Figure 1 is a schematic diagram of an example system for regulating an on-vehicle network according to certain embodiments of the present disclosure.
[0023] Figure 2 is an example system and schematic diagram for regulating a network on a vehicle according to certain embodiments of the present disclosure.
[0024] Figure 3 is an example system and schematic diagram for regulating a network on a vehicle according to certain embodiments of the present disclosure.
[0025] Figure 4 is a schematic diagram of a converged network device (CND).
[0026] Figure 5 is a schematic diagram of a converged network device (CND).
[0027] Figure 6 is a schematic diagram of a converged network device (CND).
[0028] Figure 7 is a schematic diagram of a converged network device (CND).
[0029] Figure 8 is a schematic diagram of a converged network device (CND).
[0030] Figure 9 is a schematic diagram of a converged network device (CND).
[0031] Figure 10 is a diagram of a configurable Ethernet switch.
[0032] Figure 11 is a schematic diagram of a configurable edge gateway.
[0033] Figure 12 is a schematic diagram of an example system for regulating an on-vehicle network according to certain embodiments of the present disclosure.
[0034] Figure 13 is a schematic diagram of an example system for regulating an on-vehicle network according to certain embodiments of the present disclosure.
[0035] Figure 14 is a schematic diagram of an example system for regulating an on-vehicle network according to certain embodiments of the present disclosure.
[0036] Figure 15 is a schematic diagram of an example system for regulating an on-vehicle network according to certain embodiments of the present disclosure.
[0037] Figure 16 Depicts illustrative operations for processing messages.
[0038] Figure 17 An illustrative operation of downsampling a message is depicted.
[0039] Figure 18 An illustrative operation of upsampling a message is depicted.
[0040] Figure 19 is a schematic diagram of a system for regulating a network on a vehicle, according to certain embodiments of the present disclosure.
[0041] Figure 20is a schematic diagram depicting network zones in a distributed risk profile.
[0042] Figure 21 is a schematic diagram of a system for regulating a network on a vehicle, according to certain embodiments of the present disclosure.
[0043] Figure 22 is a schematic diagram depicting a distributed CND with network redundancy circuits.
[0044] Figure 23 is a schematic diagram of a system for regulating a network on a vehicle, according to certain embodiments of the present disclosure.
[0045] Figure 24 is a schematic flow chart depicting an example process for regulating inter-network communication.
[0046] Figure 25 is a schematic flow diagram depicting an example process for encapsulating communications.
[0047] Figure 26 is a schematic flow diagram depicting an example process for handling communications.
[0048] Figure 27 is a schematic diagram of a system for providing data services.
[0049] Figure 28 is a schematic diagram of a system for regulating a network on a vehicle.
[0050] Figure 29 is a schematic diagram of a system for regulating a network on a vehicle.
[0051] Figure 30 is a schematic diagram of a system for regulating a network on a vehicle.
[0052] Figure 31 is a schematic diagram of a system for regulating a network on a vehicle.
[0053] Figure 32 is a schematic diagram depicting example network conditioning components.
[0054] Figure 33 is a schematic diagram depicting example network conditioning components.
[0055] Figure 34 is a schematic diagram depicting example network conditioning components.
[0056] Figure 35 is a schematic flow chart of a process for publishing a data service.
[0057] Figure 36is a schematic flow chart of a process for encoding a first network dataset into a second network dataset.
[0058] Figure 37 is a schematic flow chart of a process for providing network status data.
[0059] Figure 38 is a schematic flow chart of a process for mirroring a port.
[0060] Figure 39 is a schematic flow chart of a process for encoding a first network dataset.
[0061] Figure 40 is a schematic flow chart of a process for performing an active testing procedure.
[0062] Figure 41 is a schematic flow chart of a process for regulating a network of transportation vehicles.
[0063] Figure 42 is a schematic flow chart of a process for regulating inter-network communications of vehicles.
[0064] Figure 43 is a schematic flow chart of a process for encoding an Ethernet-based data set.
[0065] Figure 44 is a schematic flow chart of a process for providing network status data.
[0066] Figure 45 is a schematic flow chart of a process for performing a control operation.
[0067] Figure 46 is a schematic flow chart of a process for providing a persistent message value.
[0068] Figure 47 It is a schematic diagram of CND.
[0069] Figure 48 is a schematic diagram of endpoints of a network responsive to actuator command values.
[0070] Figure 49 is a schematic diagram of a system for regulating network communications for a vehicle.
[0071] Figure 50 is a schematic flow chart of a process for commanding an actuator.
[0072] Figure 51 is a schematic flow chart of a process for commanding an actuator.
[0073] Figure 52 is a schematic flow chart of a process for commanding an actuator.
[0074] Figure 53 is a schematic flow chart of a process for transmitting collected data to an external device.
[0075] Figure 54 is a schematic flow chart of a process for performing proactive diagnostics.
[0076] Figure 55 is a schematic flow chart of a process for commanding an actuator.
[0077] Figure 56 is a schematic diagram of a system for regulating network communications for a vehicle.
[0078] Figure 57 is a schematic flow chart of a process for regulating network communications of a vehicle.
[0079] Figure 58 is a schematic flow chart of a process for regulating network communications of a vehicle.
[0080] Figure 59 is a schematic flow chart of a process for regulating network communications of a vehicle.
[0081] Figure 60 is a schematic diagram of a system for regulating network communications of vehicles using a scheduled policy.
[0082] Figure 61 is a schematic diagram of a system for providing visualization data of a transportation network.
[0083] Figure 62 is a schematic illustrative example of a local DNS table.
[0084] Figure 63 is a schematic illustrative example of vehicle communication data.
[0085] Figure 64 is a schematic, pictorial example of visualizing data.
[0086] Figure 65 is a schematic, pictorial example of visualizing data.
[0087] Figure 66 is a schematic, pictorial example of visualizing data.
[0088] Figure 67 is a schematic, pictorial example of visualizing data.
[0089] Figure 68 is a schematic, pictorial example of visualizing data.
[0090] Figure 69 is a diagram of the visual management controller.
[0091] Figure 70 is a schematic flow chart of the process used to provide visual data.
[0092] Figure 71 is a schematic flow chart of the process used to provide visual data.
[0093] Figure 72 is a schematic diagram of a system for regulating network communications for a vehicle.
[0094] Figure 73 is a schematic pictorial example of a strategy.
[0095] Figure 74 is a schematic pictorial example of a strategy.
[0096] Figure 75 is a schematic pictorial example of a strategy.
[0097] Figure 76 is a schematic flow chart of a process for regulating network communications of a vehicle.
[0098] Figure 77 is a schematic flow chart of the process used to provide visual data.
[0099] Figure 78 is a schematic flow chart of a process for updating a policy.
[0100] Figure 79 is a schematic diagram of a system for regulating network communications for a vehicle.
[0101] Figure 80 is a schematic pictorial example of a strategy.
[0102] Figure 81 is a schematic flow chart of a process for regulating network communications of a vehicle. DETAILED DESCRIPTION
[0103] refer to Figure 1, an example system schematically depicts aspects of an embodiment of the present disclosure. The example system includes an application 102 (e.g., a vehicle) having a first network 104 and a second network 106 thereon. As utilized herein, a network should be broadly construed and may include one or more aspects such as: hardware implementation (e.g., wire and wiring configuration, applicable standards (such as connectors), insulation, shielding, wire requirements (such as metering, torsion, coaxial arrangement, etc.)), implementation of any layer (e.g., from the ISO 7-layer model, such as: application layer, presentation layer, session layer, transport layer, network layer, data link layer, and / or physical layer; although a given network may have fewer layers and / or layers organized in a different manner); and / or may be wired or wireless in whole or in part. Without limiting any aspect of the present disclosure, example and non-limiting networks include a controller area network (CAN), a media oriented systems transport (MOST) network, a local interconnect network (LIN), a FlexRay network, a time triggered protocol (TTP) network, a low voltage differential signaling (LVDS) network, and / or an Ethernet implementation network. In some embodiments, one or more networks may be an electrical signal area (e.g., a device that provides data and / or receives commands as electrical signals (such as, voltage values, frequency values, and indicated resistance values), etc.), such as a sensor or actuator electrically coupled to an interpretation device that is capable of receiving information from and / or transmitting information or commands to one or more electrical devices on the electrical signal area.
[0104] The example system includes a first network 104 that is a different type from a second network 106. As utilized herein, two networks of different types should be broadly construed and include networks having different protocols, at least one layer that is different from one another (e.g., having different application layers, presentation layers, etc.), two networks that are operationally incompatible (e.g., a device coupled to one of the networks will not function on the second network without changes to connectivity, communication, or other aspects), and / or two networks that are message-incompatible (e.g., a message configured for a first network in the network cannot be directly placed on a second network in the network due to differences such as addressing, frame construction, message logic compatibility, etc.). The example system includes the first network 104 being an Ethernet-implemented network and the second network 106 of a different type, such as a CAN network and / or a LIN network.
[0105] The example system further includes a converged network device (CND) 108 that is interposed between the first network 104 and the second network 106 and is structured to facilitate communications between the first network 104 and the second network 106. The CND 108, interposed between the networks 104 and 106, includes embodiments in which the CND 108 passes communications between the networks 104 and 106, such as receiving communications from the first network 104, translating communications destined for the second network 106 (e.g., encapsulating all or part of the communications into messages destined for the second network 106; converting aspects of the communications, such as device addresses, bit depth for the data, and / or unit values for the data; and / or adding or removing aspects of the communications, such as priority information, message delivery requests or requirements, industry standard information (e.g., message identifiers), etc.). In some embodiments, the CND 108 does not physically pass communications or only passes portions of communications, but rather can regulate, manage, provide permissions, throttle messages, or otherwise control other devices (e.g., switches, routers, gateways, repeaters, etc.) that perform operations to pass communications between networks. Accordingly, in some embodiments, a CND between the networks 104, 106 may be physically located between the networks 104, 106, wherein communications passed between the networks 104, 106 are physically received by components of the CND 108. In some embodiments, the CND 108 between the networks 104, 106 may have visibility into communications on the networks 104, 106 and control devices for regulating message passing between the networks. In some embodiments, the CND 108 between the networks 104, 106 may have visibility into endpoints on the networks 104, 106 and control devices for regulating message passing between the endpoints of each physical network 104, 106.
[0106] A person skilled in the art having the benefit of the present disclosure may readily arrange CND 108 according to one of these intervention schemes and / or according to a combination of more than one of these intervention schemes having information generally available when considering a particular system. In designing an intervention scheme for CND 108 for a given system, certain considerations include, but are not limited to: the number and type of networks on the vehicle; the capabilities of the individual networks (e.g., throughput, bandwidth, address availability, broadcast / unicast / multicast availability and desirability of each network and / or endpoint on the network, the requirement and / or availability of affirmative acknowledgement for each network and / or endpoint, and / or the requirement and / or availability of encryption for each network and / or endpoint); the availability, location and / or control of the network implementation controller (e.g., the presence and ownership of switching devices; access to instructions (such as firmware or buffers) for available devices; and / or the connectivity of available devices to one or more networks, such as whether the devices are arranged to implement desired messages passed between networks, desired redundancy and / or desired failure mode responses); the capabilities of the network implementation controller (e.g., buffer sizing and availability, message rate capacity, processing capacity); the availability, location and / or control of the network implementation controller (e.g., the presence and ownership of switching devices; access to instructions (such as firmware or buffers) for available devices; and / or the connectivity of available devices to one or more networks, such as whether the devices are arranged to implement desired messages passed between networks, desired redundancy and / or desired failure mode responses); hardware cost considerations for adding components to the system; hardware cost considerations for providing capabilities for CND operations in other components of the system; integration cost considerations and system capabilities of implementing additional CND-specific components and / or adding capabilities for CND operations in other components of the system); the number, type and / or message throughput of endpoints utilizing cross-network communications; expected changes in any one or more of these aspects over the life of a vehicle (e.g., due to service events, upgrades and / or advertising campaign events (such as, product recall events associated with the vehicle)); and / or expected changes in any one or more of these aspects over the life of an associated group of vehicles (e.g., an associated fleet of vehicles; model years of vehicles; and / or groups of model years associated with the system, such as, vehicles expected to have similar network infrastructure, with changes to device distribution, changes to the network, etc.).
[0107] exist Figure 1In the example of FIG, a first external device 110 is depicted as being communicatively coupled to the application 102. The first external device 110 is directly coupled to the application 102, which may include a direct wired connection (e.g., to a service port, an OBD port, or other available connection) and / or a wireless connection (e.g., a WiFi connection (such as an IEEE 801.11 compliant connection) and / or a Bluetooth connection). The first external device 110 can be connected to a specific network (e.g., the first network 104 or the second network 106), and / or can be connected to another device (e.g., the CND 108 and / or a device mediated by the CND 108) that directly manages communications with the external device 110. Regardless of whether the external device 110 is coupled to a network 104, 106 or another device (such as the CND 108), in certain embodiments, the CND 108 can manage communications so that the external device 110 only receives authorized communications, and can further manage communications so that the external device 110 can request communications from endpoints on any of the networks 104, 106 and still receive the requested information. In some embodiments, the first external device 110 can be a service tool, an original equipment manufacturer's (OEM's) tool, a manufacturer's tool, a body builder's tool, and / or an application (e.g., an application that communicates via a computing device such as a laptop, desktop, mobile device, and / or mobile phone; e.g., an application operated by an owner, servicer, fleet manager, etc.).
[0108] exist Figure 1 In the example of FIG, the second external device 114 is depicted as communicating with the application 102 and / or the first external device 110 via a cloud connection 112. The cloud connection 112 can be any type of connection, including a mobile connection (e.g., a modem on the application 102, connecting using cellular data or another data service), an Internet connection, a wide area network (WAN), and / or a combination of these. The cloud connection 112 can access the application 102 through a transceiver, which can form part of and / or be at least partially mediated by the CND 108. In some embodiments, the application 102 can have more than one transceiver, with one or more or all of the transceivers being at least partially mediated by the CND 108. In some embodiments, the CND 108 can mediate some vehicle communications (e.g., from certain networks, endpoints, devices, data types, streams, and / or applications on the vehicle), but not other communications.
[0109] As used herein, endpoints should be understood broadly. An endpoint is an organizational concept for access to a vehicle's networks 104, 106 and can include specific devices (e.g., engine controllers, transmission controllers, door controllers, infotainment systems, etc.), groups of devices with a single network access (e.g., multiple devices communicating together through a single network access point, where the networks 104, 106 and / or CND 108 may have visibility into individual devices, or may only have visibility into communications from the endpoint as a group). For example, a door controller (not shown) can be an endpoint for one of the networks 104, 106, where communications for underlying devices (e.g., door position sensors, door lock actuators and positions, window actuators and positions, etc.) are passed to the network 104, 106 through the door controller endpoint, where the CND 108 can have visibility into the underlying devices (e.g., messages indicating the door position that include an identifier that the door position sensor is sending the message), or can have visibility only to the door controller endpoint (e.g., messages indicating that the door position is known to be provided by the door controller, but the CND 108 is unaware of which underlying devices may have sent the message). A person skilled in the art, having the benefit of this disclosure and the information generally available regarding the system under consideration, can readily determine which devices in the system are endpoints for each network 104, 106. Certain considerations for determining endpoint placement include, but are not limited to: the availability of hardware ports on the network; the distribution of vehicle controllers; messages to be passed between vehicle controllers; the regulatory options to be available for a given endpoint as set forth in this disclosure (e.g., message rates, priorities, data collection, message configuration, identity information for components, addressing management between networks and with external devices, etc.); the desired granularity of data control (e.g., permission for specific devices to provide or request information; permission for applications on or off the vehicle to provide or request information; security authorizations and types, such as per-user, per-entity, per-device, per-application, per-flow, etc.); and / or redundancy options to be available for a given system (e.g., redundancy of network communication capabilities, redundancy of control operations and related equipment, and / or redundancy of CND operations where CND components are distributed in more than one location in a vehicle).
[0110] As used herein, applications should be understood broadly. Example applications include groups of related vehicle functions or operations, such as speed control (e.g., speed control of a vehicle or a subcomponent of a vehicle (such as an engine or drivetrain)), anti-lock braking system (ABS) operation, advanced driver assistance systems (ADAS), performance control (e.g., implementing torque requests, speed requests, or other performance requests from an operator), or other functions of a vehicle. Example applications include groups of related functions other than the vehicle, such as applications that support geolocation and / or navigation to request and / or process service information related to the vehicle, and / or third-party applications that interact with the operator (e.g., to find the nearest hotel, selected events, etc.). Applications can be implemented by vehicle manufacturers, suppliers, original equipment manufacturers, body builders, third parties, operators, service personnel, etc. As used herein, applications provide organizational concepts that can be utilized to relate certain data, certain endpoints, and / or related functions of the vehicle. In certain embodiments, CND 108 may utilize an application to identify a data source, a data destination, permissions available to the application, priority information associated with the application, and the like to implement certain data conditioning operations herein.
[0111] As used herein, streams should be understood broadly. Example streams include related groups of data (e.g., speed data, temperature data, audiovisual data, navigation data, etc.), related groups of functions (e.g., among vehicle functions, functions outside of the vehicle (such as service operations and / or data collection), aggregations between related vehicles, and / or combinations of these that are relevant for a particular system), related groups of devices (e.g., door actuators), and / or related groups of applications. As used herein, streams provide an organizational concept that can be utilized to relate certain data, certain endpoints, certain applications, and / or related functions of or in addition to vehicles. In certain embodiments, CND 108 can utilize streams to identify data sources, data destinations, permissions available for the stream, priority information associated with the stream, and the like, to implement certain data conditioning operations herein. In certain embodiments, the utilization of streams allows CND 108 to perform classification operations that may involve the same endpoint to support desired network management. For example, a vehicle speed management application may have a high priority, and a speedometer endpoint may be associated with the vehicle speed management application. In an example, if the vehicle speed is being transmitted to support a vehicle speed management application, CND 108 applies a high priority to the vehicle speed message. However, if the vehicle speed is being transmitted to support a journey planning flow (e.g., where the journey planning flow exists and does not have a high priority), CND 108 may apply a lower priority to the vehicle speed message. In a further example, a failure of a vehicle controller, a partial failure of a network, or other non-nominal conditions may cause the vehicle speed management application to migrate to another controller in the system, whereupon vehicle speed messages are being transmitted (e.g., where the backup controller is on another network) to support the vehicle speed management application, and CND 108 may apply a higher priority to the vehicle speed message. Utilizing flows and applications to organize the components of the system allows the same or similar information to be regulated differentially by CND 108 to support various functions, thereby allowing for improvements in the performance and safety of network regulation operations (e.g., reducing unnecessary cross-network traffic and providing information only when needed). Furthermore, utilizing flows and applications to organize the components of the system supports additional functionality relative to previously known systems, such as redundancy support, distributed control, and granular cross-network messaging.
[0112] As used herein, a service group should be understood broadly. Example service groups include groups of related applications for a vehicle. The related application group can be located entirely on the vehicle (e.g., one or more vehicle systems, functions, or other applications of the vehicle), and / or can include aspects located on an external device (e.g., having support for processing, data collection or storage, data obtained from an external source used by the service group, etc.), which can be a web application, web tool, cloud application, service application, etc. In certain embodiments, any group of local communication devices can be logically related and serve as a service group. Utilizing service groups to organize the components and / or applications of a system allows the same or similar information to be regulated by CND 108 in a differential manner to support various functions, thereby allowing improvements in performance and security of network regulation operations (e.g., reducing unnecessary cross-network traffic, providing information only when needed, and / or regulating communications with external devices), and utilizing service groups to organize the components and / or applications of a system supports additional functionality relative to previously known systems, such as redundancy support, distributed control, and granular cross-network messaging.
[0113] As utilized herein and without limitation to any other aspect of the present disclosure, a regulated component includes any component of a system that is regulated with respect to communications, including data collection, subscriptions, data requests, access to external devices and / or addresses, access to network zones, access to endpoints, utilization of communication resources (e.g., network zone bandwidth, external communication portals, total data limits or amounts, etc.). Regulated components include, but are not limited to, one or more of the following: an endpoint, a flow, an application, a controller, a service group, an interface circuit, a network zone, an external communication portal, an external device, a source address, a destination address, a vehicle function, an entity associated with any of these, a user associated with any of these, and / or a user role associated with any of these.
[0114] refer to Figure 2 , the example system includes a vehicle 202 having a first network 104, a second network 106, and a CND 108 between the networks 104, 106. The example system depicts the vehicle 202 being communicatively coupled to an external device 110 (with Figure 1 ) and / or communicatively coupled to a second external device 114. Figure 2 The example depicts another external device 204, which in this example is communicatively coupled to the vehicle 202 via the cloud connection 112. The third external device 204 is schematically depicted as a laptop, for example, as operated by a fleet service manager, owner, and / or vehicle representative (e.g., a claims specialist). Figure 2The examples are illustrative depictions to illustrate additional contextual options and specific applications as a vehicle, but are otherwise similar to Figure 1 system.
[0115] refer to Figure 3 , schematically depicts an example embodiment including a vehicle 202, illustrating some further details that may be present in certain embodiments. The example system includes the vehicle 202 having a first network 104 and a second network, and a CND 108 interposed between the first network 104 and the second network. Figure 3 In the example of , the second network is an Ethernet network having devices (eg, interactive dashboard 302, door actuator 310, and transmission controller 320) coupled to Ethernet switch 312. Figure 3 In the example of FIG, a third network 318 is shown with the fuel tank sensor 306 coupled to the CND 108. In the example, the third network 318 can be of the same type as one of the other networks, for example, isolated from the other networks to improve installation, risk management, or cost for other considerations, and / or the third network can be of a different type to support devices—for example, sensors operating on a LIN network. The third network 318 can communicate with the CEG 314, the Ethernet switch 312, or another device (not shown) of the CND 108.
[0116] Figure 3 Examples include a first device 308 on a first network 104 (e.g., Figure 3 In the example, for the prime mover controller) and multiple devices on the second network (e.g., Figure 3 , interactive dashboard 302, fuel tank sensor 306, and door actuator 310). The system includes one of the devices 302, 310, 320 on the second network communicating with the first device 308 via CND 108. For example, when the vehicle 202 is moving, the door actuator 310 can lock the doors, thereby pulling vehicle movement information (e.g., engine speed, gear, vehicle speed, and / or status parameters such as a "VEHICLE MOVING" Boolean value, bit mask, etc.) from the first device 308.
[0117] Figure 3 The arrangement is a non-limiting example. Additionally or alternatively, a given device (e.g., prime mover 308) may appear as a single endpoint or multiple endpoints, e.g., a controller of prime mover 308 may provide a number of parameters to first network 104, the multiple endpoints may each be provided with an identifier and operated as separate endpoints (e.g., engine temperature from an engine temperature sensor), and / or may include parameters provided as such by the prime mover 308 controller (e.g., engine temperature from an engine controller).
[0118] For illustration Figure 3 In an example of a first network 104, the first network 104 may be a CAN bus network, wherein the desired data (e.g., vehicle movement indicator) is provided as a CAN message according to the considerations for the CAN network. The door actuator 310 is provided on a second network (e.g., an Ethernet network), wherein the door actuator 310 is on a port of the second network. The port for the door actuator 310 may be a physical port (e.g., a port of an Ethernet switch 312 dedicated to the door actuator 310) or a virtual port (e.g., an address location for the second network, which may be on a physical port shared with one or more other devices). Figure 3 In the example of , the door actuator 310 is unable to receive CAN messages indicating vehicle movement, and the CND 108 interprets the request from the door actuator 310 for vehicle movement indication, retrieves the message from the first network 104, and sends the message to the door actuator 310 on the second network.
[0119] The operations performed to send the message can vary depending on the application. For example, CND 108 can publish certain parameters available from the first network (and / or third network 318) to devices on the second network and provide the selected parameters directly to the device (e.g., providing a vehicle movement indicator to the requesting device), or publish data values representing the parameters (e.g., utilizing a proxy (not shown) to make the subscribed parameters available), and those parameters are available to devices that subscribe to those parameters. In some embodiments, CND 108 can limit the publication of parameters to devices, endpoints, applications, and / or flows that are authorized to see those parameters available. In other words, different devices on the second network may see different lists of parameters available depending on the authorization of those devices and / or the applications or flows associated with those devices. In some embodiments, CND 108 can limit the provision of parameters to devices, endpoints, applications, and / or flows that are authorized to receive those parameters - for example, by rejecting subscription requests for the parameters and / or suppressing the sending of parameters to unauthorized devices despite subscription. Accordingly, in some embodiments, a device may be able to see that a parameter is available (e.g., in a published list of available parameters), but may not be able to receive the data value of the parameter. In some embodiments, a device may be restricted from seeing the available parameters that the device is authorized to receive.
[0120] In some embodiments, a device may have only limited availability for receiving parameters, e.g., CND 108 may limit the rate of data values to support reduced network utilization, data security considerations (e.g., limiting the accuracy, resolution, and / or data rate of sensitive parameters such as vehicle location), and / or to support proprietary considerations (e.g., limiting the accuracy, resolution, and / or data rate of parameters that may be relevant to proprietary control operations, e.g., to limit the ability of application engineers to completely transform or otherwise determine how control operations operate).
[0121] In some embodiments, CND 108 determines which parameters to publish, provide, and the conditions under which they are provided based on stored data that defines permissions and / or capabilities of devices, endpoints, applications, flows, etc. In some embodiments, CND 108 further defines stored data for processing or adjusting operations on data (e.g., encapsulation operations (e.g., to pass CAN messages to an Ethernet network), unit conversion, timestamp definitions, etc.). In some embodiments, CND 108 determines authorization for applications and / or flows that are on-vehicle, off-vehicle (e.g., operating on external devices such as 110, 114, 204), or a combination of on-vehicle and off-vehicle. In some embodiments, CND 108 can support prioritization of data flows based on prioritization of related devices, endpoints, applications, flows, or other parameters, including the rate at which devices provide or receive information. In certain embodiments, the CND 108 may support differential prioritization based on vehicle state or operating conditions (e.g., using a first priority scheme during startup operations, a second priority scheme during runtime operations, a third priority scheme when the vehicle is moving, etc.) In certain embodiments, the CND 108 may respond to any defined vehicle condition, such as charging, regeneration, aftertreatment operation, control regime (e.g., cruise versus operator control), emergency conditions, fault conditions, service conditions, and the like.
[0122] Figure 3The example CND 108 includes a first device 314 that communicates with the first network 104. The example first device 314 includes a configurable edge gateway (CEG) that reads communications from the first network 104 and provides them to the second network 106. In some embodiments, the first device 314 converts communications destined for the second network into (e.g., encapsulates the communications, portions of the frames of the communications, and / or the payload of the communications into) messages destined for the second network. In some embodiments, the first device 314 is capable of requesting communications from devices on the first network 104, for example, requesting parameters that are available but not currently being transmitted to the first network 104. In some embodiments, the first device 314 is not part of the CND 108, but is controlled by the CND 108, for example, by responding to commands from the CND 108, accessing stored data written in whole or in part by the CND 108, or by other operations as provided throughout this disclosure.
[0123] Figure 3 The example CND 18 includes a second device 312 that communicates with the second network. The example second device 312 includes a configurable Ethernet switch that reads communications from the second network. In some embodiments, the second device 312 receives messages from the first network 104 via the first device 314, for example, in a format transmittable on the second network. The example first device 314 includes a CEG that communicates with the Ethernet switch via a port on the Ethernet switch that is provided for messages from the first device 314. Accordingly, Figure 3 An illustration of a second device 310 on a second network communicating with a first device 308 via the CND 108 is provided.
[0124] The example system includes external devices 110, 114, 204 in communication with CND 108. Figure 3 In the example of FIG, the external device 110, 114, 204 can communicate through the transceiver 304 and / or via direct access to the network of the vehicle 202 (e.g., using a service port, an OBD port, WiFi, Bluetooth, etc.). The external device is structured to adjust the configuration of the CND 108 - for example, by changing the stored data providing published available data, associated permissions, defined applications, defined flows, defined endpoints, defined devices, etc. In some embodiments, the external device has an associated permission value, and the CND 108 permits changes based on the associated permission value, such as preventing adjustments to changes associated with certain networks, devices, endpoints, applications, flows, etc.
[0125] The example system includes a first network as a bus network, which can further be a CAN bus network. The example system includes a second network as an Ethernet network, which can have any selected topology, such as a data bus architecture. In some embodiments, the Ethernet network can have a data bus architecture as a hardware topology, but logically operate differently (e.g., as a switched network).
[0126] refer to Figure 4 , the example system includes CND 108 having a first network gateway device 402 and a second network gateway device 404. Figure 4 In the example of , the first network gateway device 402 is: a CEG that accesses one or more CAN-based networks 406, each having one or more endpoints 408 - for example, devices coupled to the CAN networks 406 that provide communications to the corresponding CAN networks 406 and / or receive communications from the corresponding CAN networks 406. Figure 4 The example depicts two CAN networks 406 that can be arranged to facilitate integration (e.g., to logically divide components of a vehicle by function, by location in the vehicle, and / or any other arrangement, such as groups of related components communicating on a common CAN network 406). In the example, the first network gateway device 402 communicates with both CAN networks 406, although the CND 108 may include and / or may be configured to accommodate more than one CEG, e.g., using a CEG to access each CAN network 406 and / or each CEG to access a subset of the CAN networks 406 on the vehicle. Figure 4 The example of FIG. 4 depicts a bus network 406, and for purposes of illustration, the network 406 is described as a CAN network, but the network 406 can be any type of network as described throughout this disclosure. The endpoint 408 can be any type of endpoint capable of communicating with the network 406 (such as a controller, smart sensor, or actuator) or other device capable of providing communications to and / or receiving communications from the network 406.
[0127] Figure 4 The examples describe CND 108 as including network gateway devices 402, 404, but CND 108 may be separate from one or more of the network gateway devices 402, 404 and may configure the operation of the network gateway devices 402, 402, such as by adjusting stored data thereon, adjusting stored data accessible to the devices 402, 404, providing commands thereto, and / or performing any other operations as set forth throughout this disclosure.
[0128] exist Figure 4In the example of , the second network gateway device 404 is an Ethernet switch that accesses an Ethernet-based network 410, schematically depicted as a plurality of endpoints 412 communicating with a plurality of ports 414 of the Ethernet switch 404. The ports 414 are schematically depicted and can be logical ports, hardware ports, or a combination of these. The physical topology of the Ethernet network 410 can be a bus arrangement, a hub arrangement, a star arrangement, or any other type of network topology, and it can be different from the logical topology of the Ethernet network 410. The second network gateway device 404 is depicted as having a network interface 416, which can include physical port connections. In some embodiments, the second network gateway device 404 is a configurable Ethernet switch that can include a processor, computer-readable storage (e.g., for storing instructions, configuration information, buffers for data communication and / or collection operations, etc.). For clarity of illustration and the present invention, these aspects are not shown, but they may reside on the second network gateway device 404, within the same housing as the second network gateway device, on a board separate from the network interface 416 and / or from the rest of the second network gateway device 404 (e.g., mounted on a separate printed circuit board), located on another device in the system and in communication with the second network gateway device 4040 (e.g., on the first network gateway device 404, on a vehicle controller, and / or on another controller in the system), and / or distributed across a combination of these locations.
[0129] exist Figure 4 In the example of FIG4 , the first network gateway device 404 includes one or more network interfaces 418 (and / or network interface circuitry) that communicatively couple the first network gateway device 404 to the network 406, and translation circuitry 420 that configures messages from the Ethernet network 410 for transmission to the network 406 and / or configures messages from the network 406 for transmission to the Ethernet network 410. Additionally or alternatively, the translation circuitry 420 configures messages for delivery from one of the networks 406 to another of the networks 406—for example, where the networks 406 are of different types, utilize different protocols, would otherwise have conflicting source or destination information, and / or would otherwise have different characteristics that are managed by the first network gateway device 404 to ensure message compatibility, successful mission operation of the vehicle, and / or to achieve any other configuration operations as set forth in this disclosure. The conversion circuitry 420 is schematically depicted as a single device, but may be implemented as one or more devices, for example where multiple conversion circuitry 420 components each implement one type of configuration, interact with one type of network 406, distribute the processing and / or memory operations of the conversion circuitry 420, or for any other reason depending on the particular system. Figure 4In the example of , the first network gateway device 404 provides a message to the Ethernet switch in response to a corresponding message on the CAN-based network 406. Figure 4 In the example of , the first network gateway device 404 provides the message to the port 414 of the Ethernet switch. Figure 4 In the example shown, any messages provided from network 406 appear on Ethernet network 410 as messages on a port between translation circuitry 420 and network interface 416, and are received from Ethernet network 410 via a port between translation circuitry 420 and network interface 416. Translation circuitry 420 allows for configuration operations between messages between which endpoints on each network 406, 410 can communicate, as mediated by CND 108.
[0130] Figure 4 The example further includes an on-board diagnostic (OBD) interface 422, which in the example communicates with a dedicated OBD port 424. For purposes of illustration, Figure 4 The examples are non-limiting, and the OBD interface 422 can be associated with any network or more than one network (e.g., to support multiple OBD tools that can be received by a vehicle). Example embodiments include an OBD interface 422 associated with a second network gateway device 402, such as where the OBD system is largely CAN-based, thereby allowing for reduced traffic between the translation circuit 420 and the network interface 416 due to many OBD parameters being native to one or more of the CAN networks 406. The OBD interface 422 can alternatively reside on an Ethernet network 410 or on more than one network 406, 410 of the system. Regardless of the location of the OBD interface 422 and the networks 406, 410, the origin of the OBD-related data, OBD requests, and information can be made available to the OBD port 424 (which can be a physical connection, a wireless connection, or another external connection including a mobile data connection) via operation of the CND 108 to authorize and provide cross-network communication from endpoints of either of the networks 406, 410. Additionally, Figure 4 The example utilizes the OBD interface 422 as a non-limiting example, but subject to configurable adjustments by the CND 108, any type of special, dedicated and / or proprietary interface may be provided in a manner similar to the interfaces and ports that may make any data from any endpoint on the networks 406, 410 available.
[0131] The example system includes a CND 108 interposed between an electrical sensor and one of networks 406 and 410 and configured to provide a sensed value on the network in response to an electrical response of the electrical sensor. For example, one of the networks 406 may be an electrical connection to a second network gateway device 402 having a corresponding endpoint 408 as an electrical sensor, and whereby a conversion circuit 420 converts an electrical signal from the sensor into communication for a corresponding network (e.g., network 410 or another network 406). In an example, the conversion circuit 420 may perform processing operations on the electrical signal, such as analog / digital (A / D) processing, determination of an indicated bit, determination of an indicated value, debouncing the signal, filtering the signal, diagnostic bit detection (e.g., determination of a fault and conversion to a corresponding fault value and / or conversion of a predetermined voltage value to a corresponding fault value), saturation management (e.g., limiting an output to a predetermined value), slew limiting (e.g., applying a rate of change limit to the indicated value), and the like. The electrical signal from the sensor, where present, may be a voltage value, a frequency value, an indicated resistance value, or any other type of sensor electrical value as known in the art.
[0132] In another example, a system includes a CND 108 interposed between an electrical actuator and one of the networks 406 and 410 and configured to provide a command value from the network as a configured electrical response to the electrical actuator. For example, one of the networks 406 may be an electrical connection to a second network gateway device 402 having a corresponding endpoint 408 as an electrical actuator, and whereby a conversion circuit 420 converts communications from the corresponding network (e.g., network 410 or another network 406) into an electrical signal for the actuator. In an example, the conversion circuit 420 may perform processing operations on the electrical signal, such as digital-to-analog processing, determination of a corresponding value from an indicated bit, provision of a diagnostic bit, saturation management, slew limiting, and the like. The electrical signal to the actuator (if present) may be a voltage value, a frequency value, a modulated value, or any other type of actuator electrical value as known in the art. In some embodiments, the electrical actuator may additionally have sensed values (e.g., position feedback, acknowledgement, etc.) and / or other feedback values (e.g., certain electrical values indicating that the actuator has a fault condition, is non-responsive, is stuck, is saturated, etc.) that may be provided on the same or different electrical connections, and which may be logically part of the same network 406 or different networks (e.g., actuation on one network 406 and feedback on a second network 406).
[0133] It can be seen that in cases where an endpoint does not require knowledge about how communications to other endpoints are to be performed or where other endpoints are located, Figure 4 The embodiment provides communication between endpoints on different networks. Without limitation to any other aspects of the present disclosure, Figure 4 Embodiments of the present invention provide the capability to operate a vehicle network having devices distributed across different networks, including networks of different types. Additionally, Figure 4 Embodiments provide for operation of a vehicle as a device moves between networks, regardless of whether the device has changed communications capabilities. For example, a first device on a CAN network that is moved to an Ethernet network can continue to operate utilizing an appropriate configuration of CND 108, as messages utilized by devices from a CAN network can be moved to an Ethernet network and made available to devices in the new location. In certain embodiments, the migrated device can continue to utilize a previous algorithm (e.g., the same local control) - for example, computer-readable instructions specifically constructed for the details of the previous CAN message, including bit depth, resolution information, message rate, floating / fixed point data properties, etc., wherein CND 108 is configured to encapsulate the entire original CAN message into an Ethernet message (e.g., frames, packets, and / or in a specified manner) so that the migrated device can receive the previous CAN message as originally presented and utilized by the same local control. Accordingly, Figure 4 Examples and Figure 4 The principles set forth allow changes in the mix of endpoint devices between networks, whether across multiple vehicles (e.g., changes that occur during a design revision, model year, etc.) or within the same vehicle (e.g., changes that occur during service, upgrades or changes to endpoints, upgrades, fittings, recall replacements, etc.), with only updates to the CND 108 being required to support the changes. In certain embodiments, Figure 4 Examples and Figure 4 The principles set forth allow for changes in the mix of endpoint devices between networks without requiring an update to the configuration of CND 108, such as where a range of endpoints are considered available in more than one possible network location and / or configuration and where CND 108 is configured to determine the arrangement of endpoints present on a vehicle and utilize a selected configuration accordingly (e.g., from among two or more available configurations). Figure 4 Examples and Figure 4 The principles set forth further allow for changes to the mix of endpoint devices between networks, at least within a predetermined range of endpoint devices and configurations, to support vehicle operation without any changes to the vehicle and even with only intermittent or no communication with external devices for the configuration of CND 108.
[0134] refer to Figure 5, an example system includes: a CND 108 that regulates communications between networks on a vehicle, where the networks may be physically, logically separated (e.g., as a virtual local area network (VLAN) or other logical separation scheme), and / or two or more of the networks may be of different types. Figure 5 The embodiments are generally Figure 4 The present disclosure is consistent with the embodiments of the present disclosure, with some differences being depicted to highlight certain aspects of the present disclosure. Figure 5 Examples include: additional interfaces 504 , 506 , which may be separate networks or network zones relative to network 406 . Figure 5 The example depicts a vehicle control device interface (VCDI) 508, which can be an interface to any type of vehicle controller (e.g., an engine controller, a transmission controller, an anti-lock braking system (ABS), an advanced driver assistance system (ADAS) controller, a door controller, a battery controller, a head unit, an interactive instrument panel, etc.), including a controller that provides communications at endpoint 504 and / or an electrical interface such as to sensors, actuators, or a combination of sensors and actuators. Figure 5 The example depicts an additional interface 506 towards endpoint 502, which may be any type of communication device as understood in the art or as described herein. Figure 5 In the embodiment of FIG, network interface circuits 418, 508 are depicted between endpoints 408, 502 and translation circuit 420 to allow translation circuit 420 to interface with many types of networks that may be present on a vehicle. Interface circuits 418, 508 may be located with translation circuit 420 or located elsewhere and communicatively coupled to the associated network and translation circuit 420. Figure 5The example further depicts networks 512, 514, which are communicatively coupled to the first network gateway device 404 via endpoint 412 on the same network as the network interface 416. In some embodiments, the CND 108 does not have or require specific knowledge of the networks 512, 514 or the associated endpoints 516, 518, as communication to the networks 512, 514 is provided via endpoint 412. However, the CND 108 is structured to provide communications from networks in communication with the second network gateway device 402 (such as network 406) and / or networks interfaced at endpoints 504, 506. Communications from the second network gateway device 402 may provide the requested information (e.g., ambient temperature, door position, vehicle speed), for example, as an encapsulated payload providing the information or as a native message (e.g., a CAN message indicating ambient temperature, door position, vehicle speed; and / or a LIN message with associated sensor information). Accordingly, endpoints 516 , 518 may send and receive tunneled messages with network 406 (or other networks) in a shared format, or otherwise receive information from any network onboard the vehicle, subject to mediation by CND 108 .
[0135] refer to Figure 6 , an example system includes: a CND 108 that regulates communications between networks on a vehicle, where the networks may be physically, logically separated (e.g., as a virtual local area network (VLAN) or other logical separation scheme), and / or two or more of the networks may be of different types. Figure 6 The embodiments are generally Figure 4 The embodiments of the present invention are consistent with those of the present invention, with some differences being depicted to highlight certain aspects of the present disclosure. Figure 4 Any flexibility in the arrangements depicted, Figure 6 The example of FIG. 4 depicts translation circuitry 420 located in first network gateway device 404 .
[0136] Without limiting any other aspects of the present disclosure, Figure 6Co-location as depicted in and utilized herein may indicate physical co-location (e.g., translation circuitry 420 located within a shared housing with first network gateway device 404 and / or on the same board as first network gateway device 404) and / or logical co-location (e.g., grouping of operational responsibilities of hardware, such as connections, connectivity, operational instructions, stored data, data storage, and / or processing resources, etc.). Determining a co-location scheme depends on: the purpose of co-location (e.g., sharing hardware resources, reducing external interfaces, simplifying and / or diversifying the risk profile of the co-located component and / or other components in the system associated with the co-located component); the nature of the co-located component (e.g., hardware implementation, processing, and / or memory resources associated with the co-located component); the division of ownership of the co-located component (e.g., manufacturer, supplier, service provider, vehicle owner, vehicle operator); operational responsibilities of the component and / or vehicle (e.g., warranty, operational liability, service, insurance, uptime responsibility, etc.); and / or integration responsibilities of the component (e.g., installation, design, meeting floor space requirements, trade-offs between components, and / or the ability to influence these). Accordingly, in certain embodiments, co-locating components may include one or more of the following: locating components within a shared housing or housing group; locating components in selected geometric proximity; locating components in a selected logical arrangement (e.g., associated in the same flow or flow group, associated in the same application or application group, providing operational constraints such as parameter naming, memory assignment, execution order, etc.); locating components in a selected risk profile arrangement (e.g., located in the same impact zone, same temperature environment, same NVH environment, same EMI environment, subject to the same failure mode (e.g., electrical, logical, fault, physical impact and / or dependent on physical components such as pumps, cooling systems, etc.)); on the same board; and / or within a shared memory location (e.g., computer readable instructions located in a shared memory location and / or executed by the same processor resources). In the example, NVH is a "noise, vibration and harshness" environment, and EMI is an "electromagnetic interference" environment. One skilled in the art, having the benefit of this disclosure and information generally available when considering a particular system, can readily determine the implementation of co-located components as set forth in this disclosure. It will be appreciated that components arranged in one or more of the described co-location schemes may be co-located for some embodiments or not co-located for other embodiments, and / or may be co-located for purposes of some operating conditions but not co-located for purposes of other operating conditions.Certain considerations used to determine whether components are to be co-located and the co-location scheme selected for those components include (but are not limited to): the purpose of the co-location; the operating cost of the resources (e.g., communications, processing resources, operational limitations on the vehicle mission, operational impacts on the vehicle mission such as cooling requirements, power consumption, etc.); the capital cost of the resources (e.g., computing power, network infrastructure, memory resources, individual component quality or capability requirements, shielding requirements, data throughput whether inside or outside the vehicle, etc.); the integration cost for the components (e.g., floor space availability and cost, interface management, design flexibility and action limitation trajectory, and / or the ability to trade off and / or optimize with other aspects of the system); and / or the ability to distribute costs to other interested parties associated with the system (e.g., suppliers, manufacturers, customers and or service providers; and which may include the ability to distribute increased costs associated with increased capabilities and / or transaction costs between interested parties).
[0137] exist Figure 6 In the example of , translation circuitry 420 may provide communication by, without limitation, populating and / or reading from shared memory using network interface 416 and / or by communicating with port 414 (not shown).
[0138] refer to Figure 7 , an example system includes: a CND 108 that regulates communications between networks on a vehicle, where the networks may be physically, logically separated (e.g., as a virtual local area network (VLAN) or other logical separation scheme), and / or two or more of the networks may be of different types. Figure 7 The embodiments are generally Figure 4 The embodiments of the present invention are consistent with those of the present invention, with some differences being depicted to highlight certain aspects of the present disclosure. Figure 4 Any flexibility in the arrangements depicted, Figure 7 The example depicts translation circuitry 420 having a first portion 702 co-located with second network gateway device 402 and a second portion 704 co-located with first network gateway device 404. Portions 702, 704 of translation circuitry 420 may be separated for any reason, including at least separating translation operations by network (e.g., which network 406 is being served), by predetermined endpoints, by stream, by translation operations (e.g., processing of frame information, processing of payload information, managing capability differences through downsampling, upsampling, buffering, providing communication commands, encapsulating messages into another message format, etc.), and / or by communication direction (e.g., between selected networks, between gateway devices, between endpoints, between streams, or a combination thereof).
[0139] refer to Figure 8, an example system includes: a CND 108 that regulates communications between networks on a vehicle, where the networks may be physically, logically separated (e.g., as a virtual local area network (VLAN) or other logical separation scheme), and / or two or more of the networks may be of different types. Figure 8 The embodiments are generally Figure 4 The embodiments of the present invention are consistent with those of the present invention, with some differences being depicted to highlight certain aspects of the present disclosure. Figure 8 In the example of , the first network gateway device and the second network gateway device are co-located and omitted from being depicted as part of CND 108. In some embodiments, Figure 8 CND 108 may alternatively be a combined gateway device regulated by CND 108 rather than forming part of CND 108. In some embodiments, one or more portions of the combined gateway device may form part of CND 108, with other portions of the combined gateway device being regulated by CND 108.
[0140] As utilized herein and without limitation to any other aspects of the present disclosure, a policy includes a description of the data to be collected, such as data parameters, collection rates, resolution information, priority values (e.g., to sort data collection values for selection in response to non-nominal conditions where not all data collection parameters can be serviced, etc.). In certain embodiments, a policy further includes event information, which can be specified as parameter or quantity-based events (e.g., a given data value exceeds a threshold, etc.) and / or categorized events (e.g., a particular fault code, operating condition or state, or vehicle location / jurisdiction occurs). In certain embodiments, a policy further includes event responses (e.g., data values to be captured in response to the occurrence of an event) and / or other changes in the data collection scheme (e.g., an increased or decreased data collection rate, a change in the resolution collected, etc.). In some embodiments, the event response further includes a time frame associated with the occurrence of the event, for example, a time period after the event occurs to utilize the modified data collection scheme and / or a time period prior to the event occurs (e.g., utilizing a rolling buffer or other data collection operation to provide temporary information that can be captured later in the event). In some embodiments, changes to the data collection scheme for an event can include multiple changes - for example, changes over a period of time, further changes based on the progression of the event (e.g., if the severity of the event becomes worse), and / or criteria for determining that the event is cleared. In some embodiments, changes to the data collection scheme can be implemented based on event-related clearing of the same or another event, for example, implementing data collection changes until the next downtime event of the vehicle, until a service technician clears the event, due to a selected number of downtime events, etc. The strategy may additionally or alternatively include parameters for performing any adjustment operation for any adjusted component as set forth throughout this disclosure.
[0141] The utilization of policies herein may reference a partial policy, e.g., an implied policy to be implemented in response to a single data collection scenario from a single user, where the full policy is prepared, verified, and transmitted to the vehicle after one or more partial policies are aggregated. The utilization of policies herein may reference an unverified policy, e.g., after policies in response to multiple users are aggregated, but a verification operation for the policy has not yet been completed (e.g., before determining whether the data collection implied by the policy can be performed). The utilization of policies herein may reference a previously applied policy (e.g., a policy that existed on the vehicle before an updated version of the policy was transmitted to the vehicle and / or implemented on the vehicle). The utilization of policies herein may reference an updated policy, e.g., a verified policy that is pending for communication to the vehicle and / or confirmed by the vehicle (e.g., from CND 108).
[0142] refer to Figure 9, an example system includes: a CND 108 that regulates communications between networks on a vehicle, where the networks may be physically, logically separated (e.g., as a virtual local area network (VLAN) or other logical separation scheme), and / or two or more of the networks may be of different types. Figure 9 The embodiments are generally Figure 4 The embodiments of the present invention are consistent with those of the present invention, with some differences being depicted to highlight certain aspects of the present disclosure. Figure 9 In the example of , the first network gateway device 404 and the second network gateway device 402 are not co-located, and the CND 108 is depicted as communicating with the first network gateway device 404. The CND 108 can communicate with any one or more of the network gateway devices and / or can be located at least partially on one or more of the network gateway devices. Additionally or alternatively, the CND 108 can regulate communications between networks by accessing and / or adjusting memory locations available to one or more of the network gateway devices (e.g., policies, configuration instructions, configurable tables, etc.), where if the CND 108 does not communicate directly with the other network gateway devices, the relevant portions of the instructions (if any) can be passed to those devices. In some embodiments (not shown), the CND 108 can communicate with one or more of the network gateway devices using one or more of the networks (e.g., at port 414 of the first network gateway device 404). In some embodiments, CND 108 may be at least partially located on one or more of the network gateway devices, co-located with one or more of the network gateway devices, and / or included (at least partially) in components (e.g., conversion circuitry and / or network interface circuitry) of one or more of the network gateway devices.
[0143] refer to Figure 10 , depicting an example first network gateway device 404. Figure 10 In the example of , the first network gateway device 404 is a configurable Ethernet switch that includes an Ethernet network interface 416 (or Ethernet network interface circuit) having a plurality of ports 414 for communicating with an Ethernet network. The ports 414 can be physical ports, logical ports, or a combination thereof.
[0144] refer to Figure 11 , depicts an example second network gateway device 402. Figure 11In the example of , the second network gateway device 402 is a configurable edge gateway (CEG) that provides translation between a secondary network 406 and a primary network interface (e.g., an Ethernet network such as network 410). The use of references to the secondary and primary of the networks merely indicates a logical arrangement of the networks, where interfaces facing networks other than the primary are referenced as edge interfaces (e.g., interfacing with an edge gateway). In some embodiments, the primary network may have higher capabilities (e.g., bandwidth, throughput, and / or resource dedication), a larger number of devices or endpoints on it, a migration target network for endpoints over time (e.g., within the life of a vehicle, a group of vehicles, a model year, etc.), and / or a primary entry network for external communications (e.g., over-the-air updates, configuration updates, data collection, etc.), although particular embodiments may have some, all, or none of these considerations present for a network that is considered a primary network. Figure 11 The example of depicts an optional OBD interface 422 , which may be present elsewhere in the system or not present in the system.
[0145] refer to Figure 12 , schematically depicts a vehicle having multiple networks thereon, wherein communication between the networks is mediated by CND 108 . Figure 12 The arrangements are provided to illustrate certain aspects of the present disclosure and are non-limiting arrangements. Figure 12 Examples include endpoints 1202, 1204 coupled to a first network 406 (e.g., one or more vehicle controllers) and a plurality of endpoints 1206, 1208, 1210, 1212 coupled to a second network (e.g., an Ethernet network with a switch co-located with and / or at least partially separated from the CND 108). Figure 12 In the example of FIG100 , controllers 1202, 1204, 1206, 1208, 1210, 1212 are capable of passing communications between disparate networks of a vehicle, as mediated by CND 108. In certain embodiments, a given controller can be switched between networks, and communications with other controllers within the vehicle and / or communications external to the vehicle can be maintained, and further can be maintained regardless of whether the relevant controller (or external controller, application, or device) has knowledge of the switch.
[0146] refer to Figure 13 , schematically depicts a vehicle having multiple networks thereon, wherein communication between the networks is mediated by CND 108. For purposes of illustration, Figure 13 Examples include Figure 12 The same network and controller set are shown in the example. Figure 13In the example of FIG. 1 , controllers 1204, 1208, 1210, and 1212 have been co-located 1302, and controller 1204 has additionally been moved from first network 406 to second network. Co-location 1302 of controllers 1204, 1208, 1210, 1212 can be implemented in any manner, including consolidating the controllers into a fewer number of housings (e.g., 1-3 total housings instead of 4), onto a fewer number of boards (e.g., 1-3 boards instead of 4), and / or utilizing at least partially shared computing resources (e.g., shared processing, shared memory, shared cache, and / or a combination thereof). In some embodiments, utilization of CND 108 allows Figure 13 An arrangement that includes integrating vehicle controllers by providing communication accommodation and maintained connectivity with only a configuration update to CND 108 and / or with changes to the integration of vehicle controllers within an available predetermined configuration of CND 108 (and thus can be achieved without an update to CND 108). Additionally, the integrated controllers can provide multiple advantages, such as a reduction in network costs, a reduction in network traffic, a selected risk profile (e.g., placement of controllers and / or network routing in lower risk or diversified risk locations; and / or a reduction in risk to another system component that takes advantage of the footprint gains and / or cost savings of controller integration). In certain embodiments, the integrated controllers can enable deeper sharing of information between controllers (e.g., due to increased available network capacity, bypassing network limitations with respect to shared controllers, and / or utilization of shared memory resources), which can allow for more capable operation of the controllers and / or operation that was previously unavailable because shared information between controllers was not as readily available. In certain embodiments, CND 108 further enables the consolidation of controllers by decoupling the locations of the controllers from the endpoint locations (not shown) where they are required to be distributed (e.g., sensors and actuators that need to be placed in certain locations to perform their functions no longer need to be located near the respective controllers due to the operation of CND 108 and / or CEG 402). In certain embodiments, the consolidation of controllers allows for reduced costs and / or increased capabilities, such as by reducing hardware costs for shared computing resources, enabling higher capacity (e.g., processing power and / or memory) computing resources, or a combination of these. The operation of CND 108 thus allows for the consolidation of previously unavailable vehicle controllers. In certain embodiments, Figure 13 An example of this could be relative to Figure 12 Illustration of controller integration and / or unrelated embodiments.
[0147] refer to Figure 14, schematically depicts a vehicle having multiple networks thereon, wherein communication between the networks is mediated by CND 108. For purposes of illustration, Figure 14 Examples include Figure 12 Example of the same network and similar controller collection. Figure 14 In the example of FIG, the co-located controller 1302 includes a set of controllers 1402, 1404, 1406 and a CND 108 depicted as controllers on the co-located controller 1302. The CND 108 may be at least partially located on one or more of the co-located controllers 1402, 1404, 1406 and / or may be separate as depicted. In some embodiments, Figure 14 An example of this could be relative to Figure 13 Further controller integration and / or with Figure 12 and 13 An example of an unrelated co-located controller 1302 is shown.
[0148] refer to Figure 15 , schematically depicts a vehicle having multiple networks thereon, wherein communication between the networks is mediated by CNDs 1502, 1504. For purposes of illustration, Figure 15 The example utilizes two integrated controllers 1302, 1506, each comprising a set of co-located vehicle controllers as set forth throughout this disclosure. Figure 15 Examples include a first CND 1502 (or CND portion) interposed between the first network 406 and the second network (endpoint 412 directly coupled to CND 1502 and integrated controller 1506 directly coupled to CND 1502), and a second CND 1502 (or CND portion) interposed between the first network 406 and the second network (endpoint 412 directly coupled to CND 1504 and integrated controller 1302 directly coupled to CND 1502). In some embodiments, the second network associated with the first CND 1502 may be a separate network relative to the second network associated with the second CND 1504, but may be the same type of network (e.g., an Ethernet network) and / or may utilize the same or electrically coupled hardware relative to each other. Figure 15 The example illustrates CND 1504 as having primary network regulation for the first network 406, but regulation of the first network 406 may be distributed, shared, regulated based on endpoints, applications, and / or flows, etc. In some embodiments, regulation of the second network may be performed by only one of CNDs 1502, 1504 and / or be distributed, shared, regulated based on endpoints, applications, and / or flows.
[0149] The following description Figure 15 of multiple representative aspects, any one or more of which may be present in certain embodiments. Figure 15 Example aspects include shared regulation of networks by CNDs 1502, 1504, where either CND 1502, 1504 is fully or partially capable of supporting regulation of all networks, for example, if an endpoint, a network, another CND (or portion), and / or a controller experiences a failure, malfunction, or decreased operational capability. Figure 15 Example aspects include primary regulation of the network by one of the CNDs 1502, 1504, with the other CND being able to fully or partially support regulation of the network, for example, if an endpoint, network, master CND, and / or controller experiences a failure, malfunction, or reduced operational capability. Figure 15Example aspects of the integrated controllers 1302, 1506 include one or more of the integrated controllers 1506, 1302 being able to at least partially assume control operations for another of the integrated controllers 1506, 1302 if one of the integrated controllers loses capability, connectivity with endpoints, etc. In some embodiments, the CNDs 1502, 1504 are able to pass along parameters that were previously available only to the original controller 1302, 1506 in response to control operations being assumed by the replacement controller 1506, 1302. In some embodiments, redundant network routing availability may be used by the CNDs 1502, 1504 to provide at least partial connectivity between endpoints that lose connectivity when a portion of the network fails. CNDs 1502, 1504 may provide equivalent parameters (e.g., another endpoint capable of providing equivalent data), alternative parameters (e.g., another endpoint capable of providing alternative or backup parameters that may be used, at least in part, as a substitute for a lost parameter), identical parameters (e.g., where data from the original endpoint or identical data values from another endpoint may be routed through the remaining network infrastructure), and / or management parameters such as controller handoff communications, heartbeat or status communications, etc. In certain embodiments, one or both of CNDs 1502, 1504, or portions of a CND, may be co-located with another system component (e.g., one of the integrated controllers 1302, 1506). In certain embodiments, network routing for on-vehicle networks is provided to generate different risk profiles for on-vehicle networks, thereby reducing the risk of a single failure rendering the vehicle inoperable for the mission and / or inoperable for at least limp home operations, controlled shutdowns, data capture, etc. In certain embodiments, controllers, CNDs, and / or integrated controller locations may be selected to provide different risk profiles for associated equipment, thereby reducing the risk of a single failure rendering the vehicle inoperable for the mission and / or inoperable for at least limp home operation, controlled shutdown, data capture, etc. In certain embodiments, network routing for the on-vehicle network is provided to result in lower operating cost, installation cost, integration cost, overall risk profile, distribution of weight and / or footprint of components on the vehicle, etc.
[0150] refer to Figure 16 , schematically depicting several illustrative examples of message conversion and / or message encapsulation embodiments. Figure 16 The examples are illustrative to illustrate certain aspects of the present disclosure, but are not limited to the present disclosure. In certain embodiments, Figure 16 The operations depicted in FIG may be performed in whole or in part by a CEG, a CES, a conversion circuit, and / or a CND, and in some embodiments, Figure 16The operations depicted in the example can be regulated by CND. The first example message conversion 1602 includes a message from a first network having a payload 1610 and other frame information 1608. The other frame information may include a header, trailer aspects, and / or end bits, and may further be determined by the relevant protocol, network type, source endpoint, destination endpoint, or other aspects as known in the art. In some embodiments, the payload 1610 may be message data, a data value expressed by the message, or other information that is considered to be the content of the message. However, in some embodiments, for certain operations, during certain operating conditions, and / or for certain endpoints, the payload 1610 may be some other aspect of the message. For example, a network monitoring operation may utilize a timestamp, acknowledgment information, source and / or destination information, or other parts of the message as a payload. The example message conversion 1602 includes: separating the payload 1610 and packaging the payload into a new frame (or packet) 1612 within information configured for the target network. Additionally or alternatively, the new frame 1612 may include an identifier (e.g., source or destination), a timestamp, or other information that allows endpoints on disparate networks to be abstracted from knowledge of each other. In some embodiments, the payload 1610 may be processed, for example, to change the units utilized, the bit depth (e.g., 2 bytes versus 4 bytes), the precision expressed, floating point or fixed point conversion, etc.
[0151] A second example message transformation 1604 includes the original messages 1608, 1610, and is completely encapsulated within a new frame 1612, e.g., to provide the target endpoint with the original message as provided by the original source (e.g., to allow previously developed algorithms to operate as is without having to transform into a new message; to allow certain network monitoring operations to utilize the entirely original message, etc.). In some embodiments, the original payload 1610 or message frame 1608 can be processed, e.g., as previously described, with the source identifier, timestamp, etc. updated to a new transformation that is transformed to abstract the endpoint from each other, but provide otherwise equivalent or systematically aligned information.
[0152] The third example message transformation 1606 includes the original message 1608, 1610 with an adjusted payload 1614. The adjustment of the payload 1614 may include transforming the payload 1614 in some manner (e.g., a corrected value, a value based on virtual sensing or modeling of the original payload 1610, upsampling or downsampling the payload 1610, etc.), and may additionally or alternatively include processing of the payload. The third example message transformation 1606 depicts the adjusted payload 1614, although adjustments may additionally or alternatively be performed on other portions of the message frame 1608. In the third example message, a new frame 1612 is applied for transmission to another network.
[0153] refer to Figure 17 , schematically depicts a schematic depiction of the operation of downsampling a sequence of messages 1702. Figure 17 In the example of , a message sequence 1702 (eg, in the example, a series of five communications) is received, for example, at a network interface circuit of one of the network gateway devices. Figure 17 In the example of , the downsampling operation is responsive to any downsampling operation described herein, such as to match a receiving endpoint data rate, provide data represented by message 1702 at a scheduled rate, manage bandwidth on the vehicle's network and / or for off-vehicle communications, maintain buffer memory, or for any other purpose, including any downsampling operation of the present disclosure. Figure 17 In the example of , the downsampling device 1704 generates a transformed sequence of messages 1708 (e.g., as Figure 16 and related disclosures and / or processed in accordance with any other message conversion and / or message processing operations set forth herein), the downsampling device 1704 can be a conversion circuit, a network interface circuit, a CND, a circuit associated with a CND, a circuit regulated by a CND, and the like. For clarity of description, Figure 17 The example depicts a transformed sequence of messages 1708. However, the transformed sequence of messages 1708 may not all exist simultaneously, for example, as messages are transformed and sent, they may be removed from a cache, deleted, expire, etc. The sequence of messages 1708 is depicted to illustrate aspects of the present disclosure. Additionally or alternatively, the transformation of messages 1708 may be performed after a downsampling operation is performed, for example, to reduce utilization of processing resources. For example, some of the messages may be eliminated as part of the downsampling prior to performing the transformation operation (e.g., replacement of frame portions or metadata, encapsulation, processing of payload and / or frame portions, etc.). In Figure 17In an example, a downsampled sequence of messages 1706 is provided and transmitted, for example, to a different network gateway device, to a different network of the vehicle from which the first sequence of messages 1702 was received, to an external device (e.g., a service tool, a cloud server, an operator's mobile device, etc.), and / or stored on a memory storage device on the vehicle (e.g., for use in later data collection operations, as part of stored vehicle data, etc.). In the example, the five messages of the original sequence 1702 are downsampled into three messages of the downsampled sequence 1706. The downsampling operation can include converting selected messages from the original sequence 1702, for example, by converting the original 10 ms data stream 1702 into a downsampled 20 ms data stream 1706 using every other data message. Additionally or alternatively, the downsampling operation can include interpolation of data messages between the original values. For example, where the original data stream 1702 is a 40 ms data stream and the downsampled data stream 1706 is a 100 ms data stream, downsampling may include taking the message closest in time, or performing an interpolation operation (e.g., applying a linear fit, a spline fit, a polynomial fit, or other interpolation operation across data points) to use as the downsampled message 1706.
[0154] As utilized herein, a spanning data point or value indicates a data value in a downsampled message 1706 that is not aligned in time with the corresponding original data message 1702. As utilized herein, a non-spanning data point or value indicates a data value in a downsampled message 1706 that is aligned in time with or synchronized with the corresponding original data message 1702. It should be understood that the original data message 1702 and the downsampled message 1706 may additionally or alternatively have a phase difference, and accordingly, in certain embodiments, any or all of the original data messages 1702 may be non-spanning messages. In some embodiments, certain messages of the original data messages 1702 may be treated as non-spanning or synchronization data messages even in the presence of phase differences between the original data messages 1702 and the downsampled messages 1706, for example, to provide a baseline downsampled message 1706 stream that follows (e.g., in the time domain) a progress character of the original data message 1702 stream, and / or where any phase difference can be ignored for the purposes of a device or operation that utilizes the downsampled messages 1706 (e.g., where such device or operation has a response time, required reaction time, etc. that is significantly greater than the magnitude of any such phase difference).
[0155] In a further example, synchronized data values (e.g., every fifth data value when converting from 40 ms to 100 ms) may be utilized directly, or a fitting function may be utilized (e.g., to provide a smoothed, filtered, or otherwise processed stream of data values). In some embodiments, it may be desirable to utilize actual data values provided from the first data stream 1702 as downsampled data values 1706, where minor transient behavior from different time steps is not relevant to how the downsampled data values 1706 are utilized, or where timestamp data is also transmitted with the message and the differential time steps between messages can be accounted for in the utilization of the downsampled data 1706. In some embodiments, it may be desirable to utilize smoothed data values that simulate the temporal response behavior of the underlying data, which may be managed using interpolated data for spanning data values (e.g., a process responsive to the rate of change in the downsampled data 1706, such as a threshold test on the rate of change). In certain embodiments, such as where a downstream process is particularly sensitive to time variations in data message 1702 (e.g., the derivative portion of a PID controller), it may be desirable to ensure that all downsampled data messages 1706 are generated from the same process, and interpolation operations (or smoothing, filtering, or moving averages) may be performed to generate both spanned and non-spanned data values 1706. In certain embodiments, downsampled data message 1706 may further include metadata or other embedded information indicating whether the message corresponds directly to original data message 1702 or is a processed message (e.g., to allow for more than one use for downsampled data message 1706, for diagnostic operations of the device providing original data message 1702, and / or for any other purpose).
[0156] It can be seen that Figure 17 The downsampling operation allows communication between devices and / or processes with different data rate capabilities, expectations and / or usage of downsampled data. In addition, Figure 17 The downsampling operation allows for a reduction in network utilization while providing sufficient data for devices and / or processes to perform their intended functions, as well as having a desired time domain response (e.g., derivative behavior, integral behavior, step change response, etc.) for proper functioning of devices and processes that may depend on the time dynamics of the transmitted data values. As can be seen, Figure 17The downsampling operation allows for progressive updates of communication aspects (e.g., components, devices, processes, and / or operations that communicatively interact with a network and / or other components, devices, processes, and / or operations) of mobile applications having a mix of network configurations and / or legacy communication aspects (e.g., having lower data rate capabilities and / or data rate expectations, and / or different network protocols, features, message types, etc.) and updated communication aspects (e.g., having higher data rate capabilities and / or data rate expectations, and / or different network protocols, features, message types, etc.).
[0157] refer to Figure 18 , depicts a schematic depiction of the operation of upsampling a sequence of messages 1802. Figure 18 In the example of , a message sequence 1806 (eg, in the example, a series of three communications) is received, for example, at a network interface circuit of one of the network gateway devices. Figure 18 In the example of , the upsampling operation is responsive to any upsampling operation described herein, such as to match a receiving endpoint data rate, provide data represented by message 1806 at a scheduled rate, manage bandwidth on the vehicle's network and / or for off-vehicle communications, maintain buffer memory, or for any other purpose, including any upsampling operation of the present disclosure. Figure 18 In the example of , the upsampling device 1804 generates a transformed sequence of messages 1808 (e.g., as Figure 16 and related disclosures and / or processed in accordance with any other message conversion and / or message processing operations set forth herein, and), the upsampling device 1804 can be a conversion circuit, a network interface circuit, a CND, a circuit associated with a CND, a circuit regulated by a CND, and the like. For clarity of description, Figure 18 The example depicts a transformed sequence of messages 1808. However, the transformed sequence of messages 1808 may not all exist simultaneously. For example, as messages are transformed and sent, they may be removed from the cache, deleted, expired, etc. The sequence of messages 1808 is depicted to illustrate aspects of the present disclosure. Additionally or alternatively, the transformation of messages 1808 may be performed after performing an upsampling operation, for example, to reduce utilization of processing resources.
[0158] For example, some of the messages may be eliminated or adjusted as part of upsampling before performing conversion operations (e.g., replacement of frame portions or metadata, encapsulation, processing of payload and / or frame portions, etc.). Figure 18In the example of FIG18 , an upsampled sequence of messages 1802 is provided and transmitted, for example, to a different network gateway device, to a different network of the vehicle from which the first sequence of messages 1806 was received, to an external device (e.g., a service tool, a cloud server, an operator's mobile device, etc.), and / or stored on a memory storage device on the vehicle (e.g., for later data collection operations, as part of stored vehicle data, etc.). In the example, the three messages of the original sequence 1806 are upsampled into the five messages of the upsampled sequence 1802. The upsampling operation can include converting selected messages from the original sequence 1806, for example, changing the original 50 ms data stream 1806 into the upsampled 20 ms data stream 1802 by inserting one or more generated messages 1810. Additionally or alternatively, the upsampling operation can include interpolation and / or extrapolation of data messages between the original values. For example, where the original data stream 1806 is a 50 ms data stream and the upsampled data stream 1802 is a 20 ms data stream, upsampling may include obtaining the message closest in time, or performing interpolation and / or extrapolation operations (e.g., applying linear fitting, spline fitting, polynomial fitting, moving average, and / or low-pass filtering progression between available data points and / or between available data points and a predicted next data point) to serve as the upsampled message 1802.
[0159] As utilized herein, a spanning data point or value indicates a data value in an upsampled message 1802 that is not aligned in time with a corresponding original data message 1806. As utilized herein, a non-spanning data point or value indicates a data value in an upsampled message 1802 that is aligned in time with or synchronized with a corresponding original data message 1806. It should be understood that the original data message 1806 and the upsampled message 1802 may additionally or alternatively have a phase difference, and accordingly, in certain embodiments, any or all of the original data messages 1806 may be non-spanning messages. In some embodiments, certain messages of the original data messages 1806 may be treated as non-spanning or synchronization data messages even in the presence of phase differences between the original data messages 1806 and the upsampled messages 1802, for example to provide a baseline upsampled message 1802 stream following (e.g., in the time domain) progress characters of the original data message 1806 stream, and / or where any phase differences can be ignored for purposes of a device or operation utilizing the upsampled messages 1802 (e.g., where such device or operation has a response time, required reaction time, etc. that is significantly greater than the magnitude of any such phase difference).
[0160] In a further example, synchronized data values (e.g., every other data value when converting from 50 ms to 20 ms, such as a 0 ms phase value and a 100 ms phase value) can be utilized directly, or a fitting function can also be utilized (e.g., to provide a smoothed, filtered, or otherwise processed stream of data values). In some embodiments, it may be desirable to utilize actual data values provided from the first data stream 1806 as upsampled data values 1802, such as where minor transient behavior from different time steps is not relevant to how the upsampled data values 1802 are utilized, or where timestamp data is also transmitted with the messages and accordingly, the differential time steps between messages can be accounted for in utilizing the upsampled data 1802. Accordingly, in some embodiments, each message of the upsampled data values 1802 can directly correspond to one or more of the first data stream 1806 values (e.g., selecting a synchronized one, a closest one, and / or a most recent one of the first data stream 1806 values (e.g., retaining the transmitted value until the next value is available)).
[0161] In some embodiments, it may be desirable to utilize smoothed data values that emulate the temporal response behavior of the underlying data (e.g., the original message 1806), which may be managed using interpolated / extrapolated data for both spanning data values (e.g., processes responsive to the rate of change in the upsampled data 1802, such as threshold checks on the rate of change) and / or for non-spanning data values. In some embodiments, such as where a downstream process is particularly sensitive to temporal variations in the data message 1806 (e.g., the derivative portion of a PID controller), it may be desirable to ensure that all upsampled data messages 1802 are generated from the same process, and interpolation / extrapolation operations (and / or smoothing, filtering, and / or moving averages) may be performed to generate both spanning and non-spanning upsampled data values 1802. In some embodiments, the non-spanning upsampled data values 1802 are utilized directly (e.g., to provide an upsampled data 1802 stream with the actual content of the data message 1806 as much as possible), and the spanning upsampled data values are processed as described herein. In some embodiments, all original messages 1806 are provided in the upsampled data 1802 stream, with additional non-spanned messages added to achieve the data rate of the upsampled data 1802 stream (e.g., to provide all original messages 1806 and otherwise support the upsampled rate). In some embodiments, the upsampled data message 1802 may further include metadata or other embedded information indicating whether the message corresponds directly to the original data message 1806 or a processed message (e.g., to allow for more than one use of the upsampled data message 1802, for diagnostic operations on the device providing the original data message 1806, and / or for any other purpose).
[0162] In some embodiments, the spanning upsampled data value 1802 can be determined based on a predicted value between the non-spanning data values, which can be performed based on a virtual sensor (e.g., a model of the value utilizing other information available in the system) and / or an extrapolation fit operation. In some embodiments, the determination of the spanning upsampled data value 1802 can additionally or alternatively include providing a predicted and / or interpolated / extrapolated value that provides an expressed rate of change of the upsampled data value 1802 determined based on the original data value 1806 and / or adjusted based on characteristics of the device, component, operation, and / or process utilizing the upsampled data value 1802. For example, the upsampling operation can include performing a predictive operation and / or interpolation / extrapolation to determine a rate of change for the value; and providing a final spanning upsampled data value 1802 that provides a predicted rate of change for the upsampled data value 1802. In some embodiments, the operation of providing the upsampled data value 1802 includes the operations of determining a rate of change (or derivative) determination operation in a device utilizing the upsampled data value 1802, and adjusting the rate of change of the upsampled data value 1802 in response to parameters of the rate of change determination in the device—e.g., accounting for data related to a time step (e.g., ΔT / 5 ms or a change in temperature every 5 milliseconds) and / or a time constant (e.g., a time constant of a low-pass filter, a time constant implicit in a moving average calculation, etc.) utilized for the derivative operation, wherein the upsampled data value 1802 is adjusted to provide a desired response in a rate of change calculation to be performed on the upsampled data value 1802. For example, in the case of an upsampling operation with a significant difference in time step between the original data value 1806 and the upsampled data value 1802 (e.g., 50 ms to 5 ms), operations such as linear interpolation / extrapolation of the data value may provide significant distortion to, for example, the output of a low-pass filter operated by a device utilizing the upsampled data value 1802, which may be configured to process true 5-ms data. Accordingly, in an example, upsampling the raw data values 1806 may include adjusting the raw data values 1806 based on a predicted response of a 5-ms device of a determined value, which may provide a significant difference in the trajectory of the upsampled data values 1802 between non-spanning data points relative to simple linear extrapolation, a moving average, etc. Adjusting the expressed rate of change may be performed for the upsampled data 1802 and / or for the downsampled data 1706, or may be omitted.
[0163] In certain embodiments, configuration information for upsampling and / or downsampling operations, such as whether to utilize non-spanned raw data values 1702, 1806 directly, metadata to be stored with the upsampled and / or downsampled data 1802, 1706, processing operations to be performed on spanned and / or non-spanned data values, whether to transfer all raw data values 1702, 1806, operations to provide for rates of change expressed in the upsampled and / or downsampled data 1802, 1706, and / or parameters (e.g., filter constants, derivative operations, etc.) determined by rates of change in devices utilizing the upsampled and / or downsampled data 1802, 1706, may be provided in whole or in part at design time (e.g., when configuring the mobile application and various network communications devices with which the mobile application is to be used), and / or may be provided or updated during runtime operation. In some embodiments, one or more aspects of the configuration information for upsampling and / or downsampling operations may be provided as part of a policy, configuration directive, and / or configuration table that may be accessible to CND 108 regulating communications between devices on a separate network for mobile applications. In some embodiments, one or more aspects of the configuration information for upsampling and / or downsampling operations may include default values that may be adjusted and / or updated, including as part of a policy, configuration directive, and / or configuration table.
[0164] refer to Figure 19 , an example system that may form part of a mobile application 1902 or a vehicle includes a first network zone 1904 of a vehicle having a first number of interconnected endpoints 1906 and a second network zone 1908 having a second number of interconnected endpoints 1910. The example system includes a CND 1912 between the network zones 1904 and 1908, wherein the CND 1912 mediates communications between the endpoints 1906 and 1910. Figure 19 In the example of , the first network zone 1904 is a first network, the second network zone 1908 is a second network, and the networks 1904 and 1908 are networks of different network types. Figure 19 In the example of , the first network zone 1904 includes a common data bus 1905, such as a CAN bus, and the second network zone 1908 utilizes a distributed topology, such as having devices 1910 communicating with switches 1914, which may be Configurable Ethernet Switches (CES). Figure 19In the example of , the configurable edge gateway 1916 (CEG) is in communication with the first network zone 1904 and is capable of reading messages from and / or providing messages to the public data bus 1905. Figure 19 In the example of , CEG 1916 communicates with CES 1914 on the second network zone 1908, and CEG 1916 can appear to CES 1914 as an endpoint device of the second network zone 1908 and / or can be associated with physical and / or logical ports of the second network zone 1908.
[0165] exist Figure 19 In the example of FIG, CND 1912 performs the following operations: regulating the communication between endpoints 1906, 1910 by configuring the operation of CEG 1916 and / or CES 1914. For clarity of this description, Figure 19 The arrangement is schematically depicted, depicting different components for CND 1912, CEG 1916, and CES 1914. However, CND 1912, CEG 1916, and CES 1914 may be combined in whole or in part, provided in the same housing and / or on the same circuit board, and / or subdivided in whole or in part. Additionally or alternatively, one or more aspects or all of CND 1912, CEG 1916, and / or CES 1914 may be located using another controller in mobile application 1902 (such as a vehicle controller) and / or using a controller associated with endpoint 1910. Network zones 1904, 1908 are depicted as having separate physical components, but network zones 1904, 1908 may be logically separate (e.g., as separate virtual networks on a single physical backbone) and / or may be separated in whole or in part by a combination of physical and / or logical structures. The example embodiment includes physically separated network zones 1904, 1908 as depicted. The example embodiment includes the first network zone 1904 being a CAN bus network and the second network zone 1908 being an Ethernet-based network. The example embodiment includes the first network zone 1904 being a legacy network with endpoints 1906 being legacy devices and / or legacy-compatible devices, and the second network zone 1908 having endpoints 1910 being new, updated, upgraded, and / or migrated devices.
[0166] Example operations for regulating communications between endpoints 1906, 1910 include, but are not limited to, operations such as those described below. The regulating operations may be performed for endpoints, for associated endpoint groups, and / or for network zones. Associated endpoint groups may be associated based on flows, applications, service groups, controllers, vehicle functions, source addresses for communications, and / or destination addresses for communications. In certain embodiments, identifiers may be provided to applications, service groups, and / or flows as a means of associating related components such as endpoints. The regulating operations may be performed by, but are not limited to, a CND, a network gateway, a network interface circuit, and / or a gateway interface circuit. The regulating operations are described throughout this disclosure in the context of certain example regulating devices, but embodiments may be configured to have other devices that perform the regulating. Example communication and / or regulating operations include: Providing communication between the first endpoint 1906 and the second endpoint 1910 (in either direction), including configuring the communication (e.g., protocol, message information, metadata, parameter elements, etc.) for the receiving network zone and / or endpoint device; Encapsulating a message from the first network zone 1904 and providing the encapsulated message to the second network zone 1908; Determining whether a requesting device (and / or associated flow) on one of the network zones (1904, 1908) has permission to request communications from a device on another of the network zones, and providing communications in response to a permission determination; adjusting at least one of a data rate, a requested resolution, and / or a requested response time for communications between devices of the network zones based on an admission determination for the requesting device, communications capabilities of the requesting and / or offering devices, and / or network performance parameters of one or both network zones (e.g., currently available bandwidth, absolute or current network capacity, network utilization, etc.), and / or a priority value for communications associated with the requesting device; Performing upsampling and / or downsampling operations on data transferred between network zones; Mirroring communications from the first endpoint 1906 to a port of the second network zone 1908, including encapsulating, configuring, processing, and / or upsampling or downsampling the mirrored communications; providing communications from the first endpoint 1906 to a device coupled to the second network zone 1908, such as a diagnostic device, an OBD device, a service tool, a manufacturing tool, an OEM tool, and / or a network monitoring device, and / or wherein providing communications includes packaging, configuring, processing, and / or upsampling or downsampling the provided communications, and / or wherein the provided communications may be unicast, multicast, and / or provided as a subscription service; providing communications from the second endpoint device 1910 to a device coupled to the first network zone 1904 or the second network zone 1908 (such as a diagnostic device, an OBD device, a service tool, a manufacturing tool, an OEM tool, and / or a network monitoring device), and / or wherein providing communications includes encapsulating, configuring, processing, and / or upsampling or downsampling the provided communications, and / or wherein the provided communications may be unicast, multicast, and / or provided as a subscription service; providing communications from a device coupled to the second network zone 1908 (such as a diagnostic device, an OBD device, a service tool, a manufacturing tool, an OEM tool, and / or a network monitoring device) to the first endpoint 1906, and / or wherein providing the communications includes encapsulating, configuring, processing, and / or upsampling or downsampling the provided communications, and / or wherein the provided communications may be unicast, multicast, and / or provided as a subscription service; o further providing the communication as a command value, e.g., wherein the first endpoint 1906 performs an operation related to the mission of the mobile application in response to the command value (e.g., setting a set point, target value, or threshold in response to the command value); providing communications from a device coupled to the second network zone 1908 (such as a diagnostic device, an OBD device, a service tool, a manufacturing tool, an OEM tool, and / or a network monitoring device) to the first endpoint 1906, and / or wherein providing the communications includes encapsulating, configuring, processing, and / or upsampling or downsampling the provided communications, and / or wherein the provided communications may be unicast, multicast, and / or provided as a subscription service; o further providing the communication as a test execution value, e.g., wherein the first endpoint 1906 performs an operation related to an active context execution operation of the mobile application (e.g., performing certain operations for a service test, an active diagnostic operation, etc.) in response to the command value; providing communications from a first endpoint 1906 to a plurality of second endpoint 1910 devices, wherein the provided communications are configured to meet a superset of the requirements of the second endpoint 1910 devices (e.g., data rate, resolution, units, etc.), and wherein the provided communications may be unicast, multicast, and / or provided as a subscription service; Parsing a communication value from a first device (e.g., a first endpoint 1906, a second endpoint 1910, and / or a device coupled to a network zone 1904, 1908, such as a diagnostic device, an OBD device, a service tool, a manufacturing tool, an OEM tool, and / or a network monitoring device), determining a target device (e.g., a communication recipient and / or a communication provider responsive to the communication value) in response to the parsed communication value, and configuring communications for the target communication recipient and / or communication provider in response to the parsed communication value. For example, the communication value may include a universal and / or normalized component identifier (e.g., turbine temperature, front passenger door actuator, etc.), and the CND 1912 determines the corresponding endpoint 1906, 1910 corresponding to the component identifier based on the current configuration of the mobile application, and may further determine communication routing, packaging, processing, etc. to be translated between the first device and the target device. For example, such operations allow the configuration and placement of devices on the network zone to be changed without requiring the device, service personnel, or other requestors to track the specific configuration and placement of the devices; o Additionally or alternatively, such operations include: CND 1912 storing configuration information in response to configuration changes (e.g., replacement or movement of a device from one network zone to another, changes to communication parameters or capabilities of a device, etc.), and / or performing runtime determinations to confirm the location, identity, configuration, communication parameters, and / or capabilities of a device, which may be utilized during runtime operation and / or stored for later utilization and / or stored as a default configuration subject to further updating; Performing any one or more of these operations on a group or subgroup of devices, such as where the devices are integrated in relation to a single endpoint 1906, 1910, but can be viewed as separate devices by other endpoints or devices (e.g., diagnostic devices, OBD devices, service tools, manufacturing tools, OEM tools, and / or network monitoring devices) communicating with the network zones 1904, 1908. For example, such operations allow for multiple configurations, updates, and / or upgrades of a mobile application, where a first configuration has two (or more) devices with separate endpoints 1906, 1910, and a second configuration has two (or more) devices utilizing a single endpoint 1906, 1910 (and / or two devices integrated into a single device). Example and non-limiting embodiments include: consolidating multiple sensors (e.g., smart sensors with network communication capabilities, multiplexing signals, etc.) that communicate with network zones 1904, 1908 through a single interface; and / or replacing the interface of multiple components behind a single network interface (e.g., a single communication device, such as an edge gateway or a configurable edge gateway, that interfaces with a single network zone 1904, 1908 as a single endpoint 1906, 1910 and manages communications for the associated devices. In a further example, such operation allows devices to communicate across network zones regardless of changes in configuration to support upgrades and updates related to the relationship of the devices to the endpoints 1906, 1910 and to support backward compatibility (e.g., later configurations, later control distribution between devices, etc., where operation of CND 1912 allows an earlier system with a different configuration to support the updated configuration and / or control distribution between devices); o Additionally or alternatively, such operations include: CND 1912 storing configuration information in response to configuration changes (e.g., intervention of a single endpoint between more than one device and a network zone, integration of devices, etc.), and / or performing runtime determinations to confirm the location, identity, configuration, communication parameters and / or capabilities of a device and / or the integration state of a device, which may be utilized during runtime operation and / or stored for later utilization and / or stored as a default configuration subject to further updating; Performing any one or more of these operations on a group or subgroup of devices, such as where the devices are distributed across more than one endpoint 1906, 1910, but can be viewed as a single device by other endpoints or devices (e.g., diagnostic devices, OBD devices, service tools, manufacturing tools, OEM tools, and / or network monitoring devices) communicating with the network zones 1904, 1908. For example, such operations allow for multiple configurations, updates, and / or upgrades of mobile applications, where a first configuration includes a device with a single endpoint 1906, 1910 and a second configuration has a device (or portion thereof) utilizing more than one endpoint 1906, 1910 (and / or a previously integrated device comprised of two or more separate devices in the second configuration). An example and non-limiting embodiment includes separating a group of sensors (e.g., smart sensors with network communication capabilities, multiplexed signals, etc.) communicating with the network zones 1904, 1908 via a single endpoint 1906, 1910 into one or more sensors each having separate endpoints 1906, 1910 (and / or subgroups of multiple sensors each having separate endpoints). In a further example, such operation allows devices to communicate across network zones regardless of changes in configuration to support upgrades and updates related to the relationship of the devices to the endpoints 1906, 1910 and to support backward compatibility (e.g., later configurations, distribution of control between devices, etc., where operation of the CND 1912 allows an earlier system with a different configuration to support a later configuration); o Additionally or alternatively, such operations include: CND 1912 storing configuration information in response to configuration changes (e.g., partitioning of a device behind a single endpoint on a single network zone into more than one endpoint and / or across more than one network zone, etc.), and / or performing runtime determinations to confirm the location, identity, configuration, communication parameters and / or capabilities of the device and / or the integration state of the device, which may be utilized during runtime operations and / or stored for later utilization and / or stored as a default configuration subject to further updates; Implementation of a service-oriented architecture, in which CND 1912 determines available services (e.g., data parameters available for communication, command values available for execution, and / or configurations of these, such as rate information, units, resolution, precision, accuracy, availability descriptions, related data, and / or operating conditions), publishes available services, and / or determines subscribing clients (e.g., devices, streams, and / or endpoints) for available services; o Additionally or alternatively, such operations include: CND 1912 determining permissions and / or authorizations for publishing available services, for viewing available services (and / or portions of available services), and / or for subscribing to available services; o Additionally or alternatively, such operations include: CND 1912 identifying the subscribing entity as an endpoint, device, stream, and / or external device, such as a diagnostic device, an OBD device, a service tool, a manufacturing tool, an OEM tool, and / or a network monitoring device; o Additionally or alternatively, such operations include: CND 1912 determining a priority for service-oriented communications, which may be dependent on a publishing device, endpoint, or associated flow and / or dependent on a subscribing device, endpoint, or associated flow; o Additionally or alternatively, such operations include: CND 1912 adjusting service-oriented architecture operations in response to an operational condition (e.g., a mobile application operational condition, a network status of one or more affected network zones, a communication status of one or more external devices, etc.); o Additionally or alternatively, such operations include: CND 1912 accessing stored information setting forth available services, publication parameters (permissions, priorities, relevant operating conditions, etc.) and / or subscribing entity information; o Additionally or alternatively, such operations include: CND 1912 updating stored information in response to one or more of: received updates, such as policy descriptions, service configuration descriptions, etc.; runtime updates from endpoints, devices, and / or flows, such as, but not limited to, those performed during startup or shutdown operations of a mobile application; o Additionally or alternatively, such operations include: CND 1912 implementing a service-oriented architecture based on runtime operations with or without storing information and / or updating or without updating stored information; and / or o Additionally or alternatively, allowing updates to stored information, runtime updates to stored information, and / or runtime operations that implement a service-oriented architecture in response to priorities and / or permissions associated with the device, endpoint, and / or flow requesting the updates and / or runtime implementation; Additionally or alternatively, the operation of the example CND 1912 includes adjusting the operation of any one or more of the above items in response to the operating conditions of the mobile application (e.g., adjusting communication operation during certain operations, such as: high power operation; high transient operation; shutdown operation; startup operation; selected operation descriptions, such as vocational operation, power take-off (PTO) operation, charging operation, cruise control operation, autonomous vehicle operation, etc.). The adjustment of communication can be qualitative (e.g., allowing or disallowing certain communication types, certain communication priority thresholds, etc. during certain operating conditions; and / or capturing certain data values as data capture events during certain operating conditions), quantitative (e.g., controlling communication rates, network zone utilization, external device communication rates, etc.), or a combination thereof (e.g., controlling communication rates for certain communication types, etc.), and can include increasing or decreasing communication capabilities based on the operating conditions and / or communication types (e.g., providing reduced device communication capabilities during shutdown operations, but increasing external device communication capabilities during shutdown operations; increasing device communication capabilities for certain devices or flows, but decreasing device communication capabilities for other devices or flows during startup operations, etc.); · Additionally or alternatively, the operation of the example CND 1912 includes: adjusting the operation of any one or more of the above items in response to non-nominal operating conditions associated with the mobile application, wherein the non-nominal operating conditions include conditions such as the following: degradation of a network area (e.g., loss of throughput, loss of communication with one or more endpoints of the network area, injection or presence of noise onto the network area, injection of traffic onto the network area, physical failure of at least a portion of the network area, etc.); failure conditions of one or more devices (e.g., wherein the CND 1912 adjusts a data source associated with the failed device, adjusts a data rate associated with the failed device, implements a backup data source for the failed device, reroutes data to a backup data recipient for data provided to the failed device, implements an event-driven data collection scheme in which the failure of the device is an event, etc.); loss of control functionality of a vehicle controller (e.g., wherein the loss of control functionality indicates that the vehicle controller is lacking data values to perform its mission; wherein the loss of control functionality indicates that the vehicle controller has lost communication with the associated network area; and / or wherein the loss of control functionality is an indication made by the vehicle controller or another controller in the system that the vehicle controller is unable to perform its mission or a portion of its mission). Further example operations of CND 1912 in response to non-nominal conditions include one or more of the following: o Providing the data value to the vehicle controller from an alternate source (e.g., from a different endpoint, network zone, etc., and which may include packaging, configuring, processing, and / or upsampling or downsampling the alternate source communication, which may result in communication that is identical to the lost original data value or may be sufficient as an alternative communication of the backup data value to the vehicle controller); o providing data values to a second vehicle controller to replace all or part of a lost control function of the vehicle controller, e.g., where the second vehicle controller is configured to act as a backup for the vehicle controller, where the second vehicle controller may be fully capable of performing the lost control function and / or may be capable of performing backup operations in place of the lost control function (e.g., utilizing more limited capabilities); the data values provided to the second vehicle controller may be the same data values as the data values provided to the vehicle controller, a backup source communication (e.g., having a different data rate, resolution, units, precision, etc.), or another data value entirely (e.g., where the second vehicle controller utilizes a different data set to perform fully capable or backup operations). Additionally or alternatively, the CND 1912 may be capable of providing data from any network zone 1904, 1908 to the vehicle controller and / or the second vehicle controller, which may itself be on any network zone 1904, 1908; o Suppressing communication of one or more data values in response to a non-nominal condition, e.g., wherein a fault condition, loss of a device or endpoint, etc., indicates that the one or more data values are not utilized; wherein the one or more data values are of low priority in view of the non-nominal condition; and / or wherein the one or more data values are indicated as invalid in view of the non-nominal condition (e.g., a sensor value from a sensor having a fault or failure condition); o Transferring communications from a first network zone (e.g., a degraded network zone) to a second network zone, such as when an endpoint and / or device is reachable through more than one network zone (e.g., where the zones are logically separate but physically coupled, where more than one physical route is available between the relevant endpoints (e.g., reference Figure 15 ), and / or wherein a second vehicle controller and / or a second endpoint coupled to a second network zone is capable of performing operations (or portions thereof and / or backups thereof) of a first vehicle controller and / or a first endpoint coupled to a first network zone); o Repeating the communication from the first network zone (e.g., the downgraded network zone) on the second network zone; o Transferring an endpoint from a first network zone (e.g., a downgraded network zone) to a second network zone, e.g., where the transferred endpoint is physically coupled or coupleable to both the first network zone and the second network zone (e.g., where the separation between the network zones is a logical separation, and / or where the endpoint is reachable through more than one network zone, such as Figure 15 ), wherein the operations of CND 1912 include: adjusting addressing, protocols, encapsulation operations, and / or any other operations used to effectuate the transfer of the endpoint, which may further include updating the location of the transferred endpoint with other devices / endpoints in the system or translating communications with other devices / endpoints in the system without notification of the transfer; o A combination of these, such as transferring an endpoint from a first network zone to a second network zone, and transferring related communications to the second network zone and / or repeating related communications on the second network zone; Regulating communications between endpoints of the first network zone (and / or one or more additional network zones) and external devices (e.g., diagnostic devices, OBD devices, service tools, manufacturing tools, OEM tools, network monitoring devices, operator devices, cloud computing devices, and / or third-party applications), wherein regulation between endpoints of the first network zone and external devices includes any one or more of the above operations, and / or may further include: limiting communications based on non-nominal conditions of components of the system (e.g., endpoints, devices, flows, network zones, etc.); limiting communications based on operational conditions of mobile applications; limiting communications based on permissions and / or permissions of endpoints, associated flows, and / or external devices. or priority; limiting communications based on an aggregate data value (e.g., corresponding to an associated data service provider for the communication; corresponding to a group of endpoints; corresponding to an associated flow; and / or corresponding to an entity associated with any one or more of these), the aggregate data value being aggregated based on time (e.g., daily, weekly, monthly, etc.), operational status (e.g., journey, event, etc.), and / or wherein the data value includes one or more of a total data sent / received value, a data rate value, and / or a combination of these; and / or limiting communications based on an external data access type (e.g., cellular, WiFi, Bluetooth, hardware / port plug-in, etc.); and / or Any one or more combinations of the above.
[0167] The described operations of CND 1912 may be incorporated into or included in any portion of the embodiments described throughout this disclosure. It should be understood that permissions and / or priorities with respect to any aspect, including endpoints, related entities (e.g., owners, manufacturers, operators, service personnel, OEMs, third parties, etc.), flows, devices (e.g., controllers, actuators, sensors, tools and / or external devices, switches, gateways, etc.), may vary depending on the operating conditions of the mobile application and / or the state of one or more devices (e.g., the same device or different devices in which the permissions or priorities are being considered). Further, permissions and / or priorities may vary depending on the operations and / or communications being performed. For example, a given flow may have a high priority and / or permission level for viewing published available services, but a low priority and / or permission level for publishing available services and / or subscribing to available services. In another example, a given endpoint may have a high priority for transmitting data values to another endpoint (e.g., on a different network zone) during one operating condition (e.g., high-power acceleration), but a low priority for transmitting data values to another endpoint during another operating condition (e.g., steady-state cruise control operation). As explained herein, priority generally relates to a comparison between competing interests for resources (e.g., network bandwidth, response time, data storage, access to limited data resources, etc.), while permissions, as explained herein, generally relate to the ability to perform a requested operation, such as the ability to request certain data, metadata, data rates, data storage, access to a device and / or external devices, etc. Accordingly, aspects can have separate priorities and permissions, such as a high priority and a low permission level (e.g., the aspect has a high priority for access to a limited number of data values, functionality, etc.) or any other combination.
[0168] Resolution of competing priority interests may be performed in any manner, such as: always favoring the highest priority requester; providing weighted responses based on priority (e.g., servicing high priority requests more often than lower priority requests); and / or utilizing a credit-based scheme that allows lower priority requests to be serviced after a period of time and / or multiple requests.
[0169] As used herein, the mission of a device (e.g., a controller, endpoint, vehicle, mobile application, etc.) should be broadly construed to include at least the relevant functionality, structure, capabilities, and operations of the device to support the operation of the mobile application to perform the intended functionality or primary functionality of the mobile application. Without limitation to any other aspect of the present disclosure, the intended functionality or primary functionality of the mobile application includes one or more of the following: motorized operation of the mobile application according to designed motorized capabilities (e.g., with specified torque, speed, responsiveness, etc.); and / or non-motorized operation of the mobile application (e.g., industrial operation, vocational operation, pumping operation, provision of shaft power, range of motion, and control thereof) with designed non-motorized capabilities. In certain embodiments, the intended functionality or primary functionality of the mobile application includes non-nominal operational responses that may be less capable than the designed motorized or non-motorized capabilities, such as operation in a limp home mode, communication of a fault or failure condition, and / or prevention of further degradation of the vehicle and / or mobile application. In certain embodiments, the intended functionality or primary functionality of the mobile application includes sending and / or receiving external data, performing update operations, facilitating service operations, facilitating update and / or upgrade operations, and the like. Accordingly, the mission of the device can vary between mobile applications based on the current operating conditions of the mobile application and / or based on the current state of the mobile application and / or components, devices, and / or their controllers. Those skilled in the art, having the benefit of this disclosure and generally available information when considering a specific mobile application, should readily understand the mission of a mobile application, the mission of the device of the mobile application, and the variability of these operating conditions and state conditions across mobile applications.
[0170] refer to Figure 20 , the example system includes a first network zone 1904 having a first risk exposure profile 2002 and a second network zone 1908 having a second risk exposure profile 2004. Figure 20 In the example of , the first risk exposure profile 2002 is different from the second risk exposure profile 2004. As utilized herein, a risk exposure profile includes at least one dimension considered by related components (e.g., Figure 20In the example of FIG, the first network zone 1904 and / or the second network zone 2004) are subjected to a risk profile, the at least one dimension being such as: geometric risk (e.g., risk to the component due to its location within the installed mobile application); environmental risk (e.g., risk to the component from factors in the installed environment, such as temperature, contaminants, NVH, EMI, heat transfer environment (e.g., exposure to radiant energy, conductive heat transfer, and / or convection or lack thereof) and / or exposure to environmental disturbances, such as service technician impact, tool drop, etc.); failure mode risk (e.g., any identified or apparent failure mode of the mobile application or its components, such as, but not limited to, exposure to short circuit events, open wire events, and / or failed components of the mobile application (e.g., exhaust components, engine components, aftertreatment components, and / or components with conditions that induce failure); any other component of energy that causes failure, such as increased temperature, electrical potential, rotational energy, mechanical energy, etc.); possible risk types (e.g., where a given risk can affect multiple areas or systems of a vehicle, components located in those areas or coupled to those systems can share the risk type, while components isolated from those areas or systems may not share the risk type, regardless of the proximity of those components or other considerations); and / or possible disturbance risks (e.g., where a given disturbance (such as a specific service event, operating condition, weather event, non-nominal charging voltage, etc.) can affect multiple areas or systems of a vehicle, components located in those areas or coupled to those systems can share the disturbance risk, while components isolated from those areas or systems may not share the disturbance risk, regardless of the proximity of those components or other considerations).
[0171] In some embodiments, the first risk exposure profile 2002 differs from the second risk exposure profile 2004 in at least one aspect of the risk exposure profile, such as being located in different locations on the vehicle (e.g., one on the left side and one on the right side); being installed so that a given environmental risk is unlikely to affect both network zones; being installed so that a given failure mode is unlikely to affect both network zones; being installed so that a considered risk (e.g., impact, accident, operational failure, non-nominal operation of a component, etc.) is unlikely to affect both network zones; and / or being installed so that a considered disturbance is unlikely to affect both network zones. In some embodiments, the difference in one risk dimension is sufficient to make the risk exposure profiles different—for example, one or more failures (e.g., complete loss of electrical power) are likely to affect both network zones, but the network zones may nonetheless have different risk exposure profiles with respect to other potential failures. Additionally, each network zone may have exposure to the same type of risk, such as a first network zone exposed to a front impact and a second network zone exposed to a rear impact, but the network zones may nonetheless be considered to have different risk profiles.
[0172] exist Figure 20 In the example of , CND 1912 is located between the first network zone 1904 and the second network zone 1908 and is configured to mediate communications between the network zones 1904 and 1908. Figure 20 In the example shown, if another of the network zones 1904, 1908 experiences a failure or degradation event, the CND 1912 can communicate with the remaining one of the network zones 1904, 1908. Accordingly, the CND 1912 can reroute communications away from the failed network zone 1904, 1908, e.g., to a backup controller (not shown), other network zones (not shown), and so on. Figure 20 The example allows for partitioning of risk of network zones 1904, 1908, thereby allowing designed redundancy and continued operation of the mobile application (whether compatible with the mobile application mission or in reduced capacity operation) in the event that one of the network zones 1904, 1908 experiences a failure or degradation.
[0173] refer to Figure 21 , the example system includes a mobile application 1902 having a first network zone 1904, a second network zone 1908, and a third network zone 2108. The network zones 1904, 1908, 2108 may have different risk exposure profiles, and / or any two of the network zones 1904, 1908, 2108 may have different risk exposure profiles. The example system includes a CEG 2102 communicatively coupled to the first network zone 1904, a CES 2104 communicatively coupled to the second network zone 1908, and a second CES 2106 communicatively coupled to the third network zone 2108. Figure 21 In the example of FIG, CND 1912 is distributed, where portions of CND 1912 are configured to mediate communications for each network zone 1904, 1908, 2108. The components are described as CEG 2102, CES 2104, and second CES 2106. Figure 21 The examples are non-limiting examples, and the network zones 1904, 1908, 2108 may be of any type, wherein communications are operated by any component. In certain embodiments, the corresponding operating component (in Figure 21 In the example of FIG, CEG 2102, CES 2104, and CES 2106) may share a risk exposure profile with associated network zones 1904, 1908, 2108, or may have a different risk exposure profile than associated network zones 1904, 1908, 2108. Additionally or alternatively, a corresponding portion of CND 1912 may share a risk exposure profile with associated network zones 1904, 1908, 2108. Figure 21The embodiments illustrate the division of risk into network zones and components and the scheduled application of redundancy therebetween, which can be applied in any manner. For example, networks of the same type (e.g., network zones 1908, 2108) can have different risk exposure profiles, while a single-instance network (e.g., network zone 1904) can have another risk exposure profile or a risk exposure profile shared with one of the other networks (e.g., network zones 1908, 2108)—for example, because the single-instance network has no available backup network and is already a single point of failure mode in the system. In certain embodiments, one or more of the networks (e.g., network zone 2108) can be installed with a very low risk exposure profile (e.g., central location, isolation from the environment, perturbation and / or failure mode risk, etc.) and can be configured to operate as a backup for one or more other networks (e.g., network zone 1908). In some embodiments, the configuration for operating backup operations includes one or more of the following: redundant connectivity to endpoints for other networks; providing a backup controller and / or stored executable commands to perform backup control operations; providing in the relevant operating component (e.g., CES2106) to perform data communication operations for the other network; and / or providing in the relevant CND 1912 portion to perform any or all operations of the other CND 1912 portion. In some embodiments, any or all of the networks can be configured to operate backup operations for one or more or all of the other networks. In some embodiments, one or more portions of CND 1912 can be co-located with the associated operating components in the operating components, located within a housing with the associated operating components in the operating components, and / or located on the same board with the associated operating components in the operating components. In some embodiments, one or more portions of CND 1912 can be co-located with controllers distributed throughout the vehicle, located within a housing with the controllers distributed throughout the vehicle, and / or located on the same board controller distributed throughout the vehicle. In some embodiments, one or more portions of CND 1912 may be provided as executable instructions stored on another device (e.g., an operating component, a vehicle controller, and / or another controller), where a processor executing the instructions causes the device to perform one or more operations of CND 1912. Figure 21 In the example of , CES 2104 mediates communication between the second network zone 1908 and the third network zone 2108, such that communication occurs at a port of CES 2106, for example. Figure 21 In the example of , CEG 2102 regulates communication between the first network zone 1904 and the third network zone 2108 , such that the communication occurs at separate ports of CES 2106 , for example.
[0174] Example and non-limiting network types for each network zone include one or more of the following: a Controller Area Network (CAN), a Media Oriented Systems Transport (MOST) network, a Local Interconnect Network (LIN), a FlexRay network, a Time Triggered Protocol (TTP) network, a Low Voltage Differential Signaling (LVDS) network, an Audio Video Bridging (AVB) compatible network, customized versions of any one or more of the above, and / or proprietary versions of any one or more of the above.
[0175] refer to Figure 22 , depicting an example apparatus for performing network redundancy operations. Figure 22 Example with Figure 21 The present invention is consistent with the embodiments of the present invention, but can be applied to any system and / or mobile application as described throughout this disclosure. The example apparatus includes: network redundancy circuitry 2202 that selectively provides regulation control commands 2204, wherein one or more CND portions 1912 respond to the regulation control commands 2204 to enable inter-network communications 2206, 2208, 2210 between network zones (e.g., 1904, 1908, 2108) of the mobile application. Example and non-limiting inter-network communications 2206, 2208, 2210 include rerouting data between network zones, transferring endpoints between network zones, a first CND portion assuming regulation of a different network zone associated with a second CND portion, utilizing alternate data sources and / or backup control operations, and / or transferring, mirroring, and / or suppressing one or more data values between and / or on one or more network zones.
[0176] Example and non-limiting mediation control commands 2204 include indications that: one or more endpoints of a network zone are unavailable; one or more endpoints of a network zone are in a fault condition; and / or one or more endpoints of a network zone are unable to perform the mission operations of the corresponding endpoints and / or are providing invalid communications. In some embodiments, mediation control commands 2204 include one or more of the following: commands to utilize alternative data sources and / or backup control operations; commands to transfer data points between available network zones; and / or commands to transfer, mirror, and / or suppress one or more data values between and / or across one or more network zones. In some embodiments, mediation control commands 2204 may include a status condition (e.g., "Network zone 1 is down"), a list of one or more endpoints, or other values indicating the status of endpoints and / or network zones, wherein one or more CND portions 1912 respond to mediation control commands 2204 to implement communication and / or control redundancy operations according to stored configuration information.
[0177] refer to Figure 23, the example mobile application 1902 includes a first network zone 1904, a second network zone 1908, a third network zone 2322, and a fourth network zone 2324. The network zones can be of any type. Figure 23 In the example, the first network area 1904 is a CAN network type, the second network area 1908 is an Ethernet network type, the third network area 2322 is an Ethernet network type, and the fourth network area 2324 is an electrical signal area. The example network areas 1904, 1908, 2322, 2324 are selected to illustrate certain aspects of the present disclosure and are non-limiting. Figure 23 In the example of FIG, CND 1912 regulates communications between endpoints of network zones by: communicating with a first CEG 1916 that provides communications between endpoints of a first network zone 1904 and a second network zone 1908 by providing communications at a port of a first CES 1914; communicating with a second CEG 2308 that provides communications between endpoints of a fourth network zone 2324 and the second network zone 1908 by providing communications at a port of the first CES 1914; communicating with a first CES 1914 that is communicatively coupled to a second CES 2320, thereby allowing communications between the second network zone 1908 and a third network zone 2322 (and further with the first network zone 1904 and the fourth network zone 2324 due to communications between CEGs 1916, 2308); and providing communications between endpoints of the third network zone 2322 and the other network zones 1904, 1908, 2324 (at Figure 23 2320) through a second network zone 1908. The CND 1912 further regulates communications between endpoints of the network zones 1904, 1908, 2322, 2324 and the external communication device 2326, for example, by communicating permissions, priority information, etc. to the first CES 1914 and / or the second CES 1916, which are selectively enabled to communicate with the external communication device 2326 (e.g., a head unit). Figure 23 The CND 1912 in the example is depicted as being between the CES 1914 , 1916 devices and the external communication device 2326 , although the CES 1914 , 1916 devices can be directly coupled to the external communication device 2326 , and / or the external communication device 2326 can be coupled to a port of one of the network zones 1908 , 2322 . Figure 23The example depicts a transmitter / receiver 2328 performing communication operations with an external device (e.g., a cloud server, a service tool, a manufacturing tool, an operator device, etc.). In some embodiments, the transmitter / receiver 2328 may be integrated with the external communication device 2326, and / or more than one transmitter / receiver 2328 may be present. Additionally or alternatively, multiple external communication access routes may be available, such as, but not limited to, physical port access on one or more of the network zones 1904, 1908, 2322, WiFi transmitters / receivers, Bluetooth transmitters / receivers, etc.
[0178] The CND 1912 is depicted as a separate device, but may be co-located with one or more of the network operations components 1916, 1914, 2308, 2320, co-located with a vehicle controller (not shown), and / or distributed across several devices. Figure 23 The example further includes: a network redundancy circuit 2202, depicted separately for ease of description, that selectively provides regulation control commands to provide redundancy and data rerouting commands to the network operations components 1916, 1914, 2308, 2320 in response to degradation or loss of a network zone and / or an endpoint of the network zone. Example operations of the network redundancy circuit 2202 include: routing communications from a first endpoint 2302 on a first network zone 1904 to a second endpoint 2304 on a second network zone 1908 (e.g., during nominal operation); and rerouting communications from the first endpoint 2302 on the first network zone 1904 to a third endpoint 2312 on a third network zone 2322 (e.g., in response to a failure or non-nominal operation of the second endpoint 2304).
[0179] Example operations of CND 1912 include providing differential priority and / or permitted access for a second endpoint 2304 on a second network zone 1908 relative to a third endpoint 2306 on a second network zone 1908, wherein the differential priority and / or permitted access relate to communications with an external communication device 2326, storage of data (e.g., in a buffer and / or in memory storage on any device of the mobile application 1902), and / or data communication throughput, collection rate, etc.
[0180] Example operations of CEG 2308 include performing analog / digital (A / D) processing of communications on fourth network zone 2324. For example, endpoint 2310 may be a sensor that provides an electrical signal representing a sensed value and / or an actuator that responds to an electrical signal from CEG 2308. In some embodiments, endpoint 2310 may include more than one electrical signal, such as a diagnostic signal, a heartbeat, or a status signal. In some embodiments, CEG 2308 performs signal processing of communications from endpoint 2310, such as debouncing, filtering, saturation (e.g., reserving high or low values for diagnostic information), rescaling, linearization, or other operations. In some embodiments, CEG 2308 generates a processed payload of the electrical signal, which may include one or more of the following: converting the electrical signal into a sensed value (e.g., pressure, temperature, velocity, etc.); changing the units of the sensed value (e.g., from °F to K or to °C); adjusting the bit depth of the sensed value (e.g., preparing a 32-bit equivalent of a nominal 16-bit value provided by endpoint 2310 or a lookup table associated with endpoint 2310); normalizing the sensed value (e.g., providing a 0-1 value with an agreed-upon meaning for the sensed parameter, and / or providing a voltage equivalent for the sensed voltage, such as when an algorithm operating on a receiving endpoint such as 2314 on the third network zone 2322 utilizes a different sensor with a different calibration, etc.); applying a time shift to the sensed value (e.g., to compensate for sensor response time, network communication time, etc.); and / or converting the sensed value between floating point and fixed point; and / or rescaling the fixed point value of the sensor. A person skilled in the art, with the benefit of this disclosure and generally available information when considering an electrical signal-based endpoint 2310 and a data recipient endpoint (or any other endpoint), can readily determine the payload processing operations to be performed to provide a configured payload for the recipient endpoint from the electrical signal provided by the endpoint 2310 in question. It should be understood that payload processing can be performed in reverse, for example, taking an incoming payload from a communication and configuring an electrical signal for the endpoint 2310 from the incoming payload (e.g., a command to adjust an actuator, an electrical signal that may not be configured for a specific endpoint 2310, etc.). The example CEG 2308 further generates communications, such as to be provided at a port of the CES 1914, by providing a communication frame, encapsulating the processed payload, and having a protocol configured for the second network zone 1908 (in the example).In some embodiments, CEG 2308 processes at least a portion of a communication frame, for example, by adjusting a timestamp (e.g., where endpoint 2310 provides a timestamp that is not properly configured for mobile application 1902), applying a timestamp (e.g., where a timestamp is expected but endpoint 2310 does not provide one), providing or adjusting a source indicator for the communication (e.g., where endpoint 2310 does not have the ability to provide a source indicator and / or utilizes a source indicator that is not properly configured for mobile application 1902), and / or providing or adjusting a destination indicator for the communication.
[0181] Example operations of the CEG 1916 include: processing payloads of communications from endpoint devices 1906, 2302 (e.g., an adjustment unit); and / or performing any other payload processing operations set forth in the present disclosure. Example operations of the CEG 1916 include: encapsulating payloads of communications from endpoint devices 1906, 2302; and / or encapsulating all or a portion of a communication frame from endpoint devices 1906, 2302 into a communication having a protocol configured for a second network zone 1908 (in the example). In some embodiments, the encapsulated portion of the communication frame from the endpoint device 1906, 2302 may be additionally processed, for example, to apply or adjust a timestamp, to apply or adjust a source indicator, and / or to apply or adjust a destination indicator. In some embodiments, encapsulation of frames or portions thereof allows communication between CAN devices (e.g., on a separate network zone) with or without processing, including where one or more CAN devices are not directly coupled to the CAN network, but are being communicated through another endpoint (e.g., endpoint 2316 on a third network zone 2322, in the example). Figure 23 In the example, the third network zone 2322 is an Ethernet network).
[0182] In some embodiments, CEGs 1916 and 2308 can share ports of CES 1914 and / or can be coupled to the second network zone 1908 using separate ports. The network zones of a mobile application can have any selected topology, including but not limited to bus, serial, mesh, hub, ring, and / or star topologies. An example mobile application includes a first network zone provided as a first virtual local area network (VLAN) and a second network zone provided as a second virtual local area network (VLAN). In an example, the first and second network zones can share network physical hardware and / or portions thereof.
[0183] Reference again Figure 23, an example system includes a first vehicle controller (e.g., endpoint 2302) on a first network zone 1904, a second vehicle controller (e.g., endpoint 2304) on a second network zone 1908, and network redundancy circuitry 2202 that selectively provides regulation control commands, wherein a CND 1912 adjusts regulation communications between the first network zone 1904 and the second network zone 1908 in response to the regulation control commands. Example and non-limiting regulation control commands include one or more of the following: a non-nominal condition corresponding to the first vehicle controller 2302; a loss of a data element associated with the first vehicle controller 2302; and / or a loss of control functionality of the first vehicle controller 2302. Example and non-limiting adjustments to regulated communications include one or more operations such as: providing alternate data elements to the first vehicle controller 2302 (e.g., from a different endpoint providing the same data, similar data, and / or backup data); providing data elements corresponding to the loss control function to the second vehicle controller 2304 (e.g., where the second vehicle controller 2304 is configured to perform backup operations for all or part of the loss control function); and / or providing data values normally available on the first network zone 1904 to the second network zone 1908 (e.g., to provide the second vehicle controller 2304 with data utilized to perform backup operations for all or part of the loss control function). Example adjustments to regulated communications include suppressing communication of data values normally available on the first network zone 1904 in response to the loss control function of the first vehicle controller 2302 (e.g., where the suppressed data values are no longer required on the first network zone 1904 and / or where the suppressed data values are no longer indicated as valid data). The example system includes the CND 1912 providing data values normally available on the first network zone 1904 to the second network zone 1908 (e.g., to provide data to the second vehicle controller 2304 to perform a fallback operation for all or part of a loss control function) as processed data values (e.g., to configure the data values for utilization by the second vehicle controller 2304). The loss control function includes one or more of: a loss of all or part of a control function nominally performed by the first vehicle controller 2302; a loss of communication with an endpoint 1906 of the first network zone (e.g., the endpoint 1906 providing data values utilized to perform the loss control function); a loss of functionality of the first vehicle controller 2302 (e.g., due to a fault code, a failure condition, and / or invalid communication provided by the first vehicle controller 2302); and / or a loss of communication with the first vehicle controller 2302.
[0184] The example system includes a first vehicle controller 2302 in a first risk exposure profile and a second vehicle controller 2304 in a second risk exposure profile, wherein the first risk exposure profile is different from the second risk exposure profile. Example and non-limiting differences between the risk exposure profiles include one or more of the following: geometric differences; environmental differences; failure mode differences; possible risk type differences; and / or possible disturbance differences.
[0185] Certain alternative and / or additional regulatory control commands provided by the network redundancy circuit 2202 include one or more of the following: a non-nominal condition corresponding to the first network area 1904; a loss of communication between at least one endpoint 1906 of the first network area and the first network area 1904; a physical failure of at least a portion of the first network area 1904; and / or a bandwidth limitation of the first network area 1904. Example and non-limiting adjustments to regulate communications include one or more of the following: routing at least one communication from first network zone 1904 to second network zone 1908; repeating at least one communication from first network zone 1904 to second network zone 1908; transferring at least one endpoint (e.g., 1906) from first network zone 1904 to second network zone 1908; transferring and / or repeating communications associated with at least one endpoint (e.g., 1906) from first network zone 1904 to second network zone 1908; and / or transferring and / or repeating communications associated with at least one endpoint (e.g., 1910) from second network zone 1908 to first network zone 1904 (e.g., utilizing endpoint 1910 as a backup data source for a missing endpoint 1906 from first network zone 1904). For purposes of illustration, operations are described between first network zone 1904 and second network zone 1908, but operations may be performed between first-second network zones, first-third network zones, and / or second-third network zones. Additionally or alternatively, certain operations (e.g., transferring an endpoint from one network zone to another) mean that: the associated endpoint can be moved between network zones, which may be available in circumstances that should be understood, but include at least: where the endpoint is coupled to or can be coupled to more than one network zone; where the endpoint is configurable to provide valid communications to more than one network zone (e.g., where the endpoint can detect network protocols, frame configurations, etc., and / or where the endpoint responds to commands from network redundancy circuitry 2202 and / or CND 1912 to adjust network protocols, frame configurations, etc.); where the network zones are compatible (e.g., consistent protocols, frame configurations, etc. and / or able to communicate with some variability in protocols, frame configurations, etc.); and / or where the network zones are separate virtual local area networks (e.g., where the separation between the respective network zones is at least partially logical, rather than physical).
[0186] In some embodiments, CND 1912 may be co-located and / or have portions co-located with one or more vehicle controllers (not shown) of the system. Figure 15 The example system includes a vehicle controller 2302 on a first network zone 1904, a first portion of a CND 1912 co-located with the vehicle controller 2302, wherein the first portion of the CND 1912 includes non-transitory computer-readable instructions configured to, when executed by a process of the vehicle controller 2302, perform at least a portion of an operation to regulate communications.
[0187] In some embodiments, CND 1912 includes a portion co-located with a vehicle controller (not shown), wherein the portion of the CND includes an Ethernet switch (e.g., 1914), wherein the network zone 1908 includes an Ethernet network, wherein communications between endpoints of network zone 1908 and another network zone 1904 are routed through the Ethernet switch 1914 (e.g., wherein CEG 1916 provides communications from network zone 1904 through ports of CES 1914), and wherein the Ethernet switch 1914 is located within a housing with the vehicle controller and / or on the same board with the vehicle controller.
[0188] In some embodiments, CND 1912 includes a portion co-located with a vehicle controller (not shown), wherein the portion of the CND includes a CEG (e.g., 1916), wherein the network zone 1904 includes an Ethernet network, wherein communications between endpoints of network zone 1904 and another network zone 1908 are routed through CEG 1916 (e.g., wherein CEG 1916 provides communications from network zone 1904 to network zone 1908 via a port of CES 1914), and wherein CEG 1916 is located within a housing with the vehicle controller and / or on the same board with the vehicle controller.
[0189] The example system includes a second vehicle controller 2304 on a second network zone 1908, wherein a CND 1912 includes a first portion co-located with the vehicle controller (not shown) and a second portion co-located with the second vehicle controller 2304. Each of the first portion or the second portion of the CND 1912 can include one or more of the following: a CES, a CEG, and / or non-transitory computer-readable instructions configured to, when executed by a process of a corresponding vehicle controller (e.g., the vehicle controller and / or the second vehicle controller 2304), perform at least a portion of the operations for regulating communications between the network zones 1904, 1908 (and / or 2322, 2324). Each of the first portion or the second portion of the CND 1912 can be located within a housing of the corresponding vehicle controller and / or on the same board as the corresponding vehicle controller.
[0190] Certain aspects of the present disclosure are described as processes for performing operations related to the present disclosure. The operations may be performed by any controller, circuit, device, component, sensor, actuator, logic circuit, or other aspects as described in the present disclosure, without limitation thereto. The processes are schematically depicted as illustrative examples, and the operations may be omitted, combined, divided, and / or reordered in whole or in part. In some embodiments, one or more operations of a first process may be combined with one or more operations of another process.
[0191] refer to Figure 24 , schematically depicts a schematic flow diagram of a process 2400 for regulating inter-network communications (e.g., between different network zones of a mobile application). The example process 2400 includes regulating inter-network communications between a first network (and / or network zone) and a second network (and / or network zone) of a mobile application (e.g., as referenced throughout this disclosure, including at least reference to Figure 19and related descriptions). The example process 2400 further includes an operation 2404 of determining whether a non-nominal condition exists, wherein the non-nominal condition includes, but is not limited to, a condition of any network, endpoint, controller, and / or control function. In response to operation 2404 determining true, process 2400 includes an operation 2406 of adjusting regulation of inter-network communications. Without limitation to any other aspects of the present disclosure, the operation 2406 of adjusting regulation of inter-network communications includes any one or more of the following: routing communications from a first network to a second network; additionally repeating, shifting, or mirroring communications nominally on the first network to the second network; shifting endpoints from the first network to the second network; suppressing communications on one of the networks; adjusting a data sampling rate and / or a communication rate of communications and / or endpoints on one of the networks; adjusting control operations, at least in part, from a first controller on the mobile application to a second controller on the mobile application; and / or providing the second controller with data that is nominally provided to the first controller and / or alternate data determined in response to the adjusted control operations; and / or providing communications to the controller on the mobile application from an alternate data source.
[0192] refer to Figure 25, schematically depicts a schematic flow diagram of a process 2500 for encapsulating and / or processing communications from a first network for communication to a second network for a mobile application (e.g., communication between endpoints on separate network zones). The example process 2500 includes: an operation 2502 of receiving a first network communication (e.g., communication provided by any endpoint on any network zone of the mobile application); an operation 2504 of processing, removing, or including non-payload frame information of the communication (e.g., metadata, identifiers, timestamps, and / or any other information of the communication that is not payload or essential data for the communication). The example process 2500 further includes: an operation 2506 of processing, removing, or including payload frame information from the communication (e.g., removing the payload, e.g., where the communication is utilized for reasons other than payload, such as in a network monitoring operation; and / or changing the payload units, resolution, bit depth, data type, etc.); and an operation 2508 of encapsulating the communication for communication to the second network for the mobile application. The example process 2500 further includes an operation 2510 of providing the encapsulated communication as a second network communication on a second network of the mobile application. In some embodiments, the process 2500 provides operations for providing messages between endpoints on separate networks with incompatibilities (e.g., network protocols, message characteristics, network addressing, etc.) and / or between endpoints with otherwise incompatible data usage (e.g., payload units, data types, bit depths, etc.). In some embodiments, the operations of the process 2500 allow for encapsulating messages from a first network (e.g., a CAN network) to a second network (e.g., an Ethernet network) and / or tunneling messages from a first network having a first network type to another network having the first network type by traversing an intermediate network having a second network type.
[0193] refer to Figure 26 , schematically depicting an example process 2600 for providing upsampling and / or downsampling communications from an endpoint on a network of a mobile application. Example process 2600 includes an operation 2602 of determining an upsampling and / or downsampling scheme for a communication (e.g., from a first network). Example operation 2602 includes, but is not limited to, any other aspects of the present disclosure: determining an upsampling and / or downsampling scheme in response to a requested data rate for the communication, a data capability rate for the network and / or for a source data point for the communication, a data storage value for a device in the system (e.g., a communication buffer storage and / or a long-term data storage location), and / or a priority for the communication (e.g., relative to competing communications, based on operating conditions for the mobile application, and / or based on relative priorities for a flow, endpoint, vehicle function, etc.).
[0194] The example process 2600 further includes: Operation 2500, preparing a second network communication (e.g., referring to Figure 25 and process 2500), including, for example, processing payload and / or non-payload information of a communication and encapsulating the (processed or unprocessed) payload and / or non-payload information into a communication prepared for a second network.
[0195] The example process 2600 further includes: an operation 2604 of upsampling and / or downsampling the second network communication. Without limitation to the general concept that all operations of the processes described herein may be reordered, divided, omitted, and / or combined, operations 2500 and 2604 of process 2600 may be performed in any order, including iteratively, simultaneously, and / or progressively together, as it should be understood that the upsampling and / or downsampling operation 2604 may make operation 2500 unnecessary for certain communications (e.g., excluded downsampled communications and / or excluded span or non-span communications) and / or operation 2604 may create payload and / or non-payload information for communications that are then prepared in operation 2500 (e.g., added upsampled communications and / or added span or non-span communications). Without limitation to any aspect of the present disclosure, operation 2604 may include information about Figure 17 and 18 and any operations described herein. The example process 2600 further includes an operation 2606 of providing the upsampled and / or downsampled communications to the second network. For clarity of this description, the operations of process 2600 are described in terms of providing communications from an endpoint on a first network to an endpoint on a second network, but it should be understood that process 2600 is applicable to any communications on a mobile application, including published communications for data services (e.g., reference to Figure 27 and related descriptions), communications delivered to external devices, and / or communications within the same network (e.g., from a first endpoint on a first network to a second endpoint on a second network).
[0196] refer to Figure 27 , schematically depicts an example apparatus 2700 for providing a service-oriented architecture for mobile applications with a hybrid network environment. The example apparatus 2700 includes a vehicle data service definition circuit 2702 that interprets a service availability description 2710 including available data values from endpoints 1906, 1910 on networks 1904, 1908 of a vehicle. For example, the vehicle data service definition circuit 2702 may receive communications from endpoints 1906, 1910 that provide indicators that one or more data values are available for communication, and / or from a profile 2718 of data values available for communication (in a Figure 27) read indicator. The service availability description 2704 may include any type of data value available on the vehicle, including sensed values, actuator feedback values (e.g., position, status, fault values, etc.), parameters from any controller in the system, virtual sensor values, control parameters (e.g., set points, reference points, determined state values, reference error values, etc.), and / or stored values (e.g., accumulated parameters, snapshot information, calibration, etc.). The service availability description 2704 may be associated with a single endpoint, a group of endpoints, a stream, or any other data provider or group of data providers in the system. The data associated with the service availability description 2704 may be raw data values and / or processed versions of the data values (e.g., filtered low sample rate, time lagged data, etc.).
[0197] The example apparatus 2700 further includes a vehicle data service management circuit 2706 that publishes a data service availability value 2708 in response to the service availability description 2704. In some embodiments, the data service availability value 2708 may include the same data or a formatted version of the data as provided by the service availability description 2704. In some embodiments, the data service availability value 2708 may include a tailored or adjusted version of the service availability description 2704 (e.g., fewer parameters, a reduced data rate, a reduced resolution, etc. than provided in the service availability description 2704), such as when the device providing the service availability description 2704 does not have full permissions to publish all listed parameters, publish at the planned data rate, and / or publish with the indicated sampling rate (e.g., as determined according to the configuration file 2718). In some embodiments, the vehicle data service management circuitry 2706 determines that the publishing device (and / or endpoint, stream, etc.) does not have permission to provide the service advertised in the service availability description 2704, and accordingly, the vehicle data service management circuitry 2706 does not provide a corresponding data service availability value 2708 for the service availability description 2704. In some embodiments, the vehicle data service management circuitry 2706 determines that certain data service availability values 2708 are restricted to certain subscribing devices and accordingly configures the data service availability values 2708 (e.g., applies tags, encryption schemes, metadata, etc.) so that unauthorized devices cannot see the corresponding data service availability values 2708 and / or cannot subscribe to the corresponding data service availability values 2708. The example vehicle data service management circuitry 2706 generates a data service value description 2709 in response to a subscription request 2710 for the data service availability values 2708 and the data values from the endpoints 1906, 1910. For example, the data service value description 2709 describes parameters to be collected, grouped, and / or processed, and may further include endpoint descriptions, etc. The data service value description 2709 provides collection parameters that may be utilized by the CND 1912 to support services with active valid subscriptions, and further allows for management of collection operations, such as filtering of authorized data access and / or consolidation of redundant parameters (e.g., where more than one service may provide the same data element as part of a service, where multiple data rates for a parameter may be serviced with a single high-rate collection operation, etc.).
[0198] The example device 2700 includes a CND 1912 that performs operations to regulate communications between the networks 1904 and 1908 of the vehicle. In the example device 2700, for clarity of illustration, the circuits 2702 and 2706 are depicted as being located together with the CND 1912, but it should be understood that Figure 27One or more of the components, circuits, communication flows, data elements, and / or other aspects depicted in the example CND 1912 may be distributed across devices in the system. The example CND 1912 includes: a mediation circuit 2710 (e.g., which may include and / or communicate with a network operating component (such as a CES, CEG, or other operating component)), which mediates communication between the first network 1904 and the second network 1908, and which generates a data service value 2712 in response to a data service value description 2709 and a data value from an endpoint, and publishes a data service value 2712 in response to the data service value description 2712.
[0199] The example moderation circuitry 2710 collects data directly from endpoints and publishes the data as broadcast (e.g., visible to all endpoints) and / or multicast (e.g., provided to subscribing endpoints) parameters, e.g., based on permissions, network capacity, parameter importance, and / or usage breadth. In certain embodiments, the example moderation circuitry 2710 provides data service values 2712 to a service agent 2714, which manages communication of the data service values 2712 to subscribing endpoints or devices. Example embodiments having a service agent 2714 additionally or alternatively utilize the service agent 2714 to communicate data service availability values 2708 to endpoints or devices and / or receive subscription requests 2710 from devices. In certain embodiments, the vehicle data service management circuitry 2706 communicates with the service agent 2714 to determine subscription requests 2710. In certain embodiments, the vehicle data service management circuitry 2706 receives subscription requests from endpoint devices on the networks 1904, 1908.
[0200] The example apparatus 2700 includes a vehicle data service management circuit 2706 and / or a service agent 2714 that receives a subscription request 2710 from an external device, such as a service device 2716. In the example, the vehicle data service management circuit 2706 determines a data service value description 2709 in response to the subscription request 2710 from the external device (e.g., including determining permissions, etc.), and the external device receives parameters according to the subscribed service, such as subscribing to an endpoint, device, stream, etc. on the vehicle.
[0201] In some embodiments, the service availability description 2704 further includes an authorization description (e.g., when publishing an endpoint and / or device application permission level for the service availability), and the vehicle data service management circuitry 2706 can further restrict the publication of the data service availability value 2708 and / or restrict the acceptance of the corresponding subscription request 2710 in response to the authorization description. Additionally or alternatively, the vehicle data service management circuitry 2706 can determine the authorization description based on a configuration file 2718. The example vehicle data service management circuitry 2706 restricts the publication of the data service availability value (and / or restricts the acceptance of the corresponding subscription request 2710) in response to one or more of the following: an endpoint identifier of the subscription requester; an application identifier of the subscription requester (e.g., mobility management; entertainment management; climate control; stability control; etc.); a flow identifier of the subscription requester; a user identifier of the subscription requester (e.g., identity of a service technician, a person role associated with the requesting device, an application, a flow, etc.); and / or an entity identifier of the subscription requester (e.g., entity name, entity role, manufacturer, OEM, service entity, owner entity, operator entity, third-party entity, etc.).
[0202] The example vehicle data service definition circuitry 2702 further interprets the service availability value 2720 and updates the service availability description 2704 in response to the service availability value 2720. For example, the service availability value 2720 may provide an indication that the published service is unavailable, such as during certain operating conditions, due to a malfunction or failure of an endpoint or device providing data for the service, due to a change in system permissions (and / or conditional permissions where permission criteria are not currently met), due to a service appearing in the configuration information 2718 but referencing an endpoint, device, application, flow, etc. that is not present on the vehicle, due to expiration of the permission, etc. In a further example, the service availability value 2720 further includes an authorization description, wherein the vehicle data service definition circuitry 2702 restricts updates to the service availability description 2704 in response to the authorization description. The example vehicle data service management circuitry 2702 restricts updates to the service availability description in response to one or more of: an endpoint identifier of the service availability value provider; an application identifier of the service availability value provider; a flow identifier of the service availability value provider; a user identifier of the service availability value provider; and / or an entity identifier of the service availability value provider. The example vehicle data service definition circuitry 2702 receives a service availability value 2704 from a data collection management device external to the vehicle, such as, but not limited to, a service device 2716. Accordingly, the apparatus 2700 enables provision and updating of services by an external device (such as, for example, utilized by an operator, owner, service entity, manufacturing entity, third-party application, fleet owner, etc.), including (depending on permissions) updating configuration information, in-vehicle permissions, etc.
[0203] refer to Figure 28 , schematically depicts an apparatus 2800 for encapsulating network communications to support mobile communications between hybrid networks on mobile applications. The example apparatus 2800 includes: a first network interface circuit 2802 that interprets a first network data set 2804 (e.g., a message from an endpoint on a first network 2805) having a first network format 2806 (e.g., protocol, message parameters, start and / or stop bits or information, payload formatting, message type, message acknowledgment protocol, and / or network layer); and a translation circuit 2808 that determines a message value 2810 from the first network data set 2804 and encodes the message value 2810 in a second network data set 2812 having a second network format 2814. As used herein, a message data set should be broadly construed and may include a single message, a group of related messages, a group of messages present on associated networks over a period of time, an operational status, and the like. As utilized herein, a message value includes any selected aspect of a message, including a payload, a frame, a portion of a frame, metadata, and the like.
[0204] The example apparatus 2800 further includes: a second network interface circuit 2816 that transmits the second network data set 2812 (e.g., as a message to the second network 2817). The apparatus 2800 includes a first network interface circuit 2802, a translation circuit 2808, and a second network interface circuit 2816, defined by a single device or by two devices, wherein the first device and / or both devices are capable of being incorporated into a vehicle. For example, the CND may include all of the first network interface circuit 2802, the translation circuit 2808, and the second network interface circuit 2816. In another example, the CEG may include the first network interface circuit 2802 and the translation circuit 2808, and the CES may include the second network interface circuit 2816. In another example, the CEG may include the first network interface circuit 2802, and the CES may include the translation circuit 2808 and the second network interface circuit 2816. In another example, the CEG may include all of the first network interface circuit 2802, the translation circuit 2808, and the second network interface circuit 2816.
[0205] exist Figure 28 In the example, the first network format 2806 is distinguishable from the second network format 2814 in at least one aspect. The example apparatus 2800 includes one of the first network format 2806 or the second network format 2814 as a CAN network. The example apparatus 280 includes the first network format 2806 as a CAN network and the second network format 2814 as an Ethernet network.
[0206] The example apparatus 2800 further includes: a configuration circuit 2818 that modifies the first network interface circuit 2802, the translation circuit 2808, and / or the second network interface 2816 in response to a configuration command value 2820. Example and non-limiting configuration command values 2820 include one or more of the following: which messages of the first network data set 2804 are to be transmitted to the second network; upsampling and / or downsampling operations to be performed on the messages of the first network data set 2804; translation parameters for determining a message value 2810 (e.g., which aspects of the message (such as payload, frame portion, metadata, etc.) are to be considered as the message value 2810) and / or encoding the message value into the second network data set 2810 (e.g., encapsulation operations, source and / or destination identifiers, unit conversion, etc.); and / or network conditioning operations (e.g., reference to Figure 19 and related descriptions). Example configuration circuitry 2818 is defined by the first device or, optionally and if present, by the second device (such as a CND, CEG, and / or CES). In some embodiments, the configuration circuitry 2818 further selectively configures which of one or more portions of the first network interface circuitry 2802, the translation circuitry 2808, and / or the second network interface circuitry 2816 are defined by the first device and / or the second device (e.g., allowing the configuration circuitry 2818 to adjust operations between devices, slightly modify devices such as a CEG or CES, and / or shift network operations and / or regulation functions in response to system changes, topology changes, and / or non-nominal operating conditions). In some embodiments, the configuration circuitry 2818 receives configuration command values 2820 from the CND, from an external device, and / or by accessing a configuration file.
[0207] refer to Figure 29, schematically depicts an apparatus 2900 for mirroring ports to provide communication from a first network to a second network on a mobile application. The example apparatus 2900 includes a first network interface circuit 2802 having a plurality of ports 2902 for interpreting first communication data 2904 from a first network 2805 on a vehicle. The ports 2902 can be physical ports, logical ports, and / or a combination of physical and logical ports. The example apparatus 2900 includes a second network interface circuit 2816 for interpreting second communication data 2906 from a second network 2817 on a vehicle. The second network 2817 is of a different type than the first network 2805 (e.g., a CAN network versus an Ethernet network, a network having different network formats 2806, 2814, and / or any other type of difference as described herein and / or understood in the art). The apparatus 2900 further includes a translation circuit 2808 that relays the second communication data 2906 (e.g., which may include processing, packaging, and / or otherwise configuring the second communication data 2906 for transmission on the second network 2805) to the first network interface circuit 2802 for transmission on the first network 2805 via at least one of the ports 2902. The example first network interface circuit 2802 mirrors a first port of the ports 2902 to a second port of the ports 2902, e.g., allowing an external device 2908, a data collection operation (not shown), and / or other devices in the vehicle to observe and / or retrieve data from the second port, thereby receiving the same data as transmitted at the first port. Without limiting any other aspect of the present disclosure, the port mirroring operation allows network monitoring operations and data collection of any parameter from any endpoint of the network in the vehicle (e.g., without requiring the requesting device's knowledge of the network configuration, communication protocols, and / or locations of endpoints distributed throughout the vehicle).
[0208] The example apparatus 2900 further includes a configuration circuit 2818 that interprets the port selection command value 2820 and designates which ports 2902 are the first port and the mirror port. Accordingly, the configuration circuit 2818 can provide a communication value from any of the ports 2902 to the selected mirror port, which communication value can include any selected endpoint on the first network 2805 and / or can include all of the second communication data 2906 (e.g., where the translation circuit 2808 relays the second communication data 2906 to a single port in the ports 2902). In some embodiments, the configuration circuit 2818 receives the port selection command value 2820 from a CND, from a configuration file, and / or from a requesting external device 2908 (e.g., a service tool, an OBD device, a vehicle and / or a network monitoring device, etc.), and / or from any controller on the vehicle that has sufficient permission to provide the port selection command value 2820.
[0209] The example configuration circuitry 2818 interprets the port assignment command value 2820, identifies: the assigned port and device (e.g., endpoint, controller, flow, application, etc.) on the second network 2817, the portion of the second communications data 2906 corresponding to the identified device, and transmits (and / or instructs the first network interface circuitry 2802 to perform the transmission) the identified portion of the second communications data 2906 to the assigned port. In certain further embodiments, the device on the second network 2817 may additionally or alternatively include communications data on other networks (e.g., the first network 2805) corresponding to the identified device, such as when the application, flow, or other device on the second network 2817 includes aspects operating on other networks, and the operation of the configuration circuitry 2818 and the first network interface circuitry 2802 further supports providing corresponding communications data from all relevant networks at the assigned port.
[0210] refer to Figure 30 , schematically depicts an apparatus for controlling intra-network traffic on a mobile application. The example apparatus 3000 includes: a first network interface circuit 2802 that interprets first communication data 2904 on a first network 2805 on a vehicle; and a second network interface circuit 2816 that interprets second communication data 2906 on a second network 2817 on the vehicle. The second network 2817 is a different type of network than the first network 2805 (e.g., a CAN network versus an Ethernet network, a network with different network formats 2806, 2814, and / or any other type of difference as described herein and / or understood in the art). The example apparatus 3000 further includes: a translation circuit 2808 that selectively relays the first communication data 2904 to the second network interface circuit 2816 for transmission on the second network 2817, and / or relays the second communication data 2906 to the first network interface circuit 2802 for transmission on the first network 2805. The example translation circuit 2808 further configures messages from each network to the other network, such as processing, encapsulating, and / or otherwise configuring the messages before relaying them. The example apparatus 3000 further includes a conditioning circuit 3002 that regulates the second network interface circuit 2816, the first network interface circuit 2802, and / or the translation circuit 2808, including but not limited to performing any one or more operations, such as regarding Figure 19The example regulation circuit 3002 regulates the amount of first communication data 2904 relayed to the second network interface circuit 2816 and / or the amount of second communication data 2906 relayed to the first network interface circuit 2802. The example regulation circuit 3002 regulates the amount of communication data by limiting the data rate (e.g., the amount of data per unit time and / or the amount of data over a period of time), by limiting the amount of data based on a saturation rate (e.g., utilization of available bandwidth, utilization of a portion of bandwidth granted for related communications, etc.), based on storage capacity, based on the capabilities of a receiving device (an endpoint on one of the networks), and / or based on a requested data rate of the receiving device.
[0211] The example conditioning circuit 3002 conditions the transmission of one or more portions of the first communication data 2904 and / or the second communication data 2906, for example, corresponding to selected endpoints, flows, applications, and / or based on vehicle operating conditions, non-nominal conditions of the network and / or endpoints, and / or the like. In some embodiments, combinations of these conditions may exist—for example, where a specified vehicle operating condition indicates that transmission to or from certain endpoints is to be regulated and / or transmission associated with certain data flows is to be regulated. Conditioning operations include, but are not limited to, any other aspects of the present disclosure, including operations such as limiting communications, limiting the rate of communications, throttling communications (at least for a period of time and / or during certain operating conditions), performing downsampling on certain messages (e.g., reducing the amount of message traffic transmitted), and / or performing upsampling on certain messages (e.g., which can shift operational workload between components, including reducing the workload of some components, such as utilizing upsampling to reduce the actual data sampling rate, performing upsampling to generate configured messages to reduce packaging workload, and / or the like). In certain embodiments, conditioning operations of the regulating circuit 3002 include: considering associated priority information for messages, endpoints, flows, networks, etc.; and / or prioritizing portions of the relayed first communications data 2904 and / or second communications data 2906.
[0212] refer to Figure 31, schematically depicts an apparatus for supporting configurable network status monitoring for mobile applications with hybrid networks. The example apparatus 3100 includes: a first network interface circuit 2802 that interprets first communication data 2904 of a first network 2805 on a vehicle; and a second network interface circuit 2816 that interprets second communication data 2906 of a second network 2817 on a vehicle. The second network 2817 is a different type of network than the first network 2805 (e.g., a CAN network versus an Ethernet network, a network with a different network format 2806, 2814, and / or any other type of difference as described herein and / or understood in the art). The example apparatus 3100 further includes: a network status circuit 3102 that generates network status data 3106 by monitoring portions of the first communication data 2904 and / or the second communication data 2906. In Figure 31 In the example, the network status circuit 3102 is depicted as communicating with the port 2902 of the first network interface circuit 2802 to collect the network status data 3106, but it should be understood that the network status circuit 3102 can be located elsewhere in the system and can collect the network status data 3106 from the conversion circuit 2808, the second network interface circuit 2816, and / or can access the network status data 3106 as stored data on the memory storage of the device 3100.
[0213] The example apparatus 3100 further includes a configuration circuit 2818 that configures at least one of the ports 2902 to monitor at least another of the ports 2902, e.g., to provide network status data 3106 at the selected port 3902 of the first network interface circuit 2802. The example configuration circuit 2818 interprets a port assignment command value 3104 and transmits (and / or instructs the first network interface circuit 2802) to transmit an identified portion of the communication to the selected port, the port assignment command value 3104 identifying the selected port (e.g., to provide network status data 3106) and further identifying a portion of the first communication data 2904 and / or the second communication data 2906 (e.g., based on a monitored device, network, endpoint, flow, etc.). The example apparatus 3100 includes a configuration circuit 2818 that modifies the network status data 3106, e.g., in response to a selected device, endpoint, flow, application, controller, network, system of a vehicle, etc. The example apparatus 3100 includes configuration circuitry 2818 that modifies network status data 3106 in response to a data selection command value 3108 (e.g., provided by the network status circuitry 3102, a CND, an external device, a configuration file, and / or other controller or component of the system) and adjusts data provided to a selected port (or otherwise provided to the network status circuitry 3102) in response to the data selection command value 3108. In some embodiments, the data selection command value 3108 additionally or alternatively identifies one or more protocols (e.g., a data collection rate, a time value and / or range, a selected process, a selected portion of a message frame, metadata, a protocol type such as TCP, UDP, AVB, etc.). In a non-limiting example, the example apparatus 3100 depicts the circuitry 2802, 2808, 2816, 2818 located within the same housing 3110 and the network status circuitry 3102 separate from the housing 3110 (e.g., as an external device). The example apparatus 3100 may include circuits 2802 , 2808 , 2816 , 2818 and / or subsets of the circuits 2802 , 2808 , 2816 , 2818 located on the same circuit board.
[0214] Further references Figure 31, example first network 2805 is an Ethernet network, and example second network 2817 is a CAN network. In an example, translation circuitry 2808 is interposed between first and second network interface circuitry 2802, 2816 and translates Ethernet communication data into CAN communication data and / or translates CAN communication data into Ethernet communication data. Network status circuitry 3102 generates network status data 3106 by monitoring Ethernet communication data 2904 and / or CAN communication data 2906. In certain embodiments, network status data 3106 is based at least in part on one or more of the following: bandwidth across translation circuitry 2808; multiple messages in the Ethernet and / or CAN communication data having addresses corresponding to the same device, the same application, and / or the same flow; and / or multiple communication errors (e.g., dropped packets, delay events, incorrect checksums, invalid data, failed handshakes or acknowledgments, etc.).
[0215] refer to Figures 32-34 , depicts an example arrangement of apparatus for mediating communications between networks on a mobile application with a hybrid network for illustration purposes.
[0216] refer to Figure 32 , an example arrangement includes a CEG 3206 (e.g., a configurable edge gateway and / or a CAN gateway) having: a first network interface circuit 2802 in communication with a CAN network 3202; and a translation circuit 2808 that passes selected messages between the CAN network 3202 and a port of a second network interface circuit 2816. An example device includes a CES 3208 that includes a second network interface circuit 2816 in communication with an Ethernet network 3204, and includes a configuration circuit 2818 that performs operations to regulate communications between the networks 3202, 3204. Figure 32 The arrangement may form all or part of a CND as set forth throughout this disclosure, and / or may perform operations to regulate communications between networks 3202, 3204 in response to CND commands, where the CND is distributed elsewhere in the system.
[0217] refer to Figure 33 , depicts an example arrangement that may form all or part of a CND as set forth throughout this disclosure, and / or may perform operations to regulate communications between networks 3202, 3204 in response to CND commands, where the CND is distributed elsewhere in the system. Figure 33 The example is different from Figure 32 , where the conversion circuit 2808 is located together with the CES 3208 and receives CAN messages directly from the first network interface circuit 2802.
[0218] refer to Figure 34, depicts an example arrangement that may form all or part of a CND as set forth throughout this disclosure, and / or may perform operations to regulate communications between networks 3202, 3204 in response to CND commands, where the CND is distributed elsewhere in the system. Figure 34 The example is different from Figure 33 , where the configuration circuit 2818 is distributed between the CES 3208 and the CEG 3206. Figure 34 In the example of FIG, one of the configuration circuits 2818 may be primary, passing configuration information to another of the configuration circuits 2818. In some embodiments, each configuration circuit 2818 may operate independently, such as receiving configuration information from a configuration file, through communication with a CND, and so on. Figures 32-34 The examples are non-limiting illustrations to illustrate certain aspects and arrangements of the present disclosure.
[0219] refer to Figure 35 , schematically depicts an example process 3500 for providing a service-oriented architecture for a vehicle with a hybrid network. The example process 3500 includes: an operation 3502 of interpreting a service availability description, the service availability description including available data values from a first endpoint device on one of a first network or a second network of the vehicle; an operation 3504 of publishing a data service availability value in response to the service availability description; an operation 3506 of generating a data service value description in response to a subscription request for the data service availability value; an operation 3508 of generating a data service value in response to the data service value description and the data value from the first endpoint device; and an operation 3510 of publishing the data service value in response to the data service value description. The example operation 3510 of publishing the data service value includes providing the data service value to a second endpoint device, such as an endpoint device on another network from the first endpoint device. The example operation 3510 further includes publishing the data service value by providing a network communication to a subscribing endpoint device, each of the subscribing endpoint devices being on one of the first network or the second network, and wherein the network communication includes the generated data service value. An example data service availability value includes the name of the service, a list of data parameters provided by the service, a list of available commands provided by the service, etc. (e.g., from a providing device to a CND), and a data service value description includes the name of the service, a list of data parameters provided by the service, a list of available commands provided by the service, etc. (e.g., from a CND to a potential subscribing device), wherein the data service value description may match the data service availability value or may be configured differently from the data service availability value (e.g., simplified, enhanced, standardized, etc.). An independent data service value includes a data value corresponding to the data service availability value.
[0220] In certain embodiments, process 3500 further includes operation 3512 of receiving a subscription request from an endpoint device on both the first network and the second network. Example operation 3512 includes receiving a subscription request from a device external to the vehicle (such as a service device, a web application, a cloud-based application, and / or a third-party application), wherein operations 3508 and / or 3510 are performed in response to operation 3512 (e.g., generating a data service value and / or publishing the data service value only if the subscribing device is available for the service). Example process 3500 includes the service availability description further including an authorization description, wherein operation 3504 includes limiting the publication of the data service availability value in response to the authorization description (e.g., wherein unauthorized devices cannot see the data service). Example operation 3504 includes limiting the publication of the data service availability value in response to an identifier of a subscription requestor (e.g., an endpoint, a flow, a vehicle function, an application, a service group, and / or an entity associated with any of these).
[0221] Example process 3500 includes: the service availability description further including an authorization description, wherein operation 3510 includes restricting the publication of the data service value in response to the authorization description (e.g., not allowing subscriptions to the published service). Example operation 3510 includes restricting the publication of the data service value in response to an identifier of a subscription requester (e.g., an endpoint, a flow, a vehicle function, an application, a service group, and / or an entity associated with any of these).
[0222] Example operations 3502 include interpreting a service availability value and updating a service availability description in response to the service availability value. For example, the service availability value may be updated by a providing device (e.g., an endpoint, a flow, a vehicle function, an application, a service group, an external device, etc.) and / or may be updated by a change in a policy for adding services to and / or removing services from available services. Example operations 3502 further include limiting updates to the service availability description in response to an authorization description (e.g., verifying authorization of an updating device before updating the service availability description) and / or in response to an identifier of the updating device.
[0223] refer to Figure 36, schematically depicts an example process 3600 for providing messages between networks for vehicles having hybrid networks. The example process 3600 includes: operation 3602, interpreting a first network data set having a first network format; operation 3604, determining a message value from the first network data set in response to operation 3602; operation 3606, encoding the message value in a second network data set having a second network format; and operation 3608, transmitting the second network data set (e.g., onto a second network). The example process 3600 includes: the network having a vehicle data format, wherein the vehicle data format is a different format (e.g., CAN, MOST, LIN, FlexRay, TTP, LVDS, AVB, and / or an electrical signal format). The example first network format is a CAN-based format, and the example second network format is an Ethernet-based format. The example process 3600 further includes: operation 3610, interpreting a configuration command value from a device external to a vehicle (e.g., via a policy update provided by the external device), the vehicle comprising: a first network interface circuit that interprets a first network data set; a conversion circuit that determines a message value from the first network data set and encodes the message value in a second data set; and a second network interface circuit that transmits the second network data set; and operation 3612, configuring the first network interface circuit, the second network interface circuit, and / or the conversion circuit based at least in part on the configuration command value, for example, so that operations 3602, 3604, 3606, 3608 are performed according to the configuration command value.
[0224] Example operations 3606 include encapsulating a message value (e.g., a payload), encapsulating an entire message (e.g., a portion or all of a frame of a message), processing a message value, and / or processing a portion or all of a frame of a message. Example operations 3606 include one or more of configuring an encapsulation scheme for the message, configuring an address description for the message (e.g., translating an address based on a target device to receive data on a separate network), and / or configuring a sampling rate (e.g., performing upsampling and / or downsampling operations on a first network data set).
[0225] refer to Figure 37, schematically depicts an example process 3700 for configuring a CND for monitoring a network of a vehicle having a hybrid network. The example process 3700 includes: operation 3702, interpreting first communication data of a first network on the vehicle; operation 3704, interpreting second communication data of a second network on the vehicle, the second network being of a different type than the first network; operation 3706, generating network status data by monitoring the first and second communication data; and operation 3708, transmitting the network status data (e.g., storing the data, transmitting the data to an external device, a service tool, a cloud server, etc.). The example process 3700 further includes: operation 3710, configuring a first port (e.g., a port on the network of the vehicle) to mirror a second port (e.g., another port on the network of the vehicle), wherein the first port provides the first communication data, for example, to provide the first communication data as an available message on the second network and / or to provide the second port as a monitoring port for the first communication data. Example operation 3710 includes interpreting a port assignment value identifying a selected port (e.g., from a policy, a configuration file, determined based on the requested data and providing an endpoint for the requested data, and / or determined based on a port corresponding to a service tool, monitoring device, etc.), wherein operation 3704 includes identifying a portion of the second communication data corresponding to the identified device (e.g., an endpoint, port, flow to be monitored, etc.), and operation 3708 includes transmitting the identified portion of the second communication data via the selected port.
[0226] Example operation 3706 further includes modifying the network status data. Example operations for modifying the network status data include: modifying the network status data in response to a selection command value; and including data corresponding to at least one device, application, vehicle function, flow, service group, network, protocol, and / or system identified by the data selection command value in the network status data. Example and non-limiting protocols include a CAN network and / or an OBD protocol.
[0227] refer to Figure 38, schematically depicts an example process 3800 for mirroring ports using a CND for a vehicle with a hybrid network. Example process 3800 includes: operation 3802, interpreting first communication data of a first network at a plurality of ports of the CND; operation 3804, interpreting second communication data of a second network (of a different type); operation 3806, relaying the second communication data to the first network using at least one of the plurality of ports (e.g., from a CEG to a CES); and operation 3808, mirroring a first one of the ports to a second one of the ports. Example process 3800 further includes: operation 3810, interpreting a port selection command value (e.g., a receiving port and / or a transmitting port for mirroring the communication data); and operation 3812, assigning the first one and / or the second one of the ports in response to the port selection command value. Example operation 3810 includes: a port assignment command value that identifies the assigned port, identifies a device on the second network, and wherein operation 3806 and / or operation 3808 includes transmitting the identified portion of the second communication data via the assigned port (e.g., to the second network and / or to the mirror port).
[0228] refer to Figure 39 , schematically depicts an example process 3900 for configuring a CND for a vehicle with a hybrid network. Example process 3900 includes: operation 3902, interpreting a first network data set having a first network format via first interface circuitry of a converged network device (CND); operation 3904, determining a message value from the first network data set in response to interpreting the first network data set via translation circuitry of the CND; operation 3906, encoding the message value in a second network data set having a second network format different from the first network format via the translation circuitry; and operation 3908, transmitting the second network data set via second interface circuitry of the CND. Example process 3900 further includes: operation 3910, interpreting a configuration command value; and operation 3912, modifying the CND in response to the configuration command value.
[0229] Example operations 3912 include interpreting a configuration command value and modifying a CND in response to the configuration command value. Example operations for modifying the CND include selectively configuring which of one or more portions of the first interface circuit, the translation circuit, and / or the second interface circuit are at least partially defined by the first device and / or the second device (e.g., transferring translation and / or interface responsibilities between different network interface circuits and / or between CEGs and / or CESs). Example operations 3912 include generating a configuration command value external to the vehicle (e.g., from an external device and / or via a policy update) and transmitting the configuration command value to the vehicle (and / or to the CND).
[0230] refer to Figure 40, schematically depicts an example process 4000 for performing test operations, diagnostic operations, and / or vehicle control operations, including operations for configuring a CND to perform these operations. Example process 4000 may be performed in addition to the operations of process 3900 and / or performed separately in whole or in part. Example process 4000 includes: operation 4002, generating a test command value external to the vehicle; operation 4004, transmitting the test command value to the CND; and operation 4006, performing a test process involving a device (e.g., one of the first or second devices of process 3900 and / or a third device on the first or second network). Example process 4000 may be performed in addition or alternatively using diagnostic command values, activity assistance command values, and / or vehicle control values (e.g., commanding actuators, vehicle functions, etc.). In certain embodiments, process 4000 allows remote configuration and / or operation of testing, diagnosis, vehicle control functions, etc. of the CND without requiring knowledge from the external device regarding the network topology, endpoint locations, and / or endpoint local addresses of the devices on the vehicle.
[0231] refer to Figure 41 , schematically depicts an example process 4100 for regulating a network of a vehicle having a hybrid network. Example process 4100 includes: operation 4102, interpreting first communication data of a first network of the vehicle; operation 4104, interpreting second communication data of a second network of the vehicle; operation 4106, relaying the first communication data to the second network (and / or vice versa); and operation 4108, regulating the second network. Example operation 4108 includes restricting relaying of the first communication data (e.g., limiting the rate, disabling and / or pausing communication, restricting devices that can send and / or receive relayed data, etc.). Example operation 4108 is performed in response to the amount of data per unit time, per operational event (e.g., per trip, during certain operational conditions, etc.), based on saturation rates of the first network and / or the second network, and / or based on the maximum bandwidth of the first network and / or the second network (e.g., maintaining to a total bandwidth limit, limiting relayed communication to a selected fraction of the available bandwidth, etc.). Example operation 4108 includes prioritizing portions of the first communication data and / or the second communication data for relaying according to any prioritization operations and / or groupings set forth throughout this disclosure (e.g., endpoint, flow, application, vehicle function, service group, etc.) Example operation 4108 includes upsampling, downsampling, encapsulating, and / or processing the relayed message and / or portions thereof (e.g., payload, selected message, frame portion, metadata, etc.).
[0232] refer to Figure 42, schematically depicts an example process 4200 for regulating inter-network communications of a vehicle with a hybrid network. Example process 4200 includes: operation 4202, interpreting first communications data of a first network on the vehicle; operation 4204, interpreting second communications data of a second network on the vehicle; operation 4206, relaying the first communications data to the second network (and / or vice versa); and operation 4208, regulating the relaying of the first communications data and / or the second communications data. Operation 4208 includes any of the regulation operations described throughout this disclosure and may be performed in response to the first network, the second network, relaying devices (e.g., CEGs, CESs, and / or network interface circuitry), memory storage (e.g., buffer memory and / or short-term memory storage for network communications), including characteristics of these, operating conditions of these and / or the vehicle, and / or non-nominal conditions present for any of these and / or the vehicle.
[0233] refer to Figure 43, schematically depicts an example process 4300 for supporting CAN status determination using Ethernet-based monitoring. Example process 4300 includes: operation 4302, interpreting an Ethernet-based data set via one or more physical ports of a first interface circuit of an Ethernet switch provided on a vehicle (e.g., forming a CES); operation 4304, determining a message value from the Ethernet data set using translation circuitry (e.g., on the Ethernet switch and / or on a CAN gateway and / or CEG); and operation 4306, encoding the message from the Ethernet-based data set into a message for a CAN-based data set. Operations 4304 and 4306 are described as going from the Ethernet-based data set to the CAN-based data set, but the operations may additionally or alternatively go from the CAN-based data set to the Ethernet-based data set. Example process 4300 further includes: operation 4308, transmitting the CAN data set using a second interface circuit (e.g., thereby sending an Ethernet message to a CAN-based device and / or sending a CAN message to an Ethernet device). Example process 4300 further includes: operation 4310, interpreting a configuration command value; and operation 4312, modifying the translation circuitry in response to the configuration command value (e.g., changing message handling, addressing, encapsulation characteristics, upsampling values, downsampling values, maximum data rate, etc.). Example operation 4310 includes receiving the configuration command value from an external device (e.g., as a request, message, policy update, etc.). Example operation 4312 includes providing the configuration command value to an Ethernet switch, CEG, configurable CAN gateway, etc. Example process 4300 can be utilized to perform testing, activity diagnostics, activity assistance, and / or vehicle control, wherein devices across a hybrid network are utilized to perform operations. Example operations can utilize any endpoint, vehicle function, application, flow, service group, etc. of a vehicle. Example operations can utilize systems and / or system-related components, such as a vehicle's prime mover, a vehicle's engine, a vehicle's driveline, a vehicle's transmission, a vehicle's braking system, a vehicle's fuel system, and / or a vehicle's electrical system.
[0234] refer to Figure 44 , schematically depicts an example process 4400 for providing Ethernet monitoring on a vehicle with a hybrid network. Example process 4400 includes: an operation 4402, converting Ethernet communication data into CAN communication data; an operation 4404, converting the CAN communication data into Ethernet communication data; and an operation 4406, generating network status data by monitoring the converted CAN and Ethernet communication data. Process 4400 further includes: an operation 4408, transmitting the network status data—for example, by storing the data, transmitting the data to an external device, and / or transmitting the data to a service tool, a web application, a cloud server, a third-party application, etc.
[0235] Example process 4400 further includes: operation 4410, configuring a first Ethernet port to interpret the first Ethernet data; and operation 4412, mirroring communications of the first Ethernet port to a second Ethernet port. In some embodiments, the first Ethernet port may be a port by which CAN communication data (e.g., from operation 4404) is provided to the Ethernet network. In some embodiments, operation 4408 of transmitting network status data includes: operation 4412, mirroring communications of the first Ethernet port to the second Ethernet port. Additionally or alternatively, operation 4406 of generating network status data is performed on at least a portion of the data provided at operation 4412, and operation 4406 of generating network status data may be performed onboard the vehicle, offboard the vehicle, and / or a combination thereof.
[0236] refer to Figure 45, schematically depicts an example process 4500 for operating a hybrid network system on a vehicle. Example process 4500 includes: operation 4502, generating a message value via a first vehicle control device on a first network provided on the vehicle; operation 4504, transmitting the message value to a second vehicle control device on a second network provided on the vehicle; and operation 4506, performing a control operation on the vehicle (e.g., moving a sensor and / or actuator, performing a vehicle function, and / or collecting specified data) in response to receiving the message value at the second vehicle control device. Example and non-limiting vehicle control devices include any sensor, actuator, and / or controller on the vehicle. Example and non-limiting vehicle control devices include systems and / or system-related components, such as a prime mover of a vehicle, an engine of a vehicle, a drive line of a vehicle, a transmission of a vehicle, a braking system of a vehicle, a fuel system of a vehicle, and / or an electrical system of a vehicle. In some embodiments, the first vehicle control device and / or the second vehicle control device may be able to perform one or more operations of the other of the vehicle control devices in whole or in part. In some embodiments, operation 4502 includes generating a message for commanding one of the vehicle control devices to take over one or more operations of the other of the vehicle control devices in whole or in part. In some embodiments, the vehicle control devices are located on different types of networks. In some embodiments, process 4500 includes operation 4508 of providing data previously transmitted to one of the vehicle control devices to the other of the vehicle control devices. Operation 4508 may be performed in addition to previous communication (e.g., both vehicle control devices receive data) and / or as a replacement for previous communication (e.g., in response to failure of previous communication and / or stopping previous communication when operation 4508 is initiated). In some embodiments, operation 4508 includes providing alternate data (e.g., data for a different executable operation of a replacement control device, however, the replacement control device is a full or partial replacement for the original control device), data from a different source (e.g., from a different endpoint than the source of the previous communication), and / or differently processed data from the previous communication (e.g., with a different resolution, communication rate, units, etc.). In some embodiments, operation 4508, including vehicle controller replacement and / or communication change, is performed in response to a request from the control device (e.g., a separate data request sent from the control device in response to the operational change) and / or according to a profile and / or policy.
[0237] Example process 4500 includes: operation 4504, transmitting a message value over one or more intermediate networks (e.g., from a CAN network on a first network zone to a CAN network on a third network zone, tunneled through an Ethernet network on a second network zone). In some embodiments, the intermediate network may be a different type of network relative to the first network and / or the second network. Example and non-limiting operation 4506 includes one or more of the following: acquiring data from a component of a vehicle; actuating a component of the vehicle; and / or controlling another vehicle control device. Example operation 4506 may utilize any endpoint, vehicle function, application, flow, service group, etc. of the vehicle. Example operation 4506 may utilize a system and / or system-related components, such as a vehicle's prime mover, a vehicle's engine, a vehicle's driveline, a vehicle's transmission, a vehicle's braking system, a vehicle's fuel system, and / or a vehicle's electrical system. Example operation 4506 may utilize a system and / or system-related components, such as a vehicle's infotainment system, a vehicle's environmental system, a vehicle's safety system, and / or a vehicle's security system.
[0238] refer to Figure 46 , schematically depicts an example process 4600 for operating a hybrid network system on a vehicle. Example process 4600 includes: operation 4602, generating a message value via a first vehicle control device on a first network of the vehicle; operation 4604, transmitting the message value (and / or a processed and / or encapsulated version of the message value) to an external device at least selectively communicatively coupled to the vehicle via a second network; and operation 4606, interpreting the message value via the external device. Example process 4600 includes: operation 4608, testing the first vehicle control device via the external device, and / or configuring the first vehicle control device via the external device (e.g., providing a direct command or request, updating a policy, and / or updating a configuration file). Example process 4600 includes: operation 4609, configuring a second vehicle control device on the second network via the external device, which may be responsive to operations 4604, 4606, and / or 4608.
[0239] Example operation 4604 includes converting a message value (e.g., using CND, CEG, CES, and / or network interface circuitry) from a first format (e.g., for a first network) to a second format (e.g., for a second network). Example operation 4608 includes configuring CND (and / or CEG, CES, and / or network interface circuitry) via an external device. Example process 4600 may additionally or alternatively include transmitting one or more message values (e.g., with reference to a CND) over an intermediate network between the first and second networks. Figure 4 、 23 , 45 and related descriptions).
[0240] Example process 4600 includes: operation 4610, generating an external message value via an external device; and operation 4612, transmitting the external message value to a first network. Operation 4612 may further include: interpreting the external message via a vehicle control device (e.g., which may be a first vehicle control device and / or another vehicle control device, such as to determine the external message content and thereby perform a control operation, a data collection operation, an active diagnostic operation, an active auxiliary operation, a test operation, an update operation for a configuration file and / or policy, etc.). Example operation 4612 may utilize any endpoint, vehicle function, vehicle controller, application, flow, service group, etc. of a vehicle. Example operation 4612 may utilize a system and / or system-related components, such as a prime mover of a vehicle, an engine of a vehicle, a drive line of a vehicle, a transmission of a vehicle, a braking system of a vehicle, a fuel system of a vehicle, and / or an electrical system of a vehicle. Example operation 4612 may utilize systems and / or system-related components, such as a vehicle's infotainment system, a vehicle's environmental system, a vehicle's safety system, and / or a vehicle's security system.
[0241] refer to Figure 47 , provides an example system 4700 for providing off-vehicle communication control consistent with embodiments of the present disclosure. The example system includes a vehicle 102 having a first network zone 5612 and a second network zone 5614, where the second network zone 5614 is of a different type than the first network zone 5612. The example system 4700 includes a CND 108 between the first network zone 5612 and the second network zone 5614. CND 108 between the network zones 5612, 5614 includes physical intervention (e.g., communication between the network zones 5612, 5614 passes through CND 108 and / or passes through equipment controlled by CND 108, such as CEG, CES or other network interface circuits) and / or logical intervention (e.g., where communication between the network zones 5612, 5614 passes through equipment controlled by CND 108, and / or where CND 108 regulates communication between the network zones 5612, 5614, such as passed data values, configuration of data values, data rates, upsampling and / or downsampling of data, encapsulation operations, frame inclusion and / or processing of passed communications, etc.).
[0242] Example system 4700 further includes: policy manager circuitry 5602 that interprets policy 5606 including active diagnostic description 4705; and diagnostic execution circuitry 4702 that provides diagnostic command values 4712 to endpoints in network zones 5612, 5614 in response to active diagnostic description 4705. Example system 4700 includes endpoints in first network zone 5612 (endpoint 4708) and second network zone 5614 (endpoint 4710). In example system 4700, endpoints 4708, 4710 comprise devices responsive to diagnostic command values 4712. Example and non-limiting diagnostic command values 4712 include commands to collect one or more data values; commands to operate actuators; and / or commands to operate vehicle functions (e.g., to provide engine speed, power level, or higher-level functions such as executing a regeneration mode, a scheduled test operation, etc.). The example system 4700 allows the execution of active diagnostic tests requested by an external device to be successfully performed regardless of the distribution of endpoints 4708, 4710 throughout the vehicle's network, including where endpoints have moved between networks and / or where a given diagnostic command value 4712 is utilized to provide active diagnostic tests across a range of vehicles having varying network configurations and distributions of endpoints 4708, 4710.
[0243] refer to Figure 48 Example endpoint 4708 includes device control circuitry 4802 that interprets a diagnostic command value 4712 and provides an actuator command value 4804 in response to the diagnostic command value 4712. Example endpoint 4708 includes or is associated with an actuator 4806 that responds to the actuator command value 4804. For example, diagnostic command value 4712 may include commands such as "lock driver's door," "close exhaust gas recirculation valve," "raise motor temperature to 80°C," etc., thereby allowing for abstraction between diagnostic command value 4712 and actuator 4806 responses to implement diagnostic command value 4712. Additionally or alternatively, diagnostic command value 4712 may be associated with a complex operation or series of operations, such as a complete test sequence, and accordingly, numerous endpoints 4708, 4710, and / or actuators 4806 throughout system 4700 may be involved by a single diagnostic command value 4712.
[0244] The example system 4700 further includes a diagnostic execution circuit 4702 that determines whether a vehicle operating condition 4720 is consistent with a diagnostic command value 4712 before providing the diagnostic command value 4712 to the endpoints 4708 and 4710. For example, the diagnostic command value 4712 may include a diagnostic test that adjusts the torque delivery of the vehicle's prime mover, and the associated vehicle operating condition 4720 may include parameters such as: ensuring the vehicle is immobile; ensuring the vehicle is not in a motorized power mode; and / or ensuring the vehicle is in a selected test mode. In some embodiments, the vehicle operating condition 4720 for a given diagnostic command value 4712 may be described in the active diagnostic description 4705, thereby allowing active control of the vehicle operating condition 4720 for test performance (e.g., target temperature; diagnosing specific conditions such as vehicle launch, high altitude operation, etc.) and / or additional test considerations (e.g., operator or service personnel safety, fuel economy or emissions, impact on network communication rates, processing requirements and / or memory storage, etc.). In certain embodiments, the vehicle operating condition 4720 for a given diagnostic command value 4712 may be mandated by another flow, application, vehicle function, etc. associated with the vehicle (e.g., torque command cannot be adjusted separately from an operator command unless a specified vehicle condition 4720 exists, etc.). Example system 4700 includes strategy 5606 including diagnostic execution condition 4706, wherein diagnostic execution circuitry 4702 further determines whether vehicle operating condition 4720 is consistent with diagnostic command value 4712 in response to diagnostic execution condition 4706.
[0245] Example system 4700 includes diagnostic execution circuitry 4702 that further executes diagnostic data collection operations in response to active diagnostic descriptions 4705 and stores diagnostic data sets 4714 in response to the diagnostic data collection operations. For example, active diagnostic descriptions 4705 may include a plurality of data parameters to be collected, vehicle status conditions to be monitored, and / or parameter thresholds to be determined (e.g., temperatures above a threshold). Stored diagnostic data sets 4714 may include the collected data, vehicle status conditions determined based on the collected data, parameter threshold confirmation values determined based on the collected data, or a combination thereof. The collected data may be from endpoints 4708, 4710 that are responsive to diagnostic command values 4712 (e.g., confirmation that an actuator has responded to a command, diagnostic data, or fault code associated with a responsive actuator) or from endpoints 4708, 4710 other than those that are responsive to commands (e.g., observations of temperature, pressure, speed values, status confirmations, etc. not directly associated with actuating endpoints 4708, 4710).
[0246] The example diagnostic execution circuit 4702 performs processing operations on the data collected in the diagnostic data collection operation and stores a diagnostic data set 4714 in response to the processing operations. For example, the stored diagnostic data set 4714 may include state information, virtual sensor information, negative information (e.g., only storing data associated with operations in which a threshold is not met), upsampling and / or downsampling values for the collected data, and / or any other processing operations set forth throughout this disclosure. Example and non-limiting processing operations, or portions thereof, for the collected data include: compressing the collected data; summarizing the collected data; operating a virtual sensor using the collected data; determining a vehicle operating condition parameter in response to the collected data; determining a diagnostic data set in response to the determined vehicle operating parameter; performing an upsampling operation on the collected data; and / or performing a downsampling operation on the collected data.
[0247] The example diagnostic execution circuitry 4702 further transmits a diagnostic data set 4714 to an external device (e.g., 5618) in response to the diagnostic data collection operation. The external device receiving the diagnostic data set 4714 may be the same or a different external device than the external device that supplied the active diagnostic description 4705. The example diagnostic execution circuitry 4702 further processes the collected data before transmitting it to the external device, which may include determining initial processing of the stored diagnostic data set 4714 and / or further processing operations on the stored diagnostic data set 4714 before transmitting it to the external device. For example, the diagnostic execution circuitry 4702 may store the diagnostic data set 4714 and transmit portions of the diagnostic data set 4714 (e.g., selected parameters, active diagnostic results, etc.) to the external device. The example diagnostic execution circuit 4702 then performs selected operations, such as: further processing the diagnostic dataset 4714 before transmitting it to the external device (e.g., to reduce external data communications in response to selected data for transmission to the external device, etc.); transmitting the diagnostic dataset 4714 to the external device (e.g., in response to the availability of external communications such as a WiFi connection, a connected external device, etc.; and / or in response to a request from the external device for all of the diagnostic dataset 4714); transmitting selected additional portions of the diagnostic dataset 4714 (e.g., data requested by the external device); maintaining the diagnostic dataset 4714 and / or a further processed form of the diagnostic dataset 4714 stored for a selected time period; and / or deleting the diagnostic dataset 4714 after the diagnostic execution operation (e.g., based on the results of an active diagnostic test and / or based on a request from an external device). As can be seen, the operation of system 4700 allows active diagnostic operations to be performed by an external device (e.g., a service tool, a service application, a cloud-based application, a team service computing device, and / or a third-party application) that engages endpoints on a vehicle across a hybrid network, thereby allowing diagnostic operations that do not require knowledge of the location and / or organization of the endpoints on the vehicle, which knowledge can support multiple configurations of the vehicle and / or can support changing configurations of the vehicle. Additionally or alternatively, the operation of system 4700 allows for scheduled data transmission including a reduction in data transmitted when implementing robust active diagnostic capabilities and scheduled consumption of processing, memory, and inter-network communication resources on the vehicle when implementing robust active diagnostic capabilities.
[0248] The example system 4700 includes a diagnostic verification circuit 4704 that determines a diagnostic confirmation value 4716 based on an actuator's response to a diagnostic command value 4712 (e.g., to confirm whether the actuator performed the commanded function and / or to confirm across a group of actuators whether the vehicle has performed an active diagnostic according to an active diagnostic description 4705). The example diagnostic verification circuit 4704 stores the diagnostic confirmation value 4716 (e.g., as part of a diagnostic data set 4714) and / or transmits the diagnostic confirmation value 4716 to an external device. In certain embodiments, the diagnostic verification circuit 4704 adjusts the storage and / or communication of the diagnostic data set 4714 in response to the diagnostic confirmation value 4716—e.g., to ensure that the diagnostic data set 4714 is relevant to the performance of the active diagnostic. In some embodiments, the diagnostic execution circuitry 4702 may store all or a portion of the diagnostic data set 4714 as a rolling buffer of data, thereby saving selected portions of the diagnostic data set 4714 in response to the diagnostic verification circuitry 4704 providing a diagnostic confirmation value 4716 (e.g., where a diagnostic has a timing value or actuator position as part of the diagnostic execution, thereby allowing the diagnostic to be determined to be complete when a timer or other accumulated condition is completed).
[0249] The example active diagnostic description 4705 includes a target device description 4718 (e.g., a fuel actuator, an engine controller, a door actuator, a mirror position adjustment actuator, etc.) that does not identify on which network zone 5612, 5614 the endpoint corresponding to the target device description 4718 is located. The example system includes configuration circuitry 5604 that determines a network address value 4722 for the endpoint in response to the target device description 4718 (e.g., a port number for an Ethernet network, a message ID for a CAN network, etc.), and diagnostic execution circuitry 4702 further provides a diagnostic command value 4712 to the endpoint in response to the network address value 4722. For example, the target device description 4718 may include a standardized description for the endpoint (e.g., engine speed, ambient temperature, passenger seat occupancy sensor, etc.), and the configuration circuitry 5604 may access a configuration table that associates the standardized description with a local network address for the intended component. Additionally or alternatively, target device description 4718 may have a description that matches a baseline product (e.g., a 2020LX version of a given vehicle), a description that matches an original version of the vehicle (e.g., when the vehicle was configured after manufacture), and / or a description that matches an earlier version of the vehicle (e.g., when the vehicle was configured as of a certain date). In some embodiments, the configuration table or other information utilized by configuration circuitry 5604 to determine network address value 4722 may be one or more configuration files maintained by network interface circuitry, a configuration file maintained by policy manager circuitry, a configuration file maintained by CND, and / or a configuration file maintained as part of policy 5606.
[0250] The example active diagnostic description 4705 includes a target device description 4718 (e.g., a fuel actuator, an engine controller, a door actuator, a mirror position adjustment actuator, etc.) that identifies an endpoint as being on one network zone (e.g., the first network zone 5612), and the configuration circuitry 5604 determines, in response to the target device description 4718, that the endpoint is on another network zone (e.g., the second network zone 5614). For example, the configuration circuitry 5604 may determine that the target device description 4718 is pointing to an incorrect device or a non-existent device, and / or may further determine that the external device is utilizing a previous, different, and / or standardized configuration file to provide the target device description 4718, wherein the configuration circuitry 5604 utilizes the local configuration file to determine an appropriate network address value and / or network zone for the endpoint intended by the target device description 4718. In some embodiments, the configuration circuitry 5604 utilizes other information from the target device description 4718 (such as parameter names, intended functionality, etc.) to determine an appropriate network address value and / or network zone for the endpoint. Similarly, the configuration circuitry 5604 may correct a target device description 4718 that indicates an incorrect address other than the erroneous network region, such as an address on the first network region, where the correct address is another address on the first network region.
[0251] Operation of the configuration circuitry 5604 allows for: simplification of active diagnostic definitions (e.g., external devices do not require system-specific information regarding endpoint location and network distribution); adaptation of diagnostic execution as a vehicle's endpoints and / or local communication devices are moved and / or upgraded; and / or allowing a layer of abstraction between the external device and the vehicle's configuration. The simplification and / or abstraction of active diagnostic definitions from the vehicle's network configuration allows for reduced cost of active diagnostic development and rollout and an increased user base for active diagnostic development (e.g., utilizing enhanced protection of confidential information (such as vehicle configuration information) and / or data compartmentalization), which can enhance overall diagnostic capabilities, enhance the vehicle operator experience, and increase competition and implicit competition for active diagnostic development and implementation.
[0252] refer to Figure 49 , the example system 4900 includes a vehicle 102 having a first traditional network area 4902 and a second high-capability network area 4904. For example, the first traditional network area 4902 can be a first network type, such as a CAN bus, and the second high-capability network area 4904 can be a second network type, such as an Ethernet network. In some embodiments, the second high-capability network area 4904 can be the same type as the first traditional network area 4902, but can be a higher-capability version, such as a high-speed CAN bus, a higher-speed Ethernet network, etc. In some embodiments, such as Figure 49A system such as the one depicted in 4900 may exist where a vehicle is migrating to an upgraded network type (such as during a transition period within multiple model years of a vehicle), as new components are added to the vehicle that utilize a higher capability network, etc.
[0253] The example system 4900 includes a CND 108 interposed between a first traditional network zone 4902 and a second high-capability network zone 4904, wherein the CND 108 includes a policy manager circuit 5602 that interprets a policy 5606 including an external communication value 4906, and an external communication control circuit 4908 that regulates communications between external devices 5618 and endpoints of the first traditional network zone 4902 and / or endpoints of the second high-capability network zone 4904 in response to the external communication value 4906. For example, external communications between endpoints of the first traditional network zone 4902 may be restricted to reduce the amount of traffic on the first traditional network zone 4902 created by communications to and from external devices 4918 and / or due to the sensitivity of endpoints on the first traditional network zone 4902 (e.g., where vehicle control and / or proprietary information is maintained on the first traditional network zone 4902, and / or where security protocols associated with the first traditional network zone 4902 are more restricted than those available with respect to the second high-capability network zone 4904). In another example, external communications between endpoints of the second high-capability network zone 4904 may be restricted to reduce external transmissions (e.g., via the vehicle's transceiver, utilizing a particular data provider, etc.) from the vehicle (e.g., where the higher-capability devices on the second high-capability network zone 4904 may have the capability to generate high data rates) due to a potentially large number of devices on the second high-capability network zone 4904, including devices that may have been recently added to the vehicle (and accordingly do not have a long history of known usage, security reviews, and / or vehicle operational impact data) and / or devices that may have been added by an entity that is not as tightly controlled as the providers of the devices on the first traditional network zone 4902 (e.g., devices that may be provided by a third party, are related to recently developed vehicle capabilities, and / or are not related to core vehicle functions (such as entertainment providers)). The reasons provided for limiting the amount of external traffic between endpoints on various networks and external devices are non-limiting and provided for illustration, but the external communications control circuitry 4908 may regulate communications between endpoints of any network zone and any external device for any reason.
[0254] The example system 4900 includes external communication values 4906 that include active diagnostic descriptions—e.g., diagnostic operations and / or data collection to be performed as diagnostic operations, and the active diagnostic descriptions can involve commands to any endpoint on any network zone of the vehicle, data collected from any endpoint on any network zone of the vehicle, and / or communications with any endpoint on any network zone of the vehicle. The example system 4900 includes external communication values 4906 that include active test descriptions—e.g., test operations (e.g., testing of any endpoint, actuator, sensor, flow, application, vehicle function, and / or vehicle controller on the vehicle), and the active test descriptions can involve commands to any endpoint on any network zone of the vehicle, data collected from any endpoint on any network zone of the vehicle, and / or communications with any endpoint on any network zone of the vehicle. The example system 4900 includes external communication values 4906, which include data request values (e.g., collection of data parameters from any endpoint and / or processing including data parameters) and / or vehicle command values (e.g., commands to any actuator, display, controller, etc. with any endpoint). Example and non-limiting external devices 5618 include service tools, manufacturer tools, dealer tools, and / or cloud-based tools.
[0255] Example external communication values 4906 include a target device description that includes an identification of a target endpoint (e.g., a network zone, a local address, a sensor name, an actuator name, a data parameter name, etc.), wherein the external communication control circuitry 4908 determines that the endpoint has a different configuration than the identification provided in the target device description (e.g., a different network zone, a local address, a sensor name, an actuator name, a data parameter name, etc.). In some embodiments, the external communication control circuitry 4908 may include or utilize configuration circuitry 5604 (e.g., referring to FIG. Figure 56 、 47 and related descriptions) to determine the appropriate identification for the target endpoint. The example external communication value 4906 does not include the identification of the target endpoint, and the external communication control circuit 4908 provides the appropriate identification for the target endpoint based on the external communication value 4906 (again refer to Figure 56 、 47 5604). As can be seen, the operation of system 4900 allows external device 5618 to operate across multiple vehicle configurations without specific knowledge of endpoint locations, parameter names, local addresses, etc., to enable active diagnostics, testing, and data collection. A vehicle configuration can represent a change in a vehicle following service, replacement of a component (e.g., an endpoint), an upgrade of a component, and / or executable instructions stored on a computer-readable medium, changes over the course of a model year, and / or changes to a vehicle due to a marketing campaign, upgrade, and / or remanufacturing.
[0256] refer to Figure 50 , schematically depicts an example process 5000 for commanding an actuator in response to a diagnostic command value. The example process 5000 includes: operation 5002, interpreting a policy including an active diagnostic description; operation 5004, providing a diagnostic command value to an endpoint in response to an active diagnostic condition; and operation 5006, commanding an actuator in response to the diagnostic command value.
[0257] refer to Figure 51 , schematically depicts an example process 5100 for commanding an actuator in response to a diagnostic command value. The example process 5100 includes: operation 5102, interpreting a policy including an active diagnostic description and a diagnostic execution condition; and operation 5104, determining whether the vehicle operating condition is consistent with the diagnostic execution condition and / or the diagnostic command value (e.g., determined based on the active diagnostic description). In response to a "yes" determination at operation 5104, process 5100 includes: operation 5004, providing the diagnostic command value to the endpoint in response to the active diagnostic condition; and operation 5006, commanding the actuator in response to the diagnostic command value.
[0258] refer to Figure 52 , schematically depicts an example process 5200 for commanding an actuator in response to a diagnostic command value. The example process 5200 includes: operation 5002, interpreting a policy including an active diagnostic description; and operation 5203, performing a diagnostic data collection operation in response to the active diagnostic description. The example process 5200 further includes: operation 5004, providing a diagnostic command value to an endpoint in response to the active diagnostic condition; and operation 5006, commanding an actuator in response to the diagnostic command value.
[0259] refer to Figure 53 , schematically depicts an example process 5202 for performing diagnostic data collection operations. The example process 5202 includes: an operation 5302 of processing the collected data (e.g., processing the payload and / or frame information of the message of the collected data); an operation 5304 of storing the collected processed data; and an operation 5306 of transmitting at least a portion of the stored data to an external device.
[0260] refer to Figure 54 , schematically depicts an example process 5400 for storing and / or transmitting a diagnostic confirmation value. Example process 5400 includes: operation 5002, interpreting a policy including an active diagnostic description; operation 5004, providing a diagnostic command value to an endpoint in response to an active diagnostic condition; and operation 5006, commanding an actuator in response to the diagnostic command value. Example process 5400 further includes: operation 5402, determining a diagnostic confirmation value; and operation 5404, storing the diagnostic confirmation value and / or transmitting the diagnostic confirmation value to one or more external devices.
[0261] refer to Figure 55 , schematically depicts an example process 5500 for commanding an actuator in response to a diagnostic command value. Figure 50 In addition to the operations described above, the example process 5500 also includes an operation 5502 of determining whether the target device description points to a network address value for a target endpoint associated with the command actuator (e.g., if the target device description does not point to a network address value or points to an incorrect network address value, then operation 5502 determines "no"). In response to a "yes" determination at operation 5502, the process 5500 continues to operation 5004. In response to a "yes" determination at operation 5502, the process 5500 includes an operation 5504 of supplying or adjusting the network address value for the target endpoint, and then proceeds to operation 5004.
[0262] refer to Figure 56 , an example system 5600 for providing off-vehicle communication control consistent with embodiments of the present disclosure is provided. The systems described throughout this disclosure can be provided on a mobile application such as a vehicle or as described throughout this disclosure. The example systems herein describe a specific arrangement of, for example, converged network devices (CNDs) 108, circuits, controllers, or other components. The arrangement is provided for clarity of the description, but the components may be distributed, combined, partitioned, and / or have a different relationship to those components depicted as forming a system and performing the processes described herein.
[0263] The circuits, controllers, processors, or other devices described herein are configured to functionally perform the operations described herein and may include computing components such as processors, memory, and / or communication components. Additionally or alternatively, such devices may include logic circuits, hardware configured to perform one or more functions of the device, sensors, actuators, and / or any type of display device. A given circuit, controller, processor, or other such device may be distributed and / or grouped with other such devices, in whole or in part.
[0264] Certain operations herein are described as interpreting or receiving a parameter or obtaining a parameter value using other similar language depending on the context. Any such operation includes: receiving a parameter value as a network communication; receiving a parameter value from a sensor; receiving a parameter value as a feedback value (e.g., actuator position, reported fault code value, etc.); retrieving a parameter value from a memory location accessible to an interpreting or receiving device; receiving a parameter value as a command; receiving a parameter value as a response to a request from a receiving or interpreting device; and / or receiving a precursor value from which a parameter is at least partially determined (e.g., operating a virtual sensor using other information to determine an interpreted or received parameter value; determining a state value based on the received information, where the state value is the received or interpreted value for the purposes of this description; and / or using the received information to infer the interpreted value). Any such operations may further include more than these (e.g., interpreting parameter values in different manners at different times, operating conditions, during non-nominal conditions, depending on the source of the parameter value and / or depending on the use or purpose of the interpreted parameter value at a given time or during certain operating conditions) and / or combinations of these (e.g., operating a virtual sensor on the received information to determine a precursor value, and determining the interpreted parameter value in response to the precursor value).
[0265] Example system 5600 includes a vehicle 102 having a first network zone 5612 and a second network zone 5614, wherein the first network zone 5612 and the second network zone 5614 are different types of networks. Without limitation to any other aspect of the present disclosure, different types of networks as described herein take into account any differences in the networks, such as: differences in network capabilities (e.g., bandwidth, message size, latency, noise sensitivity, etc.); differences in network protocols at any layer (e.g., hardware type; message framing requirements; addressing scheme; acknowledgement type, requirements, or capabilities; broadcast availability, such as unicast, multicast, and / or broadcast); network standard type (e.g., Controller Area Network (CAN); Media Oriented Systems Transport (MOST) network; Local Interconnect Network (LIN); FlexRay network; Time Triggered Protocol (TTP) network; Low Voltage Differential Signaling (LVDS) network; Audio Video Bridging (AVB) compliant network; customized versions of any one or more of the foregoing; and / or proprietary versions of any one or more of the foregoing). Example network regions include electrical signal regions (e.g., networks in which corresponding network interface circuitry interprets electrical signal values as communications and / or provides electrical signal values as communications to endpoints of the electrical signal region, such as sensors that provide certain electrical values indicative of sensed parameter values, diagnostic values, and / or actuators that respond to certain electrical values to move to a selected position and / or apply a selected force, and / or in which the actuators can additionally or alternatively provide feedback information and / or diagnostic information on the electrical signal region). The electrical signals for the electrical signal region can be of any type, including at least: voltage values; frequency values; current values; and / or configured pulse width modulation (PWM) values, such as duty cycle, amplitude, selected period, and / or the like.
[0266] The example system 5600 further includes a policy manager circuit 5602 that interprets a policy 5606 including a network regulation description (not shown); and a configuration circuit 5604 that configures at least one network interface circuit (e.g., a first network interface circuit 5608 corresponding to a first network zone 5612 and / or a second network interface circuit 5610 corresponding to a second network zone 5610) in response to the policy 5606. For example, the policy 5606 may be provided by an external device 5618 and / or may be previously stored (e.g., at the time of manufacture, assembly, and / or during a previous update from the external device 5618), wherein the policy 5606 includes the network regulation description with a selected indication of the device's capabilities to utilize the network zones 5612, 5614, communicate between zones, and / or communicate with the external device 5618.
[0267] The example system 5600 includes a first network interface circuit 5608 provided as part of a CEG, wherein a first network zone 5612 is a CAN bus network; and a second network interface circuit 5610 provided as part of a CES, wherein the second network zone 5610 is provided as an Ethernet network. In the example, the first network interface circuit 5608 provides selected communications from the first network zone 5612 to the second network interface circuit 5610 at a selected port of the Ethernet network and / or receives selected communications from the second network zone 5614 at a selected port of the Ethernet network, thereby providing inter-network communication between the first network zone 5612 and the second network zone 5614. In an example, communication from the first network zone 5612 to the external device 5618 can be provided via the second network zone 5614 (e.g., where the external device 5618 is coupled to the second network zone 5614 and / or wirelessly connected to the vehicle 102) or directly to the external device 5618 (e.g., where the external device 5618 is directly coupled to the first network zone 5612 or a CAN bus).
[0268] The example system 5600 includes a first network zone 5612 as a virtual local area network (VLAN) that is logically separate from a second network zone 5614 but is located on hardware that is at least partially shared with the second network zone 5614. In an example, the first network interface circuit 5608 and the second network interface circuit 5610 can be operated as elements of a network switch or router to control communications between endpoints of the first network zone 5612 and the second network zone 5614 in response to the policy 5606.
[0269] Devices on the vehicle 102 that are regulated by the policy include, but are not limited to, one or more of the following: endpoints in a network zone; flows associated with a communication device (e.g., an endpoint or application); and applications associated with a communication device (e.g., an endpoint). For example, an endpoint in the first network zone 5612 (e.g., a backup camera on the vehicle 102) may request or perform communications on the vehicle's network, but may be associated with more than one application or flow (e.g., associated with a first flow associated with a vehicle reverse motion operation at a first operating condition, and associated with a second flow associated with a vehicle safety operation at a second operating condition), and accordingly, communications for the backup camera on the vehicle 102 may have different regulation parameters depending on the flow associated with the current operation. In some embodiments, an endpoint is associated with more than one application or flow, and the endpoint is regulated based on the highest priority of the associated applications or flows (e.g., to reduce communication requirements, such as determining which application or flow is requesting immediate communication to be regulated, and / or to reduce processing time to determine which application or flow is requesting immediate communication). In some embodiments, an endpoint is associated with more than one application or flow, and the endpoint is regulated based on the priority of the application or flow requesting immediate communication.
[0270] Devices on vehicle 102 that are regulated by policy may be referred to herein as, without limitation, local communication devices. Local communication devices include, but are not limited to, endpoints of a network zone; applications; flows; vehicle functions (e.g., power management, cabin comfort, traction control, etc.); sensor devices; service groups; and / or vehicle controllers (e.g., engine controller, transmission controller, anti-lock brake system (ABS) controller, advanced driver assistance system (ADAS) controller, etc.). It can be seen that a given component (e.g., an endpoint of a network zone) can be a first local communication device during one operating condition and a second local communication device during another operating condition—for example, depending on the vehicle operating condition (e.g., shutdown, maneuvering, parking, etc.), and / or can be a first local communication device for a first purpose (e.g., a brake controller performing an active traction control operation) and a second local communication device for a second purpose (e.g., a brake controller providing data to be stored for diagnostic operations). Furthermore, it can be seen that the distribution of communication devices among applications, flows, controllers, vehicle functions, etc. depends on the organizational policies of a particular system, design choices made by a manufacturer or other entity with control over the design and / or configuration of the system, and / or the like. For example, traction control may be provided by a unified vehicle controller for a given system (e.g., which may treat traction control as a vehicle controller for network regulation purposes); provided by a distributed controller for another system (e.g., which may treat traction control as a vehicle function for network regulation purposes); and / or may be considered a logically grouped collection of operations for another system (e.g., which may have any hardware organization including the organization previously described, and which may treat traction control as an application or flow for network regulation purposes). An organizational scheme and network regulation for local communication devices of a system may be readily determined by one skilled in the art having the benefit of this disclosure and the information generally available when considering a particular system. The organizational scheme for local communication devices includes the inclusion and / or association of endpoints of a network zone and / or certain communications (including source or destination communications for an endpoint) with one or more of the following: specific endpoints of the system, vehicle controllers, vehicle functions, applications, and / or flows.
[0271] Certain considerations in determining the organizational scheme include, but are not limited to: the number, type, capabilities, and inter-connection bandwidth of the system's network zones; the available size and / or granularity of policies for the system; the available processing power available to implement the system's policies; the number and distribution of vehicle controllers and other controllers throughout the system; expected changes to the system over time (e.g., the availability of reconfigured, remanufactured, and / or re-engineered vehicles; expected changes in upcoming model years associated with vehicles; and / or the level of consumer and / or third-party customization of vehicles that are available or desired); the number and distribution of sensors and / or actuators throughout the system and the connectivity of the sensors and / or actuators to the network zones (e.g., integration and / or use of sensors at the controllers); integration of smart sensors / actuators capable of directly interfacing with the network zone); the presence, number, and distribution of multi-purpose communication elements on the system (e.g., sensors, actuators, controllers, and / or data values that serve multiple vehicle functions, flows, and / or applications); the presence, number, and distribution of multi-purpose data elements on the system (e.g., sensors, actuators, controllers, and / or data values that provide redundant capabilities to support a given vehicle function, flow, and / or application); and / or the expected utilization of network aspects (e.g., communications on the network zone, external communication bandwidth, external communication data limits, inter-network communications, etc.) relative to relevant capacities (e.g., bandwidth of the network zone, external communication bandwidth, external communication data limits, inter-network communications, etc.).
[0272] The example policy manager circuit 5602 receives policy communications 5620 from an external device 5618 and interprets the policy 5606 by performing operations such as storing the policy 5606 (e.g., in a memory location accessible to the policy filter circuit 5602 and / or distributed across multiple memory locations) and / or updating the stored policy 5606. In some embodiments, the policy manager circuit 5602 configures the policy 5606 for utilization by the network regulation aspect of the system 5600, for example, by updating a plurality of configuration files utilized by the interface circuits 5608, 5610, adjusting a high-level description of the policy communication 5616 by the network regulation aspect of the system 5600 (e.g., limiting external communication data to 32GB per month) to executable commands, adjusting reference values of the policy communication 5620 (e.g., associating local address values of endpoints referenced in the policy communication 5616, such as when an endpoint has been moved to an external device 5618 without notification, and / or where specific addressing information of the local device is abstracted from the external device 5618, etc.), associating system-specific nomenclature with elements of the policy description 5620 (e.g., local parameter value names or IDs, flow names or IDs, application names or IDs, etc.), and the like.
[0273] The example system 5600 include...
Claims
1. A system comprising: A vehicle having a first network and a second network; a first device on a first network; as well as a converged network device (CND) interposed between the first network and the second network and structured to facilitate communication between the first device and the second network; The first network is of a different type than the second network.
2. The system of claim 1, further comprising: The second device is on the second network and is structured to communicate with the first device via the CND.
3. The system of claim 1, further comprising: An external device is communicatively coupled to the CND, wherein the external device is structured to adjust a configuration of the CND.
4. The system of claim 1, wherein at least one of the first network and / or the second network is a controller area network (CAN) based network.
5. The system of claim 1, wherein at least one of the first network and / or the second network is an Ethernet-based network.
6. The system of claim 1, wherein the first network is a controller area network (CAN) based network and the second network is an Ethernet based network.
7. The system of claim 6, wherein the CND comprises: Structured as a Configurable Edge Gateway (CEG) to access CAN-based networks; An Ethernet switch structured to access an Ethernet-based network; and Therein, the CEG provides a message to the Ethernet switch in response to a corresponding message on the CAN-based network.
8. The system of claim 7, wherein the CEG is structured to provide the message to the Ethernet switch according to the corresponding message on the CAN-based network as an Ethernet message including the encapsulated CAN message.
9. The system of claim 1, wherein the first network comprises at least one network type selected from the group consisting of a controller area network (CAN), a media oriented systems transport (MOST) network, a local interconnect network (LIN), a FlexRay network, a time triggered protocol (TTP) network, a low voltage differential signaling (LVDS) network, and an audio video bridging (AVB) compatible network.
10. The system of claim 1, wherein the second network comprises an Ethernet-based network, and wherein the CND comprises: a configurable edge gateway (CEG) structured to access the first network; An Ethernet switch structured to access an Ethernet-based network; and Wherein the CEG provides a message to the Ethernet switch in response to a corresponding message on the first network.
11. The system of claim 10, wherein the CEG is structured to provide the message to the Ethernet switch based on the corresponding message on the first network as an Ethernet message including the encapsulated message.
12. The system of claim 10, wherein the CND further comprises Ethernet management circuitry structured to manage access to the Ethernet-based network.
13. The system of claim 1, wherein the vehicle further has: a wireless gateway device structured to facilitate communication between the CND and a third network other than the vehicle.
14. The system of claim 1, wherein the CND is further interposed between the electrical actuator and the second network and is further structured to provide the electrical command to the electrical actuator in response to the command value on the second network.
15. The system of claim 14, wherein the CND is further structured to convert the command value on the second network into an electrical command for the electrical actuator.
16. The system of claim 14, wherein the CND is further interposed between the electrical sensor and the second network and is further structured to provide a sensed value on the second network in response to an electrical response of the electrical sensor.
17. The system of claim 16, wherein the CND is further structured to process the electrical response and to process the sensed value based on the processed electrical response.
18. An apparatus comprising: a first network interface circuit structured to interpret a first network data set having a first network format; translation circuitry structured to determine a message value from a first network data set and to encode the message value in a second network data set having a second network format; as well as a second network interface circuit structured to transmit a second network data set; in: The first network format and the second network format are vehicle data formats; and The first network format is different from the second network format.
19. The apparatus of claim 18, further comprising: The configuration circuit is structured to configure the first network interface circuit, the conversion circuit and / or the second network interface circuit in response to a configuration command value from a device external to a vehicle, the vehicle including the first network interface circuit and the second network interface circuit.
20. The apparatus of claim 19, wherein the configuration command value comprises at least one value selected from the group consisting of: Sampling rate value; Payload handling value; a target device for the message value from the first network data set, wherein the target device comprises a device on a vehicle for sending and / or receiving the message value; and An encapsulated description of a message value.
21. The apparatus of claim 18, wherein the first network format and / or the second network format is based on a controller area network (CAN).
22. The apparatus of claim 18, wherein the first network format and / or the second network format is based on Ethernet.
23. The apparatus of claim 18, wherein one of the first network format or the second network format is based on a controller area network (CAN), and the other of the first network format or the second network format is based on Ethernet.
24. The apparatus of claim 18, wherein the first network interface circuit and / or the second network interface circuit is integrated with a configurable edge gateway (CEG).
25. The apparatus of claim 18, wherein the first network interface circuit and / or the second network interface circuit is integrated with an Ethernet switch.
26. A method comprising: interpreting a first network data set having a first network format; determining a message value from the first network data set in response to interpreting the first network data set; encoding the message value in a second network dataset having a second network format; as well as transmitting a second network data set; in: The first network format and the second network format are vehicle data formats; and The first network format is different from the second network format.
27. The method of claim 26, further comprising: interpreting a configuration command value from a device external to a vehicle, the vehicle including first network interface circuitry that interprets a first network data set, translation circuitry that determines a message value from the first network data set and encodes the message value in a second data set, and second network interface circuitry that transmits a second network data set; as well as The first network interface circuitry, the second network interface circuitry, and / or the translation circuitry are configured based at least in part on the configuration command value.
28. The method of claim 26, wherein the first network format and / or the second network format is based on a controller area network (CAN).
29. The method of claim 26, wherein the first network format and / or the second network format is Ethernet based.
30. The method of claim 26, wherein the first network format or the second network format is based on a controller area network (CAN), and the other of the first network format and the second network format is based on Ethernet.
31. A system comprising: A vehicle having a first network and a second network of a different type than the first network; a first device disposed on a vehicle and structured to facilitate communications over a first network; a second device disposed on the vehicle and structured to facilitate communications over a second network; as well as A converged network device (CND), disposed on the vehicle, is at least partially defined by the first device and / or the second device and is structured to facilitate communication between the first network and the second network.
32. The system of claim 31 , further comprising: Configuration circuitry is disposed on the vehicle and is structured to modify the CND in response to a configuration command value from a service device external to the vehicle.
33. The system of claim 32, wherein the configuration circuit is disposed in the first device and / or the second device.
34. A method comprising: interpreting a first network data set having a first network format via a first interface circuit of a converged network device (CND); determining, via the translation circuitry of the CND, a message value from the first network data set in response to interpreting the first network data set; encoding, via the translation circuitry, the message value in a second network data set having a second network format different from the first network format; as well as transmitting a second network data set via a second interface circuit of the CND; in: The CND is defined at least in part by the first device and / or the second device; and The first device and / or the second device is arranged on a vehicle.
35. The method of claim 34, further comprising: Interpret configuration command values; as well as The CND is modified in response to the configuration command value.
36. The method of claim 35, wherein modifying the CND comprises: Selectively configuring which of the one or more portions of the first interface circuit, the conversion circuit, and / or the second interface circuit is at least partially defined by the first device and / or the second device.
37. The method of claim 35, further comprising: generating configuration command values external to the vehicle; as well as Transmits configuration command values to CND.
38. A method comprising: interpreting a first network data set having a first network format via a first interface circuit of a converged network device (CND); determining, via the translation circuitry of the CND, a message value from the first network data set in response to interpreting the first network data set; encoding, via the translation circuitry, the message value in a second network data set having a second network format different from the first network format; as well as transmitting a second network data set via a second interface circuit of the CND; in: The CND is defined at least in part by the first device and / or the second device; and The first device and / or the second device is arranged on a vehicle.
39. The method of claim 38, further comprising: Interpret configuration command values; as well as The CND is modified in response to the configuration command value.
40. The method of claim 39, wherein modifying the CND comprises: Selectively configuring which of the one or more portions of the first interface circuit, the conversion circuit, and / or the second interface circuit is at least partially defined by the first device and / or the second device.
41. The method of claim 39, further comprising: generating configuration command values external to the vehicle; as well as Transmits configuration command values to CND.
42. A system comprising: A vehicle having a first network area and a second network area of a different type than the first network area; Converged network device (CND), located between the first network area and the second network area, CND includes: a policy manager circuit structured to interpret policies including network regulation descriptions; configuration circuitry structured to configure at least one network interface circuitry in response to the policy; and The at least one network interface circuit, wherein the at least one network interface circuit is structured to facilitate communications between endpoints of the first network zone and endpoints of the second network zone.
43. The system of claim 42, wherein the policy manager circuit is further structured to receive policy communications from an external device and interpret the policy by performing one of storing the policy or updating the stored policy in response to the policy communication.
44. The system of claim 43, wherein the external device is communicatively coupled to the policy manager circuitry through at least one of the first network region or the second network region.
45. The system of claim 43, wherein the external device is communicatively coupled to the policy manager circuitry via at least one of a wireless network connection or a cellular network connection.
46. The system of claim 43, wherein the policy manager circuit is further structured to validate a policy prior to executing one of storing the policy or updating the stored policy.
47. The system of claim 46, wherein the policy manager circuit is further structured to provide a notification to an external device in response to validating the policy.
48. The system of claim 42, wherein the policy includes at least one data collection parameter.
49. A system as described in claim 42, wherein the policy includes a permission value corresponding to at least one endpoint of the first network zone or the second network zone, wherein the permission value includes at least one permission value selected from values consisting of: a data collection permission value; a service publishing permission value; a service subscription permission value; or an external communication permission value.
Citation Information
Cited By
System, method, and apparatus for managing vehicle data collection
US12415479B2
System, method, and apparatus for managing vehicle data collection
US12798517B2
