# US 2017/0374028 A1 · Software-defined networking controller

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0374028 A1
- Document ID: US20170374028A1
- Status: Published application
- Kind: A1
- Application number: 15/545,889
- Filed: 2015-01-28
- Published: 2017-12-28
- Earliest claimed: 2015-01-28
- Assignees: Nokia Solutions and Networks Oy
- Applicants: Nokia Solutions and Networks Oy
- Inventors: Ian Justin OLIVER; Silke HOLTMANNS
- Web page: https://patentgrep.com/patent/US20170374028A1

## CPC

- H04L 63/0227: {Filtering policies (mail message filtering H04L51/212)}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04L 63/1458: {Denial of Service}
- H04L 63/1491: {using deception as countermeasure, e.g. honeypots, honeynets, decoys or entrapment}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A fault tolerant software-defined networking controller is provided by using in an alert mode a secondary soft-ware-defined networking controller.

## Claims

### Claim at position 1

-36. (canceled)

### Claim 37

A method comprising:
detecting in a software-defined networking controller an initial malicious traffic;
triggering, in response to the detecting, one of starting and creating of at least one secondary software-defined networking controller;
creating, in response to the detecting, at least one read-only copy and at least one modifiable copy of each flow table in at least one traffic forwarding layer apparatus controlled by the software-defined networking controller;
filtering, by the software-defined networking controller, from received traffic malicious traffic;
processing by the software-defined networking controller the non-malicious traffic; and
performing one of forwarding from the software-defined networking controller to the at least one secondary software-defined networking controller at least the malicious traffic to be processed and forwarding from the software-defined networking controller to the secondary software-defined networking controller the non-malicious traffic and the malicious traffic to be processed.

### Claim 38 (depends on 37)

The method of claim 37, further comprising:
performing the detecting in response to receiving from a malware detection component information indicating the initial malicious traffic.

### Claim 39 (depends on 37)

The method of claim 37, further comprising:
shutting down, in response to detecting that it is safe to return to normal operation, the at least one secondary software-defined controller.

### Claim 40 (depends on 39)

The method of claim 39, further comprising:
determining, in response to detecting that it is safe to return to normal operation, for each copied flow table a sane state of the flow table; and
updating each copied flow table to corresponding sane state.

### Claim 41 (depends on 37)

The method of claim 37, further comprising:
sending, from the software-defined controller, processing results to at least one comparing unit.

### Claim 42 (depends on 41)

The method of claim 41, further comprising:
processing by the secondary software-defined networking controller the traffic from the software-defined networking controller; and
sending from the secondary software-defined networking controller processing results to the at least one comparing unit.

### Claim 43 (depends on 42)

The method of claim 42, further comprising:
comparing in the comparing unit the processing results from the software-defined networking controller with the processing results from the secondary software-defined networking controller; and
sending from the comparing unit the comparison result as a processing result to the at least one traffic forwarding layer apparatus.

### Claim 44 (depends on 43)

The method of claim 43, further comprising:
obtaining by the comparing unit one or more policy rules; and
using the one or more policy rules in the comparing to determine the comparison result.

### Claim 45 (depends on 37)

The method of claim 37, further comprising:
processing by the secondary software-defined networking controller the traffic from the software-defined networking controller; and
sending from the secondary software-defined networking controller processing results to the at least one traffic forwarding layer apparatus.

### Claim 46

A control layer apparatus, comprising:
at least one processor, and
at least one memory for storing instructions to be executed by the processor, wherein
the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to:
perform a software-defined networking controller functionality;
detect a received initial malicious traffic;
trigger, in response to the detecting, one of starting and creating of at least one secondary software-defined networking controller;
create, in response to the detecting, at least one read-only copy and at least one modifiable copy of each flow table in at least one traffic forwarding layer apparatus controlled by the control layer apparatus as the software-defined networking controller;
filter from received traffic malicious traffic;
process the filtered non-malicious traffic; and
perform one of forwarding to the secondary software-defined networking controller at least the malicious traffic to be processed, and forwarding from the software-defined networking controller to the secondary software-defined networking controller the non-malicious traffic and the malicious traffic to be processed.

### Claim 47 (depends on 46)

The control layer apparatus of claim 46, wherein
the at least one memory and the instructions are configured to, with the at least one processor, further cause the apparatus at least to perform:
shutting down, in response to detecting that it is safe to return to normal operation, the at least one secondary software-defined controller.

### Claim 48 (depends on 47)

The control layer apparatus of claim 47, wherein
the at least one memory and the instructions are configured to, with the at least one processor, further cause the apparatus at least to perform:
determining, in response to detecting that it is safe to return to normal operation, for each copied flow table a sane state of the flow table; and
updating each copied flow table to corresponding sane state.

### Claim 49 (depends on 47)

The control layer apparatus of claim 47, wherein
the at least one memory and the instructions are configured to, with the at least one processor, further cause the apparatus at least to perform:
sending, from the software-defined controller, processing results to at least one comparing unit.

### Claim 50 (depends on 47)

The control layer apparatus of claim 47, wherein
the at least one memory and the instructions are configured to, with the at least one processor, further cause the apparatus at least to perform:
detecting that it is safe to return to normal operation only in response to receiving a corresponding indication from a security control unit.

### Claim 51

A non-transitory computer readable media having stored thereon instructions that, when executed by an apparatus, cause the apparatus to:
operate as a software-defined networking controller;
trigger, in response to detecting an initial malicious traffic, one of starting or creating of at least one secondary software-defined networking controller;
create, in response to the initial malicious traffic, at least one read-only copy and at least one modifiable copy of each flow table in at least one traffic forwarding layer apparatus controlled by the software-defined networking controller;
filter from received traffic malicious traffic;
process the filtered non-malicious traffic; and
perform one of forwarding to the secondary software-defined networking controller at least the malicious traffic to be processed, and forwarding from the software-defined networking controller to the secondary software-defined networking controller the non-malicious traffic and the malicious traffic to be processed.

### Claim 52

A system comprising:
at least one traffic forwarding layer apparatus using at least one flow table;
at least one software-defined networking controller controlling at least one of the at least one traffic forwarding layer apparatus and being configured to
detect reception of an initial malicious traffic;
trigger, in response to detecting, one of starting and creating of at least one secondary software-defined networking controller;
create, in response to the detecting, at least one read-only copy and at least one modifiable copy of each flow table in at least one traffic forwarding layer apparatus controlled by the software-defined networking controller;
filter from received traffic malicious traffic;
process the non-malicious traffic; and
perform one of forwarding to the at least one secondary software-defined networking controller malicious traffic to be processed and forwarding to the secondary software-defined networking controller both the non-malicious traffic and the malicious traffic to be processed;
a network entity to which at least one secondary software-defined networking controller of at least one of the at least one software-defined networking controller may be created to be started in response to receiving corresponding instructions from the at least one of the at least one software-defined networking controller, to process control traffic received from the at least one of the at least software-defined networking controller, the control traffic received comprising either malicious traffic or both malicious and non-malicious traffic, as if the secondary software-defined networking controller would be the at least one of the at least one software-defined networking controller and to treat all control traffic as non-malicious; and to send from the secondary software-defined networking controller processing results including routing instructions to one of the at least one traffic forwarding layer apparatus and a comparing unit to be forwarded to the at least one traffic forwarding layer apparatus;
wherein at least one of the at least one modifiable copy of the at least one flow table is used by the at least one secondary software-defined networking controller after it has been started.

### Claim 53 (depends on 52)

The system of claim 52, wherein:
the at least one software-defined networking controller controlling is further configured to send processing results to the at least one comparing unit; and
the at least one comparing unit is configured to
receive from the at least one of the at least one software-defined networking controller a first processing results relating to a non-malicious control traffic;
receive from the at least one secondary software-defined networking controller a second processing results relating to one of malicious control traffic and both malicious and non-malicious control traffic;
obtain one or more policy rules;
compare, using the one or more policy rules, the first processing results with the second processing results to determine a comparison result; and
send the comparison result as a processing result from the at least one of the at least one software-defined networking controller to at least one of the at least one traffic forwarding layer apparatus.
