throbber
Paper 7
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`__________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`___________________
`
`UNIFIED PATENTS, INC.,
`Petitioner,
`
`v.
`
`VELOCITY PATENT LLC,
`Patent Owner
`
`___________________
`
`Case IPR2017-01723
`U.S. Patent 5,954,781
`
`_____________________
`
`
`PATENT OWNER VELOCITY PATENT LLC’S PRELIMINARY
`RESPONSE
`
`
`
`
`
`
`
`

`

`TABLE OF CONTENTS
`INTRODUCTION .............................................................................................. 1
`I.
`II. OVERVIEW OF THE ’781 PATENT ............................................................... 3
`A. Driver Notifications ......................................................................................... 4
`B. Control of Driver Notifications ........................................................................ 5
`III. CLAIM CONSTRUCTION ............................................................................... 6
`A. “Said processor subsystem determining, based upon data received
`from said plurality of sensors, when to activate said fuel overinjection
`notification circuit” .......................................................................................... 7
`IV. THE PETITION SHOULD BE DENIED ON ALL GROUNDS UNDER
`37 C.F.R. § 42.104(b)(3) .................................................................................... 9
`V. THE PETITION SHOULD BE DENIED FOR GROUND I .......................... 15
`A. Westbrook does not disclose each limitation of the claimed “memory
`subsystem.” ....................................................................................................15
`1. Westbrook does not disclose storing prior levels for any of the recited
`sensors. ........................................................................................................18
`2. Westbrook does not disclose storing “prior levels” of sensors. ..................20
`3. Westbrook does not disclose any embodiment of a memory subsystem
`storing
`set points, prior levels, and current levels as arranged in the claims. .........23
`4. Petitioner failed to present a motivation to combine disparate
`embodiments of Westbrook. ........................................................................24
`5. Westbrook teaches away from using smart sensors. ...................................26
`B. Ghitea does not disclose “determining, based upon data received
`from said plurality of sensors, when to activate said fuel overinjection
`notification circuit” as required by claims 1, 7, and 13. ................................27
`C. Westbrook does not disclose or render obvious the vehicle proximity
`alarm elements as arranged in claim 17. ........................................................30
`1. Petitioner mischaracterized Westbrook’s disclosure of the reliability
`and use of collision avoidance systems with built-in radar. .......................32
`2. Westbrook teaches away from using built-in radar systems by
`disclosing the “major problem” of false reflections. ..................................33
`
`i
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`3. Westbrook teaches away from using built-in radar systems by
`disclosing alternative embodiments that were better candidates
`for collision avoidance systems. .................................................................35
`VI. THE PETITION SHOULD BE DENIED FOR GROUND II ......................... 37
`A. Petitioner failed to show that Westbrook discloses or renders obvious
`the vehicle proximity alarm elements as arranged in claim 60. ....................37
`B. Petitioner does not demonstrate that each and every limitation of claim
`60 was disclosed or rendered obvious. ..........................................................38
`1. Petitioner did not present an argument for “said processor subsystem
`determining whether to activate said vehicle proximity alarm circuit
`based upon…vehicle speed data received from said road speed sensor.” ..39
`2. Arguments for 17(i) do not demonstrate that Westbrook discloses “said
`processor subsystem determining whether to activate said vehicle
`proximity alarm circuit” as claimed in 60(g). .............................................41
`C. Westbrook does not disclose proximity alarm activation determinations
`based on data from three sources as claimed. ................................................42
`D. Westbrook does not disclose or render obvious the “processor subsystem”
`of 60(g) and 60(l). ..........................................................................................43
`VII. THE PETITION SHOULD BE DENIED FOR GROUND III ........................ 47
`A. Jurgen does not disclose “present and prior levels for each one of said
`plurality of sensors” of limitation 1(d). .........................................................47
`B. Jurgen does not disclose each limitation of the “memory subsystem”
`as arranged in limitation 1(d). ........................................................................49
`C. Jurgen does not disclose the “plurality of sensors” as arranged in
`limitation 1(b). ...............................................................................................51
`D. Jurgen does not disclose the “processor subsystem, coupled to each one of
`said plurality of sensors” as arranged in limitation 1(c). ...............................51
`E. Petitioner did not address each and every limitation of the claimed
`“processor subsystem.” ..................................................................................52
`1. Londt does not disclose “determining, based on data received from
`said plurality of sensors, when to activate said fuel overinjection
`notification circuit.” ....................................................................................53
`
`ii
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`2. Londt does not disclose “determining, based on data received from
`said plurality of sensors … when to activate said upshift notification
`circuit.” ........................................................................................................53
`F. Petitioner failed to present a motivation to combine disparate
`embodiments of Jurgen. .................................................................................54
`1. Petitioner did not present any applicable motivation to combine the
`disparate embodiments of Jurgen cited for limitation 1(d). .......................56
`2. Petitioner did not present any applicable motivation to combine the
`disparate embodiments of Jurgen cited for limitation 1(b). .......................57
`3. Petitioner did not present any applicable motivation to combine the
`disparate embodiments of Jurgen cited for limitation 1(c). .......................58
`G. Ground III should be denied because obviousness grounds based on
`Jurgen were previously considered and rejected by the Office twice
`before. ............................................................................................................59
`1. The Board should decline to hear Ground III under 35 U.S.C. § 325(d). ..60
`2. The Board should decline to hear Ground III under 35 U.S.C. § 314(a). ..62
`VIII. CONCLUSION ............................................................................................. 63
`
`
`iii
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`TABLE OF AUTHORITIES
`
`
`Cases
`ActiveVideo Networks, Inc. v. Verizon Commc’ns, Inc.,
`694 F.3d 1312 (Fed. Cir. 2012) .......................................................................... 56
`
`Page(s)
`
`Cisco Systems, Inc. v. Constellation Techs. LLC,
`Case IPR2014-01179 (PTAB 2015) ................................................................... 56
`
`Cook Group Inc. v. Boston Scientific Scimed, Inc.,
`IPR2017-00440 (PTAB 2017) .......................................................... 24, 31, 56, 57
`
`ETS-Lindgren Inc., v. Microwave Vision, S.A.,
`IPR2015-01048 (PTAB 2015) ...................................................................... 12, 13
`
`Facebook, Inc. v. Pragmatus AV LLC,
`582 F. App’x 864 (Fed. Cir. 2014) ....................................................................... 6
`
`In re Fritch,
`972 F.2d 1260 (Fed.Cir.1992) ............................................................................ 31
`
`General Plastic Industrial Co., Ltd.v. Canon Kabushiki Kaisha,
`IPR2016-01357 (PTAB 2017) ............................................................................ 62
`
`KSR Int’l Co. v. Teleflex, Inc.,
`550 U.S. 398 (2007) ...................................................................................... 25, 56
`
`Kyocera Wireless Corp. v. Int’l Trade Comm’n,
`545 F.3d 1340 (Fed. Cir. 2008) .......................................................................... 54
`
`Liberty Mutual Ins. Co., v. Progressive Casualty Ins. Co.,
`CBM2012-00003 (PTAB 2012) ......................................................................... 48
`
`Meiresonne v. Google, Inc.,
`849 F.3d 1379 (Fed. Cir. 2017) .............................................................. 26, 34, 35
`
`NCR Corp. v. Palm, Inc.,
`120 F. App’x 328 (Fed. Cir. 2005) ....................................................................... 8
`
`Net MoneyIN, Inc. v. Verisign, Inc.,
`545 F.3d 1359 (Fed. Cir. 2008) ...................................................................passim
`
`iv
`
`

`

`
`
`
`
`
`
`
`
`
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005) (en banc) ........................................................ 6, 8
`
`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`Unified Patents Inc., v. John L. Berman,
`IPR 2016-01571 (PTAB 2016) ........................................................................... 62
`
`Unified Patents Inc. v. Spex Techs., Inc.,
`IPR2017-00430 (PTAB 2017) ...................................................................... 13, 14
`
`Unigene Labs., Inc. v. Apotex, Inc.,
`655 F.3d 1352 (Fed. Cir. 2011) ........................................................ 24, 31, 56, 57
`
`Volkswagen Group of America, Inc., v. Velocity Patent LLC,
`IPR2015-00276 (PTAB 2015) ...................................................... 9, 13, 24, 59, 60
`
`Williamson v. Citrix Online,
`792 F.3d 1339 (Fed. Cir. 2015) .......................................................................... 12
`
`Zetec, Inc., v. Westinghouse Elec. Co.,
`IPR2014-00384 (PTAB 2014) ............................................................................ 48
`
`Statutes
`
`35 U.S.C. § 112 .................................................................................. 9, 10, 12, 13, 14
`
`35 U.S.C. § 314 .............................................................................................. 3, 59, 62
`
`35 U.S.C. § 325 .................................................................................. 3, 59, 60, 61, 62
`
`Other Authorities
`37 C.F.R.§ 42.104(b)(3) ....................................................................................passim
`
`
`
`v
`
`

`

`I.
`
`INTRODUCTION
`
`Patent Owner Velocity Patent LLC, (“Velocity”) submits the following
`
`Preliminary Response to the Petition filed by Unified Patents, Inc. (“Petitioner”) on
`
`July 21, 2017, requesting inter partes review of claims 1, 7, 13, 17 and 60 of U.S.
`
`Patent No. 5,954,781 (“the ’781 Patent”). Velocity respectfully requests that the
`
`Board decline institution of an inter partes review because Petitioner has failed to
`
`show a reasonable likelihood of prevailing as to any of the claims challenged in the
`
`Petition.
`
`For each challenged claim of each ground, Petitioner has failed to comply
`
`with 37 C.F.R.§ 42.104(b)(3) and provide a proper construction for the “processor
`
`subsystem” element. Petitioner’s failure to carry its burden is fatal, and all grounds
`
`should be denied for at least this reason. Moreover, for each challenged claim,
`
`Petitioner has failed to demonstrate that each element of the claim is disclosed or
`
`rendered obvious and that all of the limitations purportedly disclosed in the
`
`identified prior art are arranged or combined in the same way as recited in the
`
`claim.
`
`For Ground I, Petitioner has failed to carry its burden to demonstrate that
`
`claims 1, 7, 13, and 17 are obvious over Westbrook in view of Habu and Ghitea.
`
`The combination of references does not disclose each element of the challenged
`
`claims, including limitations of the “memory subsystem,” the vehicle proximity
`
`1
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`alarm elements, and determinations made by the “processor subsystem” as claimed.
`
`
`
`
`
`
`
`The proposed combination also has a different arrangement of elements than the
`
`claims. Moreover, Petitioner fails to provide evidence-backed reasons to combine
`
`distinct embodiments of Westbrook, a 240+ page book, to create the hypothetical
`
`vehicle combination that forms the basis of Ground I.
`
`For Ground II, Petitioner has failed to carry its burden to demonstrate that
`
`claim 60 is obvious over Westbrook in view of Habu, Ghitea, and Rashid. The
`
`combination of references does not disclose each element of challenged claim 60,
`
`including the vehicle proximity alarm elements and determinations made by the
`
`“processor subsystem” as claimed. The proposed combination also has a different
`
`arrangement of elements than the claims. Moreover, Petitioner fails to provide
`
`evidence-backed reasons to combine disparate embodiments of Westbrook used to
`
`create a hypothetical vehicle combination that forms the basis of Ground II.
`
`For Ground III, Petitioner has failed to carry its burden to demonstrate that
`
`claim 1 is obvious over Jurgen in view of Londt. The combination of references
`
`does not disclose each element of challenged claim 1, including limitations of the
`
`“memory subsystem” and determinations made by the “processor subsystem” as
`
`claimed. The proposed combination also has a different arrangement of elements
`
`than the claims. Moreover, Jurgen, a 715+ page handbook comprising 32 chapters
`
`by different authors, is not a single reference, and Petitioner fails to provide
`
`2
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`evidence-backed reasons to combine disparate embodiments from different
`
`
`
`
`
`
`
`chapters of Jurgen used to create a hypothetical vehicle combination that forms the
`
`basis of Ground III. Additionally, Ground III presents the same primary reference
`
`(Jurgen) and raises substantially the same obviousness arguments to the Office that
`
`were presented two times before, once during reexamination and again in a petition
`
`for inter partes review. Because the Office has already twice heard and rejected
`
`challenges to claim 1 based on Jurgen, Velocity respectfully requests that the
`
`Board exercise its discretion to deny institution of Ground III under 35 U.S.C. §
`
`314(a) and § 325(d).
`
`For these reasons, Petitioner has failed to show a reasonable likelihood of
`
`prevailing as to any of the claims challenged in the Petition.
`
`II. OVERVIEW OF THE ’781 PATENT
`The ’781 Patent is an invention in the field of motor vehicles and describes
`
`an inventive system that “notifies the driver of recommended corrections in vehicle
`
`operation and, under certain conditions, automatically initiates selected corrective
`
`action.” Ex. 1001 at 1:7-10. In the preferred embodiment, the ’781 Patent
`
`describes: a driver information system (e.g., lights and/or horns) conveying fuel
`
`(in)efficiency and/or safety information; a radar detector; various sensors for
`
`vehicle operating conditions; and a processor subsystem, coupled to a memory
`
`subsystem, controlling the presentation of driver information and/or automatically
`
`3
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`adjusting vehicle operation in the event of an unsafe condition. Claims of the ’781
`
`
`
`
`
`
`
`Patent relate to an inventive set of driver notifications that balance the presentation
`
`of fuel efficiency and safety information determined by an integrated control
`
`scheme using one or more processors and data from a set of particular types of
`
`sensors.
`
`A. Driver Notifications
`The inventive system communicates to the driver whether he or she is
`
`operating the vehicle in a fuel (in)efficient or unsafe manner. The Background of
`
`the Invention describes that “fuel efficiency of a vehicle may vary dramatically
`
`based upon how the vehicle is operated…operating a vehicle at excessive speed,
`
`excessive RPM and/or excessive manifold pressure will result in both reduced fuel
`
`economy and increased operating costs.” Id. at 1:13-18. Likewise, “based on the
`
`combination of a vehicle’s speed, the distance separating the vehicle from a second
`
`vehicle in front of it and road conditions, many vehicles are operated unsafely.” Id.
`
`at 1:60-63. Though “correct[ing] these types of improper vehicle operations
`
`[is]…surprisingly simple[,]…oftentimes, the driver will be unaware of the need to
`
`take corrective action.” Id. at 1:19-26. Against that background, the inventive
`
`system provides notifications to a driver indicating when to take corrective
`
`action(s) to improve fuel efficiency and/or avoid an unsafe condition.
`
`4
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`Embodiments of the inventive system include shift notifications and a fuel
`
`
`
`
`
`
`
`efficiency notification (“fuel overinjection notification.”) Id. at 14:1; 14:9-12,
`
`15:23-26. In the preferred embodiment, the system provides notifications when the
`
`driver should shift and additionally when “the amount of fuel being supplied to the
`
`engine should be reduced” based on data from various sensors and, for example,
`
`when certain levels are decreasing. Id. at 13:8-28.
`
`The ’781 Patent further describes a vehicle proximity alarm to notify drivers
`
`of an unsafe distance to another object or vehicle. Id. at 17:52-55. The
`
`notification enables drivers to release the gas and/or brake to avoid unsafe
`
`situations. Id. at 10:46-55. Complimenting the vehicle proximity alarm, the ’781
`
`Patent also provides for automatic throttle reduction when dictated by safety
`
`circumstances. Id. at 4:5-11, 7:47-58.
`
`B. Control of Driver Notifications
`The ’781 Patent further describes how a processor subsystem controls
`
`notifications provided to a driver. The processor subsystem of the preferred
`
`embodiment may use data from up to six sensors to determine when to activate
`
`notifications and alarms: a manifold pressure sensor, an RPM sensor, a road speed
`
`sensor, a throttle sensor, a windshield wiper sensor, and a brake sensor. Id. at
`
`5:65-6:4. The processor subsystem may also use information stored in a memory
`
`subsystem to determine whether certain parameters are increasing, decreasing,
`
`5
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`and/or are at, above, or below certain set points, to determine when to activate
`
`
`
`
`
`
`
`notifications. Id. at 11:27-12:31. Figure 1 of the ’781 Patent illustrates an
`
`embodiment of the inventive system.
`
`
`
`
`
`III. CLAIM CONSTRUCTION
`Because the ’781 Patent expired prior to the filing date afforded to the
`
`Petition, the claim terms are to be interpreted using the Phillips standard.
`
`Facebook, Inc. v. Pragmatus AV LLC, 582 F. App’x 864, 866 (Fed. Cir. 2014).
`
`Under this standard, claim terms are interpreted according to their plain and
`
`ordinary or customary meaning at the time of the invention. Phillips v. AWH
`
`Corp., 415 F.3d 1303, 1313 (Fed. Cir. 2005) (en banc). Velocity offers
`
`construction for one term.
`
`6
`
`

`

`
`
`A.
`
`
`
`
`
`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`“Said processor subsystem determining, based upon data received from
`said plurality of sensors, when to activate said fuel overinjection
`notification circuit”
`
`Challenged claims 1, 7, and 13 each recite the element “said processor
`
`subsystem determining, based upon data received from said plurality of sensors,
`
`when to activate said fuel overinjection notification circuit.” Claims 1 and 13
`
`identify four different types of sensors included in said plurality: “a plurality of
`
`sensors…including a road speed sensor, an engine speed sensor, a manifold
`
`pressure sensor, and a throttle position sensor.” Claim 7 identifies three different
`
`types of sensors included in said plurality: “a plurality of sensors…including a
`
`road speed sensor, a manifold pressure sensor, and a throttle position sensor.”
`
`When addressing limitation 1(g), Petitioner offered a construction of “said
`
`processor subsystem determining when to activate” (without any ellipses to
`
`indicate omitted claim terms) under a “plain and ordinary” meaning interpretation.
`
`Pet. at 29. But Petitioner eliminated the middle nine words (“based on data
`
`received from said plurality of sensors”) from the actual claim language. The
`
`limitation as claimed is: “said processor subsystem determining, based on data
`
`received from said plurality of sensors, when to activate…” As shown below, the
`
`language that Petitioner omitted is an important requirement, one that is not shown
`
`by the prior art under a proper construction (i.e., a construction that gives meaning
`
`to all of the words in limitation 1(g)).
`
`7
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`Under a plain and ordinary interpretation, “data received from said plurality
`
`
`
`
`
`
`
`of sensors” means “data received from two or more of said sensors” because a
`
`“plurality of sensors” means two or more sensors. See, e.g., NCR Corp. v. Palm,
`
`Inc., 120 F. App’x 328, 332 (Fed. Cir. 2005). This interpretation is consistent with
`
`the claims of the ’781 Patent which are structured such that independent claims
`
`(e.g., claim 1) more broadly claim the processor subsystem control scheme based
`
`on two or more sensor inputs to the processor. Ex. 1001 at 14:9-12. Then,
`
`dependent claims (e.g., claims 4 and 5) narrow the control scheme by reciting
`
`limitations requiring that the processor subsystem take into account data from four
`
`sensors when determining whether to activate the up/downshift notification and/or
`
`the fuel overinjection notification. Id. at 14:43-47, 14:58-63.
`
`This interpretation is consistent with relevant distinctions between claim 1
`
`and claim 17. Phillips, 415 F.3d at 1314 (“Differences among claims can also be a
`
`useful guide in understanding the meaning of particular claim terms.”). Claim 17
`
`requires decisions to be made based on “at least one sensor.” In contrast, claim 1
`
`requires determinations based on data from a “plurality of sensors” (i.e., two or
`
`more sensors). This interpretation is consistent with the construction by the
`
`District Court of the Northern District of Illinois in the underlying litigation, which
`
`held that “plurality of sensors” means “two or more sensors” as well as the
`
`construction of “plurality of sensors” that Velocity proposed in a prior IPR. See Ex.
`
`8
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`2002 at 17-19; Volkswagen Group of America, Inc., v. Velocity Patent LLC,
`
`
`
`
`
`
`
`IPR2015-00276 (PTAB 2015) (Paper 6) at 12. Thus, as properly construed, the
`
`claimed “processor subsystem determining, based upon data received from said
`
`plurality of sensors, when to activate said fuel overinjection notification circuit”
`
`must be based on data received from two or more of the three or four sensors
`
`recited in claims 1, 7, and 13.
`
`IV. THE PETITION SHOULD BE DENIED ON ALL GROUNDS UNDER
`37 C.F.R. § 42.104(b)(3)
`
`The Petition should be denied on all grounds under 37 C.F.R.§ 42.104(b)(3)
`
`because Petitioner failed to identify corresponding structure and claimed functions
`
`after invoking 35 U.S.C. 112 ¶ 6 for the claimed “processor subsystem.” At the
`
`Markman hearing in 2016, Defendants in the underlying litigation argued that the
`
`claimed “processor subsystem” is governed by 35 U.S.C. 112 ¶ 6 because the term
`
`purportedly does not have sufficient structure and is “a nonce term that can mean
`
`anything.” Ex. 2002 at 11. Velocity took the opposite position and argued that 35
`
`U.S.C. 112 ¶ 6 does not apply. The Court sided with Defendants, resulting in a
`
`narrow construction. The Court construed the “processor subsystem” as a means-
`
`plus-function term under 35 U.S.C. 112 ¶ 6 and identified detailed algorithms in
`
`the specification for determining when to activate various notification circuits and
`
`alarms as the structure for the element. Id. at 14-17.
`
`9
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`Here, Petitioner offered a construction of “processor subsystem” within its
`
`
`
`
`
`
`
`discussion of limitation 1(c). Pet. at 21. Relying on its expert, Dr. Andrews,
`
`Petitioner construed the element by arguing that “the recited ‘processor subsystem’
`
`is not limited to any specific physical implementation” which is simply another
`
`way of stating that the claimed “processor subsystem” has no structure. Id.
`
`(emphasis added.) Petitioner also argued that “the ’781 patent only describes it in
`
`terms of functionality without restricting the physical components or hardware”
`
`which is another way of stating that the claim term is purely functional. Id.
`
`(emphasis added). Petitioner concluded that a POSITA would understand that the
`
`element “could include one or more microprocessors for carrying out the
`
`functionality attributed to the processor subsystem of the ’781 Patent,” but did not
`
`identify the attributed functionality. Id.
`
`Although Petitioner did not explicitly argue that the “processor subsystem”
`
`is governed by 35 U.S.C. 112 ¶ 6, Petitioner has essentially taken the same position
`
`as the Defendants and Court in the underlying litigation, that the element is purely
`
`functional and does not have structure. However, unlike the Defendants or the
`
`Court, Petitioner did not identify the specific “functionality attributed to the
`
`processor subsystem” or any special purpose algorithms that could form the
`
`structure of the “processor subsystem” under a means-plus-function construction.
`
`Pet. at 21. Thus, in contrast to the Court’s narrow construction, Petitioner’s
`
`10
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`construction is exceedingly broad, enabling Petitioner to apply the “processor
`
`
`
`
`
`
`
`subsystem” to the prior art without any need to identify the functions performed by
`
`the “processor subsystem” or the corresponding structure.
`
`Petitioner relied on this exceedingly broad construction in all of its grounds.
`
`For example, Petitioner argued that “any processors included in any of the
`
`subsystems connected” to the central processor of Westbrook “constitute ‘a
`
`processor subsystem, coupled to each one of said plurality of sensors, to receive
`
`data therefrom’ as recited in claim 1.” Pet. at 21-22. The same structureless
`
`construction was applied for each challenged claim in each ground, typically by
`
`referencing back to arguments for claim 1 of Ground I. Pet. at 21, 31-33, et seq.
`
`Moreover, despite arguing that the “processor subsystem” was purely
`
`functional, Petitioner glossed over or missed entirely various claimed functions of
`
`the element. For example, as discussed below, when applying the prior art to claim
`
`60 in Ground II, Petitioner ignored
`
`the associated claimed function of
`
`“determining whether to activate said vehicle proximity alarm circuit based upon
`
`… vehicle speed data received from said road speed sensor.” As another example,
`
`Petitioner ignored the associated claimed function of “determining, based upon
`
`data received from said plurality of sensors, when to activate said fuel
`
`overinjection notification circuit,” for claims 1, 7, and 13, as described below for
`
`Grounds I and III.
`
`11
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
` It is well settled law that functional claim terms that do not restrict physical
`
`
`
`
`
`
`
`implementation or structure fall within the scope of 35 U.S.C. 112 ¶ 6. 1
`
`Williamson v. Citrix Online, 792 F.3d 1339, 1348 (Fed. Cir. 2015). Here, because
`
`Petitioner’s construction relies on Dr. Andrew’s opinion that the recited “processor
`
`subsystem” is described only in terms of function and is not restricted to any
`
`physical implementation, Petitioner should have, but did not, perform the proper
`
`35 U.S.C. 112 ¶ 6 analysis that is the consequence of Dr. Andrew’s opinion. That
`
`is, Petitioner “must identify the specific portions of the specification that describe
`
`the structure, material, or acts corresponding to each claimed function.” 37 C.F.R.
`
`§ 42.104(b)(3); Williamson, 792 F.3d at 1352 (“In cases such as this, involving a
`
`claim limitation that is subject to § 112, para. 6 that must be implemented in a
`
`special purpose computer, this court has consistently required that the structure
`
`disclosed in the specification be more than simply a general purpose computer or
`
`microprocessor.”)
`
`Because Petitioner failed to identify any structure or the claimed functions
`
`for the “processor subsystem” under its own construction, the petition must be
`
`denied. ETS-Lindgren Inc., v. Microwave Vision, S.A., IPR2015-01048 (PTAB
`
`2015) (Paper 6) at 13 (“[F]ailure to comply with 37 C.F.R.§ 42.104(b)(3) is basis
`
`
`1 Velocity continues to believe that the term is not governed by 35 U.S.C. 112 ¶ 6. Nevertheless, the
`Petition must be denied because its failure to present a complete construction based on 35 U.S.C. 112 ¶ 6
`is internally inconsistent with the position that the element is purely functional.
`
`12
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`alone to deny an inter partes review.”) This is especially true where petitioner
`
`
`
`
`
`
`
`“does not identify corresponding structure for its own proposed construction.” Id.
`
`at n.8 (emphasis in original); Volkswagen Group of America, Inc., IPR2015-00276
`
`(Paper 8) at 15 (Denying institution for Petitioner’s failure to provide a proper
`
`construction and “declin[ing] to construe the means-plus-function limitations ab
`
`initio where Petitioner has not provided argument as to the scope of these claims.”)
`
`The Board recently denied institution of a different IPR filed by Petitioner
`
`for failure to comply with 37 C.F.R.§ 42.104(b)(3) and there is no reason for a
`
`different result here. The Board agreed that a petition “cannot properly identify
`
`how the prior art renders the claims unpatentable” if Petitioner “fails[] to identify a
`
`recited function and a corresponding structure disclosed in the specification that is
`
`clearly linked or associated with the function in the claim” for a functional claim
`
`term. Unified Patents Inc. v. Spex Techs., Inc., IPR2017-00430 (PTAB 2017)
`
`(Paper 8) at 9. The Board characterized Petitioner’s “failure to identify any
`
`specific structure, material, or acts tied in the specification to the claimed function”
`
`as being “fatally deficient.” Id. at 10, n4. The Board also explained that
`
`“[b]ecause it was Petitioner’s obligation under 37 C.F.R. § 42.104(b)(3) in the first
`
`instance to identify corresponding structure for terms subject to construction under
`
`35 U.S.C. § 112 ¶ 6, and we determine for the reasons set forth above that
`
`Petitioner does not identify any appropriate structure corresponding [to the claim
`
`13
`
`

`

`
`
`
`
`
`
`
`
`Patent Owner’s Preliminary Response
`IPR2017-01723 (Patent 5,954,781)
`
`
`term] we determine that Petitioner cannot meet its burden of showing a reasonable
`
`
`
`
`
`
`
`likelihood of prevailing in its challenges.” Id. at 10.
`
`Petitioner is likely aware of the District Court’s 2016 Markman order
`
`construing the “processor subsystem” under 35 U.S.C. 112 ¶ 6 and holding that
`
`the structure of the element is a variety of detailed algorithms found in the patent
`
`specification. Ex. 2002 at 14-17. Under the Court’s construction, the combination
`
`of references relied upon in the Petition fall far, far short of anticipating or
`
`rendering obvious the challenged cla

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