Google LLC v. Koninklijke Philips N.V.

CourtCourt of Appeals for the Federal Circuit
DecidedJanuary 6, 2020
Docket19-1234
StatusUnpublished

This text of Google LLC v. Koninklijke Philips N.V. (Google LLC v. Koninklijke Philips N.V.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Google LLC v. Koninklijke Philips N.V., (Fed. Cir. 2020).

Opinion

NOTE: This disposition is nonprecedential.

United States Court of Appeals for the Federal Circuit ______________________

GOOGLE LLC, Appellant

v.

KONINKLIJKE PHILIPS N.V., Appellee ______________________

2019-1234 ______________________

Appeal from the United States Patent and Trademark Office, Patent Trial and Appeal Board in Nos. IPR2017- 00386, IPR2017-01766. ______________________

Decided: January 6, 2020 ______________________

ANDREW V. TRASK, Williams & Connolly LLP, Washing- ton, DC, argued for appellant. Also represented by AARON P. MAURER, KEVIN HARDY, DAVID M. KRINSKY.

JUSTIN J. OLIVER, Venable LLP, Washington, DC, ar- gued for appellee. ______________________

Before LOURIE, BRYSON, and TARANTO, Circuit Judges. 2 GOOGLE LLC v. KONINKLIJKE PHILIPS N.V.

TARANTO, Circuit Judge. Koninklijke Philips N.V. owns U.S. Patent No. RE44,913, which concerns device keypads that provide both primary and secondary characters associated with particular keys. After Philips sued Acer Inc. and other companies, alleging infringement based on devices that use Google operating systems, Google Inc. petitioned the Pa- tent and Trademark Office, naming Acer and others as real parties in interest, to institute an inter partes review of claims 1 and 3–16 of the ’913 patent for obviousness under 35 U.S.C. § 103. The PTO’s Patent Trial and Appeal Board, acting on behalf of the PTO’s Director, see 37 C.F.R. §§ 42.4, 42.108, instituted the requested review. In Sep- tember 2018, the Board issued a final written decision con- cluding that Google had failed to prove obviousness. Acer Inc. v. Koninklijke Philips Electronics N.V., No. IPR2017- 00386, 2018 WL 4657646 (P.T.A.B. Sept. 26, 2018). Google appeals. Philips’s claimed invention differs in at most one way from the specific method (and related de- vice) described in the principal prior-art reference featured in Google’s petition. With that prior-art method, primary and secondary characters are associated with a given key; the secondary characters are presented to a user when the key is held for an extended time; and after the user chooses a secondary character for entry, that character is substi- tuted for the primary character on the key. The last step is the only difference from Philips’s claimed invention, in which the default primary character is retained on the key after secondary-character selection. That return-to-default option is what the prior-art reference itself compares its own character-substitution option to when touting its solu- tion as enhancing efficiency. We conclude, on the record of this case, that the Philips invention would have been obvi- ous in light of the prior art. We therefore reverse the Board’s decision. GOOGLE LLC v. KONINKLIJKE PHILIPS N.V. 3

I The ’913 patent, titled “Text Entry Method and Device Therefor,” is a reissue of U.S. Patent No. 6,885,318. The patent describes a method for entering primary and sec- ondary characters on the keypad of a device such as a handheld mobile device. ’913 patent, col. 2, lines 20–37. According to the patent, traditional mobile device keypads used one of two methods for entering characters: multitap or predictive text. In the multitap method, each key on the mobile device keypad is associated with multiple charac- ters. To select a character, the user repeatedly presses a key to cycle through the key’s associated characters until the desired character is located. Id., col. 1, lines 46–48. The multitap method, the ’913 patent explains, is “slow and prone to error” because the method “often requires more than two key taps to select a character.” Id., col. 1, lines 63–67. In the predictive-text method, predictive-text soft- ware alters the layout of a dynamic, touch-sensitive display by determining the “next most likely character required by the user.” Id., col. 2, lines 6–11. But predictive-text key- pads present “an unfamiliar interface to the average user” and require “much practice and learning for proficient and quick text entry.” Id., col. 2, lines 11–17. The ’913 patent seeks to improve these methods by providing a keypad that is familiar to users and also allows for improved character entry. ’913 patent, col. 2, lines 20– 24. Each key on the keypad is associated with a primary character and a number of secondary characters. Id., col. 3, lines 27–28. In its default state, each key displays its primary character. Id., col. 2, lines 30–32. To select a pri- mary character, the user performs a “quick tap[]” on the key. Id., col. 6, lines 3–6. To select a secondary character, the user selects the key associated with the desired second- ary character for “a period longer than [a] predetermined time period.” Id., col. 6, line 61 through col. 7, line 3. This action causes the device to display a menu of secondary characters. The user then taps the desired secondary 4 GOOGLE LLC v. KONINKLIJKE PHILIPS N.V.

character to select it. Id., col. 2, lines 35–37. After the sec- ondary character is selected, “the keypad . . . is returned to the default display state,” i.e., each key displays its pri- mary character. Id., col. 3, lines 60–62; id., col. 2, line 37. The patent includes three independent claims that are at issue in this appeal: claims 1, 3, and 4. Claim 1, which is illustrative, recites: 1. A method for inputting a character to a device, the device including a keypad, the keypad includ- ing a plurality of keys, at least one of the keys has a primary character, a plurality of secondary char- acters and an associated display area, the keypad in a default state displaying the primary character associated with the at least one key in the associ- ated display area, the method comprising acts of: in the default state, returning the primary character as an input character in response to selection of the at least one key for a period shorter than a predeter- mined time period; switching to a second state after detecting a first key selection of the at least one key for a period longer than the predetermined time pe- riod; in the second state displaying each of the secondary characters associated with the first selected key in a respec- tive display area; detecting a second key selection; selecting for the input character the second- ary character associated with the second key se- lection; and returning the keypad to the default state. GOOGLE LLC v. KONINKLIJKE PHILIPS N.V. 5

Id., col. 6, line 48 through col. 7, line 3 (bracketed material omitted) (emphasis added). Claims 3 and 4 are similar to claim 1, except that claim 3 claims a computer program product that executes the method of claim 1, and claim 4 claims the device described in claim 1. Id., col. 7, line 11 through col. 8, line 5. In the inter partes review at issue here, Google chal- lenged claims 1 and 3–16 of the ’913 patent as unpatenta- ble for obviousness, stating two (related) grounds: obviousness over an English translation of Japanese Pa- tent Application No. 2000–148366 to Sakata (Sakata II); and obviousness over Sakata II in view of U.S. Patent No. 6,094,197 to Buxton (Buxton). The Board determined that Google failed to prove unpatentability on either ground. Acer, 2018 WL 4657646, at *1, *12. Google timely appealed. We have jurisdiction under 28 U.S.C. § 1295(a)(4)(A). Google asserts that claim 1 is representative and seeks reversal as to all challenged claims based on arguments fo- cused on claim 1. Philips does not dispute the representa- tiveness of claim 1, and it makes no argument against reversal as to all challenged claims if reversal is warranted as to claim 1, as we conclude it is.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

KSR International Co. v. Teleflex Inc.
550 U.S. 398 (Supreme Court, 2007)
Perfect Web Technologies, Inc. v. InfoUSA, Inc.
587 F.3d 1324 (Federal Circuit, 2009)
Belden Inc. v. Berk-Tek LLC
805 F.3d 1064 (Federal Circuit, 2015)
Investpic LLC v. International Business Machines Corp.
816 F.3d 1352 (Federal Circuit, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
Google LLC v. Koninklijke Philips N.V., Counsel Stack Legal Research, https://law.counselstack.com/opinion/google-llc-v-koninklijke-philips-nv-cafc-2020.