Bayerische Motoren Werke

Description

Within 3GPP technical specifications, specifically in TS 26.938, 'Bayerische Motoren Werke' (BMW) is cited not as a standardized protocol or network function, but as a real-world example of an automotive Original Equipment Manufacturer (OEM). Its inclusion serves a pedagogical and normative purpose, providing a concrete reference point for discussions and requirements related to vehicle-based services and communications. The specification uses this named entity to ground abstract technical discussions in a recognizable industry context, particularly when detailing scenarios for multimedia application performance in vehicular environments, which is the core subject of TS 26.938.

The role of such a reference is to facilitate a common understanding among standardization participants and later among implementers. When defining performance metrics, latency requirements, or data throughput needs for in-vehicle infotainment (IVI), advanced driver-assistance systems (ADAS), or vehicle-to-network (V2N) communication, using a well-known automotive brand like BMW helps contextualize the technical parameters. It answers the 'for whom' aspect, ensuring the developed standards are aligned with the practical capabilities and integration needs of actual vehicle manufacturers. This is crucial for ensuring the resulting 3GPP features are viable for deployment in commercial vehicles.

Architecturally, this reference does not imply a specific BMW-proprietary interface or node within the 3GPP system. Instead, the vehicle, represented by the OEM, is treated as a User Equipment (UE) or a collection of UEs with specific form factors and usage environments. The specification work considers the vehicle's integration point—the onboard unit (OBU) or telematics control unit (TCU)—which houses the 3GPP modem and executes the protocol stack. Key considerations influenced by such OEM examples include antenna placement constraints due to vehicle design, power supply stability from the vehicle's electrical system, thermal operating ranges, and the need for reliable connectivity despite high-speed mobility and varying radio environments.

Therefore, the mention of BMW in 3GPP specs is a methodological tool for requirements engineering. It ensures that the cellular system's design—covering aspects from the Physical Layer waveform design to Core Network service exposure for vehicles—accounts for real automotive integration challenges. This leads to more robust and implementable standards for Cellular Vehicle-to-Everything (C-V2X), network-controlled interactive services for vehicles, and QoS management for mobility, which are foundational for enabling connected and automated driving services.

Purpose & Motivation

The purpose of referencing specific automotive OEMs like BMW in 3GPP specifications is to anchor highly technical system requirements in tangible, real-world deployment scenarios. Abstract network performance figures gain practical significance when associated with a known manufacturer's vehicle platform. This practice was particularly motivated by the industry-driven push for standardized cellular solutions for vehicular communication, which began gaining significant momentum in 3GPP around Release 14 with the standardization of LTE-V2X. Using concrete examples helps bridge the gap between telecommunications engineers and automotive engineers, ensuring the developed standards are not only theoretically sound but also practically integrable into vehicle design and manufacturing processes.

Historically, prior to dedicated C-V2X standards, vehicular communication relied on proprietary solutions or non-cellular technologies like IEEE 802.11p (DSRC), which presented challenges in global scalability, seamless integration with mobile network services, and evolution paths. The inclusion of automotive OEM names in study items and specifications signaled a shift to a more collaborative, cross-industry standardization approach. It addressed the limitation of creating network-centric standards in isolation, without firm consideration of the end-device (the vehicle) constraints and operational profiles. By evoking a specific OEM, the specifications implicitly address problems of device certification, automotive-grade hardware requirements, and the need for predictable service behavior in challenging mobility conditions.

This methodology solves the problem of ambiguous requirements. Instead of stating 'the network shall support low latency for vehicles,' a more contextualized requirement can be framed by considering the needs of an OEM like BMW for a specific use case, such as sensor data sharing for collision avoidance. This drives more precise technical work on protocol timers, scheduling mechanisms, and QoS frameworks. The motivation is ultimately to produce a set of 3GPP standards that automotive OEMs can confidently adopt, knowing their specific operational environments and performance benchmarks have been explicitly considered during the standardization process, thereby accelerating commercial deployment of connected vehicle services.

Key Features

• Serves as a concrete reference for automotive OEM requirements in normative text
• Contextualizes performance metrics for vehicular use cases (e.g., latency, throughput)
• Anchors discussions on in-vehicle network integration and UE form factors
• Facilitates cross-industry understanding between telecom and automotive sectors
• Used to derive real-world scenarios for V2X communication studies
• Helps define channel models and mobility conditions for testing

Evolution Across Releases

Defining Specifications