Obviousness

Obviousness Analysis of US Patent 8571194 under 35 U.S.C. § 103

This analysis examines the obviousness of US patent 8571194, "System and method for initiating a conference call," based on the prior art explicitly cited within the patent and general knowledge available at its priority date of December 22, 2003. The core of the invention lies in using an instant messaging (IM) system to trigger and manage the initiation of a conference call, particularly by automatically including current IM session participants without requiring individual selection or separate registration with a conference call server.

A person having ordinary skill in the art (PHOSITA) at the time of the invention would have been familiar with instant messaging systems (including presence awareness), shared application sessions, and various methods of initiating conference calls (e.g., "meet me" calls and host-initiated calls). The patent itself highlights the recognized problem that "the integration of the call into the collaboration process has not yet been addressed" despite the clear need for voice communication during real-time collaboration and instant messaging. The motivation for a PHOSITA to combine existing technologies would be to overcome the inefficiencies and lack of spontaneity in traditional conference call setups, as explicitly stated in the patent's background.

Combination of Prior Art: U.S. Patent Publication No. 20030018725 and General Knowledge of IM and Telephony

The most relevant prior art for an obviousness analysis, aside from the patent's own parent applications (which would likely anticipate rather than merely render obvious the claims if fully disclosed), is U.S. Patent Publication No. 20030018725 (hereafter "US'725"). This reference, incorporated by reference into US8571194, describes "shared application sessions" that involve multiple viewers interacting with a software application over a network, and potentially includes "presence awareness" and "underlying communication" for collaborative environments.

Motivation to Combine:
The patent US8571194 explicitly states the problem it aims to solve: "real-time collaboration products imply the need for a conference call... yet the integration of the call into the collaboration process has not yet been addressed". It also notes the inefficiencies of existing conference call methods, such as requiring manual dialing or passcodes, making calls difficult to make spontaneous. A PHOSITA, observing these challenges in 2003, would be motivated to integrate the functionality of IM (which provides presence and an established communication channel among a defined group) with known host-initiated conference call methods to achieve a more seamless and spontaneous voice conferencing experience within a collaborative context like that described in US'725. The goal would be to reduce user effort and enable immediate voice communication among active collaborators.

Obviousness of Independent Claims

Claims 1, 6, and 11 (Client-Side Functionality)

These claims describe a non-transitory computer readable medium for a first party's device to:

• Display IM messages between current IM session participants (Claims 1, 6, 11).
• Display an indication of whether other participants are connected to the IM session (presence) (Claims 1, 6, 11).
• Display an option to automatically initiate voice communication between current IM session participants, without requiring individual selection of participants and without requiring separate registration with a conference call server (Claims 1, 6, 11).
• Request and establish voice communication upon selection (Claims 1, 6, 11).
• Further claims specify a click-on icon for single-step selection (Claims 3, 8, 13), display within a common window (Claims 4, 9, 14), and inclusion of audio/video (Claims 5, 10, 15).

Reasoning for Obviousness:

1. Display IM messages and presence: US'725 describes shared application sessions with "multiple viewers" and "underlying communication," implying a mechanism for displaying ongoing collaboration, which could include text chat. General knowledge of IM systems in 2003 confirms that client applications routinely displayed chat windows showing messages exchanged between parties and their presence (online/offline status). It would be a straightforward design choice for a PHOSITA to include such IM capabilities within a collaborative environment.
2. Display an option to automatically initiate voice communication between current IM session participants: Given the explicit need for voice communication during collaborative sessions as highlighted in US8571194's background, a PHOSITA would find it obvious to provide a quick way to escalate a text-based IM or shared application session to a voice call. Displaying a "call now" button or similar icon (as described in FIG. 3 of US8571194 and in dependent claims 3, 8, 13) within the existing IM or collaboration interface would be a predictable interface design improvement to facilitate this transition.
3. "Without requiring individual selection of potential members": When users are actively engaged in an IM session or shared application session, the group of "current participants" is already defined and known by the system (client or server). It would be an obvious simplification, aimed at reducing user effort and increasing spontaneity, to default the voice conference invitation to all current participants of that active session.
4. "Without requiring registration with a conference call server for establishing the voice communication by potential members": Host-initiated conference calls were a known practice in 2003, where a host or a service would dial out to participants, thereby eliminating the need for participants to manually dial in or enter passcodes. By combining this known host-initiated call model with the IM system's awareness of participant contact information (either stored or dynamically retrieved), it would be obvious to a PHOSITA to configure the system to make outbound calls to participants, thus removing the registration burden from them.
5. Other dependent claims: Displaying in a common window (Claims 4, 9, 14) is a standard user interface design for integrated applications. Including audio and video (Claims 5, 10, 15) in conference calls was also a known capability, and extending an IM-initiated call to include these modalities would be a natural progression for enhancing collaborative communication.

Claim 16 (Server-Side Functionality)

This claim describes a non-transitory computer readable medium for a server to:

• Exchange IM messages between a first party and at least one other party (current IM session participants) (Claim 16).
• Send to the first party an indication of whether the at least one other party is communicably connected to the IM session (Claim 16).
• Receive a request from the first party to establish voice communication amongst current IM session participants, where the request lacks specific identification of the at least one other party and does not require registration with a conference call server by potential members (Claim 16).
• Determine the at least one other party from information associated with the IM session after receiving the request (Claim 16).
• Establish voice communication between the first party and those determined other parties (Claim 16).

Reasoning for Obviousness:

1. Exchange IM messages and send connectivity indication: IM servers inherently perform these functions. US'725 implies a server component managing communication and "presence awareness" for collaborative sessions.
2. Receive a request to establish voice communication from the first party: If the client-side (as per Claims 1, 6, 11) provides an option to initiate voice communication, the corresponding server must be capable of receiving and processing such a request. This is a logical and obvious counterpart to the client functionality.
3. "Request lacking specific identification of the at least one other party": If the client-side initiates the call for "current IM session participants" without requiring individual selection, the request sent to the server would naturally refer to the session rather than enumerating individual participants. This is an obvious consequence of the simplified client interface.
4. Determine the at least one other party from information associated with the IM session: An IM server, by its very nature, maintains records of active IM sessions and their participants. Therefore, if a request to initiate voice communication refers to the "current IM session," it is a trivial and obvious function for the server to retrieve the list of participants associated with that specific session from its existing session management data.
5. "Without requiring registration with a conference call server by potential members": As discussed for client-side claims, this leverages the known host-initiated call model where the server manages outbound dialing.
6. Establish voice communication: After determining the participants, the server would then utilize a conference bridge (either its own integrated component or a third-party service) to initiate outbound calls to the identified participants, thereby forming the conference call. This process of host-initiated calling and connecting through a conference bridge was well-known in the prior art.

Conclusion:
The combination of U.S. Patent Publication No. 20030018725 and the widely understood functionalities of instant messaging systems and host-initiated conference call services available at the priority date of December 22, 2003, would have rendered the subject matter of claims 1, 6, 11, and 16 of US8571194 obvious to a person having ordinary skill in the art. The motivation stems from the clear industry need, articulated even within the patent's own background, to simplify and integrate voice communication into existing real-time collaborative environments to achieve greater spontaneity and reduce user effort. The claimed features represent predictable adaptations and combinations of known elements performing their established functions in a manner readily apparent to a PHOSITA.