China
Africa
Explore chapters and articles related to this topic
Mobility
Published in Vivek Kale, Digital Transformation of Enterprise Architecture, 2019
The protocol reference model for mobility management is illustrated in Figure 10.1. The model is composed of three planes: Data plane, the control plane and the management plane. The data plane illustrates the protocol layers that are involved in mobility management, including the physical layer, the data link layer, the network layer, the transport layer and the application layer.Control plane presents the key control functions in mobility management, including the security mechanism, location management, handover control, and interoperability control.Management plane handles the network management-related functions, including configuration management, fault management, performance management, accounting management, and security management.
Software‐Defined Networking, Caching and Computing
Published in F. Richard Yu, Tao Huang, Garima Ameta, Yunjie Liu, Integrated Networking, Caching, and Computing, 2018
F. Richard Yu, Tao Huang, Garima Ameta, Yunjie Liu
As Figure 7.1 shows, the architecture of the framework can be divided into three planes of functionality: data, control and management planes. The data plane contains the devices that are responsible for performing a set of elementary operations, including networking, caching and computing, guided by the controller in the control plane. The control plane has a logically centralized controller to control these operations by populating the flow tables of the data plane elements. The management plane includes software services, used to remotely monitor and configure the control functionality, such as routing strategy, load balancing and energy efficiency. These planes are described in detail as follows.
Convergent Network Management and Control Plane
Published in Iannone Eugenio, Telecommunication Networks, 2017
The management plane is constituted by the central management unit, which runs the network manager, and the local management units, which run the element managers, and by the management network that connects all the entities of the management plane.
Load balancing for software-defined network: a review
Published in International Journal of Computers and Applications, 2022
Vivek Srivastava, Ravi Shankar Pandey
The basic architecture of SDN is shown in Figure 1. The complete architecture of the SDN is considered into the following parts. Management plane: this part of the SDN architecture is responsible for defining various rules and policies for a network like traffic monitoring, load balancing, application of security.Control plane: This part of the SDN architecture is called the brain of the network. The controller which has the complete view of the network resides on this plane and controls all the data forwarding devices (switches and routers) present in the network.Data forwarding plane: Physical network framework is characterized in this aspect of the design. All the sending devices are interconnected by either wired or remote medium.Northbound interface: The controller at the control plane is connected with different applications present at the management plane; which instruct the controller for different work (load balancing, traffic management, routing, security) by northbound interface [35, 36]. A northbound interface is typically software that abstracts the lower-level instruction sets and uses it as a common interface for developing different applications.Eastbound and Westbound interface: This interface is responsible to establish the communication between the controllers present in the control plane.Southbound interface: This interface is characterized as the guidance set of the sending devices which determines the convention for sending and accepting the data between the control plane and sending devices present in the data forwarding plane.