Multiprocessor Programming Toolkit for Design Reuse
US-2024394048-A1 · Nov 28, 2024 · US
US9798529B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9798529-B2 |
| Application number | US-201013320853-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 24, 2010 |
| Priority date | May 29, 2009 |
| Publication date | Oct 24, 2017 |
| Grant date | Oct 24, 2017 |
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.
A computer readable medium including computer readable code for causing a computer system to perform a method. The method includes receiving an application, receiving application information for the application, and determining an access privilege for the application based, in part, on the application information. The method also includes generating a deployment package for the application using the application and the access privilege, and publishing the application.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer readable medium comprising computer readable program code embodied therein for causing a computer system to perform a method, the method comprising: receiving an application; receiving application information for the application; executing, for a reviewer, the application directly in a reviewer portal on the computer system, the reviewer portal accessible to the reviewer via a uniform resource locator; determining an access privilege for the application based, in part, on the application information and the reviewer, wherein the access privilege restricts execution of the application to a sandbox when the access privilege specifies sandbox-only execution, wherein the access privilege permits limited access to resources outside the sandbox when the access privilege specifies limited access execution, and wherein the sandbox is an isolated execution environment within a runtime environment; setting a digital rights management (DRM) setting for the application specifying that the application may be copied to multiple client devices; generating a first deployment package for the application using the application, the DRM setting, and the access privilege, and based on a first client device type; generating a second deployment package for the application using the application, the DRM setting, and the access privilege, and based on a second client device type: publishing the application to a warehouse; receiving a first request for the application from a first client device having the first client device type and associated with a user account at the warehouse, wherein the user account is associated with a purchased copy of the application; providing the first deployment package to the first client device, wherein the first client device executes the first deployment package within the sandbox using the runtime environment on the first client device; receiving a second request for the application from a second client device having the second client device type and associated with the user account; and providing, without requiring a purchase of another copy of the application, the second deployment package to the second client device, wherein the second client device executes the second deployment package within the sandbox using the runtime environment on the second client device. 2. The non-transitory computer readable medium of claim 1 , wherein the method further comprises: receiving client usage data from the first client device, wherein the client usage data includes information about the usage of the application on the first client device. 3. The non-transitory computer readable medium of claim 2 , wherein the method further comprises: providing, after removing personal identification information, the client usage data to a developer of the application. 4. The non-transitory computer readable medium of claim 2 , wherein the client usage data is obtained using a separate application. 5. The non-transitory computer readable medium of claim 1 , wherein the method further comprises: providing a latest version of the application to the first client device when the first client device does not include the latest version of the application and the first client device is attempting to execute a version of the application other than the latest version of the application. 6. The non-transitory computer readable medium of claim 1 , wherein the first client device is one selected from a group consisting of a computer connected to a wired network, a computer connected to a wireless network, a 2G mobile device, a 3G mobile device, a personal digital assistant, a smart phone, and a set-top box. 7. The non-transitory computer readable medium of claim 1 , wherein the DRM setting is enforced by the runtime environment on the first client device. 8. The non-transitory computer readable medium of claim 1 , wherein the application is received in an archive file format. 9. The non-transitory computer readable medium of claim 1 , wherein the first deployment package is generated in accordance with a Network Launch Protocol. 10. The non-transitory computer readable medium of claim 9 , wherein the access privilege is enforced by the runtime environment of the first client device. 11. The non-transitory computer readable medium of claim 1 , wherein the application is a Java application. 12. A system for publishing an application, comprising: a processor; and a memory comprising computer readable code, executable by the processor, configured to: receive an application and application information for the application; execute, for a reviewer, the application directly in a reviewer portal on the processor, the reviewer portal accessible to the reviewer via a uniform resource locator, determine an access privilege for the application based, in part, on the application information and the reviewer, wherein the access privilege restricts execution of the application to a sandbox when the access privilege specifies sandbox-only execution, wherein the access privilege permits limited access to resources outside the sandbox when the access privilege specifies limited access execution, and wherein the sandbox is an isolated execution environment within a runtime environment; set a digital rights management (DRM) setting for the application specifying that the application may be copied to multiple client devices; generate a first deployment package for the application using the application, the DRM setting, and the access privilege, and based on a first client device type; generate a second deployment package for the application using the application, the DRM setting, and the access privilege, and based on a second client device type; publish the application to a warehouse to make the first deployment package available for at least one selected from a group consisting of installation on a first client device and previewing on the first client device, wherein the first client device has the first client device type and is associated with a user account at the warehouse, wherein the user account is associated with a purchased copy of the application; receive a first request for the application from the first client device; provide the first deployment package to the first client device, wherein the first client device executes the first deployment package within the sandbox using the runtime environment on the first client device; receive a second request for the application from a second client device having the second client device type and associated with the user account; and provide, without requiring a purchase of another copy of the application, the second deployment package to the second client device, wherein the second client device executes the second deployment package within the sandbox using the runtime environment on the second client device. 13. The system of claim 12 , wherein the computer readable code is further configured to: receive client usage data from the first client device, wherein the client usage data includes information about the usage of the application on the first client device. 14. The system of claim 13 , wherein the computer readable code is further configured to: provide, after removing personal identification information, the client usage data to a developer of the application. 15. The system of claim 12 , wherein the computer readable code is further configured to: provide a latest version of the application to the first client device when the first client device does not include the latest version of the applic
Software deployment · CPC title
Restricting unauthorised execution of programs · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.