## 3 Synopsis of KDN Paradigm
### A Glimpse Comparison of KDN with Existing Networks  
The first approach of networking is known to be conventional networking, which requires manually setting and controlling equipment. This networking approach has been used often since networking's inception, and it continues to be employed in contemporary communication networks. Moreover, in conventional networks, the infrastructure layer and the control layer are dispersed among network nodes and closely connected, with nodes like routers serving both control and data-handling purposes. Since every network component must be individually set, older networks are challenging to maintain and administer. This is because massive networks can become unattainable because of the time commitment and susceptible to mistakes nature of human configuration. Furthermore, in these networks, choices are made strictly in accordance with the flow rules or guidelines that network managers have established for setup and surveillance purposes. A more modern strategy than regular networks is SDN that allows for greater versatility in network architecture by divorcing the control layer from the infrastructure layer. Network operators utilize apps to administer the network, conceptually centralizing the control layer. Due to its better adaptability and customization ability, this framework enables network executives to operate networks more rapidly and efficiently. However, SDN \begin{table}
\begin{tabular}{c c c} \hline
**Plane** & **Function** & **Protocols/Models/Languages** \\ \hline \multirow{8}{*}{Knowledge} & Store knowledge & KIF [166], OIL [167], OWL [169], RDFS [168], RDF [161] \\ \cline{2-3}  & Rule modeling and dissemination & RuleML [171], RIF [172], SWRL [173] \\ \cline{2-3}  & Knowledge querying only & KGQL [181], KGML [182], SQWRL [180] \\ \cline{2-3}  & Knowledge querying and modifying & SPARQL [178], GraphQL [179] \\ \cline{2-3}  & Rule/knowledge assessment & RETE [174], Bossam [175], Jess [176], Drools [177] \\ \hline \multirow{8}{*}{Management} & Network management & OF-CONFIG [184], SNMP [185], PACMAN [187], CONMan [186] \\ \cline{2-3}  & Network monitoring & Payless [188], HONE [189], OpenNetMon [190], OpenSample [191] \\ \cline{2-3}  & Data collection & IQP [192,235], packet sampling [193], adaptive data collection [194], sensor measurement collection [195] \\ \cline{2-3}  & Data storage & YANG [196], CIM [197] \\ \hline \multirow{2}{*}{Data} & Forwarding models & OpenFlow [202], ForCES [201], OpFlex [200], POF [203], PCE-PCC [204], \\ \cline{2-3}  & Northbound API & Adhoc [208], RESTful [209], intent-based [201], language-based API [211] \\ \cline{2-3}  & East-Westbound API & ALTO [212], Hyperflow [213], ONOS [210], Onix [214] \\ \cline{2-3}  & Southbound API & OpenFlow [202], ForCES [201], OpFlex [200], POF [203], PCE-PCC [204], \\ \cline{2-3}  & Logically and physically centralized control & NOX [208], Tema [215], Ryu [216], Meridian [217] \\ \cline{2-3}  & Logically centralized and physically distributed control & SMaRLLight [218], HyperFlow [213], ONOS [210], Onix [214], Kandoo [219], Orion [220] \\ \cline{2-3}  & Hybrid control & DevoFlow [221], Fibbing [222], HybridFlow [223] \\ \cline{2-3}  & Logically and physically & DISC [224], D-SDN [225], Cardigan [226] \\ \hline Application & Policy definition and update & Procera [211], Nettle [232], Frenetic [233], Kinetic [234] \\ \hline \end{tabular}
\end{table} 
Table 2: Synopsis of protocols/models/languages in each layer of KDN. does not place a strong emphasis on knowledge generation while making control choices, but the controller that is conceptually centralized utilizes network information to build an overall network picture and make judgments with the support of network application-enforced regulations. Although administration is centralized, it is not separated as a distinct layer but rather is a part of the control layer. Moreover, actions taken by the controller are determined by network application policies rather than knowledge-based inference.