Basic architecture for software environment of radio terminal and method of handling events in the same

• US 20030079048A1
• Filed: 06/03/2002
• Published: 04/24/2003
• Est. Priority Date: 06/04/2001
• Status: Abandoned Application

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Kim, Hyung Jung
• Application Number:
  US10/158,913
• Publication Number:
  US 20030079048A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/543 Local
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A Basic Architecture for Software Environment(BASE) of a radio terminal and a method of handling events in the same are disclosed. The BASE and the method can simply make an application programs by module and apply the independence to the application programs by changing a structure of some parts corresponding to User Interface (UI) or Man Machine Interface (MMI) among software codes used in the radio terminal.

Claims

1. A Basic Architecture for Software Environment (BASE) of a radio terminal comprising:

a task part having a plurality of tasks and generating working events;

a BASE user interface (UI) independently performing an application program by module by using the events generated by the task part; and

an application program interface (API) interfacing the application program with a program development kit (PDK) library so that the application program may access the PDK library.

2. The BASE as claimed in claim 1, wherein the BASE UI includes;

a PDK handler handling events generated within the PDK and signals and the events generated by the task part;

a preprocessor processing and determining events to be first processed among the events output from the PDK handler;

a SPY handler processing and determining events to be processed in common for all of the application programs among the events not processed by the preprocessor;

a state machine processing the events output from and not processed by the SPY handler, wherein the events are not independently processed;

an application part independently processing the events output from and not processed by the SPY handler;

an application handler providing and identifying the corresponding event for each application of the application part; and

an application manager part managing, activating, and terminating the application part.

3. The BASE as claimed in claim 1, the tasks are HandSet(HS) task, Main Control(MC) task, Call Manager(CM) task, and File System(FS) task.

4. The BASE as claimed in claim 1, the SPY handler includes;

a system spy checking whether events processed in common exist or not; and

an application SPY processing corresponding events after operation of the system spy.

5. A method of handling events in a BASE of a radio terminal, the BASE including an application handler, a plurality of applications, and a PDK of development environment, the method comprising:

(a) transforming all of the events except for events used by a PDK under the status of development provided by the BASE among the generated events into available events and storing the transformed events in a queue;

(b) orderly reading first stored events from the queue and preprocessing predetermined events;

(c) processing events required in common by all of the application programs among the events not processed in the step (b);

(d) processing events such as startup, end, call, and idle among the events not processed in the step (c) and searching an activated application;

(e) transferring the events not processed in the step (d) to the searched application;

(f) processing the events not processed using an independent program module of the activated application.

6. The method as claimed in claim 5, wherein the events transformed in the step (a) include key down, timer check, Short Message Service(SMS), serial, and pointing.

7. The method as claimed in claim 5, wherein the step (f) includes;

(a1) selecting one of a plurality of applications and initiating variables;

(b1) informing an application handler of the selected application;

(c1) generating a terminating event for terminating an activated application at the application handler and providing the activated application with it;

(d1) performing the terminating procedure after processing all of the remaining events stored in the queue when the activated application receives the terminating event;

(e1) generating an activating event for the selected application at the application handler and transferring it to the selected application;

(f1) transferring the selected application'"'"'s information to the application handler and storing the transferred information at the application handler; and

(g1) performing an initiating procedure and processing input events at the selected application.

8. The method as claimed in claim 7, wherein the information stored by the application handler includes file header information, registery information, location information of a program code, location information of small icon data, location information of large icon data, location information of resource data, a code table of program offset, icon data of a program code, and resource data.

9. The method as claimed in claim 7, wherein the terminating procedure of a current application activated from the selected application includes;

(a2) transferring a terminating signal for terminating the current application into the application handler;

(b2) generating a terminating event informing that the current application terminates when the application handler receives the terminating signal and generating an activating event informing that a previously terminated application is again activated;

(c2) processing all of the events remaining in the queue at the current application and transferring the generated terminating event to a current application through the application handler to perform the termination procedure;

(d2) transferring the generated activating event to the previously terminated application through the application handler;

(e2) reading information of the previously terminated application and replacing a run function with a PXP file of the previously terminated application at the application handler, so that all of the events to be later generated are transferred to an application again activated from the previously terminated application; and

(f2) initiating the activated application again, processing the input activating event, and terminating the current application.

10. The method as claimed in claim 5, wherein the preprocessed events in the step (b) are either for displaying the status or for animation.

11. The method as claimed in claim 5, wherein the events required in common by all of the application programs in the step (c) are those having the SPY.

12. The method as claimed in claim 5, wherein the application of the independent program module is as follows.