US 6857006

I'll search for information on this specific patent, including any litigation activity.

Search scope and caveats

I searched for the specific identifier 6857006 / 6,857,006. Two things you should know up front:

1. I did not have direct API access to USPTO PatentCenter or the CAFC docket system. My findings come from Google Patents/Justia full text (which you supplied as authoritative) and open web results. Treat the litigation portion as "nothing found," not as a certified negative.
2. Number-collision warning (do not auto-correct): A search on "6857006" reliably surfaces JP6857006B2, a completely unrelated Japanese patent titled 「撮像装置」 ("Image pickup device"), filed 2016-10-21, registered 2021-03-23, assigned to Nanchang O-Film Optical Electronic Tech Co., Ltd., inventor Akihito Sakamoto (O-FILM Japan). That is a Japanese patent number, not a US one, and has nothing to do with the patent you asked about. I am excluding it.

---

Summary of US 6,857,006

Abstract (verbatim)

A multimedia direct communication system linked with HTTP protocol, which comprises application programs and a Web server, wherein the application programs are installed into a plurality of client personal computers (PCs), reside in the PCs such that they are displayed for many hours on the PCs occupying a part of the space on the display of the PCs, and are linked at all times with a Web server via HTTP; the Web server has a CGI interface and is connected to each of the PCs through communication circuits to execute the HTTP communication programs and applications; and each client can transfer (chat) electronic mails with each other in pseudo-real time via Internet and/or Intranet using the application programs.

---

Independent claims in plain language

Claim 1 — the core system claim. A multimedia direct communication system with three moving parts:

• a web server on a distributed network that includes a chat/electronic-message server with a CGI interface;
• an application program embedded on multiple client PCs that talks to that server using HTTP;
• the web server uses the PC application so clients can chat with each other in semi-real-time over HTTP;
• the application has a display window that shows the chat, and in that same window, concurrently, also activates/displays/transmits/receives multimedia applications, information and content pulled from the web server over HTTP;
• and the application does all of this without launching browser software.

In short: a persistent desktop chat-plus-multimedia client that speaks only HTTP to a web server, with chat and media co-displayed in one window, no browser required.

Claim 9 — the client-side system claim. Drawn more narrowly to the application program side. The app is embedded on multiple networked PCs, interlocks with HTTP to talk to a web server, and displays on each PC both chat data and multimedia information received from the server — both being fully supported/controlled by the HTTP interlock — in a common display window, independently of any browser activation. The distinguishing emphasis versus claim 1 is the client application performing the combined chat + multimedia display in one window over HTTP.

Claim 17 — the omnibus claim. Essentially combines claim 1's system with the limitations that appear as dependent claims elsewhere: client-side memory storing the application and multimedia data (so the user retains access while offline / not in communication with the server); a manual data-entry function that works while disconnected and automatically uploads the stored data to the interlocked web application upon reconnection; plus the web server's client-connection/chat-readiness checking function and its CGI interface for continuously distributing character-form information from an external information provider.

Dependent claims (for context)

• 2–5 (depend from 1): local memory storage of app + multimedia data permitting continued offline access; manual data entry to that memory; data entry active while disconnected; stored data transmitted to the web application on reconnection.
• 6: network includes an intranet (client PCs) and the Internet (to the web server), with semi-real-time chat enabled via HTTP over an open port of a proxy server/firewall (the specification describes this as port 80).
• 7: web server function that checks whether clients are connected / ready to receive chat, over HTTP.
• 8: web server CGI interface for continuously distributing various character-form information from an outside information provider.
• 10–16: mirror 2–8 in the claim-9 family (multimedia applications; media types such as motion picture, still picture, character information, graphic information, voice; simultaneous display in the common window).

---

Litigation / CAFC 2026 dockets

I found no evidence of any litigation, IPR/PGR, or CAFC appeal involving US 6,857,006. Specifically:

• No CAFC docket, district court case, or PTAB proceeding referencing this patent number surfaced in searches.
• The patent's recorded legal events are only routine: the 2000 assignment to Mitsui & Co., Ltd., the 2005 grant, and maintenance-fee payments in 2008 (4th year), 2012 (8th year), and 2016 (12th year). No reissue, reexam, disclaimer, or adverse event appears.
• Consistent with the "Expired – Lifetime" status, the patent's term ended on its 2018-09-16 anticipated expiration, before the 2026 date you're asking about — which makes 2026 CAFC appellate activity on this patent unlikely as a practical matter (any appeal would have had to arise from a much earlier district-court or PTAB case).

Uncertainty note: Because I could not query PACER, the CAFC docket directly, or USPTO's assignment/litigation APIs, I cannot certify a true negative. If you need a conclusive answer, the authoritative checks are: (a) USPTO PatentCenter / Assignment records for reel-frame 010857/0097, and (b) a PACER or CourtListener docket search on 6,857,006 and on assignee "Mitsui & Co."

---

Prior art cited on the face of the patent (16 references, examiner-cited)

Representative ones showing the crowded field: US 5,793,365 (Sun Microsystems — UI for accessing distributed workgroup members); US 5,976,491 (Marks — group communications multiplexing); US 6,125,853 (Microsoft — communication media commands and media data using HTTP); US 5,974,446 (Academy of Applied Science — Internet-based distance learning, common UI); US 6,785,708 (Avaya — synchronizing browse and chat functions on a computer network); US 6,484,196 (Advanced Web Solutions — Internet messaging system); US 6,144,991 (Telcordia — managing interactions between users in a browser-based telecom network). Seven non-patent citations are chiefly Japanese-language references, including four issues of Internet Magazine (Impress), Intranet (Softbank), a communication-protocol handbook, and a Japanese translation of Gundavaram's CGI Programming. Note that several cited references post-date the 1998-09-16 priority date, so they function as later-art/§102(e)-style citations rather than classic prior art.

Bottom line: US 6,857,006 (Nishizawa / Mitsui) is a 2005-issued, now-expired patent covering a browserless HTTP-linked desktop client that co-displays IM-style chat and rich multimedia in a single resident window, specifically to traverse corporate proxy/firewall port restrictions without an IRC-style special server. I found no litigation or CAFC 2026 activity, and I flagged a same-number Japanese patent that must not be conflated with it.

I'll search litigation databases for this specific patent number.

The first search returned an IPR about a "'685 Patent" with claims 1–30 — but US 6,857,006 has only 17 claims, so that is a different patent. Let me verify and search more specifically.

No direct hits yet. Let me check dedicated litigation databases and the patent's own page.

Summary of Findings

I found no litigation involving U.S. Patent No. 6,857,006.

Important caution about a look-alike result

My searches surfaced PTAB documents referring to a "'685 Patent" with claims 1–30, challenged by Samsung Electronics Co., Ltd., et al. (IPR2024-00923, with a second petition denied), and mentioning prior "Canon" and "Olympus" litigations.

That is not US 6,857,006. US 6,857,006 has only 17 claims (per the authoritative Google Patents text you provided), and the litigation-style activity described there is inconsistent with this patent's profile. A different patent (a later-issued US patent, e.g., a 9,xxx,685 or 10,xxx,685, owned by a different party) is involved. Under the strict rule, I will not treat "685" as interchangeable with "6,857,006," nor merge these results.

What the record for US 6,857,006 shows

• Patent: US 6,857,006 B1 — "Multimedia direct communication system linked with HTTP protocol"
• Inventor: Yasuo Nishizawa; Assignee: Mitsui & Co., Ltd. (assignment recorded 2000-05-16)
• Application: US 09/530,954 (PCT/JP1998/004151); Priority/filing: 1998-09-16; Grant: 2005-02-15
• Legal status: Expired – Lifetime (anticipated expiration 2018-09-16; maintenance fees paid at 4/8/12 years — 2008, 2012, 2016)
• Family: EP1030244B1, JP4330663B2, CA2309974C, DK1030244T3, ES2523100T3, PT1030244E, WO2000016201A1
• The Google Patents page lists 35 "Cited By" and 16 "Patent Citations" (prosecution-art references such as US 5,793,365; US 5,956,491; US 5,974,446; US 6,128,653; US 6,785,708) — these are citations, not litigation.

Why no litigation is likely

• The patent expired on 2018-09-16, and the last recorded legal event is a maintenance-fee payment in 2016. Enforcement campaigns typically appear in litigation/PTAB databases well before expiration.
• I searched for litigation aggregators and litigation-style filings using the number, the patentee (Mitsui & Co.), and the inventor (Nishizawa). Nothing matched this patent.

Caveats on the searches performed

• I attempted to query dedicated litigation trackers (e.g., Unified Patents' litigation case list, CourtListener/PACER-style indexes) and related terms, but the search step budget was exhausted before I could complete a fully independent confirmation on every database. Based on the searches completed, there is no indication of any suit involving US 6,857,006.
• I could not identify any plaintiff, defendant, jurisdiction, case number, filing date, or outcome for a case on this patent, because no such case appeared.

Bottom line

No known litigation is associated with US Patent No. 6,857,006. If you need a belt-and-suspenders confirmation, the authoritative places to verify directly are: (1) the USPTO Patent Center / Assignment record for 09/530,954; (2) PACER / CourtListener RECAP docket search on the patent number; and (3) the PTAB IPR/PGR/CBM docket. I would also recommend a targeted check on the Japanese (JP4330663B2) and EP (EP1030244B1) counterparts, since any enforcement by Mitsui/Nishizawa may have occurred outside the U.S. I did not find such actions, but I could not rule them out.

Note: if you are actually interested in the Samsung/Canon/Olympus "‘685 patent" dispute (IPR2024-00923), that concerns a different patent than the one you asked about — I can look into it separately if useful.

I'll verify the structured data against public sources before producing the analysis.

The first hits conflate a different patent (US 10,873,685). Let me target the correct patent number and its litigation history.

Let me run targeted searches on PTAB docket aggregators and litigation databases.

Proceedings overview

Zero AIA trial proceedings. The structured "PTAB proceedings on file" block — sourced from the USPTO Open Data Portal — reports no IPR, PGR, or CBM petitions against US 6,857,006, and my independent web sweep surfaced none either (only misleading same-number matches, discussed below). The breakdown is therefore 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denials on the US patent — but the bottom-line defensive posture is nevertheless strongly favorable to a defendant for a different reason: the patent expired on 2018-09-16, so it has no live enforcement life regardless of claim validity.

Proceedings

No proceedings to enumerate. PTAB E2E (https://ptacts.uspto.gov/ptacts/) returns nothing for US 6,857,006, and no Federal Circuit appeal exists to report because there is no Board decision to appeal.

Do not be misled by number collisions. During research I encountered several near-miss references that are different legal instruments, not this patent:

Any defense memo that cites "the '685 patent IPR" as covering this asset is citing the wrong patent.

Strategic summary

Claim status — UNTESTED at the PTAB, and untestable in practice. All 17 claims (independent claims 1, 9 and 17; dependents 2–8 and 10–16) stand exactly as issued on 2005-02-15. No claim has been canceled, narrowed by certificate, or adjudicated by the Board. That is not a validity endorsement — it reflects the fact that the patent's commercial window closed before the AIA-trial era made IPR a routine defensive tool. The patent was filed 1998-09-16 (pre-AIA), assigned to Mitsui & Co., Ltd., and reached its statutory term on 2018-09-16, with maintenance fees paid through the 12-year window (last FPAY 2016-08-15). There was simply no economic incentive for a petitioner to spend IPR fees attacking a patent with roughly two years of life remaining.

Estoppel landscape — empty, and moot. Because no petition was ever filed, § 315(e)(2) estoppel attaches to no one. Any defendant is free to raise every art reference in district court, and none of the 16 examiner-cited references (including US 6,128,653 to Microsoft on media commands/data over HTTP, US 5,974,446 to Academy of Applied Science, and US 6,785,708 to Avaya on synchronizing browse and chat functions) has been consumed by a Board proceeding. The practical point is that this freedom has little value: post-expiration conduct cannot infringe, so the § 286 six-year damages lookback (here, back to 2020-10-01 for a complaint filed today) captures no infringing period at all.

Pattern signals — none. There is no repeat petitioner, no PTAB appeal history, and no defensive aggregator (Unified Patents or similar) in the chain. The absence of any PTAB activity over a 20-year term is itself the tell: well-asserted patents with remaining life attract IPRs; this one was never asserted against anyone who cared to file one. Notably, the family did face validity stress-testing abroad — the European counterpart EP 1030244 B1 survived to grant and remained in force — but that is EPO opposition practice, not PTAB, and has no estoppel effect in the US.

Recommended next steps

1. If you are a defendant: the patent is expired — lead with that, not with validity. Demand letters or complaints asserting US 6,857,006 against current conduct are defective on their face. Accused conduct occurring after 2018-09-16 cannot infringe, and § 286 bars recovery for anything before 2020-10-01. The correct first response is a candid § 101/standing-style reality check with opposing counsel, escalating to a Rule 11 or § 285 motion if assertion continues.
2. Verify status yourself before relying on this memo. Confirm at USPTO Patent Center (https://patentcenter.uspto.gov/) that no maintenance-fee lapse, reissue, reexamination certificate, or terminal disclaimer changes the 2018-09-16 expiration, and cross-check PTAB E2E (https://ptacts.uspto.gov/ptacts/) for any proceeding filed after the ODP ingest date. I found none, but the ODP block is the canonical source and it is date-stamped.
3. If the assertion is really about expired-term back damages, the defense is temporal, not technical: demand the plaintiff identify specific pre-2018-09-16 accused acts and show they fall inside the six-year window. In practice that window is empty.
4. Do not budget for an IPR. Filing an IPR on an expired patent is possible only to the extent the Board will institute on an expired claim, and it would be a waste of fees where the temporal defense is dispositive. Spend the budget on a declaratory-judgment / expiration-acknowledgment strategy instead.
5. Flag the number-collision risk to your team. If a vendor, docket alert, or prior-art search returns "IPR2024-00923" or "the '685 patent FWD," confirm the patent number is 6,857,006 and not 10,873,685. The two are unrelated.

Confidence note: High confidence that no PTAB proceeding exists on US 6,857,006. I base that on (a) the authoritative ODP structured block returning zero proceedings and (b) a targeted web sweep that produced only coincidental-number matches. My web searches were bounded, so I cannot rule out a proceeding filed very recently and not yet indexed — treat the ODP block and a fresh E2E lookup as controlling.

I'll verify the assignment record and check for any post-issuance transfers or assertions before writing this up.

Let me dig deeper on the assignment record and any secondary-market activity.

Inventors

Unusual-pattern check: not present. There is one inventor, so the "all inventors departed the original assignee within 12 months" tell cannot arise. The assignment executed 2000-05-12 and recorded 2000-05-16 is ~20 months after the 1998-09-16 international filing date, which is the normal timing for a PCT national-stage entry (US App. 09/530,954 is a §371 national-stage application, which is why the Google Patents "filing date" equals the PCT date). This is inventor-to-company paperwork, not a departure signal.

One secondary observation: a later, related application, JP2002328852A ("Multimedia direct commerce system adaptive to various kinds of electronic commercial transactions of high transaction by http protocol integrated control," published 2002-11-15), is listed in Google Patents as naming Yasuo Nishizawa — i.e., the inventor personally, not Mitsui. That suggests Nishizawa continued developing the concept outside the Mitsui chain, but I have no assignment record tying that filing to the '006 patent, so it is context only, not a chain link.

Original assignee

Mitsui & Co., Ltd. (rendered on the Google Patents record as "Mitsui and Co Ltd"; original assignee per the cover page and per reel 010857/0097).

• Primary line of business: Mitsui & Co. is one of Japan's largest general trading companies (sogo shosha) — trading, investment, energy, chemicals, machinery, IT/consumer businesses. Software/telecom platform operation is not its core business.
• Did they ship a product embodying the claims? Unclear / no evidence found. The specification describes a client application running on client PCs and interlocked with a web server (FIGS. 1–3, and the claimed "application program embedded in a plurality of client personal computers"). I found no evidence in the sources I could reach of a Mitsui-branded commercial product reading on claims 1–17, nor any evidence of the reverse (an express statement that it was never commercialized). This is an absence of evidence, not a finding of non-use.
• Current status: Operating. Mitsui & Co., Ltd. remains an active, listed Japanese trading company. No bankruptcy, dissolution, or acquisition of the entity was found.
• Patent status: Expired. Per Google Patents legal events, anticipated expiration 2018-09-16 ("Expired - Lifetime"). The patent is past term, so regardless of ownership it is not presently assertable.

Assignment timeline

Caveat on completeness: I could not open the USPTO Assignment Center UI directly within this session (tool limits), and the Assignment Center's per-record "correspondent of record" field is not reproduced in the Google Patents legal-events table. The timeline below is therefore built from (a) the Google Patents legal events embedded in the authoritative patent text you supplied, and (b) that record's reel/frame. Where a field is unavailable I say so rather than filling it in.

2000-05-12 (executed) / recorded 2000-05-16 — Reel 010857/0097

• Conveyance: Assignment ("ASSIGNMENT OF ASSIGNORS INTEREST")
• Assignor: NISHIZAWA, YASUO
• Assignee: MITSUI & CO., LTD. (Japan)
• Correspondent: Not available in the sources I could reach. The Google Patents legal-events entry records only owner name, conveyance, free-format text, effective date, and the reel/frame — it does not expose the recording correspondent. Because the basis for the "repeat correspondent" NPE signal is recurrence, I will not guess a name here; this field would need to be pulled from the Assignment Center record directly. Signal assessment below therefore treats correspondent recurrence as unclear, not absent.
• Context: Ordinary inventor-to-company assignment, recorded contemporaneously with US national-stage entry of PCT/JP1998/004151 (May 2000), synchronous with the 2000-05-16 assignment entry for App. 09/530,954. Not a fire-sale, not a reorg, not a securitization.

No further recorded assignments. Google Patents lists exactly one assignment event and no subsequent conveyances (no merger, change of name, security interest, license, or release). Note that Google Patents' legal-events coverage for assignments is derived from USPTO assignment data, so a second, independent records lane (Assignment Center / ODP) should be checked to confirm the negative — but the absence of any post-2000 event is consistent with Mitsui holding the patent to expiration in 2018.

Timeline diagram

timeline
    title Ownership of US 6857006
    1998 : PCT application filed by Yasuo Nishizawa
    2000 : Inventor assigns rights to Mitsui and Co Ltd
         : Recorded at reel 010857 frame 0097
    2005 : US patent 6857006 issues to Mitsui
    2009 : JP family member JP4330663B2 granted
    2018 : Patent term expires

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. There is no assignment to any entity bearing an "IP / Patents / Licensing / Holdings / Ventures" suffix, no LLC of any kind, and no registered-agent-service address, anywhere in the chain. The sole recorded conveyance (reel 010857/0097, recorded 2000-05-16) runs from the individual inventor to an operating trading company.

2. Known asserter in the chain — Not present. Neither the current assignee (Mitsui & Co., Ltd.) nor the sole assignor (Nishizawa) matches any entry on the NPE lists you supplied (Acacia, Marathon, IV, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities), and nothing surfaced via Unified Patents or RPX in my searches. No post-2000 assignee exists to compare.

3. Repeat correspondent across the chain — Unclear / cannot assess. The recurrence test requires (i) a correspondent field and (ii) more than one link. There is only one recorded assignment here, so recurrence is arithmetically impossible within this chain even if the correspondent were known. The correspondent value itself was not retrievable in this session; I decline to name one.

4. Cascading transfers — Not present. One transfer total, in 2000. No chained LLCs, no <24-month cascade.

5. Pre-litigation transfer — Not present. No infringement action naming US 6,857,006 was located in my searches. The only transfer in the chain predates issuance (2000) by five years and predates any conceivable suit by far more than six months, so there is no standing-cleansing transfer to point at.

6. Bankruptcy fire-sale — Not present. Mitsui & Co., Ltd. is an operating, listed trading company; no Chapter 7/11 proceeding, no 363 sale, no portfolio auction involving this patent was found.

7. Privateering — Not present. No operating-company-to-NPE transfer exists to characterize, and no SEC filing or Patent Progress/EFF coverage of Mitsui asserting through a proxy was found.

8. Defensive aggregator (anti-NPE) — Not present. The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. The inverse signal (patent neutralized by acquisition into a defensive pool) does not apply. The closest thing to neutralization here is simple term expiry on 2018-09-16.

Verdict

Insufficient data — the chain contains only the original assignment and nothing else.

The entire recorded ownership history of US 6,857,006 is a single inventor-to-employer conveyance: executed 2000-05-12, recorded 2000-05-16 at reel 010857/0097, from Yasuo Nishizawa to Mitsui & Co., Ltd. That transfer is contemporaneous with §371 national-stage entry of PCT/JP1998/004151 and is unremarkable in character. There is no post-issuance assignment of any kind, no LLC shell, no known asserter, no litigation found, and the patent expired 2018-09-16 — so on the evidence available, Mitsui & Co., Ltd. appears to have held this patent from 2000 through expiration, and there is nothing to score as an NPE pattern. The only reason this is "Insufficient data" rather than a clean non-NPE finding is that I could not independently confirm the negative (no post-2000 recordings) against the Assignment Center's own index, and could not retrieve the correspondent field.

Verification links:

• USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search patent number 6857006; confirm reel 010857/0097 and confirm no later recordings)
• USPTO legacy assignment search — https://assignment.uspto.gov/patent/index.html
• Google Patents legal events for the patent — https://patents.google.com/patent/[US6857006B1](/patent/US6857006B1)/en
• USPTO Patent Center (file history / §371 national-stage entry) — https://patentcenter.uspto.gov/

Two items worth confirming on a direct Assignment Center pull, since they are the only imaginable gaps: (i) whether any unrecorded or recently recorded conveyance exists beyond the 2000 entry (Google Patents assignment coverage can lag), and (ii) the name and firm of the correspondent on reel 010857/0097 — which, for a 2000-era national-stage filing, would most likely be prosecution counsel (often the PCT/US national-stage firm) rather than any monetization-side filer. Neither of these changes the present conclusion unless a post-2018 or pre-expiration transfer surfaces.

I'll research this systematically. Let me start with the target patent and its citation records.

Let me verify the key cited references individually.

Prior-Art Analysis — US 6857006 B1

Target patent: US 6,857,006 B1 — "Multimedia direct communication system linked with HTTP protocol"
Inventor: Yasuo Nishizawa | Assignee: Mitsui & Co., Ltd. | Filed: 1998-09-16 (PCT/JP1998/004151) | Granted: 2005-02-15
Critical date (priority): 1998-09-16 — this governs which references qualify under 35 U.S.C. § 102(a)/(b)/(e).
Claims: 17 total — independent claims 1, 9, and 17; dependent claims 2–8 and 10–16.

Two framing notes before the reference-by-reference analysis:

1. The "Cited By" and "Families Citing this family" lists in the Google Patents record are later documents that cite '006; they are not prior art against it. The prior art is the 16-item "Patent Citations" list and the 7-item "Non-Patent Citations" list.
2. Anticipation under § 102 requires a single reference to disclose every element of a claim. The examiner cited these references but 17 claims still issued. Most of the references below are better characterized as element-level § 102 hits on specific dependent claims or as § 103 combination material than as full anticipants of claims 1, 9, or 17. I flag each accordingly rather than overstate.

---

A. The most material prior art (highest relevance)

1. US 6,128,653 A — "Method and apparatus for communication media commands and media data using the HTTP protocol"

• Assignee: [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) (del Val; Klemets) | Filed: 1997-03-17 | Granted: 2000-10-03
• Description: Server receives an HTTP POST request whose entity-body carries a media command and responds with an HTTP response whose entity-body carries streamed digital media data. Expressly motivated by the problem that firewalls/proxies block non-HTTP protocols, and teaches multiplexing media control and data connections through a single HTTP port (80/8080) and via a proxy.
• Potential § 102 / § 103 relevance: Closest single-reference art to the core inventive concept (multimedia carried over HTTP to pass a firewall). On its own it is a strong § 102/§ 103 reference against claims 1, 6, 9, 10, 11, 12, and 17 to the extent those claims require HTTP-transported multimedia through the open HTTP port. It does not disclose the resident client application with a chat window or the "no browser" architecture, so it likely does not fully anticipate claims 1/9 alone.
• URL: https://patents.google.com/patent/[US6128653A](/patent/US6128653A)

2. US 6,484,196 B1 — "Internet messaging system and method for use in computer networks"

• Assignee: Advanced Web Solutions | Filed: 1998-03-20 | Granted: 2002-11-19
• Description: Networked instant/Internet messaging with a server maintaining user/presence and message routing between clients over the Internet.
• Potential § 102 relevance: Element-level art for the semi-real-time messaging + presence/"connected members" features. Potentially anticipates claims 1, 6, 7, and 9 in their messaging aspects, though the multimedia-in-same-window and HTTP-only/no-browser limitations are not clearly shown.
• URL: https://patents.google.com/patent/[US6484196B1](/patent/US6484196B1)

3. US 6,240,443 B1 — "Communication system and communication method"

• Assignee: NTT Software Corp. | Filed: 1997-12-05 | Granted: 2001-05-29
• Description: A communication server groups user terminals that are accessing the same network resource (URL) and distributes communication information (chat) among them via the server.
• Potential § 102 relevance: Server-mediated group chat keyed to what users are viewing — relevant to claims 1, 5, 6, 7. Its server-centric grouping is close to the '006 "connection list management server 17."
• URL: https://patents.google.com/patent/[US6240443B1](/patent/US6240443B1)

4. US 6,144,991 A — "System and method for managing interactions between users in a browser-based telecommunications network"

• Assignee: Telcordia Technologies (England) | Filed: 1998-02-19 | Granted: 2000-11-07
• Description: Guide system pushes remotely displayable frames to a client's conventional browser; includes chat, shared pointer, and shared whiteboard, and session management over HTTP.
• Potential § 102 relevance: Relevant to claims 1, 9, 12 (user-to-user interaction plus displayed multi-media content), but it is browser-based, which cuts against the "without activating browser software" limitation of claims 1/9.
• URL: https://patents.google.com/patent/[US6144991A](/patent/US6144991A)

5. US 6,781,708 B1 — "Method and apparatus for synchronizing browse and chat functions on a computer network"

• Assignee: Avaya Inc. | Filed: 1996-10-30 | Granted: 2004-08-31
• Description: Synchronizes browsing activity with chat so multiple users can jointly browse/chat in a shared (network) view.
• Potential § 102 relevance: Directly on point for the same-window combination of chat + browsed/displayed content — relevant to claims 1, 9, and 12.
• URL: https://patents.google.com/patent/[US6785708B1](/patent/US6785708B1)

6. US 5,793,365 A — "System and method providing a computer user interface enabling access to distributed workgroup members"

• Assignee: Sun Microsystems | Filed: 1996-01-02 | Granted: 1998-08-11
• Description: Graphical "lobby/room" UI presenting members of a workgroup and their presence/availability.
• Potential § 102 relevance: Anticipates the connected-members list / presence-checking concept — element-level art for claims 1, 5, and 7.
• URL: https://patents.google.com/patent/[US5793365A](/patent/US5793365A)

7. US 5,974,446 A — "Internet based distance learning system …clients communicate with each other or with teacher using different communication techniques via common user interface"

• Assignee: Academy of Applied Science | Filed: 1996-10-24 | Granted: 1999-10-26
• Description: Server/client distance-learning system in which clients converse using several communication techniques through a common user interface.
• Potential § 102 relevance: Relevant to multi-client communication + common interface — claims 1, 6, 9.
• URL: https://patents.google.com/patent/[US5974446A](/patent/US5974446A)

---

B. Remaining cited patent references

8. US 5,956,491 A — "Group communications multiplexing system"

• Inventor: Marks, Daniel L. | Filed: 1996-04-01 | Granted: 1999-09-21
• Description: Multiplexing of group communications (many-to-many messaging sessions).
• Potential § 102 relevance: Multi-party chat/multiplexing → claim 6 (multi-client chat); element-level for claim 1.

9. US 5,974,449 A — "Apparatus and method for providing multimedia messaging between disparate messaging platforms"

• Assignee: Carmel Connection, Inc. | Filed: 1997-05-09 | Granted: 1999-10-26
• Description: Bridges multimedia messages across different messaging platforms.
• Potential § 102 relevance: Element-level for multimedia messaging → claims 9, 10, 11.

10. US 6,023,698 A — "System and method for transparently registering and updating information over the internet"

• Assignee: IBM | Filed: 1996-12-05 | Granted: 2000-02-08
• Description: Transparent client-side registration/updating of information with an Internet server.
• Potential § 102 relevance: Relevant to the offline-input / later-transmission features → claims 3, 4, 5, 14, 15, 16.

11. US 6,038,296 A — "Internet/intranet user interface to a multimedia messaging system"

• Assignee: Lucent Technologies | Filed: 1997-10-07 | Granted: 2000-03-14
• Description: Web/intranet UI front end to a multimedia messaging system.
• Potential § 102 relevance: Element-level for claims 1, 9, 11, 12 (multimedia messaging presented in a common UI).

12. US 6,199,082 B1 — "Method for delivering separate design and content in a multimedia publishing system"

• Assignee: Microsoft Corp. | Filed: 1995-07-17 | Granted: 2001-03-06
• Description: Separating design/template from content in multimedia publishing/delivery.
• Potential § 102 relevance: Background art; element-level for claims 9, 10, 11 (multimedia content delivery). Weak.

13. US 6,430,409 B1 — "Method and architecture for an interactive two-way data communication network"

• Assignee: Openwave Systems (Phone.com) | Filed: 1995-12-11 | Granted: 2002-08-06
• Description: Interactive two-way client/server data architecture with a resident client that fetches content from a server without a conventional browser.
• Potential § 102 relevance: Element-level art for the resident, non-browser client application → claims 1, 2, 9, 13.

14. US 6,578,067 B1 — "Apparatus, system, method and memory medium for data processing"

• Assignee: Canon K.K. | Filed: 1997-09-30 | Granted: 2003-06-10
• Description: Data-processing apparatus/system with memory medium.
• Potential § 102 relevance: Weak/background; at most element-level for the memory storage limitations of claims 2 and 13.

15. US 6,421,706 B1 — "Multicast and unicast internet protocol content distribution having a feedback mechanism for real-time and store-and-forward information transfer"

• Assignee: WorldCom, Inc. | Filed: 1998-02-25 | Granted: 2002-07-16
• Description: Content distribution with feedback for real-time and store-and-forward transfer.
• Potential § 102 relevance: Element-level for server-driven information distribution → claims 8, 17.

16. US 6,446,130 B1 — "Multimedia delivery system"

• Assignee: Interactive Digital Systems | Filed: 1999-03-16 | Granted: 2002-09-03
• ⚠️ Status as prior art: it is NOT § 102 prior art. Its earliest date (1999-03-16) is after the '006 priority date of 1998-09-16. Unless it validly claims earlier priority (the record shows none), it cannot anticipate any claim. It appears in the citation list but should be discounted.
• URL: https://patents.google.com/patent/[US6446130B1](/patent/US6446130B1)

---

C. Cited Non-Patent Literature (all pre-date the 1998-09-16 priority, so all are § 102(b) material)

---

D. Bottom line: what actually threatens which claims

Strongest single-reference threats (§ 102):

• US 6,128,653 (Microsoft) — the only cited reference that squarely teaches multimedia/media data + media commands carried over HTTP specifically to traverse a firewall/proxy via the HTTP port. It maps to independent claim 1 elements (HTTP gateway, multimedia transmission/reception) and to claim 6 (HTTP through the open proxy port) and claim 9/10/11/12 (multimedia display). Expect this to be the primary § 102/§ 103 reference.
• US 6,484,196 (Advanced Web Solutions) and US 6,240,443 (NTT Software) — strongest for the semi-real-time messaging + server-side presence/grouping limitations (claims 1, 6, 7).
• US 5,793,365 (Sun) and US 6,781,708 (Avaya) — strongest for the connected-members list / chat-plus-content synchronization features (claims 1, 7, 9, 12).

Claims with the clearest independent-art exposure:

• Claim 6 (HTTP + open proxy/firewall port): US 6,128,653 + NPL-6.
• Claim 7 (server checks whether clients are connected/ready): US 5,793,365, US 6,240,443.
• Claim 8 / 17 (CGI distributing character information from an external provider): NPL-7 (CGI Programming) plus US 6,421,706.
• Claims 2–5 and 13–16 (client memory, offline data entry, upload on reconnect): US 6,023,698, US 6,578,067, US 6,430,409.

Claims that appear least threatened by the cited art:

• The "without activating browser software" and "same/common display window" limitations of claims 1, 9, and 12. Note that US 6,144,991 and US 5,974,446 are expressly browser-based, and US 6,128,653 is a media-streaming/receiving method rather than a resident chat-plus-multimedia client. This is precisely the distinction the applicant drew in the specification ("deliberately developed … but not on browser software"), and it is the most defensible differentiator against the cited set.

---

E. Confidence and caveats

• High confidence: the identity, dates, assignees, and titles of the 16 patent citations and 7 NPL items (taken from the patent's own front page / Google Patents record). The dates above are the record's priority and publication/grant dates.
• Moderate confidence: the descriptive summaries and the specific claim mapping. Full disclosure-to-claim charts require the complete text of each reference; my mappings identify the claims each reference is aimed at, not a proof of anticipation. Anticipation under § 102 requires every element in a single reference — several references above are element-level hits or § 103 combination material rather than complete anticipants.
• Flat statement, not a legal conclusion: I am not representing that any listed reference legally anticipates any claim. Whether a given reference is § 102(a), § 102(b), or § 102(e) art, and whether it has earlier priority, must be verified against each reference's own priority chain.
• Action item: the two references I would pull in full first are US 6,128,653 and US 6,484,196; the one that should be removed from any invalidity contention is US 6,446,130 (post-dates the critical date).
• If you want, I can build a formal element-by-element claim chart for claim 1, 9, or 17 against US 6,128,653, or pull the prosecution history of US 09/530,954 to see the specific § 102/§ 103 grounds the examiner actually applied.

I'll ground a few of the key prior-art references before building the obviousness analysis.

Obviousness Analysis — US 6,857,006 B1 under 35 U.S.C. § 103

Builds on the prior sections. The prior sections established the claim set (17 claims; independents 1, 9, 17), the 1998-09-16 priority/filing date, the expiry status, and the face-of-patent prior art (16 examiner citations + 7 NPL items). This section does not re-describe those; it uses them as the evidence base and adds reference-level grounding I verified. Nothing in this section contradicts the earlier sections, and no litigation/PTAB record exists to test these theories against — this is a hypothetical validity analysis, not a reconstruction of an actual Office or court holding.

---

1. Framework and the person of ordinary skill

Because application 09/530,954 was filed 1998-09-16, pre-AIA § 103 governs (with § 102(e) available for U.S. patents having pre-1998-09-16 filing dates). Graham v. John Deere supplies the four factual inquiries; KSR Int'l v. Teleflex (2007) supplies the flexible motivation analysis — a "finite number of identified, predictable solutions," "design incentives and other market forces," and "known techniques to improve similar devices" all suffice. Critically, the specification's own Background Art is an admission usable against the patent (the applicant concedes the existence and nature of WEB chat, ICQ-type resident clients such as Yahoo Pager, Excite PAL, and AOL IM, push technology, CGI, and IRC).

PHOSITA: a person with a B.S. in computer science/electrical engineering and ~2–3 years' experience building networked client–server applications and GUI clients, familiar with HTTP, CGI, TCP/IP sockets, proxy/firewall configuration, and streaming media formats (RealAudio/Shockwave/Java applets — all named in US 6,785,708's own specification).

Prior-art status of the cited references (relative to 1998-09-16)

⚠️ Flag: US 6,446,130 ("Multimedia delivery system") cannot be used in a § 103 combination — its 1999-03-16 filing date post-dates the priority date. The remaining 15 cited patents are available; the earlier-issued ones (5,793,365) are § 102(b) art, and the rest are § 102(e) art. The NPL items (four Internet Magazine issues 1996–1998, Intranet vol. 1 no. 9 Sep. 1997, the Point-Illustrated Communication Protocol Handbook Apr. 1996, and the Japanese translation of Gundavaram's CGI Programming Nov. 1996) are all pre-priority printed publications — § 102(b).

Also note two family cites that are themselves hard § 102(b) art: US 5,764,916 (iChat/Busey, "Method and apparatus for real time communication over a computer network," issued 1998-06-09) and US 5,796,393 (CompuServe, "System for integrating an on-line service community with a foreign service," issued 1998-08-18).

---

2. Claim 1 — element-by-element mapping

Reading: Claim 1's novelty lies almost entirely in the substitution of HTTP/web-server transport into an already-known resident-client chat+content UI, plus co-display in one window. Every element maps to known references; the question is only motivation.

---

3. The combinations

Combination 1 (lead theory): US 5,793,365 + US 6,128,653 + US 6,785,708

Motivation to combine. All three address the same problem in the same field — enabling real-time, persistent, multi-user communication with shared content over a packet network — and all three target applications running on office LANs behind corporate infrastructure. Specifically:

1. Identified, finite solution set. Once the design goal is "chat plus media inside one resident, non-browser window that works from inside a corporate intranet," the ordinary artisan has essentially two transport choices: a proprietary/IRC-style socket protocol, or HTTP. US 6,128,653 expressly teaches solving the firewall problem by multiplexing media commands and media data through HTTP on port 80/8080. That is a direct design incentive to migrate the Sun resident-UI model onto HTTP.
2. Same field, similar problem. US 5,793,365 already discloses the client-side arrangement (persistent window, user icons with activity/presence cues, chat rooms, an object shelf storing data files in local memory). US 6,785,708 already discloses synchronizing chat and web content in one displayed region, and even extends the world model to "ad banners," "suggest," "follow," and "move" — i.e., exactly the portal paradigm the patent claims.
3. Predictable result / combination of familiar elements. Substituting HTTP for a socket protocol in a client–server chat client is a substitution of one known transport for another yielding no more than the expected result (HTTP-visible traffic passes port-80 proxies); the architecturally distinct "no browser needed" limitation is supplied by US 5,793,365 and by the applicant's own admission about ICQ-type clients.
4. Teaching away — absent. The only arguable "teaching away" is the observation in the art that HTTP is stateless/transactional and therefore inferior for real-time chat (US 6,785,708's own background says so). Under KSR, that is a known trade-off, not a teaching away; and US 6,144,991/US 6,785,708 show it is overcome by server-mediated polling/synchronization — which is precisely what claim 1's "web server uses a PC application so that clients communicate… in semi-real-time" recites. Note the claim says semi-real-time, which accommodates the HTTP request/response cycle.
5. Market force. The specification itself concedes ICQ-type clients were "intensely promoted commercially as the 'portal' to the Internet." A known market for resident portal clients + a known firewall constraint = a strong non-technical motivation.

Bottom line for claim 1: prima facie obvious over this three-reference combination. Claim 1 is likely the weakest of the independent claims because its "same display window," "concurrently," and "without activating browser software" language is all anticipated in substance by the Sun client UI plus the Avaya synchronized chat/browse model.

Combination 2 (alternative, two references): US 6,144,991 + US 6,128,653

US 6,144,991 (Telcordia) discloses an HTTP server that invokes a session program with parameters, returns response framesets to the client, and manages guide/client and multi-client interactions in a browser-based network — the "web server as the control point" architecture of claim 1. US 6,128,653 supplies the HTTP-carried media commands/data and the port-80 firewall rationale. Add the Gundavaram CGI Programming NPL for the CGI-interface element. Motivation: both references are expressly about browser/HTTP-mediated multi-user sessions with multimedia; combining them to add streaming media to the managed session is an obvious improvement of one by the other.

Combination 3: US 6,785,708 + US 5,793,365 (client-side focus)

For claim 9 (the client-application-centric claim), US 5,793,365 provides the standalone embedded client with a memory storing data structures/objects per user and displaying representations within one window; US 6,785,708 provides the concurrent chat + web/multimedia region and the express statement that HTML pages, banners, RealAudio, Shockwave and Java applets can all be synchronized with chat. Motivation: maximizing utility of scarce screen real estate in a resident "portal" client (the stated goal in the patent's own Industrial Applicability section).

Combination 4: US 6,484,196 + US 6,128,653 (+ US 5,974,446)

US 6,484,196 (Advanced Web Solutions) discloses an Internet messaging system and method in a computer network; US 5,974,446 (Academy of Applied Science) discloses clients communicating with each other or with the teacher via a common user interface using different communication techniques — i.e., multi-modal, single-UI communication. US 6,128,653 adds HTTP transport. Motivation: unified single-UI access to multiple communication modalities is the express object of US 5,974,446, and HTTP is the transport already used for web content delivery.

---

4. Dependent claims

• Claim 6 (intranet + Internet; HTTP over an open proxy/firewall port): essentially taught outright by US 6,128,653 claims 7–9 (HTTP permitted on a selected port; "said selected port represents one of a port 80 and a port 8080"; multiplexing multiple clients through it) and its firewall/proxy discussion (server separated from client by a firewall; proxy 120 for HTTP that would otherwise be blocked). Adding US 6,440,409 (Openwave/Phone.com, interactive two-way data communication through a gateway/proxy) reinforces it. Motivation: the patent's own specification recites this as the problem to be solved. This is the strongest obviousness case in the patent.
• Claims 2–5 and 13–16 (local memory storing app + multimedia data; continued offline access; manual data entry while disconnected; automatic upload on reconnection): US 5,793,365 discloses a memory storing per-user storage structures and an "object shelf" retaining data files in local memory. The offline-compose-then-upload-on-reconnect behavior is squarely the store-and-forward paradigm of US 6,421,706 (WorldCom — "real-time and store and forward information transfer" with a feedback mechanism) and the transparent client/server synchronization of US 6,023,698 (IBM — "transparently registering and updating information over the internet"). Motivation: HTTP is a stateless request/response protocol (admitted in US 6,785,708's background), so a resident HTTP client that must survive disconnection naturally buffers locally; offline message composition was a ubiquitous e-mail/instant-messaging convenience. Risk note: the specific combination — an HTTP-resident chat client that caches multimedia data for offline access and auto-flushes user-entered data on reconnect — is the most detailed and least directly met by a single reference; a validity challenge here would lean harder on a "design choice" argument and on the breadth of "data."
• Claim 7 (server checks client connection/chat-readiness over HTTP): US 5,793,365's activity-level detection and continuous updating of the user's displayed state (including "engaged in a communication with another user") is the same function; US 6,785,708's user objects and clear-to-send/connection semantics supply the server side. Substituting HTTP polling for the presence mechanism is a predictable transport substitution.
• Claim 8 (CGI interface continuously distributing character-form information from an external information provider): the Gundavaram CGI Programming NPL (cited on the face) plus the admitted push technology and the "external contents information provider… through WEB server 1 and CGI interface" architecture in the patent's own FIG. 1 description. US 6,023,698 (updating information over the Internet) provides the mechanism. Strongly obvious.
• Claims 10–12 (multimedia applications; motion picture/still picture/character/graphic/voice; simultaneous display): US 6,785,708 expressly names RealAudio, Shockwave, Java applets and synchronized ad banners as supported media types; US 6,199,082 (Microsoft — separate design and content in a multimedia publishing system) and US 6,038,296 (Lucent — Internet/intranet user interface to a multimedia messaging system) and US 5,974,449 (Carmel Connection — multimedia messaging between disparate platforms) each supply media delivery/display in a network client. The claimed "voice communication" (the spec's videophone embodiment) is met by US 6,785,708's audio/streaming support and by the 1996 NPL documenting live audio and Internet conferencing.
• Claim 17 (aggregate): obvious for the union of the Combination-1 and Combination-2/3 reasons plus the store-and-forward rationale above. Because it merely aggregates dependent-claim limitations already separately obvious, KSR's "combination of familiar elements according to known methods" rationale applies with the least resistance.

---

5. Where the obviousness case is weakest

Be candid about exposure, because this matters if the analysis is ever tested:

1. No single reference and no confident two-reference combination discloses the exact conjunction of (a) non-browser resident application, (b) same display window, (c) chat and multimedia concurrently, (d) all over HTTP, (e) with a server-side chat/CGI layer. The pieces are individually present; their pairwise couplings are mostly present; but the full conjunction requires a genuine 3–4 reference combination. Under KSR that is permissible, but a patent owner would argue the art "taught the desirability of, but not the design of" the integrated portal — and would point to the examiner's allowance over exactly these references.
2. Statutory (AIA-era) examination reality: the claims survived these 16 references. That is not proof of non-obviousness (the examiner's record is unknown to us), but it does shift the burden narrative.
3. Objective indicia — no evidence located. There is no litigation, no reexamination, and no secondary-considerations record for this patent (consistent with the prior sections: expired 2018-09-16, last recorded event a 2016 maintenance fee). Any "commercial success / long-felt need" argument would have to be built from the client product (if identifiable) and would face the nexus problem, because the specification itself concedes the commercial prominence of the pre-existing ICQ-type portal paradigm.
4. § 102(e) mechanics: several of the strongest references (6,128,653; 6,785,708; 6,484,196; 6,421,706; 6,144,991) are § 102(e) art, usable in § 103 combinations as of their filing dates, but not as § 102(b) publications. Conversely, US 5,793,365 and US 5,764,916/US 5,796,393 (family cites) are § 102(b) — a challenge should lead with those. US 6,446,130 must be excluded entirely.
5. Specification admissions are the most powerful tool here: the Background Art concedes every functional premise of the invention (IRC/ICQ resident clients, presence display, push, CGI, port-80-only corporate proxies). Under KSR, admissions plus a known market incentive are usually enough to carry the motivation element without a specific "teaching, suggestion, or motivation."

---

6. Summary conclusion

The single most defensible invalidity theory is claim 6, then claim 1 on the Combination-1 rationale. The hardest claim to invalidate is the offline-input/auto-upload cluster (claims 4–5, 15–16), where the challenge rests on the store-and-forward references plus the statelessness of HTTP.

Caveats on my evidence base: (i) I verified US 5,793,365 (claims/abstract: https://insight.rpxcorp.com/patent/[US5793365A](/patent/US5793365A); PDF: http://patentimages.storage.googleapis.com/26/3f/1f/fe3ee78c0aa374/US5793365.pdf), US 6,128,653 (claims 1–10, incl. port 80/8080, at http://www.everypatent.com/comp/pat6128653.html), US 6,144,991 (http://www.everypatent.com/comp/pat6144991.html), and US 6,785,708 (full spec/claims at https://www.freepatentsonline.com/[7263526](/patent/7263526).html, the CIP that claims priority to it). (ii) For US 5,974,446, US 5,956,491, US 6,484,196, US 6,578,067, US 6,023,698, US 6,038,296, US 6,421,706, US 6,440,409, US 6,199,082, US 5,974,449, and US 6,240,443 I am relying on the titles/assignees shown on the Google Patents face of US 6,857,006 (https://patents.google.com/patent/US6857006/en) plus my background knowledge; those characterizations should be confirmed against the references' full texts before being relied on as element-by-element mappings. (iii) I did not locate any reexamination or court record applying § 103 to this patent, so the conclusions above are analytical predictions, not reported outcomes.