Network management via a secondary communication channel in a software defined network

• US 10,581,684 B2
• Filed: 12/06/2017
• Issued: 03/03/2020
• Est. Priority Date: 12/06/2017
• Status: Active Grant

• Current Assignee: Schweitzer Engineering Laboratories, Incorporated
• Original Assignee: Schweitzer Engineering Laboratories, Incorporated
• Inventors: Smith, Rhett, Gammel, Dennis
• Primary Examiner(s): Nguyen, Quang N
• Application Number:
  US15/833,468
• Publication Number:
  US 20190173754A1
• Time in Patent Office: 818 Days
• Field of Search: 709203, 709206, 709217, 709219, 709223, 709224, 709226, 709228, 709230, 709232, 709238, 398 34
• CPC Class Codes: H04L 41/0836 to enhance reliability, e.g. reduce downtime
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/64 using an overlay routing layer
• CPC Class Codes: H04L 45/66 Layer 2 routing, e.g. in Ethernet based MAN's
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: Y04S 40/00 Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them

Abstract

A software-defined network controller (SDN controller) defines a first network flow to be selectively implemented by a networking device according to a first network operation profile. The SDN controller defines a second network flow to be selectively implemented by the networking device according to a second network operation profile. The first and second network operation profiles are stored within a memory of the networking device to be selectively implemented based on the status of a profile selection input on the networking device. The profile selection input is a contact input in some embodiments. When the contact input is de-asserted, the networking device implements the first network flow according to the first network operation profile. When the contact input is asserted, the networking device implements the second network flow according to the second network operation profile.

Claims

1. A software-defined networking device, comprising:

a processor;

a plurality of communication ports for network communications;

a non-transitory computer-readable medium to store a plurality of network operation profiles, wherein each of the plurality of network operation profiles is implementable by the processor to control network behavior via the plurality of communication ports;

a profile selection port to receive a signal selecting one of the plurality of network operation profiles to be implemented by the networking device, wherein the profile selection port is a contact input that can be de-asserted to select a first of the plurality of network operation profiles and asserted to select a second of the plurality of network operation profiles; and

a controller port to receive communications from a software-defined network (SDN) controller, wherein each of the plurality of network operation profiles is defined by the SDN controller.

2. The software-defined networking device of claim 1, wherein at least one of the network operation profiles is defined in terms of changes to another of the network operation profiles.

3. The software-defined networking device of claim 1, wherein a first network operation profile of the plurality of network operation profiles disables a first communication protocol via the plurality of communication ports, and wherein a second network operation profile of the plurality of network operation profiles enables the first communication protocol via the plurality of communication ports.

4. The software-defined networking device of claim 1, wherein the profile selection port comprises one of an ethernet port and a serial port.

5. The software-defined networking device of claim 1, wherein the plurality of communication ports includes one or more of:

contact ports, a DB-25 port, an RS-485 port, an RS-232 port, an Ethernet port, an SFP port, a SONET port, a COM port, an EtherCAT port, a Fiber Channel port, a serial port, and a parallel port.

6. The software-defined networking device of claim 1, wherein each of the plurality of network operation profiles defines network behavior via the plurality of communication ports as it pertains to one or more of:

port forwarding, MAC address handling, network address translation, protocol enablement and disablement, virtual local area network creation, routing, port access control, virtual private network management, and quality of service management.

7. A method of operating a software-defined network, comprising:

defining, via a software-defined network controller (SDN controller), a first network flow to be implemented by at least one networking device connected as part of a software-defined network (SDN);

defining, via the SDN controller, a second network flow to be implemented by the at least one networking device, wherein the second network flow is different than the first network flow;

determining a status of a profile selection signal received by the at least one networking device as one of de-asserted and asserted;

implementing, by the at least one networking device, the first network flow in response to a determination that the status of the profile selection signal is de-asserted; and

implementing, by the at least one networking device, the second network flow in response to a determination that the status of the profile selection signal is asserted.

8. The method of claim 7, further comprising:

disconnecting the SDN controller from the at least one networking device before implementing the second network flow in response to the determination that the status of the profile selection signal is asserted.

9. The method of claim 7, wherein implementing the second network flow enables communication between two devices that was previously prevented per the first network flow.

10. The method of claim 7, wherein implementing the second network flow enables a communication protocol on the SDN that was previously disabled per the first network flow.

11. The method of claim 7, wherein the second network flow is defined in terms of change to the first network flow.

12. The method of claim 7, wherein the first network flow is defined, at least in part, based on a first network operation profile, and

wherein the second network flow is defined, at least in part, based on a second network operation profile.

13. The method of claim 12, wherein the at least one networking device connected as part of the SDN is configured to store the first and second network operation profiles.

14. The method of claim 13, wherein implementing the second network flow comprises executed the stored second network operation profile to the exclusion of the first stored network operation profile.

15. A software-defined network, comprising:

a networking device that facilitates communication between intelligent electronic devices (IEDs) in a software-defined network (SDN);

at least one SDN controller to;

define a first network operation profile to be implemented by default by the networking device, and

define a second network operation profile to be selectively implemented by the networking device,

at least one human interface device (HID) prevented from communicating with at least one of the IEDs using a target protocol per the first network operation profile;

a profile selection input configured to be manually asserted by an operator, wherein assertion of the profile selection input causes the networking device to selectively implement the second network operation profile, and wherein the second network operation profile allows the HID to communicate with the at least one IED using the target protocol.

16. The software-defined network of claim 15, wherein the first network operation profile restricts the target protocol, such that the HID is prevented from communicating with the at least one IED.

17. The software-defined network of claim 15, wherein the profile selection input comprises a mechanical spring-wound timer to be manually asserted for a predefined time period during which the HID is allowed to communicate with the IED using the target protocol.

18. The software-defined network of claim 15, wherein the target protocol comprises a Telnet protocol.