Distributed file management system and method based on hon gming, eular and ubuntu system

Abstract

The application relates to a distributed file management system and method based on a Hongmeng, Euler and Ubuntu system. The system can realize networking between nodes of three systems of the Hongmeng, Euler and Ubuntu systems. Networking between nodes of the Hongmeng and Euler systems is realized based on a soft bus and a distributed data service function, networking of other devices on the Ubuntu system is realized based on a self-defined protocol, so that reliable transmission and synchronization of data are realized. The system can be compatible with nodes of the three different systems and provide a unified file tree view, so that file creation, deletion, modification and real-time synchronization to other devices can be conveniently realized. The system provides a file management function based on a web interface, and the architecture of networking can also be managed through the web interface.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of distributed file management, and in particular to a distributed file management system and method based on the Hongmeng, Euler and Ubuntu systems. BACKGROUND

[0002] With the rapid development of the Internet of Things, edge computing and intelligent terminal devices, a computing task often needs to be completed by multiple different types of devices in collaboration, thus forming a distributed computing environment. In these environments, devices can run different operating systems to meet their specific application scenarios and resource constraints. For example, in smart home, industrial Internet of Things or smart vehicle scenarios, devices with rich user interfaces and strong interactivity (such as smart screens and mobile phones) can run the Huawei Hongmeng system; control devices with high real-time and reliability requirements (such as industrial computers and gateways) can run the Huawei Euler embedded system based on Linux; and servers or workstations that undertake complex data analysis and storage tasks can run general Linux distributions such as Ubuntu.

[0003] However, the coexistence of such heterogeneous operating systems brings significant technical challenges, especially in terms of distributed file management. An ideal distributed file system should provide a unified, logically consistent file tree view for all networking devices in the network, and users or applications can transparently create, delete and modify files on any node as if they were operating local files, and ensure that these operations can be synchronized in real time or near real time to other related devices in the network.

[0004] Currently, the above three systems have deficiencies in distributed file management:

[0005] Huawei Hongmeng system: Its core advantage lies in realizing self-discovery and low-latency, high-bandwidth communication between homogeneous Hongmeng devices through "soft bus" technology. However, the Hongmeng system does not open source the core source code of its distributed file management, making it difficult for third-party developers or systems to deeply integrate or extend it to non-Hongmeng devices. Its file synchronization mechanism is mainly limited within the Hongmeng ecosystem and cannot be seamlessly integrated with external systems.

[0006] Huawei Euler system: As an operating system for server and embedded scenarios, the Euler system also does not provide an open source, standardized distributed file management solution. Although it can deploy traditional network file systems such as NFS and Samba as a Linux distribution, these systems often require complex configuration and cannot provide a unified view and intelligent synchronization capability across heterogeneous networks, especially when mixed with Hongmeng and Ubuntu devices, compatibility and efficiency issues are prominent.

[0007] Ubuntu system: As a mature general-purpose operating system, Ubuntu has a rich selection of distributed file systems such as Ceph, GlusterFS, etc. However, these systems are usually designed for data center environments and have heavy architecture and high resource consumption, which is not suitable for deployment on resource-constrained edge devices (such as devices running HarmonyOS or Euler). In addition, they are also unable to natively adapt to the soft bus protocol of HarmonyOS, making it difficult to achieve efficient and adaptive file synchronization in a hybrid network.

[0008] In summary, the prior art lacks a distributed file management solution that can effectively bridge the three systems of HarmonyOS, Euler, and Ubuntu, and provide a unified file view and efficient synchronization mechanism. This results in complex and inefficient file management in a mixed device networking environment, which cannot meet the requirements of modern distributed applications for data consistency, convenient access, and cross-platform compatibility.

[0009] Therefore, there is an urgent need in the art for an innovative technical solution to solve the above technical problems. SUMMARY

[0010] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0011] The main purpose of the embodiments of the present disclosure is to propose a distributed file management system and method based on HarmonyOS, Euler, and Ubuntu systems, aiming to provide a global and unified file tree view for a network composed of nodes of the three heterogeneous operating systems, and to realize the transparency and real-time synchronization of file creation, deletion, modification, etc. operations, while ensuring the efficiency and stability of cross-system communication.

[0012] In a first aspect, the present application provides a distributed file management system based on HarmonyOS, Euler, and Ubuntu systems, the system comprising:

[0013] a center node for managing group nodes;

[0014] a plurality of group nodes, including a first group node of a HarmonyOS system, a second group node of an Euler system, and a third group node of an Ubuntu system; any two third group nodes, a third group node and another two group nodes are networked through a custom protocol; any two second group nodes, any two first group nodes, and a second group node and a first group node are networked through a soft bus; the third group node and the center node are networked through a custom protocol, and the second group node and the first group node are networked with the center node through a soft bus or a custom protocol;

[0015] A plurality of groups of end nodes, at least including a first group of end nodes of a Harmony system, a second group of end nodes of an Euler system, and a third group of end nodes of an Ubuntu system, any one of the end nodes in the first group of end nodes is networked with a corresponding first group of nodes through a soft bus, any one of the end nodes in the second group of end nodes is networked with a corresponding second group of nodes through the soft bus, and any one of the end nodes in the third group of end nodes is networked with a corresponding third group of nodes through a self-defined protocol; the group nodes are obtained through end node election;

[0016] The third group of nodes includes:

[0017] a web server configured to provide web services;

[0018] a self-defined networking module configured to network with other nodes through a self-defined protocol;

[0019] a file management module connected with the web server and the self-defined networking module, and configured to perform distributed file management;

[0020] The first group of nodes and the second group of nodes both include:

[0021] a web server configured to provide web services;

[0022] a self-defined networking module configured to network with nodes of the Ubuntu system through a self-defined protocol;

[0023] a soft bus networking module configured to network with nodes of the Harmony system or the Euler system through a soft bus;

[0024] a file management module connected with the web server, the soft bus networking module, and the self-defined networking module, and configured to perform distributed file management.

[0025] The distributed file management system based on the Harmony, Euler, and Ubuntu systems provided in the embodiment has at least the following beneficial effects:

[0026] The distributed file management system can seamlessly integrate the three heterogeneous operating systems of the Huawei Harmony, Euler, and Ubuntu, and has the advantages of providing a unified file view, simplifying user operations, and ensuring the performance and reliability of cross-platform file management through intelligent message routing and an efficient synchronization mechanism.

[0027] In some embodiments, the first group of nodes, the second group of nodes, and the third group of nodes both include:

[0028] The node information synchronization module is connected with the file management module in the corresponding group node, and is used for synchronizing the node state information and the networking configuration information with other nodes through a self-defined protocol.

[0029] In some embodiments, the first group node, the second group node and the third group node each further comprise:

[0030] The configuration management module is connected with the file management module in the corresponding group node, and is used for realizing centralized configuration management according to the file management module in the corresponding group node.

[0031] In some embodiments, the first group node, the second group node and the third group node each further comprise:

[0032] The node management service module is connected with the file management module in the corresponding group node, and is used for realizing information conversion of the web server and the file management module in the corresponding group node.

[0033] In some embodiments, the self-defined protocol is an upd protocol.

[0034] In some embodiments, when the center node is a Hongmeng system or an Euler system, the second group node and the first group node are networked with the center node through a soft bus; when the center node is an ubuntu system, the second group node and the first group node are networked with the center node through a self-defined protocol.

[0035] The second aspect of the application provides a distributed file management method based on Hongmeng, Euler and ubuntu systems applied to the first aspect, which is applied to any one end node and comprises the following steps:

[0036] Receiving a distributed file management request;

[0037] When the target node corresponding to the distributed file management request is not the node, judging the type of the target node;

[0038] When the type of the target node is an end node, forwarding a message corresponding to the distributed file management request to one group node corresponding to the target node, so that the one group node judges whether the target node is an end node of the group, and when the target node is an end node of the group, forwards the message to the target node, so that the target node executes an operation corresponding to the distributed file management request and returns an execution result;

[0039] In a case where the type of the target node is a group node corresponding to the node, the message is forwarded to the corresponding group node, so that the corresponding group node judges whether the target node is an end node of the group, and in a case where the target node is an end node of the group, the message is forwarded to the target node, so that the target node performs an operation corresponding to the distributed file management request and returns an execution result.

[0040] In a case where the type of the target node is a center node, the message is forwarded to the corresponding group node, so that the corresponding group node sends the message to the center node, so that the center node finds the target node, and the center node forwards the message to the target node, so that the target node performs an operation corresponding to the distributed file management request and returns an execution result.

[0041] In some embodiments, the center node forwards the message to the target node, comprising:

[0042] In a case where the target node is a group node, the center node forwards the message to the target node;

[0043] In a case where the target node is an end node, the center node forwards the message to the corresponding group node of the target node, so that the corresponding group node forwards the message to the target node.

[0044] In some embodiments, in a case where the target node corresponding to the distributed file management request is the node, an operation corresponding to the distributed file management request is performed.

[0045] In some embodiments, the distributed file management request comprises at least one of the following items:

[0046] Creation, modification, deletion, backup, synchronization, attribute viewing, preview, download, movement, copy, search and upload of files / folders.

[0047] Additional aspects and advantages of the present application will be in part apparent and in part pointed out hereinafter. BRIEF DESCRIPTION OF DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments or related technical description. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0049] Figure 1 This is a schematic diagram of the structure of a distributed file management system based on HarmonyOS, Euler, and Ubuntu systems provided in an embodiment of this application;

[0050] Figure 2 This is a block diagram illustrating the interaction between Ubuntu systems provided in an embodiment of this application;

[0051] Figure 3 This is a block diagram illustrating the interaction between the HarmonyOS or Euler system and the Ubuntu system, as provided in an embodiment of this application.

[0052] Figure 4 This is an interaction block diagram between HarmonyOS or Euler systems provided in the embodiments of this application;

[0053] Figure 5 This is a flowchart of a distributed file management method based on HarmonyOS, Euler, and Ubuntu systems provided in an embodiment of this application. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0055] In the description of this application, the use of terms such as "first," "second," etc., is for the purpose of distinguishing technical features only and should not be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated or the order of the technical features indicated.

[0056] In the description of this application, it should be understood that the orientation descriptions, such as up, down, etc., are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed or function in a specific orientation, and therefore should not be construed as a limitation of this application.

[0057] like Figure 1 As shown in one embodiment of this application, a distributed file management system based on HarmonyOS, Euler, and Ubuntu systems is provided. This system includes:

[0058] The central node is used to manage group nodes;

[0059] Multiple group nodes, including the first type of group node of the HarmonyOS system, the second type of group node of the Euler system, and the third type of group node of the Ubuntu system; any two third type group nodes are networked with each other, and any third type group node is networked with the other two types of group nodes via a custom protocol; any two second type group nodes are networked with each other, any two first type group nodes are networked with each other, and any second type group node is networked with the first type of group node via a soft bus; the third type group node is networked with the central node via a custom protocol, and the second type group node and the first type of group node are networked with the central node via a soft bus or a custom protocol, respectively.

[0060] Multiple groups of end nodes, including at least the first group of end nodes from the HarmonyOS system, the second group of end nodes from the Euler system, and the third group of end nodes from the Ubuntu system. Any end node in the first group can network with the corresponding first-type group of end nodes via a soft bus. Any end node in the second group can network with the corresponding second-type group of end nodes via a soft bus. Any end node in the third group can network with the corresponding third-type group of end nodes via a custom protocol. Group nodes are elected by end node election.

[0061] The third type of group node includes:

[0062] A web server is used to provide web services.

[0063] A custom networking module is used to form a network with other nodes using custom protocols;

[0064] The file management module connects to the web server and a custom networking module for distributed file management.

[0065] Both the first and second types of group nodes include:

[0066] A web server is used to provide web services.

[0067] A custom networking module for networking nodes using custom protocols and the Ubuntu system;

[0068] The soft bus networking module is used to network with nodes of the HarmonyOS or Euler systems via a soft bus.

[0069] The file management module connects to the web server, soft bus networking, and custom networking modules for distributed file management.

[0070] This embodiment involves networking multiple nodes (devices), which mainly include three types: nodes using the HarmonyOS system, nodes using the Euler system, and nodes using the Ubuntu system; the networking mainly includes:

[0071] Multiple end nodes are the actual carriers for file storage and operations, such as mobile phones, sensors, cameras, and personal computers. End nodes only need to maintain connections with their directly subordinate group nodes and do not need to be aware of the global network topology, which greatly simplifies the logic and resource consumption of end nodes.

[0072] Multiple group nodes (also called intermediate nodes) are configured. These group nodes must include at least three types: one using the HarmonyOS system, one using the Euler system, and one using the Ubuntu system. For example, there might be two of the first type, two of the second type, and two of the third type. Each group node is the backbone of the distributed file management system, responsible for managing its subordinate end nodes. It's important to note that all end nodes managed by a single group node use the same system; for example, all end nodes managed by a first-type group node might use the HarmonyOS system. A group node can be an end node; for instance, based on the performance of various end nodes, the best-performing end node can be selected as the group node.

[0073] The network also includes a central node, which serves as the logical core of the system and is responsible for managing all group nodes within the network. It maintains global node topology information and coordinates large-scale file synchronization tasks across groups. The central node can be a high-performance server, and its operating system can be HarmonyOS, Euler, or Ubuntu. The central node does not directly manage a large number of end nodes; instead, it is responsible for maintaining the registration information, status information, and global file namespace mapping relationships of all group nodes. When large-scale file synchronization or searching across multiple groups is required, the central node is responsible for coordination.

[0074] The networking method is the key innovation of this system:

[0075] Networking can be achieved between any two third-type nodes (Ubuntu-Ubuntu) and between a third-type node and a first or second-type node (Ubuntu-Harmony / Euler) through a lightweight custom protocol (such as a reliable protocol optimized based on UDP).

[0076] Any two Type 1 nodes (HarmonyOS-HarmonyOS), any two Type 2 nodes (Euler-Euler), and any two Type 1 and Type 2 nodes (HarmonyOS-Euler) can network using their natively supported soft bus technology to achieve optimal communication performance. The soft bus provides the capabilities for device self-discovery, authentication, and high-speed data transmission.

[0077] The connection method between the central node and the group nodes adapts to the type of the central node: if the central node is a HarmonyOS or Euler system, the first and second type group nodes connect to it via a soft bus; if the central node is an Ubuntu system, they connect to it via a custom protocol. The third type group node (Ubuntu) always connects to the central node via a custom protocol.

[0078] In this embodiment, nodes in the Ubuntu system are connected to any other node via a custom protocol, such as the UPD protocol. Taking the third group of nodes in the Ubuntu system as an example, the third group node is connected to the first group node, the second group node, any end node, or the central node via a custom protocol.

[0079] Furthermore, the third type of group node (Ubuntu) architecture includes:

[0080] Web Server: Provides a web service interface, allowing users to perform visual file management and system monitoring through a browser. It can be implemented using frameworks such as Nginx, Apache, or the lightweight Python Flask. It provides a RESTful API interface for web front-end calls. Users can access this web interface through a browser to perform operations such as uploading and downloading files, creating and deleting files, and viewing synchronization status.

[0081] Custom networking module: Responsible for enabling communication with other nodes (including other Ubuntu nodes, Harmony / Euler nodes, and the central node) based on a custom protocol.

[0082] The file management module, as the core, interacts with the Web Server and custom networking modules, handling all distributed file operation logic, such as metadata management, file block synchronization, and conflict resolution. For example, it executes the following process:

[0083] Maintain a metadata database for all end nodes in the group (e.g., filename, path, size, modification time, version number, storage location, etc.), which forms the foundation of a unified file tree view. When a file change (e.g., modification, addition) is received, the target node to be synchronized is determined, and a synchronization task is initiated through a custom networking module. For large files, a chunked transmission method may be used to improve efficiency and reliability; this module is responsible for file chunking, transmission scheduling, and reassembly. Verify that file operation requests from the web or network client have the appropriate permissions.

[0084] The architectures of the first and second types of nodes (HarmonyOS / Euler) are more complex, in order to handle dual protocol stacks:

[0085] Web Server: Functionally the same as the third type of group node.

[0086] Custom networking module: Used to communicate with nodes on the Ubuntu system.

[0087] Soft bus networking module: Used for high-performance communication with nodes belonging to the HarmonyOS or Euler system.

[0088] The file management module integrates a dual-protocol stack, enabling it to select the appropriate communication path (soft bus or custom protocol) for file operations based on the target node type. Compared to the group nodes in the Ubuntu system, it adds protocol selection logic. When it needs to send a message or file to a target node, it first queries the local node routing table. If the target node is a HarmonyOS or Euler system node, it selects to send via the soft bus networking module; if the target node is an Ubuntu device, it selects to send via the custom networking module. This intelligent routing ensures the optimization of the communication path.

[0089] like Figure 1 Preferably, all types of group nodes may also include the following modules to enhance system functionality:

[0090] Node information synchronization module: Used to synchronize node status (online, offline, load) and network configuration information among group nodes through a custom protocol to maintain the consistency of the global view.

[0091] Configuration Management Module: Enables centralized configuration management of the system, such as synchronization policies and access permissions.

[0092] Node Management Service Module: Serves as an adaptation layer between the Web Server and the File Management Module, performing protocol conversion and data encapsulation.

[0093] Therefore, the system provided in this embodiment can achieve:

[0094] It is compatible with three different systems and provides a unified file tree view. It offers the same secondary development interface, facilitating file creation, deletion, modification, and real-time (network-dependent) synchronization to other devices. It provides identical web-based node and file management functions. Each node automatically forms a network based on a configuration file (the network architecture consists of one central node, multiple group nodes under the central node, and multiple end nodes under each group node; the central node manages the group nodes, and the group nodes manage the end nodes). The network architecture can be arbitrarily adjusted through the node management function in the web interface. When a group node loses connection or fails during operation, a new group node is automatically elected from the end nodes under the group. Files on each node can be manipulated through the web interface, supporting functions such as adding, deleting, modifying, querying, downloading, and uploading files. On HarmonyOS and Euler systems, it is implemented based on a soft bus and distributed data service, ensuring network flexibility and stability, as well as reliable data transmission and synchronization. On Ubuntu, it uses a custom communication protocol based on a custom protocol to ensure reliable data transmission. It uses an open-source file transfer protocol to reliably synchronize files across the three systems.

[0095] One embodiment of this application provides a corresponding distributed file management method for the aforementioned distributed file management system based on HarmonyOS, Euler, and Ubuntu systems, applicable to any end node. The method includes:

[0096] Step S110: Receive a distributed file management request.

[0097] Step S120: If the target node corresponding to the distributed file management request is not this node, determine the type of the target node.

[0098] Step S130: If the target node is an end node, forward the message corresponding to the distributed file management request to a group node corresponding to the target node, so that the corresponding group node can determine whether the target node is an end node of the group. If the target node is an end node of the group, forward the message to the target node so that the target node can execute the operation corresponding to the distributed file management request and return the execution result.

[0099] Step S140: If the target node is a group node corresponding to this node, the message is forwarded to the corresponding group node so that the corresponding group node can determine whether the target node is an end node of the group. If the target node is an end node of the group, the message is forwarded to the target node so that the target node can execute the operation corresponding to the distributed file management request and return the execution result.

[0100] Step S150: If the target node is a central node, the message is forwarded to the corresponding group node so that the corresponding group node sends the message to the central node so that the central node finds the target node and forwards the message to the target node so that the target node executes the operation corresponding to the distributed file management request and returns the execution result.

[0101] The method provided in this embodiment has at least the following beneficial effects:

[0102] This method not only provides a unified file view, simplifying user operations, but also ensures the performance and reliability of cross-platform file management through intelligent message routing and efficient synchronization mechanisms.

[0103] like Figures 1 to 4 To facilitate understanding, the following is a distributed file management system based on HarmonyOS, Euler, and Ubuntu systems. The system mainly implements the following two functions:

[0104] (1) Implement networking functionality for three systems: HarmonyOS, Euler, and Ubuntu. HarmonyOS and Euler use the soft bus function for networking, while Ubuntu uses a custom protocol for networking. Network compatibility is achieved among the three systems, and networking can be managed through a web interface.

[0105] (2) Distributed file management software management function: Based on the network, it realizes the functions of uploading, downloading, creating, deleting, modifying and synchronizing files on each node on the web interface, and provides the same file processing interface for users to develop secondary applications.

[0106] The following two main functions are explained separately:

[0107] I. Implement networking functionality.

[0108] like Figure 1 , Figure 1 The network diagram is divided into three layers. The central node is the management center, and there is only one node. It is the first layer and manages all group nodes. There are multiple group nodes, which belong to the second layer and manage the end nodes connected to them. There are also multiple end nodes, which are managed by the group nodes connected to them. Each node is an independent device and can be configured to form a wired or wireless network.

[0109] Each node has the same configuration file. The nodes interconnect according to this configuration file. A web-based interface displays the network view, allowing users to add, delete, modify, and query individual network nodes. Modified network configuration files are synchronized via distributed data services (HarmonyOS and Euler) and open-source file transfer protocols (Ubuntu). When a node reconnects after a disconnection, it automatically synchronizes the network configuration file. If a group node loses communication, a new group node will be elected from its connected end nodes within one minute.

[0110] II. The process of communication between nodes.

[0111] Both HarmonyOS and Euler systems use a soft bus for communication, so they are grouped together. Ubuntu uses a custom protocol for communication, so it is grouped into another category. Therefore, there are three types of communication between them: communication between Ubuntu systems, communication between HarmonyOS and Euler systems, and communication between Ubuntu and HarmonyOS or Euler systems. The communication processes are as follows:

[0112] First: Communication between Ubuntu systems.

[0113] like Figure 2 As shown, Figure 2 The left and right sides of the diagram both represent Ubuntu systems. The distributed file management software on these systems has identical diagrams. The systems communicate with each other via a custom UDP-based protocol. The web server provides visualization of scene file metadata and supports a view management UI interface. The node management server facilitates information conversion between the web server and the distributed file management module. The distributed file management module obtains network information and node status information through the network information management module and the node information synchronization module. The network information management module obtains network and network status information through a custom protocol. The node information synchronization module synchronizes node status information and network configuration information with each node through a custom protocol. The configuration management module implements centralized configuration management through the distributed file management module.

[0114] Second: Communication between HarmonyOS or Euler systems.

[0115] like Figure 3 As shown, Figure 3 The left and right sides both display either HarmonyOS or Euler OS, and the distributed file management software deployed on them has the same block diagram. The systems communicate with each other via a soft bus, with the soft bus function application module replacing... Figure 2The application module replaces the node information synchronization module in Ubuntu, enabling rapid synchronization of node status information and network configuration information. Other functional modules are the same as those on the Ubuntu system.

[0116] Third: Communication between the Ubuntu system and HarmonyOS or Euler systems.

[0117] like Figure 4 As shown, Figure 4 The left half of the diagram shows the structure of a distributed file management software deployed on an Ubuntu system, while the right half shows the structure of a distributed file management software deployed on HarmonyOS or Euler. Compared to the left half, the right half includes a soft bus function application module, a distributed data service function application module, and a soft bus module.

[0118] Since Ubuntu lacks a software bus, HarmonyOS and Euler systems communicating with it cannot use software bus functionality application modules and distributed data service application modules (based on software bus). They need to deploy the same distributed file management software functionality modules as Ubuntu. Furthermore, because HarmonyOS or Euler networks not only with Ubuntu but also with other HarmonyOS or Euler systems, the software bus functionality application modules, distributed data service application modules, and software bus functionality also need to be included in this network.

[0119] III. Distributed file management.

[0120] This system provides distributed file management, mainly consisting of two parts: command operations and file transfer. The command operations are as follows:

[0121] The distributed file management software runs a control service program in all networked systems. All operation commands are processed according to this process, including file / folder creation, modification, deletion, backup, synchronization, attribute viewing, preview, download, move, copy, search, and upload functions.

[0122] like Figure 5 The specific process of the operation instruction is as follows: when a certain end node receives a user operation instruction, the distributed file management software control service program in the file management module first matches the target information (IP address) in the instruction with the information of this node. If the target node is this node, the instruction operation is executed and the execution result is returned to the source end (user end), and the operation ends.

[0123] When the target information (IP address) in the instruction does not match the information of this node, the type of the current node is determined. There are three node types: end node, group node, and center node. If the current node is determined to be an end node, the instruction is sent to the group node. The group node then determines whether the target node is within its group. If the target node is within its group, it forwards the instruction to the target node within that group for processing. Otherwise, based on the target node information, the instruction is forwarded to the group node of the target node's group, and the group node forwards it to the target node for processing. If the current node is a group node, it determines whether the target node is within its group. If it is, the instruction is sent to the target node for processing. If it is not, the instruction is forwarded to the group node of the target node's group, and the group node forwards it to the target node for processing. Similarly, if the current node is a center node, the instruction is matched with the group node of the target node's group within the center nodes, and the group node forwards it to the target node for processing. If the target node (including group nodes) is not found in the center nodes, the operation fails and an error code is returned to the source (user end). This enables distributed file operations, allowing files on each node to be accessed and manipulated by all nodes.

[0124] Network data involving Ubuntu systems is transmitted using a custom protocol, while data from HarmonyOS or Euler systems is transmitted via a soft bus. File synchronization and transfer functions are implemented end-to-end through an open-source file transfer protocol across all three systems.

[0125] Consider this scenario: An end node -A (HarmonyOS) belonging to group node -G1 (HarmonyOS) wants to delete a file stored on an end node -C (Ubuntu) belonging to group node -G3 (Ubuntu).

[0126] End node-A issues a file deletion request, with end node-C specified as the target node;

[0127] End node -A determines that the target is not itself and that the target type is an end node, so it sends the request message to its group node G1;

[0128] Group node G1 queries the routing table and finds that end node -C is managed by group node G3. Since G1 (HarmonyOS) and G3 (Ubuntu) are different systems, they communicate with each other through a custom protocol;

[0129] Group node G1 sends messages to group node G3 through its custom networking module;

[0130] After receiving the message, group node G3 confirms that end node -C is its subordinate, and then forwards the deletion request to end node -C through a custom protocol;

[0131] The end node -C performs a file deletion operation. Upon successful execution, it generates the execution result.

[0132] The execution result is returned in reverse along the original path: End node - C -> Group node - G3 -> Group node - G1 -> End node - A;

[0133] At this point, the application on end node -A received a notification that the file was successfully deleted.

[0134] This embodiment has at least the following beneficial effects:

[0135] (1) Through the dual-mode networking scheme of "soft bus + custom protocol", the three major systems HarmonyOS, Euler and Ubuntu are effectively bridged, solving the problem that they cannot work together efficiently due to the isolation of their technical ecosystem.

[0136] (2) The system abstracts a unified logical file tree for all devices in the network. Regardless of which device or system a user is on, they can access and manage distributed files in a consistent manner, which greatly improves user experience and management efficiency.

[0137] (3) It fully utilizes the high performance of the HarmonyOS / Euler device soft bus, and at the same time designs an efficient lightweight protocol for Ubuntu devices, ensuring low latency and high throughput synchronization of file operations, and is less affected by network fluctuations.

[0138] (4) The hierarchical architecture (central node - group node - end node) makes the system easy to expand. The election mechanism of group nodes and the node information synchronization module ensure the system's self-healing ability and service continuity when some nodes fail.

[0139] (5) The built-in Web Server provides a user-friendly graphical management interface, which makes it easy for administrators to monitor system status, manage configurations and perform file operations, thus reducing operation and maintenance costs.

Claims

1. A distributed file management system based on the systems of Hongmeng, Euler and Ubuntu, characterized in that, The system comprises: a center node for managing group nodes; a plurality of group nodes, including a first group node of a Hongmeng system, a second group node of an Euler system, and a third group node of an Ubuntu system; any two third group nodes, a third group node and another two group nodes are networked through a self-defined protocol; any two second group nodes, any two first group nodes, and a second group node and a first group node are networked through a soft bus; a third group node and the center node are networked through a self-defined protocol, and a second group node and a first group node are networked with the center node through a soft bus or a self-defined protocol; a plurality of group end nodes, including at least a first group end node of the Hongmeng system, a second group end node of the Euler system, and a third group end node of the Ubuntu system, any one end node in the first group end node is networked with a corresponding first group node through a soft bus, any one end node in the second group end node is networked with a corresponding second group node through a soft bus, and any one end node in the third group end node is networked with a corresponding third group node through a self-defined protocol; the group nodes are obtained through end node election; the third group node comprises: a web server for providing web services; a self-defined networking module for networking with other nodes through a self-defined protocol; a file management module connected with the web server and the self-defined networking module for distributed file management; the first group node and the second group node each comprise: a web server for providing web services; a self-defined networking module for networking with nodes of the Ubuntu system through a self-defined protocol; a soft bus networking module for networking with nodes of the Hongmeng system or the Euler system through a soft bus; a file management module connected with the web server, the soft bus networking module, and the self-defined networking module for distributed file management. 2.The distributed file management system based on the systems of Hongmeng, Euler and Ubuntu according to claim 1, wherein, The first group node, the second group node, and the third group node each further comprise: a node information synchronization module connected with the file management module in the corresponding group node, the node information synchronization module being used for synchronizing node state information and networking configuration information with other nodes through a self-defined protocol. 3.The distributed file management system based on the systems of Hongmeng, Euler and Ubuntu according to claim 2, characterized in that, The first group node, the second group node, and the third group node each further comprise: a configuration management module connected with the file management module in the corresponding group node, the configuration management module being used for realizing centralized configuration management according to the file management module in the corresponding group node.

4. The distributed file management system based on the systems of Hongmeng, Euler and ubuntu of claim 3, wherein, The first group node, the second group node, and the third group node each further comprise: a node management service module connected with the file management module in the corresponding group node, the node management service module being used for realizing information conversion of the web server and the file management module in the corresponding group node.

5. The distributed file management system based on the systems of Hongmeng, Euler and ubuntu of claim 1, characterized in that, The self-defined protocol is an upd protocol.

6. The distributed file management system based on the systems of Hongmeng, Euler and ubuntu of claim 1, wherein, In the case that the center node is the Hongmeng system or the Euler system, the second group node and the first group node are networked with the center node through a soft bus; in the case that the center node is the Ubuntu system, the second group node and the first group node are networked with the center node through a self-defined protocol.

7. A distributed file management method based on the Harmony, Euler and Ubuntu systems, characterized in that, The method is applied to the distributed file management system based on the Hongmeng, Euler and Ubuntu system as claimed in any one of claims 1 to 6, and is applied to any one end node, and the method comprises: receiving a distributed file management request; in the case where the target node corresponding to the distributed file management request is not the local node, judging the type of the target node; in the case where the type of the target node is an end node, forwarding a message corresponding to the distributed file management request to a group node corresponding to the target node, so that the corresponding group node judges whether the target node is the corresponding end node, and in the case where the target node is the corresponding end node, forwards the message to the target node, so that the target node executes an operation corresponding to the distributed file management request and returns an execution result; in the case where the type of the target node is a group node corresponding to the local node, forwarding the message to the corresponding group node, so that the corresponding group node judges whether the target node is an end node of the group, and in the case where the target node is an end node of the group, forwards the message to the target node, so that the target node executes an operation corresponding to the distributed file management request and returns an execution result; in the case where the type of the target node is a center node, forwarding the message to the corresponding group node, so that the corresponding group node sends the message to the center node, so that the center node finds the target node, and the center node forwards the message to the target node, so that the target node executes an operation corresponding to the distributed file management request and returns an execution result. 8.The distributed file management method based on the systems of Hongmeng, Euler and Ubuntu of claim 7, wherein, The center node forwards the message to the target node, comprising: in the case where the target node is a group node, the center node forwards the message to the target node; in the case where the target node is an end node, the center node forwards the message to the group node corresponding to the target node, so that the corresponding group node forwards the message to the target node.

9. The distributed file management method based on the systems of Hongmeng, Euler and Ubuntu according to claim 7, characterized in that, in the case where the target node corresponding to the distributed file management request is the local node, executing an operation corresponding to the distributed file management request.

10. The distributed file management method based on the systems of Hongmeng, Euler and Ubuntu according to claim 7, characterized in that, The distributed file management request comprises at least one of the following items: creation, modification, deletion, backup, synchronization, attribute viewing, preview, download, movement, copy, search and upload of a file / folder.

Images