Elastic Computing for In-Vehicle Computing Systems

The elastic computing module addresses load imbalances in in-vehicle systems by dynamically allocating resources, enhancing efficiency and reducing costs through optimized local and remote processing.

JP7593937B2Active Publication Date: 2024-12-03HARMAN INT IND INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021558660
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-04-12
Filing Date
2020-04-10
Publication Date
2024-12-03
Estimated Expiration
2040-04-10

AI Technical Summary

Technical Problem

In-vehicle computing systems face challenges with load imbalance between local and remote processing resources, leading to unnecessary consumption of external computing power and inefficiencies.

Method used

Implementing an elastic computing module that dynamically allocates computing resources between local and remote devices based on processing needs, determining resource capacity and software requirements to optimize resource utilization.

Benefits of technology

This approach reduces costs and complexity by efficiently managing local and remote processing, ensuring optimal resource allocation and load balancing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007593937000001
    Figure 0007593937000001
  • Figure 0007593937000002
    Figure 0007593937000002
  • Figure 0007593937000003
    Figure 0007593937000003
Patent Text Reader

Abstract

An example system for controlling a vehicle includes a first computing device physically located within the vehicle, a second computing device located remotely from the vehicle, and an elastic computing module communicatively coupled to the first computing device and the second computing device, the elastic computing module configured to determine computing power and memory capacity of the first and second computing devices, determine software requirements of software applications for controlling components of the vehicle, and dynamically allocate processing of the software applications to the first and / or second computing device based on the computing power and memory capacity of the first and second computing devices and the software requirements of the software applications.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 62 / 833,598, entitled "ELASTIC COMPUTING FOR IN-VEHICLE COMPUTING SYSTEMS," filed April 12, 2019. The entire contents of this application, recited above, are hereby incorporated by reference for all purposes.

[0002] The present disclosure relates to in-vehicle interface systems and associated controls. [Background technology]

[0003] Vehicles may include in-vehicle computing systems, such as a head unit for an infotainment system, that may provide multimedia and control functionality. For example, the in-vehicle computing system may provide navigation, multimedia playback, telephone, social media interactivity, mobile device charging, and / or other functionality, and may receive user input to control elements of the vehicle and the in-vehicle computing system. To provide such functionality, the in-vehicle computing system includes complex and costly processing and memory resources that enable the execution of an operating system and various applications. Summary of the Invention [Means for solving the problem]

[0004] To provide sufficient processing and memory resources to enable advanced multimedia functionality and vehicle control, vehicles may be communicatively coupled to external computing resources, such as cloud computing resources. However, such remote processing is often unnecessary when sufficient computing resources are available locally, which may result in a load imbalance between local and remote processing. Furthermore, in some cases, additional computational power may be required. To overcome such limitations, elastic computing can dynamically allocate computing resources according to processing needs.

[0005]

[0005] Embodiments are disclosed relating to in-vehicle systems and methods for allocating local and remote hardware computing resources. An exemplary system for controlling a vehicle includes a first computing device physically located within the vehicle, a second computing device located remotely from the vehicle, and an elastic computing module communicatively coupled to the first and second computing devices, the elastic computing module configured to: determine computing power and memory capacity of the first and second computing devices, determine software requirements of software applications for controlling components of the vehicle, and dynamically allocate processing of the software applications to the first and / or second computing devices based on the computing power and memory capacity of the first and second computing devices and the software requirements of the software applications. The present specification also provides, for example, the following items: (Item 1) 1. A system for controlling a vehicle, comprising: a first computing device physically located within the vehicle; a second computing device located remotely from the vehicle; and an elastic computing module communicatively coupled to the first computing device and the second computing device, determining the computational capabilities and memory capacities of the first computing device and the second computing device; determining software requirements for a software application for controlling components of the vehicle; dynamically allocating processing of the software application to the first computing device and / or the second computing device based on the computational power and the memory capacity of the first computing device and the second computing device and the software requirements of the software application; the elastic computing module configured to: A system comprising: (Item 2) 2. The system of claim 1, wherein the first computing device includes one or more of a plurality of central processing units (CPUs), a plurality of graphics processing units (GPUs), a plurality of neural processing units (NPUs), a plurality of digital signal processors (DSPs), and a plurality of memory devices. (Item 3) 3. The system of claim 2, wherein the second computing device comprises one or more of a second plurality of CPUs, a second plurality of GPUs, a second plurality of NPUs, and a second plurality of memory devices. (Item 4) 2. The system of claim 1, wherein the elastic computing module is further configured to establish a guest environment for a guest operator of the vehicle to access the software application with restricted access. (Item 5) Further comprising a plurality of peripheral devices; 2. The system of claim 1, wherein the elastic computing module is further configured to control access to one or more peripheral devices of the plurality of peripheral devices. (Item 6) the software application includes a plurality of software applications; the elastic computing module partitioning the plurality of software applications according to a domain of each software application; 2. The system of claim 1, wherein the elastic computing module allocates processing of each software application according to the partitions of the plurality of software applications. (Item 7) An in-vehicle interface system, one or more communication links configured to communicatively couple to the first local computing device, the second local computing device, or both; an elastic computing module communicatively configured to couple to the first local computing device and the second local computing device, determining a first set of processing parameters for the first local computing device and a second set of processing parameters for the second local computing device; establishing required safety parameters of a software application of the vehicle; allocating processing of the software application between the first local computing device and the second local computing device to meet the required safety parameters of the software application based on the first set of processing parameters and the second set of processing parameters; the elastic computing module configured to: An in-vehicle interface system comprising: (Item 8) 8. The in-vehicle interface system of claim 7, wherein the first set of processing parameters and the second set of processing parameters include at least one of a computing power and a memory capacity. (Item 9) Further comprising a first system on chip (SoC) and a second SoC; the first local computing device includes the first SoC; 8. The in-vehicle interface system of claim 7, wherein the second local computing device includes the second SoC. (Item 10) a first processing partition of the system is implemented to include the first device; 8. The in-vehicle interface system of item 7, wherein a second processing partition of the system is implemented to include the second device. (Item 11) the first processing partition is implemented in a first system-on-chip (SoC) of the system; Item 11. The in-vehicle interface system of item 10, wherein the second processing partition is implemented in a second SoC of the system. (Item 12) Item 11. The in-vehicle interface system of item 10, wherein the first processing partition handles processing related to one or more chassis functions, or one or more drivetrain functions, or both. (Item 13) the first processing partition is associated with a first safety class; Item 13. The in-vehicle interface system of item 12, wherein the second processing partition is associated with a second safety class. (Item 14) the communication link is configured to communicatively couple to the first local computing device; 8. The in-vehicle interface system of claim 7, further comprising a second communication link configured to communicatively couple to the second local computing device. (Item 15) the in-vehicle interface system further comprising an additional communication link configured to communicatively couple to a remote computing device; The elastic computing module includes: determining a third set of processing parameters for the remote computing device; and establishing required safety parameters of additional software applications for the vehicle; allocating processing of the software application among the first local computing device, the second local computing device, and the remote computing device to meet the required safety parameters of the software application based on the first set of processing parameters, the second set of processing parameters, and the third set of processing parameters; 8. The in-vehicle interface system of item 7, further configured to: (Item 16) 1. A method for in-vehicle elastic computing, comprising: determining a first partition for a first computing device physically located within the vehicle, the first partition being for a first domain; determining a second partition for a second computing device, the second partition being for a second domain; allocating processing of a first set of software applications associated with the first domain to the first computing device; allocating processing of a second set of software applications associated with the second domain to the second computing device; A method for in-vehicle elastic computing comprising: (Item 17) Item 17. The method for in-vehicle elastic computing described in Item 16, wherein the second computing device is a remote computing device. (Item 18) the first domain encompasses a first security category; Item 17. The method for in-vehicle elastic computing described in Item 16, wherein the second domain encompasses a second safety category. (Item 19) the first computing device includes a first system on a chip (SoC); Item 17. The method for in-vehicle elastic computing of item 16, wherein the second computing device includes a second SoC. (Item 20) 20. The method for in-vehicle elastic computing described in item 16, wherein the first domain encompasses one or more chassis functions, or one or more drivetrain functions, or both.

[0006] The present disclosure may be better understood from reading the following description of non-limiting embodiments, with reference to the accompanying drawings, in which: [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is an exemplary partial diagram of a vehicle interior including an in-vehicle computing system and a mobile device, in accordance with one or more embodiments of the present disclosure. [Diagram 2] FIG. 1 is a block diagram of an in-vehicle interface system and associated elements with which the in-vehicle interface system communicates, in accordance with one or more embodiments of the present disclosure. [Diagram 3] FIG. 1 is a block diagram of a domain-based partitioning of software processing in accordance with one or more embodiments of the present disclosure. [Figure 4] FIG. 2 is a block diagram of a computing cluster approach with a single processor in accordance with one or more embodiments of the present disclosure. [Diagram 5] 1 is a block diagram of a computing cluster approach comprising multiple processors in accordance with one or more embodiments of the present disclosure. [Figure 6] FIG. 1 is a block diagram of a computing cluster approach comprising multiple processors coupled by a network in accordance with one or more embodiments of the present disclosure. [Figure 7] FIG. 1 is a block diagram of an elastic computing architecture for in-vehicle processing in accordance with one or more embodiments of the present disclosure. [Figure 8] FIG. 1 is a block diagram illustrating partitioning of electronic devices with separate controllers in accordance with one or more embodiments of the present disclosure. [Figure 9A] FIG. 1 is a block diagram of an elastic computing architecture for in-vehicle processing for an exemplary vehicle, in accordance with one or more embodiments of the present disclosure. [Figure 9B] FIG. 1 is a block diagram of an exemplary in-vehicle interface system for a vehicle, in accordance with one or more embodiments of the present disclosure. [Figure 9C] FIG. 1 is a block diagram of an architecture for domain-based partitioning of software processing for an exemplary vehicle, in accordance with one or more embodiments of the present disclosure. [Figure 10]1 illustrates a method for in-vehicle elastic computing in accordance with one or more embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Domain partitioning, computing clustering techniques, elastic computing, and partitioning of electronics, as further described herein, may reduce the cost and complexity of providing a complete suite of advanced software for in-vehicle control.

[0009] As used herein, the terms "embodiments," "some embodiments," or "various embodiments" refer to the relevant feature, structure, or characteristic described being present in at least some embodiments, but not necessarily all embodiments. Moreover, various appearances of such terms do not necessarily all refer to the same embodiment. Also, terms listing elements using "and / or" language may refer to any combination of the listed elements. For example, "A, B, and / or C" can mean either A only, B only, C only, A and B, A and C, B and C, or A, B, and C.

[0010] FIG. 1 illustrates an exemplary partial view of the interior of a passenger compartment 100 of a vehicle 102 in which a driver and / or one or more passengers may be seated. The vehicle 102 of FIG. 1 may be an automobile including drive wheels (not shown) and an internal combustion engine 104. The internal combustion engine 104 may include one or more combustion chambers that may receive intake air via an intake flowpath and exhaust combustion gases via an exhaust flowpath. The vehicle 102 may be an automobile for road travel, among other types of vehicles. In some examples, the vehicle 102 may include a hybrid propulsion system including an energy conversion device operable to absorb energy from vehicle motion and / or the engine and convert the absorbed energy into an energy form suitable for storage by an energy storage device. The vehicle 102 may include a fully electric vehicle incorporating an on-board fuel cell, solar energy capture element, and / or other energy storage system for powering the vehicle.

[0011] As shown, the instrument panel 106 may include various displays and controls accessible to the driver of the vehicle 102, such as a touchscreen 108 of an in-vehicle interface system (e.g., an infotainment system), an audio system control panel, and an instrument cluster 110. Although the exemplary system shown in FIG. 1 includes audio system controls that may be implemented through a user interface of the in-vehicle interface system (such as the touchscreen 108) without a separate audio system control panel, in other embodiments, the vehicle 102 may include an audio system control panel that may include controls for a conventional vehicle audio system, such as a radio, a compact disc player, an MP3 player, etc. The audio system controls may include functionality for controlling one or more aspects of the audio output via one or more speakers 112 of the vehicle speaker system. For example, the audio system controls may control the volume of the audio input, the distribution of sound among the individual speakers of the vehicle speaker system, the equalization of the audio signal, and / or any other aspect of the audio output.

[0012] The instrument cluster 110 may include various gauges, such as a fuel gauge, a tachometer, a speedometer, and an odometer, as well as indicator and warning lights. A steering wheel 114 may protrude from the instrument panel 106 below the instrument cluster 110. Optionally, the steering wheel 114 may include one or more controls 116 that may be used in conjunction with the touch screen 108 to navigate and control the functions of the in-vehicle interface system. As an illustrative example, the controls 116 may include a button 117 that activates or initiates voice control of the in-vehicle interface system. For example, in response to the button 117 being pressed and / or while the button 117 is pressed, the microphone 126 may record one or more utterances by the driver or other occupants of the vehicle. The one or more utterances recorded via the microphone 126 may then be used to navigate or control one or more functions of the in-vehicle interface system if the one or more utterances include voice commands.

[0013] 1, it will be understood that instrument panel 106 may include additional components, such as door and window controls, a cigarette lighter that may also be used as a low voltage power outlet, a glove box, and / or any other suitable elements. In one or more embodiments, control of the onboard environment via one or more climate control system vents 118 may be performed using touch screen 108, and thus a separate climate control interface may not be included in instrument panel 106. However, in alternative embodiments, a separate climate control interface may be provided.

[0014] The vehicle interior 100 may include one or more sensors for monitoring the vehicle, the user, and / or the environment. For example, the vehicle interior 100 may include one or more seat-mounted pressure sensors 120 configured to measure pressure applied to a seat to determine the presence of a user. The vehicle interior 100 may include one or more door sensors 122 configured to monitor door activity, such as door opening and / or closing, door locking, door window operation, and / or any other suitable door activity events. A humidity sensor 124 may be included to measure humidity content of the vehicle interior 100. A microphone 126 may receive user input in the form of voice commands, allow a user to make phone calls, and / or measure ambient noise within the vehicle interior 100. It should be understood that the sensor arrangement shown in FIG. 1 is exemplary, and one or more additional or alternative sensors may be located in the engine compartment, the exterior of the vehicle, and / or other suitable locations to provide information regarding the operation of the vehicle, the vehicle's ambient conditions, the user of the vehicle, and / or the like.

[0015] The vehicle cabin 100 may also include one or more user objects, such as a portable device 128 that is stored within the vehicle before, during, and / or after the trip. The portable device 128 may include a smartphone, a tablet, a laptop computer, a portable media player, and / or any suitable portable computing device. The portable device 128 may be connected to the in-vehicle interface system via a communication link 130. The communication link 130 may be wired (e.g., Universal Serial Bus (USB), Mobile High Definition Link (MHL), High-Definition Multimedia Interface (HDMI), etc.) or wireless (e.g., BLUETOOTH, WI-FI, Near Field Communication (NFC), etc.) and may be configured to provide bidirectional communication between the portable device 128 and the in-vehicle interface system. For example, the communication link 130 may provide sensor and / or control signals from the in-vehicle system and touch screen 108 to the portable device 128, and may provide control and / or display signals from the portable device 128 to the in-vehicle system and touch screen 108. The communications link 130 may also provide power from an on-board power source to the portable device 128 for charging an internal battery of the portable device 128 .

[0016] Although the portable device 128 is illustrated as being spatially separate from the in-vehicle interface system and connected via a substantially external communications link (e.g., a cable or radio frequency signal), it should be understood that a portable device storage structure 132 or other storage structure may be formed in the instrument panel 106 or elsewhere in the vehicle to hold the portable device 128 at a particular location. The portable device storage structure 132 may include an integrated connector 134 to which the portable device 128 may be attached or "docked" to provide a substantially internal communications link between the portable device 128 and the interface system.

[0017] FIG. 2 illustrates a block diagram of the in-vehicle interface system 204 and associated elements with which it communicates. The in-vehicle interface system 204 may be located and / or integrated within a vehicle 202, such as the vehicle 102 of FIG. 1. The in-vehicle interface system 204 may communicate with one or more elements within the vehicle, including, but not limited to, vehicle systems connected via an in-vehicle interconnect, such as a Controller Area Network (CAN) bus 206. It should be appreciated that any suitable number and / or combination of interconnects may be used to enable communication between the in-vehicle interface system 204 (which may be referred to herein simply as the interface system 204) and various in-vehicle components, including, but not limited to, a CAN bus, a Media Oriented System Transport (MOST) bus, an Ethernet-based interconnect, and the like. The interconnects may communicate directly with the in-vehicle components and / or may communicate with such components via an intervening processor. In some embodiments, one or more in-vehicle components may communicate directly with the interface system 204 without or in addition to communicating with the interface system 204 via the CAN bus 206.

[0018] The interface system 204 can pass information from the CAN bus 206 to an external remote service 290, such as a cloud computing service or edge device, communicatively coupled to the vehicle 202 via wireless network 280 to leverage memory 292 and processor 294 and other computing resources of the remote service 290 to control various on-board elements of the vehicle 202. In some embodiments, the interface system 204 can include a wireless gateway and / or wireless protocols to enable a wireless connection between the interface system 204 and the remote service 290.

[0019] Display 210 may display images to provide visual feedback related to navigation, media playback, telephone, vehicle system control (e.g., cabin temperature control, cruise control settings, odometer output / settings, vehicle diagnostic control, vehicle operating mode control, etc.), and / or other vehicle-related functions. In some embodiments, display 210 may include a touch screen, such as touch screen 108 of FIG. 1, to allow user input for controlling vehicle-related functions to be received via display 210.

[0020] Remote service 290 can receive signals from interface system 204 and / or display 210, process the signals based on non-transitory instructions stored in memory 292 and executed by processor 294, output a display on display 210 and / or interface system 204, and / or control the signals. Although one remote service 290 is shown in FIG. 2, it should be understood that vehicle 202 can communicate with one or more remote services, including remote service 290, during operation.

[0021] As shown, remote service 290 is separate from vehicle 202 and is not integrated within vehicle 202. In contrast, each of the other systems and elements depicted within vehicle 202 in FIG. 2 may be integrated within vehicle 202. Remote service 290 may include computing resources (e.g., memory 292 and processor 294) that are separate from computing resources integrated within vehicle 202 (e.g., computing resources utilized by components depicted within vehicle 202 in FIG. 2).

[0022] The display signals may control the output of the display 210, while the control signals may control one or more other vehicle systems 216 in communication with the interface system 204. For example, the vehicle systems 216 may include controllable elements related to the engine and / or auxiliary elements such as windshield wipers, windows, doors / door locks, headlights, air conditioning systems, etc. The control signals may also control audio output at one or more speakers 218 of the vehicle 202. For example, the control signals may adjust audio output characteristics such as volume, equalization, sound imaging (e.g., a configuration of audio signals that produces an audio output that appears to a user to originate from one or more defined locations), audio distribution among the speakers 218, etc.

[0023] User input may be accepted via one or more on-board controls 220 that are transmitted to interface system 204 and / or remote services 290, for example, as an additional or alternative input source to an optional touch screen of display 210. On-board controls 220 may include any suitable user-actuable elements in and / or on the vehicle, including, but not limited to, any number or combination of buttons, sliders, switches, knobs, levers, joysticks, keypads, pedals, and the like. For example, on-board controls 220 may also include control elements within the interior of vehicle 202, such as steering wheel controls (e.g., steering wheel mounted sound system controls, cruise controls, windshield wiper controls, headlight controls, turn signal controls, and the like), instrument panel controls, accelerator / brake / clutch pedals, gear shifts, door / window controls located on the driver or passenger doors, seat controls, cabin lighting controls, sound system controls, cabin temperature controls, and the like. Control elements located outside the vehicle (e.g., controls for safety systems) may also be connected to interface system 204, such as via CAN bus 206. The control elements of the on-board controller 220 may be physically and permanently located on and / or within the vehicle to receive user input.

[0024] As a particular example, the in-vehicle control device 220 may include a microphone integrated within the cabin of the vehicle 202 that records or senses user input, such as voice control commands, that are routed to the interface system 204 and / or the remote services 290. As another example, the steering wheel controls and / or the instrument panel controls of the in-vehicle control device 220 may include the button 117 shown in FIG. 1 for initiating voice control, where pressing the button 117 indicates that the utterance sensed by the microphone includes a voice command. In this manner, utterances that are not intended for voice control of a vehicle element should not be inadvertently processed by the interface system 204 and / or the remote services 290 for controlling one or more elements of the vehicle 202. Additionally or alternatively, the user may indicate that the utterance is intended for voice control by uttering a wake word (e.g., a particular voice data string that may be a word, phrase, tone, or other predefined sound) for voice control. For example, the interface system 204 and / or the remote service 290 can monitor audio recorded by a microphone and process the audio to specifically detect a wake word without otherwise processing or handling the audio, and in response to detecting a wake word spoken by an occupant of the vehicle 202, the interface system 204 and / or the remote service 290 can process the speech sensed by the microphone that follows the wake word or trigger word.

[0025] The CAN bus 206 can communicate with one or more vehicle sensors 222 to provide an indication of vehicle operation and / or status to the interface system 204. The interface system 204 can pass sensor signals from the vehicle sensors 222 to the remote service 290 to provide contextual information related to the operation and / or environment of the vehicle and / or user to the remote service 290. The vehicle sensors 222 can include any suitable sensors, such as the in-vehicle sensors described herein above with respect to FIG. 1, vehicle operation status sensors (e.g., sensors monitoring fuel storage, engine temperature, oil storage, engine speed, vehicle speed, transmission / gear settings, tire pressure, traction, diagnostic information, etc.), and environmental sensors (e.g., rear camera and / or other sensors monitoring ambient conditions, such as temperature, humidity, pressure, road surface / conditions, etc.). Upon receiving user input and / or sensor signals at the remote service 290, the remote service 290 can determine adjustments to the display 210 and / or control instructions for the vehicle systems 216.

[0026] Information regarding the power status and / or power control signals may be exchanged between the power module 224 and the remote service 290 via the CAN bus 206 and the interface system 204. For example, the remote service 290 may receive information from the power module 224 and update the display 210 to provide feedback to a user regarding the power status of one or more vehicle components. The remote service 290 may additionally or alternatively provide control signals to the power module 224 based on user input, information received from the vehicle sensors 222, and / or information received from the power module 224.

[0027] Antenna 226 can provide AM / FM radio signals to interface system 204 for processing by interface system 204. For example, interface system 204 can control speaker 218 to control audio broadcast by an AM / FM radio station and can control display 210 to display information related to the AM / FM radio station and / or content being broadcast (e.g., information with audio broadcast via a radio data system).

[0028] To communicate with the various vehicle systems and remote 290 as described above, in some embodiments, interface system 204 may include one or more modules to address different communication protocols and other issues that may arise while passing signals between different systems. For example, interface system 204 may include a video switching module (not shown) for synchronizing and / or formatting a video feed from a rear camera for display on display 210. As another example, interface system 204 may include an encoder (not shown) and / or a decoder (not shown) for converting a signal received from one system and / or device into a format that is compatible with or otherwise can be interpreted by a target system and / or device. It should be understood that one or more of the above modules are optional, and that in some embodiments, interface system 204 may pass a received signal to another system and / or device without imparting any adjustments to the signal.

[0029] The interface system 204 includes at least a processor 232 and a memory 234 configured to provide the functionality described herein. In some examples, the interface system 204 includes multiple processors 232 and multiple memories 234. Additionally, the interface system 204 includes an elastic computing module 236.

[0030] The elastic computing module 236 evaluates vehicle hardware parameters including computational power and memory capacity of the processor 232 and memory 234, the system-on-chip (SoC) architecture of the processor 232 to which the vehicle peripherals are connected, bus speed, battery level, temperature, etc., as well as remote service parameters such as computational power and memory capacity of the processor 294 and memory 292 of the remote service 290, edge-to-edge latency, cost model, etc. The elastic computing module 236 further evaluates the needs of each software component such as computational bandwidth, memory, input / output, latency tolerance, safety, security, etc.

[0031] The elastic computing module 236 determines which software runs on the vehicle 202 and which software runs on the remote service 290. The elastic computing module 236 further dynamically allocates resources to deterministically meet the needs of the software and provides load balancing for the system.

[0032] The elastic computing module 236 establishes a guest environment for software running on the vehicle 202, allowing a "guest" user operating the vehicle 202 to access or control the vehicle 202 accordingly with limited access. The elastic computing module 236 further controls access to shared peripherals.

[0033] 3 is a block diagram illustrating an example architecture 300 for domain-based partitioning of software processing. The architecture 300 includes a central gateway 310 communicatively coupled to a cabin module 320, a telematics module 330, a drive and advanced driver assistance system (ADAS) module 340, a chassis module 350, and a drivetrain module 360. Each component of FIG. 3 may be implemented on separate processors, separate SoC architectures on a single processor, or a combination thereof. Additionally, the elastic computing module 236 described herein can dynamically allocate additional processors to a cloud computing system (e.g., remote services 290) to expand the processing power of a given module.

[0034] The cabin module 320 can handle processing related to, as illustrative and non-limiting examples, BYOD, cluster, displays (main, cluster, HUD, RSE), communication audio, DMS / OMS, door control, e-mirror, entertainment audio, HVAC, infotainment, interior lighting, noise management, seat control, sound amplification, surround view / parking, vehicle sounds (chimes, etc.), etc.

[0035] The telematics module 330 can handle processing related to 4 / 5G connectivity, antennas, Bluetooth / BLE, beam steering, C-V2X, e-Call, electronic toll collection, firewall(s), GNSS, OTA gateway, Wi-Fi, etc., as illustrative and non-limiting examples.

[0036] The Drive & ADAS module 340 can handle, as illustrative and non-limiting examples, front-facing camera, short / long range radar, e-mirror, and processing related to ADAS such as DMS / OMS, auto parking, highway pilot, collision avoidance driving assistance, intelligent intersection negotiation, surround view / parking, etc.

[0037] The chassis module 350 may handle processing related to airbag control, exterior lighting, power steering, stability control, suspension, tire pressure monitoring, turn signals, windshield wiper control, etc., as illustrative and non-limiting examples.

[0038] The drivetrain module 360 ​​may handle processing related to battery and fuel management, braking, engine / motor control, traction control, and transmission control, as illustrative and non-limiting examples.

[0039] Thus, the software processing can be partitioned according to domains, such that domain-specific processing is performed by one or more modules as described above. The arrangement of modules can be dynamically changed depending on processing resources and needs. Furthermore, the hardware implementation of the modules can vary with different embodiments, as shown in Figures 4-6.

[0040] 4 is a block diagram 400 of a computing cluster approach with a single processor in accordance with one or more embodiments of the present disclosure. Multiple display devices 402, speakers 404, microphones 406, sensors 408, and actuators 410 may be communicatively coupled to a processor 430. The processor 430 may include two or more SoC architectures, such as a SoC 432 and a SoC 434. One or more modules described above with respect to FIG. 3 may be implemented in the SoC 432, while other modules may be implemented in the SoC 434.

[0041] 5 is a block diagram 500 of a computing cluster approach with multiple processors, including processor 530 and processor 540, in accordance with one or more embodiments of the present disclosure. Rather than a single processor with multiple SoCs (e.g., processor 430 with SoCs 432 and 434), processor 530 includes one or more SoCs 532, while processor 540 includes one or more SoCs 542. Both processors 530 and 540 may be physically installed in vehicle 202, for example, and may be communicatively coupled via a Peripheral Component Interconnect Express (PCIe) or similar backplane 550 that provides a high-speed interface between processors 530 and 540.

[0042] As another example, Figure 6 is a block diagram 600 of a computing cluster approach including multiple processors 630 and 640 coupled by a network 650 in accordance with one or more embodiments of the present disclosure. Similar to the approach shown in Figure 5, processor 630 includes one or more SoCs 632, while processor 640 includes one or more SoCs 642. Network 650 may include a multi-gigabit Ethernet connection, thereby providing a high-speed interface between processors 630 and 640.

[0043] FIG. 7 is a block diagram of an elastic computing architecture 700 for in-vehicle processing, according to one or more embodiments of the present disclosure. A number of software applications and services are shown in a software layer 710. An elastic computing layer 720, which may include the elastic computing module 236 described above with respect to FIG. 2, facilitates the execution of the software applications and services of the software layer 710 by one or more components of the hardware layer. The hardware layer includes a number of computing devices 730 physically installed in the vehicle, including, as illustrative examples, a number of CPU cores, a number of GPU cores, a number of NPU cores, a number of TEEs, a number of DSP cores, and a number of memories. The hardware layer further includes a number of peripheral devices 740 physically installed in the vehicle, such as displays, microphones, speakers, sensors, and actuators. The hardware layer further includes a number of network and cloud computing devices 750, including, as illustrative and non-limiting examples, a number of CPU cores, a number of GPU cores, a number of NPU cores, a number of memories, and a number of content.

[0044] The Elastic Computing layer 720 understands the parameters of the in-vehicle hardware such as the SoC to which the peripherals are connected, bus speed, battery level, temperature, etc. The Elastic Computing layer 720 further understands the parameters of the edge and cloud devices such as compute power and memory capacity, edge-to-edge latency, cost model, etc. The Elastic Computing layer 720 further understands the needs of each software component in the Software layer 710 such as compute bandwidth, memory, I / O, latency tolerance, safety, security, etc.

[0045] The elastic computing layer 720 determines what runs on the in-vehicle computing devices 730 and what runs on the in-cloud cloud computing devices 750. The elastic computing layer 720 dynamically allocates computing resources of the hardware layer, including the in-vehicle computing devices 730 and the cloud computing devices 750, to deterministically meet the software needs of the software layer 710 and provide load balancing across the system.

[0046] The elastic computing layer 720 further establishes a guest environment for software running in the vehicle and controls access to shared peripherals 740 .

[0047] 8 is a block diagram 800 illustrating partitioning of electronics with separate controllers according to one or more embodiments of the present disclosure. The vehicle modules can include one or more domain controllers 810, such as those described above with respect to FIG. 3. The domain controllers 810 can be grouped by functional affinity and are responsible for high-level functions. The domain controllers integrate core software, control, and user experience.

[0048] Additionally, multiple zone controllers 820 may be distributed throughout the vehicle and grouped by spatial synergy. A zone controller 820 may be responsible for, for example, local sensor management and actuation, as well as power management. Splitting the electronics as shown in FIG. 8 facilitates hardware-to-software migration, optimizes cable harnesses, data sharing, function fusion, provides a single point of decision making, and simplifies configuration management, layering, and upgrades.

[0049] 9A-9C illustrate various aspects of an elastic computing architecture for on-board processing of an exemplary vehicle, an on-board interface system of an exemplary vehicle, and an architecture for domain-based partitioning of software processing of an exemplary vehicle, as discussed herein. Based on FIG. 9A, the elastic computing architecture for on-board processing 902 includes an elastic computing tier 974 that can allocate processing of software applications to local and remote computing resources, in various embodiments. Based on FIG. 9B, the on-board interface system 920 of the vehicle 904 can include an elastic computing module 926 that can implement the elastic computing tier 974. Further, based on FIG. 9C, the elastic computing module 926 can partition software applications according to domains (e.g., domains of the architecture for domain-based partitioning of software processing 906) and allocate processing of the software applications according to partitions. (Elements of FIGS. 9A-9C that have the same names as elements of other figures may be substantially similar to those elements and may function or operate in a substantially similar manner, without being limited to operating or functioning in such manner.)

[0050] 9A , the elastic computing architecture 902 includes a software layer, a hardware layer, and an elastic computing layer 974. The software layer includes one or more software applications and / or software services 972 (e.g., a first software application and / or service, a second software application and / or service, a third software application and / or service, etc., up to an Nth software application and / or service). The hardware layer includes one or more local computing devices 976 (e.g., a first computing device through an Nth computing device), one or more remote computing devices 978 (e.g., a first computing device through an Nth computing device), and one or more local peripheral devices 980 (e.g., a first peripheral device through an Nth peripheral device).

[0051] Local computing device 976 may include various computing resources that are physically installed, physically incorporated, and / or physically located on vehicle 904. Remote computing device 978 may include various computing resources that are not physically installed, physically incorporated, and / or located remotely from vehicle 904.

[0052] Thus, the local computing resources of elastic computing architecture 902 may include local computing devices 976, while the remote computing resources of elastic computing architecture 902 may include remote computing devices 978. Each of the local and remote computing resources of elastic computing architecture 902 may include, for example, one or more cores (e.g., processor cores such as CPU cores, GPU cores, NPU cores, DSP cores, etc.), a TEE, and / or memory.

[0053] Local peripherals 980 may include various peripherals that are physically installed, physically integrated, and / or physically located on vehicle 904. Local peripherals may include various input and / or output devices, such as displays, microphones, speakers, sensors, and / or actuators.

[0054] The elastic computing layer 974 may be communicatively coupled to local computing resources (e.g., local computing devices 976) via wired communications links or wireless communications links local to the vehicle 904. The elastic computing layer 974 may also be communicatively coupled to remote computing resources (e.g., remote computing devices 978) via wireless communications links and / or networks that extend to remote locations.

[0055] The elastic computing layer 974 can determine and / or understand various processing requirements and / or needs of the software applications and / or services 972. These may relate to computational bandwidth, memory, I / O, latency tolerance, safety, security, etc. The elastic computing layer 974 can also determine and / or understand one or more parameters of the local computing devices 976, such as their computational capabilities and / or memory capacity, the SoC to which various peripherals are connected, bus speeds, battery levels, temperatures, etc. Similarly, the elastic computing layer 974 can determine and / or understand one or more parameters of the remote computing devices 978, such as their computational capabilities and / or memory capacity, their edge-to-edge latency, their cost models, etc.

[0056] The elastic computing layer 974 can then facilitate the execution of one or more software applications and / or software services 972 by allocating their processing among one or more local computing resources (e.g., local computing devices 976) and / or one or more remote computing devices 978 (e.g., remote computing devices 978). The allocation can be performed to best meet the various processing requirements and / or needs of the software applications and / or software services 972. The allocation may also be performed to best meet load balancing objectives (e.g., between local and remote loads). The allocation can be dynamic and can change according to changes in the processing requirements of the software applications and / or services 972, parameters and / or availability of the local computing resources, and parameters and / or availability of the remote computing device resources. The allocation can also be deterministic.

[0057] 9B , on the other hand, the in-vehicle interface system 920 of the vehicle 904 (which may be located and / or integrated within the vehicle 904) includes one or more processors 922 and one or more memories 924, in addition to an elastic computing module 926. Similarly, one or more remote services, which may be communicatively coupled to the vehicle 904 (e.g., via a wireless network), may include one or more processors and one or more memories.

[0058] Thus, the local computing resources of the in-vehicle interface system 920 may include a processor 922 and a memory 924, while the remote computing resources of the in-vehicle interface system 920 may include a processor and memory of a remote service. Each processor 922 and / or processor of a remote service may comprise one or more SoCs (similar to the processors of FIGS. 4-6, such as processor 530). In various embodiments, each SoC may in turn have one or more processor cores.

[0059] The elastic computing module 926 may be communicatively coupled to computing resources local to the vehicle 904 (e.g., processors 922 and / or memory 924) via either a wired or wireless communication link that is local to the vehicle 904. The elastic computing layer 974 may also be communicatively coupled to remote computing resources (e.g., processors and / or memory of a remote server) via a wireless communication link that extends to a remote location (e.g., via a wireless network). In some embodiments, two or more of the processors 922 may be communicatively coupled to each other via a high-speed interface (e.g., PCIe, or multi-gigabit Ethernet connection).

[0060] The elastic computing module 926 can determine and / or understand various processing requirements and / or needs of the software components (e.g., of the in-vehicle interface system 920). These may relate to computational bandwidth, memory, I / O, latency tolerance, safety, security, etc. The elastic computing module 926 can also determine and / or evaluate various parameters related to local computing resources, such as the computational power and memory capacity of the processor 922 and memory 924, the SoC architecture of the processor 922 (to which in-vehicle peripherals may be connected), bus speed, battery level, temperature, etc. Similarly, the elastic computing module 926 can also determine and / or evaluate various parameters of remote computing resources, such as the computational power and memory capacity of the processor and memory of the remote service, edge-to-edge latency, cost model, etc.

[0061] The elastic computing module 926 can then allocate the processing of the software components among one or more local computing resources (e.g., processor 922 and / or memory 924) and / or one or more remote computing resources (e.g., processor and / or memory of a remote service). The allocation may be performed to best meet the various processing requirements and / or needs of the software components. The allocation may also be performed to best meet load balancing objectives (e.g., between local and remote loads). The allocation may be dynamic and may change according to changes in the processing requirements of the software components, parameters and / or availability of local computing resources, and parameters and / or availability of remote computing device resources. The allocation may also be deterministic.

[0062] 9C , an architecture 906 for domain-based partitioning of software processing may include a central gateway 930 and one or more domains (e.g., a first domain 932, a second domain 934, a third domain 936, etc., up to an Nth domain 938) into which software for the vehicle 904 may be partitioned. The domains of the architecture 906 may reflect functional affinity groupings, may reflect high-level functional responsibilities, and / or may alternatively reflect various portions or aspects of the vehicle 904. For example, the various domains may be substantially similar to the domains of the cabin module 320, the telematics module 330, the drive and ADAS module 340, the chassis module 350, and / or the drivetrain module 360 ​​of FIG. 3 .

[0063] Furthermore, processing of the various domains may be assigned to different computing resources. Processing for one or more of the domains may be assigned to a single processor, a single SoC within a processor, and / or a single processor core within a processor and / or SoC. Alternatively, processing of multiple domains may be assigned to separate processors, separate SoCs within a processor, or separate cores within a processor and / or SoC. In various embodiments, processing of the various domains may be assigned in various combinations of the above.

[0064] Thus, the elastic computing module 926 can partition the software processing of the vehicle 904 according to various domains, such that domain-specific processing is assigned to different sets of computing resources. The computing resources assigned to process the domains can vary between different embodiments. In various embodiments, the allocation of computing resources can be related to the processing requirements and / or needs of the software, such as computational bandwidth, memory, I / O, latency tolerance, safety, security, etc. For example, in some embodiments, the allocation of computing resources can be related to safety parameters (e.g., Automotive Safety Integrity Level (ASIL) level) required by the software. In some embodiments, the computing resources can be assigned to the computing resources according to domain controllers and zone controllers as discussed herein (e.g., with respect to FIG. 8).

[0065] Furthermore, the division of domains and / or the allocation of underlying computing resources may be dynamic and may change according to changes in software processing requirements, local computing resource parameters and / or availability, and remote computing device resource parameters and / or availability, and the processing power allocated to the various domains may be scaled accordingly.

[0066] 9A to 9C, the elastic computing module 926 may receive processing parameters associated with the computing resources from the computing resources. The elastic computing module 926 may also establish control signaling for the computing resources.

[0067] In some embodiments, the elastic computing module 926 can allocate software processing to a single SoC with multiple cores. For some embodiments, the elastic computing module 926 can allocate software processing to multiple SoCs (any of which may have one or more cores). In various embodiments, the elastic computing module 926 can allocate software processing to various combinations of a single SoC with one or more cores and / or multiple SoCs with one or more cores. In embodiments in which the elastic computing module 926 allocates software processing to multiple SoCs, the SoCs may be communicatively coupled via an interconnect (which may be, for example, a cache coherent interconnect, a PCIE interconnect, an Ethernet interconnect, etc.).

[0068] In some embodiments, the elastic computing module 926 may have access to clocking units, power supply units, and / or thermal management units for the computing resources. For example, the elastic computing module 926 may have access to dedicated mechanisms for separately adjusting the voltage, power gating, clocking, and clock gating of one or more processing cores. The elastic computing module 926 may also have access to fuse voltage values ​​that correspond to ranges of operating performance points of various computing resources, for example. In some embodiments, the elastic computing module 926 may have access to mechanisms that support dynamic voltage and frequency scaling and / or adaptive voltage scaling. In various embodiments, the elastic computing module 926 may be able to read operating temperatures from one or more cores, read average current and / or power dissipation of the computing engine, and / or read peak current and / or power dissipation of the computing engine.

[0069] For various embodiments, the elastic computing module 926 can read performance counters and / or load counters of one or more computing engines (e.g., processors, cores, and / or SoCs). The performance counters and / or load counters can distinguish the software (e.g., source, application, and / or task) generating the counter metrics. In various embodiments, the elastic computing module 926 can read read traffic counters and / or write traffic counters for one or more interconnects. The read traffic counters and / or write traffic counters may clearly distinguish the software (e.g., source and application) generating the traffic.

[0070] For some embodiments, the elastic computing module 926 can dynamically change the operating performance point of memory computing resources (such as dynamic random access memory (DRAM)) in response to factors such as system load and software demands on memory bandwidth. In some embodiments, the elastic computing module 926 can take into account currently available throughput based on parameters such as memory temperature, memory refresh rate, and / or memory throughput (e.g., captured by a counter).

[0071] In various embodiments, the elastic computing module 926 can prioritize various tasks (e.g., software processes) and / or support the specification or definition of guaranteed execution times based on the priorities. In some embodiments, if the execution time of a high priority task is critical, the elastic computing module 926 may suspend lower priority tasks (e.g., by deallocating computing resources assigned to them) to ensure execution of the higher priority task (e.g., after a predetermined time). If it is possible to execute the higher priority task within the predetermined time, the elastic computing module 926 may not suspend the lower priority task.

[0072] In various embodiments, the elastic computing module 926 can dynamically allocate and / or partition computing resources (e.g., as discussed herein) and can also define memory space regions for dedicated partitions or domains. This can advantageously facilitate and / or ensure domain isolation (e.g., freedom from interference), which in turn can facilitate and / or ensure, for example, safety-related software requirements. To support software safety requirements (such as relatively high ASIL level requirements), in some embodiments, the elastic computing module 926 can deallocate computing resources (e.g., processing cores) allocated to software applications, run one or more on-device tests (e.g., logic built-in self-test (LBIST) and / or other tests) to determine whether there are detectable issues with the computing resources, and if there are no issues, reallocate the computing resources to the software applications.

[0073] For some embodiments, the elastic computing module 926 may have access to counters for computing resources (e.g., processing cores) that indicate the available time or availability of the computing resources. The elastic computing module 926 may take this data into account when allocating software processing to various computing resources (e.g., based on the actual resource availability within the computing resources).

[0074] In some embodiments, the elastic computing module 926 can access (e.g., via counters or performance monitors) data regarding latency within the SoC and / or one or more paths within the SoC. The elastic computing module 926 can also access (e.g., via counters or performance monitors) data regarding latency on various interfaces (e.g., cache coherent interconnect interfaces, PCIe interfaces, Ethernet interfaces, etc.).

[0075] Thus, in various embodiments, the elastic computing module 926 may have access to a wide variety of data and / or control mechanisms for allocating software processing among various computing resources. For some embodiments, the elastic computing module 926 may use a neural network that can then recognize people within the vehicle 904, observe the state and / or behavior of the driver and / or one or more passengers, and use machine learning to predict in advance how various users may want to use the system.

[0076] FIG. 10 illustrates an example method 1000 for in-vehicle elastic computing. The method 1000 may include a first determination 1010, a second determination 1020, a first allocation 1030, and a second allocation 1040. In the first determination 1010, a first partition may be determined for a first computing device physically located in the vehicle, the first partition being for a first domain. In the second determination 1020, a second partition may be determined for a second computing device, the second partition being for a second domain. In the first allocation 1030, processing of a first set of software applications associated with the first domain may be assigned to the first computing device. In the second allocation 1040, processing of a second set of software applications associated with the second domain may be assigned to the second computing device.

[0077] In some embodiments, the second computing device may be a remote computing device. For some embodiments, the first domain may encompass a first safety category and the second domain may encompass a second safety category. For some embodiments, the first computing device may include a first SoC and the second computing device may include a second SoC. For some embodiments, the first domain may encompass one or more chassis functions, or one or more drivetrain functions, or both. In various embodiments, the first computing device and / or the second computing device may include one or more CPUs, one or more GPUs, one or more NPUs, one or more DSPs, and / or one or more memory devices.

[0078] In various embodiments, processing of a software application may be allocated to either a first computing device or a second computing device based on required safety parameters of the software application, one or more processing parameters of the first computing device, and one or more processing parameters of the second computing device. For some embodiments, the first set of processing parameters and / or the second set of processing parameters may include computing power and / or memory capacity.

[0079] For various embodiments, an elastic computing module as disclosed herein may be configured to perform various portions of method 1000 and / or various methods disclosed herein. In some embodiments, the elastic computing module may be configured to establish a guest environment for a guest operator of the vehicle to access software applications with limited access. For some embodiments, the elastic computing module may be configured to control access to one or more peripheral devices.

[0080] In various embodiments, the elastic computing module 926 may be configurable to perform some or all of the various methods disclosed herein. In some embodiments, the elastic computing module 926 may include custom developed circuitry (e.g., application specific integrated circuit (ASIC) components and / or field programmable gate array (FPGA) devices). In some embodiments, the elastic computing module 926 may comprise one or more processors and memory for holding executable instructions that, when executed, cause the one or more processors to perform some or all of the methods disclosed herein. For some exemplary embodiments, the elastic computing module 926 may be at least partially implemented by the processor 922 and / or the memory 924.

[0081] An elastic computing layer and / or elastic computing modules as discussed herein can advantageously distribute software processing among computing resources in a dynamic and adaptive manner. This in turn advantageously promotes system resource consolidation, processing flexibility, reduced system costs, and optimization of system output for various metrics (performance, energy usage, minimization of component aging, etc.). These advantages can be independent of the details of the software and / or hardware implementation.

[0082] In a first approach to the methods and systems discussed herein, a first example of a system for controlling a vehicle includes a first computing device physically located within the vehicle, a second computing device located remotely from the vehicle, and an elastic computing module communicatively coupled to the first computing device and the second computing device, the elastic computing module configured to: determine computing power and memory capacity of the first computing device and the second computing device, determine software requirements of a software application for controlling components of the vehicle, and dynamically allocate processing of the software application to the first computing device and / or the second computing device based on the computing power and memory capacity of the first computing device and the second computing device and the software requirements of the software application. Reconstructing the first example, in a second example of the system, the first computing device includes one or more of a plurality of CPUs, a plurality of GPUs, a plurality of NPUs, a plurality of DSPs, and a plurality of memory devices. Reconstructing the second example, in a third example of the system, the second computing device comprises one or more of a second plurality of CPUs, a second plurality of GPUs, a second plurality of NPUs, and a second plurality of memory devices. Reconstructing any of the first through third examples, in a fourth example of the system, the elastic computing module is further configured to establish a guest environment for a guest operator of the vehicle to access the software application with restricted access. Reconstructing any of the first through fourth examples, a fifth example of the system further includes a plurality of peripheral devices, and the elastic computing module is further configured to control access to one or more of the plurality of peripheral devices.Reconstructing any of the first through fifth examples, in a sixth example of the system, the software application includes a plurality of software applications, the elastic computing module partitions the plurality of software applications according to the domain of each software application, and the elastic computing module allocates processing of each software application according to the partitions of the plurality of software applications.

[0083] In a second approach to the methods and systems discussed herein, a first example of an in-vehicle interface system includes one or more communication links configured to communicatively couple to a first local computing device, a second local computing device, or both, and an elastic computing module communicatively configured to couple to the first local computing device and the second local computing device, the elastic computing module configured to: determine a first set of processing parameters for the first local computing device and a second set of processing parameters for the second local computing device, establish required safety parameters of a software application of the vehicle, and allocate processing of the software application between the first local computing device and the second local computing device to meet the required safety parameters of the software application based on the first set of processing parameters and the second set of processing parameters. Reconstructing the first example, in a second example of an in-vehicle interface system, the first set of processing parameters and the second set of processing parameters include at least one of a computing power and a memory capacity. Reconstructing either the first or second example, a third example of an in-vehicle interface system further includes a first SoC and a second SoC, the first local computing device includes the first SoC, and the second local computing device includes the second SoC. Reconstructing either the first through third examples, a fourth example of an in-vehicle interface system is implemented with a first processing partition of the system to include the first device, and a second processing partition of the system to include the second device. Reconstructing the fourth example, a fifth example of an in-vehicle interface system is implemented with a first processing partition in the system's first SoC, and a second processing partition in the system's second SoC.Reconstructing either the fourth or fifth examples, in a sixth example of the in-vehicle interface system, the first processing partition handles processing related to one or more chassis functions, or one or more drivetrain functions, or both. Reconstructing the sixth example, in a seventh example of the in-vehicle interface system of claim 6, the first processing partition is associated with a first safety class and the second processing partition is associated with a second safety class. Reconstructing any of the first through seventh examples, in an eighth example of the in-vehicle interface system, the communication link is configured to communicatively couple to a first local computing device, and the in-vehicle interface system further comprises a second communication link configured to communicatively couple to a second local computing device. Reconstructing any of the first to eighth examples, in a ninth example of an in-vehicle interface system described in any of claims 1 to 8, the in-vehicle interface system further comprises an additional communication link configured to communicatively couple to a remote computing device, and the elastic computing module is further configured to determine a third set of processing parameters of the remote computing device, establish required safety parameters of an additional software application for the vehicle, and allocate processing of the software application among the first local computing device, the second local computing device, and the remote computing device to meet the required safety parameters of the software application based on the first set of processing parameters, the second set of processing parameters, and the third set of processing parameters.

[0084] In a third approach to the methods and systems discussed herein, a first example of a method for in-vehicle elastic computing includes determining a first partition for a first computing device physically located in a vehicle, the first partition being for a first domain, determining a second partition for a second computing device, the second partition being for a second domain, and allocating a first set of processing of software applications associated with the first domain to the first computing device, and allocating a second set of processing of software applications associated with the second domain to the second computing device. Reconstructing the first example, in a second example of a method for in-vehicle elastic computing, the second computing device is a remote computing device. Reconstructing either the first example or the second example, in a third example of a method for in-vehicle elastic computing, the first domain encompasses a first safety category and the second domain encompasses a second safety category. Reconstructing any of the first through third examples, in a fourth example of a method for in-vehicle elastic computing, the first computing device includes a first SoC and the second computing device includes a second SoC. Reconstructing any of the first through fourth examples, in a fifth example of a method for in-vehicle elastic computing, the first domain encompasses one or more chassis functions, or one or more drivetrain functions, or both.

[0085] The description of the embodiments has been presented for purposes of illustration and description. Suitable modifications and variations to the embodiments may be implemented in light of the above description or may be acquired from practicing the methods. For example, unless otherwise stated, one or more of the methods described above may be implemented by a suitable device and / or combination of devices, such as the vehicle system and cloud computing system described above in connection with Figures 1 to 9C. The methods may be implemented by executing stored instructions using one or more logic devices (e.g., processors) in combination with one or more hardware elements, such as storage devices, memories, hardware network interfaces / antennas, switches, actuators, clock circuits, etc. The described methods and related acts may also be performed in various orders, in parallel, and / or simultaneously in addition to the order described in this application. The described systems are exemplary in nature and may include additional elements and / or omit elements. The inventive subject matter of the present disclosure includes all novel and non-obvious combinations and subcombinations of the various systems and configurations and other features, functions, and / or properties disclosed.

[0086] As used in this application, an element or step preceded by the word "a" or "an" in the singular is to be understood as not excluding a plurality of such elements or steps, unless the exclusion is expressly stated. Moreover, references to "one embodiment" or "one example" of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. The terms "first," "second," and "third," etc. are used merely as labels and are not intended to impose numerical requirements or a particular positional order on those objects. The following claims specifically point to subject matter from the above disclosure that is believed to be new and unobvious.

Claims

1. 1. A system for controlling a vehicle, comprising: a first computing device physically located within the vehicle; a second computing device located remotely from the vehicle; and an elastic computing module communicatively coupled to the first computing device and the second computing device, the elastic computing module comprising: determining the computational capabilities and memory capacities of the first computing device and the second computing device; determining software requirements for a software application for controlling components of the vehicle; dynamically allocating processing of the software application to the first computing device and / or the second computing device based on the computational power and the memory capacity of the first computing device and the second computing device and the software requirements of the software application; establishing a guest environment for a guest operator of the vehicle to access the software application with limited access; an elastic computing module configured to: Equipped with the software application includes a plurality of software applications; the elastic computing module categorizes the plurality of software applications into partitions according to a domain of each software application, the domain being a function of the vehicle controlled by each software application; The elastic computing module allocates processing of each software application according to the partitions of the plurality of software applications.

2. 2. The system of claim 1, wherein the first computing device comprises one or more of a plurality of central processing units (CPUs), a plurality of graphics processing units (GPUs), a plurality of neural processing units (NPUs), a plurality of digital signal processors (DSPs), and a plurality of memory devices.

3. 3. The system of claim 2, wherein the second computing device comprises one or more of a second plurality of CPUs, a second plurality of GPUs, a second plurality of NPUs, and a second plurality of memory devices.

4. 1. A system for controlling a vehicle, comprising: a first computing device physically located within the vehicle; a second computing device located remotely from the vehicle; and an elastic computing module communicatively coupled to the first computing device and the second computing device, the elastic computing module comprising: determining the computational capabilities and memory capacities of the first computing device and the second computing device; determining software requirements for a software application for controlling components of the vehicle; dynamically allocating processing of the software application to the first computing device and / or the second computing device based on the computational power and the memory capacity of the first computing device and the second computing device and the software requirements of the software application; establishing a guest environment for a guest operator of the vehicle to access the software application with limited access; an elastic computing module configured to: A system comprising:

5. Further comprising a plurality of peripheral devices; The system of claim 1 , wherein the elastic computing module is further configured to control access to one or more peripheral devices of the plurality of peripheral devices.

6. An in-vehicle interface system, one or more communication links configured to communicatively couple to the first local computing device, the second local computing device, or both; an elastic computing module communicatively configured to couple to the first local computing device and the second local computing device, the elastic computing module comprising: determining a first set of processing parameters for the first local computing device and a second set of processing parameters for the second local computing device; Establishing required safety parameters for a vehicle software application; allocating processing of the software application between the first local computing device and the second local computing device to meet the required safety parameters of the software application based on the first set of processing parameters and the second set of processing parameters; establishing a guest environment for a guest operator of the vehicle to access the software application with limited access; an elastic computing module configured to: Equipped with the software application includes a plurality of software applications; the elastic computing module categorizes the plurality of software applications into partitions according to a domain of each software application, the domain being a function of the vehicle controlled by each software application; The elastic computing module further allocates processing of each software application according to the partitions of the plurality of software applications.

7. The in-vehicle interface system of claim 6 , wherein the first set of processing parameters and the second set of processing parameters include at least one of a computing power and a memory capacity.

8. Further comprising a first system on chip (SoC) and a second SoC; the first local computing device includes the first SoC; The in-vehicle interface system of claim 6 , wherein the second local computing device includes the second SoC.

9. a first processing partition of the system is implemented to include a first device; The in-vehicle interface system of claim 6 , wherein a second processing partition of the system is implemented to include a second device.

10. the first processing partition is implemented in a first system-on-chip (SoC) of the system; 10. The in-vehicle interface system of claim 9, wherein the second processing partition is implemented on a second SoC of the system.

11. The in-vehicle interface system of claim 9 , wherein the first processing partition handles processing related to one or more chassis functions, or one or more drivetrain functions, or both.

12. the first processing partition is associated with a first safety class; The in-vehicle interface system of claim 11 , wherein the second processing partition is associated with a second safety class.

13. the communication link is configured to communicatively couple to the first local computing device; The in-vehicle interface system of claim 6 , further comprising a second communications link configured to communicatively couple to the second local computing device.

14. the in-vehicle interface system further comprising an additional communication link configured to communicatively couple to a remote computing device; The elastic computing module includes: determining a third set of processing parameters for the remote computing device; and establishing required safety parameters of additional software applications for the vehicle; allocating processing of the software application among the first local computing device, the second local computing device, and the remote computing device to meet the required safety parameters of the software application based on the first set of processing parameters, the second set of processing parameters, and the third set of processing parameters; The in-vehicle interface system of claim 6 , further configured to:

15. 1. A method for in-vehicle elastic computing, comprising: determining a first category for a first computing device physically located within a vehicle, the first category being for a first function of the vehicle; determining a second category for a second computing device, the second category being for a second function of the vehicle; and assigning to the first computing device the processing of a first set of software applications associated with the first function of the vehicle; allocating processing of a second set of software applications associated with the second function of the vehicle to the second computing device; establishing a guest environment for a guest operator of the vehicle to access the software application with limited access; Including, the software application includes a plurality of software applications; A method for in-vehicle elastic computing, wherein an elastic computing module allocates processing of each software application according to a category of the functionality of the vehicle controlled by the plurality of software applications.

16. The method for in-vehicle elastic computing of claim 15 , wherein the second computing device is a remote computing device.

17. the first function of the vehicle comprises a first safety category; The method for in-vehicle elastic computing of claim 15 , wherein the second functionality of the vehicle comprises a second safety category.

18. the first computing device includes a first system on chip (SoC); The method for in-vehicle elastic computing of claim 15 , wherein the second computing device comprises a second SoC.

19. 20. The method for in-vehicle elastic computing of claim 15, wherein the first functionality of the vehicle encompasses one or more chassis functionality, or one or more drivetrain functionality, or both.

Citation Information

Patent Citations

  • Vehicle controller

    JP2014193690A

  • Vehicle software allocation system

    JP2017171114A

  • Vehicles with multiple user interface operating domains

    JP2017507398A

  • Device, system and method for processing data

    WO2018193439A1