EVENT DRIVEN ADAPTIVE USER INTERFACE

• US 20140365907A1
• Filed: 05/01/2014
• Published: 12/11/2014
• Est. Priority Date: 06/10/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: DE FREITAS, JOSE A. G., HINDLE, GUY P.
• Granted Patent: US 9,766,862 B2
• Time in Patent Office: Days
• US Class Current: 715/746
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A method and/or computer program product provide an event driven adaptive user interface. A high-level event is received from a high-level event generator. A determination is made as to whether the high-level event is of a registered event type according to a mapping to one or more registered possible action types, where the registered event type and registered possible action types include payload objects with mappings to one or more user interface controls. One or more user interface controls for the high-level event and for possible actions are displayed to a user for selection. The user selection is then processed for the high-level event to initiate zero or more actions.

Claims

1. A method for providing an event driven adaptive user interface, the method comprising:

receiving, by one or more processors, a high-level event from a high-level event generator;

determining, by one or more processors, if the high-level event is of a registered event type according to a mapping to one or more registered possible action types, wherein the registered event type and registered possible action types include payload objects with mappings to one or more user interface controls;

displaying, by one or more processors, the one or more user interface controls for the high-level event and for possible actions to a user for selection; and

processing, by one or more processors, a user selection for the high-level event to initiate zero or more actions.

2. The method as claimed in claim 1, further comprising:

establishing, by one or more processors, a user context by means of a high-level event generator in a form of a complex event processing engine, wherein the complex event processing engine fires a time and context relevant high-level event.

3. The method as claimed in claim 1, wherein displaying the one or more user interface controls for the high-level event and for possible actions to a user for selection includes automatic selection without user input based on predefined rules.

4. The method as claimed in any one of claim 1, further comprising:

providing, by one or more processors, an event registry for;

mapping an event type to one or more action types, wherein the event type and action types have payload objects;

mapping payload objects to user interface controls; and

mapping an event and user interface controls to zero or more actions.

5. The method as claimed in claim 4, wherein providing an event registry includes the event registry having metadata to interpret event and action payloads.

6. The method as claimed in claim 5, further comprising:

providing, by one or more processors, an event registry for;

storing payload descriptors which describe the event and action payloads.

7. The method as claimed in claim 1, further comprising:

queuing, by one or more processors, received events from a complex event processing engine; and

prioritizing, by one or more processors, queued events.

8. The method as claimed in claim 1, further comprising:

determining, by one or more processors, if a received event is a registered event; and

in response to the received event not being a registered event, displaying, by one or more processors, a message to the user to ignore the event.

9. The method as claimed in claim 1, further comprising:

determining, by one or more processors, if a received event is a registered event; and

in response to the received event being a registered event, adding, by one or more processors, the one or more user interface controls to a user interface container and displaying the controls to a user for selection.

10. The method as claimed in claim 1, further comprising:

waiting, by one or more processors, for a predetermined period of time for a user response before displaying the registered one or more user interface controls for an event.

11. The method as claimed in claim 10, further comprising:

in response to no user response being received in the predetermined period, applying, by one or more processors, a predefined policy.

12. The method as claimed in claim 1, further comprising:

dispatching, by one or more processors, a registered action to a complex event processing engine.

13. An event driven adaptive user interface, comprising:

an event queue for receiving a high-level event from a high-level event generator;

an event registry of events, of a registered event type, mapped to one or more registered possible action types, wherein the registered event types and the possible action types include payload objects with mappings to one or more user interface controls;

an event processor for displaying the one or more user interface controls for the high-level event and for possible actions to a user for selection; and

an action processor for mapping a user selection for the high-level event to initiate zero or more actions.

14. The user interface as claimed in claim 13, wherein the event processor for displaying the one or more user interface controls for the high-level event and for possible actions to a user for selection includes an automatic selection component for automatic selection without user input based on predefined rules.

15. The user interface as claimed in claim 13, wherein the event registry includes:

a mapping of an event type to one or more action types, wherein the event type and action types have payload objects;

a mapping of payload objects to user interface controls; and

a mapping of an event and user interface controls to zero or more actions.

16. The user interface as claimed in claim 13, wherein the event registry includes metadata to interpret event payloads.

17. The user interface as claimed any claim 13, wherein the event registry includes:

payload descriptors which describe the high-level event and/or an action payload.

18. The user interface as claimed in claim 13, wherein the event queue is for prioritizing queued events.

19. The user interface as claimed in claim 13, wherein the event processor is for adding the one or more user interface controls to a user interface container and displaying the controls to a user for selection.

20. A computer program product for providing an event driven adaptive user interface, the computer program product comprising a computer readable storage medium having program code embodied therewith, the program code readable and executable by a processor to perform a method comprising:

receiving a high-level event from a high-level event generator;

determining if the high-level event is of a registered event type according to a mapping to one or more registered possible action types, wherein the registered event type and registered possible action types include payload objects with mappings to one or more user interface controls;

displaying the one or more user interface controls for the high-level event and for possible actions to a user for selection; and

processing a user selection for the high-level event to initiate zero or more actions.