## 1 Introduction
### Application Plane  
The final plane or layer is the application layer. This is the place of the advancement of different application programs that permit a correspondence and cooperation with all the other designs. It is completed quickly, altogether with the help of NBI APIs that accomplish the correspondence of this plane against other planes. This piece of design can get a progressively unique point of view of the system, meaningful from the amount and dispersion of the associated gadgets to assortment of measurements of the system conduct, and which are the places where choices about its organization are made [5]. Consequently, it is important that particular advancement of these significant level programs and applications are made and executed by networks that advance improvement by the open source stages, adding to adjustment [6], and including highlights, such as security, encryption, and adaptability. In such a manner, the improvement of uses with the Representational State Transfer (REST5) engineering has made progress in the SDN, giving advantageous administration-arranged applications that pay little respect to the programming languages and the executables in the different stages. The applications design is bolstered by novel dialects, for example, JSON6, JavaScript, and Python [1], which empower the administration and organization of the systems to be accepted on adaptable stages. In the course of recent periods, the promising thought of the vehicular ad-hoc networks (VANETs) has been completely examined and thoroughly looked into by analysts in both the scholarly world and industry [7]. However, the rising and promising standards of distributed computing, Fog, or potentially Edge computing, SDN and the system capacities virtualization have totally changed the remote systems administration industry, however they have additionally pushed extensive imaginative headways for the transportation division. This is combined by other huge mechanical approaches appropriate to the development of associated and autonomous vehicles and unavoidable use of various new tangible gadgets introduced on-board vehicles that encourage in the different scope of agreeable vehicular  
Figure 2: The three planes of the software defined network (SDN) architecture (data plane, control plane, and the application plane). security applications and programs (i.e., send the crash cautions, crisis vehicles help, (powerless) walker impact relief, overwhelm crossing point cautions and dangerous area cautions). These security applications are basic in nature, yet necessitate a low-dormancy foundation with the most extreme middle-of-the-road postponement running between 10 ms and 50 ms [8]. Moreover, advanced associated vehicles are outfitted with 120 sensors and this number is foreseen to increment up to 250 towards the end of 2020 [9]. These sensors produce the bulk of useful information, yet in addition they assume a fundamental job in making and sharing knowledge for vehicular correspondence. Moreover, according to a gauge of Intel [4], the averagely-determined associated vehicles (i.e., individual vehicles utilized for everyday schedule purposes and not for any business tasks) sooner rather than later would produce around 40 TB of information and this number is growing speedily [9]. The SDN architecture, modes, technologies, and opportunities are shown in Figure 3.  
The rising and promising global view of SDNs show a potential answer for these vehicular system administration challenges [10]. SDNs have been created, and in this way conveyed, for wired systems. However, recently there has been increased enthusiasm towards sending SDNs for both remote and specially appointed areas. This has increased the enthusiasm of the scholarly network to investigate the probability of planning SDN-based VANETs which not only empower security and highest data transfer capacity correspondence administrations, but also provide low inactivity to the well-being of basic VANET applications and programs [11].