throbber
Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 1 of 24 PageID #: 658
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF DELAWARE
`
`
`
`
`
`
`Case No. 17-cv-386-VAC-CJB
`
`
`
`
`
`
`
`
`TECHNO VIEW IP, INC.,
`
`
`
`
`
`OCULUS VR, LLC, and
`
`FACEBOOK, INC.,
`
`
`
`
`Plaintiff,
`
`
`
`v.
`
`
`
`Defendants.
`
`PLAINTIFF’S ANSWERING CLAIM CONSTRUCTION BRIEF
`
`
`
`
`
`
`
`
`
`
`
`
`HARRY JERNIGAN CPA ATTORNEY, P.C.
`Michael K. Botts (Pro Hac Vice)
`5101 Cleveland Street, Suite 200
`Virginia Beach, VA 23462
`mbotts@hjlaw.com
`
`
`
`
`
`Dated: May 18, 2018
`
`
`
`O’KELLY ERNST & JOYCE, LLC
`Sean T. O’Kelly (No. 4349)
`Daniel P. Murray (No. 5785)
`901 N. Market Street, Suite 1000
`Wilmington, DE 19801
`(302) 778-4000
`(302) 295-2873 (facsimile)
`sokelly@oelegal.com
`dmurray@oelegal.com
`
`Attorneys for Plaintiff Techno View IP, Inc.
`
`
`
`
`
`i
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 2 of 24 PageID #: 659
`
`TABLE OF CONTENTS
`
`A. BUFFER RELATED CLAIM TERMS .................................................................................... 1
`
`1. Introduction ............................................................................................................................ 1
`
`2. “Buffer”................................................................................................................................... 1
`
`3. “Backbuffer,” “Left Backbuffer,” and “Right Backbuffer” ................................................... 2
`
`4. “Storing an Image [in a “Buffer” or “Backbuffer”]” and Whether the Claims Require the
`
`Step of “Storing” to Occur Before the Step of “Determining” ................................................... 8
`
`5. “Storing” .............................................................................................................................. 10
`
`6. “Frontbuffer”........................................................................................................................ 12
`
`B. NON-BUFFER RELATED CLAIM TERMS: ....................................................................... 12
`
`1. “Videogame”........................................................................................................................ 12
`
`2. “Coordinates” in Various Coordinate Systems .................................................................... 16
`
`3. “With a Processor” ............................................................................................................... 18
`
`
`
`
`
`
`
`
`
`ii
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 3 of 24 PageID #: 660
`
`Cases
`
`TABLE OF AUTHORITIES
`
`Altiris, Inc. v. Symantec Corp.,
`318 F.3d 1363 (Fed. Cir. 2003)................................................................................................... 8
`
`Epcon Gas Sys., Inc. v. Bauer Compressors, Inc.,
`279 F.3d 1022 (Fed. Cir. 2002)................................................................................................. 19
`
`Graphics Props. Holdings, Inc. v. ASUS Computer Int'l, Inc.,
`No. 12-CV-1394-LPS, 2014 WL 4929340 (D. Del. Sept. 29, 2014)........................................ 15
`
`Greenberg v. Ethicon Endo–Surgery, Inc.,
`91 F.3d 1580 (Fed. Cir. 1996)................................................................................................... 19
`
`Hynix Semiconductor Inc. v. Toshiba Corp.,
`No. C-04-04708 VRW, 2006 WL 2547463 (N.D. Cal. Sept. 1, 2006) ....................................... 9
`
`Innova/Pure Water, Inc. v. Safari Water Filtration Sys., Inc.,
`381 F.3d 1111 (Fed. Cir. 2004) ................................................................................................. 16
`
`Martek Biosciences Corp. v. Nutrinova, Inc.,
`579 F.3d 1363 (Fed. Cir. 2009)................................................................................................. 14
`
`Masco Corp. v. United States,
`303 F.3d 1316 (Fed. Cir. 2002)................................................................................................. 20
`
`O.I. Corp. v. Tekmar Co. Inc.,
`115 F.3d 1576 (Fed. Cir. 1997)........................................................................................... 19, 20
`
`Sage Prods., Inc. v. Devon Indus., Inc.,
`126 F.3d 1420 (Fed. Cir. 1997)................................................................................................. 19
`
`Sinorgchem Co. v. Int’l Trade Comm’n,
`511 F.3d 1132 (Fed. Cir. 2007)................................................................................................. 14
`
`York Prods., Inc. v. Central Tractor Farm & Family Ctr.,
`99 F.3d 1568 (Fed.Cir.1996)..................................................................................................... 19
`
`Statutes
`
`35 U.S.C. § 112 ............................................................................................................................. 19
`
`Other Authorities
`
`
`
`MPEP 2173.05(e) ............................................................................................................................ 9
`
`
`
`
`
`iii
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 4 of 24 PageID #: 661
`
`A. BUFFER RELATED CLAIM TERMS
`
`1. Introduction
`
`Defendants both misunderstand and misrepresent the meaning of the term “buffer” and
`
`
`
`
`related buffer terms. Six of Defendants’ nine proposed constructions concern either a “buffer” or
`
`related sub-types of buffers: 1) “left backbuffer;” 2) “right backbuffer;” 3) “left frontbuffer;” 4)
`
`“right frontbuffer;” 5) “first buffer;” and 6) “second buffer.”
`
`
`
`A “buffer” is a commonly understood term that has no special definition in the Asserted
`
`Patents aside from the commonly understood definition. Plaintiff submits that one of ordinary
`
`skill in the art at the time of the invention would have understood the term “buffer” to mean:
`
`A region of memory reserved for use as an intermediate repository in which data is
`temporarily held while waiting to be transferred between two locations or devices.
`For instance, a buffer is used while transferring data from an application, such as a
`word processor, to an input/output device, such as a printer.1
`
`“Backbuffers” and “frontbuffers” are subsets, or special cases, of the broader temporary
`
`
`
`memory storage location known as “buffers.” The key difference between these terms is that a
`
`“buffer” may store any type of data, whereas the data temporarily stored in “backbuffers” or
`
`“frontbuffers” is limited to “image” data. After the programmer assigns a function for image
`
`storage to a specific block of memory, that portion of memory may be used as “backbuffers” or
`
`“frontbuffers.” The claims of the Asserted Patents only make sense with this distinction.
`
`2. “Buffer”
`(See Defendants’ Initial Claim Construction Brief (“ICCB”), p. 18)
`
`Defendants propose “buffer” to be construed in the ‘096 Patent, Claims 8-11, 13, 14, 16-
`
`
`
`19; and ‘218 Patent, Claims 7, 8, and 11-13, each claiming “First” and “Second” “Buffers.”2
`
`
`1 See Decl. of Michael Botts, Ex. A, Microsoft Computer Dictionary, Fifth Ed., Microsoft Press,
`2002, definition of “buffer.”
`2 See Section H of Defendants’ ICCB.
`
`
`
`1
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 5 of 24 PageID #: 662
`
`
`
`Defendants incorrectly conflate the terms “buffer,” “backbuffer” and “frontbuffer.” The
`
`differences between these terms are expressly illustrated in the claims themselves, as well as in
`
`the Specification. For example, in the ‘096 Patent, independent Claim 8 specifies “first and
`
`second buffers,” and dependent Claim 13 further limits the “buffers” to be “backbuffers,” as
`
`follows: “The method of claim 8, wherein the first and second buffers are backbuffers.”3
`
`
`
`Clearly, the “buffers” of Claim 8 are not “backbuffers” until they are made so in Claim
`
`13. Prior to the limitations of Claim 13, the “buffers” of Claim 8 are fully functional as
`
`independent temporary storage locations for the data specified in the claim – an “image”
`
`temporarily stored in the “first buffer” and the “second camera position view image” temporarily
`
`stored in the “second buffer.”
`
`
`
`The use of “frontbuffers” to store images received from “buffers” is similarly and clearly
`
`specified in dependent Claim 14, which specifically limits independent Claim 8 as follows:
`
`“The method of claim 8, wherein simultaneously displaying the images in the first
`and second buffers comprises storing the images in the first and second buffers
`to first and second frontbuffers, and wherein the images in the first and second
`frontbuffers are simultaneously displayed to the user.”4
`
`Defendants incorrectly limit a “buffer” to being construed as either a Backbuffer or a
`
`
`
`Frontbuffer. Defendants’ construction is contrary to the claims language and should be rejected.
`
`Plaintiff’s construction is consistent with the accepted definition and the use of a “buffer” in the
`
`context of the claims and specification, and is both technically and contextually correct:
`
`
`
`A memory location where data may be temporarily stored.
`
`3. “Backbuffer,” “Left Backbuffer,” and “Right Backbuffer”
`(See Defendants’ ICCB, p. 4)
`
`Defendants propose to construe a “backbuffer” as it is defined in a section of the Patents
`
`
`
`
`3 See ‘096 Patent, Claim 13
`4 See ‘096 Patent, Claim 14 (emphasis added).
`
`
`
`2
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 6 of 24 PageID #: 663
`
`Specification, and the parties originally agreed on the definition, as follows: “A memory location
`
`where the image to be displayed is temporarily ‘drawn’ without outputting it to the video card.”5
`
`It is apparent, however, that while the parties agree on the words they have disagreement on what
`
`the words actually mean. The context in which the term is described is important:
`
`A backbuffer is used, which is a memory location where the image to be
`displayed is temporarily “drawn” without outputting it to the video card. If this is
`done directly on the video memory screen, a flicker on the screen would be
`observed; therefore the information is drawn and processed quickly in the
`backbuffer. This backbuffer is usually located within the physical RAM memory
`of the video or graphics acceleration card.6
`
`First, while this reference for backbuffer specifies a memory location where an image is
`
`drawn “without outputting it to the video card,” the reference itself makes clear that this is not
`
`true in every instance. As the last sentence in the quote clearly states, the backbuffer is “usually
`
`located within the ... memory of the video or graphics acceleration card.” Obviously, an image
`
`cannot be output to something – the video card – when it is already located on the video card.
`
`Also, Defendants do not acknowledge that a “backbuffer” or a “frontbuffer” are areas of
`
`memory allocated from a “buffer.” The Specification clearly states: “Load characters, objects,
`
`textures and sounds into memory. Create a memory location for temporary processing, called
`
`doublebuffer or backbuffer.”7 The load instruction shows that several types of data are stored
`
`in the memory. The create instruction is well known as a command to allocate a portion of
`
`memory for a specific function, such as a doublebuffer or backbuffer.
`
`
`
`In an effort towards agreement between the Parties on the meaning of the Specification’s
`
`definition of “backbuffer,” Plaintiff has offered construction of the term as follows:
`
`A memory location for the temporary storage of an image.
`
`
`5 See ‘096 Patent, col. 6: 40-45, and ‘218 Patent, col. 6: 40-45.
`6 ‘096 Patent, col. 6:40-47.
`7 ‘096 Patent, Col. 6:51-53 (emphasis added).
`
`
`
`3
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 7 of 24 PageID #: 664
`
`
`Plaintiff’s construction is consistent with the Asserted Patents’ use of the term and with
`
`the distinctions between a “backbuffer” (or “frontbuffer”) and a “buffer.” Plaintiff respectfully
`
`submits this construction to the Court.
`
`
`
`Defendants also propose faulty constructions for the terms “left backbuffer” and “right
`
`backbuffer” in the following claims: ‘096 Patent Claims 1, 2, 3, 6, and 7; and ‘218 Patent
`
`Claims 1 and 6.8 Defendants’ proposed construction of both left and right backbuffers is as
`
`follows: “backbuffers that are separate from each other such that left and right independent
`
`images could be generated and stored therein.”
`
`
`
`This construction is flawed for several reasons. First, it introduces the limitation that
`
`independent images could both be “generated” and stored in the same location. There is no basis
`
`for the limitation of the images being “generated” in the backbuffers. Indeed, there is no context
`
`whatsoever in the Specification for using the term “generated” in such a construction. The terms
`
`“generated” and “generating” do appear in the ‘096 and ‘218 Patent Specifications, but nowhere
`
`with regard to images being created in the backbuffers. Moreover, Defendants’ construction is
`
`not a definition at all, but rather a description of a particular characteristic of some as yet
`
`unknown definition.
`
`Claim 6, for example, of the ‘096 Patent specifies a limitation of the element,
`
`“simultaneously displaying”, of independent Claim 1, wherein the images in the left and right
`
`backbuffers “comprises generating left and right images on different video channels.”9 In Claim
`
`6, the images already exist and are being temporarily stored in the left and right backbuffers to be
`
`
`8 See Section B of Defendants’ ICCB.
`9 See ‘096 Patent, Claim 6, quoted in full: “The method according to claim 1, wherein
`simultaneously displaying the images in the left and right backbuffers comprises generating left
`and right images on different video channels.”
`
`
`
`4
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 8 of 24 PageID #: 665
`
`later simultaneously displayed by “generating” or sending them to the display via “different
`
`video channels.” ‘096 Patent Claim 7, which depends from Claim 6, similarly does not claim
`
`“generating images”, but rather increasing the backbuffer memory prior to “generating the left
`
`and right images on different video channels.”10 Defendants alternatively propose separate
`
`constructions for “left” and “right” “backbuffers” that eliminate the “generating” limitation,11 but
`
`retain the flaw of the “separate” limitation, discussed below.
`
`
`
`A second flaw in Defendants’ proposed construction is that the backbuffers “are separate
`
`from each other.” This limitation on the claim element is vague and ambiguous. It is vague
`
`because it relies and acts upon an unknown definition of what a backbuffer actually is. The
`
`phrase “separate from each other” does not appear as a claim limitation, and it is not mentioned
`
`in the Specifications of either Asserted Patent.
`
`
`
`Defendants’ proposed construction that backbuffers are “separate from either other” is
`
`also inherently ambiguous limitation. Are the backbuffers in different physical memory
`
`locations on the same memory circuit, or are they totally different circuits? Or do Defendants
`
`mean the backbuffers are merely programmatically separated? We cannot know based on their
`
`construction. A videogame system may be configured with only internal memory or it may have
`
`external memory boards. Also, memory may be allocated temporally wherein the same physical
`
`location has different uses at different cycles of the processor.
`
`It is true that two existent backbuffers, left and right, must inherently be “different” -
`
`unique memory locations - because they are separately identified claim elements. However,
`
`Defendants appear to intend a further limitation by imposing the limitation that the two
`
`
`10 See ‘096 Patent, Claim 6, quoted in full: “The method according to claim 6, further
`comprising increasing the left and right backbuffer memory prior to generating the left and right
`images on different video channels.”
`11 See Defendants’ ICCB, p. 4, fn 3.
`
`
`
`5
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 9 of 24 PageID #: 666
`
`backbuffers be physically “separate from each other,” which is supported neither by the
`
`Prosecution History nor Defendants’ arguments. The word “separate” implies the buffers must
`
`be physically or geographically separated. This is simply incorrect, as the backbuffers can
`
`inhabit the same physical locations but be separated only in time for a particular programming
`
`cycle. Defendants are confusing the concept of “different” backbuffers with a previously
`
`undisclosed additional limitation that they are “separate,” and in a manner that is undefined.
`
`
`
`In support of their “separate” limitation, Defendants cite to, but misrepresent, the
`
`prosecution history of the ‘096 Patent. Defendants recite an interview summary in which the
`
`Examiner notes the Applicant’s argument that a cited reference, Engstrom, failed to teach two
`
`backbuffers because, although it had two backbuffers, they were connected and therefore not
`
`able to contain two independent images as specified in the application.12 Defendants erroneously
`
`conclude from this terse summary by the Examiner: “the separateness of the backbuffers was a
`
`critical basis for the applicant’s attempt to distinguish Engstrom.”13 This is wrong.
`
`In its entirety, the interview summary shows the normal back-and-forth discussions
`
`between Applicant’s attorney and Examiner:
`
`Applicants argued that the two back buffers disclosed in Engstrom were connected and
`not separate therefrom such that to left and right independent images could be generated
`and stored therein. Examiner argued that even though the backbuffers of Engstrom were
`connected in that data could be transferred therebetween, the buffers were still
`independent buffers. Applicants described the invention as providing images in the left
`backbuffer only for 2-D views and providing left images in the left backbuffer for left eye
`3-D views and right images in the right backbuffer for right eye 3-D views . . . .14
`
`The Examiner believed that two connected backbuffers that could transfer data between
`
`each location should be considered independent buffers.
`
`
`12 See Defendants’ ICCB, p. 4, quoting the Examiner’s Interview Summary, dated Sept. 18,
`2009.
`13 See Defendants’ ICCB, p. 5.
`14 See Defendants’ ICCB, Exhibit 3.
`
`
`
`6
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 10 of 24 PageID #: 667
`
`Defendants further impugn Plaintiff by baselessly asserting: “In an attempt to improperly
`
`expand the scope of the claim terms, Plaintiff seeks to run away from those narrowing
`
`statements.”15 Defendants accuse Plaintiff of wrongdoing by “improperly expand[ing] the scope
`
`of the claim terms.” However, during prosecution, the Applicant distinguished the Engstrom
`
`reference because it did not have two buffers capable of storing independent images.16 All of the
`
`backbuffer-related three-dimensional image claims require left and right backbuffers temporarily
`
`storing different images. Defendants’ accusations of wrongdoing against Plaintiff are
`
`unfounded. Now, as always, Plaintiff maintains that the backbuffers required a “left backbuffer”
`
`and a “right backbuffer” to temporarily store images to be eventually displayed to a user.
`
`
`
`Defendants also misrepresent the prosecution history record by failing to tell the Court
`
`that in the Reasons for Allowance, the Examiner agreed with the Applicant’s argument, stating
`
`that Engstrom, in combination with other prior art references, failed to teach or make obvious a
`
`method whereby it is determined that an image is in two-dimensions or three-dimensions, and
`
`when in three-dimensions, different images are stored on different backbuffers.17
`
`
`
`Defendants’ proposed claim construction baselessly specifies that images be “generated”
`
`in the “left backbuffer” and the “right backbuffer,” and needlessly adds an ambiguous limitation
`
`
`15 See Defendants’ ICCB, p. 4.
`16 See Defendants’ ICCB, Exhibit 3: “Applicants argued that the two back buffers disclosed in
`Engstrom were connected and not separate therefrom such that to [sic] left and right independent
`images could be generated and stored therein.”
`17 See Declaration of Michael Botts, Exhibit B, Examiner’s Interview Summary (October 29,
`2009), Allowance, and Reasons for Allowance, p. 2, recorded November 18, 2009, stating in
`relevant part: “The closest prior art for the features of the claimed invention are Alamparambil
`... Engstrom ... Naske ... and Bar-Nahum.... However [the combined prior art references] does
`not disclose an apparatus and a method of operating the apparatus that determines when an
`image is in two-dimensional or three-dimensional format, an image stored in a left backbuffer is
`is [sic] displayed onto at least one display, and when the image is in three-dimensional format,
`coordinates of an image in a second view position is calculated and the image is stored in a right
`backbuffer so as to simultaneously display the images of the left and right backbuffers onto a
`least on display creating a three-dimensional perspective of the image to a user.”
`7
`
`
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 11 of 24 PageID #: 668
`
`that they be “separate” from each other. This Court should deny the proposed construction.
`
`
`
`Plaintiff’s constructions below are consistent with the fact that backbuffers are buffers
`
`that store images, and that left and right backbuffers temporarily store left and right images:
`
`Left backbuffer: a memory location where the left image to be displayed is temporarily stored.
`Right backbuffer: a memory location where the right image to be displayed is temporarily stored.
`
`4. “Storing an Image [in a “Buffer” or “Backbuffer”]” and Whether the Claims Require
`the Step of “Storing” to Occur Before the Step of “Determining”
`(See Defendants’ ICCB, p. 6-11)
`
`Defendants propose the term “storing an image” to be construed in the following claims:
`
`
`
`‘096 Patent, independent Claims 1, 8, and 16; and, ‘218 Patent, independent Claims 1, 7, and 12.
`
`Defendants seek to have this Court construe that the claim step of “determining” whether an
`
`image is in 2D or 3D format must occur temporally after the step of “storing the image.” For the
`
`reasons stated below, Plaintiff maintains that the “determining step” is not required to follow the
`
`claim elements preceding it. In relevant part, ‘096 Claim 1 specifies:
`
`[a] clearing left and right backbuffers in the videogame system;
`[b] storing an image into the left backbuffer;
`[c] determining if the image is in a two-dimensional format or a three-dimensional
`format, wherein when the image is in a three-dimensional format,
`calculating the coordinates of a second view position of the image and
`storing a second view position image into the right backbuffer;
`[d] displaying the image stored in the left backbuffer onto one or more displays when
`the image is in a two-dimensional format; and simultaneously displaying the images
`stored in the left and right backbuffers onto the one or more displays to create a three
`dimensional perspective of the image to a user when the image is in a three-dimensional
`format.18
`
`Defendants recite portions of the test set out in Altiris, noting that “the first step is to
`
`
`
`‘determine if, as a matter of logic or grammar, they must be performed in the order written.’”19
`
`
`18 ‘096 Patent, Claim 1 (emphasis added).
`19 Dkt. 53, p. 6 (citing Altiris, Inc. v. Symantec Corp., 318 F.3d 1363, 1369 (Fed. Cir. 2003)).
`8
`
`
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 12 of 24 PageID #: 669
`
`Defendants then state that “there is no need to proceed beyond the first step.”20 However,
`
`Defendants are relying solely on the antecedent basis language without considering the entirety
`
`of the claim.
`
`First, the cases cited to by the Defendants all have other language that clearly limits the
`
`order. For example, in Hynix, the steps at issue clearly spelled out the forming of a polysilicon
`
`film, and then depositing something onto that polysilicon film: “step b: ‘annealing said silicon
`
`film to form a polysilicon film …;’ step c: ‘depositing a … film on said polysilicon film …’”21
`
`There, the antecedent basis clearly limited the order. That is not the case with the present
`
`“storing” and “determining” steps. While the “determining” step does refer to “the image,”
`
`and the “storing” step does refer to “an image,” this is merely done to satisfy the antecedent basis
`
`requirements when an element is referred to in a later claim limitation. Because one claim
`
`limitation had to be written first, and the other written second, one of them must use the “an
`
`image” language, while the other uses of “the image.”22
`
`When the patentee wished to specify a particular order, the patentee used language that
`
`clearly indicated such was required. For example, the claim limitation - [d] - immediately
`
`following the “determining” step reads, in part, “displaying the image stored in the left
`
`backbuffer …” (emphasis added). This was deliberate. Much like in Hynix, the displaying step
`
`clearly must follow the storing step, as evidenced by the antecedent basis and the other language
`
`describing the “image.” By contrast, the determining – [c] -step does not indicate whether the
`
`image being determined was the one stored in the left backbuffer.
`
`Defendants further point to Figure 4b in the Specification to demonstrate their contention
`
`
`20 Dkt. 53, p. 7.
`21 Hynix Semiconductor Inc. v. Toshiba Corp., No. C-04-04708 VRW, 2006 WL 2547463, at *6
`(N.D. Cal. Sept. 1, 2006) (emphasis added).
`22 See MPEP 2173.05(e).
`
`
`
`9
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 13 of 24 PageID #: 670
`
`that the claim elements must be followed in order; however, and as Defendants themselves aver,
`
`this flowchart describes merely “an embodiment of the alleged invention.”23
`
`
`
`Since Defendants have failed to meet their burden of proof, Plaintiff’s construction
`
`should be adopted, as follows:
`
`The steps do not have to be performed in the order recited.
`
`5. “Storing”
`(See Defendants’ ICCB, p. 10)
`
`Defendants consider the perceived issue as follows: “Here, the primary disputes between
`
`
`
`the parties are (1) whether the term ‘storing’ requires construction and (2) whether the term ‘the’
`
`must appear before the term ‘[back]buffer’ as set forth in the patent.”24 Defendants’ propose the
`
`following construction for “Storing”: “temporarily “drawing” an image into the
`
`[back]buffer.”25 Defendants’ construction contains an undefined term, in quotation marks,
`
`thereby indicating that it has a particular meaning, which Defendants’ fail to specify. Plaintiff
`
`submits that Defendants’ proposed construction should be denied because it is undefined, vague,
`
`and more confusing than the term it claims to construe – “storing” data to a buffer memory
`
`location.
`
`
`
`Defendants also confuse the use of the term “[back]buffer.” In an attempt to remedy this
`
`confusion, Plaintiff offered its alternative constructions in its Opening Claim Construction
`
`Brief,26 and in this Responsive Brief. Defendants’ confusion is caused by conflating “buffers”
`
`with “backbuffers.” The quoted step is more accurately read: “storing an image into the
`
`backbuffer,” because backbuffers only store a special type of data - images.
`
`
`23 See Dkt 53, page 9, line 2.
`24 See Defendants’ ICCB, p. 10.
`25 See Defendants’ICCB, p. 10.
`26 See Plaintiff’s Opening Claim Construction Brief, Doc. 52, pp. 1-2, 4-5, 7-10, and 15-16.
`10
`
`
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 14 of 24 PageID #: 671
`
`
`
`Plaintiff submits that the term “storing,” in context of the claim limitations, is abundantly
`
`clear to one of ordinary skill in the art at the time of the invention. But in the context of the
`
`claims, the “storing” step is always paired with what is to be stored; e.g., an “image,” a “second
`
`view position image,”27 a “videogame image,” a “second camera position view image,”28 a “first
`
`eye view image” and a “second eye view image.”29 Also, in context of the claim limitations, the
`
`“storing” step always identifies where the specified items are to be stored – left and right
`
`backbuffers,30 first and second buffers,31 and first and second frontbuffers.32 Hence, in the
`
`context of the claims, the “storing” step is complete and clearly stated.
`
`
`
`Defendants argue that the action of “storing” data on a memory buffer requires
`
`construction. In Defendants’ Initial Brief, they cite the Microsoft Computer Dictionary as
`
`acceptable extrinsic evidence for the construction of the term “Cartesian coordinates.”33 If
`
`Defendants had also looked up the accepted definition for “buffer storage”, they would have
`
`discovered the definition: “buffer storage n. 1. The use of a special area in memory to hold data
`
`temporarily for processing until a program or operating system is ready to deal with it.”34
`
`Plaintiffs respectfully submit that the term “storage” of data onto a buffer is clearly understood
`
`even by a layperson, and would have also been clearly understood by one of ordinary skill in the
`
`art at the time of the invention, consistent with the 2002 Microsoft Computer Dictionary, and
`
`therefore the term needs no construction.
`
`
`27 See ‘096 Patent, independent Claim 1.
`28 See ‘096 Patent, independent Claims 8, 15, and 16.
`29 See ‘218 Patent, independent Claims 1, 7, and 16.
`30 See ‘096 Patent, independent Claim 1; and ‘218 Patent, independent Claims 1
`31 See ‘096 Patent, independent Claims 8, 15, and 16; and ‘218 Patent, independent Claims, 7
`and 8.
`32 See ‘096 Patent, Claim 14.
`33 See Defendants’ ICCB, p. 12, referencing Exhibit 5 thereto.
`34 See Declaration of Michael Botts, Exhibit A, Microsoft Computer Dictionary, Fifth Ed., 2002,
`“buffer storage.”
`
`
`
`11
`
`

`

`Case 1:17-cv-00386-VAC-CJB Document 59 Filed 05/18/18 Page 15 of 24 PageID #: 672
`
`
`
`If a “storing” construction is deemed necessary, this Court should adopt Plaintiff’s
`
`construction, which identifies the contextual elements of “storing” data in the context of the
`
`claims – what is stored (claimed data or an image), where it is stored (i.e., a memory location
`
`identified in the claims as either a buffer or a backbuffer), and how long it is stored
`
`(temporarily). Plaintiff’s construction accounts for these variables as follows:
`
`Temporarily moving data or an image into a memory location.
`
`6. “Frontbuffer”
`(See Defendants’ ICCB, p. 13)
`
`Defendants propose that the term “frontbuffer” requires construction in the ‘096 Patent.
`
`
`
`
`
`Claim 14 is instructive, which states as follows:
`
`The method of claim 8, wherein simultaneously displaying the images in the first and
`second buffers comprises storing the images in the first and second buffers to first and
`second frontbuffers, and wherein the images in the first and second frontbuffers are
`simultaneously displayed to the user.35
`
`It should be noted in Claim 14, and in the independent claim from which it depends, the
`
`claims specify a “first buffer” and a “second buffer.” Both the first and second “buffers” then
`
`store images in “first and second frontbuffers.” Defendants’ proposed construction fails to
`
`include the characteristic of a buffer as “temporary” storage, instead proposing: “a memory
`
`location for outputting an image to the display.” At least because Defendants’ proposed
`
`construction is incomplete, it should be denied. Plaintiff’s construction incorporates the
`
`temporary storage characteristic, as follows:
`
`
`
`A memory location where an image to be displayed may be temporarily stored.
`
`B. NON-BUFFER RELATED CLAIM TERMS:
`
`1. “Videogame”
`(See Defendants’ ICCB, p. 2)
`
`
`35 ‘096 Patent, Claim 14.
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

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.

throbber

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.

Become a Member

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

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket