Competition Law and Ecosystem Coordination Through Protocols

1. Introduction

Ecosystem coordination through protocols refers to the use of technical rules, communication protocols, APIs, interoperability standards, authentication rules, data formats, payment protocols, messaging standards, or other technical specifications to coordinate how different participants in an ecosystem interact.

Protocols can be highly beneficial because they allow different systems to work together. However, when powerful firms or competitors control the protocol, coordination can also become a mechanism for:

excluding rivals;

fixing prices or commercial conditions;

restricting interoperability;

controlling access to infrastructure;

exchanging competitively sensitive information;

favouring an ecosystem owner's own products;

raising switching costs;

creating or protecting network effects.

EU horizontal-cooperation guidance recognises that standardisation can generate efficiencies and innovation, but also requires assessment of whether cooperation restricts competition under Article 101 TFEU. (EUR-Lex)

Core formula

PROTOCOL → COORDINATION → ACCESS/INFORMATION/INTEROPERABILITY → MARKET EFFECT → COMPETITION ANALYSIS → REMEDY

2. What Is a Protocol?

A protocol is essentially a set of technical rules governing communication or interaction between systems.

Examples include:

internet communication protocols;

payment protocols;

messaging protocols;

cloud interoperability protocols;

blockchain protocols;

API specifications;

authentication protocols;

wireless communication standards;

smart-device communication standards;

data-exchange protocols.

A protocol can determine:

Who can connect?

How can they connect?

What information must they provide?

What information can they receive?

What technical conditions must they satisfy?

Therefore, protocol design can have significant competitive consequences.

3. Legitimate Coordination vs Anti-Competitive Coordination

Protocol coordination is not inherently unlawful.

It can generate:

interoperability;

lower transaction costs;

technical compatibility;

safety;

cybersecurity;

innovation;

common standards;

economies of scale;

easier consumer switching.

For example:

Common payment protocol → more compatible payment systems → lower transaction costs → greater consumer choice

But the same mechanism can become problematic where:

Common protocol → exclusionary access rules → rival exclusion → reduced competition

4. Main Competition-Law Risks

A. Competitor coordination

Competitors may use a protocol or standards body to coordinate:

prices;

output;

customers;

market allocation;

technical restrictions;

future commercial strategies.

This can raise concerns under Article 101 TFEU or corresponding national competition laws.

B. Information exchange

A common technical system may automatically transmit information between competitors.

For example:

Competitor A → common protocol → platform → Competitor B

If the information includes future:

prices;

quantities;

capacity;

strategic plans;

customer information,

the arrangement may facilitate coordination.

The EU horizontal-cooperation guidelines specifically recognise that information exchange can produce efficiencies but can also restrict competition, particularly where competitively sensitive future information is exchanged. (EUR-Lex)

5. Protocols as Gateways

A protocol can become a gateway to an ecosystem.

For example:

Protocol → Authentication → Platform Access → Users → Transactions

If one undertaking controls the protocol, it may acquire significant influence over downstream competition.

Possible conduct includes:

refusing access;

discriminatory access;

excessive access fees;

technical degradation;

delayed certification;

incompatible updates;

preferential access to affiliated services.

6. Interoperability

Interoperability is one of the most important issues.

Suppose:

Protocol X

allows the dominant ecosystem's own service to communicate perfectly with the ecosystem.

But:

Rival Service → Protocol X → restricted functionality

The competitive question becomes whether the restriction:

is technically necessary;

protects security;

protects privacy;

is objectively justified;

disadvantages competing services;

forecloses effective competition.

Modern EU competition law continues to treat interoperability as an important issue in dominant digital ecosystems. The Commission's 2026 Article 102 guidelines refer to Microsoft, Bronner, IMS Health, Slovak Telekom and other cases when discussing access to infrastructure and interoperability. (EUR-Lex)

7. Standard-Setting and Protocol Coordination

Standard-setting is a special form of protocol coordination.

Examples:

telecommunications standards;

USB-type standards;

payment standards;

wireless standards;

digital identity standards;

smart-device standards.

A standard can create substantial benefits because manufacturers and software providers can design compatible products.

But competition concerns can arise where standard-setting:

excludes rivals;

favours one technology without objective justification;

involves competitors fixing commercial terms;

restricts alternative technologies;

creates discriminatory licensing;

enables strategic patent hold-up.

The EU horizontal-cooperation framework specifically includes standardisation agreements among the forms of cooperation requiring competition assessment. (EUR-Lex)

8. Standard-Essential Patents

A particularly important problem arises where a protocol or standard incorporates patented technology.

Such patents can become Standard-Essential Patents (SEPs).

The patent holder may have substantial bargaining power because manufacturers need the patented technology to comply with the standard.

This creates the potential problem of:

STANDARD → ESSENTIAL PATENT → MARKET DEPENDENCE → LICENSING POWER

Competition law therefore interacts with intellectual-property law.

9. Case Law

1. Microsoft v Commission — T-201/04

This is one of the most directly relevant cases.

Microsoft controlled Windows and refused to provide competitors with certain interoperability information concerning protocols used by Windows work-group server operating systems. The Commission treated the information as important for competing products, and the General Court substantially upheld the Commission's decision. (EUR-Lex)

The Commission decision concerned specifications of protocols rather than Microsoft's underlying source code. (EUR-Lex)

Competition principle

Protocol control can become a competition issue when a dominant undertaking uses control of interoperability information to restrict competition in a neighbouring market.

Ecosystem relevance

The structure was:

Windows client OS → Windows protocols → work-group servers → competing server products

Therefore, control at one ecosystem layer affected competition at another.

10. Microsoft Interoperability Remedies

The Microsoft case is also important because the remedy required interoperability information to be made available on reasonable and non-discriminatory terms.

The Commission subsequently monitored Microsoft's compliance and imposed periodic penalty payments when the required information was incomplete or inaccurate. (EUR-Lex)

Lesson

Protocol competition problems may require more than a prohibition.

They can require:

technical documentation;

access;

reasonable licensing;

non-discrimination;

independent monitoring;

continuing regulatory supervision.

11. Huawei Technologies v ZTE — C-170/13

This is a leading case involving standard-essential patents.

Huawei held an SEP relating to a telecommunications standard and had given a commitment to license it on FRAND terms.

The Court of Justice held that bringing an injunction action by an SEP holder with a dominant position can constitute an abuse in certain circumstances, particularly where the SEP holder has made a FRAND commitment and fails to follow the required negotiation procedure before seeking an injunction. (curia)

Competition principle

Competition law must balance:

IP rights

against

access to standardised technology and effective competition.

Ecosystem relevance

The protocol/standard becomes the infrastructure through which multiple competitors operate.

12. Rambus

The European Commission's Rambus proceeding concerned patents relevant to DRAM technology used in computers.

The Commission expressed concerns about unreasonable royalties and ultimately accepted binding commitments concerning royalty levels.

The Commission specifically emphasised the importance of standard-setting being conducted in an open, transparent and non-discriminatory manner. (EUR-Lex)

Competition lesson

A company should not be able to exploit participation in standard-setting to obtain unexpected market power and subsequently impose unreasonable conditions on firms that depend on the standard.

Formula

STANDARD PARTICIPATION → PATENT POSITION → LOCK-IN → LICENSING POWER → COMPETITION RISK

13. IMS Health v Commission — C-418/01

IMS Health concerned access to a pharmaceutical data structure known as the 1860 brick structure.

Although not a protocol case in the narrow technical sense, it is highly relevant to ecosystem coordination because it concerns an established technical/data structure that competitors needed to operate effectively.

The Court established demanding conditions for compulsory access to an intellectual-property-protected input.

Competition lesson

Not every proprietary technical architecture must be opened to competitors.

Exceptional intervention requires satisfying the stringent conditions associated with the essential-facilities doctrine.

The current Commission Article 102 guidelines continue to cite IMS Health when explaining refusal-of-access principles. (EUR-Lex)

14. Bronner — C-7/97

Bronner concerned access to a newspaper distribution system.

The Court applied strict conditions before a refusal to provide access to an infrastructure controlled by a dominant undertaking could constitute abuse.

Relevance to protocols

A protocol may be highly important, but importance alone does not automatically create a legal duty to provide access.

The analysis must consider factors such as:

indispensability;

elimination of effective competition;

inability to duplicate;

justification.

The modern Commission Article 102 guidelines continue to cite Bronner for these principles. (EUR-Lex)

15. Slovak Telekom — C-165/19 P

Slovak Telekom involved access to telecommunications infrastructure and pricing conditions.

The Court confirmed important principles concerning access restrictions and margin-squeeze analysis.

Ecosystem relevance

Telecommunications ecosystems demonstrate how:

network infrastructure → access → downstream services → competition

can create leverage across connected markets.

The current Article 102 guidelines expressly cite Slovak Telekom in their discussion of access-related exclusionary conduct. (EUR-Lex)

16. Deutsche Telekom — C-152/19 P

Deutsche Telekom concerned pricing conditions in telecommunications markets and margin squeeze.

Protocol/ecosystem relevance

Although not a protocol-standardisation case, telecommunications networks provide a useful ecosystem analogy:

upstream infrastructure → access conditions → downstream competition

The case illustrates that an undertaking controlling an important infrastructure layer may influence competition at another level through the conditions imposed on access.

The judgment remains expressly referenced in the Commission's current Article 102 guidance. (EUR-Lex)

17. Case-Law Comparison

18. Protocols and Article 101 TFEU

Where competitors jointly develop or operate a protocol, Article 101 can become particularly important.

The analysis is:

Step 1 — Agreement

Is there an agreement, decision of an association, or concerted practice?

Step 2 — Competitor relationship

Are the participants actual or potential competitors?

Step 3 — Protocol function

What does the protocol coordinate?

Step 4 — Restriction

Does it coordinate:

prices?

output?

customers?

technical access?

commercially sensitive information?

Step 5 — Effects

Does it restrict:

price competition;

innovation;

entry;

quality;

interoperability?

Step 6 — Efficiency

Can the cooperation satisfy Article 101(3)?

The EU's horizontal-cooperation guidelines expressly distinguish pro-competitive standardisation from cooperation capable of restricting competition. (EUR-Lex)

19. Protocols and Article 102 TFEU

Article 102 becomes particularly relevant when one dominant ecosystem controls the protocol.

Potential abuses include:

Refusal to provide access

Dominant protocol → rival requests access → refusal → foreclosure

Discriminatory access

Own service = favourable conditions

Rival = inferior conditions

Excessive access charges

The protocol becomes a bottleneck and access prices become economically burdensome.

Technical degradation

A rival technically connects but receives inferior functionality.

Tying

Access to one ecosystem component is conditioned upon adoption of another.

Self-preferencing

The protocol gives the ecosystem owner's own downstream service preferential treatment.

20. Protocols and Digital Ecosystems

Modern digital ecosystems can use protocols at almost every level.

AI ecosystem

AI model → API → application → cloud → users

Cloud ecosystem

Cloud protocol → storage → computing → applications

Payment ecosystem

Payment protocol → bank → wallet → merchant → consumer

Messaging ecosystem

Messaging protocol → interoperability → users → network effects

IoT ecosystem

Device protocol → sensor → platform → cloud → analytics

The competition question is:

Does protocol coordination increase interoperability and innovation, or does it create an artificial barrier to competing ecosystems?

21. Open vs Closed Protocols

Open protocol

Characteristics:

published specifications;

broad access;

transparent governance;

non-discriminatory participation;

interoperability.

Potential advantage:

Lower entry barriers

Closed protocol

Characteristics:

proprietary specifications;

restricted access;

licensing requirements;

ecosystem-controlled development.

Potential competition concerns:

lock-in;

foreclosure;

dependence;

exclusion.

However, closed does not automatically mean unlawful. Proprietary technology can legitimately protect innovation, security and intellectual property.

22. Protocol Governance

Governance is extremely important.

A protocol may be governed by:

one dominant company;

consortium;

standards organisation;

open-source community;

regulator;

decentralized governance system.

Competition analysis should examine:

Who controls changes?

Who approves participants?

Who controls technical specifications?

Who controls access?

Can competitors participate?

Can users switch?

Are rules transparent?

23. Algorithmic Protocol Coordination

A newer problem is algorithmic coordination.

Suppose several competitors use a common algorithm or protocol.

Competitor A → Algorithm

Competitor B → Same Algorithm

Competitor C → Same Algorithm

If the system automatically aligns prices, output or other competitive variables, the technology could potentially facilitate coordinated outcomes.

The important distinction is between:

technology independently producing efficient outcomes; and

firms intentionally using technology as a mechanism for anti-competitive coordination.

Therefore:

COMMON TECHNOLOGY ≠ AUTOMATIC CARTEL

but:

COMMON TECHNOLOGY + COMPETITIVE COORDINATION = POTENTIAL ARTICLE 101 CONCERN

24. Blockchain Protocols

Blockchain creates a special ecosystem problem.

A blockchain protocol can coordinate:

validation;

transaction ordering;

token transfers;

governance;

access;

smart contracts.

Competition concerns can include:

validator concentration;

protocol governance;

discriminatory access;

exclusion from validation;

control of essential interfaces;

interoperability restrictions;

coordinated transaction rules.

The same competition principles remain applicable even though coordination is technically decentralized.

25. Protocols and Network Effects

Protocols can strengthen network effects:

More participants

↓

More compatibility

↓

More users

↓

More developers

↓

More applications

↓

Greater ecosystem value

↓

More users

This creates a feedback loop.

If a dominant undertaking controls the protocol, it may be able to reinforce its position.

26. Competition-Law Safeguards

A competition authority may consider:

open technical specifications;

non-discriminatory access;

FRAND licensing;

interoperability obligations;

independent governance;

limits on sensitive information exchange;

monitoring;

technical audits;

data portability;

access remedies.

27. Important Distinction: Standardisation vs Cartel

This is an important examination point.

Legitimate standardisation

Competitors cooperate on technical compatibility

↓

Products become interoperable

↓

Costs decrease

↓

Innovation/choice increases

Potentially pro-competitive.

Anti-competitive coordination

Competitors cooperate on prices/output/customer allocation

↓

Competition becomes predictable or eliminated

Potential Article 101 problem.

Thus:

Technical coordination may be legitimate; commercial coordination can create serious competition concerns.

28. Ecosystem Protocol Assessment Framework

Use the following framework in an examination:

P-R-O-T-O-C-O-L

P – Participants
Who controls and uses the protocol?

R – Rules
What does the protocol coordinate?

O – Openness
Who can access it?

T – Technical interoperability
Can competing systems connect?

O – Outcome
What happens to price, quality, innovation and entry?

C – Competition effect
Is there foreclosure or coordination?

O – Objective justification
Are security, privacy or technical reasons legitimate?

L – Legal remedy
What intervention is proportionate?

29. Ultra-Short Revision

Protocol = technical rules governing interaction between systems.

Protocols can promote interoperability, innovation and efficiency.

They can also facilitate coordination, exclusion and lock-in.

Article 101 is important where competitors coordinate through common protocols.

Article 102 is important where a dominant undertaking controls an essential ecosystem interface.

Standard-setting must be assessed for both efficiencies and exclusionary effects.

SEP/FRAND disputes can create competition-law issues.

Microsoft = interoperability.

Huawei v ZTE = SEP/FRAND.

Rambus = standard-setting and patent leverage.

IMS Health = proprietary technical/data structure.

Bronner = indispensability/access.

Slovak Telekom = telecom infrastructure access.

Deutsche Telekom = upstream infrastructure and downstream competition.

Final Formula

PROTOCOL → STANDARD/INTERFACE → NETWORK EFFECT → DEPENDENCE → MARKET POWER → COORDINATION OR FORECLOSURE → COMPETITION EFFECT → LEGAL CONTROL

Final Conclusion

Ecosystem coordination through protocols occupies an important intersection between competition law, technology, interoperability and standardisation. Protocols can reduce transaction costs and enable competing products to work together, but they can also become mechanisms for controlling access, exchanging sensitive information, excluding rivals or reinforcing ecosystem dominance. The Microsoft, Huawei, Rambus, IMS Health, Bronner, Slovak Telekom and Deutsche Telekom authorities demonstrate different dimensions of this problem. The central competition-law task is therefore to distinguish legitimate technical coordination that improves interoperability from coordination or access restrictions that materially weaken competitive alternatives.