- Google LLC / Cellco Partnership D/B/A Verizon Wireless et al. v. Headwater Research LLCAll claims unpatentablePTAB · Oct 1, 2025 · IPR2024-00943 · APJ Scott B Howard · IPR · Final written decision
Claims 2–23, 26, 41–60, 63, 64, 91–152, and 155–171 are unpatentable; Rao anticipates some claims, and the stated Rao combinations render the remaining claims obvious.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner argues that a person having ordinary skill in the art “would have at least a bachelor’s degree in computer science, computer engineering, or a similar field, and approximately two years of industry or academic experience in a field related to computer software development and/or computer networking.” Pet. 2 (citing Ex. 1015 ¶¶ 50–52). Petitioner further argues that “[w]ork experience can substitute for education, and additional education can substitute for work experience.” Id. at 2–3 (citing Ex. 1015 ¶¶ 50–52). Because Petitioner’s proposed level of ordinary skill in the art is consistent with the field of the invention of the ’541 patent and not disputed by Patent Owner (see PO Resp.), we adopt Petitioner’s formulation of the person having ordinary skill in the art.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“Petitioner states “[n]o terms require construction to resolve this Petition.” Pet. 3. Patent Owner does not propose any claim constructions. See PO Resp. For the purposes of this Decision, we need not expressly construe any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 13
- Expert testimonyPetitioner expert creditedDecided for petitioner
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“preponderance of the evidence that claim 3 was anticipated by Rao.” slip op. at 25
Patent outcomesUS 8,589,541 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,589,541 - Google LLC / Cellco Partnership D/B/A Verizon Wireless et al. v. Headwater Research LLCAll claims unpatentablePTAB · Oct 1, 2025 · IPR2024-00942 · APJ Scott B Howard · IPR · Final written decision
Claims 2–23, 26, 41–60, 63, 64, 91–152, and 155–171 are unpatentable; Rao anticipates some claims, and Rao-based combinations render the others obvious.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner argues that a person having ordinary skill in the art “would have at least a bachelor’s degree in computer science, computer engineering, or a similar field, and approximately two years of industry or academic experience in a field related to computer software development and/or computer networking.” Pet. 2 (citing Ex. 1015 ¶¶ 50–52). Petitioner further argues that “[w]ork experience can substitute for education, and additional education can substitute for work experience.” Id. at 2–3 (citing Ex. 1015 ¶¶ 50–52). Because Petitioner’s proposed level of ordinary skill in the art is consistent with the field of the invention of the ’541 patent and not disputed by Patent Owner (see PO Resp.), we adopt Petitioner’s formulation of the person having ordinary skill in the art.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner states “[n]o terms require construction to resolve this Petition.” Pet. 3. Patent Owner does not propose any claim constructions. See PO Resp. For the purposes of this Decision, we need not expressly construe any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 13
- Expert testimonyOther
“157, and 171 are anticipated by Rao. Pet. 1, 19–39, 42. Petitioner’s arguments are supported by citations to the prior art and the testimony of Dr. Wolfe. See id. We have reviewed Petitioner’s arguments and evidence, agree with them, and, therefore, adopt Petitioner’s arguments and evidence as our own.” slip op. at 26
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“anticipated by Rao. Pet. 1, 30–31, 33–42. We have reviewed Petitioner’s arguments for each of those dependent claims. See Pet. 30–31, 33–42. For each of those dependent claims, the Petition appears to only argue a theory of obvious. That is, the Petition never states that the additional limitation is disclosed by Rao. See id. For example, claim 26 depends from claim 1 and further recites “wherein the policy is based on a background service class.” Ex. 1001, 112:49–52. We reproduce Petitioner’s arguments directed to claim 26 below: Rao’s policies 520 may “define prioritization” for network packets “based on whether an application is running in the foreground or the background.” [Ex. 1002] ¶ 182; id. ¶¶ 38–43, 180, 182, 188–89, 193, Figs. 5A, 5B. Each packet “may be placed and arranged in a priority order respective to all other . . . packets to provide a packet by packet prioritization across all applications 338a-338n and . . . network packets.” Id. ¶ 191. It would have been obvious to determine and apply a policy assigning a specific priority to packets associated with background applications, supra [1e]-[1f], and Rao thus discloses or renders obvious assigning a priority to network communications based on whether they are characterized as background services (class of services associated with application(s) running in the background of client 105), EX-1015 ¶¶195-96; supra [1e], [1f]. Pet. 33–34. Although the Petition sets forth why the claim limitation would have been obvious, there is no discussion as to how the additional limitation of claim 26—policy based on background class—is disclosed in Rao. See id. Similar arguments are presented for the other claims. See Pet. 30–31, 35–42. Because the Petition does not sufficiently show how the additional limitations recited in claims 20, 26, 58, 64, 165, and 169 were disclosed by Rao, Petitioner has not shown by a preponderance of the evidence that claims 20, 26, 58, 64, 165, and 169 were anticipated by Rao.” slip op. at 28
Patent outcomesUS 8,589,541 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,589,541 - PLR Worldwide Sales Ltd. v. Flip Phone Games, Inc.Some claims unpatentablePTAB · Apr 24, 2025 · IPR2024-00209 · APJ Scott B Howard · IPR · Final written decision
Claims 1–11 and 13–19 are unpatentable as obvious over Ho and Aoki; claims 12 and 20 were not shown unpatentable over Jiau and Aoki or Jiau and Kim.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner argues for a slightly different level of ordinary skill in the art: “a bachelor’s degree in electrical engineering, computer engineering, computer science, or a similar field, along with one to two years of experience developing or programming video games or video game systems, or similar types of computer systems.” PO Resp. 2 (citing Ex. 2006 ¶ 29). Patent Owner further argues that the person having ordinary skill in the art “may have additional education that might substitute for some of the experience, and additional experience might substitute for some of the educational background.” Id. (citing Ex. 2006 ¶ 29). According to Patent Owner, Petitioner’s proposal does not require experience in programming video games. Id. at 3. However, Patent Owner states, “[t]his difference does not materially affect the analysis presented below.” Id. We see very little difference between the parties’ respective proposals. We adopt Patent Owner’s marginally more specific proposal. Additionally, because we would reach the same conclusions under Petitioner’s proposal, we agree with Patent Owner that this does not affect our analysis.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Patent Owner argues that the plain and ordinary meaning of “downloading” excludes “real-time fetching of data by a client from a server system.” PO Resp. 34; see also PO Sur-reply 16–17; Tr. 32:22–34:7. Because we need not expressly construe any claim terms, we do not construe any terms of the ’662 patent. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co. Matal, 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 11
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedReference is prior artDecided for petitioner
“date of the ’662 patent, Ho is not a “printed publication” within the meaning of 35 U.S.C. § 311(b). PO Resp. 30–33; PO Sur-reply 15–16. The Federal Circuit has rejected this argument, holding that: a published patent application is, by its literal terms, a “printed publication.” So, when § 311(b) permits IPR challenges based upon “prior art . . . printed publications,” it includes within its literal scope challenges based upon a published patent application. And, by virtue of § 102(e)(1), a published patent application—this specific type of “printed publication”—is deemed prior art as of its filing date. Therefore, the plain language of §§ 311(b) and 102(e)(1) permits IPR challenges based upon published patent applications, and such published patent applications can be deemed prior art in IPRs as of their filing date. Lynk Labs, Inc. v. Samsung Elecs. Co., 125 F.4th 1120, 1127 (Fed. Cir. 2025). Thus, Petitioner asserts permissible grounds of unpatentability under 35 U.S.C. § 311(b) by arguing that claims 1–20 are unpatentable under 35 U.S.C. § 103(a) on the basis of Ho, which is a prior art printed publication, and either Aoki or Kim.” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“A person having ordinary skill in the art would have combined Aoki’s teaching of using user-identification information as part of the request for an advertisement with Ho’s system, which also teaches a client device sending information to a server to request hot spot information, such as advertisements. See Ex. 1003 ¶¶ 103–107, 111, 114, 117. Because both Ho and Aoki are directed to improvements in game design and monetization from using advertisements (id. ¶ 106; Ex. 1004, 1:26–28; Ex. 1005 ¶¶ 6–8), a person having ordinary skill in the art would have looked at both Ho and Aoki and combined the relevant features with a reasonable expectation of success (Ex. 1003 ¶¶ 103, 106, 117). A person having ordinary skill in the art would have appreciated that using Aoki’s teaching of sending user-identification information with Ho, which includes sending information with a request for information relating to interactive information elements (hot spots), allows for targeted advertisements, which was a known advantage in advertising. Id. ¶ 117; Ex. 10089 ¶¶ 54–55 (describing advantages of targeted advertising).” slip op. at 26
Patent outcomesUS 9,427,662 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,427,662 - Ingenico Inc. v. Ioengine, LLCSome claims unpatentablePTAB · Sep 21, 2020 · IPR2019-00879 · APJ Sheila F Mcshane · IPR · Final written decision
Claims 1, 2, 4–8, 13–16, 19–21, 24, 25, and 27–29 are unpatentable as anticipated by Iida; claims 3, 10–12, and 26 were not shown unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art In the Decision on Institution, we determined that Petitioner’s proposed description of the qualifications of a person of ordinary skill in the art aligned with the technology and claims of the ’969 patent. Inst. Dec. 24. Patent Owner does not challenge this determination and states that it has applied the Board’s adopted definition of one of ordinary skill in the art. PO Resp. 2. Dr. Butler testifies that the adopted level of art in the art would not have any effect on the opinions presented in his declaration, even though Dr. 6 Available at https://www.uspto.gov/sites/default/files/documents/ tpgnov.pdf. Butler had previously presented a different proposed qualifications. Ex. 2011 ¶ 13. Accordingly, for the reasons given in the Decision on Institution, we adopt Petitioner’s proposed level of ordinary skill, which is that a person of ordinary skill in the art should have:” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther
“1. “interactive user interface” In the Decision on Institution, we construed the term “interactive user interface” (“IUI”) as “a display with which a user may interact to result in the portable device taking action responsively.” Inst. Dec. 19. The parties have presented additional arguments in additional briefing on the term’s construction, which we have further considered, and, as discussed below, we modify the interpretation of the term. See PO Resp. 7–16; Pet. Reply 1–3. a. Petitioner’s Assertions In the Petition, Petitioner asserts that the term “interactive user interface” should be interpreted as “a display with which a user may interact to result in the computer taking action responsively.” Pet. 14. Petitioner argues that this proposed interpretation is consistent with the plain and ordinary meaning of the term. Id. at 13. Petitioner also contends that although the term “interactive user interface” is not used in the ’969 patent specification, the specification consistently describes the terminal output component as a “display mechanism,” and the interactive user interface is presented on the terminal output component in the claims. Id. (citing Ex. 1001, 4:40). Petitioner contends that a number of displays in the ’969 patent respond to text inputs from an input component to elicit a responsive action, and refers to an example of the input of registration information in screen 515 in Figure 5, where, if the input is successful, follow-up screen 517 is produced, but otherwise there is an error message. Id. at 13–14 (citing Ex. 1001, 9:52–54, 7:53–56). In its Reply, Petitioner asserts that the ordinary meaning of the term “interactive user interface” is “a presentation (display) with which a user may interact to result in the computer (portable device) taking action responsively.” Pet. Reply 1. This is similar to the construction that Petitioner previously proposed in the Petition, however, Petitioner now proposes that the “computer” can be considered to be a “portable device,” and a “display” can also be considered to be a “presentation. See Pet.14. According to Petitioner, the claims require that the interactive user interface be presented on the terminal output component. Pet. Reply 1. Petitioner argues that the specification describes that it is a portable device that responds to user interaction with the IUI, such as the interaction with a login screen text box. Id. at 2 (citing Ex. 1046, 52:11–55:13; Ex. 1001, 7:55–56). Petitioner asserts that the claims require that it is the portable device that responds to user interaction, with the “fourth program code” executing in response to user interaction with the interactive user interface. Id. Petitioner compares the claim of the parent ’047 patent, which was narrowed to refer to “the interactive user interface is configured to enable the user to cause the portable device processor to execute program code stored on the portable device memory,” to the claims here. Id. Petitioner also asserts that “‘[p]resentation’ is used and described in the ’969 patent as corresponding to a ‘display.’” Id. at 1.” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“2. Analysis A claim is unpatentable under 35 U.S.C. § 102 if a prior art reference” slip op. at 32
- Obviousness (§103) › Objective indicia / secondary considerationsNot reached
“obviousness, we need not determine whether Patent Owner’s evidence of objective indicia of nonobviousness weighs even further against a conclusion of obviousness. See Hamilton Beach Brands, Inc. v. f’real Foods, LLC, 908 F.3d 1328, 1343 (Fed. Cir. 2018) (holding, in affirming Board decision determining that petitioner had not shown unpatentability, that “objective indicia of nonobviousness” “need not [be] addressed” because the court “affirmed the Board’s findings regarding the failure of the prior art to teach or suggest all [claim] limitations”); Palo Alto Networks, Inc. v. Finjan, Inc., 748 F. App’x 317, 324 (Fed. Cir. 2018) (non-precedential) (affirming Board decision holding that petitioner failed to establish unpatentability due to a lack of disclosure of a claim limitation, without reaching secondary considerations, and holding that “it was not necessary for the Board to consider” expert testimony “limited to the issue of secondary considerations”).” slip op. at 78
Patent outcomesUS 9,059,969 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,059,969 - Ingenico Inc. v. Ioengine, LLCSome claims unpatentablePTAB · Sep 21, 2020 · IPR2019-00929 · APJ Elizabeth M Roesel · IPR · Final written decision
Claims 55, 57–63, 67–72, 74, 77, 78, 81–87, 89, 92–98, 100, 103, 104, 106–112, 116–121, 123, and 126–129 are unpatentable; the remaining challenged claims were not shown unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“the Board’s adopted definition of a POSITA. PO Resp. 3; Ex. 2139 ¶¶ 12, 13. Both parties’ experts state, however, that their opinions would not change based upon which party’s definition of a POSITA is adopted. Ex. 2139 ¶ 13; Ex. 2110, 240:24–241:6.” slip op. at 14
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“For these reasons, we find that Petitioner has shown by a” slip op. at 40
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentable
“meet claims 74, 89, 100, and 123 because Davis “does not have two different devices on the client side.” PO Resp. 63–64. Patent Owner’s argument does not persuasively rebut Petitioner’s obviousness case, which relies on Iida, not Davis, to teach two devices on the client side—Iida’s digital camera 12 (a portable device) and terminal 14. Pet. 13–16, 60; Ex. 1003 ¶ 57, Figs. 1A, 1B. Furthermore, in Petitioner’s combination, a digital certificate is substituted for Iida’s user ID and password. Pet. 61. Patent Owner does not dispute Petitioner’s contention that Iida discloses transmitting a user ID and password stored in memory 48 of camera 12 to image server 18 through terminal 14. Id. at 43–44 (addressing claim 71; citing Ex. 1003 ¶¶ 110, 113). Accordingly, Petitioner persuades us that the combination of Iida and Davis discloses the limitations of claims 74, 89, 100, and 123 (and claims 71, 86, 97, and 120 from which they depend).” slip op. at 89
- Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia no nexusDecided for petitioner
“First, Patent Owner has not argued that the licensed products are coextensive with the claims of the ’703 Patent, accordingly, there is no presumption of a nexus. See Lectrosonics, Paper 33 at 33.” slip op. at 94
Patent outcomesUS 9,774,703 mixed§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,774,703 - Flir Systems, Inc. / Flir Maritime US, Inc. (F/K/A Raymarine, Inc.) v. Garmin Switzerland GmbHSome claims unpatentablePTAB · Jul 10, 2018 · IPR2017-00946 · APJ Scott B Howard · IPR · Final written decision
Claims 28, 29, and 45 were held unpatentable; claims 1–7, 12–23, 25–27, and 41–44 were not shown unpatentable. Substitute claims 73 and 74 were allowed.
RulingsFinal written decision- BurdenFwd mixedMixed
“C. Legal Principles 1. Anticipation A patent claim is unpatentable under 35 U.S.C. § 102 if “the four corners of a single, prior art document describe every element of the claimed invention, either expressly or inherently, such that a person of ordinary skill in the art could practice the invention without undue experimentation.” Advanced Display Sys., Inc. v. Kent State Univ., 212 F.3d 1272, 1282 (Fed. Cir. 2000). “A single prior art reference may anticipate without disclosing a feature of the claimed invention if such feature is necessarily present, or inherent, in that reference.” Allergan, Inc. v. Apotex Inc., 754 F.3d 952, 958 (citing Schering Corp. v. Geneva Pharm., 339 F.3d 1373, 1377 (Fed. Cir. 2003)). Moreover, the reference must also “disclose[] within the four corners of the document not only all of the limitations claimed but also all of the limitations arranged or combined in the same way as recited in the claim.” Net MoneyIN, Inc. v. Verisign, Inc., 545 F.3d 1359, 1371 (Fed. Cir. 2008). However, “the reference need not satisfy an ipsissimis verbis test.” In re Gleave, 560 F.3d 1331, 1334 (Fed. Cir. 2009). We analyze the ground based on anticipation in accordance with the above-stated principles.” slip op. at 22
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“and agree with Patent Owner that the terms “re-routing the course” and “re-route the course” mean “to change at least a portion of the route of the course relative to a previous routing.” That is, there must be a first routing of a course and that routing must be changed by performance of the marine route calculation algorithm to avoid preselected conditions by identifying one or more non-user selected waypoints. The construction is consistent with the words of the claims. The claims do not merely require routing a course, but “re-routing the course.” The ordinary meaning of the prefix “re” is that something is being done again. See Tr. 18 (Petitioner agreeing that “if you put R-E in front of a word, normally that means it’s occurring a second time”). Although the claims do not explicitly recite both an original “routing” of a course that is changed by “re-routing the course,” the original “routing” is implicitly required by the use of the prefix “re.” See Tr. 34 (Patent Owner agreeing that although the claims do not explicitly require an initial routing, the initial routing is implicit in the use of “re-routing”), 44–45 (Petitioner agreeing that “re-routing” ordinarily implies an initial routing).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“proposed construction of “course” as “the path of intended travel of a craft with respect to the earth.” Instead, we need only focus on the words recited in the claim. Claim 1, which is representative, recites that performing the marine route calculation algorithm to “route a course between a first location and the potential waypoint avoiding the preselected conditions,” where such performance includes “identifying one or more non-user selected waypoints.” Ex. 1001, claim 1. The other independent claims recite similar limitations. See Ex. 1001, claims 12, 20, 27. Based on the limitation recited in the claim, the broadest reasonable interpretation of routing a “course” encompasses the identification of one or more non-user selected waypoints between a first location and a potential waypoint. No further construction is necessary for purposes of this Decision.” slip op. at 17
- Skill levelSkill level petitioner adoptedDecided for petitioner
“We are persuaded by Petitioner’s argument that the person of ordinary skill in the art need not have first-hand experience with marine navigation devices and systems. Pet. Reply 25–26. The ’703 patent explicitly defines “marine navigation” broadly, noting that “the use of the word ‘marine’ in the embodiments of the present invention (including the claims) could be replaced with the phrase ‘non-street based.’” Ex. 1001, 1:57–67 (emphasis added). Such non-street based navigation is broad enough to encompass avionic navigation. See Pet. Reply 25–26; cf. Ex. 1003, 4–7 (demonstrating Dr. Braasch’s experience in avionic navigation). We find that Petitioner’s definition is supported by the testimony of its expert, Dr. Braasch, and, for the reasons stated above, we are not persuaded that the person of ordinary skill in the art necessarily would have had first-hand experience in marine—as opposed to non-street based— navigation. We, therefore, determine, based on the complete record, that Petitioner’s proposed definition correctly states the level of ordinary skill in the art, and we apply it for purposes of this Decision.7, 8” slip op. at 24
Patent outcomesUS 7,268,703 mixedClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 7,268,703
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.