throbber
Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 1 of 8 PageID #: 6724
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`
`Case No. 2:15-CV-1274-JRG-RSP
`
`(LEAD CASE)
`
`JURY TRIAL DEMANDED
`
`
`
`BLITZSAFE TEXAS, LLC,
`
`
`Plaintiff,
`
`
`
`v.
`
`
`HONDA MOTOR CO., LTD., ET AL.,
`
`
`
`
`
`
` Defendants.
`











`
`
`
`
`PLAINTIFF BLITZSAFE TEXAS LLC’S RESPONSE IN OPPOSITION TO
`DEFENDANTS VOLKSWAGEN GROUP OF AMERICA, INC. AND VOLKSWAGEN
`GROUP OF AMERICA CHATTANOOGA OPERATONS, LLC’S OBJECTIONS TO
`THE COURT’S CLAIM CONSTRUCTION OPINION AND ORDER (D.E. 146)
`
`
`
`
`

`

`Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 2 of 8 PageID #: 6725
`
`
`
`Pursuant to Local Rule CV-72(b), Plaintiff, Blitzsafe Texas LLC (“Blitzsafe”), submits
`
`this Response in Opposition to Defendants Volkswagen Group of America, Inc. and Volkswagen
`
`Group of America Chattanooga Operations, LLC’s Objections to the Court’s Claim Construction
`
`Opinion and Order (D.E. 146). Blitzsafe requests that each of the objections lodged against the
`
`Court’s constructions of the disputed claim terms in this case be denied.
`
`I.
`
`ARGUMENT
`
`Term 1:
`
`“Interface” Need Not Be Physically Separate from the Car Stereo
`
`The Court adopted the Defendants’ proposed construction of “interface” that it must be
`
`“a structurally and functionally separate component from the car stereo.” Defendants now argue
`
`that the Court’s decision not to read an additional limitation into the construction of interface,
`
`physical separation, was in error.
`
`Defendants did not seek a construction of “interface” that requires physical separation.
`
`Defendants’ argument that structural separation requires physical separation and external
`
`placement of the interface is unsupported by any evidence and contradicts the position of the
`
`New Jersey court on which Defendants relied so heavily during the Markman process. (Dkt.
`
`101.4 at 10 (rejecting physical separation between the interface and car stereo).)
`
`Contrary to Defendants’ assertions, Blitzsafe did not take a position on the construction
`
`of “interface” in the IPR, but merely stated that if Toyota contended that a “connector” required
`
`functional and structural separation between two components, that separation should be applied
`
`consistently with respect to both the first connector and the second connector. (Dkt. 133-20 at
`
`16-17.) Blitzsafe never contended that “interface” should be construed to include the limitation
`
`read into the claim by Defendants and the Court, and never argued that an interface must be
`
`“physically separate” from the car radio. Accordingly, the Court did not err in refusing to read
`
`physical separation into the construction of “interface.”
`
`
`
`

`

`Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 3 of 8 PageID #: 6726
`
`
`
`Term 2:
`
`“Integration Subsystem” Is Not a Microprocessor
`
`Defendants’ construction is incorrect because Defendants themselves admit in their brief
`
`that the “integration subsystem” does not consist solely of a microcontroller as their construction
`
`requires. (Dkt. 175 at 2.) Moreover, Defendants provide no argument why an integration
`
`subsystem is limited to the algorithm of Figure 24 when, as the Court noted, the specification
`
`states that the integration subsystem could include a microprocessor programmed in accordance
`
`with the algorithm in Figure 24. (Dkt. 146 at 30.) The Court’s construction is correct.
`
`Term 3:
`
`Audio Generated by the Portable Device Can Be Further Decoded
`
`The Court properly found that Plaintiff never argued in the Toyota IPR that the decoded
`
`data generated by the portable device could not undergo further decoding. (Dkt. 146 at 35.) The
`
`Court correctly concluded that the ’342 Patent merely requires that the portable device decode
`
`files that contain audio data. (Id.) Defendants provide no evidence or argument that requires the
`
`Court to further limit the claims to require that no further decoding of the original audio file may
`
`be performed.
`
`Term 4:
`
`A “Continuously Transmitted” Signal Need Not be “Continuous”
`
`Defendants argue that they object to the construction of “device presence signal” as
`
`“continuously transmitted” because the specification states that the signal is “transmitted
`
`continuously.” (Dkt. 175 at 3.) In other words, Defendants object to the Court’s construction
`
`even though it is consistent with the specification.
`
`The Court drew the proper distinction between a device presence signal that is
`
`“continuously transmitted,” which Defendants concede the specification teaches, and one that is
`
`“continuous,” or constant or uninterrupted, which the specification does not teach. (Dkt. 146 at
`
`40.) Accordingly, the Court’s construction is correct and should be affirmed.
`
`
`
`2
`
`

`

`Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 4 of 8 PageID #: 6727
`
`
`
`Term 7:
`
`A “Portable Device” Must Be Capable of Being Carried by a Person
`
`The Court properly limited the “portable” to devices which can be carried by a person
`
`based on the intrinsic record. (Dkt. 146 at 48.) This is correct because a construction of
`
`“portable” as “capable of being moved about” is improper because it broadens “portable” to
`
`mean anything movable no matter how large or unwieldy, which is inconsistent with the plain
`
`and ordinary meaning of “portable.” (Id.) Far from reading limitations into the claims as
`
`Defendants contend, the Court avoids rendering the claim term a nullity. As such, the Court’s
`
`rejection of “any argument that the scope of the claims may include anything which can be
`
`moved, no matter how large or unwieldy,” (id.), should be affirmed.
`
`Term 8:
`
`The Court Properly Construed “Pre-Programmed” According to Its Plain
`and Ordinary Meaning
`
`The Court properly declined to adopt Defendants’ construction of “pre-programmed,”
`
`which was “programmed prior to its use in the normal course” because the plain and ordinary
`
`meaning of “pre-programmed” is unambiguous and the intrinsic record does not support
`
`inclusion of “in the normal course” in the construction. (Dkt. 146 at 49-50.) Defendants’
`
`argument that O2 Micro Int’l Ltd. v. Beyond Innov’n Tech. Co., 521 F.3d 1351, 1361-62 (Fed.
`
`Cir. 2008), required this Court to construe “pre-programmed” should be rejected because its
`
`plain and ordinary meaning is unambiguous, and the Court’s rejection of the term “in the normal
`
`course” resolved the claim construction dispute. Defendants do not argue that the plain and
`
`ordinary meaning of “pre-programmed” includes “in the normal course.” Therefore, the claim
`
`construction dispute was resolved by the Court, and it is not being left to the jury to choose
`
`between two or more possible plain meanings of “pre-programmed.” Accordingly, the Court’s
`
`decision to give “pre-programmed” its plain and ordinary meaning should be affirmed.
`
`
`
`3
`
`

`

`Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 5 of 8 PageID #: 6728
`
`
`
`Term 9:
`
`The Court Properly Construed “Car Audio/Video System” According to Its
`Plain and Ordinary Meaning
`
`The Court properly declined to adopt Defendants’ construction of “car audio/video
`
`system” because it is inconsistent with the plain and ordinary meaning and the patentee did not
`
`act as its own lexicographer to redefine the term. (Dkt. 146 at 55.) Defendants provide no basis
`
`for their argument that the rejection of their proposed construction does not resolve the parties’
`
`dispute, or that the plain and ordinary meaning of “car audio/video system” is ambiguous.
`
`Accordingly, the Court properly declined to construe “car audio/video system” under O2 Micro,
`
`521 F.3d at 1361-62.
`
`Term 10:
`
`The Court Properly Construed “Format Incompatible With . . .” According
`to Its Plain and Ordinary Meaning
`
`The Court properly declined to adopt either of Defendants’ constructions of “format
`
`incompatible with . . .” because each is inconsistent with the plain and ordinary meaning and the
`
`intrinsic record. (Dkt. 146 at 57-59.) Defendants’ conclusory statement that the Court’s decision
`
`not to construe the term “is not consistent with the ruling in the Order that the term
`
`‘incompatible’ has a specific meaning to a person of skill in the art” is unsupported. The Court
`
`noted that one of ordinary skill in the art would understand that “incompatible” means “not
`
`defined to work with another system or device,” and rejected Defendants’ attempts to deviate
`
`from that meaning by injecting additional limitations to effectively “redraft the claims.” (Dkt.
`
`146 at 58.) Accordingly, the Court properly resolved the claim construction dispute by rejecting
`
`Defendants’ proposed constructions in favor of the unambiguous meaning of the term. See O2
`
`Micro, 521 F.3d at 1361-62.
`
`Term 11:
`
`The Court Properly Construed “Video Information” as “Visual Images”
`
`The parties agreed that “video information” included “visual images”; the sole claim
`
`construction dispute was whether the “visual images” were limited to “moving” images as
`
`
`
`4
`
`

`

`Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 6 of 8 PageID #: 6729
`
`
`
`Defendants contended. (Dkt. 146 at 59.) The Court properly determined that the term “video
`
`information” contains no such limitation. (Id. at 61.)
`
`Defendants argue that the Court’s construction of “video information” is too broad
`
`because it includes “visual images which are not video,” (Dkt. 175 at 5), but even assuming this
`
`is a flaw, Defendants’ construction, “moving visual images,” contains the same flaw. (Dkt. 146
`
`at 59.) Defendants suggest that the Court’s construction is inconsistent with the term’s plain and
`
`ordinary meaning, but they do not argue that their proposed construction is consistent with the
`
`plain and ordinary meaning. In short, Defendants provide no reasoned basis to reject the Court’s
`
`construction and adopt Defendants’ construction.
`
` Term 12:
`
`The Court Properly Construed the “Connector” and “Connectable” Terms
`According to Their Plain and Ordinary Meaning
`
`The Court properly declined to adopt Defendants’ construction of the “connector” and
`
`“connectable” terms because it found that the plain and ordinary meaning of the terms, as
`
`reflected in the intrinsic record, does not require “a connector that is able to be disconnected.”
`
`(Dkt. 146 at 64.) This construction does not leave any claim construction dispute unresolved,
`
`and avoids adopting a construction proposed by Defendants which is circular and confusing
`
`because it attempts to construe a “connector” in terms of itself. Accordingly, the Court was not
`
`required to construe these claim terms under O2 Micro, 521 F.3d at 1361-62, nor did it err in
`
`construing the terms according to their plain and ordinary meaning.
`
`
`
`
`
`
`
`5
`
`

`

`Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 7 of 8 PageID #: 6730
`
`
`
`II.
`
`CONCLUSON
`
`For the foregoing reasons, Defendants’ Objections to the Court’s Claim Construction
`
`Opinion and Order (D.E. 146) should be denied.
`
`Dated: October 17, 2016
`
`
`
`
`
`
`
`
`BROWN RUDNICK LLP
`
`
`
` /s/Peter Lambrianakos
`Alfred R. Fabricant
`Texas Bar No. 2219392
`Email: afabricant@brownrudnick.com
`Lawrence C. Drucker
`Email: ldrucker@brownrudnick.com
`Texas Bar No. 2303089
`Peter Lambrianakos
`Texas Bar No. 2894392
`Email: plambrianakos@brownrudnick.com
`Alessandra Carcaterra Messing
`Texas Bar No. 5040019
`Email: amessing@brownrudnick.com
`BROWN RUDNICK LLP
`7 Times Square
`New York, NY 10036
`Telephone: (212) 209-4800
`
`Samuel F. Baxter
`Texas State Bar No. 01938000
`sbaxter@mckoolsmith.com
`Jennifer L. Truelove
`Texas State Bar No. 24012906
`jtruelove@mckoolsmith.com
`MCKOOL SMITH, P.C.
`104 E. Houston Street, Suite 300
`Marshall, Texas 75670
`Telephone: (903) 923-9000
`Facsimile: (903) 923-9099
`
`ATTORNEYS FOR PLAINTIFF,
`BLITZSAFE TEXAS, LLC
`
`6
`
`
`
`
`
`

`

`Case 2:15-cv-01274-JRG-RSP Document 190 Filed 10/17/16 Page 8 of 8 PageID #: 6731
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that all counsel of record who have consented to electronic
`
`service are being served with a copy of this document via the Court’s CM/ECF system per Local
`
`Rule CV-5(a)(3) on this 17th day of October, 2016.
`
`
`
`
`
`
`
`
`
`
`
`
`
`Peter Lambrianakos
`/s/
` Peter Lambrianakos
`
`
`
`
`
`
`
`
`
`
`
`
`
`

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