IP Library Granted Patent US 11,546,446
Granted Patent B2
US 11,546,446 · App. 17/248,423 · Granted Jan 3, 2023

System and method for facilitating routing

Inventor: Armand Prieditis (Arcata, CA)
Assignee: Security Services, LLC
H04L67/568H04L67/63H04L61/30
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 11,546,446
App. No.
17/248,423
Granted
Jan 3, 2023
Kind
B2
Abstract

A system and method are provided for routing content requests. On a given server network, content requests comprising a character string may be routed up a hierarchical network topology until a linear chain, corresponding to the character string, is identified. Thus, the content request is forwarded up the hierarchy until an intersecting server network is reached. Then the content request is forwarded down the hierarchy until, along a published linear chain corresponding to the character string, until a content source is reached. Content is provided to the requestor along a reverse path of the content request.

Claims (45)

1. A regional server for routing content requests, the regional server included in a present server network of a plurality of server networks of a present hierarchical level, the present hierarchical level being one of a plurality of hierarchical levels of a region-based hierarchical network, the regional server comprising:

one or more processors; and

one or more memory resources storing instructions that, when executed by the one or more processors, cause the regional server to:

parse a character string associated with a content request originating from an end user, the character string identifying content to be accessed by the end user;

identify linear chain data for the content identified by the character string based at least in part on the parsing, the linear chain data specifying a content source for the content identified by the character string;

route the content request to a second server based at least in part on the linear chain data;

receive the content identified in the content request from the second server;

store the received content in a cache associated with the regional server; and

provide the received content to a third server in a lower hierarchal level of the region-based hierarchical network.

2. The regional server of claim 1 , wherein the executed instructions further cause the regional server to:

determine whether the content is directly linked to a respective server in the present server network, the present server network representing a specified geographic region, wherein determining that the content is directly linked to the respective server of the present server network corresponds to the linear chain data intersecting with the present server network.

3. The regional server of claim 1 , wherein the second server is a server in a higher hierarchal level of the region-based hierarchical network.

4. The regional server of claim 1 , wherein the executed instructions further cause the regional server to:

log an entry corresponding to the content request in a pending interest table of the regional server; and

amend or delete the entry in the pending interest table.

5. The regional server of claim 4 , wherein the entry indicates one or more servers from which the content request was received.

6. The regional server of claim 5 , wherein the third server is specified in the logged entry, and wherein the executed instructions further cause the regional server to determine the third server based at least in part on the logged entry.

7. The regional server of claim 1 , wherein the second server is a server in the present hierarchal level of the region-based hierarchical network.

8. The regional server of claim 1 , wherein the character string is published in the linear chain data through the plurality of hierarchical levels of the region-based hierarchical network.

9. The regional server of claim 1 , wherein the executed instructions further cause the regional server to determine that the content source is directly linked to the regional server based at least in part on the linear chain data.

10. The regional server of claim 9 , wherein the linear chain data intersects the present hierarchal level at the regional server.

11. A method for routing content requests by a regional server included in a present one of a number of server networks of a present hierarchical level, the present hierarchical level being one of a plurality of hierarchical levels of a region-based hierarchical network, the method comprising:

parsing, by the regional server, a character string associated with a content request originating from an end user, the character string identifying content to be accessed by the end user;

identifying, by the regional server, linear chain data for the content identified by the character string based at least in part on the parsing, the linear chain data specifying a content source for the content identified by the character string;

routing, by the regional server, the content request to a second server based at least in part on the linear chain data;

receiving, by the regional server, the content identified in the content request from the second server;

storing, by the regional server, the received content in a cache associated with the regional server; and

providing, by the regional server, the received content to a third server in a lower hierarchal level of the region-based hierarchical network.

12. The method of claim 11 , further comprising determining whether the content is directly linked to a respective server in the present server network, the present server network representing a specified geographic region, wherein determining that the content is directly linked to the respective server of the present server network corresponds to a linear chain intersecting with the present server network.

13. The method of claim 11 , wherein the second server is a server in a higher hierarchal level of the region-based hierarchical network.

14. The method of claim 11 , further comprising:

logging, by the regional server, an entry corresponding to the content request in a pending interest table of the regional server; and

based on forwarding the content to the end user, amending or deleting, by the regional server, the entry in the pending interest table.

15. The method of claim 14 , wherein the entry indicates one or more servers from which the content request was received.

16. The method of claim 15 , wherein the third server is specified in the logged entry, and wherein the method further comprises determining, by the regional server, the third server based at least in part on the logged entry.

17. A non-transitory computer readable medium storing instructions executable by one or more processors of a regional server in a present one of a plurality of server networks of a present hierarchical level, the present hierarchical level being one of a plurality of hierarchical levels of a region-based hierarchical network, wherein the instructions, when executed by the one or more processors, cause the regional server to:

parse a character string associated with a content request originating from an end user, the character string identifying content to be accessed by the end user;

identify linear chain data for the content identified by the character string based at least in part on the parsing, the linear chain data specifying a content source for the content identified by the character string;

route the content request to a second server based at least in part on the linear chain data;

receive the content identified in the content request from the second server;

store the received content in a cache associated with the regional server; and

provide the received content to a third server in a lower hierarchal level of the region-based hierarchical network.

18. The non-transitory computer readable medium of claim 17 , wherein the second server is a server in a higher hierarchal level of the region-based hierarchical network.

19. The non-transitory computer readable medium of claim 17 , wherein the second server is a server in the present hierarchal level of the region-based hierarchical network.

20. The non-transitory computer readable medium of claim 17 , wherein the instructions, when executed by the one or more processors, further cause the regional server to access the content from the cache in response to receiving a second content request for the content.

Assignments (9)
FIRST LIEN INTELLECTUAL PROPERTY AGREEMENT SUPPLEMENT Recorded Sep 24, 2025
From: DIGICERT, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT
Reel/Frame 072947/0203 →
ASSIGNMENT OF SECURITY INTERESTS IN INTELLECTUAL PROPERTY (FIRST LIEN), RECORDED ON JANUARY 23, 2025 AT REEL 069991 FRAME 0390 Recorded Sep 24, 2025
From: UBS AG, STAMFORD BRANCH, AS RESIGNING AGENT
To: HPS INVESTMENT PARTNERS, LLC, AS SUCCESSOR AGENT
Reel/Frame 072928/0289 →
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 30, 2025
From: DIGICERT, INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 072295/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2025
From: VERCARA, LLC
To: DIGICERT, INC.
Reel/Frame 071781/0348 →
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jan 23, 2025
From: VERCARA, LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 069991/0330 →
FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jan 23, 2025
From: VERCARA, LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 069991/0390 →
CHANGE OF NAME Recorded Mar 21, 2024
From: SECURITY SERVICES, LLC
To: VERCARA, LLC
Reel/Frame 066867/0462 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 19, 2021
From: PRIEDITIS, ARMAND
To: NEUSTAR, INC.
Reel/Frame 058166/0705 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2021
From: NEUSTAR, INC.
To: SECURITY SERVICES, LLC
Reel/Frame 057327/0418 →
Continuity (5)
Continuation 16293495 · Mar 5, 2019
Continuation 15463107 · Mar 20, 2017
Continuation 14534443 · Nov 6, 2014
Provisional Application 61900739 · Nov 6, 2013
Related Publication 20210400120A1 · Dec 23, 2021