IP Library Granted Patent US 9,875,671
Granted Patent B2
US 9,875,671 · App. 12/640,938 · Granted Jan 23, 2018

Cloud-based user interface augmentation

Inventors: Chaitanya Gharpure (Mountain View, CA); Charles L Chen (San Jose, CA); Rachel Shearer (San Francisco, CA); Tiruvilwamalai V. Raman (San Jose, CA)
Assignee: Google LLC
G09B21/009G06F17/30867G09B21/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,875,671
App. No.
12/640,938
Granted
Jan 23, 2018
Kind
B2
Abstract

Method for providing augmented user interface (AUI). AUI is provided in response to a request. AUI configuration information is received, stored in preference file, and sent to remote server. Remote server receives request from computer to login user. Remote server authenticates user, retrieves and sends preference file to computer. Preference file contains information that allows computer to implement and configure AUI by directing output to AUI component. Remote server sends computer web-based API to enable browser to interface with an AUI application. API can include target callable by event handler to respond to HTML document browsing event by invoking AUI application. Remote server can send computer web-based, native, or browser plug-in AUI application. Computer can provide content rich navigation via API, AUI application and content navigation rules that define plural navigation paths through HTML document. Navigation paths providing AUI functionality to particular type of special needs user or user task.

Claims (28)

1. A computer-implemented method comprising:

providing an application programming interface running in a web browser on a computer to receive a call from an event handler to process a detected user navigation event on a web page,

wherein content navigation rules (CNRs) characterize nodes of a document-object-model (DOM) of the web page as a sequence of one or more logical paths through the web page when rendered by the computer, and wherein the CNRs are associated with respective augmented user interface (AUI) functionalities that are tailored to different types of users;

in response to receiving the call, requesting a user preference file from a remote server;

receiving, from the remote server, the user preference file and an AUI component API identified in the user preference file; and

in response to receiving the user preference file:

processing the detected user navigation event by:

identifying a CNR corresponding to the detected navigation event; and

calling, in the web browser, an AUI component application via the received AUI component API to invoke an AUI on the computer, the AUI having the respective AUI functionality associated with the identified CNR.

2. A non-transitory computer-readable storage medium comprising instructions operable to cause a programmable processor to:

provide an application programming interface running in a web browser on a computer to receive a call from an event handler to process a detected user navigation event on a web page,

wherein content navigation rules (CNRs) characterize nodes of a document-object-model (DOM) of the web page as a sequence of one or more logical paths through the web page when rendered by the computer, and wherein the CNRs are associated with respective augmented user interface (AUI) functionalities that are tailored to different types of users; and

in response to receiving the call, request a user preference file from a remote server;

receive, from the remote server, the user preference file and an AUI component API identified in the user preference file; and

in response to receiving the user preference file:

process the detected user navigation event by:

identifying a CNR corresponding to the detected navigation event; and

calling, in the web browser, an AUI component application via the received AUI component API in the web browser to invoke an AUI on the computer, the AUI having the respective AUI functionality associated with the identified CNR.

3. The method of claim 1 , wherein the received AUI component API provides the respective AUI functionality on the computer in conjunction with the AUI component application according to the user preference file.

4. The method of claim 3 , wherein the AUI component application includes at least one of a cloud-based AUI component application, a native AUI component application or a browser plug-in AUI component application.

5. The method of claim 1 , wherein the received AUI component API includes a browser plug-in.

6. The method of claim 1 , wherein the received AUI component API includes a target callable by the event handler to call the AUI component application.

7. The method of claim 1 , wherein the AUI component application includes one of a native screen reader, a native screen magnifier, a native speech recognizer, a browser plug-in version of a screen reader, a browser plug-in version of a screen magnifier, a browser plug-in version of a speech recognizer, a web based screen reader, a web based screen magnifier and a web based speech recognizer.

8. The non-transitory computer-readable storage medium of claim 2 , wherein the received AUI component API provides the respective AUI functionality on the computer in conjunction with the AUI component application according to the user preference file.

9. The non-transitory computer-readable storage medium of claim 8 , wherein the AUI component application includes at least one of a cloud-based AUI component application, a native AUI component application or a browser plug-in AUI component application.

10. The non-transitory computer-readable storage medium of claim 2 , wherein the received AUI component API includes a browser plug-in.

11. The non-transitory computer-readable storage medium of claim 2 , wherein the received AUI component API includes a target callable by the event handler to call the AUI component application.

12. The non-transitory computer-readable storage medium of claim 2 , wherein the AUI component application includes one of a native screen reader, a native screen magnifier, a native speech recognizer, a browser plug-in version of a screen reader, a browser plug-in version of a screen magnifier, a browser plug-in version of a speech recognizer, a web based screen reader, a web based screen magnifier and a web based speech recognizer.

Assignments (2)
CHANGE OF NAME Recorded Oct 5, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044129/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 24, 2010
From: GHARPURE, CHAITANYA; CHEN, CHARLES L; SHEARER, RACHEL; RAMAN, TIRUVILWAMALAI V
To: GOOGLE INC.
Reel/Frame 024589/0238 →
Continuity (1)
Related Publication 20110154212A1 · Jun 23, 2011