## 1 Introduction  
The collaborative Internet of Things (IoT) technology venture enhances scalability and mobility support for compatible devices and users. IoT application services must correctly schedule network traffic and distribution intervals to prevent latency-less service distributions. Software-defined network (SDN) traffic classification capabilities and network virtualizations in IoT services provide more reliable scheduling. As a result, the distribution and widespread use of the IoT platform is managed without sacrificing service quality [1, 2]. In addition, scheduling is performed for services customized to a given application to minimize resource stagnation and user waiting times. The SDN correctly distinguishes between user requirements, service availability, and distribution using software-based controls and control plane instructions [3]. Essential power requirements must be met for IoT environment's gadgets to operate smoothly. As a result, power management and allocation became important study areas for IoT service deployments [4]. Power distribution, conservation, and harvesting are essential components of energy management. Based on IoT and SDN concepts, unnecessary power distribution and allocations are limited [5]. Power control and management extend their useful lives by preserving the devices' remaining energy. As a result, the device's responsiveness and widespread use are preserved,making the smooth dissemination of IoT services more dependable [6]. Resource and user-centric power management and allocation techniques have been proposed for large-scale applications that require energy-efficient services. Consequently, IoT power management is integrated with resource distribution and allocation procedures, necessitating machine or SDN-based optimization [7]. The OpenFlow Protocol facilitates communication between the controller and the data plane in an SDN-based cloud environment. It decouples the network from individual switches and lets administrators remotely control routing tables and centralized packet-switching choices. This allows switches and data centers to be programmed independently [8]. Instead of a central server or cloud, predictions and data analysis are increasingly used at the edge to draw conclusions and take preventative measures [9]. The IoT is now heavily ingrained in our everyday lives and significantly impacts many aspects of our lifestyle, including how we drive, shop, and even decide what to eat and avoid, preserving our health. Flexible, agile, and adaptive IoT architecture is required due to the variety of applications associated with the IoT [10]. The design of an IoT architecture based on the SDN incorporates intelligent management functions by separating the control plane from the data plane to satisfy this requirement [11]. Nevertheless, most of the current studies in this sector focus on a particular area, which encourages researchers and engineers to provide comprehensive guidance on growth and direction for the future [12]. By switching from an open-loop to a closed-loop approach, the suggested strategy seeks to improve resource allocation efficiency and user experience in IoT networks by putting the user at the center of the network [13]. To improve traffic control and maintainability, the IoT application has recently included virtualization of resources and network control using software-defined networking policies. To enable the adjustments, though, the IoT and software-defined networking needs must coincide [14]. The IoT environment consists of heterogeneous devices, applications, and communication modes for aiding large-scale user-specific services. The computation, analytical, and visualization features are either built-in or acquired from different platforms [15]. Mobile customers can now receive real-time services on wireless networks thanks to the convergence of the IoT and SDN. The centralized control provided by the SDN optimizes resource allocation, guaranteeing reliable connectivity and effective communication between servers and IoT devices.