IP Library Granted Patent US 12,375,367
Granted Patent B2
US 12,375,367 · App. 18/519,766 · Granted Jul 29, 2025

Configuration of EVPN topologies using a user interface

Inventors: Jason Sun Woan (Playa Vista, CA); Abhiram Madhugiri Shamsundar (San Jose, CA); Bo-Chieh Yang (San Jose, CA)
Assignee: Juniper Networks, Inc.
H04L41/22H04L12/4641H04L41/12
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,375,367
App. No.
18/519,766
Granted
Jul 29, 2025
Kind
B2
Abstract

Techniques are described by which a network management system (NMS) provides a common user interface (UI) to enable a user to collectively configure network devices to establish an EVPN topology. For example, an NMS is configured to: generate data representative of a common UI comprising UI elements representing a plurality of network devices to be configured in an EVPN topology; receive, via the common UI, an indication of a user input selecting one or more of the UI elements representing selected network devices; generate UI elements representing a plurality of ports of the selected network devices; receive, via the common UI, an indication of a user input selecting the UI elements representing one or more selected ports; and generate, based on the one or more selected network devices and one or more selected ports, topology relationship information of the one or more selected devices to establish the EVPN topology.

Claims (40)

1. A network management system comprising:

one or more processors; and

a memory comprising instructions that when executed by the one or more processors cause the one or more processors to:

generate data to output for display, the data representative of user interface (UI) elements representing one or more types of network topologies configured to extend a first layer network through a second layer network and representing one or more connections of one or more network devices to be configured in a network topology of the one or more types of network topologies;

receive an indication of at least one selected connection of the one or more network devices and of a selected type of network topology; and

generate, based on the at least one selected connection of the one or more network devices and the selected type of network topology, topology relationship information of the one or more network devices to establish the network topology.

2. The network management system of claim 1 , wherein the one or more types of network topologies comprise at least one of an Ethernet Virtual Private Network (EVPN) multihoming topology or an IP-CLOS topology.

3. The network management system of claim 1 , wherein to generate data to output for display, the one or more processors are further configured to:

obtain information of the one or more network devices via an application programming interface (API).

4. The network management system of claim 1 , wherein to generate the topology relationship information, the one or more processors are further configured to:

execute an application programming interface (API) request to create or update one or more API resources specifying the topology relationship information.

5. The network management system of claim 4 , wherein the one or more API resources specifying the topology relationship information comprise at least one of an API resource specifying one or more network settings of the network topology, an API resource specifying configuration information for the at least one selected connection of the one or more network devices, or an API resource specifying topology relationship information of each of the one or more network devices of the network topology.

6. The network management system of claim 1 , wherein the topology relationship information is used to generate configuration information for each of the one or more network devices to establish the network topology.

7. The network management system of claim 1 , wherein to generate topology relationship information, the one or more processors are further configured to:

generate an Ethernet segment identifier link aggregation group (ESI-LAG) for the at least one selected connection of the one or more network devices.

8. The network management system of claim 1 , wherein to generate topology relationship information, the one or more processors are further configured to:

generate an IP address for one or more VLANs for the network topology.

9. The network management system of claim 1 , wherein the one or more processors are further configured to:

validate whether the at least one selected connection of the one or more network devices is usable to establish the network topology.

10. A method comprising:

generating, by one or more processors of a network management system, data to output for display, the data representative of user interface (UI) elements representing one or more types of network topologies configured to extend a first layer network through a second layer network and representing one or more connections of one or more network devices to be configured in a network topology of the one or more types of network topologies;

receiving an indication of at least one selected connection of the one or more network devices and of a selected type of network topology; and

generating, by the network management system, based on the at least one selected connection of the one or more network devices and the selected type of network topology, topology relationship information of the one or more network devices to establish the network topology.

11. The method of claim 10 , wherein the one or more types of network topologies comprise at least one of an Ethernet Virtual Private Network (EVPN) multihoming topology or an IP-CLOS topology.

12. The method of claim 10 , wherein generating data to output for display comprises:

obtaining, by the network management system, information of the one or more network devices via an application programming interface (API).

13. The method of claim 10 , wherein generating the topology relationship information comprises:

executing, by the network management system, an application programming interface (API) request to create or update one or more API resources specifying the topology relationship information.

14. The method of claim 13 , wherein the one or more API resources specifying the topology relationship information comprises at least one of an API resource specifying one or more network settings of the network topology, an API resource specifying configuration information for the at least one selected connection of the one or more network devices, or an API resource specifying topology relationship information of each of the one or more network devices of the network topology.

15. The method of claim 10 , wherein the topology relationship information is used to generate configuration information for each of the one or more network devices to establish the network topology.

16. The method of claim 10 , wherein generating topology relationship information comprises:

generating an Ethernet segment identifier link aggregation group (ESI-LAG) for the at least one selected connection of the one or more network devices.

17. The method of claim 10 , wherein generating topology relationship information comprises:

generating an IP address for one or more VLANs for the network topology.

18. The method of claim 10 , further comprising:

validating, by the network management system, whether the at least one selected connection of the one or more network devices is usable to establish the network topology.

19. Non-transitory computer-readable storage media comprising instructions that, when executed, configure processing circuitry to:

generate data to output for display, the data representative of user interface (UI) elements representing one or more types of network topologies configured to extend a first layer network through a second layer network and representing one or more connections of one or more network devices to be configured in a network topology of the one or more types of network topologies;

receive an indication of at least one selected connection of the one or more network devices and of a selected type of network topology; and

generate, based on the at least one selected connection of the one or more network devices and the selected type of network topology, topology relationship information of the one or more network devices to establish the network topology.

Assignments (2)
NUNC PRO TUNC ASSIGNMENT Recorded May 6, 2026
From: JUNIPER NETWORKS, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 075513/0034 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 29, 2025
From: WOAN, JASON SUN; SHAMSUNDAR, ABHIRAM MADHUGIRI; YANG, BO-CHIEH
To: JUNIPER NETWORKS, INC.
Reel/Frame 072750/0700 →
Continuity (4)
Continuation 17932980 · Sep 16, 2022
Continuation 17644979 · Dec 17, 2021
Provisional Application 63243491 · Sep 13, 2021
Related Publication 20240205102A1 · Jun 20, 2024
References Cited (54)
US 6223218B1 · Iijima et al. · 2001 [cited by applicant]
US 7450505B2 · Buchanan · 2008 [cited by examiner]
US 8892696B1 · Thai · 2014 [cited by applicant]
US 9729439B2 · MeLampy et al. · 2017 [cited by applicant]
US 9729682B2 · Kumar et al. · 2017 [cited by applicant]
US 9762485B2 · Kaplan et al. · 2017 [cited by applicant]
US 9832082B2 · Dade et al. · 2017 [cited by applicant]
US 9871748B2 · Gosselin et al. · 2018 [cited by applicant]
US 9985883B2 · MeLampy et al. · 2018 [cited by applicant]
US 10142239B2 · Nagarajan et al. · 2018 [cited by applicant]
US 10200264B2 · Menon et al. · 2019 [cited by applicant]
US 10205638B1 · Angrish · 2019 [cited by examiner]
US 10277506B2 · Timmons et al. · 2019 [cited by applicant]
US 10432522B2 · Kaplan et al. · 2019 [cited by applicant]
US 10708125B1 · Chen · 2020 [cited by examiner]
US 10797987B1 · Beacham · 2020 [cited by applicant]
US 10862742B2 · Singh · 2020 [cited by applicant]
US 10958537B2 · Safavi · 2021 [cited by applicant]
US 10958585B2 · Safavi · 2021 [cited by applicant]
US 10985969B2 · Safavi · 2021 [cited by applicant]
US 11115272B1 · Kumar · 2021 [cited by examiner]
US 11323326B2 · Kommula · 2022 [cited by examiner]
US 11451449B1 · Woan et al. · 2022 [cited by applicant]
US 11743151B2 · Safavi · 2023 [cited by applicant]
US 11831519B2 · Woan et al. · 2023 [cited by applicant]
US 12010004B2 · Gao · 2024 [cited by examiner]
US 20020186664A1 · Gibson · 2002 [cited by examiner]
US 20050091361A1 · Bernstein · 2005 [cited by examiner]
US 20060184998A1 · Smith · 2006 [cited by examiner]
US 20070199066A1 · Smith · 2007 [cited by examiner]
US 20090328192A1 · Yang · 2009 [cited by examiner]
US 20140201642A1 · Vicat-Blanc · 2014 [cited by applicant]
US 20150256413A1 · Du et al. · 2015 [cited by applicant]
US 20160191314A1 · Russell et al. · 2016 [cited by applicant]
US 20160301577A1 · Lane · 2016 [cited by applicant]
US 20180077047A1 · Srinivasan et al. · 2018 [cited by applicant]
US 20180183663A1 · Teeter et al. · 2018 [cited by applicant]
US 20190104091A1 · Hooda · 2019 [cited by examiner]
US 20190199597A1 · Valisammagari · 2019 [cited by examiner]
US 20200067812A1 · Malhotra · 2020 [cited by examiner]
US 20200280495A1 · Sarbin · 2020 [cited by examiner]
US 20200396181A1 · Lochhead et al. · 2020 [cited by applicant]
US 20200403890A1 · McCulley et al. · 2020 [cited by applicant]
US 20210226848A1 · Kommula · 2021 [cited by examiner]
US 20210306201A1 · Wang et al. · 2021 [cited by applicant]
CN 108512739B · 2021 [cited by applicant]
CN 113452551A · 2021 [cited by applicant]
Sajassi, A., et al. “RFC 7209: Requirements for Ethernet VPN (EVPN).” (2014). [cited by examiner]
Extended Search Report from counterpart European Application No. 22194654.4 dated Dec. 23, 2022, 10 pp. [cited by applicant]
George, Dr A. Shaj I, and AS Hovan George. “A Brief Overview of VXLAN EVPN.” Ijireeiceinternational Journal of Innovative Research in Electrical, Electronics, Instrumentation and Control Engineering 9.7 (2021): 1-12. [cited by applicant]
Notice of Allowance from U.S. Appl. No. 17/644,979, dated May 26, 2022, 9 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/932,980, now issued U.S. Pat. No. 11,831,519, dated Dec. 5, 2022 through Oct. 25, 2023, 26 pp. [cited by applicant]
Response to Extended Search Report dated Dec. 23, 2022, from counterpart European Application No. 22194654.4 filed Sep. 13, 2023, 27 pp. [cited by applicant]
Communication pursuant to Article 94(3) EPC from counterpart European Application No. 22194654.4 dated May 27, 2025, 27 pp. [cited by applicant]
Cited By (1)
US 12,413,578