PTAB
Advanced fields
1 decision · 285msnewest first
  • PTAB · Oct 21, 2025 · IPR2024-00786 · APJ Frances L Ippolito · IPR · Final written decision

    Claims 10, 11, 13–16 were held unpatentable: claims 10, 11, 13, 15, and 16 as anticipated by Xiao, and claim 14 as obvious over Xiao and Singh.

    RulingsFinal written decision
    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

      “arguments, we agree with Patent Owner’s proposed construction that requires the server to conduct a compatibility check. We start with the express claim language. Claim 10 recites: determining, by the server, applicable settings for the selected vehicle, the applicable settings being settings that are preferred to be set as identified from the user profile and are compatible with settings that are settable in the selected vehicle. Ex. 1001, 33:10–14 (emphases added). The express claim language requires that the server determine applicable settings. Those applicable settings, determined by the server, must also be compatible with vehicle settings. As such, the plain and ordinary meaning of the claim language expressly requires that the server make a determination of applicable settings that are defined as being compatible with vehicle settings.” slip op. at 14

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “Petitioner contends that a person of ordinary skill in the art (“POSITA”) at the time of the invention of the ’268 patent “would have had at least a Bachelor’s degree in electrical engineering, computer science, or closely related field, with at least two-to-four-years-experience in cloud services for settings customization, or a Master’s degree in electrical engineering, computer science, or equivalent.” Pet. 12 (citing Ex. 1009 ¶ 82). Patent Owner does not address the level of ordinary skill in the art. See, generally PO Resp. For purposes of this Decision, we adopt Petitioner’s proposal because it is reasonable and consistent with the prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art may reflect an appropriate level of skill in the art).” slip op. at 12

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentableNot shown unpatentable

      “However, contrary to Dr. Almeroth’s testimony and Petitioner’s position, Xiao’s server already does not attempt to command vehicles to do things they cannot do. Xiao teaches that server 118 generates commands for command codes that exist and are settable in the vehicle. Ex. 1010 ¶¶ 102– 103. As such, if there is no corresponding automobile setting, then Xiao’s server would not list those command codes for retrieval and would not send a command based on that retrieved command code to control the automobile systems to achieve the operator’s desired settings because that command code is not in the database. Our understanding of Xiao is further supported by Dr. Almeroth’s testimony: By listing them in the table of automobile command code information 606, Xiao shows that there are particular settings compatible with particular automobiles and particular desired settings. Thus, Xiao demonstrates the necessarily present characteristic that certain settings (e.g., commands) are compatible with certain automobiles. Ex. 1009 ¶ 96 (emphases added). We note that Dr. Malek further explains “the nonsensical result achieved by the combination would be that Xiao’s server, at best, in response to the command request issued by the operator, could ‘look up’ a command code to apply a vehicle-specific setting to that automobile 112, only to find that there is ‘none.’” We agree with Dr. Malek that there is a “None” command code in Xiao’s database when Xiao’s database already stores settings that are known to be settable in a specific vehicle per the operator’s preferences. Ex. 2011 ¶ 135. Thus, based on the complete record, we determine that Petitioner has not demonstrated by a preponderance of the evidence that Xiao in combination with Hayashi render claim 10 obvious.” slip op. at 79

    • BurdenNot shown unpatentable

      “Anticipation is not an ipsissimis verbis test, but “[a] claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal, 814 F.2d at 631. Petitioner and Dr. Almeroth both acknowledge that Xiao discloses operators on the same account. Pet. 40–41; Ex. 1009 ¶ 170. But Petitioner and Dr. Almeroth do not explain sufficiently how Xiao discloses these operators have sub-user accounts. Petitioner further contends Xiao discloses plurality of accounts. Pet. Reply 18–19 (citing Ex. 1024, 33:1–44:10, 45:22–46:2); Ex. 1010 ¶ 65. Again, Petitioner has not adequately explained how the plurality of accounts includes sub-user accounts because Xiao discloses generally that multiple operators of a vehicle are on the same, single account. Ex. 1010 ¶ 66.” slip op. at 65

    Patent outcomesUS 9,171,268 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 9,171,268

Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.