Mounting method, device and equipment based on network disk service and storage medium

Abstract

The invention provides a mounting method, device and equipment based on a network disk service and a storage medium, and the mounting method based on the network disk service comprises the steps: obtaining a mounting request for mounting a target network disk service initiated by an application program of a terminal, analyzing the mounting request through an abstract interface layer of a uniform interface, determining a target plug-in, and transmitting the target plug-in to the terminal; no matter which difference exists in the API of the bottom layer network disk service, the application program can be requested through the abstract interface layer of the uniform interface, the operation is very convenient and rapid, and seamless request is realized; the method comprises the following steps: connecting an abstract interface layer through an adapter mode of a target plug-in to obtain a mounting request, interacting with an API (Application Program Interface) of a target network disk service according to the mounting request, determining target data, adopting a plug-in architecture design, developing the target plug-in corresponding to the target network disk service, and synchronously mounting the target data in a terminal and an edge node. And the dependence on the remote server can be reduced by utilizing the edge node.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of computers, and in particular to a mounting method and device based on a network disk service, an apparatus, and a storage medium. BACKGROUND

[0002] With the development of cloud computing and edge computing technologies, the amount of data has greatly increased, and the challenge of data storage has become increasingly greater. Among them, the network disk service, as an important form of data storage, is widely used in personal and enterprise users. However, the traditional network disk service usually relies on a centralized cloud storage platform, and users connect to a remote server through the Internet to upload, download, and manage files. Different network disk service APIs differ, and users need to find the corresponding API to upload, download, and manage files, which is very cumbersome. SUMMARY

[0003] The embodiments of the present application provide a mounting method and device based on a network disk service, an apparatus, and a storage medium to solve at least one problem in the related art. The technical solutions are as follows:

[0004] In a first aspect, the embodiments of the present application provide a mounting method based on a network disk service, comprising:

[0005] Obtaining a mounting request for mounting a target network disk service initiated by an application program of a terminal;

[0006] Analyzing the mounting request through an abstract interface layer of a unified interface, and determining a target plug-in;

[0007] Connecting the abstract interface layer through an adapter mode of the target plug-in to obtain the mounting request, and interacting with an API of the target network disk service according to the mounting request to determine target data;

[0008] Synchronously mounting the target data in the terminal and an edge node.

[0009] In an embodiment, before obtaining the mounting request for mounting the target network disk service initiated by the application program of the terminal, the method comprises:

[0010] Determining at least one of a gRPC service interface and a RESTful API interface, and compiling a service instance for interaction between a server and the terminal; the gRPC service interface and the RESTful API are used for synchronous mounting, and the synchronous mounting includes at least one of uploading, downloading, and authentication information interaction;

[0011] When the service is started, establishing a connection with the service instance through the terminal.

[0012] In an embodiment, the establishing a connection with the service instance by the terminal when the service is started comprises:

[0013] When the service is started and there is a registration center, registering the service instance of the service in the registration center and establishing a connection with the service instance by the terminal, wherein the synchronous mounting utilizes the gRPC service interface;

[0014] When the service is started and there is no registration center, establishing a connection with the service instance by the terminal, wherein the synchronous mounting is implemented based on the WebDAV standard by the RESTful API interface.

[0015] In an embodiment, the connecting the abstract interface layer by the adapter mode of the target plug-in to obtain the mounting request and interacting with the API of the target network disk service according to the mounting request to determine the target data comprises:

[0016] Bridging the API of the target network disk service and the abstract interface layer by the adapter mode of the target plug-in and obtaining the mounting request;

[0017] According to the mounting request, performing read or write operation on the API of the target network disk service to determine the read target data or the written target data.

[0018] In an embodiment, the synchronously mounting the target data in the terminal and the edge node comprises:

[0019] In the case of determining the target data, authenticating the terminal to determine the authority of the target data;

[0020] When having the authority, encrypting the target data by using SSL / TLS encryption technology and synchronously mounting the encrypted target data in the terminal and the edge node.

[0021] In an embodiment, the method further comprises:

[0022] Obtaining load information of each edge node, analyzing and predicting according to the load information to obtain current load analysis result and future load trend;

[0023] When the current load analysis result or the future load trend represents overload, adding a new edge node and performing resource configuration on the new edge node;

[0024] Quickly deploying the new edge node by using automatic script or containerization technology and evenly distributing traffic to all edge nodes by using load balancing strategy.

[0025] In an implementation, the method further comprises:

[0026] In a case that the target data is synchronously mounted in the terminal and the edge node, the target data is cached by the edge node;

[0027] In a preset time interval, access frequency of data stored by the edge node is detected, and data with the access frequency greater than a frequency threshold is saved locally;

[0028] When the terminal initiates a request for data stored by the edge node, geographical position information, network status and load condition of the terminal are acquired to determine an optimal edge node from a plurality of edge nodes, and the request is responded by the optimal edge node.

[0029] In a second aspect, an embodiment of the present application provides a mounting device based on a network disk service, comprising:

[0030] An acquisition module is configured to acquire a mounting request for mounting a target network disk service initiated by an application program of a terminal;

[0031] An analysis module is configured to analyze the mounting request by an abstract interface layer of a uniform interface to determine a target plug-in;

[0032] A determination module is configured to connect the abstract interface layer by an adapter mode of the target plug-in to acquire the mounting request, and interact with an API of the target network disk service according to the mounting request to determine target data;

[0033] A mounting module is configured to synchronously mount the target data in the terminal and the edge node.

[0034] In an implementation, the determination module is further configured to:

[0035] Determine at least one of a gRPC service interface and a RESTful API interface, and compile a service instance for interaction between a server and the terminal; the gRPC service interface and the RESTful API are used for synchronous mounting, and the synchronous mounting comprises at least one of uploading, downloading and authentication information interaction;

[0036] When the service is started, the terminal establishes a connection with the service instance.

[0037] In an implementation, the determination module is further configured to:

[0038] Acquire load information of each edge node, analyze and predict according to the load information to obtain a current load analysis result and a future load trend;

[0039] when the current load analysis result or the future load trend represents overload, adding a new edge node and performing resource configuration on the new edge node;

[0040] The new edge node is quickly deployed through an automatic script or a containerization technology, and traffic is evenly distributed to all edge nodes through a load balancing strategy.

[0041] In an implementation, the determining module is further configured to:

[0042] The method further includes:

[0043] In a case where the target data is synchronously mounted in the terminal and the edge node, the target data is cached by the edge node;

[0044] At a preset time interval, the access frequency of the data stored by the edge node is detected, and the stored data with an access frequency greater than a frequency threshold is saved locally;

[0045] When the terminal initiates a request for the data stored by the edge node, the geographic location information, network status and load condition of the terminal are acquired, an optimal edge node is determined from a plurality of edge nodes, and the request is responded to through the optimal edge node.

[0046] In a third aspect, an electronic device is provided, including a processor and a memory, the memory storing instructions, the instructions being loaded and executed by the processor to implement the method in any of the implementations of the above aspects.

[0047] In a fourth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a computer program, the computer program being executed to implement the method in any of the implementations of the above aspects.

[0048] The above technical solutions have at least the following beneficial effects:

[0049] By acquiring a mounting request for mounting a target network disk service initiated by an application program of the terminal, the mounting request is parsed through an abstract interface layer of the unified interface, and a target plug-in is determined. Regardless of the API difference of the underlying network disk service, the application program can request through the abstract interface layer of the unified interface, which is very convenient and fast, and seamless request is achieved. The adapter mode of the target plug-in is connected to the abstract interface layer to acquire the mounting request, and the API of the target network disk service is interacted according to the mounting request to determine the target data. The plug-in architecture design is adopted, the target plug-in corresponding to the target network disk service is developed, the target data is synchronously mounted in the terminal and the edge node, and the edge node is used to reduce the dependence on the remote server.

[0050] The foregoing summary is provided only for purposes of summary and is not intended to limit the application in any regard. Additional aspects, embodiments and features of the application are more fully described below in the DETAILED DESCRIPTION section. BRIEF DESCRIPTION OF DRAWINGS

[0051] In the drawings, like numerals refer to like elements throughout the various drawings. The drawings are not necessarily to scale, the emphasis instead being placed upon illustrating principles of the application. It should be understood that the drawings are merely depictions of some embodiments of the application and that each of the drawings is a simplification.

[0052] Figure 1 A step flow diagram of a mounting method based on a network disk service according to an embodiment of the application;

[0053] Figure 2 A structural block diagram of a mounting device based on a network disk service according to an embodiment of the application;

[0054] Figure 3 A structural block diagram of an electronic device according to an embodiment of the application. DETAILED DESCRIPTION

[0055] In the following, only some exemplary embodiments are described in brief. As will be realized by those skilled in the art, the described embodiments can be modified in various different ways without departing from the spirit or scope of the application. The drawings and description are therefore to be regarded as illustrative in nature rather than restrictive.

[0056] The converged edge network refers to providing cloud, network convergence services at the edge node closest to the user, aiming to play the advantages of new metropolitan area networks and edge clouds, providing a local area network experience for broadband users, and driving business success. The new metropolitan area network has the advantages of large bandwidth and low latency (1-5 ms), and also has edge machine rooms covering the whole province, including shallow edge and deep edge nodes, which can provide an extension service and an intranet security experience for users at the closest location to the user, thereby providing an application experience that is overall superior to OTT.

[0057] Network disk mounting refers to supporting data synchronization with various types of network disks through a converged edge cloud, including uploading and downloading, maintaining the consistency of NAS files and network disk files, and synchronously managing various types of network disks, such as Baidu Netdisk, Tianyi Cloud Disk, Ali Cloud Disk, and Tencent Cloud Disk. Through a converged edge cloud, data synchronization with various types of network disks is supported, including uploading and downloading, maintaining the consistency of NAS files and network disk files. This real-time synchronization feature can make it more convenient for users to manage and share files.

[0058] Referring toFigure 1 The flowchart illustrates a method for mounting a cloud storage service based on an embodiment of this application. This method may include at least steps S100-S400:

[0059] S100: Obtain the mount request for the target cloud storage service initiated by the application in the terminal.

[0060] S200: The mounting request is parsed through the abstract interface layer of the unified interface to determine the target plugin.

[0061] S300 connects to the abstract interface layer through the adapter pattern of the target plugin to obtain the mount request, and interacts with the API of the target cloud storage service according to the mount request to determine the target data.

[0062] S400 synchronously mounts the target data on the terminal and edge nodes.

[0063] The technical solution of this application embodiment obtains the mounting request for the target cloud storage service initiated by the terminal application, parses the mounting request through the abstract interface layer of the unified interface, and determines the target plugin. Regardless of the differences in the API of the underlying cloud storage service, the application can make requests through the abstract interface layer of the unified interface, which is very convenient and fast, and achieves seamless requests. The target plugin connects to the abstract interface layer through the adapter pattern to obtain the mounting request, and interacts with the API of the target cloud storage service according to the mounting request to determine the target data. It adopts a plug-in architecture design, develops the target plugin corresponding to the target cloud storage service, and synchronously mounts the target data on the terminal and edge nodes. Utilizing edge nodes helps to reduce the dependence on remote servers.

[0064] In one implementation, steps S001-S002 are included before step S100:

[0065] S001. Determine at least one of the gRPC service interface and the RESTful API interface, and compile and generate the service for interaction between the server and the terminal.

[0066] Optionally, the gRPC service interface and the RESTful API interface are determined, the gRPC service interface and the RESTful API are used for synchronous mounting, the synchronous mounting includes uploading, downloading and authentication information interaction, in other embodiments, one of the uploading, the downloading and the authentication information interaction can be included, the interface can include one of the gRPC service interface and the RESTful API interface. In the embodiment of the application, the gRPC service interface and the RESTful API interface are determined to ensure efficient transmission in different cases, specifically, the gRPC service interface is defined using the Protocol Buffers, so that the related method of the synchronous mounting including the file uploading, the downloading, the authentication information interaction and the like is included, and the code required by the client and the server is compiled by the Protocol Buffers compiler, so that the service for the interaction between the server and the terminal is compiled.

[0067] S002, when the service is started, the connection with the service instance is established through the terminal.

[0068] Optionally, steps S0021-S0022 are included:

[0069] S0021, when the service is started and the registration center exists, the service instance of the service is registered in the registration center, and the connection with the service instance is established through the terminal,

[0070] Optionally, when the service is started and the registration center (such as Consul, Zookeeper, Eureka, etc., which realizes the dynamic registration and management of the network disk mounting and the distributed edge node) exists, the service instance of the service is registered in the registration center, the service instance can include the instance itself and the instance information thereof, such as the service address and the port, etc., which is used for the user to discover the service instance that can be used through the registration center in the terminal, and then the connection with the service instance is established through the terminal, for example, the connection is established through the gRPC service interface, which is used for the subsequent synchronous mounting.

[0071] S0022, when the service is started and the registration center does not exist, the connection with the service instance is established through the terminal.

[0072] Optionally, when the service starts and there is no registration center, at this time the terminal can call the RESTful API through an HTTP request, so that the terminal establishes a connection with the service instance, and the RESTful API is used for subsequent synchronization mounting. It should be noted that the authentication mechanism of Token is introduced in the embodiments of the present application to ensure the security of the RESTful API, and to ensure that the RESTful API interface can still work normally in the environment without the registration center, and to provide a convenient access mode. The user can choose to use the gRPC service interface or the HTTP RESTful API interface according to the application scene and environmental conditions, and correspondingly deploy the service and implement the corresponding calling logic on the client, efficiently exchange data through the selected service type, and continuously monitor the service performance, and optimize and adjust according to the feedback result. Regardless of whether the gRPC service interface or the RESTful API interface is used, load balancing, security mechanisms (such as TLS encryption, Token authentication, etc.), performance monitoring (such as through Prometheus, Grafana, etc.), and fault recovery mechanisms are implemented, ensuring efficient data interaction.

[0073] In addition, the synchronization mounting is implemented based on the WebDAV standard using the RESTful API interface. WebDAV supports integration and is a standard based on the HTTP protocol, which is used to realize remote access and editing of files. Therefore, in order to improve the ease of use of the network disk service, a WebDAV server module is integrated into its core components, so that users can browse, upload, download or edit the data stored in the cloud network disk service through the third-party software supporting WebDAV or the built-in function of the operating system, without the need to install any additional client software.

[0074] Furthermore, in order to improve the performance, security and compatibility of the network disk service, the WebDAV server module is improved in many aspects to improve the mounting performance. For example, in terms of performance optimization, efficient file reading and writing mechanisms such as asynchronous I / O and memory-mapped files are adopted, and a file caching mechanism is also implemented to reduce the repeated uploading and downloading process of files; in terms of security, HTTPS support is added to ensure the security of data transmission, and modern authentication mechanisms such as OAuth2 or JWT are introduced to replace basic authentication; in addition, in terms of HTTP method support, support for PROPFIND and PROPPATCH methods is added to get and update resource properties, and support for MKCOL method to create collections (directories) and COPY and MOVE methods to copy and move files or directories is also added. Finally, in terms of compatibility, support for differences in file path processing of different operating systems is enhanced, and interoperability with other WebDAV servers is improved to ensure good compatibility.

[0075] In an embodiment, the gRPC service interface and the RESTful API interface can also utilize the FTP file transfer protocol, through the integration of a configurable FTP server module, allowing users to connect to the target network disk service through applications such as FTP clients and perform file management operations. Users can connect to the FTP server address through command line tools or other FTP client software, easily perform file upload and download operations, etc. It should be noted that the FTP server module supports setting access permissions and restrictions, enhancing security to ensure that only authorized users can access specific files and folders; in terms of performance optimization, efficient file reading and writing mechanisms such as asynchronous I / O and memory-mapped files are used, and a file caching mechanism is also implemented to reduce repeated file upload and download processes; in terms of security, FTPS support is added to ensure the security of data transmission, and fine-grained access control and permission management are introduced to ensure that only authorized users can access specific files and folders; in terms of functional expansion, support for MLSD and MLST commands is added to obtain detailed information about files, and support for UTF8 extensions is implemented to ensure correct handling of file names and directory names. In terms of compatibility, support for differences in file path handling between different operating systems is enhanced, and interoperability with other FTP servers is improved to ensure good compatibility.

[0076] In an embodiment, the application can design corresponding drivers (or applications) for each type of network disk service, which can handle API interactions with each service provider and support file upload, download, deletion, etc. Each driver follows a standard interface definition, facilitating unified management and maintenance, ensuring cross-platform compatibility and flexibility. In this way, users can seamlessly switch between different network disk services and enjoy consistent operation experience. Moreover, the driver supports accessing files stored in the cloud through the WebDAV protocol, allowing users to access files in the network disk through WebDAV-enabled applications, and also allows it to run as an FTP server, allowing users to connect and operate files through FTP clients; enhances security, including authentication mechanisms, data encryption, etc., to ensure user data security; to improve access speed and user experience. In the application, the server in the cloud obtains a mounting request for mounting the target network disk service (target service instance) initiated by the application program of the terminal, such as a mounting request initiated based on the gRPC service interface and the RESTful API interface.

[0077] In an embodiment, in step S200, the mounting request is parsed by an abstract interface layer of the unified interface to determine the target plug-in. It should be noted that the abstract interface layer defines a set of standardized interface specifications in advance, and all interactions of the network disk service are performed through this layer, which shields the specific implementation details of different network disk service APIs, so that the application program can use a unified interface to access various network disk services, and each network disk service has a corresponding plug-in module, which is responsible for processing API calls and data format conversion of a specific network disk service. Therefore, by parsing the mounting request of the target network disk service, the target plug-in corresponding to the target network disk service can be determined. Through the plug-in design, the system can easily add support for new network disk services without changing the core code, facilitating management and expansion.

[0078] In an embodiment, a configuration management system is deployed, so that the user can specify the type of network disk service to be used and its authentication information through the configuration management interface in the application program, simplifying the configuration process of the user and improving the flexibility of the system. At the same time, the configuration has a dynamic loading mechanism: supporting on-demand loading of the target plug-in of the target network disk service at runtime, avoiding unnecessary resource consumption, and improving the response speed of the system, i.e., the server can dynamically adjust according to the actual needs of the user without recompiling the entire system to add new service support.

[0079] In an embodiment, step S300 includes steps S310-S320:

[0080] S310, bridging the API of the target network disk service and the abstract interface layer through the adapter pattern of the target plug-in, and obtaining the mounting request.

[0081] Optionally, the adapter pattern is used to bridge the differences between different network disk service APIs and the abstract interface layer, so that the plug-in can be seamlessly connected with the abstract interface layer, ensuring the consistency and integrity of the data. Specifically, the API of the target network disk service and the abstract interface layer are bridged through the adapter pattern of the target plug-in, and then the adapter pattern of the target plug-in obtains the mounting request.

[0082] S320, performing read or write operations with the API of the target network disk service according to the mounting request to determine the target data read or the target data written.

[0083] Optionally, the adapter mode of the target plug-in determines, based on a mounting request such as reading or writing, a read or write operation with the API of the target network disk service, so as to determine the target data to be read or written.

[0084] In an embodiment, the step S400 includes steps S410-S420:

[0085] S410, in the case of determining the target data, authenticating the terminal, determining the permission to the target data.

[0086] Optionally, in the embodiments of the present application, a security enhancement mechanism is provided to ensure the security of user data. In the case of determining the target data, the terminal is authenticated, for example, based on a username and password, a modern authentication protocol such as OAuth2 is supported, so as to determine whether the authentication is passed, and whether the permission of the user authenticated to the target data can access the target data. In some embodiments, the authentication can also introduce multi-factor authentication, in addition to the username and password, an additional security layer such as a mobile phone verification code, a hardware token, etc. can be added; end-to-end encryption provides end-to-end encryption for sensitive data, ensuring that even if the data is intercepted during transmission, it cannot be decrypted; audit log recording records the access and operation behavior of the user, helping to track potential security threats; anomaly detection implements anomaly detection mechanisms such as login behavior analysis, IP address monitoring, etc., to discover and respond to potential security events in a timely manner. These additional security measures, combined with existing security mechanisms, form a more comprehensive and powerful security system, providing higher level of data security protection for users.

[0087] S420, when having the permission, encrypting the target data by using SSL / TLS encryption technology, and synchronously mounting the encrypted target data in the terminal and the edge node.

[0088] Optionally, when having the permission, the target data is encrypted by using SSL / TLS encryption technology to ensure the security of data transmission and prevent the data from being intercepted or tampered during transmission, and then the encrypted target data is synchronously mounted in the terminal and the edge node.

[0089] It should be noted that a fine-grained access control list (ACL) can be set in advance, and an administrator sets the access permission of different users to data. When a user attempts to access a file in the cloud network disk, the system first authenticates and determines the access permission. In addition, for sensitive files, the system also automatically enables an encrypted channel during data transmission to ensure the secure transmission of data.

[0090] In an implementation, the mounting method based on the network disk service can further include steps S510-S530.

[0091] S510, load information of each edge node is acquired, and current load analysis results and future load trends are obtained by analyzing and predicting the load information.

[0092] Optionally, the server of the cloud acquires load information of each edge node, analyzes and predicts the load information through a load analysis model of the server, and obtains current load analysis results and predicted future load trends.

[0093] S520, when the current load analysis results or the future load trends represent overload, a new edge node is added, and resource configuration is performed on the new edge node.

[0094] Optionally, when the current load analysis results or the future load trends represent overload, that is, exceed the load threshold, a new edge node is dynamically added, and resource configuration, such as configuration of computing resources, storage resources and network resources, is performed on the new edge node, to facilitate normal operation of the new edge node.

[0095] S530, the new edge node is quickly deployed through an automated script or a containerization technology, and traffic is evenly distributed to all edge nodes through a load balancing strategy.

[0096] Then, the new edge node is quickly deployed through an automated script or a containerization technology, and traffic is evenly distributed to all edge nodes through a load balancing strategy, to ensure overall load balancing; at the same time, the running state of the system is continuously monitored, and the number of edge nodes is dynamically adjusted according to actual load changes, for example, when the number of edge nodes is reduced and the edge nodes are removed when the load is below a specified percentage of the load threshold. For example, after it is determined which edge nodes can be safely removed without affecting the quality of service, the resources of these edge nodes are recovered, and the load on the original edge nodes is redistributed to other edge nodes, to ensure load balancing. Similarly, the edge nodes are safely closed and removed through an automated script or a containerization technology, and the system load is continuously monitored after the edge nodes are removed, and resource optimization is performed as needed.

[0097] To ensure the smooth progress of this process, the embodiments of the present application use automation tools and technologies (such as Kubernetes, Ansible or Chef) to manage the deployment and maintenance of edge nodes; adopt load monitoring tools (such as Prometheus, Zabbix) to collect system load data for making reasonable decisions; use the elastic scaling function of cloud service providers (such as AWS Auto Scaling, Azure Virtual Machine Scale Sets) to realize the automatic scaling of edge nodes; use configuration management tools (such as Puppet, Ansible) to ensure the consistency and maintainability of edge nodes; design a failure recovery mechanism to ensure that services can be quickly restored in the event of edge node failure. Through the above process, edge nodes can be dynamically added or removed according to actual needs, realizing on-demand allocation and optimization of resources, so as to maintain the lightweight of the system in different orders of magnitude of file access scenarios, and reduce hardware and operation and maintenance costs.

[0098] In an embodiment, the mounting method based on the network disk service can further include steps S610-S630.

[0099] S610, in the case of synchronously mounting the target data in the terminal and the edge node, the edge node caches the target data.

[0100] Optionally, in the case of synchronously mounting the target data in the terminal and the edge node, the edge node caches the target data, and since there can be one or more caches in the historical time, the edge node can cache multiple target data.

[0101] S620, at a preset time interval, detecting the access frequency of the stored data of the edge node, and saving the stored data with an access frequency greater than a frequency threshold in the local.

[0102] Optionally, the edge node can periodically cache one or more target data at a preset time interval, which is recorded as stored data. The server can detect the access frequency or life cycle management of the stored data of the edge node, cache the frequently accessed data such as files, that is, the stored data with an access frequency greater than a frequency threshold, to the local, so as to reduce the time of obtaining data from the remote server and save the cache of the edge node.

[0103] S630, when the terminal initiates a request for the stored data of the edge node, obtaining the geographic location information, network condition and load condition of the terminal, to determine the optimal edge node from a plurality of edge nodes, and responding to the request through the optimal edge node.

[0104] It should be noted that the data can be shared among multiple edge nodes; when the terminal initiates a request for the data stored in the edge node, the server obtains the geographic location information, network status and load condition of the terminal, uses a load analysis model to comprehensively score each node according to its location, in combination with the geographic location information, network status and load condition of the terminal, and selects the edge node with the highest score as the optimal edge node, and then responds to the request through the optimal edge node, so as to ensure a shorter data transmission path and lower delay, and realize intelligent routing.

[0105] In some embodiments, the data that the user is likely to access can also be predicted through historical access pattern analysis, user behavior learning and real-time trend prediction, and the data can be loaded into the optimal edge node in advance to further reduce data access delay. These optimization measures collectively ensure the efficiency and fast response of data transmission, and significantly improve the user experience.

[0106] In terms of security, the embodiments of the present application enhance the security protection measures of the edge nodes, effectively resist potential attacks, and protect the security of the data. By optimizing the cross-domain access mechanism, an abstract interface layer and a plug-in framework based on a unified interface are constructed to solve the network isolation problem between different edge nodes, realize efficient data synchronization and cross-domain access, and ensure that data can be quickly and accurately synchronized between different edge nodes. Even if the data is stored in different locations in the network, the consistency and integrity of the data can be guaranteed. For the problem of limited resources of the edge nodes, intelligent resource allocation strategies are used to reasonably allocate resources and maximize the performance of the overall system. By optimizing the user experience design, file synchronization delay and file loss are significantly reduced, and the user experience in the actual operation process is improved. Ultimately, the data is stored nearby and accessed quickly, effectively solving the problems of data consistency, security, cross-domain access, resource utilization, and user experience.

[0107] Based on the method of the present application, the data synchronization speed is tested: in one test, the data synchronization speed of the present application technology and the traditional centralized network disk service in different geographic locations is compared. The results show that when using the present application technology, the data synchronization speed is increased by more than 30% on average, especially in high delay network environment, up to 50%.

[0108] Cross-domain access efficiency: the test of cross-domain access shows that the present application technology can effectively shorten the network delay between different regions. Compared with the traditional scheme, the delay of cross-domain data access is reduced by about 20%.

[0109] Resource utilization: Through the monitoring of resource consumption, the present technology also performs well in resource utilization. Due to the adoption of intelligent resource allocation strategies, the CPU and memory utilization of edge nodes are increased by about 15% and 20%, respectively, which indicates that the system can make more efficient use of existing hardware resources.

[0110] Data consistency and integrity: In the case of a large number of concurrent operations, the data consistency test results of the present technology show that the data loss rate is almost zero, while the traditional scheme has obvious data loss phenomenon. This proves the advancement and effectiveness of the data synchronization algorithm of the present technology.

[0111] Security test: The security test shows that the present technology has stronger resistance to common network attacks. Through simulation of multiple attack scenarios, it is found that the system's security protection measures effectively prevent more than 95% of attack attempts, while the traditional centralized scheme performs poorly in similar tests.

[0112] Performance advantage summary, fast data access: Through edge computing technology, data storage is closer to user terminals, reducing the delay caused by long-distance transmission, thereby improving data access speed, which is particularly important for users who frequently access large data sets.

[0113] Reference Figure 2 , shows the structure block diagram of the mounting device based on the network disk service of an embodiment of the present application, which can include:

[0114] The acquisition module is configured to acquire a mounting request for mounting a target network disk service initiated by an application program of a terminal.

[0115] The analysis module is configured to analyze the mounting request through an abstract interface layer of a unified interface to determine a target plug-in.

[0116] The determination module is configured to connect the abstract interface layer through an adapter mode of the target plug-in to acquire the mounting request, and interact with an API of the target network disk service according to the mounting request to determine target data.

[0117] The mounting module is configured to synchronously mount the target data in the terminal and the edge node.

[0118] In an embodiment, the determination module is further configured to:

[0119] determine at least one of a gRPC service interface and a RESTful API interface, and compile a service for interaction between the server and the terminal; the gRPC service interface and the RESTful API are used for synchronous mounting, and the synchronous mounting includes at least one of uploading, downloading, and authentication information interaction;

[0120] When the service is started, a connection with the service instance is established through the terminal.

[0121] In an implementation, the determining module is further configured to:

[0122] obtain load information of each edge node, analyze and predict according to the load information, obtain a current load analysis result and a future load trend;

[0123] when the current load analysis result or the future load trend represents overload, add a new edge node and perform resource configuration on the new edge node;

[0124] quickly deploy the new edge node through an automatic script or a containerization technology, and evenly distribute traffic to all edge nodes through a load balancing strategy.

[0125] In an implementation, the determining module is further configured to:

[0126] The method further includes:

[0127] in a case where the target data is synchronously mounted in the terminal and the edge node, cache the target data through the edge node;

[0128] at a preset time interval, detect an access frequency of the data stored in the edge node, and save, in the local, the stored data whose access frequency is greater than a frequency threshold;

[0129] when the terminal initiates a request for the data stored in the edge node, obtain geographic location information, network status and load condition of the terminal, determine an optimal edge node from the edge nodes, and respond to the request through the optimal edge node.

[0130] The functions of each module in each device in the embodiments of the application can be referred to the corresponding description in the above method, and will not be described here.

[0131] With reference to Figure 3 , a structural block diagram of an electronic device according to an embodiment of the application is shown, which includes a memory 310 and a processor 320, the memory 310 stores instructions executable on the processor 320, and the processor 320 loads and executes the instructions to implement the mounting method based on the network disk service in the above embodiments. The number of the memory 310 and the processor 320 can be one or more.

[0132] In an implementation, the electronic device further includes a communication interface 330 for communicating with external devices to transmit and receive data. If the memory 310, the processor 320 and the communication interface 330 are implemented independently, the memory 310, the processor 320 and the communication interface 330 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, Figure 3 Only one thick line is used to represent the bus in the figure, but it does not mean that there is only one bus or only one type of bus.

[0133] Optionally, in a specific implementation, if the memory 310, the processor 320 and the communication interface 330 are integrated on a chip, the memory 310, the processor 320 and the communication interface 330 can communicate with each other through an internal interface.

[0134] The embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the mounting method based on the network disk service provided in the above embodiment.

[0135] The embodiment of the present application further provides a chip, which includes a processor, and the processor is used to call and run instructions stored in a memory, so that a communication device installed with the chip executes the method provided in the embodiment of the present application.

[0136] The embodiment of the present application further provides a chip, which includes an input interface, an output interface, a processor and a memory, the input interface, the output interface, the processor and the memory are connected through an internal connection path, and the processor is used to execute code in the memory, and when the code is executed, the processor is used to execute the method provided in the embodiment of the present application.

[0137] It is to be understood that the above-described processor can be a central processing unit (CPU), but can also be other general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general purpose processor can be a microprocessor or any conventional processor, etc. It is to be noted that the processor can be an advanced RISC machine (ARM) architecture processor.

[0138] Further, the memory described above can include a read-only memory and a random access memory, and can also include a non-volatile random access memory. The memory can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. The non-volatile memory can include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can include a random access memory (RAM) used as an external cache. By way of example but not limitation, many forms of RAM are available. For example, static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM) can be used.

[0139] In the above-described embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded on a computer, all or part of the processes or functions according to the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium.

[0140] In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" and the like means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. Also, the specific features, structures, materials, or characteristics described can be combined in any appropriate manner in any one or more embodiments or examples. In addition, a person skilled in the art can combine and combine the different embodiments or examples described in the present specification and the features of the different embodiments or examples without contradiction.

[0141] In addition, the terms "first", "second", etc. are used only for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined with "first", "second" can explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "a plurality of" is two or more, unless otherwise explicitly specified.

[0142] Any process or method descriptions in flow charts or described elsewhere herein can be understood as representing code modules, segments, or portions of code that include one or more executable instructions for implementing specific logic functions or other processes. Also, the preferred embodiments of the present application can include additional implementation with respect to the order in which steps are performed, including a substantially simultaneous performance of the functions according to the functions involved, or in reverse order.

[0143] The logic and / or steps represented in the flow charts or otherwise described herein, for example, can be considered as a list of executable instructions for implementing the logic function, which can be specifically embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, apparatus, or device and execute the instructions, or in conjunction with these instructions execution systems, apparatus, or devices.

[0144] It should be understood that each part of the present application can be realized by hardware, software, firmware or a combination thereof. In the above embodiments, a plurality of steps or methods can be realized by software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above-mentioned embodiment methods can be completed by a program instructing the relevant hardware, which can be stored in a computer readable storage medium and includes one or a combination of the steps of the embodiment methods when executed.

[0145] In addition, each functional unit in each embodiment of the present application can be integrated in one processing module, or each unit can be physically present separately, or two or more units can be integrated in one module. The above-mentioned integrated module can be realized in the form of hardware or in the form of a software functional module. The above-mentioned integrated module, if realized in the form of a software functional module and sold or used as an independent product, can also be stored in a computer readable storage medium. The storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

[0146] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A mounting method based on a network disk service, characterized in that, The method comprises: obtaining a mounting request for mounting a target network disk service initiated by an application program of a terminal; analyzing the mounting request through an abstract interface layer of a unified interface, and determining a target plug-in; connecting the abstract interface layer through an adapter mode of the target plug-in to obtain the mounting request, and interacting with an API of the target network disk service according to the mounting request to determine target data; synchronously mounting the target data in the terminal and an edge node.

2. The mounting method based on the network disk service according to claim 1, characterized in that: Before the step of obtaining the mounting request for mounting the target network disk service initiated by the application program of the terminal, the method comprises: determining at least one of a gRPC service interface and a RESTful API interface, and compiling a service instance for interaction between a server and the terminal; the gRPC service interface and the RESTful API are used for synchronous mounting, and the synchronous mounting comprises at least one of uploading, downloading and authentication information interaction; when the service is started, establishing a connection with the service instance through the terminal.

3. The mounting method based on the network disk service according to claim 2, characterized in that: The step of establishing a connection with the service instance through the terminal when the service is started comprises: when the service is started and a registration center exists, registering the service instance of the service in the registration center, and establishing a connection with the service instance through the terminal, wherein the synchronous mounting utilizes the gRPC service interface; when the service is started and a registration center does not exist, establishing a connection with the service instance through the terminal, wherein the synchronous mounting utilizes the RESTful API interface based on a WebDAV standard.

4. The mounting method based on the network disk service according to any one of claims 1-3, characterized in that: The step of connecting the abstract interface layer through the adapter mode of the target plug-in to obtain the mounting request, and interacting with the API of the target network disk service according to the mounting request to determine target data comprises: bridging the API of the target network disk service and the abstract interface layer through the adapter mode of the target plug-in, and obtaining the mounting request; according to the mounting request, performing a read or write operation on the API of the target network disk service to determine target data read or target data written.

5. The mounting method based on the network disk service according to any one of claims 1-3, characterized in that: The step of synchronously mounting the target data in the terminal and the edge node comprises: when the target data is determined, authenticating the terminal, and determining the authority of the target data; when having the authority, encrypting the target data by using an SSL / TLS encryption technology, and synchronously mounting the encrypted target data in the terminal and the edge node.

6. The mounting method based on the network disk service according to any one of claims 1-3, characterized in that: The method further comprises: obtaining load information of each edge node, analyzing and predicting according to the load information to obtain a current load analysis result and a future load trend; when the current load analysis result or the future load trend represents overload, adding a new edge node, and configuring resources for the new edge node; quickly deploying the new edge node through an automatic script or a containerization technology, and evenly distributing traffic to all edge nodes through a load balancing strategy.

7. The mounting method based on the network disk service according to any one of claims 1-3, characterized in that: The method further comprises: In the case that the target data is synchronously mounted in the terminal and the edge node, the target data is cached by the edge node; In a preset time interval, access frequency of the data stored in the edge node is detected, and the stored data with the access frequency greater than a frequency threshold is saved locally; When the terminal initiates a request for the data stored in the edge node, geographical position information, network condition and load condition of the terminal are acquired to determine an optimal edge node from a plurality of edge nodes, and the request is responded through the optimal edge node.

8. A mounting apparatus based on a network disk service, characterized by comprising: Comprise: An acquisition module, configured to acquire a mounting request for mounting a target network disk service initiated by an application program of a terminal; An analysis module, configured to analyze the mounting request through an abstract interface layer of a unified interface to determine a target plug-in; A determination module, configured to connect the abstract interface layer through an adapter mode of the target plug-in to acquire the mounting request, and interact with an API of the target network disk service according to the mounting request to determine target data; A mounting module, configured to synchronously mount the target data in the terminal and the edge node.

9. An electronic device, comprising: Comprise: A processor and a memory, the memory stores instructions, the instructions are loaded and executed by the processor to implement the method of any one of claims 1-7. 10.A computer readable storage medium, the computer readable storage medium stores a computer program, the computer program is executed to implement the method of any one of claims 1-7.

Images