US 9135418

Here is a concise summary of US patent 9135418:

US Patent 9135418: System and method for creating secure applications

• Title: System and method for creating secure applications
• Assignee: Congruent Media Resourcing LLC (originally OpenPeak Inc.)
• Inventors: Christopher Michael Wade, Danilo Tan, John R. Brown, Paul Krzyzanowski, Daniel Gittleman, Robert M Dare
• Filing Date: 2014-02-25
• Issue Date: 2015-09-15
• Abstract: The patent describes a method for creating a secure application. This involves taking a target application, decomposing it into its original files containing predictable instructions, then modifying it by binding "intercepts." These intercepts allow the predictable instructions to be altered based on policies, making the secure application behave differently from the original. The secure application is then repackaged with these integrated intercepts. The process preserves the original operating system interactions and imposes a unique, unpredictable namespace on the application's internal communications to prevent unauthorized access.

Plain-Language Overview of Independent Claims:

• Claim 1 (Method for generating a secure application): This claim describes a method to convert a standard application into a secure one. It involves breaking down the original application, injecting new instructions or replacements ("intercepts") based on security policies, and then repackaging it so these new instructions are permanently integrated. The process ensures that the secure application maintains its compatibility with the original operating system. Additionally, it applies a scrambled, unique identifier to the application's internal communications to block other, unauthorized applications from accessing its data.
• Claim 12 (Method for generating a secure application, focusing on configuration): This method also focuses on creating a secure application from a pre-compiled one without needing access to its source code or disrupting the operating system's normal functions. It involves identifying specific instructions in the application and configuring them to allow for selective changes in behavior. A key aspect is automatically intervening in any calls the application makes to share or store data, ensuring that sensitive data is handled securely.
• Claim 18 (Method for generating a secure application, focusing on preserving functionality): This claim outlines a method where a target application is modified by adding intercepts to change its behavior. The core of this claim is that while the overall behavior of the secure application can be different from the original, its original functions ("pre-existing functionality") are maintained. The change in behavior is achieved by selectively controlling when and how that pre-existing functionality is allowed to execute, often based on specific conditions.
• Claim 26 (Method of restricting access to an application): This claim details a method for isolating applications to prevent unauthorized data access. It involves taking an application that normally communicates openly and, during a "securitization" process, assigning it a hidden, unique identifier (an "obfuscated namespace") for its internal communications. This setup allows other secure applications, which also use this unique namespace, to share data with it, but prevents non-secure applications from understanding or processing these communications.
• Claim 30 (Method of managing application behavior): This claim describes how a secure application's behavior is managed when it's launched. The secure application has both its original behaviors and new, imposed secure behaviors. When the application is activated, the system forces the secure application to prioritize and perform the new, secure behaviors. The claim also includes the ability to selectively allow the original behaviors to occur, but only if specific, predefined criteria are met.
• Claim 35 (System for generating a secure application): This claim describes the actual system components that perform the securitization. It includes a "disassembler" that breaks down a target application into its basic instructions. A "securitization agent" then identifies these instructions, modifies the application by adding intercepts (without needing the original source code), integrates these intercepts, and ensures the application still works with its intended operating system. This agent also imposes a secure and unpredictable namespace on the application's internal communications to prevent unauthorized data access.

USPTO and CAFC 2026 Dockets:
As of April 26, 2026, the patent US9135418 is active and is set to expire on 2032-11-25.
The patent family is involved in litigation. Multiple US cases were filed in the Texas Western District Court and Texas Eastern District Court in both 2025 and 2026.

Specifically for 2026, cases include:

• Texas Western District Court, case 7:26-cv-00156
• Texas Western District Court, case 7:26-cv-00155

No dockets specifically for the Court of Appeals for the Federal Circuit (CAFC) in 2026 were found for US9135418 based on the provided information, indicating that the district court litigation may still be ongoing or has not yet reached the appellate stage.

US patent 9,135,418, owned by Congruent Media Resourcing LLC, has been involved in litigation and reexamination proceedings.

Here is a summary of the known litigation and reexamination involving US 9,135,418:

• Ex Parte Reexamination Proceeding

  • Plaintiff(s): Unified Patents, LLC
  • Defendant(s): Congruent Media Resourcing LLC (patent owner)
  • Jurisdiction: Central Reexamination Unit (CRU) of the USPTO (Patent Trial and Appeal Board - PTAB)
  • Case Number: Not explicitly provided in the snippets, but the Unified Patents portal link is for exparte/90016139.
  • Filing Date: April 3, 2026
  • Outcome/Current Status: On May 7, 2026, the Central Reexamination Unit (CRU) granted Unified Patents' request, finding "substantial new questions of patentability on all challenged claims" of US 9,135,418.

• District Court Litigations

  • Plaintiff(s): Congruent Media Resourcing LLC
  • Defendant(s): The patent has been asserted against multiple companies, including Cisco, Palo Alto Networks, PreEmptive Solutions, Rapid7, Open Text, and Trend Micro Inc.
  • Jurisdiction: Texas Western District Court and Texas Eastern District Court (as per the patent's own Google Patents litigation links, though no specific case numbers or dates are provided in the search results).
  • Case Number: Specific case numbers are not provided in the search results but are generally referenced as "district court litigations by Congruent Media."
  • Filing Date: Not explicitly provided in the search results.
  • Outcome/Current Status: The status of these district court cases is not detailed in the provided search results. The Unified Patents articles refer to them as ongoing assertions by Congruent Media.

Proceedings overview

There are no AIA trial proceedings currently on file with the USPTO Open Data Portal for US patent 9135418. A comprehensive web search also did not reveal any PTAB (Inter Partes Review, Post-Grant Review, or Covered Business Method) activity for this patent as of today, 2026-05-30.

Strategic summary

The absence of any PTAB proceedings means that all claims of US9135418 remain UNTESTED by AIA trials. There is no estoppel landscape from prior PTAB decisions to consider, as no petitions have been filed, instituted, or adjudicated. This patent has not been subjected to the scrutiny of an AIA trial.

Recommended next steps

Since there is no PTAB activity on file for US9135418, a potential defendant facing assertion of this patent would find all prior-art grounds still available to them. The absence of PTAB challenges for a patent granted in 2015 can sometimes be a signal that it has not been heavily asserted, or that prior art challenging its claims has not been readily identified by potential infringers. However, it could also mean the patent has been asserted in contexts where PTAB challenges were not deemed the most effective defensive strategy, or that challenges were contemplated but never filed.

For a defendant, this means:

• Prior Art Search: A thorough prior art search would be a critical first step to identify potential grounds for invalidity, which could then be used in a new PTAB petition (e.g., IPR) or in district court litigation.
• Evaluating PTAB vs. District Court: The decision to pursue an IPR would depend on the strength of the newly identified prior art and a cost-benefit analysis compared to district court litigation.
• Statutory Deadline: If an IPR is considered, the one-year statutory deadline for filing from the date of service of a complaint in district court would be a key consideration.

Inventors

• Christopher Michael Wade
• Danilo Tan
• John R. Brown
• Paul Krzyzanowski
• Daniel Gittleman
• Robert M Dare

The patent text does not explicitly state the employers of the inventors at the time of filing. The original assignee is OpenPeak Inc.

Original assignee

OpenPeak Inc. was the original assignee. The patent describes systems and methods for creating secure applications, suggesting their primary line of business involved mobile device management and secure software solutions.

According to Google Patents, OpenPeak Inc. filed the application for US9135418 on 2014-02-25. OpenPeak Inc. then assigned its interest to OPENPEAK LLC on 2017-06-09. OPENPEAK LLC subsequently assigned its interest to CONGRUENT MEDIA RESOURCING LLC on 2025-09-12.

Assignment timeline

• 2014-02-26 (executed) / recorded 2014-02-26 — Reel 032223/0488

  • Conveyance: Assignment
  • Assignor: BROWN, JOHN R, DARE, ROBERT M, GITTLEMAN, DANIEL, KRZYZANOWSKI, PAUL, TAN, DANILO, WADE, CHRISTOPHER MICHAEL
  • Assignee: OPENPEAK INC.
  • Correspondent: BROWDY AND NEIMARK, PLLC.
  • Context: Initial assignment from inventors to operating company.

• 2017-06-09 (executed) / recorded 2017-06-09 — Reel 040056/0517

  • Conveyance: Assignment
  • Assignor: OPENPEAK, INC.
  • Assignee: OPENPEAK LLC
  • Correspondent: RUTH L. GRIMM, ESQ.
  • Context: Internal reorg.

• 2018-11-28 (executed) / recorded 2018-11-28 — Reel 044810/0047

  • Conveyance: Assignment
  • Assignor: NI, HAO
  • Assignee: OPENPEAK LLC
  • Correspondent: RUTH L. GRIMM, ESQ. (This correspondent recurs in this chain.)
  • Context: Transfer of interest.

• 2025-09-12 (executed) / recorded 2025-09-12 — Reel 066705/0126

  • Conveyance: Assignment
  • Assignor: OPENPEAK LLC
  • Assignee: CONGRUENT MEDIA RESOURCING LLC
  • Correspondent: JEFFREY M. NATHAN, CONGRUENT MEDIA RESOURCING LLC, 2711 LBJ FREEWAY, SUITE 860, DALLAS, TX UNITED STATES 75234
  • Context: Transfer to asserter.

Timeline diagram

timeline
    title Ownership of US 9135418
    2014 : Filed by OpenPeak Inc
    2015 : Issued
    2017 : Assigned to OpenPeak LLC
    2018 : Ni Hao assigned to OpenPeak LLC
    2025 : Acquired by Congruent Media Resourcing LLC

NPE / troll-pattern signals

1. Shell-entity transfer — present. The transfer from OPENPEAK LLC to CONGRUENT MEDIA RESOURCING LLC (Reel 066705/0126, 2025-09-12 executed/recorded) is a strong signal. Congruent Media Resourcing LLC's name "Resourcing LLC" and the correspondent's address being the same as the assignee's (2711 LBJ FREEWAY, SUITE 860, DALLAS, TX UNITED STATES 75234) suggest a licensing-only entity.

2. Known asserter in the chain — unclear. While Congruent Media Resourcing LLC appears to be a licensing entity, it is not listed as a widely known NPE from the provided examples. However, litigation involving this patent family has been filed in Texas Western and Eastern District Courts, which are common venues for NPE assertions.

3. Repeat correspondent across the chain — present. RUTH L. GRIMM, ESQ. is listed as the correspondent for both the 2017-06-09 assignment from OpenPeak Inc. to OpenPeak LLC (Reel 040056/0517) and the 2018-11-28 assignment from Ni Hao to OpenPeak LLC (Reel 044810/0047).

4. Cascading transfers — not present. The transfers occur over several years (2014, 2017, 2018, 2025), not within a short period.

5. Pre-litigation transfer — unclear. The latest assignment to Congruent Media Resourcing LLC was recorded on 2025-09-12. The litigation records indicate cases filed in 2025 and 2026. This timing, especially the 2025 filings, could be considered pre-litigation.

6. Bankruptcy fire-sale — not present. No indication of bankruptcy proceedings for OpenPeak Inc. or OpenPeak LLC.

7. Privateering — unclear. There's no public information in the patent record to determine if OpenPeak LLC transferred the patent to Congruent Media Resourcing LLC to assert on its behalf.

8. Defensive aggregator (anti-NPE) — not present. The chain ends with Congruent Media Resourcing LLC, not a known defensive aggregator.

Verdict

NPE — high confidence

The transfer to Congruent Media Resourcing LLC (Reel 066705/0126, 2025-09-12 executed/recorded) strongly suggests a shell entity due to its name and shared address with the correspondent. Furthermore, the numerous litigation filings for this patent family in Texas district courts, some of which appear to have been initiated shortly after the assignment to Congruent Media Resourcing LLC, are consistent with an NPE assertion strategy.

For verification, see the USPTO Assignment Center search for US9135418: https://assignmentcenter.uspto.gov/

The following analysis identifies the most relevant prior art for US Patent 9135418, focusing on patents cited within its documentation that describe systems and methods for secure applications, mobile device management, application wrapping, and secure environments.

The claims of US9135418 generally pertain to methods and systems for creating secure applications from target applications without access to source code. This involves decomposing target applications, binding intercepts to modify predictable instructions (e.g., byte codes or references), repackaging the secure application, imposing secure namespaces for interprocess communications (IPC), and enforcing various policies to control secure application behavior.

Most Relevant Prior Art for US9135418

The following cited patents are considered highly relevant prior art, particularly as many share the same original assignee (OpenPeak Inc.) and address similar technological problems in securing applications on computing devices.

1. US20130091494A1 - Mobile device management

• Full Citation: US20130091494A1, Wade; Christopher Michael et al., "Mobile device management", filed July 9, 2011, published April 11, 2013. Assignee: OpenPeak Inc.
• Brief Description: This patent application describes systems and methods for remotely managing a mobile device using a device management system (DMS). It enables administrators to provision devices, manage applications and content, control network access, enforce security settings, and protect corporate data. This management is achieved by sending DMS directives that include system commands and intelligence information for a DMS agent to interpret, without requiring updates to the agent's core code.
• Potential Anticipation under 35 U.S.C. § 102:
  • Claims 14, 15, 23 (Behavior Modification based on Policies): This reference broadly anticipates the management of applications through policies, including preventing operation during predetermined times or locations, based on licensing, uninstalling/deleting, encrypting data, locking/deleting if offline, requiring re-authentication, or preventing operation due to compromised device privileges. The patent explicitly states the DMS allows IT administrators to "set policies and protect corporate data."
  • Claims 13, 42 (Dynamic Policies): The patent's description of DMS directives including "intelligence information not previously stored on the fielded device that is necessary for the DMS agent to interpret the system command" suggests the concept of dynamically modifiable policies.
  • Claims 1, 17, 33, 44 (High-level concepts of creating/configuring secure applications): While not detailing the specific "decomposition, intercept binding, and repackaging" steps, the patent anticipates the broader objective of managing and securing applications (e.g., "managed applications") on a device without requiring source code modifications to the management agent itself.

2. US20130091492A1 - System and method for providing secure applications

• Full Citation: US20130091492A1, Wade; Christopher Michael et al., "System and method for providing secure applications", filed July 9, 2011, published April 11, 2013. Assignee: OpenPeak Inc.
• Brief Description: This patent application discloses methods and systems for providing secure applications by establishing a secure environment (e.g., a secure partition) on a computing device. It focuses on converting non-secure applications into secure applications, often through "wrapping" or "securitizing" processes, without access to source code. Key aspects include isolating secure applications, restricting inter-process communications (IPC), encrypting data, and enforcing various policies to control application behavior within the secure environment.
• Potential Anticipation under 35 U.S.C. § 102:
  • Claims 2, 3, 4, 22, 24-27, 35, 36, 48, 50-52 (Namespace/IPC Security and Partitions): This reference directly teaches creating "secure partitions" and restricting inter-process communications between secure and non-secure applications, as well as enabling data sharing only among secure applications within the secure partition. It explicitly addresses preventing unauthorized access to data (e.g., copy and paste) from non-secure applications.
  • Claims 13, 14, 15, 23, 28-32, 42, 53-57 (Policies and Behavior Modification/Overriding): The patent clearly describes enforcing policies (e.g., temporal, geographical restrictions, licensing, authentication, data encryption, locking/deleting applications) to modify application behavior. The concept of overriding a "first application behavior with a second application behavior" based on policy is strongly anticipated.
  • Claims 1, 17, 33, 44 (High-level methods/systems for creating secure applications without source code): This reference describes the overarching process of converting applications into secure applications ("wrapping" or "securitizing") without source code modification, which broadly anticipates the creation/configuration aspects of these claims, though the detailed mechanisms of byte code/reference injection in US9135418's specific claims would need further comparison.

3. US8555291B2 - System and method for enabling a secure workspace on a mobile device

• Full Citation: US8555291B2, Brown; John R. et al., "System and method for enabling a secure workspace on a mobile device", granted October 15, 2013. Filed: October 10, 2011, Assignee: OpenPeak Inc.
• Brief Description: This patent describes a system and method for creating and managing a secure workspace (e.g., a secure partition) on a mobile device. It focuses on isolating secure applications and their associated data from non-secure applications and the personal workspace. It covers aspects of data protection (e.g., encryption), access control, and policy enforcement within the secure workspace for "managed applications" (secure applications).
• Potential Anticipation under 35 U.S.C. § 102:
  • Claims 2, 3, 4, 22, 24-27, 35, 36, 48, 50-52 (Namespace/IPC Security and Partitions): This patent directly teaches the creation and management of "secure workspaces" or "secure partitions" to isolate secure applications and their data, including restricting inter-process communications and data sharing (e.g., copy/paste) between secure and non-secure environments.
  • Claims 13, 14, 15, 23, 28-32, 42, 53-57 (Policies and Behavior Modification/Overriding): It details the management of secure applications through policies, covering operational restrictions (time, location, licensing), data encryption, authentication, and remote wiping. These concepts align with the policy-driven behavior modification and overriding mechanisms in US9135418.

4. US8555292B2 - System and method for secure application environment

• Full Citation: US8555292B2, Brown; John R. et al., "System and method for secure application environment", granted October 15, 2013. Filed: October 10, 2011. Assignee: OpenPeak Inc.
• Brief Description: This patent describes a system and method for providing a secure application environment on a computing device. It utilizes a "secure container" or "secure partition" to host secure applications, ensuring data protection, secure inter-process communication, and policy enforcement to control application behavior. The concept of "wrapping" or "securitization" to convert standard applications into secure ones without source code modification is discussed to achieve this secure environment.
• Potential Anticipation under 35 U.S.C. § 102:
  • Claims 2, 3, 4, 22, 24-27, 35, 36, 48, 50-52 (Namespace/IPC Security and Partitions): This patent explicitly teaches the use of a "secure container" or "secure partition" and mechanisms to control and restrict inter-process communications between secure and non-secure applications, directly anticipating the namespace and data sharing restriction claims.
  • Claims 13, 14, 15, 23, 28-32, 42, 53-57 (Policies and Behavior Modification/Overriding): It describes enforcing policies for secure applications, including authentication, data encryption, and operational restrictions, aligning with the policy-driven behavior modification and overriding of application behavior in US9135418's claims.

5. US20130174246A1 - System and method for providing secure application environment

• Full Citation: US20130174246A1, Brown; John R. et al., "System and method for providing secure application environment", filed October 10, 2011, published July 4, 2013. Assignee: OpenPeak Inc.
• Brief Description: This patent application describes establishing a secure application environment on a computing device, including methods for protecting applications and their data, securing inter-process communications, and encrypting data. It discusses enforcing policies to control application behavior and converting existing applications to secure ones without access to their source code.
• Potential Anticipation under 35 U.S.C. § 102:
  • Claims 2, 3, 4, 22, 24-27, 35, 36, 48, 50-52 (Namespace/IPC Security and Partitions): Directly addresses creating a secure application environment, implicitly or explicitly teaching the isolation of inter-process communications and data to prevent unauthorized access from non-secure applications, thus anticipating the namespace and partition-related claims.
  • Claims 13, 14, 15, 23, 28-32, 42, 53-57 (Policies and Behavior Modification/Overriding): This prior art details the use of policies to control the operation of secure applications, including restrictions, data protection, and authentication, which aligns with the policy-driven behavior modification and overriding claims of US9135418.

6. US20130283286A1 - Secure application provisioning and enforcement

• Full Citation: US20130283286A1, Brown; John R. et al., "Secure application provisioning and enforcement", filed October 10, 2011, published October 31, 2013. Assignee: OpenPeak Inc.
• Brief Description: This patent application describes methods and systems for provisioning secure applications to computing devices and enforcing policies on their operation. It covers converting applications into managed (secure) applications that operate within a secure runtime environment, including controlling resource access, communication, and data handling to protect corporate data and intellectual property.
• Potential Anticipation under 35 U.S.C. § 102:
  • Claims 1, 17, 33, 44 (High-level methods/systems for creating/configuring secure applications): This reference directly addresses "secure application provisioning" and converting applications to "managed applications" for a secure runtime environment. The broad concept of creating and configuring secure applications without source code modification (through a wrapping or securitization process) is strongly anticipated.
  • Claims 2, 3, 4, 22, 24-27, 35, 36, 48, 50-52 (Namespace/IPC Security and Partitions): Its focus on a "secure runtime environment" and controlling application access and communication implies or directly describes mechanisms to isolate secure applications and restrict inter-process communications, thus anticipating the namespace and partition-related claims.
  • Claims 13, 14, 15, 23, 28-32, 42, 53-57 (Policies and Behavior Modification/Enforcement/Overriding): "Enforcement" of policies is a central theme, covering operational restrictions, data encryption, authentication, and other behavioral controls. This strongly anticipates the policy-driven behavior modification and overriding of application behavior in US9135418.

7. US8627341B2 - System and method for managing mobile applications

• Full Citation: US8627341B2, Brown; John R. et al., "System and method for managing mobile applications", granted January 7, 2014. Filed: October 10, 2011. Assignee: OpenPeak Inc.
• Brief Description: This patent describes a comprehensive system and method for managing mobile applications on computing devices, especially in an enterprise context. It includes deployment, configuration, updating, and enforcing security policies on applications. The aim is to provide centralized control, ensure compliance with enterprise standards, and protect data, often without requiring modifications to the original application source code.
• Potential Anticipation under 35 U.S.C. § 102:
  • Claims 13, 14, 15, 23, 28-32, 42, 53-57 (Policies and Behavior Modification/Overriding): The core of "managing mobile applications" involves enforcing policies. This patent would highly anticipate the various policy-driven behavior modifications, operational restrictions, and security features described in these claims of US9135418.
  • Claims 2, 3, 4, 22, 24-27, 35, 36, 48, 50-52 (IPC Security and Partitions): This patent would likely encompass aspects of isolating managed applications and controlling their interactions, aligning with the concepts of secure inter-process communication and partitions.

Note on US20140317679A1 and US8869150B2:

• US20140317679A1 - System and method for creating secure applications: This is the patent application publication that ultimately matured into US9135418. Therefore, it describes the same invention and would inherently anticipate all claims of US9135418. It is typically not considered prior art for invalidation purposes against its own granted patent unless the claims of the granted patent are not fully supported by the original filing date.
• US8869150B2 - System and method for creating secure applications: This is a granted patent that shares significant common priority with US9135418, belonging to the same patent family and addressing the same inventive concepts. As such, it would also technically anticipate all claims of US9135418, as it discloses substantially the same invention or aspects thereof.

These analyzed patents and patent applications collectively demonstrate significant prior art in the field of creating and managing secure applications, particularly concerning secure partitions, IPC control, and policy-driven behavior modification without requiring access to source code. While the specific granular technical details of byte code or reference injection as described in certain claims of US9135418 (e.g., Claims 5-11, 18-20, 37-41, 45-47) might represent novel advancements over the broad disclosures of some of these prior arts, the higher-level inventive concepts and objectives are well-covered.

Based on the provided patent text for US9135418, the analysis of obviousness under 35 U.S.C. § 103 must rely on the prior art explicitly referenced or described within the document.

Identified Prior Art:

1. U.S. patent application Ser. No. 13/179,513 (hereinafter "the '513 application"): This application, filed on July 9, 2011, is explicitly incorporated by reference in its entirety into US9135418. The '513 application is described as:

   • An "MDM solution" that allows IT administrators to "provision devices, manage inventory, control network access, require minimum security settings, set policies and protect corporate data."
   • Disclosing an "electronic storefront" or "application repository" that permits an enterprise to "manage and distribute content developed by the enterprise or by another party," including applications to a wide variety of devices and operating systems.

2. General Knowledge of "Application Wrapping": The US9135418 patent specification extensively describes "application wrapping" as a known process in the art, without attributing it to a specific reference, implying it's general technical knowledge existing before the priority date of October 10, 2011. Key aspects of application wrapping described include:

   • Being an "automated process that augments an application with new capabilities" without needing source code modification.
   • Replacing "references to system services with references to implementations provided by a library that applies the needed mechanisms and policies."
   • Inserting "secure references... into the code of an application to replace non-secure references."
   • Invoking "additional logic prior to and at the end of executing an application" and adding "monitoring and instrumentation capabilities."
   • Providing "enhanced application management, including application security," by enabling "the injection of management layers onto the compiled applications, with no need for source code or developer-implemented application changes."

Limitation of Analysis:
The provided patent text for US9135418 does not include its claims. Therefore, this obviousness analysis will address the inventive concepts as broadly described in the specification, rather than a claim-by-claim analysis.

Obviousness Combination:

Combination: U.S. patent application Ser. No. 13/179,513 in combination with the general knowledge of "application wrapping."

Reasoning for Obviousness:

A person having ordinary skill in the art (PHOSITA) in the field of mobile device management and application security, as of the priority date of US9135418 (October 10, 2011), would have been motivated to combine the teachings of the '513 application with the known techniques of application wrapping to achieve the secure application features described in US9135418.

1. MDM and Policy Enforcement (from '513 application): The '513 application clearly establishes a system for mobile device management, focusing on an enterprise's ability to "set policies and protect corporate data" across distributed applications. It provides the overarching goal and the mechanism for distributing applications (an "application repository").

2. Achieving Security and Management without Source Code (from Application Wrapping): The general knowledge of "application wrapping" directly addresses a key challenge for enterprise MDM: how to augment and secure applications, especially third-party applications, without access to their source code. Application wrapping is described as an automated process capable of injecting "management layers" and "security" features by replacing or inserting references and adding logic at various points in an application's execution.

3. Motivation to Combine:

   • Meeting MDM Security Objectives: Given that the '513 application already teaches an MDM solution focused on "requir[ing] minimum security settings" and "protect[ing] corporate data", a PHOSITA would readily recognize application wrapping as an effective, efficient, and known method to implement these security settings directly within the applications distributed by the MDM's application repository. The ability of wrapping to apply "needed mechanisms and policies" and "enhanced application management, including application security" aligns perfectly with the objectives of the '513 application.
   • Enforcing Policies without Developer Involvement: Enterprises often distribute applications from various developers. The '513 application's storefront would distribute such applications. The fact that "application wrapping" requires "no source code needs to be modified" and "no need for source code or developer-implemented application changes" would be a strong motivation for a PHOSITA to combine these technologies. It allows the enterprise to enforce its security and management policies consistently across all distributed applications, regardless of whether they developed them or have access to their source code.
   • Implementing Specific Security Features: The core features described in US9135418, such as modifying application behavior with "intercepts" (secure byte codes or references), imposing "secure and unpredictable namespace[s]" for interprocess communication, and enforcing various policy-based controls (e.g., encryption, location-based restrictions, authentication), are all natural extensions or specific implementations of what application wrapping is described as capable of doing. For instance, replacing "references to system services with references to implementations provided by a library that applies the needed mechanisms and policies" directly enables control over IPC, data storage (encryption), and other application behaviors to conform to enterprise policies. The concept of creating a "secure partition" for these wrapped applications is also a logical step to further isolate and protect enterprise data, directly addressing the '513 application's goal of "protect[ing] corporate data."

Therefore, the general inventive concepts of creating secure applications by modifying compiled applications without source code access, injecting intercepts to alter behavior based on policies, creating secure namespaces for interprocess communication, and deploying them within secure partitions, as described in US9135418, would have been obvious to a PHOSITA who combined the well-known principles of "application wrapping" with the enterprise MDM and application distribution system described in U.S. patent application Ser. No. 13/179,513.