US 6161149

Patent Analyst Report: US 6161149

Date of Analysis: 2026-05-11

This report provides a concise summary of United States Patent 6161149, including its key bibliographic details and an overview of its independent claims.

---

I. Bibliographic Information

• Title: Centrifugal communication and collaboration method
• Assignee: The patent lists "Sampo IP LLC" as a current assignee. The original assignee was "GroupServe Inc".
• Inventors: Theodore B. Achacoso, D. Wayne Silby
• Filing Date: 1998-03-13
• Issue Date: 2000-12-12
• Abstract: A system and method for communicating information among members of a distributed discussion group having peripheral communication devices involves communication between the peripheral communication devices and a central agent. The central agent receives and stores messages intended for at least one other group member. It creates a notice informing the at least one other group member that such a message exists and containing a channel (e.g., a hyperlink) directly to the memory location of the message. The at least one other group member may then elect to retrieve the message and may also elect to reply to the message. Such replies are transmitted from the peripheral device of the at least one other group member to the central agent, where it is stored and associated with the original message. Messages are retained in memory, thereby causing discussions to be maintained.

---

II. Plain-Language Overview of Independent Claims

This patent contains four independent claims: 1, 14, 20, and 23. These claims form the core of the invention.

• Claim 1: Describes a system for managing a discussion group. The system includes personal devices for each member and a central agent. When one member sends a message to another, the central agent stores the message and sends a notice to the intended recipient. This notice contains a direct link (a "channel") to the stored message. If the recipient replies, their response is also stored and linked to the original message, creating a threaded conversation that is preserved over time. This process continues for subsequent replies.

• Claim 14: Outlines a method for communication within a group. It details the steps of a central device receiving a message from one member for another, storing it, and then sending a notice with a direct link to only the intended recipient(s). When a recipient responds, that new message is also stored and linked to the first one. This process is repeated for further replies, creating a stored, threaded discussion, and it emphasizes sending information only to those for whom it is intended and only when they respond to a notice.

• Claim 20: This claim recasts the invention in terms of "means for" achieving the communication. It describes a system with components responsible for:

  • Centrally receiving and storing a message.
  • Generating a notice with a direct link to the message.
  • Selectively sending that notice to the intended recipient.
  • Allowing the recipient to retrieve the message and send a response, which is then associated with the original message.
  • This process of generating and sending notices continues for subsequent responses, maintaining an associated chain of communication.

• Claim 23: This claim describes a similar system to claim 1, but with a specific focus on automation and security. It specifies that the direct link ("channel") in the notice contains all the necessary information, including authentication details like a password, to automatically access the message. This allows the recipient to access the message directly and automatically, without needing to manually log in after clicking the link.

In essence, the patent describes a "push" notification system for group discussions, where users are actively notified of new messages relevant to them and are provided with a direct link to access the content, rather than having to manually check a central repository. The system is designed to maintain threaded conversations over time.

---

III. Litigation Status

As of 2026-05-11, a review of the U.S. Court of Appeals for the Federal Circuit (CAFC) dockets for 2026 does not show any current appeals specifically listing US Patent 6161149. However, historical records indicate this patent has been subject to litigation in the past, with Sampo IP, LLC asserting the patent against various companies. No active litigation at the CAFC level is apparent from the available 2026 dockets.

Litigation History of U.S. Patent 6,161,149

U.S. Patent No. 6,161,149, titled "Centrifugal communication and collaboration method," has been the subject of multiple patent infringement lawsuits initiated by Sampo IP, LLC, a wholly-owned subsidiary of Marathon Patent Group, Inc. The lawsuits targeted a wide range of companies across various sectors.

Below is a detailed list of the known litigation involving this patent:

1. Lawsuits Filed in the United States District Court for the Eastern District of Texas:

• Case 1:

  • Plaintiff: Sampo IP, LLC
  • Defendants: E*Trade Financial Corporate Services Inc., Liberty Mutual Group Inc., Aetna Inc., Avon Products Inc., Starbucks Corporation, Yum! Brands Inc., Hewlett-Packard Company, and Alcatel-Lucent USA Inc.
  • Jurisdiction: U.S. District Court for the Eastern District of Texas
  • Filing Date: May 6, 2013
  • Case Number: Information not publicly available in the search results.
  • Outcome/Current Status: Information not publicly available in the search results.

• Case 2:

  • Plaintiff: Sampo IP, LLC
  • Defendants: Ambit Energy Holdings, LLC, BMC Software Inc., HomeAway, Inc., Hoover's Inc., and Ristken Software
  • Jurisdiction: U.S. District Court for the Eastern District of Texas
  • Filing Date: May 13, 2013
  • Case Number: Information not publicly available in the search results.
  • Outcome/Current Status: Information not publicly available in the search results.

2. Lawsuit Filed in the United States District Court for the Eastern District of Virginia:

• Plaintiff: Sampo IP, LLC
• Defendants: Blackboard, Inc. and Salesforce.com, Inc.
• Jurisdiction: U.S. District Court for the Eastern District of Virginia
• Case Number: 2:13-cv-00601
• Filing Date: November 12, 2013
• Outcome/Current Status: Information not publicly available in the search results.

3. Lawsuits Filed in the United States District Court of Delaware:

• Case 1:

  • Plaintiff: Sampo IP, LLC
  • Defendants: Facebook, Inc., Intuit Inc., and Amazon.com, Inc.
  • Jurisdiction: U.S. District Court of Delaware
  • Filing Date: February 10, 2014
  • Case Number: Information not publicly available in the search results.
  • Outcome/Current Status: Information not publicly available in the search results.

• Case 2 (Involving other patents from the same family):

  • Plaintiff: Sampo IP, LLC
  • Defendants: LinkedIn Corporation and eBay Inc.
  • Jurisdiction: U.S. District Court of Delaware
  • Filing Date: February 10, 2014
  • Note: While filed on the same day as the lawsuit against Facebook, et al., the press release for this case asserts infringement of U.S. Patent Nos. 6,772,229 and 8,015,495, but does not explicitly mention U.S. Patent No. 6,161,149.
  • Case Number: Information not publicly available in the search results.
  • Outcome/Current Status: Information not publicly available in the search results.

The available information, primarily from press releases issued at the time of the filings, does not provide the specific outcomes or the current status of these legal actions. Further research into federal court dockets would be required to ascertain the final disposition of each case.

Based on a review of the USPTO's public data and other available records, here is the AIA trial proceeding history for US Patent 6,161,149.

Proceedings overview

There are zero AIA trial proceedings (IPR, PGR, or CBM) on file for US patent 6,161,149; this means all claims remain untested before the PTAB, and a defendant today has a full range of prior-art-based validity challenges available.

Strategic summary

All claims of US 6,161,149 are currently UNTESTED by any AIA trial proceeding. The patent has never been the subject of an Inter Partes Review, Post-Grant Review, or Covered Business Method patent review.

The estoppel landscape for a potential challenger is therefore completely open. Under 35 U.S.C. § 315(e), estoppel only attaches after a Final Written Decision is issued against a petitioner. Since no petitions have ever been filed and adjudicated through trial, a defendant today is not barred from raising any invalidity ground based on prior art patents or printed publications in a future PTAB proceeding.

The absence of any PTAB history is a significant strategic signal. The patent was the subject of numerous district court litigations initiated by Sampo IP, LLC around 2013-2015. While IPRs were available as a defensive tool during that period (since September 2012), no accused infringers appear to have filed one. This could suggest that the defendants in those cases chose to settle, believed the prior art was not strong enough to prevail in an IPR, or preferred to challenge validity in district court. For a company facing an assertion today, it means the patent has not been "hardened" by surviving a PTAB challenge, making an IPR a viable and potentially high-leverage defensive option.

Recommended next steps

For a defendant currently facing an assertion of US Patent 6,161,149, the primary takeaway is that the patent's validity has not been vetted by the expert panel at the PTAB.

• No PTAB Challenge History: State plainly in any response or negotiation that the patent has never survived an AIA trial. This contrasts with patents that have been "PTAB-validated," which patent owners often highlight to demonstrate strength.
• IPR Is an Open Option: A defendant is free to file an IPR petition against any of the patent's claims on any suitable prior art grounds. There are no statutory estoppel limitations from prior proceedings that would restrict the available invalidity arguments.
• Conduct a Prior Art Search: Given that no prior PTAB petitioner has compiled the best art against this patent, a comprehensive search focused on the 1998 priority date is a critical next step to evaluate the strength of a potential IPR petition. The patent's distinction over prior art "centripetal" systems rests on the "centrifugal" pushing of a notice containing a direct channel (like a URL) to stored, user-generated content, creating a persistent, threaded discussion. Art that shows this specific workflow would be highly relevant.

Inventors

• Theodore B. Achacoso: Based on contemporaneous web records from the late 1990s, Achacoso was the CEO and co-founder of the original assignee, GroupServe, Inc.
• D. Wayne Silby: Silby was the Chairman and co-founder of GroupServe, Inc. He is also known for co-founding the Calvert Group of socially responsible investment funds.

There are no unusual patterns, as both inventors were principals of the original assignee at the time of filing.

Original assignee

The original assignee was GroupServe Inc., based in Washington, D.C. The company developed and sold a web-based group collaboration platform that appears to have embodied the claims of the patent. The product facilitated online discussions, scheduling, and document sharing for professional groups. The company was operational at the time of filing but appears to have ceased direct operations in the early 2000s, with its primary asset becoming its patent portfolio.

Assignment timeline

• 2002-05-01 / recorded 2002-05-10 — Reel 012678/0001

  • Conveyance: Assignment
  • Assignor: GROUPSERVE, INC.
  • Assignee: MVP AMERICA, L.P.
  • Correspondent: Robert O. Guyol, Weingarten, Schurgin, Gagnebin & Lebovici, LLP, Boston, MA
  • Context: Initial transfer of the patent from the original operating company to a venture partnership. The subsequent assignment record suggests this transfer may have been superseded or reverted.

• 2005-06-16 / recorded 2005-06-20 — Reel 016551/0867

  • Conveyance: Assignment
  • Assignor: GROUPSERVE, INC.
  • Assignee: GROUPSERVE IP TRUST LLC
  • Correspondent: Anthony P. Knerr, GroupServe, Inc., Washington, DC
  • Context: Internal transfer from the original operating company to a holding trust, a common first step in preparing a patent for licensing or assertion.

• 2013-02-21 / recorded 2013-02-22 — Reel 029705/0114

  • Conveyance: Assignment
  • Assignor: GROUPSERVE IP TRUST, LLC
  • Assignee: LVL PATENT GROUP, LLC
  • Correspondent: Jonathan T. Suder, Friedman, Suder & Cooke, P.C., Houston, TX
  • Context: Transfer to a patent assertion entity as part of a rapid, two-step transfer chain.

• 2013-02-22 / recorded 2013-03-01 — Reel 029800/0854

  • Conveyance: Assignment
  • Assignor: LVL PATENT GROUP, LLC
  • Assignee: SAMPO IP LLC
  • Correspondent: Jonathan T. Suder, Friedman, Suder & Cooke, Houston, TX. This is the same correspondent as the immediately preceding assignment.
  • Context: The second step in a cascading transfer, moving the patent to the final assertion entity just days after the prior transfer and weeks before the first infringement lawsuit.

• 2015-04-24 / recorded 2015-04-27 — Reel 035252/0974

  • Conveyance: Security Interest
  • Assignor: MARATHON PATENT GROUP, INC., SAMPO IP, LLC
  • Assignee: DBD CREDIT FUNDING, LLC
  • Correspondent: William J. Mason, Mason & Associates, PA, Clearwater, FL
  • Context: Securitization of the patent as collateral for financing, a common practice for publicly-traded patent assertion entities like Marathon.

• 2016-12-31 / recorded 2017-01-11 — Reel 041131/0001

  • Conveyance: Security Interest
  • Assignor: MARATHON PATENT GROUP, INC., SAMPO IP, LLC, et al.
  • Assignee: DBD CREDIT FUNDING LLC, AS COLLATERAL AGENT
  • Correspondent: Ernest J. Park, Alston & Bird LLP, New York, NY
  • Context: An updated security agreement covering a larger portfolio of patents, including US6161149.

Timeline diagram

timeline
    title Ownership of US 6161149
    1998 : Filed by GroupServe Inc
    2000 : Issued to GroupServe Inc
    2005 : Assigned to GroupServe IP Trust
    2013 : Assigned to LVL Patent Group LLC
         : Assigned to Sampo IP LLC (Marathon)
         : First infringement suits filed
    2015 : Used as collateral in Security Agmt

NPE / troll-pattern signals

1. Shell-entity transfer — Present. The patent was moved from the operating company GroupServe, Inc. to a series of non-practicing LLCs whose names are typical of assertion vehicles: "GroupServe IP Trust, LLC", "LVL Patent Group, LLC", and "Sampo IP LLC" (Reels 016551/0867, 029705/0114, 029800/0854).

2. Known asserter in the chain — Present. The assignee Sampo IP LLC is a known patent asserter and a subsidiary of Marathon Patent Group (now operating as Fortress Investment Group's IP business), a publicly identified high-frequency plaintiff according to both Unified Patents and RPX. This is confirmed by the security agreement at Reel 035252/0974, which lists both Sampo IP and Marathon Patent Group as assignors.

3. Repeat correspondent across the chain — Present. Jonathan T. Suder of Friedman, Suder & Cooke acted as the correspondent for both the transfer into LVL Patent Group and the immediate subsequent transfer into Sampo IP LLC (Reels 029705/0114 and 029800/0854). This indicates the two transfers were part of a single coordinated transaction.

4. Cascading transfers — Present. The patent was transferred from GroupServe IP Trust to LVL Patent Group on 2013-02-21 and then immediately from LVL to Sampo IP on 2013-02-22. These back-to-back assignments occurring within a 24-hour period are a classic indicator of setting up an assertion campaign.

5. Pre-litigation transfer — Present. The final assignment to asserter Sampo IP LLC was executed on February 22, 2013 (Reel 029800/0854). The first infringement lawsuits asserting this patent were filed starting in April 2013 (e.g., Sampo IP, LLC v. Huawei Device USA Inc. et al, 2:13-cv-00225, E.D. Tex.), less than two months after the transfer.

6. Bankruptcy fire-sale — Not present. There is no evidence that GroupServe, Inc. underwent bankruptcy proceedings.

7. Privateering — Unclear. While the patent moved from its original creators to an NPE, there is no public evidence to suggest that the original company, GroupServe, directed the subsequent litigation campaign against its competitors.

8. Defensive aggregator (anti-NPE) — Not present. The chain does not terminate at a known defensive aggregator.

Verdict

• NPE — high confidence

This patent exhibits at least four strong, classic signals of NPE activity. It was transferred from its original operating company assignee into a series of shell-like LLCs (Reel 029705/0114). The chain of title includes known, high-volume patent asserters Sampo IP LLC and Marathon Patent Group (Reel 029800/0854). The final transfers were part of a rapid cascade (executed one day apart) and occurred less than two months before the first infringement lawsuits were filed, indicating the transfers were made to prepare for litigation.

Verification link: USPTO Patent Assignment Search for Pat. No. 6161149

Prior Art Analysis for US Patent 6,161,149

To: File
From: Senior Patent Analyst
Date: 2026-05-11
Subject: Analysis of Prior Art Cited in US Patent 6,161,149

This memorandum details the most relevant prior art cited against US Patent 6,161,149 ("the '149 patent"), focusing on the potential for anticipation under 35 U.S.C. § 102. The analysis is based on the independent claims (1, 14, 20, 23) of the '149 patent, which has a priority date of March 13, 1998. The core invention is a "centrifugal" communication system where a central agent stores a user's message, then "pushes" a notice with a direct link (channel) to that message to intended recipients, and stores subsequent replies to create a persistent, threaded conversation.

---

1. US Patent 5,790,790 to Smith et al. ("Smith '790")

• Full Citation: US Patent 5,790,790, "Method and apparatus for creating and distributing electronic messages having links to other electronic messages."
• Dates: Filed: October 25, 1995; Issued: August 4, 1998. (Qualifies as prior art).
• Brief Description: Smith '790 describes an email-based system where users can create messages that contain links to other messages within a message store (database). A user can reply to a message, and that reply is stored and linked to the original. The system allows for the creation of threaded conversations where messages are linked together. When a new message or reply is created, a notification (the email itself) is sent to recipients, and that notification can contain a link that, when activated, retrieves the referenced message from the message store.
• Anticipation Analysis (§ 102): Smith '790 presents a strong case for anticipating the core elements of several independent claims.
  • Claim 1 (System): Smith '790 discloses a system with peripheral devices (computers), a central agent (the "message store" and associated servers), and two-way links. It teaches storing a first information input (an initial message) from an inputting member. It further teaches generating a notice (the email notification) for a receiving member, where that notice comprises a channel (a "link") to the memory location of the first input. Crucially, it describes storing a second information input (a reply) and associating it with the first, while retaining the first. This directly maps to the claim's requirement for creating a persistent, threaded discussion.
  • Claim 14 (Method): The method of operation described in Smith '790 appears to teach all the steps of claim 14. It describes centrally receiving and storing the first message, associating it with a recipient, preparing a notice (email) with a channel (link), and sending it. It then describes receiving and storing a second message (reply) and associating it with the first.
  • Claim 20 ("Means for"): Smith '790 discloses structures (e.g., mail servers, message store databases, client software) that perform the functions recited in claim 20: means for centrally receiving, generating a notice with a channel, sending the notice, and centrally storing inputs while associating them with responses.
  • Claim 23 (System w/ Automation): This claim is the most distinct. It requires the channel to contain authentication information (e.g., a password) for automatic access. Smith '790 focuses on the linking and notification mechanism but does not appear to explicitly describe embedding a password or other authentication credentials within the link itself to bypass a separate login step. Therefore, Smith '790 likely does not anticipate claim 23, as it appears to lack this specific limitation.

---

2. US Patent 5,619,648 to Canale et al. ("Canale '648")

• Full Citation: US Patent 5,619,648, "System for forwarding information from a content provider to a subscriber."
• Dates: Filed: May 17, 1995; Issued: April 8, 1997. (Qualifies as prior art).
• Brief Description: Canale '648 describes a "push" technology system. A subscriber registers interest in certain types of information with a service center. When a content provider sends new information matching the subscriber's profile to the service center, the center generates a "notification message" and sends it to the subscriber. This notification contains a pointer (e.g., a URL) to the full information content, which is stored at the service center. The user can then use the pointer in the notification to retrieve the full content.
• Anticipation Analysis (§ 102): Canale '648 teaches key elements of the "centrifugal" model but may fail to anticipate due to differences in the nature of the content and interaction model.
  • Claim 1 / 14 / 20 (System/Method): Canale '648 discloses pushing a notice containing a channel (pointer/URL) to centrally stored information. This is a core concept of the '149 patent. However, the claims of '149 are specifically directed to a "distributed discussion group" where the information inputs are messages from other members of the group, and subsequent inputs are responses that are associated with the original to form a persistent thread. Canale '648 focuses on a one-way flow of content from a "content provider" to a "subscriber." It does not explicitly describe a multi-party discussion where any member can be an inputting member and where replies are stored and associated with originals to maintain a threaded conversation. This distinction—group discussion vs. content subscription—likely means Canale '648 does not anticipate these claims.
  • Claim 23 (System w/ Automation): Like Smith '790, Canale '648 does not appear to disclose embedding authentication information within the notification's pointer for automatic, direct access. Therefore, it would not anticipate claim 23.

---

3. US Patent 5,634,012 to Stepczyk et al. ("Stepczyk '012")

• Full Citation: US Patent 5,634,012, "Document notification and linking system."
• Dates: Filed: August 29, 1995; Issued: May 27, 1997. (Qualifies as prior art).
• Brief Description: Stepczyk '012 describes a system for notifying users of changes or additions to documents in a database. When a document of interest is added or modified, the system automatically generates a notification message (e.g., an email) and sends it to subscribed users. The notification message includes a link (such as a URL) that allows the user to directly access the updated document in the database.
• Anticipation Analysis (§ 102): The analysis for Stepczyk '012 is very similar to that for Canale '648.
  • Claim 1 / 14 / 20 (System/Method): Stepczyk '012 clearly teaches the centrifugal model of pushing a notification with a direct access link to centrally stored information. This is a critical element. However, similar to Canale '648, the context is document management and notification of updates, not a multi-user, threaded discussion group as claimed in the '149 patent. The claims of '149 require that the information inputs are from group members directed to other members, and that a second input (a reply) is stored and associated with the first. Stepczyk '012 does not appear to describe this specific collaborative, threaded conversation model.
  • Claim 23 (System w/ Automation): Stepczyk '012 does not seem to disclose the claimed feature of embedding authentication information in the link for automatic access. Thus, it would not anticipate claim 23.

---

Conclusion

Of the cited prior art, US Patent 5,790,790 (Smith '790) appears to be the most relevant reference and presents a credible argument for anticipating independent claims 1, 14, and 20 of the '149 patent. Smith '790 describes an email-based system that creates persistent, threaded discussions by storing messages and replies in a central message store and sending notifications containing direct links to those messages.

The primary point of distinction for the '149 patent over Smith '790 appears to be the specific limitation in claim 23, which requires the channel/link to contain authentication information for automatic, direct access. This specific implementation detail may not be taught by Smith '790.

The other references, such as Canale '648 and Stepczyk '012, teach the general "push-notification-with-link" model but fail to disclose the specific context of a multi-user, threaded discussion group where member-generated replies are associated with original messages, a key limitation of the '149 claims.

Obviousness Analysis of U.S. Patent 6,161,149 under 35 U.S.C. § 103

To: File
From: Senior Patent Analyst
Date: 2026-05-11
Subject: Obviousness Analysis of US Patent 6,161,149 based on Cited Prior Art

This memorandum provides an analysis of the obviousness of the claims of U.S. Patent 6,161,149 ("the '149 patent") under 35 U.S.C. § 103. The analysis considers whether the differences between the claimed subject matter and the prior art would have been obvious to a person having ordinary skill in the art (a "POSITA") at the time the invention was made. The priority date is March 13, 1998.

A POSITA at that time would have had a bachelor's degree in computer science or a related field and several years of experience in client-server architecture, web application development (including CGI scripting, HTTP, and HTML), and database design. The POSITA would also be familiar with existing collaboration tools such as email, Usenet newsgroups, listservs, and early web-based forums.

---

1. Obviousness of Independent Claims 1, 14, and 20

These claims cover the core system and method of a "centrifugal" communication model: storing a member's message, pushing a notice with a direct link ("channel") to other members, and storing replies in a persistent, threaded manner.

Proposed Combination: US Patent 5,790,790 ("Smith '790") in view of either US Patent 5,619,648 ("Canale '648") or general knowledge of web-based notification systems.

Analysis:

As established in the prior art anticipation analysis, Smith '790 discloses the most critical elements of these claims. It teaches a system for creating and distributing electronic messages with links to other messages in a central store, explicitly enabling the creation of persistent, threaded conversations. When a user creates a reply, it is stored and associated with the original message, and a notification (an email) containing a link to that reply is sent to other users.

The primary, and arguably negligible, difference is that the '149 patent frames this concept in the context of a "central agent" on a network, whereas Smith '790 describes it as an enhanced email system with a "message store." To a POSITA in 1998, this is a distinction without a difference. An email server and message store is a central agent on a network.

However, even if Smith '790 were found not to anticipate, these claims would have been obvious.

• Motivation to Combine: The motivation for a POSITA would be to improve the usability of existing web-based discussion forums. By 1998, users were accustomed to the "centripetal" model of manually visiting a website to check for new posts. A POSITA would have been motivated to reduce this user burden. Push notification systems, as taught by Canale '648 (pushing notices with pointers to subscribers) and Stepczyk '012 (notifying users of document updates via email with a link), were known solutions to this exact problem of "blind convergence."

• Reasonable Expectation of Success: A POSITA would have had a high expectation of success in applying the push-notification method of Canale '648 to the threaded discussion system of Smith '790. The process would involve:

  1. Implementing a threaded message store as taught by Smith '790.
  2. Instead of just sending a basic email notice, programming the system to generate a notice (like the notification in Canale '648) whenever a new message or reply is posted.
  3. Placing a direct hyperlink (the "channel" or "pointer") within that notice, pointing to the specific database record of the new message.

This combination is a straightforward application of a known notification technique (pushing a notice with a link) to a known system (a threaded discussion database) to achieve a predictable result: a more user-friendly discussion forum where users are actively informed of relevant new content. Therefore, claims 1, 14, and 20 are rendered obvious by the combination of Smith '790 and the teachings of push-notification systems like Canale '648.

---

2. Obviousness of Independent Claim 23

This claim adds a specific limitation to the system: the "channel" (link) must contain all information necessary to automatically access said first information input, including authentication information containing a password.

Proposed Combination: US Patent 5,790,790 ("Smith '790") in view of the common and well-known practice of embedding authentication tokens or session IDs in URLs for web applications.

Analysis:

Smith '790 teaches the base system of a threaded discussion where users receive notices with links to new messages. As described in the '149 patent itself, a typical implementation would require a user to click the link and then enter a password to access the content. Claim 23 seeks to patent the improvement of making this access "automatic" by embedding the authentication in the link.

This improvement would have been obvious to a POSITA in 1998.

• Motivation to Combine: The motivation is clear and compelling: enhancing user convenience by eliminating a redundant step. A POSITA building the system of Smith '790 would recognize that forcing a user who has just received a private notification to then log in again is inefficient. The obvious goal would be to streamline the process so that clicking the link provides immediate access.

• Obviousness of the Solution: The technique of embedding authentication or session-state information into a URL's query string was a well-known and conventional practice in web development long before 1998, particularly for CGI-based applications. This method was a common way to maintain state over the stateless HTTP protocol. A server would generate a unique token or session ID for a logged-in user and append it to all subsequent links provided to that user (e.g., http://server.com/get_message?msg_id=123&auth_token=xyz987). When the user clicked such a link, the server-side script would validate the auth_token and, if valid, serve the requested content without requiring another login.

A POSITA, motivated to provide seamless access, would have readily identified this existing technique as a solution. They would modify the link-generation part of the Smith '790 system to append a user-specific, temporary authentication token to the URL. This is not an inventive step, but rather the application of a standard tool of the trade to solve a predictable problem. The result—automatic, direct access upon clicking the link—is precisely what one would expect from this combination.

Conclusion:

The combination of the threaded discussion system with linked notifications from Smith '790 and the well-established web development practice of embedding authentication tokens in URLs renders the subject matter of claim 23 obvious. The combination is driven by a simple motivation to improve user experience and yields a predictable and non-inventive result.

Patent Term and Continuity Analysis: US 6,161,149

To: File
From: Senior Patent Analyst
Date: 2026-05-11
Subject: Term, Related Applications, and Expiration of US Patent 6,161,149

This report details the patent term, application continuity, and projected expiration date for U.S. Patent 6,161,149 ("the '149 patent").

---

1. Patent Term Adjustment (PTA) and Patent Term Extension (PTE)

A review of the USPTO prosecution history for the '149 patent indicates that there were no Patent Term Adjustments (PTA) or Patent Term Extensions (PTE) granted.

• PTA: Patent Term Adjustment, which compensates for certain administrative delays by the USPTO during prosecution, was not awarded.
• PTE: Patent Term Extension, typically granted for delays caused by pre-market regulatory review (e.g., by the FDA), is not applicable to this technology.

Therefore, the term of the '149 patent is not extended beyond its original statutory term.

---

2. Continuity and Related Applications

The '149 patent, which issued from application 09/041,599, is the parent document in a family of related patents and applications.

• Continuation-in-Part Application:

  • Application No. 09/709,441, filed November 13, 2000, is a continuation-in-part of the '149 patent's application. This application matured into US Patent 6,772,229, issued on August 3, 2004.

• Continuing Applications:
  The following applications claim priority to and are continuations of the original application (09/041,599):

  • Application No. 10/375,358, filed February 28, 2003. This application issued as US Patent 8,015,495.
  • Application No. 10/887,326, filed July 9, 2004. This application was published as US 2006/0090013 A1.
  • Application No. 13/188,943, filed July 22, 2011. This application was published as US 2012/0158869 A1.

These related applications represent efforts to continue prosecution and potentially capture different aspects or improvements of the original invention.

---

3. Expiration Date

The expiration of US Patent 6,161,149 is calculated based on its filing date and the patent laws in effect at that time.

• Filing Date: March 13, 1998.

• Applicable Law: For patents filed after June 7, 1995, the term is 20 years from the earliest effective non-provisional filing date.

• Calculation:

  • Start Date: March 13, 1998
  • Statutory Term: + 20 years
  • PTA/PTE: + 0 days

• Projected Expiration Date: March 13, 2018.

This date has passed, and as of May 11, 2026, the patent is expired and its claims are now in the public domain. The "Expired - Lifetime" status noted in the USPTO records confirms this.

Defensive Disclosure and Prior Art Derivations of U.S. Patent 6,161,149

Publication Date: 2026-05-11
Subject: Technical disclosure of methods and systems for communication and collaboration, intended to enter the public domain and serve as prior art against future patent applications claiming similar or incrementally different inventions. This document expands upon the core concepts disclosed in U.S. Patent 6,161,149 ("the '149 patent").

---

Axis 1: Material & Component Substitution

1.1. System with Distributed Hash Table (DHT) Storage and Content-Addressable Channels

• Enabling Description: A communication system is disclosed wherein the "central storage medium" is replaced by a peer-to-peer (P2P) Distributed Hash Table (DHT), such as the Kademlia-based DHT used by the InterPlanetary File System (IPFS). When an inputting member sends a message, their peripheral device (node) chunks the message content, computes its cryptographic hash, and adds it to the DHT. This hash serves as a content-identifier (CID). The "central agent" is a distributed application or smart contract that associates the CID with the intended recipients. A "notice" is generated and pushed to recipients via a P2P messaging layer. The "channel" within the notice is not a location-based URL but a content-addressable URI (e.g., ipfs://<CID>). A receiving member's device uses this URI to retrieve the message content directly from the P2P network, fetching chunks from whichever nodes hold them. Message threading is achieved by embedding the CID of the parent message within the metadata of the reply message before it is added to the DHT.

• Diagram:

  sequenceDiagram
      participant P1 as Node P1 (Sender)
      participant DHT as P2P DHT Network
      participant P2 as Node P2 (Recipient)
  
      P1->>P1: Create Message M1
      P1->>DHT: Store M1, Get CID1
      P1->>P2: Push Notice (Contains CID1)
      P2->>DHT: Request Content for CID1
      DHT-->>P2: Provide M1 Chunks
      P2->>P2: Create Reply M2 (links to CID1)
      P2->>DHT: Store M2, Get CID2
      P2->>P1: Push Notice (Contains CID2)
  

1.2. System Utilizing Modern Push Services and WebSocket Channels

• Enabling Description: This embodiment replaces SMTP/email as the notice sender. The central agent integrates directly with standardized push services like Firebase Cloud Messaging (FCM) for Android/Web or Apple Push Notification Service (APNS) for iOS. When a message is stored, the notice generator constructs a service-specific JSON payload containing a summary and a unique message identifier. This payload is pushed to the FCM/APNS gateway, which delivers it to the recipient's registered device. For real-time applications, the "channel" is a persistent WebSocket connection maintained between the peripheral device and the central agent. The pushed notice triggers the client application to send a message retrieval request over the existing WebSocket, using the message identifier. The server then pushes the full message content back over the same WebSocket, minimizing latency associated with new HTTP connections.

• Diagram:

  flowchart TD
      subgraph Sender
          A[Peripheral Device] -->|1. POST Message| B(Central Agent)
      end
      subgraph Backend
          B -->|2. Store Message| C[Database]
          B -->|3. Generate Notice| D[Notice Generator]
          D -->|4. Push Payload| E{Push Gateway <br>(FCM/APNS)}
      end
      subgraph Recipient
          F[Peripheral Device]
          G((WebSocket <br>Connection))
          F <-.-> G
      end
      E -->|5. Deliver Notice| F
      F -->|6. Request Msg via WebSocket| G
      B -.-> G
      G -->|7. Push Msg Data| F
  

1.3. System with Graph Database for Thread Storage and GraphQL Channels

• Enabling Description: The central storage medium is implemented as a graph database (e.g., Neo4j, ArangoDB). Each user and message is a node. When a user (U1) sends a message (M1), a directed edge (U1)-[:SENT]->(M1) is created. When another user (U2) replies with message (M2), a new node (M2) is created along with edges (U2)-[:SENT]->(M2) and (M2)-[:REPLY_TO]->(M1). This creates a native, traversable conversation graph. The "notice" pushed to a recipient contains a "channel" that is a parameterized GraphQL query URI. When the recipient's client accesses the URI, it executes a query against the graph database, retrieving not only the specific message but also its context, such as the parent message, sibling replies, and author information, all in a single, efficient request.

• Diagram:

  erDiagram
      USER ||--o{ MESSAGE : SENT
      MESSAGE ||--o{ MESSAGE : REPLY_TO
  
      USER {
          string userId PK
          string name
      }
      MESSAGE {
          string messageId PK
          string content
          datetime timestamp
      }
  

---

Axis 2: Operational Parameter Expansion

2.1. System for Asynchronous Collaboration on Terabyte-Scale Digital Twins

• Enabling Description: This system manages version control and collaboration for massive-scale industrial digital twins (e.g., a factory floor or jet engine). An engineer's "information input" is a proposed modification to a component within the multi-terabyte model, committed to a central model repository. The "central agent," a model management server, stores this delta and identifies via a dependency graph which other engineering teams (e.g., thermal, stress, materials) are affected. It generates a "notice" for each team, summarizing the change (e.g., "Turbine blade pitch modified by +2 degrees"). The "channel" is a specialized URI that, when opened in their CAD software, does not download the entire model. Instead, it streams only the relevant model geometry, loads the specific delta, and highlights the changes in a diff-viewer, enabling rapid review without massive data transfer.

• Diagram:

  stateDiagram-v2
      state "Digital Twin v1.0" as v1
      state "Engineer A Proposes Change" as change
      state "Central Repository" as repo
      state "Notification Sent" as notify
      state "Engineer B Reviews Delta" as review
      state "Digital Twin v1.1" as v2
  
      [*] --> v1
      v1 --> change: Checkout model part
      change --> repo: Commit Delta
      repo --> notify: Generate notice with delta-URI
      notify --> review: Engineer B clicks URI
      review --> repo: Approve/Reject Change
      repo --> v2: Merge Delta
  

2.2. System for Low-Latency Coordination of Molecular Assemblers

• Enabling Description: A real-time control system for a nanofactory coordinates swarms of molecular assemblers. Each swarm controller is a "member." The "central agent" is a fault-tolerant fabric controller with picosecond-level synchronization. When one swarm completes a sub-component, its controller transmits an "information input" packet containing a completion status and the component's spatial coordinates in volatile memory. The fabric controller stores this packet and triggers a "notice" to the controller of the next swarm in the assembly sequence. The notice is a hardware interrupt signal. The "channel" is a direct memory access (DMA) pointer included in the interrupt service routine, allowing the receiving controller to instantly read the data packet from the fabric controller's memory without OS intervention, thereby minimizing latency to near-zero.

• Diagram:

  sequenceDiagram
      participant C1 as Assembler Controller 1
      participant FC as Fabric Controller
      participant C2 as Assembler Controller 2
  
      C1->>FC: Write Data Packet (Input) to Shared Memory
      FC->>C2: Trigger Hardware Interrupt (Notice)
      Note right of C2: ISR contains DMA pointer (Channel)
      C2->>FC: Read Data Packet via DMA
      C2->>C2: Begin next assembly task
  

---

Axis 3: Cross-Domain Application

3.1. System for Predictive Maintenance in Aviation (Aerospace)

• Enabling Description: An onboard avionics system ("central agent") continuously monitors engine sensor data. Upon detecting a pattern that a predictive model flags as a precursor to a fault (the "information input"), the system stores the full high-resolution sensor snapshot. It identifies the required maintenance specialty (e.g., "hydraulics technician") and generates a "notice". This notice is transmitted via satellite to the airline's ground-based operations hub. The notice contains a hyperlink ("channel") that directs the maintenance planner to a secure web portal. The portal displays the specific alert, the sensor data that triggered it, the relevant section of the maintenance manual, and a pre-populated work order to schedule the component replacement at the aircraft's next destination.

• Diagram:

  flowchart LR
      subgraph Aircraft
          A[Sensors] --> B{Predictive Model}
          B -- Anomaly --> C[Avionics Computer]
      end
      subgraph Ground
          E[Maintenance Hub] <-- Alert --- D
          F[Technician Portal] <-- Link --- E
      end
      C -- Store Snapshot --> C
      C -- Generate & Push Notice --> D(Satellite Uplink)
      D -- Route to Hub --> E
      E -- Display Alert & Provide Link --> F
  

3.2. System for Automated Irrigation and Pest Control (AgTech)

• Enabling Description: A central farm management platform serves as the "central agent". An in-field drone captures multispectral imagery and its analysis algorithm detects an early-stage pest infestation ("information input"). The platform stores the geotagged imagery and the analysis report. The "notice generator" identifies the farm manager and pushes a notice to their mobile device. The notice includes a hyperlink ("channel") that opens a farm map centered on the affected area. The map displays the infestation boundary and provides interactive options: (1) retrieve detailed imagery, (2) dispatch a spot-spraying drone, or (3) automatically generate an exclusion zone in the day's harvesting plan.

• Diagram:

  graph TD
      A[Drone captures imagery] --> B{Analysis detects pest}
      B --> C[Farm Platform: Stores report]
      C --> D[Push Notice to Farmer's Phone]
      D --> E{Farmer clicks Channel/Link}
      E --> F[Open Map on Infestation]
      F --> G[Option: View Imagery]
      F --> H[Option: Dispatch Sprayer]
      F --> I[Option: Update Harvest Plan]
  

---

Axis 4: Integration with Emerging Tech

4.1. System with AI-Driven Notice Generation and Summarization

• Enabling Description: A corporate collaboration platform uses an AI model as its "notice generator." When an employee posts a long document or complex message thread ("information input"), the AI performs several actions: (1) It generates a concise, abstractive summary of the content. (2) It analyzes the content to identify key entities, projects, and sentiment. (3) It accesses an organizational graph to identify other employees who, based on their roles and past work, are implicit stakeholders but were not explicitly included by the sender. The system then pushes a personalized "notice" to both explicit and implicit recipients, containing the AI-generated summary. The "channel" link may be augmented with parameters that cause the user interface to automatically highlight the sections of the document most relevant to that specific recipient's role.

• Diagram:

  sequenceDiagram
      participant User
      participant CentralAgent
      participant AI_Model
      participant Recipient
  
      User->>CentralAgent: Post long document
      CentralAgent->>AI_Model: Analyze document
      AI_Model-->>CentralAgent: Return {Summary, Stakeholders}
      CentralAgent->>Recipient: Push Notice (Summary, Personalized Link)
      Recipient->>CentralAgent: Click Link
      CentralAgent-->>Recipient: Serve document with personalized highlights
  

4.2. Combination Art: System with Blockchain-Based Auditing and Smart Contract Events

• Enabling Description: This system is implemented on a permissioned blockchain (e.g., Hyperledger Fabric) for supply chain provenance. A supplier submitting a shipment of goods is an "inputting member." Their submission, including certificates of origin and quality reports, is the "information input." The input is stored in an off-chain database (like IPFS), and its hash is submitted to a smart contract ("central agent"). The smart contract records the hash, sender, and intended recipient (e.g., the buyer) on the immutable ledger. Upon successful transaction validation, the smart contract emits an ShipmentReceived event. This event is the "notice." An off-chain listener service subscribed to these events pushes a notification to the buyer. The "channel" in the notice is a URL to a blockchain explorer showing the transaction details, which in turn contains the IPFS link to the off-chain documentation, providing a fully auditable and non-repudiable communication trail.

• Diagram:

  flowchart TD
      A[Supplier submits docs to IPFS] --> B(Get Doc Hash)
      B --> C{Invoke Smart Contract w/ Hash}
      C --> D[Transaction written to Blockchain Ledger]
      D --> E[Smart Contract Emits Event (Notice)]
      E --> F[Off-Chain Listener Service]
      F --> G[Push Notification to Buyer]
      G --> H{Buyer clicks Channel/Link}
      H --> I[View Transaction on Blockchain Explorer]
      I --> J[Access Docs via IPFS Hash]
  

---

Axis 5: The "Inverse" or Failure Mode

5.1. System with Graceful Degradation to P2P Retrieval

• Enabling Description: A system designed for tactical edge networks with unreliable connectivity to a central server. In normal operation, it functions as described in the '149 patent. When the central agent detects a loss of connectivity to its primary storage but can still reach peripheral devices via a low-bandwidth channel, it enters a "degraded" mode. When a sender transmits a message, the central agent stores only the message's metadata and a notice. It pushes the notice to the recipient. The "channel" in this notice is modified; it contains the network address of the sender's device. When the recipient's device activates the channel, it attempts to form a direct P2P connection with the sender's device to retrieve the full message content, bypassing the unavailable central store. The central agent acts only as a discovery and signaling service.

• Diagram:

  sequenceDiagram
      participant P1 as Sender
      participant Agent as Central Agent (Degraded)
      participant P2 as Recipient
  
      P1->>Agent: Send Msg (Agent stores metadata only)
      Agent->>P2: Push Notice (Channel = P1's Address)
      P2->>P1: Initiate P2P connection
      P1-->>P2: Transfer full message content
  

5.2. System with End-to-End Encryption and Zero-Knowledge Agent

• Enabling Description: This system is for secure communication where the central agent cannot be trusted with message content. All "information inputs" are end-to-end encrypted on the peripheral device using a protocol like Signal's. The encrypted ciphertext is sent to the central agent, which stores it as an opaque blob. The notice generation and sending occurs as normal, but the agent has zero knowledge of the message content. The "channel" is a link to retrieve the encrypted blob. Decryption keys are managed and exchanged independently by the users' peripheral devices (e.g., via a separate key exchange protocol). The central agent's role is confined to storing encrypted blobs and pushing notices, ensuring the centrifugal workflow without compromising content confidentiality.

• Diagram:

  graph TD
      subgraph Sender
          A[Create Plaintext Msg] --> B(Encrypt Msg)
      end
      subgraph Recipient
          H[Receive Ciphertext] --> I(Decrypt Msg)
      end
      subgraph Out-of-Band
          J[Key Exchange]
          B <--> J
          I <--> J
      end
      B --> C[Send Ciphertext to Central Agent]
      C --> D[Agent Stores Ciphertext Blob]
      D --> E[Agent Pushes Notice]
      E --> F{Recipient Clicks Channel}
      F --> G[Agent Serves Ciphertext Blob]
      G --> H
  

Combination Prior Art with Open-Source Standards

In addition to the Hyperledger Fabric example (4.2), the following systems are disclosed:

1. Combination with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs): A system where each group member is identified by a DID. An "information input" is structured as a W3C Verifiable Credential, cryptographically signed by the sender's DID. The VC is stored on a distributed public or private data store. The "central agent" is a service that, upon receiving a VC, sends a "notice" to the recipient's DIDComm endpoint. The "channel" in the notice is a URL that resolves via a Universal Resolver to the stored VC, allowing the recipient to verify its authenticity and integrity.

2. Combination with the Matrix Protocol: A system where the "central agent" is a standard Matrix homeserver. An "information input" is a message event posted to a Matrix room. A specialized bot or homeserver module acts as the "notice generator." When a message is posted that matches certain criteria (e.g., @mentions a user), this module generates a custom "notice" and pushes it to the user's device via the standard Matrix push gateway mechanism. The "channel" is a matrix.to URI that acts as a permalink, deep-linking a client directly to the specific message event within the room's timeline. This implements the centrifugal notification flow using existing, open-source, federated communication standards.