## 2 System Overview
### oneM2M Technology Standard  
Connected devices have been around for a long time, but they took off after the phrase \"Internet of Things\" (IoT) was established. As IoT devices began to proliferate, a standard was needed to satisfy new IoT requirements without rewriting pieces that previously had tried and verified specifications. The oneM2M-based platform was built with these concepts in mind to facilitate IoT device and application interoperability and economies of scale. Furthermore, oneM2M's standard interoperability testing activities are important aspects of a robust standard [17]. The oneM2M standards support IoT applications to discover and interact with any IoT devices. IoT solutions can currently communicate across various silos. This is perfect for distributed and collaborative solutions in domains like smart buildings, smart cities, and smart manufacturing. Furthermore, oneM2M standards were created with the goal of reducing fragmentation, increasing reusability, and lowering costs through scalability [18]. The oneM2M initiative has been working on IoT standards to address fragmentation in the IoT landscape. It focuses on service layer interoperability rather than protocol stacks within the network or internet layers, and hence provides optimal technical standards for building a common horizontal IoT service platform across several domain sectors [19]. The authors used IoT based on oneM2M platforms in the cleanroom of a semiconductor smart factory environment to obtain reliability, validity, and interoperability of data [20]. We can have a common service capability layer in terms of the end-to-end platform with this technology. In the oneM2M standard, message queuing telemetry transport (MQTT) plays a vital role in collecting and sending sensor data. MQTT is a lightweight application layer protocol for IoT devices. MQTT is a \"publish\" and \"subscribe\" protocol in which the sender can deliver information to clients via an intermediary server known as a broker. Each published  
Figure 1: General architecture of this study. message has a single topic that clients used to subscribe to a broker. The sole broker defined in the MQTT protocol standard acts as the single point of failure (PoF). Numerous brokers are introduced into a system to increase availability. The IoT platform containing MQTT broker is depicted in Figure 2.  
In addition, M2M technology facilitates work by enabling real-time replies on complicated provider networks, such as those found in factories. Real-time control and command with crucial technologies add functions and advantages to supply chain optimization and automation. As a result, use cases should be evaluated via the standard oneM2M technology with real-time command and control [21]. Furthermore, this technology must be incorporated into the current protocol standards. Additionally, oneM2M complies with the international M2M and IoT standards with the goal of creating a single M2M service layer, as shown in Figure 3. It would enable the integration of a wide range of hardware, software, and countless devices from around the world into a system combining M2M-related fields of business into a serviceable system, including telematics, smart transportation, health care, utilities, industrial automation, and smart home applications. The oneM2M model is a decentralized design that is relatively easy to modify, as shown in Figure 3. Connecting nodes with diverse capabilities construct it. The device  
Figure 3: The oneM2M architecture model. Figure 2: IoT platform design and architecture with MQTT. component of the IoT or any logical hardware and software service might be defined as an application entity (AE) in this architecture. The oneM2M service core, the IoT gateway, and the AE application service are all managed by the infrastructure node (IN). It is typically set up on a cloud system platform or server. The IN is the in-charge of the middle layer region with several middle nodes (MNs) that serve IoT service layers and AE application services.