NETWORKED ELECTRIC VEHICLE CONTROL AND COMMUNICATION

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the benefit of and priority under 35 U.S.C. § 119 to U.S. Provisional Application No. 63/233,061, filed August 13, 2021, the disclosure of which is incorporated herein by reference in its entirety.

BACKGROUND

[0002] Motor vehicles, vehicle manufacturers, and vehicle dealerships can lack integration of internal and external systems sufficient to provide exact and timely knowledge of transactions maintenance, driver conditions, and other conditions.

SUMMARY

[0003] Systems and methods described herein are directed at least to an electric vehicle network system, a user input network system, a predictive electric vehicle maintenance system, an electric vehicle visual communication system, and a bidirectional electric vehicle communication system. Thus, a technological solution for networked vehicle control and communication is provided. This technical solution is not limited to electric vehicles, piloted vehicles, and the like. This technical solution is not limited to the particular examples set forth herein.

[0004] At least one aspect is directed to a vehicle control system. The vehicle control system can include a group control network operatively coupled with a plurality of group control devices and operable to transmit a control instruction compatible with one or more of the plurality of group control devices. The vehicle control system can include a first group control device among the plurality of group control devices, the first group control device operatively coupled with at least one first vehicle control device, operable to receive the control instruction by the group control network, operable to transform at least a portion of the control instruction into a first operating instruction compatible with the first vehicle control device, and operable to cause, based on the first operating instruction, the first vehicle control device to control a first vehicle system component operatively coupled to the first vehicle control device. The vehicle control system can include a second group control device among the plurality of group control devices, the second group control device operatively coupled with at least one second vehicle control device, operable to receive the control instruction by the group control network, operable to transform at least a portion of the control instruction into a second operating instruction compatible with the second vehicle control device, and operable to cause, based on the second operating instruction, the second vehicle control device to control a second vehicle system component operatively coupled to the second vehicle control device.

[0005] At least one aspect is directed to a method of controlling a vehicle. The method can include transmitting, by a group control network operatively coupled with a plurality of group control devices, a control instruction compatible with one or more of the plurality of group control devices. The method can include receiving, by a first group control device among the plurality of group control devices, the control instruction. The method can include transforming, by the first group control device, at least a portion of the control instruction into a first operating instruction compatible with a first vehicle control device operatively coupled with the first group control device. The method can include causing, based on the first operating instruction and via the first group control device, the first vehicle control device to control a first vehicle system component operatively coupled to the first vehicle control device, the control of the first vehicle system component restricted to the first group control device. The method can include receiving, by a second group control device among the plurality of group control devices, the control instruction. The method can include transforming, by the second group control device, at least a portion of the control instruction into a second operating instruction compatible with a second vehicle control device operatively coupled with the second group control device. The method can include causing, based on the second operating instruction and via a second group control device, the second vehicle control device to control a second vehicle system component operatively coupled to the second vehicle control device, the control of the second vehicle system component restricted to the second group control device.

[0006] At least one aspect is directed to an electric vehicle. The electric vehicle can include a group control network operatively coupled with a plurality of group control devices and operable to transmit a control instruction compatible with one or more of the plurality of group control devices. The electric vehicle can include a first group control device among the plurality of group control devices, the first group control device operatively coupled to at least one first vehicle control device, operable to receive the control instruction by the group control network, operable to transform at least a portion of the control instruction into a first operating instruction compatible with the first vehicle control device, and operable to cause, based on the first operating instruction, the first vehicle control device to control a first vehicle system component operatively coupled to the first vehicle control device. The electric vehicle can include a second group control device among the plurality of group control devices, the second group control device operatively coupled to at least one second vehicle control device, operable to receive the control instruction by the group control network, operable to transform at least a portion of the control instruction into a second operating instruction compatible with the second vehicle control device, and operable to cause, based on the second operating instruction, the second vehicle control device to control a second vehicle system component operatively coupled to the second vehicle control device.

[0007] At least one aspect is directed to a system of predictive vehicle maintenance. The system can include one or more sensors of a vehicle system to monitor one or more corresponding components of the vehicle system, and capture at least one of a vehicle operating characteristic, a vehicle operator characteristic, and an environmental characteristic. The system can include a vehicle controller coupled with the vehicle system to generate, based on at least one of the vehicle operating characteristic, the vehicle operator characteristic, and the environmental characteristic, a vehicle state metric associated with the vehicle system, and transmit, to the vehicle system, at least one diagnostic modification instruction to the vehicle system in response to a determination that the vehicle state metric satisfies a vehicle condition threshold.

[0008] At least one aspect is directed to a method of predictive vehicle maintenance. The method can include capturing, by one or more sensors monitoring one or more corresponding components of a vehicle system, at least one of a vehicle operating characteristic, a vehicle operator characteristic, and an environmental characteristic. The method can include generating, based on at least one of the vehicle operating characteristic, the vehicle operator characteristic, and the environmental characteristic, a vehicle state metric associated with the vehicle system. The method can include transmitting, to the vehicle system, at least one diagnostic modification instruction to the vehicle system in response to a determination that the vehicle state metric satisfies a vehicle condition threshold. [0009] At least one aspect is directed to a visual communication system located at a vehicle windshield. The system can include a light-emitting panel oriented toward a vehicle driver and integrated into a first surface of a dashboard of a vehicle cabin, the dashboard having a second surface opposite to the first surface and adjacent to a lower edge of a vehicle windshield. The system can include a plurality of light-emitting elements disposed within the light-emitting panel along the first surface and oriented toward the vehicle driver, the plurality of light-emitting elements operable to illuminate in accordance with a light response pattern including one or more of an order of illumination of one or more of the light-emitting elements, and one or more colors of light associated with one or more of the light-emitting elements.

[0010] At least one aspect is directed to a method of visual communication in a vehicle system. The method can include receiving, by a user interface integrated with a vehicle cabin, a user input. The method can include transmitting, in response to receiving the user input, an instruction to a light-emitting panel oriented toward a vehicle driver and integrated into a first surface of a dashboard of the vehicle cabin, the dashboard having a second surface opposite to the first surface and adjacent to a lower edge of a vehicle windshield, the light-emitting panel including a plurality of light-emitting elements disposed within the light-emitting panel along the first surface and oriented toward the vehicle driver. The method can include illuminating, in response to receiving the instruction at the light-emitting panel, the plurality of light-emitting in accordance with a light response pattern including one or more of an order of illumination of one or more of the light-emitting elements, and one or more colors of light associated with one or more of the light-emitting elements.

[0011] At least one aspect is directed to a system of bidirectional communication with a vehicle operator. The system can include a sensor operable to monitor one or more corresponding components of a vehicle system, and to obtain therefrom at least one of a vehicle operating characteristic and a vehicle operator characteristic The system can include a vehicle operator monitor operable to generate, based on at least one of the vehicle operating characteristic and the vehicle operator characteristic, a vehicle operator state metric associated with a vehicle operator of the vehicle system, and transmit, at least one diagnostic modification instruction to a bidirectional communication system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold. [0012] At least one aspect is directed to a method of bidirectional communication with a vehicle operator, including capturing, by one or more sensors monitoring one or more corresponding components of a vehicle system, at least one of a vehicle operating characteristic and a vehicle operator characteristic, generating, based on at least one of the vehicle operating characteristic and the vehicle operator characteristic, a vehicle operator state metric associated with a vehicle operator of the vehicle system, and transmitting, from the vehicle system, at least one diagnostic modification instruction to a bidirectional communication system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold.

[0013] At least one aspect is directed to a system of bidirectional communication with a vehicle operator, including a sensor operable to monitor one or more corresponding components of a vehicle system, and to obtain therefrom at least one of a vehicle operating characteristic and a vehicle operator characteristic, and a vehicle operator monitor operable to generate, based on at least one of the vehicle operating characteristic and the vehicle operator characteristic, a vehicle operator state metric associated with a vehicle operator of the vehicle system, and transmit, at least one diagnostic modification instruction to a bidirectional communication system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold.

[0014] At least one aspect is directed to an electric vehicle, with a sensor operable to monitor one or more corresponding components of a vehicle system, and to obtain therefrom at least one of a vehicle operating characteristic and a vehicle operator characteristic, and a vehicle operator monitor operable to generate, based on at least one of the vehicle operating characteristic and the vehicle operator characteristic, a vehicle operator state metric associated with a vehicle operator of the vehicle system, and transmit, at least one diagnostic modification instruction to a communication system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold.

[0015] At least one aspect is directed to a system to obtain end user input. The system can include a communication interface comprising an application programming interface (API) compatible with a plurality of transaction collection systems and operable to obtain, from the plurality of transaction collection systems, one or more transaction parameters in a plurality of first formats each respectively compatible with one of the plurality of transaction collection systems and associated with corresponding transaction identifiers. The system can include a transaction parameter integrator comprising a customer resource management (CRM) system compatible with the API, the transaction parameter integrator operatively coupled with the communication interface and operable to transform, via the API, the transaction parameters in one or more of the first plurality of formats to a second format compatible with the CRM system. The system can include a transaction processor operable to generate, based on the transformed transaction identifiers and one or more system identifiers respectively associated with one or more of the plurality of transaction collection systems, one or more transaction objects including transactions parameters from one or more of the plurality of transaction collection systems associated with a particular transaction parameter among the plurality of transaction parameters.

[0016] At least one aspect is directed to a method of obtaining customer input. The method can include obtaining, by an application programming interface (API) compatible with a plurality of transaction collection systems and from a plurality of transaction collection systems, one or more transaction parameters in a plurality of first formats each respectively compatible with one of the plurality of transaction collection systems and compatible with the CRM system. The method can include transforming, by a customer resource management (CRM) system compatible with the API, the transaction parameters in one or more of the first plurality of formats to a second format associated with the transaction identifiers. The method can include generating, based on the transformed transaction identifiers and one or more system identifiers respectively associated with one or more of the plurality of transaction collection systems, one or more transaction objects including transactions parameters from one or more of the plurality of transaction collection systems associated with a particular transaction parameter among the plurality of transaction parameters.

[0017] At least one aspect is directed to a vehicle control system, with a first group control device operatively coupled with at least one first vehicle control device and operable to instruct the vehicle control device to control a first vehicle system component operatively coupled to the first vehicle control device, and a second group control device operatively coupled with at least one second vehicle control device and operable to instruct the second vehicle control device to control a second vehicle system component operatively coupled to the second vehicle control device.

[0018] At least one aspect is directed to a method of controlling a vehicle. The method can instruct, via a first group control device, a vehicle control device operatively coupled with the first group control device to control a first vehicle system component operatively coupled to the first vehicle control device, the control of the first vehicle system component restricted to the first group control device. The method can instruct, via a second group control device, a second vehicle control device operatively coupled with the second group control device to control a second vehicle system component operatively coupled to the second vehicle control device, the control of the second vehicle system component restricted to the second group control device.

[0019] At least one aspect is directed to an electric vehicle with a first group control device operatively coupled to at least one first vehicle control device and operable to instruct the first vehicle control device to control a first vehicle system component operatively coupled to the first vehicle control device, and a second group control device operatively coupled to at least one second vehicle control device and operable to instruct the second vehicle control device to control a second vehicle system component operatively coupled to the second vehicle control device.

[0020] At least one aspect is directed to a method of predictive vehicle maintenance, including capturing, by one or more sensors monitoring one or more corresponding components of a vehicle system, at least one of a vehicle operating characteristic, a vehicle operator characteristic, and an environmental characteristic, generating, based on at least one of the vehicle operating characteristic, the vehicle operator characteristic, and the environmental characteristic, a vehicle state metric associated with the vehicle system, and transmitting, to the vehicle system, at least one diagnostic modification instruction to the vehicle system in response to a determination that the vehicle state metric satisfies a vehicle condition threshold.

[0021] At least one aspect is directed to a method of visual communication in a vehicle system. The method can include illuminating a light-emitting panel disposed proximate to a lower edge of a vehicle windshield and oriented toward a vehicle driver, in response to receiving a user input. [0022] At least one aspect is directed to a system to obtain end user input. The system can include a communication interface operable to obtain, from a transaction collection system, one or more transaction parameters in a first format and associated with corresponding transaction identifiers, and a transaction parameter integrator operatively coupled with the communication interface and operable to transform the transaction parameters to a second format associated with the transaction identifiers.

[0023] At least one aspect is directed to a method of obtaining customer input. The method can include obtaining, from a transaction collection system, one or more transaction parameters in a first format and associated with corresponding transaction identifiers, and transforming the transaction parameters to a second format associated with the transaction identifiers.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] These and other aspects and features of this technical solution will become apparent to those ordinarily skilled in the art upon review of the following description of specific implementations in conjunction with the accompanying figures, wherein:

[0025] FIG. 1 depicts an example vehicle network system.

[0026] FIG. 2 depicts an example vehicle network system.

[0027] FIG. 3 depicts an example vehicle network system.

[0028] FIG. 4 depicts an example network system to obtain user input.

[0029] FIG. 5 depicts an example method to obtain user input.

[0030] FIG. 6 depicts an example graphical user interface.

[0031] FIG. 7 depicts an example graphical user interface.

[0032] FIG. 8 depicts an example graphical user interface.

[0033] FIG. 9 depicts an example graphical user interface.

[0034] FIG. 10 depicts an example graphical user interface. [0035] FIG. 11 depicts an example graphical user interface.

[0036] FIG. 12 depicts an example graphical user interface.

[0037] FIG. 13 depicts an example graphical user interface.

[0038] FIG. 14 depicts an example graphical user interface.

[0039] FIG. 15 depicts an example graphical user interface.

[0040] FIG. 16 depicts an example graphical user interface.

[0041] FIG. 17 depicts an example visual communication system of a vehicle.

[0042] FIG. 18 depicts an example visual communication system in a state.

[0043] FIG. 19 depicts an example graphical user interface.

[0044] FIG. 20 depicts an example bidirectional communication system of a vehicle.

[0045] FIG. 21 depicts an example vehicle network system.

[0046] FIG. 22 depicts an example method of controlling a vehicle.

[0047] FIG. 23 depicts an example method of predictive vehicle maintenance.

[0048] FIG. 24 depicts an example method of visual communication in a vehicle system.

[0049] FIG. 25 depicts an example method of bidirectional communication with a vehicle operator.

[0050] FIG. 26 depicts an example method of obtaining customer input.

DETAILED DESCRIPTION

[0051] This technical solution will now be described in detail with reference to the drawings, which are provided as illustrative examples of the implementations so as to enable those skilled in the art to practice the implementations and alternatives apparent to those skilled in the art. The figures and examples below are not meant to limit the scope of this technical solution to a single implementation, but other implementations are possible by way of interchange of some or all of the described or illustrated elements. Moreover, where certain elements of this technical solution can be partially or fully implemented using known components, only those portions of such known components that are necessary for an understanding of this technical solution will be described, and detailed descriptions of other portions of such known components will be omitted so as not to obscure this technical solution. Implementations described as implemented in software should not be limited thereto, but can include implementations implemented in hardware, or combinations of software and hardware, and vice-versa, as will be apparent to those skilled in the art, unless otherwise specified herein. In the present specification, an implementation showing a singular component should not be considered limiting; rather, the present disclosure is intended to encompass other implementations including a plurality of the same component, and vice-versa, unless explicitly stated otherwise herein. Moreover, applicants do not intend for any term in the specification or claims to be ascribed an uncommon or special meaning unless explicitly set forth as such. Further, this technical solution encompass present and future known equivalents to the known components referred to herein by way of illustration.

[0052] Vehicle systems lack vehicle network systems capable of efficiently managing vehicle control across numerous legacy and modern vehicle systems. Especially as electric vehicles include systems that include advanced capabilities, a vehicle network system must also be able to support those advanced capabilities without degradation in operating requirements including latency, throughput, parallel processing or bottlenecking, and the like. Thus, this technical solution is directed to a vehicle network system including, for example, a high-bandwidth and packet-based communication interface between multiple system controller devices (“SoCs”), allow rapid peer-to-peer communication between each SoC. Each SoC can control, by an advanced system processor, a group of vehicle control devices each governed by an embedded processor or the like. Each SoC can have dedicated control over its respective group of vehicle control devices by an exclusive vehicle communication interface operatively coupling the SoC only with its respective vehicle control devices. The vehicle communication interface can be a serial interface, a parallel interface, or the like.

[0053] FIG. 1 depicts an example vehicle network system, in accordance with this technical solution. As illustrated by way of example in FIG. 1, an example vehicle network system 100 includes a group communication interface 102 and one or more vehicle control group systems. The vehicle control group systems can include a hybrid control SoC 110, an infotainment SoC 120, an ADAS SoC 130, a body control SoC 140, and an additional SoC. One or more of the SoC systems can include respective electronic devices, including microcontrollers, embedded controllers, and the like, and can include one or more system processors or the like. Any number of additional SoCs can be included in the system 100, and that an additional SoC can include or correspond in at least one of structure and operation to any SoC discussed herein but is not limited thereto.

[0054] A vehicle network system 100 can include a first group control device 110 operatively coupled with at least one first vehicle control device 210 and operable to instruct the vehicle control device 210 to control a first vehicle system component operatively coupled to the first vehicle control device 210, and a second group control device 120 operatively coupled with at least one second vehicle control device 320 and operable to instruct the second vehicle control device 320 to control a second vehicle system component operatively coupled to the second vehicle control device 320. Each of the hybrid control SoC 110, an infotainment SoC 120, an ADAS SoC 130, a body control SoC 140, and an additional SoC (as needed) 150 can correspond to respective group control devices of the vehicle network system 100, and can be operatively coupled with each other by the group communication interface 102. The group communication interface 102 can include at least one interface compatible with an Ethernet protocol, a packetized communication protocol, a full-duplex communication protocol, a parallelized communication protocol, and the like. The group communication interface 120 can support a transmission bandwidth of at least one of at least 1 Kb/s, 1 Mb/s, 1 Gb/s, and the like.

[0055] The group control device 110, 120, 130, 140 or 150 can include at least one of a central processing unit, a graphics processing unit, and a microprocessor. The group control device 110, 120, 130, 140 or 150 can include a system processor operatively coupled with the group communication interface 102 and operable to manage vehicle control by one or more vehicle control devices 310, 320, 330, 340 or 350 operatively coupled with the group control device. The group control device 110, 120, 130, 140 or 150 can thus act as a supervisor, controller, or the like, for multiple vehicle control devices 310, 320, 330, 340 or 350 associated with particular vehicle components, parts, structures, operations, or the like. [0056] Each group control device 110, 120, 130, 140 or 150 can include a system processor that is operable to execute one or more instructions associated with input from and output to the group communication interface 102. The system processor can be an electronic processor, an integrated circuit, or the like including one or more of digital logic, analog logic, digital sensors, analog sensors, communication buses, volatile memory, nonvolatile memory, and the like. The system processor can include but is not limited to, at least one microcontroller unit (MCU), microprocessor unit (MPU), central processing unit (CPU), graphics processing unit (GPU), physics processing unit (PPU), embedded controller (EC), or the like. The system processor can also include a memory operable to store or storing one or more instructions for operating components of the system processor and operating components operably coupled to the system processor. The one or more instructions can include at least one of firmware, software, hardware, operating systems, embedded operating systems, and the like. The system processor or the system 100 generally can include at least one communication bus controller to effect communication between the system processor and the other elements of the system 100.

[0057] FIG. 2 depicts an example vehicle network system further to the system of FIG. 1. As illustrated by way of example in FIG. 1, an example vehicle network system 200 includes the group communication interface 102 and one or more vehicle control group systems. The vehicle control group systems can include the hybrid control SoC 110, the infotainment SoC 120, the ADAS SoC 130, the body control SoC 140, and the additional SoC 150. The system 200 also includes a brake electronic control unit (“ECU”) 210, a battery ECU 220, a battery management system (“BMS”) ECU 230, a transmission ECU, and an active suspension ECU 250. The ECUs 210, 220, 230, 240 and 250 can be operatively coupled with each other and with the hybrid control SoC 110 by a vehicle communication interface 202. The hybrid control SoC 110 can perform one or more control and monitoring operations with respect to one or more of the ECUs 210, 220, 230, 240 and 250, and can instruct the ECUs 210, 220, 230, 240 and 250 to perform one or more control operations, monitoring operations, and the like, with respect to any vehicle systems operatively coupled with the ECUs 210, 220, 230, 240 and 250. The hybrid control SoC 110 can be operatively coupled with one or more vehicle systems to control motion, direction, travel, speed, and the like, of the vehicle having the vehicle control system. The hybrid SoC 110 can thus control a wide range of vehicle systems, and can control a plurality of vehicle control devices while communicating on a peer-to-peer basis with other SOC systems of the vehicle network system 100.

[0058] For example, the first group control device 110 and the second group control device 120 operatively can be coupled with one another by a first group communication interface 102. For example, the first vehicle control device includes a first plurality of vehicle control devices 310 operatively coupled by a first vehicle communication interface 202. For example, the second vehicle control device includes a second plurality of vehicle control devices 320 operatively coupled by a second vehicle communication interface 302. For example, the group control device 110 can include at least one of a central processing unit, a graphics processing unit, and a microprocessor. For example, the vehicle control device can include at least one of an embedded controller, an electronic control unit, and a microcontroller. For example, a vehicle corresponding to the system can include at least one of an automobile, an aircraft, a watercraft and a spacecraft, and including the vehicle system. For example, the vehicle system can include at least one of an autonomous vehicle system and a semi-autonomous vehicle system. For example, the vehicle system component can include at least one of an engine, a vehicle control system, a climate control system, and a user interface system.

[0059] FIG. 3 depicts an example vehicle network system further to the system of FIG. 1. As illustrated by way of example in FIG. 3, an example vehicle network system 300 includes the group communication interface 102 and one or more vehicle control group systems. The vehicle control group systems can include the hybrid control SoC 110, the infotainment SoC 120, the ADAS SoC 130, the body control SoC 140, and the additional SoC 150. The system 300 can include a plurality of vehicle communication interfaces 202, including the vehicle communication interface 202 associated with the hybrid control SoC, and vehicle communication interface 302, 304, 306 and 308, each correspondingly associated with the infotainment SoC 120, the ADAS SoC 130, the body control SoC 140, and the additional SoC 150.

[0060] The first group control device and the second group control device can be operatively coupled with one another by a first group communication interface. The group communication interface 102 can provide a communication link between each SoC of the vehicle network system 300, allowing each SoC to independently communicate with any other SoC on the network directly and asynchronously according to any instructions included on or associated with that SoC.

[0061] The first vehicle control device can include a first plurality of vehicle control devices operatively coupled by a first vehicle communication interface. Each SoC can include more than one vehicle control device on its respectively vehicle communication interface. This way, a particular SoC can control a particular system or subsystem of a vehicle corresponding to a particular group of operations, functions, or the like. For example, infotainment SoCs 120 and 140 can respectively control infotainment systems for a driver and a passengers, or separate and distinct passengers, or passenger interface devices integrated with the cabin of the vehicle.

[0062] The second vehicle control device can include a second plurality of vehicle control devices operatively coupled by a second vehicle communication interface. Similarly, other SoCs can include separate vehicle communication interfaces respectively operatively coupling those SoCs with their corresponding vehicle control devices. Each SoC can thus control one or more vehicle control devices by its corresponding vehicle communication interface. Each SoC can further exclusively control its corresponding vehicle control devices, because it can be exclusively operatively coupled with those corresponding vehicle control devices by its corresponding vehicle communication interface.

[0063] The vehicle control device can include at least one of an embedded controller, an electronic control unit, and a microcontroller. The vehicle control device can be an embedded device having one or more low power, high redundancy, or like characteristics advantageous for embedding within vehicle systems and devices. Each vehicle control device can include one or more logical or electronic devices including but not limited to integrated circuits, logic gates, flip flops, gate arrays, programmable gate arrays, and the like. Any electrical, electronic, or like devices, or components associated with the vehicle control device can also be associated with, integrated with, integrable with, replaced by, supplemented by, complemented by, or the like, a system processor, SoC, or any component thereof.

[0064] A vehicle can include at least one of an automobile, an aircraft, a watercraft and a spacecraft, and can include the vehicle system. A vehicle including any of the systems described herein, in any part of this application, can correspond to any type of vehicle, and is not limited to an electric vehicle, a four-wheeled, vehicle, or a vehicle restricted to traveling by a roadway.

[0065] The vehicle system can include at least one of an autonomous vehicle system and a semi- autonomous vehicle system. A vehicle including any of the systems described herein, in any part of this application, can correspond to a vehicle having any level or type of autonomous capability. The vehicle in accordance with this technical solution can be fully autonomous, partially autonomous, fully, nonautonomous, selectably fully autonomous, selectably partially autonomous, or any combination thereof, or the like.

[0066] The vehicle system component can include at least one of an engine, a vehicle control system, a climate control system, and a user interface system. The vehicle system components can include embedded electronics integrated with specific vehicle components, and can include interfaces, parts, or the like, to detect or effect mechanical activity. For example, a vehicle system component can include a microcontroller including steering control or braking control. For example, a vehicle system component can include an ambient temperature sensor, an ambient humidity sensor, a vibration sensor, and the like.

[0067] An electric vehicle can include a first group control device operatively coupled to at least one first vehicle control device and operable to instruct the first vehicle control device to control a first vehicle system component operatively coupled to the first vehicle control device, and a second group control device operatively coupled to at least one second vehicle control device and operable to instruct the second vehicle control device to control a second vehicle system component operatively coupled to the second vehicle control device. The first group device and the second group device can be independent SoC systems each responsible for vehicle operations by their respective groups of vehicle control devices. In the event that any particular SoC is dependent on input from or output to a vehicle control device of another SoC to complete a task to select a task, the dependent SOC can communicate efficiently with the other SoC by a high- bandwidth, a bidirectional communication path.

[0068] FIG. 4 depicts an example network system to obtain user input, in accordance with this technical solution. As illustrated by way of example in FIG. 4, an example network system 400 includes a back-end stack and a front-end stack. The back-end stack can include a DMS agnostic layer 402, a common API back-end 410, an ecommerce platform 420, a common customer resource management (“CRM”) application layer 430, and a marketing outreach application layer 440. The front-end stack can include a UI/UX framework 450 to present one or more graphical user interfaces or the like.

[0069] A system to obtain end user input, the system can include a communication interface operable to obtain, from a transaction collection system, one or more transaction parameters in a first format and associated with corresponding transaction identifiers, and a transaction parameter integrator operatively coupled with the communication interface and operable to transform the transaction parameters to a second format associated with the transaction identifiers. The communication interface can include an Internet interface, a network interface, a packet-switching interface, and the like. A transaction collection system can include a third party system tracking, executing, or the like, one or more transactions associated with one or more targets. Targets can include electric vehicles, hybrid vehicles, combustion vehicles, autonomous vehicles, autonomous drones, durable goods, virtual goods, virtual estate, and the like. A first format can be a digital communication format associated with a particular third party system, and a second format can correspond to a format associated with a centralized communication protocol of the system 400. A transaction identifier can include an identity, any information corresponding to identify, any information identifiable with, or the like, an entity associated with the target. For example, an entity can be a buyer or prospective buyer of an electric vehicle.

[0070] The transaction collection system can include a plurality of transaction collection systems. For example, the transaction collection system can corresponding to multiple dealership computer systems each communicatively coupled with the system 400. The DMS agnostic layer 402 can be operatively coupled with particular dealership computer systems in accordance with the communication protocols of those particular systems. For example, the DMS agnostic layer 402 can include a modular interface expandably compatible with various transaction collection system having heterogeneous protocols and the like for communication, storage, and the like.

[0071] For example, the transaction collection system can include a plurality of transaction collection systems. For example, the transaction parameters can include a plurality of groups of transaction parameters each associated with a corresponding one or the transaction collection systems. For example, a first group of transaction parameters among the plurality of groups can be in the first format, and the transaction parameters can include a second group of transaction parameters in a third format. For example, the transaction parameter integrator can transform the second group of transaction parameters to the first format. For example, the transaction collection system can include a dealership management system. For example, the transaction collection system can be at least partially remote from the communication interface. For example, the communication interface can include an application programming interface (API) corresponding to the transaction collection system. For example, the transaction parameter integrator can include a customer resource management (CRM) system.

[0072] The transaction parameters can include a plurality of groups of transaction parameters each associated with a corresponding one or the transaction collection systems. Groups of transaction parameters can include various categories of parameters including price, interaction frequency, interaction results, purchase result, purchase preferences, and the like. In addition, a group of transaction parameters can correspond to identity-based transaction parameters.

[0073] A first group of transaction parameters among the plurality of groups can be in the first format, and the transaction parameters can include a second group of transaction parameters in a third format. A first group of transaction parameters can be associated with a first group of entities at a first transaction collection system. This first group of transaction parameters can be in a first format associated with the first transaction collection system, based on the protocol and operating requirements of generating, transmitting, storing, and the like, transaction parameters in accordance with the first transaction collection system. A second, or any number of other transaction collection systems, can be in a second, third, or any other type of format in accordance with the format requirements of those respective transaction collection systems.

[0074] The transaction parameter integrator can be operable to transform the second group of transaction parameters to the first format. The transaction parameter integrator can include a command translation device, system or the like to translate commands from the first format. For example, a second format can include JSON or the like. The transaction parameter integrator can include one or more string or binary transformations to generate a JSON object from a first format. The common API back-end 410 can include the transaction parameter integrator. For example, the common API back-end 410 can include one or more APIs corresponding to translating various formats into the second format, and passing the translated information to the ecommerce platform 420.

[0075] The transaction collection system can include a dealership management system. The dealership management system can be a third party system associated with a particular dealership and operatively coupled by, for example, an Internet communication interface, to the common API back-end 410. The transaction collection system can be at least partially remote from the communication interface. The transaction collection system or dealership management system can include one or more computer devices, servers, or the like, located physically at a dealership location. Multiples transaction collection system can be located at any physical locations, and can have wide geographical distribution throughout one or more of the United States, North America, one or more international regions, international jurisdictions, and the like.

[0076] The communication interface can include an application programming interface (API) corresponding to the transaction collection system. The API can be compatible with one or more transaction collection systems, to advantageously collect, analyze and integrate entity and transaction parameter information from a wide range of disconnected and incompatible transaction collection systems. The API can advantageously translate from many formats in a single (e.g., second) format to allow concurrent and unified analysis of transaction parameters and entities obtained from a wide range of third party sources and geographic locations. The transaction parameter integrator can include a customer resource management (CRM) system. Once the transaction parameters are obtained, further analysis can be performed through a CRM system operatively coupled with the common API back-end 410.

[0077] FIG. 5 depicts an example method 500 to obtain user input further to the network system of FIG. 4. For example, the example system 400 can perform method 500. The method 500 can obtain input from an automotive website. (ACT 510.) The website can be associated with an automotive selection, customization, or like interface, application, or the like.

[0078] The method 500 can obtain a configuration of a car model. (ACT 520.) The car model can also correspond to any other type of vehicle as discussed herein. The configuration can correspond to input received from a dealership professional at a user interface of the system 400. For example, the method 500 determine availability of the car configuration. The method 500 can determine that a vehicle in accordance with an obtained configuration is available in an inventory. (ACT 522.) The example system can determine availability by querying an inventory database associated with the automotive website. The method 500 can determine that the vehicle must be customized and made. (ACT 526.)

[0079] The method 500 can determine to order a vehicle having at least a partial match to the configuration. (ACT 524.) For example, a partial match can correspond to 95% of features of the obtained configuration present in an available model. The partial match can be weighted based on input from the automotive website 510 or other criteria associated with a transaction parameter or entity. For example, factors related to particular features may be weighted more heavily if an entity has indicated high interest in those features.

[0080] The method 500 can generate an email message associated with the vehicle to alert the entity of the vehicle availability. (ACT 530.) The example system can transmit the message to the requesting entity, which can be a dealership professional or a prospective customer.

[0081] The method 500 can create a password to an account associated with one or more of the configuration, the dealership professional, and the requesting entity. (ACT 532.) For example, the example system can create an account for a requesting entity can place a voice call or the like to the requesting entity to verify the requesting entity can activate the account for the requesting entity.

[0082] The method 500 can execute a financial configurator. (ACT 540.) The financial configurator can include a user interface operable to present and obtain various parameters associated with the requesting entity and the configuration. For example, the financial configuration can generate a lease or financing plan customized to the requesting entity’s financial constraints or preferences.

[0083] The method 500 can execute a seller plug-in. (ACT 550.) The seller plug-in can include an interface, including but not limited to an application programming interface (API). The seller plug-in can generate at least one interface to obtain an indication of whether the buyer will execute a trade-in transaction. The API can translate instructions having a predetermined structure to or from the interface. The API can transform instructions between one or more structures distinct from the predetermined structure and the predetermined structure. The predetermined structure and the structures can correspond to one or more of a data format, a packet structure, an object structure, or any combination thereof, for example.

[0084] The method 500 can execute a test drive or virtual input request. (ACT 560.) The test drive or virtual input request can generate at least one interface to obtain an indication of whether the buyer will execute a test drive and whether the buyer will execute a virtual test drive, review, tour, demo, presentation, or the like.

[0085] The method 500 can present a service plan selection interface. (ACT 570.) The service plan selection interface can present one or more options for servicing a vehicle, associated with a transaction. The service plan selection interface can also obtain at least one selection indicating a user selection of a service plan, a user selection of a lack of service plan, or the like.

[0086] The method 500 can generate an indication that an order is complete. (ACT 572.) The indication can be transmitted to one or more of a user, dealership, manufacturer, or the like involved in a transaction. The indication can include one or more of a push notification, an email, a text message, a database query, or any combination thereof, for example. The indication can be transmitted to or generated at one or more computing devices each associated with one or more corresponding ones of the user, dealership, manufacturer, or the like involved in the transaction. The indication can include text, images, audio, or any combination thereof, for example, to communication that an order is complete.

[0087] The method 500 can execute a welcome gift mailing. (ACT 580.) The method 500 can execute one or more accessories options. (ACT 582.) The accessories options can include a mobility service package, and can include a temporary free trial thereof. The method 500 can execute a delivery and handover process. (ACT 584.) The delivery and handover can include a physical shipment, legal transfer, or the like of a product including an electric vehicle or the like.

[0088] A method of obtaining customer input, can include obtaining, from a transaction collection system, one or more transaction parameters in a first format and associated with corresponding transaction identifiers, transforming the transaction parameters to a second format associated with the transaction identifiers. The communication interface can include an application programming interface (API) corresponding to the transaction collection system. The transaction parameter integrator including a customer resource management (CRM) system.

[0089] FIG. 6 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 6, an example graphical user interface 600 can include record presentation portion 610, a vehicle object presentation portion 612, a record object presentation portion 614, and a navigation portion 620. The graphical user interface 600 can be presented on a display device. A display device can include, for example, a liquid crystal display (LCD), a light-emitting diode (LED) display, an organic light-emitting diode (OLED) display, or the like. The user interface 600 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface. The navigation portion 620 can present one or more control affordances to navigate to one or more distinct user interfaces as presented at least in FIGs. 6-16.

[0090] The user interface 600 can present at least a portion of a record and object data associated with the record obtained by communication interfaces between a server and a remote system. The user interface can present object data of a record corresponding to a person, and object data of a vehicle linked to the record corresponding to the person. The user interface can present the object data of the vehicle at the vehicle object presentation portion 612. The vehicle object presentation portion 612 can present at least a make or model of a vehicle currently owned by the person. The record object presentation portion 614 can present at least structured or unstructured strings of text or alphanumeric characters stored in or linked to an object corresponding to the person. The user interface 600 can obtain the object data of one or more of the record and the vehicle from one or more remote systems by a communication interface.

[0091] FIG. 7 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 7, an example graphical user interface 700 can include the navigation portion 620, a first metrics portion 710, a second metrics portion 712, a geographic metrics portion 720, and a search and details portion 730. The first and second metrics portions 710 and 712 can present metrics associated with one or more of the method 500, any data obtained from one or more graphical user interface collection systems, one or more transaction parameters, and the like. The user interface 700 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[0092] The user interface 700 can present at least one or more aggregated metrics obtained from one or more remotes systems corresponding, for example, to dealership computing system located physically at particular corresponding dealership locations. The first metrics portion 710 can present one or more visual presentations indicating particular aggregated metrics. For example, the first metrics portion 710 can present a plurality of pie charts each corresponding to aggregated interest metrics of a particular vehicle. The interest metrics can be obtained from records at remote systems by the communication interface. The first metrics portion 710 can present a plurality of pie charts each corresponding to particular subsets of dealerships. For example, the first metrics portion 710 can present a plurality of pie charts each corresponding to dealerships within particular geographical regions, demographic categories, or any combination thereof.

[0093] The second metrics portion 712 can present one or more visual presentations indicating particular aggregated metrics. For example, the second metrics portion 712can present a plurality of bar charts or line charts each corresponding to aggregated interest metrics of a particular vehicle, over time. The interest metrics can be obtained from records at remote systems by the communication interface. The second metrics portion 712 can present a plurality of bar charts or line charts each corresponding to particular aggregated subsets of dealerships. For example, the second metrics portion 712 can present a plurality of pie charts each corresponding to dealerships within particular groups of time, geographical regions, demographic categories, or any combination thereof. The geographic metrics portion 720 can present one or more geographic presentations corresponding to the first metrics portion 710 or the second metrics portion 712. [0094] FIG. 8 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 8, an example user interface 800 can include a configuration presentation portion 802, a render presentation portion 812, a vehicle parameter presentation portion 814, a configured order control affordance 820, and a predetermined order control affordance 830. The user interface 800 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[0095] The user interface 800 can present at least one or more visual aspects of an object corresponding to a vehicle. The object corresponding to the vehicle can be obtained from a remote systems by the communication interface. The render presentation portion 812 can generate, for example, a two-dimensional or three-dimensional visual depiction of a vehicle having one or more aspects obtained at a remote system and transmitted to the user interface 800 by the communication interface. The aspects can correspond to one or more data points, data selection, or any combination thereof. The aspects can be captured at the remote system in a format compatible with the remote system, and transmitted to the user interface 800 by the communication interface in a format compatible with the remote system, a format compatible with the user interface 800, or any combination thereof, for example. The render presentation portion 812 can include modifiable imagery corresponding to color, model, exterior structure, interior structure, and any combination thereof. The vehicle parameter presentation portion 814 can present at least one or more non-visual aspects of an object corresponding to a vehicle. For example, the vehicle parameter presentation portion 814 can present cost metrics corresponding to the configuration of the vehicle depicted in the render presentation portion 812.

[0096] The configured order control affordance 820 can receive user input and can cause the user interface 800 to indicate a selection of a vehicle order corresponding to the render presentation portion 812 and the parameter presentation portion 814. In response to receiving user input, the configured order control affordance 820 can cause a user interface distinct from the user interface 800 to be presented. The predetermined order control affordance 830 can receive user input and can cause the user interface to indicate a selection of a vehicle order corresponding partially to the render presentation portion 812 and the parameter presentation portion 814. In response to receiving user input, the predetermined order control affordance 830 can cause a user interface distinct from the user interface 800 to be presented. The predetermined order control affordance 830 can be selectively presented in response to a determination by any system as discussed herein that a vehicle with one or more aspects corresponding to the vehicle of the render presentation portion 812 is located at or within a predetermined distance of particular dealership location. For example, the particular dealership location can correspond to a remote system at which the object corresponding to the vehicle is obtained by the communication interface.

[0097] FIG. 9 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 9, an example user interface 900 can include the configuration presentation portion 802, a transmit presentation portion 910, a transmit destination input affordance 912, and a submit control affordance 914. The user interface 900 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[0098] The transmit presentation portion 910 can present at least one or more control affordances to receive user input and to cause the user interface to perform one or more corresponding actions. The transmit presentation portion 910 can, for example, include the transmit destination input affordance 912, and the submit control affordance 914 in a web form, mobile application, or any combination thereof. The transmit destination input affordance 912 can receive user input and can cause the user interface 900 to indicate a transmit destination corresponding to a user linked to a particular configuration of a vehicle. For example, a transmit destination can include an email address. The submit control affordance 914 can receive user input and can cause the user interface 900 to indicate a selection of transmit destination of a vehicle order corresponding to the render presentation portion 812 and the parameter presentation portion 814. In response to receiving user input, the submit control affordance 914 can cause a user interface distinct from the user interface 900 to be presented. [0099] FIG. 10 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 10, an example user interface 1000 can include the configuration presentation portion 802, an authentication presentation portion 1010, an authentication input affordance 1012, and a submit control affordance 1014. The user interface 1000 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[00100] The authentication presentation portion 1010 can, for example, include the authentication input affordance 1012, and the submit control affordance 1014 in a web form, mobile application, or any combination thereof. The authentication input affordance 1012 can receive user input and can cause the user interface 1000 to indicate an authentication parameter corresponding to a user linked to a particular configuration of a vehicle. For example, an authentication parameter can include a password, secure token, or one-time password. The submit control affordance 1014 can receive user input and can cause the user interface 1000 to indicate a submission of the authentication parameter entered at the authentication input affordance 1012. In response to receiving user input, the submit control affordance 1014 can cause a user interface distinct from the user interface 1000 to be presented.

[00101] FIG. 11 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 11, an example user interface 1100 can include the configuration presentation portion 802, a confirmation presentation portion 1110, and a submit control affordance 1112. The user interface 1100 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[00102] The confirmation presentation portion 1110 can, for example, include submit control affordance 1112 in a web form, mobile application, or any combination thereof. The submit control affordance 1112 can receive user input and can cause the user interface 1100 to indicate a confirmation of a selection of a vehicle order corresponding partially to the render presentation portion 812 and the parameter presentation portion 814. In response to receiving user input, the submit control affordance 1112 can cause a user interface distinct from the user interface 1100 to be presented.

[00103] FIG. 12 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 12, an example user interface 1200 can include the configuration presentation portion 802, payment presentation portion 1210, a payment processor input affordance 1212, and a submit control affordance 1214. The user interface 1200 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[00104] The payment presentation portion 1210 can, for example, include the payment processor input affordance 1212, and the submit control affordance 1214 in a web form, mobile application, or any combination thereof. The payment processor input affordance 1212 can receive user input and can cause the user interface 1200 to indicate a selection of a payment processing parameter corresponding to a user linked to a particular configuration of a vehicle. For example, a payment processing parameter can include a selection of a particular payment processing transaction order. A payment processing transaction order can correspond to a transaction including one or more of financing a purchase, leasing a vehicle, or executing a cash payment for a vehicle. The submit control affordance 1214 can receive user input and can cause the user interface 1200 to indicate a submission of the payment processing parameter entered at the payment processor input affordance 1212. In response to receiving user input, the submit control affordance 1214 can cause a user interface distinct from the user interface 1200 to be presented.

[00105] FIG. 13 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 13, an example user interface 1300 can include the configuration presentation portion 802, a transaction presentation portion 1310, a transaction selection control affordance 1312, and a transaction selection control affordance 1314. The user interface 1300 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[00106] The transaction presentation portion 1310 can, for example, include the transaction selection control affordance 1312, and the transaction selection control affordance 1314 in a web form, mobile application, or any combination thereof. The transaction selection control affordance 1312 can receive user input and can cause the user interface 1300 to indicate a selection of a supplemental transaction corresponding to a user linked to a particular configuration of a vehicle. For example, a supplemental transaction can include a selection of a trade-in vehicle. The transaction selection control affordance 1314 can receive user input and can cause the user interface 1300 to indicate a blocking of a supplemental transaction corresponding to a user linked to a particular configuration of a vehicle. In response to receiving user input, the transaction selection control affordance 1312 or the transaction selection control affordance 1314 can cause a user interface distinct from the user interface 1300 to be presented.

[00107] FIG. 14 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 14, an example user interface 1400 can include the configuration presentation portion 802, a timestamp presentation portion 1410, a timestamp input affordance 1412, and a submit control affordance 1414. The user interface 1400 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[00108] The timestamp presentation portion 1410 can, for example, include the timestamp input affordance 1412, and the submit control affordance 1414 in a web form, mobile application, or any combination thereof. The timestamp input affordance 1412 can receive user input and can cause the user interface 1400 to indicate a selection of a timestamp corresponding to a user linked to a particular configuration of a vehicle and a particular dealership corresponding to a particular remote system. For example, a selection of a timestamp can include a selection of a date on a calendar. The submit control affordance 1414 can receive user input and can cause the user interface 1400 to indicate a submission of the timestamp entered at the timestamp input affordance 1412. In response to receiving user input, the submit control affordance 1414 can cause a user interface distinct from the user interface 1400 to be presented.

[00109] FIG. 15 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 15, an example user interface 1500 can include the configuration presentation portion 802, a transaction presentation portion 1510, a transaction selection control affordance 1512, and a transaction selection control affordance 1514. The user interface 1500 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[00110] The transaction presentation portion 1510 can, for example, include the transaction selection control affordance 1512, and the transaction selection control affordance 1514 in a web form, mobile application, or any combination thereof. The transaction selection control affordance 1512 can receive user input and can cause the user interface 1500 to indicate a selection of a supplemental transaction corresponding to a user linked to a particular configuration of a vehicle. For example, a supplemental transaction can include a selection of a service or maintenance plan corresponding to a particular vehicle. The transaction selection control affordance 1514 can receive user input and can cause the user interface 1500 to indicate a blocking of a supplemental transaction corresponding to a user linked to a particular configuration of a vehicle. In response to receiving user input, the transaction selection control affordance 1512 or the transaction selection control affordance 1514 can cause a user interface distinct from the user interface 1500 to be presented. [00111] FIG. 16 depicts an example graphical user interface further to the system of FIG. 4. As illustrated by way of example in FIG. 16, an example user interface 1600 can include the configuration presentation portion 802, the render presentation portion 812, the vehicle parameter presentation portion 814, a confirmation presentation portion 1610, and a submit control affordance 1612. The user interface 1600 can be operatively coupled with one or more remote systems by a communication interface. The communication interface can include, for example, one or more application programming interfaces (APIs) each compatible with one or more of the remote systems. The remote system can include dealership computing systems located at physical location remote from the server including the communication interface.

[00112] The confirmation presentation portion 1610 can, for example, include the render presentation portion 812, the vehicle parameter presentation portion 814, and the submit control affordance 1612 in a web form, mobile application, or any combination thereof. The submit control affordance 1612 can receive user input and can cause the user interface 1600 to indicate a submission of a transaction corresponding to a user linked to a particular configuration of a vehicle. In response to receiving user input, the submit control affordance 1612 can cause a user interface distinct from the user interface 1610 to be presented.

[00113] Vehicle systems can be subject to wear and tear to many components, parts, systems, and the like. Vehicle operators, owners, or users may not be aware of the maintenance condition of many vehicle components, parts, systems, and the like until those parts are reduced in effective and efficient operation, and the like. Systems and methods described herein are directed to predictive vehicle maintenance to maintain a vehicle system and any systems associated therewith in improved operating condition and mitigate or prevent degradation of those systems. Predictive vehicle maintenance, in accordance with, for example, method 2300, can include obtaining one or more operating characteristics associated with the vehicle the environment of the vehicle the operator of the vehicle, any combination thereof, and any characteristics of one or more other vehicles similar to a monitored vehicle in accordance with any characteristic of the monitored vehicle. Thus, systems and methods described herein can obtain information in realtime regarding one or more systems, components, parts, and the like of a particular vehicle, and can determine whether the particular vehicle is ready for maintenance based on comparing the obtained information to historical data for that vehicle, historical data for a similar fleet of vehicles, real-time data for a similar fleet of vehicles, or any combination thereof.

[00114] Systems and methods describe herein can include a method 2300 of predictive vehicle maintenance, including capturing, by one or more sensors monitoring one or more corresponding components of a vehicle system, at least one of a vehicle operating characteristic, a vehicle operator characteristic, and an environmental characteristic, generating, based on at least one of the vehicle operating characteristic, the vehicle operator characteristic, and the environmental characteristic, a vehicle state metric associated with the vehicle system, and transmitting, to the vehicle system, at least one diagnostic modification instruction to the vehicle system in response to a determination that the vehicle state metric satisfies a vehicle condition threshold. A particular vehicle can have one or more sensors integrated therein, or the like, and can communicate one or more response from one or more of those sensors to an external device or system. For example, sensors can include a temperature sensors, an accelerometer, a pressure sensor, a humidity sensor, a methane sensor, a displacement sensor, a microelectromechanical sensor (MEMS) device, an electromagnetic sensor, a chemical sensor, or any combination thereof. Providing one or more of sensors as described herein can provide a technical improvement of at least increasing sensitivity or responsiveness of vehicle systems including a suspension system. Thus, one or more sensors as discussed herein can improve driving performance by leveraging inputting sensor data into an active suspension system for an improved driver experience.

[00115] They external device or system can be a remote server operable to obtain sensor responses from a plurality of vehicles. For example, a component of a vehicle system can include a brake pad, a brake disc, a headlamp, tail light, temperature sensor, door lock, window motor, speedometer, tachometer, differential, RADAR, LIDAR, vehicle camera, and the like. A vehicle operating characteristic can include a vehicle speed, direction, engine temperature, motor temperature, battery temperature, battery charge level, fuel level, and the like. A vehicle operator characteristic can include an operator identity, an operator route, an operator speed, and the like. For example, the operator characteristic can include a historical average, aggregate, or the like, of a particular pattern, path or the like of operating a vehicle. For example, the operator characteristic can be associated with particular rate of travel between two points, or a particular path of travel between two points commonly followed by the operator (e.g., travel by a particular highway between home and office). An environmental characteristic can include a geolocation, a geographical region, a municipality, jurisdiction, weather pattern, current weather, climate pattern, current climate, temperature, humidity, average rate of travel associated with any of the foregoing, any combination thereof, and the like. A vehicle state can include a mileage state, a tire wear state, and the like. The vehicle can also receive a modification instruction by a same or different communication channel than sensor responses are transmitted.

[00116] This technical solution can include a method of receiving, at a vehicle interface, at least one of the vehicle operating characteristic, the vehicle operator characteristic, and the environmental characteristic. The vehicle interface can include a Wi-Fi, cellular, or like connection operable to transmit and receive data between the vehicle and an external system. The vehicle interface can establish and maintain a real-time communication link with the external system. The external system can include a battery charging station, a fueling station, a home wireless network, a hotel wireless network, a public wireless network, and the like. For example, the communication interface can include an application programming interface (API) corresponding to the transaction collection system. For example, the transaction parameter integrator can include a customer resource management (CRM) system.

[00117] This technical solution can include a method with the vehicle interface including a communication interface integrated into at least one of a vehicle charging station, a vehicle fueling station, and a vehicle service station. For example, the vehicle interface can include a wireless interface at a battery charging station, a fueling station, or the like, and can include wired interface at a battery charging station, a fueling station, or the like. In a wired connection, the vehicle interface can establish a physical network connection by a network interface integrated into a vehicle battery or fueling receptacle and a corresponding network interface integrated into a vehicle battery charging of fueling nozzle, wand, handle, or the like.

[00118] This technical solution can include a method 2300 including generating the vehicle state metric, based on at least one of a historical vehicle operating characteristic, a historical vehicle operator characteristic, and a historical environmental characteristic. The vehicle state metric can be generated based on the historical vehicle operation and in view of one or more additional characteristics. For example, the vehicle state metric can determine tire wear based on a distance traveled by the vehicle, a tire type, a climate metric indicating a more or less rapid wear rate than average in the location of the vehicle, and a roadway metric indicating a more or less rapid wear rate than average in the location of the vehicle. A vehicle system can also generate one or more notifications based on satisfaction of the vehicle state metric. An external system can also generate or more notifications based on satisfaction of the vehicle state metric, and transmit the notification or an instruction to provide the notification to a particular vehicle.

[00119] This technical solution can include a method 2500 with at least one of the historical vehicle operating characteristic, the historical vehicle operator characteristic, and the historical environmental characteristic associated with past vehicle operation activity by a vehicle operator. As discussed above, the operator characteristic can be associated with particular rate of travel between two points, or a particular path of travel between two points commonly followed by the operator (e.g., travel by a particular highway between home and office). Thus, the historical vehicle operator characteristic can include the above. In addition, historical vehicle operator characteristic can include average speed associated with particular locations, average turning radius, average braking speed, average stopping distance, and the like. The historical vehicle operator characteristic can thus represent any driving behavior pattern, preference pattern, or the like, associated with a single vehicle operator, or any group of vehicle operators.

[00120] This technical solution can include a method 2500 including generating the vehicle state metric, based on at least one of an aggregate vehicle operating characteristic, an aggregate vehicle operator characteristic, and an aggregate environmental characteristic. The aggregate characteristics can be associated with a group of multiple vehicles, vehicle operators, or the like, associated with a common factor. The common factor may be one or more of the aggregate vehicle operator characteristic, and the aggregate environmental characteristic. For example, an aggregate vehicle operating characteristic may be an average brightness of headlights for a vehicle type in a particular geographic area. Thus, a vehicle having a headlight brightness significantly below the average for its local cohort of similar vehicles may be ready for predictive headlight maintenance. [00121] This technical solution can include a method 2300 with at least one of the aggregate vehicle operating characteristic, the aggregate vehicle operator characteristic, and the aggregate environmental characteristic associated with vehicle operation activity by one or more vehicle operators. One or more of the characteristics noted above can be associated with a particular vehicle operation activity of a particular vehicle operator. Thus, for example, a vehicle’s average speed on the highway may be associated with a pattern of slowdown of traffic during snowy or rainy periods associated with the locale of the vehicle operator.

[00122] This technical solution can include a method 2300 with the components of a vehicle system including at least one of an electric motor, a headlight, a taillight, a vehicle battery, a brake pad, a LIDAR system, a camera, and a radar system. The components of the vehicle system are not limited to those described herein. This technical solution can include a method 2300 with the vehicle operating characteristic including at least one of a battery discharge level, a headlight luminosity, and a vehicle speed. This technical solution can include a method 2300 with the vehicle operator characteristic including at least one of a vehicle steering pattern, and a vehicle usage pattern. A vehicle usage pattern can include a pattern of travel, including a recurring path of travel, a recurring time associated with a particular path of travel, and the like.

[00123] This technical solution can include a method 2300 with an environmental characteristic including at least one of an ambient temperature, a climate parameter, and a weather parameter associated with a geographic location. The environmental characteristic weight, modify, transform, or the like, any characteristic based on one or more of the ambient temperature, a climate parameter, and a weather parameter. For example, fully operational headlight luminosity may be weighted downward for a vehicle at a particular locale at a particular time, if, for example, that locale and time are associated with lower visibility due to snowstorms, rainstorms, sandstorms, and the like.

[00124] Vehicle operators are subjected to significant amounts of sensory input while operating a motor vehicle, and must make instant judgments and reactions to stimuli from the road and from vehicle systems providing notifications, states, and the like, related to the stimulus of the vehicle’s surroundings and the environment in which the vehicle generally operates. Complex vehicle user interfaces and notification systems can impair the vehicle operator’s ability to rapidly process and react to traffic conditions, road hazards, and the like, that may appear during the vehicle’s operation. Vehicle systems that require reading of text or close listening of narrative voice content can distract the driver and impair the vehicle operator in safe operation of the vehicle. Thus, this technical solution is directed to a visual communication system 1700 or 1800 of a vehicle to mitigate and prevent impairment of a driver while providing multiple types of communication to the driver regarding at least the vehicle’s surroundings and the environment. The visual communication system 1700 or 1800 can include one or more lights 1720 arranged in a row along a dashboard of a vehicle and oriented toward a vehicle operator. Thus, the vehicle operator is able to view the lights 1720 of the visual communication system 1700 or 1800 while operating the vehicle and remaining facing toward the windshield and thus remaining observing the vehicle’s surroundings through the windshield. The visual communication system 1700 or 1800 is operable to generate one of more patterns of illuminated lights along the dashboard in one or more colors, temporal patterns, spatial patterns, and the like. Illumination of the lights 1720 of the visual communication system 1700 or 1800 can vary in pattern, color, and the like, based on the specific notification delivered to the vehicle operator. Thus, this technical solution can generate in real-time, simplified visual notifications to the vehicle operator that the vehicle operator can perceive and understand much more quickly than text or voice communications.

[00125] FIG. 17 depicts an example visual communication system of a vehicle, in accordance with this technical solution. As illustrated by way of example in FIG. 17, an example visual communication system 1700 includes a visual communication system 1710, one or more visual communication elements 1720, a vehicle display 1730, a vehicle display control affordance 1732, and a vehicle steering affordance 1740. The visual communication system 1710 can be separate and distinct from the vehicle display 1730, and can present visual information separate and distinct from that presented by the vehicle display 1730. The visual communication system 1710 can include a plurality of visual communication elements 1720 arranged substantially in a horizontal row along the dashboard. The visual communication elements 1720 are not limited to the arrangement shown, and can, for example, be stacked or oriented in another direction.

[00126] FIG. 18 depicts an example visual communication system in a first state, further to the system of FIG. 7. As illustrated by way of example in FIG. 18, an example visual communication system 1800 includes the vehicle display 1730, the vehicle display control affordance 1732, the vehicle steering affordance 1740, a visual communication system 1810, one or more visual communication elements 1820 in a first state, one or more visual communication elements 1822 in a second state, and one or more visual communication elements 1824 in a third state. The first, second and third states of the elements 1820, 1822 and 1824 can vary based on brightness color and the like. The elements 1820, 1822 and 1824 can respectively be in a first state having a highest brightness, a second state having a lower brightness than the first state, and a third state having a lowest brightness or an off state. For example, visual communication elements 1820, to the farthest right side of the vehicle dashboard, can be in a brightest state, followed by visual communication elements 1822, between visual communication elements 1820 and visual communication elements 1824, in a dimmed state, and visual communication elements 1824, to the farthest left side of the vehicle dashboard, can be in a further dimmed or off state. A relative brightness, color, pattern thereof, timing thereof, and the like, can vary in any way, and is not limited to the examples disclosed herein.

[00127] FIG. 19 depicts an example graphical user interface further to the system of FIG. 17. As illustrated by way of example in FIG. 19, an example graphical user interface 1900 includes a display presenting one or more display interface elements. Each display interface element can include a control affordance, including but not limited to a touch-sensitive presentation portion, button, application, control, and the like. The graphical user interface 1900 can include a status bar portion 1210 including at least a local time and a wireless connectivity indicator, a media portion 1920 including media playback information, a daily summary portion 1930 including a local weather portion, a calendar portion, and a call placement portion, an application portion 1940 including one or more applications and application navigation affordances, and a vehicle control portion 1950, including vehicle cabin controls. The graphical user interface 1900 is not limited to the specific example configuration of FIG. 19.

[00128] This technical solution can include a visual communication system located proximate to a vehicle windshield, the system including a light-emitting panel disposed proximate to a lower edge of a vehicle windshield and oriented toward a vehicle driver. The light-emitting panel can include a plurality of visual communication elements arranged in a horizontal row. The visual communication elements can include, but are not limited to lighting by LED, OLED, QLED, LCD, incandescent, halogen, and the like. The light-emitting panel can be disposed on or in any surface of the vehicle cabin, including but not limited to the top of a dashboard, the bottom of a windshield, the top of a windshield, the cabin roofline adjoining the windshield, the windshield, door panels, side window panels, rear window panels, rear roofline, and the like.

[00129] This technical solution can include a system with a plurality of light-emitting elements disposed within the light-emitting panel and oriented toward a vehicle driver. The light-emitting elements can be arranged in any configuration within the light-emitting panel. For example, the light-emitting elements can be disposed in a single row across the light-emitting panel. For example, the light-emitting elements can be disposed in multiple stacking rows across the lightemitting panel. The light emitting-elements can also be disposed on, integrated with, extend onto, and the like, any other cabin surface of the vehicle cabin or the like.

[00130] This technical solution can include a method of visual communication in a vehicle system, the method including illuminating a light-emitting panel disposed proximate to a lower edge of a vehicle windshield and oriented toward a vehicle driver, in response to receiving a user input. User input can include a user’s voice command, a user’s manipulation or lack thereof of a steering affordance, user interface affordance, and the like. For example, the light-emitting panel can generate a particular visual pattern in response to a “yes or no” voice query from the vehicle operator, including a first response for a “yes” response to the vehicle operator’s query and a second response for a “no” response to the vehicle operator’s query. This technical solution can thus include a user interface including voice command responses through a visual-pattern based light-emitting device independent of natural language communication. The visual pattern communication proximate to the dashboard or windshield, for example, of this technical solution can increase safety by reducing cognitive load on a driver while operating and navigating a vehicle.

[00131] This technical solution can include a method of illuminating a plurality of light-emitting elements in accordance with a light response pattern, the light-emitting elements including the light-emitting panel. The light response pattern can include a pulsating brightness, a change in colors, a change in selective illumination or brightness, and the like. The light response pattern can include a gradient of brightness, color, and the like. [00132] This technical solution can include a method with the light response pattern including an order of illumination of one or more of the light-emitting elements. An order of illumination can include an order of changing illumination color, and the like with respect to a particular position of the visual communication element, or light-emitting element, within a light-emitting panel. For example, an order of illumination can include a brightness order from brightest at one or more light-emitting elements at a first position of the light-emitting panel, dimmest or no illumination at a second position of the light-emitting panel, and a varying, gradient, or the like at intermediate, intervening, or like positions of the light-emitting panel.

[00133] This technical solution can include a method with the light response pattern including one or more colors of light associated with one or more of the light-emitting elements. The lightemitting elements can project any visible or invisible color.

[00134] This technical solution can include a method with the light response pattern including illuminating a portion of the light-emitting elements proximate to one or more sides of a vehicle including the vehicle windshield. For example, in response to a road hazard on the right side of a vehicle, light-emitting elements on the right side of the visual communication system can illuminate to alert the driver to the hazard. For example, colors of the visual communication system can also vary based on road hazard. The color can be red for a vehicle pedestrian, deer, or the like, and can be yellow for a lane marker, barrier, pothole, or the like.

[00135] This technical solution can include a method with the user input including voice input. The vehicle operator can issue voice commands through a voice input system integrated into the vehicle cabin or associated therewith. An associated voice input system can include a smartphone, microphone, or the like, operatively coupled, wirelessly or by physical connection, to the visual communication system or the like.

[00136] Vehicle operators can be exposed to significant amounts of stimulus, stress, and the like while operating a vehicle. Stressors can be a result of operating the vehicle, and can also include stressors external to the operation of the vehicle. A physiological state of the vehicle operators can be modified by these stimuli and stressors, and a vehicle operator may desire to have the physiological state return to state not subject to stressors, stimuli, and the like. Thus, this technical solution can advantageously provide to a vehicle operator a communication in response to detecting the vehicle operator’s state, including but not limited to the vehicle operator’s physiological state.

[00137] FIG. 20 depicts an example bidirectional communication system of a vehicle, in accordance with this technical solution. As illustrated by way of example in FIG. 20, an example bidirectional communication system 2000 includes a sensor emotional awareness system 2010, one or more system inputs 2020, and one or more system outputs 2030. The emotional awareness system 2010 can include an electronic device operable to obtain one or more of the inputs 2020 and generate and transmit one or more of the outputs 2030. The inputs 2020 can include sensor response associated with the vehicle operator, the vehicle cabin, the vehicle operating state, and any combination thereof. The emotional awareness system 2010 can include one or more logical or electronic devices including but not limited to integrated circuits, logic gates, flip flops, gate arrays, programmable gate arrays, and the like. The emotional awareness system 2010 can include a learning engine, a machine learning engine, a deep learning engine, an artificial intelligence engine, a correlation engine, any portion thereof, and the like.

[00138] This technical solution can include a method of bidirectional communication with a vehicle operator, including capturing, by one or more sensors monitoring one or more corresponding components of a vehicle system, at least one of a vehicle operating characteristic and a vehicle operator characteristic, generating, based on at least one of the vehicle operating characteristic and the vehicle operator characteristic, a vehicle operator state metric associated with a vehicle operator of the vehicle system, and transmitting, from the vehicle system, at least one diagnostic modification instruction to a bidirectional communication system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold. A vehicle operator state metric can include a quantitative value, a threshold indication, and the like. The vehicle operator state metric can be generated based on one or more of the inputs 2020 and can indicate whether to activate a response to the vehicle operator’s state. For example, the vehicle operator state metric can include a “redline” in which an output 2030 is generated based on satisfying the vehicle operator state metric. For example, a communication channel to a counselor, therapist, doctor, family member, or the like can be opened if the vehicle state metric satisfies a stress threshold. [00139] This technical solution can include a method of establishing a communication channel at the vehicle system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold. The communication channel can include a telephone connection, an audio chat communication, a video chat communication, and the like. The communication channel can include an Internet channel, a packet network channel, a cellular communication channel, a frame-based communication channel, a wired communication channel, an Ethernet communication channel, an optical communication channel, and the like.

[00140] This technical solution can include a method with the vehicle operating characteristic including steering feedback. The inputs 2020 can include steering feedback, or any vehicle input that the vehicle is operable to obtain through any sensors within the vehicle or connected external vehicles.

[00141] This technical solution can include a method with the vehicle operator characteristic including biometric feedback. The inputs 2020 can include biometric feedback including from sensors included in the seat of the vehicle operator, the steering wheel, the dashboard, the windshield, the roof, and the like. Sensors can obtain temperature, heartbeat, grip strength, sweat levels, facial expressions, facial characteristics, and the like.

[00142] FIG. 21 depicts an example vehicle network system further to the system of FIG. 20. As illustrated by way of example in FIG. 21, an example vehicle network system 2100 includes the group communication interface 102 and one or more vehicle control group systems. The vehicle control group systems can include the hybrid control SoC 110, the infotainment SoC 120, the ADAS SoC 130, the body control SoC 140, and the additional SoC 150. The system 200 also includes one or more seat sensors 2110, one or more steering affordance sensors 2120, one or more braking sensors 2130, one or more facial recognition sensors 2140, and one or more HVAC temperature sensors.

[00143] FIG. 22 depicts an example method of controlling a vehicle. For example, any of 100- 400 can perform method 2200. The method 2200 can include transmitting a control instruction compatible with one or more of the plurality of group control devices. (ACT 2210.) For example, the method 2200 can include transmitting by a group control network operatively coupled with a plurality of group control devices. The method 2200 can include receiving, by a first group control device, the control instruction. (ACT 2215.) For example, the method 2200 can include receiving by a first group control device among the plurality of group control devices. The method 2200 can include transforming, by the first group control device the control instruction into a first operating instruction compatible with a first vehicle control device. (ACT 2220.) For example, the method 2200 can include transforming, by the first group control device, at least a portion of the control instruction into a first operating instruction. For example, the method 2200 can include a first vehicle control device operatively coupled with the first group control device. The method 2200 can include causing, based on the first operating instruction and via the first group control device, the first vehicle control device to control a first vehicle system component operatively coupled to the first vehicle control device. (ACT 2225.) For example, the method 2200 can include the control of the first vehicle system component restricted to the first group control device.

[00144] The method 2200 can include receiving, by a second group control device, the control instruction. (ACT 2230.) For example, the method 2200 can include receiving by a second group control device among the plurality of group control devices. The method 2200 can include transforming, by the second group control device, the control instruction into a second operating instruction compatible with a second vehicle control device. (ACT 2235.) For example, the method 2200 can include transforming, by the second group control device, at least a portion of the control instruction. For example, the method 2200 can include a second vehicle control device operatively coupled with the second group control device. The method 2200 can include causing the second vehicle control device to control a second vehicle system component operatively coupled to the second vehicle control device. (ACT 2240.) For example, the method 2200 can include causing based on the second operating instruction and via a second group control device. For example, the method 2200 can include the control of the second vehicle system component restricted to the second group control device.

[00145] FIG. 23 depicts an example method of predictive vehicle maintenance. For example, any of 100-400 can perform method 2200. The method 2300 can include capturing at least one of a vehicle operating characteristic, a vehicle operator characteristic, and an environmental characteristic. (ACT 2310.) For example, the method 2300 can include capturing by one or more sensors monitoring one or more corresponding components of a vehicle system. The method 2300 can include generating a vehicle state metric associated with the vehicle system. (ACT 2315.) For example, the method 2300 can include generating based on at least one of the vehicle operating characteristic, the vehicle operator characteristic, and the environmental characteristic. The method 2300 can include transmitting at least one diagnostic modification instruction in response to a determination that the vehicle state metric satisfies a vehicle condition threshold. (ACT 2320.) For example, the method 2300 can include transmitting to the vehicle system.

[00146] FIG. 24 depicts an example method of visual communication in a vehicle system. For example, any of 1700 and 1800 can perform method 2400. The method 2400 can include receiving, by a user interface, a user input. (ACT 2410.) For example, the method 2400 can include a user interface integrated with a vehicle cabin. The method 2400 can include transmitting an instruction to a light-emitting panel integrated into the vehicle cabin, the lightemitting panel including a plurality of light-emitting elements disposed within the light-emitting panel. (ACT 2415.) For example, the method 2400 can include transmitting, in response to receiving the user input. For example, the method 2400 can include a light-emitting panel oriented toward a vehicle driver. For example, the method 2400 can include a light-emitting panel integrated into a first surface of a dashboard of the vehicle cabin. For example, the method 2400 can include the dashboard having a second surface opposite to the first surface and adjacent to a lower edge of a vehicle windshield. For example, the method 2400 can include a plurality of light-emitting elements disposed within the light-emitting panel along the first surface and oriented toward the vehicle driver. The method 2400 can include illuminating the plurality of light-emitting elements in accordance with a light response pattern including one or more of an order of illumination of one or more of the light-emitting elements, and one or more colors of light. (ACT 2420.) For example, the method 2400 can include illuminating in response to receiving the instruction at the light-emitting panel. For example, the method 2400 can include one or more colors of light associated with one or more of the light-emitting elements.

[00147] FIG. 25 depicts an example method of bidirectional communication with a vehicle operator. For example, any of 1900-2100 can perform method 2500. The method 2500 can include capturing at least one of a vehicle operating characteristic and a vehicle operator characteristic. (ACT 2510.) For example, the method 2500 can include capturing by one or more sensors monitoring one or more corresponding components of a vehicle system. The method 2500 can include generating a vehicle operator state metric associated with a vehicle operator of the vehicle system. (ACT 2515.) For example, the method 2500 can include generating based on at least one of the vehicle operating characteristic and the vehicle operator characteristic. The method 2500 can include transmitting at least one diagnostic modification instruction to a bidirectional communication system. (ACT 2520.) For example, the method 2500 can include transmitting from the vehicle system. For example, the method 2500 can include transmitting in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold.

[00148] FIG. 26 depicts an example method of obtaining customer input. For example, any of the user interfaces 600-1600 can perform method 2600. The method 2600 can include obtaining one or more transaction parameters in a plurality of first formats each respectively compatible with one of the plurality of transaction collection systems and compatible with the CRM system. (ACT 2610.) For example, the method 2600 can include obtaining by an application programming interface (API) compatible with a plurality of transaction collection systems and from a plurality of transaction collection systems. The method 2600 can include transforming the transaction parameters in one or more of the first plurality of formats to a second format associated with the transaction identifiers. (ACT 2615.) For example, the method 2600 can include transforming by a customer resource management (CRM) system compatible with the API. For example, the method 2600 can include transforming the transaction parameters in one or more of the first plurality of formats to a second format.

[00149] The method 2600 can include generating one or more transaction objects including transactions parameters from one or more of the plurality of transaction collection systems. (ACT 2620.) For example, the method 2600 can include generating based on the transformed transaction identifiers and one or more system identifiers respectively associated with one or more of the plurality of transaction collection systems. For example, the method 2600 can include one or more of the plurality of transaction collection systems associated with a particular transaction parameter among the plurality of transaction parameters.

[00150] This technical solution can include a system of bidirectional communication with a vehicle operator, including a sensor operable to monitor one or more corresponding components of a vehicle system, and to obtain therefrom at least one of a vehicle operating characteristic and a vehicle operator characteristic, and a vehicle operator monitor operable to generate, based on at least one of the vehicle operating characteristic and the vehicle operator characteristic, a vehicle operator state metric associated with a vehicle operator of the vehicle system, and transmit, at least one diagnostic modification instruction to a bidirectional communication system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold. The diagnostic modification instruction can include any instruction in response to any determination, with respect to the vehicle operator state metric, and can be transmitted to any system of the vehicle including the vehicle operator, but is not limited thereto. The diagnostic modification instruction can also execute a modification of any vehicle system.

[00151] This technical solution can include an electric vehicle, with a sensor operable to monitor one or more corresponding components of a vehicle system, and to obtain therefrom at least one of a vehicle operating characteristic and a vehicle operator characteristic, and a vehicle operator monitor operable to generate, based on at least one of the vehicle operating characteristic and the vehicle operator characteristic, a vehicle operator state metric associated with a vehicle operator of the vehicle system, and transmit, at least one diagnostic modification instruction to a communication system in response to a determination that the vehicle operator state metric satisfies a vehicle operator condition threshold.

[00152] The term “coupled” and variations thereof, as used herein, means the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly to each other, with the two members coupled to each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled to each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g., “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic. [00153] The term “exemplary” and variations thereof, as used herein to describe various embodiments, are intended to indicate that such embodiments are possible examples, representations, or illustrations of possible embodiments (and such terms are not intended to connote that such embodiments are necessarily extraordinary or superlative examples).

[00154] The hardware and data processing components (such as the data processing system 1515) used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit or the processor) the one or more processes described herein.

[00155] The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

[00156] References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all of the described terms. References to at least one of a conjunctive list of terms may be construed as an inclusive OR to indicate any of a single, more than one, and all of the described terms. For example, a reference to “at least one of ‘A’ and ‘B’” can include only ‘A’, only ‘B’, as well as both ‘A’ and ‘B’. Such references used in conjunction with “comprising” or other open terminology can include additional items.

[00157] References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below”) are merely used to describe the orientation of various elements in the FIGURES. The orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.

[00158] Where technical features in the drawings, detailed description or any claim are followed by reference signs, the reference signs have been included to increase the intelligibility of the drawings, detailed description, and claims. Accordingly, neither the reference signs nor their absence have any limiting effect on the scope of any claim elements.

[00159] The construction and arrangement of the electric vehicle as shown in the various exemplary embodiments is illustrative only. Additionally, any element disclosed in one embodiment may be incorporated or utilized with any other embodiment disclosed herein. Although only one example of an element from one embodiment that can be incorporated or utilized in another embodiment has been described above, other elements of the various embodiments may be incorporated or utilized with any of the other embodiments disclosed herein.