Data processing method and system, server, storage medium and program product

Abstract

The invention provides a data processing method and system, a server, a storage medium and a program product. The method relates to the computer technology, uses a basic storage product to proxy a data request for an upper storage application, forwards request meta-information of the data request to the upper storage application, and returns a second processing result of the data request to an end side device according to a first processing result of the upper storage application for the request meta-information, a storage gateway of an upper-layer storage application does not need to be additionally added, only basic storage products are exposed to a user, subsequent service implementation details are hidden, the user does not perceive upgrading of the storage layout of the upper-layer storage application, and integrity of the upper-layer storage application and upgrading of the storage layout are facilitated; the user can complete operations such as data uploading and downloading by sending the data request to the basic storage product once, and the user only needs to manage one domain name and the single domain name certificate, so that the domain name management cost of the user is reduced, and the data operation efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data storage, and in particular to a data processing method, system, server, storage medium and program product. Background Art

[0002] With the development of cloud computing and storage technology, a variety of storage products based on Infrastructure as a Service (IaaS) have emerged, which are called basic storage products. These basic storage products can be systems or services used to store user data. Users can save, modify, and read their own data through basic storage products. For example, typical basic storage products include Object Storage Service (OSS), file storage system, etc.

[0003] The storage gateway of traditional basic storage products only accepts the application programming interface (API) defined by the storage product. For example, for OSS, users must access it through the OSS API. Other requests that do not conform to the OSS API format will be rejected by OSS.

[0004] When upper-layer products based on PaaS (Platform-as-a-Service) / SaaS (Software-as-a-Service) build higher-layer storage applications based on basic storage products (such as OSS), it is necessary to build an additional set of storage gateways of its own and define the API of the upper-layer storage application to provide services to users. However, because the underlying storage is implemented based on basic storage products (such as OSS), the API of the upper-layer storage application and the API of the basic storage product (such as OSS) will be exposed to users at the same time. Users will also perceive two storage products at the same time and need to manage the domain names, single domain name certificates, etc. of the two storage products at the same time, which increases the user management cost. Since the underlying storage details of the storage application layer are exposed to users, it is not conducive to the integrity of the upper-layer storage application and the upgrade of the storage layout in the future. Summary of the invention

[0005] The present application provides a data processing method, system, server, storage medium and program product, which are used to solve the problem that the details of the underlying basic storage products are exposed to the users of the upper-level storage applications, the user management cost is high, and it is not conducive to the integrity of the upper-level storage applications and the future upgrade of the storage layout.

[0006] In a first aspect, the present application provides a data processing method, which is applied to a basic storage product, and the method comprises:

[0007] A data request from a receiving end-side device to an upper-layer storage application, wherein the data request includes request meta-information;

[0008] Forwarding the request meta information to the upper-layer storage application, and receiving a first processing result of the request meta information by the upper-layer storage application;

[0009] According to the first processing result of the request meta-information by the upper-layer storage application, a second processing result of the data request is determined, and the second processing result is returned to the end-side device.

[0010] In a second aspect, the present application provides a data processing method, which is applied to an object storage service, and the method includes:

[0011] A data request from a receiving device to a network disk and photo album service, wherein the data request includes request meta information;

[0012] Forwarding the request meta information to the network disk and photo album service, and receiving a first processing result of the request meta information by the network disk and photo album service;

[0013] According to the first processing result of the network disk and album service on the request meta-information, a second processing result of the data request is determined, and the second processing result is returned to the terminal device.

[0014] In a third aspect, the present application provides a server, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the server executes a method provided in any of the preceding aspects.

[0015] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions. When a processor executes the computer-executable instructions, the method provided in any of the aforementioned aspects is implemented.

[0016] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method provided in any of the aforementioned aspects.

[0017] In a sixth aspect, the present application provides a data processing system, including: a basic storage product and an upper-layer storage application built on the basic storage product;

[0018] The basic storage product is used to: receive a data request from a terminal device to the upper storage application, and forward request meta information in the data request to the upper storage application;

[0019] The upper storage application is used to: in response to receiving the request meta information, process the request meta information to obtain a first processing result, and return the first processing result to the basic storage product;

[0020] The basic storage product is also used to: determine a second processing result for the data request based on the first processing result returned by the upper-layer storage application, and return the second processing result to the end-side device.

[0021] The data processing method, system, server, storage medium and program product provided by the present application receive a data request for an upper-layer storage application through a basic storage product, forward request meta-information in the data request to the upper-layer storage application, receive a first processing result of the upper-layer storage application on the request meta-information, determine a second processing result of the data request according to the first processing result of the upper-layer storage application on the request meta-information, and return the second processing result to the terminal device, by using the basic storage product to proxy the data request for the upper-layer storage application, without the need to add an additional storage gateway for the upper-layer storage application, only the basic storage product is exposed to the user, and the service implementation details after the basic storage product are invisible to the user, and the upgrade of the storage layout of the upper-layer storage application is imperceptible to the user, which is beneficial to the integrity of the upper-layer storage application and the future upgrade of the storage layout; and the user can complete data upload, download and other operations by sending a data request to the basic storage product once, and the user only needs to manage a domain name and a single domain name certificate, which not only reduces the user's management cost of the domain name, but also improves the efficiency of data operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0023] Figure 1 An architectural diagram of a traditional upper-layer storage application based on a basic storage product provided for this application;

[0024] Figure 2 A framework diagram of a data upload process of a traditional upper storage application provided by this application;

[0025] Figure 3 A framework diagram of a data download process of a traditional upper storage application provided by this application;

[0026] Figure 4 The architecture diagram of the data processing system provided for this application;

[0027] Figure 5A flowchart of a data processing method provided for an exemplary embodiment of the present application;

[0028] Figure 6 A flow chart of a method for uploading data provided by an exemplary embodiment of the present application;

[0029] Figure 7 An interactive flow chart of a data uploading method provided by an exemplary embodiment of the present application;

[0030] Figure 8 A flowchart of data uploading provided by an exemplary embodiment of the present application;

[0031] Fig. 9 A flow chart of a method for data downloading provided in an exemplary embodiment of the present application;

[0032] Fig.10 An interactive flow chart of a data downloading method provided in an exemplary embodiment of the present application;

[0033] Fig.11 A flowchart of data downloading provided in an exemplary embodiment of the present application;

[0034] Fig.12 A flow chart of a data processing method provided for another exemplary embodiment of the present application;

[0035] Fig.13 A schematic diagram of the structure of a server provided in an embodiment of the present application.

[0036] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0037] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0038] It should be noted that the user information (including but not limited to user device information, user attribute 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 laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0039] First, the terms involved in this application are explained:

[0040] Storage product: a system or service used to store user data. Users can save, modify, and read their own data through storage products.

[0041] Basic storage products: refers to storage products at the IaaS layer. Typical basic storage products include object storage OSS, file storage, etc.

[0042] Storage Gateway: The storage product front-end machine, also known as the storage product gateway, is a component of the storage product implementation that is used to process requests from users and then persistently store data from users by calling internal subsystems (such as key-value storage).

[0043] Storage applications: refers to PaaS / SaaS layer storage products, which provide users with richer storage capabilities. Storage applications are usually built based on IaaS layer storage products (such as object storage). Typical storage applications include Drive and Photo Service (PDS). In this embodiment, in order to distinguish from the storage products of the IaaS layer, the storage applications of the PaaS / SaaS layer are called upper-layer storage applications, and the storage products of the IaaS layer are called basic storage products.

[0044] Figure 1 This is an architecture diagram of a traditional upper-layer storage application based on basic storage products. Figure 1 As shown in the figure, the basic storage product has its own storage gateway (Storage Gateway 1 shown in the figure). Storage Gateway 1 of the basic storage product defines the API of the basic storage product to provide services to users. Users need to access the basic storage product through this API. For example, for OSS, users must access it through the OSS API. Other requests that do not conform to the OSS API format will be rejected by OSS.

[0045] like Figure 1As shown in the figure, the upper-layer storage application built on the basic storage product needs to build an additional set of its own storage gateways (such as storage gateway 2 shown in the figure). The storage gateway 2 of the upper-layer storage application defines the API of the upper-layer storage application and provides services to users. In order to realize the functions of the upper-layer storage application, it is necessary to expose the API of the upper-layer storage application to the users of the upper-layer storage application, and at the same time, it is necessary to expose the API of the basic storage product to them.

[0046] For example, take the network disk and photo album service PDS as a typical upper storage application. The network disk and photo album service PDS is an open platform for enterprise and personal data management, content identification and collaboration provided to customers. Its bottom layer relies on the basic storage product OSS to save the user's file data, and the PDS side manages the metadata of the network disk. In order to realize the functions of the upper storage application, OSS API and PDS API are provided to users.

[0047] In this way, users will perceive both the basic storage product and the upper-level storage application as two storage products, and need to manage the domain names and single-domain certificates of the two storage products at the same time, which increases the user management cost. Since the underlying storage details of the storage application layer are exposed to users, it is not conducive to the integrity of the upper-level storage application and the future upgrade of the storage layout.

[0048] Figure 2 The framework diagram of the data upload process of the traditional upper storage application provided in this embodiment. Figure 2 As shown, the data upload process of the upper storage application is as follows:

[0049] 1) The user (through the end-side device used) sends a data upload request to the upper-layer storage application (storage gateway 2) by calling the API of the upper-layer storage application (for example, the API used by PDS to create files: CreateFile shown in the figure). The upper-layer storage application (through storage gateway 2) returns the target storage address of the data object to be uploaded to the user.

[0050] 2) The user (end-side device) accesses the basic storage product based on the API of the basic storage product (for example, the API for writing data objects to OSS: PutObject as shown in the figure) and stores the data object to be uploaded in the storage space corresponding to the target storage address.

[0051] 3) The user (end-side device) sends a message of data upload completion to the upper-layer storage application (storage gateway 2) by calling the API of the upper-layer storage application (for example, the API of the PDS to complete / end data upload shown in the figure: CompleteFile) to maintain the data consistency of the upper-layer storage application. The upper-layer storage application ends the data upload operation.

[0052] For example, taking the upper-layer storage application as the network disk and photo album service PDS built on OSS, when the user needs to upload a file, he will first call the CreateFile API of PDS to create a file, and CreateFile will return the OSS storage address of the file data to be uploaded. After the user obtains the OSS storage address of the file to be uploaded, he will access OSS (call the PutObject API of OSS) to store the file data to be uploaded on OSS. After the file data is uploaded, the user needs to call the CompleteFile API of PDS again to inform PDS that the file has been uploaded to maintain data consistency. PSD will close the data upload operation this time.

[0053] Figure 3 The framework diagram of the data download process of the traditional upper storage application provided in this embodiment. Figure 3 As shown, the data download process of the upper storage application is as follows:

[0054] 1) The user (end-side device) sends a data download request to the storage gateway 2 of the upper-layer storage application according to the API of the upper-layer storage application (for example, the API for obtaining the file download address of the PDS shown in the figure: GetDownloadUrl, which returns an OSS download link). The storage gateway 2 of the upper-layer storage application returns the storage address of the data object to be downloaded (such as the OSS download link) to the user.

[0055] 2) The user (end-side device) accesses the basic storage product based on the API of the basic storage product (for example, the OSS API for reading data objects: GetObject shown in the figure), and downloads the corresponding data object from the basic storage product according to the storage address of the data object to be downloaded.

[0056] For example, if the upper storage application is a network disk and photo album service PDS built on OSS, when a user needs to download a file, he will first call the GetDownloadUrl API of PDS to obtain the file download address, and the API will return an OSS download link. After obtaining the OSS download link, the user will access OSS and download the file data from OSS.

[0057] In summary, based on Figure 1 The architecture for implementing upper-layer storage applications shown in the figure is a triangle model of users (end-side devices), upper-layer storage applications (such as PDS), and the underlying storage products they rely on (such as OSS). The APIs of the upper-layer storage applications and the underlying storage products they rely on are exposed to users, which exposes the underlying storage details of the storage application layer to users, which is not conducive to the integrity of the upper-layer storage applications and future upgrades of the storage layout.

[0058] In addition, users will also be aware of the upper-layer storage application and the underlying storage product on which it depends. They need to manage the domain names and single-domain certificates of the two storage products at the same time, which increases the user management cost. It also makes the upper-layer storage application unable to provide the ability of static URL (Uniform Resource Locator). In the data upload process of the upper-layer storage application, users need to go through three stages (such as Figure 2 In the data download process, users need to go through two stages (as shown in Figure 3 The operation shown in the figure makes the data upload and download process complicated and inefficient.

[0059] In view of the above technical problems, the present application provides a data processing system. Figure 4 As shown, the data system includes a basic storage product and an upper-layer storage application built on the basic storage product. The basic storage product supports the upper-layer storage application to register its own API to the basic storage product, so that the basic storage product can proxy data requests to the upper-layer storage application.

[0060] Specifically, the basic storage product can receive data requests from end-side devices (users) to upper-layer storage applications, parse the request metadata and data stream (which may or may not be present) contained in the data request, and forward the request metadata in the data request to the upper-layer storage application. Among them, the request metadata of the data request refers to the information in the data request other than the data stream to be processed, including various parameters in the request, such as operation type, file length, data storage location, etc. The request metadata contained in different types of data requests may be different, and can be specifically designed and adjusted according to the application requirements of the upper-layer storage application, which is not specifically limited here. The data stream in the data request refers to the data that needs to be stored in the basic storage product.

[0061] After receiving the request meta information, the upper-layer storage application is responsible for processing the request meta information to obtain a first processing result, and returning the first processing result to the basic storage product. In actual applications, the upper-layer storage application processes different data requests differently, which is different from the Figure 1 The processing performed by the upper-layer storage application for corresponding data requests in the traditional architecture shown is the same and will not be repeated here.

[0062] The basic storage product receives a first processing result returned by an upper-layer storage application, generates a second processing result for the data request based on the first processing result of the upper-layer storage application on the request metadata, and returns the second processing result to the end-side device.

[0063] In an embodiment of the present application, the second processing result is the processing result that needs to be returned to the user who issued the data request, that is, the final processing result of the data request. For data requests for data operations on the metadata of the upper-layer storage application (not involving data changes on the basic storage product), the upper-layer storage application processes the data request to obtain a first processing result, which is the final processing result that needs to be returned to the user. Furthermore, the basic storage product uses the first processing result returned by the upper-layer storage application as the second processing result, and returns the second processing result to the end-side device. Among them, metadata refers to data defined by the uploaded storage application to describe the attributes, organizational structure, and relationships of the data stored by the basic storage product, which helps to better manage the data stored in the basic storage product, such as target data, folder data, etc. in the upper-layer storage application, and supports functions such as indicating storage location, historical data, resource search, file records, etc.

[0064] For requests for data upload or data download (both involving data changes on the basic storage product) from upper-layer storage applications, since upper-layer storage applications rely on basic storage products, data upload by upper-layer storage applications essentially requires uploading data to the basic storage product, and data download by upper-layer storage applications essentially requires downloading data from the basic storage product. The upper-layer storage application processes the request metadata for data upload or data download to obtain a first processing result, including the target storage address of the data uploaded to the basic storage product, or the actual storage address of the data to be downloaded on the basic storage product. Further, the basic storage product uploads data according to the target storage address of the data uploaded to the basic storage product, and generates a second processing result for the data upload request according to the result of the data upload; alternatively, the basic storage product downloads data according to the data to be downloaded, and generates a second processing result for the data download request according to the result of the data download. Further, the second processing result is returned to the end-side device.

[0065] It should be noted that the data format of the processing results of different data requests can be designed and adjusted according to the application requirements of the upper-layer storage application, and is not specifically limited here. For example, for a data download request to a PDS, the data download result obtained by the OSS for data download may not comply with the response specification of the PDS for the data download request. The data download result needs to be converted into a second processing result that complies with the response specification of the PDS for the data download request, and then returned to the end-side device. If the processing of the data request fails, the error information generated by the OSS also needs to be converted into an error information that complies with the corresponding specification of the PDS, and then returned to the end-side device.

[0066] like Figure 4The architecture of the upper-layer storage application shown in the figure expands the capabilities of the basic storage product, enabling the basic storage product to support other upper-layer storage application APIs, changing the traditional triangle mode to a single-point mode (or serial mode), with the basic storage product providing services to users in a unified manner. The execution process of the upper-layer storage application API has been changed. When a data request for an upper-layer storage application reaches the basic storage product, the basic storage product forwards the request metadata in the data request to the specific upper-layer storage application. The upper-layer storage application processes the request metadata. For example, it processes the metadata of the upper-layer storage application. If specific data needs to be uploaded or downloaded, the upper-layer storage application returns the real data storage address to the basic storage product. The basic storage product uploads or downloads data based on the real data storage address, and then returns the final result to the user.

[0067] Since the architecture of the upper-layer storage application has changed from the traditional triangle mode to the serial mode, the details of the upper-layer storage application implementation are hidden from the user, and the user no longer needs to access two different storage products, the basic storage product and the upper-layer storage application. When the upper-layer storage application changes the underlying storage details, such as changing the data layout, developing a deduplication function, etc., the user's API call can be compatible and unaffected. Data upload based on the triangle mode architecture requires three calls (such as Figure 2 As shown, data download requires two calls (such as Figure 3 This solution is based on Figure 4 For data upload and download of the serial model architecture shown, users only need to make one call, which simplifies the user data upload and download process.

[0068] Because users only need a single call to access a unique basic storage product, they only need a domain name and a single domain name certificate, which is easier to manage. Because the upper-level storage application supports a single request to complete data download, it can also have the ability to download data signed by static resource descriptors (such as static URLs, static URIs (Uniform Resource Identifiers), etc.).

[0069] In addition, the upper-layer storage applications and the basic storage products built on the basic storage products can be deployed in the same region. However, the user's end-side devices and the basic storage products can be in different regions. This solution only has one cross-region call (between the user and the basic storage product), and subsequent calls between the basic storage product and the upper-layer storage applications usually occur within the same region, thus reducing access latency.

[0070] In addition, one difficulty in ensuring the security of storage products is the anti-attack and traffic cleaning of the storage gateway, which is very complex to implement and consumes a lot of bandwidth. Therefore, the construction of the storage gateway is very challenging for upper-level storage applications. The solution of this application does not require the additional storage gateway of the upper-level storage application, but integrates its functions into the basic storage product, saving various costs for the construction of the storage gateway.

[0071] In the embodiment of the present application, the data request to the upper-layer storage application is proxied by the basic storage product, and there is no need to add an additional storage gateway for the upper-layer storage application. Only the basic storage product is exposed to the user, and the subsequent service implementation details are invisible to the user. The upgrade of the storage layout of the upper-layer storage application is imperceptible to the user, which is beneficial to the integrity of the upper-layer storage application and the future upgrade of the storage layout. Moreover, the user can complete data upload, download and other operations by sending a data request to the storage gateway of the basic storage product once. The user only needs to manage one domain name and a single domain name certificate, which not only reduces the user's management cost of the domain name, but also improves the efficiency of data operations.

[0072] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0073] Figure 5 This is a flowchart of a data processing method provided by an exemplary embodiment of the present application. The execution subject of this embodiment is Figure 4 The basic storage product in the architecture shown can be a storage gateway for the basic storage product. Figure 5 As shown, the specific steps of this method are as follows:

[0074] Step S501: A data request from a receiving device to an upper-layer storage application.

[0075] The end-side device refers to an electronic device used by a user that runs a client of an upper-layer storage application, which may specifically be various types of terminal devices and is not specifically limited here.

[0076] Data requests to upper-layer storage applications refer to requests for various data operations issued by users to upper-layer storage applications during the process of using the services provided by upper-layer storage applications, including but not limited to: data upload, data download, directory management, directory migration, network disk management, and folder management. Data requests include request meta information, and data upload requests also include data flows to be stored in the basic storage application, such as the target data to be uploaded.

[0077] In this embodiment, the API of the upper-layer storage application is registered on the basic storage product that the upper-layer storage application depends on, and the capabilities of the basic storage product are expanded so that the basic storage product can proxy the data requests of the upper-layer storage application and forward the request metadata of the data requests to the upper-layer storage application, without the need to build a set of storage gateways for the upper-layer storage application.

[0078] For example, taking the basic storage product as OSS and the upper-layer storage application as the network disk and photo album service PDS built on OSS, the capabilities of the OSS storage gateway are expanded by defining the API of the upper-layer storage application on the OSS storage gateway, so that the OSS storage gateway can proxy PDS requests and forward the requests to PDS.

[0079] Since the basic storage product can proxy the data requests of the upper-layer storage application, that is, the upper-layer storage application and the basic storage application share a storage gateway, the upper-layer storage application can support the capabilities of static resource descriptors (such as static URLs). In an optional embodiment, for static resources with a high access frequency (such as files, pictures, etc.), a static URL corresponding to at least one data resource can be provided to the user. The static URL points to the storage path of the corresponding data resource on the storage product (which can be an upper-layer storage application or a basic storage product). Users can use the static URL to quickly download data resources and improve the efficiency of data downloading.

[0080] Specifically, the user can send a data download request to the basic storage product through the end-side device according to the static URL. The data download request is used to download the second target data belonging to the upper-layer storage application. The second target data belongs to the upper-layer storage application, that is, the upper-layer storage application manages the second target data, but the second target data is actually stored on the basic storage product. The basic storage product receives the data download request sent by the end-side device according to the static URL, and parses the storage path of the data resource to be downloaded, obtains the data resource according to the storage path of the data resource, and returns the data resource to the end-side device.

[0081] In addition, the static URL can also include a digital signature to ensure data security. The basic storage product can verify the digital signature. The basic storage product has the ability to implement data access based on the static URL. The specific implementation principle is consistent with the implementation principle of the existing static URL and will not be repeated here.

[0082] Step S502: forward the request meta-information in the data request to the upper-layer storage application, and receive a first processing result of the upper-layer storage application on the request meta-information.

[0083] In this step, the basic storage product parses the received data request to the upper storage application, obtains the request meta information in the data request, and forwards the request meta information to the upper storage application, so that the upper storage application processes the request meta information to obtain a processing result. In this embodiment, the processing result of the upper storage application on the request meta information is called the first processing result.

[0084] In actual applications, one or more upper-layer storage applications can be built based on a basic storage product. The basic storage product can proxy the requests of these upper-layer storage applications at the same time. Optionally, the data request to the upper-layer storage application may contain information about the upper-layer storage application, such as a domain name, URL, and other information that can uniquely identify an upper-layer storage application. The basic storage product can obtain the information of the upper-layer storage application by parsing the data request, and determine the access address of the upper-layer storage application to be accessed based on the information of the upper-layer storage application; and forward the request meta-information in the data request to the upper-layer storage application based on the access address of the upper-layer storage application. Optionally, the data request to the upper-layer storage application may contain the access address of the upper-layer storage application to be accessed. The basic storage product can obtain the access address of the upper-layer storage application by parsing the data request, and forward the request meta-information of the data request to the upper-layer storage application based on the access address of the upper-layer storage application.

[0085] Optionally, if the information of the upper-layer storage application cannot be obtained, that is, if the data request of the corresponding upper-layer storage application cannot be identified, the basic storage product processes the data request as a data request for the basic storage product.

[0086] It should be noted that, in this embodiment, the request metadata processing flow of the upper storage application for various data requests remains unchanged, and can be specifically designed and adjusted according to the needs and implementation logic of the upper storage application, and is not specifically limited here.

[0087] Step S503: Determine a second processing result for the data request based on the first processing result of the upper-layer storage application on the request meta-information, and return the second processing result to the terminal device.

[0088] In this embodiment, the processing result of the request meta information by the upper storage application is referred to as the first processing result. For data requests of different data operation types, the upper storage application processes the corresponding data request based on the request meta information of the data request to obtain the first processing result. For data requests of different data operation types, the processing performed by the upper storage application and the first processing result obtained are different.

[0089] Exemplarily, a data upload request includes the first target data to be uploaded and request meta information (recorded as the first request meta information). The upper-layer storage application processes the first request meta information of the data upload request, that is, processes the data upload request based on the first request meta information, and can obtain the target storage address of the data uploaded to the basic storage product. The first processing result may include the target storage address of the data to be uploaded on the basic storage product. The upper-layer storage application returns the first processing result (including the target storage address) to the basic storage product.

[0090] Furthermore, the basic storage product receives the first processing result returned by the upper-layer storage application, and stores the data to be uploaded in the storage space corresponding to the target storage address on the basic storage product, thereby completing the data upload and obtaining the data upload result, and generating a response result of the data upload request that meets the requirements of the upper-layer storage application according to the data upload result as the second processing result. The basic storage product returns the second processing result (including the data upload result) to the end-side device.

[0091] Exemplarily, for a data download request, the data download address of the data to be downloaded on the basic storage product is included, that is, the second request meta information. The upper-layer storage application processes the second request meta information of the data download request and can obtain the data download address of the data to be downloaded on the basic storage product. The first processing result includes the data download address of the data to be downloaded on the basic storage product. The upper-layer storage application returns the first processing result (including the data download address) to the basic storage product.

[0092] Furthermore, the basic storage product receives the first processing result returned by the upper storage application, downloads data from the basic storage product according to the data download address, obtains the data download result, and generates a response result of the data download request that meets the requirements of the upper storage application according to the data download result as the second processing result. The basic storage product returns the second processing result (including the data obtained by the data download) to the end-side device.

[0093] Exemplarily, for processing requests for metadata of upper-layer storage applications, such as directory migration, folder management, etc., such processing requests only contain request metadata (recorded as third request metadata), and do not contain data streams. The upper-layer storage application processes the third request metadata (i.e., the metadata processing request) to obtain the processing result of the metadata. For example, target migration success / failure, etc. The first processing result includes the processing result of the metadata. In this case, there is no need to access data to the basic storage product, and the first processing result is the final processing result of the request, that is, the processing result returned to the user who issued the request. The basic storage product uses the first processing result returned by the upper-layer storage application (i.e., the processing result of the metadata) as the second processing result, and returns the second processing result to the end-side device.

[0094] The solution of this embodiment receives data requests for upper-layer storage applications through a basic storage product, forwards request meta-information in the data request to the upper-layer storage application, receives a first processing result of the upper-layer storage application on the request meta-information, and determines a second processing result of the data request based on the first processing result of the upper-layer storage application on the request meta-information, and returns the second processing result to the terminal device. By using the basic storage product to proxy data requests for upper-layer storage applications, there is no need to add an additional storage gateway for the upper-layer storage application. Only the basic storage product is exposed to the user, and the service implementation details after the basic storage product are invisible to the user. The upgrade of the storage layout of the upper-layer storage application is imperceptible to the user, which is beneficial to the integrity of the upper-layer storage application and the future upgrade of the storage layout. In addition, the user can complete data upload, download and other operations by sending a data request to the basic storage product once. The user only needs to manage one domain name and a single domain name certificate, which not only reduces the user's management cost of the domain name, but also improves the efficiency of data operations.

[0095] Figure 6 This is a flow chart of a method for uploading data provided by an example embodiment of the present application. In this embodiment, the basic storage product is used to proxy the request of the upper storage application to achieve data uploading. Figure 6 As shown, the specific steps of this method are as follows:

[0096] Step S601: A data upload request from a receiving end device to an upper storage application, where the data upload request includes first request meta-information and first target data to be uploaded.

[0097] The first request meta information includes data carried in the data upload request except the first target data to be uploaded. The basic storage product forwards the first request meta information to the upper-layer storage application.

[0098] For example, the first request metadata in the data upload request to PDS may include the upload location and data length of the first target data (such as a file) in the PDS network disk. The PDS may convert the upload location in the PDS network disk into the actual storage location in the basic storage product, that is, the target storage address of the first target data on the basic storage product.

[0099] The implementation principle of this step refers to the relevant content of the aforementioned step S501, and is not specifically limited here.

[0100] Step S602: forward the first request meta-information in the data upload request to the upper-layer storage application.

[0101] In this step, the basic storage product parses the data upload request to obtain first request meta information and first target data to be uploaded.

[0102] For a data upload request, after receiving the first request meta information of the data upload request, the upper-layer storage application processes the first request meta information to obtain the target storage address of the first target data to be uploaded on the basic storage product. The first processing result may include the target storage address of the first target data on the basic storage product. The upper-layer storage application returns the first processing result to the basic storage product.

[0103] Step S603: Receive a first processing result of the upper-layer storage application on the first request meta-information, where the first processing result includes a target storage address of the first target data on the basic storage product.

[0104] Step S604: According to the target storage address of the first target data on the basic storage product, the first target data is written into the storage space corresponding to the target storage address to obtain a data upload result.

[0105] In this step, the basic storage product writes the first target data into the storage space corresponding to the target storage address on the basic storage product, thereby completing the uploading of the first target data and obtaining the data uploading result, including whether the data uploading is successful.

[0106] Step S605: Generate a second processing result according to the data upload result, and return the second processing result to the terminal side device.

[0107] In this step, the basic storage product generates a response result of the data upload request that meets the requirements of the upper-layer storage application according to the data upload result as the second processing result. The basic storage product returns the second processing result (including the data upload result) to the terminal device.

[0108] Exemplarily, the data format of the response result of the data upload request can be configured on the basic storage product. The basic storage product can encapsulate the first processing result according to the data format of the response result of the data upload request to obtain a second processing result that meets the requirements of the upper-layer storage application. Among them, the data format of the response result of the data upload request can be specifically configured and adjusted according to the needs of the data download function of the upper-layer storage application, and is not specifically limited here.

[0109] Figure 7 This is an interactive flow chart of the data uploading method provided in the embodiment of the present application. Figure 7 As shown in the figure, the interactive process of data upload is as follows:

[0110] Step S701: A basic storage product receives a data upload request from a terminal device to an upper-layer storage application. The data upload request includes first request metadata and first target data to be uploaded.

[0111] Step S702: The basic storage product forwards the first request metadata to an upper-layer storage application.

[0112] Step S703: The upper-layer storage application processes the first request meta-information to obtain a first processing result, where the first processing result includes a target storage address of the first target data to be uploaded on the basic storage product.

[0113] Step S704: The upper-layer storage application returns the first processing result to the basic storage product.

[0114] Step S705: The basic storage product writes the first target data into the storage space corresponding to the target storage address, obtains a data upload result, and generates a second processing result for the data upload request according to the data upload result.

[0115] Step S706: The basic storage product returns the second processing result to the end-side device.

[0116] It should be noted that the implementation principles of each step in this embodiment refer to the aforementioned Figure 6 The relevant contents of the corresponding embodiments will not be repeated here.

[0117] For example, Figure 8 The data upload process framework diagram provided in this embodiment. Take the basic storage product as OSS, and the upper storage application as the network disk and photo album service PDS built on OSS as an example. Figure 8 As shown, based on Figure 4 The data upload process of the architecture shown is as follows:

[0118] 1. The user (through the end-side device used) sends a data upload request to the OSS by calling the API of the upper-layer storage application (for example, the API used by PDS to upload files: PutFile).

[0119] 2. OSS forwards the first request metadata in the data upload request to the upper-layer storage application.

[0120] 3. The upper-layer storage application returns the first processing result to the OSS, including the target storage address of the first target data to be uploaded.

[0121] 4. OSS calls the OSS subsystem (such as the OSS API for uploading data objects: PutObject) to write the first target data into the physical space corresponding to the target storage address on OSS.

[0122] In addition, after completing the data upload, OSS can also return a response result to the data upload request containing the data upload result to the user.

[0123] In this embodiment, a data upload request to an upper-layer storage application is received through a basic storage product, the first request meta-information in the data upload request is forwarded to the upper-layer storage application, and the first processing result of the upper-layer storage application on the first request meta-information is received, including the target storage address of the first target data to be uploaded on the basic storage product; according to the first processing result, the first target data is written into the storage space corresponding to the target storage address to obtain the data upload result; and according to the data upload result, a second processing result of the data upload request (i.e., a response result to the data upload request) is generated. By using the basic storage product to proxy the data upload request to the upper-layer storage application, only one domain name and a storage gateway of the basic storage product are exposed to the user, and the service implementation details after the storage gateway are invisible to the user. Therefore, in terms of user experience, the data upload operation can be completed by sending a data request to the basic storage product once, and the user only needs to manage one domain name and a single domain name certificate, which not only reduces the user's management cost of the domain name, simplifies user operations, but also improves data upload efficiency.

[0124] Fig. 9 A flowchart of a method for downloading data provided by an exemplary embodiment of the present application. Fig. 9 As shown, the specific steps of this method are as follows:

[0125] Step S901: A data download request from a receiving end device to an upper-layer storage application, where the data download request includes second request meta-information.

[0126] The second request meta information includes data carried in the data download request. The basic storage product forwards the second request meta information to the upper-layer storage application.

[0127] The implementation principle of this step refers to the relevant content of the aforementioned step S501, and is not specifically limited here.

[0128] Step S902: forward the second request meta-information in the data download request to the upper-layer storage application.

[0129] Step S903: Receive a first processing result of the upper-layer storage application on the second request meta-information, where the first processing result includes a data download address of the second target data to be downloaded on the basic storage product.

[0130] For a data download request, the upper-layer storage application processes the second request meta-information in the data download request, that is, processes the data download request, and can obtain a first processing result, which includes the data download address of the second target data to be downloaded on the basic storage product. The upper-layer storage application returns the first processing result to the basic storage product. Among them, the upper-layer storage application determines the actual storage address of the second target data to be downloaded on the basic storage product based on the second request meta-information and the metadata stored by the upper-layer storage application, and can obtain the data download address of the second target data on the basic storage product. The specific implementation method of the upper-layer storage application processing the data download request can be defined and configured in the upper-layer storage application, and is not specifically limited here.

[0131] In this step, the basic storage product receives a first processing result of the second request meta-information returned by the upper-layer storage application.

[0132] Step S904: Obtain second target data according to the data download address in the first processing result.

[0133] In this step, the basic storage product downloads data from the basic storage product according to the data download address in the first processing result, generates second target data according to the data download result, and generates a second processing result for the data download request according to the second target data.

[0134] In an example scenario, the basic storage product may use the data download result as the second target data. In a subsequent step, the basic storage product generates a second processing result for the data download request according to the data download result.

[0135] In another example scenario, the data structure of the second target data requested by the user and the data actually stored in the basic storage product may be different and not necessarily one-to-one corresponding. For example, a file in a PDS is actually stored as one or more OSS objects in the basic storage product.

[0136] The first processing result of the upper-layer storage application on the second request meta-information in the data download request includes, in addition to the data download address (i.e., the actual storage address) of the second target data on the basic storage product, the conversion rules between the second target data and the actual storage data of the basic storage product. After the basic storage product obtains the downloaded data based on the data download address, it converts the downloaded data into the second target data according to the conversion rules. The upper-layer storage application has flexible data layout capabilities and can adjust the data format according to the data conversion rules.

[0137] For example, a user requests to download a file from PDS, which is actually stored as one or more OSS objects in the basic storage product. PDS returns the actual storage address of these OSS objects (i.e., data download link) and the conversion rules between OSS and files to OSS. OSS reads the OSS object according to the actual storage address and converts the OSS object into a file to obtain the file that the user wants to download.

[0138] Step S905: Generate a second processing result of the data download request according to the second target data, and return the second processing result to the terminal device.

[0139] In this step, the basic storage product generates a response result of the data download request that meets the requirements of the upper storage application according to the second target data as the second processing result. The basic storage product returns the second processing result (including the second target data) to the terminal device.

[0140] Exemplarily, the data format of the response result of the data download request can be configured on the basic storage product. The basic storage product can encapsulate the second target data according to the data format of the response result of the data download request to obtain a second processing result that meets the requirements of the upper-layer storage application. The data format of the response result of the data download request can be specifically configured and adjusted according to the needs of the data download function of the upper-layer storage application, and is not specifically limited here.

[0141] Fig.10 This is an interactive flow chart of the data download method provided in the embodiment of the present application. Fig.10 As shown in the figure, the interactive process of data download is as follows:

[0142] Step S1001: A basic storage product receives a data download request from a terminal device to an upper-layer storage application, where the data download request includes second request meta-information.

[0143] Step S1002: The basic storage product forwards the second request metadata to an upper-layer storage application.

[0144] Step S1003: The upper-layer storage application processes the second request meta-information to obtain a first processing result, where the first processing result includes a data download address and a data conversion rule of the second target data to be downloaded on the basic storage product.

[0145] Step S1004: The upper-layer storage application returns the first processing result to the basic storage product.

[0146] Step S1005: The basic storage product downloads data according to the data download address, converts the downloaded data into second target data according to the data conversion rule, and generates a second processing result according to the second target data.

[0147] Step S1006: The basic storage product returns the second processing result to the end-side device.

[0148] It should be noted that the implementation principles of each step in this embodiment refer to the aforementioned Fig. 9 The relevant contents of the corresponding embodiments will not be repeated here.

[0149] For example, Fig.11 The data download process framework diagram provided in this embodiment. Take the basic storage product as OSS, and the upper storage application as the network disk and photo album service PDS built on OSS as an example. Fig.11 As shown, based on Figure 4 The data download process for the architecture shown is as follows:

[0150] 1. The user (through the end-side device used) sends a data download request to the OSS by calling the API of the upper-layer storage application (for example, the API used by PDS to download files: GetFile).

[0151] 2. The OSS forwards the second request metadata in the data download request to the upper-layer storage application.

[0152] 3. The upper-layer storage application returns the data download address and data conversion rules of the second target data to be downloaded to the OSS.

[0153] 4. OSS calls the OSS subsystem (such as the OSS API for downloading data objects: GetObject), downloads data from OSS according to the data download address, and converts the downloaded data into the second target data.

[0154] In addition, after the data download is completed, the OSS may also return a response result to the data download request including the second target data to the user.

[0155] In this embodiment, a data download request for an upper-layer storage application is received through a basic storage product, the second request meta-information in the data download request is forwarded to the upper-layer storage application, and the first processing result of the upper-layer storage application on the second request meta-information is received, including the data download address and data conversion rules of the second target data to be downloaded. Data is downloaded from the basic storage product and the downloaded data is converted into the second target data to obtain a data download result. By using a basic storage product to proxy the data download request for the upper-layer storage application, only one domain name and one basic storage product are exposed to the user, and the service implementation details after the basic storage product are invisible to the user. Therefore, in terms of user experience, the data download operation can be completed by sending a data request to the basic storage product once, and the user only needs to manage one domain name and a single domain name certificate, which not only reduces the user's management cost of the domain name, simplifies user operations, but also improves the efficiency of data download.

[0156] Fig.12 A flowchart of a data processing method provided for another exemplary embodiment of the present application. In this embodiment, the basic storage product may be OSS, and the upper storage application is a network disk and photo album service PDS built on OSS as an example. Fig.12 As shown, the data processing flow is as follows:

[0157] Step S1201: The receiving device sends a data request to the network disk and photo album service, where the data request includes request meta information.

[0158] Among them, data requests for the network disk and photo album service PDS include but are not limited to data upload, data download, directory management, directory migration, network disk management, and folder management.

[0159] In the network disk and album service PDS, users can perform data operations such as image upload, image download, network disk target management, album folder management, etc., which can be designed and adjusted according to the actual application requirements of PDS, and are not specifically limited here. For different data operations, PDS can define corresponding APIs. The API provided by PDS can be defined and described on OSS, so that OSS can proxy PDS requests.

[0160] The implementation principle of this step refers to the relevant content of the aforementioned step S501, which will not be repeated here.

[0161] Step S1202: forward the request meta-information to the network disk and photo album service, and receive the first processing result of the network disk and photo album service on the request meta-information.

[0162] The implementation principle of this step refers to the relevant content of the aforementioned step S502, which will not be repeated here.

[0163] Step S1203: Determine a second processing result for the data request based on the first processing result of the network disk and album service on the request metadata, and return the second processing result to the terminal device.

[0164] The implementation principle of this step refers to the relevant content of the aforementioned step S503, which will not be repeated here.

[0165] In an example scenario, the data request is a data upload request. The OSS forwards the first request meta-information in the data upload request to the PDS, and receives a first processing result of the PDS on the first request meta-information, the first processing result including a target storage address of the first target data to be uploaded on the OSS.

[0166] Further, the OSS writes the first target data into the storage space corresponding to the target storage address of the first target data on the OSS in the first processing result to obtain the data upload result. The OSS generates a second processing result for the data upload request based on the data upload result, and returns the second processing result to the end-side device.

[0167] In an example scenario, the data request is a data download request. The OSS forwards the second request meta-information in the data download request to the PDS, and receives a first processing result of the PDS on the second request meta-information, the first processing result including a data download address and a data conversion rule.

[0168] Furthermore, the OSS downloads data from the storage space corresponding to the data download address on the OSS according to the data download address in the first processing result, and converts the downloaded data into second target data according to the data conversion rule. The OSS generates a second processing result of the data download request according to the second target data, and returns the second processing result to the end-side device.

[0169] In an example scenario, for processing requests for metadata of PDS, such as directory migration, folder management, etc., PDS processes the metadata processing request (i.e., request metadata) and can obtain the processing result of the metadata. For example, target migration success / failure, etc. The first processing result includes the processing result of the metadata. In this case, there is no need to access data to OSS, and the first processing result is the final processing result of the request, that is, the processing result returned to the user who issued the request. OSS uses the first processing result returned by PDS (i.e., the processing result of the metadata) as the second processing result, and returns the second processing result to the end-side device.

[0170] The solution of this embodiment receives a data request for PDS through OSS, forwards the request meta information in the data request to PDS, receives a first processing result of the request meta information by PDS, and determines a second processing result of the data request based on the first processing result of the request meta information by PDS, and returns the second processing result to the end-side device. By using OSS to proxy data requests for PDS, there is no need to add an additional storage gateway for PDS. Only the storage gateway of OSS is exposed to users, and the service implementation details after the storage gateway are invisible to users. Upgrading the storage layout of PDS is imperceptible to users, which is beneficial to the integrity of PDS and future storage layout upgrades; and users can complete data upload, download and other operations by sending a data request to OSS once. Users only need to manage one domain name and a single domain name certificate, which not only reduces the user's management cost of the domain name, but also improves the efficiency of data operations.

[0171] Fig.13 A schematic diagram of the structure of a server provided in an embodiment of the present application. Fig.13 As shown, the server includes: a memory 1301 and a processor 1302. The memory 1301 is used to store computer-executable instructions and can be configured to store various other data to support operations on the server. The processor 1302 is connected to the memory 1301 in communication and is used to execute the computer-executable instructions stored in the memory 1301 to implement the technical solution provided by any of the above method embodiments. The specific functions and technical effects that can be achieved are similar and will not be repeated here.

[0172] Optional, such as Fig.13 As shown, the server also includes: a firewall 1303, a load balancer 1304, a communication component 1305, a power supply component 1306 and other components. Fig.13 Only some components are shown schematically, which does not mean that the server only includes Fig.13 Components shown. Fig.13 In the description, the server is only taken as a cloud server deployed in the cloud as an example for exemplary description. The server can also be deployed locally, and this embodiment is not specifically limited here.

[0173] An embodiment of the present application also provides a computer-readable storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, the method of any of the aforementioned embodiments is implemented. The specific functions and technical effects that can be achieved are not repeated here.

[0174] The embodiment of the present application also provides a computer program product, including a computer program, which implements the method of any of the above embodiments when executed by a processor. The computer program is stored in a readable storage medium, and at least one processor of the server of the basic storage product can read the computer program from the readable storage medium. At least one processor executes the computer program so that the server executes the technical solution provided by any of the above method embodiments. The specific functions and technical effects that can be achieved are not repeated here.

[0175] The embodiment of the present application provides a chip, including: a processing module and a communication interface, the processing module can execute the technical solution of the basic storage product in the aforementioned method embodiment. Optionally, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the technical solution provided by any of the aforementioned method embodiments.

[0176] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0177] It should be understood that the above processor can be a processing unit (Central Processing Unit, referred to as CPU), a graphics processing unit (graphics processing unit, referred to as GPU), or other general-purpose processors, digital signal processors (Digital Signal Processor, referred to as DSP), application-specific integrated circuits (Application Specific Integrated Circuit, referred to as ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the application can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in at least one processor.

[0178] The memory may include high-speed random access memory (RAM), and may also include non-volatile storage, such as at least one disk storage, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk.

[0179] The above storage may be an object storage service (OSS).

[0180] The above-mentioned memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0181] The above-mentioned communication component is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as a mobile hotspot (WiFi), a second-generation mobile communication system (2G), a third-generation mobile communication system (3G), a fourth-generation mobile communication system (4G) / Long Term Evolution (LTE), a fifth-generation mobile communication system (5G) and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared technology, ultra-wide band (UWB) technology, Bluetooth technology and other technologies.

[0182] The power supply assembly provides power to various components of the device where the power supply assembly is located. The power supply assembly may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply assembly is located.

[0183] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0184] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in a dedicated integrated circuit. Of course, the processor and the storage medium can also exist as discrete components in an electronic device or a main control device.

[0185] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0186] The order of the above-mentioned embodiments of the present application is only for description and does not represent the advantages and disadvantages of the embodiments. In addition, in some of the processes described in the above-mentioned embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed or executed in parallel in the order in which they appear in this article, and are only used to distinguish between different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or less operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit "first" and "second" to different types. The meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.

[0187] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods of each embodiment of the present application.

[0188] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not disclosed in the present application.

[0189] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A data processing method, characterized in that: Applied to basic storage products, the method includes: A data request from a receiving end-side device to an upper-layer storage application, wherein the data request includes request meta-information; Forwarding the request meta information to the upper-layer storage application, and receiving a first processing result of the request meta information by the upper-layer storage application; According to the first processing result of the request meta-information by the upper-layer storage application, a second processing result of the data request is determined, and the second processing result is returned to the end-side device.

2. The method according to claim 1, characterized in that The data request is a data upload request, the data upload request includes first request meta information and first target data to be uploaded, and forwarding the request meta information to the upper-layer storage application, and receiving a first processing result of the upper-layer storage application on the request meta information, includes: The first request meta-information is forwarded to the upper-layer storage application, and a first processing result of the upper-layer storage application on the first request meta-information is received, where the first processing result includes a target storage address of the first target data on the basic storage product.

3. The method according to claim 2, characterized in that The determining, according to the first processing result of the upper-layer storage application on the request meta-information, a second processing result on the data request includes: According to the target storage address of the first target data on the basic storage product, writing the first target data into the storage space corresponding to the target storage address to obtain a data upload result; A second processing result of the data request is generated according to the data upload result.

4. The method according to claim 1, characterized in that: The data request is a data download request, the data download request includes second request meta information, and forwarding the request meta information to the upper-layer storage application and receiving a first processing result of the upper-layer storage application on the request meta information includes: The second request meta-information is forwarded to the upper-layer storage application, and a first processing result of the upper-layer storage application on the second request meta-information is received, wherein the first processing result includes a data download address of the second target data to be downloaded on the basic storage product.

5. The method according to claim 4, characterized in that The determining, according to the first processing result of the upper-layer storage application on the request meta-information, a second processing result on the data request includes: Acquire the second target data according to the data download address in the first processing result; A second processing result of the data download request is generated according to the second target data.

6. The method according to claim 1, characterized in that The data request is a request for processing metadata of the upper storage application, the processing request includes third request meta information, and forwarding the request meta information to the upper storage application and receiving a first processing result of the upper storage application on the request meta information includes: The third request meta-information is forwarded to the upper-layer storage application, and a first processing result of the upper-layer storage application processing the third request meta-information is received, where the first processing result includes a processing result of the metadata.

7. The method according to claim 6, characterized in that The determining, according to the first processing result of the upper-layer storage application on the request meta-information, a second processing result on the data request includes: The first processing result is used as the second processing result.

8. The method according to any one of claims 1 to 7, characterized in that The forwarding the request meta information to the upper storage application includes: Determining an access address of the upper storage application according to the data request; The request meta information is forwarded to the upper-layer storage application according to the access address of the upper-layer storage application.

9. The method according to any one of claims 1 to 7, characterized in that: Also includes: Providing a static resource descriptor corresponding to at least one data resource to the terminal device; A data download request is received from the terminal device according to the static resource descriptor, where the data download request is used to download second target data belonging to the upper-layer storage application.

10. A data processing method, characterized in that: Applied to an object storage service, the method includes: A data request from a receiving device to a network disk and photo album service, wherein the data request includes request meta information; Forwarding the request meta information to the network disk and photo album service, and receiving a first processing result of the request meta information by the network disk and photo album service; According to the first processing result of the network disk and album service on the request meta-information, a second processing result of the data request is determined, and the second processing result is returned to the terminal device.

11. The method according to claim 10, characterized in that The data request is a data upload request, the data upload request includes first request meta information and first target data to be uploaded, and forwarding the request meta information to the network disk and album service, and receiving a first processing result of the request meta information by the network disk and album service, includes: Forwarding the first request meta information to the network disk and photo album service, and receiving a first processing result of the network disk and photo album service on the first request meta information, wherein the first processing result includes a target storage address of the first target data on the object storage service; The determining, according to the first processing result of the request meta information by the network disk and album service, a second processing result of the data request includes: According to the target storage address of the first target data on the object storage service, writing the first target data into the storage space corresponding to the target storage address to obtain a data upload result; A second processing result of the data upload request is generated according to the data upload result.

12. The method according to claim 11, characterized in that The data request is a data download request, the data download request includes second request meta information, and forwarding the request meta information to the network disk and album service, and receiving a first processing result of the network disk and album service on the request meta information includes: Forwarding the second request meta-information to the network disk and photo album service, and receiving a first processing result of the network disk and photo album service on the second request meta-information, wherein the first processing result includes a data download address of the second target data to be downloaded on the basic storage product; The determining, according to the first processing result of the request meta information by the network disk and album service, a second processing result of the data request includes: Reading the second target data from the corresponding storage space according to the data download address of the second target data on the basic storage product; A second processing result of the data download request is generated according to the second target data.

13. A server, characterized in that: include: at least one processor; as well as a memory communicatively coupled to the at least one processor; The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the server to execute the method described in any one of claims 1-12.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the processor executes the computer-executable instructions, the method according to any one of claims 1 to 12 is implemented.

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

16. A data processing system, characterized in that: include: Basic storage products and upper-layer storage applications built on the basic storage products; The basic storage product is used to: receive a data request from a terminal device to the upper storage application, and forward request meta information in the data request to the upper storage application; The upper storage application is used to: in response to receiving the request meta information, process the request meta information to obtain a first processing result, and return the first processing result to the basic storage product; The basic storage product is also used to: determine a second processing result for the data request based on the first processing result returned by the upper-layer storage application, and return the second processing result to the end-side device.

Images