Cloud Lambda Deployment for Dynamic Vehicle Function Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies lack the ability to dynamically change vehicle functions via cloud-generated lambda.

Innovation Solution

A method involving accessing cloud applications, generating lambda functions, implementing software services, and transferring these functions to vehicles through a centralized location, utilizing a configuration manager, database manager, trigger manager, and other services to dynamically change vehicle functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional vehicle software update methods are used, then system stability is maintained, but adaptability and speed of deploying new features are limited

Engineering Contradiction:
Improvevehicle function adaptabilityVSAvoiddeployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic function deployment by allowing vehicle software functions to be updated, added, or removed in real-time based on cloud-generated lambda functions. The system transitions from static pre-programmed functionality to dynamic cloud-controlled functionality, enabling rapid adaptation of vehicle behaviors without physical reconfiguration or lengthy update cycles

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent pre-establishes a cloud-based infrastructure with lambda function generation capabilities and vehicle communication protocols before deployment. The cloud system is pre-configured to generate, validate, and transmit function definitions to vehicles, enabling rapid deployment when needed without requiring complex on-vehicle compilation or configuration processes

Inventive Principle:
Principle #10Preliminary action

2Productivity

If cloud-generated lambda functions are implemented, then productivity and deployment speed improve, but system complexity increases

Engineering Contradiction:
Improvefeature deployment efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-based intermediary system that generates lambda functions and manages vehicle function definitions. This cloud intermediary handles the complexity of function compilation, validation, and version management, while vehicles receive simplified function definitions through standardized protocols. The intermediary absorbs architectural complexity away from the vehicle side, enabling high productivity without proportionally increasing on-vehicle system complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a universal cloud-based lambda function generation platform that can deploy multiple types of vehicle functions through a single standardized interface. The system uses common communication protocols and data structures that work across different vehicle models and function types, reducing the need for model-specific complexity while maintaining high deployment efficiency across diverse applications

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20260019784A1Dynamically changing vehicle function via cloud generated lambda
Publication Date: 2026.01.15 GM GLOBAL TECHNOLOGY OPERATIONS LLC
  • US20260019784A1 patent drawing
  • US20260019784A1 patent drawing
  • US20260019784A1 patent drawing

AI summary

A method for dynamically changing functions of a vehicle, or one more vehicles, via cloud generated lambda or a non-transitory computer-readable storage medium on which is recorded instructions, includes: accessing a cloud application, via other communication protocols; generation of the lambda; implementing software services on a server or other remote devices; accessing a database via the cloud application; and transferring the lambda to one or more vehicles. The software services may include other communication protocols; a configuration manager; a database manager; and a trigger manager. The software services may further include a rule manager; a data collector; an action manager; and a status handler. The methods may further include configuration parameters, implemented for the monitoring and execution of the function on the vehicle, services and applications, implemented for the monitoring and execution of the function on the vehicle, or implementing configurations, via the cloud application.