Rules-based network service management with on-demand dependency insertion
US-9485159-B1 · Nov 1, 2016 · US
US12175254B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12175254-B2 |
| Application number | US-202318150547-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 5, 2023 |
| Priority date | Sep 22, 2016 |
| Publication date | Dec 24, 2024 |
| Grant date | Dec 24, 2024 |
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).
The invention claimed is: 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 and each service application is configured to execute within a separate thread upon startup; and in response to a selection of a first reference within a communication or an external application: (i) determine to execute a first service application of the plurality of service applications; (ii) determine, based on the dependency tree, one or more parent service applications of the first service application; and (iii) startup the one or more parent service applications based on the dependency tree in one or more threads, wherein the one or more parent service applications comprise at least one parent service application and at least one grand-parent service application that depends on the at least one parent service application, wherein the first service application and the one or more parent service applications are started in an order defined by the dependency tree, wherein the order comprises starting up the at least one grand-parent service application and starting up the at least one parent service application after the at least one grand-parent service application has completed startup. 2. The mobile device of claim 1 , wherein the circuitry is further configured to: startup the one or more parent service applications simultaneously or concurrently based on the dependency tree. 3. The mobile device of claim 1 , wherein the circuitry is further configured to: 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. 4. The mobile device of claim 3 , wherein the circuitry is further configured to: subsequent to starting up the one or more parent service applications, generate, within the first thread and by the first service application, an application page including a second reference to a second service application, wherein the second service application has been started up as a parent service application of the first service application. 5. The mobile device of claim 4 , wherein the circuitry is further configured to: provide the application page to a user interface of the mobile device. 6. The mobile device of claim 5 , wherein the circuitry is further configured to: in response to determining user selection of the second reference, send a service application request to the second service application to execute the second service application. 7. The mobile device of claim 6 , wherein the first service application is a base application coded in a native mobile operating system code format, and the second service application is coded in a standard mobile application code format. 8. The mobile device of claim 7 , wherein the second service application is configured to present a second application page that includes a promotion details page or a redemption information page. 9. A method for a mobile device to provide a mobile application, the mobile application including a plurality of service applications, the method comprising: determining a dependency tree for the mobile application, wherein the dependency tree defines startup and shutdown dependencies among the plurality of service applications and each service application is configured to execute within a separate thread upon startup; and in response to a selection of a first reference within a communication or an external application: (i) determining to execute a first service application of the plurality of service applications; (ii) determining, based on the dependency tree, one or more parent service applications of the first service application; and (iii) starting up the one or more parent service applications based on the dependency tree in one or more threads, wherein the one or more parent service applications comprise at least one parent service application and at least one grand-parent service application that depends on the at least one parent service application, wherein the first service application and the one or more parent service applications are started in an order defined by the dependency tree, wherein the order comprises starting up the at least one grand-parent service application and starting up the at least one parent service application after the at least one grand-parent service application has completed startup. 10. The method of claim 9 , further comprising: startup the one or more parent service applications simultaneously or concurrently based on the dependency tree. 11. The method of claim 9 , further comprising: 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. 12. The method of claim 11 , further comprising: subsequent to starting up the one or more parent service applications, generate, within the first thread and by the first service application, an application page including a second reference to a second service application, wherein the second service application has been started up as a parent service application of the first service application. 13. The method of claim 12 , further comprising: provide the application page to a user interface of the mobile device. 14. The method of claim 13 , further comprising: in response to determining user selection of the second reference, send a service application request to the second service application to execute the second service application.
Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title
Installation · 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.