Component-based control structure for wireless communication

• US 6,263,213 B1
• Filed: 12/21/1998
• Issued: 07/17/2001
• Est. Priority Date: 12/23/1997
• Status: Expired due to Term

• Current Assignee: Sony International Europe Gmbh (Sony Group Corp.)
• Original Assignee: Sony International Europe Gmbh (Sony Group Corp.)
• Inventors: Kovacs, Ernö
• Primary Examiner(s): LE, THANH C
• Application Number:
  US09/217,674
• Time in Patent Office: 939 Days
• Field of Search: 455/422, 455/426, 455/423, 455/424, 455/445, 455/450, 455/452, 455/458, 455/560, 455/561, 455/550, 455/556, 455/557, 455/558, 455/575
• US Class Current: 455/550.1
• CPC Class Codes: G06F 9/4488 Object-oriented

Abstract

A component-based control application structure for the dynamic configuration, adaptation and extension of applications in wireless communication is presented. Thereby, a control application (304) for technical elements (301) of a mobile communications device (101a, 101b) is structured in components of a predetermined configuration (305), wherein the configuration (305) depends on the task to be performed. Each component (401) is provided with its own thread (404). Each component (401) is furthermore provided with a method interface (403) comprising different commands for the control of the operation of the respective component (401). The configuration (305) of the control application (304) can be changed dynamically (203) depending on the current task to be performed by the device.

Claims

1. A method for controlling a mobile communications device, comprising the steps of:

structuring a control application of the mobile communications device in components of a predetermined configuration, wherein the predetermined configuration depends on a current task to be performed by the mobile communications device and each component is designed as an active object responsible for a specific operation of the mobile communications device;

providing each component with its own execution thread corresponding to the operation to be effected by the component;

providing each component with a method interface comprising different commands for the control of the operation of the respective component; and

dynamically changing the configuration of the control application depending on the current task to be performed.

2. A method according to claim 1, wherein the structuring step structures the control application in a tree-like configuration.

3. A method according to claim 2, further comprising the steps of:

transmitting an emitted command upwards in the tree-like configuration to at least one level above an emitting component; and

transmitting the emitted command downwards to all components in the tree-like configuration of the control application.

4. A method according to claim 2, further comprising the steps of:

transmitting an emitted command upwards in the tree-like configuration to a root component of the tree-like configuration; and

transmitting the emitted command downwards to all components in the tree-like configuration of the control application.

5. A method according to claim 1, further comprising the step of providing each component with an identifier identifying the component and a role of the component in the configuration of the control application.

6. A method according to claim 5, further comprising the step of providing a command to be emitted with the identifier of a target component, so that the command is only executed by that component.

7. A method according to claim 1, further comprising the step of providing a command to be emitted to the control application or a sub-tree thereof without an identifier.

8. A method according to claim 1, further comprising the steps of:

sending a start command to each component to start the control application;

forwarding program line arguments as parameters to each component;

assigning a thread to at least one component;

starting the assigned thread; and

stopping the components by a stop command.

9. A method according to claim 8, further comprising the step of providing a query command to query whether a component has been stopped or not.

10. A method according to claim 8, further comprising the step of providing a halt command to stop the execution of a thread of an assigned component.

11. A method according to claim 10, further comprising the step of providing a resume command to restart a stopped execution of a thread of a component.

12. A method according to claim 8, further comprising the step of providing a bind command to request a pointer to a specific component with a specific identifier.

13. A method according to claim 12, wherein leaves of the tree-like configuration of the control application represent technical elements of the mobile communications device.

14. A method according to claim 1, wherein an abstract factory directly transmits a create configuration command to a concrete factory, and

wherein the abstract factory contains an abstract, platform independent method and the concrete factory implements the abstract method of the abstract factory by creating the actual configuration of the control application depending on the platform used.