Communication device with persistent configuration and verification

• US 9,900,206 B2
• Filed: 07/20/2015
• Issued: 02/20/2018
• Est. Priority Date: 07/20/2015
• Status: Active Grant

• Current Assignee: Schweitzer Engineering Laboratories, Incorporated
• Original Assignee: Schweitzer Engineering Laboratories, Incorporated
• Inventors: Grussling, Barry Jakob, Dearien, Jason A., Bradetich, Ryan
• Primary Examiner(s): Jagannathan, Melanie
• Application Number:
  US14/803,810
• Publication Number:
  US 20170026226A1
• Time in Patent Office: 946 Days
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/0661 by reconfiguring faulty entities
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/42 Centralised routing
• CPC Class Codes: H04L 9/08 Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords network architectures or network communication protocols for supporting key management in a packet data network H04L63/06

Abstract

The present disclosure pertains to systems and methods for establishing communication with a remote communication device in a software defined network (SDN) during time when an SDN controller is unavailable. In one embodiment, a local communication device may be configured to receive a plurality of data flows from an SDN controller and to store the plurality of data flows in a persistent data memory. The device may generate a unique identifier for the local communication device that is transmitted to a remote communication device. Following a disruption the results in the SDN controller being unavailable, the local communication device may recover into a default configured state based on the plurality of data flows in the persistent data memory. The local communication device may then transmit the unique identifier to the remote communication device after the disruption to begin a process of reestablishing communication with the remote communication device.

Claims

1. A communication device, comprising:

a data bus;

a communication interface in communication with the data bus;

a persistent data memory in communication with the data bus;

a processor in communication with the data bus and configured execute instructions to cause;

an SDN controller communication subsystem in communication with the data bus to receive a plurality of data flows and authentication credentials from an SDN controller and to store the plurality of data flows and the authentication credentials in the persistent data memory;

a unique identifier subsystem to generate a unique identifier for the communication device and to transmit the unique identifier to a remote communication device through the communication interface;

a traffic routing subsystem to communicate with the remote communication device based on the plurality of data flows;

a direct communication subsystem to;

identify the occurrence of a disruption affecting the communication device and to determine that communication with the SDN controller is unavailable,

recover the communication device into a default configured state based on the plurality of data flows in the persistent data memory;

transmit a link layer discovery packet comprising the unique identifier to the remote communication device after the disruption;

receive a response to the link layer discovery packet from the remote communication device;

perform an authentication process with the remote communication device using the authentication credentials; and

reestablish communication with the remote communication device.

2. A method of establishing communication between a local communication device and a remote communication device in a software defined network (SDN), the method comprising:

receiving at a local communication device a plurality of data flows from an SDN controller;

storing the plurality of data flows in a persistent data memory;

generating a unique identifier for the local communication device;

transmitting the unique identifier to remote communication device;

communicating with the remote communication device based on the plurality of data flows;

identifying the occurrence of a disruption affecting the local communication device;

determining that the SDN controller is unavailable;

recovering the local communication device into a default configured state based on the plurality of data flows in the persistent data memory;

transmitting the unique identifier to the remote communication device after the disruption;

the remote communication device verifying the identity of the local communication device based on the unique identifier; and

reestablishing communication with the remote communication device.

3. A method of claim 2, wherein the unique identifier represents an identifier of the local communication device and a configuration of the local communication device.

4. The method of claim 3, wherein the configuration of the local communication device comprises the plurality of data flows.

5. The method of claim 3, further comprising generating the unique identifier using a hash function.

6. The method of claim 2, wherein the disruption comprises one of a loss of power, a restart of the local communication device, and a loss of communication with the SDN controller.

7. The method of claim 2, wherein reestablishing communication with the remote communication device further comprises:

receiving a response from the remote communication device to transmission of the unique identifier after the disruption; and

performing an authentication process.

8. The method of claim 7, further comprising:

receiving authentication credentials from the SDN controller, the authentication credentials comprising one of a cryptographic key and a digital signature;

storing the cryptographic credentials in the persistent data memory; and

providing the cryptographic credentials during the authentication process.

9. The method of claim 2, further comprising transmitting a link layer discovery packet after the disruption.

10. The method of claim 9, wherein the link layer discovery packet comprises the unique identifier.

11. A communication device configured to establish communication with a remote communication device in a software defined network (SDN), comprising:

a data bus;

a communication interface in communication with the data bus;

a processor in communication with the data bus and configured to process communications received via the communication interface;

a persistent data memory in communication with the data bus;

an SDN controller communication subsystem in communication with the data bus and configured to receive a plurality of data flows from an SDN controller and to store the plurality of data flows in the persistent data memory;

a unique identifier subsystem configured to generate a unique identifier for the communication device and to transmit the unique identifier to a remote communication device through the communication interface;

a traffic routing subsystem configured to communicate with the remote communication device based on the plurality of data flows;

a direct communication subsystem configured to;

identify the occurrence of a disruption affecting the communication device, to determine that the SDN controller is unavailable,

recover the communication device into a default configured state based on the plurality of data flows in the persistent data memory;

transmit the unique identifier to the remote communication device after the disruption; and

reestablish communication with the remote communication device based on verification of the identity of the communication device using the unique identifier.

12. The communication device of claim 11, wherein the unique identifier represents an identifier of the communication device and a configuration the communication device.

13. The communication device of claim 12, wherein the configuration of the communication device comprises the plurality of data flows.

14. The communication device of claim 12, wherein the unique identifier subsystem is configured to generate the unique identifier using a hash function.

15. The communication device of claim 11, wherein the disruption comprises one of a loss of power, a restart of the communication device, and a loss of communication with the SDN controller.

16. The communication device of claim 11, wherein the direct communication subsystem is further configured to:

receive a response from the remote communication device to transmission of the unique identifier after the disruption; and

perform an authentication process.

17. The communication device of claim 16, wherein the SDN controller communication subsystem is further configured to receive authentication credentials from the SDN controller and to store the authentication credentials in the persistent data memory;

and wherein the direct communication subsystem is further configured to provide the authentication credentials during the authentication process.

18. The communication device of claim 11, wherein the direct communication subsystem is further configured to transmit a link layer discovery packet after the disruption.

19. The communication device of claim 18, wherein the link layer discovery packet comprises the unique identifier.

20. The communication device of claim 11, wherein the default configured state corresponds to a configuration of the communication device immediately preceding the disruption.