Unitized scheduling cloud NAS system and method

Abstract

The invention provides a unitized scheduling cloud NAS system and method, the unitized scheduling cloud NAS system comprises an edge area module, a central node, a central service platform and a central service gateway, the edge area module is a unitized architecture, the edge area module is provided with a file resource storage pool, and the edge area module comprises an edge node and an edge cloud NAS service, and the edge area module is connected with edge equipment in the service area. The central node is in signal connection with the edge area module and the central service platform. The central service platform comprises a plurality of services and functions and is used for supporting and managing various services or technical requirements. And the central service gateway is used for unified entry, request distribution and flow control. When the user equipment operates the files in the unitized scheduling cloud NAS system, interaction needs to firstly arrive at the edge node, a data viewing request is subjected to closed-loop processing at the edge node, and a file updating request triggers the operation of synchronizing user file metadata to the central node, so that lower data interaction time delay is realized, and network flow is saved.

Description

Technical Field

[0001] The present invention relates to the technical field of cloud storage devices, and more particularly to a system and method for unitized scheduling of cloud NAS. Background Art

[0002] With the improvement of fixed-line bandwidth and technological advancements, the mobile internet has begun to flourish. The types and number of devices connected to the internet, as well as the amount of data users can access from internet resources, have skyrocketed. Managing and accessing data anytime, anywhere has become a daily requirement for users. Currently, users primarily use NAS (Network-Attached Storage), an emerging storage technology, to store data on the network and access it from multiple machines. Common implementations include: 1. User-built local NAS, which provides basic services and functions based on self-purchased physical devices; 2. Cloud services, which are network storage services implemented on public or private clouds and provide some NAS functions to enterprises or individual users.

[0003] However, NAS also has some problems. First, the dispersed data storage locations may cause latency and performance issues, especially for remote users. In addition, multiple dispersed service nodes increase the complexity of management and maintenance, requiring more manpower and resources. Resource allocation may be uneven, resulting in some nodes being overused while others are idle, which may lead to resource waste. At the same time, ensuring data consistency in a dispersed environment may be more difficult and may require more data synchronization work. Finally, complex data flow management and request routing may require more network bandwidth, increasing network complexity. Therefore, unitized cloud NAS services are generally easier to manage, optimize performance, and ensure data consistency.

[0004] Unitized cloud NAS services offer multiple advantages. First, they centralize management and control, making monitoring, maintenance, and policy implementation more convenient and improving management efficiency. Furthermore, unitized cloud NAS services make it easier to optimize resource allocation, ensuring that resources are fully utilized to the greatest extent possible and reducing resource waste. Centralized services are generally easier to optimize performance to meet the demands of high loads and rapid responses. Centralized storage of data helps ensure data consistency because it is located in the same location, avoiding data inconsistencies or conflicts. Finally, centralized management strengthens data security and access control, reducing the potential for data leakage and security risks. Therefore, unitized cloud NAS services offer comprehensive benefits for management, resource utilization, performance, data consistency, and security. Summary of the Invention

[0005] To address the above issues, the present invention implements a stateless, modularized cloud NAS service. This differs from most public or private cloud-based NAS services, which primarily utilize multiple modularized deployments and can form a multi-active, multi-center architecture. This architecture supports the migration of NAS service data centers to the user side, achieving lower data interaction latency and saving network traffic. Furthermore, any cloud NAS node supports user data access, enabling cross-unit scheduling of user data access, rationally allocating user traffic, and meeting high-concurrency, high-availability system requirements, providing users with a low-latency, highly stable cloud storage solution.

[0006] The present invention provides a unitized scheduling cloud NAS system, the unitized scheduling cloud NAS system comprising:

[0007] An edge area module, wherein the edge area module is configured as a unitized architecture and is provided with a file resource storage pool;

[0008] A central node, the central node being signal-connected to the edge area module and the central service platform;

[0009] A central service platform, which includes a variety of services and functions for supporting and managing various business or technical needs;

[0010] Central service gateway, the central service gateway is connected to the central service platform signal, and the central service gateway is used for unified entry, request distribution and flow control.

[0011] In one embodiment, the central service platform includes a user service module, a user scheduling service module, a file service module, a capability exposure service module and other service modules;

[0012] The user service module is used to store user data and provide information management services and service subscription;

[0013] The user scheduling service module is used to provide user authentication, user scheduling and edge node management;

[0014] The file service module is used to provide query, management, and synchronization functions with edge cloud NAS service devices.

[0015] In one embodiment, the central node area stores metadata, and when a user accesses, the metadata is synchronized to the accessed edge node;

[0016] The file resource storage pool stores data.

[0017] In one embodiment, the edge area module includes an edge node and an edge cloud NAS service, and the edge area module is connected to the edge devices in the service area.

[0018] In one embodiment, the edge node is signal-connected to the edge cloud NAS service;

[0019] The edge node includes a plurality of single edge nodes, and the edge cloud NAS service includes a plurality of single edge cloud NAS services;

[0020] The single edge node is set corresponding to the single edge cloud NAS service.

[0021] In one embodiment, the single edge cloud NAS service is set as an independent application, the edge cloud NAS service is provided with a Docker container image, the single edge cloud NAS service is placed in a Docker container image that can be transplanted at any time, and the single edge cloud NAS service image serves as a deployment unit.

[0022] In one embodiment, the edge node is provided with a health management module, a load balancing module and a computer room monitoring and alarm module. When a single edge cloud NAS service image in the computer room fails, the health management module will automatically shut down the service and initialize a new image service. At the same time, the load balancing module will adjust the request.

[0023] In one embodiment, when the entire computer room fails, the computer room monitoring alarm module will issue a reminder, and the staff will resolve the domain name IP of the center of the fault area to the backup node or other node IP. When the backup node service receives the request, it will trigger the user's cloud file metadata initialization to the node process, provide services to the user normally, and the user will be in a seamless switching state.

[0024] In one embodiment, the central node uses the scheduling strategy of the user scheduling service module to concentrate the requests of user devices to the unitized cloud NAS edge interface, ensuring that user data is stored and accessed nearby, making the user's data request interaction delay lower and the data transmission more stable.

[0025] A unitized scheduling cloud NAS method, used in the unitized scheduling cloud NAS system, comprising:

[0026] Step S101: The user logs in to the user's cloud NAS service account using a client on the PC and accesses the central node;

[0027] Step S102: After accessing the central node, generate and distribute an access token and access the nearest edge cloud NAS service address;

[0028] Step S103: The client connects to the cloud NAS address, triggering file system initialization. At this time, the file metadata of the user file system is loaded on the edge cloud NAS service, and the entire file tree structure is at the edge node;

[0029] Step S104: User operation: the user chooses to view data and update files on the client.

[0030] In one embodiment, when a user device operates a unitized scheduling of files within a cloud NAS system, the interaction must first go to an edge node, where a request to view data is closed-loop processed, and a request to update a file triggers the synchronization of user file metadata to a central node.

[0031] In one embodiment, the updated file includes newly added file data and modified file data;

[0032] When new file data is added, the client uploads the file to the file resource storage pool of the nearest edge node, and the cloud NAS service synchronizes the file metadata changes to the central node;

[0033] When file data is modified, the cloud NAS service directly synchronizes the file metadata to the central node.

[0034] The technical solution provided by the embodiments of the present application has the following advantages:

[0035] 1. By leveraging edge cloud node resources, cloud NAS service data centers are migrated to the user side, enabling lower data interaction latency and reducing network traffic. This architecture allows data to be closer to end users, reducing round-trip data time and improving application responsiveness. It also helps reduce network load on cloud data centers, as some data processing and storage can be performed on edge cloud nodes.

[0036] 2. Unitized scheduling services, centralized file metadata management, and real-time distribution enable user request scheduling and traffic allocation, meeting high-concurrency and high-availability system requirements. This architecture emphasizes the modularization and centralized management of scheduling services, enabling the system to monitor user requests in real time and effectively allocate traffic, ensuring high availability under high concurrency. This also provides more efficient file metadata management, enabling the system to quickly retrieve and process user data requests, thus meeting the needs of highly dynamic and diverse applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 This is a schematic diagram of the structure of a unitized scheduling cloud NAS system according to one embodiment of the present invention;

[0038] Figure 2 This is a flowchart of a unitized scheduling cloud NAS method according to an embodiment of the present invention;

[0039] Figure 3 Schematic diagram of the flow of a unitized scheduling cloud NAS method according to one embodiment of the present invention;

[0040] Figure 4 A schematic diagram of cloud NAS metadata changes in a unitized scheduling cloud NAS method according to an embodiment of the present invention.

[0041] Among them, 100 is the edge area module; 110 is the file resource storage pool; 120 is the edge node; 130 is the edge cloud NAS service; 200 is the central service platform; 210 is the user service module; 220 is the user scheduling service module; 230 is the file service module; 240 is the capability exposure service module; 250 is the other service module; 300 is the central service gateway. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solutions and advantages of the implementation of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below in conjunction with the drawings in the embodiments of this application. In the drawings, the same or similar reference numerals represent the same or similar elements or elements with the same or similar functions. The described embodiments are part of the embodiments of this application, not all of the embodiments. The embodiments described below with reference to the drawings are exemplary and are intended to be used to explain this application, and should not be understood as limitations on this application. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0043] In addition, it should be noted that, unless otherwise clearly stipulated and limited, the words "install", "connect", "connect" and similar terms used in the description of this application should be understood in a broad sense. For example, the connection can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, an indirect connection through an intermediate medium, or a connection between two components. Technical personnel in the field can understand their specific meanings in this application according to the specific circumstances.

[0044] Figure 1 This is a schematic diagram of the structure of a unitized scheduling cloud NAS (Network-Attached Storage) system according to one embodiment of the present invention. The unitized scheduling cloud NAS system includes:

[0045] The edge region module 100 is configured as a unitized architecture and is provided with a file resource storage pool 110;

[0046] A central node, which is signal-connected to the edge area module 100 and the central service platform 200;

[0047] Central service platform 200, which is signal-connected to the central service gateway 300 and includes multiple services and functions for supporting and managing various business or technical needs;

[0048] The central service gateway 300 is connected to the central node or the central service platform 200 by signal. The central service gateway 300 is used for unified entry, request distribution and flow control.

[0049] In one embodiment, Figure 1 As shown, the central service platform 200 includes a user service module 210, a user scheduling service module 220, a file service module 230, a capability exposure service module 240 and other service modules 250;

[0050] The user service module 210 is used to store user data and provide information management services and service subscription;

[0051] The user scheduling service module 220 is used to provide user authentication, user scheduling and edge node 120 management;

[0052] The file service module 230 is used to provide query, management, and synchronization functions with edge cloud NAS devices.

[0053] In one embodiment, the central node area stores metadata, and when a user accesses the area, the metadata is synchronized to the edge node 120 that is accessed.

[0054] The file resource storage pool 110 stores data.

[0055] In one embodiment, the edge region module 100 includes an edge node 120 and an edge cloud NAS service 130 , and the edge region module 100 is connected to edge devices within a service area.

[0056] In one embodiment, the edge node 120 is signal-connected to the edge cloud NAS service 130;

[0057] The edge node 120 includes a plurality of single edge nodes 120 , and the edge cloud NAS service 130 includes a plurality of single edge cloud NAS services 130 ;

[0058] The single edge node 120 is configured corresponding to the single edge cloud NAS service 130 .

[0059] In one embodiment, the single edge cloud NAS service 130 is set as an independent application, the edge cloud NAS service 130 is provided with a Docker container image, the single edge cloud NAS service 130 is placed in a Docker container image that can be transplanted at any time, and the single cloud NAS service image serves as a deployment unit.

[0060] In one embodiment, the edge node 120 is provided with a health management module, a load balancing module and a computer room monitoring and alarm module. When a cloud NAS service image in the computer room fails, the health management module will automatically shut down the service and initialize a new image service. At the same time, the load balancing module will adjust the request.

[0061] In one embodiment, when the entire computer room fails, the computer room monitoring alarm module will issue a reminder, and the staff will promptly resolve the domain name IP (Internet Protocol) of the fault area center to the backup node or other node IP. When the backup node service receives the request, it triggers the user's cloud file metadata initialization to the node process, provides services to the user normally, and the user is in a seamless switching state.

[0062] In one embodiment, the central node uses a scheduling strategy to centralize user device requests to the unitized cloud NAS edge interface, ensuring that user data is stored and accessed nearby, making the user's data request interaction delay lower and the data transmission more stable.

[0063] Figure 2 This is a flowchart of a unitized scheduling cloud NAS method according to an embodiment of the present invention, which is used in the unitized scheduling cloud NAS system, including:

[0064] Step S101: The user logs in to the user's cloud NAS service account using a client on the PC and accesses the central node;

[0065] Step S102, after accessing the central node, generate and distribute an access token and access the address of the nearest edge cloud NAS service 130;

[0066] Step S103: The client connects to the cloud NAS address, triggering file system initialization. At this time, the file metadata of the user file system is loaded on the edge cloud NAS service 130, and the entire file tree structure is at the edge node 120;

[0067] Step S104: User operation: the user chooses to view data and update files on the client.

[0068] In one embodiment, when a user device operates a unitized scheduling of files in a cloud NAS system, the interaction must first go to the edge node 120, where the data viewing request is closed-loop processed. Updating the file triggers the synchronization of the user file metadata to the central node.

[0069] In one embodiment, the updated file includes newly added file data and modified file data;

[0070] When new file data is added, the client uploads the file to the file resource storage pool 110 at the nearest edge point, and the cloud NAS service synchronizes the file metadata changes to the central node;

[0071] When file data is modified, the cloud NAS service directly synchronizes the file metadata changes to the central node.

[0072] like Figure 3 As shown, after the user device logs in to the network, it first initiates a login registration request to the user scheduling service module of the central service platform 200, and obtains the login token and the edge cloud NAS service 130 address, and then returns the address of the nearest edge cloud device. The device initiates a connection to the edge cloud NAS service 130, and the edge cloud NAS service 130 obtains the user's login token, and synchronizes the user file metadata to the edge cloud NAS service 130 on the file service of the central service platform 200, and then returns it to the user device for initialization.

[0073] When a user device operates a file within the cloud NAS service, the interaction primarily occurs with the edge cloud node. Query requests are closed-loop processed on edge node 120, while update requests trigger the synchronization of user file metadata with the central node. Metadata is lightweight, consumes little bandwidth, and requests are fast. Data is synchronized to the file resource storage pool 110 on edge node 120. Requests to the nearest resource pool have lower latency and more stable data transmission.

[0074] The cloud NAS service does not store user data and file data separately. When a failure occurs, the backup node can be directly switched without affecting user services, and smooth switching can be achieved.

[0075] A specific example of cloud NAS metadata synchronization is Figure 4 As shown in the figure, assume that the user's cloud NAS service system includes a document folder and a compressed file .zip (zipped). The user file tree metadata information structure of the initialized file system is as follows, where fileTree is a description of the subdirectory tree of the folder, and path is a description of the location of the user folder directory in the file system:

[0076]

[0077]

[0078] In one embodiment, when the metadata information in the cloud changes, only the changed file tree directory information is synchronized. For example, the description of a newly added picture folder and picture.jpg is as follows:

[0079] 1. The metadata information of the newly added image folder synchronized to the cloud is:

[0080]

[0081] 2. The metadata information of the newly added .jpg image synchronized to the cloud is:

[0082]

[0083] In one embodiment, when the compressed file .zip is moved to the document folder, the metadata information synchronized to the cloud is:

[0084]

[0085]

[0086] The metadata information structure of the end user is as follows:

[0087]

[0088]

[0089] The technical solution provided by the embodiments of the present application has the following advantages:

[0090] 1. By leveraging edge cloud node resources, cloud NAS service data centers are migrated to the user side, enabling lower data interaction latency and reducing network traffic. This architecture allows data to be closer to end users, reducing round-trip data time and improving application responsiveness. It also helps reduce network load on cloud data centers, as some data processing and storage can be performed on edge cloud nodes.

[0091] 2. Unitized scheduling services, centralized file metadata management, and real-time distribution enable user request scheduling and traffic allocation, meeting high-concurrency and high-availability system requirements. This architecture emphasizes the modularization and centralized management of scheduling services, enabling the system to monitor user requests in real time and effectively allocate traffic, ensuring high availability under high concurrency. This also provides more efficient file metadata management, enabling the system to quickly retrieve and process user data requests, thus meeting the needs of highly dynamic and diverse applications.

[0092] Those skilled in the art will appreciate that information, signals, and data may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips cited throughout the foregoing description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0093] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Technicians can implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of this application.

[0094] The various illustrative logic modules and circuits described in conjunction with the embodiments disclosed herein may be implemented or executed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0095] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read and write information from / to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and storage medium may reside in a user terminal as discrete components.

[0096] In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. A storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0097] The above embodiments are provided for persons familiar with the art to implement or use the present application. Personnel familiar with the art may make various modifications or changes to the above embodiments without departing from the application concept of the present application. Therefore, the scope of protection of the present application is not limited to the above embodiments, but should be the maximum scope of the innovative features mentioned in the claims.

Claims

1. A unitized scheduling cloud NAS system, characterized in that: The unitized scheduling cloud NAS system includes: An edge area module, wherein the edge area module is configured as a unitized architecture and is provided with a file resource storage pool; A central node, the central node being signal-connected to the edge area module and the central service platform; A central service platform, which includes a variety of services and functions for supporting and managing various business or technical needs; Central service gateway, the central service gateway is signal-connected to the central service platform, and the central service gateway is used for unified entry, request distribution and flow control.

2. The unitized scheduling cloud NAS system according to claim 1, characterized in that: The central service platform includes a user service module, a user scheduling service module, a file service module, a capability exposure service module and other service modules; The user service module is used to store user data and provide information management services and service subscription; The user scheduling service module is used to provide user authentication, user scheduling and edge node management; The file service module is used to provide query, management, and synchronization functions with edge cloud NAS devices.

3. The unitized scheduling cloud NAS system according to claim 1, characterized in that: The central node stores metadata, and when a user accesses, the metadata is synchronized to the accessed edge node, and the file resource storage pool stores data.

4. The unitized scheduling cloud NAS system according to claim 1, characterized in that: The edge area module includes an edge node and an edge cloud NAS service, and the edge area module is connected to the edge device in the service area.

5. The unitized scheduling cloud NAS system according to claim 4, characterized in that: The edge node is connected to the edge cloud NAS service signal; The edge node includes a plurality of single edge nodes, and the edge cloud NAS service includes a plurality of single edge cloud NAS services; The single edge node is configured corresponding to the single edge cloud NAS service.

6. The unitized scheduling cloud NAS system according to claim 5, characterized in that: The single edge cloud NAS service is configured as an independent application, the edge cloud NAS service is configured with a Docker container image, the single edge cloud NAS service is placed in a Docker container image that can be transplanted at any time, and the single edge cloud NAS service image serves as a deployment unit.

7. The unitized scheduling cloud NAS system according to claim 6, characterized in that: The edge node is provided with a health management module, a load balancing module and a computer room monitoring and alarm module. When a single edge cloud NAS service image in the computer room fails, the health management module will automatically shut down the service and initialize a new image service, and the load balancing module will adjust the request.

8. The unitized scheduling cloud NAS system according to claim 7, characterized in that: When the entire computer room fails, the computer room monitoring alarm module will issue a reminder, and the staff will resolve the domain name IP of the center of the faulty area to the backup node or other node IP. When the backup node service receives the request, it will trigger the user's cloud file metadata initialization to the node process, and provide services to users normally, and users will not feel the switch.

9. The unitized scheduling cloud NAS system according to claim 5, characterized in that: The central node uses the scheduling strategy of the user scheduling service module to concentrate the requests of user devices to the unitized cloud NAS edge interface, ensuring that user data is stored and accessed nearby, making the user's data request interaction delay lower and the data transmission more stable.

10. A unitized scheduling cloud NAS method, used in the unitized scheduling cloud NAS system according to any one of claims 1 to 9, comprising: Step S101, the user uses the client on the PC to log in to the user's cloud NAS service account and access the central node; Step S102, after accessing the central node, generate and distribute an access token and the nearest edge cloud NAS service address; Step S103, the client connects to the cloud NAS address, triggering the file system initialization. At this time, the file metadata of the user file system is loaded on the edge cloud NAS service, and the entire file tree structure is at the edge node; Step S104: User operation: the user chooses to view data and update files on the client.

11. The unitized scheduling cloud NAS method according to claim 10, characterized in that: When user devices operate unitized scheduling of files in the cloud NAS system, the interaction must first go to the edge node, where data viewing requests are closed-loop processed, and file update requests trigger the synchronization of user file metadata to the central node.

12. The unitized scheduling cloud NAS method according to claim 10, characterized in that: The update file includes newly added file data and modified file data; When new file data is added, the client uploads the file to the file resource storage pool of the nearest edge node, and the cloud NAS service synchronizes the file metadata changes to the central node; When file data is modified, the cloud NAS service directly synchronizes the file metadata to the central node.

Images