Using UDP port numbers for service delimiting, such as for delimiting virtual routing and forwarding instances in layer 3 tunnels

Patent metadata

Field	Value
Publication number	US-12568047-B2
Application number	US-202318372088-A
Country	US
Kind code	B2
Filing date	Sep 23, 2023
Priority date	Jun 28, 2023
Publication date	Mar 3, 2026
Grant date	Mar 3, 2026

Abstract

Different services through Virtual Routing and Forwarding instances (VRFs) are identified without needing a Multiprotocol Label Switching (MPLS) label or a Virtual Extensible Local Area Network (VXLAN) Network Identifier (VNI) by using, for example, different UDP port numbers to identify different connectivity services (e.g., customers, VRFs) when IP-in-IP (also referred to as IP over UDP) is used as a tunneling mechanism (e.g., in the data center).

First claim

What is claimed is:

1 . A computer-implemented method comprising:
a) allocating, by a network device at the egress of an Internet Protocol (IP) over User Datagram Protocol (UDP) tunnel and belonging to a shared network, (1) a UDP destination port value for the IP over UDP tunnel to (2) a unique instance of a private connectivity service; b) associating, by the network device at the egress of the IP over UDP tunnel, a forwarding table for the unique instance of the private connectivity service and the UDP destination port value; and c) advertising, by the network device at the egress of the IP over UDP tunnel to a network device at the ingress of the IP over UDP tunnel and belonging to the shared network, information associating (1) the UDP destination port value for the IP over UDP tunnel to (2) the unique instance of a private connectivity service, wherein the advertisement is included in a Border Gateway Protocol (BGP) message, and wherein the unique instance of a private connectivity service is a virtual router and forwarder (VRF) instance.

2 . The computer implemented method of claim 1 , wherein the act of allocating is based on a manual, user input.

3 . The computer-implemented method of claim 1 , wherein the act of allocating is performed automatically, using an available and unallocated UDP destination port value.

4 . The computer-implemented method of claim 3 , wherein the act of allocating is performed dynamically, using either (A) a UDP-port-allocation library on the network device, or (B) a software-based management utility external to the network device.

5 . The computer-implemented method of claim 1 , wherein the information associating (1) the UDP destination port value for the IP over UDP tunnel to (2) the unique instance of a private connectivity service is advertised through at least one service route belonging to the unique instance of the private connectivity service.

6 . The computer-implemented method of claim 1 wherein the advertisement is included in a tunnel encapsulation attribute (TEA) type-length value (TLV).

7 . The computer-implemented method of claim 1 wherein the advertisement is included in an Address Family Identifier (AFI) and a Subsequent Address Family Identifier (SAFI).

8 . The computer-implemented method of claim 1 , further comprising:
d) receiving, by the network device at the ingress of the IP over UDP tunnel, an IP packet associated with the unique instance of the private connectivity service; e) encapsulating, by the network device at the ingress of the IP over UDP tunnel, the IP packet with an IP over UDP header to generate an IP-in-IP packet having (1) a UDP destination port field populated with the UDP destination port value, and (2) an IP destination field populated with an IP address of the network device at the egress of the IP over UDP tunnel; and f) transmitting, by the network device at the ingress of the IP over UDP tunnel, the IP-in-IP packet.

9 . The computer-implemented method of claim 8 , further comprising:
g) receiving, by the network device at the egress of the IP over UDP tunnel, the IP-in-IP packet; h) decapsulating, by the network device at the egress of the IP over UDP tunnel, the IP-in-IP packet to expose the IP packet; i) selecting, by the network device at the egress of the IP over UDP tunnel, one of a plurality of forwarding tables using a UDP destination port value in the received IP-in-IP packet; and j) forwarding, by the network device at the egress of the IP over UDP tunnel, the IP packet using the one of the plurality of forwarding tables selected.

10 . The computer-implemented method of claim 1 , further comprising:
d) receiving, by the network device at the egress of the IP over UDP tunnel, an IP-in-IP packet; e) decapsulating, by the network device at the egress of the IP over UDP tunnel, the IP-in-IP packet to expose an IP packet; f) selecting, by the network device at the egress of the IP over UDP tunnel, one of a plurality of forwarding tables using a UDP destination port value in the received IP-in-IP packet; and g) forwarding, by the network device at the egress of the IP over UDP tunnel, the IP packet using the one of the plurality of forwarding tables selected.

11 . The computer-implemented method of claim 1 , further comprising:
d) allocating, by the network device at the egress of a second IP over UDP tunnel, (1) a second UDP destination port value for the IP over UDP tunnel to (2) a second unique instance of a private connectivity service; and e) associating, by the network device at the egress of the second IP over UDP tunnel, a second forwarding table for the second unique instance of the private connectivity service and the second UDP destination port value.

12 . The computer-implemented method of claim 11 , wherein the second unique instance of a private connectivity service is a second virtual router and forwarder (VRF) instance.

13 . A system comprising:
a first network device at an egress of an Internet Protocol (IP) over User Datagram Protocol (UDP) tunnel and belonging to a shared network, the network device at the egress of the IP over UDP tunnel including:
a) at least one processor; and
b) a non-transitory computer-readable storage medium storing processor-executable instructions, which, when executed by the at least one processor, cause the at least one processor to perform a method of
1) allocating, by the first network device, (i) a UDP destination port value for the IP over UDP tunnel to (ii) a unique instance of a private connectivity service;
2) associating, by the first network device, a forwarding table for the unique instance of the private connectivity service and the UDP destination port value; and
3) advertising, by the network device at the egress of the IP over UDP tunnel to a network device at the ingress of the IP over UDP tunnel and belonging to the shared network, information associating (i) the UDP destination port value for the IP over UDP tunnel to (i) the unique instance of a private connectivity service, wherein the advertisement is included in a Border Gateway Protocol (BGP) message, and
wherein the unique instance of a private connectivity service is a virtual router and forwarder (VRF) instance.

14 . The system of claim 13 , further comprising:
a second network device at an ingress of the IP over UDP tunnel and belonging to the shared network,
wherein the method performed by the first network further includes:
3) advertising, by the first network device to the second network device, information associating (i) the UDP destination port value for the IP over UDP tunnel to (ii) the unique instance of a private connectivity service.

15 . The system of claim 14 , wherein the second network device includes
a) at least one processor; and b) a non-transitory computer-readable storage medium storing processor-executable instructions, which, when executed by the at least one processor of the second network device, cause the at least one processor of the second network device to perform a method of
1) receiving, by the second network device, an IP packet associated with the unique instance of the private connectivity service;
2) encapsulating, by the second network device, the IP packet with an IP over UDP header to generate an IP-in-IP packet having (i) a UDP destination port field populated with the UDP destination port value, and (ii) an IP destination field populated with an IP address of the network device at the egress of the IP over UDP tunnel; and
3) transmitting, by the second network device, the IP-in-IP packet.

Assignees

• Juniper Networks Inc

Inventors

• Lin Wen
• Wang Kevin
• Kompella Kireeti

Classifications

• H04L45/586

  of virtual routers · CPC title

• H04L45/02

  Topology update or discovery · CPC title

• H04L69/22

  Parsing or analysis of headers · CPC title

• H04L45/025

  Updating only a limited number of routers, e.g. fish-eye update · CPC title

• H04L63/0272

  Virtual private networks · CPC title