Browser-based user interface and control architecture with priority attributes

• US 8,458,728 B2
• Filed: 12/18/2008
• Issued: 06/04/2013
• Est. Priority Date: 12/20/2007
• Status: Active Grant

• Current Assignee: Access Company Limited
• Original Assignee: Access Company Limited
• Inventors: Tian, Yong, Chin, Brian
• Primary Examiner(s): Ho, Andy
• Assistant Examiner(s): SEYE, ABDOU K
• Application Number:
  US12/809,982
• Publication Number:
  US 20100299607A1
• Time in Patent Office: 1,629 Days
• Field of Search: 719/328, 709/204
• 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 browser-enabled device includes a browser-based user interface and control architecture, which has a browser core, a browser framework, and a user interface. The user interface is written using a markup language. In processing event registrations, the browser framework receives an event registration. The received event registration having a response unique resource identifier (URI) content and a priority field. The priority field of the received event registration is examined to determine priority of the received event registration. If the browser core is loading the response URI content of a prior event registration and if the priority of the received event registration is higher than the priority of the prior event registration, then the loading of the response URI content of the prior event registration is halted, and loading of the response URI content of the received event registration is begun.

Claims

1. A computer-enabled method of processing event registrations in a browser-based user interface and control architecture of a browser-enabled device, the browser-based user interface and control architecture having a browser core, a browser framework, and a user interface, the user interface being written using a markup language, the method comprising:

receiving an event registration, by one or more processors, the received event registration having a response unique resource identifier (URI) content and a priority field, the event registration being received by the browser framework;

examining, by the one or more processors, the priority field of the received event registration to determine priority of the received event registration;

if the browser core is loading the response URI content of a prior event registration, then determining if the priority of the received event registration is higher than the priority of the prior event registration; and

if the priority of the received event registration is higher than the priority of the prior event registration, then;

halting the loading of the response URI content of the prior event registration and starting to load the response URI content of the received event registration, and

after starting to load the response URI content of the received event registration, returning to loading the response URI content of the prior event registration,

wherein the response URI content of the received event registration includes at least a portion of the user interface.

2. The method of claim 1, further comprising:

if the priority of the received event registration is not higher than the priority of the prior event registration, then continuing to load the response URI content of the prior event registration.

3. The method of claim 1, further comprising:

queuing event registrations in a queue; and

processing event registrations from the queue based on the priorities of the event registrations.

4. The method of claim 1, wherein the event registrations in the queue include timeout parameters, and further comprising:

removing event registrations from the queue based on the timeout parameters of the event registrations.

5. The method of claim 1, further comprising:

defining all events to be processed by the browser core; and

assigning priorities to the defined events.

6. The method of claim 5, wherein the defined events includes:

a first set of events associated with telephony functions; and

a second set of events associated with browsing functions.

7. The method of claim 6, wherein one of the first set of events is an incoming call event, wherein the incoming call event is assigned the highest priority.

8. The method of claim 1, wherein the browser-based user interface and control architecture includes an operating system kernel capable of running only one thread at a time.

9. The method of claim 1, wherein the steps of receiving, examining, determining, and halting are performed by an application programming interface of the browser framework.

10. The method of claim 1, wherein the prior event registration is related to a browsing function, and wherein the received event registration is an incoming call event.

11. The method of claim 1, wherein the prior event registration is related to a first web page, wherein the received event registration is related to a second web page, and further comprising:

alternating between loading the response URI contents of the received and prior event registrations until the second web page has been completely loaded; and

when the second web page has been completely loaded, instructing the display of the second web page on the browser-enabled device.

12. The method of claim 1, wherein the prior event registration is related to a first web page, wherein the received event registration is related to a second web page, and further comprising:

when the first web page has been loaded and is being displayed on the browser-enabled device, loading the response URI content of the received event registration in background on the browser core; and

when the second web page has been completely loaded, instructing the browser-enabled device to switch from displaying the first web page to displaying the second web page.

13. A non-transitory computer-readable storage medium having computer-executable instructions for processing event registrations in a browser-based user interface and control architecture of a browser-enabled device, the browser-based user interface and control architecture having a browser core, a browser framework, and a user interface, the user interface being written using a markup language, comprising instructions for:

receiving an event registration, the received event registration having a response unique resource identifier (URI) content and a priority field, the event registration being received by the browser framework;

examining the priority field of the received event registration to determine priority of the received event registration;

if the browser core is loading the response URI content of a prior event registration, then determining if the priority of the received event registration is higher than the priority of the prior event registration; and

if the priority of the received event registration is higher than the priority of the prior event registration, then;

halting the loading of the response URI content of the prior event registration and starting to load the response URI content of the received event registration, and

after starting to load the response URI content of the received event registration, returning to loading the response URI content of the prior event registration,

wherein the response URI content of the received event registration includes at least a portion of the user interface.

14. The computer-readable storage medium of claim 13, further comprising instructions for:

if the priority of the received event registration is not higher than the priority of the prior event registration, then continuing to load the response URI content of the prior event registration.

15. The computer-readable storage medium of claim 13, further comprising instructions for:

queuing event registrations in a queue; and

processing event registrations from the queue based on the priorities of the event registrations.

16. The computer-readable storage medium of claim 13, wherein the browser-based user interface and control architecture includes an operating system kernel capable of running only one thread at a time.

17. The computer-readable storage medium of claim 13, wherein the prior event registration is related to a first web page, wherein the received event registration is related to a second web page, and further comprising instructions for:

alternating between loading the response URI contents of the received and prior event registrations until the second web page has been completely loaded; and

when the second web page has been completely loaded, instructing the display of the second web page on the browser-enabled device.

18. The computer-readable storage medium of claim 13, wherein the prior event registration is related to a first web page, wherein the received event registration is related to a second web page, and further comprising instructions for:

when the first web page has been loaded and is being displayed on the browser-enabled device, loading the response URI content of the received event registration in background on the browser core; and

when the second web page has been completely loaded, instructing the browser-enabled device to switch from displaying the first web page to displaying the second web page.

19. A browser-enabled device, comprising:

a processor;

memory; and

a browser-based user interface and control architecture comprising;

an operating system kernel;

a browser core;

a user interface written using the markup language; and

a browser framework, the browser framework having an application programming interface (API) configured to;

receive an event registration, the event registration having a response unique resource identifier (URI) content and a priority field;

examine the priority field of the event registration to determine priority of the received event registration;

if the browser core is loading the response URI content of a prior event registration, then determine if the priority of the received event registration is higher than the priority of the prior event registration; and

if the priority of the received event registration is higher than the priority of the prior event registration, then;

halt loading of the response URI content of the prior event registration and start loading the response URI content of the received event registration, and

after starting to load the response URI content of the received event registration, return to loading the response URI content of the prior event registration,

wherein the response URI content of the received event registration includes at least a portion of the user interface.

20. The browser-enabled device of claim 19, further comprising:

a queue configured to store event registrations, wherein the API is configured to process event registrations from the queue based on the priorities of the event registrations.

21. The browser-enabled device of claim 19, further comprising:

a table having an assignment of priorities to events to be processed by the browser framework.

22. The browser-enabled device of claim 21, wherein an incoming call event is assigned the highest priority.

23. The browser-enabled device of claim 19, wherein the operating system kernel is capable of running only one thread at a time.

24. The browser-enabled device of claim 19, further comprising:

telephony components, wherein the event of the prior event registration is related to a browsing function, and wherein the event of the received event registration is an incoming call event.

25. The browser-enabled device of claim 19, wherein the prior event registration is related to a first web page, wherein the received event registration is related to a second web page, and wherein the API is further configured to:

alternate between loading the response URI contents of the received and prior event registrations until the second web page has been completely loaded; and

when the second web page has been completely loaded, instruct the display of the second web page on the browser-enabled device.

26. The browser-enabled device of claim 19, wherein the prior event registration is related to a first web page, wherein the received event registration is related to a second web page, and wherein the API is further configured to:

when the first web page has been loaded and is being displayed on the browser-enabled device, load the response URI content of the received event registration in background on the browser core; and

when the second web page has been completely loaded, instruct the browser-enabled device to switch from displaying the first web page to displaying the second web page.