IP Library Granted Patent US 9,755,899
Granted Patent B2
US 9,755,899 · App. 12/777,028 · Granted Sep 5, 2017

Generation and usage of mobility VLAN ID version value

Inventors: William Stanislaus (Fremont, CA); Seemant Choudhary (Fremont, CA); Vivek L. Atreya (Vyalikaval Bangalore, IN); Shashi H. Ankaiah (Karnataka, IN)
Assignee: Avaya Inc.
H04L41/082H04L12/4641
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 9,755,899
App. No.
12/777,028
Granted
Sep 5, 2017
Kind
B2
Abstract

A mobility network architecture includes a control plane and data plane. The control plane supports notification of VLAN configurations. The data plane supports routing of data amongst VLANs. Each VLAN has an associated identifier value as well as a version number. The version number for a respective VLAN can be updated to a new value each time there is a change to the VLAN. Typically, a controller communicates over the control plane to notify each member switch when a version number has changed for a VLAN. If controller notification fails, a member switch can receive a notification from a neighboring switch that the version number for a VLAN has been modified. In response to detecting such a condition, the switch receiving the notification can prevent forwarding of data even though the switch does not receive notification from the controller that the version number for the VLAN has changed.

Claims (67)

1. A method comprising:

at a given switch configured to route data in a network, wherein the network comprises a control plane, a data plane, and a virtual local area network (VLAN):

receiving, from a VLAN controller in the network via the control plane of the network, a first notification including a VLAN identifier for the VLAN in the network and a corresponding current version value for the VLAN in the network, wherein said current version value for the VLAN in the network indicates a current number of times there has been a change of a configuration of said VLAN;

forwarding the data in the network over the VLAN via the data plane based on the VLAN identifier and the current version value received from the VLAN controller;

receiving a second notification from a first remote switch in the network via the data plane, the second notification including the VLAN identifier and a first outdated version value for the VLAN, wherein the first outdated version value indicates a previous number of times there has been a change of the configuration of said VLAN;

in response to detecting that the first outdated version value in the second notification received from the first remote switch does not match the corresponding current version value received from the VLAN controller, preventing forwarding of data on the VLAN from the given switch to the first remote switch;

receiving a third notification from a second remote switch in the network via the data plane, the third notification including the VLAN identifier and an updated version value for the VLAN, wherein the updated version value indicates a new number of times there has been a change of the configuration of said VLAN; and

forwarding the data in the network over the VLAN based on the VLAN identifier and the updated version value received from the second remote switch;

receiving a fourth notification from a third remote switch in the network via the data plane, the fourth notification including the VLAN identifier and a second outdated version value for the VLAN, wherein the second outdated version value indicates a previous number of times there has been a change of the configuration of said VLAN; and

in response to detecting that the second outdated version value in the fourth notification received from the third remote switch does not match the corresponding updated version value received from the second remote switch, preventing forwarding of the data on the VLAN from the given switch to the third remote switch.

2. The method as in claim 1 further comprising:

initiating, in response to detecting that the outdated version value received from the first remote switch does not match the corresponding version value received from the VLAN controller, communications over a control plane of the network with the VLAN controller to receive, via the control plane, a current version value for the VLAN identifier.

3. The method as in claim 2 further comprising:

at the given switch:

keeping track of identities of multiple remote switches that are member resources of the VLAN; and

initiating, in response to receiving the current version value from the VLAN controller, communications to notify each of the multiple remote switches that are member resources of the VLAN of the current version value.

4. The method as in claim 3 further comprising:

receiving another notification from the first remote switch including the current version value for the VLAN via the control plane; and

forwarding, in response receiving another notification from the first remote switch including the current version value for the VLAN via the control plane, the data over the VLAN from the given switch to the first remote switch.

5. The method as in claim 1 , wherein forwarding the data in the network over the VLAN via the data plane based on the VLAN identifier includes:

inserting the VLAN identifier into a data packet.

6. The method as in claim 5 further comprising:

transmitting the data packet over a tunnel associated with the VLAN.

7. The method as in claim 1 further comprising:

in response to receiving notification from a remote switch that a stored version value for the VLAN identifier has been updated to a new version value that is different than the stored version value, changing the stored version value to the new version value.

8. The method as in claim 1 further comprising:

at the given switch:

keeping track of identities of multiple remote switches in the network that are members of the VLAN; and

in response to receiving a notification from one of the multiple remote switches that a stored version value for the VLAN has been changed to a new version value, initiating communications with at least one other of the multiple remote switches that are members of the VLAN to notify of the new version value.

9. A computer system comprising:

a processor;

a memory unit that stores instructions associated with an application executed by the processor; and

an interconnect coupling the processor and the memory unit, enabling the computer system to execute the application and perform operations of:

receiving, from a VLAN controller in a network via a control plane of the network, a first notification including a VLAN identifier for a VLAN in the network and a corresponding current version value for the VLAN in the network, wherein said current version value for the VLAN in the network indicates a current number of times there has been a change of a configuration of said VLAN;

forwarding the data in the network over the VLAN via a data plane based on the VLAN identifier and the current version value received from the VLAN controller;

receiving a second notification from a first remote switch in the network via the data plane, the second notification including the VLAN identifier and a first outdated version value for the VLAN, wherein the first outdated version value indicates a previous number of times there has been a change of the configuration of said VLAN;

in response to detecting that the first outdated version value in the second notification received from the first remote switch does not match the corresponding current version value received from the VLAN controller, preventing forwarding of data on the VLAN from the given switch to the first remote switch;

receiving a third notification from a second remote switch in the network via the data plane, the third notification including the VLAN identifier and an updated version value for the VLAN, wherein the updated version value indicates a new number of times there has been a change of the configuration of said VLAN; and

forwarding the data in the network over the VLAN based on the VLAN identifier and the updated version value received from the second remote switch;

receiving a fourth notification from a third remote switch in the network via the data plane, the fourth notification including the VLAN identifier and a second outdated version value for the VLAN, wherein the second outdated version value indicates a previous number of times there has been a change of the configuration of said VLAN; and

in response to detecting that the second outdated version value in the fourth notification received from the third remote switch does not match the corresponding updated version value received from the second remote switch, preventing forwarding of the data on the VLAN from the given switch to the third remote switch.

10. The computer system as in claim 9 , wherein the application further supports operations of:

initiating, in response to detecting that the outdated version value received from the first remote switch does not match the corresponding version value received from the VLAN controller, communications over a control plane of the network with the VLAN controller to receive, via the control plane, a current version value for the VLAN identifier.

11. The computer system as in claim 10 , wherein the application further supports operations of:

keeping track of identities of multiple remote switches that are member resources of the VLAN; and

initiating, in response to receiving the current version value from the VLAN controller, communications to notify each of the multiple remote switches that are member resources of the VLAN of the current version value.

12. The computer system as in claim 11 , wherein the application further supports operations of:

receiving another notification from the first remote switch including the current version value for the VLAN via the control plane; and

forwarding, in response receiving another notification from the first remote switch including the current version value for the VLAN via the control plane, the data over the VLAN from the given switch to the first remote switch.

13. The computer system as in claim 9 , wherein forwarding the data in the network over the VLAN via the data plane based on the VLAN identifier:

inserting the VLAN identifier into a data packet.

14. The computer system as in claim 13 , wherein the application further supports operations of:

transmitting the data packet over a tunnel associated with the VLAN.

15. The computer system as in claim 9 , wherein the application further supports operations of:

in response to receiving notification from a remote switch that a stored version value for the VLAN identifier has been updated to a new version value that is different than the stored version value, changing the stored version value to the new version value.

16. The computer system as in claim 9 , wherein the application further supports operations of:

keeping track of identities of multiple remote switches in the network that are members of the VLAN; and

in response to receiving a notification from one of the multiple remote switches that a stored version value for the VLAN has been changed to a new version value, initiating communications with at least one other each of the multiple remote switches that are members of the VLAN to notify of the new version value.

17. A non-transitory computer-readable storage medium having instructions stored thereon for processing data information, such that the instructions, when carried out by a processing device, cause the processing device to perform operations of:

receiving, from a VLAN controller in a network, via a control plane of the network, a first notification including a VLAN identifier for a VLAN in the network and a corresponding current version value for the VLAN in the network, wherein said current version value for the VLAN in the network indicates a current number of times there has been a change of a configuration of said VLAN;

forwarding the data in the network over the VLAN via a data plane based on the VLAN identifier and the current version value received from the VLAN controller;

receiving a second notification from a first remote switch in the network via the data plane, the second notification including the VLAN identifier and a first outdated version value for the VLAN, wherein the first outdated version value indicates a previous number of times there has been a change of the configuration of said VLAN;

in response to detecting that the first outdated version value in the second notification received from the first remote switch does not match the corresponding current version value received from the VLAN controller, preventing forwarding of data on the VLAN from the given switch to the first remote switch;

receiving a third notification from a second remote switch in the network via the data plane, the third notification including the VLAN identifier and an updated version value for the VLAN, wherein the updated version value indicates a new number of times there has been a change of the configuration of said VLAN; and

forwarding the data in the network over the VLAN based on the VLAN identifier and the updated version value received from the second remote switch;

receiving a fourth notification from a third remote switch in the network via the data plane, the fourth notification including the VLAN identifier and a second outdated version value for the VLAN, wherein the second outdated version value indicates a previous number of times there has been a change of the configuration of said VLAN; and

in response to detecting that the second outdated version value in the fourth notification received from the third remote switch does not match the corresponding updated version value received from the second remote switch, preventing forwarding of the data on the VLAN from the given switch to the third remote switch.

Assignments (20)
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
SECURITY AGREEMENT Recorded Feb 22, 2011
From: AVAYA INC., A DELAWARE CORPORATION
To: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE
Reel/Frame 025863/0535 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2010
From: STANISLAUS, WILLIAM; CHOUDHARY, SEEMANT; ATREYA, VIVEK L.; ANKAIAH, SHASHI H.
To: AVAYA INC.
Reel/Frame 024361/0984 →
Continuity (2)
Provisional Application 61178288 · May 14, 2009
Related Publication 20100290348A1 · Nov 18, 2010