throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`
`
`
`
`BAYERISCHE MOTOREN WERKE AKTIENGESELLSCHAFT &
`BMW OF NORTH AMERICA, LLC,
`Petitioners
`
`v.
`
`PAICE LLC & THE ABELL FOUNDATION, INC.
`Patent Owners
`
`
`
`
`
`
`
`
`
`
`
`Inter Partes Review No.: To Be Assigned
`
`U.S. Patent No. 8,630,761
`
`___________________
`
`
`PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 8,630,761 UNDER
`35 U.S.C. § 311 AND 37 C.F.R. § 42.100
`
`
`
`

`

`
`
`Table of Contents
`
`Petition
`U.S. Patent No. 8,630,761
`
`Page
`
`“controls operation … responsive to said derived near-term
`predicted pattern” / “predictively controls operation …
`
`Introduction .................................................................................................. 1
`I.
`Overview of the ’761 Patent ......................................................................... 2
`II.
`A.
`The Specification and the Challenged Claims ..................................... 2
`B.
`File History ......................................................................................... 6
`C.
`Relevant Prior IPRs Invalidating Claims Based on Severinsky ........... 8
`D.
`Person of Ordinary Skill in the Art (“POSA”) ................................... 10
`III. Claim Construction ..................................................................................... 10
`A.
`“derives a predicted/predicts a near-term pattern of operation” ......... 10
`B.
`responsive to said predicted near-term pattern of operation” ............. 12
`C.
`“road load”........................................................................................ 13
`IV. Statutory Grounds of Challenge .................................................................. 15
`V. Overview of the Technology ....................................................................... 15
`Background of the Art ...................................................................... 15
`A.
`Severinsky – U.S. Patent No. 5,343,970............................................ 16
`B.
`C.
`Quigley, et al..................................................................................... 17
`D. Nii – U.S. Patent No. 5,650,931 ........................................................ 18
`E.
`Graf – U.S. Patent No. 6,188,945 ...................................................... 19
`VI. Detailed Explanation of the Challenge ........................................................ 19
`A. Ground 1 – Claims 1-12 are Obvious Over Severinsky in View
`of Quigley ......................................................................................... 19
`1.
`Claim 1 ...................................................................................19
`2.
`Claim 2 ...................................................................................35
`3.
`Claim 3 ...................................................................................36
`4.
`Claim 4 ...................................................................................36
`5.
`Claim 5 ...................................................................................39
`
`Quigley – “Predicting the Use of a Hybrid Electric Vehicle”
`
`i
`
`

`

`
`
`B.
`
`C.
`
`Petition
`U.S. Patent No. 8,630,761
`
`Ground 2 – Claims 1-12 are Obvious Over Severinsky in View
`
`Claim 6 ...................................................................................47
`6.
`Claim 7 ...................................................................................49
`7.
`Claim 8 ...................................................................................49
`8.
`Claim 9 ...................................................................................50
`9.
`10. Claim 10 .................................................................................50
`11. Claim 11 .................................................................................50
`12. Claim 12 .................................................................................50
`of Nii ................................................................................................ 50
`1.
`Claim 1 ...................................................................................50
`2.
`Claim 2 ...................................................................................56
`3.
`Claim 3 ...................................................................................56
`4.
`Claim 4 ...................................................................................57
`5.
`Claim 5 ...................................................................................58
`6.
`Claim 6 ...................................................................................59
`7.
`Claim 7 ...................................................................................61
`8.
`Claim 8 ...................................................................................62
`9.
`Claim 9 ...................................................................................62
`10. Claim 10 .................................................................................62
`11. Claim 11 .................................................................................62
`12. Claim 12 .................................................................................62
`Severinsky in view of Graf ............................................................... 63
`1.
`Claim 1 ...................................................................................63
`2.
`Claim 2 ...................................................................................69
`3.
`Claim 5 ...................................................................................70
`4.
`Claim 6 ...................................................................................72
`5.
`Claim 7 ...................................................................................73
`6.
`Claim 8 ...................................................................................74
`
`Ground 3 – Claims 1-2, 5-8, 11-12 are Obvious Over
`
`ii
`
`

`

`
`
`Petition
`U.S. Patent No. 8,630,761
`
`Claim 11 .................................................................................74
`7.
`Claim 12 .................................................................................74
`8.
`VII. Mandatory Notices Under 37 C.F.R. §42.8 ................................................. 74
`Real Parties-in-Interest ...................................................................... 74
`A.
`Related Matters ................................................................................. 74
`B.
`Identification of Counsel and Service Information ............................ 75
`C.
`VIII. Grounds for Standing and Procedural Statement (37 C.F.R.
`§42.104(a)) ................................................................................................. 75
`IX. Payment of Fees (37 C.F.R. §§42.103 and 42.15(a)(1)) .............................. 76
`Conclusion .................................................................................................. 76
`X.
`Claim Appendix of Challenged Claims ................................................................. 77
`Certification of Word Count ................................................................................. 83
`Certificate of Service ............................................................................................ 84
`
`
`
`
`
`iii
`
`

`

`
`
`
`Exhibit No.
`
`BMW1001
`
`BMW1002
`
`BMW1003
`
`BMW1004
`
`BMW1005
`
`BMW1006
`
`BMW1007
`
`BMW1008
`
`Petition
`U.S. Patent No. 8,630,761
`
`LIST OF EXHIBITS
`
`Description of Exhibit
`
`U.S. Patent No. 8,630,761
`
`USPTO Assignments on the Web for U.S. Patent No.
`7,104,347 K2
`
`Ford Motor Co. v. Paice LLC, IPR2014-00571, Paper 44,
`Final Written Decision (P.T.A.B. Sep. 28, 2015)
`
`Ford Motor Co. v. Paice LLC, IPR2014-00579, Paper 45,
`Final Written Decision (P.T.A.B. Sep. 28, 2015)
`
`Paice LLC v. Ford Motor Co., Appeal Nos. 2016-1412, -
`1415, -1745, Doc. 46-2, Opinion (Fed. Cir. Mar. 7, 2017)
`
`Ford Motor Co. v. Paice LLC, IPR2015-00794, Paper 31,
`Final Written Decision (P.T.A.B. Nov. 1, 2016)
`
`Paice LLC v. Ford Motor Co., Appeal Nos. 2017-1442, -
`1443, Doc. 59-2, Opinion (Fed. Cir. Feb. 1, 2018)
`
`Declaration of Dr. Gregory W. Davis in Support of Inter
`Partes Review of U.S. Patent No. 8,630,761
`
`BMW1009
`
`Curriculum Vitae of Dr. Gregory W. Davis, Ph.D., P.E.
`
`BMW1010
`
`BMW1011
`
`BMW1012
`
`BMW1013
`
`BMW1014-
`BMW1019
`
`Ford Motor Co. v. Paice LLC, IPR2015-00795, Paper 31,
`Final Written Decision (P.T.A.B. Nov. 1, 2016)
`
`Ford Motor Co. v. Paice LLC, IPR2014-00884, Paper 38,
`Final Written Decision (P.T.A.B. Dec. 10, 2015)
`
`RESERVED
`
`U.S. Patent No. 5,343,970 (“Severinsky”)
`
` RESERVED
`
`iv
`
`

`

`
`Exhibit No.
`
`BMW1020
`
`BMW1021
`
`BMW1022
`
`BMW1023
`
`BMW1024
`
`BMW1025
`
`Petition
`U.S. Patent No. 8,630,761
`
`Description of Exhibit
`
`U.S. Patent No. 6,188,945 (“Graf”)
`
`RESERVED
`
`U.S. Patent No. 5,650,931 (“Nii”)
`
`Innovations in Design: 1993 Ford Hybrid Electric Vehicle
`Challenge, Society of Automotive Engineers, SAE/SP-
`94/980, Davis, G.W. et al., “United States Naval
`Academy, AMPhibian” (Feb. 1994), 277-87
`
`1996 Future Car Challenge, Society of Automotive
`Engineers, SAE/SP-97/1234, Swan, J. et al., “Design and
`Development of Hyades, a Parallel Hybrid Vehicle for the
`1996 FutureCar Challenge” (Feb. 1997), 23-30
`
`1997 Future Car Challenge, Society of Automotive
`Engineers, SAE/SP-98/1359, Swan, J. et al., “Design and
`Development of Hyades, a Parallel Hybrid Electric
`Vehicle for the 1997 FutureCar Challenge” (Feb. 1998),
`29-39
`
`BMW1026
`
`RESERVED
`
`BMW1027
`
`BMW1028
`
`BMW1029
`
`BMW1030
`
`Wakefield, E.H., Ph.D., History of the Electric Automobile
`– Hybrid Electric Vehicles, Society of Automotive
`Engineers, SAE/SP-98/3420 (1998), 17-34 (Chapter 2:
`The History of the Petro-Electric Vehicle)
`
`Unnewehr, L.E. et al., “Hybrid Vehicle for Fuel
`Economy,” Society of Automotive Engineers, SAE/SP-
`76/0121 (1976)
`
`Burke, A.F., “Hybrid/Electric Vehicle Design Options and
`Evaluations,” Society of Automotive Engineers, SAE/SP-
`92/0447, International Congress & Exposition, Detroit,
`Michigan (Feb. 24-28, 1992)
`
`Duoba, M, “Challenges for the Vehicle Tester in
`Characterizing Hybrid Electric Vehicles,” 7th CRC On
`Road Vehicle Emissions Workshop, San Diego, California
`
`v
`
`

`

`
`Exhibit No.
`
`BMW1031
`
`BMW1032
`
`BMW1033
`
`BMW1034
`
`Petition
`U.S. Patent No. 8,630,761
`
`Description of Exhibit
`(Apr. 9-11, 1997)
`
`Electric and Hybrid Vehicles Program, 18th Annual
`Report to Congress for Fiscal Year 1994, U.S. Department
`of Energy (Apr. 1995)
`
`Bates, B. et al., “Technology for Electric and Hybrid
`Vehicles,” Society of Automotive Engineers, SAE/SP-
`98/1331 (Feb. 1998)
`
`Stodolsky, F. et al., “Strategies in Electric and Hybrid
`Vehicle Design,” Society of Automotive Engineers,
`SAE/SP-96/1156, Kozo, Y. et al., “Development of New
`Hybrid System – Dual System,” SAE/SP-96/0231 (Feb.
`1996), 25-33
`
`Leschly, K.O., Hybrid Vehicle Potential Assessment,
`Volume 7: Hybrid Vehicle Review, U.S. Department of
`Energy (Sep. 30, 1979)
`
`BMW1035
`
`RESERVED
`
`BMW1036
`
`BMW1037-
`BMW1038
`
`BMW1039
`
`BMW1040
`
`BMW1041
`
`Masding, P.W., et al., “A microprocessor controlled
`gearbox for use in electric and hybrid-electric vehicles,”
`Transactions of the Institute of Measurement and Control,
`Vol. 10, No. 4 (July –Sep. 1988), 177-86
`
`RESERVED
`
`Davis, G.W., Ph.D. et al., Introduction to Automotive
`Powertrains, Chapter 2: Road Loads (2000), 27-68
`
`Ehsani, M. et al., “Propulsion System Design of Electric
`Vehicles,” Texas A&M University, Department of
`Electrical Engineering (1996), 7-13
`
`Ehsani, M. et al., “Propulsion System Design of Electric
`and Hybrid Vehicles,” IEEE Transactions on Industrial
`Electronics, Vol. 44, No. 1 (Feb. 1997), 19-27
`
`vi
`
`

`

`
`Exhibit No.
`
`BMW1042
`
`BMW1043
`
`BMW1044
`
`BMW1045-
`BMW1051
`
`BMW1052
`
`BMW1053
`
`BMW1054
`
`BMW1055
`
`BMW1056
`
`BMW1057
`
`BMW1058
`
`
`
`Petition
`U.S. Patent No. 8,630,761
`
`Description of Exhibit
`
`Bauer, H., ed., Automotive Handbook, Robert Bosch
`Gmbh (4th Ed. Oct. 1996), Excerpts
`
`Design Innovations in Electric and Hybrid Electric
`Vehicles, Society of Automotive Engineers, SAE/SP-
`96/1089, Anderson, C., et al., “The Effects of APU
`Characteristics on the Design of Hybrid Control Strategies
`for Hybrid Electric Vehicles,” SAE/SP-95/0493 (Feb.
`1995), 65-71
`
`U.S. Patent No. 5,656,921 (“Farrall”)
`
`RESERVED
`
`File History for U.S. Patent No. 8,630,761
`
`USPTO Assignments on the Web for U.S. Patent No.
`8,630,761
`
`“Predicting the Use of a Hybrid Electric Vehicle” Quigley,
`et al. (“Quigley”)
`
`Declaration of Sylvia Hall-Ellis, Ph.D.
`
`U.S. Patent No. 5,189,621 (“Onari”)
`
`U.S. Patent No. 4,625,697 (“Hosaka”)
`
`U.S. Patent No. 5,533,583 (“Adler”)
`
`
`vii
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`Pursuant to 35 U.S.C. §311 and 37 C.F.R. §42.100, Petitioners Bayerische
`
`Motoren Werke Aktiengesellschaft and BMW of North America, LLC (“BMW”)
`
`request inter partes review (“IPR”) of Claims 1-12 (the “Challenged Claims”) of
`
`U.S. Patent No. 8,630,761 (“’761 Patent”) (BMW1001). The ’761 Patent is
`
`assigned to Paice LLC and the Abell Foundation, Inc. (“Patent Owners”) per
`
`United States Patent and Trademark Office (“PTO”) assignment records.
`
`BMW1002; BMW1053.
`
`I.
`
`Introduction
`
`Despite containing a lengthy specification describing a hybrid vehicle
`
`topology and control scheme, the purportedly novel feature of the ’761 Patent
`
`claims is predicting a near-term pattern of operation of the hybrid vehicle and
`
`controlling the hybrid vehicle in response thereto. But that feature, which is
`
`disclosed only generally in a few passages in the specification, is not new.
`
`Numerous prior art references—not before the PTO during examination of the ’761
`
`Patent—expressly disclose analyzing a driver’s operation of the vehicle to predict
`
`travel patterns in order to optimize the control strategy for hybrid vehicles. One
`
`reference used in the challenge herein, Quigley, is actually titled “Predicting the
`
`Use of a Hybrid Electric Vehicle.” Applying such optimization techniques to
`
`increase efficiency of hybrid vehicles, which is described as a goal across the prior
`
`art, would have been obvious to a person of skill in the art.
`
`1
`
`

`

`II. Overview of the ’761 Patent
`
`Petition
`U.S. Patent No. 8,630,761
`
`
`A. The Specification and the Challenged Claims
`
`The ’761 Patent specification is directed to purported improvements in
`
`hybrid vehicles. BMW1001, 1:16-19. Some of those improvements were
`
`allegedly made over U.S. Patent No. 5,343,970 (“Severinsky”), which is discussed
`
`extensively throughout the specification and issued to one of the named inventors
`
`here. See, e.g., id., 10:16-11:12. Nevertheless, in six IPRs on related patents, the
`
`Board and Federal Circuit found that Severinsky anticipates or renders obvious
`
`numerous claims to the allegedly “improved” hybrid vehicle and control scheme.
`
`The bulk of the ’761 Patent specification is directed to an alleged “new
`
`‘topology’ for a hybrid vehicle” that required “two” motors and an engine. Id.,
`
`11:25-45. For background information on the two-motor topology, Figure 3,
`
`reproduced below, shows one such embodiment, with a starting motor 21 in green,
`
`a traction motor 25 in blue, and an internal combustion engine 40 in red.
`
`2
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`
`
`BMW1001, 25:29-50. This two-motor hybrid vehicle was said to be an
`
`improvement over the “one-motor” hybrid vehicle already disclosed by
`
`Severinsky. Id., 16:59-65; 25:4-6. The claims in the ’761 Patent, however, do not
`
`claim a two-motor design. Each challenged claim requires only a single motor
`
`configuration, which the ’761 Patent admits already existed in Severinsky.
`
`The ’761 Patent specification describes a number of operating modes to best
`
`control operation of the hybrid vehicle, including a “low-load mode” in which the
`
`vehicle is propelled only by the electric motor, a “highway cruising mode” in
`
`3
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`which the vehicle is propelled only by the engine, and an “acceleration mode” in
`
`which the vehicle is propelled by both the engine and the electric motor.
`
`BMW1001, 35:1-48. A microprocessor determines the mode of operation based
`
`on road load. Id. If the road load is below a setpoint (or “transition point”), the
`
`vehicle operates in the motor only mode; if the road load is between the setpoint
`
`and the maximum torque output of the engine, the vehicle operates in the engine
`
`only mode; if the road load is above the maximum torque output of the engine, the
`
`vehicle operates in the motor/engine mode. Id., 35:1-48, 39:42-47. But the ’761
`
`Patent admits that these features were also not new in view of Severinksy, which
`
`disclosed operating hybrid vehicles in different modes depending on the torque
`
`required, the state of charge of the batteries, and other variables. Id., 34:10-15.
`
`The only aspect of challenged claims 1-12 that the ’761 Patent specification
`
`does not admit to be disclosed in the prior-art Severinsky reference (as confirmed
`
`in the file history, which is discussed below), relates to using driving pattern data
`
`to enhance control of a hybrid vehicle. The ’761 Patent specification references
`
`that feature in a few locations within the specification, and only at a high level of
`
`generality. See BMW1001, 39:48-67; 40:41-43; 43:7-22. In particular, the
`
`specification explains that the microprocessor can monitor a vehicle’s operation
`
`over a period of time to alter the vehicle’s setpoint in response to a repetitive
`
`driving pattern. Id., 39:48-51. As an example, the specification states that an
`
`4
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`operator may drive the same route from a congested suburban development to a
`
`workplace at about the same time every morning, and it may be beneficial to adjust
`
`the engine/motor transition point to prevent repetitive engine starts that would
`
`otherwise occur in suburban traffic. Id. Notably, the specification also recognizes
`
`that “how” to record and analyze patterns and adapt a control strategy would
`
`essentially be a simple task, because it states that it was “within the skill of the art
`
`to program a microprocessor to record and analyze such daily patterns, and to
`
`adapt the control strategy accordingly.” Id., 39:58-61.
`
`The challenged claims are recited fully in the Claims Appendix, including an
`
`identification of the subparts referenced throughout this petition. Independent
`
`claims 1 and 7 both relate to a method of operation of a hybrid vehicle including
`
`numerous steps, generally summarized as follows:
`
`[a] storing and supplying electrical power from a battery bank;
`
`[b] applying torque to road wheels from an engine or a motor;
`
`[c] controlling flow of torque between the engine, motor, and wheels;
`
`[d] controlling flow of electrical power between the battery bank and motor
`
`employing a controller;
`
`[e] the controller derives/predicts a near-term pattern of operation of the
`
`hybrid vehicle by monitoring operation of the hybrid vehicle;
`
`5
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`[f] controlling the motor or engine for propulsion in response to the
`
`derived/predicted near-term pattern.
`
`Steps [a] to [d] refer to well-known features included in many single motor
`
`hybrid vehicle control systems in the prior art, such as Severinsky.
`
`Steps [e] and [f], which were distinguished by Applicants over Severinsky as
`
`discussed below, were, however, also well-known features taught in multiple prior
`
`art references, such as Quigley, Nii, and Graf used in the challenges here.
`
`The dependent claims add details concerning alterations to the known
`
`control schemes based on such pattern data.
`
`B.
`
`File History
`
`The ’761 Patent issued from U.S. Patent Application No. 13/573,728, which
`
`was filed on October 5, 2012. The ’761 Patent claims priority to a lengthy chain of
`
`parent non-provisional and provisional patent applications, dating back to
`
`September 14, 1998.
`
`In response to a rejection under 35 U.S.C. §102(b) over Severinsky,
`
`Applicants amended the claims and disputed the presence of what would become
`
`parts [e] and [f] of eventually issued claims 1 and 7 (pending claims 17 and 23,
`
`respectively). Specifically, Applicants argued that Severinsky did not disclose
`
`using predicted patterns to enhance its control scheme:
`
`6
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`[I]ndependent claims 17 and 23 [(issued claims 1 and 7)] have
`
`both been amended hereby to recite that the controller performs
`
`the separate steps of monitoring vehicle operation to derive a
`
`predicted pattern of operation, and then controlling vehicle
`
`operation accordingly. [Severinsky] discloses only that the
`
`vehicle is operated in different modes responsive to vehicle
`
`speed, makes this mode determination strictly in real time, and
`
`says nothing about predicting a pattern of operation, and
`
`altering vehicle operation accordingly.
`
`BMW1052, 58.1 Accordingly, Applicants limited the scope of the claims to
`
`require that the controller control the vehicle based on predicted pattern
`
`information instead of making determinations strictly in real time. Applicants
`
`further argued that Severinsky is different from the amended claims because the
`
`control scheme is not based on actual driver behavior but on predetermined
`
`settings:
`
`Further, [Severinsky] says nothing about the controller
`
`performing the step of monitoring vehicle operations in order to
`
`derive a predicted pattern or anticipate a pattern of operation of
`
`the vehicle. That is, as noted by the Examiner, highway
`
`operation and operation in traffic are predictable modes of
`
`operating any vehicle, and therefore any vehicle must be
`
`
`1 All emphasis added unless otherwise indicated.
`
`7
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`designed to accomplish both properly. But in this case, it is the
`
`vehicle designer who anticipates highway and low-speed
`
`driving, and incorporates the necessary components into the
`
`vehicle to permit the vehicle to perform in both modes.… This
`
`is very different from the vehicle’s controller monitoring
`
`operation of the particular vehicle and using this data to predict
`
`future operational patterns accordingly, as claimed.
`
`Id. In other words, Patent Owner distinguished a general-purpose control strategy
`
`selected by the vehicle designer (manufacturer) to cover known modes of operation
`
`for any hybrid vehicle from an optimized intelligent control strategy for a
`
`particular hybrid vehicle based on how a driver actually operates that particular
`
`vehicle.
`
`In response to the claim amendments and arguments, the Examiner issued a
`
`Notice of Allowance. Id., 24.
`
`C. Relevant Prior IPRs Invalidating Claims Based on Severinsky
`
`U.S. Patent No. 7,104,347 (“’347 Patent”), which is a parent of the ’761
`
`Patent containing the same disclosure, has been the subject of eight previous IPRs
`
`8
`
`

`

`in which 30 of 322 challenged claims were found invalid based upon a variety of
`
`Petition
`U.S. Patent No. 8,630,761
`
`
`different references.3 The Final Written Decision (“FWD”) in IPR2014-00571
`
`specifically determined that numerous claims were invalid as obvious over
`
`Severinsky in view of secondary references. BMW1003. The Federal Circuit
`
`affirmed that decision. BMW1005.
`
`U.S. Patent No. 7,237,634, which also stems from the ’347 patent and
`
`contains the same disclosure, as well as over 300 claims, has been the subject of 26
`
`previous IPRs, many of which found numerous claims invalid based upon a variety
`
`of different references. The FWDs in IPR2014-00904; IPR2014-01416; IPR2015-
`
`00758; IPR2015-00785; IPR2015-00801 specifically determined Severinsky
`
`rendered obvious numerous claims in view of secondary references. The Federal
`
`Circuit affirmed each of those decisions.
`
`
`2 The two claims not found unpatentable recited “monitoring patterns of vehicle
`
`operation,” but those IPRs were not based on Severinsky or any of the secondary
`
`references used in this Petition. Instead, the challenger relied upon references that
`
`the Board found to only monitor the vehicle battery’s state of charge for patterns,
`
`rather than a driver’s operation. The Grounds presented herein have no such issue.
`
`3 Petitioners have also recently filed IPR2020-00994 on the ’347 Patent, which is
`
`currently pending.
`
`9
`
`

`

`Person of Ordinary Skill in the Art (“POSA”)
`
`Petition
`U.S. Patent No. 8,630,761
`
`
`D.
`
`A POSA in the art of the ’761 Patent would have either: (1) a graduate
`
`degree in mechanical, electrical or automotive engineering with at least some
`
`experience in the design and control of combustion engines, electric or hybrid
`
`electric vehicle propulsion systems, or design and control of automotive
`
`transmissions, or (2) a bachelor’s degree in mechanical, electrical or automotive
`
`engineering and at least five years of experience in the design of combustion
`
`engines, electric vehicle propulsion systems, or automotive transmissions.
`
`BMW1008, ¶¶43-46.
`
`III. Claim Construction
`
`In an inter partes review, claim terms “shall be construed using the same
`
`claim construction standard that would be used to construe the claim in a civil
`
`action.” 37 C.F.R. §42.100(b); Phillips v. AWH Corp., 415 F.3d 1303, 1313 (Fed.
`
`Cir. 2005). Except as discussed below, the terms in the Challenged Claims should
`
`have their plain and ordinary meaning for purposes of this IPR proceeding.
`
`A.
`
`“derives a predicted/predicts a near-term pattern of operation”
`
`Claims 1 and 7 both essentially recite a “predicted near-term pattern of
`
`operation” (or very similar variant) in claim elements [1e], [1f] and [7e], [7f].
`
`Petitioners propose that the phrase be construed to mean “expected
`
`upcoming vehicle operation based on past repetitive driver behavior.” This
`
`10
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`construction flows from the claim language itself, as well as the specification,
`
`which refers to monitoring the vehicle’s operation over a period of days or weeks
`
`to determine repetitive driving patterns, such as when an operator drives the same
`
`route to the workplace every morning. BMW1001, 39:49-61. The ’761 Patent
`
`specification explains that “in response to recognition of a regular pattern,” the
`
`transition point for the control strategy may be altered. Id., 39:58-67; see also id.,
`
`43:15-22. Petitioner’s construction is also consistent with the file history which
`
`distinguished the identified prior art on the basis that this claim term requires the
`
`prediction of future operation based on monitored driver behavior. See Section
`
`II.B. It is also consistent with the ordinary understanding of a POSA. BMW1008,
`
`¶¶157-58.
`
`Notably, in a prior IPR on the parent ’347 Patent, Patent Owners argued for
`
`a construction of the related phrase “monitoring patterns of vehicle operation over
`
`time” to mean “monitoring a driver’s repeated driving operations over time.”
`
`BMW1011, 11-13. The Board agreed with Patent Owners’ proposed construction.
`
`Id. That construction is also consistent with the one proposed herein by
`
`Petitioners.
`
`Petitioners do note that claim 1 recites “deriv[ing] a predicted near-term
`
`pattern of operation, whereas claims 7 recites “predict[ing] a near-term pattern of
`
`operation.” However, there does not appear to be a substantive difference between
`
`11
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`those requirements. Indeed, the ’761 Patent specification’s cursory discussion of
`
`altering the control strategy based on pattern data does not describe any
`
`differences. See BMW1001, 39:48-67; 40:41-43; 43:7-22. Nor does the file
`
`history indicate any differences when these limitations were introduced by
`
`amendment, but treats the claims the same when distinguishing over the prior art.
`
`BMW1052, 57-59. Particularly, Applicants stated that pending claim 17 [issued
`
`claim 1] and 23 [issued claim 1] have “both been amended hereby to recite that the
`
`controller performs the separate steps of monitoring vehicle operation to derive a
`
`predicted pattern of operation, and then controlling vehicle operation
`
`accordingly.” Id., 58.
`
`In view of the above, the slight difference in wording in claims 1 and 7 does
`
`not lead to any different constructions across the claims.
`
`B.
`
`“controls operation … responsive to said derived near-term
`predicted pattern”
`/ “predictively controls operation …
`responsive to said predicted near-term pattern of operation”
`
`Part [f] of claim 7 is the same as part [f] of claim 1 except for minor
`
`variations. Claim 7 requires that the system “predictively controls operation,”
`
`whereas claim 1 requires that the system “controls operation.” Since claim 1
`
`requires that the system “controls operation” based upon the “predicted pattern of
`
`operation,” there does not appear to be any difference in the control requirements
`
`12
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`imposed by claim 7’s requirement of “predictive control.” Simply, both claims
`
`require control based on near-term predicted patterns.
`
`The ’761 Patent specification’s cursory discussion of altering the control
`
`strategy based on pattern data does not describe any differences between predictive
`
`control and control in view of predicted pattern data. See BMW1001, 39:48-67;
`
`40:41-43; 43:7-22. Also, as noted previously, when amending the claims to
`
`include these limitations, Applicants stated that pending claim 17 [issued claim 1]
`
`and 23 [issued claim 1] have “both been amended hereby to recite that the
`
`controller performs the separate steps of monitoring vehicle operation to derive a
`
`predicted pattern of operation, and then controlling vehicle operation
`
`accordingly.” BMW1052, 58. Applicants also presented identical arguments to
`
`distinguish the prior art for both claims. Id., 57-59.
`
`Accordingly, the “controls operation” language of claim 1 and “predictive
`
`control” language of claim 7 should be construed consistently across both claims to
`
`require that the control of the hybrid vehicle be reflective of the “predicted near-
`
`term pattern of operation.”
`
`C.
`
`“road load”
`
`The term “road load” appears in dependent claims 4-6 and 10-12. The
`
`Board has previously construed that term in two slightly different ways when
`
`construing the parent ’347 Patent, and those constructions should apply here. See
`
`13
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`Elkay Mfg. Co. v. Ebco Mfg. Co., 192 F.3d 973, 980 (Fed. Cir. 1999) (“When
`
`multiple patents derive from the same initial application, the prosecution history
`
`regarding a claim limitation in any patent that has issued applies with equal force
`
`to subsequently issued patents that contain the same claim limitation.”).
`
`Specifically, the term “road load” was construed in several IPRs to mean the
`
`“amount of instantaneous torque required for propulsion of the vehicle,” and that
`
`construction was expressly considered and affirmed by the Federal Circuit.
`
`BMW1003, 8, 11; BMW1004, 8, 11; BMW1005.4 The Board considered the
`
`term’s “ordinary and customary meaning…as understood by [a POSA] reading the
`
`patent’s entire written disclosure.” BMW1003, 5; BMW1004, 5-6; BMW1011, 6.
`
`Petitioners adopt this construction of the Board for consistency with those prior
`
`constructions in the parent ’347 Patent, and the concurrently pending IPR2020-
`
`
`4 In a few other FWDs on the ’347 Patent (as well as in certain FWDs on the
`
`related ’634 Patent) the Board similarly construed “road load” to mean “the
`
`amount of instantaneous torque required to propel the vehicle, be it positive or
`
`negative.” BMW1006, 9, 12; BMW1010, 8- 9; BMW1011, 7, 10. Those
`
`constructions were also affirmed by the Federal Circuit. BMW1005; BMW1007.
`
`There is no substantive difference between the two sets of constructions, and either
`
`would be acceptable. BMW1008, ¶159.
`
`14
`
`

`

`Petition
`U.S. Patent No. 8,630,761
`
`
`00994 on the ’347 Patent.
`
`IV. Statutory Grounds of Challenge
`
`Ground Basis
`
`1
`
`2
`
`3
`
`Claims 1-12: obvious over Severinsky in view of Quigley
`
`Claims 1-12: obvious over Severinsky in view of Nii
`
`Claims 1-2, 5-8, 11-12: obvious over Severinsky in view of Graf
`
`
`V. Overview of the Technology
`
`A. Background of the Art
`
`For more than 100 years, numerou

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