Document type: Toolkit Practice area: Intellectual Property — Patents Jurisdiction: United States, with international context Last reviewed: 5 September 2026

1. Standards exposure register

Build this before any demand arrives. Most companies cannot answer these questions and lose months learning to.

STANDARDS EXPOSURE REGISTER — [Company]
Owner: __________   Last updated: __________

| Product | Standard | Release | Implemented by | Optional
  features used | Units/yr | ASP | Component | Component
  price | Supplier | Supplier licensed? | Pool license? |

BY STANDARD
| Standard | Products affected | Annual units | Device
  revenue | Component cost | Known SEP holders | Pools |
  Current royalties paid |

MANDATORY VS OPTIONAL
For each standard, list the optional features we DO implement
and those we do NOT:
  Implemented: ______________________
  Not implemented: __________________
  [Patents mapping to features we do not implement cannot
  support essentiality-based infringement.]

ROYALTIES ALREADY PAID
| Counterparty | Standard | Rate | Base | Term | Scope |

GAPS
Products with no identified license coverage: ______________
Standards with no royalty budgeted: _______________________

Drafting notes.

The optional-features section is the most valuable page and the one nobody maintains. A patent mapping to an optional feature you do not implement is not infringed by your product, and knowing which features you use turns a portfolio demand into a much smaller conversation.

Maintain it quarterly. Products change, standards releases change, and suppliers change.

Keep the component price column. It is the apportionment base you will argue for.

2. Supplier licensing inquiry

Send this to every supplier of a component implementing a standard, before you need the answer.

[Date]
[Supplier]

Re: Standards-Essential Patent Licensing — [Component/Part No.]

Dear [__]:

[Company] purchases [component] from you for incorporation into
[products]. That component implements [standard(s) and
release(s)].

To assess our respective positions on standards-essential
patent licensing, we ask you to confirm the following in
writing:

1. Have you obtained licenses to standards-essential patents
   for [standard(s)]? If so, from which licensors?

2. For each such license, does it cover:
   (a) your manufacture and sale of the component;
   (b) our incorporation of the component into our products;
       and
   (c) our sale of those products worldwide?

3. Are you a licensee of any patent pool for [standard(s)]?
   If so, which, and at what tier?

4. Do you take the position that your sale of the component
   exhausts the licensors' patents as to our downstream sale?

5. Have you received any communication from a patent holder
   asserting standards-essential patents against this component
   or against customers who incorporate it?

6. Will you provide copies of the relevant licenses, or the
   relevant provisions, under a confidentiality agreement?

We refer you to Section [__] of our Supply Agreement dated
[date] regarding intellectual property indemnification.

Please respond by [date].

Very truly yours,

Drafting notes.

Question 2 is the question. A supplier that is licensed for its own manufacture but whose license does not reach downstream use has not solved your problem, and suppliers routinely answer question 1 as though it answered question 2.

Question 5 matters for timing. A supplier that has already received a demand may be negotiating, and coordinating is better than duplicating.

The reference to the indemnity section is deliberate. It signals that you have read it and it prompts the supplier to read it too.

Send it before there is a dispute. Suppliers answer these letters more helpfully when nothing is pending.

3. Implementer willingness response

The single highest-value document in this practice. Send it within three weeks.

[Date]

[Patent Holder]

Re: Your letter of [date] regarding [standard] patents

Dear [__]:

Thank you for your letter of [date]. We write promptly to
respond.

**[Company] is willing to take a license to [Patent Holder]'s
patents that are essential to [standard] on fair, reasonable,
and non-discriminatory terms.** We would like to reach
agreement on such a license and are prepared to engage
promptly and in good faith.

To evaluate your proposal, we request the following:

1. **The patents.** A list of the patents you contend are
   essential to [standard] and infringed by our products,
   identified by number and by the standard section each is
   said to be essential to.

2. **Claim charts.** For a representative sample, charts
   mapping each claim element to the specific section, clause,
   and release of the standard.

3. **Essentiality.** For each charted patent, confirmation
   whether the mapped section is mandatory or optional in the
   relevant release.

4. **The rate.** The basis for the [rate] you propose,
   including the royalty base and the apportionment reasoning.

5. **Comparable licenses.** Licenses to this portfolio or
   comparable portfolios on which you rely. We enclose a draft
   confidentiality agreement and are prepared to execute it
   promptly.

6. **Licensing level.** Whether you license at the component
   level, and whether any of our suppliers — including
   [supplier] — hold licenses from you.

We propose the following schedule: your response by [date]; our
technical evaluation by [date]; our substantive counter-proposal
by [date]. We are available for a technical meeting at your
convenience.

Please direct communications to [name, title, contact].

Very truly yours,

Enclosure: Draft Confidentiality Agreement

Drafting notes.

The bolded sentence is the letter. It is free, it commits you to nothing about the rate, and it makes an unwillingness finding very difficult in any forum. An implementer that omits it has given away its best move.

The enclosed confidentiality agreement matters. Offering one — rather than asking the patent holder to propose one — removes the "the implementer refused to enter an NDA" argument entirely.

The proposed schedule does real work. It demonstrates engagement and it creates a benchmark against which the patent holder's responsiveness is later measured.

Do not deny infringement here. Save the technical position for after you have the charts.

4. Patent holder notice letter

[Date]

[Implementer]

Re: [Standard] Standard-Essential Patents — Licensing

Dear [__]:

[Patent Holder] owns patents essential to [standard], and has
declared them to [SSO] with a commitment to license on fair,
reasonable, and non-discriminatory terms. We understand
[Implementer]'s [products] implement [standard, release]. We
write to offer a license.

**1. THE PATENTS.** Enclosed as Exhibit A is a list of [__]
patent families we consider essential to [standard]. Exhibit B
identifies [__] representative patents.

**2. CLAIM CHARTS.** Enclosed as Exhibit C are claim charts for
the representative patents, mapping each element of the
identified claims to the specified sections of [standard,
release]. Each mapped section is mandatory in that release.

**3. OUR OFFER.** We offer a worldwide, non-exclusive license
to our [standard]-essential portfolio for the term [__], at
[rate] per [unit / percentage of net selling price of the
licensed product], with a release for past sales through
[date].

**4. THE BASIS FOR THE RATE.** [State it: comparable licenses,
a top-down analysis, or both. Identify the apportionment
reasoning and the royalty base.] We have entered licenses on
comparable terms with [number] licensees and are prepared to
share those agreements under a confidentiality agreement; a
draft is enclosed as Exhibit D.

**5. LICENSING LEVEL.** [State your position and whether the
implementer's suppliers hold licenses.]

**6. NEXT STEPS.** We propose a technical meeting within [30]
days and would welcome a substantive response by [date]. Our
contact is [name, title, authority].

Very truly yours,

Exhibits A–D

Drafting notes.

Sections 2 and 4 are what distinguish a serious letter from a demand. A patent holder that sends a rate without charts and without a basis has given the implementer its best argument, and it will be quoted for years.

Confirming that mapped sections are mandatory forecloses the easiest essentiality attack and signals that you did the work.

Enclosing the confidentiality agreement removes a month of back and forth.

Section 6's named contact with authority matters. Negotiations stall when neither side's contact can agree to anything.

5. Essentiality analysis worksheet

ESSENTIALITY ANALYSIS — U.S. Patent No. __________
Standard: __________  Release: __________
Analyst: __________  Date: __________

CLAIM 1 MAPPING
| Element | Standard section cited | What the section requires |
  Does the element read on it? | Mandatory or optional? |
  Notes |
| 1.a | § 5.3.2 | [quote] | Yes | Mandatory | |
| 1.b | § 5.3.4 | [quote] | Yes | **OPTIONAL** | We do not
  implement |
| 1.c | § 6.1 | [quote] | **No — claim requires X; standard
  permits X or Y** | Mandatory | |

FINDINGS
[ ] Essential — every element maps to mandatory requirements
[ ] Not essential — element(s) ___ map to optional features
[ ] Not essential — claim requires more than the standard
[ ] Essential but we do not implement the relevant feature
[ ] Arguably essential — the mapping is contestable because ___

VALIDITY (only if essentiality survives)
Prior art identified: ______________  Strength: ____/5

PORTFOLIO EXTRAPOLATION
Patents charted by the holder: ______
Found arguably essential: ______  (____%)
[NOTE: charted patents are presumably the holder's best.]
Declared portfolio size: ______
**ESTIMATED GENUINELY ESSENTIAL: ______ (____%)**

Drafting notes.

The "mandatory or optional" column is the highest-value one. Optional features you do not implement cannot support standards-based infringement, and declared portfolios contain many patents mapped to optional sections.

Row 1.c's pattern recurs constantly: a claim requiring one specific approach where the standard permits several. Practicing the standard then does not necessarily infringe, and the patent holder must prove infringement product by product.

The extrapolation is imprecise and it is the only quantitative estimate anyone will have. State the methodology and the sample size; a defensible estimate beats an assertion.

6. Top-down valuation model

TOP-DOWN ROYALTY MODEL — [Standard]
Prepared by: __________  Date: __________

STEP 1 — AGGREGATE ROYALTY BURDEN
What should ALL essential patents on [standard] collectively
earn?
Sources considered:
  [ ] Public statements by SSO participants at standard
      adoption
  [ ] Published pool rates and coverage
  [ ] Industry studies
  [ ] Product economics (device margin analysis)
Selected aggregate: ______% of [base] or $______ per unit
Rationale: ______________________________

STEP 2 — THE DENOMINATOR
Declared-essential families for [standard]: ______
Essentiality rate applied: ______%
Source of the essentiality rate:
  [ ] Our own sampling of ___ patents
  [ ] Published essentiality studies
  [ ] Third-party evaluation
**ADJUSTED ESSENTIAL FAMILIES: ______**

STEP 3 — THE NUMERATOR
Holder's declared families: ______
Essentiality rate from our charting: ______%
**HOLDER'S ADJUSTED ESSENTIAL FAMILIES: ______**

STEP 4 — SHARE
Numerator / Denominator = ______%

STEP 5 — RELATIVE VALUE ADJUSTMENT
[ ] No adjustment (pure count)
[ ] Adjustment for technical importance: ______
    Basis: ______________________________

STEP 6 — RESULT
Aggregate × Share = ______% of [base], or $______ per unit
Per-unit at device base ($__): $______
Per-unit at component base ($__): $______
[The same number, expressed two ways.]

CROSS-CHECK AGAINST COMPARABLES
Comparable-derived rate: $______
Difference: ______  Reconciliation: ______________

Drafting notes.

Step 2 is where the model is attacked, so document the essentiality rate's source. A rate drawn from your own charting of a meaningful sample is far more defensible than one taken from a study of a different standard.

Step 6's dual expression prevents the base argument from obscuring the number. Offering the same royalty at either base makes clear that the dispute is about apportionment methodology rather than about money.

The cross-check is not optional. A party presenting one methodology and dismissing the other is less persuasive than one that reconciles them.

7. Comparable license normalization table

COMPARABLE LICENSE ANALYSIS — [Portfolio]

| # | Licensee | Date | Portfolio scope | Standards | Field |
  Geography | Term | Structure | Stated rate | Cash or cross? |
  Volume assumption | Litigation context | NORMALIZED RATE |
  Comparable? | Why / why not |

NORMALIZATION ADJUSTMENTS APPLIED
Portfolio scope: [license covered ___ patents vs ___ asserted;
  adjustment: ______]
Lump sum to running: [amount / assumed units over term]
Cross-license: [value of the incoming rights; net balancing
  payment analysis]
Litigation settlement: [discount for litigation cost avoidance]
Time: [adjustment for portfolio changes since]
Geography: [scope difference]

SIMILARLY SITUATED ANALYSIS (non-discrimination)
| Licensee | Volume | Product type | Market position | Rate |
  Similarly situated to us? | Rate difference | Justification
  offered |

CONCLUSION
Best comparables: ______________________
Derived rate range: $______ to $______
Discrimination argument available? [ ] Yes [ ] No

Drafting notes.

The "Why / why not" column is what a tribunal reads. Excluding a license because it is a cross-license with no cash rate is a reasoned exclusion; excluding it because it is inconvenient is not.

The similarly situated table is the non-discrimination case, which is the least developed element of FRAND and therefore the one where a well-built record has the most room to persuade.

Litigation settlements get discounted by tribunals as reflecting litigation cost rather than technology value. Note the context for each.

8. Counter-offer letter

[Date]

[Patent Holder]

Re: [Standard] licensing — [Company]'s counter-proposal

Dear [__]:

Thank you for your materials of [date]. We have completed our
technical and economic analysis and write with a substantive
counter-proposal, as we indicated we would.

**1. OUR OFFER.** [Company] offers to take a worldwide,
non-exclusive license to your [standard]-essential portfolio
for a term of [__] years at **$[__] per licensed unit**, with a
release for past sales through [date].

**2. OUR ESSENTIALITY ANALYSIS.** We charted each of the [__]
patents you provided against [standard, release]. Our findings:

  Arguably essential and implemented by our products: ___
  Mapped to optional features we do not implement: ___
  Claims requiring more than the standard requires: ___
  Subject to substantial invalidity questions: ___

Our detailed analysis is enclosed as Annex 1. We would welcome
a technical discussion of any point on which you disagree.

**3. TOP-DOWN ANALYSIS.** [Summarize: aggregate burden, adjusted
denominator, adjusted numerator, share, result.] Annex 2.

**4. COMPARABLE LICENSES.** [Summarize the analysis of the
licenses produced, the normalization applied, and the derived
range.] Annex 3.

**5. ROYALTY BASE.** The standardized functionality is
implemented in the [component], which we purchase at $[__].
Our offer is stated per unit and is equivalent to [__]% of the
component price or [__]% of the device price.

**6. RESPONSE TO YOUR RATE.** [Address the holder's basis
directly: why the comparables cited are not comparable, or why
the base is wrong.]

**7. SECURITY.** As set out in our separate letter of [date],
we have placed $[__] in escrow representing our offer for the
period [__] to [__].

We remain willing to reach agreement and are available to meet.

Very truly yours,

Annexes 1–3

Drafting notes.

Section 2's honest breakdown is more persuasive than a lower number. A counter-offer supported by an analysis that concedes some patents are essential reads as credible; one that finds nothing essential reads as advocacy.

Section 5's dual expression takes the base argument off the table as a distraction.

Section 7's escrow reference is why the security letter should precede or accompany this one.

Never offer zero. A nominal counter-offer without justification is the fact that establishes unwillingness.

9. Escrow and security notice

[Date]

[Patent Holder]

Re: Security pending resolution — [standard] licensing

Dear [__]:

Further to our counter-proposal of [date], and to demonstrate
our good faith while the parties work toward agreement,
[Company] has established security as follows:

1. **Amount.** $[__], representing royalties at our offered
   rate of $[__] per unit for [__] units sold during the period
   [date] to [date].

2. **Form.** [Escrow account at [institution] under the
   attached escrow agreement / irrevocable standby letter of
   credit no. [__] issued by [bank] / bond no. [__]].

3. **Release.** The funds will be released to [Patent Holder]
   upon (a) execution of a license agreement, (b) a final
   determination of FRAND terms by a court or arbitral tribunal
   of competent jurisdiction, or (c) written agreement of the
   parties.

4. **Ongoing.** We will supplement the security quarterly for
   continuing sales at the same rate.

5. **No admission.** This security is provided without
   admission as to infringement, essentiality, validity, or the
   appropriate rate, and without prejudice to any position.

6. **Accounting.** Enclosed is a statement of units sold during
   the period, certified by [officer].

Very truly yours,

Drafting notes.

This is the highest-return document an implementer files relative to its cost. It is the strongest available evidence of good faith, it neutralizes the exclusion order argument at the ITC, and it costs only the time value of the escrowed funds.

Paragraph 4's ongoing commitment matters. A one-time deposit that is never supplemented undercuts the point.

Paragraph 6's accounting satisfies the "render an account" element of most willingness frameworks.

Paragraph 5 is essential and it does not weaken the gesture.

10. Negotiation log

The document from which the willingness record is built. Maintain it from the first letter.

NEGOTIATION LOG — [Company] / [Patent Holder] — [Standard]

| # | Date | From | To | Type | Substance | Days since prior |
  Response due | Responded on | Days elapsed |
| 1 | Mar 3 | PH | Us | Demand letter | Rate demand, no charts,
  no basis | — | — | Mar 24 | 21 |
| 2 | Mar 24 | Us | PH | Response | Willingness stated; charts,
  essentiality, rate basis, comparables requested; NDA enclosed
  | 21 | Apr 24 | Jun 8 | **76** |
| 3 | Jun 8 | PH | Us | Charts | 8 patents charted | 76 | — | — |

RESPONSIVENESS SUMMARY
Our average response time: ______ days
Their average response time: ______ days
Longest unanswered request (ours): ______ days
Longest unanswered request (theirs): ______ days

COMMITMENTS MADE AND KEPT
| Party | Commitment | Due | Met? |

OUTSTANDING REQUESTS
| Requested by | What | Date requested | Days outstanding |

Drafting notes.

The days-elapsed column is the whole document. Every willingness framework asks who responded promptly and who did not, and a table showing three-week responses on one side and eleven-week silences on the other is more persuasive than any characterization.

Maintain it contemporaneously. Reconstructing it later is possible and much less credible.

Both sides should keep one, and both should notice when their own column looks bad.

11. ITC public interest submission outline

STATEMENT ON THE PUBLIC INTEREST
[Investigation No. 337-TA-____]

I.   INTRODUCTION
     Why an exclusion order would harm the public interest
     here: a FRAND-committed patent asserted against a willing
     licensee.

II.  THE STATUTORY FACTORS
     A. Public health and welfare
        [If the products serve health, safety, infrastructure,
        or critical functions, develop this specifically.]
     B. Competitive conditions in the U.S. economy
        [Effect on downstream competition; whether the
        complainant competes.]
     C. Production of like or directly competitive articles
        [Supply availability; whether alternatives exist and on
        what timeline.]
     D. U.S. consumers
        [Price and availability effects.]

III. THE FRAND COMMITMENT AND RESPONDENT'S WILLINGNESS
     A. Complainant committed to license on FRAND terms
     B. Respondent responded within [__] days and stated
        willingness [Exhibit __]
     C. Respondent requested and analyzed claim charts
        [Exhibit __]
     D. Respondent made a supported counter-offer [Exhibit __]
     E. Respondent has placed $[__] in escrow [Exhibit __]
     F. **The negotiation log** [Exhibit __]
     G. Complainant declined arbitration [Exhibit __]
     H. An exclusion order would confer leverage inconsistent
        with the FRAND commitment

IV.  A MONETARY REMEDY IS AVAILABLE AND ADEQUATE
     [The district court action; the rate determination sought;
     the security already provided.]

V.   TAILORED RELIEF, IF ANY ORDER ISSUES
     [Carve-outs, transition periods, service and repair
     exceptions, certification provisions.]

VI.  CONCLUSION

Drafting notes.

Section III is the submission. The statutory factors are argued in every investigation; what distinguishes an SEP submission is a documented record of the respondent's reasonableness and the complainant's conduct. This section is written from the negotiation log and the escrow notice — which is why those documents are created months earlier.

Section V matters even when you expect to lose. Tailored relief — a transition period, a service and repair carve-out — can be worth a great deal, and a respondent that argues only for no order gets no order or a full one.

12. License term sheet

SEP LICENSE TERM SHEET — [Holder] / [Licensee]

ROYALTY
Rate: $[__] per Licensed Unit / [__]% of Net Selling Price
Base: [defined: the Licensed Product / the component]
Tiering: [volume bands, if any]
Cap / floor: [__]
Payment: quarterly, within [45] days of quarter end
Currency: [__]

SCOPE
Licensed Patents: [all patents Holder owns or controls that are
  essential to [standards], including patents issuing during
  the Term]
Standards: [list, including future releases]
Licensed Products: [defined by CATEGORY, not model number]
Territory: Worldwide
Have-made rights: Yes, including contract manufacturers
Affiliates: Included; treatment on acquisition: [__]
Downstream: Sale of a Licensed Product exhausts the Licensed
  Patents as to that unit for all purposes

TERM AND RELEASE
Term: [__] years from [date]
Release: All claims through [date] for all products
Covenant: Holder will not assert any patent not licensed
  hereunder against the same functionality during the Term

LICENSEE PROTECTIONS
Most favored licensee: If Holder grants a similarly situated
  licensee a lower effective rate, this rate adjusts.
  Comparison methodology: [__]
Portfolio shrinkage: Rate adjusts if essential families fall
  below [__]% of the number at execution
Transferees: Holder will require any transferee of Licensed
  Patents to take subject to this Agreement
Audit: Not more than once annually, by an independent auditor,
  at Holder's expense unless underpayment exceeds [5]%
Challenge: Licensee may challenge validity or essentiality;
  [consequence, if any]

HOLDER PROTECTIONS
Reporting: quarterly, by product and territory
Late payment: [__]% per annum
Termination: material breach with [60] days' cure
Confidentiality: mutual, with carve-outs for auditors,
  advisors, and litigation

DISPUTE RESOLUTION
Rate adjustments and audits: arbitration under [rules]
Governing law: [__]

Drafting notes.

"Licensed Products defined by category" is the provision that determines whether the license survives your next product generation. Model-number definitions require amendment every year.

The downstream exhaustion sentence is what your customers need and what a supplier-level license usually lacks.

Most-favored-licensee with a defined comparison methodology is worth more than the clause without one; "similarly situated" undefined is unenforceable in practice.

The transferee provision is increasingly important as portfolios change hands, and it is easy to omit.

13. Arbitration proposal

[Date]

[Counterparty]

Re: Proposal for binding arbitration of FRAND terms

Dear [__]:

The parties disagree about the rate. We propose resolving that
disagreement through binding arbitration rather than
litigation in multiple jurisdictions.

We propose the following framework:

1. **Scope.** A worldwide, non-exclusive license to [Holder]'s
   patents essential to [standards], for [Licensee]'s products
   in [categories], for a term of [__] years.

2. **The question.** What rate and terms are fair, reasonable,
   and non-discriminatory?

3. **Methodology.** The tribunal shall consider comparable
   licenses and a top-down analysis, and shall address
   apportionment and the royalty base expressly.

4. **Essentiality.** [Determined by the tribunal on a sample of
   [__] patents selected [__] / assumed for purposes of the
   rate determination].

5. **Tribunal.** Three arbitrators with experience in patent
   licensing and telecommunications standards, appointed under
   [rules].

6. **Interim measures.** Neither party will seek injunctive
   relief or exclusion orders on the Licensed Patents during
   the arbitration. [Licensee] will maintain security in the
   amount of $[__].

7. **Award.** Binding and non-appealable; the parties will
   execute a license on the terms determined.

8. **Confidentiality.** The proceeding and the award are
   confidential, subject to disclosure necessary to implement
   the license.

9. **Costs.** [Allocation.]

We are prepared to begin immediately.

Very truly yours,

Drafting notes.

Propose this from either side. A refusal to arbitrate is increasingly offered as evidence of unwillingness, and the proposal costs nothing but a letter. The party that proposes it has made a record it will use in every forum.

Paragraph 6 is what makes it acceptable to an implementer and what a patent holder resists, because the injunction leverage is the point. That is the trade being negotiated.

Paragraph 4's essentiality question is the one most often left vague and it drives the outcome. Decide whether the tribunal determines essentiality on a sample or assumes it, because the two produce very different numbers.

14. Supply agreement indemnity provision

For an implementer negotiating with a component supplier — and read carefully by any supplier being asked to sign it.

[__]. INTELLECTUAL PROPERTY INDEMNIFICATION

(a) Supplier shall defend, indemnify, and hold harmless Buyer
and its customers against any claim that the Components, or
Buyer's incorporation of the Components into Buyer's products
in accordance with Supplier's specifications, infringes any
patent, including any patent claimed to be essential to any
standard implemented by the Components.

**[NOTE TO IMPLEMENTER: The final clause is the point. Many
standard indemnities carve out standards-essential patents,
which is precisely the exposure that matters.]**

(b) Supplier represents that it has obtained, or will obtain,
licenses to all patents essential to [standards] as implemented
in the Components, covering (i) Supplier's manufacture and
sale, (ii) Buyer's incorporation of the Components, and
(iii) Buyer's worldwide sale of products incorporating them.

(c) Supplier shall notify Buyer within [10] days of any
communication asserting standards-essential patents against the
Components or against any customer.

(d) Supplier shall cooperate with Buyer in any licensing
negotiation or proceeding relating to the Components, including
by providing technical information about which standard
sections and optional features the Components implement.

(e) Buyer's remedies under this Section are [not] limited by
any limitation of liability elsewhere in this Agreement, and
[are / are not] subject to the cap in Section [__].

Drafting notes.

Subsection (a)'s final clause is the whole provision. A supplier's standard indemnity that excludes standards-essential patents leaves the implementer exposed to the largest category of claim it will face. Negotiate it, price it, or know that you do not have it.

Subsection (b)(iii)'s downstream coverage is what makes a supplier license useful to you.

Subsection (d) is underused and cheap. The supplier knows which standard sections its component implements, and that information is the essentiality analysis you will otherwise pay to develop.

Subsection (e) matters. An SEP indemnity subject to a cap equal to twelve months of component purchases is not meaningful protection against a device-level royalty claim.

Related documents

This toolkit is general information, not legal advice, and does not create an attorney-client relationship. Templates require adaptation by counsel to the standard, the portfolio, and the applicable SSO policy and governing law.