IP Library Granted Patent US 11,646,993
Granted Patent B2
US 11,646,993 · App. 16/467,427 · Granted May 9, 2023

System and method to register FQDN-based IP service endpoints at network attachment points

Inventors: Sebastian Robitzsch (London, GB); Dirk Trossen (London, GB)
Assignee: INTERDIGITAL PATENT HOLDINGS, INC.
H04L61/4511H04L61/5076H04L65/1016H04L67/02H04L67/568
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,646,993
App. No.
16/467,427
Granted
May 9, 2023
Kind
B2
Abstract

System and methods are described to register FQDN-based IP service endpoints at network attachment points. One embodiment takes the form of a method comprising: receiving, at a server-side network access point (sNAP) in an information-centric network (ICN), a registration request including a first fully qualified domain name (FQDN), a port, a transport protocol, and a service name of an IP server; publishing, at the sNAP, the port, the transport protocol, and the service name to a first content identifier (CID); and subscribing, at the sNAP, to a second CID that is based on the FQDN.

Claims (50)

1. A method comprising:

receiving, at a server-side network access point (sNAP) in an information-centric network (ICN), a registration request including a first fully qualified domain name (FQDN), a port, a transport protocol, and a service name of an IP server;

publishing, at the sNAP, the port, the transport protocol, and the service name to a first content identifier (CID),

wherein the first content identifier is a dedicated registration namespace of the ICN; and

subscribing, at the sNAP, to a second CID that is based on the FQDN,

wherein the first CID and the second CID are used to match respectively the sNAP and a client-side network access point (cNAP), and to calculate respectively a first path among the sNAP and the cNAP and a second path among the sNAP and a second cNAP.

2. The method of claim 1 , further comprising:

generating, at the sNAP, a feedback message indicating a successful registration; and

outputting, from the sNAP, the feedback message.

3. The method of claim 2 , wherein outputting, from the sNAP, the feedback message comprises broadcasting the feedback message.

4. The method of claim 1 , further comprising transmitting, from the sNAP to the client-side network access point (cNAP) in the ICN, the port, the transport protocol, and the service name.

5. The method of claim 4 , wherein the cNAP is subscribed to the first content identifier.

6. The method of claim 1 , wherein the registration request further includes an IP address of the IP server.

7. The method of claim 6 , further comprising:

transmitting, from the sNAP, the IP address and the FQDN to a domain name service (DNS) server associated with the ICN.

8. The method of claim 6 , further comprising adding the FQDN, the port, the transport protocol, the service name, and the IP address of the IP server to a database of the sNAP.

9. The method of claim 1 , further comprising:

receiving, at the sNAP, a deregistration request including the FQDN, the transport protocol, and the service name;

verifying, at the sNAP, the deregistration request;

deleting, at the sNAP, a database entry associated with the deregistration request; and

terminating an existing IP session towards the IP server.

10. The method of claim 1 , further comprising:

receiving, at the sNAP, a second registration request including the FQDN;

checking whether the FQDN is already registered; and

in response to the FQDN being already registered, transmitting, from the sNAP, a registration error response.

11. The method of claim 1 , further comprising:

receiving, at the sNAP via the subscription to the second content identifier, a first ICN packet encapsulating an HTTP request directed to the FQDN; and

responsively transmitting, from the sNAP to the IP server, the HTTP request.

12. The method of claim 11 , further comprising:

in response to transmitting the HTTP request to the IP server, receiving, at the sNAP, an HTTP response from the IP server;

encapsulating, at the sNAP, the HTTP response in a second ICN packet; and

publishing, at the sNAP, the second ICN packet to a third CID.

13. The method of claim 1 , further comprising:

receiving, at the sNAP, an update message indicating an update to an existing FQDN registration corresponding to the IP server;

updating, at the sNAP, the existing FQDN registration based on the update message;

transmitting, from the sNAP, an update acknowledgment message; and

terminating a session towards the IP server.

14. The method of claim 1 , further comprising establishing a communication socket between the sNAP and the IP server based on the port.

15. A server-side network access point (sNAP) for an information-centric network (ICN) comprising:

a processor; and

a computer-readable storage medium storing instructions operative, when executed by the processor, to cause the processor to:

receive, at a server-side network access point (sNAP) in an information-centric network (ICN), a registration request including a first fully qualified domain name (FQDN), a port, a transport protocol, and a service name of an IP server;

publish, at the sNAP, the port, the transport protocol, and the service name to a first content identifier (CID),

wherein the first content identifier is a dedicated registration namespace of the ICN; and

subscribe, at the sNAP, to a second CID that is based on the FQDN,

wherein the first CID and the second CID are used to match respectively the sNAP and a client-side network access point (cNAP), and to calculate respectively a first path among the sNAP and the cNAP and a second path among the sNAP and a second cNAP.

16. The sNAP of claim 15 , wherein the registration request further includes an IP address of the IP server.

17. The sNAP of claim 16 , wherein the functions further comprise:

transmitting, from the sNAP, the IP address and the FQDN to a domain name service (DNS) server associated with the ICN.

18. The sNAP of claim 16 , wherein the functions further comprise adding the FQDN, the port, the transport protocol, the service name, and the IP address of the IP server to a database of the sNAP.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 5, 2023
From: IDAC HOLDINGS, INC.
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 062308/0215 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 15, 2019
From: ROBITZSCH, SEBASTIAN; TROSSEN, DIRK
To: IDAC HOLDINGS, INC.
Reel/Frame 050721/0708 →
Continuity (2)
Provisional Application 62434181 · Dec 14, 2016
Related Publication 20200076764A1 · Mar 5, 2020