Method and system for starting up application
US-2019108038-A1 · Apr 11, 2019 · US
US10922089B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10922089-B2 |
| Application number | US-201715711264-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 21, 2017 |
| Priority date | Sep 22, 2016 |
| Publication date | Feb 16, 2021 |
| Grant date | Feb 16, 2021 |
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.
Techniques for improved mobile application architectures and service communication protocols are discussed herein. Some embodiments may include a mobile device configured for providing a mobile application including multiple service applications. The service applications may execute asynchronously and in separate containers, providing service orientated architecture (SOA)-like services with respect to other portions of the mobile application, or even external applications. The separation of a monolithic mobile application into separate service applications provide advantages in terms of application performance, development, and maintenance. For example, a subset of all service applications may be started up, and executed on demand to improve device resource utilization efficiency.
Opening claim text (preview).
That which is claimed: 1. A mobile device configured for providing a mobile application, the mobile application including a plurality of service applications, the mobile device comprising circuitry configured to: determine a dependency tree for the mobile application, wherein the dependency tree defines startup and shutdown dependencies among the plurality of service applications, wherein each service application is configured to execute within a separate thread upon startup, and wherein each thread is associated with a unique execution context; determine to execute a first service application of the plurality of service applications, wherein the first service application is configured to generate an application page for presentation on at least a portion of a user interface operating on the mobile device, and responsive to receiving a service application request comprising application page input parameters: determine, based on the dependency tree, one or more parent service applications of the first service application; startup the one or more parent service applications based on the dependency tree in one or more threads; subsequent to starting up the one or more parent service applications, startup the first service application in a first thread separate from the one or more threads; subsequent to starting up the first service application, execute the first service application within the first thread; and provide, based at least in part on the application page input parameters, the application page corresponding with the first service application for presentation on the at least a portion of the user interface. 2. The mobile device of claim 1 , wherein the circuitry is further configured to startup the one or more parent service applications by being configured to startup the plurality of parent applications simultaneously or concurrently. 3. The mobile device of claim 1 , wherein the circuitry is further configured to startup the first service application and the one or more parent service applications in an order defined by the dependency tree. 4. A method for a mobile device to provide a mobile application, the mobile application including a plurality of service applications, the method comprising: determining, by circuitry of the mobile device, application a dependency tree for the mobile application, wherein the dependency tree defines startup and shutdown dependencies among the plurality of service applications, wherein each service application is configured to execute within a separate thread upon startup, and wherein each thread is associated with a unique execution context; determining, by the circuitry, to execute a first service application of the plurality of service applications, wherein the first service application is configured to generate an application page for presentation on at least a portion of a user interface operating on the mobile device, and responsive to receiving, by the circuitry, a service application request comprising application page input parameters: determining, by the circuitry and based on the dependency tree, one or more parent service applications of the first service application; starting up, by the circuitry, the one or more parent service applications based on the dependency tree in one or more threads; subsequent to starting up the one or more parent service applications, starting up, by the circuitry, the first service application in a first thread separate from the one or more threads; subsequent to starting up the first service application, executing, by the circuitry, the first service application within the first thread; and providing, by the circuitry and based at least in part on the application page input parameters, the application page corresponding with the first service application for presentation on the at least a portion of the user interface. 5. At least one non-transitory computer readable medium for causing a mobile device configured to provide a mobile application, the at least one non-transitory computer readable medium storing a plurality of service applications and further storing instructions that, when executed by the mobile device, cause circuitry of the mobile device to: determine a dependency tree for the mobile application, wherein the dependency tree defines startup and shutdown dependencies among the plurality of service applications, wherein each service application is configured to execute within a separate thread upon startup, and wherein each thread is associated with a unique execution context; determine to execute a first service application of the plurality of service applications, wherein the first service application is configured to generate an application page for presentation on at least a portion of a user interface operating on the mobile device, and responsive to receiving a service application request comprising application page input parameters: determine, based on the dependency tree, one or more parent service applications of the first service application; startup the one or more parent service applications based on the dependency tree in one or more threads; subsequent to starting up the one or more parent service applications, startup the first service application in a first thread separate from the one or more threads; and subsequent to starting up the first service application, execute the first service application within the first thread; and provide, based at least in part on the application page input parameters, the application page corresponding with the first service application for presentation on the at least a portion of the user interface.
Installation · CPC title
Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title
Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57) · CPC title
Bootstrapping (security arrangements therefor G06F21/57) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.