Semiconductor and Hardware IP Toolkit: Mask Works, Chip Patents, Foundries, and IP Cores

By Casey Scott McKay · 2024-08-03

Semiconductor intellectual property runs on four regimes at once, and practitioners trained in any one of them routinely misjudge the others. This toolkit collects them. It covers the mask work right created by the Semiconductor Chip Protection Act - a sui generis regime with its own registration deadline, its own two-year forfeiture rule, and a reverse engineering privilege with no analogue elsewhere - alongside the patent, copyright, and trade secret layers that actually carry most of the value. It works IP core licensing, foundry and process design kit arrangements, the export control regime that operates independently of any of it, exhaustion after Quanta, and section 337 exclusion orders. It closes with supply chain integrity, counterfeit components, and portfolio strategy.

IP and Technology > Patent Counseling Transactions | Toolkit | Published 3 August 2024 - Updated 26 September 2024 | Casey Scott McKay - marksy.us

Summary. Semiconductor intellectual property runs on four regimes at once, and practitioners trained in any one of them routinely misjudge the others. This toolkit collects them. It covers the mask work right created by the Semiconductor Chip Protection Act — a sui generis regime with its own registration deadline, its own two-year forfeiture rule, and a reverse engineering privilege with no analogue elsewhere — alongside the patent, copyright, and trade secret layers that actually carry most of the value. It works IP core licensing, foundry and process design kit arrangements, the export control regime that operates independently of any of it, exhaustion after Quanta, and section 337 exclusion orders. It closes with supply chain integrity, counterfeit components, and portfolio strategy.

Keywords: semiconductor IP toolkit · mask work protection · Semiconductor Chip Protection Act · Brooktree · reverse engineering privilege · mask work registration · chip patents · HDL and RTL copyright · IP core licensing · foundry agreements · process design kits · trade secrets in fabrication · export control · section 337 exclusion orders · exhaustion after Quanta · standard essential patents · hardware trade dress · supply chain security · counterfeit components · portfolio strategy

Start Here

A chip design company asks what protects its product.

The honest answer involves four regimes operating simultaneously, and the one created specifically for the industry is the least valuable of the four.

Mask works are protected by a sui generis right at 17 U.S.C. § 901 and following, enacted because neither copyright nor patent fitted the problem: layouts were dictated by function so copyright's originality requirement sat awkwardly, and they were rarely inventive enough for a patent. The result is a regime with a ten-year term, a two-year registration deadline that forfeits the right entirely, and — remarkably — an express privilege permitting competitors to reverse engineer and to create their own original layouts from what they learn.

Patents carry the circuit architecture, the process technology, the packaging, and the system-level innovation. This is where the value is, and where the assertion happens.

Copyright protects the hardware description language, the register transfer level code, the firmware, the drivers, and the documentation — as literary works, subject to the same functional limits that constrain software copyright generally.

Trade secret protects the process recipes, the yield data, the design methodology, and the tuning knowledge that no patent discloses and no layout reveals.

And running alongside all four, wholly independently, is an export control regime that can prohibit a transfer no intellectual property analysis would question — including disclosure to a foreign national inside the licensor's own building.

This toolkit answers four questions. What does the mask work right actually give, and why is it narrower than clients expect? How are the patent, copyright, and secret layers assembled into a portfolio? What do the industry's characteristic agreements — IP core licences, foundry agreements, and process design kit arrangements — need to contain? And what non-intellectual-property regimes constrain the transaction regardless?

A framing note. The industry's structure — fabless designers, foundries, packaging houses, and core licensors — means almost every product involves rights held by four or five parties, and the intellectual property question is usually an allocation question rather than a protection question.

The Mask Work Right

What it protects. 17 U.S.C. § 902 protects a mask work fixed in a semiconductor chip product — the series of related images representing the three-dimensional pattern of metallic, insulating, or semiconductor material on the chip.

What it does not protect. A mask work that is not original, or that consists of designs that are staple, commonplace, or familiar in the industry, or variations of those combined in a way that considered as a whole is not original.

Term. Ten years from registration or first commercial exploitation, whichever comes first, under 17 U.S.C. § 904.

Registration and the forfeiture rule. 17 U.S.C. § 908 requires registration within two years of first commercial exploitation. Miss it and the right is lost entirely. This is unlike copyright, where late registration costs remedies rather than the right itself, and it is the single most common failure in mask work practice.

The reverse engineering privilege. 17 U.S.C. § 906 expressly permits reproduction of a mask work for the purpose of teaching, analysing, or evaluating the concepts or techniques embodied in it — and permits a person who does so to incorporate the results in an original mask work of their own.

Which is extraordinary, and has no analogue in patent or copyright. A competitor may lawfully take the chip apart, study the layout, and design its own using what it learned, provided the result is original and represents genuine independent effort. The paper trail of that effort is the defence, which is why serious reverse engineering programmes document every step.

Brooktree v. Advanced Micro Devices is the leading decision, confirming that substantial similarity in the protectable portions supports infringement while recognising the breadth of the reverse engineering privilege and the significance of the paper trail.

Innocent infringement. 17 U.S.C. § 907 limits the liability of a purchaser who did not know and had no reasonable grounds to believe a chip was infringing, requiring a reasonable royalty only for units in inventory or ordered after notice.

Notice. 17 U.S.C. § 909 provides for a mask work notice, which is not required but which defeats the innocent infringement defence.

Remedies. 17 U.S.C. § 911 provides actual damages plus profits, or statutory damages, with a three-year limitations period under 17 U.S.C. § 912.

The practical assessment. The right is real, narrow, and cheap to obtain. Register within the deadline as a matter of routine, expect it to be a supporting claim rather than a primary one, and do not build a strategy around it.

The Patent Layer

Where the value is. Circuit architecture, process technology, packaging, memory structures, interconnect, power management, and system-level integration.

Eligibility. Hardware inventions generally survive 35 U.S.C. § 101 comfortably. The exposure arises where claims are drafted at the level of a computational method — a signal processing algorithm claimed without meaningful hardware limitation invites the Alice v. CLS Bank International framework and frequently loses.

Drafting consequence. Claim the structure. Where the invention is genuinely algorithmic, tie it to specific hardware implementation rather than reciting a processor.

Enablement and written description. 35 U.S.C. § 112 constrains broad claims, and Amgen v. Sanofi tightened the analysis for functional genus claiming. A claim to a class of circuits achieving a result, supported by two embodiments, is exposed.

Obviousness. 35 U.S.C. § 103, in an art where the prior art is enormous and where combinations are the norm. Secondary considerations — commercial success, long-felt need, unexpected results in yield or power — carry real weight here.

Timing. 35 U.S.C. § 102 supplies a one-year domestic grace period for the inventor's own disclosure and most foreign systems supply none. Conference papers, tape-out announcements, and customer sampling are all disclosures, and the filing calendar should precede them.

Extraterritorial reach. 35 U.S.C. § 271 at subsections (f) and (g) reach the supply of components from the United States for assembly abroad, and the importation of products made by a patented process — both directly relevant to an industry where design, fabrication, packaging, and assembly occur in different countries.

Marking. 35 U.S.C. § 287 conditions damages on marking or actual notice, and marking a chip is impractical — which makes virtual marking on a website the standard practice and its maintenance a real obligation.

Portfolio strategy. Fabless designers, integrated device manufacturers, foundries, and equipment vendors have structurally different portfolios and different reasons for filing. Defensive cross-licensing is the industry norm, which means portfolio size functions as negotiating currency independent of the merits of individual patents.

Injunctions. eBay v. MercExchange makes injunctive relief unlikely where the patentee does not practise the invention, which shifts the leverage in most semiconductor assertions to damages and to the border remedy described below.

Copyright, Code, and Design Files

What copyright reaches. Hardware description language and register transfer level code as literary works. Firmware. Device drivers. Development tools. Documentation, application notes, and reference designs.

The functional limits. 17 U.S.C. § 102 excludes ideas, procedures, and methods of operation, and Google v. Oracle America treats declaring code and interface specifications as further from the core of copyright than implementing code. A register map, a pin definition, and an instruction set encoding are interfaces, and protection over them is thin.

Which is the industry's structural reality: compatible implementations of a published interface are generally lawful, and Sega Enterprises v. Accolade supports intermediate copying to achieve interoperability.

Open source in firmware and tooling. Composition analysis over shipped firmware and over any distributed toolchain. Copyleft obligations attach on distribution, and a driver or bootloader shipping with a device is distribution. The bill of materials is what a customer's diligence asks for. See Copyleft and Consequences.

Design files. Netlists, GDSII files, testbenches, verification suites, and characterisation data are protected as copyright works, as trade secrets, or both — and the practical protection is access control rather than registration.

Registration strategy. Register firmware and substantial tools with trade secret portions redacted under the deposit rules, so that 17 U.S.C. § 411 and 17 U.S.C. § 412 remedies remain available without publishing the code.

Trade Secrets

What they carry in this industry. Process recipes and step parameters. Yield data and failure analysis. Design methodology and internal tooling. Characterisation and binning data. Supplier terms and equipment configurations. Test programmes.

Why they carry so much. A process node is not adequately described by any patent, and the tuning knowledge that produces yield is exactly the sort of thing patents do not disclose and layouts do not reveal.

Reasonable measures under 18 U.S.C. § 1836. Access controls at the fab and in the design environment. Compartmentalisation so no single vendor or contractor sees the whole process. Confidentiality agreements with employees, contractors, equipment vendors, and foundry partners. Marking. Exit procedures with written acknowledgement of access. Clean-room protocols for personnel arriving from competitors.

The mobility problem. Semiconductor engineers move between competitors constantly, and the protection depends on measures rather than on restrictive covenants, which are increasingly hard to enforce. See Where an Employee Can Go.

Onboarding from a competitor. Document that the incoming engineer was instructed not to bring or use the former employer's information, and that no such material entered the environment. This record is the defence to the inevitable claim.

The interaction with reverse engineering. 17 U.S.C. § 906 permits mask work reverse engineering and lawful reverse engineering generally defeats trade secret claims in the resulting information — so a secret embodied in a shipped chip is a secret with a limited life.

IP Cores

What they are. Pre-designed functional blocks — processor cores, interface controllers, memory controllers, analogue blocks — licensed for integration into a customer's design.

Delivery forms. Soft cores as synthesisable hardware description language; firm cores as gate-level netlists; hard cores as fully placed and routed layout. The form determines what the licensee can modify, what the licensor discloses, and what the trade secret position is.

Terms that decide these deals.

Field of use, frequently expressed by application, product category, or process node.
Royalty basis — per die, per wafer, per product, or a paid-up fee — with the measurement mechanism specified because it is where audits produce disputes.
Volume commitments and caps.
The right to sublicense to a foundry for manufacturing purposes, which is essential to a fabless model and which a licence drafted for a different structure omits.
Modification rights, and ownership of modifications and derivative cores.
Deliverables — source, netlist, or hard macro — and what happens on a process migration.
Support, updates, and errata, and whether a bug fix is included or chargeable.
Escrow, where the licensee's product life exceeds the licensor's likely survival.
Indemnity, which is the term that actually gets negotiated.

Why indemnity dominates. A core infringing a third-party patent contaminates every product built on it, and the licensee's exposure vastly exceeds the licence fee. Expect a cap and negotiate a supercap; assess the licensor's ability to stand behind it; and understand what is excluded — typically modification, combination, and continued use after notice.

Diligence on an inbound core. What third-party components does the core itself contain? What open source is embedded? What standards does it implement, and are the essential patents licensed? Has the licensor been asserted against on this core before? Does the licence survive a change of control on either side?

Diligence on outbound licensing. Whether the company can support the indemnity it is being asked to give, and whether its own inbound cores permit sublicensing to the customer's foundry.

Foundries and Process Design Kits

The structural point. A fabless designer must disclose its design to a foundry, and a foundry must disclose its process to the designer. Both disclosures are of the most sensitive material each party holds, and the agreements exist to make that survivable.

Process design kits. The foundry supplies device models, design rules, extraction decks, and libraries. These are the foundry's crown jewels, and the agreement should specify who may access them, on what systems, in what geographies, for how long, and what happens on termination — including whether designs already taped out may continue in production.

Node migration. A design ported to another foundry raises whether the first foundry's design rules and libraries influenced the migrated design, which is the recurring dispute. Address it expressly, and maintain records of independent development where a migration is contemplated.

Ownership of process improvements. Where a designer's requirements drive a process change, allocate ownership expressly rather than leaving it to a later argument.

Capacity and allocation. Not an intellectual property term, and frequently the term that matters most commercially.

Test and yield data. Who owns it, who may use it, and whether the designer's yield learning may be shared with a second source.

Packaging and assembly houses receive design and test information and need equivalent terms, plus overrun and scrap controls — because scrapped and out-of-spec parts entering the market as genuine components is a persistent supply chain problem.

Mask ownership. Who owns the physical masks, who may use them, and their disposition on termination.

Second sourcing. A designer that wants a second source needs the right to transfer the design, and a foundry that has invested in enabling it will resist. Negotiate at the outset rather than when the first source has a capacity problem.

What Operates Independently

Export control. The regime that constrains transactions no intellectual property analysis would question.

Deemed exports. Disclosing controlled technology to a foreign national inside the United States is treated as an export to that person's country. In an industry where design teams are internationally staffed, this reaches ordinary internal engineering discussions. See export administration regulations for semiconductors.

Entity and end-use restrictions. Prohibitions on supplying named entities and on supplying technology for specified end uses, which change with policy rather than with law and which require monitoring rather than a one-time analysis.

Licence conditions in agreements. Every core licence, foundry agreement, and joint development agreement should carry export compliance covenants and a right to suspend where compliance requires it.

Investment screening. Foreign investment in semiconductor businesses attracts national security review, which reaches licensing arrangements conferring control or access to sensitive technology as well as equity transactions.

Government funding conditions. Public funding programmes carry their own obligations on manufacturing location, reporting, and technology transfer, operating alongside any Bayh-Dole obligations where research funding is involved.

Supply chain security requirements for defence and critical infrastructure customers, including provenance, authenticity, and prohibitions on components from specified sources.

Practical arrangement. Route every transfer of technical data through an export classification step, and treat the classification as a gate rather than a record. This is a compliance function rather than a legal one, and a company that runs it as legal review after the fact will fail it.

Exhaustion and the Chain

Why it matters here more than in most industries. A chip is a component, sold to a module maker, incorporated into a board, sold to a device maker, sold to a consumer — and the patent covering it may read on the chip, the board, or the finished device.

Quanta Computer v. LG Electronics holds that an authorised sale of a component that substantially embodies a patented invention exhausts the patent as to that item, and that a licence permitting the sale exhausts even where the licence purports to restrict downstream use.

Which is the structural answer to double-dipping. A patentee that licenses a chip supplier and then asserts against the supplier's customers on the same patents is generally exhausted, and the licence terms it drafted determine the answer.

Impression Products v. Lexmark International confirms that an authorised sale exhausts regardless of post-sale restrictions and that sales abroad exhaust US patent rights.

Drafting consequence for a licensor. A patentee wishing to license at the device level rather than the component level must be careful about what it authorises upstream — and a licence to a chip supplier that permits sale into the market exhausts.

Drafting consequence for a licensee. Establish expressly that the licence covers the licensee's customers and their customers, or at minimum that sales are authorised for exhaustion purposes.

Have-made rights. A licensee using a foundry needs the right to have products made by third parties, and a licence silent on it may not cover foundry manufacture at all.

Cross-licences. The industry norm, and their scope questions are exhaustion questions in disguise — whether products made for a third party under a foundry arrangement are covered, and whether a party's customers are.

The Border Remedy

Why it dominates semiconductor enforcement. 19 U.S.C. § 1337 supports an investigation at the trade agency leading to an exclusion order barring importation, on a statutory schedule far faster than district court and without the eBay v. MercExchange constraint on injunctive relief.

The elements. An unfair act — patent, trademark, copyright, mask work, or trade secret misappropriation — importation, and a domestic industry.

The domestic industry requirement is the gating question for a fabless company or a licensing entity, and it can be satisfied through substantial investment in exploitation including engineering and research, not only manufacturing.

Remedies. Limited exclusion orders against named respondents, general exclusion orders reaching all sources where circumvention is likely, and cease and desist orders against domestic inventory. No damages.

Why it matters to a defendant. An exclusion order stops the product at the border, which for a component supplier means every downstream customer is affected. The pressure to settle is structural rather than merits-driven.

Timing. Fast, expensive, and document-intensive, with a compressed discovery schedule that punishes unprepared respondents.

Practical consequence. A semiconductor company should understand its exposure before an investigation is instituted — which means knowing the standards it implements, the cores it licenses, and the patents that have been asserted in its category. See Section 337 at the ITC.

Counterfeits and Supply Chain

The problem. Remarked parts sold as higher-grade or newer devices. Recovered parts from scrapped boards. Scrapped and out-of-spec production entering the market. Cloned devices. Relabelled products from a different manufacturer.

Why it matters beyond revenue. A counterfeit component in a safety-critical or defence system is a liability and a reputational event, not merely an infringement.

Controls at the source. Overrun and scrap accounting at foundries and assembly houses, with certified destruction. Wafer and die traceability. Serialisation where volume permits.

Authentication. Physical unclonable functions, secure identifiers, and cryptographic attestation, which move the problem from enforcement to verification.

Distribution controls. Authorised distributor agreements with territory and resale terms, and the recordation and customs work that supports interception. Broker and grey market purchasing is where counterfeits enter most supply chains.

Enforcement. Trademark claims against remarked and relabelled parts, mask work claims where layouts are cloned, patent claims where the design is copied, and the border remedy where importation is involved.

Customer obligations. Defence and critical infrastructure customers impose provenance and authenticity requirements that flow down through the supply chain, and a supplier that cannot document its chain loses the qualification rather than the case.

Testing programmes. Incoming inspection, decapsulation, and electrical characterisation, which is how counterfeits are actually detected and which produces the evidence for any claim.

Standards and Interfaces

Almost every chip implements standards — memory interfaces, serial buses, wireless protocols, video codecs, and instruction set architectures — and each carries a licensing question.

Participation. Where the company participates in standard setting, follow the disclosure policy literally, record searches and disclosures, and brief participants that meetings are gatherings of competitors.

Declarations run with the patent. An acquirer of a portfolio inherits the FRAND commitments, and a company that acquired patents without checking has overpaid.

Pools. Common in this industry for codecs and connectivity standards. Taking a pool licence clears the pool's patents and nothing else, and essential patents outside the pool are the residual exposure.

Implementation without a licence. A frequent commercial reality, addressed through indemnity from a core supplier where one exists and through provisioning where it does not.

Interface compatibility. Implementing a published interface is generally lawful, and copyright over register maps and instruction encodings is thin following Google v. Oracle America. The risk sits in patents rather than in copyright.

Architecture licensing. Where an instruction set is licensed rather than published, the terms determine whether a compatible implementation is permitted at all, and the distinction between an implementation licence and an architecture licence is the commercial hinge.

Practical arrangement. Maintain a standards register: which standards each product implements, which pools have been joined, which essential patents are licensed, and which remain exposed. See The Promise You Made to the Standards Body.

Diligence Questions

On a semiconductor acquisition or investment, in order.

Mask work registrations — are they filed within the two-year deadline under 17 U.S.C. § 908, and are any designs already forfeited?
Patent title — assignments read, present-tense language confirmed, recordation checked, and contractor and joint development work covered.
Inbound core licences — field, volume, royalty basis, foundry sublicensing rights, change of control, and indemnity strength.
Open source in firmware and tooling — a current bill of materials and any copyleft components in shipped code.
Foundry and process design kit agreements — access restrictions, termination consequences, mask ownership, and whether designs in production may continue.
Standards commitments — declarations made, pools joined, essential patents licensed and unlicensed.
Export classification — whether technology has been classified, whether deemed export controls have been observed, and whether any transfer occurred without authorisation.
Trade secret measures — access controls, compartmentalisation, exit records, and clean-room documentation for engineers hired from competitors.
Assertion history — investigations at the trade agency, district court matters, and demand letters received in the category.
Supply chain — overrun and scrap controls, distributor agreements, and counterfeit incidents.

The recurring findings. Forfeited mask work rights nobody knew were forfeited. Core licences without foundry sublicensing rights. Copyleft in shipped firmware. And export transfers that occurred without classification.

Portfolio Strategy by Business Model

The fabless designer. Patents on architecture and circuit technique; mask works registered as routine; copyright and trade secret on the design database and verification suites; inbound core licences with foundry sublicensing; and a defensive portfolio sized for cross-licensing rather than for assertion.

The integrated device manufacturer. Adds process patents and a very substantial trade secret programme around fabrication, plus the equipment vendor relationships that carry their own confidentiality obligations.

The foundry. Process patents, process design kits as trade secrets, and the customer confidentiality obligations that are the business's foundation. Its intellectual property problem is mostly a compartmentalisation problem.

The core licensor. The portfolio is the product. Patents, copyright in the deliverables, trade secret in the methodology, and an indemnity position it can actually support — because the indemnity is what customers buy.

The equipment and materials vendor. Process and apparatus patents, and trade secret in the tuning knowledge that makes the equipment work in a customer's fab.

The system company designing its own silicon. Frequently the least prepared, because its intellectual property function was built for products rather than components, and because the mask work deadline and the export classification step are unfamiliar.

Where to spend first, at any model. Patent filing before disclosure, mask work registration on the calendar, the core and tool inventory, and export classification as a gate. Those four are cheap and their absence is not recoverable.

A Closing Note

The regime built specifically for this industry is the narrowest one it has.

Mask work protection is real, cheap, and easily lost — a two-year deadline under 17 U.S.C. § 908 that forfeits the right outright, and a reverse engineering privilege at 17 U.S.C. § 906 that lets a competitor study the layout and build its own. Register it as routine and expect it to be a supporting claim.

The value sits in the patents, the trade secrets, and the contracts — and in an industry structured around fabless designers, foundries, packaging houses, and core licensors, the contracts are doing allocation work as much as protection work.

Over all of it sits a regime that has nothing to do with intellectual property and that can prohibit a transfer no intellectual property analysis would question. Export classification belongs at the front of the process as a gate, not at the end as a review.

Do the four cheap things — file before disclosure, register the mask works on the calendar, maintain the core and tool inventory, and classify before transferring — and the rest of the practice is ordinary licensing work with unusually high stakes on the indemnity.

Common Errors

Missing the mask work registration deadline. 17 U.S.C. § 908 forfeits the right entirely after two years from first commercial exploitation, unlike copyright where late registration costs remedies. Companies discover the forfeiture during diligence.

Filing patents after tape-out announcements or customer sampling, both of which are public disclosures that destroy foreign novelty.

Claiming an algorithm without hardware limitation, which invites the Alice v. CLS Bank International framework in an art where structural claiming was available.

Taking a core licence without foundry sublicensing rights, then discovering the fabless model is not covered.

Accepting an indemnity cap at the licence fee, when a defective core contaminates every product built on it.

Shipping firmware with unreviewed copyleft components, discovered when a customer's diligence runs a scan.

Treating export classification as legal review after the fact rather than as a gate before transfer, particularly for deemed exports to internationally staffed design teams.

Asserting against a licensee's customers on patents already exhausted by an authorised component sale under Quanta Computer v. LG Electronics.

Acquiring a portfolio without checking standards declarations, which run with the patents and constrain what the acquirer can demand.

Hiring from a competitor with no clean-room documentation, which is the defence to the claim that always follows.

Assuming a chip can be marked for 35 U.S.C. § 287 purposes, when virtual marking is the practical route and requires maintenance.

No overrun or scrap controls at the assembly house, producing genuine parts in grey channels that get misdiagnosed as counterfeits.

Cadence

Per tape-out. Mask work first commercial exploitation date recorded; two-year registration deadline diaried; notice applied.

Per invention disclosure. Filing decision before any conference paper, announcement, or customer sampling.

Per core or tool acquired. Inventory entry with licence terms, field and volume limits, sublicensing rights, and indemnity strength.

Per build. Composition analysis over firmware and distributed tooling; bill of materials regenerated.

Per technical transfer. Export classification as a gate, including internal disclosures to foreign nationals.

Per new hire from a competitor. Clean-room instruction, documented, before access is granted.

Quarterly. Standards register updated; assertion landscape in the category reviewed.

Annually. Mask work registration audit; patent portfolio review against product roadmap; trade secret access review; distributor and supply chain audit; virtual marking page verified against the current portfolio.

On event. A foundry change, a node migration, a second-source decision, an acquisition, a trade agency investigation in the category, or a change in export policy affecting the customer base.

Running a Reverse Engineering Programme

The privilege exists and it is unusually broad, but it depends entirely on the record.

17 U.S.C. § 906 permits reproduction of a mask work for the purpose of teaching, analysing, or evaluating the concepts or techniques embodied in it, and permits incorporating the results in an original mask work of the recipient's own.

What "original" requires. Genuine independent design effort, not a redrawn copy. Brooktree v. Advanced Micro Devices treats the paper trail as the evidence of that effort, which makes documentation the whole of the defence.

What the record should contain. How the sample was lawfully acquired. Who performed the analysis and when. What was extracted and in what form. What concepts were identified. What design work followed, by whom, and over what period. What alternatives were considered and rejected. And the resulting layout, dated.

Separate the analysis team from the design team where the budget permits, which converts a similarity argument into an independent development argument.

Do not carry over layout files. Analysis outputs stay with the analysis team; the design team works from documented concepts.

Trade secret interaction. Lawful reverse engineering generally defeats trade secret claims in the information obtained, which is why a secret embodied in a shipped chip has a limited life — and why process knowledge that is not embodied in the product is the more durable secret.

Patent interaction. The privilege reaches mask works only. A design that reads on a valid claim infringes regardless of how it was developed, and independent development is no defence to patent infringement.

Contractual interaction. A licence or purchase agreement prohibiting reverse engineering may bind by contract even where the statute permits it, and the enforceability of that term is a separate question from the statutory privilege.

A note on who runs this. Almost none of the recurring failures are legal errors. The mask work deadline is a docketing task, the export classification is a compliance gate, the core inventory is maintained by whoever licenses cores, and the composition analysis runs in the build pipeline. Counsel's role is to set the gates and be available for the genuine questions — and a programme that routes every transfer through legal review will be bypassed within a quarter.

A Suggested Reading Path

For the patent layer:

For the software and interoperability layer:

For the standards and licensing dimension:

For the enforcement and border dimension:

Primary Authorities

| Authority | Proposition | |---|---| | 17 U.S.C. § 901 | Definitions; mask work and chip product | | 17 U.S.C. § 902 | Subject matter of protection | | 17 U.S.C. § 903 | Ownership and transfer | | 17 U.S.C. § 904 | Duration | | 17 U.S.C. § 905 | Exclusive rights | | 17 U.S.C. § 906 | Reverse engineering privilege | | 17 U.S.C. § 907 | Innocent infringement | | 17 U.S.C. § 908 | Registration; two-year deadline | | 17 U.S.C. § 909 | Mask work notice | | 17 U.S.C. § 911 | Civil remedies | | 17 U.S.C. § 912 | Limitations; relationship to other laws | | 17 U.S.C. § 102 | Literary works; idea exclusion | | 17 U.S.C. § 107 | Fair use | | 35 U.S.C. § 101 | Eligibility | | 35 U.S.C. § 102 | Novelty; grace period | | 35 U.S.C. § 103 | Obviousness | | 35 U.S.C. § 112 | Enablement; written description | | 35 U.S.C. § 271 | Infringement; components abroad | | 35 U.S.C. § 287 | Marking and notice | | 18 U.S.C. § 1836 | Trade secret civil action | | 19 U.S.C. § 1337 | Unfair practices in importation | | Brooktree v. Advanced Micro Devices | Mask work infringement and reverse engineering | | Alice v. CLS Bank International | Abstract idea framework | | Amgen v. Sanofi | Enablement of broad claims | | Google v. Oracle America | Fair use in functional code | | Sega Enterprises v. Accolade | Intermediate copying for interoperability | | Quanta Computer v. LG Electronics | Exhaustion on authorised sale of components | | Impression Products v. Lexmark International | Domestic and international exhaustion | | eBay v. MercExchange | Injunctive relief factors | | Export administration regulations for semiconductors | Deemed exports and controlled technology |

Forms and Templates

Semiconductor practice produces two registers that carry disproportionate weight. The first is the mask work registration diary: one row per taped-out design, with the first commercial exploitation date, the two-year registration deadline calculated from it, the registration number once obtained, and the notice status. 17 U.S.C. § 908 forfeits the right entirely on a missed deadline, unlike copyright where late registration costs remedies, and the Portfolio Inventory Template adapts to that diary directly. The second is the core and tool inventory: every licensed IP core, every third-party library, every process design kit, and every open source component in the firmware or tooling, with its licence terms, its field and volume limits, its royalty basis, and whether it may be redistributed to a foundry or a customer.

The License Agreement Template is the instrument for both directions of core licensing, and the terms that decide these deals are unusual: the field of use expressed by process node and application; the royalty basis expressed per die, per wafer, or per product; the right to sublicense to a foundry for manufacturing purposes; the treatment of derivative and modified cores; the source-versus-netlist deliverable question; and the indemnity, which in this industry is the term that actually gets negotiated because a core infringing a third-party patent contaminates every product built on it. The Assignment Agreement Template matters for the contractor and joint development work that produces much of the design, and it should carry present-tense assignment language, because layout and verification work is frequently outsourced and is not a work made for hire category.

Related Toolkits and Checklists

The Patent Licensing and Technology Transfer Toolkit covers the licensing framework that core and cross-licence arrangements sit within. The Software, Data, and Open Source Toolkit covers the code layer — firmware, drivers, and tooling — where copyleft obligations arise in shipped products. The Standard Essential Patents and FRAND Toolkit covers the interface and connectivity standards that most chip products implement. The IP and Antitrust Toolkit covers the pool and cross-licence governance this industry relies on heavily. And the IP Audit and Portfolio Governance Toolkit covers the register discipline that a portfolio spanning four regimes requires.