US2019075150A1PendingUtilityA1

Hosting provider hosting routes from a media repository

52
Assignee: GO DADDY OPERATING CO LLCPriority: Mar 22, 2016Filed: Oct 30, 2018Published: Mar 7, 2019
Est. expiryMar 22, 2036(~9.7 yrs left)· nominal 20-yr term from priority
Inventors:Samuel Ng
H04L 63/00H04L 67/02H04L 67/2814H04L 61/302G06F 21/00H04L 61/1511H04L 67/563G06F 21/31H04L 63/0227H04L 61/4511H04L 63/08G06F 21/10
52
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A hosting provider may be bi-directionally authenticated with one or more media repositories. The hosting provider preferably has domain name registration and hosting capabilities. The media repositories may collect data (such as pictures and/or files) from one or more users. Once authenticated, the hosting provider and media repositories may cooperate in storing, aggregating and transmitting data to a user. Routes may be hosted by the hosting provider and used to organize and access the data. For example, a user may enter a route into a browser and receive media/data, possibly from a plurality of media repositories, that is associated with that route. In another example, the user may enter a route into the browser and be redirected from the hosting provider to a website of the media repository.

Claims

exact text as granted — not AI-modified
The invention claimed is: 
     
         1 . A method, comprising:
 receiving by a hosting provider a plurality of routes from a media repository comprising a hardware server, wherein each route in the plurality of routes comprises a root, wherein the root is stored in a name server and includes a third level domain combined with a domain name registered to a user; and   storing by the hosting provider on a hardware server the plurality of routes from the media repository with the root.   
     
     
         2 . The method of  claim 1 , wherein at least one route in the plurality of routes is a uniform resource locator redirect. 
     
     
         3 . The method of  claim 1 , wherein at least one route in the plurality of routes points to data in a database. 
     
     
         4 . The method of  claim 1 , wherein at least one route in the plurality of routes comprises a redirect to a website of the media repository. 
     
     
         5 . The method of  claim 1 , further comprising the steps of:
 receiving by the hosting provider a second plurality of routes from a second media repository, wherein each route in the second plurality of routes comprises the root; and   storing by the hosting provider on the hardware server the second plurality of routes from the second media repository with the root, wherein the media repository is a different service from the second media repository.   
     
     
         6 . The method of  claim 1 , wherein at least one route in the plurality of routes comprises the root and a user applied tag, wherein the user applied tag was applied by the user while logged into the media repository. 
     
     
         7 . The method of  claim 1 , wherein at least one route in the plurality of routes comprises the root and a user applied filter, wherein the user applied filter was applied by the user while logged into the media repository. 
     
     
         8 . A method, comprising:
 receiving by a hosting provider a route selected from a plurality of routes, wherein the route is a first uniform resource locator, from a browser running on a client device, wherein the first uniform resource locator is associated with a second uniform resource locator, the plurality of routes are received from a media repository and each route in the plurality of routes includes a root, the root includes a third level domain combined with a domain name registered to a user, and the root is stored in a nameserver that is part of a domain name system; and   redirecting by the hosting provider the browser on the client device to the second uniform resource locator.   
     
     
         9 . The method of  claim 8 , wherein at least one route in the plurality of routes points to data in a database. 
     
     
         10 . The method of  claim 8 , further comprising the step of:
 storing by the hosting provider the second uniform resource locator and a corresponding IP address that points to a website of the media repository in the domain name system.   
     
     
         11 . The method of  claim 8 , wherein at least one route in the plurality of routes comprises the root and a user applied tag, wherein the user applied tag was applied by the user while logged into the media repository. 
     
     
         12 . The method of  claim 8 , wherein at least one route in the plurality of routes comprises the root and a user applied filter, wherein the user applied filter was applied by the user while logged into the media repository. 
     
     
         13 . The method of  claim 8 , further comprising the steps of:
 receiving by the hosting provider a second plurality of routes from a second media repository, wherein each route in the second plurality of routes comprises the root; and   storing by the hosting provider on a hardware server the second plurality of routes from the second media repository with the root, wherein the media repository is a different media repository than the second media repository.   
     
     
         14 . A method of transmitting aggregated data, comprising the steps of:
 receiving by a hosting provider a first route from a first media repository, wherein the first route comprises a root and the first route points to a first data, wherein the root includes a third level domain combined with a domain name registered to a user;   storing by the hosting provider on a hardware server the first route from the first media repository with the root;   receiving by the hosting provider a second route from a second media repository, wherein the second route comprises the root and the second route points to a second data and wherein the first route comprises a tag and the second route comprises the tag;   storing by the hosting provider on the hardware server the second route from the second media repository with the root;   receiving by the hosting provider the tag from a browser running on a client device; and   transmitting by the hosting provider the first data and the second data to the browser running on the client device.   
     
     
         15 . The method of  claim 14 , further comprising the step of:
 receiving by the hosting provider a third route from the first media repository comprising a redirect to a website of the first media repository.   
     
     
         16 . The method of  claim 14 , wherein the tag was applied by the user while logged into the first media repository. 
     
     
         17 . The method of  claim 14 , further comprising the step of:
 receiving by the hosting provider a third route from the first media repository comprising a user applied filter and wherein the user applied filter was applied by the user while logged into the first media repository.   
     
     
         18 . The method of  claim 14 , further comprising the steps of:
 receiving by the hosting provider a plurality of routes from a plurality of media repositories, wherein each route in the plurality of routes comprises the tag and wherein the plurality of routes point to a corresponding plurality of data stored in a database;   receiving by the hosting provider the tag from the browser running on the client device; and   transmitting the plurality of data pointed to by the plurality of routes that comprise the tag to the browser running on the client device.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.