WO2020168692A1

WO2020168692A1 - Mass data sharing method, open sharing platform and electronic device

Info

Publication number: WO2020168692A1
Application number: PCT/CN2019/100988
Authority: WO
Inventors: 潘森; 朱力鹏; 乔俊峰; 胡斌; 周爱华; 饶玮; 蒋静; 杨佩; 裘洪斌; 黄进
Original assignee: 全球能源互联网研究院有限公司; 国家电网有限公司; 国网上海市电力公司
Priority date: 2019-02-22
Filing date: 2019-08-16
Publication date: 2020-08-27
Also published as: CN109936571A; CN109936571B

Abstract

Disclosed are a mass data sharing method, an open sharing platform and an electronic device. The mass data sharing method comprises: receiving a target shared directory access request sent by a user terminal, wherein a target shared directory is constructed based on storage metadata of data requested to be accessed by the user terminal, and the target shared directory is associated with configuration metadata of a storage platform storing the data requested to be accessed by the user terminal; creating a container assembly according to the configuration metadata, wherein the container assembly pulls a mirror image file of the data requested to be accessed by the user terminal to form a shared gateway; connecting the user terminal and the shared gateway; and sending to the user terminal the data requested to be accessed by the user terminal.

Description

Mass data sharing method, open sharing platform and electronic equipment

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with an application number of 201910134290.1 on February 22, 2019. The entire content of this application is incorporated into this application by reference.

Technical field

This application relates to the field of big data open sharing technology, for example, it relates to a massive data sharing method, an open sharing platform and electronic equipment.

Background technique

With the rapid development of electronic informatization, multiple functional departments and even multi-functional internal organizations of large organizations have built multiple types of electronic business application systems to meet the business needs of their respective fields, and gradually accumulated huge data resources. These data resources are widely stored in different units, different departments, different systems and even different network environments in multiple locations and multi-level organizations, and there are many types of data. Due to the decentralized management of these business application systems, the inconsistent technical systems, inconsistent software and hardware standards, and poor data interface compatibility have led to serious problems of islanding and private closure of data resources. Most data resources cannot be integrated and shared. Different business application systems The low efficiency of data sharing and utilization between large-scale institutions poses serious challenges to the efficient and precise governance of large institutions.

Data sharing between different business application systems includes many forms. Among them, data retrieval, analysis, display, and export based on running components or tools on the big data storage platform are one of the common sharing methods. However, in related technologies , The data requester can directly connect with the data provider and access the source data in the data provider. Therefore, there is a risk of the source data being modified, which reduces the security of the source data.

Summary of the invention

The embodiments of the present application provide a massive data sharing method, an open sharing platform, and electronic equipment to solve the risk that the source data in the data provider can be directly accessed by the data requester in the related technology. Reduce the security of the source data.

In one embodiment, the embodiment of the present application provides a massive data sharing method, including: receiving a target shared directory access request sent by a user terminal; the target shared directory is constructed based on the storage metadata of the data requested by the user terminal, and the target The shared directory is associated with the configuration metadata of the storage platform that stores the data requested by the user terminal; the container component is created based on the configuration metadata, and the container component pulls the image file of the data requested by the user terminal to form a shared gateway; connects the user terminal with The shared gateway connects; the data requested by the user terminal is sent to the user terminal.

In one embodiment, an embodiment of the present application provides an open sharing platform, including: a request receiving module configured to receive a target shared directory access request sent by a user terminal; the target shared directory is based on the storage element of the data requested to be accessed by the user terminal Data is constructed, the target shared directory is associated with the configuration metadata of the storage platform that stores the data requested by the user terminal; the container creation module is set to create a container component based on the configuration metadata, and the container component pulls the data that the user terminal requests to access The mirror file forms a shared gateway; the terminal connection module is set to connect the user terminal with the shared gateway; the data sharing module is set to send the data requested by the user terminal to the user terminal.

In an embodiment, an embodiment of the present application provides an electronic device, including: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory is stored with computer instructions, and the processing The device executes the computer instructions to execute the massive data sharing method described in the foregoing embodiments.

In an embodiment, an embodiment of the present application provides a computer-readable storage medium that stores computer instructions, and the computer instructions are used to make the computer execute the massive data described in the above-mentioned embodiments. Sharing method.

Description of the drawings

FIG. 1 is a method flowchart of a massive data sharing method provided by an embodiment of this application;

Figure 2 is a flow chart of constructing a shared gateway provided by an embodiment of the application;

FIG. 3 is a method flowchart of another massive data sharing method provided by an embodiment of the application;

Figure 4 is a schematic diagram of the configuration of access permissions for HDFS storage platform data;

Figure 5 is a schematic diagram of the configuration of access permissions for HBase storage platform data and Hive storage platform data;

FIG. 6 is a functional block diagram of an open sharing platform provided by an embodiment of the application;

FIG. 7 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. The described embodiments are part of the embodiments of the present application, rather than all of the embodiments. In the description of this application, the terms "first", "second", and "third" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance.

Example 1

This embodiment provides a massive data sharing method, which is suitable for a data exchange platform, which is an information exchange platform constructed based on a computer network. The data exchange platform can be connected to multiple data storage platforms to receive and store data from multiple data platforms as the basis for data sharing; and can be connected to user terminals to send data requested by the user terminal to the user terminal to realize data sharing.

Fig. 1 shows a flowchart of a method for sharing massive data according to an embodiment of the present application. As shown in Fig. 1, the method may include the following steps:

S1010: Access multiple data from multiple data storage platforms. In an embodiment, the multiple data storage platforms include the Hadoop Distributed File System (HDFS) storage platform, the Hadoop Database (HBase) storage platform, and the data warehouse tool Hive storage platform. One or more of, among them, the HDFS storage platform can store text files, semi-structured data, unstructured data, etc.; the HBase storage platform can store non-relational data, and the Hive storage platform can store relational data.

S1020: Form a mirror warehouse of multiple data. In one embodiment, the mirror warehouse includes multiple mirror files of data, where the mirror files are implemented by copying data, and the data stored in the mirror files are the same as the original data.

S1030: Obtain storage metadata and configuration metadata of multiple data storage platforms. In an embodiment, the storage metadata is used to describe multiple data. In an embodiment, the storage metadata of one piece of data may include multiple metadata items.

When the accessed data is data of the HDFS storage platform, the metadata items of the storage metadata of the data may include: data name (dataName), data storage path (dataPath), data owner (dataOwner), data content description ( dataDesc), one or more of data storage size (dataSize), data storage type (datatype), and data storage date (dataDate).

When the accessed data is the data of the HBase storage platform, the metadata items of the data storage metadata can include: data table name (tableName), database to which the data table belongs (tableDatabase), data table description (tableDesc), data table One or more of the creation date (tableDate) and the data table creation statement (tableCreateSql).

When the accessed data is the data of the Hive storage platform, the metadata items of the storage metadata of the data can include: data table name (tableName), database to which the data table belongs (tableDatabase), data table description (tableDesc), data table One or more of the creation date (tableDate) and the data table creation statement (tableCreateSql).

The type and quantity of metadata items can be adjusted according to the needs of actual application scenarios. The names of the above-mentioned metadata items are only examples to facilitate those skilled in the art to understand the technical solutions of the embodiments of this application, and should not constitute the embodiments of this application. Limit, in addition, when a data is updated, re-access and update the storage metadata of the data.

In one embodiment, the configuration metadata is used to describe multiple storage platforms, and defines the service name, address, port, user, security, etc. of the storage platform. For example, when the storage platform is an HDFS storage platform, the configuration metadata can be Including core-site.xml, hdfs-site.xml, mapred-site.xml and yarn-site.xml configuration files in the HDFS storage platform; when the storage platform is an HBase storage platform, the configuration metadata can include the HBase storage platform Configuration files such as hbase-site.xml in the Hive storage platform; when the storage platform is the Hive storage platform, the configuration metadata can include configuration files such as hive-site.xml in the Hive storage platform. In one embodiment, when the configuration metadata of a storage platform is updated, the configuration metadata of the storage platform is re-accessed and updated.

S1040: Construct a shared directory of multiple data according to the storage metadata to form a shared directory table, and associate the multiple shared directories in the shared directory table with configuration metadata corresponding to the multiple shared directories. In an embodiment, the shared directory table may be constructed by filtering and integrating the metadata items of the storage metadata of multiple data. Following the above example, when multiple data storage platforms include HDFS storage platform, HBase storage platform and Hive storage platform, the data name of the HDFS storage platform data (dataName) and the data table name of the HBase storage platform data (tableName) can be used , And the data table name (tableName) of the Hive storage platform data are integrated into one table item "data name (dataName)".

S1050: Receive the target shared directory access request sent by the user terminal. In one embodiment, the target shared directory is a shared directory constructed based on the data requested to be accessed by the user terminal in the shared directory table. In one embodiment, the shared directory table is constructed based on the storage metadata of multiple data, including Store some or all of the metadata items in the metadata. Therefore, the user terminal can browse or search the shared directory table according to the information of the data (such as data name, data storage time or data content description, etc.) that it needs to access. In this way, the shared directory corresponding to the data to be accessed is determined, the shared directory is the target shared directory, and the user terminal requests to access the data corresponding to the target shared directory by sending a target shared directory access request.

S1060: Create a container component according to the configuration metadata, and the container component pulls the image file of the data requested by the user terminal to form a shared gateway. In one embodiment, the configuration metadata refers to the configuration metadata associated with the target shared directory. Through the configuration metadata, the storage mode of the data requested by the user terminal (which type of storage platform is the data from Access data) to create a corresponding type of container component. In an embodiment, the construction process of the shared gateway is explained by taking the data requested by the user terminal as the data accessed by the HDFS storage platform as an example. As shown in FIG. 2, the construction process includes the following steps:

S1: The client submits the Pod specification file for creating HDFS to the Application Programming Interface (API) server.

S2: The API server writes the Pod object to the etcd data storage area (distributed consistent key-value storage system data storage area).

S3: The Scheduler automatically discovers the Pod objects newly created by the API server that are not bound to any node through the monitor.

S4: Scheduler allocates nodes for new unbound pods and updates them to the API server.

S5: The API server writes this pod node allocation information to the etcd data storage area.

S6: The Kubelet container management service on each node automatically discovers the new Pod assigned to it through the monitor.

S7: The Kubelet container management service calls the Docker interface, pulls the HDFS image file (the radial file of the data that the user terminal requests to access), and creates an HDFS container on its node.

S8: The HDFS container is created and started, the HDFS configuration file (configuration metadata) is loaded, and the Pod is started.

S9: The Kubelet container management service updates the pod status to the API server; the API server saves the pod status to etcd.

S10: The API server writes the HDFS pod node status information to the etcd data storage area, and the shared gateway is created.

The client, API server, etcd data storage area, Scheduler, Kubelet container management service, and Docker interface in the above S1-S10 are all container components.

When the data that the user terminal requests to access is the data accessed by the HBase storage platform or the hive storage platform, the construction process of the shared gateway can be understood with reference to the specific content of the above S1-S10, and will not be repeated here.

S1070: Connect the user terminal with the shared gateway. In an embodiment, a data sharing interface is generated on the sharing gateway, and when a data access request sent by the user terminal to the sharing gateway is received, the user terminal is connected to the data sharing interface on the sharing gateway. In an embodiment, when a data access request sent by a shared data request to the shared gateway is received, the shared data requester can be directly used as the user terminal (the user terminal that sent the target shared directory access request), and It connects with the shared gateway; it can also generate the login interface of the shared gateway. After obtaining the login information of the shared data requester, it is judged whether it is a user terminal (the user terminal that sent the target shared directory access request), and only in this When the shared data requester is a user terminal, connect it to the shared gateway, so that the data in the shared gateway is finally obtained by the user terminal that requested the data, preventing the data in the shared gateway from being obtained by other illegal user terminals, and improving the Data sharing security of massive data sharing method.

S1080: Send the data requested to be accessed by the user terminal to the user terminal.

In the embodiment of the present application, after receiving the target shared directory access request sent by the user terminal, the container component is created according to the configuration metadata of the storage platform that stores the data requested to be accessed by the user terminal and is associated with the target shared directory, The container component pulls the image file of the data requested by the user terminal to form a shared gateway (that is, a virtual data provider) to connect to the user terminal and share the data requested by the user terminal to the user terminal. The shared gateway can separate the data supply and the data operation environment of the user terminal, prevent the source data in the data provider from being modified, and ensure the security of the data provider itself.

As an optional implementation manner of the embodiments of the present application, as shown in FIG. 1, the mass data sharing method may further include the following steps:

S1090: Determine whether the connection between the user terminal and the shared gateway is disconnected. When the shared data requestor is directly used as the user terminal, it can be determined that the connection between the user terminal and the shared gateway is disconnected when the step of sending the data requested by the user terminal to the user terminal (ie S1080) is completed; When it is necessary to generate the login interface of the shared gateway to obtain the login information of the shared data requester and determine whether it is a user terminal, the step of sending the data requested by the user terminal to the user terminal (i.e. S1080) can be completed, or When the user terminal logs out, it is judged that the connection between the user terminal and the shared gateway is disconnected.

S1100: Destroy the shared gateway when the connection between the user terminal and the shared gateway is disconnected.

Since the shared gateway used as a virtual data provider is dynamically created based on the user terminal’s target shared directory access request, only when the user terminal connects to the shared gateway and obtains data, the server resources occupied by it will be used. When the connection between the user terminal and the shared gateway is disconnected, the server resources occupied by the shared gateway will be idle, causing a waste of resources. Therefore, in this embodiment, when the connection between the user terminal and the shared gateway is disconnected , Destroying the shared gateway can recover the server resources occupied by the shared gateway in time, prevent the server resources from being idle, and further enable the server resources to be reused, reducing the server cost for the massive data sharing method.

Fig. 3 shows a flowchart of a method for analyzing a video code stream according to another embodiment of the present application. As shown in Fig. 3, the method may include the following steps:

S201: Access multiple data from multiple data storage platforms. For details, refer to S1010.

S202: Form a mirror warehouse of multiple data. In an embodiment, the mirror warehouse includes a plurality of mirror files of data. For details, refer to S1020.

S203: Obtain storage metadata and configuration metadata of multiple data storage platforms. For details, refer to S1030.

S204: Construct a shared directory of multiple data according to the stored metadata to form a shared directory table, and associate the multiple shared directories in the shared directory table with configuration metadata corresponding to the multiple shared directories. For details, refer to S1040.

S205: Configure access permissions for data corresponding to each shared directory in the shared directory table. In an embodiment, the access permissions for HDFS storage platform data, HBase storage platform data, and Hive storage platform data can all be defined and divided by their users. For HDFS storage platform data, every HDFS file or directory has an owner (owner) and a group (group). A file or directory has different permissions to its owner, other user terminals in the same group, and all other user terminals. For example, you can set the access permission to the owner to have all permissions to read, write, and execute, and other user terminals in the same group only Have read permission, all user terminals outside the group have no permission. For HBase storage platform data and Hive storage platform data, it is achieved by granting different read and write permissions to user terminals. For administrator user terminals, all permissions are granted to data. For general user terminals, there is no permission by default. .

In one embodiment, each user who needs to request access to data (herein referred to as a legitimate user) is assigned a unique terminal user name as the basis for data access authority management.

For example, for HDFS storage platform data, the data access permission mapping is realized by mapping the terminal user name and the user group to which the HDFS storage platform data belongs. As shown in Figure 4, the user terminal with the terminal user name datauser1 needs to request access to the data Files (File)1 and File2, and need to have all the permissions to read and write, you can add them to the user group "gp1" of File1 and set them as the owner "ow1" of the user group "gp1". At the same time, Add datauser1 to the user group "gp2" of File2 and set it as the owner "ow2" of the user group "gp2".

For HBase storage platform data and Hive storage platform data (usually a data table), after determining the user name of the terminal that needs to request access to the data, the read permission of the specified table is synchronously assigned to the terminal user name. After the sharing is completed (S209, execution ends) After), cancel all permissions that have been granted. Following the above example, as shown in Figure 5, when the user terminal with the terminal user name datauser1 needs to request access to data tables (Table)1 and Table2, directly set datauser1 as the data table query permission user group "m1" of Table1 Set datauser1 as a user terminal in the data table query permission user group "m2" of Table2, so as to give datauser1 the right to read Table1 and Table2.

In an embodiment, the configuration of data access permissions can be performed by adding metadata items to the storage metadata of the data. For example, for HDFS storage platform data, the metadata item data owner (dataOwner) and data owner can be added. The user group (dataOwnerGroup) where the person belongs, and record the corresponding information under the corresponding metadata item to complete the configuration of the access rights to the HDFS storage platform data; for HBase storage platform data and Hive storage platform data, you can add data table management The user (tableAdmin) and the data table query authority user (tableSelectUser), and record the corresponding information under the corresponding metadata items, complete the configuration of the access rights items for HBase storage platform data and Hive storage platform data. In an embodiment, for the user name of the data administrator (tableAdmin) defined in the storage metadata of the HBase storage platform data and the Hive storage platform data, since it has all the permissions of the data table, in order to ensure the security of the data table Therefore, these usernames are regarded as reserved users and they are forbidden to log in on the shared terminal.

The specific names such as the terminal user name, data name, and metadata item name mentioned above are all examples to facilitate those skilled in the art to understand the technical solutions of the embodiments of the present application, and should not limit the embodiments of the present application.

S206: Receive the target shared directory access request sent by the user terminal. For details, refer to S1050.

S207: Determine whether the user terminal has the authority to access the data corresponding to the target shared directory.

S208: When the user terminal has the permission to access the data corresponding to the target shared directory, create a container component according to the configuration metadata, and the container component pulls a mirror file of the data requested by the user terminal to form Shared gateway. For details, refer to S1060.

S209: Connect the user terminal with the shared gateway. For details, refer to S1070.

S210: Send the data requested to be accessed by the user terminal to the user terminal.

In the embodiment of the present application, by configuring the access permissions for data corresponding to multiple shared directories in the shared directory table, only some user terminals (legitimate users) with access permissions are allowed to access the data corresponding to the shared directory, preventing the shared directory The corresponding data is obtained and used by illegal user terminals, which improves the data sharing security of the massive data sharing method.

As an optional implementation manner of the embodiment of the present application, the mass data sharing method may further include the following steps:

S211: Determine whether the connection between the user terminal and the shared gateway is disconnected. For details, refer to S1090.

S212: When the connection between the user terminal and the shared gateway is disconnected, destroy the shared gateway. For details, refer to S1100.

Example 2

FIG. 6 shows a principle block diagram of an open sharing platform according to an embodiment of the present application. The device can be configured to implement the massive data sharing method described in Embodiment 1 or any optional implementation thereof. As shown in FIG. 6, the open sharing platform includes: a request receiving module 10, a container creation module 20, a terminal connection module 30, and a data sharing module 40.

Wherein, the request receiving module 10 is configured to receive a target shared directory access request sent by a user terminal; the target shared directory is constructed based on the storage metadata of the data requested to be accessed by the user terminal, and the target shared directory is associated with storing the user The configuration metadata of the storage platform of the data that the terminal requests to access is associated; the container creation module 20 is configured to create a container component based on the configuration metadata, and the container component pulls a mirror file of the data requested by the user terminal to form Shared gateway; the terminal connection module 30 is configured to connect the user terminal with the shared gateway; the data sharing module 40 is configured to send the data requested by the user terminal to be accessed to the user terminal.

As an optional implementation manner of the embodiment of the present application, as shown in FIG. 6, the open sharing platform further includes: a connection judgment module 50 and a resource recovery module 60.

Wherein, the connection determination module 50 is configured to determine whether the connection between the user terminal and the sharing gateway is disconnected; the resource recovery module 60 is configured to determine whether the connection between the user terminal and the sharing gateway is disconnected Next, destroy the shared gateway.

The embodiment of the present application also provides an electronic device. As shown in FIG. 7, the electronic device may include a processor 71 and a memory 72, where the processor 71 and the memory 72 may be connected by a bus or other means. Take bus connection as an example.

The processor 71 may be a central processing unit (Central Processing Unit, CPU). The processor 71 may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), or Chips such as other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above-mentioned multiple types of chips.

As a non-transitory computer-readable storage medium, the memory 72 can be configured to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as program instructions corresponding to the massive data sharing method in the embodiment of the present application. Modules (such as the request receiving module 10, the container creation module 20, the terminal connection module 30 and the data sharing module 40 in FIG. 6). The processor 71 executes multiple functional applications and data processing of the processor by running non-transitory software programs, instructions, and modules stored in the memory 72, that is, implements the method described in any of the foregoing embodiments.

The memory 72 may include a program storage area and a data storage area. The program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created by the processor 71 and the like. In addition, the memory 72 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory 72 may optionally include memories remotely provided with respect to the processor 71, and these remote memories may be connected to the processor 71 through a network. Examples of the aforementioned networks include the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The one or more modules are stored in the memory 72, and when executed by the processor 71, the mass data sharing method in the embodiment shown in FIGS. 1-5 is executed.

The specific details of the above electronic device can be understood by referring to the corresponding related description and effects in the embodiments shown in FIG. 1 to FIG. 5, and will not be repeated here.

Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. During execution, it may include the process of the method described in any of the foregoing embodiments. Wherein, the storage medium may be a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), a random access memory (RAM), a flash memory (Flash Memory), a hard disk (Hard Disk Drive, abbreviation: HDD) or solid-state drive (Solid-State Drive, SSD), etc.; the storage medium may also include a combination of the foregoing types of memories.

Claims

A massive data sharing method, including:

Receive a target shared directory access request sent by the user terminal; the target shared directory is constructed based on the storage metadata of the data requested to be accessed by the user terminal, and the target shared directory is connected to a storage platform that stores the data requested to be accessed by the user terminal Is associated with the configuration metadata;

Create a container component according to the configuration metadata, and the container component pulls the image file of the data requested by the user terminal to form a shared gateway;

Connecting the user terminal with the shared gateway;

Sending the data requested by the user terminal to access to the user terminal.
The method according to claim 1, further comprising:

Determine whether the connection between the user terminal and the shared gateway is disconnected;

When the connection between the user terminal and the shared gateway is disconnected, destroy the shared gateway.
The method according to claim 1, further comprising:

Access multiple data from multiple data storage platforms;

Forming a mirror warehouse of the multiple data; the mirror warehouse includes mirror files of the multiple data;

Acquiring storage metadata and configuration metadata of the multiple data storage platforms; the storage metadata is used to describe the multiple data, and the configuration metadata is used to describe the multiple storage platforms;

Construct a shared directory of the multiple data according to the storage metadata to form a shared directory table, and correlate the multiple shared directories in the shared directory table with the configuration metadata corresponding to the multiple shared directories, respectively United.
The method according to claim 3, further comprising:

Configure access permissions for data corresponding to multiple shared directories in the shared directory table.
The method according to claim 4, before said creating a container component according to said configuration metadata, said container component pulling a corresponding image file to form a shared gateway, further comprising:

Determine whether the user terminal has the authority to access the data corresponding to the target shared directory; in the case that the user terminal has the authority to access the data corresponding to the target shared directory, create a container component according to the configuration metadata, The container component pulls the image file of the data requested by the user terminal to form a shared gateway.
The method according to claim 1, wherein said connecting said user terminal with said shared gateway comprises:

Generating a login interface of the shared gateway;

Obtain the login information of the requesting party of the shared data;

Determine whether the shared data requestor is the user terminal;

In a case where the shared data requestor is the user terminal, connect the user terminal with the sharing gateway.
The method according to claim 3, wherein the data storage platform comprises one or more of the Hidupu Distributed File System HDFS storage platform, the Hidupu database HBase storage platform, and the data warehouse tool Hive storage platform.
An open sharing platform, including:

The request receiving module is configured to receive a target shared directory access request sent by the user terminal; the target shared directory is constructed based on the storage metadata of the data requested to be accessed by the user terminal, and the target shared directory is configured to store the user terminal request The configuration metadata of the storage platform of the accessed data is associated;

A container creation module, configured to create a container component based on the configuration metadata, and the container component pulls a mirror file of the data requested by the user terminal to form a shared gateway;

A terminal connection module, configured to connect the user terminal with the shared gateway;

The data sharing module is configured to send the data requested to be accessed by the user terminal to the user terminal.
The open sharing platform according to claim 8, further comprising:

The connection judgment module is configured to judge whether the connection between the user terminal and the sharing gateway is disconnected;

The resource recovery module is configured to destroy the shared gateway when the connection between the user terminal and the shared gateway is disconnected.
An electronic device including:

A memory and a processor, the memory and the processor are in communication connection with each other, and computer instructions are stored in the memory, and the processor executes the computer instructions by executing any one of claims 1-7 The method described.
A computer-readable storage medium storing computer instructions for causing the computer to execute the method according to any one of claims 1-7.