, or QoS Parameters Support List will be updated and communicated to the gNB-CU-CP via the gNB-CU-UP Configuration Update procedure. For additional information about OAM support for control- and user-plane separation, see Section 6.5. Full details of OAM are specified in 3GPP TS 28.541. 4 NG-RAN Architecture 4.4.3.3 Relation to SDN SDN technology is an approach to networking architecture in which control logic is implemented in a network entity separate from, for example, routers and switches. This represents a paradigm shift compared with previous networking architectures and has been successfully applied to many networking technologies, for example, transport network and cloud computing, to name a few. The SDN concept makes it easier to meet new requirements from, for example, data centers that cannot be easily satisfied by traditional IP networks. Examples of such new requirements are: enforcement of dynamic routing policies, simplifying network configuration, accelerating the deployment of new networking features, and support of network customization. A typical SDN network generally consists of three layers: Data plane, which perform packets forwarding. Control plane (or SDN controller), which installs forwarding rules in data forwarding devices via the south-bound interface, e.g. OpenFlow Management plane (or network applications), which leverage the functions offered by the north-bound interface to implement network control and operation logic. Even though 3GPP has not explicitly defined SDN, NG-RAN with separated control/user- plane architecture makes it easy to map 3GPP network entities to the SDN architecture: In the data plane, a gNB-CU-UP becomes a simple device to process and forward GTP or IP packets. In the control plane, a gNB-CU-CP role is similar to that of an SDN controller with the E1 interface acting as the south-bound interface, which installs processing rules for inbound packets of the data plane. The management plane is not explicitly standardized in 3GPP; however, RRM ranging from radio ac