Method and system for a uniform resource identifier (URI) broker

Patent metadata

Field	Value
Publication number	US-10447797-B2
Application number	US-201514802274-A
Country	US
Kind code	B2
Filing date	Jul 17, 2015
Priority date	Jul 18, 2014
Publication date	Oct 15, 2019
Grant date	Oct 15, 2019

Abstract

A system provides the ability for developers to create and embed a URI in HTML, a document, or an application to invoke another application or functionality according to a URI scheme name. The invoked application does not natively react to URI selections. Rather, a URI Broker can redirect the URI selection to the desired application and conduct any pre-processing to allow the URI to invoke any application, even those that do not include URI capability.

First claim

What is claimed is:

1. A non-transitory computer readable medium comprising instructions stored in a non-transitory memory and executed by a processor of a user device, wherein the instructions cause the processor to execute a method for enabling a uniform resource identifier (URI), the instructions comprising:
instructions to receive a selection of the URI by a user on the user device, wherein the URI is embedded in an application executing on the user device;
instructions to intercept the selection of the URI with a URI Broker, wherein the URI Broker is executed by the processor;
instructions to redirect the URI based on a mapping in a data store stored on a server in communication with the user device through a network, wherein the data store comprises user preference data; and
instructions to launch functionality, by the URI Broker, based on the mapping, wherein the application does not natively execute the functionality based on the URI, wherein the functionality is based on the user preference data, and wherein the functionality is one of a web service, an application programming interface (API), and a second application.

2. The computer readable medium according to claim 1 , wherein the URI Broker is a second application executing on the user device.

3. The computer readable medium according to claim 2 , wherein the data store is associated with a server that is in communication with the user device through a network.

4. The computer readable medium according to claim 3 , wherein the URI is associated with a URI scheme and a first preference defined by a developer.

5. The computer readable medium according to claim 4 , wherein the URI scheme and the first preference are stored in the data store.

6. The computer readable medium according to claim 5 , the instructions further comprising:
instructions to retrieve the first preference from the data store; and
wherein the functionality is based in part on the first preference.

7. The computer readable medium according to claim 6 , wherein the user preference data overrides the first preference.

8. The computer readable medium according to claim 1 , wherein intercepting the selection of the URI comprises executing browser extension technology that intercepts webpage content.

9. A user device comprising:
a memory configured to store instructions to execute a URI Broker;
a processor in communication with the memory, wherein the processor retrieves the instructions from the memory and executes the URI Broker based on the instructions, wherein, when executing the URI Broker, the processor is configured to:
receive a selection of the URI by a user on the user device, wherein the URI is embedded in an application executing on the user device;
intercept the selection of the URI with a URI Broker, wherein the URI Broker is executed by the processor;
redirect the URI based on a mapping in a data store stored on a server in communication with the user device through a network, wherein the data store comprises user preference data; and
launch functionality, by the URI Broker, based on the mapping, wherein the application does not natively execute the functionality based on the URI, wherein the functionality is based on the user preference data, and wherein the functionality is one of a web service, an application programming interface (API), and a second application.

10. The device according to claim 9 , wherein the processor is further configured to:
retrieve a first preference from the data store, wherein the URI is associated with a URI scheme and the first preference defined by a developer, wherein the first preference defines which functionality the developer desires for the URI; and
wherein the functionality is based on at least one of the user preference and the first preference.

11. The device according to claim 10 , wherein the user preference data overrides the first preference.

Assignees

• Avaya Inc

Inventors

• Dingwall Bryan
• Vlasenko Sergey
• Nezarati Mohammad

Classifications

• G06F16/955

  using information identifiers, e.g. uniform resource locators [URL] · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L41/0293

  for accessing web services by means of a binding identification of the management service or element · CPC title

• H04L67/306

  User profiles · CPC title

• G06F9/44526

  Plug-ins; Add-ons · CPC title