Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 1 of 109
`
`
`
`IN THE UNITED STATES COURT OF FEDERAL CLAIMS
`
`
`
`
`C.A. No. 19-859-RTH
`
`
`E-NUMERATE SOLUTIONS, INC. and
`
`E-NUMERATE, LLC,
`
`
`
`
`Plaintiffs,
`
`v.
`
`
`
`
`THE UNITED STATES OF AMERICA,
`
`
`
`
`
`
`
`
`
`
`Defendant.
`
`
`
`JOINT CLAIM CONSTRUCTION STATEMENT
`
`Plaintiffs e-Numerate Solutions, Inc. and e-Numerate, LLC (collectively “e-Numerate”)
`
`and Defendant the United States of America respectfully submit this Joint Claim Construction
`
`Statement (“JCCS”) pursuant to the Court’s Scheduling Order (Dkt. # 94). Section I lists the claim
`
`terms for the Asserted Patents for which the parties have agreed on a joint proposed construction.
`
`Section II and Exhibit A contain the parties’ proposed constructions for the disputed terms, along
`
`with supporting intrinsic and extrinsic evidence.
`
`I.
`
`Terms Proposed for Construction on Which the Parties Have Reached Agreement
`
`As reflected in the parties’ proposed constructions, the parties have reached agreement on
`
`certain terms’ proposed constructions as detailed in the following table.
`
`Term/Phrase
`“meta-data”
`
`“metadata”
`
`“at least one of … and”
`
`
`Agreed-Upon Definition
`“data about data”
`
`
`“data about data”
`
`“at least one of … or”
`
`“operation”
`
`
`plain and ordinary meaning
`
`Patents/Claims
`‘355 Patent - 1, 13, 27, 28, 40,
`54;
`
`‘748 Patent – 20
`
`‘355 Patent - 7, 8, 9, 10, 11, 12,
`14, 21, 34, 35, 36, 37, 38, 39,
`41, 46, 55;
`‘816 Patent - 1, 4, 10, 17, 20, 26,
`27;
`
`‘355 Patent - 1, 27, 28, 54
`
`
`
`
`
`IN THE UNITED STATES COURT OF FEDERAL CLAIMS
`
`
`
`
`C.A. No. 19-859-RTH
`
`
`E-NUMERATE SOLUTIONS, INC. and
`
`E-NUMERATE, LLC,
`
`
`
`
`Plaintiffs,
`
`v.
`
`
`
`
`THE UNITED STATES OF AMERICA,
`
`
`
`
`
`
`
`
`
`
`Defendant.
`
`
`
`JOINT CLAIM CONSTRUCTION STATEMENT
`
`Plaintiffs e-Numerate Solutions, Inc. and e-Numerate, LLC (collectively “e-Numerate”)
`
`and Defendant the United States of America respectfully submit this Joint Claim Construction
`
`Statement (“JCCS”) pursuant to the Court’s Scheduling Order (Dkt. # 94). Section I lists the claim
`
`terms for the Asserted Patents for which the parties have agreed on a joint proposed construction.
`
`Section II and Exhibit A contain the parties’ proposed constructions for the disputed terms, along
`
`with supporting intrinsic and extrinsic evidence.
`
`I.
`
`Terms Proposed for Construction on Which the Parties Have Reached Agreement
`
`As reflected in the parties’ proposed constructions, the parties have reached agreement on
`
`certain terms’ proposed constructions as detailed in the following table.
`
`Term/Phrase
`“meta-data”
`
`“metadata”
`
`“at least one of … and”
`
`
`Agreed-Upon Definition
`“data about data”
`
`
`“data about data”
`
`“at least one of … or”
`
`“operation”
`
`
`plain and ordinary meaning
`
`Patents/Claims
`‘355 Patent - 1, 13, 27, 28, 40,
`54;
`
`‘748 Patent – 20
`
`‘355 Patent - 7, 8, 9, 10, 11, 12,
`14, 21, 34, 35, 36, 37, 38, 39,
`41, 46, 55;
`‘816 Patent - 1, 4, 10, 17, 20, 26,
`27;
`
`‘355 Patent - 1, 27, 28, 54
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 2 of 109
`
`
`
`“object”
`
`“interpreted code”
`
`“markup document”
`
`“data document”
`
`plain and ordinary meaning
`
`
`“code that is executed by an
`interpreter”
`“a document that contains
`markup language tags”
`
`“a markup language document
`that contains data”
`
`
`“line item”
`
`“a set of data values that share
`metadata”
`
`
`
`‘383 Patent – 15;
`‘748 Patent – 11, 19;
`‘337 Patent – 1;
`
`‘355 Patent - 1, 27, 28, 54;
`
`‘816 Patent - 1, 10, 17, 26, 27;
`‘383 Patent - 1, 17, 18;
`
`‘383 Patent - 7, 8, 9, 10, 11, 12,
`15;
`‘384 Patent – 66;
`‘748 Patent - 1, 10, 11, 12, 13,
`14, 20;
`‘842 Patent – 29;
`‘337 Patent – 1;
`‘708 Patent - 1, 10, 17;
`
`‘383 Patent - 7, 8, 15;
`‘384 Patent – 66;
`‘748 Patent - 1, 4, 5, 11, 15, 16,
`19, 20;
`‘842 Patent – 29;
`‘337 Patent – 1;
`‘708 Patent - 1, 10, 17;
`
`
`II.
`
`Proposed Claim Constructions and Supporting Evidence
`
`In the chart attached as Exhibit A, the parties propose constructions for the disputed claim
`
`terms and identify intrinsic and extrinsic evidence which they may rely upon to support their
`
`respective proposed constructions.
`
`III.
`
`Proposed Dates for Markman Hearing
`
`The parties have met and conferred about proposed dates for the Markman Hearing. The
`
`parties’ respective positions are as follows:
`
`A. e-Numerate’s Position
`
` e-Numerate’s client representatives would like to attend the Markman Hearing. e-
`
`Numerate’s counsel and client representatives could attend a hearing on September 14 – 16 and
`
`October 3, 6, and 7, 2022. If the Court is not available on any of these dates, e-Numerate
`
`respectfully requests that the Court provide dates when it is convenient for the Court to hold the
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 3 of 109
`
`
`
`Markman hearing.
`
`B. Defendant’s Position
`
`Defendant is available on September 13-16 and 19-23, 2022. Should the Court seek
`
`additional potential dates in October, Defendant will provide such dates upon request.
`
`
`
`Dated: August 18, 2022
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Of Counsel:
`SCOTT BOLDEN
`NELSON KUAN
`Department of Justice
`
`
`
`
`
`
`
`Respectfully submitted,
`
`/s/ Sean T. O’Kelly
`Sean T. O’Kelly
`Gerard M. O’Rourke
`O’KELLY & O’ROURKE, LLC
`824 N. Market Street, Suite 1001A
`Wilmington, DE 19801
`302-778-4000
`sokelly@okorlaw.com
`gorourke@okorlaw.com
`
`Attorneys for Plaintiffs
`
`BRIAN M. BOYNTON
`Principal Deputy Assistant Attorney
`General
`
`GARY L. HAUSKEN
`Director
`
`
`s/ Shahar Harel
`SHAHAR HAREL
`Trial Attorney
`Commercial Litigation Branch
`Civil Division
`Department of Justice
`Washington, DC 20530
`Email:
`Shahar.Harel@USDOJ.gov
`Telephone: (202) 305-3075
`Facsimile: (202) 307-0345
`COUNSEL FOR THE UNITED STATES OF
`AMERICA
`
`
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 4 of 109
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 4 of 109
`
`
`
`
`
`
`
`EXHIBIT A
`EXHIBIT A
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 5 of 109
`
`JOINT CLAIM CONSTRUCTION CHART
`A. ’355 Patent
`
`’355 Patent - Term 1
`
`Claim Term
`
`Claims
`
`e-Numerate
`Construction
`
`series of numerical
`values having tags
`indicating
`characteristics of the
`numerical values
`
`
`1, 27, 28 and 54 A set of one or more
`numerical values
`having markup
`language tags
`wherein the markup
`language tags for the
`one or more
`numerical values
`have more than one
`attribute that explains
`the meaning of the
`numerical values
`
`
`
`
`Defendant
`Intrinsic and
`Extrinsic Support
`’355 Patent at
`Abstract, 2:1-2,
`4:28-30, 8:38-40,
`15:43-46, 17:57-
`60, 20:23-59,
`21:31-33, 24:50-
`60, 25:34-37.
`
`
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘355 Patent at
`Abstract; Col. 4,
`lines 28 - 30; Col. 8,
`lines 38 - 40;
`Figure 10, steps
`1010 and 1012;
`Figure 21 steps
`2106 and 2018; Col.
`7, lines 7 – 11; col.
`7, lines 42-44; Col.
`16, lines 55 – 57;
`Figure 4 and Col.
`17, line 55 – col.
`18, line 3; col. 18,
`lines 22 – 25; col.
`18, lines 50 – 60;
`col. 19, lines 12 –
`14; col. 19, line 57
`– col. 20, line 1;
`col. 20, lines 11 –
`64; col. 24, lines 50
`– 60; col. 25, lines
`34 – 37;
`
`1
`
`Defendant
`Construction
`
`Plain and ordinary
`meaning
`(incorporating
`Defendant’s
`construction of
`“tag/tags”).
`Defendant maintains
`that the term “tag”
`should be construed
`as “markup language
`tag” and “tags” as
`“markup language
`tags.” Alternatively,
`to the extent the
`term is construed as
`a whole, Defendant
`proposes
`“A set of one or
`more numerical
`values having
`markup language
`tags wherein the
`markup language
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 6 of 109
`
`
`
`’355 Patent - Term 2
`
`Claim Term
`
`Claims
`
`tag/tags
`
`1, 13, 14, 15, 27,
`28, 40, 41, 42,
`54
`
`‘816 patent, claim
`27 (claim
`differentiation)
`(“characteristic”);
`
`Appendix B of
`‘383, ‘384, ’748 and
`‘337 patents via
`incorporation by
`reference;
`
`tags for the one or
`more numerical
`values have one or
`more attributes that
`describe the
`meaning of the one
`or more numerical
`values.”
`
`e-Numerate Intrinsic
`and Extrinsic
`Support
`‘355 Patent at Col. 1,
`lines 32 - 36
`
`e-Numerate
`Construction
`
` “Tag” should not be
`construed as a stand-
`alone term because e-
`Numerate has
`identified a phrase for
`construction. In
`addition, the claim
`language uses the
`term “tags” in the
`plural. To the extent
`“tags” is construed,
`e-Numerate contends
`that the term “tags”
`should be construed
`
`Defendant Intrinsic
`and Extrinsic
`Support
`’355 Patent at
`Abstract, 1:65-66,
`2:1-2, 4:28-30,
`8:38-40, 9:5-6,
`15:43-46, 17:57-
`60, 20:23-59,
`21:31-33, 24:50-
`60, 25:34-37.
`
`
`
`Defendant
`Construction
`
`“Tag” should be
`construed as “markup
`language tag” and
`“tags” as “markup
`language tags.”
`Further, a markup
`language is “a
`language that uses
`tags to define
`elements within a
`document. Examples
`of markup languages
`include HTML, XML
`and XBRL.”
`
`
`
`2
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 7 of 109
`
`as “markup language
`tags”.
`
`
`
`’355 Patent - Term 3
`
`Claim Term
`
`Claims
`
`e-Numerate
`Construction
`
`macro
`
`1, 2, 3, 4, 6, 25,
`26, 27, 28, 29,
`30, 31, 33, 52,
`53, 54, 55
`
`Interpreted code that
`performs one or more
`well-defined,
`generally limited
`tasks
`
`
`
`’355 Patent -Term 4
`
`Claim Term
`
`Claims
`
`e-Numerate
`Construction
`
`transform the series
`of numerical values
`into a new
`representation of
`the series of
`numerical values
`
`
`1, 27, 28 and 54 Converting the series
`of one or more
`numerical values and
`one or more of the
`attributes for the
`numerical values into
`a new series of one or
`more numerical
`
`Defendant
`Construction
`
`Short program which
`performs one or more
`well-defined, limited
`tasks
`
`Defendant Intrinsic
`and Extrinsic
`Support
`’355 Patent at 2:55-
`57.
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘355 Patent at Col.
`2, lines 54 – 62;
`col. 3, lines 11 –
`15; col. 7, lines 37
`– 39; col. 13, lines
`27 – 43; col. 53,
`lines 22 – 32.
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘355 Patent at Col.
`4, lines 4 – 30;
`
`Defendant
`Construction
`
`Plain and ordinary
`meaning
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`’355 Patent Claims
`1, 27, 28 and 54.
`
`
`
`3
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 8 of 109
`
`
`
`’355 Patent - Term 5
`
`Claim Term
`
`Claims
`
`1, 28
`
`generating at least
`one second title
`corresponding to
`results of the
`operation
`
`
`
`’355 Patent - Term 6
`
`Claim Term
`
`Claims
`
`the step of
`receiving
`
`15 and 42
`
`
`
`values and one or
`more attributes that
`reflects the operation
`
`e-Numerate
`Construction
`
`Plain and ordinary
`meaning
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘355 Patent at Col.
`13, lines 4 – 20;
`col. 28, lines 57 –
`61; col. 36, lines 17
`– 33;
`
`Defendant
`Construction
`
`Generating at least
`one second title based
`on the results of the
`operation and the tags
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`’355 Patent: claims
`1, 28; at 56:42-47
`
`Defendant
`Construction
`
`Indefinite
`
`e-Numerate
`Construction
`
`Not indefinite. In
`claim 15, the step
`referred to is
`“receiving a series of
`numerical values
`having tags indicating
`characteristics of the
`numerical values” in
`claim 1. In claim 42,
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`Intrinsic Support
`
`‘355 Patent at
`Language of the
`claims; col. 49,
`lines 40 – 45;
`
`Extrinsic Support
`
`
`4
`
`Defendant Intrinsic
`and Extrinsic
`Support
`Intrinsic Support
`
`’355 Patent: Claims
`1, 15, 28, 42; at
`20:23-54; 50:2-5;
`50:35; 50-39-55;
`50:39-55.
`
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 9 of 109
`
`
`
`’355 Patent -Term 7
`
`Claim Term
`
`Claims
`
`report2
`
`21
`
`Smith Declaration
`pars. 34 - 491
`
`the step referred to is
`“receiving a series of
`numerical values
`having tags indicating
`characteristics of the
`numerical values” in
`claim 28.
`
`’748 Patent: col.
`97-col. 106; col.
`107-col. 112.
`
`Extrinsic Support
`
`ECF 81-7 (“Martin
`Decl.”) at ¶¶ 41-46.
`
`e-Numerate
`Construction
`
`Plain and ordinary
`meaning
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘355 Patent at Col.
`2, lines 35 – 41;
`col. 9, lines 36 –
`52; col. 12, lines
`4–- 11; col. 13,
`line 55 – col. 14,
`line 7; col. 16,
`lines 31 – 46; ‘842
`
`Defendant
`Construction
`
`Document generated
`by combining an
`XML-compliant
`document with a
`template.
`
`Defendant Intrinsic
`and Extrinsic
`Support
`’355 Patent at
`9:36-52; 12:4-7;
`16:31; 16:40-46.
`
`XML Bible3 at
`110, 132.
`
`
`1 e-Numerate contends that reference to extrinsic evidence by either party is inappropriate for all terms in dispute. Support from the
`Smith Declaration is cited only in the event that the Court considers extrinsic evidence.
`2 The Government did not list this term with respect to the ‘842 Patent, but as indicated in its prior briefing seeks the same
`construction for this term in that patent based on the same disclosure. See ECF 90 at 10, n. 2. Intrinsic evidence within the ’842
`Patent includes U.S. Patent No. 6,920,608 at 9:48-64; 12:18-21; 16:46; 16:55-61; U.S. Patent No. 7,421,648 at 9:36-52; 12:4-7; 16:31;
`16:40-46. See also ECF 80 at 4.
`3 The XML Bible constitutes intrinsic evidence as it was incorporated by reference in the asserted patents and Defendant included
`relevant excerpts in its prior briefing. See ECF 82-1. Should the Court seek additional portions, Defendant will furnish them.
`5
`
`
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 10 of 109
`
`
`
`B. ’816 Patent
`
`’816 Patent -Term 1
`
`Claim Term
`
`Claims
`
`tags reflecting
`characteristics of the
`numerical values
`
`1, 10, 17, 26, 27
`
`patent, claim 29
`(Government does
`not seek
`construction of
`“report”); ‘842
`patent claims 32
`and 33 (claim
`differentiation).
`
`e-Numerate
`Construction
`
`Markup language
`tags wherein the
`markup language
`tags for the one or
`more numerical
`values have more
`than one attribute
`that explains the
`meaning of the
`numerical values
`
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘816 Patent at
`Abstract, col. 4,
`lines 29 – 33; col.
`8, lines 41 – 43;
`col. 16, lines 55 –
`67; col. 17, line 54
`– col. 18, line 2;
`col. 20, lines 10 –
`57; claim 27
`(“characteristic”).
`
`Appendix B of
`‘383, ‘384, ’748
`and ‘337 patents
`
`Defendant
`Construction
`
`Plain and ordinary
`meaning
`(incorporating
`Defendant’s
`construction of
`“tag/tags”)
`Defendant maintains
`that “tag” should be
`construed as
`“markup language
`tag” and “tags” as
`“markup language
`tags.” Further, a
`markup language is
`
`Defendant
`Intrinsic and
`Extrinsic Support
`’816 Patent at
`Abstract; 2:6-7;
`4:31-33; 8:41-43;
`15:43-46; 17:56-
`59; 20:24-57;
`21:22-25; 24:40-
`50; 25:25-28;
`25:30-33.
`
`’355 Patent at
`Abstract, 2:1-2,
`4:28-30, 8:38-40,
`15:43-46, 17:57-
`60, 20:23-59,
`
`
`
`6
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 11 of 109
`
`21:31-33, 24:50-
`60, 25:34-37.
`
`
`“a language that
`uses tags to define
`elements within a
`document.
`Examples of markup
`languages include
`HTML, XML and
`XBRL.” To the
`extent this term is
`construed,
`Defendant proposes:
`“Markup language
`tags wherein the
`markup language
`tags for the one or
`more numerical
`values have one or
`more attributes that
`describe the
`meaning of the
`numerical values.”
`
`via incorporation
`by reference;
`
`‘355 Patent at
`Abstract; Col. 4,
`lines 28 - 30; Col.
`8, lines 38 - 40;
`Figure 10, steps
`1010 and 1012;
`Figure 21 steps
`2106 and 2018;
`Col. 7, lines 7 –
`11; col. 7, lines
`42-44; Col. 16,
`lines 55 – 57;
`Figure 4 and Col.
`17, line 55 – col.
`18, line 3; col. 18,
`lines 22 – 25; col.
`18, lines 50 – 60;
`col. 19, lines 12 –
`14; col. 19, line 57
`– col. 20, line 1;
`col. 20, lines 11 –
`64; col. 24, lines
`50 – 60; col. 25,
`lines 34 – 37;
`
`
`7
`
`
`
`
`
`
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 12 of 109
`
`’816 Patent – Term 2
`
`Claim Term
`
`Claims
`
`tag/tags
`
`1, 3 – 8, 10, 17 and
`19 – 27
`
`
`
`
`
`
`
`
`
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘816 Patent at Col.
`1, lines 37 – 41;
`
`e-Numerate
`Construction
`
`“Tag” should not be
`construed as a stand-
`alone term. e-
`Numerate has
`identified a phrase
`for construction. In
`addition, the claim
`language uses the
`term “tags” in the
`plural. To the extent
`the term “tags” is
`construed, it should
`be construed as
`“markup language
`tags.”
`
`Defendant
`Construction
`
`“Tag” should be
`construed as
`“markup language
`tag” and “tags” as
`“markup language
`tags.” Further, a
`markup language is
`a “language that
`uses tags to define
`elements within a
`document.
`Examples of markup
`languages include
`HTML, XML and
`XBRL.”
`
`Defendant Intrinsic
`and Extrinsic
`Support
`’816 Patent at
`Abstract; 2:1-4;
`2:6-7; 4:31-33;
`8:41-43; 9:8-9;
`15:43-46; 17:56-
`59; 20:24-57;
`21:22-25; 24:40-
`50; 25:25-28;
`25:30-33.
`
`’355 Patent at
`Abstract, 2:1-2,
`4:28-30, 8:38-40,
`15:43-46, 17:57-
`60, 20:23-59,
`21:31-33, 24:50-
`60, 25:34-37.
`
`
`
`
`8
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 13 of 109
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘816 Patent at
`Abstract; col. 8,
`lines 28 – 43; col.
`26, lines 5 – 30;
`
`Defendant
`Construction
`
`Plain and ordinary
`meaning
`
`Defendant
`Intrinsic and
`Extrinsic Support
`’816 Patent at
`20:28; 25:12-17;
`46:42-51.
`
`’816 Patent – Term 3
`
`Claim Term
`
`Claims
`
`1, 10, 17, 26, 27
`
`wherein the
`characteristics
`indicate that the
`numerical values of
`the first markup
`document differ in
`format from the
`numerical values of
`the second markup
`document
`
`
`
`
`’816 Patent – Term 4
`
`e-Numerate
`Construction
`
`One or more
`attributes for the
`numerical values in
`the first markup
`document are
`different from one
`or more attributes
`for the numerical
`values in the second
`markup document
`
`Claim Term
`
`Claims
`
`1, 10, 17, 26 and
`27
`
`automatically
`transforming/transforms
`the numerical values of
`at least one of the first
`markup document and
`the second markup
`document, so that the
`numerical values of the
`
`
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘816 Patent at
`Abstract; col. 4,
`lines 14 – 28; col.
`8, lines 28 – 43;
`col. 26, lines 5 –
`30;
`
`e-Numerate
`Construction
`
`Automatically
`converting/converts
`at least a portion of
`the first or second
`numerical values and
`one or more
`attributes for the
`numerical values in
`
`9
`
`Defendant
`Construction
`
`Plain and ordinary
`meaning.
`
`Defendant
`Intrinsic and
`Extrinsic Support
`’816 Patent:
`Claims 1, 10, 17,
`26 and 27.
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 14 of 109
`
`first markup document
`and the second markup
`document have a
`common format
`
`
`
`
`’816 Patent – Term 5
`
`Claim Term
`
`Claims
`
`the markup
`language
`
`12
`
`
`
`
`
`the first or second
`markup document to
`create new numerical
`values and common
`attributes for the
`numerical values
`
`Defendant
`Construction
`
`Indefinite
`
`e-Numerate
`Construction
`
`Not indefinite.
`Antecedent basis is
`implied, inter alia,
`by the use of the
`term “markup
`document” in claim
`10.
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`Intrinsic Support
`
`‘816 Patent at
`Language of the
`involved claims;
`Abstract; col. 1,
`lines 39 – 43; col.
`3, line 65 – col. 4,
`line 6; col. 8, lines
`15 – 55.
`
`Extrinsic Support
`
`Smith Dec. pars.
`40 – 47;
`
`Defendant Intrinsic
`and Extrinsic
`Support
`Intrinsic Support
`
`’816 Patent:
`Claims 10, 12; 2:1-
`8; 3:65-4:6; 8:44-
`46; 20:33-37.
`
`Extrinsic Support
`
`Martin Decl. at ¶¶
`47-52.
`
`10
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 15 of 109
`
`’816 Patent – Term 64
`
`Claim Term
`
`Claims
`
`26
`
`means for receiving
`a first markup
`document and a
`second
`markup document,
`both the first markup
`document and
`the second markup
`document containing
`numerical values
`and tags reflecting
`characteristics of the
`numerical
`values wherein the
`characteristics
`indicate that the
`numerical values of
`the first markup
`document differ in
`format from the
`numerical values of
`the second markup
`document
`
`
`Defendant
`Intrinsic and
`Extrinsic Support
`See construction
`column for
`support.
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`See construction
`column for
`support;
`
`e-Numerate
`Construction
`
`To be construed
`under § 112 par. 6.
`
`Function: receiving
`a first markup
`document and a
`second markup
`document.
`
`Structure: Reader
`See, e.g., Fig. 7A
`box 704, Fig. 8, step
`802, col. 8, line 4;
`col. 19, lines 30 –
`48; col. 29, lines 35
`– 65; col. 30, lines
`37 – 45.
`
`Defendant
`Construction
`
`In the interest of
`narrowing the issues
`before the Court,
`Defendant does not
`contest e-
`Numerate’s
`identification of
`function and
`structure for this
`term.
`
`Function: receiving
`a first markup
`document and a
`second markup
`document.
`
`Structure: Reader
`See, e.g., Fig. 7A
`box 704, Fig. 8, step
`802, col. 8, line 4;
`col. 19, lines 30 –
`48; col. 29, lines 35
`– 65; col. 30, lines
`37 – 45.
`
`
`4 This term is no longer in dispute.
`
`
`
`11
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 16 of 109
`
`’816 Patent – Term 7
`
`Claim Term
`
`Claims
`
`26
`
`means for
`automatically
`transforming the
`numerical values
`of at least one of the
`first markup
`document and the
`second markup
`document, so that
`the numerical values
`of the first markup
`document and the
`second markup
`document have a
`common format
`
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`See construction
`column for
`support;5
`
`e-Numerate
`Construction
`
`To be construed
`under § 112 par. 6.
`
`Function:
`automatically
`transforming the
`numerical values
`of at least one of the
`first markup
`document and the
`second markup
`document.
`
`Structure: X-value
`transformer
`employing
`conversion factors.
`Fig. 7A block 710;
`Figure 8 block 808;
`Figure 10, blocks
`1012 and 1014;
`Figure 11; col. 19,
`line 49 – col. 20,
`line 3; col. 23, lines
`
`Defendant
`Intrinsic and
`Extrinsic Support
`Intrinsic Support
`
`’816 Patent: Claim
`26; Fig. 7A; 7:1-2;
`25:36-45; 25:63-
`64; 26:7-11;
`26:31-67; 27:1-45;
`31:31-55; 31:56-
`60; 32:21-29.
`
`Extrinsic Support
`
`Martin Decl. at ¶¶
`68, 69, 72, 74-76,
`78,82.
`
`Defendant
`Construction
`
`To be construed
`under § 112 ¶6
`
`Function:
`Automatically
`transforming the
`numerical values of
`at least one of the
`first markup
`document and the
`second markup
`document, so that
`the numerical values
`of the first markup
`document and the
`second markup
`document have a
`common format.
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`
`5 e-Numerate contends that the Government’s use of the Martin Declaration to opine on the construction of the “means-plus-function”
`terms in the ‘816 and ‘383 patents is inappropriate as is the Government’s reliance on the Martin Declaration to assert that the claims
`are indefinite for alleged failure to disclose an algorithm. e-Numerate refers the Court to its briefing on this issue.
`12
`
`
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 17 of 109
`
`
`
`’816 Patent – Term 8
`
`Claim Term
`
`Claims
`
`26
`
`means for
`combining the first
`markup document
`and the
`second markup
`document into a
`single data
`
`
`47 – 59; col. 30, line
`46 - col. 33, line 33;
`col. 25, line 45 –
`col. 27, line 45.
`
`
`
`e-Numerate
`Construction
`
`To be construed
`under § 112 par. 6.
`
`Function:
`combining the first
`markup document
`and the second
`markup document.
`
`Structure: primary
`data store; Fig. 7,
`Box 712; Figure 8,
`line 810; Fig; 11;
`Figure 13; col. 19,
`line 66 – col. 20,
`line 3; col. 31, lines
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`See construction
`column for
`support;
`
`Defendant
`Construction
`
`To be construed
`under § 112 ¶6
`
`Function:
`combining the first
`markup document
`and the second
`markup document
`into a single data.6
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`Defendant
`Intrinsic and
`Extrinsic Support
`Intrinsic Support
`
`’816 Patent: Claim
`26; 33:26-33;
`33:39-41; Table 2
`at col. 34.
`
`
`Extrinsic Support
`
`Martin Decl. at ¶¶
`87-93.
`
`
`6 As noted in Defendant’s prior briefing, “Defendant had previously mistakenly stated that the function was indefinite. However, it previously disclosed this
`function in its expert declaration.” ECF 83 at 18, n. 5 (citations omitted).
`
`
`
`13
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 18 of 109
`
`
`
`’816 Patent – Term 97
`
`Claim Term
`
`Claims
`
`means for
`displaying the
`single data set
`
`26
`
`4 – 30; col. 33, lines
`9 – 59; col. 35, line
`50 – col. 36, line 40.
`
`e-Numerate
`Construction
`
`To be construed
`under § 112 par. 6.
`
`Function:
`displaying the single
`data set
`
`Structure: graphical
`user interface.
`Fig. 7A block 734;
`Figures 15 A, B &
`C; Fig. 19 B; col.
`35, line 50 – 63; col.
`36, line 66 – col. 37,
`line 45; col. 48,
`lines 41 – 49; col.
`53, lines 44 – 53.
`
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`See construction
`column for
`support;
`
`Defendant
`Intrinsic and
`Extrinsic Support
`See construction
`column for
`support.
`
`Defendant
`Construction
`
`In the interest of
`narrowing the issues
`before the Court,
`Defendant does not
`contest e-
`Numerate’s
`identification of
`function and
`structure for this
`term.
`
`To be construed
`under § 112 par. 6.
`
`Function:
`displaying the single
`data set
`
`Structure: graphical
`user interface.
`
`
`7 This term is no longer in dispute.
`
`
`
`14
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 19 of 109
`
`Fig. 7A block 734;
`Figures 15 A, B &
`C; Fig. 19 B; col.
`35, line 50 – 63; col.
`36, line 66 – col. 37,
`line 45; col. 48,
`lines 41 – 49; col.
`53, lines 44 – 53.
`
`
`Defendant
`Construction
`
`Plain and ordinary
`meaning
`
`Defendant
`Intrinsic and
`Extrinsic Support
`’816 Patent at
`Abstract, 4:31-33;
`8:41-43; 10:7-10;
`24:40-50.
`
`
`
`’816 Patent – Term 10
`
`Claim Term
`
`Claims
`
`characteristic of the
`numerical value
`
`27
`
`
`
`
`
`e-Numerate
`Construction
`
`An attribute that
`explains the
`meaning of the
`numerical value
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘816 Patent at
`Language of the
`claims; Abstract,
`col. 4, lines 29 –
`33; col. 8, lines 41
`– 43; col. 16, lines
`55 – 67; col. 20,
`lines 10 – 57.
`
`Appendix B of
`‘383, ‘384, ’748
`and ‘337 patents
`via incorporation
`by reference;
`
`15
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 20 of 109
`
`C. ’383 Patent
`
`’383 Patent – Term 1
`
`Claim Term
`
`Claims
`
`1, 17, 18
`
`first tags reflecting
`characteristics of the
`first numerical
`values
`
`
`e-Numerate
`Construction
`
`Markup language
`tags wherein the
`markup language
`tags for the one or
`more numerical
`values have more
`than one attribute
`that explains the
`meaning of the
`numerical values
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘383 Patent at Col.
`2, lines 20 – 23;
`col. 2, lines 54 –
`56; Col. 3, lines 49
`- 51; Col. 6, lines
`46 – 48; col. 15,
`line 59 – col. 16,
`line 7 & Figure 4;
`col. 18, line 42 –
`col. 19, line 18;
`col. 19, lines 25 –
`35; col. 23, lines
`21 – 60; Figure 10,
`steps 1010 and
`1012; Figure 21
`steps 2106 and
`2018; Appendix A
`and Appendix B
`
`‘816 Patent at
`Abstract, col. 4,
`lines 29 – 33; col.
`8, lines 41 – 43;
`col. 16, lines 55 –
`67; col. 17, line 54
`
`Defendant
`Construction
`
`Plain and ordinary
`(incorporating
`Defendant’s
`construction of
`“tag”/”tags”).
`Defendant maintains
`that ”tag” should be
`construed as
`“markup language
`tag” and “tags”
`should be construed
`as “markup
`language tags.”
`Further, a markup
`language is “a
`language that uses
`tags to define
`elements within a
`document.
`Examples of markup
`languages include
`HTML, XML and
`XBRL.” To the
`extent the Court
`construes the entire
`
`Defendant
`Intrinsic and
`Extrinsic Support
`’383 Patent at
`Abstract, 3:49:51,
`6:46-48, 7:13-14,
`13:47-50,
`15:61:64, 18:48-
`19:13, 19:51-52,
`23:9-20, 23:62-65.
`
`’355 Patent at
`Abstract, 1:65-66,
`2:1-2, 4:28-30,
`8:38-40, 9:5-6,
`15:43-46, 17:57-
`60, 20:23-59,
`21:31-33, 24:50-
`60, 25:34-37.
`
`
`’816 Patent at
`Abstract; 2:1-4,
`4:31-33; 8:42-43,
`9:8-9, 15:43-46;
`21:22-25; 20:24-
`57; 17:56-59;
`
`
`
`16
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 21 of 109
`
`24:40-50, 25:30-
`33; 25:25-28.
`
`term, Defendant
`proposes “Markup
`language tags
`wherein the markup
`language tags for the
`one or more
`numerical values
`have one or more
`attributes that
`describe the
`meaning of the
`numerical values.”
`
`– col. 18, line 2;
`col. 20, lines 10 –
`57; claim 27
`(“characteristic”).
`
`Appendix B of
`‘383, ‘384, ’748
`and ‘337 patents
`via incorporation
`by reference;
`
`‘355 Patent at
`Abstract; Col. 4,
`lines 28 - 30; Col.
`8, lines 38 - 40;
`Figure 10, steps
`1010 and 1012;
`Figure 21 steps
`2106 and 2018;
`Col. 7, lines 7 –
`11; col. 7, lines
`42-44; Col. 16,
`lines 55 – 57;
`Figure 4 and Col.
`17, line 55 – col.
`18, line 3; col. 18,
`lines 22 – 25; col.
`18, lines 50 – 60;
`col. 19, lines 12 –
`14; col. 19, line 57
`– col. 20, line 1;
`col. 20, lines 11 –
`64; col. 24, lines
`
`
`
`17
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 22 of 109
`
`
`
`’383 Patent – Term 2
`
`Claim Term
`
`Claims
`
`1, 17, 18
`
`second tags
`reflecting
`characteristics of the
`second numerical
`values
`
`
`50 – 60; col. 25,
`lines 34 – 37;
`
`
`e-Numerate
`Construction
`
`Markup language
`tags wherein the
`markup language
`tags for the one or
`more numerical
`values have more
`than one attribute
`that explains the
`meaning of the
`numerical values
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘383 Patent at Col.
`2, lines 20 – 23;
`col. 2, lines 54 –
`56; Col. 3, lines 49
`- 51; Col. 6, lines
`46 – 48; col. 15,
`line 59 – col. 16,
`line 7 & Figure 4;
`col. 18, line 42 –
`col. 19, line 18;
`col. 19, lines 25 –
`35; col. 23, lines
`21 – 60; Figure 10,
`steps 1010 and
`1012; Figure 21
`steps 2106 and
`2018; Appendix A
`and Appendix B
`
`‘816 Patent at
`Abstract, col. 4,
`lines 29 – 33; col.
`
`Defendant
`Construction
`
`Plain and ordinary
`(incorporating
`Defendant’s
`construction of “tag”
`and “tags”)
`Defendant maintains
`that “tag” should be
`construed as
`“markup language
`tag” and “tags” as
`“markup language
`tags.” Further, a
`markup language is
`“a language that
`uses tags to define
`elements within a
`document.
`Examples of markup
`languages include
`HTML, XML and
`XBRL.” To the
`extent the Court
`
`Defendant
`Intrinsic and
`Extrinsic Support
`’383 Patent at
`Abstract, 3:49:51,
`6:46-48, 7:13-14,
`13:47-50,
`15:61:64, 18:48-
`19:13, 19:51-52,
`23:9-20, 23:62-65.
`
`’355 Patent at
`Abstract, 1:65-66,
`2:1-2, 4:28-30,
`8:38-40, 9:5-6,
`15:43-46, 17:57-
`60, 20:23-59,
`21:31-33, 24:50-
`60, 25:34-37.
`
`’816 Patent at
`Abstract; 2:1-4,
`4:31-33; 8:42-43,
`9:8-9, 15:43-46;
`21:22-25; 20:24-
`
`
`
`18
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 23 of 109
`
`57; 17:56-59;
`24:40-50, 25:30-
`33; 25:25-28.
`
`construes the entire
`term, Defendant
`proposes “Markup
`language tags
`wherein the markup
`language tags for the
`one or more
`numerical values
`have one or more
`attributes that
`describe the
`meaning of the
`numerical values.”
`
`8, lines 41 – 43;
`col. 16, lines 55 –
`67; col. 17, line 54
`– col. 18, line 2;
`col. 20, lines 10 –
`57; claim 27
`(“characteristic”).
`
`Appendix B of
`‘383, ‘384, ’748
`and ‘337 patents
`via incorporation
`by reference;
`
`‘355 Patent at
`Abstract; Col. 4,
`lines 28 - 30; Col.
`8, lines 38 - 40;
`Figure 10, steps
`1010 and 1012;
`Figure 21 steps
`2106 and 2018;
`Col. 7, lines 7 –
`11; col. 7, lines
`42-44; Col. 16,
`lines 55 – 57;
`Figure 4 and Col.
`17, line 55 – col.
`18, line 3; col. 18,
`lines 22 – 25; col.
`18, lines 50 – 60;
`col. 19, lines 12 –
`14; col. 19, line 57
`
`
`
`19
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 24 of 109
`
`
`
`’383 Patent – Term 3
`
`Claim Term
`
`Claims
`
`tag/tags
`
`1, 4, 17
`
`– col. 20, line 1;
`col. 20, lines 11 –
`64; col. 24, lines
`50 – 60; col. 25,
`lines 34 – 37;
`
`e-Numerate
`Construction
`
`“Tag” should not be
`construed as a stand-
`alone term because
`e-Numerate has
`identified a phrase
`for construction. In
`addition, the claim
`language uses the
`term “tags” in the
`plural. To the extent
`“tags” is construed,
`e-Numerate
`contends the term
`“tags” should be
`construed as
`“Markup language
`tags”.
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`See citations from
`‘355 and ‘816
`patents which are
`incorporated by
`reference into the
`‘383 patent.
`
`‘355 Patent, Col.
`1, lines 32 – 36;
`
`‘816 Patent, Col.
`1, lines 37 – 41;
`
`
`Defendant
`Construction
`
`“Tag” should be
`construed as
`“markup language
`tag and “tags” as
`“markup language
`tags.” Further, a
`markup language is
`“a language that
`uses tags to define
`elements within a
`document.
`Examples of markup
`languages include
`HTML, XML and
`XBRL.”
`
`Defendant Intrinsic
`and Extrinsic
`Support
`’383 Patent at
`Abstract, 3:49:51,
`6:46-48, 7:13-14,
`13:47-50,
`15:61:64, 18:48-
`19:13, 19:51-52,
`23:9-20, 23:62-65.
`
`’355 Patent at
`Abstract, 1:65-66,
`2:1-2, 4:28-30,
`8:38-40, 9:5-6,
`15:43-46, 17:57-
`60, 20:23-59,
`21:31-33, 24:50-
`60, 25:34-37.
`
`’816 Patent at
`Abstract; 2:1-4,
`4:31-33; 8:42-43,
`
`
`
`20
`
`
`
`Case 1:19-cv-00859-RTH Document 95 Filed 08/18/22 Page 25 of 109
`
`
`
`’383 Patent – Term 4
`
`Claim Term
`
`Claims
`
`1, 17, 18
`
`wherein the first tags
`and the second tags
`each include
`computer-readable
`semantic tags that
`describe a semantic
`meaning of a
`corresponding one
`of at least one of the
`first numerical
`values or the second
`numerical values
`
`9:8-9, 15:43-46;
`21:22-25; 20:24-
`57; 17:56-59;
`24:40-50, 25:30-
`33; 25:25-28.
`
`e-Numerate
`Construction
`
`Markup language
`tags wherein the
`markup language
`tags for the one or
`more numerical
`values have more
`than one attribute
`that explains the
`meaning of the
`numerical values
`
`e-Numerate
`Intrinsic and
`Extrinsic Support
`‘383 Patent at Col.
`2, lines 20 – 23;
`col. 2, lines 54 –
`56; Col. 3, lines 49
`- 51; C
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
