Method and Apparatus for Identifying Application Instances Within a Machine-to-Machine Network Domain
US-2015149633-A1 · May 28, 2015 · US
US10257207B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10257207-B2 |
| Application number | US-201715714318-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 25, 2017 |
| Priority date | Sep 30, 2014 |
| Publication date | Apr 9, 2019 |
| Grant date | Apr 9, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are various embodiments relating to managed clones of applications. In one embodiment, an application is received. If it is determined that the application should be managed, a managed clone of the application is generated. The managed clone of the application is configured for coexistence along with the application upon a client device under management. The managed clone of the application may then be deployed to the client device under management.
Opening claim text (preview).
Therefore, the following is claimed: 1. A method comprising: receiving an application that is publicly available via an application distribution environment, the application being associated with a first icon; generating a managed clone of the application by: adding a management wrapper to the application; generating a badge; and applying the badge to a second icon associated with the managed clone of the application; deploying the managed clone of the application to the mobile client device, wherein the managed clone of the application and the application are both installed by the mobile client device, and wherein the mobile client device displays the first icon for the application and the second icon with the badge for the managed clone of the application; and instructing the mobile client device to automatically launch the application, rather than the managed clone of the application, in response to: receiving a user selection of the managed clone of the application; and determining that a compliance rule established remotely by an administrator and provided to the mobile client device prevents launch of the managed clone. 2. The method of claim 1 , wherein the first icon and the second icon comprise the same icon, except the second icon includes the badge. 3. The method of claim 1 , further comprising providing instructions to the mobile client device to select between executing the application and the managed clone of the application based on an applied gesture. 4. The method of claim 3 , wherein the instructions instruct the mobile client device to select between executing the application and the managed clone of the application based on a length of a press by a user. 5. The method of claim 4 , wherein the instructions instruct the mobile client device to execute the application upon receipt of a short press, and to execute the managed clone of the application upon receipt of a long press. 6. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor of a mobile client device, performs a method comprising: receiving an application that is publicly available via an application distribution environment, the application being associated with a first icon; generating a managed clone of the application by: adding a management wrapper to the application; generating a badge; and applying the badge to a second icon associated with the managed clone of the application; deploying the managed clone of the application to the mobile client device, wherein the managed clone of the application and the application are both installed by the mobile client device, and wherein the mobile client device displays the first icon for the application and the second icon with the badge for the managed clone of the application; and instructing the mobile client device to automatically launch the application, rather than the managed clone of the application, in response to: receiving a user selection of the managed clone of the application; and determining that a compliance rule established remotely by an administrator and provided to the mobile client device prevents launch of the managed clone. 7. The non-transitory, computer-readable medium of claim 6 , wherein the first icon and the second icon comprise the same icon, except the second icon includes the badge. 8. The non-transitory, computer-readable medium of claim 6 , the method further comprising providing instructions to the mobile client device to select between executing the application and the managed clone of the application based on an applied gesture. 9. The non-transitory, computer-readable medium of claim 8 , wherein the instructions instruct the mobile client device to select between executing the application and the managed clone of the application based on a length of a press by a user. 10. The non-transitory, computer-readable medium of claim 9 , wherein the instructions instruct the mobile client device to execute the application upon receipt of a short press, and to execute the managed clone of the application upon receipt of a long press. 11. A system comprising: a memory storage storing program code; and a processor coupled to the memory storage, wherein, upon execution, the program code causes the processor to: receive an application that is publicly available via an application distribution environment, the application being associated with a first icon; generate a managed clone of the application by: adding a management wrapper to the application; generating a badge; and applying the badge to a second icon associated with the managed clone of the application; deploy the managed clone of the application to a mobile client device, wherein the managed clone of the application and the application are both installed by the mobile client device, and wherein the mobile client device displays the first icon for the application and the second icon with the badge for the managed clone of the application; and instructing the mobile client device to automatically launch the application, rather than the managed clone of the application, in response to: receiving a user selection of the managed clone of the application; and determining that a compliance rule established remotely by an administrator and provided to the mobile client device prevents launch of the managed clone. 12. The system of claim 11 , wherein the first icon and the second icon comprise the same icon, except the second icon includes the badge. 13. The system of claim 11 , the program code further causing the processor to provide instructions to the mobile client device to select between executing the application and the managed clone of the application based on an applied gesture. 14. The system of claim 13 , wherein the instructions instruct the mobile client device to select between executing the application and the managed clone of the application based on a length of a press by a user.
when the policy decisions are valid for a limited amount of time · CPC title
Image based installation; Cloning; Build to order · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
Multiple levels of security · CPC title
Installation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.