Telecommunications IP Checklist: Spectrum and Licence Conditions, Equipment and Firmware Terms, Interconnection Agreements, Standards Exposure, and Subscriber Data

By Casey Scott McKay · 2026-04-07

This checklist audits the intellectual property position of a carrier or network operator in the order the questions arise. It begins with the asset register, because a carrier's position consists largely of licensed rather than owned assets and no single document lists them. It then works through spectrum licence conditions, equipment and firmware terms, the standard essential patent exposure vendor licences do not reach, interconnection and wholesale agreements, subscriber data and consent architecture, network trade secrets, carrier-developed software, the brand channel, and the transaction file. Gate items mark the points at which work should stop until a specific artefact exists.

IP and Technology > Information Technology | Checklist | Published 7 April 2026 - Updated 1 June 2026 | Casey Scott McKay - marksy.us

Summary. This checklist audits the IP position of a carrier or network operator in the order the questions arise. It begins with the asset register, because a carrier's position consists largely of licensed rather than owned assets and no single document lists them. It then works through spectrum licence conditions, equipment and firmware terms, the standard essential patent exposure vendor licences do not reach, interconnection and wholesale agreements, subscriber data and consent architecture, network trade secrets, carrier-developed software, the brand channel, and the transaction file. Gate items mark where work should stop.

Keywords: telecommunications checklist · spectrum conditions · build-out obligations · firmware licence survival · third party maintenance · IP indemnity cap · vendor licence scope · network method claims · FRAND commitments · interconnection confidentiality · MVNO integration ownership · CPNI consent audit · location data controls · dealer trademark audit · network trade secrets

How to use this checklist

| Phase | What it produces | Who runs it | Gate | |---|---|---|---| | 1. Register | One consolidated view of licensed and owned assets | Counsel | Register exists before any negotiation | | 2. Spectrum | Conditions extracted and owned by a named person | Regulatory and counsel | Build-out position confirmed in writing | | 3. Equipment | Firmware, feature, data, and indemnity terms fixed | Procurement and counsel | IP indemnity outside the general cap | | 4. Standards | Written vendor licence scope per product line | Counsel | Network-level exposure identified | | 5. Interconnection | Technical-data confidentiality and data allocation | Wholesale and counsel | No template confidentiality for topology | | 6. Subscriber data | Consent mapped to every use | Privacy and counsel | No data product without supporting consent | | 7. Trade secrets | Named categories with real measures | Network ops and counsel | Route data protected | | 8. Software | A filing and secrecy decision | Counsel | Decision made rather than defaulted | | 9. Brand | Channel audit and quality control layer | Brand and counsel | Licensee use controlled | | 10. Transaction | Six answers supported by documents | Counsel | All six answered |

The matter. A regional carrier holds spectrum in three bands, operates equipment from four vendors, hosts two mobile virtual network operators, sells through 140 authorised dealers, and has recently launched an analytics product built on aggregated subscriber location data. The equipment contracts were negotiated by procurement. The IP indemnity is inside the general liability cap. Nobody has read the build-out conditions since the auction. An acquisition approach arrived last week.

Phase 1. Build the register

[ ] Consolidate spectrum licences with their conditions, not merely their identifiers and expiry dates.
[ ] Summarise each equipment agreement's IP terms: firmware licence scope and survival, third-party maintenance rights, feature licence behaviour, configuration data ownership, indemnity scope, and indemnity cap.
[ ] Record standards participation and any licensing commitments the company has made.
- Why. Commitments made through standards participation run with the patents and bind assignees, and they appear in diligence far more often than in the company's own records.
[ ] Inventory open source obligations by network element, including whether the company is a distributor of any build.
[ ] List the trademark portfolio and every licensee — dealers, agents, resellers, device manufacturers, wholesale customers — with the quality control mechanism applied to each.
[ ] Name the trade secret categories with an owner and an access position for each.
[ ] Reconcile the patent portfolio, including anything acquired historically or through acquisition, against current maintenance decisions.
[ ] [Gate] The register exists in one document before any vendor negotiation, wholesale deal, or transaction process begins.

Phase 2. Read the spectrum licences for what they constrain

[ ] Extract every build-out obligation with its date, and confirm the current position against it in writing.
- Trap. Missing a build-out milestone can cost the licence, and remedies for partial performance are discretionary. A licence with an unmet obligation is an asset with a capital commitment attached that often exceeds the auction price.
[ ] Name the person inside the business tracking each obligation. If no name exists, that is the finding.
[ ] Confirm power and interference constraints with radio engineering, because two licences in adjacent bands support different architectures and a plan built on the wrong assumption fails its first engineering review.
[ ] Record transfer approval requirements and realistic timelines, since assignment requires regulatory approval that takes months and can carry conditions.
[ ] State the renewal assumption explicitly where the business case runs longer than the licence term, because renewal expectancy is policy rather than entitlement.
[ ] Record any sharing, coordination, or priority-tier obligation, which determines practical availability in a way a static grant does not and changes more often than licences renew.
[ ] Review any lease arrangement for who bears the build-out obligation, what happens on non-renewal, and who holds the regulatory relationship.
[ ] [Gate] No financing pledges spectrum and no transaction timetable is fixed until the transfer approval position is written down.

Phase 3. Fix the equipment and firmware terms

[ ] Confirm the firmware licence is perpetual and does not terminate with support.
- Why. A licence coterminous with the support agreement converts a capital asset into a rental and hands the vendor every renewal negotiation.
[ ] Negotiate third-party maintenance rights after a defined period, with access to the diagnostic tooling required to exercise them.
- Trap. Vendors resist through licence terms, access controls, and parts refusal. Access controls engage 17 U.S.C. § 1201 with its triennial exemption process, and post-sale restrictions run in contract rather than patent after Impression Products, Inc. v. Lexmark International, Inc. — which means the contract is where this is won, and only at negotiation.
[ ] Fix feature licence behaviour at renewal, at non-renewal, and on the vendor's acquisition, because deployed capacity dependent on annual licence keys is an operational dependency that should be priced.
[ ] Confirm carrier ownership of configuration and performance data, with a documented extraction format and bounded vendor use.
[ ] Carve third-party IP claims out of the general liability cap, or negotiate a separate and substantially higher cap.
- Why. A capped indemnity against a portfolio assertion is not an indemnity, and the cap is the only number that matters when a claim arrives.
[ ] Confirm the indemnity covers use in the network, not merely the equipment as sold, and extends to combination claims where the combination was contemplated.
[ ] Obtain source escrow with tested build verification for anything whose vendor failure would be an operational catastrophe. Untested escrow is theatre.
[ ] Require a bill of materials with licence identification for each firmware release.
[ ] [Gate] No equipment contract is signed with the IP indemnity inside the general cap.

Reading an equipment agreement in one pass

Ten questions, answered from the document rather than from the account manager, tell you what the contract actually does.

Is the software licence perpetual? Find the grant, then find the termination provision, then check whether the grant is expressed to survive. Many are not.

What happens on support lapse? Some licences terminate. Some continue but forbid updates. Some continue and permit updates already delivered. The three positions produce very different networks five years out.

May a third party maintain the equipment? Look for restrictions on who may access diagnostic software, who may hold spares, and whether the warranty is voided by third-party service.

How do feature licences behave on non-renewal? Do enabled features remain enabled, revert, or disable? Is capacity a permanent grant or an annual one?

Who owns the configuration? The network as configured is the carrier's design work. Confirm it is not swept into a vendor ownership clause covering "materials generated by the equipment."

Who owns performance data, and what may the vendor do with it? Vendors increasingly build analytics products from customer telemetry, and the right to do so is granted in a clause nobody negotiated.

What does the IP indemnity cover? Equipment as sold, equipment as used, or the network in which it operates. Combination claims or not. Defence and settlement control, or reimbursement only.

Is the indemnity capped, and where? Inside the general cap, in a separate cap, or uncapped. This is the answer that matters most.

What are the escrow terms, and has the deposit ever been verified? A deposit receipt is not a remedy.

What open source is in the build, and has a bill of materials been supplied? The carrier's rights to copyleft components exist independently of the vendor, and asking is both a compliance step and a continuity measure.

[ ] Answer all ten for each major vendor and record them in the register.

Phase 4. Locate the standards exposure accurately

[ ] Obtain a written statement from each vendor of what its licences cover: system-level or component-level claims, and whether they authorise the carrier's operation of the equipment in a network.
- Why. Quanta Computer, Inc. v. LG Electronics, Inc. exhausts a patent as to a component substantially embodying the invention, and Impression Products confirms authorised sales exhaust regardless of restrictions or location — but whether a component substantially embodies a given invention is a claim-by-claim fact question.
[ ] Identify network-level method claims — handover, scheduling, session management, interference coordination — which are practised by the operator and reached by an equipment licence only if it says so.
[ ] Identify service-level claims, practised by the carrier as a service provider and outside any equipment licence.
[ ] Identify combination claims reading on a multi-vendor network, where no single vendor's licence covers the combination.
[ ] Record the FRAND position: a patent declared essential carries a licensing commitment generally treated as enforceable by implementers as third-party beneficiaries, and remedies are governed by the four-factor test in eBay Inc. v. MercExchange, L.L.C., which a FRAND-committed patentee rarely satisfies against a willing licensee.
[ ] Check what the carrier has committed through its own standards participation.
[ ] Run freedom to operate on customer-facing systems before deployment, since billing, self-service, messaging, content delivery, and fraud detection are the assertion targets.
[ ] Keep architecture documentation current so the eligibility defence under 35 U.S.C. § 101 and Alice Corp. v. CLS Bank International stays viable, since an early eligibility motion is the most cost-effective defence available in this category.
[ ] [Gate] The network-level and service-level exposure is documented before the next equipment renewal.

Where assertions actually land

[ ] Allocate defence budget by category rather than by assumption. Five categories, roughly in order of volume against operators.
[ ] Non-practising entity assertions against network operation. The largest category. Patents frequently acquired from operating companies, claims directed to methods performed in the network or in the service, and the carrier chosen as defendant because it is the carrier. The vendor indemnity often does not respond.
[ ] Assertions against customer-facing systems — billing, portals, messaging, content delivery, fraud detection, identity products. Software claims facing the eligibility screen, where an early motion is the most cost-effective defence available.
[ ] Standard essential patent assertions. Less frequent against operators than device makers, expensive when they arrive, complicated by supply chain licensing structure.
[ ] Inherited exposure from acquisitions. Acquired networks bring equipment purchased under weak indemnities and services built on unexamined software. Carrier diligence weights regulatory and spectrum matters heavily and treats IP as a schedule.
[ ] Trade secret claims from vendors and former employers. Rarer but serious, and defended by the documented onboarding process in Phase 7.
[ ] Confirm the four mitigations that work across all five: know what the vendor indemnities cover; keep customer-facing architecture documentation current; run genuine IP diligence on acquisitions; and paper onboarding.

Phase 5. Rewrite interconnection and wholesale terms

[ ] Allocate the signalling and traffic records interconnection generates: who retains them, for how long, and for what purposes.
[ ] Name routing, capacity, and topology information as protected categories in the confidentiality clause rather than relying on a commercial template.
- Trap. This is trade secret material disclosed under a clause drafted for pricing terms, and the mismatch is invisible until someone tries to enforce it.
[ ] Address roaming records across jurisdictions: who holds them, who may use them, and whose law governs, since the framework at 47 U.S.C. § 222 was not drafted for foreign subscribers on a domestic network.
[ ] Settle MVNO integration ownership. Whoever owns the integration controls migration; a host that owns it holds the relationship, and an MVNO that owns it holds a portable asset the host funded.
[ ] Allocate MVNO subscriber data expressly, remembering the host's obligations under 47 U.S.C. § 222 and 47 C.F.R. § 64.2001 attach regardless of commercial allocation.
[ ] State whether the host may use MVNO traffic patterns, growth, churn, and usage profile competitively.
[ ] Define the exit: number portability, data return, and the fate of provisioning integrations. A relationship with no exit has renewal terms that write themselves.
[ ] Use a technical-data confidentiality regime for infrastructure sharing with named categories, access limits, and return or destruction, and allocate ownership of anything jointly developed.
[ ] Scrutinise IRU and dark fibre terms for resale rights, insolvency consequences, and what the grantor learns about the grantee's network design.
[ ] [Gate] No wholesale agreement is signed without the four MVNO terms resolved.

Long-haul, cable, and site infrastructure

[ ] Classify route information as a protected category: where fibre runs, where splice points sit, and what the real diversity is between two nominally separate paths.
- Trap. It is disclosed to contractors, to enterprise customers demanding diverse routing, to permitting authorities, and to regulators as a matter of routine, which means a carrier that has never asked whether it is protected has answered by conduct.
[ ] Review indefeasible rights of use for resale rights, insolvency consequences, and what the grantor learns about the grantee's network design from the traffic carried.
[ ] Read consortium agreements for submarine builds, which allocate rights in the design, the marine engineering, and the seabed survey data. Survey data is expensive, reusable across future builds, and frequently allocated by silence.
[ ] Check landing station and site terms for physical security information, power and cooling design, and access arrangements governed by a property lease rather than a technical-information agreement.
[ ] Review maintenance pooling arrangements, since shared failure records describe each participant's network weaknesses in detail.
[ ] Check tower and site agreements for data terms, because a tower company accumulating rights to network performance data has acquired something valuable that nobody priced.

Roaming and international

[ ] Identify which records cross borders and under what legal basis.
[ ] Confirm the retention position for foreign subscribers' records held on the domestic network.
[ ] Check whether the roaming agreement addresses competitive use of the traffic patterns it reveals.
[ ] Confirm the technical disclosures made to establish roaming — network configuration, capability signalling, and interconnect topology — are covered by terms drafted for technical data.

Phase 6. Audit subscriber data and consent

[ ] Map the perimeter of customer proprietary network information under 47 U.S.C. § 222, with the notice, consent, safeguard, and breach-reporting detail from 47 C.F.R. § 64.2001 and following.
[ ] Map every data use in the business against the consent that supports it.
- Why. Consent obtained for service provision does not authorise analytics or advertising products, and rebuilding consent flows is a product exercise with a long lead time.
[ ] Treat location data as its own category with access logging, purpose limitation, and a documented process for legal demands.
- Trap. Carpenter v. United States held that acquiring historical cell-site location information is a search, which reframed both the response process and the industry's understanding of the record's sensitivity.
[ ] Reconcile the state privacy overlay into one operational process rather than running parallel programmes with different vocabularies.
[ ] Obtain a technical de-identification assessment for any aggregation product, since location traces are distinctive enough that naive aggregation does not de-identify them.
[ ] Separate regulated from unregulated data, because the boundary is drawn around service definitions rather than around systems and a single record supporting both is a problem waiting to be found.
[ ] Check preloaded and carrier-branded applications, which collect on the carrier's account even where a vendor wrote them.
[ ] [Gate] No data product launches without a documented consent basis for each input.

The numbering and identity layer

[ ] Record which resources are administered rather than owned. Numbers are allocated under regulatory arrangements and portable as a matter of obligation, which means they cannot function as a retention mechanism and the systems supporting portability are compliance infrastructure rather than product.
[ ] Assess the remote provisioning position. Software-issued credentials shift leverage toward the device owner, and the governing specifications are standardised — which brings the licensing questions in Phase 4 into the identity layer.
[ ] Locate authentication and anti-fraud products on the regulatory map. They are built on carrier-held identity signals, they are commercially attractive, and they sit precisely on the boundary between a regulated network function and an unregulated data product — the boundary the consent architecture in Phase 6 must be designed around.
[ ] Confirm what the identity product discloses to its customers, since a verification signal derived from subscriber data is a disclosure of that data in a compressed form and the analysis under 47 U.S.C. § 222 does not turn on the compression.
[ ] Check the terms on which identity signals are supplied to enterprise customers, including whether the customer may retain, aggregate, or resell them.

Phase 7. Protect network knowledge as trade secret

[ ] Name the categories: network design and configuration standards; capacity models; radio optimisation parameters; traffic analyses; fibre and cable route information including diversity and splice points; fault correlation knowledge; wholesale pricing models; and churn and behaviour models.
[ ] Establish who holds each and who has access, expecting more contractors and vendors than anyone anticipates, because network operations is heavily outsourced.
[ ] Apply real measures: marking at creation, role-based access, and disclosure to vendors under terms specific to technical data rather than a general commercial confidentiality clause.
- Why. The reasonable measures element of 18 U.S.C. § 1839 is satisfied by what was done, and an unmarked network diagram sent to four vendors under a purchase-order clause is not protected.
[ ] Give route information particular attention, since it is disclosed to contractors, enterprise customers, permitting authorities, and regulators as a matter of routine.
[ ] Run an exit process for departing network engineers: access revocation, device return, and a documented interview covering the named categories.
[ ] Screen incoming hires with a written acknowledgement that they will not bring or use a former employer's confidential material.
[ ] [Gate] Route and optimisation data are marked and access-limited before the next contractor engagement.

Phase 8. Decide the position on carrier-developed software

[ ] Ask the network automation and IT teams what problems they solved in the last two years, rather than what inventions they made. Engineers do not think in inventions.
[ ] Screen candidates for eligibility. Network management and orchestration claims survive the Alice analysis when they recite specific technical improvements to network operation — reducing signalling load, improving handover reliability, allocating resources by a defined mechanism — rather than desired outcomes.
[ ] Confine claims to one actor, since methods distributed across elements operated by different entities run into Limelight Networks, Inc. v. Akamai Technologies, Inc..
[ ] Keep as trade secret what is not observable from outside, which is most operational automation, because its value lies in accumulated tuning rather than in a claimable mechanism.
[ ] Handle open source obligations in carrier-written software, particularly where it is supplied to enterprise customers or embedded in equipment delivered to them, since distribution triggers the obligations attaching under 17 U.S.C. § 106 and the component licences.
[ ] Confirm contributor assignment for internally developed software, including contractors.
[ ] Address the virtualisation licensing metric — per instance, per capacity, per subscriber, or per core — since a metric designed for hardware behaves badly under elastic scaling.
[ ] Negotiate deployment portability expressly, because licences frequently restrict virtualised functions to named hardware, clouds, or geographies.
[ ] [Gate] The filing and secrecy position is a recorded decision, not a default.

Virtualisation, in four questions

[ ] What is the licensing metric, and how does it behave under elastic scaling? Per instance, per capacity, per subscriber, or per core. A metric designed for a hardware world produces surprising invoices when a virtualised core scales during a traffic event, and the carrier should know the number before the event rather than after it.
[ ] Is deployment portable? The premise of virtualisation is that a function runs anywhere; licences frequently restrict it to named hardware, named clouds, or named geographies. Negotiate portability expressly, because it is the property the architecture was chosen for.
[ ] What open source is load-bearing? Orchestration platforms, container runtimes, and management stacks are open source, which means the operational core is governed by licences the carrier must comply with and did not negotiate. Build the inventory before an enterprise customer requests it.
[ ] Where has vendor lock migrated to? The old lock was hardware; the new lock is orchestration, and it is stickier, because migrating an automation platform means re-implementing years of accumulated operational logic. Negotiate configuration and workflow portability at the orchestration layer specifically, and treat an orchestration contract with no export path as a longer commitment than its stated term.

Phase 9. Audit the brand channel

[ ] Audit dealer and agent use for marks used outside the agreement, after termination, or on services the carrier does not provide.
[ ] Confirm a quality control layer exists over every licensed use.
- Trap. A certification programme testing only radio performance is a licensing programme with no quality control over branded use, which supports an abandonment argument under 15 U.S.C. § 1064.
[ ] Run a takedown workflow for account fraud sites offering bill payment, plan changes, or unlocking under the carrier's mark, with registrar and hosting complaints as the fast path and 15 U.S.C. § 1114 and 15 U.S.C. § 1125 as the underlying claims.
[ ] Write a nominative use policy and follow it, because a large legitimate market uses carrier marks to describe compatibility and over-enforcement produces adverse decisions.
[ ] Record marks with customs and enrol in marketplace programmes for counterfeit accessories, where the harm is partly a safety harm.
[ ] Address refurbished device disclosure, since the analysis turns on whether the resold article is materially different from the original and accurate disclosure is what keeps the programme lawful.
[ ] Review unlocking policy for consistency, covering both whether the lock is an access control under 17 U.S.C. § 1201 and how third-party unlocking services referencing the mark are treated.
[ ] [Gate] No dealer agreement renews without the quality control mechanism specified.

Devices, accessories, and the retail end

[ ] Review the device lock and unlocking policy for consistency, covering whether the lock is an access control whose circumvention engages 17 U.S.C. § 1201 and how third-party unlocking services referencing the carrier's marks are treated.
- Trap. Inconsistent enforcement against nominative use is what produces adverse decisions, and a written policy applied uniformly is worth more than aggressive one-off actions.
[ ] Audit preloaded carrier-branded applications for their own IP position, their open source obligations, and their data practices, since an app collecting subscriber data does so on the carrier's account under 47 U.S.C. § 222 whoever wrote it.
[ ] Confirm the device certification programme includes a quality control layer over branded use, not only radio performance testing.
[ ] Record marks with customs and enrol in marketplace enforcement programmes for counterfeit chargers, cables, and batteries, where the harm is partly a safety harm and the volume defeats individual litigation.
[ ] Confirm refurbished device disclosure is accurate and prominent, since the analysis turns on whether the resold article is materially different from the original.
[ ] Check retail signage and dealer marketing against the licence terms, which is where the most uncontrolled branded use occurs.

Convergence, and what it does to this checklist

[ ] Re-run the checklist per product line rather than per network once the business sells content, cloud, security, identity, or enterprise software.
- Why. A carrier selling a security product faces assertions aimed at security software, and no network equipment indemnity reaches them. Each new line arrives with its own assertion landscape and typically without its own freedom-to-operate work.
[ ] Identify whether the business now contains a software company with filing decisions, contributor assignment questions, open source obligations, and employee mobility problems it has not built processes for.
[ ] Draw the regulated/unregulated data boundary explicitly, since the obligations under 47 U.S.C. § 222 attach to a service definition rather than to a system, and state privacy law overlays both with a different vocabulary.
[ ] Ask each product line the same four questions: what do we own, what do we license, what do we disclose, and who could assert against us.

Phase 10. Assemble the transaction file

[ ] Answer the six questions in writing: what the spectrum licences require; what the equipment indemnities cover and whether they are capped; what network-level and service-level exposure no vendor licence addresses; what the company has committed through standards participation; what consent supports each subscriber data use; and what the trademark licensing position is in the channel.
[ ] Support each answer with documents, not a memorandum summarising documents that do not exist.
[ ] Assemble the encumbrance list: standards commitments, spectrum conditions, exclusivity arrangements, security interests, and any government funding obligation.
[ ] Confirm chain of title for any patent portfolio, particularly assets acquired through prior transactions.
[ ] Stage data room access so competitively sensitive network information is not disclosed to a reviewer whose principal may walk away.
[ ] Reconcile the open source inventory, since a buyer will ask and an incomplete answer is treated as an unknown liability.
[ ] [Gate] The file is complete when all six answers are supported by documents.

A note on order

The phases are ordered by dependency and by cost of delay, not by importance.

The register is first because every later phase reads from it and because the three most expensive findings in a carrier audit — an indemnity cap, an unmet build-out obligation, and an unexamined standards commitment — surface during its construction rather than during the analysis that follows.

The spectrum and equipment phases come next because both are governed by documents that renew on fixed cycles. A term that can be fixed at renewal cannot be fixed between renewals, which means the value of the work depends entirely on when it happens relative to the contract calendar. Counsel arriving three months before a major equipment renewal should reorder this checklist and start at Phase 3.

The standards phase follows equipment because the written vendor licence statements are obtained through the same procurement relationship, and asking both sets of questions in one conversation is more effective than opening two.

Interconnection and subscriber data sit in the middle because both are ongoing programmes rather than one-time exercises, and both take a quarter or more to change.

Trade secrets, software, and brand come later not because they matter less but because they are internal: nothing external forces the timing, which means they are the phases most likely to be deferred and the phases where deferral is least visible. A carrier that never does Phase 7 will not notice, and its route data will simply become known.

The transaction file is last because it is a compilation of everything above. Assembling it first produces a document of assertions, and a buyer's counsel who finds one unsupported assertion discounts the remainder.

Outcome. A carrier that has run this checklist can say what its spectrum licences oblige it to build and by when, whether its equipment indemnities would respond to a portfolio assertion, which claims against its network no vendor licence reaches, whether its analytics product rests on consent that supports it, and whether 140 dealers are using its marks under any quality control at all. Those five answers determine both what the business is worth and what it can safely do next, and none of them lives in the network operations centre.

Key Authorities at a Glance

| Authority | What it settles | Phase | |---|---|---| | 47 U.S.C. § 222 | Confidentiality duty for customer proprietary network information | 5, 6, 10 | | 47 C.F.R. § 64.2001 | CPNI notice, consent, safeguards, and breach reporting | 5, 6 | | Carpenter v. United States | Acquiring historical cell-site location information is a search | 6 | | Quanta Computer, Inc. v. LG Electronics, Inc. | Sale of a component substantially embodying the invention exhausts | 4 | | Impression Products, Inc. v. Lexmark International, Inc. | Authorised sale exhausts regardless of post-sale restrictions | 3, 4 | | eBay Inc. v. MercExchange, L.L.C. | Four-factor test for injunctive relief | 4 | | Alice Corp. v. CLS Bank International | Two-step eligibility framework | 4, 8 | | 35 U.S.C. § 101 | Patentable subject matter | 4, 8 | | Limelight Networks, Inc. v. Akamai Technologies, Inc. | Single-actor requirement for direct infringement | 8 | | 35 U.S.C. § 271 | Acts of infringement | 4, 8 | | 17 U.S.C. § 1201 | Circumvention and the triennial exemptions | 3, 9 | | 17 U.S.C. § 106 | Exclusive rights including distribution | 8 | | 18 U.S.C. § 1839 | Reasonable measures element of trade secret status | 7 | | 15 U.S.C. § 1064 | Cancellation, including for abandonment | 9, 10 | | 15 U.S.C. § 1114 | Infringement of a registered mark | 9 | | 15 U.S.C. § 1125 | False designation of origin and dilution | 9 | | 35 U.S.C. § 112 | Written description and enablement | 8 |

The five things people get wrong

One: treating the IP indemnity as a boilerplate term. Equipment contracts are negotiated on price, delivery, and service levels, and the intellectual property indemnity is accepted as drafted — usually inside a general liability cap set as a multiple of annual fees. When a portfolio assertion arrives, that cap is the whole of the protection, and it bears no relationship to the exposure. Carving third-party IP claims out of the cap is a single sentence, it is achievable at negotiation, and it is unavailable afterwards.

Two: assuming the vendor's licence covers the network. It usually covers the box. The claims that produce carrier litigation are directed to methods performed across the network or to the service delivered to subscribers, and neither is addressed by an equipment purchase. The exhaustion doctrine helps where the component substantially embodies the invention, but that is a claim-by-claim question, and a carrier that has never asked its vendors what their licences reach does not know where its exposure sits.

Three: reading the spectrum licence once, at auction. The conditions attached to a spectrum grant — build-out obligations, power limits, coordination duties, transfer approval, sharing regimes — constrain the business continuously and are consulted almost never. A carrier that cannot state its current build-out position against its obligations has an asset it may lose and a capital commitment it has not priced.

Four: using a commercial confidentiality clause for technical disclosure. Interconnection, infrastructure sharing, and wholesale relationships require disclosing routing, capacity, and topology information — genuinely secret material of real competitive value — under clauses written to protect pricing terms. The mismatch is invisible until someone tries to enforce, and by then the material has been in a counterparty's systems for years without marking, access limits, or a return obligation.

Five: building a data product before auditing consent. Subscriber data is the one asset a carrier genuinely holds, and what may be done with it depends entirely on the consent obtained. Consent taken for service provision does not authorise analytics or advertising, and rebuilding consent flows is a product exercise measured in quarters. A commercial team that commits to a data product before the audit has committed to a timeline the compliance position cannot meet.