throbber
Paper 45
`
`Entered: September 28, 2015
`
`
`
`
`
`
`
`Trials@uspto.gov
`571-272-7822
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`FORD MOTOR COMPANY,
`Petitioner,
`
`v.
`
`PAICE LLC & THE ABELL FOUNDATION, INC.,
`Patent Owner.
`____________
`
`Case IPR2014-00579
`Patent 7,104,347 B2
`____________
`
`
`
`Before SALLY C. MEDLEY, KALYAN K. DESHPANDE, and
`CARL M. DEFRANCO, Administrative Patent Judges.
`
`DEFRANCO, Administrative Patent Judge.
`
`
`
`FINAL WRITTEN DECISION
`35 U.S.C. § 318(a) and 37 C.F.R. § 42.73
`
`
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`
`I. INTRODUCTION
`
`Ford Motor Company (“Ford”) filed a Petition (“Pet.”) for inter partes
`
`review of claims 1, 7, 8, 18, 21, 23, and 37 of U.S. Patent No. 7,104,347 B2
`
`(“the ’347 patent”), which is owned by Paice LLC & The Abell Foundation,
`
`Inc. (collectively, “Paice”). In a preliminary proceeding, we determined
`
`there is a reasonable likelihood that the challenged claims are unpatentable
`
`under 35 U.S.C. § 103, and instituted trial (“Dec. to Inst.”). In support of
`
`patentability, Paice filed a Patent Owner Response (“PO Resp.”), and Ford
`
`followed with a Reply (“Reply”). After hearing oral argument from both
`
`parties,1 and pursuant to our jurisdiction under 35 U.S.C. § 6(c), we
`
`conclude Ford has proven, by a preponderance of the evidence, that all of the
`
`challenged claims are unpatentable.
`
`II. BACKGROUND
`
`The ’347 patent 2
`
`The ’347 patent describes a hybrid vehicle with an internal
`
`A.
`
`
`
`combustion engine, two electric motors (a starter motor and a traction
`
`motor), and a battery bank, all controlled by a microprocessor that directs
`
`the transfer of torque from the engine and traction motor to the drive wheels
`
`of the vehicle. Ex. 1101, 17:5–45, Fig. 4. The microprocessor features an
`
`engine control strategy that runs the engine only under conditions of high
`
`efficiency, typically when the vehicle’s instantaneous torque requirements
`
`(i.e., the amount of torque required to propel the vehicle, or “road load”) is
`
`
`1 A transcript (“Tr.”) has been entered into the record. Paper 44.
`2 The ’347 patent is also the subject of several co-pending cases, including
`Paice LLC v. Ford Motor Co., No. 1:14-cv-00492 (D. Md.), filed Feb. 19,
`2014 (Pet. 1), and Paice LLC v. Hyundai Motor Co., No. 1:12-cv-00499
`(D. Md.), filed Feb. 16, 2012 (PO Resp. 6).
`
`2
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`at least equal to 30% of the engine’s maximum torque output (“MTO”)
`
`capability. Id. at 20:52–60, 35:5–14; see also id. at 13:47–61 (“the engine is
`
`never operated at less than 30% of MTO, and is thus never operated
`
`inefficiently”).
`
`
`
`Running the engine only when it is efficient to do so leads to
`
`improved fuel economy and reduced emissions. Id. at 13:47–51. To achieve
`
`such efficiency, the hybrid vehicle includes various operating modes that
`
`depend on the vehicle’s torque requirements, the battery’s state of charge,
`
`and other operating parameters. Id. at 19:53–55. For example, the hybrid
`
`vehicle may operate in: (1) an all-electric mode, where only the traction
`
`motor provides the torque to propel the vehicle and operation of the engine
`
`would be inefficient (i.e., stop-and-go city driving); (2) an engine-only
`
`mode, where only the engine provides the torque to propel the vehicle and
`
`the engine would run at an efficient level (i.e., highway cruising); (3) a dual-
`
`operation mode, where the traction motor provides additional torque to
`
`propel the vehicle beyond that already provided by the engine and the torque
`
`required to propel the vehicle exceeds the maximum torque output of the
`
`engine (i.e., while accelerating, passing, and climbing hills); and (4) a
`
`battery recharge mode where the engine operates a generator to recharge the
`
`battery while the traction motor drives the vehicle. Id. at 35:66–36:58,
`
`37:26–38:55.
`
`B.
`
`The challenged claims
`
`
`
`Ford challenges the patentability of claims 1, 7, 8, 18, 21, 23, and 37.
`
`Pet. 3. Of the challenged claims, claims 1 and 23 are independent. Claim 1
`
`is directed to a “hybrid vehicle” (Ex. 1101, 58:13), while claim 23 is
`
`directed to a “method of control” of a hybrid vehicle (id. at 60:22). Each of
`
`3
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`the independent claims recites that the engine is employed when it can
`
`produce torque “efficiently,” which claim 1 describes as when the torque
`
`required to propel the vehicle is “at least equal to a setpoint (SP) [but]
`
`substantially less than the maximum torque output (MTO)” of the engine (id.
`
`at 58:29–37), and claim 23 describes as when the torque required to propel
`
`the vehicle is “between a lower level SP and a maximum torque output
`
`MTO” (id. at 60:23–42).
`
`
`
`Claim 1 is illustrative of the challenged claims:
`
`1.
`
`A hybrid vehicle, comprising:
`
`an internal combustion engine controllably coupled to
`
`road wheels of said vehicle;
`
`
`
`a first electric motor connected to said engine [a]nd
`operable to start the engine responsive to a control signal;
`
`
`
`a second electric motor connected to road wheels of said
`vehicle, and operable as a motor, to apply torque to said wheels
`to propel said vehicle, and as a generator, for accepting torque
`from at least said wheels for generating current;
`
`
`
`a battery, for providing current to said motors and
`accepting charging current from at least said second motor; and
`
`a controller for controlling the flow of electrical and
`mechanical power between said engine, first and second
`motors, and wheels,
`
`
`
`wherein said controller starts and operates said engine
`when torque require[d] to be produced by said engine to propel
`the vehicle and/or to drive either one or both said electric
`motor(s) to charge said battery is at least equal to a setpoint
`(SP) above which said engine torque is efficiently produced,
`and wherein the torque produced by said engine when operated
`at said setpoint (SP) is substantially less than the maximum
`torque output (MTO) of said engine.
`
`Ex. 1101, 58:13–37 (emphases added).
`
`4
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`C.
`
`The instituted grounds of unpatentability
`
`
`
`In a preliminary proceeding, we instituted trial because Ford made a
`
`threshold showing of a “reasonable likelihood” that the challenged claims
`
`were unpatentable as obvious over five publications that share a common
`
`author, Professor James R. Bumby, which are referred to individually as
`
`Bumby I,3 Bumby II,4 Bumby III,5 Bumby IV,6 and Bumby V,7 and
`
`collectively as “the Bumby references” or “Bumby.” Dec. to Inst. 13. We
`
`now decide whether Ford has proven the unpatentability of the challenged
`
`claims by a “preponderance of the evidence.” 35 U.S.C. § 316(e).
`
`A.
`
`Claim construction
`
`III. ANALYSIS
`
`
`
`In an inter partes review, claim terms in an unexpired patent are given
`
`their broadest reasonable construction in light of the specification of the
`
`patent in which they appear. 37 C.F.R. § 42.100(b). This standard involves
`
`determining the ordinary and customary meaning of the claim terms as
`
`understood by one of ordinary skill in the art reading the patent’s entire
`
`
`3 J.R. Bumby, Computer modelling of the automotive energy requirements
`for internal combustion engine and battery electric-powered
`vehicles, IEE PROC., v. 132, pt. A, no. 5, 265–279 (Sep. 1985) (Ex. 1103).
`4 J.R. Bumby and I. Forster, Optimisation and control of a hybrid electric
`car, IEE PROC., v. 134, pt. D, no. 6, 373–387 Nov. 1987 (Ex. 1104).
`5 I. Forster and J.R. Bumby, A hybrid internal combustion engine/battery
`electric passenger car for petroleum displacement, PROC. INST. MECH.
`ENGRS., v. 202, no. D1, 51–64 Jan. 1988 (Ex. 1105).
`6 J.R. Bumby and P.W. Masding, A Test-Bed Facility for Hybrid IC Engine-
`Battery Electric Road Vehicle Drive Trains, TRANS. INST. MEAS. & CONT.,
`v. 10, no. 2, 87–97 Apr. 1988 (Ex. 1106).
`7 P.W. Masding and J.R. Bumby, Integrated microprocessor control of a
`hybrid i.c. engine/battery-electric automotive power train, TRANS. INST.
`MEAS. & CONT., v. 12, no. 3, 128-146 Jan. 1990 (Ex. 1107).
`
`5
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`written disclosure. In re Translogic Tech., Inc., 504 F.3d 1249, 1257 (Fed.
`
`Cir. 2007). Here, our review centers on the construction of two claim
`
`terms—“road load (RL)” and “setpoint (SP).”8
`
`
`
`
`
`1.
`
`“Road load” or “RL”
`
`The terms “road load” and “RL” appear throughout the claims of the
`
`’347 patent. For example, claim 7, which depends from claim 1, recites that
`
`the operating modes are “responsive to the value for the road load (RL) and
`
`said setpoint (SP), both expressed as percentages of the maximum torque
`
`output of the engine,” and claim 23 recites the step of “determining the
`
`instantaneous torque RL required to propel said vehicle responsive to an
`
`operator command.”
`
`
`
`The specification also describes “road load” as “the vehicle’s
`
`instantaneous torque demands, i.e., that amount of torque required to propel
`
`the vehicle at a desired speed.” Ex. 1101, 12:40–57 (emphasis added).
`
`Elsewhere the specification similarly speaks of road load in terms of a
`
`“torque” requirement:
`
`The vehicle operating mode is determined by a microprocessor
`responsive to the “road load,” that is, the vehicle’s
`instantaneous torque demands.
`
`
`* * *
`While operating at low speeds, e.g., when the vehicle’s
`torque requirements (“road load,” or “RL”) are less than
`
`
`8 Ford also contends that the terms “low-load mode I,” “highway cruising
`mode IV,” and “acceleration mode V” are in need of construction. Pet. 13–
`17. Those terms are expressly defined by claim 7 (Ex. 1101, 58:64–59:8),
`and, thus, no further construction is necessary.
`
`6
`
`
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`
`30% of the engine's maximum torque output (“MTO”),
`engine 40 is run only as needed to charge battery bank 22.
`
`Id. at 11:60–63, 36:8–11 (emphases added). Also, in distinguishing the
`
`claimed invention over the prior art, the specification explains that:
`
`Numerous prior art references . . . indicate the vehicle operating
`mode should be controlled in response to vehicle speed . . . [but
`none] recognizes that the desired vehicle operational mode
`should preferably be controlled in response to the vehicle’s
`actual torque requirements, i.e., the road load. Doing so
`according to the invention provides superior performance, in
`terms of both vehicle response to operator commands and fuel
`efficiency. . . .
`
`Id. at 13:1–15 (emphasis added).
`
`
`
`These passages from the specification comport with a construction of
`
`“road load” that is limited to an instantaneous torque value, and, more
`
`specifically, a torque value which can be expressed in terms of a percentage
`
`of the engine’s “maximum torque output” or “MTO.” For instance, the
`
`specification states that:
`
`road load is shown . . . as varying from 0 at the origin to 200%
`of maximum torque output.
`
`
`* * *
`During highway cruising . . . where the road load is between
`about 30% and 100% of the engine’s maximum torque output,
`the engine alone is used to propel the vehicle.
`
`
`* * *
`[W]hen the microprocessor detects that the road load exceeds
`100% of the engine’s maximum torque output, it controls
`inverter/charger 27 so that energy flows from battery bank 22 to
`traction motor 25, providing torque propelling the vehicle in
`addition to that provided by engine 40.
`
`Id. at 37:13–15, 37:45–47, 38:5–10 (emphases added).
`
`7
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`
`
`We see no reason to depart from these express definitions of “road
`
`load” in terms of an amount of torque. Thus, consistent with the
`
`specification’s many uses of the term, “road load” is properly construed to
`
`be “the amount of instantaneous torque required for propulsion of the
`
`vehicle.”
`
`
`
`Paice urges that our construction of “road load” should additionally
`
`account for external forces acting on the vehicle, such as “aerodynamic
`
`drag.” PO Resp. 19–20 n.8. Although aerodynamic forces may play a role
`
`in the amount of torque required to propel the vehicle, we need not address
`
`them in order to construe the term “road load.” That is because the claims
`
`and specification of the ’347 patent consistently speak of “road load” in a
`
`more general sense. In fact, the specification mentions aerodynamic forces
`
`only in the context of a “heavy vehicle” having “high torque requirements”
`
`and “poor aerodynamic characteristics.” Ex. 1101, 49:9–14. That singular
`
`example, however, is not enough for us to overlook the countless
`
`descriptions found elsewhere in the specification, where “road load” or “RL”
`
`is defined simply as “the amount of torque required to propel the vehicle,”
`
`divorced from other potential forces acting on the vehicle.
`
`
`
`
`
`2.
`
`“Setpoint” or “SP”
`
`Each of independent claims 1 and 23 recites that the engine operates
`
`“efficiently” when the torque required to propel the vehicle is between a
`
`“setpoint (SP)” and a “maximum torque output (MTO).” Paice seeks to
`
`construe the term “setpoint” as “a definite, but potentially variable value at
`
`which a transition between operating modes may occur.” PO Resp. 7. Ford,
`
`on the other hand, advocates that “setpoint” means a “predetermined torque
`
`value.” Pet. 14. Paice protests any construction that limits the meaning of
`
`8
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`“setpoint” to a “torque value” (PO Resp. 11), arguing that the specification
`
`supports a broader definition that also could encompass a “state of charge of
`
`the battery” (Prelim. Resp. 13–16) or a “transition between operating
`
`modes” (PO Resp. 7–10).
`
`
`
`We agree with Paice that the specification speaks of “setpoint” in
`
`terms of a “torque output,” a “state of charge of the battery,” or a “transition
`
`point.” See Ex. 1101, 40:20–54. However, the claim language is not so
`
`broad. Although we recognize that the specification is an important tool in
`
`claim construction, it is the claim language—and the context in which the
`
`disputed term is used—that is of primary importance. Phillips v. AWH
`
`Corp., 415 F.3d 1303, 1314 (Fed. Cir. 2005) (en banc) (“the claims
`
`themselves provide substantial guidance as to the meaning of particular
`
`claim terms . . . the context in which a term is used in the asserted claim can
`
`be highly instructive”) (citations omitted). Put another way, “the name of
`
`the game is the claim.” In re Hiniker Co., 150 F.3d 1362, 1369 (Fed. Cir.
`
`1998) (quoting Giles Sutherland Rich, Extent of Protection and
`
`Interpretation of Claims—American Perspectives, 21 Int’l Rev. Indus. Prop.
`
`& Copyright L. 497, 499 (1990)).
`
`
`
`Here, contrary to Paice’s assertion, the claim language consistently
`
`refers to a “setpoint” in terms of a “torque” requirement. For instance,
`
`claim 1 recites that the controller starts and operates the engine
`
`when torque require[d] to be produced by said engine . . . is at
`least equal to a setpoint (SP) above which said engine torque is
`efficiently produced, and wherein the torque produced by said
`engine when operated at said setpoint (SP) is substantially less
`than the maximum torque output (MTO) of said engine.
`
`
`9
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`Ex. 1101, 58:30–37 (emphases added). And, likewise, claim 23 speaks
`
`consistently of “setpoint” or “SP” as being the “lower level,” or limit, at
`
`which the engine can efficiently produce torque, reciting that: the engine is
`
`capable of “efficiently producing torque at loads between a lower level SP
`
`and a maximum torque output”; the engine is employed to propel the vehicle
`
`“when the torque RL required to do so is between said lower level SP and
`
`MTO”; and “wherein the torque produced by said engine when operated at
`
`said setpoint (SP) is substantially less than the maximum torque output.” Id.
`
`at 60:22–54 (emphases added). These express limitations suggest that
`
`“setpoint” is not just any value, but a value that—per the surrounding claim
`
`language—equates to the level of the engine’s “torque.”
`
`
`
`Moreover, we note that claim 23 includes a limitation directed to “the
`
`state of charge of said battery,” but it never correlates that limitation with a
`
`“setpoint” or “SP,” even though those terms are used elsewhere throughout
`
`the claim. Nor does Paice point us to anywhere in the claims that describe
`
`the setpoint in the context of the battery’s state of charge. Indeed, when
`
`speaking of “the state of charge of the battery,” dependent claims 9 and 31
`
`refer to it in terms of falling below “a predetermined level,” not a “setpoint.”
`
`Thus, given the claim language’s unequivocal use of “setpoint” or “SP” in
`
`the context of a “torque” requirement, we construe the terms “setpoint” and
`
`“SP” to mean “a torque value.” Our assessment does not end there,
`
`however.
`
`
`
`The specification states that “the value of a setpoint (for example)
`
`may vary somewhat in response to recent [driving] history, or in response to
`
`monitored variables” or may be “reset . . . in response to a repetitive driving
`
`pattern.” Ex. 1101, 40:37–59. But, just because a setpoint may vary under
`
`10
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`certain circumstances, that potential variation does not foreclose it from
`
`being “set,” or “fixed,” at some point in time.9 A setpoint for however short
`
`a period of time still is a setpoint. Any other construction would defeat its
`
`purpose of being set for comparison against another value. For example, the
`
`specification states that “the microprocessor tests sensed and calculated
`
`values for system variables [such as road load (RL)] . . . against setpoints,
`
`and uses the results of the comparisons to control the mode of vehicle
`
`operation.” Ex. 1101, 40:22–31 (emphasis added). That description makes
`
`clear that the comparative setpoint is a pre-defined value. Indeed, the
`
`specification refers to setpoint in terms of a “defined setpoint.” Id. at 19:64.
`
`As such, we construe the term “setpoint” to mean at least “a predefined
`
`torque value that may or may not be reset.”10
`
`
`
`Finally, we cannot disregard Paice’s argument that our construction is
`
`“directly at odds” with the construction adopted by two district courts in
`
`related actions.11 PO Resp. 6. According to Paice, each of the district courts
`
`construed “setpoint,” as used in the ’347 patent, to mean “a definite, but
`
`potentially variable value at which a transition between operating modes
`
`may occur.” Id. Although, generally, we construe claim terms under a
`
`different standard than that of a district court, and thus, are not bound by a
`
`district court’s prior claim construction, we nonetheless feel compelled, by
`
`the circumstances of this case, to evaluate the district courts’ construction in
`
`
`9 The definition of “set” is “determined . . . premeditated . . . fixed by
`authority or appointment . . . prescribed, specified . . . built-in . . . settled,
`persistent.” Merriam-Webster’s Collegiate Dictionary (10th ed. 2000).
`Ex. 3001.
`10 Even Paice’s declarant agreed that, given the “comparison” being made in
`claims 1 and 23, the “most straightforward” construction is that “setpoint is a
`torque value.” Ex. 1143, 79:1–80:25.
`
`11
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`light of our construction. See Power Integrations, Inc. v. Lee, 2015 WL
`
`4757642, at *6 (Fed. Cir. Aug. 12, 2015) (“Given that [patent owner’s]
`
`principal argument to the board . . . was expressly tied to the district court’s
`
`claim construction, we think that the board had an obligation, in these
`
`circumstances, to evaluate that construction”).
`
`
`
`Here, the first half of the district courts’ construction—“a definite, but
`
`potentially variable value”—coincides squarely with our construction of
`
`“setpoint” as a “predefined” value “that may or may not be reset.” The
`
`difference, however, lies in our construction of “setpoint” to be a “torque”
`
`value. On that point, the district court held:
`
`there is nothing in the claims or specification that indicate a
`given setpoint value is actually represented in terms of torque.
`In fact, the specification clearly indicates that the state of
`charge of the battery bank, ‘expressed as a percentage of its full
`charge’ is compared against setpoints, the result of the
`comparison being used to control the mode of the vehicle.
`
`Ex. 1115, 10 (citing the ’347 patent, 40:28–31). But, as discussed above,
`
`although claims are read in light of the specification, it is the use of the term
`
`“setpoint” within the context of the claims themselves that provides a firm
`
`basis for our construction. See Phillips, 415 F.3d at 1314 (“the context in
`
`which a term is used in the asserted claim can be highly instructive”). Here,
`
`the claims instruct us that “setpoint,” when read in the context of the
`
`surrounding language, is limited to a torque value. We decline to read the
`
`term as also encompassing a state of charge of the battery, as the district
`
`
`11 Paice LLC v. Toyota Motor Corp., No. 2:07-cv-00180, Dkt. 63 (E.D. Tex.
`Dec. 5, 2008); Paice LLC v. Hyundai Motor Co., No. 1:12-cv-00499, 2014
`WL 3725652 (D. Md. July 24, 2014).
`
`12
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`court did. Thus, we stand by our determination that claims 1 and 23
`
`consistently refer to “setpoint” as a “torque” requirement.
`
`
`
`With regard to the second half of the district courts’ construction of
`
`“setpoint” as “a transition between operating modes,” we believe it imports
`
`an extraneous limitation into the meaning of “setpoint” that is neither
`
`supported by the claim language nor the specification. In particular,
`
`claims 1 and 23 expressly describe “setpoint (SP)” as being the lower limit
`
`at which the engine can “efficiently” produce torque. Those claims make no
`
`mention of this lower limit as being a “transition” point for the “operating
`
`modes,” although it potentially may be. Indeed, the specification
`
`acknowledges that the mode of operation does not always transition, or
`
`switch, at the setpoint, but instead depends on a number of operating
`
`parameters:
`
`the values of the sensed parameters in response to which the
`operating mode is selected may vary . . . , so that the operating
`mode is not repetitively switched simply because one of the
`sensed parameters fluctuates around a defined setpoint.”
`
`Ex. 1101, 19:53–64 (emphasis added).
`
`
`
`Moreover, that a “setpoint” is not a per se transition between
`
`operating modes is reinforced by the fact that only the dependent claims, for
`
`example claims 7 and 28, mention “setpoint” in terms of “operating modes.”
`
`See id. at 58:58–60, 61:11–13. Where the meaning of a claim term is clear
`
`from the context of its use in an independent claim, we will not further limit
`
`the meaning of the term by its use in a dependent claim, absent justification
`
`for doing so. See Phillips, 415 F.3d at 1315 (“the presence of a dependent
`
`claim that adds a particular limitation gives rise to a presumption that the
`
`limitation in question is not present in the independent claim”). Thus,
`
`13
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`although the district courts may have had justification for a narrower
`
`construction of “setpoint,” we believe it is necessary here and may lead to
`
`confusion given our standard of applying the “broadest reasonable
`
`construction” to the terms of a claim. See 37 C.F.R. § 42.100(b). As such,
`
`we maintain our construction of “setpoint,” as discussed above, which
`
`arguably may differ from the construction arrived at in the related district
`
`court actions.
`
`B.
`
`The sole asserted ground—obviousness over the Bumby references
`
`
`
`Ford relies on the five Bumby references as teaching, collectively, the
`
`limitations of the contested claims, and a reason why a skilled artisan would
`
`have been combined them to arrive at the claimed invention. Pet. 28–59.
`
`Specifically, like the contested claims, the Bumby references disclose the
`
`essential components of a hybrid electric vehicle, including an internal
`
`combustion engine, an electric motor, a battery, and a controller for
`
`controlling the vehicle’s different modes of operation. Compare Ex. 1104,
`
`Fig. 2 (Bumby II) with Ex. 1101, Fig. 4 (the ’347 patent). The “different
`
`operating modes,” according to Bumby III, include an electric mode, a
`
`hybrid mode, an engine mode, and a battery charge mode. Ex. 1105, 4–5
`
`(Table 2), 11–12 (Fig. 15).
`
`
`
`In turn, Bumby IV teaches that the “microprocessor” controller is “the
`
`heart of the drive-train control system” and “implement[s] the hybrid-vehicle
`
`control strategy . . . in the most efficient way to meet driver demand.” Ex.
`
`1106, 4 (emphasis added). Efficiency is achieved, Bumby IV explains, by
`
`operating the engine only “when load demand is high,” rather than at “low
`
`speed, low load situations [where] the ic engine is inefficient compared with
`
`the electric traction system.” Ex. 1106 at 3–4; Ex. 1108 ¶¶ 254–255, 258.
`
`14
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`And, notably, Bumby II and III define “maximum engine efficiency” in
`
`terms of a “lower torque bound” and an “upper torque bound.” Ex. 1104 at
`
`10–11 (Fig. 16); Ex. 1105 at 7–8 (Fig. 8). “Above the upper torque bound,”
`
`according to Bumby II, “true hybrid operation is used with the electric motor
`
`supplying the excess torque above the maximum available from the engine.”
`
`Ex. 1104, 11. “Below the lower torque bound and the lower speed bound,
`
`all-electric operation is favoured [which] eliminates inefficient use of the
`
`engine.” Id. Thus, taken together, the five Bumby references teach a hybrid
`
`vehicle in which the internal combustion engine and the electric motor are
`
`capable of driving the road wheels, with the mix of power between the
`
`engine and motor being controlled by a microprocessor to provide maximum
`
`engine efficiency.12
`
`
`
`Paice, in turn, argues essentially five points in rebuttal of Ford’s
`
`reliance on the Bumby references: first, a skilled artisan would not have
`
`combined the Bumby references because they “teach away” from one
`
`another; second, the Bumby references do not disclose or suggest the use of
`
`“setpoints (SP),” as required by claims 1, 7, and 23; third, the Bumby
`
`references do not disclose or suggest the use of “road load (RL),” as required
`
`by claims 7 and 23; fourth, the Bumby references do not disclose or suggest
`
`the “first electric motor” of claims 1 and 8; and fifth, the Bumby references
`
`do not disclose or suggest the “battery charging” mode of claims 1 and 23.
`
`PO Resp. 15, 21, 34, 37, 43, respectively. We are not persuaded by any of
`
`Paice’s arguments.
`
`
`12 Ford’s declarant, Dr. Davis, whose testimony we find persuasive,
`confirms the teachings of each of the Bumby references. Ex. 1108 ¶¶ 238–
`244, 251–255, 259–272.
`
`15
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`
`
`1.
`
`The reason to combine the Bumby references
`
`
`
`Despite the overlapping teachings of the Bumby references, Paice
`
`argues that Ford’s “only reasons” for combining the Bumby references are
`
`that they “share a common author and cite to each other.” PO Resp. 15. We
`
`disagree. Aside from their citation to one another, the Bumby references
`
`document, chronologically, the evolution of a hybrid vehicle project
`
`undertaken by Professor James Bumby and his team at the University of
`
`Durham in the 1980s. See Pet. 18–28; see also Ex. 1106, 2 and Ex. 1107, 2–
`
`3 (referencing earlier Bumby references). Indeed, common to the five
`
`Bumby references is the stated objective of the project—to develop an
`
`optimal control strategy for maximizing efficient operation of a hybrid
`
`vehicle. See, e.g., Ex. 1104, 6, Ex. 1105, 6, 15, Ex. 1106, 2; see also Ex.
`
`1108 ¶¶ 206, 208, 220, 230.
`
`
`
`Also, evidence proffered by Paice itself, a doctorate thesis by Philip
`
`Masding in 1988 (Ex. 2104, “the Masding Thesis”), further supports the
`
`rationale to combine.13 The Masding Thesis brings together the five Bumby
`
`references in a single compilation and summarizes the efforts undertaken by
`
`Professor Bumby and his team. Ex. 1140 ¶¶ 5–16, 21–22 (citing Ex. 2104,
`
`35–49). Even Paice’s own declarant, Mr. Hannemann, testified that the
`
`“thesis written by Masding . . . encompasses a lot of the elements of all of
`
`the other five [Bumby] papers.” Ex. 1141, 17:1–9.
`
`
`13 Mr. Masding was part of Professor Bumby’s team at the University of
`Durham and a listed author on some of the Bumby references. See Exs.
`1106, 1107. Although the Masding Thesis is not a basis for the instituted
`ground, it is offered as relevant evidence to corroborate certain testimony of
`the declarants and to indicate the level of skill in the art.
`
`16
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`
`
`Nonetheless, Paice contests that a skilled artisan would have
`
`combined the Bumby references, arguing that Bumby IV and V “teach
`
`away” from Bumby II and III. PO Resp. 15–21. According to Paice,
`
`Bumby IV and V teach an “arbitrary speed-based mode controller” that
`
`would be incompatible, or “impractical,” for use with the “sub-optimal
`
`control strategy” taught by Bumby II and III. PO Resp 16–18. But the mere
`
`disclosure of more than one design in a prior art reference does not
`
`constitute a teaching away if “such disclosure does not criticize, discredit, or
`
`otherwise discourage” one design over the other. In re Fulton, 391 F.3d
`
`1195, 1201 (Fed. Cir. 2004).
`
`
`
`Here, although Bumby V describes the use of two control strategies, it
`
`explains clearly that one is for purposes of initial testing while the other is
`
`for actual use in the hybrid vehicle. More specifically, the “arbitrary [speed-
`
`based] strategy,” Bumby V acknowledges, “is intended purely to
`
`demonstrate” that the “more sophisticated [control] strategy” of Bumby II
`
`and III is capable of being implemented on a hybrid vehicle. Ex. 1107, 19
`
`(emphasis added). In other words, Bumby V is simply teaching how to test,
`
`and prove, the feasibility of the sub-optimal control strategy taught earlier by
`
`Bumby II and III, rather than criticizing or disparaging it. And, contrary to
`
`Paice’s protest, we credit the testimony of Ford’s declarant, Dr. Davis, that
`
`nowhere does Bumby V characterize the sub-optimal control algorithm as
`
`inadequate or inoperable. Ex. 1140 ¶¶ 23–32.
`
`
`
`Paice continues to protest the combination, proffering the testimony of
`
`its declarant, Mr. Hannemann, that “it was not technically feasible to
`
`implement” the sub-optimal control strategy of the Bumby references due to
`
`potential problems with “gear shifting.” PO Resp. 18–19 (citing Ex. 2102
`
`17
`
`

`
`IPR2014-00579
`Patent 7,104,347 B2
`
`¶¶ 66–68). But, upon further questioning, Mr. Hannemann clarified that the
`
`“gear shifting” problem was merely “a challenge” that Professor Bumby and
`
`his team were “trying to tackle.” Ex. 1141, 56:14–17. Simply because a
`
`prior art reference recognizes a problem, and discusses the work to solve it,
`
`does not necessarily teach away from what the reference otherwise discloses,
`
`for it is still “prior art for all that it teaches.” Beckman Instruments v. LKB
`
`Produkter AB, 892 F.2d 1547, 1551 (Fed. Cir. 1989).
`
`
`
`Moreover, rather than criticizing the sub-optimal control strategy
`
`taught by the Bumby references, the Masding Thesis (proffered by Paice)
`
`provides encouragement that corrections to the implementation software will
`
`alleviate the gear-shifting problem:
`
`Once correct action of the component controllers and
`
`associated sequencing logic had been demonstrated with the
`speed based mode strategy, the logical extension is to introduce
`a mode control strategy aimed at maximizing vehicle efficiency.
`To do this the sub-optimal controller, devised in previous work
`at Durham, is most appropriate. At this point however the
`necessary software to implement such control has not been
`perfected, specifically problems have arisen in avoiding
`excessive numbers of gear shifts.
`
`Ex. 2104, 240 (emphasis added). That passage suggests that, while not yet
`
`“perfected,” the

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