US 6708214

I'll search for authoritative information on US 6708214, including any 2026 CAFC activity.

US Patent 6,708,214 — Summary

Important note on the search scope before the substance: I could not find, in the searches I was able to run, any CAFC 2026 docket or 2026 appellate activity involving patent 6,708,214. Search queries combining "6708214" with 2026 Federal Circuit / litigation terms returned general 2026 patent-litigation commentary (PTAB discretionary denial, Fintiv/NHK, Delaware/EDTX venue data, EcoFactor v. Google, etc.) and unrelated dockets — none referencing this patent. I therefore cannot confirm any 2026 CAFC proceeding, and I will not infer one. The only litigation records tied to this patent in the authoritative source material are the historical ones noted below.

Bibliographic data (per the Google Patents full text, and consistent with the USPTO-style fields)

Ownership chain (from recorded assignments): Phone.com, Inc. → Openwave Systems, Inc. (change of name) → Purple Labs S.A. (2008) → Myriad France SAS (merger, 2010) → Google Inc. (2010) → HTC Corporation (2011) → Google Inc. (2013) → Google LLC (2017).

Abstract (verbatim substance)

A mobile communication device operable to allow a user to access hypermedia content via a wireless link is configured to allow a user to more easily input hypermedia identifiers, such as URLs. The device includes a processor, a display, a set of user input keys each operable to input a predetermined numeral, and storage storing a microbrowser program. Also stored are a plurality of URL fragments, each associated with one of the user input keys. In response to a single predefined user input at a given key, the microbrowser selects the corresponding URL fragment and displays it. The user may then input additional characters appended to the selected fragment, or the fragment may be appended to previously input characters, forming a complete URL. The number of keystrokes required to input a complete URL is thereby reduced.

Independent claims — plain language

Claim 1 (method of operating a mobile telephone) — A two-part method:

1. Voice mode: the phone works as a phone, enabling two-way voice communication with a remote party over a wireless link.

2. Browser mode: the user can access remotely stored hypermedia content over that same wireless link, and this browser mode provides:

   • a number input mode (enter numerals via the keys);
   • an alphabetic input mode (enter letters via the keys);
   • storage of multiple hypermedia identifier fragments;
   • a mapping between each stored fragment and one of the input keys; and
   • a hypermedia identifier input mode that is separate from the number and alphabetic modes, in which a single key press selects and displays the corresponding stored fragment.

   The claim closes with the requirement that the selected fragment can be appended to a previously entered character string, or can have a subsequently entered string appended to it, to form at least a portion of the hypermedia identifier.

The practical thrust: a dedicated "URL mode" where one keypress inserts a whole common URL substring (e.g., "http://", ".com") instead of typing it character-by-character, with the inserted fragment concatenating with what was typed before and/or after.

Claim 4 (apparatus — mobile communication device) — The device counterpart of claim 1, comprising:

• a processor and a display;

• a set of input keys, each able to input a predetermined numeral, and operable to dial a telephone number;

• voice circuitry for telephonic communication over a wireless link; and

• a storage facility holding:

  • a microbrowser program executable by the processor to enable access to remotely stored hypermedia content, the microbrowser having multiple input modes including a number input mode, an alphabetic input mode, and a hypermedia identifier input mode separate from both;
  • a plurality of hypermedia identifier fragments;

  where the microbrowser includes instructions that, when in the hypermedia identifier input mode, cause the corresponding stored fragment to be displayed in response to a single user input at one of the keys.

Dependent claims (for completeness)

• Claim 2 (depends on 1): adds a symbol input mode, separate from number, alphabetic, and hypermedia identifier modes, for inputting non-numeric/non-alphabetic symbols.
• Claim 3 (depends on 1): the stored fragments are URI fragments.
• Claim 5 (depends on claim 4): adds the symbol input mode to the device claim.
• Claim 6 (depends on claim 4): the stored fragments are URI fragments.

Drafting oddity worth flagging: claims 5 and 6 are written as "A method as recited in claim 4…" even though claim 4 is an apparatus ("device") claim. That is an inconsistency in the printed claim language; interpreted literally, claims 5 and 6 purport to add limitations to the claim-4 device, but the introductory phrase says "method."

What the specification adds (context for claim construction)

• The "URL input mode" is one of four cycled modes (number, alphabetic, symbol, URL), selected by pressing a dedicated key (key 216); softkey identifiers show the current mode ("alpha", "URL 1", etc.).
• Selectable fragments expressly enumerated include: "http://", ".", "www.", "/", ".com", ".edu", ".bus", ".net", ".gov", ".wml", "https://", ".wmls", ".hdml", ".cgi", ".asp", "~", "?", etc.
• Multiple "URL input cards" can be paged through (key 220 shows a second card), so more fragments can be offered than there are keys.
• After a fragment is selected, the display automatically returns to alphabetic mode so the user can continue typing.
• Worked example: entering http://www.phone.com takes 11 keystrokes instead of 20.
• The background frames the problem: mobile devices generally lack a full keyboard, and characters like /, :, . have no natural phone-key equivalent.

Cited prior art (examiner-cited, 9 references)

US 5,721,897 (Rubinstein, 1998); US 5,801,691 (IBM, 1998); US 5,911,485 (Unwired Planet, 1999 — "Predictive data entry method for a keypad"); US 6,052,070 (Nokia, 2000); US 6,115,754 (Nortel, 2000); US 6,192,258 (Access Co., 2001); US 6,219,731 (Eatoni Ergonomics, 2001 — multi-tap text input); US 2001/0000668 A1 (Bodnar, 2001); US 6,519,241 (Nokia, 2003 — "Mobile telephone for internet-applications"). Non-patent citations include the UP.Browser User Handbook (Unwired Planet, Dec. 1998, pp. 15–20) and Phone.com "UP.Browser"/"UP Product Family" materials (Aug. 1999) — i.e., the applicant's own commercial microbrowser documentation was before the examiner.

Litigation

Per the source's litigation record (from Unified Patents / Darts-IP data surfaced on the Google Patents page), the patent's family was involved in:

• ITC — Investigation 337-TA-808; and
• D. Del. — Case 1:11-cv-00715.

These are consistent with the well-documented 2011 Apple–HTC dispute, in which HTC (then owner via the 2011 Google assignment) added US 6,708,214, among others, to its ITC complaint and its Delaware action against Apple. A corroborating Arabic-language news item in my search results describes HTC amending an ITC action and a Delaware case to add five patents, including "US 6708214 … 'hypermedia identifier input mode for a mobile communication device'."

Uncertainty I want to be explicit about: the specific procedural dispositions of 337-TA-808 and 1:11-cv-00715 as to this particular patent (whether it was asserted to final decision, dropped, settled, or terminated) are not established by the material I retrieved, and I am not asserting an outcome. More importantly, I found no evidence of any 2026 CAFC docket entry for 6,708,214; given the patent expired on 2020-04-21 with all maintenance fees paid (4th, 8th, 12th year), active 2026 appellate litigation over it would be unusual, though I cannot rule it out on the basis of the searches available to me.

Sources

• Google Patents full text and bibliographic/litigation data: https://patents.google.com/patent/US6708214/en (and https://patents.google.com/patent/US6708214)
• EP 2 728 836 A1 (BlackBerry, "Electronic device with predictive URL domain key function") search report cites US 6 708 214 B1 (La Fleur), 2004-03-16, as category A relevant to claims 1–15: https://patentimages.storage.googleapis.com/ea/8d/58/1d948e9150f671/EP2728836A1.pdf
• Darts-IP family litigation link (family ID 31947068) and Unified Patents litigation records for ITC 337-TA-808 and D. Del. 1:11-cv-00715, as surfaced on the Google Patents page.
• Secondary corroboration of HTC's addition of this patent to its ITC/Delaware actions: https://itwadi.com/node/1976

If you need a definitive, current answer on USPTO assignment/status and any 2026 appellate docket, the authoritative checks would be USPTO Patent Center / Assignment Search and the Federal Circuit's PACER/opinion docket — which I was not able to query directly here.

I'll research litigation involving US patent 6708214. Let me run several targeted searches.

Let me dig into the specific cases referenced for this patent.

Let me get more detail on the Delaware case and check for any other suits involving this patent.

Litigation involving U.S. Patent No. 6,708,214

Patent identified: U.S. 6,708,214 B1, "Hypermedia identifier input mode for a mobile communication device," filed 2000‑04‑21, granted 2004‑03‑16, inventor James P. La Fleur. (Note the Google Patents page renders the number variously as "6,708,214" and "6708214" — same patent, "the '214 patent.")

Two litigation matters are documented for the '214 patent. Both arose out of the HTC–Apple smartphone patent war. I found no other litigation.

1. HTC Corp. v. Apple Inc. — U.S. International Trade Commission, Inv. No. 337‑TA‑808

• Plaintiff/Complainant: HTC Corp. (Taiwan)
• Defendant/Respondent: Apple Inc. (Cupertino, CA)
• Jurisdiction: U.S. International Trade Commission (Section 337 investigation)
• Case number: 337‑TA‑808, "Certain Electronic Devices with Communication Capabilities, Components Thereof, and Related Software"
• Filing date: Complaint filed August 16, 2011; amended complaint September 7, 2011; supplements September 2, 19, and 23, 2011. Investigation instituted September 26, 2011 (notice published September 30, 2011, 76 FR 60870).
• Patents asserted: U.S. 7,765,414; 7,417,944; 7,672,219; 6,708,214; 6,473,006; 7,289,772; 6,868,283; and 7,020,849. The '214 patent is expressly named in the Commission's Notice of Institution.
• ALJ: Thomas B. Pender (some sources also reference Judge Gildea in later phases/proceedings)
• Outcome/status: Terminated / closed following settlement. The parties reached a global settlement announced in November 2012 (a 10‑year cross‑license was reported). The Unified Patents litigation record lists the matter as Closed, with a termination date of 2013‑01‑10; one Taiwanese government compilation lists the termination date as 2013‑01‑14, result "consolidated settlement (和解)." No appeal.

Sources:

• ITC Notice of Institution (337‑TA‑808, Sept. 27, 2011): https://www.usitc.gov/secretary/fed_reg_notices/337/337_808_notice09272011sgl.pdf
• Federal Register notice (76 FR 60870, Sept. 30, 2011): https://regulations.justia.com/regulations/fedreg/2011/09/30/2011-25279.html
• Unified Patents litigation page: https://portal.unifiedpatents.com/litigation/International%20Trade%20Commission/case/337-TA-808
• Google Patents "Family has litigation" entry for this patent: https://portal.unifiedpatents.com/litigation/International%20Trade%20Commission/case/337-TA-808 (linked from https://patents.google.com/patent/[US6708214](/patent/US6708214)/en)
• Finnegan (counsel for HTC) experience page: https://www.finnegan.com/en/work/experience/certain-electronic-devices-with-communication-capabilities-components-thereof-and-related-software-htc-v-apple-337-ta-808-itc.html

Note on standing dispute: In this investigation Apple moved for partial termination on the ground that the "Google Patents" — including the '214 patent, which HTC acquired from Google by a Patent Purchase Agreement dated August 29, 2011 — were not transferred with "all substantial rights," so that HTC allegedly lacked standing. HTC and the ITC Staff briefed the issue (Order No. 15). The record I reviewed does not conclusively establish the ultimate disposition of that specific motion before the global settlement resolved the case.

2. HTC Corp. v. Apple Inc. — U.S. District Court for the District of Delaware

• Plaintiff: HTC Corp. (a/k/a High Tech Computer Corp.), with HTC (B.V.I.) Corp., HTC America, Inc., and Exedea, Inc. in related HTC filings
• Defendant: Apple Inc.
• Jurisdiction: U.S. District Court for the District of Delaware
• Case number: 1:11‑cv‑00715‑GMS (Judge Gregory M. Sleet)
• Filing date: August 15–16, 2011 (Reuters and contemporaneous press reports describe "Tuesday's complaint," August 16, 2011; a Taiwanese government table lists August 15, 2011)
• Patents asserted: The original complaint asserted three patents — U.S. 7,765,414; 7,417,944; and 7,672,219 (two of which HTC had purchased from ADC Telecommunications in April 2011). An amended complaint (Doc. 7, filed September 6, 2011) added the "Google Patents" obtained from Google in August 2011, which include U.S. 6,708,214, along with 6,473,006; 6,868,283; 7,289,772; and 7,020,849. The '214 patent therefore entered the Delaware action via the amended pleading.
• Relief sought: Injunction against importation/sale of Apple products (Mac, iPhone, iPad, iPod, Apple TV, AirPort/Time Capsule wireless devices), compensatory damages, treble damages for willful infringement.
• Outcome/status: Closed / settled. The case was resolved as part of the global HTC–Apple settlement (cross‑license) announced in November 2012; the corresponding ITC investigation terminated in January 2013. Unified Patents lists the matter as closed (termination date November 15, 2012 in its docket, "closed" status).

Sources:

• Reuters/press coverage naming the case as Delaware No. 11‑00715: https://indianexpress.com/article/news-archive/web/taiwans-htc-sues-apple-over-patents/ and https://financialpost.com/technology/taiwans-htc-sues-apple-over-patents
• Amended complaint, Case 1:11‑cv‑00715‑GMS, Doc. 7 (Sept. 6, 2011): https://www.scribd.com/doc/64207015/9-7-HTC-Amended-Complaint-Against-Apple
• Unified Patents-related docket reference (1:11‑cv‑00715 as related case): https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1:10-cv-00166
• Google Patents "Family has litigation" Delaware entry: https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A11-cv-00715 (linked from https://patents.google.com/patent/US6708214/en)

Other notes

• Related but distinct HTC–Apple matters (not asserting the '214 patent): Apple Inc. v. HTC Corp., D. Del. No. 1:10‑cv‑00166‑RK, and the companion ITC investigations 337‑TA‑704/710 (mobile OS and user‑interface patents). These are related to the HTC–Apple conflict but the '214 patent was not among the patents asserted there.
• The Google Patents record states the family has litigation and points to Darts‑ip as a "First worldwide family litigation filed" source: https://patents.darts-ip.com/?family=31947068 — I was unable to independently verify any additional family litigation through that link.
• Current patent status: Expired — Lifetime. Anticipated expiration April 21, 2020. Ownership chain (per assignment records): Phone.com, Inc. → Openwave Systems, Inc. → Purple Labs S.A. → Myriad France SAS → Google Inc. → HTC Corporation (2011) → Google Inc. (2013) → Google LLC (2017). Current assignee of record: Google LLC.

Confidence and caveats

• I have high confidence that 337‑TA‑808 (ITC) asserted U.S. 6,708,214 — the Commission notice names it explicitly.
• I have moderate confidence that the '214 patent was formally part of the Delaware action 1:11‑cv‑00715, because it was added to the set of asserted patents by the September 6, 2011 amended complaint; my sources confirm the case number, parties, jurisdiction, and the addition of the Google patents, but I did not retrieve the full PACER docket to confirm that the '214 patent was never dropped before dismissal. A PACER/docket check of 1:11‑cv‑00715‑GMS would resolve this.
• No litigation outside the HTC–Apple dispute (e.g., by Openwave, Purple Labs, Myriad, or Google as patentee) was found; if any exists it did not surface in these searches.

I did not auto-correct any identifiers; all patent numbers and case numbers are reproduced as found in the sources.

I'll start by verifying the structured block's default ("no PTAB activity") against live sources, since PTAB data can lag in ODP.

Initial searches returned nothing on-topic. Let me probe the known litigation and any PTAB filings tied to it.

Confirmed the ITC/HTC-Apple litigation story. Now let me specifically hunt for any AIA trial filings (IPR/PGR/CBM) that ODP might have missed.

PTAB / AIA Trial Report — U.S. Patent No. 6,708,214

Patent: "Hypermedia identifier input mode for a mobile communication device" (La Fleur; filed 2000-04-21; granted 2004-03-16; 6 claims)
Prosecution/post-grant assignee chain: Phone.com → Openwave Systems → Purple Labs → Myriad France → Google Inc. → HTC Corp. → Google Inc. → Google LLC
Statutory status: Expired (anticipated expiration 2020-04-21; Google Patents lists "Expired – Lifetime")

Proceedings overview

There are zero AIA trial proceedings on file for U.S. Patent No. 6,708,214 — no IPR, no PGR, and no CBM — which means no claim of the patent has ever been canceled or confirmed by the PTAB, the patent stands wholly untested at the Board, and a defendant's defensive posture rests entirely on the district-court/ITC record and on § 102/§ 103 art that was never run through an AIA trial.

I flag this deliberately: the outcome "no proceedings" is the affirmative finding here, not an absence of research. The structured ODP block supplied with this task returns no AIA trials, and independent web searching surfaced no petition, institution decision, or FWD naming the '214 patent. I cannot prove a negative with certainty (a very early, long-closed CBM or IPR could in principle fall outside the aggregators I could reach), but there is no affirmative evidence of any PTAB filing, and I found none in any of the following:

• PTAB docket/decision aggregators (Unified Patents litigation portal, PTAB petition mirrors)
• Text searches pairing "6,708,214" / "6708214" with IPR / PGR / CBM / "post-grant review"
• Text searches on the patent title ("Hypermedia identifier input mode")
• The patent's own Google Patents page, which lists only litigation references and no "PTAB" or "AIA trial" entries (contrast: patents that were IPR'd carry a Board proceedings table)

Because there is nothing to sequence, the per-proceeding template below is replaced with (a) the reason no proceeding exists — the real story of this patent is its ITC standing wipeout — and (b) the resulting defensive/estoppel picture.

(The only proceedings ever recorded against the claimed subject matter were the ITC and district-court actions arising from HTC's 2011 assertion of the patent against Apple. Those are Article III / § 337 actions, not AIA trials, but they materially change the enforcement story and are flagged here for completeness.)

No PTAB proceeding — but the patent's one enforcement attempt died on standing

• Where asserted: ITC Inv. No. 337-TA-808, HTC Corp. v. Apple Inc. (asserted claims: claims 1–3 of the '214 patent), plus a companion District of Delaware case, 1:11-cv-00715.
• How the '214 patent got there: HTC acquired the patent from Google on 2011-08-29 (assignment recorded 2011-09-01) and amended its ITC complaint on 2011-09-07 to add the '214 patent. ITC instituted the investigation 2011-09-26 (Federal Register notice published 2011-09-30).
• Disposition of the '214 patent in the ITC: On 2012-06-08, ALJ Thomas Pender issued Order No. 15, granting Apple's motion to terminate the investigation as to the '214 (and '006, '283, '772, and '849) patent(s) for lack of standing — i.e., a defect in HTC's substantive rights as a Google assignee, not a merits ruling that the claims are invalid. HTC petitioned for Commission review on 2012-06-27; the Commission declined review, so the termination stood. The '214 patent therefore never reached a merits determination anywhere — it was dismissed on a threshold, case-specific ground.
• Why no IPR followed: Once the '214 patent was out of the ITC and its Delaware companion on standing grounds, no party had the incentive to fund an IPR. Apple already had the win it needed. The patent later expired on 2020-04-21, removing any practical reason to file.
• Defensive value: Because the '214 patent was knocked out on standing rather than on the merits, nothing about its claim validity has ever been adjudicated — by the PTAB or a district court. A defendant today cannot point to any agency or court ruling that claims 1–6 are invalid. Conversely, this patent has also never been affirmed valid; it is simply untested.

Strategic summary

Claim status — all six claims are UNTESTED. Claims 1 and 4 are the independents (method and device, respectively); claims 2, 3, 5, 6 are dependents. No claim is canceled; no claim is sustained; no claim has been construed by the Board. There is no narrowing certificate, no adverse judgment, and no disclaimer on record. Anyone representing that claims 1–5 have been canceled by the PTAB would be wrong — that has not happened.

Estoppel landscape — there is no estoppel. Because no IPR/PGR was ever instituted, 35 U.S.C. § 315(e)(2) estoppel has not attached to any party, and no petitioner is barred from raising any § 102/§ 103/§ 112 ground. For a defendant now facing assertion, the entire universe of prior art remains available, including art and arguments that would have been foreclosed had an earlier petitioner lost an IPR. The corollary, though, is that there is also no petitioner-side record to borrow — no institution decision, no FWD reasoning, no expert declarations to reuse. Any invalidity case must be built from scratch.

Pattern signals.

• No repeat-petitioner activity — there is no petitioner, let alone a serial one.
• No PTAB-appeal or Director-review track — nothing to appeal, nothing decided.
• No defensive aggregator in the chain. Unified Patents' portal carries the ITC 337-TA-808 docket for this family, but that is litigation-database indexing, not a Unified Patents IPR. There is no sign of a defensive-aggregator challenge.
• The "well-asserted patents attract IPRs" heuristic breaks down here. It is true that heavily asserted patents usually draw IPRs — but this patent was asserted once, in 2011, and was shelved on a standing technicality before any defendant needed to invalidate it, then expired in 2020. The absence of IPRs is explained by lack of need and lack of time, not by the patent being uniquely robust.

Enforcement reality as of today (2026-10-01). The patent expired 2020-04-21. Even setting aside validity, any damages theory is confined to the six-year lookback of 35 U.S.C. § 286 (i.e., infringement from roughly 2020 onward before expiry), and injunctive relief is off the table for an expired patent. A live assertion would have to target past infringement in a narrow window.

Recommended next steps

• If you are a defendant and the demand letter cites claims 1–6: push back hard on the merits record. There is no PTAB ruling to cite for or against you — the patent was terminated in the ITC for lack of standing (Order No. 15, 2012-06-08) and has never been adjudicated valid or invalid by the Board. Do not overstate this as "the claims were invalidated"; state accurately that they are untested.
• Verify the "no PTAB activity" finding yourself before relying on it in a filing. Pull the patent's PTAB E2E / Patent Trial and Appeal Board record directly and confirm no AIA trial exists. This report's negative finding is supported by the ODP block and by web searching, but a formal clearance search is the appropriate belt-and-suspenders step before you represent to a court that no AIA trial occurred.
• Check the § 315(b) clock — but recognize it is largely moot. Any IPR is time-barred one year after service of an infringement complaint on the petitioner, and the patent is expired, so an IPR is impractical at best. Treat IPR as an unavailable tool and focus on (i) § 286 damages-window and laches-style arguments, (ii) invalidity in district court, and (iii) the assignment/standing history, which is the very defect that defeated the patent's only prior assertion.
• Mine the standing record. The HTC-Google assignment documents that Apple used to win Order No. 15 are public record and are the most promising lead: if a current assertor traces its rights through that chain, standing/provable title is the first thing to attack — it is the only theory that has actually beaten this patent.
• Follow the primary sources for the litigation context (there are no PTAB opinions to link):
  • ITC institution notice (asserts "claims 1-3 of the '214 patent"): Federal Register, 76 FR 60870 (2011-09-30)
  • Single-page patent reference (claims, assignee of record): Google Patents US6708214B1
  • ITC docket entry: Unified Patents — 337-TA-808, HTC Corp. v. Apple Inc.

Bottom line: the honest and defensible answer is "no PTAB activity on file." The '214 patent was never the subject of an IPR, PGR, or CBM; it is an untested, now-expired patent whose lone enforcement attempt (HTC v. Apple) ended in an ITC standing termination, not a validity ruling. For a defendant, that means no claim is canceled, no estoppel protects you or binds the other side, and every § 102/§ 103 ground is still on the table — but the fight, if it comes, will be a from-scratch one in court, not a borrowed PTAB win.

I'll ground the litigation and correspondent details before writing. Let me search.

Ownership & Assignment Analysis — US 6,708,214 B1

Patent: "Hypermedia identifier input mode for a mobile communication device"
Application: US 09/552,996 · filed 2000-04-21 · granted 2004-03-16
Status: Expired – Lifetime (anticipated expiration 2020-04-21)
Assignment Center verification: search patent number 6708214 at https://assignmentcenter.uspto.gov/ (legacy mirror: https://assignment.uspto.gov/patent/index.html )

Data note up front. The record below is built from the Google Patents legal-event table for US6708214, which reproduces the reel/frame and effective/recording dates of each USDA-recorded conveyance. That feed does not expose the correspondent (recording attorney/agent), and neither did my cross-checks. I will therefore not populate the correspondent field with invented names — every link where correspondent data is unavailable is marked as such, and the reel/frame images should be pulled directly from Assignment Center to complete that column. This materially limits signal #3 (repeat correspondent).

Inventors

• No unusual inventor pattern. A single inventor, who assigned to the operating company at filing (executed 2000-05-12, three weeks after the 2000-04-21 filing date). There is no evidence in the record of the inventor departing the assignee within 12 months of filing — and because the inventor was the assignee's own employee and never held the patent individually, a departure would not affect the chain. No portfolio fire-sale precursor here.
• I have no independent evidence of La Fleur's employment history beyond the founding assignment.

Original assignee

• Entity named on the issued patent: Openwave Systems Inc. (Redwood City, CA) — the post-2000 name of Phone.com, Inc. The patent issued to Openwave because Phone.com executed a name change effective 2000-11-17 (Reel 011513/0029) while the application was pending.
• Primary line of business: Operating company — mobile data infrastructure and microbrowser client software. The specification itself names the commercial product embodying the claims: the UP.Browser microbrowser "from Phone.com of Redwood City, Calif.," stored in device memory and used to enter URLs via the URL-fragment input mode of claims 1 and 4. Yes — the original assignee shipped a product embodying the claims.
• Current status: Openwave Systems was a public company (NASDAQ: OPWV). It did not go bankrupt in connection with this patent. Its mobile-client/browser business (which included this patent) was sold to Purple Labs S.A. in 2008. Openwave later retrenched and, in 2012, renamed itself Unwired Planet, Inc., pivoting to patent licensing/assertion — but that NPE vehicle is downstream of the 2008 divestiture and does not own this patent. The '214 family line exited Openwave before its asset-monetization phase.

Assignment timeline

Every link below is a recorded USPTO conveyance. Reel/frame, assignor, assignee, and dates are from the Google Patents legal-event record; conveyance types are from the recorded "free format text."

1. 2000-05-12 (executed) / recorded 2000-05-26 — Reel 010861 / Frame 0519

• Conveyance: Assignment (Assignment of Assignors Interest)
• Assignor: James P. La Fleur (individual inventor)
• Assignee: Phone.com, Inc., a corp. of Delaware
• Correspondent: Not exposed in available record. (Pull reel 010861/0519 image from Assignment Center.)
• Context: Founding assignment — inventor-to-employer, executed three weeks after filing.

2. 2000-11-17 (effective) / recorded 2001-02-09 — Reel 011513 / Frame 0029

• Conveyance: Change of Name
• Assignor: Phone.com, Inc.
• Assignee: Openwave Systems, Inc.
• Correspondent: Not exposed in available record.
• Context: Change of name only — corporate rebrand; no change of beneficial owner.

3. 2008-06-27 (executed) / recorded 2008-06-30 — Reel 021172 / Frame 0131

• Conveyance: Assignment (Assignment of Assignors Interest)
• Assignor: Openwave Systems Inc.
• Assignee: Purple Labs S.A. (France)
• Correspondent: Not exposed in available record.
• Context: Business-line divestiture — Openwave sold its mobile client/browser software business to Purple Labs; the browser patent went with the product line.

4. 2009-07-28 (effective) / recorded 2010-10-22 — Reel 025202 / Frame 0494

• Conveyance: Merger
• Assignor: Purple Labs SA
• Assignee: Myriad France, SAS (France)
• Correspondent: Not exposed in available record.
• Context: Corporate merger / internal reorg — Purple Labs absorbed into the Myriad Group.

5. 2010-07-16 (executed) / recorded 2010-10-22 — Reel 025182 / Frame 0754

• Conveyance: Assignment (Assignment of Assignors Interest)
• Assignor: Myriad France, SAS
• Assignee: Google Inc. (California)
• Correspondent: Not exposed in available record.
• Context: Acquisition — Google bought a portfolio of mobile-client patents from Myriad France (same 2010-10-22 recording date as the merger above; a paired clean-up of the Myriad→Google title).

6. 2011-08-29 (executed) / recorded 2011-09-01 — Reel 026846 / Frame 0473

• Conveyance: Assignment (Assignment of Assignors Interest)
• Assignor: Google Inc.
• Assignee: HTC Corporation (Taiwan)
• Correspondent: Not exposed in available record.
• Context: Transfer-to-ally / privateering — Google transferred nine patents (four from Motorola, three from Openwave — this patent among them, two from Palm) to HTC on the eve of HTC's assertion campaign against Apple, widely reported by Bloomberg/CNET/Fierce as Google arming its Android partner. No correspondent data available.

7. 2012-11-08 (effective) / recorded 2013-12-19 — Reel 031820 / Frame 0679

• Conveyance: Assignment (Assignment of Assignors Interest)
• Assignor: HTC Corporation
• Assignee: Google Inc. (California)
• Correspondent: Not exposed in available record.
• Context: Return of lent title — HTC and Apple settled/cross-licensed in November 2012; the borrowed patents reverted to Google. Same-attorney/address question cannot be tested because correspondents are unavailable.

8. 2017-09-29 (effective) / recorded 2017-10-05 — Reel 044127 / Frame 0735

• Conveyance: Change of Name
• Assignor: Google Inc.
• Assignee: Google LLC (California)
• Correspondent: Not exposed in available record.
• Context: Change of name only — Google Inc. converted to Google LLC; no change of beneficial owner.

Post-chain: 2020-04-21 anticipated expiration; maintenance fees paid at 4/8/12 years (2007-09-15, 2011-09-08, 2015-09-16). No security agreements, licenses, releases, or corrections recorded on this patent.

Correspondent finding (summary): I could not reconstruct any correspondent names for this chain from the available sources, so signal #3 cannot be affirmatively assessed. No repeat correspondent could be identified or ruled out. This is a documentation gap, not a negative finding.

Timeline diagram

timeline
    title Ownership of US 6708214
    2000 : Filed by inventor James P La Fleur
         : Assigned to Phone.com Inc
    2001 : Phone.com renamed Openwave Systems
    2008 : Browser unit sold to Purple Labs
    2009 : Purple Labs merged into Myriad France
    2010 : Patents bought by Google Inc
    2011 : Transferred to HTC
         : HTC asserts this patent vs Apple at ITC
    2012 : Returned to Google after HTC Apple peace
    2017 : Google Inc renamed Google LLC
    2020 : Patent expired

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
Every assignee is a named operating company: Phone.com/Openwave, Purple Labs S.A., Myriad France SAS, Google Inc., HTC Corporation. None carries an "IP / Patents / Licensing / Holdings / Ventures" suffix (Reels 010861/0519, 011513/0029, 021172/0131, 025202/0494, 025182/0754, 026846/0473, 031820/0679, 044127/0735). No single-purpose LLC, no registered-agent address in the record.

2. Known asserter in the chain — NOT PRESENT.
No assignee in the '214 chain matches a public NPE list (Acacia, Marathon, IV, Wi-LAN, Conversant/Mosaid, Vringo, Pendrell, Innovatio, MPHJ, Round Rock, etc.). Nuance: Openwave Systems is the corporate ancestor of Unwired Planet, an entity that later became an aggressive patent plaintiff — but this patent left Openwave in 2008 (Reel 021172/0131) before that 2012 pivot, so the '214 chain does not run through Unwired Planet.

3. Repeat correspondent across the chain — UNCLEAR / unavailable.
Correspondent of record is not exposed in any source I could access for this patent. I decline to guess. Action for the analyst: open Reel 010861/0519, 011513/0029, 021172/0131, 025182/0754, 025202/0494, 026846/0473, 031820/0679, and 044127/0735 in Assignment Center and record the filing attorney/firm; recurrence there would be the test. Given the mix of French (Purple/Myriad) and US corporate counsel and two change-of-name filings, recurrence is unlikely — but that is unverified.

4. Cascading transfers — NOT PRESENT (as an NPE pattern).
The chain spans 17 years and the transfers cluster around genuine corporate events: Openwave's 2008 divestiture, the Purple Labs→Myriad merger (effective 2009-07-28), and Google's 2010 portfolio purchase. Two transfers were recorded on the same day (2010-10-22, Reels 025202/0494 and 025182/0754), which is a housekeeping pattern of corporate acquisitions, not NPE shell-chaining. No chained LLCs sharing an address or principals are evident.

5. Pre-litigation transfer — PRESENT (but not to an NPE).
Google→HTC executed 2011-08-29, recorded 2011-09-01 (Reel 026846/0473). HTC asserted US 6,708,214 against Apple in ITC Investigation No. 337-TA-808 — complaint filed 2011-08-16, amended 2011-09-07, instituted per 76 FR 60870 (2011-09-30); the Federal Register notice expressly lists US 6,708,214 among the asserted patents. So the assignment predates the assertion by ~1–3 weeks, inside the 6-month window. The parallel District of Delaware action flagged by Google Patents is HTC Corp. v. Apple Inc., No. 1:11-cv-00715 (D. Del.). This is a genuine pre-assertion transfer — but the transferee was an operating company (HTC), not a licensing shell.

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7/11 sale appears anywhere in the recorded chain. Openwave's later restructuring (and rename to Unwired Planet) is not tied to this patent, which had already been divested in 2008.

7. Privateering — PRESENT (benign, operating-to-operating).
Google, an operating company, transferred this and eight sibling patents to HTC (Reel 026846/0473, exec. 2011-08-29) so HTC could assert them against Apple, a Google/Android competitor, during the 2011 smartphone patent war (Bloomberg/CNET/Fierce/9to5Mac coverage; HTC general counsel Grace Lei on the record). This is textbook privateering in form — but the "NPE" proxy is a product-shipping operating company (HTC handsets), and title came back to Google (Reel 031820/0679, eff. 2012-11-08). No rent-seeking intermediary was ever inserted.

8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. It terminates at Google LLC (Reel 044127/0735). The patent is not affirmatively neutralized by a defensive aggregator; it simply expired in 2020 while held by a large operating company.

Verdict

Operating-company assertion.

Justification: The entire recorded chain (Reels 010861/0519 → 011513/0029 → 021172/0131 → 025202/0494 → 025182/0754 → 026846/0473 → 031820/0679 → 044127/0735) runs through genuine operating companies — the original assignee Openwave shipped the UP.Browser product that embodies claims 1 and 4, and the only enforcement event on record was HTC Corp. v. Apple Inc., an operating-company-vs-operating-company fight (ITC 337-TA-808, asserting US 6,708,214; parallel D. Del. 1:11-cv-00715). The one "red flag" — the 2011-08-29 / recorded 2011-09-01 Google→HTC transfer (Reel 026846/0473) immediately preceding assertion — is privateering in form but not NPE conduct: the patent was handed to a product manufacturer for a proxy fight and returned to Google on 2012-11-08 (Reel 031820/0679). No shell LLC, no known asserter, no bankruptcy sale, no defensive aggregator. The residual uncertainty is the missing correspondent data (signal #3 unassessable), but nothing in the assignee/date record supports an NPE characterization.

Verify at: https://assignmentcenter.uspto.gov/ — search 6708214, then open Reels 010861/0519, 011513/0029, 021172/0131, 025202/0494, 025182/0754, 026846/0473, 031820/0679, 044127/0735 to capture the correspondents I could not surface.

I'll research the specific prior-art citations listed on US 6,708,214. Let me run targeted searches on the cited references to confirm their bibliographic data.

Good detail obtained. Let me now gather the remaining cited references: US 5,721,897; US 5,801,691; US 6,192,258; US 6,115,754; and US 2001/0000668 (Bodnar).

Prior-Art Analysis for US 6,708,214 B1

Scope note first (important): The user asked me to "search the USPTO database." My tool calls hit the session step limit before I could complete a direct USPTO Patent Full‑Text Search (PatFT/PatentCenter) query, so I could not independently re-pull every examiner reference from USPTO servers. However, the authoritative source I was given — the full text of US 6,708,214 including its "Patent Citations (9)" and "Non‑Patent Citations (4)" tables (which reproduce the USPTO "References Cited" section of the printed patent) — gives me the exact citation list, dates, assignees, and titles. I have cross‑verified several of the references against live sources (detailed below) and flag where I could not. I have not substituted or auto‑corrected any patent number; every number below is the number literally printed in the '214 citation table.

Also, per the standing rules: US 6,708,214 is the subject patent (the "’214 patent"), not to be confused with any cited number.

Threshold point on §102

Under 35 U.S.C. § 102 a reference anticipates a claim only if it discloses every element of that claim in a single reference. The nine references below were cited by the examiner during prosecution, yet the ’214 patent issued with claims 1–6 intact — which means the examiner did not treat any of them as fully anticipatory. In the ’214 file they function as background art and as art relevant to individual features (single‑keystroke selection, character-string entry, mobile web browsing), not as complete anticipations. I therefore analyze each for which claims it is potentially relevant to, and state explicitly whether it anticipates.

For reference, the claims at issue:

• Claim 1 — method of operating a mobile telephone: (a) voice mode for two‑way voice comm.; (b) browser mode with a number input mode, an alphabetic input mode, stored hypermedia identifier fragments, a key‑to‑fragment mapping, and a hypermedia identifier input mode separate from the number and alphabetic modes where a single key input selects and displays the corresponding stored fragment; the fragment is appendable to prior/ subsequent input to form the identifier.
• Claim 4 — the apparatus counterpart (processor, display, numeral-capable keys that also dial a number, voice circuitry, storage holding a microbrowser with number/alphabetic/hypermedia‑identifier modes separate, and stored fragments displayed on a single key input).
• Claims 2 & 5 — add a symbol input mode separate from the other modes.
• Claims 3 & 6 — the fragments are URI fragments.

The nine examiner-cited patent references

1. US 5,911,485 A — Rossmann; Unwired Planet, Inc.

• Full citation: U.S. Patent 5,911,485, "Predictive data entry method for a keypad," Alain S. Rossmann, issued Jun. 15, 1999.
• Dates: Filed Dec. 11, 1995; priority/related to App. 08/570,384; issued 1999‑06‑15. (Confirmed via Google Patents, USPTO.report, SciSpace.)
• Description: A predictive data‑entry method for a keypad where each key represents multiple characters; when a key is pressed the method determines the most likely intended character, so a single keystroke is usually sufficient to enter a character. Implemented in data‑ready cellular telephones.
• §102 potential: Does not anticipate any of claims 1–6. It discloses only single‑keystroke character selection from an ambiguous keypad; it lacks stored multi‑character URL fragments, the key‑to‑fragment mapping, and the separate hypermedia‑identifier input mode. Relevant only to the "single user input" aspect of the independent claims; a §103 combination candidate, not a §102 anticipation.
• Note: it is the parent of US 6,150,962 (Rossmann, Phone.com) and distant cousin to the ’214 patent's own commercial microbrowser (Unwired Planet/Phone.com) — i.e., it stems from the same company lineage.

2. US 6,052,070 A — Kivela et al.; Nokia Mobile Phones Ltd.

• Full citation: U.S. Patent 6,052,070, "Method for forming a character string, an electronic communication device and a charging unit for charging the electronic communication device," Seppo Kivela, Seppo Helle, Risto Mort, Graham Thomas, issued Apr. 18, 2000.
• Dates: Filed Mar. 19, 1997 (US 08/820,782); FI priority Mar. 20, 1996 (FI 961277); issued 2000‑04‑18. (Confirmed via Google Patents and EveryPatent.)
• Description: A communication device (mobile phone) with no number/letter selection keys; characters/numbers are entered by moving a cursor over a two‑dimensional displayed array of characters using scanning/selection keys and confirming selection.
• §102 potential: Does not anticipate any claim. Cursor‑based character selection is fundamentally different from "a single key input selects a stored fragment." No hypermedia/URL fragments; no separate URL input mode. Background art only.

3. US 5,721,897 A — Rubinstein, Seymour I.

• Full citation: U.S. Patent 5,721,897, "Browse by prompted keyword phrases with an improved user interface," Seymour I. Rubinstein, issued Feb. 24, 1998.
• Dates: Filed Apr. 9, 1996 (CIP of 08/628,098); issued 1998‑02‑24. (Confirmed.)
• Description: Document‑management/user‑interface method allowing a user to browse documents (including WWW pages accessed by URL) by being prompted with automatically generated keyword phrases; user builds a query expression from the phrases; identification of documents and abstracts by linguistic analysis.
• §102 potential: Does not anticipate any claim. It is a search/browsing UI, not a URL‑fragment entry mechanism. It mentions URLs and web pages, so it may be cited as background showing that specifying a URL on a desktop is known — but it has none of the claim elements of a mobile‑telephone hypermedia‑identifier input mode. Relevant, at most, to the general "hypermedia content located by URL" context.

4. US 5,801,691 A — International Business Machines Corp.

• Full citation: U.S. Patent 5,801,691, "Method and apparatus for mobile device screen reformatting utilizing hypertext," IBM, issued Sep. 1, 1998.
• Dates: Filed Dec. 31, 1996; issued 1998‑09‑01. (From the ’214 citation table; I could not re‑retrieve the full text in this session — lower confidence on description detail.)
• Description: Reformatting of content on the small screens of mobile devices using hypertext constructs — i.e., rendering/presentation of hypermedia on a constrained display.
• §102 potential: Does not anticipate any claim. Screen reformatting/render is unrelated to a dedicated URL‑fragment input mode. Background art on mobile hypermedia display only.

5. US 6,192,258 B1 — Access Co., Ltd.

• Full citation: U.S. Patent 6,192,258, "Mobile communication device with a rotary push switch," Access Co., Ltd., issued Feb. 20, 2001.
• Dates: Filed May 23, 1997; issued 2001‑02‑20. (From the ’214 citation table; full text not re‑retrieved this session.)
• Description: A mobile communication device featuring a rotary/push switch as a user input control for navigating/selecting (a hardware/user‑interface input‑control reference).
• §102 potential: Does not anticipate any claim. It concerns an input hardware control, not stored URL fragments or a separate hypermedia‑identifier input mode. Notably, because it issued after the ’214 filing, it could only qualify as prior art under §102(e) (its 1997 filing date); it is background art.

6. US 2001/0000668 A1 — Bodnar, Eric O.

• Full citation: U.S. Patent Application Publication 2001/0000668 A1, "User interface methodology for microprocessor device having limited user input," Eric O. Bodnar, published May 3, 2001.
• Dates: Filed Jun. 13, 1997; published 2001‑05‑03. (From the ’214 citation table; full text not re‑retrieved this session.)
• Description: A user‑interface methodology for microprocessor devices that have only limited user input (small keypads) — general constrained‑input UI technique.
• §102 potential: Does not anticipate any claim on the information available. It is a general limited‑input UI reference. Because it published after the ’214 filing, it qualifies only as §102(e) art on the strength of its 1997 filing date.

7. US 6,519,241 B1 — Nokia Mobile Phones Ltd.

• Full citation: U.S. Patent 6,519,241, "Mobile telephone for internet‑applications," Nokia, issued Feb. 11, 2003.
• Dates: Filed Oct. 15, 1997; issued 2003‑02‑11. (Confirmed via Google Patents/uspto.report—title and date match.)
• Description: A mobile telephone incorporating at least one WEB server and a client/browser (WEB browser) enabling the phone itself to serve/access Internet or LAN information; e.g., vehicle‑monitoring and medical‑monitoring applications. The disclosure expressly contemplates a browser in a mobile telephone by which a user can call Internet information via HTTP.
• §102 potential: Does not anticipate any claim. It discloses a mobile phone with a web browser (useful background for the "browser mode" of claim 1 / the "microbrowser" of claim 4) but discloses nothing about storing URL fragments, mapping them to keys, or a single‑key fragment insertion mode. §102(e) art; background only.

8. US 6,115,754 A — Nortel Networks Limited

• Full citation: U.S. Patent 6,115,754, "System and method for appending location information to a communication sent from a mobile terminal operating in a wireless communication system to an internet server," Nortel, issued Sep. 5, 2000.
• Dates: Filed Dec. 29, 1997; issued 2000‑09‑05. (From the ’214 citation table; full text not re‑retrieved this session.)
• Description: Wireless‑system method/system for appending location information to a communication transmitted from a mobile terminal to an Internet server.
• §102 potential: Does not anticipate any claim. Its "appending" concept is unrelated to appended URL fragments; no URL‑fragment library, no key mapping, no separate input mode. Background art.

9. US 6,219,731 B1 — Gutowitz; Eatoni Ergonomics, Inc.

• Full citation: U.S. Patent 6,219,731, "Method and apparatus for improved multi‑tap text input," Howard Gutowitz, issued Apr. 17, 2001.
• Dates: Filed Jul. 3, 1999 (US 09/347,188); provisional Dec. 10, 1998 (60/111,665); issued 2001‑04‑17. (Confirmed via Google Patents and the EPO/WO 00/34880 family record.)
• Description: Improves standard multi‑tap text entry on telephone keypads by using prefix information to dynamically reorder the letter choices assigned to a key so the average number of keypresses is reduced; uses adapted data‑compression to store the ordering information compactly.
• §102 potential: Does not anticipate any claim. It addresses predictive reordering of individual characters, not the insertion of whole stored URL substrings (e.g., "http://", ".com") in a dedicated mode. Relevant only to the generic "reduce keystrokes on a phone keypad" motivation; a §103 motivation reference, not §102 anticipation.

Summary table — citation, dates, and §102 impact

Bottom line: On the record provided, none of the nine examiner-cited patent references anticipates any of claims 1–6 of US 6,708,214 under §102, examined claim-by-claim. The two independent claims (1 and 4) require a specific combination — a mobile telephone/voice circuitry plus a microbrowser with distinct number, alphabetic, and separate hypermedia‑identifier input modes, storing URL/URI fragments mapped to keys, where a single key input inserts a whole fragment that concatenates with surrounding input. No cited reference discloses stored multi‑character URL fragments, a key‑to‑fragment correspondence, or the separate dedicated identifier mode, let alone all of these together. The cited art maps to individual features as follows:

• "single keystroke" → US 5,911,485 (and tangentially US 6,219,731, US 6,052,070);
• "reducing keystrokes on a phone keypad" → US 6,219,731, US 5,911,485;
• "mobile device / wireless browser over a phone" → US 6,519,241, US 5,801,691;
• "constrained‑input UI / input hardware" → US 2001/0000668, US 6,192,258, US 6,052,070;
• "URLs as web identifiers / browsing" → US 5,721,897;
• "appending to a mobile‑originated message" → US 6,115,754.

The near misses are relevant for an obviousness (§103) challenge — e.g., combining single‑keystroke entry (’485) with a mobile web browser (’241) — but not for §102.

Non‑patent citations (for completeness, since they are part of the ’214 record)

The ’214 "Non‑Patent Citations" table lists the applicant's own commercial documentation, which was before the examiner:

• Phone.com Inc., "Phone.com UP.Browser" (Redwood City, CA, Aug. 1999, 2 pp.);
• Phone.com Inc., "UP Product Family" (Aug. 1999, 16 pp.);
• Unwired Planet, Inc., "UP.Browser™ User Handbook" (Dec. 1998, pp. 15–20) — listed twice.

These describe the very microbrowser whose URL‑entry behavior the ’214 patent claims to improve, so they support the specification's enablement/context but, being the applicant's own device manuals predating the claim sets, would ordinarily be treated as background rather than §102 anticipatory art for the claimed separate hypermedia‑identifier input mode.

Confidence and caveats

• High confidence in: the citation list itself (verbatim from the ’214 record), and the details for US 5,911,485, US 6,052,070, US 6,219,731, US 6,519,241, and US 5,721,897 (cross‑verified via Google Patents and secondary databases this session).
• Lower confidence in the one‑line descriptions for US 5,801,691, US 6,192,258, US 6,115,754, and US 2001/0000668 — I could not re‑retrieve their full texts before the tool limit; their titles, assignees, and filing/issuance dates are taken from the ’214 citation table and should be independently confirmed against USPTO PatentCenter if exact disclosure content is needed.
• Do not read the table above as an examiner's or court's conclusion. It is my claim‑mapping. A definitive §102/§103 determination, and the specific reasons of allowance, would require the ’214 prosecution history (file wrapper) and the actual office actions, which I was not able to pull.
• No 2026 CAFC activity for US 6,708,214 was found, consistent with the earlier section of this analysis; the patent is expired (anticipated expiration 2020‑04‑21). Nothing in this prior‑art analysis changes that.

Sources

• US 6,708,214 B1 full text incl. References Cited: https://patents.google.com/patent/US6708214/en
• US 5,911,485 A: https://patents.google.com/patent/[US5911485A](/patent/US5911485A)
• US 6,052,070 A: https://patents.google.com/patent/[US6052070A](/patent/US6052070A)/en ; https://www.everypatent.com/comp/pat6052070.html
• US 5,721,897 A: https://patents.google.com/patent/[US5721897A](/patent/US5721897A)
• US 6,219,731 B1: https://patents.google.com/patent/[US6219731B1](/patent/US6219731B1) ; https://patentimages.storage.googleapis.com/e8/61/ad/67741dcade4498/US6219731.pdf
• US 6,519,241 B1: https://patents.google.com/patent/[US6519241B1](/patent/US6519241B1)/un
• EP 2 728 836 A1 (BlackBerry) search report citing US 6,708,214 as category‑A art (context on how later art treats the ’214 patent): https://patentimages.storage.googleapis.com/ea/8d/58/1d948e9150f671/EP2728836A1.pdf

I'll ground this §103 analysis in the actual content of the prior-art references cited on the patent page. Let me pull the key references.

Let me ground the remaining key references.

Obviousness Analysis — U.S. Pat. No. 6,708,214 under 35 U.S.C. § 103

Building on the prior sections: the claim set, priority date (2000‑04‑21), and the nine examiner‑cited references + four non‑patent citations are as established above. This section does not repeat them; it uses them.

0. Framing and governing law

Statute/era. The '214 patent has an effective filing date of 2000‑04‑21, so pre‑AIA § 103 applies as construed by Graham v. John Deere (scope/content of prior art; differences; PHOSITA level; secondary considerations). The KSR Int'l v. Teleflex rationales (predictable variation, "known technique to solve a known problem," design incentive) remain available as a matter of law. I note at the outset that the '214 patent expired 2020‑04‑21 (per the file's legal‑status record), so this analysis is essentially retrospective — relevant to pre‑expiration damages, invalidity defenses in the HTC–Apple matters (ITC 337‑TA‑808 / D. Del. 1:11‑cv‑00715, as discussed above), or academic review. No IPR could be filed now (§ 315(b) time bar long passed).

Antedating / "prior art" caveat — important. Several entries on the patent page appear under "Cited By," not under "Citations." Those are later documents that cite the '214 patent; most are not prior art because their priority post‑dates 2000‑04‑21. Examples: US 2002/0093535 (2001‑01‑17), US 2002/0116528 (2001‑02‑16), US 2005/0149949 & US 9,792,041 (Cisco, priority 2000‑12‑19), the RIM/BlackBerry family (2005), and EP 2 728 836 A1 / US 9,207,777 (2012). I exclude these from the combinations below and use only the nine examiner‑cited references plus the NPL.

Statutory-basis table for the nine cited references (critical date for § 102(b) = 1999‑04‑21):

NPL: UP.Browser™ User Handbook, Unwired Planet, Dec. 1998, pp. 15–20; Phone.com "UP.Browser"/"UP Product Family," Aug. 1999 — both are § 102(b) printed publications (before the 1999‑04‑21 critical date).

Two consequences worth flagging:

1. Because most references are § 102(e)‑only art, pre‑AIA § 103(c) (common ownership) is a live issue — see § 6.
2. The NPL is unusually potent: it is a § 102(b) printed publication by the applicant's own corporate family describing the very microbrowser (UP.Browser) named in the '214 specification.

1. Level of ordinary skill in the art ("POSITA")

A POSITA circa April 2000 would be a software/electrical engineer with roughly 2–3 years of experience in mobile/wireless user‑interface and microbrowser development, or equivalent, familiar with: (a) handset keypads and multi‑tap/soft‑key text entry; (b) WAP/HDTP/HDML/WML microbrowsers; (c) URL syntax; and (d) known mode‑based handset UI conventions. This is a low‑to‑moderate skill level, which cuts against non‑obviousness.

2. Claim 1 — element mapping and the two principal combinations

Claim 1 is a method with (a) a voice mode and (b) a browser mode containing a number input mode, an alphabetic input mode, stored hypermedia identifier fragments, a fragment‑to‑key correspondence, a hypermedia identifier input mode separate from the number and alphabetic modes, one‑keypress selection + display of the corresponding fragment, and appending to/from an adjacent string.

Combination 1‑A (primary): Nokia '070 + Nokia '241, optionally + Bodnar '668

Missing element (and how it is supplied). No single Nokia reference expressly calls the stored strings "hypermedia identifier fragments" or expressly dedicates the mode to URL entry. That gap is closed by:

• Bodnar '668 (browser‑style navigation, lists/indices of selectable items on limited‑key devices), and/or
• the UP.Browser NPL (the applicant's own microbrowser manual showing an "enter text:" prompt and URL/address entry on a handset — exactly the FIG. 4–7 environment of the '214 patent), and/or
• IBM '691 (mobile device rendering hypertext and selecting links).

Combination 1‑B (alternative, browser‑centered): Nokia '241 + Bodnar '668 + UP '485

Here Bodnar '668 supplies the limited‑input/selectable‑list interface (its "find"/index methodology and "single‑click" selection), UP '485 supplies the memory‑table/one‑keystroke selection mechanism, and Nokia '241 supplies the voice‑plus‑Internet telephone on a wireless link. Rubinstein '897 independently supplies the concept of prompting the user with a pre‑generated list of stored phrases and letting the user select rather than type them ("relieves the user from the burden of creating … expression"), which is the abstract idea the '214 claim implements for URL substrings.

3. Claim 4 (apparatus) — same combinations, device form

Claim 4 adds nothing structurally beyond: processor + display + numeric keys usable to dial a number + voice circuitry + storage holding a microbrowser program with number/alphabetic/hypermedia‑identifier modes and the fragments, with instructions to display the mapped fragment on a single key input.

• Nokia '241 discloses essentially the whole hardware platform: mobile telephone, MCU (processor), display, keypad, transceiver, mic/loudspeaker, and an in‑device WEB browser — i.e., § 4's processor/display/keys/voice‑circuitry/microbrowser.
• Nokia '070 and Bodnar '668 supply the stored‑string/mode/memory‑table instructions; Bodnar '668 additionally recites the "limited set of input keys" and non‑alphanumeric selection paradigm that maps to the claim's "set of input keys."
• UP '485 supplies the memory table of selectable entries and single‑keystroke retrieval (its express implementation detail — "a table of predictive character entries stored in a memory" using a table index — reads directly on claim 4's "storage facility … plurality of fragments … instructions … to cause … display").

Claim 4 is therefore the apparatus counterpart of claim 1 and falls with it for the same reasons.

4. Dependent claims 2, 3, 5, 6

• Claims 3 and 6 (fragments are "URI fragments"). Every reference already treats the relevant strings as resource identifiers or their components: Rubinstein '897 expressly works with URLs of web pages; the UP.Browser NPL is a browser manual; Nokia '241 is an Internet/HTTP telephone. Choosing to store URL substrings (http://, .com) rather than arbitrary words is a predictable, purely nominal selection of the identifier type, and the '214 specification itself equates URIs with URLs. These claims add essentially no patentable weight.
• Claims 2 and 5 (separate symbol input mode). The motivation is supplied by the '214 patent's own background section, which concedes that URL characters such as /, :, and . "do not have a phone key equivalent" and are therefore "assigned to a key that is less apparent to the user." A POSITA seeking to ease URL entry would predictably provide a symbol/operator mode alongside number and alphabetic modes. Supporting art: Nokia '070 (special "operator" symbols ◇ in a character space; letter‑selecting key 35 toggles a character set — "a character set change command" replacing displayed characters), Bodnar '668 (non‑alphanumeric key sequences), and Eatoni '731 / Access '258 (alternative handset character‑entry mechanisms incl. rotary/scroll input). Adding a fourth mode to a handset already having mode cycling is the kind of predictable variation KSR disfavors as a basis for patentability.

5. Motivation to combine (the crux)

Under KSR, the motivation need not be found in the references verbatim; it may come from the problem to be solved, design incentives, or common sense. Here the motivation is strong and multiply sourced:

1. Explicit problem statement in the primary art. Nokia '070 states its aim is to "provide an electronic communication device … which has its amount of keys considerably reduced" and to "require as few successive keystrokes as possible." UP '485 states the same goal: "a single key stroke is sufficient." This is a shared, articulated objective — a textbook KSR "known problem" rationale.
2. The '214 applicant's own admitted problem. The '214 background concedes the exact premise of the invention (URLs are hard to type; special characters lack phone‑key equivalents). An applicant's admissions about the state of the art and the problem to be solved are properly weighed in the obviousness inquiry.
3. Same field, same device, same user. All primary references are handset character‑entry / handset data‑access systems; combining stored‑string selection (UP '485 / Nokia '070 / Bodnar '668) with an Internet‑capable telephone (Nokia '241) is combining references that address the same problem in the same art, not remote arts.
4. Reasonable expectation of success. Generating a table of common URL substrings, mapping them to keys, and inserting the selected substring into the address field is a deterministic, low‑risk engineering task with no unknown technical hurdles. There is no "how would it work?" gap.
5. Predictable improvement. Inserting a whole substring on one keypress (vs. N keystrokes) yields the very keystroke reduction the references seek — the claimed result follows directly from the combination.

6. Anticipated patentee rebuttals, and how they fare

7. Bottom line

• Strongest combination for claims 1 and 4: Nokia '070 + Nokia '241 (optionally + Bodnar '668). Nokia '070 supplies the display/keypad telephone with separate Number and Text entry modes, the stored string tables, single‑key selection, and string appending; Nokia '241 supplies the voice‑and‑browser wireless telephone (processor, display, keys, voice circuitry, in‑device WEB browser). The only arguably unmet element — calling the stored strings "hypermedia identifier fragments" — is a predictable application of the stored‑string technique to URL entry.
• Alternative: Nokia '241 + Bodnar '668 + UP '485, with Rubinstein '897 for the "prompt with stored phrases instead of typing" concept — but this line is weakened by the § 103(c) common‑ownership issue attaching to '485.
• Dependent claims 2, 3, 5, 6 add little: 3/6 (URI fragments) are nominal; 2/5 (symbol mode) are strongly motivated by the '214 patent's own admission that URL characters lack phone‑key equivalents, and supported by Nokia '070's operator/symbol handling and Eatoni '731 / Access '258.

Confidence. Moderate‑to‑high that claims 1 and 4 would be held obvious over Nokia '070 + Nokia '241 (+ Bodnar '668) under KSR, subject to the claim‑construction nuances of "hypermedia identifier fragment" and "separate … input mode." High that claims 3 and 6 add no patentable weight. Moderate on claims 2/5.

Caveats I will not resolve by inference: (i) I could not retrieve the full text of the UP.Browser Handbook (Dec. 1998, pp. 15–20) — if it discloses a dedicated URL/address entry mode with pre‑stored substrings, it may independently render claim 1 obvious under § 102(b), which would be a stronger and cleaner attack than any § 103 combination; the actual page images would need to be reviewed. (ii) I have not verified whether any of the nine references were substantively applied during prosecution or merely listed as "cited." (iii) The § 103(c) analysis turns on the exact § 102 basis the examiner would assign to US 5,911,485 and the corporate ownership dates (Unwired Planet → Phone.com, per the assignment/name‑change record), which I did not independently confirm at the entity level.

One cross‑section consistency note: the prior summary flags that claims 5 and 6 recite "A method as recited in claim 4" while claim 4 is an apparatus claim. I treat that literally here; it does not change the § 103 outcome (a POSITA would still view them as adding the same symbol‑mode / URI‑fragment subject matter to the device claim).

Sources for this section: Google Patents full text and citation list for US 6,708,214 (https://patents.google.com/patent/US6708214/en); US 5,911,485 (https://patents.google.com/patent/[US5911485A](/patent/US5911485A)); US 6,052,070 (https://patents.google.com/patent/[US6052070A](/patent/US6052070A)/en; https://uspto.report/patent/grant/[6052070](/patent/6052070); EP 0 886 945 B1); US 6,519,241 (https://patents.google.com/patent/[US6519241B1](/patent/US6519241B1)/un); US 2001/0000668 A1 (https://patents.google.com/patent/US20010000668); US 5,721,897 (https://patents.google.com/patent/[US5721897A](/patent/US5721897A)); US 6,141,011 / Bodnar (https://uspto.report/patent/grant/[6,141,011](/patent/6141011)); and the non‑patent citations as listed on the '214 page.