Handling Messages in a Computing Device

• US 20110197202A1
• Filed: 06/24/2009
• Published: 08/11/2011
• Est. Priority Date: 06/25/2008
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Lodolo, Francesco
• Application Number:
  US13/001,012
• Publication Number:
  US 20110197202A1
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A method for determining dynamically how data processing requests are to be handled within a computing device. On receipt of a message at a central dispatching entity, the dispatching entity retrieves information from a database specifying how the message is to be handled, and in response it issues commands to selected components within the computing device to cause a data processing operation to be performed.

Claims

1. A method for handling messages relating to data processing operations in a computing device, the method comprising:

receiving a message from a client process at a dispatching entity;

in response to receiving the message, retrieving, from an entity external to the dispatching entity, data specifying how the message is to be handled; and

in response to retrieving the data, causing one or more selected components of the computing device to carry out a data processing operation indicated in the message, by sending further messages from the dispatching entity to the said components.

2. A method according to claim 1 wherein the retrieval of data specifying how the message is to be handled is performed at runtime, such that a determination of how the message is to be handled is made dynamically in response to receiving the message at the dispatching entity.

3. A method according to claim 1 wherein the retrieval of data comprises retrieving a predefined scheme from a data structure, the scheme corresponding to the message received at the dispatching entity.

4. A method according to claim 3 wherein the scheme specifies which components are to be used in the handling of the message.

5. A method according to claim 4 wherein the scheme additionally specifies timing considerations relating to the components that are to be used in the handling of the message, such as the order in which the further messages are to be sent from the dispatching entity to the components.

6. A method according to claim 5 wherein the timing considerations are based at least in part on hardware or software dependencies between the said components.

7. A method according to claim 5 wherein the timing considerations are based at least in part on conditions prevailing within the computing device.

8. A method according to claim 1 wherein no predefined scheme exists which corresponds to the message received at the dispatching entity, and the retrieval of data comprises retrieving one or more rules, at least one rule corresponding to more than one message and specifying how a given type of message is to be handled.

9. A dispatching entity for handling messages relating to data processing operations in a computing device, the dispatching entity being arranged to perform:

receiving a message from a client process at a dispatching entity;

in response to receiving the message, retrieving, from an entity external to the dispatching entity, data specifying how the message is to be handled; and

in response to retrieving the data, causing one or more selected components of the computing device to carry out a data processing operation indicated in the message, by sending further messages from the dispatching entity to the said components.

10. Apparatus according to claim 9 wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to additionally perform the retrieval of data, specifying how the message is to be handled, at runtime, such that a determination of how the message is to be handled is made dynamically in response to receiving the message at the dispatching entity.

13. Apparatus according to claim 9 wherein the retrieval of data comprises retrieving a predefined scheme from a data structure, the scheme corresponding to the message received at the dispatching entity.

14. Apparatus according to claim 13 wherein the scheme specifies which components are to be used in the handling of the message.

15. Apparatus according to claim 14 wherein the scheme additionally specifies timing considerations relating to the components that are to be used in the handling of the message, such as the order in which the further messages are to be sent from the dispatching entity to the components.

16. Apparatus according to claim 15 wherein the timing considerations are based at least in part on hardware or software dependencies between the said components.

17. Apparatus according to claim 15 wherein the timing considerations are based at least in part on conditions prevailing within the computing device.

18. Apparatus according to claim 9 wherein no predefined scheme exists which corresponds to the message received at the dispatching entity, and the retrieval of data comprises retrieving one or more rules, at least one rule corresponding to more than one message and specifying how a given type of message is to be handled.

11. (canceled)

12. (canceled)

19. A computer program product comprising computer program code arranged to perform:

receiving a message from a client process at a dispatching entity;

in response to receiving the message, retrieving, from an entity external to the dispatching entity, data specifying how the message is to be handled; and

in response to retrieving the data, causing one or more selected components of the computing device to carry out a data processing operation indicated in the message, by sending further messages from the dispatching entity to the said components.