Competition Law and Public Sector Ecosystem Interoperability

1. Introduction

Public sector ecosystem interoperability refers to the ability of government agencies, public-sector enterprises, regulated entities, private suppliers, digital platforms, databases, infrastructure systems, and public digital services to communicate and operate with one another through common technical, legal, or institutional standards.

Examples include:

government digital identity systems;

public payment infrastructure;

tax platforms;

public procurement systems;

healthcare information networks;

transport-ticketing systems;

electricity and energy platforms;

railway reservation systems;

telecommunications infrastructure;

government data exchanges;

public cloud and digital-service infrastructure.

Interoperability can promote competition because it reduces switching costs, network barriers, technical exclusion, and dependence on a single infrastructure provider.

At the same time, interoperability requirements can create competition concerns if a dominant undertaking uses control over an interface, standard, API, database, or public infrastructure to exclude rivals.

2. Meaning of Interoperability

Interoperability means that two or more systems can:

communicate;

exchange information;

authenticate users;

process transactions;

understand exchanged information; and

provide compatible services.

There are several forms.

Technical interoperability

Different systems can technically communicate.

Data interoperability

Information can be exchanged in a standardized format.

Functional interoperability

Different systems can perform complementary functions together.

Commercial interoperability

Users can transact across competing platforms.

Institutional interoperability

Different public bodies operate according to compatible rules.

3. Why Interoperability Matters for Competition

Interoperability can reduce several sources of market power.

Without interoperability

Large platform → users locked in → competitors cannot connect → entry barriers

With interoperability

Platform A ↔ common interface ↔ Platform B

Users can potentially move between systems while continuing to interact with users of other systems.

This can reduce:

switching costs;

network effects;

entry barriers;

data lock-in;

ecosystem dependency.

4. Public Sector Ecosystems and Competition

Public-sector ecosystems are unusual because the infrastructure may be:

government-owned;

state-controlled;

privately operated under licence;

publicly funded;

operated through public-private partnerships;

regulated by a statutory authority.

A public-sector platform can become competitively significant where private enterprises depend upon it.

For example, businesses may require access to:

government authentication;

payment infrastructure;

procurement platforms;

regulatory databases;

transportation networks;

electricity grids;

telecommunications infrastructure.

Control over such systems can therefore influence competition in downstream markets.

5. Interoperability as a Pro-Competitive Mechanism

Interoperability can produce substantial benefits.

A. Lower switching costs

Users can move between competing providers without abandoning the entire ecosystem.

B. Reduced network effects

A new entrant does not necessarily have to recreate the entire existing network.

C. Greater consumer choice

Users can select different providers while retaining connectivity.

D. Innovation

New firms can build complementary services.

E. Lower entry barriers

Start-ups can access established infrastructure without duplicating it.

F. Increased resilience

Multiple interoperable systems can reduce dependence upon a single provider.

6. Interoperability and Dominance

Interoperability becomes particularly important where an undertaking controls a bottleneck.

Suppose:

Public infrastructure → API → downstream services

If the infrastructure operator refuses to provide the API to competitors while allowing its own affiliate unrestricted access, the operator may potentially use infrastructure control to protect its downstream market position.

This can raise abuse-of-dominance concerns.

7. Essential Facilities

The essential-facilities doctrine is particularly relevant.

The central questions include:

Is the infrastructure indispensable?

Can competitors reasonably duplicate it?

Is interoperability technically feasible?

Would refusal eliminate effective competition?

Is there an objective justification for refusal?

The European cases Bronner and IMS Health provide important guidance.

The doctrine is exceptional and does not mean that every dominant enterprise must make every system interoperable.

8. Case Law

1. United States v. Terminal Railroad Association of St. Louis, 224 U.S. 383 (1912)

Facts

Railroad interests controlled important terminal facilities necessary for rail traffic entering St. Louis.

Principle

The Supreme Court addressed the exclusionary potential of collectively controlled infrastructure and required meaningful access arrangements.

Relevance

The case illustrates the foundational competition concern associated with bottleneck infrastructure.

In a public-sector ecosystem, a government-controlled or concession-operated infrastructure platform may similarly become a gateway through which competitors must operate.

9. MCI Communications Corp. v. AT&T, 708 F.2d 1081 (7th Cir. 1983)

Facts

MCI challenged AT&T's conduct concerning access to telecommunications infrastructure.

Principle

The Seventh Circuit developed an important framework for determining when refusal to provide access to infrastructure could have antitrust significance.

Relevance

The case is relevant to interoperability involving:

telecommunications networks;

digital infrastructure;

payment systems;

public communication networks;

cloud infrastructure.

It demonstrates why control over an infrastructure interface can become a competitive bottleneck.

10. Aspen Skiing Co. v. Aspen Highlands Skiing Corp., 472 U.S. 585 (1985)

Facts

Ski operators had previously participated in a cooperative ticketing arrangement. The dominant operator eventually terminated the arrangement.

Principle

The Supreme Court considered the termination of an established and profitable cooperative relationship relevant to monopolization under the particular circumstances.

Relevance

The case provides an analogy where a dominant public-sector platform:

historically permitted interoperability;

later terminates it;

lacks an adequate commercial justification;

thereby disadvantages a competing platform.

The case must, however, be read alongside the later limitations established in Trinko.

11. Verizon Communications Inc. v. Trinko, 540 U.S. 398 (2004)

Facts

The case involved telecommunications access and alleged discriminatory treatment of competitors.

Principle

The Supreme Court emphasized that antitrust law does not ordinarily impose a general obligation upon firms to assist competitors.

Relevance

This is a crucial limitation.

A public-sector ecosystem should not automatically be required to make every component interoperable with every competing service.

Compulsory interoperability requires stronger justification where:

duplication is possible;

multiple alternative systems exist;

security risks are substantial;

interoperability would undermine investment incentives.

12. Oscar Bronner GmbH & Co. KG v. Mediaprint, C-7/97

Facts

Bronner sought access to Mediaprint's newspaper distribution system.

Principle

The Court of Justice adopted a stringent approach to compulsory access, emphasizing indispensability and the absence of realistic alternatives.

Relevance

The principle is directly relevant to public-sector interoperability.

A system may be important without being legally indispensable.

For example, the existence of a popular government platform does not automatically mean that all private competitors must receive access on identical terms.

13. IMS Health GmbH & Co. OHG v. NDC Health, C-418/01

Facts

IMS controlled a pharmaceutical data structure that competitors considered necessary to compete effectively.

Principle

The Court recognized exceptional circumstances where refusal to provide access to an indispensable structure could constitute abuse.

Relevance

The case is useful for interoperability involving:

public databases;

proprietary data formats;

technical standards;

APIs;

digital identity systems.

If competitors cannot reasonably develop alternative systems, interoperability restrictions become more significant from a competition-law perspective.

14. Microsoft Corp. v. Commission, Case T-201/04

Facts

The European Commission found Microsoft dominant in certain software markets and examined its refusal to provide interoperability information to competing work-group server products.

Principle

Control over interoperability information can become an abuse where it substantially impairs competition in an adjacent market and the relevant exceptional conditions are satisfied.

Relevance

This is one of the most important analogies for modern public-sector digital ecosystems.

Consider:

Government platform → authentication API → private service providers.

If the platform operator provides its own affiliated services with complete interoperability information while denying competitors information necessary to achieve equivalent functionality, competition concerns may arise.

15. United States v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001)

Facts

Microsoft possessed substantial power in PC operating systems and engaged in conduct that affected competition in browser distribution.

Principle

The case demonstrated how control over an important technological platform can be used to disadvantage complementary or competing products.

Relevance

Public digital infrastructure can generate similar competitive dynamics.

For example:

Public platform → authentication → downstream financial/health/transport services

can become an ecosystem in which control over the infrastructure affects competition in adjacent markets.

16. Google Shopping — European Commission, Case AT.39740

Facts

Google used its general search infrastructure in a way that gave preferential treatment to its own comparison-shopping service relative to competing services.

Principle

The case illustrates competition concerns where control over an important digital gateway is used to favour an affiliated downstream service.

Relevance

A public-sector infrastructure operator that also provides downstream commercial services could potentially create comparable concerns through:

preferential APIs;

priority processing;

superior technical access;

discriminatory authentication;

preferential search or ranking;

preferential data access.

The specific legal analysis would depend upon market structure and evidence.

17. American Needle, Inc. v. NFL, 560 U.S. 183 (2010)

Facts

NFL teams coordinated commercial licensing through the NFL structure.

Principle

The Supreme Court emphasized that formally coordinated structures may still involve separate economic actors capable of competing with one another.

Relevance

Public-sector ecosystems often involve multiple bodies:

government departments;

public enterprises;

infrastructure operators;

private concessionaires;

technology providers.

Their collective governance arrangements can therefore raise competition questions when they coordinate rules affecting independent competition.

18. Ohio v. American Express Co., 585 U.S. 529 (2018)

Facts

American Express operated a two-sided payment network connecting merchants and cardholders.

Principle

The Supreme Court emphasized the importance of considering both sides of a two-sided platform when assessing competitive effects.

Relevance

Public-sector platforms can also be multi-sided.

For example:

government ↔ platform ↔ private service providers

or

citizens ↔ public digital infrastructure ↔ businesses

A change to interoperability may affect multiple sides simultaneously.

19. Interoperability and Self-Preferencing

One of the most significant risks is asymmetric interoperability.

Imagine a public infrastructure platform that allows:

its own affiliate: full API access;

independent competitors: restricted API access.

The infrastructure operator may then use its control over the upstream platform to distort downstream competition.

This creates the chain:

Infrastructure dominance → unequal interoperability → higher rival costs → reduced competition.

20. Interoperability and Data Portability

Interoperability frequently overlaps with data portability.

Users may accumulate:

transaction records;

identity information;

service histories;

performance records;

credentials;

usage data.

If those data cannot move easily between competing platforms, switching costs increase.

Data portability can therefore complement interoperability by allowing users to move between providers without losing accumulated information.

21. Public Procurement Platforms

Interoperability is especially important in public procurement.

A government procurement platform may interact with:

supplier databases;

payment systems;

tax systems;

identity systems;

logistics systems;

banking systems.

If a single provider controls the technical interfaces, it may become difficult for competing procurement-service providers to enter.

Competition authorities may therefore examine:

API access;

data standards;

certification requirements;

interoperability fees;

technical access conditions.

22. Payment Infrastructure

Public or regulated payment systems create another important example.

Suppose a dominant payment infrastructure gives:

its own affiliated wallet immediate access;

rival wallets delayed access;

its own service lower transaction costs;

competitors higher technical requirements.

The concern is not merely technical discrimination.

The infrastructure operator may be using control over an upstream bottleneck to distort downstream competition.

23. Telecommunications and Public Networks

Telecommunications infrastructure historically provides many examples of interoperability problems.

Important competitive inputs include:

network access;

numbering;

interconnection;

spectrum-related infrastructure;

authentication;

routing.

The fundamental principle is that a dominant infrastructure provider should not necessarily be allowed to use technical control to eliminate downstream competitors.

At the same time, compulsory access must not undermine network security or infrastructure investment.

24. Public Infrastructure Standards

A government or public-sector entity may establish technical standards.

Standards can be pro-competitive because they:

create compatibility;

reduce transaction costs;

increase consumer choice;

allow multiple suppliers to compete.

But standards can also become exclusionary if:

competitors are deliberately excluded;

proprietary technology is unnecessarily mandated;

standard-setting is captured by incumbents;

interoperability is denied to rival technologies.

Thus:

Standardization can either reduce or increase barriers to competition depending upon how it is designed and implemented.

25. Indian Competition Law

Section 4 — Abuse of Dominant Position

Section 4 of the Competition Act, 2002 is particularly relevant where a public-sector or privately operated infrastructure platform is dominant.

Potential conduct includes:

discriminatory access;

denial of market access;

unfair conditions;

tying;

leveraging dominance into another market.

For example, if a dominant public digital infrastructure requires competing service providers to satisfy substantially more burdensome technical conditions than an affiliated provider, Section 4 issues may arise depending upon the facts.

26. Section 3 — Anti-Competitive Agreements

Interoperability arrangements can also involve agreements between competing entities.

Potential concerns include:

collective exclusion from a standard;

agreements not to interoperate;

allocation of users;

restrictions on compatible products;

information exchange.

However, interoperability agreements can also generate substantial efficiencies.

Therefore, context is critical.

27. Sections 5 and 6 — Combinations

Mergers involving interoperability infrastructure can raise additional concerns.

Examples include:

acquisition of a payment-interoperability provider;

acquisition of a public-procurement technology provider;

acquisition of a digital identity platform;

acquisition of a competing API provider.

The competition issue may arise if the transaction gives one undertaking control over an important interoperability gateway.

28. Legitimate Reasons for Restricting Interoperability

Competition law should not require interoperability at any cost.

Legitimate reasons may include:

Cybersecurity

Opening interfaces can create attack surfaces.

Privacy

Certain information may not lawfully be transferred.

System stability

Uncontrolled interoperability can destabilize infrastructure.

Fraud prevention

Interoperability may need authentication and monitoring.

Technical limitations

Legacy systems may not immediately support interoperability.

National security

Certain government systems may require restricted access.

Regulatory compliance

Financial, healthcare and identity systems may have statutory restrictions.

29. Interoperability vs Compulsory Access

These concepts are related but not identical.

Interoperability means systems can interact.

Compulsory access means a dominant undertaking is legally required to provide another undertaking with access to its infrastructure or information.

Competition law may encourage interoperability without necessarily imposing unrestricted access.

A proportionate approach may involve:

standardized APIs;

reasonable technical requirements;

non-discriminatory access;

security certification;

reasonable fees;

privacy safeguards.

30. Competition Risks

31. Potential Remedies

Where an infringement is established, authorities may consider:

1. Non-discriminatory interoperability

Comparable competitors receive comparable access.

2. Standardized APIs

Technical interfaces can be made available under transparent conditions.

3. Data portability

Users can transfer relevant data between systems.

4. Interoperability standards

Common technical standards can reduce fragmentation.

5. Separation of functions

Infrastructure operation can potentially be separated from downstream commercial activities.

6. Transparency

Access criteria and technical requirements can be disclosed.

7. Monitoring

An independent authority may monitor compliance with interoperability obligations.

32. Key Legal Balance

The central competition-law balance is:

Open interoperability

versus

legitimate infrastructure protection.

Too little interoperability may produce:

monopoly;

lock-in;

foreclosure;

entry barriers.

Too much compulsory interoperability may produce:

cybersecurity risks;

privacy problems;

free-riding;

reduced investment incentives;

technical instability.

Competition law therefore generally requires a fact-specific and proportionate assessment.

33. Conclusion

Public-sector ecosystem interoperability can be a powerful competition-enhancing mechanism because it allows different systems and service providers to interact without requiring competitors to duplicate an entire infrastructure.

The principal competition issues arise when a dominant infrastructure operator uses technical control to:

deny interoperability;

discriminate between competitors;

favour its own downstream services;

restrict data portability;

impose exclusionary technical standards;

raise rivals' costs;

increase switching costs; or

prevent effective market entry.

The principal cases provide complementary principles:

Terminal Railroad — control of critical infrastructure can facilitate exclusion.

MCI v. AT&T — infrastructure access can have substantial competitive significance.

Aspen Skiing — termination of established cooperation can matter in exceptional circumstances.

Trinko — no general antitrust duty to assist competitors.

Bronner — compulsory access requires stringent conditions.

IMS Health — exceptional access may be required where an indispensable infrastructure prevents effective competition.

Microsoft — interoperability information can become a competitive bottleneck.

Google Shopping — infrastructure control can potentially be leveraged to favour downstream services.

American Needle — collective governance does not automatically remove competition-law scrutiny.

American Express — platform effects must sometimes be evaluated across multiple sides of an ecosystem.

Under Indian competition law, Sections 3 and 4 of the Competition Act, 2002, together with the combination provisions in Sections 5 and 6 where applicable, provide the principal framework.

The essential principle is:

Public-sector interoperability should generally be assessed as a means of preserving competitive access, but interoperability is not an absolute entitlement. Competition law must distinguish exclusionary interoperability restrictions from legitimate requirements based on security, privacy, technical integrity, safety and investment incentives.