A Survey on Software-Defined Network and OpenFlow: From Concept to Implementation

Software-Defined Networking Reviewed Model

“…The SDN switches can always report forwarding results to the higher layer -OpenFlow Controller [3]. The results could be simple success or failure for a data forwarding operation, or some error messages or other forwarding status data.…”

“…Robust Wireless Integration: Although OpenFlow has been well developed in wired network, there are very few studies on its performance in wireless networks [3]. Two issues are not covered in OpenFlow, which are necessary for wireless networks (Figure 9).…”

“…It is important to ensure compatibility among Controllers to enable cooperation [3]. The compatibility is needed for enabling various fundamental services like inter-domain routing to enable communication between hosts in different domains ( Figure 5).…”

“…Software language SDN framework need to translate these policies into low-level switch configurations [5,6]. If a programmer tries to implement a new policy atomically to a particular switch, in current SDN frame work, it will cause the disruption of the whole network [3]. A suitable low level language in SDN framework is required to make this model more programmer-friendly ( Figure 6).…”

“…In OpenFlow framework, the central part is a software named Controller [3]. It is where intelligence of routing decisions, routing table generation and packet traffic control are generated.…”