Aviation Digital Control Systems And Coordination Monopolies

Autonomous Vehicle Platform Competition Regulation

Introduction

Autonomous vehicle platforms combine vehicles, autonomous-driving software, mapping, sensors, cloud infrastructure, vehicle data, charging systems, mobility applications, and digital marketplaces. As these elements become integrated into a single technological ecosystem, competition concerns can arise not merely from control over cars, but from control over the digital infrastructure through which autonomous vehicles operate.

An autonomous vehicle platform may simultaneously function as:

  1. a vehicle manufacturer;
  2. an autonomous-driving software provider;
  3. a mapping/data provider;
  4. a mobility marketplace;
  5. an operating-system or application platform;
  6. a cloud/AI provider;
  7. an infrastructure operator; and
  8. a provider of complementary services such as charging, insurance or maintenance.

This creates a potential ecosystem-dominance problem. A platform that controls one essential layer may use that position to disadvantage competitors operating at another layer.

The European Commission has specifically recognised that access to vehicle-generated data may become an important factor of competition in the motor-vehicle sector.

I. Meaning of Autonomous Vehicle Platform Competition

An autonomous vehicle platform is broader than an autonomous vehicle itself.

It can be represented as:

Vehicle → Sensors → Autonomous Driving Stack → Operating System → Cloud/AI → Maps/Data → Mobility Marketplace → Consumer

Competition can occur at every level.

Examples

A dominant platform could potentially:

  • prevent rival autonomous-driving software from accessing vehicle sensors;
  • restrict access to high-quality vehicle data;
  • favour its own navigation service;
  • make its own charging network preferentially available;
  • impose exclusivity on vehicle manufacturers;
  • tie autonomous-driving software to cloud services;
  • discriminate against competing mobility operators;
  • use data obtained from competitors to improve its own service;
  • restrict interoperability;
  • impose unfair API conditions; or
  • acquire emerging autonomous-driving competitors before they become significant competitors.

The competition-law question is therefore not simply:

"Who sells the most autonomous vehicles?"

It may instead be:

Who controls the technological ecosystem necessary for autonomous vehicles to compete?

II. Relevant Competition-Law Framework

1. Abuse of Dominant Position

Under systems such as Article 102 TFEU and Section 4 of India's Competition Act 2002, dominance becomes particularly important when a platform controls an indispensable technological layer.

Potential abuses include:

  • refusal to supply;
  • discriminatory access;
  • tying and bundling;
  • exclusionary rebates;
  • self-preferencing;
  • discriminatory algorithms;
  • exploitative data practices;
  • interoperability restrictions;
  • predatory pricing; and
  • leveraging dominance from one market into another.

The relevant market may be narrowly defined around a technological service rather than the entire automobile sector.

Possible markets include:

  • autonomous-driving software;
  • autonomous mobility services;
  • vehicle-generated data;
  • digital mapping;
  • vehicle operating systems;
  • autonomous-vehicle cloud services;
  • vehicle-to-cloud connectivity;
  • autonomous fleet-management services.

III. Multi-Sided Platform Markets

Autonomous vehicle platforms are frequently multi-sided markets.

A single platform may connect:

Passengers ↔ Autonomous Vehicles ↔ Fleet Operators ↔ Vehicle Manufacturers ↔ Software Developers ↔ Data Providers

This creates strong network effects.

More vehicles generate more data.

More data improves the autonomous-driving system.

A better autonomous-driving system attracts more users.

More users attract more fleet operators.

More fleet operators generate more data.

This produces a feedback loop:

Users → Vehicles → Data → Better AI → More Users

Competition law must therefore consider whether the platform's advantage is the result of legitimate innovation or whether exclusionary conduct artificially prevents rivals from reaching sufficient scale.

IV. Data as a Competitive Asset

Vehicle-generated data may become one of the most important competitive inputs.

Autonomous vehicles can generate:

  • camera data;
  • LiDAR information;
  • radar data;
  • GPS information;
  • road-condition information;
  • driving behaviour;
  • braking patterns;
  • traffic information;
  • mapping information;
  • maintenance data;
  • sensor-failure information;
  • charging information; and
  • autonomous-driving intervention data.

A dominant platform could therefore obtain an important competitive advantage from controlling a large installed base of vehicles.

The EU has recognised vehicle-generated data as an important competition issue in the motor-vehicle sector.

The competition concern becomes particularly significant where:

Data accumulation → better AI → better autonomy → greater market share → more data

This can create a self-reinforcing competitive advantage.

V. Self-Preferencing

Suppose a company operates:

  • an autonomous-driving platform;
  • a mapping service;
  • a mobility marketplace; and
  • a fleet-management service.

The company could theoretically configure its algorithm so that its own mobility service receives:

  • preferential vehicle allocation;
  • better routing;
  • superior visibility;
  • faster API access;
  • better charging access; or
  • lower platform fees.

This resembles the concerns examined in digital-platform competition cases.

The legal inquiry would generally examine:

  1. whether the platform is dominant;
  2. whether the platform provides an important infrastructure;
  3. whether competitors depend upon access;
  4. whether the platform discriminates between internal and external users;
  5. whether the conduct forecloses competitors; and
  6. whether there are legitimate technical or safety justifications.

VI. Interoperability and API Access

Autonomous vehicles require extensive interaction among:

  • sensors;
  • software;
  • maps;
  • cloud services;
  • charging systems;
  • telecommunications networks;
  • fleet-management platforms; and
  • third-party applications.

A platform owner could restrict interoperability by controlling:

  • APIs;
  • software-development kits;
  • vehicle interfaces;
  • authentication;
  • cloud access;
  • mapping interfaces;
  • data formats;
  • charging interfaces; or
  • safety certification.

A competition regulator may therefore examine whether interoperability restrictions are objectively necessary for cybersecurity and functional safety, or whether they are being used to exclude rivals.

VII. Tying and Bundling

A dominant autonomous-vehicle platform might require customers to purchase several products together.

For example:

Autonomous-driving software + Cloud + Mapping + Insurance + Charging

A manufacturer could theoretically be told:

Access to the autonomous-driving system is available only if the manufacturer also purchases the platform's cloud and mapping services.

This creates a potential tying problem.

The important question is whether the bundle:

  • produces legitimate technical efficiencies;
  • reduces costs;
  • improves safety;
  • prevents cybersecurity vulnerabilities;

or instead:

  • forecloses competitors;
  • raises entry barriers;
  • eliminates interoperability; or
  • transfers dominance from one market to another.

VIII. Exclusive Dealing

An autonomous-driving platform might attempt to obtain exclusive arrangements with vehicle manufacturers.

For example:

Vehicle Manufacturer A → Exclusive autonomous-driving software → Platform X

If Platform X already possesses substantial market power, extensive exclusivity could prevent rival autonomous-driving providers from obtaining sufficient vehicle installations to compete.

The analysis would consider:

  • duration of exclusivity;
  • market coverage;
  • availability of alternative customers;
  • switching costs;
  • network effects;
  • technical compatibility;
  • entry barriers; and
  • actual or likely foreclosure.

IX. Autonomous Vehicle Data Portability

Data portability becomes important because users and manufacturers may become locked into one ecosystem.

Suppose a fleet operator has accumulated years of:

  • route data;
  • vehicle-performance data;
  • maintenance information;
  • charging history;
  • autonomous-driving records.

If that information cannot be transferred to a competing platform, switching costs may become substantial.

The regulatory objective would therefore potentially include:

Interoperability + Data Portability + API Access

The EU's Digital Markets Act illustrates the broader regulatory trend toward data access and portability for certain designated gatekeepers.

X. Six Important Case Laws

Because there are relatively few reported judicial decisions specifically concerning autonomous-vehicle platforms, established digital-platform, technology, essential-facility and mobility cases provide the principal legal analogies.

1. Google LLC & Alphabet Inc. v European Commission — Google Android

Case T-604/18, General Court, 2022

This is particularly relevant to autonomous-vehicle platforms because it concerned a technology ecosystem involving an operating system, applications and a multi-sided platform.

The General Court considered Google's conduct involving:

  • Android;
  • Google Play;
  • Google Search;
  • Chrome;
  • device manufacturers;
  • mobile-network operators;
  • product bundling;
  • exclusivity payments; and
  • anti-fragmentation obligations.

The Court's judgment treated the ecosystem and the interaction between multiple platform layers as relevant to the Article 102 analysis.

Relevance to autonomous vehicles

An autonomous-driving operating system could similarly become the technological gateway through which:

Vehicle → Applications → Mapping → Cloud → Mobility Services

must operate.

The case therefore provides an important analogy for analysing:

  • tying;
  • bundling;
  • ecosystem leverage;
  • contractual restrictions;
  • platform dominance; and
  • exclusionary effects.

2. Bronner v Mediaprint

Case C-7/97, Court of Justice of the European Union

Bronner is fundamental to the law of refusal to supply and essential facilities.

The Court adopted a stringent approach toward requiring a dominant undertaking to provide competitors with access to infrastructure.

Autonomous vehicle relevance

Suppose a dominant company controls an autonomous-driving infrastructure that competitors cannot realistically reproduce.

Examples could include:

  • proprietary vehicle interfaces;
  • indispensable mapping infrastructure;
  • unique vehicle-data infrastructure;
  • autonomous-driving APIs; or
  • critical charging/communication infrastructure.

A regulator would still need to distinguish between:

ordinary proprietary technology

and

infrastructure whose denial of access can satisfy the stringent conditions applicable to compulsory access.

Thus, autonomous-vehicle regulation should not automatically treat every proprietary API or dataset as an essential facility.

3. IMS Health v NDC Health

Case C-418/01, Court of Justice of the European Union

IMS Health concerned access to a proprietary information structure and the circumstances under which refusal to license intellectual property could amount to abusive conduct.

The decision is important because it demonstrates that competition law must balance:

  • intellectual-property rights;
  • innovation incentives;
  • market access; and
  • competitive foreclosure.

Autonomous vehicle application

An autonomous-driving company could possess proprietary:

  • AI models;
  • sensor-processing technology;
  • mapping systems;
  • vehicle-control software; or
  • data structures.

Mandatory access to such technology should therefore not be presumed.

The competition analysis must consider whether the refusal prevents effective competition in a related market and whether the relevant legal conditions for intervention are satisfied.

4. Microsoft Corp. v Commission

Case T-201/04, General Court, 2007

Microsoft is highly relevant to technology ecosystems.

The case addressed Microsoft's conduct concerning:

  • interoperability information;
  • operating systems;
  • media-player technology;
  • network effects; and
  • leveraging platform dominance.

Autonomous vehicle application

An autonomous-vehicle operating system could become a technological bottleneck.

For example:

Dominant Vehicle OS → API → Third-Party Autonomous Applications

If the platform refuses interoperability information and competitors consequently cannot effectively operate on the system, Microsoft provides an important analytical precedent.

The case demonstrates why interoperability can become a competition-law issue where technological architecture itself affects market access.

5. Continental Automotive Systems v Avanci

United States Court of Appeals for the Fifth Circuit, 2022

This case involved Continental Automotive Systems and the Avanci patent-licensing ecosystem and is especially relevant to connected vehicles.

Continental challenged licensing arrangements involving standard-essential patents and alleged anticompetitive conduct.

The case illustrates the interaction between:

  • connected vehicles;
  • standard-essential patents;
  • licensing;
  • interoperability;
  • FRAND principles; and
  • competition law.

 

Autonomous vehicle relevance

Autonomous vehicles depend heavily on connectivity standards.

A future autonomous ecosystem may rely upon standards involving:

  • 5G/6G;
  • vehicle-to-everything communications;
  • positioning;
  • sensor communications;
  • connectivity protocols; and
  • intelligent transport infrastructure.

Control over essential patents or standards can therefore affect competition between autonomous-vehicle manufacturers and technology platforms.

6. Meru Travel Solutions v Uber India

Competition Commission of India

The CCI examined competition issues surrounding app-based radio-taxi services. The matter demonstrates how digital mobility platforms can be assessed under India's competition framework. The CCI records the proceedings in Case No. 96/2015 and related proceedings.

The case is particularly relevant because autonomous mobility is likely to develop from the existing platform-based mobility model.

The CCI's cab-aggregator work has also recognised that app-based transportation platforms generate distinct competition concerns arising from digital technology, network effects and algorithmic pricing.

Autonomous vehicle relevance

The same principles can extend from:

Human driver + ride-hailing algorithm

to:

Autonomous vehicle + fleet algorithm + mobility platform.

The latter could potentially produce even stronger network effects because the platform may control both:

  • the vehicle fleet; and
  • the algorithm allocating autonomous vehicles.

XI. Additional Relevant Precedent: Qualcomm

FTC v Qualcomm

The Qualcomm litigation provides an important technology-platform analogy involving control over critical semiconductor technology.

The FTC alleged that Qualcomm used anticompetitive practices to maintain its position in key semiconductor markets.

The broader lesson for autonomous vehicles is that competition authorities may examine whether control over an important technological input is being used to preserve market power in downstream markets.

This is relevant to:

  • autonomous-driving chips;
  • AI accelerators;
  • vehicle processors;
  • sensor-processing hardware;
  • connectivity chips; and
  • edge-computing infrastructure.

The EU's later Qualcomm litigation likewise concerned abuse of dominance and predatory pricing in the baseband-chipset market.

XII. Merger Regulation

Autonomous-vehicle competition policy cannot rely solely on abuse-of-dominance rules.

Merger control is equally important.

Consider:

Major Autonomous Platform + Mapping Company

or:

Vehicle Manufacturer + Autonomous AI Developer

or:

Cloud Provider + Autonomous Driving Company

or:

Autonomous Fleet Operator + Mobility Marketplace

Such transactions could create vertical or conglomerate effects.

Regulators may examine:

  • data accumulation;
  • elimination of potential competitors;
  • foreclosure of rival autonomous systems;
  • access to mapping;
  • access to cloud infrastructure;
  • interoperability;
  • switching costs;
  • vertical integration; and
  • network effects.

XIII. Killer Acquisitions

Autonomous-driving technology is characterised by rapidly developing startups.

A dominant platform might acquire a small company possessing:

  • superior perception technology;
  • better reinforcement-learning systems;
  • specialised mapping;
  • safety-validation technology;
  • fleet optimisation;
  • sensor fusion;
  • simulation technology.

Even where the target has relatively low revenue, the acquisition could be competitively significant because the target may be an innovation competitor.

Consequently, merger control should not rely exclusively upon historical turnover.

XIV. Algorithmic Competition

Autonomous vehicle platforms will increasingly use algorithms to determine:

  • vehicle allocation;
  • routes;
  • prices;
  • charging;
  • fleet deployment;
  • maintenance;
  • surge pricing;
  • passenger matching; and
  • road utilisation.

This creates potential risks of algorithmic coordination.

For example:

Platform A algorithm ↔ Platform B algorithm

could potentially produce parallel pricing or allocation without conventional human communication.

Competition authorities may therefore investigate whether apparent algorithmic coordination results from:

  • independent optimisation;
  • deliberate information exchange;
  • common software;
  • common algorithmic providers;
  • contractual restrictions; or
  • conscious coordination.

XV. Predatory Pricing

A large autonomous platform with substantial financial resources could potentially subsidise autonomous rides below sustainable levels.

For example:

Phase 1: Extremely low autonomous-ride prices
↓
Phase 2: Competitors exit
↓
Phase 3: Network effects increase
↓
Phase 4: Prices increase after competitive constraints disappear

The relevant competition-law analysis would depend on the applicable jurisdiction's predatory-pricing doctrine, including appropriate cost benchmarks and evidence of exclusionary strategy/effects.

The Qualcomm litigation illustrates the importance of rigorous price-cost analysis in technology markets.

XVI. Safety as a Legitimate Justification

Autonomous vehicles create an unusual competition-law complication:

Not every restriction on interoperability is anticompetitive.

Safety can legitimately require:

  • certification;
  • cybersecurity testing;
  • controlled APIs;
  • restricted access to vehicle-control systems;
  • software validation;
  • authentication;
  • encryption;
  • functional-safety requirements.

Therefore, regulators should distinguish:

Legitimate safety restriction

"Only certified software may directly control braking."

from potentially problematic exclusion:

"Only our affiliated navigation service may access vehicle location data."

The regulatory challenge is to prevent safety requirements from becoming a pretext for exclusion, while ensuring that competition law does not force manufacturers to compromise vehicle safety.

XVII. Data and Privacy Regulation

Autonomous vehicles create a convergence between:

Competition Law + Data Protection + Cybersecurity + Transport Regulation + AI Regulation

Data-sharing obligations therefore need safeguards.

Potentially sensitive information may include:

  • precise location;
  • travel history;
  • passenger behaviour;
  • biometric information;
  • vehicle identifiers;
  • household patterns;
  • workplace locations.

A competition remedy requiring data access should therefore incorporate:

  • anonymisation;
  • purpose limitation;
  • security requirements;
  • access controls;
  • proportionality;
  • data minimisation; and
  • protection against re-identification.

XVIII. Digital Markets Regulation

Traditional antitrust enforcement is often ex post.

Digital-platform regulation can also be ex ante.

The EU's Digital Markets Act demonstrates this approach by imposing specified obligations on designated gatekeepers. The Commission currently lists services such as Google's Android, Maps, Search and Play and Amazon Marketplace among designated core platform services.

The broader regulatory model could be relevant to autonomous vehicle ecosystems where a platform becomes a gatekeeper between:

Vehicle manufacturers ↔ developers ↔ mobility providers ↔ consumers.

XIX. Potential Regulatory Remedies

Competition authorities could employ several remedies.

1. Interoperability

Require reasonable technical interoperability between competing platforms.

2. Data portability

Allow users or legitimate business users to transfer relevant data.

3. Non-discrimination

Require objectively comparable access conditions.

4. API access

Provide access to necessary interfaces subject to safety and cybersecurity controls.

5. Separation

In extreme circumstances, structural or functional separation may be considered.

6. Behavioural commitments

Require:

  • transparent ranking;
  • non-discriminatory access;
  • audit mechanisms;
  • independent monitoring.

7. Merger remedies

Require:

  • divestiture;
  • licensing;
  • data-access commitments;
  • interoperability;
  • firewall arrangements.

XX. India-Specific Regulatory Position

For India, the principal competition-law framework is the Competition Act 2002, administered by the Competition Commission of India.

Autonomous vehicle platform issues could potentially implicate:

Section 3

Anti-competitive agreements.

Relevant conduct may include:

  • platform exclusivity;
  • coordinated algorithms;
  • restrictive interoperability agreements;
  • information exchange.

Section 4

Abuse of dominant position.

Potential concerns include:

  • denial of access;
  • discriminatory access;
  • tying;
  • leveraging;
  • unfair conditions;
  • exclusionary pricing.

Sections 5 and 6

Combination regulation.

This becomes important for acquisitions involving:

  • autonomous-driving companies;
  • mapping companies;
  • AI developers;
  • mobility platforms;
  • charging networks;
  • vehicle-data businesses.

The CCI's treatment of the Ola marketplace is instructive: in one combination, commitments were offered so that the marketplace algorithm would not favour drivers merely because their vehicles were manufactured by the acquiring parties, and the CCI relied on that modification in approving the transaction.

That provides a particularly useful Indian analogy for algorithmic neutrality in autonomous mobility platforms.

XXI. Key Competition Risks

Competition concernAutonomous-vehicle example
DominanceOne platform controls autonomous-driving OS
Data foreclosureRivals denied vehicle-generated data
Self-preferencingPlatform favours its own mobility fleet
TyingAutonomous software tied to cloud service
BundlingMapping + AI + charging sold together
ExclusivityVehicle manufacturers prohibited from using rivals
Refusal to dealRivals denied essential API access
Interoperability restrictionsThird-party systems cannot communicate
Predatory pricingAutonomous rides subsidised to eliminate rivals
Algorithmic coordinationCompeting platforms use common pricing technology
Killer acquisitionsDominant firm buys emerging AI competitor
Vertical foreclosurePlatform restricts access to vehicle hardware
Data accumulationLarge fleet produces uniquely valuable training data
Switching costsFleet cannot migrate historical operational data
Standard-essential patentsConnectivity licensing restricts vehicle competitors

XXII. Regulatory Test for an Autonomous Vehicle Platform

A competition authority can conceptually apply the following sequence:

1. Define the relevant market
↓
2. Identify the platform's market power
↓
3. Identify the controlled technological input
↓
4. Determine competitor dependence
↓
5. Identify exclusionary conduct
↓
6. Assess actual/potential foreclosure
↓
7. Examine efficiencies and safety justifications
↓
8. Examine innovation effects
↓
9. Consider privacy/cybersecurity constraints
↓
10. Select proportionate remedy

XXIII. Core Legal Principle

The central competition-law problem is not simply whether an autonomous vehicle company becomes large.

Scale itself is not unlawful.

The critical question is whether control over a technologically important autonomous ecosystem is used to exclude competing platforms, foreclose complementary providers, restrict interoperability, exploit data advantages, or extend market power into neighbouring markets.

The existing jurisprudence on Google Android, Microsoft, Bronner, IMS Health, Qualcomm, and digital mobility platforms such as Uber provides the legal building blocks for addressing these problems even though autonomous vehicles introduce technological circumstances that those older cases did not directly contemplate.

Conclusion

Autonomous vehicle platform competition regulation will increasingly require a layered regulatory approach.

The most important competitive assets may shift from the physical vehicle to:

AI models + vehicle data + maps + operating systems + APIs + cloud infrastructure + network effects.

Competition authorities should consequently examine not only vehicle market shares but also control over data, interoperability, software interfaces, standards, mobility marketplaces and complementary ecosystems.

For India, the Competition Act 2002 provides the principal antitrust framework, while the CCI's experience with app-based mobility platforms offers an important foundation for analysing future autonomous-mobility markets. Internationally, Google Android, Microsoft, Bronner, IMS Health, Qualcomm and connected-vehicle licensing disputes provide useful precedents for analysing dominance, interoperability, access, technology leverage and exclusion.

LEAVE A COMMENT