Obviousness

Obviousness Analysis of U.S. Patent 11,349,787 Under 35 U.S.C. § 103

Based on the prior art cited during the prosecution of U.S. Patent 11,349,787 and its parent applications, the independent claims of the '787 patent appear to be obvious under 35 U.S.C. § 103. An invention is considered obvious if the differences between the claimed invention and the prior art are such that the invention as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (PHOSITA). The following analysis presents combinations of the provided prior art references that would render the claims obvious.

The core elements of independent claims 1 and 17 of the '787 patent are:

1. Receiving a communication request from a web browser of an unauthenticated user.
2. Connecting the user with a responder who may use a different communication protocol.
3. Determining and using a conversation identifier to track and associate all messages in the conversation.
4. Persistently storing the conversation linked to the identifier.
5. Retrieving the stored conversation upon a subsequent request from the user's web browser.

---

Combination 1: U.S. Patent No. 9,413,812 (LivePerson) in view of U.S. Patent No. 8,930,480 (IMForward)

This combination of references would have rendered the claimed invention obvious to a PHOSITA. LivePerson ('812) provides the foundational system, and IMForward ('480) provides a known method for implementing a key feature.

• Base Reference: LivePerson ('812 patent)
  The LivePerson patent discloses a comprehensive system that teaches the majority of the '787 patent's claimed elements. It describes a system for facilitating communication between a website visitor (an unauthenticated user) and an agent (a responder). The communication is initiated through a chat window on the website. Critically, LivePerson explicitly teaches the ability to transfer the conversation to a different medium, such as from web chat to SMS, if the user leaves the website. To accomplish this, the system must inherently use a persistent session identifier—the "conversation identifier" claimed in the '787 patent—to link the messages across different platforms and maintain conversational context. This system therefore teaches the core concepts of receiving a request from a web browser, connecting to a responder, managing the session with an identifier across different communication platforms, and storing the conversation to enable this continuity.

• Secondary Reference: IMForward ('480 patent)
  The IMForward patent teaches a method and apparatus for a "universal translator for text messaging" that allows seamless communication between users on different and incompatible messaging platforms (e.g., SMS, AOL Instant Messenger, Yahoo Messenger). It provides the specific technical details for a server-side system that can receive a message in one protocol, translate it, and forward it to a recipient using another protocol.

• Motivation to Combine:
  A PHOSITA, starting with the system described by LivePerson, would be motivated to enhance its cross-platform capabilities. The LivePerson system already establishes the need to communicate across different platforms (web chat to SMS). A PHOSITA seeking to build a more robust and flexible version of this system—one that allows responders to use a wide variety of communication tools beyond just SMS—would naturally look for known solutions for protocol translation. The IMForward patent provides exactly this solution: a universal translation engine.

  The motivation is commercial and practical: to increase the efficiency and flexibility of the customer service agents (responders). By integrating the universal translation technology of IMForward into the LivePerson framework, agents would not be limited to a specific application or protocol but could use their preferred real-time communication tool. This combination of a web-based chat portal (LivePerson) with a multi-protocol communication bridge (IMForward) directly results in the system claimed in the '787 patent, where a web user communicates with a responder on a different platform, and a central server manages the conversation. This would have been a predictable and obvious improvement to a PHOSITA at the time.

---

Combination 2: U.S. Patent No. 8,364,741 (Avaya) in view of U.S. Patent No. 9,413,812 (LivePerson)

This combination demonstrates that even from a more foundational starting point, the claimed invention would have been an obvious next step.

• Base Reference: Avaya ('741 patent)
  The Avaya patent discloses a foundational "communications portal" for managing interactions between external users on a website and internal agents. It teaches the core elements of establishing a communication session (e.g., a chat) initiated by a website user and routing that communication to an appropriate agent. This provides the basic framework for claims 1 and 17: a server that receives a communication from a web browser and connects it to a responder.

• Secondary Reference: LivePerson ('812 patent)
  As described previously, the LivePerson patent teaches a specific and powerful improvement to such a basic system: ensuring conversation continuity when a user leaves the website by transferring the conversation to another medium like SMS. This solves a known problem in the field of online customer support.

• Motivation to Combine:
  A PHOSITA tasked with improving the Avaya communications portal would face the well-known business problem of abandoned chat sessions. When a user closes their browser or navigates away, the conversation is lost, leading to a poor customer experience. The LivePerson patent provides a direct and explicit solution to this problem. It would have been obvious for a PHOSITA to enhance the Avaya system by incorporating the continuity feature described by LivePerson.

  This combination would involve modifying the Avaya portal to:

  1. Assign a persistent identifier to each conversation, not just a temporary session ID.
  2. Incorporate logic to bridge communications to other platforms (like SMS), as taught by LivePerson.
  3. Store the conversation history to allow it to be seamlessly continued on the new platform.

  The result of this combination is a system that receives a web request, routes it to a responder, and maintains the conversation using a persistent identifier across multiple platforms—the very essence of the '787 patent's claims. The element of retrieving the conversation upon the user's return is a trivial and predictable extension of this functionality; if the conversation is stored for continuity, making it visible to the user upon their return via a session cookie is a standard feature for user convenience, not an inventive step. Therefore, combining the foundational portal of Avaya with the known continuity-enhancing features of LivePerson would render the claims of the '787 patent obvious.