IP Library › Granted Patent US 12,010,014
Granted Patent B2
US 12,010,014 · App. 17/437,211 · Granted Jun 11, 2024

System and a method for routing traffic in an MPLS network

Inventors: Yuval Moshe (Ra'anana, IL); Tamir Gal (Nofit, IL); Alexander Gelberger (Ashdod, IL); Felix Weinstein (Even Yehuda, IL); Omri Nir (Kfar Saba, IL)
Assignee: DRIVENETS LTD.
H04L45/50
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 12,010,014
App. No.
17/437,211
Granted
Jun 11, 2024
Kind
B2
Abstract

A system and a method are provided for use in an MPLS network, wherein the system comprises at least one routing element configured to share one or more circuits among multiple Intermediate System to Intermediate System (IS-IS) routing protocol instances, wherein each of the multi instances is associated with a unique database, and wherein the at least one routing element comprises a managing entity configured to: manage a plurality of traffic engineering software agents each associated with a respective database, and allocate available resources to respective instances; update at least one of the plurality of databases; and for traffic that is about to be conveyed via a specific instance, determine a neighboring instance through which said traffic will be conveyed, based on information comprised in the database associated with the specific instance through which said traffic will be conveyed.

Claims (12)

1. A system for use in an MPLS network, said system comprising:

a) a routing element that shares one or more circuits among multiple Intermediate System to Intermediate System (IS-IS) routing protocol instances;

b) a plurality of routing protocol instances each of which is associated with a database from among a plurality of databases;

c) a managing entity that manages plurality of traffic engineering software agents, and dynamically selects a database from among the plurality of databases, to be associated with a traffic engineering software agent from among said plurality of the traffic engineering software agents, wherein said traffic engineering software agent conveys traffic along a path being currently used for conveying traffic, and wherein said selection of a database is made based on an ad hoc selection of a database from among the plurality of databases;

d) wherein said managing entity updates databases associated with respective routing protocol instances and based on that update, allocates available resources to routing protocol instances via which traffic is being conveyed; and

e) wherein said managing entity conveys traffic via a specific routing protocol instance, wherein said specific routing protocol instance is associated with the one or more databases currently selected from among the plurality of databases.

2. The system of claim 1 , wherein for traffic that is being conveyed via a specific routing protocol instance, said managing entity is further configured to determine a neighboring routing protocol instance through which said traffic will be conveyed, based on information comprised in the database associated with the specific routing protocol instance through which said traffic is being conveyed.

3. A method for use in an MPLS network by a managing entity comprises in a routing element, wherein said routing element is configured to share one or more circuits among multiple Intermediate System to Intermediate System (IS-IS) routing protocol instances, and wherein each of the routing protocol instances is dynamically associated with a database selected from among a plurality of databases, said method comprising the steps of:

managing a plurality of traffic engineering software agents, and to dynamically select a database from among the plurality of databases, to be associated with a traffic engineering software agent from among said plurality of the traffic engineering software agents, wherein said traffic engineering software agent is used for conveying traffic along a path being currently used for conveying traffic, and wherein said selection of a database is made based on an ad hoc selection of a database from among the plurality of databases,

updating databases associated with respective routing protocol instances and based on that update, to allocate available resources to routing protocol instances via which traffic is being conveyed; and

conveying traffic via a specific routing protocol instance, wherein said specific routing protocol instance is associated with the one or more databases currently selected from among the plurality of databases.

4. The method of claim 3 , wherein for traffic being conveyed via a specific routing protocol instance, the method comprises determining a neighboring routing protocol instance through which said traffic is being conveyed, based on information comprised in the database associated with the specific routing protocol instance through which said traffic is being conveyed.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 19, 2022
From: MOSHE, YUVAL; GAL, TAMIR; GELBERGER, ALEXANDER; WEINSTEIN, FELIX; NIR, OMRI
To: DRIVENETS LTD.
Reel/Frame 058690/0544 →
ASSIGNMENT OF 1% INTEREST Recorded Jan 19, 2022
From: DRIVENETS LTD.
To: AT&T SERVICES, INC.
Reel/Frame 058768/0158 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 19, 2022
From: AT&T SERVICES, INC.
To: DRIVENETS LTD.
Reel/Frame 058770/0581 →
Continuity (2)
Provisional Application 62816433 · Mar 11, 2019
Related Publication 20220174003A1 · Jun 2, 2022