AUTOSAR in Indian EVs: Scaling Software Across 2W, 3W, LCV and Passenger Platforms

India’s EV market crossed 2 million units in CY2024: e-2W at 1.14 million (up 33%), e-3W at 691,323 (up 18%), electric passenger vehicles at 99,068 (up 20%), and commercial EVs doubling to 10,051 units (JMK Research, 2024). Embedded software is now the primary competitive differentiator across all four segments. Global OEMs spent approximately EUR 40 billion on automotive software in 2024, up 50% from 2021, while software complexity grew 4x faster than development productivity. For Indian OEMs scaling across four distinct vehicle segments, AUTOSAR is the standard that converts that complexity into a structured, reusable, and regulation-aligned foundation.

AUTOSAR Classic and Adaptive: The Right Tool for Each Domain

AUTOSAR is not a single platform. It is two complementary standards designed for different computing domains within the same vehicle.

AUTOSAR Classic Platform (CP) targets deeply embedded, real-time ECUs: BMS, motor controllers, braking systems, and body control modules. Its statically configured layered architecture (BSW, RTE, Application Layer) provides hard real-time scheduling and native ISO 26262 support. For India’s high-volume 2W, 3W, and LCV segments, Classic is the production-proven choice for cost-sensitive microcontrollers.

AUTOSAR Adaptive Platform (AP), introduced in 2017, targets High Performance Computing units running POSIX-based operating systems. Its Service-Oriented Architecture enables dynamic service discovery, OTA updates, and cloud connectivity via SOME/IP and DDS. For India’s growing passenger EV segment, where platforms like the Tata Nexon EV and Mahindra BE.06 incorporate ADAS and multi-domain HPCs, Adaptive is the SDV-era middleware that makes these capabilities possible.

In practice, CP and AP coexist. Safety-critical real-time functions run on Classic ECUs connected via CAN or LIN, while Adaptive HPCs handle ADAS, infotainment, and connectivity over Ethernet. Gateway ECUs translate between the two domains. The latest AUTOSAR release, R25-11 (December 2025), introduced the Automotive API Gateway based on the VISS protocol, further expanding connectivity between in-vehicle and external cloud services across both platforms.

What AUTOSAR Delivers Across India’s EV Segments

Each segment has a distinct software profile, and AUTOSAR addresses each differently:

• Electric 2W: Cost and efficiency dominate. AUTOSAR Classic’s scalable BSW allows OEMs to deploy only the modules required, keeping ECU resource consumption low while maintaining standards-compliant diagnostics and communication stacks across scooter and motorcycle platforms.
• Electric 3W: Fleet operators managing hundreds of cargo and passenger vehicles need remote diagnostics and OTA software updates. AUTOSAR Classic provides the structured UDS diagnostic and communication stack that enables remote health monitoring and over-the-air patches, protecting fleet uptime and daily revenue.
• LCV: Commercial EVs require functional safety compliance and J1939 interoperability for fleet telematics. AUTOSAR Classic’s ISO 26262 alignment and standardised communication stack make it the natural architecture for LCV BMS and motor controller ECUs. Commercial EV sales doubled to 10,051 units in 2024, making scalable software architecture a near-term priority.
• Passenger Vehicles: As Indian passenger EVs add ADAS features and multi-domain HPCs, AUTOSAR Adaptive is the enabling middleware. Its SOA model allows OEMs to update and extend software services post-delivery, supporting continuous improvement. AUTOSAR Adaptive Platform membership grew 22% in the past year, validating its rapid adoption trajectory.

Practical Benefits of AUTOSAR for Indian EV Platforms

Across all four segments, four benefits consistently define the AUTOSAR investment case:

1. Cross-Platform Software Reuse

AUTOSAR Classic’s layered architecture allows diagnostic, communication, and safety stacks to be reused across ECUs and vehicle lines with minimal rework. An OEM building both a 2W scooter and a 3W cargo vehicle reuses the same UDS and communication modules across both programs, cutting time-to-market and engineering costs.

ElectRay’s AUTOSAR-compliant UDS Stack and OBDonUDS Stack are production-ready components built for exactly this cross-platform reuse, with proven deployments across 2W, 3W, LCV, and passenger ECU programs.

2. EV-Specific Diagnostics

Standard OBD diagnostics were never designed for zero-emission powertrains. Indian EV OEMs need diagnostics tailored to battery SoH, motor control, and thermal management.

ElectRay’s eSAR.ZEVonUDS Stack delivers AUTOSAR-compliant EV diagnostics aligned with SAE J1979-3, purpose-built for electric and zero-emission vehicle ECUs across all Indian vehicle segments.

3. Functional Safety and AIS-189/190 Compliance

AUTOSAR Classic natively supports ISO 26262 functional safety compliance, critical for BMS and motor controller programs. As AIS-189 and AIS-190 compliance deadlines approach, AUTOSAR’s standardised BSW and cryptographic stack directly enable the certified software lifecycle these regulations mandate.

ElectRay’s Cybersecurity and Functional Safety engineering services align ECU software with ISO 26262 and ISO/SAE 21434, de-risking ICAT and ARAI homologation across all vehicle segments.

4. OTA Readiness and Secure ECU Programming

AUTOSAR Classic’s standardised communication stacks make OTA integration seamless. For fleet 3W and LCV operators and passenger OEMs deploying connected features, production-grade OTA and secure ECU flashing are operational necessities.

ElectRay’s Secure Flash Bootloader ensures authenticated ECU programming across manufacturing and field environments, while the FOTA Solution enables secure firmware-over-the-air updates, and eConnectX provides real-time vehicle health monitoring, remote diagnostics, and predictive maintenance for Indian EV fleets.

5. Faster ECU Development and Hardware Integration

AUTOSAR also improves ECU development efficiency by separating application software from hardware-specific drivers.

With standardized Basic Software layers and Board Support Packages, OEMs can port the same application logic across different microcontrollers or ECU variants with minimal changes.

This hardware abstraction is particularly valuable for Indian EV programs, where platform variants often evolve rapidly due to cost optimization and supply chain changes.

AUTOSAR and the Software Defined Vehicle Transition

As vehicles evolve toward Software Defined Vehicle (SDV) architectures, software complexity continues to grow.

New EV platforms are beginning to incorporate:

• Centralized vehicle controllers
• High-performance compute units
• Advanced connectivity and telematics systems

In this transition, AUTOSAR Classic continues to support real-time ECU functions such as powertrain control and diagnostics, while AUTOSAR Adaptive increasingly supports high-performance computing domains.

Together, these architectures enable scalable software platforms capable of supporting long vehicle lifecycles and continuous feature updates.

Challenges Worth Planning For

AUTOSAR Classic requires higher initial tooling and engineering investment than bare-metal approaches, and finding trained AUTOSAR engineers remains a skills challenge. For very simple, single-function ECUs, lightweight stacks may offer better cost efficiency. The right choice between Classic, Adaptive, or a hybrid depends on the ECU domain, safety requirements, and lifecycle horizon, and should be resolved at the E/E architecture stage to avoid costly mid-program pivots.

AUTOSAR as a Strategic Foundation

As India’s EV volumes scale and software complexity compounds, the gap between OEMs building on standardised AUTOSAR foundations and those on fragmented proprietary stacks will widen commercially. AUTOSAR Classic and Adaptive, deployed across the right domains, give Indian OEMs the reusability, safety compliance, OTA readiness, and diagnostic depth to compete at scale in a software-defined, regulation-governed market.