Telecommunications and Network Infrastructure IP Toolkit: Spectrum, Equipment, Standards, and Subscriber Data

By Casey Scott McKay · 2024-10-15

A carrier owns almost nothing that makes its network work. The spectrum is licensed from the state, the equipment is licensed from vendors, the protocols are standardised and patented by others, and the software running the core is increasingly somebody else's. This toolkit assembles the working material for practitioners advising carriers, equipment vendors, tower companies, and network software businesses. It covers the standard essential patent regime that governs the sector's core technology, the equipment agreements where feature licensing and firmware terms create long-term dependency, the subscriber data rules that predate modern privacy law and still constrain it, and the disaggregation of the network into open interfaces and virtualised functions that is rewriting every assumption in the previous three.

IP and Technology > Information Technology | Toolkit | Published 15 October 2024 - Updated 1 March 2026 | Casey Scott McKay - marksy.us

Summary. A carrier owns almost nothing that makes its network work. The spectrum is licensed from the state, the equipment from vendors, the protocols are standardised and patented by others, and the core software is increasingly somebody else's. This toolkit assembles working material for advising carriers, equipment vendors, tower companies, and network software businesses: the standard essential patent regime governing the sector's core technology, the equipment agreements where feature licensing and firmware terms create dependency, the subscriber data rules that predate modern privacy law and still constrain it, and the disaggregation rewriting all of it.

Keywords: telecommunications IP · spectrum licences · standard essential patents · FRAND commitments · network equipment terms · firmware licensing · interconnection agreements · subscriber data · CPNI · open RAN · network function virtualisation · tower and site agreements · roaming · lawful intercept · carrier brand licensing

Start Here

The instinct on approaching a telecommunications matter is to look for the carrier's patents. That is the wrong place to start, because the modern carrier is a licensee of nearly everything it depends on.

Spectrum is a licence from the state, granted on conditions, renewable on conditions, transferable only with approval. It is the carrier's most valuable asset and it is not property in the ordinary sense.

Equipment is bought as hardware and licensed as software, with feature unlocks, capacity licences, and firmware terms that determine what the purchased box may actually do and for how long.

The protocols are standardised through industry bodies whose participants declare patents essential to the standard and commit to license them on fair, reasonable, and non-discriminatory terms. That commitment is the sector's central intellectual property mechanism and the subject of two decades of litigation.

The core software is increasingly virtualised, containerised, and open source derived, which converts a hardware procurement into a software licensing problem.

The subscriber data is governed by a sector-specific confidentiality regime that predates modern privacy statutes, sits alongside them, and reaches uses that general privacy law does not.

What the carrier does own is the network as deployed: the site portfolio, the fibre routes, the customer relationships, the operational data, and the brand. Those are the assets to protect. Everything else is a licence to negotiate.

Four questions organise the practice.

What does the equipment agreement actually permit? Feature licensing, capacity limits, resale restrictions, and end-of-support terms determine the economics of a network for a decade.

What standards exposure exists, and in which direction? A carrier is an implementer; a vendor may be both implementer and holder; the analysis and the leverage differ completely.

Who may use subscriber data, for what? The sector-specific rules and the general privacy statutes overlap imperfectly and the overlap is where enforcement happens.

What happens on disaggregation? Open interfaces and virtualised functions multiply the number of suppliers and destroy the single-vendor accountability the old model provided.

See The Pipes and the Spectrum for the doctrinal treatment and Advising a Telecommunications or Network Business for the sequence.

Standards and the FRAND commitment

Cellular and networking technology is standardised, and standardisation is where the intellectual property in this sector actually lives.

The mechanism: participants in a standards development organisation contribute technical proposals; where a contribution is adopted and a participant holds patents necessarily infringed by implementing the standard, the organisation's policy requires disclosure and a commitment to license on fair, reasonable, and non-discriminatory terms.

That commitment produces a distinctive body of law and practice.

Essentiality is asserted, not adjudicated. Declared-essential portfolios are large, over-inclusive, and largely untested. A declaration is a starting point for negotiation, not a finding.

Rate-setting is the fight. What is fair and reasonable, and against what royalty base, has produced extended litigation, with the smallest saleable patent-practising unit and end-device pricing as competing frameworks.

Non-discrimination constrains the holder in ways ordinary licensing does not, which is why comparable licences are the central evidence.

Injunctive relief is constrained. A holder who has committed to license generally cannot obtain an injunction against a willing licensee, and the willingness analysis has become the practical battleground.

Contract theory underpins it. The FRAND commitment is generally analysed as a contract with the standards organisation for the benefit of implementers, which gives implementers a claim independent of patent law.

Antitrust sits alongside. Deceptive conduct in the standardisation process, evasion of a commitment through transfer, and refusal to license at any rate raise competition issues. See the IP and Antitrust Toolkit.

Pools exist and are partial. Patent pools reduce transaction costs and never cover the whole landscape, which means a licensee with a pool licence still faces holdouts.

For the working material, see Licensing or Litigating a Standard Essential Patent and the Standard Essential Patents and FRAND Toolkit.

Equipment agreements, where the money is decided

Network equipment purchasing looks like hardware procurement and behaves like software licensing, and the difference costs carriers enormous sums.

Feature licensing. A base station or a router ships with capability that is disabled until a licence is bought. The hardware was paid for; the function was not. Whether this is objectionable is a commercial question; whether it was understood at purchase is a legal one.

Capacity licensing. Throughput, subscriber count, or port count limits enforced in software, with growth triggering payments unrelated to marginal cost.

Firmware and update terms. Whether updates are included, for how long, and what happens at end of support. An operator running equipment past the vendor's support horizon has a security problem and a contractual one.

Resale and transfer restrictions. Whether a decommissioned unit may be sold, and whether its licences transfer, determines the secondary market's existence. This is exhaustion territory, and Impression Products, Inc. v. Lexmark International, Inc. limits what post-sale restrictions can achieve through patent law even where contract terms purport otherwise.

Interoperability and lock-in. Proprietary interfaces between a vendor's elements make multi-vendor deployment impractical, which is the commercial problem open interface initiatives exist to solve.

Source escrow and continuity. Vendor consolidation and geopolitical restriction have made vendor availability a live risk. See the Software Continuity and Escrow Toolkit.

Third-party and open source components. Network equipment firmware is substantially open source, with obligations that reach the carrier as a distributor in some configurations. See Copyleft and Consequences and the Software, Data, and Open Source Toolkit.

Security and supply chain provenance are now procurement terms rather than technical annexes. See the Cybersecurity Governance and Disclosure Toolkit.

Spectrum, sites, and the physical layer

Spectrum licences are conditional grants: build-out obligations, interference constraints, renewal expectancy, and transfer approval. They are treated as assets in financings and are not owned outright, which affects security interests. See the IP Security Interests and Financing Toolkit.

Site and tower agreements are real property arrangements with intellectual property consequences: whose equipment, whose data from that equipment, whose branding on the structure, and what happens on decommissioning.

Fibre and conduit raise indefeasible right of use structures, which are long-term capacity grants that behave like leases and are documented like licences.

Interconnection between carriers is regulated, negotiated, and technical, and the agreements carry confidentiality obligations over traffic data that are frequently the only protection the data has.

Roaming agreements move subscriber data across borders and across legal regimes, and the data protection terms are usually thinner than the technical annexes.

Lawful intercept capability is mandated, is built into equipment, and is itself sensitive technical information whose disclosure is separately restricted.

Subscriber data, and a regime older than privacy law

Telecommunications carriers have been subject to sector-specific confidentiality obligations over customer information for far longer than general privacy statutes have existed, and the two regimes now sit awkwardly together.

The sector-specific regime protects information about a customer's use of the service — what was called, when, from where, for how long, and which services were purchased — and restricts use for marketing without appropriate approval. It is enforced by a sector regulator with its own procedures.

The general privacy statutes reach the same data as personal information, with rights of access, deletion, and opt-out, plus sensitive-category treatment for precise location.

Three practical points.

Location data is the sharp edge. Network-derived location is generated continuously, is commercially valuable, has been the subject of significant enforcement, and sits in the sensitive category under most modern statutes.

Aggregation does not necessarily solve it. Aggregate location products have been shown to be re-identifiable, and the contractual representations made to purchasers of such products are where liability attaches.

The downstream chain is the exposure. Data sold or shared with aggregators, resellers, and application providers travels further than the carrier's controls, and the carrier remains accountable.

See The State Privacy Wave, the State Privacy Compliance Toolkit, the Data Licensing and Rights Toolkit, and the Incident Response and Breach Notification Toolkit.

Disaggregation: open interfaces, virtualisation, and the end of single-vendor accountability

The traditional network was bought from two or three vendors who supplied hardware, software, and integration as one thing, and who were accountable when it did not work. Disaggregation breaks that apart, and every intellectual property assumption breaks with it.

Open interface initiatives publish specifications for the connections between radio units, distributed units, and central units, so that components from different suppliers interoperate. That converts a vendor relationship into a specification-compliance question, and specification compliance is a standards question with declared patents attached.

Network function virtualisation replaces purpose-built hardware with software on general-purpose servers. The intellectual property consequence is that the network core becomes a software estate, with licensing, open source, and container-image provenance questions the operations team has never had to answer.

Cloud-native core deployments put the network on infrastructure the carrier does not control, adding a hyperscaler's terms to the stack.

Integration accountability disappears. When a multi-vendor deployment underperforms, no single supplier is responsible, and the contractual mechanisms — service levels, remedies, indemnities — were designed for a world where one was.

Indemnity coverage fragments. A patent claim against a disaggregated network reaches components from several suppliers, each with its own indemnity, its own cap, and its own view of whose element is accused.

Test and integration data becomes an asset. The carrier that has done the work of making a multi-vendor stack function holds knowledge nobody else has, which is a trade secret if it is treated as one under 18 U.S.C. § 1839.

See the Technology Contracts Toolkit and the AI Procurement and Governance Toolkit for the automation layer increasingly built on top.

What a carrier actually owns, and should protect

The brand. Carrier brands are among the most valuable in any market, are heavily licensed to resellers and virtual operators, and require the quality control discipline of any licensing programme. See Drafting a Trademark License That Survives and the Brand Licensing Program Toolkit.

The network design and planning data. Site selection, propagation modelling, capacity planning, and the operational knowledge of what works where. Trade secret material, rarely treated as such.

The operational and performance data. Which is increasingly a product in its own right and which raises the derived-data questions treated in the Data Licensing Checklist.

Internally developed software. Provisioning, orchestration, billing, and customer-facing applications, whose ownership depends on contractor agreements satisfying 17 U.S.C. § 204.

The customer relationships and the data behind them, subject to the regime above.

Whatever patents exist, which in a carrier's portfolio are typically defensive and frequently acquired rather than invented.

Virtual operators, resellers, and the wholesale layer

A large share of retail telecommunications is sold by parties that own no network. Mobile virtual operators, resellers, and white-label providers buy wholesale capacity and sell under their own brands, which produces a distinct set of intellectual property arrangements.

The wholesale agreement allocates network access, service levels, and — critically — subscriber data. Who owns the customer relationship, who may market to it, and what happens to the base on termination are the terms that determine the value of the business.

Brand licensing runs both ways. A host carrier licensing its network to a virtual operator may or may not want its brand associated; a virtual operator using a host's coverage claims is making representations about someone else's asset.

Nominative use governs coverage claims. A reseller may accurately say whose network it runs on; it may not present itself as the carrier. See Descriptive and Nominative Fair Use.

Data flows are the hidden asset. A virtual operator generating subscriber data on a host's network needs to know whether the host may use it, and hosts routinely reserve rights that resellers do not notice.

Exit is the recurring dispute. On termination the base must be ported or lost, the branding must be removed, and the data must be dealt with — none of which happens smoothly without terms drafted in advance. See the Reseller, Dealer, and Channel Partner IP Toolkit and the Channel Partner IP Checklist.

Assertion campaigns, and why carriers are targets

Carriers are among the most frequently sued defendants in patent litigation, for reasons that have little to do with what they invented.

They are the visible party. A subscriber uses a handset, on a network, running standardised protocols, over equipment from three vendors. The carrier is the entity with the customer relationship, the revenue, and the name on the building.

The accused instrumentality is often somebody else's. Much of what is asserted against a carrier is implemented in equipment or handsets the carrier bought. That makes vendor indemnity the first question and, frequently, a disappointing one: caps, exclusions for combinations, and control-of-defence provisions all reduce what looks like protection.

Damages theories reach service revenue. A plaintiff whose patent covers a network function will attempt to base damages on subscriber revenue rather than on equipment cost, which makes the apportionment fight under 35 U.S.C. § 284 the centre of the case.

Injunctive risk is asymmetric. An injunction against network operation is catastrophic in a way that damages are not, which is why the eBay Inc. v. MercExchange, L.L.C. factors and, for standards-committed patents, the willing-licensee analysis matter more here than almost anywhere.

Campaigns are serial. A plaintiff who sues one carrier sues all of them, which creates both a coordination opportunity and an information problem: settlements are confidential, comparables are hard to obtain, and each defendant negotiates partly blind.

The practical response is structural. Maintain a defensive file: which vendors indemnify what, with what caps and what control provisions; which standards commitments constrain which likely plaintiffs; what prior art the industry already has from earlier campaigns; and what settlements are known. Build it once, maintain it, and the third campaign costs a fraction of the first.

See the Patent Assertion Defense Toolkit, the Patent Assertion and Litigation Funding Toolkit, and the Claim Construction Toolkit.

The regulatory overlay that shapes every commercial term

Telecommunications is a regulated industry, and the regulation reaches into arrangements that look purely commercial.

Service classification determines the rules. Whether an offering is a regulated telecommunications service, an information service, or something else determines which obligations attach, and the classification has shifted repeatedly. A business built on one classification's assumptions is exposed when it changes.

Universal service and access obligations constrain who must be served and on what terms, which limits the freedom to structure territorial arrangements the way an ordinary licensor would.

Transfer approval reaches transactions. Spectrum, licences, and control changes require regulatory clearance, which means an intellectual property transaction in this sector has a regulatory timeline running alongside it and occasionally over it.

Equipment authorisation is a prerequisite to marketing, and it attaches to the device and to the party that obtained it — a structure closely analogous to aerospace approvals and with the same consequence: the authorisation does not transfer with the design.

Supply chain restriction has become a hard constraint. Rules limiting the use of equipment from designated suppliers have forced replacement programmes, which are simultaneously procurement projects, financing exercises, and intellectual property problems, because the replacement equipment does not run the incumbent's configuration.

Lawful intercept and assistance obligations require capability to be built and maintained, and the technical details are restricted information sitting inside otherwise-commercial equipment agreements.

Consumer protection reaches the marketing. Coverage maps, speed claims, and pricing representations are advertising claims subject to substantiation, and competitors challenge them under 15 U.S.C. § 1125 as readily as regulators do under 15 U.S.C. § 45. See the Advertising and Marketing Law Toolkit.

The practical instruction is that a telecommunications intellectual property practitioner cannot work alone. Every substantial matter needs a regulatory colleague in the room early, because the regulatory answer frequently determines whether the commercial structure is available at all.

Network data as a product, and the line nobody draws

Carriers sit on data of a richness few businesses match: who moved where, when, how often, with what device, using which applications, at what quality. Turning that into revenue is an obvious commercial idea and a compliance minefield, and the sector has repeatedly discovered the minefield after entering it.

Six distinctions matter, and they are routinely collapsed.

Content versus metadata. Content is protected by interception rules under 18 U.S.C. § 2511 and its analogues; metadata is protected by the sector-specific regime and by general privacy law. Different rules, different consents, different enforcement.

Individual versus aggregate. Aggregation reduces exposure and does not eliminate it, because aggregate location products have repeatedly proven re-identifiable, and the representation that a product is anonymised is the representation that fails.

Internal use versus disclosure. Using data to plan a network is materially different from selling it, and consents drafted for the first do not support the second.

First-party versus downstream. A carrier remains accountable for data that passes to aggregators, resellers, and application partners, and the controls that matter are the flow-downs and the audit rights, not the initial contract.

Operational versus commercial purpose. Data collected to run the network and later used for advertising has changed purpose, which is the exact fact pattern the general privacy statutes address and which almost no legacy collection notice covers.

Location versus everything else. Precise location is sensitive-category data in most modern statutes, has been the subject of the sector's most significant enforcement, and deserves its own governance rather than inclusion in a general data policy.

The practical position is unglamorous and durable: build the use matrix, treat location as its own category, put re-identification prohibitions and audit rights into every downstream contract, and require a named approver for any new purpose. A carrier that can produce that matrix on request is in a different position from one that cannot, both with a regulator and with a counterparty.

See the Data Licensing Checklist and the Marketing Privacy Compliance Checklist.

The first meeting

Seven questions asked of a new telecommunications client surface most of what matters, and none requires network engineering knowledge.

What do you own outright? The answer is shorter than the client expects — brand, sites, fibre, customer relationships, internally built software — and articulating it reframes everything that follows.

When does your largest equipment agreement come up for refresh, and who has read it? The terms agreed at the last refresh determine the economics of the next decade, and the person who negotiated them has usually left.

What have your engineers contributed to standards bodies, and under what policy? If there is no policy, there are commitments nobody has recorded.

Show me your declared-patent register — in both directions. Most carriers have neither their own declarations nor a view of what is declared against the standards they implement.

Who receives subscriber data outside the company, and under what terms? The downstream chain is where the enforcement risk sits and where the contracts are thinnest.

Is precise location handled as its own category? If it sits inside a general data policy, it is under-governed relative to both the statutes and the enforcement history.

Who is accountable when a multi-vendor deployment underperforms? If the answer is a committee, the contractual architecture has not caught up with the technical architecture.

Seven questions, forty minutes, and a work plan ordered by exposure. The answers also produce the asset map, which is the document every subsequent conversation depends on and which almost no carrier has.

Handset, device, and the edge of the carrier's estate

The device in a subscriber's hand is not the carrier's, and yet a great deal of the carrier's legal exposure runs through it.

Branding on devices. Carrier marks appear on hardware, in boot sequences, and in preloaded software under licences that are frequently informal and rarely quality-controlled. A mark applied to a product the licensor does not control is the classic naked licensing exposure. See the Trademark License Quality Control Checklist.

Preloaded software. Applications placed on devices by a carrier raise privacy questions, consumer protection questions about removability, and licence questions about the software itself.

Locking and unlocking. Device locks are technological measures, and the rules governing their circumvention have been the subject of specific exemptions. See The DMCA's Other Half and the Anticircumvention and Repair Toolkit.

Trade-in and refurbishment programmes put the carrier into the secondary market, with exhaustion, data-wiping, and warranty consequences. See the Exhaustion and Gray Market Toolkit.

Counterfeit accessories and devices in the retail channel are a trademark problem the carrier owns even where it did not manufacture anything. See the Anticounterfeiting and Border Enforcement Toolkit.

Device-side data collection by the carrier's own applications is subject to the general privacy statutes rather than only the sector-specific regime, which is a distinction operations teams routinely miss.

The unifying point is that the carrier's brand, and therefore its exposure, extends past the network into hardware it does not build and software it does not write. The licences governing that extension are usually the least examined documents in the estate.

A closing observation

The carrier's position is unusual among large technology businesses: it operates critical infrastructure at enormous scale while owning almost none of the technology that makes it work. That is not a failure of strategy. Standardisation is what makes a phone bought in one country work in another, and the licensing regime that accompanies it is the price of that interoperability.

But it does mean the legal work in this sector is disproportionately about other people's rights — reading them, bounding them, and preserving the ability to walk away from them. The carrier that thinks of itself as a technology owner will build a patent programme nobody uses. The carrier that thinks of itself as the largest licensee in its market will read its equipment agreements, run its standards register, document its FRAND negotiations, govern its data, and control its brand across a channel it does not own.

That second carrier is rarer than it should be, and the difference between the two is visible entirely in documents that cost very little to produce and are almost never produced until something has already gone wrong.

The same observation applies, with the parties reversed, to the equipment vendor: its value is concentrated in rights it must commit to license, on terms it does not fully control, to customers who are also its licensors' targets. Both sides of this market are managing dependency rather than owning position, and the practitioner who understands that will draft for exit and for evidence rather than for exclusivity.

Draft for exit, because every arrangement here outlives the people who negotiated it; draft for evidence, because willingness, quality control, and substantiation are all assessed retrospectively from records nobody was keeping at the time.

Those two habits, applied consistently, are worth more to a telecommunications client than any portfolio it could realistically build.

They are also the two habits that survive a change of general counsel, which is the real test of any programme in an industry where the assets outlast the people by decades.

A Suggested Reading Path

Advising a carrier for the first time: The Pipes and the Spectrum, then Advising a Telecommunications or Network Business, then the Telecommunications IP Checklist.

Standards exposure: Licensing or Litigating a Standard Essential Patent, the Standard Essential Patents and FRAND Toolkit, and the IP and Antitrust Toolkit.

Equipment procurement: the Technology Contracts Toolkit, the Software Continuity and Escrow Toolkit, and the Software, Data, and Open Source Toolkit.

Subscriber data: the State Privacy Law Applicability and Readiness Checklist, Standing Up a Multi-State Privacy Compliance Program, and the Marketing Communications Toolkit for the outbound side.

Brand and channel: the Brand Licensing Program Toolkit, the Trademark License Quality Control Checklist, and Structuring a Reseller or Channel Programme.

Assertion defence: the Patent Assertion Defense Toolkit, the Patent Case Assessment Checklist, and the Patent Damages and Remedies Toolkit.

Adjacent sectors: the Space and Satellite IP Toolkit for non-terrestrial networks and the Logistics and Supply Chain Technology IP Toolkit for the network-effects data analysis.

Primary Authorities

| Authority | Use | |---|---| | 35 U.S.C. § 101 | Eligibility for network and signalling method claims | | Alice Corp. v. CLS Bank International | The abstract idea framework applied to protocols | | 35 U.S.C. § 102 | Standards contributions as prior art | | 35 U.S.C. § 103 | Obviousness over a dense standards literature | | 35 U.S.C. § 112 | Definiteness in claims drafted to a specification | | 35 U.S.C. § 271 | Divided infringement across handset, network, and core | | 35 U.S.C. § 284 | Damages and the royalty base question | | 35 U.S.C. § 287 | Marking across a distributed network | | eBay Inc. v. MercExchange, L.L.C. | Injunctions against network operation | | Impression Products v. Lexmark International | Exhaustion and secondary-market equipment | | KSR International Co. v. Teleflex Inc. | Combination obviousness | | Microsoft Corp. v. i4i Ltd. Partnership | The clear and convincing standard on invalidity | | 15 U.S.C. § 1 | Concerted conduct in standardisation and pools | | 15 U.S.C. § 2 | Monopolisation through commitment evasion | | 15 U.S.C. § 45 | Unfair methods and deceptive coverage claims | | 15 U.S.C. § 1125 | Coverage and speed claims between competitors | | 15 U.S.C. § 1114 | Counterfeit network hardware in the channel | | 17 U.S.C. § 102 | Firmware, orchestration, and billing software | | 17 U.S.C. § 106 | Reproduction and distribution in firmware supply | | 17 U.S.C. § 201 | Contractor-developed operational software | | 17 U.S.C. § 204 | The signed writing behind that software | | 17 U.S.C. § 1201 | Feature locks and access controls on equipment | | Google LLC v. Oracle America, Inc. | Interfaces and reimplementation in open interface work | | Feist v. Rural Telephone | Subscriber listings and the limits of compilation protection | | 18 U.S.C. § 1836 | Misappropriation of planning and integration knowledge | | 18 U.S.C. § 1839 | Reasonable measures over network design data | | 18 U.S.C. § 2511 | Interception, and the carrier's position | | 18 U.S.C. § 2702 | Disclosure by providers of communications services | | 18 U.S.C. § 2703 | Required disclosure and process | | FRCP 26 | Protective orders over network and licensing data |

Search the underlying materials directly for FRAND royalty base smallest saleable unit, standard essential patent injunction willing licensee, network equipment feature licensing dispute, carrier location data enforcement, and open RAN interoperability agreement.

Forms and Templates

An asset map, one page, distinguishing what the carrier owns, what it licenses, and what it holds under regulatory grant. Almost no carrier has one and every strategic conversation needs it.

An equipment agreement review template covering feature and capacity licensing, firmware and update terms, end-of-support commitments, resale and transfer, interoperability obligations, escrow, open source disclosure, security provenance, and indemnity scope.

A standards participation policy governing who attends, what may be contributed, what must be disclosed, and how declarations are tracked — because an engineer's contribution creates an obligation the licensing team will live with for twenty years.

A declared-patent register, maintained rather than reconstructed, covering both the company's declarations and the declarations against standards it implements.

A FRAND negotiation file template: the demand, the claim charts, the essentiality assessment, the comparable licences, the counteroffer, and the correspondence — because willingness is assessed from the record.

A subscriber data use matrix, mapping each data category to the sector-specific regime, the general privacy statutes, the internal permitted uses, and the downstream recipients.

A location data annex for any commercial arrangement touching it, with re-identification prohibitions, downstream flow-down, audit rights, and termination consequences.

A wholesale and virtual operator agreement schedule covering base ownership, marketing rights, data use, branding, coverage claims, and exit porting.

A site and tower agreement checklist covering equipment ownership, data from that equipment, branding, access, and decommissioning.

An open source disclosure requirement in every equipment purchase, requiring a machine-readable bill of materials rather than a notices file.

A coverage claim substantiation file, since network performance claims are advertising claims and competitors challenge them.

For general drafting starting points, see the Draft License Agreement and the License Agreement Template.

Five recurring matters

A declared-essential portfolio holder sends a demand. Do not treat it as an ordinary assertion. Assess essentiality claim by claim, request comparable licences, make a counteroffer that is genuine, and document everything — because the injunction analysis will turn on whether the implementer behaved as a willing licensee, and silence reads as unwillingness.

A vendor announces end of support for equipment with years of service life left. Check the contract for support commitments and for source escrow, check whether third-party maintenance is contractually or technically prevented, and check whether the feature licences survive a transfer to a secondary-market buyer. The exhaustion analysis limits what patent law can do to stop resale; the contract and the software locks are what actually bind.

A location data product is found to be re-identifiable. This is simultaneously a regulatory matter under the sector-specific regime, a privacy matter under the general statutes, a contractual matter with every downstream purchaser, and a representation problem. Sequence it: stop the flow, preserve, assess notification obligations, then deal with the contracts.

A multi-vendor deployment underperforms and nobody is accountable. The remedy is contractual architecture rather than litigation: a named integration authority, service levels measured end to end, and remedies that do not require proving which vendor's element failed.

A virtual operator terminates and wants its base. Porting mechanics, branding removal, and data deletion all need to have been agreed in advance. Where they were not, the host holds the operational leverage and the reseller holds the customer relationships, which produces a settlement rather than a resolution.

Advising the four kinds of client

The carrier. Owns spectrum grants, sites, customers, and a brand; licenses everything else. Its priorities are equipment agreement terms, standards exposure as an implementer, subscriber data governance, and brand licensing discipline across its channel. Its characteristic error is treating a decade-long equipment relationship as a procurement rather than as a licensing arrangement, and discovering at refresh that the capacity it needs costs more than the hardware did.

The equipment vendor. Holds patents, contributes to standards, and sells hardware whose value is increasingly in software. Its priorities are declaration discipline, feature-licensing enforceability, open source compliance in firmware, and supply-chain provenance. Its characteristic error is allowing engineering contributions to standards without a policy, creating commitments the licensing team must honour indefinitely.

The tower or infrastructure company. Owns physical assets and hosts other people's equipment. Its priorities are site agreement terms, data generated on its structures, branding, and decommissioning. Its characteristic error is treating itself as a landlord when it is increasingly a data business.

The network software business. Sells orchestration, analytics, or virtualised functions. Its priorities are the open source position, customer data rights, interoperability claims, and the indemnity it can realistically offer in a disaggregated stack. Its characteristic error is offering an unqualified patent indemnity in a sector where the assertion risk is systemic and standards-based.

A short glossary

Spectrum licence. A conditional regulatory grant, not property, transferable only with approval.

Declared-essential patent. A patent its holder has declared necessarily infringed by implementing a standard. A declaration, not a determination.

FRAND commitment. The undertaking to license on fair, reasonable, and non-discriminatory terms, generally analysed as a contract benefiting implementers.

Royalty base. What the percentage is applied to — a component, a module, or the end device. The central rate-setting dispute.

Willing licensee. The implementer conduct standard that determines injunction availability. Assessed from the negotiation record.

Feature licence. Payment to enable capability already present in purchased hardware.

End of support. The date after which a vendor stops maintaining equipment, converting a technical asset into a security and contractual problem.

Indefeasible right of use. A long-term capacity grant in fibre or conduit, structured as a licence and behaving like a lease.

Interconnection agreement. The regulated arrangement by which carriers exchange traffic, carrying confidentiality obligations over traffic data.

Subscriber proprietary information. The sector-specific category of customer usage data, protected by a regime older than general privacy law.

Virtual operator. A retail provider using another carrier's network under wholesale terms.

Disaggregation. The separation of network functions across multiple suppliers via published interfaces.

Network function virtualisation. Replacement of purpose-built hardware with software on general-purpose compute.

Lawful intercept. Mandated interception capability, itself sensitive technical information.

What good looks like

An asset map exists, distinguishing owned, licensed, and regulatory-grant assets, and it is used in strategic discussions rather than filed.

Every equipment agreement has been reviewed against one template, so the carrier knows across its estate what it may do, for how long, and at what marginal cost.

A standards policy governs contribution and declaration, and a register tracks both directions.

FRAND negotiations are documented as they happen, because willingness is assessed retrospectively from a record nobody was thinking about at the time.

Subscriber data uses are mapped against both regimes, with location data handled as its own category and downstream recipients enumerated.

Brand licences to resellers carry real quality control, exercised and recorded, rather than recited.

Internally developed software has signed assignments, which is a five-minute check that fails surprisingly often.

The disaggregated stack has a named integration authority and end-to-end service levels, so that accountability survives the loss of the single-vendor model.

Carriers with those eight features negotiate refreshes from a position and answer assertions from a file. Carriers without them discover that the most important terms in the business were agreed a decade ago by a procurement team optimising for the hardware price.