Data sharing method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a data sharing method and device, computer equipment, a computer readable storage medium and a computer program product, and relates to the technical field of big data. The method comprises the following steps: storing non-file format data sent by a data sharing requester into a cache; extracting non-file format data from the cache, and detecting a to-be-converted file format type of the non-file format data according to data content information and data identification information of the non-file format data; searching a general file format identifier corresponding to the format type of the file to be converted, and calling a general format conversion component corresponding to the general file format identifier to perform file format conversion on the non-file format data to obtain file format data; storing the file format data and a file format identifier corresponding to the file format data in a data sharing pool in an associated manner; and carrying out file format data interaction with the data requester based on the data sharing pool. By adopting the method, the convenience of data interaction can be improved.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a data sharing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of big data technology, data sharing technology has emerged, which can be used to share the data of one party with another party.

[0003] In traditional technology, the data to be shared by the data provider is usually directly stored in a data sharing pool, so that the data request acquirer can directly obtain the data to be shared from the data sharing pool.

[0004] However, since the data to be shared provided by the data provider usually has multiple data formats, and the data request acquirer usually requires multiple data formats, it is difficult to unify the data interaction method between the data provider and the data request acquirer, and the convenience of data interaction is low. Summary of the invention

[0005] Based on this, it is necessary to provide a data sharing method, apparatus, computer device, computer-readable storage medium and computer program product that can improve the convenience of data interaction in response to the above technical problems.

[0006] In a first aspect, the present application provides a data sharing method, comprising:

[0007] In response to a data sharing request from a data sharing requester, storing the non-file format data sent by the data sharing requester into a cache;

[0008] Extracting non-file format data from the cache, and detecting the file format type to be converted of the non-file format data according to data content information and data identification information of the non-file format data;

[0009] Finding a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier;

[0010] According to the called general format conversion component, the non-file format data is converted into a file format to obtain file format data;

[0011] The file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool;

[0012] Based on the data sharing pool, file format data is exchanged with the data requester.

[0013] In one embodiment, the interacting with the data requester in a file format based on the data sharing pool includes:

[0014] In response to a data acquisition request from a data requester, searching for file format data in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request;

[0015] If the search is successful, the found file format data is used as the target file format data;

[0016] If the search fails, performing a non-file data search in the cache according to the file content identifier to obtain a non-file data search result; generating target file format data according to the non-file data search result and the file format identifier;

[0017] The target file format data is fed back to the data requester.

[0018] In one embodiment, generating target file format data according to the non-file data search result and the file format identifier includes:

[0019] If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data;

[0020] If the non-file data search result indicates that the search fails, then according to the file content identifier, data is searched in the data sharing pool to obtain the first file format data;

[0021] searching for a customized file format corresponding to the file format identifier, and configuring a first customized format conversion component according to a common file format of the first file format data and the customized file format;

[0022] According to the first customized format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as target file format data.

[0023] In one embodiment, performing file format conversion on the found non-file format data according to the file format identifier to obtain target file format data includes:

[0024] If the file format identifier is a universal file format identifier, calling a universal format conversion component corresponding to the universal file format identifier to perform file format conversion on the found non-file format data to obtain target file format data;

[0025] If the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and the found non-file format data is converted into a file format according to the second customized format conversion component to obtain target file format data.

[0026] In one embodiment, the method further comprises:

[0027] Detecting a first usage frequency corresponding to each common file format and a second usage frequency corresponding to each customized file format;

[0028] A universal format conversion component library is updated according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

[0029] In one embodiment, updating the universal format conversion component library according to the first usage frequency and the second usage frequency includes:

[0030] For each of the universal file formats, if the first usage frequency of the universal file format is less than a first preset frequency threshold, removing the universal format conversion component corresponding to the universal file format from the universal format conversion component library;

[0031] For each of the customized file formats, if the second usage frequency of the customized file format is greater than a second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

[0032] In a second aspect, the present application also provides a data sharing device, including:

[0033] A cache module, configured to respond to a data sharing request from a data sharing requester and store the non-file format data sent by the data sharing requester into a cache;

[0034] A detection module, used to extract the non-file format data from the cache, and detect the file format type to be converted of the non-file format data according to the data content information and data identification information of the non-file format data;

[0035] A calling module, used for searching for a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier;

[0036] A format conversion module, used for performing file format conversion on the non-file format data according to the called general format conversion component to obtain file format data;

[0037] An associated storage module, used for associating and storing the file format data and the file format identifier corresponding to the file format data in a data sharing pool;

[0038] The data interaction module is used to interact with the data requester in file format based on the data sharing pool.

[0039] In one embodiment, the data interaction module is further used for:

[0040] In response to a data acquisition request from a data requester, a file format data search is performed in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request; if the search is successful, the found file format data is used as target file format data; if the search fails, a non-file data search is performed in the cache according to the file content identifier to obtain a non-file data search result; target file format data is generated according to the non-file data search result and the file format identifier; and the target file format data is fed back to the data requester.

[0041] In one embodiment, the data interaction module is further used for:

[0042] If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data; if the non-file data search result indicates that the search fails, data is searched in the data sharing pool according to the file content identifier to obtain first file format data; the custom file format corresponding to the file format identifier is searched, and a first custom format conversion component is configured according to the common file format of the first file format data and the custom file format; according to the first custom format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as the target file format data.

[0043] In one embodiment, the data interaction module is further used for:

[0044] If the file format identifier is a universal file format identifier, the universal format conversion component corresponding to the universal file format identifier is called to perform file format conversion on the found non-file format data to obtain target file format data; if the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and according to the second customized format conversion component, file format conversion is performed on the found non-file format data to obtain target file format data.

[0045] In one embodiment, the device further comprises:

[0046] An update module is used to detect a first usage frequency corresponding to each universal file format and a second usage frequency corresponding to each customized file format; and update a universal format conversion component library according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

[0047] In one embodiment, the update module is further used to:

[0048] For each of the universal file formats, if the first usage frequency of the universal file format is less than the first preset frequency threshold, the universal format conversion component corresponding to the universal file format is removed from the universal format conversion component library; for each of the customized file formats, if the second usage frequency of the customized file format is greater than the second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

[0049] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0050] In response to a data sharing request from a data sharing requester, the non-file format data sent by the data sharing requester is stored in a cache; the non-file format data is extracted from the cache, and the file format type to be converted of the non-file format data is detected according to the data content information and data identification information of the non-file format data; the universal file format identifier corresponding to the file format type to be converted is searched, and the universal format conversion component corresponding to the universal file format identifier is called; according to the called universal format conversion component, the non-file format data is converted into a file format to obtain file format data; the file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool; based on the data sharing pool, the file format data is interacted with the data requester.

[0051] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0052] In response to a data sharing request from a data sharing requester, the non-file format data sent by the data sharing requester is stored in a cache; the non-file format data is extracted from the cache, and the file format type to be converted of the non-file format data is detected according to the data content information and data identification information of the non-file format data; the universal file format identifier corresponding to the file format type to be converted is searched, and the universal format conversion component corresponding to the universal file format identifier is called; according to the called universal format conversion component, the non-file format data is converted into a file format to obtain file format data; the file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool; based on the data sharing pool, the file format data is interacted with the data requester.

[0053] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0054] In response to a data sharing request from a data sharing requester, the non-file format data sent by the data sharing requester is stored in a cache; the non-file format data is extracted from the cache, and the file format type to be converted of the non-file format data is detected according to the data content information and data identification information of the non-file format data; the universal file format identifier corresponding to the file format type to be converted is searched, and the universal format conversion component corresponding to the universal file format identifier is called; according to the called universal format conversion component, the non-file format data is converted into a file format to obtain file format data; the file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool; based on the data sharing pool, the file format data is interacted with the data requester.

[0055] In the above-mentioned data sharing method, apparatus, computer equipment, computer-readable storage medium and computer program product, the data sharing platform responds to the data sharing request of the data sharing requester, stores the non-file format data sent by the data sharing requester into the cache, and then after extracting the non-file format data from the cache, the file format type to be converted of the non-file format can be detected according to the data content information and data identification information of the non-file format data, and then the universal file format identification corresponding to the file format type to be converted is found, and the universal format conversion component corresponding to the universal file format identification is called, so that the non-file format data can be converted into standardized file format data, and the non-file format data can be reasonably converted into file format data by identifying the file format type to be converted of the non-file format data, and then the file format data and the file format identification corresponding to the file format data are associated and stored in the data sharing pool; the data requester can obtain the standardized file format data from the data sharing pool, so as to avoid the situation where the data sharing requester and the data requester cannot interact with each other due to different data interaction methods, thereby improving the convenience of data interaction between the data sharing requester and the data requester. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0057] Figure 1 This is an application environment diagram of a data sharing method in one embodiment of the present application;

[0058] Figure 2 This is a flowchart of a data sharing method in one embodiment of the present application;

[0059] Figure 3 A schematic diagram of a process for interacting file format data between a data sharing platform and a data requester in one embodiment of the present application;

[0060] Figure 4 A schematic diagram of a process for updating a general format conversion component library in one embodiment of the present application;

[0061] Figure 5 This is a structural block diagram of a data sharing device in one embodiment of the present application;

[0062] Figure 6 This is a diagram of the internal structure of a computer device in one embodiment of the present application. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. It should be noted that in the embodiments of the present application, some existing solutions in the industry such as certain software, components, models, etc. may be mentioned, and they should be considered as exemplary. Their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0064] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations. The acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with relevant provisions of national laws and regulations.

[0065] The data sharing method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 through a network. The data storage system can store data that the server 104 needs to process. The data storage system can be integrated on the server 104, or placed on the cloud or other network servers. The server 104 can be a data sharing platform, and the terminal 102 can be a data requester.

[0066] Specifically, in response to the data sharing request of the terminal 102, the server 104 stores the non-file format data sent by the data sharing requester in a cache; the server 104 extracts the non-file format data from the cache, and detects the file format type to be converted of the non-file format data based on the data content information and data identification information of the non-file format data; the server 104 searches for the universal file format identifier corresponding to the file format type to be converted, and calls the universal format conversion component corresponding to the universal file format identifier; the server 104 performs file format conversion on the non-file format data according to the called universal format conversion component to obtain file format data; the server 104 associates the file format data and the file format identifier corresponding to the file format data and stores them in a data sharing pool; based on the data sharing pool, the server 104 interacts with the data requester for file format data.

[0067] The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. The IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices may be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.

[0068] In an exemplary embodiment, Figure 2 As shown, a data sharing method is provided, which is applied to a data sharing platform. Figure 1 The server 104 in the example is used as an example to illustrate the method, which includes the following steps 202 to 206. Among them:

[0069] Step 202 : In response to a data sharing request from a data sharing requester, the non-file format data sent by the data sharing requester is stored in a cache.

[0070] Among them, a cache is set up in the data sharing platform, which is used to store non-file format data in various data formats provided by the data sharing requester; the data sharing requester is the data provider, and the data sharing requester will send non-file format data in various data formats to the data sharing platform; non-file format data may be data that does not exist in the form of a file.

[0071] Step 204: extract the non-file format data from the cache, and detect the file format type to be converted of the non-file format data according to the data content information and data identification information of the non-file format data.

[0072] Among them, data content information is information used to characterize data content characteristics, for example, it can be content keywords in non-file format data; data identification information can be information that characterizes data attributes of non-file format data, such as data length, data type, and whether the data is compressed.

[0073] As an example, step 204 includes: extracting non-file format data from the cache, extracting content keywords from the data content of the non-file format data, and extracting data identification information from the metadata of the non-file format data; text encoding the content keywords to obtain data content features, and information encoding the data identification information to obtain data identification features; fusing the data content features and the data identification features to obtain data features corresponding to the non-file format data; classifying the non-file format data according to the data features corresponding to the non-file format data to obtain the file format type to be converted of the non-file format data.

[0074] Step 206, searching for a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier.

[0075] The data sharing platform is provided with a general format conversion component library, and maintains the general format conversion component library in real time.

[0076] As an example, step 206 includes: searching for a universal file format identifier corresponding to the file format type to be converted; and calling a corresponding universal format conversion component from a universal format conversion component library according to the found universal file format identifier.

[0077] Step 208: Perform file format conversion on the non-file format data according to the called general format conversion component to obtain file format data.

[0078] Among them, the format conversion component is a set software module, and the non-file format data can be converted into corresponding file format data by running the general format conversion component; the file format data can be data existing in the form of a file.

[0079] As an example, step 208 includes: running the called format conversion component, and inputting the non-file format data into the universal format conversion component, using the universal format conversion component to perform file format conversion on the non-file format data to obtain file format data.

[0080] Step 210: associate the file format data and the file format identifier corresponding to the file format data and store them in a data sharing pool.

[0081] The file format identifier is used to identify the file format type corresponding to the file format data.

[0082] As an example, step 210 includes: associating and storing the file format identifier and the file format data corresponding to the file format data in a data sharing pool in a key-value pair manner.

[0083] Step 212: Based on the data sharing pool, the file format data is exchanged with the data requester.

[0084] As an example, step 212 includes: responding to a data acquisition request from a data requester, extracting a data format identifier from the data acquisition request, acquiring corresponding target file format data from a data sharing pool using the data format identifier, and feeding back the acquired target file format data to the data requester.

[0085] In the above data sharing method, the data sharing platform responds to the data sharing request of the data sharing requester, stores the non-file format data sent by the data sharing requester in the cache, and then after extracting the non-file format data from the cache, the file format type to be converted of the non-file format can be detected according to the data content information and data identification information of the non-file format data, and then the universal file format identifier corresponding to the file format type to be converted is found, and the universal format conversion component corresponding to the universal file format identifier is called, so that the non-file format data can be converted into standardized file format data, and the file format type to be converted of the non-file format data can be identified, and the non-file format data can be reasonably converted into file format data, and then the file format data and the file format identifier corresponding to the file format data are associated and stored in the data sharing pool; the data requester can obtain the standardized file format data from the data sharing pool, so as to avoid the situation where the data sharing requester and the data requester cannot interact with each other due to different data interaction methods, thereby improving the convenience of data interaction between the data sharing requester and the data requester.

[0086] In an exemplary embodiment, Figure 3 As shown, step 212 includes steps 302 to 306. Among them:

[0087] Step 302: In response to a data acquisition request from a data requester, a file format data search is performed in a data sharing pool according to a file content identifier and a file format identifier in the data acquisition request.

[0088] The identifier corresponding to the file format data in the data sharing pool may be a file content identifier and a file format identifier.

[0089] As an example, step 302 includes: in response to a data acquisition request from a data requester, extracting a file content identifier and a file format identifier from the data acquisition request, using the file content identifier and the file format identifier as indexes, and searching for corresponding file format data from a data sharing pool.

[0090] Step 304: If the search is successful, the found file format data is used as the target file format data and fed back to the data requester.

[0091] Step 306: If the search fails, a non-file data search is performed in the cache according to the file content identifier to obtain a non-file data search result.

[0092] As an example, steps 304 to 306 include: if the search is successful, the found file format data is fed back to the data requester as the target file format data; if the search fails, it means that the target file format data corresponding to the file content identifier may not have been converted into file format data, so according to the file content data, the corresponding non-file format data is searched from the cache to obtain the non-file data search result.

[0093] Step 308: Generate target file format data according to the non-file data search result and the file format identifier.

[0094] As an example, step 308 includes: if the non-file data search result is a successful search, converting the found non-file format data into file format data according to the universal format conversion component corresponding to the file format identifier, and feeding back the converted file format data as the target file format data to the data requester.

[0095] In some embodiments, generating target file format data according to the non-file data search result and the file format identifier includes:

[0096] If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data; if the non-file data search result indicates that the search fails, the data is searched in the data sharing pool according to the file content identifier to obtain first file format data; the custom file format corresponding to the file format identifier is searched, and a first custom format conversion component is configured according to the common file format and the custom file format of the first file format data; according to the first custom format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as the target file format data.

[0097] Specifically, if the non-file data search result indicates that the search is successful, the corresponding universal format conversion component is called according to the file format identifier, and the data format conversion is performed on the non-file format data found to obtain the target file format data; if the non-file data search result indicates that the search fails, it means that the non-file format data corresponding to the file content identifier has been converted into file format data of other file formats, and the file format corresponding to the file format identifier in the data acquisition request is not a universal file format, so according to the file content identifier, data search is performed in the data sharing pool to obtain first file format data; the custom file format corresponding to the file format identifier is searched, and the first custom format conversion component is configured according to the universal file format and the custom file format of the first file format data, wherein the first custom format conversion component is used to convert the file format data of the universal file format into file format data of the custom file format; according to the first custom format conversion component, the first file format data is converted into file format data of the universal file format to obtain second file format data, and the second file format data is used as the target file format data, wherein the first file format data is file format data of the universal file format existing in the data sharing pool, and the second file format data is file format data of the custom file format not existing in the data sharing pool.

[0098] Based on this, when non-file format data is found in the cache, the universal format conversion component corresponding to the file format identifier can be called to directly convert the non-file format data into the target file format identifier; when non-file format data is not found in the cache, the custom file format corresponding to the file format identifier in the data acquisition request is first searched for the first file format data of the universal file format in the data sharing pool according to the file content identifier, and the first custom format conversion component is configured according to the universal file format and the custom file format of the first file format data. The first custom format conversion component can be used to convert the file format of the first file format data from the universal file format to the custom file format, and obtain the second file format data, and the second file format data is used as the target file format data. In this way, the generation of file format data of the custom file format is realized, and even if the data requester makes a request to obtain the custom format data, the data sharing platform can respond in time and generate the target file format data matching the data acquisition request, thereby ensuring the accuracy and success rate of data sharing.

[0099] In some embodiments, performing file format conversion on the found non-file format data according to the file format identifier to obtain target file format data includes:

[0100] If the file format identifier is a universal file format identifier, the universal format conversion component corresponding to the universal file format identifier is called to perform file format conversion on the non-file format data found to obtain target file format data; if the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and according to the second customized format conversion component, file format conversion is performed on the non-file format data found to obtain target file format data.

[0101] Specifically, if the file format identifier is a universal file format identifier, the universal format conversion component corresponding to the universal file format identifier is called to perform file format conversion on the non-file format data found to obtain target file format data; if the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, wherein the second customized format conversion component is used to convert the non-file format data in the non-file format into customized file format data in the customized file format; the second customized format conversion component is called to convert the non-file format data found into target file format data.

[0102] Based on this, when the file format identifier in the data acquisition request corresponds to the universal file format, the universal format conversion component can be directly called from the data format conversion component library to convert the non-file format data into the target file format data; when the file format identifier in the data acquisition request corresponds to the customized file format, the second customized format conversion component corresponding to the customized file format can be configured to convert the data format of the non-file format data into the customized file format to obtain the target file format data. In this way, even if the data requester makes a request to obtain the customized format data, the data sharing platform can respond in time and generate the target file format data that matches the data acquisition request, thereby ensuring the accuracy and success rate of data sharing.

[0103] In this embodiment, after receiving a data acquisition request, the data sharing platform can search for file format data from the data sharing pool according to the file content identifier and the file format identifier in the data acquisition request; if the search is successful, the searched file format data can be fed back to the data requester as the target file format data; if the search fails, further data search is performed in the cache or data sharing pool based on the file content identifier alone, and the data for further data search is converted into the target file format data required by the data requester by calling a general format conversion component or configuring a customized format conversion component. In this way, regardless of whether the data request method requests file format data in a general file format or a customized file format, the data sharing platform can accurately respond to the data acquisition request, which helps to increase the response success rate of the data acquisition request.

[0104] It should be noted that, compared with configuring a customized format conversion component to perform file format conversion, calling a general format conversion component to perform file format conversion takes less time and is more efficient.

[0105] In some embodiments, reference Figure 4 , the above data sharing method further includes:

[0106] Step 402: Detect a first usage frequency corresponding to each common file format and a second usage frequency corresponding to each customized file format.

[0107] Step 404: Update the universal format conversion component library according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

[0108] Among them, the data sharing platform will maintain the corresponding usage frequency for each file format, and the file formats include general file formats and customized file formats.

[0109] As an example, steps 402 to 404 include: detecting a first usage frequency corresponding to each universal file format and a second usage frequency corresponding to each custom file format; in a universal format conversion component, eliminating universal file formats whose first usage frequency is greater than a first preset frequency threshold; setting a custom file format whose second usage frequency is greater than a second preset frequency threshold as a universal file format, and adding a format conversion component corresponding to the set universal file format to a universal format conversion component library.

[0110] As an example, updating the general format conversion component library according to the first usage frequency and the second usage frequency includes:

[0111] For each universal file format, if the first usage frequency of the universal file format is less than the first preset frequency threshold, the universal format conversion component corresponding to the universal file format is removed from the universal format conversion component library; for each customized file format, if the second usage frequency of the customized file format is greater than the second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added to the universal format conversion component library as a universal format conversion component.

[0112] The first usage frequency may be the number of times the common file format is used within a preset time period, and the second usage frequency may be the number of times the customized file format is used within a preset time period.

[0113] Specifically, for each universal file format, if the first usage frequency of the universal file format is less than the first preset frequency threshold, the universal format conversion component corresponding to the universal file format is removed from the universal format conversion component library; if the first usage frequency of the universal file format is not less than the first preset frequency threshold, the universal format conversion component corresponding to the universal file format is retained in the universal format conversion component library; for each customized file format, if the second usage frequency of the customized file format is greater than the second preset frequency threshold, the customized format conversion component corresponding to the customized file format is added to the universal format conversion component library as the universal format conversion component.

[0114] In this embodiment, the data sharing platform will flexibly set each file format as a general file format or a customized file format according to the frequency of use of each file format. In this way, a file format with a high frequency of use can be set as a general file format, so that the general file format data in the data sharing pool is the data with a high frequency of use. Therefore, it can be ensured that when the data sharing platform responds to a data acquisition request, it is more likely to directly obtain the response file format data from the data sharing pool, thereby improving the efficiency of data sharing.

[0115] In a complete embodiment, the data sharing platform responds to a data sharing request from a data sharing requester by storing the non-file format data sent by the data sharing requester in a cache; extracts the non-file format data from the cache, extracts content keywords from the data content of the non-file format data, and extracts data identification information from the metadata of the non-file format data; performs text encoding on the content keywords to obtain data content features, and performs information encoding on the data identification information to obtain data identification features; merges the data content features and the data identification features to obtain data features corresponding to the non-file format data; and classifies the non-file format data according to the data features corresponding to the non-file format data to obtain the file format type to be converted for the non-file format data.

[0116] Furthermore, a universal file format identifier corresponding to the file format type to be converted is searched; and based on the universal file format identifier found, a corresponding universal format conversion component is called from a universal format conversion component library; the called format conversion component is run, and non-file format data is input into the universal format conversion component, and the universal format conversion component is used to perform file format conversion on the non-file format data to obtain file format data; the file format identifier corresponding to the file format data and the file format data are associated and stored in a data sharing pool in the form of a key-value pair.

[0117] Furthermore, in response to a data acquisition request from a data requester, a file content identifier and a file format identifier are extracted from the data acquisition request, and the file content identifier and the file format identifier are used together as indexes to search for corresponding file format data from a data sharing pool; if the search is successful, the found file format data is fed back to the data requester as target file format data; if the search fails, it means that the target file format data corresponding to the file content identifier may not have been converted into file format data, and therefore, based on the file content data, the corresponding non-file format data is searched from the cache to obtain a non-file data search result.

[0118] Furthermore, if the non-file data search result indicates that the search is successful, the corresponding universal format conversion component is called according to the file format identifier, and the data format conversion is performed on the non-file format data found to obtain the target file format data; if the non-file data search result indicates that the search fails, it means that the non-file format data corresponding to the file content identifier has been converted into file format data of other file formats, and the file format corresponding to the file format identifier in the data acquisition request is not a universal file format, so according to the file content identifier, data search is performed in the data sharing pool to obtain first file format data; the custom file format corresponding to the file format identifier is searched, and the first custom format conversion component is configured according to the universal file format and the custom file format of the first file format data, wherein the first custom format conversion component is used to convert the file format data of the universal file format into file format data of the custom file format; according to the first custom format conversion component, the first file format data is converted into file format data of the universal file format to obtain second file format data, and the second file format data is used as the target file format data, wherein the first file format data is file format data of the universal file format existing in the data sharing pool, and the second file format data is file format data of the custom file format not existing in the data sharing pool.

[0119] In this embodiment, the situation where the data sharing requester and the data requester are unable to interact with each other due to different data interaction modes can be avoided, thereby improving the convenience of data interaction between the data sharing requester and the data requester.

[0120] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0121] Based on the same inventive concept, the embodiment of the present application also provides a data sharing device for implementing the data sharing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more data sharing device embodiments provided below can refer to the limitations on the data sharing method above, and will not be repeated here.

[0122] In an exemplary embodiment, Figure 5 As shown, a data sharing device is provided, including: a cache module 502, a detection module 504, a calling module 506, a format conversion module 508, an associated storage module 510 and a data interaction module 512, wherein:

[0123] The cache module 502 is used to store the non-file format data sent by the data sharing requester into the cache in response to the data sharing requester;

[0124] A detection module 504, configured to extract the non-file format data from the cache, and detect the file format type to be converted of the non-file format data according to the data content information and data identification information of the non-file format data;

[0125] A calling module 506 is used to find the universal file format identifier corresponding to the file format type to be converted, and call the universal format conversion component corresponding to the universal file format identifier;

[0126] The format conversion module 508 is used to convert the non-file format data into a file format according to the called general format conversion component to obtain file format data;

[0127] An associated storage module 510, configured to associate and store the file format data and the file format identifier corresponding to the file format data in a data sharing pool;

[0128] The data interaction module 512 is used to interact with the data requester in a file format based on the data sharing pool.

[0129] In one embodiment, the data interaction module is further used for:

[0130] In response to a data acquisition request from a data requester, a file format data search is performed in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request; if the search is successful, the found file format data is used as target file format data; if the search fails, a non-file data search is performed in the cache according to the file content identifier to obtain a non-file data search result; target file format data is generated according to the non-file data search result and the file format identifier; and the target file format data is fed back to the data requester.

[0131] In one embodiment, the data interaction module is further used for:

[0132] If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data; if the non-file data search result indicates that the search fails, data is searched in the data sharing pool according to the file content identifier to obtain first file format data; the custom file format corresponding to the file format identifier is searched, and a first custom format conversion component is configured according to the common file format of the first file format data and the custom file format; according to the first custom format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as the target file format data.

[0133] In one embodiment, the data interaction module is further used for:

[0134] If the file format identifier is a universal file format identifier, the universal format conversion component corresponding to the universal file format identifier is called to perform file format conversion on the found non-file format data to obtain target file format data; if the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and according to the second customized format conversion component, file format conversion is performed on the found non-file format data to obtain target file format data.

[0135] In one embodiment, the device further comprises:

[0136] An update module is used to detect a first usage frequency corresponding to each universal file format and a second usage frequency corresponding to each customized file format; and update a universal format conversion component library according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

[0137] In one embodiment, the update module is further used to:

[0138] For each of the universal file formats, if the first usage frequency of the universal file format is less than the first preset frequency threshold, the universal format conversion component corresponding to the universal file format is removed from the universal format conversion component library; for each of the customized file formats, if the second usage frequency of the customized file format is greater than the second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

[0139] Each module in the above data sharing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0140] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 6 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store file format data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a data sharing method is implemented.

[0141] Those skilled in the art will understand that Figure 6The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0142] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0143] In response to a data sharing request from a data sharing requester, storing the non-file format data sent by the data sharing requester into a cache;

[0144] Extracting non-file format data from the cache, and detecting the file format type to be converted of the non-file format data according to data content information and data identification information of the non-file format data;

[0145] Finding a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier;

[0146] According to the called general format conversion component, the non-file format data is converted into a file format to obtain file format data;

[0147] The file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool;

[0148] Based on the data sharing pool, file format data is exchanged with the data requester.

[0149] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0150] In response to a data acquisition request from a data requester, searching for file format data in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request;

[0151] If the search is successful, the found file format data is used as the target file format data;

[0152] If the search fails, performing a non-file data search in the cache according to the file content identifier to obtain a non-file data search result; generating target file format data according to the non-file data search result and the file format identifier;

[0153] The target file format data is fed back to the data requester.

[0154] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0155] If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data;

[0156] If the non-file data search result indicates that the search fails, then according to the file content identifier, data is searched in the data sharing pool to obtain the first file format data;

[0157] searching for a customized file format corresponding to the file format identifier, and configuring a first customized format conversion component according to a common file format of the first file format data and the customized file format;

[0158] According to the first customized format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as target file format data.

[0159] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0160] If the file format identifier is a universal file format identifier, calling a universal format conversion component corresponding to the universal file format identifier to perform file format conversion on the found non-file format data to obtain target file format data;

[0161] If the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and the found non-file format data is converted into a file format according to the second customized format conversion component to obtain target file format data.

[0162] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0163] Detecting a first usage frequency corresponding to each common file format and a second usage frequency corresponding to each customized file format;

[0164] A universal format conversion component library is updated according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

[0165] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0166] For each of the universal file formats, if the first usage frequency of the universal file format is less than a first preset frequency threshold, removing the universal format conversion component corresponding to the universal file format from the universal format conversion component library;

[0167] For each of the customized file formats, if the second usage frequency of the customized file format is greater than a second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

[0168] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0169] In response to a data sharing request from a data sharing requester, storing the non-file format data sent by the data sharing requester into a cache;

[0170] Extracting non-file format data from the cache, and detecting the file format type to be converted of the non-file format data according to data content information and data identification information of the non-file format data;

[0171] Finding a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier;

[0172] According to the called general format conversion component, the non-file format data is converted into a file format to obtain file format data;

[0173] The file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool;

[0174] Based on the data sharing pool, file format data is exchanged with the data requester.

[0175] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0176] In response to a data acquisition request from a data requester, searching for file format data in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request;

[0177] If the search is successful, the found file format data is used as the target file format data;

[0178] If the search fails, performing a non-file data search in the cache according to the file content identifier to obtain a non-file data search result; generating target file format data according to the non-file data search result and the file format identifier;

[0179] The target file format data is fed back to the data requester.

[0180] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0181] If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data;

[0182] If the non-file data search result indicates that the search fails, then according to the file content identifier, data is searched in the data sharing pool to obtain the first file format data;

[0183] searching for a customized file format corresponding to the file format identifier, and configuring a first customized format conversion component according to a common file format of the first file format data and the customized file format;

[0184] According to the first customized format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as target file format data.

[0185] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0186] If the file format identifier is a universal file format identifier, calling a universal format conversion component corresponding to the universal file format identifier to perform file format conversion on the found non-file format data to obtain target file format data;

[0187] If the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and the found non-file format data is converted into a file format according to the second customized format conversion component to obtain target file format data.

[0188] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0189] Detecting a first usage frequency corresponding to each common file format and a second usage frequency corresponding to each customized file format;

[0190] A universal format conversion component library is updated according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

[0191] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0192] For each of the universal file formats, if the first usage frequency of the universal file format is less than a first preset frequency threshold, removing the universal format conversion component corresponding to the universal file format from the universal format conversion component library;

[0193] For each of the customized file formats, if the second usage frequency of the customized file format is greater than a second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

[0194] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0195] In response to a data sharing request from a data sharing requester, storing the non-file format data sent by the data sharing requester into a cache;

[0196] Extracting non-file format data from the cache, and detecting the file format type to be converted of the non-file format data according to data content information and data identification information of the non-file format data;

[0197] Finding a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier;

[0198] According to the called general format conversion component, the non-file format data is converted into a file format to obtain file format data;

[0199] The file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool;

[0200] Based on the data sharing pool, file format data is exchanged with the data requester.

[0201] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0202] In response to a data acquisition request from a data requester, searching for file format data in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request;

[0203] If the search is successful, the found file format data is used as the target file format data;

[0204] If the search fails, performing a non-file data search in the cache according to the file content identifier to obtain a non-file data search result; generating target file format data according to the non-file data search result and the file format identifier;

[0205] The target file format data is fed back to the data requester.

[0206] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0207] If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data;

[0208] If the non-file data search result indicates that the search fails, then according to the file content identifier, data is searched in the data sharing pool to obtain the first file format data;

[0209] searching for a customized file format corresponding to the file format identifier, and configuring a first customized format conversion component according to a common file format of the first file format data and the customized file format;

[0210] According to the first customized format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as target file format data.

[0211] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0212] If the file format identifier is a universal file format identifier, calling a universal format conversion component corresponding to the universal file format identifier to perform file format conversion on the found non-file format data to obtain target file format data;

[0213] If the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and the found non-file format data is converted into a file format according to the second customized format conversion component to obtain target file format data.

[0214] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0215] Detecting a first usage frequency corresponding to each common file format and a second usage frequency corresponding to each customized file format;

[0216] A universal format conversion component library is updated according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

[0217] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0218] For each of the universal file formats, if the first usage frequency of the universal file format is less than a first preset frequency threshold, removing the universal format conversion component corresponding to the universal file format from the universal format conversion component library;

[0219] For each of the customized file formats, if the second usage frequency of the customized file format is greater than a second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

[0220] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0221] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0222] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A data sharing method, characterized in that: Using a data sharing platform, the method includes: In response to a data sharing request from a data sharing requester, storing the non-file format data sent by the data sharing requester into a cache; Extracting non-file format data from the cache, and detecting the file format type to be converted of the non-file format data according to data content information and data identification information of the non-file format data; Finding a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier; According to the called general format conversion component, the non-file format data is converted into a file format to obtain file format data; The file format data and the file format identifier corresponding to the file format data are associated and stored in a data sharing pool; Based on the data sharing pool, file format data is exchanged with the data requester.

2. The method according to claim 1, characterized in that The step of performing file format data interaction with a data requester based on the data sharing pool includes: In response to a data acquisition request from a data requester, searching for file format data in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request; If the search is successful, the found file format data is used as the target file format data; If the search fails, performing a non-file data search in the cache according to the file content identifier to obtain a non-file data search result; generating target file format data according to the non-file data search result and the file format identifier; The target file format data is fed back to the data requester.

3. The method according to claim 2, characterized in that The step of generating target file format data according to the non-file data search result and the file format identifier includes: If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data; If the non-file data search result indicates that the search fails, then searching for data in the data sharing pool according to the file content identifier to obtain data in a first file format; searching for a customized file format corresponding to the file format identifier, and configuring a first customized format conversion component according to a common file format of the first file format data and the customized file format; According to the first customized format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as target file format data.

4. The method according to claim 3, characterized in that The step of converting the found non-file format data into a file format according to the file format identifier to obtain target file format data includes: If the file format identifier is a universal file format identifier, calling a universal format conversion component corresponding to the universal file format identifier to perform file format conversion on the found non-file format data to obtain target file format data; If the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and the found non-file format data is converted into a file format according to the second customized format conversion component to obtain target file format data.

5. The method according to claim 1, characterized in that The method further comprises: Detecting a first usage frequency corresponding to each common file format and a second usage frequency corresponding to each customized file format; A universal format conversion component library is updated according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

6. The method according to claim 5, characterized in that The updating of the universal format conversion component library according to the first usage frequency and the second usage frequency includes: For each of the universal file formats, if the first usage frequency of the universal file format is less than a first preset frequency threshold, removing the universal format conversion component corresponding to the universal file format from the universal format conversion component library; For each of the customized file formats, if the second usage frequency of the customized file format is greater than a second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

7. A data sharing device, characterized in that: The device comprises: A cache module, configured to respond to a data sharing request from a data sharing requester and store the non-file format data sent by the data sharing requester into a cache; A detection module, used to extract the non-file format data from the cache, and detect the file format type to be converted of the non-file format data according to the data content information and data identification information of the non-file format data; A calling module, used for searching for a universal file format identifier corresponding to the file format type to be converted, and calling a universal format conversion component corresponding to the universal file format identifier; A format conversion module, used for performing file format conversion on the non-file format data according to the called general format conversion component to obtain file format data; An associated storage module, used for associating and storing the file format data and the file format identifier corresponding to the file format data in a data sharing pool; The data interaction module is used to interact with the data requester in file format based on the data sharing pool.

8. The device according to claim 7, characterized in that The data interaction module is also used for: In response to a data acquisition request from a data requester, searching for file format data in the data sharing pool according to a file content identifier and a file format identifier in the data acquisition request; if the search is successful, using the found file format data as target file format data; If the search fails, a non-file data search is performed in the cache according to the file content identifier to obtain a non-file data search result; Generate target file format data according to the non-file data search result and the file format identifier; The target file format data is fed back to the data requester.

9. The device according to claim 8, characterized in that The data interaction module is also used for: If the non-file data search result indicates that the search is successful, the found non-file format data is converted into a file format according to the file format identifier to obtain target file format data; If the non-file data search result indicates that the search fails, then searching for data in the data sharing pool according to the file content identifier to obtain data in a first file format; searching for a customized file format corresponding to the file format identifier, and configuring a first customized format conversion component according to a common file format of the first file format data and the customized file format; According to the first customized format conversion component, the first file format data is converted into a file format to obtain second file format data, and the second file format data is used as target file format data.

10. The device according to claim 9, characterized in that The data interaction module is also used for: If the file format identifier is a universal file format identifier, calling a universal format conversion component corresponding to the universal file format identifier to perform file format conversion on the found non-file format data to obtain target file format data; If the file format identifier is a customized file format identifier, a second customized format conversion component is configured according to the customized file format identifier, and the found non-file format data is converted into a file format according to the second customized format conversion component to obtain target file format data.

11. The device according to claim 7, characterized in that The device also includes: An update module is used to detect a first usage frequency corresponding to each universal file format and a second usage frequency corresponding to each customized file format; and update a universal format conversion component library according to the first usage frequency and the second usage frequency, wherein the universal format conversion component library includes at least one universal format conversion component.

12. The device according to claim 11, characterized in that The update module is also used for: For each of the universal file formats, if the first usage frequency of the universal file format is less than a first preset frequency threshold, removing the universal format conversion component corresponding to the universal file format from the universal format conversion component library; For each of the customized file formats, if the second usage frequency of the customized file format is greater than a second preset frequency threshold, the customized file format is identified as a new universal file format, and the customized format conversion component corresponding to the customized file format is added as a universal format conversion component in the universal format conversion component library.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images