US 6868399

I'll search for authoritative information on this patent, then summarize.

US Patent 6,868,399 — Verified Summary

Search scope note: I searched for litigation and CAFC/PTAB activity tied to this exact number. I found no 2026 U.S. Court of Appeals for the Federal Circuit docket naming U.S. Patent 6,868,399. Given the patent's legal status (expired), that absence is unsurprising, but I cannot exclude a lingering appeal I did not surface. I found no search result that contradicted the patent's own front matter, and I use that front matter as authoritative below.

Bibliographic data

Priority chain: Six U.S. provisional applications, all filed October 22, 1999 — 60/160,973 ("Systems and Methods for Enabling Network Gateway Devices to Communicate with Management Systems…"), 60/161,182, 60/161,139, 60/161,189, 60/161,181, and 60/161,093.

Assignment-chain caveat: The record is non-linear. Nomadix, Inc. → NTT DOCOMO (security interests, 2015 and 2017) → Gate Worldwide Holdings LLC (2018) → Knobbe, Martens, Olson & Bear (security interest, 2019) → released back to Nomadix, Inc. (2019-05-28), with a further quitclaim from Gate Worldwide Holdings LLC to Nomadix, Inc. dated 2019-11-22. Google's "current assignee" field still lists Gate Worldwide Holdings LLC, which appears stale relative to the 2019 quitclaim. Treat assignee ownership as uncertain without a current USPTO assignment record.

Inventor-name caution: The assignment abstract spells the second inventor "PERELYBUSKIY, DENIS I.," while the patent front matter and Google both render it "Perelyubskiy." I am reporting both as found and not auto-correcting either.

Abstract (as issued)

Systems and methods enabling a management system to communicate with a network gateway device to automatically manage a user accessing a computer network, such as a local network. The system includes a computer, and a network gateway device in communication with the computer for connecting the computer to a computer network, wherein the network gateway device maintains data representative of the user's access to the computer network and wherein the network gateway device reconfigures the data. The system also includes a management system connected to said network gateway device for automatically billing the user based upon usage of the computer network, wherein the management system is configured to communicate according to at least one compatible protocol. The network gateway device reconfigures the data to meet one of the predetermined protocols supported by the management system, and the management system receives the data reconfigured by the network gateway device and utilizes the data reconfigured by the network gateway device for automatic billing purposes.

Plain-language overview of the five independent claims

(1) Claim 1 — System claim (billing, CAR format). A system with three pieces: (a) a computer; (b) a network gateway device wired to that computer that connects it to the network and holds data about what the user did on the network — and critically, it works "absent additional agents implemented by the computer," i.e., no special client software on the user's machine; and (c) a management system (e.g., a hotel property management system) attached to the gateway, which is built to speak at least one predetermined protocol. The gateway itself reformats the usage data into call accounting record (CAR) format, and the management system consumes that formatted data to bill the user.

(2) Claim 6 — Method claim (clientless, CAR format). The method counterpart to claim 1: let a user reach the network through the gateway without any added client software on their machine; collect access data at the gateway; reconfigure it into call accounting record format; and send it to the management system.

(3) Claim 10 — System claim (management system drives the gateway). Here the flow runs the other direction. Same clientless gateway, but the gateway keeps data on the user's physical location and their network access. The management billing system is described as able to "activate communication with" the gateway — it can push instructions back down to control (allow/deny) a given user's access and a given physical location's access. This captures the specification's "upstream" direction (e.g., the PMS telling the gateway a room should be denied access, or asking whether a user is online).

(4) Claim 13 — System claim (billing keyed to physical location + usage). Combines the billing purpose with location awareness: the gateway (again clientless) stores data on the user's physical location and network usage, then formats that data to conform to whichever predetermined protocol the management system supports. The management system bills based on the physical location and the usage. Note this claim is broad — it does not require CAR format; it requires conformity to a supported protocol.

(5) Claim 18 — Method claim (location + usage, protocol-flexible). Method counterpart to claim 13: clientless access through the gateway, collect data including physical location and network usage at the gateway, reconfigure it into one of the predetermined formats the management system can receive, and transmit. Dependent claim 20 narrows that format set to the group "a low level protocol, a call accounting record, and a private branch telephone system protocol."

Dependent-claim highlights: translator for a second-stage reformatting pass (claims 2 and 14; also 7 and 19 for the method); location data (claim 3); hotel property management system as the management system (claims 4, 8, 12, 16, 21); and storage of the reconfigured data at the management system with at least some data accessible by the computer (claims 5, 9, 17).

Technical substance worth flagging

The specification's central mechanism is protocol masquerading. Because deployed hotel property management systems already ingest data from point-of-sale systems, PBX systems, pay-per-view, and credit-card authorization servers, the gateway is configured to present its records as if it were a PBX. It emits a CAR containing month/day 310, extension/room 315, time 320, duration 325, charge 330, phone number 335, and routing code 340 — and, since network access involves no dialed number, the specification describes substituting a descriptive record for the phone-number field or inserting a "mock telephone number" so the PMS receives a complete record, and replacing non-numeric ASCII characters with numeral designations where needed. Named target systems include Micros Fidelio, HOBIC, and Autoclerk. The optional translator 53 is described as, in one embodiment, a Lodging Link II device from Protocol Technologies, Inc. (Scottsdale, AZ) converting to UHALL protocol.

Prior art cited on the face (17 references), notably: US 5,745,884 (Mobile Area Networks), US 5,852,812 and US 5,893,077 (Microsoft), US 5,987,430 (Atcom), US 6,119,160 (Cisco), US 6,208,977 (Apogee Networks), US 6,338,046 (Nokia), US 6,349,289 (Ameritech), plus non-patent items including Business Wire releases about Ascend/ATCOM-INFO, Atreus Systems/B2B Connect, Copper Mountain's hotel initiative, NetGame, and "Nomadix Joins Copper Mountain Networks."

Litigation posture (as found, not as legal conclusion)

Google Patents lists six Central District of California cases touching this patent: 2:07-cv-01946, 2:09-cv-08441, 2:10-cv-00381, 2:11-cv-02604, 2:14-cv-00322, and 2:14-cv-08256. Corresponding matters I verified: Nomadix, Inc. v. Second Rule LLC, No. 2:07-cv-01946 (C.D. Cal.); Nomadix, Inc. v. Hewlett-Packard Co., No. 09-cv-08441 (DDP/VBKx) (C.D. Cal.); Nomadix, Inc. v. Solutioninc Technologies Ltd., No. 2:10-cv-00381 (DDP/VBKx); and Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. 2:14-cv-08256 (DDP/VBKx). A separate Nomadix v. Guest-Tek Interactive Entertainment Ltd. matter, No. 2:16-cv-08033 (AB/FFMx), was a breach-of-license action in which Guest-Tek raised invalidity and filed IPRs against licensed patents.

Two claim-construction outcomes are directly on this patent, from the 2011 Nomadix v. Hewlett-Packard Markman ruling: the term "absent additional agents implemented by the computer" was construed as "absent additional special client software implemented by the computer for managing the communication between the computer and the gateway device" (defendants did not oppose Nomadix's construction), while "management system" and "physical location" were given no construction — the court declined defendants' attempts to require a physical link between gateway and management system, and declined to limit "physical location" to a communication port.

I also found a reference to an "Exhibit List, Petition for Covered Business Model (CBM), Review of U.S. Pat. No. 6,868,399," indicating a CBM petition was at least contemplated or filed against this patent. I could not confirm the petition number, whether it was instituted, or its outcome — treat that as unresolved.

CAFC 2026 docket search result

No CAFC 2026 docket entry specifically identifying U.S. Patent 6,868,399 was found. The 2026 Federal Circuit and district court materials my searches returned concerned unrelated patents and parties (e.g., 25-1306 Spero v. Mercedes-Benz USA; 25-1596 Wipqtus v. Samsung; Neonode Smartphone v. Apple, N.D. Cal. 3:21-cv-08872; Netlist v. Micron). Because the patent's adjusted expiration is December 21, 2021, the window for new infringement suits on it has closed, which is consistent with the absence of 2026 appellate activity. I state this as a search finding, not as proof of a negative.

I'll research litigation involving US Patent 6,868,399 across patent litigation databases.

Let me get details on each specific case and cross-check the litigation records.

Known Litigation Involving U.S. Patent 6,868,399

Important preliminary note (identifier integrity): Several search hits reference an "'839 patent" that is not U.S. 6,868,399. One PTAB document discusses an "'839 patent" with claims to a "selected torque value" and accuses "Ford's 3.5L EcoBoost engine" (with iBeacon/Apple references elsewhere) — that is a different patent whose number coincidentally ends in "839." I excluded those. All cases below were verified as asserting 6,868,399 (the Nomadix "network gateway / management system" patent).

The patent is a Nomadix, Inc. patent (now associated with Gate Worldwide Holdings LLC / Nomadix, Inc. after a chain of assignments, including NTT DOCOMO security interests). All identified litigation is offensive enforcement by Nomadix in the Central District of California (C.D. Cal.), before Judge Dean D. Pregerson (DDP) with Magistrate Judge Victor B. Kenton (VBK).

1. Nomadix, Inc. v. Second Rule LLC

• Plaintiff: Nomadix, Inc.
• Defendant: Second Rule LLC
• Jurisdiction: U.S. District Court, Central District of California
• Case No.: 2:07-cv-01946 (DDP/VBK)
• Filing Date: March 23, 2007
• Status/Outcome: Terminated March 31, 2009. Patents asserted included 6,130,892; 6,636,894; 6,857,009; 6,868,399; 7,088,727. An invalidity expert report on the '399 (among others) was served Oct. 31, 2008. No merits judgment on the '399 identified.
• Sources: Stanford NPE Litigation Database (https://npe.law.stanford.edu/patent/6868399 and case/121952).

2. Nomadix, Inc. v. Hewlett-Packard Company, et al.

• Plaintiff: Nomadix, Inc.
• Defendants: Hewlett-Packard Company and others; iBAHN Corporation (counterclaimant)
• Jurisdiction: C.D. Cal.
• Case No.: 2:09-cv-08441 (DDP/VBK)
• Filing Date: November 17, 2009
• Status/Outcome: Extensive litigation. The '399 was among the asserted patents and appeared in Defendants' supplemental joint invalidity contentions (Exhibit C6, claim comparison for U.S. 6,868,399, dated July 22, 2011). Key rulings:
  • Standing/indispensable-party motion (UC co-ownership) denied (May 7, 2012).
  • Partial summary judgment of non-infringement for HP's "Group 2" devices granted for HP (March 1, 2012).
  • Nomadix obtained summary judgment of non-infringement on iBAHN's counterclaim patents ('073 and '376) (Jan. 17, 2012).
  • Cause of action: Patent Infringement. The case was consolidated for pretrial purposes with 2:10-cv-00381. Ultimate case disposition (settlement/consent judgment) not confirmed in the retrieved records.
• Sources: Justia (2:09-cv-08441), CourtListener (838 F. Supp. 2d 962), Google Patents litigation links.

3. Nomadix, Inc. v. Solutioninc Technologies Limited

• Plaintiff: Nomadix, Inc.
• Defendant: SolutionInc Technologies Limited (also spelled "Solutioninc"), with iBAHN Corporation counterclaims
• Jurisdiction: C.D. Cal.
• Case No.: 2:10-cv-00381 (DDP/VBK)
• Filing Date: Complaint filed January 19, 2010
• Status/Outcome: Consolidated with 2:09-cv-08441 for pretrial purposes. A claim-construction (Markman) order issued October 24, 2011. Patents asserted included 6,130,892; 7,088,727; 7,554,995; 6,636,894; 7,194,554; 6,868,399; 6,789,110; 7,689,716; and 6,875,009. The '399 was addressed in Defendants' Supplemental Joint Invalidity Contentions (Exhibit C6, claim comparison for U.S. 6,868,399). Final disposition (e.g., settlement) not confirmed in the retrieved records.
• Sources: Stanford NPE Database; Justia; patent-family documents citing Case No. 2:10-CV-00381 (e.g., US 9,548,935 and US 10,367,748 file references).

4. Nomadix, Inc. v. Hospitality Core Services LLC, d/b/a Blueprint RF

• Plaintiff: Nomadix, Inc. (interested parties identified as DOCOMO interTouch / NTT DOCOMO)
• Defendant: Hospitality Core Services LLC d/b/a Blueprint RF
• Jurisdiction: C.D. Cal.
• Case No.: 2:14-cv-08256 (DDP/VBK)
• Filing Date: October 24, 2014
• Status/Outcome: Settled. The '399 was one of seven asserted patents (6,636,894; 6,868,399; 8,156,246; 8,266,266; 8,266,269; 8,364,806; 8,788,690). On Jan. 27, 2016, the court granted Nomadix's motion for summary judgment of infringement of the '246 patent and denied Blueprint's invalidity motions; Nomadix "prevailed" per IPWatchdog (Feb. 26, 2016). The parties then settled (confidential agreement executed June 13, 2016) and filed a joint stipulation to dismiss on June 28, 2016; the case was closed. Related IPRs (IPR2016-00052, -00073, -00077, -00081, -00092) were terminated.
• Sources: Justia/Casetext (2:14-cv-08256), Unified Patents docket, Docket Alarm (IPR2016-00081 joint motion to terminate), IPWatchdog.

5. Google Patents–listed cases with defendant not confirmed

The Google Patents litigation record for US 6,868,399 also lists two C.D. Cal. case numbers whose case captions I could not confirm from the retrieved sources:

• 2:11-cv-02604 — C.D. Cal. (defendant not identified in retrieved records)
• 2:14-cv-00322 — C.D. Cal. (this appears as a "related case" in the 2:14-cv-08256 docket; defendant not identified in retrieved records)

I am flagging these explicitly rather than guessing the parties. A PACER or Unified Patents portal lookup would be required to confirm plaintiff/defendant and outcome for these two.

Caveats and confidence

• Confidence: high that 6,868,399 was asserted in at least the Second Rule, HP/iBAHN, SolutionInc, and Blueprint RF (Hospitality Core Services) matters — all C.D. Cal., all Nomadix as plaintiff.
• Not confirmed: the final disposition/outcome of the HP/iBAHN (2:09-cv-08441) and SolutionInc (2:10-cv-00381) cases (settlement vs. judgment), and the parties in 2:11-cv-02604 and 2:14-cv-00322.
• Do not conflate with unrelated "'839" patents (e.g., the engine/torque patent litigated against Ford, and the iBeacon-related "'839" in PTAB proceedings) — those are different patents.
• The Google Patents page also lists a global litigation family (Darts-IP link) and six C.D. Cal. case links; the retrieved family data is consistent with the cases above.
• No Federal Circuit (CAFC) appeal specifically docketed on the '399 was identified in the retrieved materials (the CAFC/9th Cir. materials surfaced — e.g., Nomadix v. Guest-Tek, No. 20-55439 — concern other Nomadix patents/license disputes, and I did not confirm '399 was at issue there).

If you need PACER-confirmed dockets and outcomes for cases 4–5 above (and the two unconfirmed C.D. Cal. case numbers), those should be pulled directly from PACER or the Unified Patents litigation portal at https://portal.unifiedpatents.com/litigation/caselist.

I'll start by checking the canonical source (no proceedings on file per ODP) and then search for any older/unindexed AIA trials — particularly CBM reviews, given this patent's G06Q billing classifications and Nomadix's litigation history.

No AIA trial on the '399 patent surfaced yet — but I need to verify against PTAB dockets directly, since the '399 patent was heavily litigated (Nomadix v. HP, Nomadix v. Blueprint RF, Nomadix v. Second Rule) and its siblings did attract IPRs.

Let me run a few more targeted checks — CBM reviews on Nomadix's portfolio, and any reexamination certificate for the '399 patent (which would be a non-AIA challenge but relevant to a defendant).

PTAB / AIA Trial Analysis — U.S. Patent No. 6,868,399

Patent: Systems and methods for integrating a network gateway device with management systems
Patent Owner: Nomadix, Inc. (original); current assignee of record per Google Patents is Gate Worldwide Holdings LLC, with Nomadix, Inc. appearing as a post-2019 assignee/release holder.
App. No.: 09/693,061 | Priority: 1999-10-22 | Filed: 2000-10-20 | Issued: 2005-03-15
Claims: 21 (independent claims 1, 6, 10, 13, 18)
Status: Expired – Lifetime; legal status line shows expiration 2021-12-21

Proceedings overview

There are zero AIA trial proceedings on file for US 6,868,399 — no IPR, no PGR, no CBM — per the USPTO ODP "PTAB proceedings on file" block (0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denials), and my independent searches of PTAB dockets, the Unified Patents litigation portal, the Stanford NPE database, and contemporaneous PTAB filing reports surfaced no petition ever filed against this patent; the practical consequence for a defendant is that all 21 claims stand exactly as issued and have never been tested in an AIA trial, but the patent expired on 2021-12-21, so the offensive posture today is a historical-damages claim within the § 286 lookback window, not an injunction threat.

Caveat on the negative finding. The absence of PTAB activity is well corroborated by the affirmative record of other challenges to the Nomadix portfolio: when petitioner Hospitality Core Services, LLC (d/b/a Blueprint RF) filed five IPRs against Nomadix patents in October 2015, it listed the full set of patents at issue in the co-pending district court case, and the '399 patent was at issue in that litigation but was not among the patents petitioned. See Nomadix's mandatory notices, Hospitality Core Services, LLC v. Nomadix, Inc., IPR2016-00081, Paper 7 (filed 2015-11-17), available via Docket Alarm, IPR2016-00081. That is strong circumstantial evidence that sophisticated adversaries with claim charts in hand deliberately declined to petition on the '399 patent.

Proceedings on US 6,868,399

None. There is no proceeding to report. Per your instruction not to invent proceeding numbers, I am not creating placeholder sections. The per-proceeding fields you specified (petition grounds, institution decision, FWD claim-level disposition, settlement, appeal) have no content for this patent because no petition was ever filed.

For completeness on the three AIA vehicle types:

Adjacent records worth knowing (NOT proceedings on this patent)

Do not misread these as '399 challenges. They concern different patents but are the closest thing to a "pattern signal" here.

IPR2016-00052 / -00073 / -00077 / -00081 / -00092 — Hospitality Core Services, LLC (d/b/a Blueprint RF) v. Nomadix, Inc.

• Type: Inter Partes Review (five separate petitions)
• Filed: 2015-10-21 through 2015-10-22 (IPR2016-00052 filed 2015-10-21 per the PTO Litigation Center Report, 2015-10-22)
• Patents challenged: U.S. 6,636,894; 8,156,246; 8,266,266; 8,266,269; 8,364,806 — the '399 patent is conspicuously absent
• Context: All five patents were simultaneously asserted by Nomadix against Blueprint RF in Nomadix, Inc. v. Hospitality Core Services LLC, No. 2:14-cv-08256 (C.D. Cal.) — the same case in which the '399 patent was asserted (Unified Patents case page)
• Institution / FWD outcomes: I could not verify institution decisions or final written decisions for these five petitions with confidence from the sources retrieved, and I will not guess at them. They have no estoppel or preclusive effect on the '399 patent regardless of outcome.
• Defensive value for the '399 patent: Low direct value, high indirect value. It shows the invalidity theories Blueprint developed against the Nomadix family (ATCOM/IPORT white papers, MICROS-Fidelio, Short PCT WO 98/40990) were also charted against the '399 patent in district court — see Defendants' claim charts for U.S. 6,868,399 re: ATCOM/IPORT White Papers, dated 2015-07-24, and re: ATCOM 430 / MICROS-Fidelio / Short PCT, dated 2015-07-17, indexed at the Unified Patents US-10,341,243-B2 page.

Guest-Tek IPRs against Nomadix patents — petitions denied

• Reported disposition: On 2018-06-29, the PTAB denied Guest-Tek Interactive Entertainment's petitions for review of two Nomadix patents, finding Guest-Tek "failed to demonstrate a reasonable likelihood that it could show unpatentability of any of the claims." GlobeNewswire, 2018-07-02. Separately, Guest-Tek petitioned on U.S. 8,725,899 (Guest-Tek Interactive Entertainment Ltd. v. Nomadix, Inc.).
• Relevance to the '399: None directly — different patents — but it establishes that Nomadix prevailed on § 103 obviousness challenges to its gateway/PMS architecture family and that Nomadix is a litigious, well-resourced patent owner with a track record at the Board.

Ex parte / inter partes reexamination — no '399 reexamination found

• I found no reexamination certificate or reexamination proceeding for the '399 patent. The reexamination hits in the search results (e.g., Control No. 95/001,831, request filed 2011-11-18 against U.S. 6,636,894; Control No. 90/011,569 against U.S. 7,149,511) concern sibling and unrelated patents, not the '399. If a reexamination certificate exists for the '399, it was not surfaced here and I am not asserting one does.

District court validity posture on the '399 (relevant to any invalidity theory)

• The '399 patent survived claim construction intact and un-narrowed in Nomadix, Inc. v. Hewlett-Packard Co. (2011 Markman order, reported at 2011 WL 5037162): the court rejected defendants' proposed constructions of "management system" (defendants wanted a physically-linked, separate system) and "physical location" (defendants wanted a specific communication port), holding no construction required, and adopted Nomadix's construction of "absent additional agents implemented by the computer" as "absent additional special client software implemented by the computer for managing the communication between the computer and the gateway device." Full Markman order PDF
• In the later Blueprint RF summary judgment round (order dated 2016-01-27, No. 2:14-cv-08256), the court framed the validity dispute as to the '246, '266, '269, '806 and '690 patents — again, the '399 was not part of the validity adjudication. Order PDF
• Blueprint's inequitable conduct counterclaims specifically targeting the '399 (failure to submit WO 98/40990 and Kleinrock publications; misleading attorney arguments) were the subject of Nomadix's motion to dismiss/strike, granted in part on 2015-04-03. Casetext opinion

Strategic summary

Claim status of US 6,868,399. Independent claims 1, 6, 10, 13 and 18 and all dependent claims 2–5, 7–9, 11–12, 14–17, 19–21 are UNCANCELED and UNTESTED — there is no PTAB claim-level disposition of any kind, so nothing is "canceled," nothing is "sustained" by the Board, and no claims have been narrowing-amended. The patent's 21-claim set is exactly as it issued on 2005-03-15. Any statement that this patent "survived IPRs" is pedantically defensible but analytically wrong — surviving means a Board trial was run and claims were held patentable. That never happened here. What happened is that the patent sat outside the four corners of every petition filed against the Nomadix portfolio despite being asserted in the same district court cases as the petitioned patents.

Estoppel landscape — this is a defendant's rare advantage. Because no IPR was ever instituted against the '399, no § 315(e)(2) estoppel attaches to any petitioner or privy as to this patent. There is no petitioner who is barred from raising any ground it raised or reasonably could have raised. Every § 102/§ 103 ground that Blueprint, Guest-Tek, HP, Solutioninc, iBAHN or Second Rule developed — the ATCOM/IPORT white papers and ATCOM 430 manual, MICROS-Fidelio, Short PCT WO 98/40990, the Kleinrock publications, the 6,226,677 reference, and whatever else appears in the 2011 Supplemental Joint Invalidity Contentions — remains fully available in district court against the '399. What a defendant does lose is the ability to leverage someone else's Board proceeding: there is no FWD to point to, no canceled claim, no Board finding of unpatentability. The same clean slate cuts both ways — Nomadix likewise has no adverse PTAB holding to overcome.

Practical gating issues for a defendant today. Three things dominate over any invalidity theory. First, the patent expired 2021-12-21. Post-expiration, there is no injunctive relief and no ongoing royalty for post-expiration use; the entire exposure is past damages capped by the six-year lookback of 35 U.S.C. § 286, measured from the date the complaint is filed. Second, PGR is unavailable (effective filing date 1999-10-22, long before the 2013-03-16 AIA cutoff) and CBM is unavailable (window closed 2020-09-16), leaving IPR and ex parte reexamination as the only post-issuance PTO vehicles — and ex parte reexamination, unlike IPR, has no § 315(b) bar and no estoppel. Third, § 315(b)'s one-year bar: if a defendant has already been served with a complaint alleging infringement of the '399 more than one year ago, IPR is time-barred, and the realistic options are district court invalidity, ex parte reexamination (which any third party may request, and which carries no estoppel), or a reexam-based stay motion.

Pattern signals. No defensive aggregator (Unified Patents, RPX, etc.) appears anywhere in the chain — the '399 patent's challenges have come exclusively from operating-company competitors (BluePrint RF, Guest-Tek, HP, Solutioninc, iBAHN) and one prior licensee dispute, with no Unified Patents IPR on this patent. Nomadix has historically been on both sides of PTAB appeals: it defended its portfolio at the Board against Guest-Tek and Blueprint, and it litigated a forum-selection-clause/license dispute with Guest-Tek through the Ninth Circuit over whether Guest-Tek's PTAB petitions breached a license agreement (a contract appeal, not a Federal Circuit appeal of any FWD — no FWD exists for the '399 to appeal). Nomadix also monetized through the Nomadix/Gate Worldwide Holdings assignment chain and NTT DOCOMO security interests, and its patents were asserted across at least six C.D. Cal. cases: 2:07-cv-01946 (Second Rule, terminated 2009-03-31), 2:09-cv-08441 (HP), 2:10-cv-00381 (Solutioninc), 2:11-cv-02604 (iBAHN, as defendant), 2:14-cv-00322 (iBAHN), and 2:14-cv-08256 (BluePrint RF). See Stanford NPE Database and the Google Patents litigation links at US6868399B1.

Recommended next steps

If you are a defendant facing assertion of the '399:

1. Confirm expiration as your lead argument, before touching invalidity. The Google Patents legal-status line states "Expired – Lifetime, expires 2021-12-21." Verify the exact term against the front-page patent term adjustment and any terminal disclaimer on the face of the printed patent, then compute the § 286 window from your complaint's filing date. Any demand letter asserting ongoing or prospective royalties for post-2021-12-21 conduct is legally describing relief the statute no longer permits.

2. Do not overstock your defense with a nonexistent PTAB win. There is no FWD to quote and no canceled claim to point at. If opposing counsel or a demand letter implies the patent has been tested and survived at the Board, the accurate response is that it has never been petitioned — the Board has said nothing about this patent, and the "survival" framing is a rhetorical claim, not a record fact.

3. Verify the negative with primary sources before relying on it. Because the ODP block is your canonical list, run a fresh E2E/PTAB docket search yourself — USPTO PTAB E2E and the Patent Public Search reexamination records — filtered on "6868399," and pull the full prosecution/reexam history via the USPTO PatentCenter file wrapper for App. No. 09/693,061. Also confirm whether any reexamination certificate exists (I found none, but the file wrapper is definitive).

4. Recycle the prior art, but re-verify each reference. The 2011 Supplemental Joint Invalidity Contentions claim charts for the '399 (Exhibit C6, dated 2011-07-22) and the 2015 Blueprint charts re: ATCOM/IPORT, MICROS-Fidelio and Short PCT are a ready-made starting set. None of it is estopped, and none of it was adjudicated. Note the critical date for § 102(b) art is 1998-10-22 (one year before the 1999-10-22 priority date), so anything published before that date is fair game.

5. Consider ex parte reexamination rather than IPR if you are outside § 315(b). If you have been served more than one year ago, IPR is barred; ex parte reexamination under 35 U.S.C. § 302 has no time bar and no estoppel, costs far less, and routinely supports a stay motion — but it acts on only the claims you identify and cannot reach § 112 or public-use/on-sale grounds.

6. Mine the 2011 Markman order and the 2016 Blueprint SJ order for your construction strategy. The '399's key limitations — "management system," "physical location," and "absent additional agents implemented by the computer" — were construed in Nomadix's favor in Nomadix v. Hewlett-Packard (2011), which cuts against you on infringement but leaves the door open on § 103 obviousness, since broad constructions typically enlarge the prior-art field. Full order: 2011 WL 5037162 PDF. The Blueprint SJ order (2016-01-27) is here: No. 2:14-cv-08256, Doc. 142.

If a PTAB filing is contemplated on a sibling patent (e.g., any surviving Nomadix gateway patent with a post-2013 effective filing date), re-run this analysis per patent — the portfolio-wide picture above (five Blueprint IPRs, Guest-Tek petitions denied 2018-06-29) applies to other members of the family, not to the '399.

Confidence and source limitations. The zero-proceeding finding is stated at high confidence for the period the ODP index covers and is corroborated by the absence of the '399 from every contemporaneous petition list I retrieved; a very recently filed petition not yet indexed cannot be categorically excluded, which is why step 3 above is a direct E2E docket check rather than an inference. I did not verify institution decisions or FWDs for IPR2016-00052/-00073/-00077/-00081/-00092, and I make no representation about their outcomes; they do not affect the '399 regardless. No Federal Circuit appeal of any '399 proceeding exists because no proceeding exists. All litigation citations above are to publicly posted orders and dockets linked inline.

I'll research the assignment record, litigation history, and entity background before building the analysis.

Ownership Chain Analysis — US Patent 6,868,399 B1

Methodological note / limitation up front (important): Two data fields you asked for — reel/frame and correspondent of record — are not exposed by any source I could reach. The Google Patents "Legal Events" reassignment table (which mirrors the USPTO assignment dataset) reports assignor, assignee, conveyance type, and a processing date, but strips the reel/frame and correspondent fields. I could not pull the raw USPTO Assignment Center (https://assignmentcenter.uspto.gov) records interactively. I have therefore not invented reel/frame numbers or correspondent names. Where those fields are required below, they are marked [not retrieved]. The conveyance chronology itself is grounded in recorded USPTO data as surfaced by Google Patents.

Inventors

Unusual-pattern check: No "all inventors exit within 12 months" pattern is discernible — the inventors assigned to Nomadix and the company retained the patent and litigated on it for ~15 subsequent years (see NPE signals below). Note one name-discrepancy flag: the recorded assignment spells the second inventor "PERELYBUSKIY, DENIS I." (transposed letters) whereas the patent names "Perelyubskiy." This is a recording typo in the USPTO assignment abstract, not a different person, but it is worth carrying forward if the chain is ever challenged on standing/derivation.

No evidence recovered that either inventor left Nomadix within 12 months of filing; I do not have departure dates, so I will not assert a fire-sale precursor.

Original assignee

Nomadix, Inc. (Woodland Hills / Agoura Hills, California; founded 1998).

• Product embodying the claims? Yes. Nomadix shipped network gateway hardware — the AG 2000 / AG 2100 / AG 2300 / AG 2400 / AG 3000 / AG 3100 / AG 5000 series, NITO 500 / 1500, USG, USG II, HSG — and its own published "Nomadix Products / Patent Listing" expressly lists 6,868,399 among patents that "may be covered by" those products. This is a direct, self-declared product-to-patent link.
• Primary line of business: Visitor-based / hospitality network gateways and managed Wi-Fi access (hotels, airports, venues).
• Current status: Operating, acquired. Corporate history: acquired by Singapore-based MagiNet (Dec 2006) → MagiNet acquired by DOCOMO interTouch Pte. Ltd. (NTT DOCOMO subsidiary, Dec 2007, ~$150M) → later within the Gate Worldwide Holdings / GWHSPV, LLC corporate family → acquired by Assa Abloy (March 2024). As of the 2024 Assa Abloy deal the Nomadix business is a live operating subsidiary. No bankruptcy of the original assignee was found.

Assignment timeline

Chronology below is reconstructed from the Google Patents Legal Events reassignment table (USPTO-sourced). Dates are the recorded/processed dates as published; execution dates were not exposed by the source.

1. Executed date [not retrieved] / recorded 2001-02-01 — Reel [not retrieved]

   • Conveyance: Assignment of Assignors' Interest (original inventor→company assignment)
   • Assignor: Perelybuskiy, Denis I.; Short, Joel E. (sic — recorded misspelling of "Perelyubskiy")
   • Assignee: Nomadix, Inc.
   • Correspondent: [not retrieved] — cannot assess recurrence without the raw record
   • Context: founder/inventor assignment to the startup at/around filing. Standard for a VC-backed operating company.

2. Executed date [not retrieved] / recorded 2015-09-30 — Reel [not retrieved]

   • Conveyance: Security Interest (patent security agreement)
   • Assignor: Nomadix, Inc.
   • Assignee: NTT DOCOMO, Inc.
   • Correspondent: [not retrieved]
   • Context: securitization — Nomadix pledged the portfolio as collateral to its then-corporate parent/affiliate NTT DOCOMO. Not an ownership sale.

3. Executed date [not retrieved] / recorded 2017-08-29 — Reel [not retrieved]

   • Conveyance: Modification to Patent Security Agreement
   • Assignor: Nomadix, Inc.
   • Assignee: NTT DOCOMO, Inc.
   • Correspondent: [not retrieved]
   • Context: amendment of the 2015 security interest — consistent with an ongoing financing/credit relationship, i.e., continued securitization.

4. Executed date [not retrieved] / recorded 2018-01-23 — Reel [not retrieved]

   • Conveyance: Assignment of Patent Security Agreement
   • Assignor: NTT DOCOMO, Inc.
   • Assignee: Gate Worldwide Holdings LLC
   • Correspondent: [not retrieved]
   • Context: securitization transfer — the secured party's position moves from DOCOMO to Gate Worldwide Holdings. This is the debt/collateral side, not a sale of the patent.

5. Executed date [not retrieved] / recorded 2018-01-23 — Reel [not retrieved] (same day as #4)

   • Conveyance: Assignment of Assignors' Interest
   • Assignor: Nomadix, Inc.
   • Assignee: Gate Worldwide Holdings LLC
   • Correspondent: [not retrieved]
   • Context: internal corporate reorganization / equity-family restructuring — Gate Worldwide Holdings is the disclosed parent of GWHSPV, LLC, which is the parent of Nomadix, Inc. (per Nomadix's own Fed. R. Civ. P. 7.1 corporate-interest filing in Nomadix, Inc. v. SIA Mikrotikls et al., No. 2:19-cv-10202, C.D. Cal., Dec. 2, 2019). This is a within-family holding transfer, not a transfer to an unrelated licensing shell.

6. Executed date [not retrieved] / recorded 2019-03-20 — Reel [not retrieved]

   • Conveyance: Security Interest
   • Assignor: Nomadix, Inc.
   • Assignee: Knobbe, Martens, Olson & Bear, LLP
   • Correspondent: [not retrieved]
   • Context: securitization (fee/lien) — a law-firm secured interest granted by Nomadix. This is an unusual but not unknown arrangement (security for unpaid legal fees / financing), and it is a strong marker of cash-flow distress around 2019. It was released three months later (see #7).

7. Executed date [not retrieved] / recorded 2019-05-28 — Reel [not retrieved]

   • Conveyance: Release by Secured Party
   • Assignor: Knobbe, Martens, Olson & Bear, LLP
   • Assignee: Nomadix, Inc.
   • Correspondent: [not retrieved]
   • Context: release of the #6 security interest — lien satisfied/withdrawn.

8. Executed date [not retrieved] / recorded 2019-11-22 — Reel [not retrieved]

   • Conveyance: Quitclaim
   • Assignor: Gate Worldwide Holdings LLC
   • Assignee: Nomadix, Inc.
   • Correspondent: [not retrieved]
   • Context: internal corporate reorganization (reversal) — the 2018 in-family assignment of interest (event #5) is quitclaimed back to Nomadix, Inc., restoring the operating company as record owner.

Discrepancy flag: Google Patents' "Current Assignee" field still displays Gate Worldwide Holdings LLC, even though the last recorded event (#8, 2019-11-22) is a quitclaim to Nomadix, Inc. The most likely reconciliation is that "current assignee" is being reported at the corporate-parent level (Gate Worldwide Holdings LLC → GWHSPV, LLC → Nomadix, Inc., per Nomadix's own 2019 court filing), while the record owner chain terminated at Nomadix, Inc. Verify against the live Assignment Center before relying on either label.

Timeline diagram

timeline
    title Ownership of US 6868399
    1999 : Priority date 22 Oct 1999
    2000 : Application filed by Nomadix
    2001 : Inventors assign to Nomadix Inc
    2005 : Patent issued 15 Mar 2005
    2015 : Security interest to NTT DOCOMO
    2017 : Security agreement modified
    2018 : Secured interest to Gate Worldwide
         : Nomadix assigns interest to Gate
    2019 : Knobbe Martens security interest
         : Release by secured party
         : Quitclaim back to Nomadix
    2021 : Patent term expires 21 Dec 2021
    2024 : Nomadix acquired by Assa Abloy

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT (weakest sub-tell: minor).
   The only candidate is the 2018-01-23 assignment of interest to Gate Worldwide Holdings LLC. However, that entity is not an anonymous licensing shell: Nomadix's own 2019 court filing identifies AWB/“GWHSPV, LLC, Parent Company of Nomadix, Inc.; and Gate Worldwide Holdings LLC, Parent Company of GWHSPV, LLC.” It is the disclosed corporate parent, and the interest was quitclaimed back to Nomadix, Inc. on 2019-11-22. No registered-agent-only address, no single-purpose licensing LLC, no product-free suffix entity is evidenced in the recovered record. Not a shell transfer.

2. Known asserter in the chain — NOT PRESENT.
   No link to Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, DGC, or any Spangenberg entity. The chain names are Nomadix, Inc. (operating), NTT DOCOMO, Inc., Gate Worldwide Holdings LLC (Nomadix's parent), and Knobbe, Martens, Olson & Bear, LLP (a law firm, secured party only). Nomadix is a high-frequency patent plaintiff, but it is a product-shipping operating company, not a classic NPE.

3. Repeat correspondent across the chain — [INSUFFICIENT DATA].
   The correspondent-of-record field could not be retrieved for any of the eight events, so recurrence cannot be demonstrated or ruled out. This is the single most important gap and the reason a live Assignment Center pull is required. I will not name a correspondent I did not verify.

4. Cascading transfers — PARTIAL / WEAK.
   There were five recordings within a 22-month window (2018-01-23 → 2019-11-22), and the 2015→2017→2018 sequence is also dense. But these are not chained LLCs sharing a correspondent; they are one corporate family restructuring plus two security interests and a release, with the asset returning to the operating company. This is a securitization/reorg cascade, not an assertion-driven shell cascade.

5. Pre-litigation transfer — NOT PRESENT.
   The '399 patent was already in suit long before the 2015-2019 recordings: it was asserted in Nomadix, Inc. v. Hewlett-Packard Co. et al., No. 09-cv-08441 (C.D. Cal.) and appears in the 2011 Markman record (Nomadix v. Hewlett-Packard, 2011), and again in Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. 2:14-cv-08256 (C.D. Cal.) (one of seven asserted patents). The 2015–2019 assignments post-date the first assertions, so no pre-suit transfer-to-enable-assertion pattern exists.

6. Bankruptcy fire-sale — NOT PRESENT (distress indicators present, bankruptcy absent).
   No Chapter 7/11 proceeding for Nomadix was found. However, the 2019-03-20 Knobbe Martens security interest and the 2015/2017 NTT DOCOMO security interests indicate creditor liens on the portfolio, and Nomadix took a PPP loan (April 2020) — consistent with financial stress, but not a judicial sale of patents.

7. Privateering — NOT PRESENT.
   NTT DOCOMO held only a security interest, and the corporate-family transfers went to Nomadix's own parent, not to an NPE asserting against the operating company's competitors. Nomadix asserted its own patents (e.g., MikroTik, Guest-Tek, Blueprint RF, iBAHN, HP, SolutionInc).

8. Defensive aggregator — NOT PRESENT.
   The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. Nomadix remained an active plaintiff (e.g., 2019 suit against SIA Mikrotikls; 2020 Ninth Circuit appeal in Nomadix v. Guest-Tek, No. 20-55439).

Verdict

Operating-company assertion.

Justification: the original assignee, Nomadix, Inc., is a product-shipping operating company whose own published product/patent listing names 6,868,399 as covering its AG-series gateways, and it asserted the '399 patent against competitors including HP (09-cv-08441), Blueprint RF/Hospitality Core Services (2:14-cv-08256), iBAHN (14-cv-00322), and the Guest-Tek campaign — the hallmark of an operating-company patent suit, not an NPE licensing play. The recorded chain after 2001 consists entirely of securitization events (NTT DOCOMO security interests 2015/2017; Knobbe Martens security interest 2019 and its release) plus a within-corporate-family assignment to the disclosed parent Gate Worldwide Holdings LLC (2018-01-23) that was quitclaimed back to Nomadix, Inc. on 2019-11-22 — no shell LLC, no known asserter, and no defensive aggregator appears. Caveats: (a) the reel/frame and correspondent fields could not be verified and should be pulled from the Assignment Center before this is treated as final; and (b) the patent expired 2021-12-21, so assertion is moot going forward regardless of chain.

Verification link: https://assignmentcenter.uspto.gov/ — search patent number 6868399 (also mirrored at https://patents.google.com/patent/[US6868399B1](/patent/US6868399B1) under "Reassignment / Legal Events").

I'll research the USPTO record for US 6,868,399 and examine each cited reference. Let me run several searches.

I have good detail on several references. Let me research the remaining cited references.

Verification of the record for US 6,868,399

I confirmed the target patent's identity and front matter via Justia, Google Patents, USPTO.report, and the Golden wiki mirror. This matches the bibliographic data already generated in the prior section, so I will not repeat it. Key facts carried forward:

• US 6,868,399 B1, Systems and methods for integrating a network gateway device with management systems, App. 09/693,061, filed 2000-10-20, priority 1999-10-22, issued 2005-03-15, inventors Short & Perelyubskiy, original assignee Nomadix, Inc.
• The examiner-conducted search produced 17 patent citations and 6 non-patent citations (the Business Wire releases and the Schoen et al. World Telecom Congress paper already noted).
• The claims at issue are 1–21, with five independents: 1, 6, 10, 13, 18.

Scope/caveat: I grounded the citation list on the patent's own face (authoritative). I obtained full text for a subset (US 5,745,884; US 6,119,160; US 5,984,730; US 5,852,812; and the 6,868,399 claims). For the remaining references I rely on title, dates, and assignee as they appear in the patent's citation table, and I flag where I could not pull the full specification. I did not locate a USPTO examiner name for 6,868,399 within budget, so I do not assert one.

Anticipation framework (§ 102)

A single reference anticipates a claim only if it discloses every limitation, arranged as in the claim. The independent claims here each carry at least one limitation that is unusual and narrow:

1. Clientless operation — "communicates with the computer absent additional agents implemented by the computer," construed in the 2011 Nomadix v. Hewlett-Packard Markman as "absent additional special client software implemented by the computer for managing the communication between the computer and the gateway device."
2. CAR / PBX masquerading (claims 1 and 6 only): "formats the data into call accounting record format."
3. Management-system identity/direction — a billing/property management system that either receives the record (claims 1, 6) or initiates communication to control access (claims 10, 13, 18).

Because of limitation (2) in particular, no cited reference appears to anticipate independent claims 1 or 6 — none of the 17 references, on their face, discloses a network gateway reformatting usage data into call accounting record format for a property management system. The cited art is materially useful as § 103 obviousness material and for the protocol/location sub-limitations, not as clean § 102 art. I detail this below rather than overclaiming.

The 17 cited patent references

Metadata below is taken from the patent's own citation table (authoritative). Descriptions and § 102 assessments are my analysis; where I did not retrieve full text, the description reflects title/abstract only and is marked accordingly.

Group A — Closest to the disputed limitations

1. US 5,745,884 A — Carnegie et al., Mobile Area Networks, Inc.
System and method for billing data grade network use on a per connection basis. Priority 1996-10-21; published 1998-04-28.

• Substance (full text reviewed): Billing data-grade (>64 kbps) network use per user/per connection. Identifies the remote user by originating modem or caller identity; explicitly associates physical location ("in a hotel room, the physical location of the modem-equipped computer is associated with the hotel room number") and airport-lounge/credit-card access. Notes gateway resource functionality and the need for per-user billing on public data-grade networks.
• § 102 relevance: The best candidate for a location-keyed billing concept. Touches the subject matter of claims 13/18 (billing based on physical location) and claim 3 (location data). But it does not disclose a network gateway device formatting a record into call accounting record format (claims 1/6) or a hotel property management system that drives the gateway (claims 4, 10–21). It also relies on PSTN/caller-ID identification rather than the "absent additional agents" clientless gateway architecture. No full anticipation of any independent claim; relevant to dependent location limitations and as § 103 art.

2. US 6,119,160 A — Zhang et al., Cisco Technology, Inc.
Multiple-level internet protocol accounting. Priority/filing 1998-10-13; published 2000-09-12. (Continuation: US 6,792,457.)

• Substance (full text reviewed): A gateway device at a network access point generates IP accounting start/stop requests (account logon, service establishment, PPP connection) and communicates them to an accounting (AAA) server using RADIUS, a "standard Internet protocol." Tracks duration and byte count; the server stores records and matches start/stop pairs.
• § 102 relevance: This is the closest art on the generic architecture of claims 1 and 6 — a gateway maintaining "data representative of the user's access to the computer network" and transmitting it to a management/accounting system over a predetermined protocol (RADIUS could map to claim 11/15's "low level protocol"). But it fails the CAR-format limitation of claims 1/6, and it discloses neither a hotel PMS nor the "absent additional agents" clientless framing, and no physical-location-based billing (claims 13/18). Not anticipatory; strong § 103 art against the data-collection-and-transmission core.

3. US 5,987,430 A — Van Horne et al., Atcom, Inc.
Communications network connection system and method. Priority 1997-08-28; published 1999-11-16.

• Substance (partial full text reviewed): High-speed public-place network access (e.g., hotel/airport) via specialized access ports linked to a server; describes client software 90 on the user device and a network management server performing billing transaction processing and usage reporting. (US 6,128,601, an Atcom continuation, corroborates the "client software" architecture.)
• § 102 relevance: Directly relevant to the environment of the claims (public-place gateway; billing). Critically, its reliance on client software 90 is the opposite of claim 1/6's "absent additional agents implemented by the computer," so it actually cuts against those independent claims and is more naturally prior art that the applicants distinguished. It does not disclose CAR-format generation or a hotel PMS. Not anticipatory.

4. US 5,852,812 A — Reeder, Microsoft Corporation.
Billing system for a network. Priority 1995-08-23; published 1998-12-22.

• Substance (abstract/claims reviewed): Real-time billing for on-line networks via event objects; billable events "can include access to premium services, file downloads or gateway connections to other systems"; charges posted to a customer's on-line charge statement. Claims recite "an event generator providing… events indicative of network access."
• § 102 relevance: Relevant to the billing-event generation / automatic-billing elements shared by claims 1, 6, 13, 18. No CAR format, no gateway-device-as-formatter, no PMS, no clientless framing. Not anticipatory; § 103 art for the billing element.

5. US 5,893,077 A — Griffin, Microsoft Corporation.
Method and apparatus for generating and collecting a billing event object within an on-line network. Priority 1995-08-23; published 1999-04-06.

• Substance: (description from title/abstract metadata only) Generation and collection of billing-event objects in an on-line network.
• § 102 relevance: Overlaps the billing-event data concepts in claims 1/6/13/18. Same deficiencies as US 5,852,812. Not anticipatory.

Group B — Access-control / policy and accounting art

6. US 5,950,195 A — Stockwell et al., Secure Computing Corporation.
Generalized security policy management system and method. Priority 1996-09-18; published 1999-09-07.

• § 102 relevance (metadata only): Policy-based access control. Touches the claim 10 "control a user's access… and a physical location's access" concept (management system initiate-communication-to-control was the disputed upstream direction). Does not disclose CAR/PMS/gateway formatting. Not anticipatory; possible § 103 art for claim 10's access-control limitation.

7. US 6,348,289 B1 — Ameritech Corporation.
Method and system for tracking computer system usage through a remote access security device. Priority 1998-01-16; published 2002-02-19.

• § 102 relevance (metadata only): Tracking computer-system usage via a remote access security device. Relevant to "maintains data representative of the user's access" (claims 1, 6, 10, 13, 18) but not to CAR formatting or PMS. Not anticipatory.

8. US 6,208,977 B1 — Apogee Networks, Inc.
Accounting and billing based on network use. Priority 1998-12-04; published 2001-03-27.

• § 102 relevance (metadata only): Network-use accounting/billing. Same category as US 6,119,160 and US 6,348,289. Not anticipatory.

9. US 6,338,046 B1 — Saari et al., Nokia Telecommunications, Oy.
System and method for determining charges for usage of a network connection. Priority 1997-10-06; published 2002-01-08.

• § 102 relevance (metadata only): Usage-based charging for a network connection. Relevant to the usage-based billing element of claims 13/18. No CAR/PMS/clientless. Not anticipatory.

Group C — Telephone/toll/telecom billing and network-access infrastructure

10. US 5,802,502 A — British Telecommunications PLC.
System for selective communication connection based on transaction pricing signals. Priority 1993-05-24; published 1998-09-01. — Marked as * cited by examiner. Pricing-driven connection selection. Peripherally relevant to billing-rate flexibility; not to the gateway/CAR/PMS architecture. Not anticipatory.

11. US 5,864,610 A — AT&T Corp.
Interactive and information data services telephone billing system. Priority 1995-09-22; published 1999-01-26.

• § 102 relevance (metadata only): Telephone-service billing. Of interest because the patent's mechanism bills network access through the hotel telephone/CAR billing channel; the AT&T reference shows the telephone billing lineage but not the gateway-generated CAR-for-network-access idea. Not anticipatory, though conceptually adjacent to the CAR/PBX masquerade.

12. US 5,612,730 A — Multimedia Systems Corporation.
Interactive system for a closed cable network. Priority 1995-03-03; published 1997-03-18. — Closed-network interactive services. Peripheral; hotel/closed-network heritage art. Not anticipatory.

13. EP 0762707 A2 — Telia AB.
Arrangement for network access via the telecommunication network by remote-controlled filter. Priority 1995-08-21; published 1997-03-12. — Filter-controlled network access. Peripheral to access gating. Not anticipatory.

14. WO 1998016044 A1 — Mitel Corporation.
Remote on-demand applications server. Priority 1996-10-07; published 1998-04-16. — Remote application provisioning. Peripheral to gateway services. Not anticipatory.

Group D — Peripheral / arguably non-material to these claims

15. JP 2000354127 A — Ricoh Co. Ltd.
Control method for real-time Internet facsimile communication system. Priority 1999-06-11; published 2000-12-19. — Internet facsimile control. Only tenuously relevant (real-time Internet communication control); no billing/PMS/gateway-CAR teaching. Not anticipatory.
Note: Its 1999-06-11 priority predates the target's 1999-10-22 priority, so it is prior art under § 102(a)/(b) by date even though it is not close in subject matter.

16. US 6,496,850 B1 — Accenture LLP.
Clean-up of orphaned server contexts. Priority 1999-08-31; published 2002-12-17. — Server session cleanup. Appears in the citation list primarily as general network-server prior art; no billing/CAR/PMS teaching. Not anticipatory.

17. JP 2002111870 A — Toshiba Corp.
Communication system, mobile terminal device, gateway device, and communication control method. Priority 2000-09-28; published 2002-04-12.

• Critical date issue: Its 2000-09-28 priority is after the target's 1999-10-22 priority date, and after the target's 2000-10-20 filing. It therefore cannot be § 102 prior art against 6,868,399 on the dates shown in the table; if it is relied on at all it would have to be as an "A" reference or under a different statutory basis. I flag this date asymmetry explicitly. Not anticipatory.

Ranked § 102 candidacy summary

Bottom line for the § 102 question

1. No single cited reference anticipates any independent claim (1, 6, 10, 13, or 18). The decisive missing limitations across the board are (a) the gateway's formatting of usage data into call accounting record format (claims 1 and 6) and (b) integration with a hotel property management system including the upstream "management system initiates communication" direction (claims 4, 10–12, 16, 21).
2. The cited art's real value is § 103 obviousness, especially the combination of a gateway-to-AAA accounting architecture (US 6,119,160) with location-keyed, per-connection billing (US 5,745,884) and on-line billing-event collection (US 5,852,812 / US 5,893,077) — which together map onto the location+usage+automatic-billing elements of claims 13/18, but still reach neither the CAR/PBX masquerade nor the clientless limitation.
3. Date caveat to flag to downstream reviewers: JP 2002111870 A (2000-09-28 priority) is post-priority relative to 6,868,399 and is not § 102 art on the listed dates. Also, consistent with the earlier-generated summary, the CBM petition against 6,868,399 remains unresolved (petition number/institution not confirmed), so I cannot report whether any of these references were actually asserted in a validity challenge.

What I could not verify within budget (stated rather than guessed): full specification text for US 5,893,077, US 5,864,610, US 5,802,502, US 5,612,730, US 5,950,195, US 6,348,289, US 6,208,977, US 6,338,046, US 6,496,850, EP 0 762 707, WO 98/16044, JP 2000354127, and JP 2002111870. My characterizations of those are limited to their titles/abstracts as reflected in the patent's citation table and should be re-verified against the full texts before being relied on in any invalidity contention.

I'll ground this analysis in the actual prior-art references listed on the patent's face before mapping them to the claim elements.

Let me pull the remaining key references — the AT&T telephone-billing patent, the Cisco IP-accounting patent, and check for any PTAB/CBM record on the '399 itself.

Obviousness Analysis — U.S. Patent 6,868,399 under 35 U.S.C. § 103

Analyst note / methodology. This analysis uses the 17 patent references and 6 non-patent items listed in the "Prior Art" sections of the patent's Google Patents page (Citations, Cited By, Non-Patent Citations), and builds on the claim charts and Markman findings already generated in the prior sections of this file rather than repeating them. I retrieved the full printed text of several references (US 5,745,884; US 6,349,289; US 6,208,977; US 5,864,610; US 5,987,430's family) but for others I am working from title, assignee, priority date, and abstract/front-matter only. Where my mapping rests on title/abstract rather than full text, I label it inferred. Nothing here is a legal conclusion; it is a preliminary invalidity opinion for further testing.

1. Governing framework

• Statute: The application was filed October 20, 2000, and claims priority to six provisionals all filed October 22, 1999. It is therefore a pre-AIA patent. Pre-AIA § 103(a) governs, and the pre-AIA § 102 categories (including § 102(b) and § 102(e)) define what qualifies as prior art. Pre-AIA § 103(c)'s common-ownership exception is potentially in play for the applicant's own family members (discussed in § 8).
• Standard: Graham v. John Deere factors (scope/content of the art; differences; PHOSITA level; secondary considerations), applied through KSR Int'l v. Teleflex (obvious to try; predictable combination of known elements; "design incentives and other market forces"; any need or problem known in the field can supply the motivation).
• Admissions as prior art: Critically, the '399 specification itself admits much of the environment — that deployed hotel property management systems (PMS) already communicate with point-of-sale, PBX, pay-per-view, and credit-card authorization systems over serial/modem/dedicated links; that PMSs are "generally configured to receive such communications"; that the gateway can be made to look like a third-party device the PMS "is designed to receive"; and that Micros Fidelio, HOBIC, Autoclerk, and the Lodging Link II translator exist. Under In re Fout / MPEP 2129 these statements are usable as admitted prior art, which materially narrows the inventive gap.

Probable PHOSITA: a person with a B.S. in EE/CS or equivalent and ~2–4 years designing network access/authentication or hospitality-network systems, familiar with (a) user metering and billing records for data networks, (b) hotel PMS integration conventions and PBX/call-accounting-record (CAR) formats, and (c) serial/line-protocol integration of peripheral equipment to PMS.

2. Reference inventory and its actual prior-art status

Non-patent literature: Schoen et al., Convergence Between Public Switching and the Internet, XVI World Telecom Congress Proc. 549–560 (Sept. 21, 1997) → § 102(b). The Business Wire items dated June 16 and June 22, 1999 (NetGame; Ascend/ATCOM-INFO) → § 102(b)/printed publications. The December 6, 1999 (Copper Mountain; Nomadix/Copper Mountain) and February 14, 2000 (Atreus/B2B Connect) items postdate the 1999-10-22 priority date and are usable mainly as state-of-the-art/motivation evidence, not as § 102 art unless the priority claim fails for the relevant subject matter — a point a challenger should test, because if the Oct. 22, 1999 provisionals do not support the CAR-format limitations, the critical date shifts toward Oct. 20, 2000.

Two facts worth stating plainly: (i) "Cited" ≠ "prior art." Two of the 17 listed references (the two Japanese publications) appear to postdate the critical date and should not be relied on in a § 103 combination without a priority analysis. (ii) I could not complete my check of whether a CBM petition was actually filed/instituted against the '399 (my search was cut off); the previously generated litigation summary already flags this as unresolved, and I do not upgrade it here. Note the CBM program sunset on Sept. 16, 2020 and the patent expired Dec. 21, 2021, so § 103 challenges now live in district court, not the PTAB's CBM track.

3. Claim 1 (system; CAR-format billing) — claim-element mapping

Combination A — Atcom '430 + Mobile Area Networks '884 + AT&T '610 (optionally + Apogee '977 or Ameritech '289).

• Why combine: US 5,745,884 expressly frames the problem the '399 claims to solve — that for data-grade networks "there is currently no satisfactory per user, per connection billing system," that such a system "will become highly advantageous to operators of such networks," and that in a hotel room "the physical location of the modem-equipped computer is associated with the hotel room number," with charges "accrued to the phone location" plus "additional surcharges (such as airport access, hotel, etc.)." That is the motivation, the venue (hotel/airport), the location-based identification, and the telephone-billing channel in a single reference. US 5,987,430 supplies the hotel/public-access high-speed network with a server and a network-management server that already performs "billing transaction processing… and usage statistical reporting." AT&T '610 supplies the bridge: it teaches billing for data/information services (not voice) by associating the user's network address with a telephone billing record charged to the user's telephone account — i.e., it makes the telephone-billing artifact the vehicle for data-service charges.

Combination B — Mobile Area Networks '884 + Apogee '977 + AT&T '610 + the '399's own admitted PMS/PBX art.

• Why combine: '884 supplies per-user/per-connection network-access billing and room-number identification; Apogee '977 supplies the metering architecture (distributed collection units accumulate traffic data; a subsystem computes a price and transmits the bill); AT&T '610 supplies the telephone-record billing vehicle; and the '399 specification itself supplies the admission that hotel PMSs already accept PBX call-accounting data. Under KSR, once the PMS's existing PBX/CAR interface is admitted prior art, presenting network-access charges as a PBX-style call record is "a predictable variation" using "a known technique to improve similar devices in the same way."

Combination C (alternative for the CAR element) — any of A/B + Microsoft '077 / Microsoft '812. Microsoft '077 teaches generating and collecting a standardized billing-event object across an on-line network — a teaching that usage records are formatted to a defined schema for downstream rating/billing. A POSITA would predictably adapt that schema to the PMS's CAR schema.

4. Claim 10 (management system drives the gateway) — mapping

Claim 10 turns the flow upstream: the management billing system "initiates communication with the gateway device to control a user's access… and a physical location's access," and the gateway maintains data on the user's physical location plus access.

Combination D — Secure Computing '195 + Telia EP 0 762 707 + Ameritech '289 (or Mobile Area Networks '884).

• Why combine: '195 teaches that a central policy/management authority can push policy down to distributed enforcement points — the ordinary AAA/RADIUS model (the specification itself points to the Short/Pagan "Dynamic Network Authorization, Authentication and Accounting" application). EP 0 762 707 teaches that access over a telecom network can be gated by a remotely controlled filter — a management-driven gate on network access. Ameritech '289 supplies the gateway-side usage log and automated billing record. Combining a management-driven policy/filter function with a usage-logging gateway that bills through the PMS yields claim 10's upstream control with predictable results — the identical control already exerted over PBX/PPV charges. Caveat: claim 10's "physical location's access" is broad (the previously generated section notes the Markman court declined to narrow "physical location"), which if anything helps a prior-art read.

5. Claims 13 and 18 (location + usage billing, protocol-flexible)

Claims 13/18 are the broadest of the set: unlike claims 1/6 they do not require CAR format — only that the gateway format the data "to meet one of the predetermined protocols supported by [the] management system" (claim 20's narrowing group is "a low level protocol, a call accounting record, and a private branch telephone system protocol").

Combination E — Mobile Area Networks '884 + Apogee '977 (or Ameritech '289) + Atcom '430/NPL (hotel PMS).

• '884: location-based (room number) identification of network users and per-connection charge computation with surcharges.
• Apogee '977 / Ameritech '289: metering usage and generating/transmitting a billing record and bill.
• Atcom '430 + the Business Wire NPL (NetGame Jun-1999; Copper Mountain/Nomadix Dec-1999 as industry context): high-speed in-room hotel network access with a management/billing server.
• Why combine (KSR rationales): (1) Known problem, known solution — '884 states the absent per-user data-network billing system is a drawback "deterring wider deployment"; (2) Predictable combination of known elements — location ID + usage metering + billing record generation were each routine; (3) Market forces — the NetGame and Copper Mountain/ATCOM public announcements show an established commercial practice of in-room hotel high-speed access with property-side billing, evidencing both demand and the ordinariness of the integration. Claims 13/18 should be the easiest to invalidate and the least defensible; the CAR-specific claims (1/6) are the most defensible.

6. Dependent claims

7. Why a PHOSITA would have combined these references (consolidated KSR motivations)

1. Express recognition of the problem in the art. US 5,745,884 states outright that no satisfactory per-user, per-connection billing system exists for data-grade networks and that one "will become highly advantageous." KSR holds that a problem known in the field supplies the motivation.
2. Design incentive / backward compatibility. The '399 spec admits the PMS is a closed, vendor-specific, already-deployed system that already ingests PBX/POS/PPV/credit-card records. Retrofitting a PMS is costly; the natural design choice is to emulate the device the PMS already knows (a PBX) and speak its record format. This is the classic "adapt to the existing interface" motivation.
3. Predictable result of a known data-handling technique. Reformatting one record type into another (usage record → billing record → CAR) is routine data translation with an expected outcome.
4. Convergence trend. Schoen et al. (1997) document PSTN/Internet convergence; AT&T '610 already charges data services to a telephone account. Together they motivate running data-network charges through the telephone record infrastructure — the conceptual core of the CAR-format claims.
5. Commercial practice as of the 1999 priority date. The NetGame (Jun-16-1999) and Ascend/ATCOM-INFO (Jun-22-1999) releases show in-room hotel high-speed Internet access and vendor integration were current practice; the later Copper Mountain/Nomadix and Atreus releases (Dec-1999/Feb-2000) show the trend continuing. These support the "market forces" and "known need" rationales (subject to the priority-date caveat noted in § 2).
6. Metering + billing architectures were interchangeable. Apogee '977, Ameritech '289, Cisco '160, Nokia '6338046, and Microsoft '812/'3077 all describe collecting per-user network-usage records and feeding them to a rating/billing engine — evidence that combining any one of them with the "present to the PMS" idea was within ordinary skill.

8. Weaknesses, counterarguments, and the honest limits of this case

1. The clientless limitation is the patent's best non-obviousness anchor. Claim 1/6/13/18 all require that the gateway "communicate with the computer absent additional agents implemented by the computer," and the Hewlett-Packard Markman (per the prior section) construed that as "absent additional special client software implemented by the computer for managing the communication between the computer and the gateway device." The two otherwise-closest references cut the wrong way: US 5,987,430 (Atcom, Horne et al.) uses "client software 90" (FIG. 8), and US 5,745,884 uses a "signalling resource 105 inside portable device 101." Neither cleanly discloses the clientless transparency the claims require. A challenger must therefore find a network-side/transparent-access teaching (e.g., WO 98/16044's server-side model, or a generic browser/DHCP/HTTP-redirect teaching) — otherwise the CAR-format claim set has a genuine § 103 gap. This is the single most important issue to resolve before asserting invalidity.
2. No cited reference clearly teaches the concrete "masquerade" mechanics. The specification's specific implementation — inserting a "mock telephone number" where no dialed number exists, and substituting numeral designations for non-numeric ASCII — is a particularized detail not shown in the references I reviewed. It is likely obvious as a design choice (satisfy the PMS's expected record shape), but it is not squarely disclosed.
3. Two cited references are probably not prior art (JP 2000-354127 A; JP 2002-111870 A), and two NPL items postdate priority (Dec-6-1999; Feb-14-2000). Combinations must be rebuilt only from the genuine § 102(b)/§ 102(e) art.
4. Priority dependency. If the Oct-22-1999 provisionals fail to support the CAR-format limitations, the effective date shifts toward Oct-20-2000, which broadens the prior art (bringing the Dec-1999 NPL items into play). Conversely, if priority holds, those items drop out. Determine support before finalizing any combination.
5. Common ownership / pre-AIA § 103(c). The '399's own specification incorporates the "Gateway Device Applications" (Ser. No. 08/816,174 and Prov. 60/111,497), which matured into the Nomadix family (priority Mar-12-1997; e.g., US 6,130,892). Those could be § 102(e) art on their filing dates, but pre-AIA § 103(c) may disqualify them for obviousness purposes if commonly owned at the time the invention was made. A challenger should not assume they can be used.
6. Secondary considerations. The prior sections document Nomadix's enforcement history and licensing/security interests (NTT DOCOMO; Gate Worldwide Holdings), which the patentee could cite as evidence of commercial success or industry recognition. That evidence is weakened by (a) the crowded, competitive hotel-broadband field evidenced by the NPL, and (b) the need to prove nexus to the CAR-format/clientless features specifically rather than to hotel broadband generally. The apparent Hewlett-Packard summary-judgment non-infringement for HP's "Group 2" devices (per the prior section) also suggests the claims are narrow enough that commercial activity may not map to them.
7. Art characterization risk. Some references are directed at carrier/WAN cost-apportionment (Apogee '977) rather than hospitality PMS billing; a patentee may argue non-analogous art or "different field of endeavor." Given that all address billing for network/data usage, this argument is weak but should be anticipated.

9. Bottom line

• Strongest obviousness positions: claims 13 and 18 (location + usage billing, protocol-flexible) are the broadest and most vulnerable — a Mobile Area Networks '884 + Apogee '977/Ameritech '289 + Atcom '430 / hotel-PMS NPL combination renders them prima facie obvious. Claim 10 is also vulnerable via a Secure Computing '195 + Telia EP 0 762 707 + Ameritech '289 combination.
• Most defensible: claims 1, 6, 2, 7, 14, 19 — the CAR-format and clientless limitations. The clientless element is the real hurdle (the closest references disclose client software), and the CAR/mock-field mechanics are only inferentially obvious. A successful § 103 challenge to claims 1/6 likely needs additional art teaching transparent, client-free network access (a network-side redirection/filter model) to combine with the billing art.
• Confidence: Moderate-to-high that claims 13/18 and 10 are vulnerable; moderate as to claims 1/6, contingent entirely on finding a clientless-access teaching; and low as to whether the specific mock-telephone-number/CAR-format implementation can be shown obvious from the cited record alone.
• Unresolved items carried over: (i) whether a CBM petition on the '399 was in fact filed/instituted (still unconfirmed; do not represent otherwise); (ii) the priority-support question in § 8.4; (iii) full-text verification of US 5,987,430's client-software teaching and of US 6,119,160 and US 6,338,046, which I mapped from title/abstract only.