Middleware application environment

• US 20040098727A1
• Filed: 09/19/2003
• Published: 05/20/2004
• Est. Priority Date: 09/23/2002
• Status: Active Grant

• Current Assignee: Optis Wireless Technology, LLC (Brevet Capital)
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Hansson, Jonas, Bjare, Bjorn, Le, Chi Thu
• Granted Patent: US 7,350,211 B2
• Time in Patent Office: Days
• US Class Current: 719/310
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

A software application framework includes a framework interface domain for interfacing a platform domain with application domain software of an application domain. The framework also includes a software application domain that includes a first application entity. The first application entity is adapted to interact with at least one of a second application entity, the framework interface domain, at least one utility entity, and at least one plug-in entity.

Claims

1. A software application framework comprising:

a framework interface domain for interfacing a platform domain with application domain software of an application domain;

a software application domain comprising a first application entity; and

wherein the first application entity is adapted to interact with at least one of;

a second application entity;

the framework interface domain;

at least one utility entity; and

at least one plug-in entity.

2. The software application framework of claim 1, wherein the application domain further comprises:

the at least one utility entity;

the at least one plug-in entity;

wherein at least one of the at least one utility entity is adapted to use at least one of;

the framework interface domain;

at least one of;

the first application entity;

the second application entity; and

a third application entity;

at least one of the at least one plug-in entity; and

at least one of the at least one utility entity; and

wherein the at least one plug-in entity is adapted to use the framework interface domain.

3. The software application framework of claim 2, wherein the plug-in entity is adapted to extend the functionality of the platform domain.

4. The software application framework of claim 2, wherein the plug-in entity is adapted to appear to be a part of the framework interface domain.

5. The software application framework of claim 2, wherein the utility entity is adapted to buffer and shield legacy code.

6. The software application framework of claim 2, wherein the application entity is adapted to own at least one thread.

7. The software application framework of claim 6, wherein the at least one thread is automatically created upon start-up of the application entity.

8. The software application of claim 7, wherein at least one of the following comprises encapsulated code:

the first application entity;

the second application entity;

the third application entity;

the at least one of the at least one plug-in entity; and

the at least one of the at least one utility entity.

9. The software application framework of claim 1, wherein the software application framework is resident on a mobile equipment.

10. The software application framework of claim 1, wherein:

the software application framework uses a dual-mode message-exchange procedure; and

the procedure comprises use of procedure/stack-based handling and message/serialization-based handling.

11. The software application framework of claim 1, wherein the application domain minimizes a need for support code.

12. A method of using a software application framework, the method comprising:

interfacing a platform domain with application domain software of an application domain via a framework interface domain; and

a first application entity of the application domain interacting with at least one of a second application entity, the framework interface domain, at least one utility entity, and at least one plug-in entity.

13. The method of claim 12, wherein the application domain further comprises the at least one utility entity and the at least one plug-in entity, the method further comprising:

at least one of the at least one utility entity using at least one of;

the framework interface domain;

at least one of the first application entity, the second application entity, and a third application entity;

at least one of the at least one plug-in entity; and

at least one of the at least one utility entity; and

the at least one plug-in entity using the framework interface domain.

14. The method of claim 13, wherein the plug-in entity extends the functionality of the platform domain.

15. The method of claim 13, wherein the plug-in entity appears to be a part of the framework interface domain.

16. The method of claim 13, wherein the utility entity buffers and shields legacy code.

17. The method of claim 13, wherein the application entity owns at least one thread.

18. The method of claim 17, wherein the at least one thread is automatically created upon start-up of the application entity.

19. The method of claim 18, wherein at least one of the following comprises encapsulated code:

the first application entity;

the second application entity;

the third application entity;

the at least one of the at least one plug-in entity; and

the at least one of the at least one utility entity.

20. The method of claim 12, wherein the software application framework is resident on a mobile equipment.

21. The method of claim 12, further comprising:

using, by the software application framework, of a dual-mode message-exchange procedure; and

wherein the procedure comprises use of procedure/stack-based handling and message/serialization-based handling.

22. The method of claim 12, wherein the application domain minimizes a need for support code.