IP Library › Granted Patent US 12,726,429
Granted Patent B2
US 12,726,429 · App. 18/814,255 · Granted Sep 1, 2026

Connectivity service provisioning for a software-defined data center (SDDC) group

Inventors: Chandan Ghosh (Bangalore, IN); Gaurav Jindal (Pune, IN); Neeraj Mantri (Pune, IN)
Assignee: VMware LLC
H04L45/24H04L45/04H04L45/64H04L45/76
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,726,429
App. No.
18/814,255
Granted
Sep 1, 2026
Kind
B2
Abstract

Example methods and systems for connectivity service provisioning for a software-defined data center (SDDC) group are described. In one example, a computer system may detect an event that affects a first connectivity service connecting multiple members of the SDDC group. The computer system may obtain first routing information that is applicable in a first SDDC; and second routing information that is applicable in a second SDDC. In response to the event, the computer system may generate and send a first instruction towards the first SDDC and a second instruction towards the second SDDC to cause: (a) the first SDDC and second SDDC to establish a second connectivity service; (b) the first SDDC to update the first routing information to associate a first flow with the second connectivity service; and (c) the second SDDC to update the second routing information to associate a second flow with the second connectivity service.

Claims (66)

1 . A computer system to perform connectivity service provisioning for a software-defined data center (SDDC) group in a software-defined networking (SDN) environment that includes the computer system, a first SDDC and a second SDDC, comprising:

a processor; and

a non-transitory computer-readable medium having stored thereon instructions that, when executed by the processor, cause the processor to perform the following:

detect an event that affects a first connectivity service connecting multiple members of an SDDC group, wherein the multiple members include the first SDDC and the second SDDC;

obtain, from the first SDDC, first routing information that is applicable in the first SDDC and that associates the first connectivity service with a first flow from the first SDDC to the second SDDC;

obtain, from the second SDDC, second routing information that is applicable in the second SDDC and that associates the first connectivity service with a second flow from the second SDDC to the first SDDC; and

in response to the event, generate and send a first instruction towards the first SDDC and a second instruction towards the second SDDC to cause:

(a) the first SDDC and the second SDDC to establish a second connectivity service;

(b) the first SDDC to update the first routing information to associate the first flow with the second connectivity service; and

(c) the second SDDC to update the second routing information to associate the second flow with the second connectivity service.

2 . The computer system of claim 1 , wherein the instructions for detecting the event cause the processor to:

detect one of the following events, being a first event, associated with the SDDC group: (a) removal of the SDDC group from the SDN environment; (b) removal of the first SDDC or the second SDDC from the SDDC group; and (c) addition of a third SDDC, being a new member, to the SDDC group.

3 . The computer system of claim 1 , wherein the instructions for detecting the event cause the processor to:

detect the event that affects the first connectivity service provided by a virtual transit gateway that is configured to connect the multiple members of the SDDC group, to connect at least one of the multiple members with an on-premises data center and to connect at least one of the multiple members with a virtual network.

4 . The computer system of claim 1 , wherein the instructions for obtaining the first routing information and the second routing information cause the processor to:

obtain, from a first management entity associated with the first SDDC, the first routing information that is applicable by a first edge to forward the first flow towards the second SDDC using the first connectivity service; and

obtain, from a second management entity associated with the second SDDC, the second routing information that is applicable by a second edge to forward the second flow towards the first SDDC using the first connectivity service.

5 . The computer system of claim 4 , wherein the instructions for obtaining the first routing information or the second routing information cause the processor to:

obtain the first routing information or the second routing information through an application programming interface (API) invocation that specifies a first identifier (ID) associated with the first edge, a second ID associated with the second edge, or a third ID associated with a virtual transit gateway providing the first connectivity service.

6 . The computer system of claim 1 , wherein the instructions for generating and sending the first instruction and the second instruction cause the processor to:

generate and send the first instruction towards a first management entity to cause a first edge associated with the first SDDC to generate and send a first route advertisement to a second edge associated with the second SDDC, wherein the first route advertisement indicates that a first destination network associated with the second flow is reachable using the second connectivity service; and

generate and send the second instruction towards a second management entity to cause the second edge to generate and send a second route advertisement to the first edge, wherein the second route advertisement indicates that a second destination network associated with the first flow is reachable using the second connectivity service.

7 . The computer system of claim 2 , wherein the instructions further cause the processor to:

in response to detecting a second event to configure the SDDC group to include the first SDDC and the second SDDC, and determining that the first connectivity service is up and running, generate and send instructions to instruct (a) the first SDDC and the second SDDC to disable the second connectivity service, (b) the first SDDC to re-associate the first flow with the first connectivity service and (c) the second SDDC to re-associate the second flow with the first connectivity service.

8 . A method for a computer system to perform connectivity service provisioning for a software-defined data center (SDDC) group in a software-defined networking (SDN) environment that includes the computer system, a first SDDC and a second SDDC, wherein the method comprises:

detecting, by the computer system, an event that affects a first connectivity service connecting multiple members of the SDDC group, wherein the multiple members include the first SDDC and the second SDDC;

obtaining, by the computer system, first routing information that is applicable in the first SDDC and that associates the first connectivity service with a first flow from the first SDDC to the second SDDC;

obtaining, by the computer system, second routing information that is applicable in the second SDDC and that associates the first connectivity service with a second flow from the second SDDC to the first SDDC; and

in response to the event, generating and sending, by the computer system, a first instruction towards the first SDDC and a second instruction towards the second SDDC to cause:

(a) the first SDDC and the second SDDC to establish a second connectivity service;

(b) the first SDDC to update the first routing information to associate the first flow with the second connectivity service; and

(c) the second SDDC to update the second routing information to associate the second flow with the second connectivity service.

9 . The method of claim 8 , wherein detecting the event comprises:

detecting, by the computer system, one of the following events, being a first event, associated with the SDDC group: (a) removal of the SDDC group from the SDN environment; (b) removal of the first SDDC or the second SDDC from the SDDC group; and (c) addition of a third SDDC, being a new member, to the SDDC group.

10 . The method of claim 8 , wherein detecting the event comprises:

detecting, by the computer system, the event that affects the first connectivity service provided by a virtual transit gateway that is configured to connect the multiple members of the SDDC group, to connect at least one of the multiple members with an on-premises data center and to connect at least one of the multiple members with a virtual network.

11 . The method of claim 8 , wherein obtaining the first routing information and the second routing information comprises:

obtaining, by the computer system, from a first management entity associated with the first SDDC, the first routing information that is applicable by a first edge to forward the first flow towards the second SDDC using the first connectivity service; and

obtaining, by the computer system, from a second management entity associated with the second SDDC, the second routing information that is applicable by a second edge to forward the second flow towards the first SDDC using the first connectivity service.

12 . The method of claim 11 , wherein obtaining the first routing information or the second routing information comprises:

obtaining, by the computer system, the first routing information or the second routing information through an application programming interface (API) invocation that specifies a first identifier (ID) associated with the first edge, a second ID associated with the second edge, or a third ID associated with a virtual transit gateway providing the first connectivity service.

13 . The method of claim 8 , wherein generating and sending the first instruction and the second instruction comprises:

generating and sending, by the computer system, the first instruction towards a first management entity to cause a first edge associated with the first SDDC to generate and send a first route advertisement to a second edge associated with the second SDDC, wherein the first route advertisement indicates that a first destination network associated with the second flow is reachable using the second connectivity service; and

generating and sending, by the computer system, the second instruction towards a second management entity to cause the second edge to generate and send a second route advertisement to the first edge, wherein the second route advertisement indicates that a second destination network associated with the first flow is reachable using the second connectivity service.

14 . The method of claim 9 , wherein the method further comprises:

in response to detecting a second event to configure the SDDC group to include the first SDDC and the second SDDC, and determining that the first connectivity service is up and running, generating and sending, by the computer system, instructions to instruct (a) the first SDDC and the second SDDC to disable the second connectivity service, (b) the first SDDC to re-associate the first flow with the first connectivity service and (c) the second SDDC to re-associate the second flow with the first connectivity service.

15 . A non-transitory computer-readable storage medium that includes a set of instructions which, in response to execution by a processor of a computer system, cause the processor to perform a method of connectivity service provisioning for a software-defined data center (SDDC) group in a software-defined networking (SDN) environment that includes the computer system, a first SDDC and a second SDDC, wherein the method comprises:

detecting an event that affects a first connectivity service connecting multiple members of the SDDC group, wherein the multiple members include the first SDDC and the second SDDC;

obtaining, from the first SDDC, first routing information that is applicable in the first SDDC and that associates the first connectivity service with a first flow from the first SDDC to the second SDDC;

obtaining, from the second SDDC, second routing information that is applicable in the second SDDC and that associates the first connectivity service with a second flow from the second SDDC to the first SDDC; and

in response to the event, generating and sending a first instruction towards the first SDDC and a second instruction towards the second SDDC to cause:

(a) the first SDDC and the second SDDC to establish a second connectivity service;

(b) the first SDDC to update the first routing information to associate the first flow with the second connectivity service; and

(c) the second SDDC to update the second routing information to associate the second flow with the second connectivity service.

16 . The non-transitory computer-readable storage medium of claim 15 , wherein detecting the event comprises:

detecting one of the following events associated with the SDDC group: (a) removal of the SDDC group from the SDN environment; (b) removal of the first SDDC or the second SDDC from the SDDC group; and (c) addition of a third SDDC, being a new member, to the SDDC group.

17 . The non-transitory computer-readable storage medium of claim 15 , wherein detecting the event comprises:

detecting the event that affects the first connectivity service provided by a virtual transit gateway that is configured to connect the multiple members of the SDDC group, to connect at least one of the multiple members with an on-premises data center and to connect at least one of the multiple members with a virtual network.

18 . The non-transitory computer-readable storage medium of claim 15 , wherein obtaining the first routing information and the second routing information comprises:

obtaining, from a first management entity associated with the first SDDC, the first routing information that is applicable by a first edge in the first SDDC to forward the first flow towards the second SDDC using the first connectivity service; and

obtaining, from a second management entity associated with the second SDDC, the second routing information that is applicable by a second edge in the second SDDC to forward the second flow towards the first SDDC using the first connectivity service.

19 . The non-transitory computer-readable storage medium of claim 16 , wherein obtaining the first routing information or the second routing information comprises:

obtaining the first routing information or the second routing information through an application programming interface (API) invocation that specifies a first identifier (ID) associated with the first edge, a second ID associated with the second edge, or a third ID associated with a virtual transit gateway providing the first connectivity service.

20 . The non-transitory computer-readable storage medium of claim 15 , wherein generating and sending the first instruction and the second instruction comprises:

generating and sending the first instruction towards a first management entity to cause a first edge associated with the first SDDC to generate and send a first route advertisement to a second edge associated with the second SDDC, wherein the first route advertisement indicates that a first destination network associated with the second flow is reachable using the second connectivity service; and

generating and sending the second instruction towards a second management entity to cause the second edge to generate and send a second route advertisement to the first edge, wherein the second route advertisement indicates that a second destination network associated with the first flow is reachable using the second connectivity service.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 23, 2024
From: GHOSH, CHANDAN; JINDAL, GAURAV; MANTRI, NEERAJ
To: VMWARE LLC
Reel/Frame 068388/0825 →
Priority Claims (2)
IN 202341061926 · Sep 14, 2023 · national
IN 202341061932 · Sep 14, 2023 · national
Continuity (1)
Related Publication 20250097138A1 · Mar 20, 2025
References Cited (14)
US 10129096B2 · Holkkola · 2018 [cited by examiner]
US 10567288B1 · Mutnuru · 2020 [cited by examiner]
US 10715419B1 · Suryanarayana · 2020 [cited by examiner]
US 11553002B2 · Rotkop · 2023 [cited by examiner]
US 11582083B2 · Shil · 2023 [cited by applicant]
US 11646941B2 · Christober · 2023 [cited by examiner]
US 12074765B2 · Jindal · 2024 [cited by applicant]
US 12368717B1 · Cheethirala · 2025 [cited by examiner]
US 20150249573A1 · Miller et al. · 2015 [cited by applicant]
US 20200374221A1 · Tandon · 2020 [cited by applicant]
US 20220019482A1 · Jiang et al. · 2022 [cited by applicant]
US 20240406104A1 · Jindal et al. · 2024 [cited by applicant]
WO WO2017199062A1 · 2017 [cited by examiner]
Extended European Search Report mailed Jan. 28, 2025 in European Patent Application No. 24200170.9, 12 pages. [cited by applicant]