## 3 ComEdge Experimental Platform
### Platform Scenario  
Figure 1 illustrates the cloud-native edge intelligence scenario where the functions of each node can be flexibly deployed on various real-world devices, such as drones, vehicles, ships, satellites, and cloud hosts in different scenarios. The physical communication methods used within the cluster are also varied, including but not limited to fiber optic, wifi, microwave, as well as different types of satellites. Moreover, despite the various underlying communication methods used, the cloud-native edgemesh [12] technology shields the complex underlying topology, enabling the platform to be agile in the allocation and scheduling of business, tasks, and resources. The majority of nodes in the system are equipped with containerized 5G base stations, and the master node deploys a containerized 5G core network, granting access to numerous 5G terminals through the  
platform's southbound interface. The platform's quick deployment on nodes with varied architectures and forms, added to the flexibility and maneuverability of actual physical nodes, alongside the integration of satellite links, greatly expands the various application scenarios of the platform.  
In the actual construction of the platform, we use five physical nodes with different architectures, computing power, and communication capabilities as the main cluster parts of ComEdge. The actual situation of each physical node is shown in Table 1.  
Meanwhile, the various nodes in the platform can operate in two working modes as needed based on the actual situation, and some devices of the ComEdge platform are shown in Figure 2.  
Mesh Mode: A network is formed between Nodes 1, 2, 3, and 4 through a wifi hotspot, with Node 1 creating the hotspot, and Nodes 2, 3, and 4 wirelessly connecting, while Node 5 joins through a wired connection, thus forming a fully functional high-availability cluster. Our platform deploys multiple master nodes to establish a high-availability cluster that adopts a master-slave architecture, with the master node in physical node 1 acting as the primary node, while the other master nodes act as secondary nodes. The primary node bears the responsibility of processing all requests and forwarding them to the secondary nodes, which receive and perform the corresponding operations. In case of failure or ineffectiveness of the primary node, the secondary nodes can automatically take over its role to ensure the high availability and reliability of the cluster. The multiple master nodes collaborate with each other and manage all components and resources in the cluster.  
\begin{table}
\begin{tabular}{l l l l} \hline \hline
**Node** & **CPU** & **Memory** & **Communication Method** \\ \hline node1 & X86/64 bit, 16 core & 126 GB & wifi; ethernet \\ node2\&3 & X86/64 bit, 8 core & 8 GB & wifi \\ node4 & ARM/64 bit, 4 core & 8 GB & ethernet \\ node5 & ARM/64 bit, 4 core & 4 GB & wifi;ethernet \\ \hline \hline \end{tabular}
\end{table}
Table 1: The actual situation of each physical node.  
Figure 2: Actual deployment of ComEdge platform.  
Standardone Mode: The standalone mode refers to the case when only one physical node is present in the system or when a task is designated to a single physical node. It proves useful in scenarios where tasks are simplistic or necessitate specific requirements for edge devices.