# A Comprehensive Survey on Knowledge-Defined Networking
## 4 Management Plane  
### Introduction to Management Plane  
There is a requirement for efficient and effective management of the network resources in order for the control plane functionality to be effective. The main purpose of the management plane, which operates in parallel with the KDN controller in the KDN architecture, is to collect data and information from the devices in the network, discover and configure QoS options in the network, monitor the network devices, configure the network, prevent undesired traffic interruptions, etc. [58]. Traditional network management has been mostly performed by humans, which can be erroneous due to human errors. In such networks, the network operators must implement policies and complex tasks with a highly constrained set of configuration commands in a command-line interface environment. As the network state changes continuously, reconfiguring manually is time-consuming and less efficient. Note that the management plane has been identified as the \"Measurement\" plane by some researchers, which serves the same purposes as the management plane described above [57]. Therefore, note that measurement or management plane refers to the same plane. For the rest of this paper, we use the term management plane in order to maintain consistency in terminology, which refers to the same plane referred to in the existing literature as the measurement plane.  
\begin{table}
\begin{tabular}{p{113.8 pt} p{113.8 pt} p{113.8 pt} p{113.8 pt}} \hline \hline
**Category** & **Language/Protocol/Model** & **Purpose** & **Developer** \\ \hline Rule representation, storage and exchange & RuleML [209] & Markup language to represent rules & H. Boley et al. \\ \cline{2-4}  & Semantic Web Rule Language (SWRL) [210] & Express rules and constraints & W3C, RIF \\ \cline{2-4}  & Rule Interchange Format (RIF) [211] & Rule language to represent and exchange rules between systems & W3C, RIF \\ \cline{2-4}  & Query and modify knowledge & SPARQL [239] & Query and modify knowledge which appears in RDF & W3C \\ \cline{2-4}  & GraphQL [243] & Query and modify knowledge in knowledge graphs & Huahai He et al. \\ \hline  & SQWRL [240] & Query OWL ontologies & W3C \\ \cline{2-4}  & Knowledge Graph Query Language (KGQL) [241] & Query knowledge graphs & P. Liu et al. \\ \cline{2-4}  & Knowledge Query and Manipulation Language (KGQL) [242] & Exchange messages such as queries, assertions, and requests & T. Finin et al. \\ \hline  & YANG [244] & Describe state data of network devices and their configurations & Bjorklund \\ \cline{2-4}  & Common Information Model (CIM) [245] & Representing information about network infrastructure and services of devices & Uslar M. et al. \\ \hline  & RETE [233] & Rule evaluation and pattern matching & A. Gupta et al. \\ \cline{2-4}  & Dtools [234] & Rule pattern matching supporting querying, rule chaining & M. Proctor \\ \cline{2-4}  & VLog [235] & Reasoning for rules or knowledge represented in RDF or OWL & D. Carral et al. \\ \cline{2-4}  & Bossam [236] & Reason from OWL ontology, support chaining & M. Jang et al. \\ \cline{2-4}  & CLIPS [237] & Evaluate rules using a forward chaining algorithm & F. M. Lopez \\ \cline{2-4}  & Jess [238] & Rule engine for the Java platform & F.H. Ernest \\ \hline \hline \end{tabular}
\end{table}
Table 3: _Cont._