Hashtag, deep link and linket for more user interactions

• US 10,042,946 B2
• Filed: 06/07/2016
• Issued: 08/07/2018
• Est. Priority Date: 06/07/2016
• Status: Active Grant

• Current Assignee: Wesley Boudville
• Original Assignee: Wesley Boudville
• Inventors: Boudville, Wesley John
• Primary Examiner(s): Dyer, Andrew R
• Application Number:
  US14/999,625
• Publication Number:
  US 20170351693A1
• Time in Patent Office: 791 Days
• Field of Search: 715205, 715206, 715208
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 40/134 Hyperlinking
• CPC Class Codes: G06F 40/169 Annotation, e.g. comment data or footnotes

Abstract

A mobile web page shows messages with a hashtag. The page shows deep links or linkets, related to the messages'"'"'s topic. If a user clicks a deep link or linket, an app is launched on the mobile device, connecting to a different device. The user interacts with a second user. The latter can be an instructor, teacher or observer. The first user can be a student. Similar steps are done for a page with an author'"'"'s username, where the page shows messages by the author and the messages have hashtags. This page has a linket ad. If the ad is by the author, she can promote herself or an item sold by her or an event where she will be playing. Increasing the chance that more people will click the linket and interact with her via the linket app.

Claims

1. A method consisting of a first mobile device interacting with a registry and a second mobile device;

where the first mobile device displays a page in a browser or app;

where the page came from a server;

where the page includes a hashtag, a first linket and a messages containing the hashtag;

where the first linket is clickable;

where the first linket is clicked;

where the first mobile device sends the first linket to the Registry;

where the first mobile device receives a deep link;

where the deep link has an id of an app;

where the deep link has a network address of a remote instance running on the second mobile device;

where the network address is not an URL (Universal Resource Locator);

where the network address does not contain an URL;

where a local instance of the app is run on the first mobile device;

where the local instance connects to the remote instance;

where the local instance interacts with the remote instance.