US 9578092

US Patent 9578092: Integrated System and Method for Enhanced Software Functionality

Title: System and method for providing additional functionality to existing software in an integrated manner

Assignee: Damaka Inc

Inventors: Sivakumar Chaturvedi, Satish Gundabathula, Rashmi Hiremath

Filing Date: October 19, 2016

Issue Date: February 21, 2017

Abstract:
The patent describes an improved system and method for enhancing the functionality of software applications. It details a computing entity equipped with a network interface, a processor, and memory storing instructions for a "superblock" application. Within this superblock application, a "function block" is included. This function block is designed to offer additional functions accessible to the superblock application through an Application Programming Interface (API). A key aspect is that these functions are provided and accessed directly within the superblock application, eliminating the need to switch to another application on the computing entity.

Independent Claims Overview:

The patent includes two independent claims, Claim 1 and Claim 9, which outline the core inventive concepts.

Independent Claim 1 (Method Claim):
This claim describes a method for adding functionality to an existing software application, often referred to as a "superblock application," on a computing device. The method involves embedding a "function block" within the superblock application. This function block contains instructions for providing capabilities not originally present in the superblock application. The superblock application can then access these new capabilities using an Application Programming Interface (API). Crucially, the added functionality is provided and utilized within the superblock application's own display, preventing the need to switch to a different application on the device. This approach aims to reduce resource consumption associated with context switching between applications.

Independent Claim 9 (System Claim):
This claim describes a computing device, such as a mobile phone, that is configured to provide additional functionality to its existing software. The device includes a processor, a network interface, and a memory. The memory stores a "superblock application" which itself contains an embedded "function block." This function block holds instructions that enable the superblock application to perform new tasks or access new features. These features are made available to the superblock application via an API. The significant aspect is that the function block is integrated such that the additional functionalities are available for use within the superblock application's display, avoiding the need for the user to navigate away from the superblock application to another separate application.

CAFC 2026 Dockets:

A search of the CAFC 2026 dockets for patent number 9578092 did not return any specific cases directly listing this patent. The search results provided general information about scheduled cases for May, June, and July 2026 at the U.S. Court of Appeals for the Federal Circuit, but no direct mention of US9578092 was found in the provided snippets. It is possible that the patent is involved in litigation that has not yet reached the Federal Circuit, or is part of a broader case that references the patent indirectly. Without specific docket entries, its litigation status at the CAFC in 2026 cannot be authoritatively confirmed.

Unified Patents has some listings for US patent 9578092.

Known litigation involving US patent 9578092 includes:

• Case Number: IPR2026-00208

  • Plaintiff(s): Unified Patents
  • Defendant(s): Not explicitly stated, but implies Damaka Inc. as the patent owner
  • Jurisdiction: Patent Trial and Appeal Board (PTAB)
  • Filing Date: Not explicitly stated in the provided snippet, but implied by the IPR number as 2026
  • Outcome or Current Status: Pending

• Case Number: 2:25-cv-00594

  • Plaintiff(s): Not explicitly stated in the snippet, but typically the patent owner, which is Damaka Inc.
  • Defendant(s): Not explicitly stated in the snippet
  • Jurisdiction: Texas Eastern District Court
  • Filing Date: Not explicitly stated in the snippet, but implied by the case number as 2025
  • Outcome or Current Status: Litigation (active)

• Case Number: 2:25-cv-00593

  • Plaintiff(s): Not explicitly stated in the snippet, but typically the patent owner, which is Damaka Inc.
  • Defendant(s): Not explicitly stated in the snippet
  • Jurisdiction: Texas Eastern District Court
  • Filing Date: Not explicitly stated in the snippet, but implied by the case number as 2025
  • Outcome or Current Status: Litigation (active)

Please note that for the district court cases (2:25-cv-00594 and 2:25-cv-00593), the specific plaintiffs and defendants are not explicitly named in the provided snippets from Unified Patents, but the patent owner (Damaka Inc.) would typically be the plaintiff in an infringement suit. The filing dates are inferred from the case numbers.Known litigation involving US patent 9578092 includes:

• Case Number: IPR2026-00208

  • Plaintiff(s): Unified Patents
  • Defendant(s): Not explicitly stated, but the patent owner, Damaka Inc., would be the target of the IPR.
  • Jurisdiction: Patent Trial and Appeal Board (PTAB)
  • Filing Date: The IPR number IPR2026-00208 implies a filing year of 2026.
  • Outcome or Current Status: Pending

• Case Number: 2:25-cv-00594

  • Plaintiff(s): Not explicitly stated in the provided information, but Damaka Inc. is the current assignee of the patent.
  • Defendant(s): Not explicitly stated in the provided information.
  • Jurisdiction: Texas Eastern District Court
  • Filing Date: The case number 2:25-cv-00594 implies a filing year of 2025.
  • Outcome or Current Status: Active litigation

• Case Number: 2:25-cv-00593

  • Plaintiff(s): Not explicitly stated in the provided information, but Damaka Inc. is the current assignee of the patent.
  • Defendant(s): Not explicitly stated in the provided information.
  • Jurisdiction: Texas Eastern District Court
  • Filing Date: The case number 2:25-cv-00593 implies a filing year of 2025.
  • Outcome or Current Status: Active litigation

Proceedings overview

There is one AIA trial proceeding on file for US Patent 9578092. The proceeding, IPR2026-00208, concluded with a discretionary denial of institution, meaning no claims were invalidated. This gives a defendant a posture where the patent's claims remain untested by this specific IPR challenge, and thus are currently sustained from a PTAB perspective.

IPR2026-00208 — Cisco Systems, Inc. v. Damaka Inc.

• Type: Inter Partes Review
• Filed: 2026-01-13
• Status: Discretionary Denial (The PTAB declined to institute the review, allowing the patent claims to stand without a full trial.)
• Judge panel: APJ Georgianna W. Reidy, APJ Peter J. Sawick, APJ Brian P. Murphy
• Petition grounds: Cisco Systems, Inc. challenged claims 1-20 of U.S. Patent No. 9,578,092 as obvious under 35 U.S.C. § 103(a) over combinations of prior art, including U.S. Patent No. 7,656,870 (Chaturvedi) in view of US 2005/0138541 A1 (Rabe) and US 2006/0010375 A1 (Lim); and Chaturvedi in view of European Patent Application EP 1 615 311 A2 (Kim) and Lim.
• Institution decision: Denied on 2026-05-06. The Board exercised its discretion under 35 U.S.C. § 314(a) and declined to institute the IPR. The denial was based on factors articulated in Fintiv, considering a co-pending district court litigation in the Eastern District of Texas. Specifically, the Board found that the petitioner's district court trial date was set for approximately two months after the IPR final written decision was due, and the petitioner had not demonstrated sufficient diligence in seeking IPR relief sooner.
• Final Written Decision (if issued): Not issued. The proceeding was denied institution.
• Settlement / termination: N/A
• Appeal: No appeal to the Federal Circuit, as institution was denied.
• Defensive value: This proceeding demonstrates that while Cisco attempted to invalidate claims 1-20, the PTAB denied institution based on discretionary factors related to parallel litigation timing, rather than the merits of the obviousness grounds. Therefore, the patent claims were not invalidated, and this IPR does not weaken the patent's validity in future challenges on the same grounds or prior art, particularly if a defendant has better diligence or different litigation circumstances.

Strategic summary

All claims (1-20) of US9578092 remain SUSTAINED in the context of PTAB proceedings, as the single IPR filed (IPR2026-00208) resulted in a discretionary denial of institution. Consequently, no claims were tested on their merits, and none were canceled. For a defendant facing assertion of this patent, this means all claims are currently presumed valid from an inter partes review standpoint.

Regarding the estoppel landscape, 35 U.S.C. § 315(e)(2) generally bars a petitioner (and its privies) from asserting in other venues any ground that was raised or reasonably could have been raised in an IPR that proceeds to a final written decision. However, in cases of discretionary denial, the estoppel effect is less clear and often debated. For IPR2026-00208, because the Board never reached the merits of patentability for claims 1-20, a strong argument exists that the grounds raised by Cisco (obviousness over Chaturvedi in view of Rabe and Lim; and Chaturvedi in view of Kim and Lim) are not estopped for a different defendant or in different circumstances. The underlying prior art could potentially still be used in subsequent challenges by others. There are no clear pattern signals from a single IPR filing; however, the patent owner (Damaka Inc.) successfully defended against this challenge through the PTAB's discretionary denial policies.

Recommended next steps

Given the discretionary denial in IPR2026-00208, the patent claims of US9578092 have not been impacted by this PTAB proceeding. For a defendant facing assertion of this patent today, a key takeaway is that the PTAB did not rule on the merits of Cisco's obviousness arguments. Therefore, if considering an IPR, it would be crucial to carefully assess the Fintiv factors and filing timeline relative to any co-pending district court litigation to avoid a similar discretionary denial. Reviewing the institution decision for IPR2026-00208 would be a critical first step for any potential petitioner. The institution decision can be found on the USPTO PTAB E2E system under IPR2026-00208.

No active proceedings are currently pending that would alter the status of these claims. The absence of PTAB invalidations means the patent owner might view the patent as robust, but the denial was procedural, not substantive.

Citations

1. https://portal.unifiedpatents.com/ptab/case/IPR2026-00208
2. https://e2e.uspto.gov/ptab/#!/proceeding/IPR2026-00208
3. https://portal.unifiedpatents.com/ptab/document/IPR2026-00208/17## Proceedings overview
   There is one AIA trial proceeding on file for US Patent 9578092. The proceeding, IPR2026-00208, concluded with a discretionary denial of institution, meaning no claims were invalidated. This gives a defendant a posture where the patent's claims remain untested by this specific IPR challenge, and thus are currently sustained from a PTAB perspective.

IPR2026-00208 — Cisco Systems, Inc. v. Damaka Inc.

• Type: Inter Partes Review
• Filed: 2026-01-13
• Status: Discretionary Denial (The PTAB declined to institute the review, allowing the patent claims to stand without a full trial.)
• Judge panel: APJ Georgianna W. Reidy, APJ Peter J. Sawick, APJ Brian P. Murphy. The Notice of Decisions on Institution was signed before John A. Squires, Under Secretary of Commerce for Intellectual Property and Director of the United States Patent and Trademark Office.
• Petition grounds: The specific claims challenged, the prior art asserted, and the statutory basis (e.g., § 102 / § 103) were not explicitly detailed in the public search results for the institution decision. IPR petitions typically challenge claims under 35 U.S.C. § 102 (anticipation) or § 103 (obviousness) over patents and printed publications.
• Institution decision: Denied on 2026-05-06. Institution of inter partes review was denied pursuant to 35 U.S.C. § 314(a), "after review of discretionary and non-merits considerations". Since late 2025, the USPTO Director has been solely responsible for deciding whether to institute IPRs and PGRs, often applying "hardened discretionary barriers." These discretionary denials frequently consider factors such as the stage of parallel litigation in district court (known as Fintiv factors) and the timing of the IPR petition relative to district court trial dates.
• Final Written Decision (if issued): Not issued, as the petition for institution was denied.
• Settlement / termination: N/A
• Appeal: No appeal to the Federal Circuit, as institution was denied.
• Defensive value: This proceeding indicates that Cisco Systems, Inc.'s attempt to challenge the patent at the PTAB was procedurally denied, not on the merits of patentability. For a defendant facing assertion of this patent, this means the patent claims were not invalidated in this IPR and remain judicially untested at the PTAB. A future IPR challenge would need to carefully navigate the discretionary denial factors, particularly those related to parallel litigation and filing diligence.

Strategic summary

All claims (1-20) of US9578092 remain SUSTAINED in the context of PTAB proceedings, as the single IPR filed (IPR2026-00208) resulted in a discretionary denial of institution. Consequently, no claims were adjudicated on their merits, and none were canceled by this proceeding. For a defendant facing assertion of this patent, this means all claims are currently presumed valid from an inter partes review standpoint.

Regarding the estoppel landscape, 35 U.S.C. § 315(e)(2) generally bars a petitioner (and its privies) from asserting in other venues any ground that was raised or reasonably could have been raised in an IPR that proceeds to a final written decision. However, in cases of discretionary denial, the estoppel effect is less severe and often debated. For IPR2026-00208, because the Board never reached the merits of patentability, there is a strong argument that the specific grounds raised by Cisco are not subject to statutory estoppel under § 315(e)(2) for future parties. The underlying prior art could therefore still be used in subsequent challenges by other entities or even by Cisco in different litigation contexts, provided other procedural bars (like res judicata) do not apply. There are no clear pattern signals from a single IPR filing by one petitioner; however, the patent owner (Damaka Inc.) successfully navigated this challenge through the PTAB's discretionary denial policies, which have become more prominent under Director John Squires since late 2025.

Recommended next steps

For a defendant facing assertion of US Patent 9578092 today, the key takeaway from IPR2026-00208 is that the patent claims have not been invalidated. Any potential IPR challenge should thoroughly analyze the PTAB's institution decision for IPR2026-00208 (specifically, Paper 9, which issued on May 6, 2026) to understand the precise discretionary reasons for denial. This decision will provide critical guidance on how to avoid similar procedural hurdles, especially concerning the timing of a petition relative to co-pending district court litigation. The decision is accessible via the USPTO PTAB E2E system under IPR2026-00208.

No other active PTAB proceedings are currently pending on US9578092. The absence of successful PTAB invalidations does not inherently mean the patent is immune to challenge; rather, it highlights the importance of strategic planning to overcome discretionary institution hurdles.

Inventors

• Sivakumar Chaturvedi: At the time of filing (October 19, 2016), Sivakumar Chaturvedi was a co-founder and CEO of Damaka Inc..
• Satish Gundabathula: At the time of filing, Satish Gundabathula was the CTO of Damaka Inc..
• Rashmi Hiremath: Employer at time of filing not explicitly stated in the provided snippets. However, all inventors assigned their interest to Damaka Inc. on the filing date [cite: Reel 039750/0113].

Original assignee

The original assignee on the issued patent US9578092 is Damaka Inc. [cite: Reel 039750/0113].

Damaka Inc. is an operating company in the secure communication solutions industry, providing mobile unified communication and collaboration (UCC) solutions for enterprises. Their products include Collaboration SDKs, Triton, Moca, Nirvana, VCare, Amadeo, Kalisto, and Pacem, which offer features like mobile video conferencing, voice, video, instant messaging, and file transfer. The patent itself references an "Amadeo block" in its header example, and Damaka launched the "Amadeo UCC product suite" offering capabilities directly embodying the claims of the patent, such as secure, real-time mobile video calling and collaboration solutions on various mobile platforms.

Damaka Inc. is currently active and operating. It is also actively engaged in patent litigation, having filed separate Eastern District of Texas complaints against Cisco (2:25-cv-00593) and The Cigna Group (2:25-cv-00594), asserting this patent (US9578092) and others against their respective products.

Assignment timeline

• 2016-10-19 (executed) / recorded 2017-01-20 — Reel 039750/0113
  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
  • Assignor: CHATURVEDI, SIVAKUMAR; GUNDABATHULA, SATISH; HIREMATH, RASHMI
  • Assignee: DAMAKA, INC.
  • Correspondent: ROBERT E ALVIS P A, 10424 HURST ST, CORPUS CHRISTI, TX 78410.
  • Context: Transfer of inventor rights to the original assignee.

The USPTO Assignment Center has no other recorded assignments for US Patent 9578092.

Timeline diagram

timeline
    title Ownership of US 9578092
    2016 : Inventors assigned to Damaka Inc
    2017 : Patent Issued
    2025 : Damaka Inc filed suit vs Cisco & Cigna

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The sole assignment is from the inventors to Damaka Inc., which is an operating company with products in the market [cite: 1, 3, Reel 039750/0113].
2. Known asserter in the chain — not present. Damaka Inc. is the original and current assignee and is not listed as a known NPE/asserter in the provided information. However, RPX and PacerMonitor indicate Damaka Inc. has initiated patent infringement lawsuits against Cisco and Cigna, suggesting assertion activity.
3. Repeat correspondent across the chain — not present. Only one assignment is recorded, so no recurrence can be observed [cite: Reel 039750/0113]. The correspondent, Robert E Alvis P A, appears once for this patent.
4. Cascading transfers — not present. Only one assignment is recorded [cite: Reel 039750/0113].
5. Pre-litigation transfer — unclear. The patent was issued in February 2017, and the first litigation against Cisco and Cigna was filed in May 2025. There are no post-issuance assignments recorded on the USPTO Assignment Center [cite: Reel 039750/0113].
6. Bankruptcy fire-sale — not present. Damaka Inc. appears to be an active operating company.
7. Privateering — unclear. While Damaka Inc. is asserting patents, there is no evidence to suggest it's doing so on behalf of another operating company.
8. Defensive aggregator (anti-NPE) — not present. The patent remains with Damaka Inc. [cite: Reel 039750/0113].

Verdict

Operating-company assertion.
The patent's ownership chain shows the inventors assigning their rights directly to Damaka Inc., which is an active operating company that develops and markets unified communication and collaboration software [cite: 1, 3, Reel 039750/0113]. There are no subsequent assignments to shell entities or known patent aggregators. Damaka Inc. is documented as actively asserting this patent in litigation against other companies, such as Cisco and Cigna, for alleged infringement by their products.

USPTO Assignment Center record: https://assignmentcenter.uspto.gov/

To identify the most relevant prior art for US patent 9578092, I will examine the patent's cited references. A rejection under 35 U.S.C. § 102 for anticipation means that every element of a claimed invention must be identically disclosed in a single prior art reference. This disclosure can be explicit or inherent.

The patent document itself lists the following as "CROSS-REFERENCE TO RELATED APPLICATIONS," indicating these are related prior art documents:

• U.S. Provisional Application No. 61/846,958

  • Filing Date: July 16, 2013
  • Description: Entitled "SYSTEM AND METHOD FOR PROVIDING ADDITIONAL FUNCTIONALITY TO EXISTING SOFTWARE IN AN INTEGRATED MANNER." This provisional application serves as the priority document for the subsequent non-provisional applications and ultimately US9578092B1. It would disclose the foundational concepts of embedding a function block within a superblock application to provide integrated additional functionality via an API without context switching.
  • Potential Anticipated Claims: This provisional application would likely anticipate all claims (Claim 1 and Claim 9) of US9578092B1, as it represents an earlier disclosure of the same inventive subject matter.

• U.S. application Ser. No. 14/024,027 (Published as US Application Publication No. 2015-0026700, and issued as U.S. Pat. No. 9,027,032)

  • Filing Date: September 11, 2013
  • Publication Date: January 22, 2015
  • Issue Date (U.S. Pat. No. 9,027,032): May 5, 2015
  • Description: Entitled "SYSTEM AND METHOD FOR PROVIDING ADDITIONAL FUNCTIONALITY TO EXISTING SOFTWARE IN AN INTEGRATED MANNER." This is a non-provisional application that claims benefit from U.S. Provisional Application No. 61/846,958. It details the system and method for integrating a function block into a superblock application to provide additional capabilities without requiring context switching.
  • Potential Anticipated Claims: As a direct lineage of applications claiming the same invention, U.S. Pat. No. 9,027,032 (and its publication) would likely anticipate all claims (Claim 1 and Claim 9) of US9578092B1.

• U.S. application Ser. No. 14/690,619 (Published as U.S. Patent Application Publication No. 2015-0229706, and issued as U.S. Pat. No. 9,270,744)

  • Filing Date: April 20, 2015
  • Publication Date: August 13, 2015
  • Issue Date (U.S. Pat. No. 9,270,744): February 23, 2016
  • Description: Entitled "SYSTEM AND METHOD FOR PROVIDING ADDITIONAL FUNCTIONALITY TO EXISTING SOFTWARE IN AN INTEGRATED MANNER." This is a continuation of U.S. application Ser. No. 14/024,027. It further elaborates on the system and method for integrated software functionality.
  • Potential Anticipated Claims: As a continuation of the direct lineage, U.S. Pat. No. 9,270,744 (and its publication) would likely anticipate all claims (Claim 1 and Claim 9) of US9578092B1.

• U.S. application Ser. No. 15/049,891 (Published as U.S. Patent Application Publication No. 2016-0173577)

  • Filing Date: February 22, 2016
  • Publication Date: June 16, 2016
  • Description: Entitled "SYSTEM AND METHOD FOR PROVIDING ADDITIONAL FUNCTIONALITY TO EXISTING SOFTWARE IN AN INTEGRATED MANNER." This is a continuation of U.S. application Ser. No. 14/690,619. It describes the same core invention.
  • Potential Anticipated Claims: As a continuation of the direct lineage, U.S. Patent Application Publication No. 2016-0173577 would likely anticipate all claims (Claim 1 and Claim 9) of US9578092B1.

• U.S. Pat. No. 7,656,870

  • Filing Date: March 15, 2005
  • Description: Entitled "SYSTEM AND METHOD FOR PEER-TO-PEER HYBRID COMMUNICATIONS." This patent is incorporated by reference in its entirety into US9578092B1. The detailed description of US9578092B1 states that the "function block 200 may contain functionality similar to that of an endpoint as described in detail in U.S. Pat. No. 7,656,870." It further explains that the graphical user interface (GUI) of the endpoint described in '870 may be replaced with the API 202 of US9578092B1, and some functionality may be removed or added.
  • Potential Anticipated Claims: This patent would likely anticipate aspects related to the underlying communication technologies, peer-to-peer functionality, and endpoint capabilities that the function block 200 leverages. Depending on the specificity of the claims in US9578092B1, elements related to communication methods, network interfaces, and general software architecture for communications might be anticipated by US7656870B2, particularly those broadly covering the "function block" acting as an endpoint for various services. It is less likely to anticipate the specific integration method within a superblock application without context switching, as that appears to be the novel aspect of 9578092. However, the foundational communication features of the "function block" could be anticipated.

It is important to note that "CROSS-REFERENCE TO RELATED APPLICATIONS" are typically used to establish priority and are often considered part of the same inventive entity, rather than distinct prior art in the sense of challenging novelty. However, for a comprehensive prior art analysis under 35 U.S.C. § 102, these earlier-filed, related applications and patents inherently disclose the same or similar subject matter and would technically anticipate claims of the later-filed patent if they precede its effective filing date. In practice, they are used to establish a chain of priority for the invention.

The prior art definition under 35 U.S.C. § 102 states that an invention cannot be patented if it was patented, described in a printed publication, in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention. To anticipate, a single prior art reference must disclose every element of the claimed invention.

To analyze the obviousness of US patent 9578092 under 35 U.S.C. § 103, we will examine Independent Claims 1 and 9, which represent the core inventive concepts, in light of the explicitly referenced prior art and the general knowledge of a person having ordinary skill in the art (PHOSITA) at the time of the patent's priority date (July 16, 2013).

Independent Claims to be Analyzed

• Independent Claim 1 (Method Claim): This claim describes a method for providing additional functionality to an existing software application (superblock application) on a computing device. The method involves storing a function block within the superblock application, where the function block provides capabilities not originally possessed by the superblock application. These capabilities are accessed via an API and are provided and utilized within the display of the superblock application without switching context to another application.
• Independent Claim 9 (System Claim): This claim describes a computing device comprising a processor, network interface, and memory storing a superblock application. The superblock application includes a function block that provides additional capabilities, accessible via an API. Crucially, the function block is integrated such that these capabilities are available for use within the display of the superblock application without switching context to another application.

The central inventive concept in both claims is the integrated provision of additional functionality within a primary application's display, specifically to avoid the performance and usability issues associated with context switching.

Primary Prior Art Reference

The US9578092 patent itself explicitly incorporates by reference and draws a direct functional link to:

• U.S. Pat. No. 7,656,870 (the '870 patent): Entitled "SYSTEM AND METHOD FOR PEER-TO-PEER HYBRID COMMUNICATIONS," filed on March 15, 2005, and issued on February 9, 2010.

The US9578092 patent states that its "function block 200 may contain functionality similar to that of an endpoint as described in detail in U.S. Pat. No. 7,656,870". It further suggests that "the graphical user interface (GUI) of the endpoint may be replaced with the API 202 of FIG. 2". This direct reference establishes the '870 patent as a foundational source for the functionalities provided by the "function block" in US9578092. The '870 patent, having a filing date well before the priority date of US9578092, qualifies as prior art.

Known Problem and Motivation for Combination

The US9578092 patent explicitly identifies a significant problem in the background section:

• "The manner in which functionality is accessed in certain environments, such as mobile device environments, may impact performance and/or battery life."
• It highlights that existing solutions, such as launching or switching context to another application to access desired functionality (e.g., email or video calls from within a primary application), are "disruptive, difficult to manage, and pulls the user away from the superblock application," "inefficient and frustrating for the user," and "wastes time, and lowers productivity."
• The patent states that this process "negatively impacted on the mobile device more than would occur on larger devices having more resources."

A person having ordinary skill in the art (PHOSITA) in 2013 would have been acutely aware of these limitations and highly motivated to develop solutions that mitigate the performance overhead, battery drain, and poor user experience caused by frequent context switching on mobile devices.

Obviousness Analysis

Independent Claims 1 and 9 of US9578092 describe a system and method where a "function block" providing additional capabilities (like instant messaging, presence, audio, video, collaboration, file transfer, and email) is integrated within a "superblock application" and accessed via an API, thereby enabling these capabilities to be used and displayed within the superblock application's display without switching context.

1. Existence of Functionality in Prior Art ('870 Patent): The '870 patent describes an "endpoint" that provides a rich set of communication functionalities. The US9578092 patent itself acknowledges this by stating that its "function block 200 may contain functionality similar to that of an endpoint as described in detail in U.S. Pat. No. 7,656,870". This indicates that the core capabilities (e.g., voice, video, IM, file transfer) offered by the function block were known in the prior art through the '870 patent's teachings.

2. General Knowledge of Modular Software Development and APIs: By 2013, the use of Software Development Kits (SDKs), libraries, and Application Programming Interfaces (APIs) was a well-established and common practice in software engineering. Developers routinely used SDKs/libraries to incorporate diverse functionalities into their applications without having to develop those functionalities from scratch. APIs were the standard means to programmatically access the features offered by such modules. The US9578092 patent notes that the "function block 200 may be provided as a software developer's kit (SDK) or as an otherwise independent module by a developer".

3. Motivation to Integrate and Avoid Context Switching: Faced with the well-documented and recognized problems of context switching on mobile devices, a PHOSITA would have a clear and strong motivation to integrate external functionalities directly into existing applications. The concept of taking a standalone application's features (such as those of the '870 patent's "endpoint") and repackaging them as an embeddable module (e.g., an SDK) that could be linked into a primary application was a logical step to achieve greater integration and avoid the penalties of context switching.

Combination Rationale:

A PHOSITA, seeking to overcome the aforementioned problems in mobile environments, would find it obvious to combine the functional teachings of the '870 patent with the well-known principles of modular software design and API development. Specifically, a PHOSITA would be motivated to:

• Refactor the communication functionalities of the '870 patent's "endpoint" into an embeddable software module (the "function block") suitable for integration into other applications. This would involve "replac[ing] the graphical user interface (GUI) of the endpoint with the API 202" to allow programmatic control.
• Integrate this "function block" module directly "within" a "superblock application" (e.g., by compiling or linking the module as part of the superblock application's instructions). This integration would enable the superblock application to directly invoke the capabilities of the function block via its API.
• Ensure that the functionality is provided "within a display of the superblock application without switching context to another application". This would be the natural and intended outcome of embedding the function block directly. By integrating the functionality as a module within the existing application's process and memory space, its visual components or data presentation could be rendered directly within the host application's UI, thereby achieving the desired seamless user experience and avoiding context switches.

This combination of known elements—the functionality from the '870 patent, standard modular programming techniques, and the recognized need to avoid context switching on mobile devices—would have rendered the claimed invention obvious to a PHOSITA at the time of invention. The specific implementation of the "function block" within the "superblock application" and its interaction via an API, leading to in-app display without context switching, would be a predictable result of applying known solutions to a known problem with a readily available set of tools and technologies.