Object data access method, device, system, equipment, medium and product

Abstract

The invention relates to an object data access method, device and system, equipment, a medium and a product. The object data access method provided by the invention comprises the following steps: receiving an initial request sent by a client; under the condition that the initial request meets a preset segmentation condition, performing segmentation processing on the initial request to obtain a segmentation request; and according to the segmentation request, requesting data from an object storage pool, receiving first target object data returned by the object storage pool based on the segmentation request, and sending the first target object data to the client. By adopting the method, the object data access efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to an object data access method, device, system, equipment, medium and product. Background Art

[0002] In an object storage system, when a client requests a large-scale object data from an object storage pool, directly sending the entire request to the object storage pool may cause pressure on network bandwidth and storage resources. When the client reads the object data, due to client implementation or network anomalies, the originally expected length of the content is not sent and the connection is disconnected prematurely. However, because the object storage gateway has a cache and pre-reads a large amount of data, the data is cached on the object storage gateway, which not only occupies system resources but also affects the overall performance of the object storage system.

[0003] In the related technology, all requests are sharded in the object storage gateway, which can save excessive resource consumption caused by requesting complete data; however, the request sharding function commonly used in the industry is uniformly enabled, and a large number of normal requests also execute sharding requests, which will cause a significant increase in the number of requests and load on the backend, resulting in low efficiency in object data access. Summary of the invention

[0004] Based on this, it is necessary to provide an object data access method, device, system, equipment, medium and product that can improve the efficiency of object data access in response to the above technical problems.

[0005] In a first aspect, the present application provides an object data access method, the method comprising:

[0006] Receive the initial request sent by the client;

[0007] When the initial request meets the preset segmentation condition, the initial request is segmented to obtain a segmented request;

[0008] According to the segment request, data is requested from the object storage pool, and first target object data returned by the object storage pool based on the segment request is received, and the first target object data is sent to the client.

[0009] In one embodiment, when the initial request meets the preset segmentation condition, segmenting the initial request to obtain the segmented request includes:

[0010] Analyze and process the initial request to obtain segment information, including request header time consumption, client version, and network bandwidth jitter;

[0011] Based on the segmentation conditions, the segmentation information is matched to obtain a matching result;

[0012] When the matching result is successful, the initial request is segmented to obtain segmented requests.

[0013] In one embodiment, based on the segmentation condition, the segmentation information is matched to obtain a matching result, including:

[0014] For each segment information, a segment condition corresponding to the segment information is used for comparison processing to obtain a sub-matching result corresponding to the segment information;

[0015] The matching result is determined according to the number of sub-matching results that are successfully matched.

[0016] In one embodiment, the initial request is analyzed and processed to obtain segment information, including:

[0017] Perform permission authentication on the initial request and obtain the permission authentication result;

[0018] When the authorization authentication result is that the authentication is passed, the initial request is subjected to protocol parsing to obtain segment information.

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

[0020] When the initial request does not meet the segmentation condition, data is requested from the object storage pool according to the initial request, and second target object data returned by the object storage pool based on the initial request is received, and the second target object data is sent to the client.

[0021] In a second aspect, the present application further provides an object data access device, comprising:

[0022] A request receiving module, used for receiving an initial request sent by a client;

[0023] A segment processing module, used for segment processing the initial request to obtain a segment request when the initial request meets the preset segment conditions;

[0024] The data request module is used to request data from the object storage pool according to the segment request, receive the first target object data returned by the object storage pool based on the segment request, and send the first target object data to the client.

[0025] In a third aspect, the present application further provides an object storage system, the system comprising:

[0026] Client side;

[0027] Object storage pools; and

[0028] An object storage gateway is used to execute the method of the first aspect.

[0029] In a fourth aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the method of the first aspect when executing the computer program.

[0030] In a fifth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the method of the first aspect when the computer program is executed by a processor.

[0031] In a sixth aspect, the present application further provides a computer program product, comprising a computer program, which implements the method of the first aspect when executed by a processor.

[0032] The object data access method, apparatus, system, device, medium and product provided above, in one aspect, provides an object data access method by receiving an initial request sent by a client; in the case where the initial request meets the preset segmentation conditions, the initial request is segmented to obtain a segmented request; according to the segmented request, data is requested from the object storage pool, and the first target object data returned by the object storage pool based on the segmented request is received, and the first target object data is sent to the client. In this way, in the case where the object storage gateway receives an initial request with a large amount of data sent by the client, the initial request is segmented, which can effectively reduce the bandwidth occupied by a single request, avoid a single request occupying too much network bandwidth, reduce the time required for each request, reduce the probability of timeouts, and improve the overall performance and stability of the network, thereby improving the efficiency of the object data access method. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0034] FIG1 is an application environment diagram of an object data access method in one embodiment;

[0035] FIG2 is a schematic diagram of a flow chart of an object data access method in one embodiment;

[0036] FIG3 is a schematic diagram of a flow chart of an object data access method in another embodiment;

[0037] FIG4 is a block diagram of an object data access device in one embodiment;

[0038] FIG5 is a block diagram of an object storage system in one embodiment;

[0039] FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0040] 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.

[0041] The object data access method provided in the embodiment of the present application can be applied to the object storage system shown in FIG. 1. The object storage system includes a client 102, an object storage gateway 104, and an object storage pool 106. Among them, the client 102 communicates with the object storage pool 106 through the object storage gateway 104. The object storage pool 106 refers to a physical or logical storage collection for storing object data, which is composed of multiple storage nodes, such as solid-state hard disks, etc., and can provide elastic, scalable and highly reliable storage services; the client may use a traditional file system protocol, such as NFS (Network File System) protocol or SMB (Server Message Block) protocol, and the object storage pool 106 usually provides services through the object storage protocol. The object storage gateway 104 is responsible for converting the traditional protocol to the object storage protocol, so that the application can seamlessly access the storage. The client 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc.

[0042] In an exemplary embodiment, as shown in FIG2 , a method for accessing object data is provided, which is described by taking the method applied to the object storage gateway 104 in FIG1 as an example, and includes the following steps 202 to 206. Among them:

[0043] Step 202: Receive an initial request sent by the client.

[0044] The initial request may include a request for accessing a single or multiple object data in the object storage pool.

[0045] Step 204: When the initial request meets the preset segmentation condition, segment the initial request to obtain a segmented request.

[0046] In a possible implementation, step 204 may further include: analyzing and processing the initial request to obtain segmentation information, the segmentation information including: request header time consumption, client version and network bandwidth jitter; matching the segmentation information based on the segmentation condition to obtain a matching result; when the matching result is a successful match, segmenting the initial request to obtain a segmented request.

[0047] The preset segmentation condition may be an interval judgment condition based on quantitative data such as client version identification, request header time consumption, network delay jitter, etc. Matching processing refers to comparing the segmentation information corresponding to the initial request with the interval in the segmentation condition. If the segmentation information falls within the interval range, the matching result is a successful match; if the segmentation information does not fall within the interval range, the matching result is a failed match.

[0048] For client version identifiers, clients with older version identifiers may not have optimized segmentation support or lower bandwidth utilization, so segmentation may need to be enabled to ensure efficient data transmission; clients with newer version identifiers usually support more efficient data transmission methods, parallel processing, and better error recovery mechanisms, so for these clients, whether segmentation is required can be determined based on network conditions, the nature of the request, etc. The segmentation condition corresponding to the client version identifier can be higher than the pre-set conditional version identifier. If the client version identifier corresponding to the initial request is lower than the conditional version identifier, the initial request needs to be segmented; if the client version identifier corresponding to the initial request is higher than the conditional version identifier, the initial request does not need to be segmented and can be sent directly to the object storage pool.

[0049] The request header time consumption can reflect the time required from the client sending the request header to the object storage gateway receiving the response. At this time, the initial request is segmented to prevent a single request from slowing down the overall response speed of the system during transmission. If the request header time consumption is long, it means that there may be reasons such as high network latency and heavy storage pool load, which may easily lead to timeout. If the request header time consumption is short, it indicates that the network status and the status of the object storage pool are good. At this time, the initial request does not need to be segmented and can be directly sent to the object storage pool. The segmentation condition corresponding to the request header time consumption can be: if the request header time consumption exceeds the preset time threshold, such as 2 seconds, the initial request needs to be segmented; if the request header time consumption is less than or equal to the time threshold, the initial request does not need to be segmented. The setting of the time threshold needs to be adjusted according to the actual situation to ensure a reasonable response time.

[0050] For network delay jitter, if the network delay is high, for example, more than 300ms, or there is a large delay fluctuation, the initial request may be processed inefficiently or even timed out. In this case, segmenting the initial request can disperse the pressure of data transmission and reduce the risk of single transmission, thereby improving the success rate and overall throughput, and improving the stability and reliability of data transmission; if the network delay is low and stable, for example, the delay is below 100ms and the fluctuation is small), you can choose not to perform segmentation. The segmentation condition corresponding to the network delay jitter can be: if the real-time delay jitter of the network exceeds the delay jitter threshold, for example, the delay exceeds 200ms, or the jitter is greater than 50ms, the initial request needs to be segmented; if the real-time delay jitter of the network is less than or equal to the delay jitter threshold, there is no need to segment the initial request. The delay jitter threshold can be flexibly adjusted according to the specific network environment and usage scenario.

[0051] In addition, it is also possible to determine whether the initial request meets the segmentation condition based on the load of the object storage pool. The load condition can be represented by CPU usage, memory usage, or disk I / O (input / output). If the load of the object storage pool is high, processing a single request may cause excessive pressure on the object storage pool, slowing down system performance and affecting the overall throughput. A segmentation condition corresponding to a load condition represented by CPU usage may be: when the CPU usage exceeds the usage threshold, such as exceeding 80%, the initial request needs to be segmented; if the CPU usage is less than or equal to the usage threshold, the initial request does not need to be segmented.

[0052] The process of segmenting the initial request may include: determining the segment size corresponding to each segment request according to the request object of the initial request; and segmenting the initial request according to the segment size to obtain the segment request.

[0053] Exemplarily, the maximum size of each segment request is preset to 10MB or 50MB to prevent a single sub-request from being too large and affecting performance. The initial request can be segmented based on byte ranges or logical units. For example, if the client requests a 100MB object, it can be divided into 10 10MB segment requests. Each segment request contains the starting byte position and the ending byte position of the data as a query condition for the object storage system.

[0054] Step 206: Request data from the object storage pool according to the segment request, receive first target object data returned by the object storage pool based on the segment request, and send the first target object data to the client.

[0055] Among them, the segmentation requests can be sent to the object storage pool in sequence in a serial manner, or multiple segmentation requests can be sent to the object storage pool in a parallel manner, so as to accelerate the acquisition of data. The object storage pool responds to each segmentation request and returns the segmentation object data corresponding to the segmentation request. The segmentation object data may include: data block content and metadata, wherein the data block content is the main data part, usually a fragment of the target object data; the metadata includes the checksum, timestamp, data integrity check and other information of the target object data to ensure the correctness of the data during the transmission process. After receiving the segmentation object data corresponding to each segmentation request, the segmentation object data is merged in the order of the segmentation request to obtain the first target object data. Specifically, the splicing order can be determined according to the byte range in each segmentation request, and the integrity check is performed on the spliced ​​data. If data is lost or damaged during the data transmission process, the object storage pool can be requested to resend the lost part of the data, and finally the first target object data is obtained, and the first target object data is sent to the client.

[0056] In a possible implementation, when the initial request does not meet the segmentation condition, data is requested from the object storage pool according to the initial request, and second target object data returned by the object storage pool based on the initial request is received, and the second target object data is sent to the client.

[0057] In the above object data access method, an initial request sent by a client is received; when the initial request meets the preset segmentation conditions, the initial request is segmented to obtain a segmented request; according to the segmented request, data is requested from the object storage pool, and the first target object data returned by the object storage pool based on the segmented request is received, and the first target object data is sent to the client. In this way, when the object storage gateway receives an initial request with a large amount of data sent by the client, the initial request is segmented, which can effectively reduce the bandwidth occupied by a single request, avoid a single request occupying too much network bandwidth, reduce the time required for each request, reduce the probability of timeout, and improve the overall performance and stability of the network, thereby improving the efficiency of the object data access method.

[0058] In an exemplary embodiment, in the provided method, the process of matching the segmented information based on the segmentation conditions to obtain the matching results includes: for each segmented information, using the segmentation conditions corresponding to the segmented information to perform comparison processing to obtain the sub-matching results corresponding to the segmented information; and determining the matching results based on the number of successful matches in the sub-matching results.

[0059] In which, in combination with the aforementioned embodiment, the segmentation condition corresponding to each segmentation information may be a quantized data interval. When the segmentation information conforms to the quantized data interval, the sub-matching result corresponding to the segmentation information is determined as a successful match; when the segmentation information does not conform to the quantized data interval, the sub-matching result corresponding to the segmentation information is determined as a failed match.

[0060] In a possible implementation, when the number of successful matches in the sub-matching result is greater than a preset segmentation threshold, the matching result is determined to be a successful match, and the initial request is segmented to obtain a segmented request; when the number of successful matches in the sub-matching result is less than or equal to the preset segmentation threshold, the matching result is determined to be a failed match, and there is no need to segment the initial request, and data can be directly requested from the object storage pool according to the initial request.

[0061] In one possible implementation, different weights are set for each segment information, and weighted processing is performed on the sub-matching results corresponding to each segment information to obtain a segment weight corresponding to the initial request. When the segment weight is greater than a preset segment threshold, the matching result is determined as a successful match, and the initial request is segmented to obtain a segment request. When the segment weight is less than or equal to the segment threshold, the matching result is determined as a failed match, and there is no need to segment the initial request, and data can be directly requested from the object storage pool according to the initial request.

[0062] Exemplarily, for each segment information, if the request header takes longer than the time threshold, record this feature as 1, otherwise 0; if the client version identifier is higher than the condition version identifier, record this feature as 1, otherwise 0; if the network bandwidth jitter of the client receiving data is greater than the jitter threshold, record this feature as 1, otherwise 0, and the jitter calculation is based on the current bandwidth value minus the past average value, and take the absolute value. Calculate the sum of the characteristic values. If the sum of the characteristic values ​​is greater than the segment threshold 2, the matching result is determined as a successful match, and the initial request is segmented to obtain a segmented request; if the sum of the characteristic values ​​is less than or equal to the segment threshold 2, the matching result is determined as a failed match, and there is no need to segment the initial request, and data can be directly requested from the object storage pool based on the initial request.

[0063] In this embodiment, whether to perform segmented processing on the initial request is determined based on the segmentation information. The segmentation strategy can be dynamically adjusted according to different requests from the client, real-time traffic and load conditions, and the optimal processing can be performed based on actual conditions, thereby enhancing the adaptability to different loads and requests.

[0064] In an exemplary embodiment, the provided method analyzes and processes the initial request to obtain segmented information, including: performing authority authentication processing on the initial request to obtain an authority authentication result; when the authority authentication result is authentication passed, performing protocol parsing processing on the initial request to obtain segmented information.

[0065] The request header or request body of the initial request includes authentication information, and the authentication information may include: API key (Application Programming Interface Key), token, signature or open authentication protocol (OAuth). The authorization authentication result is obtained by performing authorization authentication processing on the authentication information. The authorization authentication processing process may include: verifying whether the API key or token is valid by accessing the authentication server, and for the token, verifying whether it has exceeded the expiration time; if the authentication information contains a signature, verifying whether the signature matches the content and key of the initial request; verifying the authentication information through verification strategies such as access control lists and role permissions to determine whether the client corresponding to the initial request has the authority to access the specified object or perform operations such as reading, writing, and deleting. If the authorization authentication result is an authentication failure, it means that the initial request may have problems such as invalid API key, expired token, insufficient authority, or tampered content. An error response is generated according to the authorization authentication result, and the error response is returned to the client, and the processing of the initial request is stopped.

[0066] Protocol parsing refers to the process of parsing the request content corresponding to the initial request according to the protocol adopted by the initial request and extracting the segment information. Specifically, it can include: judging the protocol type used by the client according to the content type (Content-Type) or URL (Uniform Resource Locator) path information in the request header; based on the protocol type, determining the segment information corresponding to the initial request from the initial request.

[0067] In an exemplary embodiment, as shown in FIG3 , a method for accessing object data is provided, which is described by taking the method applied to the object storage gateway 104 in FIG1 as an example, and includes the following steps 301 to 3. Among them:

[0068] Step 301: Receive an initial request sent by a client.

[0069] Step 302: Perform authority authentication on the initial request to obtain an authority authentication result.

[0070] Step 303: When the authority authentication result is authentication passed, the initial request is subjected to protocol parsing to obtain segment information.

[0071] Step 304: for each segment information, a comparison process is performed using the segment conditions corresponding to the segment information to obtain a sub-matching result corresponding to the segment information.

[0072] Step 305: Determine the matching result according to the number of sub-matching results that are successfully matched.

[0073] Step 306: When the matching result is successful, the initial request is segmented to obtain segmented requests.

[0074] Step 307: Request data from the object storage pool according to the segment request, receive the first target object data returned by the object storage pool based on the segment request, and send the first target object data to the client.

[0075] Step 308: if the initial request does not meet the segmentation condition, request data from the object storage pool according to the initial request, receive second target object data returned by the object storage pool based on the initial request, and send the second target object data to the client.

[0076] It should be understood that, although the steps in the flowcharts involved in the above 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 is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may 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 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.

[0077] Based on the same inventive concept, the embodiment of the present application also provides an object data access device for implementing the object data access 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 one or more object data access device embodiments provided below can refer to the limitations on the object data access method above, and will not be repeated here.

[0078] In an exemplary embodiment, as shown in FIG. 4 , an object data access device is provided, including: a request receiving module 402, a segment processing module 404 and a data request module 406, wherein:

[0079] The request receiving module 402 is used to receive the initial request sent by the client;

[0080] The segment processing module 404 is used to segment the initial request to obtain a segment request when the initial request meets the preset segment condition;

[0081] The data request module 406 is used to request data from the object storage pool according to the segment request, receive the first target object data returned by the object storage pool based on the segment request, and send the first target object data to the client.

[0082] In one of the embodiments, the segmentation processing module 404 is also used to analyze and process the initial request to obtain segmentation information, which includes: request header time, client version and network bandwidth jitter; based on the segmentation conditions, the segmentation information is matched to obtain a matching result; when the matching result is a successful match, the initial request is segmented to obtain a segmented request.

[0083] In one embodiment, the segmentation processing module 404 is further used to perform comparison processing on each segmentation information using the segmentation conditions corresponding to the segmentation information to obtain the sub-matching results corresponding to the segmentation information; and determine the matching result according to the number of successful matching sub-matching results.

[0084] In one embodiment, the segment processing module 404 is further used to perform permission authentication processing on the initial request to obtain a permission authentication result; when the permission authentication result is authentication passed, the initial request is subjected to protocol parsing processing to obtain segment information.

[0085] In one of the embodiments, the data request module 406 is also used to request data from the object storage pool according to the initial request when the initial request does not meet the segmentation conditions, receive second target object data returned by the object storage pool based on the initial request, and send the second target object data to the client.

[0086] Each module in the above-mentioned object data access 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.

[0087] In an exemplary embodiment, an object storage system is provided, the system comprising: a client; an object storage pool; and an object storage gateway, configured to execute the object data access method provided in the above embodiment.

[0088] In one embodiment, as shown in FIG5, the object storage system further includes an intelligent segmentation module and a network element module. In the object storage system, the client communicates with the object storage gateway through the network element module. The object storage gateway is used to receive the initial request sent by the client, generate a corresponding sub-request according to the initial request, and send the sub-request to the intelligent segmentation module; the intelligent segmentation module is used to determine whether the sub-request meets the preset segmentation condition. If the sub-request meets the preset segmentation condition, the sub-request is segmented to obtain a segmentation request, such as segmentation request 1 to segmentation request N in FIG5; according to the segmentation request, data is requested from the object storage pool, and the first target object data returned by the object storage pool based on the segmentation request is received, and the first target object data is sent to the client through the object storage gateway. Optionally, if the sub-request does not meet the segmentation condition, data is requested from the object storage pool according to the sub-request, and the second target object data returned by the object storage pool based on the sub-request is received, and the second target object data is sent to the client through the object storage gateway.

[0089] In one embodiment, the intelligent segmentation module can be integrated into the object storage gateway or can be a standalone device.

[0090] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. 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 via a system bus, and the communication interface is connected to the system bus via 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 initial requests, segmented requests and first target object 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 client through a network connection. When the computer program is executed by the processor, an object data access method is implemented.

[0091] Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial 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 shown in the figure, or combine certain components, or have a different arrangement of components.

[0092] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0093] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0094] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0095] 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.

[0096] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments 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 this application can include at least one of non-volatile 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), magnetoresistive 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, etc., but are not limited to this.

[0097] 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 specification.

[0098] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations 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. An object data access method, characterized in that: The method comprises: Receive the initial request sent by the client; When the initial request meets the preset segmentation condition, segment the initial request to obtain a segmented request; According to the segment request, data is requested from the object storage pool, and first target object data returned by the object storage pool based on the segment request is received, and the first target object data is sent to the client.

2. The method according to claim 1, characterized in that When the initial request meets the preset segmentation condition, segmenting the initial request to obtain a segmented request includes: Analyze and process the initial request to obtain segment information, where the segment information includes: request header time consumption, client version, and network bandwidth jitter; Based on the segmentation condition, matching processing is performed on the segmentation information to obtain a matching result; When the matching result is a successful match, the initial request is segmented to obtain the segmented request.

3. The method according to claim 2, characterized in that The performing matching processing on the segment information based on the segment condition to obtain a matching result includes: For each of the segmented information, a comparison process is performed using the segmentation condition corresponding to the segmented information to obtain a sub-matching result corresponding to the segmented information; The matching result is determined according to the number of successful matching sub-matching results.

4. The method according to claim 2, characterized in that: The analyzing and processing the initial request to obtain segment information includes: Performing authority authentication processing on the initial request to obtain an authority authentication result; When the authority authentication result is authentication passed, the initial request is subjected to protocol parsing to obtain the segment information.

5. The method according to claim 1, characterized in that The method further comprises: When the initial request does not meet the segmentation condition, data is requested from the object storage pool according to the initial request, second target object data returned by the object storage pool based on the initial request is received, and the second target object data is sent to the client.

6. An object data access device, characterized in that: The device comprises: A request receiving module, used for receiving an initial request sent by a client; A segmentation processing module, used for segmenting the initial request to obtain a segmentation request when the initial request meets the preset segmentation condition; The data request module is used to request data from the object storage pool according to the segment request, receive first target object data returned by the object storage pool based on the segment request, and send the first target object data to the client.

7. An object storage system, characterized in that: The system comprises: Client side; Object storage pools; and An object storage gateway, configured to execute the method according to any one of claims 1 to 5.

8. 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 5 are implemented.

9. 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 5 are implemented.

10. 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 5 are implemented.

Images