Automotive, Mobility, and Connected Vehicle IP Toolkit: Data, Suppliers, Software, and Parts

By Casey Scott McKay · 2023-12-31

A modern vehicle is a computer that generates data continuously, assembled from components supplied by dozens of tier one and tier two vendors, sold to an owner who expects to repair it and increasingly asked to subscribe to features it already contains. This toolkit collects the intellectual property and data questions that arrangement produces. It works through ownership of vehicle-generated data across the manufacturer, the supplier, the dealer, the driver, and the fleet operator; the supplier agreements that decide who owns embedded software and the improvements made to it; feature licensing and over the air updates as a contractual rather than a product question; and the aftermarket, where design filings, software authentication, and repair legislation collide. It closes on standard essential patents, which reached automotive later than telecoms and with less settled practice.

IP and Technology > Information Technology | Toolkit | Published 31 December 2023 - Updated 22 July 2026 | Casey Scott McKay - marksy.us

Summary. A modern vehicle is a computer that generates data continuously, assembled from components supplied by dozens of vendors, sold to an owner who expects to repair it and increasingly asked to subscribe to features it already contains. This toolkit collects the intellectual property and data questions that arrangement produces: ownership of vehicle-generated data across manufacturer, supplier, dealer, driver, and fleet; the supplier agreements that decide who owns embedded software; feature licensing and over the air updates as a contractual question; the aftermarket, where design filings, software authentication, and repair legislation collide; and standard essential patents, which reached automotive later than telecoms and with less settled practice.

Keywords: connected vehicle toolkit · vehicle data rights · telematics privacy · tier one supplier IP · automotive software licensing · feature subscriptions · over the air updates · right to repair vehicles · parts pairing · standard essential patents in automotive · event data recorder · driver monitoring · fleet data licensing · dealer data · aftermarket access

Start Here

A vehicle now produces more legally interesting output than the vehicle itself. Location traces, driving behaviour, cabin audio and video, biometric attention data, diagnostic codes, charging patterns, and — in advanced systems — sensor data used to train the next generation of the product.

Four constituencies claim that output. The manufacturer, which built the system and wants the training data. The supplier, whose sensor and software produced it. The owner or driver, who generated it and is a data subject. And the fleet operator, dealer, insurer, or platform whose commercial arrangements assume access.

The contracts rarely settle the question, because vehicle programmes are negotiated as component supply arrangements by people thinking about parts per million defect rates rather than about data licences.

Three further structural features shape everything else.

The supply chain is deep and old. Tier one suppliers integrate tier two components, programmes run for a decade, and the intellectual property terms in a platform agreement signed six years ago govern a feature invented last year.

Software is now the product. Vehicles ship with software that is updated after sale, features that activate by subscription, and functionality that can be added, removed, or degraded remotely — which converts a sale into an ongoing relationship the sales contract did not describe.

And the aftermarket is politically active. Repair legislation, dealer franchise law, and insurance salvage rules all constrain what a manufacturer may do with parts pairing and diagnostic access, and this is one of the few areas of intellectual property practice where legislative change arrives faster than case law.

This toolkit works through data, suppliers, software, aftermarket, and standards, in that order.

Vehicle Data: Who Owns What the Car Knows

Start by rejecting the framing. There is no property right in data as such in United States law. Databases attract thin copyright at best after Feist Publications, Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991), which requires originality in selection or arrangement and excludes facts themselves.

So "ownership" of vehicle data is really four questions. Who holds it; who is contractually permitted to use it and for what; what privacy law permits; and whether any of it is a protectable trade secret.

Contract does most of the work. The supplier agreement, the vehicle purchase or lease terms, the connected services terms of use, the dealer agreement, and the fleet contract each grant or withhold rights, and they are frequently inconsistent with one another.

Privacy law constrains all of it. Vehicle data is frequently personal data: location is identifying, driving behaviour is behavioural, cabin video and driver monitoring are biometric in several state regimes, and comprehensive state privacy statutes now reach vehicle manufacturers directly, with sensitive data categories, consent requirements, and rights of access and deletion.

Event data recorders have their own regime, with statutory restrictions in many states limiting access to the owner's consent, a court order, or specified safety and research purposes.

Trade secret protection is available for the derived layer. Raw telemetry from a vehicle in the field is not secret in any useful sense, but the aggregated dataset, the labelling, the feature engineering, and the models trained on it can satisfy 18 U.S.C. § 1839 if reasonable measures are taken.

Which produces the practical architecture. Do not claim to own data. Contract for the rights you need — collect, transmit, store, analyse, aggregate, license, and train — for defined purposes, with a defined term, and with express treatment of derived and aggregated outputs. Then protect the derived layer as a secret and document the measures.

Supplier Agreements and Embedded IP

The tier one relationship is a contract manufacturing relationship with software in it, and it fails in the same places.

Background and foreground. The supplier brings platform technology it will not assign; the programme generates developments that both parties want. Allocate background, foreground, and improvements separately rather than assigning everything to the manufacturer, which suppliers will not accept and local law may not enforce.

Embedded software ownership. Most vehicle software is supplier-owned and manufacturer-licensed, which is workable until the manufacturer wants to change suppliers, port a feature, or update a vehicle whose original supplier has exited the programme.

So the terms that matter are continuity terms. Source escrow with verification, a licence surviving termination sufficient to maintain and update deployed vehicles, and transferability to a successor supplier.

Open source is embedded everywhere. Vehicle software stacks contain substantial open source, and copyleft obligations attach to distribution — which includes shipping a vehicle. Bills of materials should be contractual deliverables, refreshed on each release, with a warranty of accuracy and an obligation to supply corresponding source where a licence requires it.

Tooling and specifications raise the same questions as any contract manufacturing relationship: title, marking, possession, and transfer obligations surviving termination.

Data rights need their own clause. Who may use data produced by the supplier's component, for what purposes, and — critically — whether the supplier may use it to improve its own products sold to the manufacturer's competitors. This is the single most commonly omitted term in tier one agreements, and it is the one that matters most as vehicles become data platforms.

And the improvements question recurs at the model layer. A supplier whose algorithm improves through exposure to a manufacturer's fleet data has built something valuable from an input the manufacturer supplied, and neither party's standard form addresses it.

Software Features, Subscriptions, and Updates

Selling a vehicle containing hardware the buyer cannot use without paying again is a commercial choice with legal consequences, and the consequences are mostly consumer and contract rather than intellectual property.

Disclose at the point of sale. What is included, what is subscription, what happens if the subscription lapses, and what happens if the service is discontinued. Undisclosed feature gating is a deceptive practices exposure under 15 U.S.C. § 45 and its state analogues, whatever the licence says.

Distinguish the software licence from the vehicle sale. The vehicle is sold; the software is licensed; and Impression Products, Inc. v. Lexmark International, Inc., 581 U.S. 360 (2017), holds that an authorised sale exhausts patent rights in the article regardless of post-sale restrictions — so restrictions on use must run in contract, not in patent.

Copyright first sale under 17 U.S.C. § 109 applies to copies owned rather than licensed, and the licence-versus-sale characterisation of embedded software is the fight that determines whether a purchaser may transfer it.

Over the air updates raise three questions. Consent to modification of a product already sold; liability for a defect introduced by an update; and the removal of functionality, which is where the strongest consumer objections arise and where several regulators have taken interest.

Feature transferability on resale matters commercially and legally. A subscription tied to the owner rather than the vehicle reduces the vehicle's resale value, which is a disclosure question and, in some jurisdictions, a warranty and consumer protection question.

Discontinuation is the hard case. A connected service the manufacturer stops operating degrades a product the customer bought, and the terms should say what happens — a refund, a local-only fallback mode, or a defined notice period — because saying nothing is what generates the class action.

And the update mechanism itself needs security and integrity controls, because an unauthenticated update path is a safety issue before it is an intellectual property one.

The Aftermarket and Repair

Vehicles are the archetypal aftermarket problem, and the analysis follows the general repair framework with sector-specific overlays.

Repair is permitted. Aro Manufacturing Co. v. Convertible Top Replacement Co., 365 U.S. 336 (1961), permits replacement of unpatented components of a patented combination, and only reconstruction of the whole infringes.

Design patents are the manufacturer's strongest tool. Body panels, lamps, wheels, and mirrors are routinely covered by design registrations under 35 U.S.C. § 171, with infringement assessed under Egyptian Goddess, Inc. v. Swisa, Inc., 543 F.3d 665 (Fed. Cir. 2008), obviousness reframed by LKQ Corp. v. GM Global Technology Operations LLC, 102 F.4th 1280 (Fed. Cir. 2024) (en banc), and the total profits remedy of 35 U.S.C. § 289 available.

The United States has no must-match exception, unlike several other jurisdictions, which is why component design patents are commercially significant here and less so elsewhere.

Software authentication is the operative control. Parts pairing — a replacement component that will not function until authorised by the manufacturer's system — is more effective than any patent, and it engages 17 U.S.C. § 1201 when a repairer works around it.

Triennial exemptions matter. The rulemaking under section 1201 has produced exemptions covering diagnosis, repair, and modification of motorised land vehicles, and their scope and renewal cycle should be tracked, along with the trafficking gap: an exemption permits the act of circumvention and does not authorise supplying the tool that performs it.

Repair legislation is moving. State statutes requiring access to parts, tools, and documentation on fair and reasonable terms, and sector-specific agreements in the automotive space, are changing the practical position faster than the case law.

Insurance and salvage rules constrain the use of non-original parts in repairs in some states, which cuts the other way and is frequently overlooked by aftermarket suppliers.

And the marketing rules are their own layer. Aftermarket parts sold as compatible must use the manufacturer's marks nominatively and truthfully, and reconditioned goods must be disclosed as such — the principle running from Champion Spark Plug Co. v. Sanders, 331 U.S. 125 (1947), and Prestonettes, Inc. v. Coty, 264 U.S. 359 (1924).

Standard Essential Patents in Automotive

Vehicles became connected devices, and the cellular patent holders noticed.

The structural question is licensing level. Patent holders prefer to license the vehicle manufacturer, because the royalty base is the vehicle. Manufacturers prefer that their suppliers take the licence, because the base is the module. This is the access-to-all-versus-licence-to-all dispute, and it has been litigated on two continents without settled resolution.

FRAND commitments are contractual. A declaration to a standards body is a promise, and Microsoft Corp. v. Motorola, Inc., 696 F.3d 872 (9th Cir. 2012), treats it as one — enforceable by implementers as third-party beneficiaries and capable of supporting anti-suit relief.

Injunctions are constrained but not unavailable. eBay Inc. v. MercExchange, L.L.C., 547 U.S. 388 (2006), makes injunctive relief discretionary, and a patentee that has committed to license on FRAND terms has difficulty showing irreparable harm — though a genuinely unwilling licensee changes the analysis.

Rate setting has gone global. The English courts have accepted the role of setting worldwide terms, and courts elsewhere have responded with anti-suit and anti-anti-suit injunctions, which means the forum question in an automotive standards dispute is at least as important as the merits.

Patent pools are the practical answer for most manufacturers, and the diligence on a pool is unglamorous: essentiality of the declared patents, the rate stack across all pools and bilaterals, the indemnity position with suppliers, and the treatment of non-participating holders.

Supplier indemnities are where the exposure actually lands. A manufacturer sued on a cellular patent will look to its module supplier, whose indemnity is typically capped at a fraction of the exposure and frequently excludes standards claims entirely. Read those caps before the programme launches, not after the demand arrives.

Brand, Trade Dress, and the Vehicle Itself

Vehicle appearance is protected on several layers and enforced inconsistently.

Design patents on body panels, grilles, lamps, and interior components, filed before public disclosure to preserve foreign rights under 35 U.S.C. § 102.

Trade dress in the overall look where it has acquired distinctiveness and is non-functional, subject to the bar of TrafFix Devices, Inc. v. Marketing Displays, Inc., 532 U.S. 23 (2001). Grille designs and silhouette have been registered; most functional bodywork has not.

Trademarks in model names, badge designs, and — increasingly — sound marks for electric vehicles, which have no engine note and are legally required to make some noise.

Merchandise and scale models raise licensing questions, and manufacturers licence heavily into toys, games, and simulations.

Depictions in games and film are the recurring dispute, with manufacturers asserting trade dress and publishers asserting expressive use — a balance courts have generally struck in favour of the expressive work where the use is not explicitly misleading.

And the digital twin is the new front. Vehicle models used in simulation, virtual environments, and training data raise licensing questions that no existing agreement addresses, and the manufacturers with a position on this are the ones that thought about it before the request arrived.

Fleets, Mobility Services, and Insurance

Commercial fleet and mobility arrangements distribute the data question differently.

The fleet operator wants the data for utilisation, maintenance, and driver management, and its contract with the manufacturer should say so rather than relying on the connected services terms written for consumers.

Drivers are data subjects even at work. Location, behaviour, and cabin monitoring of employees engage privacy and employment law, and consent obtained through an employment relationship is treated sceptically in several regimes.

Insurance telematics turns driving data into pricing, which brings insurance regulation, discrimination analysis, and consent requirements alongside the data rights question.

Ride-hailing and car sharing platforms sit between the manufacturer and the driver, with their own terms, their own data collection, and their own claims to derived outputs.

Charging networks generate their own dataset, tied to location and payment, and the interoperability standards are still consolidating.

And the maintenance data flow is contested between manufacturer, dealer, fleet, and independent servicer, which is the aftermarket access question in a commercial rather than a consumer setting — and it is frequently governed by a dealer agreement nobody outside the franchise team has read.

Building the Programme

Map the data. What each system collects, where it goes, who touches it, and under what agreement. This map does not exist in most manufacturers and takes about six weeks to build.

Rewrite the supplier template. Background and foreground allocation; improvements in three buckets; data rights including a prohibition on competitive use; open source bill of materials as a deliverable; escrow with verification; and a survival licence sufficient to maintain and update deployed vehicles.

Audit the open source position across the software stack, and treat the bill of materials as a release gate rather than as an annual project.

Align the consumer terms. Purchase documentation, connected services terms, privacy notice, and subscription terms should describe one arrangement, and in most manufacturers they describe three.

Decide the aftermarket posture deliberately. Parts pairing, diagnostic access, and independent repair are commercial and political decisions with legal consequences, and they should be taken by someone senior rather than emerging from an engineering default.

Track the section 1201 exemption cycle and the state repair legislation calendar.

Model the standards exposure — declared patents, pools, rate stack, supplier indemnity caps — before the connected feature launches.

Protect the derived data layer with segregation, marking, and access control, so the trade secret claim is available if it is ever needed.

And review annually, with triggers on a new supplier, a new connected feature, a new market, a change in repair legislation, and any standards demand.

A Worked Example

A manufacturer launches a driver assistance feature whose supplier provides the sensor and the perception software, and whose performance improves as the fleet accumulates miles.

The data question comes first. Whose data are the sensor outputs? The supplier's agreement is silent, so the supplier is using fleet data to improve a product it also sells to two competitors — which the manufacturer discovers when the competitors ship the same improvement.

The remedy is prospective. The clause needed was a prohibition on competitive use of data generated by the manufacturer's fleet, plus an allocation of improvements derived from it, and it will only go into the next platform agreement.

The privacy question comes second. The sensor captures cabin video for attention monitoring, which is biometric data under several state regimes, requiring notice, consent, and retention limits — and the consent flow was designed by the supplier for a different jurisdiction.

The standards question comes third. The feature requires connectivity, the connectivity module is licensed at module level, and a declared patent holder demands a vehicle-level licence. The supplier's indemnity is capped at the module purchase price.

The aftermarket question comes fourth. The sensor is paired to the vehicle, an independent repairer cannot replace it, and the state where the manufacturer's largest market sits has repair legislation in committee.

Four questions, four different disciplines, one feature — and the only one the intellectual property function was asked about was the fourth.

Autonomy, Simulation, and Training Data

Autonomous systems concentrate every problem in this toolkit into one programme.

The training data is the asset. Miles driven, edge cases encountered, and labelled scenarios represent the bulk of the investment, and their protection is contractual and secret rather than proprietary — there is no property right in the data, and Feist Publications, Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991), forecloses a database claim in the facts.

Labelling is outsourced, frequently offshore, and the vendor agreements rarely address ownership of the labels, use of the underlying data for the vendor's own purposes, or the confidentiality obligations of the individual annotators.

Simulation environments raise licensing questions nobody drafted for: vehicle models, road network data, building geometry, and the appearance of third-party vehicles and brands within a simulated scene.

Sensor data from public roads captures people, which engages biometric and privacy regimes in several states regardless of whether the manufacturer intends to identify anyone.

Model weights are the second asset, protectable as trade secrets if measures are taken, and increasingly the subject of supplier improvement clauses that allocate the wrong thing.

Safety documentation is the third, and in a sector heading toward regulatory approval regimes it will become the barrier to entry — the same pattern seen in medical devices and aerospace.

And the patent layer is crowded and contested, with perception, planning, and control claims held across manufacturers, suppliers, and non-practising entities, which makes freedom to operate a standing programme rather than a project.

Antitrust and Distribution

Aftermarket control invites antitrust scrutiny, and the automotive sector has more of it than most.

Aftermarket monopolisation. Eastman Kodak Co. v. Image Technical Services, Inc., 504 U.S. 451 (1992), permits a monopolisation claim in a derivative aftermarket even without primary market power, where information and switching costs lock customers in — which describes vehicles reasonably well.

Refusal to deal is generally lawful, subject to the narrow exception the Supreme Court has left, and a manufacturer that has never supplied diagnostic access to independents is in a better position than one that supplied it and withdrew.

Warranty conditioning is regulated. 15 U.S.C. § 2302 prohibits conditioning warranty coverage on the use of branded parts or authorised service absent a waiver, and marketing that implies otherwise is an enforcement target.

Franchise and dealer statutes constrain manufacturer conduct toward dealers in most states, including on parts sourcing, warranty reimbursement, and — increasingly — data access.

Selective distribution of parts is generally lawful and should be documented for legitimate quality and safety reasons rather than as a pricing measure.

And the direct sales question intersects with all of it, as manufacturers selling directly and updating vehicles over the air bypass a dealer network whose legal protections were written for a different business model.

Cross-Border Considerations

Vehicle programmes are global and the rules are not.

Design protection differs sharply. Several jurisdictions have a repair or must-match exception excluding visible replacement parts from design protection, and the United States does not — which means the same body panel is protected here and unprotected elsewhere, and the filing programme should reflect that rather than mirroring a domestic strategy abroad.

Data protection differs more. Comprehensive regimes with lawful basis requirements, transfer restrictions, and automated decision-making rules apply to vehicles sold into those markets, and a connected services architecture designed for one market rarely satisfies another without changes at the system level.

Standards litigation is forum-driven. Injunctions issue more readily in some jurisdictions than others, rate-setting has been claimed by more than one court, and the anti-suit escalation described in the standards section is most active precisely in automotive.

Export control reaches the software and the sensor data, particularly for advanced driver assistance and autonomy, and technical data transfers to foreign engineering centres are controlled events regardless of intra-group status.

Homologation and type approval regimes create their own documentation packages, and those packages are frequently the most sensitive technical disclosure a manufacturer makes.

And the aftermarket rules diverge. Block exemption style regimes in some markets require manufacturers to make technical information available to independent repairers as a condition of distribution, which is a legal obligation rather than a commercial choice.

Scale and Cadence

A component supplier needs background and foreground allocation in its customer agreements, an open source bill of materials discipline, and a clear position on whether its improvements derived from customer data may be used elsewhere.

A vehicle manufacturer needs the data map, the rewritten supplier template, the aligned consumer terms, the aftermarket posture, the standards exposure model, and the open source release gate.

A mobility or fleet operator needs data rights in its vehicle purchase and service agreements, driver privacy compliance, and a clear position on maintenance data access.

An aftermarket supplier needs design clearance on every part, a parts pairing and circumvention analysis, a nominative use listing template, and a working knowledge of the exemption cycle and the state legislation calendar.

Review annually, and on six triggers: a new supplier, a new connected feature, a new market, a change in repair legislation, a standards demand, and the first request from a fleet customer for raw data.

What Clients Actually Ask

"Do we own the vehicle data?" Nobody owns data as such. You hold it, and your rights come from contracts and are limited by privacy law. The useful conversation is about which rights you need and from whom.

"Can our supplier use our fleet data to help our competitors?" Unless the agreement says otherwise, frequently yes. This is the most consequential omission in tier one agreements and it is invisible until the competitor ships the improvement.

"Can we charge a subscription for hardware already in the car?" Commercially yes, and the exposure is disclosure and consumer protection rather than intellectual property. Say what is included and what is not at the point of sale.

"Can we stop independent repairers?" Less than you could five years ago, and less each year. Parts pairing works technically; the exemption cycle and state legislation are moving against it; and Kodak supplies an antitrust theory where lock-in is real.

"Can we be sued on cellular patents if our supplier is licensed?" Frequently yes, and the licensing-level dispute is unresolved. Model the exposure and read the supplier indemnity cap before launch.

"What is our biggest exposure?" Usually a platform agreement signed years ago that allocates parts and says nothing about data, governing a feature nobody had thought of when it was drafted.

A Ninety-Day Programme

Days one to twenty. Build the data map: every system that collects, every destination, every agreement that touches it, and every privacy characterisation. This does not exist in most manufacturers and it is the foundation for everything else.

Days twenty to thirty-five. Audit the top ten supplier agreements against the six terms that matter: background and foreground, improvements buckets, data rights and competitive use, open source bill of materials, escrow with verification, and a survival licence sufficient to maintain deployed vehicles.

Days thirty-five to fifty. Reconcile the consumer-facing documents — purchase, connected services, privacy notice, subscription terms — into one coherent description of the arrangement, and identify every feature gated after sale without disclosure.

Days fifty to sixty-five. Model the standards exposure: declared patents touching the connectivity stack, pool participation, the rate stack, and every supplier indemnity cap.

Days sixty-five to eighty. Take the aftermarket posture decision explicitly, at a level senior enough to own it, with the section 1201 exemption cycle and the state legislation calendar in front of the decision-maker.

Days eighty to ninety. Stand up the open source release gate and the derived-data protection measures, and write the annual review calendar with its six triggers.

The output is four documents and one decision, and a manufacturer that has them is in a materially different position from one whose position is distributed across a purchasing department, an engineering team, and a privacy officer who have never met.

A Closing Note

The automotive sector has been through this transition before, and did not recognise it.

When electronics entered the vehicle, the intellectual property function continued to think in terms of mechanical patents and body design while the value migrated into control units nobody had drafted a supply agreement for. The result was a generation of platform agreements that allocated castings precisely and software carelessly.

The same thing is happening again with data, and the pattern is identical: agreements that specify tolerances to the micron and say nothing about whether a supplier may use fleet data to improve products it sells to competitors.

The correction is not complicated. Six terms in the supplier template, one data map, one coherent set of consumer documents, and one explicit decision about the aftermarket. None of it requires new doctrine, and all of it requires someone to ask the question during the programme rather than after the feature ships.

And the aftermarket posture deserves the most attention, because it is the decision most likely to be reversed by legislation. A manufacturer building a business model on parts pairing is building on ground that is moving, and the honest advice is to say so — not to draft around it more cleverly.

Electrification, Charging, and Batteries

Electrification adds a technology stack with its own intellectual property profile.

Battery chemistry and cell design are the classic chemical patent and trade secret problem: composition claims, process conditions that leave no signature, and manufacturing know-how held by a small number of suppliers, most of them offshore.

Pack and thermal management are more mechanical and more patentable, and they are where manufacturers with no cell capability can still build a portfolio.

Battery management software is licensed from suppliers with the same continuity problems as any embedded software, and a pack whose management software cannot be updated after the supplier exits is a warranty problem with a ten-year tail.

Charging interfaces are standards. Connector geometry, communication protocols, and payment interoperability all involve standards bodies, declared patents, and the same FRAND questions that arrived with connectivity — with the added feature that charging infrastructure is partly publicly funded and subject to procurement conditions.

Battery passports and traceability requirements in several markets create documentation obligations that reach into the supply chain and disclose composition and provenance data the supplier regards as confidential.

Second life and recycling raise exhaustion and repair questions in a new setting: a pack removed from a vehicle and repurposed for storage is an authorised article being adapted, and the analysis follows Aro and Impression Products rather than anything battery-specific.

And the state of charge and usage data generated by the pack is among the most commercially valuable telemetry in the vehicle, which returns the analysis to the data section of this toolkit.

Two Practical Notes on Process

Get the intellectual property function into the programme gate reviews. Vehicle programmes run on staged gates with defined deliverables, and in most manufacturers the legal deliverable is a freedom to operate memorandum at one gate and nothing else. Adding four questions — data rights, open source, standards exposure, and aftermarket posture — to the existing gate structure is a process change rather than a resourcing one, and it catches nearly everything this toolkit describes.

And write the platform agreement once. Supplier negotiations happen dozens of times per programme, conducted by purchasing teams working from a template. Improving the template is worth more than improving any individual negotiation, and it is the single highest-leverage piece of work available to counsel in this sector.

Both changes are cheap, both are durable, and both survive a change of counsel — which is more than can be said for advice delivered feature by feature into a programme that runs for a decade and outlasts everyone who worked on its first year.

A third note is worth adding for smaller participants. Suppliers, aftermarket manufacturers, and mobility operators face the same questions from the other side of the table, and their leverage is lowest at the point when the template arrives and highest when the manufacturer needs something specific from them. The terms to press for are symmetrical: a right to use data generated by their own components for their own product improvement, a carve-out for background technology, and a cap on indemnity that reflects the component price rather than the vehicle price. Those three asks are reasonable, they are frequently conceded when raised early, and they are almost never raised at all.

Raising them costs an email during a negotiation that is already happening, which makes this the cheapest advice in the entire toolkit.

It is also the advice most likely to be taken, because it asks the client to say something rather than to build something.

A Suggested Reading Path

Start with the doctrine in The Car That Reports Back.

Then the practice in Advising an Automotive or Mobility Business.

Then the audit in the connected vehicle IP and data checklist.

For the aftermarket layer, The Part That Broke and the Aftermarket, Repair, and Spare Parts IP Toolkit.

For circumvention and repair legislation, The DMCA's Other Half and the Anticircumvention and Repair Toolkit.

For standards, The Promise You Made to the Standards Body and the Standard-Essential Patents and FRAND Toolkit.

For the data layer, the Data Licensing and Rights Toolkit and the State Privacy Compliance Toolkit.

For biometric exposure, the Biometric and Sensitive Data Toolkit.

For the software stack, the Software, Data, and Open Source Toolkit and the Software Continuity and Escrow Toolkit.

And for the supplier relationship, Contracting With a Manufacturer and the Contract Manufacturing, OEM, and Private Label IP Toolkit.

Primary Authorities

| Authority | Proposition | |---|---| | 35 U.S.C. § 171 | Design patents on components | | 35 U.S.C. § 102 | Novelty; disclosure before filing | | 35 U.S.C. § 271 | Infringement; contributory and induced | | 35 U.S.C. § 289 | Total profits for design infringement | | 17 U.S.C. § 109 | First sale; owned versus licensed copies | | 17 U.S.C. § 117 | Maintenance and repair copies | | 17 U.S.C. § 1201 | Circumvention; triennial exemptions | | 17 U.S.C. § 1203 | Civil remedies for circumvention | | 15 U.S.C. § 45 | Unfair or deceptive practices | | 15 U.S.C. § 1125 | False designation; trade dress | | 15 U.S.C. § 2302 | Warranty anti-tying | | 18 U.S.C. § 1839 | Trade secret; reasonable measures | | Feist Publications v. Rural Telephone Service | No property in facts | | Aro Manufacturing v. Convertible Top Replacement | Permissible repair | | Impression Products v. Lexmark International | Exhaustion on authorised sale | | Egyptian Goddess v. Swisa | Ordinary observer test | | LKQ Corp. v. GM Global Technology Operations | Design patent obviousness | | TrafFix Devices v. Marketing Displays | Functionality bar | | Champion Spark Plug v. Sanders | Reconditioned goods; disclosure | | Prestonettes v. Coty | Truthful use of another's mark | | Microsoft v. Motorola | FRAND as an enforceable commitment | | eBay v. MercExchange | Discretionary injunctive relief | | Eastman Kodak v. Image Technical Services | Aftermarket monopolisation | | Chamberlain Group v. Skylink Technologies | Circumvention nexus to infringement | | Section 1201 vehicle repair exemptions | Scope and renewal cycle | | State right to repair legislation | Access obligations | | Event data recorder access statutes | Owner consent and disclosure limits |

Forms and Templates

The License Agreement Template supplies the structure for a tier one supply and development agreement, and the provisions that carry the relationship in this sector are the background and foreground allocation, the three-bucket improvements clause, the data rights clause including a prohibition on competitive use of fleet-derived data, the open source bill of materials deliverable, and the escrow and survival licence sufficient to maintain deployed vehicles. The Assignment Agreement Template covers engineer and contractor assignments across the software and design functions. The Portfolio Inventory Template adapts into a combined register of design filings, declared standards patents, open source obligations, and data rights by system — which is the document a connected vehicle programme actually needs. Beyond those, maintain four records: a data map by system and agreement; an open source bill of materials per release; a standards exposure model with supplier indemnity caps; and an aftermarket posture note recording the parts pairing and diagnostic access decisions and who took them.

Related Toolkits and Checklists

The Aftermarket, Repair, and Spare Parts IP Toolkit carries the repair doctrine analysis in full. The Anticircumvention and Repair Toolkit covers parts pairing and the exemption cycle. The Standard-Essential Patents and FRAND Toolkit covers the licensing-level dispute. The Data Licensing and Rights Toolkit covers the derived data layer, and the Software, Data, and Open Source Toolkit covers the bill of materials discipline that vehicle software requires.